Pytorch Version Error: Loss becomes NaN with LEARNING_RATE=0.001

When I cloned the code and wanted to train the model from the very beginning, I modified the configAVD2 file's LEARNING_RATE to 0.001 and RESIZE_IMG to 1 according to the paper. But this leads to "loss becoming NaN" during the training process after few iterations. (it works on LEARNING_RATE=0.0001)
Is there something I've done incorrectly? Thank you so much.
(PyTorch version is 0.4.0)

I'm not sure. When you say it "works on LEARNING_RATE=0.0001" what do you mean by works? You get a loss that isn't NaN? If so, does the network learn anything, i.e. does the mAP improve? Does it work with RESIZE_IMG=1 and LEARNING_RATE=0.0001?  What is the original size of the images?
You can try putting a breakpoint at line 223 of TDID.py and see what is the cause of the NaN loss. check the values of all the variables used in lines 221-223.
You can also check on lines 154-158 of train_tdid.py to make sure the resizing is happening as you expect.

Thank you for the reply.
I trained with the AVD dataset split 2 and the original size is 1920*1080.
Here's the appearance:

lr = 0.001 (same with the paper), doesn’t work
lr = 0.0001

resize image to 960*540 (same with the paper), works
not resize (same with the original code), doesn’t work

lr = 0.00001, works whether resize or not.

("not work" stands for I'll get NaN loss and "work" stands for the loss becomes lower and lower, and according to the out_img.jpg, if I train with the lower learning rate, the result makes sense so the network actually learns something. )
And I trained on the setting lr=0.0001 && resize for one epoch and I'm testing it now. Once I have the mAP report I'll let you know.

I switch my torch version back to 0.3.1 and won't get this error now.

Ok thanks.
I have experienced similar issues with other code when switching between Pytorch 0.3 and 0.4.
I will make a note on the README, and will continue to look for why the different version causes the issue.

Thank you so much

@Qiaoyf96 @ammirato
FYI, I've met the similar issue, and after debug, it solved.
In TDID.py, build_loss method of TDID class,
the line loss_box = F.smooth_l1_loss(bbox_pred, bbox_targets, size_average=False) / (fg_cnt + 1e-4)
=>
loss_box = F.smooth_l1_loss(bbox_pred, bbox_targets, size_average=False) / (fg_cnt.float() + 1e-4)
fg_cnt seems to be int type before, and which makes 1e-4 term fails to regularize the formula.


#1197 Show error for invalid number in Numberfield and Spinner controls

Fixes #1197
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

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

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

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

Another way to fix this issue is by removing allowEmpty flag. After that, carbon detects invalid input and shows error. However, this won't allow any numeric field to be empty.


Spine Atlases that refer to an image that contains an underscore character are not displayed.

Spine Plugin : e11c820
Phaser Build : 6bc858e
If a Spine atlas refers to a texture that has an underscore in its name, that texture will not display, and will instead return a "__MISSING" texture. I did some internal digging and it seems that the texture key is getting chopped before the first underscore, so it cannot find the texture by its referred name. I have attached an example of the error. For example, in the code I posted, the expected key name is "test_with_underscore.png", but it is being stored as "with_underscore.png"
SpineErrorTest_NamesWithUnderscores.zip

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


New versioning scheme.

I will change Dungeon's versioning scheme to something closer to semantic versioning.
A release that is not compatible with old saved files increases the MAJOR version.
A release that adds content in a backwards-compatible manner increases the MINOR version.
A release that makes backwards-compatible bug fixes increases the PATCH version.

Being used since v2.0.0.


Set fallback for DISPLAY

This PR set a fallback for the DISPLAY environmental variable.
If not present, it will fallback to the docker host IP address.

See https://docs.docker.com/compose/environment-variables/set-environment-variables/
See https://docs.docker.com/compose/environment-variables/envvars-precedence/

This wont work as a solution for MacOS because this:

On MacOS, ssh'ing in to the Cypress box gives me a $DISPLAY of /private/tmp/com.apple.launchd.e2GTZQiXPQ/org.xquartz:0
Which, on MacOS, Cypress has no access to.
A potential solution might be to add .Xauthority, according to some. However I've not found that even to exist on MacOS...


register must register metadata

#491

Pull Request Test Coverage Report for Build 1512

6 of 9 (66.67%)  changed or added relevant lines in 2 files are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.2%) to 63.611%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/registry/bootstrap.go
5
8
62.5%

Files with Coverage Reduction
New Missed Lines
%

core/options.go
2
85.96%

core/lager/logrotate.go
3
33.48%

core/config/key_generator.go
3
28.85%

Totals

Change from base Build 1509:
0.2%

Covered Lines:
5052

Relevant Lines:
7942

💛  - Coveralls


never-typed properties are required when instantiating object

Bug Report
🔎 Search Terms
never, discriminated union
🕗 Version & Regression Information
I am seeing this bug in Typescript 5.0.4 (and in the latest beta at time of writing 5.1.0 Beta, and in the Nightly v5.1.0-dev20230428), but I do not know when it was introduced. I've also checked all 4.X releases in the Typescript Playground and it is indeed reproducible in all of them.
This is the behavior in every version I tried, and I reviewed the FAQ for entries about never.
⏯ Playground Link
Playground link with relevant code
💻 Code
type Person = { firstName: string, surname: string; tailLength: never };

const me: Person = {
  firstName: "Homer",
  surname: "Simpson"
}

🙁 Actual behavior
When instantiating me, the following type-error is produced:

Property 'tailLength' is missing in type '{ firstName: string; surname: string; }' but required in type 'Person'.

🙂 Expected behavior
I would expect that never-typed properties should not be "required" properties.

Additional Context
The Playground link offers a minimal-reproducible case, but does not contextualise a real-world use-case. Of course I could just remove the tailLength property from the Person-type, and that would unblock me from instantiating me without a tailLength property. My real-world use case involves discriminated union patterns. I've been trying to build this Button component, which can render either an  or <button /> element, depending on the type property that I pass to it. Here's what I tried originally:
// Use-case Example #1

const Button = ({
  _type,
  href,
  onClick,
}:
  | { _type: "button"; onClick: React.MouseEventHandler }
  | { _type: "link"; href: string }) => {
  switch (_type) {
    case "button": {
      return <button className="button" onClick={onClick} />;
    }
    case "link": {
      return ;
    }
  }
};

However, this produces type errors on href and onClick, such as:

Property 'href' does not exist on type '{ _type: "button"; onClick: React.MouseEventHandler; } | { _type: "link"; href: string; }'.

Property 'onClick' does not exist on type '{ _type: "button"; onClick: React.MouseEventHandler; } | { _type: "link"; href: string; }'.

I can address these errors by making all props present on both sides of the type-union, using never:
// Use-case Example #2

const Button = ({
  _type,
  href,
  onClick,
}:
  | { _type: "button"; onClick: React.MouseEventHandler; href: never }
  | { _type: "link"; onClick: never; href: string }) => {
  switch (_type) {
    case "button": {
      return <button className="button" onClick={onClick} />;
    }
    case "link": {
      return ;
    }
  }
};

And this resolves the errors in the component definition, raises type errors at the call-location:
<Button type="link" href="https://www.typescriptlang.org/" />

Produces:

Type … is not assignable …  Property 'onClick' is … required in type '{ _type: "link"; onClick: never; href: string; }'.

So, there is a circular issue here. In my opinion, making never-typed properties "required" basically reduces their utility, because (unless I'm mistaken) there is no valid value which you can pass (not even any!).

This is working as intended, see #37104.
And technically, a property typed never is a property that should throw an error upon access, not a property that doesn't exist. You can't represent the absence of properties in TypeScripts type system, this would require the "Exact Types" feature.

Yes I see where you're coming from - but I suppose my objection is that instantiation is, by definition, not access. Or am I mistaken there?

interface A {
  a: string;
  b: never;
}

This type says it has two properties: one typed string, and one that throws an error upon access. You can't just omit the second property, it's part of the interface definition, you must provide it when constructing an object:
const a: A = {
  a: "abc",
  get b(): never { throw new Error(); }
};

And technically, a property typed never is a property that should throw an error upon access,

Is this ever a thing? I can't repro this anyhow or I'm unsure what kind of access you have in mind:
interface A {
  a: string;
  b: never;
}

declare const foo: A
foo.b // ok
const str: string = foo.b // fine, never is assignable to everything

That’s the point - never is assignable to everything because it’s uninhabited; you can’t produce a value of that type and must throw.  If you don’t, the code isn’t sound.

a property typed never is a property that should throw an error upon access

This doesn't really hold up as an objective truth, though. Plus, I think we're conflating thrown (runtime) errors and compile-time (type) errors, which are not the same thing.
const Button = ({
  _type,
  href,
  onClick,
}:
  | { _type: "button"; onClick: () => void; href: never }
  | { _type: "link"; onClick: never; href: string }) => {
  console.log(href);
};

The destructuring assignment operation is "access" - is it not? This code does not result in a thrown error, nor a raised type error.
I stand by my statement at the end of my original post - the utility of never types is handicapped by this behaviour - it would appear to my (admittedly uneducated) eye that the compiler needs to pick a lane: either it needs to let me omit the property upon instantiation, or there needs to be a valid value that one can pass to a never-typed property.

If you’re trying to ensure href doesn’t exist then you want to write href?: never.

Be aware that the solution by @fatcerberus does not guarantee mutually exclusive types either. It's always a possibility that both properties are defined.

And I essentially just repeated what Ryan said before:
https://github.com/microsoft/TypeScript/issues/47071#issuecomment-990084007

Record<string, never> describes a type that, if you accessed any of its properties, you'd get an exception.


added router link and resolve to open new tab between two pages

Describe your changes
Implemented feature to use middle click allowing to open Project page in a new tab from the front page. You can also middle click on the Projects in the header of the page to access the previous page in a new tab. Useful to have multiple projects opened
Screenshots (if appropriate):
Issue ticket number and link
178 : https://github.com/debiai/DebiAI/issues/178
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have increased the version number in the frontend/package.json and backend/swagger.yaml files
[x] I have checked that Black, Flake8, Prettier and Cspell are passing

 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.Fady BEKKAR seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Redirect not working on Brave Browser

Expected behavior: redirect out of the page when opening devtools via menu.
Actual result: nothing happens besides console being cleared over and over again.

Thanks for your feedback, I'll check it out

because the brave browser block javascript on website, maybe update notice redriect user to another site when user turn on block load javascript, call them turn off block javascript to continues view the website


Peaks outside of frequency range

In some (rare) circumstances, FOOOF can end up with a final peak set that includes a peak with a CF outside of the frequency range (outside of data it even sees).
Reason: our candidate oscillations are currently restricted to the actual frequency range, and dropped if they are too close to the edge, but the final fit procedure actually isn't adequately restricted. Currently we bound CF as guess +/- some range (defined in units of guess BW, I think), but not in a way that address edges of the PSD range. It appears the fit function is happy to extrapolate beyond the literal data it sees.
Solution: we need to update the bound passed into the fit function. Basically, this just needs to be a special case check, in which the CF bounds checks for the data frequency boundaries, and update appropriately. The only open question: this update procedure bound is another thing to be chosen - it can be chosen to be literal edges (so a 3-40 Hz PSD, with a candidate oscillation at 4.5 Hz would bound CF to something like [3, 6.5]), or include a boundary of the edge (so the bound would be something like [4, 6.5]), in the same way we have a boundary for the guesses.
Note that currently it is quite rare for peaks to be placed outside the frequency range (a small number of examples in millions of MEG fits). I presume this is largely because our guess-drop procedure does push away from doing this, and that it is only slightly weird edge cases in which the fit function settles on best solution including a peak outside the available range.

Side note: fixing this, I realized our CF-bound is pretty broad. Our cf_bound param is set in units of std-dev, but applied in units of 'bandwidth', and though this
For, so a peak guess of [10, 1, 2] ,where 2 is guess std-dev so 'bandwidth' is 4 Hz, and default cf_bound of 1.5, CF bounds, as [cf - 2 * cf_bound * peak[2], cf + 2 * cf_bound * peak[2]], ends up as bounded between 2-18 Hz, which seems like a really broad range (and helps explain how the possible range can extend outside frequency range).
Point being: this is a magic number, and I think, setting it, in my head, I didn't quite realize how broad it can end up. This is something we could explore a bit more (systematically), and maybe try to limit bit more.
Counter-point: I don't really know how much influence these bounds are, in the grand scheme of themes, they are probably not that important, as curve_fit presumably does well in finding the best actual peak, and if the guesses are good, is unlikely to end up with outputs that are super far from the guess CF.

Okay - the simple fix of updating CF bound to be within existing frequency range is pushed (simple version - literally checks that bounds are not outside f_range, and updates to f_range edge if not).

The premise of this issue is fixed. The note about CF-bound is separate (something to keep in mind), but not a problem per se, so I'm going to close this.


Fix build issue for feature/circle_ci_android_machine branch

Description
Closes https://github.com/CircleCI-Public/android-image-preview-docs/issues/5
Steps to reproduce
The workflow is able to succeed now (though it sometimes fails possibly due to flaky tests)

@mtwalli Would you be able to help me rerun the workflow from failed? The workflow was working on my fork, so I believe it should be working

@lokst  Thank you very much. It looks good to me.


Support CRACO v7

This PR allows craco-module-federation to work with CRACO v7 and Webpack 5

fix Webpack import for Webpack v5
fix dependencies
update node version to 16

Nice! Came here to see if anyone was on top of this!

I was looking for a solution to this as well. Thanks!


Remove sbt-scalajs-crossproject dependency

Updates org.portable-scala:sbt-scalajs-crossproject from 1.1.0 to 1.2.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.1.0).
You might want to review and update them manually.
site/src/main/mdoc/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.portable-scala", artifactId = "sbt-scalajs-crossproject" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1

We now get sbt-scalajs-crossproject through sbt-typelevel. I'm lazy so I did the change here in this PR.


Lancache.net has lost the documentation on how to disable/enable specific services

This used to be in the DNS readme (https://github.com/lancachenet/lancache-dns/blob/1c73dfdfbb6229d039cf25a175be19a2789a2aa6/README.md) but hasn't been transferred over to the variables page. It is on General, but isn't very clear to find. A sub page might be better in the index or a link out from variables

A search for "service" also doesn't find it, i suspect due to it not being a heading


can't add package by giturl (weight=3)

can't add package by giturl
when using a dummy path along, it says only giturl or path

it requires url like: https://github.com/ranatrk/demo_package/tree/master, that's not intuitive, we should allow branch somehow or don't bother if it's not there and use the default branch, however the branch name is used in the downloaded package directory name. let's keep that in mind

duplicate of  https://github.com/threefoldtech/js-sdk/issues/1120


Render Google AMP conform images

First of all - fantastic job building this stuff.  I love it a lot!
I have a question. Since we can also render AMP pages with next I wonder how complicated it would be to add a new param "?amp" which would render an AMP conform  instead of a  element?
My First thought would be a switch in Img.tsx but there might be better ways to achieve this
What do you think?

example webp with fallback


Recommending the use of next gen formats without adequate browser support

Welcome! Please use this template for reporting documentation issues on https://developers.google.com/web/.
Page Affected: https://developers.google.com/web/TODO
**Page Affected ** https://developers.google.com/speed/pagespeed/insights/
What needs to be done?
caniuse.com shows that jpg 2000 is hardly supported, the webp is hardly supported either, etc...
It's nice to recommend newer standards, but without universal dependable browser support, I find it unfair that pagespeed insights punishes for not using next gen formats, when those aren't majorly supported by browsers.

[ ] Appropriate type-something label has been added.
[ ] Appropriate section-something label has been added.

I would argue that WebP is well supported. At the time of writing, WebP is supported on over 75%  of browsers according to caniuse.com. https://caniuse.com/#feat=webp

@PaintNinja safari ios, no support. All iphone/ipad users can't use it. That's a large chunk of users. Safari itself doesn't support either, so mac users fall out also. That's a large user base that need a fallback.
Neither IE browser, which will mean that a lot of older users or corporate/government users can't see it either since they are IE locked in for activex support.
I could ignore IE, if safari would support webp. But without safari support, webp is mostly useless in the real world where we make websites, and supporting fallbacks is what we used to do in the heydays of IE versions and Netscape navigator.
I'm all for upgrading to webp when safari is on board. as long as Apple users can't use it, it's a useless feature and one shouldn't be "penalized" for not using it.

You can easily make image fallbacks with the  element, literally 3 lines of code. And in css you can just first define your fallback and then define the webp on the next line and if a browser doesn't support webp it ignores that line.

Content team finds image on pixabay.
team uploads image in cms from pixabay.
Image needs to be converted to webp.
Image needs to have srcset resizes to webp for responsive image loading
Original jpg image needs to have srcset resizes for fallback image.
Image needs to be included to host fallback src set and webp srcset.
That's a lot of work, and duplicate image data to host, plus management of files that need to be deleted when someone removes an image from the cms.
That's a lot more implementation cost than "just three lines of code"

<source srcset="photo.webp" type="image/webp">

</picture>```
That's it. You aren't required to define different sizes, you can just define a different format and it'll work.

Sure you may have to convert the image once if it's uploaded by a user in a different format, but it's only a one time conversion. It's already done on some cms implementations where they accept gif uploads and convert to mp4 (e.g. Imgur)

@PaintNinja My main gripe is having to host duplicate image content. We currently have 3gb of image data due to all the srcsets. This move would double our image data we need to host and manage.
If a push could be made for safari to support it, then I could just host converted files and have a one time change in the cms. currently, it's too large a strain for something that isn't widely supported yet, and for commercial websites, IOS and Apple users are usually the revenue driving force.
It will also increase the size of the generated HTML significantly.
currently:
<img data-sizes="auto" class="marketing-banner-image img-responsive marketing-banner-image-l lazyautosizes lazyloaded" alt="something something" title="something something" data-src="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_60_00auto.jpg" src="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_60_00auto.jpg" data-srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.jpg 1170w 107h, https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.jpg 1200w 109h" sizes="1140px" srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.jpg 1170w 107h, https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.jpg 1200w 109h">

would become
<picture
	data-sizes="auto"
	class="marketing-banner-image img-responsive marketing-banner-image-l lazyautosizes lazyloaded"
	alt="something something"
	title="something something"
	data-src="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_60_00auto.webp"
	data-srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.webp 1170w 107h,
				https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.webp 1200w 109h"
	sizes="1140px">
	<img
		data-sizes="auto"
		class="marketing-banner-image img-responsive marketing-banner-image-l lazyautosizes lazyloaded"
		alt="something something"
		title="something something"
		data-src="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_60_00auto.jpg"
		data-srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.jpg 1170w 107h,
		https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.jpg 1200w 109h"
		sizes="1140px">
</picture>

That's even leaving behind the consideration if the lazyloading library will work properly with nested img elements.
It's a lot more cpu power wasted, a lot more data traffic wasted in useless html, a lot more storage wasted, a lot more management solutions that need to be implemented for the removal of discarded data etc...
A blanked switch to new standard is easier to implement.
I'm fine with webp being a recommendation. The reason I opened this issue, is that it shouldn't count against you when you don't use it in the reporting.

A few of things to note: first off, that's not the correct syntax for the <picture> element. There's a lot less duplicated code in reality than in your example (e.g. you don't need to put the alt, title, etc... twice).
Here's what your theoretical example might actually look like with the correct syntax:
<picture class="marketing-banner-image img-responsive marketing-banner-image-l lazyautosizes lazyloaded">
    <source srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.webp 1170w 107h,
	    			https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.webp 1200w 109h"
    type="image/webp">
    <source srcset="https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1170x0_100_00auto.jpg 1170w 107h,
                    https://www.example.com/app/uploads/public/5ce/3a8/483/77879/something-something--1200x0_100_00auto.jpg 1200w 109h"
    type="image/jpeg">

</picture>

Secondly, why are you worried about HTML size? You might increase the filesize of the HTML by a KB or so, sure (probably much less when factoring in gzip/brotli compression), but you'll reduce the bandwidth usage for the majority of clients that support WebP by a much larger margin (potentially hundreds of KB. at least tens of KB).
Also, why those sizes? It doesn't make sense to have two photos that are 33px different in size, the browser can probably do a better job resizing the larger image. Having one image that's half the size for small mobile screens and another image that's the full size would be a more logical use of srcset sizes.
I agree that it would be easier if every vendor just supported a given modern format (be it FLIF, JPEG-XT, WebP, BPG, HEIC/HEIF or whatever), but we're not at that point yet. However, there's a lot of options that can be used in the meantime.
If you don't care about bandwidth usage and page load times too much, you probably shouldn't be worrying about different image formats at all.


Unkown error for query partition key <> value || != value

表语句
CREATE TABLE `t1` (
  `k1` bigint(20) NOT NULL COMMENT "",
  `c1` bigint(20) NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(`k1`)
PARTITION BY (`k1`)
DISTRIBUTED BY HASH(`k1`) BUCKETS 32
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"enable_persistent_index" = "false",
"replicated_storage" = "true",
"compression" = "LZ4"
);

插入数据
insert into t1 values(1, 1);
当查询分区键不等于存在的分区键值时报Unkown error
mysql> select * from t1 where k1 !=1;
ERROR 1064 (HY000): Unknown error
mysql> select * from t1 where k1 <> 1;
ERROR 1064 (HY000): Unknown error
下面是OK的语句：
mysql> select * from t1 where k1 =1;
+------+------+
| k1   | c1   |
+------+------+
|    1 |    1 |
|    1 |    1 |
+------+------+
2 rows in set (0.01 sec)
mysql> select * from t1 where k1 !=2;
+------+------+
| k1   | c1   |
+------+------+
|    1 |    1 |
|    1 |    1 |
+------+------+
2 rows in set (0.01 sec)

Looks like it's related to partition. The bug is repeated on versions 3.2.6, 3.2.7. Not on 3.2.4.
SQL Error [1064] [42000]: Unknown error
Workarounds:
disable PARTITION
or
select * from t1 where k1 not in (select(1))

The main migration to Starrocks has a lot of such query syntax, and the migration process will be more complicated. There are of course many ways to workaround. I hope to upgrade to 3.2x or above as soon as possible.


autorandr: 59f6aec0b -> 53d29f9

Motivation for this change
This PR changes autorandr to the python branch of phillipberndt's for of autorandr.
The main reason for this is that the legacy branch seems to no longer work with a current version of xrandr, resulting in an failed to parse 'x' as a position error when trying to apply a profile.
In addition, disper support, the reason I believe for using the legacy branch, is no longer valid as disper itself does not support nvidia drivers of version >= 300 as of version 0.3.1 with the reasoning that those drivers support xrandr. Xrandr support however in incomplete in disper, making it effectively defunct on non-legacy hardware.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

LGTM from a explanation point of view. Have not reviewed the code.
On Sat, Nov 26, 2016 at 3:47 PM Mention Bot<EMAIL_ADDRESS>wrote:

@kampka https://github.com/kampka, thanks for your PR! By analyzing the
history of the files in this pull request, we identified @coroa
https://github.com/coroa, @grahamc https://github.com/grahamc and
@rycee https://github.com/rycee to be potential reviewers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/20744#issuecomment-263084794, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAErrNSLJ0MLn4RjDo1FNASBDz_V0md0ks5rCJrQgaJpZM4K8_NL
.

Haven't had time to look at this but at some point I used the Python branch myself and this was the expression I used:
{ stdenv, fetchFromGitHub, python3Packages, xrandr }:

stdenv.mkDerivation rec {
  name = "autorandr-${version}";
  version = "20160509";

  src = fetchFromGitHub {
    owner = "phillipberndt";
    repo = "autorandr";
    rev = "6cd92b657027423721a29dfe0c7080483cdfc81e";
    sha256 = "01m8q8jqz8jmvsfpw1jb13yc11wrfim9hj7c496advp21krj7ynz";
  };

  buildInputs = [ python3Packages.python python3Packages.wrapPython ];

  patchPhase = ''
    substituteInPlace autorandr.py \
      --replace "popen(\"xrandr" "popen(\"${xrandr}/bin/xrandr" \
      --replace "\"xrandr\"" "\"${xrandr}/bin/xrandr\""
  '';

  installPhase = ''
    mkdir -p $out/bin $out/etc/bash_completion.d
    cp -v contrib/bash_completion/autorandr $out/etc/bash_completion.d
    cp -v autorandr.py $out/bin/autorandr

    wrapPythonPrograms
  '';

  meta = with stdenv.lib; {
    description = "Automatic display configuration selector based on connected devices";
    homepage = https://github.com/phillipberndt/autorandr/;
    maintainers = [ maintainers.coroa ];
    license = licenses.gpl3Plus;
  };
}

I don't know how relevant it is now but maybe there is something of interest to have there. I notice, for example, that the bash completion is not installed in this proposed PR.
Also, since the package is built from a git revision and not a formal release I believe the name should include "unstable" , i.e., name = "autorandr-unstable-${date}";. See https://nixos.org/nixpkgs/manual/#sec-package-naming

@rycee Thanks for sharing your expression, it was very useful.
I am aware of the naming policy, but I am unsure how renaming the derivation will impact the upgrade path.
Can you maybe shed some light on that?

@kampka if you mean the unstable prefix. you can change it without breaking anything.

@Mic92 Alright, done.

@kampka you have not uploaded any updates so far.

@Mic92 I have squashed the commits, sorry if that confuses the process.
Anyways, I noticed there is still an issue with the python version that I am having trouble fixing.
When using the batch mode, autorandr tryies to figure out its own binary [1], which fails if called from udev or systemd.
If someone has a good idea on how to patch / fix that, I'd be glad to hear it.
[1] https://github.com/phillipberndt/autorandr/blob/master/autorandr.py#L791

@kampka ok usually github rendered such changes differently.

@kampka if you mean the unstable prefix. you can change it without breaking anything.

Upgrading of imperatively installed programs (nix-env -i) uses the name of derivations to find the upgrade. So if I am correct add unstable might break that. We should document this behavior.

Anyways, I noticed there is still an issue with the python version that I am having trouble fixing.
When using the batch mode, autorandr tryies to figure out its own binary [1], which fails if called from udev or systemd.
If someone has a good idea on how to patch / fix that, I'd be glad to hear it.

Use substituteInplace ?

Ping?


[MAINT] update contributors

companion PR to bids website https://github.com/bids-standard/bids-website/pull/476
some BEP leads were not listed in contributors
move all emails of BEP leads from the BIDS website to citation.cff of the spec to have only one instance of them
add new contributors from some BEP
add contributors who contributed to some tools

converting to draft:

[ ] check if some of the new contributors have a github account (I know some do)
[ ] need to add a few more contributors from some recently developed BIDS tools

TODO (but for future PRs):

[ ] add github usernames to contributors who have one
[ ] update affiliations (help to know where our contributors are from)
[ ] check people who have contributed to repos on BIDS and BIDS apps github organization, tools / converters repos...
[ ] check people mentioned on BIDS papers (that probably should be listed as contributors ?)

For reviewing purposes, .tributors is the thing that's being changed, and everything else flows from that? And there are a lot of new email addresses. Is everybody okay with this?

Yes the tributors is meant to be the ground truth and everything else should be generated form that.
The emails in here were those that were in the bids website metadata for the BEP leads or in the Google docs of the BEP.
I have not double checked with every person that they are OK having the email being in the bids spec.
I did check with a few people when "deduplication" of emails.

I want to get back to this one tomorrow to try to wrap it up.


Does not work with ipynb files (jupyter Notebooks)?

Doesn't seem to work with ipbynb files (jupyter Notebooks), right?

Yes @AP3dr, you're correct, ipynb files are currently not supported. Jupyter notebooks are special files that open on a special interactive editor (not a regular vscode editor).
I will look into supporting this soon.

Perhaps you would like to get some inspiration from this extension that does work with jupyter notebooks: https://github.com/zhcode-fun/file-size


API review for Storage + Database modules

Parent issue: #24356
Tasks

[x]  Fix api review problems
[x]  Write gist about resources

linked PR: https://github.com/Azure/azure-sdk-for-java/pull/25896

close this issue, since the linked pr has been merged


Todo before release

[x] Tool enchants
[ ] Global enchants
[ ] Bow enchants
[x] Armor enchants
[ ] Helmet enchants
[x] Boot enchants
[ ] Check to make sure you can enchant item
[ ] Enchanting

How do I put this on my server I will give you credit

Get DevTools. Download the zip and extract it. Then move the folder to plugins folder. Start server, do /makeplugin PiggyCustomEnchants and now you have a phar in your DevTools folder.

I can't see enchant on my weapon / item

That is an issue that only happens on Tesseract.

This happens on genisys too

Tesseract is basically Genisys, they are the same except Tesseract is a mix of both Genisys and pmmp.

It's a good plugin but custom enchant don't pop up on items

Add CustomEnchants book?

that will be nice

can you enchant it even with the original /enchant?

Nope.

Didnt felt like making another issue for this as it would waste a ticket so I just wanted to Thank You for your awesome plugin. Thanks a lot @DaPigGuy

Your welcome.

Hi, I am an Owner of a server and YOU ARE INCREDIBLY GOOD at making plugins it's astounding :1st_place_medal:
I just would like to say maybe in a future update there should be a way to buy Enchants for example /buy berserker 5 and you bought the enchant that would be awesome for my server!
Keep up the good work guys 👍
And please help make this plugin happen please :) thanks and in sorry if this isn't where u post ideas I'm new to github :P

Might make that a separate plugin.

Omg thx so much!
I would love to make you an op in my server if you want !
I'm really looking forward for this plugin thx so much.
I was thinking if quitting my server because I couldn't figure out away
people can buy/use the enchant, all my friends donated in the server
believing me ,
But what you said now is a glimmer of hope for me thanks!
On Jun 15, 2017 2:34 AM, "DaPigGuy"<EMAIL_ADDRESS>wrote:

Might make that a separate plugin.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DaPigGuy/PiggyCustomEnchants/issues/2#issuecomment-308603676,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcFHWr1u4AaSNKpEaQLOxRqwtM9IPQNVks5sEIo1gaJpZM4NMWFK
.

Hi,
I just had an idea which would make this plugin a HIT...
If you guys can some how make it so if you do /cebuy add charge 10000
This command basically means you created a command where you buy can buy he custom enchant charge for 10k
Then you can do
/cebuy charge
This will buy the enchant charge and apply it to the sword.
If you need anything ask me I. Happy to help thus wonderful project with inspiring people!
I am willing to give you FTP access and Console access to my server :D
Thanks mrpiggy and continue your awesome work!
PS I'm vegan :3

Hi
I really have a big promblem i cant use it it wont work for me

Please stop spamming. Also added support for 3.0.0-ALPHA7

Please submit custom enchant ideas here. (https://docs.google.com/forms/d/e/1FAIpQLScfWdk8OyQ6NNw6KiJxP_4CH4GHnKlaFr4VfZIQojk7OPlyoQ/viewform)

PiggyCustomEnchantsShop has just been released. get it here

can you please accept my friend request is discord my discord is hexwarriorfir#2006, i am having trouble adding the custom enchant plugin so would you might helping me really quickly?, i'm a starter, sorry

I can halp

You should add an enchant (for any item really) that removes all enchantments on drop, 100% of the time (or 25 percent per level with 4 levels) This would be useful for enchants you only want with certain sets of armor, so you can prevent players from dropping the item and another player picking it up, or another player killing the player with the special item and then using it.


Dashboard is working only partially on FireFox

some of the panels show blank

Are you able to upload screenshots about this?
It would be also helpful if you can post details of your Firefox (like build number and complete User Agent string).
:D

thanks @mautematico :)
@eliktz could you please clarify your problem?

@mautematico @micrum Thanks for your replies, after further investigation turned out there was something incoherent with how i set up the html.
Thanks anyway and keep up the good work

@eliktz thanks for using AMD, closing the issue


mbyte character support

Would you please add mbyte character support?
Highlight all the same single character in range [\u4e00-\u9fa5]  is all I need.
Thank you very much.

I'm not sure what you mean. Can you provide an example and what you expect to be highlighted based on your cursor position.

Treat character that in range of [\u4e00-\u9fa5] as a word.
Then we can achieve

Highlight all the same single character in range [\u4e00-\u9fa5]

Chinese character and word is different from English letter and word because they don't have delimiters.
So we can treat the tiniest textobj of Chinese i.e. character in range [\u4e00-\u9fa5]  as a word.
Then we can highlight the same pseudo word as usual.

If we have a this match pattern , we can even do more on it:
use text segmentation to highlight other textobj.

use text segmentation to highlight other textobj.

What does this mean?
As for matching specific unicode characters as whole words, vim-illuminate uses \k which is controlled by :h 'iskeyword' which doesn't support unicode characters AFAIK. vim-illuminate loosely highlights the same thing matched by the motion iw (try viw on your text and you will see what it highlights). To add support for matching specific unicode characters I would likely add an option to match against a regex pattern along the lines of [a-z] but with unicode characters. However, I'm not sure about adding this, I'm going to think about this for a couple of days.

Text segmentation should be done by tools like jieba or other natural language grammar checkers.

Text segmentation should be done by tools like jieba or other natural language grammar checkers.

For the record I was confused by textobj because it means something very different than simply the tokens in a document, for example vim-illuminate to an extent highlights the text object iw, while there are no text objects for single unicode characters.

You are right. Thank you very much.
I realized that I should make a custom textobj to cooperate with vim-illuminate, that's Vim way.
I will learn to write plugins.


Add spring autoconfiguration for metrics and prometheus reporter

This PR contains code moved from this PR: https://github.com/opentracing-contrib/java-spring-cloud/pull/15
An example of how it simplifies an example can be seen in this PR: https://github.com/objectiser/opentracing-prometheus-example/pull/13

@jpkrohling @pavolloffay Thanks!


exit after redirect

Note: wp_redirect() does not exit automatically, and should almost always be followed by a call to exit;:

Thanks!

thanks for quick response
at webbiz.com we had most of these cleanups but thanks to painkiller it’s now even better :heart:


Transport modes

Closes #45

TODO:

[ ] Use TransportModes directly in the controller (with an all method)
[ ] Basic editing functionality
[ ] Backend tests
[ ] Frontend style tests


Possible path parameters listed as body parameters in create from template javascript example

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/rest/reference/repos#create-a-repository-using-a-template--code-samples
What part(s) of the article would you like to see updated?
The current javascript sample for creating a repo using a template has template_owner and template_repo as keys in the body parameters object. (Notably, the sample cUrl command does not include these keys, and they are labelled as path parameters in the preceding table.)
Using these keys results in the following error:
RequestError [HttpError]: Invalid request.

"template_owner", "template_repo" are not permitted keys.

Suggestion is to omit these keys, changing this:
await octokit.request('POST /repos/{template_owner}/{template_repo}/generate', {
  template_owner: 'template_owner',
  template_repo: 'template_repo',
  name: 'name'
})

To match the cUrl equivalent, this:
await octokit.request('POST /repos/{template_owner}/{template_repo}/generate', {
  name: 'name'
})

Additional information
If I understand correctly, these samples are script generated and not human editable. If I am incorrect on that, I will happily file a PR if someone can point me to the appropriate file.

My money
On Tue, 25 Jan 2022, 11:57 docubot, @.***> wrote:

Closed #14636 https://github.com/github/docs/issues/14636.
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/14636#event-5949293016, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXID4ISL7ELFMQ5VBPXFNZ3UX2FZ5ANCNFSM5MXMDETQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Dont show splash in case of network issue

Users are complaining that it happens in middle of some action

[x] increase timer to 5 seconds
[x] dont show splash - just show dialog

@sirpy The dialog appears after around 5 sec, splash screen isn't displayed
Video: https://www.screencast.com/t/N0u8cCF5KyCV
Checked on DEV V1.0.6-1
LG V30+ // Android 8.0 // Google Chrome 84.0.4147.111
Desktop: Windows 10 // Google Chrome  84.0.4147.125
iPhone 8 //13.3.1


recon image has shape (width+1,height+1)

$ ipython
Python 2.7.10 (default, Oct 14 2015, 16:09:02)

IPython 2.3.0 -- An enhanced Interactive Python.

In [1]: import numpy as np

In [2]: from abel.basex import BASEX

In [3]: im = np.loadtxt("O-ANU2048.txt")

In [4]: (n,m) = np.shape(im)

In [5]: print (n,m)
(2048, 2048)

In [6]: recon,speed = BASEX(im,center=(int(n/2),int(m/2)),n=n,basis_dir='./',verbose=True,calc_speeds=True)
Loading basis sets...
0.72 seconds
Reconstructing image...
16.19 seconds
Generating speed distribution...
2.07 seconds

In [7]: print (np.shape(recon))
(2049, 2049)

PS: Great work guys!

Could you retry with an image that has width = odd integer?

Hi Steve,
thanks for pointing this out.
As far as I understand, the current BASEX implementation only supports n odd, and will raise an error if that is not the case. When given an image with an odd n, the BASEX transform produces a result of the same shape, as checked by this test. Now, what must be happening here is that the centering function pads the original image to make it odd, which result in a transform of shape (2049, 2049).
What I'm wondering about is there actually a physical reason why we can't generate basis sets for n=even?  If so, we probably should ensure that the centering function produces the result of the shape (n x n) and raise an error if it is odd in the BASEX function and not just in the generate_basis_sets routine. What do you think about it ?

Thanks for the very fast response. The odd size image is a good point. I have trimmed the image by one pixel and the new basis calculation in progress.
Unfortunately, I am unfamiliar with the basex algorithm and do not know any reason for the odd pixel image size.
My group uses the Hansen and Law J. Opt. Soc. Am A2, 510-520 (1985). I have written a version that could be included, as an alternative to the basex method (and onion peel). I am just waiting on approval for the upload from my colleague. The agreement is excellent apart from a small displacement in the radial position of the speed profile.

Oh, this is weird, previously we would always produce an image that had an even size! We must have switched something when we were messing with the requirements for n and nbf.
I  see a conceptual reason why there should be any odd/even requirement for n, though I would expect that having nbf be the same odd/even character as n makes the most sense.
For computing the speeds, it makes the most sense not to have a "zero pixel", which we would have if n is odd. (I think that for the speed calculation to be strictly correct, we should be multiplying by a radial factor to take the volume into account. We currently do a naive angular integration of the 2D image that does not take into account the real 3D shape.)
We would be very happy to have the Hansen and Law iterative method incorporated into PyAbel. It seems to produce a bit less noise (especially centerline noise) than BASEX. Does it take a long time? I recall using one of Vrakking's iterative methods several years ago, and the results were good, but it took several minutes even for 1000x1000 pixels. I suppose downsampling the image to a smaller size could improve the speed...
Either way, it would still be fun to experiment with! Having more methods to compare will just make things better.

Oh, and thanks for pointing out that basex.exe cannot handle negative values. I did not realize this. We will need to point this out (along with the ability to use large images) if we write a "Features of PyAbel" section! :)
One more thought about the 2048->2049 bug: It could just be the centering algorithm. If you have an even number image dimension, then it's not actually clear where the center should be. For example, if your image is 2 pixels wide, then the center is actually between pixel 0 and pixel 1.
What happens if you set the center to be 1025 instead of 1024 as you are currently doing?

Excellent, open source wins.
The Hansen and Law algorithm core is ~13 lines of code. The inversion for a 2048x2048 pixel image takes  42 sec cf 16 sec for basex (for an already constructed basis), so about 1/2 the basex speed, but very usable. It is great to have other algorithms to use, and compare, which helps track down implementation faults, possibly centring in my case.
Good comments about the definition of the image centre. While on this topic,
IMO centre, and the vital image circularization, should be external to the inversion algorithms, otherwise each new inversion algorithm will need to duplicate the centre offset code.
My images are centred with respect to left cf right, and top cf bottom radial profiles, and are self-consistent with my own code (of course). For pyAbel I played with different centre offsets with the results that the spectral features broadened, so the image centre appears consistent with pyAbel.
For even pixel number images, the centre is not a pixel, but the grid between pixels. It appears to be more complicated for odd pixel number images.

Thanks for the details Steve. 42 seconds is not so bad for a huge image like that. The reduction in the centerline noise could be worth it depending on the situation. So yes, it would be great to incorporate it.
The centering code actually lives in abel.tools. And you can use abel.basex.basex_transform if you just want the transform and no centering. The abel.BASEX function just wraps the centering, basex transform, and angular integration (speeds generation) into a single function in case people were looking for a one-liner for processing their data.

So, here is a minimal example that reproduces a problem with the centering function:
import numpy as np
import matplotlib.pyplot as plt
import abel

data = np.zeros((5,5))

data[2,2]=1

fig = plt.figure(figsize=(12,6))
ax1 = plt.subplot(121)
ax2 = plt.subplot(122)

d2 = abel.tools.center_image(data,center=(2,2),n=5)

ax1.imshow(data,interpolation='nearest')
ax2.imshow(d2,interpolation='nearest')

ax1.set_title('Raw data')
ax2.set_title('Center=(2,2)')

plt.show()

In the case of an image with an odd-size image, the center is clearly defined. But for an even-sized image, we need to make a formal decision if the center is at the left or right edge of the defined pixel.

Hah, as an even-size image person, I tend to think that the even image centre is clearly defined, as the bottom left corner of the pixel (or the grid). This also facilitates the use of Python slicing functions.
In reality the pixels are irrelevant. The image centre is defined with respect to the centre of symmetry of the measurement.
[May not be on topic]
I have not looked at the centre issue in detail, but the basex algorithm appears to do a great job for even-size images, so excluding even-sized images from the basex inversion is too stringent a condition.

To add to the discussion, independently of the centering function, it looks like currently BASEX doesn't handle well even image sizes.
For instance, here is a reconstruction of the Gaussian with n=21, nbf=11, which is correct except at the origin,

now if I disable all the checks in the basis generation, and force it to run with n=20, nbf=10, I get the following image that is wrong,

Therefore, even if we agree on the way to fix the centering function (which we should at some point), the BASEX algorithm will produce incorrect results (and somebody would need to redo the math to understand why).
Well, essentially this is only a problem when analyzing images (10x10), for e.g. 1024x1024 images, setting the center with +- 1 px precision should not matter (particularly as there is amplification of the noise on the axis), no? Can't we just keep the processing the way it is now (i.e. centering function that produces odd shapes, process with abel) and then simply remove one pixel row/column to get to the size of the original image? This way we would support both odd and even image, and although this is not ideal nor very clean, for all practical applications this shouldn't be an issue, don't you think?

The even basex result appears to be correct, apart from the displacement off-centre. I agree that "for all practical applications this shouldn't be an issue". Definitely, allow basex processing of even images.

@stggh, when you say that you define the center as the bottom left of the pixel, you have the origin at the bottom left, correct? So, the center is at the "lower index" side of the pixel in both the horizontal and vertical directions. This definition makes sense to me, so I would recommend that in the case of even images, we adopt the convention that the center is located at the low-index side of the defined pixel. This means that the defined center has different meanings in the case of odd and even sized images, but this seems unavoidable and as long as we document it, users should not get too confused.
@rth, in the short run it looks like we should slide the even-sized image transform over a pixel in order to get it to line up. In the long run, we probably need to re-write the basex code for better readability and agreement with some sort of analytical math, either the Dribinski Rev. Sci. Instrum. paper or something that we write ourselves. We can put that off for a while.

Agreed, for the even case, although, counting pixels from bottom/top is depends on the image format definition, and is not important for all (velocity-map ?) images which are z-symmetric.
Having not previously encountered an odd-pixel image, the even centre definition makes perfect sense.
I have just realised that the hansenlaw recursion will work with odd images, it is only the image slicing that breaks. In principle, HL does not care about pixels, each row is just a 1d grid. However, I prefer the (more common?) grid definition of the centre. I also think, that somehow we should use the same centre definition, otherwise confusion will reign.

Now that I think about it more, the basex output for the even-sized image is not really correct. It contains a "central pixel", which an even-sized image should not. So, our basex algorithm only seems to make sense for an odd-sided image. I think that @rth is correct that the "quick fix" is to just make the original image odd-sized. In this case, it seems like the most honest thing to do would be to also return an odd sized image to the user.

This is tricky. I would prefer that recon has the same size as the input image. Your plan for even images is to add one row and column AND shift the centre by 1/2 a pixel, then apply the basex inversion, returning an odd size image.   I just want to check at the centre is also relocated? Tks.

@DanHickstein would it make sense to eliminate the "first" basis function (k = 0 case, Fig 1, Dribinski et al paper) in the case of even functions? That way, there wouldn't be a need for a central pixel.

Hmmmm, okay, maybe I need to go back and read the paper and figure out what's going on with the basis set generation. I think that you're correct that we need to eliminate the center basis function in the case of even sized images. I have some travel and other obligations for the next few days, so if one of you has time to think about this, that would be great. Otherwise I can work more about this later this week.

@DanHickstein another possibility to think about is creating a "fake" column/row/both in even sized images (possibly by taking the average of the two columns/rows on either side of the "real" center), inserting it into the even raw_data and doing the transformation.
We could then return the transform as-is to the user, or remove the added fake column/row/both and return a transform of the same size as raw_data.

@DhrubajyotiDas - the image centre would need to be also shifted = my query

So just summarize the conversation above.
Problem 1. I think we all agree on the definition of the center for an image as illustrated the @stggh comment.  The centering function should be fixed properly in PR #38, #37.  This can be done in v0.6
Problem 2. The BASEX transform currently does not work with even image sizes.

Approach 1. Return the an odd reconstruction even if the image is even => I think that's not ideal (shapes should be preserved), and besides since PR #38, #37 fix the centering function it will not produce odd images for an even input anymore.
Approach 2. Comment checks for odd images in BASEX, pass even image, then shift the output by 1/2 pixel (i.e. interpolate the result on a new grid).
Approach 3.  If the image is even, add a fake central row,  pass the image to BASEX, then remove the added row (@DhrubajyotiDas)
Approach 4. If the image has an even shape, eliminate the "first" basis function. Read the paper etc..

I think that the image size should not be changed by the Basex transform. If we want a quick solution, I would rather go with the Approach 3., as interpolating on a new grid to shift by 1/2 pixel in Approach 2. would also have other undesired side effects (not sure what happens to noise etc). We could do this in v0.6. The clean solution would be  Approach 4. which would require reading the paper in more detail. Personally, I won't be able to look into it this week.
So maybe we can implement the Approach 3.  which won't be very hard and finally release v0.6? Then we can work on fixing this problem more thoroughly under v0.7 with the Approach 4.  ?

Excellent summary and solution. I agree. The resulting speed data may also need correction?

Today, on the call we arrived at the following conclusions about even vs odd images:

Each transform function should just complete the transform for odd images. (This works for all of the transform methods except for the onion peeling method, but it's possible that it can be modified.)

The abel.iabel/abel.fabel methods will allow for centering with a center specified by the central pixel, which generates an odd image. The array size returned by the function will be odd, so if an even image is passed, the image shape may not be preserved.

We will provide code that allows users that have even-sized images (say from a CCD camera) to re-interpolate them to odd-sized images through a half-pixel shift. Currently, this is implemented in the tools.vmi.find_image_center_by_slice() function, though I wonder if it would be better to incorporate this directly into the centering function. We could allow users to specify the center in terms of decimal pixels and re-interpolate the image by a fraction of a pixel, ultimately generating an odd-sized image.

We have now implemented a abel.tools.center.center_image() function that uses interpolation to always produce an odd image. So, I think that we can close this issue.


how to set color variations?

how to variation by args.color?

The colors are provided as hex values.
what are exactly hex values?  Is there a reference list yet?


Update RBAC for compatibility with OpenShift 4.16

Checklist

[x] The PR has a meaningful title. It will be used to auto-generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[x] PR contains a single logical change (to build a better changelog).
[x] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.

It's a good question, I wasn't sure whether that codebase is openshift-specific.

Closed in favor of https://github.com/appuio/alerts_exporter/pull/33


using pointer semantic on value slice range

The DB product slice uses value semantics. While ranging on it to convert to the core product, we can use pointer semantic instead of value semantic to prevent an extra copy on the range.
I know it's not too much optimization. 😅

I hear you but unless the profiler is saying this is a performance issues with the service, it's a premature optimization that is taking an exception to maintaining consistent data semantics.
Let's keep with the data semantic consistency until we can't.

I see this engineering decision about consistency and it's beautiful.
Also, I ran a benchmark test for these semantics:
goos: darwin
goarch: amd64
pkg: valuepointer
cpu: Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
BenchmarkRangeValue-8               4080            269524 ns/op          647169 B/op          1 allocs/op
BenchmarkRangeValuePointer-8        4957            243476 ns/op          647171 B/op          1 allocs/op
PASS

BenchmarkRangeValue benchmarks the range for value slice using value semantic (i, val := range)
BenchmarkRangeValuePointer benchmarks the range for value slice using pointer semantic (i := range)
It's not too much 😅.
Feels free to close the pull request.

Yea, 26 microseconds. This is usually the case with most things internally.


inline script tags break IE

This is invalid:
element("script", {}, [ text(" code ") ])

won't fix for 0.7.x


Same name Problem when removing layout

If I want to remvo a layout which isn't the first in the list (Layout.AssociatedBlock.name != *papaer_Space) then the problem appears "There is already another block with the same name.".
The problem starts in the class Layouts, Method Remove by renaming the paperspace block names.
If i remove the secound layout the name *papaer_Space is still in the list, but the code trys to set the same name for another element.
foreach (Layout l in this.list.Values)             {                 // rename the corresponding PaperSpace block                 if (l.IsPaperSpace)                 {                     string spaceName = index == 0 ? Block.PaperSpace.Name : string.Concat(Block.PaperSpace.Name, index - 1);                     l.AssociatedBlock.SetName(spaceName, false);                                       index += 1;                 }             }
Maybe the problem can be solved by reversing the layout list.
Or by renaming the Layout.AssociatedBlock.names first by using names outside the autocad naming convention.
Timm

ANother maybe the same problem:
I starts with an importet *.dxf.
Inside AutoCAD I manually created layouts, after i Made a mistake I deleted one layout in this *.dxf and created another new one.
Now I see that in my *.dxf Model_Space, Paper_Space, Paper_Space0 and Paper_Space2 existst but Paper_Space1 is missing.
Inside my code I want to clone one of these layouts. Inside your add method you creat a new Paper_Space and add the indexnumber by counting the List -2. So the new Paperspace gets the name Paper_Space2 (Which already exists!).
(See in your layouts class, layout.Add method, Line 132).
So in all these methods which creats, adds or remove Layouts (Paperspaces) you have to check if the Paperspace name is already given.
Yours sincerely
Timm

At the moment I have this solution:
`        //original Code
//string spaceName = this.list.Count == 1 ? Block.DefaultPaperSpaceName :  string.Concat(Block.DefaultPaperSpaceName, this.list.Count - 2);
//new Code by Timm Lemke (intermetric GmbH)
string spaceName = GetPaperSpaceName();`

`private string GetPaperSpaceName() {
string newPaperSpaceName= Block.DefaultPaperSpaceName;
List paperSpaces = new List();
		foreach (Layout layout in this) {
			paperSpaces.Add(layout.AssociatedBlock.Name);
		}

		int i= 0;
		while (paperSpaces.Contains(newPaperSpaceName)) {
			i++;
			rueck = string.Concat(Block.DefaultPaperSpaceName, i);
		}

		return newPaperSpaceName;
	}`

At the moment I have this solution:
//original Code
//string spaceName = this.list.Count == 1 ? Block.DefaultPaperSpaceName : string.Concat(Block.DefaultPaperSpaceName, this.list.Count - 2);

//new Code
string spaceName = GetNewPaperSpaceName();

private string GetNewPaperSpaceName() {
    string newPaperSpaceName(= Block.DefaultPaperSpaceName;
    List<string> paperSpaces = new List<string>();

    foreach (Layout layout in this) {
        paperSpaces.Add(layout.AssociatedBlock.Name);
    }
    int i= 0;
    while (paperSpaces.Contains(newPaperSpaceName)) {
        i++;
        newPaperSpaceName= string.Concat(Block.DefaultPaperSpaceName, i);
    }
    return newPaperSpaceName;
}

Yours sincerely
Timm

This should work in your end with the latest commit October,9,2019
DxfDocument doc = new DxfDocument();
doc.Layouts.Add(new Layout("Layout1"));
doc.Layouts.Add(new Layout("Layout2"));
doc.Layouts.Remove("Layout1"); // you can replace the string with any other layout name
doc.Save("test.dxf");

The origin of the problem looks like is not within the layout removing process but with the layout associated block naming. AutoCad does not seems to care if a *Paper_Space0, *Paper_Space1,... is missing; but the *Paper_Space block must always be present (legacy code, I guess, long time ago there use to be only one paper space). If you delete a Layout associated with one of those 0, 1,... blocks it just delete it; but if the Layout associated with the *Paper_Space block is deleted, one must become the *Paper_Space, an existing one is renamed or a new one is created if that is the only one.
To accommodate to this, I am adding a new Layout if there are none when the file is saved, or just renaming the existing ones to strictly following the naming convention *Paper_Space, *Paper_Space0, *Paper_Space1,... But when adding a new layout to the list, the number of layouts is used to create the block name for the layout, and this might be the origin of your problem, if, for example, like in your case *Paper_Space1 block name is missing the new generated layout name will interfere with the existing one. You will end up with two layouts pointing to the same block and this is wrong, it might end up generating the issue you are experiencing. This is easily solved renaming the layouts during the DXF loading process, I will add a fix for that.

thank you for the quick reply.
Timm


Using Vite's programmatic API to inject HTML modifications

My situation is that I'm creating React widgets that I'm injecting on an external site (Shopify in this instance).  In order to develop these things I need to run the widgets locally and tunnel them on a Shopify hosted storefront so I can easily interact with things like their AJAX cart API etc.
SO... I went to the Shopify theme, added a root entry div, and added a script tag tunneled to my local main.tsx.  Basically what you see in index.html out of the box for Vite, but using an ngrok tunnel.
I was running into the "vite-plugin-react can't detect preamble. Something is wrong." error and saw this other thread.  Below code works, but would like to better understand what's going on here and if there's a better way using Vite configuration options so I don't need to add the first script tag (guy in that thread was serving HTML via PHP, & I'm not).
Thank you so much

COMMENT FROM ORIGINAL THREAD:
Ah, so you are serving the HTML over your PHP server. Unfortunately because of this, Vite plugins (in this case @vitejs/plugin-react-refresh) won't be able to inject its HTML modifications.
Since you are not using Node.js, you can't leverage Vite's programmatic API to inject those HTML modifications, so in this case you'll have to do it manually inject this code into your HTML:

This isn't a bug per-se, but we probably want to consider how to improve that.
Originally posted by @yyx990803 in https://github.com/vitejs/vite/issues/1984#issuecomment-778289660

Can you check this? https://github.com/vitejs/vite-plugin-react/issues/336#issuecomment-2164859744
It's possible that two


1.2

Your company plans to migrate all its network resources to Azure.
You need to start the planning process by exploring Azure.
What should you create first?
A. a subscription
B. a resource group
C. a virtual network
D. a management group

B

A*


[schema test]add integration tests for go schema

Signed-off-by: xiaolong.ran<EMAIL_ADDRESS>Motivation
add integration tests for go schema， testing scenarios:

publish from Java and consume from Golang
publish from Golang and consume from Java

@sijie @merlimat PTAL

thanks, @sijie will fix it

@wolfstudy is it better to move it to 2.7.0? or if you have time you can fix sijie's comments and onboard this PR in 2.6.0

@wolfstudy Do you want to continue to work on this PR before 2.7.0 release?

@codelipenghui CGo client is currently out of maintenance, so I think we can close this change.


Features/limit repeated queries

WIP throttle for disincentivizing large cabals by querying their hotkeys less often. Taken together with #92 this will query them less often and cause them to achieve lower scores.
This is an important step to increase the throughput of the network, while reducing repeated responses.

Is this PR planned to be in the next release?

only remaining issue is determinism in the unit tests

https://wandb.ai/opentensor-dev/alpha-validators/runs/750gbtsw/overview?workspace=user-opentensor-steffen


++Support /app, -+next/router to next/navigation

Fixing issue #78

Hi @karthi-21, any movement on this?
Thanks!

Sry for the late reply, YES this change is specific to app directory. This might now work for pages directory.
https://nextjs.org/docs/app/building-your-application/routing/linking-and-navigating#userouter-hook
https://stackoverflow.com/questions/76285831/whats-the-difference-between-next-router-and-next-navigation


Many hyperlinks are no longer valid, responding with 404. Please update.

Many hyperlinks are no longer valid, responding with 404. Please update.
For example:
In main README.md:

👉 See reusable dataset splits for CTR prediction.

In FuxiCTR/data/README.md:

Criteo: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/Criteo
Avazu: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/Avazu
Taobao: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/Taobao
KKBox: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/KKBox
MicroVideo1.7M: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/MicroVideo1.7M
Frappe: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/Frappe
Movielens: https://github.com/openbenchmark/BARS/blob/master/ctr_prediction/datasets/Movielens

Thanks for your issue. It has been fixed now.


langchain-core和langchain-community版本问题

pip install -r requirements.txt安装时候会有如下报错：
ERROR: Cannot install -r requirements.txt (line 2) and langchain-core==0.2.2 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested langchain-core==0.2.2
langchain-community 0.0.29 depends on langchain-core<0.2.0 and >=0.1.33
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

@jousonren  你好，感想发现问题。
这个问题是由于我 requirements.txt  依赖列表
问题是否已经通过以下方式解决？
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

我更新了依赖列表 以解决问题
https://github.com/bytesc/data-copilot/commit/379af3090cd1ba3ddb88ebacfe63a4e903e381d2


Remove Api.ai integration from readme-slack.md

in the PR #443 We created a file called readme-middlewares.md that is dedicated to talking about the various middlewares.
For this reason, i removed Api.ai documentation from readme-slack.md and added it to the new readme file didicated to middlewares.

@ouadie-lahdioui
I approuve. Good initiative

Did these changes independently in my docs branch I just pushed, but appreciate the effort!


Bug: Map tile image gets saved with the wrong plus code

Hello,
I would like to report a bug. Here are the reproduction steps:

Enter the OverheadView scene which fetches map tile images from the PraxisMapper server.
Quickly move around the map with arrow keys causing multiple simultaneous HTTP calls for map tiles.
Eventually the same map tile image might get saved for two different plus codes. You see this on the map as two duplicate images next to each other.

Map in the debugger with two duplicate map tiles on the middle row:

Saved images on the device:

Once this has occurred and an image has been saved with the wrong plus code, there is no way to remedy the situation within the client. The only thing you can do is remove the images from the device so that they get fetched again.
It seems to be a race condition issue. One way to alleviate the issue would be to pass the plusCode with which the HTTP request was made to the tile_called function in PraxisMapper/Controls/MapTile.gd, and only save the image and draw the texture if the plusCode matches currentTile. Like so:
func tile_called(result, plusCode): # Added parameter plusCode
	print("tile called received body")
	request.response_data.disconnect(tile_called)

	if plusCode == currentTile: # Added check
		var image = Image.new()
		if (image.load_png_from_buffer(result) != OK):
			return "error2"

		var saved = image.save_png("user://MapTiles/" + plusCode + "-" + styleSet + ".png")
		if (saved != OK):
			print("Not saved: " + str(saved))

		var texture = ImageTexture.create_from_image(image)
		texRect.texture = texture

func LoadTile(plusCode):
    ...
    # New parameter passed like so:
    request.response_data.connect(tile_called.bind(plusCode))
    ...

However, this solution is not perfect as when the bug would get reproduced the map tile is instead initially left empty. It will get fetched again and then saved with the correct plus code, but only after moving the screen a bit. I am not very familiar with the codebase or GDScript yet so perhaps there is a better solution.
P.S. Thank you for the project, hoping to make something out of it!

Thanks for the bug report!
I think the core cause for this was multiple requests to draw stuff could go off, and if they overlapped the requests would wait for the same frame and then grab the image. I have a fix uploaded for ScrollingCenteredMap that should fix the issue, though it will also stop redrawing the map while it draws.  Get the latest code and see if that fixes things for you.

I cloned this repo again and unfortunately the bug still seems to reproduce. Middle tile has been duplicated in the image, and the two tiles below it are in the wrong place. Wrong placement instead of duplication also happened before the recent changed.

The gaps between the tiles are due to the newly cloned repo assuming this resolution (PraxisCore.gd):
#system config values. These are for Cell12 resolution images from detailed data.
var mapTileWidth = 320
var mapTileHeight = 500

Previously I had changed mapTileHeight to 400. This is a separate issue, but how would you go about changing the OverheadView scene and/or PraxisMapper server to accommodate mapTileHeight 500?

Oh, I misunderstood. I thought you were drawing the tiles on the device, not the server. I have been spending weeks on fixing that for client-side drawing. Your code is a good step towards fixing it, and it should work fine at walking speed on a mobile device. I'm going to include it while I work through this and figure out how to resolve this completely.
OverheadView and MapTile.gd were my first attempt at showing map tiles on the client, and that's painfully clear here. I should have done something to handle the case where a MapTile made a second request before the first one completed.
If you're using the server to draw tiles, it's easiest to update PraxisCore.mapTileHeight to 400 to fix the gaps in the OverheadView layout. The 500 value is for drawing high-resolution tiles on the client itself.  I'll make a note to do something about that discrepancy, even if its just "document the differences and when/why to use which".

Check the latest code out now. In addition to your change, MapTile now cancels any existing request when it needs to be updated, and if it still somehow gets the wrong PlusCode, it asks again for the new one.
This should resolve out your issues both with "Wrong maptile is saved" and "blank ones dont update until you move again". Please check it out and let me know.

Great work! The issue is resolved, and the would-be blank ones indeed update without having to move.


Feature Request

Can you add google drive/td support?
I want to extract audio/subtitle from a video available in my google drive/td, so instead of sending video file to bot we will send google drive/td link and it will copy it to heroku and extract the audio/subtitle and send that to us.
I hope u got the idea.

If you got it plz send me

If you got it plz send me

no bro no any response from OP


omniauth version has vuneralbilities

Github is reporting a venerability in versions of omniauth before 1.9.0, this gem appears to be tied to v1.3. Can this dependancy be bumped?
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9284

@NeilH-CCS haven't heard about it despite this repo has enabled security alerts. Can you share a link to this vulnerability description?

@NeilH-CCS haven't heard about it despite this repo has enabled security alerts. Can you share a link to this vulnerability description?

I have added it my original post.

@NeilH-CCS could you test this branch for regressions?
gem 'omniauth_openid_connect', git: 'https://github.com/m0n9oose/omniauth_openid_connect.git', branch: 'update_omniauth_dependency'

This branch seems to be fixed and works with our integration.
Please go ahead and release if you can.


RFC: switch to using the full oraclelinux:8 base image for the Oracle Linux Developer images

This makes the developer images far more developer-friendly by including such useful tools as a module-aware dnf and more. Yes, the images jump in size, but then developer images are inherently larger because of their purpose.
Of particular importance is for folks to test the builds at https://github.com/Djelibeybi?tab=packages to make sure current functionality is unaffected, including any downstream CI/CD tooling that assumes the existence of microdnf.

I've hit an issue with compiling native gem extensions in the 2.7 image, but it's consistent with the current (official) image, so I'll look at this once we've fattened the images.

That would be great.

Can you clarify how you would like to transition to oraclelinux:8 beyond this RFC?
Is the plan to re-base all dev images on the compat image and as second step have the code owners move from microdnf to dnf and drop the dependency on compat?
For the migrated images (like your golan/latest)  shouldn't we drop the module file?

No, we have to maintain microdnf and the module files until at least the next Oracle Linux update is released, to give downstream consumers of the images time to update their tooling. My plan is actually to provide two updates cycles for this.
When the next update is released, my plan is to replace microdnf with a script that outputs a notice saying the image has changed and to switch to dnf before the next update is released, at which point microdnf will be removed from this image. Then the script will pause for 30 seconds. That pause should be sufficient for folks to notice their CI jobs are taking longer and to check the logs.
At the next update, we can finalise the switch by removing the module files and switching directly to the oraclelinux:8 base image.

Once #2044 is merged and the oraclelinux8-compat:8-slim image is built, I will update this PR to use that image from Oracle's GHCR.

@AmedeeBulle I would deeply appreciate it if you could fix the workflow breakage I caused. :)

@AmedeeBulle @mark-au @totalamateurhour can I please get another review/approval from one of you? I'd like to merge this sooner rather than later.

Thanks @cjbj, I've pushed changes to the main README.md with a deprecation notice for microdnf and I've updated all the applicable copyright notices. I'm going to leave the explicit installation of oracle-instantclient-basic because there's no change in the result and it makes it more obvious that it's part of the image when only reviewing the source.

@AmedeeBulle @totalamateurhour @mark-au it would be great to get another review, but I will be merging this change in regardless by the end of the week, because we need to stop using 8-slim.


Biological variants of genes not explicitly referred to the human taxon

Hello once again. I was trying to get all biological variants (P3433) of human genes in wikidata when I realized that some of them (17 right now) are referred to genes that do not have the statement:
gene found in taxon (P3433) Homo sapiens (Q15978631)
Here is a query to see such a behavior in action. From a theoretical point of view, I expected all human genes explicitly referred to their taxon. I'm quite new to wikidata, so I don't know if that is perfectly normal or not. Isn't there a kind of ShEx to formalize data constraints?

Hi floatingpurr,
There as a bug in handling of genes that encode more than one protein. I've implemented it and these should get corrected by the bot by tomorrow.

Hi stuppie,
thank you! Please note that the taxon property seems still missing in Q14874282 and in Q18033471

The bot is still running, should be done in 3 hrs.

There are just few genes left without the P3433. I don't know if it's ok or if there is a piece of bug still there.

@floatingpurr Check out this page here for a log of the latest bot run. This is a work in progress, but they should all be showing up here eventually.
You can see 666 out of 58,753 items were skipped due to some failure/conflict. The two left have some ID conflicts and need to be manually fixed..

Looks like someone fixed the human examples -- thanks!  Closing...


[WFCORE-5640][WFCORE-5641] XSD and XML cleanup

This PR includes:

[WFCORE-5640] Relax constraint on host-releaseType's id attribute
Instead of making it an enum that must be updated with every WildFly
Core release, let's use a string type.
JIRA: https://issues.redhat.com/browse/WFCORE-5640

[WFCORE-5641] Clean up DomainXml parser classes
Remove all WildFly core Xml classes that were identical to their previous
versions.
This only leaves classes that introduced actual changes to the
XML parsing
1 commit per XML class
JIRA: https://issues.redhat.com/browse/WFCORE-5641

@yersan thanks for the review


Title of node not visible in node component display

The title of the node is not visible because we are displaying it as white text on a white background in the default theme

Closing via #38


Auto-refresh after whitelisting

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
After adding a URL to the white list via the extension, I need to manually refresh the page. This is cumbersome when links use multiple intermediary links to get to the final URL (e.g. Slickdeals.net).
Describe the solution you'd like
A clear and concise description of what you want to happen.
After adding a URL to the whitelist via the chrome extension, it would be nice for the page to automatically reload.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Manually refreshing the page.
Additional context
Add any other context or screenshots about the feature request here.
Thanks for the extension! It's extremely useful!

@christasich Do you really mean "after whitelisting"? I think you mean the on/off switch?
Lets say you are on one of those redirecting domains where you go to 2-4 domains at once, and all of them are blocked.
You would then whitelist the first domain -> extension reloads the page -> you get to the second domain that is blocked.
This seems a little bit weired to me.
I would understand the following as more usefull, because you typically don't want to whitelist all of these redirecting domains.
My Solution:
You are on a blocked domain -> Press the pihole offline switch -> extension reloades and you get pass all domains as fast as possible.
Is this maybe the thing you want?

@badsgahhl That would also be useful. I did mean whitelisting though. My personal issue comes from browsing www.slickdeals.net. I use this site to monitor deals. The links they use are often passed through multiple hops (slickdeals -> site 1 - > site 2 -> site 3 -> final url). I've looked into these domains and I feel comfortable whitelisting them all. I think the auto-refresh option would be useful for both toggling the switch on/off and when whitelisting.

Ah ok, cool idea.
I will play around with it a bit and see how it harmonizes well together.
Maybe it will become an option that you have to activate in the settings, and you can deactivate it if you don't want to have it.

Yeah. I think opting into the setting is a reasonable way of handling it. It seems safer to have it off by default. Thanks for being responsive to the idea!

There will be now the option to "Reload current tab after Whitelisting" and "Reload current tab after Disabling".
Blacklisting makes problems with caching and makes not so much sense.
Enabling and reloading is the same.


ci(buildkite): revert to node-14-buster

Revert of https://github.com/prisma/prisma/pull/16503

Done in https://github.com/prisma/prisma/pull/16519


[Q] variants start / end fuzzy range.

Hello,
In the draft4 variants Position.start / end are defined as an array ("examples": ["[1000], [1000,1100]"]):
https://github.com/ga4gh-beacon/beacon-v2-Models/blob/main/BEACON-V2-draft4-Model/genomicVariations/defaultSchema.json
I understand the logic for the request parameters (to provide "fuzzy" search), but for the Beacon what is the meaning? Is this for structural variants?
I see the current Beacon 2 draft implementation and do not see it is reflected in the database ("variant_table" start / end int4).
https://github.com/EGA-archive/beacon-2.x/
Cheers,
Dmitry

I'm confused.
Aren't we using the brtacketed queries in the example queries document?
Aren't we talking about that here?

No. One thing is a fuzzy query (requestParameters ?) and another range position in the found beacon.
I do not object, but the meaning may be different - for the query, we search for beacons those start position is within a range.
For the concrete beacon "fuzzy" position should mean different thing.
Is this related to the:
##INFO=<ID=CIPOS,Number=2,Type=Integer,Description="Confidence interval around POS for imprecise variants">
##INFO=<ID=CIEND,Number=2,Type=Integer,Description="Confidence interval around END for imprecise variants">

?
I took a look at the CRG implementation and found that it is still a number in the postgres database.
Cheers,
Dmitry