[go_router_builder] Iterable parameters don't support default values

Steps to Reproduce

Execute flutter pub run build_runner build --delete-conflicting-outputs on the code sample (see "Code sample" section below)
The default value for the Iterable parameter is not copied and there are errors in the generated code (see "Logs" section below)

Expected results:
Default parameters should be supported on all the supported types (aka Iterable)
Actual results:
Iterable parameters don't support default values

Code sample
Or you can check out https://github.com/ValentinVignal/flutter_app_stable/tree/go-router-builder/default-value-with-iterable-parameters
import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

part 'main.g.dart';

@TypedGoRoute<MyRoute>(path: '/')
class MyRoute extends GoRouteData {
  const MyRoute({
    this.iterable = const [],
  });

  final Iterable<int> iterable;

  @override
  Widget build(BuildContext context, GoRouterState state) =>
      const Placeholder();
}

which generates
// GENERATED CODE - DO NOT MODIFY BY HAND

part of 'main.dart';

// **************************************************************************
// GoRouterGenerator
// **************************************************************************

List<GoRoute> get $appRoutes => [
      $myRoute,
    ];

GoRoute get $myRoute => GoRouteData.$route(
      path: '/',
      factory: $MyRouteExtension._fromState,
    );

extension $MyRouteExtension on MyRoute {
  static MyRoute _fromState(GoRouterState state) => MyRoute(
        iterable: state.queryParametersAll['iterable']?.map(int.parse), // <- The argument type 'Iterable<int>?' can't be assigned to the parameter type 'Iterable<int>'
      );

  String get location => GoRouteData.$location(
        '/',
        queryParams: {
          if (iterable != const [])
            'iterable': iterable?.map((e) => e.toString()).toList(), // <- The receiver can't be null, so the null-aware operator '?.' is unnecessary.
Try replacing the operator '?.' with '.'
        },
      );

  void go(BuildContext context) => context.go(location);

  void push(BuildContext context) => context.push(location);

  void pushReplacement(BuildContext context) =>
      context.pushReplacement(location);
}

Logs
No log

Analyzing flutter_app_stable...

  error • The argument type 'Iterable<int>?' can't be assigned to the parameter type 'Iterable<int>' • lib/main.g.dart:20:19 • argument_type_not_assignable
   info • Equality operator `==` invocation with references of unrelated types • lib/main.g.dart:26:15 • unrelated_type_equality_checks
warning • The receiver can't be null, so the null-aware operator '?.' is unnecessary • lib/main.g.dart:27:33 • invalid_null_aware_operator

3 issues found. (ran in 4.1s)

Reproducible using the code sample and the steps outlined above.

flutter doctor -v
[✓] Flutter (Channel stable, 3.7.6, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.7.6 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12cb4eb7a0 (5 days ago), 2023-03-01 10:29:26 -0800
    • Engine revision ada363ee93
    • Dart version 2.19.3
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8617.8

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

[✓] Connected device (3 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 110.0.5481.177

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

• No issues found!

[!] Flutter (Channel master, 3.9.0-1.0.pre.50, on macOS 13.2.1 22D68 darwin-arm64, locale en-GB)
    • Flutter version 3.9.0-1.0.pre.50 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6afaeab23a (5 hours ago), 2023-03-06 01:42:24 -0500
    • Engine revision b4297f3cc8
    • Dart version 3.0.0 (build 3.0.0-290.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

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

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

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 72.1.4
    • Dart plugin version 223.8617.8

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

[✓] Connected device (3 available)
    • M2007J20CG (mobile) • adb-5dd3be00-17AYzd._adb-tls-connect._tcp. • android-arm64  • Android 12 (API 31)
    • macOS (desktop)     • macos                                      • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)        • chrome                                     • web-javascript • Google Chrome 110.0.5481.177

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.


UndefVarError

I met UndefVarError(:alk) error after I run the built binary.
alk() is definied by my module, and I've import the module before main()
If I call main() in REPL everything works well, but it fails if I run the executable
OS: Mac OSX
Julia v0.5

Do you call the function like: MyModule.alk(). Full qualification of the objects in a module is necessary see https://github.com/dhoegh/BuildExecutable.jl/blob/master/README.md

I didn't use Moduld.fund(), trying now... thanks.
Another issue, the built executable dir is very big (> 200MB), which makes it not convenient to deploy. Is there any way to make a small and clean build (like < 30 MB)

This issue is gone after use Module.func()
But got another error:
SystemError("mkdir",17,"alk")

Do you still have an issue, if so could you provide more information?


Broken website?

I am getting an strangely-formatted version of https://vowsjs.org when views in Safari 14.0 and Chrome 86. Here's a partial capture:

Did some investigation before seeing this issue. Closing in favor of vowsjs/vowsjs.org#4 which has more details and is in the website repo.


Update gems

Coverage remained the same at 99.367% when pulling 31ca4375f7bf6a1a6eea457cf2241f1f7931d689 on update-gems into de847e47737675a3aa244cfeb0ccacf77d90232e on master.


Blazor Virtualize component

Fixes #19871
Three concerns on this one:

Consistency (I guess since it works either way) ... but there's still flexibility in how objects are assigned to component parameters in samples and examples. The blog post (and other assorted examples) assign without the @ symbol, but we've been moving docs consistently to using @ when the attribute isn't prefixed with @...

Items="@collection" ... because what's in quotes isn't necessarily C# for a Blazor parameter. However, the framework seems to accept it without @. The examples in the blog post don't use @ ... <Virtualize Items="employees" Context="employee">.
@bind="collection" :+1:, NOT @bind="@collection" :x: ... because it's C# in the quotes per Razor syntax.

The examples on this PR currently use the @ on the collection, as we do elsewhere throughout these docs based on our prior convo. Proceed? ... or revert everywhere?

The blog post doesn't place
 tags around the Virtualize component for the item templates that contain
 elements. I think it was left out just to abbreviate the examples ... keep them short. For completeness, I placed an example into a sample app and am surprised to see
 elements rendered inside the
 tags. I don't think that's permissible under HTML5. Thoughts? ... and btw ... this would also be a problem for
 elements in a template with a
 or
 around the Virtualize component ...
 tags between them should be an HTML spec problem.

    <Virtualize Items="@employees" Context="employee">

<EMAIL_ADDRESS><EMAIL_ADDRESS>

    </Virtualize>

        Joe

        Blow

        Sally

        Hurricane

        Big

        Mess!

Finally, we had some content on this for 3.2. I left that on the PR for <5.0. Should it be left as I have it here? ... or should I strike that 3.x versioned content and version the whole topic for 5.0+?

Thanks @pranavkm ... do you need some time on my questions ☝. ...... or should I just merge and forget about that stuff. :smile: lol


Migrate Elyra documentation to Sphinx

Migrate Elyra documentation to Sphinx
Took the existing README.md and the docs folder to create a sphinx documentation site.
Uses the theme sphinx_rtd_theme
Currently uses markdown as all the existing files were in markdown.
Fixes #428
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Thanks @kevin-bates. Agreed the content needs work and we can focus on that after we have moved the docs. I was going to take a closer look at that as I played with the product more following each page. I'll work through your review comments.

And FYI, the readthedocs link: https://elyra.readthedocs.io/en/latest/


How do i download it

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

You don't download it. You paste the code into the console in inspect element on prodigy and execute it.

You don't download it. You paste the code into the console in inspect element on prodigy and execute it.

wut im confused show me a screenshot


Upgrade to RN 0.37

Thanks for this PR @fabriziomoscon 🚀 ! We will check it as soon as possible. With our latest update on master your package.json is conflicting now so you might want to solve this first :)

I have rebased my fork on top of upstream/master.
Feel free to check out

npm test is passing locally (after rm -fr node_modules; npm install)
No idea why tests are not passing on travis. I have run out of options.

more clues... after updating node to v7.1.0 I got the test failures as in travis.

I have updated all the devDependencies and the tests started to pass. I think RN 0.37 has some updates for dev packages that are used in this project, so npm was installing incompatible versions.

I use nvm to update node, that let me switch easily back and forth.
I don't think node version 7 is a requirement to run pepperoni, my test were passing on 6.1

Got it finally working on my machine as well. My issue is actually related to #153. Upgrading to React 15.4 seems to raise issues still with depending packages like react-addons-test-utils: 15.4. So I solved it now by setting React and ReactTestUtils versions to 15.3.
"react": "~15.3.2",
"react-addons-test-utils": "~15.3.2",

If no obligations I'd merge in #153 first and fix ReactTestUtils as well once the issues for React 15.4 are resolved.

I see what you mean.
the react team released 15.4.1 meanwhile this PR was waiting.
I think we should use tilde not caret for all facebook dependencies:
"react": "^15.3.2" => "react": "~15.3.2"
caret allows npm to upgrade the minor version, but tilde allows only to upgrade the patch.


Don't remove "Send to" context menu from Sophia.ps1

Have you confiagured the preset file before running?
Please read this: https://github.com/farag2/Sophia-Script-for-Windows#how-to-use
And this: https://github.com/farag2/Sophia-Script-for-Windows#how-to-run-the-specific-functions
After reading now you know what to do: find the appropriate function name SendToContext -Show, and invoke it.
. .\Functions

Sophia -Functions "SendToContext -Show"

But can you make it SendToContext -Show default instead of -Hide?

But can you make it SendToContext -Show default instead of -Hide?

Users have to configure it before running, not me. This is just default preset. :)

ok, i understand

Wait for https://github.com/Sophia-Community/SophiApp 😺


Can edit in preview using drag&drop selection

Content editable feature. Preview should be RO.

Huh, how did you manage to make editable preview? :)

Sorry, since I am the only one working on the project at the moment, I sometimes create issues as todos for myself with very little explanation.
The preview is not editable in user interaction meaning, and should not be.
However, at this moment the preview has contenteditable and blocked onChange, so it simulates RO, but drag&drop selection does not fire the event.
...then  why on earth does it have thecontenteditable attribute at the first place? From UI perspective the editor should minimalize needs to use mouse in interaction. You can catch shortcut events when focused on editor, but since the editor has pure preview mode, you would lose focus while in it. Thus early stage fix was to make preview focusable and give it focus when source code is hidden.
But could it be?
It could if given LML can be easily partially rendered. This is the case for markdown, but not so much for adoc. It is not priority for now. But Typora handles this masterfully in my expirience.

That's okay, I was just curious. :) Real editable preview is quite complicated feature, not something that happens by accident. :) Thanks for the explanation.

#47


Moving opsworks (17) resources to v1beta1 version

Moving 17 resources in the opsworks group:

[ ] aws_opsworks_static_web_layer
[ ] aws_opsworks_user_profile
[ ] aws_opsworks_application
[ ] aws_opsworks_custom_layer
[ ] aws_opsworks_ecs_cluster_layer
[ ] aws_opsworks_ganglia_layer
[ ] aws_opsworks_haproxy_layer
[ ] aws_opsworks_instance
[ ] aws_opsworks_java_app_layer
[ ] aws_opsworks_memcached_layer
[ ] aws_opsworks_mysql_layer
[ ] aws_opsworks_nodejs_app_layer
[ ] aws_opsworks_permission
[ ] aws_opsworks_php_app_layer
[ ] aws_opsworks_rails_app_layer
[ ] aws_opsworks_rds_db_instance
[ ] aws_opsworks_stack

Stack is required for all opsworks resources, but it fails with this error:
message: 'observe failed: cannot run refresh: refresh failed: Missing required
argument: The argument "region" is required, but no definition was found.'

As suggested by @sergenyalcin added the following to overrides.go:24:
if r.ShortGroup == "iam" || r.ShortGroup == "opsworks" {
   return
}


Fix issue-2675

Fix issue #2675.
The bug is because insertion didn't check query graph pattern against schema constraint. It makes me think the storage backend should assert inserted data (specifically table_id) while inserting.
This PR also improves error message to be more readable.

Just to leave a note here, as discussed, I will add sanity checks on the storage side for these cases, too.


wait animation for article deletions disappears on roll-off

related to #468 – if you click the trash-can icon to delete an article it gets a loading animation, but the button with animation disappears if you roll-off the article. I think it should persist even if you roll off!

I'm not sure I see this happening. Can you show me this if it reproduces?

This is what I mean...

I think the wait animation should persist even when I roll off.

Why do we have any rollover mystery buttons at all?

Oh that delete button! Yeah, that's not great. Watching that gif on loop is actually really frustrating.
Re: mystery rollover buttons. I think that the article-list view has two user purposes right now:
1. The primary way of navigating to the file you want to edit.
2. A way to restructure the IA.
Since most people will be using it primarily as a navigation page, I didn't want to litter it with edit and delete buttons. It was a matter of simplifying the interface so that people only see what they need at the last possible moment.
I'm not convinced its the solution we want ultimately either though. It's one of the reasons I was weighing in this prototype when I decided to hide all the of IA editing actions in a separate mode.
http://chimecms.github.io/chime-prototypes/content-ordering/browse.html

I do like the modal interactivity in that version. I think deletion might classify as content editing, rather than structural editing, and I wouldn’t put the edit/delete buttons in the category of litter. They’re important UI, and provide valuable hints about what’s possible. Better to include them, than provide a false appearance of cleanliness but require people to hunt around with their mouse.

Huh. Given that 80% of our users are non-experts going in and tinkering with copy on a small number of pages, my bet is that having all other operations hidden would be a net win, but user tests are the only way to know for sure.

Making the modal switch explicit ("Edit Article Structure") provides those non-experts with affordances and language to increase their skills. Basing it on mouse rollovers leads to a confusing situation, where they may never quite know what functions they’re missing because they haven’t rubbed the whole surface of the genie lamp with their mice yet.

I understand the theory, but would want to see the problems in user testing before we made big bets either way. Slack, for example, uses a fair bit mouseover UI to reduce clutter and I'm not so worried that I've missed anything. But when I was getting started, it was nice to have the focus on what really mattered.


FTB Quests 1902.5.0+ Requires FTB XMod Compat

FTB Quests 1902.5.0+ requires the mod FTB XMod Compat for KubeJS, JEI, REI or Game stages integration with FTB Quests.
You can see this requirement stated on the FTB Quests Curseforge page.
https://www.curseforge.com/minecraft/mc-mods/ftb-quests-forge

I looked at the page and it's not a 'requirement' but more of a suggestion if you want better compatibility. Had it been a requirement, it would've had installed automatically.
But regardless of phrasing, I will add it in next update. Next time you make a suggestion, please use a more polite and less demanding language, as it makes me(or whoever you suggest it to) be less willing to add your suggestion.

I looked at the page and it's not a 'requirement' but more of a suggestion if you want better compatibility. Had it been a requirement, it would've had installed automatically. But regardless of phrasing, I will add it in next update. Next time you make a suggestion, please use a more polite and less demanding language, as it makes me(or whoever you suggest it to) be less willing to add your suggestion.

I'm sorry I misread it as a requirement.

No problem. Just be careful in the future. But the suggestion is really helpful


S3FS + RexRay + Third party S3 integration possible?

Hi I have a quick question, I played around with
https://wasabi.com/
A 100% compatible, as they claim, S3 storage service. I noticed that rexray recently exposed the S3FS_ENDPOINT setting for s3fs via environment variable.
When I create a docker volume with kontena (config below) the buckets get created but the deployment fails because of a error the rexray/s3fs throws. Deploying a container manually and mounting it works.
Do you support wasabi as storage backend or is there some example how to greate a s3fs volumn driver with kontena?
If I do the same with a AWS integration everything works.
Docker plugin install
docker plugin install rexray/s3fs S3FS_ENDPOINT='https://s3.wasabisys.com' S3FS_MAXRETRIES=20 S3FS_ACCESSKEY=XXXX S3FS_SECRETKEY=YYYY  REXRAY_LOGLEVEL=debug

Create driver
kontena volume  create --driver rexray/s3fs --scope instance testvolume

Create driver
kontena volume  create --driver rexray/s3fs --scope instance testvolume

If wasabi.com is really 100% S3 compatible, I don't see any reason why it shouldn't work. Kontena "just"  instructs Docker to create and mount the volumes, really the same operation you do manually with docker volume create +  docker run -v my-s3-vol:/data ...

When I create a docker volume with kontena (config below) the buckets get created but the deployment fails because of a error the rexray/s3fs throws.

What kind or error you see?

I was able to get volumes running to the point where the bucket is created on wasabi side.
BUT
There seems to be something wrong with rexray, it is able to create the bucket, but when mounting it on a container it actually gets mounted as local storage only. See: https://github.com/thecodeteam/rexray/issues/908
I just included some debug info on the issue, let's see if rexray folks are able to pin down the issue.
One other thing I encountered was this:
core@wild-shadow-74 ~ $ docker run -ti -v wasabi-rexray-test:/data alpine sh
/ # ls -lah /data/
total 16
drwx------    2 root     root        4.0K Nov 24 08:38 .
drwxr-xr-x    1 root     root        4.0K Nov 24 08:38 ..
/ # df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                 133.1G      1.1G    126.4G   1% /
overlay                 133.1G      1.1G    126.4G   1% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                     3.9G         0      3.9G   0% /sys/fs/cgroup
/dev/sda9               133.1G      1.1G    126.4G   1% /data
/dev/sda9               133.1G      1.1G    126.4G   1% /etc/resolv.conf
/dev/sda9               133.1G      1.1G    126.4G   1% /etc/hostname
/dev/sda9               133.1G      1.1G    126.4G   1% /etc/hosts
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                    64.0M         0     64.0M   0% /proc/kcore
tmpfs                    64.0M         0     64.0M   0% /proc/latency_stats
tmpfs                    64.0M         0     64.0M   0% /proc/timer_list
tmpfs                    64.0M         0     64.0M   0% /proc/sched_debug
tmpfs                     3.9G         0      3.9G   0% /sys/firmware
/ # exit
$ docker run -ti -v wasabi-rexray-test:/data alpine sh
/run/torcx/bin/docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/3ddde09ebb0b23c0011ceb685cd3699b18ba019c7954493cd1a58b88d10081b3/rootfs': VolumeDriver.Mount: docker-legacy: Mount: wasabi-rexray-test: failed: error mounting s3fs bucket.

So I'm only able to mount the volume once. Mounting it second time always fails. :/

I'm getting this error:
Deployment of service vicoli/wordpress/redis failed:
  - halting deploy of vicoli/wordpress/redis, one or more instances failed
  - GridServiceInstanceDeployer::ServiceError: Docker::Error::ServerError: VolumeDriver.Mount: docker-legacy: Mount: wordpress.redis.testvolume13-1: failed: error mounting s3fs bucket (on node company)

Hi @piscis and @jnummelin,
I copy here my answer for rexray#849 issue maybe it can solve your issue in Kontena.
If you want to install the plugin using a 3rd party like minio or wasabi, you should use S3FS_OPTIONS and specidy the URL that you use in the S3FS_ENDPOINT as @clintkitson mentioned, but there's a typo it should be S3FS_OPTIONS="url=http://..." removing the -o. For example:
docker plugin install rexray/s3fs S3FS_OPTIONS="allow_other,use_path_request_style,nonempty,url=http://<IP_ADDRESS>:9000" S3FS_ENDPOINT="http://<IP_ADDRESS>:9000" S3FS_ACCESSKEY="xxxxxxxxxxxxxxxx" S3FS_SECRETKEY="xxxxxxxxxxxxxxxxxx" --alias s3fs --grant-all-permissions
Hope that helps!

@piscis did you test with the S3FS_OPTIONS pointing to Wasabi?
I was able to use volumes with Wasabi

@jnummelin yes it works for me thank you

Closing, revealed to be docs/usability thing in rexray side

same compose file used by my mate it worked in there system but in mine it doesn't the only
volume is creating But at the time of mounting I am getting this error
ERROR: for node-server  Cannot create container for service server: VolumeDriver.Mount: docker-legacy: Mount: code2rockenvironmentsfile: failed: error mounting s3fs bucket
ERROR: for server  Cannot create container for service server: VolumeDriver.Mount: docker-legacy: Mount: code2rockenvironmentsfile: failed: error mounting s3fs bucket
ERROR: Encountered errors while bringing up the project.

@Tariqu Have you found solution?


Talent-based alternative characteristics for lightsaber checks

Wondering if there are plans to implement the F&D talents that allow for characteristics other than Brawn to be used for lightsaber skill checks? I've got a Makashi Duelist who keeps forgetting that she can use her Presence instead of Brawn, and I don't see a way to account for that other than to manually adjust the dice pool every time she makes a lightsaber check.

Right click the lightsaber skill and click "change characteristic".
Btw, questions like this can be answered a lot faster in the Discord :)


Add support for assigning a managed identity on ContainerGroup creation

using (IAzure azure).ContainerGroups.Define()... and so on does not give me the ability to assign a user-defined managed service identity to the container group / container instance.
The REST request mus then look like this:
{
   "identity": {
      "type" = "UserAssigned",
      "userAssignedIdentities": {
         "/subscriptions/.../resourceGroups.../providers/Microsoft.ManagedIdentity/userAssignedIdentities/..." = {}
      }
   },
   "properties": {
      ...
   }
}

Please add support for .WithUserAssignedIdentity(string resourceId) or something like this.

Thank you for opening this issue!  We are routing it to the appropriate team for follow up.

Sorry for late response. @weidongxu-microsoft could you help with this issue? Thank you!

@ChenTanyi
It appears to be a feature request. Please double confirm.

it is. But i'd say it should have been possible from the start or at least not year later

@clericc You can use the Inner object as workaround if it is not provided in fluent API.
aci.Inner.Identity.Type = ResourceIdentityType.UserAssigned;
aci.Inner.Identity.UserAssignedIdentities = new Dictionary...

aci.update().apply()

Or even use the inner create function
azure.ContainerGroups.Inner.CreateOrUpdateAsync();

uuh nice, thanks, didnt know that. I moved on from this project like 10 monts ago, so i didnt try to figure it out in other ways.
So its a plain feature request then ;)

cc @nickzhums  this is a feature request to .net fluent SDK

hi @xccc-msft could you pls help to have a look? thanks

hi @xccc-msft could you pls help to have a look? thanks

@nickzhums It looks we can mark as Track2 feature request here.

@nickzhums It looks we can mark as Track2 feature request here.

added to backlog, cc @markcowl @allenjzhang @m-nash for awareness

added to backlog, cc @markcowl @allenjzhang @m-nash for awareness


Update POS layout configuration entities diagram

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


CUPTI Support Compatibility Check

There are quite a bunch of new activity introduced in CUDA-11.2. Presumably, even more will be brought in CUDA-11.3 in the next month.
When we implement features based on these new activities, we should be careful about the minimum supported CUPTI version. For example, CUpti_ActivityMemoryPool is a new feature only collected in CUDA-11.2.

This repository has moved to GitLab, please continue this issue there.


Useless code in the importer

Bug description
Get ride of useless code
https://github.com/DefectDojo/django-DefectDojo/blob/d14696e576e31bc447645018d2d3aed558dd7ccd/dojo/importers/importer/importer.py#L54-L58

FYI @valentijnscholten

?

@valentijnscholten we already discussed about this piece of code. That's it

merged for release 2.7.0

I also changed the title of the PR, the titles are what ends up in the release note so I'd like to see us make an effort to make them clear and neutral.

yes, you're right


cleanup dpdk tests

@drunkirishcoder use descriptions in your PR dawg. comeon yo.

My code is self-describing. I don't need descriptions!


Integrate Snowbridge bridge features: ERC20 <=> Polkadot token transfer

Is your feature request related to a problem? Please describe.
The Snowbridge team has successfully tested bidirectional ERC20 token transfers between Rococo and Goerli. They will enable testing for other parachains soon. Please do research and integrate their solutions

https://forum.polkadot.network/t/update-on-snowbridge/3902
https://docs.snowbridge.network/applications/token-transfers
https://www.youtube.com/watch?v=wq8SAg2TjKY

Added these tokens:
https://docs.google.com/spreadsheets/d/1D3sJWxHQZBipNhqjAZUDRlGrQCTPW8nS3r7ZNUsL904/edit?gid=1523240658#gid=1523240658

Version test: http://<IP_ADDRESS>:8900/s/qfjfFR5RFRQ2iFA
Validation passed in cases:

XCM WETH: Rococo Asset Hub <-> Ethereum Sepolia
Re-check WETH, WBTC: PAH <-> Ethereum (Approve step)
Re-check all validate on Send fund feature


Is there a way to have snapshot scale to 75% before opening up the simulator?

I have notice that when snapshot run, it open in 100%
[12:04:14]: Patching '/Users/jenkins/Library/Preferences/com.apple.iphonesimulator.plist' to scale simulator to 100%
This would take forever too boot and usually time out. When i rescale to 75 % or 50% and close out the simulator, snapshot would continue onward and reopen it again with smaller scale and it would boot correctly.

🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.11.6

Ruby
2.2.2

Bundler?
false

Git
git version 2.9.3 (Apple Git-75)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.11.6 (15G31)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.2.2/lib

OpenSSL Version
OpenSSL 1.0.2a 19 Mar 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.25.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.4.0

i18n
0.7.0

json
1.8.1

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.4.3

activesupport
4.2.4

colored
1.2

claide
0.9.1

xcodeproj
0.28.2

rouge
1.10.1

xcpretty
0.2.4

terminal-notifier
1.6.3

terminal-table
1.4.5

plist
3.1.0

addressable
2.3.8

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

highline
1.7.8

commander-fastlane
4.4.4

excon
0.45.4

faraday
0.9.2

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.25

http-cookie
1.0.2

faraday-cookie_jar
0.0.6

fastimage
1.6.8

gh_inspector
1.0.2

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types
2.6.2

hurley
0.2

little-plugger
1.1.4

multi_json
1.11.2

logging
2.0.0

jwt
1.5.2

memoist
0.12.0

os
0.9.6

signet
0.7.2

googleauth
0.5.1

thor
0.19.1

httpclient
2.8.0

google-api-client
0.9.8

mini_magick
4.5.1

multi_xml
0.5.5

rubyzip
1.1.7

security
0.1.3

xcpretty-travis-formatter
0.0.3

dotenv
2.1.1

bundler
1.12.5

faraday_middleware
0.10.0

generated on: 2017-04-11

https://github.com/fastlane/fastlane/blob/60bac7e4a2a6c1e19d1cd20eb83201e7d0cb9e48/snapshot/lib/snapshot/fixes/simulator_zoom_fix.rb#L16 indicates no. Perhaps you can edit your local copy, but that's ill advised.

Why do you want to scale it differently? The screenshots will still have the same resolution

As @RyanCopley said, it's not possible, and I currently don't know of a reason why it should be added

snapshot open simulator in 100% scale, but the simulator is unable to load all the way. it remain at around 80% for an unlimited amount of time before i manually close and reopen in 75%.


Automatic translation of checklists/aro_checklist.en.json

Processed changed files checklists/aro_checklist.en.json

Closing this one, I am too lazy to solve the conflicts


Refactor websocket close logic

Fixes potential deadlocks and panics, that may occur when closing websockets
Streamlines websocket close logic for client and server
Gracefully closes all clients, after calling Stop on the websocket server
Fixed typos in documentation

There's no reason to have different readPump/writePump methods for client and server is there? Or put another way, I think the right abstraction might be "connection" and "server", where a server just manages multiple connections.

There's no reason to have different readPump/writePump methods for client and server is there? Or put another way, I think the right abstraction might be "connection" and "server", where a server just manages multiple connections.

There a few subtle differences between the two, like:

the ping/pong mechanism (which adds an additional timer channel and two code blocks, different on each entity)
the auto-reconnect mechanism, which is only triggered in the client
message handling callback
closing logic and error handling

I could definitely abstract this away with a few function parameters, pass a nil channel to the entity that doesn't send the ping and add a couple more conditions, but I'm afraid it won't read as nicely and look as clean.
I'm willing to give it a try, if you believe it would be worth it, but in general I'm not against code duplication, when two entities actually behave differently.

I merged this one for now, will tackle your suggestion in a separate MR.


Introduces optional error handlers for each route

A global error handler remains, but now exists for global errors like a request for route that's not registered or insecure connection.
Decoding of a message type and encoding of a reply type and/or error type are still sent to the global error handler. Ideally those would also be sent to the route specific one. If we like this approach, can take a look at doing that next.

@amomchilov I'd appreciate getting your thoughts on this approach. If you think it's a good idea, I'd also welcome a code review although this approach is currently incomplete - it should also have applicable decoding/encoding errors go to the route's error handler and not the global one.

@amomchilov Thought on this approach? Genuinely unsure if this is actually helpful or not.

Not convinced this is the correct approach, so closing for the time being. Can always be reconsidered in the future.

Sorry, this slipped through the cracks, I never even took a look at it :o


Please add a "latest" tag to hub.docker.com images

Fantastic plugin -- thank you!
To simplify upgrades, it would help greatly if you could tag your hub.docker.com images with 'latest' or similar.  This will ensure those with automation (eg ouroboros, watchtower, etc) can keep up with development.

Hey @ThisIsTheOnlyUsernameAvailable, thanks for your interest! I'm glad you are enjoying the project.
We tend to discourage latest tags :slightly_frowning_face: they just introduce so many fun new ways for things to change unexpectedly and that wakes us up at night. This plugin does not change very often anyway, but surprise changes to DNS... :grimacing:
I'm not a user of ouroboros or watchtower, but most automation we rely on currently can track new tags and update "downstream" projects that way. Dependabot or Renovate, for example, can update references to this image on GitHub or other version control systems, and Flux can track image releasesin a Kubernetes context. Maybe one of those will work for your use case? If not, I'd be open to hearing about it and maybe we can figure something out.

Thanks very much for the advice, @stone-z.  I'll update my workflow accordingly.


Is there support for AES-128-GCM and AES-256-GCM

Hi @pitbulk -- this is a question related to PRs #255 and #203 -- neither of which give definitive answers.
Does python3-saml currently support AES-128-GCM and AES-256-GCM as encryption methods? I have a customer that has upgraded to Shibboleth 4 which uses AES-128-GCM as the default encryption algorithm. They specifically want AES-256-GCM, but I just need to know if python3-saml supports either of these out of the box.

python3-saml uses xmlsec which it seems added gcm support on 2020:
https://github.com/mehcode/python-xmlsec/pull/154
Give a try and see if you are able to decrypt with gcm algorithm.

@pitbulk You were right, of course. python3-saml works just fine with the right version of xmlsec. In my case, I tested successfully with xmlsec 1.2.34. Thank you for the help here. 🙏🏻


Fix IFL radio not refreshing seed

Backwards-compatible fix for the "I'm Feeling Lucky" radio station not refreshing its seed each time it is requested - #393
The format for getting tracks for this radio station has changed, instead of using the magic "IFL" string, the radioId property is omitted and a seed: {seedType: 6}  property is included (not entirely sure what the 6 signifies)

Thanks! Sorry for the delay in getting to this!


fix/planning-display-mobile-first

Please review before merging.

:tada: This PR is included in version 1.46.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


missing end of sentence in code comment of "Hoarding Gold"

In a code comment is written: "Get its value with"
I expect a function name/description to get the value of a coin to end the sentence.

I see this:
# Get its value with:  coin.value
If you use the "Reload" button to reset to the default code, do you still not see it?
If it's still not there, please let us know what code language you're using, what browser, and what operating system?
Thanks!

I don't play this level. I translate it into German by the translation page.

Ah! The end of the sentence is added inside the level, so this is ok.


fix: detect unresponsiveness and restart window

Fixes #1865
@lidel Still working on this. I'm having issues making the window unresponsive. Could not reproduce #1865 and using process.hang() does not trigger a complete window freeze but only the page itself. That is not triggering the unresponsive event.

Superseeded by #1952


compile problem in current trunk

Hi guys,
in the current trunk version I get a compile error in pkcs7.h file saying:
openssl/pkcs7.h:38:5: error: expected ')' before numeric constant
     X509_NAME *issuer;
     ^

This happens with gcc and also with VS.

Is that with a program of your own, or is it when building OpenSSL?  If the former, would you mind providing test source?
The reason I asked is that I just tried the following short program, and it compiles without failure on my system (Linux):
#include <openssl/pkcs7.h>

int main()
{
    return 0;
}

@wolftobias is this still an issue for you?

Please give me some more time. I'm currently not in the office.

No movement on this. Closing assuming fixed. Please open a new issue if not.

I compile under windows with gnu compiler and still get this error. It seems that this symbol is not defined OPENSSL_SYS_WIN32. Do I have to define that by myself or is there some other mechanism which does this?

Try adding –DOPENSSL_SYS_WIN32 to the configure line and see if that works.  Normally the flag is set only when using VC.

You mean you use mingw/msys? Please provide your Configure line.

Yes I`m using mingw and as IDE eclipse.
g++ -DOPENSSL_SYS_WIN32 "-IC:\\Daten\\_projects\\sourcecode\\branches\\NewOpenSSL_1_1\\src\\main\\include" -O0 -g3 -Wall -c -fmessage-length=0 -o "src\\main\\cpp\\openssl_ssl_ctx.o" "..\\src\\main\\cpp\\openssl_ssl_ctx.cpp"

But even when I define that symbol I get the error above. It seems to me it includes the windows one somewhere else before.
In file included from C:/TDM-GCC-64/x86_64-w64-mingw32/include/windows.h:95:0,
                 from C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl/crypto.h:393,
                 from C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl/bio.h:20,
                 from C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl/asn1.h:16,
                 from C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl/pkcs7.h:13,
                 from C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl_pkcs7.h:6,
                 from ..\src\main\cpp\openssl_pkcs7.cpp:1:
C:\Daten\_projects\sourcecode\branches\NewOpenSSL_1_1\src\main\include/openssl/pkcs7.h:38:5: error: expected ')' before numeric constant
     X509_NAME *issuer;
     ^

Please provide the arguments you give to "Configure"!

I compile the openssl library as you can see below:
./Configure mingw64 --cross-compile-prefix=x86_64-w64-mingw32- --prefix=$root_bin_dir/bin/$lib_dir_name/win64 enable-ssl-trace enable-crypto-mdebug no-deprecated

Ahhhh....so you are cross-compiling this - what host platform are you on?

Yes youre right. Im using a machine to compile for win64/32 and linux 64/32. The os is centos 2.6.32-642.el6.x86_64.

I just compiled with VS2015 / Win7 64bit and I got the same error.

I`ve a header where I include #include <openssl/opensslconf.h>, is this ok? Are there other "global" headers need to included?

Should be fine...can you supply simple test code that replicates the problem?

My thought is that it always goes into wincrypt.h to resolve X509_NAME.

Try this at the top of your source file before any other includes:
#include <openssl\e_os2.h>
#undef X509_NAME

Obviously that should be openssl/e_os2.h !!

When I do this in  pkcs7.h then I can successfully compile.
#	undef X509_NAME
	typedef struct X509_name_st X509_NAME;

Sorry didn`t saw your comment before my last post. I´ll try this asap.

With your suggestion it work also fine.
# include <openssl/e_os2.h>
#undef X509_NAME

Looks like this issue has been seen before, but the fix was only partial. See the top of x509v3.h.

And in x509.h and ts.h!!

What I don't understand is that pkcs7.h includes ossl_typ.h, which already has this in it:
# ifdef OPENSSL_SYS_WIN32
#  undef X509_NAME
#  undef X509_EXTENSIONS
#  undef PKCS7_ISSUER_AND_SERIAL
#  undef OCSP_REQUEST
#  undef OCSP_RESPONSE
# endif

So rewinding the conversation a bit you said:

It seems that this symbol is not defined OPENSSL_SYS_WIN32.

So if you were to have this symbol then presumably you would not get this problem because of the above code in ossl_typ.h. So why do you not have OPENSSL_SYS_WIN32. This should get defined in e_os2.h:
# if defined(OPENSSL_SYS_UEFI)
#  undef OPENSSL_SYS_UNIX
# elif defined(OPENSSL_SYS_UWIN)
#  undef OPENSSL_SYS_UNIX
#  define OPENSSL_SYS_WIN32_UWIN
# else
#  if defined(__CYGWIN__) || defined(OPENSSL_SYS_CYGWIN)
#   undef OPENSSL_SYS_UNIX
#   define OPENSSL_SYS_WIN32_CYGWIN
#  else
#   if defined(_WIN32) || defined(OPENSSL_SYS_WIN32)
#    undef OPENSSL_SYS_UNIX
#    if !defined(OPENSSL_SYS_WIN32)
#     define OPENSSL_SYS_WIN32
#    endif

So, assuming you haven't done something crazy like define OPENSSL_SYS_UEFI or OPENSSL_SYS_UWIN yourself, and also assuming you are not trying to do this under cygwin (I assume there is no chance you are picking up the cygwin compiler?), then as long as you have _WIN32 defined you should get OPENSSL_SYS_WIN32. _WIN32 should be automatically defined under windows.
Can you include e_os2.h at the top of your file and then include something like this after it:
#ifdef __CYGWIN__
# error Running under cygwin!
#endif
#ifndef _WIN32
# error expecting _WIN32 to be defined!
#endif
#ifndef OPENSSL_SYS_WIN32
# error Not detected win32!
#endif

Let me know what errors you get (if any).

The comment about defining the symbol OPENSSL_SYS_WIN32 was misleading. I tried around a lot and gave a wrong statement about this. Sorry! Finally I would say defining that symbol wouldnt change anything. What made the difference and a working compile was ```#undef X509_NAME```. With this undef in pkcs7.h Im able to compile successfully.

I tried what you said and I didnt got any output, means the symbols you mentioned are defined. But I got still the compile message regarding X509_NAME. My idea is that somehow or somewhere the windows.h file get included again, but dont know where or how. Will continue searching.

Well normally if you include a header twice, the second include has no effect. At least that's what the openssl headers do, and I think that is common practice.

I was setting the option in VS to verbose the includes and I saw that after including pkcs7.h and e_os2.h etc. the windows.h file was included. That`s the reason I was asking.

It would be interesting to know whether the following block in ossl_type.h actually gets entered or not:
# ifdef OPENSSL_SYS_WIN32
#  undef X509_NAME
#  undef X509_EXTENSIONS
#  undef PKCS7_ISSUER_AND_SERIAL
#  undef OCSP_REQUEST
#  undef OCSP_RESPONSE
# endif

i.e. Do we enter the block and undef X509_NAME, only to then redefine it again later? Or alternatively do we not enter the block at all. If you add a "#error" line inside the block in ossl_typ.h we would find out. If you see an error, then we know that X509_NAME does get undefined and redefined later. If you don't then we know that, for some reason, OPENSSL_SYS_WIN32 is not yet defined at that point, i.e.
# ifdef OPENSSL_SYS_WIN32
# error This should cause an error
#  undef X509_NAME
#  undef X509_EXTENSIONS
#  undef PKCS7_ISSUER_AND_SERIAL
#  undef OCSP_REQUEST
#  undef OCSP_RESPONSE
# endif

Yes I see the error, as mentioned before the symbol is being used.

I`m not sure if the including and reading of header files are that easy! Anyway use a protection for multiple including of the same headers.
#ifndef HEADER_PKCS7_H
# define HEADER_PKCS7_H

But as reference you can see that the windows.h file is included after the openssl stuff.
1>  openssl_pkcs7.cpp
1>  Hinweis: Einlesen der Datei: C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl_pkcs7.h
1>  Hinweis: Einlesen der Datei:  C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl_global.h
1>  Hinweis: Einlesen der Datei:   C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stdio.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime.h
1>  Hinweis: Einlesen der Datei:      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\sal.h
1>  Hinweis: Einlesen der Datei:       C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\ConcurrencySal.h
1>  Hinweis: Einlesen der Datei:      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vadefs.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_wstdio.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_stdio_config.h
1>  Hinweis: Einlesen der Datei:   C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\stdint.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime.h
1>  Hinweis: Einlesen der Datei:   C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\stdarg.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime.h
1>  Hinweis: Einlesen der Datei:   C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stdlib.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_malloc.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_search.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\stddef.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_wstdlib.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\limits.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime.h
1>  Hinweis: Einlesen der Datei:   C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\string.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_memory.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_memcpy_s.h
1>  Hinweis: Einlesen der Datei:      C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\errno.h
1>  Hinweis: Einlesen der Datei:      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime_string.h
1>  Hinweis: Einlesen der Datei:       C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vcruntime.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_wstring.h
1>  Hinweis: Einlesen der Datei:   C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/opensslconf.h
1>  Hinweis: Einlesen der Datei:  C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/pkcs7.h
1>  Hinweis: Einlesen der Datei:   C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/asn1.h
1>  Hinweis: Einlesen der Datei:    C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\time.h
1>  Hinweis: Einlesen der Datei:     C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\corecrt_wtime.h
1>  Hinweis: Einlesen der Datei:    C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/e_os2.h
1>  Hinweis: Einlesen der Datei:     C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/opensslconf.h
1>  Hinweis: Einlesen der Datei:    C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/opensslconf.h
1>  Hinweis: Einlesen der Datei:    C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/bio.h
1>  Hinweis: Einlesen der Datei:     C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/crypto.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/stack.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/safestack.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/opensslv.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/ossl_typ.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/opensslconf.h
1>  Hinweis: Einlesen der Datei:      C:\Daten\_projects\_Dev\sourcecode\branches\_NewOpenSSL_1_1\src\main\include\openssl/symhacks.h
1>  Hinweis: Einlesen der Datei:      C:\Program Files (x86)\Windows Kits\8.1\Include\um\**windows.h**

I think I might have figured this out. I thought e_os2.h included windows.h, but apparently not.
What I think is happening is pkcs7.h includes asn1.h which include e_os2.h. At this point windows.h has not yet been included but OPENSSL_SYS_WIN32 gets defined.
Later asn1.h includes bio.h, which in turn includes crypto.h which in turn includes ossl_typ.h. At this point windows.h has still not been included. So ossl_typ.h runs the block above and does the "#undef X509_NAME". Later in crypto.h there is an include of windows.h which in turn includes wincrypt.h which redefines X509_NAME!
The answer in my mind is to include windows.h early on in ossl_typ.h. Can you add the following line to ossly_typ.h after the include of e_os2.h:
# include <windows.h>

In the header file ossl_typ.h I made the change
#ifndef HEADER_OPENSSL_TYPES_H
# define HEADER_OPENSSL_TYPES_H

#include <limits.h>

#ifdef  __cplusplus
extern "C" {
#endif

# include <openssl/e_os2.h>

# include <windows.h>

and this will fix the issue.

Great. I'll write a patch for that shortly.

Sounds great! Please let me know when it is available.

This should now be fixed, but was implemented in a different way. After some internal debate it was decided that including windows.h in our public header files was probably a bad idea. Apps developers may want more control over when windows.h is included (or even if it is included at all). Therefore we have removed windows.h from all our public headers altogether (in 1.1.0). This does have some knock on impacts - notably that if you want to use any of the CRYPTO_THREAD_* functions or you want to use any of the async.h functions that use the OSSL_ASYNC_FD type then you should include windows.h before any openssl headers.
Closing this ticket.

But if include windows.h before any openssl header leads to #undef x509_name behavor.

Not sure if I understand your point?

Just wondering why x509_name is undefined.

Because there is a name clash between windows and openssl. They both define that symbol. Therefore it is necessary for OpenSSL to undefine the windows version.

Ah yeah, there is a file that did not compile on windows 7 32bit vc++2015 and some openssl headers in it.
https://github.com/xhs/librtcdc/blob/master/src/dtls.c
And when I included windows.h on top , it get compiled. X509_name get compiled like a charm.
Thank you very much for your hint.


webpack-dev-server npm install warnings on first run jb-compose getting started tutorial

Following instructions at https://github.com/JetBrains/compose-jb/tree/master/tutorials/Web/Getting_Started

open community edition idea, create new compose project
edit build.gradle.kts, change version of kotlin plugin to 1.7.20 and compose plugin to 1.2.1
run build

expect:
Clean build and a project ready to run
observe:
many build warnings, noted below
Looking at the warnings, they are run-of-the-mill deprecation warnings and probably do not block the tutorial.  But it's not the easy-to-use developer experience promised by use of IntelliJ and Compose project wizard.  Perhaps there's a newer version of webpack-dev-server and watchpack that would avoid the jarring experience?  Audience is n00bs, such as myself.  We scare easily.
3:30:13 PM: Executing ':assemble :jsMainClasses :jsTestClasses :metadataMainClasses'...

> Configure project :
Kotlin Multiplatform Projects are an Alpha feature. See: https://kotlinlang.org/docs/reference/evolution/components-stability.html. To hide this message, add 'kotlin.mpp.stability.nowarn=true' to the Gradle properties.

The property 'kotlin.native.enableDependencyPropagation=false' has no effect in this and future Kotlin versions, as Kotlin/Native dependency commonization is now enabled by default. It is safe to remove the property.

Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime/1.2.1/runtime-1.2.1.pom, took 116 ms (2.76 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/web-core/1.2.1/web-core-1.2.1.pom, took 131 ms (2.04 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime/1.2.1/runtime-1.2.1.module, took 24 ms (21.81 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/web-core/1.2.1/web-core-1.2.1.module, took 21 ms (3.15 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/web-core-js/1.2.1/web-core-js-1.2.1.pom, took 18 ms (2.76 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/web-core-js/1.2.1/web-core-js-1.2.1.module, took 23 ms (3.4 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-js/1.2.1/runtime-js-1.2.1.pom, took 19 ms (2.8 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-js/1.2.1/runtime-js-1.2.1.module, took 23 ms (3.37 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/internal-web-core-runtime/1.2.1/internal-web-core-runtime-1.2.1.pom, took 20 ms (2.06 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/internal-web-core-runtime/1.2.1/internal-web-core-runtime-1.2.1.module, took 20 ms (2.35 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/atomicfu/0.17.2/atomicfu-0.17.2.pom, took 20 ms (1.67 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core/1.6.1/kotlinx-coroutines-core-1.6.1.pom, took 40 ms (2.06 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/atomicfu/0.17.2/atomicfu-0.17.2.module, took 22 ms (20.93 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-bom/1.6.1/kotlinx-coroutines-bom-1.6.1.pom, took 20 ms (4.29 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core/1.6.1/kotlinx-coroutines-core-1.6.1.module, took 23 ms (22.89 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/internal-web-core-runtime-js/1.2.1/internal-web-core-runtime-js-1.2.1.pom, took 17 ms (2.32 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/internal-web-core-runtime-js/1.2.1/internal-web-core-runtime-js-1.2.1.module, took 20 ms (2.79 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core-js/1.6.1/kotlinx-coroutines-core-js-1.6.1.pom, took 23 ms (2.1 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core-js/1.6.1/kotlinx-coroutines-core-js-1.6.1.module, took 19 ms (5.92 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-test-js/1.7.20/kotlin-test-js-1.7.20.pom, took 62 ms (1.72 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-test-js/1.7.20/kotlin-test-js-1.7.20.module, took 91 ms (2.07 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/web-core-js/1.2.1/web-core-js-1.2.1.klib, took 68 ms (483.15 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/web/internal-web-core-runtime-js/1.2.1/internal-web-core-runtime-js-1.2.1.klib, took 28 ms (20.26 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-js/1.2.1/runtime-js-1.2.1.klib, took 126 ms (1.09 MB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/atomicfu-js/0.17.2/atomicfu-js-0.17.2.klib, took 142 ms (33 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core-js/1.6.1/kotlinx-coroutines-core-js-1.6.1.klib, took 31 ms (777.41 kB)
Default webpack version now is 5. Support of webpack 4 is deprecated.
Download https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-test-js/1.7.20/kotlin-test-js-1.7.20.jar, took 38 ms (107.13 kB)

> Task :transformCommonMainDependenciesMetadata
> Task :compileCommonMainKotlinMetadata SKIPPED
> Task :generateProjectStructureMetadata
> Task :metadataCommonMainClasses UP-TO-DATE
> Task :allMetadataJar
> Task :jsProcessResources
> Task :jsBrowserProductionExecutableDistributeResources
> Task :kotlinNpmCachesSetup
> Task :jsPackageJson
> Task :kotlinNodeJsSetup
> Task :kotlinRestoreYarnLock SKIPPED
> Task :kotlinYarnSetup
> Task :jsTestPackageJson
> Task :packageJsonUmbrella
> Task :rootPackageJson

> Task :kotlinNpmInstall
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server ><EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > chokidar ><EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > webpack-log ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > url ><EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > chokidar > braces > snapdragon ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
warning workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted > webpack-dev-server > chokidar > braces > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning "workspace-aggregator-383690c4-6e0e-46fb-bdd5-caddc2a0acf8 > compose-gettingStarted-test ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning Ignored scripts due to flag.

> Task :jsGenerateExternalsIntegrated SKIPPED
> Task :kotlinStoreYarnLock
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/compiler/compiler/<IP_ADDRESS>/compiler-<IP_ADDRESS>.pom, took 71 ms (1.77 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/compiler/compiler/<IP_ADDRESS>/compiler-<IP_ADDRESS>.module, took 18 ms (2.69 kB)
Download https://repo.maven.apache.org/maven2/org/jetbrains/compose/compiler/compiler/<IP_ADDRESS>/compiler-<IP_ADDRESS>.jar, took 104 ms (963.75 kB)
> Task :jsPublicPackageJson
> Task :jsSourcesJar
> Task :jsTestProcessResources NO-SOURCE
> Task :compileKotlinMetadata SKIPPED
> Task :metadataMainClasses UP-TO-DATE
> Task :compileKotlinJs
> Task :jsMainClasses
> Task :jsJar
> Task :compileTestKotlinJs NO-SOURCE
> Task :jsTestClasses UP-TO-DATE
> Task :compileProductionExecutableKotlinJs
> Task :jsProductionExecutableCompileSync
> Task :jsBrowserProductionWebpack
> Task :jsBrowserDistribution
> Task :assemble

BUILD SUCCESSFUL in 2m 34s
20 actionable tasks: 20 executed
3:32:48 PM: Execution finished ':assemble :jsMainClasses :jsTestClasses :metadataMainClasses'.

Followup: if the root of this problem is the use of Webpack 4 when it could/should be v5, where do I specify this?  I cannot find a dependency  version of webpack being specified anywhere in the project?

@bobhy
Webpack can be configured with file gradle.properties
kotlin.js.webpack.major.version=4

@bobhy
I see gradle output BUILD SUCCESSFUL
Has your project started successfully?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Question: rationale behind v2

Hey there,
I was just curious about what prompted the rewrite to v2 of react-measure. Could you explain a bit about why the new api is better?
Thanks!

Yes, definitely! The biggest gain from the new version, is the removal of findDOMNode. This was blocking people from being able to write certain tests, mainly with Jest. This actually helped simplify things in my opinion, because now we can be explicit with what component we want to measure.
The new version also introduces a HoC (Higher-order Component). So now you can take measurements of a custom component a little easier, mainly the fact that you don't have to hook into onResize and set up state, you can just wrap a component and receive props. This ended up working out really well and now Measure is a simple wrapper around withContentRect.
The way dimensions are calculated changed, this was due to personal use of the component and needing different measurements. I landed on just giving you a way to get every possible DOM box model measurement so you could do whatever you need with those calculations.
Sorry if it was a big jump out of nowhere 😞 I've been super busy so I wanted to try and get it out while I had the chance. Thanks for filing this! I hope it helps explain a bit of the reasoning behind the changes. I'm always open for critique, so please let me know if you have any troubles or think something can be better 🙏

I keep getting height 0, so I'm not sure if I'm doing it properly...

Interesting.. would you mind pasting the code that gives you that result @designbyadrian? I'll try and look into it to see where the regression it.

@souporserious I'm seeing the same issue, i have something like this:
    <Measure
        bounds
        onResize={(contentRect) => {
           resizeHeight(contentRect.bounds.height);
        }}
      >
        {({ measureRef }) =>
          (<div ref={measureRef}>
            {content}
          </div>)
        }
    </Measure>

I'm seeing all the values as 0 except for "right" which is strangely set correctly. Is this the correct usage?


Add support for using shared HAL and ntcore

In order to improve 3rd party library support, we should switch the HAL and ntcore to be linked to shared instead of statically. The necessary changes have already been PR'd to allwpilib (https://github.com/wpilibsuite/allwpilib/pull/291) and ntcore (https://github.com/wpilibsuite/ntcore/pull/139). The changes we need in eclipse are as followed.
C++:

copy libHALAthena.so and libntcore.so from the c++ build libraries to the rio (probably /usr/local/frc/lib

Java:

During plugin build, when we get the latest maven artifact, it should include a nativelibraries.jar file. We need the 2 files from that libwpilibJavaJNI.so and libHALAthena.so moved to a directory where it can be copied to the robot.
During plugin build, get libntcore.so either from ntcore maven, or potentially from the C++ artifact, and move that into a directory it can be copied from.
During deploy, make sure all 3 libraries libwpilibJavaJNI.so, libHALAthena.so and libntcore.so get moved to the robot, most likely in /usr/local/frc/lib.

When doing this, we most likely want #27 as well.

Fixed in #38


active_sla table is always empty

active_sla table is always empty,but I set sla success

is this fixed with #2506 ?


Document DeployTestSourceDependencies

This runsettings setting should be documented.
See https://github.com/Microsoft/testfx/issues/490

@Evangelink That seems to be documented in https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-mstest-configure#runsettings (done in https://github.com/dotnet/docs/pull/40496)


add support to MFA configuration via EUMAPI

Closes #14425
Implemented Option 2 -> https://github.com/CartoDB/cartodb/issues/14425#issuecomment-438384700

:heavy_check_mark: Acceptance OK!
Tested:

POST/DELETE
Validations: FF, api key, not admin, user not in org, mfa already existing, mfa not found


Issues with mnesia on production

When I run my app on my local computer I don't have any issues, but when I run the release version on the prod server I get the following error message:
{:error,
 {{{:case_clause,
    {:aborted,
     {:bad_type, :"honeydew_\"swiftvox\"", :disc_copies, :smsc@smsc01}}},
   [
     {Honeydew.Queue.Mnesia, :"-init/2-fun-0-", 2,
      [file: 'lib/honeydew/queue/mnesia.ex', line: 79]},
     {Enum, :"-each/2-fun-0-", 3, [file: 'lib/enum.ex', line: 789]},
     {:maps, :fold_1, 3, [file: 'maps.erl', line: 232]},
     {Enum, :each, 2, [file: 'lib/enum.ex', line: 2127]},
     {Honeydew.Queue.Mnesia, :init, 2,
      [file: 'lib/honeydew/queue/mnesia.ex', line: 76]},
     {Honeydew.Queue, :init, 1, [file: 'lib/honeydew/queue.ex', line: 97]},
     {:gen_server, :init_it, 2, [file: 'gen_server.erl', line: 374]},
     {:gen_server, :init_it, 6, [file: 'gen_server.erl', line: 342]}
   ]},
  {:child, :undefined, "swiftvox",
   {Honeydew.Queue, :start_link,
    [
      [
        "swiftvox",
        Honeydew.Queue.Mnesia,
        [disc_copies: [:smsc@smsc01]],
        {Honeydew.Dispatcher.LRU, []},
        {Honeydew.FailureMode.Abandon, []},
        nil,
        false
      ]
    ]}, :transient, 5000, :worker, [Honeydew.Queue]}}}

I am wondering what could be the issue.
Here is the sample code (based on the mnesia example):
defmodule Worker do
  @behaviour Honeydew.Worker

  def hello(thing) do
    IO.puts "Hello #{thing}!"
    :timer.sleep(5000)
  end
end

defmodule App do
  def start do
    nodes = [node()]
    :ok = Honeydew.start_queue(:swiftvox, queue: {Honeydew.Queue.Mnesia, [disc_copies: nodes]})
    :ok = Honeydew.start_workers(:swiftvox, Worker, num: 1)
  end
end

App.start

Here is my mix file:
defmodule Smsc.MixProject do
  use Mix.Project

  def project do
    [
      app: :smsc,
      version: "0.1.0",
      elixir: "~> 1.5",
      elixirc_paths: elixirc_paths(Mix.env()),
      compilers: [:phoenix, :gettext] ++ Mix.compilers(),
      start_permanent: Mix.env() == :prod,
      aliases: aliases(),
      deps: deps()
    ]
  end

  # Configuration for the OTP application.
  #
  # Type `mix help compile.app` for more information.
  def application do
    [
      mod: {Smsc.Application, []},
      extra_applications: [:logger, :runtime_tools, :mnesia]
    ]
  end

  # Specifies which paths to compile per environment.
  defp elixirc_paths(:test), do: ["lib", "test/support"]
  defp elixirc_paths(_), do: ["lib"]

  # Specifies your project dependencies.
  #
  # Type `mix help deps` for examples and options.
  defp deps do
    [
      {:phoenix, "~> 1.4.12"},
      {:phoenix_pubsub, "~> 1.1"},
      {:phoenix_ecto, "~> 4.0"},
      {:ecto_sql, "~> 3.1"},
      {:postgrex, ">= 0.0.0"},
      {:phoenix_html, "~> 2.11"},
      {:phoenix_live_reload, "~> 1.2", only: :dev},
      {:gettext, "~> 0.11"},
      {:jason, "~> 1.0"},
      {:plug_cowboy, "~> 2.0"},
      {:honeydew, "~> 1.4"}
    ]
  end

  # Aliases are shortcuts or tasks specific to the current project.
  # For example, to create, migrate and run the seeds file at once:
  #
  #     $ mix ecto.setup
  #
  # See the documentation for `Mix` for more info on aliases.
  defp aliases do
    [
      "ecto.setup": ["ecto.create", "ecto.migrate", "run priv/repo/seeds.exs"],
      "ecto.reset": ["ecto.drop", "ecto.setup"],
      test: ["ecto.create --quiet", "ecto.migrate", "test"]
    ]
  end
end

Hey @martinos,
What elixir/erlang versions are you running locally and in production?

In Production:
ENV ERLANG_VERSION 22.2
ENV ELIXIR_VERSION 1.10.0

In dev:
elixir         1.10.0
Erlang/OTP 22 [erts-10.6.3]

This is easy to reproduce.
Create a project:
mix new my_project
cd my_project

Add this to the mix file dependencies

Thanks for putting in the effort to provide me with the reproduction, I appreciate it. :)
The issue is that mnesia needs its "schema" (on disk files) created before the actual :mnesia application is started. By including :mnesia in :extra_applications, it gets started before honeydew, and we don't want to stop mnesia to create the schema, since that might interfere with other applications.
Instead of using :extra_applications, try putting :mnesia in :included_applications, that'll have it included in the release, but leave it up to honeydew to start it, like so:
  def application do
    [
      extra_applications: [:logger],
      included_applications: [:mnesia]
    ]
  end

If you don't want to do that (maybe you need mnesia started), you can manually stop mnesia in your release environment and create the schema yourself:
:mnesia.stop()
:mnesia.create_schema(nodes)

Let me know how that works for you, I'll fix the README, etc...

Thanks @koudelka, it works like a charm. I am pretty new to elixir, so I don't master all these subtleties yet.

No worries dude, let me know if you run into any other issues. :)


Kerberos: Authenticating as a principal in the remote realm not allowing to run Hadoop commands

Hi @memoryoflife , @cyxxy
I am using the secure.sh scripts to Kerberos the cluster and enable cross-realm trust with AD server.  Authenticating as a principal in the local realm using root user allows to successfully run Hadoop commands but when I use principal in the remote realm, I can successfully authenticate but when I  execute hadoop fs -ls  I get the below errors.
Details:
My Windows AD is running on on-premises
DEBUG ipc.Client: Exception encountered while connecting to the server : javax.security.sasl.SaslException:
GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Fail to create credential.
(63) - No service creds)]

Can you please help me on this.

Did you set up the cross-realm shared-key in the AD server?
https://github.com/GoogleCloudPlatform/dataproc-initialization-actions/tree/master/secure#enabling-cross-realm-trust-to-an-active-directory

Sorry for the late reply. Try set the encryption type on your AD domain controller:
ksetup /SetEncTypeAttr <YOUR_ON_CLUSTER_REALM> AES256-CTS-HMAC-SHA1-96


Enforcing linux line endings

Documenting desired line endings/will help prevent windows developers don't accidentally push code with windows line endings.

Thanks! 🎆


Is there a known issue around ContractSigned events for multi-clause contracts not firing?

OK so this might be my code (and am still digging), but I am seeing something odd. I have a contract that is made up of two clauses. Each clause has its own lifecycle that starts with initialised then onto contract signed. Once both are in the contract signed state, they are then able to be executed and do their thing.
Both clauses implement the method signature of: clause contractSigned(request : ContractSigned) : Response
When the contract is signed, both of the clauses are initialised OK. However, only one clause ever has its contract signed method called (always the same clause), despite the contract Timeline showing the init and contract signed requests made for both clauses (and with no errors). So the clause in question is always stuck in the initialised state. If I create a contract with just one of the clauses (either one), then the lifecycle works perfectly.
I also tried sending a contract signed request as a REST call to the clause and this worked and moved the state on, so maybe the engine is not passing the contract signed events on correctly?
So my question is, is there a known issue with multiple clauses not being able to receive contract signed requests?

OK so an update, I have run the test again by creating a new contract with both clauses added and this time the clause that was moving onto the contract signed state previously is no longer doing so, but the other is. So my claim that it is the same clause each time is not the case, it appears to be random which one actually gets/processes the contract signed event.
I also checked the Timeline and can see that both have been sent both the init and contract signed requests.

At the moment, the Cicero engine triggers the first clause which matches the given request. We've had recent discussions on the Ergo call about this (see https://github.com/accordproject/ergo/issues/550).
For the time being, you might want to merge the two clauses into one if possible for your scenario.
Any examples and requirements on triggering multiple clauses for the same event would be very useful since we haven't encountered many such scenarios yet.

OK that probably explains it. So the reason for having two clauses is because the contract has two clauses, separated by static text in between.
At the top of the contract is the SOW definition that outlines the parties and the contract affective dates etc. This has been implemented as a clause because I need to request that information which is then used by the second clause (see below) by passing in the SOW parameters returned in the response from this clause.
Then at the bottom of the contract there is the clause that performs a calculation, and amongst the information passed into its request, it also takes the party information returned by the clause above. The orchestration between the clause service calls is all handled by Node-RED.
In between both these clauses there will be static text, therefore we could not combine the two clauses into one.
We have (as you are aware) worked on other use cases that used the same pattern for the same reasons, but this worked because the lifecycle management was only implemented on one of the clauses, so this problem was never encountered.
If this explanation does not make sense then happy to have a call to demonstrate.

This makes sense to me. What do you think the order of invocation of the two clauses should be?

This makes sense to me. What do you think the order of invocation of the two clauses should be?

@dselman Are you talking in terms of executing the clause or the order in which the contract signed events should be dispatched to each clause in the contract?

This makes sense to me. What do you think the order of invocation of the two clauses should be?

@dselman Are you talking in terms of executing the clause or the order in which the contract signed events should be dispatched to each clause in the contract?

The latter: we need deterministic execution, so if we have N clauses that all want to process the same incoming transaction we need to somehow order them, and because each could perform state updates, it will be important for the programmer to understand this "conflict resolution". Thoughts?

OK so in my specific case it does not matter which order, because each clause is transitioning from an initialised state to a contract signed state. But I understand your point, so somehow we need to specify an order. Maybe this could be implemented as an annotation much like in Java, for example:
@dispatch(order = n)
clause contractSigned(request : ContractSigned) : Response {
...
}

Clauses with the same order or those that do not specify one are then the mercy of the dispatcher as to the order in which they are called.
The other issue is how we make this process atomic, i.e. if one clause successfully transitions state but another fails then the contract is inconsistent. This would need a way of reverting back to a last known state for each clause in the contract. This all starts to get quite complex!

Another way is to consider a sequence clause (like an atomic flow of execution), that will enforce the order of invocations and determine actions on failure.
Can a clause invoke another one ?

Closing in favour of https://github.com/accordproject/ergo/issues/550


dlopen bypass broken on Android 12 (S)

Seems to work fine on Android versions 11 and lower, but does not appear to work correctly on Android 12. I'll take a look at it later and see if I can find any reason/fix for this.
It looks like libssl.so (the test) is able to be opened on Android 12, but while other libraries like libhwui.so can be opened on Android 11, they cannot be opened on Android 12.

Looks like this https://github.com/quarkslab/android-restriction-bypass should still work; for libhwui.so specifically, I did have to add /apex/com.android.i18n/lib and /apex/com.android.i18n/lib64 to set_ld_library_paths.
Some debugging also showed that RestrictionBypass wasn't loading libhwui.so on Android 12 because it couldn't load all of it's dependencies. The dependency libandroidicu.so cannot be loaded from the ART namespace so I don't know if it is fixable in the scope of this implementation.

Hi yes currently it's only unsealing the java/vm part. Library loading is currently not supported, but I will work on it. Thanks for your feedbak


improve readability by fixing tab inconsistencies

Fixes

Fixes #84  by @mbonamensa
Description

The tab inconsistencies in the home-buckets.php make the code difficult to read. This fix removes unnecessary tabs and creates a uniform indentation. This makes the code look clean and readable.
Technical details

Tests

Screenshots

Problem

Solution

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@possumbilities @TimidRobot  I didn't check the second checkbox because I am not sure what that means. Does it mean I have to merge with my main branch first? Anyone else who knows and can help? Thanks.

@mbonamensa you can tick that, it simply means you are requesting a PR that targets the main branch i.e an update to the files cloned by all interns

@mbonamensa you can tick that, it simply means you are requesting a PR that targets the main branch i.e an update to the files cloned by all interns

Oh okay. Thanks.

Thank you so very much for your contribution, but I'm closing this PR. Please see this comment for further details: https://github.com/creativecommons/search/issues/84#issuecomment-1279422799


Fix the global request title logging

08:21:09.4147 Global Diagnostic Readiness 1 Request
should be:
08:21:09.4147 Global DM5 Request

Created in the wrong place.


[SUGGESTION] object oriented - classes_cpp.md

The page is very clear and the concepts flow naturally - but it would be nice for the exercises to all have an expected output no matter how small, that you tell us about before we peak at the solution.
this allows people to try to run and debug their code until they get the expected behaviour before they look at your solution, also it incentives people to compile and run the code. if what they write looks kind of like your solution at the minute people might scroll away even if their class is defined in the wrong spot (accidentally declared my vectors before defining position) if they don't have the reflex to compile the code every time they change it, which new-comers to compiled languages won't necessarily do!

Thanks @HeloiseS, I agree it would be good to have an expected behaviour for these problems, we'll have a look through and add these where appropriate


use utils.Logger not log

I've been doing some quic-unrelated debugging with Syncthing and noticed log output in a format that Syncthing doesn't use (https://github.com/syncthing/syncthing/issues/7146):
2020/11/24 10:52:01 Failed to sufficiently increase receive buffer size. Was: 208 kiB, wanted: 2048 kiB, got: 416 kiB.

Turns out it is quic logging directly to stdout instead of using it's own logger.
Please let me know if the error itself is problematic, then I can enable quic logging locally and see if it comes up consistently.

Could you please update your contributing section in the readme. Nothing in this private repo suggested to me that this is a google project. I know signed it as I already PRed and will probably guess I'll come accross a google project again anyway in the future, but if I'd new I wouldn't have done it for such a trivial change.
@googlebot I signed it!

We're not logging to stdout, we're just using the log package. And we're deliberately doing that. If you use the default Linux UDP receive buffer size, you're guaranteed to have bad performance on high-bandwidth links.

Ok, apparently I've jumped to wrong conclusions. Getting these lines printed to stdout and the presence of
		logger.Debugf("Connection doesn't allow setting of receive buffer size")

just a few lines above the usage of log, I assumed that was the reason. Should I open an issue to track that and find out what actually causes this?

If you use the default Linux UDP receive buffer size, you're guaranteed to have bad performance on high-bandwidth links.

Good to know, thanks for the hint. The use-case is indeed high-bandwidth and on linux and almost any other OS@ data transfer between the same application using quic-go. And we don't (recommend to) modify any UDP settings as far as I am aware, so this definitely affects us. Definitely good to know if that pops up in support, unfortunately nothing we can do pro-actively given it requires privileges to change.

Having looked at your logging implementation this is how I understand it works:
You have an internal Logger interface and use a DefaultLogger instance of that for logging on different severity levels. The output of that default logger goes to the default logger of Go's log package. DefaultLogger is controlled by the env var QUIC_GO_LOG_LEVEL, which disables all logging by default, as described in https://github.com/lucas-clemente/quic-go/wiki/Logging. However in addition to this, you also use the log package directly in places, thus circumventing the logging control by QUIC_GO_LOG_LEVEL. Did I get this right?
As you log to the default logger of log, there's no way for an application using quic-go to control specifically quic-go's logging. If these errors are so bad, that they must reach the user of QUIC, then make them errors. Or expose a logging interface in the public API and log at error level by default instead of disabling, so that the user of your library can hook into that and integrate quic-go's logging into their own logging. It's not like I don't want to know when errors happen in QUIC, I just don't want any library to directly print things to stdout and thus confuse my users with weird looking log lines coming from Syncthing, but not really.

how about just returning error to user and let it decide what to do ?

Thank you for the discussion. This issue should have been alleviated by #2923 (which is included in the v0.19.3 release).


chore: include correct css-vars for selected theme

При переключении темы в сторибук не подтягивались токены теней (блютинт). Пофиксил.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.483%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7390

Relevant Lines:
8364

💛  - Coveralls


[XCUITest] Detox v21 release candidate with web-view support.

RC version is 21.0.0-rc.5. We are testing internally ATM
This version is still unstable and there are critical fixes that need to be made in it (including performance improvements)


Cannot connect to softAP when first connect to a TPLINK Wi-Fi AP

Steps to reproduce:
(1) open a terminal 1, type
sta tplink_ssid tplink_password
(2) open another terminal 2, type
ap csi_softap
(3) in terminal 1, type
sta csi_softap
resulted an endless loop.

The logic you executed is wrong. One device cannot connect to two APs at the same time. Please refer to the following operations:
Steps to reproduce:
(1) open a terminal 1, type
sta tplink_ssid tplink_password
ap csi_softap
(2) open another terminal 2, type
sta csi_softap

Thanks for your reply. Is there any way in monitor mode to connect to one AP first, then disconnect from it, after that connect to another AP? What are the operations needed to disconnect from the first AP in order to connect to the second AP successfully?

By the way, I have two ESP32 boards, terminal 1 connect to board1, terminal 2 connect to board 2.

I use board1 to connect to a TPLINK AP first to sync SNTP time, then I want to keep the synced local time and connect to board2's softAP to do experiment.

By the way, I have two ESP32 boards, terminal 1 connects to board1, terminal 2 connects to board2.

You need to call esp_wifi_stop() before reconfiguring other Wi-Fi

I use board1 to connect to a TPLINK AP first to sync SNTP time, then I want to keep the synced local time and connect to board2's softAP to do experiment.

If you want to achieve your board1 synchronization requirements, you need to enable the NATP service on Board2
Or there is Board2 synchronized time, indirectly transmitted to Board1 via Wi-Fi

Thanks. I have managed to sync timestamp from Board2 to Board1 through TCP communication.


We rely on your plugin for real work. It's irresponsible to release untested version once in 5 months and ignore all issues.

It's not like we can rollback to previous version of plugin. Figma ecosystem does not have that possibility. You release broken plugin and we are stuck.

I agree, I spent all day yesterday trying to figure out why it wasn't pulling to the neutral pallet only to realize it's a bug. And I tried to use it again now and it doesn't update at all. Why is QA not testing this properly? I would never release an app from a well know company in this state. PLEASE test your app. I lost a whole day to work yesterday.

This plugin is a nightmare. Somethimes it works, sometimes is totally does not save the colors.
I have tried using this plugin on 2 project right now. The first project I got it working somewhat. When I open the project now the theme colors are kept when loading the theme. But in my second project no matter how many times I try to set the colors and save the theme, on every instance I re-open the project the default purple colors are reset.

So, "not planned" to be responsible and test the plugin before releases?


Travis: Rely on default directives

This PR changes the Travis configuration to stay closer to "default settings".

Thanks, those were added by bundle gem

Thank you, I now wrote https://github.com/bundler/bundler/pull/6968


A way to opt out of version checking

I'm intending to package felix. Since the update process is tied to the distro packaing, I want it to not check for update by any means (the user won't be able to update the package anyway). Also, since it just spawn a cargo command, it will just print the error message for lots of normal users not having cargo installed.
Adding a feature flag at build time to toggle the version check behavior (on running fx --version) would be nice.

Thanks, you're right: The cargo command does not work for many cases. I'll remove at least the cargo search line.
Is printing the current version OK for your use case? Also, could you tell me to which repository you're going to package?

Is printing the current version OK for your use case?

I'm doing exactly that (printing the current version only). I made a naive patch here just to remove the check_version function: https://gitlab.alpinelinux.org/alpine/aports/-/blob/432db0e2c870d11b187b75627585d678372489f9/testing/felix/disable-version-check.patch

Also, could you tell me to which repository you're going to package?

The attempt can be seen here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/46337. It's for AlpineLinux.

I'm doing exactly that (printing the current version only). I made a naive patch here just to remove the check_version function: https://gitlab.alpinelinux.org/alpine/aports/-/blob/432db0e2c870d11b187b75627585d678372489f9/testing/felix/disable-version-check.patch

Smart and clear. I'll change the code like this in the next release. It is a very simple change and will only take a few days. (Of course PR is welcomed though)
Would appreciate to let me know when the packaging is finished.

The MR got merged. felix should be available on AlpineLinux edge's testing repo now.

Released #195


add docker-based shiny R example

similar to this one: https://github.com/ploomber/doc/pull/235
but for shiny R

I just realized we have a docker-based example: https://github.com/ploomber/doc/tree/main/examples/shiny-r/igraph
but it's not named docker-based as our other example. let's just rename it and update the docs


this issue is only for test

Please answer these questions before submitting your issue. Thanks!

What did you do?
If possible, provide a recipe for reproducing the error.

What did you expect to see?

What did you see instead?

What version of TiDB are you using (tidb-server -V)?

first comment test