Bayesmethod xval

Flexible beta now works from command line.  Example usage:
bayeschime  -p data/Downtown_parameters.csv -d data/Downtown_ts.csv -b flexible_beta -k 10
k is the spline dimension, and b is the functional form for beta.  If you want flexible beta, indicate as above.  Default is logistic.  The penalty parameter for beta is in the params file.  Note you need to add a "pen_beta" and a "beta_intercept" parameter.  The former should be gaussian mean-zero, and the latter should be something like 10 -- some region that is logistic(x) is very close to 1.
Still plenty to be done; see the running list in issue #61

Getting this error when I run the example usage:
Traceback (most recent call last):
  File "/Users/cchivers/anaconda2/envs/bayeschime/bin/bayeschime", line 11, in <module>
    load_entry_point('bayes-chime==0.1.0', 'console_scripts', 'bayeschime')()
  File "/Users/cchivers/proj/chime_sims/bayes_chime/normal/scripts/cli.py", line 302, in main
    {"hosp_min": 10, "vent_min": 1}, fit_kwargs
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/_extras.py", line 162, in empbayes_fit
    z = convert(_multiminex(z0buf, minfcn, **minargs).x)
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/_scipy.py", line 223, in __init__
    callback=analyzer, method='Nelder-Mead',
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/scipy/optimize/_minimize.py", line 588, in minimize
    return _minimize_neldermead(fun, x0, args, callback, **options)
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/scipy/optimize/optimize.py", line 585, in _minimize_neldermead
    fsim[k] = func(sim[k])
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/scipy/optimize/optimize.py", line 326, in function_wrapper
    return function(*(wrapper_args + args))
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/_extras.py", line 154, in minfcn
    fit = lsqfit.nonlinear_fit(**args)
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/__init__.py", line 681, in __init__
    p0, nf, self._chiv, tol=tol, maxit=maxit, **self.fitterargs
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/_scipy.py", line 160, in __init__
    **extra_args
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/scipy/optimize/_lsq/least_squares.py", line 835, in least_squares
    J0 = jac(x0, *args, **kwargs)
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/_scipy.py", line 150, in Dfun
    fx = f(_valder + x)
  File "_utilities.pyx", line 67, in lsqfit._utilities.chiv
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/lsqfit/__init__.py", line 1876, in flatfcn_ad
    ans = fcn(po) if x is False else fcn(x, po)
  File "/Users/cchivers/proj/chime_sims/bayes_chime/normal/models/base.py", line 181, in fit_fcn
    df = self.propagate_uncertainties(xx, pp)
  File "/Users/cchivers/proj/chime_sims/bayes_chime/normal/models/base.py", line 139, in propagate_uncertainties
    df = DataFrame(data=self._iterate_simulation(**pars)).set_index("date")
  File "/Users/cchivers/anaconda2/envs/bayeschime/lib/python3.7/site-packages/pandas/core/frame.py", line 445, in __init__
    data = list(data)
  File "/Users/cchivers/proj/chime_sims/bayes_chime/normal/models/base.py", line 161, in _iterate_simulation
    inp_pars = self.update_parameters(date, **pars)
  File "/Users/cchivers/proj/chime_sims/bayes_chime/normal/scripts/cli.py", line 153, in flexible_beta
    ppars["beta"] = kwargs["beta"] * (1-1/(1+np.exp(kwargs['beta_intercept'] + X@kwargs['TI_coef'])))
TypeError: ufunc 'matmul' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''

Update READ.me with your example usage for this PR.

Got it working. I get this output. Is this the expected behaviour (seems like a narrow CI)?

The width of CI bands depends on the size of the estimated data-errors (hosp and vent admissions), which are also quite narrow.
I believe this script uses the empirical Bayes criterium to estimate data uncertainties. Simplifying how it works, this criterium tries to optimize the probability that the model describes the data. If there are more model parameters, it might be easier to describe the data and thus this criterium suggests that the data errors are smaller. Thus this estimation process might be a potential source for overfitting.
If possible, it might be a good cross check to run the same analysis against data uncertainty estimations motivated through other means (these can be specified by file through the -y flag).

Great. I was able to run it with the -y flag and get reasonable results.


Added Office 365 CLI documentation

Based on the PowerShell implementation a version that contains all O365 CLI commands to easily manage site designs and site scripts from any device.
Category

[ ] Content fix
[x] New article

@andrewconnell yes there is such a page. I do not mind putting these changes in there as well, but that would require renaming the page to a broader term then is used now. I would suggest to rename site-design-powershell to site-design-management and merge both pages together. Please let me know if that approach sounds viable and if so decline this PR. I will do a new one with that change in it.

Hmmm... wasn't aware of that page. Maybe keeping a sperate page then so not to screw up existing links, rather adding a callout in the other page pointing to this one and vice versa?

@andrewconnell added a see also link on both pages,

LGTM... because it's a new article, need to let MSFT merge this one in...

Sorry for screw up, removed branch by accident.

thx @appieschot, getting things finally merged.


Add delete functionality for samples

Added delete functionality for issue #67. Used react-icons for trash icon for delete button. delete button is placed next to edit button.
Used the /api/v1/sqldelete/{id} API endpoint to perform the deletion.
Also added a confirmation prompt before deletion to prevent accidental removals using the confirmDialog function as well as some additional error handling.

I've made the requested changes, thanks for the feedback. Please review it when you can @sethumadhavan-k

Hi @sethumadhavan-k, I have adjusted as instructed. Sorry for the trouble

@zteezy19  let me check

Hi @sethumadhavan-k, I've changed the name of the confirmDailog function to confirmDialog to fix the typo, and also adjusted the usage of the function in the Samples.jsx. Please take a look thanks

@zteezy19 The parameter of the confirmDialog function is not an object. Please ensure it follows the example provided, and for now, don't change the function name.
example :
confirmDailog("Are you sure you want to delete this?", "", {deleteicon}, {cancelicon}, {confirmButtonText}, {deleteButtononClickFunction})

Hi @sethumadhavan-k , I think I've adjusted as requested.

@zteezy19  let me check this.

@zteezy19 getting  this error in frontend

Hi, I've fixed the API url typo.

@zteezy19 let check

@zteezy19 please update the sample delete  API url  /sqldelete/{id} also i am getting the same error

Hi, sorry, I did not commit the codes properly. The changes should be committed. so sorry for the newbie mistakes

@zteezy19 please join on our slack channel https://join.slack.com/t/theailounge/shared_invite/zt-2ogkrruyf-FPOHuPr5hdqXl34bDWjHjw, i will assist there


New hardware with minimal HID

Info
Hi team. I'm using Rascsi with vintage synths and samplers. The oled display is invaluable for when each scsi ID represents a HDD or CD containing samples.
What would take the project to the next level would be the use of a rotary encoder with push switch to allow the user to navigate through a basic menu structure allowing the user to change the mounded ISO image on an attached CD drive, the disk in a MO drive and so on. I'm sure this feature would be useful to other demographics too.
The hardware doesn't need much of a change, however, the current python for the oled would need a rethink.
Given that there is discussions around having the oled move from polling to subscription, i thought it a good time to raise my idea.

@hsiboy - thank you for the suggestion! Its definitely an option for control.
My 2 cents on things - the tiny OLED screen is going to really limit the user experience for editing things. It wouldn't be a big deal to upgrade to a larger OLED display.
I definitely agree that it wouldn't be much of a hardware change. RaSCSI eats up most of the available GPIO pins, but we could use some sort of I2C device to handle the rotary encoder.
What do you think about adding a 3-4" touch screen and creating a version of the web interface that is touch-optimized?

So I have cooked something up to prototype with in this direction.

Personally, I don't like the idea of a touchscreen due to the size. I'm kinda thinking along the lines of a 1U 19" studio rack bay for 4 separate rascsi devices. At least I find it useful to have choice and want to use all SCSI IDs for each sampler. Though, I will probably switch to a slightly bigger 1.3" 128x64 I2C display once it arrives.

@bzeiss I've done something very similar, but only two push buttons, because my rotary encoder also has a button.
I've got a larger LCD display, and I've used one of those cheap Chinese i2c display interface adapters. The hardware works, but I need to branch so I can add the LCD lib.
For me, I don't want to use the web interface every time I want to mount a new sample ISO and the RaSCSI won't be located at arms length, so a bigger display is a must.

@hsiboy I'm not sure yet about the acutal number of buttons. I was thinking something like two buttons for recalling configurations and one shutdown button. Or maybe one back button and one shutdown button. I want to use the rotary encoder button (my encoder has one as well) mainly for navigating the menu on the display. I think the display resolution will be good enough, it kind of works fine for me on the gotek drives. I rather don't want to waste two units in the rack, I have too few of them.

I love this!! It would be awesome to make a simple control board (like you prototyped) that could be installed apart from the rascsi.

Would something like this be interesting? (very... very.. very... rough concept)

Yes, absolutely. This is essentially what I was going for. My intuitive right-handed biased reaction would be to want to rotary encoder to the right of the display though ;-) I'm curious about that IC. Are you thinking about separating the front panel from the I2C bus with its own atmega168 or so?

By the way, for the stuff I wanted to toy around with, I also wanted to do something about the power management. It would be cool to have proper startup and soft shutdown switches/buttons or something like that. It's probably step two after everything else, but still, it probably makes sense to think about this as well when designing a front panel.

Here's what I'm thinking so far.... If you're using a RaSCSI, you'd use the 5 pin connector on the left. But, I also wanted this to work generically on any Raspberry Pi. For the RaSCSI use case, the 40 pin header probably won't be populated.

Ditto on the power management concept. I'd love to have a battery connector so that we could have a safe shutdown option. But, right now, with the chip shortage, I haven't been able to find any battery controllers that will meet our needs. I'm not an Electrical guru, so that's going to take more work (If I do the design, anyway) :]
The IC on this is a I2C I/O Expander, similar to the MCP23017 that @bzeiss is using (but a little less expensive and seems to be easier to find)

Rotary Encoder: https://www.mouser.com/ProductDetail/Alps-Alpine/EC11E15244B2?qs=m0BA540hBPfDpUEkDmFV5A%3D%3D
Discrete expander: https://www.mouser.com/ProductDetail/NXP/PCA9554APW118?qs=LOCUfHb8d9t6Q6oURZSRTg%3D%3D
OLED - (Should work with most?) https://smile.amazon.com/Self-Luminous-Display-Compatible-Arduino-Raspberry/dp/B09JWLDK9F/ref=sr_1_4?keywords=i2c+oled&qid=1639278355&sr=8-4

This is looking really nice now! I like the idea to keep it universal with the gpio pins. This is something I would happily use :-)

About the power. One circuit that I came across and that looked pretty simple and sweet with a small footprint is this one:
https://othermod.com/raspberry-pi-soft-onoff-circuit/
It's something I want to test out some day.

Hey @akuker your design is looking very familiar... https://buildalightshow.com/pixel-controllers/117-fpp-pi-control-cape-pioled.html

About the power. One circuit that I came across and that looked pretty simple and sweet with a small footprint is this one:
https://othermod.com/raspberry-pi-soft-onoff-circuit/
It's something I want to test out some day.

That looks very promising! However, it relies on the "TXD" pin, which is also used as the D4 data line by RaSCSI.
I think we could figure out a way to use a spare discrete on the I/O expander for the processor to flag when its ready to shut down. We could put a 20 second delay on it using a R/C circuit.

Teaser:
https://youtu.be/lVSJcFynzxc

Teaser:
https://youtu.be/lVSJcFynzxc

@hsiboy What kind of lcd did you want to use or have in mind? I'll probably start to do some more abstraction over screen libs and sizes pretty soon, starting with the 128x32 oled and a 2.x" oled I think I have somewhere around.

@hsiboy What kind of lcd did you want to use or have in mind? I'll probably start to do some more abstraction over screen libs and sizes pretty soon, starting with the 128x32 oled and a 2.x" oled I think I have somewhere around.

Hey @bzeiss I was going to use a 4x20 alphanumeric LCD (or its OLED equivalent), I2C based.
The LCDs are cheap and plentiful and easily readable from a distance.
Happy New Year btw.

@hsiboy happy new year to you as well. Ok, I'll order one of those for testing as well just in case.

Hey @bzeiss I'm way behind on the changes you've been making, because i took a slight deviation.
I woke up one morning remembering something i had used in my professional work, some time ago LCDProc https://github.com/lcdproc/lcdproc
LCDProc uses the idea of a server client, so the LCD display can be physically located somewhere else and updated over TCP/IP. Thinking about my setup, having the RaSCSI in the rack, close to the gear, with a small remote display, located near the keyboard/workstation for control and information.
It was then i remembered that I had an old Matrix Orbital display that was intended for use in a 5.25" drive bay. Its a graphics LCD with some LEDs, some push buttons etc in a neat package. It was available in USB, Serial, I2C and is fully supported by LCDProc. LCDProc supports a lot of displays and interfaces.
LCDProc was supported by a number of softwares, through the use of "plugins", so I started thinking about a plugin for RaSCSI, and thats the rabbit hole i've been down, with a couple of bald Yaks for company.
Your thoughts?

I'm not exactly sure about the use case for that. If you use RASCSI in a 19" rack with a bunch of samplers, you probably won't to put your Raspberry Pi into that rack as well and control it directly from the rack. That's what I'm aiming at. In this case, there is no advantage in decoupling display from the Raspberry Pi over tcp/ip. If you have your RASCSI on a desk with your old Mac and want a hardware interface, you also have the Raspberry Pi+RASCSI standing right next to your Mac and thus within the reach of your hand. Personally, I think that the tcp/ip solution would make sense if you really have the control board physically somewhere else than the RASCSI. For that use case, you might just as well use the Android app. So I can't think of a convincing use case to justify the effort (for myself that is) right now though.
That said, there are some first steps towards and abstraction already in there. So it is probably possible with some more refactoring effort to support multiple ways to draw the menu. I'm not sure whether I'm motivated enough to do this though. I have more or less all features in place for the first pull request. It's mostly linting+fixing, documentation and adaptation of easyinstall.sh what is left now.

For that use case, you might just as well use the Android app.
Or the web app ;-)

FYI: @bzeiss , my boards are still stuck in limbo at JLCPCB. I'm assuming the lunar new year is slowing them down. If the status is to be believed, I should get them mid-Feb.

@akuker My board also hasn't been sent out yet, but I did add a few other ones which current delay the shipping. I guess I won't have them before mid-Feb as well.

This is done and has been released into the wild!
https://www.tindie.com/products/landogriffin/raspberry-pi-oled-controler-board/?pt=ac_prod_search

Dumb question. How do you get this control board to work? I built the hardware and ran the easyinstall script to setup the control board, but nothing shows up on the display. I used Adafruit's test scripts to verify the LCD works, but I can't get anything else to show up on it. I'm running the latest PiSCSI image from November.

@jzmacdaddy There are sometimes problems with fetching of the python packages if I recall correctly. Maybe try to run it manually. In the python/ctrlboard directory, there is a README.md with instructions. Maybe the problem is more visible when run manually. Make sure that the systemd ctrlboard service is stopped before you try this.

@jzmacdaddy In addition, there is a bug in the Nov 2023 release that prevents the Control Board from working. It has been fixed in the development code. https://github.com/PiSCSI/piscsi/pull/1394
You can either wait for the next release, or build the latest code by yourself. Please let us know if you want to try the latter!

@jzmacdaddy In addition, there is a bug in the Nov 2023 release that prevents the Control Board from working. It has been fixed in the development code. #1394
You can either wait for the next release, or build the latest code by yourself. Please let us know if you want to try the latter!

Thanks. I assume it works in the release prior to November? If so, I'll give that a shot.

@jzmacdaddy I don't recommend using an earlier release, because of Python dependency hell. Neither of the Python clients (in particular the Web UI) will work out of the box, forcing you to have to go in and manually fix the dependencies. IMHO it will be less effort to roll forward to the latest development code.
To make a long story short, in all previous piscsi releases we had loose Python dependency mapping. And when a key Python library released a major breaking change late last year it completely broke our dependency tree. So no prior piscsi release version will work fully out of the box anymore. Lesson learned to do very explicit Python dependency mapping...

I honestly just want to verify my control board is working. Are there instructions on how to roll forward with the latest code for a rookie like me?


Add more margin to the last item in the highlighted guidance panel

In the screenshot I've added 0.75rem

This is already fixed.


cmakedoc.cmake_regexer purpose strings should be enums

Using plain strings (such as "block comment end") for processing is fragile, especially if these strings are not constants. Retyping these string literals everywhere will eventually lead to mistypes and unmaintainable code. Using enums allow greater flexibility, quick and easy comparisons, and easy extension for more purposes (if needed).

Honestly I'd probably throw away all the code I wrote in favor of using an actual parser/lexer, which fixes this problem :slightly_smiling_face:


[Pie] missing props size

Thank you for using react native pure chart!
Would you explain more specifically?

in file index folder pure chart
component pie chart
size={this.props.height}
...

Sorry for late, it is fixed in recent version. You can use it like below:
<PureChart typ='pie' size={50} ....


Site not loading

Often when I open the site and always when I switch between "Home", "To links" and "About" the sites crashes, or starts loading very slowly.

I believe this has to do something with the domain registration or the hosting service. Everything should be fine now.


Add FB Broadcast Messages API

Hello,
This PR add the new FB Broadcast API to send a message to many recipients.
Enjoy :alien:

Thank you @jonchurch for the review 👍


Android development with kotlin

Description 📜
Added documentation for CardView and MaterialCardView in Android (Kotlin)
Fixes  #1448

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Android Dev (Kotlin)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

https://github.com/amaan118921/Android-Kotlin-09.18-CardView-and-MaterialCardView-in-Android-Kotlin-1448

please push your pr again into Android_Development_With_Kotlin branch.


Add anonymous-credentials review to wasabi/research-club

This PR adds anonymous-credentials transcript review to the wasabi/research-club directory.

Hey! @Johnycrown Thank you for coming onboard and making a contribution to this project. Your efforts are sincerely appreciated.
When reviewing transcripts from youtube videos, please make an effort to check the video description on youtube, The information provided there could help make your work easier .
Most of the information you need on style conventions can be found here. it would help you understand the corrections made and what is expected.
Since you are a new reviewer, I invite you to join our Bitcoin Dev Project discord. This platform will allow you to ask questions, connect with other reviewers, get notified about new transcripts for review, and explore ongoing developments in the Bitcoin Dev Project.

Also review this Fixup commit that I made to help you improve


skymask data type

Have:
BITPIX  =                  -32 / number of bits per data pixel
Want:
BITPIX  =                    8 / number of bits per data pixel
(as in bad pixel masks)

fixed by dd3989e4475ef5e0592331fc187fe98670d83e70


Package causes a new UWP app to fail Windows App Certification for Deployment to Microsoft Store

Describe the bug
If you add the latest version of the NuGet package (1.1.0) to a blank UWP app, the app will fail the Windows App Certification with the following error and not be able to be deployed to the Microsoft Store. The failure relates to sni.dll failing the Binary analyzer Windows Security features test.
Windows security features test

FAILED
Binary analyzer
Error Found: The binary analyzer test detected the following errors:
File C:\Program Files\WindowsApps\(PackageName)\sni.dll has failed the AppContainerCheck check.
Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.
How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:
Fixing Binary Analyzer Errors

PASSED
Banned file analyzer

PASSED
Private code signing

Supported API test

FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API _mbschr in api-ms-win-crt-multibyte-l1-1-0.dll is not supported for this application type. sni.dll calls this API.
API _mbsnbicmp_l in api-ms-win-crt-multibyte-l1-1-0.dll is not supported for this application type. sni.dll calls this API.
API _mbsspn in api-ms-win-crt-multibyte-l1-1-0.dll is not supported for this application type. sni.dll calls this API.
API IsTokenRestricted in advapi32.dll is not supported for this application type. sni.dll calls this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable.

To reproduce

Create a new, blank UWP app (File->New->Project->Blank App (Universal Windows))
Right click the project -> Publish -> Create app packages -> Sideloading -> Yes, select a certificate: Create -> Next -> Next -> Choose an installer location -> Create -> Copy and Close (once it finishes running)
Launch the Windows App Cert Kit (just search for app in Windows 10)
Choose Validate Store App -> Browse for the app you want to validate -> Select the .msixbundle created in Step 2. -> Next -> leave all Selected, Next
View the report once finished (should pass for everything except for default logos)
Right click the project -> Manage NuGet Packages -> search for Microsoft.Data.SqlClient and install the latest version (v1.1.0 as of now)
Repeat steps 2-5, report will show the failure documented above.

Expected behavior
Package should not prevent UWP apps from being deployed to store, as this will prevent production usage.
Further technical details
Microsoft.Data.SqlClient version: 1.1.0
.NET target: Universal Windows Target Version 1903
SQL Server version: SQL Server 2017
Operating system: Windows 10 Version 1909
Additional context
This seems to have been an issue at one point with the System.Data.SqlClient package as well. Perhaps the same fix could be applied to this package?
https://social.msdn.microsoft.com/Forums/en-US/5bcc17fa-5184-4fab-8ff2-cbee229a12a2/snidll-has-failed-the-appcontainercheck-check?forum=wpsubmit
Here is some documentation on fixing similar failures of this test with another dll (with the linker options /dynamicbase /nxcompat /appcontainer)
https://github.com/grpc/grpc/issues/18188
Specifically, step 3 of this comment in the issue thread: https://github.com/grpc/grpc/issues/18188#issuecomment-544848727

Hi @bolyb
I believe you're suggesting changes in SNI.dll source which loads from runtime.native.System.Data.SqlClient.sni when targeting UWP Apps.
Currently there are some hiccups with this library, we'll look into it if feasible and get back to you.

Hi @bolyb
Could you try with Microsoft.Data.SqlClient v2.0.0 and let us know if that works for you since the SNI DLLs are now different.
Alternatively, we also enabled switching native SNI to Managed implementation to avoid loading native DLL. You can set AppContext switch to Enable Managed SNI on Windows.

As mentioned in https://github.com/dotnet/SqlClient/issues/703#issuecomment-677897900, the issue will be resolved by enabling Managed Networking on Windows for UWP apps.
It's not enabled by default, but necessary for UWP applications.

Hi @cheenamalhotra and @David-Engel
Thank you for your time investigating this issue, it is much appreciated.
I've just now had the opportunity to circle back on this. I've attempted to use Microsoft.Data.SqlClient 2.0.0, and 2.1.1, both with and without enabling Managed Networking on Windows for UWP apps. I have tried enabling this by adding the line AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.UseManagedNetworkingOnWindows", true); in App.xaml.cs as suggested in both the constructor and OnLaunched methods. Unfortunately in all cases, when following the reproduction steps outlined in the original bug report reproduction steps, the app still fails the Windows App Certification Kit with the same error.
FAILED Binary analyzer Error Found: The binary analyzer test detected the following errors: File C:\Program Files\WindowsApps\35d4df60-94b9-465f-a5bc-3d8bbd4e5f1e_<IP_ADDRESS>_x64__dt8z0k56dgxnc\Microsoft.Data.SqlClient.SNI.dll has failed the AppContainerCheck check.
In summary, there doesn't appear to have been any change on this original issue, what do you suggest as far as next steps to try?

@bolyb @cheenamalhotra @David-Engel I too am circling back around this as I have run into the same thing again as well, I updated #703 mentioned above back in December. Right now, we cannot ship the newest versions of our Microsoft Windows application due to this issue.

Hi @bolyb @wjvii
I think the error you're seeing is mainly due to SNI dependency that continues to exist even if you enable Managed SNI and do not use that DLL at all. I think the only solution that would work is when you we completely move away from Native SNI to managed for UAP targets. But because Microsoft.Data.SqlClient is now an external component and not built same way as System.Data.SqlClient was built in the .NET Core SDK, we have had challenges in the past when building for UAP targets.
I'll reopen this issue again, and we can revisit options that we can do here.

@cheenamalhotra is there any chance that you can work with the Microsoft Store team and have them allow this Microsoft SNI dll?

Remove the SNI files during build?

Is there any chance that you can work with the Microsoft Store team and have them allow this Microsoft SNI dll?

@wjvii The purpose of UWP is to provide a uniform set of APIs that apps can use, which are supported on all the devices that Windows 10 runs on. The Microsoft.Data.SqlClient.SNI.dll is not compiled specifically to use only the UWP core APIs, so there isn't any way the store can simply "allow" it because, without changing it, it likely would not work across all devices.
As ErikEJ suggested, try deleting the SNI files from your build/publish folder (and maybe remove any references to it from your dep.json file, depending on your publish config), assuming you have set the switch to Enable Managed SNI on Windows. Those SNI dlls are not actually used when that switch is set.

Hi @David-Engel
Thank you for your suggestions, I appreciate the insight. So far I have tried adding the following as both Pre and Post Build event commands:

This successfully removes the Microsoft.Data.SqlClient.SNI.dll file from the bin directories, but unfortunately the application built this way is still failing the Windows App Certification Kit with the same error relating to this dll. This makes me think that the file is still making it's way into both the .msix and .msixbundle (I tested both with the same result).
I'm open to any suggestions as far as other methods to prevent the Microsoft.Data.SqlClient.SNI.dll from making it into the final .msix/.msixbundle in order to pass the Windows App Certification Kit. We publish our UWP app to our organization via the Microsoft Store for Business, and cannot submit the installer without passing these checks.

Same issue here, when we package the app it still includes the dlls and fails to pass certification in the Microsoft Store.

@bolyb @wjvii
Make sure you search and delete any occurrences of the SNI file recursively. In my test, there were 4 or them in runtime subfolders in my build folder for the different platforms that SNI supports. But this may vary depending on your project targets. Inspect the output folders manually to be sure. I also found I had to edit my *.deps.json file to remove references to the dependency in my .NET Core project.

Hi @David-Engel
Thank you again for your suggestions. After further troubleshooting I was able to get it to successfully pass the Binary analyzer check on my local machine. I first had to add the following lines to my project's post build script to delete all files recursively as you suggested:
cd $(TargetDir)
DEL /F/Q/S Microsoft.Data.SqlClient.SNI.dll

Similar to your suggestions about the *.deps.json file for a .NET Core project, I then also had to remove all references (about 50 in my case) to Microsoft.Data.SqlClient.SNI.dll in the project.assets.json file located in the obj folder of my UWP App project. Doing this right before publishing the app packages for the project I was able to get a package created which successfully passes the Binary analyzer check. It's worth noting that a Rebuild All on the solution would trigger a NuGet Package Restore, which re inserts the ~50 references to the JSON file and then it will not pass or build successfully again until they are deleted.

We are also having issues yet again with "Microsoft.Data.SqlClient.SNI.DLL".

We are referencing "Microsoft.Data.SqlClient" 2.1.2 directly.

We have switched the AppContext.

We are removing all SNI files from the files system.
We are editing the "project.assets.json" to remove all references to "Microsoft.Data.SqlClient.SNI".
However it still fails. I have now spent days on this... What else can I do?
We are building and bundling in one "msbuild" but I think we have to. I don't think I can build with one Azure Dev Ops Visual Studio Build that will build and one that bundles. This way we could build, then clean, then bundle... I'm going to try this next because I literally have no ideas on what to do to get our app in the store.
What frustrates me the most is if this was a WPF app it would have just worked. I think the best thing for us to do is walk away from UWP and just use WPF.

Oh and another interesting piece. A previous build which use the exact same references is working and in the store.

OK, I think I know how this was possible. This is only what I think happened. Our application was private for some time. Literally until the last release. I release the current version as private. Once we tested it and such I flipped our application to public. I'm guessing the app was just transition from private to public?
I'm not sure if they're different requirements but this is my guess...

@bolyb How did you bundle your app? In VS or in ADO (Azure Dev Ops).
I have tried what you said (remove files and edit the json). The files get deleted and edit but AFTER the bundling process in ADO. I'm guessing you did a build locally, editing the files locally, then did a local "publish" to bundle it?

Hi @3AM-Innovations
Yes, I built the project locally in VS and then did a local "Publish" -> "Create App Packages..." to bundle it exactly like in the screenshot you posted.
This ended up being such a problem for us that we stopped using the Microsoft Store for many of our apps. Even though we were publishing our application as a line of business application, we would still have to pass the store checks which became very limiting.
We now deploy our UWP application using App Installer with automatic updates, which offers a far better user experience than the older sideloading methods (no powershell visible by the user, and includes the ability to automatically update similar to the Microsoft Store). We publish the App Installer package to a company fileshare (or website) instead of to the Microsoft store, and users install the applications from there (more like traditional MSI with WPF). We had to jump through a few hoops to do this, acquiring a Code Signing Cert from Sectigo and publishing our app with this cert (which requires a hardware dongle that we share between developers on the company network using USB over IP).
Here's a link to some more information about App Installer if you are interested in going that route: https://docs.microsoft.com/en-us/archive/blogs/appconsult/handling-auto-updates-for-sideloaded-uwp-and-desktop-bridge-apps

For me what worked is using PowerShell script to remove Microsoft.Data.SqlClient.SNI references in project.assets.json from the obj directory after restore, before build. I am using build pipeline to create the store upload package so I needed something automated. The PowerShell script:
function Remove-Property {
  param(
    [Parameter(Mandatory, ValueFromPipeline, Position = 0)]
    [object] $InputObject,
    [Parameter(Mandatory, Position = 1)]
    [string] $NamePattern
  )
  process {
    foreach ($el in $InputObject) {
      foreach ($propName in $el.psobject.Properties.Name) {
        if ($propName -like $NamePattern) {
          $el.psobject.Properties.Remove($propName)
        }
        else {
          $null = Remove-Property -InputObject $el.$propName -NamePattern $NamePattern
        }
      }
    }
    $InputObject
  }
}

$fileContent = Get-Content ".\obj\project.assets.json" -Raw | ConvertFrom-Json
$fileContent = Remove-Property -InputObject $fileContent -NamePattern "*Microsoft.Data.SqlClient.SNI*"
$fileContent | ConvertTo-Json -Depth 100 | Out-File ".\obj\project.assets.json" -Force

In my case the obj and bin folders do not exist. Restore target is run using msbuild, then the script above is run from the UWP project folder. Then I run msbuild with appropriate parameters to create store upload package, and it passes certification.
The above script creates a world where Microsoft.Data.SqlClient package does not depend on SNI package, and it removes any references to the SNI package from targets/libraries portions of json file.
(sigh). Sad this was needed, but hope it helps someone.

@dahovey Thank you for your comment. I am going to try your script because mine just doesn't seem to work...
I'm trying to get the ADO build to work but cannot seem to find the correct "target" to make it happen at the correct time.
<Target Name="Cleanup 1" BeforeTargets="CoreCompile">
    <Message Importance="High" Text="Cleaning up SqlClient SNI files so Windows Store will accept the release..." />
    <Exec Command="powershell -NonInteractive -Command "& '$(ProjectDir)\Invoke-PostBuild.ps1' -Path \"$(ProjectDir)\""" WorkingDirectory="$(ProjectDir)" />
  </Target>

I've have tried many many many different "BeforeTargets" and "AfterTargets"...
However this is still not working? Now my build / package step is a single pipeline step of "Visual Studio Build" using the following arguments
/p:AppxBundlePlatforms="x86|ARM64" /p:AppxBundle=Always  /p:UapAppxPackageBuildMode=StoreUpload  /p:AppxPackageSigningEnabled=true /p:PackageCertificateThumbprint="aoeuaoeu"  /p:PackageCertificateKeyFile="$(signingCert.secureFilePath)" /p:PackageCertificatePassword="$(signingCert.password)"

OK, we finally got a build from ADO to pass. Here is the final working  for your CSPROJ file.
<Target Name="Cleanup SqlClient SNI" AfterTargets="PrepareForBuild">
    <Message Importance="High" Text="Cleaning up SqlClient SNI files so Windows Store will accept the release..." />
    <Exec Command="powershell -NonInteractive -Command "& '$(ProjectDir)\Invoke-PostBuild.ps1' -Path \"$(ProjectDir)\""" WorkingDirectory="$(ProjectDir)" />
</Target>

Closing issue as above options are available to mitigate SNI.dll dependency problems during deployment.


wait_for_replicas - cherrypick from main

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!verified


add lookup to NewFunction

I needed this. Giving back in case anybody else does.

Thank you for this. Was just looking for the lookup function in the documentation but was surprised it wasn't included.

@mottykohn, merged this as part of https://github.com/Intacct/intacct-sdk-net/pull/174...... Thank you for your contribution :)


Fixes issue #15

The StashEvent listener will catch all requests for keys at user, repo and project level and only rely on the user/group to approve or reject.  This will allow bamboo to create system keys at the repo level.

Previously the removed event listeners blocked any attempt to add a key based user permission to the repo.
The remaining method still blocks any keys not created by the right users.  I was worried before that this would cause inconstancy. But testing showed desired result.


Feature Request: Option To Select File Encoding and Option to select Line Endings (Unix or Windows)

File encoding selection ability like ANSI, UTF-8, UTF-16 etc while saving would be great. If big/little endian can also be selected, even better.

Option to choose which line ending character to use CR/LF or CR. That will allow to preserve the file structure.

@bajrangCoder, is the encoding and line ending character type automatically inferred from the file when opening it? As an example, when I open a CRLF file, does ACode automatically select the correct types?

Hmm(except some cases)

https://github.com/deadlyjack/Acode/issues/309#issuecomment-2323262982

@bajrangCoder, can you elaborate?


disable tax

Hi,
I need to disable the default tax rate ie 21%. I don't want any tax. Cart total is my final price.

Hi,
You need to publish the cart config to your laravel app..
php artisan vendor:publish
and select the tag with config.
Therefore, you will get the cart.php in your config folder, there you can set the tax value.

php artisan vendor:publish --provider="Gloudemans\Shoppingcart\ShoppingcartServiceProvider" --tag="config"
Then you have a copy of the config file in /config/cart.php which you can edit!!
That's all there is to it :)


Idea: abstract url generator or use absolute URLs

https://github.com/stefandoorn/sitemap-plugin/blob/3858e2cbbcb2397936168a5619d7a9592a89553b/src/Provider/ProductUrlProvider.php#L143-L146
Using the UrlGeneratorInterface::ABSOLUTE_URL option will ensure the right protocol (http or https) is used.
An alternative might be to abstract the code to generate an URL to a generator class that users could overwrite/replace.

Seems to have been an issue on my end, closed!


Job spec as IPLD document

We'd like to express the job spec as an IPLD document so that we can integrate better with the Protocol Labs ecosystem. This is a breaking API change so better do it sooner than later.

@lukemarsden Ah, is this what you mean by caching for free? If we hash the job spec and use the hash as an ID then job specs will get cached by the IPFS node automatically.

pretty much yeah: basically, that the results will be cached by the bacalhau network.
User A submits Job with hash a1b2bc3
User A gets results after some time
User B submits same job with hash a1b2c3
User B instantly gets results because job has already been calculated (and previous results are still pinned to IPFS)
This depends on y=f(x) being deterministic for all jobs f, so hash(y), hash(f) and hash(x) are all constant


New package: AbstractDatasets v0.1.0

Registering package: AbstractDatasets
Repository: https://github.com/JuliaGeo/AbstractDatasets.jl
Created by: @Alexander-Barth
Version: v0.1.0
Commit: e51cd870f9365dc2d2222db4197f90338c340e16
Reviewed by: @Alexander-Barth
Reference: https://github.com/JuliaGeo/AbstractDatasets.jl/commit/e51cd870f9365dc2d2222db4197f90338c340e16#commitcomment-103573882
Description: AbstractDatasets is a module that defines types common to NetCDF and GRIB data

Name is too general

There are quite a few packages with quite general names:
AbstractNumbers
AbstractTensors
AbstractTrees
AbstractOperators
AbstractInstances
...

this is Geo specific no?

The NetCDF format is indeed widely used in geosciences, but is a container format like XML or JSON (but optimized for multidimensional arrays). NetCDF is closely related to HDF5 which has many applications beyond geosciences (e.g. in keras).  AbstractDatasets would be a collection of named multi-dimensional arrays with a list of metadata (like a Dict{String,Any}). AbstractDatasets would not require that the arrays are geo-referenced for example or that the arrays represent parameters related to the earth. There would not be a problem to store for example the MNIST dataset from Machine learning (a series of photos of  hand-written digits) in such an AbstractDatasets or a movie clip as a 4D array (color / x / y / time). Another example would be an audio file where the data arrays is the sound data and the metadata are the typical information, like artist and genre.
Initially we focus on  NetCDF and GRIB data, but it would not be complicated to treat HDF5 files also as AbstractDatasets or other formats.

AbstractGeoData?

The data does not have to be georeferenced or related to geoscience.

I see, since everything seems to be related to Common Data Model maybe name around that?

OK, I will try to register CommonDataModel.jl (or somthing like that), hoping that it does not generate confusion too.


AQCU-929: add rating shifts and rating shift comment table to uvhydro

Coverage decreased (-0.3%) to 98.633% when pulling f9b25f04083157fc3c1ba8c21b606ca9a4d085ad on mhines-usgs:AQCU-929 into ec48e908b556a6c1cb9577ef5aa81b093c8945d2 on USGS-R:master.

Coverage decreased (-0.4%) to 98.566% when pulling 7b126536e0226670cb0bf67d86781e4924182a5e on mhines-usgs:AQCU-929 into 7227b97cf8bdc293a7499694856738eb33b216e2 on USGS-R:master.

I realize I should add tests here too, but waiting on other PR feedback.

Thanks! @zmoore-usgs

Coverage decreased (-0.4%) to 98.567% when pulling e5934fe859f0ee55bd401759a96b8639d28c68cb on mhines-usgs:AQCU-929 into cdadec1b08168ca34861ca857e832fbe59b22f38 on USGS-R:master.

Coverage decreased (-0.4%) to 98.567% when pulling 4e332420f10b3787f442a71cebb36b903a0d68ad on mhines-usgs:AQCU-929 into cdadec1b08168ca34861ca857e832fbe59b22f38 on USGS-R:master.

Coverage decreased (-0.5%) to 98.486% when pulling 375e6822afc299d87b4ebf9bef4849724fbe80a3 on mhines-usgs:AQCU-929 into cdadec1b08168ca34861ca857e832fbe59b22f38 on USGS-R:master.

Coverage decreased (-0.4%) to 98.486% when pulling 95310d79d9a9b479d872dbe704a16341bbaa69da on mhines-usgs:AQCU-929 into 4a05a8213fae9225ec9963eba4495924c372bfd0 on USGS-R:master.


A few intel macs appear to be in bad shape

From https://chromium-swarm.appspot.com/bot?id=build806-m9

XCode installs are failing due to data corruption as in:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733087603218910657/+/u/install_xcode/install_xcode_from_cipd/stdout
There are other failure modes as well. I suspect a bad disk or bad memory. The automatic reboots on task failure don't seem to be helping.
I put up this CL to remove it from the prod pool, but I'm wondering if this is the right thing to do? https://chrome-internal-review.googlesource.com/c/infradata/config/+/7775927
cc @christopherfujino I'm wondering if bad machines like this are the underlying cause of https://github.com/flutter/flutter/issues/156614 ?

808 and 812 also have an abnormally high job failure rate:

builder
red
purple
total
rate

build806-m9
26
10
90
40.0%

build808-m9
13
4
90
18.9%

build812-m9
13
1
90
15.6%

I'm going to update my CL to remove all three, and then audit the try pool as well.

Filed internal https://b/376081455 to investigate the bots.

Based on the fact that many of the task failures are due to a failure to install Xcode, my suspicion is that we should be following the flow to delete the caches on the machine before requesting that the machines be re-imaged, or suspecting that the hardware is bad: go/flutter-luci-playbook under "Delete corrupted Mac caches".

@jmagman after chatting with the LUCI team, it sounds like caches can be corrupted if we have bots switching back and forth between Xcode versions. It looks like we are still on Xcode 15, but some machines have Xcode 16 on them. Do you know where the Xcode 16 installs are coming from?

In the last 30 days, I count 199 builds using version: 16b40

Given how many Mac subbuilds happen on a single engine PR (see https://github.com/flutter/engine/pull/55053 related builds), then add in framework and packages and maybe me pushing ~2x per PR and re-running flakes, seems low if anything.

They're all presubmit builds between November 5 and November 8. I'm not gonna click through to 199 builds, but I'd bet they're all for your PR.
So at least we know how our bots got in this state.

I wonder why clearing the cache (even if they are shared) work when corruption is detected? https://flutter-review.googlesource.com/c/recipes/+/52421

I am focused on this presently.

I am still working on fixing this permanently. In the interim, weekly going in and clearing the Xcode cache of the 10 worst offending bots appears to be mitigating the issue.


Feature/settings validation

This PR fixes #51 by adding support for a custom handler to be called whenever settings are updated.
Note: Currently, if a new setting is rejected, it still persists in the cached settings.

@jordens Would you mind taking a look at the implementation here for some thoughts? I'm trying to answer the following questions:

Should settings requests be rejectable?
If so, what should miniconf do on rejection? (e.g. restore settings, republish previous values, more?)


[Physics] Make CharacterComponent.Gravity a Vector3 instead of a float

(Closes #170 )
This allows the user to configure all three dimensions in CharacterComponent.Gravity rather than assuming gravity is always on the Z plane.
Also some miscellaneous comment updates to clear up some underexplained properties in the documentation.
(ignore all these merges, I'm bad at Git haha)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Given the test case @Kryptos-FR gave me in Gitter passed with flying colors, is this good to merge?

@xen2 when we change assets (breaking change) what is our policy regarding the version number? Should we increase the minor or major one? In that case we might want to wait for more changes or create a "future" branch to differentiate bug fixes and new features.

@Kryptos-FR good question.
Contrary to before, we should now technically be fine to have asset changes for minor upgrades since we upgrade project dependencies to Xenko even for minor releases.
Still, I am not decided on whether to allow such changes in minor release (bump to 3.0.1.x? or bump to 3.1.x same as before?)

@DW01 yes, PR looks good to me. Just need to figure out the last point @Kryptos-FR brought up, but that's on my side.

@xen2 @Kryptos-FR No problem, it's best that gets figured out for future changes much larger than this anyway.

(ignore all these merges, I'm bad at Git haha)

You should squash all of these commits together into one. Clean history is important for Git workflow.
Via GitKraken: Ctrl-Click commits, then right-click, and click "Squash",
Via Git in the terminal: git rebase -i HEAD~10 and change "pick" to "fixup" or just "f". Replace 10 with the number of commits you're trying to squash.

@aaronfranke not necessary, github has an option to squash before merging PR

Did a few minor tweaks in your branch.
Merged, thanks!


Zoom false-positive fix for #34.

Increasing bait dimensions fixes the issue, and as bait is placed off screen this shouldn't impact usability

Indeed, very good point, can you repeat the same pull request, but with 10px?
Because 3px seems still a little small.
Thank you.

Sure, done.


Live stream freezes after a few seconds

Here is my example using videojs-contrib-dash - v2.6.0 - 2016-12-12:
http://codepen.io/terrafox/pen/a7b707e8ac08255b29beb282562b4963
The LIVE stream freezes after about 30 seconds.
Using the DASH reference player 2.3.0,  it works no problem.. for hours.
http://codepen.io/terrafox/pen/47a780d3698f49fc304a07d9d11c276d

Seems this is the same issue:
#https://github.com/videojs/videojs-contrib-dash/issues/81
#https://github.com/videojs/videojs-contrib-dash/issues/109
#https://github.com/videojs/videojs-contrib-dash/issues/35

We have the same issue. After few second the Live Dash are stoped and the console show:
dash.all.min.js:3 [63936] ThroughputRule requesting switch to index:  0 type:  audio Average throughput 591248 kbps  dash.all.min.js:3 [63937] AbrController (audio) stay on 0/0 (buffer: 2.818)  dash.all.min.js:3 [63938] Getting the request for audio time : 20433.455022222224  dash.all.min.js:3 [63939] Index for audio time 20433.455022222224 is 299  dash.all.min.js:3 [63939] SegmentTimeline: 20427.41768888889 /<PHONE_NUMBER>  dash.all.min.js:3 [63939] Getting the next request at index: 300  dash.all.min.js:3 [64081] AbrController (video) stay on 0/3 (buffer: 0.106)  dash.all.min.js:3 [64082] Getting the request for video time : 20430.74302222222  dash.all.min.js:3 [64082] Index for video time 20430.74302222222 is 180  dash.all.min.js:3 [64082] SegmentTimeline: 20420.74302222222 /<PHONE_NUMBER>  dash.all.min.js:3 [64082] Getting the next request at index: 181  dash.all.min.js:3 [64440] ThroughputRule requesting switch to index:  0 type:  audio Average throughput 591248 kbps  dash.all.min.js:3 [64440] AbrController (audio) stay on 0/0 (buffer: 2.818)  dash.all.min.js:3 [64440] Getting the request for audio time : 20433.455022222224  dash.all.min.js:3 [64441] Index for audio time 20433.455022222224 is 299  dash.all.min.js:3 [64441] SegmentTimeline: 20427.41768888889 /<PHONE_NUMBER>  dash.all.min.js:3 [64441] Getting the next request at index: 300  dash.all.min.js:3 [64584] Switch to index 0; buffer is empty.  dash.all.min.js:3 [64584] Switch history rule index: 0 samples: 8 drops: 1  dash.all.min.js:3 [64584] AbrController (video) stay on 0/3 (buffer: 0.106)  dash.all.min.js:3 [64584] Getting the request for video time : 20430.74302222222  dash.all.min.js:3 [64585] Index for video time 20430.74302222222 is 180  dash.all.min.js:3 [64585] SegmentTimeline: 20420.74302222222 /<PHONE_NUMBER>
etc...

The same behaviour - with live DASH Widevine if autoplay used.
Issue doesn't reproduce by us on dash.js, on videojs-contrib-hls without autoplay, on VOD, or on non-encrypted live video.

I'm having the same issue. Trying to workaround using stalled or waiting events, by reseting the player and reloading the source.
videojsPlayer.on('waiting', function(e) {
videojsPlayer.pause();
videojsPlayer.reset();
videojsPlayer.src(this.videojsPlayer.currentSource());
});
Problem is that both stalled and waiting are called randomly, not only when player freezes.

Do you have an example feed?


Returning PermanentlyOverweight error on scheduled runtime upgrade when using set_code()

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
I have tested some runtime upgrade actions while using the node-template of the current master branch. But when trying the instant runtime upgrade by the sudoUncheckedWeight() extrinsic, it worked fine as expected.
Instead, when trying to schedule a runtime upgrade at a certain future block, it always returns a PermanentlyOverweight error from pallet_scheduler. (Both sudo and governance proposals)
So I've tried to check out where the exact error point was and found out it was in the execute_dispatch() method. https://github.com/paritytech/substrate/blob/master/frame/scheduler/src/lib.rs#L1119
Inside the method it measures the weight for the scheduled call (max_weight). But in the case of set_code(), the weight is set as the maximum block weight of the system. So the actual measured weight for the scheduled set_code() call will be max_block_weight + execute_dispatch_unsigned_weight, that will always exceed the limit of the maximum block weight. So due to this kind of situation it will always fall into an Overweight error.
https://github.com/paritytech/substrate/blob/master/frame/scheduler/src/lib.rs#L1132
So I'm leaving an issue for any help to figure it out. And please let me know if I've done the right way to upgrade a runtime. (Just followed the official documentations)
My runtime impl for pallet_scheduler and pallet_preimage. Except implementing the pallets, no other changes have been made.
parameter_types! {
	pub MaximumSchedulerWeight: Weight = NORMAL_DISPATCH_RATIO * BlockWeights::get().max_block;
	pub const MaxScheduledPerBlock: u32 = 50;
}

impl pallet_scheduler::Config for Runtime {
	type RuntimeEvent = RuntimeEvent;
	type RuntimeOrigin = RuntimeOrigin;
	type PalletsOrigin = OriginCaller;
	type RuntimeCall = RuntimeCall;
	type MaximumWeight = MaximumSchedulerWeight;
	type ScheduleOrigin = EnsureRoot<AccountId>;
	type MaxScheduledPerBlock = MaxScheduledPerBlock;
	type OriginPrivilegeCmp = EqualPrivilegeOnly;
	type WeightInfo = pallet_scheduler::weights::SubstrateWeight<Runtime>;
	type Preimages = Preimage;
}

parameter_types! {
	pub const PreimageBaseDeposit: Balance = 1 * DOLLARS;
	pub const PreimageByteDeposit: Balance = 1 * CENTS;
}

impl pallet_preimage::Config for Runtime {
	type WeightInfo = pallet_preimage::weights::SubstrateWeight<Runtime>;
	type RuntimeEvent = RuntimeEvent;
	type Currency = Balances;
	type ManagerOrigin = EnsureRoot<AccountId>;
	type BaseDeposit = PreimageBaseDeposit;
	type ByteDeposit = PreimageByteDeposit;
}

I also suggest to update the official runtime upgrade tutorial, because the type Preimages = (); for pallet_scheduler is not set to pallet_preimage. This will always lead to an Exhausted error.

Steps to reproduce

Add pallet_scheduler and pallet_preimage to the node-template runtime.
Build and launch the node. (./target/release/node-template --dev)
Increase the spec_version and rebuild the project in a second terminal.
Access polkadot.js apps page.
Access the sudo tab and execute a set_code() call by schedule()
Wait until it reaches the scheduled block.

This may be resolved when we don't use max_weight anymore when #13192 lands

Yes someone also asked this on SE https://substrate.stackexchange.com/questions/6919 and it should indeed be fixed by the aforementioned MR.
The work-around is to wrap it in Utility::with_weight to override the weight to something small.
Closing in favour of https://github.com/paritytech/substrate/issues/13192

Thanks for your support 👍


add download-product command

Add ability to download product from pivnet.
Sample usage:
$ om download-product -h
......
Command Arguments:
  --config, -c               string             path to yml file for configuration (keys must match the following command line flags)
  --download-stemcell        bool               If set, the latest available stemcell for the product will also be downloaded
  --output-directory, -o     string (required)  Directory path to which the file will be outputted. File name will be preserved from Pivotal Network
  --pivnet-api-token         string (required)
  --pivnet-file-glob, -f     string (required)  Glob to match files within Pivotal Network product to be downloaded.
  --pivnet-product-slug, -p  string (required)  Path to product
  --product-version          string (required)  version of the provided product file to be used for validation
  --stemcell-iaas            string             The stemcell for the specified iaas. for example 'vsphere' or 'vcloud' or 'openstack' or 'google' or 'azure' or 'aws'

$ om download-prodcut --pivnet-api-token $TOKEN --pivnet-product-slug elastic-runtime --pivnet-file-glob 'cf*.pivotal' --product-version 2.3.0 --output-directory . --download-stemcell --stemcell-iaas google
......

$ ls
......
cf-2.3.0-build.264.pivotal
light-bosh-stemcell-3363.78-google-kvm-ubuntu-trusty-go_agent.tgz

A easy way to fetch product tile and latest stemcell fulfill the requirement at the same time.

I put a story near the top of our backlog to look this over. We should get to it and hopefully merge in the next day or two.


Sqlite 3.32 Upgrade Plans ?

Are there any plans to Upgrade to SQLite 3.32
Because one feature that I could use is that the Maximum Variable Number was increased from 999
to 32766
https://www.sqlite.org/limits.html#max_variable_number
Or
Is there a way to Read SQLITE_LIMIT_VARIABLE_NUMBER Parameter?
Currently I have hard coded this value to 999

Hello, Any news?

I will plan to incorporate 3.32.x in the next release (or maybe the one after).

Thanks for the Information

Great! Looking forward to that too!

There are also several vulnerabilites fixed in 3.32

@ericsink Can't we close this, since 2.0.4 is updated to 3.33.0?

I'm closing this, i tried the newst sqlite.raw package and it worked with 16000 Variables instead of 999 Variables


Add conditional traceresponse propagation to Symfony auto-instrumentation

Depends on #143

Needs to be run after open-telemetry/opentelemetry-propagation-traceresponse was created in packagist.

@cedricziel - are you ready for this to be merged?

Yep, let's go @bobstrecansky


TFLite quantization of bias

In the docu regarding quantization of models (https://coral.ai/docs/edgetpu/models-intro/#quantization) this page of the tflite docu is linked: https://www.tensorflow.org/lite/performance/post_training_quantization#integer_only.
But the tflite quantization uses int32 for biases and I do believe there is no way around this. Is this going to be an issue with the edgetpu? In case it is a note within the edgetpu docu would be good.

Bias should be okay with int32, do you have a broken model you would like for us to take a look?

There is of course a performance reduction when doing post training quantization with my model. But what I tried is to compare the output of the quantized TFLite model (on CPU) vs the compiled model on the EdgeTpu and they seem to have the same output. So that would support the claim that int32 should be ok.
I am just surprised this is working since the EdgeTpu states all tensors must be 8-bit quantized. Anyway, thanks for the offer, but I think this can be closed.


uses an unsupported class file version (pre Java 5)

Using springboot 2.1.3 and Greenwich Cloud but got above warning but i believe this is not the actual case. I am using Java 11.
2019-03-26 09:50:58.038 [main] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor$$EnhancerBySpringCGLIB$$728e40e3 uses an unsupported class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library.

Please provide more details about your environment (you application, the spring setup, how did you install the agent) and the full log

Agent is installed as a dependency in gradle
compile group: 'co.elastic.apm', name: 'apm-agent-attach', version: '1.5.0'
Windows 10, Open JDK 11 . Same thing have been observed in centos 7 openJdk 11
And this is a spring boot application
plugins {
	id 'org.springframework.boot' version '2.1.3.RELEASE'
}
dependencyManagement {
	imports {
		mavenBom "org.springframework.cloud:spring-cloud-dependencies:Greenwich.SR1"
	}
}

And Configuration is initialized as follows
@Configuration
public class ApmConfiguration {
    @Value("${spring.profiles.active}")
    private String activeProfile;

    @Value("${spring.application.name}")
    private String appName;

    @PostConstruct
    public void setupApm() {

        System.setProperty("spring.profiles.active", getEnvironment());
        System.setProperty("elastic.apm.environment", getEnvironment());
        System.setProperty("elastic.apm.service_name", appName);

        ElasticApmAttacher.attach();
    }

    private String getEnvironment() {
        return activeProfile;
    }
}

Hi,
we're seeing the same exception in our application and we've done some digging. I'm not that firm in spring/java, but I'll try to answer as far as I can. If you need more info, I can ask some people around here.

We're running a tomcat7, openjdk 1.8.0_172 and some spring application in this setup. In particular, we're running 4.3.20 of most spring libaries I can see. If you need more specific versions of indidvual libraries, let me know, but listing ~300 different versions doesn't seem too productive

Our APM server and our elasticsearch 6 + kibana 6 for the APM setup is working correctly. We're able to gather APM in another application into the same backend.  As such I think we can ignore that part.

Our REST Controllers are annotated with springs @Component  and various jax-rs @Path / @GET annotations and discovered using classpath scanning.

We have deployed the elastic-apm-agent 1.5.0 as a jarfile on the system. After that, we added a "-javaagent:/path/elastic-apm-agent-1.5.0.jar" to the tomcats CATALINA_OPTS in bin/setenv.sh. This is pulling in the agent properly, as we will see in a moment.

Among the URL, service_name and version we configured the logging for the elastic APM setup using elastic.apm.log_file, as well as various iterations of the application_packages and the trace_methods (though these iterations didn't change the following behavior). In the logfile of the elastic-agent, we can see messages like the following. I have anonymized the java package of our application. This error is thrown for just about every controller in our application.
   2019-04-05 11:10:11.464 [localhost-startStop-1] WARN co.elastic.apm.agent.bci.bytebuddy.ErrorLoggingListener - com.pany.user.UserControllerImpl$$EnhancerBySpringCGLIB$$c5b6075d uses an unsupported class file version (pre Java 5) and can't be instrumented. Consider updating to a newer version of that library.

With this setup, we do get some amount of tracing, but most traces are reported as the name "Servlet#doGet" or "SpanServlet#get", which isn't entirely helpful.

Digging into this somewhat, we figured out that the EnhancerBySpringCGLIB-proxies are created by the Enhancer from spring core, and some of the files in spring-core-4.23 are indeed java 5 classes. The same holds for spring-core-5.1 (latest)
      Classfile spring-core.4.23/org/springframework/cglib/proxy/Enhancer$2.class
        major version: 49
      Classfile spring-core.4.23/org/springframework/cglib/proxy/Enhancer$EnhancerFactoryData.class
        major version: 49
      Classfile spring-core.4.23/org/springframework/cglib/proxy/Enhancer.class
        major version: 49
      Classfile spring-core.4.23/org/springframework/cglib/proxy/Enhancer$3.class
        major version: 49
      Classfile spring-core.4.23/org/springframework/cglib/proxy/Enhancer$5.class
        major version: 49

Our current guess thus is that something wraps our spring controllers in these EnhancerByCGLIB classes, and these for some reason still java 4/5 classes, while the rest of the class files in spring boot are java 8 files. And that in turn causes the instrumentation to choke with the exception from OP, and thus we don't get good traces.
I don't have a solution for this, but if you need further information, or want to test something, we can reproduce this problem.

You can set classes_excluded_from_instrumentation=*$$* to exclude all proxies from instrumentation. I assume you only get this error when trace_methods is set?
That removes the exception (which is really just a warning). However, I don't think it would influence the transaction name. It seems like for some reason, the JaxRsTransactionNameInstrumentation does not match your annotated JAX-RS resources. Do you spot any obvious mismatches?

I did some additional digging and you are right - the warning is not consequential for Spring Controllers. If I enable the log file and set the log_level to DEBUG, I can see that both the actual controller classes and the proxies created by spring are considered for instrumentation. The Proxies end up  being logged at WARN-level and the controllers are instrumented properly. So I guess we are not affected, or this is simply a false positive for the warning if Spring figures to create proxies through cglib. Should I add this to the documentation as a simple troubleshooting step?
Regarding the naming, I've discovered an entirely ... fascinating mess of filters, servlet classes, spring controllers and more in our application. It took me a while to understand when transactions are created, when spans are created in transactions and how names eventually end up in the full transaction name. I think in my case, the servlet api plugin created a transaction called "Servlet#doGet" and my trace_methods created a new span in the transaction called "Servlet#doGet", and the JaxRsInstrumentation set the name of that span to "MyController#getStuff". As such, all I could see in the Kibana APM tab was a request "Servlet#doGet" being called really, really often.
To remedy this, I have excluded the servlet-api plugin and traced our ServletFilter-Implementations.  Hooray. Thank you for your help

It appears these are work around solutions instead of actually fixing this. Are we concluding that spring proxy library compiled in  java 5 ? I am confused

CGLIB creates proxies which are in Java 5 bytecode format. The log just warns that these classes are not instrumented, which is what we want with proxies anyway. But I'll add a default exclude for classes containing $$, which indicates that it's a proxy. That is the same as setting classes_excluded_from_instrumentation=*$$*. Have you tried that out? Is that helping?

The servlet instrumentation actually only sets the name to ServletClass#doGet in case no more specific name, like based on a Spring controller or a JAX-RS resource, could be found.
So something is clearly not working as expected. Kudos to your workaround but that should actually work out-of-the-box as well. Does your application work with FORWARD and INCLUDE? If so, I might have a suspicion what's going wrong.


fix(snapshot): allow delete for errored snapshots

Pull Request Test Coverage Report for Build 1502

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 53.792%

Totals

Change from base Build 1499:
0.0%

Covered Lines:
8855

Relevant Lines:
14543

💛  - Coveralls


Add TigerJunction

Add TigerJunction to website.

Looks good! Added TigerJunction to the top of the course selection section


[BUG] AbsChunkedInputStream's wait_lock releases before chunk is ready

Describe the bug
From time to time, librespot-python library would fail to play audio in the middle of the stream. After debugging the problem (hard to reproduce), I noticed that AbsChunkedInputStream.read(__size: int = 0) method returns an empty buffer. After debugging it further, I tracked the problem down to AbsChunkedInputStream.wait_lock which is prematurely released under the AbsChunkedInputStream.check_availability method.
So, I put a few debugging statements around the  wait() call:
def check_availability(self, chunk: int, wait: bool, halted: bool) -> None:
    ...
    with self.wait_lock:
            if not halted:
                self.stream_read_halted(chunk, int(time.time() * 1000))
            self.chunk_exception = None
            self.wait_for_chunk = chunk
            print("block")
            self.wait_lock.wait()
            print("unblock")
            if self.closed:
                return
    ...

And received the following logs:
block
DEBUG:Librespot:Session:Chunk 25/55 completed, cached: False, stream: 131072
unblock

block
DEBUG:Librespot:Session:Chunk 26/55 completed, cached: False, stream: 131072
unblock

block
DEBUG:Librespot:Session:Chunk 27/55 completed, cached: False, stream: 131072
unblock

block
DEBUG:Librespot:Session:Chunk 28/55 completed, cached: False, stream: 131072
unblock

block
unblock

As you can see for chunk #29, self.wait_lock.wait() returns before the chunk is downloaded; thus, the buffer returned empty.
You can also verify that by checking self.wait_for_chunk which is not -1. Although, it must be set to -1 right before self.wait_lock.notify_all() calls.
To Reproduce
As I mentioned reproducing this bug is difficult since it happens haphazardly.
Not entirely sure why this happens. I did some googling, but I haven't found anyone else encountering this problem before. I've been trying streaming songs >6 mins long, and in 1 out of 5 times this issue occurs.
Expected behavior
self.wait_lock.wait() call under AbsChunkedInputStream.check_availability method should return after the chunk is ready to be consumed.
Client Information (please complete the following information):

OS: Ubuntu 21.10
Python Version: Python 3.9.7
Library Version: git+https://github.com/kokarare1212/librespot-python (master)

Additional context
One potential resolution that has worked for me was to change the call from self.wait_lock.wait() to self.wait_lock.wait_for(lambda: self.available_chunks()[chunk]).
Effectively, the result would be the same as we are blocking and waiting for the chunk to become available.

Thank you for reporting the bug.
I have made the change.


[Bug]: Icons Button name

Prerequisites

[X] I have searched the backlog for duplicate or closed feature requests

Your test device
iPhone 14 pro Max
OS Version
iOS 17.0
App version
v0.8.0
Describe the issue
The name is "Buttons Icons."
Expected Behavior

The name should be "Icons Button."
Change the order and put Segmented Button last

@Tayebsed93 the information was to be changed base on our last discussions to "Icon Buttons"


Update Catch2 to 2.9.0

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/kaihowl/hunter/builds/25314141
https://travis-ci.com/kaihowl/hunter/builds/115712770

There is now an additional library integrated into Catch2, called nonius. This is disabled by default and enabled with the flag CATCH_CONFIG_ENABLE_BENCHMARKING. Would it make sense to add an additional compilation unit to the examples that exercises this compilation flag? Or do we keep the testing to a minimum as to not run afoul of testing the entire library again as part of integrating it into Hunter?

Hold on, there is already a new version available after some bug was discovered upstream. I will close this PR and open a new one with the new version.


supporting Remove Transceiver

Your environment.

Version: Latest
Browser: Any Browsers
Other Information - N/A

What did you do?

I'm developing SFU Server using ion-sfu.
Client can send Join with offer SDP repeatedly and this happens negotiate or re-negotiate Publisher's peerConnection.
SetRemoteDescription keeps adding transceiver for Receiver so peerConnection.rtpTransceivers keeps growing memory because Transceiver references allocated variables.
As much as this PeerConnection alive, memory never shrinks.
What did you expect?
When Transceiver is stopped, all references in PeerConnection is removed.
What happened?
I don't know keeping transceivers is standard behavior or not. If not, how about providing RemoveTrasnceiver func?
heres debugging log using delve
v3.PeerConnection {
	statsID: "PeerConnection-1640932940100021665",
	mu: sync.RWMutex {
		w: (*sync.Mutex)(0xc0002e0d90),
		writerSem: 0,
		readerSem: 0,
		readerCount: 0,
        ...
        ....
	rtpTransceivers: []*webrtc/v3.RTPTransceiver len: 103, cap: 128, [
		*(*"webrtc/v3.RTPTransceiver")(0xc000234c60),
		*(*"webrtc/v3.RTPTransceiver")(0xc000234e10),
                 ...
                 ...
    		*(*"webrtc/v3.RTPTransceiver")(0xc000473680),
		*(*"webrtc/v3.RTPTransceiver")(0xc00193eab0),

no references is stored. it isn't main reason that memory grows I think.

Hi lenaky, I also meet this question too. Can you give me any advice? Thanks a lot!
In my opinion, more and more rtpTransceivers will cause SDP negotiation to bring a lot of overhead in calling CreateOffer, which needs to generate a lot of objects. In my test of continuously join and leave a large conference, the memory of the server will quickly increase because of this, until the process is killed due to OOM. It is not a leak, but because rtpTransceivers is not removed.
So I think this issue still needs to be resolved.


Spring dependencies upgraded

Spring dependencies upgraded to latest spring 2 version

https://jenkins.fdp.osgp.cloud/view/SMHE-cucumber/job/gxf-smhe-cucumber-build/89/


Fixes URL for organizations

This PR appends the /u/username to organizations users to fix a problem requesting images for private visualizations.

@CartoDB/frontend: review this, please please.

Frontend tests were OK :+1: (details)

:)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


9/15/2020 Publish

Docs Build status updates of commit 0485d57:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/Get-AzureADContactManager.md
:warning:Warning

Details

azureadps-2.0-preview/AzureAD/Get-AzureADContactManager.md
:warning:Warning

Details

azureadps-2.0-preview/AzureAD/Get-AzureADContact.md
:warning:Warning

Details

azureadps-2.0/AzureAD/Get-AzureADContact.md
:warning:Warning

Details

azureadps-2.0/AzureAD/Remove-AzureADContactManager.md
:warning:Warning

Details

azureadps-2.0-preview/AzureAD/Remove-AzureADContactManager.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/install-adv2.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/new-user-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/working-with-licenses.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Enabling-licenses-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/List-Service-principal-application-roles.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/signing-in-service-principal.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Find-Module-version.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/working-with-licenses.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Find-Module-version.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/signing-in-service-principal.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Cannot-find-object.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/PowerShell-logfile.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Install-previous-version.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/PowerShell-logfile.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Cannot-find-object.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/List-Service-principal-application-roles.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/recovering-deleted-data.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Install-previous-version.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/importing-data.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/recovering-deleted-data.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/importing-data.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/install-adv2.md
:warning:Warning

Details

docs-conceptual/azureadps-1.0/install-msonlinev1.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/using-extension-attributes-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Enabling-licenses-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/using-extension-attributes-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/overview.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/overview.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Working-with-Administrative-Units.md
:warning:Warning

Details

docs-conceptual/azureadps-1.0/overview.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Working-with-Administrative-Units.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/new-user-sample.md
:warning:Warning

Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/AzureADPreview.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/text.txt
:white_check_mark:Succeeded

azureadps-2.0/AzureAD/AzureAD.md
:white_check_mark:Succeeded

azureadps-2.0/AzureAD/Get-AzureADContactManager.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContactManager.md'.

azureadps-2.0-preview/AzureAD/Get-AzureADContactManager.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContactManager.md'.

azureadps-2.0-preview/AzureAD/Get-AzureADContact.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContact.md'.

azureadps-2.0/AzureAD/Get-AzureADContact.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContact.md'.

azureadps-2.0/AzureAD/Remove-AzureADContactManager.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContactManager.md'.

azureadps-2.0-preview/AzureAD/Remove-AzureADContactManager.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzureADContactManager.md'.

docs-conceptual/azureadps-2.0/install-adv2.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Azure Active Directory PowerShell for Graph' is duplicated with other articles: 'docs-conceptual/azureadps-2.0/install-adv2.md(15,1), docs-conceptual/azureadps-2.0/overview.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 15, Column 1: [Suggestion-duplicate-titles] Title 'Azure Active Directory PowerShell for Graph' is duplicated in: 'docs-conceptual/azureadps-2.0/install-adv2.md(15,1), docs-conceptual/azureadps-2.0/overview.md(15,1)'. Titles must be unique within a docset.

docs-conceptual/azureadps-2.0/new-user-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/working-with-licenses.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/Enabling-licenses-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/List-Service-principal-application-roles.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/signing-in-service-principal.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/Find-Module-version.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/working-with-licenses.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/Find-Module-version.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/signing-in-service-principal.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/Cannot-find-object.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/PowerShell-logfile.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/Install-previous-version.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/PowerShell-logfile.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/Cannot-find-object.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/List-Service-principal-application-roles.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/recovering-deleted-data.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/Install-previous-version.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/importing-data.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 52, Column 1: [Suggestion-code-block-unclosed] Unclosed code block. Code blocks must begin and end with triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

docs-conceptual/azureadps-2.0-preview/recovering-deleted-data.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/importing-data.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/install-adv2.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-1.0/install-msonlinev1.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/using-extension-attributes-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/Enabling-licenses-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/using-extension-attributes-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0/overview.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Azure Active Directory PowerShell for Graph' is duplicated with other articles: 'docs-conceptual/azureadps-2.0/install-adv2.md(15,1), docs-conceptual/azureadps-2.0/overview.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 15, Column 1: [Suggestion-duplicate-titles] Title 'Azure Active Directory PowerShell for Graph' is duplicated in: 'docs-conceptual/azureadps-2.0/install-adv2.md(15,1), docs-conceptual/azureadps-2.0/overview.md(15,1)'. Titles must be unique within a docset.
Line 19, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/azuread?view=azureadps-2.0 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 26, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/azuread?view=azureadps-2.0 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 27, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/msonline?view=azureadps-1.0 NOTE: This Suggestion will become a Warning in early December, 2020.

docs-conceptual/azureadps-2.0-preview/overview.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 19, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/azuread?view=azureadps-2.0 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 26, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/azuread?view=azureadps-2.0 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 27, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /powershell/module/msonline?view=azureadps-1.0 NOTE: This Suggestion will become a Warning in early December, 2020.

docs-conceptual/azureadps-2.0/Working-with-Administrative-Units.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-1.0/overview.md

Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/Working-with-Administrative-Units.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

docs-conceptual/azureadps-2.0-preview/new-user-sample.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[BUG] 'bulk' requests produce warning about accessing system indices

What is the bug?
When using the 'bulk' api in the opensearch-py library, I get a warning that the request accesses system indices.
How can one reproduce the bug?
#!/usr/bin/python3

from opensearchpy import OpenSearch
from opensearchpy import helpers

os_url = input("OpenSearch url: ")
os = OpenSearch([os_url],
                        use_ssl=False,
                        verify_certs=False,
                        ssl_show_warn=False)

def demo():
        yield({ "_index": "demo",
                "foo": "bar"}
                )

helpers.bulk(os, demo())

[ec2-user@host ~]$ ./demo.py
OpenSearch url: ...
/home/ec2-user/.local/lib/python3.7/site-packages/opensearchpy/connection/base.py:208: OpenSearchWarning: this request accesses system indices: [.opendistro_security], but in a future major version, direct access to system indices will be prevented by default
  warnings.warn(message, category=OpenSearchWarning)

What is the expected behavior?
No warning :)
What is your host/environment?

OS: AL2 on EC2 x86_64
Version: OpenSearch 1.1.0, opensearch-py 1.0.0, python 3.7.10

Related: https://github.com/opensearch-project/OpenSearch/issues/1108

I'd say that a bulk request that specifies a non-system index should not be doing anything to trigger this warning even one time. Note that the index specified is not the index being warned about. So either the python client or OpenSearch is doing something that generates this spurious warning during bulk actions, and that should be fixed.

I think this would be an issue in Core. If there are no objections, I will close it.

@dblock would you be able to transfer this issue to https://github.com/opensearch-project/opensearch/issues


Design review horizontal scrolling

Contributes to #2509

Rename Sticky column story to Frozen columns
The width of the sticky actions column on right is too wide (width should be 48px, in addition, the column header should also be 48px): Scope - frozen columns, row action buttons
There should not be any white space/margins at end of the scrollable column header row: Scope - frozen columns, row action buttons
Frozen column border should use $active-light-ui: Scope - frozen columns, row action buttons, select row, radio select
Control for multi-wrap column property, multiLineWrap, also potential for adding it once for all columns and not on a per-column basis
Unfreeze the first column at <672px, and the frozen column header not sticking anymore: Scope - frozen columns, row action buttons, select row, radio select
Row index labels to the left of selectable row/checkbox : Scope - frozen columns, row action buttons, select row, radio select
Remove "click action menu" from frozen columns story

What did you change?
Datagrid/Datagrid.mdx
Datagrid/Datagrid.stories.js
Datagrid/useActionsColumn.js
Datagrid/useDefaultStringRenderer.js
Datagrid/useSelectAllToggle.js
Datagrid/useSelectRows.js
Datagrid/useStickyColumn.js
Datagrid/Datagrid/DatagridSelectAll.js
Datagrid/DatagridSelectAllWithToggle.js
Datagrid/Extensions/RowActionButtons/RowActionButtons.stories.js
Datagrid/styles/_datagrid.scss
Datagrid/styles/_useSelectAllToggle.scss
Datagrid/styles/_useStickyColumn.scss
How did you test and verify your work?
Storybook: stories - frozen columns, row action buttons, select row, radio select

Raised by mistake.


Fix #189 whitespace removal

Changes
Fixes #189 : Remove leading and trailing whitespace in the comment box so stop bleach failing it when it's empty with carriage returns
How to test

Complete a survey with valid data
Enter multiple carriage returns in the comments box
Check you can submit (on master it will error)

Who can test
Anyone apart from @warrenbailey

23 test failures, bar that looks good

One failed due to rebase fun, so I've fixed that one. No idea why Travis failed the others