fixed layout on mobile

You should implement the following interactions:

When the user clicks (or taps) the button to check project details, the popup with details about the project appears.
When the user clicks (or taps) the close (X) button, the popup disappears.

In order to associate each project with the popup window details, you must refactor the project section:

You need to use a JavaScript array to store all of the information for all projects.
For each project you need to store the following pieces of data in a JavaScript object, at a minimum: name, description, featured image, technologies, link to live version, link to source.
You need to update the main page so that the projects section is created dynamically using the information stored in that JavaScript object. Remember, all of the HTML in that section is created when the page loads.
After that, you could implement the popup window.

You should implement popups for both mobile and desktop screen sizes

Implemented the following interactions:

When the user clicks (or taps) the button to check project details, the popup with details about the project appears.
When the user clicks (or taps) the close (X) button, the popup disappears.

Refactored the project section:

Used a JavaScript array to store all of the information for all projects.
Stored the following pieces of data in a JavaScript object, at a minimum: name, description, featured image, technologies, link to live version, link to source.
Updated the main page so that the projects section is created dynamically using the information stored in that JavaScript object. Remember, all of the HTML in that section is created when the page loads.
Implements the popup window.

STATUS: Changes Required ♻
Hi @willococa, 👋
Good job so far! There are some issues that you still need to work on to go to the next project but you are almost there!

To Highlight 🥇

Descriptive Pull Request title and summary. ✔
User clicks the button, the popup with details about the project appears ✔
User clicks the close (X) button, the popup disappears ✔
Modal popup data is populated with the data from the projects array ✔
Pair-Programming activity implemented ✔
Good use of Github flow ✔

Changes Required

[x]   Please check the comments under the review.

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me on( @brainconnect93 ) in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

the original pull request was https://github.com/willococa/portfolio/pull/12 it seems that as i  created a new feature from this feature and merged it I accidentally merged this pull request so I had to create a new one these are the fixes suggested on the previous one:
https://github.com/willococa/portfolio/pull/12#discussion_r1174143344

Your project works and align fine in the desktop view, but when i move to the mobile view it wasn't aligning or looking good at all kindly check your mobile view design and be sure you are maintaining a screen size of 375px whilst designing it.

Below is the video of the webpage performance 👇
willpop.mp4


Module not compiling when a dependency

I've got a project where erlang_iso8601 is a dependency (in the project's rebar.config file). When running rebar compile, only the .app.src and unit test file get compile and placed in the ./deps/iso8601/ebin directory:
$ ls -al deps/iso8601/ebin/
total 48
drwxr-xr-x   4 oubiwann  staff    136 Sep  6 15:45 .
drwxr-xr-x  10 oubiwann  staff    340 Sep  6 15:43 ..
-rw-r--r--   1 oubiwann  staff    262 Sep  6 15:45 iso8601.app
-rw-r--r--   1 oubiwann  staff  20244 Sep  6 15:45 iso8601_tests.beam

In order to compile the iso8601.beam file, I have to switch to deps/iso8601 and run rebar compile in that dir.

Looks like this is due to a discrepancy between two different .app.src files (one in src, one in ebin).
I'll submit a patch.

This is fixed now.


Removing minheight from dialog implementation

Removing minHeight on dialog update to avoid a breaking changes

But won't your other changes break without a min-height?

Closing. as planning to rewrite Dialog component https://github.com/segmentio/evergreen/pull/193#issuecomment-385566872


AttributeError: 'BetterScreen' object has no attribute 'report_device_status'

Crash when running vim
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/pymux/main.py", line 500, in run_server
PipeInput(), DummyCallbacks())
File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/eventloop/posix.py", line 150, in run
t()
File "/usr/local/lib/python2.7/dist-packages/pymux/process.py", line 280, in _read
process()
File "/usr/local/lib/python2.7/dist-packages/pymux/process.py", line 274, in process
self.stream.feed(d)
File "/usr/local/lib/python2.7/dist-packages/pymux/stream.py", line 51, in feed
send(c)
File "/usr/local/lib/python2.7/dist-packages/pymux/stream.py", line 157, in _parser_generator
dispatch(csi[char], *params)
File "/usr/local/lib/python2.7/dist-packages/pymux/stream.py", line 91, in dispatch
getattr(listener, event)(*args, **flags)
AttributeError: 'BetterScreen' object has no attribute 'report_device_status'

Hi @ya790206,
Thanks for reporting! This went wrong after the last release of pyte. I'll fix it asap.
Jonathan

Hi @ya790206,
This was fixed 8 days ago in https://github.com/jonathanslenders/pymux/commit/df949504b28fb73621a39552cd0fda3bdacafe10
I will do a new release soon.

(Don't hesitate to create a new issue if you find other bugs.)


FGWREU-111 - Report state null with physical buttons

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
After upgrading to ZWaveJSUI 8.19.0 (before I used 8.13.1) , my fibaro state is incorrect when I use physical clic (with specific Target Value it's OK).
In 8.13.1, there is no log about currentValue, but now with 8.19.0 I see somes new logs (check Attach Drivers Logfile - 8.19.0).
There is nothing is newValue and I got a null value for state:
https://community.jeedom.com/uploads/default/original/3X/8/b/8b42fe8065b1be85daf1d223efbc61a803119409.png
For your information, my shutter is a bubendorff with 4 wires (N, L and 2 commands wires), so I can't use calibrate feature, I want to set it manually (information about my shop).
I configured the FGWREU-111 like this:

Parameter 151: 5 (5 - Roller blind with built-in driver)
Parameter 155: 5W (if I disable it, nothing work)
Parameter 156 / 157: Set time manually

Maybe it's relies with https://github.com/zwave-js/node-zwave-js/issues/5825
If you need more information, please tell me.
Device information
Manufacturer: Fibaro
Model name: FGWREU-111
Node ID in your network: 17
How are you using node-zwave-js?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[X] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch: 11.0.0
zwave-js-ui branch: 8.19.0
Did you change anything?
yes (please describe)
If yes, what did you change?
Yes update today to 8.19.0 from 8.13.1 but 8.13.1 don't work too.
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
8.13.1:
Arg 0:
└─commandClassName: Multilevel Switch
└─commandClass: 38
└─property: targetValue
└─endpoint: 1
└─newValue: 0
└─prevValue: 0
└─propertyName: targetValue
2023-05-31T20:21:41.627Z - value updated
Arg 0:
└─commandClassName: Multilevel Switch
└─commandClass: 38
└─property: duration
└─endpoint: 1
└─newValue: unknown
└─prevValue: unknown
└─propertyName: duration
2023-05-31T20:21:42.510Z - value updated
Arg 0:
└─commandClassName: Multilevel Switch
└─commandClass: 38
└─property: duration
└─endpoint: 1
└─newValue: unknown
└─prevValue: unknown
└─propertyName: duration
2023-05-31T20:21:44.751Z - value updated
Arg 0:
└─commandClassName: Meter
└─commandClass: 50
└─property: value
└─propertyKey: 66049
└─endpoint: 1
└─newValue: 0
└─prevValue: 0.3
└─propertyName: value
└─propertyKeyName: Electric_W_Consumed

8.19.0:
*2023-06-28T18:09:17.832Z* - **value updated** Arg 0: └─commandClassName: Multilevel Switch └─commandClass: 38 └─property: currentValue └─endpoint: 1 └─newValue └─prevValue: 7 └─propertyName: currentValue

*2023-06-28T18:09:20.193Z* - **value updated** Arg 0: └─commandClassName: Meter └─commandClass: 50 └─property: value └─propertyKey: 66049 └─endpoint: 1 └─newValue: 0 └─prevValue: 0.4 └─propertyName: value └─propertyKeyName: Electric_W_Consumed

zwavejs_2023-06-28.log
Logfile :)

I'm afraid there's nothing to be done about that:
2023-06-28T20:45:08.841Z SERIAL « 0x010f0004001109600d01002603fefefe5b                                (17 bytes)
                                                              ^^^^^^

These 3 bytes mean "unknown" "unknown" "unknown", so the device doesn't know the state itself.

About that:

I've opened https://github.com/zwave-js/zwave-js-ui/issues/3153 to make it clearer what null means.

Bad news...
I think it's a firmware issue, because I think module know the state.
In fact, when I use first physicals buttons and after set position with zwavejs, the shutter go to the good position everytime!
If the state was really unknow, it can go to the right position, isn't it?

I'm inclined to agree

Impossible to send these informations to Fibaro...
Thanks for your help!


UCP: support help command

Description

Move all available commands into a single package, and add descriptions for them.
/help command will comment with basic usage comment.

Bonus
/help command comments different guide for different people, consider the access.
Difficulty

Easy

Score

300

The extra bonus worth 200 points.
Mentor
@you06
Recommended Skills

Go

Are all the available commands in cmd/bot.go？

@wq1019 You only need to consider the commands in this bot.
To find all commands, you can look into the issue comment handle function in providers to find all the available commands.
https://github.com/pingcap-incubator/cherry-bot/blob/70abd98e8864e5b80bc9cb6ad1497512339724bd/bot/webhook.go#L71-L97

Maybe you can collect all the commands into pkg/types or a new package.


chore(workspace): update to mwc 0.25.1

introduces replacement for the lit-helpers locally for the interim. see https://open-wc.org/blog/updating-to-lit-2-0/#open-wclit-helpersnext

[ ] restore vwc-slider autofocus

partially resolved by material-components/material-web#2823


feat: add the possibility to configure namespace for make page command

BREAKING CHANGE: Change configuration file :
pages->path becomes string instead app_path()
resources->path becomes string instead app_path()
possibility to use a $JOKER$ for resources->path and namespace
e.g :
  resources' => [
          'namespace' => 'App\\Filament\\$RESOURCE$\\Resources',
          'path' => 'Filament/Resources/$RESOURCE$/Pages',
          'register' => [],
      ],

resolve #2494

Thanks, but duplicate of #2784, which does not have breaking changes.

Alright but #2784 resolve only one problem.
In future the same problem will be always present for the path, namespace,...
Thinking for the next major version

Honestly I am very confused about what this PR introduces and why we need a wildcard

It introduces a customization of the namespace and path.
Currently, the path is not customizable because it is hardcoded. This allows to give back this possibility via the config file. In particular for :
``filament\resources
\{{$resource}}\pages```

I'm not really interested in customising the path to files inside the resource, the original issue was filed because the path to the resources parent directory was not being observed


[OLS-3 Cohort call week 7]

Weekly emails

[ ] Send email to mentees
[ ] Send email to speakers

Cohort call video preparation (from week 6)

[x] Download from Zoom cloud recordings
[x] Upload to Otter.ai (will need a few minutes to process)
[x] Upload to the OLS YouTube account
[x] Create a front page slide for the video - templates are available in Google Drive
[x] Make sure the YouTube video is added to the current cohort playlist
[x] Correct Otter.ai transcripts (make sure to use uploaded video, not the original transcript, as the timings won't match the video)
[x] Download corrected transcript as a .srt file from Otter
[x] Upload it to the YouTube video

Website (in schedule in _data folder)

[x] Add link to recording
Add talks

[x] Add link to slide deck
[ ] Add peron detail to people.yaml if needed

I'm assuming point 3 is also for week 6!


Change Binding Post Spacing to 19mm

Standard binding post spacing is 3/4" (19.05mm).  The binding posts in the current model appears to be about 34mm.  Changing the spacing to the standard used for bench PSUs would allow use of dual-binding post adapters.

I added step and stl files with 19mm spacing. I actually intended the original wider spacing because I've only ever used dual-banana connectors extremely rarely, but have often bumped my fingers into the neighboring terminal.  Anyway, it's good to have choices!


Faceless Void sometimes casts chrono and then runs

thanks for reporting in Github. should be fixed in the latest release today


Cloud rebalancer UI

Fixes #492

TODO: rebase this on https://github.com/citusdata/citus_docs/pull/547 when that gets merged so that the new content goes in the right section.

Waiting for final review and merge of Cloud TOC reorganization, then I'll rebase and merge this one.


Create How to create a QR generator website instruction

Title and Issue number

Title :
Issue No. :
Code Stack :
Close #<issue_no>

Checklist:

[] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have updated the Index.html file for my contribution

Please fill the proper details in the description

Sir merge my request , I create a file that show how I create a QR generator using front end

Sir I basically instruct that hoe I create a QR generator Frontend website.
Please merge 🥹🥹
On Fri, 6 Oct, 2023, 10:11 Sadanand Pai, @.***> wrote:

Assigned #100
https://github.com/sadanandpai/frontend-mini-challenges/pull/100 to
@jeetRaha9 https://github.com/jeetRaha9.
—
Reply to this email directly, view it on GitHub
https://github.com/sadanandpai/frontend-mini-challenges/pull/100#event-10570672620,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3W7ZA43KHR73IZTAYW55ZTX56DY7AVCNFSM6AAAAAA5VHCCYOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQGU3TANRXGI3DEMA
.
You are receiving this because you were assigned.Message ID:
<sadanandpai/frontend-mini-challenges/pull/100/issue_event/10570672620@
github.com>


Change from python-dateutil to types-python-dateutil

We aren't running CI on this often (last time was 7 months ago) and there seems to be a change with using python-dateutil and instead the CI fails saying use types-python-dateutil
CI failure: https://app.circleci.com/pipelines/github/dbt-labs/hologram/158/workflows/130bcf0c-3f8e-43ad-be93-e6cfa58fc2e3/jobs/315
New package details explain its a stub package for the python-dateutil package: https://pypi.org/project/types-python-dateutil/
I ran locally and it builds and passes pytest with this

Hi, Is it possible to resolve these conflicts and merge the branch ?

@praveerk I'm very sorry for the delay! We are moving on releasing this now


Feature Request: Ability to upload videos in mass to lbry.tv via BitTorrent

I would love lbry.tv to have the ability to take video uploads in mass batches via bit torrent via a torrent file to upload videos in batches to lbry.tv channels via BitTorrent similar to how bit torrent can be used to upload files in batches or mass to the internet archive.
the way this should work is
you put all the video files in one folder you want to upload and create a new torrent file of that folder
you enter trackers for lbry into the torrent properties when you create the new torrent file
you let the new torrent file start seeding
you upload the .torrent file itself to your channel on lbry.tv
Lbry.tv from there downloads your videos over BitTorrent and puts your videos on the lbry.tv network under the channel you selected to upload the .torrent file you created to seed the files.

Thanks for filing this issue! We have some basic torrent support on the SDK side but it's not working with lbry.tv and probably won't be for some time. We may consider this down the road.
We're also looking into the ability to add multiple files along side a single claim which could help the multiupload scenario.


Add swagger schema for Microsoft.MachineLearning/webservices RP

Commit of preview version for the Microsoft.MachineLearning/webservices RP APIs swagger schema

Hi @tudordid, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (tudordid). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

No modification for Python


[flutter_adaptive_scaffold] Use ClipRect in AdaptiveScaffold widget

I am trying to adapt the go_router nested navigation sample to use an AdaptiveScaffold but ran into an issue with the animation, where the navigation rail is hidden by the inner Navigator's transition animation:

Code sample
// Copyright 2013 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

import 'package:flutter/material.dart';
import 'package:flutter_adaptive_scaffold/flutter_adaptive_scaffold.dart';
import 'package:go_router/go_router.dart';

final GlobalKey<NavigatorState> _rootNavigatorKey =
    GlobalKey<NavigatorState>(debugLabel: 'root');
final GlobalKey<NavigatorState> _shellNavigatorKey =
    GlobalKey<NavigatorState>(debugLabel: 'shell');

// This scenario demonstrates how to set up nested navigation using ShellRoute,
// which is a pattern where an additional Navigator is placed in the widget tree
// to be used instead of the root navigator. This allows deep-links to display
// pages along with other UI components such as a BottomNavigationBar.
//
// This example demonstrates how to display a route within a ShellRoute and also
// push a screen using a different navigator (such as the root Navigator) by
// providing a `parentNavigatorKey`.

void main() {
  runApp(ShellRouteExampleApp());
}

/// An example demonstrating how to use [ShellRoute]
class ShellRouteExampleApp extends StatelessWidget {
  /// Creates a [ShellRouteExampleApp]
  ShellRouteExampleApp({Key? key}) : super(key: key);

  final GoRouter _router = GoRouter(
    navigatorKey: _rootNavigatorKey,
    initialLocation: '/a',
    routes: <RouteBase>[
      /// Application shell
      ShellRoute(
        navigatorKey: _shellNavigatorKey,
        builder: (BuildContext context, GoRouterState state, Widget child) {
          return ScaffoldWithNavBar(child: child);
        },
        routes: <RouteBase>[
          /// The first screen to display in the bottom navigation bar.
          GoRoute(
            path: '/a',
            builder: (BuildContext context, GoRouterState state) {
              return const ScreenA();
            },
            routes: <RouteBase>[
              // The details screen to display stacked on the inner Navigator.
              // This will cover screen A but not the application shell.
              GoRoute(
                path: 'details',
                builder: (BuildContext context, GoRouterState state) {
                  return const DetailsScreen(label: 'A');
                },
              ),
            ],
          ),

          /// Displayed when the second item in the the bottom navigation bar is
          /// selected.
          GoRoute(
            path: '/b',
            builder: (BuildContext context, GoRouterState state) {
              return const ScreenB();
            },
            routes: <RouteBase>[
              /// Same as "/a/details", but displayed on the root Navigator by
              /// specifying [parentNavigatorKey]. This will cover both screen B
              /// and the application shell.
              GoRoute(
                path: 'details',
                parentNavigatorKey: _rootNavigatorKey,
                builder: (BuildContext context, GoRouterState state) {
                  return const DetailsScreen(label: 'B');
                },
              ),
            ],
          ),

          /// The third screen to display in the bottom navigation bar.
          GoRoute(
            path: '/c',
            builder: (BuildContext context, GoRouterState state) {
              return const ScreenC();
            },
            routes: <RouteBase>[
              // The details screen to display stacked on the inner Navigator.
              // This will cover screen A but not the application shell.
              GoRoute(
                path: 'details',
                builder: (BuildContext context, GoRouterState state) {
                  return const DetailsScreen(label: 'C');
                },
              ),
            ],
          ),
        ],
      ),
    ],
  );

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      routerConfig: _router,
    );
  }
}

/// Builds the "shell" for the app by building a Scaffold with a
/// BottomNavigationBar, where [child] is placed in the body of the Scaffold.
class ScaffoldWithNavBar extends StatelessWidget {
  /// Constructs an [ScaffoldWithNavBar].
  const ScaffoldWithNavBar({
    required this.child,
    Key? key,
  }) : super(key: key);

  /// The widget to display in the body of the Scaffold.
  /// In this sample, it is a Navigator.
  final Widget child;

  @override
  Widget build(BuildContext context) {
    return AdaptiveScaffold(
      destinations: [
        NavigationDestination(
          icon: Icon(Icons.home),
          label: 'A Screen',
        ),
        NavigationDestination(
          icon: Icon(Icons.business),
          label: 'B Screen',
        ),
        NavigationDestination(
          icon: Icon(Icons.notification_important_rounded),
          label: 'C Screen',
        ),
      ],
      selectedIndex: _calculateSelectedIndex(context),
      onSelectedIndexChange: (idx) => _onItemTapped(idx, context),
      body: (_) => child,
    );
  }

  static int _calculateSelectedIndex(BuildContext context) {
    final String location = GoRouterState.of(context).location;
    if (location.startsWith('/a')) {
      return 0;
    }
    if (location.startsWith('/b')) {
      return 1;
    }
    if (location.startsWith('/c')) {
      return 2;
    }
    return 0;
  }

  void _onItemTapped(int index, BuildContext context) {
    switch (index) {
      case 0:
        GoRouter.of(context).go('/a');
        break;
      case 1:
        GoRouter.of(context).go('/b');
        break;
      case 2:
        GoRouter.of(context).go('/c');
        break;
    }
  }
}

/// The first screen in the bottom navigation bar.
class ScreenA extends StatelessWidget {
  /// Constructs a [ScreenA] widget.
  const ScreenA({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          children: <Widget>[
            const Text('Screen A'),
            TextButton(
              onPressed: () {
                GoRouter.of(context).go('/a/details');
              },
              child: const Text('View A details'),
            ),
          ],
        ),
      ),
    );
  }
}

/// The second screen in the bottom navigation bar.
class ScreenB extends StatelessWidget {
  /// Constructs a [ScreenB] widget.
  const ScreenB({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          children: <Widget>[
            const Text('Screen B'),
            TextButton(
              onPressed: () {
                GoRouter.of(context).go('/b/details');
              },
              child: const Text('View B details'),
            ),
          ],
        ),
      ),
    );
  }
}

/// The third screen in the bottom navigation bar.
class ScreenC extends StatelessWidget {
  /// Constructs a [ScreenC] widget.
  const ScreenC({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          children: <Widget>[
            const Text('Screen C'),
            TextButton(
              onPressed: () {
                GoRouter.of(context).go('/c/details');
              },
              child: const Text('View C details'),
            ),
          ],
        ),
      ),
    );
  }
}

/// The details screen for either the A, B or C screen.
class DetailsScreen extends StatelessWidget {
  /// Constructs a [DetailsScreen].
  const DetailsScreen({
    required this.label,
    Key? key,
  }) : super(key: key);

  /// The label to display in the center of the screen.
  final String label;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Details Screen'),
      ),
      body: Center(
        child: Text(
          'Details for $label',
          style: Theme.of(context).textTheme.headlineMedium,
        ),
      ),
    );
  }
}

As a workaround, I can wrap the AdaptiveScaffold's child with a ClipRect widget, but is this something that the AdaptiveScaffold could take care of or at least document somewhere?

Issue is reproducible using the code sample provided above.

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.9, on macOS 13.0.1 22A400 darwin-arm, locale en-GB)
    • Flutter version 3.3.9 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (2 weeks ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • 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.13+0-b1751.21-8125866)

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

[✓] Connected device (4 available)
    • M2007J20CG (mobile)    • 5dd3be00                             • android-arm64  • Android 12 (API 31)
    • iPhone 14 Pro (mobile) • 4F72110C-F38B-4CF9-93C4-4D6042148D28 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.0.1 22A400 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.94

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

• No issues found!

[!] Flutter (Channel master, 3.7.0-4.0.pre.38, on macOS 13.0.1 22A400 darwin-arm64, locale en-GB)
    • Flutter version 3.7.0-4.0.pre.38 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 521028c808 (10 hours ago), 2022-12-07 13:46:17 -0800
    • Engine revision 67254d6e4b
    • Dart version 2.19.0 (build 2.19.0-467.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • 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.13+0-b1751.21-8125866)

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

[✓] Connected device (4 available)
    • M2007J20CG (mobile)    • 5dd3be00                             • android-arm64  • Android 12 (API 31)
    • iPhone 14 Pro (mobile) • 4F72110C-F38B-4CF9-93C4-4D6042148D28 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.0.1 22A400 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.94

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

! Doctor found issues in 1 category.


Could not connect to Ollama API

Bug Description
After updating to Langflow 1.1.1 Ollama embeddings component is erroring out while building the component with : Error building Component Ollama Embeddings: Could not connect to Ollama API. This worked with earlier

Reproduction
Press run button on Ollama Embeddings Component
Expected behavior
Component build successful
Who can help?
No response
Operating System
Windows
Langflow Version
1.1.1
Python Version
None
Screenshot

Flow File
No response

Hey @samgit17
I just tried to reproduce your case and it worked as expected.
https://github.com/user-attachments/assets/db45ca52-0f7f-4072-9c16-0a860e85f85f
Make sure you have the embedding installed.
https://ollama.com/library/mxbai-embed-large

I am having the issue still. Verified that the embed model is returning a response with curl cmd : curl http://localhost:11434/api/embed -d "{"model": "nomic-embed-text:latest", "input": "Why is the sky blue?"}". That means the model and the api on ollama is working. But the Ollama Embedding Component  build fails repeatedly with Could not  connect to Ollama API

Will try an update on langflow

update too didnt work.

Hey @samgit17! I'm here to help you with any bugs, questions, or contributions. Let's squash this bug together!
I found a similar issue that was reported and resolved. The problem with the Ollama Embeddings component not connecting to the Ollama API after updating to Langflow 1.1.1 is likely due to the base_url being set to "http://localhost:11434". If the Ollama API is not running on this URL or port, the connection will fail. You should ensure that the Ollama API is running and accessible at the specified base_url. If the API has moved to a different URL or port, update the base_url accordingly in the component's configuration [1].
To continue talking to Dosu, mention @dosu.

@dosu - Yes Ollama server is running at the port 11434 on localhost, I was able to get a response using curl.

Which vector store are you using?

@samgit17 I had the same error. The issue for me was that there was a "temperature" argument which you need to delete:
src\backend\base\langflow\components\embeddings\ollama.py

@samgit17 I had the same error. The issue for me was that there was a "temperature" argument which you need to delete:
src\backend\base\langflow\components\embeddings\ollama.py

@KevinMichaelSchindler - You are absolutely right, deleted the temperature argument and presto, that worked like a charm. Can this be fixed in a future release, I banged my head on this issue for the last few days since updating to 1.1.1.

Ahh, ye no worries that happens. Just one tip, when you run langflow
locally, copy paste the stack trace into chatGPT/Claude and ask what the
issue is. The stacktrace is very long and the "temperature" stuff was
mentioned way at the beginning of the trace and was overshadowed but the
other exceptions. But an LLM can scan much better and can find it :)
On Fri, Nov 29, 2024, 7:57 PM samgit17 @.***> wrote:

@samgit17 https://github.com/samgit17 I had the same error. The issue
for me was that there was a "temperature" argument which you need to delete:
src\backend\base\langflow\components\embeddings\ollama.py [image: image]
https://private-user-images.githubusercontent.com/43708715/391133696-6e1f6320-a84d-4d3a-b7a7-1837c332e8dc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzI5MDY2MjcsIm5iZiI6MTczMjkwNjMyNywicGF0aCI6Ii80MzcwODcxNS8zOTExMzM2OTYtNmUxZjYzMjAtYTg0ZC00ZDNhLWI3YTctMTgzN2MzMzJlOGRjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTI5VDE4NTIwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ5Yjk5NjEyZmJhMTc0MjQ4YTc3YzRkODBiZDlmN2UwNjY3MzBkNDNhNjE4OWI1OTY5MzIxMTNmYmVkOTdlOTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.f4NkSugY2sX2jVHtTARgluAWERlfPjgzusixm28McL8
@KevinMichaelSchindler https://github.com/KevinMichaelSchindler - You
are absolutely right, deleted the temperature argument and presto, that
worked like a charm. Can this be fixed in a future release, I banged my
head on this issue for the last few days since updating to 1.1.1.
—
Reply to this email directly, view it on GitHub
https://github.com/langflow-ai/langflow/issues/4895#issuecomment-2508361388,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKNPCK6OBJVLC7AZCJ6AOXT2DC2LLAVCNFSM6AAAAABSTQVNPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBYGM3DCMZYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


exits with strange errors

This is the current tip of master:
/usr/local/bin/flexible_freeze.py: 10: /usr/local/bin/flexible_freeze.py: Flexible Freeze script for PostgreSQL databases
Version 0.5
(c) 2014 PostgreSQL Experts Inc.
Licensed under The PostgreSQL License

This script is designed for doing VACUUM FREEZE or VACUUM ANALYZE runs
on your database during known slow traffic periods.  If doing both
vacuum freezes and vacuum analyzes, do the freezes first.

Takes a timeout so that it wont: File name too long
/usr/local/bin/flexible_freeze.py: 11: /usr/local/bin/flexible_freeze.py: Note: not found
/usr/local/bin/flexible_freeze.py: 12: /usr/local/bin/flexible_freeze.py: may: not found
/usr/local/bin/flexible_freeze.py: 272: /usr/local/bin/flexible_freeze.py: Syntax error: Unterminated quoted string```

Oh, it seems the reason is that there's no shebang #!/usr/bin/python or similar at the top. We should probably mention that in the README

Yah, my understanding is that it's typical python idiom to omit the #!/use/bin/env python line you would expect — maybe because python is used on Windows too? Anyway, I'll patch the README once I'm back at my computer.

I already submitted a pull request


minor: 添加服务目录搜索空状态

Codecov Report

Merging #1051 (f3ca2b4) into v2.6.x_develop (a72d2f1) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop    #1051   +/-   ##
===============================================
  Coverage           60.58%   60.58%
===============================================
  Files                 469      469
  Lines               30073    30073
===============================================
  Hits                18220    18220
  Misses              11853    11853

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


optimize: fix codecov (2.x)

optimize: fix codecov (2.x)

Codecov Report

Merging #5829 (2681328) into 2.x (e69627d) will increase coverage by 0.28%.
Report is 70 commits behind head on 2.x.
The diff coverage is 52.85%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files

@@             Coverage Diff              @@
##                2.x    #5829      +/-   ##
============================================
+ Coverage     48.73%   49.02%   +0.28%
- Complexity     4339     4428      +89
============================================
  Files           778      805      +27
  Lines         27454    28498    +1044
  Branches       3412     3571     +159
============================================
+ Hits          13380    13970     +590
- Misses        12677    13049     +372
- Partials       1397     1479      +82

Files Changed
Coverage Δ

...c/main/java/io/seata/common/ConfigurationKeys.java
0.00% <ø> (ø)

...ommon/src/main/java/io/seata/common/Constants.java
100.00% <ø> (ø)

...rc/main/java/io/seata/common/util/StringUtils.java
41.07% <0.00%> (ø)

...c/main/java/io/seata/config/FileConfiguration.java
46.82% <0.00%> (-0.28%)
:arrow_down:

...eata/config/exception/ConfigNotFoundException.java
0.00% <0.00%> (ø)

...in/java/io/seata/config/file/SimpleFileConfig.java
84.61% <0.00%> (-15.39%)
:arrow_down:

.../src/main/java/io/seata/core/constants/DBType.java
0.00% <0.00%> (ø)

...c/main/java/io/seata/core/context/RootContext.java
46.77% <ø> (ø)

...rc/main/java/io/seata/core/model/GlobalStatus.java
77.50% <0.00%> (-22.50%)
:arrow_down:

.../io/seata/core/protocol/AbstractResultMessage.java
71.42% <ø> (-28.58%)
:arrow_down:

... and 115 more

... and 65 files with indirect coverage changes


3:<IP_ADDRESS> - Patient Identifiers vs Patient Identities

Section Number 3:<IP_ADDRESS> https://profiles.ihe.net/ITI/PIXm/ITI-83.html#2383413-expected-actions
Issue Sec <IP_ADDRESS>.2.1 and <IP_ADDRESS>.2.2 use "Patient Identifiers", but <IP_ADDRESS>.3 uses "Patient Identities" for the same concept.
Proposed Change
In the following text from <IP_ADDRESS>.3, I think "Patient Identities" which I marked in Italics should be changed to "Patient Identifiers":
The Patient Identifier Cross-reference Manager shall use the sourceIdentifier and the targetSystem to determine the Patient Identities that match, where Patient Identities include business identifier(s) and the Logical id(s) of FHIR Patient Resource(s).
Response returned encoding and semantics is defined in Section 2:<IP_ADDRESS>:
The Patient Identities returned may be a subset based on policies that might restrict access to some Patient Identities. For guidance on handling Access Denied, see ITI TF-2x: Appendix Z.7.
Priority:

Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

thx, will adjust it.


[SPARK-16251][CORE][wip] Fix Flaky test - LocalCheckpointSuite's - missing checkpoint block…

What changes were proposed in this pull request?
On running LocalCheckpointSuite repeatedly 3-4 times, following test fails:
Collect should have failed if local checkpoint block is removed... (LocalCheckpointSuite.scala:173)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.Assertions$class.newAssertionFailedException(Assertions.scala:495)

One such instance at jenkins https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61354/consoleFull
This test is flaky because, there is a time delay between remove block is requested
at BlockManagerMasterEndpoint.scala:229 and it actually get's removed at slave.
One drawback of the change is time required to run the test will increase.
How was this patch tested?
Existing tests.

Test build #61376 has started for PR 13943 at commit a7f2f11.

Test build #61376 has finished for PR 13943 at commit a7f2f11.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61376/
Test FAILed.

Merged build finished. Test FAILed.


Error on install, UBUNTU 16 LTS

Errors

after pip install pdfminer.six ... 100% ... bit fineshed with permission error,

Successfully built pdfminer.six
Installing collected packages: pdfminer.six
Exception:
Traceback (most recent call last):
  File "/home/user/.local/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
.....
OSError: [Errno 13] Permission ... '/usr/local/lib/python2.7/dist-packages/pdfminer'

next repeting with sudo, sudo pip install pdfminer.six resulted in

The directory '/home/user/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/user/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Collecting pdfminer.six
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages (from pdfminer.six)
Requirement already satisfied: pycrypto in /usr/lib/python2.7/dist-packages (from pdfminer.six)
Installing collected packages: pdfminer.six
Successfully installed pdfminer.six-20170419

but, no way to call it
pdf2txt.py myFile.pdf produced error "/usr/bin/env: “python\r”: not found"

Did you try sudo's -H flag

Got the same error on mac.

Duplicate of #27

@jeeftor - Your solution

Closing this as it is a duplicate of #27
@ppKrauss, feel free to reopen if I am wrong.


Refactor TuningJobState and BaseSearcher to use trial_id instead of c…

…onfig
Issue #, if available:
Description of changes:
This is cleaning up searcher code to use trial_id, instead of identifying trials by their configs. The latter lead to all sorts of problems. With this change, we could also allow two trials to have the same config.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi Matthias,
Thanks for proposing those changes. The PR is very long and will be hard to review as it is.
It seems to be doing also several things at once that are independent (trial-id, warmstart, blackbox, support of batch suggest).
Can we split it and send one PR per topic? This would make the review process more efficient.
Thanks

I'll reopen this in 3 parts


Can you provide dependency injection components?

As the title

e.g. Java Spring DI

You can refer to https://www.cloudwego.io/zh/docs/hertz/tutorials/framework-exten/


Cool moving effect.

The text will move from left to right .

@Darshan-SD Please assign me this issue under hacktoberfest.

Can you elaborate more on the effect? Moving the text from left to right can be implemented easily, and it does not require creating standalone snippets.


Create .travis.yml

this closes #189

@vgrichina is there some easy way to ignore certain patterns of URL?
here's an example (there are a several) that is a valid use of a URL which is not available at time of validating the docs for CI
Getting links from: http://localhost:3000/docs/development/near-clitool
├───OK─── https://www.npmjs.com/get-npm
├───OK─── https://nodejs.org/en/download
├─BROKEN─ http://localhost:3030/ (ERRNO_ECONNREFUSED)
Finished! 95 links found. 92 excluded. 1 broken.

i guess we can just add this and make sure all dev links match the pattern
npx broken-link-checker -gro -exclude "localhost:3030" http://localhost:3000


[Service Bus] Improve implementation of sender

For more context refer to #6903
Used issue https://github.com/Azure/azure-sdk-for-js/issues/3375 for reference on changes to make.
Included a test case as well.

Closing this PR as it is superseded by #7369


WIP: include "hasChildren" field in a work item's "children" relationship

In order for the planner to render an expander symbol, it needs to know if a work item has any children. I've create a SELECT EXISTS... query for this because we don't need to fetch or count all children for this task.
These work item actions will include the hasChildren meta information:

list,
show,
update,
reorder
list children, and
create

@xcoulon tests are in the making, hence the WIP prefix.

ok, great! I just wanted to make sure there would be new tests to cover this feature ;)


Empty reply from server in python 3.6.1 on flask with Content-Type: application/json

I'm getting "Empty reply from server" using python 3.6.1 and flask 0.12 with raven 6.1.0 and blinker 1.3 whe n using the header "Content-Type: application/json". Working ok without the header or without the import of from raven.contrib.flask import Sentry

Do you have a stacktrace or anything else to go with this coming from the server? Usually this happens as a side effect of the WSGI server crashing or erroring.

Sorry I just forgot to tell that I'm using gunicorn==19.7.1, and there's no stacktrace or even warning message, it appears that gunicorn doesn't receive the petition. What seems very interesting is that in python 3.5 it works.


bad request when accessing cloud code using javascript sdk

cloud code working well if i'm using rest api but its failed when i'm using javascript sdk and it's return 400 (bad request).
this is my cloud code:
Parse.Cloud.define("testing", function(request, response) {     response.success("It works!"); });
and this is my rest api request:
curl -X POST \ -H "X-Parse-Application-Id: ${mysecretestring}" \ -H "Content-Type: application/json" \ https://myhosting.herokuapp.com/parse/functions/testing
and this is my javascript code:
Parse.Cloud.run('testing').then(function(r) {      console.log(r); });
this is error message:
POST https://myhosting.herokuapp.com/parse/functions/testing 400 (Bad Request)
so, what's wrong with that code?
thank you

Same error

Thanks for your question!
We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it.
You may also use Server Fault for questions about managing your own servers.


feat: GHE support for Go releases

Fixes #664

I separated some of the logic into helper functions, for docs, should I be changing any of the md files like the README? I wasn't sure if that was autogenerated by CI or something, but I can add some notes there. I think one thing that may need to be called out maybe as a warning or something is that if someone was running a go release with publib in something that's not GHA, they'd need the GITHUB_API_URL defined since that's how the logic would detect if the env is either public GitHub or GHE, and that's a default env var that's present in a GHA workflow.

Hadn't had time to look at the updated code yet, but I can answer the question.

For docs, should I be changing any of the md files like the README? I added docstrings to the helper functions but wasn't sure if the README/other doc files were autogenerated by CI or something, but I can add some notes there if it's not.

Yes, please update the goland section here: https://github.com/cdklabs/publib?tab=readme-ov-file#golang
Especially the env var table.

I think one thing that may need to be called out maybe as a warning or something is that if someone was running a go release with publib in something that's not GHA, they'd need the GITHUB_API_URL defined since that's how the logic would detect if the env is either public GitHub or GHE, and that's a default env var that's present in a GHA workflow.

We can support both GITHUB_API_URL and GH_HOST (from the CLI conventions). But definitely needs to be called out in the docs.

Added some extra documentation to the README!

Hadn't had time to look at the updated code yet, but I can answer the question.

For docs, should I be changing any of the md files like the README? I added docstrings to the helper functions but wasn't sure if the README/other doc files were autogenerated by CI or something, but I can add some notes there if it's not.

Yes, please update the goland section here: https://github.com/cdklabs/publib?tab=readme-ov-file#golang Especially the env var table.

I think one thing that may need to be called out maybe as a warning or something is that if someone was running a go release with publib in something that's not GHA, they'd need the GITHUB_API_URL defined since that's how the logic would detect if the env is either public GitHub or GHE, and that's a default env var that's present in a GHA workflow.

We can support both GITHUB_API_URL and GH_HOST (from the CLI conventions). But definitely needs to be called out in the docs.


Broken URL for south_ayrshire

Broken URL: #'https://opendata.arcgis.com/api/v3/search?catalog[groupIds]=any(436655c931664e279f675390213d828e)

Automatically closed due to URL now working.


Implement Frontend basic validation on the user input, such as the username cannot be empty. Password cannot be empty.

c3a1503


Add flist archiver argument forwarder and improve hashing

there will be a new flist implementation based on a key value stor, don't put too much time in this one


ERROR: Unable to extract uploader id

youtube-dl --verbose https://www.youtube.com/watch?v=aN28k-OC8Rw
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=aN28k-OC8Rw']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.7.3 (CPython) - Linux-5.4.0-139-generic-x86_64-with-debian-buster-sid
[debug] exe versions: ffmpeg 3.4.11, ffprobe 3.4.11
[debug] Proxy map: {}
[youtube] aN28k-OC8Rw: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/davysouthernboy/anaconda3/lib/python3.7/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/home/davysouthernboy/anaconda3/lib/python3.7/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/home/davysouthernboy/anaconda3/lib/python3.7/site-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/home/davysouthernboy/anaconda3/lib/python3.7/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
    'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
  File "/home/davysouthernboy/anaconda3/lib/python3.7/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

#30839.


adding HA queue mirroring option

Closing this due to inactivity. Feel free to reopen to add this defined type to wrap around the new rabbitmq_policy type.


fix: catch expected runtime exception when race condition of cookie...

… updates

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

During portlet cookie processing, there is a known potential for a race-condition where more than one portlet thread is updating the user's portlet cookie. The code previously caught the optimistic locking exception and continued. The exception was changed in Spring/Hibernate but the uPortal code was not updated. This caused failed pages (uncaught runtime exception) on occasion.

Planning to cut a release once this is approved & merged.


cpp-ethereum: fix description metadata

I noticed some of the metadata wasn't showing up, and figured I'd send a PR to
fix it.

Thank you


Create a getting started guide

Blocked on #83.
Related to #82.
Related to #80.
AC:

Create a use case-based getting started guide in the README or linked from the README
Use case: Searching an APM application entity by name, retrieving its application ID, and adding an entity tag to it

Resolved by #103 .


[CLOUDGA-18204] Add support for db-audit (update and remove)

Summary:
This PR add support for 2 operations of DB-audit: update a DB audit config applied on a cluster and remove a config entirely from a cluster.
Test Plan:
Manually tested the operations, working as expected. Added UTs
CLI logs/usage ---
rkumar@dev-server-rkumar-31 ybm-cli]$ ./ybm db-audit-logs-exporter unassign --cluster-id=98096a41-9bf6-4421-a9fc-274df53eb9d4 --export-config-id=60dc5a8d-d89c-49bd-abe0-ee2b6ab16149
A newer version is available. Please upgrade to the latest version v0.1.18
? Are you sure you want to unassign DB audit config: 60dc5a8d-d89c-49bd-abe0-ee2b6ab16149 Yes
Deleting Db Audit Logs Exporter Config 60dc5a8d-d89c-49bd-abe0-ee2b6ab16149

[rkumar@dev-server-rkumar-31 ybm-cli]$ ./ybm db-audit-logs-exporter update --cluster-id=a37b4f18-7f55-4a7a-846a-ae8361b5ea7d --export-config-id=77e53e0d-b6c3-4c04-ab3c-1c5a6cc213b6 --ysql-config=log_catalog=true,log_client=false,log_level=INFO,log_parameter=true --statement_classes=READ,WRITE --telemetry-provider-id=538a8302-35b0-432f-9860-630955d98a8e
A newer version is available. Please upgrade to the latest version v0.1.18
The db audit exporter config 77e53e0d-b6c3-4c04-ab3c-1c5a6cc213b6 is being updated
ID                                     Date Created               Cluster ID                             Telemetry Provider ID                  State     Ysql Config
77e53e0d-b6c3-4c04-ab3c-1c5a6cc213b6   2024-02-27T06:30:51.304Z   a37b4f18-7f55-4a7a-846a-ae8361b5ea7d   538a8302-35b0-432f-9860-630955d98a8e   ACTIVE    {"log_settings":{"log_catalog":true,"log_client":false,"log_level":"INFO","log_parameter":true,"log_relation":true,"log_statement_once":false},"statement_classes":["WRITE","READ"]}

Honestly, this is a bit outside of this PR but the function setDbAuditLogsExporterSpec is quite bad, there absolutely no validation been done, plus how the user can know all the field for the ysql config, you only give two log_catalog=<boolean>,log_level=<LOG_LEVEL> ?
	log_catalog := ysqlConfigMap["log_catalog"]
	log_client := ysqlConfigMap["log_client"]
	log_level := ysqlConfigMap["log_level"]
	log_parameter := ysqlConfigMap["log_parameter"]
	log_relation := ysqlConfigMap["log_relation"]
	log_statement_once := ysqlConfigMap["log_statement_once"]

@shinji62 added validations on all these fields and made ysql-config more descriptive.
We have the same validations and error handling present in ybm backend

Honestly, this is a bit outside of this PR but the function setDbAuditLogsExporterSpec is quite bad, there absolutely no validation been done, plus how the user can know all the field for the ysql config, you only give two log_catalog=<boolean>,log_level=<LOG_LEVEL> ?
	log_catalog := ysqlConfigMap["log_catalog"]
	log_client := ysqlConfigMap["log_client"]
	log_level := ysqlConfigMap["log_level"]
	log_parameter := ysqlConfigMap["log_parameter"]
	log_relation := ysqlConfigMap["log_relation"]
	log_statement_once := ysqlConfigMap["log_statement_once"]

@shinji62 added validations on all these fields and made ysql-config more descriptive. We have the same validations and error handling present in ybm backend

Why do we have to duplicate the validations? Validations in apiserver code and ones over here will get ot of sync.

Honestly, this is a bit outside of this PR but the function setDbAuditLogsExporterSpec is quite bad, there absolutely no validation been done, plus how the user can know all the field for the ysql config, you only give two log_catalog=<boolean>,log_level=<LOG_LEVEL> ?
	log_catalog := ysqlConfigMap["log_catalog"]
	log_client := ysqlConfigMap["log_client"]
	log_level := ysqlConfigMap["log_level"]
	log_parameter := ysqlConfigMap["log_parameter"]
	log_relation := ysqlConfigMap["log_relation"]
	log_statement_once := ysqlConfigMap["log_statement_once"]

@shinji62 added validations on all these fields and made ysql-config more descriptive. We have the same validations and error handling present in ybm backend

Why do we have to duplicate the validations? Validations in apiserver code and ones over here will get out of sync.

@jagdish-yb Well I think the CLI should do some validation as well, if some field are expected or not, trial and error from user is not a good experience, plus no need to call the API if we know that something. is mandatory or not

I am ok an apiserver client like UI/CLI adding a layer of validations, but in case of CLI, I feel we may not always keep it up-to-date with apiserver/ui.

@shinji62 is this good to merge?


User Research: Viewer Round 1 (week of 13 May)

[x] Popup research
[x] Prototype
[x] Script
[x] Analysis
[ ] Recommendations

@hthair @Heesoomoon Is this still needed?


Request user consent to get a refresh token

That's not explicitly stated in the Google OAuth 2.0 documentation but getting a refresh token requires the user's consent.
Without this change, the token stored into the keyring by googlephotos-uploader-go-api looks like:
# keyring get googlephotos-uploader-go-api<EMAIL_ADDRESS>{"access_token":"ya29.******-Va67Ye2i6TPX_eCo5awriw_Q","token_type":"Bearer","expiry":"2019-06-13T01:42:33.895720618+02:00"}

With this change:
# keyring get googlephotos-uploader-go-api<EMAIL_ADDRESS>{"access_token":"ya29.******-ImE5lpTrzF8FhSBqktvxtWi","token_type":"Bearer","refresh_token":"1/vyd******RRDE","expiry":"2019-06-13T02:35:01.967502755+02:00"}

This allows gphotos-uploader-cli to automatically retrieve a new access token without any browser.
Maybe this can be made into an option if this is not always desired.

This should avoid the issue reported in https://github.com/nmrshll/google-photos-api-client-go/issues/5 were the underlying error is:
Caused by: Post https://photoslibrary.googleapis.com/v1/mediaItems:batchCreate?alt=json: oauth2: token expired and refresh token is not set

Hi @pacoorozco,
could you check this small PR that avoids opening new browser tabs all the time?
Also, do you think this should be made into an option if for some not yet identified reason this may not always desired?
PS: sorry to bother you directly, it's just that I've noticed you were very active these times on the gphotos-uploader-cli repo.

Note: combined with https://github.com/nmrshll/gphotos-uploader-cli/pull/63/commits/12c07054aba6e1ba9b428c4bd9b2f0120ba6f98e that's a killer feature.

I'd love that too. I'm uploading a large gallery with a low upload speed, my token expire all the time and i need to start again and reauth...

I'm still getting "panic: interface conversion: error is *url.Error, not *googleapi.Error" I also have a relatively slow connection and relatively large photo collections I try to upload. If this is a fix, that would be great. Is there something blocking this from being merged? If so, can I help in unblocking it?

This project is not followed here anymore, please take a look to https://github.com/gphotosuploader/gphotos-uploader-cli


Value field in tooltip doesn't respect units and decimals

Values in drill-down from cells are ignoring format in an used pattern.

Thanks for notifying this. Current master branch is having the fix. This will be part of 0.6.0 release


The list feature in the web interface doesn't appear to work

Fresh install (two days old) out of git.
Running a single domain works as expected, however using the 'list' part of the web interface to start a scan causes several issues:

if you put more than one domain, the modal for the input goes away as though it's started a job but nothing happens and no scans are performed
if you put no domains in, you get very verbose error messages (probably not great for publicly accessible instances)
if you put a single domain into the list feature, it seems to work

I spent some time trying to figure out if the list needed to be in a specific format, like all domains on new lines, or separated by spaces, or commas, but nothing I tried worked.

Hello @Viss, how are you?!!
Thank you very much for getting in touch! This feature is still in development. As we know that users are in need of it, we will change our priority and focus on the add list functionality.
If all goes well, we will perform the upload to /dev/ this week.

Hi!
that's awesome news! ill keep an eye out!
On June 19, 2023 7:27:25 AM PDT, "悲しいオオカミ" @.***> wrote:

Hello @Viss, how are you?!!
Thank you very much for getting in touch! This feature is still in development. As we know that users are in need of it, we will change our priority and focus on the add list functionality.
If all goes well, we will perform the upload to /dev/ this week.
--
Reply to this email directly or view it on GitHub:
https://github.com/six2dez/reconftw/issues/728#issuecomment-1597289840
You are receiving this because you were mentioned.
Message ID: @.***>

Web server will not be maintained nor deployed with reconftw anymore


Improve mapping for apps that are effectively in 'crashed' state

The default retry attempts for
case "CRASHED":
  return DeploymentState.failed;

is very long, certainly more than 3 hrs and heard it maybe weeks, so it is really never reached in practice for a dataflow deployment.  We should introduce our own logic to keep track of how many deployment attempts were made and then decide to fail the deployment state after our own threshold is reached.  This is done in the kubernetes deployer.

I lean towards a time-based duration instead of pure counts.

Fixed by https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry/commit/a3696a4077ebcae0fcfc6f791d19b66786ab6807


FLAX 0.6.0 has removed 'optim' module

Hi, I was trying to run a training process with MTV on a custom dataset. When executing the code, I got the following error:
ImportError: cannot import name 'optim' from 'flax'
I have been researching on my own a little bit and, according to this issue in FLAX package, they have removed flax.optim in FLAX 0.6.0. I had to downgrade to FLAX 0.5.3 for solving this error.

Hi, I was trying to run a training process with MTV on a custom dataset. When executing the code, I got the following error:
ImportError: cannot import name 'optim' from 'flax'
I have been researching on my own a little bit and, according to this issue in FLAX package, they have removed flax.optim in FLAX 0.6.0. I had to downgrade to FLAX 0.5.3 for solving this error.

Thanks to you, I was able to install the essential modules!


fix build failed on aarch64

since linux has drop __NR_open on aarch64, we will get build
failed on aarch64 without __NR_open defined.
Signed-off-by: Chunmei Xu<EMAIL_ADDRESS>
Checklist

[ ] Language changes are updated in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Looks good to me. Can you fix the clang format, though?

Looks good to me. Can you fix the clang format, though?

Done.

Thanks :)


Supplementary contract interface documentation

Supplementary contract interface documentation
Documents are required to be beautiful and easy to understand, and should be completed in English.
You can refer to the excuse description of ERC20
https://docs.openzeppelin.com/contracts/2.x/api/token/erc20

I wrote a new demo here
https://github.com/treasurenetprotocol/treasurenet-contracts/tree/main/docs/treasure/oil/producer
https://github.com/treasurenetprotocol/treasurenet-contracts/tree/main/docs/treasure/oil/data
No need to refer to ERC20 documentation anymore

I've completed the task to document the supplementary contract interfaces. The documentation is now available in English.


chore(main): release 0.31.1

:robot: I have created a release beep boop
0.31.1 (2023-06-15)
Miscellaneous

Remove console.log & fix erorr in dev mode (#334) (8a1d695)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-frontend/releases/tag/0.31.1 :sunflower:


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
Fixed URLs
Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

[ ] http://www.apache.org/licenses/ with 1 occurrences migrated to:
https://www.apache.org/licenses/ (https result 200).
[ ] http://www.apache.org/licenses/LICENSE-2.0 with 112 occurrences migrated to:
https://www.apache.org/licenses/LICENSE-2.0 (https result 200).

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: spring-operator sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


fix AcquGeometr for multichannels

Fix order of geometry label
Add ADMM

Added ADMM (linearized version) equivalent to PDHG.
Tested for denoising

Currently this build fails on Jenkins. Of the 3 problems the FAIL is more worrisome.
======================================================================
ERROR: test_ADMM_linearized (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_ADMM_linearized
Traceback (most recent call last):
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.6/unittest/loader.py", line 428, in _find_test_path
    module = self._get_module_from_name(name)
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.6/unittest/loader.py", line 369, in _get_module_from_name
    __import__(name)
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/test_tmp/ccpi/Wrappers/Python/test/test_ADMM_linearized.py", line 47, in <module>
    which_noise = int(sys.argv[1])
ValueError: invalid literal for int() with base 10: 'discover'

======================================================================
ERROR: test_ADMM_linearized_tomo (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_ADMM_linearized_tomo
Traceback (most recent call last):
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.6/unittest/loader.py", line 428, in _find_test_path
    module = self._get_module_from_name(name)
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.6/unittest/loader.py", line 369, in _get_module_from_name
    __import__(name)
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/test_tmp/ccpi/Wrappers/Python/test/test_ADMM_linearized_tomo.py", line 51, in <module>
    from ccpi.astra.operators import AstraProjectorSimple
ModuleNotFoundError: No module named 'ccpi.astra'

======================================================================
FAIL: test_AcquisitionGeometry_allocate (test_DataContainer.TestDataContainer)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/conda-bld/ccpi-framework_1567254695710/test_tmp/ccpi/Wrappers/Python/test/test_DataContainer.py", line 589, in test_AcquisitionGeometry_allocate
    self.assertEqual(default_order[1], sino.dimension_labels[1])
AssertionError: 'angle' != 'vertical'
- angle
+ vertical

----------------------------------------------------------------------
Ran 63 tests in 276.419s

FAILED (failures=1, errors=2)

Well I am not sure why there is a problem with the ccpi.astra import, but the 3rd fail is because I change the order of output for the 3D case
https://github.com/vais-ral/CCPi-Framework/pull/363/files#diff-1dac79a6e3d1c54b8dabcf986ef52a28L282
so either we have astra as default, which generates 3D sinograms as (vertical, angle, horizontal)
or leave it as it was before (angles, vertical, horizontal) and change axis before doing direct/adjoint, which will cost


Routes configuration during runtime

I have AngularJS app which builds it's UI according to API input data . All information about routes are inside my input data so I can't configure routes after/during building UI. I need a possibility to configure routes after/during UI building.

You can hang onto the $stateProvider and register states on the fly.  If you fetch all the states before synchronizing with the URL, it's pretty easy.  If you want to register after the user logs in, for instance, there are some more subtle nuances that may cause difficulty.
Easy mode:
var stateProvider
app.config($stateProvider, $urlRouterProvider) {
  stateProvider = $stateProvider;
  $urlRouter.deferIntercept(); // Dont sync the URL yet
}

app.run(($http, $urlRouter) => {
  // get routes, then register them with the state provider
  $http.get('states.json').then(resp => resp.data.forEach(state => stateProvider.state(state)));
  // tell ui-router to sync the url and listen for changes
  $urlRouter.listen();
  $urlRouter.sync();
})

See also: https://christopherthielen.github.io/ui-router-extras/#/future

Closing. this is on the radar, and I've provided a workaround
See also #2739 #2711 #146


Elaborate on PPX hooks and composition.

Note also the stylistic change of "Abstract Syntax Tree" in the extended
paragraph.

This is awesome! Thank you!


Revert libc upgrade

Despite manual updates to staging libc, I see that there are no logs from all instances approx. after the initial libc PR bump merge:

Reverting those changes to see if that helps.

Apparently, the logs missing were caused by something else but malfunctioning libc, physically the logs are still present on envs:


docs: update configuration kick in tips

fixes: https://github.com/envoyproxy/gateway/issues/4471
xref: https://github.com/envoyproxy/gateway/pull/4451

preview:


CASMINST-4054: Move check-static-routes test to suites run after CSM deployment

Summary and Scope
The check-static-routes test was in two test suites (ncn-kubernetes-tests-worker and ncn-storage-tests) which are executed during CSM installs before CSM is deployed. This was causing it to fail, as it should not be run that early. This PR moves it to ncn-healthcheck-storage and ncn-healthcheck-worker, which are not run until the regular CSM health validation procedure.
I also added a small comment to the two suites from which I removed it, noting that they are run before CSM services are deployed (to help avoid this type of issue in the future).
Issues and Related PRs
Resolves https://jira-pro.its.hpecorp.net:8443/browse/CASMINST-4054
Testing
I will test the new csm-testing RPM on my current install of surtur. I will update this section once I have done so.
Risks and Mitigations
Very low risk -- the test itself is unchanged. It is only being called from different test suites.
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[N/A] Copyrights updated
[X] License file intact
[X] Target branch correct
[N/A] CHANGELOG.md updated
[TBA] Testing is appropriate and complete, if applicable
[N/A] HPC Product Announcement prepared, if applicable

Rebased since I see Brad made a PR into the 1.2 branch today


add Institut polytechnique de Paris

add IPP Paris:
Name: Institut polytechnique de Paris (IP Paris)
Web: https://www.ip-paris.fr/en
Address: 5 Av. Le Chatelier 2ème étage, 91764 Palaiseau, France
Phone: +33 1 69 33 33 33

@quanPhamvan First stage of verification passed, official domain is ip-paris.fr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@quanPhamvan Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fairlight audio variables

Would be nice to have variables with different audio-levels(per source, master, headset volume etc), at least now with the StreamDeck +, so I can have one knob to adjust a volume of a source or the master, and I can see the volume level on the button above.

handled by #200


Complete - ready for PR

In preparing associative relationship edit dialog, wait until after the
associative class candidate list has been sorted before trying to set an
existing associative class as the default selection.

See comment here: https://github.com/xtuml/bridgepoint/pull/823#issuecomment-1190177333


Tab scroll button inconsistently clipped

Originally posted by @simonratner in microsoft/terminal#7313.
Environment
Windows build number: Microsoft Windows [Version 10.0.19041.450]
Windows Terminal version (if applicable): Windows Terminal Preview [Version: 1.2.2022.0]

Display scale: 125%.

Steps to reproduce
Open more tabs than fit horizontally across the window, and observe the tab scroll buttons.
Expected behavior
Tab scroll buttons consistent in size and style to other buttons in the tab/title bar (new tab, dropdown, min/max/close), and aligned to the same baseline
Actual behavior
Tab scroll buttons differ in style and alignment from all other buttons, and the icon within the scroll-right button appears clipped.

similar to #1650

I would like to take a look at this.

Awesome, thank you!


Migrate to nextjs in order to utilise SSE

Is your feature request related to a problem? Please describe.
I'm always frustrated when our website is not frequently crawled by Google
Describe the solution you'd like
Migrate to nextjs and utilise SSR.
Additional context
This is a big project

@shanonjackson I believe was 50% there with the migration 🙏


ROX-22816: Fix issues with port bind in unit tests

Description
There are two problems that this PR is trying to address:

we have extensive reusing of the same port across multiple tests
we are not closing connections cleanly in our tests

After some investigation, the conclusion is that the FIN_WAIT state is piled because of the not properly closed connection on the client side. This should be improved with this PR.
Another problem that is not 100% clear is the FIN_WAIT state requires the server to be alive. It can be that it's hard to reproduce such a case manually, and it's happening with a big load during unit tests. To reduce high port reuse and potential collision, a new method has been added to this PR to get a free port. This should reduce port number "overload".
User-facing documentation

[x] CHANGELOG is updated OR update is not needed
[x] documentation PR is created and is linked above OR is not needed

Testing and quality

[x] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[x] modified existing tests

How I validated my change
Local unit tests executed.
I also tested on a dedicated Linux machine, where I was able to reproduce and test the amount of FIN_WAIT states generated by the test run.
Here is a helpful article with some scripts on how to reproduce such a state: https://blog.cloudflare.com/this-is-strictly-a-violation-of-the-tcp-specification/

I did a similar approach but I checked the port availability by reading socket info in /proc/net/tcp and /proc/net/tcp6. This way we can avoid opening a port and freeing it to check availability. WDYT?


add travis ci

add travis ci fo this repository.

cc @sids-b

LGTM overall. Please update the README, then we can merge this PR.
For docker images support, we can do it in another PR.

Done, Thanks @m1093782566 @sids-b


cmd/compile: cannot use generic type without instantiation

What version of Go are you using (go version)?

$ go version
go version go1.21.0 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/septemlee/Library/Caches/go-build'
GOENV='/Users/septemlee/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/septemlee/.gvm/pkgsets/go1.21.0/global/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/septemlee/.gvm/pkgsets/go1.21.0/global'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/septemlee/.gvm/gos/go1.21.0'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/septemlee/.gvm/gos/go1.21.0/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='go1.21.0'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/1t/2fzzpms929v28gr7b0mdqcrr0000gn/T/go-build1855045304=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?
I expected that I don't need infer type here after #59338 and #58650 be implemented.
https://go.dev/play/p/EFLOb5SmpYe

What did you expect to see?
Compiling succeed. And it would print out value 3 on screen.
What did you see instead?
cannot use generic type FnArg2 without instantiation

I guess it might related to #50285 ?

CC @golang/compiler

Type inference only applies to generic functions. Generic types always require explicit type arguments.
/cc @griesemer @ianlancetaylor

Thanks for @mdempsky response. This thing is even more relevant to #61731


ENH: New mode for plot_dipole_locations

Would other people find it useful if I adapted some plotting code from https://www.sciencedirect.com/science/article/pii/S221315822100022X?via%3Dihub to produce plots like this?

It could be a new mode for plot_dipole_locations for example. I find it a bit more readable than the 3D one with MRI slices when there are multiple dipoles, e.g., this with multiple becomes harder to see immediately the X/Y/Z relationships I think:

I love it ❤

Message ID: @.***>

@larsoner Cool! How are the slices chosen when there are multiple dipoles?

Makes sense, that would be a great addition!


WIP: The great split

So in the past, this project had to deal with various size related issues, e.g. in the very first version I was running with all features enabled and quickly realized that my computer does not have enough memory. I solved this by running commands like cargo check in a loop against each feature individually instead of running against the entire project with all features enabled. This worked for a while, however once more and more custom resources were added and thus the number of features grew as well, we ran into a limit of crates.io which only allows 300 features per crate nowadays. Originally, each version in each custom resource group had its own feature, which was changed so that each group is mapped to one feature and each version in that group is one module. Additionally, I contacted the crates.io team to increase the feature limit for this project, so that I can continue to grow past 300 custom resource groups. Lately, we are running into the 10 MiB per crate size limit of crates.io. Again, I contacted the crates.io who again were very helpful and quickly increased the size limit. However, both the feature and size limits will be reached again eventually since the Kubernetes community is very active and creates more and more custom resources all the time.
The idea here is to come up with a solution to allow this project to grow indefinitely. The rather simple idea in this PR is to split all custom resource groups into their own crate. Each version within a group continues to be a module within that crate. Since each group typically only contains a handful of resources, I do not see any size related problems happening in the future (although it's possible in theory..). Each crate will be versioned and released individually and the release schedules are spread across an entire day, so that we won't hammer the crates.io API with hundreds of crates at the same time.
Open questions:

Should we introduce the feature-per-version from the original version of this project again? I think this can help users, since groups often expose the same custom resource in various versions but users are typically only using one version. By introducing features, users can make sure that they will only ever use the version they want to use and not accidentally use something else.
Is the crates.io team ok with this? We would be releasing 400+ crates and that number will only ever go up. Beside the high number of crates and the potential API bottleneck, I'm concerned about name squatting since crates.io does not have a namespace/group concept. My idea here is to prefix each crate with something that does not exist yet in crates.io and hope for the best :shrug: (the current implementation uses the kcr_ prefix which stands for kube-custom-resource). The crates.io team have asked me in the past to limit the number of releases since the high number of features in the original crate causes too much strain in their API.

Feedback highly welcomed here. I'm pinging @w3irdrobot, @waynr, @banool, @brendanhay and @orf since you guys either pushed changes in this repo or somehow interacted with it in the past and I'm assuming you are using this project. Likewise, @clux since he created kopium and maintains kube-rs. I'm going to contact the crates.io team by mail since I don't not know any of their usernames on GitHub (feel free to ping them here if you do?)
Ignore the build failures - this is WIP. If you want to see what this currently looks like open https://github.com/metio/kube-custom-resources-rs/tree/split since the diff view in this PR will be completely useless :sweat_smile:

Last comment/idea, sorry for the spam!
Rather than version/release each crate individually and per resource, we could group them by namespace instead?
I.e rather than have ~40ish *_k8s_aws crates, we could have a single crate for k8s_aws with all resources inside?
From a UX point of view, you're more likely to use CRDs in these "groups", so you probably want all of the AWS resources available to you.
This could be grouped by the last two parts of the CRD? So sqs.services.k8s.aws would become k8s.aws?
But maybe this isn't always safe, idk.

Thanks for the feedback - I'll adjust the workspace related stuff as per your comment in my next push :heart:
Wrt. releasing crates: I'm not sure if that will be an issue but I don't want to be a bad citizen on crates.io so spreading releases out a bit won't hurt? My current implementation just calculates the hash of the group name and then mods them with 24 and 60 to get hours and minutes.
I like the idea of grouping crates even further to reduce the total number of crates! Not sure if we can use the last two segments of their group though, e.g. https://github.com/metio/kube-custom-resources-rs/tree/split/crd-catalog/aws sometimes uses amazon.com or k8s.aws and even some special cases like karpenter.sh. I thought about using the GitHub/GitLab organization name to group crates (e.g. just aws for the previous example), however there are some special cases like https://github.com/metio/kube-custom-resources-rs/tree/split/crd-catalog/aws-controllers-k8s which should probably belong to the aws group as well or https://github.com/metio/kube-custom-resources-rs/tree/split/crd-catalog/apache which contains resources for multiple disjointed projects and it might be weird to group them together? That said, the crd-catalog is manually maintained anyway, so manually grouping the aws and aws-controllers-k8s orgs into aws isn't really a showstopper. Likewise, we can manually split the apache org into their individual projects.
If we go down this road, how would this work with features though? Would we have one feature for each version in each group in each project? Using https://github.com/metio/kube-custom-resources-rs/tree/split/crd-catalog/aws/amazon-cloudwatch-agent-operator/cloudwatch.aws.amazon.com/v1alpha1 as an example, would we have a feature called cloudwatch_aws_amazon_com_v1alpha1 in the aws crate? Should we add cloudwatch_aws_amazon_com as well in case someone wants to enable all versions of that group at once?

Hmm, on second thought perhaps it's best to not group them. It would work for larger groups of packages, but for smaller ones it would be confusing to add a package then enable a feature with the same name?
It would also increase update churn - you're not going to be sure your specific CRDs are updated when you update a package, whereas with a single package per CRD you can be?

Hey! I think this is a good idea also. Less mega crates that does everything. Everywhere I go I end up inlining kopium output into some vendor-equivalent directory, and this would help with that. Group names make sense to me, provided you don't run into some crate name length limit.
My expectation on load is that given how you've set it up (only publish when there are commits touching the directory), it'll likely end being less load altogether on crates.io as there will be less stuff released, but maybe there's some common overhead you incur. Definitely see much bigger offenders in the crates ecosystem in the build queue every now and then though (like repos releasing 100+ crates at every update unconditionally; those seem to get downprioritised in the queue).
Maybe the calendar versioning (masquerading as semver) that you inject with sed should be avoided in favor of something like cargo-release or cargo-workspaces with a blanket minor release - if it's easy to install in ci via something like the taik-e/release-action. It's not like the numbers are going to be super meaningful either way, but people do write github action logic around auto-merging based on whether or not something is a major version, and this would make "one major every year" rather meaninglessly.

Hey all - thanks for the feedback & sorry for the delay here. I was busy moving to another city and life I guess :shrug:
I agree with the package/feature name duplication. It doesn't really feel right using this, so I've switched back to one crate per custom resource group and one feature for each version within that group. I've added a default feature as well which enables all versions because the crates.io UI has this quick copy&paste box that does not contain any features. My thinking here was that people should be good to go by just pasting the string they got from crates.io into their project while still allowing them to fine-tune the enabled features later.
The crate length limit should be fine (at least right now). The maximum is 64 chars and we are at 43 with the kcr_ prefix.
@clux can you clarify what a version number would look like in your idea? Would we always increment the major version and set minor/path to 0? So like going from 1.0.0 to 2.0.0 to 3.0.0 on each release? My original idea behind the calendar based versioning was to give some meaning to the version number since users can quickly see how old their CRDs are. However, I agree that the current versioning scheme has no meaning for auto-merging workflows that expect semver based behavior.
I've replaced the sed call with cargo set-version  which seems to work fine. cargo-release won't work I think because I'm changing the version number on the fly and thus do not have a clean working tree to release from. That said, I'm not that familiar with cargo-release so maybe I have to replace larger parts of the current release process to make it work?Likewise, the current setup uses a release pipeline for each crate and therefore cargo-workspaces seems like the wrong tool to use, but maybe the release process could be changed to integrate better with cargo-workspaces as well?
About releasing: How about we do not release to crates.io at all and instead tell users to declare a git dependency? I think the advantages are:

zero load on crates.io
no crate name prefix required & no potential name clashes in the future
simplified release process since we just create a new git tag every week or so

Can't really think about strong downsides. Maybe it feels weird because every other crate is fetched from crates.io?

@clux can you clarify what a version number would look like in your idea? Would we always increment the major version and set minor/path to 0? So like going from 1.0.0 to 2.0.0 to 3.0.0 on each release? My original idea behind the calendar based versioning was to give some meaning to the version number since users can quickly see how old their CRDs are. However, I agree that the current versioning scheme has no meaning for auto-merging workflows that expect semver based behavior.

I would imagine making minor releases automatically (1.X++.0), and reserving majors for something unexpected that you actually want people to look at (if it should occur). People can already see how old things are from crates.io last publish or github release/tag dates. To be clear, I like the intention of giving at-a-glance information, but I don't like underming an existing system with existing conventions (semver,  where majors should be looked at) to present it.

How about we do not release to crates.io at all and instead tell users to declare a git dependency?

This does mean people have to whitelist git dependencies in tools such as cargo-deny. It's occasionally a tricky thing to get buy-in for in some security focused organisations because people can (and do) overwrite git history. A crates registry pin is also more permanent (e.g. survives yanks).

Ok thanks for clarifying!

Another major downside of using git dependencies is that you’re unable to publish crates with git dependencies onto crates.io.
Regarding the versioning, I’m of two minds. On one hand, as a user, I did value the date based (calver?]) approach, and I’m also not entirely sure I’d want my CRDs updated “under my feet”, so to speak.
I never experienced this personally, but it seems like it’s possible that existing CRD definitions can change in a way that causes my code to either break or refuse to compile.
And we’re not actually versioning Rust code here, not really, we’re versioning collections of very loosely versioned external “things” that don’t abide by server at all.
This leads to two possible options:

Assume every change is breaking - onus is on the user to update - calver
Do not assume anything about changes - onus is on the user to fix any abrupt breakages - “semver” (but not really)

I’m not sure what is best.

Yeah I think there is no clear best way to version the crates in this repo.
I basically outsourced that problem to the upstream projects in my original design, e.g. if they introduce a breaking change, they would have to increase the version of their CRD which would result in an entirely new rust struct to be generated while still keeping the old struct around. Users would then have a choice to update their code to the latest CRD version or keep using the old one as long as they like. However updating versions of CRDs seems to be mostly done by humans and therefore errors are to be expected. Again I kinda outsourced that problem to upstream projects by just ignoring it in this repo and using calver to have an increasing version number and a simplified release process :grimacing:
Additionally, there is still #289 around which describes a breakage introduced by updating dependencies. I've been toying around with cargo-release, cargo-workspaces and how we could version/release this repo for a bit now and maybe there is at least something we can improve compared to the original design. My proposal is to use 1.X.Y as a version number with X being the output of date --utc +'%Y%m%d' and Y being the output of date --utc +'%-H%M%S'. The resulting version number right now would be 1.20241222.162630. The advantage here is that we can increase the major version for technical reasons, e.g. whenever kube-rs releases a new major version which might help with #289 in the future, the calendar based minor version would still show how old a crate is (although it's a bit harder to read) and using clock based patch version allows us to release multiple times a day if necessary. Users can auto-merge on minor/patch updates and still be notified when something major changes.
The release process would basically stay the same: We spread the publication of crates in the repo throughout a day to combat limits like https://github.com/pksunkara/cargo-workspaces/issues/177 and do not commit versions back into git. Instead all crates get a 0.0.0 version number which will be incremented on the fly with cargo set-version ... before calling cargo publish. No release on GitHub and no git tag for each release.


pkg/fileutil: clean src dir in CopyTree

Otherwise you could end up with truncated file paths.
cc @dgonyeo

Test? :)

Added a test

LFAD.