Are pretrained models of ResNext-101(64-f) architecture available?

Hi, thanks for an awesome work.
Have you obtained pretrained models of ResNext-101(64-f) architecture?
If so, could you please add that models as well.
Thank you.

The model resnext-101-64f-kinetics.pth already exist in my Google Drive.

I mean for K+M pretrained model, not for Kinetics-400
I think in your google drive, you provided pretrained models only for ResNet model, not ResNext, right?

We did not try ResNeXt models on Kinetics-700 and Moments in Time datasets.
You have to train the models on your own if you want to use the models.


fix(footer): removed default slot

Describe pull-request
Removed default slot and introduced named slot for label.
Solving issue
Fixes: -
How to test

Go to storybook
Check in Components -> Footer -> Web Components
Check that the links are still working correct and look correct.

Suggested test steps

[ ] Browser testing (Chrome, Safari, Firefox)
[ ] Keyboard operability
[ ] Interactive elements have labels.
[ ] Storybook controls
[ ] Design/controls/props is aligned with other components
[ ] Dark/light mode and variants
[ ] Input fields – values should be displayed properly
[ ] Events

Closing this PR. I think we might not have to to do this for the links since they are not gonna change text in runtime as often as other text.


Updatig Popup Controls

I have been trying to update a Popup Slider to show volume, and have not found any way to do so.
I have tried before, and just now, to call the draw() function on the popup as you have suggested on Reddit with no success.
This is the code I am using. It's a bit ugly but should work.
def diagnosticView(qtile):
    global diagnosticPopup
    diagnosticPopup = PopupAbsoluteLayout(qtile, width=800, height=2097, controls=[
    PopupSlider(max_value=150, min_value=0, pos_y=100, pos_x=100, height=400, width=500, value=getVolume()[0], bar_size=20, marker_size=1, can_focus=False)
    ], background="#000000", close_on_click=False, can_focus=False)

@lazy.function
def showDiagnosticView(qtile)
    diagnosticView(qtile)
    diagnosticPopup.show(x=10, y=50)

@lazy.function
def hideDiagnosticView(qtile):
    diagnosticPopup.hide()

@lazy.function
def updateDiagnosticView(qtile):
    diagnosticPopup.draw()

Thank you.

How are you updating the value of the slider?

value=getVolume()[0] will only set the value at that point. It's not a reference to call getVolume() each time. You need to change the control's value and then redraw the popup.

Okay I'll try that. Sorry for the slow responses. I've been a bit busy.
For updating the value should I just call the function that defines the Popup?

That's one way of doing it but the trouble is I don't think it will hide the old one first.

I've started a PR (#185) that should make this easier.


CocoaPods could not find compatible versions for pod "FirebaseCore"

[REQUIRED] Please fill in the following fields:

Unity editor version: 2019.4.18f1
Firebase Unity SDK version: 7.0.2
Source you installed the SDK: Unity Package Manager
Problematic Firebase Component: Auth (Core?)
Other Firebase Components in use: Auth, Firestore, Crashlytics, RemoteConfig, InstanceID
Additional SDKs you are using: Tapdaq (includes AdMob)
Platform you are using the Unity editor on: Windows
Platform you are targeting: iOS, Android
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:
When building for iOS, we get the following error output in Unity's console:
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "FirebaseCore":
  In Podfile:
    Firebase/Auth (= 7.0.0) was resolved to 7.0.0, which depends on
      Firebase/CoreOnly (= 7.0.0) was resolved to 7.0.0, which depends on
        FirebaseCore (= 7.0.0)

    Firebase/Auth (= 7.0.0) was resolved to 7.0.0, which depends on
      FirebaseAuth (~> 7.0.0) was resolved to 7.0.0, which depends on
        FirebaseCore (~> 7.0)

CocoaPods could not find compatible versions for pod "GoogleAppMeasurement":
  In Podfile:
    Firebase/Analytics (= 7.0.0) was resolved to 7.0.0, which depends on
      Firebase/Core (= 7.0.0) was resolved to 7.0.0, which depends on
        FirebaseAnalytics (= 7.0.0) was resolved to 7.0.0, which depends on
          GoogleAppMeasurement (= 7.0.0)

    Tapdaq/AdMob (= 7.8.2) was resolved to 7.8.2, which depends on
      Google-Mobile-Ads-SDK (= 7.67.0) was resolved to 7.67.0, which depends on
        GoogleAppMeasurement (~> 6.0)

Steps to reproduce:
Generated Podfile by External Dependency Manager:
source 'https://github.com/tapdaq/cocoapods-specs.git'
source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/CocoaPods/Specs'
platform :ios, '11.0'

target 'UnityFramework' do
  pod 'Firebase/Analytics', '7.0.0'
  pod 'Firebase/Auth', '7.0.0'
  pod 'Firebase/Core', '7.0.0'
  pod 'Firebase/Crashlytics', '7.0.0'
  pod 'Firebase/Firestore', '7.0.0'
  pod 'Firebase/Messaging', '7.0.0'
  pod 'Firebase/RemoteConfig', '7.0.0'
  pod 'FirebaseInstanceID', '7.0.0'
  pod 'GoogleSignIn', '>= 5.0.0'
  pod 'Pollfish', '5.5.2'
  pod 'Tapdaq', '7.8.2'
  pod 'Tapdaq/AdColony', '7.8.2'
  pod 'Tapdaq/AdMob', '7.8.2'
  pod 'Tapdaq/AppLovin', '7.8.2'
  pod 'Tapdaq/FAN', '7.8.2'
  pod 'Tapdaq/Tapjoy', '7.8.2'
  pod 'Tapdaq/UnityAds', '7.8.2'
end

target 'Unity-iPhone' do

end

Packages:
"com.google.external-dependency-manager": "1.2.162",
"com.google.firebase.analytics": "7.0.2",
"com.google.firebase.auth": "7.0.2",
"com.google.firebase.crashlytics": "7.0.2",
"com.google.firebase.firestore": "7.0.2",
"com.google.firebase.instance-id": "7.0.2",
"com.google.firebase.messaging": "7.0.2",
"com.google.firebase.remote-config": "7.0.2",

Relevant Code:
See above

Hi @Nyankoo,
It appears that the Tapdaq/AdMob plugin depends on Firebase Analytics (GoogleAppMeasurement), too, and in this case a different, older version of Firebase (6.0.0) than the version that you're app uses (7.0.0).
In these scenarios where conflicts like this occur you will neither either need to downgrade Firebase to match the same version that Tapdaq/AdMob uses, or preferably update the version of Tapdaq/Admob if an update is available.
I hope this helps.

Hi @Nyankoo,
It appears that the Tapdaq/AdMob plugin depends on Firebase Analytics (GoogleAppMeasurement), too, and in this case a different, older version of Firebase (6.0.0) than the version that you're app uses (7.0.0).
In these scenarios where conflicts like this occur you will neither either need to downgrade Firebase to match the same version that Tapdaq/AdMob uses, or preferably update the version of Tapdaq/Admob if an update is available.
I hope this helps.

@DellaBitta That helps, thank you! :)

@DellaBitta That helps, thank you! :)


[Sentinel] Upgrade Microsoft Sentinel

Resolves: https://github.com/Azure/azure-cli/issues/21665

Powered by CodeGen v2. Due to current limitation, the following command groups are not generated:

az sentinel entity;
az sentinel watchlist item;

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Sentinel


Refs #11964 -- Renamed a database check constraint test name.

I think the idea behind the original name is that the constraint is declared on the model (meta). The new name doesn't seem markedly better to me but I'm open to being convinced otherwise.

@timgraham the idea behind the name change was that CheckConstraint (and all Constraint instances) must be defined at the model level and that the test is actually asserting that the database constraint is enforced. In other words, the assertion the test contains have little to do with the fact the constraint is defined at the model level; they are asserting that it's enforced at the database level as well.