pluginName: BackgroundGeoLocation does not exist.

Hello Sir,
I am working on the project that using Ionic. I need using signification location change to track the path.
I found your plugin and installed it. Below is the error that I got from the system log.

CDVPlugin class CDVBackgroundGeoLocation (pluginName: BackgroundGeoLocation) does not exist.
ERROR: Plugin 'BackgroundGeoLocation' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.
-[CDVCommandQueue executePending] [Line 159] FAILED pluginJSON = ["BackgroundGeoLocation1343263250","BackgroundGeoLocation","start",[]]

Please help me fix this issue. Thanks in advance.

how did you install the plugin?
On Wed, Apr 8, 2015 at 10:39 AM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

Hello Sir,
I am working on the project that using Ionic. I need using signification
location change to track the path.
I found your plugin and installed it. Below is the error that I got from
the system log.
CDVPlugin class CDVBackgroundGeoLocation (pluginName:
BackgroundGeoLocation) does not exist.
ERROR: Plugin 'BackgroundGeoLocation' not found, or is not a CDVPlugin.
Check your plugin mapping in config.xml.
-[CDVCommandQueue executePending] [Line 159] FAILED pluginJSON =
["BackgroundGeoLocation1343263250","BackgroundGeoLocation","start",[]]
Please help me fix this issue. Thanks in advance.
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

I installed follow your instruction:
$ cordova plugin add https://github.com/christocracy/cordova-plugin-background-geolocation.git
$ cordova platform add ios
$ cordova build ios

Works perfect here.  I just did a fresh install of my example/SampleApp and
booted without problem.
Problem is on your end, I’m afraid.  What version of cordova are you using?
On Wed, Apr 8, 2015 at 11:28 AM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

I installed follow your instruction:
$ cordova plugin add
https://github.com/christocracy/cordova-plugin-background-geolocation.git
$ cordova platform add ios
$ cordova build ios
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-90950920
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

I am using cordova v4.3.0

Have you tried booting my SampleApp?
see README.
On Wed, Apr 8, 2015 at 11:42 AM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

I am using cordova v4.3.0
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-90955371
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

I can not boot your sampleApp. I got the following error http://pastebin.com/7vJXkYpQ
I really appreciate for your help. Thanks so much.

Seems to be an issue with my SampleApp icons.  Are you on Mac or Linux?
$ rm /Users/brianvu/Developers/geo_example/SampleApp/hooks/before_prepare/
resource_copier.js
Then try again.
On Wed, Apr 8, 2015 at 12:02 PM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

I can not boot your sampleApp. I got the following error
http://pastebin.com/7vJXkYpQ
I really appreciate for your help. Thanks so much.
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-90960068
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

Hello,
I am using Mac.
After delete that file, it work perfect on iOS 7 but iOS 8.
Sorry for late reply.

Hello Sir,
Your example only work on iOS 7.
Could you please help me make it work on iOS 8?
Thanks & Regards,

How do you expect me to help you?  You've provided no evidence to support
your statement and my experience contradicts your observation.
ios8 works for me.
On Thursday, April 9, 2015, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

Hello Sir,
Your example only work on iOS 7.
Could you please help me make it work on iOS 8?
Thanks & Regards,
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91396772
.

--
Snet from Gmail Mobile

Hi,
I'm sorry.I re-checked, your example work like charm.
However, my app is still work on iOS 7.
Here is the error log when I run my app on iOS8 http://pastebin.com/2KhfnKcD

I just installed booted my SampleApp from scratch on iOS8.2, Cordova 4.3.0,
iPhone 5 and it continues to work as expected.
My boot-log
https://gist.github.com/christocracy/0cfd4e87e4d72f0d2ded
On Thu, Apr 9, 2015 at 10:45 PM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

Hi,
I'm sorry.I re-checked, your example work like charm.
However, my app is still work on iOS 7.
Here is the error log when I run my app on iOS8
http://pastebin.com/2KhfnKcD
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91409230
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

Yes, I also boot your SampleApp work on iOS8.2, Cordova 4.3.0.
But I can not make my app work as expected on iOS8.2, the callbackFn did not excute
I get notifications on Simulator and I see one of the notification as Outstanding bg-task was force killed.
Anyway, thanks for your help.

"Outstanding bg-task was force killed.” this is of no consequence.
On Fri, Apr 10, 2015 at 4:19 AM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

Yes, I also boot your SampleApp work on iOS8.2, Cordova 4.3.0.
But I can not make my app work as expected on iOS8.2, the callbackFn did
not excute
I get notifications on Simulator and I see one of the notification as
Outstanding bg-task was force killed.
Anyway, thanks for your help.
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91474900
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

delete app from ios 8 device.  re-install.
On Fri, Apr 10, 2015 at 4:21 AM, Chris Scott<EMAIL_ADDRESS>wrote:

"Outstanding bg-task was force killed.” this is of no consequence.
On Fri, Apr 10, 2015 at 4:19 AM, Vu Khanh Truong<EMAIL_ADDRESS>
wrote:

Yes, I also boot your SampleApp work on iOS8.2, Cordova 4.3.0.
But I can not make my app work as expected on iOS8.2, the callbackFn did
not excute
I get notifications on Simulator and I see one of the notification as
Outstanding bg-task was force killed.
Anyway, thanks for your help.
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91474900
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

--
Chris Scott
Transistor Software http://www.transistorsoft.com

I did, but it still did not work. It meet the same error above.
Thanks for your help :)

just installed iOS 8.3, still works without any issues.
On Fri, Apr 10, 2015 at 6:44 AM, Vu Khanh Truong<EMAIL_ADDRESS>wrote:

I did, but it still did not work. It meet the same error above.
Thanks for your help :)
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91512782
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

Field test successful
On Friday, April 10, 2015, Chris Scott<EMAIL_ADDRESS>wrote:

just installed iOS 8.3, still works without any issues.
On Fri, Apr 10, 2015 at 6:44 AM, Vu Khanh Truong<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

I did, but it still did not work. It meet the same error above.
Thanks for your help :)
—
Reply to this email directly or view it on GitHub
https://github.com/christocracy/cordova-plugin-background-geolocation/issues/165#issuecomment-91512782
.

--
Chris Scott
Transistor Software http://www.transistorsoft.com

--
Snet from Gmail Mobile

Today, I update iOS 8.3 and It work great. Thanks so much for your support.


Style Teaser Pattern

Style the and teaser and teaser list patterns

[ ] Style teaser pattern
[ ] Style teaser list pattern
[ ] Added to Browser

Linked with https://github.com/libero/libero/issues/97

https://github.com/libero/pattern-library/pull/80

Styled the title for teaser. Other styling to be done later.


Increase the threshold for NoNewTransactions alert

NoNewTransaction alert is fired when there are no transactions gossiped for 40 mins (including 10mins of wait time specified using for).
This alert has mostly been firing because of dust transactions not being sent either due to node crashes or sync issues. Assuming they are resolved within 40mins (catchup time after a restart) we'd see it getting triggered less. One can silence the alert if dust transactions are not happening even after 40mins
Is it ok to wait for 40mins in the case of a genuine txn gossip issue?

This hasn't been an issue in the last several years. Closing, we can revisit if it becomes an issue again.


Feature request for customizing go lsp

Golang server is a bit slow, I want to try bingo. Could you support this option in config file? Thanks!

Hi cosmtrek, have you seen https://tabnine.com/semantic? There's an example of overriding the default config to use ccls which you could adapt to use bingo.

Thanks a lot!


Refactor news section styling and add dynamic news fetching

Refactored the styling of the news section in style.css to improve readability and organization.
Added JavaScript code in script.js to fetch news articles using the Mediastack API.
Created a function to display the fetched news articles dynamically in the news section of index.html.

for issue #28

Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


VB.NET intellicode support for VS Code

Does anyone know if and when there will be VB.NET intellicode support for VS Code?

Thanks for raising this feedback.  We don't have any current plans to support IntelliCode features for VB.NET (or C#) on Visual Studio Code. At this point we recommend using Visual Studio for VB.NET and C# IntellICode support.
Thanks
Mark


Fixed alpha initialization bug

Default value of alpha should be 0.5 instead of 0.05

Coverage remained the same at 94.937% when pulling 0a22fea89d008bb98e4f5fb684163eb9dcde3606 on ravigarg27:master into 8a56ae7a86dca251e65411c4a279757c1bdcfad6 on pavanramkumar:master.

LGTM, merging

thanks @ravigarg27 !
you might want to add the email-id you used to commit to the list of recognized email addresses on github. Right now, the commit cannot be traced back to you

Ahh it was missing from my local git config. I guess li8 for this, for future I believe it will be done. Thanks for letting me know.

Thanks for this @ravigarg27


Support exposing HTTP ports with the @web_server decorator

This is another built-in type of web endpoint that exposes an external port on the container. Documentation is provided on the method.
We'll need to write a guide for this in the future, and we can simplify some examples.
Usage:
import subprocess

from modal import Stub, web_server

stub = Stub()

@stub.function()
@web_server(8000)
def my_file_server():
    subprocess.Popen("python -m http.server -d / 8000", shell=True)

Resolves MOD-2504.
Changelog

Add the @web_server decorator, which exposes a server listening on a container port as a web endpoint.

@freider Requesting review in case you have insights about asyncio error handling! I tried to write this code to be pretty concise and handle disconnects properly.

I somehow messed up the git merge / diff situation with main, so I'm going to rebase and squash this branch to fix that — sorry for deleting history.

I think I ironed out all of the kinks? Will merge now.
Re: the TaskContext thing, we can revise the code to use that once #1533 is merged, if we decide to take that route. Along the way we can audit other usage of TaskContext.


(SJ@JX Arcade)Using start select in Makecode

Hi! I talked a bit about this on the Makecode Arcade forum with you.  At a bit of a loss how to do this I am using this encoder https://www.amazon.ca/gp/product/B07FZ3YT1G/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
and when setting up the joystick and keys in emulation station I configure them all.  However as I mentioned the start/select will not bring me out of Makecode as it does in Mame.  I know you mentioned the .cfg files but I am a bit new to Raspberry Pi so if you could walk me through how to get those to work in Makecode that would be awesome.

...if you could walk me through how to get those to work in Makecode that would be awesome.

Hi @QuadDam / @Dace,
I'll try my best, even though it's hard to be precise and correct when I don't have first hand access myself to your particular gamepad. We therefore have to try to help eachother on the way.
First a brief introduction to how MakeCode Arcade games and McAirpos handles game controller inputs:
Basically, there are 2 kinds of button/input event types for the various supported controllers(keyboards, gamepads etc.):

EV_KEY: These are "digital" type of buttons, with either value 1(pressed) or 0(released), typical for keyboards and many gamepad buttons, like typically the START button in question, SELECT etc. EV_KEY is the only type of inputs that MakeCode Arcade games understands natively.
EV_ABS: These are "analog" or graded inputs with values typically somewhere between -255 and 255, denoting how much a joystick axis/button is moved/pressed in one direction. Most modern gamepads have several EV_ABS for both axis and various buttons. McAirpos uses uniput-mapper to translate EV_ABS input values, if present, to EV_KEY values and mappings, which MakeCode Arcade games understand.

Then there is the fact that MakeCode Arcade games operates with "RAW"/physical/most basic inputs, totally unaware of any higher level gamepad systems/libraries, like SDL etc. in RetroPie etc. To be precise, MC Arcade games uses input events directly from Linux Input Subsystem, and how these were implemented in the gamepad hardware driver, which has no adapted standard between gamepad producers, and where e.g. value -127 for a given input could be either up or down, within or outside bounds etc., and the names for the various axis and buttons varies just as much...
MC Arcade games with McAirpos have 3 logical levels to deal with this, in order of higher complexity to get it right:

Physical/Linux Input Subsystem(LIS) level(is the button intended to be START physically wired correctly to driver's representation of the START button, and how/by what name and type is it represented in LIS?)
Are all gamepad inputs EV_KEY and can be mapped directly to MC Arcade games in /sd/arcade.cfg without the need for uinput-mapper,(run launCharc with nomap option), or
Are some buttons EV_ABS which have to be translated by uinput-mapper to EV_KEY, and the re-mapped via ../uinput-mapper/configs/arcade1.py to the mappings in /sd/arcade.cfg?

The good news are that with most buttons/axis working, you're already 95% there, and with a high probability of success, hopefully on the first/lowest level. (And if you're lucky, your gamepad driver only sends EV_KEY input events, and you may also choose to optimize away the highest level/uinput-mapper, saving a lot of resources running Python and re-mapping of mappings, with just a few edits to /sd/arcade.cfg.)
What you need to do is:

Find your gamepad's input eventX number: more /proc/bus/input/devices
Read out all registered button and types, and test to which button name each physical button is mapped by(maybe install evtest first if not already installed) running: evtest /dev/input/eventX, where X is the input number found in the first point.

Hopefully(normally) your gamepad driver has registered keys for START and SELECT, and you just have to rewire the two buttons you intended to be START and SELECT, respectively, and everything works out of the box(except for a required quick remap inside RetroPie afterwards). If not, or if you only have EV_KEY inputs, please come back here again, and we'll give it another shot with the various config files.
Other issues maybe related to yours:
https://github.com/Vegz78/McAirpos/issues/9
https://github.com/Vegz78/McAirpos/issues/6
Thanks for the start and nice pictures of and other resources from your great project shared on the MakeCode forum! I hope you get this to work for yourself and your students!
Br, Vegard

Great thanks for the info, so

I ran evtest /dev/input/eventX
https://drive.google.com/file/d/1Eaonui26ALcExJGZZnt45Xp70Wr46nZn/view?usp=sharing
It created this running list, so I tapped the select and start buttons (how do you stop the list from running? I had to hit ctrl/alt/ delete)
https://drive.google.com/file/d/1ahhOZiYPh3amjEUKrqec77v6RPnSgyrt/view?usp=sharing
I am unsure what to do from here so I looked up how to retrieve the event log
https://drive.google.com/file/d/1BTeWm5qNHSUi0I7fkOGmSeUEC_1Hqxbq/view?usp=sharing
which results in nothing, just a blinking cursor, so I am a bit sure what to do beyond this, even if I get that list what would be the next step?  Sorry for my lack of skills on the Pi :( thanks for any help!

I ran evtest /dev/input/eventX

Ok, so you found the "Dragonrise" controller at /dev/input/event2, that's good and seems correct.

It created this running list, so I tapped the select and start buttons (how do you stop the list from running? I had to hit ctrl/alt/ delete)

Then, when running evtest /dev/input/event2 (I assume event2 and not eventx that you wrote above), you got a running list instead of the normal static list of all available button/axis names for the driver, which we want, and a cursor waiting for you to press a button or move the stick in a direction.
This might be because your stick maybe not is not dead center in one of the axis directions(EV_AVS....ABS_Z), and therefore giving continuous inputs in the range 128-133, which makes it harder to read the button presses in between.
However, at around 9 seconds into your movie, I was able to read out button press (EV_KEY....BTN_THUMB), which is neither the button BTN_START or BTN_SELECT I was expecting from you pressing either of the two front buttons that you intend to be START and SELECT, respectively:

So you could either try to center the joystick or disconnect its wires, and then run evtest /dev/input/event2 again and note down the BTN_ name for all your buttons. Exit evtest, normally, by pressing CTRL+C.
From what we have discovered so far, I now more strongly suspect that some of the buttons are wired wrong in respect to what the RAW driver uses as factory BTN_ names. Very often you have at least buttons BTN_A and _B and BTN_START and _SELECT, but not always...

I am unsure what to do from here so I looked up how to retrieve the event log

If you want to write to file, maybe try with two angle characters instead: evtest /dev/input/event2 >> ~/evtest.log. But more importantly, try instead to center the joystick or disconnect it before running evtest again and noting down each button name for each button, and then maybe rearrange/connect some of them differently(especially BTN_START and BTN_SELECT, which don't work for you, and where probably one of them are connected incorrectly as BTN_THUMB).

Thanks for the update, unfortunately when I disconnect the joystick it still does a running list, so I filmed and hit the buttons in order - top 3, bottom 3, select, start.  https://drive.google.com/file/d/1-hyzkkVr3iOCNCAqEHfeuVsz5vkf4HZK/view?usp=sharing

Ok figured it out! Start now restarts the game, select takes you out!

Great! Glad to hear that it works now!

Thanks so much for your help!

You are welcome and thank you for the final write-up above for others to follow with similar arcade controllers! The idea stems from wanting to get my son's MakeCode Arcade creations playable on a big screen with some Raspberry Pis and some old PS3 console controllers lying around in the house. But my impression is that various impressive homemade arcade cabinet creations, like yours, is the more common use case. Sadly, I don't have any such arcade controllers at home to test myself, and they come in countless different flavours, so I appreciate your support here!

Just need a volume control for my usb and we will be all set!

Also thank you for finding and sharing a solution to the USB sound issues, which many have been complaining about, and that I also have been unable to figure out myself!

The kids will love this, time for me to get back to focusing on my coding in Makecode, to build out some games for this unit, thanks for all your hard work on this amazing platform, Makecode should be paying close attention to what you are doing!

Thanks for the kind words! MakeCode is really amazing, with Arcade and alle the supported hardware and interfaces(Minecraft), and the unique seamless transition from block based to text based programming! It's a real treat to watch how my son learns and evolves his programming and creative skills, and all his and the nice community's game creations(and all the creative maker stuff). It is also a bit odd to me that MakeCode therefore isn't the biggest thing around yet since the invention of ice cream... ;-) Anyhow, good luck with future cabinet and MakeCode coding projects for you and your students!
Microsoft, by the way, have been really supportive regarding compilation of MC Arcade games for the RPi, figuring out why the games froze the screen initially and the inner workings of the controller support. They also awarded McAirpos a link on the RPi hardware pages, so I guess we cannot complain... ;-)
But don't forget that McAirpos is as close to the definition of a kludge/hack as it is possible to get. The elegant and best (and probably not that hard for anyone competent enough in C++/TypeScript)solution to the screen freeze and controller support issues on the RPi(or other OS'es and devices) would have been directly in the compiler source code itself, which is open source, too. I am still battling with Bjarne Stroustrup's books, but this might be a fun challenge for anyone who dares to take it on, and I know that there are people in both the RetroPie and Recalbox teams who are willing to help anyone's efforts to integrate MakeCode Arcade game support into their installers and with their respective gamepad implementations.
That would be really cool, but not worth anyone's effort to build on top of the McAirpos hack. I don't know exactly why, but Microsoft seems to prioritize small handheld devices over native execution support on RPi(with many retro game users and systems) and other OS'es and devices, and the RPi community seems a bit lukewarm towards MakeCode. Maybe I am wrong.

Quick question I unplugged the joystick but I still got that running log, any idea why? thnx

I was wondering about the same thing myself. The closest thing I know about was the Raspberry Pi OS built in driver for the PS3 controller, which did not have a "dead zone" for the "analog"/graded thumb joysticks, and showed a similar behaviour. But this does not quite fit with running values in the interval 128-133(strange "center" values), and definitively not when still showing if the joystick is physically disconnected... But some switch/input is definitively in an "ON" state. Maybe a driver or electrical fault, where I would start searching for the error by first identifying what the axis ABS_Z really is. However, if it doesn't noticeably interfere with how your controller works in games, I would just leave it be.
One optimization tip, though: To maximize controller support, I added a calibration script to get max values for joystick left, right, up and down, which runs every time you start a game, and some redundant button mappings for uinput-mapper. If you ever get the time or need, the max values can be hard-coded for your specific controller instead and the redundant mappings removed in ../uinput-mapper/configs/arcade1.py to get somewhat better and more stable performance(sometimes your game character sprite might shoot in one direction until you have moved the stick fully in every direction). I once had a grand plan to make or gather from the community uinput-mapper config files for common controllers that should be supported, but I am personally not that fond of doing almost the same config operation many times over... ;-)

Thanks for all that, ive learned a lot  from this little adventure, one more question before I go, I am now attempting to use a potentiometer for the volume.  It looks like I will need to use 4 GPIOs, I am assuming the joystick/button encoder takes up some of these GPIOs, how would I determine which ones those are? thnx

Sorry, I have no experience with the GPIOs beyond a power button and script that I use. Your controller states a USB interface, and you mentioned audio over USB, as well. I thought USB was fully independent of the GPIOs on the RPi?
I would image, just like it is possible to read GPIO signals from a button press in the power Python script I am using, that it would be possible to have a program reading either voltages from a potentiometer position or button presses(up and down) from the GPIOs and then translate to volume levels or volume in-/decrements? But really I have no tested idea.

Thnx again, have a great day!

I reopened this issue for @sofiania, for the same controllers, from this issue:
https://github.com/Vegz78/McAirpos/issues/13

I get the game going, but I can't use the buttons, neither on keyboard nor the encoder...

Please read and follow this issue as best you can, and maybe you could ping @QuadDam (@dace at the MakeCode Arcade forum) for help here, as he is one who has actually had success with this.

is there any guide for this.

No, not that I know of outside:

The McAirpos readme
The relevant solved issues here and on the MakeCode Arcade forum.
The official guide for /sd/arcade.cfg
The uinput-mapper repository

I find a lot of troubleshooting threads, but no summary, so I'm a bit confused.

I understand your confusion(which I share...), controller support is a giant subject, where everything has to play together in the correct order, from:

Correct physical wiring, via
Working driver that recognizes and maps raw inputs events according to physical wiring in the Linux Input Subsystem, via
Mapping of EV_KEY digital input events correctly in /sd/arcade.cfg, to
Mapping of EV_ABS analog input events correctly in_~/McAirpos/McAirpos/uinput-mapper/configs/arcadeX.py_

Therefore, after advise from the creators of MakeCode Arcade, I have tried to the best of my abilities to maximize controller support out of the box in McAirpos, and then I leave it up to the community to help each other, share knowledge and maybe write guides, publish pull requests etc., and I try to help with the issues here and update the code when I have time.

I tried to change the config files, but neither keyboard nor encoder works (they both work in RetroPie though).

Please reset /sd/arcade.cfg and the ~/McAirpos/McAirpos/uinput-mapper/configs/arcadeX.py_ files to their original McAirpos state, where they are configured to play nicely together:
https://raw.githubusercontent.com/Vegz78/McAirpos/master/McAirpos/MakeCode/sd/arcade.cfg
https://github.com/Vegz78/McAirpos/tree/master/McAirpos/uinput-mapper/configs
Then, please start at the physical step 1. above, maybe with some help from reading further up inside this issue or from @QuadDam (@dace at the MakeCode Arcade forum).
Remember, that MakeCode Arcade games uses raw input event codes from keyboards and controllers, so normally you have to start from the beginning with checking the physical wiring(most common issue with DIY arcade controllers), and the, when it all works in McAirpos, reconfigure RetroPie etc. again/accordingly. McAirpos controller setup does not know about controller configuration in RetroPie, Recalbox etc., because it operates directly in the OS level below.
If stuck after trying a while, please post another question here.

I have now changed to this encoder https://www.electrokit.com/uploads/productfile/41017/SBC-ZDE-Datasheet.pdf, because it's the one the kids will have (I'll revert to the SJ@JX later). Could you point me to tha latest issue on this encoder, if there is anyone else who have tryed it? It would be really helpful. I have worked out the following so far:
Dragonrise inc generic USB joystick on event 4
Button 1 (K1) = TRIGGER
Button 2 (K2) = BTN THUMB = A
Button 3 (K3) = BTN THUMB2 = B
Button 4 (K4) = BTN TOP
Button 5 (L2) = BTN TOP 2
Button 6 (R2) = BTN PINKIE
Button 7 (L1) = BTN BASE
Button 8 (R1) = BTN BASE 2
Button 9 (SE) = BTN BASE 3
Button 10 (ST) = BTN BASE 4
Button 11 (K11) = BTN BASE 5
Button 12 (K12) = BTN BASE 6
I get A and B and the joystick to work, but the rest seem to work sometimes and sometimes not, and I randomly can't exit. It also seems like the B button (which acts like the B button in the game, also can select, hm...

This config does however not work in the RetroPie games.... I don't really get how it's supposed to work out of the box. It seems I need to configure them separately.

Deleted tha last comment. It does seem to work with both retropie and makecode games now!!! It seems that many of my "unstable" problems occurs when I an to fast for the system. If I press Button 10 (ST) = BTN BASE 4 it does exit, but the screen goes black for a while first. Still some strange things, like button B seems to be select plus the B-button. And Button 10 - exit also opens the manue if I exit from Makecode (the list of makecode games)

Try using evtest /dev/input/eventX | grep "(type 1) and see what pressing each of the buttons shows. Specifically, press B and select, and see what shows up. If they have the same button name, there might be a problem with the encoder. Maybe try plugging the select button into a different port on the encoder if another is available, and seeing if it fixes the issue.

This is B and select:

I have now changed to this encoder https://www.electrokit.com/uploads/productfile/41017/SBC-ZDE-Datasheet.pdf, because it's the one the kids will have (I'll revert to the SJ@JX later)
Originally posted by @sofiania in #10 (comment)

Closing this issue again as originally solved by @QuadDam, and can reopen again if others experience issues with the SJ@JX controller, or if @sofiania reverts to it later and still needs support.


[1.16.3] Does not generate pack.png seed correctly

Using the pack.png seed, instead of it generating the iconic hill, it generates this instead:

using alpha world type

The Alpha world type uses the Alpha 1.1.2_01 terrain generator, which is different than the one used from Alpha 1.2 to Beta 1.7.3.  Use the Beta world type.

That was it, thanks!


allow imagePath to be a function, useful for cache busting

Adds support for a function to be provided as the imagePath option. The current option doesn't easily allow for cache busting assets.
Usage:
var markerCluster = new MarkerClusterer(map, markers, {
    imagePath: function (i) {
      // would return something like m1-e359da86cb.png
      return imageCache['m' + (i + 1) + '.png']
    }
});

Haven't tested it but it makes sense and looks good!


Investigate installing over OKD/CRC

The goal of this issue is to collect in one place the issues that arise from installing the chart as is in an OKD/CRC cluster. OKD is the upstream, community version of OpenShift - think of it as what Fedora is to RHEL. CRC is their slimmed down, single node installation tool which lets you run OpenShift on your local development machine - think of it as kind is to Kubernetes.
You can find the CRC binaries here: https://www.okd.io/crc/ (no need for a RedHat account in this case, no matter what their documentation states).
I'll document the results of installing the chart here, which is the first step to understand what we need to do.

[x] Investigate zeebe chart (see https://github.com/camunda/camunda-platform-helm/issues/342#issuecomment-1179589677)
[x] Investigate zeebe-gateway chart (see https://github.com/camunda/camunda-platform-helm/issues/342#issuecomment-1179589677)
[x] Investigate zeebe and elastic (see https://github.com/camunda/camunda-platform-helm/issues/342#issuecomment-1179589677)
[x] Investigate curator and elastic (see https://github.com/camunda/camunda-platform-helm/issues/342#issuecomment-1179589677)
[x] Investigate operate
[x] Investigate operate and elastic
[x] Investigate operate and zeebe
[x] Investigate tasklist
[x] Investigate tasklist and elastic
[x] Investigate tasklist and zeebe
[x] Investigate identity
[x] Investigate identity and keycloak
[x] Investigate identity, operate, and keycloak
[x] Investigate identity, tasklist, and keycloak
[x] Investigate optimize
[x] Investigate optimize and elastic
[ ] Investigate a complete deployment

Running CRC is pretty simple. Download the binary from the page above (it's pretty hefty though), then simply run:
crc setup --check-only
crc setup
crc start

In the meantime, you can check the status to see when it's ready:
watch -n1 -- crc status

Starting takes quite a while the first time (~15 minutes for me), but should be faster after.

Zeebe

:tada: Zeebe gateway works out of the box, though there's no ingress definition so I didn't test using the built-in controller.
:tada: Zeebe broker works almost out of the box! Unfortunately the configMap volume for startup.sh (and I guess potentially exporters but I didn't try it out) is mounted with default mode 0484, which means our non-root user cannot do anything with it. It should be either configurable or mounted to at least 0555.

Elastic
As expected, the Elastic Helm chart has support already for OpenShift, so it just needs to be properly configured as shown here. Primarily you need to set the right security context, disable the initContainer which updates sysctl (e.g. updating the ulimits). Note that they mention setting fsGroup and runAsGroup in the podSecurityContext, but doing this actually produced errors for me. Omitting them entirely just worked.
Curator
Curator does not work out of the box, with a similar reason. The config must be mounted at the very least with 0444.
The first thing that's missing is configuring the user under which the container runs. Either this, or we default images to always run as non-root by default. In my opinion, running as non-root is not a bad idea as the default mode, though it will make debugging more complicated for us. Anyway, regardless.
Looks like our curator image/configuration does not work on OpenShift and crash loops out of the box.
Tips
I found it very useful when debugging networking and other stuff to have a busybox container running in my project. This is mostly because since you don't run as root, you won't be able to use apt to install things to your other containers. So you can use this definition:
apiVersion: v1
kind: Pod
metadata:
  name: debug
spec:
  containers:
    - name: busybox
      image: busybox:1.28
      args:
        - sleep
        - "1000000"

Which will start a long running busybox, where you can just kubectl exec -it debug -- sh to test network routes and the likes.
Conclusion
So zeebe, zeebe-gateway, elastic, and curator work with minimal fixes to the Helm chart. What's missing here is adding a configurable ingress template to zeebe-gateway, and using the built-in ingress class which maps to OpenShift Route objects.

Jfyi we added option to configure the defaultMode of the configMap see https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform/values.yaml#L142

We would need to be able to configure the mode for all volume mounts, essentially (other than PVC claims, as this seems to be mounted properly already).

Tasklist
:tada: Tasklist works out of the box with Elastic/Zeebe, without any special configuration.

Identity
Identity works out of the box, but both Keycloak and Postgresql must be configured properly.
identity:
  enabled: true
  keycloak:
    containerSecurityContext:
      runAsUser: null
    podSecurityContext:
      fsGroup: null
      runAsUser: null
    postgresql:
      primary:
        containerSecurityContext:
          runAsUser: null
        podSecurityContext:
          fsGroup: null
          runAsUser: null
      readReplicas:
        containerSecurityContext:
          runAsUser: null
        podSecurityContext:
          fsGroup: null
          runAsUser: null
      metrics:
        containerSecurityContext:
          runAsUser: null
        podSecurityContext:
          fsGroup: null
          runAsUser: null

By the way, setting values to null does not work with Helm 3.2.0+. This is a longstanding bug, where you either need to use Helm 3.1.3 (which is what I'm using for now), or use a post-renderer. See https://github.com/helm/helm/issues/9136 and https://github.com/helm/helm/issues/5184

Optimize
:tada: Runs fine out of the box, nothing special to configure.
Complete deployment
I couldn't test a complete deployment because the resource requirements are just too high. If I reduce them to a minimum, then things start crashing :smile:
Anyway, I deployed everything in the cloud with the following manifest (note, this is not the final one I would like to provide, but I adding it here for posterity):
global:
  image:
    tag: 8.0.4
    pullPolicy: Always
  identity:
    auth:
      enabled: true

zeebe:
  # Image configuration to configure the zeebe image specifics
  image:
    # Image.repository defines which image repository to use
    repository: camunda/zeebe
  # ClusterSize defines the amount of brokers (=replicas), which are deployed via helm
  clusterSize: "1"
  # PartitionCount defines how many zeebe partitions are set up in the cluster
  partitionCount: "1"
  # ReplicationFactor defines how each partition is replicated, the value defines the number of nodes
  replicationFactor: "1"

  # CpuThreadCount defines how many threads can be used for the processing on each broker pod
  cpuThreadCount: 4
  # IoThreadCount defines how many threads can be used for the exporting on each broker pod
  ioThreadCount: 4

  # do not run as root
  containerSecurityContext:
    runAsUser: null
  configMap:
    defaultMode: 0555

  # JavaOpts can be used to set java options for the zeebe brokers
  javaOpts: >-
    -XX:MaxRAMPercentage=25.0
    -XX:+ExitOnOutOfMemoryError
    -XX:+HeapDumpOnOutOfMemoryError
    -XX:HeapDumpPath=/usr/local/zeebe/data
    -XX:ErrorFile=/usr/local/zeebe/data/zeebe_error%p.log
    -Xlog:gc*:file=/usr/local/zeebe/data/gc.log:time:filecount=7,filesize=8M

  # Environment variables
  env:
    # Enable JSON logging for google cloud stackdriver
    - name: ZEEBE_LOG_APPENDER
      value: Stackdriver
    - name: ZEEBE_LOG_STACKDRIVER_SERVICENAME
      value: zeebe
    - name: ZEEBE_LOG_STACKDRIVER_SERVICEVERSION
      valueFrom:
        fieldRef:
          fieldPath: metadata.namespace
    - name: ZEEBE_BROKER_EXECUTION_METRICS_EXPORTER_ENABLED
      value: "true"
    - name: ATOMIX_LOG_LEVEL
      value: INFO
    - name: ZEEBE_LOG_LEVEL
      value: DEBUG
    - name: ZEEBE_BROKER_DATA_DISKUSAGECOMMANDWATERMARK
      value: "0.8"
    - name: ZEEBE_BROKER_DATA_DISKUSAGEREPLICATIONWATERMARK
      value: "0.9"
    - name: ZEEBE_BROKER_EXPERIMENTAL_CONSISTENCYCHECKS_ENABLEPRECONDITIONS
      value: "true"
    - name: ZEEBE_BROKER_EXPERIMENTAL_CONSISTENCYCHECKS_ENABLEFOREIGNKEYCHECKS
      value: "true"

  # Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limitsS
  resources:
    limits:
      cpu: 2
      memory: 2Gi
    requests:
      cpu: 1
      memory: 1Gi

  # PvcAccessModes can be used to configure the persistent volume claim access mode https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes
  pvcAccessMode: ["ReadWriteOnce"]
  # PvcSize defines the persistent volume claim size, which is used by each broker pod https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims
  pvcSize: 12Gi
  # PvcStorageClassName can be used to set the storage class name which should be used by the persistent volume claim. It is recommended to use a storage class, which is backed with a SSD.
  pvcStorageClassName: gp2

zeebe-gateway:
  # Replicas defines how many standalone gateways are deployed
  replicas: 1
  # Image configuration to configure the zeebe-gateway image specifics
  image:
    # Image.repository defines which image repository to use
    repository: camunda/zeebe
  # LogLevel defines the log level which is used by the gateway
  logLevel: debug

  # Env can be used to set extra environment variables in each gateway container
  env:
    - name: ZEEBE_LOG_APPENDER
      value: Stackdriver
    - name: ZEEBE_LOG_STACKDRIVER_SERVICENAME
      value: zeebe
    - name: ZEEBE_LOG_STACKDRIVER_SERVICEVERSION
      valueFrom:
        fieldRef:
          fieldPath: metadata.namespace
    - name: ATOMIX_LOG_LEVEL
      value: INFO
    - name: ZEEBE_LOG_LEVEL
      value: DEBUG
    - name: ZEEBE_GATEWAY_MONITORING_ENABLED
      value: "true"
    - name: ZEEBE_GATEWAY_THREADS_MANAGEMENTTHREADS
      value: "1"

  # Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits
  resources:
    limits:
      cpu: 1
      memory: 1Gi
    requests:
      cpu: 1
      memory: 512Mi

   # do not run as root
  containerSecurityContext:
    runAsUser: null

# RetentionPolicy configuration to configure the elasticsearch index retention policies
retentionPolicy:
  # RetentionPolicy.enabled if true, elasticsearch curator cronjob and configuration will be deployed.
  enabled: true
  # RetentionPolicy.schedule defines how often/when the curator should run
  schedule: "*/15 * * * *"
  # RetentionPolicy.zeebeIndexTTL defines after how many days a zeebe index can be deleted
  zeebeIndexTTL: 1
  # RetentionPolicy.zeebeIndexMaxSize can be set to configure the maximum allowed zeebe index size in gigabytes.
  # After reaching that size, curator will delete that corresponding index on the next run.
  # To benefit from that configuration the schedule needs to be configured small enough, like every 15 minutes.
  zeebeIndexMaxSize: 10
  # RetentionPolicy.operateIndexTTL defines after how many days an operate index can be deleted
  operateIndexTTL: 30
  # RetentionPolicy.tasklistIndexTTL defines after how many days a tasklist index can be deleted
  tasklistIndexTTL: 30

operate:
  enabled: true
  image:
    repository: camunda/operate
    tag: 8.0.4
  podSecurityContext:
    runAsUser: null
  resources:
    limits:
      memory: 2Gi
      cpu: 1
    requests:
      memory: 1Gi
      cpu: 1

tasklist:
  enabled: true
  image:
    repository: camunda/tasklist
    tag: 8.0.4
  podSecurityContext:
    runAsUser: null
  resources:
    limits:
      memory: 2Gi
      cpu: 1
    requests:
      cpu: 1
      memory: 1Gi

identity:
  enabled: true
  resources:
    limits:
      cpu: 1
      memory: 2Gi
    requests:
      cpu: 1
      memory: 1Gi
  keycloak:
    resources:
      limits:
        cpu: 1
        memory: 2Gi
      requests:
        cpu: 1
        memory: 1Gi
    containerSecurityContext:
      runAsUser: null
    podSecurityContext:
      fsGroup: null
      runAsUser: null
    postgresql:
      storageClass: "gp2"
      primary:
        resources:
          requests:
            cpu: 1
            memory: 512Mi
          limits:
            cpu: 1
            memory: 1Gi
        persistence:
          size: "2Gi"
        containerSecurityContext:
          runAsUser: null
        podSecurityContext:
          fsGroup: null
          runAsUser: null
      readReplicas:
        persistence:
          size: "2Gi"
        containerSecurityContext:
          runAsUser: null
        podSecurityContext:
          fsGroup: null
          runAsUser: null
      metrics:
        enabled: false

# ELASTIC
elasticsearch:
  enabled: true
  imageTag: 7.16.2

  replicas: 1
  minimumMasterNodes: 1

  volumeClaimTemplate:
    accessModes: [ "ReadWriteOnce" ]
    storageClassName: "gp2"
    resources:
      requests:
        storage: 32Gi

  esJavaOpts: "-Xmx1g -Xms1g"

  resources:
    requests:
      cpu: 1
      memory: 2Gi
    limits:
      cpu: 1
      memory: 3Gi

  securityContext:
    runAsUser: null

  sysctlInitContainer:
    enabled: false

  podSecurityContext:
    fsGroup: null
    runAsUser: null

optimize:
  enabled: true
  image:
    repository: camunda/optimize
    tag: 3.8.0
  partitionsCount: 1
  resources:
    requests:
      cpu: 1
      memory: 1Gi
    limits:
      cpu: 2
      memory: 2Gi

# PrometheusServiceMonitor configuration for the prometheus service monitor
prometheusServiceMonitor:
  # PrometheusServiceMonitor.enabled if true then a service monitor will be deployed, which allows a installed prometheus controller to scrape metrics from the broker pods
  enabled: false

Also you need Helm [3.0.0 - 3.1.3] to deploy this due to the bugs mentioned above. I'll add an example of how to use a post-renderer to work around this bug if you need to be on Helm 3.2.x or greater.

With that said, I think we can close this.


Use cublasGemmEx in tensordot_core when CUDA11

This PR modifies to use cublasGemmEx, an extension of cublas<t>gemm, as the matrix multiply backend to be called in tensordot_core in case of CUDA11. cublasGemmEx is flexible, allowing users to specify the data types for each of the matrices A, B, C, the precision of computation and the matrix multiply algorithm to be used.
https://docs.nvidia.com/cuda/cublas/index.html#cublas-GemmEx
This is a kind of preparatory PR and the following PR will allow the use of TF32 (TensorFloat32) as the compute precision of the matrix multiply.
This is related to https://github.com/cupy/cupy/issues/3602

Thank you for your comment, @leofang ! I've updated the branch based on your comment. Could you take a look when you have time?

Jenkins, test this please.

@asi1024 @takagi @kmaehashi I think Jenkins is dead since yesterday.

Jenkins, test this please.

Jenkins CI test (for commit 752de1bd9c4b0cd293ea6ac3f5b3af4494346095, target branch master) succeeded!

I will retrigger CI after https://github.com/chainer/chainer-test/pull/593 is merged.

Jenkins, test this please.

Jenkins CI test (for commit 752de1bd9c4b0cd293ea6ac3f5b3af4494346095, target branch master) succeeded!

LGTM!


:bd crashes nvim

I opened an issue in AstroNvim, and was told to transfer it here instead. I would make a more minimally reproducible example that cuts out the rest of the astro plugins, but unfortunately I have no idea how to do that.
Checklist

[X] Using a stable version of Neovim (i.e. not neovim nightly)
[X] :PackerSync
[x] :AstroUpdate
[X] Restarted AstroNvim

AstroNvim version
v2.4.2
Neovim version (>= 0.8)
NVIM v0.8.0
Operating system/version
macOS 12.6
Describe the bug
:bd crashes nvim
Steps to Reproduce

Run nvim
Open the file tree: <SPACE>e
Edit a file: :e foo.txt
Edit another file: :e bar.txt
Close the current buffer: :bd

Expected behavior
:bd should merely close the current buffer, not exit nvim completely
Screenshots
https://user-images.githubusercontent.com/6969415/197542344-e0e53ac2-386e-4ec8-889e-b60eaa7ebf07.mov
Additional Context
Return code:
❯ echo $?
0

Hi, @TheButlah
Your issue may be occurred by the default behavior of Neovim, not caused by Neo-tree.
AstroNvim already serves a  keymap of closing a buffer by hitting "c" so that you should use it.
See the details below:

famiu/bufdelete.nvim
Plugin list used in Astro
Default mappings of Astro(See, "close buffer"

Closing as solved


Add deprecation annotation to RelationshipExtraction

This pull request adds a deprecation annotation to Relationship Extraction to alert users to use the AlchemyLanguage service instead.

[Current coverage][cc-pull] is 85.39%

No coverage report found for master at 9b25723.

Powered by Codecov. Last updated by [9b25723...01ae7f2][cc-compare]
[cc-base-branch]: https://codecov.io/gh/watson-developer-cloud/ios-sdk/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/watson-developer-cloud/ios-sdk/compare/9b2572326d1f29a7dd6cbc53c57a76a8e8a6f759...01ae7f28c1c573fbd2c48bdb50f7446f54309cca
[cc-pull]: https://codecov.io/gh/watson-developer-cloud/ios-sdk/pull/366?src=pr


Incorrect registry information in OSPP - sethst

[Enter feedback here]
The ospp.vbs script > /sethst:value now does not set HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName any more in newer versions of OSPP (possibly because of Windows 10).
This needs update to newer value:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\APPID_GUID\SKUID_GUID\KeyManagementServiceName
A list of APPID and SKUID would be a plus.

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

ID: babf11e1-a068-ce1a-0157-d574a995f663
Version Independent ID: 235a8d72-2c4b-d4a0-1683-b275f64c055f
Content: Tools to manage volume activation of Office - Deploy Office
Content Source: DeployOffice/vlactivation/tools-to-manage-volume-activation-of-office.md
Product: office-perpetual-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Duplicate with issue #832


GitHub authn

This is a new PR like #115, but squashed.

This change is

@rojer squashed down to 11 commits already:

1 commit to add GitHub authn
1 commit for TokenDB
3 "typo" commits at the end

the rest is commits I'm having a hard time squashing because they depend on TokenDB. I'll try to see how I can simplify a bit more.

sorry for being pedantic, but this needs to be squashed more. for those who come later, back and forth about location of documentation or revalidate vs retrieve is really just noise. ideally, this should be three commits: pulling out TokenDB interface, implementing GH provider, fixing typos in old stuff. or two commits - adding new stuff and fixing typos in old stuff. or just one will do as well, just as long as it's not this noisy.

oh, something just changed on my screen. are you squashing? ok, let me know when you're done.

OK, I'm down to 3 commits now:

Add GitHub + TokenDB (because splitting the two was just a nightmare)
Fix a bug (nil in logs)
Fix typos

great, thanks!

Thanks for merging. Now to move to #118. If you want to comment and bring in ideas, I'll get coding on it soon.

just noticed that organization parameter is not documented in reference.yml, please send a followup.

@rojer see #120


Skip dimension of size 1 in contiguous checks.

Since PyTorch 1.13 dimension of size 1 have normalised strides in PyTorch which fail here when using DLPack. This was done to conform the torch stride representation and the one from numpy. Unfortunately this means we are stuck with PyTorch 1.12.0 in python models.
Here is the related issue on the server side.
I haven't found any contributing guidelines as to what format Pull Requests should take for the python_backend will be happy to apply any changes you deem necessary.
Description of the Torch Issue since PyTorch 1.13.0
PyTorch updated the way they handle strides for dimensions of size 1.
In Pytorch 1.12 :
import torch
from torch.utils.dlpack import to_dlpack, from_dlpack

x = torch.randn((1, 1, 768,768)).cuda()

y = from_dlpack(to_dlpack(x))

print(x.stride()) # (589824, 589824, 768, 1)
print(y.stride()) # (589824, 589824, 768, 1)

In PyTorch >= 1.13:
import torch
from torch.utils.dlpack import to_dlpack, from_dlpack

x = torch.randn((1, 1, 768,768)).cuda()

y = from_dlpack(to_dlpack(x))

print(x.stride()) # (589824, 589824, 768, 1)
print(y.stride()) # (1, 1, 768, 1)

Closes: https://github.com/triton-inference-server/server/issues/6102

@Tabrizian Have you had some time to look at this ?
This would enable using PyTorch >= 1.13 in python models in Triton which would enable torch compile too

Thanks for fixing this issue. This PR looks good to me. Could you please sign the CLA as instructed here: https://github.com/triton-inference-server/server/blob/main/CONTRIBUTING.md#contributor-license-agreement-cla

Looks like there is a formatting issue: https://github.com/triton-inference-server/python_backend/actions/runs/5659827069/job/15605216705?pr=281
Could you please format the PR using the pre-commit instructions here: https://github.com/triton-inference-server/server/blob/main/CONTRIBUTING.md#coding-convention

thanks, I can confirm that we've received the CLA. I'm running the CI now and will merge if the CI looks green.

@Tabrizian I forgot to ask, do you know when this will be shipped in the Triton container ?

This should be included in the 23.09 release.

Perfect, thank you very much !!


Improve self-talk test utils

Please note that while we are transitioning from travis-ci to AWS CodeBuild, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Description of changes:
Our current self-talk test utility method doesn't handle errors properly. Instead of failing when the error occurs, it fails when our peer tries to read the message we failed to write due to the error. This means that all the self-talk tests that use this method only ever fail with "blocked" errors. This makes debugging the tests painful.
While I was fixing this, I also updated any test that had implemented its own version to just use the common test utility, so we only have to get this right once.
I also added notnull_checks to s2n_negotiate so my test would pass instead of seg fault :(
Testing:
I wrote a test for our test method to ensure it produces the right error. The behavior I'm testing doesn't get triggered by other unit tests because it only matters to failing tests; this only comes up when a developer is trying to get a failing test to pass.
Before the fix, the new test would produce:
 Error Message: 'underlying I/O operation would block'
 Debug String: 'Error encountered in s2n_recv.c line 70'
 System Error: Resource temporarily unavailable (11)

That's not helpful :( After the fix, the test produces:
 Error Message: 'NULL pointer encountered'
 Debug String: 'Error encountered in s2n_handshake_io.c line 1052'
 System Error: Socket operation on non-socket (88)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1984 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1984      +/-   ##
==========================================
- Coverage   89.18%   89.17%   -0.02%
==========================================
  Files         149      149
  Lines       11523    11525       +2
==========================================
  Hits        10277    10277
- Misses       1246     1248       +2


Error: ModuleNotFoundError: No module named 'datasets.arrow_dataset'

Hi there,
I'm currently using continuum 1.2.7 but I got this error when trying to import CIFAR10.
Here the traceback of the error:
File "/code/src/cl2r/main.py", line 17, in <module>
    from cl2r.utils import create_pairs, update_criterion_weight, BalancedBatchSampler
  File "/code/src/cl2r/utils.py", line 12, in <module>
    from continuum.datasets import CIFAR10
  File "/code/venv/lib/python3.10/site-packages/continuum/__init__.py", line 11, in <module>
    from continuum.scenarios import *
  File "/code/venv/lib/python3.10/site-packages/continuum/scenarios/__init__.py", line 14, in <module>
    from continuum.scenarios import hf
  File "/code/venv/lib/python3.10/site-packages/continuum/scenarios/hf/__init__.py", line 3, in <module>
    from continuum.scenarios.hf.huggingface_fellowship import HuggingFaceFellowship
  File "/code/venv/lib/python3.10/site-packages/continuum/scenarios/hf/huggingface_fellowship.py", line 4, in <module>
    from datasets.arrow_dataset import Dataset as HFDataset
ModuleNotFoundError: No module named 'datasets.arrow_dataset'

I've found this in the following two files:
https://github.com/Continvvm/continuum/blob/master/continuum/scenarios/hf/huggingface_continual.py#L5
https://github.com/Continvvm/continuum/blob/master/continuum/scenarios/hf/huggingface_continual.py#L5
and the problem is that is in dataset there is no arrow_dataset.py file.
Can you fix it?
Best Niccolò

Hi Timothée,
thanks for your reply!
I have installed the 2.11.0 version of the datasets packages.
Bests
Niccolò

If you do just:
import datasets
from datasets.arrow_dataset import Dataset as HFDataset

Does that work?

Yes it works, probably I got some package versions crash.
I reinstalled again by virtual env and it works!
Thanks a lot,
Niccolò


Can't release 2.4.0 ...

I don't have access to release guard-minitest 2.4.0 (one commit before master), since I'm not an owner of the gem.
@rymai, @genericsteele, @yannlugrin - could and of you give me access and/or release 2.4.0?
Thanks!

@e2 I've added you as owner to https://rubygems.org/gems/guard-minitest

Thank you ssooooooo much!

Thanks @rymai and @e2!


Add generalized implementation of MapResult which supports infinite p…

As MapResult was not supporting more than 16 verbs in its generic templates, I patched this which supports infinite number of verbs. I think it can be a more generalized implementation.

Thanks for work.
Can you add #621 as a unit test?

@moh-hassan it's done now

Can you show an example how to use this method in case of async/await?
It's nice if you add it as a test case.

I did a test for async/await and it's fine.
We can do it in wiki, and no need to modify PR.

fixed a wrong mapping value in tests


Remove the need of anyuid permission on OpenShift

Remove the hard-coded usages of runAsUser and runAsGroup in charts
Where necessary, replace them with a helm field .ProxyUID and .ProxyGID.
When running in OpenShift, these fields will be set at runtime based on annotations present on the pod's namespace.
When not on OpenShift (strictly speaking, when such annotations are not present), these values fallback to the current, defauls value of 1337.

With this change we can remove the extra steps related to anyuid in the OpenShift setup page.

Does openshift block the UIDs at Deployment level or only Pod level?

Does openshift block the UIDs at Deployment level or only Pod level?

Replicaset level.

I am a bit worried these changes may have some subtle negative impact on non-openshift users. This is a bit vague since I don't have any concrete criticisms, more of the unknown-unknown of the template changes

The general idea is to remove hardcoded values in RunAs fields in the deployments. If this field is absent, Kubernetes will honor the USER value of the container image. OpenShift will automatically assign a value derived from an range defined in a namespace annotation.
If we change the USER field in the base proxy image to be 1337 - which we did in this PR - we can remove the RunAs declarations in some places. Kubernetes will use 1337 and OpenShift will assign a value at runtime.

The issue is if users are currently running the images without explicitly setting runas, they are now changed from 0 to 1337. See https://github.com/istio/istio/pull/45394#discussion_r1227012907 - I am 100% certain this will break some of our users.
To be fair - its a good end result, we don't want users running as root. But I am a bit worried about the breakage.
Does openshift even need it? Can we just keep 1337 hardcoded as-is, and then override with the max UID range on openshift as added in this PR?

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I reverted the + USER 1337:1337 change I had done in proxy dockerfile. Hopefully changes now are safe.

@jwendell you have a do-not-merge, LGTM to merge when you are ready

@jwendell : I am trying to run integration tests locally on my mac, and starts getting the below error today. This used to work before. Do you think it is related?
2023-08-30T08:16:27.591923Z	error	Pod injection failed: failed to run injection template: template: inject:88:9: executing "inject" at <.ProxyUID>: can't evaluate field ProxyUID in type *inject.SidecarTemplateData
2023-08-30T08:16:27.996153Z	info	Sidecar injection request for echo1-5-51122/a-v1-7868db5759-***** (actual name not yet known)
2023-08-30T08:16:27.998146Z	error	Invalid template: template: inject:88:9: executing "inject" at <.ProxyUID>: can't evaluate field ProxyUID in type *inject.SidecarTemplateData

@jwendell : I am trying to run integration tests locally on my mac, and starts getting the below error today. This used to work before. Do you think it is related?
2023-08-30T08:16:27.591923Z	error	Pod injection failed: failed to run injection template: template: inject:88:9: executing "inject" at <.ProxyUID>: can't evaluate field ProxyUID in type *inject.SidecarTemplateData
2023-08-30T08:16:27.996153Z	info	Sidecar injection request for echo1-5-51122/a-v1-7868db5759-***** (actual name not yet known)
2023-08-30T08:16:27.998146Z	error	Invalid template: template: inject:88:9: executing "inject" at <.ProxyUID>: can't evaluate field ProxyUID in type *inject.SidecarTemplateData

ignore, things are working fine when I use latest test image.


[Infra] UI Docker failure

The following error appears:
 => [builder 6/7] WORKDIR /app/switch-manager-react                                                                                0.0s
 => ERROR [builder 7/7] RUN npm run build                                                                                2.8s
------
 > [builder 7/7] RUN npm run build:
0.442
0.442 ><EMAIL_ADDRESS>build
0.442 > tsc && vite build
0.442
2.746 src/api/mutations/upsertFullConnection.tsx(26,7): error TS2322: Type 'any[]' is not assignable to type 'never[]'.
2.746   Type 'any' is not assignable to type 'never'.
2.747 src/api/mutations/upsertFullConnection.tsx(27,7): error TS2322: Type 'any[]' is not assignable to type 'never[]'.
2.747 src/components/inputs/datePicker.tsx(8,20): error TS2307: Cannot find module '@icons/carret.svg?react' or its corresponding type declarations.
2.747 src/components/inputs/toggle.tsx(3,22): error TS2307: Cannot find module '@icons/toggleOn.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/connection/form/TechnicalSection.tsx(10,18): error TS2307: Cannot find module '@icons/lock.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/connection/form/TechnicalSection.tsx(11,20): error TS2307: Cannot find module '@icons/lock-open.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/connection/form/TechnicalSection.tsx(13,17): error TS2307: Cannot find module '@icons/gps.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/connection/form/index.tsx(9,19): error TS2307: Cannot find module '@icons/cross.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/header/TableHeaderCell.tsx(3,20): error TS2307: Cannot find module '@icons/carret.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/header/index.tsx(1,19): error TS2307: Cannot find module '@icons/house.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/header/index.tsx(2,21): error TS2307: Cannot find module '@icons/network.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/header/index.tsx(3,22): error TS2307: Cannot find module '@icons/customer.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/header/index.tsx(4,22): error TS2307: Cannot find module '@icons/calandar.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/row.tsx(3,26): error TS2307: Cannot find module '@icons/computer.svg?react' or its corresponding type declarations.
2.747 src/routes/connections/table/row.tsx(4,22): error TS2307: Cannot find module '@icons/ethernet.svg?react' or its corresponding type declarations.
2.747 src/routes/dashboard/navigation/SearchBar.tsx(4,20): error TS2307: Cannot find module '@icons/search.svg?react' or its corresponding type declarations.
2.747 src/routes/dashboard/navigation/SearchBar.tsx(94,17): error TS2322: Type '{ sm?: boolean | undefined; icon?: FunctionComponent<SVGAttributes<SVGElement>> | undefined; text?: string | undefined; onError?: ReactEventHandler<...> | undefined; ... 266 more ...; disabled: boolean; }' is not assignable to type 'IntrinsicAttributes & IconFilterElemProps'.
2.747   Property 'disabled' does not exist on type 'IntrinsicAttributes & IconFilterElemProps'.
2.747 src/routes/dashboard/navigation/filters.tsx(6,22): error TS2307: Cannot find module '@icons/customer.svg?react' or its corresponding type declarations.
2.747 src/routes/dashboard/navigation/filters.tsx(7,19): error TS2307: Cannot find module '@icons/house.svg?react' or its corresponding type declarations.
2.748 src/routes/dashboard/navigation/filters.tsx(8,21): error TS2307: Cannot find module '@icons/network.svg?react' or its corresponding type declarations.
2.748 src/routes/dashboard/navigation/filters.tsx(9,22): error TS2307: Cannot find module '@icons/computer.svg?react' or its corresponding type declarations.
2.748 src/routes/dashboard/navigation/filters.tsx(10,22): error TS2307: Cannot find module '@icons/asterisk.svg?react' or its corresponding type declarations.
2.748 src/routes/dashboard/navigation/index.tsx(4,24): error TS2307: Cannot find module '@icons/search.svg?react' or its corresponding type declarations.
2.748 src/routes/dashboard/navigation/index.tsx(5,19): error TS2307: Cannot find module '@icons/cross.svg?react' or its corresponding type declarations.
------
Dockerfile:8
--------------------
   6 |     COPY . .
   7 |     WORKDIR /app/switch-manager-react
   8 | >>> RUN npm run build
   9 |     # Stage 2: Create the production image
  10 |     FROM nginx:mainline-alpine-slim
--------------------
ERROR: failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2

When I'm trying to build with the following Dockerfile:
# Stage 1: Build the React app
FROM node:lts-slim as builder
WORKDIR /app
COPY switch-manager-react/package*.json ./
RUN npm install --legacy-peer-deps
COPY . .
WORKDIR /app/switch-manager-react
RUN npm run build
# Stage 2: Create the production image
FROM nginx:mainline-alpine-slim
COPY --from=builder /app/build /usr/share/nginx/html
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]

removed tsc from the npm run build, it was left from the react-create-app scripts.
It should work as expected now


[Bug]: Save Workspace doesn't appear to be working correctly

What happened?
After generating an image, I saved the workspace. After doing some additional outpainting on top of that, I wanted to save again, so I clicked the floppy disk icon to save. Didn't get a popup to save the filename, so I guessed that it saved under the same name. Later, did a refresh, and lost the work that occurred after the first save.
I manually reproduced this sequence of events with the console open, and noticed an error during the second save:
Uncaught TypeError: Cannot read properties of undefined (reading 'name')
    at workspaces.put.onsuccess (workspace.populate.js?v=2aea61f:101:60)
workspaces.put.onsuccess @ workspace.populate.js?v=2aea61f:101
IndexedDB (async)
workspaces.get.onsuccess @ workspace.populate.js?v=2aea61f:100

Then, I tried to delete the workspace that was initially created on the first save and I see this error:
Uncaught (in promise) DOMException: Failed to execute 'delete' on 'IDBObjectStore': The transaction has finished.
    at workspaces.get.onsuccess (http://<IP_ADDRESS>:7860/file=extensions/openOutpaint-webUI-extension/app/js/initalize/workspace.populate.js?v=2aea61f:180:23)
workspaces.get.onsuccess @ workspace.populate.js?v=2aea61f:180

Steps to reproduce the problem

Go to openOutpaint via A1111 extension in Chrome. Open the console in DevTools
Generate an image via the Dream tool
Save the workspace and give it a name
Outpaint the image
Try to save the workspace again.
See the first error in the console: Cannot read properties of undefined reading ('name')
Try to delete this workspace
See the second error in the console: Failed to execute 'delete' on 'IDBObjectStore': The transaction has finished.

What should have happened?
I think what should have happened was either the current workspace gets updated when the new data, or a new popup dialog box opens up with the current workspace name/ability to add a new name.
Commit where the problem happens
5e84d6d5
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Google Chrome
Browser Extensions/Addons
No extensions installed
AUTOMATIC1111 webUI Commandline Arguments
--allow-code --xformers --enable-insecure-extension-access --api --port 7860 --cors-allow-origins=http://localhost:7860
Additional information
Screenshot of console after going through the above sequence of steps:

terribly sorry for the extended delay; this project isn't abandoned but i've had to step away from it due to Reasons for a while, and i admit additional responses may (aka will probably) be delayed but hopefully not nearly as long
confirming issue experienced here, will definitely look into this, my apologies for the trouble :( can't exactly provide an ETA due to aforementioned Reasons but i just wanted to at least respond that this is noted with regrets

fixed in https://github.com/zero01101/openOutpaint/commit/b369d3cfcfccf66462b5c6bb131e781f47ed4725


Displaying terminal ansi color characters

This pull request adds ansi color characters decoding using ansi_up.js. It also escapes HTML so no need for _escape function any more.
Tests are passing!

Looks like lint is not passing. Could you add ansiup to https://github.com/mthenw/frontail/blob/master/.jshintignore?

Actually I will do that after merging

v2.3.0 published. Thanks for contibution!


refactor(ArgumentsRenderingTree): split buildInputValue function into smaller functions for better maintainability

The first thing that stood out to me was that the code was doing a lot of type checking and then creating different types of objects based on those checks. This is a classic use case for the Factory pattern. The Factory pattern is a creational design pattern that provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created.
Another principle I kept in mind while refactoring was the Single Responsibility Principle. This principle states that a class should have only one reason to change. It should do one thing and do it well. So, I created three separate factory classes - ValueFactory, ArrayValueFactory, and ObjectValueFactory. Each of these factories are responsible for creating a specific type of object. The ValueFactory creates a value of the appropriate type based on the input, ArrayValueFactory creates an ArrayValue object, and ObjectValueFactory creates an ObjectValue object.
Refactoring the code in this way makes it more readable and maintainable. It's easier to understand what each part of the code is doing because each class has a clear, single responsibility. If you need to change how a certain type of object is created, you know exactly where to go to make that change.

Hi @AikoRamalho.
Thank you for submitting your contribution!
I am sorry, but we've decided we will not merge it. Whether or not functional style (3 pure functions) this code is originally written in is inferior to OOP-style (3 factory classes) this PR introduces is up to debate and big part of it comes down to a personal preference. A lot of classic GoF design patterns were designed for working around Smalltalk and pre-ISO C++ weakness and might not be that relevant for different paradigms. If you are interested in this discussion, this Stackoverflow thread will provide a nice starting point.
Lastly, if you are interested in contributing to Prisma, I'd suggest to pick up some small improvement or a bug fix, rather than refactoring - it is much less likely that those kinds of tasks will get merged afterward. Since you are already looking into error rendering code, one of the existing issues on the topic might of interest. Let me know if you need any guidance.


Spawn local

This is a very simple implementation of spawn_local, a function that spawns a rust future using the javascript promise infrastructure as the executor.

Are the docs good enough? It might be that the module documentation needs to be changed.


Increase max_connect_errors to avoid timeouts triggered by health checks

When behind load balancers like AWS ELBs, the MySQL server will get hit by TCP health checks. These health checks look like partial connection attempts to MySQL, so MySQL blocks the host trying to connect (which is the load balancer) after max_connect_errors. Since this Docker image isn't meant to allow arbitrary hosts to connect (either an ELB will be connecting or a small finite set of app instances behind inside a VPC will be connecting), I don't think we need the protection of max_connect_errors. Instead, we should set it to a high value (the value set here would allow for 10 years of health checks every 30 seconds) so that we actually get the benefit of health checks without the possibility of a blocked internal app or load balancer.
I can patch this onto the "standardized" branch as well if nobody objects to the patch.

Looks good to me, though it's a shame there's not a better workaround. If you're going to patch "standardized", the config change can go in templates/etc/mysql/conf.d/overrides.cnf.

Merging this sucker and I also opened a PR with this commit ported to the standardized branch.


Is \n hard coded into CSS Beautifier logic?

JSBeautifier released 1.5.6 with an "eol" fix.
I am looking at the CSS Beautifier code (beautifiy-css.js) and it looks like there are a lot of hard coded  "\n".
I am on a Windows system and I am noticing the files are getting changed in git, but without any visible changes, so I am suspecting its a line ending problem between Windows/Linux environments.
Could it be that CSS Beautifier should have its own eol fix as well?

Yes, it should.

Awesome work, thanks!


Added override keyword to codefix implemented abstract methods

Passes an overridesAbstract flag down the codefix methods so the member adder knows whether to add an override keyword.
Fixes #50464

@typescript-bot pack this


Fix(keymaps): change v mode to x mode for save file

While trying to disable <C-s> entirely by vim.keymap.del({ "i", "v","n", "s" }, "<C-s>") in my own keymaps.lua, I got an error on reopening Neovim No such mapping. After tinkering around a bit, I changed v to x, since v incorporates both x and s and the error stopped occuring.

Strange, vim.keymap.del({ "i", "v", "n", "s" }, "<c-s>") also gives me a No such mapping error, but vim.keymap.del({ "i", "n", "s", "v" }, "<c-s>") does not.

Yes, it gives the error as long as s comes after v. If s comes beforehand, then I also don't notice such error. The first time i noticed it because I tried with the order the keymap was set in lazyvim keymaps. Anyway, I'm not too confident about Neovim's internals, but also from the help it seems that v supersedes x and s. So, I thought maybe it would be good to distinguish them when setting the keymap?

I also noticed the error.
As an alternative, maybe removing the s from LazyVim's definition is a solution as well, as v implies both x and s.
In that case, when removing v, s is also removed. Thus, when removing s after v, the no mapping error occurs.
I do hope I interpret :h map-overview correctly.
In my own keymaps, I currently don't include the s specified by LazyVim:
-- save file with C-s in all modes
-- "s", -- stacktrace ...
for _, mode in pairs({ "i", "v", "n" }) do
  vim.keymap.del(mode, "<C-s>")
end

The result is as expected.

Yes, of course it could be done that way as well. I just left it there, because I interpreted it like folke would like to distinguish between them for some reason from the initial code. It's up to him to decide which way to go.  The same result will be achieved.

Hi @dpetka2001,
I described an alternative and its reasoning, on a problem I recognized, without disqualifying your changes. Just to make sure:

Yes, of course it could be done that way as well.

I am uncertain on how to interpret that quoted line. I hope my comment did not offend you.

No no, absolutely no offense at all taken. I totally agree with your point as well. It's one way or the other. I'm fine with either to be honest.

No no, absolutely no offense at all taken

That's a relief, as I am a big fan of your contributions to this project! It's not always easy to know how written text is interpreted by the receiver. Thanks!


Closes #423 - Improve error handling if user does not include all config...

...uration files

+1


config: bump to 2.0.0+6 for production release

Ref #167

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3853

Relevant Lines:
5239

💛  - Coveralls


DynamicsPerf In Prod

Is it recommended to run the DynamicsPerf Job's and batch all time or only when we need to troubleshoot.
I don't find any overload but want to know the best practice ?

I would only use it for troubleshooting. It is the perfect tool for it if
you are using it on the right way. Just send me a email if you need help.
On Thu, Mar 28, 2019 at 4:26 AM toronyax<EMAIL_ADDRESS>wrote:

Is it recommended to run the DynamicsPerf Job's and batch all time or only
when we need to troubleshoot.
I don't find any overload but want to know the best practice ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PFEDynamics/DynamicsPerf/issues/11, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFrlpHluAT4WBDH2OM1FEwy0zlUsbRmDks5vbDZKgaJpZM4cPNkV
.

--
Groeten
Alexander


Service status Jamf Pro extension attribute

I made a quick script to get the status of Outset and return it as an extension attribute. I'm using this alongside a smart group to determine if any services are somehow disabled by a local user.

While this will tell you the state of the services it's a bit raw. Could we consider cleaning it up into a "Healthy/Not Healthy" type status instead?
e.g. if any of the agents return something other than Enabled then the EA will indicate it with a simple value, rather than show the raw output of --service-status.

The script now counts the number of enabled services, which should equal 6. If all services are enabled it will report "Healthy" otherwise it will return "Not Healthy"


feat: add path to NormalizeError and ParseError

This makes it easier to use the library in our schema plugin

somewhat related to https://github.com/dylibso/xtp-go-bindgen/issues/14


GET /v1/projects not returning all projects for LDAP user on v0.56.1

After upgrading to v0.56.1 (from v0.51.0), we've noticed a user logging in via LDAP (even if they're set as "admin" as user type) sees a restricted subset of projects in a GET /v1/projects call. Specifically, they only see projects where hosts have been joined to the environment. We can GET the specific project ID without hosts if we know the ID, but it doesn't show up in the list of all projects.
Because we have authentication enabled, we can't create API keys anymore for the built-in admin user (account id 1a1, user "admin") and so this is affecting our ability to automate environment creation. We can't join hosts automatically to a newly created environment if there's no way to find the project ID for that environment (which allows us to find the registration token for the Rancher agent).
The API key associated with 1a1 existed prior to enabling authentication which is the only reason any part of this process works.

Does /v1/projects?all=true return what you want?
The /v1/projects list is just the ones the account is a member of (so that you don't have to see every project on earth because you happen to be an admin), and the UI uses /v1/projects?all=true to load the full list for the environment management screen.
None of this is new though so it's not clear why you've seen a change in behavior;  @hibooboo2 is looking into the 51->56 diff.

Yes it does! Is there any reason why this filter isn't declared in the filters section for the project API? Or is that a global filter?

It's not a "real" filter because there isn't an actual field with a "am I a member of this" value to filter based on.. Added to https://github.com/rancher/rancher/issues/1052

Closing in favor of #1052


Reports about the build needed for the demo work

I don't think this is necessary since there's an example at the bottom of the page

This PR is based on feedback from my local community. More than one time they had doubts with this situation.

I'd rather add global note at the beginning of the guide: http://router.vuejs.org/en/essentials/getting-started.html

All examples will be using the standalone version of vue to make template parsing possible

@fnlctrl What are your thoughts on this?

Yeah, that should work.

@vinicius73 Do you find that statement clear enough?

yes @posva is much better so I will update.


Forget not working

setting()->forget('foo'); does not work and setting()->forget('foo')->save() gives Call to a member function save() on null ;

For some reason I never actually had the need to use the forget function even though I have been using this package for 2 years.
Will look into it and see what the issue might be.
-TT

Oh wait, just noticed the issue, you are chaining the methods. That wont work.
using setting()->forget('foo') will remove the key from the array but not persist it, you need to call setting()->save() afterwords to persist the change. You cannot chain them.
setting()->forget('foo');
setting()->save();

-TT

Thanks, figured it out.


node_modules_reactnativerouterflux_node_modules_reactnavigationstack_dist_views_assets_backiconmask.png: error: Invalid filename.  Unable to add.

"react": "16.4.0",
"react-native": "0.55.4",
"react-native-router-flux": "^4.0.1",

android/app/build/intermediates/res/merged/release/drawable-mdpi/node_modules_reactnativerouterflux_node_modules_reactnavigationstack_dist_views_assets_backiconmask.png: error: Invalid filename.  Unable to add.

Solution:
node_modules->react-native-router-flux->node_modules->react-navigation-stack->dist->views->assets->backiconmask.png find backiconmask.png delete， to  node_modules->react-native-router-flux->node_modules->react-navigation-stack->dist->views->assets->Header->Header.js change line 334 <Image source={require('../assets/back-icon.png')} style={styles.iconMask} />

Hi @js1121302139 - glad you found a workaround to this issue. Even happier that you not just found it and come back and wrote it down here and in other issue where other user was having the same problem.
This was a known issue with react-native and gradle and it seems that is fixed with<EMAIL_ADDRESS>as seen here: https://github.com/facebook/react-native/issues/16906.


[Renew Key] Upcoming expiration of our current sub public key (expire on 20230512)

This is a reminder that the new sub public key that we extended in #2040 will expire on 20230512.
We need to take action to extend the key again before that.
Guide: https://github.com/opensearch-project/opensearch-build/issues/2040#issuecomment-1125449385

Upload the key to the production S3 bucket while work with project-website on it.
Upload to keyserver: https://github.com/opensearch-project/opensearch-build/issues/2040#issuecomment-1132261924
Update on https://opensearch.org/verify-signatures.html
Make sure the key will expire in exactly one year on 20240512.

Thanks.

Hi,
@bbarani this is for 20230512 expiration which is the extension of our extended key.
Thanks.

@rishabh6788 are we tracking it via current monitoring and alarms?

We are on the way to replace the new public key with SHA2 hash.

https://github.com/opensearch-project/opensearch-build/issues/3124#issuecomment-1533752538

Related website changes: https://github.com/opensearch-project/project-website/issues/1562

The key is out now to the public:
https://opensearch.org/verify-signatures.html


VS2012 issue

As VS2012 lacks complete support for c++, and only missing function involved in minijson_writer is std::isinfinite, there is workaround which could be included in code.
from
#define MJW_CPP11_SUPPORTED __cplusplus > 199711L || _MSC_VER >= 1800
to
#define MJW_CPP11_SUPPORTED __cplusplus > 199711L || _MSC_VER >= 1700
#if _MSC_VER == 1700
namespace std {
	template<typename T> bool isfinite(T t)	{
		return t == t && t != std::numeric_limits<T>::infinity() &&	t != std::numeric_limits<T>::infinity();
	}
}
#endif

Well... I think VS2012 can be considered a legacy toolchain and if you have Boost you can probably just compile the code as it is, can't you? Sorry, I don't think it's worth it to mess with those already ugly macros and re-implement a basic Boost/standard library function for supporting VS2012, considering that it will soon disappear (I hope), I have no way to support it in the long run (I'm not going to install it), and you already have the workaround.


GeoLocator - Request - Get NMEA string and Number of Satellites

From @tlhintoq on June 13, 2016 15:54
This is a

[X] Feature Request

Which plugin does this impact:

[x] Geolocator

Feature Request:
It would be really great if the Number of Satellites and raw NMEA string could be accessible properties just like Latitude, Longitude etc.  I feel silly contemplating have to create my own dependency service for these when GeoLocator is (presumably) already grabbing this data. Not to mention worrying that two different services trying to grab the same data just smells like trouble.
Copied from original issue: jamesmontemagno/Xamarin.Plugins#330

Will not implement, out of scope


ERROR running force:source:deploy: Component conversion failed: Cannot read properties of undefined (reading 'RecordType')

Hello,
I have updated my SFDX cli to 7.183.1 using below docker image
https://hub.docker.com/layers/salesforce/salesforcedx/7.183.1-full/images/sha256-d6e0eff7e16b3914b701b07312c576b890a8d33bb704f143e764f791cc82958e?context=explore
and while i am trying to run below sfdx:force:deploy command I am encountering this issue..
sfdx force:source:deploy --manifest manifest/package.xml  --loglevel error --targetusername $USERNAME --checkonly --testlevel RunLocalTests -w 60
›   Warning: sfdx-cli update available from 7.183.1 to 7.186.2.
ERROR running force:source:deploy:  Component conversion failed: Cannot read properties of undefined (reading 'RecordType')
However while running the same command from VSCODE is not throwing this error.In my system the CLI version is too 7.183.1 which is successfully executing the command.
Note:Even I tried updating to the latest version(7.186.2),which throws the same error
ERROR running force:source:deploy:  Component conversion failed: Cannot read properties of undefined (reading 'RecordType')
JSON OUTPUT:
{
"status": 1,
"name": "Conversion",
"message": "Component conversion failed: Cannot read properties of undefined (reading 'RecordType')",
"exitCode": 1,
"actions": [],
"context": "Deploy",
"stack": "Conversion: Component conversion failed: Cannot read properties of undefined (reading 'RecordType')\n    at MetadataConverter.convert (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/metadataConverter.js:107:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async MetadataApiDeploy.getZipBuffer (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/client/metadataApiDeploy.js:380:35)\n    at async Promise.all (index 0)\n    at async MetadataApiDeploy.pre (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/client/metadataApiDeploy.js:285:29)\n    at async MetadataApiDeploy.start (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/client/metadataTransfer.js:41:29)\n    at async ComponentSet.deploy (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:196:9)\n    at async Deploy.deploy (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-source/lib/commands/force/source/deploy.js:107:28)\n    at async Deploy.run (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-source/lib/commands/force/source/deploy.js:33:9)\n    at async Deploy._run (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/command/lib/sfdxCommand.js:102:40)\n    at async Config.runCommand (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/config/config.js:272:25)\n    at async run (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/main.js:74:5)\nCaused by: TypeError: Cannot read properties of undefined (reading 'RecordType')\n    at RecompositionFinalizer.recompose (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:87:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RecompositionFinalizer.finalize (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:43:38)\n    at async ConvertContext.executeFinalizers (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:264:17)\n    at async ComponentConverter._flush (/usr/local/lib/nodejs/lib/node_modules/sfdx-cli/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/streams.js:87:30)",
"warnings": [],
"commandName": "Deploy"
}
Upon further investigation I found If Custom Object is added to my package.xml its throwing above error.
Is there any issue with the docker image or package.xml
Any suggestions on this is really appreciable

@satyasfdc6 there's some instructions in our issue template that provide version and plugin information we need.  Can you please run that?

Looking into where this error is coming from, can you check that your metadata looks like
objects/
└ Something__c/
└ Something__c.object-meta.xml
└ recordTypes/
└whatever.recordType-meta.xml

Looking into where this error is coming from, can you check that your metadata looks like
objects/
└ Something__c/
  └ Something__c.object-meta.xml
  └ recordTypes/
    └ whatever.recordType-meta.xml

this is how my project looks like as excatly mentioned by you

is Account the only object?  Might there be some object that has recordTypes but doesn't have an object-meta.xml, or some recordTypes not inside an object folder, or some files with the wrong extension?


[Improvement][API-Test] Init commit of adding api tests for resources controller

Purpose of the pull request

WIP

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14551 (78f6374) into dev (8020c15) will increase coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head 78f6374 differs from pull request most recent head 43e86f9. Consider uploading reports for the commit 43e86f9 to get more accurate results

@@            Coverage Diff            @@
##                dev   #14551   +/-   ##
=========================================
  Coverage     38.73%   38.73%
+ Complexity     4578     4576    -2
=========================================
  Files          1237     1237
  Lines         43537    43489   -48
  Branches       4823     4791   -32
=========================================
- Hits          16862    16845   -17
+ Misses        24804    24774   -30
+ Partials       1871     1870    -1

see 36 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Change the badger wallet logo to the geen BCH logo

Not sure if a custom badger logo is in the works or you plan on keeping the one which is currently used. But the green BCH logo, like the one used on coinbase, would look much better imo.

We'll consider it. TY


Unittests for documentation coverage

Similar to how Python's coverage.py utility to completeness of our unitests in evaluating each line of code, we propose to develop a set of custom unittests that will inspect the models and fields in our app and evaluate how fully they document themselves.

[x] Create a new subclass of Django unittests in our tests.py file
[ ] Add test methods on that class that evaluate each of the following and return a statistical report that looks and acts much like coverage.py

[ ] Every model should have a docstring that explains the definition of the model by testing if __doc__ exists on every model
[ ] Every model should have a UNIQUE_KEY definition that at least guesses its primary key combination
[ ] Every model should have a custom __unicode__ method that instructs Django how to print out an individual object
[ ] Every field should have a verbose_name attribute, even if is a repeat of the field name
[ ] Every field should have a help_text attribute with a more descriptive sentence explaining what it does
[ ] Every multiple choice field with coded values should have a django CHOICES crosswalk defined to decode the odd values that are stored in the database

[ ] "Unknown" values in the choices fields should be counted and surfaced somehow

[ ] That test should also generate and surface a list of models and fields that still need to be further documented
[ ] Generate a report card that can be published as part of our model documentation on ReadtheDocs and serve as a progress report on our work

Once this ticket is complete all of the undocumented things will obviously need to be worked through. In the mean time, I am going to close the hodge podge of tickets in that vein.

With the previous commit, I created a new Makefile command that will run only the documentation tests. My hope is that this can grow to become a tool of iterating to expand our documentation tests and reach the goals of this ticket.
$ make testdocs