HDDS-7536. Remove unused dependency declarations

What changes were proposed in this pull request?
Some dependency declarations in Ozone root POM's dependencyManagement are leftover from Hadoop, unused, and can be removed.
https://issues.apache.org/jira/browse/HDDS-7536
How was this patch tested?
No added or removed dependencies, verified by dependency check in CI.
Also verified that dependency tree has not changed.  The only difference between Maven's output from master and the patch is in the Reactor Summary (time required to build each sub-module):
$ git checkout master
$ mvn -Dorg.slf4j.simpleLogger.showDateTime=false -B --no-transfer-progress dependency:tree > dep.master
$ git checkout HDDS-7536
$ mvn -Dorg.slf4j.simpleLogger.showDateTime=false -B --no-transfer-progress dependency:tree > dep.HDDS-7536
$ diff -uw dep.master dep.HDDS-7536
--- dep.master	2022-11-25 18:14:37.836905281 +0100
+++ dep.HDDS-7536	2022-11-25 18:14:20.081183954 +0100
@@ -5085,52 +5085,52 @@
 [INFO] ------------------------------------------------------------------------
 [INFO] Reactor Summary for Apache Ozone Main 1.3.0-SNAPSHOT:
 [INFO]
-[INFO] Apache Ozone Main .................................. SUCCESS [  0.214 s]
-[INFO] Apache Ozone HDDS .................................. SUCCESS [  0.230 s]
+[INFO] Apache Ozone Main .................................. SUCCESS [  0.194 s]
+[INFO] Apache Ozone HDDS .................................. SUCCESS [  0.218 s]
...

Regular CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/3535439077

@jojochuang would you like to take a look?

Thanks @ayushtkn, @jojochuang for the review.

I thought you wanted to remove unused but declared dependencies in each modules

Yeah, that's another task.  We need to be more careful there, as some dependencies are only used at runtime e.g. when using Hadoop classes.


Geekie bugfix

When using the text tool, not having the text "type something". Often the text does not disappear when you start typing.
When using the zoom tool, it should have buttons to zoom in and out with maximum zoom at 200% and minimum zoom at 50%. Only the trackpad is not intuitive. Buttons increment/decreases 10%.
When using the pencil, shape, or text tool, the font size and color options box should be exposed while I have the tool selected.

Append two fixes in this MR:

The default value of pencil, shape and text tools should be Normal and not Small value.
When it has background image, if I use the eraser, it won’t erase the background image, just the layers above.

Hi @dilidili, thanks for the PR. GitHub says "This branch cannot be rebased due to conflicts". I can solve this here, but for the next PRs could you please create the new branch from the master branch to avoid conflicts?

Hi @gabrielguilhoto, could you give me more details about the confilict? From my side, there are no conflicts exist.

Hi @dilidili, I was using the "rebase and merge option":

But looking at the commits I don't see why there would be conflicts. I guess I can use the other merge options, no need to worry on your side.


Android blur view

Which platform(s) does your issue occur on?

Android

I know that the documentation says only images can be blurred on Android but Is there any workaround to blur a nativescript view on Android such as a StackLayout ? I'm trying to blur the entire screen except the ActionBar and I would like to keep it consistent between the IOS and Android versions.
Thank you

Nevermind used a blurred image for Android


Corrected regression with preference files name (since 2.0.0)

Corrected a regression introduced by https://github.com/puppetlabs/puppetlabs-apt/commit/351c8d5941f6bd02304df6b4185dea8c8104aefa
(Default value of 50 was used for priority param when apt::setting is called inside pin.pp)
Added changes from https://github.com/puppetlabs/puppetlabs-apt/pull/554

@mhaskel , @bmjen could you have a look at this?

This needs a squash, 1 feature, 1 commit to keep the history reasonable.

@daenney is the rest OK?

See https://github.com/puppetlabs/puppetlabs-apt/pull/562

Apparently there's now two pull requests from @Vincent-- for the same issue. I'd appreciate if one would get closed.

Hey @daenney,
You've asked for a squash, so I did...
See https://github.com/puppetlabs/puppetlabs-apt/pull/562

@Vincent-- Ah, thanks. I assumed you'd force-push it to this one, not raise a new PR. That's where my confusion came from.


Fix Panic in PackageManifest Server

Description
Seems to have been caused by variable shadowing.
Fixes https://jira.coreos.com/browse/ALM-823

/approve
/lgtm


Add hint text for driving licenses

Add hint text for both sides of id to be uploaded
https://trello.com/c/647B1THu/1852-hint-text-both-sides-of-id-card-dev-card

 Hint text: both sides of ID card - Dev card


Fix "Cannot read property 'text' of undefined" exception

Fixes #19.
@50Wliu: could you help me confirm this fixes the issue you reported? Thanks! ✨

I'll test it out once I have some more packages with incompatible modules :+1:.

Okay, I'll optimistically merge this and bump it on master. Thanks!


docker support

Currently try will not work in docker containers, as they’re backed by overlayfs already (by docker default).
Stackoverflow has a solution to this, which works.
mkdir /tmp/overlay
mkdir /tmp/{low,merged}
mount -t tmpfs tmpfs /tmp/overlay
mkdir /tmp/overlay/{up,work}
mount -t overlay overlay -o lowerdir=/tmp/low/,upperdir=/tmp/overlay/up/,workdir=/tmp/overlay/work/ /tmp/merged/

Essentially, the directory that both upperdir and workdir resides in has to be tmpfs. Note that making just the upperdir and workdir tmpfs is not sufficient.
We can modify try to leverage this to enable support for docker.
This is trivial to do if we only care about running this try as root. We can simply run mount -t tmpfs tmpfs “$SANDBOX_DIR” after mktemp -ding it.
However, if we want to do this as a user (in docker containers), this becomes tricky, as we will have to make the tmpfs in unshare, which is also do-able, i was able to make a proof of concept to do this. However, that tmpfs will disappear after we exit the unshare, so we will have to find a way to persist it. This will require some considerable refactoring.

As indicated earlier in #19, we are not planning on implementing this right now. This issue is just for documentation purposes.
I’ll close this as won’t fix, until maybe someday we want to address this.


Cannot set divider thickness in java

Hi,
As the title says, divider thickness can only be set in xml, because mSelectionDividerThickness is private.
Thanks.

Hi @lukaspili,
It's supported at v2.2.0.
numberPicker.setDividerThickness(int thickness);

Thank you @ShawnLin013


phantomjs-prebuilt

Hi Thomas,
In stead of "phantomjs" or "phantomjs2" i got installed "phantomjs-prebuilt".
In its README.md it says: "Pre-2.0, this package was published to NPM as [phantomjs] (https://www.npmjs.com/package/phantomjs). We changed the name to phantomjs-prebuilt at the request of PhantomJS team."
As a workarround I now use:
phantomjsBinary: require('phantomjs-prebuilt').path,
Is it an idea to add in /master/Pool.js something like:
try { phantomjsLib = require('phantomjs-prebuilt'); } catch (e) {}

Thank you for opening an issue. I just released a fix (v0.3.2).


Connections to TI CC254x break after conn_update

Nordic softdevices have a flag BLE_GAP_OPT_COMPAT_MODE, for ensuring the connection window offset does not become zero because of bugs in TI CC254x stacks. Is there a way to prevent such windows from being used in zephyr?

I've assigned this to @cvinayak so he can provide an answer here.

I put the following in isr_rx_scan()
	if (_radio.scanner.win_offset_us == 0) {
	   _radio.scanner.win_offset_us = 2;
	}
            {
		conn_space_us = _radio.scanner.win_offset_us;
		while ((conn_space_us & ((u32_t)1 << 31)) ||
		       (conn_space_us < conn_offset_us)) {
			conn_space_us += conn_interval_us;
		}
		pdu_adv_tx->connect_ind.win_offset =
			(conn_space_us - conn_offset_us) / 1250;
		pdu_adv_tx->connect_ind.win_size++;
	}

Now connections to TI devices work, but i doubt this is safe to do. I also considered calling the ticker api and reserving the first time slot for some non existent user function, but wasn't able to figure out the ticker api or the correct constants to make that work.


Make TextSpan hit testing precise.

Fixes https://github.com/flutter/flutter/issues/131435, #104594, #43400
Needs https://github.com/flutter/engine/pull/48774 (to fix the web test failure).
Currently the method we use for text span hit testing TextPainter.getPositionForOffset always returns the closest TextPosition, even when the given offset is far away from the text.
The new TextPaintes method tells you the layout bounds (width =  letterspacing / 2 + x_advance + letterspacing / 2, height = font ascent + font descent) of a character, the PR changes the hit testing implementation such that a TextSpan is only considered hit if the point-down event landed in one of it's character's layout bounds.
Potential issues:

In theory since the text is baseline aligned, we should use the max ascent and max descent of each character to calculate the height of the text span's hit-test region, in case some characters in the span have to fall back to a different font, but that will be slower and it typically doesn't make a huge difference.

This is a breaking change. It also introduces a new finder and a new method WidgetTester.tapOnText: await tester.tapOnText('string to match') for ease of migration.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Passing TGP: OCL:592353811:BASE:592365935:1703029674505:124de1d9


big Y offset icon position when generated with fontforge engine

icons: {
src: 'path/*.svg',
dest: 'path',
destCss: "path",
options: {
fontFilename: 'IconsMain',
hashes: false,
types: "eot,woff2,woff,ttf,svg",
templateOptions: {
baseClass: 'mIcons',
classPrefix: 'm_'
},
stylesheets: ["scss"],
normalize:   true,
autoHint: false,
htmlDemo: false,
fontPathVariables: true,
relativeFontPath: "./../path",
}
}

OS 	Ubuntu 17.10
Task manager: grunt(grunt-cli v1.2.0)
What it can be. True size of icon - 80px x 80px. (if i do sizes bigger, for example 512px x 512px - offset is stand smaller)
was tried generate fonts on node engine - have warning - "Found a clipPath element in the icon "iconName" theresult may be different than expected." and generated icons have color(black and white) reverse(but doesn't having offset problem)
all path are summed.
viewBox="2289 -1301 96 96" (viewBox="0 0 96 96" - don't help)

this is not a css problem


Polynomial constructors should collapse additive-inverse terms

import spire._, math._, poly._
val t = Term(Rational(8, 7), 1)  // 8x/7
val p = Polynomial(Seq(t, -t))
// p: spire.math.poly.PolySparse[spire.math.Rational] = ()

p.isZero  // false; bad!
val p2 = p.toDense.toSparse  // (0)
p2.isZero  // true
p2 == p  // false; bad!

Polynomial.apply and PolySparse.apply will happily generate ~invalid polynomials this way.
This means PolynomialCheck has had several broken tests (which fail nondeterministically, cf #665, which failed 2 of 3 jobs in a recent CI on #668).
I'll look into fixing it as well as otherwise working-around the tests' issue.

#669 also just failed due to this

@ryan-williams (Still doing clean up) Do you think this is still a bug?

Thanks @denisrosset, I think https://github.com/non/spire/pull/653 fixed this!


Add fields on json for submission

@Jerem-info Thanks for your pull request, I will test the changes as soon as possible.


Updated embedding generation with batch processing

Changes made in the code

Changed the normal processing to batch processing in embedding generation.

Dealed with vector dimension mismatch and fixed it.

Hello, I am a PR summary agent on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


Cookie names not set properly.

I overlooked the fact that setting the AuthenticationScheme values does not actually achieve what we want. By default, cookie names are set to .AspNetCore.{AuthenticationScheme} and this leads to names like .AspNetCore..AspNetCore.Identity.Application. We can remove the .AspNetCore. from the prefix  of the authentication scheme.
Still investigating the why there are also cookies like .AspNetCore.Microsoft.AspNetCore.Identity.ExternalLogin.
Edit: Ignore the ExternalLogin cookie issue. That is a really old legacy name for the cookie and the test is only checking it for non-existence.
fyi @natemcmaster

By default, cookie names are set to .AspNetCore.{AuthenticationScheme}

Where is this in code?

@natemcmaster I mean the default schemes https://github.com/aspnet/Identity/blob/dev/src/Microsoft.AspNetCore.Identity/IdentityCookieOptions.cs#L16-L20


Add nearest-neighbor method to netcdf subsetting

One problem we face is that of small catchments whose polygons fall between climate model grid points. Our current codes take the average of all grid points within a catchment boundary as the climate data time series. This will fail for catchments with 0 points (return empty array). We need to catch this and revert to a plan B, either the average of the 4 bounding points (4 closest points to the center essentially) or simply take the nearest neighbor, perhaps with a warning message that this is what has been done.

For nearest neighbour, you could use finch.subset_gridpoint.
For averaging over an area, this is still a WIP.

OK so for now we can use the local "salem" roi process for larger catchments, and revert to finch.subset_gridpoint if there are no points. Make sense?

Yes, but working on a flyingpigeon process to return the average over a shapefile, which I think will be robust to the situation you're pointing out.

Yes exactly, good. Keep me posted when that process is implemented so we can switch from salem to FP.

@richardarsenault I would be careful with building too much based off of salem. It doesn't seem to receive too many updates and the dependencies are quit out of date (to the point that it doesn't jive with xclim anymore). Would you be open to different tools?

Yes absolutely, actually I think the idea is that the subsetting will eventually be part of Finch? so that would basically supersede Salem

I would be careful with building too much based off of salem. It doesn't seem to receive too many updates and the dependencies are quite out of date (to the point that it doesn't jive with xclim anymore)

On the Jupyter env, salem has forced pinning much older version of pandas and geopandas https://github.com/Ouranosinc/PAVICS-e2e-workflow-tests/blob/0ffbd16b334e6628a19befd3c380c67b873e96eb/docker/environment.yml#L20-L23

I have zero attachment to Salem, only to do the demo I needed something and it was the first I could get to work. If we can replace it by something more modern I'd be more than happy!

Is this something that we can now do in the refactored Xclim?

@richardarsenault Actually, once the next version comes out, this won't be possible out of the box for xclim. The subsetting libraries are being migrated to another project (https://github.com/roocs/clisops/) where they will need to be loaded from. It will functionally be the same with some minor changes to the function calls. Hopefully the transition work for Raven won't be too complicated.

I think this is now offered though Finch.


Omnisharp Current State

I'm not sure whether this is the right place to raise this issue, but I think it is more appropriate than non-official forums, but please let me know if I should discuss this elsewhere.
I feel that the current state of Omnisharp is a complicated one... Development with VSCode + Omnisharp is very slow and can get very frustrating due to the amount of bugs that range from wrong syntax highlighting to random crashes, and performance is awful, sometimes taking anywhere from 15 to 30 minutes to parse 100kloc to 200kloc multi-project solutions, sometimes crashing halfway. Also, the support for Razor is bad.
I am not ranting or pointing fingers to the developers that spend their time and energy to make this project happen, and I ask other users to behave in a respectful way. But I would like to know if other Omnisharp users have had the same productivity problems, and are thinking of dropping or have dropped Omnisharp for other solutions.
If possible, I would like to know from the repository maintainers what the current state of the project is. Specially if there internal  consensus/awareness that the current software is instable, if there is a plan to make it better, and how the community can help.
Also, I've been asking myself lately if Omnisharp is actively supported and/or developed by Microsoft or is 100% driven by the community developers. Does anybody know?
It turns out that it is not making sense for us to double down on VS Code + Omnisharp + Linux anymore... Which is a shame because other options like  VS Studio or ReShaper IDE lags behind in portability, extensibility  and customization features, specially setting up the development environment with containers, which we rely heavily on.

100% echo these sentiments, and would be glad to try preview builds and contribute in any way I can. I had some really good successes with O# over the past few years, and I really love it. Unfortunately, in the past 8-9 months things have gotten much worse, and it's to the point that I'm having trouble estimating timelines and consistently delivering features in a modest (<100K LOC) codebase.
There's a community here that wants this to succeed! How can we help?

It's sad that the c# support is vs code is so poor compared to other languages. I try it in earnest once or twice a year, and the experience is just frustrating for anything beyond 'hello world'. In contrast, the experience for c++, java, and golang is quite good when I've used it.
I highly recommend Rider, it is fast on even our largest c# code base, where VS + ReSharper is unusably slow.
There are definitely some unique capabilities that keep my coming back to VS Code (git UI, remote development). I wish Microsoft considered C# support to be important enough to support, seems like it would be a funnel of new C# users that the developer relations folks keep talking about trying to reach.

My organization is actively pursuing alternatives to Omnisharp due to the lack of direction and continuing bugs in this project.  These issues with false bugs being reported and extremely slow response times are slowing down our teams.  As for myself, I would prefer to echo @floyd-may:

There's a community here that wants this to succeed!  How can we help?

According to #4307 many of the issues we've been seeing have to do with a change that got introduced around August of last year. There was a new release cut a couple weeks ago that should make things... better... However, if I understand correctly, most of the effort in this project is headed towards converting it to use the language server protocol (LSP) to communicate with the Omnisharp server instead of the current custom protocol. That effort is still ongoing, and I'm probably going to wait to retry Omnisharp until it's complete.
When that day does come, I will be glad to try it again and dig in with the community, but it seems like right now we just need to step away and let them finish.

There was a new release cut a couple weeks ago that should make things... better

Apparently not https://github.com/OmniSharp/omnisharp-vscode/issues/4527

For me Omnisharp does one of the following:

Crashes for no reason (40% of the time)
Eats all available CPU and Memory (40% of the time)
Works (10% of the time)

At the current state of things I don't even know if it's helping or hurting my productivity. And I have no idea why the hell does it use Mono in 2021. I tried to build it for .NET Core but it doesn't work and nobody seems to care https://github.com/OmniSharp/omnisharp-roslyn/issues/1703#issuecomment-837710970

@JoeRobich would you mind giving us some feedback on these matters?

@filipw Hi, would you mind giving us some feedback on the project stability?

I'm also having a rough time, expecially with multi-project solutions. For instance, squigglies stay on their line instead of following their line of code and I often need to rebuild for them to go away.
I'd also like to ping @filipw to know how's the project doing.

@BrightSoul @Mithras @floyd-may @BradBarnich et al
Although we never had any reply or feedback from the Omnisharp team, apparently the issue is fixed with the new net6 based version.
If you haven't tested, all you have to do is upload to the latest version  of omnisharp-vscode (1.24) and add the following configuration to your vs code settings:
		"omnisharp.useModernNet": true,
		"omnisharp.useGlobalMono": "never",
		"omnisharp.path": "latest",

Please let me know if this fixes the issue for your too so we can close this issue.

Yep, it works flawlessly for me. Momo was the only reason OmniSharp was unusable on Linux.

"omnisharp.path": "latest", is not needed and should be avoided because it will download a new build every single time there is a merge to omnisharp-roslyn repo. This is likely to be slow and destabilize the extension, or in extreme cases may even cause the extension to stop working if new OmniSharp Roslyn requires changes on the extension side.
Now that 1.24.0 is released the only settings to opt into .NET 6 build are
"omnisharp.useModernNet": true,
"omnisharp.useGlobalMono": "never", // the current default behavior is never anyway, though it may change

@filipw thanks for point that out, and for the effort on moving the omnisharp compilation to .net6

@filipw If we are still stuck on net5, can we nonetheless install/use the new version of the extension? And if so, will all the updates not apply to us (because it seems like everything is behind a feature flag)?

OmniSharp requires .NET 6.x.x SDK to be present.
The old variant based on Mono is still maintained (for now).

@filipw Thanks. Just to confirm I understand - I have net6 Runtime installed as a number of extensions need it. But my projects target net5, and the SDK installed is net5. Are you implying that is not good enough for this extension - it must have the v6 SDK rather than the Runtime?

Yes the .NET 6 SDK is necessary to be installed to use the .NET 6 build of Omnisharp, as it supplies the MSBuild.


I find it so many ‘spark-deep-learning’

I find it so many ‘spark-deep-learning’, such as :
elephas：https://github.com/maxpumperla/elephas
dist-keras：https://github.com/cerndb/dist-keras
sparknet：https://github.com/amplab/sparknet
dl4j：https://github.com/deeplearning4j/dl4j-spark-ml
TensorFlowOnSpark：https://github.com/yahoo/TensorFlowOnSpark
spark-deep-learning：https://github.com/databricks/spark-deep-learning
H2O：https://github.com/h2oai/sparkling-water/tree/master/
BigDL：https://github.com/intel-analytics/BigDL
analytics-zoo：https://github.com/intel-analytics/analytics-zoo
It looks like BigDL is the most active one. I want to start my DeepLearning on spark by using spark-deep-learning, but I afraid others will popular than  databricks.spark-deep-learning. So I still hesitate which one to choice.

I find it so many ‘spark-deep-learning’, such as :
elephas：https://github.com/maxpumperla/elephas
dist-keras：https://github.com/cerndb/dist-keras
sparknet：https://github.com/amplab/sparknet
dl4j：https://github.com/deeplearning4j/dl4j-spark-ml
TensorFlowOnSpark：https://github.com/yahoo/TensorFlowOnSpark
spark-deep-learning：https://github.com/databricks/spark-deep-learning
H2O：https://github.com/h2oai/sparkling-water/tree/master/
BigDL：https://github.com/intel-analytics/BigDL
analytics-zoo：https://github.com/intel-analytics/analytics-zoo
It looks like BigDL is the most active one. I want to start my DeepLearning on spark by using spark-deep-learning, but I afraid others will popular than databricks.spark-deep-learning. So I still hesitate which one to choice.

Hey, my bro, have u made your decision?


Update history

Hello @HolQue,
Thank you for your comment, I made the mistake.
Hello Thomas,
I have just updated the packageversion too.
Thank you,
Son

Hello Thomas,
I updated pdf file.
Thank you,
Son


⚠ ClamAV has degraded performance

In 07af301, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 71 ms

Resolved: ClamAV performance has improved in 7eb4646.


feat: [AAP-35878] add copy endpoint for EDA Credentials

Closing in favor of https://github.com/ansible/eda-server/pull/1158


GAE/GCE "python" runtime support?

I've been investigating the feasibility of migrating from python-compat to python as defined on https://cloud.google.com/appengine/docs/managed-vms/python/migrating-an-existing-app (to get a more standard GCE environment, Google Cloud Debugger, etc).
But doing so means no more google.appengine.*. Was curious if there was any plan/possibility of this library working on GCE (through gcloud.datastore, etc), or if the reliance on push-taskqueues (which are apparently unavailable on GCE?) means this is a nonstarter that will never happen, and I should get used to my GAE-Managed-VM python-compat world for the longterm...
Thanks!

I believe the "correct" answer here is to use Cloud Dataflow, which is supported on the GCE environment (without the need for push taskqueues):
https://cloud.google.com/blog/big-data/2016/03/google-announces-cloud-dataflow-with-python-support


Minor updates for 11.0

IsAddOnLoaded was moved into C_AddOns in 11.0
TOC bump
Additional TOC for upcoming launch build as well

Looks good to me! I've gotten reports that the addon is currently not working on the beta servers, can you confirm that this works with the newest version? Or is this only for 11.0?

Haven't looked in to the beta yet, I'm guessing Ace needs updating for the new method of adding options to the interface panel (+ maybe a workaround for the fact that EasyMenu is gone)

I see, I have someone else working on updating everything, so I'll hold off on merging this for a bit. I'll see if there are still any changes left once the other updates are done and merge this then, if that's ok with you.

Sounds good, as for 11.0.2 I just did some research and found that C_Scenario.GetCriteriaInfo is broken on Blizzards end and already got reported - there is no way to grab mount-count currently and the C_Scenario.GetCriteriaInfo is sometimes nil when you start the key. some reference here

WarpDeplete is currently broken on live pre-patch 11.0. It would be helpful to merge this if it fixes WarpDeplete in live and then we can open another to address 11.0.2 in beta?

Yeah, I've seen that as well, guess we'll need to wait a bit for everything to be working again. Since these changes were already done in other PRs, I'll go ahead and close this. If anything is missing from main, feel free to open another PR.


Vi Mode: Request change cursor for insert/normal mode

Is there any way the cursor can be changed to indicate the insert/normal mode status?

Done.  Use the -ChangeCursor switch parameter to turn it on (-ChangeCursor:$false for off).

AWESOME!
A couple of minor nits though. :wink:
Shouldn't -ChangeCursor be -ChangeViCursor just like the property name just for the sake of consistency?
Also, to be more consistent with console vim could you make the cursor block in normal mode and small in insert mode?

I initially had it as ChangeViCursor, but changed it to be more general in case other opportunities come up.  I should have changed the property name as well.  I don't know enough about Emacs or Windows mode to know whether they'd ever benefit from a cursor change.  Thoughts?
The cursor in normal mode should be the opposite of what the user has the default cursor set to (or should be).  I just tried it, and it worked for me.  So, if you want insert mode to be small, set your default via Properties - Options - Cursor Size to small.  You have to restart your console for the change to take hold as far as my code is concerned.

Windows mode should (but doesn't yet) support overstrike mode, in which case the cursor should change.
I'm not sure it's worth having an option here - it feels like there should always be a visual way to know you're in one or the other modes.  If there was an option, I would expect to choose from alternate visual styles, maybe something like: -ViNormalModeIndicator [StatusLine|Cursor].

Thanks Steve. I forgot I had changed my default cursor size to Large. I'm getting too old I think. :pensive:
I just set my cursor size back to small and the changes were reflected immediately -- no restart. Awesome!

Oops, I take that back. The cursor changed for one command and then reverted back. Oh well, restart it is. :smile:

I changed the parameter to -ViModeIndicator [Cursor|StatusLine|None].  The default is None.


directive not work after url changes

Do you want to request a feature or report a bug?
bug*:
Directive $compile
What is the current behavior?
var $el = $(`
                <div
                    frm-element-attr-editor
                    element="element"
                    data="data"
                >
                </div>
            `);
        $('div[name="el_attr_editor_container"]').html($el);
        $timeout(function(){
            $compile($el)($scope);
        }, 0);

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).

a click button will render $scope's element, data value then recompile this directive.

firstly url history back, secondly url back to this page, click the button the directive not compiled.

I checked the scope contains '$$destroyed: true' attribute.

the directive compile and link function not being called.

What is the expected behavior?

directive should be compiled each time. when the function called.
after url changes then back to this url router. the directive should be compiled.

What is the motivation / use case for changing the behavior?
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Other information (e.g. stacktraces, related issues, suggestions how to fix)

directive like this
.directive('frmElementAttrEditor', ['$rootScope', function($rootScope){
    return {
        restrict: 'EACM',
        templateUrl: './static/templates/frm_elem_attrs_editor.html',
        scope: {
            element : '=',
            data: '='
        },
        compile: function(){
            return {
                pre: function (scope, iElement, iAttrs, controller) {
                },
                post: function ($scope, element, attrs) {
                    $scope.add_select_option = function(){
                        $scope.data.gcOptList.push({
                            'value': '',
                            'selected': true
                        });
                    };

                    $scope.remove_select_option = function(option){
                        _.remove($scope.data.gcOptList, function(n){
                            return n === option;
                        });
                    };

                    $scope.$watch('data', function(data){
                        var $element = $($scope.element);
                        for(var el_attr in data){
                            var el_attr_val = data[el_attr];
                            switch(el_attr) {
                                case 'gcCpnAlias':
                                    $element.children('h8').html(el_attr_val);
                                    break;
                                case 'gcCpnDisc':
                                    $element.children('div[name="el_desc"]').html(el_attr_val);
                                    break;
                                case 'gcDefVal':
                                    $element.children('div > input, div > textarea').val(el_attr_val);
                                    break;
                            }
                        }
                    }, true);
                }
            }
        }
    }
}])

compile function
function edit_attrs($element){
        var data = $element.data('data');
        $scope.element = $element;
        $scope.data = data;
        var $el = $(`
                <div
                    frm-element-attr-editor
                    element="element"
                    data="data"
                >
                </div>
            `);
        $('div[name="el_attr_editor_container"]').html($el);
        $timeout(function(){
            $compile($el)($scope);
        }, 0);
    }

is anyone can help me on this? Appreciate!

Hi,
If you think this is a bug in Angular, please create a minimal example in a plnkr.co or similar that shows the problem. If you have a question on how to build something, please try one of the listed Support Channels. Thanks!


[BEAM-9898] Move snowflake.py from apache_beam.io to apache_beam.io.external for backwards compatibility

The problem is that read has already been merged to the 2.24 RC and in there snowflake.py is in apache_beam.io.external while after write merge into 2.25 it was moved to apache_beam.io, as this is the preferred place to put cross-language ios.
There are 2 possibilities:

Move snowflake.py back to apache_beam.io.external
Make a redirect file with imports from apache_beam.io.snowflake and add a deprecation warning like in kafka.py

There are also changes to versions in CHANGES.md - cross-language Read and write dispositions were added in 2.24, not 2.23

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

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

@chamikaramj Could I ask you for review and for the decision what is the preferable approach? Move snowflake.py to .io.external or leave it in .io and do the same thing as for kafka.py?

Please keep this in apache_beam.io instead of apache_beam.io.external. There's not much value in differentiating cross-language IO connectors from other connectors. If you worry about backwards compatibility you can add a stub similar to https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/external/kafka.py
(also please make sure to add backwards compatibility warnings to all new transforms)

Please keep this in apache_beam.io instead of apache_beam.io.external. There's not much value in differentiating cross-language IO connectors from other connectors. If you worry about backwards compatibility you can add a stub similar to https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/external/kafka.py
(also please make sure to add backwards compatibility warnings to all new transforms)

If it will be impossible to move snowflake.py to apache_beam.io in RC-2.24.0 then I'll do as you suggested. But I keep my fingers crossed so we'll avoid deprecation warnings

Please keep this in apache_beam.io instead of apache_beam.io.external. There's not much value in differentiating cross-language IO connectors from other connectors. If you worry about backwards compatibility you can add a stub similar to https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/external/kafka.py

I added a stub like in kafka.py.

(also please make sure to add backwards compatibility warnings to all new transforms)

I'm not sure about this part. Is the warning in the stub file sufficient or should I add some warning with WriteToSnowflake also? I think that only ReadFromSnowflake requires that.

LGTM. Thanks.

Please resolve the conflict.

@chamikaramj Done

@chamikaramj  ping

Run Python PreCommit


Prevent entryCreateUser from being used when forbidClientAccountCreation is enabled

Even when forbidClientAccountCreation was enabled users could still be added from the client if you manually went to the /sign-up route, or by calling entryCreateUser from the console:
Meteor.call(
    'entryCreateUser',
    {email:'asdf@asdf.com',password:'asdfasdf1'},
    function(e){console.log(e);
});

This commit disables the entryCreateUser method when forbidClientAccountCreation is enabled.

Hey guy's. Any update on this PR? Functionality to prevent sign up's seems pretty vital.


remove comment

Remove a comment.

@dsyme, lol, I have a bunch more tweaks to do, but I guess I will do another PR now :-)

@KevinRansom The PR did what it said on the tin :)

I know, i ain't that imaginative.

So sorry 😅


BirthDeath.m tutorial example: Undefined function or variable 'generateLNA'.

>> BirthDeath
Undefined function or variable 'generateLNA'.

matlab or python?

matlab. for python it's there.

maybe generateLNAComponents.m?

Tried that one. But it expects additional arguments.

In python generateLNA calls generateLNAComponents, I guess the matlab version of the former is missing.

could be

@feigelman It would be great if you could assist.

Hi Jan,
I will try to take a look as soon as I have time.
Thanks
Justin
On Tue, Apr 17, 2018, 11:02 Jan Hasenauer<EMAIL_ADDRESS>wrote:

@feigelman https://github.com/feigelman It would be great if you could
assist.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ICB-DCM/LNAplusplus/issues/2#issuecomment-382086818,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADnEQYLptobx0oQnYRKswUYq6-VVnmgcks5tpi4wgaJpZM4TYr1b
.

Dear Justin,
it would be great if you could have a quick look if you find the file. (The submission deadline is already next week.)
Thanks, Jan

i included the file and some other. I hope that it works now.

Works now, thanks.


Proxy polyfill fix

Allows use of proxy polyfill library.
See issue #41.

Current coverage is 99.35% (diff: 95.45%)

Merging #65 into master will increase coverage by 0.04%

@@             master        #65   diff @@
==========================================
  Files             8          8
  Lines           143        154    +11
  Methods          35         36     +1
  Messages          0          0
  Branches         15         17     +2
==========================================
+ Hits            142        153    +11
  Misses            1          1
  Partials          0          0

Powered by Codecov. Last update 1439f0e...0fb15bc


code problem

Hi, thank you for your great work! I think the value of dim should be 2.
https://github.com/liuruiyang98/Jittor-MLP/blob/b86656b65cf5f18ba9eb760d1f7565ed95e7e96e/models_pytorch/hire_mlp.py#L113

Thanks for your care and correction, I made a mistake in the PyTorch :( but it was right in Jittor version.  Feel free to raise a PR if you would like, and let's continue to maintain Vision MLP together.


Add rules_erlang 3.1.0

https://github.com/rabbitmq/rules_erlang/releases/tag/3.1.0

@meteorcloudy should this be resubmitted or recreated due to the stable URLs topic?

@pjk25 I think alls rules_erlang URLs are already stable, so no need to be updated.


Fluent Validation Swagger Support

Is there a way to include fluent validation rules in swagger document object.

Please ignore this ticket. Wrong repo.


[WIP] FEAT: Make LoRA work with custom models

This is a basis for discussion and not yet ready to be merged.
There are surprisingly few changes necessary to make LoRA work with custom models. Those changes mostly revolve around attributes or methods that are present by default on transformers models but not necessarily on custom models, and many of those changes are only required for tests. This PR identifies those lines of code and fixes them so that they work with custom models without creating any backwards incompatibility for models that are already supported.
A new suite of tests is introduced that checks that LoRA works for various kinds of custom models.
In _test_inference_safetensors, I removed the layers_to_transform config setting, as layer indexing does not work with many custom models.
There are still some TODOs for this PR, or possible future PRs:

Some more tests need to be added
Some tests (those using conv layers) are failing and I'm not sure why, take a look at tests_failing.py
It could be useful to have an example and/or update the docs.
Layer indexing doesn't really work with custom models, except if they have a very specific naming pattern. I'll do a small refactor of layer indexing in a separate PR, perhaps this also enable it to work better with custom models.
Test if custom models also work with AdaLora (and IA³).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Let's maybe add few lines on the documentation to explain what it means that LoRA is supported for any model with a handy example snippet

Yes, I'll work on that.

Made also: BenjaminBossan#1 that should unlock the issues with Conv1D layers

Great, this fixed the issues in test_failing.py. There are some more failing tests when conv layers are used, but they're probably unrelated, I'll investigate and get back once I know what's going on.

Can you add few lines in the documentation about this feature? It could live in the lora section. It can be also done in a follow up PR

Yes, I'd like to add some docs and examples. Still, I would like to ensure that everything works well before merging, so my preference is to deliver the docs and examples first, as new issues could surface. That means it's not going to be ready if we want to release today, but I think that's fine.

Can you add few lines in the documentation about this feature? It could live in the lora section. It can be also done in a follow up PR

Yes, I'd like to add some docs and examples. Still, I would like to ensure that everything works well before merging, so my preference is to deliver the docs and examples first, as new issues could surface. That means it's not going to be ready if we want to release today, but I think that's fine.

May I ask if the current model can be used for custom models? After fine-tuning using the custom model with the addition of Lora module, the model still reports an error in dropout

May I ask if the current model can be used for custom models?

It should work now, here is an example notebook: https://github.com/BenjaminBossan/peft/blob/DOC-custom-models/examples/multilayer_perceptron/multilayer_perceptron_lora.ipynb

After fine-tuning using the custom model with the addition of Lora module, the model still reports an error in dropout

Could you provide some code to produce that error?

This is a basis for discussion and not yet ready to be merged.
There are surprisingly few changes necessary to make LoRA work with custom models. Those changes mostly revolve around attributes or methods that are present by default on transformers models but not necessarily on custom models, and many of those changes are only required for tests. This PR identifies those lines of code and fixes them so that they work with custom models without creating any backwards incompatibility for models that are already supported.
A new suite of tests is introduced that checks that LoRA works for various kinds of custom models.
In _test_inference_safetensors, I removed the layers_to_transform config setting, as layer indexing does not work with many custom models.
There are still some TODOs for this PR, or possible future PRs:

Some more tests need to be added
Some tests (those using conv layers) are failing and I'm not sure why, take a look at tests_failing.py
It could be useful to have an example and/or update the docs.
Layer indexing doesn't really work with custom models, except if they have a very specific naming pattern. I'll do a small refactor of layer indexing in a separate PR, perhaps this also enable it to work better with custom models.
Test if custom models also work with AdaLora (and IA³).

Also fixes #365

I would like to use PEFT to fine tune the Adaspech model, but I noticed that after adding PEFT code, print (model. base_model. model. module. speaker_emb. ora_embedding. A) outputs all 0 matrices, which means that this part did not participate in training. This is part of my code. May I ask where the problem is with me?
`
Prepare model
model, optimizer = load_pretrain(args, configs, device, train=True)
model = nn.DataParallel(model)
model = model.to(device)
peft_config = peft.LoraConfig(
    r=8,
    target_modules=["module.speaker_emb"])
model = peft.get_peft_model(model, peft_config)
model.print_trainable_parameters()
num_param = get_param_num(model)
Loss = AdaSpeechLoss(preprocess_config, model_config).to(device)

`
when i input this code：
‘print(model.base_model.model.module.speaker_emb.lora_embedding_A) ’
it always output that：
parameterDict(  (default): Parameter containing: [torch.cuda.FloatTensor of size 8x174 (GPU 0)])
Its value will not be updated


python311Packages.rioxarray: 0.15.5 -> 0.15.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.rioxarray is: geospatial xarray extension powered by rasterio
meta.homepage for python311Packages.rioxarray is: https://corteva.github.io/rioxarray/
meta.changelog for python311Packages.rioxarray is: https://github.com/corteva/rioxarray/releases/tag/0.15.7
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.7 with grep in /nix/store/xnyz9akv2sh5qpwakvn4xp16p8c8y8d5-python3.11-rioxarray-0.15.7
found 0.15.7 in filename of file in /nix/store/xnyz9akv2sh5qpwakvn4xp16p8c8y8d5-python3.11-rioxarray-0.15.7

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.rio-tiler
python311Packages.rioxarray
python312Packages.rio-tiler
python312Packages.rioxarray

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xnyz9akv2sh5qpwakvn4xp16p8c8y8d5-python3.11-rioxarray-0.15.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.rioxarray https://github.com/r-ryantm/nixpkgs/archive/cb59bc06e95e4c259212611bcaa960e4a81adca7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cb59bc06e95e4c259212611bcaa960e4a81adca7#python311Packages.rioxarray

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xnyz9akv2sh5qpwakvn4xp16p8c8y8d5-python3.11-rioxarray-0.15.7
ls -la /nix/store/xnyz9akv2sh5qpwakvn4xp16p8c8y8d5-python3.11-rioxarray-0.15.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages built:

python311Packages.rio-tiler
python311Packages.rio-tiler.dist
python311Packages.rioxarray
python311Packages.rioxarray.dist
python312Packages.rio-tiler
python312Packages.rio-tiler.dist
python312Packages.rioxarray
python312Packages.rioxarray.dist

Maintainer pings
cc @imincik @l0b0 @nh2 @nialov @sikmir @willcohen for testing.

Result of nixpkgs-review pr 322757 run on x86_64-darwin 1

8 packages built:

python311Packages.rio-tiler
python311Packages.rio-tiler.dist
python311Packages.rioxarray
python311Packages.rioxarray.dist
python312Packages.rio-tiler
python312Packages.rio-tiler.dist
python312Packages.rioxarray
python312Packages.rioxarray.dist

Result of nixpkgs-review pr 322757 run on x86_64-linux 1

8 packages built:

python311Packages.rio-tiler
python311Packages.rio-tiler.dist
python311Packages.rioxarray
python311Packages.rioxarray.dist
python312Packages.rio-tiler
python312Packages.rio-tiler.dist
python312Packages.rioxarray
python312Packages.rioxarray.dist


npm package not updated

Version 3.0 isn't published to npm

@germanattanasio any updates? I'd like to play with the v3 support

Hey I just pushed the package to npm. Sorry for the delay


Add external crate http_service_mock, delete local TestBackend

This solves ust-net-web/tide#15. We wanted to extract the HttpBackend inside the tests, and offer it inside the http-service create (https://github.com/rust-net-web/http-service/pull/6).
Description
I removed the HttpBackend from the wildcard.rs tests, and used the external crate (which needs to be merged and pushed first inside http-service).
Motivation and Context
After the change, we are able to offer a TestBackend which is not tied to Tide.
How Has This Been Tested?
The PR in http-service needs to be merged first. I tested it locally and it ran fine.
Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Ping @tirr-c Tests are passing


Change sample text ability

Please provide sample text in settings to change for other languages

Please provide sample text in settings to change for other languages

Are there any specific languages you were thinking of?

Gonna close this since it was addressed in version 1.1.2 (c3b373624dde75fb388fc1c306260c256b21e327) but I'm always open to more suggestions!


Action Handler

How to handle the file which is chosen is not known, pl. provide sample which could push the file selected to server

I'm going to close this since we've neglected it for a while :/
You can look at Charles blog post about functional templating. emberx-file-input is just one component of many needed to create an upload workflow. http://frontside.io/blog/2016/01/22/functional-templating-in-ember.html
Let me know if you have any questions. I promise I won't wait months to reply :(


[#141423205] Use ACM to create a real cert for concourse.

What
This uses Amazon Certificate Manager to create a valid signed cert to use for the concourse instance this deploys.
How to review
🚨  Note: this depends on https://github.gds/government-paas/aws-account-wide-terraform/pull/91

Run the bootstrap pipeline from this branch.
The cf-terraform job will create a certificate request, and then pause waiting for it to be approved.
Persuade someone on the paas-domain-admins list (currently @alext, @dcarley and @timmow) to approve the certificate request.
Observe the pipeline continue and update the concourse to use this cert.
Verify that your concourse now has a valid cert (Note: chrome seems to cache SSL connections, so it may require a restart/incognito mode to pickup the change).

You could also test that the destroy pipeline works correctly and cleans up the cert.
Who can review
Not me.

Running bootstrap on top of existing deployer works. Chrome has some caching issues with certs and needs to be restarted to notice new one. I'm going to destroy deployer now and test whether this works while creating deployer from scratch.


how to set width and height, now it default 200px

now width and height default 200px, how to set it?

You can pass style or className — same way you would style any other React element.
See https://github.com/okonet/react-dropzone/blob/gh-pages/browser.js for example.

I'd also prefer to keep this issue tracker for issues, not questions. If you have questions, please ask them on StackOverflow.