Windows ce app container edits

Merging in part 2 of CE App Container page.
This page adds a guide on how to work with the CE App Container page.

Docs Build status updates of commit 6a6d4a8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:warning:Warning

Details

windows-iotcore/media/WindowsCEAppContainer/image1.png
:white_check_mark:Succeeded

windows-iotcore/media/WindowsCEAppContainer/image2.png
:white_check_mark:Succeeded

windows-iotcore/windows-ce-app-container.md

Line 20, Column 64: [Warning-bookmark-not-found] Cannot find bookmark '#Prerequisites' in 'windows-ce-app-container.md', did you mean '#prerequisites'?
Line 31, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 40, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 59, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 87, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 36, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image './/media/WindowsCEAppContainer/image1.png'. Alt text is required for accessibility. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 83, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image './media/WindowsCEAppContainer/image2.png'. Alt text is required for accessibility. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 474e2a2:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 474e2a2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container.md
:warning:Warning

Details

windows-iotcore/media/WindowsCEAppContainer/image1.png
:white_check_mark:Succeeded

windows-iotcore/media/WindowsCEAppContainer/image2.png
:white_check_mark:Succeeded

windows-iotcore/windows-ce-app-container.md

Line 20, Column 64: [Warning-bookmark-not-found] Cannot find bookmark '#Prerequisites' in 'windows-ce-app-container.md', did you mean '#prerequisites'?
Line 34, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 43, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 62, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 90, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 39, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image './/media/WindowsCEAppContainer/image1.png'. Alt text is required for accessibility. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 86, Column 1: [Suggestion-alt-text-missing] Missing alternate text for image './media/WindowsCEAppContainer/image2.png'. Alt text is required for accessibility. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


2022.2 Version is Launched

Any chance to get a new version for 2022.2, released yesterday? 👍🙏

Thanks for reminding 😊 Will do later today!

Published. Should appear soon once moderation will be done.
BTW still decided to not opt-in into floating version, so I can quickly re-test it for each version of R#. For most of the updates I actually had to tweak the code to fix the complication, so do not see huge win from that anyway 😉
So thanks for doing a good service and keep reminding me of updates 😊

Happy to help!
🙏🙏🙏


Ace3 libs are loaded out of order in BetterBags.toc

The various Ace3 libs depend on each other to be loaded in a specific order, which you can see in Ace3.toc. BetterBags.toc does not follow this order, which can lead to "missing" Ace3 components or APIs that are not missing but not loaded yet.
Any Ace3 libs that are unused in BetterBags do not need to be referenced or loaded. While the .pkgmeta doesn't require an order, I suggest matching .pkgmeta to the corrected BetterBags.toc to avoid confusion.

Have you observed an actual error?

No, I have not observed an error. I posted the issue because the Ace3 devs recommend loading their libs in a particular order to prevent "cart before the horse" problems. One thing I haven't tested is to disable ALL other addons, including BugSack and BugGrabber, along with a standalone Ace3; according to WoW's loading algorithm and Ace3's suggested load order, then yes, an error should be observed.

Can you show me the error, please? I'm fine with reordering, but if there's no error right now, I'm not going to spend the time on it -- you're welcome of course to send a PR as well!


Array pop does not change state

Array.pop is no longer updating the state in the latest build.
Current build (28 September 2017, version ad69d01):
var testArray = esper.eval("var testArray = ['one', 'two', 'three']; testArray.pop(); testArray");
console.log('testArray', testArray); //  ['one', 'two', 'three']

The current version doesn't update the testArray variable after pop.
Previous build on Esper.js demo website (23 Aug 2017, unversioned):
var testArray = esper.eval("var testArray = ['one', 'two', 'three']; testArray.pop(); testArray");
console.log('testArray', testArray); //  ['one', 'two']

The previous build has the correct behavior.

Interesting.
The problem here is actually that esper is missing the magic behavior where setting the length value of an array truncates the integer key values.  This misbehavior was sometimes masked in older version when the object was copied out of the esper because it would set the length property on the output object, and the browser would apply the magic behavior.

That's strange. Do you know why the unit tests are passing?
type-array.tests.js
        Array.prototype.pop
          ✓ should return the last item from the array
          ✓ should update the length
          ✓ should return undefined for an empty array
          ✓ should not affect length of empty array

That sorta works, but doesn't really fix the underlaying problem.
function p(o) { console.log(JSON.stringify(o)); }
var arr = [1,2,3];
p(arr);
arr.length = 1;
p(arr);
p(arr[2]);

Anya:~ rob$ node o.js
[1,2,3]
[1]
undefined

Anya:~ rob$ esper o.js
o.js
[1,2,3]
[1]
3

Should be fixed by 8e431a6


ReferenceError: exports is not defined

I'm getting this error after trying to import.
import useSWR from '@zeit/swr'

Would you provide some more information on your project setup? Are you using Next.js, CRA, or similar? Any configuration files would be helpful too.
This should work out of the box with Next.js if you want to get started quickly:
npm init next-app && yarn add @zeit/swr

Since webpacker adds a layer of indirection, you might want to verify everything is in the right places.  I would double check that @zeit/swr is in the node_modules directory and listed in your package.json alongside react and other packages.

We're running into this issue, too.
By default, webpacker configures babel to transpile node_modules, too. In our config, we disabled this, opting in to modules which provide ES6 code.
As swr uses arrow functions in it's dist modules, this breaks IE11, so we'd opt in to having babel transpile swr, too.
Now, something in the chain breaks and leads to ReferenceError: exports is not defined in the line
Object.defineProperty(exports, "__esModule", {
  value: true
});

(dist/useSWR.js)

This issue should have been fixed in v0.2.3.


Array.forEach is Incorrect

Doing something like:
    player
        .AllPlayers()
        .filter((p) => player.GetTeamId(p) == player.GetTeamId(2))
        .forEach((v) => {
            gameplay.SetTeam(v, player.GetTeamId(1));
        });

Will output a block like:

The only problem is, CurrentArrayElement cannot be used within a loop, hence, this code will fail in the game and break.

In portal code, it is much better to do a while loop, at increments:
For example:

or
while (player.AllPlayers().filter((p) => player.GetTeamId(p) == player.GetTeamId(2)).length > 0) {
    gameplay.SetTeam(player.AllPlayers().filter((p) => player.GetTeamId(p) == player.GetTeamId(2)).first, player.GetTeamId(1))
    logic.Wait(0.1)
}

I suggest maybe this been looked into as a possible replacement for the current  Array.forEach method


Fix/bad status code

In certain cases the statusCode wasn't set in in the proxy iframe, it was causing failing requests to appear as they were succeeding.
This should be tested together with D6511
(originally opened in https://github.com/Automattic/wpcom-proxy-request/issues/5 ),
Steps to reproduce that issue:

Run Calypso locally, go to /me
Select a new image to upload
Before clicking 'Change my photo', turn off the network in chrome dev tools
Click 'Change my photo'
See the success notice saying the new Gravatar was uploaded
See that the network request in fact failed, and no new Gravatar was uploaded to Gravatar.com

The steps above should result in error when there is no network, and with success when there is network.

LGTM 👍
Don't forget to remove the "REMOVE ME" commit and bump the package version to 4.0.4 :D


Thank you for this initiative!

Sorry, could not find a better channel to express my gratitude! This is a great project that fills a much needed niche to handle SQLITE extensions in a predictable and automatic way!
I'm using a MacBook M1, and quite some extensions are not available for mac arm architecture. Is there anything the community could help with to fill this void? I would really love to be able to install all of those current 58 extensions on a MacBook AIR M1 just by using sqlpkg. What would be the best way to contribute?
Cheers and have a great week start!
Roman

You are very welcome! I've just updated all the extensions I maintain to support macOS Apple processors. So you can install them with the sqlpkg.
As for extensions maintained by others (it's mostly @asg017, I think) — you'll have to ask them to add such support to their extensions. After that, I'll update the package specs so that sqlpkg can handle them as well.

I see. When I tried to install asg017/vss, it was missing the vector extension, that has no package for ARM.
Then I took the release directly from https://github.com/asg017/sqlite-vss/releases. (https://github.com/asg017/sqlite-ecosystem#sqlite-vss) - https://github.com/asg017/sqlite-vss/releases/download/v0.1.1-alpha.20/sqlite-vss-v0.1.1-alpha.20-loadable-macos-aarch64.tar.gz.
And it has the vector extensions zipped into the archive:
./sqlite-vss-v0.1.1-alpha.20-loadable-macos-aarch64
./sqlite-vss-v0.1.1-alpha.20-loadable-macos-aarch64/vector0.dylib
./sqlite-vss-v0.1.1-alpha.20-loadable-macos-aarch64/vss0.dylib

I've tried it, it works. I only needed to mark it a as allowed binary with xattr -d com.apple.quarantine *.
Granted this is an unusual case and there are not standards right now... This is why it's so great to have a single place with all the extensions, so it's possible to come up with some standards for compilation / distribution.
But yeah, I'll bug @asg017 if I need one of his extensions to work on ARM.
Thanks and have a great week!
Roman

Okay, so it looks like you don't need the separate vector extension because it's already included in the vss extension.


Dummy Configuration Unnecessary?

It does not appear that the configuration in Step 10 is necessary.  Configuring the dummy settings on the gateway caused the backend health for the dummy backend to come through as unhealthy, resulting in a 502 Bad Gateway for external service requests through the App Gateway.
Once we removed the dummy settings and set the default backend address pool and http settings to the proxy backend pool and proxy backend http settings respectively in the url path map, the integration behaved as expected (non-existent APIs would return 404).

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

ID: 37c1f253-44c2-bd07-4c74-9d4c77c45e6e
Version Independent ID: 281ce98c-115b-3c39-52b7-3df95dfd8b52
Content: How to use Azure API Management in Virtual Network with Application Gateway
Content Source: articles/api-management/api-management-howto-integrate-internal-vnet-appgateway.md
Service: api-management
GitHub Login: @solankisamir
Microsoft Alias: sasolank

@scottzilla Thank you for the feedback!  We are investigating the document in question and will get back to your shortly.

@scottzilla I'm assigning this to the document author so that they can review and update the document appropriately.

yes we have updated the documentation and removed the configuration.

@scottzilla We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Thanks!


Tone.Player seconds

Hi @tambien
Sorry for posting this in github issues but it seems that forum is not really active and a lot of questions are answered for a long time.
So I'm writing a player with an ability to seek while playing and automatically play next song when current ends.
The first problem I've encountered is that Tone.Player doesn't have an option to check the current time while playing. Then I've found this issue https://github.com/Tonejs/Tone.js/issues/361
I've tried to make workaround with syncing player to Tone.Transport and it worked as expected by changing slider position with Tone.Transport.seconds. But unfortunately I can't get the event when the song has fully played. I'm using the typescript branch. Assigning an onstop callback on Tone.Player and calling Tone.Transport.pause() triggers onstop callback on player.
I've also investigated in using Tone.ToneBuffersSource but he has the same problem as Tone.Player not having an option to check the current time playing.
I've made a workaround using Tone.Player.onstop callback and checking the difference between Tone.Player.buffer.duration and Tone.Transport.seconds. But it has some deviation which depends on the performance of system and can be from -0.1 to -0.5.
Also I have in mind another workaround by triggering a Tone.Event at the song duration time
Something like here https://github.com/Tonejs/Tone.js/blob/7236600182d336d6598f86d7d7afe8761e733774/Tone/source/OneShotSource.ts#L171-L176
Maybe there is an option to add back seconds to the Tone.Player or provide one more state value when pausing? Or I have missed something in docs
Thanks

@Grimones Unfortunately it's not possible to add seconds back because of the complexities of having variable playbackRates with the player combined with loopStart/End behavior. Once safari allows for playbackRate to be scheduled with another signal by connecting it (currently not easily possible to create a shim for this behavior as well), i think there is another way where adding seconds is possible.
Until then i am going to close this issue. I think the simplest solution to your issue is to either use onstop but since as you pointed out that's not using the Web Audio API's scheduling parameter, it is susceptible to loose timing. The other solution would be to try to compute the end time of your player manually by calculating the startTime + duration / playbackRate and scheduling the next buffer to start exactly at that time.
Hope that helps! i will try to check back once safari gets around to fixing this behavior.


GGRC-8315 Rework test_data_handlers.py

Issue description
Needs rework tests from test_data_handlers.py without custom slugs.
Steps to test the changes
Run tests from test_data_handlers.py and all tests should pass.
Solution description
Import from assessment_notifications.csv has been replaced by import assessment data.
Sanity checklist

[x] I have clicked through the app to make sure my changes work and not break the app.
[x] I have applied the correct milestone and labels.
[x] My changes fix the issue described in the description (and do nothing else). 🤞
[ ] My changes are covered by tests.
[x] My changes follow our performance guidelines.
[x] My changes follow our js and/or python guidelines.
[x] My commits follow our commit guidelines.

PR Review checklist

[ ] The changes fix the issue and don't cause any apparent regressions.
[ ] Labels and milestone are correctly set.
[ ] The solution description matches the changes in the code.
[ ] There is no apparent way to improve the performance & design of the new code.
[ ] The pull request is opened against the correct base branch.
[ ] Upon merging, the Jira ticket's fixversion is correctly set and the ticket is moved to "QA - In Progress".

PR was closed in reason wrong repository.


Not Detecting few words in French, It is detecting as a English And Few words not detecting as English but it is English

I have few words or sentences in French, Need to detect the Language of it. While running the script those words are recognizing as a English and getting failed.
Ex: French Words detecting as English
"value":"Seleccionar actividades"
"value":"Contacter le service client:"
Below words are in English but it is detecting as French.
"value":"notifications!"
"value":"Contributions: $0.00" etc.,
Can you help me to identify this words as a French and English properly.
Thanks in advance!

@vidyasagarfis Sorry for my late response. Statistical approaches to language recognition are never 100 % correct. Experiment with the LanguageDetector settings and methods to find out what works best for you.


Show status of PR in overview

With the new PR review features GitHub introduced today, it's possible to "review" a PR. It is possible to approve the PR, or to request changes.
My problem is, that after I approve or request changes, I can't see in the overview what I've done. I need to click on every PR and check what the status is.

What kind of status are you interested in? Like Approved, Pending requested changes, etc?

Yeah, those two statuses.

Seems like many people agree: https://twitter.com/dan_abramov/status/777224519543128064
Anyone wanna do a pull request?

I like the idea a lot, but this is could be brutal for people on slow connections if we don't offer a setting to disable. We'll have to make (up to) 25 requests on page load anytime you visit /pulls/. The GitHub API doesn't have the ability to batch requests (and the new GraphQL API doesn't have the functionality we'd need quite yet), so we'd just be fetching the DOM for each PR page

@DrewML, is it correct that the GitHub API doesn't even have the ability to see the status at all? I've browsed through it, but the "review comments" API also doesn't seem to have it.

@SpaceK33z Yeah, doesn't look like it :( We'd have to do fetch + DOM parsing/scraping like we do with real names functionality.

While these reviews could prove to be immensely useful I think they are in very early stage at the moment and GitHub would significantly improve them in the next 6 months (as stated at GitHub Universe). They could fix some nagging problems in the review process, but could also improve the API and the rest of the UI around them. I'm not sure this is worth doing before we see what they'll do with them. I guess we could contact GitHub and urge them to add the review status to the PR list. I'd also like to add them to the search filters.

Looks like GitHub implemented exactly what I wanted:

If you hover over them you see more details. Super awesome! Closing this.


Fix slowdown in progressive render

this is a partial fix for #124
A new method was added: renderAnimated . This will render the layers progressively, to show progress while loading. Meant for large files that can take many seconds to render.
the gradient can be maintained in the DEMO because we load the whole gcode in advance. So the gcode should be parsed as a whole before rendering. For true incremental rendering the gradient should be disabled.
Render progressively:

[x] when initially loading benchy
[x] when dropping a new file
[x] when choosing a file from the file selector
[x] render progressively when toggling tubes
[x] maintain gradient
[ ] minimize code impact webpreview class:

[x] don't expose new methods
[ ] separate animation in a new class
[x] double check state/prevState handling and if it is really needed
[ ] possibly create a new method processLayer that does only that.

[ ] find a good 'chunk' ratio for rendering reasonably smooth for small and large models
[ ] in the demo, skip animation for small files?

I just tested it. Wow. It's so smooth now! I am impressed!

I finally figured out we could parse it all, know the number of layers and then render incrementally. This has the added effect that the color gradient can be accurately computed even when rendering the start. That's why it is stable now. Previously the gradient stretched out during rendering.

I'm not sure about the api change I did. I'm need of critical opinions

Are you sure we need to extract the animation in a new class right now? How would that look like?


RC.5 TestBed and Test Import Updates

Mainly just changing out the new import locations, as well as replacing the shorthand of bep with the TestBed implementation.
Also updated the tns-ios version to use the updated minor release.
I believe nativescript-angular is still not supporting rc.5, correct? Because I could not successfully get past an animation driver conflict, when attempting to update the NS app to rc.5 (not part of this PR).
(Duplicated PR because I accidentally tried to merge into master...haha)

CI is still running but I'll merge this tomorrow if it passes, thank you so much for your help!

I'll fix the CI warnings today and hopefully wrap this up. big help @sean-perkins 👍


Always send uniques

First of all thanks very much for the embed commit, my notifications look so much cleaner now!
A feature I still would like to see added is an option under Loot; Always send uniques.
The way it works now is that the collection log notification will still pop but if you already have gotten it once it obviously won't.
Could this be a new toggle? Thank you it's very nice to see active development on this!

My immediate question is how do we go about checking what is a unique?
From what I can see discord-rare-drop-notifier has their own list but taking that approach would be no fun. https://github.com/BossHuso/discord-rare-drop-notificater/blob/master/src/main/java/com/masterkenth/EventRarity.java
Hopefully there's some API that we could use to figure this out 🤔

By unique, do you mean every item in the collection log? So if this setting is on, you'd send a loot notification every time you loot a:

Vorkath's head from Vorkath
Soaked pages from Tempoross
Ancient Shard from any monster in Catacombs of Kourend
Ancient essence from Phantom Muspah
Iasor/Kronos/Attas seed from Hespori
Granite dust from Grotesque Guardians
Mole skin or Mole claw from Giant Mole
Bolt rack from Barrows

Yeah, that is kinda what I meant. And then for example that you can set a minimum value and drop rate.
For example I don't want to have every Mole claw as notification but if I could set the value rarity to have a minimum of 1/256 it would still give me notifications for rare drops that maybe cost less than what I have set up under "Loot" as Min Loot Value.

Do you think your recent suggestion of https://github.com/pajlads/DinkPlugin/issues/139 would cover this use-case effectively?

Do you think your recent suggestion of #139 would cover this use-case effectively?

Yeah, I think it does. Maybe it's better to close this and continue in that topic.


Can't scroll with mouse selection

Can't scroll with mouse selection.
This problem also be occured in CodeMirror 6 Top Page.
https://user-images.githubusercontent.com/7702653/124218179-ad776f00-db34-11eb-97fe-f82b922ad45d.mp4
This problem is due to viewport.
I forked codemirror/view to hata6502/codemirror-view, and disabled viewport.
commit: https://github.com/hata6502/codemirror-view/commit/b3fb35c967726935ad0c56ff08228e6511d78d0c
But, this problem should be resolved by fixing the viewport logic.
Thank you for maintaining!
Bug tracking information
OS: Ubuntu 20.04
browser: Google Chrome 91.0.4472.114
Code Mirror version<EMAIL_ADDRESS>

Attached patch seems to resolve this.


Added SJCET to the list

http://www.sjcet.co.in/ St. John College of Engineering and Technology (SJCET) provides facilities for professional education in the rural area with the mission of 'Serving to Educate Educating to Serve' by offering four year Degree Courses in Civil Engineering, Computer Engineering, Electronics and Telecommunications Engineering, Information Technology and Mechanical Engineering and two year Post Graduate Degree Course - Masters of Management Studies.

@jerilkuriakose The website is currently not available, with a error message "An internal server error occurred. Please try again later." We'll look at it some time later, and it may cause a delay with processing your request. Thank you for the understanding.

@jerilkuriakose Pull request merged. Thank you!


Bump minimatch version to avoid vulnerability

minimatch < 3.0.4 uses an old version of brace-expansion, with a known vulnerability:
https://snyk.io/test/npm/brace-expansion/1.1.6

Not needed due to auto update via ^.


[SPARK-8876][SQL] Remove InternalRow type alias in expressions package.

The type alias was there because initially when I moved Row around, I didn't want to do massive changes to the expression code. But now it should be pretty easy to just remove it. One less concept to worry about.

Merged build triggered.

Merged build started.

Test build #36727 has started for   PR 7270 at commit 72fc842.

Test build #36727 has finished for   PR 7270 at commit 72fc842.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.


Feature flaw: EditCommand not displaying the right message usage.

After executing "edit 1 n/alex", even though Student 1 has attended classes, under the attendance message returned, it will not be shown. I am thinking either remove the displaying of attendance field after EditCommand is executed, or remove the editing of attendance from EditCommand.

Okay this seems fixed already.


Revert "Add a completion handler to FIRExperimentController's updateE…

…xperimentsWithServiceOrigin: method (#4897)"
This reverts commit 7587c3c2e4af3f1cd7e10a33eb075b81a18941ae.
This change needs to go through an API review first.
cc @christibbs

Unnecessary at the moment - will not be included in M65 so this doesn't need to be reverted.


IndexError: Caught IndexError in DataLoader worker process 0.

When I ran python 01_pytorch-vit.py or python 00_pytorch-vit-random-init.py, I got this error. How to solve it? Thanks!

Hi there,
wow, this looks bizarre. It seems that the data loader may have gone out of control suggesting these very high index values. I've never seen something like this to be honest.
Have you seen something like this before @awaelchli?

@bjzhb666 Did this happen at the beginning of training or sometime in the middle? Do len(dataset) and len(dataloader) return the expected values?

Thanks for your quick reply.
This happened at the beginning of training. I print len(train_dataset) and len(train_dataloader), it returns 50000 and 703 (50000*0.9/64, where 64 is the batch size). They are all correct.

Hm, this sounds normal to me. This error is so weird, I don't have any rational explanation for this.

Shouldn't matter, but can't hurt to try 😄:

create a fresh environment 2) reinstall torch

Same error.

I think I know where the error comes from. Since we are using regular dataloaders here (I used them for simplicity) instead of Lightning DataModules, the multiple GPUs try to download the dataset at the same time which can lead to corrupted files. I will update the files so that the data is downloaded separately first.
But what you can try is to delete your data directory, and then run it with 1 GPU and Frabric(..., devices=1)
If the error then still persists, then there is a different issue.


Update SECURITY.md

AWS Security Outreach submitting update to security.md file to include new extended VDP portal with Hackerone. The GitHub Admin Team is applying these changes to all Amazon-managed organizations.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing in favour of https://github.com/aws-deadline/.github/pull/21


Powertoys Run does not find or cannot open Microsoft Office apps

When I use Powertoys Run, I cannot open the default version of the Microsoft Office apps such as Excel or Word. When I type "Word" or "Excel" or "Microsoft Excel", or some combination of that into the search box, the apps do not appear as options to launch.
However, I can search for and launch specific files by name that will then open in those apps.
I'm not super familiar with how the launcher works so if this is not a bug or is inherent to how the launcher works, I apologize. It's just I can launch the default version of other apps so I do not understand why the Office apps don't work this way.

Running Powertoys Run 0.18.2 on Windows 10 (2004), can't reproduce. Office is found for me.

I'm also running Powertoys Run 0.18.2 on Windows 100 Build 18363. I'm using the Office apps downloaded with my Office 365 subscription. Not sure if that makes a difference? The apps are downloaded on my device so they aren't the online versions.

Not sure if there's a way for me to track down or diagnose the issue

Can you write down your office directory?

So I just looked in Program files and didn't see Office and couldn't find where it was located. So I went online and reinstalled the Office 365 apps. Now the executables to launch the apps are here:
C:\Program Files\Microsoft Office\root\Office16
It looks like it could be the correct folder but they still don't show up in the Powertoys launcher.

I got it to work. I uninstalled and reinstalled Office and uninstalled and reinstalled Powertoys. Not sure what led to the original issue or the issue continuing after the first time I tried reinstalling Office.
I appreciate the suggestion about it being installed someplace weird .

Great to hear it's working now, but we need to investigate this further. I'm closing this in favour of #3146.

Have this with v0.19, Office Apps are installed via Microsoft Store. Word, Excel Point are not found. Was not a Problem with 0.18.x.


Firefox has double playback on the official YouTube site (not in embedds)

Script version
on the extension version 5.5 (and 5.4) this issue occurs:
The bug
1:The player now always opens as if it's an embedded page even on the official YouTube site
2:The default player seems to still be on as after a few seconds it plays again (refreshing fixes this)
3:Ad blocking still works perfectly so there's that
Expected behavior
It to open with default YouTube.com  video player and not have the video playing double
Screenshots
It's just the embedded video player instead of the usual player, for the rest it's the same
Desktop:

OS: Linux
Browser Firefox

Additional context
issues started appearing in the first few v5s however I'm only confident about 5.5 and 5.4

Yes, I came here to report this too.

This is also occurring on opera gx, win11

一样

Temporary fix, disable the script and mute your youtube player, then re-enable the script. You'll still have double videos playing but the one that gets overwritten won't be playing audio

Temporary fix, disable the script and mute your youtube player, then re-enable the script. You'll still have double videos playing but the one that gets overwritten won't be playing audio

omg your a genius


Fixed typo in Azure Active Directory conditional access

@devlead : Thanks for your contribution to the Azure documentation! The author, @markusvi, has been notified to review your proposed change.

#sign-off


Space around zones show up even when deactivated

Microsoft PowerToys version
0.64.0
Installation method
PowerToys auto-update, Microsoft Store
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
https://user-images.githubusercontent.com/117743462/200579711-a48517a5-7c1f-49bc-8561-1d22ed9b7a23.mp4
PowerToysReport_2022-11-08-17-45-03.zip
Select any layout with the space around zones deactivated, whether it's one that was created before the update or a brand new one.
The preview in the editor will show that there should be no spaces between the zones.
After applying the layout, when attempting to move a window to a zone, the preview shows the space and the snapped windows will actually be spaced apart.
✔ Expected Behavior
The zones should not be spaced apart as per the setting in the layout options.
❌ Actual Behavior
The zones have spaces between them, even with that option was deactivated in the layout options. This was working fine before the 0.64.0 update.
Other Software
No response

/dup #21630


GDScript 2.0: Global enum shadowing it's class_name should show specific error message

Godot version
4.0dev
System information
Pop!_OS 22.04 LTS
Issue description
When assigning a global enum to a const variable, the compile error Assigned value for constant "<name>" isn't a constant expression. is shown.
Here there shouldn't be an error, since the enum is constant.
This only happens for global enums defined with class_name (see MRP).
EDIT: This error is happening, because the enum has the same name as the class_name. If it is renamed the errors go away.
I propose adding an error message when an enum has the same name as its class_name to make it clearer for the user ,why this happens.
Steps to reproduce

Create script GlobalEnum.gd with content

class_name GlobalEnum;
enum GlobalEnum{A, B};

Create script Test.gd with content

func _ready():
  const x = GlobalEnum.GlobalEnum.A;

Check console and see the error Assigned value for constant "x" isn't a constant expression..

EDIT: When renaming the enum to f.e. Values, the error doesn't happen. Everything works.
Minimal reproduction project
63942_Test.zip

Have you registered GlobalEnum.gd as an autoload-script?

Have you registered GlobalEnum.gd as an autoload-script?

As you can see in the MRP, it is not registered as an autoload. But I found the error and will update the OP to reflect that.

@Calinou I think it isn't a bug anymore, but an enhancement with the proposal to add more specific error messages, when an enum name equals the class_name it is defined in.

Is there a reason why classes can't have members with the name of the outer class? Pretty sure this works just fine in most other programming languages with nested types (random example, works in Crystal). Curious to hear what the language designers think but I'd reclassify this as a bug.
Whether it's good practice is another discussion entirely (but imo it's still sensible since we don't have global enums)

@jgillich I agree, that this is a common scripting language feature. Classifying this issue as bug is in my opinion wrong, because gdscript never has supported this, so there isn't anything "broken". This enhancement should only improve the feedback to the user. To implement the feature you are requesting, I suggest opening a seperate issue.
The priority of it I think is pretty low though, because with some best practice variable naming the feature is not really necessary.
Thank you for your input!

Fixed by #70613.

Note that this is only possible for GDScript enums, not for native and @GlobalScope enums.


Build fails for linux starting with v2.44

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
This is an issue with building the source code in linux.  Using Linux Ubuntu 20.04, the last known good build seems to be v2.43.  It seems this build error is in every version after v2.43 I tried to compile v2.44, v2.45, v2.47 and they all give this build error:
Using gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
When I tried to build with these cmake settings:
cmake ../ -DFORCE_RSUSB_BACKEND=true -DBUILD_PYTHON_BINDINGS=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DCMAKE_INSTALL_PREFIX=/opt/realsense
There is an issue with what seems to the depth quality.  It fails with this error:
The first error is:
n file included from /home/richardt/projects/apira-avatar/librealsense/common/realsense-ui-advanced-mode.h:7,
                 from /home/richardt/projects/apira-avatar/librealsense/common/model-views.h:26,
                 from /home/richardt/projects/apira-avatar/librealsense/common/model-views.cpp:21:
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:549:22: error: ‘const char* librealsense::get_string’ redeclared as different kind of entity
  549 |     RS2_ENUM_HELPERS(rs2_calib_target_type, CALIB_TARGET)
      |                      ^~~~~~~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:519:48: note: in definition of macro ‘RS2_ENUM_HELPERS_CUSTOMIZED’
  519 |     LRS_EXTENSION_API const char * get_string( TYPE value );                                       \
      |                                                ^~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:549:5: note: in expansion of macro ‘RS2_ENUM_HELPERS’
  549 |     RS2_ENUM_HELPERS(rs2_calib_target_type, CALIB_TARGET)
      |     ^~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:519:36: note: previous declaration ‘const char* librealsense::get_string(rs2_timestamp_domain)’
  519 |     LRS_EXTENSION_API const char * get_string( TYPE value );                                       \
      |                                    ^~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:515:5: note: in expansion of macro ‘RS2_ENUM_HELPERS_CUSTOMIZED’
  515 |     RS2_ENUM_HELPERS_CUSTOMIZED( TYPE, 0, RS2_##PREFIX##_COUNT - 1 )
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:548:5: note: in expansion of macro ‘RS2_ENUM_HELPERS’
  548 |     RS2_ENUM_HELPERS(rs2_timestamp_domain, TIMESTAMP_DOMAIN)
      |     ^~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:549:22: error: ‘rs2_calib_target_type’ was not declared in this scope; did you mean ‘rs2_calibration_type’?
  549 |     RS2_ENUM_HELPERS(rs2_calib_target_type, CALIB_TARGET)
There are more errors of this type about the ambiguous operator overload
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:524:39: error: invalid conversion from ‘int’ to ‘rs2_timestamp_domain’ [-fpermissive]
  524 |             return out << get_string( value );                                                     \
      |                                       ^~~~~
      |                                       |
      |                                       int
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:515:5: note: in expansion of macro ‘RS2_ENUM_HELPERS_CUSTOMIZED’
  515 |     RS2_ENUM_HELPERS_CUSTOMIZED( TYPE, 0, RS2_##PREFIX##_COUNT - 1 )
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:549:5: note: in expansion of macro ‘RS2_ENUM_HELPERS’
  549 |     RS2_ENUM_HELPERS(rs2_calib_target_type, CALIB_TARGET)
      |     ^~~~~~~~~~~~~~~~
/home/richardt/projects/apira-avatar/librealsense/tools/realsense-viewer/../../src/types.h:526:24: error: ambiguous overload for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream<char>’} and ‘int’)
  526 |             return out << (int)value;                                                              \
      |                    ~~~ ^~ ~~~~~~~~~~
      |                    |      |
      |                    |      int
      |                    std::ostream {aka std::basic_ostream<char>}

Hi @bontsai  I have not seen these particular errors before.  Most of the CMake build instruction that you are using is widely used, with the rarer part being the -DCMAKE_INSTALL_PREFIX=/opt/realsense statement to control where librealsense is built.
As a starting point in this investigation, I would therefore suggest removing this command from the CMake build instruction to see whether it makes a positive difference.

Hi @MartyG-RealSense, so I haven't tried to run it, but to clarify the DCMAKE_INSTALL_PREFIX=/opt/realsense actually only controls where the libraries are installed from the make install.  Not where the librealsense is built.  It is still built in the build directory where you run the cmake .. from
I will inform you if it works without.  I'm still guessing this is still a problem and a bit miffed that nobody has actually run into this problem for three different versions.  As I mentioned it built for 2.42 and because of new hardware I needed to upgrade as that old version didn't detect the camera.  and started with 2.47 and went one by one until 2.43 worked and I was able to use it with the new camera.

Okay, thanks very much @bontsai - I look forward to hearing whether the build works without using DCMAKE_INSTALL_PREFIX

Hi @bontsai  Do you require further assistance with this case, please?  Thanks!

Hi @MartyG-RealSense - I actually tried what you suggested and it seems to work.  Ironically I got the recent v2.48 and was able to use the one with the CMAKE flag for the install directory to work.  I did not bother to try with the other versions, since I'll probably just go with the latest.  But I still do think there is some issue with possibly the CMAKE flag for install directory which was introduced in v2.44

Thanks very much @bontsai for the confirmation that the CMake flag DCMAKE_INSTALL_PREFIX works for you in 2.48.0.

Hi @bontsai  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


AZ-104 image download fails

Describe the bug
When downloading the AZ-104 course, the download stops with an error : question43.jpg couldn't be opened.

Download fails because of missing image in source folder. PR opened to fix image reference:
https://github.com/Ditectrev/Microsoft-Azure-AZ-104-Microsoft-Azure-Administrator-Practice-Tests-Exams-Questions-Answers/pull/2

FEATURE:
Implement better error handling when downloading courses. When image does not exist, skip image and show the missing image error after the course has downloaded completely. Might make sense to add a "Send debug log to developer button".

We're aligned on the error handling mechanism ;-) just added my notes to https://github.com/Ditectrev/Microsoft-Azure-AZ-104-Microsoft-Azure-Administrator-Practice-Tests-Exams-Questions-Answers/issues/1#issuecomment-2180889109


go-ceph: bump Go version of module to 1.17

Updates the Go version of the module with go mod tidy -go 1.17,
which also adds some explicit requirements in order to support lazy
module loading.
Signed-off-by: Sven Anderson<EMAIL_ADDRESS>

You mean oldest supported version, right?
So, as you can see it didn't remove anything from the sum file or changed versions in the mod file. Therefore it still would work with older versions. Also please note that compatibility is always set to one version before the specified one, so 1.16 in this case. Since we don't test with older Go versions, any other version would be quite arbitrary.

Huh, I had no idea about that tidy behavior. You learn something new every day. :-)

Hah. This is all new-ish stuff that wasn't in Go 1.16 so I'm no longer surprised I didn't know about it. I'll read up on https://go.dev/ref/mod#graph-pruning and https://go.googlesource.com/proposal/+/master/design/36460-lazy-module-loading.md  to try and better understand the ins and outs of this feature better.

Cool. However, for this PR it's orthogonal and therefore irrelevant, since the versions didn't change. I even tried with -compat 1.12, and it doesn't complain and has exactly the same result. So I can also claim, I created this PR with go mod tidy -go 1.17 -compat 1.12 if that makes you feel better. ;-)


Better test.extend API

Clear and concise description of the problem
I'd like to propose a better way of reusing the extend API.
The example illustrating both the new pattern and the pain points with the current implementation:
// Painpoint 1: vitest does not expose types I could use here; what is `task`, what is `use` - TypeScript can't tell.
export const myAppFn = (params: MyAppParams) =>
  async ({ task }, use) => {
    const state = runApp(params);
    await use(state);
    await state.cleanup();
  };

// Here is how the new API composition is proposed to work:
// Painpoint 2: no types for use here either.
export const withMyApp = (params: RunNodeParams): WithNode => ({
  myApp: myAppFn(params),
});

Usage:
import { expect, test, describe } from "vitest";
import { withMyApp } from "./testlib";

describe("a context with my app", () => {
  const extest = test.extend(withMyApp({ args: ["--dev", "--tmp"] }));

  extest("hello world with my app", async ({ myApp }) => {
    await myApp.boot;

    await expect(myApp.request("hello")).resolves.toBe("world");
  });
});

The idea here is that we could share the withMyApp functions that enable us to parametrize the test context without being tied to a particular describe/test fn. Normally you would shared test.extend(...) instead of that ... - but then when you need to have a describe.extend(...) or it.extends(...) you have to declare and expose them again.
Another thing about this is it allows parametrizing the context - see how we pass params to withMyApp call? These parameters can be tweaked per test.
Suggested solution
Actually, what's needed to use this today is to expose more internal types, like Fixtures, etc. Maybe some rearchitecting of the TypeSystem will be necessary to make the types more pleasant to use.
If thus pattern is enabled, it should also be documented.
Alternative

Let every use who implements this declare their own types - bad for many reasons.
Just don't do it - use before/after and etc.

Additional context
In my case, I want to e2e test a CLI app that spawns its own server and exposes a couple of sockets with HTTP servers on them. Not sure if it's relevant.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

If you just need to expose types, pr welcome. I don't see any new public APIs needed to implement what you want.

Yeah, well, I guess exposing types would be enough here. That is if we don't want to recognize what I outlined as a pattern and do the work associated with that - docs, etc. So, I'll make the PR. What about the pattern though?

Yeah, well, I guess exposing types would be enough here. That is if we don't want to recognize what I outlined as a pattern and do the work associated with that - docs, etc. So, I'll make the PR. What about the pattern though?

Your pattern is just a wrapper around test.extend. I think it's fine to leave implementation to users if the want to experiment with the API.

Ok, I guess I've messed up formulating my point here, I was authoring this very late at night, and I think I didn't communicate my point straight (i.e. the title is misleading).
My point here is that vitest has issues with not exposing types here and there. I have personally stumbled upon a but too many instances where I want to extend vitest somehow, and the types are there but just not exported. This is the root cause, I'd say.
How to solve it? I was thinking if we have a particular pattern that is documented and actually used by people it would create sort of a QA pressure on keeping those types in check. As there is very little way of ensuring people will actually keep the types exported. You'd think it's common sense - but here we are, and this means there is some sort of fundamental issue with the current way design of the modules (i.e. it makes it easy to do this mistake and forget exporting the types) or it is a development culture issue (meaning people omit the type exports intentionally, and it passes the code review and QA). Either of these issues will be solved by pushing the pattern into the documentation, making it into a problem of documentation/implementation coherence, which is ultimately a problem that a lot more people tend to be involved in.
Am I making sense?
Also, sorry for the lengthy messages. I have a trail of thought here and it seems like the suggested solution doesn't make sense without me providing the context for how I got to it.
Also, the proposed solution is actually a partial one, since it will create this QA pressure just for this code area, while leaving the others uncovered. It seemed like a good idea still when I was originally writing it, however it doesn't anymore - I guess we should really try to look and see how to address the core problem.
I am, however, unsure this discussion can reach the whole core team behind vitest - as it is their input is what would be required to solve the lacking types issue now just once and for just these particular types, but once and for all.

I am, however, unsure this discussion can reach the whole core team behind vitest - as it is their input is what would be required to solve the lacking types issue now just once and for just these particular types, but once and for all.

Fundamentally, I don't think we can solve this. Vitest team works in their free time and doesn't have to follow any strict rules. We can limit the code only with linters. QA is done usually by me and it's not unusual for me to miss something. I usually check PR description, so we can add bullet points to export types if there are any.
I think that with the current pace of development, it's fine to miss some things and add them in a fix later on.
If you have any problems with types, you can simply open an issue or even a PR to expose them. Just like here 😄

What is the thinking process behind the decision to make only the surface types exposed, but no the inner ones?

Because we risk creating breaking changes by exposing everything.

as I'm writing this, I've decided to dig in a bit into the code in this repo - and it doesn't look like the types that are not exposed are there...

Types are exposed manually here:
https://github.com/vitest-dev/vitest/blob/edb322fe7539f362f83c00dc3b0229ae2f1fca65/packages/vitest/src/types/index.ts#L4
I personally think exposing types manually is better for the end user because we control what is bundled in this case. We had a lot of releases where something that should not be bundled as part of the bundle.
Runner-related types are here:
https://github.com/vitest-dev/vitest/blob/edb322fe7539f362f83c00dc3b0229ae2f1fca65/packages/vitest/src/types/tasks.ts#L25
I guess technically it should be fine to expose everything with an asterisk here because if the package exposes it, then we can probably export it. And limit what's exported inside the package.

I think this can be closed.


report_client make error

Some errors occurred during compiling the report_client.
report_client.cpp:26:28: fatal error: boost/format.hpp: No such file or directory
#include <boost/format.hpp>
^
compilation terminated.
make: *** [report_client] Error 1

install boost
yum install boost boost-thread boost-devel

Retry 3.1.0


Deep MNIST - exit code 139 (interrupted by signal 11: SIGSEGV)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): I have copied all the code lines from the tutorial Deep MNIST for Experts manually into a python file.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Arch Linux, kernel: 4.13.12-1-ARCH
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v1.4.0-rc1-11-g130a514 1.4.0
Python version: 3.5
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: Nvidia GTX770 4GB
Exact command to reproduce: accuracy.eval(feed_dict={x: mnist.test.images, y_: mnist.test.labels, keep_prob: 1.0})

Describe the problem
I am trying to run the example code from the tutorial Deep MNIST for Experts by copying every line from the tutorial into a python file and running it. The first part of the script with the model with a single linear layer runs fine, but the second part with a multilayer convolutional network fails to run. When the last line of the script executes: print('test accuracy %g' % accuracy.eval(feed_dict={x: mnist.test.images, y_: mnist.test.labels, keep_prob: 1.0})) I get the following error: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV).
I tried to evaluate the accuracy with a batch of size 50 from the testing data instead of supplying mnist.test.images and mnist.test.labels and that worked fine.
I was directed here from Stackoverflow because this was believed to be a bug (Stackoverflow question).
Source code / logs
I am unfamiliar with gdb so if I have missed to provide any relevant debugging output I'll try to add it if you can tell me how to get it.
Source code
Stackframe
Backtrace

Code 139 is attempt to access a virtual address which is not in your address space, which would support a memory allocation error, which could happen easily if you are on 32-bit system
SIGSEGV is a hard crash of the process do to an invalid memory access in native code, it has no chance to signal that to the multiprocessing host.
It should throw an exception on its own, is that not happening?

I am running it on a 64-bit system and the exit code message is the only error output I get from running the program. The exit code message is from running the python code through my IDE (Intellij). When I run it from a terminal with and without gdb I only get Segmentation fault (core dumped)

To clarify, are you using a GPU version of TensorFlow? You listed a GPU, but put N/A for CUDA/cuDNN version. I cannot reproduce with either.
/CC @benoitsteiner @rmlarsen, any ideas what the issue could be?

No, I'm using a standard build of TensorFlow running on my CPU. Yes, I realise it might be confusing so I changed the GPU to N/A aswell.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

+1  I'm getting a similar error on the following platform:
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 10.13.3
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.6
Python version: 3.6
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: (my own script, using standard tensorflow ops: while, rnn, scatter_nd, etc)

Hi ,are you solve this problem. i getting a similar error .
but i runing on GPU,using this code https://github.com/sampepose/flownet2-tf
waiting for you write back Thanks

Nagging Assignee @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 53 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 68 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 83 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 98 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 113 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 128 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 143 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@jfjallid sorry for the gap in responding. Is this still an issue for you?

@cy89 I do not now. I could not get around it so I stopped using tensorflow while awaiting response to this ticket and now I do not have it installed anymore.

Nagging Assignee @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 75 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 89 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Please check with the latest version of TensorFlow. Feel free to reopen if the issues still persists.
Thanks!


⚠ Bofrost.de has degraded performance

In 03cc442, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2200 ms

Resolved: Bofrost.de performance has improved in 856041f after 35 minutes.


Bluelink: add CCS api support

This adds support for newer Hyundai and KIA models, such as Hyundai Kona SX2. I've tested with said Kona. It would be good if someone could test with a Kia and an older Bluelink version.
This is the first piece of Golang I have ever written, so I'm happy to take feedback in case something is not quite idiomatic.

Starker PR!

I see now only "Kilometerstand" mileage

After a while it is working!!!!

@horstvogel position and odometer update immediately, the rest every refresh interval, safely 5 minutes. This is due to the structure of the old bluelink api, the new one returns everything in a single call. Optimizing this means less shared code, so for the first version I took the easy way. 😉


[RFC] Versioning and backwards compatability

Checklist:

[ ] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

In the functor example, it's not clear to me which types are allowed to have deriving bin_io.
The rule we've been following is, types like Foo.Stable.Vn.t may have bin_io, but not Foo.t. Is that true in the example?
Could you add the deriving annotations so it's obvious which types may be serialized?

The changes from this RFC have been made, and subsequent development has moved things beyond the suggestions here. There's no real need to merge this. Closing.


Evaluation part which include the comparison of the standard metrics?

Hi,
first thanks for your great work!
Is it possible to also upload your evaluation part which include the comparison of the standard metrics (region similarity J , contour accuracy F, and their average J&F) for DAVIS 2017?
That would be very helpful and thanks!
Best
Rojin

Use the official routine: https://github.com/davisvideochallenge/davis2017-evaluation

Of Course, thank You!


feat(Table): accept sort/onSortChange properties to display sorted state

Need this for MVP, figure we can have it implement more complex logic when we're not crunched for time.

:ship:

:octopus: :snowflake:


settings: Rename "user avatar" to "profile picture".

There are a couple of places this needs to be changed:

https://chat.zulip.org/#settings/your-account (section heading and buttons)
https://chat.zulip.org/#settings/your-bots (button can be "Customize profile picture")
https://chat.zulip.org/#organization/organization-profile

For this one we should just move all the logos into one section: Organization logos.
The text for the first one can be "Square logo, for white background (appears on registration and login pages)"
The second can be "Rectangular logo, for white background (appears in upper left of logged-in app)"
The third can be "Rectangular logo, for dark background (appears in upper left of logged-in app)"
As followup, we'll want to grep for avatar in templates/zerver/help and make changes there as needed.

Let's not do any work on "organization logo" stuff here until #11612 is complete.

@zulipbot claim

Quick question regarding:
As followup, we'll want to grep for avatar in templates/zerver/help and make changes there as needed.

Does that mean it should be a separate PR, or should any PR to change the UI text also update the help changes along with it?

@BenMusch it'd be great if you did that while you're at it.


eid-mw: 4.1.19 -> 4.4.1

Motivation for this change
Urgent version bump as tax season is coming and 4.1.19 is not compatible with firefox (>= 58) anymore.
eid-viewer was merged upstream with eid-mw, so it is included here now.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build eid-mw

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: eid-mw
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: eid-mw
Partial log (click to expand)
shrinking /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/libexec/beid-changepin
shrinking /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/libexec/beid-askpin
shrinking /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/lib/libeidviewer.so.0.1.0
shrinking /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/lib/libbeidpkcs11.so.0.0.0
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/lib  /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/libexec  /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/bin
patching script interpreter paths in /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1
/nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1/bin/eid-nssdb: interpreter directive changed from "/bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1...
/nix/store/ab67x283f97nv5idr0wg6asb4j53d4nx-eid-mw-4.4.1

Success on x86_64-linux (full log)
Attempted: eid-mw
Partial log (click to expand)
shrinking /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/libexec/beid-askpin
shrinking /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/libexec/beid-askaccess
shrinking /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/libexec/beid-spr-askpin
shrinking /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/bin/.eid-viewer-wrapped
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/lib  /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/libexec  /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/bin
patching script interpreter paths in /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1
/nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1/bin/eid-nssdb: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1...
/nix/store/nhnvq706dk314837z5yqy27j8z0y73ci-eid-mw-4.4.1


[Feature request] adding a monitoring system

Description
can you add a monitoring system or is it already implemented and I'm just dumb.
[Description of the bug or feature]
add in a new number in the tool just for monitoring . where we can enter a pixiv id  and from the date when we entered the number it downloads anything new of that pixiv id.
Versions
v20210421

well, it already track the downloaded image id in the db, also you can try to set checkupdatedlimit = 7 (check readme for more details).

well, it already track the downloaded image id in the db, also you can try to set checkupdatedlimit = 7 (check readme for more details).

don't you think it would be better if it was a bit automated for convenience sake . instead of putting in a bunch of member ids manually for pixivutil to download the new images. wouldn't it be better if we enter them just one time in some bookmark type feature and every time you chose the feature they would automatically download new images of the artist that you already put there once.
something like the monitoring system from imgbrd-grabber: https://github.com/Bionus/imgbrd-grabber/issues/1620
that's the only thing that i feel like this app is laking. besides that it's perfect.

instead of putting in a bunch of member ids manually for pixivutil to download the new images. wouldn't it be better if we enter them just one time in some bookmark type feature and every time you chose the feature they would automatically download new images of the artist that you already put there once.

Follow the artists on Pixiv and then smash option 8.

instead of putting in a bunch of member ids manually for pixivutil to download the new images. wouldn't it be better if we enter them just one time in some bookmark type feature and every time you chose the feature they would automatically download new images of the artist that you already put there once.

Follow the artists on Pixiv and then smash option 8.

thx . i'll give it a try

instead of putting in a bunch of member ids manually for pixivutil to download the new images. wouldn't it be better if we enter them just one time in some bookmark type feature and every time you chose the feature they would automatically download new images of the artist that you already put there once.

Follow the artists on Pixiv and then smash option 8.

Would it work with tags?


put back hero kills/map in teamfights

I'm going to try something in a PR, you guys can tell me whether or not it qualifies for this issue or is even a good idea.


[Fixes #2174] makes get_logical_operations and is_valid_routing more robust

also adds SwapNetwork.str

For good measure, I ran the test 10k times, and it always passed. (Previously, would fail at least once in a hundred runs.)


RDS conversion fails with "Unable to allocate 267. GiB for an array with shape (1169213, 30639) ..."

See #single-cell-data-wrangling.
Dataset that failed RDS conversion: s3://kuni-tmp/failing-dense-dataset.h5ad
The dataset validation was successful, but RDS conversion failed during memory allocation:

Seurat conversion failed: b'' b"Loading required package: reticulate\nLoading required package: devtools\nLoading required package: usethis\nLoading required namespace: Seurat\nError in (function (cond) : \n error in evaluating the argument 'x' in selecting a method for function 't': numpy.core._exceptions._ArrayMemoryError: Unable to allocate 267. GiB for an array with shape (1169213, 30639) and data type int64\nCalls:  ... py_to_r.numpy.ndarray -> NextMethod -> py_to_r.default -> py_ref_to_r\nExecution halted\n"

RDS conversions must fast fail  if there would be a failure, similar to the earlier Seurat failure investigation.
@ebezzi recommends:
we'd need to add a check like: if it's a dense matrix, and n_row*n_col*8 > x (where x is 20G or so), fail.

@brianraymor to review and add to the schema 4 velocity epic.


Disable calls from modules to DB / Auth for 3rd party developers

Hi,
i want to enable third party developers to extend our web app via laravel-modules.
However, i don't want them to access the raw user data, so to disallow something like
User::all()
or
DB::table('users')->query()->get()
or even
auth()->user() or Auth::user()
Is this possible using this package or do you recommend using other approaches?

Hi,
This is not in the scope of this package, probably any package as it's custom stuff.
I suggest you make your own wrapper classes around User DB etc, where you check for roles/permissions before proxying through the main class.

You're right, that's a good idea.
Do you know which would be the easiest way to, let's say, change the DB::table('users')->query()->get() method (just the get) without screwing with the laravel code managed by composer?

I didn't mean you have to change laravel's code. I meant you create your own wrapper class which proxies calls through laravel's class.
Something to look up, the decorator pattern.

Thanks, Nicolas!

I'll close this as there hasn't been a reply in a while, feel free to comment if needed.


Who can help?
No response

@rezacute, have you tried?
iroha_client_cli asset burn [OPTIONS] --account <ACCOUNT> --asset <ASSET> --quantity <QUANTITY>


Handle callback messages from preproposal contracts

Rebased #636 so linting passes.

Codecov Report
Base: 90.72% // Head: 90.67% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (c518724) compared to base (41bdd45).
Patch coverage: 50.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #638      +/-   ##
==========================================
- Coverage   90.72%   90.67%   -0.05%
==========================================
  Files          60       60
  Lines        5122     5127       +5
==========================================
+ Hits         4647     4649       +2
- Misses        475      478       +3

Impacted Files
Coverage Δ

...cts/proposal/dao-proposal-multiple/src/contract.rs
90.90% <50.00%> (-0.62%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Stock Price Changes Prediction

In this I will develop a model which will predict the prices of stock whether it will increase or decrease using stock news.
Will be using various libraries like numpy, scikit learn, matplotlib
And in algorithm will use random forrest.
And predict whether the stock price will increase or decrease.

@Niketkumardheeryan ,please assign this to me under LGM SOC.

@akash435 check issue no . #37


[REG2.067] Issue 15744 - (SIGABRT) Error: overloadset t.Bar.__ctor is aliased to a function

The immediate reason is that resolveFuncCall is not designed to work for OverloadSet (and it hadn't caused ICE fortunately until 2.066), but I think the root cause is a rejects-valid bug issue 15784.
Until we'll fix 15784 in the next major release, this workaround fix is necessary.

Auto-merge toggled on


Data centre-specific estimation when using Cloud Computing

For now, the app assume that data centres managed by Cloud providers (such as AWS, Azure or GCP) draw their power from the local power grid. For the data centres where it's not the case, it would be good to include this information in the calculator.
The efficiency of these providers is already taken into account through their respective PUE (data here), but it would be good to have more specific data at data centre level for a more accurate estimation.

Done for GCP and Azure. AWS don't make this information available...


Removed duplicate topsl.AppInit() call

Duplicate topsl.AppInit() call causes invalid terminal state when application exists. This fixes https://github.com/gdamore/govisor/issues/37

I integrated your fix, but I did change the commit comments to match my preferred style which is just to have fixes #
Nothing else changed.
Fix integrated here:  https://github.com/gdamore/govisor/commit/95ebbd0a8e075074611859d6de4b78780909c0f2


Add support for application/vnd.collection+json

Add support for content-type application/vnd.collection+json, see spec.

This has been started already, see Servant.Hateoas.ContentType.Collection.
But it seems to collide with what class Resource intends.
CollectionResource a represents [a] , so CollectionResource [a] represents [[a]].
This is bad, when rewriting [Foo] for the resource-server we get CollectionResource [Foo] but we want CollectionResource Foo.
Best would be to handle this when rewriting. But does this result in bloat?
It actually may not because we can match specialized cases in type families Resourcify and ResourcifyServer
How does this affect other parts of the procedure?
Ideally we do not have to adjust any HasResourceServer/BuildLayerLink instances at all.


ctl-plutip-test check is green with failing tests

Example?

@klntsky https://ci.staging.mlabs.city/build/10021#tabs-buildsteps

This is because exit = false in test config.

We can use runSpecT instead of runSpec' to let us inspect post-test whether any failed, and exit non-successfully. That, or have two 'modes' of running the plutip tests, one for integration that fails fast, and one for development which runs as many as possible


Trouble composing multiple files

Hello everybody,
first of all thank you for this fine piece of software. It even runs on my raspberry pi (arm8), great job. Secondly, I want to apologize, because this might be regarded as a very novice question and it (might) not be an issue at all.
I am trying to combine several images into one, but I have trouble doing so. E.g. I want to put images A, B and C on a blank alpha, my result is only C, but not A and B appearing. I tried to put together a precise example of showing what is happening:
var sharp = require('sharp');

var images = [
    __dirname + '/test.jpg', // blue square, 200x200
    __dirname + '/test.jpg',
    __dirname + '/test.jpg'
];

// create 1800x1200 transparent canvas
var canvas = sharp(null, {
    create: {
        width: 1800,
        height: 1200,
        channels: 4,
        background: '#ffffff00'
    }
});

// load images
var buffers = [];
for (i = 0; i < images.length; i++) {
    // load the image into sharp
    console.log("Loading image");
    buffers.push(sharp(images[i]).resize(50, 50).toBuffer());
}

// wait for buffers to be ready
Promise
    .all(buffers)
    .then(function (buffers) {

        // overlay the canvas with the buffers, spread them out a bit
        for (i = 0; i < buffers.length; i++) {
            sharp(buffers[i]).toFile('buffer-'+ i + '.png'); // 50x50 blue squares
            canvas = canvas.overlayWith(buffers[i], {left: i*100, top: i*100});
        }
        canvas.toFile('canvas.png'); // has only one blue square, not three on it
    }).catch(error => console.log(error));

The results
Please note that I did not manage to include the images directly. Basically, I expected that there will be three (3) blue squares on the canvas, but the resulting canvas.png has only one on it. From the position I would assume that the last canvas.overlayWith(..) was written to the canvas, overwriting the existing ones.
test.jpg - input
http://abload.de/image.php?img=buffer-0lky4n.png
Output (canvas.png)
http://abload.de/image.php?img=canvastzzrd.png
Expected output (but transparent, this was a mistake of mine):
http://abload.de/image.php?img=expected-canvasrwxf1.png
What did I do wrong here, or is just one .overlayWith supported? Thank you for your time to read up on all this.
Sebastian

Hello, did you see #728 ?

I have seen it know, and will be investigating into this direction. I got the code sample working, that was provided in #405, but I have to admit: For me, that seems like a really cumbersome way to do it. I found a suggestion while digging through the issues that a
sharp(..)
  .overlayWith(..)
  .overlayWith(..)

pipeline would be a bit more intuitive. But this is coming from someone without your javascript background, so I might be totally wrong and that solution indeed is elegant and the way to do it.
Thank you for the pointer into the right direction. Perhaps it could be mentioned in the API docs that multiple overlays are not pipe-able right now?

Just wanting to update my question (thanks for labeling it as one): I am trying to accomplish something according to the example of #405, but I cannot manage it. This is just a tad too much on javascript and the library here.
If it's not too much to ask, could you give me a pointer on how to do:

load fours images
combine them, each one below the latter
write to output?

-----------
+    1    +
-----------
+    2    +
-----------
+    3    +
-----------
+    4    +
-----------

I understood the example you were giving in #405, but I didn't manage to adapt additional processing steps (resizing and positioning) while doing so.
You may close this question if you consider this as non-related to your project, of course (which it is), I would understand that.

I have the same (noob) question. So any help would be much appreciated!

If you're able to wait for #728 then that will make this task significantly easier :)

I actually got around this as described in https://github.com/lovell/sharp/issues/573#issuecomment-302109919, but thanks for the heads-up

Thanks for the headsup, I spent my time building other code and I am coming back right now at the image processing part, so if I manage to pull something off, I will post it here, too, as an additional ressource for other users.

Here's at least part of the promised result. I am capturing images with Canon EOS digital camera, and I have plenty of time between captures and composing. Since I am running it on a Raspberry Pi, memory is quite limited, so I gave up on the idea to store each captured and resized image in a buffer (raw buffers are huge, I quickly ran out of memory), and build some kind of queue system.
So, in pseudo-code, I have something like this:
add(filename) {
   // options for the whole image
   const defaultOpts = {raw: {height: 200, width: 200, channels: 4}};

   // load background canvas as the first buffer
   if (this.buffer === null) {
     this.buffer = sharp(background).raw().toBuffer();
   }

   // I am getting width, height, left and top as meta information, just assume that they are "there"
   var newImage = sharp(filename)
   .resize(width, height)
   .rotate(180) // since my camera is upside-down, I need to do this. Space limitation in the photobooth box
   .raw()
   .toBuffer();

   // contains top and left for translation of the resized image, too
   const newImageOpts = { raw: {height: height, width: width, channels: 4}, top: top, left: left};

   Promise.all([this.buffer, newImage])
   .then( function (buffers) {
      this.buffer = sharp(buffers[0], defaultOpts).overlayWith(buffers[1], newImageOpts).raw().toBuffer();
   })
   .catch (function(reason) {
      throw reason;
   });
}

Perhaps it might help someone else getting on track.


chore(ci): updating release action

Ref https://issues.apache.org/jira/browse/INFRA-23154

Release Note
NONE

Skipping checks as this change will only affect nightly release process. :crossed_fingers:


Initialize empty proxies.json when creating app

Proxies work locally in the v2 runtime now so let's give people a good starting point.
Initialize a proxies.json along with the app with the schema and empty proxies object.
{
  "$schema": "http://json.schemastore.org/proxies",
  "proxies": {}
}

That will give them intellisense for working with proxies if they choose.

Re-opening this and moving to the next milestone. See https://github.com/Microsoft/vscode-azurefunctions/pull/472 for more info


kpt fn render|eval should support excluding resources from function input

CUJ
kpt fn render and kpt fn eval supports mechanism to target resources to apply function on.  For example:
# Apply set-labels on resources of kind Deployment and belonging to group apps
$ kpt fn eval [PKG_DIR] -i set-labals:v0.1.5 --match-group apps --match-kind Deployment

Declaratively, for example, apply set-labels on resources with group apps and kind Deployment.
# excerpts from Kptfile

...

pipeline:
  mutators:
   - image: set-labels:v0.1.5
     selectors:
       - group: apps
          kind: Deployment

Sometimes users want to exclude set of resources from function's target. For ex. apply this function on all resources except the ones with kind Kptfile or apply this label on all the deployments except with a specific name.
This will become especially important as we allow functionConfigs and Kptfile to be included in function input by default in kpt fn commands.
Proposal
Imperative workflow:
# apply set-labels to all the deployments except a given name
$ kpt fn eval [PKG_DIR] -i set-labels:v0.1.5 --match-kind Deployment --exclude-name some-name

# apply set-labels on resources belonging to apps group except kind StatefulSet
$ kpt fn eval [PKG_DIR] -i set-labels:v0.1.5 --match-group apps --exclude-kind StatefulSet

Declarative workflow:
Introduce exclude selectors.

# apply set-labels on all resources except with kind `Kptfile` or group `apps`
...
pipeline:
  mutators:
   - image: set-labels:v0.1.5
     exclude:
       - kind: Kptfile
       - group: apps

Alternatives names for exclude: except, reject
It will also be nice to have a way syntactic sugar for select or exclude all local-configs (resources with a config.kubernetes.io/local-config: "true" annotation).

I looked for some prior art in this space and found kustomize's built-in replacement transformer to be the closest.

@droot Question, when we write something like
exclude:
  - kind: Kptfile
  - group: apps

Does that mean we should reject resources that have both kind Kptfile and group apps? Or does it mean that we should reject resources that have either kind Kptfile, or group apps?
It seems like it should be the latter, and to do the former it should look like
exclude:
  - kind: Kptfile
     group: apps

Is that correct?

It's the latter. It's ORs(ANDs) very similar to how reject is implemented. It is also consistent with how selectors is implemented.

/cc @bgrant0607 @yuwenma @mengqiy @phanimarupaka

From discussion yesterday, fn eval exclusions will also be treated as an 'AND', and this should be documented with examples to prevent confusion for users.
This means that something like --exclude-name some-name --exclude-kind StatefulSet will exclude resources that have both Kind StatefulSet and name some-name.
If a user wants to exclude resources that are of either Kind StatefulSet, OR name some-name, there will be no way to do this with eval, and users will have to do it declaratively with the Kptfile pipeline.
Some related kustomize issues with similar requests:
Issue to skip PrefixTransformer for certain GVKs: https://github.com/kubernetes-sigs/kustomize/issues/519#issuecomment-527734888
KEP to skip transformations for a specific resource or resource kind: https://github.com/kubernetes/enhancements/pull/1232/files

Agree with the idea that kpt CLI should be flexible enough to provide a way to select/exclude resources. But I'm not sure if we want to add the feature on function level or even in the pipeline.mutators/validators
Some high level questions I have:

What's the right syntax for users to describe the expected hydration workflow (Kptfile specification). Writing the exclusion logic in function level or even the mutator/validator list level is non-trivial user requirements.
When we talk about idempotent, should we consider the entire mutation, like changing the function execution order should not end up as different results (this is the criteria for horizontal and resource-specific functions, if kpt pipeline breaks this rule, it would make nested packages hydration error prone)

Discussed with @droot offline, we are thinking to not support these exclusions right now, and to release the change is and collect feedback from users.
Per @droot's request, I have created an example of how a user would exclude meta resources with the current selectors functionality: https://github.com/natasha41575/kpt-exclude-kptfile
The Kptfile looks like this:
apiVersion: kpt.dev/v1
kind: Kptfile
metadata:
  name: example
pipeline:
  mutators:
    - image: gcr.io/kpt-fn/set-labels:unstable
      configPath: functionconfig.yaml
      selectors:
        - apiVersion: "batch/v1"
        - apiVersion: "apps/v1"
        - apiVersion: "v1"
        - apiVersion: "example.com/v1"

It's a bit verbose, but it doesn't look too bad to me. Of course verbosity would increase if users have more apiVersions they need to select.

For the use case of excluding meta resources, I think we need a simpler mechanism. We should not expect function or package authors to keep an exhaustive list of everything which is a meta resource.
We either need an explicit exclusion selector or for kpt to automatically add an annotation to all meta-resources.

This will become especially important as we allow functionConfigs and Kptfile to be included in function input by default in kpt fn commands. Is it ? What is the rationale behind this ? By default users expect kpt fn should only include normal resources.

Agree with @morgante on a simpler mechanism for excluding meta resources. If this exclude is specifically for meta resources like Kptfile, users should not be required to handle kptfile resource in their Kptfile .pipeline.mutators. Kptfile is required by kpt CLI and if kpt CLI decides to include this meta-resource, the CLI has the responsibility to properly handle the cases.
To exclude meta-resource with a a simpler mechanism, how about
Option #1: kpt defines a new annotation config.kubernetes.io/hydration-override: false. At the end of kpt fn eval and kpt fn render, resources with this annotation will not be saved.
Option #2: extend the existing annotation config.kubernetes.io/local-config: true, which not only skip annotated resources from kpt live apply (current behavior) but not save resources in kpt fn eval and kpt fn render. This proposal is sort of mixed the definitions but simplifies the UX (especially if the final goal is deploying KRM resources, it does not really matter whether local resource is updated or not)
One risk condition about the new annotation approach:
if users want to apply function 1 "set-annotation" to kptfile, but not function 2 "ensure-name-substring", they have to run one-off command "kpt fn eval -i set-annotation" on Kptfile with hydration-override:true and then switch hydration-override:false. So they can have both set-annotation and ensure-name-substring in their Kptfile.

Option https://github.com/GoogleContainerTools/kpt/issues/1: kpt defines a new annotation config.kubernetes.io/hydration-override: false. At the end of kpt fn eval and kpt fn render, resources with this annotation will not be saved.

I don't think we want to make such a decision globally. Some functions do want to read/write the Kptfile. So I think a config.kubernetes.io/meta-resource: true annotation would work well, then function selectors can choose to ignore it or not.

Option https://github.com/GoogleContainerTools/kpt/issues/2: extend the existing annotation config.kubernetes.io/local-config: true, which not only skip annotated resources from kpt live apply (current behavior) but not save resources in kpt fn eval and kpt fn render. This proposal is sort of mixed the definitions but simplifies the UX (especially if the final goal is deploying KRM resources, it does not really matter whether local resource is updated or not)

Local resources are useful for generator functions (including generators of generators), so we should conflate whether a resource is applied with whether functions should modify it. We definitely don't want to overload it in this way.

Re: option #1, if we are choosing between config.kubernetes.io/hydration-override: false and config.kubernetes.io/meta-resource: true, I think config.kubernetes.io/hydration-override: false is better. It is more accurate to what kpt is doing with the annotation and  easier to understand. The user may not intuitively understand what "meta resource" means, and IMO it very easy to explain that "hydration override" determines whether or not the hydration modifies the resource or not.

Local resources are useful for generator functions (including generators of generators), so we should conflate whether a resource is applied with whether functions should modify it. We definitely don't want to overload it in this way.

+1, users may have local-config resources that they want kpt to modify.

The user may not intuitively understand what "meta resource" means, and IMO it very easy to explain that "hydration override" determines whether or not the hydration modifies the resource or not.

The problem is this seems like it's making an absolute statement ("functions will not modify this resource") when really we want to indicate "this resource is a meta-resource that most functions might not want to modify." Some functions do want to modify the Kptfile and we still want to allow that.

Another issue to address is what if users want some functions in their pipeline to modify the Kptfile/meta resources, and others to not touch it? This will not be possible to control at a function level if we use an annotation.

@morgante Got it, that makes a lot of sense. Will discuss more internally and sync back.

I think my proposal was unclear. I just want kpt to automatically attach the annotation to meta-resources.
Separately, we can have "exclude" parameters in the Kptfile pipeline as this originally proposed:
pipeline:
  mutators:
   - image: set-labels:v0.1.5
     exclude:
       - annotations:
            config.kubernetes.io/meta-resource: "true"

My main concern for this new exclude.annotations is that it basically requires users to manually configure the new exclude syntax to all functions, but the meta-resources are not a typical deployable resources so this additional manual work does not add much real value to users. I propose using the reverse logic include.annotations here based on the assumptions that users won't need to configure it most of the times, and if they do, they really know what they are doing.

I propose using the reverse logic include.annotations here based on the assumptions that users won't need to configure it most of the times, and if they do, they really know what they are doing.

IIUC we already had the reverse logic previously with the include-meta-resources flag, and that we decided that we should instead include all meta resources, including the Kptfile, to kpt functions by default. If the meta resources are included by default, then naturally it seems to me that there should be an optional  mechanism to exclude them. Unless I am misunderstanding something, wouldn't doing the reverse logic be excluding the meta resources by default, and then providing an optional mechanism to include them? This seems like it would be reverting our previous decision (to include meta resources by default).
IMO we can have our own kpt functions like set-label and set-namespace exclude the Kptfile in their own function logic, since they are our own kpt functions and it doesn't make sense to apply them to the Kptfile, which can mitigate problems for users.

IMO we can have our own kpt functions like set-label and set-namespace exclude the Kptfile in their own function logic, since they are our own kpt functions and it doesn't make sense to apply them to the Kptfile, which can mitigate problems for users.

Agreed, and my proposal was that kpt automatically adds the meta-resource annotation to the Kptfile and function configs. Then any function which wants to ignore them can just look for that mutation, instead of trying to figure out all the meta-resources itself.

Note: Background for this change is in #1280 and #2184.
The kind of filtering that's needed is a per-function behavior that should be implemented as part of the function's logic. kpt fn source, sink, and render should always deal with all objects in the package.
The function SDKs need to make such filtering easy.
If we need to be able to more easily identify meta-resources (just Kptfile at this point? or also inline ConfigMaps in the Kptfile?), automatically adding an annotation seems fine, as with the other pipeline annotations.
As a transitional workaround, the exclude approach seems fine. I could also imagine it could be useful for more narrow targeting of broad functions like set-labels. The alternative right now is to put the affected resources into a subpackage with its own Kptfile, which is pretty heavyweight.

Design and implementation approved and merged. Will create a PR for documentation shortly.

Closing this issue as it is complete.
The docs PR https://github.com/GoogleContainerTools/kpt/pull/3022 should be merged at the time of the next release.


Add IPv6 preferred JVM support

What changes were proposed in this pull request?
Now loopback address is <IP_ADDRESS> always.
But it's not work for JVM that was run with -Djava.net.preferIPv6Addresses=true. It's better to pass host (that will be ::1 for IPv6) to py4j gateway creation.
How was this patch tested?
Livy with this fix is using on IPv6 machines now.

@askhatri
Can you look at the PR, please?


Add section warning against mapping all types of crime on a single hotspot map

This might be useful in a list of top 10 hotspot mapping mistakes, or something like that.

This problem currently only comes up in the final assessment because that's the first time students are asked to analyse multiple crime types at once. It may be useful to make one of the previous assessments about more than one crime type so that any issues with this can be caught earlier.

This doesn't seem to fit very well in either of the tutorials in Week 2, but I'm not sure where it should go.

This was implemented in Tutorial 5 in 2024, so the issue can be closed.


Added Arduino UltraSonic Sensor files

Have you read the Contributing Guidelines ?

[x] Yes

Description
Added an Arduino setup that makes use of an UltraSonic sensor to measure distance and represents the read distance over 3 LEDs.
fixes #528

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
PR made under GSSoC'22 contributions.

@Kushal997-das any updates about the review?

@photon149 Have a look and check any duplicate PR exits or not .