[google_sign_in] [firebase_auth] PlatformException Error Code: 2

I'm simply trying to use google_sign_in plugin to authorize myself on firebase via firebase_auth with function shown under. On the other hand I'm able to create user via email and password in my firebase project just this bloody google sign in is misbehaving.
Steps to Reproduce
Future<String> signInWithGoogle () async {

    try {
      GoogleSignIn googleSignIn = new GoogleSignIn();
      GoogleSignInAccount googleUser = await googleSignIn.signIn();
      GoogleSignInAuthentication googleAuth = await googleUser.authentication;

      FirebaseAuth firebaseAuth = FirebaseAuth.instance;
      print(googleAuth.accessToken);
      print(googleAuth.idToken);

      await firebaseAuth.signInWithGoogle(
        accessToken: googleAuth.accessToken,
        idToken: googleAuth.idToken,
      );

      final FirebaseUser user = firebaseAuth.currentUser;
      print(user.displayName);

      return('signInWithGoogle succeeded ');
    } catch (e) {
      print(e);
    }

Logs
Log from Android studio terminal try/catch
/flutter (25608): [ERROR:topaz/lib/tonic/logging/dart_error.cc(16)] Unhandled exception:
E/flutter (25608): type '_AssertionError' is not a subtype of type 'PlatformException' of 'onError' where
E/flutter (25608):   _AssertionError is from dart:core
E/flutter (25608):   PlatformException is from package:flutter/src/services/message_codec.dart
E/flutter (25608):
E/flutter (25608): #0      LoginScreenState._loginWithGoogle.<anonymous closure> (package:flutter_flat_app/screens/Login/index.dart:65:38)
E/flutter (25608): #1      _RootZone.runUnary (dart:async/zone.dart:1381)
E/flutter (25608): #2      _FutureListener.handleError (dart:async/future_impl.dart:144)
E/flutter (25608): #3      _Future._propagateToListeners.handleError (dart:async/future_impl.dart:645)
E/flutter (25608): #4      _Future._propagateToListeners (dart:async/future_impl.dart:666)
E/flutter (25608): #5      _Future._complete (dart:async/future_impl.dart:467)
E/flutter (25608): #6      _SyncCompleter.complete (dart:async/future_impl.dart:51)
E/flutter (25608): #7      _completeOnAsyncReturn (dart:async-patch/dart:async/async_patch.dart:292)
E/flutter (25608): #8      UserAuth.signInWithGoogle (package:flutter_flat_app/services/authentication.dart:59:3)
E/flutter (25608): #9      _asyncErrorWrapperHelper.<anonymous closure> (dart:async-patch/dart:async/async_patch.dart:84)
E/flutter (25608): #10     _RootZone.runBinary (dart:async/zone.dart:1386)
E/flutter (25608): #11     _FutureListener.handleError (dart:async/future_impl.dart:141)
E/flutter (25608): #12     _Future._propagateToListeners.handleError (dart:async/future_impl.dart:645)
E/flutter (25608): #13     _Future._propagateToListeners (dart:async/future_impl.dart:666)
E/flutter (25608): #14     _Future._completeError (dart:async/future_impl.dart:485)
E/flutter (25608): #15     _SyncCompleter._completeError (dart:async/future_impl.dart:55)
E/flutter (25608): #16     _Completer.completeError (dart:async/future_impl.dart:27)
E/flutter (25608): #17     FirebaseAuth.signInWithGoogle (package:firebase_auth/firebase_auth.dart)
E/flutter (25608): #18     _asyncErrorWrapperHelper.<anonymous closure> (dart:async-patch/dart:async/async_patch.dart:84)
E/flutter (25608): #19     _RootZone.runBinary (dart:async/zone.dart:1386)
E/flutter (25608): #20     _FutureListener.handleError (dart:async/future_impl.dart:141)
E/flutter (25608): #21     _Future._propagateToListeners.handleError (dart:async/future_impl.dart:645)
E/flutter (25608): #22     _Future._propagateToListeners (dart:async/future_impl.dart:666)
E/flutter (25608): #23     _Future._completeError (dart:async/future_impl.dart:485)
E/flutter (25608): #24     _SyncCompleter._completeError (dart:async/future_impl.dart:55)
E/flutter (25608): #25     _Completer.completeError (dart:async/future_impl.dart:27)
E/flutter (25608): #26     MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart)
E/flutter (25608): #27     _RootZone.runUnary (dart:async/zone.dart:1381)
E/flutter (25608): #28     _FutureListener.handleValue (dart:async/future_impl.dart:129)
E/flutter (25608): #29     _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:633)
E/flutter (25608): #30     _Future._propagateToListeners (dart:async/future_impl.dart:662)
E/flutter (25608): #31     _Future._completeWithValue (dart:async/future_impl.dart:477)
E/flutter (25608): #32     _Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:507)
E/flutter (25608): #33     _microtaskLoop (dart:async/schedule_microtask.dart:41)
E/flutter (25608): #34     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)

Print from 'catchError'  method
  void _loginWithGoogle() {
    userAuth.signInWithGoogle().then((onValue) {
      if (onValue == "signInWithGoogle succeeded ")
        Navigator.pushNamed(context, "/HomePage");
      else
        showInSnackBar(onValue);
    }).catchError((PlatformException onError) {
      print(onError.toString());
      showInSnackBar(onError.message);
    });
  }

flutter (26060): PlatformException(exception, An internal error has occurred. [ Error code:2 ], null)

Flutter analyze
Analyzing /home/tabuz/projects/flat-app...
  error • Target of URI doesn't exist: 'package:flutter_flat_app/Screens/Login/index.dart' at test/widget_test.dart:8:8 • uri_does_not_exist
  error • The constructor returns type 'dynamic' that isn't of expected type 'Widget' at test/widget_test.dart:15:29 • strong_mode_invalid_cast_new_expr
  error • Undefined class 'LoginScreen' at test/widget_test.dart:15:33 • undefined_class
  warning • This function declares a return type of 'Future<String>', but doesn't end with a return statement at lib/services/authentication.dart:34:3 • missing_return
  hint • This class inherits from a class marked as @immutable, and therefore should be immutable (all instance fields must be final) at lib/components/Buttons/roundedButton.dart:3:7 • must_be_immutable
  hint • This class inherits from a class marked as @immutable, and therefore should be immutable (all instance fields must be final) at lib/components/Buttons/textButton.dart:3:7 • must_be_immutable
  hint • This class inherits from a class marked as @immutable, and therefore should be immutable (all instance fields must be final) at lib/components/TextFields/inputField.dart:3:7 • must_be_immutable
7 issues found.
(Ran in 7.9s)

Flutter Doctor
[✓] Flutter (Channel beta, v0.2.3, on Linux, locale pl_PL.UTF-8)
    • Flutter version 0.2.3 at /home/tabuz/software/flutter
    • Framework revision 5a58b36e36 (3 weeks ago), 2018-03-13 13:20:13 -0700
    • Engine revision e61bb9ac3a
    • Dart version 2.0.0-dev.35.flutter-290c576264

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /home/tabuz/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /home/tabuz/software/android-studio/jre/bin/java
    • Java version openjdk version "1.8.0_152-release"
    • All Android licenses accepted.

[✓] Android Studio (version 3.1)
    • Android Studio at /home/tabuz/software/android-studio
    • Java version openjdk version "1.8.0_152-release"

[✓] Connected devices (1 available)
    • Pixel • FA69L0304820 • android-arm64 • Android 8.1.0 (API 27)

• No issues found!

Dependencies
  image_picker: 0.1.1                                             # new
  google_sign_in: 0.3.1                                           # new
  firebase_analytics: 0.0.4                                       # new
  firebase_auth: 0.1.1                                            # new
  firebase_database: 0.0.12                                       # new
  firebase_storage: 0.0.5                                         # new

@tabuz
The issue at https://github.com/flutter/flutter/issues/16239 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @tabuz
If you are still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your updated  flutter doctor -v
and your flutter run --verbose/flutter build --verbose ?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

@iapicca Oh my friend... this was issue was addressed in April 2018, like more than a year ago. I don't have this code base anymore. Unfortunately I won't be much help here.
Anyway much appreciate that someone did look into it ;)

Hi @tabuz
I know, I apologize for the delay.
I'm closing this issue for now,
but if you are encountering any problem
please let me know and I'll open it again.
thank you


cinnamon.cinnamon-common: fix various issues

Description of changes
See commit message for related issues.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Tested this by editing a menu entry with the virtual keyboard:

The linked issue can be closed after this, right?

Commit messages can automatically close issues I think (example is https://github.com/NixOS/nixpkgs/issues/169178)


Add a negative impl for the builtin Sync trait.

Since 388e30f which is part of the work on the builtin traits RFC it's now required to have a negative impl for the Send and Sync traits instead of using the markers NoSend/NoSync (UnsafeCell doesn't opt-out for us either).
Fixes #13

Superseded by df6f74c.


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(devDependencies): add<EMAIL_ADDRESS>from template
chore(devDependencies): add<EMAIL_ADDRESS>from template

Codecov Report

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

@@           Coverage Diff           @@
##           master     #181   +/-   ##
=======================================
  Coverage   83.92%   83.92%
=======================================
  Files           1        1
  Lines         168      168
=======================================
  Hits          141      141
  Misses         27       27

Continue to review full report at Codecov.

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


About an invalid date

Hi,
I found there is an invalid date 20100431 here since there are only 30 days in April. It will be generally ok but may not pass some validator checking.
https://github.com/HL7/C-CDA-Examples/blob/ac15cf53cf5483baf0f9173fcd0c79f36ca3b654/Documents/History and Physical/History_and_Physical.xml#L1954

🕌


Error when updating geometry column with Postgresql/PostGIS

I get an error trying to edit geometry records in DBeaver against a PostGIS table with a geometry column set to SRID 4326 (geographic/wgs84).  I see that DBeaver obtains the geometry from the server in binary form and then converts it to WKT text format to display in the results table.  If I try to either edit the coordinates text in the field or copy a geometry value from another record into the field, I get an error upon commit:
SQL Error [22023]: ERROR: Geometry SRID (0) does not match column SRID (4326)
If I edit the WKT text and append 'SRID=4326;' to the beginning of the string, commits are successful.  Example:
SRID=4326;MULTIPOLYGON (((148.666666667138 -42.2880555598776,<PHONE_NUMBER>16863 -42.2800617309498,<PHONE_NUMBER>67138 -42.2880555598776)))
Is there something else I should be doing to edit geometry fields? Or is this a bug in need of a fix?

This  looks like a bug..


Remove -openmp flag from XLF (since it doesn't support it).

Remove -openmp flag from XLF (since it doesn't support it).

I wonder if it did in the (fairly distant) past, as this snippet appears to be a remnant from GotoBLAS


Feature:  STL

Is your feature request related to a problem? Please describe.
STL is difficult to understand and use to newbies.
Describe the solution you'd like
I will contribute a simple documentation along with simple codes
Describe alternatives you've considered

Additional context

I am waiting for your permission.

I want to contribute to this project can you please assign me?

I want to contribute to this project and would like to contribute by providing a detailed documentation, possibly video explanations and provide sample codes if it's about teaching.
If STL has to be implemented in a program, I am confident to provide an accurate solution


Visual Editor / Code Editor Switch component

Implement the Switch component as seen in the design.

Note: Do not try to make it a generic Switch component. This one is a very special one with two icons so I would not call it Switch but, instead, EditorSwitch or something like that to avoid naming collisions with a future Switch component.
Related to #636

/progress 70
The implementation is done. just waiting for https://github.com/asyncapi/studio/issues/666 to use the official tokens instead of hardcoding them in the component.

You got it :) https://github.com/asyncapi/studio/pull/681

/progress 80
https://github.com/asyncapi/studio/pull/691

/progress 95
PR is ready for review. https://github.com/asyncapi/studio/pull/691


add cryptopower on fdroid

ref: https://gitlab.com/fdroid/rfp/-/issues/2952

ref: https://github.com/crypto-power/cryptopower/pull/714

Set up instant exchange private key: copy file ./libwallet/instantswap/instant_example.json into ./libwallet/instantswap/instant.json. Then replace with your own key.

umm, what happens if we don't? F-Droid will not try to get any API keys... not does it support "secrets"
ref: https://f-droid.org/docs/Inclusion_Policy/


Starting from Big Sur 11.3 certificate installation requires user interaction

First, thank you so much for mkcert! I love it and use it often ⭐
It seems that some default behavior may have changed in macOS 11, as mkcert isn't working out of the box on GitHub Actions with macos-latest. (Ah yes, I just read an issue I referenced and it said Starting from Big Sur 11.3 certificate installation requires user interaction, however it can be bypassed by using SecItemAdd method.)
I'm getting the same error as reported in https://github.com/FiloSottile/mkcert/issues/94
And I was advised that I could compile some swift code to solve my issue, similar to what they did in this PR https://github.com/actions/virtual-environments/pull/3311.
swiftc add-certificate.swift
sudo ./add-certificate YourCertName.cer

By the time I was done, however, I wasn't using mkcert anymore. I thought this would be a more appropriate solution to build into mkcert.

@potatoqualitee where is the add-certificate.swift ?

add-certificate.swift can be found in GitHub's Runner repo at https://github.com/actions/virtual-environments/blob/main/images/macos/provision/configuration/add-certificate.swift

git ut working here : https://github.com/FiloSottile/mkcert/issues/412#issuecomment-976429667

Does the Swift script still work as of macOS 12.3.1? I tried it and the SecTrustSettingsSetTrustSettings invocation still pops up a dialog on my machine. Interestingly enough, the dialog doesn't support Touch ID while the security-driven one does.

By the way, that's a pretty bad script. The return code of SecTrustSettingsSetTrustSettings is not checked, the script will exit silently if SecItemAdd fails, and the certificate label is always Test which I guess made sense in https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-swift-security/blob/c26988a7f5de338c1d9e0d43a64c2b6db33be541/Source/mca/internal/certificate/SecurityUtils.swift but not really in a standalone CLI tool.

Unfortunately, I have no idea. GitHub would know more. Because my use-case was CI/CD, I just used a command that was way too permissive.

Looks like GitHub is indeed still using this script. I tried figuring out why it works on their runners and couldn't reproduce uninteractive behavior. https://github.com/actions/virtual-environments/blob/main/images/macos/provision/configuration/configure-machine.sh

I'll see who I can ping and let you know! Thanks for looking into this

Whatever is going on is inconsistent with the SecTrustSettingsSetTrustSettings docs.

When making changes to system-wide trust settings, the user is prompted with an alert panel asking for an administrator’s name and password unless the calling process is running as root, in which case no further authentication is needed.

https://developer.apple.com/documentation/security/1399119-sectrustsettingssettrustsettings
@timsutton found the relevant entry in the Big Sur release notes: https://github.com/FiloSottile/mkcert/issues/322#issuecomment-868822285

macOS Big Sur 11 beta improves system security by requiring an administrator password when a certificate trust settings change is made in the admin trust domain. Running as the root user alone is no longer sufficient to modify certificate trust. User trust domain settings continue to require confirmation by entering the password for the user’s account. This change may affect you if one of the following is true:
You have written scripts which call /usr/bin/security add-trusted-cert -d ... as root.
Your process runs as root and calls the SecTrustSettingsSetTrustSettings function to trust a certificate.
Workflows that add trust settings in the admin trust domain, such as for an enterprise root certificate, may require modification if the user can’t authenticate as an administrator at the time settings are changed. (21855995)
Workaround: Use Apple Configurator 2 to create and install a configuration profile containing your root certificate.

Which seems to imply this is intentional. I wonder if the Configurator path is viable for mkcert.
If this is intentional, though, it seems weird it can be defeated with sudo security authorizationdb write com.apple.trust-settings.admin allow per https://github.com/actions/virtual-environments/issues/4519#issuecomment-970202641 (surely any malicious code would just do that?), and still doesn't explain why the script works for the GitHub runner setups.
We could mention com.apple.trust-settings.admin in the docs for CI/CD runners, but I'm worried about people just running it on their main machine.

Hmm. The Configurator idea I think won't help here: besides requiring an extra download, Apple ID sign-in and "purchase" of a free app, you still can't install configuration profiles automatically starting with Big Sur either. Apple removed local profiles installation in the same OS release they also took away an officially-supported way to trust a root cert at the command line.
It seems weird about the workaround being possible, but I think there's a few possible reasons:

the security authorizationdb database is not a widely-known thing
they likely had to implement this restriction hastily because their security org has a lot of engineering power to impose demands on OS teams on short notice
they don't always coordinate these things so well that they don't leave other lesser-known workarounds working for a while

It is possible to afterwards revert the authorizationdb settings for com.apple.trust-settings.admin too, but I agree this is probably better off a thing to just document as an unsupported workaround that a user should do on their own if they accept the risk. IIRC reverting the settings is a more complicated command because the original setting's rules is a more complicated dictionary structure.

Don't know if this is too severe, but a documented flag can also be added like -forcemactrust and people can opt-in to the easier method in exchange for a few milliseconds of lessened security. I'd use that.
@timsutton -- seems you may also be suggesting to wait for workarounds to appear? also valid and clean(er).

I was just suggesting that I think it's acceptable if the tool doesn't want to own a system configuration change that could be risky (and instead to document how users can do it at their own risk).
I'm not thinking 'risky' in the sense that one needs to temporarily reduce security policy, but risky in the sense that it's a change that Apple doesn't have a documented public API for and can easily break or change in the future, and that reverting the setting may take some time effort to get right. So if mkcert decided it would offer to make this change and also revert it afterwards, it'd be something to support in future years of macOS releases.
IMO the trickier details of the authorization database is the rules nomenclature and how to revert them after changing the configuration. 'eskimo' (an Apple engineer who posts a lot of very helpful replies on Apple's developer forums) has some good details provided here. The "allow" setting is easy to apply, and I think it's straightforward enough to put back a rule for the right (by piping the correct plist into stdin of security authorizationdb). But if those rules might change next OS release, that'd be not great. Maybe that's unlikely – but it's just the example of how this opens up a bit of a can of worms thanks to Apple having no simple and documented way to do this (outside of what they officially support for automation which is MDM-only).

Sill an issue in Sonoma.

There is new issue occurs in new MacOS 15 version while adding certificates through MDM, before that it was working using below cmd
security authorizationdb write com.apple.trust-settings.admin allow ; security add-trusted-cert -d -r trustRoot -k "/Library/Keychains/System.keychain" cert.cer ; security authorizationdb remove com.apple.trust-settings.admin


Add the ConfigMap for rollouts

Added the ConfigMap named 'argo-rollouts-config' in the Rollouts namespaces.

LGTM!


PubSub does not work

Hello,
I tried to configure the google PubSub dispatcher and it does not seems to run. I tested the connection to Google Cloud separatedly and credentials work fine. The docker logs does not show anything running in terms of this. How can I debug it?
The telemetry receives data fine .
This is my yml config of docker implementation:
services:
app:
build:
context: ./repo
ports:
- <IP_ADDRESS>:443:443
environment:
- GOOGLE_APPLICATION_CREDENTIALS=/etc/tesla-telemetry/service-account.json
volumes:
- ./certs:/etc/tesla-telemetry/certs:rw
- ./config.json:/etc/fleet-telemetry/config.json
- ./service-account.json:/etc/tesla-telemetry/service-account.json:ro
Config.json:
"port": 443,
"log_level": "debug",
"json_log_enable": true,
"namespace": "telemetry",
"reliable_ack": false,
"rate_limit": {
"enabled": false,
"message_limit": 100
},
"records": {
"alerts": [
"logger"
],
"errors": [
"logger"
],
"V": [
"logger"
]
},
"pubsub": {
"gcp_project_id": "tesla-telemetry-437xxxx"

Hi there
Have you tried setting up the way described in https://github.com/teslamotors/fleet-telemetry/pull/62#issue-1878023909?

If I read it correctly that is for deploying the telemetry on GCP, while I have mine on AWS EC2. If somebody can confirm if the mount is right for the google environment: - ./service-account.json:/etc/tesla-telemetry/service-account.json:ro.
Also, I don't see anything in the logs, so I am not sure if the PubSub is invoked at all... it might be a config thing done wrong.

@ciumagcatalin your config is wrong, as per agbpatro's comment, you need to actually enable pubsub in your records too.
"records": {         "alerts": [             "pubsub"         ],         "errors": [             "pubsub"         ],         "V": [             "pubsub"         ]     },

@ciumagcatalin your config is wrong, you need to actually enable pubsub in your records too.
"records": { "alerts": [ "pubsub" ], "errors": [ "pubsub" ], "V": [ "pubsub" ] },
This would be why you dont have any errors.

Thank you @Bre77 ! That was missing. Now everything seems to be working!


Nvidia Jetson runtime failure

 python3 sample.py --image img.png --prompt "hi"

I get a different type of error on my Jetson Orin with JetPack 5.1.2:
Using device: cuda
If you run into issues, pass the --cpu flag to this script.
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Traceback (most recent call last):
File "sample.py", line 32, in
moondream = Moondream.from_pretrained(
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/transformers/modeling_utils.py", line 3462, in from_pretrained
model = cls(config, *model_args, **model_kwargs)
File "/home/theuser/Devs/GitHub/MoonDream/moondream/moondream/moondream.py", line 16, in init
self.vision_encoder = VisionEncoder()
File "/home/theuser/Devs/GitHub/MoonDream/moondream/moondream/vision_encoder.py", line 98, in init
VisualHolder(timm.create_model("vit_so400m_patch14_siglip_384"))
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/models/_factory.py", line 117, in create_model
model = create_fn(
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/models/vision_transformer.py", line 2598, in vit_so400m_patch14_siglip_384
model = create_vision_transformer(
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/models/vision_transformer.py", line 1764, in create_vision_transformer
return build_model_with_cfg(
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/models/builder.py", line 385, in build_model_with_cfg
model = model_cls(**kwargs)
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/models/vision_transformer.py", line 525, in init
self.attn_pool = AttentionPoolLatent(
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/layers/attention_pool.py", line 63, in init
self.init_weights()
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/layers/attention_pool.py", line 68, in init_weights
trunc_normal_tf(self.latent, std=self.latent_dim ** -0.5)
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/layers/weight_init.py", line 94, in trunc_normal_tf
trunc_normal(tensor, 0, 1.0, a, b)
File "/home/theuser/Devs/GitHub/MoonDream/MoonDreamEnv/lib/python3.8/site-packages/timm/layers/weight_init.py", line 32, in trunc_normal
tensor.erfinv()
RuntimeError: "erfinv_vml_cpu" not implemented for 'Half'
I made sure to run compatible versions of torch/torchvision with cuda 11.4:
torch                     2.1.0a0+41361538.nv23.6
torchvision           0.16.2

I fixed my issue by modifying the code in python3.8/sitepackages/timm/layers/weight_init.py to convert the tensor to float32 and back to float16 after the incompatible operations. This appears to be only executed before run-time inference so it does not seem to affect the performance. Running the webcam_gradio_demo.py demo on my Jetson Orin Dev Kit, I get an update every 2 secs or even a bit less, slightly faster than my Mac mini M2 Pro running MoonDream with MPS Torch ;)


Change Request in chainercv/examples/fpn/train_multi.py

Hello,
line 61 in TrainChain Class in chainercv/examples/fpn/train_multi.py ,
I think
x = np.zeros(
(len(imgs), 3, pad_size[0], pad_size[1]), dtype=np.float32)
should be changed to
x = self.xp.zeros(
(len(imgs), 3, pad_size[0], pad_size[1]), dtype=np.float32) because when model is gpu-mode,  the model use cupy instead of using numpy.
Am I right?

Current code is correct.
In FPN example, all arguments of TrainChain.forward is CPU array.
They are sent to GPU in https://github.com/chainer/chainercv/blob/master/examples/fpn/train_multi.py#L66-L69.


pythonPackages.pandas: 1.0.5 -> 1.1.0

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

addressed by https://github.com/NixOS/nixpkgs/commit/2dafde493f1


Added Shiffman's head to use on skeleton!

Thanks! I'm going to add a second one, but I can't decide between the "this dot" and the GitHub cat head... What do you think?

How's this?


Could not find method google() for arguments [] on repository

What went wrong:
A problem occurred evaluating project ':react-native-contacts'.

Could not find method google() for arguments [] on repository container of type org.gradle.api.internal.artifacts.dsl.DefaultRepositoryHandler.

Please help to resolve the issue.

not sure

@krishna201  add google() to .//android/build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
gradlePluginPortal()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
mavenLocal()
jcenter()
maven { url "https://jitpack.io" }
maven { url "https://maven.google.com" }
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}
}

Same issue here.

i resolve the issue
update the gradle to 4.5
by going andorid/gradle/wrapper/gradle-wrapper.properties
to distributionUrl=https://services.gradle.org/distributions/gradle-4.5-all.zip
then react-native run-android
enjoy


Use a RNG instead of legacy np.random

see: https://numpy.org/doc/stable/reference/random/index.html

Used numpy's RandomState instead of numpy's Generator to get the same dataset as before. Explained here: https://numpy.org/doc/stable/reference/random/new-or-different.html#new-or-different


More services in Benchmarks

Hi!
Is it possible to include more popular services to the benchmarks, like Ruby/Rails, Netty/Vertx etc?

Possible yes, but the point is to have just enough to see the shape from worse to better. I rather remove than add.


2020-09-01-preview Inference Endpoints and Deployments

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Thanks for taking the feedback, I'm good with the ARM perspective. Please work with SDK team to get this closed.

/azp run automation - sdk

Thanks for taking the feedback, I'm good with the ARM perspective. Please work with SDK team to get this closed.

Thanks. I had to make a couple more changes to avoid naming conflicts.  Can you please take another look?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@ArcturusZhang Can you please take another look?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Please do not check in yet as recent changes may change the API.

Please do not merge changes immediately.

Please let me know when this is good to merge.

/azp run automation - sdk

Hi @fullmetalcloud please resolve the merge conflict and double check if there is any un-resolved merge conflicts committed in

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Due to changes in naming and structure, I will open a new PR with new names and changes. I will need another review for that.

/azp run automation - sdk

Reopen to reuse the PR for name change

Closing. Need to make a new PR.


ci: set CGO_ENABLED=0 for local crane binary

The crane binary is used by some of the e2e tests, which can be run in a container which does not have glibc. Compiling with CGO causes an error when invoking the binary in such a container.

/assign @karlkfi


Python import does not find pip installation from Github

However, editable installation with pip install -e backbones works.

Solved in #2.


Fix unexpected polymorphism

Closes #1259 and #951. After all, it is a one-line fix. But given how hard it was to find, we should consider making quantified type variables explicit in the annotations and types.

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[x] Entry added to UNRELEASED.md for any new functionality

Codecov Report

Merging #1262 (a88ffe9) into unstable (f769c70) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head a88ffe9 differs from pull request most recent head 4ec6d57. Consider uploading reports for the commit 4ec6d57 to get more accurate results

@@            Coverage Diff            @@
##           unstable    #1262   +/-   ##
=========================================
  Coverage     73.96%   73.96%
=========================================
  Files           327      327
  Lines         10731    10732    +1
  Branches        539      542    +3
=========================================
+ Hits           7937     7938    +1
  Misses         2794     2794

Impacted Files
Coverage Δ

.../apalache/tla/typecheck/etc/ConstraintSolver.scala
97.22% <100.00%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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


How can I make the custom navigation bar transparent? I have tried all the options in react-native-router-flux like:   navigationBarStyle or navTransparent and also navigationBarStyle={[STYLES.navBar]}all of these are  not working while trying to make the custom navigation bar transparent  Is there any ways to make it transparent using react-navigation and should I change from react-native-router-flux to react-navigation to do this

Current Behavior
this is my Router.js file
import React from 'react';
import { Scene, Router } from 'react-native-router-flux';
import mainScreen from './components/mainScreen';
import challengeScreen from './components/challengeScreen';
import NavBar from './components/NavBar';
const RouterComponent = () => {
return (

);
};
export default RouterComponent;
and this is my navigationbar js file
`import {
View, Image, StatusBar, TouchableWithoutFeedback
} from 'react-native';
import React, { Component } from 'react';
import { Actions, Router, Scene } from 'react-native-router-flux';
class NavBar extends Component {
render() {
return (

<View style={{ flexDirection: 'row' }}>
<TouchableWithoutFeedback onPress={() => Actions.homeScreen()}>
<Image
source={require('./Images/back-arrow.png')}
style={styles.backarrowStyle} />

  <Image

source={require('./Images/help.png')}
style={styles.helpStyle} />
<Image
source={require('./Images/setting.png')}
style={styles.settingStyle} />

);
}
}
const styles = {
backgroundStyle: {
backgroundColor: 'transparent'
},
backarrowStyle: {
resizeMode: 'contain',
flexDirection: 'row',
width: 55,
height: 55,
left: 0,
justifyContent: 'flex-start'
},
helpStyle: {
resizeMode: 'contain',
width: 50,
height: 50,
left: 210,
justifyContent: 'flex-end',
position: 'relative'
},
settingStyle: {
resizeMode: 'contain',
width: 50,
height: 50,
justifyContent: 'flex-end',
position: 'relative',
left: 210
}
};
export default NavBar;
`
Expected Behavior
need to make the present navigation bar look transparent and the background be visible
Your Environment
"react": "16.0.0-alpha.12",
"react-native": "0.46.4",
"react-native-router-flux": "^4.0.0-beta.14",
 "react-native-router-flux-nav-bar": "^1.1.0"

I would recommend switching from react-native-router-flux to react-navigation.
What you are looking for can be done easily with react-navigation by either using a TabNavigator and setting tabBarVisible: false or by using a StackNavigator and setting header: null depending on which kind of Navigator you need.
See:
https://reactnavigation.org/docs/navigators/tab#tabBarVisible and https://reactnavigation.org/docs/navigators/stack#header

thanks @PhillipWinder I will surely try that but is there any way to do this without switching from react-native-router-flux

None that I would know of :)

I couldn't make the custom navBar transparent I tried all the methods suggested everywhere and i think its an issue with react-navigation and thats why i posted it as an issue it would be better to refer to some solution or giving a solution  rather than posting up views @augustoabreu

This issue is not solved. It shouldn't be closed

I am facing the same issue now. It is really necessary to provide a way to make the bar transparent.


swarm cluster can't be created again

when we test a swarm cluster with three manager no worker, and restart the three manager node at the same time, the swarm cluster can't be created again.

Do you have logs that show more info? Can you provide more information about your setup?

how can I get more logs as far as possible, thanks :)

Hi @lixiaobing10051267, you can enable more verbose logging by changing the contents of /etc/docker/daemon.json and making sure the following option is present in the JSON dictionary:
{
    "log-level": "debug"
}

Then restart your docker daemon.
On a side-note, once you have quorum in a swarm cluster (e.g. 2 or more nodes), you will be unable to restart all of them at the same time because, when each comes back online, they won't be able to vote on who is the master and who's data is correct. This is usually the case in all clustered software and is not specific to docker. You need to make sure that at least N-1 of your nodes are always available in order for the cluster to survive.
Because your cluster is dead, you will need to forcibly make all nodes leave the swarm and then re-create the swarm again. You will also have lost all your service definitions, as they are stored in the cluster-state.

Then restart your docker daemon.

Enabling/disabling debugging is possible without restarting the daemon, you can send a SIGHUP to the daemon, and it should reload the configuration from daemon.json


tests: adds a purge_cluster_collocated scenario

This test verifies that you can purge a cluster using journal collocation and then redeploy the cluster again. There were some minor fixes to purge-cluster.yml needed for the playbook to work.

This PR needs https://github.com/ceph/ceph-build/pull/605 for the purge_cluster_collocated scenario to be used.


Allow running Clippy lints via infra

...but don't error when it fails. This should help us prepare to gradually adopt the linter and fix the relevant reported lints.
Part of #155
EDIT: This runs the lint command as usual and we control which lints we warn against, so that we can gradually migrate.

Thanks a lot for the back and forth @OmarTawfik! Happy to land Clippy lints, finally.


Global unit not running on all machines

I have a global unit deployed to my cluster, but for some reason it will not deploy to one node in the cluster. Where do I start troubleshooting this?
Unit
[Unit]
Description=Analyzes resource usage and performance characteristics of running containers.
After=docker.service
Requires=docker.service

[Service]
Restart=always
ExecStartPre=-/usr/bin/docker kill %n
ExecStartPre=-/usr/bin/docker rm -f %n
ExecStartPre=/usr/bin/docker pull google/cadvisor:latest
ExecStart=/usr/bin/docker run --volume=/var/run:/var/run:rw --volume=/sys/fs/cgroup/:/sys/fs/cgroup:ro --volume=/var/lib/docker/:/var/lib/docker:ro --publish=8080:8080 --name %n google/cadvisor:latest
ExecStop=-/usr/bin/docker stop %n

[X-Fleet]
Global=true

Cluster
$ fleetctl list-machines
MACHINE		IP		METADATA
869b5e94...	<IP_ADDRESS>	-
943b0e30...	<IP_ADDRESS>	-
e081671e...	<IP_ADDRESS>	-

After starting - units are only loaded on 222, and 223 but not 221
$ fleetctl list-units
UNIT					MACHINE				ACTIVE		SUB
cadvisor.service			869b5e94.../<IP_ADDRESS>	active		running
cadvisor.service			e081671e.../<IP_ADDRESS>	active		running
...

can you check fleetctl ssh 943b0e30 systemctl status cadvisor.service?

The unit isn't loaded there.
$ systemctl status cadvisor.service
● cadvisor.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Also strange, if I try pinning a service to 943b0e30 using MachineID then fleetctl just hangs trying to load the unit. It seems like fleet doesn't consider 943b0e30 to be part of the cluster?

So I found the problem, but I don't know why it happened. The root cause was a bad unit file in /run/fleet/units on 943b0e30. Deleting the file un-wedged fleet on that host and all started going well.
What I don't know is why that unit file was there in the first place and why a single unit blocked all other units from running. I had used fleetctl destroy on it before.
Jul 16 13:34:35 vtse-coreos01 fleetd[31875]: ERROR reconcile.go:79: Unable to determine agent's current state: failed fetching unit states from UnitManager: Unit name<EMAIL_ADDRESS>is not valid

this happens when you try to fleetctl load or fleetctl start a template. it's been fixed now, and fleetd 0.11.0 in the next alpha should prevent this.
duplicate of #1236.


1.8.2 The scroll bar cannot scroll

The scroll bar cannot scroll

Known, should be fixed in next release.
It can happen if you have long, multiline output.

Known, should be fixed in next release.
It can happen if you have long, multiline output.

@yamashi can be closed I believe.

@yamashi can be closed I believe.


feat: Google Token Credentials using Type-Safe Middleware

Introduces a TypeSafeGoogleToken protocol which implements the TypeSafeCredentials and TypeSafeMiddleware protocols, that can be passed to a user's Codable Routing handler representing a user authenticated using a Google OAuth token.
A default implementation GoogleTokenProfile has been provided, which serves as a sample, or can be used as-is if the user does not want to further customize their type.
The requirements of a type-safe Google token middleware are:

The type must conform to TypeSafeGoogleToken, which itself conforms to Codable. Any properties must therefore be Codable.
The type must be a struct or a final class. The class must be final because the TypeSafeMiddleware protocol includes a static function with a Self type reference.

When defining a conformance to TypeSafeGoogleToken, the user must define:

id: String representing the (app-scoped) unique identifier for a subject,
name: String representing the subject's display name,
additional properties may be declared matching the available fields from the Google user profile API. Examples of such properties are included in the GoogleTokenProfile.

An example declaration:
import CredentialsGoogle

// Defines the user's session instance data.
struct MyGoogleToken: TypeSafeGoogleToken {
    let id: String
    let name: String
    let email: String?
}

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ace87f4). Click here to learn what that means.
The diff coverage is 60%.

@@            Coverage Diff            @@
##             master      #30   +/-   ##
=========================================
  Coverage          ?   19.17%
=========================================
  Files             ?        5
  Lines             ?      219
  Branches          ?        0
=========================================
  Hits              ?       42
  Misses            ?      177
  Partials          ?        0

Flag
Coverage Δ

#CredentialsGoogle
19.17% <60%> (?)

Impacted Files
Coverage Δ

Sources/CredentialsGoogle/TypeSafeGoogle.swift
22.22% <22.22%> (ø)

...ources/CredentialsGoogle/TypeSafeGoogleToken.swift
83.72% <83.72%> (ø)

Continue to review full report at Codecov.

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

@ianpartridge FYI, this is the Google equivalent of: https://github.com/IBM-Swift/Kitura-CredentialsFacebook/pull/41
Where applicable, I have incorporated Helen's review comments in this one.

The missing doc on GoogleTokenProfile was due to there being no code between the copyright header and the doc header on the struct.  I've worked around this by adding a redundant import Foundation.  It's not great but it doesn't cause any harm.


Ml asap

Modify to run a native ASAP3. HPCC runs should not be affected.
What's changed

added an extra variable servername <- Sys.info()['nodename'] in getrunInfo.R. I use this to make new values of runClass.
runSetup.R has places to specify the path to ASAP3 (linux) or ASAP3.EXE (Linux with WINE). This depends on runClass
runSetup.R has a warning message about runClass if it is not set to a few known values.
getASAP.R now executes different commands based on runClass.

To run ASAP3 natively in Linux, you must.

Get the ASAP3 source code. rename asap3.tpl to ASAP3.tpl
Use ADMB to compile it.
Update the full.path.to.asap in runSetup.R
Update the asapEst in get_ASAP.R

Sorry, I did something wrong in PR #206, I think i either built it on the Econ_only2 branch or pulled Econ_only2 into that branch. And We definitely dont want that now.
Edit:
This built from master and tested just a minute ago on the NEFSC neptune servers by just running "runSim.R" .

This address a tangent to #201.

Great, thanks. We are going to work on testing on this end.


Cannot compile on Debian 11

Using cmake.sh script to install and configure automatically all dependencies, when doing the make, I get the following error on Debian 11:
[ 84%] Building CXX object test/CMakeFiles/ut-clib.dir/timestamp.cc.o
[ 87%] Building CXX object test/CMakeFiles/ut-clib.dir/version.cc.o
In file included from /root/lab/centreon-clib/test/version.cc:20:
/root/.conan/data/gtest/cci.20210126/_/_/package/e019a06362b932ca5d1b082b6c112aa150c88de4/include/gtest/gtest.h: In instantiation of ‘testing::AssertionResult testing::internal::CmpHelperEQ(const char*, const char*, const T1&, const T2&) [with T1 = int; T2 = unsigned int]’:
/root/.conan/data/gtest/cci.20210126/_/_/package/e019a06362b932ca5d1b082b6c112aa150c88de4/include/gtest/gtest.h:1564:23:   required from ‘static testing::AssertionResult testing::internal::EqHelper::Compare(const char*, const char*, const T1&, const T2&) [with T1 = int; T2 = unsigned int; typename std::enable_if<((! std::is_integral<_Tp>::value) || (! std::is_pointer<_Dp>::value))>::type* <anonymous> = 0]’
/root/lab/centreon-clib/test/version.cc:26:3:   required from here
/root/.conan/data/gtest/cci.20210126/_/_/package/e019a06362b932ca5d1b082b6c112aa150c88de4/include/gtest/gtest.h:1545:11: warning: comparison of integer expressions of different signedness: ‘const int’ and ‘const unsigned int’ [-Wsign-compare]
 1545 |   if (lhs == rhs) {
      |       ~~~~^~~~~~
[ 89%] Linking CXX executable ut-clib
/usr/bin/ld: cannot find -lcentreon_clib
collect2: error: ld returned 1 exit status
make[2]: *** [test/CMakeFiles/ut-clib.dir/build.make:257: test/ut-clib] Error 1
make[1]: *** [CMakeFiles/Makefile2:1035: test/CMakeFiles/ut-clib.dir/all] Error 2
make: *** [Makefile:160: all] Error 2

With Debian 10 works normally
More information:
# neofetch
       _,met$$$$$gg.          root@debian11
    ,g$$$$$$$$$$$$$$$P.       -------------
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 11 (bullseye) x86_64
 ,$$P'              `$$$.     Host: BHYVE 1.0
',$$P       ,ggs.     `$$b:   Kernel: 5.10.0-8-amd64
`d$$'     ,$P"'   .    $$$    Uptime: 22 mins
 $$P      d$'     ,    $$P    Packages: 1038 (dpkg)
 $$:      $$.   -    ,d$$'    Shell: bash 5.1.4
 $$;      Y$b._   _,d$P'      CPU: Intel i3 550 (2) @ 3.190GHz
 Y$$.    `.`"Y$$$$P"'         GPU: 00:06.0 Vendor fb5d Device 40fb
 `$$b      "-.__              Memory: 86MiB / 1981MiB
  `Y$$
   `Y$$.
     `$$b.
       `Y$$b.
          `"Y$b._
              `"""

hello,
this bug is normally corrected by these PR:
https://github.com/centreon/centreon-clib/pull/57/files
https://github.com/centreon/centreon-engine/pull/541
Regards.


default to workspace TS version in .vscode/settings.json

Add the following to .vscode/settings.json
{
  "typescript.tsdk": "node_modules/typescript/lib"
}

typescript.tsserver.pluginPaths

I don't think it'll work to force the plugin paths

Yeah, this setting has to be set personally.


How to get the .graph file？

mmconvert -sf tensorflow -in model.ckpt-30000.meta -iw model.ckpt-30000 --dstNodeName add -df caffe -om tf_align
Parse file [model.ckpt-30000.meta] with binary format successfully.
Tensorflow model file [model.ckpt-30000.meta] loaded successfully.
Tensorflow checkpoint file [model.ckpt-30000] loaded successfully. [36] variables loaded.
Traceback (most recent call last):
File "/home/super/.local/bin/mmconvert", line 11, in
sys.exit(_main())
File "/home/super/.local/lib/python2.7/site-packages/mmdnn/conversion/_script/convert.py", line 102, in _main
ret = convertToIR._convert(ir_args)
File "/home/super/.local/lib/python2.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 68, in _convert
parser = TensorflowParser(args.network, args.weights, args.dstNodeName)
File "/home/super/.local/lib/python2.7/site-packages/mmdnn/conversion/tensorflow/tensorflow_parser.py", line 221, in init
model = extract_sub_graph(model, dest_nodes)
File "/home/super/.local/lib/python2.7/site-packages/tensorflow/python/framework/graph_util_impl.py", line 174, in extract_sub_graph
_assert_nodes_are_present(name_to_node, dest_nodes)
File "/home/super/.local/lib/python2.7/site-packages/tensorflow/python/framework/graph_util_impl.py", line 133, in _assert_nodes_are_present
assert d in name_to_node, "%s is not in graph" % d
AssertionError: add is not in graph

hello！ Could you tell me how to solve this problem ? Thx!


Ignore vm.overcommit for redis on lxc

Attempting to set this in an lxc container results in this
# sysctl -w "vm.overcommit_memory=1"
error: permission denied on key 'vm.overcommit_memory'

Even though
# id && mount | grep proc
uid=0(root) gid=0(root) groups=0(root)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)

This change will get rid of the permissions error during the chef run, but might cause trouble with Redis in operation under an LXC container. Redis may fail to background save without the kernel being told to allow overcommit.

@robbkidd What would you like to do with this?
It sounds like it's impossible to set this setting in a container.
Would you rather fail the Supermarket install and direct the user out to the Host of the container to fix it?

@sean-horn After talking with the team, we concluded it would be better to fail the Chef run than to allow overcommit_memory to be false and leave the possibility that Redis will silently fail to save. I'm investigating options around catching the failure and re-raising with a message to the user about making that setting change on the LXC host.

@sean-horn I'm poking at this issue again today. Do you have a record of the stacktrace from a failed Chef run in LXC?

@robbkidd Cool! Sounds like the right thing to do. Thanks

Closing this PR now that the omnibus packaging has moved over to combine with chef/supermarket. This issue is being tracked (and worked soon!) in chef/supermarket#1262


Release v1 2 0

Releasing v1.2.0 and adding a new mage command to prepare releases: ./mage prepare_release v1.2.0

I like the idea, updated!


Missing WebKit example

Issue
No Cypress Docker images include a WebKit browser and there is no example showing how to use WebKit with a Cypress Docker image.

Cypress documentation includes a section Guides > Launching Browsers > WebKit (Experimental) which describes how to use Cypress with WebKit.
https://github.com/cypress-io/cypress-docker-images/blob/7c65baf2cc1b1f0bf585f7d72b58bfe3ad4815ff/factory/.env#L35-L37 includes an open TODO regarding WebKit which refers to https://github.com/cypress-io/cypress/issues/25344. This issue was however closed due to inactivity.

If there is interest in having an example documented of using WebKit with Cypress Docker images then I would submit a PR contribution for this.

This needs to be deferred until there is more clarity about version compatibility.


Change text to "Mute Audio"

On the dashboard, on the stream detail page (homepage -> create stream), when creating a multistream destination there's a checkbox that reads "video only." This isn't clear that this check box removes the audio.
Change this text to read "Mute Audio"

https://github.com/livepeer/livepeer-com/pull/691


sofia-sip depend

Hello Dave,
while the issue should go into https://github.com/davehorton/sofia-sip/issues I think it is worth mentioning it here because it is a depend of drachtio-server.
The version of sofia-sip under github.com/davehorton, as you stated, is a fork of the original sofia-sip from 2014.
Reading a bit the commit backlog I noticed that you didn't cherry-pick the commits from the original version but the program followed an 'its own' way.
So in the meantime there were a lot of improvements. The commits talks also about crash/overflow, so there may be security bugs fixed silently and there are three recent CVE: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=sofia-sip
Did you plan to improve the situation in any way? e.g. put your modifications under the main sofia-sip (if they accept them) or maintain a proper fork?
Thanks

I felt I could not do a simple fork because I had to make some additions for my usage that the older code did not have.  Also, the repo is now maintained by the freeswitch people, and they do not use the nta library that drachtio uses, they use the nua library and most of their fixes are pointed there.  That said, I will review those commits and bring over the ones that seem useful


Support custom scope for ADFS custom claim

Hello,
On ADFS 2016 it is possible to configure some custom claims with OpenID Connect sign-in,
but it is necessary to send a custom scope.
On https://github.com/boylesoftware/tomcat8-oidcauth/blob/master/src/main/java/org/bsworks/catalina/authenticator/oidc/OpenIDConnectAuthenticator.java line 518, scope is hardcoded.
would it be possible to add a configuration for this (as userNameClaim) ?
I can do a pull request if you want

We are preparing a long due new revised/refreshed release of this module in a few days, phasing out 8.0 support from the main branch. Configurable login name claim is going to a part of it.

The new 2.0 release now includes "additionalScopes" attribute in the authenticator configuration.


The name isn't completely highlighted after renaming it with a longer name

OS: All
Build Version: 20200731.2
Repro Steps:

Open one deployment template in VS Code.
Select one variable name and rename it with a longer name.
Check the result.

Expect:
The name is completely highlighted.
Actual:
The name isn't completely highlighted.

More Info:
This issue also reproduces when renaming a parameter.

Verified on the latest build 20201215.1, this issue also reproduces for now, we will continue to track this issue.


Authorization not in header

Hey guys,
With Slim2 I was able to get the value supplied in the Authorization in the headers but with Slim3 i can't get it.
I can get other header parameters though.
This is what I have tried
$request->getHeader("Authorization")

Is there any other way to access this?

That is how you read a header field.

Call to $request->getHeader("Authorization") works fine. However if you are using Apache and send something else than valid basic auth header PHP won't have access to it unless you add the following to your .htaccess file.
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

@tuupola Thanks it works. I am using apache. Does this also fix if am using nginx?
For apache server, this is how I had hacked it :dart:
$headers = apache_request_headers();
$headers["Authorization"];

@bmutinda The missing Authorization header appears to be an Apache only thing.

On Apache 2.4 (before 2.4.13) with PHP-FPM this rewrite would work
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
but it will result in a REDIRECT_HTTP_AUTHORIZATION header which is still not accessible by
$request->getHeader("Authorization")
Apache 2.4.13 introduced a CGIPassAuth directive that would allow passing the Authorization header to the script although I haven't tested this myself.
For now the only workarounds are to either access $_SERVER['REDIRECT_HTTP_AUTHORIZATION'] or use a custom header name.

https://github.com/slimphp/Slim/pull/898 was Slim 2 pull request regarding this

Thanks I was only searching for Slim 3. Any chance a similar PR would be accepted for 3?

@akrabat
I have this issue and cant solve it. I am using nginx and Slim 3 heres my route
`$app->get('/api/private/offers', function($request, $response, $next){
//$headers = apache_request_headers();
$headers = $request->getHeaders();
var_dump($headers);`

})
Here is the output
`array (size=11)
 'HTTP_COOKIE' =>
 array (size=1)
  0 => string 'PHPSESSID=p8r0lrt3ujkj24jac72hnh1fqs' (length=36)
 'HTTP_ACCEPT_LANGUAGE' =>
  array (size=1)
  0 => string 'en-US,en;q=0.9' (length=14)
  'HTTP_ACCEPT_ENCODING' =>
  array (size=1)
  0 => string 'gzip, deflate' (length=13)
  'HTTP_ACCEPT' =>
  array (size=1)
  0 => string
  'text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8' (length=85)
   'HTTP_UPGRADE_INSECURE_REQUESTS' =>
array (size=1)
  0 => string '1' (length=1)
   'HTTP_USER_AGENT' =>
array (size=1)
  0 => string 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36' (length=114)
    'HTTP_CACHE_CONTROL' =>
array (size=1)
  0 => string 'max-age=0' (length=9)
    'HTTP_CONNECTION' =>
array (size=1)
  0 => string 'keep-alive' (length=10)
    'Host' =>
array (size=1)
  0 => string 'offline-report.test' (length=19)
   'CONTENT_LENGTH' =>
array (size=1)
  0 => string '' (length=0)
    'CONTENT_TYPE' =>
array (size=1)
  0 => string '' (length=0)`

Notice 'Authorization' header is not included
I enabled the CORS as per Slim Docs
`$app->options('/{routes:.+}', function ($request, $response, $args) {
return $response;
});
$app->add(function ($req, $res, $next) {
$response = $next($req, $res);
return $response
->withHeader('Access-Control-Allow-Origin', '*')
->withHeader('Access-Control-Allow-Headers', 'X-Requested-With, Content-Type, Accept, Origin, Authorization')
->withHeader('Access-Control-Allow-Methods', 'GET, POST, PUT, DELETE, OPTIONS');
});`
Trying
    //$headers = apache_request_headers();

Still same result. Do you have in idea for this? I am using NGINX

I've never used nginx. Maybe ask on the forums.


Add endpoint for users to get their actions

#1589
The issue in the ticket was because the UI was comparing
the GitHub username with the Google email address that came back from
the permissions call. That, plus the fact that I had forgotten about
SAM's support for groups, means we do need an endpoint to indicate
the actions a user can perform on workflow.
I had this before, with OPTIONS operations on a few API calls, but it
was clunky and overkill, so I've added a new endpoint,
/path/workflow/{repository}/actions, that returns the actions a user
can perform on a workflow.
The issue with groups is that a user can be given permissions to a
resource through a group -- in that case the user's individual email
will not show up in the list of permissions. So we could not tell
client-side what a user's permissions are just by reading the email
addresses.
Also:

Added Not Implemented to state changing operations in
NoOpPermissionsImpl, just in case it gets turned on and somebody
tries to use it.
Not sure why openapi and swagger files have new endpoint unrelated
to my changes; maybe they not commited with a change made to
WorkflowResource?

Please make sure that you've checked the following before submitting your pull request. Thanks!

[] Check that you pass the basic style checks and unit tests by running mvn clean install

Coverage decreased (-4.1%) to 70.292% when pulling<PHONE_NUMBER>13adcb7def4bb3909d0903ecab32aa on feature/1589/actionsendpoint into 8d3a94a9eadd08f0323ceeba91c8a0228d41a2ad on develop.


[Proposal] Integrate with vcluster https://www.vcluster.com/

Issue Description

https://www.vcluster.com/
As a cluster admin, I want to create some tenant clusters with sealer images on a hosted cluster for some multi-tenancy cases.

Type: feature request
Describe what feature you want
Additional context
Add any other context or screenshots about the feature request here.

Thanks for your feature request @gyliu513
I have to say this is quite farsighted. Now sealer's architecture is still evolving and not so stable. In our roadmap https://github.com/sealerio/sealer/blob/main/ROADMAP.md we aim at separating distributed application and k8s infra and basic infra explicitly. I think the vcluster part could be located in k8s infra layer to enhance virtual multi-tenancy ability.
@starComingup @justadogistaken When we re-arch the underlying  architecture, we could take k8s infra scalability into consideration.

Thanks for your feature request @gyliu513 .
And after I view the vcluster introduce. It may just Dependent a bin file like vcluster?
In my opinion, you may just focus on how to build cloudImage.
FROM kubernetes:v1.19.8
COPY vcluster /bin
COPY helm /bin

vluster look like rely on helm but I'm not for sure, but install helm can help you deploy chart smoothly!

Also you can expand any chart or imageList as you need it in Kubefile, read http://sealer.cool/docs/getting-started/build-cloudimage.html#build-instruction  may help you write kubefile. And read http://sealer.cool/docs/reference/cloudrootfs.html#how-can-i-get-cloudrootfs may help understand the principle of Sealer rootfs.
I'd like to know if this method would help you a little. I have been validated this method in ubuntu 20.04.1 LTS.

@allencloud @starComingup thanks for the update.
Here I was hoping I can use sealer create or sealer apply to create a vcluster with specified apps, is it possible to add some options in sealer create like -v vcluster, and this wil create a new vcluster.
I mainly want to use the feature of ClusterImage to create a vcluster on existing host cluster.

@starComingup I think the feature from @gyliu513 is different with the way you create a new vcluster. What you suggest to do is packaging vcluster into image, it may fail to deal with scalability for the whole cluster. Maybe we need to learn more about vcluster, and consider the way of integrating vcluster. Making it a image may not be the best approach.
(I'm getting to know the background)

@justadogistaken yes, I was hoping sealer create, sealer apply can create both physical cluster and virtual cluster based on some config parameters.

we aim at separating distributed application and k8s infra and basic infra explicitly.

@allencloud , this is great feature, any timeline for those features?

@gyliu513 It's great for expanding usage scenarios for sealer. But the sealer community is going to re-design the architecture, and it's a long-term job. So integrate with vcluster may not be the high-priority task to work on. And thanks for inputting such usage case to us. We will let you know when we start to deal with this feature.


[BUG] - SQLite experience with conda-store is not great

Describe the bug
The root of the issue is the length of transactions and when conda-store-server is initially starting it attempts to update the sqlite database with bulk inserts. I believe bulk inserts are the key problem here.
The sqlite database currently gets locked frequently.
Expected behavior
SQLite should be a great database choice for sqlite. Especially for the local use case.
How to Reproduce the problem?
Run conda-store-server locally.
Output
No response
Versions and dependencies used.
No response
Anything else?
No response

@costrouc Could you please add more thoughts here from today's meeting? You had some other ideas on what might help and some differences between SQLite and Postgres.

I've been using standalone mode and have not observed the same bulk insert performance issues, so I'm not sure if this issue is still relevant. Please reopen if this is still a problem in the future.


Add decrlarations from ceval.h

Add PyEval_InitThreads and PyEval_ThreadsInitialized.
Resolves #2205.

Adding a link to my comment, https://github.com/cython/cython/issues/2205#issuecomment-398511174, here in case it's of any value.


[AGE VIEWER  DESKTOP]Fix Error From API Integration To backend

[AGE VIEWER  DESKTOP]Fix Error From API Integration To backend Correct EndPoints.

@aked21 Please merge, reviewed the PR


A possible bug in Data Process

Thanks for your released beautiful and easy-to-follow code ! It is very helpful to the dense retrieval researchers as me.
However, maybe I have met a bug in the preprocess.py. As the model requires to use the RoBERTa-base model for initialization, the native pad token is 1 but not 0. While I found that in this file, the pad token is set to 0 (the [CLS] token id), which has caused that the pre-trained model checkpoint can not achieve the same results as reported in your paper.
https://github.com/jingtaozhan/DRhard/blob/main/preprocess.py#L23

Thanks for the nice words and for raising the issue.
This is indeed a `bug'. Nevertheless, the pad_token_id is actually not important because attention_mask will mask these pad tokens. Because of attention_mask, I think pad tokens can be any tokens. I wonder whether this actually causes performance loss. What are your reproduced results?
Best

Sorry for later response.
I agree that the pad token can be any tokens. But once I use the following code to build the attention mask, a possible bug would happen, where the CLS position will be also masked.
mask = input_ids == pad_token
I have successfully reproduced the results as the paper mentioned, while found this problem when I was going to revise the code for using other dense retrieval methods. Anyway, it is not a serious problem but a possible bug for users who are not familiar with this task. I just raise this issue for a notification. :)
Best


fix testing memcache_servers for localhost under Puppet 4

When running under Puppet 4 (or presumably simply with the future parser), an
error is raised when trying to perform a regex check against an array. Using
functions from the stdlib module, ensure $memcache_servers is an array before
using grep to check each element for localhost.

Thank you for contributing to stackforge/puppet-swift!
stackforge/puppet-swift uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Align allowed aggregations

What are you changing in this pull request and why?

The page on Measures for the SL lists different values allowed for agg in the first table and in the paragraph a bit lower.
This aligns the definitions (but do we want to maintain those 2 lists separately?).

merging ths now for you @b-per !


For test

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.84%. Comparing base (a8e4c31) to head (5eea4a1).
Report is 15 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   91.96%   92.84%   +0.87%
==========================================
  Files          58       40      -18
  Lines         971      699     -272
  Branches      126       98      -28
==========================================
- Hits          893      649     -244
+ Misses         74       46      -28
  Partials        4        4

Flag
Coverage Δ

backend
?

frontend
92.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Displaying subtype probabilities for RF models for single-cell results

Related to #76.
Here, I'm presenting some ideas for how we might visualize probabilities for the RF model outputs in the single-cell notebook (both pseudobulk and individual cell results). I expect this notebook and the upstream prediction script will be further updated to include GSE155446 (and probably refactored a bit!) shortly. So, my goal is to have ideas and code for how to visualize the probabilities in as a reference before we make those changes. As such, I didn't concern myself too much with polishing.
Summary of changes to plots:

Plotting a stacked barplot for kTSP where the x-axis shows a percentage of the total score; this panel gets combined with an RF plot using probabilities, which sum to 1 and don't require any calculations/wrangling.
Adding a plot that uses points instead of a stacked barplot as another option
Adding a faceted UMAP where the points are colored by the G3 and G4 probabilities
Adding a stacked barplot that shows probabilities for individual cells in the 3 mixed samples
I've removed the combined plots for now because I think it's too early to say what the combined plots should be!

I am also updating predict/predict_pseudobulk_and_single_cells.R to output the pseudobulk results in wide-format for plotting.

:sparkle: sounds great!
On Fri, Nov 22, 2024 at 15:24 Jaclyn Taroni @.***>
wrote:

@.**** commented on this pull request.
In analysis_notebooks/pseudobulk_and_single_cells.Rmd
https://github.com/AlexsLemonade/medulloblastoma-classifier/pull/80#discussion_r1854608282
:

+# Calculate the % of total score for each subgroup for the kTSP model
+# This will allow us to use 0-100 for the x-axis

I'm fairly convinced now we should use raw kTSP scores and not modify them
by total_score...
Yea, I was also leaning towards this. I might vote for the points plot for
kTSP raw scores.
—
Reply to this email directly, view it on GitHub
https://github.com/AlexsLemonade/medulloblastoma-classifier/pull/80#discussion_r1854608282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPG5BE5JMW7I7YZXK4N5TL2B6HGTAVCNFSM6AAAAABSHYYN4GVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINJVGU3TANBQGM
.
You are receiving this because your review was requested.Message ID:
@.***
.com>


Remaining bug in Audit Raw Data - see closed issue #147

The Audit Raw Data plots still do not update properly.  When a spot is removed (using right click menu), the plots in this window do not update (although the correct data point is removed from further processing).  The attached video demonstrates this by removing a data point where the duoplasmatron went out (primary beam intensity to 0).  This is a very distinct data point, and when I remove it from the prawn file, it persists in the Audit Data plot (but it gets renamed to the next point in the list)
Video_2018-08-21_135445.zip

Nice catch.  It turns out this was only a problem with primary beam and qt1y and qt1z - the correct spot was removed but the grapher for these three was not using updated data.  Fixed in next release.


[single-instance][v2] no method named emit found for reference &AppHandle<_> in the current scope

By using single-instance plugin, we follow README:
.plugin(tauri_plugin_single_instance::init(|app, argv, cwd| {
            println!("{}, {argv:?}, {cwd}", app.package_info().name);
            app.emit("single-instance", Payload { args: argv, cwd }).unwrap();
        }))

But we got this error:
error[E0599]: no method named `emit` found for reference `&AppHandle<_>` in the current scope
   --> src\lib.rs:13:11
    |
13  |       app.emit("single-instance", Payload { args: argv, cwd }).unwrap();
    |           ^^^^
    |
    = help: items from traits can only be used if the trait is in scope

cargo.toml
tauri = { version = "2.0.0-beta.24", features = ["isolation"] }
tauri-plugin-single-instance = "2.0.0-beta.11"

In the latest tauri version you now need to add use tauri::Emitter; to your file to use emit(). Normally the compiler error should tell you about that right where you cut off the message.


[WIP] Simple heuristics to reject loading of crossdomain SWFs.

Basically it's tracking all allowDomain calls and adds them to the whitelist. Before loading a new SWF Loader.load checks if the remote SWF allowed by this whitelist.
/cc @tschneidereit

/botio preview

Excellent! I commented on a few nits, mostly around naming, but this looks very good.

/botio test

/botio test


LDAP/AD configuration

Hello,
That is possible to have LDAP and AD for authentication ?
with adding 3 parmeters  i think it spossible
[Class to search]
[User attribute to search]
[LDAP search base]
login.py => bind = l.simple_bind_s([Class to search]+'='+user+','+[LDAP search base], password)
options.py => criteria = "(&(objectClass=[Class to search])([User attribute to search]="+username+"))"
Regards,

Yes, it's possible

And "LDAP search base" is not the same "Base domain. Example: dc=domain, dc=com"

I check it


Fix bugs improvements refactors

Added new logo in Welcome message.
Configure Welcome command to work on Direct LIne.

Codecov Report

Merging #509 (e948481) into main (9a66557) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #509   +/-   ##
=======================================
  Coverage   32.84%   32.84%
=======================================
  Files          76       76
  Lines        2128     2128
=======================================
  Hits          699      699
  Misses       1429     1429

Continue to review full report at Codecov.

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


Follow up the license rules

Add the NOTICE file and the copyright part for the missed files. Create a link in the README.md.

This PR was partially landed manually. This repository no longer follows GloDroid progress and will be archived. Closing.


New notification settings page in Manage

Context
As part of a new design, we have simplified the notification settings page
Changes proposed in this pull request
Link to the existing notification settings page from the new "Your account" page
Update the content on the page behind the feature flag
Guidance to review
I didn't add a new route here because it didn't seem necessary.
Link to Trello card
https://trello.com/c/PDNnOsg9/4047-add-your-email-notifications-page-to-your-account
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

@cwrw This version has a subset of the ones in the prototype (and in a different order). I think adding the new settings will be a different piece of work – not sure if there's a card for it yet


Select a custom Opam repo

Hi!
I’m experimenting with Duniverse. How do I chose a custom Opam repository?
I saw the code:
https://github.com/ocamllabs/duniverse/blob/44b74dc6bb97c2a316e749055bd7b8ba338232ca/cli/init.ml#L94-L97
and
https://github.com/ocamllabs/duniverse/blob/44b74dc6bb97c2a316e749055bd7b8ba338232ca/lib/config.ml#L31
Can the repository be selected from the command-line, or do I have to change the value or duniverse_opam_repo? What’s the #duniverse fragment for in the URI?
Thanks!

You should indeed be able to select your own opam-repository from the command line by passing it to duniverse init with the --opam-repo <path_or_url> CLI option.
When pointing to a git repository you can select a particular branch with the #<branch_name> suffix, that's what the #duniverse part of the default URL is.
Also note that the documentation for this option isn't up to date and that the provided opam-repository isn't used as a complement to the regular one but as a full replacement. That means it should provide all the packages you need and not only dune port of the packages that haven't been ported yet on https://github.com/ocaml/opam-repository.

Thanks!
I don’t remember how I managed to get duniverse running in the first place, because now I have the same compilation failure as the CI.

Hmm I'm not getting this error locally but I don't bootstrap dune, I just use the version I installed through opam.
Can you tell me a bit more how you ended up with this error so I can try to reproduce it?

I did not bootstrap dune or duniverse, I installed dune through Opam, and did a fresh clone of the duniverse repo, and got the same error as the CI.
$ opam --version
2.0.6
$ ocaml --version
The OCaml toplevel, version 4.09.0
$ dune --version
2.3.1
$ git clone git@github.com:ocamllabs/duniverse.git
$ cd duniverse
$ make
dune build
    discover duniverse/base.v0.13.0/src/mpopcnt.sexp (exit 2)
(cd _build/default/duniverse/base.v0.13.0/src && discover/discover.exe -o mpopcnt.sexp)
Fatal error: exception Configurator__V1.Fatal_error("Configurator scripts must be run with Dune. To manually run a script, use $ dune exec.")
make: *** [Makefile:6 : build] Error 1

Hmm ok interesting, there might be an issue with duniverse's duniverse.
Can you try running:
opam install --deps-only -t .

to get the dependencies through opam and see if it works?
I have a local opam switch with all the dependencies installed, I'm running the same versions of dune and OCaml as you are and I get it to build and run the test without issues.
I'll try creating a fresh switch a bit later to see if I can reproduce but in the meantime that might be enough. If it's not try adding (data_only_dirs duniverse) to the root dune file. It's not great but at least you should be able to build it!

Installing the dependencies via Opam did not change anything, apparently duniverse still fetches its dependencies in the duniverse/ directory and not in Opam tree.
opam install ./duniverse.opam
duniverse is now pinned to git+file:///home/antonin/duniverse#master (version ~dev)
The following actions will be performed:
  ∗ install duniverse ~dev*

<><> Gathering sources ><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
[duniverse.~dev] synchronised from git+file:///home/antonin/duniverse#master

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><>
[ERROR] The compilation of duniverse failed at "/home/antonin/.opam/opam-init/hooks/sandbox.sh build dune build -p duniverse -j 11
        @install".

#=== ERROR while compiling duniverse.~dev =====================================#
# context     2.0.6 | linux/x86_64 | ocaml-system.4.09.0 | pinned(git+file:///home/antonin/duniverse#master#44b74dc6)
# path        ~/.opam/default/.opam-switch/build/duniverse.~dev
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p duniverse -j 11 @install
# exit-code   1
# env-file    ~/.opam/log/duniverse-151732-60459a.env
# output-file ~/.opam/log/duniverse-151732-60459a.out
### output ###
#     discover duniverse/base.v0.13.0/src/mpopcnt.sexp (exit 2)
# (cd _build/default/duniverse/base.v0.13.0/src && discover/discover.exe -o mpopcnt.sexp)
# Fatal error: exception Configurator__V1.Fatal_error("Configurator scripts must be run with Dune. To manually run a script, use $ dune exec.")

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
┌─ The following actions failed
│ λ build duniverse ~dev
└─
╶─ No changes have been performed

As you predicted, adding (data_only_dirs duniverse) produced a working executable.

It might be interesting to do a batch update of all the dependencies in the duniverse/ directory, now that OCaml 4.10 is out. For instance, ppxlib.0.10.0 does not build, but is fixed in its last (0.12.0) version.
File "duniverse/ppxlib.0.10.0/ast/pprintast.ml", line 1301, characters 17-25:
1301 |             else Misc.may (pp f "(%s:%a)" s.txt (module_type ctxt)) mt;
                        ^^^^^^^^
Error: Unbound value Misc.may

Yeah you're right that it needs to be fixed! I'll try to take a look ASAP!
If you don't mind, I'd like to close this issue and open a separate one about updating and fixing the duniverse specifically.

Also note that the documentation for this option isn't up to date

It would be nice to update the documentation with all the available options.


v9: The legacy expo-cli does not support Node +17.

Describe the bug
Creating a new project crash.
Tested on the brand new macOS Sonoma with Xcode 15.0
npx ignite-cli@next new PizzaAppNext --verbose
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

✅ What bundle identifier? · com.pizzaappnext
✅ Where do you want to start your project?  (Y/n) · Yes
✅ Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · No
✅ Which package manager do you want to use? · yarn
✅ Do you want to install dependencies? (Y/n) · Yes
✅ ❗EXPERIMENTAL❗Would you like to enable the New Architecture? (y/N) · No

    🖨  3D-printing a new React Native app
    🎨 Getting those last few details perfect
    🧶 Installing yarn dependencies (wow these are heavy)
    ⠇  Generating native template via Expo Prebuild
/Users/cerebra/.npm/_npx/2351a7c35afcf833/node_modules/gluegun/build/index.js:15
    throw up;
    ^
WARNING: The legacy expo-cli does not support Node +17. Migrate to the versioned Expo CLI (npx expo).
[12:46:52] Error reading Expo config at /Users/cerebra/workspace/rn/PizzaAppNext/app.config.ts:

⨯ Unable to compile TypeScript:
error TS6053: File 'expo/tsconfig.base' not found.

(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.15.0

Hint I think gluegun needs to be updated to the last version to be node v18+ compatible?
https://github.com/infinitered/gluegun/commit/0386d445b51c5595bd2c5e1d0e238581f1af9ebe
Ignite version
9.0.0-alpha.6
Additional info

❯ npx ignite-cli doctor
System
  platform           darwin
  arch               arm64
  cpu                8 cores      Apple M1
  directory          rn           /Users/cerebra/workspace/rn

/Users/cerebra/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:13
    throw up;
    ^
Usage Error: No project found in /Users/cerebra/workspace/rn

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...

(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.15.0

@jvm-cognition this is the type of error we want to catch gracefully with regards to the issue you are working on

@flexbox it seems as if this died on prebuild - can you cd into the directory and run yarn prebuild:clean and see if there are any other error messages associated with it?

it's weird I thought I removed globally expo-cli from my machine
⨯ Unable to compile TypeScript:
error TS6053: File 'expo/tsconfig.base' not found.

~/workspace/rn/PizzaAppNext
❯ where expo
/Users/cerebra/.nvm/versions/node/v18.15.0/bin/expo
/usr/local/bin/expo

~/workspace/rn/PizzaAppNext
❯ where expo-cli
/Users/cerebra/.nvm/versions/node/v18.15.0/bin/expo-cli
/usr/local/bin/expo-cli

~/workspace/rn/PizzaAppNext
❯ yarn --version
3.4.1

expo init

is the legacy cli
from the docs

That's what I ran

~/workspace/rn
❯ npx expo init NewExpoApp

  $ expo init is not supported in the local CLI, please use npx create-expo-app instead

~/workspace/rn
❯ npx create-expo-app NewExpoApp
✔ Downloaded and extracted project files.
> npm install

and then
npx expo prebuild --clean

is working

Yeah it doesn't. We just call prebuild. Can you try clearing your npx cache?
Something like rm -rf ~/.nom/_npx

The WARNING: The legacy expo-cli does not support Node +17. Migrate to the new local Expo CLI: https://blog.expo.dev/the-new-expo-cli-f4250d8e3421. warning also comes out if you haven't installed dependencies at all.

We are making progress 🚀
I ran
rm -rf ~/.npm/_npx

We should add an extra line here https://github.com/infinitered/ignite/blob/master/docs/Upgrading-Ignite.md
I tryed @9.0.0-alpha.7
npx ignite-cli@next new PizzaAppNextExpressoNoCache --verbose
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

    🧶 Installing yarn dependencies (wow these are heavy)
    ⠴  Generating native template via Expo Prebuild
/Users/cerebra/.npm/_npx/2351a7c35afcf833/node_modules/gluegun/build/index.js:15
    throw up;
    ^
npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
Git status is dirty but the command will continue because the terminal is not interactive.
CommandError: Error reading Expo config at /Users/cerebra/workspace/rn/PizzaAppNextExpressoNoCache/app.config.ts:

⨯ Unable to compile TypeScript:
error TS6053: File 'expo/tsconfig.base' not found.

Oh wow interesting, didn't consider yarn 2 with the doctor output failing. Will look into that thanks

See this thread about Expo and yarn2, might be a workaround you can try, but going to close this as likely not an Ignite issue directly
https://github.com/expo/expo-cli/issues/1073


Development

Hello @maborak! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file ebooksdl/rest.py:

Line 25:39: E202 whitespace before '}'


You attempted to set the key 'time' with the value '2017-05-31' on an object that is meant to be immutable and has been frozen.

Please I have raised an issuse before #14266 , but someone just closed it without solve this.they said the reason is that I try to changing prop value. But the fact is that even state value will also encounter this error.
now please see my code :
this.state{
     markerList : this.props.positionList,
}

render(){
     return(
        <CustomMapView markers = { this.state.markerList}/>
     )
}

aMethodWillThisIssuse(){
    var list = this.state.markerList;
    list[0].time = '2017-05-31';
    // **error occured here!!!**
}

What I can confirm is that my componentMapView is ok. and once I assign markerList to my customMapView component , the error will occured!
Please don't close this until we solve this, thanks.
PS: Android Platform + React Native 0.43.

They were right to close it. This is not related to React Native, and barely even to React itself. React is just nice enough to give you that informative message.
You say that even a state value will cause you to encounter the error. State is meant to be changed with setState, not by direct mutation. More than that, just because your state object "steals" the object from this.props does not mean that it becomes changeable. You need to be copying the object, because it is still referencing a frozen object.
There's no point in getting into greater detail, you should post on stackoverflow, and many would be happy to give you a more detailed explanation on why this is not working, and how to fix it. But make no mistake, this is not an issue with the react-native project, and will be closed. Please post on stackoverflow, it's easy and free.

@aaronofleonard Thanks for your feedback! I understand what you said. but what confuse me a lot is that I have assign the state value to a totally new variable.
var list = this.state.markerList;

it would be no related to the state value, but I still encounter this error when I try to change its value, that's the key point.

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


First Version of the batcave

First Version of the Batcave. Some adjustment may be needed in the futur.
Introducing:

BatGadget as standalone Gadgets that are registered in the batcave
BatBundles as a a collection of BatGadgets

Super cool stuff ! Thanks for contributing !


VSCode extension fails to format .cs file

Formatting does not work. I checked the debug output and this is the error message
["WARN" - 5:05:10 PM] Exception while running 'dotnet csharpier --version' in C:\Users\<WITHHELD>\AppData\Local\CSharpier\0.20.0
"Cannot use file stream for [C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.deps.json]: No such file or directory\r\nA fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\\Program Files\\dotnet\\'.\r\nFailed to run as a self-contained app.\r\n  - The application was run as a self-contained app because 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' was not found.\r\n  - If this should be a framework-dependent app, add the 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' file and specify the appropriate framework.\r\n"
["ERROR" - 5:05:10 PM] ,,Tool 'csharpier' is already installed.

["DEBUG" - 5:05:10 PM] returning NullCSharpierProcess because of the previous error when trying to set up a csharpier process

Operating System: Windows 11
dotnet --version: 6.0.202
Running dotnet csharpier --version in the built-in terminal works and prints 0.20.0

The IDE extensions use a version of csharpier installed to a custom location. This error sounds like that install is somehow corrupted. You could test it by running this
C:\Users\<WITHHELD>\AppData\Local\CSharpier\0.20.0\dotnet-csharpier --version`

Deleting that directory and restarting VSCode would get the extension to reinstall csharpier in the custom location.
In the past I've seen errors that seemed related. It could be that the custom install is sometimes interrupted and leaves the install directory in a non-working state. I think the other errors usually involved an empty directory though. It may be that I need to tweak the extensions again to get them smarter about installing csharpier or smarter about detecting conditions like this and recovering from them.

Thanks, deleting the folder and reinstall via dotnet tool uninstall / install works wonders!


Regen

cc @antoyo

@antoyo You are not against adding 'cargo fmt` check too?

I'm fine with cargo fmt.

Updated


Strongly type UTf8 strings using SafeHandle

Rename SafeUnmanagedMemoryHandle to Utf8StringHandle - it's now used in a strongly typed fashion rather than DangerousGetHandle()
The CLR will marshal a SafeHandle to and from IntPtr automatically which makes the delegates strongly typed, you can only pass in a Utf8StringHandle which is created through Utf8InteropStringConverter. Should make the API more readable.
All the InteropObjectInstance classes could be removed and the delegates could be changed to use SafeHandles, make the code more readable/maintainable in my opinion.
Let me know what you think.

If .Net standard 1.3 wasn't a target I'd probably have looked at using ICustomMarshaler
https://apisof.net/catalog/System.Runtime.InteropServices.ICustomMarshaler
Something like https://github.com/nikki-nn4/NimDemo/blob/e87abf020f26e6bc98c9d0ea4faf0cdc0cd0660e/Assets/nim/Utility/UTF8StringMarshaler.cs would probably work nicely. The signatures would be long, greatly simplified usage again. Just a passing comment.

Thanks, You can check in 2.2.2-develop225 :)


Linkedin Auth0 sign in page should implement Linkedin's SDK. The current Web implementation is suboptimal

Issue: LinkedIn has a fairly new SDK and it would be great if this was used on the auth0 sign in for LinkedIn. SDK Info here: https://developer.linkedin.com/blog/posts/2015/mobile-sdk-ios
Not only would this move the UI away from the suboptimal Web implementation, it could also fix a bug that we have been dealing with. This bug happens for Linkedin Sign-in, but not Active Directory Sign in. The issue is:
The Linkedin Auth0 sign in page web view has broken links.  Tapping on the following links does nothing:
Forget Password
Join Linkedin
Terms of Service
Privacy Policy.

This is in our pipeline but since the only way to get Linkedin SDK is by downloading it from their page (which is suboptimal for us) we are trying to figure out the best way to make this available for Carthage/CocoaPods.
About the broken links we noticed them and we're trying to fix them.


Mod used in Librum Modlist set to hidden

Modpack currently fails due to Dawn of Skyrm - AI Overhaul Patch having been set to hidden by the uploader:
https://www.nexusmods.com/skyrimspecialedition/mods/38527
"No solution for broken download Dawn of Skyrim - AI Overhaul Patch-38527-0-91-159-535-1188.7z ..."

Closed as workaround has been posted on discord