command "dotnet tool install -g mlnet" is not working

I execute the command "> dotnet tool update -g mlnet" and it produces the following output. If this is just expected to work as the page suggests then it would seem a dependency or command parameter, e.g. --version #.#.# ,  is missing from the instructions.
d:\src\repos>dotnet --list-sdks
2.1.602 [C:\Program Files\dotnet\sdk]
2.2.202 [C:\Program Files\dotnet\sdk]
3.0.100-preview3-010431 [C:\Program Files\dotnet\sdk]

d:\src\repos>dotnet tool install -g mlnet
C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\NuGet.targets(119,5): error : Unable to load the service index for source https://pkgs.dev.azure.com/myusrn/_packaging/myfeed/nuget/v3/index.json. [d:\src\temp\z0qccm5x.r1m\restore.csproj]
C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\NuGet.targets(119,5): error :   Response status code does not indicate success: 401 (Unauthorized). [d:\src\temp\z0qccm5x.r1m\restore.csproj]
The tool package could not be restored.
Tool 'mlnet' failed to install. This failure may have been caused by:

* You are attempting to install a preview release and did not use the --version option to specify the version.
* A package by this name was found, but it was not a .NET Core tool.
* The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
* You mistyped the name of the tool.

d:\src\repos>

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

ID: 4200d7af-ea16-7b93-5263-6a1ce41ecb3b
Version Independent ID: e1697ee4-9d3a-e1cc-b678-cab88f1b5f86
Content: How to install the ML.NET Command-Line Interface (CLI) tool - ML.NET
Content Source: docs/machine-learning/how-to-guides/install-ml-net-cli.md
Product: dotnet-ml
GitHub Login: @JRAlexander
Microsoft Alias: johalex

Hi, @myusrn. The prerequisites state that .NET Core 2.2 SDK is needed for this tool.  Retry it with 2.2 instead of 3.0 preview and you should be good to go. Closing as this issue is resolved. Thanks!

Thanks for details.  Are you aware of how one tells the C:\Program Files\dotnet\dotnet.exe tool install command to use their 2.2.202 sdk installation and not the vs19 installed 3.0.100-preview# sdk installation?

Try dotnet tool update -g mlnet --framework netcoreapp2.2

Thanks for those details.  Doing more testing the issue was arising not from the vs19 installed dotnet core 3.0.100-preview sdk installed.  It was a result of the 401 accessed denied arising when the dotnet tool install/update . . .  command attempted to iterate through my set of defined nuget feeds and hit the one pointing at my azure devops nuget package feed where it appears there are no cached credentials in place.  I used vs19 | tools | options | nuget pacakage manager | package sources UI to uncheck/disable that package feed and after that the dotnet tool install/update -g mlnet command to succeed with dotnet core 3.0 sdk preview installed.


example used in promo video does not work

I'm submitting a Bug report
I watched this recent MS promo video: https://www.youtube.com/watch?v=-qf2PMuOXWI
It mentioned Windows-Machine-Learning\Samples\SqueezeNetObjectDetection
I cloned the repo and tried to build and run. Building totally failed for the NC, JS, CS projects. For the CPP project all release builds failed and so did the debug x64 build. The only ones that work are debug x86 and debug AnyCPU (but I need 64 bit).
Running the demo in debug mode worked in CPU mode but failed in directX mode (but I need directX).
Pretty annoying when the most simple hello world example does not work out of the box.
:(
Environment
Windows Build Number: 18363.1016
App min and target version: Windows SDK 10.0.18362.0
OS Version (Server, IoT Core, Desktop, etc): Windows 10 Enterprise
Graphics Driver version: NVidia GForce GTX 1070  driver 27.21.5206 from 2020-08-12, updated today
Visual Studio 2019 Pro, v.16.7.2 updated today, left the project toolset at v141 as per project file in Git.

Hey @IngmarBitter , the pull request #343 should fix the CPP project. I tried x64 in debug and release mode and they are working now. Let me know if it works for you.
Thanks!


New patches

You should add the following patches for perfect box drawing and to avoid screen tearing glitches. A use case might be something like cava mpd visualizer.
https://st.suckless.org/patches/boxdraw/
https://st.suckless.org/patches/sync/

Open a working PR. People have tried to add boxdraw to this build, but I remember it not correctly functioning. I never bothered to figure it out.

You have to enable it in config.h, 3 lines change 0 to 1. That's it. I manually patched it myself in my build. Just a bit of work.

If that's the case, if I have time soon I'll try adding it myself then.
What is sync for?

Sync stops screen tearing. Not sure if you've used cava or ncmpcpp visualizations and seen tearing? Well the sync patch stops that.

Are we talking about the general screen tearing that occurs on Linux (at least xorg?). I mean that should be dealt with with system settings universally.
Or is this something specific to st? I've never seen something like this or heard complaints.

Are we talking about the general screen tearing that occurs on Linux (at least xorg?)

No. It's about the terminal tearing/flicker because it refreshes/redraws the screen before the application has completed the output - and then it has to redraw again once the remainder of the output from the application arrives. The autosync patch simply waits until no more content arrives - and then draws. See more details at the patch page (I'm the author).

Also, I saw that at the boxdraw patch you enabled both boxdraw_bold and boxdraw_braille. IMHO these should be disabled by default.
Braille because while cute, it's a bit unexpected unless you want it that way.
Bold because other terminals seem to also disable bold for boxdraw lines (e.g. VTE). I think that fonts also don't always have bold, and because application which want thicker box lines usually explicitly use heavy lines (which boxdraw supports too regardless of bold). The only place I saw bold used with boxdraw lines was with htop in tree mode (F5), and it's bold just to get gray (bold black) and not for the thickness.
FWIW, Personally I have braille enabled and bold disabled, but that's just my personal taste.

Okay. Well I guess I'd sort of want to see examples of the differences between the variables.
As for sync, I mean I've never really seen this, or at least acknowledged it, so I don't know what it's fixing: is there any particular time when this occurs and is highly noticeable/a problem?

Tearing and flicker are usually names for different aspects of the same thing. I'm sure you've seen flicker, e.g. at less or vim status line, or cursor flicker in tmux while the cursor is in one pane and there's some ongoing output at another pane, etc.
Tearing is usually more associated with unattended outputs like animation where the terminal draws partial image and then draws the remaining output. Examples of this would be any terminal audio visualizer (I tested with cava configured to 60fps, but it generally manifests in any fps), and also mpv --really-quiet --vo=tct or other applications which update the whole terminal area frequently.

I'll try to record an example shortly to show. I'm in Australia so a bit of time difference. But it's 1pm here now. I'm just giving my son lunch then I'll try and make an example.

I noticed you already got boxdraw working so thats fine. Here is an example, first video is your st without sync and the second is mine with sync applied. Notice the flicker/tear where there is an emply horizontal line across the bars now and then.
No sync: https://streamable.com/bafzbo
Sync: https://streamable.com/s785qc

I've noticed a lot of flickering in st so Sync would be very much appreciated. I have my own fork with boxdraw added but unfortunately there's no Sync for 0.8.2 so I'll have to move everything to 0.8.3 eventually.
Could anybody test whether or not Sync fixes flicker in ncmpcpp's clock mode, tremc options or calcurse when scrolling with h or l? These are the programs in which I encountered the worst flickering and tearing

there's no Sync for 0.8.2

autosync ("Part 1") should work fine with 0.8.2, and generally it should be enough.
appsync ("Part 2") is more experimental and you probably don't really need it because there are barely any applications which make use of this feature, and indeed it doesn't apply cleanly to 0.8.2 (but if you know C then you should be able to resolve the conflict yourself).

Okay. I've added autosync.

Okay. I've added autosync.

FYI, autosync was merged upstream recently as-is.


Update cas-compliance-trust.md

Added notes on AAD IP consuming MDA alerts

Learn Build status updates of commit 83c0717:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CloudAppSecurityDocs/cas-compliance-trust.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Fix for OSX Sierra bug (#39)

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is 66.66%.

@@           Coverage Diff           @@
##           master      #40   +/-   ##
=======================================
  Coverage   75.86%   75.86%
=======================================
  Files          43       43
  Lines         924      924
  Branches       45       45
=======================================
  Hits          701      701
  Misses        197      197
  Partials       26       26

Impacted Files
Coverage Δ

Source/Sockets/JMPathSocket.m
83.33% <100%> (ø)
:arrow_up:

Source/USB/USBMux/JMUSBMuxEncoder.m
69.56% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


⚠ Bofrost.com has degraded performance

In a828f98, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 5363 ms

Resolved: Bofrost.com performance has improved in 1d2cfdc after 10 minutes.


Result receiver

closes #13 #290

Coverage increased (+2.38%) to 47.93% when pulling 47f82a7501c7f3b5029f42cb7c41aab0e9d137b6 on result_receiver into f54a46092155768c49bec3848439f806b7248d58 on master.

Coverage increased (+2.38%) to 47.93% when pulling 47f82a7501c7f3b5029f42cb7c41aab0e9d137b6 on result_receiver into f54a46092155768c49bec3848439f806b7248d58 on master.


Use upstream support GHA ruby/setup-ruby

Replace retired github action actions/setup-ruby with supported replacement ruby/setup-ruby
Use built in ruby/setup-ruby bundler cache support
Remove manual install of libpq-dev https://github.com/actions/virtual-environments/pull/350
Use .ruby-version as CI version
Use .nvmrc as CI version
Use npm ci instead of install per https://docs.npmjs.com/cli/v8/commands/npm-ci

Successful run: https://github.com/Firefishy/digitalservice4germany.github.io/runs/6392624152?check_suite_focus=true (pages push fails as expected)


resolving global id highlight issue

Description
Fixing issue with pick highlight using global zone ids. The highlight extraction needs the local zone id to apply the correct highlight, but it was receiving the global id when PickByGlobalZone was used.
Type of change

[x] Bug fix
[ ] New feature
[ ] New Documentation
[ ] Other (please describe below)

How Has This Been Tested?
I ran all tests that include the pick operator, and they passed. I also added a test that specifically makes sure that the global zone highlight works correctly.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added any new baselines to the repo
[x] I have assigned reviewers (see VisIt's PR procedures for more information).

Can you add something to the 3.0.2 release notes. We still haven’t started the final builds.
From: Alister<EMAIL_ADDRESS>Sent: Friday, September 13, 2019 7:43 AM
To: visit-dav/visit<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [visit-dav/visit] resolving global id highlight issue (#3897)
Description
Fixing issue with pick highlight using global zone ids. The highlight extraction needs the local zone id to apply the correct highlight, but it was receiving the global id when PickByGlobalZone was used.
Type of change

[ ] Bug fix
[ ] New feature
[ ] New Documentation
[ ] Other (please describe below)

How Has This Been Tested?
I ran all tests that include the pick operator, and they passed. I also added a test that specifically makes sure that the global zone highlight works correctly.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have added any new baselines to the repo
[ ] I have assigned reviewers (see VisIt's PR procedureshttps://visit-sphinx-github-user-manual.readthedocs.io/en/develop/dev_manual/pr_create.html#reviewers for more information).

You can view, comment on, or merge this pull request online at:
https://github.com/visit-dav/visit/pull/3897
Commit Summary

resolving global id highlight issue

File Changes

M src/avt/Queries/Pick/avtPickByZoneQuery.Chttps://github.com/visit-dav/visit/pull/3897/files#diff-0 (6)
M src/test/tests/queries/pick.pyhttps://github.com/visit-dav/visit/pull/3897/files#diff-1 (22)
A test/baseline/queries/pick/GlobalHighlight_00.pnghttps://github.com/visit-dav/visit/pull/3897/files#diff-2 (3)

Patch Links:

https://github.com/visit-dav/visit/pull/3897.patch
https://github.com/visit-dav/visit/pull/3897.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/visit-dav/visit/pull/3897?email_source=notifications&email_token=AAING7QIZWIQR2FVR3ORN53QJORHNA5CNFSM4IWQYV72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLIEOJQ, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAING7XTRCXOMWVQRBSSRITQJORHNANCNFSM4IWQYV7Q.

@brugger1 Yeah, I can do that. I just added to do the 3.0.3 release notes, but I'll remove that and add it to 3.0.3. Sorry about that (forgot it was underway).


openedge-project.json - allow for comments via openedge-project.jsonc

Breaking this off from #104 for further research/consideration.
openedge-project.json .config

Allow for using openedge-project.jsonc instead of openedge-project.json. Most of the other VSCode config files allow for comments, and it would be really helpful for this plugin too.

Found another way to allow comments in openedge-project.json: https://github.com/vscode-abl/vscode-abl/commit/c9ab8426e836276af69e01d2b2c2532cd40cb9f4#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
No need to deal with two extensions in project. Changes have also been pushed in the language server.


Automated daily update to rustc (to nightly-2024-05-01)

Automated update to Github CI workflow rust.yml by create-pull-request GitHub action

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19195

Relevant Lines:
23090

💛  - Coveralls


Please add PlatformIO integration

I was requested to open this here.
Original issue: https://github.com/platformio/platformio-core/issues/3805
PlatformIO is a very popular build system, it would be awesome if the RP2040 and/or RPi Pico were targets.

I don't believe this is something we would do, we already use the Cortex debug extensions which work for us. Seems more like a job for the PlatformIO devs, they would be much more familiar with the process of adding a new platform to their system.

There seems to be some confusion between the PlatformIO team (@JamesH65) and the RasPI team (@ivankravets)...
PlatformIO and Pico seem like a natural fit.  I hope that this can be worked out!

I don't believe this is something we would do, we already use the Cortex debug extensions which work for us. Seems more like a job for the PlatformIO devs, they would be much more familiar with the process of adding a new platform to their system.

There seems to be some confusion between the PlatformIO team (@JamesH65) and the RasPI team (@ivankravets)...
PlatformIO and Pico seem like a natural fit.  I hope that this can be worked out!

This may not be the right place to ask about this but PlatformIO is pretty popular for programming boards like the Pico. It makes it really easy to use VSCode to write and upload C++ code to Arduino boards, so being able to use it for the Pico would be awesome!

This may not be the right place to ask about this but PlatformIO is pretty popular for programming boards like the Pico. It makes it really easy to use VSCode to write and upload C++ code to Arduino boards, so being able to use it for the Pico would be awesome!

As @JamesH65 said upthread, this isn't something we're likely to look at ourselves. We're happy to answer questions from the PlatformIO devs if they want to add support.

As @JamesH65 said upthread, this isn't something we're likely to look at ourselves. We're happy to answer questions from the PlatformIO devs if they want to add support.

Hi @aallan,
See an update at https://github.com/platformio/platformio-core/issues/3805#issuecomment-771551792
P.S: I've just sent you an email. Hope to chat soon.

P.S: I've just sent you an email. Hope to chat soon.

So @ivankravets, it's @ghollingworth, who I think you're already talking to, that is the person you need to chat to about this.

As I said upthread we're happy to support your porting effort, and if you have any issues with doing that then you can use the pico-feedback repo to communicate with our engineering team.
However we are not going to work on this ourselves.

just experiment as beginning...
https://github.com/Wiz-IO/wizio-pico


tmt tests export -h nitrate should run checks before for all selected tests first

When attempting to export 54 new tests to Nitrate, tmt fails with:
$ tmt tests ls | wc -l
54

$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

$ tmt tests export -h nitrate --create
Test case 'TC#0615155' created.
Append the nitrate test case id.
summary: /CoreOS/scap-security-guide/hardening/anaconda/C2S
components: scap-security-guide
tags: fmf-export
estimated time: 4h
automated: auto
status: CONFIRMED
arguments: PYTHONPATH=../../lib PROFILE=C2S
Structured Field:
description: Remediates VM via anaconda %addon, scans via oscap
hardware: keyvalue = HVM=1
hostrequire = memory>=4000
fmf id:
url: https://github.com/RHSecurityCompliance/contest.git
name: /hardening/anaconda/C2S
Add migration warning to the test case notes.
Append the ID c7c35b94-ce61-43d5-a784-c60730e152a1.
2 Markdown files found in the current working directory.
Manual steps couldn't be exported
Test case 'TC#0615155' successfully exported to nitrate.
Can't export due 'Uncommitted changes in hardening/anaconda/main.fmf'.
Use --ignore-git-validation on your own risk to export regardless.

It seems that the uncommited-changes check is performed for each test export separately, instead of at the beginning of the entire export operation.

Thanks for the feedback. You are right - it makes more sense to check first and only then do the export.
Good thing is that extra-nitrate is written to the disk as soon as case is created so you are not creating too many cases (as export fails with new issue each time you fix & rerun)


Update unexpected to 8.5.0 and adjust the expected output of a single…

… test.

Thanks :)

Released in v1.1.1


Vincent

ugdg updates

Pull Request Test Coverage Report for Build 920

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

Totals

Change from base Build 915:
0.0%

Covered Lines:
3183

Relevant Lines:
3876

💛  - Coveralls


Sender id varies and botmaster can't handle incoming messages

I've set two instances of botmaster-messenger listening to two different pages (two different pageTokens). I then sent one message from my personal account to each of these two pages and did a simple reply(return bot.reply(update, 'Hello world');) but got this error:
StatusCodeError: 400 - {"error":{"message":"(#100) No matching user found","type":"OAuthException","code":100,"error_subcode":2018001,"fbtrace_id":"BJFnjNlYWmT"}}
I noticed in the update obj that the sender id (that should be the same, right?) varies, and I think that it may be related to the error.
The update object of the message sent to each page:
{"sender":{"id":"1562151773797420"},"recipient":{"id":"311723625925833"},"timestamp":1495198187591,"message":{"mid":"mid.$cAAEbgvNWwbFiUgcIR1cIMG_0iWpC","seq":31635,"text":"hi"},"raw":{"id":"311723625925833","time":1495198187640,"messaging":[{"sender":{"id":"1562151773797420"},"recipient":{"id":"311723625925833"},"timestamp":1495198187591,"message":{"mid":"mid.$cAAEbgvNWwbFiUgcIR1cIMG_0iWpC","seq":31635,"text":"hi"}}]}}
{"sender":{"id":"1354592824626036"},"recipient":{"id":"1335710399797960"},"timestamp":1495198190004,"message":{"mid":"mid.$cAAS-0nNMF7BiUgcRtFcIMHJREirb","seq":31638,"text":"hey"},"raw":{"id":"1335710399797960","time":1495198190087,"messaging":[{"sender":{"id":"1354592824626036"},"recipient":{"id":"1335710399797960"},"timestamp":1495198190004,"message":{"mid":"mid.$cAAS-0nNMF7BiUgcRtFcIMHJREirb","seq":31638,"text":"hey"}}]}}
The error happens only for the second bot I add, not for the first one. If I invert the order of the addBot the one that was throwing an error works and the one that was working stops working.
I googled and found some issues ([1], [2] related to it, but it seems that it should be fixed by now. It seems that the issue was that sometimes the id came as string and sometimes as number, but it's not what's happening to me..
Any idea?

Hey, this issue should be raised on botmaster-messenger. I created an issue there referencing this one. Closing this issue.
The issue can be found here: https://github.com/botmasterai/botmaster-messenger/issues/5


Marathon & Mesos providers' GroupsAsSubDomains option broken

Currently, the GroupsAsSubDomains option returns a reverse-sorted subdomain instead of a reverse-ordered subdomain.
As an example, if the application path is /d/c/b/a, the proper subdomain should be a.b.c.d (reversed). However, with the current implementation, the subdomain returned is d.c.b.a because it always returns in reverse sorted order.

Fixed by #868


Not usable on Linux - bug or feature?

The path needs to be specified Windows way with backlashes, but there seems to be an additional problem with the end of line character resulting in the message SyntaxError: unexpected character after line continuation character.

@jsbien Thanks for your feedback. I'll run on a linux machine. I was just using on Windows. I'll review and update.

Just worked fine for me ubuntu 20.04. The filepaths were a bit weird, it couldn't handle relative paths or ~ special characters. It needed the path all the way from root.
Thanks much for making this!

@lpurdy01 Thanks! I need to figure out how to handle cross-platform file names better. Thanks for the note.


GPU cost price in calculators

https://github.com/threefoldtech/home/issues/1392
https://github.com/threefoldtech/zos/pull/1973

every node will have its own fee for the GPU so don't think it should be in the calculator


Fix XSearch

Unified of processing of Mikami command and cross search command.
Add test of Mikami command and cross search command.

Coverage increased (+2.5%) to 85.408% when pulling d0504fea0f59e1cc4eec5da67ded9c47d88cc19f on 178inaba:xsearch into 759ce4a33160acab411081d5b6e9c856cfe11f7d on mattn:master.

Coverage increased (+2.5%) to 85.408% when pulling 5e8f3ded436272734758b214b4751ce8e8d9a234 on 178inaba:xsearch into 759ce4a33160acab411081d5b6e9c856cfe11f7d on mattn:master.

:+1:  cool  :+1:


File MIME types not working

The MIME-types (contentType) of files are not read from AAS Metamodel v3 and images are therefore not displayed

I will take a look into that ;)

Problem resulting from a name change. mimeType is now called contentType. The fix will be in the next update. Thanks for pointing this out :)

I fixed the problem. Update coming next week. I also implemented a feature to display defaultThumbnails of assets. Both image files as well as asset thumbnails currently only support external links. The BaSyx AAS- and Submodel- Repository will feature dedicated endpoints for this in the future.
Here is a little sneak peek:


Licence issue

Hi,
You are saying OpenFace can be use for commercial purposes (Apache 2.0 license). But In your code you are using the 68 face landmarks descriptor from DLIB which is not matching this license. I found a statement saying this file is not for commercial use

The license for this dataset excludes commercial use and Stefanos Zafeiriou, one of the creators of the dataset, asked me to include a note here saying that the trained model therefore can't be used in a commercial product.

It seems there is a conflict here. But the 5 face landmarks descriptor can be used for commercial use.
Cheers,

I’m the real owner of this account , I’m just gonna have to close this
hacked email
On Sun, Nov 24, 2019 at 9:45 PM chamel<EMAIL_ADDRESS>wrote:

Hi,
You are saying OpenFace can be use for commercial purposes (Apache 2.0
license). But In your code you are using the 68 face landmarks descriptor
from DLIB which is not matching this license. I found a statement saying
this file is not for commercial use
https://github.com/davisking/dlib-models
The license for this dataset excludes commercial use and Stefanos
Zafeiriou, one of the creators of the dataset, asked me to include a note
here saying that the trained model therefore can't be used in a commercial
product.
It seems there is a conflict here. But the 5 face landmarks descriptor can
be used for commercial use.
Cheers,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cmusatyalab/openface/issues/426?email_source=notifications&email_token=AMYE5VUHKGF2ROFD6O5OXY3QVNJ5XA5CNFSM4JRDKGIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3WHNRA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMYE5VU3UDDBIVDGMDGA7GTQVNJ5XANCNFSM4JRDKGIA
.

I have no idea what this email is about I will be presenting this to the
police department.
On Sun, Nov 24, 2019 at 9:45 PM chamel<EMAIL_ADDRESS>wrote:

Hi,
You are saying OpenFace can be use for commercial purposes (Apache 2.0
license). But In your code you are using the 68 face landmarks descriptor
from DLIB which is not matching this license. I found a statement saying
this file is not for commercial use
https://github.com/davisking/dlib-models
The license for this dataset excludes commercial use and Stefanos
Zafeiriou, one of the creators of the dataset, asked me to include a note
here saying that the trained model therefore can't be used in a commercial
product.
It seems there is a conflict here. But the 5 face landmarks descriptor can
be used for commercial use.
Cheers,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cmusatyalab/openface/issues/426?email_source=notifications&email_token=AMYE5VUHKGF2ROFD6O5OXY3QVNJ5XA5CNFSM4JRDKGIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3WHNRA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMYE5VU3UDDBIVDGMDGA7GTQVNJ5XANCNFSM4JRDKGIA
.

Thanks for pointing this out, I just added a reference to this in the licensing section of the README -- https://github.com/cmusatyalab/openface/commit/92d61fdd53e6e2a01d0b73bc32f5db8a93271e4d

Hi,
You are saying OpenFace can be use for commercial purposes (Apache 2.0 license). But In your code you are using the 68 face landmarks descriptor from DLIB which is not matching this license. I found a statement saying this file is not for commercial use

The license for this dataset excludes commercial use and Stefanos Zafeiriou, one of the creators of the dataset, asked me to include a note here saying that the trained model therefore can't be used in a commercial product.

It seems there is a conflict here. But the 5 face landmarks descriptor can be used for commercial use.
Cheers,

Hello @corentin87 and @bamos  from the comment above and looking at the link
https://github.com/davisking/dlib-models
I understand that the dlib pretrained 68 face landmarks descriptor model can't be used to build a commercial product but 5 face landmarks descriptor model can be used (correct me if I'm wrong) If this is correct suppose someone wants to build a product using this can he/she sell it directly or needs some prior permission (written / via email etc.) Any insights / description / links regarding this will be much appreciated. Are there online tools available for verifying if some repo license permits commercial use ? Thank you in advance. Also are there any commercial products built out of the pretrained models used in openface library  OR openface lib itself


Add a  for %AsyncIteratorPrototype%

This will cause everything to autolink to it.
Also it should be added to the intrinsics table.

Also for %AsyncGeneratorFunction%


Panic on "C source files not allowed when not using cgo or SWIG"

When wharf seen like not handling c files and giving error "C source files not allowed when not using cgo or SWIG"
github.com/elastic/beats/filebeat as an example:
unable to load packages: unable to load github.com/power-devops/perfstat: C source files not allowed when not using cgo or SWIG: c_helpers.c

Also occurred hashicorp/vault v1.16.3


Active Directory authentication provider setup gets stuck if service account password field is not filled in

Rancher versions:
rancher/server: v2.0.0-beta1
rancher/agent: N/A
Docker version: (docker version,docker info preferred) 17.12.0-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred) Ubuntu 16.04.3 LTS
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) Bare-metal
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB) Single node rancher with internal DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos) N/A
Steps to Reproduce:

Set up Active Directory by filling in all the details on the authentication provider page, but leave out the password for the service account.
Click Authenticate at the bottom.

Results:
The page will get stuck and not issue any requests because the service account password required field is not filled in. However, no error is shown to notify the user of this and they need to reload the page.

Reproduces on master 04/16

Duplicate of https://github.com/rancher/rancher/issues/12538


bugfixes + add subtitles info

collapse product & player info to one line
added subtitles info
fix typos
correct video resolution info when not a number eg 'SD'
enhance video resolution transcode info

Big bug fix.

@Hellowlol can you merge this in, it fixes a number of bugs in the plexpy module.

Thanks heaps
On 9/04/2018 9:13 PM, "Hellowlol"<EMAIL_ADDRESS>wrote:
Merged #586 https://github.com/Hellowlol/HTPC-Manager/pull/586.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Hellowlol/HTPC-Manager/pull/586#event-1563364839, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABCDZfpodh8SVXbTwhuTPPfdLw2MWLktks5tmyY6gaJpZM4TGcTl
.


Adding hide() to hide the tuto showcase

Creating a method to hide the tuto showcase dynamically. This changes made based on this issue.

wow, thanks for this ;)


ISSUE-15426 increase the server response rate GET /v1/dataQuality/testCases

Increase the server response rate for endpoint GET /v1/dataQuality/testCases

Describe your changes:
Improved server response for "GET /v1/dataQuality/testCases"
on pages (/data-quality/test-cases, /table/RedshiftProd.dev.demo_dbt_jaffle.customers/profiler?activeTab=Data%20Quality)
It was 2 seconds, now it's 200-400 milliseconds.
https://sandbox.open-metadata.org/data-quality/test-cases

There is a noticeable increase here, because the table for test cases is the same.
https://sandbox.open-metadata.org/table/RedshiftProd.dev.demo_dbt_jaffle.customers/profiler?activeTab=Data Quality

Fixes

I worked on ... because ...

Type of change:

[ ] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Hello @TeddyCr
Please see the changes

@TeddyCr @pmbrull why is this call even going to PIIMasker.java?

@Alexandr-Nedomets thanks for the PR can you check the tests failures 😊

@Alexandr-Nedomets can you take a look at the failing tests?

@TeddyCr @pmbrull why is this call even going to PIIMasker.java?

I believe we'll be masking sensitive data from the test result if a test is set against a PII sensitive column @pmbrull to confirm.

@harshach @TeddyCr that's correct. We mask the test info to avoid showing any possible sensitive info

@Alexandr-Nedomets can you take a look at the failing tests?

@TeddyCr
Sorry, missed the first message.
Need to correct the test (see picture)?

@TeddyCr Sorry, missed the first message. Need to correct the test (see picture)?

this one is ok. We'll be deprecating this part of the code in the 1.4.0 release

@Alexandr-Nedomets can you run mvn spotless:apply though to fix the checkstyle please? Then we should be good.

mvn spotless:apply

@TeddyCr
run in root project and get exception

Hi @TeddyCr
I fixed code style use comand mvn spotless:apply

Done


Update selector following rich text wrapper rename

Following some BED updates the rendered markup changed.

Fixing in a different PR.


[5.0]  [Clang importer] Existentials do not conform to Hashable.

The Clang importer was importing Objective-C types such as NSSet<NSObject<SomeProto> *> * with a set of an existential type, e.g., Set<NSObject & SomeProto>. However, such existential types do not conform to the Hashable protocol, causing a crash in later stages of compilation. Detect these cases and instead import as Set<AnyHashable>.
Fixes rdar://problem/47564982.

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 2f3468fec25a98fe3fa0eb19e1f4648930b6a145

@swift-ci please test Linux


pull request for e2e test at 11/09/2016 14:45:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Rails 6.0 fixes

This fixes things with 6-0-stable branch again. The first and last commit is actually stuff that is already on master. Problem is that this alone would break the current stable Rails 6.0.2 because of an internal API change that got back-ported from 6.1. The commit in the middle fixes this.
This will cause a merge-conflict during 60-stable -> master merge. Resolution is simple: master shouldn't change 😉

btw here's my run on travis: https://travis-ci.org/dr-itz/activerecord-jdbc-adapter/builds/634347274?utm_medium=notification&utm_source=github_status
I'm pretty sure the one from this PR will fail with rvm problems in some of the jobs. I had to restart like five of the jobs for them to go through...it's very annoying with travis atm.

Changes look good to me but I'll defer to @enebo and @rdubya for merging and release.

Wow this is super weird.  I really thought I merged this 5 days ago.  I woke up and saw this PR and then I guess didn't merge it.

oh I know what happened I read you comment about how nothing should change on master and realized I would need to spend a little time on the merge and spaced it out.

@dr-itz merge completed.  Hopefully I did not merge anything from 60?


Not able to get user information in Api Controller

Hi I tried to follow this document to create a SPA that talks to server API. In the API controller I try to get the current logged in user information via
var user = await _userManager.GetUserAsync(User);
But I get null with this method. What is the proper way to get the user information from server or is it not part of the bearer token?

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

ID: 21cb7455-3305-9316-5440-bdc22947a82d
Version Independent ID: 137d4b94-7b26-3911-b22d-42c754a95fc1
Content: Introduction to authentication for Single Page Apps on ASP.NET Core
Content Source: aspnetcore/security/authentication/identity-api-authorization.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @javiercn
Microsoft Alias: scaddie

OK solved this by adding the follow line in Startup.cs
        services.Configure<IdentityOptions>(options =>
        {
            options.ClaimsIdentity.UserIdClaimType = ClaimTypes.NameIdentifier;
        });

I think the identityserver sets UserIdClaimType to "sub" which messed things us. Somewhere in the code base needs to be fixed for this to work automatically.
I will leave this open until someone helps to address this in general so that this hack is no longer needed. Thanks.

Please open an issue in the aspnet core repo for actual code issues.

You can't use the user manager APIs to retrieve user information directly in your APIs. The user you see inside your API is the result of validating and deserializing the access token sent by the SPA to the app, which is different from the user that Identity expects (which is serialized into the Identity cookie).
This is also something that you shouldn't do in your API. The access token is the piece of data that represents the credentials for the call, and you should key your decisions on information that comes from the token, and not try to get to the underlying authentication mechanism.

Closing as this is not something we plan to support.

Just so to clarify, the user id does exist in the token directly, just identity server override the options.ClaimsIdentity.UserIdClaimType configurations which resulted in that user manager cannot parse and get it correctly. And I still feel getting user id from access token is the proper thing to do. There is no identity cookie involved here as the OIDC protocol we are using is based on authorization header as I understand.
Please advise on other alternatives of getting user identities if any. Thank you.

The Claims principal in the controller action was not produced by Identity and so UserManager does not know how to work with it. You can choose to tweak how the ClaimsPrincipal gets produced to make it work with Identity, but afaik, UserManager only works with ClaimsPrincipal instances produced by Identity and does not guarantee working with other ClaimsPrincipals. Is that fair @blowdart?
@caihongxu Could you provide more detail on what you are trying to do with the user you retrieved? You are coupling your app code to your auth code, which is not something we recommend, as it will prevent you in the future from changing the auth implementation without a high cost.

Again, please open an issue in the core repo for this. It's not a docs issue.


Xposed module not working

I have tried enabling the Xposed module via Zygisk LSPosed on A11 and it doesn't seem to work. Only way I have gotten it to work is through Accessibility option.

Same here. Doesnt popup anymore when xposed Module is enabled.

Device: Xiaomi Mi5
Android version: Android 11
Here is the log.
The error in the log does not seem to occur in 1.3.1, but now occurs in 1.4 (including 1.4.1).
modules_2022-03-20T02_12_19.937.log

@telumletiferum @e0xify
Please post your device info and send a log like C0unt-zero did.
1.4.x merges a PR that adds MIUI 13 support, if you're all using MIUI it may explain it.

I'm running Arrow OS on Mi 9 Lite. From what I've seen it doesn't produce any errors like it does for @C0unt-zero, but here are the logs anyway
LSPosed_2022-03-19T20_50_54.517.zip

.

API Version
93
Injektionsschnittstelle
Zygisk
Framework Version
1.7.2 (6379)
Manager Version
1.7.2 (6379)
System Version
12 (API 31)
Gerät
Samsung SM-G988B
System ABI
arm64-v8a
OneUI 4.0 Android 12

API Version 93
Injektionsschnittstelle Zygisk
Framework Version 1.7.2 (6379)
Manager Version 1.7.2 (6379)
System Version 12 (API 31)
Gerät Samsung SM-G988B
System ABI arm64-v8a
OneUI 4.0 Android 12

OneUI is expected to not work, I don't support OEM skins unless support has been added by PR (like MIUI has)

Sorry, I will provide additional logs.
[ E/LSPosed-Bridge] java.lang.NoSuchFieldException: mDeviceProvisioned
	at java.lang.Class.getField(Class.java:1604)
	at com.kieronquinn.app.classicpowermenu.components.xposed.Xposed.hookAospSystemUI(Xposed.kt:93)
	at com.kieronquinn.app.classicpowermenu.components.xposed.Xposed.hookSystemUI(Xposed.kt:60)
	at com.kieronquinn.app.classicpowermenu.components.xposed.Xposed.handleLoadPackage(Xposed.kt:39)
	at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:34)
	at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:98)
	at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:148)
	at org.lsposed.lspd.hooker.LoadedApkGetCLHooker.afterHookedMethod(LoadedApkGetCLHooker.java:90)
	at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(XposedBridge.java:455)
	at LSPHooker_.getClassLoader(Unknown Source:8)
	at android.app.LoadedApk.getResources(LoadedApk.java:1214)
	at android.app.ContextImpl.createAppContext(ContextImpl.java:2663)
	at android.app.ContextImpl.createAppContext(ContextImpl.java:2655)
	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6602)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.lsposed.lspd.nativebridge.HookBridge.invokeOriginalMethod(Native Method)
	at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(XposedBridge.java:442)
	at LSPHooker_.handleBindApplication(Unknown Source:11)
	at android.app.ActivityThread.access$1300(ActivityThread.java:237)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:223)
	at android.app.ActivityThread.main(ActivityThread.java:7659)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:594)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

LSPosed_2022-03-22T21_18_53.937.zip

Same happens to me on Pixel 4 Android 12, using Xposed module via Zygisk LSPosed.
logcat.txt.zip

Fixed by changing the getField call to getDeclaredField.
Here's a debug-signed release build (rename to .apk): app-release-aligned-debugSigned.zip

I tried @hacker1024's build.
https://user-images.githubusercontent.com/82859690/159655144-6573b230-0fc0-457d-a520-b5c4a8a9ea1b.mp4
It works fine as in 1.3.x
No errors or crashes.

@hacker1024's debug build works like a charm. Thank you kind sir!

I've put the fix into an official build (1.4.2). Thanks @hacker1024 for the fix!

Guess there is no way to get it fixxed unless there is someone into doing in PR.
Anyway ill attach some logs. Just in case someone feels free to take a Look into it.
Guess the Samsung.kg.client is crashing (payment Services) and some Power.io issue with fatal exception
LSPosed_2022-03-24T12_37_19.117.zip

That's not related to this app. Support for OEM firmware has to be custom, logs aren't helpful here as they change too much.

Same issue MIUI 13


[EventHubs] Update async samples

Related to #21101
I've updated EventHubs samples to drop loop.run_until_complete(...)(updated to asyncio.run(...))
I did not modified those files.

client_creation_async.py
connection_to_custom_endpoint_address_async.py
sample_code_eventhub_async.py

Because I'm not sure if the behavior will be changed or not once I modified the code.
For examples,
from
loop = asyncio.get_event_loop()
loop.run_until_complete(create_producer_client())
loop.run_until_complete(create_consumer_client())

to
async def main():
    await create_producer_client()
    await create_consumer_client()

asyncio.run(main())

@sammiee5311 great, thank you! These look good to me! I'll run the tests and merge this PR once the tests pass.
Regarding your example, those two snippets are doing different things, as you mentioned. The await is non-blocking execution, so it will allow other tasks to execute while waiting, whereas the run_until_complete is blocking, so it will ensure that create_producer_client is completed before calling create_consumer_client.
It shouldn't matter much in this scenario, since it's just an example of initializing clients. However, we should keep the original behavior, so I can update those examples as needed later.
Thanks again for your contribution!

/azp run python - eventhub - tests

@swathipil thank you so much for detailed explaination ! It helps me understand very well so now I understand how await works !
No worries. Even if It is not a big contribution, thanks for your kindness !


Add custom video/audio transforms

I had to update the MediaStreamConstraints so that the users will be able to use the APIs nicely.
Resolves https://github.com/pion/mediadevices/issues/31.

Personally, I like functional options pattern rather than method chaining.
But using it looks bit complicated due to the namespace.
Any thoughts?

Yea.. I definitely agree. I don't honestly like method chaining. But, the problem with functional options though is that the users can specify non-related constraints. For example:
Video: func(c *MediaTrackConstraints) {
    c.ChannelCount = 2
}

I guess the pros and cons would be:
Functional Options:
Pros:

Definitely look cleaner on the user side
Less code on our side

Cons:

User might be confused with the options that they can set because non-related constraints are also included.

Method Chaining or Builder Pattern:
Pros and Cons are basically just the flip side of Functional Options' Pros and Cons.
So, I guess, we'll keep the MediaTrackConstraints to be:
type MediaTrackConstraints struct {
	prop.Media
	Enabled        bool
	VideoTransform video.TransformFunc
	AudioTransform audio.TransformFunc
}

And, we'll keep functional options. What do you think? Do you like the naming and where VideoTransform and AudioTransform by the way? I'm curious, because I don't really like it, but I don't have a better idea atm.

So, I guess, we'll keep the MediaTrackConstraints to be:
type MediaTrackConstraints struct {
	prop.Media
	Enabled        bool
	VideoTransform video.TransformFunc
	AudioTransform audio.TransformFunc
}

And, we'll keep functional options. What do you think?

Sounds reasonable to me.

Do you like the naming and where VideoTransform and AudioTransform by the way?

They are not actually parts of Constraints, but I also don't have good alternative.
So, it's fine for now.

Do you like the naming and where VideoTransform and AudioTransform by the way?

They are not actually parts of Constraints, but I also don't have good alternative.
So, it's fine for now.

Yea.. Definitely agree. It looks weird to be a part of Constraints

Just updated the PR.


feat: deploy all functions after bootstrap

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 12 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 57.667%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/bootstrap/bootstrap.go
0
3
0.0%

internal/functions/deploy/deploy.go
0
9
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
6378

Relevant Lines:
11060

💛  - Coveralls


Placeholder type Body is defaulting in a hanging indent

Hi,
Thanks for a great library!
I am seeing an issue whereby when I try to add text using a placeholder of type Body I am getting a default hanging indent of .95cm. You can see this in the 3rd slide of the online Master slides demo pptx.
I can't figure out a way to change or work around this. paraSpaceBefore, paraSpaceAfter and indentLevel all seem to be ignored when using placeholders. Is it possible to use a placeholder to add text without getting that hanging indent?
Thanks :)
Edit - a fiddle illustrating the point, the added text has a hanging indent.
https://jsfiddle.net/7muse9ca/

These seem to be default values assumed by powerpoint if certain attributes are not set. I opened the generated file and fixed the bad formating of the placeholder. Both, indent and hangign were set.

I saved the changed file and compared the xml sources of the generated(left) and fixed(right) file:

I was able to make a quick fix by tweaking:
	function genXmlParagraphProperties(textObj, isDefault) {
                       // code omitted....

			// OPTION: bullet
			// NOTE: OOXML uses the unicode character set for Bullets
			// EX: Unicode Character 'BULLET' (U+2022) ==> '<a:buChar char="•"/>'
			if ( typeof textObj.options.bullet === 'object' ) {
// ...
			}
			else if ( textObj.options.bullet == true ) {
// ...
			}
			else {
                               // added these lines
				paragraphPropXml += ' indent="0"';
				paragraphPropXml += ' marL="0"'
				strXmlBullet = '<a:buNone/>';
			}
// ...
		return paragraphPropXml;
	}

I could do a pull request but I haven't been able to test these changes.

Hi @gitbrent
Any update on this issue?? Any timeline with regards to the solution??

let pptx = new PptxGenJS();

pptx.defineSlideMaster({
    title: "MASTER_SLIDE",
    bkgd: "FFFFFF",
    objects: [
        {
            placeholder: {
                options: {
                    name: "title",
                    type: "title",
                    x: "5%",
                    y: "5%",
                    w: "90%",
                    h: "10%",
                    fontSize: 18,
                },
                text: "",
            },
        },
        {
            placeholder: {
                options: {
                    name: "body",
                    type: "body",
                    x: "5%",
                    y: "20%",
                    w: "90%",
                    h: "80%",
                    fontSize: 14,
                    paraSpaceBefore: 0,
                    paraSpaceAfter: 0,
                },
                text: "",
            },
        },
    ],
});

const testSlide = pptx.addSlide("MASTER_SLIDE");
testSlide.addText("Slide Title", {
    placeholder: "title",
    valign: "top",
    autofit: true,
});
testSlide.addText(
    "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",
    {
        placeholder: "body",
        autofit: true,
        valign: "top",
    }
);

pptx.writeFile("Issue589-" + getTimestamp());

Result:

Thanks @colmben
This is now fixed in master branch.

Thanks @gitbrent


feat: update footer Apr 2022

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

related Forum footer swap pr with review instructions: https://github.com/freeCodeCamp/forum-theme/pull/69
related News footer swap pr https://github.com/freeCodeCamp/cdn/pull/129

Links all look good.
Do we want to shorten this one title?

Yes, any good replacement candidates!


No response from server

I've stepped through the ReadMe tutorial and started the server, but getting no response in browser.  Note that I am running the tutorial on a Vagrant Ubuntu 16.04 VM, with port 8080 opened to my host machine.
Here's the terminal from the start server command:

From the terminal output, does anything appear to be obviously wrong?

@rgwozdz This looks like everything is in working order. We look for the Bound to localhost/<IP_ADDRESS>:8080 to see the server has started.
Did you access through static/index.html? Hitting port 8080 from the browser wouldn't produce anything, but the endpoints that the index.html page hits are where the functionality would be exposed.

Thanks Rob.  I'm trying this URL: http://<IP_ADDRESS>:8080/static/index.html
And getting this response:
"The webpage at http://<IP_ADDRESS>:8080/static/index.html might be temporarily down or it may have moved permanently to a new web address."
It's strange - I guess it could be some problem with the port forwarding or some configuration on my Vagrant VM -  but for other webservers, the configuration I am using works.  I guess I'll close the issue and assume its something on my end.

Same problem here

@mattfullerton we can discuss it in our gitter channel: https://gitter.im/geotrellis/geotrellis
though be careful with host names: https://github.com/geotrellis/geotrellis-landsat-tutorial/blob/master/src/main/scala/tutorial/Serve.scala#L42

Not sure what your develop environment is like, but for me, I was trying to connect to 8080 via port-forwarding on a virtual machine.  Had the same response once I switched over to geotrellis-chatta-demo.  What ending up working was installing NGINX on the VM and have all incoming HTTP traffic forwarded to the jetty server port.
On Feb 6, 2017, at 2:58 PM, Grisha <notifications<EMAIL_ADDRESS>wrote:
@mattfullertonhttps://github.com/mattfullerton we can discuss it in our gitter channel: https://gitter.im/geotrellis/geotrellis
though be careful with host names: https://github.com/geotrellis/geotrellis-landsat-tutorial/blob/master/src/main/scala/tutorial/Serve.scala#L42
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/geotrellis/geotrellis-landsat-tutorial/issues/5#issuecomment-277842088, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEKrKEyeZOQlH843a_LaVjQBQ5mTjlNRks5rZ6WEgaJpZM4LyG5g.


Protobuf transition overview

This issue is to collect discussion about the transition to protobuf, and to provide a high-level overview of the planned transition.

On the protobuf branch, we make the minimal possible changes to the current server in order to replace Avro. This will happen through a series of PRs. The first PR will probably be the initial chanegover for the main server code, with any problematic tests disabled via nose decorators. Subsequent follow-up PRs will then gradually reenable these test cases, or replace them if they are too Avro specific.

Once the protobuf schema has been formally accepted upstream in the schemas repository, we can then merge the protobuf branch into our mainline development branch. Mainline development will then happen on protobuf based server.

Once we are sure we can make a release based on the protobuf version that can be reliably installed by users, we begin the process of changing the codebase over from the current camelCase convention to snake_case. Once we have fully transitioned to snake_case, we can consider the conversion to protobuf complete.

Note During the transition period, we will have an odd coding convention that is a mixture of snake_case when we are interacting with the protobuf generated classes, and the existing camelCase convention for everything else. This will cause confusion, but it seems to be the lesser of a number of unpalatable evils.

Question - perhaps I am missing something, but it looks like responses are being returned as JSON, at least currently. Are there plans to support receiving protobuf messages as requests and/or sending protobuf messages as the response, I'm assuming in addition to JSON?

The initial plan is to keep  JSON on-the-wire, and to move to protobuf as the Interface Definition Language. There will be a few minor incompatibilities between the different versions of the protocol (i.e. the one defined in Avro and the one defined in Protobuf), but no more that we would see between two minor versions of the protocol in any case.
Once the dust has settled, I think that there is strong interest in adding protobuf as a second, optional encoding for messages on-the-wire.

@jeromekelleher can you provide an update on the to-dos wrt protobuf or close this issue?

Closing --- protobuf is done. The only remaining issue is the snake_case and camelCase mess, but this is something we'll just have to work at to fix over time.


Log4jXmlEvent - Fix dummy-Namespace when using IncludeScopeProperties

Resolves #5196 and fixes bug introduced with #2672

NLog v5.1.4 has been released - https://www.nuget.org/packages/NLog/5.1.4


Fastlane is still running version 2.114 instead of 2.110 after a reinstall

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
After uninstalling/reinstalling an older version of Fastlane, it still appears to be running the latest version.
Question Description
I recently updated Fastlane to version 2.114, but when I ran my ionic ios build script, it failed on the get_provisioning_profile step. It had worked fine just before I ran the update.
I uninstalled it using gem uninstall fastlane, then reinstalled it using gem install fastlane -v 2.110.0, gem list fastlane showed only version 2.110.0.
Then I ran the script again and the box in the get_provisioning_profile step still showed version 2.114.0 and the step failed with the same error.
Does anyone know how to make Fastlane use version 2.110.0, instead of the latest version?
To uninstall/reinstall Fastlane:
gem uninstall fastlane
gem install fastlane -v 2.110.0

The result of gem list fastlane:
*** LOCAL GEMS ***

commander-fastlane (4.4.6)
fastlane (2.110.0)

Expected result:
+-------------------------------------+--------------------------+
|                    Summary for sigh 2.110.0                    |
+-------------------------------------+--------------------------+

and the Fastlane script to work successfully as before.
Actual result:
An example of one of the Fastlane boxes showing v2.114:
+-------------------------------------+--------------------------+
|                    Summary for sigh 2.114.0                    |
+-------------------------------------+--------------------------+

The Fastlane error messages:
[13:47:24]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you

[13:47:25]: No certificates for filter: Certificate ID: '433NN4XZ66'

[13:47:25]: Could not find a matching code signing identity for type 'AdHoc'. It is recommended to use match to manage code signing for you, more information on https://codesigning.guide. If you don't want to do so, you can also use cert to generate a new one: https://fastlane.tools/cert

It turned out that when I deleted the gemfile in the root dir, it used the global fastlane and worked properly.


Sarima added

#131  Fixes Issue🛠

Description👨💻
Sarima Added

Type of change📄

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

How this has been tested✅

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

Pls pull the latest changes and do create a new PR @ayushrathore111


nb config events render correctly

Closes #1863

Coverage decreased (-0.01%) to 82.061% when pulling f3cf63d97f279025b886420411f9fb92140a696b on na3d:make-events-more-meaningful into b41353b4ea457712fc3b38b2521ca56a430344e2 on linode:master.

Coverage remained the same at 82.074% when pulling 78e90aa8fe6c6b89a9326075330744cfdde9c83a on na3d:make-events-more-meaningful into b41353b4ea457712fc3b38b2521ca56a430344e2 on linode:master.


Error 401

Hello, I am trying to use the docker for ASFclaim, but I am met with this error upon trying to run it:
asfclaim  | Only runs on the last 10 games
asfclaim  | Error:
asfclaim  | {
asfclaim  |   Result: { Permanent: true, StatusCode: 401 },
asfclaim  |   Message: 'Failed!',
asfclaim  |   Success: false
asfclaim  | }

I believe this is because my IPC password is too big, or because it uses special characters (*, !, ^, @, %, ...)
I'm not sure how this could be fixed (Maybe using an Authentication header instead of a query string? https://github.com/JustArchiNET/ArchiSteamFarm/wiki/IPC#authentication) but I really appreciate this project and hope somebody can look into this!

Thanks for this! Could you test if it works now?

Sorry, I have since switched to hosting ASF on a Raspberry Pi but this project does not support the ARM architecture under Docker, so I cannot test or use this project anymore


[Backport 2.x] Compress and cache cluster state during validate join request (#7321)

Backports #7321 to 2.x

Flaky test: #7592


refactor(error): remove unnecessary error return

If a function does not produce any errors, it should not return an error (except for functions defined by an interface). This will reduce the mental burden on users.
The AddDevices method was also added, on the side. (If you are concerned about this, I will move it to another PR.)

Thank you. I'll let @cfergeau decide as there might have been reasons, though he is currently on leave.

The AddDevices method was also added, on the side. (If you are concerned about this, I will move it to another PR.)

Knowing Christophe, this should have been at least a separate commit, but best to make a PR specific to this with clear description.

Waiting for repush to ok-for-test

/ok-to-test

this should have been at least a separate commit

Done

Hey @cfergeau. I agree with what you said: maintaining a consistent style is also a way to reduce cognitive load.
In this current PR, I noticed that there are only two FooNew() methods that return an error, and I’m wondering if we could also make them not return an error to maintain a consistent style.

VirtioInputNew: This method calls dev.validate(), but it actually doesn’t need to because other FooNew() methods will call dev.validate() during the ToCmdLine and FromOptions stages. So it’s pretty simple to make this method no-err.
VirtioNetNew: This method needs to call net.ParseMAC to determine whether the input mac address is correct. If we change the function signature to: VirtioNetNew(macAddress net.HardwareAddr), could we avoid having this function return an error?

as you said: "This also makes the API future-proof if one day we need to return an error". is also a reason. But for me: The optimal design for now will surely not be optimal in the future, avoid over-design. When the future returns an error, we can consider ways to improve, such as changing the function name to: FooSetup. At this stage, FooNew only does one thing, which is to create a struct instance.

as you said: "This also makes the API future-proof if one day we need to return an error". is also a reason. But for me: The optimal design for now will surely not be optimal in the future, avoid over-design. When the future returns an error, we can consider ways to improve, such as changing the function name to: FooSetup. At this stage, FooNew only does one thing, which is to create a struct instance.

For internal/private API, I agree. For external API, changing the API in incompatible ways has to be balanced with the annoyances this will cause to users.
Removing the errors mean changing https://github.com/crc-org/crc/blob/2b661eb9eb2c57676e1f18b728e8aa5c025ba360/pkg/drivers/vfkit/driver_darwin.go#L187-L196 , changing https://github.com/containers/podman/blob/01b2243e73076a0e71a667153af1b98ecbf3b2f5/pkg/machine/applehv/vfkit.go#L10-L33
And I don't know if there are other users of vfkit's config code.
If we make the change now, and have to change it back in the future to add the error, then we'll have broken our API twice, and annoyed twice vfkit go users. This is why I'm very conservative with these changes. If we don't have a choice, I'll consider it, otherwise, I'll think hard about it before making the change.
(and API changes get even harder after the module has had a v1 release, as breaking API means we have to change the module path, which causes even more churn to go programs using vfkit)

@cfergeau Okay, you convinced me. I will close this PR and create two new ones to address the following issues:

Add the AddDevices method
Improve comments

@cfergeau Okay, you convinced me. I will close this PR and create two new ones to address the following issues:
1. Add the `AddDevices` method

2. Improve comments

Sharing our different point of views made for an interesting discussion! Thanks for the 2 additional PRs :)


Create ERD from relationships in schema.yml files

For complicated table relationships, it's nice to have an ERD (i.e. schema diagram) to help understand how everything fits together.
Schema.yml files already have relationship tests built into them that show the relationship between tables, so those could be parsed to get the data needed for the "keys," which may not actually be keys in most warehouse systems.
A first implementation of this functionality might just look at the schema.yml file and get any columns listed there so that only one data source is needed. A fuller implementation would get all columns from the tables.
Other thoughts:

Integrating the descriptions that are in the schema.yml files would also be great, perhaps with a tooltip next to the table or column name
If there are multiple schema.yml files in a project, it might be nice to color or box the tables that are known to be related to each other because they're in the same yml. Also would be nice to be able to filter for things in the same yml file. I think this is the nicest way to deal with being able to look at individual layers of a project, but would like someone else to think about that too
Being able to zoom in/out and pan around like in the graph view would be a nice feature here

We're thinking about this too. dbt docs are great, but a lot of the data in there isn't for the right downstream audience. If you have business users that want to know what to query and where, having a clear ERD can be more useful than saying "go read the dbt docs".
I agree that this should just be done in the schema.yml files, probably using the ref syntax with some specific variables for PKs, FKs, etc.

We've tried a lot of solutions for this, none of which quite fit and none of which supported the schema.yml spec directly.
https://github.com/BurntSushi/erd, https://gojs.net/latest/index.html, https://pypi.org/project/ERAlchemy/, http://www.nomnoml.com/, https://dbdocs.io/
Right now, we have a functional tool that parses the schema.yml, specifically the relationships tests and columns to auto-generate an ERD

I've never worked in the dbt codebase, and there is a fair amount of work to make this something that will work generally. I'm interested in seeing this through, but would need some help

https://getdbt.slack.com/archives/C0VLNUUTZ/p1603828627482100

This is really, really cool!
Since dbt-docs is already built out of artifacts produced by dbt docs generate, namely manifest.json (which includes all tests and documentation) and catalog.json (which includes the set of all columns in the database), I think it would make sense to leverage the information available in those as inputs to the ERD.
E.g. grab the to-from components of all relationships tests in the manifest, to identify foreign keys:
jq '.nodes | .[] | select(.test_metadata.name=="relationships") | .test_metadata.kwargs' target/manifest.json

So my questions are:

Tactically, is there a reason to prefer parsing the schema.yml files directly?
@tayloramurphy It sounds like you'd want ERD components to be an additional schema.yml specification, rather than relying on unique + relationships tests to define PKs + FKs, respectively. Could you say more about your thinking there?

@jtcohen6 there is no benefit to parsing schema.yml directly. We don't have any experience working in the dbt docs code, so we just took the path of least resistance.
My preference would be to use the existing specification if possible. The column names, unique tests, and relationship tests provide the necessary metadata. If we are able to use the existing specification, then something like this would just work. Maybe we would need to add a toggle in dbt_project.yml to enable the feature, or something to that effect.
However, I can see a lot of edge cases that my initial assumptions are not good for. We stick to Kimball and star schemas pretty heavily, but what about people who do a normalized model and don't have a visually appealing start schema? What about the use case to see the entire data model in one visual?

@tayloramurphy It sounds like you'd want ERD components to be an additional schema.yml specification, rather than relying on unique + relationships tests to define PKs + FKs, respectively. Could you say more about your thinking there?

My first ideas for solutions typically lean more explicit than implicit. But if we're able to parse out relevant joins just based on testing I think it would make sense. Like @aroder mentioned there are corner cases on that.

if you have multiple unique tests for a given table would they all be parsed as primary keys?
limiting what gets drawn on an ERD would be tough
how do you define many-to-one, one-to-one, one-to-many joins?
can we limit columns appearing in the ERD tables?

Stuff like that. I think there are some clear easy wins / iterations that can happen on this which can certainly be improved over time. We're just doing things in LucidChart right now which makes me sad 😆 https://about.gitlab.com/handbook/business-ops/data-team/platform/edw/#first-iteration-in-gitlab-dwh

This is a fantastic idea and would certainly decrease the fragmentation of documentation. I think defining the explicit configuration would be preferrable, if I was to add an opinion to the mix, since you could then define the relationship style for the ERD connecting lines.
I'm wondering if using the exposures concept would be a good vehicle to start from, for this requirement. Since you are already configuring inferred relationships between a subset of objects, it would make sense to define how they are related. It would also mean you don't need to worry about the "limiting" factor straight away, since the expectation would be that you want to see all objects defined in the exposure.
With regards to limiting columns in the tables, perhaps you could have max limit of 50 columns with a collapse/expand option to hide the excess columns interactively.
Also, imagine being able to hover over the column in the ERD and seeing a tooltip of the docs description or a link to docs page.

Primary Keys. One might argue, "Well, at the least, uniqueness tests indicate the equivalent of an enforced unique index on a table, and all a Primary Key is is choosing which of the one or more unique columns present in a table is the actual PK if there are more than one. At the least we could indicate unique columns on the ERD even if we can't show a PK". Even that might be the case but the challenge is that in schema.yml files you can call out things that are not actual columns in the table for a uniqueness test (and for many things in general). E.g. "col1 || col2: or "SubStr(col1, 2, 4)". How would that be shown on the ERD and how would relationships be shown from another table to a table where one of these calculations exists as being shown as unique?

To get around this, you could create some custom schema tests in a package that are reserved for things that you want to include in the ERD. They'd be custom tests that didn't really do anything interesting, but they could serve as a hook for helping decide what to pick up. This feels like it would be a nice balance between not having to define everything twice and still getting to a more explicit definition for the ERD, to address @tayloramurphy 's comment.

I'm wondering if using the exposures concept would be a good vehicle to start from, for this requirement. Since you are already configuring inferred relationships between a subset of objects, it would make sense to define how they are related. It would also mean you don't need to worry about the "limiting" factor straight away, since the expectation would be that you want to see all objects defined in the exposure.

I really like this. We could put an ERD right on the exposure's page in docs site.

Column datatypes. We would need to interrogate INFORMATION_SCHEMA or the equivalent for these. That is doable, it just leads to another layer of complexity for the code. What if the columns defined in INFORMATION_SCHEMA don't match up to what is in the .yml files?

We have access to column datatypes in catalog.json, populated by the dbt docs generate command, and they ultimately come from information schema or show/describe queries. I think that should be the source of truth.

We wanted to know if you have any plans to release capabilities for data modeling with GUI to reverse and forward engineer DDL.

Hi we are also looking for this functionality! Would love to hear if there is a timeline on this.

Also very interested in this functionality and created this (ugly) solution that parses manifest.json in the interim: https://gist.github.com/panasenco/31d4c12f0cadce91f576a818018970a0

@jtcohen6, I'm interested in trying to go about developing the functionality here for injecting .png files into the markdown and attempting to have this be performed with the dbt docs generate command with perhaps some type of flag to indicate ERD generation.
Right now, I'm starting some initial prototyping with @aroder who has an early stage POC that generates the .png files from a schema.yml files via a short python script which ids facts and dimensions based on naming conventions of fct_ and dim_. I know this isn't the ideal for a more permanent solution for this.
WIth that, do you have recommendations on how I might get started to either add in this existing script to the dbt core system? From there, I'm happy to carry on the next phase of development that would leverage the manifest.json file like you recommended earlier up in this post.
Let me know what you think on next steps for this.

@joeyfezster I'm looking for collaborators to make this more robust. It's working for us but could use some work https://github.com/dbt-labs/dbt-docs/issues/84#issuecomment-717552239

@joeyfezster I'm looking for collaborators to make this more robust. It's working for us but could use some work #84 (comment)

@aroder we have some code (written for other purposes) that lets us load up the network file and comprehend the compiled graph. If you have the visualization side, we might be able to back it with data in the way that Jeremy suggested above. Is that the part that you're looking for help with?

I like this open source package for the R programing language:
https://krlmlr.github.io/dm/
Not sure how hard it would be to translate the dbt yml to what the dm package can pare (I don't know dbt well myself)

I would solve adding a yml for tuning the docs generation with multiple options like so

add lineage graph
add column names
add docs
add tests
etc
So I could create an erd or a full doc just changing the yaml config 😅

Hey folks, I just published first version CLI for generating ERD-as-code in DBML from manifest.json, which can be easily used together in the generating dbt docs pipeline.
https://github.com/datnguye/dbterd
Check it out!
Feel free to let me know for any questions or requests.
Cheers

unstale

Thanks @eitsupi! Perhaps not surprising given that I opened the ticket initially, but I still think having a solution built into dbt would be great.

This would be a great feature to update in dbt

This would be a fantastic addition to DBT

A solution like this built into dbt would be awesome

I would love to have this feature in dbt-docs. Will help to convince teams to move to DBT

Yes, we would really appreciate the ability to generate an ERD based on our models - what a timesaver in being able to get everyone "on the same page" without having to manually update when the data model changes.  Great idea!

This would be amazing, crossing my fingers this gets delivered eventually

Seems like there is a lot of interest here!
[A blue and black logo  Description automatically generated]
Ricky Renner
Senior Data Engineer
216-906-5178
AMEND Consulting
538 Reading Road
Cincinnati, Ohio 45202
LinkedInhttps://www.linkedin.com/company/amend/ | www.amendllc.comhttp://www.amendllc.com/

From: Michael Gray @.>
Sent: Monday, November 11, 2024 12:53 PM
To: dbt-labs/dbt-docs @.>
Cc: Ricky Renner @.>; Comment @.>
Subject: Re: [dbt-labs/dbt-docs] Create ERD from relationships in schema.yml files (#84)
This would be amazing, crossing my fingers this gets delivered eventually
—
Reply to this email directly, view it on GitHubhttps://github.com/dbt-labs/dbt-docs/issues/84#issuecomment-2468732974, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCP57XIH42RSC6O5KSKJ7T2ADVJLAVCNFSM4MIFIJMKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENBWHA3TGMRZG42A.
You are receiving this because you commented.Message ID: @.***>

Looking forward to this feature. That'd be massive!

At OpenMetadata we're introducing this feature in v1.6 🎉. Check out a live example in action: ER Diagram Demo.
✅ Automatically parses database CONSTRAINT structures
✏ Fully customizable: manually edit or create as needed!
PS: We have a native integration with dbt and we are OpenSource 🚀


 - Update mocha to version 8, migrate configs to js files

Unit tests still run fine after this upgrade
e2e does not fail anymore. However it still does not work properly.
Configs are now js files.
command option --opts was deprecated in favor of --config which now points to the new js files

Thanks a lot, I was not aware of spectron.
Rest looks great, also thanks for finding the 'spec' option, I didn't see it

I've forgotten to include the spectron upgrade to ^10.0.0 in my patch. Can you make the change and retry. It should work then.

Done


DOC: add API methods summary for NdPPoly

Added lost summary for the following API methods:

derivative
antiderivative
integrate
integrate_1d

The methods summary will be displayed in NdPPoly documentation page.

Thanks @espdev

@AtsushiSakai @pv
Thanks for review and merging


Binary file in repository

https://github.com/dutchcoders/gister/blob/master/gister
Maybe it commited by mistake?

has been fixed, thx!


Draftkings Tiers Help

Heres my code:
Pretty generic, but it cant get past 3
from pydfs_lineup_optimizer import get_optimizer, Site, Sport, CSVLineupExporter
from pydfs_lineup_optimizer.stacks import TeamStack, PositionsStack, PlayersGroup
from pydfs_lineup_optimizer import AfterEachExposureStrategy
optimizer = get_optimizer(Site.DRAFTKINGS_TIERS, Sport.FOOTBALL)
optimizer.load_players_from_csv(r"C:\Users\brand\Downloads\TiersWk3DKSalaries.csv")
lineups = optimizer.optimize(20,exposure_strategy=AfterEachExposureStrategy)
for lineup in lineups:
print(lineup)
optimizer.export(r"C:\Users\brand\Desktop\PYTHON\NFL\NFLFANDUEL.csv")
optimizer.print_statistic()
GenerateLineupException: Can't generate lineups. Following constraints are not valid: min_games

You have an error in min_games constraint, dk tiers settings have configs that at least 2 games must be used. How many games are in your csv?

10 different games to choose from.


Godmode doesn't prevent bloodloss

I know coz you get the drunk shader effect still.

the gods can bleed

God mode in general just needs re-working. E.g., it stores data in the system rather than in components. It should also block all the negative effects that are reset by the rejuvenate verb.

#14651


Nothing happens if you don't already have a file opened in the editor when creating a new file

If you launch vscode in a directory, and don't open any files, but just use cmd-alt-n to create a new file, it won't work.
If you first select an existing file, and then repeat the cmd-alt-n and try again to create the same file, it will work.
If you then delete the file you just created and close the first file you opened, you're back to not being able to create files.
I assume this has something to do with the code which determines which folder you want to create the file in, because that seems logical...

Yeah that's a bug I realized yesterday as well. It's related to a change in that I recently did. I'll try to fix it this week and push a new update :) thanks for filing the issue!

Thanks for quick reply 👍

@dkundel Any luck with this? I tried taking a look in the code but I feel I don't really understand what's going. E.g. in determineFullPath, what is the following code trying to do?
if (filePath.indexOf('/') === '/') {
  if (root) {
    deferred.resolve(path.join(root, filePath));
  } else {
    deferred.resolve(filePath);
  }
  return deferred.promise;
}

indexOf always returns an integer, so I don't think this branch is ever entered.
I think it might be simpler to just suggest the typed filename/filepath relative to:

The containing folder of the currently open file (if available)
The workspace (if available)
The user's home folder

That way the user can simply choose which one they actually want (if it's the default, they just need to hit return). Here's what the workflow looks like in each case:

With no folder or file opened
With a folder opened, but no file in the editor
With an active file in the editor

If this makes sense to you I can submit a PR.

Any news on this annoying issue?

This should be fixed now with v2.0.0 😊
Sorry for the delay!

Sorry, it does not work for me even with v2.0.0. My steps to reproduce:

My location is c:\Users<userName>\Downloads\
Execute "code.exe ." (note the spot - I am running VSCode on folder)
See VSCode background with some keymappings, press Ctrl+Alt+N
Enter "test.txt" and press ENTER button
See that nothing happens - neither window opens, nor file creates

Hi @ilog2000!
That is because the default option is that it tries to use the current file path as "root" for the file created. You can change this behavior globally by changing the setting "newfile.relativeTo": "project" which will always create the files relative to the project structure. Make sure to look also into the other options. I chose "file" as the default option because that was the behavior of the original version of the extension.

Hi @dkundel
Thank you for the tip - now I see these options in the readme file. I will try to switch to "project" and see. But I have concerns about such approach - is it really needed? My understanding, that we either have a path to the particular file (then we can extract a directory to navigate from) or we have a project directory. And it's possible to make selection automatically, w/o choosing a suitable option in settings. Am I wrong?

I'll be adding that behavior back as soon as I get around it. The reason why I introduced the other configuration is that there were other issues where people asked if the path could be an absolute path, if it could be relative to the project, if it could be relative to the current file and many more. So I tried to make everyone happy by offering the configuration. As part of that the fallback logic for "file" kinda dropped out again without me realizing it.

Alright I published a new minor version that should fix this issue. Let me know if you hit any more issues :)

Thank you for this quick update. Unfortunately, it still doesn't work for me - neither with "file", nor with "project"/"root" (I was overriding only "newFile.relativeTo"). I tried to create "test.txt", then ".\test.txt", then "temp\test.txt", then ".\temp\test.txt" - nothing happened when all previously edited files are closed. I also re-installed addon several times.

This is really odd. Which version of VS Code do you have installed? It works flawlessly for me. Can you very that it's really using the correct path by adding in your settings: "newFile.showFullPath": true to make the whole path visible. Maybe there is a Windows problem?

Oh, seems I finally found it. That "newFile.showFullPath": true was the initial setting. When I changed it to false, all started working as I expected. So, in my previous tests I was getting absolute path after pressing Ctrl+Alt+N, then I was replacing it with relative path, and there was no window created.
Thank you for help.

Ah okay. Yeah another person had the same issue. It's hard to cater to all requests people have. Glad it works now though!


Popper.js does not work in Bootstrap

Any element requiring Popper.js functionality like dropdowns is broken. To reproduce, simply create a new svelte app, use the Bootstrap add, and paste this snippet in +page.svelte:

  <button
    class="btn btn-secondary dropdown-toggle"
    type="button"
    data-bs-toggle="dropdown"
    aria-expanded="false"
  >
    Dropdown button
  </button>

Action

Another action

Something else here

Clicking in the dropdown does not show any menus.

Hey @EduMenges
thanks for reporting this.
I'm not fully comfortable with bootstrap so please help me if I jump from to the wrong conclusions or ask not so good questions!
First of all I would like to know, how you jumped to the conclusion that this is a problem with popper.js.
The only thing I can currently imagine, is that you have read the following in the adders readme:

The @popperjs/core package is installed to satisfy bootstrap's peer dependency on it. You can safely ignore it, or uninstall it if you can do so without introducing package manager errors.
But from my understanding this lib was only added, to satisfy all npm install dependencies.

After a lot of trying around, I can confirm this bug. As far as my understanding goes the easiest way to make this work is by modifying the +layout.svelte like this:

<slot />

Does this work for you? Do you have a better implementation that works?

@manuel3108 Your solution works for me, this issue can be closed from in my point of view.

@EduMenges Thanks for the confirmation. I will leave this open until this is properly implemented into the adder.
As you mentioned above, the above behaviour causes confusion and does not seem to be entirely correct.

@manuel3108 Your solution also works to open the mobile nav. However, it does not collapse after clicking. https://omundy.github.io/givememydata/

Hey! Did you already change anything @omundy ?
Because for me it's working on my phone and in the chrome mobile view on my desktop.

That's odd because the nav stays open on desktop and my phone for me (both Chrome incognito). I haven't changed anything with the nav.

I've had issues getting the JavaScript part of Bootstrap to work in SvelteKit as well.
Using svelte-add to add Bootstrap and then changing +layout.svelte as shown by @manuel3108 in this comment above indeed seems to work.
I've created a SvelteKit REPL with a working Bootstrap dropdown. I created this REPL using the files I get when I run npm create @svelte-add/kit@latest my-new-svelte-kit-app -- --with bootstrap, changing +layout.svelte as shown in the comment above and copying the code for the first Bootstrap dropdown example to +page.svelte.

I upgraded the REPL from my previous comment with examples of all Bootstrap components that require JavaScript:

New REPL with examples of all Bootstrap JS components.

The only two components that I can't get to work are Toasts and Tooltips/Popovers (as shown of the bottom of the new REPL).
@manuel3108 (or anyone else) can you get those to work?

@siccovansas Thanks for your work!
You were 99% there! The last clue is to use this dynamic import statement:
const bootstrap = await import("bootstrap");

instead of just
await import("bootstrap")

(I have updated my comment above, including the last details you found out!)

@manuel3108 (or anyone else) can you get those to work?

@siccovansas  The Navbar collapse does not work on Chrome desktop when clicking a link.

Thanks @manuel3108! I added const bootstrap = await import("bootstrap"); and indeed all Bootstrap JS components now work :fireworks:! I've updated the REPL.
Can this code be added to the Bootstrap adder or are there still things (I can help) to test?
@omundy, I just tested Navbar collapse in Chromium (on Ubuntu) and I can't see anything wrong with it. Can you describe your issue more precisely? Which exact link do you click and what doesn't work then?

This is supported by svelte-adds successor svelte-compose
Bootstrap composer


Support IGNORE NULLS for FIRST/LAST window function

Which issue does this PR close?

Closes #.
Related https://github.com/apache/arrow-datafusion/issues/9055
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @huaxingao. I'll review this in few days.

Thank you all very much for helping me with this PR!


Update access-policies' README

…mall alphabets.
Referring this doc, I worked on creating a permission policy. The permission policy wouldn't get created because of the caps for the keys in Json format. I was able to successfully create a permission policy by removing the caps letters.
This is the default pull request template. You can customize it by adding a pull_request_template.md at the root of your repo or inside the .github folder.
Jira Ticket
Include a link to your Jira Ticket
Example: JIRAISS-1234
Demo
Please add a recording of the feature/bug fix in work. if you added new routes, the recording should show the request and response for each new/changed route
Checklist:

[x] I have filled relevant self assessment (NodeJS, Frontend, Backend)
[x] I have run ESlint on my changes and fixed all warnings and errors (NodeJS & Frontend Services)
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have validated all the requirements in the Jira task were answered
[x] I have all neccessary approvals for the design/mini design of this task
[x] I have approved the API changes and granular permission patterns (documentation subtask) (For public services only)

lowercase


Fully Sharded Training clip_grad_norm_

🚀 Feature
FSDP does not supprot the gradient_clip_val setting in Trainer

Motivation

Pitch

Alternatives

Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

hey!
are you getting any errors when you are specifying it?

when specifying it, cause the error: pytorch_lightning.utilities.exceptions.MisconfigurationException: gradient_clip_algorithm='norm' is currently not supported for FullyShardedNativeMixedPrecisionPlugin

A fix around this is to pass this in your LightningModule:
...
    def configure_gradient_clipping(
            self,
            optimizer,
            optimizer_idx: int,
            gradient_clip_val: Optional[Union[int, float]] = None,
            gradient_clip_algorithm: Optional[str] = None,
    ):
        assert gradient_clip_algorithm in ('norm', None), gradient_clip_algorithm
        self.model.clip_grad_norm_(gradient_clip_val)

But we'll need more context about how your code is structured.
Fully Sharded training requires that you wrap your model (it doesn't wrap it for you). As a result, only you know the reference to call the clip_grad_norm_ function for your model. You can see an example of this here: https://github.com/SeanNaren/SmallScience/blob/fsdp/train.py#L235-L243