AzureCP works in all web applications except central admin

I am using AzureCP v12.Beta, version committed May 14
AzureCP does not return results from Central Administration.
From the 'Add users to this group' dialog, I see "Sorry, we're having trouble reaching the server."  From the Web Applications page -> User Policy -> Add Users -> 'Select People and Groups' dialog, I get the error "No results were found to match your search item.  Please enter a new term or less specific term.  This is true even when selecting 'Bypass Azure AD lookup' from the AzureCP configuration page.
These errors only exist in Central Administration, no other web application.
I see the following in ULS:

[Forced due to logging gap, cached @ 05/10/2018 11:05:04.64, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache.

[AzureCP] Unexpected error in FillSearch: System.ArgumentException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: encodedValue, Callstack:
at Microsoft.SharePoint.Administration.Claims.SPClaimEncodingManager.DecodeClaimFromFormsSuffix(String encodedValue)
at azurecp.RequestInformation..ctor(IAzureCPConfiguration currentConfiguration, RequestType currentRequestType, List`1 processedClaimTypeConfigList, String input, SPClaim incomingEntity, Uri context, AzureADObjectType[] directoryObjectTypes, String hierarchyNodeID, Int32 maxCount)
at azurecp.AzureCP.FillSearch(Uri context, String[] entityTypes, String searchPattern, String hierarchyNodeID, Int32 maxCount, SPProviderHierarchyTree searchTree)

Claims Search call failed. Error Message: Object reference not set to an instance of an object.  Callstack:    at Microsoft.SharePoint.WebControls.PeopleQueryControl.IssueClaimsQuery(String searchPattern, String providerID, String hierarchyNodeID, Int32 pageSize, SPProviderHierarchyTree spgroupTree).

The Active Directory spclaimprovider was disabled via the following:
$cpm = Get-SPClaimProviderManager
$ad = get-spclaimprovider -identity "AD"
$ad.IsVisible = $false
$cpm.Update()

I downloaded the update, updated via Update-SPSolution, and manually ran IISRESET on all servers.
Unfortunately I am still unable to resolve from Central Admin and now I am unable to resolve from any Web Application.  The error has changed and is now:

[AzureCP] Unexpected error while querying tenant '': Microsoft.Graph.ServiceException: Code: BadRequest  Message: An identifier was expected
at position 16.    Inner error  , Callstack:
at Microsoft.Graph.HttpProvider.d__19.MoveNext()  --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.BaseRequest.d__36.MoveNext()  --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.BaseRequest.d__321.MoveNext()  --- End of stack trace from previous location where exception was thrown ---      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)      at Microsoft.Graph.GraphServiceUsersCollectionRequest.<GetAsync>d__4.MoveNext()  --- End of stack trace from previous location where exception was thrown ---      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)      at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at azurecp.AzureCP.<>c__DisplayClass52_0.<b__0>d.MoveNext()

I added the tenant as the GUID identifier and tried tenant.onmicrosoft.com as well as tenant.microsoftonline.com.   Once the other two tenant identifiers were added, the configuration page threw errors, see issue 18, but the change seems successful as the aforementioned error repeats with the three different identifiers.  Is there a way to clean this out and try again?
Thank you so much for this claim picker and the LdapCP.

Ah yes, sorry I forgot to mention that you need to reset the claim types list after you updated AzureCP.
You have 2 options:

central admin > AzureCP global settings page > "Reset AzureCP Configuration" (but that will also remove all tenants registered)
PowerShell: run this script:

Add-Type -AssemblyName "AzureCP, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=65dc6b5903b51636"
$config = [azurecp.AzureCPConfig]::GetConfiguration("AzureCPConfig")
$config.ResetClaimTypesList()
$config.Update()

Thank you very much for your feedback!

Thank you for the suggestion; I appreciate all your help!  I am still getting the same error after resetting the claim types list.  I also tried resetting the AzureCP configuration and starting from scratch with no change in behavior.   The error message is the same.
I am using the Tenant identifier GUID as the Tenant name in the 'Informations to add new Azure tenant' form.  This worked prior to the May 14 update.  I also tried tenant.onmicrosoft.com (domain status: available) and tenant.microsoftonline.com (primary domain).

I tried both of the following (individually) in addition to the GUID
TENANT.onMicrosoft.com
tenant.microsoftonline.com
Is there anything that needs to be done to the Enterprise App in Azure AD after upgrading the solution version?
The claims mapping looks good:

Same error:

[AzureCP] Unexpected error while querying tenant 'TENANT.onMicrosoft.com': Microsoft.Graph.ServiceException: Code: BadRequest  Message: An identifier was expected
at position 16.    Inner error  , Callstack:
at Microsoft.Graph.HttpProvider.d__19.MoveNext()  --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()      at Microsoft.Graph.BaseRequest.<SendRequestAsync>d__36.MoveNext()  --- End of stack trace from previous location where exception was thrown ---      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)      at Microsoft.Graph.BaseRequest.<SendAsync>d__321.MoveNext()  --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.GraphServiceUsersCollectionRequest.d__4.MoveNext()  --- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at azurecp.AzureCP.<>c__DisplayClass52_0.<b__0>d.MoveNext()

Nope, claims mapping page is not good: look at the properties column: it shows numbers instead of actual property names.
That's the reason why you have this error (I changed the enum type that stores property names).
For some reason the reset of claim types configuration didn't work. Can you reset it again from claims mapping page and see if it works?

I swear I tried that before posting the error message but I just tried again anyway.  It works just fine now.  Sorry to waste your time!  Thank you so much for your help.


Add acceptance tests using cypress and miragejs

Pull Request Test Coverage Report for Build 99

26 of 146 (17.81%)  changed or added relevant lines in 10 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+31.2%) to 60.687%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/index.js
0
27
0.0%

src/server.js
0
93
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/buixieval.js
1
66.67%

src/App/Buixieval/Buixieval.js
3
0%

Totals

Change from base Build 84:
31.2%

Covered Lines:
670

Relevant Lines:
1012

💛  - Coveralls


Upgrade Newtonsoft.Json to 13.0.1.  Port patches from source-build-externals.

This supports some contributing repos which have updated their Newtonsoft.Json version as well.

Closing, this is included in https://github.com/dotnet/source-build/pull/2967.


query performance improvements

resolves #284

This looks mostly good.  However there are some applications which consume the Yap api that might need some additional data points.  Checkout https://github.com/bmlt-enabled/yap-bots and https://github.com/bmlt-enabled/yap-alexa-skill which call api.php, which in turn uses getMeetings()

My bad I squashed the commit, I guess that was silly before approving.

I added location info and province I believe

There seems to be some other values missing.


RuntimeError: ASGI transport was closed

I'm getting the following error when using Granian (0.5.0) with Django (4.2.2). This error does not appear to occur with version 0.4.3 of Granian. It also doesn't seem to break functionality, the web server still serves the page, but these errors appear on nearly every request. Additionally, if it helps, I'm running this via docker with a RHEL-8-UBI image. Let me know if there are any further details I can provide & thank you for creating such a wonderful server!
webapp-app-1       | Task exception was never retrieved
webapp-app-1       | future: <Task finished name='Task-11' coro=<future_watcher_wrapper.<locals>.future_watcher() done, defined at /usr/local/lib/python3.11/site-packages/granian/_futures.py:2> exception=RuntimeError('ASGI transport closed')>
webapp-app-1       | Traceback (most recent call last):
webapp-app-1       |   File "/usr/local/lib/python3.11/site-packages/granian/_futures.py", line 4, in future_watcher
webapp-app-1       |     await inner(watcher.scope, watcher.proto)
webapp-app-1       |   File "/usr/local/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 160, in __call__
webapp-app-1       |     await self.handle(scope, receive, send)
webapp-app-1       |   File "/usr/local/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 190, in handle
webapp-app-1       |     await self.send_response(response, send)
webapp-app-1       |   File "/usr/local/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 284, in send_response
webapp-app-1       |     await send({"type": "http.response.body"})
webapp-app-1       | RuntimeError: ASGI transport closed
webapp-app-1       | Application callable raised an exception

@ameyer117 I wasn't able to reproduce the issue.
I still have made a change in https://github.com/emmett-framework/granian/commit/d127424eecbdd4dc49e3165eae3d1af436c13b5d to avoid tx in ASGI I/O when body is empty to avoid prompting errors in such case.
Will be released in 0.5.1 shortly, gonna keep this open until that.

@gi0baro - thank you!


Describe major contribution aspects

@alexbeatnik could you please review this pull request and leave your comments?

@extsoft Why do you use 3 commits in one pull request?

@extsoft  The meaning of this commit https://github.com/bees-hive/elegant-git/pull/176/commits/4ad1d287bc89ea5ca2eece20640354acb3e309b3 is understandable only after you read the file

@alexbeatnik as for me, it’s not a problem having several commits in one PR. This is because they related to a single goal - describe the contribution process.
Sincerely,
Dmytro
Sent from my iPhone
1 вер. 2019 р. о 21:49 alexbeatnik<EMAIL_ADDRESS>пише:

@extsoft Why do you use 3 commits in one pull request?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@alexbeatnik as for me, it’s not a problem having several commits in one PR. This is because they related to a single goal - describe the contribution process. Sincerely, Dmytro
…
Sent from my iPhone 1 вер. 2019 р. о 21:49 alexbeatnik<EMAIL_ADDRESS>пише:
@extsoft Why do you use 3 commits in one pull request? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

understood thanks

@alexbeatnik I've fixed all your comments. Please look at changes again.

Thanks, looks good


[iOS] Remove iosClientId requirement from JS side

We can get clientID from Google-Service.plist directly so there is no need for additional iOS specific configuration when calling configure().
Additionally, since we are checking if Google-Service.plist is missing, we can inform users about misconfiguration. Hopefully this reduces setup pain a bit.
Updated README and fixed wording here and there.

Pushed a fix for NSMutableDictionary. :)


Ideas for firewall circumvention

Currently, two ports are needed for hellcat to operate: a control port and a data port. This can cause issues in firewalled environments where very few ports are accessible. For example, I run an SSH daemon on port 443 so that I can access it from behind a firewall that blocks all outgoing connections except for HTTP and HTTPS. This means that I only have one port left (80) and so cannot use hellcat effectively.
I have two ideas of how to get around this, but there are probably more ways it could be done:

Allow the hosts for the control and data ports to be different
This would allow SSH port forwarding to be used for the control port, making my usecase possible.
Remove the need for a control port altogether.
From a quick look at the source code, it seems that the control port simply tells the receiver when to stop receiving. Perhaps this could be done by closing a data port connection before chunksize bytes have been sent. That way, if the data being transferred is divisible by chunksize a new connection could be opened and then immediately closed when the transfer is finished, and if not, the connection would be automatically closed.

I've not had a detailed look at the code yet, so I don't know whether or not these ideas would work, but I'll try and take a look at some point, and I may try and patch this functionality in.
Let me know what you think and if you have any other suggestions!

I've made a patch for a separate controlport and will submit a PR now. Still looking into the possibility of removing the need for the controlport altogether.

Of course, I can't actually push my PR because I'm on a firewalled connection, lol.
I'll start looking at my second idea and push when I get home.

I've managed to remove the need for the controlport, so both my ideas do work.
From the README, it seems there is planned feature to allow hellsend to tell hellrecv what the chunksize is. Obviously some kind of transport would be needed to do this, which would be the controlport.
With the controlport removed, this could be acheived by sending a single integer of a set length (say, 16-bit or 32-bit unsigned) before sending any data, and using that as the chunksize. Of course, there may be issues with endianness, but these would occur with the controlport as well and are relatively easy to solve using a few bitwise operations.

Okay, I've got two branches ready to PR, so I'm wondering which you'd prefer: the one that adds controlhost or the one that removes controlport.


Add "files" key to package.json

I only listed index.js, because according to https://docs.npmjs.com/files/package.json:

Certain files are always included, regardless of settings:

package.json
README (and its variants)
CHANGELOG (and its variants)
LICENSE / LICENCE

(closes #6)

I actually prefer to use .npmignore because it's easy to forget about this and if you add new files it can be easy to create broken releases.

Will do. I'll update this shortly.

I've now edited this to use .npmignore.

Thanks


havfo/multiparty-meeting will be renamed and transfered to edumeet/edumeet

On this Friday this transition will happen, please update after it your links.

Edumeet transfer finished


Go server run fail (cannot use *notification)

I setup golang on Mac (using official manual)

Install go-gcm:

	$ go get github.com/google/go-gcm
	$ go install github.com/google/go-gcm

Open friendlyPing/server/Go folder and run:

go run server.go -testData testdata/clients.json -apiKey XXXXXXXXX -senderId XXXXXXXXX

Then I get:

# command-line-arguments
./server.go:174: cannot use *notification (type gcm.Notification) as type *gcm.Notification in field value

I checked that /Users/username/gocode/src/github.com/google/go-gcm exist in my workspace folder
Can you give me some directions what is need to be checked in my setup? I suggested that go do not see go-gcm package, but everything looking fine for me

HI @tv8eye, I got the same error.
Where you able to solve it?
Thanks in advance

Hey @guillosaracco
No, I decided to write small Java tool to send messages :) That how i solved it.


Method fsm.transitions() should always return array

The method fsm.transitions returns Array or undefined now. The description states it returns a list of events. No events for a current state doesn't imply no list of events. It implies the empty list.

fixed in (upcoming) v2.4


Manjaro-keyring not supported on manjaro.

VS Code Version:1.70.0
OS Version:Linux x64 5.19.0-2-MANJARO
About keyring:
After login,it says it cannot write login information into keyring,
But on my system,it has a keyring named manjaro-keyring(i'm sure i have installed it).

Seeing issue 92972,I didn't get any useful information.
This problem makes me login every restart vscode.

Manjaro keyring needs to support Secret Storage API talked about here:
https://code.visualstudio.com/docs/editor/settings-sync#_linux

If the error is "The name org.freedesktop.secrets was not provided by any .service files", make sure that you have a package that implements the Secret Storage API installed, such as gnome-keyring. VS Code expects such a package for storing credentials on the machine. More information can be found in issue #104319.

Can you get an issue going on Manjaro to support this in their keyring?

Is manjaro-keyring an app that you can open and store credentials into? Everything I'm reading online says it is just for pacman... in which case you'll need a Secret Storage compatible keyring like gnome-keyring

oh i see, i read it's doc, it's really just for pacman.
maybe i must try to install another keyring.
thank you!


<EMAIL_ADDRESS>hash check failed

Checking hash of SpotifyFullSetup.exe ... ERROR Hash check failed!
App:         spotify/spotify-latest
URL:         https://download.scdn.co/SpotifyFullSetup.exe
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    d96fd7c3f3970fbb26192b2d8022efdd2edc7fb60669f2bb1d351ad3e816c8f5
Actual:      ee2957008b72e044738bcbd4816fe32698ee361b9462556bad5354768707873a

Fixed, thank you!


Style tweaks

Various style tweaks to match up with design references

@cdebourcy hmm interesting. Reverted that button for now / can be in a different PR.

Ok. Shouldn't be hard though -- just a matter of making sure clicking "New Project" doesn't trigger form onSubmit action.


Controversy statements

Checklist

[X] I've searched through the current issues to make sure this change hasn't been suggested already.
[X] I agree to follow the Code of Conduct that this project adheres to.

Which documents need updating?
https://leafletjs.com/
Motivation
To make things clear.
Suggested changes
Once you visit the main page you can see a statement regarding russian invasion, it's clearly you don't support it.
At the same time you display Crimea as a part of russia federation.
These statements are conflicting with each other.

Closing as a duplicate of https://github.com/Leaflet/Leaflet/issues/5056 - Leaflet is the map display library, not the underneath map data.
What you're seeing is OpenStreetMap data (as you should be able to discern from the attribution). The subject of Crimea has been contentious in the past (as have been Kosovo, Cyprus, and a dozen other places). And just to make this clear: even though the Leaflet folks know the OSM folks (and vice versa), that doesn't mean that both groups operate as a whole (as opposed to commercial providers, which have the map interface and the dataset under the same umbrella).
The people taking care of territorial disputes is the OSMF DWG (see https://wiki.openstreetmap.org/wiki/Data_working_group ). Alas, maintaining Leaflet keeps us busy enough, and (I have some second-hand accounts that) working in the DWG is quite draining. As much as we'd love to move the OSM border, it's not an easy task and it has its own geopolitical implications.
Do have a look at https://wiki.openstreetmap.org/wiki/Disputed_territories#Europe for a bit more background.

@dmitrygorbenko do you find a way to change the border of Ukraine?


BIG MODE

Changes in this merge include:
-Core memery functionality is now a class that will keep the CLIP model, tree index, and database cached once loaded
-Typing almost everywhere
-pyproject.toml now replaces setup.py, settings.ini, MANIFEST.in, pipfile, and more
-github workflow will build the project (including installing CLIP) whenever a merge to main is made. It also lints with flake8 and could be configured to run tests
-New CLI commands: build - indexes the given directory, purge - removes index and database files from the directory
-Notebooks moved from the root directory to the 'notebooks' directory
-You can now specify the number of workers for indexing from the streamlit GUI
In terms of speed, the big change here is that caching the model saves a good chunk of time, instead of having to load it again for every search and every index. If you keep the GUI open, it just stays cached. Stuff like cleaning index files has also been moved where it was in the streamlit GUI to the core module.
TODO:
-The bottleneck in terms of displaying images now comes from the speed with which streamlit can display them. So any optimizations that can be made to the GUI would be helpful
-In my opinion, some of the data structures that get used for the databasing are kind of confusing and could be split up so the database gets built in a more atomic way

As usual, i have misgivings about OOP and class-based programming, but i can't deny this does speed things up. Installation works nicely through poetry too. I'll merge and then try to upload to PyPi

As usual, i have misgivings about OOP and class-based programming, but i can't deny this does speed things up. Installation works nicely through poetry too. I'll merge and then try to upload to PyPi

I forgot to mention a couple notes here. These changes were pretty opinionated because I just wanted to address the big stuff and let you decide on the details. I did comment out the code for the Notebook GUI we previously had because it was causing issues and was no longer in a notebook.
Also, the switch to pyproject.toml might have stripped out some metadata from settings.ini so if there's anything you want in there you'll have to add it back manually. I was able to upgrade all the dependencies except for streamlit with no errors, but the pyproject uses "^" to pin them with semantic versioning. I like the way it is right now and especially with torch I was having errors finding 1.7.1 for some reason.
I'm totally down for a rewrite to make it more functional, I just genuinely don't know a good way to cache stuff without using a class like that. It could be a fun learning experience though!
Unfortunately, you probably won't be able to upload to PyPi because our dependency for CLIP still comes from github and that's not allowed.
I also added a workflow to repo, so you might want to delete the one you had previously it it's still around.


Breaks from Bootstrap 3 to 4

With the coming weeks that Bootstrap 4 beta will probably be released (it's at 99% completion), it would be really great to have some minor fixes to make this project reusable with 4.
The main issue with the switch, as stated partly before with #1339, is that icons don't show up because of removed classes such as caret, as well as the replacement of Glyphicons with Font Awesome.
The second issue, though minor, is that the global search bar is no longer in the correct position and gets squished. Probably an easy CSS fix, but something worth noting.
Another important issue is that if I download your examples page but replace v3 with v4, then the navbar disappears unless I manipulate the CSS/play around with the new v4 classes, and the documents aren't laid out correctly.
The images below were used with the "Quick Demo" code provided in the README.md, except search={true} was added to BootstrapTable.
Bootstrap 3:

Bootstrap 4:

#780 a pull request was made to fix the icons issue, but after trying to fix it myself with the newer files (and doing essentially the same thing, which was globally replacing Glyphicons with Font Awesome), I still had errors.
#1272 asked something similar, but the issues weren't clearly stated so I'm making a specific issue for it.
If icons could at least be fixed initially, then the main components of this repository could definitely be used.
Also worth noting that I downloaded 4.0.0-beta.7 and had the same results as the images above, which used the most recent stable version.

@jtheberge, thanks your sharing, I'll try to make react-bootstrap-table more compatible with bootstrap@3 and bootstrap@4, but need some time, so PR is welcome, thanks

any progress on this?

I am waiting for this issue to be fixed. Also there is problem while selecting pagePerSize. The pagePerSize only work if you click in the number but not in that column.

@Suban5 if you use bootstrap@4, please add version="4" on BootstrapTable.

Remember to upgrade to newest react-bootstrap-table, thanks.


release: 1.2.0

:robot: I have created a release beep boop
1.2.0 (2022-08-30)
Features

add LTP0 to refresh token (bc17203)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/starudream/douyu-task/releases/tag/v1.2.0 :sunflower:


Rejected by Apple for being too similar to iOS passcode interface

[x] I have read this issue template and provided all possible information.
[x] I'm using CocoaPods and have run pod update before filing this issue.

Hardware / Software
Which version of the library were you using? 0.0.2
Which version of iOS are you running? 11.4
What model of iOS device were you testing on? iPhone 8
If using CocoaPods, which version of CocoaPods are you on? 1.5.2
Goals
What is the outcome result you want to achieve with this library?
The interface to be different enough from the stock passcode interface to be approved by Apple.
Expected Results
What did you expect to happen?
Approval by Apple.
Actual Results
What happened instead?  (Please attach a screenshot/screen recording if possible)

Steps to Reproduce
What are the steps needed to reproduce this issue? Submit an app to the App Store with the light theme. Tried updating the title text, and even injecting the app icon into the passcode screen (via addSubview to passcodeView.backgroundView). Still rejected.
If this bug was caused by a specific image, please post it here.

Thanks for filling out the issue template properly @corymayer!
Argghhhh! And I JUST got back from WWDC when I could have asked the App Store team directly about this. I can't believe I forgot.
Dammit. I was afraid this would happen. I was hoping changing the top text and having an icon would be enough, but it looks like it's not.
Usually in the rejection process, you can request that Apple calls you so you can discuss what needs to be changed. If it's not too much of an imposition, can you please ask them to call you? I'm really curious to know which specific aspects they don't like. If the title text doesn't matter, I guess it's the circular buttons.
Thanks for letting me know about this!

Ah, bad timing. We did request a call, but I didn't get a chance to talk to them personally– it was someone else from my team. They had a problem with our title text, which was originally "Please enter your passcode to access [APP_NAME]", and wanted us to change it to "Please enter your organization ID". It seems like they didn't like the word "passcode". They also told us that the keypad resembled the iOS one too closely, but my team member didn't ask for specifics. I'm going to see if they can follow up and ask for more details (I'm currently out of office).

Yep. Murphy's Law at its finest. 😅
Ahh okay. Yeah, I can understand that. I think I did read somewhere that Apple is REALLY touchy about apps using the name "Passcode". I was considering saying in the README that for numerical codes to change it to "Enter your  PIN Code".
Okay. I figured as much. They keypad's going to be the main problem.
I'm not sure if it's merged in yet (I'm REALLY behind on my OSS projects right now. 😅), but there's an option to hide the lettering and the border lines. That MIGHT make it visually distinctive enough to pass muster.
In the meantime, I'll definitely start thinking of a complete redesign for this view controller. As fun as it was to recreate the iOS 7 lockscreen effect, it's a pretty lousy library if it can't be used in shipping products.

Hello corymayer,
Did you get approval from apple?
Kindly advice me changes.
Thanks.

Any update on this issue?

Apple gave us a one-time exception, but claimed that any future updates would need to fix this issue. Unfortunately the person who was in contact with Apple still hasn't had a chance to follow up with them. I am on leave for the summer, otherwise I would look into it myself.

@corymayer Thanks for the update Cory!
I'll start looking into redesigning this library as soon as I can. I'm probably going to end up making it look a lot more similar to the keypad in the settings panel (ie rounded rectangles).

We are facing the same issue. Can you please help us how to resolve it.

Hi @tapannathvani! Sorry, I haven't had a chance to get to doing a complete redesign of this thing yet.
Sorry to hear that! If you need to ship ASAP, I've seen other apps get approved if they change the shape of the buttons to something other than circles.
The button shapes are controlled here: https://github.com/TimOliver/TOPasscodeViewController/blob/master/TOPasscodeViewController/Models/TOPasscodeCircleImage.m
For now, you could make a fork, and change it to something else (Like UIBezierPath rounded rectangles) and that should hopefully do it in a pinch.
Good luck!

@TimOliver Thanks a lot for quick reply. Made Rounded Rectangle right now and submitting the same to the apple store.

@TimOliver It works. Apple approved application with Rounded rectangle.

Awesome! Thanks @tapannathvani! I didn't have a clear idea of how much this thing would need to be modified to pass Apple's review, so that was EXTREMELY valuable to hear. Thanks so much! :)


Password reset doesn't work correctly if the username isn't the User.username

We've extended login to allow users to login with any Email.address known for their Person. This extension is failing at the password reset code  - users have to use their actual User.username, and they may not be able to know what that even is.

This was actually the User has no Person problem - the reset was being done to a broken User record.


How to change the tab background color while it is in active state

how can I change the tab background color while in active state

You can't

Please note: You didn't fill out the issue template (the prefilled text if you open an issue). The issue template always helps every maintainer in every project by having structured reports, informations and generally stay sane. If you submit a issue, always fill out the issue template, if there is one.
I'm going to close this issue since it's not possible and thus a feature request. PRs are welcome.


Encoder::multithread without zstdmt returns an error

Using Encoder::multithread returns at runtime a Result::Err value that says "Unsupported parameter", unless the zstdmt Cargo feature was enabled at compile-time.
To figure this out I ended up reading code all the way to finding #ifdef ZSTD_MULTITHREAD in the C library.
At minimum, the doc-comment of multithread should explain to enable the Cargo feature. I’d be nice if the error message was more specific, too. However it would be better IMO to eliminate this runtime error case entirely by using #[cfg(feature = "zstdmt")] so the method does not exist at all when the feature is not enabled. Until https://github.com/rust-lang/rust/issues/43781 is stabilized though this may require some handling for docs to show up appropriately.

Hi! Indeed, hiding this function behind a feature (and improving the doc) sounds like a great idea!
In theory it may be possible to dynamically link to zstd and only discover at runtime if multithreading is enabled, but in practice I think it's safe to only support the usual static linking, especially in the top-level zstd crate (zstd-safe should still be able to use this flag, regardless of cargo features).


DeprecationWarning on import imp

/Users/peterbe/virtualenvs/recipe-server/lib/python3.6/site-packages/configurations/importer.py:1: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  import imp

It's referring to this line

Thanks for the report.
Please consider providing a PR to fix it, please.

Interesting, as of today, there is no such warning anymore:
$ python
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import configurations.importer
>>>

Though, the imp module is officially deprecated, hence it makes sense to replace the import. Unfortunately, the feature set of importlib is different from Python 2.7 to Python 3 (no find_module and load_module in Python 2), which requires a version check for the import. :unamused:
PR #212 is related to this issue, but it doesn't seem to be a real fix.

@bittner
You have to enable the warning.
% python -W error
Python 3.7.1 (default, Oct 22 2018, 10:41:28)
[GCC 8.2.1 20180831] on linux
Type "help", "copyright", "credits" or "license" for more information.
Using histfile /home/user/.python_history (via pythonrc)
>>> import configurations.importer
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "…/Vcs/django-configurations/configurations/importer.py", line 1, in <module>
    import imp
  File "/usr/lib/python3.7/imp.py", line 33, in <module>
    DeprecationWarning, stacklevel=2)
DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses

Replacing imp is fairly tricky. Too much has changed. Also, I'm not totally sure what ConfigurationImporter.find_module and ConfigurationLoader.load_module are doing. Whether it needs to be that complicated.
I found a related issue, though, where it's possible to simplify the current code. (PR #222)

Looks like it might be possible to take some inspiration from how importhook works and/or take it as a dependency perhaps.

This has been resolved in #365


Exclude "not-contenteditable" children from counting selection position of "contenteditable" parent

Looks like it will help with #422

It's the same things. I'll close #422 in favor of this issue


github: remove CentOS6 PR check

To avoid confusion and not put off potential contributors we should remove this check for now until https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1745 is resolved.
Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
Checklist

[x] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] inventory changes, ensure bastillion is updated accordingly

My only concern with this is that it's what is used to update the docker images for the builds.

My only concern with this is that it's what is used to update the docker images for the builds.

There looks to be actions in there associated with PRs and pushes - is the push executed when it's merged? [NOTE: Original PR had the wrong but comented out - have adjusted to leave it on push] Otherwise aren't we pushing and updating the image on every PR creation regardless of whether it's approved?
Either way, presumably at the moment it's unable to update so is fundamentally non-functional right now and only leading to confusion?

wasn't there a proposed fix coming from Will?

I believe you're referring to https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/1765/files which has already been merged and does not appear to have fixed the issue in the github checks.
@Willsparker are you still looking at a further fix?

That only solves part of the problem. See https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1745
The same sed change needs to be done on the SCL repo - but due to that being added in the playbook, it needs to be an ansible task too.

@Willsparker Is that something which can be resolved soon or should we land this instead?

I'll have it done by today :-)

As of #1780, the CentOS6 PR check works. (VPC also shows that the C6 playbook is working on a vagrant VM, too). Closing this as it's unnecessary now :-)


Better Temp file management

I wold like to request for better temp file cashing management.
It just fills up my ubuntu 20.04 temp folder.
If storage fills up it should get rid of previously cashed files.
It should delete data that was saved during a cycle under a new cycle's same variable name.

Hello @stromal, thanks for reporting!
Do you have any more data you can provide on those files filling up the /tmp? I'm assuming you're talking about Ray files, but would like to confirm that. Would be helpful if you can share at least file names there.

yep ray files. I got rid of them and switched off the whole pipeline now. I did not save down the error message but it was like 99% CPU utilization on a 32 thread AWS EC2 instance.

@vnlitvinov
Warning messages similar to this but with 100% CPU, it have crashed at the end and my storage was at 100%
distributed.utils_perf - WARNING - full garbage collections took 93% CPU time recently (threshold: 10%)
distributed.utils_perf - WARNING - full garbage collections took 93% CPU time recently (threshold: 10%)

@stromal, those warning messages should come from dask.distributed. Could you clarify what Modin engine are you using and what Ray files are you seeing?

@pyrito I can not put more resources in this. Just make sure that RAY gets rid of the same name variables from it's cash when it generates it's temp files (I got a temp file that was +200 GB, 100% filled up my storage and crashed the whole Ubuntu 20.04 server.)

@stromal I need some more context. Can you show what files are in tmp/?

@pyrito  that is my issue it takes a long time to reproduce the error.
It just pushes out this 100% CPU nonsense and the ssd is at 100% in the ubuntu hidden  tmp directory.
I holder many dataframes with the same name because it went thru for cycles.
If I have time I will let you know here.

@stromal thanks for the context. The distributed.utils_perf thing that you are seeing are not from Ray, but Dask. Can you confirm what Modin engine you are using?

@pyrito I get back to you tomorrow with that.

Versions:

conda version : 4.6.14
Python 3.7.12
modin version: 0.12.1

I have tried installing different modin versions they all crash this is the only package combination that actually functioned:

https://github.com/modin-project/modin/issues/4906
https://github.com/modin-project/modin/issues/4719


Ajax - method parameters not passed

Hey.
I have following components in my source:
Controller:
[HttpGet]
[HttpPost]
 public PartialViewResult Grid(string name)
{
    return PartialView("_CarsGrid",
       *GetModel*);
}

_CarsGrid.cshtml:
...
@Html.Grid(Model).Build(columns =>
{
...
}).Pageable(pager =>
{ pager.RowsPerPage = 1; })

List.cshtml:
<!DOCTYPE html>

<html>
<head>
    <link rel="stylesheet" href="~/css/mvc-grid.css" />
</head>
<body>
    @Html.AjaxGrid(Url.Action("Grid"))

    <script src="~/js/jquery.min.js" type="text/javascript"></script>
    <script src="~/js/mvc-grid.js" type="text/javascript"></script>
    <script>
        $('.content-refresh').on('click', function () {
            $('.mvc-grid').mvcgrid({
                requestType: 'post', // defaults to get
                reload: true,
                data: {
                    name: 'Joe'
                }
            });
        });
    </script>
    <script>
        $('.mvc-grid').mvcgrid();
    </script>
</body>
</html>

If I refresh browser page (or turn to other grid page), method Grid is called on the controller, but name parameter isn't passed to the method.
The parameter seems to be not even send to the controller.
Is there any mistake in my code that I cannot find? I walked through steps in tutorial many times, but it's never started working.
Thx.

This is expected behavior. You refresh the page, you lose all the state it had, unless you save it somehow.
If you still have that data on the page after the refresh you can pass it to the grid on the first initialization.
So instead of
.mvcgrid()

do
.mvcgrid({
    requestType: 'post', // defaults to get
    data: {
        name: 'Joe'
    }
})

and it should work after refresh.

It works, thank you very much.
Is there any recommended approach to pass complex parameters to the method? For example to pass the data parameter in request body?
Currently I use this:
var filter = @Json.Serialize(Model.Filter);

    $('.mvc-grid').mvcgrid({
        data: {
            "filter.BrandId": filter.brandId,
            "filter.ModelId": filter.modelId
        }
    });

    $('.content-refresh').on('click', function () {
        $('.mvc-grid').mvcgrid({
            reload: true,
            data: {
                "filter.BrandId": filter.brandId,
                "filter.ModelId": filter.modelId
            }
        });
    });

Never used complex models for grid filtering, so I can't say for sure.
But wouldn't it be simpler if your grid action took the filter parameter itself?
That way you could probably inline the json data, like so?
$('.mvc-grid').mvcgrid({
  data: filter
});

It works. Thanks.


Add onlyif option to postgresql_psql type

This adds an onlyif option to the postgresql_psql type to allow for commands to only run if the onlyif command succeeds. The primary use case being to only add a table grant if the table exists (if for example, the tables are managed outside of puppet but the grants are managed within puppet).

Hi @kimor79 , could you rebase this against the current master and squash it down to a single commit?

Closing due to #606

Sorry, haven't had a chance to look at this in a long while.

ping @kimor79  ?

I have no idea if I did the rebase correctly. How do I squash if I'm not the one merging into master?

Squashing commits
git log --pretty=oneline
To squash the last 2 commits
git rebase --interactive HEAD~2
The read the text, and save. You can view the squash with the log command.
git push -f origin destination_branch

pulled locally and rebased and merged c4c0402bd424dbedc5ccfee85e3dcf566c1d5829


Attach to PID does not process "Initial Commands" before attaching

The current method used to attach to a process on the local machine is to specify the PID on the command line to the debugger.  However, by doing this, the debugger will attach to the process prior to executing the initial configuration commands (specified in MI2::initCommands).  This is inconsistent with remote attach operations (using target-select remote or target-select extended-remote) which only attach to the remote process after the initial configuration commands have been processed.
The problem with attaching prior to processing the initial configuration commands is that there can be spurious errors that occur because of this.  For example, if a source path mapping is needed to resolve the source code, when the debugger attaches to the process, it will attempt to locate the source file, but won't be able to find it because the source path mappings commands have not yet been processed.  Additionally, this can also lead to errors attempting other commands, such as gdb-set target-async on failing with "Cannot change this setting while the inferior is running".
The below output demonstrates both the source path mapping issue as well as the issue with the failing gdb-set target-async on command.  I'd suggest that the current behavior be changed to process the initial configuration commands first, and then issue a "target-attach" command afterwards to attach to the local process.
1-gdb-set target-async on
2-list-features
3-environment-directory "/home/troy/git/hello_world_exe"
4-gdb-set substitute-path "C:\\usr\\src" "/home/troy/git/hello_world_exe/../hello_world_c"
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"thread-group-added","output":[["id","i1"]]}]}
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Attaching to process 7801\n"}]}
Attaching to process 7801
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"thread-group-started","output":[["id","i1"],["pid","7801"]]}]}
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"thread-created","output":[["id","1"],["group-id","i1"]]}]}
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Reading symbols from /home/troy/git/hello_world_exe/hello_world-gcc..."}]}
Reading symbols from /home/troy/git/hello_world_exe/hello_world-gcc...
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"done.\n"}]}
done.
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"library-loaded","output":[["id","/lib/x86_64-linux-gnu/libc.so.6"],["target-name","/lib/x86_64-linux-gnu/libc.so.6"],["host-name","/lib/x86_64-linux-gnu/libc.so.6"],["symbols-loaded","0"],["thread-group","i1"],["ranges",[[["from","0x00007f8d2b173360"],["to","0x00007f8d2b2ebafc"]]]]]}]}
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"library-loaded","output":[["id","/lib64/ld-linux-x86-64.so.2"],["target-name","/lib64/ld-linux-x86-64.so.2"],["host-name","/lib64/ld-linux-x86-64.so.2"],["symbols-loaded","0"],["thread-group","i1"],["ranges",[[["from","0x00007f8d2b543f10"],["to","0x00007f8d2b564550"]]]]]}]}
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Reading symbols from /lib/x86_64-linux-gnu/libc.so.6..."}]}
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libc-2.27.so..."}]}
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libc-2.27.so...
5-thread-info
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"done.\n"}]}
done.
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"done.\n"}]}
done.
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Reading symbols from /lib64/ld-linux-x86-64.so.2..."}]}
Reading symbols from /lib64/ld-linux-x86-64.so.2...
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/ld-2.27.so..."}]}
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/ld-2.27.so...
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"done.\n"}]}
done.
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"done.\n"}]}
done.
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"console","content":"main () at hello_world.c:6\n"}]}
main () at hello_world.c:6
GDB -> App: {"outOfBandRecord":[{"isStream":true,"type":"log","content":"6\thello_world.c: No such file or directory.\n"}]}
6	hello_world.c: No such file or directory.
GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"exec","asyncClass":"stopped","output":[["frame",[["addr","0x00005615fb5f864a"],["func","main"],["args",[]],["file","hello_world.c"],["fullname","C:\\usr\\src/hello_world.c"],["line","6"]]],["thread-id","1"],["stopped-threads","all"],["core","5"]]}]}
GDB -> App: {"token":1,"outOfBandRecord":[],"resultRecords":{"resultClass":"error","results":[["msg","Cannot change this setting while the inferior is running."]]}}
WARNING: Error executing command 'gdb-set target-async on'
GDB -> App: {"token":2,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["features",["frozen-varobjs","pending-breakpoints","thread-info","data-read-memory-bytes","breakpoint-notifications","ada-task-info","language-option","info-gdb-mi-command","undefined-command-error-code","exec-run-start-option","python"]]]}}
GDB -> App: {"token":3,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["source-path","/home/troy/git/hello_world_exe:$cdir:$cwd"]]}}
GDB -> App: {"token":4,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[]}}
GDB -> App: {"token":5,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["threads",[[["id","1"],["target-id","process 7801"],["name","hello_world-gcc"],["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["args",[]],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]],["state","stopped"],["core","5"]]]],["current-thread-id","1"]]}}
6-thread-info
GDB -> App: {"token":6,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["threads",[[["id","1"],["target-id","process 7801"],["name","hello_world-gcc"],["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["args",[]],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]],["state","stopped"],["core","5"]]]],["current-thread-id","1"]]}}
7-stack-info-depth --thread 1
8-stack-info-depth --thread 1
GDB -> App: {"token":7,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["depth","1"]]}}
GDB -> App: {"token":8,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["depth","1"]]}}
9-stack-list-frames --thread 1 0 0
10-stack-list-frames --thread 1 0 0
GDB -> App: {"token":9,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["stack",[["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]]]]]}}
GDB -> App: {"token":10,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["stack",[["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]]]]]}}
11-thread-info
GDB -> App: {"token":11,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["threads",[[["id","1"],["target-id","process 7801"],["name","hello_world-gcc"],["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["args",[]],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]],["state","stopped"],["core","5"]]]],["current-thread-id","1"]]}}
12-thread-info
GDB -> App: {"token":12,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["threads",[[["id","1"],["target-id","process 7801"],["name","hello_world-gcc"],["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["args",[]],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]],["state","stopped"],["core","5"]]]],["current-thread-id","1"]]}}
13-stack-info-depth --thread 1
GDB -> App: {"token":13,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["depth","1"]]}}
14-stack-list-frames --thread 1 0 0
GDB -> App: {"token":14,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["stack",[["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]]]]]}}
15-stack-info-depth --thread 1
GDB -> App: {"token":15,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["depth","1"]]}}
16-stack-list-frames --thread 1 0 0
GDB -> App: {"token":16,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["stack",[["frame",[["level","0"],["addr","0x00005615fb5f864a"],["func","main"],["file","hello_world.c"],["fullname","/home/troy/git/hello_world_c/hello_world.c"],["line","6"]]]]]]}}
17-stack-list-variables --thread 1 --frame 0 --simple-values
GDB -> App: {"token":17,"outOfBandRecord":[],"resultRecords":{"resultClass":"done","results":[["variables",[]]]}}

That is actually a duplicate as we did had that "side-noted" multiple times, but it is the most expressive ones so is the one this is to be tracked under.
To solve it (ideally after #316 - please feel free to comment on this actually untested change) I'd also suggest to change the setup to a plain load, then "attach". I'd welcome a PR (maybe a combined with with the changes of #316? in this case we can close that and use another one instead). Can you self-assign this issue (upper-right corner) to yourself? If not, may I do that?
Note: we only do the -p if there is no executable specified and some of the initial commands may need an executable loaded already (I'd need to check, don't know).

Ah, ok, I'm sure I probably missed that it was already documented in one of the previous issues.  I happened to stumble upon it and dug into it a bit to understand what has happening.  Can you link the other issues to this one if this will be the place where we fix it?
I don't think I can assign this to myself (as I'm not a Collaborator, only Contributor).  However, I'd be fine if you assigned to this me.
I'll take a look at #316.  Probably makes sense to finish that one first and then start on this one separately.  It does looks like there would be some overlap of the affected source, but probably would be good keep the issues separate if possible.

It was only a "side note" in other issues, when I stumble over one I'll reference this one there.
Thank you for looking into this and #316.

@brownts is this still open? Looks like "kind of related" to the other nice work you've did.

Yes, this is still open.  I was trying to push through a few of the other issues and PRs that were already in work.  This was going to be the next thing I took a look at.  It will require a change to both the MI2::attach and MI2::ssh.

Thanks for your work on this extension, it helps a lot!

@brownts would you also like to have collaborator access?

@brownts would you also like to have collaborator access?

Sure, that would be wonderful! :+1:


vue3 预览pdf出现白屏

vue3 预览pdf出现白屏

Hi @leishenws,
I guess you're using the essential build, thus you must either switch to the regular build or use the v3.11.174 worker (as it comes from the error message).


Transactions should be editable

I have set up a draft PR for this with the callbacks you can use for submitting the update form.
#115.


Dialog hide and then show after returning from background

How disable show dialog after returning to the app from background?

Hello @Secretbox1987,
If you don't what to, you just need to dismiss the bottom sheet when the app is resumed from the caller of the sheet. Example:
val findFragmentByTag = supportFragmentManager.findFragmentByTag("DemoBottomSheetFragment")
        (findFragmentByTag as AppCompatDialogFragment).dismiss()


[IGNORE] Ensure unique ids are used in legend

When testing with a migrated Node Exporter dashboard locally (JSON here), I saw this warning in the console related to our legend:

This PR ensures that the keys will always been unique.
Checklist

[x] Pull request has a descriptive title and context useful to a reviewer.
[x] Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, IGNORE.
[x] All commits have DCO signoffs.

UI Changes

[x] Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
[x] Code follows the UI guidelines.

Hmm, I thought I was hardcoding all the right values for those happo stories not to be flaky. You can ignore them for the purposes of this PR and I'll look into what's happening there.

Fix for the flakiness in https://github.com/perses/perses/pull/1092
I also think there's something weird happening with the storybook caching that I'll debug after lunch. I tried to make a separate branch based on yours to reproduce that, but I think it might've messed up your github actions for this PR. I closed it to avoid future impact on this one and will debug separately. Sorry for the headaches there!


matrix-synapse: 0.28.1 -> 0.30.0

Motivation for this change
Mainly some new features for getting GDPR consent of users: https://matrix.org/blog/2018/05/24/synapse-0-30-0-released-today/
Note: For some reason running the tests don't work on my machine, could someone who can do that initiate running them through @GrahamcOfBorg ?
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg test matrix-synapse

Success on x86_64-linux (full log)
Attempted: tests.matrix-synapse
Partial log (click to expand)
server_postgres: exit status 0
server_sqlite: running command: sync
server_sqlite: exit status 0
test script finished in 54.27s
cleaning up
killing server_postgres (pid 593)
killing server_sqlite (pid 605)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/dvnacnm4ws18gjasis9ajhhqn8rfmksa-vm-test-run-matrix-synapse

Success on aarch64-linux (full log)
Attempted: tests.matrix-synapse
Partial log (click to expand)
server_sqlite: exit status 0
server_postgres: running command: sync
server_postgres: exit status 0
test script finished in 100.14s
cleaning up
killing server_sqlite (pid 627)
killing server_postgres (pid 640)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/vdnv3hzfys80kc3khka323vccnjyfahm-vm-test-run-matrix-synapse

Can we backport that to stable at least as an optional package? GDPR compliance could be a very important feature. @xeji


Internal launch timed out and terminated

2020-10-09 20:00:22.213230: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-10-09 20:00:22.243996: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.244526: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce 920M computeCapability: 3.5
coreClock: 0.954GHz coreCount: 2 deviceMemorySize: 1.96GiB deviceMemoryBandwidth: 14.92GiB/s
2020-10-09 20:00:22.244886: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-10-09 20:00:22.246939: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-10-09 20:00:22.248872: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-10-09 20:00:22.249439: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-10-09 20:00:22.251486: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-10-09 20:00:22.252804: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-10-09 20:00:22.257173: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-10-09 20:00:22.257405: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.258014: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.258479: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
(4834, 21, 5)
(538, 21, 5)
2020-10-09 20:00:22.663431: I tensorflow/core/profiler/lib/profiler_session.cc:159] Profiler session started.
2020-10-09 20:00:22.663497: I tensorflow/core/profiler/internal/gpu/cupti_tracer.cc:1363] Profiler found 1 GPUs
2020-10-09 20:00:22.664240: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcupti.so.10.1
2020-10-09 20:00:22.665489: I tensorflow/core/profiler/internal/gpu/cupti_tracer.cc:1479] CUPTI activity buffer flushed
2020-10-09 20:00:22.678966: I tensorflow/core/platform/cpu_feature_guard.cc:143] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2020-10-09 20:00:22.684542: I tensorflow/core/platform/profile_utils/cpu_utils.cc:102] CPU Frequency:<PHONE_NUMBER> Hz
2020-10-09 20:00:22.684806: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x558bf28f53e0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-10-09 20:00:22.684835: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-10-09 20:00:22.685094: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.685482: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce 920M computeCapability: 3.5
coreClock: 0.954GHz coreCount: 2 deviceMemorySize: 1.96GiB deviceMemoryBandwidth: 14.92GiB/s
2020-10-09 20:00:22.685564: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-10-09 20:00:22.685607: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-10-09 20:00:22.685631: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-10-09 20:00:22.685653: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-10-09 20:00:22.685676: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-10-09 20:00:22.685698: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-10-09 20:00:22.685721: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-10-09 20:00:22.685813: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.686221: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.686534: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-10-09 20:00:22.686597: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-10-09 20:00:22.765993: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-10-09 20:00:22.766040: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1108]      0
2020-10-09 20:00:22.766058: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] 0:   N
2020-10-09 20:00:22.766352: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.766933: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.767337: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-09 20:00:22.767749: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1247] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 1757 MB memory) -> physical GPU (device: 0, name: GeForce 920M, pci bus id: 0000:01:00.0, compute capability: 3.5)
2020-10-09 20:00:22.769944: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x558bf65bd9f0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-10-09 20:00:22.769984: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce 920M, Compute Capability 3.5
2020-10-09 20:00:25.217767: E tensorflow/stream_executor/cuda/cuda_event.cc:29] Error polling for event status: failed to query event: CUDA_ERROR_LAUNCH_TIMEOUT: the launch timed out and was terminated
2020-10-09 20:00:25.217849: F tensorflow/core/common_runtime/gpu/gpu_event_mgr.cc:273] Unexpected Event status: 1
Aborted (core dumped)
Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Manjaro 20.1.1
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): 2.2
Python version: 3.8.3
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 11.0/7.6
GPU model and memory: Nvidia 920m / 2GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Describe the expected behavior
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

tested with tensorflow v2.3.0-rc2-23-gb36436b087 2.3.0
same error

Issue resolved by downgrading the display driver to v435


Out of memory when toggling cameras on and off repeatedly

We were getting out of memory issues on xbox when objects with HDCameraUI on them were toggled on and off frequently (on opening and closing our pause menu for example). This doesn't happen in editor seemingly, but maybe I just had more memory available.
I presume the issue is that internalRenderTexture gets newed OnEnable every time, so the old texture is orphaned and wasn't getting cleaned up automatically (at least on xbox). Moving as much of the OnEnable functionality as possible into Start seems to have fixed the issue, however it also doesn't seem ideal that once you turn a HDCameraUI component on then it holds on to a screen sized buffer for the entirety of its lifetime (and then possibly leaks it once it's destroyed if that is what was happening before), so I also made changes to release the RenderTexture on Disable/Destroy.
void Start()
{
    data = GetComponent<HDAdditionalCameraData>();
    attachedCamera = GetComponent<Camera>();

    if (data == null)
        return;

    data.customRender -= StoreHDCamera;
    data.customRender += StoreHDCamera;

    // TODO: Add VR support
    internalRenderTexture = new RenderTexture(1, 1, 0, graphicsFormat, 1);
    internalRenderTexture.dimension = TextureDimension.Tex2DArray;
    internalRenderTexture.volumeDepth = 1;
    internalRenderTexture.depth = 24;
    internalRenderTexture.name = "HDCameraUI Output Target";

    cullingSampler = new ProfilingSampler("UI Culling");
    renderingSampler = new ProfilingSampler("UI Rendering");
    uiCameraStackingSampler = new ProfilingSampler("Render UI Camera Stacking");
    copyToCameraTargetSampler = new ProfilingSampler("Copy To Camera Target");
    initTransparentUIBackgroundSampler = new ProfilingSampler("Init Transparent UI Background");

    if (blitWithBlending == null)
        blitWithBlending = Shader.Find("Hidden/HDRP/UI_Compositing");
    if (blitInitBackground == null)
        blitInitBackground = Shader.Find("Hidden/HDRP/InitTransparentUIBackground");

    CameraStackingCompositing.uiList.Add(this);
}

void OnEnable()
{
    if (data == null)
        return;

    data.customRender -= StoreHDCamera;
    data.customRender += StoreHDCamera;

    CameraStackingCompositing.uiList.Add(this);
}

void OnDisable()
{
    if (data == null)
        return;

    data.customRender -= StoreHDCamera;
    CameraStackingCompositing.uiList.Remove(this);
    if(internalRenderTexture.IsCreated()) internalRenderTexture.Release();
    internalRenderTexture.width = 1;
    internalRenderTexture.height = 1;
}

private void OnDestroy()
{
    OnDisable();
}

Hello,
That's a very good catch! I think adding a Release of the RenderTexture in the OnDisable should be enough to fix the issue.
I pushed the chages in this commit: https://github.com/alelievr/HDRP-UI-Camera-Stacking/commit/72de05246e5a1b3824e5dab694b28531adf86c1e let me know if that fixes the issue. I've seen a pretty weird behavior where after a Release(), the C# RenderTexture handle is still treated as "alive" but it shouldn't take too much memory since it was release on C++ side which contains the actual data of the RenderTexture. Calling Resources.UnloadUnusedAssets seems to clear these handles.


Enhanced LXQt DE Support

Couldn't find version info in any files, so this is as slow as it gets...

It fetches 3 versions
lxqt-session 0.17.1
liblxqt   0.17.0
Qt        5.15.2

Somehow github is broken so i have to comment this way.
In code:
ffStrbufSubstrAfter(&result->deVersion, result->deProcessName.length);
ffStrbufSubstrBefore(&result->deVersion, 6); //X.XX.X

This is unsave. I just installed LXQT for testing the PR and i get the following output:
"Icon Theme not set. Fallbacking to Oxygen, if installed"
lxqt-session 0.17.1
liblxqt   0.17.0
Qt        5.15.2

You will need to to some more advanced parsing. Maybe loop through it like i do here: https://github.com/LinusDierheimer/fastfetch/blob/8af1cde10b2be86c486efcb38ed2ab43a9302b10/src/modules/disk.c#L118 or here: https://github.com/LinusDierheimer/fastfetch/blob/8af1cde10b2be86c486efcb38ed2ab43a9302b10/src/common/init.c#L27 just use '\n' as the seperator and not ':'. You can than use ffGetPropValue on each line.
It installed a lot of files with the version 0.17.0 on my system. /usr/share/cmake/lxqt/lxqt-*.cmake look promising. Maybe we should fallback to that if slow operations are not allowed.

Hm. Didn't know --version outputs even more garbage....
Yes, I looked at the cmake files after this commit. If they are there for everyone, we should probably use those. The main LXQt About dialog also shows version as 0.17.0.
lxqt-config.cmake: set(LXQT_VERSION            "0.17.0")
I'll rewrite it.

Your latest commits made this very easy. :+1:
I went with checking the liblxqt version, as that seems to be more accurate the lxqt-session.


ZEPPELIN-1459: Zeppelin JDBC URL properties mangled

What is this PR for?
While creating connection DriverManager.getConnection(url, properties); for JDBC interpreter, phoenix driver is modifying the properties that is passed as parameter, which in modifies propertiesMap.
This all is resulting in, not able to execute any other paragraph with phoenix interpreter.
This only happens if JDBC URI is "jdbc:phoenix:thin:url"
What type of PR is it?
[Bug Fix]
Todos

[x] - Pass a copy of properties to DriverManager.getConnection(url, properties)

What is the Jira issue?

ZEPPELIN-1459

How should this be tested?
Use the example setting below
https://issues.apache.org/jira/browse/ZEPPELIN-1459?focusedCommentId=15505750&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15505750
Screenshots (if appropriate)
Questions:

Does the licenses files need update? n/a
Is there breaking changes for older versions? n/a
Does this needs documentation? n/a

I tested the PR and it works as expected. Thanks @prabhjyotsingh!

Thank you @randerzander, will merge this soon.


ABBA

Hi @NduatiWambugu, Please don't modify existing values in application.properties while sending PR.
But, you are free to add new properties.


Added Code Of Coduct file

Added Code-Of-Conduct file that includes "A Code of Conduct for Open Source Communities".

Next - time pls create the issue and the branch for the same and then merge the pr

Next - time pls create the issue and the branch for the same and then merge the pr

Sure. Will work on that. Thanks for the information.


Prime general-purpose allocator caches with known sizes.

This change will pre-populate (but not allocate) allocator-internal caches with predefined sizes (power-of-twos) to eliminate the first request latency (cold request).

Fixed #149


Export native not working in 0.29.3

export native is not working anymore in version 0.29.3. export html works correctly.
Version 0.29.2 works as expected also. Win10.

also folder command doesn't work

fixed in .30


pvpanic, qemufwcfg, and qemupciserial are self signed with a bad basic constraint

Describe the bug
The drivers for pvpanic, qemufwcfg, and qemupciserial in virtio-win 0.1.217 are signed with a self signed certificate. As well as this it has a CA constraint set which stops you from importing the self signed cert as a trusted root authority and then installing the driver.
Here is the certificate used for pvpanic as a PEM file
-----BEGIN CERTIFICATE-----
MIIFfzCCA2egAwIBAgIQ71SLoHAVzrtEjztcjLJ7iTANBgkqhkiG9w0BAQsFADA6MRMwEQYDVQQK
Ewp2aXJ0aW8td2luMQwwCgYDVQQLEwNEZXYxFTATBgNVBAMTDFJlZCBIYXQgSW5jLjAeFw0yMjAx
MTMxMTE5MjdaFw0zOTEyMzEyMzU5NTlaMDoxEzARBgNVBAoTCnZpcnRpby13aW4xDDAKBgNVBAsT
A0RldjEVMBMGA1UEAxMMUmVkIEhhdCBJbmMuMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKC
AgEAxMvr0k21d+COYanxQfDBZNyp9clJWg3Fh9S9ty0npM+EZIjUyN+Psr83/Ln5NMgUPpNSmRjX
FwNJ+/31swPHm4+QpUbl2iyF8Lj9c4g85APu9dJD6i3Hma86lO+rpUVmuQnklO/9H2ee2Ss1qCoX
HyLsQC54mqpC7awe0TBEszoGN86eiHO2Sl/HvmxgEMxtiQIHcZ+YR4bdASWc7EWcv8MPaznb8yEy
kYCxY0nQG/24ecrNUn9+sLmvrnPwE6Lrl7sAK3quUmK9Zl0gElY4eJi01xHyXlgxsaDtv7IsPf3U
LR2vHRb65ZzIbURro7EOYoB8ggYCGQB8UDG2uow0LYmDlBC2+HCSqia8DYYOKMB9DzKv2Pa0lpzl
R4N7npfxW0xPfOWYfafZM0s4yNE043eAx1VAe3GTfdRHIkRMH4CevT1CqvcEFa9MLELZUIS/RECc
rpnvg5pEhE6IICE4geJO9zFYxRDk3zO2lN2RlYNVOeLLqV9qY4LXxNEP1AuLC1YM1R0NxXxnFh78
GJY4O7/9D+P8W1yWI6+7YIDJOWDH+1HTG+3S+oTVC6snNqqTlLSQG/GfU3CTS0jc6Qca20srQGvf
rP5SuVCF0oXTKMX9Nea3U6L8CpUz8EYnpCcc0VlKUuLDeeI9osjvu5lxBYPbrmBHRUXKI6XBPvym
yvECAwEAAaOBgDB+MA8GA1UdEwEB/wQFMAMBAf8wawYDVR0BBGQwYoAQzPQihzig+fTivgwwp5O1
EKE8MDoxEzARBgNVBAoTCnZpcnRpby13aW4xDDAKBgNVBAsTA0RldjEVMBMGA1UEAxMMUmVkIEhh
dCBJbmMughDvVIugcBXOu0SPO1yMsnuJMA0GCSqGSIb3DQEBCwUAA4ICAQA9gaMgb0HuI+CzFqcP
KeKx5B/MWX05CJWu/Th8gpAQxDjP2XKDdj+BE9qjY1mNdebAFEl1ITib+0LBo6COTVd8o+NBOkcy
anV88MPa/Gwkhp7/AKYIYrwXQJl9cGdt3jBKqO8bDtU0Vrv5PvWQTz1Fv8JDHsIZLxqf5RLSFAag
khDaTF2vxr8Nwkzgmt9/u/aLSrVHFBbXoScKt82TWgtbfBK99Pz8XDnojH28cFszAp4hW11o9J8Z
94iWbkfPGUCtX9JREFWyykcZGfb6Isln2pdvOrPKBWp9vQvHnGln2tvkQ05vcUbTNz/laHLYq38v
AoAu2m74u63GK0hIMygMMW9wz3fiAwyNmQ+/EHSQYXSlBojYVUoM8EcceXSBHsxcDp2Ht+e0Zzbs
uaZsXADWkNefzVPAG+T2hFeyo9C4UCI2mn3to3ZA+i08dcLpz4XnTklZ740XeTIC9arJMR52r1T4
qM6UTUQPxUOeAho+wcpKfEVqWu1bRe+gocJbWv8FkpLvgBqUSrh0x0iGy4ohO9mXwdFjrdxiWKuh
Ffl70/zzu3BWlPSwd6D4S1oNWWDquSMhSejg3KLxdEWfMrQ+f26YBQYhEHcCSgAynwk3I5kKsiyb
NlAIWKPLwIZ00D2NW+OUTihDnuTdEuL7TUz5RFqd3orEsHVtSgjOhoX7UA==
-----END CERTIFICATE-----

The contents decoded by OpenSSL are
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
             (Negative)10:ab:74:5f:8f:ea:31:44:bb:70:c4:a3:73:4d:84:77
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: O = virtio-win, OU = Dev, CN = Red Hat Inc.
        Validity
            Not Before: Jan 13 11:19:27 2022 GMT
            Not After : Dec 31 23:59:59 2039 GMT
        Subject: O = virtio-win, OU = Dev, CN = Red Hat Inc.
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (4096 bit)
                Modulus:
                    00:c4:cb:eb:d2:4d:b5:77:e0:8e:61:a9:f1:41:f0:
                    c1:64:dc:a9:f5:c9:49:5a:0d:c5:87:d4:bd:b7:2d:
                    27:a4:cf:84:64:88:d4:c8:df:8f:b2:bf:37:fc:b9:
                    f9:34:c8:14:3e:93:52:99:18:d7:17:03:49:fb:fd:
                    f5:b3:03:c7:9b:8f:90:a5:46:e5:da:2c:85:f0:b8:
                    fd:73:88:3c:e4:03:ee:f5:d2:43:ea:2d:c7:99:af:
                    3a:94:ef:ab:a5:45:66:b9:09:e4:94:ef:fd:1f:67:
                    9e:d9:2b:35:a8:2a:17:1f:22:ec:40:2e:78:9a:aa:
                    42:ed:ac:1e:d1:30:44:b3:3a:06:37:ce:9e:88:73:
                    b6:4a:5f:c7:be:6c:60:10:cc:6d:89:02:07:71:9f:
                    98:47:86:dd:01:25:9c:ec:45:9c:bf:c3:0f:6b:39:
                    db:f3:21:32:91:80:b1:63:49:d0:1b:fd:b8:79:ca:
                    cd:52:7f:7e:b0:b9:af:ae:73:f0:13:a2:eb:97:bb:
                    00:2b:7a:ae:52:62:bd:66:5d:20:12:56:38:78:98:
                    b4:d7:11:f2:5e:58:31:b1:a0:ed:bf:b2:2c:3d:fd:
                    d4:2d:1d:af:1d:16:fa:e5:9c:c8:6d:44:6b:a3:b1:
                    0e:62:80:7c:82:06:02:19:00:7c:50:31:b6:ba:8c:
                    34:2d:89:83:94:10:b6:f8:70:92:aa:26:bc:0d:86:
                    0e:28:c0:7d:0f:32:af:d8:f6:b4:96:9c:e5:47:83:
                    7b:9e:97:f1:5b:4c:4f:7c:e5:98:7d:a7:d9:33:4b:
                    38:c8:d1:34:e3:77:80:c7:55:40:7b:71:93:7d:d4:
                    47:22:44:4c:1f:80:9e:bd:3d:42:aa:f7:04:15:af:
                    4c:2c:42:d9:50:84:bf:44:40:9c:ae:99:ef:83:9a:
                    44:84:4e:88:20:21:38:81:e2:4e:f7:31:58:c5:10:
                    e4:df:33:b6:94:dd:91:95:83:55:39:e2:cb:a9:5f:
                    6a:63:82:d7:c4:d1:0f:d4:0b:8b:0b:56:0c:d5:1d:
                    0d:c5:7c:67:16:1e:fc:18:96:38:3b:bf:fd:0f:e3:
                    fc:5b:5c:96:23:af:bb:60:80:c9:39:60:c7:fb:51:
                    d3:1b:ed:d2:fa:84:d5:0b:ab:27:36:aa:93:94:b4:
                    90:1b:f1:9f:53:70:93:4b:48:dc:e9:07:1a:db:4b:
                    2b:40:6b:df:ac:fe:52:b9:50:85:d2:85:d3:28:c5:
                    fd:35:e6:b7:53:a2:fc:0a:95:33:f0:46:27:a4:27:
                    1c:d1:59:4a:52:e2:c3:79:e2:3d:a2:c8:ef:bb:99:
                    71:05:83:db:ae:60:47:45:45:ca:23:a5:c1:3e:fc:
                    a6:ca:f1
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:TRUE
            <IP_ADDRESS>:
                0b....".8......0.....<0:1.0...U.
.
virtio-win1.0
..U....Dev1.0...U....Red Hat Inc....T..p...D.;\..{.
    Signature Algorithm: sha256WithRSAEncryption
         3d:81:a3:20:6f:41:ee:23:e0:b3:16:a7:0f:29:e2:b1:e4:1f:
         cc:59:7d:39:08:95:ae:fd:38:7c:82:90:10:c4:38:cf:d9:72:
         83:76:3f:81:13:da:a3:63:59:8d:75:e6:c0:14:49:75:21:38:
         9b:fb:42:c1:a3:a0:8e:4d:57:7c:a3:e3:41:3a:47:32:6a:75:
         7c:f0:c3:da:fc:6c:24:86:9e:ff:00:a6:08:62:bc:17:40:99:
         7d:70:67:6d:de:30:4a:a8:ef:1b:0e:d5:34:56:bb:f9:3e:f5:
         90:4f:3d:45:bf:c2:43:1e:c2:19:2f:1a:9f:e5:12:d2:14:06:
         a0:92:10:da:4c:5d:af:c6:bf:0d:c2:4c:e0:9a:df:7f:bb:f6:
         8b:4a:b5:47:14:16:d7:a1:27:0a:b7:cd:93:5a:0b:5b:7c:12:
         bd:f4:fc:fc:5c:39:e8:8c:7d:bc:70:5b:33:02:9e:21:5b:5d:
         68:f4:9f:19:f7:88:96:6e:47:cf:19:40:ad:5f:d2:51:10:55:
         b2:ca:47:19:19:f6:fa:22:c9:67:da:97:6f:3a:b3:ca:05:6a:
         7d:bd:0b:c7:9c:69:67:da:db:e4:43:4e:6f:71:46:d3:37:3f:
         e5:68:72:d8:ab:7f:2f:02:80:2e:da:6e:f8:bb:ad:c6:2b:48:
         48:33:28:0c:31:6f:70:cf:77:e2:03:0c:8d:99:0f:bf:10:74:
         90:61:74:a5:06:88:d8:55:4a:0c:f0:47:1c:79:74:81:1e:cc:
         5c:0e:9d:87:b7:e7:b4:67:36:ec:b9:a6:6c:5c:00:d6:90:d7:
         9f:cd:53:c0:1b:e4:f6:84:57:b2:a3:d0:b8:50:22:36:9a:7d:
         ed:a3:76:40:fa:2d:3c:75:c2:e9:cf:85:e7:4e:49:59:ef:8d:
         17:79:32:02:f5:aa:c9:31:1e:76:af:54:f8:a8:ce:94:4d:44:
         0f:c5:43:9e:02:1a:3e:c1:ca:4a:7c:45:6a:5a:ed:5b:45:ef:
         a0:a1:c2:5b:5a:ff:05:92:92:ef:80:1a:94:4a:b8:74:c7:48:
         86:cb:8a:21:3b:d9:97:c1:d1:63:ad:dc:62:58:ab:a1:15:f9:
         7b:d3:fc:f3:bb:70:56:94:f4:b0:77:a0:f8:4b:5a:0d:59:60:
         ea:b9:23:21:49:e8:e0:dc:a2:f1:74:45:9f:32:b4:3e:7f:6e:
         98:05:06:21:10:77:02:4a:00:32:9f:09:37:23:99:0a:b2:2c:
         9b:36:50:08:58:a3:cb:c0:86:74:d0:3d:8d:5b:e3:94:4e:28:
         43:9e:e4:dd:12:e2:fb:4d:4c:f9:44:5a:9d:de:8a:c4:b0:75:
         6d:4a:08:ce:86:85:fb:50

You can verify that the issuer and subject match and the basic constraints has set CA:TRUE.
To Reproduce
Attempt to install one of these drivers on Windows will fail. The security details show the chain is not signed by a trusted root authority.

When manually trusting the cert by importing it into the root store it still fails due to the basic constraints being violated (CA cert being used as an end entity).

Expected behavior
The driver(s) to be installable like the other drivers in the virtio package, or even if self signed the basic constraints being set properly to allow it to be trusted and installed manually.
I'm unsure what the policy is behind signing these drivers and whether it is possible to sign these 3 like the rest of them but it should be possible to install these drivers somehow.
Screenshots
Added above in line where mentioned.
Host:

Disto: [e.g. Fedora, Ubuntu, Proxmox]: N/A
Kernel version: N/A
QEMU version: N/A
QEMU command line: N/A
libvirt version: N/A
libvirt XML file: N/A

VM:

Windows version: Windows Server 2022
Which driver has a problem: pvpanic, qemufwcfg, qemupciserial
Driver version or commit hash that was used to build the driver: 0.1.217-1

Additional context
Add any other context about the problem here.

Hi @jborean93 ,
If you are looking for immediate workaround, you can enable test signing on the VM.
Run:

Thanks for the workaround, I'm attempting to see if I can just resign them myself with my own certificate. Currently working through New-FileCatalog and generating my cert, will let you know how I go.

Just noticed that viostor for 2k12 and 2k12R2 are also affected by this same problem. Unfortunately that's even more difficult to deal with as these are needed to install windows on a virtio backed hdd.

What's funny, is that qemufwcfg, qemupciserial, and smbus are completely unchanged in actual substance between 0.1.215-2 and 0.1.217-1. Yet in the latter version, the same exact driver files (literally just .infs for these) are now self-signed, rather than signed with a valid certificate.
(pvpanic maybe has somewhat of an actual excuse, since I think the driver file was actually changed in some actual manner between 0.1.215-2 and 0.1.217-1.)
It's a bit silly to release a new version and have several drivers go from valid-signature status to self-signed status when nothing in those drivers actually changed.

 (I don't have test signing turned on; presumably if I did, the installation would succeed.) MSI log excerpt:
[...]
DIFXAPP: ENTER: InstallDriverPackages()
DIFXAPP: INFO: 'CustomActionData' property 'DIFxApp Version' is '2.1'.
DIFXAPP: INFO: 'CustomActionData' property 'UI Level' is '5'.
DIFXAPP: INFO: 'CustomActionData' property 'componentId' is '{544B33DA-A7E0-44D2-9DB0-CACA3B842DA3}'.
DIFXAPP: INFO: 'CustomActionData' property 'componentPath' is 'C:\Program Files\Virtio-Win\Pvpanic\'.
DIFXAPP: INFO: 'CustomActionData' property 'flags' is 0x6.
DIFXAPP: INFO: 'CustomActionData' property 'installState' is '2'.
DIFXAPP: INFO: 'CustomActionData' property 'ProductName' is 'Virtio-win-driver-installer'.
DIFXAPP: INFO: 'CustomActionData' property 'ManufacturerName' is 'Red Hat, Inc.'.
DIFXAPP: INFO: user SID of user performing the install is 'S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-1001'.
DIFXAPP: INFO: opening HKEY_USERS\S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-1001\Software\Microsoft\Windows\CurrentVersion\DIFxApp\Components\{544B33DA-A7E0-44D2-9DB0-CACA3B842DA3} (User's SID: 'S-1-5-21-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-1001') ...
DIFXAPP: INFO:   ENTER:  DriverPackageInstallW
DIFXAPP: INFO:   RETURN: DriverPackageInstallW  (0xE0000247)
DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\Virtio-Win\Pvpanic\pvpanic.inf'
DIFXAPP: ERROR: InstallDriverPackages failed with error 0xE0000247
DIFXAPP: RETURN: InstallDriverPackages()<PHONE_NUMBER> (0xE0000247)
CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 21:28:23: InstallFinalize. Return value 3.
MSI (s) (D8:F0) [21:28:23:902]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (D8:F0) [21:28:23:902]: User policy value 'DisableRollback' is 0
MSI (s) (D8:F0) [21:28:23:902]: Machine policy value 'DisableRollback' is 0
MSI (s) (D8:F0) [21:28:23:979]: Note: 1: 2318 2:
MSI (s) (D8:F0) [21:28:23:991]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1421650826,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (D8:F0) [21:28:23:991]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (D8:F0) [21:28:23:994]: Executing op: DialogInfo(Type=1,Argument=Virtio-win-driver-installer)
MSI (s) (D8:F0) [21:28:24:001]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 21:28:24: Rollback. Rolling back action:
[...]

So basically what's happening here is that DriverPackageInstallW is returning ERROR_DRIVER_STORE_ADD_FAILED, presumably because the signature isn't valid. And then the installer helpfully does a complete rollback of everything it had done up to that point and tells the user to go do something productive with their life instead of trying to install virtio drivers.

The problem with Win10 pvpanic and stub-drivers should be fixed in https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.217-2/virtio-win-gt-x64.msi
Win8 drivers need enabling testsigning in the BCD and our test-signing cert to be installed in the root and trustedpublisher certificate stores. I'm going to add this certificate to the virtio-win package in the next (latest) build.
Best,
Vadim.

Can you confirm that the self signed cert you are now using will not have the following constaint
X509v3 Basic Constraints: critical
    CA:TRUE

This makes it impossible to trust the certificate manually rather than enabling test signing.

@jborean93
Confirmed.The new certification was created without  "-cy authority" flag to make sure that it has no Base Constraint property.
This change was required to fix the embedded signature issue https://bugzilla.redhat.com/show_bug.cgi?id=2082021
The new certificate is effective from build 221 which planned to be used as the base for the next "latest" rpm.
Vadim.


Double letter column addresses not recognized

Trying to address a partial row with the range(["S2:DP2"]) produces a failure with this error:  "address (["S2:DP2"]) not in A1- or R1C1-format".  This is documented as an acceptable A1 addressing format.  If the documentation is correct then the problem would appear to be that double-letter column ranges beyond 'Z' are not understood correctly by Robust.

Bug fix: Now several letter column addresses are correctly recognized.
Thank you for pointing this out.

My pleasure as always, Thomas.  Be well.
  From: Thomas R<EMAIL_ADDRESS>
To: Thomas008/robust_excel_ole<EMAIL_ADDRESS>Cc: shbeavers<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Friday, November 2, 2018 5:49 PM
Subject: Re: [Thomas008/robust_excel_ole] Double letter column addresses not recognized (#12)
Bug fix: Now several letter column addresses are correctly recognized.
Thank you for pointing this out.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


DioError [DioErrorType.RESPONSE]: Http status error [415]

Issue Info
在项目中设置了contentType，但是在后端获取contentType与Content-Type时都是null，试了很多遍都不行，后端通路，就是dio提交数据过去没办法获取这两个属性。

Info
Value

Platform Name
flutter /android

Platform Version
1.12.23+hotfix.8

Dio Version
2.1.0

Android Studio / Xcode Version
no

Repro rate
all the time (0%)

Repro with our demo prj
don't try

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
我的dio被我封装一个单例。
global config:
_dio.options = BaseOptions(
        baseUrl: API.baseUri,
        connectTimeout: 5000,
        receiveTimeout: 3000,
        contentType: Headers.jsonContentType,
        headers: {
          'Authorization': 'Bearer '
        }

single request config：
await BjuHttp.post(
                              API.addComment,
                              data: data,
                              options: Options(contentType: Headers.jsonContentType, headers: {"Content-Type": "application/json"})
                            )

请求后后台日志：
22:43:10.517 [http-nio-8080-exec-7] WARN  org.springframework.web.servlet.mvc.support.DefaultHandlerExceptionResolver - Resolved [org.springframework.web.HttpMediaTypeNotSupportedException: Content type '' not supported]
22:43:10.528 [http-nio-8080-exec-7] INFO  top.hzwei.bju.common.intercepter.JWTIntercepter - #### ContentType=null, Content-Type=null

检查一下data是否为null?

Since I changed a method, this problem has not occurred. I feel that DIO's global BaseOptions settings cannot be overridden by options. See if other users have experienced this problem

I'm getting the same error, anyone was able to resolve it?

I was able to solve the issue by defining BaseOptions, exactly like the following:
`
import 'package:dio/dio.dart' as dio;
String baseUrl = 'http://YourLinkHere/api/';
dio.BaseOptions _dioOpts = dio.BaseOptions(
method: 'POST',
connectTimeout: 1000000,
sendTimeout: 100000,
receiveTimeout: 100000,
baseUrl: baseUrl,
headers: {
HttpHeaders.userAgentHeader: '*******',
HttpHeaders.acceptCharsetHeader: 'utf-8',
HttpHeaders.acceptEncodingHeader: 'gzip, deflate, br',
HttpHeaders.acceptHeader: '/',
HttpHeaders.acceptLanguageHeader: 'en-US',
HttpHeaders.contentTypeHeader: 'multipart/form-data;',
HttpHeaders.connectionHeader: 'keep-alive',
},
contentType: dio.Headers.jsonContentType,
responseType: dio.ResponseType.json,
);
//then, executing the Post Method like this:
try {
dio.Response response = await dio.Dio(_dioOpts).request(
'UserPhoto',
data: dio.FormData.fromMap(jsonData), //Getting FormData object from jsonData: Map<String, Object>
);
  if(response.statusCode == 200)
    return 'Success';
  else
    return '';

} catch (e) {
  print("Exception Caught: $e");
  return '';
}

`

I have the same issue after update to this version. any solution yet?

I have a similar issue on the latest version and even the previous one. It seems Dio cant handle any other response codes except 200. I have an authentication endpoint and been sending forbiden or unauthorized response code but i get an exception thown with the error  DioError [DioErrorType.RESPONSE]: Http status error [403] or  DioError [DioErrorType.RESPONSE]: Http status error [401]. I tried catching it as shown below, the exception can't be caught, it gows straight to the dio.dart file on the _dispatchRequest() method and code hanges, as shown below. Only way to go ahead was to return a 200 with a json of response etc, but thats not really ideal. Why cant it just handle the http codes and return them on the statusCode parameter like iot does 200.
Here i try to catch the exception but cannot.

Tried again to catch it on the auth.controller.dart file, stuill cannmot be caught

I see this issue was opened on April 15, still not fixed yet? Any solution to this, or maybe I wrote my code wrong.

Should i open a new issue for y'all guys to work on it?

To me the solution was set the contentType header like this:
Dio dio = new Dio();
dio.options.contentType = Headers.formUrlEncodedContentType;

Search for your type of content.
Best regards

我是这样解决的，需要设置拦截器  dio: ^4.0.0
var baseUrl="";
BaseOptions _dioOpts = BaseOptions(
method: 'POST',
connectTimeout: 1000000,
sendTimeout: 100000,
receiveTimeout: 100000,
baseUrl: baseUrl,
contentType: Headers.formUrlEncodedContentType,
responseType: ResponseType.json,
);
Interceptor interceptor = LogInterceptor(
requestHeader: true,
requestBody: true,
responseBody: true,
responseHeader: false,
error: true,
);
Dio dio = Dio(_dioOpts);
dio.interceptors.add(interceptor);


rebase: bump go-ceph version to v0.16.0

Describe what this PR does
go-ceph v0.16.0 contains subvolume metadata APIs and subvolume snapshot
metadata APIs.
Please note, as the APIs can not be tested in the go-ceph CI, it requires
build-tag ceph_ci_untested.
Signed-off-by: Prasanna Kumar Kalever<EMAIL_ADDRESS>

/retest ci/centos/upgrade-tests-cephfs

/retest ci/centos/upgrade-tests-rbd

/retest ci/centos/mini-e2e-helm/k8s-1.21
/retest ci/centos/mini-e2e-helm/k8s-1.22
/retest ci/centos/mini-e2e-helm/k8s-1.23
Jun 15 08:00:23.316: FAIL: backend images not matching kubernetes resource count,image count 23 kubernetes resource count 21

/retest ci/centos/mini-e2e-helm/k8s-1.21

/retest ci/centos/mini-e2e-helm/k8s-1.23

/retest ci/centos/mini-e2e-helm/k8s-1.23

/retest ci/centos/mini-e2e-helm/k8s-1.23


Improve OpenAI tracing and implement metrics

Partner [Ge] ask: improve observability for OpenAI SDK

OpenAI SDK should enrich traces with additional attributes, suggested semconv: https://github.com/open-telemetry/semantic-conventions/compare/main...lmolkova:semantic-conventions:openai
And emit metrics

Prototype: https://github.com/Azure/azure-sdk-for-net/compare/main...lmolkova:azure-sdk-for-net:openai-hackathon

See also https://github.com/cartermp/opentelemetry-instrument-openai-py

See also https://github.com/openai/openai-dotnet/blob/main/docs/observability.md and https://github.com/open-telemetry/semantic-conventions/blob/main/docs/gen-ai/gen-ai-spans.md


Lost support for camera dolly during movie capture

In 3.3 it was possible to define a camera trajectory for changing the camera view during play back and video recording. This feature is now missing in 4.0.
Users at WCB looking at overground running or in some cases automotive design want the camera to move with the model so the model doesn't simply move out of view.

I'm also missing this feature. Would be great if you could have the view track a body during playback (ie watch the knee up close during walking).