[Stepper]Circle size and connecting lines between icons are not customizable

I want to customize the size of stepper icon and connecting lines between them but I am unable to achieve it.
Expected results:

Actual results:

[✓] Flutter (Channel stable, 2.10.5, on macOS 12.3.1 21E258 darwin-x64, locale
en-IN)
• Flutter version 2.10.5 at /Volumes/data/development/sdks/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (2 weeks ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[✓] Android toolchain - develop for Android devices (Android SDK version
32.0.0-rc1)
• Android SDK at /Users/akashav/Library/Android/sdk
• Platform android-32, build-tools 32.0.0-rc1
• ANDROID_HOME = /Users/akashav/Library/Android/sdk
• Java binary at: /Applications/Android
Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.10.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.1)
• 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.11+0-b60-7590822)
[✓] VS Code (version 1.66.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.40.0
[✓] Connected device (4 available)
• iPhone SE (2nd generation) (mobile) • 91FF2EA7-7194-4CC1-9456-B3C27165748D
• ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
• iPhone 13 (mobile)                  • 4141610B-4FA4-4F02-828E-E5DFB375989B
• ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
• macOS (desktop)                     • macos
• darwin-x64     • macOS 12.3.1 21E258 darwin-x64
• Chrome (web)                        • chrome
• web-javascript • Google Chrome 100.0.4896.127
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

Hi @aakashawalkar, Have you tried wrapping the Stepper in a theme and changing primary Color and iconsize?
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

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

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: const Center(
          child: MyStatefulWidget(),
        ),
      ),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {
  const MyStatefulWidget({Key? key}) : super(key: key);

  @override
  State<MyStatefulWidget> createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  int _index = 0;

  @override
  Widget build(BuildContext context) {
    return Theme(
      data: Theme.of(context).copyWith(
          colorScheme:
              Theme.of(context).colorScheme.copyWith(primary: Colors.green),
          iconTheme: Theme.of(context).iconTheme.copyWith(size: 32.0)),
      child: Stepper(
        currentStep: _index,
        onStepCancel: () {
          if (_index > 0) {
            setState(() {
              _index -= 1;
            });
          }
        },
        onStepContinue: () {
          if (_index <= 0) {
            setState(() {
              _index += 1;
            });
          }
        },
        onStepTapped: (int index) {
          setState(() {
            _index = index;
          });
        },
        steps: <Step>[
          Step(
            isActive: true,
            title: const Text('Step 1 title'),
            content: Container(
                alignment: Alignment.centerLeft,
                child: const Text('Content for Step 1')),
          ),
          const Step(
            title: Text('Step 2 title'),
            content: Text('Content for Step 2'),
          ),
        ],
      ),
    );
  }
}

Hi @maheshmnj  - Yes, I tried changing size of icon by wrapping Stepper widget into Theme() but it didn't changed size of stepper icon.
Actually, I went to look the code inside the package and I noticed that the icon size is hardcoded to 24.0 and for connecting lines there is predefined margin from start of 12.0 which is also hardcoded.

Thanks for the confirmation @aakashawalkar, I can reproduce the issue the circle size and the lines are not customizable, Labeling this issue as a new feature request.

@HansMuller would it make sense to provide a way to override the kStepSize to allow customization of Circle size and a param to override the default size of line? Happy to raise a PR, if it sounds good.

Has this feature not been added yet?

It's not available yet.. 🥲

@AyushBherwani1998 - sorry, I missed your comment.  The customizations you suggested sound reasonable; happy to review a PR.

@HansMuller no worries, I'll raise PR with the suggested fix.

@AyushBherwani1998 have you raised pull request??

Ah, it skipped from my head. I'll raise it by tomorrow, adding it in my TODOs.

cannot imagine this issue still not resolved.  On tabs this looks crazy...

Tem previsão de quando vão implementar o kStepSize personalizável e o tamanho da barra dos steps personalizável também?

@aakashawalkar Did this PR solve your problem?

Fixed by https://github.com/flutter/flutter/pull/140825


Compatibility with G Suite

Starting February 15, 2021, G Suite accounts will only allow access to apps using OAuth
https://github.com/google/gmail-oauth2-tools/issues/18

@sombatos -- mail-mime-parser only parses raw email (RFC 822 and its successors), it doesn't provide an IMAP/POP/mail retrieval api.  Please reopen if I misunderstood something.


Reduce deserialization allocations/copies

This removes an allocation and a copy in AccountSharedData::reserve(). Calling data_mut().reserve(additional) used to result in two allocs and memcpys: the first to unshare the underlying vector, and the second upon calling reserve since Arc::make_mut clones so it uses capacity == len. With this change we now manually "unshare" allocating with capacity = len + additional, therefore saving on extra alloc and memcpy.
Additionally we skip another extra copy in AccountSharedData::set_data_from_slice(). We used call make_data_mut() from set_data_from_slice() from the days when direct mapping couldn't deal with accounts getting shrunk. That changed in https://github.com/solana-labs/solana/pull/32649 (see the if callee_account.capacity() < min_capacity check in cpi.rs:update_caller_account()). We now don't call make_data_mut() anymore before set_data_from_slice(), saving the cost of a memcpy since set_data_from_slice() overrides the whole account content anyway.
These two changes improve deserialization perf.
Before:

After:

On my mnb node this reduces cost of deserialization from 16% to 5%. It improves overall replay perf by 6%, although I expect the saving to be even larger on nodes with a lot of stake which seem to struggle more with memory allocations.

much like https://github.com/anza-xyz/agave/pull/1192#issuecomment-2099726627, i did similar benmarking. this time, i confirmed this improves favorably unified scheduler performance as well yet again.
before(at 206a87ab5da64eb362f5e40131d8bf9625985c0f)
--block-verification-method blockstore-processor:
ledger processed in 32 seconds, 286 ms
ledger processed in 32 seconds, 470 ms
ledger processed in 32 seconds, 569 ms

--block-verification-method unified-scheduler:
ledger processed in 16 seconds, 847 ms
ledger processed in 17 seconds, 331 ms
ledger processed in 17 seconds, 310 ms

after(at f180b088737fd00d17b0ea342f312e90c5fd4b73)
--block-verification-method blockstore-processor:

ledger processed in 31 seconds, 335 ms
ledger processed in 31 seconds, 164 ms
ledger processed in 31 seconds, 473 ms

--block-verification-method unified-scheduler:

ledger processed in 16 seconds, 512 ms
ledger processed in 16 seconds, 601 ms
ledger processed in 16 seconds, 363 ms

blockstore-processor sees ~1 sec reduction (~3% faster) while unified scheduler sees ~0.8 sec reduction (~5% faster)
Now unified scheduler is basically faster twice. :)


[howdoi] rebind C-j, C-k in org-mode-map

What are you trying to achieve?
I'm trying to remap C-j and C-k globally to evil-window-{down,up} - global mappings worked, but in org-mode they're still mapped to smth else. describe-key for C-j in org file:
C-j runs the command org-forward-heading-same-level (found in org-mode-map),
which is an interactive compiled Lisp function in ‘org.el’.

It is bound to <motion-state> ] h, C-c C-f, C-j, g j, <normal-state> C-j,
<normal-state> g j, <menu-bar> <Org> <Navigate Headings> <Next Same Level>.

What have you tried?
I mapped them globally:
(map!
 (:after evil
   :en "C-h"   #'evil-window-left
   :en "C-j"   #'evil-window-down
   :en "C-k"   #'evil-window-up
   :en "C-l"   #'evil-window-right)
 )

and then locally for org since org-mode-map has other binds:
(map!
   :map org-mode-map
   :n "<C-j>" #'evil-window-down
   :n "<C-k>" #'evil-window-up)

but C-j is still bound to org-forward-heading-same-level. I don't have that map in own config
System information

emacs   version    26.3
        features   XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS GLIB NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD LCMS2
        build      Aug 29, 2019
        buildopts  (--prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-modules 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now)
        windowsys  x
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 8a01ef908 2020-01-20 20:17:43 -0500
        dir        ~/.dotfiles/doomemacs/.doom.d/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /bin/zsh
        uname      Linux 5.4.6-arch3-1 #1 SMP PREEMPT Tue, 24 Dec 2019 04:36:53 +0000 x86_64
        path       (~/.bin ~/go/bin /usr/local/bin /usr/local/sbin /usr/local/bin /usr/bin /bin /usr/local/sbin /usr/lib/jvm/default/bin /usr/bin/site_perl /usr/bin/vendor_perl /usr/bin/core_perl /usr/lib/emacs/26.3/x86_64-pc-linux-gnu)
config  envfile    nil
        elc-files  0
        modules    (:completion company (ivy +childframe +fuzzy) :ui doom fill-column hl-todo modeline nav-flash ophints (popup +all +defaults) pretty-code treemacs vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors rotate-text snippets word-wrap :emacs dired electric vc :term term :tools debugger editorconfig eval :checkers syntax :tools (lookup +docsets) lsp magit make pass pdf :lang data emacs-lisp ess go latex markdown (org +dragndrop +present) plantuml rest sh :app calendar (write +wordnut) :config (default +bindings +smartparens))
        packages   ((ivy-rich :pin "7bfc7262fda46c38636eac3080980024b5881a64") counsel-tramp (dap-mode :pin "9d08eaf77d4aeb80880be85bc0591554314d0eb7") zoom (evil-snipe :pin "3ec8adfd4990f95fa0fab2b7019ead3596857673") evil-visual-mark-mode outline-magic outshine org-journal poporg (edit-indirect :pin "935ded353b9ed3da67bc61abf245c21b58d88864") writeroom-mode)
        elpa       (n/a)

Don't you think that it should be added to the FAQ? I found myself having a similar issue with remapping M-x and it took me some time to realize that there were this general-override-mode-map.


Artifacts for ppc64le are not published like linux x64 architecture

Opensearch snapshot for X64 is available at https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz
As power architecture is supported now, any update when the similar artifacts will be published for ppc64le as well ?

@dblock it would be great if the build team can publish these and we will continue to watch for Power specific issues and fix them,  on our side.

@bbarani @peterzhuamazon what would it take to add those to automation? Maybe @seth-priya can contribute?

[Triages] First step is to have the IBM server in order to move forward. Adding @elfisher and @setiah for discussion.

There are a few places to get access to ppc64le VMs, one of them is https://osuosl.org/services/powerdev/request_hosting/

Hi Team, any thoughts on above?

Adding @bbarani to comment on future supporting PowerPC 64 Little Endian ..thanks!

thanks @jordarlu , we can definitely contribute the changes that are needed for building the artifacts via automation and we can also discuss about the infrastructure that's needed for the same (if needed on a call?). As of now - we already have the Power changes up-streamed for the main opensearch repository and have been able to locally build the images and test them and also have a working build and image for opensearch-dashboards. Currently, we are building/validating all of the opensearch plugins separately on Power to make sure all of them work smoothly (though from what we have seen so far, they should). I am also adding our overall technical lead/architect @gerrith3 here.

Yeah - we would love to help support getting a CI environment set up for ppc64le.  I'd love to know what the options are from your side, what we would need to integrate with, etc.  We have some challenges with broadly available CI platforms but we do have several solutions, alternatives, and work arounds to integrate with most/many environments.

@dblock, @bbarani, @jordarlu and others,
I am from @seth-priya's team. We can help adding/maintaining ppc64le support to CI environment. Let us know how can we
move further on this.

@Sapana-Khemkar Thanks for your support. How do you want to proceed with next steps? Would a kick off call help to get things started soon? It would be really easy to collaborate if you can join OpenSearch Slack.

@Sapana-Khemkar Thanks for your support. How do you want to proceed with next steps? Would a kick-off call help to get things started soon? It would be really easy to collaborate via OpenSearch Slack workspace.

@bbarani joined slack and sent you message on devops channel.

Had an offline sync up with @Sapana-Khemkar, since OpenSearch supports ppc64le, having a Power9 server and running the build and assemble workflow should give us an artifact for ppc64le. While we request for the server and integrate with the CI/CD @Sapana-Khemkar  can you please post the results of the steps (manually executing the workflows on your server inside the opensearchstaging/ci-runner:ci-runner-centos7-opensearch-build-v3 docker) we discussed over the call?
Thank you

Hey for the OpenSearch folks, if you do request a free VM at OSL per the link earlier in this thread, reference my name as your IBM support contact and we will make sure it gets expedited for you.  We would love to see this integrated and we encounter more users of OpenSearch on Power all the time, so this would be a great step for all of us!!

And, apologies if this should be in a thread of its own, but does anyone know if OpenSearch is keeping up with Elasticsearch's ability to be used as a vector database?  I've been seeing that question come up several times and at the moment, I have no clue.  ;)  thanks, and apologies for hijacking another thread, although this is really yet another Power use case for us.  ;)

Hi @prudhvigodithi , I am from  @seth-priya and @Sapana-Khemkar's team. I was able to manually execute the build and assemble workflows on Power server and create an artifact for ppc64le.
The docker image opensearchstaging/ci-runner:ci-runner-centos7-opensearch-build-v3 is not available for power, hence was not able to execute workflows inside the container.
There were a few changes required to be made. I have attached logs of output for execution of build and assemble workflows, also attached the changes that were made to build the artifact.
OpenSearch_assemble.txt
OpenSearch_build.txt
OpenSearch_Patch.txt

And, apologies if this should be in a thread of its own, but does anyone know if OpenSearch is keeping up with Elasticsearch's ability to be used as a vector database? I've been seeing that question come up several times and at the moment, I have no clue. ;) thanks, and apologies for hijacking another thread, although this is really yet another Power use case for us. ;)

OpenSearch indeed has made lot of strides in Vector DB space. It uses K-NN functionality as documented in this blog to implement vector db functionality. The issues related to Vector DB functionalities are tracked here.

Had an offline sync up with @Sapana-Khemkar, since OpenSearch supports ppc64le, having a Power9 server and running the build and assemble workflow should give us an artifact for ppc64le. While we request for the server and integrate with the CI/CD @Sapana-Khemkar can you please post the results of the steps (manually executing the workflows on your server inside the opensearchstaging/ci-runner:ci-runner-centos7-opensearch-build-v3 docker) we discussed over the call? Thank you

@prudhvigodithi any update from your side? Have you raised request for ppc64le vm?

Hey @Sapana-Khemkar I have the form submitted NAME:   OpenSearch Project, support.osuosl.org #33270.
Thank you
@bbarani @peterzhuamazon

Hey @Sapana-Khemkar I have the form submitted NAME: OpenSearch Project, support.osuosl.org #33270. Thank you @bbarani @peterzhuamazon

@prudhvigodithi  your request 33270 is approved. Please let me know if you face any issue.

Thanks, @Sapana-Khemkar what is the next step here? I just got an email as Approved to the request I created. Let me know we can discuss the next steps in public slack on how to securely connect the ppc64le VM as jenkins agent.

Have a discussion with @prudhvigodithi and we need to add a test ci-runner image layer of linux/ppc64le, then try to start it up on the requested server before trying out the built.
If successful, then we will proceed with a manual build, before adding the changes to all the ci-runner images.
I will start on creating the new ci-runner image soon.

Thanks, @Sapana-Khemkar what is the next step here? I just got an email as Approved for the request I created. Let me know we can discuss the next steps in public slack on how to securely connect the ppc64le VM as jenkins agent.

@prudhvigodithi your request is approved from IBM. Now Lance Albertson from OSU will create VM. But he have few questions. I am pasting it here. Can you please respond to these?

Distribution:
CentOS

Will AlmaLinux work for this or do you want CentOS Stream? Also do you want The
8 or 9 release?

Est Size Of User Community:
NA
Expected Usage Model:
The POWER is used to build and assemble the OpenSearch software for
ppc64le architecture.
Flavor:
xlarge
Number Of Nodes:
5

Is this quantity a hard requirement is are you able to reduce this to something
smaller? I want to make sure we only allocate what's really needed.
cc: @ramereth

@Sapana-Khemkar since we are using docker here for the build, as long as there is docker installed for base OS on that machine, we good.

There are issues generating the ppc64le layer on docker, mainly due to pip installation here:
 => ERROR [linux/ppc64le 15/22] RUN ln -sfn /usr/local/bin/python3.9 /usr/bin/python3 &&     ln -sfn /usr/local/bin/pip3.9 /usr/bin/pip &&     ln -sfn /usr/local/bin/pip3.9 /usr/local/bin/pip &&     ln -sfn /usr/local/bin/pip3.9 /usr/bin/pip3 &&     pip3 install pip==23.1.2 && pip3 install pipenv==2023.6.12  81.0s
------
 > [linux/ppc64le 15/22] RUN ln -sfn /usr/local/bin/python3.9 /usr/bin/python3 &&     ln -sfn /usr/local/bin/pip3.9 /usr/bin/pip &&     ln -sfn /usr/local/bin/pip3.9 /usr/local/bin/pip &&     ln -sfn /usr/local/bin/pip3.9 /usr/bin/pip3 &&     pip3 install pip==23.1.2 && pip3 install pipenv==2023.6.12 awscli==1.22.12:
#0 6.242 Collecting pip==23.1.2
#0 6.365   Downloading pip-23.1.2-py3-none-any.whl (2.1 MB)
#0 7.345 Installing collected packages: pip
#0 7.345   Attempting uninstall: pip
#0 7.347     Found existing installation: pip 21.2.3
#0 8.631     Uninstalling pip-21.2.3:
#0 9.266       Successfully uninstalled pip-21.2.3
#0 19.95 Successfully installed pip-23.1.2
#0 19.95 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
#0 25.83 Collecting pipenv==2023.6.12
#0 26.07   Downloading pipenv-2023.6.12-py3-none-any.whl (2.9 MB)
#0 26.77      ���������������������������������������� 2.9/2.9 MB 4.4 MB/s eta 0:00:00
#0 34.13 Collecting awscli==1.22.12
#0 34.16   Downloading awscli-1.22.12-py3-none-any.whl (3.8 MB)
#0 35.04      ���������������������������������������� 3.8/3.8 MB 4.4 MB/s eta 0:00:00
#0 35.97 Collecting certifi (from pipenv==2023.6.12)
#0 36.00   Downloading certifi-2023.11.17-py3-none-any.whl (162 kB)
#0 36.07      ��������������������������������������� 162.5/162.5 kB 3.6 MB/s eta 0:00:00
#0 39.04 Collecting setuptools>=67.0.0 (from pipenv==2023.6.12)
#0 39.07   Downloading setuptools-69.0.3-py3-none-any.whl (819 kB)
#0 39.29      ��������������������������������������� 819.5/819.5 kB 4.3 MB/s eta 0:00:00
#0 39.50 Collecting virtualenv-clone>=0.2.5 (from pipenv==2023.6.12)
#0 39.53   Downloading virtualenv_clone-0.5.7-py3-none-any.whl (6.6 kB)
#0 40.75 Collecting virtualenv>=20.17.1 (from pipenv==2023.6.12)
#0 40.78   Downloading virtualenv-20.25.0-py3-none-any.whl (3.8 MB)
#0 41.66      ���������������������������������������� 3.8/3.8 MB 4.4 MB/s eta 0:00:00
#0 49.00 Collecting botocore==1.23.12 (from awscli==1.22.12)
#0 49.03   Downloading botocore-1.23.12-py3-none-any.whl (8.2 MB)
#0 50.91      ���������������������������������������� 8.2/8.2 MB 4.4 MB/s eta 0:00:00
#0 51.51 Collecting docutils<0.16,>=0.10 (from awscli==1.22.12)
#0 51.54   Downloading docutils-0.15.2-py3-none-any.whl (547 kB)
#0 51.70      ��������������������������������������� 547.6/547.6 kB 4.2 MB/s eta 0:00:00
#0 51.93 Collecting s3transfer<0.6.0,>=0.5.0 (from awscli==1.22.12)
#0 51.96   Downloading s3transfer-0.5.2-py3-none-any.whl (79 kB)
#0 52.00      ���������������������������������������� 79.5/79.5 kB 3.2 MB/s eta 0:00:00
#0 52.46 Collecting PyYAML<5.5,>=3.10 (from awscli==1.22.12)
#0 52.49   Downloading PyYAML-5.4.1.tar.gz (175 kB)
#0 52.56      ��������������������������������������� 175.1/175.1 kB 3.7 MB/s eta 0:00:00
#0 53.91   Installing build dependencies: started
#0 77.90   Installing build dependencies: finished with status 'done'
#0 77.91   Getting requirements to build wheel: started
#0 80.14   Getting requirements to build wheel: finished with status 'error'
#0 80.22   error: subprocess-exited-with-error
#0 80.22
#0 80.22   � Getting requirements to build wheel did not run successfully.
#0 80.22   � exit code: 1
#0 80.22   ��> [48 lines of output]
#0 80.22       running egg_info
#0 80.22       writing lib3/PyYAML.egg-info/PKG-INFO
#0 80.22       writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
#0 80.22       writing top-level names to lib3/PyYAML.egg-info/top_level.txt
#0 80.22       Traceback (most recent call last):
#0 80.22         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
#0 80.22           main()
#0 80.22         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
#0 80.22           json_out['return_val'] = hook(**hook_input['kwargs'])
#0 80.22         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
#0 80.22           return hook(config_settings)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
#0 80.22           return self._get_build_requires(config_settings, requirements=['wheel'])
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
#0 80.22           self.run_setup()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 311, in run_setup
#0 80.22           exec(code, locals())
#0 80.22         File "<string>", line 271, in <module>
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 103, in setup
#0 80.22           return distutils.core.setup(**attrs)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 185, in setup
#0 80.22           return run_commands(dist)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
#0 80.22           dist.run_commands()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
#0 80.22           self.run_command(cmd)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 963, in run_command
#0 80.22           super().run_command(command)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
#0 80.22           cmd_obj.run()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 321, in run
#0 80.22           self.find_sources()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 329, in find_sources
#0 80.22           mm.run()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 551, in run
#0 80.22           self.add_defaults()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 589, in add_defaults
#0 80.22           sdist.add_defaults(self)
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/command/sdist.py", line 112, in add_defaults
#0 80.22           super().add_defaults()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
#0 80.22           self._add_defaults_ext()
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
#0 80.22           self.filelist.extend(build_ext.get_source_files())
#0 80.22         File "<string>", line 201, in get_source_files
#0 80.22         File "/tmp/pip-build-env-pp05v2oy/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
#0 80.22           raise AttributeError(attr)
#0 80.22       AttributeError: cython_sources
#0 80.22       [end of output]
#0 80.22
#0 80.22   note: This error originates from a subprocess, and is likely not a problem with pip.
#0 80.25 error: subprocess-exited-with-error
#0 80.25
#0 80.25 � Getting requirements to build wheel did not run successfully.
#0 80.25 � exit code: 1
#0 80.25 ��> See above for output.
#0 80.25
#0 80.25 note: This error originates from a subprocess, and is likely not a problem with pip.
#0 80.28
#0 80.28 [notice] A new release of pip is available: 23.1.2 -> 23.3.2
#0 80.28 [notice] To update, run: pip install --upgrade pip

Hey @janani66, the link asks for login details https://support.osuosl.org/Ticket/Display.html?id=33270 so we can continue to discuss on this issue. The requirement can be adjusted later based on how frequently we want to build the ppc64le distribution (scale up and scale down as required), since we are at POC phase, its ok to get a basic VM that works to build and assemble the OpenSearch distribution. For linux x64 distribution build the existing setup uses C54xlarge (Ref: https://github.com/opensearch-project/opensearch-ci/blob/main/lib/compute/agent-nodes.ts#L74-L86) which can handle multiple parallel OpenSearch distribution builds. So please adjust the requirement that can be given for testing and flexible enough to update if required.
Thank you
Adding @peterzhuamazon

Hey @janani66, the link asks for login details https://support.osuosl.org/Ticket/Display.html?id=33270 so we can continue to discuss on this issue. The requirement can be adjusted later based on how frequently we want to build the ppc64le distribution (scale up and scale down as required), since we are at POC phase, its ok to get a basic VM that works to build and assemble the OpenSearch distribution. For linux x64 distribution build the existing setup uses C54xlarge (Ref: https://github.com/opensearch-project/opensearch-ci/blob/main/lib/compute/agent-nodes.ts#L74-L86) which can handle multiple parallel OpenSearch distribution builds. So please adjust the requirement that can be given for testing and flexible enough to update if required. Thank you Adding @peterzhuamazon

As of now either Rocky/Alma/Ubuntu based server is fine, as we are using docker to build.
We can have 5 nodes to start with, each having 16CPU 32GB setup, as each will be loaded with 4 docker containers (4CPU/8GB each). That means a total of 20 executors with containers which is sufficient enough for now.
Tho keep in mind our current setup is utilizing EC2 to dynamically provision runners, which means if there are a lot of builds, then 20 executors may be execeeded later. If there is a way to provision ppc64le server dynamically through EC2 that would be even better.

@peterzhuamazon should be able to use the OpenStack API to automatically provision what you need, however @janani66 mentioned in the ticket that you wanted us to create the VMs for you instead of getting API access.
@janani66 if you can get email addresses for @peterzhuamazon and whomever else on this issue, I can add them to our ticket so we can discuss this further without going back and forth here.

@peterzhuamazon should be able to use the OpenStack API to automatically provision what you need, however @janani66 mentioned in the ticket that you wanted us to create the VMs for you instead of getting API access.
@janani66 if you can get email addresses for @peterzhuamazon and whomever else on this issue, I can add them to our ticket so we can discuss this further without going back and forth here.

I dont think I have a login credential for the ticket now, assuming this one?
https://support.osuosl.org/Ticket/Display.html?id=33270
I can give you more information once I can login and comment there.

@peterzhuamazon it's best if we just add you to the ticket directly and move the conversation to email only. We don't typically open up logins directly to the tickets.

@peterzhuamazon it's best if we just add you to the ticket directly and move the conversation to email only. We don't typically open up logins directly to the tickets.

Got it.

Able to login to the initial almalinux8 test server.
More issues:
Error:
 Problem: cannot install the best candidate for the job
  - package gh-2.42.0-1.i386 from gh-cli does not have a compatible architecture
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Issue: gh client has no ppc64le support.
Error:
 Problem: cannot install the best candidate for the job
  - package gh-2.42.0-1.i386 from gh-cli does not have a compatible architecture
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

# yum list gh --showduplicates
Last metadata expiration check: 0:01:43 ago on Thu 11 Jan 2024 09:57:38 PM UTC.
Available Packages
gh.aarch64                                                                                2.42.0-1                                                                                gh-cli
gh.armv6hl                                                                                2.42.0-1                                                                                gh-cli
gh.i386                                                                                2.42.0-1                                                                                gh-cli
gh.x86_64                                                                                2.42.0-1                                                                                gh-cli

As of https://github.com/cli/cli/releases/tag/v2.42.0 we are not seeing support on ppc64le for gh client.

Add a few tweaks before making maven run:
# mvn --version
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/apache-maven
Java version: 11.0.15, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/temurin-11-jdk
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.18.0-513.9.1.el8_9.ppc64le", arch: "ppc64le", family: "unix"

PRs:

#4336
#4340

Issue: gh client has no ppc64le support.
Error:
 Problem: cannot install the best candidate for the job
  - package gh-2.42.0-1.i386 from gh-cli does not have a compatible architecture
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

# yum list gh --showduplicates
Last metadata expiration check: 0:01:43 ago on Thu 11 Jan 2024 09:57:38 PM UTC.
Available Packages
gh.aarch64                                                                                2.42.0-1                                                                                gh-cli
gh.armv6hl                                                                                2.42.0-1                                                                                gh-cli
gh.i386                                                                                2.42.0-1                                                                                gh-cli
gh.x86_64                                                                                2.42.0-1                                                                                gh-cli

As of https://github.com/cli/cli/releases/tag/v2.42.0 we are not seeing support on ppc64le for gh client.

Hi @peterzhuamazon, We are working on enabling power support for gh-cli, as a workaround gh-cli can be installed using following command :
go install github.com/cli/cli/v2/cmd/gh@latest

Issue: gh client has no ppc64le support.
Error:
 Problem: cannot install the best candidate for the job
  - package gh-2.42.0-1.i386 from gh-cli does not have a compatible architecture
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

# yum list gh --showduplicates
Last metadata expiration check: 0:01:43 ago on Thu 11 Jan 2024 09:57:38 PM UTC.
Available Packages
gh.aarch64                                                                                2.42.0-1                                                                                gh-cli
gh.armv6hl                                                                                2.42.0-1                                                                                gh-cli
gh.i386                                                                                2.42.0-1                                                                                gh-cli
gh.x86_64                                                                                2.42.0-1                                                                                gh-cli

As of https://github.com/cli/cli/releases/tag/v2.42.0 we are not seeing support on ppc64le for gh client.

Hi @peterzhuamazon, We are working on enabling power support for gh-cli, as a workaround gh-cli can be installed using following command : go install github.com/cli/cli/v2/cmd/gh@latest

Seems like it needs go version 1.21 or above?
I will take a look on that.
Thanks.

20240122: Have meeting with IBM team on current status:

ml-commons still have some issues and IBM team is still testing on their end.
IBM team will raise the PR to have gh cli supported officially on gh cli repo, with prebuild binaries.
IBM team is aiming for TAR distribution to start with, and later RPM. Only build/assemble now, not integTest, see 6.
IBM Team needs to make changes on these files to start with:

Adding ppc64le build target: https://github.com/opensearch-project/opensearch-build/blob/main/scripts/components/OpenSearch/build.sh
Adding ppc64le stage: https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/opensearch/distribution-build.jenkinsfile#L148

IBM Team will try to resolve the pytest errors due to PyYAML 6.0.1 upgrades: https://github.com/opensearch-project/opensearch-build/pull/4348
IBM Team will try to figure out some ways of allowing Jenkins to dynamically provision servers for its agents. So we will not have resource exhaustion problem or have to manually setup the runners everytime there is a Jenkins maintenance.

Current expectation: At least 10x Servers with 16CPU 32GB setups to start with.

@peterzhuamazon will get this PR reviewed and merged soon, and building new images with linux/ppc64le layer: https://github.com/opensearch-project/opensearch-build/pull/4336

cc: @Sapana-Khemkar @seth-priya @Sunidhi-Gaonkar1 @bbarani @prudhvigodithi
Thanks.

ml-commons - we are working on this.
Official support from gh-cli

We have raised PR for ppc64le support. But it may take a little time. Meanwhile can you install go v1.21.0 using below steps
wget https://go.dev/dl/go1.21.0.linux-ppc64le.tar.gz
tar -C /usr/local -xzf go1.21.0.linux-ppc64le.tar.gz
export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export PATH=$PATH:$GOROOT/bin:$GOPATH/bin:/usr/local/bin
go version

@Sunidhi-Gaonkar1  will raise PR for build.sh and update you. For changes in Jenkins file we will wait for your PR to get merged.
@Sunidhi-Gaonkar1 will be looking into pytest errors due to PyYAML 6.0.1.
For dynamic provision of ppc64le servers, you can raise request with OpenStack Access. While raising vm request select "I'do like to have access to the Openstack GUI/API" option (as highlighted in below image) and use Openstack APIs for dynamically provision ppc64le servers.

Thanks @Sapana-Khemkar ,
On 7, @prudhvigodithi has completed the review of my ci-runners changes.
Since building these images takes a lot of time, so I plan to reduce the load if possible.
This PR is in review to add gh cli ppc64le support, and I will give it a few days to see gh team reply.

https://github.com/cli/cli/pull/8612

If their review and support takes a lot of time, I will merge #4336 and start building the images next week.
Thanks.

On 6, I am still a bit confused as that seems like still manual approaches to request servers, without internally connect through EC2 APIs.
Or is there is any plugin that can directly connect Jenkins provision agents with openstack, we still need to look into that in details.

Or is there is any plugin that can directly connect Jenkins provision agents with openstack, we still need to look into that in details.

@peterzhuamazon  yes, there is an openstack plugin for jenkins that can help with dynamic provisioning of VMs once you have openstack access - https://plugins.jenkins.io/openstack-cloud/ , https://plugins.jenkins.io/openstack-cloud/releases/

Sent OpenStack Access.

Due to #4241 #4370, we will delay the image generation for ppc64le, to unblock 2.12 release issues with IntegTests.

@peterzhuamazon, I was able to resolve the pytest errors faced for #4348. The errors were thrown due to code linting issue. The sorting order was fixed  after running command pipenv run isort . as mentioned in https://github.com/opensearch-project/opensearch-build/blob/main/DEVELOPER_GUIDE.md#code-linting.

@peterzhuamazon, I was able to resolve the pytest errors faced for #4348. The errors were thrown due to code linting issue. The sorting order was fixed after running command pipenv run isort . as mentioned in https://github.com/opensearch-project/opensearch-build/blob/main/DEVELOPER_GUIDE.md#code-linting.

Hi @Sunidhi-Gaonkar1 if you resolve the sort issue and actually run pipenv run pytest you will see new issues. The isort issues is expected and not related to the pytest issues.
Thanks.

Receive credentials on accessing to OpenStack and it endpoints. Will work on connecting to Jenkins.

Raised PR #4413  to fix pytests and update build.sh to add ppc64le build target.
Please review, Thank you.

Use package manager for go installation for easier setups.
Move gh to https://github.com/cli/cli/releases/tag/v2.32.1 since that is the last version using go < 1.21.

Only possible when manually checkout the repo then make:
make install prefix=/path/to/gh

The 1st docker ci images with ppc64le layer is up online: https://hub.docker.com/r/opensearchstaging/ci-runner/tags?page=1&ordering=last_updated&name=ci-runner-centos7-opensearch-build-v3.8
More to come.

More issues:
Rockylinux8:
ERROR: failed to solve: rockylinux:8: no match for platform in manifest: not found

We might need to change to almalinux from rockylinux due to version 8 is not having ppc64le layer for rockylinux.

More to read:
https://rockylinux.org/news/rocky-linux-9-2-power-le-update/

All build and test ci images now support ppc64le and have gh installed with go modules.
However, docker release images will not support ppc64le unless AmazonLinux 2023 image start supporting it.

All build and test ci images now support ppc64le and have gh installed with go modules. However, docker release images will not support ppc64le unless AmazonLinux 2023 image start supporting it.

Thanks @peterzhuamazon please go ahead with this part and release tar for power. We will work with you on docker images separately.

We will continue with the Almalinux switch after 2.13.0 release.

We will continue with the Almalinux switch after 2.13.0 release.

Hi @peterzhuamazon , Any updates on this?


chore(main): release 0.8.1

:robot: I have created a release beep boop
0.8.1 (2024-06-25)
Bug Fixes

removed all .count() and replaced with attribute in the class definition (#16) (b86c5ec)
ui: fix import path for DataQualityMetrics and ModelQualityMetrics in import-detail-modal (#24) (0be20d5)
ui: show filename in import-detail-modal header (#25) (99629c5)

Chores

force dataType to TABULAR (#7) (c9c37ff)
sdk: align reference metrics business models with API (#11) (0db1dfe)
sdk: apply ruff format and lint like done in API project (#18) (41fd0cf)
sdk: get current dataset statistics (#13) (dec2d05)
sdk: get current model quality metrics (#21) (74fef65)
sdk: get data quality for current dataset (#19) (fce83aa)
sdk: implement get current dataset drift (#15) (7513b39)
sdk: manage all metrics based on model type (#22) (8d2710e)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.8.1
:sunflower:


Line missing a work

In the first section, between the two purple boxes, the following line appears to be missing a word. "Therefore, if you want to grant permissions to a only in Azure Sentinel..."

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

ID: 1a7e388c-e6fd-22df-0070-b051fc09cb0c
Version Independent ID: c543b5d2-e0db-d137-acd2-43ed1f712817
Content: Permissions in Azure Sentinel
Content Source: articles/sentinel/roles.md
Service: azure-sentinel
Sub-service: azure-sentinel
GitHub Login: @yelevin
Microsoft Alias: yelevin

@garybushey Thanks for the feedback! We will review and update accordingly.

@garybushey The PR for the fix has been created and it will be merged soon. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.


Patch ACM retry to not retry after LimitExceededException

Should fix https://github.com/pulumi/pulumi-aws/issues/3279.
Followed the guide in https://github.com/hashicorp/terraform-provider-aws/blob/main/docs/retries-and-waiters.md linked in https://github.com/pulumi/pulumi-aws/pull/3234.
Essentially we should not retry after getting a LimitExceededException.
I've tested the repro in https://github.com/pulumi/pulumi-aws/issues/3279 and it now correctly returns LimitExceededException instead of InvalidSignatureException. I've also tested that the happy path works in an account which has not reached the quota.
We'll defer setting up a regression test until we set up the infra for mocking out AWS responses.
The full error message we are matching is of the shape "LimitExceededException: You have imported the maximum number of 5000 certificates in the last year."

We'll defer setting up a regression test until we set up the infra for mocking out AWS responses.

LMK if you've added a ticket already, if not I will.

I haven't feel free to open one, I imagine you have some ideas on how to mock out the API.

LGTM if tests pass and you confirmed it's fixing the issue.
I've tested:

with this patch we get the right LimitExceededException
after removing it I get the old InvalidSignatureException on the same program and stack
with the patch and on an account which has not reached the quota, the happy path of creating a certificate works fine.


Present PROF information

ProfCat must draw Profiles Vocabulary information from individual profiles and present it both for each Profile in the catalogue and in aggregate via PROF views of the catalogue items.

Resolved, see https://w3id.org/profile/chekatest?_profile=prof for an example

Resolved, see https://w3id.org/profile/chekatest?_profile=prof for an example


hostname not correct after initial installation, content must be served over HTTPS

Hi,
Upon installing the latest version, I load my homepage (very vanilla install of Laravel), I get this in my console:
was loaded over HTTPS, but requested an insecure script 'http://[::]:5173/resources/js/Pages/Dashboard.vue'. This request has been blocked; the content must be served over HTTPS.

I looked in other issues and other docs, but can't figure out how solve it. Any suggestions?

Disregard, I found the solution.
Added this to my vite.config.js
    server: {
        https: true,
        hmr: {
            host: 'mysite.ddev.site',
        }
    },

getting a CORS issue now, but that's something totally different ;)


Only try to print out the subscription if it has been created successfully

Proposed Changes

Only try to print out the subscription if it has been created successfully.
- If the subscription is nil, then logging it will panic.

Release Note

NONE

/lgtm

/lgtm
/approve


NoSuchMethodError

I've been happily using depot for some time, including on a project I'm actively working on, but recently it started throwing this exception with this project:
Exception in thread "main" java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.eclipse.aether.util.ConfigUtils.getFloat(Ljava/util/Map;F[Ljava/lang/String;)F
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at clojure.core$deref_future.invokeStatic(core.clj:2300)
	at clojure.core$future_call$reify__8439.deref(core.clj:6974)
	at clojure.core$deref.invokeStatic(core.clj:2320)
	at clojure.core$deref.invoke(core.clj:2306)
	at clojure.core$map$fn__5851.invoke(core.clj:2755)
	at clojure.lang.LazySeq.sval(LazySeq.java:42)
	at clojure.lang.LazySeq.seq(LazySeq.java:58)
	at clojure.lang.RT.seq(RT.java:531)
	at clojure.core$seq__5387.invokeStatic(core.clj:137)
	at clojure.core$keep$fn__8544.invoke(core.clj:7330)
	at clojure.lang.LazySeq.sval(LazySeq.java:42)
	at clojure.lang.LazySeq.seq(LazySeq.java:51)
	at clojure.lang.RT.seq(RT.java:531)
	at clojure.core$seq__5387.invokeStatic(core.clj:137)
	at clojure.core$sort.invokeStatic(core.clj:3113)
	at clojure.core$sort_by.invokeStatic(core.clj:3119)
	at clojure.core$sort_by.invokeStatic(core.clj:3119)
	at clojure.core$sort_by.invoke(core.clj:3119)
	at depot.outdated$gather_outdated.invokeStatic(outdated.clj:122)
	at depot.outdated$gather_outdated.invoke(outdated.clj:104)
	at depot.outdated.main$_main.invokeStatic(main.clj:55)
	at depot.outdated.main$_main.doInvoke(main.clj:33)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:705)
	at clojure.core$apply.invokeStatic(core.clj:665)
	at clojure.main$main_opt.invokeStatic(main.clj:491)
	at clojure.main$main_opt.invoke(main.clj:487)
	at clojure.main$main.invokeStatic(main.clj:598)
	at clojure.main$main.doInvoke(main.clj:561)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:705)
	at clojure.main.main(main.java:37)
Caused by: java.lang.NoSuchMethodError: org.eclipse.aether.util.ConfigUtils.getFloat(Ljava/util/Map;F[Ljava/lang/String;)F
	at org.eclipse.aether.internal.impl.PrioritizedComponents.add(PrioritizedComponents.java:66)
	at org.eclipse.aether.internal.impl.DefaultLocalRepositoryProvider.newLocalRepositoryManager(DefaultLocalRepositoryProvider.java:104)
	at org.eclipse.aether.internal.impl.DefaultRepositorySystem.newLocalRepositoryManager(DefaultRepositorySystem.java:392)
	at depot.outdated$make_session.invokeStatic(outdated.clj:28)
	at depot.outdated$make_session.invoke(outdated.clj:25)
	at depot.outdated$coord__GT_version_status.invokeStatic(outdated.clj:36)
	at depot.outdated$coord__GT_version_status.invoke(outdated.clj:32)
	at depot.outdated$eval1367$fn__1369.invoke(outdated.clj:63)
	at clojure.lang.MultiFn.invoke(MultiFn.java:239)
	at depot.outdated$current_latest_map.invokeStatic(outdated.clj:102)
	at depot.outdated$current_latest_map.invoke(outdated.clj:98)
	at depot.outdated$gather_outdated$fn__1393.invoke(outdated.clj:113)
	at clojure.core$pmap$fn__8447$fn__8448.invoke(core.clj:7022)
	at clojure.core$binding_conveyor_fn$fn__5739.invoke(core.clj:2030)
	at clojure.lang.AFn.call(AFn.java:18)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

I assume (but have not confirmed) that a change in my project's own dependencies conflicted with depot's own dependencies.  Here's my deps.edn:
{:deps    {org.clojure/clojure              {:mvn/version "1.10.0"}
           org.clojure/data.zip             {:mvn/version "0.1.3"}
           version-clj                      {:mvn/version "0.1.2"}
           org.owasp/dependency-check-maven {:mvn/version "4.0.2"}
           eu.7bridges/corallo              {:mvn/version "0.1.1"}}
 :aliases {:check        {:extra-deps {athos/clj-check {:git/url "https://github.com/athos/clj-check.git"
                                                        :sha "b48d4e7000586529f81c1e29069b503b57259514"}}
                          :main-opts ["-m" "clj-check.check"]}                          ; clj -A:check
           :test         {:extra-paths ["test"]}
           :ancient      {:extra-deps {olical/depot {:mvn/version "1.8.2"}}             ; clj -A:ancient
                          :main-opts  ["-m" "depot.outdated.main"]}
           :uberjar      {:extra-deps {luchiniatwork/cambada {:mvn/version "1.0.0"}}    ; clj -A:uberjar
                          :main-opts  ["-m" "cambada.uberjar"
                                       "-m" "clojars-dependencies.main"]}
           :native-image {:extra-deps {luchiniatwork/cambada {:mvn/version "1.0.0"}}    ; clj -A:native-image
                          :main-opts  ["-m" "cambada.native-image"
                                       "-m" "clojars-dependencies.main"]}}}

Aha, well that's odd. I can see aether in that stack trace, so maybe it's a conflicting version there, yeah. Definitely not from a change on depot's side, it's been pretty stable and hasn't changed much at all recently. Try clj -Stree and have a look through there for things that don't seem to match up I guess?
I've never really had to resolve these sorts of conflicts in the past I'm afraid.

Here's the output from clj -Stree:
$ clj -Stree
org.clojure/clojure 1.10.0
  org.clojure/core.specs.alpha 0.2.44
  org.clojure/spec.alpha 0.2.176
org.clojure/data.zip 0.1.3
aysylu/loom 1.0.2
  tailrecursion/cljs-priority-map 1.2.1
    org.clojure/clojurescript 1.7.170
      org.clojure/data.json 0.2.6
      org.clojure/google-closure-library 0.0-20151016-61277aea
        org.clojure/google-closure-library-third-party 0.0-20151016-61277aea
      org.mozilla/rhino 1.7R5
      com.google.javascript/closure-compiler v20151015
      org.clojure/tools.reader 0.10.0-alpha3
  org.clojure/data.priority-map 0.0.5
org.owasp/dependency-check-maven 4.0.2
  org.apache.maven.reporting/maven-reporting-api 3.0
    org.apache.maven.doxia/doxia-sink-api 1.0
  org.apache.maven.shared/maven-dependency-tree 3.0.1
    org.eclipse.aether/aether-util 0.9.0.M2
  org.apache.maven.shared/file-management 3.0.0
    org.apache.maven.shared/maven-shared-io 3.0.0
      org.apache.maven.wagon/wagon-provider-api 2.10
      org.apache.maven/maven-compat 3.0
    org.apache.maven/maven-plugin-api 3.0
      org.sonatype.sisu/sisu-inject-plexus 1.4.2
        org.sonatype.sisu/sisu-inject-bean 1.4.2
          org.sonatype.sisu/sisu-guice$noaop 2.1.7
      org.apache.maven/maven-model 3.0
  org.owasp/dependency-check-core 4.0.2
    joda-time/joda-time 1.6
    org.apache.commons/commons-compress 1.18
    com.h3xstream.retirejs/retirejs-core 3.0.1
      com.esotericsoftware/minlog 1.3
      com.github.spullara.mustache.java/compiler 0.8.17
      org.json/json 20140107
    org.apache.lucene/lucene-analyzers-common 7.6.0
    com.h2database/h2 1.4.196
    commons-io/commons-io 2.6
    commons-collections/commons-collections 3.2.2
    org.apache.lucene/lucene-core 7.6.0
    org.apache.lucene/lucene-queryparser 7.6.0
      org.apache.lucene/lucene-queries 7.6.0
      org.apache.lucene/lucene-sandbox 7.6.0
    org.apache.commons/commons-text 1.3
      org.apache.commons/commons-lang3 3.7
    com.google.guava/guava 27.0.1-jre
      com.google.errorprone/error_prone_annotations 2.2.0
      org.codehaus.mojo/animal-sniffer-annotations 1.17
      com.google.guava/listenablefuture 9999.0-empty-to-avoid-conflict-with-guava
      com.google.guava/failureaccess 1.0.1
      com.google.j2objc/j2objc-annotations 1.1
      org.checkerframework/checker-qual 2.5.2
      com.google.code.findbugs/jsr305 3.0.2
    org.apache.velocity/velocity 1.7
      commons-lang/commons-lang 2.4
    com.sun.mail/mailapi 1.6.3
    com.vdurmont/semver4j 2.2.0
    org.jsoup/jsoup 1.11.3
    org.slf4j/slf4j-api 1.7.25
    org.glassfish/javax.json 1.0.4
    com.google.code.gson/gson 2.8.5
  org.owasp/dependency-check-utils 4.0.2
  org.apache.maven.shared/maven-artifact-transfer 0.10.1
    commons-codec/commons-codec 1.11
    org.codehaus.plexus/plexus-component-annotations 1.7.1
    org.codehaus.plexus/plexus-utils 3.1.0
    org.apache.maven/maven-core 3.0
      org.sonatype.aether/aether-util 1.7
      org.apache.maven/maven-model-builder 3.0
      org.apache.maven/maven-settings-builder 3.0
      org.apache.maven/maven-settings 3.0
      org.apache.maven/maven-aether-provider 3.0
      org.sonatype.aether/aether-impl 1.7
        org.sonatype.aether/aether-spi 1.7
      org.codehaus.plexus/plexus-classworlds 2.2.3
      org.codehaus.plexus/plexus-interpolation 1.14
      org.sonatype.aether/aether-api 1.7
      org.apache.maven/maven-repository-metadata 3.0
    org.apache.maven.shared/maven-common-artifact-filters 3.0.1
      org.apache.maven.shared/maven-shared-utils 3.1.0
    org.apache.maven/maven-artifact 3.0
  org.sonatype.plexus/plexus-sec-dispatcher 1.4
    org.sonatype.plexus/plexus-cipher 1.4
version-clj/version-clj 0.1.2

I see a few different aether artifacts in there, but no obvious conflicts based solely on GAVs (though it's entirely possible that different JARs contain the same class, which would be unfortunate...).

So this wouldn't happen to be fixed in 1.8.4 would it?

I’m not in a position to check until late July, but if you’d like to try yourself the project is here.

Please update again this was due to a bad deploy and has since been fixed.
Sorry about that!
On Wed, 3 Jul 2019, 04:18 Peter Monks<EMAIL_ADDRESS>wrote:

I’m not in a position to check until late July, but if you’d like to try
yourself the project is here
https://github.com/pmonks/clojars-dependencies.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Olical/depot/issues/23?email_source=notifications&email_token=AACM6XJJ7SIOAOYNJEBJO2LP5QLAHA5CNFSM4HSVBGNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDEJHA#issuecomment-507921564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACM6XPQBXURPPAVDGFU55LP5QLAHANCNFSM4HSVBGNA
.

I actually thought this was a new issue and replied by email :man_facepalming: my bad! I realised my prompt to update looked pretty weird and pushy after that. I thought it was someone having an issue with the previous version which was a broken deploy. Take your time! :smile:

No worries - I appreciated the update, tbh!  😃
I’m traveling without a laptop right now, but once I get home I’ll give the new version a shot.
Thanks!

Ok finally had a chance to upgrade and try it again, but I'm still getting an error with v1.8.4:
$ clj -A:ancient
Execution error (NoSuchMethodError) at org.eclipse.aether.internal.impl.PrioritizedComponents/add (PrioritizedComponents.java:66).
org.eclipse.aether.util.ConfigUtils.getFloat(Ljava/util/Map;F[Ljava/lang/String;)F

Full report at:
/var/folders/x4/jg66qz6n3dqd4fwxgfsp3j2h0000gn/T/clojure-2910453177622845879.edn

:thinking: not sure if anyone else is having this issue so I'm still wondering if it's to do with your other dependencies in your project. Like one of them is shifting some transitive dependency version slightly. Haven't had time to take a proper look at a bug, if I do it won't be for a little while yet :disappointed:
If I could reproduce it maybe I could work out some sort of workaround, just not sure how right now.

The project where this is happening is open source, so you should be able to clone that repo and reproduce at will:
$ git clone https://github.com/pmonks/clojars-dependencies.git
$ cd clojars-dependencies
$ clj -A:ancient

So I commented out the dependencies one at the time and it worked after I got rid of org.owasp/dependency-check-maven, updating it to the latest version doesn't seem to work either, sadly. Maybe there's a way to exclude it while trying to use depot? I can't see it messing with any dependencies that depot requires, so it's pretty confusing.
Maybe it's treated as an optional dependency by some other dependency in the tree, so it's presence triggers some other path in some tool that I'm not aware of. I'm afraid I don't have any simple answers for this one.

Sounds like a transitive dependency conflict, unless you also checked those?
We now know it’s a conflict between one of aether’s dependencies and either dependency-check-maven itself or one of its dependencies, which narrows down the hunt somewhat.

  It's possible the problematic class (org.eclipse.aether.util.ConfigUtils) moved JARs at some point, but tracking that down is going to be a royal pita.  😢

Upgrading org.owasp/dependency-check-maven to v5.2.1 didn't help either, FWIW.

Yep, I'm not sure if it's a straight conflict, like I couldn't see anything in a minimal depot project that is shared in this error stack. Which is what makes me think it's the presence of the library that causes something to require it and try to do something with it, like an optional dependency?

What's a tad annoying is that I only use org.owasp/dependency-check-maven for its (very handy) XmlInputStream class.  I guess I wasn't the only one who got fed up with the garbage POM files on Maven Central, but I digress...
Given that that class is based on a StackOverflow answer (plus it's Apache licensed) it's tempting to just copy that code out into my own project and ditch that dependency...

Hmm, yeah, ripping it out to remove the rest of the dep is probably the easiest and best thing to do. It's still annoying but I'm not sure what I can do to fix this, especially since it impacts a fraction of the potential projects out there.

So I'm chalking this up to "extremely rare and unlikely dependency conflict of some kind that I don't fully understand". I think working around this for the small amount of possible cases is the way to go for now.
If this is more common than I think right now I'll dig deeper and work out what's causing it. I'm still considering a rewrite of this one day to unify the "find updates" and "apply updates" halves of the code base, so it could go away with that.
Closing for now, thank you for all of the data and help! I'm sure it'll help a lot as and when I get around to patching this issue out somehow.


sticky-sidebar - Support new issue view

part of #7856
Test URLs
https://github.com/download-directory/download-directory.github.io/issues/141

I made some changes to support the notification bar. But then I noticed a z-index issue with the header:

should be fixed
I also removed the additional spacing on the repo site

Good catch!
If you're interested, I realized that this feature doesn't apply to discussions, so it can be added there, it it's not difficult.
Test URL:
https://github.com/eslint/eslint/discussions/18304


Index was outside the bounds of the array.

StackTrace:
at System.Text.StringBuilder.get_Chars(Int32 index)
at AngleSharp.TextSource.get_Item(Int32 index)
at AngleSharp.Parser.BaseTokenizer.NormalizeBackward(Char p)
at AngleSharp.Parser.BaseTokenizer.BackUnsafe()
at AngleSharp.Parser.BaseTokenizer.Back()
at AngleSharp.Parser.Html.HtmlTokenizer.DataText(Char c)
at AngleSharp.Parser.Html.HtmlTokenizer.Data(Char c)
at AngleSharp.Parser.Html.HtmlTokenizer.Get()
at AngleSharp.Parser.Html.HtmlDomBuilder.Parse(HtmlParserOptions options)
at AngleSharp.Parser.Html.HtmlParser.Parse(String source)

Source of the document where this happened? What version of AngleSharp did you use?

Oh! I see that the issue has been resolved in .9.2

Alright - glad that was fixed already!

Hmm, the problem is back


[added] Allow overlay override

Continues and Closes #281
@diasbruno @claydiffrient Sorry that it took so long for me to prepare this feature. Leaving previous branch if someone uses it.
To override overlay one should provide overlay prop to Modal containing react element. That component will be cloned and filled with overlay props and children (using React.cloneElement).
Another way may be to provide overlayComponent and overlayProps and then create react element from them (using React.createElement). Which way us better and more idiomatic?
Changes proposed:

Extract ModalOverlay to component
Allow user to provide custom overlay with Modal.props.overlay prop

Acceptance Checklist:

[ ] All commits have been squashed to one.
[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.

@cema-sp this looks awesome. i'll bring some feedback later.

Coverage increased (+2.4%) to 83.072% when pulling d7193a8d53afa68dda860ba41f21a8276008ec57 on cema-sp:modal-overlay into a8b7aa0901de84d82c7335f31d6afe1e2cb8caaa on reactjs:master.

@diasbruno Rebased & squashed

@diasbruno would this PR get merged at any point soon? Would love to have the scroll functionality on the modal. thanks.

@Monte9 FYI if all you need is a scrollable modal, you can just add
.ReactModal__Overlay {
  overflow-y: scroll !important;
 }

to your css

@rifkegribenes that's correct. the idea for this PR is to make the overlay customizable.
@cema-sp I think it's a good time to 'revive' this branch. Any help you need to get this branch updated, please let me know.

@rifkegribenes thanks for the quick css fix.
I found the following works better for my case. It retains the modal positon. (I have the modal open a little closer to the top instead of center.)
.ReactModal__Overlay--after-open {
  overflow-y: scroll !important;
}

Sorry, won't be able to get back to it any time soon.


Services: ret NOnionException downloadDescriptor

Previously returned exception with failwith which returned System.Exception. Now it returns NOnionExceptoin.

@aarani please review

From my side, you're not explaining the why in the commit message (adding a link to the bug you're aiming to fix provides the why).

Fixes https://github.com/nblockchain/geewallet/issues/181

This statement is false, because even if I merge this PR, it doesn't fix the bug.

@aarani please review

The code LGTM.

Fixes nblockchain/geewallet#181

This statement is false, because even if I merge this PR, it doesn't fix the bug.

I updated the body message and explained the situation.

but it dosn't fix it. The fix for that problem should be continued on GWallet.

Typo "dosn't" ^ and anyway, you don't need to say it doesn't fix it; it's obvious that GWallet needs to update NOnion dep for that.

but it dosn't fix it. The fix for that problem should be continued on GWallet.

Typo "dosn't" ^ and anyway, you don't need to say it doesn't fix it; it's obvious that GWallet needs to update NOnion dep for that.

Fixed.


Error when fresh new run 'npm run build'

I'm facing this error when running 'npm run dev' and 'npm run build', see image bellow:
http://pix.toile-libre.org/upload/original/1464870344.jpg
To fix this I need to change how the code load the components and App, see code:
File: ./src/main.js
// from
import App from './App';
// to
import App from './App.vue';

File: ./src/App.vue
// from
import Hello from './components/Hello';
// to
import Hello from './components/Hello.vue';

Is this correct so and this project outdated ?

Hmm, cannot reproduce this, because it should resolve correctly: https://github.com/vuejs-templates/webpack/blob/dist/template/build/webpack.base.conf.js#L16 (.vue extension is included)
Can you provide the OS/Node/npm/webpack versions?

@jaschweder This is a known issue with the Airbnb linting config - is that what you're using? It's actually a bug on their end (and frankly, I think an overreach, since module bundlers already report errors if they can't find a module).

@yyx990803
OS: Ubuntu 14.04 LTS
Node: v4.4.3 (stable)
Webpack: latest (cloned from branch master)
@chrisvfritz
yes I'm using Airbnb

Duplicate #144.


better construction for flags

What is the issue about:
Improvement needed for StringFlag

What happened:
There are simply too many fields to be filled for StringFlag.
What you expected to happen:
Should be a builder or some other helper functions to fulfill default values.
Anything else we need to know:

Can you just leave the flag field empty?

+1, leave the fields empty.
Only Name is required, the others are optional.

no action


Split components into multiple CRD/controllers

Split the Harbor CRD into multiple smaller one.
So every components can be reconciled independently.
Have a definition for following components

ChartMuseum
Clair
Core
JobService
NotaryServer
NotarySigner
Portal
Registry
RegistryController

And an other definition Harbor which can handle all of them.
BTW with multiple controllers this would reconcile faster.

Work has been done!


Make all queues seleced by default

Currently, when queues are displayed, they are not selected. As there are many queues, it is good to have them selected when they are displayed.

it's good idea.


Add bc to nv_fuse_read.sh path

Description of changes
The nv_fuse_read.sh shell script (in l4t-tools) expects bc to be in PATH.

Testing
Tested on a fused xavier-agx and an unfused orin-agx.

Looks pretty unobjectionable.


Bring tar runfiles up to feature parity with pkg_files.runfiles.

This change changes pkg_tar to use add_label_list to process srcs. That brings it in conformance with pkg_files and pkg_zip. That changes the behavior of runfiles to be useful, but it is a breaking change.
Fixes: ????
Other bits:

do not fail verify_archive_test without a min_size or max_size
fix bug in runfiles support where files were not added to file_deps list.
buildifier to make the linters happy

@aiuto what's needed to make this draft Ready for review? We're eager to get this in to fix python images.

The refactoring PR #756 has to go in first. Then I need to rebase on that and add a legacy option.
It would also help if #749 were in too, then I can import to Google and test the legacy option.
About a day's work, when I get back from vacation.

@aiuto both PRs are merged, is there anything we could do to help with this?

I'm waiting on  https://github.com/bazelbuild/rules_pkg/pull/784 so CI can
be green again.
On Mon, Nov 20, 2023 at 10:42 AM Diego Ortin @.***>
wrote:

@aiuto https://github.com/aiuto both PRs are merged, is there anything
we could do to help with this?
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/754#issuecomment-1819311287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHCZTEFVZURSOGMMSFDYFN263AVCNFSM6AAAAAA44DUYAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZGMYTCMRYG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

will this change be pulled into an official release sometime soon? looks like the latest was from may

Now that we are past the bazel 7 release and the holidays it might be time
for a new one.
It needs a little CI work first to make sure we are testing with bazel 6
(wihout bzlmod)
and 7 with both bzlmod and without.
Just a matter of an afternoon of grunt work.
On Mon, Jan 1, 2024 at 5:11 PM Connor Latham @.***>
wrote:

will this change be pulled into an official release sometime soon? looks
like the latest was from may
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/pull/754#issuecomment-1873500732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHCV67TBH5WWB2JVVQDYMMYAZAVCNFSM6AAAAAA44DUYAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGUYDANZTGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Add method check for _notify_skeleton_bones_renamed.

Adds check for existence of _notify_skeleton_bones_renamed method when walking nodes in PostImportPluginSkeletonRenamer. Silences errors and closes https://github.com/godotengine/godot/issues/83148

Did you see this alternative PR? #83149

Hmm, I didn't actually. It's somewhat hard to say which is a more appropriate fix. Hypothetically with this approach, you could allow other nodes which could consume this event, but honestly, I think any approach to this would be fine since this is just one relatively bespoke notification event. If we changed this to a cast, even though it's exclusively an editor only thing, we could remove an extra method bind I guess.

Okay, I've modified it now to remove the bind, and use casting instead. I didn't put the change @dpalais made in case you want to merge that seperately, though I can put it in mine too if you'd prefer this all be one PR. It's not strictly nessecary, but it results in less looping and feels like good practice.

Oh, I could have sworn I put the include in the right order. I think my IDE did something strange. Anyway, it's resolved now.

Oh, another minor thing I missed: got of the redunant vargs since we don't need them anymore.

Thanks!


Fix url fragment without query

Change Summary
Fixes the URL regex to correctly parse URLs with a fragment but no query string.

Related issue number
Fixes #2168

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] (n/a) Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

Looks good to be, I'll merge when I next go though PRs.

thanks so much.

thanks so much.


Missing info about .NET 6 required dependencies on "Install .NET on Windows" page

.NET 6 preview 1 is out and supports same Windows versions as .NET 5.
So I suppose that Install .NET on Windows page should be updated with information about .NET 6 required dependencies for Windows 7/Vista/8.1/Server 2008 R2/Server 2012 R2.
They are the same as for .NET 5 or there are differences?

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

ID: 1eeab451-820f-de42-983e-4d0d5764f6ab
Version Independent ID: d11d0d14-8a03-50e4-5c00-9a4417ad4d0a
Content: Install .NET on Windows
Content Source: docs/core/install/windows.md
Product: dotnet
Technology: dotnet-install
GitHub Login: @adegeo
Microsoft Alias: adegeo

The Supported OS information on the dotnet github wiki is generally the source of truth. Considering .NET 5 is supported until a few months after .NET 6 is released, they generally should have the same requirements related to OS. The only thing that could possibly be different is if the dependencies change a bit with .NET 6, choosing a better library, or a new feature requires something. If a new OS version comes out close to the end of .NET 5, I could see that being excluded.


Error when creating new secret

When creating new secret, I get error "(intermediate value).custom_metadata is undefined". Secret actually has been created, just need to manually refresh netbox page.

i have a feeling this might be related to the vault API not returning the custom metadata after saving.
what version of vault are you running?
if this still happens would you be able to show the output of the API call that is made on the click on "Save"? you should be able to get it from your browser's devtools.

I have a similar problem, but the error message is different.
I'm getting this error message

:
Vault v1.10.2 (94325865b12662cb72efa3003d6aaa4f5ae57f3a)
Netbox (v3.2.1)
API call for "Save"
Vault_plugin_Save.zip

The vault server needs to be at least 1.9 to support custom_metadata.  The custom_metadata fields are silently ignored before that.  With v1.8.7 on the server, I experienced the exact same error message.  When I upgraded to 1.10.4 the error went away.
You can test this from the command line using:
vault kv metadata delete secret/test-secret
vault kv metadata put -custom-metadata=foo=abc -custom-metadata=bar=123 secret/test-secret
vault kv metadata get secret/test-secret
The output should have:
custom_metadata         map[bar:123 foo:abc]
If not then the vault server needs to be upgraded.

I solved the problem what I indicated.
In my case, the error was that the vault used KV secrets engine with version 1.
After I converted KV secrets engine version 1 to version 2, the plugin will work without error.
Check KV secrets version:
vault secrets list -detailed
The working result:
secret / kv kv_670cf333 system system false replicated false false map [version: 2] n / a
Upgrading from version 1 to version 2:
https://www.vaultproject.io/docs/secrets/kv/kv-v2#upgrading-from-version-1

thanks for digging into it! i might add a note to the readme.


[CENNSO-1370] Remove interface stats increment from upf nodes

They broken (wrong iface_id, missed cache flush), never worked and shouldn't be here in the first place. Since they increase software interface stats and this should be done once in input nodes.

@mogaika which stats/metrics are affected by this change?

@mogaika which stats/metrics are affected by this change?

None, this is remove of leftover from gtpu plugin which upg was based on


Common: Refacor index pages

Content now starts in the middle of the page. Put things into tabs with some kind of "welcome" tab and the others with data:

Done.


Swift build error

Hi,
I get the following error when I run "swift build".
/rainbow/Server/.build/checkouts/Kitura-Credentials.git-1137106172743287290/Sources/Credentials/TypeSafeCredentials.swift:48:38: error: use of undeclared type 'TypeSafeMiddleware'
public protocol TypeSafeCredentials: TypeSafeMiddleware, Codable {
                                     ^~~~~~~~~~~~~~~~~~
/rainbow/Server/.build/checkouts/Kitura-Credentials.git-1137106172743287290/Sources/Credentials/TypeSafeCredentials.swift:85:111: error: use of undeclared type 'RequestError'
    public static func handle(request: RouterRequest, response: RouterResponse, completion: @escaping (Self?, RequestError?) -> Void) {
                                                                                ^~~~~~~~~~~~
error: terminated(1): /usr/local/Cellar/swift/4.1/Swift-4.1.xctoolchain/usr/bin/swift-build-tool -f /Users/upkar/Documents/code-upkar/rainbow/Server/.build/debug.yaml main output:

Swift version
$ swift --version
Swift version 4.1 (swift-4.1-RELEASE)
Target: x86_64-apple-darwin17.4.0

I am new to swift to fix the code quickly. Thank you for your help !

I added the following import code to TypeSafeCredentials.swift and resolved the
Use of undeclared type 'RequestError'
import KituraContracts
I then removed the unused variable TypeSafeMiddleware from the TypeSafeCredentials protocol and resolved the undeclared type error and the server code compiled successfully, HOWEVER, I'm not sure if this has any impact to the functioning of this protocol but it appears to be unused
public protocol TypeSafeCredentials: TypeSafeMiddleware, Codable {
Use of undeclared type 'TypeSafeMiddleware',
The new line of code now looks like
public protocol TypeSafeCredentials: Codable {
This also resolved the conversion to Swift 4 errors and the conversion ran successfully


⚠ Samsung has degraded performance

In afa43a0, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2386 ms

Resolved: Samsung performance has improved in eaf0ef8.


[Snyk] Security upgrade lodash from 4.17.4 to 4.17.17

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

application/server/testdata/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

768/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Prototype Pollution SNYK-JS-LODASH-6139239
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Add INSERT IGNORE option

This change is

Coverage remained the same at 93.883% when pulling ee3149a41667982aee20a7ca7d55acfd9c5b0e6a on Judokus:patch-1 into 14f1c2d600b97276529571f4ae623a60403ae1a3 on voku:master.

do we really need to discard insert errors?
-> maybe we can use a array instead, so that we can also handle e.g.: LOW_PRIORITY | DELAYED | HIGH_PRIORITY


Support max-size and size modifiers to limit token length

Description
Linked issue: #219
Definition of Done

[x] I read contributing.md
[x] There are no TODOs left in the code
[x] Code style follows the tinylog standard
[x] All classes and methods have Javadoc
[x] Changes are covered by JUnit tests including edge cases, errors, and exception handling
[x] Maven build works including compiling, tests, and checks (mvn verify)
[x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation
Additions or amendments for the public documentation:
Optionally, the minimum (`min-size`)/maximum (`max-size`)/fixed size (`size`) of a placeholder or a group of placeholders can be defined. For example, this is useful to format placeholders as columns.

Example:

writer        = console
writer.format = {{level}:|min-size=8,max-size=10} {message}

Agreements

[x] I agree that my changes will be published under the terms of the Apache License 2.0 (mandatory)
[x] I agree that my GitHub user name will be published in the release notes (optional)

Thank you for the quick adding of the both tests. There are just two Checkstyle violations:
Error:  src/test/java/org/tinylog/pattern/MaximumSizeTokenTest.java:[21,1] (imports) ImportOrder: Wrong order for 'java.sql.PreparedStatement' import.
Error:  src/test/java/org/tinylog/pattern/SizeTokenTest.java:[21,1] (imports) ImportOrder: Wrong order for 'java.sql.PreparedStatement' import.

Fixed them already. Sorry, seems that my local formatting settings are not working properly.

Awesome, thank you!


[WIP] National Minimum Wage update

In general this looks like a big improvement on #2419 - I found it much easier to follow in terms of the structure of the commits.
As I mention in a couple of the (large) commits which change the regression test artefacts, I can't be completely confident that all the changes are intentional. However, as long as the Content Team and/or the relevant Department are happy that the functionality is as required, I think this should be OK to merge.

I expect you're already aware, but GitHub is indicating that there are conflicts between this branch and master which will need resolving before it can be merged.

Other than my comments above, I'm happy for this to be merged.

Thanks for your review @floehopper, and for your comments on #2419. It might be interesting to write in our docs the approach that smart-answers is following when facing commits granularity (small vs squashed commits) cc/@chrisroos? It might help other devs to follow the same approach.
I have tackled all your comments, so I will rebase with master and force push in preparation for merging.

Thanks for your review @floehopper, and for your comments on #2419. It might be interesting to write in our docs the approach that smart-answers is following when facing commits granularity (small vs squashed commits) cc/@chrisroos? It might help other devs to follow the same approach.
I have tackled all your comments, so I have rebased with master and force pushed in preparation for merging.

I had already added this Trello card and I've just added this other one to write-up some documentation about the structure of commits.


[T6A1][W13-C4]

Hi Akshay ^^

@Zhiyuan-Amos @ylhlh @edmundmok @fisherhx
Some comments added. Please ack & close the PR after reading comments.

walao why Akshay never comment on my part at all sia

your code flawless nothing to improve on

lol! let me pick on you next week ;-)
On Sun, Oct 2, 2016 at 10:29 AM, Edmund Mok<EMAIL_ADDRESS>wrote:

your code flawless nothing to improve on
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/nus-cs2103-AY1617S1/addressbook-level3/pull/732#issuecomment-250949813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-eBpyHHP9YlYgk3x1C-i8lgmC1cPmHks5qvxclgaJpZM4KIayC
.


Fix dense layer instantiation for io_serial mode

A few things needed to make serial mode work well for dense layers:

Partition the "flattened" weight vector correctly
Edit the softmax operation in serial mode so it accesses the input in sequential order
Add a RESOURCE directive to instantiate weights into BRAMs if requested

As best as I can tell, the 1layer and 3layer example projects are working well with these updates. Item 2 should be compatible with parallel mode -- but I have not gotten a chance to test this yet so I'll take an action to exercise softmax with io_parallel before the PR gets merged.
The end result appears to be working as expected and completes both the synthesis and RTL simulation successfully... Honestly, the performance vs resource tradeoffs we can evaluate using the reuse_factor is WAY better than anything I had in the old RFNOC repo :)

I tested serial and parallel mode and it seems fine.
For parallel mode, I had to add this line to the tcl which is part of a larger issue we need to discuss with Xilinx
config_array_partition -maximum_size 4096
But this is a different issue.  As far as serial mode goes, I think this is ready to merge.
@ejk43 do you want test anything else?

@nhanvtran  Nothing else on my end-- thanks for checking out parallel mode!
Agree this is good to go for now.


Better Response for NoneType is not Callable

Context

A somewhat common and mystifying error that new zappa devs run into is the "NoneType is not callable" There are a few ways we could make this clearer, so I just wanted to make an issue talking about where this occurs and see what the right way to solve it is.
Expected Behavior

When an error occurs, provide appropriate and helpful messaging.
Actual Behavior

When zappa fails to load the underlying application, it stores the application as None. Subsequent calls to the application yield the error above.
During handler initialization, the self.wsgi_app property gets set here:
https://github.com/Miserlou/Zappa/blob/master/zappa/handler.py#L129
Initial calls to the handler yield a 500 server error, this is different from the NoneType error above, but most devs never encounter this due to zappa's "touch": true default setting. This error is encountered by zappa and not the dev.
Because the warm handler is reused, the self.wsgi_app property is None (handler initialization crashed during touch/cold-start). The handler has already been initialized, and so crashes when it attempts to get a response from this app:
https://github.com/Miserlou/Zappa/blob/master/zappa/handler.py#L448
Possible Fix

There are quite a few reasons why the app my not load. While missing packages is the most common I've experienced and seen on slack/issues, it certainly isn't the only one. So fixing this gets a little tricky. Currently we just tell people to look at zappa tail. This honestly answers most of the questions but it feels like some people either don't do it until told by the community or have difficulty in debugging the error it printed out. So there are a few possible fixes with the sole aim of helping people debug.

Do nothing. We tell people already to check out zappa tail and they might just need to put in the hard work of debugging.

For the most part, these errors are caused by ImportErrors that get raised up to the tail end of the init() method. We could catch ImportErrors and provide slightly better reporting in the response. Import errors are usually a result of the environment differences between lambda, their local package, and the packages that we put on lambda via manywheel or Miserlou/lambda-packages.

We could check in the handle() method if self.wsgi_app exists and provide a little more explicit response there.

We could attampt to call the handler during zappa update/zappa deploy with the pre-zipped project directory in an attempt to encounter any import errors prior to deployment. This might not work though because the packages that we're testing against were meant for Lambda and not the local environment. Might cause more issues than it solves.

Steps to Reproduce

Deploy the example app: https://github.com/Miserlou/Zappa/tree/master/example
Add a line to the app.py file to import some_unknown_package
Call zappa update to put the missing package code online

Your Environment

Zappa version used: 0.43.2
Operating System and Python version: OSX

👍

I would like to share my experience as a user:

I got the "NoneType is not Callable" error yesterday after I deployed the application and tried it via curl.
The first thing I did was zappa tail but the events that were visible (at the bottom) were not very helpful to find the problem (more on this later).
After that I started googling and found many issues in this projects that were related. I figured out that it is a generic error and that it can be related to imports failing.
I found that my application was missing a local module, but after I added it I was still getting the error.
At some point I looked at zappa tail again. This time I kept it running a bit longer, I noticed that it was refreshing, and that you could scroll up.
When I scrolled all the way up to the top I found that scipy was not being found. This was interesting because it was installed in the virtual environment.
I remembered that there was a configuration setting to avoid using the precompiled packages. Disabling it fixed the issue.

Given my experience yesterday, I have these suggestions:

In general, make it easier for the user to find the errors when using zappa tail. It could be interesting to be able to filter events that are not related to errors (for example when you get events related to the warm up script). At least newbies could be informed that they may need to scroll up quite a bit before they can find the error cause.
When there is a "NoneType is not Callable" error, the user could get some generic information, for example

This error is generated when zappa fails to load the underlying application. In most cases, this is caused by ImportErrors.
and/or add a link to a documentation page (FAQ or similar).

I received this error due to having a duplicated function name. More useful error messaging would be very helpful if possible.


include the snapshot image name in the PR comment so it is easier to …

…pull and test the image locally

@rawlingsj fabric8/fabric8-ui:SNAPSHOT-PR-2066-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2066-fabric8-planner.badger.fabric8.io

@rawlingsj fabric8/fabric8-ui:SNAPSHOT-PR-2066-2 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2066-fabric8-planner.badger.fabric8.io

@rawlingsj fabric8/fabric8-ui:SNAPSHOT-PR-2066-3 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2066-fabric8-planner.badger.fabric8.io


fix(link): fixing github redirecting links

Description

Fixed the edit-page-config.json file to fix the issue
changed page in the href key to markdown

Related issue(s)
Fixes #3067

CC: @derberg @akshatnema

@akshatnema dunno why Lighthouse CI is failing even for small change is there any way to fix ?

Thanks for the change, @DhairyaMajmudar. Can you please dig into the issue further as I just found out some other docs edit links are broken. For example: https://www.asyncapi.com/docs/tools/generator/asyncapi-document link should have an edit link to https://github.com/asyncapi/generator/blob/master/apps/generator/docs/asyncapi-document.md but is instead https://github.com/asyncapi/generator/tree/master/docs/asyncapi-document.mdx which is wrong.
There might be other such links, which you would need to find out.

Thanks for the change, @DhairyaMajmudar. Can you please dig into the issue further as I just found out some other docs edit links are broken. For example: https://www.asyncapi.com/docs/tools/generator/asyncapi-document link should have an edit link to https://github.com/asyncapi/generator/blob/master/apps/generator/docs/asyncapi-document.md but is instead https://github.com/asyncapi/generator/tree/master/docs/asyncapi-document.mdx which is wrong. There might be other such links, which you would need to find out.

Sure thing 👍🏻

@DhairyaMajmudar  just check all the links and report them here after that have we can see that need to change only the config or the gh action ferentor '

Hi, @anshgoyalevil @sambhavgupta0705 I checked the links and did the needy changes in config files bu the bug still exists since the links generated redirects to .mdx files instead of .md
The reason behind is their declaration in the posts.json file but since it is mentioned in .gitignore I am not able to commit the changes in that file.

Hi, @anshgoyalevil @sambhavgupta0705 I checked the links and did the needy changes in config files but the bug still exists since the links generated redirects to .mdx files instead of .md
The reason behind is their declaration in the posts.json file but since it is mentioned in .gitignore I am not able to commit the changes in that file.

@sambhavgupta0705 just a friendly ping on this.

@derberg we need your suggestion here

you also need to update the component responsible for edit link: https://github.com/asyncapi/website/blob/master/components/layout/DocsLayout.tsx#L53

@DhairyaMajmudar any updates on the PR?

@DhairyaMajmudar any updates on the PR?

I'm still unsure of this https://github.com/asyncapi/website/pull/3071#issuecomment-2222107745

@akshatnema @sambhavgupta0705 I've fixed the problem stated in https://github.com/asyncapi/website/pull/3071#issuecomment-2220436121 now links are working as expected, can you pls. review the PR.

@DhairyaMajmudar
add config for glee docs


Compiling the project on a machine with only VS 2017

Running build.ps1 on a machine with only VS 2017 fails as Cake finds the wrong msbuild.exe (http://stackoverflow.com/a/34364698 notes that the msbuild.exe in C:/WINDOWS... is pre-C# 6, and hence does not understand string interpolation).
When I run build.ps1 with -Verbosity Diagnostic it get
...
========================================
Build
========================================
Executing task: Build
Executing: "C:/WINDOWS/Microsoft.NET/Framework64/v4.0.30319/MSBuild.exe" /v:minimal /nr:false /p:Configuration="Release" /p:Platform="Any CPU" /target:Build "C:/Temp/nunit-gui/nunit-gui.sln"
Microsoft (R) Build Engine version 4.6.1586.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

  nunit.uikit -> C:\Temp\nunit-gui\bin\Release\nunit.uikit.dll
Views\AddinPages\ExtensionNodeView.cs(92,34): error CS1056: Unexpected character '$' [C:\Temp\nunit-gui\src\nunit-gui\nunit-gui.csproj]

Lifting the Cake version to 0.19.1 (from 0.15.2) solves the problem.
...
========================================
Build
========================================
Executing task: Build
Executing: "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/MSBuild/15.0/Bin/amd64/MSBuild.exe" /v:minimal /nr:false /p:Configuration="Release" /p:Platform="An
y CPU" /target:Build "C:/Temp/nunit-gui/nunit-gui.sln"
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.

  nunit.uikit -> C:\Temp\nunit-gui\bin\Release\nunit.uikit.dll
  nunit-gui -> C:\Temp\nunit-gui\bin\Release\nunit-gui.exe
  mock-assembly -> C:\Temp\nunit-gui\bin\Release\mock-assembly.dll
  nunit-gui.tests -> C:\Temp\nunit-gui\bin\Release\nunit-gui.tests.dll

I think the problem was solved by cake-build/cake#1369 and related issues.

@mikkelbu I added you to the gui team, which gives you write access to the  repository if you need it.
You can continue to work in your own fork or you can create branches in the main nunit-gui repo. Either way, the process is the same, with a PR needed before merging. Using a branch in the main repo is handy in that we will see your work in progress and it's also possible for two committers to share work in the same branch. Additionally, you'll find you can now assign issues to yourself.

@CharliePoole Thanks. I'll assign myself to the issues that I've made PR for.


Modify Force Calculator

I feel we can make one force calculator which can do the following operations:

Calculate force as F = ma
Calculate force as F = p/t
Calculate electric force as F = kq1q2/r^2
Calculate gravitational force as F = Gm1m2/r2
Calculate magnetic force as F = BIl => F = magnetic flux density * length of rod * current

Plus make the page responsive for all devices. As a result, we can also remove the preexisting force and gravitation force calculator from the repo. I can do this under JWOC'23.

I am already working on F=ma one..it is almost done

then let me add my calculator..ideally this issue will be valid only when force calculator is added....

@Srijita-Mandal
I would like to work on this under JWOC