Trying to animate input view container using layoutIfNeeded causes field animation to trigger also

I have a UIview as a container for a SkyFloatingLabelTextField and another uiview that can grow its height. Im trying to animate that growing but when i use layoutIfNeeded for the container, i also can see the text for the input animating from the top to its position in the input field.
Is there a way to prevent the animation in this case?

You can try to empty the queue of waiting layout operations with layoutIfNeeded and use it again when you try to grow your view.

I have the same problem. @mania3908 did you found a solution?
To be honest: this is a bug in SkyFloatingTextField for me and I should not worry to workaround it.

Thanks guys for reporting, I can take a look.
If you can provide a sample project to reproduce it would make it much faster to track it down.
Thanks.

I can fix my issues by adding a simple layoutIfNeeded() before the animation block in -[SkyFloatingLabelTextField updateTitleVisibility:completion:].
See http://stackoverflow.com/a/12664093/5385140 - unfortunately the Apple link is down.
@mania3908 can you give it a try and check if your problem is also gone?

Calling layoutIfNeeded is usually needed when you want to animate constraint based layout changes. It's usually not required before regular UIView animations.
Can you provide a stripped down example to demonstrate the problem?

As @moogle19 identified the fix in #101 broke animations so I reverted it. I'll take a stab at fixing this

Hmm, I never notice that it breaks the animation. But it took another look and you are right.
Would be nice to find a solution that solve both animation problems.

I have tried calling a layoutIfNeeded() just before my UIView animated layoutIfNeeded() method but it didn't solve anything.
I've achieved a solution by doing so:
textField.delegate = self

extension YoutViewController: UITextFieldDelegate {
    func textFieldDidEndEditing(_ textField: UITextField) {
        self.view.layoutIfNeeded()
    }
}

This triggers just right in time before the keyboard hiding/showing animations and vice versa. All the animations in the page works correctly without interrupting the textField.


Links/URL and image not showing on Comments

Comment should display link(url) + image and other markdown
there are many comment made on steemit that takes markdown or image or link or url

@nil1511 i'm working on it. Will be in my next PR.


May I ask you to add a 2.3.x release of Carthage?

I still have users on iOS 9-10 ... I would be grateful

The 2.3.x release didn't use carthage..


Please add the option to copy the original (non-flipped) character.

Currently it is difficult to copy the character in non-flipped state (hiragana/katakana) to clipboard, as it is flipped immediately when mouse cursor is placed above it (hover). Sometimes it is desirable to copy the original character.
Maybe flipping could be inhibited by holding some keyboard key, or temporarily disabled by a button?

I'm working on a new version, where the copying won't be an issue. Hopefully I will find some time for that soon.
For now, as a workaround you can start selecting next to the card — that way you won't trigger the flip.


Transaction state exception: Cannot call "beginTransaction" in state "COMMITTING"

Describe the bug
Ran into this exception on a producer with
      const producer = kafka.producer({
        maxInFlightRequests: 1,
        idempotent: true,
        transactionalId: `${options.clientId}-${uuidv4()}`
      });

Full error:
KafkaJSNonRetriableError:
Transaction state exception: Cannot call "beginTransaction" in state "COMMITTING"
at Object.beginTransaction (node_modules/kafkajs/src/producer/eosManager/transactionStateMachine.js:25:23)
...
To Reproduce
We're not even able to replicate ourselves honestly.
Expected behavior
Read more about this particular error so we can work toward avoiding it.
Environment:

OS: Mac OS [11.6] (20G165)
KafkaJS version [1.15.0]
Kafka version [2.8.1]
NodeJS version [14(?)] - let me know if this actually matters, I am unable to find a quick answer

I think this is equivalent to #1282, except for starting a new transaction while there is already a transaction currently being committed. Closing this one in favor of that one.


[Request] Maintain clipping overlay for duration of next GCD

As it is currently, if you clip late in the GCD you may not see it - the red portion will disappear as soon as the GCD rolls over. My suggestion would be to retain the clipping portion of the overlay until the wheel reaches that point again, or until the next instance of clipping, whichever happens sooner.

I agree with this, it worked that way in a previous iteration, but I felt like it made the already cluttered wheel worse, and it got confusing when the clipped portion had to change size with cooldowns that speed up the GCD (MCH or DNC).
I was toying with the idea of displaying the clipped ms as a toast for a couple of seconds, see example here:

Would that work? would appreciate ideas on how to make it better.

That's a good point with the GCD changing duration, I hadn't considered that. I think a binary indicator would work better in my opinion, there's enough going on that a yes/no (or a yes/blank) would be preferable to something more to read.

You are right, might be too much information, I'm working with this right for now, because I can't think about a neater way that's easy to understand.

Obviously would have some setting to turn it off when it gets annoying.

I'm a bit torn, as that's more noticeable but I feel like the window isn't much longer than how long the red shows on the bar. Maybe making the slim bar's background red for the clipped GCD?

Yep, that looks a lot better:

I'll polish it a bit, add some config options and it will be in the next release.

Thanks! I'm looking forward to giving it a shot


Evac pod gravity

About the PR
Fixed Doors on lifeboats
Fixed gravity on pods and lifeboats
Fixed windows on lifeboats
Why / Balance
Fixes
Changelog
:cl:

fix: Lifeboats doors
fix: Lifeboats windows
fix: Lifeboats & Evac Pod gravity.

I dont know what this CL is trying to say to me ,

does the lifeboat still perform epic drifting manoeuvres and fly sideways


Authentication

There's now a logout button in the middle of nowhere on the screen but that's fine :)
Before: https://screenshot.googleplex.com/B97U4DwJs2F
After:
https://screenshot.googleplex.com/Fe1HKTP9n7j
https://screenshot.googleplex.com/x4pyswEhcVD
https://screenshot.googleplex.com/bVqpeDuX26o


FEATURE: minimal parser and bytecode generation, for browser bundling

Howdy Mike, I'm revisiting some of my ESP32 work and have seen a future roadblock for one of my goals.
One of the things I have in mind is the ESP32 serving up an editor over WiFi. From there a user can manage and edit scripts, to be either updated on the fly or deployed once ready. In either case it requires being able to parse the JS source. Since the C interface has no parser, this cannot be done on the backed.
Additionally it seems the microvium module includes too many NodeJS specific modules to be bundled. I've tried requiring more specific portions of microvium, like virtual-machine but seems this doesn't do a lot of setup around globalSlots, globalVariables, etc. This is handled by virtual-machine-friendly, which unfortunately imports the core Microvium module.... repeat module import errors...
I've started down the rabbit hole of trying to bootstrap those values, but this seems the wrong approach, especially with my limited TS experience. Though I do believe this can be broken down in a way that doesn't require OS level modules, possibly shifting these imports to the CLI interface while allowing a more specific require call when needed. I may even have missed something, so any input on this would be appreciated.

Hi @morganrallen.

Additionally it seems the microvium module includes too many NodeJS specific modules to be bundled

I'm not sure I understand. If your intention is to host a web-based editor on an ESP32, then what purpose does bundling the compiler do? If the result is a bundle of JS code, then you're back to square one requiring a JS runtime that can parse and run that code (which the Microvium runtime would not be able to do since it only supports a subset of the language). If your plan was to bootstrap the Microvium front-end to run on the Microvium backend, I don't expect this to work since Microvium only supports a subset of the JS spec. It would be awesome to someday have it self-hosting, but that's a long way off since the front-end compiler is a beast.

In either case it requires being able to parse the JS source.

If you need a parser at runtime on an embedded device, and you're using a beefy device like ESP32, I might suggest looking into the Moddable XS engine. It has a built-in parser at runtime and there are examples in the SDK on how to use it on ESP32. Also, this is the smallest engine that supports the full modern ECMAScript spec, which will make it easier to set up a web server. And it has its own HTTP module with examples on how to use it.
If you're looking for something smaller than XS but which has a parser at runtime, mJS and Elk are options but they're quite limited in terms of supported language features.
If I'm misunderstanding your use case, let me know.

Oh, is your intention to run the compiler in the browser client and have the client post the snapshot to the ESP32 server to execute?

Oh, is your intention to run the compiler in the browser client and have the client post the snapshot to the ESP32 server to execute?

Yes, sorry that wasn't clear, I started writing this very late last night, should have just started over fresh this morning.

Ok, that makes sense. That would be cool to see!
Two thoughts come to mind:

Can you shim out the node.js API (e.g. with something equivalent to rollup-plugin-node-builtins).
If it's getting stuck with VirtualMachineFriendly then possibly it's the SynchronousWebSocketServer which uses a few Node modules including worker_threads. This is unused at the moment so we could just comment out that code for the moment and I can revisit it later (it's WIP for adding Microvium debugger), if it doesn't stub well.

Yes, it hangs up the the WS server for sure. My preferred bundler is browserify and it outputs...
$ echo "mcvm = require('microvium');"|./node_modules/.bin/browserify -
Error: Can't walk dependency graph: ENOENT: no such file or directory, lstat './worker_threads'
    required by /home/morgan/devel/lorajs/node_modules/microvium/dist/lib/synchronous-ws-server/index.js

I've commented out that dependency. Does that help?

Yup, that'll get it to build.
$ echo "mcvm = require('microvium');"|./node_modules/.bin/browserify -|wc
88377<PHONE_NUMBER>183

Ok, great. Glad it worked for you!


Remove react references in core

core is a framework agnostic package, currently being used in Svelte and other non react apps. We should not be exporting react code there to cut down on the bundle and reduce confusion.

Closed by #51


Optimize SunSpec read/write with specific keys

Based on testing, reading specific keys took longer than reading the entire model because each "block" of keys has a lot of overhead for the connection. So it's more efficient to read the entire block still.
range start 40123 length 6 took<PHONE_NUMBER>00003 ms
range start 40132 length 1 took 1233.578300000001 ms
getNameplateModel some keys took 1235.3727 ms (the two ranges are in parallel)

getNameplateModel all took<PHONE_NUMBER>000011 ms


Line (drawn using canva.drawPoints()) placed above an interactive viewer disappears partially when a widget is placed above it

Steps to Reproduce

The issue was previously described in https://github.com/flutter/flutter/issues/106187 and was closed as it didn't have a problem on the master branch. The current code includes the addition of the line being placed on top of an interactive viewer and has also been tested on the master branch.

Execute flutter run on the code sample
Tap on the TextField and hover the mouse on the screen

Expected results: Line below the text field should remain the same length and not get cut off on hovering above it.
Actual results: Part of the line below disappears from time to time when clicking the text box and hovering the mouse over the screen.

Code sample

import 'dart:ui';

import 'package:flutter/material.dart';

void main() async {
  runApp(const MaterialApp(
      debugShowCheckedModeBanner: false, home: DistanceProvider()));
}

class DistanceProvider extends StatelessWidget {
  const DistanceProvider({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    // Finds the center of the screen
    final width = MediaQuery.of(context).size.width / 2;
    final height = MediaQuery.of(context).size.height / 2;

    return Scaffold(
      body: InteractiveViewer(
        child: Stack(
          children: [
            // Draws a line using the Custom painter at the center of the screen (width :400 px)
            CustomPaint(
              size: Size.infinite,
              painter: _DrawPath(
                offsetPoints: [
                  Offset(width - 200, height),
                  Offset(width + 200, height)
                ],
              ),
            ),
            // Places a text box to enter the distance between the two points
            Center(
              child: Container(
                width: 50,
                decoration: const BoxDecoration(color: Colors.white),
                child: TextField(
                  onChanged: (String value) {},
                ),
              ),
            ),
          ],
        ),
      ),
    );
  }
}

///Creates a path by drawing a line from one consecutive point to the next
class _DrawPath extends CustomPainter {
  _DrawPath({
    required this.offsetPoints,
  });

  final List<Offset> offsetPoints;

  @override
  void paint(Canvas canvas, Size size) {
    canvas.drawPoints(PointMode.polygon, offsetPoints, Paint());
  }

  @override
  bool shouldRepaint(_DrawPath oldDelegate) => true;
}

Logs

Analyzing disappearing_line_bug...
No issues found! (ran in 3.6s)

flutter doctor -v
[✓] Flutter (Channel stable, 3.0.3, on macOS 12.4 21F79 darwin-x64, locale en-DE)
• Flutter version 3.0.3 at /Users/jshe/Developer/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 676cefaaff (7 days ago), 2022-06-22 11:34:49 -0700
• Engine revision ffe7b86a1e
• Dart version 2.17.5
• DevTools version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/jshe/Library/Android/sdk
• Platform android-31, build-tools 30.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.57.0)
• VS Code at /Users/jshe/Downloads/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (2 available)
• macOS (desktop) • macos  • darwin-x64     • macOS 12.4 21F79 darwin-x64
• Chrome (web)    • chrome • web-javascript • Google Chrome 103.0.5060.53
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

<!--
      Consider also attaching screenshots and/or videos to better
      illustrate the issue.

      You can upload them directly on GitHub.
      Beware that video file size is limited to 10MB.
--

https://user-images.githubusercontent.com/60810797/176413148-d5094180-23ac-46e3-bce2-b50b7c85aa13.mov

>

Hello @SheenaJacob. If you are still facing this issue, please follow up on the original issue you posted. Since this is a duplicate issue, I'm closing this one. You can post your findings on https://github.com/flutter/flutter/issues/106187 and ask for it to be reopened. If you disagree with my decision, feel free to comment. Thank you.

Hello @exaby73 .Thanks for the feedback.  I just wanted to specify that the issue is slightly different from the first one, as it happens under different circumstances. The first one didn't have an interactive viewer involved and was actually fixed on the master branch. The problem that occurs is of course the same.

I can reproduce this on stable and master on Desktop (MacOS)
Video
https://user-images.githubusercontent.com/50555895/176422785-a81d18a9-435a-432e-baff-d4085e564a71.mov

Code sample
import 'dart:ui';

import 'package:flutter/material.dart';

void main() async {
  runApp(
    const MaterialApp(
      debugShowCheckedModeBanner: false,
      home: DistanceProvider(),
    ),
  );
}

class DistanceProvider extends StatelessWidget {
  const DistanceProvider({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    // Finds the center of the screen
    final width = MediaQuery.of(context).size.width / 2;
    final height = MediaQuery.of(context).size.height / 2;

    return Scaffold(
      body: InteractiveViewer(
        child: Stack(
          children: [
            // Draws a line using the Custom painter at the center of the screen (width :400 px)
            CustomPaint(
              size: Size.infinite,
              painter: _DrawPath(
                offsetPoints: [
                  Offset(width - 200, height),
                  Offset(width + 200, height)
                ],
              ),
            ),
            // Places a text box to enter the distance between the two points
            Center(
              child: Container(
                width: 50,
                decoration: const BoxDecoration(color: Colors.white),
                child: TextField(
                  onChanged: (String value) {},
                ),
              ),
            ),
          ],
        ),
      ),
    );
  }
}

///Creates a path by drawing a line from one consecutive point to the next
class _DrawPath extends CustomPainter {
  _DrawPath({
    required this.offsetPoints,
  });

  final List<Offset> offsetPoints;

  @override
  void paint(Canvas canvas, Size size) {
    canvas.drawPoints(PointMode.polygon, offsetPoints, Paint());
  }

  @override
  bool shouldRepaint(_DrawPath oldDelegate) => true;
}

flutter doctor -v (Stable)
[✓] Flutter (Channel stable, 3.0.3, on macOS 12.4 21F79 darwin-arm, locale en-US)
    • Flutter version 3.0.3 at /Users/nabeelparkar/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 676cefaaff (7 days ago), 2022-06-22 11:34:49 -0700
    • Engine revision ffe7b86a1e
    • Dart version 2.17.5
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5921.27

[✓] VS Code (version 1.68.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

flutter doctor -v (Master)
[✓] Flutter (Channel master, 3.1.0-0.0.pre.1422, on macOS 12.4 21F79 darwin-arm, locale en-US)
    • Flutter version 3.1.0-0.0.pre.1422 on channel master at /Users/nabeelparkar/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1d5c189d28 (52 minutes ago), 2022-06-29 02:19:02 -0400
    • Engine revision 8c36371fa7
    • Dart version 2.18.0 (build 2.18.0-234.0.dev)
    • DevTools version 2.14.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5921.27

[✓] VS Code (version 1.68.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

CC @justinmc

This works as expected if I disable display lists.
@flar

It looks like our "empty bounds" rejection was a little too over-aggressive. For drawPoints(), it eliminates the bounds of completely horizontal or vertical sets of points before we get a chance to apply the stroke attributes (because they cover no area - which is fine for stroked paths).

Fixed in https://github.com/flutter/engine/pull/34430

Thanks @flar!


Volumes are not generated in the docker compose file

🔥 Bug Description
I have a project where I bind several volumes per docker container to load configuration files.
But generating the docker compose file does not include these volumes.
🔍 Steps to Reproduce the Bug

Clone https://github.com/Depechie/OpenTelemetryGrafana/tree/aspire/code/otel.AppHost
aspirate generate --output-format compose
Open the docker compose and see that there are no volumes defined

Unfortunately we can't support volumes until Aspire outputs volume information in the manifest
Aspir8 operates solely on the information output in the manifest file that is produced from the AppHost.
You can see whats available by running this in the AppHost directory of the otel project
dotnet run --publisher manifest --output-path manifest.json
Right now, there aren't any volume resources, and without them aspir8 has no way to know that it can create them 😢

Thanks for the clarification!

We've done work in preview 5 to preserve container volumes for container resources specifically.


Smart tabs support

It is great, that we can now set tabs / spaces indentation in configuration. But would be better still, if there is a support for smart tabs, so we can indent with tabs and align with spaces. Are there any plans for supporting smart tabs feature?

Maybe in the future.


[Doc] Add fault tolerance for Pulsar Flink Connector 2.7

This PR adds docs for Pulsar Flink connector 2.7.0 on StreamNative Hub w/ green highlighted parts as below.

Will add them to the README of Pulsar Flink connector 2.7.0 in streamnative/pulsar-flink after this PR gets merged.

Same to https://github.com/streamnative/pulsar-hub/pull/126

Same to https://github.com/streamnative/pulsar-hub/pull/126


Package stats not updating https://www.nuget.org/packages/opencover

The package download stats don't appear to be working for https://www.nuget.org/packages/opencover
Also, is it possible to remove packages (pre-release) that have no downloads (I understand why you may want to keep those that have already had downloads)? My build server and github had a bit of a recursive trigger/build/deploy/tag/trigger... cycle.

Download stats are something we are working on. They will definitely be back, just not in the next few hours :)
Regarding your other question, please reach out to<EMAIL_ADDRESS>


speed up the loading process from the defis

Insert de GEOJSONs from defi_archive.

New JSON Files here: https://github.com/chnuessli/defi_archive/commit/538c267189958a8e48dec14ecc2ce3d408f49ed0
Umap updated to deliver the Json Files.


Using GitLab and Anka Build Cloud

Hi
I think there is a missing image in the end of this section:

You should now see the runner in your GitLab:
gitlab runner attached

With the image url https://ankadocs.veertu.com/images/gitlab-runner-attached.png
Best regards
Jens

Fixing, thanks!


Enable framework extras in backend

Fixes #1233

@mjauvin does this cause any duplication / double handling of existing backend functionality?

@LukeTowers I checked thoroughly and there is no duplication whatsoever.

I just realized there may be a need to also include the extras css as well... will check asap and report back here.

Ok, so the extras styles are already contained in snowboard.extras.css, so no need here.

@bennothommo what was the reason you included snowboard.extras.css in the backend ?

@mjauvin the backend build of Snowboard does use some utilities that need styling (Flash, Stripe Loader, Transition).

I've submitted an alternate way of handling this - #1235. I've seen one plugin manually including the framework.extras (Test plugin), so I'm leaning towards it was only meant to be included when needed and not globally, but up to you guys if we want to hook it into Snowboard or just use @mjauvin's PR.

@jaxwilko any thoughts?

replaced by #1235


Typescript broken in 3.2.0

After upgrading to 3.2.0, no typescript suggestion available. Am I missing something?
Versions

react-native-geolocation: 3.2.0
react-native: 0.72.10
react: 18.2.0

+1

Me too


user request - Study API whitelabel error

gwas-info query re: study API:
I am writing to inform you about an issue we are currently facing while using the Study API at the following URL: https://www.ebi.ac.uk/gwas/rest/api/studies/GCST90086814.
Unfortunately, we have encountered a whitelabel error page with a status code of 500,
Please let me know the estimated timeline for when the API will be responsive and the issue resolved.

no problem detected, resolved itself after a few minutes, probably an intermittent memory issue


Apply a filter on undefined response data

I'm currently writing a custom template based on webpack template, and I ask user the JavaScript compiler he wants.
Based on the answer, some other questions are removed using when
"compiler": {
      "type": "list",
      "message": "Which JavaScript compiler do you want to use?",
      "choices": [
        {
          "name": "Babel (ES2015)",
          "value": "babel",
          "short": "babel"
        },
        {
          "name": "TypeScript (Awesome Typescript Loader)",
          "value": "typescript",
          "short": "typescript"
        },
        {
          "name": "No compiler (Vanilla JS)",
          "value": "none",
          "short": "none"
        }
      ]
    },
    "eslint": {
      "when": "compiler == 'babel'",
      "type": "confirm",
      "message": "Use ESLint to lint your code?"
    },

The eslint question is displayed only when compiler babel is choosen, all is ok here.
But then, if user choose something else than babel as compiler, an error message is displayed about filters.
Error when evaluating filter condition: eslint

It seems to be caused by the filters handling because eslint is undefined in data.
  "filters": {
    ".eslintrc.js": "eslint",
    ".eslintignore": "eslint",
    "config/test.env.js": "unit || e2e",
    "test/unit/**/*": "unit",
    "build/webpack.test.conf.js": "unit",
    "test/e2e/**/*": "e2e",
    "src/router/**/*": "router"
  }

@Toilal Is...solved?

I don't think it's been solved, but I have now switched to @vue/cli 3.

good !


[BUG] MAUI refusing to build for iOS with package

Library name and version
Azure.Identity 1.6.0
Describe the bug
I am currently having an issue with building a MAUI project with the Azure.Identity 1.6.0 library installed. When I try to build it, I get a 'clang++ exited with code 1' error in the console and refuses to go any further. It works building for Windows.
Expected behavior
It should be able to build for the iOS platform
Actual behavior
I refuses to build for the iOS platform with the error 'clang++ exited with code 1'
Reproduction Steps

Create a new default MAUI project
Import the Azure.Identity 1.6.0 library
Make sure you are paired to a Mac device
Switch the Build Device to an iOS simulator or Remote Device
Run the project on simulator or remote device
The error will happen in the build process

Attached is a project I quickly got together: MauiAzureTest.zip
Environment
Using:
Visual Studio 2022 Preview 3.0 (Version 17.3.0 Preview 3.0)
MAUI version 6.0.408
.NET 6

Hi @NickD-Callaway.   Thank you for reaching out and we regret that you're experiencing difficulties.   I was able to reproduce the behavior that you're seeing with the project that you attached using dotnet build directly on MacOS.   However, I trigger the same error with and without the package reference to Azure.Identity.
When I create a new default Maui project, add a reference to Azure.Identity and build, I do not receive errors.   I'm able to run the application natively on the Mac, on an iOS simulator, and an Android simulator.
That said, I cannot seem to isolate the issue to something specific in your project.  I've run through a diff on every file and don't see anything outside of GUIDs and some formatting differences.   I even copied my project file over, removed all the .vs and *.user customizations, and still run into the issue.
I'm reasonably sure that your build error is unrelated to the Azure package reference.   I believe it has something to do with the message ld: framework not found System, but I can't reasonably speculate about a root cause.  I believe your best path forward would be to report this to the Maui team, as they will have the expertise to investigate further and advise.
In case it helps, I'm including the full output for dotnet build when run against your project:
Microsoft (R) Build Engine version 17.2.0+41abc5629 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  All projects are up-to-date for restore.
  Detected signing identity:

    Bundle Id: com.companyname.mauiazuretest
    App Id: com.companyname.mauiazuretest
  Detected signing identity:

    Bundle Id: com.companyname.mauiazuretest
    App Id: com.companyname.mauiazuretest
  MauiAzureTest -> /Users/jesse/src/scratch/MauiAzureTest/bin/Debug/net6.0-maccatalyst/maccatalyst-x64/MauiAzureTest.dll
  MauiAzureTest -> /Users/jesse/src/scratch/MauiAzureTest/bin/Debug/net6.0-ios/iossimulator-x64/MauiAzureTest.dll
  MauiAzureTest -> /Users/jesse/src/scratch/MauiAzureTest/bin/Debug/net6.0-android/MauiAzureTest.dll
  Optimizing assemblies for size, which may change the behavior of the app. Be sure to test after publishing. See: https://aka.ms/dotnet-illink
  Optimizing assemblies for size, which may change the behavior of the app. Be sure to test after publishing. See: https://aka.ms/dotnet-illink
  Tool xcrun execution finished (exit code = 1).

  ld: framework not found System
  clang: error: linker command failed with exit code 1 (use -v to see invocation)

/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.4.328/targets/Xamarin.Shared.Sdk.targets(1219,3): error : clang++ exited with code 1 [/Users/jesse/src/scratch/MauiAzureTest/MauiAzureTest.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.4.328/targets/Xamarin.Shared.Sdk.targets(1219,3): error :          [/Users/jesse/src/scratch/MauiAzureTest/MauiAzureTest.csproj]

Build FAILED.

Thanks for you response @jsquire ! My next course of action is to get ahold of the MAUI team.
I spent some time just now trying to use my Mac to do the same thing with no success. Same issue. I created the base MAUI project using VS for Mac 17.3 Preview, imported the Azure.Identity library, and it still gives me the clang++ error. I will bring this up with them and see what they have to say about the issue.
Thanks!!

Sorry that we couldn't get you fully unblocked; please let us know if we can be of further assistance.    I'm going to mark this as addressed, but please feel free to unresolve if you'd like to continue the discussion.


I/O APIC is disable and crash the machine with 2 or more CPUs

Hi guys,
I didn't find where openSUSE build Vagrant images, just this repository, and it looks old, anyway we need to add I/O APIC during machine creation, or it'll crash on setips with 2 or more cpu cores.
vb.customize ["modifyvm", :id, "--ioapic", "on"]

Thanks for the heads up! I'll look into this later this week.

Hi @hector-vido, sorry for the long radio silence from my side. I was initially not able to reproduce any crashes and then it fell into my backlog…
Anyway, I came back to this a few days ago when debugging a terrible slowness in nested virtualization envirnoments. I hope that I have fixed the issue now and will submit fixes to the existing images. They should hopefully Vagrantcloud soon.

Nice! Good to know :D

This should be fixed on Leap now and on Tumbleweed hopefully in a few days at most.


[stable/keycloak] Use KUBE_PING for discovery

Signed-off-by: Thomas Recloux<EMAIL_ADDRESS>What this PR does / why we need it:
This PR changes the jgroups autodiscovery used by Keycloak in multi node mode (highavailability) to use Kubernetes discovery.
The Chart was using DNS_PING discovery which was based on the headless service to list endpoints.
This PR switches to KUBE_PING, using a the jgroups-kubernetes discovery already bundled in Keycloak image. Discovery is more kubernetes native and is not linked to node readiness.
Special notes for your reviewer:
Checklist

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

Ping @thomasdarimont

@thomasdarimont I have two others contributions:

Add options to configure probes (URLs, periods) in order to use your healthcheck module
Allow usage of templates usingtpl function to configure database host and database secret.

Do you want me to push two more commits here or to submit to other pull requests ?
Thank you, Thomas

I prepared two additional contributions:

Add options to configure probes (path, periods)
Add support for templates using tpl function to configure database host and database secret.

Do you prefer two more pull requests or to add these commits here ?

Thanks for the PR. Let's keep things separate. Please create new PRs for the other features.
I'd say way should keep DNS_PING as default and offer KUBE_PING as additional option.

I'd say way should keep DNS_PING as default and offer KUBE_PING as additional option.

OK. I'll submit a change to keep both.

The Keycloak chart here is being deprecated (#13316) and moved to a new home:
https://github.com/codecentric/helm-charts
I'm closing this PR. Feel free to direct future contributions to the new repo. Thanks.


Constraint specification for SMARTY XML ForceField

At some point, we'll need to expand ForceField to allow us to specify which bonds or angles should be constrained.
One way to do this is to extend the ffxml format to allow this to be specified via SMIRKS. For example:
<Constraints>
  <!-- bonds involving hydrogen -->
  <Constraint smirks="[#1:1]-[*:2]"/> <!-- add constraint between atoms 1 and 2 using equilibrium bond distance -->
  <!-- angles involving hydrogen -->
  <Constraint smirks="[#1:1]-[*:2]-[#1:3]"/> <!-- add constraint between atoms 1 and 3 using auto-calculated distance from equilibrium bond and angles -->
</Constraints>

This seems reasonable to me. I can discuss with Chris on Monday if you want. I'll tag him here but he's probably out for the weekend. ( @cbayly13 ?)

@jchodera - this is where we stand on constraints.

OK! This is super easy to implement if we get the thumbs-up.
We might want to also draft an example for rigid waters. Would that be:
<Constraints>
  <Constraint smirks="[#1X1:1]-[#6X2:2]-[#1X1]"/> <!-- water O-H -->
  <Constraint smirks="[#1X1:1]-[#6X2]-[#1X1:2]"/> <!-- water H...H -->
</Constraints>

I guess one question is whether we are OK with the number of atoms tagged in the smirks string determine whether to use the equilibrium bond length or whether to interpret the 1-2-3 atom tuple as an angle from which to derive an equilibrium constraint length.

I'll ask Chris to look at this. This was sitting there from August, so the comment about asking him in the morning is an old one.

There are different use cases for constraints, so we either need a superbly designed mother-of-all-API-points or we can go with a fit-for-purpose design for the more immediate needs. IMHO the immediate need is for torsion driving and, conventionally, interaction energies. In these cases we assume the user submits the structure having the desired value of the degree of freedom, so I think it fits in with John's suggestion above: tagged atoms specify the constrained atoms, and they are constrained to their starting value. It would be nice if we could inherit improper torsions, meaning if the tagged 1-2-3-4 atoms are linear, it is a regular torsion, but if it is a trefoil as in 1-2(-3)-4, the whole improper is constrained (all six paths).

I think we might be thinking of different application domains here. This is
just for "which distance constraints are imposed during simulation via
SHAKE or SETTLE?"
OpenMM doesn't currently allow for torsion or other kinda of constraints.
If we do torsion drives, it will be using an external code to impose
geometries.
We don't need to come up with the final set of all possible constraints
either. We just need a syntax that can have stuff added to it later, but
where we don't remove or change things.

@jchodera - I just pinged Chris again to clarify that we're addressing constraints for MD simulations, i.e. as normally applied to bonds involving hydrogen or to waters, etc.
In terms of your proposals, here are my thoughts:

We need an easy mechanism to constrain bond lengths
We need an easy mechanism to constrain bond angles
Those two seem like they are separate and can cover all (?) of our typical use cases (?)

So, I like the first part of this example:
<Constraints>
  <!-- bonds involving hydrogen -->
  <Constraint smirks="[#1:1]-[*:2]"/> <!-- add constraint between atoms 1 and 2 using equilibrium bond distance -->
  <!-- angles involving hydrogen -->
  <Constraint smirks="[#1:1]-[*:2]-[#1:3]"/> <!-- add constraint between atoms 1 and 3 using auto-calculated distance from equilibrium bond and angles -->
</Constraints>

At least, I think the "bonds involving hydrogen" case is exactly what we would want a lot. I'm a little nervous about the "angles involving hydrogen" case as it sounds like, in your comment, you would want to interpret this to constrain the 1-3 distance AND the angle. Is that doing too much? (i.e. what if I wanted to constrain all bond angles in a molecule, as is sometimes done?)
For example, for water, don't we want to constrain the H-O-H angle and the O-H distance separately, at least in TIP3P?
To visit your water example:
<Constraints>
  <!-- constrain water O-H bond to equilibrium bond length -->
  <Constraint smirks="[#1X1:1]-[#6X2:2]-[#1X1]"/>
  <!-- constrain water H...H, calculating equilibrium length from H-O-H equilibrium angle and H-O equilibrium bond lengths -->
  <Constraint smirks="[#1X1:1]-[#6X2:2]-[#1X1:3]"/>
</Constraints>

That looks right to me, except that I'd be using these SMIRKS strings:

[#1:1]-[#8X2H2:2]-[#1] (oxygen with two connected hydrogens, not carbon with two connections, is the central atom, and the "X1" decorator on the protons is unnecessary)
[#1:1]-[#8X2H2:2]-[#1X1:3] (same changes as above)
I'd also constrain the bond lengths only based on the first entry and use the second one, which denotes an angle, only to fix the equilibrium angle. If you have the angle case ALSO constrain the bond lengths, then there's no mechanism to apply a constraint only to an angle without also constraining bond lengths, right?

I'm a little nervous about the "angles involving hydrogen" case as it sounds like, in your comment, you would want to interpret this to constrain the 1-3 distance AND the angle. Is that doing too much? (i.e. what if I wanted to constrain all bond angles in a molecule, as is sometimes done, but constrain no bond lengths?)

We certainly wouldn't want to use this generally, but I was originally proposing this as a way to replace the functionality I stripped out where OpenMM allowed the user to specify None (no constraints), HBonds (constrain only bonds to hydrogen), and HAngles (constrain all bonds and any angles involving hydrogen.

The updated rigid water example is then:
<Constraints>
  <!-- constrain water O-H bond to equilibrium bond length -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1]"/>
  <!-- constrain water H...H, calculating equilibrium length from H-O-H equilibrium angle and H-O equilibrium bond lengths -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1:3]"/>
</Constraints>

I'd also constrain the bond lengths only based on the first entry and use the second one, which denotes an angle, only to fix the equilibrium angle. If you have the angle case ALSO constrain the bond lengths, then there's no mechanism to apply a constraint only to an angle without also constraining bond lengths, right?

Oh, I hadn't even thought about that. We can't really constrain an angle specifically in OpenMM without constraining bonds, since only bond constraints are supported, so I'd actually argue we would want [#1:1]-[#8X2H2:2]-[#1:3] to constrain three bonds: (1,2), (2,3), and (1,3). Otherwise, we would constrain a distance (1,3) but it wouldn't keep the angle fixed.

We certainly wouldn't want to use this generally, but I was originally proposing this as a way to replace the functionality I stripped out where OpenMM allowed the user to specify None (no constraints), HBonds (constrain only bonds to hydrogen), and HAngles (constrain all bonds and any angles involving hydrogen.

It would certainly work for that, though is it preferable to do things this way rather than the slightly more general way of allowing a user to constrain bonds, angles, or both in combination? The latter actually seems easier to understand to me as it doesn't require wrapping my head around the idea that defining an angle SMIRKS also results in bond length constraints.

Oh, I hadn't even thought about that. We can't really constrain an angle specifically in OpenMM without constraining bonds, since only bond constraints are supported, so I'd actually argue we would want [#1:1]-[#8X2H2:2]-[#1:3] to constrain three bonds: (1,2), (2,3), and (1,3). Otherwise, we would constrain a distance (1,3) but it wouldn't keep the angle fixed.

Ah, OK, @jchodera - if there is no mechanism to constrain an angle then I agree with you that the best way to do this is as you're proposing, that an angle constraint results in constraining all both bonds involved in the angle as well as the distance between the terminal atoms.
And I agree with your syntax.

is it preferable to do things this way rather than the slightly more general way of allowing a user to constrain bonds, angles, or both in combination? The latter actually seems easier to understand to me as it doesn't require wrapping my head around the idea that defining an angle SMIRKS also results in bond length constraints.

I'm trying to think ahead as to what we might want to support in this format. There was initially some discussion about wanting to potentially keep some moieties rigid, or potentially to have groups of atoms (or pseudoatoms) that act like rigid units. This would allow us to have a way of having targeted groups of atoms be rigid in interesting ways, while still making it easy to specify "constraint all bonds to hydrogen" or "constrain all bonds" with a single <Constraint/> tag.

Just catching up here, I agree with most of the above discussion about SHAKE and TIP/FastWater. SHAKE/SETTLE is about bond constraints in general, and we certainly need them quite apart from TIP/FastWater. I wonder if FastWater deserves a constraint special case. However, for both SHAKE and FastWater I am quite sure we need to abandon the assumption that the input structures will have the correct values; an obvious case is structured water from the pdb file. For SHAKE and TIP/FastWater we need to specify a constraint value I think.
Also, just FYI, TIP water has an explicit (though artificial) bond from H1 to H2, and thus in SMARTS would be a divalent hydrogen: [#1X2]

What is TIP/FastWater?
SETTLE is the analytical solution of SHAKE for three-site waters, so is specific to three-site molecules.

We do have an example for water that includes this artificial bond from H1 to H2:
<Constraints>
  <!-- constrain water O-H bond to equilibrium bond length -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1]"/>
  <!-- constrain water H...H, calculating equilibrium length from H-O-H equilibrium angle and H-O equilibrium bond lengths -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1:3]"/>
</Constraints>

Any further thoughts, or is this final format OK?

I'm good with this, @jchodera . I don't think Chris has any other insights.

I just got finished reading through this, I'm a little confused about the implication of the TIP water with the explicit H-H bond:

Also, just FYI, TIP water has an explicit (though artificial) bond from H1 to H2, and thus in SMARTS would be a divalent hydrogen: [#1X2]

If we had Tip3p water then the H-H bond would exist and [#1X2] would match. Assuming you just start from a water molecule then that H-H bond isn't explicitly there and the [#1X2] would not match, correct? My understanding is the angle pattern ([#1:1]-[#8X2H2:2]-[#1:3]) would then be used to indicate all three distances (not really bond lengths) would be kept constant.
Otherwise this format makes sense to me.

I don't believe OpenEye tools would be able to correctly process an HOH molecule where the hydrogens were bonded to each other---that would violate its rules of chemistry, from what I understand.
I believe we're thinking of the case where the system contains a bunch of normal H-O-H molecules and we want to apply parameters typically considered to be "TIP3P" parameters. In that case, we would want to impose both H-O and intramolecular H...H constraints, which is why we need a syntax capable of specifying that.

I agree with @jchodera here. I don't think Chris was thinking of how we're actually processing molecules/assigning parameters here. He was just thinking that if you had a hypothetical water that was set up like TIP3P, you could have a virtual bond between the two hydrogens and then [#1X2] would be a perfectly sensible SMIRKS. But it doesn't make any sense here.

@jchodera - we think this is final.

I just spoke with @cbayly13, who pointed out that it would be desirable to be able to express constraint distances as well in this format:
<Constraints distance_unit="angstroms" angle_unit="degrees">
  <!-- constrain all bonds to hydrogen to their equilibrium bond length -->
  <Constraint smirks="[#1:1]-[*:2]" />
  <!-- constrain water O-H bond to equilibrium bond length (overrides earlier constraint) -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1]" distance="0.9572"/>
  <!-- constrain water H...H, calculating equilibrium length from H-O-H equilibrium angle and H-O equilibrium bond lengths -->
  <Constraint smirks="[#1:1]-[#8X2H2]-[#1:2]" distance="1.8532"/>
  <!-- alternatively, specify the angle, but use equilibrium bond lengths (do we need this?) -->
  <Constraint smirks="[#1:1]-[#8X2H2:2]-[#1:3]" angle="104.52"/>
</Constraints>

If I read this correctly, @jchodera , the difference is that you're just specifying distance and angle, potentially? I agree this would be a plus since one might want to be able to start with structures that don't necessarily have correct geometries.

Closed, at least temporarily, by #239 , which implements much but not all of this.


share app_settings with pre-live slot

Add a PR title
Describe what changed in this PR at a high level.
Issue
Add a link to the issue here.  Consider using
closing keywords
if the this PR isn't for a story (stories will be closed through different means).
Checklist

[ ] I have added tests to cover my changes
[ ] I have added logging where useful (with appropriate log level)
[ ] I have added JavaDocs where required
[ ] I have updated the documentation accordingly

Note: You may remove items that are not applicable

I'm going to merge main into this branch because Jeff and I merged a change that makes deploys better.


Add Spanish country name and phone code

This version add two columns for country name in Spanish and phone code.
So, indexes of fields are updated.

Hi @rubensaid,
It looks like you're after a very specific feature of adding support for the Spanish language. While I understand it'd be useful for Spanish-speaking people, this minimalistic library focuses mainly on the flag images themselves, not on language support.
I suggest you either:

apply the changes to your fork and use it;
use this library as is and create a map to translate English to Spanish in your application.

I would prefer the second option because you'd still be able to get new versions of the library (as people make new contributions/bug fixes) while keeping your translation code decoupled from the flag logic. Makes sense?
I understand you took the time to try and improve the library and I'd like to thank you for that. I'd suggest next time you open an issue first to present the problem you have so others can discuss it and see if it makes sense.
I am closing this PR, but thank you again!

That being said, I think the phone code addition is a very nice feature. If you feel like opening a separate PR just for the phone code, it'd be awesome.


Laravel 8 compatibility

Hey there,
Just wanted to know if there will be a Laravel 8 support anytime soon.
Thanks in advance.

It requires kalnoy/nestedset depency to be released for L8 too.
I hope soon.

It requires kalnoy/nestedset depency to be released for L8 too.
I hope soon.

kalnoy/nestedset  already support L8

Adding this to update the issue and subscribe myself 👍🏻

rinvex/laravel-support has an open PR to support L8 but it has a failing check
felixkiss/uniquewith-validator has two (identical) open PRs (#116 and #118) to support L8

any updates ?

@tallesairan unfortunately, neither of the packages have had any significant updates/releases since my last message. PR #116 on felixkiss/uniquewith-validator was approved, but it wasn't merged for some reason. Someone commented 3 days ago asking if it could be merged and a new release made, but nothing has happened yet.

I also tried to contribute to the progress but I still don't have the necessary skills to create a PR :(

@tallesairan I'd be happy to help! Have you made the code changes and you just need to create a PR?

Yes please update soon. Laravel 9 is already in the pipeline.

Yes please update soon. Laravel 9 is already in the pipeline.

Believe we are stuck until this PR dependancy is pushed.

any updates?

@Omranic - What do you suggest happens with updates if we have no response from your dependency?

push ✨

this is nightmare.

this is nightmare.

I've ended up dropping the package and using https://github.com/lazychaser/laravel-nestedset directly. Take a look at this package for ideas on setting it up for categories. Took me about a day to migrate it. Best of luck!

this is nightmare.

I've ended up dropping the package and using https://github.com/lazychaser/laravel-nestedset directly. Take a look at this package for ideas on setting it up for categories. Took me about a day to migrate it. Best of luck!

YOU ARE THE HERO SIR :) thanks a mil.

First off, what i did, i wrote an kind email directly to rinvex without a response.
In case it could help anyone too. Here is my solution which has a few downsides and is not perfect at all.

Modify your composer.json

"autoload": {
        "psr-4": {
....
            "Rinvex\\": "support/rinvex"
        },
    },

Create a directory /support/rinvex or anything you would like
Move the src Code from rinvex packages into their corresponding directory ( /support/rinvex/Categories|Subscriptions|Support)
Decide if you want to keep rinvex model validation (I removed it). You might have to do some more work here too to get it working (e.g. you'll need another third party dependency)
Integrate every dependency that any rinvex package use in your composer.json (like spatie/laravel-sluggable, kalnoy/nestedset, ...)
Run your tests, if you don't have any, write them.

My win for this solution, i don't have to modify my existing source code and can leave it, as it is. For instance, i'm mostly subclassing package models like seen below
<?php

namespace App\Shared\Models;

class Category extends \Rinvex\Categories\Models\Category
{
}

I don't like this approach but when rinvex comes back i can easily switch back and re-run my tests.
Good luck everyone in surviving this nightmare
PS: same as : https://github.com/rinvex/laravel-subscriptions/issues/117

I also take care this issue.

Hello, thank you for your patience, this is now done! Check latest release!!
This package now supports Laravel v8, PHP v8, Composer v2, enjoy 🥳
CC @nguyendatdh93 @schranzer235 @namsir @enkota @abmohajeri @dhi2 @squatto @tallesairan @sashsvamir @Wikiki @afshiinasghari


[Event Request] table 1381 "Customer Templ." - OnCopyTemplateOnBeforeModifyTemplate

Could you please add the following event ?
local procedure CopyTemplate(SourceCustomerTempl: Record "Customer Templ.")
var
    SavedCustomerTempl: Record "Customer Templ.";
begin
    SavedCustomerTempl := Rec;
    TransferFields(SourceCustomerTempl, false);
    Code := SavedCustomerTempl.Code;
    Description := SavedCustomerTempl.Description;
    //+EVENT
   OnCopyTemplateOnBeforeModifyTemplate(SourceCustomerTempl, SavedCustomerTempl, Rec);
    //+EVENT
    Modify();
end;

[IntegrationEvent(false, false)]
local procedure OnCopyTemplateOnBeforeModifyTemplate(SourceCustomerTempl: Record "Customer Templ."; SavedCustomerTempl: Record "Customer Templ."; var CustomerTempl: Record "Customer Templ.")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52552.


NumberField problem with css

Hello,
I added NumberField to my form and it looks like this:

Arrows are outside and the field looks square

I guess your forgot to import antd css file

i use create-react-app and i used official doc to import css. TextArea and textfield looks good. Just have a problem with number field.

 It was my fault.


feat/library: creating Ansible's official lib dir for roles

According with Ansible documentations, is an best practice to create custom libraries inside librarydirectory in it's directories structures, I.E ansible root or role dirs.
Following this way, we can use this project as an official directory importing automatically these modules to the role dir.
For more information, please read the README section updated here
Changes:

creating symlink from spotinst/ (modules dir) to library, official Ansible anternative for modules lookup.

Hey guys,
Thanks for contributing.
We're reviewing the PR and will approve it soon.

Thanks @MV32 and @nadavnaor


Update CI python version from 3.7 to 3.8, README fix

[] I have added an entry to docs/changelog.md
I didn't add a changelog entry since this was an internal testing issue and not affecting pipx itself.  (But I can if it's needed.)
Summary of changes
I bumped the python version to 3.8 of all tests that only use one python version (doc, lint, macos tests, windows tests), since that's the current stable python version.
I also fixed the badges on README.md so their height matches each other, and gave an alt tag to the Test badge.
Test plan

Tested by running
# command(s) to exercise these changes

Thanks for the quick approval, @gaborbernat 🙂


Could not load dynamic library 'libcudnn.so.7'

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
TensorFlow installed from (source or binary):
TensorFlow version: 2.3.1
Python version: Python 3.8.5
Installed using virtualenv? pip? conda?: pip
CUDA/cuDNN version: CUDA 11.1/cuDNN v8
GPU model and memory: RTX 3080

ISSUE similar to #20271 and #36426
Describe the problem
So I was setting up CUDA and cuDNN for my RTX 3080 on ubuntu 20.04. I followed the TF guide and installed CUDA 10.1 and cuDNN v7. But then I was running into several issues. From a similar issue #43718, I was suggested to use CUDA 11.1 and cuDNN v8.
But whenever I run tf.config.list_physical_devices('GPU') I get the following error:
2020-10-25 17:36:10.844295: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2020-10-25 17:36:10.879258: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-25 17:36:10.879821: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:2b:00.0 name: GeForce RTX 3080 computeCapability: 8.6
coreClock: 1.71GHz coreCount: 68 deviceMemorySize: 9.76GiB deviceMemoryBandwidth: 707.88GiB/s
2020-10-25 17:36:10.879836: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-10-25 17:36:10.881041: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2020-10-25 17:36:10.881627: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-10-25 17:36:10.881750: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-10-25 17:36:10.882821: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2020-10-25 17:36:10.883332: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2020-10-25 17:36:10.883401: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'libcudnn.so.7'; dlerror: libcudnn.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/cuda-11.1/lib64:/usr/local/cuda-11.1/lib64:/opt/ros/noetic/lib
2020-10-25 17:36:10.883408: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1753] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
[]

Here is my ~/.zshrc:
# ROS
source /opt/ros/noetic/setup.zsh

# CUDA
export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
# export LD_LIBRARY_PATH=/usr/lib/cuda/lib64:$LD_LIBRARY_PATH
# export LD_LIBRARY_PATH=/usr/lib/cuda/include:$LD_LIBRARY_PATH

I'm pretty certain that your Tensorflow is built against CUDA 10.1.

2020-10-25 17:36:10.879836: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-10-25 17:36:10.881041: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10

If it was built against CUDA 11.1 you'd be seeing 11/11.1 libs. I would suggest purging CUDA and CUDNN and starting with a clean environment.
What is weird is that it successfully loaded CUDA 10.1 libs, did you source your .zhrc after making those changes or restarted/ opened a new session?

@BorhenJlidi I tried following the official documentation to purge CUDA 10.1. I'm not sure anymore I'm new to ubuntu. Should I just reinstall ubuntu and start over again?

@Harsh188 reinstalling Ubuntu won't do you any good in this case, nothing is wrong with your OS.
For me to be able to help you, please write down a precise list of what packages you installed in order and what commands you executed. If you don't remember , salvage what you can from .bash_history . I've got to know the order of installation, package format, build args...

**powerlevel**
    1  subl
    2  ^[[200~yay -S --noconfirm zsh-theme-powerlevel10k-git~
    3  yay -S --noconfirm zsh-theme-powerlevel10k-git
    4  git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ~/powerlevel10k
    5  echo 'source ~/powerlevel10k/powerlevel10k.zsh-theme' >>! ~/.zshrc
    6  p10k configure
    7  sudo reboot
    8  python
    9  python3
   10  subl ~/zshrc
   11  subl ~/.zshrc
   12  python

**Nvidia-Driver**
   20  git clone https://github.com/zsh-users/zsh-syntax-highlighting.git "$HOME/.zsh-syntax-highlighting" --depth 1
   21  echo "source $HOME/.zsh-syntax-highlighting/zsh-syntax-highlighting.zsh" >> "$HOME/.zshrc"
   22  ubuntu-drivers devices
   23  cd
   24  ubuntu-drivers devices
   25  ubuntu-drivers
   26  ubuntu-drivers devices
   27  sudo apt update
   28  git status
   29  ubuntu-drivers devices
   30  sudo add-apt-repository ppa:oem-solutions-group/nvidia-driver-staging
   31  sudo apt update
   32  sudo nano /etc/apt/sources.list.d/graphics-drivers*.list
   33  apt search nvidia-driver*
   34  apt search nvidia-driver
   35  sudo nano /etc/apt/sources.list.d/graphics-drivers.list
   36  sudo apt install nvidia-driver-455 nvidia-settings
   37  apt search nvidia-driver
   38  ubuntu-drivers devices
   39  sudo reboot

**Docker**
   52  sudo apt-get update
   53  sudo apt-get install \\n    apt-transport-https \\n    ca-certificates \\n    curl \\n    gnupg-agent \\n    software-properties-common
   54  curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
   55  sudo apt-key fingerprint 0EBFCD88
   56  sudo add-apt-repository \\n   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \\n   $(lsb_release -cs) \\n   stable"
   57  sudo apt-get update
   58  sudo apt-get install docker-ce docker-ce-cli containerd.io
   59  apt-cache madison docker-ce
   60  sudo apt-get install docker-ce=<5:19.03.13~3-0~ubuntu-focal> docker-ce-cli=<5:19.03.13~3-0~ubuntu-focal> containerd.io\n
   61  sudo apt-get install docker-ce=<VERSION_STRING> docker-ce-cli=<VERSION_STRING> containerd.io
   62  sudo docker run hello-world
   63  clear

**cuDNN v8**
   77  cd
   78  tar -xvzf cudnn-10.1-linux-x64-v<IP_ADDRESS>.tgz
   80  cd Downloads
   81  tar -xvzf cudnn-10.1-linux-x64-v<IP_ADDRESS>.tgz
   82  sudo cp cuda/include/cudnn.h /usr/lib/cuda/include/
   83  sudo cp cuda/lib64/libcudnn* /usr/lib/cuda/lib64/
   84  ^[[200~sudo chmod a+r /usr/lib/cuda/include/cudnn.h /usr/lib/cuda/lib64/libcudnn*
   85  sudo chmod a+r /usr/lib/cuda/include/cudnn.h /usr/lib/cuda/lib64/libcudnn*\n
   86  echo 'export LD_LIBRARY_PATH=/usr/lib/cuda/lib64:$LD_LIBRARY_PATH' >> ~/.zshrc
   87  echo 'export LD_LIBRARY_PATH=/usr/lib/cuda/include:$LD_LIBRARY_PATH' >> ~/.zshrc
   88  source ~/.zshrc

**Checking things?**
   94  lspci -v
   96  nvidia-smi -a
   97  nvcc --version
   98  sudo apt update
   99  sudo apt install nvidia-cuda-toolkit
  100  nvcc --version
  101  whereis cuda
  102  tar -xvzf cudnn-10.1-linux-x64-v<IP_ADDRESS>.tgz\n
  103  source env/bin/activate
  104  python
  105  pip list
  106  sudo docker run hello-world
  107  clear
  108  curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | sudo apt-key add - \necho "deb http://repository.spotify.com stable non-free" | sudo tee /etc/apt/sources.list.d/spotify.list
  109  sudo apt-get update && sudo apt-get install spotify-client
  110  cd
  111  export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/extras/CUPTI/lib64
  112  subl ~/.zshrc

**cuDNN v7**
  116  cd
  117  cd Downloads
  118  tar -xvzf cudnn-10.1-linux-x64-v<IP_ADDRESS>.tgz
  120  sudo cp cuda/include/cudnn.h /usr/lib/cuda/include/
  122  sudo cp cuda/lib64/libcudnn* /usr/lib/cuda/lib64/
  123  sudo chmod a+r /usr/lib/cuda/include/cudnn.h /usr/lib/cuda/lib64/libcudnn*
  124  git status
  125  nvcc -V
  126  nvidia-smi
  141  subl ~/.zshrc

**Installing ROS/Removing CUDA**
  147  cd
  148  sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'
  149  sudo apt-key adv --keyserver 'hkp://keyserver.ubuntu.com:80' --recv-key C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654
  150  sudo apt update
  151  sudo apt install ros-noetic-desktop-full
  152  source /opt/ros/noetic/setup.bash\n
  153  echo "source /opt/ros/noetic/setup.zsh" >> ~/.zshrc\nsource ~/.zshrc
  154  nvcc --version
  155  lspci | grep -i nvidia
  156  uname -m && cat /etc/*release
  157  gcc --version
  158  uname -r
  159  sudo apt-get install linux-headers-$(uname -r)
  160  sudo /usr/local/cuda-X.Y/bin/uninstall_cuda_X.Y.pl
  161  whereis cuda
  162  whereis cuda-X.Y
  163  dpkg -l | grep -i nvidia
  164  sudo /usr/local/cuda-X.Y/bin/uninstall_cuda_X.Y.pl
  165  sudo /usr/lib/cuda-X.Y/bin/uninstall_cuda_X.Y.pl
  166  sudo apt-get remove --auto-remove nvidia-cuda-toolkit
  167  sudo apt-get purge --auto-remove nvidia-cuda-toolkit
  168  sudo /usr/bin/nvidia-uninstall\n
  169  whereis cuda
  171  nvcc -V
  172  nvidia-smi
  173  sudo dpkg -i cuda-repo-<distro>_<version>_<architecture>.deb
  174  wget https://developer.download.nvidia.com/compute/cuda/11.1.0/local_installers/cuda_11.1.0_455.23.05_linux.run
  175  sudo sh cuda_11.1.0_455.23.05_linux.run
  176  which cuda
  177  whereis cuda
  178  sudo sh cuda_11.1.0_455.23.05_linux.run
  203  rl
  204  roscore
  205  cd
  206  sudo apt-get install ros-$(rosversion -d)-turtlesim
  207  rosrun turtlesim turtlesim_node

**Testing ROS**
  216  cd
  217  printevn | grep ROS
  218  rosversion -d
  219  printenv | grep ROS
  220  rosversion -h
  221  source /opt/ros/noetic/setup.bash
  222  mkdir -p ~/catkin_ws/src
  223  cd ~/catkin_ws
  224  catkin_make
  225  source devel/setup.bash
  226  source /devel/setup.bash
  227  source devel/setup.bash
  228  echo $ROS_PACKAGE_PATH /home/harsh/catkin_ws/src:/opt/ros/noetic/share
  229  cd
  230  sudo apt-get install ros-neotic-ros-tutorials
  231  sudo apt-get install ros-noetic-ros-tutorials
  232  rospack find roscpp
  233  roscd roscpp
  234  pwd
  235  echo $ROS_PACKAGE_PATH
  236  roscd roscpp/cmake/
  237  roscd log
  238  rosls roscpp_tutorials/
  239  roscd roscpp_tutorials/
  240  roscd turtle
  241  rosls
  242  roscd turtlesim/
  243  rosls

**Downloading CUDA 11**
  244  cd
  246  which CUDA
  247  whereis cuda
  249  lspci | grep -i nvidia~
  250  nvcc -V
  251  sudo apt-get install linux-headers-$(uname -r)
  252  gcc --version
  253  uname -r
  254  sudo apt-get remove --auto-remove nvidia-cuda-toolkit~
  255  sudo apt-get purge nvidia*\nsudo apt-get autoremove\nsudo apt-get autoclean\nsudo rm -rf /usr/local/cuda*
  256  get https://developer.download.nvidia.com/compute/cuda/11.1.0/local_installers/cuda_11.1.0_455.23.05_linux.run
  257  wget https://developer.download.nvidia.com/compute/cuda/11.1.0/local_installers/cuda_11.1.0_455.23.05_linux.run
  258  sudo sh cuda_11.1.0_455.23.05_linux.run
  259  cat /usr/local/cuda/version.txt
  260  sudo lshw -numeric -C display
  261  lspci | grep -i nvidia
  262  md5sum
  263  wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin
  264  sudo mv cuda-ubuntu2004.pin /etc/apt/preferences.d/cuda-repository-pin-600
  265  wget https://developer.download.nvidia.com/compute/cuda/11.1.0/local_installers/cuda-repo-ubuntu2004-11-1-local_11.1.0-455.23.05-1_amd64.deb
  266  sudo dpkg -i cuda-repo-ubuntu2004-11-1-local_11.1.0-455.23.05-1_amd64.deb
  267  sudo apt-key add /var/cuda-repo-ubuntu2004-11-1-local/7fa2af80.pub
  268  sudo apt-get update
  269  sudo apt-get -y install cuda
  270  cat /usr/local/cuda/version.txt
  271  nvcc --version
  272  /usr/local/cuda/bin/nvcc --version
  273  dpkg -l | grep cuda-toolkit
  274  whereis cuda
  275  nvcc -V
  276  sudo apt install nvidia-cuda-toolkit
  277  nvcc -V
  278  nvcc --version
  279  nvidia-smi
  280  dpkg -l | grep cuda-toolkit
  281  whereis cuda
  282  /usr/local/cuda/bin/nvcc --version
  283  subl ~/.zshrc
  284  export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
  285  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\\n                         ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  286  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64:${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  287  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  288  systemctl status nvidia-persistenced
  289  source ~/.zshrc
  290  /usr/bin/nvidia-persistenced --verbose
  291  sudo -i
  293  cd Downloads
  294  ls
  297  tar -xzvf cudnn-11.1-linux-x64-v<IP_ADDRESS>.tgz
  298  sudo cp cuda/include/cudnn*.h /usr/local/cuda/include
  299  sudo cp cuda/lib64/libcudnn* /usr/local/cuda/lib64\n
  300  sudo chmod a+r /usr/local/cuda/include/cudnn*.h /usr/local/cuda/lib64/libcudnn*
  301  cp -r /usr/src/cudnn_samples_v8/ $HOME
  302  sudo update-alternatives --config libcudnn
  303  sudo dpkg -i libcudnn*.deb
  304  ldconfig -p | grep cuda
  305  nvidia-smi
  306  cat /usr/local/cuda/include/cudnn.h | grep CUDNN_MAJOR -A 2
  307  cd
  308  python
  309  pip list
  310  pip install tensorflow
  311  python
  312  source ~/.zshrc
  313  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\\n                         ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  314  export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
  315  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\\n                         ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  316  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  317  source ~/.zshrc
  318  python
  319  source ~/.zshrc
  321  export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
  322  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
  323  python

The packages I've installed:

Powerlevel
Docker
Spotify
Nvidia-driver
cuDNN v8 for CUDA 10.1
cuDNN v7 for CUDA 10.1
ROS Noetic
Purge CUDA 10.1 [not sure if this was done correctly]
CUDA 11.1
cuDNN v8 for CUDA 11.1

Thanks for providing the log. I must point out that every CUDA runfile installation will overwrite the installed Nvidia driver.
I noticed that you used runfiles for both CUDA installations, from my experience local deb repos are more reliable.
I don't see anything wrong with installation of each individual package, but I must ask   310  pip install tensorflow is this the one and only tensorflow installation that you've done? If so, it will require preinstalled CUDA 10.1 and CUDNN 7. Installing CUDA 11.1 for a prebuilt binary against CUDA 10.1 does not have any effect. If we assume that you installed tensorflow after installing CUDA 11.1, the error messages indicate that CUDA 10.1 libs are still visible but not CUDNN 7.

312  source ~/.zshrc
313  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\n                         ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
314  export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
315  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64\n                         ${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
316  export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
317  source ~/.zshrc

Another question, are you sourcing .zhrc without modifying it? are you running those exports in other terminals other the ones in which you are runing python tensorflow scripts?
To be precise, these are the packages that enabled me to use tensorflow 2.3.1 with RTX 3080 on Ubuntu 20.04 :
cuda-repo-ubuntu2004-11-1-local_11.1.0-455.23.05-1_amd64.deb
cudnn-11.1-linux-x64-v<IP_ADDRESS>.tgz
TensorRT-<IP_ADDRESS>.Ubuntu-18.04.x86_64-gnu.cuda-11.1.cudnn8.0.tar.gz

I see. I wasn't sure what exactly the differences were between run file and deb so I just randomly chose run file. But then I realized something wasn't working so I used deb to install CUDA 11.1 again.  I installed tensorflow in with virtualenv but I didn't have it on my global pip so that's why I ran 310 pip install tensorflow to test if TensorFlow was detecting my gpu.

Another question, are you sourcing .zhrc without modifying it?

I actually had sublime open with .zshrc so I was changing it and then sourcing it. Heres what my .zshrc file looks like:
if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then
  source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh"
fi

export ZSH=$HOME/.oh-my-zsh

ZSH_THEME="robbyrussell"

plugins=(git)

source $ZSH/oh-my-zsh.sh

alias python=python3
alias pip=pip3

source ~/powerlevel10k/powerlevel10k.zsh-theme

[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh
source /home/harsh/.zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

# ROS
source /opt/ros/noetic/setup.zsh

# CUDA
export PATH=/usr/local/cuda-11.1/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
# export LD_LIBRARY_PATH=/usr/lib/cuda/lib64:$LD_LIBRARY_PATH
# export LD_LIBRARY_PATH=/usr/lib/cuda/include:$LD_LIBRARY_PATH

I'm not sure how to make TensorFlow use CUDA 11.1 instead of CUDA 10.1. It's very confusing. I think if there is no direct solution to this, I might just reinstall Ubuntu. That way I can make sure that I only install CUDA 11.1. I don't know if this is an effective solution.

export LD_LIBRARY_PATH=/usr/lib/cuda/include:$LD_LIBRARY_PATH

uncomment this line or add cuda include to LD_LIBRARY_PATH especially if you want to build something against CUDA.

I'm not sure how to make TensorFlow use CUDA 11.1 instead of CUDA 10.1. It's very confusing. I think if there is no direct solution to this, I might just reinstall Ubuntu. That way I can make sure that I only install CUDA 11.1. I don't know if this is an effective solution.

There are two solutions :

Install dependencies and pre-built tensorflow binaries (tf-nightly as I mentioned was reported to work out of the box with CUDA 11.1 https://pypi.org/project/tf-nightly/)
Install dependencies and build tensorflow from source.

Thanks a lot for your help @BorhenJlidi!


Make size type returned by -i option compatible with C standard

resolves #13876

Thank you. Can you please create a test for it? See test_xxd.vim

Thank you. Can you please create a test for it? See test_xxd.vim

Do you mean as in checking if sizeof(type returned by xxd) >= sizeof(size_t) ? Because otherwise there is nothing to test, only to change it so existing tests, which have int hardcoded as the type dont fail.

No I'd like to have a test, that verifies, that xxd -i now generates a size_t array

No I'd like to have a test, that verifies, that xxd -i now generates a size_t array

Do you mean changing the existing tests that check the type of the size variable, to use size_t ?
There's no "size_t" array being generated, only a size variable that has the type size_t.
The only platforms a test for this could fail on would be ones that don't follow the C standard, in which case I'd say having a test is kind of redundant.
Do you mean creating a test where the version of xxd without this change fails? You can maybe force it even without a 16 bit platform if you generate an array that is more than 4-5 GB ?
Otherwise you can probably force the compiler optimizations to mess up your code and use that as the test, as e.g. there are cases where using a type for a variable that is too small causes compiler optimizations to fail.
See e.g. the first example here:
https://mohitmv.github.io/blog/Shocking-Undefined-Behaviour-In-Action/

Also, separate from this, it may be desirable to make sure that arrays larger than 2^32 (a few GB) don't fail to announce their size correctly, but that would require actual tests, or trusting the compiler to determine it with sizeof(array)/sizeof(array[0]) instead of letting vim handle printing the size from a variable.

Heads up that this probably breaks a bunch of software that uses -i for source code generation, as they will now potentially need to include stddef.h IF xxd > latest. I just had to troubleshoot at least one project that no longer builds with build tools updated to xxd latest.
Might be useful to add a flag to revert to the native unsigned int type to make migration easier than having to update source code templates everywhere.

Maybe this helps?
https://github.com/Szybet/InkWatchy/blob/master/resources/global_functions.sh
https://github.com/Szybet/InkWatchy/blob/2c085c3a1db3a38fb6a814c44cd1b4ea0934e33a/resources/xxd_legacy.sh (this one needs xxd input with -i from a pipe, so xxd -i |xxdwrapper )
You will need to edit build scripts either way.
Otherwise I'd suggest coming up with a test environment have that doesn't build, as apparently all the existing test. environments have the type available by default or don't include a test.
What project were you building and how?

Before this change, a file generated using xxd -i compiled successfully without requiring any additional edits.  I suppose that xxd should simply use the long unsigned int type for a very long array instead of breaking backward compatibility.

Are you by any chance compiling  C projects which use headers in the wrong order? Say if you include  a generated file from xxd -i before any of the common standard headers that nearly every project uses, then you might get this error. Or if you're trying to compile this as C++ code even though it's only supposed to generate C.
I suspect all the tests have size_t available for this reason.
It's more complicated to support fully dynamic type generation and doesn't have the same guarantees as size_t with regard to choosing an appropriate type on a platform. You might end up with a type larger than what is natively supported on a 16 bit system for example.
It's also better to fail to compile than to compile with a bug, as using an array size that is too large for int isn't considered a compiler error and the warning might be overlooked when compiling a large project.

My point is that before this change,  xxd -i didn't require a program to include any additional headers. Therefore, this change introduces a serious regression.
According to the C standard, size_t is at least 16 bits, unsigned int is at least 16 bits, unsigned long is at least 32 bits, and unsigned long long is at least 64 bits.  So, changing unsigned int to size_t did not solve any problem anyway.

xxd should use a type that is appropriate (based on the standard, not the platform it is compiled for), according to the size of an array.

2. So, changing unsigned int to size_t did not solve any problem anyway.

I think maybe you didn't read the issue. A platform can have 32 bit addressing but can have an int type that is 16 bits. We already have similar issues with 64 bit platforms using 64 bit addressing but using 32 bit int types.

So, changing unsigned int to size_t did not solve any problem anyway.
I think maybe you didn't read the issue.
Ok, I agree that sizeof(size_t) is usually greater than sizeof(unsigned int) nowdays, but you can't rely on that based on the standard.

Int is not guaranteed to hold the size of an array for a platform.
Yes, if an array size doesn't fit in 16 bits you should use the type that is guaranteed to be at least 32 bit (same for 32 -> 64 bits).  size_t is not guaranteed to be more then 16 bits.

You can't store an array in memory that is bigger than size_t on any platform.

Technically you can have a platform that has 32 bit memory addressing but can only do objects in memory that are 16 bits large, but since size_t is the type returned by sizeof() it's not a problem.

Ok, I agree, but it doesn't change that the header requirement is a regression.

The only change that'd help with that while not violating the standard might be using int if the array is smaller than 16 bits and size_t for anything larger, but that means you need to generate the type dynamically.
I'm also not 100% sure that you can't run into the undefined behaviour situation I linked earlier if you do math to compute the size of one array using another.

In terms of generating a header file, adding an include makes a lot of sense, but still may break some users.

However, this feature was previously functional for C++ projects without any issues.  So, I still believe that use 'unsigned long' and 'unsigned long long' remains the best solution we have.

The documentation specifies that xxd -i is meant to generate C-style code, not C++.

I agree that size_t is better, but you broke something that worked for almost 3 decades, it can't be a new feature to unbreak it.
Again, xxd should use a type appropriate for array size, unsigned if it fits in 16 bits, unsigned long if it fits in 32 bits and unsigned long long if it fits in 64 bits.

JFYI, gcc built to compile for AVR triggers a error for 1Mb array (error: size of array is too large) and also issues a warning for size_t foo_len = 1048576; (warning: unsigned conversion from ‘long int’ to ‘size_t’ {aka ‘unsigned int’} changes value from ‘1048576’ to ‘0’ [-Woverflow]).

size_t is a type that is appropriate for every possible array size.
You can make a pull request for it if you think you can come up with a good solution that covers every use case without performance costs while supporting C++.

alright, let me roll back that change. It's seems to cause too much issues. Perhaps in some future we can make -i use correct type depending on size then.

@chrisbra possibly reopen the corresponding issue


Decode a Morse code message

On this milestone we:

Created a method to decode a Morse code character, takes a string parameter, and return the corresponding character in uppercase.
Created a method to decode an entire word in Morse code, takes a string parameter, and return the string representation.
Created a method to decode the entire message in Morse code, takes a string parameter, and return the string representation.

Hi @mercymugambi and @mnaibei, you are missing the future features section in your readme

@prolajumokeoni  can I have a minute to add it back?

@prolajumokeoni I have added it


Accessibility Improvements (Components)

Most components should be OK, but there are likely to be improvements.

Hi @markmead
May you allow me to work on this issue?, if the answer is "yes" which components need improvement? Thank you

Hi, @irham9494h I'm happy for you to work on this. Thanks for your interest!
There's no strict "this component needs looking at", it's more of a general review to improve accessibility.
Please don't feel like you need to do every component, just do the ones you are comfortable with 🎉

Please assign me this task, it can be my 1st pr for hacktoberfest.

Happy for you to work on @jyotika6221 but there's no need to change the assignee.

hi! I am a frontend dev and accessibility consultant, could I also help test accessibility? @markmead

Hey, @dianaberna of course! 🎉
Feel free to do as much/little as you feel like. It's an open issue for anyone to come in and make improvements.

I'm going to close this issue as I'm no longer getting relevant errors back from pa11y or aXe.
However, PRs are still welcome to improve accessibility.


Feature: Specify maximum cosine distance in the WHERE clause of table.search()

SDK
Python
Description
I'd love to be able to specify a minimum cosine similarity threshold (or maximum cosine distance) when using table.search(). One way to do this would be to alter the .where() method to allow a _distance condition:
max_distance = 0.3
table.search(vector).metric('cosine').where(f'_distance < {max_distance}').limit(10)

@changhiskhan suggested that .limit() be required in this case, which sounds good to me.
Weaviate does it like this:

I'd offer to add this new feature myself, but I don't know Rust yet. 😬
Thanks!

I looked at implementing this in Lance briefly. https://github.com/lancedb/lance/commit/abe30e79832c3f93325eed1678a504c72594dae1
The current blocking error happens here: https://github.com/lancedb/lance/blob/d56f65e76b5990b6eaaed6c657ad7f4f9bbfa681/rust/lance/src/dataset/scanner.rs#L276-L279
Right now the schema we pass to the expression optimizer doesn't include the _distance column. We therefore need to defer the expression optimization until later when we know whether there will be a distance column. Once we do that, it should just work.

Since distance values can be negative

This makes the mathematician in me scream. 😆
But thanks for the reminder.

I'd be interested in this feature as well, but for now I'm being pragmatic like so:
top_k = 10
max_distance = 0.3
results = [r for r in table.search(vector).metric('cosine').limit(top_k).to_list() if r["_distance"] < max_distance]

Thanks @mhillebrand, I've edited my comment to reflect yours.


Blm

NEW FEATURES:

implement Stars & half stars to reviews for rating field
Add Shirt component to render
begin construction on HomePage -- in progress
Update webpack v5 -- add config-override.js file and change dependencies to render successfully

UPDATES:

add rating field into Accordion Component
add 'size' field to cart for better UI experience
add UI feedback when adding item to cart
fixed file structure for ItemDetails for cleaner approach
bug fix: correctly render search results utilizing SearchedItemDetails component


Better handling of case where EPSG:4326 reprojection can't happen

In
geowave-vector/src/main/java/mil/nga/giat/geowave/vector/util/FeatureDataUtils.java
a failure to reproject results in data in another projection being inserted in the database.  We probably want to either

Log this (error) and don't insert anything
Runtime error (leaning away from this)
But either way don't want mixed projection in the same table.

Note: issues is still outstanding (despite merged commit above; that's where it was identified)


Fshakerin/clu release to main

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[ ] 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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

fixing the incorrectly selected update API option.

Please add an entry to the README.md file for this spec.

This PR just adds a new API path to an existing version. I added an entry for the json file that contains the API path. The PR is meant to bring the CLU 2021-11-01-preview version from release branch into main (An ask from Heath).

It adds a new document, which must be in the README.md under the appropriate tag so it's actually processed. I'll have to start a thread with stakeholders like @JeffreyRichter and @johanste about how to handle situations like this, especially under the guise of Cognitive Language Unification where this might happen more often than not.

Also, why is this just not a PR to merge the release/cognitiveservices/clu-2021-11-01-preview branch into main? As it is, I'll have to compare all the files in your PR to all the files in that branch (a would-be PR). It's more common to just merge the release branch we've been working on, and that I've been reviewing all this time.
If we're done with that branch, you can rebase it on main before proceeding (easier to review), or is that what you did?
git fetch upstream main
git rebase upstream/main
git push --force # or push to your own branch - is that was this PR is?

@fxs130430 is this ready to merge? We'd like to ship a new preview. We can do it on feature branches, but ideally it's on main so that the commits on which we pin won't be eliminated when this branch is squash-merged.


Get pystan-protostan compile working and tested on travis CI

Once this is done we can move on to bigger fish.

@ariddell If this is done can you close?


Possible bug in subdomain routing and controllers with the same name

Laravel v4.2.11
I was playing around with the subdomain grouping method for routing and noticed that if you have same controller name in both groups then the wrong one is being used depending on the namespace.
There isn't an easy way to create an example but here's some test code so you can see what I mean.
Route::group(['domain' => 'sub1.domain.com, 'namespace' => 'Sub1'], function()
{
	Route::resource('sessions', 'SessionsController', ['only' => ['create', 'store', 'destroy']]);
});

Route::group(['domain' => 'sub2.domain.com', 'namespace' => 'Sub2'], function()
{
    Route::resource('sessions', 'SessionsController', ['only' => ['create', 'store', 'destroy']]);
});

If you then reference sessions.store in a form via the Sub1 namespaced controller and view it'll output the URL for Sub2 instead.
The simple solution is of course not to have the same Controller names but I wondered if it was a bug, or expected functionality?
Further details:
Sub1 SessionsController:
namespace Sub1;

class SessionsController extends \BaseController {
	public function create()
	{
        return \View::make('sub1.login');
	}
}

View: sub1.login
{{ Form::open(['route' => 'sessions.store', 'role' => 'form']) }}

{{ Form::close() }}

With everything namespaced and running subdomains, it shouldn't be crossing between or referencing the other namespace or subdomain, should it?

Is this present in Laravel 4.2.16? Only the latest patch version of 4.2 or the latest dev versions of 4.2 or 5.0 are currently supported.

Closing due to inactivity.


Unconnected Pong

Trying to Connect a friend to my (Geyser)[https://geysermc.org/] server with this script but it's reporting a "Recieved Unconnected Pong from server.
I am not sure what else this could be. Without debug we are seeing connections trying to come in but nothing show on Xbox.
@echo off
phantom-windows.exe -server play.capecraft.net:19132 -6 -debug
pause

I am having the same problem. This issue started when I updated the server to Bedrock v1.19.
The server shows up on the Xbox Lan game list when I stop the server and the "Server Offline" message appears on the LAN Game server list. However, when I restart the server the game vanishes from the Lan Game list.
The server is definitely running because I can connect using Minecraft on a Windows computer or on the Xbox using the Bedrock Together app.
Any help with this would be greatly appreciated. Thanks


Pin MSAL version to avoid broken release of MSAL 1.1.16

Workaround for:
https://github.com/AzureAD/microsoft-authentication-library-for-objc/issues/1280

@tjprescott Do we care if we pin it to 1.1.2 as opposed to 1.1.15. Or is this just telling consumers 15 is the highest we are willing to go?

The way it is written it will always grab 1.1.15


2x dragon claws drop on BSO COX raid, but never got them in bank.

🐛 Bug Report
just finish a raid and got 2x dragon claws. never saw them in my bank ever, see screenshots. not sure what else i can do.
would be nice to get them since its my first big drop. or at least fix it so my next drop actually showup!
https://user-images.githubusercontent.com/78720782/107186061-95e6f080-69b1-11eb-8bda-f3f1eef212d4.PNG
https://user-images.githubusercontent.com/78720782/107186065-967f8700-69b1-11eb-840b-fd455ffc3946.PNG
https://user-images.githubusercontent.com/78720782/107186067-967f8700-69b1-11eb-862d-ab1e44e47a7e.PNG
https://user-images.githubusercontent.com/78720782/107186070-97181d80-69b1-11eb-84e6-4c38e490a9bb.PNG
Thanks, love the bot!
2x dragon claws drop on BSO COX raid, but never got them in bank.

resolved, if need refund contact mod or magnaboy


Increase the amount of time the progressBlock is called

Hey there,
Is there a way to increase the amount of time the progressBlock is called for the setImage function? Current I only ever get the following 5 "notifications", every time I try to download my test image. It's always at the same percentages:
progress: 32.9320013668067%
progress: 34.1862475126128%
progress: 67.1182488794195%
progress: 69.1764989648449%
progress: 100.0%

Also, am I correct in assuming that the progressBlock will ALWAYS be called at least once when the progress is 100.0%?
Thanks

Hi,
The progress block will be called every time the url session task received a data trunk, so there is no good way to increase the amount in a good way.
And if your server is returning the correct expected size to you, the progress block should be called when it finishes. But a better way to handle the finish things should be the completion handler callback instead.


Improve structure of test targets

Problem to Solve
In client-java, we have separated out the Core and Cluster tests. I'm not sure if this is really a good idea, we should review it. Also, it has resulted in a huge number of CI jobs, which feels excessive.
Whatever we do, it should be propagated to the other clients. The other clients currently have no separation between Core and Cluster.
Proposed Solution
We could either:

bring the Core and Cluster tests together again, or
bring the various Graql tests together again (definable, writable, readable)

Could even do both.

This change was propagated to all clients.


www. doesn't work?

I followed the guide completely, mysite.com works, but www.mysite.com still goes to the default nginx page.

The only issue is with certbot I think? The page works but it isn't secure.

Make sure your www. domain is getting renewed along with the normal domain's certificate. Remember, www is not special, it's just like any other subdomain, so it needs to be included in the subjects of a certificate, or have its own certificate.


Create insertion_sort.java

Thanks for contributing. It would be great if you could add a description and the issue number.

@pratik0527 : Please check out our contribution guidelines
(https://github.com/fnplus/interview-techdev-guide/blob/master/CONTRIBUTING.md)
for your PR's.

@pratik037 : Thanks for Contributing