3.0.100-preview6/7/8 not working on ARM64

We use .NET Core on a Variscite DART-MX8M-MINI SoM and it worked fine with 3.0.100-preview5.
With preview 6 .NET Core doesn't work at all, because as soon as a program is startet it gets stuck without any output (also nothing on the serial console) and needs to be killed. Even dotnet --info does not work.
We are running Yocto (Linux imx8mm-var-dart 4.14.78-imx8mm+g33611e8 #1 SMP PREEMPT Tue Jun 4 14:04:01 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux) on the board.
I do not know what information I can also provide, but if you need something I'm happy to provide anything you need.

Would you be able to attach gdb to the hung dotnet process and then print stack trace of thread 1 and share it?
sudo gdb -p PidOfYourHungDotnet
thread select 1
bt

Here the output:

root@imx8mm-var-dart:~# sudo gdb -p 636
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-poky-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 636
[New LWP 637]
[New LWP 638]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
0x0000ffffbd382320 in __lll_lock_wait (futex=futex@entry=0xffffbc61a7d8, private=0) at /usr/src/debug/glibc/2.27-r0/git/nptl/lowlevellock.c:43
43          lll_futex_wait (futex, 2, private); /* Wait if *futex == 2.  /
(gdb) thread 1
[Switching to thread 1 (Thread 0xffffbcf99e80 (LWP 636))]
#0  0x0000ffffbd382320 in __lll_lock_wait (futex=futex@entry=0xffffbc61a7d8, private=0) at /usr/src/debug/glibc/2.27-r0/git/nptl/lowlevellock.c:43
43          lll_futex_wait (futex, 2, private); / Wait if *futex == 2.  */
(gdb) bt
#0  0x0000ffffbd382320 in __lll_lock_wait (futex=futex@entry=0xffffbc61a7d8, private=0) at /usr/src/debug/glibc/2.27-r0/git/nptl/lowlevellock.c:43
#1  0x0000ffffbd37b648 in __GI___pthread_mutex_lock (mutex=0xffffbc61a7d8) at /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_mutex_lock.c:78
#2  0x0000ffffbc5bbe68 in ust_lock_nocheck () from /usr/lib/liblttng-ust.so.0
#3  0x0000ffffbc5c17d4 in ?? () from /usr/lib/liblttng-ust.so.0
#4  0x0000ffffbc60eeb0 in ?? () from /usr/lib/liblttng-ust.so.0
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

@janvorli should this issue be moved to another repo to increase visibility? Maybe dotnet/iot?

@janvorli Just tried preview 7 with the same result :-(

@janvorli @carlossanlop Still not working with preview 8 👎
Is there anything we can do to help fix this issue?

@janvorli @joperezr @krwq who can help with this iot issue? Should I transfer it to another repo for better visibility?

dotnet/iot is not the right place for this issue. If this should be transfered, the best place for it would be either coreclr repo or the cli repo. I would probably start with coreclr. That said, I think that either @janvorli or @jkotas would probably be the ones that could help here.

@chrfin how are you running dotnet on ARM64? Could you share the exact steps? Do you have TTY allocated when you are printing stuff on the console? (if not sure try running you app inside tmux which ensures TTY)

This looks like duplicate of https://github.com/dotnet/coreclr/issues/15693. This hang is caused by a incompatibility between glibc and lttng in Yocto images.
To workaround it, you can either:

Update to latest version of lttng library that has the hang fixed (https://github.com/dotnet/coreclr/issues/15693#issuecomment-479333213)
or
Set export COMPlus_LTTng=0 to disable use of lttng tracing in CoreCLR

@jkotas we are facing similar issue on Yocto build of stm32mp1-dk2-mx 4.19.9 Linux on armv7. The last preview we were able to run our app on was 5 (preview 4 is working as well) every newer preview hangs before the app starts. The last line in trace is CoreCLR path = ....
Setting COMPlus_LTTng=0 does fixes the issue.
May I suggest changing the issue name to just ARM since both architectures appear to be affected.
Possibly also related to:

dotnet/coreclr#19025
dotnet/coreclr#24038
dotnet/core-setup#3561

Setting export COMPlus_LTTng=0 did work, but updating lttng-tools to 2.10.6 (previous version was 2.9.5) did not work.

As @jkotas mentioned, this seems like a duplicate of dotnet/coreclr#15693 .
Since the workaround did not work, let's please move the discussion to that issue/repo for better visibility.


document how to review a PR

It'd be great to add it to the dev doc: https://github.com/openservicemesh/osm/blob/main/docs/development_guide.md


Danger doesn't work with pull requests

https://github.com/danger/danger-js/issues/918
My disappointment is immeasurable and my day is ruined.

So yeah. That's it for my idea of offloading common code review tasks to Danger.
Here's an example of the bug in action.

omfg

So it's less a Danger issue and more a GitHub actions issue. Not that it makes me feel any better...

Yeah, forked repos only have read permission, so they can't add comments or anything. A personal access token won't help either because no secrets are shared with forks (aside from GITHUB_TOKEN). This makes Danger pretty much useless for OSS project.
Technically, it's not Danger's fault but they could at least mention this limitation in their docs.


Implement the Windows Image Acquisition (WIA) API

Definitions for the WIA api, based on "wia_lh.h" from the Windows 10 SDK.
Example use can be found at wia-example-rs

The PR has been updated to resolve the merge conflicts

Thanks for the thorough review on this. I have pushed an updated with the changes as suggested.

Thank you, latest suggested changes have been pushed


Fixed a formatting issue with a bullet list of schema properties.

I noticed that the formatting of this section of properties was incorrect on the asyncapi web site (but fine when viewed in GitHub).  I assume this change will fix the problem, but I can't verify since I don't know how the website is displaying the MD.
Here is how it currently looks when rendered on the web site:

This is definitely one of my better open source contributions.  ;)
Signed-off-by: Eric Wittmann<EMAIL_ADDRESS>

FWIW, the website is powered by Hugo. They use Blackfriday.

Thanks, Eric!


export hardcoded java errors into properties

close #399
This PR prepare java code String`s to translate. I hope that I find all strings for translation.
Testing done
Waiting for automatic test results. When the test passed it shall be fine.
Proposed upgrade guidelines
N/A
Localizations

[x] English

Submitter checklist

[x] The Jira / Github issue, if it exists, is well-described.
[x] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).

The changelog generator for plugins uses the pull request title as the changelog entry.
Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.

[ ] There is automated testing or an explanation that explains why this change has no tests.
[ ] New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.

[ ] New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
[ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
[ ] For new APIs and extension points, there is a link to at least one consumer.
[x] Any localizations are transferred to *.properties files.
[ ] Changes in the interface are documented also as examples.

Maintainer checklist
Before the changes are marked as ready-for-merge:

[ ] There is at least one (1) approval for the pull request and no outstanding requests for change.
[ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
[x] Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
[x] Proper changelog labels are set so that the changelog can be generated automatically. See also release-drafter-labels.
[ ] If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
[ ] java code changes are tested by automated test.

The tests are failing, I will look here little later


Added upgrade script which removes non-translated properties

There are problems with the index-command if you have properties which looks like this: i18n:-* you get the error
Error indexing or de-indexing page (path: ...) No structure type was available and no default exists for document with alias "home"
```

__informations:__

| q                | a
| ---------------- | ---
| Fixed tickets    | none
| Related PRs      | none
| BC breaks        | run `phpcr:migrations:migrate`
| Documentation PR | none

@danrot fixed


Issue 1541: fix wrong text in onboarding step

https://github.com/jdi-testing/jdn-ai/issues/1541

https://github.com/jdi-testing/jdn-ai/pull/1696
3.15.17


Fix uninitialised constant Gem::ConfigFile::SYSTEM_CONFIG_PATH

This is the same PR as #6073 but now being merged for master
What was the end-user problem that led to this PR?
bundle env uses the constant Gem::ConfigFile::SYSTEM_CONFIG_PATH which is not defined in early versions of RubyGems.
See: https://travis-ci.org/bundler/bundler/builds/276981165
What is your fix for the problem, implemented in this PR?
While SYSTEM_CONFIG_PATH is not defined for earlier versions of RubyGems, a constant called Gem::ConfigFile::SYSTEM_WIDE_CONFIG_FILE does appear to be both in current and early versions of RubyGems which contains the path (plus the ruby config file) we want.
Why did you choose this fix out of the possible options?
This fix is compatible with all the tested versions of RubyGems in CI and is not overly complex.

@bundlerbot r+


Code component control copy functions

I'm fine changing the copy function names to whatever, copyColorData, etc. is fine by me.
The controls/controls structure — there's things in src/controls that are not in fact "controls". This file, copy.ts, and another more meta file, called control.ts. I thought it was confusing to have slot.ts and copy.ts be siblings, when they're semantically different. One is a control itself, the other is something that uses controls. Given that, do you have some preference?


Milestone #2

Milestone #2 Tasks:

SCRIPT 1: Write a script that reads the downloaded data and performs and data cleaning/pre-processing, transforming, and/or splitting
SCRIPT 2: Write a script that performs data cleaning/pre-processing, reads in data from the first script
SCRIPT 3: Write a script which creates exploratory data visualization(s) and table(s) that are useful to help the reader/consumer understand that data set, reads in data from the second script
SCRIPT 4: Write a script that performs some statistical or machine learning analysis and summarizes the results as a figure(s) and a table(s), reads in data from the third script
SCRIPT 5: Write a literate code document which presents your analysis and findings (Jupyter notebook report), reads in data from the fourth script and maybe the third script?, written properly and shows KEY USEFUL information about EDA and statistical summaries from ML
Iterate on work done for milestone 1 as required per TA feedback

From discussion in class today:

write scripts in markdown but still in Python to make the written report easier
before lab tomorrow: think about a general workflow (ex// split the data, do this next, then this...)

Machine Learning Plan:

Split data into training and testing
Label our features (categorical, numerical, binary)
Create transformers for our features
Create models{} to test out 2 models (BASELINE DUMMY and RBF SVM and LR) - 571 LAB 4 3.2
use best. whatever to continue with our best model, based on f1 score? or mean cv score?
Hyperparameter Optimization with randomized search with best model - 571 LAB 4 3.3
Hyperparameter Optimization results - Confusion matrix , precision-recall curve, AUC? 573 LAB 1 2.7
use best model and best hyperparameters on test set
Use coeff to get top coefficients of best indicators 571 LAB 4 4.1

extra * find the test set with the most predictive readmission outcome vs not 571 LAB 4 5.2

Also, for any functions written we need documentation and sensible tests.

Machine Learning Plan:

Split data into training and testing
Label our features (categorical, numerical, binary)
Create transformers for our features
Create models{} to test out 2 models (BASELINE DUMMY and RBF SVM and LR) - 571 LAB 4 3.2
use best. whatever to continue with our best model, based on f1 score? or mean cv score?
Hyperparameter Optimization with randomized search with best model - 571 LAB 4 3.3
Hyperparameter Optimization results - Confusion matrix , precision-recall curve, AUC? 573 LAB 1 2.7
use best model and best hyperparameters on test set
Use coeff to get top coefficients of best indicators 571 LAB 4 4.1

extra * find the test set with the most predictive readmission outcome vs not 571 LAB 4 5.2

Also, for any functions written we need documentation and sensible tests.

Thanks for this Rachel! I checked in with Varada regarding this work - specifically for correlated features. If we decide to go ahead with logistic regression, it will make the weights of one of the correlated features larger than the other which will make the interpretability of the coefficients in #9 difficult. But prediction will be okay. I can't remember if we can do this in RBF SVM either. I will double check.

As we discussed in lab:

let's stick with LR and note that there is correlation but that the correlation is not too strong between features so we still want to go ahead with LR and predict

Scripts and other docs:

SCRIPT 1 --> @wiwang
SCRIPT 2 --> take info from raw folder from script 1 and clean it and put it into the processed folder @jraza19
SCRIPT 3 --> @jraza19 @sukh2929
SCRIPT 4 --> @rachelywong @wiwang @sukh2929 @jraza19
SCRIPT 5 --> @rachelywong @jraza19 , rachel write the results/conclusion, Javairia do intro and updates
update the READme to a summary --> @jraza19
put current proposal into a doc to save --> @wiwang
edits from Milestone 1 --> @wiwang / all of us depending on what edits need to be made
output tables and plots into a folder (name them Figure 1. and whatever, pls coordinate) so that referencing in SCRIPT 5 is easy --> @wiwang
references.bib document --> @rachelywong @jraza19 , provide all references to rachel in GH issue, figure out how to reference links and issues

Analysis plan:

Split data into training and testing @rachelywong
Label our features (categorical, numerical, binary) @rachelywong
Create transformers for our features @rachelywong
Create models{} to test out 2 models (BASELINE DUMMY and RBF SVM and LR) - 571 LAB 4 3.2 @rachelywong
use best. whatever to continue with our best model, based on f1 score? or mean cv score? @rachelywong
Hyperparameter Optimization with randomized search with best model - 571 LAB 4 3.3 @sukh2929
Hyperparameter Optimization results - Confusion matrix , precision-recall curve, AUC? 573 LAB 1 2.7 @sukh2929
use best model and best hyperparameters on test set @sukh2929
Use coeff to get top coefficients of best indicators 571 LAB 4 4.1 @wiwang
extra --> find the test set with the most predictive readmission outcome vs not 571 LAB 4 5.2 @wiwang
store_results function --> write documentation and function tests @rachelywong --> maybe in the future make this its own script

Submission:
@wiwang

@wiwang Please close this issue when we have all confirmed via Slack that we are good to go! and then create version 0.1.0 and submit both links to canvas (repo link and version link)! Thank you


error: device still authorizing

Steps to Reproduce

In android studio , i met this error when i tried to run the flutter project on my android phone（android 8.0）.
I'm sure that I have:

installed android 8.0 SDK  from Android Studio.
set the USB config to MTP in debug setting.
restart android studio/restart computer/reconnect device

all of these didn't work.
Logs

Error retrieving device properties for ro.product.cpu.abi:
error: device still authorizing

Launching lib\main.dart on<PHONE_NUMBER>493098 in debug mode...
Initializing gradle...
Resolving dependencies...
error: device still authorizing
Unhandled exception:
Exit code 1 from: C:\Users\Administrator\AppData\Local\Android\sdk\platform-tools\adb -s<PHONE_NUMBER>493098 shell -x logcat -v time -t 1
#0      _runWithLoggingSync (package:flutter_tools/src/base/process.dart:353:7)
#1      runCheckedSync (package:flutter_tools/src/base/process.dart:284:10)
#2      AndroidDevice.lastLogcatTimestamp (package:flutter_tools/src/android/android_device.dart:504:27)
#3      _AdbLogReader._start (package:flutter_tools/src/android/android_device.dart:678:41)
#4      _runGuarded (dart:async/stream_controller.dart:804:24)
#5      _BroadcastStreamController._subscribe (dart:async/broadcast_stream_controller.dart:217:7)
#6      _ControllerStream._createSubscription (dart:async/stream_controller.dart:817:19)
#7      _StreamImpl.listen (dart:async/stream_impl.dart:472:9)
#8      FlutterDevice.startEchoingDeviceLog (package:flutter_tools/src/resident_runner.dart:242:71)
#9      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:285:5)
<asynchronous suspension>
#10     HotRunner.run (package:flutter_tools/src/run_hot.dart:272:39)
<asynchronous suspension>
#11     AppDomain.startApp.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:387:62)
#12     AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:438:26)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#19     AppInstance._runInZone (package:flutter_tools/src/commands/daemon.dart:820:20)
#20     AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:436:15)
<asynchronous suspension>
#21     AppDomain.startApp (package:flutter_tools/src/commands/daemon.dart:384:12)
<asynchronous suspension>
#22     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:289:38)
<asynchronous suspension>
#23     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:401:18)
#24     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#25     _rootRunUnary (dart:async/zone.dart:1132:38)
#26     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#27     _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#28     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
#29     Future._propagateToListeners (dart:async/future_impl.dart:671:32)
#30     Future._complete (dart:async/future_impl.dart:476:7)
#31     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#32     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#33     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:295:13)
#34     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#35     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#36     _rootRunUnary (dart:async/zone.dart:1132:38)
#37     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#38     _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#39     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
#40     Future._propagateToListeners (dart:async/future_impl.dart:671:32)
#41     Future._complete (dart:async/future_impl.dart:476:7)
#42     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#43     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async/runtime/libasync_patch.dart:33:20)
#44     _rootRun (dart:async/zone.dart:1124:13)
#45     _CustomZone.run (dart:async/zone.dart:1021:19)
#46     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#47     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#48     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#49     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#50     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

D:\Development\flutter_windows_v1.0.0-stable\flutter>flutter doctor -v
[√] Flutter (Channel stable, v1.0.0, on Microsoft Windows [Version 10.0.16299.431], locale zh-CN)
    • Flutter version 1.0.0 at D:\Development\flutter_windows_v1.0.0-stable\flutter
    • Framework revision 5391447fae (9 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

\Error retrieving device properties for ro.product.cpu.abi:
error: device still authorizing

[√] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at C:\Users\Administrator\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: D:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.3)
    • Android Studio at D:\Program Files\Android\Android Studio
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] Connected device (1 available)
    • SM G9600 •<PHONE_NUMBER>493098 • android-arm • Android null (API null)

• No issues found!

This is an error that happens in adb, possibly due to insufficient permissions. See https://github.com/flutter/flutter/issues/10330.
What does adb devices return ?

This is an error that happens in adb, possibly due to insufficient permissions. See #10330.
What does adb devices return ?

C:\windows\system32>adb devices
List of devices attached
3949363555493098        offline

This is an error that happens in adb, possibly due to insufficient permissions. See #10330.
What does adb devices return ?

C:\windows\system32>adb devices
List of devices attached
3949363555493098        authorizing

The result change from ''offline'' to ''authorizing''

This is an error that happens in adb, possibly due to insufficient permissions. See #10330.
What does adb devices return ?

I re-install the whole develop tools(include Android Studio and SDK)，the problem is gone，thank for your effort.

For me it's not working i reinstall it again but it's not working
when i am running flutter doctor
Output: ******************************************************
C:\Users\z003n0dt>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel dev, v1.3.8, on Microsoft Windows [Version 10.0.17134.590], locale en-US)
\ Checking Android licenses is taking an unexpectedly long time...Error retrieving device properties for ro.product.cpu.abi:
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.3)
[√] VS Code, 64-bit edition (version 1.32.1)
[√] Connected device (1 available)
• No issues found!

You can see here Error retrieving device properties for ro.product.cpu.abi: Error and my device is connected with Andriod studio.
Currently i am using adb version 1.0.39 and
Following the Error from Android studio :

Error retrieving device properties for ro.hardware:
Launching lib\main.dart on ONEPLUS A6000 in debug mode...
Initializing gradle...
Resolving dependencies...
--------- beginning of main
03-10 18:14:09.910<EMAIL_ADDRESS> 691): Release wakelock is released
Unhandled exception:
Exit code -1073740940 from: D:/Mobile-Dev/src/Andriod/SDK\platform-tools\adb -s 5df11745 shell -x logcat -v time -t 1
#0      _runWithLoggingSync (package:flutter_tools/src/base/process.dart:352:7)
#1      runCheckedSync (package:flutter_tools/src/base/process.dart:283:10)
#2      AndroidDevice.lastLogcatTimestamp (package:flutter_tools/src/android/android_device.dart:507:27)
#3      _AdbLogReader._start (package:flutter_tools/src/android/android_device.dart:681:41)
#4      _runGuarded (dart:async/stream_controller.dart:805:24)
#5      _BroadcastStreamController._subscribe (dart:async/broadcast_stream_controller.dart:213:7)
#6      _ControllerStream._createSubscription (dart:async/stream_controller.dart:818:19)
#7      _StreamImpl.listen (dart:async/stream_impl.dart:472:9)
#8      FlutterDevice.startEchoingDeviceLog (package:flutter_tools/src/resident_runner.dart:261:71)
#9      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:304:5)

#10     HotRunner.run (package:flutter_tools/src/run_hot.dart:295:39)

#11     AppDomain.startApp. (package:flutter_tools/src/commands/daemon.dart:393:23)
#12     AppDomain.launch. (package:flutter_tools/src/commands/daemon.dart:452:26)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:142:29)

#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)

#19     AppInstance._runInZone (package:flutter_tools/src/commands/daemon.dart:835:20)
#20     AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:450:15)

#21     AppDomain.startApp (package:flutter_tools/src/commands/daemon.dart:387:12)

#22     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:281:38)

#23     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:545:18)
#24     _asyncThenWrapperHelper. (dart:async/runtime/libasync_patch.dart:77:64)
#25     _rootRunUnary (dart:async/zone.dart:1132:38)
#26     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#27     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#28     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#29     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#30     Future._complete (dart:async/future_impl.dart:473:7)
#31     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#32     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#33     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#34     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#35     _asyncThenWrapperHelper. (dart:async/runtime/libasync_patch.dart:77:64)
#36     _rootRunUnary (dart:async/zone.dart:1132:38)
#37     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#38     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#39     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#40     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#41     Future._complete (dart:async/future_impl.dart:473:7)
#42     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#43     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#44     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#45     AndroidDevice.targetPlatform (package:flutter_tools/src/android/android_device.dart)
#46     _asyncThenWrapperHelper. (dart:async/runtime/libasync_patch.dart:77:64)
#47     _rootRunUnary (dart:async/zone.dart:1132:38)
#48     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#49     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#50     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#51     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#52     Future._complete (dart:async/future_impl.dart:473:7)
#53     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#54     _AsyncAwaitCompleter.complete. (dart:async/runtime/libasync_patch.dart:33:20)
#55     _rootRun (dart:async/zone.dart:1124:13)
#56     _CustomZone.run (dart:async/zone.dart:1021:19)
#57     _CustomZone.bindCallback. (dart:async/zone.dart:947:23)
#58     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#59     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#60     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#61     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

Reinstall Android and SDK don't work for me.

I revoked "USB debugging authorizations" in developer options on the phone a than reconnected the phone to the computer and allowed debugging on that device once again. Now it's working again.

For me, disconnecting the phone from the USB, and the running those commands solved the issue
adb kill-server
adb start-server


github oauth2 error 401 - jwt: no primaryInstance auth provider found in default context

I have followed github OAuth2 config as per README file. My caddyfile (caddy v2) looks like this.
{
	http_port 4050
	https_port 4051
	# auto_https off
}

https://beta.example.com:4051 {
  	root * /var/srv

	## https
	tls /etc/ssl/mycert.pem /etc/ssl/mycert.key

	basicauth /* bcrypt "Restricted" {
		user1 <hashed pwd1>
		user2 <hashed pwd2>
	}

	file_server browse {
		hide *.conf *.txt
		index index.html index.htm
	}

	encode zstd gzip

	handle_errors {
		rewrite * /{http.error.status_code}.html
		file_server
	}

	header {

		# Replace http with https
		Location http:// https://

		# enable HSTS
		Strict-Transport-Security max-age=31536000;

		# disable clients from sniffing the media type
		X-Content-Type-Options nosniff

		# clickjacking protection
		X-Frame-Options DENY

		# keep referrer data off of HTTP connections
		Referrer-Policy no-referrer-when-downgrade
	}

	log {
		output file /var/logs/caddy2/access.log {
			roll_size 200mb
			roll_keep 5
			roll_keep_for 720h
		}

		format console

		level ERROR
	}

	## reverse proxy servers
	route /proxy1/* {
		uri strip_prefix /proxy1
		reverse_proxy localhost:6000
	}

	route /proxy2/* {
		uri strip_prefix /proxy2
		reverse_proxy localhost:7000
	}

	## webdav
	route {
		rewrite /dav /dav/

		@intranet {
			protocol https
			method GET
			remote_ip <ALLOWED_IP_RANGE>

			## disallow any of following
			not {
				method PUT DELETE
				remote_ip <ALLOWED_IP_RANGE>
				remote_ip <ALLOWED_IP1>
				remote_ip <ALLOWED_IP2>
			}
		}

		webdav @intranet {
			root /scratch/dav
			prefix /dav
		}

		file_server @intranet browse {
			hide *.txt *.md
			index index.html index.htm
		}
	}

	## OAuth2
	route /auth* {
		auth_portal {
			backends {
				github_oauth2_backend {
		          method oauth2
		          realm github
		          provider github
		          client_id Iv1.XXXXXXXXXXXXX
		          client_secret dummysdfo8sdfncs9usffsdfjfsd8yfsdufnsd87fgsdb
		          scopes user
		          user github.com/foo add role superuser
        		}
			}
		}
	}

	## Secure /vault using OAuth2 while serve rest of website using basicAuth
	route /vault* {
		jwt {
			auth_url /auth/oauth2/github
			allow roles superuser
		}
		respond * "github oauth2 sso" 200
	}
}

I have also setup github app per instructions with a callback URL: https://beta.example.com:4051/auth/oauth2/github/authorization-code-callback
When visiting https://beta.example.com:4051/vault/, I get 401 error after entering valid basic auth credentials. However, it does not redirect me to OAuth2 login. Also, I can visit https://beta.example.com:4051/auth and can successfully login via github OAuth2 but still I get an error 401  visiting https://beta.example.com:4051/vault/
While I have successfully used caddy v1 with https://github.com/tarent/loginsrv for github oauth2 login flow, I am new to caddy2 schema.
Caddy2 error log shows following:
2020/10/07 15:36:17.364 ERROR   http.authentication.providers.jwt       authorization provider provisioning error {"instance_name": "jwt-1", "error": "no primaryInstance authorization provider found in default context when configuring jwt-1"}
2020/10/07 11:36:17 [ERROR] Authenticating with jwt: no primaryInstance authorization provider found in default context when configuring jwt-1

And detailed access.log showing following:
# XXXXXXXXXXX	error	http.log.access.log0	handled request	{"request": {"remote_addr": "XXXXXXXXXXX", "proto": "HTTP/2.0", "method": "GET", "host": "beta.example.com:4051", "uri": "/vault", "headers": {"Accept-Language": ["en-US,en;q=0.9,hi;q=0.8,gu;q=0.7"], "Cookie": ["access_token=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX; backTo=https://beta.example.com:4051/vault"], "Upgrade-Insecure-Requests": ["1"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.XXXX Safari/537.36"], "Sec-Fetch-Site": ["none"], "Sec-Fetch-Mode": ["navigate"], "Accept-Encoding": ["gzip, deflate, br"], "Authorization": ["Basic XXXXXXXXXXXX=="], "Accept": ["text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9"], "Sec-Fetch-User": ["?1"], "Sec-Fetch-Dest": ["document"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "h2", "proto_mutual": true, "server_name": "beta.example.com"}}, "common_log": "<REMOTE_IP> - user1 [07/Oct/2020:11:19:20 -0400] \"GET /igv HTTP/2.0\" 500 4315", "duration": 0.000333441, "size": 4315, "status": 500, "resp_headers": {"Referrer-Policy": ["no-referrer-when-downgrade"], "Strict-Transport-Security": ["max-age=31XXXXX;"], "X-Content-Type-Options": ["nosniff"], "X-Frame-Options": ["DENY"], "Etag": ["\"XXXXXX\""], "Content-Type": ["text/html; charset=utf-8"], "Server": ["Caddy"]}}

@sbamin , the issue is that your portal and jwt plugins are misconfigured.

@sbamin , posting details ...

@sbamin , please take a look at this and this.

@sbamin , you need something along these:
	## OAuth2
	route /auth* {
		auth_portal {
			backends {
				github_oauth2_backend {
		          method oauth2
		          realm github
		          provider github
		          client_id Iv1.XXXXXXXXXXXXX
		          client_secret dummysdfo8sdfncs9usffsdfjfsd8yfsdufnsd87fgsdb
		          scopes user
		          user github.com/foo add role superuser
        		}
			}
      jwt {
  token_name access_token
  token_secret 0e2fdcf8-6868-41a7-884b-7308795fc286
  token_issuer e1008f2d-ccfa-4e62-bbe6-c202ec2988cc
  token_lifetime 3600
}
		}
	}

	## Secure /vault using OAuth2 while serve rest of website using basicAuth
	route /vault* {
		jwt {
      primary yes
      trusted_tokens {
        static_secret {
          token_name access_token
          token_secret 0e2fdcf8-6868-41a7-884b-7308795fc286
          token_issuer e1008f2d-ccfa-4e62-bbe6-c202ec2988cc
        }
      }
			auth_url /auth/oauth2/github
			allow roles superuser
		}
		respond * "github oauth2 sso" 200
	}

@sbamin , the important this is that token_secret matches between jwt and portal. Please keep me posted on your progress.

Thanks @greenpau
I am now able to get past err 401 but visiting /vault/ now gives me github oauth2 sso while HTTP status showing 200. Log was showing invalid jwt signature but I double checked token_secret in both jwt and auth_portal, and they are identical.

I am now able to get past err 401 but visiting /vault/ now gives me github oauth2 sso while HTTP status showing 200. Log was showing invalid jwt signature but I double checked token_secret in both jwt and auth_portal, and they are identical.

@sbamin , once authenticated, please go to /auth/whoami and post what you see. It should be the content of you token.

@sbamin . also, are you using the latest version of portal?

I build caddy2 from its website on Oct 5.
{
  "authenticated": true,
  "exp":<PHONE_NUMBER>,
  "iat":<PHONE_NUMBER>,
  "iss": "https://beta.example.com:4051/auth/oauth2/github/authorization-code-callback",
  "nbf":<PHONE_NUMBER>,
  "origin": "https://api.github.com/user",
  "roles": [
    "anonymous",
    "guest",
    "everyone",
    "labusers"
  ],
  "sub": "github.com/sbamin"
}

@sbamin , please rebuild with the latest.
Also, I think the issue is with. You should remove it ... It is what causes the 401.
	basicauth /* bcrypt "Restricted" {
		user1 <hashed pwd1>
		user2 <hashed pwd2>
	}

Then, reconfigure other endpoint to use jwt.

got cha and just noticed that in access.log as basicauth and not jwt secret was being passed in header. Let me reconfigure and check how it goes. Thanks for helping out here.

@sbamin , see https://github.com/greenpau/caddy-auth-jwt#caddyfile for reference. First jwt mention should be primary. The rest are non-primary.

I removed basicauth and followed same schema as https://github.com/greenpau/caddy-auth-jwt#caddyfile but getting a plain text message (HTTP 200 OK) with github oauth2 sso with invalid jwt signature. I removed cookies, and started a new session incognito mode but no luck. I will debug more after reading your docs and let you know how it goes.
2020/10/07 15:39:26.387 INFO    watcher config file changed; reloading  {"config_file": "Caddyfile"}
2020/10/07 15:39:26.388 INFO    using provided configuration    {"config_file": "Caddyfile", "config_adapter": ""} Authenticating with jwt: [signature is invalid]

Authenticating with jwt: [signature is invalid]

@sbamin , is it possible you have another JWT token in your cookies?

@sbamin , just a suggestion. First, enable debugging:
{
	http_port 4050
	https_port 4051
	# auto_https off
        debug
}

Next, use trace plugin to get better output: https://github.com/greenpau/caddy-trace#getting-started

Enabled debug and trace plugin. Following is after I get github oauth2 sso when visiting beta.example.com:4051/vault/. If I fall back to caddy v1 with OAuth2 based on https://github.com/tarent/loginsrv, same /vault path works.
2020/10/07 20:11:05.288	INFO	http.log.access.log0	handled request	{"request": {"remote_addr": "XXXXX:49945", "proto": "HTTP/2.0", "method": "GET", "host": "beta.example.com:4051", "uri": "/vault", "headers": {"Accept-Language": ["en-US,en;q=0.5"], "Accept-Encoding": ["gzip, deflate, br"], "Dnt": ["1"], "Cookie": ["access_token=XYZXYZXYZ......"], "Upgrade-Insecure-Requests": ["1"], "Te": ["trailers"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Firefox/78.0"], "Accept": ["text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "h2", "proto_mutual": true, "server_name": "beta.example.com:4051"}}, "common_log": "XXXXXX - - [07/Oct/2020:16:11:05 -0400] \"GET /vault HTTP/2.0\" 200 17", "duration": 0.000529221, "size": 17, "status": 200, "resp_headers": {"Server": ["Caddy"], "Referrer-Policy": ["no-referrer-when-downgrade"], "Strict-Transport-Security": ["max-age=31536000;"], "X-Content-Type-Options": ["nosniff"], "X-Frame-Options": ["DENY"], "Content-Type": []}}

Following is after I get github oauth2 sso when visiting beta.example.com:4051/vault/.

@sbamin , do you see all of the JWT instances successfully initialize?

2020/10/07 20:11:05.288	INFO	http.log.access.log0	handled request	...

@sbamin , this is not the log from trace plugin. That's native caddy v2 logging.

@sbamin . side note.
No need to do this ...
https://beta.example.com:4051 {

Rather,
beta.example.com {

opps! Looks like I don't have it in caddy2 binary. I will rebuilt and update tomorrow.
and can update with full log. AFAIK, jet directives were initialized w/o any error.

Is it ok to send you logs via email?

@sbamin , yes, email is fine. Please send the logs and config.

Thanks and just sent.

This now closed. @sbamin , when you get a chance please post your working config.

Thanks @greenpau
Here is  a working Caddyfile for caddy v2, https://gist.github.com/sbamin/1450d11044c4fc750268c2e7772940c9 It enables OAuth2 for static files under /vault* and a webDAV server under /mango* while keep rest of the contents without any authentication. You may set caddy2 directive, basicauth to protect rest of contents.
Main issue with my original Caddyfile was a wrong directive: respond * "github oauth2 sso" 200.
	route /vault* {
		jwt {
			auth_url /auth/oauth2/github
			allow roles superuser
		}
		respond * "github oauth2 sso" 200
	}

The correct directive to browse static files was file_server, e.g.,
		jwt {
			auth_url /auth/oauth2/github
			allow roles superuser
                        ## additional configs
		}
		file_server browse {
			index index.html index.htm
		}

Also, OAuth2 configurations should precede rest of configurations, and the default route  with/* path must be written at the last.


Create Select component

Features

Controlled component
Separators (horizontal lines between lists of options, see radix-ui example)
Categories (label to group options together), see radix-ui and ant examples.
disabled options
Keyboard navigation (handled by radix-ui)

API

Label can be anything (ReactNode)
Find selected element by comparing the value property

<Select
  selected={{label: 'Apple, value: 'apple'}}
  onSelect={(option) => {
    console.log(option); // {label: 'Banana', value: 'banana'}
  }

  // First level of array controls where dividers are placed
  options={[
    [
      // options with categories
      {
        label: 'Fruit',
        options: [
          { label: 'Banana', value: 'banana' },
          { label: 'Apple', value: 'apple' },
        ],
      },
      {
        label: 'Vegetables',
        options: [
          { label: 'Carrot', value: 'carrot' },
          { label: 'Broccoli', value: 'broccoli' },
        ]
      }
    ],
    [
      // options without categories
      {label: 'Beef', value: 'beef'},
      {label: 'Pork', value: 'pork', disabled: true},
      {label: 'Chicken', value: 'chicken'},
    ]
  ]}
/>

Design
As for all react-science components, should be designed with compactness in mind. Use blue / gray as the base colors.
You can get inspired by:

Radix-ui: https://www.radix-ui.com/docs/primitives/components/select#select
Ant design: https://ant.design/components/select

Requirements:

Use radix-ui: https://www.radix-ui.com/docs/primitives/components/select#select

Closed by https://github.com/zakodium-oss/react-science/pull/495


Anyone getting this thing where their game freezes for a bit then suddenly the skin is gone? then if you press Ins the skin choices are sudddenly different from the champ

I was playing swain yesterday and the game was lagging for a bit then it suddenly notified that I reconnected and I had default skin again, when I press Ins I had rengar skins as choices, this has also been an old thing with the previous r3nzskin before vanguard also

Happens to me as well, pretty much every game.

thats normal the R3nzskill is like that too u just gotta go to global and changer ur skin there


Not supported characters in the manga name and the file structur

Hi i found a bug where under windows the folder cant be created because there are unsupported characters in the manga name string.
So these characters are important to be replaced NUL, , /, :, *, ?, ", <, >, |
https://stackoverflow.com/questions/4814040/allowed-characters-in-filename
getting uuid.
fetching manga info 'Title' 'description' 'status' based on your language setting.
No altTitles with that language found; using default title.
fetching chapters info 'available languages' 'available volumes if any' 'available chapters' 'total chapters (language independent)'.
-------------------------------------------
Ore no Genjitsu wa Ren’ai Game?? ka to Omottara Inochigake no Game datta
-------------------------------------------
fetching 'chapter list by language' 'total chapters by language.'
found 209 out of 327 for en
getting a server url to download the images from.
starting download
Traceback (most recent call last):
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex-py.py", line 4, in <module>
    main()
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\util.py", line 16, in main
    file_main(args.File, langwithindex, args.quality_mode, args.destination, args.max_threads)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\file_main.py", line 11, in file_main
    main(url_name[0], langWithIndex, quality_mode, Manga_main_dir, thread)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\main.py", line 25, in main
    download.main(title, chap_list, desc, status, quality_mode, base_url, Manga_main_dir, thread)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\download.py", line 47, in main
    create_manga_dir(manga_title, Manga_main_dir)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\fs.py", line 16, in create_manga_dir
    os.makedirs(os.path.join(current_working_dir, Manga_main_dir, manga_title))
  File "C:\Users\Linus\AppData\Local\Programs\Python\Python39-32\lib\os.py", line 225, in makedirs
    mkdir(name, mode)
OSError: [WinError 123] Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch: 'C:\\Users\\Linus\\Desktop\\Mangadex\\mangadex-py-master\\Manga\\Ore no Genjitsu wa Ren’ai Game?? ka to Omottara Inochigake no Game datta'

i'll fix it right away.

should be fixed.

I am still getting this error, even with the fix:
skipping chapter-28.3.zip
getting uuid.
fetching manga info 'Title' 'description' 'status' based on your language setting.
No altTitles with that language found; using default title.
fetching chapters info 'available languages' 'available volumes if any' 'available chapters' 'total chapters (language independent)'.
fetching 'chapter list by language' 'total chapters by language.'
found 209 out of 327 for en
getting a server url to download the images from.
starting download
writing json
Traceback (most recent call last):
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex-py.py", line 4, in <module>
    main()
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\util.py", line 16, in main
    file_main(args.File, langwithindex, args.quality_mode, args.destination, args.max_threads)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\file_main.py", line 11, in file_main
    main(url_name[0], langWithIndex, quality_mode, Manga_main_dir, thread)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\main.py", line 22, in main
    download.main(title, chap_list, desc, status, quality_mode, base_url, Manga_main_dir, thread)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\download.py", line 47, in main
    write_series_json(manga_title, description, status, Manga_main_dir)
  File "C:\Users\Linus\Desktop\Mangadex\mangadex-py-master\mangadex_py\fs.py", line 92, in write_series_json
    with open(series_json, "w", encoding='utf-8') as f :
OSError: [Errno 22] Invalid argument: 'C:\\Users\\Linus\\Desktop\\Mangadex\\mangadex-py-master\\Manga\\Ore no Genjitsu wa Ren’ai Game?? ka to Omottara Inochigake no Game datta\\series.json'

now the filtered title will be used globally can you check if it's working ?

It is working now!

okay i'll close the issue.


Defining custom properties in mixins

I have read through all open issues about mixins, but I can't find anything about the fact that custom properties do not seem to work in mixins.
And before you criticize this isn't necessary (as someone else did):

It doesn't make sense from a usage point of view that they behave differently
Let me give en example where I need it, I have a <paper-datatable> with checkboxes in it ( http://david-mulder.github.io/paper-datatable/components/paper-datatable/demo/theming.html ). If I next wish to allow the user to change only the <paper-checkbox> in the header I would have to expose custom variables for every variable of <paper-checkbox>

Sorry, I'm not sure what you mean by custom properties "don't seem to work" in mixins.
Can you post a small JSBin sample that points out what you mean?

Oh wow, never saw the reply, my bad, here you go:
http://jsbin.com/jucavikiju/edit?html,output

Spec-wise, I'm not sure if you're supposed to be able to define a custom property in a mixin. This could also be a parsing bug on our end. @sorvell will know.
In the meantime, you can define classes for specific paper-card/paper-checkbox to style them differently:
:root{
      --some-mixin: {
        color: green;
      };
    }
    paper-card.yellow {
      --paper-card-header-color: yellow;
      @apply(--some-mixin);
    }

Defining a custom property within another custom property is not something
Polymer currently supports. Since the @apply native feature is still
being spec'd, it's unclear if it will be available in a future native
implementation.
On Sun, Dec 20, 2015 at 9:32 AM, Eric Bidelman<EMAIL_ADDRESS>wrote:

Spec-wise, I'm not sure if you're supposed to be able to define a custom
property in a mixin. This could also be a parsing bug on our end. @sorvell
https://github.com/sorvell will know.
In the meantime, you can define classes for specific
paper-card/paper-checkbox to style them differently:
:root{
--some-mixin: {
color: green;
};
}
paper-card.yellow {
--paper-card-header-color: yellow;
@apply(--some-mixin);
}
—
Reply to this email directly or view it on GitHub
https://github.com/Polymer/polymer/issues/2740#issuecomment-166138124.

I am closing this issue as a wont-fix, as this is an upstream issue for the apply specification. If you would like to contribution to the spec, please check it out at https://tabatkins.github.io/specs/css-apply-rule/, although I am not sure if the specification has a champion still.


Is there a way to change the accent color?

Changing the accent color doesn't change the standard cyan.

This should be fixed now. However to have more flexibility, I recommend installing Style Settings.

This should be fixed now. However to have more flexibility, I recommend installing Style Settings.

Thank you! Very fast support!


🐛 BUG: Astro files no intellisense for import component/new created files

Describe the Bug
This bug has become normal in Astro now and I think it needs serious consideration.
Whenever you work with Astro files the files that have an extension (.astro) have no IntelliSense for CSS and now for components or files.
The scenario:
I created a new component for example
new.astro or new.jsx or new.tsx
if I tried to import this component in any old .astro file no IntelliSense and even when I use the path to reach the file like
../../ >> I get no directory like the directory is not or not created, i checked double and trouble the files, and they and working because I can add the path myself like writing down the path without autocomplete so it works even Astro show me there is no file it imported the component and it's working, Sometimes even it gives me an error that the module can't be found while it's imported and working!!
The reason I became sure 100% that this problem only belongs to .astro files is that it never happens with any other framework outside or even inside Astro
I use Astro with React, all the .jsx/.tsx files work fine and great no problem of any kind even with React inside Astro. It's crystal clear there is a problem with it.Astro files import and before that, I reported the CSS IntelliSense is not working too all the time i even now use .css files as a solution for this.
I did a reproduction here
Reproduceand it contains all the problems with this one too.
I will try my best to record a video or screenshot of the problem but it needs serious consideration.
> astro "info"

  Astro                    v4.3.1
  Node                     v20.9.0
  System                   Linux (x64)
  Package Manager          pnpm
  Output                   server
  Adapter                  none
  Integrations             @astrojs/react
                           astro-icon

While I checked the old issues I found this one
https://github.com/withastro/language-tools/issues/707#issue-2004337612
it's the same problem typically, from December and it's still
As he described, all the services are crashing constantly astro ts, and this is in Astro only.
But now it reached the CSS intellisense service too.

Everything works just fine for me in your reproduction, so unfortunately, I don't really know what the issue is. The only issue I notice in your repro is the same one as this issue https://github.com/withastro/language-tools/issues/685
I'm sorry, I'm not really sure how to help.

It's here too, so I'm not the only one
https://github.com/withastro/language-tools/issues/707
as it's typically the same problem and as I see in this issue too no solution.
Sadly, I was hoping to use Astro as our main framework for production projects at work but with this situation, we can't continue with that, any of us can work while there are constant crashes and no IntelliSense
For the reproduction, we moved it to Nextjs yes as we reached a dead end with Astro. After a search, we found many complaints on Reddit and Twitter about the typescript ls crashes in Astro and this explains everything.
I think this needs more and deeper investigation in the future.
Thanks for your help and support. 🙏

No worries, sorry it didn't work. Hopefully I'll eventually be able to reproduce the issue and fix it. It's quite likely the issue is somewhat isolated or we'd get much more reports (we have thousands of users and the same code powers Vue's extension, that has millions of users), but unfortunately I can't quite tell what the common factor is.

Closing this issue because it seems to be a mix of two previously reported ones, namely #707 and #685

I have the same problem, it seems to happen only on linux.

I have the same problem, it seems to happen only on linux.

Your point about Linux makes me wonder because yes I only use Linux and I don't have any other OS to test with.
Even all the team uses Linux.
Can you test this in another OS if you can Like Mac or Windows?
I did some deep dubbing yesterday and today too,
First, we used Vue as they said they are using the same code as Vue but Vue works perfectly and has no problems like Astro - again and again it's only Astro-Related problem.
I even used Vue for continuous 3 hours deleting editing and creating files and code with no problem like this!
Another thing I found is that the Astro dev server lags horribly after some time of use, But as I member this never happened in the previous realizes, This issue started to be very vague after the last 3-4 releases, before that and I never encountered that and Astro was never lagging or slow like now.

I have the same problem, it seems to happen only on linux.

Another point I was suspecting before moving the project to Nextjs completely, Is that I remember  something that could maybe help detect this problem
1- Try to remove any Image component (Astro Image) and use only the regular img element
2- If you are using any SSR/Hybrid remove and use the default.
Test both solutions, maybe could work for you.
Here's why I'm suspecting both this:
Long story short: When Nextjs 13 was released I faced the same problem with lags and hangs but it wasn't like what is in Astro but very close and turns out that the Next Image component was using a server for image optimization that did this whole problems of lag and hangs.
Another thing I remember the Next team at that time detected some Nodejs workers were causing most of the problems too.
But as I understand Astro uses Vite which uses Go not node!
Hope you can find a solution, but unfortunately reached a dead end it was time-consuming and frustrating, and not like it will be solved any soon.

https://github.com/withastro/language-tools/issues/707#issuecomment-1820998136
Wow, it looks like it's getting worse and others reporting the same problem with ts and you here saying where the others=, they are in the issue you replayed to?!
I'm shocked!! you replied to a user who facing the same issue with the ts LSP for astro crashing and replay to me here where the others!!

Now I'm really confused you said you did test on every OS, and users here saying they face it on every OS?!
Bottom Line: There is a real issue with the LSP or Astro Extension or maybe both, you yourself can't reach the issue OK fine, Bu others are facing it and it's real you can't reproduce it Ok fine but it's happening to others.
End of line

The issue you linked is not the same one, the majority of those users are reporting about new files not appearing in auto imports, not that they're losing all kinds of intellisense, which is what you seem to be reporting.
Same thing for the tsserver crashes, it's not the same issue. The tsserver can crash without the language server stopping, and vice versa.
I tried on Arch Linux, last version of everything (as expected on Arch)
Please understand that I am alone on this project, it is not my main project at Astro (Astro itself is), no one else in the Astro team works on it and I receive 1 or 2 external contributions per year.
I'm trying my best to fix people's issues, I do not have the time to do 1:1 calls regarding people's specific setups when the issues are this isolated. Thousands and thousands of people use this project every day, if an issue like was super prevalent, there would be hundreds of reports.


Can deamonless accelctl parse parameter directly?

Can the parameters of deamonless accelctl be passed directly on the
command line instead of through the configuration file?
For example, referring to the practice of crictl, the auth parameter
is made into the following form:
crictl pull --auth "xxxx" image-name
deamonless accelctl also adds a "--auth" parameter, and other
parameters are similar.

Acceleration-Service is a general service to support image acceleration, and accelctl is mainly to manage acceleration service. The accelctl convert can do image conversion in one-time mode, but we don't recommend using accelctl alone.
If we need a better one-time conversion experience, why not use an image-specific conversion tool? Such as nydusify or nerdctl image convert.

It may be possible to support reading registry auth from the docker config.

It may be possible to support reading registry auth from the docker config.

If we support reading registry auth from the docker config, other driver configs also need config file. See https://github.com/goharbor/acceleration-service/blob/main/pkg/config/config.go#L82C6-L82C19

Anyway, support reading registry auth from the docker config is a good idea.


(ISO 6709) PDF: missing copyright warning symbol

As per @manuel489 : https://github.com/metanorma/iso-6709/issues/13
Original:

Generated:

Xslt renders copyright warning symbol (static image in xslt) before the text 'COPYRIGHT PROTECTED DOCUMENT' from boilerplate/copyright-statement/clause/title. Here is example from mn-samples-iso repository:

(see two month ago generated xml and pdf:
https://github.com/metanorma/mn-samples-iso/blob/gh-pages/documents/international-standard/rice-en.fdis.presentation.xml
https://github.com/metanorma/mn-samples-iso/blob/gh-pages/documents/international-standard/rice-en.fdis.pdf)
But in ISO 6709 presentation xml the element boilerplate/copyright-statement/clause/title is missing:

ping @opoudjis

In https://github.com/metanorma/metanorma-iso/issues/587, the update to the 2022 Simple ISO template meant the removal of the COPYRIGHT PROTECTED DOCUMENT heading. I had no reason at the time to think that would not apply to all stages, and to be blunt, I still don't.
I am not going to put it back in until I have an explicit statement, from ISO, overriding the 2022 Simple ISO template, and an indication of where it is to be ridden. My assumption until then is that you are working off a Word document generated following 2021 rules, which is invalid.
And this is why I keep insisting on official statements from ISO editors, and not random documents they generated last year.

In https://github.com/metanorma/metanorma-iso/issues/587, the update to the 2022 Simple ISO template meant the removal of the COPYRIGHT PROTECTED DOCUMENT heading. I had no reason at the time to think that would not apply to all stages, and to be blunt, I still don't.

The "ISO Simple Template" is different from the Edited DIS template.
Published PDF documents do not use the "ISO Simple Template", at all.

The contents of the ISO Simple Template have no bearing to the Edited DIS or the resulting PDF.

This is no way to run a project.
Reinserting the title into the copyright boilerplate if Stage < 40. (ref https://github.com/metanorma/metanorma-iso/commit/7c596d57041164baa46882cb15ab945ef47cba7a)

I think we just want to separate the generation of templates. The ISO Simple Template does not have the copyright statement.
The Edited DIS has a copyright statement. I believe the XML should be identical. It’s only the rendering of the Simple Template does not render it.

Since I did not change the copyright template other than the title of the copyright statement, I don't see what else I need to do here:
<boilerplate>
  <copyright-statement>
      {% if stage_int >= 40 %}
      <title>COPYRIGHT PROTECTED DOCUMENT</title>
      {% endif %}
    <clause>

© {{ agency }} {{ docyear }}

    All rights
    reserved. Unless otherwise specified, or required in the context of its implementation,
    no part of this publication may be
reproduced or utilized otherwise in any form or by any means, electronic or
mechanical, including photocopying, or posting on the internet or an intranet,
without prior written permission. Permission can be requested from either ISO
at the address below or ISO's member body in the country of the requester.

    ISO copyright office

    CP 401 • Ch. de Blandonnet 8

    CH-1214 Vernier, Geneva

    Phone:  + 41 22 749 01 11

    Email<EMAIL_ADDRESS>    Website: www.iso.org

    Published in Switzerland

</clause>
  </copyright-statement>

  {% if unpublished %}
  <license-statement>
    <clause>
<title>Warning for WDs and CDs</title>

This
document is not an ISO International Standard. It is distributed for review and
comment. It is subject to change without notice and may not be referred to as
an International Standard.

Recipients
of this draft are invited to submit, with their comments, notification of any
relevant patent rights of which they are aware and to provide supporting
documentation.

</clause>
  </license-statement>
{% endif %}
</boilerplate>

I will note that the published samples you sent me DO NOT include the COPYRIGHT PROTECTED DOCUMENT title, as you can see, but I am at this stage so sick of the ongoing clusterfuck lack of clarity around DIS rendering, that I'm just doing what you told me.


Update ERC-5564: Move to last call

When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:

The PR edits only existing draft PRs.
The build passes.
Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside .
If matching on email address, the email address is the one publicly listed on your GitHub profile.

Merged in https://github.com/ethereum/ERCs/pull/322#event-12494867858


Please define outside collaborators in code

Hi there
We now have a process to manage github collaborators in code:
https://github.com/ministryofjustice/github-collaborators/blob/main/README.md#github-outside-collaborators
Please follow the procedure described there to grant @duncancrawford access to this repository.
If you have any questions, please post in #ask-operations-engineering on Slack.

Outside collaborator not required


metamaps database

This PR includes a database for metamaps

@henningonsbring DB.fa and DB_proteins.faa files seem to have the same sequence?

@ramprasadn I will look into this. DB.fa is a file made by me. The DB_proteins.faa is made by MetaMaps when their create database process in invoked.

thanks for comments @ramprasadn and @jfy133
I updated according to @jfy133 suggestion and uploaded a tar file


[BUG] Build is broken

Example: https://github.com/sdatkinson/neural-amp-modeler/actions/runs/6306868146
I think it's the fault of a new ONNX version

This is a known issue and will be patched: https://github.com/microsoft/onnxruntime/issues/17631
Once that happens we can get back on board.


No error handling information related to Copy activity when using Odata as your connector

[[There is no information on handling Copy Data error related to source when using Odata as your connector. For example;

Operation on target Copy Statements failed: Failure happened on 'Source' side. 'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Requesting response from path Statements and query $filter=RowChangedDatetime gt 2021-06-30T15:59:57.0000000Z failed with status code Unauthorized and message .,Source=Microsoft.DataTransfer.Runtime.ODataConnector,'

]]

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

ID: 8193f2a3-80f3-14e9-7022-27ea5fa02001
Version Independent ID: 9eff4721-c265-74a7-11fd-c6920f309982
Content: Copy data from OData sources by using Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/connector-odata.md
Service: data-factory
GitHub Login: @jianleishen
Microsoft Alias: jianleishen

@Ipmac - Thanks for brining this to our attention. We will investigate it further and update you shortly.

@lpmac
Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

Thanks for reporting this issue @lpmac.  Can you provide some more context on this failure?  The OData connector appears to be surfacing the underlying error returned from the OData source, so investigation at the source might be necessary too.  I do notice the error mentions Unauthorized, so this might indicate some problem with the authentication provided to the source.  I will go ahead and close this issue out for now but we can continue the discussion here if necessary.
#please-close


Cannot use both '--mode=' and deprecated options that specify mode.

Github Action building a Python release build generates the following failure for both Linux and Windows:
Successfully installed nuitka-2.5.5
...
Nuitka-Options: Used command line options: --output-dir=. --output-file=erriez-midi-sysex-io-linux --include-data-dir=images=images --include-data-dir=data=data --standalone --onefile --mode=app --assume-yes-for-downloads --script-name=main.py --enable-plugins=pyside6
FATAL: Cannot use both '--mode=' and deprecated options that specify mode.

Github action build config: build-release.yml
      - name: Build Linux executable
        if: runner.os == 'Linux'
        uses: Nuitka/Nuitka-Action@main
        with:
          script-name: main.py
          output-dir: .
          output-file: erriez-midi-sysex-io-linux
          include-data-dir: |
            images=images
            data=data
          standalone: true
          onefile: true
          enable-plugins: pyside6

      - name: Build Windows executable
        uses: Nuitka/Nuitka-Action@main
        with:
          script-name: main.py
          output-dir: .
          output-file: erriez-midi-sysex-io.exe
          include-data-dir: |
            images=images
            data=data
          standalone: true
          onefile: true
          disable-console: true
          windows-icon-from-ico: images/midi.ico
          enable-plugins: pyside6

Buildlog: https://github.com/Erriez/midi-sysex-io/actions/runs/12125747829

FATAL: Cannot use both '--mode=' and deprecated options that specify mode.

The error message is unclear. If this mode cannot be used anymore, where is documented how to migrate existing projects to resolve this problem?

Funny thing; 1h ago was woking perfectly....

Last successful run: 28 October 2024 nuitka-2.4.11
First build error: 16 November 2024 nuitka-2.5

No project source modifications.

I can confirm that it still works without using "standalone" and/or "onefile" on Nuitka 2.5.5.
Tested on Windows and OSX.
PS: On windows is working with mode: standalone

Reproducible testcase on a Linux desktop (repeating commands from Github Action):
$ git clone git@github.com:Erriez/midi-sysex-io.git
$ cd midi-sysex-io/
$ virtualenv venv
$ . venv/bin/activate
$ pip install -r requirements.txt
$ pip install nuitka

$ nuitka --version
2.5.4
Commercial: None
Python: 3.12.3 (main, Nov  6 2024, 18:32:19) [GCC 13.2.0]
Flavor: Debian Python
Executable: ~/src/midi-sysex-io/venv/bin/python
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 24.04.1
Version C compiler: /usr/bin/gcc (gcc 13).

$ nuitka --output-dir=. --output-file=erriez-midi-sysex-io-linux --include-data-dir=images=images --include-data-dir=data=data --standalone --onefile --mode=app --assume-yes-for-downloads --script-name=main.py --enable-plugins=pyside6

Nuitka-Options: Used command line options: --output-dir=. --output-file=erriez-midi-sysex-io-linux
Nuitka-Options: --include-data-dir=images=images --include-data-dir=data=data --standalone --onefile --mode=app
Nuitka-Options: --assume-yes-for-downloads --script-name=main.py --enable-plugins=pyside6
FATAL: Cannot use both '--mode=' and deprecated options that specify mode.

https://nuitka.net/changelog/Changelog.html#new-features
UI: Introduced a new --mode selector to replace the options --standalone, --onefile, --module, and --macos-create-app-bundle.

And: https://github.com/Nuitka/Nuitka-Action/releases

This adds support for 2.5 new option mode, that shall be used over standalone, module or onefile options in the future.

Where is this migration of Github Action yaml file to Nuitka 2.5 documented?

What should I do to fix my project?

remove old standalone and onefile and just use
mode: standalone or --mode=standalone
Reading https://nuitka.net/changelog/Changelog.html#new-features, you should replace both --standalone --onefile with --mode=app

Thanks for your suggestion, but does not work:

Changes in https://github.com/Erriez/midi-sysex-io/commit/c647fe3a01e9e6ebca37c5702d41c9611d8c4f39
Buiild log: https://github.com/Erriez/midi-sysex-io/actions/runs/12128015446/job/33813517416

I've now set Nuitka to a fixed previous working version 2.4.11 and Github Nuitka-Action to v1.1. I don't want to get bothered by silent Nuitka API or command line changes where the error should be reverse engineered. Was this breaking API change really necessary? I do not see the value other than wasting time on fixing my projects.
I consider to replace Nuitka by another full open source tool which is non-commercial.
Closing ticket. I will not spend more time on this issue.

Strange... I see that in the build log, Nuitka automatically inserts --onefile even if in the file .yml is not specified...
Checking your log as soon as Nuitka-Actions invokes, automatically inserts 'onefile: true', it could be a git actions cache issue.
Your log:
Run<EMAIL_ADDRESS>  with:
    nuitka-version: [2](https://github.com/Erriez/midi-sysex-io/actions/runs/12128015446/job/33813517416#step:9:2).5.5
    script-name: main.py
    output-dir: .
    output-file: erriez-midi-sysex-io-linux
    include-data-dir: images=images
  data=data

    mode: standalone
    enable-plugins: pyside6
    working-directory: .
    onefile: true
    assume-yes-for-downloads: true
  env:
    ...

Your workflow file:
uses<EMAIL_ADDRESS>        with:
          nuitka-version: 2.5.5
          script-name: main.py
          output-dir: .
          output-file: erriez-midi-sysex-io-linux
          include-data-dir: |
            images=images
            data=data
          mode: standalone
          enable-plugins: pyside6

In my cases i get instead:
Run Nuitka/Nuitka-Action@main
  with:
    script-name: start.py
    mode: standalone
    output-filename: ***
    output-dir: dist
    windows-icon-from-ico: logo/logo.ico
    working-directory: .
    nuitka-version: main
    assume-yes-for-downloads: true

As you can see there is no extra onefile: true

The change is indeed necessary, why else would it have been done. You could have gone to the stable release of the Actions build, I believe it ought to be currently working for 2.5 still, but the defaults changed, onefile is not true by default anymore (and it had to be disabled to specify anything else), instead mode defaults to app, and should be used exclusively.

Ah, the old action, version 1.2 cannot use mode yet due to said default change, and introduces the default onefile. You would have to set it to false in order to use mode there. I think you must have not used the stable version, encountered an issue during the transition (it took me a while to Nuitka-Action main right I think, and maybe it still does not work, but I believe it does).
Sad to see that happening to you.
The --onefile adding was always automatic, a default mismatching proper Nuitka, and that was never good, however I think the original author deemed it unlikely, that people would not fall for using accelerated mode and be disappointed that it is then not standalone.
Also, with app as a mode, we do away with the differences between macOS and non-macOS for best deployment option, that will make life easier if you otherwise can have a shared action configuration for different OSes.
Thanks for being respectful where you are. Surely I didn't handle the transition as perfect as you want it to be. But all you had to do is to check the new docs and apply them, and it's not really a big read. The matter is, I am not getting any help with Nuitka Action, and so I am taking more risks there while developing a full blown Python compiler on the side.
But I think, indeed there is no issue really. Old setups should still work, provided they used the config as written in the docs, and new setups should still work.
As for transition, once I am happy with --mode (and it was really bad, e.g. app didn't work properly at all until hotfixes of Nuitka), I will deprecate the old options and tell people what to use instead. For now, I didn't deem it necessary.
Please open an issue, if there are unresolvable issues here. One thing I am lacking is a comprehensive test suite with Nuitka Action that tests modes and artifact construction as described in the docs, and an example for module mode to do packages. But who is going to create those? If we had those, it would make sense for me to have a "develop" branch and make changes there first.

I am leaving this open in hopes that here it will be more visible to potential helpers, it of course always was not a Nuitka issue, but a Nuitka-Action issue if anything.

I post this here, if not the right place feel free to say.
with nuitka 2.5.6 used by my actions, I got now this warning:
Nuitka-Options:WARNING: Using onefile specific option '--onefile-tempdir-spec' has no effect when '--onefile' is not specified.
--onefile option has been removed on my side and replaced with --mode=app
and I still need --onefile-tempdir-spec

That should be a false alarm, that you can ignore, I will look into it, and yes, a new issue would have been best, since there is a high risk I just forget about it.

@zak-45 in an action, this makes sense to have it for only when it applies, indeed --onefile-child-grace-time and currently (will be changed in the near future to not be onefile specific) --include-onefile-external-data have the same issue. For OS specific options the same will apply, so this is a goal to have, that conflicts with user awareness that this is bound to happen. I might have to disable these warnings when coming from GitHub Actions input or something like that.
Please create a separate issue for it, since it's really separate, and that's always the best option or else I will forget, ignore, or whatever comments unrelated to the main issue.


N+1 Eager Solution

Motivation
Currently, Loading Associations Strategy in pop introduce the N+1 problem for every association type (has_many, has_one, belongs_to, many_to_many).
Glossary

Association: A relationship existing in pop on a model to model level.
Loading Association Strategy: An implementation used for loading model associations.

Introduce Eager Mode
By defining an Eager Mode function developers can be able to induce pop to use a different approach for loading associations. People who used to develop web applications with Rails and ActiveRecord will realize there are different “modes” or ways to load models associations: Include, Preload and Eager. Each of them have its own strategy to load data associations and different ways to query database. This flexibility also makes sense to be implemented in Pop.
This blueprint is a proposal  I’ve been thinking of when trying to solve this need:

1. Define Eager Mode options.
These options will allow developers to change current loading association strategy. Developers will be able to change the overall strategy, meaning they can change the default behavior for all queries made by pop, or they can just change the loading association strategy for a particular Query.
EagerDefault: current implementation, the default behavior of pop. This one introduce N+1 problem and will be used as default value for backward compatibility.
EagerPreload: This mode works similar to Preload mode used in ActiveRecord.  Avoid N+1 problem by reducing the number of hits to the database but increase memory use to process and link associations to parent.
EagerInclude: This mode works similar to Include mode used in ActiveRecord. It uses Left Join clauses to load associations.
2. Activate Eager Mode.
Developers would use Eager Mode options in this way to change the loading association strategy.
// To change overall Eager Mode.
   pop.SetEagerMode(pop.EagerPreload)
// this will change the default loading associations strategy for
// all Eager queries to be in "Preload" mode. This should be
// used once, when setting up pop connection.

// To change query specific Eager Mode.
tx.SetEagerMode(pop.EagerDefault).Eager().Find(&user, id)
// this will change the default loading associations strategy
// for this specific query, not the one used overall.

This PR Introduces the implementation of two modes: EagerDefault(Already existing) and EagerPreload(WIP)
How to Test?

You can check Test Eager Preload Mode  to get an inside of how to test.
I really appreciate any help with this to give it a little more form and cover all posible test cases.

hi @larrymjordan the naming was the concern. previously i did point out that in rails, Eager means left join, while Preload means separated queries (which should not be n+1 issue, but using where condition)
if we use these names, then we shall not need to have Eager prefix

Is there any infrastructure in place for starting (Eager)Include?  This is the mode that I think is by far the most useful and flexible.  I think if this PR is going to land, it should come with both modes (and I'm willing to help, but need to know where the useful starting place is based on what you're pursuing here).

@u007 you are correct about naming, I'm open to hear options.  Regarding default behaviour, I agree N+1 solution should be the one, and with this design we could change it easily. Also remove current implementation gradually.
@gavbaa glad to hear about it. There are three parts you can check to make your start point:
1 - this method Query.eagerAssociations.  has the responsibility to decide which mode implementation to use.
2- In [Loading Options] (https://github.com/gobuffalo/pop/pull/146/files#diff-3ef3327702394ae04f1ba6329e0feb52R21) you can find all posibles mode a developer can use.
3- Developers can change the mode with Mode Changer Function
I'm pretty bad naming functions in a first try, lol,  but that's the idea to share and discuss and came out with a solution.

@larrymjordan maybe we can retain original Eager(), and add deprecation warning to ask user to rename to Preload, and
introduce:

EagerLoad() - which uses left join
Preload() - sub sequence query via Where IN condition

this shall solve the naming issue in a progressive deprecation method
what do you think?

@u007 totally agree. It makes more sense the intention of every method.

Any news on this one?

Hey, I'm building a heavily relation dependent system here and this could help me a lot (ATM i'm doing this by hand every time)

Julien,
Still watching this, still have a strong need for it, but I've run out of time in the short term to put direct effort in.  I'm trying to silo some time in October to take another swipe, but hoping someone else steps up and makes progress before then. :)

@larrymjordan thanks for putting this together, it looks great. Curious about the status of this? What would it take to get it over the finish line?

This is getting real Guys,  By enabling the  new EagerMode state to pop to be EagerPreload , you can reduce the number of queries that hit to the database. Here is an example showing the difference between the default eager loading and the new preload mode.
Given a many to many relationship between Parent and Student
student := Student{}
tx.Create(&student)

for i := 0; i < 2; i++ {
  parent := Parent{}
  tx.Create(&parent)
  tx.RawQuery("insert into parents_students(parent_id, student_id) values(?,?)", parent.ID.String(), student.ID.String()).Exec())
}

When we call default Eager:
parents := []Parent{}
tx.Eager().All(&parents)

A N+1 Problem is introduced. It iterates over every parent and hits the database to query every students list.
 // SELECT parents.created_at, parents.id, parents.updated_at FROM parents AS parents

// SELECT students.created_at, students.id, students.updated_at FROM students AS students WHERE id in (select student_id from parents_students where parent_id = '1569d42e-75a3-4d05-bf16-0f65bb729532')

//SELECT students.created_at, students.id, students.updated_at FROM students AS students WHERE id in (select student_id from parents_students where parent_id = '0966a998-c1bf-4cde-bda2-7f0763b50662')

With the new EagerPreload mode activated, you can change the way pop loads parents  and its associations:
parents := []Parent{}
tx.SetEagerMode(EagerPreload).Eager().All(&parents)

// SELECT parents.created_at, parents.id, parents.updated_at FROM parents AS parents

// SELECT parent_id, student_id FROM parents_students WHERE parent_id in ($1, $2) | ["cc6a7c1f-f9d9-4d8f-ac69-c827f78fc1f3" "e9c42530-648a-4dda-b780-96119d81b9c1"]

// SELECT students.created_at, students.id, students.updated_at FROM students AS students WHERE id in ($1, $2) | ["82e5ddd2-3daa-4bf0-92f0-7c37b9374db1" "82e5ddd2-3daa-4bf0-92f0-7c37b9374db1"]

Only three queries hit the database in order to get all data, independently of the parents and studentys lists size .  This reduces the number of queries performed on the database and allows a more efficient use of it.
Things I'm still working on:

Inner associations loading.
improve performing on many to many relation.

NOTE: you can use this for experiment purpose if you want. Let us know how this works for you.

@larrymjordan thanks for putting this one together! this is one that we are hoping a lot to get shipped into pop. If it's not too much to ask, would it be possible to have a branch in pop with this? That would allow us (and other modules users) to use it by referencing the branch.
I'm looking forward to helping with testing it and reporting any bug.

thank you @paganotoni, that would be really helpful.

I've created a new branch in pop repository nplus1 for people who is interested in testing and reporting any bug. In order to use it, you can update you go.mod file and add this line at the end.
replace github.com/gobuffalo/pop => github.com/gobuffalo/pop v4.5.10-0.20190831173857-97d87b584d7a+incompatible

Thanks, @larrymjordan! we'll give it a shot and post any findings.

Nested/Inner associations are now supported, update your pop module reference to be
replace github.com/gobuffalo/pop => github.com/gobuffalo/pop v4.11.4-0.20190905220504-0c1cb5e39943+incompatible

Hi team!
Where'd we end up with this? Did work move elsewhere?

@gobuffalo/pop-managers new update with fixes:

avoid duplicity loading for nested fields that are passed as arguments twice or more.
Avoid unwanted looping when loading associations when Preload mode is enabled globally.

use this new version:
replace github.com/gobuffalo/pop/v5 => github.com/gobuffalo/pop/v5 v5.0.7-0.20200217141442-e8f6c77c2e5e

@gobuffalo/pop-managers new update with refinements:

Add support for order_by tag:
replace github.com/gobuffalo/pop/v5 => github.com/gobuffalo/pop/v5 92e6cbd51084e6eedef6c4228d8cf4f3d231e6a4

@larrymjordan This looks fine to me, and we gave enough time for people to test it. Can I ask you to fix the conflicts, then we can merge it? :)

Thanks a lot @larrymjordan! 🎉

@larrymjordan
Hi, I have found out an issue
 type Risk struct {
	RiskOwner          Peopledb    `belongs_to:"risk_owner"`
	RiskOwnerID       uuid.UUID  `json:"risk_owner_id" db:"risk_owner_id"`
}

If  you will try to query this model with EagerPreload(), you will get nill pointer exception, but it will work with regular Eager() function
This will work
 type Risk struct {
	RiskOwner          Peopledb    `belongs_to:"risk_owner" fk_id:"risk_owner_id"`
	RiskOwnerID        uuid.UUID `json:"risk_owner_id" db:"risk_owner_id"`
}

Regular Eager will take field name + ID by default if there was no fk_id tag provided.
Could you fix it? Or should I try to help with that?
Thank you a lot for your Eager solution, it really helped.

Hi @Ilkrash thanks for taking notes on this. There is no any problem if you help to fix the issue. I would recommend to open an issue first with the steps to reproduce it, so we can follow it up and if you already have the solution for it, we would like to receive a PR from you.


Improve component versioning

Couple of challenges:

It is now based on a commit hash. This makes it unclear if a change means a down- or upgrade
From a MACH configuration perspective it's possible to define a component using a git tag. However, a artifact (serverless function ZIP file) needs to be present with both the commit hash and the git tag. This we should document better (and include in the cookiecutter)

@tleguijt is this still something we should look into? In the current setup of mach composer I think we store all this metadata in the Mach Composer cloud (or infer it from a git checkout).
Not sure if the problem still persists?

I think with https://github.com/mach-composer/mach-composer-cli/issues/149 covered we got it fixed.
MACH composer already allows you to use git tags (we have been using it for a long time on our project already) so I think with the mach update support we have everything to fully support it. Thanks!


Add margin to no-op text and centre vertically more accurately

Coverage increased (+0.2%) to 70.247% when pulling ffdd795f5684e2a3b488f94706a5102a26d947f6 on noop-minor-style-tweak into bc0340b6942b98b69e6b8a86d63bb8a4d2e45122 on master.

LGTM


eye button corrected in sign up page

updated the sign up page and removed the "eye" bug which was present earlier
Fixes Issue #377

Hey @Shikha954 Good work.
Thanks for contributing :)

@i-am-SnehaChauhan welcome ma'am


NSLocalizedString throwing exception.

NSString *description = NSLocalizedString([command argumentAtIndex:1 withDefault:@"No Message Provided"], nil);
In iOS is throwing an exception when calling logEvent?
Latest build version 1.1.1?

I am just working through testing a fix with:

        @try {
          NSString *description = NSLocalizedString([command argumentAtIndex:1 withDefault:@"No Message Provided"], nil);
          parameters = @{ NSLocalizedDescriptionKey: description };
        }
        @catch (NSException *execption) {
          parameters = [command argumentAtIndex:1];
        }

If it works I will create a PR.

@JonSmart publishing of v1.1.1 failed.  Trying again.   I'll comment once published successfully.

@soumak77 no worries, would be good to get this resolved anyway?  As it currently crashes on iOS.

@JonSmart v1.1.1 has been published to npm

@soumak77 Just used the published 1.1.1 and this bug is still present.  Shall I do a PR for a fix?

fixed via #815


Promote guydc as a maintainer

Description:
guydc has contributed a lot in v1.0.0, implemented circuit breaker, retry, btp timeout, btp tcpkeepalive, and active in code reviews.

big +1, well deserved

cc @guydc let us know if you are interested.
Also cc @envoyproxy/gateway-maintainers

Thanks @Xunzhuo and @arkodg. I appreciate the recognition and I will gladly accept the maintainer role.

+1 on this

+1, @guydc  well deserved!


Search follow symlinks spawns an rg process that uses 100% of CPU

Does this issue occur when all extensions are disabled?: Yes

Version: 1.86.2 (Universal)
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:42:13.651Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.2.0
Steps to Reproduce:

Make sure Search > Follow symlinks option is enabled in settings
Open a big enough repo (in my case it's a monorepo that uses pnpm and has a lot of symlinks in node_modules)
Use the global find and replace to look for something
after a while you'll see that your CPU usage is going up to 100% and most of it is consumed by rg process

The temporary fix is to disable Follow symlinks, but this option is enabled by default and pretty much everyone who works with this repo has the same problem.

I'm having this same issue, also as previously described in #98594; details below:
Does this issue occur when all extensions are disabled?: No (but see details below)
Version: 1.87.1
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:07.287Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-18-generic (ZorinOS, based on Ubuntu 22.04LTS)
I've isolated it to, specifically, the Microsoft published-extension (ms-vscode-remote.remote-containers) "Dev Containers".  As soon as I enable this extension, all 8 cores of my i7-6700k CPU go to 100% sustained, as shown in bashtop. The process taking up the most CPU time (~50% each) is rg (ripgrep), which searching indicates "ripgrep recursively searches directories for a regex pattern while respecting your gitignore", with their GitHub page linked here.
I've included a screen recording clearly demonstrating this behavior:
https://github.com/microsoft/vscode/assets/11323060/d6e5b762-d534-4170-a0ad-917d514481f6

@kmanwar89

I've isolated it to, specifically, the Microsoft published-extension (ms-vscode-remote.remote-containers) "Dev Containers".

So that's probably why I can't reproduce this problem anymore, since I deleted this extension.
Thanks for adding context to the problem.

Cheers, thanks for creating this issue so I didn't have to :)

@chrmarti This might be because you use the findFiles API, which will follow symlinks if the user sets followSymlinks to true. If you use findFiles2, which is proposed, you can force disable followSymlinks on your particular search.

Hi, is there any update that can be shared on this issue?

@kmanwar89 Could you try the Dev Containers extension version 0.356.0-pre-release? That comes with a fix for microsoft/vscode-remote-release#9738.
Skipping symlinks might still be an option, but it would also miss devcontainer.json files in linked subfolders of the .devcontainer folder and links to devcontainer.json files themselves. 🤔

@kmanwar89 Could you try the Dev Containers extension version 0.356.0-pre-release? That comes with a fix for microsoft/vscode-remote-release#9738.
Skipping symlinks might still be an option, but it would also miss devcontainer.json files in linked subfolders of the .devcontainer folder and links to devcontainer.json files themselves. 🤔

Happy to test - could you share guidance on how might I get access to pre-release?

There is a Switch to Pre-Release Version button when you open the extension's description from the Extensions side-panel:

Hi, I switched over tot the pre-release version and it appears to have cleared up the issue - monitoring my CPU doesn't show any significant increase with the extension enabled, and no noticeable decrease with it disabled.
I'll keep testing, because what I'm noticing is my base CPU usage seems a bit higher overall - ~40% while idle compared to <20% in the screencast that I shared previously. It's unclear what is causing this much of a difference since my setup hasn't changed significantly between posts, but I'll share any feedback if the issue reoccurs.


Item in ui-sortable which is not part of the model leads to some weird behaviour

Hey Guys,
when inside the ui-sortable one item appears which is not part of the ng-repeat (or the model) two strange thinks happen

dragging the last one leads to create a new null-object
dragging any other one does not change the order

see codepen below for an example
http://codepen.io/anon/pen/avmqje?editors=100
bg,
Johannes

Duplicate of #41.
This is fixed in v0.14.x branch.


Drop flask-apispec support

I am now planning to drop flask-apispec support. Because there are issues with the extension, including:

https://github.com/jmcarp/flask-apispec/issues/122

I've found a flask-apispec replacement extension which is FlaskEase
And I plan to use it. But, I'm also open to other suggestions.

I don't know FlaskEase. You could be interested in flask-smorest.
flask-smorest uses marshmallow. FlaskEase uses pydantic.

I don't know FlaskEase. You could be interested in flask-smorest.
flask-smorest uses marshmallow. FlaskEase uses pydantic.

Interesting, I'll try later. thanks

Interesting, I'll try later. thanks

Hi @lafrech, Does flask-smorest have a configuration to not enable swagger-ui? (for example, when the application is in our production environment not using swagger-ui)

Hi @lafrech, Does flask-smorest have a configuration to not enable swagger-ui? (for example, when the application is in our production environment not using swagger-ui)

Sure. It is off by default.
https://flask-smorest.readthedocs.io/en/latest/openapi.html#serve-the-openapi-documentation
More precisely, the docs is always generated, but serving it is optional and opt-in.
I forgot to mention that I wrote it because I was not satisfied with flask-apispec but it looks very much like it so the move shouldn't be too hard.

Sure. It is off by default.
https://flask-smorest.readthedocs.io/en/latest/openapi.html#serve-the-openapi-documentation
More precisely, the docs is always generated, but serving it is optional and opt-in.
I forgot to mention that I wrote it because I was not satisfied with flask-apispec but it looks very much like it so the move shouldn't be too hard.

Yes, I feel the same way too.

Yes, I feel the same way too.

Is adding a security schema the same as flask-apispec?

Is adding a security schema the same as flask-apispec?

Is adding a security schema the same as flask-apispec?

@lafrech ?

Is adding a security schema the same as flask-apispec?

@lafrech ?

Can't help you. Don't know flask-apispec.

Can't help you. Don't know flask-apispec.

Hi @lafrech, can flask-smorest create a path to swagger-ui without a blueprint?