AlexaPi on Win7 desktop?

Would it be possible to run AlexaPi on Win7 desktop?
that would be epic!

Not this version, because windows doesn't support all the libraries involved in making this. At some point some will make Alexa for Windows, but it won't be coded in python.

I have a version written in .Net, but it's not been upgraded to the new API yet...

Not easy to get this up & running on Win7 mainly due to the audio limitations and also the reliance on external GPIO buttons for control.
I have built a browser based version though which is using similar code to version 1.0, you can use it for free at https://alexaweb.herokuapp.com or download and run your own from http://github.com/sammachin/alexaweb

My version uses an on screen button, so mouse required.  Runs fine using VLC on Windows.


Code Formatting: Whitespace Before Open Brace

Issue Description
I am experiencing a problem with... "Code Formatting: Whitespace Before Open Brace" is creating a space between a parenthesis and the open brace.
Attached Logs
Follow the instructions in the README about
capturing and sending logs.
Environment Information
Visual Studio Code

Name
Version

Operating System
Windows_NT x64 10.0.19041

VSCode
1.46.0

PowerShell Extension Version
2020.6.0

PowerShell Information

Name
Value

PSVersion
5.1.19041.1

PSEdition
Desktop

PSCompatibleVersions
1.0 2.0 3.0 4.0 5.0 5.1.19041.1

BuildVersion
10.0.19041.1

CLRVersion
4.0.30319.42000

WSManStackVersion
3.0

PSRemotingProtocolVersion
2.3

SerializationVersion
<IP_ADDRESS>

Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)

Extension
Author
Version

azure-account
ms-vscode
0.8.11

bracket-pair-colorizer-2
CoenraadS
0.1.4

code-settings-sync
Shan
3.4.3

code-spell-checker
streetsidesoftware
1.9.0

gistfs
vsls-contrib
0.1.1

github-markdown-preview
bierner
0.0.2

gitlens
eamodio
10.2.2

markdown-all-in-one
yzhang
3.0.0

markdown-checkbox
bierner
0.1.3

markdown-emoji
bierner
0.0.9

markdown-preview-github-styles
bierner
0.1.6

mssql
ms-mssql
1.9.0

powershell
ms-vscode
2020.6.0

project-manager
alefragnani
11.0.1

rainbow-csv
mechatroner
1.7.0

remote-containers
ms-vscode-remote
0.122.1

remote-ssh
ms-vscode-remote
0.51.0

remote-wsl
ms-vscode-remote
0.44.3

vscode-docker
ms-azuretools
1.3.0

vscode-markdownlint
DavidAnson
0.36.0

vscode-yaml
redhat
0.8.0

@dsolodow Can you provide more details please?
Given the following snippet
if($foo){
    'hello'
}

The powershell.codeFormatting.whitespaceBeforeOpenBrace setting would make it insert a  space before the open brace if the setting is set to true
if($foo) {
    'hello'
}

The powershell.codeFormatting.whitespaceBeforeOpenParen setting would make it insert a space before the open parenthesis if the setting is set to true
if ($foo){
    'hello'
}

If that is not the case for you please state that or your specific problem and the settings you use.

Sure!
    [ValidateScript({Test-Path -Path $PSItem})]

If powershell.codeFormatting.whitespaceBeforeOpenBrace is true, it shows as:
    [ValidateScript( {Test-Path -Path $PSItem})]

I probably should have phrased my report better; it does as the setting name suggests insert whitespace before the open brace. However, the info with the setting says "Adds a space between a keyword and its associated scriptblock expression" and a parentheses isn't a keyword.
So perhaps this is better described as a mismatch between the behavior indicated by the setting description and the actual behavior.

Duplicate of #1468


Deprecated method used in README.md

RequestBody.Companion.create(json, JSON); is deprecated but it is used in the example POST request in the README.md:
public static final MediaType JSON = MediaType.get("application/json; charset=utf-8");

OkHttpClient client = new OkHttpClient();

String post(String url, String json) throws IOException {
  RequestBody body = RequestBody.create(JSON, json);
  Request request = new Request.Builder()
      .url(url)
      .post(body)
      .build();
  try (Response response = client.newCall(request).execute()) {
    return response.body().string();
  }
}

I have tried everything from here https://stackoverflow.com/questions/57100451/okhttp3-requestbody-createcontenttype-content-deprecated but without success. I can not find working solution for JAVA 16 Only the deprecated method works for me.
I'm using okhttp client with maven like this:
<dependency>
	<groupId>com.squareup.okhttp3</groupId>
	<artifactId>okhttp</artifactId>
	<version>4.9.1</version>
</dependency>

That method is not deprecated, the form with swapped parameter order is. See this edit to the post example

For kotlin, it actually directs to
    val rb = "{}".toRequestBody("application/json".toMediaTypeOrNull())

This solution is proposed in the stackoverflow question that I have sent above and as I said I have tried every solution from there and nothing works. Try to execute this code with JAVA 16 (openjdk-16). I get the following exception:
java.lang.NoSuchMethodError: 'okhttp3.RequestBody okhttp3.RequestBody.create(java.lang.String, okhttp3.MediaType)'

You must be using an old version in your classpath.  Check the resolved dependencies in your build.

Yes you are correct. I'm using spring with spring boot parent pom and the version of the okhttp dependecy was getting overwritten. However the README.md still uses the deprecated version I will create pull request to replace RequestBody.create(JSON, json) with RequestBody.create(json, JSON). Thanks :)


QR Code functionality for Android

Not sure if this should go in an issue or if there is a page for feature request inquiries, but do you have native Android QR support or do you use API's to accomplish this task?
Is there Android QR support or a plan for this  (couldn't see it in the code, but that might just be me)?

There's a QR code scanner, here's how it's used: https://github.com/rawtxapp/rawtxapp/blob/ba4e23499f22beadec04acd66e266c6d9848c8fa/NativeRtxModule.js#L71. It is implemented using Java on Android and objC on iOS.


Monitor Overlay integration

This is the first plugin integration to GDShell. If you find any problems or have any suggestions, open up a new issue!
If no issues are discovered, this will be included in 1.0.dev2
All the code and rights to Monitor Overlay belong to @HungryProton

Good enough for now. Will be merged before next release

Is the next release soon?

Is the next release soon?

Currently I have a lot of work at uni, so nothing groundbreaking. Maybe in a week?


Adding include block and not providing name breaks workspace.

The include block has been temporarily removed from v1, and when it is added this problem should be avoided.


feat: multiple language localization added

#9
->Multiple Language Support feature included.
->Added additional languages like hindi
->settings ui updated to choose language

The language is reset when the user changes their language and opens the app.

@TangoBeee
Persistency for language fixed.
Now if user reopens app language remains same as  earlier


session_0

done with session 0 and 1 but I am unable to upload hello_world project ,,its been a day since I am trying to do that.
@abhishekkumar2718  can you please help me

Hi,
its seems like you have not executed the command

cp page_controller_test.rb hello_world/test/controllers

once you have done this simply add this to your vcs

git add hello_world/test/controllers/page_controller_test.rb

followed by commit and push.
Also can you push session_1 to a seperate branch.

git checkout -b sravanireddy_session_1
git add session_1/*

Hi,
its seems like you have not executed the command

cp page_controller_test.rb hello_world/test/controllers

once you have done this simply add this to your vcs

git add hello_world/test/controllers/page_controller_test.rb

followed by commit and push.
Also can you push session_1 to a seperate branch.

git checkout -b sravanireddy_session_1
git add session_1/*

Hey, you don't need to push session 1's code for this pull request. Don't mind the failing checks.
The easiest way to upload them would be:
git checkout -b session_1_sravani
git add session_1/hello_world
git commit -m 'Solution for Session 1'
git push --set-upstream origin session_1_sravani

Hey, you don't need to push session 1's code for this pull request. Don't mind the failing checks.
The easiest way to upload them would be:
git checkout -b session_1_sravani
git add session_1/hello_world
git commit -m 'Solution for Session 1'
git push --set-upstream origin session_1_sravani

error: The following untracked working tree files would be overwritten by checkout:
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/.gitignore
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/README.md
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/page_controller_test.rb
Please move or remove them before you switch branches.
Aborting
@abhishekkumar2718  This is the error im getting,eventhough I have removed them

error: The following untracked working tree files would be overwritten by checkout:
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/.gitignore
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/README.md
Desktop/IRIS-RoR-Bootcamp-2020-main/session_1/page_controller_test.rb
Please move or remove them before you switch branches.
Aborting
@abhishekkumar2718  This is the error im getting,eventhough I have removed them

error: failed to push some refs to 'https://github.com/sravanireddy1102/IRIS-RoR-Bootcamp-2020'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

error: failed to push some refs to 'https://github.com/sravanireddy1102/IRIS-RoR-Bootcamp-2020'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Closed because of a more recent PR: #47

Closed because of a more recent PR: #47


Redirects on /name@latest/?meta not working as expected

Recently, I think within the last 24 hours, the behavior of redirects on @latest/?meta changed. It now seems to redirect to @x.x.x/?meta=, and the extra = character is causing the server to return a HTML directory listing instead of JSON.
Here's a few couple examples:
https://unpkg.com/vue@latest/?meta -> https://unpkg.com/vue@2.5.22/?meta=
https://unpkg.com/react@latest/?meta -> https://unpkg.com/react@16.7.0/?meta=

Previously, these redirects didn't include the final = character, and returned JSON as expected.
I've had a look through recent commits to see if I could put together a fix as a PR, but couldn't find any code changes that would be responsible.

Seems to be working now. Thanks!


Match fetch quality check

My b if this is wrong. Just trying to learn out here.

Nahh looks great and cleans up my sloppy counting variable! Thank you for contributing I appreciate it a ton!


feat(quantic): create-and-promote-quantic-package-with-github-actions

Related Issue
SFINT-3906
Changes Proposed
Create workflow for automatically creating and promoting salesforce package for Quantic with GitHub Actions.
It is meant to create the package (trigger manually and once every day), then fetch the creation status in a loop until Status==Success. On success, it should first create the create-package-result.json  to display details, and then promote the package if specified by the shouldPromote workflow input.

@fbeaupreCoveo Regarding what you say here:

It is meant to create the package (trigger manually and once every day)

I'd suggest to trigger the workflow manually, and when pushing to master. I don't think we want to generate a new package systematically every day.

@lbergeron, triggers manually and on pushes to master were initially what we set out to do. But the org has a daily limit of 6 package version creations. The concern then is that on some days we might quickly reach that limit if the workflow is triggered on pushes to master.
There is the option of creating packages without validation, those creations have a daily limit of 200 instead of 6, but I am not sure what the --skipvalidation parameter does. Maybe you do, or someone else does, @lathanlb, @tedre191 , @erocheleau ?

@lbergeron, triggers manually and on pushes to master were initially what we set out to do. But the org has a daily limit of 6 package version creations. The concern then is that on some days we might quickly reach that limit if the workflow is triggered on pushes to master.
There is the option of creating packages without validation, those creations have a daily limit of 200 instead of 6, but I am not sure if the  --skipvalidation parameter in  sfdx force:package:version:create ... --skipvalidation would do more harm than good. Maybe you do, or someone else does, @lathanlb, @tedre191 , @erocheleau ?

The trouble with the --skipvalidation option is that versions created like that cannot be promoted to published status so it wouldn't work for this script. See here
So I think a daily build on condition of changes having been pushed to master is what we should go for. What do you guys think?

That sounds good to me, I just pushed a commit with changes that I think will work in triggering the workflow daily only when changes have been made. Let me know if you guys think that's better

@lbergeron, triggers manually and on pushes to master were initially what we set out to do. But the org has a daily limit of 6 package version creations. The concern then is that on some days we might quickly reach that limit if the workflow is triggered on pushes to master.
There is the option of creating packages without validation, those creations have a daily limit of 200 instead of 6, but I am not sure if the  --skipvalidation parameter in  sfdx force:package:version:create ... --skipvalidation would do more harm than good. Maybe you do, or someone else does, @lathanlb, @tedre191 , @erocheleau ?

We can submit a partner request in order to increase those limits I believe if necessary.

Look at this for inspiration: https://gitlab.com/etienne.rocheleau/coveo-demo-kit/-/blob/master/.gitlab-ci.yml
it's a bit different, using jq a CLI tool to parse JSON so it parses the output of the commands in json format to read some information from the output

Excited to try a run of this thing!

and a little scared 🙃


Fix limit setting and add ServerImp tests (RIPD-1463,1458):

Add more test coverage for ServerHandlerImp.cpp. Ensure limit parameter
is propagated from parsed object to in-memory config.
Release Notes
This fixes a bug whereby the limit parameter on a port configuration was
ignored.

Codecov Report

Merging #2097 into develop will increase coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           develop   #2097      +/-   ##
==========================================
+ Coverage    68.84%   69.1%   +0.26%
==========================================
  Files          684     684
  Lines        50367   50368       +1
==========================================
+ Hits         34674   34809     +135
+ Misses       15693   15559     -134

Impacted Files
Coverage Δ

src/ripple/rpc/impl/ServerHandlerImp.cpp
94.65% <100%> (+18.06%)
:arrow_up:

src/ripple/beast/asio/io_latency_probe.h
97.01% <0%> (-1.5%)
:arrow_down:

src/ripple/server/impl/BaseWSPeer.h
67.5% <0%> (-0.63%)
:arrow_down:

src/ripple/core/impl/JobQueue.cpp
86.17% <0%> (ø)
:arrow_up:

src/ripple/app/main/Application.cpp
61.81% <0%> (+0.87%)
:arrow_up:

src/ripple/app/ledger/impl/LedgerMaster.cpp
45.06% <0%> (+1.02%)
:arrow_up:

src/ripple/basics/impl/BasicConfig.cpp
87.09% <0%> (+1.61%)
:arrow_up:

src/ripple/server/impl/JSONRPCUtil.cpp
75% <0%> (+2.77%)
:arrow_up:

src/ripple/server/impl/Port.cpp
68.9% <0%> (+5.04%)
:arrow_up:

src/ripple/server/impl/PlainHTTPPeer.h
92.3% <0%> (+5.12%)
:arrow_up:

... and 4 more

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 1dbc5a5...117cf1d. Read the comment docs.

@bachase and @ximinez - I would appreciate your review of this latest commit: https://github.com/ripple/rippled/pull/2097/commits/ff13bd032c9187cf68ffdd3a02b1756fdbf6deda
(resolves the issues with cout for validation).

In 0.80.0-b4


Add example html2pdf

Please help me review PR. Thanks!

Hi @chuongtrh looks good! Thanks for the contribution, but we already have a pdf example. https://github.com/checkly/puppeteer-examples/blob/master/1. basics/pdf.js

@tnolet Got it!
But it is another way to create pdf from static HTML. I think it is different

Correct, can you add it to the existing example so that the example creates two PDF's?

@tnolet yes, I create a new PR #10. Can you check it again? Thanks!


Upgrade version of dependency to selenium-server

What problem does this feature solve?
Currently, the version of the dependency to selenium-server is ^2.53.1 as defined in package.json. Could you upgrade it to 3.x.x? I am asking because that dependency causes a version conflict in our application and breaks our tests.
What does the proposed API look like?
The Api of vue would stay the same.

selenium is a devDependency, our version cannot affect yours


coursier: 1.0.1 -> 1.1.0-M10

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I can never decide whether we want the milestones or not :) We should be OK...


discrete_uniform broken by autograd 1.1.3

Hi, thanks for the interesting library!
I was playing with the German Tank Problem example, and initially had trouble getting it to work - it would throw "TypeError: data type not understood" while computing the logp.
This turns out to only be a problem when using autograd 1.1.3 - the previous version 1.1.2 works fine.  It happens because autograd now wraps numpy.int_ as a new function, which breaks the integral type check in discrete_uniform: if x.dtype != np.int_: because it is not checking against the real np.int_.
Currently it appears that discrete_uniform is only used by the tank example.
I am inclined to think that if autograd is going to wrap np.int_ then it should also make it work transparently in the numpy type hierarchy, but I don't know enough about numpy internals to know how that might be done.
A possible workaround is to replace the check with if x.dtype.kind in "iu":.  I guess another is to use the unwrapped numpy to get access to numpy.int_, although it might be confusing to have two references to numpy which are not safely interchangeable.

Autograd dev here. Great catch and diagnosis. I agree that this is really an autograd bug. Can you open an issue on our issue tracker?
We wrapped np.int_ in a new function to fix #71. One fix for this issue would be to wrap it instead in a class that also overrides __eq__. That would fix the dtype check here (though something like if x.dtype is np.int_ would remain broken). Let me know if you have thoughts on that solution. Another fix would be to undo the commit that fixed our #71, since it was kind of an edge case.
(Tangentially, autograd also breaks some subclass checks like isinstance(x, tuple) and isinstance(x, np.ndarray) because TupleNode doesn't subclass tuple due to its use of __slots__ and ArrayNode doesn't subclass np.ndarray.)

I think the autograd commit that closed autograd #81 should fix this problem. @gbarta, can you check and update either here or in the autograd tracker?


Add topKWeighted aggregate function

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Category (leave one):

New Feature

Short description (up to few sentences):
Add topKWeighed aggregate function by adding options to classes of topK function.

It doesn't work for generic types:
SELECT topKWeighted(toString(number), number) FROM numbers(10)

Merged.


About model checkpoint

Hello,
Thank you for your hard work.
I am new to Tensorflow, so I am writing to ask for your help about check point file.
In the bash file, you mention about:
"--finetune=/tmp3/first350/TensorFlow/Logs/model.ckpt-1000"
Could you please guide me how to get the model.ckpt?
Thank you so much for your help.

Hi, the checkpoint should be save automatically in your log_dir, you can refer to model.py line 350 for specify log_dir, line 468 for saving ckpt file

Hi,
I got it. Thank you so much for your time.


fix fix priority queue order in memtable memory limiter

Proposed changes
#41018 used priority queue when selecting memtables to flush.
But the cmp function is wrong and the order is reversed.
This PR fixes the cmp function to make larger memtables come first.

run buildall


The following integrations and platforms could not be set up:  hahm.climate

After installing last release 0.36.0 on core-2022.2.9, supervisor-2022.01.1 and Home Assistant OS 7.4 receiving this log entry:
2022-02-24 17:57:37 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform hahm.climate: Platform not found (cannot import name 'HM_PRESET_MODE_PREFIX' from 'hahomematic.devices.climate' (/usr/local/lib/python3.9/site-packages/hahomematic/devices/climate.py)).
All climate entities are dead:

I know, thats why i removed the BETA release shortly after release.
Just rollback to a non beta.

dont know how to do this :-(

In HACS:

click on "erneut herunterladen".
Disable BETA.
select a version listed

thx, found it.
All is working again.
Always learning something new :-)


How to update bindings programmatically

I create custom bindings:
    public class TextExtension : MarkupExtension

This is used to show a string by ID. How can I force the UI to update the values when there are new texts available?

I don't believe Winui supports custom markup extensions. @fabiant3 or @MikeHillberg could confirm.

Great timing, thanks @StephenLPeters . Adding @alwu-msft  to comment.

@StephenLPeters: We definitely support custom markup extensions. :)
@mc0re: You'll want your markup extension to return a Binding object that it creates in code-behind. Set as the Binding object's Source and Path properties to point to the property on the object providing the updated string. That should do what you want (i.e. allow updated values to flow from the source string to the target property). If this is for a WinUI 3 app and you can wait for Preview 3 to be released, we're adding IXamlServiceProvider which will give you access to the object/property that the markup extension is being set on via the IProvideValueTarget interface and allow you to store/recall the target whenever it's time to update the displayed text; this is an alternative to constructing a Binding object.

Thanks, works like a charm.


Fix paths for npm publish

Coverage remained the same at 100.0% when pulling 8a06e0837a7e66da76ab07f270da0673f0462686 on next into d560449bd9bfd38c82d34d9a9c4dd4266e51bf6b on main.


python310Packages.types-pyyaml: 6.0.8 -> 6.0.9

Description of changes
Update to latest upstream release 6.0.9

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 181209 run on x86_64-linux 1

3 packages built:

gphotos-sync
python310Packages.types-pyyaml
python39Packages.types-pyyaml


[Bug]:  After Configuring the GitHub from admin setting the GitHub login fails for the first time

Is there an existing issue for this?

[X] I have searched the existing issues

Description
After Configuring the GitHub from the admin setting the GitHub login fails for the first time also the same issue happens for google login too

Steps To Reproduce
Scenario 1:

Go to Admin setting
Add a Github Auth
Now open a incognito window
Open localhost
Try to login with Github auth
The internal server error is displayed on UI
Refresh the page The user will be logged in
Here the user cant see the Default created workpsace

Scenario 2:

Signout from the instance
Now login again with Github
Now the user will be logged in without any error

Public Sample App
No response
Version
release

Verified in release-ee and found to be fixed.


Wrong value of this passed to module

I'm using webfontloader via WebPack CommonJS module. Webpack compiles fine but when I load up the JS on the page I get an error
Uncaught TypeError: Cannot read property 'userAgent' of undefined
So userAgent lives on window.navigator so I checked to see what window referred to inside the webfontloader.js file in the node_modules directory and I see it's set to this which is passed in via the module closure.
If I alter the this to window and recompile it works fine.
I'm not sure if this is a webfontloader issue or a misconfig of WebPack. However I've noticed a similar issue https://github.com/typekit/webfontloader/issues/246 which indicates there may have been a similar issue before?
Please can you advise? Web Font Loader v1.6.0
Update: may relate to https://github.com/webpack/webpack/issues/97

Could you try v1.6.2 to see if this is fixed?

Unfortunately the same error persists. Logging this return a plain JavaScript object {}

Hmm, there is only one place in the code that reads userAgent and it correctly references window.navigator.userAgent. It looks like webpack isn't setting up the window correctly in this case.

I believe it is a webpack issue. Closing.


Preview HTML Report not allowing me to select file

Describe the bug
I am trying to use the Preview Coverage Report feature. I select the command from the Command list and see "Choose a Coverage Report to preview". From this point I don't know how to select the file. I have tried clicking on it in VS code and typing the file name with and without the path included. No matter what I do I see the following in the logs.
[1543327608077][gutters]: Error Did not choose a file!
[1543327608077][gutters]: Stacktrace Error: Did not choose a file!
	at Coverage.<anonymous> (/Users/jrai/.vscode/extensions/ryanluker.vscode-coverage-gutters-2.2.2/out/src/coverage-system/coverage.js:43:27)
	at Generator.next (<anonymous>)
	at fulfilled (/Users/jrai/.vscode/extensions/ryanluker.vscode-coverage-gutters-2.2.2/out/src/coverage-system/coverage.js:4:58)
	at <anonymous>

To Reproduce
Steps to reproduce the behaviour:

Open project folder with report at coverage/Icov.info
CMD Shift P to show all commands
Select "Preview Coverage Report"
See that you are not able to select a file.

Expected behaviour
I can select a file
Screenshots

Desktop (please complete the following information):

OS: macos
Extension Version 2.2.2
VSCode Version 1.29.1

I am having the same issue.

@MisterJimson thanks for submitting an issue and @krishnakumar3044 for giving further info. Coverage report runs only via the html files that are generated by some lcov coverage tools. I have attached a screenshare below of me loading a node coverage report from the example project.
Depending on which language and the features of its lcov generation tool you may or may not get something similar to what I showed below.

I have html files in my directory, but I could not select the .html file. I am using C++ language. Here is the screenshot.

@krishnakumar3044 ahh it is because the findReports https://github.com/ryanluker/vscode-coverage-gutters/blob/master/src/coverage-system/coverage.ts#L53-L69
is looking for coverage/**/index.html I will add a bug #199 to the 2.3.1 release to make this more forgiving by using something like **/index.html. In the meantime if you move the index.html into a folder called coverage it will work.

Thanks for the update. Yes, if I move the index.html under /coverage folder, it works. I look forward to the fix for this, as we use separate source and build directories and coverage data is nested inside build directory

One more enhancement request is following:
If we can allow custom name , instead of fixed "index.html" file, that would be helpful too.
Ex: coverage_results_index.html

@krishnakumar3044 thanks for the additional info I have updated #199


Prometheus instance has no targets (syncing nodes into Endpoints object failed)

What did you do?
I have deployed Prometheus operator to monitor my application, however the Prometheus instance is showing no targets listed.
Note that before deploying a Prometheus instance and Service Monitor for my app, I deployed kube prometheus by following the KOPSonAWS docs.
With this, the prometheus-k8s instance in the monitoring namespace is working as expected and lists all cluster related targets. So, user error is highly likely here.
What did you expect to see?
I expected to see my app listed as a target in Prometheus.
What did you see instead? Under which circumstances?
A blank page listing no targets.
Environment

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"17d7182a7ccbb167074be7a87f0a68bd00d58d97", GitTreeState:"clean", BuildDate:"2017-08-31T09:14:02Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"f38e43b221d08850172a9a4ea785a86a3ffa3b3a", GitTreeState:"clean", BuildDate:"2017-10-11T23:16:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
KOPS on AWS

Manifests:

My apps manifest:
apiVersion: apps/v1beta2 # for versions before 1.7.0 use apps/v1beta1
kind: Deployment
metadata:
  name: sampleapp
  namespace: sampleapp
  labels:
    app: sampleapp
spec:
  replicas: 1
  selector:
    matchLabels:
      app: sampleapp
  template:
    metadata:
      labels:
        app: sampleapp
    spec:
      containers:
      - name: sampleapp
        image: mysampleapp:latest
        ports:
        - name: web
          containerPort: 8081
          protocol: TCP
---
kind: Service
apiVersion: v1
metadata:
  name: sampleapp
  namespace: sampleapp
spec:
  selector:
    app: sampleapp
  ports:
  - name: web
    protocol: TCP
    port: 8081
    targetPort: web

The prometheus instance manifest:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
  namespace: sampleapp
  labels:
    app: prometheus
spec:
  version: v1.7.1
  serviceMonitorSelector:
    matchLabels:
      app: sampleapp
  resources:
    requests:
      # 2Gi is default, but won't schedule if you don't have a node with >2Gi
      # memory. Modify based on your target and time-series count for
      # production use. This value is mainly meant for demonstration/testing
      # purposes.
      memory: 400Mi
---
kind: Service
apiVersion: v1
metadata:
  name: prometheus
  namespace: sampleapp
spec:
  selector:
    app: prometheus
  ports:
  - name: web
    protocol: TCP
    port: 30904
    targetPort: 9090

and lastly, the service monitor:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: sampleapp
  namespace: sampleapp
  labels:
    app: sampleapp
spec:
  selector:
    matchLabels:
      app: sampleapp
  endpoints:
  - port: web
    interval: 10s

Prometheus Operator Logs:

ts=2017-10-19T10:01:17Z caller=operator.go:293 component=prometheusoperator msg="Prometheus updated" key=monitoring/k8s
ts=2017-10-19T10:01:17Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
ts=2017-10-19T10:01:17Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:01:24Z caller=operator.go:273 component=prometheusoperator msg="Prometheus added" key=sampleapp/prometheus
ts=2017-10-19T10:01:24Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:01:24Z caller=operator.go:987 component=prometheusoperator msg="creating configuration"
ts=2017-10-19T10:01:24Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:01:24Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:01:24Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:01:24Z caller=operator.go:347 component=alertmanageroperator msg="update handler" old=4300 cur=4304
ts=2017-10-19T10:01:24Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:01:24Z caller=operator.go:605 component=prometheusoperator msg="update handler" old=4300 cur=4304
ts=2017-10-19T10:01:24Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:01:24Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:02:08Z caller=operator.go:327 component=alertmanageroperator msg="Alertmanager updated" key=monitoring/main
ts=2017-10-19T10:02:08Z caller=operator.go:383 component=alertmanageroperator msg="sync alertmanager" key=monitoring/main
ts=2017-10-19T10:02:23Z caller=operator.go:293 component=prometheusoperator msg="Prometheus updated" key=monitoring/k8s
ts=2017-10-19T10:02:23Z caller=operator.go:293 component=prometheusoperator msg="Prometheus updated" key=sampleapp/prometheus
ts=2017-10-19T10:02:23Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
ts=2017-10-19T10:02:23Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:02:23Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:02:23Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:02:29Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
ts=2017-10-19T10:02:29Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:02:29Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
ts=2017-10-19T10:02:29Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:02:40Z caller=operator.go:605 component=prometheusoperator msg="update handler" old=4304 cur=4445
ts=2017-10-19T10:02:40Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:02:40Z caller=operator.go:347 component=alertmanageroperator msg="update handler" old=4304 cur=4445
ts=2017-10-19T10:02:40Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:03:08Z caller=operator.go:327 component=alertmanageroperator msg="Alertmanager updated" key=monitoring/main
ts=2017-10-19T10:03:08Z caller=operator.go:383 component=alertmanageroperator msg="sync alertmanager" key=monitoring/main
ts=2017-10-19T10:03:20Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:03:20Z caller=operator.go:1001 component=prometheusoperator msg="current config or current configmaps has changed"
ts=2017-10-19T10:03:20Z caller=operator.go:1007 component=prometheusoperator msg="updating configuration"
ts=2017-10-19T10:03:20Z caller=operator.go:640 component=prometheusoperator msg="sync prometheus" key=sampleapp/prometheus
ts=2017-10-19T10:03:20Z caller=operator.go:998 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2017-10-19T10:03:33Z caller=operator.go:306 component=prometheusoperator msg="syncing nodes into Endpoints object failed" err=null

I thought that this may be a namespacing issue, so I tried deploying everything to default but the results were the same.
Does anyone see what I may be doing wrong? or how I can get further more detailed debug logs from prom-operator? Currently it just has the last line on syncing nodes to EPs failing.
Many thanks,
Andy

Can you share the configuration that your Prometheus instance has loaded (you can find it in the Prometheus web UI)? Also the Deployment used to deploy the Prometheus Operator would be helpful as well.

Hi @brancz
The Prometheus instance configuration is:
global:
  scrape_interval: 30s
  scrape_timeout: 10s
  evaluation_interval: 30s

It seems quite empty, I am guessing it is a default.
The Deployment for the Prometheus Operator is the one from kube-prometheus. Linked here
Although, I note that you have recently updated the image tag version to v0.14.0 - I do not see a v14 on Quay so I have reverted back to the v0.13.0 tag.
Additionally, As I had torn down the kops cluster, I had to redeploy the cluster to capture the above Prom config. This time around I noticed the syncing nodes into Endpoints object failed message after the initial prometheus-operator deployment but before the prometheus instance or servicemonitor were created.
Lastly, I note that kube-prom was recently updated to use Prometheus tag v2.0.0-rc.1. In the Deployment I posted initially I used v1.7.1. I have tried updating to the 2.x tag with no change in result.
Kind Regards,
Andy

The fact that your configuration is nothing but the default, this means the ServiceMonitor was either not correctly selected or is malformed. Can you double check that your ServiceMonitor is correctly indented (also no tabs instead of spaces etc.)?

This is the service monitor definition that I am using:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: sampleapp
  namespace: sampleapp
  labels:
    app: sampleapp
spec:
  selector:
    matchLabels:
      app: sampleapp
  endpoints:
  - port: web
    interval: 10s

I based it on (or copied it from) the example definitions for kube-prom. Also comparing it to the prometheus-k8s definitions for kube-prob (here), I notice that these definitions have a namespaceSelector.
  namespaceSelector:
    matchNames:
    - monitoring

Perhaps this is something I need to add, as I am running my service in the sampleapp NS. Although I did try deploy everything to default and that didn't work either. I will give the namespaceSelector a try over the weekend.
Also, does it matter what NS that the ServiceMonitor is deployed to? I deploy my ServiceMonitor to the sampleapp NS, but perhaps it needs to run in the monitoring NS alongside the operator?

The kube-prometheus Prometheus instance is highly adapted to only monitor cluster components. It only has RBAC access to the namespaces it needs to: default, monitoring, and kube-system. If you look at your Prometheus logs, this will probably tell you that you don't have access to request something from the apiserver.

I am deploying a separate Prometheus instance to monitor my sampleapp.
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
  namespace: sampleapp
  labels:
    app: prometheus
spec:
  version: v1.7.1
  serviceMonitorSelector:
    matchLabels:
      app: sampleapp
  resources:
    requests:
      # 2Gi is default, but won't schedule if you don't have a node with >2Gi
      # memory. Modify based on your target and time-series count for
      # production use. This value is mainly meant for demonstration/testing
      # purposes.
      memory: 400Mi
---
kind: Service
apiVersion: v1
metadata:
  name: prometheus
  namespace: sampleapp
spec:
  selector:
    app: prometheus
  ports:
  - name: web
    protocol: TCP
    port: 30904
    targetPort: 9090

and then a ServiceMonitor to tie my app to this Prometheus instance:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: sampleapp
  namespace: sampleapp
  labels:
    app: sampleapp
spec:
  selector:
    matchLabels:
      app: sampleapp
  endpoints:
  - port: web
    interval: 10s

Do you see any reason why this would not work? There must be something wrong with these manifests because the prometheus instance in the sampleapp namespace does not get configured with the service monitor.

There must be something wrong with these manifests because the prometheus instance in the sampleapp namespace does not get configured with the service monitor.

Yes I agree. Can you check the logs of the Prometheus server? It might show if there are permission problems or malformed configuration or something like that.

I just got around to testing again today. Looks like I made a mistake on the above regarding the Prometheus configuration. It takes some time for the prometheus-config-reloader to push the config after the service monitor is created. Previously I had checked right away and not waited. Today, I see the following under the Prometheus configuration tab:
global:
  scrape_interval: 30s
  scrape_timeout: 10s
  evaluation_interval: 30s
scrape_configs:
- job_name: sampleapp/sampleapp/0
  scrape_interval: 10s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  kubernetes_sd_configs:
  - api_server: null
    role: endpoints
    namespaces:
      names:
      - sampleapp
  relabel_configs:
  - source_labels: [__meta_kubernetes_service_label_app]
    separator: ;
    regex: sampleapp
    replacement: $1
    action: keep
  - source_labels: [__meta_kubernetes_endpoint_port_name]
    separator: ;
    regex: web
    replacement: $1
    action: keep
  - source_labels: [__meta_kubernetes_namespace]
    separator: ;
    regex: (.*)
    target_label: namespace
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_pod_name]
    separator: ;
    regex: (.*)
    target_label: pod
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_service_name]
    separator: ;
    regex: (.*)
    target_label: service
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_service_name]
    separator: ;
    regex: (.*)
    target_label: job
    replacement: ${1}
    action: replace
  - separator: ;
    regex: (.*)
    target_label: endpoint
    replacement: web
    action: replace

There are no errors in the prometheus logs:
level=info ts=2017-10-22T08:58:48.892015977Z caller=main.go:216 msg="Starting prometheus" version="(version=2.0.0-rc.1, branch=HEAD, revision=5ab8834befbd92241a88976c790ace7543edcd59)"
level=info ts=2017-10-22T08:58:48.892115056Z caller=main.go:217 build_context="(go=go1.9.1, user=root@1f56dd8b6f7b, date=20171017-12:34:15)"
level=info ts=2017-10-22T08:58:48.892163723Z caller=main.go:218 host_details="(Linux 4.4.78-k8s #1 SMP Fri Jul 28 01:28:39 UTC 2017 x86_64 prometheus-prometheus-0 (none))"
level=info ts=2017-10-22T08:58:48.895060701Z caller=web.go:380 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2017-10-22T08:58:48.895787189Z caller=main.go:315 msg="Starting TSDB"
level=info ts=2017-10-22T08:58:48.915806574Z caller=targetmanager.go:68 component="target manager" msg="Starting target manager..."
level=info ts=2017-10-22T08:58:48.92163596Z caller=main.go:327 msg="TSDB started"
level=info ts=2017-10-22T08:58:48.92170002Z caller=main.go:394 msg="Loading configuration file" filename=/etc/prometheus/config/prometheus.yaml
level=info ts=2017-10-22T08:58:48.921937642Z caller=main.go:371 msg="Server is ready to receive requests."
level=info ts=2017-10-22T08:58:49.27556235Z caller=main.go:394 msg="Loading configuration file" filename=/etc/prometheus/config/prometheus.yaml
level=info ts=2017-10-22T09:00:17.457440378Z caller=main.go:394 msg="Loading configuration file" filename=/etc/prometheus/config/prometheus.yaml
level=info ts=2017-10-22T09:00:17.458215127Z caller=kubernetes.go:100 component="target manager" discovery=k8s msg="Using pod service account via in-cluster config"
level=info ts=2017-10-22T09:44:48.487319538Z caller=main.go:394 msg="Loading configuration file" filename=/etc/prometheus/config/prometheus.yaml
level=info ts=2017-10-22T09:45:54.456308687Z caller=main.go:394 msg="Loading configuration file" filename=/etc/prometheus/config/prometheus.yaml
level=info ts=2017-10-22T09:45:54.456875018Z caller=kubernetes.go:100 component="target manager" discovery=k8s msg="Using pod service account via in-cluster config"

I have also tried a few different changes today. As mentioned in a previous comment, I have added the namespaceSelector to the service monitor.
Lastly, I thought that it may be a permissions issue, so I have updated my Prometheus manifest to include a service account and role definitions (that I have blatantly copied from kube-prom with changed names and namespaces):
apiVersion: v1
kind: ServiceAccount
metadata:
  name: prometheus-sampleapp
  namespace: sampleapp
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: prometheus-sampleapp
  namespace: sampleapp
rules:
- apiGroups: [""]
  resources:
  - nodes
  - services
  - endpoints
  - pods
  verbs: ["get", "list", "watch"]
- apiGroups: [""]
  resources:
  - configmaps
  verbs: ["get"]
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: prometheus-k8s
rules:
- nonResourceURLs: ["/metrics"]
  verbs: ["get"]
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
metadata:
  name: prometheus-sampleapp
  namespace: sampleapp
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: prometheus-sampleapp
subjects:
- kind: ServiceAccount
  name: prometheus-sampleapp
  namespace: sampleapp
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: prometheus-sampleapp
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: prometheus-sampleapp
subjects:
- kind: ServiceAccount
  name: prometheus-sampleapp
  namespace: sampleapp
---
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
  namespace: sampleapp
  labels:
    app: prometheus
spec:
  version: v2.0.0-rc.1
  serviceAccountName: prometheus-sampleapp
  serviceMonitorSelector:
    matchLabels:
      app: sampleapp
  resources:
    requests:
      # 2Gi is default, but won't schedule if you don't have a node with >2Gi
      # memory. Modify based on your target and time-series count for
      # production use. This value is mainly meant for demonstration/testing
      # purposes.
      memory: 400Mi
---
kind: Service
apiVersion: v1
metadata:
  name: prometheus
  namespace: sampleapp
spec:
  selector:
    app: prometheus
  ports:
  - name: web
    protocol: TCP
    port: 30904
    targetPort: 9090

However, unfortunately while the service monitor configuration is being pushed to prom, the targets are not being detected and no errors are being logged.

 Solved the problem, my Service was missing the label that the Service Monitor was tied to.
kind: Service
apiVersion: v1
metadata:
  name: prometheus
  namespace: sampleapp
spec:
  selector:
    app: prometheus
  ports:
  - name: web
    protocol: TCP
    port: 30904
    targetPort: 9090
---
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: sampleapp
  namespace: sampleapp
  labels:
    app: sampleapp
spec:
  selector:
    matchLabels:
      app: sampleapp
  endpoints:
  - port: web
    interval: 10s

I just had to update the service to include the label:
metadata:
  name: prometheus
  namespace: sampleapp
  labels:
    app: sampleapp

As hinted in my original post, I always suspected user error was the cause - however, I am embarrassed that it took me that long to notice the missing label.
Either way, all happy now, closing. :)


[Code Addition Request]: Add Weather App to Beginner_Projects

Have you completed your first issue?

[X] I have completed my first issue

Guidelines

[X] I have read the guidelines
[ ] I have the link to my latest merged PR

Latest Merged PR Link
N/A
Project Description
Want to build a simple weather app using python and API
Full Name
Prisha Sanyal Aich
Participant Role
gssoc-ext, hacktoberfest-accepted

@psanyalaich what tech stack you are planning to use?

I'm planning to use Python, PyQt5, and OpenWeather API


AttributeError: 'Gaze_GAN' object has no attribute 'D_real_gan_logits'. Could you please find that whether there is any wrong in the code?

Hi, I am encountering the same error: AttributeError: 'Gaze_GAN' object has no attribute 'D_real_gan_logits'. @zhangqianhui could you please help here.
Thanks!

I will check the code.

Additionally, the v2 version of gazegan has been released.
https://github.com/zhangqianhui/GazeAnimation

i have updated new code.

@zhangqianhui Thanks a lot. It will be helpful. By the way, training the code without setting "--is_ss" how will that effect the results?
Thanks.

a little @anantthebiker  However, it is important to design a self-supervised module to improve the sample quality of gan.


Create Social Distance Detection

The Social Distance Detection system is a Python application that uses OpenCV and deep learning techniques to monitor and determine whether individuals in a specified area are maintaining appropriate social distancing. This tool is particularly useful in public spaces to promote safety during health crises.
Pull Request Template
script name - social_distance_detection.py
Brief about script
The Social Distance Detection script utilizes OpenCV and a YOLO deep learning model to monitor real-time social distancing in public spaces. It captures video from a webcam, detects individuals in the frame, and calculates the distance between them. If any two individuals are found to be closer than a specified threshold, a visual alert is displayed on the screen. This tool promotes safety by helping ensure compliance with social distancing guidelines.
Issue no.(must) - #683
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[ ] My file is in proper folder (Name of folder should be in lowercase with no space in between) (E.g. meet_schedular)
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt (Include version numbers too e.g. pandas==0.0.1) with my script
[ ] I have used REPO README TEAMPLATE (Necessary)
[ ] Just including required dependencies in requirements.txt (Don't include Python version too)

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

@pawangeek , I've uploaded my PR please do have a look


Tests hang

Running npm run test hangs. Specifically, this seems to be an issue with async/await in test.js and in app/index.js.
A working test.cb() has been pushed to feat/add-tests, but these tests are not done serially, which means that the README file in temp isn't deleted and re-run each time. It would be better to fix test.serial to work, like the other generator testing I've seen.
Adding tests is crucial; it will allow me to validate how the READMEs should look given any output, which currently is a haphazard process.

They no longer hang.


Update index.ts

Do not try to extract thumbnail if there is no pointer.

"firstIfdPointer" gets null? I think it's no.
https://github.com/hMatoba/piexifjs/blob/2.0/src/utils.ts#L547

I am very sorry I do not have the image that caused that anymore... But this corrected it. Sorry I do not know much of exif so can't really help. The only thing I know is that I was getting null at that spot. Maybe it was due to some incorrect exif in the first place.


Added bracket notation support

Hi!
#6

@erictrinh Could you pay some attention to this PR please?


Initial video support

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Test URLs:

Before: https://main--audemarspiguet-careers--hlxsites.hlx.page/en/
After: https://videos--audemarspiguet-careers--hlxsites.hlx.page/en/

The "black video box" seems to be a firefox issue, it works in chrome


Diagnose a conflicting silgen_name/extern(c) name instead of asserting/crashing

Today, if we have a multiple conflicting forward-declarations using the name @_extern(c) or @_silgen_name name, the compiler asserts (in asserts-on builds) or crashes in SIL verifier. Let's turn the assert into a diagnostic instead.

@swift-ci please test


Log table loading problems

Rationale
We don't know what caused Issue 49506: Delete of samples has a null table, so add some logging for next time. We're still returning null, though (future change will address that part of the issue).

Closed in favor of https://github.com/LabKey/platform/pull/5183

Closed in favor of https://github.com/LabKey/platform/pull/5183


adding utils.isRoot function

Closes https://github.com/stealjs/system-npm/issues/104.

This should be utils.pkg.isRoot.  Also a function like utils.pkg.default(loader) to return loader.npmPaths.__default would be good.

Ok, I'll make those changes.

@matthewp I don't think my change would have caused the error in CI. Should I just try re-running the CI task? Or do I need to look into this error?

I just restarted it

This is released as system-npm 0.5.4


i18n Spanish and Messages.pot

Hi team, I have uploaded some comments in the Message.pot, I had to change some settings as some data was not loading, I think it is now all synchronised.
I also added the new appendices structures, and Keyword translations, as well as some other things from the new flow.
I hope everything is ok, I've tested it locally, best regards.

Thank you, I will update and review the new changes, thanks for the work you do, it's awesome....  Appendix E - Most Common Types and Traits Required To Write Contracts


Question: Cannot import minified script as ES6 module

I am working in a large (300k+ LOC) codebase that's based on require.js and bower after all scripts run through Babel. Our build process is not flexible enough to accommodate bundling with node_modules, so we're opting for direct inclusion of scripts in dist. After copying the minified version into our files, the exported object is undefined.
import Draft from 'frameworks/draftjs/Draft.min'; // script runs, but 'Draft' is undefined here

DevTools shows that the script does execute, but I don't understand the disconnect. I noticed a window.Draft, but that is also undefined

from a light look at dist/Draft, it looks like we simply define the "Draft" variable when it is loaded.
var Draft = ...

Maybe we should set something on the (window || module.exports) object within the script.
If this is true, cc @hellendag, maybe can modify the way we produce dist, to do this.


PUT/DELETE requests using aadHttpClient is nowhere documented

I have to to PUT and DELETE requests to my custom api.
I know, that I can do that with the fetch() function.
I am allready using .get like following (example code):
 this.props.context.aadHttpClientFactory     .getClient('https://graph.microsoft.com')     .then((client: AadHttpClient) => {       // Search for the users with givenName, surname, or displayName equal to the searchFor value       return client         .get(           https://graph.microsoft.com/v1.0/users?$select=displayName,mail,userPrincipalName&$filter=(givenName eq '${escape(this.state.searchFor)}')%20or%20(surname%20eq%20'${escape(this.state.searchFor)}')%20or%20(displayName%20eq%20'${escape(this.state.searchFor)}'),           AadHttpClient.configurations.v1         );     })
But how would I use fetch or post instead of .get()?
I mean, how do I have to pass the body parameters?

The HTTP-based APIs in SPFx are all based on the browser fetch API. This has three methods: get(), post() and fetch(). The fetch() method allows you to do anything... the post() method automatically uses the HTTP POST method.
They are all based on the SpHttpClient object, which is documented.
All three methods have three parameters, the last one being optional. That lets you customize anything... this is the IHttpClientOptions interface. It's not documented on the SPFx docs because it's not necessary to duplicate what's already documented in the fetch API.
This object has properties for headers to set, the body, and more.

there is not documented, how I have to pass the paramethers.
I only get following from my editor:
(method) AadHttpClient.fetch(url: string, configuration: AadHttpClientConfiguration, options: IHttpClientOptions): Promise
Performs a REST service call.
@remarks — Although the AadHttpClient subclass adds additional enhancements, the parameters and semantics for HttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/
@param url — The endpoint URL that fetch will be called on.
@param configuration — Determines the default behavior of HttpClient; normally this should be the latest version number from HttpClientConfigurations.
@param options — Additional options that affect the request.
@returns — A promise that will return the result.
So far so good... but what is AadHttpClientConfiguration?? The documentation  doesn'thelp me alot here.
Same with options...
Where do I have to pass my http method, the body etc?

@andreschmid8 said:

what is AadHttpClientConfiguration

It sets the default configuration of the client, like setting headers such as accept:application/json and others. You will always use AadHttpClientConfiguration.configuration.v1 because that's the only one available.

Where do I have to pass my http method, the body etc?

That's the options parameter. If you look at the definition of it's type IHttpClientOptions, you'll see it has properties for body (a string), headers (object of name-value pairs) and method (a string).


Atom for the scalar relative entropy cone: ExpConeQuad

In this PR, I add support for the scalar relative entropy cone via the approximation method that was defined in Theorem-3 of THIS paper.
The sREC also happens to be directly connected (under a permutation and sign change of the arguments) to the exponential cone, and @rileyjmurray added a method for conversion from ExpCone to ExpConeQuad to that end.
As it stands now, the biggest shortcoming in the current state of the PR, are two things:

Lack of support for elementwise application of ExpConeQuad to vector variables --- this is due to the usage of the quad_over_lin atom for implementing the semidefinite approximation (currently, one of the test cases has been explicitly modified to make it pass)
Lack of proper experimentation for arriving at a sensible set of defaults for the parameters $(m,k)$ in the approximation --- while $m$ is related to the quadrature approximation used in the procedure, $k$ doesn't lend itself to any kind of an obvious intuitive interpretation.

There's also some documentation missing, but I will add that in the next few commits.
Thank you!

Just wanted to kick off an important discussion regarding where ExpConeQuad should be placed within the web documentation.
So, as it stands right now, semantically, ExpConeQuad  pretty much offers an alternative (which can be made arbitrarily accurate by tweaking $(m,k)$) canonicalization pathway to the standard ExpCone; hence, I felt that it might be a bit awkward to place it within all the other constraint classes (like ExpCone, SOC, PowConeNDetc.) since it is _functionally_ redundant toExpConefrom a modeling perspective, and instead, expose it through theas_expconequad(. , .)method that has been written for converting fromExpConetoExpConeQuad`.
I would like to hear everyone's thoughts on this! @SteveDiamond @rileyjmurray

Just wanted to kick off an important discussion regarding where ExpConeQuad should be placed within the web documentation.
So, as it stands right now, semantically, ExpConeQuad pretty much offers an alternate (which can be made arbitrarily accurate by tweaking (m,k) ) canonicalization pathway to the standard ExpCone; hence, I felt that it might be a bit awkward to place it within all the other constraint classes (like ExpCone, SOC, PowConeND etc.) since it is functionally redundant to ExpCone from a modeling perspective, and instead, expose it through the as_expconequad(. , .) method that has been written for converting from ExpCone to ExpConeQuad.

I'd be in favor of retaining an ExpConeQuad class but not really suggesting that users work with that class. Rather, they should use the ExpCone class and then call con.as_expconequad(m k). How about this:

ExpConeQuad gets a disclaimer at the top of its docstring saying that we don't promise stability of its API. However, we do promise stability of the API for ExpCone.as_expconequad.
The docstring for ExpCone.as_expconequad contains a meaningful amount of information as to how the approximation works, but it wouldn't be as detailed as the documentation for ExpConeQuad.

If we go in that direction then I think we would expose ExpConeQuad in this part of the web docs like every other Constraint class.

@aryamanjeendgar the style check with isort is failing. Take a look and fix when you get a chance.

Approved! @SteveDiamond or @akshayka please review as soon as convenient. Since this changes CVXPY's public API we need more than one maintainer to approve. (We will have follow-up PRs though, so these changes can easily be modified.)


[CI][R][C++] test-r-linux-valgrind has started failing

Describe the bug, including details regarding any error messages, version, and platform.
The test-r-linux-valgrind job has started failing since those commits were merged (https://github.com/apache/arrow/compare/fe38d47e82c6ffc231f0918be15aa5cd0da98607...cd607d00b9e3c5f2ac2a2e373ba7571fd75fc725) with several leaks:
2024-04-10T00:57:52.3151980Z ==774== LEAK SUMMARY:
2024-04-10T00:57:52.3152139Z ==774==    definitely lost: 0 bytes in 0 blocks
2024-04-10T00:57:52.3152329Z ==774==    indirectly lost: 0 bytes in 0 blocks
2024-04-10T00:57:52.3152513Z ==774==      possibly lost: 15,813 bytes in 36 blocks
2024-04-10T00:57:52.3152718Z ==774==    still reachable: 121,607,441 bytes in 38,708 blocks
2024-04-10T00:57:52.3152903Z ==774==                       of which reachable via heuristic:
2024-04-10T00:57:52.3153095Z ==774==                         newarray           : 4,264 bytes in 1 blocks
2024-04-10T00:57:52.3153280Z ==774==         suppressed: 0 bytes in 0 blocks
2024-04-10T00:57:52.3153481Z ==774== Reachable blocks (those to which a pointer was found) are not shown.
2024-04-10T00:57:52.3153778Z ==774== To see them, rerun with: --leak-check=full --show-leak-kinds=all
2024-04-10T00:57:52.3153941Z ==774==
2024-04-10T00:57:52.3154114Z ==774== For lists of detected and suppressed errors, rerun with: -s
2024-04-10T00:57:52.3154330Z ==774== ERROR SUMMARY: 15 errors from 15 contexts (suppressed: 0 from 0)

Please see link of the job for more details.
Component(s)
C++, Continuous Integration, R

This seems an awful lot like https://github.com/apache/arrow/issues/30368 but it's not clear to me how we end up with an AVX512 instruction. EXTRA_CMAKE_FLAGS=-DARROW_RUNTIME_SIMD_LEVEL=AVX2 gets set but I also see (arrow::compute::SimdLevel::type)4 which looks like it maps to SimdLevel::AVX512. @paleolimbot does this ring any bells?

I agree with @amoeba, what likely happened is that the runner supports avx512 (valgrind does not) and for some reason the code that get's invoked is not covered by the runtime simd level envvar. The quick way to fix this would be to also add ARROW_SIMD_LEVEL=AVX2 to that job so we don't compile anything for avx512.
Actually fixing it would probably be #30368 and checking the thing that valgrind instruments to set the simd level correctly.

I don't think this is a blocker so I've created RC0 for 16.0.0 without it.

@raulcd Looking at the likely cause you are right, if this issue would happen on CRAN it would happen with our current version (as we don't control the envvars there).


Support flightplan.babel.js a la gulpfile.babel.js

Please!

This should already work [1]. Alternatively, you can simply use Node 6 and get native ES6 features.
[1] https://github.com/pstadler/flightplan/issues/114

@pstadler Nice! You need to document this! 😄


Update README.md #127

@x13enos, Thanks for your help, but we might be ahead of time here 😄. The component import functionality won't be available until the next release. I'm collecting some other issues before making it public, it will come with changes in README too.
I will close your PR because of the README [kind of] rewriting I have been working on. But I do appreciate your help!

no problem, thank you for feedback!


Several transactions stuck in mempool for days despite sufficient fee (mainnet)

Describe the issue
Transactions are reported as in the mempool for days (according to most explorer and our node), while some other public queries show them as mined. Yet there is no reason (from my understanding) for them not to be mined, as they are valid and have more than sufficient fee.
Can you reliably reproduce the issue?
See the most recent 6 (or more, depending when you're reading this) unconfirmed transactions here: https://blockchair.com/dogecoin/address/D6WpnsUFCVdKZp52PNGwT7Ei3NGkaGaoKp
Notice that all those transactions are perfectly valid, and are paying fees well in line with transactions currently being minded.
Take this transaction, for example: https://blockchair.com/dogecoin/transaction/41e90534bb9d59f48ed5a9887937e8a5de93344b600d87d49a00e73c91a35586
2 days unconfirmed, despite being marked as confirmed here: https://live.blockcypher.com/doge/tx/41e90534bb9d59f48ed5a9887937e8a5de93344b600d87d49a00e73c91a35586/
Now, obviously it's possible that blockcypher is incorrect, although I don't know how they could et this wrong, but it still doesn't explain why miners won't include those 6 transactions in blocks.
What version of Dogecoin Core are you using?
Dogecoin Core 1.14.2
Machine specs:

OS: linux
CPU: N/A (K8s cluster)
RAM: N/A (K8s cluster)
Disk size: N/A (K8s cluster)
Disk Type (HD/SDD): SSD (K8s cluster)

Possible solutions:
We can try rebuilding and rebroadcasting each of them with a much higher fee, but that is somewhat of a last report here given the nature of our system.

#1650 Duplicate. Not sure how this happened.


Feature request: Allow sending trace messages to client

Currently, both the old BotFrameworkAdapter and the new CloudAdapter prevent trace activities from being sent to the client. There are some use-cases where this might be useful though (e.g., certain test scenarios).
Would it be possible to add an option to the CloudAdapterBase class that would allow trace messages to be sent?
It could be a simple boolean or a function that determines per request if traces should be forwarded.
Happy to suggest a PR myself but wanted to know if it would even have a chance getting merged.
https://github.com/microsoft/botbuilder-js/blob/7afa288668abd45b680bc0cd8bc7a58f3e276f34/libraries/botbuilder-core/src/cloudAdapterBase.ts#L75

Thanks for filing this and opening a PR @alopix! Could you expand on the certain test scenarios that you're facing?
As a workaround, you could could add a SendActivitiesHandler to your TurnContext instance to grab or create a ConnectorClient instance and forcibly send the trace activity. Have you explored this approach to get unblocked?
https://github.com/microsoft/botbuilder-js/blob/3dc3d7e7ceb949ab18d1f236fd6a2daf46c53e16/libraries/botbuilder-core/src/turnContext.ts#L53-L57
One caveat is that I'm not sure the channel (DLS in this case) will respect this ActivityType and send it to the end client.

The scenario is to run trace analysis just like in the botbuilder emulator but for using any other client—especially since the emulator only supports DirectLine and not DirectLine Speech and others.


When is publishedSuppressions.xml file updated?

publishedSuppressions.xml file was last updated on Jan 7. Since then several new suppressions have been added to generatedSuppressions.xml file. Do I understand correctly that at some point suppressions should be copied from generatedSuppressions.xml to publishedSuppressions.xml? When will this happen? Or if I understand something wrong, what is the correct way to get those false positives from generatedSuppressions.xml file to my own workflow? I'm using dependency-check-maven:8.0.2 and currently my build fails because of #5373.

Should update automatically anytime the FP approval flow runs. Approved a pending proper FP suppression, which triggered the pipeline and has restored resolved the published suppressions for now.
@jeremylong Is there some issue in the release pipeline that reverts to an old version of the published suppressions in the gh-pages branch?

The release pipeline shouldn't revert the publishedSuppressions.xml as the file is not generated as part of the site. I'll double check this during the next release.

Would it be useful to have a meta-header in the publishedSuppressions.xml, something along the lines of knownExploitedURL
datestamp and count?
"title":  "Published suppressions for false positives",
"catalogVersion":  "2023.02.27",
"dateReleased":  "2023-02-27T09:52:01.2907Z",
"count":  102


x/tools/go/analysis/passes/nilness: no position information with error

What version of Go are you using (go version)?

$ go version
1.12

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/reilly/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/reilly/league/services:/Users/reilly/go:"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gz/4ytqr0r12q1fbx8ct_w3k_880000gn/T/go-build175674008=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Ran the nilness analyzer on this (simplified) package:
package foo

import (
	"fmt"
)

func Foo() {
	var x []int
	for _, a := range x {
		fmt.Println(a)
	}
}

What did you expect to see?
Ideally: a different error about how you're iterating over a nil slice
Less ideally: the same error, but with information telling me where the error is
What did you see instead?
-: nil dereference in index operation
This kind of error is pretty hard to track down if I'm running the analyzer over a large codebase, because it doesn't say which file or package is failing.

/cc @matloob

This is a major problem that deserves attention

@vovapi's CL above adds position information to the error message, but I think to improve this further we'd have alter the way go/ssa tracks position information.  Something similar was done for staticcheck: https://github.com/dominikh/go-tools/commit/c14c261fd1fd7dec2e23b44bbf8c7b49cbd4e239

Thought it might be worth adding a case where the nilness analyzer fails to provide position information where it seemingly should do so.
func do(a interface{}) {
	switch a.(type) {
	case nil:
		return
	}
	switch a.(type) {
	case nil:
		return
	}
}

https://go.dev/play/p/3K_9FFGOWzd
❯ go run golang.org/x/tools/go/analysis/passes/nilness/cmd/nilness@latest test.go
-: impossible condition: non-nil == nil
exit status 3

Thought it might be worth adding a case where the nilness analyzer fails to provide position information where it seemingly should do so.
...

Change https://go.dev/cl/394694 should have now addressed the issue with positions in case conditions.


How to use your script?

Thank you for your work.
I follow your instruction and it seems to works fine.
My problem is I don't know how to use your verifier.
I stored the results in a variable:
results = socks_verifier.verify(email)
and then what else?
How do I know this "email" is a correct email.
I printed the results:
{'address': Address(name=''<EMAIL_ADDRESS>username='contact', domain='miiting.fr'), 'valid_format': True, 'deliverable': False, 'full_inbox': False, 'host_exists': True, 'catch_all': False}
But how do I enjoy all this?
I can understand in this result that format is ok, but what does mean all these info?
Could you please be more clear about the usage of your work.
I guess you spend a lot of time in developping this script, but I can't enjoy it.
Thanks in advance to help me.
Kind regards

U can check the three flags - deliverable, host exist, valid format - if these are true then u should mark the email as usable


sentinel support

Like redis sentinel.
Using raft to manage sentinel cluster.

support in http://github.com/siddontang/redis-failover


appimage-run: export OWD

documented here: https://docs.appimage.org/packaging-guide/environment-variables.html
Fixes #203330
could you test, @gvegidy ? If you already have installed nix to test your appimage, then it's easy:
git clone https://github.com/NixOS/nixpkgs
cd nixpkgs
nix-shell -p nix-review --run "nix-review pr https://github.com/NixOS/nixpkgs/pull/203598 -p appimage-run"

inside the shell that opens, you have the fixed appimage-run:
appimage-run foo.appImage

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thanks for the instructions how to build the patch.
With the patch my owdtest.AppImage worked, but also the full AppImage I originally wanted to run. So from my side the patch works and fixes https://github.com/NixOS/nixpkgs/issues/203330
Thanks for fixing this so fast.


Setup -> Installation + title updates

Updates the docs to reflect that it's not a "setup" documention but
rather an installation document.
I've also updated the header of architecture.md to reflect the filename.

LGTM :+1:


Script column of schema version table, showing scripts with name trimmed(1001__t.sql, instead of V1001__t.sql)

What version of Flyway are you using?
flyway-commandline-4.0.2.tar.gz (without JRE)
and
flyway-commandline-4.0.2-windows-x64.zip
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
MAVEN
What database are you using (type & version)?
Oracle <IP_ADDRESS>.0
What operating system are you using?
UNIX
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
My folder structure is :
folder 1      : flyway\ddl ; flyway\ddl\procs
files in ddl : V10001__t_t1.sql , V10002__t_t2.sql
file in procs folder : R__proc1.sql
CASE 1 -
On executing migrate command on my local machine using flyway-commandline-4.0.2-windows-x64.zip,  the schema_version table column "SCRIPT" , shows data as :
V10001__t_t1.sql
V10002__t_t2.sql
proc/R__proc1.sql
CASE 2 -
On executing migrate command on our server machine configured using maven, using flyway-commandline-4.0.2.tar.gz (without JRE),  the schema_version table column "SCRIPT" , shows data as :
10001__t_t1.sql
10002__t_t2.sql
roc/R__proc1.sql
What did you expect to see?
For CASE 2 also I expect , the results to be same as in CASE 1.
But somehow, names of scripts(including folder path) are being left trimmed by one character
What did you see instead?
CASE 2

Hmmm... the code is 100% identical for all distributions, so I am afraid you'll need to dig a little deeper to find out what is going on. How do the configurations and the debug output compare?

Config file is same. Debug, I will compare and confirm in some time.

have compared both debugs(commandline windows and commandline tar.gz ).
Both are deploying in same manner..
Example of Repeatable Migration script
_windows:--
DEBUG: Successfully completed migration of schema "SCHEMA1" with repeatable migration log rx
DEBUG: MetaData table "SCHEMA1"."schema_version" successfully updated to reflect changes
tar.gz :--
259	notice	DEBUG: Successfully completed migration of schema "SCHEMA1" with repeatable migration log rx
260	notice	DEBUG: MetaData table "SCHEMA1"."SCHEMA_CODE" successfully updated to reflect changes_

@axelfontaine  Any clue buddy?

I am afraid we'll need more information to be able to find the problem here. Can you post a minimal GIthub repo with instructions to clearly reproduce the issue?

Closing due to lack of response from original reporter

This happened for me too. Check if you have doub '\' in the conf file - flyway.locations.
There should only be a single back slash: ''

@mehta-m  Thanks for response.. I will check.
Because of on restricted networks, I can't simulate the same scenario at home. so can't explain the issue. But it is still happening in our project. The tar.gz file is placed on Unix server and is being called using PUPPET from an internal CD tool.


Shell Scripts - Replacement of Turbot AWS V3 Shell Script

This piece of work with migrate the V3 shell script turbot-aws to V5.
It will use curl and graphql mutations / queries to provide backward compatibility.

@siddharthaturbot Hi, you can add code here: ./api_examples/graphql/clients/shell/turbot-aws
`


Explain where global .csslintrc file should be

You should explain in your readme, where the global .csslintrc file goes. I only figured it out by looking at the source, and a lot of people probably won't do that.

I do agree that it could help some people, but the global .csslintrc file location will differ from system to system and your setup? So should I write the default location on all systems? (linux/macOS/windows)?
THis is not me saying no, but looking for the best way to do this 😄

Can't you just say that it should be saved in the users home directory, because it looks like it's looking in there for the .csslintrc

fixed in #22


ECL-450: Removed returnsJourneyEnabled feature switch and usages

looks good @TonyCOgilvie i'm thinking wait until it's removed from the email template before merging this though as it will cause problems for the email if we merge this before


Payments should reference coinbases being spent.

We noticed in testing v1.1.0 on testnet that input selection via the wallet's constructTx grpc sometimes included other coinbases.  This caused issues down the line in both cases because the included coinbase in the tx became change (confs at 1 now) after publishing the tx and no longer could satisfy the required confirmation constraint of coinbaseMaturity+1. This created a deficit in prevOuts at the required confirmations to process further payments.
To resolve this, payments generated need to reference the coinbase they are spending so that transactions can be constructed with the referenced coinbases instead of relying on constructTx to select inputs for the transaction.

With payments directly referencing the outputs they spend, the payment manager will have to be reworked because each payout transaction will no longer be generating change. Fees will be deducted from the pool fees collected. This means txfeereserve will no longer be needed and will have to be removed, maxtxfeereserve as well. Their corresponding config variables will be deprecated and removed in v1.1.1.

Payment processing requests will also be removed because with the updated payment processing payments will be processed immediately they are spendable.

Resolved by #207.


Reuse Custom Endpoint Settings

Hello,
Apologize in advance if I'm not writing in the right repo, if so, please feel free to redirect me.
Recently I started to work with workbooks, and I'm trying to implement a dashboard that make several calls to ADO rest endpoints, is there any way to share the base config like:

Base url, eg: https://dev.azure.com/ORG/PROJ
Headers, eg: authorization ...
Query Params, eg: api-version ...

across every query, instead of redeclare everything every time?
something like these Grafana data sources can do:

https://grafana.com/docs/plugins/marcusolsson-json-datasource/latest/
https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/

Thanks

@panda-sharp while not the same as grafana, you could declare those things as parameters, and mark them hidden so they don't display in read mode, and then reference the parameters in the configuration of the individual steps

@gardnerjr thanks for your reply, that's what I managed to do meanwhile ... so looks like there is no better way, at least for now :)


Bluetooth: Switch to inclusive terminology from the 5.3 specification

The inclusive naming mappings can be found here:
https://btprodspecificationrefs.blob.core.windows.net/language-mapping/Appropriate_Language_Mapping_Table.pdf
The item will be discussed in the API meeting so seek acceptance for inclusion in 2.7.0.
Areas to be covered:

[x] include/bluetooth (excluding hci.h): #38522
[x] include/bluetooth/hci.h #38605
[x] subsys/bluetooth/host: #38640
[x] subsys/bluetooth/controller: #38687
[x] subsys/bluetooth/mesh #38356
[x] subsys/bluetooth/other #38640
[x] drivers/bluetooth/
[x] samples/bluetooth
[x] tests/bluetooth #38640

CC @jhedberg @joerchan @alwa-nordic @asmk-ot @wopu-ot @kruithofa @Thalley @Vudentz @asbjornsabo @sjanc @andrzej-kaczmarek @KKopyscinski @trond-snekvik @LingaoM @michal-narajowski @ppryga

@carlescufi Is there anything in subsys/bluetooth/audio that would require a change?

API meeting:

The version of the specification that replaces the terms with inclusive ones is 5.3
All Bluetooth subsystems will claim compliance with the 5.3 version of the spec in Zephyr 2.7.0
General consensus is to allow for the change, as long as it only involves replacing the terms and is well documented in the release notes for 2.7.0
Requires TSC approval

@carlescufi Is there anything in subsys/bluetooth/audio that would require a change?

I am not sure about that @Thalley. Can you check?

@carlescufi Is there anything in subsys/bluetooth/audio that would require a change?

I am not sure about that @Thalley. Can you check?

A quick course search reveals nothing. Do we have a list of words that has/should be changed? Should be able to write a fairly quick script to validate.

All done!


Added support for numeric spaces for LocalGridSearcher

Description of changes:
Added support for numeric spaces for LocalGridSearcher
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1448-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1448/1/index.html

Job PR-1448-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1448/2/index.html

Job PR-1448-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1448/4/index.html

Job PR-1448-7 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1448/7/index.html


Integrate previously developed sky subtraction metrics into the pipeline

From Dec'22 quarterly update

Integrate previously developed sky subtraction metrics  into the pipeline for regular automated testing of the    pipeline's performance at LSB levels.

this will be in the form as previously by WP3.7 since not useful to integrate into pipelien itself as previously reported
run-times will also be a big factor in determining the way forward

23/MAR/23

this will not happen in Phase B hence closed


Predicate expression evaluated incorrectly

Parsing this expression:
items[?quantity == `2.0`]

produces:
[@0,0:4='items',<NAME>,1:0]
[@1,5:6='[?',<'[?'>,1:5]
[@2,7:14='quantity',<NAME>,1:7]
[@3,16:17='==',<BINARY_OP>,1:16]
[@4,19:19='`',<'`'>,1:19]
[@5,20:22='2.0',<NUMBER>,1:20]
[@6,23:23='`',<'`'>,1:23]
[@7,24:24=']',<']'>,1:24]
[@8,25:24='<EOF>',<EOF>,1:25]
line 1:16 missing ']' at '=='
line 1:20 mismatched input '2.0' expecting {'[', '{', JSON_CONSTANT, STRING, REAL_OR_EXPONENT_NUMBER, SIGNED_INT}
line 1:24 extraneous input ']' expecting <EOF>

JMESPath produces:
[@0,0:4='items',<NAME>,1:0]
[@1,5:6='[?',<'[?'>,1:5]
[@2,7:14='quantity',<NAME>,1:7]
[@3,16:17='==',<COMPARATOR>,1:16]
[@4,19:19='`',<'`'>,1:19]
[@5,20:22='2.0',<REAL_OR_EXPONENT_NUMBER>,1:20]
[@6,23:23='`',<'`'>,1:23]
[@7,24:24=']',<']'>,1:24]
[@8,25:24='<EOF>',<EOF>,1:25]
(jmesPathExpression (pathExpression (pathExpression (identifier items)) (bracketSpecifier [? (pathExpression (pathExpression (identifier quantity)) == (pathExpression (literal ` (jsonValue 2.0) `))) ])) <EOF>)

Expected Behaviour
Actual Behaviour
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

Resolved with refactoring.


Fix token extraction

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 13 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 80.311%

Totals

Change from base Build<PHONE_NUMBER>:
0.6%

Covered Lines:
515

Relevant Lines:
635

💛  - Coveralls


Suggestion. use branches to avoid master conflicts, cmd+s / ctrl+s to push

Just leaving a suggestion.
But I use obsidian on two computers and often run into merge conflicts.
Just a friendly suggestion but to be able to create branches directly from obsidian instead of terminal.
Also to have a save function to auto backup.
Forgive me if these features are there, and I haven't been able to see it.

I'm unsure how separate branches help you to avoid merge conflicts. I don't suggest you to set the backup/commit/push command to CTRL + S, but you should be able to do it via default Obsidian hotkeys settings. Then this issue is only about managing branches from the plugin. This is tracked in #132.

Duplicate of #132


Safari Technology Preview 142 enabled Container Queries by default

https://developer.apple.com/safari/technology-preview/release-notes/

Thanks!


Allow localhost enabling to be a parameter

Perhaps we should add a parameter that allows chains to enable or disable localhost on their chain
This would then be checked in the localhost verification case to ensure it is enabled. Localhost verification should fail if the parameter is set to false

There already is a parameter, clsoing

One possible approach:

add a enable/disable field to client state
add msg to change this value (gov v1 msg, authority is only gov module)
update localhost client state upon execution
use client state field in Status

I think in order to do gov v1 message execution it will incur an API breaking change to the ibc core NewKeeper() function.
SDK modules which have migrated to use self managed params now take the additional arg to NewKeeper() functions: authority and store it as a field on the keeper.
See here and below where the additional authority arg is added

Could we preemptively get the API breaking change in v7? Or does it feel too late in the cycle for that?

Sounds good to me. I think if its just changing the core NewKeeper function to accept an additional arg and store it as a field on the keeper then its totally fine

closing this as #3196 has been merged into the feature branch.


No mention of required permissions

It would be helpful to have this article include a note about what permissions are required in order to change the authentication mode.

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

ID: 3e9b632d-7e6d-1434-cc6b-9aa77d37f41a
Version Independent ID: 3689727c-e685-1503-fd9e-365aa15c33fa
Content: Change Server Authentication Mode - SQL Server
Content Source: docs/database-engine/configure-windows/change-server-authentication-mode.md
Product: sql
Technology: configuration
GitHub Login: @markingmyname
Microsoft Alias: maghan

@nvdacsheets -- Charley, thank you for your feedback.  Please consider these resources:

DBA Stack Exchange
Stack Overflow

@markingmyname -- Mark, please look into this issue.

Hi, @nvdacsheets,
Thank you for your feedback! We will investigate and get back to you with the relevant info.
@VanMSFT for awareness

Hi, @nvdacsheets,
Sysadmins and CONTROL SERVER can change the authentication mode.
We will update the article to reflect this info.
Expect the changes to be live by early next week.
thank you.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue. To see what the community is wanting, please visit the SQL Server User Feedback site.


KeyError: 'trans'

when I ues my own npz file, it got wrongs as follows, can you tell me why?
in run
self._target(*self._args, **self._kwargs)
File "server.py", line 26, in tcplink
data = getData()
File "server.py", line 16, in getData
temp = np.append(a[key][0]['poses'], a[key][0]['trans'])
KeyError: 'trans'

It looks like the key 'trans' is missing from your npz dict.

I just run this to get the npz file, is there anthing I should do?

ah, I found the line 83was '#'


fix(dependencies): upgrade to next majors

Current dependencies on/for this PR:

main

PR #118   👈

This comment was auto-generated by Graphite.


Update deploy scripts to use Node.js 8.2.1

Landed in 4c20f12

Landed in 0c4d79a

Landed in 0c4d79a


not correct  number of installed  extensions after settings sync

VSCode v1.78, in my case:

After settings sync ,  number of installed  extensions is 72.
restart vscode , the number changes to 83.

Not sure if this information is helpful to reproduce. Can you please provide steps to reproduce or provide a gif/video demonstrating what is not working.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


remove unreachable clause

This clause is sent by the "tail" node on the ring to the "head" node. However, by the time this message is sent, the "tail" node has long gone. Thus, this clause is never matched.
Side note:  send(pid, "a message")  doesn't fail even if the pid is no longer alive.

Yikes, sorry I missed this PR!

No worries. Thanks for merging it!


Normalize before using LogisticRegression

Hi,
as far as I can see is that setfit applies LogisticRegression on top of the output of the sentence transformer model.
See here:
https://github.com/huggingface/setfit/blob/7735e8e3b208edb8dfb549beb16e585453c5f44e/src/setfit/modeling.py#L49-L55
The problem I see is that the output is not normalized by default. Since we use Cosine Sim. to compare embeddings the
length of the vector does not matter. When you do Cosine Sim. this is ok but it is IMO not ok when you apply LogisticRegression.
IMO the embeddings should be normalized to unit length before LogisticRegression is applied. That would be done by passing
normalize_embeddings=True to the encode function. See here:
https://github.com/UKPLab/sentence-transformers/blob/0422a5e07a5a998948721dea435235b342a9f610/sentence_transformers/SentenceTransformer.py#L111-L118
What do you think? I can provide a PR if wanted.

That explains those messages i'm getting : when using fit and trying to predict :
_logistic.py:444: ConvergenceWarning: lbfgs failed to converge (status=1):
STOP: TOTAL NO. of ITERATIONS REACHED LIMIT.
Increase the number of iterations (max_iter) or scale the data as shown in:
https://scikit-learn.org/stable/modules/preprocessing.html
Please also refer to the documentation for alternative solver options:
https://scikit-learn.org/stable/modules/linear_model.html#logistic-regression
n_iter_i = _check_optimize_result(
`df_ri_manclassif['predicted']= model(df_ri_manclassif['global_text'].to_list())
this is the message : ---------------------------------------------------------------------------
NotFittedError Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_7856/2981536964.py in
----> 1 df_ri_manclassif['predicted']= model(df_ri_manclassif['global_text'].to_list())
c:\Users\doub2420\AppData\Local\Programs\Python\Python39\lib\site-packages\setfit\modeling.py in call(self, inputs)
60 def call(self, inputs):
61 embeddings = self.model_body.encode(inputs)
---> 62 return self.model_head.predict(embeddings)
63
64 def _save_pretrained(self, save_directory):
c:\Users\doub2420\AppData\Local\Programs\Python\Python39\lib\site-packages\sklearn\linear_model_base.py in predict(self, X)
445 Vector containing the class labels for each sample.
446 """
--> 447 scores = self.decision_function(X)
448 if len(scores.shape) == 1:
449 indices = (scores > 0).astype(int)
c:\Users\doub2420\AppData\Local\Programs\Python\Python39\lib\site-packages\sklearn\linear_model_base.py in decision_function(self, X)
425 this class would be predicted.
426 """
--> 427 check_is_fitted(self)
428
429 X = self._validate_data(X, accept_sparse="csr", reset=False)
...
-> 1345 raise NotFittedError(msg % {"name": type(estimator).name})
1346
1347`

Well, I have a branch where I can enable normalize.
I did some tests with default settings, a normal BERT model (no pretrained sentence embedding model) and optuna.
Letting optuna optimize also the normalize parameter (True or False) shows that it is definitly better when NOT doing it.
This is strange since it means that the length of the vector seems to encode important information...

@lewtun what is your opinion on this? Do you have more insights?

Seems like SetFit already has something like this but only hidden in a script and not the main package...
https://github.com/huggingface/setfit/blob/43dbaf1a914a08ff8ef8ec836ddd51586d7881bb/scripts/setfit/run_fewshot.py#L118

this is implemented via #177 - closing this


Allow specifying a Proxy for the HTTP connection

Is your feature request related to a problem? Please describe.
My app needs to be able to fetch OG tags over Tor.
Describe the solution you'd like
Ability to specify a Proxy when parsing from URL.
Describe alternatives you've considered
And/or would also be nice to be able to parse from a String of a URL fetched some other way.

Thanks @singpolyma
Can you explain what you mean by the alternative you have mentioned?

If I could do the http fetch with my existing http client and feed it to the OpenGraphParser as a String or File then it wouldn't matter how the http fetcher worked.

right.  I don't prefer that option necessarily, but it might be a good option to have for other reasons, and it would happen to work here since I of course have an http client in my app already.

New update : 2.5.6


Check diff on PR, and check the entire files when other builds

[ ] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[x] Tests are included and/or updated for code changes.
[x] Updates to CHANGELOG.md are included.
[x] MIT license headers are included in each file.

/azp run Azure.azure-sdk-for-go

/check-enforcer evaluate