Import from USB on RPi4 doesn't set i2c parameters inside /boot/config.txt

HassOS release with the issue:
HassOS 3.7
Supervisor logs:
Traceback (most recent call last):   File "/usr/local/lib/python3.7/site-packages/smbus/smbus.py", line 81, in open     self._fd = os.open(path, os.O_RDWR, 0) FileNotFoundError: [Errno 2] No such file or directory: '/dev/i2c-1'
Host Logs:
ls -l /dev/i2c*: ls: /dev/i2c*: No such file or directory
Description of problem:
Following instructions Here to enable i2c works fine for RPi 3, using the same USB stick on the RPi 4, it doesn't update /boot/config.txt therefore doesn't enable i2c
Manually uncommenting dtparam=i2c_arm=on and adding dtparam=i2c1=on then rebooting the host enables i2c.
ls -l /dev/i2c* crw-------    1 root     root       89,   1 Jan  5 19:43 /dev/i2c-1
I have just tested on a completely fresh Hassos 3.7 install, plugged the usb stick in and checked /etc/modules-load.d/ nothing there as expected, clicked import from USB inside Hass.io and interestingly rpi-i2c.conf does get placed in /etc/modules-load.d/ so the usb import is sort of working, it just doesn't modify the config.txt inside /boot/config.txt
Has anyone any ideas? is there any logs I can provide from journal on the host that will help?
Thanks

just doesn't modify the config.txt inside /boot/config.txt
Yes, they import don't touch the config.txt. So it's not directly a bug as a feature request.

I have just checked what the import has access to and yes you are correct it doesn't touch the config.txt link
Looks like the instructions on home-assistant.io need changing on how to enable i2c, unless the import used to touch the config.txt in an older hassOS release?

Or maybe better will be add this function to new image hassos ? To import config can mod /boot/config.txt

also setting for NTP is wrong path:
NTP
You can manual edit the systemd timesync file on /etc/systemd/timesyncd.conf. Our default ntp configuration look like:
[Time]
NTP=time1.google.com time2.google.com time3.google.com
FallbackNTP=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org
In Hassos not found this path: /etc/systemd/timesyncd.conf.


[NLTK Error]

If someone get the following error to when running the run_xl.py

Solution: https://stackoverflow.com/questions/35861482/nltk-lookup-error
You can install what is in the image, or you can install as I did:
python3 -c "import nltk; nltk.download('all')"

Thank you!
I've updated README.md to include this


silence test compile warnings

This fixes compile warnings for exec-src/rastertest.hs locally.

Thanks!


Build step to detect breaking API changes

We should look into using this: https://github.com/dotnet/roslyn-analyzers/issues/976
To break the build when breaking API changes get introduced.

Team Triage: We have been handling these through process so far and doesn't seem likely we will get to this. Closing.


Added a new script under Github Automation

Added a script to automate git commit and push all the code after a time delay (specified by the user).

@RohanTrix Please mention the issue that your PR fixes whenever you raise a pull request. You are not allowed to add your script in someone else's project folder, if your PR fixes an issue then please add your script in new folder with appropriate README file.

@RohanTrix Please mention the issue that your PR fixes whenever you raise a pull request. You are not allowed to add your script in someone else's project folder, if your PR fixes an issue then please add your script in new folder with appropriate README file.


document maintainer guidelines

This probably exists in a "project" somewhere, but we need to formalize contribution guidelines, decision-making process, etc.  I like what ESLint has done.
UPDATE: I forgot that I already wrote up CONTRIBUTING.md, and I can live with that for now.  What we're missing is "how to become a maintainer" and "how to be a good maintainer once you are one", etc.
I'll tackle "governance" in another issue.

there is a bit of "governance" in here, but I don't think we have enough "governance" to warrant a separate doc for it (yet)


Make inventory more generic and species agnostic

To better support perennial plant  and animal breeders

Change the name "Seed Lots" to "Inventory Lots"
Add a "Lot Type" that can be customized by application and/or species (seed, pollen, bud wood, root stocks eggs, etc..)
Add "Lot Expiry", to support management of  time-limited inventory

Would it be possible to generalise it a little more to cover a 'plant'? Would the term Inventory Lot still be applicable to a Plant. Perhaps we can just use the term 'Lot'? So a plant, would be a Lot with Lot type 'plant'.

I'm not a huge fan of just "Lot", it is too generic and not descriptive enough.
The intention of this endpoint is to record and control the inventory management for things that can grow into plants (seeds, root stock, etc). Planting or sending seeds away are transactions that reduce the amount in an inventory lot. Seed production adds to a lot. A cross might create a new lot.
@daveneti what would "lotType": "plant" relate to in the real world? can you describe the use case a little more?
From previous conversation, I'm guessing you are talking about perennials, and I could see how you could have "inventory" to choose from to build an experiment, even though no seed production or planting is required because the perennial plants already exist. Is this kind of your idea?

No problem, I am happy with 'Inventory Lot' , a plant can be an in Inventory Lot. You could also call it Inventory Item as a suggestion.
Here is the use case for plant lots.
Seed is sown and then transplanted out in to trays, usually 96 cell, 8 x 12. Leaf samples are taken for DNA to genotyped. Individual plants are grown on and put in to pots. Pots move from a glasshouse to a outdoor nursery at some stage. Based on the genotyping results and perhaps some phenotypic measurements, such as resistance/tolerance to endemic biotic stress, plants are kept, sometime moved within the nursey. When the field/orchard is ready to receive then, they are planted out either in mass into a newly prepared plots, or are used to replace plants that have been culled or have died. In the later case the same plot location is used for a new lot. This is a new plot in the system, but the plot location is the same. For several years many observations are taken on the plant, in different trials. After a few years, the plant is considered too valuable to be destroyed so it is moved to another field/orchard location. So as before new plot but same lot, new trial. This can occur several times. Although clonal propagation can also occur, in this case it is the same plant. In some cases plants are used a root stocks for clonal propagation. So as before the plant will move to another trial, but the location and the plant would remain the same, and a scion from a different germplasm is grafted on to this rootstock. The scion is then a separate lot, attached to plant lot. There can be several scions even form different germplasm on the same rootstock.

Would a Inventory Lot, still continue to have a content mixture? Is there an opportunity to have a direct link to a single germplasm? I can understand that in a physical seed mixture (bulk) you can know the relative contributions of the germplasm in the mix, but is this a rare case?

The "content mixture" concept comes from @NPZInno in #466. They might want to comment on this discussion.
From a technical perspective, you do still have a direct link to a single germplasm if there is only one item in the content mixture list. Perhaps it is not as human readable, but the computer doesn't care if you reference seedLot.germplasmDbId or seedLot.contentMixture[0].germplasmDbId. For safety, you may want to include something like if (contentMixture.size == 1) ... just to make sure you aren't dealing with a special case.
From a conceptual perspective, we could add a field like primaryGermplasmDbId or something to indicate the primary thing in a lot and make it clear to a human reader that this is the germplasm we care about. I don't know if that concept makes sense for the seed mixture special case, if there is one germplasm in a mixture we care about more than the others. Maybe @NPZInno can chime in there.

Would a Inventory Lot, still continue to have a content mixture? Is there an opportunity to have a direct link to a single germplasm? I can understand that in a physical seed mixture (bulk) you can know the relative contributions of the germplasm in the mix, but is this a rare case?

As suggested as an alternative option in our initial #466 another way of solving this, is to create another "inhomogenous" genotype and attach the mixture info there. Using this concept, a given lot item would have exactly one genotype connected (1:M -> Genotype:LotItem), as recommeded by @daveneti .
When I understand the current approach right (N:M -> Genotype:LotItem), there is no and should be no "primeryGermplasmDbId" IMHO, because this is a kind of interpretation which could greatly depend on the context of the request.

Sorry for taking so long to get back to this. We will implement using contextMixture :)

Can we add inventoryLotPUI as a field for InventoryLot.

We would need to rename SeedLotTransaction to InventoryLotTransaction as well.

The term 'Lot' is a little overloaded and is highly associated with 'seed', e.g, Seed Lot. Perhaps a better name would be InventoryUnit, to make it more generic?

@daveneti I agree and this aligns well with other parts of the standard, as well (e.g., ObservationUnit)


[Video] use dynamic import for hls.js

Tested on the video feed w/ deployment, seems to be working good now. Appreciate you taking a look @gaearon


Plugin does not recognize PipAuthenticate@1

The plugin seems to be missing support for v1 of PipAuthenticate. v0 works fine.

See PR 290

Fixed in 1.170.0, according to #290.

Fixed in 1.170.0, according to #290.


Gripper control interface in ROS2

Hi, I would like to follow up on the discussion in #30. @munseng-flexiv said that you'll release the gripper control interface in version 0.10 but I can't find anything about that in the release. Are you still planning on that? Thanks!

Hi @TomCC7
What gripper are you using?
If the gripper you are using is Flexiv Grav gripper and you connect the Grav gripper to the control box, the direct gripper control is now only supported in RDK and Flexiv Elements. The gripper control interface will be supported together with the RDK v1.x release.
Another way is by connecting the gripper directly to your PC with Modbus, you can use the Modbus RTU communication protocol to control the gripper (check the Grav documentation). To control the gripper in ROS, you can try the existing ROS Modbus RTU driver to send information to the gripper (e.g. https://github.com/openvmp/modbus_rtu).
If you use other grippers, you can check the corresponding ROS 2 driver.

Hi, thanks for replying! It's good to know that you are still planning on that. Currently I can control the gripper through the RDK API, so I'll just write a workaround and wait for your future release.

Hi Flexiv Team! I would like to follow up on this issue, as version 1.4 has been released, but I'm still not sure how to control the gripper through ROS2. Are there any examples demonstrating how to control the GRAV gripper through the ROS2 interface?
Also, is it now possible to move the arm and gripper through one connection to the robot   (for example #30 mentions that you can't)?
Lastly, when are you planning on adding URDF files and meshes of the gripper to the humble branch of the repo? This is quite important for us as we use MoveIt for motion planning, but if MoveIt doesn't have the gripper mesh then it generates trajectories that result in the gripper hitting the arm and table.
If you could please help with these issues I will be very grateful!

Hi Flexiv Team! I would like to follow up on this issue, as version 1.4 has been released, but I'm still not sure how to control the gripper through ROS2. Are there any examples demonstrating how to control the GRAV gripper through the ROS2 interface?
Also, is it now possible to move the arm and gripper through one connection to the robot (for example #30 mentions that you can't)?
Lastly, when are you planning on adding URDF files and meshes of the gripper to the humble branch of the repo? This is quite important for us as we use MoveIt for motion planning, but if MoveIt doesn't have the gripper mesh then it generates trajectories that result in the gripper hitting the arm and table.
If you could please help with these issues I will be very grateful!

Hi @artyom-boyarov
Thanks for your inquiry. The public release of RCA v3.6 and RDK v1.4 was last week. The gripper control interface in ROS 2, which is compatible with RDK v1.4, is still in development. I am working on it to deliver it by October 2024.
The Grav gripper URDF and meshes will be added together with the Grav gripper ROS 2 driver.
Sorry for the delay.

@munseng-flexiv could you please provide me an update on when to expect the v1.5 release of the Flexiv ROS2 library?

@munseng-flexiv could you please provide me an update on when to expect the v1.5 release of the Flexiv ROS2 library?

Hi @artyom-boyarov
Flexiv ROS 2 release plan is aligned with the Flexiv RDK release plan, as Flexiv ROS 2 is built with RDK. Flexiv ROS 2 v1.5 will be released one or two weeks after the official release of Flexiv RDK v1.5.

Update: The gripper control feature (of the gripper connected to the robot) is released in v1.5. For details, please refer to the Release Note and the README.


KAFKA-9846: Filter active tasks for running state in KafkaStreams#allLocalStorePartitionLags()

Added check that only treats running active tasks as having 0 lag
Tasks that are neither restoring, nor running will report 0 as currentoffset position
Fixed LagFetchIntegrationTest to wait till thread/instance reaches RUNNING before checking lag

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

test this please

@guozhangwang So, I still need to add a test case around this specific scenario, tasks stuck in created state.. Seems it needs some engineering to create that scenario. (sophie gave me some pointers, yet to try them)..
if we need to just fix the test issue, I can open a simpler one with just the test fix.. That's probably better?

Opened a simple backport here #8534.. We can focus on that for fixing the test flakiness itself.

Opened a simple backport here #8534.. We can focus on that for fixing the test flakiness itself.

Sounds good, thanks!

Closing this PR as outdated.


can not close a namespace

I wrote some code to add macvlan device to a container, however, it can not get out from container's namespace.
here is the code https://gist.github.com/CMGS/4f60fd8da2014eed0dd8
Is there anyone can help me to solve this problem?
this is output
root@kili1:/home/armin# ./test
ifc in host &{2119 1500 mt2 16:2c:ef:fe:09:44 broadcast|multicast}
set ip &{2119 1500 mt2 16:2c:ef:fe:09:44 broadcast|multicast} <nil>
up link &{2119 1500 mt2 16:2c:ef:fe:09:44 broadcast|multicast} <nil>
close <nil>
check outside &{2119 1500 mt2 16:2c:ef:fe:09:44 up|broadcast|multicast}

@CMGS You need to Setns back in parent namespace. You can find such code here: https://github.com/docker/libnetwork/blob/master/sandbox/namespace_linux.go


request.ajax() returns false even if it comes from ajax

Here's my axios code
        axios.post('/paktay', {             headers: {                 'X-Requested-With': true             }         }).then((res)=>{             console.log(res.data);         });     }

Hey @kingleuther! 👋
Remove the header X-Requested-With, this is automatically set by axios and sound't be true.
Code https://github.com/poppinss/node-req/blob/develop/index.js#L366

You won't have to set X-Requested-With. If the request is from browser using axios, then it will set it for you.
Also I recommend using forum or the discord channel for confusions.

@thetutlage noted I will retry that.

Closing since not actionable


Create 84. Largest Rectangle in Histogram.cpp

Added solution to leetcode problem 84. Largest Rectangle in Histogram

Great work @77Spencer77 please give this repo a star if it really helped you to complete your PR.
Also follow me for follow back if you want to get connected with me for any such open source contribution program. Thank you 😊


Toscanini.Iterator

What: An iterator to make iterating over a score simpler.
Why: Per Dr. T's request, this abstraction should simplify the process for a new programmer to start developing new queries. New programmers need not know about XML parsing techniques. This makes collecting information about chords and melodic sequences much easier for example.
Concerns:
-chords or multiple voices?
MuseScore and seems like the MusicXML standard require two voices to be used when a note of a chord has different duration from other notes of the chord.
Chords not voices will be considered. If two notes are played by one part at a single point in time, then they are to be considered a chord of one instrument as opposed to two voices under any circumstance. It would be impractical to code otherwise. Guitar music where notes in a chord have different durations require multiple voices to be used according to the MusicXML standard and MuseScore, but in reality it's clearly meant for one instrument.
-How do you represent a chord that is spread across multiple parts? Should the iterable contain all notes of all parts at a given point in time for harmonic analysis across instruments?

Rests?
Ties?
Repeats?
Dynamics?
Vibrato?
Tremolo?
Time Signatures: effect beat (ex: in 7/8 a measure of all eights means each note is a beat)
etc...

Provision one:
ScoreIterator

Draft spec 6/24/17:
Iterator.nextMeasure(); //takes you to the first beat of the next measure
Iterator.next(); //takes you to the next note or set of notes or rest ... of a measure or across measures?
Iterator.nextBeat(); //takes you to the next beat of the measure or across measures??
Iterator.prevMeasure();
Iterator.prev();
Iterator.prevBeat();

First Draft Specification coming soon. Concerns:

should beat be represented in terms of quarters or in terms of the beat-type?( Ex: a measure with all eight notes in 7/8 - should each note be treated as beat for the Iterator?) It becomes very difficult to determine chords formed by instrument parts with the latter in the event the music is polyrhythmic. Also, for conductors- I recall in high school marching band: 7/8 was typically counted "1 2, 1 2, 1 2 3". How meaningful is it to count the beat in terms of eights (ex: "1 2 3 4 5 6 7")? Which is most important for the iterator-  respecting time signature beat type or having a single uniform way of knowing how far the note is from the start of the measure?

I.next().notes[0].duration
I.next().notes[0].pitch

Iterator 1.1.0:
-user can listen for key and time signature changes


[MLIR] NFC remove dangling braces in comments

Remove incorrect braces in example comments in hlo/lhlo/linalg
conversion passes - these mess up brace matching.

Gentle ping reviewers @joker-eph


specify bump up minor by default

I would like to do something like
autobump {
    majorPattern = ~/(?m)^\[major-release\]$/
    patchPattern = ~/(?m)^hotfix$/
}

1: git commit -m "normal stuff" -> v1.1.0
2: git commit -m "hotfix" -> v1.1.1
3: git commit -m "[major-release]" -> v2.1.1

but when I do case 1 I get a bump in patch component, not minor

@DemianTinkiel You'd have to set a pattern that matches anything except hotfix or [major-release] for minorPattern I would think.

Hi @vivin
Yeah that was my first thought. Perhaps my regex foo is not as strong as I thought
    majorPattern = ~/(?m)^\[major-release\]$/
    patchPattern = ~/(?m)^hotfix$/
    minorPattern = ~/^(?!(.*(hotfix|\[major-release\]).*))$/

1: git commit -m "normal stuff" gives me v1.0.1 and I expected v1.1.0

Perhaps ~/^(?!.*(hotfix|\[major-release\]))/?

For me this regex works great you could change it for your use case:
minorPattern = ~/(?m)^(?!(.*(\[bump-major\]|\[bump-patch\]|\[make-new-pre-release\]|\[promote-to-release\]).*)$).*$/

@DemianTinkiel Did this fix your issue?

@vivin sorryl for te really late reply. Yes issue fixed


”Mogoșești-Siret” is listed in the drop-down menu

Description:
"Mogoșești-Siret" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Mogoșești-Siret" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Mogoșești-Siret, IAȘI".


Bugfix/readme fix for SQL and python examples

While working through the SQL and Python examples in the readme, I noticed some issues.  I've attempted to correct these for the next user so that they can hit the ground running.  Please let me know if I can improve this PR.
Thanks!

Hi @prmoore77 , thanks for the fixes, it's always better when someone actually tries the readme since they are not as biased as the writer :-)


[FEAT] move experimental feature to permanent and set default caching…

… to true
Description

Set default caching of compiled files to true
Add the --no-cache option to disable caching

closes #3838
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in 64798acc8abcc3b7b31ab657f1d04e1974209d6f


Issues on Laravel 8

When I try to run
PHP artisan stats

I'm getting the next message:
LogicException
You must call one of in() or append() methods before iterating over a Finder.

Is the LogicException really thrown from the laravel-stats-package? Or maybe from a different part of the application?
The Finder should be built correctly in the stats package. Otherwise our testsuite should fail when testing against Laravel 8 🤔
https://github.com/stefanzweifel/laravel-stats/blob/51826b3a0cc274e23c475ab40f5b6b8eae23cd55/src/ClassesFinder.php#L46-L48
Could you share your exact Laravel and PHP Version and your config/stats.php file?
Is symfony/finder a direct dependency in your Laravel application? Maybe we run into a problem here.

I am also having the same issue with Laravel 8.
symfony/finder is not a direct dependency in my Laravel application, and it's not coming from a different part of my application.
Here is the full error:
LogicException

  You must call one of in() or append() methods before iterating over a Finder.

  at vendor/symfony/finder/Finder.php:610
    606|      */
    607|     public function getIterator()
    608|     {
    609|         if (0 === \count($this->dirs) && 0 === \count($this->iterators)) {
  > 610|             throw new \LogicException('You must call one of in() or append() methods before iterating over a Finder.');
    611|         }
    612|
    613|         if (1 === \count($this->dirs) && 0 === \count($this->iterators)) {
    614|             return $this->searchInDirectory($this->dirs[0]);

  1   [internal]:0
      Symfony\Component\Finder\Finder::getIterator()

      +20 vendor frames
  22  artisan:37
      Illuminate\Foundation\Console\Kernel::handle()

Environment: Ubuntu 20.04.1 LTS, PHP 7.4.3, and I did not publish the vendor files for the package so no changes to config/stats.php made.

I resolved this issue by publishing the vendor config and caching the config.
For anybody else that comes across this issue:
php artisan vendor:publish --provider="Wnx\LaravelStats\StatsServiceProvider"
config:cache

@kyleboehlen Can you share the Laravel Version of your project (php artisan --version)?
And what's the output of composer why symfony/finder?
I can't reproduce this error on a fresh Laravel 8 install. That's why I need a bit more information here.

@stefanzweifel
Laravel Framework: 7.28.4
barryvdh/laravel-debugbar  v3.5.1   requires  symfony/finder (^4.3|^5)
laravel/framework          v7.28.4  requires  symfony/finder (^5.0)
sebastian/finder-facade    2.0.0    requires  symfony/finder (^4.1|^5.0)
wnx/laravel-stats          v2.4.1   requires  symfony/finder (^4.3 || ^5.0)

That being said, it only happens when your config is cached without having published the vendor config for the package.
Steps to reproduce issue on a fresh laravel installation:
composer create-project --prefer-dist laravel/laravel laravelstatstest
cd laravelstatstest
php artisan config:cache
composer require "wnx/laravel-stats" --dev
php artisan stats

@kyleboehlen Thanks! Good to know about the config-cache thing. Will have to give this a spin.

@stefanzweifel
I just tested caching the config on a freshly created laravel project without publishing the vendor config and it still resolves the issue. So this really isn't an issue with your package at all, I suppose you could add something in the installation directions of the readme but config:cache and composer dump-autoload should be the first thing people try when they have an issue like this ¯\(ツ)/¯

@kyleboehlen Yeah, will add a note to the README I think. php artisan config:cache shouldn't be run on dev machine anyway (IMHO).
As this resolves the original issue mentioned here, I'm gonna close this issue for now.


clean up backend types and return values

Issue
Getting type errors when running PyCharm's automated checker. Some related to #371.
Cause
The inconsistent types and return values exist but do not trigger any tests.
Solution
Update the types and return values as appropriate.

LGTM, should we add PyCharm to our lint tests?

I think so. I only included the lints from the backend. There's quite a number of other lints to clean up that PyCharm warned about.

I think so. I only included the lints from the backend. There's quite a number of other lints to clean up that PyCharm warned about.

I'd be OK with this, but how does it work? I don't have that IDE and don't think you can get it's internal linter seperately?
I've also been meaning to add ruff format to the lints, so we always have formatted code...

LGTM too, thanks!

I've also been meaning to add ruff format to the lints, so we always have formatted code...

@willcl-ark That seems like a great idea. I had imagined that ruff would be as picky as clippy right out of the box. But, I guess not!

I'd be OK with this, but how does it work?

PyCharm has a "Try Locally" button I can press that allegedly allows me to run something called Quodana. When I press the button it examines everything in my local warnet project and lints it.


kubectl shell : kubectl version show client and server different version

Setup

Rancher version: 2.7.9
Rancher UI Extensions: not enabled
Browser type & version: Firefox 115.5.0esr (64 bits)

Describe the bug
With rancher 2.7.9, we recently upgrade our clusters from 1.24.16 to 1.25.14 and after to 1.26.9
When I launch kubectl shell from rancher dashboard, the kubectl version --short command show client and server different version :
# Run kubectl commands inside here
# e.g. kubectl get all
> kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.24.16
Kustomize Version: v4.5.4
Server Version: v1.26.9
WARNING: version difference between client (1.24) and server (1.26) exceeds the supported minor version skew of +/-1

To Reproduce

Result
Expected Result

kubectl version command show same version for client and server
Screenshots

Additional context

From memory the image used to execute kubectl commands is the same for all downstream clusters. There may be existing issues for it over at rancher/rancher. Either way, this issue lives that side


why Nest.js Project slower on ts-node-dev with >= Node.js v10.16.0, frozen after [INFO] 10:46:03 Restarting: /xxx/xxx.ts has been modified

My ENV:
macOS v10.14.6 + Node v12.8.1
Try:

change to  "ts-node-dev": "1.0.0-pre.35 / 37 / 39 / 40 / 41" in Node v12.8.1, The problem is still.
change to "ts-node-dev": "1.0.0-pre.41" and Node v10.13.0 LTS, It's works!

so, How can I work under "ts-node-dev": "1.0.0-pre.41" and Node v12.8.1 now?
it's a bug?

My test list (with "ts-node-dev": "1.0.0-pre.41"):
✅ WORKS
v10.13.0 (LTS: Dubnium)
v10.14.0 (LTS: Dubnium)
v10.14.1 (LTS: Dubnium)
v10.14.2 (LTS: Dubnium)
v10.15.0 (LTS: Dubnium)
v10.15.1 (LTS: Dubnium)
v10.15.2 (LTS: Dubnium)
v10.15.3 (LTS: Dubnium)
❌ NOT WORKS
v10.16.0 (LTS: Dubnium)
v10.16.1 (LTS: Dubnium)
v10.16.2 (LTS: Dubnium)
v10.16.3 (Latest LTS: Dubnium)
v12.0.0
v12.1.0
v12.2.0
v12.3.0
v12.3.1
v12.4.0
v12.5.0
v12.6.0
v12.7.0
v12.8.0
v12.8.1
v12.9.0

look 2019-05-28, Version 10.16.0 'Dubnium' (LTS), @BethGriggs, Is it related to ICU or libuv?

Sorry, I found out that the Express.js project is working fine after minimizing the test, but the Nest.js project is very slow.
I tried to debug and found that just deleting node_modules/ts-node-dev/lib/index.js L64 watcher.removeAll() is normal. Continue to delve into the debug discovery is actually: Here's the problem.
// node_modules/filewatcher/index.js

FileWatcher.prototype.remove = function(file) {
  var watcher = this.watchers[file]
  if (!watcher) return

  delete this.watchers[file]
  watcher.close()     <---- Here in Node.js 12 is very SLOW.
}

minimizing test use [nest/tree/master/sample/01-cats-app](https://github.com/nestjs/nest/tree/master/sample/01-cats-app).

This is an issue in other packages too - exactly the same scenario using socket-cluster and express. Unsure of the actual culprit, but it runs fine using node and ts-node v12, but when you add ts-node-dev to the mix you cant use to any version > v10.15.3 - it just hangs on startup. No errors thrown.

This is beyond frustrating!

Filed an issue: https://github.com/nodejs/node/issues/29949, thanks @SolidZORO for debugging.

@jonjaques   I refer to this https://github.com/whitecolor/ts-node-dev/issues/51#issuecomment-490764844 and it works fine on node.js v12.13.0.
finally solved the problem. 😄
// package.json

"dev-tsnodedev": "NODE_ENV=development ts-node-dev --respawn --transpileOnly --ignore-watch node_modules -r tsconfig-paths/register ./src/main.ts",


docs: fix documentation broken links and snippets formatting

Related issue

Closes #1309
Scope of work
Fixes documentation broken links a snippets formatting
Screenshots of visual changes

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x] Self code-reviewed

If applicable:

[x] I followed composition rules for my component
[x] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)
[x] I accept Individual Contributor License Agreement

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you!


ion-js v4.0.0; Maximum call stack size exceeded

Hi! I'm running into the exception Maximum call stack size exceeded when trying to use the new DOM Api with v4.0.0. I am attempting to load an ion serialized arrayBuffer created via Java's Jackson Ion serializer which has an underlying object structure that looks like...
{
     data: {
          id: '123',
          featureCollections: [{
                id: '456',
                positions: [],
                fillColors: [],
                lineColors: []
          }]
     }
}

The positions (Double), fillColors (Integer) and lineColors (Integer) arrays contain ~ 1800000 values.
Uncaught (in promise) RangeError: Maximum call stack size exceeded
    at new eval (Sequence.js?7237:9)
    at new List (List.js?0c8b:7)
    at _loadList (index.js?79f0:89)
    at _loadValue (index.js?79f0:71)
    at _loadStruct (index.js?79f0:82)
    at _loadValue (index.js?79f0:73)
    at _loadSequence (index.js?79f0:99)
    at _loadList (index.js?79f0:89)
    at _loadValue (index.js?79f0:71)
    at _loadStruct (index.js?79f0:82)
asyncGeneratorStep @ asyncToGenerator.js?1da1:6
_next @ asyncToGenerator.js?1da1:25
eval @ asyncToGenerator.js?1da1:32
eval @ asyncToGenerator.js?1da1:21

Thanks!

Hi, thanks for reporting this! It looks like this is caused by Sequence calling Array#push with too many arguments.

This was fixed in #603.

@zslayton any chance this fix will be released soon? Thanks!

I'll try to find time to release this next week. Are you able to work with the HEAD of master in the meantime, or is this blocking you?

@jfuehner: This fix was included in v4.0.1, which was released earlier today.


Fix color on blank search

Upon searching for something and then deleting the searched text, all the results show up as searched (In the gray background color)
Ideally, none of them should when the field is empty

Hey @srujandeshpande  Can I work on this issue. and please elaborate a little more on this.

Sure!
This is how the page looks in the beginning

This is how it looks when searching

If you delete the search term, it looks like this when actually it should look like the first image

Hey @srujandeshpande  .I have raised #27 .Please Review.!


Failed to build on latest pytorch master.

🐛 Bug
torchvision failed to build with latest pytorch master.
Same build script was working weeks ago, indicating this can be a recent regression.
  Compiling objects...
  Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
  [1/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build/t
emp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-option
s ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60 -gencode=
arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build/temp.lin
ux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu(160): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu(106): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu(169): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu(169): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, double)>>, &vision::ops::<unnamed>::nms_ke
rnel>)
              object type is: torch::Library

  2 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/nms_kernel.cu".
  [2/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu -o /tmp/pip-req-build-tzug7t
tm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constex
pr --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,
code=sm_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu -o /tmp/pip-req-build-tzug7ttm/buil
d/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --co
mpiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm
_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(644): warning: variable "guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(806): warning: variable "guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(938): warning: variable "guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(1210): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(1209): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, const at::Tensor &, const at::Tensor &, co
nst at::Tensor &, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, __nv_bool)>>, &vision::ops::<unnamed>::deform_conv2d_forward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(1213): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu(1212): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<std::tuple<at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor> (const at::Tensor &, c$
nst at::Tensor &, const at::Tensor &, const at::Tensor &, const at::Tensor &, const at::Tensor &, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, int64_t, __nv_bool)>>, &vision::ops::<unnamed>::deform_conv2d_backward_kernel>)
              object type is: torch::Library

  4 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/deform_conv2d_kernel.cu".
  [3/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu -o /tmp/pip-req-build-tzug7ttm
/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -
-compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code
=sm_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build/
temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compil
er-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60
-gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(177): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(205): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(158): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(248): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(272): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(233): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(280): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(279): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<std::tuple<at::Tensor, at::Tensor> (const at::Tensor &, const at::Tensor &, double, int64_t, i
nt64_t)>>, &vision::ops::<unnamed>::ps_roi_pool_forward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(283): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(282): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, const at::Tensor &, double, int64_t, int64
_t, int64_t, int64_t, int64_t, int64_t)>>, &vision::ops::<unnamed>::ps_roi_pool_backward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu(85): warning: parameter "num_rois" was declared but never referenced

  4 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_pool_kernel.cu".
  [4/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu -o /tmp/pip-req-build-tzug7tt
m/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr
 --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,co
de=sm_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build
/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --comp
iler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_6
0 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(337): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(366): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(318): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(411): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(436): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(396): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(444): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(443): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<std::tuple<at::Tensor, at::Tensor> (const at::Tensor &, const at::Tensor &, double, int64_t, i
nt64_t, int64_t)>>, &vision::ops::<unnamed>::ps_roi_align_forward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(447): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(446): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, const at::Tensor &, double, int64_t, int64
_t, int64_t, int64_t, int64_t, int64_t, int64_t)>>, &vision::ops::<unnamed>::ps_roi_align_backward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(21): warning: parameter "index" was declared but never referenced
            detected during instantiation of "void vision::ops::<unnamed>::ps_roi_align_forward_kernel_impl(int, const T *, T, int, int, int, int, int, int, const T *, int, T *, int *) [with T=double]"
  (349): here

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(206): warning: parameter "num_rois" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu(156): warning: parameter "index" was declared but never referenced
            detected during instantiation of "void vision::ops::<unnamed>::ps_roi_align_backward_kernel_impl(int, const T *, const int *, int, T, int, int, int, int, int, int, int, T *, const T *) [with T=double]"
  (418): here

  4 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/ps_roi_align_kernel.cu".
  [5/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu -o /tmp/pip-req-build-tzug7ttm/bu
ild/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compi
ler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60
 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build/tem
p.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-opt
ions ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60 -genco
de=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(163): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(183): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(141): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(226): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(256): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(210): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(264): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(263): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<std::tuple<at::Tensor, at::Tensor> (const at::Tensor &, const at::Tensor &, double, int64_t, i
nt64_t)>>, &vision::ops::<unnamed>::roi_pool_forward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(267): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(266): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, const at::Tensor &, double, int64_t, int64
_t, int64_t, int64_t, int64_t, int64_t)>>, &vision::ops::<unnamed>::roi_pool_backward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(85): warning: parameter "num_rois" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu(86): warning: parameter "spatial_scale" was declared but never referenced

  4 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_pool_kernel.cu".
  [6/32] /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/
dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu -o /tmp/pip-req-build-tzug7ttm/b
uild/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --com
piler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_
60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  FAILED: /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.o
  /usr/local/cuda/bin/nvcc  -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-pa
ckages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu -o /tmp/pip-req-build-tzug7ttm/build/te
mp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-o
ptions ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_60,code=sm_60 -gen
code=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -ccbin /usr/bin/gcc-8 -std=c++14
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(355): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(376): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(336): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(415): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(445): warning: variable "error_unused" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(401): warning: variable "device_guard" was declared but never referenced

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(453): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(452): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, double, int64_t, int64_t, int64_t, __nv_bo
ol)>>, &vision::ops::<unnamed>::roi_align_forward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(456): error: expression must have a constant value
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
  /usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_allowlist.h(62): note: called from:

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(455): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(606): here
              function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
  /usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(616): here
              argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, double, int64_t, int64_t, int64_t, int64_t
, int64_t, int64_t, int64_t, __nv_bool)>>, &vision::ops::<unnamed>::roi_align_backward_kernel>)
              object type is: torch::Library

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(21): warning: parameter "index" was declared but never referenced
            detected during instantiation of "void vision::ops::<unnamed>::roi_align_forward_kernel_impl(int, const T *, T, int, int, int, int, int, int, __nv_bool, const T *, T *) [with T=double]"
  (360): here

  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu(159): warning: parameter "index" was declared but never referenced
            detected during instantiation of "void vision::ops::<unnamed>::roi_align_backward_kernel_impl(int, const T *, T, int, int, int, int, int, int, __nv_bool, T *, const T *, int, int, int, int) [with T=double]"
  (425): here

  4 errors detected in the compilation of "/tmp/pip-req-build-tzug7ttm/torchvision/csrc/ops/cuda/roi_align_kernel.cu".
  [7/32] /usr/bin/g++-8 -MMD -MF /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip-req-build-tzug7ttm/torchvision/csrc/vision.o.d -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORT
IFY_SOURCE=2 -fPIC -DWITH_CUDA -I/tmp/pip-req-build-tzug7ttm/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-packages/to
rch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-tzug7ttm/torchvision/csrc/vision.cpp -o /tmp/pip-req-build-tzug7ttm/build/temp.linux-x86_64-3.6/tmp/pip
-req-build-tzug7ttm/torchvision/csrc/vision.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1013"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -std=c++14
  In file included from /tmp/pip-req-build-tzug7ttm/torchvision/csrc/vision.cpp:1:
  /tmp/pip-req-build-tzug7ttm/torchvision/csrc/vision.h:10:40: warning: ‘_register_ops’ initialized and declared ‘extern’
   extern "C" VISION_INLINE_VARIABLE auto _register_ops = &cuda_version;
                                          ^~~~~~~~~~~~~

Environment

PyTorch / torchvision Version (e.g., 1.0 / 0.4.0): master
OS (e.g., Linux): Ubuntu 18.04
How you installed PyTorch / torchvision (conda, pip, source): source
Build command you used (if compiling from source): pip install from git repo
Python version: 3.6
CUDA/cuDNN version: 11.3

Likely the same as #3695

Is this issue still happening today? Our CI seems to be working fine.

The last log in our side for pytorch+torchvision (Fri Apr 30 02:27:17 UTC 2021) still shows the issue, checking again...

@fmassa I don't think it's fixed.

Also I noticed our pure cmake build of torchvision works fine, but pip build from git repo doesn't work.

Let me grab some log for you about the same file nms_kernel.cu:
CMake build:
ccache /usr/local/cuda/bin/nvcc -forward-unknown-to-host-compiler -DGFLAGS_IS_A_DLL=0 -DGOOGLE_GLOG_DLL_DECL="" -DGOOGLE_GLOG_DLL_DECL_FOR_UNITTESTS="" -DWITH_CUDA -D__CUDA_NO_HALF_OPERATORS__ -Dtorchvision_EXPORTS -I../torchvision/csrc -isystem=/usr/local/include/torch/csrc/api/include -isystem=/usr/local/cuda/include -isystem=/usr/include/python3.6m --expt-relaxed-constexpr -O3 -DNDEBUG -Xcompiler=-fPIC -D_GLIBCXX_USE_CXX11_ABI=1 -std=c++14 -MD -MT CMakeFiles/torchvision.dir/torchvision/csrc/ops/cuda/nms_kernel.cu.o -MF CMakeFiles/torchvision.dir/torchvision/csrc/ops/cuda/nms_kernel.cu.o.d -x cu -c ../torchvision/csrc/ops/cuda/nms_kernel.cu -o CMakeFiles/torchvision.dir/torchvision/csrc/ops/cuda/nms_kernel.cu.o
../torchvision/csrc/ops/cuda/nms_kernel.cu(106): warning: variable "device_guard" was declared but never referenced

pip build:
/usr/local/cuda/bin/nvcc --generate-dependencies-with-compile --dependency-output /tmp/pip-req-build-9e2kvinu/build/temp.linux-x86_64-3.6/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.o.d -DWITH_CUDA -I/tmp/pip-req-build-9e2kvinu/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda/include -I/usr/include/python3.6m -c -c /tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.cu -o /tmp/pip-req-build-9e2kvinu/build/temp.linux-x86_64-3.6/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_75,code=compute_75 -gencode=arch=compute_75,code=sm_75 -ccbin /usr/bin/gcc-8 -std=c++14
/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.cu(160): warning: variable "error_unused" was declared but never referenced

/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.cu(106): warning: variable "device_guard" was declared but never referenced

/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.cu(169): error: expression must have a constant value
/usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(585): note: constexpr memory comparison is only supported for top-level integer or array-of-integer objects
/usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(340): note: called from:
/usr/local/lib/python3.6/dist-packages/torch/include/c10/util/string_view.h(369): note: called from:
/usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/op_registration/op_whitelist.h(62): note: called from:

/tmp/pip-req-build-9e2kvinu/torchvision/csrc/ops/cuda/nms_kernel.cu(169): error: more than one instance of overloaded function "torch::Library::impl" matches the argument list:
function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<false>, Func &&) &"
/usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(593): here
function template "torch::Library &torch::Library::impl(torch::detail::SelectiveStr<true>, Func &&) &"
/usr/local/lib/python3.6/dist-packages/torch/include/torch/library.h(603): here
argument types are: (torch::detail::SelectiveStr<<error-constant>>, c10::CompileTimeFunctionPointer<std::remove_pointer_t<std::remove_reference_t<at::Tensor (const at::Tensor &, const at::Tensor &, double)>>, &vision::ops::<unnamed>::nms_kernel>)
object type is: torch::Library

A clear difference is the simple -isystem=/usr/local/include/torch/csrc/api/include vs many -I for pytorch.
Wondering if there's any include with the same file name that can lead to the difference.

This seems to be an issue with PyTorch registration mechanism.
@ezyang is this a known issue in PyTorch?

I noticed that you set -D_GLIBCXX_USE_CXX11_ABI=1. Could you try adding -D_GLIBCXX_USE_CXX11_ABI=0 in your build flags?

I attempted to build a minimal repro for this but failed:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Sun_Mar_21_19:15:46_PDT_2021
Cuda compilation tools, release 11.3, V11.3.58
Build cuda_11.3.r11.3/compiler.29745058_0
root@40738805190e:~/pytorch# cat test.cu
#include <c10/util/string_view.h>
#include <cassert>

namespace c10 {

constexpr bool f(c10::string_view op_name) {
        assert(op_name.find("::") != string_view::npos);
        return true;
}

  template <bool enabled>
  class SelectiveStr {
  public:
    constexpr SelectiveStr(const char* name) : name_(name) {}
    constexpr operator const char*() { return name_; }
  private:
    const char* name_;
  };

#define TORCH_SELECTIVE_NAME(n) SelectiveStr<f(n)>(n)

void impl(SelectiveStr<true>) {}
void impl(SelectiveStr<false>) {}

void f() {
        impl(TORCH_SELECTIVE_NAME("foo::bar"));
}

}
root@40738805190e:~/pytorch# nvcc -std=c++14 --expt-relaxed-constexpr -c -I. test.cu

I'm OK with commenting out the assert (or ifdefing it so it doesn't run on nvcc) in pytorch core. Can someone send the patch?

This was on nvidia/cuda:11.3.0-cudnn8-devel-ubuntu20.04 Docker image.


specify the response header methods

Add the response headers, but leave out the rest

I split it up, and added via the following commits
704b1c95e9545ffe6edd3ac07a367e7539e96a7b
b1fd094370b87591878d8074d6f77b645299d51e


Added previews

This PR adds commands for previewing prebuild files and evaluated configs.

Expo: Preview modifier -- select a file and view the introspected results of that file in a side editor.
Expo: Preview modifier as JSON -- select a file and view the introspected results of that file in a side editor as JSON, useful for debugging a plugin.
Expo: Preview config -- select a config type and view the results, this is an interactive version of running expo config --type XXX

Most of the heavy lifting for this PR has been implemented in expo/config-plugins. Results are based on the saving a file that was open when the command was invoked. i.e. if you save an app.json after opening a preview while on the app.json, then you should see the results. If you open the preview while on a different file, then you won't see any changes from saving the app.json.

Seems to work nicely in development mode! I'll merge it but not release it, production mode throws a random error:

Guess I'm off to debugging webpack again 😄


gNOI3.1: change reboot request mode from force to graceful

Modified rebootRequest.Force default value as false to allow graceful reload of the router.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 47.948%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1320

Relevant Lines:
2753

💛  - Coveralls


Should operator-sdk test local be using global manifests?

Feature Request
Is your feature request related to a problem? Please describe.
As of now, operator-sdk test local command uses kubeconfig passed. I see two issues with this .

We are not testing RBAC(like serviceaccounts, privileges associated with them) provided in deploy directory location while using kubeconfig(unless the kubeconfig is created from serviceaccount). This is something that should be tested just like in case of operator when created within kube cluster as a  deployment.
The kubeconfig needs to have additional privileges for creating CRDs which is outside the scope of testing.

Describe the solution you'd like

test local option should be able to create service account from the rbac files and use that as kubeconfig(or atleast document that whoever wants to test RBAC should generate kubeconfig, in order for testing to be comprehensive. (Make some changes to https://github.com/operator-framework/operator-sdk/blob/master/commands/operator-sdk/cmd/test/local.go#L125-#L160)
test local option should allow CRDs to be manually created just like in case of deployment. Perhaps deleting this

(https://github.com/operator-framework/operator-sdk/blob/5b5d5ac9958a369b89cfbe18d0b41d5aca0da3b8/pkg/test/main_entry.go#L117-#L127)

/cc @AlexNPavel @hasbro17

Hello. Thanks for the suggestion of running the test under the created service account and RBAC. I'll look into adding that functionality to the testing framework.
In the case of manually creating CRDs (and other global resources), you can pass an empty file to the test using the --global-manifest flag. This way, no resources are created during that step. We do this internally for both manifest files when the --no-setup flag is set: https://github.com/operator-framework/operator-sdk/blob/master/commands/operator-sdk/cmd/test/local.go#L161-L179

Actually, can you try passing an empty file to --global-manifest, just the CR manifest to --namespaced-manifest, set the --namespace flag to the configured namespace you want to test, and set --kubeconfig to point to a kubeconfig using the service account? In this case you would have to create the CRD and service account/RBAC. That should work for your use case but I'm not sure. I can make a flag to simplify that process, but I want to make sure that I understand what you are trying to do first.

If there is no CRD in the global manifest you pass to the tests, it does not need those privileges. The test cluster subcommand creates a pod to run the tests that runs under the service account. It essentially acts the same once started with the exception of the skipped lines here: https://github.com/operator-framework/operator-sdk/blob/master/pkg/test/main_entry.go#L117-L126 and the fact that the default namespaced manifest generated doesn't include RBAC creation (the user is supposed to create that along with the CRDs).
If you pass an empty file as your global manifest, createFromYAML will only get the namespace, and then return as the yaml file is empty: https://github.com/operator-framework/operator-sdk/blob/master/pkg/test/resource_creator.go#L55-L104. It should act very similarly to the test cluster subcommand in that case.

@ravisantoshgudimetla Closing this issue due to inactivity but if you have any other questions, feel free to open a new issue or just reopen this one, thanks.


feat: adding json filter docs and clean up

Description

Adding docs around search_indexes and liquid filters

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


Node exporter - Scraping

Hi,
I am trying to run GMP. We are used to NodeExporter, and it would be nice to have that. How can we configure GMP to scrape nodeexporter?
Annotations:  prometheus.io/path: /metrics
              prometheus.io/port: 9100
              prometheus.io/scrape: true

apiVersion: v1
items:
- apiVersion: monitoring.googleapis.com/v1
  kind: PodMonitoring
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"monitoring.googleapis.com/v1","kind":"PodMonitoring","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"prom-example"},"name":"prom-example","namespace":"gmp-test"},"spec":{"endpoints":[{"interval":"30s","port":"metrics"}],"selector":{"matchLabels":{"app":"prom-example"}}}}
    creationTimestamp: "2022-06-01T18:12:27Z"
    generation: 1
    labels:
      app.kubernetes.io/name: prom-example
    name: prom-example
    namespace: gmp-test
    resourceVersion: "4734651"
    uid: 750188dc-e9a5-4477-8a17-d49dc077da33
  spec:
    endpoints:
    - interval: 30s
      port: metrics
    selector:
      matchLabels:
        app: prom-example
    targetLabels:
      metadata:
      - pod
      - container
  status:
    conditions:
    - lastTransitionTime: "2022-06-01T18:12:27Z"
      lastUpdateTime: "2022-06-01T18:12:27Z"
      status: "True"
      type: ConfigurationCreateSuccess
    observedGeneration: 1

Hey Naveen,
You'll have to craft a PodMonitoring resource to discover the node-exporter exporters and scrape them. What you pasted above is the example PodMonitoring resource that scrapes the example app.
This reference PodMonitoring will probably work for you: https://github.com/GoogleCloudPlatform/prometheus-engine/blob/29ac8e9175732b1d75b848a8a023c4da2ef5dfa0/cmd/operator/deploy/node-exporter/pod_monitoring.yaml

Thanks, I was able to deploy the one that you shared. It still doesn't show up. How do I debug this?

So we're developing a targets status page to help you figure out if it's not appearing due to a bad scrape config. Not ready yet.
I'd start debugging by port-forwarding node-exporter and manually verifying that it's accessible as expected. Then once that's done, I'd tweak the PodMonitoring until metrics appear.

You could also keep using your existing Prometheus deployment and scrape configs but switch to GMP via self-deployed collection: https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-unmanaged.

We've developed some copy-pastable YAML that will let you easily scrape node-exporter without having to figure it out yourself: https://cloud.google.com/stackdriver/docs/managed-prometheus/exporters


Related filter

This issue is complement of ermrest#376. It includes:

Support subset query parameter in recordset app.
Add unfilteredButton to recordset app.
Add default fallback value to appTagToURL (appLink function).

@hongsudt  @jrchudy
This is an example of how I am presenting the filter. Can you please give me some feedbacks? Should I change anything?


Make .Content (almost) always available in shortcodes

The timing issues here is esp. visible now with shortcodes and .Site.GetPage. There are chicken and egg situations, so perfect is hard. But we should do better.

Will take another stab at this.

@moorereason @anthonyfok @digitalcraftsman @kaushalmodi @regisphilibert and gang: Can you chime in with your clever minds if you have time. This is a fix you are going to like; I should have done this long time ago, but I have not been hit with this issue until now.
I have created a very confusing test section on my test site:
https://github.com/bep/hugotest/commit/6e7462650801f3044c0b0d69b0fe16949ebb89b5
http://hugotest.bep.is/scodes/
It is easier to explain:

Before this, using .Content (and content derived methods) from content pages found via .GetPage and similar had an undefined behaviour. Or: It seemed to work sometimes, but not really.
After this PR: All .Content is available except the content the shortcode itself lives in. The last point is impossible (please prove me wrong) to solve ...

Benchmarks show "as fast" as before, but there are potential wins if we look closer here, esp. for situations where you don't use the content. But I might delay that until later.
I plan to get this out sooner (Monday) rather than later, so any "no, this looks funky" would be good. We can take it into master tomorrow for people to take it for a spin.

Took a quick peek.  :heart:
What happens if p1.md contains {{< bundle-content "section" "scodes" "p1" >}}?  Does it behave like {{< current-page >}}?
The ToC works from a shortcode but clearly doesn't contain entries from the shortcode output.  Would the ToC contain the full list of entries if used from a normal page template (ie. not in a shortcode)?

I see that I have commented on the issue, not the PR that lives here:
https://github.com/gohugoio/hugo/pull/4651

There are some potential data races and I also need to pull out the ToC logic; there was a logical flaw in that. But other than that this looks god.

Never investigated shortcode vs .mdthis much, but this will become very important when people decide to use resources of type Page to build sections on their page (and call such sections using shortcodes).
At this point, shortcode will have to behave nicely with the page bundle's .md so it's great you're addressing this.


How to access the dashbord?

Hi.
I use the war file from your project and deployed to my server（Tomcat）. but failed to access the dashbord,  What is the local access path for the dashboard?      thanks advance

Same here. Trying on tomcat, the http://localhost:8080/dashboard comes as empty page


Add TK Wave kernels to conv benchmark

Add option to test TKW-based conv kernels to convbench.
Only limited subset of datatypes is supported for now (only f16xf16xf32)
Need latest iree-turbine main

Please rebase and it will pick up the runner label change so that CI runs


HMTL code in Notifications

So, there are some parts of html code in Notifications window:

Gotta get rid of them.

Notifications will be reworked, links will be underlined and painted to blue (as usual links). However they won't be clickable. To make them clickable we must completely rewrite notifications dialog window and change its structure.

Fixed in Master.

Fixed in Prod.


Create CI Workflow for TestCentric.Metadata

:tada: This issue has been resolved in version 3.0.3 :tada:
The release is available on:

GitHub Release
NuGet Package


GPU usage 15% / intel UHD graphics

Microsoft PowerToys version
0.53.0
Running as admin

[ ] Yes

Area(s) with issue?
Always on Top
Steps to reproduce
First enable Always on Top then pin a window by using the hotkey you've set up
✔ Expected Behavior
Low to non existing gpu usage (like the case with Deskpins)
Device : Dell latitude 3510 with intel i7 core and nvidia mx230 GPU / HDD
❌ Actual Behavior
gpu jumps to 15% usage whenever a window is pinned and stays there (increases with the number of windows pinned) & (percentages in video may seem wrong because recording software is also using gpu resources but the jump is apparent)
Device : Dell latitude 3510 with intel i7 core and nvidia mx230 GPU / HDD
Recorded preview:
https://user-images.githubusercontent.com/89031146/148662603-4f238bea-9806-4d01-8bef-deb1a7e0d716.mp4
Other Software
No response

After further research this seems to stem from enabling the (Show a border around the pinned window) setting , thus having a small dot or some other indication will solve this issue.
thanks for your time and attention

Preview for previous comment :
https://user-images.githubusercontent.com/89031146/148663000-f58d547a-a577-4122-b329-68a096f6dcd0.mp4

Duplicate of #15362

Thanks for reporting this. This issue is a duplicate.
I'm linking this issue to #15362 to centralize the discussion thread for tracking.
Thanks for your help to make PowerToys a better piece of software!


Add NativeErrorCode in Win32Exception.Message

Consider adding NativeErrorCode in the exception message.
Greatly improves debugging and logs reading.
For instance
class Win32Exception
{
 // Return original Message with the code
 public override string Message => $"{base.Message} ({NativeErrorCode})";
}

Another option is to hack "_message" property to not store the same message twice and get free serialization.

If this diverges from the behavior of Win32Exception on .NET Framework, that's not inline with the goal for this class. If Win32Exception behavior varies between platforms that can ultimately cause unexpected issues for consumers.
So while I don't challenge the value that you're proposing, PInvoke's charter is not to improve on Win32Exception. We only implement it in the first place because PCL profiles don't define it themselves.


Automate the unit-testing of the openebs-iscsi k8s driver

This was raised to cover the UT for the openebs-iscsi flexvolume driver, which has been deprecated.


custom_profile_fields: Update label for non-editable field toggle.

CZO thread

Before
After

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I tweaked the help center a bit more for consistency and pushed here: