Adding indexed, keyed, and entries

Not yet ready.

Codecov Report

Merging #120 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #120   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         898    943   +45
=====================================
+ Hits          898    943   +45

Impacted Files
Coverage Δ

dist/partial.lenses.cjs.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ae5b2c2...eb270fb. Read the comment docs.


Refactor abstract master client with master selection policy

What changes are proposed in this pull request?
Enhance the abstract master client with the master selection policy that allows a client to connect to primary master / standby master or a specific master. This refactoring is a prerequisite for the following master side works.
Why are the changes needed?
Introduced different types of MasterSelectionPolicy(/ies)
Does this PR introduce any user facing changes?
N/A

alluxio-bot, merge this please

@jiacheliu3 @elega please sign the cla before merging the code in OS repo


Television Accessory showing incorrect icon

@karlentwistle Thanks for releasing the new version of the gem with the Television functionality. I got it installed and I am able to create an accessory, a television service, a speaker service, a few input services and link them all together.
They show up in the Home app and I can control volume and send button presses from the Remote app as well.
The only thing I can't get to work is to show the accessory as a TV in the Home app.
I've tried doing
RubyHome.configure do |c|
   c.discovery_name = 'Television'
   c.category_identifier = :television
 end

per the example, but this seems to operate on the Bridge, not the accessory. When I have this configuration, I see a TV icon when adding the bridge to the Home app, but after the accessory is added it displays a house icon instead of a TV.
Any ideas what I'm doing wrong?

Hey again @johndbritton 👋
I just tested this out using the television example and it appears to work ok for me.

Are you using a relatively recent version of iOS - mine is 14.3
Something else that springs to mind.  Assuming you don't have any automation setup against your ruby_home television I would try to remove that file and then restart ruby_home. It might fix the issue.
If that doesn't work could you share the entire script you're trying to run and I can take a look.

Hey again @johndbritton 👋
I just tested this out using the television example and it appears to work ok for me.

Are you using a relatively recent version of iOS - mine is 14.3
Something else that springs to mind.  Assuming you don't have any automation setup against your ruby_home television I would try to remove that file and then restart ruby_home. It might fix the issue.
If that doesn't work could you share the entire script you're trying to run and I can take a look.


Revert Changes To The Stable One

I'm sorry, it has been 2 months since the latest update, and everything has become complicated. It makes me uncomfortable to even look at this repository. I want to revert the changes before things became complicated. Regarding the /dev/ branch, here's what I want to do:
Things I want to do:

Revert support for multi-concept training: This was never on my list because it's really hard to do in Colab. Yet, I still did it, and now we have been dealing with bugs for 2 months that I couldn't fix.
Revert recursive arguments and sub_folder for certain cells: This also supports multi-concept training.
Take back my word to simplify cells: It's hard to maintain simplified and automated processed cells. It also makes the training process inflexible, whereas my notebook promises flexibility. Since there is a 1-click Lora training notebook, I think I don't need to do this anymore.
Remove the Launch Portable Web UI cell: This is my fault. I will focus on updating the inference cell next time.

Also, I hope you all can use Kohya LoRA Finetuning instead of Kohya LoRA Dreambooth, so I can focus on one LoRA notebook. It's basically my fault from the start to create two LoRA notebooks.

Yes, I know that feeling when a code base gets out of control ;)
I haven't used the "Lora Finetuning" yet and there are a couple of settings which are new to me (e.g., "Bucketing and Latent Caching"). There also doesn't appear to be as lot annotated as in the "Lora Dreambooth" notebook. Is there some "getting started" documentation to get familiar with the notebook? Or maybe a simple "migration" guide :)?

Revert support for multi-concept training

Will it still be possible to change the dataset.toml or something similar by hand? I rarely use multi-concepts as such but I frequently use subsets to prioritize images (better images get more repetitions than those of lower quality).

Remove the Launch Portable Web UI cell

How can we test unsupported lora types such as locon and loha without the Web UI?


using pyrealsense2 with L515

Required Info

Camera Model
L515

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Windows 10

Platform
PC

SDK Version
<IP_ADDRESS>7

Language
Python

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
I just purchased the L515 Lidar camera. I want to use this camera with Python via the pyrealsense2 library and recently found the sample codes to be written in C++. I've read through the Python wrapper examples as well.
So my main question is, if I were to use pyrealsense2, is everything that's written in C++ (the examples) doable in Python as well? Are there any limitations? Asking this since there is no tutorial in using the Python wrapper except for the one in your repository.
Any help/advice is appreciated.

Hi @leemerlas
To the best of my knowledge 100% of functionality available in C/C++ is also available in python.

Hi @dorodnic
Thanks for the response! We want to implement our use case in Python, that's why I asked this question. Gonna leave this issue open for a bit more in case someone has more info to add.

@leemerlas
Is there anything further needed here?
*If we don’t hear from you in 7 days, this issue will be closed.


Getting Crash continuously (Make sure to call FirebaseApp.initializeApp(Context) first)

Hello I am getting this exception continuously on launch of app :
Process: appPackage, PID: 5951
java.lang.RuntimeException: Unable to create application .BaseApplication: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process package-name. Make sure to call FirebaseApp.initializeApp(Context) first.
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5406)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1545)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6119)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this processpackage-name. Make sure to call FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(Unknown Source)
at com.google.firebase.database.FirebaseDatabase.getInstance(Unknown Source)
at
.BaseApplication.onCreate(BaseApplication.java:32)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1024)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5403)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1545)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6119)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
My gradle file contains this :
compile 'com.google.firebase:firebase-auth:11.6.2'
compile 'com.google.firebase:firebase-core:11.6.2'
}
apply plugin: 'com.google.gms.google-services'
and in main gradle :
    classpath 'com.google.gms:google-services:3.1.1' // google-services plugin

Only my system getting this issue, please give any suggestions to solve this issue.

@NehaKushwah993 could you show your AndroidManifest.xml as well as the onCreate function of your BaseApplication class.

For androidManifest, no code written regarding Firebase, and for BaseApplication :
@Override
public void onCreate() {
    super.onCreate();

    FirebaseApp.initializeApp(BaseApplication.this);

    // initialize image loader (load image-urls)
    ImageDisplayer.initialize(getApplicationContext());
}

I

@NehaKushwah993 I'd like to see the AndroidManifest anyway.  Also can you explain why you're manually calling initializeApp in your onCreate?  You should not need to.

There was another issue too, I was getting exception that Firebase is not initialized in this process, even when  this initialize() method was written. and that issue resolved automatically and then I started getting this issue.

I searched for its solution and found this in suggestion, I was calling it in MainActivity first. Initially I was not calling it then it started throwing this error and then I put this method in onCreate of MainActviity then also it didn't solved.

 Enter Password Activity -->

    <activity android:name=".mainActivity.MainActivity" />

</application>

I removed that from BaseApplication, and now getting it in MainActivity :
@Override
protected void onCreate(@Nullable Bundle savedInstanceState) {

    super.onCreate(savedInstanceState);

    FirebaseApp.initializeApp(MainActivity.this);
    database = FirebaseDatabase.getInstance(); // THIS LINE IS CRASHING
    myRef = database.getReference("remoteControl");

....
Logs :
FATAL EXCEPTION: main
Process: com.asiatv.demoz5xtv, PID: 19106
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.asiatv.demoz5xtv/com.asiatv.demoz5xtv.mainActivity.MainActivity}: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.asiatv.demoz5xtv. Make sure to call FirebaseApp.initializeApp(Context) first.
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2339)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2413)
at android.app.ActivityThread.access$800(ActivityThread.java:155)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1317)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)
Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.asiatv.demoz5xtv. Make sure to call FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(Unknown Source)
at com.google.firebase.database.FirebaseDatabase.getInstance(Unknown Source)
at com.asiatv.demoz5xtv.mainActivity.MainActivity.onCreate(MainActivity.java:69)
at android.app.Activity.performCreate(Activity.java:6010)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1129)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2292)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2413)
at android.app.ActivityThread.access$800(ActivityThread.java:155)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1317)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)

What happens if you remove the FirebaseApp.initializeApp(MainActivity.this); from MainActivity as well?

Getting samr error after removing it from mainactivity too.

Getting this after removing from mainActivity :
java.lang.RuntimeException: Unable to create application .BaseApplication: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process package-name. Make sure to call FirebaseApp.initializeApp(Context) first.

@NehaKushwah993 this is very confusing, as Firebase.initializeApp is normally called automatically in a ContentProvider we inject.
Could you try doing a full manual initialization in your base Application class?  It looks like this:
FirebaseOptions options = new FirebaseOptions.Builder()
       .setApplicationId("YOUR_APP_ID") // Required for Analytics.
       .setApiKey("YOUR_API_KEY") // Required for Auth.
       .setDatabaseUrl("YOUR_DATABASE_URL") // Required for RTDB.
       // ...
       .build();
FirebaseApp.initializeApp(this /* Context */, options, "secondary");

You can find the values you need in the google-services.json file.

I fixed that issue, I searched about this issue and applied all solutions i found and it worked.
The changes I made are :
build.gradle (main) :
buildscript {
repositories {
jcenter()

   google()

}
dependencies {
classpath 'com.android.tools.build:gradle:2.3.3'
// removed this
//        classpath 'com.google.gms:google-services:3.0.0'
}
}

allprojects {
repositories {
jcenter()

   google()

}
}

build.gradle (app) :
 //Updated firebase

compile 'com.google.firebase:firebase-database:10.0.1'
compile 'com.google.firebase:firebase-auth:10.0.1'
compile 'com.google.firebase:firebase-analytics:10.0.1'
compile 'com.google.firebase:firebase-core:10.0.1'

compile 'com.google.firebase:firebase-database:11.6.2'
compile 'com.google.firebase:firebase-auth:11.6.2'
compile 'com.google.firebase:firebase-analytics:11.6.2'
compile 'com.google.firebase:firebase-core:11.6.2'

had to remove app-support-v4. I think firebase includes older version of that because when i was adding android-support-v4 externally newer version then I was getting another error : "isDeviceSupported() not found"
Had to exclude android-support-v4 from another library too :
compile('com.jakewharton:butterknife:8.8.1') {
exclude module: 'android-support-v4'
exclude module: 'appcompat-v7'
exclude group: 'com.android.support'
}
These all changed made my code work. And now that issue has been fixed.
Thanks

@NehaKushwah993 glad it's all working for you!

I had the same exact problem, what I did is the following

I unified the version of the firebase services to be as following
compile 'com.google.firebase:firebase-firestore:11.8.0'
compile 'com.google.firebase:firebase-database:11.8.0'
compile 'com.google.firebase:firebase-core:11.8.0'
compile 'com.google.firebase:firebase-auth:11.8.0'

I did add those

//@ at the app module
apply plugin: 'com.google.gms.google-services'

//@the dependenices
 classpath 'com.google.gms:google-services:3.2.0'

@AMR-aa1405465 solution worked for me. I was using different firebase versions for different firebase services. After unified version & applying plugin & dependencies at module level  resolved the issue.
Thanks AMR-aa1405465 .

//ML Kit dependencies
 implementation 'com.google.firebase:firebase-core:16.0.3'
 implementation 'com.google.firebase:firebase-ml-common:16.1.2'
 implementation 'com.google.firebase:firebase-ml-vision:17.0.0'
 implementation 'com.google.firebase:firebase-ml-vision-image-label-model:15.0.0'
 implementation 'com.google.firebase:firebase-ml-model-interpreter:16.2.0'

The above can't be unified. Still looking for a solution to this problem

I had to downgrade google service plugin from version 4.1.0 to version 4.0.1 in my project's build.gradle
classpath 'com.google.gms:google-services:4.0.1'

The work around proposed by @Edijae works for me as well. However, in my case, the problem appears only in release where I've proguard enabled. Pretty sure it is something to do with proguard.

@NehaKushwah993  are those code for android studio? i'm using xamarin forms and want to solve this problem where fire base not initialize

The reply by @Edijae is the only one that worked for me too

Try to call
	LoadApplication(new App(new DroidModule()));

before firbase
On Mon, 5 Nov 2018 at 00:42, Aman Alam<EMAIL_ADDRESS>wrote:

The reply by @Edijae https://github.com/Edijae is the only one that
worked for me too
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-android/issues/385#issuecomment-435696935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASYzdMzdnkv4QbZ6na_gYKHfGiNbCpADks5urzwSgaJpZM4QySJM
.

Downgrading the google service plugin from version 4.1.0 to version 4.0.1 in the project's build.gradle seemed to do the trick for me.
classpath 'com.google.gms:google-services:4.0.1'

I had to downgrade google service plugin from version 4.1.0 to version 4.0.1 in my project's build.gradle
classpath 'com.google.gms:google-services:4.0.1'

I actually upgraded to--> classpath 'com.google.gms:google-services:4.2.0' and it works like a charm with : implementation 'com.google.firebase:firebase-database:16.0.6'
implementation 'com.google.firebase:firebase-core:16.0.7'

update the gradle main classpath 'com.google.gms:google-services:4.2.0'

Mil gracias, solo era de cambiar la versión classpath 'com.google.gms:google-services:4.0.1' a la más actual classpath 'com.google.gms:google-services:4.2.0' =)

I tried almost everything that was suggested in Stack Overflow and almost gave up....
Then I came across this Code Labs and I opened the app/build.gradle ... here is what I found
dependencies {
// Firestore
implementation 'com.google.firebase:firebase-firestore:18.1.0'
implementation 'com.google.firebase:firebase-auth:16.2.0'
implementation 'com.google.android.gms:play-services-auth:16.0.1'

....
Then I realized something, ... they didn't include
 implementation 'com.google.firebase:firebase-core:16.0.7'
So i took the Firebase Core out and my app run successfully... spent the whole day on this nasty error.
So I suggest that, you upgrade your Firebase dependencies to the latest and take out the Firebase Core.

Downgrading the google service plugin from version 4.1.0 to version 4.0.1 in the project's build.gradle seemed to do the trick for me.
classpath 'com.google.gms:google-services:4.0.1'

It really works..Thanks

Reason and solution:
This is the common error you will get most of the time.
Reason: when you integrate your project with the Firebase it adds the dependencies
 implementation 'com.google.firebase:firebase-auth:16.1.0'     implementation 'com.google.android.gms:play-services-auth:16.0.1'
and classpath
classpath 'com.google.gms:google-services:4.1.0'
you just need to update them
This is how you can update https://youtu.be/5d1g9aqczIE

update the gradle main classpath 'com.google.gms:google-services:4.2.0' it worked for me

I had to downgrade google service plugin from version 4.1.0 to version 4.0.1 in my project's build.gradle
classpath 'com.google.gms:google-services:4.0.1'

This worked for me too

@KrightKnight  Thanks, Worked for me as well!

Updating gradle main classpath from 4.1.0 -> 4.0.1 worked for me. Not sure though what's going on under the hood.

I have same issue, error log :
Process: com.sentrabilling.kasir.free, PID: 8814     java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sentrabilling.kasir.free/com.sentrabilling.kasir.activity.SplashActivity}: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.sentrabilling.kasir.free. Make sure to call FirebaseApp.initializeApp(Context) first.         at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3319)         at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)         at android.app.ActivityThread.access$1100(ActivityThread.java:229)         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)         at android.os.Handler.dispatchMessage(Handler.java:102)         at android.os.Looper.loop(Looper.java:148)         at android.app.ActivityThread.main(ActivityThread.java:7325)         at java.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)      Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.sentrabilling.kasir.free. Make sure to call FirebaseApp.initializeApp(Context) first.         at com.google.firebase.FirebaseApp.getInstance(com.google.firebase:firebase-common@@16.0.2:240)         at com.google.firebase.iid.FirebaseInstanceId.getInstance(Unknown Source)         at com.sentrabilling.kasir.activity.SplashActivity.onInit(SplashActivity.java:48)         at com.sentrabilling.kasir.core.BaseActivity.onCreate(BaseActivity.java:83)         at android.app.Activity.performCreate(Activity.java:6904)         at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1136)         at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3266)         at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)          at android.app.ActivityThread.access$1100(ActivityThread.java:229)          at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)          at android.os.Handler.dispatchMessage(Handler.java:102)          at android.os.Looper.loop(Looper.java:148)
I tried to call FirebaseApp.initializeApp(this); in Application class, but got different error log :
Process: com.sentrabilling.kasir.free, PID: 9469     java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sentrabilling.kasir.free/com.sentrabilling.kasir.activity.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'com.google.android.gms.tasks.Task com.google.firebase.iid.FirebaseInstanceId.getInstanceId()' on a null object reference         at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3319)         at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)         at android.app.ActivityThread.access$1100(ActivityThread.java:229)         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)         at android.os.Handler.dispatchMessage(Handler.java:102)         at android.os.Looper.loop(Looper.java:148)         at android.app.ActivityThread.main(ActivityThread.java:7325)         at java.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)      Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'com.google.android.gms.tasks.Task com.google.firebase.iid.FirebaseInstanceId.getInstanceId()' on a null object reference         at com.sentrabilling.kasir.activity.SplashActivity.onInit(SplashActivity.java:48)         at com.sentrabilling.kasir.core.BaseActivity.onCreate(BaseActivity.java:83)         at android.app.Activity.performCreate(Activity.java:6904)         at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1136)         at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3266)         at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)          at android.app.ActivityThread.access$1100(ActivityThread.java:229)          at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)          at android.os.Handler.dispatchMessage(Handler.java:102)          at android.os.Looper.loop(Looper.java:148)          at android.app.ActivityThread.main(ActivityThread.java:7325)
In SplashActivity.java I just call
FirebaseInstanceId.getInstance().getInstanceId().addOnSuccessListener(this, new OnSuccessListener<InstanceIdResult>() {             @Override             public void onSuccess(InstanceIdResult task) {                 String token = task.getToken();                 Pref.setFirebase(token);             }         });
But I tried to create new empty project, and everything goes well. The project need not call FirebaseApp.initializeApp(Context) first.
Any help will be appreciate.
Thank you.

Hi,
The problem is value node="replace" in AndroidManifest.xml. When I removed it or changes to "merge", everything goes well.
Here project example for reproducing this issue. It is made using Android Studio 3.4.1.
https://github.com/asrofie/TestFirebase.git
Please use your google-service.json
Any help will be appreciate.
Thank you

What a fragile mess. is any of this documented in any structured, reliable way? I've been banging my head against the wall for days just trying to get FCM working for simple push notifications.  This is nuts.

I had the same exact problem, what I did is the following and IT WORKS =)

I unified the version of the firebase services to be as following
compile 'com.google.firebase:firebase-firestore:11.8.0'
compile 'com.google.firebase:firebase-database:11.8.0'
compile 'com.google.firebase:firebase-core:11.8.0'
compile 'com.google.firebase:firebase-auth:11.8.0'
I did add those

//@ at the app module
apply plugin: 'com.google.gms.google-services'

//@the dependenices
 classpath 'com.google.gms:google-services:3.2.0'

Adding plugin solved my issue.

try different versions of 'com.google.gms:google-services' . I changed that to 4.2.0 and now it works fine with sdk version 27
classpath 'com.google.gms:google-services:4.2.0'

https://github.com/asrofie/TestFirebase.git
I am getting this error in xamarin.forms. Can you please me on this?

@SrinivasaRaoMakkena Hi. I am getting this error in xamarin.forms. Can you please help me on this?


Performance issues between SFBO and Teams powershell modules

Hi,
There seems to be a sizable reduction in performance when switching to the new Teams Powershell module from the SFBO one.
Connect-MicrosoftTeams

PS> Measure-Command { Grant-CsTeamsCallingPolicy<EMAIL_ADDRESS>-PolicyName:$null }

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 13
Milliseconds      : 712
Ticks             : 137125621
TotalDays         : 0.000158710209490741
TotalHours        : 0.00380904502777778
TotalMinutes      : 0.228542701666667
**TotalSeconds      : 13.7125621**
TotalMilliseconds : 13712.5621

Compared with the SFBO module
$sfbSession = New-CsOnlineSession -Credential $o365Cred -OverrideAdminDomain "$sfboOrgName.onmicrosoft.com"
Import-PSSession $sfbSession  | Out-Null

PS> Measure-Command { Grant-CsTeamsCallingPolicy<EMAIL_ADDRESS>-PolicyName:"Test-Policy" }

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 3
Milliseconds      : 329
Ticks             : 33294699
TotalDays         : 3.853553125E-05
TotalHours        : 0.00092485275
TotalMinutes      : 0.055491165
**TotalSeconds      : 3.3294699**
TotalMilliseconds : 3329.4699

This seems to occur consistently when using the Grant-cs* and set-cs* cmdlets. I have seen the Teams module take up to 2 minutes to execute commands the older Skype for Business Online Module would do in 3 seconds or less.
Powershell on Windows Server 2019.
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17763.1490
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.1490
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Hi,
i have also raised this already in another post:
https://github.com/MicrosoftDocs/office-docs-powershell/issues/7407

i had to switch back to the old module accelerate my scripts again.

Also experiencing issues with this
in my case it takes more than 30 seconds to run a get-csonlineuser for a single user
This problem becomes painful when you have Powershell scripts that take hours to complete
I noticed SFBO powershell even tough it still works is no longer available for download
Is it going to stop working?

Hello @dappleby300 I'll try to pass this information on to the team behind the module, as here we are limited to documentation issues, also if you want you can open a support ticket from your tenant.
Hope this information helps you,

@get-itips Thank you very much for the contribution and sharing this explanation. @dappleby300 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Update RAGAgentLlama and ReActLlama

Description

Use ChatOpenAI to interface with TGI-gaudi as ChatHuggingFace has a bug
Update tools for unit test as duckduckgo throws strange rate limit error

Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds new functionality)

Dependencies
No newly introduced 3rd party dependency.
Tests
unit test

Tested with OpenAI GPT-4o-mini for react_langgraph and ragagent. Screenshots below.


Isn't there a Blink?

I was searching for a blink modifier. Is there a reason why Chalk isn't providing a .blink-modifier?
Thanks in advance! 😄  💐

Yes, it's intentionally left out as it's annoying for the user.
See: https://github.com/chalk/ansi-styles/pull/6

Thanks a lot - I could have expected that! 😃

Also, it's pretty much a dead render mode. Blink isn't supported many places at all, and indeed it's incredibly annoying for the user.


Setup build on Azure Pipelines

Setup build on Azure Pipelines

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.

:white_check_mark: Package verification completed without issues. PR is now pending human review


LAB_08-Manage_Virtual_Machines.md

Current Translation:
Penyeimbang beban Azure
Suggested Translation:
Azure load balancer

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run the bugfix tool and waiting for result. ICMS QUERY


Add parameters to specify custom ca, key and cert files

This PR adds 3 parameters to server class, which enables to use custom ca/key/cert, for exemple to use the ones provided by puppet : https://community.openvpn.net/openvpn/wiki/PuppetCA

Thanks a lot for your work!
Unfortunately, this PR interferes with #181. As #181 adds the same functionality in a more complete manner, I'd like to go with the changes in #181.


Cannot find BrowserModul

I'm submitting a...

[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

- Node version: XX
- Platform:

Others:

Closing now as author didn't fill the issue template.


Scale Node Pool Up or Down for RKE2 provisioned clusters is not working for long cluster/node pool names

Setup

Rancher version: v2.6-head (052336574a21bf5675af9dc80632c69215a9715d)
Browser type & version: Chrome (94.0.4606.81)

Describe the bug
"+" and "-" buttons do nothing on node pools of RKE2-provisioned clusters.
To Reproduce

Navigate to RKE2-provisioned cluster in Cluster Manager with long name used for cluster and node pool (see examples on screenshots below and in the comments).
For any node pool, click "+" or "-" buttons to attempt to scale up/down the number of nodes in the pool.

Result
Nothing happens, no new nodes are provisioned or existing ones removed. Looking at "Network" tab confirms there is no request going to backend.
Expected Result
Node pool is scaled up/down accordingly.
Screenshots

This is going to have to be solved with a team effort. The backend cannot change the naming. Kubernetes has a strict length maximum for names. Therefore, we have to do what we are doing (truncating the name and adding 5 random characters at the end).
Instead of looking at just the name of the MachineDeployment and matching it to the machinePool, the UI will have to do the following:

The MachineDeployment will have an infrastructureRef that points to a MachineTemplate
That MachineTemplate will be cloned from a Config (*)
The Config will be referenced by a machineConfigRef from the cluster object's spec.rkeConfig.machinePools

So the identification of MachineDeployment to machinePool will be more complicated, but I don't really see a way around that at this point.
(*) This is currently not possible because the backend does not identify which Config a MachineTemplate is cloned form. This is the part that will need to be adjusted by the backend.

@thedadams , thank you for detailed explanation and plan of action. Moving it to 2.6.4 as it only happens if longer names are used and we're close to 2.6.3 dev code freeze time.

There may need to be UI change for this, to be confirmed as part of the implementation.

Backend changes seems to be working as expected. There is an issue with UI not working with some node drivers. Will keep the issue in the "QA Working" column until the UI issue is fixed. See comments https://github.com/rancher/dashboard/issues/4990#issuecomment-1043656690

The UI issue is still in the reopened status but I see now that the backend issue can be passed since I was able to provision and scale up/down node pools for different RKE2 node driver clusters. (the UI issue got more comments  https://github.com/rancher/dashboard/issues/4990#issuecomment-1049035700)

Test Environment:
Rancher version: rancher_version
Rancher cluster type: single-node docker install / HA
Docker version: 20.10
Downstream cluster type: rke2 node driver clusters

Testing:

provision different node driver RKE2 clusters
get machine templates for those clusters (apiversion: rke-machine.cattle.io/v1)
each template will have new annotations added:

  rke.cattle.io/cloned-from-group-version:
  rke.cattle.io/cloned-from-kind:
  rke.cattle.io/cloned-from-name:

rke.cattle.io/cloned-from-kind is machineConfigRef type from the cluster yaml file
rke.cattle.io/cloned-from-name: is machineConfigRef name from the cluster yaml file

UI will be looking for that rke.cattle.io/cloned-from-name value in the template and then working with the pool which machineConfigRef.name is the same as the value in template
whole picture/logic

linode and do examples

I can deploy different rke2 node driver clusters
I can scale pool up/down
I can delete the cluster

Upgrade testing
2.6.3 -> 2.6-head 8c785a1

Create Rancher server (HA) 2.6.3
Deploy DO RKE2 node driver cluster
Copy digitaloceanmachinetemplates.rke-machine.cattle.io resource for one of the node pools
Upgrade Rancher to 2.6-head
Notice that digitaloceanmachinetemplates.rke-machine.cattle.io got updated with 3 new annotations (see above)

2.6.3 template            vs             2.6-head template

scale node pools up/down and verify that nodes are created/deleted

the following issue created while testing the upgrade path https://github.com/rancher/rancher/issues/36627


clr-tree-node on triggering collapse a scroll appears on Chrome, an overlapping on Firefox

Describe the bug
When we try to collapse a clr-tree-node from a clr-tree a scroll appears on Chrome and an overlapping on Firefox.
How to reproduce
It is visible on the docs site https://clarity.design/documentation/tree-view#recursive-tree
Steps to reproduce the behavior:

Go to https://clarity.design/documentation/tree-view#recursive-tree
Click to collapse a tree node
[Chrome] See the scroll when a node starts collapsing
[Firefox] See the overlapping when a node starts collapsing

Expected behavior
The component's UI should be clean without the scroll and the overlap.
Versions
App

Angular: [9]
Clarity: [3]

Device:

Type: [pc]
OS: [win10]
Browser [Chrome 83.0.4103.106 (Official Build) (64-bit)]
Browser [Firefox 77.0.1 (64-bit)]

Additional notes

@iivanovgit - I looked at this on windows and macOS in both Chrome and FF and I'm not sure what you mean by

a scroll appears on Chrome
and
overlapping on Firefox

In both borwsers on macOS and windows I'm only seeing a page scrollbar as I would expect because the content of the page is longer than the viewport.
Can you clarify this a bit and  create an isolated reproduction in stackblitz that demonstrates what you are seeing in your application? Website demos on the website are not a good representation of real world use cases and should not be used for submitting issues.
We keep starter apps here: https://stackblitz.com/@clr-team

https://stackblitz.com/edit/clarity-v3-light-theme-nw42ve?file=src/app/app.component.html
On Chrome: Initially the Michael Scott (Regional Manager) tree node is expanded. When collapsing it, the scroll appears on its child node.
The same situation in Firefox: instead of scroll there is overlapping of child nodes on top of the remaining page content.

Any chance this bug gets prioritized? We're seeing this in our production app too.


make sites.js human-readable

this PR re-implementes "commas-first" structre, first proposed and approved in #39
( https://github.com/XXIIVV/Webring/commit/3a75ddaf60ff22c567a4d84e958e912dcd1fe343#diff-eacf331f0ffc35d4b482f1d15a887d3b )
re-formated sites.js, to make it human-readable;
this will also make future editing (like adding site-types) simplier and clearer.
order and functionality stayed unchanged.

My personal preference is that we shouldn't do this. I know it used to be this way, and I really disliked it since it doesn't follow a standard "linting" practice. The way it is now, it can be run through Standard easily checked for single quotes, space between object brackets, and trailing commas. If we implement this, we can no longer do this.
If we are going to attempt to make this more easily readable, then I recommend that we put each key-value pair on its own line just like you did, but not with a leading comma unless we enforce that throughout the project, which I'd be against.
I'm much more in favor of this:
{
  url: 'https://electro.pizza',
  title: 'electro pizza',
  type: 'blog',
  author: 'rho',
  rss: 'https://electro.pizza/feed.xml',
  feed: 'https://electro.pizza/twtxt.txt'
}

rather than this:
, { url: 'https://electro.pizza'
    , title: 'electro pizza'
    , type: 'blog'
    , author: 'rho'
    , rss: 'https://electro.pizza/feed.xml'
    , feed: 'https://electro.pizza/twtxt.txt'
    }

I'm pretty much ambivalent between the current format and a standard friendly unfolded display for readability.
{
  url: 'https://electro.pizza',
  title: 'electro pizza',
  type: 'blog',
  author: 'rho',
  rss: 'https://electro.pizza/feed.xml',
  feed: 'https://electro.pizza/twtxt.txt'
}

ok, now it's comma-lst

yeah, that's intentional, and officially acknowleged usecase: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas

ok, no trailing commas

yeah, that's intentional, and officially acknowleged usecase: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas

True, but the project is using Standard which doesn't allow comma-dangle. Looks good though. Thanks!


Refactor: import-targets to import-artifacts

Description

Updates the user commands to show as import-artifacts instead import-targets following the changes in the API and documentation.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality not to work as expected)

Additional requirements

[x] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct.

[x] I agree to follow this project's Code of Conduct

A few recommendations where to rename targets to artifacts:

https://github.com/kairoaraujo/repository-service-tuf-cli/blob/4d92647e388a496fda5cce45abc5cf707850b200/pyproject.toml#L49-L50

Done

https://github.com/kairoaraujo/repository-service-tuf-cli/blob/4d92647e388a496fda5cce45abc5cf707850b200/repository_service_tuf/cli/admin/ceremony.py#L216

Done

!!! BUG !!! https://github.com/kairoaraujo/repository-service-tuf-cli/blob/4d92647e388a496fda5cce45abc5cf707850b200/repository_service_tuf/helpers/api_client.py#L23 I am in favor of
renaming the enum URL from public_targets to public_artifacts here

If you rename publish_targets above you can consider doing here: https://github.com/repository-service-tuf/repository-service-tuf-cli/blob/980495ad51ee0cc3a847c24d0ceb4de9eec1b1d6/repository_service_tuf/helpers/cli.py#L45
and here https://github.com/kairoaraujo/repository-service-tuf-cli/blob/4d92647e388a496fda5cce45abc5cf707850b200/repository_service_tuf/helpers/api_client.py#L161

I'm not renaming now. We can do it as another issue. This PR was intended to change the user views.


PowerShell does/did not work

I try to use it with DCS, but apparently, it does not work. The Plugin shows up in OBS, but no screen can be seen. It stays black/empty.
I am not sure if I installed it correctly. I can not test any other game at the moment, since I only play DCS with my VR headset. Maybe you can help?

I think I fixed my problem. I added the regkey on my own and it now works. I added C:\Program Files\OpenXR-OBSMirror\XR_APILAYER_NOVENDOR_OBSMirror.json
I think the Powershell did not work for me for what ever reason.

https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/24 has a .reg file if you want to copy it


Read the README in APM

Is your feature request related to a problem? Please describe.

It is difficult to find and read the readme for plugins installed through APM.
Describe the solution you'd like

Add a button to the plugin list to read the readme for the selected plugin. The readme file will be searched for in the extracted folder by pattern matching.
Describe alternatives you've considered

Add a button to open the extracted folder of the plugin.
Additional context

I tried to implement this, but the feature to open the Readme and license of the package directly was not very useful, even though it makes the code more complicated. Instead, I will consider to add the feature to open the download folder of the package.

This assignment is just to show your effort.


Response timeout

(base) root@Jengro:~# curl google.com
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE>

301 Moved

The document has moved
here.

(base) root@Jengro:~#

I can access Google normally, but running main.go keeps timeout
(base) root@Jengro:/home/jengro/dev/translateimage# go run example/main.go
2024/04/29 12:34:19 playwright: timeout: Timeout 30000ms exceeded.
exit status 1

No matter how long the timeout is set, running main.go still prompts for timeout. So far, I haven't succeeded once

I can't reproduce this problem unless I slow down my internet very much. So, send me your ping, internet speed and full console output from the example in the dev branch.

PS C:\Users\Administrator\Documents\Dev\translateimage> ping translate.google.pl

Pinging translate.google.pl [<IP_ADDRESS>] with 32 bytes of data:
Reply from <IP_ADDRESS>: bytes=32 time=14ms TTL=118
Reply from <IP_ADDRESS>: bytes=32 time=14ms TTL=118
Reply from <IP_ADDRESS>: bytes=32 time=14ms TTL=118
Reply from <IP_ADDRESS>: bytes=32 time=14ms TTL=118

Ping statistics for <IP_ADDRESS>:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 14ms, Average = 14ms
PS C:\Users\Administrator\Documents\Dev\translateimage>

PS C:\Users\Administrator\Documents\Dev\translateimage> git branch
* dev
  main
PS C:\Users\Administrator\Documents\Dev\translateimage> go run .\example\main.go
2024/05/10 06:21:32 Driver and Firefox browser installed
2024/05/10 06:21:33 Playwright instance started
2024/05/10 06:21:33 Firefox instance started
2024/05/10 06:21:34 Created a new page
2024/05/10 06:21:35 Set the site URL to: https://translate.google.pl/?op=images&hl=en&sl=auto&tl=en
2024/05/10 06:22:06 playwright: timeout: Timeout 30000ms exceeded.
exit status 1
PS C:\Users\Administrator\Documents\Dev\translateimage>

I have written a draft patch. Please test it and send me the console results and the videos.zip file.

I have written a draft patch. Please test it and send me the console output and the videos.zip file.

https://tmp.link/f/663f285402799

I didn't mean the screen recording, but the videos.zip file, which contains recordings of the headless browser. After running these commands:
git clone https://github.com/spywiree/translateimage.git
cd translateimage
git checkout dev
cd example
go run .

the videos.zip file will be in the translateimage/example folder.

我指的不是屏幕录制，而是 videos.zip 文件，其中包含无头浏览器的录制。

videos.zip

@spywiree-priv  Found a solution?

I think so. Check now.

I think so. Check now.

Great, it can work now


Fix Ember.emberDeprecate is not a function

The internal deprecate wrapper imports Ember's deprecation utility from a different location than the documented one.
When running this addon against the latest version of Ember, a runtime error occurs where Ember's deprecation function is not defined.
deprecate documentation: https://api.emberjs.com/ember/3.24/functions/@ember%2Fdebug/deprecate

For some reason, when the deprecate import is renamed through the import, the Babel plugin breaks. It converts the function into Ember.emberDeprecate rather than Ember.deprecate.
At first I thought that this was all caused by importing from the wrong module (my first commit) but that didn't actually fix the problem.
I then figured this would be a bug in ember-cli-babel since the version used here is really old. However, I updated the dependency and that didn't fix the issue.
Just avoiding the alias while importing does fix the problem so... I guess we'll do that? 🤷♂

Interestingly, it seems like the @ember/debug modules are handled as a special-case in ember-cli-babel...
https://github.com/babel/ember-cli-babel/blob/76876904812fee227fff2af1e29aca73cf6f1c76/node-tests/addon-test.js#L113-L136
I wonder if that is related to the fact that the alias on importing seems broken.

Oh hey, here's the actual bug
https://github.com/ember-cli/babel-plugin-debug-macros/issues/48

Hey, thanks for the fix and info!
I'm going to merge and publish it, once CI passes.

Recently I had to do a similar change to the v2-beta branch https://github.com/san650/ember-cli-page-object/pull/537/commits/2d7ea1b22f3ac910381c2f0b009fc6d9db293691, but I didn't realized we do use invalid import path. Will fix it there as well.

alright, travis build has failed for ember-beta scenario due to a monstrous amount of deprecations, and maximum log length 😋
seems I'd need to cleanup some of ember deprecations to make Travis a bit more happy. But not today.

published as 1.17.7. Thanks!


[BUG] CONNECT command append unwanted string to ClientID

What happened
The Client ID provieded in the connection parameters was not reflected 1:1 into the CONNECT command. By inspecting the newtork traffic (i.e. Wireshark) it was detected that MQTTX append a random suffix; altering it without any notice/way to control this behavior may cause some headhache.
Expected
Some MQTT services expect to receive a precise MQTT client ID as a part of the authentication process, before granting access to the topics queue.

Client ID inserted in MQTTX UI: gabbagabbahey
Client ID provided by MQTTX to the remote service: gabbagabbahey_1720423123000

Environment

OS: Microsoft Windows [Versione 10.0.22631.3737]
MQTTX Version: v1.10.0

More detail

Hi, thanks for using it. It shouldn't be a bug because you have turned on the timestamp auto-add feature. You can click the clock icon to turn it off.

This prevents disconnection issues when using the same Client ID to connect in different locations.

Hi @ysfscream and thank you for your quick rountrip. I was totally unaware of it!
Have a great day

If there is no update, I will close this issue. Thanks.


Random key error in stax.Dropout layer

Dropout layer not working due to it's apply_fun keep = random.bernoulli(rng, rate, inputs.shape) .
When I add rng = PRNGKey(seed) before this line, the apply_fun works well

Hey, thanks for raising this. However, that change isn't what you want: it will make the dropout layer always to use the same fixed pattern of dropped out units (rather than sampling random ones).
The actual issue is that you need to pass a PRNG key into your top-level apply_fun. Here's an example of using the Dropout layer constructor in stax:
from __future__ import print_function
import jax.numpy as np
from jax import jit, grad
from jax import random
from jax.experimental import minmax
from jax.experimental import stax
from jax.experimental.stax import Dense, Relu, Dropout, LogSoftmax

init_fun, apply_fun = stax.serial(
    Dense(512), Relu, Dropout(0.4, mode='train'),
    Dense(512), Relu, Dropout(0.4, mode='train'),
    Dense(3), LogSoftmax
)

## Initialize parameters, not committing to a batch shape
in_shape = (-1, 28 * 28)
out_shape, net_params = init_fun(in_shape)

## Apply network to dummy inputs.

# Every time we want a new random dropout pattern, we split the prng key and
# pass a fresh subkey into the call
key = random.PRNGKey(0)
inputs = np.ones((10, 28 * 28))

key, subkey = random.split(key)
print(apply_fun(net_params, inputs, subkey))

key, subkey = random.split(key)
print(apply_fun(net_params, inputs, subkey))

# If we don't pass a prng key, we should get a clear error (this is new)
# print(apply_fun(net_params, inputs))  # NOTE: now an error!
# ValueError: Dropout layer requires apply_fun to be called with an rng argument.

## Run a training loop on dummy data

# When writing a training loop, we need to be sure to split the PRNG for each
# call that we want to have a different dropout pattern (i.e. each train step).

opt_init, opt_update = minmax.momentum(step_size=1e-3, mass=0.9)

def loss(params, batch, key):
  inputs, targets = batch
  predictions = apply_fun(params, inputs, key)
  return np.sum((predictions - targets) ** 2)

@jit
def step(i, opt_state, batch, key):
  params = minmax.get_params(opt_state)
  g = grad(loss)(params, batch, key)
  return opt_update(i, g, opt_state)

# Dummy input data stream
data_generator = ((np.zeros((10, 28 * 28)), np.zeros((10, 3)))
                  for _ in range(10))

# Optimize parameters in a loop
opt_state = opt_init(net_params)
for i in range(10):
  key, subkey = random.split(key)
  opt_state = step(i, opt_state, next(data_generator), subkey)
net_params = minmax.get_params(opt_state)

Look for the line with the comment "NOTE: now an error!".
It's too easy to forget to pass in a PRNG key, and then the error that happens isn't very informative. I'll improve the error message, but the real solution will be for us to include some better examples and make the PRNG system less surprising.

got it, seems the PRNG system need more work on it


Topology optimization

This PR presents an MFEM example of topology optimization. This addresses a user request made at the first MFEM workshop.
The objective is to minimize the compliance
\text{minimize} \int_\Omega f \cdot u\, \mathrm{d}x \text{~~over~~} u \in [H^1(\Omega)]^2 \text{~~and~~} \rho \in L^2(\Omega)

subject to
-\mathrm{Div}(r(\tilde{\rho})\mathsf{C}\varepsilon(u)) = f  \quad \text{in~} \Omega ~+ ~ \text{BCs}

-\epsilon^2 \Delta \tilde{\rho} + \tilde{\rho} = \rho  \quad \text{in~} \Omega ~ + ~ \text{Neumann BCs}

0 \leq \rho \leq 1 \quad \text{in~} \Omega
\qquad
\text{and}
\qquad
\int_\Omega \rho\, \mathrm{d}x = \theta\, \mathrm{vol}(\Omega)

Here, $r(\tilde{\rho}) = \rho_0 + \tilde{\rho}^3 (1 - \rho_0)$ is the solid isotropic material penalization (SIMP) law, $\mathsf{C}$ is the elasticity tensor for an isotropic linearly elastic material, $\epsilon > 0$ is the design length scale, and $0 < θ < 1$ is the volume fraction.
The method used here is based on entropic mirror descent [1] and was first proposed in [2].
The code does not rely on external software packages (e.g., IPOPT, PETSc).
[1] Beck, A., & Teboulle, M. (2003). Mirror descent and nonlinear projected subgradient methods for convex optimization. Operations Research Letters, 31(3), 167-175.
[2] Keith, B. and Surowiec, T. (2023) Proximal Galerkin: A structure-preserving finite element method for pointwise bound constraints. arXiv:2307.12444 [math.NA].

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3400
@brendankeith
@v-dobrev
@psocratis + @bslazarov
1/16/23
⌛due 1/30/23
⌛due 2/6/23

PR Checklist

[x] Code builds.
[x] Code passes make style.
[x] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[x] All sample runs at the top of the example source file work.
[x] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[x] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[x] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

The cmake file in the examples directory has to be updated.

I just updated this branch with the following changes:

Set $rho_h=\text{sigmoid}(\psi_h)$ with $\psi_h\in V_h$.
In the code, this is done by defining GridFunction psi(&control_fes) and MappedGridFunctionCoefficient rho(psi, sigmoid).
Here, MappedGridFunctionCoefficient is a child class of GridFunctionCoefficient returning fun(gf->Eval(T, ip). In this example, fun=sigmoid.

Update projit with a more mathematically correct projection psi = psi + c where $c\in\mathbb{R}$ satisfies $\int_\Omega \text{sigmoid}(\psi + c) = \theta \text{vol}(\Omega)$.

In this way, we do not have to use $\text{sigmoid}^{-1}$ in the update procedure and can preserve $0\leq \rho \leq 1$ exactly. Also, we do not need BasisType::Positive anymore.
To prevent psi from diverging, i.e., $\rho \rightarrow 0$ or $\rho \rightarrow 1$, we apply clip after each mirror descent update.

I just updated this branch with the following changes:

Set ρh=sigmoid(ψh) with ψh∈Vh.
In the code, this is done by defining GridFunction psi(&control_fes) and MappedGridFunctionCoefficient rho(psi, sigmoid).
Here, MappedGridFunctionCoefficient is a child class of GridFunctionCoefficient returning fun(gf->Eval(T, ip). In this example, fun=sigmoid.
Update projit with a more mathematically correct projection psi = psi + c where c∈R satisfies ∫Ωsigmoid(ψ+c)=θvol(Ω).

In this way, we do not have to use sigmoid−1 in the update procedure and can preserve 0≤ρ≤1 exactly. Also, we do not need BasisType::Positive anymore. To prevent psi from diverging, i.e., ρ→0 or ρ→1, we apply clip after each mirror descent update.

Thank you, @dohyun-cse !!

@bslazarov, can you please take another look after the latest changes?

@brendankeith , I am a bit confused. It seems that this branch contains also the changes from #3398. Should we close the other one and review just his one?

@brendankeith , I am a bit confused. It seems that this branch contains also the changes from #3398. Should we close the other one and review just his one?

The plan is to review and finish the review of https://github.com/mfem/mfem/pull/3398 and then merge that PR into this one. The only files to review in the topology optimization PR pertain to example 35, which make sense to review separately from the ex34 files.

Merged in next for testing...

I have one request: is there a way to make the test runs of ex37 and ex37p (for both GNU make and CMake) faster? Maybe use a coarser mesh or just make a few optimization iterations? Currently, the test runs of other example take a few seconds and for ex37/ex37p they take roughly 2min/1min.

I have one request: is there a way to make the test runs of ex37 and ex37p (for both GNU make and CMake) faster? Maybe use a coarser mesh or just make a few optimization iterations? Currently, the test runs of other example take a few seconds and for ex37/ex37p they take roughly 2min/1min.

@v-dobrev:
Reducing the number of iterations might not make sense. If we used much fewer iterations in any of the runs, we wouldn't resolve much of the optimal design.
I could easily reduce the number of test runs. However, there may be a pedagogical drawback to doing so.
As a potential compromise, is it possible to include additional test runs that aren't checked by the CI?

When running make test (or ctest with CMake) we don't necessarily need to run the examples so that the results makes sense from the point of view of a user. We mainly want to exercise the main code paths, so using a smaller number of iterations or a coarser mesh should not be a problem since our aim is not to fully solve the problem.
I agree that running the examples without parameters or the sample runs in the source files should make sense and fully solve the problem of interest. What I suggest is to run the tests of the examples with a set of parameters that is just used in make test (and ctest). Such tests can be added similar to this (in make): https://github.com/mfem/mfem/blob/664dfa2f625fbf3dcfee0b3b46d90da9f404a008/examples/makefile#L130-L133 and this (in CMake): https://github.com/mfem/mfem/blob/664dfa2f625fbf3dcfee0b3b46d90da9f404a008/examples/CMakeLists.txt#L104-L105

When running make test (or ctest with CMake) we don't necessarily need to run the examples so that the results makes sense from the point of view of a user. We mainly want to exercise the main code paths, so using a smaller number of iterations or a coarser mesh should not be a problem since our aim is not to fully solve the problem.
I agree that running the examples without parameters or the sample runs in the source files should make sense and fully solve the problem of interest. What I suggest is to run the tests of the examples with a set of parameters that is just used in make test (and ctest). Such tests can be added similar to this (in make):
https://github.com/mfem/mfem/blob/664dfa2f625fbf3dcfee0b3b46d90da9f404a008/examples/makefile#L130-L133
and this (in CMake):
https://github.com/mfem/mfem/blob/664dfa2f625fbf3dcfee0b3b46d90da9f404a008/examples/CMakeLists.txt#L104-L105

Thanks, @v-dobrev!! This is exactly what I was thinking of.

Re-merged in next for testing.


The package at "node_modules/react-native-dotenv/index.js" attempted to import the Node standard library module "path"

While building the js bundle I get:
The package at "node_modules/react-native-dotenv/index.js" attempted to import the Node standard library module "path". It failed because React Native does not include the Node standard library. Read more at https://docs.expo.io/versions/latest/introduction/faq/#can-i-use-nodejs-packages-with-expo

My versions:
node: 10.16
npm: 6.9
expo: 32.0.6
react-native-dotenv: 0.2.0
I've tried to remove node_modules, cleared cache, restarting the computer, install again.
I have the same problem as the stackoverflow question.
This is my babel.config.js:
module.exports = function config(api) {
  api.cache(true);

  return {
    presets: ['babel-preset-expo', 'module:metro-react-native-babel-preset', 'module:react-native-dotenv'],
    plugins: [
      [
        '@babel/plugin-proposal-decorators',
        {
          legacy: true,
        },
      ],
    ],
  };
};

Sure, you can do that.  But the problem is that the build toolchain doesn't support dynamic imports, so if I want to have multiple .env files floating around at the same time (e.g. .env.development, .env.staging, .env.production) there needs to be some way to switch which one I want to use at built-time without having to make code changes.
In general I find it rather remarkable that react-native doesn't have official support and recommandations for this kind of essential configuration management....

I have fixed it by installing the missing path package. I hope somebody gets a better solution and let us know.
File Structure:
my-app
  |_ package.json
  |_ babel.config.js:
  |_ config.js:
  |_ .env

My package.json
{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "axios": "^0.19.0",
    "expo": "~36.0.0",
    "path": "^0.12.7",
    "react": "~16.9.0",
    "react-dom": "~16.9.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz",
    "react-native-gesture-handler": "~1.5.0",
    "react-native-reanimated": "~1.4.0",
    "react-native-screens": "2.0.0-alpha.12",
    "react-native-web": "~0.11.7",
    "react-navigation": "^4.0.10",
    "react-navigation-stack": "^1.10.3"
  },
  "devDependencies": {
    "babel-preset-expo": "~8.0.0",
    "eslint": "^6.7.2",
    "eslint-plugin-prettier": "^3.1.1",
    "prettier": "1.19.1",
    "react-native-dotenv": "^0.2.0"
  },
  "private": true
}

My babel.config.js:
module.exports = function(api) {
  api.cache(true);
  return {
    presets: ['babel-preset-expo', 'module:react-native-dotenv'],
  };
};

My config.js
import { API_KEY } from 'react-native-dotenv';

export default {
  API_KEY,
};

My .env
API_KEY=example

I had the same problem for my expo project and clearing the npm cache helped.
 rm -r node_modules rm package-lock.json npm install expo start or npm start
In my bable config babel.config.js has the following.
module.exports = function(api) {   api.cache(true);   return {     presets: [       'babel-preset-expo',       'module:react-native-dotenv'     ],   }; };

Anything worked for me:
The package at "node_modules\react-native-dotenv\index.js" attempted to import the Node standard library module "path". It failed because React Native does not include the Node standard library. Read more at
https://docs.expo.io/versions/latest/introduction/faq/#can-i-use-nodejs-packages-with-expo
Failed building JavaScript bundle.

There's a new repo and package babel-plugin-dotenv-import.


MAIN - adds ids to Modal component

heya and good weeek @Weetbix ! 🤚
this will add ids to all the buttons of the modal.

Warnings

:warning:
Missing reviewer - Looks like this pull request is missing a reviewer. That's OK as long as this PR is still a 'work in progress', if that is the case please add 'WIP' in the PR title or corresponding label.

Messages

:book:
✅  Get a 🏆 for adding description on this PR. - Celebrate on every step!

  Generated by :no_entry_sign: dangerJS against 88755fbaa7c766daf7161179fc5891f555028f93


luv fails to build on Red Hat Linux

I'm building luv as part of Neovim, and I'm getting the following failure (likely related to #229).
[ 73%] Performing build step for 'luv-static'
gmake[4]: Entering directory `/home/anrussell/.local/src/neovim/.deps/build/src/luv-static-build'
gmake[5]: Entering directory `/home/anrussell/.local/src/neovim/.deps/build/src/luv-static-build'
gmake[6]: Entering directory `/home/anrussell/.local/src/neovim/.deps/build/src/luv-static-build'
gmake[6]: Leaving directory `/home/anrussell/.local/src/neovim/.deps/build/src/luv-static-build'
gmake[6]: Entering directory `/home/anrussell/.local/src/neovim/.deps/build/src/luv-static-build'
[ 50%] Building C object CMakeFiles/luv.dir/src/luv.c.o
In file included from /home/anrussell/.local/src/neovim/.deps/build/src/luv/src/luv.c:40:
/home/anrussell/.local/src/neovim/.deps/build/src/luv/src/fs.c: In function ‘push_fs_result’:
/home/anrussell/.local/src/neovim/.deps/build/src/luv/src/fs.c:222: error: ‘UV_FS_REALPATH’ undeclared (first use in this function)
/home/anrussell/.local/src/neovim/.deps/build/src/luv/src/fs.c:222: error: (Each undeclared identifier is reported only once
/home/anrussell/.local/src/neovim/.deps/build/src/luv/src/fs.c:222: error: for each function it appears in.)

System information:
$ uname -a
Linux dev100 3.8.13-98.2.1.el6uek.x86_64 #2 SMP Wed Aug 19 16:33:29 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux

Please let me know if I can provide additinoal information.

I had similar errors: https://gist.github.com/daurnimator/0d87994e809d87950cd963c834718762
The issue there was not updating the uv submodule. You need to use git submodule update --recursive

It’s been inactive for too long, so it’s closed.


added instructions for installing extension references

Docs Build status updates of commit 6c9ee2c:
:clock10: Full build: the average full build time is 7 min(s) 46 sec(s), this is based on the last 717 build(s) for this repository.

Docs Build status updates of commit 6c9ee2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-reference-for-IoT.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d7722a4:
:clock10: Full build: the average full build time is 7 min(s) 46 sec(s), this is based on the last 718 build(s) for this repository.

Docs Build status updates of commit d7722a4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-reference-for-IoT.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c78c8de:
:clock10: Full build: the average full build time is 7 min(s) 47 sec(s), this is based on the last 720 build(s) for this repository.

Docs Build status updates of commit c78c8de:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-reference-for-IoT.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[build] Meson kwargs support (>=0.49)

http://mesonbuild.com/Release-notes-for-0-49-0.html#can-specify-keyword-arguments-with-a-dictionary
Changes nothing, but keyword arguments became more maintainable.
e.g. #945 could be something like
--- a/meson.build
+++ b/meson.build
@@ -69,6 +69,10 @@ common_exe_opts    = common_opts + { 'install': true }
 common_static_opts = common_opts + { 'include_directories': dxvk_include_path }
 common_shared_opts = common_opts + { 'include_directories': dxvk_include_path, 'name_prefix': '', 'install': true }

+if dxvk_compiler.get_id() == 'msvc'
+  common_exe_opts  += { 'gui_app' : true }
+endif
+
 glsl_compiler = find_program('glslangValidator')
 glsl_generator = generator(glsl_compiler,
   output    : [ '<EMAIL_ADDRESS>],

Started this just for fun, to check how those kwargs works. I'm sharing this, since patch already exists.
Feel free to reject this PR, and use it's parts as a guide when/if DXVK will support Meson 0.49.

I think it's far too early to require 0.49. We have to account for build systems being at least one year old.

Don't get me wrong though, I don't mind these changes - I'll keep this one open and probably merge them at a later time, when pretty much everyone will have meson 0.49 available.


dataInputSchema generated form doesn't bind value

What happened:
dataInputSchema generated form doesn't bind value
What you expected to happen:
Inputed values to be bound
How to reproduce it:
Create a workflow with dataInputSchema generated form doesn't bind value`, click "Start Workflow" and try to modify the value.

Closed as stale


Build error fixed ,removed one navbar and footer is added in all pages

Build error is fixed which was coming after the merge operation, there were 2 navbar, removed one navbar and footer was only added on home page, now its coming in all the pages.

Don't accept the removed-bugs-after-merge branch PR, in that I have only resolved the error, but their were 2 navigation  bar and footbar was only coming on home page, that I have resolved in this PR.

Please check before merging; multiple people have sent pull requests for this bug.


Update README badge

latest tag on emacs-27 is 27.0.91

I had an unpushed redesign of the readme I decided to push today, which includes an update to the badge (or at least generalizes it to say 27.x). Thanks for the PR in any case!


feat: add variant option

PR for the discussion here: https://github.com/nvim-tree/nvim-web-devicons/discussions/491#discussioncomment-10649821
I have a few questions about the code. Right now, refresh_icons() is called directly in the nvim-web-devicons.lua file. However, now that I'm adding an option which the refresh_icons() function depends on, should I move the call into the setup() function? Right now im just calling refresh_icons() again if the variant option is not "auto", which is a bit inefficient.

Right now im just calling refresh_icons() again if the variant option is not "auto", which is a bit inefficient.

That's unavoidable; we can't do anything until we know their choice.
Setup actually expects the icons to be populated i.e. refresh_icons has been called: https://github.com/williamhCode/nvim-web-devicons/blob/83238ce4809b4a34282ca8148e26e2d3fbf09ff7/lua/nvim-web-devicons.lua#L397
Suggestion: move the refresh_icons call at 595 to setup.

Additionally, i moved the refresh to right after setting variant global opt

No problem!


Fix particles freezing by resetting particle timer

one line change, resets particle lifetime when new particle is emitted. closes #56886

Thanks for opening a pull request!
 This way, people reading the Git log can easily figure out what's going on :slightly_smiling_face:
Once this is done, please squash the commits together so we can merge this. See PR workflow for instructions :slightly_smiling_face:

done, thank you

Cool, it took a lot of time to learn how to use git properly, haha.
It's exactly as you said, the system was getting set to inactive too early, I figured that the best way to deal with this was resetting the inactive_time and letting the new particle survive it's entire lifetime.
Thanks for all your help in this, had a huge breakthrough with the problem while talking with you about it :)

Thanks!


fix(about_dialog): Always use black color for window texts

Description
Updated the QPalette in AboutDialog.app to display texts in black colour even if dark mode is enabled on the environment.
I am really noob of Qt/C++ stack; please let me know if I am missing something to do or doing wrong.
Issue IDs
Closes #897
Steps to test new behaviors (if any)

OS: Any environment that dark mode is supported by Qt
Steps:

Open the about dialog
Confirm that texts in the window is written in black color

Before
After

Additional context
Tested on macOS 14.4 Sonoma, Arm64, M1 Max, Mac Studio (2022).

Hi siketyan,
We have been running the internal process to accept your PR.
Thank you for your contribution.

We have merged your PR.
Thank you for the contribution!


class not resolved when followed by a new-line character in a multiline classname

UnoCSS version
0.62.4
Describe the bug
When I use custom arbitrary selector, it will not get extracted if it is placed alone on line in a multi-line className.
/edit as per the screenshots below, it is problem with any classes that are alone on a new line.
/edit2 more tests revealed that any class followed by a new-line character will not get resolved.
    <button
      class={`
        ...more classes
        [&.withChildren]:px-3
        ...more classes
      `}
    />

e.g.
This will NOT work
    <button
      data-test-id="Button"
      class={`
        Button.Base ${onlyIconChild ? "iconOnly" : "withChildren"}
        [&.withChildren]:px-3
        flex items-center justify-center gap-1
        whitespace-nowrap [white-space:nowrap]
        [&_*]:pointer-events-none
        ${className}
      `}
      {...props}
    />

This WILL work
    <button
      data-test-id="Button"
      class={`
        Button.Base ${onlyIconChild ? "iconOnly" : "withChildren"}
        x [&.withChildren]:px-3 x
        flex items-center justify-center gap-1
        whitespace-nowrap [white-space:nowrap]
        [&_*]:pointer-events-none
        ${className}
      `}
      {...props}
    />

Possibly related to https://github.com/unocss/unocss/issues/4158
Reproduction
/edit NOTE This reproduction is INVALID as per my findings below.
Interestingly, it will behave a bit differently in this reproduction example.
import * as unocss from "@unocss/core"
const uno = unocss.createGenerator(unoConfig)

uno
  .generate(
    `
  flex
  [&.No]:px-3
  x [&.No]:px-3 x
  flex [&.Yes]:px-3 flex
  flex
  `
  )
  .then(res => {
    const { matched, css } = res
    console.debug("[UNO]\n", [...matched], "\n\n", css)
  })

This will print
[UNO]
 (3) ['flex', '[&.No]:px-3', '[&.Yes]:px-3']
...
/* layer: default */
.flex{display:flex;}
.\[\&\.No\]\:px-3.No,
.\[\&\.Yes\]\:px-3.Yes{padding-left:0.75rem;padding-right:0.75rem;}

So while the "No" arbitrary selector gets picked up, it is not resolved.
System Info
Chrome
node v20.14.0
"preact": "^10.23.2",
"@unocss/runtime": "^0.62.3",
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Need more investigation. I made a mistake in the reproduction, however I still do miss the class definition.

I cannot comprehend this. I managed to isolate the issue further and you can clearly see that this is not working, where • denotes a space.
••••••bg-red

However, both of these ARE working
••••••bg-red•
••••••bg-red•hi

More tests revealed that ANY class that is followed by a newline character does not get resolved

After affirming that uno.generate(tokenString) produces expected result AND MORE debugging, I actually found the issue and it was caused by the peculiar setup of our project.
I apologize


rdedup: 2.0.0 -> 3.0.1

https://github.com/dpc/rdedup/wiki/rdedup-v3.0.0-Release-Notes
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option 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] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @dpc

Success on x86_64-linux (full log)
Attempted: rdedup
Partial log (click to expand)

installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1
shrinking /nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1/bin/rdedup
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1/bin
patching script interpreter paths in /nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1
checking for references to /build in /nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1...
/nix/store/z60fqw7hgyr0ph80xx28fy56jhvhizvl-rdedup-3.0.1

Success on aarch64-linux (full log)
Attempted: rdedup
Partial log (click to expand)

installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1
shrinking /nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1/bin/rdedup
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1/bin
patching script interpreter paths in /nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1
checking for references to /build in /nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1...
/nix/store/jwxswmwq8bfb0sbpqqfy0xl07syzfvv1-rdedup-3.0.1


Add section on thread synchronization

As promised, this is my attempt to give a summary of all the things that can go wrong when using unsafe code to synchronize threads.

It might be a good idea to also add a section about premature deallocation of shared resources used by other threads, which is another classic multi-threading gotcha. But I'm not sure if I can find a nice Correct/Incorrect example pair for this.
Usually, people go for custom resource management because they're in a hot code path where Arc-style atomic increment/decrement is too expensive, and there is no general suggestion that can apply to all use cases there...

PS: I believe I am not responsible for this CI failure. Should I fix it anyway?

Don't worry about the CI failure, it's my fault for not checking that the Travis config works after setting it up =P.  (I got distracted trying to figure out how to deploy to a GitHub pages)

Looks great!


Send direct and share post

Hey, I just started to use your library and am loving it. I currently have a selenium bot that I use to send directs and posts to targets.
It would be great to have it implemented in your android tool because of all the IG bot suspicion limits on browsers and etc.
Thanks again for your work!

Thanks for the request. To clarify, you want to:

Send direct messages
Share posts with others

Under what conditions do you want to do this? Is it as part of another existing process? Or do you want to be able to do this with specific people?

In my case I would want to to this to specific people. I already use the Levi Pasha Instagram API to scrap targets to an list, excluding those who already follow me or I have interacted in the past. So it would be nice to have a file of dm targets to import.
Making sure you dont already have a chat with the person or she doesnt follows you would be important here.

In my case I would want to to this to specific people. I already use the Levi Pasha Instagram API to scrap targets to an list, excluding those who already follow me or I have interacted in the past. So it would be nice to have a file of dm targets to import.
Making sure you don't already have a chat with the person or she doesn't follows you would be important here.

Hello there.. The bot can send PM to private and public profiles, you can share your posts link putting it inside the PM_list.txt. (you can also do only that by removing other actions (like following or whatever).
You won't send PM (and other actions) if you already interacted with that user using this bot cause that's saved in interactions.json
Currently there isn't any check to see if you already sent a PM to someone without using this tool


Fluid pipes have transparent connecters when views at certain angles.


MM-18582 Remove utils.displayTime in favour of FormattedTime component

Summary

Remove utils.displayTime in favour of FormattedTime component
Ticket Link

https://github.com/mattermost/mattermost-server/issues/12242

@niklabh Why did you closed this PR?

react-intl doesn't export formatTime, formatDate. Will use FormattedDate and FormattedTime components to create correct PR.


Will this beta version plug into the skybrud for umbraco, by replacing core.dll and adding the provider.dlls?

Not an issue more a request for info..
Looking to leverage particularly the extended_tweet mode in the twitter provider.
So as per the topic should I be able to replace the core.dll and the provider.dlls and it work with the existing umbraco.skybrud.social implementation?

Hi Mike,
The new providers introduce a number of breaking changes, and I will probably introduce some more before the betas eventually turn into stable releases. The breaking changes are mostly to fix errors I've made in the past, reflect changes in the underlying APIs and simply to give the code a better structure (as Skybrud.Social was started more than five years ago).
Therefore, you won't just be able to switch out the current Skybrud.Social with the new core and provider DLLs. I'm pretty sure things will break, although I don't know exactly which parts at the moment.
When stable releases are available of the provider packages used by the Umbraco package (Facebook, Twitter, Instagram and Google), I'll make sure to update the Umbraco package accordingly. If I can find the time, I might even make some beta releases of the Umbraco package as well. I do however not yet know how much work it will take to update the Umbraco package, so I don't really have a time frame for that.
I hope that answers your questions ;)


Use CompositeByteBuf in CommandHandler instead of buffer copy

We should investigate whether we can use CompositeByteBuf as buffer aggregator instead of copying buffers in CommandHandler.

After measuring performance, management overhead for composite buffers nihilates performance gains that come from preventing buffer copies. So we're not going to implement that ticket.