GMYLE Bluetooth Dongle Plugged in, still getting "NOT OK. Your hardware doesn't support Bluetooth 4.0"

I'm on a mid 2010 MacBook pro, running OSX 10.11.2.
I've got my GMYLE BL 4.0 dongle plugged in, and CAT consistently reports my hardware as not supporting it. The relevant line from running the tool:
"NOT OK.  Aborting."
The diagnostic tool reports the same V=4/expected 6 issue. I've tried this with my system bluetooth turned on and off. The tool will detect when I unplug/replug the dongle, yet it still produces this error.
Am I missing something? What am I doing wrong here? Thanks!

Open System Information and go to Bluetooth. Whats you LMP Version there?

Apple Bluetooth Software Version:	4.4.3f4 16616
Hardware, Features, and Settings:
Address:	00-00-00-00-00-00
Bluetooth Low Energy Supported:	No
Handoff Supported:	No
Instant Hot Spot Supported:	No
Manufacturer:	Ericsson
Transport:	USB
Firmware Version:	0.15216 (0.0)
Bluetooth Power:	Off
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x05AC
Product ID:	0x8218
HCI Version:	0x0
HCI Revision:	0x3B70
LMP Version:	0x0
LMP Subversion:	0x00
Auto Seek Keyboard:	On

It seems like your dongle is either not correctly recognized or you've got the wrong dongle. Your Manufacturer should be Broadcom.

Will this dongle work with my MacPro 12 Core (Mid 2010) ?
http://www.ebay.com/itm/GMYLE-Ultra-Mini-USB-Broadcom-Bluetooth-Adapter-Dongle-Class-2-V4-0-Dual-Mode-/151811980079?hash=item2358b2fb2f:g:GaMAAOSw~gRV4UMW
I want to buy it today once I know it's the right one and that it will work. I have an ASUS dongle... but no luck with that.
Regards,
Anthony

It's definitely the right dongle. After turning off bluetooth in my statusbar, and unplugging/replugging the dongle and looking at the Bluetooth page, it now reads broadcom and LMP version 6:
Apple Bluetooth Software Version:	4.4.3f4 16616
Hardware, Features, and Settings:
Name:	Colin Hart’s MacBook Pro
Address:	5C-F3-70-71-FA-4A
Bluetooth Low Energy Supported:	Yes
Handoff Supported:	No
Instant Hot Spot Supported:	No
Manufacturer:	Broadcom
Transport:	USB
Chipset:	2070B0
Firmware Version:	v14 c4096
Bluetooth Power:	Off
Discoverable:	On
Connectable:	Yes
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x0A5C
Product ID:	0x21E8
HCI Version:	0x6
HCI Revision:	0x1000
LMP Version:	0x6
LMP Subversion:	0x220E
Device Type (Major):	Computer
Device Type (Complete):	Mac Portable
Composite Class Of Device:	0x38010C
Device Class (Major):	0x01
Device Class (Minor):	0x03
Service Class:	0x1C0
Auto Seek Keyboard:	On
Going to disable SIP and try this all again.

It worked, awesome!
Apple Bluetooth Software Version:	4.4.3f4 16616
Hardware, Features, and Settings:
Bluetooth Low Energy Supported:	Yes
Handoff Supported:	Yes
Instant Hot Spot Supported:	Yes
Manufacturer:	Broadcom
Transport:	USB
Chipset:	Unknown (ffff)
Firmware Version:	v14 c4096
Bluetooth Power:	Off
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x0A5C
Product ID:	0x21E8
HCI Version:	0x6
HCI Revision:	0x1000
LMP Version:	0x6
LMP Subversion:	0x220E
Auto Seek Keyboard:	On
Now to turn Bluetooth back on in the status bar and see if my trackpad and keyboard connect...

Hi Holincart.... I have a MacPro 12 Core (Mid 2010) running El Capitan 11.2.3. I used to have CAT running perfectly on Yosemite with my ASUS Bluetooth 4.0 Dongle, but ever since I upgraded to El Capitan the CAT has been broken.
Could you send me a link to the dongle that you purchased to get CAT to work on El Capitan... and could you tell me where to download the very latest version of the CAT software with all the latest patch updates... and how you can turn SIP off..?
Regards,
Anthony

I bought this dongle: http://www.amazon.com/gp/product/B010NISKFK
CAT itself works, after I did the steps I mentioned above. I haven't had the chance to fully determine whether or not continuity itself is operating properly (though the OS lets me activate it now).
The SIP instructions are found in the main readme of this project:
https://github.com/dokterdok/Continuity-Activation-Tool#cant-open-the-tool

holincart Did you try CAT and GMYLE on 10.11.3?

I bought a BT dongle off amazon based on the correct 4.0 broadcom chipset.. a UD-400M
it shows the same incompatibility notice as mentioned above.. here is the system profile info with SIP back on and CAT not installed, since it won't.....  apple BT off, dongle plugged in...
product IDs are different.. perhaps it can be added or overridden?
thanks
\  Apple Bluetooth Software Version:	4.4.3f4 16616
Hardware, Features, and Settings:
Name:
Address:
Bluetooth Low Energy Supported:	No
Handoff Supported:	No
Instant Hot Spot Supported:	No
Manufacturer:	Broadcom
Transport:	USB
Chipset:	2046
Firmware Version:	v208 c522
Bluetooth Power:	Off
Discoverable:	On
Connectable:	Yes
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x05AC
Product ID:	0x8213
HCI Version:	0x4
HCI Revision:	0x20A
LMP Version:	0x4
LMP Subversion:	0x21D0
Device Type (Major):	Computer
Device Type (Complete):	Mac Portable
Composite Class Of Device:	0x38010C
Device Class (Major):	0x01
Device Class (Minor):	0x03
Service Class:	0x1C0
Auto Seek Keyboard:	On  Apple Bluetooth Software Version:	4.4.3f4 16616
Hardware, Features, and Settings:
Name:
Address:
Bluetooth Low Energy Supported:	No
Handoff Supported:	No
Instant Hot Spot Supported:	No
Manufacturer:	Broadcom
Transport:	USB
Chipset:	2046
Firmware Version:	v208 c522
Bluetooth Power:	Off
Discoverable:	On
Connectable:	Yes
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x05AC
Product ID:	0x8213
HCI Version:	0x4
HCI Revision:	0x20A
LMP Version:	0x4
LMP Subversion:	0x21D0
Device Type (Major):	Computer
Device Type (Complete):	Mac Portable
Composite Class Of Device:	0x38010C
Device Class (Major):	0x01
Device Class (Minor):	0x03
Service Class:	0x1C0
Auto Seek Keyboard:	On

duecedriver What is UD-400M? Is it asus?
When you plug in dongle what is the system profiler info?

yeah sorry about that .. realized after sending yesterday that even with the bluetooth switched off.. the bluetooth in system reports is the apple board...
here is what shows up in the usb bus...
this is the dongle...
BCM20702A0:
Product ID:	0x21ec
Vendor ID:	0x0a5c  (Broadcom Corp.)
Version:	1.12
Serial Number:<PHONE_NUMBER>71
Manufacturer:	Broadcom Corp
Location ID:	0x06200000
this is the entire UBS bus hub with apples built in board on it as well...

Try to:
Load system without dongle
Switch of bluetooth
Turn of computer
Insert dongle
Turn on computer
Turn on bluetooth
System profiler must show Bluetooth Low energy support - Yes. Handoff and Instant Hotspot are not supported. If you got it - you are ready to apply CAT.

yeah.. I think that is the problem.. this dongle shows the correct chipset and manufacturer but I think the device/product id is not in the apple bluetooth kext and won't load?  I tired what others have done.. shut off the bluetooth unplug and replug.. but not via reboots..
can you confirm that my device id's are in the apple plist?

I cannot. Basically chipset is important. One more time. When you plug in dongle what does the system profiler say? You have gmyle dongle, haven't you?

I posted it above..
BCM20702A0:
Product ID: 0x21ec
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.12
Serial Number:
Manufacturer: Broadcom Corp
Location ID: 0x06200000
it shows broadloom
its the correct chipset but the id's have to match what is in apples kexts for them to load for the device.
when bought on amazon it said gmyle but its not on the package.. just that its 4.0 + EDR BCM20702
my guess is that the CAT tool would have to inject the 0x21ec id into the proper kext for it to work.

I have the same UD-400M dongle and I too cannot get it to work. I spent some time messing around with the BrcmPatchRAM tool ([https://github.com/the-darkvoid/BrcmPatchRAM]), but this didn't seem to do anything either.
I've been through the suggested steps above with no success. Does anyone have any other ideas I can try?
Thanks.

that 21ec hex is not the device ID that these working broadcom dongles are using and that is expected by the apple kext, hence its not loading...
with sip we cant just go and exit the kext to insert the new ID since it will no longer pass signing as I understand it.  it must me injected at the time the pre linked kernel in being built but that is beyond my abilities..
for the 10 bucks I wasted probably buying the right one is easiest solution, but given the poor advertising on amazon, I thought this was the right one as someone in the reviews said it was a gymle..

According to the BrcmPatchRAM site it should be possible to edit that hex value. I couldn't get it to work though.

I've installed the listed Broadcom Wi-Fi chip in my 2011 iMac, which previously had Atheros. I cannot get my system to recognize the GBU521 dongle though. I am getting the same line in CAT:
"NOT OK.  Aborting."
@mobile4, I've done the steps you listed, but 4.0 is still not loading.
One thing I can think of, I didn't disconnect any wires from the stock bluetooth chip, I only swapped the the Atheros for the Broadcom Wi-Fi, which reads fine.
Is it necessary to disconnect the stock bluetooth wires as well? My system seems to be loading the 2.1 chip instead of the 4.0 dongle.

@archaik yes disconnecting the old chip should solve this. As you've already concluded, any other connected bluetooth chip/device could cause problems and should therefore be disconnected.

Thank you

For those still having issues with "NOT OK. Your hardware doesn't support Bluetooth 4.0", this may be of some help. I solved my problem without opening my iMac.
The key was to download the Bluetooth Explorer app from Developer Tools for Xcode, from Apple.
Here's a link to get that done: http://www.geekguides.co.uk/414/how-to-select-a-bluetooth-adapter-in-os-x/
Once you've gone through the steps in the above article and selected your Broadcom Bluetooth dongle, once you restart your Mac, and run system diagnostics for CAT, you should no longer see the "NOT OK" error. As long as you keep the bluetooth dongle plugged in, the Bluetooth Explorer should keep your bluetooth loading to the dongle, not your internal 2.0 bluetooth.
Hopes this helps!

for me and this particular dongle.. it was not that the original built in bluetooth was blocking activation as my other systems that are osx and dont have bluetooth would fail to load it as a bluetooth device also, stilll points to the device id not loading the kext.. if this tool fixes that it would be easier than having to edit plists and such.. although what kind of overhead is there having to have this tool always running in the background..

i don't know if it's a fluke just for me, because i see now the tool says "the change will NOT last after a restart," but to my knowledge, it isn't running in the background, and it DOES keep your desired bluetooth selection after restart. no maintenance required.
worth a shot.

nvm. !!! it reverted back on it's own sometime since yesterday. thought it was all good after many restarts.

I Have a message for deucedriver, please shoot me an email.  Thanks
<EMAIL_ADDRESS>

If you, like I, end up getting the UD-400M (marketed as GMYLE, though I don't think it actually is), you've been scammed.  This is a Bluetooth 2.1 device marketed as a 4.0 device.  This is why it will not work.

Are you sure dougc84? How did you figure that out?
I'll plug mine into a Windows PC tomorrow and see what it detected.

OK, as promised I have plugged my UD-400M into a Windows PC and it definitely:

Works
Is a Bluetooth 4.0 device

Any other ideas out there please?

Then it's a mismatch of drivers.  On OS X, it is reported as a Bluetooth 2.1 device with no low power mode.  It's also branded as + EDR, which does not exist on 4.0.  My guess is there has to be some sort of driver trickery used on certain devices to activate its 4.0 abilities, none of which are available on OS X.
For the record, the IOGEAR one rocks.

UD-400M Same problem, any update for this?

I bought the GMYLE from eBay here  but I received a USB Bluetooth dongle packaged as a UD-400M. I'm having no luck with Out-of-box compatibility like the folks here. Same problems as described above.. please, somebody tell me they've got it working. I've emailed the seller and even GMYLE about my situation but have yet to hear anything positive back. I hope someone with this dongle has got it working...
It only shows up in my system profile under "USB" as:
BCM20702A0:
Product ID:	0x21ec
Vendor ID:	0x0a5c  (Broadcom Corp.)
Version:	1.12
Serial Number:	001986000F56
Speed:	Up to 12 Mb/sec
Manufacturer:	Broadcom Corp
Location ID:	0x1d100000 / 1
Current Available (mA):	500
Extra Operating Current (mA):	0

@YogaFlame - try cycling Bluetooth on & off in Apple Logo -> System Preferences until you see in Apple Logo -> System Report -> Bluetooth -> Bluetooth Low Energy Supported: YES
Then return to the CAT tool and re-run it;
Failing that, get the Cambridge Silicon Radio (CSR4.0) dongle - its cheap as chips and works for me!
Sent from my iPad

On 27 Nov 2016, at 15:15, YogaFlame<EMAIL_ADDRESS>wrote:
I bought the GMYLE from eBay here but I received a USB Bluetooth dongle packaged as a UD-400M. I'm having no luck with Out-of-box compatibility like the folks here. Same problems as described above.. please, somebody tell me they've got it working. I've emailed the seller and even GMYLE about my situation but have yet to hear anything positive back. I hope someone with this dongle has got it working...
It only shows up in my system profile under "USB" as:
BCM20702A0:
Product ID:	0x21ec
Vendor ID:	0x0a5c (Broadcom Corp.)
Version:	1.12
Serial Number:	001986000F56
Speed:	Up to 12 Mb/sec
Manufacturer:	Broadcom Corp
Location ID:	0x1d100000 / 1
Current Available (mA):	500
Extra Operating Current (mA):	0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just to update everyone on the GMYLE / UD-400M issue I've had. I've confirmed it does not work on my Mac Pro running Sierra 10.12.1. I got a statement back from GMYLE stating their device is not supported under OSX and they have updated their product descriptions accordingly. Strange... because their site did say it supported OSX (it is now gone).
I looked at the IOGEAR GBU521 but they don't officially support OSX either and although I see people saying it works on El Cap, I don't see anyone saying it works on Sierra so that makes me nervous. @dougc84 - Can you confirm this?
@airmanchairman, if you can recommend a CSR dongle that you know would work on my Early '09 Mac Pro running 10.12.1, please let me know. There's so many different kinds out there and after this experience, I'm wary of taking any kind of purchase risk again.
Thanks

@YogaFlame The IOGEAR GBU521 is what I have, and while it's ugly as sin sticking out of the side of my MacBook, it definitely works.  I'm on 10.12.1, and it works just fine.  Actually, since Sierra came out, Handoff has been even more reliable.

Do you need an airport wifi card to get the GMYLE from eBay to work?

I'm using CSR 4.0 Dongle but it says handoff not supported , what should I do
Apple Bluetooth Software Version:	6.0.7f10
Hardware, Features, and Settings:
Name:      MacBook Pro
Address:	00-1A-7D-DA-71-13
Bluetooth Low Energy Supported:	Yes
Handoff Supported:	No
Instant Hot Spot Supported:	No
Manufacturer:	Cambridge Silicon Radio
Transport:	USB
Firmware Version:	8891
Bluetooth Power:	On
Discoverable:	Off
Connectable:	Yes
Auto Seek Pointing:	On
Remote wake:	On
Vendor ID:	0x0A12
Product ID:	0x0001
HCI Version:	4.0 (0x6)
HCI Revision:	0x22BB
LMP Version:	4.0 (0x6)
LMP Subversion:	0x22BB
Device Type (Major):	Computer
Device Type (Complete):	Mac Portable
Composite Class Of Device:	0x38010C
Device Class (Major):	0x01
Device Class (Minor):	0x03
Service Class:	0x1C0
Auto Seek Keyboard:	On


Please Delete this Issue

There is no issue here. Need to delete.

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

ID: 1220843e-8e78-cbd8-3407-8f73d833f446
Version Independent ID: e5d5272d-50c8-d1dd-1293-e6c0c6a6335f
Content: Quickstart: Run a Spark job on Azure Databricks using Resource Manager template
Content Source: articles/azure-databricks/quickstart-create-databricks-workspace-resource-manager-template.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

I'm wrong. There is a button that has a template behind it.

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


next() function not documented

The next() method is everywhere in your docs, it's quite clear that passes control to the next 'action' but it's definitely not documented itself. Where does it come from?

@stratboy next in described on http://expressjs.com/guide/using-middleware.html.
@crandmck do you think we should create a page dedicated to explaining next?

@stratboy makes a good point.
Although that article does explain how to use next() and the requirement to use it to pass control to the next middleware, it doesn't really explain "where it comes from", and a new user might assume that it's actually part of the API, either in Express or Node.
However, IIUC, it's merely a naming convention based on the arguments to the callback function.  In theory it could have any name, but almost universal convention is to call it "next"... right?
This seems to be a common question, based on these SO topics:

http://stackoverflow.com/questions/5384526/javascript-node-js-next
http://stackoverflow.com/questions/13133071/express-next-function-what-is-it-really-for
http://stackoverflow.com/questions/10695629/node-js-express-next
etc. etc.

I think it would be helpful for new developers to provide a bit more explanation and clarity.  I don't think it needs its own page; rather, I suggest that we add a section to http://expressjs.com/guide/using-middleware.html (or perhaps in http://expressjs.com/guide/writing-middleware.html) and then cross-reference it whenever we mention using next() (e.g. http://expressjs.com/guide/error-handling.html, http://expressjs.com/guide/routing.html, etc.)
Thoughts?

Yes, I'm with you, only add the section, and one line to explain just what you explained below, it's enough.
Thank you, regards,
Luca
Rand McKinney wrote:

@stratboy https://github.com/stratboy makes a good point.
Although that article does explain how to use |next()| and the
requirement to use it to pass control to the next middleware, it
doesn't really explain "where it comes from", and a new user might
assume that it's actually part of the API, either in Express or Node.
However, IIUC, it's merely a naming convention based on the arguments
to the callback function. In theory it could have any name, but almost
universal convention is to call it "next"... right?
This seems to be a common question, based on these SO topics:

http://stackoverflow.com/questions/5384526/javascript-node-js-next
http://stackoverflow.com/questions/13133071/express-next-function-what-is-it-really-for
http://stackoverflow.com/questions/10695629/node-js-express-next
etc. etc.

I think it would be helpful for new developers to provide a bit more
explanation and clarity. I don't think it needs its own page; rather,
I suggest that we add a section to
http://expressjs.com/guide/using-middleware.html (or perhaps in
http://expressjs.com/guide/writing-middleware.html) and then
cross-reference it whenever we mention using |next()| (e.g.
http://expressjs.com/guide/error-handling.html,
http://expressjs.com/guide/routing.html, etc.)
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/strongloop/expressjs.com/issues/478#issuecomment-151947626.

Ok, then I think it should be mentioned and briefly explained even on
the API reference page, maybe somewhere in the app section, where you
mainly write about middlewares. Maybe a title like 'about the next()
callback' or 'Passing control with next()' or something.
Thank you, regards
Luca
Hage Yaapa ha scritto:

@stratboy https://github.com/stratboy |next| in described on
http://expressjs.com/guide/using-middleware.html.
@crandmck https://github.com/crandmck do you think we should create a
page dedicated to explaining |next|?
—
Reply to this email directly or view it on GitHub
https://github.com/strongloop/expressjs.com/issues/478#issuecomment-151936632.

I believe this has been addressed, so I will close.
@stratboy Thanks for bringing it up.

:) thank you


Guide says you can run Mocha from HBC, then doesn't follow up

Section 3 of the guide says "Note: If you are unable to buy a DS VC title, you can still run Mocha CFW from the Homebrew Channel."
However, every single part of the guide after that assumes that your running Haxchi.  I have absolutely no idea what to do in part 4, for instance, if I am not using Haxchi.
Also, I really wish there was a part of the guide "Upgrading from Loadiine".  For instance, can I use my SD card with Loadiine-ready games with MochaCFW?  (And will I keep my saves?)

I fixed all that for you.
I'm not going to write an "Upgrading from Loadiine" section, as it's not really necessary. It's just an app, and you can't easily just convert games for the Brazilian method (It's possible, but it's not so much of a super user friendly process yet). You're better off getting games again from NUSGrabbers anyways.
In terms of using your saves again, it's possible. I moved all my various other tutorials to the WiiUHacks wiki which is linked on the homepage, and the sidebar.


Correctly spell GitLab

s/Gitlab/GitLab

The assertions in unit tests have to be updated as well because they are broken now.

@fguillot ready!


Component: ActionSet, Action, ActionSpacer

issue: #123
Testing

Run yarn storybook
Go to http://localhost:6006/
You should see this:
https://user-images.githubusercontent.com/90475219/139957407-85c55ed8-eafc-4474-950c-7703829c9ad2.mov

Note
The Actions currently does not show the action when you click on each action. This will be further discussed.

@rmshopify I was just looking at this again. It looks like you're missing a top-level index.ts to export ActionSet.


Track "Opted-Out" Users

We must collect the emails of users who choose to opt-out. These should be easy to aggregate and deliver to customer success for followup.
Dependent on answer to "Opt out" question (#1422)

@davidangb If we are storing the opt-out decision in thurloue per #1422, and Thurloe values are in BigQuery, is there anything to actually do here?

Brad will confirm with Alex that this is a no-op from the Terra perspective

Confirmed it as a no-op. Closing this story as "invalid" because there turns out to be nothing to do


document filter expression

Documents the filterExpression option in the DynamoIndexQueryIterator.

Codecov Report
Patch and project coverage have no change.

Comparison is base (bb6911d) 96.77% compared to head (5efd970) 96.77%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #24   +/-   ##
=======================================
  Coverage   96.77%   96.77%
=======================================
  Files          74       74
  Lines        1552     1552
=======================================
  Hits         1502     1502
  Misses         50       50

Files Changed
Coverage Δ

DynamoIndexQueryIterator.js
100.00% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Remove Atom from editors readme

The editor is no longer maintained, and the package link no longer works.

@swift-ci Please test


target cross platform support

hello, it looks like you do not support different targets, like, I want to support cross compiling for linux, android, windows, etc, so, currently I'm doing
FFMPEG_LIBS_DIR=/home/dev/project/deps/ffmpeg/build/linux/x86_64/lib/pkgconfig \
FFMPEG_INCLUDE_DIR=/home/dev/project/deps/ffmpeg/build/linux/x86_64/include

I could set each one before building, but wouldn't it be better to make something more automated where it can support all types?

Writing xtask scripts is always suggested if you have complex environment variables set for rust project. If you find it complex, hardcode the env var in project build script(cfged by target_os) should also work.

but wouldn't it be better to make something more automated where it can support all types?

Providing env vars for rsmpeg build script is the best option I can think of. Any suggestion?

Feel free to reopen this issue if it doesn't meet your expection. :-)


GDAX Parsing not working

For some reason GDAX parsing does not work (ie. the high bid and low ask does not line up with the GDAX website high bid and low ask), this could be for a number of reasons, namely, incorrect mapParsing, incorrect data parsing, or a host of other reasons.

Is this still an issue? Seems to be fine on my end. Can you post a screenshot of a reproduction of the erroneous values?

Fixed it in my new branch, not sure where I was going wrong with Level 3 Orderbook parsing, but it works fine with Level 2.


Black screen on Quest3's end

Description

Quest connects to the host with no problems, all data sans video is streamed. The video is just a black screen on the quests end.
steamVR throws the error, -202: Make sure your headset's display is in full screen mode.

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment
Hardware
Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
CPU: Intel i5-9300H (8) @ 4.100GHz
GPU: NVIDIA GeForce GTX 1650 Mobile
GPU Driver Version: Nvidia-driver-545
Audio: Pipewire ?
Installation
ALVR Version: v20.6.0
ALVR Settings File:
SteamVR Version:
Install Type:

[ ] Packaged (exe, deb, rpm, etc)
[x] Portable (zip)
[ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions): Pop!_OS 22.04 LTS

I had the same issue (I have the same gpu), and given that it is the mobile gpu I’d assume you also have an igpu
If running an integrated GPU with an Nvidia GPU add this into the launch options of SteamVR:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%

I had the same issue (I have the same gpu), and given that it is the mobile gpu I’d assume you also have an igpu
If running an integrated GPU with an Nvidia GPU add this into the launch options of SteamVR: VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%
That should fix the black screen issue

Thank you, that works!


Provide a standard list of variables for toggling

What problem does your feature request solve?

Typing in field names is a laborious process, fraught with the the risk of typos. and frustrated with the inadequacy of rose edit's lists.
Describe the solution you'd like

Provide a pre-populated list of common fields that can be toggled on or off. This could just be specific field names, or it could be more general concepts that maps to both UM and LFRic field names. An option should be provided for manual input to deal with rare or custom fields however.
Describe alternatives you've considered

Maybe a seperate ticket, but it would be useful to provide different lists to different models, even when they use the same recipe, to allow of UM vs. LFRic comparisons.
Questions
Is there a standard set of model variables?

Could this be done via a dictionary? This could alos allow introducing more intelligence into the variable picking such as with i.e. precipitation, where users should in some case add fields together and not look at the individual stash codes? Problem would be that we need to keep the dictionary updated.
Also, we would still keep an element of frustration if variables appear in pre-populated dropdown menues, but they are not actually in the file.
So should they only be pre-populated if  found in a file following the fetch task?

Unfortunately we have not fetched any data when we are presenting this list (in rose edit), which makes it difficult to know what can be enabled.


Kubenretes node cannot connect kube-apiserver by vip and 8443 port

Describe the bug
Kuberentes cluster architecture is 3 master (control panel) and 3 worker nodes , When I restart one of the master nodes, it will appear that the working node cannot connect to the kube-apiserver, the node to be unready status, Viewing the kubelet log shows that the connection kube-apiserver timed out, When I reboot the node I am able to restore the connection again
To Reproduce
Steps to reproduce the behavior:
Restart one of the master nodes
Expected behavior
When I restart the master node all the worker nodes can connect kube-apiserver
Screenshots
kubelet[1279]: E0131 11:13:54.806663    1279 kubelet_node_status.go:402] Error updating node status, will retry: error getting node "node1": Get https://xxx.xx.xxx.4:8443/api/v1/nodes/node1?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
If I switch master node ip (xxx.xx.xxx.1) and 6443 port connect is ok.
Environment (please complete the following information):

OS/Distro:  CentOS Linux 7 (5.4.210-1.el7.elrepo.x86_64)
Kubernetes Version: v1.18.20
Kube-vip Version: v0.1.1

Kube-vip.yaml:
localPeer:
id: xxx.xx.xxx.1
address: xxx.xx.xxx.1
port: 10000
remotePeers:

id: xxx.xx.xxx.2
address: xxx.xx.xxx.2
port: 10000
id: xxx.xx.xxx.3
address: xxx.xx.xxx.3
port: 10000
vip: xxx.xx.xxx.4
gratuitousARP: true
singleNode: false
startAsLeader: false
interface: ensxx
loadBalancers:
name: API Server Load Balancer
type: tcp
port: 8443
bindToVip: true
backends:

port: 6443
address: xxx.xx.xxx.2
port: 6443
address: xxx.xx.xxx.1
port: 6443
address: xxx.xx.xxx.3

name: ingress Load Balancer
type: tcp
port: 80
bindToVip: true
backends:

port: 8080
address: xxx.xx.xxx.2
port: 8080
address: xxx.xx.xxx.1
port: 8080
address: xxx.xx.xxx.3

Additional context
Add any other context about the problem here.

Hey thanks,
This is from a really really old version of kube-vip, all of the internal load-balancing and HA logic has completely changed since then. You should be able to do an inplace upgrade.

Hey thanks,
This is from a really really old version of kube-vip, all of the internal load-balancing and HA logic has completely changed since then. You should be able to do an inplace upgrade.

I try it upgrade 0.3.5, when restarted vip on master node occur the same issue.

Hey @thebsdbox thanks, I solved it after update to 0.4.0 release of kube-vip


Callback URL Resolver for FormClient loginUrl

Apply the callback url resolver to the loginUrl field of org.pac4j.http.client.indirect.FormClient to dynamically generate URLS with the appropriate host and context root.
Without this this functionality, the context root must be specified for the field. In configurations with static config files (for example Shiro ini) this does not allow the application to be deployed with different context roots.

Thanks. Would you mind submitting a pull request for that?


ENH: Add FA-based IQMs (nans percentage and degenerate percentage)

Percentage of brain volume.
Related: #1216.

Moved to parts per million instead of %


Windows10Universal,exe not detected

Im not sure if im doing something wrong, but already gotten all permissions to WindosApps and file can be found at:
"C:\Program Files\WindowsApps\ROBLOXCORPORATION.ROBLOX_2.604.491.0_x64__55nm5eh3cm0pr\Windows10Universal.exe"
Trying to run manually Windows10Universal.exe gives the error given in second image.
Have compiled as Release x86
Im really newbie to injection tools or even VS projects, but im pretty sure that i've done everything right following read me file
Any clue?

All PC exploits are patched...

We can't fix
This is not fixable, since the game from the UWP version added Hyperion with the introduction of their x64 bit version


Proper Angular support

Description
It seems like Angular module compatibility has been broken after forking openapi-typescript-codegen. Previously, we used --name flag to set a module name that would contain all the services, and we could utilize OpenAPI and BaseHttpClient as injection tokens, which is a common way of doing configuration in Angular.
However, when generating the client via code (using createClient and setting UserConfig), there is no way of creating a module, thus not having the ability to use injection tokens at all.
I haven't seen any mentions of that topic in the changelog, so I'm curious if was that made on purpose or by mistake.
Btw. is there any ongoing effort to create an Angular plugin?

@mightymatth Can you share your config?

My config is irrelevant in this context. I'm just asking why name property is deprecated in ClientConfig. If something is deprecated, it should be noted what to use instead. If I understood the idea, you're making separate libraries for each client, and only in that case, name is deprecated.
So, can we still use name if using a legacy Angular client?

hi there any news on this? I was happy with the older version because they support Angular, but now I see a lot of development going on but the angular generator is stuck to an older version.
Is there any plan about adding a new @hey-api/client-angular or should we consider Angular support as something legacy/dead?
And if it's legacy/dead, does anybody know if the fetch client is compatible with $httpService without breaking an existing angular application and without loosing the "advantages" of using $httpService over fetch()?

If there was more interest in Angular support it would get prioritised, but that's not the case right now @lamuertepeluda. I am definitely open to pull requests fixing any of the broken functionality. Sadly, I don't have a good overview of the state of the support for Angular at the moment because as you correctly noted, it has not been my focus.
@mightymatth feel free to use name as long as it's available. There's a discussion around its usage https://github.com/hey-api/openapi-ts/discussions/619, I need to understand for what use cases it's currently being used before removing it. And, of course, those use cases will need to be migrated or explicitly unhandled. For now it's a warning to get people to react.
tl;dr Angular support is not currently maintained for new features. If it works with any new features, that's a happy accident, but it's not being tested against them. If Angular became broken, please let me know what broke and I will try to fix. The goal is to keep Angular working as before, definitely not trying to kill it.


C128 type in XlaRuntimeError when Float64 is used: "Element type C128 is not supported on TPU"

Description
When creating an array with dtype=jnp.float64 and passing this to Jax's lax.fft and fft.fft functions, an error is generated that indicates an element type of C128 was passed in.
XlaRuntimeError: INVALID_ARGUMENT: Element type C128 is not supported on TPU.

Here is a reproducible notebook: https://www.kaggle.com/zyrellla/c128-error
What jax/jaxlib version are you using?
jax 0.4.17 jaxlib 0.4.17 and jax 0.4.4 jaxlib 0.4.4
Which accelerator(s) are you using?
TPU
Additional system info?
1.26.3 3.10.13 (main, Jan 17 2024, 06:53:56) [GCC 12.2.0] uname_result(system='Linux', node='a77b3ba272f3', release='6.1.75+', version='#1 SMP PREEMPT_DYNAMIC Sat Feb 10 15:23:41 UTC 2024', machine='x86_64')
NVIDIA GPU info
No response

Hi - thanks for the report! FFT operations require complex inputs, and when you input 64-bit floats, the corresponding complex type is complex128.
As for why this is erroring: TPU does not have support for many 64-bit operations. If you're working on TPU, we generally would suggest using the default jax_enable_x64=False setting, to limit all operations to 32-bit.
Hope that helps!


为何不能用input.elasticsearch 对 aws opensearch的监控？

What would you like to be added:
Why is this needed:
Describe the solution you'd like
Additional context

已经解决，参数配置问题


SQL - CREATE SEQUENCE not working

As I know from documentation, OrientDB will support sequences since version 2.2.
http://orientdb.com/docs/last/SQL-Create-Sequence.html
I downloaded 2.2 alpha to test this feature and came across following error when executed SQL code from the documentaion:
CREATE SEQUENCE idseq

The error is:
com.orientechnologies.orient.core.command.OCommandExecutorNotFoundException: Cannot find a command executor for the command request: sql.CREATE SEQUENCE idseq

Hi @Dalamar
where did you get 2.2? Is it a snapshot version or did you build it from sources?
I tried it building from "develop" branch and I get a different error (a null pointer) just because it needs sequence type, but adding it the statement works fine:
create sequence idseq type ORDERED

I'm going to fix docs about this
Please share some additional details, so that I can reproduce the problem
Thanks
Luigi

Hi @luigidellaquila
I got 2.2 alpha from here http://orientdb.com/download/
Download the experimental OrientDB 2.2-alpha.
The download link is as follows:
<EMAIL_ADDRESS>

Ah, ok, that's a quite old alpha, probably sequences were not available yet at that time.
I suggest you to try a snapshot:
https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/2.2.0-SNAPSHOT/
I'm closing this issue (docs updated), please reopen in case you have other problems
Thanks
Luigi


200 to 250

this is supposed to fix issue #7

This pull request includes a small change to the Message class in the RazorPagesTestSample application. The change increases the character limit for messages.

src/Application/src/RazorPagesTestSample/Data/Message.cs: Increased the character limit for the Text property from 200 to 250.


Config: expose swap finality parameters

This PR introduce a new section[swap...] in the config file farcasterd.toml. The swap section, for now, contains finality and safety parameters per chain per network. A chain can accept arbitrating parameters or accordant parameters, currently we only support btc and xmr:
https://github.com/farcaster-project/farcaster-node/blob/981c0d1d93986f7584bd4b32efbbe41e5ae1854e/src/config.rs#L239-L246
The configuration can then return a parsed swap configuration for a given network, arb chain, and acc chain
https://github.com/farcaster-project/farcaster-node/blob/981c0d1d93986f7584bd4b32efbbe41e5ae1854e/src/config.rs#L150-L156
We have default values for mainnent and testnet for Bitcoin and Monero, if no config is found in the file we return those default value (backward compatibility), otherwise an error is returned. The configuration translate the real chain (Btc, Xmr) into its interface (Arb, Acc) as the swap is started with the offer that contains the chains used.
Launching a swap now takes the parsed swap config to
https://github.com/farcaster-project/farcaster-node/blob/981c0d1d93986f7584bd4b32efbbe41e5ae1854e/src/farcasterd/runtime.rs#L1244-L1260
Cli arguments of swapd have been reworked to accept the new arguments. (Breaking change with other bins that use swapd directly)
The new chains.rs file contains enums for listing support arb/acc chains in our node (e.g. btc as acc is in theory possible but probably not supported in the current architecture, but that would be a nice test to see where the current design falls apart). These structs can be reused later elsewhere (e.g. make cli args) to ensure we accept only valid params.

@Lederstrumpf @TheCharlatan do we want to expose different finality and safety margin per network? (And are those names good?)

names lgtm

@Lederstrumpf @TheCharlatan do we want to expose different finality and safety margin per network? (And are those names good?)

agree it makes sense to have different finality thresholds per network. for safety, it would be more consistent to call this safety_threshold rather than safety_margin, but it works in the opposite direction (upper vs lower bound) to finality, so having distinct names may avoid someone misinterpreting the direction.
I'll also put suggestions of finality_min and safety_max on the table to be absolutely clear on direction since they require less thinking / a lower command of English to be understood unambiguously.

(I'm holding off on merge to get #789 in first since they conflict slightly)

This PR introduce a new section[swap...] in the config file farcasterd.toml. The swap section, for now, contains finality and safety parameters per chain per network. A chain can accept arbitrating parameters or accordant parameters, currently we only support btc and xmr:
...

ok - merging :). And nice new PR docs, @h4sh3d!


GitHub action tests fix

Set maven.test.failure.ignore to false in github actions
Prepare surefire reports even if maven build is failed
Fix SchemaTest
Disable failed tests

Fixes #866

Can you create issues to track the disabled tests ?
The issue was created - #868

Can you create issues to track the disabled tests ?
The issue was created - #868

That issue does not list the tests that need work.
We should either file separate issues for each set of tests that need to be fixed, or have a task list in the issue you created.

What is the difference between build.sh and github-build.sh ? It looks like it is doing the same thing, or did I miss something ?

What is the difference between build.sh and github-build.sh ? It looks like it is doing the same thing, or did I miss something ?

-Dmaven.test.failure.ignore=false

Can you create issues to track the disabled tests ?
The issue was created - #868

That issue does not list the tests that need work. We should either file separate issues for each set of tests that need to be fixed, or have a task list in the issue you created.

I have added the list of the failed tests to the description of the issue #868


Different timestep for averaging?

I am trying to figure out how to average over a different time step for any of the fields you are plotting, but I cannot find it in the code anywhere.  Is there a quick spot you can point me to so I can change from 1-min averaging to 5-min averaging to make the AWIPS-standard (at least currently) output?
If this isn't available anywhere, can you let me know where the averaging is occurring so I can look into making it possible?
Thanks.

It's been happening in post-processing at the moment, so not in this
package. You can sum FED and TOE directly, but 1 min AFA must be multiplied
by FED to give total area, then total area divided by the same of FED to
get 5 min AFA.
I think you can do the same thing by passing --dt=300 (seconds) to
make_glm_grids.py. To get 1 min updates every 5 min, you'd then need to
rerun the processing every minute with a shifting bundle of files.
I think the former route is more resource-efficient overall, as you only
process each raw L2 file once.
On Tue, Aug 28, 2018 at 1:00 PM Bryan Guarente<EMAIL_ADDRESS>wrote:

I am trying to figure out how to average over a different time step for
any of the fields you are plotting, but I cannot find it in the code
anywhere. Is there a quick spot you can point me to so I can change from
1-min averaging to 5-min averaging to make the AWIPS-standard (at least
currently) output?
If this isn't available anywhere, can you let me know where the averaging
is occurring so I can look into making it possible?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deeplycloudy/glmtools/issues/19, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ6y6MUOAsUVCwcmt2kcyRFhQRZhfJpks5uVYVBgaJpZM4WQHRL
.


New Triplestore subclass

Triplestore class starts to be large and has kind of two roles - both providing a common interface to different triplestore backends as well as providing functionality for working with data mapped to ontological concepts.
Would it make sense to create a new module that defines a Triplestore subclass to which we can move the data and mapping related methods, like:

map()
get_value()
add_data()
add_function()
add_interpolation_source()

What would be good names for the new Triplestore subclass? Datastore?

In tripper/ create new name.py containing a class name. name has the methods:

get_value()
add_data()

which should be moved from tripper/triplestore.py.
Suggestions for name from ChatGPT:

OntologyDataHandler
TriplestoreDataHandler
SemanticDataHandler

Hei @jesper-friis
The methods you listed are not in #main yet but in #91 (not merged yet)


Consider put library into reddit review :)

Consider put library into reddit review :)
https://www.reddit.com/r/cpp_review/comments/6o1189/submissions_for_review/

Yes, already have a plan, but not quite yet ready.
Yesterday, I modified the website and added a CONTRIBUTE page for encouraging people to review the pull requests and commits.


Clarification : Autoscale doesn't support scaling of generalized or sysprepped VMs

Hello ,
In this article it is mentioned that "Autoscale doesn't support scaling of generalized or sysprepped VMs with machine-specific information removed" .
In a situation that i created custom image following this guide https://learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image , does this means that autoscaling will not be supported ?

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

ID: 1197d680-f941-a2c6-eeaf-eb65d337040c
Version Independent ID: e1832f6c-820a-b0b8-2a7a-13e7791bb884
Content: Autoscale scaling plans and example scenarios in Azure Virtual Desktop
Content Source: articles/virtual-desktop/autoscale-scenarios.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

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

@TarekNabeel
We're currently working on that issue. We're just waiting for confirmation from the PM who requested the original change.

Hi Team, any update on this ?

@Heidilohr
Can you update the status on above request?


[FEATURE]: Integrate NVIDIA Docker support

Feature Type
Adding new functionality to the BlueROV2 driver
Problem Description
The current Docker image and devcontainer configuration are defined specifically for folks using the default Ubuntu graphics driver. This decision was made to first provide support for the general population. However, this driver does have it's drawbacks and it can be useful to take advantage of the NVIDIA drivers if those are an option to users (and they work way better).
Feature Description
Integrate the requirements necessary for using the NVIDIA drivers with the Docker image. It will be necessary to determine how to best integrate this in such a way that it can be used when the source implementation is released as an image (re-released). Furthermore, it will be necessary to implement an additional devcontainer.json configuration file to support the NVIDIA driver development environment.
Alternative Solutions
Another idea that I've had is to template the Dockerfiles and to generate these as part of the CI/CD pipeline. This could be templated to integrate the NVIDIA driver packages when a particular flag is set. My last idea would be to create a new Dockerfile altogether and keep them separate; however, I like the stages that already exist and want to continue to take advantage of those.
Additional Context
No response

I've integrated this over in my other (unpublished) project and it works really well. Just need to port it over here


Durable functions hubname cannot be configured from app settings

We have the hubname for Durable Functions configured in app settings and local.settings.json. After updating to Durable Functions in isolated worker process mode we run into the problem that variables are no longer allowed for hubname. The setup is similar to what is documented on msdn: https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-task-hubs?WT.mc_id=Portal-WebsitesExtension&tabs=csharp#hostjson-functions-20-1
When running the function app we get the following error:

Microsoft.Azure.WebJobs.Extensions.DurableTask: Task hub name '%MyTaskHub%' should contain only alphanumeric characters, start with a letter, and have length between 3 and 45. Microsoft.WindowsAzure.Storage: Invalid container name. Check MSDN for more information about valid container naming.

@wldevries can you share your host.json and local.settings.json files? Feel free to redact anything sensitive.


[FEATURE] Example docker-compose.yml which pulls appropriate containers from Docker Hub itself or Github's container repositories.

Is your feature request related to a problem? Please describe.
For the most part, the title should be enough; however, I'd like to know at least in the comments within the example docker-compose.yml file provided in this repository which public container images I can pull directly from to deploy this tool.

Also kudos for using the correct reverse proxy tool with the correct style of configuration <3

Thank you so much for your support to the project by creating issues and asking questions :) Truly appreciate the interactivity. I would like to know a bit more, because as I understand it, the current docker-compose.yml already contains comments on which image to pull for production runs.
https://github.com/AmruthPillai/Reactive-Resume/blob/ebd9253038ada5389fff004bcd1d4640a455a404/docker-compose.yml#L28
https://github.com/AmruthPillai/Reactive-Resume/blob/ebd9253038ada5389fff004bcd1d4640a455a404/docker-compose.yml#L52

Is there finished docker-compose yml file? so everyone with compose can deploy it?

@Pheggas Working on it right now, along with a doc on how to deploy on a server. Will have an update soon :)

I've updated the docker-compose.yml to work right out of the box now. Just ensure to change the <SERVER-IP> values within the file to make it work on your server so that you can access it externally on your home network.


Policy-refresh Excel update to reflect current assignments

Overview/Summary
Updating Excel file to reflect current default ALZ policy/initiative assignments.
This PR fixes/adds/changes/removes

Documentation updates

Breaking Changes

N/A

As part of this Pull Request I have

[X] Checked for duplicate Pull Requests
[X] Associated it with relevant issues, for tracking and closure.
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Performed testing and provided evidence.
[X] Ensured contribution guidance is followed.
[X] Updated relevant and associated documentation.
[X] Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)

Will merge once #1242 is merged


[ENHANCEMENT]: Improve description, examples, and tests of 'remove'

Description
The current description and examples of the remove function is confusing at best. It was originally inspired by the lodash remove function: https://github.com/30-seconds/30-seconds-of-code/pull/148
However, from the description and examples it is not really clear that remove actually mutates the original array. I've updated the description and the examples to reflect better what is actually happening.
PR Type

[x] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
[ ] Tools, Scripts & Automation (anything related to files in the scripts folder, Gatsby, website, Travis CI or Netlify)
[ ] General, Typos, Misc. & Meta (everything related to content, typos, general stuff and meta files in the repository - e.g. the issue template)
[ ] Other (please specifiy in the description above)

Guidelines

[x] I have read the guidelines in the CONTRIBUTING document.

Sorry, but I'm not really sure in which way the contribution guidelines are being violated, at least they should not violate them more than the current state of the snippet ... do you mean nums instead of evenNums ? nums would however be not really clear in this case.

Also, why is this PR immediately closed and not left open to improve it as with other PRs ?


Slack Header Content-type coding=utf-8

Version report
Jenkins and plugins versions report:
Jenkins 2.303.1
Slack Notification Plugin 2.48
Reproduction steps
Just send message from pipeline with Cyrillic symbols or other system symbols like № or »
Results
Expected result:
Normal text in slack
Actual result:
����������������
Need add coding to Content-type Header.

The above issue also occurs when sending korean.
I'm guessing the jenkins update below is related.
Update Stapler from 1.263 to 1563.v3da2d02f9572 to improve performance when encoding unicode characters in JSON API

I upgraded from v2.45 to v2.48 and confirm chars like » are not buggy as �

Any chance you are running in docker and are hit by: https://github.com/jenkinsci/docker/issues/1193 ?
If you use 2.309 does it work?

@timja I'm indeed running with Docker, I'm not able to upgrade the image right now but I guess that's the issue... let's others confirm they are running Docker too :)
Thank you,

If you're doing a custom build all you need to do is add this:
https://github.com/jenkinsci/docker/commit/e71180956b43b89b6cd3559db6922e0c47e7d574#diff-7891a6415ef795387fa7e9c8f2f5eee4dc1bb9291e6420b321132405ce15f56a
Otherwise you can probably set the JVM flag -Dfile.encoding=utf-8 as well as an alternative


Use Firebase security settings

Right now you could probably mess with other people.

Swapped redis for firebase.


VM Deployment

Hi! Great documentation - very easy and great to pair it with the GitHub code sample. I am getting a resource provisioning error when I try to make a new VM through the AI Toolkit for Azure IoT Edge Git repo. I've tried several different sizes now. Do you mind sharing which are presently available?

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

ID: ce5efb43-af55-95ea-cc6f-9597ace9b1b8
Version Independent ID: 94f8eff2-fc0d-af3c-5b41-944665674cfc
Content: Deploy Azure Machine Learning to a device - Azure IoT Edge
Content Source: articles/iot-edge/tutorial-deploy-machine-learning.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@KingdomOfEnds Thanks for the feedback! We are currently investigating and will update you shortly.

@KingdomOfEnds You receive this error when the resource SKU you've selected (such as VM size) isn't available for the location you've selected.
To determine which SKUs are available in a region, use the Get-AzComputeResourceSku PowerShell cmdlet. Filter the results by location. You must have the latest version of PowerShell for this command.
Ex: Get-AzComputeResourceSku | where {$_.Locations -icontains "westcentralus"}
For more details, see Resolve errors for SKU not available.

Thanks @AshokPeddakotla-MSFT - I appreciate it. I'll try again here.

I think that resolved my issue. Thanks again!

PS - I used Azure's "create" rather than the deployment template.


Tiling all the higher dimensions to 1

The idea is to force memref.alloca generated after tiling to have a static size. This with https://github.com/iree-org/iree/pull/11944 and https://github.com/iree-org/iree/pull/11938 (hoisting inner loop'smemref.alloca and check that stack size constraint is met) should fix https://github.com/iree-org/iree/issues/11923

Huh, I would expect the test that was failing now to pass. That should show up as an error on CI as an unexpectedly passing tesy

Huh, I would expect the test that was failing now to pass. That should show up as an error on CI as an unexpectedly passing tesy

Hmm have you submitted the other two PRs? Then it should pass

Huh, I would expect the test that was failing now to pass. That should show up as an error on CI as an unexpectedly passing tesy

Hmm have you submitted the other two PRs? Then it should pass

It's not hoisting the memref.alloca outside the inner loops yet.

That's interesting. It should. Can you post the IR just before bufferization

That's interesting. It should.
I didn't debug that function - it seems age old, and should not be wrong (famous last words).

I have just one part above I dont follow. Also begs the question it doesnt seem to actually fix the test... Do we really want to do this then? (I think yes, but ideally we'd want to just dig into the function and see whats failing)

Somebody has to fix the hoisting logic

I have just one part above I dont follow. Also begs the question it doesnt seem to actually fix the test... Do we really want to do this then? (I think yes, but ideally we'd want to just dig into the function and see whats failing)

Somebody has to fix the hoisting logic

RIght, I am saying we could look into fixing that. The hoisting logic itself is simple. It needs fixing the upper bound calculation function. I suspect it is something simple....

Sorry, I'm a bit confused now. Is this necessary to fix the tf integration issue? If not, not doing any tiling would be better than tiling by one, right? Less loops around...

I think eventually it would because it makes the allocation size bounded. Seems like the bound computation logic is missing handling some things, so it is not found to be bounded and the test still fails.

Sorry, I'm a bit confused now. Is this necessary to fix the tf integration issue? If not, not doing any tiling would be better than tiling by one, right? Less loops around...

I think eventually it would because it makes the allocation size bounded. Seems like the bound computation logic is missing handling some things, so it is not found to be bounded and the test still fails.

The dynamic dimension (Value) that is passed to getUpperBoundForIndex https://github.com/llvm/llvm-project/blob/main/mlir/lib/Dialect/Linalg/Utils/Utils.cpp#L229 seems to be a memref.dim, not an affine.min. What exactly is dynamicSizes https://github.com/iree-org/iree/blob/main/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp#L140 ? Are you using it correctly?

Sorry, I'm a bit confused now. Is this necessary to fix the tf integration issue? If not, not doing any tiling would be better than tiling by one, right? Less loops around...

I think eventually it would because it makes the allocation size bounded. Seems like the bound computation logic is missing handling some things, so it is not found to be bounded and the test still fails.

The dynamic dimension (Value) that is passed to getUpperBoundForIndex https://github.com/llvm/llvm-project/blob/main/mlir/lib/Dialect/Linalg/Utils/Utils.cpp#L229 seems to be a memref.dim, not an affine.min. What exactly is dynamicSizes https://github.com/iree-org/iree/blob/main/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp#L140 ? Are you using it correctly?

I think what is happening is that memref.dim is not optimized into affine.min at the time you do the hoisting.

Ok, so we need to resolve the memref.dim in terms of its operands. Full IR please

Ok, so we need to resolve the memref.dim in terms of its operands. Full IR please

%dim = memref.dim %subview, %c3 : memref<1x1x1x?x?x?xf32, strided<[?, ?, ?, ?, ?, 1], offset: ?>, #hal.descriptor_type<storage_buffer>>

Ok, so we need to resolve the memref.dim in terms of its operands. Full IR please

%dim = memref.dim %subview, %c3 : memref<1x1x1x?x?x?xf32, strided<[?, ?, ?, ?, ?, 1], offset: ?>, #hal.descriptor_type<storage_buffer>>

Is there a pass to partially evaluate any program (i.e. constant propagate values)? Didn't @stellaraccident write such a pass in December? If we have that, at any point we need to get a constant SSA result, we can partially evaluate it to determine if it's a constant instead of relying on one-level dependencies having a particular form.

You don't need constant evaluation that Stella added. What you need is use https://github.com/llvm/llvm-project/blob/main/mlir/include/mlir/Dialect/MemRef/Transforms/Passes.h#L129 to resolve the result dims

The complication is that it has to happen within the bufferize pass

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
https://gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!
The only way I can think of addressing this afterwards is to have a pass that hoists the allocas after bufferization. I started working on a pass here https://github.com/MaheshRavishankar/iree/commit/954c5c360d28076bf5ee7e9a4a0fe86152b67dc1 , but the issue is I need to track down all users and replace all users of the original alloca with a subview. You are more than welcome to try to finish up that pass and see if it fixes the issue. I am not planning to look at it anytime soon.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!

That's exactly what I was saying. At the time of bufferization, the pass hadn't been applied and if we evaluated memref.dim using Stella's const propagation /partial evaluation pass when bufferization calls your hoisting function, it would work. That might be easier than post facto hoisting.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!

That's exactly what I was saying. At the time of bufferization, the pass hadn't been applied and if we evaluated memref.dim using Stella's const propagation /partial evaluation pass when bufferization calls your hoisting function, it would work. That might be easier than post facto hoisting.

That const propagation is for whole program constant propagation. It isnt applicable within a dispatch.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!

That's exactly what I was saying. At the time of bufferization, the pass hadn't been applied and if we evaluated memref.dim using Stella's const propagation /partial evaluation pass when bufferization calls your hoisting function, it would work. That might be easier than post facto hoisting.

That const propagation is for whole program constant propagation. It isnt applicable within a dispatch.

Ok then we really need a utility that partially evaluates any value, i.e become a constant of possible, else lower to the "simplest" form. That way, we don't have to transform the code but use the transformed code for analysis

I propose landing this PR independent of other bugs.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!

That's exactly what I was saying. At the time of bufferization, the pass hadn't been applied and if we evaluated memref.dim using Stella's const propagation /partial evaluation pass when bufferization calls your hoisting function, it would work. That might be easier than post facto hoisting.

That const propagation is for whole program constant propagation. It isnt applicable within a dispatch.

Ok then we really need a utility that partially evaluates any value, i.e become a constant of possible, else lower to the "simplest" form. That way, we don't have to transform the code but use the transformed code for analysis

Thats kind of a difficult thing to do, especially when you are evaluating dimensions.... THe dim of result can in general be resolved into dim of its operands. This chain can keep happening. So every dim statement you add could end up being O(N) transformation in the IR. Its fairly hard to manage that.... You can always do it after the fact. Run a fixed point to resolve all the dims, and then you can hoist the allocas (see the pass I linked to)

I propose landing this PR independent of other bugs.

Sure, just then comment on the code itself... Once that is resolved we can land this.

The complication is that it has to happen within the bufferize pass

I don't think so, (please always post full IR, either at function scope or module scope, IR snippets are confusing). We can resolve the dims before bufferization? (unless the dim is generated during bufferization which would be strange). If the IR before bufferization doesn't have this, then this is something we can probably get Matthias to help with.

The full IR is pretty big, but here is the entire dump of all the passes. You have to look at the second ComprehensiveBufferize pass (the first one is for a different function).
gist.github.com/9862e2e86c8e4e9da22c10a0ce5ed1f5
Notice that memref.dim is not present in the IR before ComprehensiveBufferize, but is internally used by ComprehensiveBufferize (that's what my debug prints when doing the getConstantUpperBound show).

Ok, I think I undestand what is happening. During bufferization there is a memref.dim, so at the time of allocation, it cannot figure out that the bounds is constant (but it does after the fact since those patterns apply). That kind of sucks!

That's exactly what I was saying. At the time of bufferization, the pass hadn't been applied and if we evaluated memref.dim using Stella's const propagation /partial evaluation pass when bufferization calls your hoisting function, it would work. That might be easier than post facto hoisting.

That const propagation is for whole program constant propagation. It isnt applicable within a dispatch.

Ok then we really need a utility that partially evaluates any value, i.e become a constant of possible, else lower to the "simplest" form. That way, we don't have to transform the code but use the transformed code for analysis

Such utilities are hard to use and have a compilation cost. In such cases it usually better to do all propagation using fixed point "after the fact". https://github.com/iree-org/iree/pull/11992 finishes up the commit I pointed you to earlier that should be able to hoist such buffers after the fact. That should help resolve the issues for good after the tile size for outer loops you are picking here lands

Thats kind of a difficult thing to do, especially when you are evaluating dimensions.... THe dim of result can in general be resolved into dim of its operands. This chain can keep happening. So every dim statement you add could end up being O(N) transformation in the IR. Its fairly hard to manage that.... You can always do it after the fact. Run a fixed point to resolve all the dims, and then you can hoist the allocas (see the pass I linked to)

Such utilities are hard to use and have a compilation cost. In such cases it usually better to do all propagation using fixed point "after the fact". #11992 finishes up the commit I pointed you to earlier that should be able to hoist such buffers after the fact. That should help resolve the issues for good after the tile size for outer loops you are picking here lands

Yes, there's a compiler cost of O(N) for running the fixed point. But the analysis cost is O(1) if the corresponding transformation has already occurred. So, ideally we would want to have such an analysis pass which can be invoked whenever, and if we are not losing any information running the corresponding (lowering) transformation, we can optimize it in those places by transforming the IR and then paying O(1) (or refactoring the code to not do the analysis, saving the O(1)).
Anyway, talking about speed of the compiler (as opposed to the generated code) seems to be premature optimization unless it becomes a documented bottleneck.
I haven't looked at https://github.com/iree-org/iree/pull/11992. If that is indeed solving the problem, we can look into it.

That analysis has to worst do a whole graph traversal on every query. Also it's not an analysis pass always. It has to mutate the IR. So it's actually O(N)^2 instead of O(N).

I am talking about evaluating the bounds of a single SSA value. If it's already a constant because of an earlier pass or is defined by an op such as affine.min from which the bounds can be evaluated immediately, then the analysis pass will stop. So it cannot be O(N^2) all the time.

I am confused by this discussion. If you can improve the bounds computation cheaply then that is fine. If you need to apply a transformation during bufferization to make it constant, that gets more complicated. The difference seems mostly academic. I suggest looking into it and evaluating if there are improvements to be made. For now a pass after the fact fixes the issue and is a cheap enough solution that adding complexity to bufferization doesn't seem justified. As far as I am concerned the issue is mostly fixed with the pass after the fact.

I am confused by this discussion. If you can improve the bounds computation cheaply then that is fine. If you need to apply a transformation during bufferization to make it constant, that gets more complicated. The difference seems mostly academic. I suggest looking into it and evaluating if there are improvements to be made. For now a pass after the fact fixes the issue and is a cheap enough solution that adding complexity to bufferization doesn't seem justified. As far as I am concerned the issue is mostly fixed with the pass after the fact.

Yes, hoisting will work to fix this particular bug. I am talking about handling such situations in general in the future. I can see partial evaluation, implemented as a general analysis pass, useful in a lot of other contexts to see if a value is bounded

I think the issue was fixed by enabling masking PR. Do we still need the PR?
The IR in the full dump after TileAndDistribute does not look good to me. It is creating more than three loops and the loop ranges are not straight forward to me..
  scf.for %arg0 = %22 to %8 step %8 {
    scf.for %arg1 = %21 to %9 step %9 {
      scf.for %arg2 = %19 to %10 step %10 {
        %23 = affine.apply affine_map<()[s0] -> (s0 * 32)>()[%17]
        %24 = affine.apply affine_map<()[s0] -> ((s0 ceildiv 32) * 32)>()[%11]
        scf.for %arg3 = %23 to %11 step %24 {
          %25 = affine.min affine_map<(d0)[s0] -> (-d0 + s0, 32)>(%arg3)[%11]
          %26 = affine.apply affine_map<()[s0] -> (s0 * 32)>()[%workgroup_id_y]
          %27 = affine.apply affine_map<()[s0] -> (s0 * 32)>()[%workgroup_count_y]
          scf.for %arg4 = %26 to %12 step %27 {
            %28 = affine.min affine_map<(d0)[s0] -> (-d0 + s0, 32)>(%arg4)[%12]
            %29 = affine.apply affine_map<()[s0] -> (s0 * 32)>()[%workgroup_id_x]
            %30 = affine.apply affine_map<()[s0] -> (s0 * 32)>()[%workgroup_count_x]
            scf.for %arg5 = %29 to %13 step %30 {

If we want make some dims be all ones, we can tile them with size 1 in the second level of tiling.

Yeah, those affine maps are really hard to fix once they've been built like that (see for example #12517).

I think the issue was fixed by enabling masking PR. Do we still need the PR?

Closing some old PRs, especially given ^


Add #rotate_left and #rotate_right for primitive integers

Resolves #11841. Note that BigInts cannot rotate because they don't have a maximum magnitude.
IIRC this makes Random.rand approximately 30% faster.

For the interpreter, the intrinsics addition means that stdlib won't be compatible with older interpreter builds before this change. This is probably not a big issue since the interpreter is still in preview and people have to build it themselves. But you'll need to rebuilt it now in order to provide these intrinsics.
We could consider pulling this apart and adding the compiler enhancements first.

FWIW, this change in hasher also make the >> no longer show up at all in the toplist when running bin/crystal build -s spec/std/array_spec.cr as in https://forum.crystal-lang.org/t/ongoing-experiment-ident-pool/4795/2 . So it also make hashing a lot faster. :+1:


luci-app-nlbwmon, exporting previous accounting periods broken.

Hi All
I am using Netlink Bandwidth Monitor for more than a month now so i have two accounting periods to choose from.
The problem i have is that i am not able to export previous accounting period. When i select previous period and perform export, it always exports current accounting period.
I am on 22.03.1.
Step to reproduce:
Select previous accounting period and try to export to CSV.
Expected behaviour:
Selected accounting period exported.
Acutal behaviour:
Current accounting period exported.
Can anyone confirm that this not only my issue?

I have confirmed this behaviour, but it only occurs within luci-app-nlbwmon.
Selecting different accounting periods works using CLI notation ie.nlbw -c csv -t 2021-07-17

It simply never was implemented in the ui, it always exports the latest period. This isn't strictly a bug, just nbot implemented functionality and misleading ui interface.

Makes sense. I've always used nlbw for that functionality. Thanks.


Bug Report: Scale Error

Hi there: there's a bug that when you change the scale rate, the link line would stay same state as the scale rate before. The link lines don't scale at all~

Hi, having the same issue, is there any updates or chances to fix this?


Artemis!66E7106BDDAA was detected and deleted from ms-python vscode extension

This happened for the first time today. McAfee Endpoint Security Software deleted the following:
.vscode\extensions\ms-python.python-2020.1.57204\pythonFiles\lib\python\new_ptvsd\wheels\ptvsd_vendored\pydevd\pydevd_attach_to_process\inject_dll_x86.exe. The Trojan named Artemis!66E7106BDDAA was detected and deleted.
I apologize if this is not the correct forum to notify you of this.

Same problem here. MacAfee On-Access scanner picked up on it when opening VS Code.

Please open this issue on the Python extension

This is related;
https://github.com/microsoft/vscode-python/issues/9474#issue-547336257
On Thu, 9 Jan 2020 at 21:57, Connor Peet<EMAIL_ADDRESS>wrote:

Please open this issue on the Python extension
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/88383?email_source=notifications&email_token=AJ3VPUIBPLB5KDZZOZLADKDQ46MT7A5CNFSM4KE4TKW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIR5VHQ#issuecomment-572775070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ3VPUNU6SZB6Z245DKLK6DQ46MT7ANCNFSM4KE4TKWQ
.

--
Best Regards,
Scott


performance problem when get schema from collection

When I am trying to loading data from mongo to spark, I find one wired performance issue in spark UI. It shows that it split into 2 stages the first is flatMap at MongodbSchema.scala:41, the second one is aggregate at MongodbSchema.scala:47. My problem is that the first stage always get one task and one executor, which is crazy slow with some big table. Sometimes, it use 1hr in flatMap stage but only   several seconds in next one.  source code is blow:
 override def schema(): StructType = {
    val schemaData =
      if (samplingRatio > 0.99) add
      else rdd.sample(withReplacement = false, samplingRatio, 1)

    val structFields = schemaData.flatMap {
      dbo => {
        val doc: Map[String, AnyRef] = dbo.seq.toMap
        val fields = doc.mapValues(f => convertToStruct(f))
        fields
      }
    }.reduceByKey(compatibleType).aggregate(Seq[StructField]())(
        (fields, newField) => fields :+ StructField(newField._1, newField._2),
        (oldFields, newFields) => oldFields ++ newFields)
    StructType(structFields)
  }

It looks like just grabbing the schema from collection. I don't know why this stage is limited to one executor. Is it normal? or whether I can do something to increase the number of executor and gain higher performance. I am working with spark 1.6.2 and stratio 0.11.0
THX.

Facing a similar problem,can someone update on this.In order to reduce the fetch time,I'm trying to load mongo collection using a split key on isodate field without any success.
I'm using the following config to load data:
val mongoConfig = MongodbConfigBuilder(
Map(
Credentials -> List(slaveCredentials),
Host -> mongoHost,
Database -> mongoDatabase,
Collection -> mongoCollection,
SamplingRatio -> 1.0,
WriteConcern -> "normal",
SplitSize -> "10",
SplitKey -> "created_at",
SplitKeyMin -> "2016-11-20T10:01:32.239Z",
SplitKeyMax -> "2016-11-23T10:01:32.239Z",
SplitKeyType -> "isoDate"
)
).build()
val mongoDF = spark.sqlContext.fromMongoDB(mongoConfig)
But what I find was,this query is fetching all the data into spark which is very slow because of one executor in flat map stage.


[AutoPR resources/resource-manager] Added Swagger api spec for tags (tracked resources and subscription)

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7704

(message created by the CI based on PR content)


Marshaled xml root tag is always starting with uppercase

Generating structs from
<parent>
  <child>childValue</child>
</parent>

produces
type Parent struct {
        Child string `xml:"child"`
}

Which marshals as xml with an uppercase root tag (notice the uppercase P) playground
<Parent>
   <child>childValue</child>
</Parent>

Ideally, the root struct should contain an xml.Name field to preserve the proper xml name.
This will also allow the user to rename the root struct without affecting the xml output

Thanks for spotting and reporting. v1.5.0 includes a WithNamedRoot option to include an XMLName in the generated root struct.

@twpayne the import statement should not be included when package name is empty.

@twpayne the import statement should not be included when package name is empty.

You're right, thanks. However, there's a more to this issue. If one of the generated fields is a time.Time then an import "time" statement will be included when the package name is empty. This is because the current code to strip the package name is too simple. Could you open a separate issue for this?


borderTopWidth for tabBarStyle does not work well if it is set to decimal fraction on iPhone 6/6s Plus

[x] Provide a minimal code snippet / rnplay example that reproduces the bug.
Everything is ok on rnplay.org because it is not a plus version of iPhone:   https://rnplay.org/apps/VM5Zsg

import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  Text,
  View,
} from 'react-native'

class RNPlayground extends Component {
  render() {
    return (
      <View style={styles.container}>
        <View style={styles.wrapper}>
        </View>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  wrapper: {
    borderTopWidth: 0.5, // bug occurs on iPhone 6/6s Plus
    width: 200,
    height: 200,
    backgroundColor: '#DDDDDD',
  }
});

AppRegistry.registerComponent('RNPlayground', () => RNPlayground);

[x] Provide screenshots where appropriate
On iPhone 6 Plus(real devices too)

Expected:

[x] What's the version of React Native you're using?
0.28 & 0.29
[x] Does this occur on iOS, Android or both?
ONLY on iPhone 6 Plus and iPhone 6s Plus
[x] Are you using Mac, Linux or Windows?
Mac

It seems that issue #6951 is related.
Solution at current time:
Use Shadow Props(only for iOS):
    shadowColor: '#B0B0B0',
    shadowOffset: {
      width: 0,
      height: -0.5,
    },
    shadowOpacity: 1,
    shadowRadius: 0,

so @imWildCat , have you solve the problem? same here

It is not clear to me what the problem is from reading this issue. I am going to close it but if this is still a problem and someone can explain precisely what the problem is then I can reopen.

@imWildCat  have you solved??

@iiitmahesh I am currently a business suffering from my essays 🙈
I think I didn't solve this problem at that time and gave up.


VirtualTourPlugin support tiles

What are you trying to do?
in VirtualTourPlugin ,i change the nodes's  panorama from string to object.  i want  VirtualTourPlugin  support tiles.

Code
No response
Sandbox Link
No response
Library Version
lasted
What operating system are you using?
Windows
What browser are you using?
None
Logs
No response

Hi, I saw that you have already added a issue to "photo-sphere-viewer". After some tests I think that it's a problem of the main lib.

Please refer to: https://github.com/mistic100/Photo-Sphere-Viewer/issues/1168 issue in main lib. add the Adapter to the Viewer.


fail: check condition only when its failpoint is open

Signed-off-by: Liqi Geng<EMAIL_ADDRESS>The check-condition code in failpoint runs all the time even it is not open.
It may lead to bad performance if checking the condition is very expensive
or misuse if someone modifies some variables in check-condition code and it's valid only when its failpoint is open. (my guess scenario)

Here's a patch to fix CI: https://github.com/tikv/fail-rs/pull/49


ENH: proposed improvements to plot_psd_topomap

Some things I wished I was able to do when using epochs.plot_psd_topomap yesterday, and some ideas about how to implement them:

automatic joint determination of vlims. copy over the API from #6922 that allows vlim='joint' for multi-topomap figures

logarithmic colormap.  SSVEP carrier frequency ought to have more power than oddball frequency, by virtue of the experimental design (fewer oddball stimulus exposures).  A logarithmic colormap might help make the carrier & oddball spikes both visible given the same vmin/vmax.  In addition to the sharp SSVEP spikes, the data I'm currently working with has a large broad bump in the spectrum, with power roughly an order of magnitude greater than the spikes (probably a muscle artifact).  A logarithmic colormap would make it possible to plot that in the same figure with the spikes (useful during exploratory analysis).

make it easier to plot a specific frequency bin.  Because SSVEP leads to very focal spikes in the spectrum, the current API of bands=[(band1_lower_edge, band1_upper_edge, 'subplot title'),] is a inconvenient. It would be nice to be able to pass a specific single frequency and have it not fail. Possible API ideas:

pass in a single frequency, get back a topomap of the single bin nearest to that frequency
pass in a single frequency and a bandwidth
pass in a single frequency and an integer number of bins

For comparison, currently to get a single bin topomap you have to compute the bin spacing and pick bin lower/upper edges that are ± half a bin width from the target frequency. But knowing the bin spacing requires computing the PSD first before plotting (and the PSD then gets computed again within the plotting function, which is not very efficient).

For (1) agreed
For (2) this should probably be an option, +1 for making it the default since it's closer to what we do when plotting PSDs anyway
For (3) I like the first idea, just get the single bin nearest to that freq. I don't love the integer number of bins because it's not a natural unit of measurement. We could enable the second idea, too, which would make a float bands (first idea) basically just get upconverted to (bands, 0) in the code (assuming you always make sure you get at least one band in your freq += bw limit).


docs: fix typo az reservations list

fix typo on opened issue (Azure/azure-cli#26385)

@kyuubang, Thank you for submitting this PR and working to provide accuracy to the Azure CLI reference content.  As this is an autogenerated document from source code, this PR has been moved to Azure/azure-cli issue 27510 where it will be directed to the correct Azure service team.  Please feel free to leave additional comments in the related GitHub issue.


Additional properties to existing nodes?

Hello,
Is it possible to add additional properties to existing nodes?
Actually, I am wondering if you can create, delete, modify, properties to existing nodes and relations after they have already been created?

Hello,
Can you please elaborate what do you mean by additional properties in Node?
There is a "data" field in Node object and it can contain any JSON data, does this help you or do you mean anything else?


Override .max_nb_records

Improve the pagination performance to https://github.com/killbill/killbill-plugin-framework-ruby/issues/67, return 20001 when records are more than 20k.

@pierre I did not see anything broken by doing this.
As I commented above, setting max_nb_records to a large number would work with normal limits of the page size (no more than 20k). I set it to 20001 just because you mentioned that KB core will treat 20k+ as 20k.
If we look at the codes:
def self.search(search_key, kb_tenant_id, offset = 0, limit = 100)
    pagination                  = ::Killbill::Plugin::Model::Pagination.new
    pagination.current_offset   = offset
    pagination.total_nb_records = self.count_by_sql(self.search_query(search_key, kb_tenant_id))
    pagination.max_nb_records   = self.max_nb_records
    pagination.next_offset      = (!pagination.total_nb_records.nil? && offset + limit >= pagination.total_nb_records) ? nil : offset + limit
    # Reduce the limit if the specified value is larger than the number of records
    actual_limit                = [pagination.max_nb_records, limit].min
    pagination.iterator         = ::Killbill::Plugin::ActiveMerchant::ActiveRecord::StreamyResultSet.new(actual_limit) do |offset, limit|
        self.find_by_sql(self.search_query(search_key, kb_tenant_id, offset, limit)).map { |x| x.to_transaction_info_plugin }
    end
    pagination
end

max_nb_records only matters when the page size the client asking is more than the max record number in the database. So to me, it would be more efficient to use a fixed number here than counting the database every time. I'm OK if you think a smaller number (200?) would be better.
Besides that, I think the pagination would be fine cause it actually works with total_nb_records which is not changed.
Could you please give more details about the pagination failure you mentioned?

max_nb_records only matters when the page size the client asking is more than the max record number in the database. So to me, it would be more efficient to use a fixed number here than counting the database every time.

max_nb_records is returned as part of the API here: https://github.com/killbill/killbill-api/blob/3b7a66545e3c319d41b6860132405f2e8193195d/src/main/java/org/killbill/billing/util/entity/Pagination.java#L44-L51
You can follow how it is used in Kill Bill here:

https://github.com/killbill/killbill/blob/c64f1ed838bd2333729ef1787e1560dbbab48d62/util/src/main/java/org/killbill/billing/util/entity/dao/DefaultPaginationHelper.java#L70-L75
https://github.com/killbill/killbill/blob/c64f1ed838bd2333729ef1787e1560dbbab48d62/jaxrs/src/main/java/org/killbill/billing/jaxrs/resources/JaxRsResourceBase.java#L361

Eventually, the value is used in Kaui for the pagination tables:

https://github.com/killbill/killbill-admin-ui/blob/4688c6daac9e820e9b1a0b31e408f7bdc830a214/app/controllers/kaui/payments_controller.rb#L10
https://github.com/killbill/killbill-admin-ui/blob/7af799e79a90e9de3803c0db77abd176cfb59391/app/controllers/kaui/engine_controller_util.rb#L26-L28

If you always say that it's 20K+, the "next" arrows will always be populated, regardless of the exact number. The legend will also probably be always wrong, saying that the dataset has 20k+ records, even if there are only a few hundred records. Am I missing something?
My suggestion in the mentioned ticket was to do something like this https://github.com/killbill/killbill/blob/c64f1ed838bd2333729ef1787e1560dbbab48d62/util/src/main/java/org/killbill/billing/util/entity/dao/DefaultPaginationSqlDaoHelper.java#L79-L83 instead.

I might miss something here, but I don't think a fixed max_nb_records would break the "next" arrow. In my option, for a given pagination, the "next" arrow should be populated according to the total_nb_records and offset, not the max_nb_records.
And for a real working payment system, 20k+ responses would be easy to exceed in a short period. So I still prefer reducing 2 or at least 1 query for every search request to providing a max record number which is only accurate in 20k. Because if the search volume is high the query time matters otherwise if the search volume is low the max number does not matter.
To finalize the change, I'm fine to follow your suggestion if you insist.

I might miss something here, but I don't think a fixed max_nb_records would break the "next" arrow. In my option, for a given pagination, the "next" arrow should be populated according to the total_nb_records and offset, not the max_nb_records.

Maybe, to be tested (all of that logic is delegated to DataTables, and it has been a while since I touched this integration). Regardless, the legend would be wrong/confusing.

And for a real working payment system, 20k+ responses would be easy to exceed in a short period.

Agreed, but we have lots of Kill Bill deployments nowadays at a much smaller scale (and typical QA/test environments don't have that many rows).

So I still prefer reducing 2 or at least 1 query for every search request to providing a max record number which is only accurate in 20k. Because if the search volume is high the query time matters otherwise if the search volume is low the max number does not matter.

I'm all in favor to optimize the large scale deployment, but I don't want to compromise on the generic use-case (a brand new deployment would be broken out of the box).
My initial suggestion on the other ticket was to do something similar that Kill Bill core does today, but in the plugin-framework-ruby (that way, you have it for free for CyberSource and PayPal). If you prefer fixing it only for Orbital for now, I'm fine too.

For now, the search only applies to Orbital, so I override it to restrict the scope and impact. I'm happy to do the follow up refactor in the framework reop if we think it's the solution to all plugins or they have the same performance issue in search.

@pierre Yes, it would resolve the performance problem. And I built a version locally and deployed it to our staging, the search endpoint works without any smoke test broken.
Please help to release the change.
Thanks


Generated PDF sizes with v8.x are ~2-3x larger than same generated PDF on v7.x

Hi,
When wanting to migrate from v7 to v8, we noticed that a PDF document generated on v8 was 2 to 3 times heavier than the same one generated with v7. We use the endpoint forms/chromium/convert/html.
This case is easily reproducible by instantiating a docker container for each version, we used these image versions:
gotenberg/gotenberg:7.10.2
gotenberg/gotenberg:8.10.0
With our html, the PDF in v7 has a size of 286kb, whereas 795kb in v8.
Why such a difference?
Thanks.

Hey @RomainTFasst
I think it’s related to #1058. Does it happens with version 8.9.1?

Hi, no it doesn't, the PDF siize is globally the same as v7.10 with v8.9.1.
Is this issue will be corrected in future version?
Thanks.

Nothing much I can do, looks like an issue with Chromium 🫤

OK, thanks for your feedback!


Suggestion: deprecate module keyword in place of namespace

TypeScript Version:  2.7.0-dev.201xxxxx

Search Terms:  module, namespace, module vs namespace, module keyword
Suggestion:
The use of the module keyword has been replaced with namespace, except when actually declaring ES6 modules in a declaration file. However, in my personal experience I still see new developers getting confused about ES6 modules and the TS module keyword, even through it's well documented, because TS silently supports the module keyword for backwards compatibility.
Why not deprecate the use of the module keyword where it "shouldn't" be used anymore? Emit an error or a warning by default, suppressible with a tsconfig flag for backwards compatibility?
Code
// Example of needless namespacing
export module Shapes {
    export class Circle { }
    export class Square { }
}

Expected behavior:
Some kind of warning that module here should be namespace, and that a namespace is not needed in an ES6 module using export.
I realize you could argue a linter is a better place to provide this kind of check, but the idea is to help users during the learning process who will easily fall into the confusion of module as a namespace vs ES6 module.
Actual behavior:
Playground Link:
Related Issues:

Tracking at #51825


autocomplete.py: allow toggling of matches

Not sure if this was an issue for anyone else, but autocomplete for commands was not working for me. It was using a variable, inputList, that wasn't a list. The variable was the first item in the list returned from .split(). So I:

Made inputList a list, so it works with the already in place code that checks its length
currCommand indexes the list to get the first item
Add tab completion for next match, i.e. if the input command is thread and you press tab, it autocompletes to threadView. Previously it would just stay as thread
Toggle between autocompletion, i.e. if I tab complete to thread, then threadView, I can press tab once more to go back to thread, and so on.

The logic for the toggling auto completion is a little jank so just lmk if you want it reworked.

yeah i kind of yeeted that together one afternoon good to get it cleaned up


Fix some wrong HTML elements

Only some minor fix on the HTML.

Thanks! Will look into your other PRs later.