Set-PSBreakpoint allows you to set the same breakpoint again, and again, and again

The Set-PSBreakpoint command allows you to set a breakpoint multiple times. Most users never encounter this because if they debug and use breakpoints, they do so from Visual Studio Code or PowerShell ISE. For users who use the command line and set breakpoints that way, this behavior leads to additional breakpoints being created that are not necessary and do not add any value to their debugging experience.
Steps to reproduce
Set-PSBreakpoint -Command Get-Process
Set-PSBreakpoint -Command Get-Process
Set-PSBreakpoint -Command Get-Process

Expected behavior
  ID Script                            Line Command                           Variable                          Action
  -- ------                            ---- -------                           --------                          ------
   0                                        Get-Process

Actual behavior
  ID Script                            Line Command                           Variable                          Action
  -- ------                            ---- -------                           --------                          ------
   0                                        Get-Process

  ID Script                            Line Command                           Variable                          Action
  -- ------                            ---- -------                           --------                          ------
   1                                        Get-Process

  ID Script                            Line Command                           Variable                          Action
  -- ------                            ---- -------                           --------                          ------
   2                                        Get-Process

Environment data
Name                           Value
----                           -----
PSVersion                      6.2.1
PSEdition                      Core
GitCommitId                    6.2.1
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Desired outcome
I would like to change this behavior such that Set-PSBreakpoint does not create duplicates, by having it look at existing breakpoints when a breakpoint is set. If an exact match is found, that breakpoint is returned to the caller. Otherwise, the new breakpoint is set and returned to the caller. There is no value in allowing multiple breakpoints that are 100% identical to be set in a debugger. In fact, graphical debuggers don't allow you to do this, so the command line shouldn't either.

@KirkMunro Don't forget about actions. Each breakpoint object can have it's own action q.e.d multiple breakpoints are necessary.

That wasn't my point. My point was that if you're setting a breakpoint that is already set the exact same way (same line/column/command/variable/script/action), then that should just give you back the breakpoint you're setting. When working from the command line using PSReadline's Ctrl+R or just up arrow to set-breakpoint commands between sessions, it's easy to set a single breakpoint twice the exact same way. That's what I want to prevent.

Yeah, I'd expect what you're talking about to be a simple idempotent operation. Looks like the impl reflects the desire to have multiple breakpoints with different actions/commands/variable but nobody bothered to check if those actions/command/variable are actually different.  BTW, in your example with Get-Process, it doesn't actually break three times, does it?

In my example it breaks once, but shows three triggering breakpoints that only differ by their ID when it does.


How to show directions between two markers or points on Map

this is either a feature request or an inquiry about a feature
I would like to show my user on a React Native application the directions of a ride between two markers like in google maps,
it would also be super helpful if I can show the estimated distance in KM / time in minutes or hours
is this available with this package or is there another way to do it?

Hello, you can use : https://github.com/bramus/react-native-maps-directions

thank you a lot this was really super helpful

Hi @AhmedSarhan. I'm going to close this for now, but feel free to open a new issue following the feature request template if this is still relevant :)


Get rid of cloud-user-sa in openscapes hubs

Before we got https://infrastructure.2i2c.org/en/latest/howto/features/cloud-access.html and AWS IRSA for providing access to S3 buckets to users, we used a cloud-user-sa created by eksctl to make this happen:
https://github.com/2i2c-org/infrastructure/blob/bf6ae45b97d27cf303c68379c35adf9d493097cf/eksctl/carbonplan.jsonnet#L52 and https://github.com/2i2c-org/infrastructure/blob/master/config/clusters/carbonplan/common.values.yaml#L35.
We should migrate both carbonplan and openscapes away from this eksctl provisioned service account towards following the AWS docs in https://infrastructure.2i2c.org/en/latest/howto/features/cloud-access.html.

This is gone


prevent artificial delays due to ridiculously low client attempts

per https://github.com/kubernetes/kubernetes/pull/22281
I can't test this in my travis anymore, but locally I see throttling all the time.

lol, it does appear to make
E0411 20:42:09.195008    4688 controller_instance.go:1205] ServiceInstance "test-namespace/test-instance": Failed to update status: Operation cannot be fulfilled on serviceinstances.servicecatalog.k8s.io "test-instance": the object has been modified; please apply your changes to the latest version and try again

worse. Maybe I'll fix that next.

LGTM.


Added support for large Rectangles in OrientedBoundingBox.fromRectangle

There have been reports of 3D tiles that use TileBoundingRegion disappearing when viewing from a horizon angle. This is because the root tile generates a broken OrientedBoundingBox when the Rectangle's width is greater than half the ellipsoid. The terrain system doesn't have this problem because it handles this edge case and generates a BoundingSphere instead.
In this PR OrientedBoundingBox.fromRectangle has been made to work with larger rectangles. The approach is different than small rectangles which orient the OBB around the rectangle's center normal. I tried doing it this way for large rectangles but it produced very poorly fitted, albeit correct OBBs. The final approach ignores the latitude when calculating the OBBs orientation.
With this fix, all of the special case code is gone. I did a good amount of testing but this change impacts a lot of core systems so more eyes on it the better.
Fixes #4483
Sandcastle
Examples:

3D tile before (incorrectly culled):

3D tile after:

@loshjawrence
@lilleyse
@jasonbeverage

Thanks for the pull request @IanLilleyT!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Very cool, this will help tremendously with global datasets!

@IanLilleyT could this fix #4483?

Just tested and it does not fix it, but I'm looking into it

@hpinkos  Looks like GroundPrimitive swapped the order of the minimumHeight and maximumHeight parameters to OrientedBoundingBox.fromRectangle. My newest commit fixes it.
Sandcastle from #4483

GroundPrimitive swapped the order of the minimumHeight and maximumHeight parameters

:woman_facepalming:
Nice catch @IanLilleyT :laughing:

@lilleyse fixed some bugs, ready for review

Looks good based on my checks

The number of render tiles is the same between this branch and master. I tested all the different terrain providers and 3D Tiles.
The OBBs look good with rectangles spanning from positive longitude to negative longitude (crossing IDL)
Confirmed that the Alaska tileset above and another tileset that had this problem are now working in 3D.

The only thing to fix now is there's a crash when switching to 2D or CV with the Alasaka tileset.

@lilleyse did you check rectangles at the poles?

@hpinkos yes I forgot to mention that, I checked as many extreme cases as I could in the Sandcastle example including poles.
This is how I ended up hitting this bug, which also happens in master: https://github.com/AnalyticalGraphicsInc/cesium/issues/8478

@lilleyse That crash you posted is a different problem which is fixed here: https://github.com/AnalyticalGraphicsInc/cesium/pull/8482/

@IanLilleyT cool, I'll check that out next


GetTags command

GetTags method to get the current tags from a file RESTObjectGETtagging
The return type is Vec<String, String> (a vector of tagname->tagvalue tuples) and the operation result code S3Result<(Vec<(String, String)>, u32)>.
XML 'parsing' (for this simple purpose) was done using a simple regular expression (r"<Key>([\s|\S]+)</Key><Value>([\s|\S]+)</Value>").
Added regex external crate .

This change is

Published version 0.12.1


Rust/WASM in Fluid

Description
This PR introduces a pattern for adding Rust WASM modules to the Fluid repo. See the README in the root WASM directory to learn more!
Reviewer Guidance
These are trivial examples (arithmetic) to demonstrate repo patterns and will be replaced by useful code later. We're looking for feedback on the repo patterns and tooling to see what should/could be improved.

Is this built at all as part of the client release group or otherwise? The rust compilation doesn't seem to be automated in this PR. I assume that's expected. It is interesting to think about how we might incorporate non-TS builds into the CI pipelines.

Some other questions to consider:

Is there any value in keeping any of the three categories of project out of the client release group? My instinct is no, that they should all be a part of the client release group and pipeline, but I could also imagine keeping the idiomatic Rust pieces separate given that the build pipeline will need to be different.
Naming convention seems useful for these projects. Having wasm in the name helps, but I don't understand the difference between client-wasm and fluid-wasm from a naming perspective. Using "glue" in the names for the glue crates isn't terrible, either, but I guess those will be visible to consumers so it may be a bad idea.
What 'build scripts' would developers expect to have for the rust projects? build and test are obvious, but maybe format should be there too. Could be a good opportunity to whittle down our list of "common scripts that all projects should have."


Allow MemGPT to access the web?

Is your feature request related to a problem? Please describe.
This would be useful so that MemGPT could have knowledge to currents events as well as add what they learned to their archive.
Describe the solution you'd like
It could make http requests on google or any search engines then grab the first few results as reference.

Closing b/c HTTP requests are part of the included memgpt_extras preset


Allow the content attribute in logstash::patternfile besides source

would like to supply my grok pattern via strings, and not via files on the node or master. Would it be possible to add this option?

+1


Next release?

@niklasvh any news on when the next release will be available and when it'll be "production" ready and no longer beta?

More info at #1167


[issue-252] Upgrades and changes to build with jdk 11

Signed-off-by: Flavio Junqueira (fpj<EMAIL_ADDRESS>Change log description

Adds source and target compatibility with Java 8 to work with the shadow plugin
Upgrades lombok to 18.4 to fix compilation error
Updates checkstyle configuration to fix build errors

Purpose of the change
Fixes #252
What the code does
There is no code change, only one upgrade and a few configuration changes. Specifically:
1- Upgrades lombok to fix a lombok error when compiling.
2- Adds source and target compatibility to avoid an error when running the shadow plugin
3- Changes the configuration of checkstyle according to the instructions here:
https://github.com/gradle/gradle/issues/8286
How to verify it
Build must succeed.

Looks good to me


ListView scroll resets scroll position of child items (CachedImage inside horizontal scrollview)

Good Day
First of all, great library, can't live without it. Here is the issue.
Am using Xamarin.Forms. I have a ListView. Every item in ListView is a horizontal scroll view. Every item in the scroll view displays FFImageLoading.CachedImage with couple of labels with very short text. If the ListView is scrolled up or down, the last scroll position of certain ListView items (which is a horizontal scrollview) is reset. The source of the CachedImage is base64string coming from web api.
Here is the catch, if I do not display CachedImage and only display labels, everything works fine.
Following is the sample XAML I am using:
<ffimageloading:CachedImage Source="{Binding Base64Logo}" HeightRequest="70" WidthRequest="70" HorizontalOptions="Center"/>
Version Information:
Xamarin Froms: <IP_ADDRESS>82
FFImageLoading Library: 2.2.5

@mofadevs Thanks, I'll need some details first:

What platform?
Did you try to update to the latest prerelease nuget?

the last scroll position of certain ListView items (which is a horizontal scrollview) is reset

Could you write more info?


zipfile.BadZipFile: File is not a zip file

when I try to install pyzed from the http url, I got the following error:
(base) qiulin@qiulin-G3-3579:~$ pip3 install https://download.stereolabs.com/whl/cu90/pyzed-2.8-cp36-cp36m-linux_x86_64.whl
Collecting pyzed==2.8 from https://download.stereolabs.com/whl/cu90/pyzed-2.8-cp36-cp36m-linux_x86_64.whl
Downloading https://download.stereolabs.com/whl/cu90/pyzed-2.8-cp36-cp36m-linux_x86_64.whl
- 51kB 41kB/s
ERROR: Exception:
Traceback (most recent call last):
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/cli/base_command.py", line 188, in main
status = self.run(options, args)
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 345, in run
resolver.resolve(requirement_set)
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/legacy_resolve.py", line 196, in resolve
self._resolve_one(requirement_set, req)
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/legacy_resolve.py", line 359, in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/legacy_resolve.py", line 307, in _get_abstract_dist_for
self.require_hashes
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/operations/prepare.py", line 199, in prepare_linked_requirement
progress_bar=self.progress_bar
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/download.py", line 1050, in unpack_url
progress_bar=progress_bar
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/download.py", line 914, in unpack_http_url
unpack_file(from_path, location, content_type, link)
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/utils/misc.py", line 738, in unpack_file
flatten=not filename.endswith('.whl')
File "/home/qiulin/anaconda3/lib/python3.6/site-packages/pip/_internal/utils/misc.py", line 615, in unzip_file
zip = zipfile.ZipFile(zipfp, allowZip64=True)
File "/home/qiulin/anaconda3/lib/python3.6/zipfile.py", line 1108, in init
self._RealGetContents()
File "/home/qiulin/anaconda3/lib/python3.6/zipfile.py", line 1175, in _RealGetContents
raise BadZipFile("File is not a zip file")
zipfile.BadZipFile: File is not a zip file
I tried to install in the following way:
pip3 install --no-cache-dir https://download.stereolabs.com/whl/cu90/pyzed-2.8-cp36-cp36m-linux_x86_64.whl
but it doesn't work for me. Could anyone give me some help on this? Thanks!

The package for Python 3.6, CUDA 9.0 doesn't exist yet, the page is therefore redirected into the https://www.stereolabs.com webpage. Which means pip downloaded an HTML page and complains that it can't install it.
The support for the packaged version is currently quite limited and will be extended in the future.
For now, you can check if the package is available by simply trying to download it manually, by clicking the link and see if the redirection appears.
In your case, you will have to follow the instruction in the README to install the pyzed package.


linting errors hopefully

Signed-off-by: Nicole Lefebvre<EMAIL_ADDRESS>Contributes to # (add issue number here. i.e. #302)
What did you do?
Why did you do it?
How have you tested it?
Were docs updated if needed?

[ ] No
[ ] Yes
[ ] N/A

Type of change

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

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new console logs
[ ] Fixes entire issue
[ ] Partial fix for issue

For testing purposes only.


Build the HTML for the signup template

Done: https://github.com/baskager/redesign-minor-web-dev/pull/19


(#10) Update to the public recipe package

Description Of Changes

Updated to the public Chocolatey.Cake.Recipe package
Removed the source configurations as we were setting the same
as the defaults.
Included some readme updates, that thing hasn't been updated in eons.

Motivation and Context

We forgot to come back and update the recipe package used in the previous PR.
There were some README changes needed, that file was very old and no longer useful to anyone.

Testing

Build script run to ensure all tests are still passing and new build recipe functions properly.

Change Types Made

[ ] Bug fix (non-breaking change)
[x] Feature / Enhancement (non-breaking change)
[ ] Breaking change (fix or feature that could cause existing functionality to change)

Related Issue
#10
Change Checklist

[ ] Requires a change to the documentation
[x] Documentation has been updated
[ ] Tests to cover my changes, have been added
[x] All new and existing tests passed.

This looks good to me, and build on the Dev server.
It did use the branch name as part of the version number, though I imagine this will be something that won't be accurately reflected until we're building from master (@gep13?)

@vexx32 thanks for getting this updated, and thanks to @Windos for the review!


added third optislang integration scenario

@seanpearsonuk @mkundu1 I've included the addition of the optislang doe creation test in the same script as the original integration test in this PR. I will rerun 23.1 tests and coverage once Issue #124 is resolved. Please let me know if you have any concerns.


Terminal content goes missing when resizing (powershell/conpty)

Environment
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Any other software?

Steps to reproduce
This bug is identical to what VSCode had a few months ago: https://github.com/microsoft/vscode/issues/78634

Open Terminal
Type some PowerShell command
Get output
Resize terminal and notice how half of the output is missing

Expected behavior
No cutouts on resize
Actual behavior

This is a bunch of issues that are all largely being tracked by #4200. Thanks!
/dup #4200


adding behavior_tree package

Hello,
I would like to add the behavior_tree package.
Thank you
Michele

Just an unrelated question: where are the build status badges in your README file coming from?

I have manually copied from shield.io after testing them. Is there an automatic way to do that?

If the code is being built on our Jenkins farm you can use the badges from there. Please see the wiki which already makes use of that: http://wiki.ros.org/roscpp (click on the sidebar on "Jenkins jobs")

There's an Embeddable Build Status Icon provided by our jenkins instance for each job.
It provides documentation for how to embed it in different places such as: http://build.ros.org/view/Jsrc_uT/job/Jsrc_uT__roscpp__ubuntu_trusty__source/badge/

Thank you! I will change that!
Michele


Add host functions for returning contract ids

What
Resolves https://github.com/stellar/rs-soroban-env/issues/538
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Looks like this PR has some merge conflicts that need fixing before it can be merged.

Merged with latest env changes and fixed conflicts.
Aldo did a drive-by clean up on one host function returning contract id to use AddressObject, which should close https://github.com/stellar/rs-soroban-env/issues/818 too.
@leighmcculloch I think it's ready to be merged.


Can´t install snippets

Issue Type: Bug
why i can`t install snippets in visual studio code
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:38:57.434Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.90GB (3.81GB free)

Process Argv
C:\Users\antho\AppData\Local\Programs\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions: none

How are you trying to install snippets?

As i always had done
[image: 3.jpg]
[image: snippest visual studio code.png]
El mar., 4 sept. 2018 a las 20:39, Matt Bierner<EMAIL_ADDRESS>escribió:

How are you trying to install snippets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/57926#issuecomment-418580799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AoS8RENe0t-kqA80EJ_MOHauYm3wv8oRks5uXzlogaJpZM4WaEuU
.

How is that?


Home Assistant MQTT Config Lost (Awkward Retain Situation...)

Is your feature request related to a problem? Please describe.
I've been having trouble lately where Home Assistant loses the MQTT configuration from ecowitt2mqtt. The whole thing is a little frustrating (why can't HA just persist it? is there a workaround?), but it's not ecowitt2mqtt's fault.
The simple answer to my woes is to set the retain flag and let my MQTT broker handle the rest.
The issue is that I'm using RabbitMQ as my MQTT broker (for reasons), and RabbitMQ doesn't really handle retained messages in clustered environments. There are workarounds, but nothing I'm too keen to dive into right this moment.
Describe the solution you'd like
I have a couple ideas that aren't too outlandish, I believe.

I've heard that it's good practice for MQTT publishers to react to homeassistant/status by republishing config, but I don't actually know if that would solve my problems.
For a more broadly-applicable solution, what if there was an endpoint for ecowitt2mqtt that forced it to republish? Then I could even go nuts and set up an automation that automatically called it if a sensor went unavailable for some amount of time.

Additional context
I'm very open to recommendations too. I'm sure I don't know everything about RabbitMQ, MQTT, ecowitt2mqtt, nor indeed Home Assistant. If anyone has ideas of how I can work around these issues, I'm all ears. The most correct solution would be for me to set up RabbitMQ to share retained messages across the cluster, but I see these workarounds as being independently valuable additions to ecowitt2mqtt, so I figured I'd pitch them.

Thanks for your patience.

For a more broadly-applicable solution, what if there was an endpoint for ecowitt2mqtt that forced it to republish? Then I could even go nuts and set up an automation that automatically called it if a sensor went unavailable for some amount of time.

Is the idea here that this new endpoint would simply republish whatever the most recently received payload was?


CMake Error at CMakeLists.txt:155 (add_subdirectory)

Steps to reproduce the issue:

git clone ...
...
cmake .. -DRAIBLOCKS_GUI=ON -DBOOST_ROOT=/usr/local

Describe the results you received:
CMake Error at CMakeLists.txt:155 (add_subdirectory):
add_subdirectory given source "miniupnp/miniupnpc" which is not an existing
directory.
the miniupnp directory in root of git repo is empty, there is no miniupnp in build directory
Describe the results you expected:
No error
cmake version 3.9.1 on fedora 25.

In build directory
git submodule init
git submodule update

Or use git clone --recursive
https://github.com/nanocurrency/raiblocks/wiki/Build-rai_node-samples#building-rai_node

Oh right, I forgot about --recursive. After some googling there doesn't seem to be a way in cmake to detect whether add_subdirectory failed to print a more useful error. But some kind of check that submodules have been cloned would be nice.


Self import issue

Somehow in the mock, moq generated import that import package itself
So after the second generate command I've got:
couldn't load source package: -: import cycle not allowed: import stack: [github.com/.../api github.com/.../api] (and 2 more errors)

An Interface used Response type as a returned value, and it's generated in mock as api.Response.
If I remove import by hand and remove api. prefix from the type it works.

It happens because of -pkg something parameter - without it, it works well


Backend: Endpoint to update delivery info for user - POST api/users/{user_id}

User story
Who: As a developer
What: I want to be able to update delivery info for user
Why: so that we can use form to update delivery info
Acceptance criteria
The endpoint needs to return a result that allows user to update delivery info through the form marked red below:

Implementation details

Create the POST endpoint for 'api/users/{user_id}'

Check the README file here https://github.com/HackYourFuture-CPH/fp-class18/#-working-with-api-documentation---swagger  and this article should also help you with that https://blog.logrocket.com/documenting-your-express-api-with-swagger/

Hi @Jul-S . I think that issue need to be PUT method. Because the purpose of this part is to update the user address. from database

Hey @semih1239 i think we need POST user anyway to add new user to our DB, maybe you can create it

Hey @semih1239 i think we need POST user anyway to add new user to our DB, maybe you can create it

Yes @Jul-S . You are right. I create an issue for it


Add ability to monitor Intel and amd gpus

This program has the ability to get stats on a nvidia gpu but it not Intel or amd gpus. It would be ideal if you could get statistics on other gpus.

https://github.com/SlyFabi/WSysMon/commit/7bf1293b589cd27407a255bbde38954c869ce80f should add support for it. If you have an Intel or AMD GPU it would be really helpful if you could test it.

I tested https://github.com/SlyFabi/WSysMon/commit/7bf1293b589cd27407a255bbde38954c869ce80f on AMD Ryzen 7 PRO 4750G with Radeon Graphics. It does show GPU usage graph on Performance tab. However the 'Speed' and 'Temperature' values are not populated. Also it does not populate the 'GPU Memory' column on Processes tab.

Same here with an AMD RX6600

Also, I just noticed the weird Video memory report -> 1GiB of 9GiB , when my card have 8 GiB


RTL first draft with images

@abhiShandy Here's a starting chapter for RTL.
Please review and critique.

Part of #3

Thanks for correcting the wrong image. Things have been so hectic here at home the past few weeks that I'm getting sloppy in my work.


MQTT disconnect loop if the device name contains '+' or '#' characters

Description
When the devices.conf contains a device name with characters not legal in a Mqtt topic name, e.g. name: 'T2 candle 5W RGB+CW' -> upon first attempt of publishing data to device's topic, the script enters endless reconnect loop it can not recover from.
Broker-side (Mosquitto) this is seen as a connection-->socket error-->connection-->...
Notes:

This happens when using either '+' or '#' in the device name, though if a '/' is used in the name - it also gets passed into Mqtt, creating unnecessary subtopics.
The name T2 candle 5W RGB+CW is a real-world default device name of a lightbulb I have (generated by Tuya app). It was copy-pasted from tuya-cli wizard

To Reproduce
Originally observed when using Mosquitto as a broker (did not check behavior of other brokers)

Edit devices.json and put a device with a name containing either a '+' or a # - e.g.  name: 'T2 candle 5W RGB+CW'
Run DEBUG=tuya-mqtt:* node tuya-mqtt.js
Observe (logs) that the MQTT connection is established first, but the moment there is an attempt to publish anything on the device's channel (technically: when [devices/tuya-device.js::626] this.mqttClient.publish(topic, message, { qos: 1 }) is hit) - the script enters an endless reconnect loop, with 'reconnect' event firing every second.
Effectively - no data gets published to the MQTT server

Expected behavior

Device name should be canonized, not to include any of # + /
It might suffice to extend the filter here and update the readme (unfortunately don't have time today, to submit a PR for this myself, though it should be fairly trivial)
Additionally - If such class of errors happens - logging should be expanded to indicate the origin (hopefully mqtt module allows for catching these errors). While it seems trivial now, without looking at source code it was impossible for me to figure out what is happening.

System info/logs

Click to expand!

OS: Ubuntu 20.04.1 LTS, ARM

MQTT Broker: mosquitto  1.6.9-1 (MQTT version 5.0/3.1.1/3.1 compatible message broker)

Packages:
$>npm list --depth=0
<EMAIL_ADDRESS>~/tuya-mqtt
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Log exceprt (from DEBUG=tuya-mqtt:* node tuya-mqtt.js - not including output of DEBUG=* as it is massive... and frankly does not help too much other than explicitly showing when the disconnect happens :) )

tuya-mqtt:info Connection established to MQTT server +0ms
tuya-mqtt:tuyapi Search for device id 00000000deadbeef0000 +0ms
tuya-mqtt:tuyapi Found device id 00000000deadbeef0000 +9ms
tuya-mqtt:tuyapi Received JSON data from device 00000000deadbeef0000 ->
(... device communication omitted for brevity ...)
tuya-mqtt:discovery Home Assistant config topic: homeassistant/light/00000000deadbeef0000/config +0ms
tuya-mqtt:discovery { name: 'T2 candle 5W RGB+CW',
tuya-mqtt:discovery   state_topic: 'tuya/t2_candle_5w_rgb+cw/state',
(... cut ...)
tuya-mqtt:discovery   max_mireds: 400 } +2ms
tuya-mqtt:info Unable to connect to MQTT server +2s
tuya-mqtt:tuyapi Received JSON data from device 00000000deadbeef0000 -> {"20":true,"21":"white" ...
(... a few of these follow ...)
tuya-mqtt:state tuya/t2_candle_5w_rgb+cw/state ON +0ms
(... rest of tuya-mqtt:state omitted ...)
tuya-mqtt:info Unable to connect to MQTT server +1s
tuya-mqtt:info Unable to connect to MQTT server +1s
tuya-mqtt:info Unable to connect to MQTT server +1s
tuya-mqtt:info Unable to connect to MQTT server +1s
tuya-mqtt:info Unable to connect to MQTT server +1s
tuya-mqtt:info Unable to connect to MQTT server +1s
(...)

From /var/log/mosquitto/mosquitto.log:

1604644221: New connection from <IP_ADDRESS> on port 1883.
1604644221: New client connected from <IP_ADDRESS> as mqttjs_4ca70238 (p2, c1, k60).
1604644221: Socket error on client mqttjs_4ca70238, disconnecting.
1604644222: New connection from <IP_ADDRESS> on port 1883.
1604644222: New client connected from <IP_ADDRESS> as mqttjs_4ca70238 (p2, c1, k60).
1604644222: Socket error on client mqttjs_4ca70238, disconnecting.
1604644223: New connection from <IP_ADDRESS> on port 1883.
1604644223: New client connected from <IP_ADDRESS> as mqttjs_4ca70238 (p2, c1, k60).
1604644223: Socket error on client mqttjs_4ca70238, disconnecting.
1604644224: New connection from <IP_ADDRESS> on port 1883.
1604644224: New client connected from <IP_ADDRESS> as mqttjs_4ca70238 (p2, c1, k60).
1604644224: Socket error on client mqttjs_4ca70238, disconnecting.
(...)

Thanks for the report.  I'll try to at least update the docs to tell people not to use names with + or # in them for now and maybe fix the filter.
However, regarding point #2, while you are correct that it might be nice to log for such things, there's probably 100's of those types of cases in the code where it would be nice to log some stuff but where the current logging is insufficient, however, I don't have a lot of time to maintain this project and adding usefl logging to cover all failure cases is a time consuming task, I'll probably just try to implement the minimal fix for this and move on, but PR requests are welcome.

Thanks @tsightler.
I fully agree the logging aspect is a nice to have (and this particular issue is unlikely to be the only one, or the important one) In fact, I just meant to highlight this as an 'area', in case there are future refactorings in this region. Consider it more of a subjective observation than anything else - i.e. when this classes of issues happen... they are not so easy to trace (*at least for me) using existing logs. It took me a good 2-3 hours to figure out and I was close to attaching a debugger, in fact :). But then again, I am not using MQTT daily, so I guess for someone seasoned with it it might have been a breeze...

Re this:

I'll try to at least update the docs to tell people not to use names with + or # in them for now and maybe fix the filter.

Consider cautioning users about / in the name as well. While it does work... it creates unnecessary subtopics, so I could envision it breaking some more elaborate usages(?)

Yeah, my current thought is just to filter out all invalid characters for topic names, but the main question is do I replace them with underscores or just filter them out completely.  I'm not sure which is best, but I'm thinking completely remove them.  I guess it probably doesn't matter too much as long as I document it.
I'm going to test to see if I can trap the reason for disconnect from MQTT and log that.  I have a small bundle of minor updates and fixes at this point so hopefully I'll get a 3.0.1 published this weekend to address this.
Thanks for the report!

Out of curiosity, did you run with enabling debugging of MQTTjs?  I mean, I document how to enable debugging for mqtt-tuya, but you can also run DEBUG='mqttjs*' (or even DEBUG=*, but that's a LOT of debug) and the MQTTjs library will give you much more information about any MQTT specific issues.  I'm guessing it would have probably caught this pretty clearly but then again I haven't tried it.

Yes, I did do a DEBUG=* at one point... Which obviously created a ton of logs... yet as far as I recall other than the connection mysteriously terminating.... there wasn't much actionable output there (or I missed it).
What it did help with, was it pinpointed that the reconnect start once the 'publish' runs

This is hopefully fixed in the latest push so closing this for now.


win10，cupy and pytorch can‘t work together

torch can work on project
cupy112 also can work without torch
C:>python
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import cupy
>>> cupy.show_config()
OS                           : Windows-10-10.0.19043-SP0
Python Version               : 3.8.10
CuPy Version                 : 9.4.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.19.3
SciPy Version                : 1.7.1
Cython Build Version         : 0.29.24
Cython Runtime Version       : None
CUDA Root                    : C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2
nvcc PATH                    : C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\bin\nvcc.EXE
CUDA Build Version           : 11020
CUDA Driver Version          : 11040
CUDA Runtime Version         : 11020
cuBLAS Version               : (available)
cuFFT Version                : 10401
cuRAND Version               : 10203
cuSOLVER Version             : (11, 1, 0)
cuSPARSE Version             : (available)
NVRTC Version                : (11, 2)
Thrust Version               : 101000
CUB Build Version            : 101000
Jitify Build Version         : 60e9e72
cuDNN Build Version          : 8202
cuDNN Version                : 8201
NCCL Build Version           : None
NCCL Runtime Version         : None
cuTENSOR Version             : 10301
cuSPARSELt Build Version     : None
Device 0 Name                : NVIDIA GeForce RTX 3070
Device 0 Compute Capability  : 86
Device 0 PCI Bus ID          : 0000:05:00.0
>>>

i tried install cupy like pip install cupy-cuda112 and pip install cupy-cuda112 -f https://github.com/cupy/cupy/releases/tag/v10.0.0b2
C:\>pip install cupy-cuda112 -f https://github.com/cupy/cupy/releases/tag/v10.0.0b2
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
Looking in links: https://github.com/cupy/cupy/releases/tag/v10.0.0b2
Collecting cupy-cuda112
  Using cached cupy_cuda112-9.4.0-cp38-cp38-win_amd64.whl (59.9 MB)
Requirement already satisfied: fastrlock>=0.5 in c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages (from cupy-cuda112) (0.6)
Requirement already satisfied: numpy<1.24,>=1.17 in c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages (from cupy-cuda112) (1.19.3)
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
Installing collected packages: cupy-cuda112
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
Successfully installed cupy-cuda112-9.4.0
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\roaming\python\python38\site-packages)
WARNING: Ignoring invalid distribution - (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: You are using pip version 21.1.1; however, version 21.2.4 is available.
You should consider upgrading via the 'c:\users\optoma\appdata\local\programs\python\python38\python.exe -m pip install --upgrade pip' command.

but when uninstall it，got some err
C:>pip uninstall cupy-cuda112
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
WARNING: Ignoring invalid distribution -upy-cuda112 (c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages)
Found existing installation: cupy-cuda112 9.4.0
Uninstalling cupy-cuda112-9.4.0:
  Would remove:
    c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\cupy\*
    c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\cupy_backends\*
    c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\cupy_cuda112-9.4.0.dist-info\*
    c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\cupyx\*
Proceed (y/n)? y
  Successfully uninstalled cupy-cuda112-9.4.0
ERROR: Exception:
Traceback (most recent call last):
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\cli\base_command.py", line 180, in _main
    status = self.run(options, args)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\commands\uninstall.py", line 89, in run
    uninstall_pathset.commit()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\req\req_uninstall.py", line 442, in commit
    self._moved_paths.commit()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\req\req_uninstall.py", line 282, in commit
    save_dir.cleanup()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\utils\temp_dir.py", line 184, in cleanup
    rmtree(self._path)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_vendor\tenacity\__init__.py", line 339, in wrapped_f
    return self(f, *args, **kw)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_vendor\tenacity\__init__.py", line 430, in __call__
    do = self.iter(retry_state=retry_state)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_vendor\tenacity\__init__.py", line 378, in iter
    raise retry_exc.reraise()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_vendor\tenacity\__init__.py", line 206, in reraise
    raise self.last_attempt.result()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\concurrent\futures\_base.py", line 437, in result
    return self.__get_result()
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\concurrent\futures\_base.py", line 389, in __get_result
    raise self._exception
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_vendor\tenacity\__init__.py", line 433, in __call__
    result = fn(*args, **kwargs)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\site-packages\pip\_internal\utils\misc.py", line 135, in rmtree
    shutil.rmtree(dir, ignore_errors=ignore_errors, onerror=rmtree_errorhandler)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\shutil.py", line 740, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\shutil.py", line 613, in _rmtree_unsafe
    _rmtree_unsafe(fullname, onerror)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\shutil.py", line 613, in _rmtree_unsafe
    _rmtree_unsafe(fullname, onerror)
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\shutil.py", line 618, in _rmtree_unsafe
    onerror(os.unlink, fullname, sys.exc_info())
  File "c:\users\optoma\appdata\local\programs\python\python38\lib\shutil.py", line 616, in _rmtree_unsafe
    os.unlink(fullname)
PermissionError: [WinError 5] 拒绝访问。: 'C:\\Users\\OPTOMA\\AppData\\Local\\Programs\\Python\\Python38\\Lib\\site-packages\\~-py\\.data\\lib\\nvToolsExt64_1.dll'

nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Sun_Feb_14_22:08:44_Pacific_Standard_Time_2021
Cuda compilation tools, release 11.2, V11.2.152
Build cuda_11.2.r11.2/compiler.29618528_0

i didn't find torch-cu11.2，so torch-cu11.1 was installed， it works。
C:\Users\OPTOMA>python
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> print(torch.backends.cudnn.version())
8005
>>> print(torch.__version__)
1.9.0+cu111
>>> print(torch.version.cuda)
11.1

import torch after import cupy：
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import cupy
>>> import torch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\__init__.py", line 124, in <module>
    raise err
OSError: [WinError 127] 找不到指定的程序。 Error loading "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\lib\cublas64_11.dll" or one of its dependencies.
>>> exit()

cublas64_11.dll can found in the path
import cupy after import torch：
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> import cupy
Traceback (most recent call last):
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\__init__.py", line 16, in <module>
    from cupy import _core  # NOQA
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\_core\__init__.py", line 1, in <module>
    from cupy._core import core  # NOQA
  File "cupy\_core\core.pyx", line 1, in init cupy._core.core
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\cuda\__init__.py", line 8, in <module>
    from cupy.cuda import compiler  # NOQA
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\cuda\compiler.py", line 11, in <module>
    from cupy.cuda import device
  File "cupy\cuda\device.pyx", line 1, in init cupy.cuda.device
ImportError: DLL load failed while importing runtime: 找不到指定的程序。

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\__init__.py", line 37, in <module>
    raise ImportError(_msg) from e
ImportError: CuPy is not correctly installed.

If you are using wheel distribution (cupy-cudaXX), make sure that the version of CuPy you installed matches with the version of CUDA on your host.
Also, confirm that only one CuPy package is installed:
  $ pip freeze

If you are building CuPy from source, please check your environment, uninstall CuPy and reinstall it with:
  $ pip install cupy --no-cache-dir -vvvv

Check the Installation Guide for details:
  https://docs.cupy.dev/en/latest/install.html

original error: DLL load failed while importing runtime: 找不到指定的程序。
>>> exit()

Any help is appreciated！！！

Thanks for the detailed feedback. CUDA versions cannot be mixed in a single process, so if you use torch+cu111 you need to install CUDA Toolkit 11.1 and cupy-cuda111.

thank you， reply so quickly，
and i reinstalled cupy-cuda111，and didn't reinstall cuda112 to cuda111（too many modules need to reinstall），
it seems that：
works like
import torch
import cupy

but not work like
import cupy
import torch
Traceback (most recent call last):
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\__init__.py", line 16, in <module>
    from cupy import _core  # NOQA
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\_core\__init__.py", line 1, in <module>
    from cupy._core import core  # NOQA
  File "cupy\_core\core.pyx", line 1, in init cupy._core.core
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\cuda\__init__.py", line 8, in <module>
    from cupy.cuda import compiler  # NOQA
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\cuda\compiler.py", line 15, in <module>
    from cupy_backends.cuda.libs import nvrtc
ImportError: DLL load failed while importing nvrtc: 找不到指定的模块。

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\OPTOMA\AppData\Local\Programs\Python\Python38\lib\site-packages\cupy\__init__.py", line 37, in <module>
    raise ImportError(_msg) from e
ImportError: CuPy is not correctly installed.

If you are using wheel distribution (cupy-cudaXX), make sure that the version of CuPy you installed matches with the version of CUDA on your host.
Also, confirm that only one CuPy package is installed:
  $ pip freeze

If you are building CuPy from source, please check your environment, uninstall CuPy and reinstall it with:
  $ pip install cupy --no-cache-dir -vvvv

Check the Installation Guide for details:
  https://docs.cupy.dev/en/latest/install.html

original error: DLL load failed while importing nvrtc: 找不到指定的模块。

so i‘ll just write like the first way，if there still some other problem，i’ll reinstall cuda。
thanks again


Mobile View padding is still there on the left

@katpas have you seen this... seems to be some css causing this. you have any idea as to why this might be happening?

I have created a PR that will fix this issue.

I deleted the css we had in their originally when I was moving stuff around. Sorry.


feat: scroll to the most recent conversation when the plugin first loads

Looks good to me, thanks!

没有写入权限, 无法合并


User/provencher/exposed box activation setting

Overview
Previously, the box activation mode was set to Manual, which meant that changing handle visibility settings would not be persisted as the pointer focus change listener would prevent handle activation depending on the box activation mode.
Changes

Fixes: # https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/4052
-> The above issue is resolved when setting the activation type to ActivateByProximityAndPointer

/azp run

I want to give @luis-valverde-ms a chance to look at this.

The intent of the changes looks reasonable to me but the component owners (@cre8ivepark and @johnppella?) should have a look too.
The changes seem to deal with being able to change the activation type at runtime (from code) but the PR description doesn't make it clear. Can we rework that a bit and make it clear too how it solves the connected issue?

@luis-valverde-ms this is from the referenced issue
"So the jist is that I was setting which handles the bounding box would show, as your code example pointed out, but when it came time to hover over the box, no handles would show up at all.
I looked through the code, and this is because the focus change function in the bounding box returns before changing handle visibility if the enum I exposed was set to manual, which is the default value. This early return prevents the handles that should be visible from showing, as the code that determines visibility does a check against the show wireframe property, which is set on the focus change function.
Perhaps this exposes a deeper bug, but I didn't want to change core functionality of the box as that could have far reaching consequences. Simply changing the enum I exposed stops the focus change function from returning early, and the wireframe bool is properly set.
Part of the issue with my bug report is that I conflated manipulation constraints with bounding box handles thinking they were more related.
Perhaps constraints on the manipulation handler should affect which handles the bounding box shows, as the handles permit transformations the manipulation handler might forbid."

I'll followup with @cre8ivepark to see if he can look at this.


放出一个release版本试用？

试用成本有点高，能不能给一个安装包试用一下

试用成本有点高，能不能给一个安装包试用一下

目前分支还没有合并，这可能不太容易。
或许可以等我们的分支合并进官方再说。

https://github.com/hhao/ollama/releases

非常感谢，能否提供一个windows下可用的安装包

Hi, I don't always pay attention to the issue area in this fork code repo.

If this issue still needs to be answered, please raise an issue in the main repo with "ollama" label. I will respond very quickly.
If this issue no longer needs to be answered, I will close it this week.


Consecutive print statements don't work. Compiler only outputs first print statement.

Test added to check for this. It's named, "test-helloTwice.dice"


C Libraries (c_framework) causes memory problem

Most of C libraries causes memory problem, e.g. c_resolve.

Now we uses something special to solve it. see latest release


Redefine getPacketTypeID() functions as macros

Not sure if it makes any sense to actually implement it, but it'd be nice to be able to do, e.g.:
switch (getNovatelPacketID())
{
case getBinaryResponsePacketID():
    // Do something...
    break;
};

So in that particular case, it'd be a change in NovatelPackets.h that'd look something like this:
- uint32_t getBinaryResponsePacketID(void);
+ #define getBinaryResponsePacketID() (1)

Done, version 1.4.8.a


"Face recognition failed" "Invalid input" Error: Invalid input

Description: The user is not able to pass the Face Verification
Steps to reproduce:

Open the https://wallet.gooddollar.org/
Go to the Face Verification screen
Scan your face
Pay attention to the Error message in the console

Expected result:
The user can pass the Face Verification
Actual result:
The user is not able to pass the Face Verification
Environment:  Prod 1.12.0
Devices list: Desktop- Windows 10 // Chrome 87.0.4280.88
Additional info:
the mobile that was used to signup via passwordless - +380636456452
email<EMAIL_ADDRESS>pass: Tester_11111

hotfixed on prod (changed fv api version to 8, redeployed on netlify)

@sirpy
@serdiukov-o-nordwhale
The issue is fixed. The user can pass the Face Verification.  If the user's face is in the system the "Unfortunately we found your twin" message is shown.
Checked on the Prod v 1.12.0
Google Chrome v 87.0.4280.88


Fix memory leak in TokenTransport

Close token-demand response before making auth-and-retry.
Unclosed responses lead to unclosed sockets and to memory leaks in long running apps:
...
lrwx------ 1 root root 64 Mar 12 20:16 11 -> socket:[3213896]
lrwx------ 1 root root 64 Mar 12 20:16 110 -> socket:[3238100]
lrwx------ 1 root root 64 Mar 12 20:16 111 -> socket:[3238973]
lrwx------ 1 root root 64 Mar 12 20:16 112 -> socket:[3238317]
lrwx------ 1 root root 64 Mar 12 20:16 113 -> socket:[3239210]
lrwx------ 1 root root 64 Mar 12 20:16 114 -> socket:[3239321]
lrwx------ 1 root root 64 Mar 12 20:16 115 -> socket:[3239503]
lrwx------ 1 root root 64 Mar 12 20:16 116 -> socket:[3239643]
lrwx------ 1 root root 64 Mar 12 20:16 117 -> socket:[3238846]
...

Isn't this resolved by https://github.com/heroku/docker-registry-client/pull/50? Although admittedly I prefer this implementation since it checked for the error...


Infinite predictions when using Poisson regression with large weights

Description
Using objective='poisson' with big weights in some cases produces very large predictions, up to $10^{252}$ times higher than the biggest example in the train dataset.
Reproducible example
A minimum working example of this can be produced with the dataset 'mwe.csv' which can be downloaded from https://pastebin.com/0gw1vz9x
import pandas as pd
import lightgbm as lgb
df = pd.read_csv("mwe.csv")
print(df['y'].describe())

model = lgb.LGBMRegressor(objective='poisson', num_trees=1, verbose=2)
model.fit(df[['x']], df['y'], sample_weight=df['w'])
print(pd.Series(model.predict(df[['x']])).describe())

The example trains a model with a single tree however it stops after the first tree for higher values of num_trees.
The tree looks like this:

The problem disappears if we use sample_weight=df['w']/10000 instead. We obtain the following tree

Dividing the weights by any value between 2008 and 16454 seems to produce the same tree.
Environment info
LightGBM version or commit hash: This can be reproduced both with the latest version and with  v3.2.1.

Did you ever find the cause of this? I'm seeing a similar behaviour when using gamma regression


Order support options alphabetically

Fixes https://github.com/prometheus/prometheus/issues/4080

Sounds fair.


2023 08 01

Agenda - 2023 08 01
Time 1630pm (BST) - See the time in your timezone

Chair – Tammy McClellan @tmcclell (Microsoft)
Vice-Chair – Chris Lloyd-Jones @Sealjay (Avanade)
Convener – Sean Mcilroy @seanmcilroy29  (GSF)

Antitrust Policy
Joint Development Foundation meetings may involve participation by industry competitors, and it is the intention of the Joint Development Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.
Roll Call
Please add 'Attended' to this issue during the meeting to denote attendance.
Any untracked attendees will be added by the GSF team below:
Agenda

[ ] Review/Approve agenda

Answering the so-what question

[ ] https://github.com/Green-Software-Foundation/oc/discussions/18
[ ] https://github.com/Green-Software-Foundation/oc/discussions/16 - Sarah

Proposed new projects

[ ] #44
[ ] https://github.com/Green-Software-Foundation/oc/discussions/17 - Sarah @greenhsu123:
AI: @jawache to revert on https://github.com/Green-Software-Foundation/oc/discussions/17

Agenda submissions

[ ] #33
[ ] #32
[ ] #35
[x] #39
[ ] https://github.com/Green-Software-Foundation/oc/issues/42

Governance

[ ] https://github.com/Green-Software-Foundation/oc/issues/23
[ ] https://github.com/Green-Software-Foundation/oc/issues/26
[ ] https://github.com/Green-Software-Foundation/oc/issues/36

Process Improvement

[ ] https://github.com/Green-Software-Foundation/oc/discussions/11
New onboarding process has now been rolled out
[ ] Review the GSF Contributing Writers' Guidelines
[ ] #36
[ ] #37

Regular updates

[ ] https://github.com/Green-Software-Foundation/oc/issues/29

Anniversary 'Health Check' survey

[ ] https://www.research.net/r/gsf-health-anniversary-check-survey

Sean

AOB

[ ] Any questions or other business

Next meeting

[ ] 05th Sept

Adjourn

[ ] Any objections?

Approved


Remove unnecessary semicolons at the end of the namespace definition

I found that there were some unnecessary semicolons at the end of the
namespace declaration and this patch cleaned them up.
Use the following command(on MacOS):
# Replace "}; // namespace" with "} // namespace".
find velox/ \( -name "*.h" -o -name "*.cpp" \) -type f -exec sed -i '' 's/}; \/\/ namespace/} \/\/ namespace /g' {} +

No functional changes.

@mbasmanova  could you please take a look, thanks.

@lingbin Would you rebase?

@mbasmanova  Already rebased, thanks for the review.

@mbasmanova Only the "Facebook Internal - Builds & Tests" check failed, but I can't see the details. If there's anything I need to do, feel free to tell me. Thanks.

@lingbin Here are some errors:
In file included from fbcode/velox/experimental/codegen/ast/ConstantExpression.cpp:17:
buck-out/v2/gen/fbcode/c80f2ef40170ee86/velox/experimental/codegen/ast/__velox_codegen_ast__/buck-headers/velox/experimental/codegen/ast/ConstantExpressions.h:144:2: error: expected ';' after class
} // namespace codegen
 ^
 ;
1 error generated.

@lingbin Would you rebase?

@mbasmanova  Already rebased, thanks.


Getting heading value -1 in navigator.geolocation.getCurrentPosition method only in iOS

I am using navigator.geolocation.getCurrentPosition method for getting current latitude and longitude and I am getting heading value as -1 in iOS whereas in android it working fine
React Native version:

"react-native": "0.58.4"

Steps To Reproduce

Getting heading value -1 in iOS.

navigator.geolocation.getCurrentPosition(
      position => {
        alert("postion12345........6" + JSON.stringify(position.coords.heading));
  })

Describe what you expected to happen:
To get the correct heading value to rotating the marker.
Snack, code example, screenshot, or link to a repository:
https://stackoverflow.com/questions/55688545/getting-heading-value-1-in-getcurrentpostion-method-in-geoloaction
Screenshot:-

Geolocation module removed in 0.60 version, please use https://github.com/react-native-community/react-native-geolocation and report issue there.


[SPARK-47396][SQL] Add a general mapping for TIME WITHOUT TIME ZONE to TimestampNTZType

What changes were proposed in this pull request?

Add a general mapping for TIME WITHOUT TIME ZONE to TimestampNTZType
Why are the changes needed?

TIME WITHOUT TIME ZONE should be able to be configured to map to TimestampNTZType like TIMESTAMP WITHOUT TIME ZONE
Does this PR introduce any user-facing change?

yes, TIME WITHOUT TIME ZONE can be mapped to TimestampNTZType when preferTimestampNTZ is true
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?
no

Thank you @dongjoon-hyun

Oh, it seems that the newly added test case fails at PostgresIntegrationSuite.
[info] PostgresIntegrationSuite:
[info] - Type mapping for various types (209 milliseconds)
[info] - Basic write test (293 milliseconds)
[info] - Creating a table with shorts and floats (80 milliseconds)
[info] - SPARK-47390: Convert TIMESTAMP/TIME WITH TIME ZONE regardless of preferTimestampNTZ *** FAILED *** (55 milliseconds)
[info]   1970-01-01T09:22:31.949271 was not instance of java.sql.Timestamp (PostgresIntegrationSuite.scala:293)

Oh, it fails at the previous PR (SPARK-47390) instead of this PR, SPARK-47396.

Oops...I Will check the pg time types again. The typeNames for times are copied from existing code，and they might be wrong

https://github.com/apache/spark/pull/45522 is merged.
Could you rebase this PR to the master branch once more?

Thank you very much @dongjoon-hyun

Merged to master for Apache Spark 4.0.0. Thank you, @yaooqinn .


AppVeyor: Fix creation of symblic links for good

Description of changes:
The main repository contains symbolic links to directories in the
submodule. As the submodule is initialized after the main repository, it
is unknown to Git whether the links point to files or directories. On
Windows, this is important to know as symbolic links can point to
either files or directories, and the type has to be known at the point of
their creation. The default is to create file symbolic links, which is
wrong in this case. So delete the symbolic links and check them out
again after the submodule has been initialized to get them recreated as
directory symbolic links.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Cool -- looks like AppVeyor is reporting a successful status here too. Thanks for the change!


Widget

I would like to see basic widgets of some type, since those graphic are beautiful.

Do you have a widget on your home screen?

No. I would see this as a suggestion, or roadmap item, if you will. It's not an issue. Sorry if this might be a misunderstanding.

No, it's just that if you mean the widget on the home screen, then this is already present #1

Hm. I don't have that available
Nova launcher

I mean, I have it planned.

 Sorry. 😂


Electron.WindowManager.CreateWindowAsync -> NullRef when debugging the ASP.NET core app

  public async void Configure(IApplicationBuilder app, IHostingEnvironment env)
        {
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
                app.UseBrowserLink();
            }
            else
            {
                app.UseExceptionHandler("/Error");
            }

            app.UseStaticFiles();

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "{controller}/{action=Index}/{id?}");
            });

            // Open the Electron-Window here
            await Electron.WindowManager.CreateWindowAsync();
        }

WebApplication6> Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
WebApplication6>    at ElectronNET.API.WindowManager.CreateWindowAsync(BrowserWindowOptions options, String loadUrl)
WebApplication6>    at ElectronNET.API.WindowManager.<CreateWindowAsync>d__7.MoveNext()
WebApplication6> --- End of stack trace from previous location where exception was thrown ---
WebApplication6>    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
WebApplication6>    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
WebApplication6>    at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
WebApplication6>    at WebApplication6.Startup.<Configure>d__5.MoveNext() in D:\Users\muehsig\Documents\Visual Studio 2017\Projects\WebApplication6\WebApplication6\Startup.cs:line 51
WebApplication6> --- End of stack trace from previous location where exception was thrown ---
WebApplication6>    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
WebApplication6>    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
WebApplication6>    at System.Threading.ThreadPoolWorkQueue.Dispatch()

Problem was no hybrid support for classic asp.net web apps.
I implement a HybridSupport.IsElectronActive-Proptery. See in our sample app in the startup.cs and controllers code, how to use it.


Add package url to searchengine api

Package url can be retrieved from api by replacing suffix .so with .url in "download_url" (though it's not documented). It would be useful to have easier access to this, directly from https://libc.rip/api/find endpoint. Maybe under "package_url" or "libs_url"?
This .url file was added in this PR: https://github.com/niklasb/libc-database/pull/10

I'll be happy to consider a pull request for this feature


Fix: Jfrog Webhook Handler Cannot Get Right Image

Description of your changes

Fixes #

Fix the image path from the JFrog webhook when it is triggered.
Fix the Info Payload Type From Harhor to JFrog in JFrog handle function
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

will do tests on weekends.


[doc] TSDoc Error During Build

Hi,
I encountered the following TSDoc error when installing this package and running npm run build in my project. Could you please update the comments to resolve these errors?
Thank you!
Warning: node_modules/@nevware21/ts-utils/dist/types/ts-utils.d.ts:492:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
Warning: node_modules/@nevware21/ts-utils/dist/types/ts-utils.d.ts:493:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen
Warning: node_modules/@nevware21/ts-utils/dist/types/ts-utils.d.ts:495:4 - (tsdoc-unsupported-tag) The TSDoc tag "@remarks" is not supported by this tool
Warning: node_modules/@nevware21/ts-utils/dist/types/ts-utils.d.ts:3591:29 - (tsdoc-code-span-missing-delimiter) The code span is missing its closing backtick
Warning: node_modules/@nevware21/ts-utils/dist/types/ts-utils.d.ts:6203:4 - (tsdoc-param-tag-missing-hyphen) The @param block should be followed by a parameter name and then a hyphen

Ok, this is a larger issue than expected as there was no existing tsdoc.json defintion defined and the api-extractor config was ignoring warnings. So this is a larger issue than expected and is taking longer than expected to fix all of the typedoc issues, so it might be another day or two before I have these (ts-utils and ts-async) addressed and released.
One note: the @remarks is expected and you should add this to your tsdoc.json as an expected block comment
include in your supportForTags section of tsdoc.json
"@remarks": true


Change response code returned to client when they are over limits

Current Result

Client sends bad key                                       --> got 403 Authentication failed
Client sends valid key, but is over rate limits --> got 403 Authentication failed.

This makes errors difficult to debug, as the two different causes are not discriminated.
Requested Result
Return 429 "Too many requests"
There maybe documentation pages that will required modification to explain this code has changed in this (insert version of apicast that implements this here) or apicast
Additional Information
I believe that this is when Service Management API returns a 409 Conflict with authorizing.
We do not at the moment contemplate the need to customize this code and error message via Admin Portal - so a fixed code and message are all that's requested in this issue.

We have survived with the abused 403 for years. I am all for improving this, but I would prefer to take a bit more time and do a proper implementation with the ability to customize the response. The code to handle that was designed in a good extensible manner. The second phase beyond that would be to provide meta data response to the client about the rate limit and the time remaining until the next window.

I agree we can wait. Especially as it seems we can use the X-3scale header that will be supported here. This should cover most scenarios in the meantime.

OK.
Will the X-3scale be documented in the trouble-shooting guide. I see this behavior as a trouble-shooting problem for providers....

Once it is supported and documented it makes sense to document it also in the troubleshooting guide.

The response header referred by @kevprice83 would be (with the corresponding value):

3scale-rejection-reason: limits_exceeded

For this to work the gateway will need to provide a header in its request to backend with the following form:

3scale-options: rejection_reason_header=1

and if it not parsing the body, use instead:

3scale-options: no_body=1&rejection_reason_header=1

This needs to wait until deployment of the affected backend version, which we are working towards completing today (or given the current time, probably on Monday).

Just chipping it to say that the deployment of support for that header happened a while ago.

This is a duplicate of #368


Client Interoperability between Paho and Vertx: Multi level topics

Thank you for this wonderful library. Appreciate the great effort.
We seem to have a issue with client side interoperability. For the server we do use https://github.com/GruppoFilippetti/vertx-mqtt-broker (latest)

Paho Java client version 1.2.0
Vertx Java client version 3.5.0

Multi level topic subscription with # wildcard (Example xxx/report/new/#)
Note: Message sent to xxx/report/new/123

Paho to Paho Subscription: works
Vertx to Vertx MQTT Client Subscription: works
Paho Sent Message is Received by Vertx client subscribing it: works
Vertx client sent message receiving by Paho Client: DOESN'T  WORK

Just to add, in the case where there is a issue single level topic messages sent to wildcard still works.
I have put the above in github as below and each contains a Readme.txt. BTW, it is pretty much stripped down code. Nothing else really in it.
https://github.com/Mahaswami/paho_mqtt_client_demo
https://github.com/Mahaswami/vertx_mqtt_client_demo
To reproduce the above behaviour here is what is needed:
Run the https://github.com/GruppoFilippetti/vertx-mqtt-broker after doing standard mvn stuff. Forgot to mention earlier that you had to comment out Line #6 in config.json of vertx-mqtt-broker (authenticator_address) to bypass the login requirement.
Run Paho client demo standalone. You should see a message sent by self coming back to the client. This demonstrates paho to paho working with multi level wildcard subscription
Run Vertx client demo standalone. You should see a message sent by self coming back to the client. This demonstrates vertx to vertx working with multi level wild card subscription
Run vertx client demo first and let it keep running. Then run paho client demo. You should see vertx client demo receiving messages sent from paho client demo. This demonstrates paho -> vertx working with multi level wild card subscription
Run Paho client demo and keep it running. Then run vertx client demo. You WON'T BE SEEING message sent by Vertx received by Paho. This demonstrates vertx -> paho NOT WORKING for multi level wild card subscription
Any idea what could be leading to this case? Thanks.

This turns to be a Eclipse Paho API method calling issue (confusing method signatures with different behaviours). Will write that up and put it here a bit later


vsts-npm-auth: Already have credentials - new credentials

Issue Description
How do I refresh the credentials or use different ones then I have set up?
Error logs
Because of invalid credentials I get the error code E401 Unauthorized.

@adiii4,
Need more information.

Are you using hosted or on-prem?
Is your agent *nix or win?
When you say "use different ones then I have set up", exactly what do you mean?  Do you have credentials in $HOME or checked in to your git repo?

I'm using on-prem also my agent is win. What I mean is the following: Imagine I set up vsts-npm-auth for the first time and enter my credentials. Now after a couple months I want to change my entered credentials (which I have set up the first time) to completly enter new credentials.
I found this but it didn't work. The message I got was 'entered credentials already for xx'.
Now my questions is how can I enter new credentials or overwrite the existing credentials?

@adiii4 ,
Are you saying that you have manually configured credentials for NPM on the build agent?  If so, you should not do this.  The NPMv2 task will automatically fetch credentials and inject them into your project's .npmrc for you.
This is all documented here in the "Set up authentication in a build task" section.

No I didn't. What I mean the first time you use vsts-npm-auth you have to enter your credentials via the terminal. My question is how do I change those credentials I entered?

@adiii4,
There are two things at play here.

VSTS npm auth will first check the credentials in your .npmrc to see if they need refreshing.  If they don't the tool will abort and not do anything.  You can override this behavior with "force" or by simply removing credentials from your .npmrc.
The tool will save VSTS creds in [1].  You need to remove [1] to get the login prompt again.

[1] HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSCommon\14.0\ClientServices\TokenStorage\VisualStudio\VssApp

@adiii4,
There are two things at play here.
VSTS npm auth will first check the credentials in your .npmrc to see if they need refreshing.  If they don't the tool will abort and not do anything.  You can override this behavior with "force" or by simply removing credentials from your .npmrc.
The tool will save VSTS creds in [1].  You need to remove [1] to get the login prompt again.
[1] HKEY_CURRENT_USER\SOFTWARE\Microsoft\VSCommon\14.0\ClientServices\TokenStorage\VisualStudio\VssApp

I don't have this registry entry.  Has it changed?  I'm not getting a prompt to enter my credentials so I constantly get a 401 when running npm install.

try add -F flag to force prompt
ex: vsts-npm-auth -F -config .npmrc

try add -F flag to force prompt
ex: vsts-npm-auth -F -config .npmrc

Thank you. This worked for me.

try add -F flag to force prompt ex: vsts-npm-auth -F -config .npmrc

Worked for me too


in suggested usage of AAD to get to storage accounts need to call out that accessing tables is unsupported

connection strings allow you to connect to all storage account funcitonality, but AAD access to storage account does not work for table access.
Also:
it is unclear whether the AAD access is in preview or GA.
The link from the note 1 above just says: Azure Storage supports using Azure Active Directory (AD) to authorize requests to Blob and Queue storage. ) So it would  seem that it is in GA.

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

ID: 1059069a-e860-f66d-3445-60425a5bffe1
Version Independent ID: 1d80c823-5a41-7d2b-f40d-b0f2ca3c673f
Content: Azure Key Vault managed storage account - PowerShell version
Content Source: articles/key-vault/key-vault-overview-storage-keys-powershell.md
Service: key-vault
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

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

@peledins Thanks again for the feedback, we're going to look into this one as well to see if we can put this into the docs.

Hey @peledins this issue seems to be resolved now as the Note at the top says :
Azure storage integration with Azure Active Directory (Azure AD) is now in preview.
Is this sufficient for the doc change now? We are currently adding the another bullet point to the first note saying :
AAD access to storage account does not work for table access.
Please let us know if there are any other issues with this, otherwise we will be closing this out by end of day tomorrow.

It might be great to match CLI and powershell information. Maybe refactor out common parts.

Azure storage integration with Azure Active Directory (Azure AD) is now in preview.
Is it still in preview? The linked page does not talk about being in preview.

“AAD access to storage account does not work for table access.”
This is great.

Thanks,
Peteris
From: Frank Hu<EMAIL_ADDRESS>Sent: Wednesday, July 31, 2019 6:20 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Peteris Ledins<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] in suggested usage of AAD to get to storage accounts need to call out that accessing tables is unsupported (#35886)
Hey @peledinshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpeledins&data=02|01|peledins%40microsoft.com|d05514b013fb429dd4bd08d7161e6076|72f988bf86f141af91ab2d7cd011db47|1|0|637002192032409663&sdata=158LX8THJiZWivXdTGLW%2B1iJas9QnT3wr1NvUN94UcU%3D&reserved=0 this issue seems to be resolved now as the Note at the top says :
Azure storage integration with Azure Active Directory (Azure AD) is now in preview.
Is this sufficient for the doc change now? We are currently adding the another bullet point to the first note saying :
AAD access to storage account does not work for table access.
Please let us know if there are any other issues with this, otherwise we will be closing this out by end of day tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F35886%3Femail_source%3Dnotifications%26email_token%3DAK7MHLWCW2NH4OXN7QA3EOLQCI24DA5CNFSM4IG7PPS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3JAI6Q%23issuecomment-517080186&data=02|01|peledins%40microsoft.com|d05514b013fb429dd4bd08d7161e6076|72f988bf86f141af91ab2d7cd011db47|1|0|637002192032419658&sdata=L90Bape7MTnjniNMTfOglZ68EfrxjRq3eyhKLJXzmgQ%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAK7MHLVTOB5TUYD7CS2QTV3QCI24DANCNFSM4IG7PPSQ&data=02|01|peledins%40microsoft.com|d05514b013fb429dd4bd08d7161e6076|72f988bf86f141af91ab2d7cd011db47|1|0|637002192032419658&sdata=Xhgj1ao4%2Bmp1DdL43Uo2Ps0GR%2FeErzbtYM5URoB1Q4g%3D&reserved=0.

Sure, could you create a new git issue for each update you'd like to make?
@peledins Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day today. Please reopen this git issue if you have anymore concerns. Thanks


Http IZipkinSender example

I couldn't find any example of how would one use this library without kafka, if you just want to report spans directly to Zipkin.
How hard would be to implement one?

Hi @Rurouni,
It doesn't exist yet but I imagine it would just be a POST request on /spans route of your zipkin collector (according to http://zipkin.io/zipkin-api/#/paths/%252Fspans).
I can come up with a draft version if you wish.

After looking at how it's implemented at https://github.com/clearctvm/zipkin.net it seems you need to do POST to /api/v1/spans with ContentType: application/x-thrift so it is straightforward indeed, but requires initial digging, so I think that having Http option included out of the box would help with adoption of this library

We just added an HttpZipkinSender. You're totally right when saying it'll help with adoption (not only the lib but also with Zipkin itself as the collector http is basically the first step to test now). Thanks for your feedback


Scaling in RGB linear

Hi.
I used VapourSynth to scale a YUV420P8 video in RGB linear but I got a strange result.
import vapoursynth as vs
from vapoursynth import core
video = core.ffms2.Source(source=r"source.mkv")
video = core.resize.Spline36(clip=video,format=vs.RGBS, range_in_s="limited", matrix_in_s="709", primaries_in_s="709", primaries_s="709", transfer_in_s="709", transfer_s="linear",matrix_s="rgb",range_s="limited",dither_type="none")
video = core.resize.Spline36(clip=video,width=854, height=356, format=vs.YUV420P8, range_in_s="limited", matrix_in_s="rgb", primaries_in_s="709", primaries_s="709", transfer_in_s="linear", transfer_s="709",matrix_s="709",range_s="limited",dither_type="error_diffusion")
video.set_output()

The result - http://imgbox.com/2FiQgCKD
Scale with Avisynth dither in RGB linear:
FFVideoSource("source.mkv")
dither_convert_yuv_to_rgb(output="rgb48y",chromak="spline36",matrix="709",lsb_in=false)
dither_y_gamma_to_linear(false, false, "709")
dither_resize16(854,356)
dither_y_linear_to_gamma(false, false, "709")
dither_convert_rgb_to_yuv(selectevery(3,0),selectevery(3,1),selectevery(3,2),chromak="spline36",matrix="709",lsb=true)
f3kdb(0,0,0,0,0,0, keep_tv_range=true, input_depth=16,output_depth=8)

The result - http://imgbox.com/o3rMdLeG
You can notice the edges difference.  Is this result expected? Could zimg scaling be used in RGB linear?

Please provide a test image.

https://files.catbox.moe/tsszj7.7z

After reviewing the provided image, I have determined that the dark/bright halo is correct behavior. Scaling in linear light naturally results in increased haloing with filters that overshoot. You might observe the haloing growing progressively worse from billinear to bicubic and then to spline/lanczos.
DitherTools (a.k.a. fmtconv) demonstrates the same artifacts. You are seeing a visual difference with z.lib because of differences in gamma-linear conversion. When "curve" is set to "709" in dither_y_gamma_to_linear, it uses the BT.709 OETF. In z.lib, when the transfer characteristics are "709", then the BT.1886 EOTF is used. This is because z.lib performs all gamma operations in display light.

Correct, using "1886" curve in dither_y_gamma_to_linear/dither_y_linear_to_gamma there is no visual difference with z.lib. I didn't realize different transfer curve is used. Just those edges look a bit unnaturally compared to curve "709" but I guess it's subjective.
Thanks for the help and your time.
Thanks for you work.
This ticket could be closed.

After reviewing the provided image, I have determined that the dark/bright halo is correct behavior. Scaling in linear light naturally results in increased haloing with filters that overshoot. You might observe the haloing growing progressively worse from billinear to bicubic and then to spline/lanczos.
DitherTools (a.k.a. fmtconv) demonstrates the same artifacts. You are seeing a visual difference with z.lib because of differences in gamma-linear conversion. When "curve" is set to "709" in dither_y_gamma_to_linear, it uses the BT.709 OETF. In z.lib, when the transfer characteristics are "709", then the BT.1886 EOTF is used. This is because z.lib performs all gamma operations in display light.

BT.1886 just defines the corresponding EOTF to the long-used BT.709 OETF.
The OETFs specified in BT.1886 and BT.709 are identical.


can't find class ShapeBadgeItem...

hi, thank u for your BottomNacigation ,its awesome!
Now , i want to add a red dot shaped badge into my bottomitem,just like samle.Just a red dot ,without text.
However, i can't find class ShapeBadageitem in my project which is supported in your Sample like this:
import com.ashokvarma.bottomnavigation.ShapeBadgeItem;
ShapeBadgeItem circularBadgeItem, sqaureBadgeItem;
 circularBadgeItem =   new ShapeBadgeItem()                 //.setBorderWidth(8)                 .setBackgroundColorResource(R.color.red)                 .setDimen(8) // the size to badge in dp                 .setShape(ShapeBadgeItem.CIRCLE) // Choose between ShapeBadgeItem.CIRCLE or ShapeBadgeItem.SQUARE                 .setMargins(0, 2, 4, 0) // left, top, right, bottom                 .setHideOnSelect(autoHide.isChecked());
addItem(new BottomNavigationItem(R.drawable.ic_book_white_24dp, "Books").setActiveColorResource(R.color.teal).setShapeBadgeItem(circularBadgeItem))
Is ShapeBadgeItem-function disabled in 1.4.1?Or i use the wrong way?Maybe it's only exsist in Sample Projest...?
My english is not good ,but i hope you understand.Thank you~

it's present in 1.4.2 i will update read me


Update README.md

Updated the pyOSCAL and pyOSCAL-Builder descriptions

I think I can trust the provenance of this one, @mruge! :-)


Don't allow mixing of CDs and sequence features

Right now, when showing sequence features instead of CDs, the user can still drop in CDs.  This doesn't make sense and isn't supported (and causes undefined behavior/other bugs).  The canvas should either be a CD editor or immutable sequence feature viewer.

@cjmyers appears to be fixed. Please verify.

Agreed.  Closing.


Running the latest mlnet throws System.NotImplementedException exceptions.

System Information (please complete the following information):
mlnet --version
16.14.0+4be0d1bbdd23182e304cd74a8b833c40fd980be3
Visual Studio Version : 17.4.2
I've been using the command line mlnet tool to train my datasets. The previous version worked fine. The new version is crashing with some exceptions like below. The previous version was (16.13.9+3066041f1761935763bdd267a9bcbb64cb3ec543) the new version is (16.14.0+4be0d1bbdd23182e304cd74a8b833c40fd980be3).
Describe the bug
Running mlnet on the command line throws the bug:
C:\pubtemp>mlnet classification --dataset "Diameter.csv" --label-col 1 --name "Diameter" --train-time 60
Start Training
System.NotImplementedException: The method or operation is not implemented.
at Microsoft.ML.ModelBuilder.AutoMLService.Experiments.ExperimentFactory.CreateExperiment(MLContext context, ITrainingConfiguration config, AutoMLDependService services, PathConfiguration pathConfig) in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/ExperimentFactory.cs:line 36
at Microsoft.ML.ModelBuilder.AutoMLEngine.StartTrainingAsync(ITrainingConfiguration config, PathConfiguration pathConfig, CancellationToken userCancellationToken) in //src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 135
at Microsoft.ML.CLI.Runners.AutoMLRunner.ExecuteAsync() in //src/mlnet/Runners/AutoMLRunner.cs:line 89
at Microsoft.ML.CLI.Program.TrainAsync(TrainingConfiguration trainingConfiguration, PathConfiguration pathConfig, AutoMLServiceLogLevel logLevel) in //src/mlnet/Program.cs:line 349
at Microsoft.ML.CLI.Program.AutoMLCommandRunner(AutoMLCommand command, Boolean skipGenerateConsoleApp) in //src/mlnet/Program.cs:line 330
at Microsoft.ML.CLI.Program.<>c.<b__4_0>d.MoveNext() in //src/mlnet/Program.cs:line 90
--- End of stack trace from previous location ---
at System.CommandLine.Invocation.CommandHandler.GetExitCodeAsync(Object value, InvocationContext context)
at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.ML.CLI.Program.<>c__DisplayClass4_0.<b__9>d.MoveNext() in /_/src/mlnet/Program.cs:line 291
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<b__0>d.MoveNext()
Check out log file for more information: C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt
Exiting ...
Additional info from log.txt:
2022-12-06 13:02:43.3963 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4245 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4245 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4331 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4331 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4331 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4450 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4450 DEBUG System.FormatException: String ' available trainer: LGBM, RF, FASTTREE, LBFGS, SDCA ' was not recognized as a valid Boolean.
at System.Boolean.Parse(ReadOnlySpan`1 value)
at System.Boolean.Parse(String value)
at Microsoft.ML.CLI.FeatureFlagManager.ReadFeatureFlags(String ffPath) in //src/mlnet/FeatureFlagManager.cs:line 64 (Microsoft.ML.CLI.FeatureFlagManager.ReadFeatureFlags)
2022-12-06 13:02:43.4857 DEBUG Set log file path to C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Commands.MLCommand.set_LogFilePath)
2022-12-06 13:02:43.4857 DEBUG Set log level to Info (Microsoft.ML.CLI.Commands.MLCommand.set_Verbosity)
2022-12-06 13:02:43.8027 INFO Start Training (Microsoft.ML.CLI.Runners.AutoMLRunner+d__8.MoveNext)
2022-12-06 13:02:43.8185 DEBUG [Source=TextLoader; Binding, Kind=Trace] Channel started (Microsoft.ML.CLI.Runners.AutoMLRunner.Instance_DiagnosticDataReceived)
2022-12-06 13:02:43.8279 DEBUG [Source=TextLoader; Binding, Kind=Trace] Channel finished. Elapsed 00:00:00.0095776. (Microsoft.ML.CLI.Runners.AutoMLRunner.Instance_DiagnosticDataReceived)
2022-12-06 13:02:43.8279 DEBUG [Source=TextLoader; Binding, Kind=Trace] Channel disposed (Microsoft.ML.CLI.Runners.AutoMLRunner.Instance_DiagnosticDataReceived)
2022-12-06 13:02:43.8584 ERROR System.NotImplementedException: The method or operation is not implemented.
at Microsoft.ML.ModelBuilder.AutoMLService.Experiments.ExperimentFactory.CreateExperiment(MLContext context, ITrainingConfiguration config, AutoMLDependService services, PathConfiguration pathConfig) in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/ExperimentFactory.cs:line 36
at Microsoft.ML.ModelBuilder.AutoMLEngine.StartTrainingAsync(ITrainingConfiguration config, PathConfiguration pathConfig, CancellationToken userCancellationToken) in //src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 135
at Microsoft.ML.CLI.Runners.AutoMLRunner.ExecuteAsync() in //src/mlnet/Runners/AutoMLRunner.cs:line 89
at Microsoft.ML.CLI.Program.TrainAsync(TrainingConfiguration trainingConfiguration, PathConfiguration pathConfig, AutoMLServiceLogLevel logLevel) in //src/mlnet/Program.cs:line 349
at Microsoft.ML.CLI.Program.AutoMLCommandRunner(AutoMLCommand command, Boolean skipGenerateConsoleApp) in //src/mlnet/Program.cs:line 330
at Microsoft.ML.CLI.Program.<>c.<b__4_0>d.MoveNext() in //src/mlnet/Program.cs:line 90
--- End of stack trace from previous location ---
at System.CommandLine.Invocation.CommandHandler.GetExitCodeAsync(Object value, InvocationContext context)
at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.ML.CLI.Program.<>c__DisplayClass4_0.<b__9>d.MoveNext() in //src/mlnet/Program.cs:line 291
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<b__0>d.MoveNext() (Microsoft.ML.CLI.Program+<>c__DisplayClass4_0.b__7)
2022-12-06 13:02:43.8677 DEBUG System.NotImplementedException: The method or operation is not implemented.
at Microsoft.ML.ModelBuilder.AutoMLService.Experiments.ExperimentFactory.CreateExperiment(MLContext context, ITrainingConfiguration config, AutoMLDependService services, PathConfiguration pathConfig) in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/ExperimentFactory.cs:line 36
at Microsoft.ML.ModelBuilder.AutoMLEngine.StartTrainingAsync(ITrainingConfiguration config, PathConfiguration pathConfig, CancellationToken userCancellationToken) in //src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 135
at Microsoft.ML.CLI.Runners.AutoMLRunner.ExecuteAsync() in //src/mlnet/Runners/AutoMLRunner.cs:line 89
at Microsoft.ML.CLI.Program.TrainAsync(TrainingConfiguration trainingConfiguration, PathConfiguration pathConfig, AutoMLServiceLogLevel logLevel) in //src/mlnet/Program.cs:line 349
at Microsoft.ML.CLI.Program.AutoMLCommandRunner(AutoMLCommand command, Boolean skipGenerateConsoleApp) in //src/mlnet/Program.cs:line 330
at Microsoft.ML.CLI.Program.<>c.<b__4_0>d.MoveNext() in //src/mlnet/Program.cs:line 90
--- End of stack trace from previous location ---
at System.CommandLine.Invocation.CommandHandler.GetExitCodeAsync(Object value, InvocationContext context)
at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.ML.CLI.Program.<>c__DisplayClass4_0.<b__9>d.MoveNext() in /_/src/mlnet/Program.cs:line 291
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<b__0>d.MoveNext() (Microsoft.ML.CLI.Program+<>c__DisplayClass4_0.b__7)
2022-12-06 13:02:43.8677 INFO Check out log file for more information: C:\Users\bddev\AppData\Local\Temp\mlnet\log.txt (Microsoft.ML.CLI.Program+<>c__DisplayClass4_0.b__7)
2022-12-06 13:02:43.8677 INFO Exiting ... (Microsoft.ML.CLI.Program+<>c__DisplayClass4_0.b__7)

@gbanuk2  sorry for hitting this issue!
@LittleLittleCloud   I think this is CLI issue,  do you have context about ?

I'm not sure what else I can post. I tried installing the tools on a new system and have the same issue. I installed the tool like so:
dotnet tool install --global mlnet-win-x64
Also installed the .NET6.0 SDK
C:\pubtemp>dotnet --list-sdks
6.0.403 [C:\Program Files\dotnet\sdk]
7.0.100 [C:\Program Files\dotnet\sdk]
I installed visual studio 17.4.2 community.

@gbanuk2  the latest ml.net is 2.0,  @LittleLittleCloud  knows more about how CLI works with ml.net 2.0.

So I copied mlnet version (16.13.9+3066041f1761935763bdd267a9bcbb64cb3ec543) from a working system to the new system and it works fine. I can train files again. So something changed in the 16.14 version that causes it to crash.

Hello! I have the same issue.

We will soon push a fix (version 16.14.1) for this issue.

16.15.1 still has this problem. I just downgraded it to version 16.13.4 and it works fine.


i can see fuction HtmlHttpImageGetter(htmlTextView));

i use version 1.0.2 , i can see fuction HtmlHttpImageGetter(htmlTextView)), can you help me?

Sry, this wasn't released. Please try using version 2.0 now.