Fix .deb install on ubuntu 20.04

Fix https://github.com/atom/atom/issues/20356

With Ubuntu 20.04 release schedule in a month, wouldn't it be appropriate to merge this for a next release, so that all Ubuntu users have a sane upgrade path?

Exactly one month until Focal Fossa final release. See the release schedule for details:
https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule
As it stands, atom cannot be installed on Ubuntu 20.04 (Focal Fossa). This PR would be an appropriate and easy solution, IMO.

Could you push a dummy commit? CI build hasn't triggered apparently.

CC-ing some active maintainers of this repo: @darangi @lkashef @Aerijo.
There is a packaging issue for Atom against the upcoming Ubuntu 20.04 LTS release. That will come out in a just over three weeks. (The issue prevents installing Atom in Ubuntu 20.04.)
Please consider this small (just a few bytes of diff) Pull Request to fix the situation. Thank you.

Thanks @zorn-v for your contribution 🙇♂
The CI failed test seems to be unrelated and flakey so I will just give it a re-run and merge this in 👍.
Thanks @aminya and @DeeDeeG for the support and the heads up.

Another heads-up: In Ubuntu 20.04, it will soon be possible to install a package "python-is-python3" which satisfies the python deb dependency with Python 3.x. In previous Ubuntu releases, running versionless python generally implied running Python 2.x
So, in theory (that is, if the python code Atom uses isn't Python 3 compatible), this could break that part of Atom for users with python-is-python3 installed.
For what it's worth: according to this comment, Python is only used for node-gyp. A long-term solution to this Python 2.x/3.x ambiguity would be to confirm that node-gyp is compatible with Python 3... Or update the way Atom is packaged so the python (and/or python2/python3) dependency/ies can be dropped entirely from Atom's deb package.
I am not an expert with regard to python, node, etc. or how Atom is packaged for debian/Ubuntu. Just thought I should mention.
In summary: For the time-being, this PR solves the problem for the vast majority of users. Those who deliberately install python-is-python3 might or might not break node-gyp as bundled with Atom. (I don't know/understand this for sure, just interpreting the comment I linked above.) I believe this PR is a reasonable step forward, and much better than doing nothing. (The difference between most users being able to use Atom on Ubuntu 20.04, vs no-one on Ubuntu 20.04 without hacky workarounds).

So, eventually, it may make sense to switch the dependency from python to python3, and not use an "either-is-allowed" approach as in this PR with python | python2.
For now, removing the generic python dependency would drop support for debian Jessie.
(Jessie has versionless python but no python2 package (python2 in Jessie's package archives returns a 404 not found error...), and Jessie has python3 that is too old (3.4; node-gyp requires Python 2.7 for Python 2, or 3.5 and newer for Python 3).
(I suppose that if node-gyp can be un-bundled from this deb package, then perhaps the issue can be handled by dropping this package's dependency on any sort of python or python2 or pythonr3.)

which satisfies the python deb dependency with Python 3.x

No, it is just symlink. There is no "Provides" section in that package, only "Breaks" and "Replaces".
You can check with apt show python-is-python3

Description: symlinks /usr/bin/python to python3
In Ubuntu, all python packages use explicit python3 or python2
interpreter and do not use unversioned /usr/bin/python at all. Some
third-party code is now predominantly python3 based, yet may use
/usr/bin/python.
.
This is a convenience package which ships a symlink to point
the /usr/bin/python interpreter at the current default python3. It may
improve compatibility with other modern systems, whilst breaking some
obsolete or 3rd-party software.

But anyway removing python2 from deps is good.

@zorn-v python-is-python3 will provide/satisfy the python package soon: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2020-March/018615.html
In my opinion, the python dependency should stay somewhere in the "Depends:" until Debian Jessie is end-of-life, which will be in June.
There is a way to do this with no python2 dependency. I suppose it could be python | python3 (>= 3.5.0) | python2 to be most flexible. Or just python | python3 (>= 3.5.0) in order to prefer Python 3.x, and begin to phase out support for Python 2.x.

I think upgrading from Python 2 to Python 3 for Atom's dependencies should be decoupled from fixing the current Python 2 dpkg dependency administration.
So I'd propose to merge in as soon as possible the change to the python | python2 dependency. That still uses Python 2.
And make a new PR that does all necessary testing whether Atom works with Python 3. If that all works fine, you could have until June 2020:
python | python3 (>= 3.5.0) to keep support Debian Jessie
and after June 2020 you could change it to:
python3 (>= 3.5.0) (at that time all supported Ubuntu and Debian releases have Python3.5+)

@mfonville Yes, 100%. I just thought mentioning it here would ensure people who already dealt with this PR (who have the background and context to understand the work left to be done) are aware of the things on the TODO list for, say, a couple months from now.
IMO this can/probably should be just merged as-is and any follow-up work is icing on the cake. (I defer judgment on the actual decision to maintainers of this repo, as always.)
I volunteer to open said follow-up PR if it helps the maintainers here feel comfortable and ready to merge this. Thanks again.

By the way, I migrated to vscode :smile:
Tired from such relation to simple things.

Thanks for merging!
Re: Migrating to python3 I think this is good as-is (i.e. should work with all currently active/supported Debian/Ubuntu distros), and IMO migrating the dependency to pure Python 3 would be premature until at least when Debian Jessie is not supported anymore (June this year).
Also: In hindsight, the python-is-python3 thing looks like it would not be a problem.
Longer explanation: As far as I understand it, we only need Python for node-gyp (according to that one comment?? I want to do more research to confirm that.) and I now know that node-gyp supports both Python 2 and Python 3.)
So it doesn't matter if python is ambiguous because both meanings would work.
I'm interested in doing the research to confirm all the ducks are in a row going forward, but I admit I'm learning some of this info as I go. I would plan to post any updates in the follow-up issue I opened: #20585

@lkashef
With the release of Ubuntu 20.04 within 10 days from now, and the cycle still not through for even a beta release.
I'd propose this trivial patch for inclusion in a 1.45.1 release if that is possible. Otherwise users get during the running of do-release-upgrade an automatic removal of atom.

atom users must suffer :smile:
No other explain for such things.

No harm in backporting this to atom 1.45.x IMO, if possible.
That said, there's a chance it will be a somewhat moot point. atom depending on simply python might pull in python-is-python2.
I find this difficult to test for now, waiting on Ubuntu package maintainers update python-is-python2 to have Provides: python... And they are putting that off until the last minute to track down packages that are broken by versionless python being deprecated.
So maybe there is no action needed, maybe not. I will try to update here as early as said update to pythin-is-python2 happens.
(Backporting this PR is still a safe/no-downsides and reasonable step though, IMO.)

help my acc

Thanks @DeeDeeG, highly appreciate you digging deep into this.

@lkashef
With the release of Ubuntu 20.04 within 10 days from now, and the cycle still not through for even a beta release.
I'd propose this trivial patch for inclusion in a 1.45.1 release if that is possible. Otherwise users get during the running of do-release-upgrade an automatic removal of atom.

@mfonville Thanks for the heads up, although as per @DeeDeeG's comment, we are not sure if the release will break Atom on Ubuntu 20.04, did they release any updates on the matter?
This kinda of information would be helpful to make a decision.
On a different note, Atom Nightly should work on Ubuntu 20.04 until we decide on the patch.

@lkashef Yesterday Ubuntu published the python-is-python2 package ( https://packages.ubuntu.com/focal/python-is-python2)
so luckily, as mentioned by @DeeDeeG Atom is install-able again when upgrading to 20.04.
One thing to check for this patch (@DeeDeeG maybe you can check?) if node-gyp is correctly using the python2 env and not python?

Thanks @mfonville!
That's great news and would definitely buy us some time to make sure we resolve this across different versions.
Feel free to mention me, in case the situation escalated or new information came up.

Tested this, you can just do apt install atom now, even on a fresh install of Ubuntu 20.04.
The "Provides: python" bit means this PR wasn't strictly necessary, with hindsight.
My apologies. On the other hand, it just works™ now, so that's good news.

Ongoing effort to switch to Python 3 entirely should still be looked at, because the next stable Debian (whenever they decide to release Debian Bullseye) and Ubuntu 20.10 plan on not shipping Python 2.
I posted an issue to track that whole thing here: https://github.com/atom/atom/issues/20585
As I found out, the first order of business would be this PR over at the apm repo: https://github.com/atom/apm/pull/875 (apm bundles a version of npm, which depends on node-gyp. Need a newer node-gyp to support Python 3. Should be back-compatible with Python 2 as well, so could ship on today's distros no problem.)
That PR sorts out the main Python usage in atom. There is a little more to do to get CI passing over there, and probably some follow-up work at this repo, but that PR would be the core thing IMO. I am not familiar with the tests over there, so if anyone knows what to do for that PR to pass CI I think that would be very helpful!)

@mfonville the version of node-gyp used in atom at the moment specifically uses python if I recall correctly. But if you install atom in Focal you get the python-is-python2 package, which depends on python2 and symlinks /user/bin/python --> /usr/bin/python2. So node-gyp is none the wiser about it. It should "just work." (People seem to be reading these issues/PR threads a lot so I wanted to lay that all out.)
As mentioned in the comment just above, newer node-gyp that supports Python 3 would be gotten through this PR: https://github.com/atom/apm/pull/875

@lkashef I just realized this PR should probably be reverted.
If one does sudo apt install python2 and sudo apt install atom-nightly... they can end up with python2 installed, but no symlink from python to python2.
Then apm install [package] fails because it can't find the executable python.
So, basically the user needs to have python symlinked to python2... The dependencies from before this PR would now work better than the current python | python2. If we just depend on versionless python, apt pulls in python-is-python2, problem solved.)
Once again, apologies for getting this wrong.
(How things are in Ubuntu development branch isn't necessarily how it will be in stable release. I got confused about what the eventual situation would be in final release.)

One problem (then become others) that atom can not make "patch release"

And, yeah. Problem was known sins february

@zorn-v thank you for being involved in making a fix. But the criticisms of atom here are not helpful or called for. The decision whether to release an update of a piece of software is the maintainers' decision alone. It turns out in this case, this did need some time to make sure it was the right thing to do. With adequate research and testing, I found out this PR actually wasn't needed all along. (I regret repeatedly saying it was needed, when In hindsight I didn't understand the situation enough.)
If this PR gets reverted before the next stable release, there will be no need for a patch update anyhow.
Please stop criticising the atom maintainers and their actions, or insisting they should make a patch release.

The sources of my confusion here was down to a few things:

I didn't understand that python-is-python2 would eventually "Provide" versionless python, and that this had been disabled only temporarily. That situation was not very clear to me without more digging and reaching out to folks from Ubuntu.
I didn't understand the behavior of apt clearly enough to see that by having "Provides: python", python-is-python2 would be auto-installed when trying to install atom.
I initially hadn't identified a way to test actual python support in apm, so I was basing whether this PR "solved the problem" simply by whether it allowed you to install the atom package.

With all those things being clearer to me now, I can see this PR was unnecessary, and opens up a possibility of apm install not working anymore, so it should be reverted.

Update: Not many packages require node-gyp in order to install. (And that's the only time I believe Atom uses Python: during package installs that use node-gyp.) So the negative impact of this PR looks pretty limited.
Testing details (click to expand):
To test this, I have tried installing many packages in atom. (Via "settings -> install"). I tested this with an "unsupported" version of Python on my system (Python 3). Only a few packages failed to install due to wrong Python version:

https://atom.io/packages/language-rust-treesitter
https://atom.io/packages/tree-sitter-4dm
https://atom.io/packages/language-python-treesitter
https://atom.io/packages/language-zig-treesitter
https://atom.io/packages/language-tree-test
https://atom.io/packages/language-lux
https://atom.io/packages/language-janet
https://atom.io/packages/language-carp
https://atom.io/packages/greyatom-hydrogen
https://atom.io/packages/atom-ide-terminal
https://atom.io/packages/terminal-tab-plus
https://atom.io/packages/terminal-tab-service
https://atom.io/packages/electric-terminal
https://atom.io/packages/ls-compile
https://atom.io/packages/build-haxe
https://atom.io/packages/flatpak-builder-runner

(There are almost definitely some more packages than this that need node-gyp. But I installed what felt like hundreds of packages, and these are the only ones out of those that failed due to my system having the wrong Python version. The point being, most packages don't need node-gyp and would therefore be unaffected by this PR.)
(Other than the ones listed above, I only found tree-view, and some other packages bundled with Atom, which similarly fail to install, but these are bundled with Atom and aren't intended to be manually installed or upgraded by end-users. So I don't think they count. These can't be reinstalled or upgraded from within the Atom UI, but they can be reinstalled on the command-line with apm.)
If someone knows another package that requires to be built with node-gyp at install time, (other than packages bundled with Atom such as tree-view), please let me know.
(My setup for testing this is Ubuntu 20.04, using Atom stable 1.45.0 patched to include this PR. I also tried with Atom nightly 1.47.0, which had the same results. python is symlinked to python3 on my machine. I got equivalent results trying this briefly on Windows with Atom 1.45.0 and no Python installed whatsoever.)
[End of testing details]

So maybe Atom doesn't strictly need a Python dependency at all. Not having such a requirement would bring the Debian/Ubuntu (.deb) package for Atom in line with the Windows and Fedora (.rpm) packaging. And I haven't had time to confirm this yet, but I think the macOS packaging doesn't require Python either. (It probably relies on the fact macOS ships Python 2 out of the box, but that's almost off-topic level of detail.)
Regarding whether to revert or keep this PR, it seems like pretty low-stakes either way, IMO. But reverting it would ensure the packages I listed above (in "Testing details") can always be built and installed with Atom/apm... On Debian/Ubuntu anyhow.
(See also the snap package of Atom... which has no apparent Python requirement to install. It's equivalent to the Windows, .rpm or macOS packaging.)

Summary and recommendation from me: This PR effectively gives the option of running Atom with broken Python support, which has surprisingly low impact on using Atom. I'd suggest making Python an optional dependency, or dropping the dependency altogether... Or just reverting to before this PR, which returns to requiring working Python support to install Atom on Ubuntu. (Requiring Python support that then can't be used (Requires: python2) seems kinda silly.)
Making Python an optional dependency (or dropping the dependency altogether) is more future-proof than going back to the way it was before this PR.

@DeeDeeG
My criticisms is something like "agony", caused by "deading" of my favorite editor.
You investigations is great, but is somebody will take them into account ?

If I was deb packager of atom I assign @DeeDeeG surely for it :smile:

@DeeDeeG your research has been awesome! thanks again! I am currently working on other stuff but I will definitely, take a deep dive into the comments.


Fix notify group flakiness

This fixes an issue where the built payload would sometimes not include all the kwargs. I changed to copying the kwargs and then adding the message to it instead of iterating over all kwargs.

I doubt that this will address the flakiness. The flakiness occurs because the order in which we handle events is non-deterministic.

A result of a flaky run here where it seems the assert fails for the message target, maybe we should just be a bit more lenient on the target. Since unnamed device and None is similar
-  'target': ['unnamed device'],  (EXPECTED)
+  'target': None,  (RECEIVED)

Some more results in the flaky tests issue #3365

We should be able to successfully predict what the value is going to be.
None (no value given) and ['unnamed device'] (value given but no name) are not similar ;-)


Download kubectl on macOS

Download kubectl binary on macOS

Hi @amitkrout thank you so much for your contribution.
We probably don't want to sudo here for security reasons.
For something easy, can we just check if kubectl is available and if its not just exit with an error code.
If you really want to auto download and install. Do something like this might be better for security:
which kubectl
check if $? is 0 then
KUBECTL_EXEC (or whatever name you want) = `which kubectl`
if not 0 then
mkdir -p bin
curl
mv kubectl to bin
chmod +x bin/kubectl
KUBECTL_EXEC=realpath ./bin/kubectl

I mentioned this previously in https://github.com/open-cluster-management/multicloud-operators-subscription-release/pull/106#discussion_r526932688 but Ian and I agreed its more beneficial to check in the bulk of the e2e framework first then come back and fix this problem. Since you are working in this area of the code, could you please try to do something like what I suggested and remove the sudo security risk. Thanks.

@mikeshng Thanks for the feedback.
I have addressed your suggestion. Instead of directly using the binary, i put bin/ into PATH. PTAL

+make lint
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    90  100    90    0     0    359      0 --:--:-- --:--:-- --:--:--   360
.build-harness-bootstrap:1: *** missing separator.  Stop.
The command "bash ${TRAVIS_BUILD_DIR}/build/run-code-lint.sh" exited with 2.

lint check is failing

@amitkrout the travis build doesn't support fork PRs.
Could you please do this and reopen the PR:

clone the repo
git checkout master
git checkout -b branch_name_you_want
make your changes and git add and git commit
git push origin branch_name_you_want
recreate the PR

sorry for the trouble and thank you for the good work

@mikeshng Np, i will create separate pr. thanks


Formatting the code

Put the documentation before the function and also improving the "if"
statements

1+


[Bug] Type errors on width/height

Bug Report
Describe the bug
When testing the latest, i seem to be getting type errors for width and height

@matiasfha not quite sure why this is happening

It uses width and height as numbers.
width={600}
Should we support them as strings too?
but, what other props are you passing there?

i have it set to allow string and numbers because people stylistically have different preferences on how to pass that in
https://github.com/colbyfayock/cloudinary-util/blob/main/packages/url-loader/src/types/asset.ts#L28
i feel like its more common to see it passed in as a string

example with the other props:
<CldImage
	width="600"
	height="600"
	src="images/turtle"
	alt="turtle"
	overlays={[{
		publicId: `images/earth`,
		position: {
			x: 10,
			y: 10,
			gravity: 'north_west',
		},
		effects: [
			{
				crop: 'fill',
				gravity: 'auto',
				width: 200,
				height: 200
			}
		]
	}]}
/>

Been working on refactor the type for the props to respect
width: number | string | undefined
height: number | string | undefined
and also the rules related with layout inherited from unpic

`layout='fullWidth'  => width should not be present
other layout values width and height should be present

but for some reason TS "swallow" the types and expose width and height as strings | undefined removing  the number type
When merging ImageOptions (from cloudinary-util library) and ImageProps (from unpic) those types are wrongly merged. If you Omit width and height from both ends to define them in here the layout rules are missed.
If I rewrite the layout rules by omitting height , width and layout from ImageOptions and ImageProps
I get another weird ts Error saying that fullWidth is not a valid option.
I'll keep working on it tho

Release/Solved


chore(deps): update terraform terraform-ibm-modules/cos/ibm to v8.11.6

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.11.5 -> 8.11.6

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.11.6
Compare Source
Bug Fixes

deps: update terraform-module (#715) (6dfd1b9)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can PanGenie genotype inversions?

Hi Jana,
Previously I thought PanGenie only worked with SNPs, insertions, and deletions. However, I read about a study with your contribution (https://doi.org/10.1101/2<IP_ADDRESS>2354 , "Haplotype-resolved inversion landscape reveals hotspots of mutational recurrence associated with genomic disorders") in which it used PanGenie to genotype inversions. May I ask how the inversions should be represented in the input VCF file of PanGenie?
Thank you!
Best regards,
Honghe

Hi Honghe,
in principle, PanGenie can genotype any sequence-resolved variants in the input panel VCF. But for inversions, the method might not work very well due to the absence of unique k-mers. The preprint you are referring to has been published here: https://pubmed.ncbi.nlm.nih.gov/35525246/. We genotyped two of the inversions based on 1000 Genomes SNPs genotypes produced by PanGenie, not using PanGenie directly. Details are explained in the Star methods (Section "Identifying potential inversion carriers using PanGenie"). So that genotyping approach did not directly genotype inversions, but used rare SNPs to find potential carriers. It also only works for cases with sufficient rare SNPs.
Best,
Jana

Hi Jana,
Thank you for this detailed explanatio! That helps a lot!
Best,
Honghe
On Fri, Sep 22, 2023 at 12:50 Jana Ebler @.***> wrote:

Hi Honghe,
in principle, PanGenie can genotype any sequence-resolved variants in the
input panel VCF. But for inversions, the method might not work very well
due to the absence of unique k-mers. The preprint you are referring to has
been published here: https://pubmed.ncbi.nlm.nih.gov/35525246/. We
genotyped two of the inversions based on 1000 Genomes SNPs genotypes
produced by PanGenie, not using PanGenie directly. Details are explained in
the Star methods (Section "Identifying potential inversion carriers using
PanGenie"). So that genotyping approach did not directly genotype
inversions, but used rare SNPs to find potential carriers. It also only
works for cases with sufficient rare SNPs.
Best,
Jana
—
Reply to this email directly, view it on GitHub
https://github.com/eblerjana/pangenie/issues/50#issuecomment-1731736723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUNRB64USUAAQCFTE4TSKDX3W6XBANCNFSM6AAAAAA5BUYHYY
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix: check OS info from facts instead of inventory

https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html#ansible-fact-namespacing

Another method would be to define a default execpath in vars/main.yml and a specific one in vars/RedHat_8.yaml. (similar to #173)

Example:
$ git diff --cached
diff --git a/roles/core/conman/templates/conman.conf.j2 b/roles/core/conman/templates/conman.conf.j2
index fe54f07..6b6bc84 100644
--- a/roles/core/conman/templates/conman.conf.j2
+++ b/roles/core/conman/templates/conman.conf.j2
@@ -1,11 +1,7 @@
 #### Blue Banquise file ####
 ## {{ansible_managed}}

-{% if (equipment_profile['operating_system']['distribution'] | lower) in ['redhat', 'centos'] and equipment_profile['operating_system']['distribution_major_version'] < 8 %}
-SERVER execpath="/usr/share/conman/exec"
-{% else %}
-SERVER execpath="/usr/lib/conman/exec"
-{% endif %}
+SERVER execpath="{{ execpath }}"
 SERVER syslog="daemon"
 SERVER logdir="/var/log/conman"
 GLOBAL log="/var/log/conman/%N.log"
diff --git a/roles/core/conman/vars/RedHat_7.yml b/roles/core/conman/vars/RedHat_7.yml
new file mode 100644
index 0000000..1ecca16
--- /dev/null
+++ b/roles/core/conman/vars/RedHat_7.yml
@@ -0,0 +1 @@
+execpath: "/usr/share/conman/exec"
diff --git a/roles/core/conman/vars/main.yml b/roles/core/conman/vars/main.yml
index 193e084..9958a30 100644
--- a/roles/core/conman/vars/main.yml
+++ b/roles/core/conman/vars/main.yml
@@ -1 +1,2 @@
 role_version: 1.0.2
+execpath: "/usr/lib/conman/exec"

RedHat_7.yml being derived from os_family + distribution_major_version in the task.

What about my proposal above? (https://github.com/bluebanquise/bluebanquise/pull/172#issuecomment-612980174)

I find this logic interesting.
If I understand you well, idea is use some kind of default value if no operating system is found, so an generic pattern, and then a specific one if OS is known.
Am I right ?

Yes. Ansible first load variables from vars/mail.yml, then the role start with a first task that look to vars/$OS.yml files, which take precedence. This is implemented in #179 for review.

So go for #179  :-)

Close in favour of #179


Fix URL Previews for Twitter

Broken link: https://twitter.com/ryanshawtech/status/1474213262442958852?s=10, make the preview image take precedence over Apple thumbnail

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #android-support.

No longer applicable, twitter no longer supplies an image in metadata


Doesn't work on iOs

Bug report

Summary

The package doesn't work on iOs. The main example from Git is working perfectly on Android, but on iOS I receie this error"View config not found for name RNC Segmented Control".
Environment info

I am using Expo.
react-native info output:
# paste it here

Library version: x.x.x
Steps to reproduce

cut example code from git
copy example code in the component where I want to use the component
I am trying to open the screen that contains the segmenet-control component
is working perfectly on Android, but on iOS I see the red screen with this error message "View config not found for name RNC Segmented Control".

Describe what you expected to happen:

to see the segment-control component behaving the same on android and iOs

Reproducible sample code

I've created a Snack here. Try to open the app using an iOs phone<EMAIL_ADDRESS>

I am facing same issue, any solution

Looks like your forgot to do a pod install in the ios directory

@ivy-mihai
Have you tried running npx pod-install in your project? for iOS modules, installing its dependency via cocoapods is required.

@ivy-mihai
Have you tried running npx pod-install in your project? for iOS modules, installing its dependency via cocoapods is required.

I am using Windows. I cannot use npx pod-install in my project, but I've tried anyway. Here is the answer: CocoaPods is only supported on darwin machines.

@ivy-mihai thanks for the reply! And sorry, i missed the part about expo.
Could you tell me which expo sdk version you're using?
This package will only work on iOS for expo sdk 38 and beyond.

@ivy-mihai thanks for the reply! And sorry, i missed the part about expo.
Could you tell me which expo sdk version you're using?
This package will only work on iOS for expo sdk 38 and beyond.

Not a problem! Thank you for your answer. I use SDK 38.


Clicking on the links doesn't move the page to specific id.

Hello.
When I scroll through the page the active class is added to the links properly. But when I click on the link it doesn't seem to work.
My repo
Demo

I am facing the same issue, What is the resolution.
When I scroll manually, The link is getting highlighted. However clicking on the link doesn't do anything and no scroll happens. If I remove , the anchor tags start to work fine.

@prashantchoudhary could you pelase copy here your related code?


Add span snapshots to the v1 payload for caching purposes

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#612  👈
#611
master

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

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Mar 21, 11:03 AM EDT: @bidetofevil started a stack merge that includes this pull request via Graphite.


【Merbridge performance test  produces many errors】

Bug Description
【question】
   pilot-agent-69571   [006] d...<PHONE_NUMBER>31: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-69571   [006] d...<PHONE_NUMBER>38: bpf_trace_printk: [debug] call from sidecar container: cookie: 780438927, ip: 0xa9fcf8ac, port: 8080
     pilot-agent-91591   [030] d...<PHONE_NUMBER>35: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-91591   [030] d...<PHONE_NUMBER>43: bpf_trace_printk: [debug] call from sidecar container: cookie: 780424679, ip: 0xaffcf8ac, port: 8080
     pilot-agent-93300   [023] d...<PHONE_NUMBER>52: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-93300   [023] d...<PHONE_NUMBER>60: bpf_trace_printk: [debug] call from sidecar container: cookie: 780603512, ip: 0x88fcf8ac, port: 8080
     pilot-agent-4007    [031] d...<PHONE_NUMBER>07: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-4007    [031] d...<PHONE_NUMBER>16: bpf_trace_printk: [debug] call from sidecar container: cookie: 780349765, ip: 0x90fcf8ac, port: 8080
     pilot-agent-93217   [007] d...<PHONE_NUMBER>28: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-93217   [007] d...<PHONE_NUMBER>35: bpf_trace_printk: [debug] call from sidecar container: cookie: 780508501, ip: 0xbafcf8ac, port: 8080
     pilot-agent-3763    [017] d...<PHONE_NUMBER>15: bpf_trace_printk: [debug] get current pod ip error
     pilot-agent-3763    [017] d...<PHONE_NUMBER>24: bpf_trace_printk: [debug] call from sidecar container: cookie: 780646392, ip: 0xaafcf8ac, port: 8080
     pilot-agent-94600   [038] d...<PHONE_NUMBER>20: bpf_trace_printk: [debug] get current pod ip error
           <...>-94887   [034] d...<PHONE_NUMBER>27: bpf_trace_printk: [debug] get current pod ip error

【Kubernetes Cluster】

os
Kernel
cpu
memory

UOS
5.10.0-10.uelc20.x86_64
40
256

UOS
5.10.0-10.uelc20.x86_64
40
256

UOS
5.10.0-10.uelc20.x86_64
40
256

【Test Process】

deploy merbridge with cni  on.
use load-tool to test merbridge. note: We access backend services through ingress-gateway. see ingress-gateway. see

run test script.
there are so many error,see below logs.

Version
Kubernetes Version：v1.19.15
kubectl Version：v1.19.15
istio Version：1.11.5
net plugin：   calico/kube-controllers:v3.20.1
Kernel Version:             5.10.0-10.uelc20.x86_64
OS Image:                   UnionTech OS Server 20
Operating System:           linux
Architecture:               amd64
Container Runtime Version:  docker://20.10.8
Kubelet Version:            v1.19.15
Kube-Proxy Version:         v1.19.15

I will try to reproduce the problem as soon as possible and give you feedback later.

I will try to reproduce the problem as soon as possible and give you feedback later.

how is it？

ohh, I'm very sorry for forgetting to reply. I tested this specifically a few days ago, and your problem did not reproduce in my environment. Can this be reproduced directly in your environment?

ohh, I'm very sorry for forgetting to reply. I tested this specifically a few days ago, and your problem did not reproduce in my environment. Can this be reproduced directly in your environment?

ok  i tested it again.

Hi @tanjunchen , in the latest version, we have optimized the performance, can you test it again?

@kebe7jun  hello I test it again，I have the same question. When the concurrency is high, merbridge will generate an error.
time="2023-04-20T10:15:35Z" level=error msg="init tc prog filed: field Ingress: program mb_tc_ingress: load program: operation not permitted (MEMLOCK may be too low, consider rlimit.RemoveMemlock)" func="ebpfs.GetTCIngressProg()" file="prog.go:88"
time="2023-04-20T10:15:35Z" level=error msg="attach tc for eth0 of /host/proc/52817/ns/net error: can not get ingress prog" func="cni-server.(*server).checkAndRepairPodPrograms.func1()" file="cni-plugin.go:274"
time="2023-04-20T10:15:35Z" level=error msg="Failed to check existing pods: can not get ingress prog" func="cni-server.(*server).Start()" file="server.go:142"
time="2023-04-20T10:20:00Z" level=error msg="init tc prog filed: field Ingress: program mb_tc_ingress: load program: operation not permitted (MEMLOCK may be too low, consider rlimit.RemoveMemlock)" func="ebpfs.GetTCIngressProg()" file="prog.go:88"
time="2023-04-20T10:20:00Z" level=error msg="CmdAdd failed for /var/run/netns/cni-2245ab6d-38b4-05df-b8f4-2fe378965ab0: can not get ingress prog" func="cni-server.(*server).CmdAdd()" file="cni-plugin.go:107"
time="2023-04-20T10:20:00Z" level=error msg="merbridge-cni cmdAdd error: can not get ingress prog" func="cni-server.(*server).CmdAdd.func1()" file="cni-plugin.go:75"
time="2023-04-20T10:30:00Z" level=error msg="init tc prog filed: field Ingress: program mb_tc_ingress: load program: operation not permitted (MEMLOCK may be too low, consider rlimit.RemoveMemlock)" func="ebpfs.GetTCIngressProg()" file="prog.go:88"
time="2023-04-20T10:30:00Z" level=error msg="CmdAdd failed for /var/run/netns/cni-4e98c1bf-f7a1-7e75-371d-50288b8bedac: can not get ingress prog" func="cni-server.(*server).CmdAdd()" file="cni-plugin.go:107"

This should be the result of not executing RemoveMemLock in the code.


[Hacker Rank] Interview Preparation Kit: Dictionaries and Hashmaps: H…

…ash Tables: Ransom Note. Coverage increased.

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

Project coverage is 100.00%. Comparing base (ad5d757) to head (e7fca54).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #82   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        18
  Lines          312       310    -2
  Branches        43        41    -2
=========================================
- Hits           312       310    -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add a config file where custom command and aliases can be saved

The idea I had in mind was that this file would be a INI file (Crystal has support for that format in the standard library) since it is just about the simplest format that can express what we want to express.
We'll want to support custom commands and aliases. A custom command could include multiple commands within it using the logical operators to decide which ones get called. An alias would just be a placeholder for a single command or even just a part of a command (it could maybe accept multiple flags after the alias).
There will need to be additional flags to handle this config file.
   # --check-config : Validate the config file commands
   # --config-path  : Path to the config file
   # --reset-config : Reset the config file to its default state

The key will be to provide a set of good defaults and then let people tweak them over time.
I also think it'd be useful for there to be internal commands that allow you to change the config file while the REPL is running.
The syntax for internal commands, custom commands and aliases is up in the air. Here are my initial thoughts.

Aliases

Behave like normal commands but provide a hint expansion in the REPL when typed.
Ex. gaa would add a trailing git add --all hint in the REPL but would otherwise behave like a normal command.

Internal Command

Requires a separate prefix (my first guess is that a dot would be good).
Ex. .alias gaa git add --all

Custom Command

Requires a separate prefix (my first guess is that a colon would be good).
Ex. :home would be equivalent to git switch MAIN

It might also be nice to provide some constants that can be used in custom commands, aliases and just generally when using the REPL. I'm not sure if we need general variables for most use cases. Some examples would be CURRENT_BRANCH, PREVIOUS BRANCH, etc. We'll see how necessary those really are though.
All of this work will be built on the changes to allow for logical operators that are being done right now in #7.

I ended up only going with the custom command option of the three mentioned above but I called it alias since the other naming options weren't taken. It might be nice to add internal commands at some point but the distinction between aliases and custom commands doesn't seem that useful to me right now so I'm planning on just avoiding it.
The trickiest thing here with aliases is providing good error messages when users combine aliases with other arguments. Alias expansion means that user errors become trickier since we want to communicate that an alias got expanded and then was invalid after expansion or that it didn't get expanded because it is not in the first position of a statement.


Link on the help page is broken

This link is broken:
http://geojson.io/#id=github:tmcw/dc-wifi-social/blob/master/bars.geojson&map=14/38.9140/-77.0302

My pull request #461 fixes this same link in API.md -- but does not directly address this issue (ie. #434).

Resolved with #461


contributions: update file extension validation - only accept .json

some policy definitions have been contributed as .jsonc ref

@JulianHayward Hi, we have presented a PR for this. Should be accepted in a couple of days. Thank you.
https://github.com/Azure/Community-Policy/pull/452


Generic driver incorrectly uses Fedora provisioning for Fedora CoreOS

When provisioning a machine using the generic SSH driver, Fedora CoreOS is wrongly identified as Fedora. Machine therefore uses the RedHat provisioner which tries to install packages such as curl using yum - which will not work since Fedora CoreOS lacks yum. Furthermore, Fedora CoreOS comes  pre-installed with Docker, meaning that that Docker and the Systemd service will already be configured.

I'm willing to try to solve this, given some guidance. The plan would be to properly identify Fedora CoreOS and then use a provisioning separate from the RedHat provisioner in order to adapt the provisioning more accurately to fit the needs of Fedora CoreOS.

Solved in https://github.com/docker/machine/issues/4807.
Available in https://github.com/AlexGustafsson/machine.
Pre-built binaries available here: https://github.com/AlexGustafsson/machine/releases/tag/v0.16.3.

It might be worth a try to submit that change to the GitLab fork of docker-machine: https://gitlab.com/gitlab-org/ci-cd/docker-machine
It might be that they are willing to integrate this change into their fork of docker-machine...

@tobiashuste : note that gitlab only accepts "critical bug fixes affecting running costs"
https://gitlab.com/gitlab-org/ci-cd/docker-machine/-/blob/master/CONTRIBUTING.md
The libmachine fork at machine-drivers is also only aggregating bug fixes, not features.
https://github.com/machine-drivers/machine

@AlexGustafsson : you will probably have to use something other than docker-machine, to provision your Fedora CoreOS hosts
I was a little surprised that it is still running docker actually, certaintly thought that it would have moved to podman/cri-o by now...

Yeah, I think this article sums it up pretty well: https://merlijn.sebrechts.be/blog/2020-01-docker-podman-kata-cri-o/. The Docker daemon and it’s related tooling are on life support.
Fedora CoreOS currently features podman (default) or docker if I remember correctly. Moving forward I think it’s time to realise that we’re at an end of an era and that it’s time to look elsewhere.

The Docker daemon and it’s related tooling are on life support.

It's more like they moved from Docker Toolbox to Docker Desktop, but sure.
Both machine and boot2docker have been deprecated, and 19.03 is the last...
However, currently the only supported option for podman is through OpenShift.
The alternative through boot2podman is deprecated, leaving only vagrant etc.


Auto-commit switches to manual commit when import is finished

System information:

Operating system (distribution) and version Windows 10
DBeaver version 6.3.0

Connection specification:

Database name and version SQLite

Describe the problem you're observing:
Auto-commit switches to manual commit when import is finished.
Steps to reproduce, if exist:
Precondition: auto-commit is selected

Go through wizard to iImport CSV file to a table in SQLite (DB Navigator, DB task panel)

Actual result: Auto-commit switches to manual commit when Start btn is pressed at the end of the Wizard.

Fixed (note: this happens only when you reuse main datasource connection).

Fixed


Query params with empty url

Try localhost/gigs?what=dsads redirects to localhost:3000/gigs without 'what' param
$stateProvider
	.state('gigs', {
  		parent: 'root.frontend',
		abstract: true,
		url: '/gigs',
		template: '<ui-view/>'
	})

	.state('gigs.list', {
		url: '?what',
		templateUrl: 'client/pages/gigs/gigs.list.view.ng.html',
		controller: 'GigsListCtrl',
		controllerAs: 'vm'
	})

Confirmed, this is a bug.  Unfortunately, this probably won't be resolved until we overhaul the urlmatcher subsystem.


You uh.. published it

Ooops? Looking forward to seeing this feature launch though!

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

ID: 12823601-7426-a768-e72f-866b150baccd
Version Independent ID: c1f993e3-a405-6860-8ab1-7b3d387b4631
Content: Hybrid AAD Join
Content Source: windows/deployment/windows-autopilot/user-driven-hybrid.md
Product: w10
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

The topic is blank, so it's not really a problem. I think the person who said "do not publish" meant that if there were content on the page, don't publish it yet.  It does look odd though, so I'll fix it this week when I publish some new content.

Any word on when Autopilot will support hybrid joined devices?

Really looking forward to this.   Eagerly waiting.

Hi any idea when this will be available?

Content has been added to the page today. It should publish in an hour. It's possible that it might not go live until 11/8.


Aurora not launching on start up

What are you experiencing an issue with?

[x] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[ ] Enhancement suggestion
[ ] Device issue
[ ] Other, (Fill in another type of issue here)

Expected behavior:
Should launch on start up. Checked in start up manager and anti virus, both have it ticked to launch on start up, no delay.
Actual behavior:
Doesn't launch
How often does this problem occur?

Everytime.
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

What is the version of Aurora you are experiencing this issue with?

My version is... v.0.6.0b
Does the previous version of Aurora have this issue?
Yes.
Please include any logs, screenshots, or files that are related to this issue:

Log: https://pastebin.com/EhkqKsvK
Aurora is run as admin everytime.

Could you try the latest development release to see if you still have the issue?

Tried it and problems are all solved thank you!


tons of file resources with nexus 3.0.x

We have the following setup (with Nexus 3.0.0):
  class{ '::nexus':
    version               => '3.0.0',
    revision              => '03',
    download_site         => 'http://download.sonatype.com/nexus/3',
    nexus_type            => 'unix',
    nexus_work_dir_manage => false,
  }

Despite nexus_work_dir_manage being set to false, since recurse is set to true in file{ $nexus_home_real:, with default settings, the work dir seems to be inside the main nexus home anyway, so Puppet creates a resource for each of those files. This is creating massive reports and long Puppet run times.
# grep -c "resource: File" /var/lib/puppet/state/last_run_report.yaml
47371

      resource: File[/srv/nexus-3.0.0-03/data/blobs/default/content/vol-08/chap-38/9bfbb901-705f-4ed1-921e-82d4262e71ee.properties]

Is the goal to ensure permissions on the initial installation, or to preserve them?
You might also look into replacing wget + exec with the archive module?

I'll also check - it looks like we may have made a local modification that could be partially to blame.


Failed to validate the SSL certificate for deb.nodesource.com:443

We use the ansible role martinmicunda.bower which depends of this role since long time and we have a problem since today. Apparently, we can't anymore import the GPG key of NodeSource because we haven't a valid certificate.

TASK [martinmicunda.nodejs : Import the NodeSource GPG key into apt] ***********
fatal: [default]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to validate the SSL certificate for deb.nodesource.com:443. Make sure your managed systems have a valid CA certificate installed. If the website serving the url uses SNI you need python >= 2.7.9 on your managed machine or you can install the urllib3, pyopenssl, ndg-httpsclient, and pyasn1 python modules to perform SNI verification in python >= 2.6. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible"}

I've changed the role nodejs on my space. In a first time, I added validate_certs=no in the apt_key ansible command but I get this error after:

TASK [martinmicunda.nodejs : Import the NodeSource GPG key into apt] ***********
fatal: [default]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to download key at https://deb.nodesource.com/gpgkey/nodesource.gpg.key: Request failed: <urlopen error [Errno 1] _ssl.c:510: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure>"}

If I remove the validate_certs and use http instead of https for the url of the GPG key, it works but it's not optimal and it's just a temporary quick fix.

Same as https://github.com/nodesource/ansible-nodejs-role/issues/33

I also encountered this problem. After checking this repository I was not quite sure why it still existed, because the key has been updated in the repository and therefore the problem should be resolved.
However, the problem is the ansible-galaxy command pulling the latest created release (v1.0.1 at the time of writing this) instead of the master branch. Would be great if you could create a new release or (if possible, I have no idea of ansible-galaxy) change the source of the ansible-galaxy project to 'dev-master'.

I see this happen as well when just attempting to fetch the setup_4.x file from deb.nodesource.com, but oddly only from specific IP addresses.
If I run the command "curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -" on Ubuntu 12.04.5 LTS, I get different results depending on the public IP of the server from which I run the command....
I have several machines across Florida, but one of them just cannot get that file, and ALL the machines are running the same version of Ubuntu (all updated), same version of wget, curl, and openssl, but one specific machine just hangs when attempting the above install fetch command.
I get the following when attempting wget, or curl without the pipe to bash:
wget https://deb.nodesource.com/setup_4.x
OpenSSL: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
or
curl -sL https://deb.nodesource.com/setup_4.x
error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

@rgagnon24 for this issue you need to add -k to curl. This will tell it to ignore ssl


command 'extension.coq.stepForward' not found

When restarting vs code, with it immediately automatically opening an existing Coq script, and doing Ctl-Alt-Down, get the warning: command 'extension.coq.stepForward' not found.
This doesn't happen all of the time, but enough to be frustrating...

This happens if you attempt to access vscoq's functions before it has been loaded by vscode. There's not much I can do about it directly, but maybe file a bug report with vscode because enabling an extension's keybindings before activating the extension is silly.

blocked on Microsoft/vscode#10401

Microsoft/vscode#10401 has been closed with the following explanation:

Yeah, closing this issue because we have the commandPalette section and context keys. A sample is here: https://code.visualstudio.com/updates/v1_10#_context-specific-visibility-of-command-palette-menu-items

I got this error, and for me it was because my vscode treated coq file as a verilog file, which made the vscode emit this message when I run step forward command.
If you check your bottom right corner and it says verilog it might help to change it to coq.


Exclude webhook port of prometheus operator from istio

Part of https://github.com/streamnative/data-plane-epics/issues/4
Add annotation to exclude the webhook port from istio.

LGTM


[BUG] Deserialization CreateIndexRequest is broken.

What is the bug?
The deserialization of CreateIndexRequest is broken.
How can one reproduce the bug?
deserialize CreateIndexRequest using ObjectMapper
What is the expected behavior?
Here, it is unclear what the behaviour should be. however it should not fail.
Do you have any additional context?
Serialization is opensearch request specific, The "index" field is discarded as it is part of the URL.
Deserialization follows the same process. however, "index" field is mandatory.
https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/main/java/org/opensearch/client/opensearch/indices/CreateIndexRequest.java#L440-L446
https://github.com/opensearch-project/opensearch-java/blob/main/java-client/src/main/java/org/opensearch/client/opensearch/indices/CreateIndexRequest.java#L97

Repro steps? Or maybe want to try to write a failing test for this?

Hi,
Thanks for the quick turn around.
I haven't found any test template,
However any CreateIndexRequest deserialization will fail.
Here a simple example of the issue:
      JacksonJsonpMapper mapper = (JacksonJsonpMapper) client._transport().jsonpMapper();

      JsonParser parser = Json.createParser(new StringReader("{\"index\":\"index\",\"mappings\":{\"properties\":{\"test\":{\"type\":\"text\",\"fields\":{\"keyword\":{\"type\":\"keyword\"}}}}},\"settings\":{\"number_of_shards\":\"1\",\"number_of_replicas\":\"1\"}}"));
      CreateIndexRequest deserialize = mapper.deserialize(parser, CreateIndexRequest.class);

      client.indices().create(deserialize);

You should get
Caused by: org.opensearch.client.util.MissingRequiredPropertyException: Missing required property 'CreateIndexRequest.index'.

I am getting the same error. Any news on this bug?
Or, can someone suggest a way to create index using a JSON file?

I have created a builder for the builder using the internal Serialiser. If that can help.

@alexisgayte - sure, can you please share it?

@alexisgayte @abhinav-nath
This is how I have created index using the client. Let me know if this works for you
private String getAnomalyDetectorMappings() throws IOException {
        URL url = AnomalyDetectionIndices.class.getClassLoader().getResource(ANOMALY_DETECTORS_INDEX_MAPPING_FILE);
        return Resources.toString(url, Charsets.UTF_8);
    }

JsonpMapper mapper = sdkClient._transport().jsonpMapper();
        JsonParser parser = null;
        try {
            parser = mapper
                .jsonProvider()
                .createParser(new ByteArrayInputStream(getAnomalyDetectorMappings().getBytes(StandardCharsets.UTF_8)));
        } catch (Exception e) {
            e.printStackTrace();
        }

        CreateIndexRequest request = null;
        try {
            request = new CreateIndexRequest.Builder()
                .index(ANOMALY_DETECTORS_INDEX)
                .mappings(TypeMapping._DESERIALIZER.deserialize(parser, mapper))
                .build();
        } catch (Exception e) {
            e.printStackTrace();
        }

and for handling deserialization using ObjectMapper
OpenSearchTransport transport = new RestClientTransport(
            restClient,
            new JacksonJsonpMapper(new ObjectMapper().registerModule(new JavaTimeModule()))
        );

Yes, that is mainly the idea.
However in my case I had to build a builder for the builder :
@JsonpDeserializable
public final class CreateIndexRequestBuilder extends CreateIndexRequest.Builder {

    private CreateIndexRequestBuilder(Builder builder) {
        mappings(builder.mappings);
        settings(builder.settings);
    }

    public static class Builder extends ObjectBuilderBase implements ObjectBuilder<CreateIndexRequestBuilder> {

        @Nullable
        private TypeMapping mappings;
        @Nullable
        private IndexSettings settings;

        public final Builder mappings(@Nullable TypeMapping value) {
            this.mappings = value;
            return this;
        }

        public final Builder settings(@Nullable IndexSettings value) {
            this.settings = value;
            return this;
        }

        public CreateIndexRequestBuilder build() {
            _checkSingleUse();
            return new CreateIndexRequestBuilder(this);
        }
    }

    // ---------------------------------------------------------------------------------------------

    /**
     * Json deserializer for {@link CreateIndexRequestBuilder}
     */
    public static final JsonpDeserializer<CreateIndexRequestBuilder> _DESERIALIZER = ObjectBuilderDeserializer
            .lazy(Builder::new, CreateIndexRequestBuilder::setupCreateIndexRequestDeserializer);

    protected static void setupCreateIndexRequestDeserializer(ObjectDeserializer<CreateIndexRequestBuilder.Builder> op) {
        op.add(Builder::mappings, TypeMapping._DESERIALIZER, "mappings");
        op.add(Builder::settings, IndexSettings._DESERIALIZER, "settings");
    }

}

Then you can use it the way you want :
      JacksonJsonpMapper mapper = (JacksonJsonpMapper) client._transport().jsonpMapper();

      JsonParser parser = Json.createParser(new StringReader("{\"mappings\":{\"properties\":{\"test\":{\"type\":\"text\",\"fields\":{\"keyword\":{\"type\":\"keyword\"}}}}},\"settings\":{\"number_of_shards\":\"1\",\"number_of_replicas\":\"1\"}}"));
      CreateIndexRequestBuilder indexRequestBuilder = mapper.deserialize(parser, CreateIndexRequestBuilder.class);
      indexRequestBuilder.index(indexName);
      client.indices().create(indexRequestBuilder.build());

I am not sure what you mean by that, I have done it 3 months ago and moved on, bear with me.
The main problem I had, is the definition cannot be auto populated without the index (which is not provided by the opensearch API call and the mapping we get from the API).
I am mainly using spring to wrap my object and auto mapping.

Thanks for sticking around @alexisgayte!
The original issue and the example above says "The deserialization of CreateIndexRequest is broken." and your code ends up with a missing required property error. Is it unexpected? What do we want to do in this project about it?

Yes of course, the property is part of the json.
What ever you do you will get this error. Basically you can't deserialised, if I recall.


Check to verify response status & content type in CLI / Runner

Resolves #101

Codecov Report

Merging #235 into master will increase coverage by <.01%.
The diff coverage is 100%.

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


The UI doesn't indicate whether a pod can have the proxy injected into it or why not

Consider a pod that has hostNetwork: true (see #366) or another reason (see #62 for example) why we might not inject the proxy into the pod. In that case, the UI will show the pod as "not in the service mesh." However, I think it would be useful if the UI showed the pod in a different state that indicates that it requires work beyond just doing conduit inject to get it into the service mesh.
Consider also the case where a pod has an explicit annotation (which we don't support yet, but we might eventually) that explicitly indicates the proxy shouldn't be injected and/or that we shouldn't do any proxying for the pod (we already support this with our port skipping options for conduit inject but this isn't persistent in the pod specs yet). The UI should somehow show these explicitly-opting-out pods differently.
Similarly, when conduit inject or equivalent is run and we skip some pods for the above reasons, we might want to output (perhaps only in "verbose" mode) messages indicating that we're skipping the pod spec and all the reasons why we're skipping it.

Similarly, the documentation should reflect these choices.


Changed wording

Changed the instruction "Set Two pane view" to "Toggle Two pane view"

Toggle won't work if it's currently on 2 pane view. Thanks for the suggestion.


Deserialization usage example

Hey, I would like to use this library to analyse the blockchain. I already have a downloaded copy, using the standard bitcoind. I assumed that I could use bitcoin::network::serialize::deserialize to deserialize a blk*.dat file into a Block struct. Is that correct? When I try to do that, the deserializer allocates an extremely large Vec<u8> and crashes because it's out of memory.

No, the blk*.dat files are not stored in the same format as blocks are in the Bitcoin network protocol. You cannot parse them with rust-bitcoin.
Thank you for reporting this memory-DoS issue though!

Thanks for your fast response! I'll look for another way then. If you want you can close this issue.

Fixed in https://github.com/apoelstra/rust-bitcoin/commit/cdb452f79faea376034c835557ad0cfe4ccd0659


update history and point at tagged releases

09/??/2018 | Team Hephy blog comes online
-- | --

We should make sure all the releases are properly tagged as well; outwardly on our Github presence, it still basically looks like we haven't actually made any releases since v2.18.0! (not true!)

Now for serious, all links appear to make sense... share to Facebook, Twitter, Google+
I will squash commits if that helps deisrel

On the timeline of everything, what was the k8s or kops release event that made the first need for Workflow to cut a v2.19.0?

(Or was it first, the router modsecurity stuff?)

RBAC was broken for 2.18.0 and we needed to fix the charts. They just so happened to have a few features like lifecycle hooks which was one of the major features in 2.19.0
Modsecurity will be a feature in the next release 2.20.0

Merged! :smile_cat:


Fix missing sRGB conversion for dithering non-HDR pipelines

Objective

Fixes #6706

Zoom in on the shadow in the following images:
Current bevy/main
HDR On - correct

HDR Off - incorrect

This PR
HDR On - correct

HDR Off - corrected

Close-up comparison
New

Old

Solution

It turns out there was an outright missing sRGB conversion for dithering non-HDR cameras.
I also tried using a precise sRGB conversion, but it had no apparent effect on the final image.

Changelog

Fix deband dithering intensity for non-HDR pipelines.

bors r+

bors retry

bors plz 🥺
bors retry

bors r+


GIF animation speed is slightly off

Rather than waiting X milliseconds before rendering the next GIF frame Pictus waits X milliseconds before displaying the current one. This may make certain animations to look a bit weird, but also introduces a delay before the first frame becomes visible.

It seems that I was wrong about that. Animations start up delayed in the start (equal to the delay of the first frame) if the first frame attempts to render before it is fully loaded.

The way animations are handled is inherently flawed (TOCTOU), but I should be able to make a basic work-around to make things work "well enough" for now.


Add all valid Transaction Type codes

Add all transaction types codes as defined by NACHA Corporate Rules in Appendix 3 - ACH Record Format
Specifications

Coverage remained the same at 96.872% when pulling 6ca958d3dd9141474df8f3a6227b2c149ffceb7c on wadearnold:transaction-codes into 3f07a52091e4c35f684c948613f9b911c5358fc5 on moov-io:master.


Department field description is not available in docs

Fixed [1]
[1] https://docs.wso2.com/display/IS550/Using+the+End+User+Dashboard


[Request-for-external] table 36 "Sales Header" - SetSalespersonCode

Can you change SetSalespersonCode to global in table 36 "Sales Header"?

Already done for 19.0


WIP: Upload excel

SUMMARY

Upload excel file to create table In addition to the csv
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #9825 into master will increase coverage by 4.60%.
The diff coverage is 65.00%.

@@            Coverage Diff             @@
##           master    #9825      +/-   ##
==========================================
+ Coverage   66.16%   70.77%   +4.60%
==========================================
  Files         585      184     -401
  Lines       30427    17879   -12548
  Branches     3152        0    -3152
==========================================
- Hits        20133    12653    -7480
+ Misses      10113     5226    -4887
+ Partials      181        0     -181

Flag
Coverage Δ

#javascript
?

#python
70.77% <65.00%> (-0.26%)
:arrow_down:

Impacted Files
Coverage Δ

superset/db_engine_specs/base.py
85.47% <56.25%> (-1.64%)
:arrow_down:

superset/config.py
89.66% <100.00%> (+0.08%)
:arrow_up:

superset/views/database/views.py
89.71% <100.00%> (ø)

superset/views/database/mixins.py
58.92% <0.00%> (-21.43%)
:arrow_down:

superset/utils/cache.py
45.83% <0.00%> (-20.84%)
:arrow_down:

superset/db_engine_specs/mysql.py
78.26% <0.00%> (-13.05%)
:arrow_down:

superset/views/database/api.py
83.90% <0.00%> (-3.45%)
:arrow_down:

superset/db_engine_specs/postgres.py
97.29% <0.00%> (-2.71%)
:arrow_down:

superset/models/core.py
83.77% <0.00%> (-2.36%)
:arrow_down:

superset/jinja_context.py
84.69% <0.00%> (-1.03%)
:arrow_down:

... and 405 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 ea9b7f2...c7d389b. Read the comment docs.

I need your help guys. With this PR the user is able to upload an Excel file in addition to the CSV files. but I don't know how to change it on the UI! I mean I don't know should I create a page for that like Upload excel file or should I handle uploading files e.g CSV and Excel only on the 1 page?
What about labels and existing translation! I only know English and Persian! and other questions :))
@villebro

Codecov Report

Merging #9825 into master will decrease coverage by 6.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9825      +/-   ##
==========================================
- Coverage   66.16%   59.29%   -6.88%
==========================================
  Files         585      399     -186
  Lines       30427    12564   -17863
  Branches     3152     3162      +10
==========================================
- Hits        20133     7450   -12683
+ Misses      10113     4933    -5180
  Partials      181      181

Flag
Coverage Δ

#javascript
59.29% <ø> (+0.03%)
:arrow_up:

#python
?

Impacted Files
Coverage Δ

...rset-frontend/src/explore/components/SaveModal.jsx
91.39% <0.00%> (-1.24%)
:arrow_down:

...rontend/src/visualizations/FilterBox/FilterBox.jsx
5.00% <0.00%> (-0.09%)
:arrow_down:

superset-frontend/src/chart/chartAction.js
49.07% <0.00%> (ø)

superset-frontend/src/explore/constants.js
100.00% <0.00%> (ø)

superset-frontend/src/setup/setupPlugins.ts
0.00% <0.00%> (ø)

superset-frontend/src/explore/exploreUtils.js
76.78% <0.00%> (ø)

...rset-frontend/src/components/ListView/ListView.tsx
98.07% <0.00%> (ø)

...frontend/src/components/ListView/LegacyFilters.tsx
75.00% <0.00%> (ø)

...rontend/src/explore/components/PropertiesModal.tsx
13.23% <0.00%> (ø)

...ntend/src/explore/components/ExploreChartPanel.jsx
11.11% <0.00%> (ø)

... and 194 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 ea9b7f2...695e131. Read the comment docs.

@blcksrx at least the following files are involved in the CSV upload feature:

superset/app.py: here the menu item is defined.
superset/views/database/forms.py: here the actual form is defined.
superset/views/database/views.py: here the view is defined.

I think Uploading of Excel files probably needs to happen via a dedicated dialog, as many of the CSV fields are not applicable for Excel. Having said that, many are, hence it might make sense to have a parent form with the global options (fail, replace, append etc), and then only add/override the ones that are specific to the format in question.

@villebro So it needs to do copy and pates many same things for that. right? for example, it needs to add a column allow_excel_upload to the database and extra. do you okay with that?

@blcksrx I think we can assume CSV and Excel importing being equal here, so no need to add a new column in table metadata for that. We should perhaps change the name to "allow upload" or similar. But I don't think that needs to be done now.

@villebro I got it. thank

@villebro Done!

Hi @blcksrx and @villebro thanks for bringing this feature to Superset! Today when I first tried this feature it gave me this error: "AttributeError: 'SupersetSecurityManager' object has no attribute 'database_access'",  but when I changed  security_manager.database_access(database) to security_manager.can_access_database(database) it worked. I'm not quite understand why the change works, so could you guys help me with this? Cheers!

Hi @blcksrx and @villebro thanks for bringing this feature to Superset! Today when I first tried this feature it gave me this error: "AttributeError: 'SupersetSecurityManager' object has no attribute 'database_access'", but when I changed  security_manager.database_access(database) to security_manager.can_access_database(database) it worked. I don't quite understand why the change works, so could you guys help me with this? Cheers!

Hi. it seems, there are some other commits that above my commit that changes the database_access to the can_access_database and the commiters forgot to change this on my commit


unknown auth mechanism：NTLM

What did you do?
When using alertmanager in enterprise, which often come with a closed network and private email server (exchange server). Thus email notify with NTLM auth support is needed
What did you expect to see?
alertmanager should send email notify through exchange server
What did you see instead? Under which circumstances?
smtp_require_tls: false
unknown auth mechanism：NTLM
Environment

System information:
kubernetes 1.14

Alertmanager version:
alertmanager 0.18.0

Prometheus version:
prometheus 2.11

Alertmanager configuration file:

global:
  resolve_timeout: 5m
  smtp_smarthost: "1xxxx:25"
  smtp_from: "xxxx"
  smtp_auth_username: "xxxx"
  smtp_auth_password: "xxxx"
  smtp_require_tls: false
route:
  group_by: ["alertname", "cluster", "service"]
  group_wait: 10s
  group_interval: 10s
  repeat_interval: 1m
  receiver: "test-mails"

receivers:
- name: "test-mails"
  email_configs:
  - to: "xxxxx"

Prometheus configuration file:

insert configuration here (if relevant to the issue)

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here
``

any news  ? does this issues wai fixed ?


bug: custom 384 well plates can't be used with the complex commands

Overview
The complex API level commands e.g. transfer() and distribute() will allow multichannel access to the 2nd row of the standard Opentrons 384-well plate, but will not allow this for a 384-well plate generated with the labware creator tool.
Steps to reproduce
Create a custom 384 well plate with the web tool https://labware.opentrons.com/create/ or just use this one
Greiner Bio-one 384 Well Plate 30 µL.zip
Now try to use it with transfer() into the B row.
def run(protocol):

    custom_348 = protocol.load_labware('greinerbioone_384_wellplate_30ul', 11)
    ot_384 = protocol.load_labware('corning_384_wellplate_112ul_flat', 10)

    tiprack_1 = protocol.load_labware('opentrons_96_tiprack_20ul', 1)
    p20_multi = protocol.load_instrument('p20_multi_gen2', 'left', tip_racks=[tiprack_1])

    # this works
    p20_multi.transfer(7.5, ot_384["B3"], ot_384["B14"])

    # this line will throw an error
    p20_multi.transfer(7.5, custom_348["B3"], custom_348["B14"])

Current behavior
The labware creator tool produces labware definitions with "format": "irregular" for all labware. This appears to be the root cause. Changing to "format": "384standard" in the custom labware definition resolves the issue.
Expected behavior
Complex commands should perform the same on custom labware as Opentrons standard labware.

I think this is a dupe of https://github.com/Opentrons/opentrons/issues/5085, right?
(I just skimmed these two issues. There might be a difference that I glossed over.)

Ah yep it is. Good Call!

Duplicate of #5085

Ooooooh!

I have no idea what marking an issue as a duplicate like that actually does.
Okay, I've had my fun.


feature: keymap overloading

Did you check the docs?

[X] I have read all the which-key.nvim docs

Is your feature request related to a problem? Please describe.
Item selection defaults are usually <c-n> <c-p> in Neovim. However, I find <c-j> <c-k> sensible over the defaults. I would have that in any directional item selection for example, Telescope, cmp etc... However, all of these has to be added to Insert mode which is a conflict so one will overrides the previous. But these could coexist because, Telescope should only work if the telescope window is opened. cmp keymaps only should work if the completion menu is open. Some plugins supports fallback some does not so there is no proper solution.
For example, I could use following to set keymaps and it fires the  original key sequence if there is no completion menu.
cmp.setup({
	mapping = cmp.mapping.preset.insert({
                -- I'm a colemak-dh user so I'm using e & n instead
		['<C-e>'] = cmp.mapping.select_prev_item(),
		['<C-n>'] = cmp.mapping.select_next_item(),
	}),
})

Drawback of the above is cmp.mapping.preset.insert adds custom <c-p> which I have never defined nor can get rid of. I could use it for something else. I could add mappings using which key, but now I cannot have a fallback map. Basically, what I'm looking for is keymap overloading.
Describe the solution you'd like
It's easier for me to explain this using a code snippet. So here we go.
wk.register({
	['<c-n>'] = {
		wk.conditional(function()
			if not completion_menu_open() then
				-- when returning false mean, which key should execute the next
				-- keymap overload
				return false
			end

			select_prev_cmp_item()

			-- if the function returns true, that means the action was handled
			-- by this function and no longer need to continue
			return true
		end),
	},
})

wk.register({
	['<c-n>'] = {
		wk.conditional(function()
			if not telescope_is_open() then
				return false
			end

			telescope_select_prev_item()
			return true
		end),
	},
})

Above key registration does not need to live within the same file (module).
Describe alternatives you've considered
I could create a generator module that generates a global or static function that takes all the condition functions by unique keymap. But it would be lovely to have a builtin function so I don't have to add the keymap to every keymap overload.
Something like below,
local action = keymap_overload('<c-n>', function()
  if not telescope_is_open() then
          return false
  end

  telescope_select_prev_item()
  return true
end)

wk.register({
  ['<c-n>'] = { action, 'does something'}
})

Additional context
No response

That's out of scope for which-key


Implemented setting types

There are many changes, as well as one critical change with the settings structure. I couldn't come up with strong types to implement the old settings, and I had to change the signature of the public setSettings method.
Also I found one eslint rule that conflicts with another
@typescript-eslint/consistent-type-imports <-> no-duplicate-imports
And I decided to remove @typescript-eslint/consistent-type-imports and I think that we should use only the classic import.

And about DX - now it's not very good. I think we should consider switching to another transpiler, or we should do a normal watch mode with the current build.)

And about DX - now it's not very good. I think we should consider switching to another transpiler, or we should do a normal watch mode with the current build.)

we could use concurrently with tsc watch + esbuild watch
esbuild could be a bundler and minifier, it is extremely fast
but not sure if that is what you thought? to after you change the typescript, that example dir is also built?

Wow, you really nailed it man, your work is so inspirative :)
will have much fun reviewing and learning from your changes

we could use concurrently with tsc watch + esbuild watch
esbuild could be a bundler and minifier, it is extremely fast
but not sure if that is what you thought? to after you change the typescript, that example dir is also built?
Well, I just now tried setting up the rollup watch mode with ts and it works.) Looks like my DX issues are gone and we can work with the current build config.

In this PR I will add new configuration and script for development - npm run watch

@Smrtnyk please check the latest commit. I have added some changes to the build configuration.

LGTM, amazing work


Mark web_connectivity with blocking or accessible = None as failed

Fixes backend#610
Example: https://explorer.ooni.org/measurement/20220524T011649Z_webconnectivity_TM_20661_n1_K12GviVnQLLRnJoU?input=https%3A%2F%2Fajax.aspnetcdn.com%2Fajax%2F4.5.2%2F1%2FMicrosoftAjax.js

0.59~pr395-152 deployed on FSN
Includes the deployment of https://github.com/ooni/pipeline/pull/390

Rolled back.


how to create customer column for Edit/Delete?

I would like to create customer column for Edit/Delete

@thearabbit Hi, Currently it doesn't support edit features in the component. But if you want to show dropdown and implement edit features by yourself, you can set react nodes as values in data props. for example,
const data = [{
  date: '30/03/2017',
  action: (<DropDownMenu>...),
  ...
}];

OK, thanks for your reply.
I will try soon.

I would like to custom action field with current data row
const data = [{
  _id: '01'
  date: '30/03/2017',
  action: (
    <IconMenu
                                                iconButtonElement={<IconButton><MoreVertIcon /></IconButton>}
                                                anchorOrigin={{ horizontal: 'right', vertical: 'top' }}
                                                targetOrigin={{ horizontal: 'right', vertical: 'top' }}
                                            >
                                                <MenuItem
                                                    primaryText="Edit"
                                                    onTouchTap={(event) => this.handleEdit(this._id)}
                                                />
                                                <MenuItem
                                                    primaryText="Delete"
                                                    onTouchTap={(event) => this.handleOpenConfirmDel(this._id)}
                                                />
                                            </IconMenu>
  )
  ...
}];

Please help me to get this doc of current row like above

Considering the scope of your event handler function, In this case, I would say using call method with specific arguments is a solution. And I think the other way is getting from dom using html5 data attribute.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/call


#327 and #328

The db context object - passed to every api endpoint now has two usefull methods: getElasticClient and getRedisClient for accesing the data stores - @pkarw (#328)
The lib/utils got two new methods getStoreCode(req: Express.Request) and getStoreView(code: string) for getting the current multistore context from vue-storefront frontend requests - @pkarw
The way Elastic and Redis clients have been fixed and code duplication removed across the app - @pkarw (#327)

One small improvment so we don't have every where the .../../../util  as example we could use the paths config in tsconfig.json in the compilerOptions. So we can use it for example "@lib/util"
This would then need this in the tsconfig.json.
    "paths": {
      "@lib": "src/lib/*"
    }

But to clean it up for the future I would add:
    "paths": {
      "@src": "src/*"
      "@lib": "src/lib/*"
    }

With that we could clean up our imports.

Thanks @ResuBaka for CR; I will take care of the changes next week by doing #342

@ResuBaka thanks for your insights; unfortunately tsconfig paths won't work with *.js files :/
I've applied changes to #342; closing tthis one in favor of #342


Errors in subflows are difficult to trace

When an error occurs within a subflow the error that appears in the debug pane doesn't contain a link to that subflow, this makes it hard to debug error when multiple subflows are present. Would be nice if hovering on the error message could hilight the subflow instance that triggered the error and clicking the link could open the flow template and hilight the node that caused it.

A message coming from a node inside a subflow will now:

highlight the subflow instance node when the msg is hovered
clicking on the node id in the msg will reveal the subflow instance node
if the subflow template is open, highlight the node the msg came from when the msg is hovered

This isn't quite what you suggested - it is a two step process to get to the node as you have to manually open the subflow template. If we jumped straight to opening up the subflow template, you wouldn't know which instance of the subflow the error had come from.
Nor does this work if the subflow is inside another subflow - it only works one level deep. Will need a fair bit more work to make it work at arbitrary depths of subflow nesting.

Thanks ! That will already help alot!


How to test example?

Hi,
I cannot run the program with the default example in test phase.
What i did:
Successfully ran the following command:
python3 main.py --data_dir datasets/DOTA_devkit/example/ --num_epoch 80 --batch_size 1 --dataset dota --phase train
The command worked perfectly and now I've got weights_dota folder, which contains the .pth neural networks.
After that, I would like to test the neural network, so i created a "datasets/DOTA_devkit/example/test.txt" file with the necessary filenames. The file contains only two row:

P0706
P0770

After the preparation I ran the following command:
python3 main.py --data_dir datasets/DOTA_devkit/example/ --resume weights_dota/model_20.pth --dataset dota --phase test
and I got the following output:
Traceback (most recent call last):
  File "main.py", line 61, in <module>
    ctrbox_obj.test(args, down_ratio=down_ratio)
  File "/home/project/programs/BBAVectors-Oriented-Object-Detection/test.py", line 128, in test
    nms_results = func_utils.non_maximum_suppression(pts_cat, scores_cat)
  File "/home/project/programs/BBAVectors-Oriented-Object-Detection/func_utils.py", line 45, in non_maximum_suppression
    keep_index = py_cpu_nms_poly_fast(dets=nms_item, thresh=0.1)
  File "/home/project/programs/BBAVectors-Oriented-Object-Detection/datasets/DOTA_devkit/ResultMerge_multi_process.py", line 74, in py_cpu_nms_poly_fast
    tm_polygon = polyiou.VectorDouble([dets[i][0], dets[i][1],
NameError: name 'polyiou' is not defined

I have no idea what should i do, because the training part worked flawlessly.
Have you ever met with this issue, or Am I missing something?
Thank you in advance for your help.

It looks like you haven't download the DOTA_devkit, you may download and install first and put the folder under datasets.


Component | Graph: nodeFill doesn't accept CSS variables or custom SVG defs

@rokotyan I noticed that unlike our other components, Graph doesn't support CSS variables or custom SVG defs for the node color. When providing either to nodeFill it fails with the following console error:

Is this by design or should we fix it?

For more context here is a side-by-side comparison w/ Area where custom color works:

@reb-dev I think we should fix it.
The isStringCSSVariable function can be helpful here (here is an example) but it won't work with gradients. I feel like we need to come up with a new unified approach for handling cases like this in the library.


Thread.sleep() in docs for connecting the Bean

The README states to use Thread.sleep() for a connection, but this is ill advised: it will lock up the main thread, making the app hang and technically there's no guarantee that the device will be connected in 5 seconds. In practice calls to the Bean should only be made after a succesfull onConnected call.

Hey @hvisser I am real sorry about the delayed reply.  My original goal with the README was to show off API usage, not necessarily best practice, however you are absolutely correct and I've updated the README to reflect your feedback!  Thanks.


#2180 - Queued Assessments - Assessment Workflow Enqueuer Scheduler - Start Assessment (Part 1)

Created the new queue configuration for the scheduler, executed every 30 seconds, and cleaned up every 24 hours.
Removed from the code the points where the queue to start the workflow was invoked. From now on only the scheduler will invoke the workflow start queue.

Method startAssessment removed since it is no longer needed.
Method hasIncompleteAssessment and assertAllAssessmentsCompleted removed since there is no purpose anymore.
Multiple workflows can now be saved and the scheduler will coordinate their execution.

StartApplicationAssessment queue can now be started without providing the workflowName.
Created a migration to update the assessment status based on assessment_workflow_id, and assessment_data. The rollback is less meaningful and it was created to try to bring the column back to its original state where the column was set with its default value Submitted.

TODO:

E2E tests
Logs

Move ProcessSummaryResult from integrations to lib to allow its use outside integrations.

Great job with creating the queue to process assessments. Great to see the depth of analysis and considerations involved in the effort. Thanks for explaining the issue with migrations. Please have a look at the comments.


chore(docker): add stadalone

:tada: This PR is included in version 0.4.0 :tada:
The release is available on:

GitHub release
v0.4.0

Your semantic-release bot :package::rocket:


New-Vesterconfig cannot differentiate datacenter with similar names

Expected Behavior
Selecting the data center selects the correct object
Current Behavior
Two datacenter objects exist with similar names:

Britomart Development
Britomart

Selecting either of them chooses the first one only so the second one is unable to be selected.
Possible Solution
Name selection needs to be an exact match instead of a "like" match
Steps to Reproduce (for bugs)
In the screesnhots below the only difference between them is selecting a different datacenter in each but the cluster and list of hosts is the same for both (ie "Britomart Development" datacenter has been selected for both)
https://www.dropbox.com/s/f9f8bq816noqm4i/vester1.jpg?dl=1
https://www.dropbox.com/s/imaqfshla0w1312/vester2.jpg?dl=1
Context
Currently unable to select the correct datacenter to run the script on
Your Environment

PSVersion: 5.1.14409.1005
OSVersion: Microsoft Windows NT 6.3.9600.0
Pester: 4.0.5
Vester: 1.1.0
VMware.PowerCLI: <IP_ADDRESS>77412
VMware.VimAutomation.Cis.Core: <IP_ADDRESS>74323

Actually... my expectation appears to be wrong, I assumed the subsequent selections were based off the previous selected options but don't seem to be. Actual issue appears to be with running { $Cluster    = $Datacenter | Get-Cluster -Name $config.scope.cluster } which is giving an error from the script.
When I run { get-cluster -Name '*' }  that works without an error.

Problem seems to be something strange happening when piping the $Datacenter array to the get-cluster command. If I pipe the array (containing two datacenter objects) to the get-cluster command one of them fails to execute but if I pipe the command from each of the array objects (eg $Datacenter[0]) then the commands work fine.
https://www.dropbox.com/s/71pwckh2j3vl2ou/vester3.jpg?dl=1

Welcome, @GodKratos!
So that's fun. It looks like Get-Cluster is incorrectly binding the [DatacenterImpl] objects to the -VMHost parameter, instead of -Location.
I'll hit up the PowerCLI team and see if they know about it.
In the meantime, if needed, we can compensate for that:
# Old
Get-Datacenter | Get-Cluster
# New
Get-Cluster -Location (Get-Datacenter)

Thanks, changing that line above does indeed work!
Not sure if it is binding to the VMHost parameter though because if I run Get-Cluster -VMHost (Get-Datacenter) I get quite a different error.

Ah, that's fair. I was assuming based on the error message, but didn't confirm. Interesting.

This is confirmed as a PowerCLI bug, and it won't be resolved in PowerCLI 6.5.2.
I'm thinking we can change Vester to officially use Get-Cluster -Location (Get-Datacenter) in the interim. Any interest in submitting a Pull Request? If not, I can tackle soon.
Thanks again for reporting!

Resolved in #180 🎉


Fix errors in 1.19

Also fixed some code because PacketPlayOutChat has been replaced to ClientBoundSystemChatPacket.

there is still a bug - "<>" is attached in front of the message


fix use correct dataset for unique_with_mow_p2

Proposed changes
Issue Number: close #xxx
cases in unique_with_mow_p2 should use sf100 dataset, rather than sf0.1 dataset
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


feat!: code and tests

This PR was included in release version 1.0.0-beta.2 :tada:

This PR was included in release version 1.0.0 :tada:


Proposal: Visual Studio xaml editor is not showing color inline preview when using AppThemeBinding in Xamarin

Related link to Xamarin.Forms repo: https://github.com/xamarin/Xamarin.Forms/pull/11012
Themes for Xamarin.Forms enables to fast implementation of dark/light themes.
when using for example:
<Label Text="Xamarin.Forms!" TextColor="{AppThemeBinding Dark=#2196F3, Light=#2196F3}"/>

Summary
Visual studio should display an incline color preview near beside Dark=#2196F3" and Light=#2196F3 the same way it did for something like:
Rationale

Because you are setting a color hex code it make sens to have preview inline for it.

Note:
I am not able to report this thru visual studio because of some session issues, if this is not the right place please someone report this as a visual studio issue.

@fabiant3 I'm not sure if this is us or VS's issue

@StephenLPeters, @fabiant3 @chingucoding  any update if this issue is in the right place or no ?

@LyalinDotCom is this something on the Xamarin team?

@Cfun1 J.P is correct this seems like a Xamarin issue, please be sure to report it in our repo for triage. Thanks!

@LyalinDotCom Thanks for clarification, (It is already there) I will ask to be reopened https://github.com/xamarin/Xamarin.Forms/issues/12441

Closing as duplicate in Xamarin.Forms repo.


Update codegen for service crate documentation that describes the high-level crate layout

This would help users understand how Service crates are structured and assist them in navigating the docs.
NOTE: A related change for fluent_builder was made in PR #1064.

I believe this is done now in the Crate Organization top-level section.


Introduce separator between "mark as handled" and other actions

A separator between "mark as handled" and other actions would make the. context menu more readable. And I think it is a nice logical separation.

Done


Pashto language added

Pashto language added
Account Number: 04ab47908bf0e72161f1b4c3b93e87c3d09b8e20162c220e3284972e3f82ab2b

@naveedahmad99 Thank you for your contribution!

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

done


Add table of contents generator/verify scripts

This adds scripts to generate and verify that the README table of contents is updated
/kind feature

/close
keeping this PR as an example though


Add Option To Ignore @ replies From Twitter

Having an option to ignore @ replies from tweet would cut down on the amount of tweet to toots I am seeing. Generally 95% of the @ replies from Twitter aren't directed at me so I don't necessarily see any value in adding them to Pleroma/Mastodon. For example, brands do a lot of @ replies as they support users over Twitter.
I made some small changes to _pleroma.py which I believe will skip @ replies. However it doesn't factor in an actual option to enable or disable the functionality. I suppose it's a start though. Around line 79:
    result = tweet_text.startswith('@')
    while not result:
        print (f'Tweet did not start with "@", processing...')
        if self.media_upload:
            for file in media_files:

Probably don't need the print statement but may be useful for debugging.

Agreed, this would a much welcomed quality of life improvement we could let the users choose to use.
However, I actually see this enhancement as including replies or not, not as including tweets which begin with '@' or not. I could write a new tweet mentioning someone without it being a reply neccesarily, I see the value of keeping that hypothetical "new" tweet when posting it to the Fediverse account.
Twitter's API has this field called referenced_tweets for each tweet which is a list of dicts. These dicts have the attribute type which can take the value replied_to, if the tweet in question is a reply to another existing one.
This is how we currently identify retweets and filter them, we could do much the same for replies:
https://github.com/robertoszek/pleroma-twitter-info-grabber/blob/039ed7279240ed7d7146fac1a267cbc6030bce4e/pleroma_bot/_utils.py#L116-L125

Agreed, this would a much welcomed quality of life improvement we could let the users choose to use.
However, I actually see this enhancement as including replies or not, not as including tweets which begin with '@' or not. I could write a new tweet mentioning someone without it being a reply neccesarily, I see the value of keeping that hypothetical "new" tweet when posting it to the Fediverse account.
Twitter's API has this field called referenced_tweets for each tweet which is a list of dicts. These dicts have the attribute type which can take the value replied_to, if the tweet in question is a reply to another existing one.
This is how we currently identify retweets and filter them, we could do much the same for replies:
https://github.com/robertoszek/pleroma-twitter-info-grabber/blob/039ed7279240ed7d7146fac1a267cbc6030bce4e/pleroma_bot/_utils.py#L116-L125

Hi,
as I mentioned, I followed a similar approach to how we filtered RTs to acomplish the same thing with replies.
Here's the commit ce55a3c8fbff6df7bc7aff5d7fa1e9081c9bce5b
You can test it out with a staging release by running:
pip install --index-url https://test.pypi.org/simple/ pleroma-bot --upgrade

Version number should be 0.6.8
These changes will be included on the next roll out to master.

Hi,
as I mentioned, I followed a similar approach to how we filtered RTs to acomplish the same thing with replies.
Here's the commit ce55a3c8fbff6df7bc7aff5d7fa1e9081c9bce5b
You can test it out with a staging release by running:
pip install --index-url https://test.pypi.org/simple/ pleroma-bot --upgrade

Version number should be 0.6.8
These changes will be included on the next roll out to master.

Twitter's API has this field called referenced_tweets for each tweet which is a list of dicts. These dicts have the attribute type which can take the value replied_to, if the tweet in question is a reply to another existing one.

@robertoszek That's definitely way better of an implementation. I hadn't dug too much into the Twitter API so I wasn't aware of referenced_tweets.
Any ETA on next master rollout? 😁

Twitter's API has this field called referenced_tweets for each tweet which is a list of dicts. These dicts have the attribute type which can take the value replied_to, if the tweet in question is a reply to another existing one.

@robertoszek That's definitely way better of an implementation. I hadn't dug too much into the Twitter API so I wasn't aware of referenced_tweets.
Any ETA on next master rollout? 😁

Any ETA on next master rollout? 😁

Probably sometime next week, I'll need to receive some sort of confirmation that the unstaged changes solved your issues before pushing them though haha
I did my own testing but you never know, maybe I missed something particular to the instance you're pushing to.

Any ETA on next master rollout? 😁

Probably sometime next week, I'll need to receive some sort of confirmation that the unstaged changes solved your issues before pushing them though haha
I did my own testing but you never know, maybe I missed something particular to the instance you're pushing to.

Changes promoted to master. Let me know if you experience any issues with the fix implementation.
Cheers!

Changes promoted to master. Let me know if you experience any issues with the fix implementation.
Cheers!


Coupling pdb residue mapping

Codecov Report

Merging #71 into master will decrease coverage by 0.76%.
The diff coverage is 55.76%.

@@           Coverage Diff            @@
##           master    #71      +/-   ##
========================================
- Coverage   82.76%    82%   -0.77%
========================================
  Files          29     31       +2
  Lines        1416   1450      +34
  Branches      224    231       +7
========================================
+ Hits         1172   1189      +17
- Misses        244    261      +17

Impacted Files
Coverage Δ

src/component/NGLComponent.tsx
94.28% <ø> (ø)
:arrow_up:

src/component/widget/ChellTooltip.tsx
0% <0%> (ø)

src/helper/ResidueMapper.ts
100% <100%> (ø)

src/component/chart/PlotlyChart.tsx
100% <100%> (ø)
:arrow_up:

src/helper/DataHelper.ts
99.15% <90%> (+3.95%)
:arrow_up:

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 39e09a5...c8a6183. Read the comment docs.