Tapping TextFormField throws _CastError was thrown during method call TextInputClient.performPrivateCommand type 'Null' is not a subtype of type 'Map<String, dynamic>'

Steps to Reproduce

Use an Android 5 device e.g. HTC One M1
Execute flutter run on the code sample
Just Tap inside the form field. It will throw

The issue only occurs on Flutter 3.3, it works fine on 3.0...
Expected results:
No error should occur
Actual results:
_CastError was thrown during method call TextInputClient.performPrivateCommand: type 'Null' is not a subtype of type 'Map<String, dynamic>' in type cast

Code sample
void main() => runApp(const TextInputErrorHome());

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(primarySwatch: Colors.blue),
      home: const TextInputErrorApp(),
    );
  }
}

class TextInputErrorApp extends StatefulWidget {
  const TextInputErrorApp({super.key});

  @override
  State<TextInputErrorApp> createState() => _TextInputErrorAppState();
}

class _TextInputErrorAppState extends State<TextInputErrorApp> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Padding(
          padding: const EdgeInsets.all(20.0),
          child: Column(
            children: [
              TextFormField(
                decoration: const InputDecoration(
                    hintText: 'Tap here it will throw',
                    label: Text('Numeric keyboard')),
                keyboardType:
                    const TextInputType.numberWithOptions(decimal: true),
              ),
              const SizedBox(height: 30),
              TextFormField(
                decoration: const InputDecoration(
                    hintText: 'Tap here it will throw',
                    label: Text('Normal keyboard')),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

Logs
======== Exception caught by services library ======================================================
The following _CastError was thrown during method call TextInputClient.performPrivateCommand: type 'Null' is not a subtype of type 'Map<String, dynamic>' in type cast

When the exception was thrown, this was the stack:
#0      TextInput._handleTextInputInvocation (package:flutter/src/services/text_input.dart:1823:28)
#1      TextInput._loudlyHandleTextInputInvocation (package:flutter/src/services/text_input.dart:1701:20)
#2      MethodChannel._handleAsMethodCall (package:flutter/src/services/platform_channel.dart:536:55)
#3      MethodChannel.setMethodCallHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:529:34)
#4      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:387:35)
#5      _invoke2 (dart:ui/hooks.dart:186:13)
#6      _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
#7      _Channel.push (dart:ui/channel_buffers.dart:132:31)
#8      ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17)
#9      PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:599:22)
#10     _dispatchPlatformMessage (dart:ui/hooks.dart:89:31)
call: MethodCall(TextInputClient.performPrivateCommand, [2, {action: com.htc.sense.ime.getInputExtras}])

flutter analyze
Analyzing issue_reproducibles...
No issues found! (ran in 3.6s)

flutter doctor -v
[√] Flutter (Channel stable, 3.3.5, on Microsoft Windows [Version 10.0.19044.2130], locale en-US)
[√] Flutter (Channel stable, 3.3.5, on Microsoft Windows [Version 10.0.19044.2130], locale en-US)
    • Flutter version 3.3.5 on channel stable at c:\Apps\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d9111f6402 (5 days ago), 2022-10-19 12:27:13 -0700
    • Engine revision 3ad69d7be3
    • Dart version 2.18.2
    • DevTools version 2.15.0

[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at c:\Apps\Android\Sdk
    • Platform android-33, build-tools 32.0.0-rc1
    • ANDROID_HOME = c:\Apps\Android\Sdk
    • Java binary at: c:\Apps\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2021.3)
    • Android Studio at c:\Apps\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[√] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at c:\Apps\JetBrains\IntelliJ IDEA 2021.1
    • 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

[√] Connected device (3 available)
    • Windows (desktop) • windows      • windows-x64    • Microsoft Windows [Version 10.0.19044.2130]
    • Chrome (web)      • chrome       • web-javascript • Google Chrome 106.0.5249.119
    • Edge (web)        • edge         • web-javascript • Microsoft Edge 104.0.1293.47

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

! Doctor found issues in 1 category.

Hi @absar, I can not reproduce the issue on the latest stable and master channels.
My device: Samsung Galaxy Tab A7 Lite, Android 12 OneUI 4.1, SM-T225
Does this issue only happen with the numeric keyboardType? Also, please retry on the latest master channel to see if the issue still reproduces.

Hi @huycozy, as mentioned in the steps the issue is on Android 5 which is API level 21. Since flutter supports Android API 16 (Android 4.1) & above, it should work on Android 5.
Regarding keyboardType and master channel, I will have to check and comeback to you

Issue occurs with both numeric and text keyboardType, and default type as well, sample source code updated in OP
Issue occurs on Flutter channels stable and beta
Issue does not occur on Flutter channel master

@absar thanks for verifying on all channels.
Given your last message, I feel safe to close the issue as fixed on the master channel. The fix should land on the stable channel in future releases.

@huycozy please mention the commit/PR in which it is fixed, as it's a regression for us, it is flooding crashlytics with crashes. Since the fix is not even on beta channel it means it might take at least a quarter to land on stable. If it is related to https://github.com/flutter/flutter/pull/113553 it should be cherry picked into stable

Given the error message, the fix seems to be https://github.com/flutter/flutter/pull/112590


Write a PHP program to move all zeroes to end of array

Description
Write a PHP program to move all zeroes to end of array
Input  : arr[] = {1, 2, 0, 4, 3, 0, 5, 0};
Output : arr[] = {1, 2, 4, 3, 5, 0, 0, 0};

Input  : arr[] = {1, 2, 0, 0, 0, 3, 6};
Output : arr[] = {1, 2, 3, 6, 0, 0, 0};

How to contribute

Comment !assign to assign this issue to yourself
Fork this repository
Create a new branch
Save the solution in program/program/move-all-zeroes-to-end-of-array/move_all_zeroes_to_end_of_array.php
Commit the changes
Create a pull request

!assign


Use uint16 for Checksum fields instead of byte slice

Using byte slice for Checksum fields is just not very efficient as we need to allocate a slice for a 2Bytes field, plus the util.Checksum function returns a uint16 value that we then convert to slice before writing it to a buffer.

New slayers implementation uses uint16


False negative for D403 when the first sentence only has one word but the whole docstring is longer

D403 has a false negative when the docstring’s first word (tokenized by spaces) is not ASCII alphabetic and the docstring either contains a space or doesn’t end with ASCII terminal punctuation. This is similar to #10775. #10776 only fixed the case where a docstring contains no spaces and ends with ASCII terminal punctuation.
In the following example, f1 has a true positive and f2 has a false negative.
$ ruff --version
ruff 0.6.3
$ cat d403.py
def f1():
    """footles."""
def f2():
    """footles.

    This is a no-op.
    """
$ ruff check -q --output-format concise --isolated --select D403 d403.py
d403.py:2:5: D403 [*] First word of the first line should be capitalized: `footles` -> `Footles`

The current behavior is insofar intentional that it matches pydocstyle
We would have to take a closer look why pydocstyle deliberately excludes all first words that contain any non ASCII characters.

Ruff’s D403 already doesn’t match pydocstyle: Ruff flags f1 and pydocstyle doesn’t. This is intentional due to #10775. As long as Ruff’s behavior is different, I think it should be self-consistent.


Can epoll directly monitor the io_uring_fd, or does it need to be done indirectly through evenfd?

Multiple io_uring instance,  one thread consumer;
Can epoll directly monitor the io_uring_fd, or does it need to be done indirectly through evenfd?
Can this epoll be replaced with io_uring?

Epoll can directly monitor the io_uring_fd.


Reduce Travis impact

We have a machine running daily builds with a number of no- options.  There is no need to have them run in Travis as well.  Also, there is no need to run the fuzz corpus tests in every build.

I've a private Travis build here that will finish much earlier than the current OpenSSL builds...

Here is an idea. [skip ci] is handy, but you tend to forget it. What if there was reverse option, i.e. you'd have to opt-in for full test. I mean majority of builds would go through reduced/minimalistic procedure, preferably with --strict-warning. Unless a commit is marked with easy-to-forget tag. This should be possible to arrange in script: section. I mean script would simply look at last commit and not call make if there is no tag. In dream-land there is button that says CI to run remaining tests...

Sure.  Are you willing to implement that, @dot-asm?

I can throw in proof-of-concept into #2292...

Sounds like a good idea

As for strict warnings. With risk that it was discussed too, why not "flip" situation with --strict-warnings? I mean now it's used sporadically, and question is if it should rather be everywhere [as opposite to sporadically] but possibly one target. [And purpose of having one target without --strict-warnings is to quickly assess if problem is syntax or warning.] --strict-warning is not any harder on CPU and problems would have to be addressed anyway...

As for strict warnings. With risk that it was discussed too, why not "flip" situation with --strict-warnings? I mean now it's used sporadically, and question is if it should rather be everywhere [as opposite to sporadically] but possibly one target. [And purpose of having one target without --strict-warnings is to quickly assess if problem is syntax or warning.] --strict-warning is not any harder on CPU and problems would have to be addressed anyway...

I'm all for that

Yes, flipping it is a very good idea!

Ha, but note that --strict-warnings turns on DPEDANTIC which can cause completely different code paths to be taken, see e.g. https://github.com/openssl/openssl/blob/master/crypto/poly1305/poly1305.c#L98
So, we need to test both flavours. Or give up on -pedantic?

Ha, but note that --strict-warnings turns on DPEDANTIC which can cause completely different code paths to be taken

And this of course was discussed too. I shouldn't have taken the risk :-) Apologies again. But on the other hand it might be appropriate to revisit this from time to time. How about following set for minimal testing: "bare-bone" ./config, then no-asm -Werror and no-asm --strict-warnings? First one is "most popular platform", second one is "max C coverage but with -Werror" and third is "max pedantic C coverage". And "minimal" is kind of hint toward #2292. Yeah, what about no-this-or-that... Maybe it would be more appropriate to add a tag to commit message that would pass specific flag? I mean if one fixes specific no-this-or-that, then just setup that specific run with additional flag passed through tag in commit message?

Since #2292 is committed this needs to be re-based, if not simply closed. Minimal testing in referred request include straight no options, no-asm -Werror, no-asm --strict-warnings, enable-tls1_3 --strict-warnings with gcc-5, --strict-warnings with clang-3.6, no-stdio with mingw32 compiler. Last one is basically to have a 32-bit test. no-asm is to maximize C code expose to warnings. Default CPU time per merge request is taken down to ~30 minutes from >2 hours, with option to opt-in for ~1.5 hour test.

Closing

I figured that after #2292, there wasn't anything more that this PR could contribute with.


Restic fixes: pruning, process substitution (take 2)

Motivation for this change
I rebased https://github.com/NixOS/nixpkgs/pull/44203 and replace some if expressions with optionals/optionalString/optionalAttr.
The result is untested.
cc @jerith666 @bbigras
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Can you add https://github.com/jerith666/nixpkgs/commit/dc6616b190e0aa6670324ad5078b365dd39fd402 to this PR please?

@GrahamcOfBorg test restic

@GrahamcOfBorg test restic

@GrahamcOfBorg test restic

thanks @Mic92 :heart:

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/126


How to sample from batch OT if batch size used for compute OT is large than training batch?

Hi, how to sample from batch OT if batch size used for compute OT is large than training batch? For example, I use batch size 128 to compute batch OT, then should I sample 32 from this OT for training repeat 4 times or I sample from it only once?

Hi!
Both are mathematically valid. I have personally opted for the latter as it is easier to implement, and is fine as long as the OT is very fast relative to the model. I suspect that the former might be slightly better in some circumstances, but I don't think it should matter too much. To me it is the same question as to whether you should train your neural network by randomly sampling examples at each step, or pre-shuffle an epoch of data and run through the entire thing. Both can give satisfactory results.

Hi @atong01, thank you for your prompt response!
I believe the key consideration between these two options is data loading efficiency. The latter approach may significantly increase loading time. I'm curious why you suspect the former might be slightly better? From my perspective, if we employ replaceable sampling, both methods should yield similar results.

Yes, very possible. In this case I was assuming loading time was not a bottleneck. If it is than the former should be preferred. Definitely similar results. I think you would only see differences in big datasets with a small number of epochs (where you may miss some datapoints by chance with replaceable sampling.


[auto-merge] bot-auto-merge-branch-23.04 to branch-23.06 [skip ci] [bot]

auto-merge triggered by github actions on bot-auto-merge-branch-23.04 to create a PR keeping branch-23.06 up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

SUCCESS - auto-merge


Architecture - Explore MVI

A great article if you're familiar with Rx, MVP, and MVC: https://hannesdorfmann.com/android/model-view-intent/


Audit fix

Ran npm audit fix then lets see how the open renovate PRs pan out.

Tagging @maoo  here


PDS4 Information Model Release <IP_ADDRESS>

Automated tagging of repo for nominal release of sub-model for PDS4 Release <IP_ADDRESS>

closing sub-model is not ready for production


Add CONTRIBUTING.md

Describe the ideal solution or feature request
Add CONTRIBUTING.md according to https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors
Difficulty, impact, and usage score

Technical difficulty
User goals
Usage frequency

Small
Important to help and guide contributors
Daily

How does this tie into our current application?
It helps contributors improve this project.

Can i work on this?

@salted0dreams Go for it!

This should also mention an explicit style guide like https://peps.python.org/pep-0008/


Is there any process on @optional member? [14402]

Is there an already existing issue for this?

[X] I have searched the existing issues

Expected behavior
the @optional member which is not present, shall be omitted from the serialization.
Current behavior
the @optional member which is not present, would be serialized by default value.

Steps to reproduce

generate code from IDL
new non-optional member instance
send sample

Fast DDS version/commit
FastDDS 2.6.0
Platform/Architecture
Ubuntu Focal 20.04 amd64, Windows 10 Visual Studio 2019
Transport layer
UDPv4
Additional context
According to “Extensible and Dynamic Topic Types for DDS，Version 1.2”Standard, there are three encoding.

XML configuration file
No response
Relevant log output
No response
Network traffic capture

Hi @ilikecola,
I have just moved the issue to the proper repository. Regarding your issue, the @optional annotation is not currently supported by Fast DDS-Gen as it is stated in the documentation. If you are interested into moving this feature implementation forward in our development timeline, you may consider contacting our support team.

@ilikecola
Latest Fast DDS-Gen v3.0.0 introduces support for @optional annotation. Enjoy!


Add custom subsection group prefix title support

*Issue number of the reported bug or feature request: Closes #11
Describe your changes
The purpose is detailed in issue #11, this change adds the option group_title_prefix which accepts a string. If not provided, the prefix added to titles of groups subsections is the <prog> itself, but providing some string, this prefix will be changed, without overriding the #<prog>-... in hrefs.
Testing performed
Multiple tests added.
Additional context
setdefault is not allowed by flake8-spellcheck.

Alternatively, we could also make this a boolean and, if set, strip both the entry point and the sub-command.

I like the idea, I will implement it as soon as possible :+1:

I've implemented group_sub_title_prefix as a string parameter, just like group_title_prefix.

https://pypi.org/project/sphinx-argparse-cli/1.7.0/


Update auth, dynamodb, s3, sqs to 2.17.115

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.66 to 2.17.115.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #811.


fix reDOS CVE in getColor function

Short description
This fixes CVE-2024-25885 mentioned in issue #783
Proposed changes

Length Limitation: Restricted the input string length to 100 characters to avoid excessively long inputs.
Optimized Regular Expression Usage: Replaced the search method with match for more controlled matching and proper validation.

Resolved issues
Fixes: #783

hi @luisza, when will this be released?


Update OMERO.tables 5.1 docs

Documentation for openmicroscopy/openmicroscopy#3249 (includes breaking changes)
--no-rebase

Looks fine except for the noted discrepancy where it looks like the keyname would be needed to get a specific property?

Fixed.

Happy with this now @rleigh-dundee ?

@hflynn Yes, looks fine, thanks.  Good to merge.


support get image from VirtualMachineImages API endpoint

The Java SDK entry point to the virtual machine image management API com.microsoft.azure.management.compute.VirtualMachineImages only supports listing of images.
I would like to see the full API implemented, or at least a get method to retrieve meta data about a particular image (and, implicitly, find out if it exists).

it's all there. See:

VirtualMachineImages#getImage(...)
VirtualMachineImages#publishers()
VirtualMachinePublisher#offers()
VirtualMachineOffer#skus()
VirtualMachineSku#images()

So it seems, indeed. I guess they've been added after v1.0.0-beta3, which is the version I'm using (the latest released version?).
http://azure.github.io/azure-sdk-for-java/com/microsoft/azure/management/compute/VirtualMachineImages.html

I see. Indeed. We're about to release beta4. What's in master right now is practically it.


weather platforms still using mdi:weather-partlycloudy

Home Assistant release with the issue:

98.1
Last working Home Assistant release (if known):
never
Operating environment (Hass.io/Docker/Windows/etc.):

hass.io
Component/platform:

Description of problem:
naming for the mdi:weather-partly-cloudy has been change for the sensor weather, but the mapping in the weather platforms still uses mdi:weather-partlycloudy.
This forces user to create unnecessary complex templates
      weather_dark_sky_icon:
        friendly_name_template: >
          {{states('sensor.weather_dark_sky_icon').split('weather')[1]|replace('-',' ')|title}}
        value_template: >
          {% set mapper =
            {'clear-day': 'sunny',
             'clear-night': 'night',
             'sunny': 'sunny',
             'rain': 'rainy',
             'snow': 'snowy',
             'sleet': 'snowy-rainy',
             'wind': 'windy',
             'fog': 'fog',
             'cloudy': 'cloudy',
             'partlycloudy': 'partly-cloudy',
             'partly-cloudy-day': 'partly-cloudy',
             'partly-cloudy-night': 'night-partly-cloudy',
             'hail': 'hail',
             'thunderstorm': 'lightning',
             'tornado': 'hurricane'} %}
          {% set state = states('weather.home_darksky') %}
          {% set weather = mapper[state] if state in mapper else 'sunny-alert' %}
            mdi:weather-{{weather}}

when wanting to show dynamic icons the front-end could be as easy as:
            icon: >
              var weer = entity['weather.dark_sky'].state;
              weer;

would be more consistent if all weather sensors, and platforms use the mdi methodology with the dash '-' between words.
No mapping would then be required any longer, unless in the case of non-existent mdi icons.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
            icon: >
              var weer = entity['weather_dark_sky'].state;
              weer;

Traceback (if applicable):

Additional information:
please see: https://github.com/home-assistant/home-assistant/pull/26274#issuecomment-526407449

This is incorrect.  The state is partlycloudy in the backend, but it maps to mdi:weather-partly-cloudy in the frontend.
Id recommend instead that the sensors use the weather platform mapping.  That way both could be updated centrally.

Why are you opposed to adapting both sensors and weather platforms use the HomeAssistant wide used methodology of a dash between words?
It would be so much more consistent.
The central approach you suggest could indeed be a great improvement, so yes , hope we can agree on that. Though I would not be able to describe how that could be achieved. Let alone the fact that the sensors have way more states than the weather components.
Still, if you check the Darksy component, my suggestion for the added dash in the state would only be needed in 1 case, partlycloudy (even the auto correct  of the editor sees that....) that really would be a quick and very useful fix.

please keep open until https://github.com/home-assistant/architecture/issues/321 is resolved


APP loading launch time

I noticed on startup the app takes approximately 20+ seconds to load, is there a way for me to debug this process with more granularity as it seems too long, I would like to provide feedback on each stage to the user of the app as to why it's taking long to load or actions that occur in the background. On the web page it loads quite quickly but, on the app, it is much to slow on startup. Any feedback or way to improve this issue would be appreciated (currently building on android but will be building for iOS soon too)

Hi @Mark-MV-Wizard,
Here you can find info about how to debug performance issues https://docs.flutter.dev/perf


 The specified VPC has no internet gateway attached.Update the VPC and then try again

This was resolved by adding an internet gateway with public subnet <IP_ADDRESS>/0.  This resolved this issue.

https://stackoverflow.com/questions/27635030/cannot-create-a-publicly-accessible-dbinstance-because-customer-vpc-has-no-aws


where to find the cross compile guide?

I didn't find it on this page, https://developer.arm.com/products/processors/machine-learning/arm-nn
or this one, https://developer.arm.com/technologies/machine-learning-on-arm/developer-material/how-to-guides
Thanks very much

Hi @fcyella, are you referring to https://github.com/ARM-software/armnn/blob/master/BuildGuideAndroidNDK.md?
You should be able to adapt those instructions for other targets as you require.

Hi @fcyella,
I hope you've found the guide Matteo was referring to. Please open a new one if you have any problems.
Thanks,
Surabhi


Unexpected behaviour in the coverage of the lines of the test functions

While checking a crate for its test coverage I saw that custom panic messages in test functions are counted as uncovered lines. Is this expected behavior and is already a way to fix this?
Below is a screenshot of a simplified example:

This means that some of the code generated by the assert_eq macro is not covered, but I believe this is an upstream bug anyway. (It is somewhat similar to https://github.com/rust-lang/rust/issues/98712.)
Would you mind submitting an issue at https://github.com/rust-lang/rust?

Closing in favor of upstream bug report (https://github.com/rust-lang/rust/issues/84892).


error with apm package installation from cmd windows 10

i would want to install https://atom.io/packages/autocomplete-python via apm with command prompt windows 10. when i  write it there's problem like this.

Maybe you are behind a firewall?

Thanks for the report! Can you re-open this in https://github.com/atom/apm if there's no existing issue already so we have it in the right place?  Please fill out the issue template as well and let us know if there's anything interesting about your network setup like if you're behind a proxy/firewall (thanks @serafeimgr :v:).


Consider switching publisher to Red Hat

While I developed this extension I do think it would be much better to publish it from either already existing Red Hat publisher or by creating a new Ansible, or Ansible Community publisher, one where @gundalow will also be fallback admin.
I am personally inclined to find the Red Hat publisher better because it would send a very good positive message about Red Hat contributions in general.
In fact, I would not even mind to transfer the github repository to @redhat-developer github organization if that is required.
My personal take is is may be better to keep it under @ansible-community because here are all the Ansible specific knowledge is involved and I expect that most contributors are likely to know more about Ansible than about JavaScript.
Obviously that we first need to find-out if Red Hat folks are going to welcome us.

I already got some progress on this front, mainly this will likely happen once the extension matures a little bit. There will be implications for the users as the extension id can be updated.

I will be closing this issue because there is no action expected yet with the note that it will happen.

Reopening as we got the green light to start that process.

Reopening as we got the green light to start that process.


Do not check if table exist from KafkaTableManager

Build will fail with:
ERROR: for runner  b"pull access denied for prestodev/centos6-oj8, repository does not exist or may require 'docker login'"

So we need to migrate to use ghcr.io/trinodb/testing/ images.

Please rebase

Merged, thanks


Add sqlite feature flag and document own store implementation

I think currently rusqlite comes in both the CLI and the library. We use it to run integration tests for example. It's sort of our "default" store implementation. That's why I find it reasonable to put it under a sqlite feature flag. Perhaps it's better to make an issue to address this in the documentation as well as putting the sqlite store under a feature flag. What do you think?

Originally posted by @mFragaBA in https://github.com/0xPolygonMiden/miden-client/pull/262#discussion_r1576711473

As a part of this, we may want to break out dependencies which are needed for the CLI binary and then turn on relevant features for a specific use case.

This should be closed once #367 is merged.

Closed by https://github.com/0xPolygonMiden/miden-client/pull/367


[feat]: Stepper UI component

Feature description
Is it possible to implement a stepper using components already in shadcn
e.g. Googel Maps

e.g. GMPRO Viewer

Affected component/components
No response
Additional Context
No response
Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues and PRs

i like this

PR #318


Parameters for expert policy

Dear authors,
Hi. Thank you for sharing your codes.
Recently, I've been interested in MAGAIL and tried to reproduce your results.
Firstly, I tried to train expert policy as recommended in README.md by python -m sandbox.mack.run_simple, but I failed. I thought there is a problem on action dimension, so I made all actions as multi-hot vectors and modified relevant terms. After training with MACK, however, it seems like agents cannot recover the appropriate policies similar to MADDPG.
So I wonder whether it is possible to share the weight files of expert so that readers can simply generate expert trajectories.
Thanks.

Also have a problem on action dimension when running codes follows README.md, with some private path problems...

@wsjeon Hi! May I ask if you eventually came up with weights with good performance (for expert trajectories with MACK)?
I am currently running the cooperative navigarion  "simple___spread" environment, and all losses rise at some point

@wsjeon @Ericonaldo An update for the code: I found new implementation of MAGAIL used for the new paper of ermongroup here. The paper is "Multi-Agent Adversarial Inverse Reinforcement Learning".
Results of execution are similar to new paper, but I cannot reach the results of MAGAIL paper (based on the paper "Multi-Agent Generative Adversarial Imitation Learning").
Anyone reached performance from this paper with MAGAIL?

Hi all!
I am a rookie in Deep Reinforcement Learning.
Here is a problem when I were running python -m sandbox.mack.run_simple.
Here is the log:
logging to: /atlas/u/lantaoyu
Traceback (most recent call last):
  File "/home/teng/anaconda3/envs/tensorflow/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/teng/anaconda3/envs/tensorflow/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/teng/Desktop/MA-AIRL-master/multi-agent-irl/sandbox/mack/run_simple.py", line 63, in <module>
    main()
  File "/home/teng/.local/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/teng/.local/lib/python3.6/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/home/teng/.local/lib/python3.6/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/teng/.local/lib/python3.6/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/teng/Desktop/MA-AIRL-master/multi-agent-irl/sandbox/mack/run_simple.py", line 58, in main
    train(logdir + '/exps/mack/' + env_id + '/l-{}-b-{}/seed-{}'.format(lr, batch_size, seed),
TypeError: must be str, not NoneType

Did you have the same problem?


Vendored HdrHistogram_c library build error on FreeBSD.

Seems to be an issue with hdr_endian.h and not having the right defined(__FreeBSD__) or redefining what is present in <sys/endian.h>
Relevant log section and full logs
[ 69%] Linking C executable hdr_histogram_log_test
*** Error code 1

Stop.
make[2]: stopped in /src/_build/default/lib/libhdr_histogram/_build
*** Error code 1

Stop.
make[1]: stopped in /src/_build/default/lib/libhdr_histogram/_build
*** Error code 1

Stop.
make: stopped in /src/_build/default/lib/libhdr_histogram/_build
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:51:10: warning: 'be16toh' macro redefined [-Wmacro-redefined]
#       define be16toh(x) betoh16(x)
               ^
/usr/include/sys/_endian.h:111:9: note: previous definition is here
#define be16toh(x)      __bswap16((x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:52:10: warning: 'le16toh' macro redefined [-Wmacro-redefined]
#       define le16toh(x) letoh16(x)
               ^
/usr/include/sys/_endian.h:114:9: note: previous definition is here
#define le16toh(x)      ((uint16_t)(x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:10: warning: 'be32toh' macro redefined [-Wmacro-redefined]
#       define be32toh(x) betoh32(x)
               ^
/usr/include/sys/_endian.h:112:9: note: previous definition is here
#define be32toh(x)      __bswap32((x)

        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:55:10: warning: 'le32toh' macro redefined [-Wmacro-redefined]
#       define le32toh(x) letoh32(x)
               ^
/usr/include/sys/_endian.h:115:9: note: previous definition is here
#define le32toh(x)      ((uint32_t)(x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:10: warning: 'be64toh' macro redefined [-Wmacro-redefined]
#       define be64toh(x) betoh64(x)
               ^
/usr/include/sys/_endian.h:113:9: note: previous definition is here
#define be64toh(x)      __bswap64((x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:58:10: warning: 'le64toh' macro redefined [-Wmacro-redefined]
#       define le64toh(x) letoh64(x)
               ^
/usr/include/sys/_endian.h:116:9: note: previous definition is here
#define le64toh(x)      ((uint64_t)(x))
        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:273:24: warning: implicit declaration of function 'betoh16' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be16toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:51:21: note: expanded from macro 'be16toh'
#       define be16toh(x) betoh16(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:282:24: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be32toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:291:24: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be64toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:380:22: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_len = be32toh(compression_flyweight->length);
                     ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:404:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:478:25: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_length = be32toh(compression_flyweight->length);
                        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:503:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:580:25: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_length = be32toh(compression_flyweight->length);
                        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:604:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:674:42: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compression_cookie = get_cookie_base(be32toh(compression_flyweight->cookie));
                                         ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
16 warnings generated.
/src/_build/default/lib/libhdr_histogram/src/hdr_time.c:80:2: warning: #warning is a language extension [-Wpedantic]
#warning "Platform not supported\n"
 ^
/src/_build/default/lib/libhdr_histogram/src/hdr_time.c:80:2: warning: "Platform not supported\n" [-W#warnings]
2 warnings generated.
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:51:10: warning: 'be16toh' macro redefined [-Wmacro-redefined]
#       define be16toh(x) betoh16(x)
               ^
/usr/include/sys/_endian.h:111:9: note: previous definition is here
#define be16toh(x)      __bswap16((x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:52:10: warning: 'le16toh' macro redefined [-Wmacro-redefined]
#       define le16toh(x) letoh16(x)
               ^
/usr/include/sys/_endian.h:114:9: note: previous definition is here
#define le16toh(x)      ((uint16_t)(x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:10: warning: 'be32toh' macro redefined [-Wmacro-redefined]
#       define be32toh(x) betoh32(x)
               ^
/usr/include/sys/_endian.h:112:9: note: previous definition is here
#define be32toh(x)      __bswap32((x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:55:10: warning: 'le32toh' macro redefined [-Wmacro-redefined]
#       define le32toh(x) letoh32(x)
               ^
/usr/include/sys/_endian.h:115:9: note: previous definition is here
#define le32toh(x)      ((uint32_t)(x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:10: warning: 'be64toh' macro redefined [-Wmacro-redefined]
#       define be64toh(x) betoh64(x)
               ^
/usr/include/sys/_endian.h:113:9: note: previous definition is here
#define be64toh(x)      __bswap64((x))
        ^
In file included from /src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:33:
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:58:10: warning: 'le64toh' macro redefined [-Wmacro-redefined]
#       define le64toh(x) letoh64(x)
               ^
/usr/include/sys/_endian.h:116:9: note: previous definition is here
#define le64toh(x)      ((uint64_t)(x))
        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:273:24: warning: implicit declaration of function 'betoh16' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be16toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:51:21: note: expanded from macro 'be16toh'
#       define be16toh(x) betoh16(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:282:24: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be32toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:291:24: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
        h->counts[i] = be64toh(counts_data[i]);
                       ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:380:22: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_len = be32toh(compression_flyweight->length);
                     ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:404:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       d
fine be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:478:25: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_length = be32toh(compression_flyweight->length);
                        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:503:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:580:25: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compressed_length = be32toh(compression_flyweight->length);
                        ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:604:32: warning: implicit declaration of function 'betoh64' is invalid in C99 [-Wimplicit-function-declaration]
    lowest_discernible_value = be64toh(encoding_flyweight.lowest_discernible_value);
                               ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:57:21: note: expanded from macro 'be64toh'
#       define be64toh(x) betoh64(x)
                          ^
/src/_build/default/lib/libhdr_histogram/src/hdr_histogram_log.c:674:42: warning: implicit declaration of function 'betoh32' is invalid in C99 [-Wimplicit-function-declaration]
    compression_cookie = get_cookie_base(be32toh(compression_flyweight->cookie));
                                         ^
/src/_build/default/lib/libhdr_histogram/src/hdr_endian.h:54:21: note: expanded from macro 'be32toh'
#       define be32toh(x) betoh32(x)
                          ^
16 warnings generated.
/src/_build/default/lib/libhdr_histogram/src/hdr_time.c:80:2: warning: #warning is a language extension [-Wpedantic]
#warning "Platform not supported\n"
 ^
/src/_build/default/lib/libhdr_histogram/src/hdr_time.c:80:2: warning: "Platform not supported\n" [-W#warnings]
2 warnings generated.
ld: error: undefined symbol: hdr_gettime
>>> referenced by hdr_histogram_log_test.c
>>>               CMakeFiles/hdr_histogram_log_test.dir/hdr_histogram_log_test.c.o:(writes_and_reads_log)
>>> referenced by hdr_histogram_log_test.c
>>>               CMakeFiles/hdr_histogram_log_test.dir/hdr_histogram_log_test.c.o:(log_reader_aggregates_into_single_histogram)

ld: error: undefined symbol: betoh32
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed) in archive ../src/libhdr_histogram_static.a
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed_v0) in archive ../src/libhdr_histogram_static.a
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed_v0) in archive ../src/libhdr_histogram_static.a
>>> referenced 14 more times

ld: error: undefined symbol: betoh64
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed_v0) in archive ../src/libhdr_histogram_static.a
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed_v0) in archive ../src/libhdr_histogram_static.a
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(hdr_decode_compressed_v1) in archive ../src/libhdr_histogram_static.a
>>> referenced 6 more times

ld: error: undefined symbol: betoh16
>>> referenced by hdr_histogram_log.c
>>>               hdr_histogram_log.c.o:(apply_to_counts_16) in archive ../src/libhdr_histogram_static.a
cc: error: linker command failed with exit code 1 (use -v to see invocation)
jail: /usr/bin/su -l opam -c cd '/src' && env OCAMLCI='true' CI='true' DEPS='base-bigarray.base base-domains.base base-nnp.base base-threads.base base-unix.base bigarray-compat.1.1.0 conf-cmake.1 conf-libffi.2.0.0 conf-pkg-config.3 conf-zlib.1 csexp.1.5.2 ctypes.0.21.1 ctypes-foreign.0.21.1 dune.3.12.1 dune-configurator.3.12.1 integers.0.7.0 ocaml.5.1.1 ocaml-base-compiler.5.1.1 ocaml-config.3 ocaml-options-vanilla.1 stdlib-shims.0.3.0' OPAMCOLOR='always' CLICOLOR_FORCE='1' '/usr/bin/env' 'bash' '-c' 'opam exec -- dune build @install @check @runtest && rm -rf _build': failed
"jail" "-c" "name=obuilder_42916_5323" "mount.devfs" "path=/obuilder/result/b9ebe90c59d7f9cf5474c58f73e70627d6f5f7c4138592dc1278c5391df10c1f/rootfs" "vnet" "exec.start=/sbin/ifconfig lo0 <IP_ADDRESS>/8" "command=/usr/bin/su" "-l" "opam" "-c" "cd '/src' && env OCAMLCI='true' CI='true' DEPS='base-bigarray.base base-domains.base base-nnp.base base-threads.base base-unix.base bigarray-compat.1.1.0 conf-cmake.1 conf-libffi.2.0.0 conf-pkg-config.3 conf-zlib.1 csexp.1.5.2 ctypes.0.21.1 ctypes-foreign.0.21.1 dune.3.12.1 dune-configurator.3.12.1 integers.0.7.0 ocaml.5.1.1 ocaml-base-compiler.5.1.1 ocaml-config.3 ocaml-options-vanilla.1 stdlib-shims.0.3.0' OPAMCOLOR='always' CLICOLOR_FORCE='1' '/usr/bin/env' 'bash' '-c' 'opam exec -- dune build @install @check @runtest && rm -rf _build'" failed with exit status 1
2023-12-20 05:42.05: Job failed: Failed: Build failed
2023-12-20 05:42.05: Log analysis:
2023-12-20 05:42.05: >>> : error: undefined symbol: hdr_gettime (score = 10)
2023-12-20 05:42.05: >>> : error: undefined symbol: betoh32 (score = 10)
2023-12-20 05:42.05: >>> : error: undefined symbol: betoh64 (score = 10)
2023-12-20 05:42.05: >>> : error: undefined symbol: betoh16 (score = 10)
2023-12-20 05:42.05: >>> : error: linker command failed with exit code 1 (use -v to see invocation) (score = 10)
2023-12-20 05:42.05: undefined symbol: hdr_gettime

Ouch. I don't have a FreeBSD machine (or the FreeBSD foo) to work on a fix. Would @dustanddreams know what the fix should be here?

Ouch. I don't have a FreeBSD machine (or the FreeBSD foo) to work on a fix. Would @dustanddreams know what the fix should be here?

DragonFlyBSD and FreeBSD can use the same construct as OpenBSD. The following diff ought to fix this:
diff --git lib/libhdr_histogram/src/hdr_endian.h lib/libhdr_histogram/src/hdr_endian.h
index 839fdb1..6276fab 100644
--- lib/libhdr_histogram/src/hdr_endian.h
+++ lib/libhdr_histogram/src/hdr_endian.h
@@ -38,15 +38,15 @@
 #      define __BYTE_ORDER    BYTE_ORDER
 #      define __BIG_ENDIAN    BIG_ENDIAN
 #      define __LITTLE_ENDIAN LITTLE_ENDIAN
 #      define __PDP_ENDIAN    PDP_ENDIAN

-#elif defined(__OpenBSD__)
+#elif defined(__DragonFly__) || defined(__FreeBSD__) || defined(__OpenBSD__)

 #      include <sys/endian.h>

-#elif defined(__NetBSD__) || defined(__FreeBSD__) || defined(__DragonFly__)
+#elif defined(__NetBSD__)

 #      include <sys/endian.h>

 #      define be16toh(x) betoh16(x)
 #      define le16toh(x) letoh16(x)

Fixed.


Ambiguous digitalized button

Based on user testing that said the button is a bit ambiguous since it does not redirect to any page.
I guess I will make it a default red or green color and nonclickable, so that user know that it is meant to be showing status of digitalization only.

@KamiliArsyad I need your help in this. So I think I decided to make it a popover instead. Like if you click the button it will have a little textbox popup that explain more about the digitalization. But then it seems that I cannot enable the popup to work. I noticed that for this page we kind of still use Bootstrap (?) so I choose to work the Bootstrap way.
First I have added the popper script (since for popover the kind of relying on popper.
<script
  src="https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>  integrity="sha384-Xe+8cL9oJa6tN/veChSP7q+mnSPaj5Bcu9mPX5F5xIGE0DVittaqT5lorf0EI7Vk"
  crossorigin="anonymous"
>

Then I have also added this code inside the script:
  const popoverTriggerList = document.querySelectorAll('[data-bs-toggle="popover"]')
  const popoverList = [...popoverTriggerList].map(popoverTriggerEl => new bootstrap.Popover(popoverTriggerEl))

And then finally for the button it will look something like this for the code:
        <button
          type="button"
          class={
            business.has_digitalized
              ? "btn btn-success"
              : "btn btn-danger"
          }
          data-bs-toggle="popover"
          data-bs-title="Digitalization status"
          data-bs-content={
            business.has_digitalized
              ? "Congrats! You are digitalized!"
              : "First next big step: digitalize your business!"
          }
        >
          {business.has_digitalized ? "Digitalized" : "Not Digitalized"}
        </button>

But somehow still cannot? I have followed the Bootstrap documentation and watch the tutorial, but it still cannot functions so I am wondering if there is some conflict? FYI I do this inside the new-features branch.

I am not sure about Bootstrap, but shouldn't the button be wrapped inside an OverlayTrigger component? Also the button should be Bootstrap's button imported from react-bootstrap and not the default html button.
Btw are you sure the tutorial you're following is a React JS tutorial? Some syntaxes don't seem very familiar to me

side note btw: Chakra's popover is far easier to code and it's only like a 3 minute code


ffcv with torch.Tensor

Hi
I have a dataset in the form of 'torch.Tensor' and was wondering how to use the DatasetWriter? I am trying to use FFCV for SimCLR, where dataset is torch.utils.data.Dataset, including pairs of augmented images in tensor.
I tried different options like RGBImageFields but this does not work as the inputs are tensors, not images, getting this error
TypeError: Unsupported image type <class 'torch.Tensor'>
writer = DatasetWriter(write_path, {         'image': RGBImageField(),         # 'image': FloatField(),         # 'image':NDArrayField(shape=(2,), dtype=np.dtype('float64')),         'label': IntField()     }, num_workers=16)

Hi @rahimentezari ! Sorry for the very late response -- you should use the NDArrayField and convert the torch tensors to numpy arrays with .numpy().


Replace WinRT clipboard API with Win32 for pasting

The Win32 API is significantly faster than the WinRT one, in the order
of around 300-1000x depending on the CPU and CPU load.
This might slightly improve the situation around #15315, but I suspect
that it requires many more fixes. For instance, we don't really have a
single text input "queue" into which we write. Multiple routines that
resume_background just to WriteFile into the input pipe are thus
racing against each other, contributing to the laggy feeling.
I also fear that the modern Windows text stack might be inherently
RPC based too, producing worse lag with rising CPU load.
This might fix #14323
Validation Steps Performed

Paste text from Edge ✅
Paste text from Notepad ✅
Right click the address bar in Explorer, choose "Copy address",
paste text into WT ✅

I am curious about the "what if the source hangs while we're reading it" question - maybe there's a space for us to wrap this up as an AsyncAction that we can cancel if it doesn't return.

I recently changed this PR to yield to the background thread and untagged #15315 as being fixed, so it won't hang the UI anymore. We can't use an AsyncAction, because there's no way to cancel reading from the clipboard. It'll simply time out after 30s (as guaranteed by the win32 API). To us this doesn't really matter, because WinRT calls OLE and OLE calls the Win32 API which also hangs for 30s. It's a matryoshka.

That's probably not as expensive as all the other COM calls.

Not even remotely. Even with yielding to a background thread first the total latency is still 20000% faster than the WinRT API on average (using percentages makes it look a bit funnier 😄).

Honestly though I'm not super familiar with the edge cases with the win32 API so I'm not sure what we have to be afraid of.

The worst that can happen is that it works as bad as the conhost implementation, but the only major complaint we've ever gotten there is that pasting breaks Unicode, but that has always been our own fault (TextToKeyEvents being UCS-2). On that note I've just noticed that I should use wcsnlen and not wcslen to protect ourselves against strings without null terminator.

@zadjii-msft @DHowett It'd be great if we could still get this into 1.19. We've been testing it for quite a bit already after all. It's missing just 1 more approval.

This one is from before the CI rewrite so it might need to be manually merged...


Powershell Constrained Language Mode is inconsistent between process and hyperv isolation.

Describe the bug
When building a docker image with --isolation hyperv the Powershell Constrained Language Mode is altered.
To Reproduce
PS > docker run --isolation hyperv --entrypoint powershell mcr.microsoft.com/windows/servercore:ltsc2022 echo $ExecutionContext.SessionState.LanguageMode
ConstrainedLanguage

Ok.
PS > docker run --isolation process --entrypoint powershell mcr.microsoft.com/windows/servercore:ltsc2022 echo $ExecutionContext.SessionState.LanguageMode
ConstrainedLanguage

Ok.
FROM mcr.microsoft.com/windows/servercore:ltsc2022
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
RUN echo $ExecutionContext.SessionState.LanguageMode

PS > docker build --isolation process  --no-cache=$true .
Sending build context to Docker daemon  2.048kB
Step 1/3 : FROM mcr.microsoft.com/windows/servercore:ltsc2022
 ---> 06bb218927a8
Step 2/3 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
 ---> Running in f14e82e8b8b4
Removing intermediate container f14e82e8b8b4
 ---> d56812725126
Step 3/3 : RUN echo $ExecutionContext.SessionState.LanguageMode
 ---> Running in 8ad9e234c89f
ConstrainedLanguage

Ok.
PS > docker build --isolation hyperv  --no-cache=$true .
Sending build context to Docker daemon  2.048kB
Step 1/3 : FROM mcr.microsoft.com/windows/servercore:ltsc2022
 ---> 06bb218927a8
Step 2/3 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
 ---> Running in b5ae063e8187
Removing intermediate container b5ae063e8187
 ---> e1c015c0bc2e
Step 3/3 : RUN echo $ExecutionContext.SessionState.LanguageMode
 ---> Running in b46656491282
FullLanguage

What?
Expected behavior
Constrained Language Mode should be consistent between docker build and docker run.
Constrained Language Mode should be consistent between --isolation process and --isolation hyperv
Configuration:
Windows Version	10.0.22621 Build 22621
Image mcr.microsoft.com/windows/servercore                     ltsc2022                         06bb218927a8
Container engine: docker
PS > docker version
Client:
 Cloud integration: v1.0.24
 Version:           20.10.17
 API version:       1.41
 Go version:        go1.17.11
 Git commit:        100c701
 Built:             Mon Jun  6 23:09:02 2022
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.10.1 (82475)
 Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.24)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:03:58 2022
  OS/Arch:          windows/amd64
  Experimental:     false

Hey @judyliu-ms, any thoughts on this?

Hi @mbelt thanks for capturing this, we will be investigating internally - for MS folks internal tracking #43089806

For the first issue - Constrained Language Mode should be consistent between docker build and docker run:

PowerShell on Windows Containers defaults to FullLanguage and is consistent between docker run and docker build. This can be confirmed by running the same command on cmd instead of PowerShell : docker run --isolation hyperv --entrypoint powershell mcr.microsoft.com/windows/servercore:ltsc2022 echo $ExecutionContext.SessionState.LanguageMode
In PowerShell, the above command is impacted by variable substitution so when Language Mode on the host is ConstrainedLanguage  we effectively run echo ConstrainedLanguage
This is not unique to the LanguageMode and can be reproduced using $HOME variable as well and you'll get the host home path instead of the container:  docker run --isolation hyperv --entrypoint powershell mcr.microsoft.com/windows/servercore:ltsc2022 echo $home


Fabo/769 tx history

Closes #769
Description:
Reenable tx history querying

❤ Thank you!

Dependend on https://github.com/cosmos/cosmos-sdk/pull/1260


Extension for conceptual dictionary

Most of the needed terminology is focused on the Input/Output Parameter or Calculated property
Here we collect the classes to be added. Hierarchy for the properties will be discussed at a later point.
@srmnitc please add here

Related to DFT (VASP) jobs:

Superclass
Label
Definition
Comment

Calculated Property
Total Energy

Calculated Property
Potential Energy

Calculated Property
Pressure

Calculated Property
Volume

Related to DFT (VASP) jobs:

Superclass
Label
Definition
Comment

Calculated Property
Total Energy

Calculated Property
Potential Energy

Calculated Property
Pressure

Calculated Property
Volume

Output Parameter
Number of ionic steps

Related to MD (LAMMPS) jobs:

Superclass
Label
Definition
Comment

Calculated Property
Temperature

Output Parameter
Number of ionic steps

Output Parameter
Initial/Final???

Related to EOS jobs:

Superclass
Label
Definition
Comment

Input Parameter
Number of data points

Input Parameter
Volume range

Related to ThermodynamicIntegration jobs:

Superclass
Label
Definition
Comment

CalculatedProperty
FreeEnergy

PhysicalProperty
Temperature

PhysicalProperty
Volume

currently labelled AtomicVolume since its vol/atom

also simulation cell lengths as before..

For LAMMPS:
A major category we are missing are thermostats/barostats. We should consider if we want to add somethings like hasThermostat -> Langevin etc, and same for Barostat. We should discuss..

@Tara-Lakshmipathy @pkruzikova After going through the OpenBis data model, this is the proposed update to the ontology. There are still some points to be discussed. If you have any suggestions or comments, please feel free to add here!

MASS?

Did we agree on a strategy for periodic boundaries?

An additional, PeriodicBoundaryConditions -> PeriodicityinXdirection , similarly for Y and Z will be added.

Ok, this is the schematic for the new classes. I'll go ahead with the changes now.


[Smoke Tests] Remove Explicit Azure.Core Reference

Summary
The focus of these changes is to remove the explicit references to the Azure.Core package; these can cause the run to fail when rewritten for daily runs due to existing project references to Azure.Core.

/azp run net - smoke-tests


Sometimes the wrong options are shown

Hi @wouterpeere,
Sometimes the wrong options are shown for the selected options. This issue seems to be fixed by show and hide the linked options if the main options is shown/hidden.
With best regards
@tblanke

Hi @tblanke, thanks for noticing this. Can you elaborate on how you can repoduce this error?
I will take a closer look at it, in the beginning of January!
Best regards,
Wouter

First delete the backup.
Then select determine borehole depth and the L4 sizing method
Then select determine temperature profile
And no peak length is displayed.

@tblanke, indeed, I noticed this also. However, when you selected L4 sizing, you most likely also loaded an hourly profile. Then, when switching to 'determine temperature profile' the hourly profile still is loaded, making the 'peak length' option obsolete.

@tblanke, while working on #61 it seems like this is a more logical behavior. I will open the PR.


ISO 8601 parser. Wanted feature?

So, I wrote an ISO 8601 subset parser for my own purposes, and I was wondering it it's a wanted feature? Personally I've ended up needing it everywhere I use chronoutil.
Currently it doesn't support decimals or weeks, because I didn't need either, but I could add those and submit a PR if it's wanted.

Hey, thanks for this and sorry it's taken so long to get back to you.
Serialisation / deserialisation for durations has come up a couple of times. My main argument for not including it is that chrono doesn't include anything for their own durations, but also it's not a great standard. However I'm willing to include it if we can get a "good enough" implementation.
There are a few thorny issues to solve - namely:

dealing with negative durations (I believe not part of the standard)
excluding fractional durations (P0,5Y is valid iso8601, but we don't allow fractions of years or months due to ambiguity)
decide on the relativeduration -> iso representation - should we map 13 months to P1Y1M or `13M? should this be configurable?

No worries! And thanks for getting back to me.

Do you have a particular viewpoint on negative durations? Personally I would not be inclined to support them at all, since the standard doesn't seem to specify a format for them. I would just return an error on attempt to serialise a negative duration.
I would put a warning in the docs and error on deserialisation.
I think there should be one canonical representation, and it should be the simplest. IMO this is start with the largest increment, and set it to its max before going to the next. So in the case of your example, P1Y1M.

I'll also add a fourth thorny issue:
4. What to do about weeks (the spec allows for things like P5W)? For deserialisation, I think it should be ok to just times by 7 and this as days the the chrono duration. For serialisation I don't think we should use weeks at all.

a lot of prior art tends to allow negative duration serialisation/deserialisation (in that sense it's an extension to the standard - see e.g. momentjs https://momentjs.com/docs/#/durations/) - I'd be tempted to go the same route (perhaps strict serialisation could be an optional feature)
nice, that's probably as good as we can get
yes, one canonical representation is good. Since Duration and RelativeDuration I think store everything in the min increment, I think it will be easier on a first pass to use just do that - so P13M etc.
good catch - yes multiplying by 7 works nicely

Ok, it seems like we have a clear path forward. I’m a little busy right now, but I’ll refine my implementation and file a PR when i have time

Thanks! No rush :)


Fix gpuci versions

This fixes the current fail in main with CUDA 11.5 in gpuCI (which is down to a bad CI setup / configuration), and adds support for the CUDA Toolkit 12.3 supported compute capabilities.
Notes:

gpuCI now passes with this fix, the Windows fails are due to the issue that will be fixed by #9449
I've marked it as "skip release notes" because it's only a fix for CI, plus a change to the CC matrix that makes no functional difference for users of CTK 12.3 at this time - Numba would have correctly inferred the supported range for 12.3 already anyway.

gpuci run tests

gpuci run tests


Decompiler interprets SHUFPS Z values as 0.

Describe the bug
A clear and concise description of the bug.
To Reproduce
Steps to reproduce the behavior:

Compile

#include <cstdio>
#include <xmmintrin.h>

int func(const __m128 v)
{
    __m128 x = _mm_shuffle_ps(v, v, 0x00);
    __m128 y = _mm_shuffle_ps(v, v, 0x55);
    __m128 z = _mm_shuffle_ps(v, v, 0xAA);

    __m128 s = _mm_add_ps(x, y);
    s = _mm_add_ps(s, z);

    return _mm_cvtt_ss2si(s);
}

int main(int argc, char** argv)
{
    __m128 v = _mm_setr_ps(30 * argc, 0.3 * argc, 0.4 - argc, 0);
    int sum = func(v);
    printf("Result: %d", sum);

    return 0;
}

Compile with MSVC (any version, at least from 2013 to latest)
The disassembly should say something akin to _func__cdecl_int_char_ptr("Result: %d",(int)((float)_Argc * 0.3 + (float)(_Argc * 30) + 0.0));. Note the incorrect 0.0 in place of 0.4 - (float)_Argc.

Expected behavior
It appears that the result of SHUFPS XMM#, 0xAA gets turned into 0.0, which is very difficult to work with for many executables. Here's a direct example below:
Screenshots

File:

Language ID: x86:LE:64:default (2.13)
Compiler ID: windows
Processor: x86
Endian: Little
Address Size: 64

Environment:

OS: Windows 11 22621.963
Java Version: openjdk 19 2022-09-20
Ghidra Version: 10.2.2
Ghidra Origin: https://github.com/NationalSecurityAgency/ghidra/issues/releases

Thanks for reporting this.  There's an issue with the generated pcode; should be an easy fix.


Fix CompressionAdapter interface definition

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixes #556

Please merge this


downloadToFile (Cloud-Storage) creates empty file when files does not exists in bucket

Environment details

OS: RHEL 7
PHP version: PHP 7.2
Package name and version: google/cloud-storage 1.22

Steps to reproduce

Download a non existing file
Exception is thrown, but there is a 0-size file created anyway

Code example
 $object = $bucket->object('non-existing-files.txt');
 $object->downloadToFile('download/non-existing-files.txt');

IMHO the file should never be created when an exceptions rises. Right now I'm catching the exception, but I have to remove the empty file afterwards.

@rodehoed in cases where you do not know ahead of time that the requested file exists, you should use StorageObject::exists() to check its status prior to calling the download method.
$object = $bucket->object('non-existing-files.txt');
if ($object->exists()) {
	$object->downloadToFile('download/non-existing-files.txt');
} else {
	throw new \Exception('Object does not exist!');
}

@dwsupplee I'm not a fan of wrapping the exists() check into the download method since it seems to me that the majority of cases would know the existence status before downloading. I think this is something we should explain in the documentation. WDYT?

Hi,
Thanks for your prompt answer. I could use the exist function.....
I'm fine with the current exception.
But my main concern, when the download fails for whatever reason (not only
because it doesn't exist) it should not write an empty file.
Op vr 28 aug. 2020 15:19 schreef John Pedrie<EMAIL_ADDRESS>
@rodehoed https://github.com/rodehoed in cases where you do not know
ahead of time that the requested file exists, you should use
StorageObject::exists() to check its status prior to calling the download
method.
$object = $bucket->object('non-existing-files.txt');if ($object->exists()) {
$object->downloadToFile('download/non-existing-files.txt');
} else {
throw new \Exception('Object does not exist!');
}
@dwsupplee https://github.com/dwsupplee I'm not a fan of wrapping the
exists() check into the download method since it seems to me that the
majority of cases would know the existence status before downloading. I
think this is something we should explain in the documentation. WDYT?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/google-cloud-php/issues/3347#issuecomment-682562354,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRWVQ23UVOED4AJURCM2YTSC6VF3ANCNFSM4QN5IC5Q
.

@rodehoed sorry for coming late to the issue. I understand the reason for insisting on not creating an empty file.
I have raised a potential fix for this.


.dart and .dartServer is stored in home folder on macOS

On macOS, Dart stores data in the unconventional folders ~/.dart and ~/.dartServer. This contributes to a mess where app files are scattered everywhere, the home folder is cluttered, and backups get filled with unnecessary junk.
This should be fixed and moved to proper paths, like ~/Library/Application Support, ~/Library/Caches and ~/Library/Preferences.

Dart SDK version: 2.17.1 (stable) (Tue May 17 17:58:21 2022 +0000) on "macos_x64"
macOS 10.15

Not sure who uses .dart, but .dartServer sounds like the analysis server.

.dart seems to be for user-level settings. If .dartServer is for the analysis server, is there a different repo this should be reported in?

Yes, .dartServer is from the analysis server, and this repo is the right place for reporting the issue.
There's a larger conversation happening about unifying all of our tools and cleaning up where we're putting temporary files. Unfortunately, I don't remember who's leading that effort.

@mit-mit Do you remember where this was recently discussed?
Assigning p3 until I can figure out what the larger plan is.

I think there was some discussion about this for pub, @jonasfj ?
I think we might be able to create a package with FFI for determining the canonical folders for each host OS?

See: https://github.com/dart-lang/sdk/issues/41560#issuecomment-919071070
But that's really only for configuration.
There is XDG specification details for where to put cache folders. So if we want .dartServer to live somewhere else we should probably add a applicationCacheHome() to cli_util similar to how I added applicationConfigHome in https://github.com/dart-lang/cli_util/pull/66

In your .zshrc, add:
``
export ANALYZER_STATE_LOCATION_OVERRIDE=$HOME/Library/Caches/dart_server

related https://github.com/dart-lang/sdk/issues/42813


[PE-D][Tester C] User guide duplicate heading for deleteEvent

The double heading for "Deleting an Event" can be confusing for readers of the User Guide.

Labels: severity.VeryLow type.DocumentationBug
original: chantellyu/ped#14

Resolved


Dependency package @opentelemetry/core has a new version available

We have identified a dependency on version 1.0.1 of @opentelemetry/core. A new version (1.1.1) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

already on v1.12.0 and v1.13.0


Fix private notes

Thanks for these PRs, i haven't been keeping an eye on the repo, is it still working ok for your needs?

Thanks for these PRs, i haven't been keeping an eye on the repo, is it still working ok for your needs?

Hey.  I'm not sure yet. I'm a long time user of InvoicePlane (fusion invoice before)  but since there is no updates for last couple months and their website is down for last two weeks, I started looking at alternatives.
There is some mess caused by VAT (TAX) rates not being imported neither the country of clients.
Also not sure if replacing empty email addresses to<EMAIL_ADDRESS>is a good idea.
One more thing I noticed:  Terms on InvoicePlane can be in HTML so when imported to nijna, HTML tags are being shown.
I need to experiment more if invoiceninja fits my needs and understand better the licencing model of the open source version.

@csiwek thanks for the feedback.
If you have any questions on licensing of Invoice Ninja or anything else, let us know.
We'd love to know what features are missing to make the change to Invoice Ninja simpler.


checkstyle task fails with Could not inspect the Groovy system for ClassLoader VisitableURLClassLoader(ant-and-gradle-loader)

Hey there!
I'm trying to migrate my GitHub Actions build script from simple ./gradlew execution to the gradle-build-action. Unfortunately even simple build task fails with:
* What went wrong:
Execution failed for task ':odd-platform-api:checkstyleMain'.
> Could not create service of type IsolatedAntBuilder using BuildScopeServices.createIsolatedAntBuilder().
   > Could not inspect the Groovy system for ClassLoader VisitableURLClassLoader(ant-and-gradle-loader)

Here is the script: https://github.com/DementevNikita/odd-platform/blob/main/.github/workflows/build.yaml
Here are the execution logs: https://github.com/DementevNikita/odd-platform/runs/4422487514?check_suite_focus=true
also attaching logs in txt just in case
1_images.txt

Thanks for the report. I suspect that this issue is unrelated to the gradle-build-action, but would need to verify.
To demonstrate that this is an issue with the action, can you please check:

That you can run the same build locally with JDK 17
That the build runs successfully with JDK 17 without the gradle-build-action. (eg use run: ./gradlew :odd-platform-api:build -Penv=dev ...)

@bigdaz thanks for the reply!

Yep, I run the build locally with JDK 17
Here is the original build file from the repo I forked: https://github.com/opendatadiscovery/odd-tracing-gateway/blob/main/.github/workflows/build.yaml. Even though it's a different gradle task (it's not working using gradle-build-action as well, but for the different reason) which depends on :odd-platform-api:build, it uses JDK 17 and the wrapper. I will check if the exact same command works and get back to you

@DementevNikita Do you have a follow up here? I still suspect that this issue is unrelated to the gradle-build-action, but it would be nice to confirm this.

@DementevNikita I'm closing this issue on the assumption that it is not a problem with gradle-build-action. If you can help me reproduce it, I'm happy to re-open this issue.


[stable/nats] Adapt chart to NATS version 2

What this PR does / why we need it:
In NATS v2 the main server binary has been renamed from gnastd to nats-server. This PR makes the necessary changes.
Special notes for your reviewer:
Don't merge yet.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/hold

/hold cancel

I see that the changes to make it work with the new version or nats are mininal. Could we parametrize the config file name and the command so it is compatible with the previous version of nats?

@javsalgar I implemented the requested change. Please take a look when you have a chance

I would add the comment related to the new version:
## Nats filenames:
##  - For Nats 1.x.x version, some filenames (binary, configuration file, pid file) uses `gnatsd` as part of the name.
##  - For Nats 2.x.x version, those filenames now uses `nats-server`
## In order to make the chart compatible with NATS versions 1.0.0 and 2.0.0 we have parametrized the following value
## to specify the proper filename according to the image version.
##

in the README, the rest LGTM

/ok-to-test

/lgtm


The  email content for UAT environment and production environment should be in sync

The content of the email body which is sent to job applicant , through production environment, and UAT environment is not synchronized.
Describe the solution you'd like
Review of email content should be performed to maintain synchronization.
Review should be performed for other email content
Refer image for reference

Closing this issue as it is not releavant


Add incomplete test using Mocha framework

Adds the Mocha framework for tests and adds an incomplete initial test.
The test is written in the BDD format.
You can run the tests using npm test.

Closing due to lack of requested changes


Advice for failing 'Ensure permissions are set'

Most likely user error, but can you point me in the right direction. Standard vanilla aws ubuntu64, remote_user=ubuntu
TASK [fubarhouse.nodejs : NVM | Ensure permissions are set] *******************************************************************************************************
failed: [web-server] (item=/usr/local/lib/node_modules) => {"changed": false, "failed": true, "item": "/usr/local/lib/node_modules", "msg": "There was an issue creating /usr/local/lib/node_modules as requested: [Errno 13] Permission denied: '/usr/local/lib/node_modules'", "path": "/usr/local/lib/node_modules", "state": "absent"}

Doesn't this need a become: yes?  My user doesn't have permissions for /usr/local/lib/node_modules
- name: "NVM | Ensure permissions are set"
  file:
    path: "{{ item }}"
    state: directory
    mode: 0777
    owner: "{{ fubarhouse_user }}"
    recurse: no
  with_items:
    - "/usr/local/lib/node_modules"
    - "{{ fubarhouse_user_dir }}/.npm"
    - "{{ fubarhouse_user_dir }}/.nvm"
  changed_when: false

There's a good case for it, so I'll work on this in the next couple of days.
In the interim, you can add the following to this task for the desired effect.
become: yes
become_user: "{{ fubarhouse_user }}"

I'm currently on 1.8.5 (I think, I installed with ansible-galaxy just now but the ansible-galaxy info command doesn't give a version number, the only hint I have is a link to travis that includes 1.8.5 in it).
I'm having some trouble getting this to work. I'm importing the role from inside my own because I want to create a user to install under first. For convenience I'm currently just testing with the default vagrant user. This is on the vagrant box bento/ubuntu-16.04 (I'm sure you can guess the distro I'm using :P).
First if I try to install as a specific user:
- name: Install and configure nodejs, nvm and npm
  import_role: name=fubarhouse.nodejs
  become: yes
  become_user: vagrant

This is where it breaks:
TASK [fubarhouse.nodejs : NVM | Ensure permissions are set] ********************
failed: [<IP_ADDRESS>] (item=/usr/local/lib/node_modules) => {"changed": false, "item": "/usr/local/lib/node_modules", "msg": "There was an issue creating /usr/local/lib/node_modules as requested: [Errno 13] Permission denied: b'/usr/local/lib/node_modules'", "path": "/usr/local/lib/node_modules", "state": "absent"}
ok: [<IP_ADDRESS>] => (item=/home/vagrant/.npm)
ok: [<IP_ADDRESS>] => (item=/home/vagrant/.nvm)

Because the vagrant user of course doesn't have permission to modify /usr/local/lib.
Then If I try to run as root:
- name: Install and configure nodejs, nvm and npm
  import_role: name=fubarhouse.nodejs
  become: yes
  become_user: root

Here is where I get to:
TASK [fubarhouse.nodejs : NodeJS | Install all requested versions] *************
failed: [<IP_ADDRESS>] (item=0.10.48) => {"changed": true, "cmd": "/usr/local/bin/nvm install 0.10.48", "delta": "0:00:00.002229", "end": "2018-03-03 12:09:21.434866", "item": "0.10.48", "msg": "non-zero return code", "rc": 1, "start": "2018-03-03 12:09:21.432637", "stderr": "/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied", "stderr_lines": ["/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied"], "stdout": "", "stdout_lines": []}
failed: [<IP_ADDRESS>] (item=0.10.48) => {"changed": true, "cmd": "/usr/local/bin/nvm install 0.10.48", "delta": "0:00:00.002185", "end": "2018-03-03 12:09:21.950798", "item": "0.10.48", "msg": "non-zero return code", "rc": 1, "start": "2018-03-03 12:09:21.948613", "stderr": "/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied", "stderr_lines": ["/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied"], "stdout": "", "stdout_lines": []}

I'm assuming it's dropping down to a regular user at that point (eg. the SSH user, in this case vagrant) despite my efforts to suggest it become root.
If I try installing as vagrant again but with /usr/local/lib/node_modules preconfigured:
- name: Create node_modules global directory with correct permissions
  file: path=/usr/local/lib/node_modules owner=vagrant group=vagrant mode=0777 state=directory

Then here is where I get to:
TASK [fubarhouse.nodejs : NVM | Create an executable] **************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "checksum": "31e9d754862be4485390df6479b1e8846f664fba", "msg": "Destination /usr/local/bin not writable"}

So I modified the undocumented nvm_symlink_exec parameter to a file in vagrant's home directory (~/nvm), try again and get here:
TASK [fubarhouse.nodejs : NodeJS | Linking binaries] ***************************
failed: [<IP_ADDRESS>] (item=node) => {"changed": false, "item": "node", "msg": "Error while linking: [Errno 13] Permission denied: b'/home/vagrant/.nvm/versions/node/v0.10.48/bin/node' -> b'/usr/local/bin/node'", "path": "/usr/local/bin/node", "state": "absent"}
failed: [<IP_ADDRESS>] (item=npm) => {"changed": false, "item": "npm", "msg": "Error while linking: [Errno 13] Permission denied: b'/home/vagrant/.nvm/versions/node/v0.10.48/bin/npm' -> b'/usr/local/bin/npm'", "path": "/usr/local/bin/npm", "state": "absent"}

I only want a local installation for a specific user anyway so all of this global stuff is unnecessary for my use case. I've technically got it working at this point by simply ignoring the errors but it's pretty gnarly and means if other parts of the role go wrong I can have some cascading problems. Can it be a flag or something to specify that you want to globally install or not?

Actually it only works as the user I SSH in as (vagrant). I can't create a user then run the role with become_user set to my newly created user (eg. a nodejs user) :(

@mhotchen, I'll have a better look tonight.
I can't even recall if this role still installs to the specified folder, so it could be safe to remove.
I'll let you know after I've looked into it.

I believe I've found a solution which should cater for everybody.
I ask that you give it a try, and let me know.

https://github.com/fubarhouse/ansible-role-nodejs/tree/issue-53

So some problems fixed include:

Updates the default NVM version
Prevent root ownership of the IVM clone task
Removes superseded/unused folder creation tasks
Allows root user to create the nvm file (better known as the sym)
Updates the badges
Updates the readme to identify yaml code blocks
Adds brief documentation for the nvm_symlink_exec variable.

Please let me know if and how this goes - I'm pretty confident with the results given I haven't messed with this one in some time. I've been putting it off due to legacy support for node 4 on some of my older docker images. So it's been a while, but it appears to be happy again, and tests are beginning to pass as I'm typing this.

Man I hate that about software. You build or configure something and in a couple of months it won't work anymore. I've especially had that problem with ansible. As I'm writing this an update to Ubuntu last night has broken my vagrant box by uninstalling an older version of NFS and the newer version just hangs. Easy enough to fix (although finding a version that works across OSs is going to be a challenge) but it makes me a bit sad that we have to deal with stuff like this.
Anway! Here's a fun one for you, I've checked out your branch and it doesn't work.
Whilst the fubarhouse_user var is set to 'vagrant' the '$HOME' env var is populated with /root :) That produces the following error:
TASK [ansible-role-nodejs : NodeJS | Install all requested versions] ***********
failed: [<IP_ADDRESS>] (item=0.10.48) => {"changed": true, "cmd": "/usr/local/bin/nvm install 0.10.48", "delta": "0:00:00.002122", "end": "2018-03-05 18:44:50.185998", "item": "0.10.48", "msg": "non-zero return code", "rc": 1, "start": "2018-03-05 18:44:50.183876", "stderr": "/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied", "stderr_lines": ["/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied"], "stdout": "", "stdout_lines": []}
failed: [<IP_ADDRESS>] (item=0.10.48) => {"changed": true, "cmd": "/usr/local/bin/nvm install 0.10.48", "delta": "0:00:00.002136", "end": "2018-03-05 18:44:50.690057", "item": "0.10.48", "msg": "non-zero return code", "rc": 1, "start": "2018-03-05 18:44:50.687921", "stderr": "/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied", "stderr_lines": ["/usr/local/bin/nvm: line 4: /root/.nvm/nvm.sh: Permission denied"], "stdout": "", "stdout_lines": []}

I've added some debug stuff to your branch in a local checkout to demonstrate the problem:
TASK [ansible-role-nodejs : ansible_ssh_user] **********************************
ok: [<IP_ADDRESS>] => {
    "ansible_ssh_user": "vagrant"
}

TASK [ansible-role-nodejs : ansible_user_id] ***********************************
ok: [<IP_ADDRESS>] => {
    "ansible_user_id": "root"
}

TASK [ansible-role-nodejs : fubarhouse_user] ***********************************
ok: [<IP_ADDRESS>] => {
    "fubarhouse_user": "vagrant"
}

TASK [ansible-role-nodejs : shell_home_dir] ************************************
ok: [<IP_ADDRESS>] => {
    "shell_home_dir": {
        "changed": false,
        "cmd": "echo $HOME",
        "delta": "0:00:00.001075",
        "end": "2018-03-05 18:41:22.904683",
        "failed": false,
        "rc": 0,
        "start": "2018-03-05 18:41:22.903608",
        "stderr": "",
        "stderr_lines": [],
        "stdout": "/root",
        "stdout_lines": [
            "/root"
        ]
    }
}

Swapping the registering of fubarhouse_user from ansible_ssh_user first to ansible_user_id fixes my issues. So now the beginning of main.yml looks like:
- name: "Define user variable for non-ssh use"
  set_fact:
    fubarhouse_user: "{{ ansible_user_id }}"
  when: ansible_user_id is defined and fubarhouse_user is not defined

- name: "Define user variable for ssh use"
  set_fact:
    fubarhouse_user: "{{ ansible_ssh_user }}"
  when: ansible_ssh_user is defined and fubarhouse_user is not defined

Note that I am connecting with SSH (as the user 'vagrant') but ansible has become root when executing the script hence the change in $HOME and change in ansible_user_id. The above yields the following values for the variables I debugged before:
TASK [ansible-role-nodejs : ansible_ssh_user] **********************************
ok: [<IP_ADDRESS>] => {
    "ansible_ssh_user": "vagrant"
}

TASK [ansible-role-nodejs : ansible_user_id] ***********************************
ok: [<IP_ADDRESS>] => {
    "ansible_user_id": "root"
}

TASK [ansible-role-nodejs : fubarhouse_user] ***********************************
ok: [<IP_ADDRESS>] => {
    "fubarhouse_user": "root"
}

TASK [ansible-role-nodejs : shell_home_dir] ************************************
ok: [<IP_ADDRESS>] => {
    "shell_home_dir": {
        "changed": false,
        "cmd": "echo $HOME",
        "delta": "0:00:00.001256",
        "end": "2018-03-05 18:46:33.852367",
        "failed": false,
        "rc": 0,
        "start": "2018-03-05 18:46:33.851111",
        "stderr": "",
        "stderr_lines": [],
        "stdout": "/root",
        "stdout_lines": [
            "/root"
        ]
    }
}

At this point the installation is successful! What do you think?

@mhotchen Don't know if it helps until this gets sorted, for vagrant usage we also have these two variables set:
fubarhouse_user: vagrant
fubarhouse_user_dir: /home/vagrant

Yeah that would work! Although it feels a little like looking in to the internals/implementation details and trusting that they don't change (unless it becomes a documented part of the interface which I would be quite satisfied with as a solution).

It’s useful that you both are finding this feature troublesome - so I will
have it addressed soon 😊
I appreciate the background work you did to help this one along.
On Tue, 6 Mar 2018 at 6:12 am, Matthew Hotchen<EMAIL_ADDRESS>wrote:

Yeah that would work! Although it feels a little like looking in to the
internals/implementation details and trusting that they don't change
(unless it becomes a documented part of the interface which I would be
quite satisfied with as a solution).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fubarhouse/ansible-role-nodejs/issues/53#issuecomment-370529666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7ZOMF0H2XrCBOBZ2iiOozZeGYWUBtzks5tbY4ogaJpZM4RIx_2
.

It's the least I can do when I'm depending on your free labour lol. Thanks buddy much appreciated.

Morning fubarhouse.
Unfortunately for me my brain decided to think about ansible instead of sleeping last night and I think I've come up with a pretty simple solution: have a documented variable asking who to install under (eg. fubarhouse_install_user), falling back to ansible_user_id. According to this superuser answer you can get the user's home directory using ~$USER:
vagrant@test:~$ pwd ~vagrant
/home/vagrant
vagrant@test:~$ pwd ~root
/home/vagrant

So that could be used throughout the script when referencing the installation directory instead of relying on the $HOME variable. A neat trick I didn't know about.

I have removed the implementation entirely in favour of the ~ replacement which is supported, however inelegant.
Tests are passing, so you are welcome to test against the changes in branch issue-53.
Please let me know - sooner rather than later. I would love to get this released.

Good morning from drizzly and cold England :)
Sorry for the delay I'm dealing with some personal stuff right now. I have tested the latest updates and they work perfectly for me. Really nice work friend and thank you for your promptness. I really appreciate and admire your work.

@mhotchen,
Thanks, I appreciate your kind words.
I'll organise a release for this tonight - I'm just doing some work on a personal Drupal module I manage.
I'll get to this straight after :)

Version 1.9 has been released, and Ansible Galaxy has picked the changes up.
This ticket will now be closed - if for any reason it should not be closed, please re-open it.


python312Packages.tencentcloud-sdk-python: 3.0.1224 -> 3.0.1225

Diff: https://github.com/TencentCloud/tencentcloud-sdk-python/compare/refs/tags/3.0.1224...3.0.1225
Changelog: https://github.com/TencentCloud/tencentcloud-sdk-python/blob/3.0.1225/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 339749 run on x86_64-linux 1

4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


chore(main): release 3.2.1

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

allow error-like objects in the types (60b7a79)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v3.2.1
:sunflower: