Transpose ES5 => ES6

Fixes #3

It looks like the build with this PR fails unexpectedly. I don't know why. I'm going to try some local testing.

Hello James!
Thanks for your pull request. It would be great if you can check tests and update if needed, as you can see the error log from the details.
./src/morsify.js: line 1, col 1, Use the function form of "use strict".
./src/morsify.js: line 3, col 70, Invalid typeof value 'symbol'
./src/morsify.js: line 13, col 38, Unmatched '{'.

Also, you may use arrow functions and replace var declarations with const or let.
Thank you.

I’m heading out soon, but I will fix these issues ASAP!

It is OK, thank you :)

I was wondering, where are you finding this additional error information?

Ok, Travis CI build is passing! I'll go add some arrow functions! (also, I'm not sure if any of the variables are changed globally, or need to be changed at all. Which ones should be const vs let?)

I reverted what I did because they were throwing errors. I don't know much about arrow functions, but I'll research them later when I have the time so I can help convert some of the functions. Tests should be passing now.

What you changed was OK actually, you need to make those changes again, however, you also need to configure the project so that it will pass the tests.
See this log line for instance.
./src/morsify.js: line 12, col 3, 'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

You need to declare that you are using ES6, to do that, add a JSHint file, .jshintrc, with the contents o
{
  "esversion": 6
}

Sorry James, someone has done all the changes here before you, thank you for all of your efforts.

Glad that it worked out!


Assertion Failed: A helper named 'mut' could not be found

Not working with ember 1.10.0 version.
It gives the errors

Assertion Failed: A helper named 'mut' could not be found
for (action (mut time4))

Uncaught TypeError: this.getAttr is not a function
inputGroupClass: computed('attrs.noIcon', function () {
if (!this.getAttr('noIcon')) {
return 'input-group';
}

Master is not compatible with < 1.13

Could we install a prior version compatible with ember versions less than 1.13?


dragging and dropping to other apps

With the exception of File Explorer (explorer.exe), other apps can not accept drag and drop operations of files from Files window.
I tested this and the file type is shown as "Files.Filesystem.StorageItems.SystemStorageFile" type

Is there any way to maybe expose this as a "StorageFile" type?

What app version are you testing?

I'm using the latest version in the store, and the code is from an app I'm developing

I'm using the latest version in the store

Could you confirm which version is that? (is it the insider version or the latest public version 2.0.13?)

Versión: <IP_ADDRESS>
OS Version: 10.0.22489.1000

Indeed it looks like we provide "normal" storage items on Copy/Paste but not Drag/Drop.

@TyJOrtiz when you mention "other apps" is it just your app or did you find others for which drag/drop from Files does not work? E.g in my testing dropping to Edge works.

Dragging to Snip & Sketch doesnt work for example, I can drag images from Explorer.exe to there

Thanks for pointing this out!


Customizing keyboard layouts

Need to consider the possibility that users will need to customize keyboard layouts of the physical keyboard.
Perhaps offer the keyboard keycaps as a module that can be snapped into the design. The downside of this is that the snaps/screws to support this in a robust fashion will add a considerable amount of thickness/size to the design.

I believe a keyboard as the absolutely major input for any digital device is quite a sensitive topic (you might have already come across that with Novena).
It seems to me there will be a need to differentiate not just caps (i.e. visual layout), but also mechanical layout might need to be fully swappable - to account for the differences between the most widespread ones (as outlined in the wikipedia article) as well as for e.g. the otho-linear (aka "matrix") mechanical layout or special layouts like Lingo Splix Board.
Btw I believe the solution of Novena is an excellent one - "here you have a hole and place the keyboard and keys inside the way you like".

The trade-off of a modular keyboard is it'll increase the size footprint of the device. For example, if the device could be say, 3.5mm thick, but with a modular keyboard it'd have to be 5.5mm thick, plus add about 4mm to width and height, would users accept that? obviously the impact is primarily felt on the thickness, but I worry users will tend to judge a device more by aesthetics and metrics that are less related to utility such as a swappable keyboard.

My words.
My idea could be summed up to "do not make the design modular, but make the design in a way, that a little effort will be needed to support other mechanical layouts even if you have limited conditions" (e.g. do the keyboard part of the device so much mechanically simple, that every buyer could print it's own variant on a 3D printer (and connect the keys/touch_foil/touch_screen to the same existing PCB) to accommodate the different needs.

That makes sense. I'll take the suggestion into consideration. thanks.

I just wanted to say I am very happy that the device will be coming with dvorak layout, I believe it is the most effective for thumb typing of any layout.

I reference here horizontal keyboard hardware possible benefit: https://github.com/betrusted-io/betrusted-wiki/issues/13#issuecomment-1072018384
thank you so much for your work and consideration


Should I put a space in between a heading that was split?

I'm annotating some fulltext training data and came across an instance that makes me question what will alter the stream of text or not.
I have the following block of data after generating training data:
3.2.1 (U) Staffing

Criteria<lb/>
Each are on separate lines in the file.
"Criteria" should be in the head section after "Staffing" but there is no space between  and
. There is a space in the header of the actual PDF but im not sure if the fixed annotation should be 3.2.1 (U) StaffingCriteria or 3.2.1 (U) Staffing Criteria.
Any thoughts?

Hi @mneis1  !
In the generated training data, an end of line is equivalent to a space. And the two tokens should be separated to introduce a new label. So 3.2.1 (U) Staffing Criteria should be the right one.

Thanks so much @kermitt2 ! I really appreciate your help.
Just to clarify, does adding more breaks between labels affect the amount of spaces? For instance, does:

test

string

and

test

  (ignore the space just imagine this is a new line)

string

and

test

   (ignore the space just imagine this is a new line)
   (ignore the space just imagine this is a new line)

string

all equal the string "test string" with one space or will 2 and 3 have extra spaces?
Also is there anything wrong with ending the label on a new line? Like:

test

Once again, thanks for all your help!

You're very welcome @mneis1 !
Adding more space or end of line in the training XML files has no impact. They are all seen as one delimiter. So you can introduce EOL/spaces to improve readability.
The training file is simply used to align tokens with the feature file and get a label (with the XML mark-up).
The actual layout information, delimiters, space, etc. are all captured in the feature files that come with the TEI for training.
The idea is that the TEI file captures the labellng information that is stable over time. The feature files capture all the rest and can be updated each time we add/change features or improve pdfalto to better extract tokens and layout information (for instance usually there is no space character in a PDF, they are introduced by the PDF parser that tries to detect token delimiters based on font size and positions).

Thanks! Thats a huge help!


python37Packages.mss: 6.0.0 -> 6.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.mss is: "Cross-platform multiple screenshots module in pure Python"
meta.homepage for python37Packages.mss is: "https://github.com/BoboTiG/mss/"
meta.changelog for python37Packages.mss is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.1.0 with grep in /nix/store/fdvn16bzaxx0qafjb3y2ad2bm0659f6w-python3.7-mss-6.1.0

directory tree listing: https://gist.github.com/af088a2974ecfe0cde301ad07f2f2272

du listing: https://gist.github.com/44dac1de5ecc17ae85c7cca8e8a4a008

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

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python37Packages.mss
python37Packages.pyscreenshot
python38Packages.mss
python38Packages.pyscreenshot

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fdvn16bzaxx0qafjb3y2ad2bm0659f6w-python3.7-mss-6.1.0 \
  --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 python37Packages.mss https://github.com/r-ryantm/nixpkgs/archive/121c822eabb5949abb72a94753d7014f26c35265.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fdvn16bzaxx0qafjb3y2ad2bm0659f6w-python3.7-mss-6.1.0
ls -la /nix/store/fdvn16bzaxx0qafjb3y2ad2bm0659f6w-python3.7-mss-6.1.0/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 1

4 packages built:

python37Packages.mss
python37Packages.pyscreenshot
python38Packages.mss
python38Packages.pyscreenshot

Maintainer pings
cc @austinbutler for testing.

@ofborg eval


Change 'Caveat emptor' to 'Caveat usor'

I really should have made an alt account to raise this issue... But it was annoying my OCD! :P

While not technically correct, "caveat emptor" is the common phrase, which I've seen used in this situation as well


Please update iOS building procedure to cmake 3.14

Starting from cmake 3.14.0 there is native support for iOS:
https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos
Building with CMake for iOS
https://github.com/firebase/firebase-cpp-sdk/blob/master/README.md#building-with-cmake-for-ios
Should not require  -DCMAKE_TOOLCHAIN_FILE=../cmake/ios.cmake with CMake 3.14 and above

@crazyhappygame the min cmake version we support is 3.1, we're happy to accept pull requests if this can be applied conditionally.


30 Day not registered

Not at all super urgent, but when a cat is marked adopted, and 30 days have passed. Alert the system if the cat has not been registered yet.

Notification System needed.


OSGeo-Live project maintainer is needed

we from OSGeo-Live project tried to contact the OpenLayers project
the are looking for a new maintainer for OL on OSGeo-Live

work to do:

decide which version to put on OSGeo-Live version
update OL version in sh https://github.com/astroidex/OSGeoLive/blob/master/bin/install_openlayers.sh
update documentation
** https://github.com/OSGeo/OSGeoLive-doc/blob/master/en/overview/openlayers_overview.rst
** https://github.com/OSGeo/OSGeoLive-doc/blob/master/en/quickstart/openlayers_quickstart.rst
** version https://github.com/OSGeo/OSGeoLive-doc/blob/master/conf.py

Please volunteer.

hey Astrid, how did you try to contact before this attempt? I will look at your request today. Can I just PR on osgeolive repo?
Sent from my iPhone

On 29 May 2017, at 23:25, Astrid Emde<EMAIL_ADDRESS>wrote:
we from OSGeo-Live project tried to contact the OpenLayers project
the are looking for a new maintainer for OL on OSGeo-Live
work to do:
decide which version to put on OSGeo-Live version
update OL version in sh https://github.com/astroidex/OSGeoLive/blob/master/bin/install_openlayers.sh
update documentation
** https://github.com/OSGeo/OSGeoLive-doc/blob/master/en/overview/openlayers_overview.rst
** https://github.com/OSGeo/OSGeoLive-doc/blob/master/en/quickstart/openlayers_quickstart.rst
** version https://github.com/OSGeo/OSGeoLive-doc/blob/master/conf.py
Please volunteer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes - pull request would be fine see http://wiki.osgeo.org/wiki/Live_GIS_Disc#Git_migration
bartvde - would be great if we could add you as contact person.

how did you try to contact before this attempt?

@astroidex wrote to me personally, and I failed to even respond. Mea culpa, @astroidex, your mail was marked important, but somehow I ignored it for quite a while. Sorry.
Ping me again if there is additional help you need. I won't be available to work as official contact person. but will help when time permits it.

@astroidex do you or anyone else know what the legacy projects are that need openlayers 2 on the OSGeo Live?
and OpenLayers 2.13.1 for legacy demos in OSGeoLive

since ideally I'd like to get rid of openlayers 2 on the OSGeo live and only use the latest stable (so 4.1.1)

ah I found one here: https://github.com/OSGeo/OSGeoLive/blob/aaec0fddf95fd5ebf6b1af19dad41719075e9b15/app-conf/mapnik/local.html#L21

but that seems to be the only one as far as I can tell

would be great to have OpenLayer 4.x installed.

please have a look at the package list and update OpenLayers to the version you will install
https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit?hl=en_GB#gid=2014800150

@astroidex PR for OSGeoLive and OSGeoLive-docs opened. Updated the spreadsheet as well with the version, but not as yet the field 11.0 comment. I'm happy to be point of contact going forward.

great! Thanks @bartvde

Please add yourself to the following file too https://github.com/OSGeo/OSGeoLive-doc/blob/master/contributors.csv
Then you will show up in the list https://live.osgeo.org/en/sponsors.html

thanks for the pointer, done in the PR


Device specific "tap" or "click?"

I realized that we have the ability to use specific language for specific devices, i.e. show "Tap" to mobile users, and "click" to desktop users, with docassemble's device(). It uses user agent strings, so it's not perfect (won't handle when people use bluetooth mice on tablets, or a touch enabled laptop), but it's better than we do now, and can still use the general "tap" for devices we don't know about.
The only existing convo I can find about this is https://github.com/SuffolkLITLab/docassemble-MAVirtualCourt/issues/232, but I'm not sure if we've had this conversation before.

TBH, we used "tap" but I think nobody is really familiar with that term and I kind of hate it every time I see it. I think people are used to seeing "click" even for an action they do with their finger on a touch screen.

FWIW I did run across this opinion piece randomly: https://www.learningtoo.eu/articles/writing-for-ux-click-or-tap.htm


#112 - don't extend sync line of suites

this allows implementing specs to use either sync or async suites

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

wanted to get this up for discussion - this should allow users to make use of either sync or async tests, but there is one notable change in behavior:
Using testOnly **ChromeExampleSpec* as an example (without the chrome driver set up)
Previously, a failure to start up web driver for the Browser line would report as a cancelled test and the test run would succeed, such as
[info] Run completed in 3 seconds, 775 milliseconds.
[info] Total number of tests run: 0
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 0, failed 0, canceled 5, ignored 0, pending 0
[info] No tests were executed.
[info] Passed: Total 0, Failed 0, Errors 0, Passed 0, Canceled 5
[success] Total time: 4 s, completed Apr 25, 2020 3:08:35 AM

with this change, it would show up as an aborted suite and the test run would fail:
[info] ScalaTest
[info] Run completed in 3 seconds, 751 milliseconds.
[info] Total number of tests run: 0
[info] Suites: completed 0, aborted 1
[info] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[info] *** 1 SUITE ABORTED ***
[error] Error: Total 1, Failed 0, Errors 1, Passed 0
[error] Error during tests:
[error] 	org.scalatestplus.play.examples.guice.onebrowserpersuite.ChromeExampleSpec
[error] (scalatestplus-play / Test / testOnly) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 9 s, completed Apr 25, 2020 3:23:56 AM

This can be observed on the Travis CI builds for the PR - the Safari/IE tests were previously showing up as canceled due to being unable to create a webdriver - but are now aborted and failing the build (tests previously not working, but are now aborted->failure rather than cancelled->success)
There could be different mindsets on whether that's a good or bad thing - but it is a change in behavior, so looking for feedback on whether that's acceptable before continuing on.  If so, I think there could be a follow up to switch PerSuites over to use BeforeAndAfterAll, to address #111

I like the change, perhaps we should add a switch to disable tests that rely on webdriver so they can be explicitly cancelled when running on a system that doesn't have the browsers installed?

that could work.  also found another option.  it's a bit hacky, but overriding testDataFor will allow the cancellation to keep the previous behavior
override def testDataFor(testName: String, theConfigMap: ConfigMap = ConfigMap.empty): TestData = createTestDataFor(testName, theConfigMap, this)

happy to either:

revert the browser specs back, so that at least the base app/server line is decoupled from sync
put the testDataFor override in, to maintain behavior for the browser specs

any preference?

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

for now, I've reverted the browser specs back.  so this PR in total, for app/server fixtures:

allows use of sync or async (#112)
uses BeforeAndAfterEach for PerTest and BeforeAndAfterAll for PerSuite for lifecycle start/stop

defers creation of app/server unless the test will actually run (so won't happen if excluded via tags)
throws exception rather than creating app/server "outside" of a test/suite execution
allows specs to hook onto to BeforeAndAfterEach/BeforeAndAfterAll for setup/cleanup (#111 and #121 )

aborts the full suite for PerTest if the app/server can't be created, rather than trying once per test and failing each individually

another issue popped up - this currently breaks the previous behavior for using ParallelTestExecution with PerSuite, like extends OneAppPerSuite with ParallelTestExecution
before: results in an app/server being created per test (perhaps surprising behavior, was to us)
after: results in an exception/null
what's the intended behavior?

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

Not being allowed to use either sync or async suites has bothered me for so long. Oh I would so love to get this change outthere.

I've signed the CLA (a few times) - don't know why it hasn't picked it up
If someone can lend some guidance on what to do with the MIMA errors, would be happy to fix them up

I've signed the CLA (a few times) - don't know why it hasn't picked it up

The signature for github user 'kwinter' was indeed recorded, but the commits have<EMAIL_ADDRESS>as the email address for the Author file, and that email address isn't associated with your GitHub account. You can associate additional email addresses as documented at https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account

If someone can lend some guidance on what to do with the MIMA errors, would be happy to fix them up

Hmm, that looks pretty tricky: AFAICS these changes are binary incompatible "by design", the whole point of the PR is to no longer extend the things that were extended before.
I wonder what binary compatibility guarantees we have promised for this project though - we tend to be a bit less strict in projects that are only used in test scope. Perhaps someone more intimately familiar with the project can say something about that?

Any updates on this ? I need it !

I've associated the commit email with my account - so that's hopefully good to go
I think that just leaves the binary compatibility issue from MIMA, and guidance on what we want to do there


WIP [SPARK-12172][SPARKR] Remove internal-only RDD methods

What changes were proposed in this pull request?
Remove non-public internal only methods for RDD in SparkR
How was this patch tested?
Jenkins

Test build #98148 has started for PR 22866 at commit b16de30.

Test build #98148 has finished for PR 22866 at commit b16de30.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98148/
Test FAILed.

Merged build finished. Test FAILed.

Test build #98149 has started for PR 22866 at commit 78f47e8.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4563/
Test FAILed.

Test build #98149 has finished for PR 22866 at commit 78f47e8.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98149/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4564/
Test PASSed.

Test build #98150 has started for PR 22866 at commit ba37a8a.

Test build #98150 has finished for PR 22866 at commit ba37a8a.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98150/
Test FAILed.

Test build #98152 has finished for PR 22866 at commit 6fc37f2.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98152/
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4567/
Test PASSed.

Test build #98153 has started for PR 22866 at commit 00ae00a.

Test build #98153 has finished for PR 22866 at commit 00ae00a.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98153/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4930/
Test PASSed.

Test build #98703 has finished for PR 22866 at commit d1f622e.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98703/
Test FAILed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/15732/
Test PASSed.

@felixcheung where did you end up on this one?

sorry, didn't get a chance to follow up. Since this is a big change, I might need to revert part of it to see what is leading to some implicit type conversion type of problem, IIRC. I will try to get back in a week.

Hi, @felixcheung . Do you think we can have this at 3.0.0~?


Query parameter not bound if method parameter has same name as property

If the parameter name in the method is the same as the property beeing bound via query string it doesn't work. If I prefix the query string key then the value is parsed correctly
Question: Should/can the [FromQuery] attribute be used on a property to indicate that it should use that name instead of the property name when creating the query string?
E.g. [FromQuery(Name = "q")]public string SomeReallyLongPropertyName { get; set; } would generate http://github.com/aspnet/Mvc?q=work?
Attaching a solution where the issue and the question is present.
Thank
AspNetCoreMVcBugs.zip

@rynowak can you take a look at this?

This is MVC's prefix detection logic in action.
When MVC sees a parameter like public IActionResult HelloNameWorks([FromQuery] HelloViewModel hello)...
It tries first to see if a key was provided for hello.  If it finds one then it will try to bind hello.FirstName, hello.LastName, etc for all of the properties on HelloViewModel - in your case it's going to look for hello.Hello.  Using a property name with the same name as the parameter will almost always do the wrong thing due to how this feature behaves.
You can can fix your specific issue by using [ModelBinder(Prefix="")] or [FromQuery(Name="")] on the parameter to force it to look for Hello from the query string instead of hello.Hello.

@Eilon - this is not a bug, but it's a good candidate for more logging and an analyzer.

Ok I added this to our tracking item for future analyzers. Beyond that, this issue is currently by-design.


[automation] Introduce flexible loop in deploy-edpm.yml

Consuming architecture automation, this patch, with the rest of the
"[automation]" related patches, will allow to deploy VAs directly by
running the deploy-edpm.yml playbook.
Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/1168
As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] Content of the docs/source is reflecting the changes

/test all

recheck

/approve

/hold
/lgtm

/hold cancel


FileNotFoundError even when hardcoding the correct directory

my conda version:
          conda version : 24.7.1
    conda-build version : not installed
         python version : 3.10.14.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=24.7.1=0
                          __cuda=12.5=0
                          __glibc=2.40=0
                          __linux=6.10.3=0
                          __unix=0=0

command:
new-conda-env -old_ver 3.11.9 -new_ver 3.12.5 -env_to_clone retirement_algo -new_env_name ralgo
error:
/mnt/legacy/home/kng_kapital/miniforge3/envs/retirement_algo/envs
new_conda_env.envir.CondaEnvir: ERROR    Typo in <env_to_clone>? Path not found: /mnt/legacy/home/kng_kapital/miniforge3/envs/retirement_algo/envs/retirement_algo)
Traceback (most recent call last):
  File "/mnt/legacy/home/kng_kapital/miniforge3/envs/retirement_algo/bin/new-conda-env", line 10, in <module>
    sys.exit(main())
             ^^^^^^
  File "/mnt/legacy/home/kng_kapital/miniforge3/envs/retirement_algo/lib/python3.11/site-packages/new_conda_env/cli.py", line 126, in main
    conda_vir = envir.CondaEnvir(old_ver=o_ver,
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/legacy/home/kng_kapital/miniforge3/envs/retirement_algo/lib/python3.11/site-packages/new_conda_env/envir.py", line 112, in __init__
    raise FileNotFoundError
FileNotFoundError

The Paths don't appear to be correct. It duplicates envs/retirement_algo so I tried to hardcode the correct path just as a test and it generated another error further down the chain.

Sorry about that!
I found an error a couple of months ago (might be the same one): I have not gotten around to fixing it.

There have been a lot of changes on the conda side...
I'll try to dig into it before the end of the week.

PS: I mask the irrelevant (& private) paths from all tracebacks, when I post in a public forum.


Unable to create new projects using Nuxt Hub Team

Describe the bug
We are unable to create new projects from the Nuxt Hub within a team.
When we try to create a new project, we get a 400 error:

These are the changes we have made in our team:

I and another team member are in the team. I am the owner, everything works as expected.

I am invited to another account in Cloudflare. I get limited access to this new account, so that I can only create pages, not other types of instances.

I change the API token in NuxtHub to connect to the Cloudflare account.

I try to create a new instance, but it fails. At this point I thought it might be due to my limited access in Cloudflare.

I remove the other team member from my Nuxt Hub team.

I add a new team member to the Nuxt Hub team. This member is the same person who controls the account in Cloudflare.

I make him an admin

He tries to initialise the project, but we keep seeing the same error.

We have tried deploying several Nuxt applications but they all seem to return the same error.

UPDATED:

The admin has tried to create also project using his private account and gives the same error.

I am not sure what other context to give or what other information might be important, so please let me know if you want us to try something new.
Thanks in advance!

Hi @onmax
What is the error message from the API call?

I have also updated the issue context with the following

The admin has tried to create also project using his private account and gives the same error.

Ok. Now it works. But not sure why it was failing. Here are some reasons:

In my private Cloudflare account I had projects with the same name. I deleted them.
When recreating the token in the Cloudflare Dashboard I have the option to "Include" the accounts. we were selecting always the account of my coworker, but I have changed it to "All accounts" and used that token instead. Then in NuxtHub Admin, I selected my coworkers' account.

Closing this issue now since we are able to create projects.
Thank you!


Update to rust master

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

 @bors r=alexcrichton 50c6eb4

@bors: r+

:hourglass: Testing commit 50c6eb4 with merge 2ed3138...

:broken_heart: Test failed - cargo-win-32

@bors: retyr

@bors: retry

:hourglass: Testing commit 50c6eb4 with merge cf4af09...

:broken_heart: Test failed - cargo-win-32

@bors: retry force

@bors: force

:zap: Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64 are reusable. Rebuilding only cargo-win-32, cargo-win-64...

@bors: retry clean force

:hourglass: Testing commit 50c6eb4 with merge 9b46b9b...

:broken_heart: Test failed - cargo-win-64

@bors: retry
On Wed, Mar 18, 2015 at 10:49 AM, bors<EMAIL_ADDRESS>wrote:

[image: :broken_heart:] Test failed - cargo-win-64
http://buildbot.rust-lang.org/builders/cargo-win-64/builds/540
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1428#issuecomment-83088721.

:zap: Previous build results for cargo-mac-32, cargo-mac-64 are reusable. Rebuilding only cargo-linux-32, cargo-linux-64, cargo-win-32, cargo-win-64...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


create  bridge with existing name returns 201 created  instead of 409 conflict

Steps:

Create bridge (B1)
Create another bridge (B2) with same name as (B1)

Issue
Create (B2) return 201 created instead of 409 conflict

https://github.com/zero-os/0-orchestrator/issues/266


SBT 0.13.9 launcher won't resolve SBT

I downloaded sbt as described on the download page and installed it on an OS that has never seen SBT before. It then has trouble resolving itself when started in an empty folder. This is not a problem with getting a project to work or using sbt.
sudo apt-get install sbt works but sbt subsequently doesn't
Here's how the error looks:
tormod@tormod-desktop:~$ sbt
Getting org.scala-sbt sbt 0.13.9 ...

:: problems summary ::
:::: WARNINGS
        module not found: org.scala-sbt#sbt;0.13.9

    ==== local: tried

      /home/tormod/.ivy2/local/org.scala-sbt/sbt/0.13.9/ivys/ivy.xml

      -- artifact org.scala-sbt#sbt;0.13.9!sbt.jar:

      /home/tormod/.ivy2/local/org.scala-sbt/sbt/0.13.9/jars/sbt.jar

    ==== jcenter: tried

      https://jcenter.bintray.com/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.pom

      -- artifact org.scala-sbt#sbt;0.13.9!sbt.jar:

      https://jcenter.bintray.com/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.jar

    ==== typesafe-ivy-releases: tried

      https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.9/ivys/ivy.xml

    ==== Maven Central: tried

      https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.pom

      -- artifact org.scala-sbt#sbt;0.13.9!sbt.jar:

      https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.jar

        ::::::::::::::::::::::::::::::::::::::::::::::

        ::          UNRESOLVED DEPENDENCIES         ::

        ::::::::::::::::::::::::::::::::::::::::::::::

        :: org.scala-sbt#sbt;0.13.9: not found

        ::::::::::::::::::::::::::::::::::::::::::::::

:::: ERRORS
    Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://jcenter.bintray.com/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.pom

    Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://jcenter.bintray.com/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.jar

    Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.9/ivys/ivy.xml

    Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.pom

    Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.9/sbt-0.13.9.jar

:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.scala-sbt#sbt;0.13.9: not found
Error during sbt execution: Error retrieving required libraries
  (see /home/tormod/.sbt/boot/update.log for complete log)
Error: Could not retrieve sbt 0.13.9

I've installed 0.13.5 and it's problem-free so far.

what does the launch script look like?
can you still reproduce the problem if you bypass the installed launch script and just run java on the launcher jar directly?

This is /usr/bin/sbt:
#!/usr/bin/env bash

###  ------------------------------- ###
###  Helper methods for BASH scripts ###
###  ------------------------------- ###

realpath () {
(
  TARGET_FILE="$1"
  FIX_CYGPATH="$2"

  cd "$(dirname "$TARGET_FILE")"
  TARGET_FILE=$(basename "$TARGET_FILE")

  COUNT=0
  while [ -L "$TARGET_FILE" -a $COUNT -lt 100 ]
  do
      TARGET_FILE=$(readlink "$TARGET_FILE")
      cd "$(dirname "$TARGET_FILE")"
      TARGET_FILE=$(basename "$TARGET_FILE")
      COUNT=$(($COUNT + 1))
  done

  # make sure we grab the actual windows path, instead of cygwin's path.
  if [[ "x$FIX_CYGPATH" != "x" ]]; then
    echo "$(cygwinpath "$(pwd -P)/$TARGET_FILE")"
  else
    echo "$(pwd -P)/$TARGET_FILE"
  fi
)
}

# Uses uname to detect if we're in the odd cygwin environment.
is_cygwin() {
  local os=$(uname -s)
  case "$os" in
    CYGWIN*) return 0 ;;
    *)  return 1 ;;
  esac
}

# TODO - Use nicer bash-isms here.
CYGWIN_FLAG=$(if is_cygwin; then echo true; else echo false; fi)

# This can fix cygwin style /cygdrive paths so we get the
# windows style paths.
cygwinpath() {
  local file="$1"
  if [[ "$CYGWIN_FLAG" == "true" ]]; then
    echo $(cygpath -w $file)
  else
    echo $file
  fi
}

. "$(dirname "$(realpath "$0")")/sbt-launch-lib.bash"

declare -r noshare_opts="-Dsbt.global.base=project/.sbtboot -Dsbt.boot.directory=project/.boot -Dsbt.ivy.home=project/.ivy"
declare -r sbt_opts_file=".sbtopts"
declare -r etc_sbt_opts_file="${sbt_home}/conf/sbtopts"
declare -r win_sbt_opts_file="${sbt_home}/conf/sbtconfig.txt"

usage() {
 cat <<EOM
Usage: $script_name [options]

  -h | -help         print this message
  -v | -verbose      this runner is chattier
  -d | -debug        set sbt log level to debug
  -no-colors         disable ANSI color codes
  -sbt-create        start sbt even if current directory contains no sbt project
  -sbt-dir   <path>  path to global settings/plugins directory (default: ~/.sbt)
  -sbt-boot  <path>  path to shared boot directory (default: ~/.sbt/boot in 0.11 series)
  -ivy       <path>  path to local Ivy repository (default: ~/.ivy2)
  -mem    <integer>  set memory options (default: $sbt_mem, which is $(get_mem_opts $sbt_mem))
  -no-share          use all local caches; no sharing
  -no-global         uses global caches, but does not use global ~/.sbt directory.
  -jvm-debug <port>  Turn on JVM debugging, open at the given port.
  -batch             Disable interactive mode

  # sbt version (default: from project/build.properties if present, else latest release)
  -sbt-version  <version>   use the specified version of sbt
  -sbt-jar      <path>      use the specified jar as the sbt launcher
  -sbt-rc                   use an RC version of sbt
  -sbt-snapshot             use a snapshot version of sbt

  # java version (default: java from PATH, currently $(java -version 2>&1 | grep version))
  -java-home <path>         alternate JAVA_HOME

  # jvm options and output control
  JAVA_OPTS          environment variable, if unset uses "$java_opts"
  SBT_OPTS           environment variable, if unset uses "$default_sbt_opts"
  .sbtopts           if this file exists in the current directory, it is
                     prepended to the runner args
  /etc/sbt/sbtopts   if this file exists, it is prepended to the runner args
  -Dkey=val          pass -Dkey=val directly to the java runtime
  -J-X               pass option -X directly to the java runtime
                     (-J is stripped)
  -S-X               add -X to sbt's scalacOptions (-S is stripped)

In the case of duplicated or conflicting options, the order above
shows precedence: JAVA_OPTS lowest, command line options highest.
EOM
}

process_my_args () {
  while [[ $# -gt 0 ]]; do
    case "$1" in
     -no-colors) addJava "-Dsbt.log.noformat=true" && shift ;;
      -no-share) addJava "$noshare_opts" && shift ;;
     -no-global) addJava "-Dsbt.global.base=$(pwd)/project/.sbtboot" && shift ;;
      -sbt-boot) require_arg path "$1" "$2" && addJava "-Dsbt.boot.directory=$2" && shift 2 ;;
       -sbt-dir) require_arg path "$1" "$2" && addJava "-Dsbt.global.base=$2" && shift 2 ;;
     -debug-inc) addJava "-Dxsbt.inc.debug=true" && shift ;;
         -batch) exec </dev/null && shift ;;

    -sbt-create) sbt_create=true && shift ;;

              *) addResidual "$1" && shift ;;
    esac
  done

  # Now, ensure sbt version is used.
  [[ "${sbt_version}XXX" != "XXX" ]] && addJava "-Dsbt.version=$sbt_version"
}

loadConfigFile() {
  cat "$1" | sed '/^\#/d' | while read line; do
    eval echo $line
  done
}

# TODO - Pull in config based on operating system... (MSYS + cygwin should pull in txt file).
# Here we pull in the global settings configuration.
[[ -f "$etc_sbt_opts_file" ]] && set -- $(loadConfigFile "$etc_sbt_opts_file") "$@"
# -- Windows behavior stub'd
# JAVA_OPTS=$(cat "$WDIR/sbtconfig.txt" | sed -e 's/\r//g' -e 's/^#.*$//g' | sed ':a;N;$!ba;s/\n/ /g')

#  Pull in the project-level config file, if it exists.
[[ -f "$sbt_opts_file" ]] && set -- $(loadConfigFile "$sbt_opts_file") "$@"

run "$@"

This is /usr/share/sbt-launcher-packaging/bin:
#!/usr/bin/env bash
#

# A library to simplify using the SBT launcher from other packages.
# Note: This should be used by tools like giter8/conscript etc.

# TODO - Should we merge the main SBT script with this library?

declare -a residual_args
declare -a java_args
declare -a scalac_args
declare -a sbt_commands
declare java_cmd=java
declare java_version
declare -r sbt_bin_dir="$(dirname "$(realpath "$0")")"
declare -r sbt_home="$(dirname "$sbt_bin_dir")"

echoerr () {
  echo 1>&2 "$@"
}
vlog () {
  [[ $verbose || $debug ]] && echoerr "$@"
}
dlog () {
  [[ $debug ]] && echoerr "$@"
}

jar_file () {
  echo "$(cygwinpath "${sbt_home}/bin/sbt-launch.jar")"
}

acquire_sbt_jar () {
  sbt_jar="$(jar_file)"

  if [[ ! -f "$sbt_jar" ]]; then
    echoerr "Could not find launcher jar: $sbt_jar"
    exit 2
  fi
}

execRunner () {
  # print the arguments one to a line, quoting any containing spaces
  [[ $verbose || $debug ]] && echo "# Executing command line:" && {
    for arg; do
      if printf "%s\n" "$arg" | grep -q ' '; then
        printf "\"%s\"\n" "$arg"
      else
        printf "%s\n" "$arg"
      fi
    done
    echo ""
  }

  # THis used to be exec, but we loose the ability to re-hook stty then
  # for cygwin...  Maybe we should flag the feature here...
  "$@"
}

addJava () {
  dlog "[addJava] arg = '$1'"
  java_args=( "${java_args[@]}" "$1" )
}
addSbt () {
  dlog "[addSbt] arg = '$1'"
  sbt_commands=( "${sbt_commands[@]}" "$1" )
}
addResidual () {
  dlog "[residual] arg = '$1'"
  residual_args=( "${residual_args[@]}" "$1" )
}
addDebugger () {
  addJava "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=$1"
}

get_mem_opts () {
  # if we detect any of these settings in ${JAVA_OPTS} we need to NOT output our settings.
  # The reason is the Xms/Xmx, if they don't line up, cause errors.
  if [[ "${JAVA_OPTS}" == *-Xmx* ]] || [[ "${JAVA_OPTS}" == *-Xms* ]] || [[ "${JAVA_OPTS}" == *-XX:MaxPermSize* ]] || [[ "${JAVA_OPTS}" == *-XX:MaxMetaspaceSize* ]] || [[ "${JAVA_OPTS}" == *-XX:ReservedCodeCacheSize* ]]; then
     echo ""
  else
    # a ham-fisted attempt to move some memory settings in concert
    # so they need not be messed around with individually.
    local mem=${1:-1024}
    local codecache=$(( $mem / 8 ))
    (( $codecache > 128 )) || codecache=128
    (( $codecache < 512 )) || codecache=512
    local class_metadata_size=$(( $codecache * 2 ))
    local class_metadata_opt=$([[ "$java_version" < "1.8" ]] && echo "MaxPermSize" || echo "MaxMetaspaceSize")

    echo "-Xms${mem}m -Xmx${mem}m -XX:ReservedCodeCacheSize=${codecache}m -XX:${class_metadata_opt}=${class_metadata_size}m"
  fi
}

require_arg () {
  local type="$1"
  local opt="$2"
  local arg="$3"
  if [[ -z "$arg" ]] || [[ "${arg:0:1}" == "-" ]]; then
    echo "$opt requires <$type> argument"
    exit 1
  fi
}

is_function_defined() {
  declare -f "$1" > /dev/null
}

process_args () {
  while [[ $# -gt 0 ]]; do
    case "$1" in
       -h|-help) usage; exit 1 ;;
    -v|-verbose) verbose=1 && shift ;;
      -d|-debug) debug=1 && shift ;;

           -ivy) require_arg path "$1" "$2" && addJava "-Dsbt.ivy.home=$2" && shift 2 ;;
           -mem) require_arg integer "$1" "$2" && sbt_mem="$2" && shift 2 ;;
     -jvm-debug) require_arg port "$1" "$2" && addDebugger $2 && shift 2 ;;
         -batch) exec </dev/null && shift ;;

       -sbt-jar) require_arg path "$1" "$2" && sbt_jar="$2" && shift 2 ;;
   -sbt-version) require_arg version "$1" "$2" && sbt_version="$2" && shift 2 ;;
     -java-home) require_arg path "$1" "$2" && java_cmd="$2/bin/java" && shift 2 ;;

            -D*) addJava "$1" && shift ;;
            -J*) addJava "${1:2}" && shift ;;
              *) addResidual "$1" && shift ;;
    esac
  done

  is_function_defined process_my_args && {
    myargs=("${residual_args[@]}")
    residual_args=()
    process_my_args "${myargs[@]}"
  }

  java_version=$("$java_cmd" -Xmx512M -version 2>&1 | awk -F '"' '/version/ {print $2}')
  vlog "[process_args] java_version = '$java_version'"
}

# Detect that we have java installed.
checkJava() {
  local required_version="$1"
  # Now check to see if it's a good enough version
  if [[ "$java_version" == "" ]]; then
    echo
    echo No java installations was detected.
    echo Please go to http://www.java.com/getjava/ and download
    echo
    exit 1
  elif [[ ! "$java_version" > "$required_version" ]]; then
    echo
    echo The java installation you have is not up to date
    echo $script_name requires at least version $required_version+, you have
    echo version $java_version
    echo
    echo Please go to http://www.java.com/getjava/ and download
    echo a valid Java Runtime and install before running $script_name.
    echo
    exit 1
  fi
}

run() {
  # no jar? download it.
  [[ -f "$sbt_jar" ]] || acquire_sbt_jar "$sbt_version" || {
    # still no jar? uh-oh.
    echo "Download failed. Obtain the sbt-launch.jar manually and place it at $sbt_jar"
    exit 1
  }

  # process the combined args, then reset "$@" to the residuals
  process_args "$@"
  set -- "${residual_args[@]}"
  argumentCount=$#

  # TODO - java check should be configurable...
  checkJava "1.6"

  #If we're in cygwin, we should use the windows config, and terminal hacks
  if [[ "$CYGWIN_FLAG" == "true" ]]; then
    stty -icanon min 1 -echo > /dev/null 2>&1
    addJava "-Djline.terminal=jline.UnixTerminal"
    addJava "-Dsbt.cygwin=true"
  fi

  # run sbt
  execRunner "$java_cmd" \
    ${SBT_OPTS:-$default_sbt_opts} \
    $(get_mem_opts $sbt_mem) \
  	  ${JAVA_OPTS} \
    ${java_args[@]} \
    -jar "$sbt_jar" \
    "${sbt_commands[@]}" \
    "${residual_args[@]}"

  exit_code=$?

  # Clean up the terminal from cygwin hacks.
  if [[ "$CYGWIN_FLAG" == "true" ]]; then
    stty icanon echo > /dev/null 2>&1
  fi
  exit $exit_code
}

I've achieved this by upgrading from 0.13.5 to 0.13.9, so it's no longer a virgin install, unlike what was the case when I tested it last time. I've got the same error now but with a different module: module not found: org.scala-lang#scala-library;2.10.5

I'm not expert on this, but the trustAnchors errors seems unlikely to be sbt-specific, maybe a more general config problem on your machine. does e.g. http://askubuntu.com/questions/627426/minecraft-with-openjdk-7-i-get-the-trustanchors-parameter-must-be-non-empty help?

Well, it's not only sbt-specific, it's sbt 0.13.9-specific. Everything works fine with sbt 0.13.5.

Another one here: http://stackoverflow.com/questions/6784463/error-trustanchors-parameter-must-be-non-empty
Your Java installation is probably missing CA root certificates. Try
apt-get install ca-certificates-java

and if that doesn't help
sudo update-ca-certificates -f

´´´sudo update-ca-certificates -f ´´´ did it for me. Could be added as a tip in the error message, perhaps?

apt-get install ca-certificates-java fixed the problem for me. Thanks!

Any idea how to fix this on a mac?

also ask help for mac ...

There are some hints for Mac here. http://stackoverflow.com/questions/6784463/error-trustanchors-parameter-must-be-non-empty/6788682
I'm closing this as it doesn't seems to be a sbt specific issue.

I tried updating ca-certificates mentioned above but it did not fix the issue.
Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.13/sbt-0.13.13.jar
Is there anything I can try to fix this?

The root cause is a conflict between openjdk-11-jdk (which is default in Ubuntu 18.04) and sbt packages settings. It has already been fixed in Debian and will be included in Ubuntu shortly. Meanwhile the simplest workaround is to demote your java to version 8. Other solutions employing ca-certificates-java are much more complicated.
First remove conflicting packages:
sudo apt-get remove --purge openjdk* java-common default-jdk
sudo apt-get remove --purge sbt
sudo apt-get autoremove --purge

Check weather you successfully removed all related packages by:
sudo update-alternatives --config java

The system shall prompt you there is no Java available to config, otherwise this workaround fails.
Then reinstall required packages:
sudo apt-get install openjdk-8-jdk sbt

Test by:
sbt compile

The instructions by @shvahabi no longer work.
xobs@Cuboid:~$ sudo apt-get install openjdk-8-jdk sbt
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openjdk-8-jdk : Depends: openjdk-8-jre (= 8u171-b11-0ubuntu<IP_ADDRESS>) but it is not going to be installed
                 Recommends: libxt-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
xobs@Cuboid:~$

This appears to be because openjdk-8-jdk depends on openjdk-8-jre, which depends on libgl1, which depends on libglapi-mesa (= 17.2.8-0ubuntu0~16.04.1) which is unavailable.  Instead, 18.04 includes libglapi-mesa 18.0.0~rc5-1ubuntu1, and so Java 8 cannot be installed.

I am running sbt==0.13.1 on 18.04 and followed exactly @shvahabi steps.

Attention Ubuntu users: Please see the note here https://www.scala-sbt.org/1.x/docs/Installing-sbt-on-Linux.html#Ubuntu+and+other+Debian-based+distributions:

There's been reports about SSL error using Ubuntu: Server access Error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/1.1.0/sbt-1.1.0.pom, which apparently stems from OpenJDK 9 using PKCS12 format for /etc/ssl/certs/java/cacerts cert-bug. According to https://stackoverflow.com/a/50103533/3827 it is fixed in Ubuntu Cosmic (18.10), but Ubuntu Bionic LTS (18.04) is still waiting for a release. See the answer for a workaround.


Do we need to support a "lint directory" use case?

Currently, super-linter mainly focuses on linting single files, treating cases where a linter supports "whole" directories only as special/peculiar. ~For example (the only example we have now), we handle ansible-lint as a special case in the LintAnsibleFiles function.~ This is not true actually
Now, there's another of such cases in #886: tfsec.
Instead of adding another special case, shall we plan for a more generalized lint this whole directory use case?
/cc @admiralAwkbar @GaboFDC

This would be a really nice feature, there is some related issues also like #424, #736 and maybe others.
Problem is not sure what would be the logic to do so, if we pretend to do it auto-magically it.
We could also take the same approach as with ansible, and when the users wants to check a folder as a whole, allow it to do so via an ENV var, but this doesn't seems like the best.

I think most of the complexity will be where we build the file list. In fact, the other parts still continue to work as they are now.
In cases where we want to lint directories, we can automatically detect them if possible, so that a user doesn't have to specify them manually (in other words, remove the ANSIBLE_DIRECTORY variable). This would be consistent with what we do with other linters: for files, we have criteria to detect a file type (extension, content...).
For directories, I feel we should do the same.

PS: after we gather some consensus, I can give this a shot.

Ok I need jt thanks
On Wednesday, October 21, 2020, Marco Ferrari<EMAIL_ADDRESS>wrote:

PS: after we gather some consensus, I can give this a shot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/super-linter/issues/888#issuecomment-713579992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARMURFEI4FS554VFTPKRVQ3SL3PP5ANCNFSM4SZUBLNQ
.

I'm just wondering what will be the criteria, or how you will determine which liter to use in what folder.
i.e. if there is a folder with 3 yml files, then what?
what if there are 2 ruby files and 2 yml?
what if there are 5 files from 5 different extensions?
what if the folder has 80% of one extension, 10% of other, and 10% of another one?
what if there is a folder with some files of one extension, then 3 folders, each with files from 3 diferent extensions?
That is the logic I mean would be the problem.
If you see a solution to this, or maybe i'm seeing it on the wrong way please share your feedback, but if you see it simplier or there is something i'm missing by all means give it a shot.

Fi nuW disk wuzic ould anw..ass I won’t o .. pl5
On Wednesday, October 21, 2020, Gabriel Diaz<EMAIL_ADDRESS>wrote:

I'm just wondering what will be the criteria, or how you will determine
which liter to use in what folder.
i.e. if there is a folder with 3 yml files, then what?
what if there are 2 ruby files and 2 yml?
what if there are 5 files from 5 different extensions?
what if the folder has 80% of one extension, 10% of other, and 10% of
another one?
what if there is a folder with some files of one extension, then 3
folders, each with files from 3 diferent extensions?
That is the logic I mean would be the problem.
If you see a solution to this, or maybe i'm seeing it on the wrong way
please share your feedback, but if you see it simplier or there is
something i'm missing by all means give it a shot.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/super-linter/issues/888#issuecomment-713876159,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARMURFF5GJNGJNT67VAUWVTSL5EDPANCNFSM4SZUBLNQ
.

I'm just wondering what will be the criteria, or how you will determine which liter to use in what folder.

i.e. if there is a folder with 3 yml files, then what?
what if there are 2 ruby files and 2 yml?
what if there are 5 files from 5 different extensions?
what if the folder has 80% of one extension, 10% of other, and 10% of another one?
what if there is a folder with some files of one extension, then 3 folders, each with files from 3 diferent extensions?
That is the logic I mean would be the problem.
If you see a solution to this, or maybe i'm seeing it on the wrong way please share your feedback, but if you see it simplier or there is something i'm missing by all means give it a shot.

You might run different linters on in the same folder! The criteria would be easier than it seems, because it's already somewhat similar to what we're doing in the DetectXXX functions. In this case, we should look at the linter documentation to check what it looks for before linting. Example criteria for tfsec: Is there at least one terraform descriptor in that folder? Yes -> add it to the tfsec file list; no -> skip it.
We don't have to bother if there are other kind of files in that folder, because the logic to build the file list that we have now still applies. Example: if the aforementioned folder contains not only Terraform stuff, but also a shell script, that script is going to be linted by other linters as well (such as shellcheck). And this is ok, and expected.

I think we need to tackle this problem somehow, because there are significant discrepancies between LintCodeBase and LintAnsibleFiles (our only "lint directories" use case).

So, if I get it correctly, yo sai, that we check a file in a dir, and then depending on the type of that file, we add the parent dir, to be linted as a whole?
And what controls when to lint a dir and when to lint a file? We leave to user choice by a flag? or do you think there is a way we can detect automatically?

I don't see that complexity because linting a file or a directory with a linter doesn't prevent you from linting the same file or directory with another linter. We're already doing this. For example:

YAML files are linted against multiple linters already (yamllint and kubeval if the yaml is also a Kubernetes descriptor, and possibly others)
editorconfig-checker lints every text file, and then we lint the same files with other linters.

So I was thinking more about something like a refinement of our scanning logic. We currently deal with files only, adding a file to (possibly multiple) file lists, according to its extension, type, and contents. What I propose is adding logic to do the same with directories. Example: is this directory an ansible role? -> add it to the directories to be linted with ansible-lint.
Since we already have ansible-lint on board, and might be others in the future, we might want to think about a possible implementation of this use case. Note that we're already doing this, because we're using LintAnsibleFiles, instead of LintCodeBase.
Backstory: when refactoring the code base to remove duplicate code, I originally thought to get rid of the LintAnsibleFiles function and add its logic to LintCodeBase as an exception. And we got #886, which asked for the very same feature but for tfsec.
We might still abandon the idea of a lint directory use case, but we've to make LintAnsibleFiles use the same logic we're using in LintCodeBase, and think about how to add linters that work on directories instead of files, in a scalable way.

I'm in favor of this, I was just a bit lost on how you planned to do it. But seems like you have the idea pretty clear. Maybe I saw it more complicated that it actually is. Go for it 👍

#1035 takes care of getting rid of the LintAnsibleFiles function.

@Hanse00 I see that you reopened this one. What work still needs to be done here? Does https://github.com/super-linter/super-linter/pull/1035 not cover closing this issue? Just looking for some more info so we can try and move towards completing this one.

After additional consideration, we realized that the infrastructure already supports this when we can correctly identify the contents of a directory.


[FLINK-30629][Client/Job Submission] Increase clientHeartbeatTimeout to 1 second

What is the purpose of the change
Increase clientHeartbeatTimeout to 1 second to avoid shutting down the job in ClientHeartbeatTest.
Brief change log

Increase clientHeartbeatTimeout to 1 second

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

thanks @Myracle


examples not working for me

please run the code (execute v run) from outside the module directory, in this case, the vgrid directory.
I opened an issue one month ago in the v lang repo, about this import unexpected behaviour, they mark the issue as a bug 6 days ago but not fixed yet.


Renew the static bindings for the bots that don't have SWIG.

rdar://problem/49520686

@swift-ci please test and merge


Add optional file metadata

Metadata is stored in the file index structure and is opaque to SPIFFS.
It allows user to associate additional information with a file.
Fixes pellepl/spiffs#127

thanks for the speedy review!


Datadog exporter does not run

I'm posting this here because I think the issue is specific to running the helm chart, not a problem with the Datadog exporter in general. Please let me know if this is not the case and I can post this is the collector contrib repo.
When I run the image directly:
docker run -p 4317:4317 \
    -v $PWD/otel-collector-config.yaml:/etc/otel-collector-config.yaml \
    otel/opentelemetry-collector-contrib:0.30.0 \
    --config=/etc/otel-collector-config.yaml

Where otel-collector-config.yaml looks like:
receivers:
    otlp:
        protocols:
            http:
exporters:
    datadog:
        service: test
        env: test
        version: 0.0.0
        api:
            key: "..."
processors:
    batch:
        timeout: 10s
service:
    pipelines:
        traces:
            receivers: [otlp]
            exporters: [datadog]
            processors: [batch]

I see:
info    utils/api.go:32 Validating API key.     {"kind": "exporter", "name": "datadog"}
info    utils/api.go:39 API key validation successful.  {"kind": "exporter", "name": "datadog"}
...
info    builder/exporters_builder.go:98 Exporter started.       {"kind": "exporter", "name": "datadog"}

And everything works as expected.
However if I use this helm chart:
helm install opentelemetry-collector open-telemetry/opentelemetry-collector --values opentelemetry-collector.yaml

Where opentelemetry-collector.yaml looks like:
agentCollector:
  enabled: false

standaloneCollector:
  enabled: true

image:
  repository: otel/opentelemetry-collector-contrib
  pullPolicy: IfNotPresent
  tag: "0.30.0"

command:
  name: otelcontribcol

config:
  receivers:
    otlp:
      protocols:
        http:

  processors:
    batch:
      timeout: 10s

  exporters:
    datadog:
      service: test
      env: test
      version: 0.0.0
      api:
        key: "..."

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog]

I see:
info    builder/exporters_builder.go:98    Exporter started.    {"kind": "exporter", "name": "datadog"}

But I don't see the other messages about verifying the API key.
And if I send over traces, I see them being logged (if I enable the logger exporter ad debug level):
Span #57
     Trace ID       : 12055027ec737720c79be4a66b1e8672
     Parent ID      : 1363f0dfbd1f4d41
     ...

But nothing is being exported to Datadog.
So it seems like the Datadog exporter is not starting up correctly.

I spotted that it was being ignored because it is not used by any pipeline. Which I think is wrong. But moving the service config under standalongCollector.configOverride seems to have solved it.

I see the issue in your helm config. service is on the top level, but it must be under config.

Thanks! Definitely user error. I appreciate the reply


Support via and pad in net.plot()

Description of the current limitations
need to improve details on plotting
Code sample expected
No response
Useful links and references
No response

Covered by #841. Close.


Local mkdocs issues

mypy fails locally with the following:
$ poetry run mypy .
site/scripts/gen_ref_pages.py: error: Duplicate module named "gen_ref_pages" (also at "./docs/scripts/gen_ref_pages.py")
site/scripts/gen_ref_pages.py: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#mapping-file-paths-to-modules for more info
site/scripts/gen_ref_pages.py: note: Common resolutions include: a) using `--exclude` to avoid checking one of them, b) adding `__init__.py` somewhere, c using `--explicit-package-bases` or adjusting MYPYPATH
Found 1 error in 1 file (errors prevented further checking)

You're overriding the path(s) for MyPy with the ., instead do:
poetry run mypy

If you drop the local path then MyPy will default to the following directories:
https://github.com/fulcrumgenomics/prymer/blob/5d79a52064fbc331e77ed2c626eaf15a85c3d524/pyproject.toml#L103
Alternatively we could tell MyPy what to exclude instead of include:
https://mypy.readthedocs.io/en/stable/config_file.html#confval-exclude


Server timeout elapsed

Server timeout elapsed without receiving a message from the server.
Does anyone know what I could try to modify on the server to remove this error? Or to be able to test better?
Until recently, I was successfully using the package, in the same API.
In debug mode, it works. But in release mode, it doesn't.
My code in client:
class SignalRService {
  SignalRService(this.serverUrl) {
    _hubConnection = HubConnectionBuilder()
        .withAutomaticReconnect()
        .withUrl(
          serverUrl,
          options: HttpConnectionOptions(
            requestTimeout: 60000,
          ),
        )
        .build();
  }

  late final String serverUrl;
  late final HubConnection _hubConnection;

  HubConnection get hubConnection => _hubConnection;

  Future<void> connect() async {
    await _hubConnection.start();
  }
}

In server:
public class MobileHub : Hub
{
//Methods
}

The hub is also registered in Startup.cs.

@diegorkalschne : I am experiencing the same issue. Did you find a solution?

@beebobox
On my Windows Server, the WebSocket protocol was not installed.
After installing it, it started working again.
See: https://secure.jadeworld.com/developer-centre/JADE2018/OnlineDocumentation/content/resources/installconfig/ch3configuringjade/iisinstallforwebsocket.htm


Add .editorconfig to this repository

So that editors will automatically indent with 4 spaces and the like.

Fixed in #356.


GKE permission issue with micro api

Trying to deploy micro-api pods on Google Kubernetes Cluster
Getting the below error. Seems to be some permission issue. Was hoping if someone can give me some pointers. Namespace of go-micro pod is in app
2018/08/22 00:43:40 Registering RPC Handler at /rpc
2018/08/22 00:43:40 Registering API Default Handler at /
2018/08/22 00:43:40 Listening on [::]:3000
2018/08/22 00:43:40 Listening on [::]:33959
2018/08/22 00:43:40 Broker Listening on [::]:46409
2018/08/22 00:43:40 Registering node: go.micro.api-6a215d3c-a5a4-11e8-a5bb-0a580a0c0153
2018/08/22 00:43:40 K8s: request failed with code 403
2018/08/22 00:43:40 K8s: request failed with body:
2018/08/22 00:43:40 {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:app:default\" cannot list pods in the namespace \"app\": Unknown user \"system:serviceaccount:app:default\"","reason":"Forbidden","details":{"kind":"pods"},"code":403}
2018/08/22 00:43:40 Error watching endpoints K8s: error
2018/08/22 00:43:40 K8s: request failed with code 403
2018/08/22 00:43:40 K8s: request failed with body:
2018/08/22 00:43:40 {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"microapi-5f5bdfb9d5-f5g2g\" is forbidden: User \"system:serviceaccount:app:default\" cannot patch pods in the namespace \"app\": Unknown user \"system:serviceaccount:app:default\"","reason":"Forbidden","details":{"name":"microapi-5f5bdfb9d5-f5g2g","kind":"pods"},"code":403}
2018/08/22 00:43:40 K8s: error

kind: Deployment
apiVersion: apps/v1
metadata:
  name: microapi
  namespace: app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: micro
  template:
    metadata:
      namespace: app
      labels:
        app: micro
    spec:
        containers:
        - name: micro
          image: microhq/micro:kubernetes
          args:
            - "api"
          env:
          - name: MICRO_API_ADDRESS
            value: "<IP_ADDRESS>:3000"
          - name: MICRO_API_NAMESPACE
            value: "mgyongappk8"

          ports:
          - containerPort: 3000
            name: api-port

apiVersion: v1
kind: Service
metadata:
  name: micro
  namespace: app
spec:
  type: LoadBalancer
  ports:
  - name: api-http
    port: 3000
    targetPort: api-port
    protocol: TCP
  selector:
    app: micro

Note: I am not using Kubernetes registry for service discovery but using a consul cluster

If you were using the consul registry you would not see this error

It looks like my server app is using consul for service discovery but the micro api container i am deploying is using kubernetes registry for service discovery. How do i configure the micro-api to use the consul registry? I don't see a flag to set as per the documentation micro api here
https://micro.mu/docs/api.html

The micro api uses consul by default. Which container image are you using?

    spec:
        containers:
        - name: micro
          image: microhq/micro:kubernetes

      image: microhq/micro:kubernetes

That image uses the kubernetes registry. Do not use it if you want to use consul.


current temperature problem

Describe The Bug:

I have a Tadiran AC that works perfectly with gree but I’m using homekit (with homebridge of course).
There are several problems with it:

It says the current temperature is -40 degrees (on the accessory).
When I create an automation and set the AC to turn on and set to 24 degrees, it does it with 22 degrees.
I want that the apple homekit will be able to control the light (that shows the temperature) on the AC.
In heat mod, I cant go higher than 25 degrees (I want 30)

To Reproduce:

Expected behavior:

Logs:
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
NPM Version:
Operating System:
Raspbian

Please attach plugin config and debug logs to analyze your issues!
It seems that you have set sensorOffset to 0 instead of the default 40 but I am not sure until I see your configuration settings.

Hi @orich4322
I am still waiting for plugin config and debug log...
I have analyzed your issue and I can answer some questions:

It says the current temperature is -40 degrees (on the accessory).

I have found a bug in processing data received from temperature sensor. I have fixed it in version 2.1.5. Please upgrade to the latest version before you create debug logs. I do not think any more that you have set sensorOffset to 0. -40 is a bug which is solved in the latest version. Unfortunately there are some firmware versions which do not report data from the built-in temperature sensor. In this case the plugin can't access the room temperature and the target temperature is used. Only a firmware upgrade or downgrade can solve this problem. This is documented in plugin's readme.

When I create an automation and set the AC to turn on and set to 24 degrees, it does it with 22 degrees.

Automations do not depend on this plugin nor on homebridge. As I know automations save the target temperature value upon definition. If the AC unit was set to 22 degrees at the time the automation was saved then Home App will turn it on to 22 degrees. Please ask Apple's support for more information.

I want that the apple homekit will be able to control the light (that shows the temperature) on the AC.

This plugin was designed to support the Home App's HeaterCooler accessory. Apple's HeaterCooler does not support the light. It is not on my short time plan to add this feature to the plugin because it is not supported by Apple and could make the UI confusing.

In heat mod, I cant go higher than 25 degrees (I want 30)

This is not a bug, this is documented in plugin's readme. (Please read the known limitations section!) When adding the accessory to Home App it is not possible to set the minimum and maximum values. They can be set only in active cooling and heating modes. So initially the maximum value is 25 degrees which is Apple's default value. On first time use the plugin updates the minimum and maximum values but you can see the new limits only after restarting the Home App. Next time you open the Home App the correct minimum and maximum values are accessible and you can set heating to 30 degrees.

Hello
Thank you a lot for your help
About 4, I’ve set the maximum temperature to be 30 when I added the device in the first place.
I’ve restarted the apple home app several times and it still doesn’t let me set the temperature above 25 in heating mode.
I’m using the heat mode.
Thank for you help!!

Hi @orich4322 ,
I have added some comments about Home App restart to the plugin readme yesterday. Home App restart means that the Home App must be removed from device memory before starting again. On iPhone the following steps are required:

From the Home Screen, swipe up from the bottom of the screen and pause in the middle of the screen.
Swipe right or left to find the app that you want to close.
Swipe up on the app's preview to close the app.

On iPad follow these steps:

Swipe up from the bottom of the screen and hold. You will see all open apps and their preview.
Swipe horizontally to find the app you wish to close. Finally, swipe up on an app card to force quit it.

Did you do the above steps? If yes please try to restart your iPhone or iPad and check the acceptable maximum temperature again. Please tell me the result!
Thank You!

Yes of course I closed the home app (removed from memory) but it still cant go higher than 25 on heat.
What can i do?

I am working on a solution. Please be patient while it's done.


--verbosity=error flag for dart run does not suppress pub get warnings

The tests in the build repo are failing with the latest dev SDK, due to new warnings from pub get being emitted on stderr, during a call to dart run. We want to be able to detect unexpected warnings/errors in this test, but there are now some expected ones which are always emitted, due to the automatic running of pub get.
I tried looking for an option to not run pub get, which I didn't find, and I also tried using the --verbosity=error flag to suppress the expected warnings (about dependency overrides). But I am still seeing the warnings emitted on stderr.
Is it possible for the tool to suppress warnings from pub? Or can we get a flag to have it not run pub get (this should honestly be opt in imo, it's not necessary >99% of the time...).

For now I will just skip these expectations in the dart repo, but I would like to restore them if possible... the tests are pretty meaningless as is.

I think the problem here is that we output:
'Warning: You are using these overridden dependencies:\n'
'! build 2.3.1 from path /home/runner/.pub-cache/hosted/pub.dev/build-2.3.1/\n'
'! build_config 1.1.1 from path /home/runner/.pub-cache/hosted/pub.dev/build_config-1.1.1/\n'
'! build_daemon 3.1.0 from path /home/runner/.pub-cache/hosted/pub.dev/build_daemon-3.1.0/\n'
'! build_resolvers 2.1.0 from path /home/runner/.pub-cache/hosted/pub.dev/build_resolvers-2.1.0/\n'
'! build_runner 2.3.3-dev from path /home/runner/work/build/build/build_runner/\n'
'! build_runner_core 7.2.7 from path /home/runner/.pub-cache/hosted/pub.dev/build_runner_core-7.2.7/\n'
'! code_builder 4.3.0 from path /home/runner/.pub-cache/hosted/pub.dev/code_builder-4.3.0/\n'

on stderr. I think it belongs more on stdout together with other output from pub get.
Alternatively we should block all terminal output unless we have a failing resolution.


Add counters reference-getters for PrecisionRecallLayer

There are many ML problems where TP/FP/FN/TN counters make sense, however they differ in terms of how these counters should be calculated. It would be nice to re-use PrecisionRecallLayer through inheritance for these ML problems.
Currently PrecisionRecallLayer counters are private, so they are inaccessible in the inherited classes, and one can not change the way these counters are calculated.
PR adds virtual reference-getters and uses them instead of direct changes of member variables. Now inherited classes have an access to the counters, and if this access is not sufficient somehow, it is possible to override the getters to use some other member variables.

@FedyuninV

Speaking of virtual getters, the idea was that in some cases it would be reasonable to have more than 4 counters. For example, in case of multi-class classification metrics it could be a whole confusion matrix instead.
On the other hand, reference-getters need a member varable anyway, and may be non-virtual getters would be enough in practice.


Wrong project description

"Speechkit Could examples and SDK" should be renamed to "Speechkit Cloud examples and SDK"

Oh my. Good eye! :+1:


Add Spark benchmarks

Which issue does this PR close?

N/A
Rationale for this change

Make all benchmark code public so others can run the same benchmarks and help find issues.
What changes are included in this PR?

Spark benchmarks
Are there any user-facing changes?

No

@avantgardnerio fyi


Postgresql as data source

Hello
Can I use a chart with a Postgres source?
What are the requirements for this?
Thank you!

@shizacat
Never tried. I use Elastic and InfluxDB. Did you try ? It could work, I will try to check if I find some time this week-end.

Yes, I tried, but did not draw.
Example: https://ibb.co/ih5nzb
Maybe I'm doing something wrong.
I have the latest version of graph: v4.6.2 (commit: 8db5f08)
It would be great if you could check

@shizacat I made a version 1.4 that is working for me. Can you check on your side ?
Cheers,

@snuids You have different content of the folder "src" and "dist". In "dist" still version 1.3
If I replace files manual, the following message pops up:
Plugin Error
Unable to dynamically transpile ES module A loader plugin needs to be configured via `SystemJS.config({ transpiler: 'transpiler-module' })`.
Instantiating http://<IP_ADDRESS>:3000/public/plugins/snuids-radar-panel/module.js Loading plugins/snuids-radar-panel/module

I built from "grunt" and all worked.
Edited the 242 line in the file radargraph_ctrl.js:
if (fulldata[i].datapoints.length >= 1) {
Otherwise, the graph did not show rows from one element
Can I somehow give the names of the charts, instead of A, B?

@shizacat I made a version 1.4.1 that has the >= lien 242 which fixes the single value series problem. Concerning the series name, PostGreSQL support is quite new, I suppose that they will add series alias as for the other datasources in the next versions. Thanks for helping with the code.

Thank you!


706

Update dashboard release to v<IP_ADDRESS>
extensions release remains at v<IP_ADDRESS>
https://github.com/tektoncd/dashboard/releases

Technically <IP_ADDRESS> is still a release candidate... we'll just keep an eye on it and roll it back if necessary.


addon conflicts with Bagnon Equipment 2

Your addon doesn't work together with the bagnon equipment which puts a tiny set icon over gear in bag.
I would like to have they working together, could you make a change to acomplish that? Maybe a smaller font, or another overlay layer ( if that's even possible ) or something.

Also the dev from bagnon equipment 2 is not responding, maybe you could take over his addon just to have all 3 compatible would be wonderful :)

Well I can't take over somebody else's addon, would take a looooot of time of inactivity, and it still wouldn't be mine to keep.
But I can take a look at it and see if I can make mine work better with it. :)

Also, I found another addon that have many functions in one, BoE, ilevel, etc.. That one is named Bagnon_ItemInfo. and worked with bagon equipment with no conflicts. Maybe you could take a look there to see the code differences ;)

Well that's my addon too, so I'm kind aware of both that and your report on it already! :D

aaah sorry, I'm very methodic, like to put each issue to where it belong as a reminder to the coder, even if it's the same, I know how it is to handle several different projects at once forgetting one is easy :)

By the way, I posted a suggestion/issue on the iteminfo place.  I could keep editing the lua file, but If you made it native, It would one less addon tweak to make ; )

aaah sorry, I'm very methodic and I like to put each issue to where it belong as a reminder to the coder, even if it's the same, I use to handle several different projects at once and I know how easy is to forget one :)

Hey, nothing to apologize for! That's the right way to do it. One issue report per actual issue. Otherwise we'll have chaos, mayhem and total anarchy! :laughing:

Yes, I can. But this is an old report about something completely different, so I'm closing this issue and opening a new one about this problem. The new issue is here: #7


refactor(rust): refactor CliState so it can be built using an explicit directory

It also refactors the NodeManager so it includes a CliState instance instead of building a new default instance every time it needs it.
Tries to fix https://github.com/build-trust/ockam/issues/4345

Ready now, all the CliState::try_default usages come from ockam_command.


Documentation on hosting

Can you please document how this should be run? In particular it seems there is a hard coded port and no option documented to configure for the system its running on.

snap provides any application built with it a set of standard options, which can be viewed with --help. This includes port setting, using the -p argument.
I will document this and push.