Support for Nano 33 BLE Sense

Hello all,
I'm trying to use the SPS30 PM sensor with a UART driver from this repository, however, I am new to this sensor and I don't know what to do in order to use the sensor on UART with the Nano 33 BLE Sense, which runs on an nRF52840 MCU. It communicates through the use of Serial1. functions.  What steps do I need to perform in order to use the SPS with UART on this board. I tried using I2C, it works but my project uses much faster pull rates than i2c.
Regards
Guntas

Hi @GuntasSinghProg5
Have you tried the Arduino sample implementation?
Just copy it to the top level folder and maybe change Serial2 to Serial1.

I tried using I2C, it works but my project uses much faster pull rates than i2c.

What do you mean by "faster pull rates"? The device only provides one measurement per second, so you'll get the same values if you just read them again and again.

Will try, Mr. Nestler. Thank you for replying.
Sent from my iPhone

On 6 Aug 2020, at 3:35 PM, Raphael Nestler<EMAIL_ADDRESS>wrote:

Hi @GuntasSinghProg5
Have you tried the Arduino sample implementation?
Just copy it to the top level folder and maybe change Serial2 to Serial1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I meant that on Sparkfun, it says that I2C only works fine for mass concentrations and not number, so I think using UART would solve that problem. UART is faster than I2C, I think. So, I want to use the fastest protocol possible for my project.
Regards
Guntas
Sent from my iPhone

On 6 Aug 2020, at 3:36 PM, Raphael Nestler<EMAIL_ADDRESS>wrote:

I tried using I2C, it works but my project uses much faster pull rates than i2c.
What do you mean by "faster pull rates"? The device only provides one measurement per second, so you'll get the same values if you just read them again and again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


time conversion on travis

New and interesting failure on Travis today (https://travis-ci.org/USGS-R/streamMetabolizer/builds/104157263):
> test_check('streamMetabolizer')
Loading required package: streamMetabolizer
This information is preliminary or provisional and is subject to revision. It is being provided to meet the need for timely best science. The information has not received final approval by the U.S. Geological Survey (USGS) and is provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the information. Although this software program has been used by the USGS, no warranty, expressed or implied, is made by the USGS or the U.S. Government as to the accuracy and functioning of the program and related program material nor shall the fact of distribution constitute any such warranty, and no responsibility is assumed by the USGS in connection therewith.
1. Failure (at test-convert.R#35): converting between date and DOY works -------
convert_date_to_doyhr(as.POSIXct("2016-05-29 01:00:00", tz = "CST6CDT")) not equal to 150
150 - 150 == 0.0417
treat numbers as true time since jan 1, ignoring daylight time

2. Failure (at test-convert.R#42): converting between date and DOY works -------
convert_date_to_doyhr(convert_doyhr_to_date(120, year = 1998, tz = "CST6CDT")) not equal to 120
120 - 120 == 0.0417
should preserve DOY in there&back even during daylight savings

3. Failure (at test-convert.R#43): converting between date and DOY works -------
convert_doyhr_to_date(convert_date_to_doyhr(as.POSIXct("2007-06-15 12:00:00", tz = "MST7MDT")), 2007, tz = "MST7MDT") not equal to as.POSIXct("2007-06-15 12:00:00", tz = "MST7MDT")
Mean absolute difference: 3600
preserve date in there&back

Calling 2 simulations using the parallel method...
All chains have finished
Simulation complete.  Reading coda files...
Coda files loaded successfully
Finished running the simulation
Calling 2 simulations using the parallel method...
All chains have finished
Simulation complete.  Reading coda files...
Coda files loaded successfully
Finished running the simulation
testthat results ================================================================
OK: 289 SKIPPED: 0 FAILED: 3
1. Failure (at test-convert.R#35): converting between date and DOY works
2. Failure (at test-convert.R#42): converting between date and DOY works
3. Failure (at test-convert.R#43): converting between date and DOY works

Error: testthat unit tests failed
In addition: Warning messages:
1: In getSchmidt(temperature, gas) : temperature out of range
2: In getSchmidt(temperature, gas) : temperature out of range
3: In getSchmidt(temperature, gas) : temperature out of range
4: In getSchmidt(temperature, gas) : temperature out of range
5: In getSchmidt(temperature, gas) : temperature out of range
6: In getSchmidt(temperature, gas) : temperature out of range
7: In getSchmidt(temperature, gas) : temperature out of range
8: In getSchmidt(temperature, gas) : temperature out of range
9: In getSchmidt(temperature, gas) : temperature out of range
Execution halted

travis_time:end:01faefe6:start=1453490012280903437,finish=1453490012287478155,duration=6574718
R CMD check failed

On my computer, ctrl-shift-T (devtools::test()) does just fine. Same number of getSchmidt warnings (9), but no failures.

Here's the whole testthat block:
test_that("converting between date and DOY works", {
  # date to doyhr
  expect_equal(convert_date_to_doyhr(as.POSIXct("2020-01-01 00:00:00", tz="GMT")), 1, tol=0.000001, info="Jan 1 should be 1")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2020-01-01 00:00:00", tz="CST6CDT")), 1, tol=0.000001, info="use the same timezone as the arg date")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2020-01-01 00:00:00")), 1, tol=0.000001, info="should work in any tester's default tz")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2020-01-01 01:00:00")), 1+1/24, tol=0.000001, info="decimal should include hours")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2020-01-01 01:03:58")), 1+(60+3+58/60)/(24*60), tol=0.000001, info="decimal should include minutes and seconds")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2004-12-01 00:00:00")), 1+convert_date_to_doyhr(as.POSIXct("2019-12-01 00:00:00")), tol=0.000001, info="should catch leap days")
  expect_equal(convert_date_to_doyhr(as.POSIXct("2016-05-29 01:00:00", tz="CST6CDT")), 150, info="treat numbers as true time since jan 1, ignoring daylight time")
  # doyhr to date
  expect_equal(convert_doyhr_to_date(1, year=1920), as.POSIXct("1920-01-01 00:00:00", tz="GMT"), info="1 should be Jan 1, default GMT")
  expect_equal(convert_doyhr_to_date(3, year=2016, tz="CST6CDT"), as.POSIXct("2016-01-03 00:00:00", tz="CST6CDT"), info="tz should stay as indicated")
  expect_equal(convert_doyhr_to_date(150, year=2016, tz="CST6CDT"), as.POSIXct("2016-05-29 01:00:00", tz="CST6CDT"), info="treat numbers as true time since jan 1, ignoring daylight time")
  # there and back
  expect_equal(convert_date_to_doyhr(convert_doyhr_to_date(12, year=2024, tz="CST6CDT")), 12, info="should preserve DOY in there&back")
  expect_equal(convert_date_to_doyhr(convert_doyhr_to_date(120, year=1998, tz="CST6CDT")), 120, info="should preserve DOY in there&back even during daylight savings")
  expect_equal(convert_doyhr_to_date(convert_date_to_doyhr(as.POSIXct("2007-06-15 12:00:00", tz="MST7MDT")), 2007, tz="MST7MDT"),
               as.POSIXct("2007-06-15 12:00:00", tz="MST7MDT"), info="preserve date in there&back")
})

and here are the lines that fail:
expect_equal(convert_date_to_doyhr(as.POSIXct("2016-05-29 01:00:00", tz="CST6CDT")), 150, info="treat numbers as true time since jan 1, ignoring daylight time")
expect_equal(convert_date_to_doyhr(convert_doyhr_to_date(120, year=1998, tz="CST6CDT")), 120, info="should preserve DOY in there&back even during daylight savings")
expect_equal(convert_doyhr_to_date(convert_date_to_doyhr(as.POSIXct("2007-06-15 12:00:00", tz="MST7MDT")), 2007, tz="MST7MDT"),
             as.POSIXct("2007-06-15 12:00:00", tz="MST7MDT"), info="preserve date in there&back")

looks to me like the failure is happening only when daylight savings time is on (summer). this is consistent with the numerical differences in the error messages - 0.0417 is 1/24 day is 1 hour, and 3600 seconds is also 1 hour. so there's something about the (new?) Travis environment that's failing to understand time zones as we're communicating them.

The recent Travis change is that travis-ci.org builds (i.e., ours) are now running on Google Compute Engine (GCE).

This job ran on our new platform for Precise builds. Please read our blog post for more information.

There appear to be two options for sudo: required builds: there's Legacy Precise (what I think we've been running based on the above) and Trusty Beta (https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments). I think there's time zone information missing from Legacy Precise. It's possible we can fix that there, but a quick Google isn't turning up the answer. Maybe just running Trusty instead will work?

Nope. Rats.
https://travis-ci.org/USGS-R/streamMetabolizer/builds/106360415

maybe the problem is that CST6CDT and, MST7MDT, etc. are unrecognized time zones in Ubuntu - see http://manpages.ubuntu.com/manpages/saucy/man3/DateTime::TimeZone::Catalog.3pm.html. (Why did these work OK before?? anyway...). I'll try it.

solved in #146 by switching from lubridate::floor_date to a format-based solution:
 -  out <- 1 + as.numeric(v(date) - floor_date(v(date), unit="year"), units="days") # days_since_dec31
 +  year <- as.POSIXct(format(v(date), "%Y-01-01 00:00:00"), tz=lubridate::tz(v(date)))
 +  out <- as.numeric(v(date) - year, units="days") + 1 # days_since_dec31

This seems to work better for Travis (Linux) and still works for my computer (Windows). Don't know about Appveyor (Windows) because of that install_github thing =(.
A bug report to lubridate could be in order - floor_date appears to be mishandling daylight savings on at least one (but not all) versions of Linux. Or this might be Linux's fault rather than lubridate's. Wish I could explore this more directly...


Correction for raw affiliation Western Institute for Neuroscience, Western University, London, Ontrio, Cnd

Correction needed for raw affiliation Western Institute for Neuroscience, Western University, London, Ontrio, Cnd
raw_affiliation_name: Western Institute for Neuroscience, Western University, London, Ontrio, Cnd
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4378231579
contact: 9bd00e20cde22f08de9856804e5e22d2:ab4adb4dbf50664e @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Assets can not be stached after being moved to database

I am migrating our site's content from flat files to a Postgres database to improve performance. The site works and the files are migrated, but every time I try to run php please stache:refresh, I get the following error when the $handle = 'all':
 TypeError

  Statamic\Eloquent\Assets\AssetContainerRepository::findByHandle(): Return value must be of type ?Statamic\Contracts\Assets\AssetContainer, Illuminate\Support\Collection returned

  at vendor/statamic/eloquent-driver/src/Assets/AssetContainerRepository.php:41
     37▕                 return null;
     38▕             }
     39▕
     40▕             return app(AssetContainerContract::class)->fromModel($model);
  ➜  41▕         });
     42▕     }
     43▕
     44▕     public function make(string $handle = null): AssetContainerContract
     45▕     {

      +33 vendor frames
  34  please:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

When I access the site without the stache is it able to get the assets using the individual $handles, and when I hardcode the $handle inside AssetContainerRepository it works fine but it fails on $handle = 'all'. I presume it is because it gets a collection of AssetContainers but is there a way to fix this?
I also get the following when trying to access assets in the control panel:
TypeError
Statamic\Eloquent\Assets\AssetContainerRepository::all(): Return value must be of type Illuminate\Support\Collection, Statamic\Eloquent\Assets\AssetContainer returned (View: /Users/martin/Sites/sd-statamic/vendor/statamic/cms/resources/views/layout.blade.php)

Setup:
Statamic 3.4.5 Pro
Laravel 8.83.27
PHP 8.1.16
Stache Watcher Enabled
Static Caching Disabled
adapt/tfa 1.0.1
statamic/eloquent-driver 1.2.0
thehome/statamic-elasticsearch dev-ADP-1213-loadtide-statamic-update

Should be fixed by https://github.com/statamic/eloquent-driver/pull/136


Make it easier to quickly close a large number of tabs

Have you ever noticed how you can close a large number of tabs very quickly in Chrome? This is because the width of the tab is held constant until the mouse leaves the tab area, so if I close a tab, the next tab moves to occupy the exact same space that the previous tab did, with the "x" in the same position, allowing me to quickly close a large number of tabs by simply clicking repeatedly in the same spot.
I've noticed while using Atom that I oftentimes want to quickly close a large number of tabs, which proves to be challenging given the current state of tab closing. Below are two options for how this could be improved.
Option 1 (easier)
Move the "x" to the same side tabs are floated. For me, tabs are floated left (this may be different for right-to-left languages, I don't know). For me, if the "x" was also on the left, then you could rapidly close tabs by clicking repeatedly in the same position, since the "x" of the next tab would occupy the same position as the "x" of the tab that was just closed. This seems like the obvious solution to me, but there may be other reasons that the "x" was placed on the right-hand side that I'm not aware of.
Option 2 (more difficult)
Leave the "x" where it is (on the right-hand side), but use Chrome's approach of keeping the tab size constant until the user moves the mouse out of the tab region. This would require a lot more code, but would allow you to keep the "x" on the right-hand side (if that is important for some reason).

Thanks for the suggestion! This looks like a duplicate of https://github.com/atom/tabs/issues/129 – feel free to keep the discussion going there.


OnTap() does not get triggered for CirculitoSection in iOS example app. Version : ^1.0.0

Is it a known issue that the onTap is not triggered for CirculitoSection in iOS devices/simulators?
The same app in Android responds to onTap gesture.

@kegadev : Is it a known issue ?

Hi there @tashiwangdi. I haven't noticed that, thanks for letting me know. I checked myself and it's true.
I've been busy this days with other projects, but as soon as I get a free time I put an eye on it and see what is going on.

Hi @tashiwangdi. I just updated the package now, fixing the OnTap on mobiles. Thanks for letting me know that issue. Now I will close this issue.


Improve the Readme Documentation

Create a beautiful Readme Documentation

HI I can help here

@sanjana-1604  I am assigning this task to you

Shall I work on this issue? @Ayushpanditmoto

@Rishav1707  sure, i m assigning this task


Support automatic role creation for read and backend (to write data b…

…ack) roles
Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Spoke with @derek-ho and @anirudha for this PoC PR will close for now but will be used for inspiration.


Real data testing

hello, it seems the results of the real dataset are not run from the fbcnn_color.pth ? Would you mind providing the corresponding fbcnn model for the real dataset?
Thank you!

Hi, the real examples I showed are run from the fbcnn_color.pth. What results did you get?

It looks like the default result from the model trained with single jpeg images. Please check out the result with given QF = 10. https://github.com/jiaxi-jiang/FBCNN/blob/main/main_test_fbcnn_color_real.py#L23


support unlimited paging

The repositories command needs unlimited paging support. I run this fragment daily and suddenly the found repositories count became 100:
    printf "Fetching repositories..."
    repos=$(docker-ls repositories | jq -r '.Repositories[]')
    printf "%d repositories found\n" "$(echo "$repos" | wc -l)"

... which is weird as command usage says the default is 100, and i have made no code changes, why it found 515 before?
# less /var/log/cronlogs/gitlab-delete-build-images |grep Fetching.rep
2019-02-15 16:58:27.450820467+02:00 O: Fetching repositories...525 repositories found
2019-02-16 02:05:47.290234647+02:00 O: Fetching repositories...525 repositories found
2019-02-17 02:05:52.705250692+02:00 O: Fetching repositories...525 repositories found
2019-02-18 02:04:31.973095461+02:00 O: Fetching repositories...100 repositories found
2019-02-19 02:04:41.782786956+02:00 O: Fetching repositories...100 repositories found
2019-02-20 02:04:35.441645254+02:00 O: Fetching repositories...100 repositories found
2019-02-21 02:04:44.042338783+02:00 O: Fetching repositories...100 repositories found
2019-02-22 02:04:41.641497521+02:00 O: Fetching repositories...100 repositories found

what I mean is that I don't care how internally docker-ls fetches the repos, I want to get them all.

Hi! Barring the possibility of a bug, there is not limitation on the number of repositories that are fetched by docker-ls. "Paging" in this context is just a detail of how the registry API works, it should not influence the result.
Have you checked that all repositories are still stored in your registry? Did anything happen between February 17th and 18th that could account for the change? What happens if you set the --page-size parameter to, say, 50?

Closing for lack of feedback. For what it is worth, querying a repository with multiple tags works as expected for different page sizes, so paging works fine.


Nav 2.0 - New route paths and redirect old paths

Epic ticket lays out the nav nesting, but doesn't address URL paths:
https://github.com/ethyca/fidesplus-licensing/issues/77
Renaming pages and/or creating new page files that redirect to the canonical will keep things working and keep browser history to old pages usable.

Doing this without renaming all the page file/directory names requires some messy config:
https://github.com/ethyca/fides/compare/a251eeac
But renaming a bunch of pages might have major merge problems with in-progress work. Also, git history would be slightly messier. Not sure if it's worth, as the nav works as-is.

Related on the plus side: https://github.com/ethyca/fidesplus/issues/256


Make a Wishlist

When I am a User
When I am on the "Make a Wishlist" page
I enter the name of the wishlist
I enter my name into the author field
I enter the first Item which enables another text box for entering another Item
I click the save Icon
it saves (POST /wishlist)
Do not worry about redirecting
Here is where you can find the save Icon

Hey @thirionlogan , I would like to take on this issue. Let's discuss your expectations!


New version: ParetoSmooth v0.6.5

Registering package: ParetoSmooth
Repository: https://github.com/TuringLang/ParetoSmooth.jl
Created by: @ParadaCarleton
Version: v0.6.5
Commit: bdc841f38c8a9d01dc6065e01520103462e44505
Reviewed by: @ParadaCarleton
Reference: https://github.com/TuringLang/ParetoSmooth.jl/commit/bdc841f38c8a9d01dc6065e01520103462e44505#commitcomment-55940871

Cancel


[BUG] pageInfo.title no longer displayed in browser tab

Environment
Self-Hosted (Docker)
System
No response
Version
3.0.0
Describe the problem
After upgrading from 2.1.2 to 3.0.0 the title configured in pageInfo.title is no longer displayed in the browser tab.
As a workaround I defined the environment variable VUE_APP_TITLE which solves the issue.
I assume this is because of the recent changes to the makeMetaTags const: https://github.com/Lissy93/dashy/commit/a1bf7a69311a95487f30faa7324e270917d56dd7#diff-d7f41ba1aa74f41ef4b0c2337abe593d08092ffae6528a8aa2db712afeee0b66L69-L72
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

I assume this is because of the recent changes to the makeMetaTags const:  a1bf7a6

You are correct. Since the config is now loaded at runtime, yet page title needs to go into the Vue router, which needs to be compiled, it was no longer possible to load that dynamically.
I've pushed an update (not merged yet), which will set the title (client-side) to whatever is in pageInfo.title. It will go live once #1542 is merged.

I was about to post an issue about this haha thanks for this update, much appreciated

Fixed in 3.0.1 :)


No timeout message

Downloading a theme today with a lot of files I got the log:
[development] Fetching assets from *****.myshopify.com
but then the command stopped running without downloading any files or any message.
I resolved the issue by adding timeout: 90s to the config on a hunch but it would be handy to know if the command had timed out. I think this used to be a feature of themekit.

Thanks @ButsAndCats I will look into it because it by default has a value of 30s so it should timeout no matter what.


Change password discrepancy

Hello. The required permissions are listed as such:
Reset password
Change password
Write permissions on lockoutTime
Write permissions on pwdLastSet
Extended rights for "Unexpire Password" on the root object of each domain in that forest, if not already set.
However, "change password" is missing later in the detailed steps.
Do we need to set "Change password" or not?

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

ID: 115ae83a-95dd-5643-bc88-f5447ebb2b99
Version Independent ID: 7462ce84-0a9f-4bfd-7eba-c00928d77865
Content: Enable Microsoft Entra password writeback - Microsoft Entra ID
Content Source: docs/identity/authentication/tutorial-enable-sspr-writeback.md
Service: entra-id
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@aleksbor
Thanks for your feedback! We will investigate and update as appropriate.

Hi @aleksbor
You are correct that the Change password permission is not mentioned in the detailed steps. However, it is required for password writeback to work correctly. So, in addition to the permissions listed in the document, you also need to assign the "Change password" permission to the account specified in Azure AD Connect.
Please go through this below link for your reference.
 Note


Fix compiler warnings about read API

Check the return value when semu calls read API to read content
from STDIN. If there is an error or EOF, we can ignore further
UART operations.

Check the return value when semu calls fread API to read
content from binary or image. If the size of read content is less
than requested size, we trigger a fatal error to exit semu.

Thank @gagachang for contributing!


[Datafactory] Remove readOnly flag on github hostName property

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Related task: https://msdata.visualstudio.com/Azure Data Factory/_workitems/edit/267868

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Hi @hvermis , can you take a look at the change?

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

@azuresdkci regenerate azure-sdk-for-go

@AutorestCI regenerate azure-sdk-for-go

@AutorestCI regenerate azure-sdk-for-go


oC10 and oCIS responses when trying to delete non-existing group request are not identical

Steps to reproduce
curl -u admin:admin -X DELETE https://localhost:9200/ocs/v1.php/cloud/groups/nonExisting

Expected behavior
oC10 and oCIS to have identical response
Actual behavior
oC10
<?xml version="1.0"?>
<ocs>
  <meta>
    <status>failure</status>
    <statuscode>101</statuscode>
    <message/>
  </meta>
  <data/>
</ocs>

oCIS
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>error</status>
    <statuscode>998</statuscode>
    <message>The requested group could not be found</message>
  </meta>
</ocs>

Setup
oCIS build from git

Similiar to https://github.com/owncloud/ocis/issues/1777


Installation of github version

Hello
When installing github version in anaconda with this line : pip install git+https://www.github.com/mouseland/cellpose.git
it says :
ERROR: Error [WinError 2] The system cannot find the file specified while executing command git clone -q https://www.github.com/mouseland/cellpose.git 'C:\Users\REVOLUTION - K30\AppData\Local\Temp\pip-req-build-0j3ox5i0'
ERROR: Cannot find command 'git' - do you have 'git' installed and in your PATH?
Do you have any idea where to find it ? thank you

Hi, it seems that you do not have installed git in your conda environment,
first try the command:
conda install git
then :
pip install git+https://www.github.com/mouseland/cellpose.git


Cannot install latest version 3.1.0 from npm

npm dist-tag ls madge
latest: 3.1.0

npm i --exact<EMAIL_ADDRESS>
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR!      C:\Users\sampo.kivisto\AppData\Roaming\npm-cache\_logs\2018-05-24T07_17_38_728Z-debug.log

npm i --exact madge@latest

npm notice created a lockfile as package-lock.json. You should commit this file.
+<EMAIL_ADDRESS>added 122 packages from 94 contributors in 10.861s
[!] 1 vulnerability found [208 packages audited]
    Severity: 1 Low
    Run `npm audit` for more detail

I know NPM had some issues with the registry when I published. Something must have been messed up. I republished madge as v3.1.1 and it seems to work now.

Seems to work now! 👍
thanks


chore(minsize): remove brotlic because it takes too long to compile

#2954  👈
main

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

Join @Boshen and the rest of your teammates on  Graphite


Feature Request: Retry Failed Tests

Based on conversation in #705
it might be good to have a retry failed test mechanism to help alleviate flaky tests. Similar to repeat but retry would only occur if a test failure (or http connection / request timeout) occurs.
Assume the cli param would look something like --retry N where N is the max number of retries permitted before giving up and reporting the test failure / error.
Thanks!

hi I have not forgotten the issue. I agree with you that for flaky tests a retry mechanism would not be bad. I just need to research first how other tools handle these tests (duplicate in junit export, or only last result,...).


MM-37326: Inline editing

Summary
This PR makes both the title and the description editable inline. It also removes the Description field from the interactive dialog, making the inline edition the only way to change the description.
https://user-images.githubusercontent.com/3924815/127485888-f2872e2b-5982-4071-9bef-8278045123ce.mp4
When editing the title, hitting Enter closes the edition and saves the new title. For the description, I chose Ctrl+Enter for that. Both the title and description are automatically saved whenever the user clicks outside of the input area.
As you can see in the video and in the code, changing the run name is actually a channel name change. It was the most straightforward way to do it given the time constraints.
This branch is based off of #656, I'll change it to master as soon as that one's merged.
Ticket Link
https://mattermost.atlassian.net/browse/MM-37326
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[X] Unit tests updated

By the way, the title ellipsizes when it overflows, taking also into account the presence of the top section buttons.
https://user-images.githubusercontent.com/3924815/127487064-2e569fe5-c8fc-4fe5-9107-8eecb5043f6f.mp4

I'm starting to like answering to questions with videos, it's really easy :joy: @abhijit-singh, there you go:
https://user-images.githubusercontent.com/3924815/127502345-8ef04e0d-02b8-41e5-ad73-49b3bd486b8b.mp4
When you click either in the title or the description, the caret is always at the end. But the title does not "scroll" horizontally to see it, I had to hit the End key for it to show. That's a bit annoying.


Make corrections in tutorial-0

Made directions for adding tutorial0 directory clearer. Also made a few formatting corrections.

Thanks for the patch!

Yay! :yum: :yum:


Add public keys to getAddresses response

Currently only address and type are returned

Super important addition – is this a quick one we can release this week?

Please do! 🙏

Public keys can't be derived from addresses, because addresses are hashes. You need to use the private key. @0xVikasRushi
Should users been informed about exporting public keys vs addresses only? @markmhx

@0xVikasRushi I might suggest checking out how the authentication endpoint returns public keys and using that method, though @kyranjamie can confirm whether there's a better approach: https://hirowallet.gitbook.io/developers/bitcoin/connect-users/authenticate-users
@friedger what kinds of info do you have in mind?

@markmhx In the popup of authentication show what is exported from the wallet so that we don't get disappointments like ledger did.


Microsoft.Data.SqlClient.SqlConnection' threw an exception with SnapshotCollector 1.4.0 and 1.4.1

No issue with the version : <IP_ADDRESS> of Microsoft.ApplicationInsights.SnapshotCollector
Since the upgrade to 1.4.0 (and same error with 1.4.1)
When we call EF core call to the SQL DB we get this error message :
System.TypeInitializationException: 'The type initializer for 'Microsoft.Data.SqlClient.SqlConnection' threw an exception.'
ArgumentException: Delegates must be of the same type.
at System.MulticastDelegate.CombineImpl(Delegate follow)
at System.Runtime.Loader.AssemblyLoadContext.add__unloading(Action1 value) at System.Runtime.Loader.AssemblyLoadContext.add_Unloading(Action1 value)
at Microsoft.Data.SqlClient.SqlDiagnosticListener..ctor(String name)
at Microsoft.Data.SqlClient.SqlConnection..cctor()

Thank you ! :-)

i confirm the target version is net5.0 in the csproj ;)

@didaskein please upgrade to 1.4.2 and try again. Let me know if there are further problems.

I confirm, it's working ! thank you for the fix ;-)


Docker Support

Support Docker compose
The ability to keep training model with the need to rebuild web
Training the Model
docker-compose build train

Running Web
docker-compose build web && docker-compose up web

@mayooear mayooear


Return the correct reply packet type of Chrony reply packets

Changes the return value function GetType to be of type ReplyType instead of type PacketType. The latter merely captures whether a given packet is a request or a reply, which is thus redundant given that GetType() operates on a ResponsePacket that by definition is always a reply (same argument for ReplyHead).
The comment of GetType suggests that it returns the "reply packet type", which is precisely what type ReplyType captures according to its documentation. We therefore assume that this to be a bug.
Also now exports the different ReplyType constants such that they can be used along with what GetType() now returns.

Thank you for this contribution!


Add "list storage" command

If we use the Store task, unless we know where everything is stored into, we have no way to know what's in the persistent storage place (which should be an àcutectl` configuration knob).  This command will list all directories inside the storage area and how many files are in each.

Committed in d9aa5c9c10933c10aa58e94abe049791a9ef9180.


Add an endpoint which returns the version and commit hash

When debugging issues with a running service, it can be useful to know which version is running. We should embed this at build time and expose it over the HTTP interface. This already exists in CCF as the /node/version endpoint, which returns the version of the framework.
We should make it clear what the behaviour is when multiple versions are running. We may want both a /app/node_version and a /app/leader_version endpoint, where the former never gets forwarded and the latter always does.
This is of course a self-reported value, used for debugging only. It does not replace the existing code identity managed by CCF.

Differentiating between primary and follower is not very useful here because each node has its own view of what the primary is. To get a full picture of all nodes this information would have to come from the KV and stored as node_data, however, that happens as part of governance and is not what we want here.
When moving to containers, https://github.com/microsoft/CCF/issues/4705 will address the issue and allow an executor to store metadata that can then be retrieved for all executors on a single endpoint.
In the meantime, the only thing that really makes sense and should be good enough is to expose a node-local endpoint. The metadata would be assembled from constants compiled into the code. If nodes are behind a load balancer and not individually accessible then you will get the metadata from a random node, but I think assuming the network is in a stable state is good enough in the meantime until we switch to containers.


Regression from original

I've tested your torchscript models on linux with A6000 gpu.
Regression 1:
Running the original sam huge model, I get 3 output masks from a point prompt, but efficient-sam only outputs 1 mask.
Regression 2:
The original sam offers 2 stage inference using SamPredictor.setimage and SamPredictor.predict but efficient-sam has only 1 stage of inference.
Speed:
Original sam (huge) inference stage 1 - about 450ms, stage 2 - 25ms. This means interactive segmentation adjusting points/boxes can be done at 40fps.
Efficient sam (small) inference one stage - about 105ms. Overall 4-5 times faster but now rather blocky for interactive picking.
Efficient sam tiny - about 75ms. Mask quality not so great.
I haven't looked into the mask quality much and whether I should be comparing one of the smaller sam models. I'd be interested to know your thoughts/plans. Thanks for the work.

@Chris-toe-pher did you also check the inference time on CPU? what input size you tested out the models?

I was using standard HD inputs 1920x1080. Sam resized everything to 1024x1024 internally, I didn't experiment with resizing yet. Of course it can be hard to compare if you change all these things, apples and pears are both tasty.

@Chris-toe-pher,
1, EfficientSAM also outputs 3 masks. The mask with max predicted iou will be used as the final input. @klightz can you link it to your colab code?
2, Our code is based on our internal infra, which makes some changes for efficient training purpose. @bala can you share more context here? We are thinking if we can change it back for 2-stage inference.
3, For EfficientSAM, we include all the preprocess and the postprocess for the final throughput. @klightz can you share more context here?

Actually our head implementation is same as SAM, which means we also get 3 masks at output, we are doing a post processing to take the mask with largest predicted IoU as the final output. Additionally, there are some image reshape operator in the torchscript which will further slow the speed if you directly profiling the whole torchscript. In SAM, it is implemented when setting the image.


Update lodash to 4.x

Currently have a dependency in a project for lodash 4.x and looks like this is at 3.10 and the package layout is much different.... no longer an object folder

I will remove lodash as a dependency altogether, it is not really needed.


srmv2 stageout implementation fails for file paths containing consecutive slashes

The srm v2 stageout implementation determines the size of the written file by doing srmls on the remote PFN and then grep for the remote path (https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/Storage/Backends/SRMV2Impl.py#L197). When the PFN and the path contain consecutive slashes, e.g. (*), this does not work because srmls returns the path with just a single slash and the grep does not match. This results in declaring perfectly successful stageouts as failed.
(*)
srm://lcgsedc01.jinr.ru:8443/srm/managerv2?SFN=/pnfs/jinr.ru/data/cms/store/temp/user/pkonst/logs///pkonst_crab_crab3test-PK-001_121003_101259/Analysis/0000/0/eb423dac-0d47-11e2-893f-003048f1c5ce-23-0-logArchive.tar.gz

Seems it got fixed. @ticoann please close


Display path details without elevation data

It would be nice to have the graph also available for debugging purposes even if no elevation data is present.

e.g display a flat 0m graph with color gradient for elevation=false + debug=true + details=

Here is a workaround patch where I got it working for a graphhopper setup without elevation: https://gist.github.com/karussell/b28d5dbaed9dbb62748499226d7f6463 (the surface part is a different issue)


"Overriding non-@objc declarations from extensions is not supported"

"Overriding non-@objc declarations from extensions is not supported"
I get this error when I try to compile in Swift 4.1, Xcode 9.4.

Hey @johnlietzke, you are probably pointing your podspec to master. If you are using Swift 4, you were supposed to point your Podspec to the swift4 branch. No worries, the master  branch now contains the Swift 4 support, so please just run pod install and it should be fixed!

Patrick, I was unable to get it work using pod install.  Same issue.

On May 20, 2018, at 10:11 AM, Patrick Balestra<EMAIL_ADDRESS>wrote:
Hey @johnlietzke https://github.com/johnlietzke, you are probably pointing your podspec to master. If you are using Swift 4, you were supposed to point your Podspec to the swift4 branch. No worries, the master branch now contains the Swift 4 support, so please just run pod install and it should be fixed!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/BalestraPatrick/ParticlesLoadingView/issues/5#issuecomment-390496815, or mute the thread https://github.com/notifications/unsubscribe-auth/AEABz4qyCqfJ2sd1aKr2xkToPL5w5Apoks5t0aOugaJpZM4UGJAy.

@johnlietzke Did you run also pod update? Please post here your Podfile if you need more help.

Thank for the fast response and quick fix..  That worked. I feel rather dumb.
Best,
John

On May 20, 2018, at 10:29 AM, Patrick Balestra<EMAIL_ADDRESS>wrote:
@johnlietzke https://github.com/johnlietzke Did you run also pod update? Please post here your Podfile if you need more help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/BalestraPatrick/ParticlesLoadingView/issues/5#issuecomment-390498011, or mute the thread https://github.com/notifications/unsubscribe-auth/AEABzwYM8-ZlspJHa0BxAW2ITVbl3CzKks5t0agRgaJpZM4UGJAy.


NEP-35 duck array update

This tests out adding an __array_function__ condition to our is_arraylike check (xref https://github.com/dask/dask/issues/7263#issuecomment-786088835). Let's see if CI passes
cc @pentschev @jakirkham

[ ] Closes https://github.com/dask/dask/issues/7263
[ ] Tests added / passed
[ ] Passes black dask / flake8 dask

cc @shoyer

Just to summarize the test failures we're seeing:

The mindeps build is failing because we support versions of NumPy that predate the addition of __array_function__ which causes is_arraylike to return False on things like NumPy arrays
There is one test, dask/dataframe/tests/test_dataframe.py::test_dask_dataframe_holds_scipy_sparse_containers which is failing because scipy.sparse arrays don't implement __array_function__. FWIW I tracked this test back to https://github.com/dask/dask/pull/3738 where it looks like we don't fully support scipy.sparse arrays inside Dask arrays, but it is useful to partially support for some Dask-ML work (hand chunks off to dask.delayed or da.map_blocks workflows)

We also support CuPy sparse matrices for similar reasons, which likely have similar issues

Thanks @jrbourbeau , you beat me to it on working this PR. 😄

The mindeps build is failing because we support versions of NumPy that predate the addition of __array_function__ which causes is_arraylike to return False on things like NumPy arrays

For this, we'll also want to check for https://github.com/dask/dask/blob/5273e73ced76862e4d73f2ac4e7373c59540c3f0/dask/array/utils.py#L524 .

There is one test, dask/dataframe/tests/test_dataframe.py::test_dask_dataframe_holds_scipy_sparse_containers which is failing because scipy.sparse arrays don't implement __array_function__. FWIW I tracked this test back to #3738 where it looks like we don't fully support scipy.sparse arrays inside Dask arrays, but it is useful to partially support for some Dask-ML work (hand chunks off to dask.delayed or da.map_blocks workflows)

Seems like we'll need to special-case this as well in is_arraylike, it doesn't look like we have a much better alternative.

If there are no further comments I'll propose we include this in the release tomorrow. @jakirkham @pentschev could I ask one of you to run the cupy tests with the changes here to ensure they pass?

If there are no further comments I'll propose we include this in the release tomorrow. @jakirkham @pentschev could I ask one of you to run the cupy tests with the changes here to ensure they pass?

I agree with changes here and tested it locally, the tests pass with the exception of those I mentioned in https://github.com/dask/dask/issues/7324 . I also applied the patch to a start just after #6738 and by doing so all tests would pass, so from the CuPy side I thing we're good.
Thanks @jrbourbeau for working on this! 😄

Thanks for working on this -- yes, this is important to keep Xarray working with dask :)
My only thought is that the name is_arraylike() is not quite appropriate, given that NumPy uses "array like" for a different meaning. I would suggest using the name is_duck_array() instead.

My only thought is that the name is_arraylike() is not quite appropriate, given that NumPy uses "array like" for a different meaning. I would suggest using the name is_duck_array() instead.

I do not oppose doing that, and semantically agree with it. I'm only wondering if renaming that may cause confusion with people, we also have other utility function such as is_dataframe_like and is_series_like with similar meaning, but perhaps renaming and adding that information to docstrings would suffice?

Given this is a bug fix we are trying to get in before a release and I don’t think this function is intended for usage outside Dask, maybe we can punt on function renaming and track that in a new issue?

maybe we can punt on function renaming and track that in a new issue?

+1. @shoyer thanks for bringing this terminology issue up -- I agree there's a mismatch between the is_arraylike method and the term "array-like". Let's discuss in a follow-up issue

Thanks all for reviewing! Your feedback was very useful

Thanks James! 😄

Thanks! I agree, this might be clarified well just by updating the
docstring for this helper function.
On Fri, Mar 5, 2021 at 9:02 AM jakirkham<EMAIL_ADDRESS>wrote:

Thanks James! 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/7321#issuecomment-791551364, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJJFVS3DDSKGHAK7EKYRY3TCEFCFANCNFSM4YTT3AEQ
.

Filed issue ( https://github.com/dask/dask/issues/7327 ) on that point. Also noted updating the docstring. Please feel free to add anything else there 🙂


Update Posts “heard-it-on-the-radio”

Automatically generated by Netlify CMS

👷 Deploy Preview for enchanting-chaja-c384e5 processing.

Name
Link

🔨 Latest commit
b35000d625109a5c6fc769fb5d8a20ea5f602668

🔍 Latest deploy log
https://app.netlify.com/sites/enchanting-chaja-c384e5/deploys/66d38d0c05fff10008dfb1e2


Attempted import error: 'read' is not exported from './io/reader'.

Describe the bug
Getting this error when import danfojs (in typescript, for a React application):
import * as dfd from "danfojs/src/index";
Note that typescript complains about the lack of types as well:
Could not find a declaration file for module 'danfojs/src/index'. '//wsl$/Ubuntu/home/kachkach/workspace/mlconsole/public/node_modules/danfojs/src/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/danfojs` if it exists or add a new declaration (.d.ts) file containing `declare module 'danfojs/src/index';`

To Reproduce
Steps to reproduce the behavior:

Import danfo: import * as dfd from "danfojs/src/index";
Try to create a dataframe: new dfd.DataFrame(data, {columns: columns})
Get this error:

./node_modules/danfojs/src/index.js
Attempted import error: 'read' is not exported from './io/reader'.

Expected behavior
Danfo can be successfully imported.

it seems like this commit 2a0614380edc74dc3cbe481f7c5674d182af92dd removed the method but forgot to update the types

@halflings Thanks for the update. I totally missed that.
FIXED in new release (v0.2.7)


Function accepting njitted functions as arguments is slow

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

I was trying numba 0.38 and the new support for jitted functions as arguments with this code snippet:
# coding: utf-8
from scipy.optimize import newton
from numba import njit
@njit
def func(x):
    return x**3 - 1
@njit
def fprime(x):
    return 3 * x**2
@njit
def njit_newton(func, x0, fprime):
    for _ in range(50):
        fder = fprime(x0)
        fval = func(x0)
        newton_step = fval / fder
        x = x0 - newton_step
        if abs(x - x0) < 1.48e-8:
            return x
        x0 = x

get_ipython().run_line_magic('timeit', 'newton(func.py_func, 1.5, fprime=fprime.py_func)')
get_ipython().run_line_magic('timeit', 'newton(func, 1.5, fprime=fprime)')
get_ipython().run_line_magic('timeit', 'njit_newton.py_func(func, 1.5, fprime=fprime)')
get_ipython().run_line_magic('timeit', 'njit_newton(func, 1.5, fprime=fprime)')

And I found surprising that njit_newton is the slowest of all, while njit_newton.py_func is the fastest:
$ ipython test_perf.py
4.76 µs ± 8.52 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)
4.14 µs ± 30.8 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)
3.58 µs ± 26 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)
20 µs ± 85.3 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

cc @nikita-astronaut
(Inspiration: https://github.com/scipy/scipy/blob/607a21e07dad234f8e63fcf03b7994137a3ccd5b/scipy/optimize/zeros.py#L164-L182)

Thanks for the report. I can reproduce.

I would like to kindly ask how is this issue placed in the general roadmap of numba. For me (in particular for the poliastro project, which has numba as a core requirement) is kind of critical to be able to pass functions as arguments, because it's the kind of thing that would enable us to make reusable, fast code (the Newton's method example is a paradigmatic one). However, I understand that it might be a) difficult to implement, b) less important for numba developers than other features, c) low hanging fruit waiting for a champion or d) others. I appreciate that it was acknowledged as a bug, so if numba devs have some more information on when do they think this could be fixed (short term, medium term, not before 2019) it would be great to know. Thanks for this wonderful library :heart:

By the way, it seems that the problem lies in having functions in the signature, not in calling them:
In [12]: @njit
    ...: def njit_newton3(func, x0, fprime):
    ...:     for _ in range(50):
    ...:         fder = 3 * x0**2
    ...:         fval = x0**3 - 1
    ...:         newton_step = fval / fder
    ...:         x = x0 - newton_step
    ...:         if abs(x - x0) < 1.48e-8:
    ...:             return x
    ...:         x0 = x
    ...:

In [13]: @njit
    ...: def njit_newton4(x0):
    ...:     for _ in range(50):
    ...:         fder = 3 * x0**2
    ...:         fval = x0**3 - 1
    ...:         newton_step = fval / fder
    ...:         x = x0 - newton_step
    ...:         if abs(x - x0) < 1.48e-8:
    ...:             return x
    ...:         x0 = x
    ...:

In [14]: %timeit njit_newton3(func, 1.5, fprime=fprime)
26.8 µs ± 277 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [15]: %timeit njit_newton4(1.5)
268 ns ± 1.16 ns per loop (mean ± std. dev. of 7 runs, 1000000 loops each)

(this is with numba 0.39).

Investigating this further, I discovered that I can workaround the issue by using closures:
In [24]: def newton_generator(func, fprime):
    ...:     @njit
    ...:     def njit_newton_final(x0):
    ...:         for _ in range(50):
    ...:             fder = fprime(x0)
    ...:             fval = func(x0)
    ...:             newton_step = fval / fder
    ...:             x = x0 - newton_step
    ...:             if abs(x - x0) < 1.48e-8:
    ...:                 return x
    ...:             x0 = x
    ...:     return njit_newton_final
    ...:
    ...:

In [25]: newton_func = newton_generator(func, fprime)

In [26]: newton_func(1.5)
Out[26]: 1.0

In [27]: %timeit newton_func(1.5)
297 ns ± 10.7 ns per loop (mean ± std. dev. of 7 runs, 1000000 loops each)

Hi, if possible I'd like to work on this issue.

I couldn't reproduce this bug
In [1]: import numba

In [2]: from numba import njit

In [3]: @njit
   ...: def foo(x):
   ...:     return x
   ...:

In [4]: def bar(x, f):
   ...:     return x
   ...:

In [5]: %timeit foo(1)
160 ns ± 2.8 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

In [6]: %timeit bar(1, foo)
98.1 ns ± 0.184 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

I am using numba '0.44.0dev0+336.gb633849ee'

Sorry, I forgot to put the decorator on bar.

I don't have that much knowledge of how Numba works under the hood. But the LLVM IR generated for both functions is almost the same, except for the entry basic block:

My bet is that even though bar does not use the second argument, the compiler needs to allocate space for it and unpack bot arguments together when it calls @PyArg_UnpackTuple

Thanks for looking into this. I think that because the functions involved have no real work the performance disparity will likely come from dispatch. Taking this example:
@njit
def foo(x):
    return x

@njit
def bar(x, f):
    return x

When bar is called with args which are in Numba's internal type cache (which mostly holds simple and common types) then it dispatches very quickly, e.g. bar(1, 1). Whereas bar(1, foo) dispatches via a slow path as Numba has to go and work out what the type of foo is, as it's not in its type cache this involves call backs to the interpreter (i.e. typeof(jitted_func)). Profiling this with perf and looking at the call hierarchy for the dispatcher I think demonstrates this to be the case:
Simple case bar(1,1):
-   13.15%        _dispatcher.cpython-37m-x86_64-linux-gnu.so
        3.42%        [.] TypeManager::selectOverload
        2.70%        [.] Dispatcher_call
        2.59%        [.] TypeManager::_selectOverload
        1.96%        [.] Rating::Rating
        1.11%        [.] dispatcher_resolve
        0.55%        [.] call_cfunc
        0.46%        [.] TypeManager::isCompatible
        0.37%        [.] typeof_typecode

Case with jitted function dispatch bar(1, foo):
-    2.25%        _dispatcher.cpython-37m-x86_64-linux-gnu.so
        0.41%        [.] Dispatcher_call
        0.27%        [.] TypeManager::_selectOverload
        0.27%        [.] compute_fingerprint
        0.21%        [.] TypeManager::selectOverload
        0.20%        [.] _typecode_fallback
        0.20%        [.] typeof_typecode
        0.18%        [.] call_cfunc
        0.16%        [.] dispatcher_resolve
        0.14%        [.] typecode_using_fingerprint
        0.14%        [.] Rating::Rating
        0.07%        [.] TypeManager::isCompatible

Note that in the case with the jitted function in the call the _typecode_fallback path is in use.

How feasible is it for us to JIT a custom decision tree to pick the right implementation, and update that selection function every time we add a new type?  That would make the fallback path unnecessary, and probably speed up the dispatcher overall to only look for the types that function knows about.

I believe that the decision tree is necessary. There is no need to keep more than one implementation of the same method because if an argument is not used in a function body, one can strip the argument and change all the call sites to reflect this changes.

def sum(a, b):
    return a + b

def mul(a, b):
    return a * b

def bar(x, y, z, f):
	# y is not used
	return f(x, z)

def bar_opt(x, z, f):
    return f(x, z)

bar(2, 5, 10, sum) # is equivalent to call bar_opt(2, 10, sum)
bar(20, 3, 10, mul) # is equivalent to bar_opt(20, 10, mul)

I'm looking into this. When profiling a simple bar_jit(1, foo) example like in https://github.com/numba/numba/issues/2952#issuecomment-492945130, I noticed that a nontrivial amount of time is spend making a repr of the CPUDispatcher object for the function Dispatcher init here: https://github.com/numba/numba/blob/f76c3a5c1600a50588579239e238ac2140c81d95/numba/types/functions.py#L263
If I replace type(%s)" % dispatcher with just "type" it brings the runtime of bar_jit(1, foo) from 5.6 µs down to 4.2 µs. But I don't know if this change actually breaks anything. This obviously doesn't get into the meat of the real problem here, but it seems like a simple gain if it is possible to change this.
(unrelated note: would you be open to removing the import *s from these files? They make it more difficult for me to navigate the codebase because I can't tell where stuff is coming from, and neither can my text editor)

@asmeurer regarding removal of star-imports: if it doesn't break anything due to then missing side-effects, I am all for getting rid of them! 👍 Please feel free to submit a PR for consideration.

For reference, if the functions do any real work, the differences disappear (and strangely reverse, which I cannot explain)
import numba

from numba import njit

@njit
def foo(x):
    a = 0.
    for i in range(10000000):
        a += i
    return a

def bar(x, f):
    a = 0.
    for i in range(10000000):
        a += i
    return a

bar_jit = njit(bar)
foo(1)
%timeit foo(1)
#26.6 ms ± 2 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

bar_jit(1, foo)
%timeit bar_jit(1, foo)
#25.7 ms ± 2 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

@luk-f-a I suspect it's because the real work cost is much greater than the work-out-the-types-to-dispatch cost?

@stuartarchibald , of course, you made that point earlier and I just measured it to confirm your intuition. I've been passing a lot of functions in my code and wanted to make sure that there was no impact from this issue.

Just in case some magic had happened after #5287, I tested again the code in my previous comment and the times are the same.
$ conda list | grep -e numba -e llvm
llvmlite                  0.31.0           py38hf484d3e_0    numba
numba                     0.49.0rc1       np1.11py3.8h04863e7_gdc1c08865_0    numba

I can confirm that this issue exists. However, as mentioned above, the issue does in fact seem to be caused by a cost when calling Numba jitted code from Python.
import numpy as np
import numba as nb

@nb.njit
def foo(x):
    return x

@nb.njit
def foo_bad(x, func):
    return x

@nb.njit
def foo_bad_alt(x, func):
    return func(x)

@nb.njit
def bar(x):
    s = 0.0

    for v in x:
        s += v

    return s

@nb.njit
def bar_bad(x, func):
    s = 0.0

    for v in x:
        s += v

    return s

@nb.njit
def bar_bad_alt(x, func):
    return func(x)

%timeit foo(10)
%timeit foo_bad(10, foo)
%timeit foo_bad_alt(10, foo)

# 167 ns ± 11.3 ns per loop (mean ± std. dev. of 7 runs, 10,000,000 loops each)
# 17.5 µs ± 1.54 µs per loop (mean ± std. dev. of 7 runs, 10,000 loops each)
# 15.7 µs ± 591 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

data = np.random.random(1000000)

%timeit bar(data)
%timeit bar_bad(data, bar)
%timeit bar_bad_alt(data, bar)

# 1.02 ms ± 57.5 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)
# 1.1 ms ± 65.8 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)
# 1.05 ms ± 29.2 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

The difference in performance when comparing the foo functions is great, however, since timeit is called from the Python context these timings are largely affected by Numba invokation costs.
The difference in performance when comparing the bar functions is minimal, because now most of the time is actually spent in the function and not in interfacing between Numba and Python.


[Bug]: do not disable adding sensitive columns for mysql datasource

ODC version
4.2.3
OB version
none
What happened?
now when adding sensitive columns ,  the front-end will filter mysql datasource. We hope to cancel this restriction.
What did you expect to happen?
cancel this restriction.
How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 54622ce47d898da7c82fec32f7f956612c64f361

PASS


[WIP] Dialog import should use safe_load

If you upload a dialog that is a blank file, it breaks badly at the moment, because potential_dialogs = YAML.load(import_file_upload.uploaded_content) with YAML.load("") is false and it won't be caught by Psych. So, we should safe_load to avoid the whole mess.

https://bugzilla.redhat.com/show_bug.cgi?id=1720611
@miq-bot add_label bug
@miq-bot assign @tinaafitz
@miq-bot add_reviewer @eclarizio

Hm, wouldn't check_dialogs_for_validity catch it? A spec for that specific condition would be good, too.

@djberg96 that's the issue, you can't call check_dialogs_for_validity(potential_dialogs) with a false value. So I think not.

@d-m-u Ah, I take it that it tries to access dialog['dialog_tabs'] and bombs with NoMethodError (undefined method '[]' for false:FalseClass), is that right?
Well, since it's the validator's method to validate, I would argue that a conditional should be made within that method to see if dialog is actually present, and raise an error if it's not.

@djberg96 no, it does this:
    dialogs.each do |dialog|```
```false.each``` is bad. But since Erik was involved in writing a bunch of this, I'd like to get his opinion. Since there's already a error catching mechanism before you hit the validity check, it made more sense to me to fail earlier.

@eclarizio what about this? 😆

@eclarizio what about this? 😆

Doesn't safe_load just return nil instead of false? This isn't going to cause that rescue to be hit, it will still blow up trying to iterate over nil?


Change url regex to allow :variables

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
What i'm trying to do is use a pattern to replace for variables in my application, now we use the pattern of :variable but the plugin doesn't allow this kind of character.
Here is the diff that solved my problem:
diff --git a/node_modules/strapi-plugin-menus/admin/src/constants.js b/node_modules/strapi-plugin-menus/admin/src/constants.js
index 29be819..2e9110b 100644
--- a/node_modules/strapi-plugin-menus/admin/src/constants.js
+++ b/node_modules/strapi-plugin-menus/admin/src/constants.js
@@ -14,15 +14,15 @@ export const URL_ABSOLUTE_REGEX = new RegExp(
   '^(https?:\\/\\/)?'+
   '((([a-z\\d]([a-z\\d-]*[a-z\\d])*)\\.)+[a-z]{2,}|'+
   '((\\d{1,3}\\.){3}\\d{1,3}))'+
-  '(\\:\\d+)?(\\/[-a-z\\d%_.~+@]*)*'+
-  '(\\?[-a-z\\d%_.~+@;&=]*)?'+
+  '(\\:\\d+)?(\\/[-a-z\\d%_:.~+@]*)*'+
+  '(\\?[-a-z\\d%_:.~+@;&=]*)?'+
   '(\\#[-a-z\\d_]*)?$',
   'i'
 );

 export const URL_RELATIVE_REGEX = new RegExp(
-  '^(\\/[-a-z\\d%_.~+@]*)*'+
-  '(\\?[-a-z\\d%_.~+@;&=]*)?'+
+  '^(\\/[-a-z\\d%_:.~+@]*)*'+
+  '(\\?[-a-z\\d%_:.~+@;&=]*)?'+
   '(\\#[-a-z\\d_]*)?$',
   'i'
 );
diff --git a/node_modules/strapi-plugin-menus/admin/src/pages/EditView/form-layout.js b/node_modules/strapi-plugin-menus/admin/src/pages/EditView/form-layout.js
index f348482..f92be31 100644
--- a/node_modules/strapi-plugin-menus/admin/src/pages/EditView/form-layout.js
+++ b/node_modules/strapi-plugin-menus/admin/src/pages/EditView/form-layout.js
@@ -61,6 +61,7 @@ const menuItem = [
         id: getTrad( 'form.label.url' ),
         defaultMessage: 'URL',
       },
+      description: 'URL of the menu item. If the URL is external, please add http:// or https://. For parameters, please use the following format: /:param?anotherParam=:anotherParam',
       name: 'url',
       type: 'text',
     },

This issue body was partially generated by patch-package.

Hi again @WeslleyNasRocha  This is now updated in the latest version 1.6.1 of the plugin to allow : characters in URLs 🎉


Ignore NodeLocalDNS when deploying user-provided addons

What this PR does / why we need it:
Ignore NodeLocalDNS when deploying user-provided addons.
Does this PR introduce a user-facing change?:
NONE

/assign @kron4eg

/retest

/retest

/retest

/retest


fix: use events for web-component parent/child communication

Some refactors were done on the following, so they need some quick tests.

[ ] Modal
[ ] Popover

The parent/child changes that were made require more extensive testing for the following components:

[ ] Dropdown
[ ] FormStepper
[ ] RadioGroup
[ ] Tabs

For Angular, Dropdown filter not working

https://github.com/GovAlta/ui-components/assets/7528736/f9a490b8-5436-4d38-bd9e-33d8fc80671e

For React, Form Stepper Not working

This is most likely due to the following missing React code

For Angular, Dropdown filter not working

I can't replicate this issue either. Below is what I see

:tada: This PR is included in version 1.17.0-alpha.52 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.17.0-alpha.26 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How about unzipping the sketch file and generating code based the json files?

I noticed that u have been generated code with svg files which are exported by sketch. As we all know, there are some compatibility between svg and sketch file.
After I find the news about sketch 43: https://sketchplugins.com/d/87-new-file-format-in-sketch-43,  maybe using the sketch source file is better, how do you think?

@Creemli Yep! That's something we're looking into.  I'm also looking at creating a Sketch plugin, which would let you do it right from the app itself

@chrisachard I am also working on this, and has created RN code with formatted sketch file which has many many limits such as naming in one style, grouping with right orders, and so on.
The biggest problem I met is about how to translate the absolute position layout into flex layout, do you have some suggestions? Thank you very much~~

@Creemli That sounds awesome!  If you plan to open source it, I'd love to see it when it's ready.
Yes, converting from absolute to flex box was a big tricky part.  Check out https://github.com/nanohop/sketch-to-react-native/blob/master/src/flex.js for how I did it (start at the "flexBox" function) - but here's the basic algorithm:

Get all the component's x, y, width and height
Put them into a tree based on what is nested inside of what - so try to develop a "parent/child" tree of components
Iterate over that tree, and make wrapping Views where neccessary to put things into flex columns, and then flex rows
Do that recursively until you are done with the tree

I hope that helps some - feel free to reach out with any other questions!


Set openjdk7 to use a specific version

The latest openJDK7 (131) image introduces a SSL security issue. (Already reported here)
An older version solves the test failures. We can revert to use the latest image once the issue is resolved at their end.

LGTM


Update Splice main to version 0.2.0-snapshot.20240816.6736.0.v380341f7 (automatic PR)

This PR updates branch main of Splice from the latest changes as of version 0.2.0-snapshot.20240816.6736.0.v380341f7, commit DACH-NY/canton-network-node@380341f7c

0 files changed.


Do you have plans to support Vercel deployment in the future?

Do you have plans to support Vercel deployment in the future?

If they support docker deployments then we already support it
There is just no pre setup for it

Vercel is a platform to deploy frontend applications and does not support Docker deployments (backend).


Some minor fixes and improvements

Fixed wrong quit button placement when menu is hidden
Reduced sleep and reconfiguration wait times by half (this might adversely effect older displays when DDC read is enabled - but it is disabled by default now)
Disengaged brightness keys after sleep and reconfiguration so it does not interfere with using the brightness keys in the sobering period on M1 macbooks (they wake up superfast)
Modified Swift version number to 5.5 (this had some minor effect on the code - like removal of unneeded return keywords - but will become handy as I can simplify the syntax of some of the asynchronous stuff later)
Bumped app version number to 4.0.2

@JoniVR @the0neyouseek - can you approve this one for me if all is well? Thanks!

Thanks!

Thanks guys. Looking forward to using this on the fast waking M1!


fix: force layout in bounding box

Some tests were flaky because DOM.getBoxModel doesn't force a layout. Maybe it should on the backend?

@JoelEinbinder That’s a nice catch. Yes, getboxmodel has to force layout on the backend. Let’s fix upstream

@JoelEinbinder is this indeed the case and requires fixing in the protocol?

Fixed upstream


Uasynco

I cannot get it to work. Probably because the latest version is now 1.5.4. The previous workaround does not work anymore.
Traceback (most recent call last):
File "boot.py", line 16, in
File "webcam.py", line 42, in run
File "/lib/picoweb/init.py", line 299, in run
File "/lib/uasyncio/core.py", line 163, in run_forever
File "/lib/uasyncio/core.py", line 129, in run_forever
File "/lib/uasyncio/init.py", line 31, in add_reader
TypeError: function expected at most 3 arguments, got 4
Any idea how I can solve this?

I manged to fix it by using a different Micropython fork.  We currently need to use the Falcon build of Micropython. Apparently Pfalcon also wrote Picoweb. I forked the Falcon build and added your changes.
https://github.com/Lennyz1988/micropython.
I made a ready to flash working build.
https://github.com/Lennyz1988/micropython/releases/tag/v1

Thanks @Lennyz1988!
Actually I had somehow overlooked that Picoweb is not targeting standard Micropython, sorry for not realizing that.
Although Picoweb with asyncio support is nice, there is not much that the webcam use case can benefit from.  So I'm wondering, maybe other web server should be used or since this is just one request, just enough HTTP support could be implemented inline directly with just sockets.  That would allow basing on standard Micropython fork, if that is preferred.  I don't have any long term goals with this project though, it is just for a personal need / curiosity...


Context Manager and General Cleanup

Added self.camera_num  to class instantiation. This would mean that users would need to call and assign different names to a new Picamera2 class to use two cameras.
Changed open_camera to open to stay in tune with start,, stop ,close etc. I don't know if it is bad form to use it in a class.
Added enter and exit to allow for use of Picamera2 in a with statement.
Created conversions.py for file or buffer conversions that don't necessarily require Picamera2.
Changed camera_manager attribute to cm to reduce number of characters per line.
Changed verbose_print to __verbose_print so it can't be called by a user.
Changed start_, stop_ to __start, __stop so it can't be called by the user and to limit confusion when using interactive IDEs.
Added initialize and acquire functions to give more flexibility to developers.
Changed time.time() to time.monotonic() to remove interference with clock changes (although unlikely).
Added reset_flags, which could probably be made private.
Minor changes to messages displayed with errors.
Added camera id (cid) and camera index (cidx) to initialize. This gives the class access to camera identifying information that the user may not know or may input incorrectly at instance creation.
Moved self.sensor_resolution to still_configuration function because it had the only usage.
Cleaned up some lines to bring them close to pep8.

I now see a mistake with moving self.sensor_resolution, so that can be moved back to open().

Hi, thanks very much for doing all this. I'd like to adopt most of these changes, perhaps there are a few where we might think about exactly how to present them.
Mostly I think I'd like to split up the commits so that it's clear what each one is. Perhaps we could have a "PEP8" commit on it's own? Commits that just rename variables and functions might be separate from ones that rearrange code, perhaps. Also perhaps we could remove any diffs that do absolutely nothing (e.g. deleting newlines from the ends of files).
The purpose is simply to start making commits easier to review and to follow over time. I appreciate that things have been a bit random in the rush to get something out there for folks to try, but I would like to start improving the process a little. What do you think?

Can do.  I'll work on separating them out over the next couple of days. If you see anything else, let me know.


PhantomJS exited with return value 1

Error when capturing and sending screenshot: PhantomJS exited with return value 1
Does anybody know how to solve it?
i have tried to use these:
sudo apt-get update
sudo apt-get install build-essential chrpath libssl-dev libxft-dev
sudo apt-get install libfreetype6 libfreetype6-dev
sudo apt-get install libfontconfig1 libfontconfig1-dev

and its not working.
what can i do to solve this?

Screenshots won't be a thing for the new bot, what you should do is edit the code and disable the screenshots that way. I don't remember the exact lines, but you can look in the pinned messages on the discord server to find them.

just asking how would i be able to see the trades?

just asking how would i be able to see the trades?

The console ;)

but lets say i am not at home?
just asking

Sorry but that's your problem my dude, I won't be working on the old bot

okay ty for your answer and work


Documentation added for digital signature verification

Adding documentation describing the I/O Events new digital signature feature
Description
This ticket

adds documentation for digital signature.
documentation describing the complete digital signature signing process of I/O Events
describing the additional verification of the target recipient
documentation describing the customer experience with the changed event signing process

See ticket CI-4936 and CI-4937 for details.
Also follow this wiki here for additional information
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@ledroff/ @shikhartanwar : let me know if the changes look good to be merged now. thanks


fix(*): gRPC and cJSON's behavior to empty array

Summary
Lua does not distinguish empty arrays and tables, which makes empty array decoded from gRPC gateway be encoded as {} by cJSON.
The fix makes use of cjson.empty_array_mt to hint the cJSON.
Special thanks to @starwing, who spent their public holidays adapting new features for this issue.
Checklist

[x] The Pull Request has tests
[x] There's an entry in the CHANGELOG
[ ] N/A There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

Bumped lua-protobuf
Use cjson.empty_array_t for arrays
Tests

Issue reference
https://github.com/starwing/lua-protobuf/pull/240
Fix FTI-5002
Fix #10801
Review suggestion

Please go through the discussion https://github.com/starwing/lua-protobuf/pull/240 before reviewing;
*.pb.go are auto-generated

Need a person familiar with Go to double check.

rebased onto master to fix conflicts; good to merge whenever CI is :green_circle:

This fix was added very late so it was missing a cherrypick into 3.3 (notice that this PR targets master)


feature: Discover unused ClusterRoleBindings

Is your feature request related to a problem?
ClusterRoleBindings can be created while referencing non-existing users/groups/ServiceAccounts on one hand or ClusterRoles on the other hand.
Go through all existing ClusterRoleBindings and verify if they are applied to existing subjects and ClusterRoles.
Utilize ShowReason flag to indicate that the reason the ClusterRoleBinding was considered unused was because it referenced an unused subject or ClusterRole.
NOTE: Since a ClusterRoleBinding can include multiple subject references, discovering a single non-existing subject (one of several existing ones) might indicate the ClusterRoleBinding as unused while it actually is, in that case, it shouldn't be considered as unused.

Examples
In the attached example, we could see a ClusterRoleBinding with references to both users: alice & bob.

Assuming both users alice & bob does not exist, the ClusterRole is not applied to them, hence the ClusterRoleBinding will be considered as UNUSED.
Assuming both users alice & bob exist, but the ClusterRole does not exist, it is not applied to them, hence the ClusterRoleBinding will be considered as UNUSED.
Assuming user alice does exist and the ClusterRole is applied to it, even while bob does not exist - the ClusterRoleBinding will be considered as USED.

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: read-pods-global
subjects:
- kind: User
  name: alice
  apiGroup: rbac.authorization.k8s.io
- kind: User
  name: bob
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: pod-reader
  apiGroup: rbac.authorization.k8s.io

Describe the solution you'd like
$ kor clusterrolebindings
Unused ClusterRoleBindings:
+---+----------------+----------------------------------------------+-----------------------------+
| # | NAMESPACE |   RESOURCE NAME |                         REASON                                |
+---+----------------+----------------------------------------------+-----------------------------+
| 1 |           | example-crb-1   | ClusterRoleBinding references a non-existing ServiceAccount   |
| 2 |           | example-crb-2   | ClusterRoleBinding references a non-existing ClusterRole      |
+---+----------------+----------------------------------------------+-----------------------------+

Feature checklist

[ ] pkg/kor/clusterrolebindings.go
[ ] pkg/kor/clusterrolebindings_test.go
[ ] pkg/kor/create_test_resources.go
[ ] pkg/kor/all.go
[ ] pkg/kor/delete.go
[ ] pkg/kor/multi.go
[ ] pkg/kor/exceptions/clusterrolebindings
[ ] cmd/kor/clusterrolebindings.go
[ ] charts/kor/templates/role.yaml
[ ] README.md

@nati-elmaliach would you also like to claim this issue following #362?
The logic would be pretty similar.

@nati-elmaliach would you also like to claim this issue following #362? The logic would be pretty similar.

Sure thing. @yonahd please assign it to me.

@doronkg @yonahd
Just a quick clarification:

A ClusterRoleBinding is not tied to any specific namespace. How would you prefer the output to be displayed? Should it be presented as an entirely new table like --group-by=resource does?

This command make no sense kor clsuterrolebindings --include-namespaces. should it throw, show a warning, or ignored ?

Great questions
You can see how it is handled in the persistent volume resource.
Let me know if this covers your questions


Serving nodes.json from memory

I moved index.html to / and changes the HttpHandler to serve nodes.json from memory.

I'm ashamed


v1.3 of Fabric Essentials is not loading in MCreator

I am trying to load this plugin but its not loading.
Version: 1.3 [Latest]
MCreator: 2022.3

Go into more detail. I currently have the plugin loaded so I am positive that this issue is invalid.

Go into more detail. I currently have the plugin loaded so I am positive that this issue is invalid.

Actually, I download the plugin and tried to import it but in UI of MCreator, it is not showing nothing like 'Fabric Essentials' or something. Let me try again. if it didn't worked then I will update this comment.

you need mcreator 2022.3 and the latest version of the fabric generator.

Seems I zipped the file wrong on accident. Updating the file now.

Seems I zipped the file wrong on accident. Updating the file now.

Yea, Ok. Thanks. It happens.
And YAY! I again found a valid bug to report a dev.


Expand & collapse button click issue

Sometimes clicking expand & collapse button does not do anything. Possibly because of drag & click events confrontation. Needs investigation

Fixed in v3


HHH-13493 - For a native query, the SessionImpl class does not call applyQuerySettingsAndHints

https://hibernate.atlassian.net/browse/HHH-13493

hi @vladmihalcea , could you review your test?
f I isolate and revert the fix, it still passes the test. I guess we need a better way to test for this.

@Sanne
Without the fix, I get:
java.lang.AssertionError: Should have thrown lock timeout exception!

	at org.junit.Assert.fail(Assert.java:88)
	at org.hibernate.jpa.test.lock.NativeSQLQueryTimeoutTest.lambda$test$0(NativeSQLQueryTimeoutTest.java:47)
	at org.hibernate.testing.transaction.TransactionUtil.doInJPA(TransactionUtil.java:210)
	at org.hibernate.testing.transaction.TransactionUtil.doInJPA(TransactionUtil.java:251)
	at org.hibernate.jpa.test.lock.NativeSQLQueryTimeoutTest.test(NativeSQLQueryTimeoutTest.java:39)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:748)

I haven't rebased it, so I simply retest the PR branch. I could only run it with IDEA 2017. The new one does not even run the tests since it cannot locate the hibernate.properties.
So, I'm not sure how it works for you without the fix.

Thanks @vladmihalcea  ,
applied upstream

@Thanks @dreab8
If you have time, can you take a look at these two PRs as well:

HHH-13614 Allow the IntegratorProvider to be supplied via its FQN in the JPA persistence.xml
HHH-13608 Oracle8iDialect should use CASE_INSENSITIVE pattern matching when checking the statement type

I think both are very useful and pose no risk to integrate them.

Hi @vladmihalcea , you are welcome, as soon as I have time I'll give a look at them ( by the way I'll try to do it before the next release)

Great, thanks.


Outdated command can update all outdated candidates

The purpose of this PR is to provide a way to update all the outdated candidates and set them as the default version.
When running sdk outdated, with or without a specific candidate, and only if there is any outdated candidate, ask the user for confirmation on updating all of them and setting them as the default, and do so accordingly.

Sure, it totally makes sense. I've updated the commit and the PR description.

Excellent work! Thanks for your valuable contribution!

@pbassiner I made some minor improvements in what/how is displayed on CLI. Let me know if you agree.

LGTM. Maybe you could consider adding auto_answer_outdated as a config parameter as well and then avoiding the interactive question accordingly.

We already have such a config in the form of sdkman_auto_answer. We should probably check for the case that this is present in sdkman-install.sh too. However, our case is slightly different since we only want to fast track the installation when driven from the outdated command.
I'll add a further test for this and include the third case.


grammar: macports compatibility

Macports is quite popular a way to install some application to macOS and it is shame that it doesn't support such way by default.

Thanks!


Multiple signature verification

When checking signatures on new TBB binaries, require a more complex signature set than just Mike Perry. Perhaps Mike Perry and one of these several others.

It looks like the official Tor Browser Developers (signing key) with fingerprint EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290 is the only signing key now.


Use picovoice.ai is easy to make wakeup word

Use picovoice.ai is easy to make wakeup word
https://picovoice.ai/docs/quick-start/porcupine-web/

I have seen picovoice. Correct me if I'm wrong, but it seems it's quite expensive and they don't have a free option for open source projects: https://picovoice.ai/pricing/

I have seen picovoice. Correct me if I'm wrong, but it seems it's quite expensive and they don't have a free option for open source projects: https://picovoice.ai/pricing/
you can free to create to three wake up words, no need pay.

you can do with with the existing TTS fyi.   just need to add the code with the keyword which tell it to send down the path else. ignore.


regex subscription causes librdkafka to fault

I'm getting reproducible faulting in librdkafka.dll on the consumer side with 0.11.3:
Faulting module name: librdkafka.dll
Exception code: 0xc0000409
Fault offset: 0x00111c45

This has only started happening since we started tapping into a live stream of data so are now testing with some decent volume. Furthermore it only happens when the consumer is well behind in the topic, therefore trying to catch up as fast as possible.
When the problem happens the process just crashes and its not possible to debug. The only information available is in the Windows event log and a Windows Error Report is created but it doesn't look to be much use.
I can reproduce this with the simple code found in the AdvancedConsumer project Poll example, I just point it at my topic and run from the beginning.
Once it crashes the first time if I restart the consumer it always crashes within 2 minutes, but its not related to specific messages in the topic as it will easily get past the previous offset it stopped on.
No logs of interest on the broker side.
I've tried upgrading (just librdkafka) to 0.11.4-RC2, but no change.

I've been scratching my head for a day experimenting with different things and the only breakthrough I've had is that if I don't output anything to the Console in the OnMessage event handler, everything works fine (entire topic of 1.6 million messages is consumed).  What's more bizarre is that I do have "debug" set to "all" so there is plenty of Console output from librdkafka!
The only errors coming out from the debug log are these (regularly seen, and these come out even when everything is working so I don't think this is the issue):
7|2018-03-28 14:39:45.145|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev03:9092/3]: kafkadev03:9092/3: Protocol parse failure at 1031386/1048631 (rd_kafka_msgset_reader_v2:802) (incorrect broker.version.fallback?)
7|2018-03-28 14:39:45.145|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev03:9092/3]: kafkadev03:9092/3: product_raw [4] MessageSet at offset 396382 payload size 21245 > 17245 remaining bytes
7|2018-03-28 14:39:45.152|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev03:9092/3]: kafkadev03:9092/3: Protocol parse failure at 2094236/2097237 (rd_kafka_msgset_reader_v2:802) (incorrect broker.version.fallback?)
7|2018-03-28 14:39:45.152|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev03:9092/3]: kafkadev03:9092/3: product_raw [1] MessageSet at offset 392741 payload size 27264 > 3001 remaining bytes
7|2018-03-28 14:39:45.167|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev02:9092/2]: kafkadev02:9092/2: Protocol parse failure at 1032453/1048631 (rd_kafka_msgset_reader_v2:802) (incorrect broker.version.fallback?)
7|2018-03-28 14:39:45.168|rdkafka#consumer-1|PROTOERR| [thrd:kafkadev02:9092/2]: kafkadev02:9092/2: product_raw [3] MessageSet at offset 399982 payload size 25974 > 16178 remaining bytes

[x] Confluent.Kafka nuget version: 0.11.3
[x] Apache Kafka version: 1.0.0 (confluent docker running in Ubuntu)
[x] Provide logs (with "debug" : "..." as necessary in configuration)
[x] Operating system: Windows 10

what client was used to produce the messages into Kafka?

The same client (Confluent.Kafka 0.11.3) on a different machine.
The messages are Avro+SR if that makes any difference.  I have also noticed that it seems to work for a .NET Core Console app (all the crashes have been on .NET Framework Console app), though I do need to run it a few more times to be sure.

The protocol parse failures at debug level (7|..)  are expected and okay (the broker may send partial responses).

I'm doing various other tests and will update here observations:

Using .NET Core is rock solid so far, can't reproduce the crash.
Offloading the Console output to another thread with Task.Run seems to improve things - it takes up to 10 minutes to crash rather than 1-2 mins.  But it does still crash.
Doing console output outside of the event handlers (i.e. outside of the poll thread) so far does not crash.
To rule out the messages themselves being the issue, I filled another topic with 20m 1k messages using kafka-producer-perf-test and pointed the consumer at that.  It still crashed.

I didn't mention it before but the topic is using lz4 compression.

I've experiencing the same. My little test program exits with code: 0xc0000409 when consuming a topic with lz4 compression, which has messages in plain string keys and values. It just terminate in a few seconds.

@raycheung, good to know someone else is seeing this too!  Does your test program output to the console?
I'm currently running a test on a topic with no compression and not seeing the issue after about 1 hour.  I'll try other compression types to narrow this down a bit.

update: I had this running for > 4hrs yesterday, and the problem did not occur.
which cloud provider? i will hopefully get a chance to run some more tests ...

Rackspace

@mhowlett I'm not yet an expert of F# and definitely can't represent anything. :smiley: I found the API straightforward enough and plays nicely with my F# code, however if we have an asynchronous consumer it would be perfect, tracked here: https://github.com/confluentinc/confluent-kafka-dotnet/issues/487.

@raycheung - same comment as #487 - feel free to jot down any pseudo code as to what you think such an API should look like :-), I'll take note.

Running into the same issue with the Consumer. .net 4.6.1 with one instance of the consumer running using poll in a windows service, it works fine. If we increase the number of consumer instances to more than 1, it fails after few seconds, or it fails instantaneously while starting the service. If you try to start it n number of times once in while it starts fine and fails after a while ranging from few seconds to minutes.
Initially was using 0.11.4 then tried using 0.11.1 both having the same behavior.

@mhowlett @comdw
We have nailed down what was causing this behavior for us. The Subscribe method we had a regex, to match a list of topics and that is causing heap corruption / above ntdll exception when there are more than 1 consumer instances with a process.
The issue goes away by not using Regex pattern and specifying the topics explicitly.

cc @edenhill

We have the same ptoblem on a Windows 10 physical machine with 0.11.4.
The problem arises quickly if the consumer is "on late", while it is harder to reproduce if the consumer has only a few messages to consume.
Switching from lz4 to gzip solved the problem

@edenhill  Regex we had "^spo."

its 2020 ! still not fixed ?

Can you provide your original regexps and some example (matched) topic names?

i saw it as open issue. thats why im asking if there is any progress
On Fri, Jun 12, 2020, 10:22 Magnus Edenhill<EMAIL_ADDRESS>wrote:

Can you provide your original regexps and some example (matched) topic
names?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/confluentinc/confluent-kafka-dotnet/issues/482#issuecomment-643113769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJVVU4PZYJWKUENKZ6XO2LRWHJURANCNFSM4EX3HRYA
.

@Nadav-Revuze If you are experiencing this issue please provide your regexp, the list of topics in the cluster (needed to reproduce), your client and OS version.

Fixed in https://github.com/edenhill/librdkafka/pull/2949


CWL tool+workflow launching with yaml

Feature Request
Desired behaviour
A number of examples use yaml to parametrize rather than json. While using something like http://yamltojson.com/ is pretty trivial, it is inconvenient. Add a parameter to dockstore tool launch and dockstore workflow launch to accept yaml instead of json (convert to json behind the scenes to do file provisioning).

Helpful link http://yamltojson.com/#java


⚠ PrivateHD has degraded performance

In 774dce2, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 5862 ms

Resolved: PrivateHD performance has improved in b2c6c90.


Swagger Parser OpenAPI class does not allow same path, different verbs

I am using io.swagger.parser.v3:swagger-parser:2.0.17 to parse swagger OpenAPI class from swagger json.
If I have two resource methods with same path, but with different verbs, for example
GET /profile.  - read the profile
POST /profile  - create or update a profile
OpenAPI class only keep one. When looked at the code, the OpenAPI.Paths class uses a Linked Hash Map to store paths, where key will be String type to hold the resource path. This contradicts with swagger v3 open api, where (path + verb) maintains the uniqueness, not just path itself.
Can you please let us know whether we have a workaround for this, or validity of my case ?

In your file, you should have the path one time, and the two verbs under that single path. Is that the case?

I am using javax.ws.rs GET and Path Java annotations in my rest resource methods to indicate it (code first approach, generating swagger v2 from BeanConfig). Then use the io.swagger.v3.parser.converter.SwaggerConverter to convert swagger v2 in to v3.
Code snippet.
// First process to generate swagger  json from code.
Swagger swaggerV2 = getBeanConfig(config.get("swagger")).getSwagger();
String swaggerV2String = Files.write(Paths.get(target), Json.pretty(swagger).getBytes());
// Second process take step 1 swaggerv2 json and convert it to v3 openapi.
SwaggerConverter converter = new SwaggerConverter();
ParseOptions parseOptions = new ParseOptions();
parseOptions.setResolve(true);
SwaggerParseResult result = converter.readContents(swaggerV2String, null, parseOptions);
OpenAPI api = result.getOpenAPI();

Why are you not just generating v3 from your code?

I think the issue was, PathItem can hold all the Verbs, so having Paths maintain a HashMap is fine. Thanks for the clue.

Closing ticket, please reopen if you're still experiencing issues or have more questions.


think about save as gist feature

see:
http://stackoverflow.com/questions/18667303/how-to-create-a-github-gist-with-api
and also load from gist file based on the hashtag

https://developer.github.com/v3/gists/


ec2-room-validation

Checks for the best subnet capacity and runs the instances

Codecov Report

Merging #77 into master will decrease coverage by 0.13%.
The diff coverage is 15.38%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
- Coverage    22.1%   21.96%   -0.14%
==========================================
  Files          44       44
  Lines        2063     2112      +49
  Branches      225      239      +14
==========================================
+ Hits          456      464       +8
- Misses       1585     1626      +41
  Partials       22       22

Impacted Files
Coverage Δ

lib/python/treadmill_aws/cli/admin/aws/instance.py
0% <0%> (ø)
:arrow_up:

lib/python/treadmill_aws/aws.py
41.17% <100%> (+18.09%)
:arrow_up:

lib/python/treadmill_aws/hostmanager.py
24.24% <14.28%> (-7.34%)
:arrow_down:

Continue to review full report at Codecov.

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


Cut a new release on pypi

Much obliged :)

Also, I have to ask; why did you remove the tests? Back in e4a66cde?

Cheers :)
I ask mainly because I ran into a few bugs/typos which could have been avoided with tests, in particular one which seems to have been around since you added the code to the repo.
In the server.py file, you use geometry, but the argument to the function is Geometry.
A few others (errors as reported by the flake8 tool);

arcrest\geometry.py:132:12: F821 undefined name 'self'
arcrest\geometry.py:133:30: F821 undefined name 'self'
arcrest\geometry.py:134:14: F821 undefined name 'self'
arcrest\geometry.py:135:31: F821 undefined name 'self'
arcrest\gptypes.py:177:31: F821 undefined name 'reduce'
arcrest\gptypes.py:220:31: F821 undefined name 'reduce'
arcrest\server.py:960:52: F821 undefined name 'GenerateKMLResult'
arcrest\server.py:2308:54: F821 undefined name 'version'
arcrest\server.py:2507:12: F821 undefined name 'sr'
arcrest\server.py:2509:31: F821 undefined name 'Geometry'
arcrest\server.py:2515:61: F821 undefined name 'geometryType'
arcrest\admin\admin_objects.py:59:49: F821 undefined name 'System'
arcrest\admin\cmdline.py:588:12: F821 undefined name 'exportcacheargs'

There are also a few instances of basestring usage without it having being assigned to under python 3.
In any case, I will submit a pull request later today/tonight fixing a few issues. And I might see if I can't get those old tests running with a mocked backend :)