[import/no-cycle] possible false-positive with re-exported names

Given these files:
a.js
import {b} from './internal';
export const a = 'a';

b.js
import {a} from './internal';
export const b = 'b';

internal.js
export * from './a';
export * from './b';

.eslintrc
plugins:
  - import

parserOptions:
  ecmaVersion: 2020
  sourceType: module

rules:
  import/no-cycle: [2]

I see these errors:
a.js
  1:1  error  Dependency cycle detected  import/no-cycle

b.js
  1:1  error  Dependency cycle detected  import/no-cycle

internal.js
  1:1  error  Dependency cycle detected  import/no-cycle
  2:1  error  Dependency cycle detected  import/no-cycle

This is a example of @mweststrate's internal module pattern and if I understand correctly, there are no actual circular dependencies here. Is it a false-positive or a error in the pattern itself?

This is absolutely a circular dependency, because a requires internal, and internal requires a (and the same for b).
In other words, the pattern itself violates the no-cycle rule because it forces everything to be a cycle.

I don't understand enough of how module resolution works, but I was under the impression that this pattern exploits a mechanism in the resolution that leads to modules being loaded in the order defined in internal.js, so the import in a will initially resolve to {}, then internal will load the modules and the re-exported values then resolve to the actual exports.
The pattern is in use in MobX so it apparently does work to some extent.
Some info from the linked post:

Being a cycle is not about touching the filesystem; it's about conceptually creating a situation where two files mutually depend on each other.
What you're describing is how node's CommonJS makes circular dependencies possible - but they're still circular.

I guess technically you're correct. I didn't really like that pattern anyways so I willl avoid it.

The requirement of the project is to separate DOM from logic in different files.
Thus, I have these files:
default.js
import { submitForm } from './logic'

function displayTaskForm(key) {
  // function create form HTML content with btn submit.
  submitForm(addTaskbtn, key);
  return form;
}

export { displayTable };

logic.js
import { displayTable } from './default';

const submitForm = (btn, key) => {
  // Adds event listener to add input to the table && local storage
  displayTable(key) // shows the table content including recent input
  return btn;
}

export { submitForm };

And I have a similar error as above:
default.js
1:1  error  Dependency cycle detected  import/no-cycle
logic.js
1:1  error  Dependency cycle detected  import/no-cycle
Could you advise how I could solve this issue? the problem is I have to split my DOM from the logic part. I don't see a way to link creating DOM based on if statement results.
Here is the original repository link


[AUTH-388] set pod security admission labels for namespace

What type of PR is this?
bug
What this PR does / why we need it?
This sets pod security admission labels. Currently, none are set and starting with OpenShift 4.13 this generates warnings in Telemetry. This fixes it.
Refer to https://kubernetes.io/docs/concepts/security/pod-security-standards/ to further tighten the labels potentially to the recommended restricted level.
The labels were determined by using the https://github.com/stlaz/psachecker tool.
Which Jira/Github issue(s) this PR fixes?
Fixes #
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

/lgtm
/approve


Renaming refactor

rename BindingAccess to SymbolAccess
rename SymbolType to SymbolBinding
simplify the SymbolBinding enum variant names

@tohrnii thanks for review and for catching those oversights. I believe I've addressed everything, but could you please check again?


doc: require more detailed description of struct tags

Maybe we need more detailed description of struct tags.
Such as:
nullzero will marshal as SQL NULL, but when dialect support DefaultPlaceholder, it will marshal as SQL DEFAULT.
In my case,
i can't find how to marshal zero value as DEFAULT before i read code.
This may be my own reason, not question of document.

Thanks for the suggestion - I've updated the docs with your edit.


Allstar

Hello, my name is Laurel , an Outreachy applicant.
I have investigated what Allstar is about, it's capabilities and how it aligns with the needs of this project as indicated in the checklist in issue #12.
I found out that Allstar is a Security Policy for open source projects which can help to ensure that all repositories have a security policy, scan all repos for common vulnerabilities, enforce best practices for code reviews, and require security testing for all releases.
I have written a documentation which highlights;
How much of the checklist Allstar can cover
What items needs to be manually configured and
Proposed steps to enable Allstar across organizations.
Please let me know if i need to fix anything to make it a better contribution. Thank you

As discussed on #21, I'm closing this one.


message supplier

When we run code with
logger.debug("heavy message generator")
or
logger.trace("heavy message generator")
and debug or trace is not enabled, program have to calculate method argument to throw it away in next step.
Message supplier will speed up code execution ))

Ops. We are thinking in the same direction.
If I were You I would add SLF4J-504 into p/r title.

Will you add info/warn/error ?

"If it OK I will add all other methods" - that's the answer ))))


Kube failed: ServiceError: client error (Connect)

Bug Description

when run with VSC  it's failed with error:

mirrord preparation failed: Failed to create mirrord-agent: Kube failed: ServiceError: client error (Connect). Please check the logs/errors.

then run mirrord exec -f config.json -- sh with error:

⠤ mirrord exec
    ✓ running on latest (3.119.1)!
⠖ mirrord exec
    ✓ running on latest (3.119.1)!
  ⠚ preparing to launch process
  x mirrord exec
    ✓ running on latest (3.119.1)!
    x preparing to launch process
      ✓ layer extracted
      ✓ operator disabled                                                                                Error:   × Failed to create mirrord-agent: Kube failed: ServiceError: client error (Connect)
  help: 1. Please check the status of the agent pod, using `kubectl get pods` in the relevant namespace.
                2. If you don't see any `mirrord-agent-[...]` pods, then try running `kubectl get jobs`, and `kubectl describe mirrord-agent-[...]`.
                Make sure it is able to fetch the agent image, it didn't fail due to lack of resources, etc.

        - If you're still stuck:

        >> Please open a new bug report at https://github.com/metalbear-co/mirrord/issues/new/choose

        >> Or join our Discord https://discord.gg/metalbear and request help in #mirrord-help

        >> Or email us at<EMAIL_ADDRESS>

kubectl get pods | grep mirrord:

No resources found in default namespace.

kubectl get jobs | grep mirrord

No resources found in default namespace.

BTW: docker pull is ok
pls help me to fix it, thx you all
Steps to Reproduce
the config.json as follow:
{
    "operator": false,
    "feature": {
        "network": {
            "incoming": {
                "mode": "steal"
              }
        },
        "fs": "read",
        "env": true
    },

    "use_proxy": false,
    "target": {
        "path": {
            "pod": "foobar-66475d9f77-cmtxr"
        },
       "namespace": "foobar"
      },
    "internal_proxy": {
        "idle_timeout": 180
    },
    "agent": {
        "log_level": "mirrord=trace,debug,warn",
        "namespace": "default",
        "image": "ghcr.io/metalbear-co/mirrord:latest"
    }
}

Backtrace
No response
mirrord layer logs
No response
Internal proxy logs
No response
Your operating system and version
os: Ubuntu 22.04.4 LTS  k8s: v1.30.4 go: go1.22.0 linux/amd64
Local process
xxx
Local process version
No response
Additional Info
No response

Hi,
Does kubectl get pods work?
Do you have HTTP_PROXY set?

can you run like this and share logs?
MIRRORD_PROGRESS_MODE=off RUST_LOG=mirrord=trace mirrord exec -f config.json -- sh

can you run like this and share logs?
MIRRORD_PROGRESS_MODE=off RUST_LOG=mirrord=trace mirrord exec -f config.json -- sh

thx for your help,  with  run likes it: i found this log:
 DEBUG start:create_and_connect: mirrord::connection: Failed to detect OpenShift error=KubeError(Service(hyper_util::client::legacy::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) } })))

so set this option:
    "accept_invalid_certificates": true,

it's works

Thanks for reporting. We'll create an issue to detect that error and print nicer explanation.


Added Bfs algo visualizer

Type of change

[x] Added new project
[ ] Bug fix
[ ] New features
[x] Enhanced documentation

Changes proposed in this pull request

Project name :  BFS Algo vizulizer

Short description : his project helps us to visualize BFS algorithm by searching end point from start in a maze.

Checklist

[x] The code is Python 3 compatible
[x] I have added my project in a folder which includes all the necessary files

Looks good! Thank you. 🚀

@Mrinank-Bhowmick  please add the hacktober tag to this pr if its eligible .


[PSM Interop] Enable xDS affinity test for Node

Similar to #34146, this will only run on master for now. This will work after grpc/grpc-node#2568 is merged.

[ ] grpc/node/master/xds_k8s_lb

framework.helpers.retryers.RetryError: Retry error calling framework.test_app.client_app.XdsTestClient.find_server_channel_with_state: timeout 0:05:00 (h:mm:ss) exceeded. Last exception: ChannelNotFound: [psm-grpc-client-6cf9cc7d9c-t9sdv] Client has no READY channel with server xds:///psm-grpc-server:59164
Reason: The client couldn't connect to the server.

Attempt 2:

[ ] grpc/node/master/xds_k8s_lb

Attempt 3:

[ ] grpc/node/master/xds_k8s_lb

The test passed, and I merged the implementation PR.


Clarify points in Line2D doc

Clarify that PoolVector2Array Points are interpreted as local vectors and not global. Closes https://github.com/godotengine/godot-docs/issues/3115

Note that this is also true for Polygon2D and any other node which accept an array of vertices, it's just that Line2D is more likely (IMO) to be used in global coordinates context.

Thanks!

Cherry-picked for 3.2.3.


app crash when show keyboard

Steps to Reproduce

app launch success
tap [TextField] and show keyboard
app crashed

Logs
[2019-05-21 14:55:43.985] [11248] [11248] [4] [crash_dump32] : obtaining output fd from tombstoned, type: kDebuggerdTombstone
[2019-05-21 14:55:43.986] [1037] [1037] [4] [/system/bin/tombstoned] : received crash request for pid 10886
[2019-05-21 14:55:43.987] [11248] [11248] [4] [crash_dump32] : performing dump of process 10834 (target tid = 10886)
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : Build fingerprint: 'vivo/PD1728/PD1728:9/PKQ1.180819.001/compiler04081614:user/release-keys'
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : Revision: '0'
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : ABI: 'arm'
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : pid: 10834, tid: 10886, name: 1.gpu  >>> com.izhaowo.user <<<
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : signal 6 (SIGABRT), code 0 (SI_USER), fault addr --------
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] : Abort message: '[FATAL:flutter/flow/layers/transform_layer.cc(28)] Check failed: transform_.isFinite().
'
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] :     r0  00000000  r1  00002a86  r2  00000006  r3  00000008
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] :     r4  00002a52  r5  00002a86  r6  c3efdb3c  r7  0000010c
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] :     r8  c3efe290  r9  c3efdc98  r10 00000001  r11 c3eff428
[2019-05-21 14:55:44.015] [11248] [11248] [7] [DEBUG] :     ip  e59a33c4  sp  c3efdb28  lr  e590e11d  pc  e5904ffe
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :
backtrace:
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #00 pc 0001cffe  /system/lib/libc.so (abort+58)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #01 pc 00136ea3  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #02 pc 00134569  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #03 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #04 pc 00132043  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #05 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #06 pc 001345c1  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #07 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #08 pc 0013228f  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #09 pc 00132571  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #10 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #11 pc 00132d17  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #12 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #13 pc 001345c1  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #14 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #15 pc 001345c1  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #16 pc 001322c7  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #17 pc 001345c1  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #18 pc 00131641  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #19 pc 001590ff  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #20 pc 0015939f  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.024] [11248] [11248] [7] [DEBUG] :     #21 pc 00159c51  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #22 pc 001592ab  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #23 pc 00159609  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #24 pc 00138041  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #25 pc 00139461  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #26 pc 0000fbf9  /system/lib/libutils.so (android::Looper::pollInner(int)+636)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #27 pc 0000f8ff  /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+26)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #28 pc 0000c699  /system/lib/libandroid.so (ALooper_pollOnce+56)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #29 pc 001394fb  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #30 pc 001371eb  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #31 pc 00138441  /data/app/com.izhaowo.user-Kj2NVrNUCkV9NDIpjGUv2g==/lib/arm/libflutter.so (offset 0x113000)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #32 pc 00072471  /system/lib/libc.so (__pthread_start(void*)+22)
[2019-05-21 14:55:44.025] [11248] [11248] [7] [DEBUG] :     #33 pc 0001e025  /system/lib/libc.so (__start_thread+24)

flutter doctor -v
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Mac OS X 10.13.6 17G6030, locale zh-Hans-CN)
    • Flutter version 1.5.4-hotfix.2 at /Users/suke/development/flutter
    • Framework revision 7a4c33425d (3 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/suke/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/suke/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 1.9.4
    • CocoaPods version 1.7.0.beta.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 29.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[!] IntelliJ IDEA Ultimate Edition (version 2017.1.5)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 171.4694.29
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[!] VS Code (version 1.5.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (1 available)
    • MI 8 • f0a15e3f • android-arm64 • Android 9 (API 28)

! Doctor found issues in 2 categories.

see here

@ShaiDemri  tks, i will check it ;)

App crashing in release
flutter: ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
flutter: The following assertion was thrown during a scheduler callback:
flutter: Offset argument contained a NaN value.
flutter: 'dart:ui/painting.dart': Failed assertion: line 38: '<optimized out>'
flutter:
flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
flutter: more information in this error message to help you determine and fix the underlying cause.
flutter: In either case, please report this assertion by filing a bug on GitHub:
flutter:   https://github.com/flutter/flutter/issues/new?template=BUG.md
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #2      _offsetIsValid (dart:ui/painting.dart:38:10)
flutter: #3      Path.contains (dart:ui/painting.dart:2090:12)
flutter: #4      ClipPathLayer.find (package:flutter/src/rendering/layer.dart:1137:19)
flutter: #5      ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #6      OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #7      TransformLayer.find (package:flutter/src/rendering/layer.dart:1218:18)
flutter: #8      ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #9      ClipPathLayer.find (package:flutter/src/rendering/layer.dart:1139:18)
flutter: #10     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #11     PhysicalModelLayer.find (package:flutter/src/rendering/layer.dart:1515:18)
flutter: #12     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #13     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #14     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #15     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #16     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #17     PhysicalModelLayer.find (package:flutter/src/rendering/layer.dart:1515:18)
flutter: #18     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #19     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #20     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #21     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #22     ContainerLayer.find (package:flutter/src/rendering/layer.dart:616:36)
flutter: #23     OffsetLayer.find (package:flutter/src/rendering/layer.dart:846:18)
flutter: #24     TransformLayer.find (package:flutter/src/rendering/layer.dart:1218:18)
flutter: #25     RenderView._updateSystemChrome (package:flutter/src/rendering/view.dart:218:58)
flutter: #26     RenderView.compositeFrame (package:flutter/src/rendering/view.dart:201:9)
flutter: #27     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:350:16)
flutter: #28     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:701:13)
flutter: #29     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:286:5)
flutter: #30     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1012:15)
flutter: #31     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:952:9)
flutter: #32     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:864:5)
flutter: #36     _invoke (dart:ui/hooks.dart:219:10)
flutter: #37     _drawFrame (dart:ui/hooks.dart:178:3)
flutter: (elided 5 frames from class _AssertionError and package dart:async)
flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════

@zcweng How's it with current flutter stable? It should have been fixed already in June.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

hello, i'm having the same problem, could you explain how you fixed it?

@Paul-cbt
can you please open a new issue providing
your flutter doctor -v, your flutter run -v and a minimal reproducible code sample


Incorrect output when any of the 64-bit words begins with a zero nybble

As the string conversion is not zero-padded, in the case that any of the 64-bit words of the hash starts with a zero, the output will be incorrect (too short).
To fix this, replace the line:
ss << std::hex << h[i];

with:
ss << std::hex << std::setw(16) << std::setfill('0') << h[i];

In the SHA512::digest method.

This is fixed now. Thanks for the heads up!


triangle: incorrect test in some tracks

Please check if there's a test that states that a triangle with sides 2, 4, 2 is invalid. The triangle inequality states that for any triangle, the sum of the lengths of any two sides must be greater than or equal to the length of the remaining side. If this doesn't affect this track, go ahead and just close the issue.

There is such a test which demands a failure. AFAIR I just took this from JSON or another track. Is it enough to just remove that test or shall I rewrite it to test for a specific kind?
I will tackle this after #84 is finished and merged.

Oh, good question. I think we should have it return an isosceles triangle -- it's a good edge case to have.

Hmm, I just asked Wolfram alpha, it does classify as degenerated.
So I'd go for either taking further research when a triangle is degenerated
exactly and add it as another possible return value for kind. Or leaving as
is (error) or do classify as isosceles, because this is what comes when you
simply change the inequality.
Since we have 1 o'clock in the morning here, I'll go to bed now, but I'll
do some more research tomorrow and open a ticket in xcommon (or chime into
an ongoing one if there is one).
Katrina Owen<EMAIL_ADDRESS>schrieb am Sa., 30. Jan. 2016 00:58:

Oh, good question. I think we should have it return an isosceles triangle
-- it's a good edge case to have.
—
Reply to this email directly or view it on GitHub
https://github.com/exercism/xerlang/issues/85#issuecomment-177024421.

This is very interesting. You are right.
2,4,2 is not a triangle because since 2 + 2 equals the length of the 4, then the 2 + 2 sides merge into the same plane so you end up with only a line.. (Technically is is three lines that occupy the same space of the 4 length)

So I'd go for either taking further research when a triangle is degenerated exactly and add it as another possible return value for kind.

So wikipedia is wrong, huh. Imagine that! OK, let's do some more research.

Wikipedia is not wrong. The 2,2,4 is a degenerate triangle, but still a triangle.

So for a degenerate triangle (e.g. 2,2,4) which looks like a line segment do we return "isosceles" as kind or "degenerate"?

My opinion is that we either add degenerate as a case, or specifically say in our problem definition that degenerate triangles should be rejected.
To be honest, rejecting degenerate triangles feels like a cleaner solution. I'd just like the problem description to get an update.

triangle.md could really need some improvement. I think it should also mention the 3 kinds.
+1 rejecting degenerate triangles

for adding degenerate as a case

We can then separate the math definition from the notion of accepting or rejecting as a triangle, thus moving the conversation away from declaring what is or not a triangle, to just stating the type of case.
(I personally think degenerate triangles are not triangles and should be rejected! they are just lines! ;)  "the emperor has no clothes" yo! ).

It seems like the generally vibe here is to reject degenerate triangles and update the .md accordingly, yeah?

yeah, agreed

:+1:

So actually, we leave all the "faulty" tests as they are and repair the
"correct" ones?
Which again would mean I don't need to do anything here?
Katrina Owen<EMAIL_ADDRESS>schrieb am Sa., 30. Jan. 2016 20:25:

yeah, agreed
—
Reply to this email directly or view it on GitHub
https://github.com/exercism/xerlang/issues/85#issuecomment-177280813.

I'm not sure I understand your double quotes, @NobbZ, but the xerlang triangle tests look good as they are.

I say that we do exclude examples that stretch the definition to an absurd[1] degree.   We keep to general position not special position geometry, and keep this where it should be in the context of the program here.  If the assumption is that Triangles have area, this goes against that assumption, and is suitable for our purposes, and keeps everything  at a non-college level, and is reasonable.
We don't test for the other more commonly known triangles, which is to say "right, acute or obtuse" why are we jumping into special position before we talk about all the general position triangles?
This is (as far as I can see) meant to be a simple exercise, even more so since we test for only 3 specific triangles.

Yeah, having slept on this I think that the right approach is to avoid the edge cases and stick to the basics (having things that obviously violate the triangle inequality thing is great, the distinction between not-a-triangle and yes-but-degenerate seems like a tangent that isn't useful here.

I've summarized this issue here: https://github.com/exercism/x-common/issues/202
I am closing this issue. If necessary I will open a new issue once we have come to an agreement about how to resolve the inconsistencies and what exact steps to take.


Fix type inference issue when upgrading from javac 8 to 9.

In https://bugs.openjdk.java.net/browse/JDK-8033718 upstream fixed a bug where type inference wasn't properly handling capture variables as upper bounds.  This causes a backwards incompatibility in versions of javac that include this fix, starting with 9.  This change adds an explicit type argument to work around the incompatiblity.

Coverage increased (+0.1%) to 98.873% when pulling e99ea574b114351969501330e6fbbc5e8fe412cc on eaftan:master into 936bbd1b7dfbcf64a3b990682bfc848213441d14 on amaembo:master.

Thanks!


Uniform Standards Request: Experimental Repository

Hello!
We believe this repository is Experimental and therefore needs the following files updated:

[x] The Experimental badge
[x] The Experimental Statement in the README.md
[x] Getting Started Tutorial
[x] README.md
[x] LICENSE
[x] CI/CD
[x] OWNERS.md
[x] Developer Certificate of Origin
[x] At least one maintainer

If you feel the repository should be maintained or end of life or that you'll need assistance to create these files, please let us know by filing an issue with https://github.com/packethost/standards.
Equinix Metal maintains a number of public repositories that help customers to run various workloads on Equinix Metal. These repositories are in various states of completeness and quality, and being public, developers often find them and start using them. This creates problems:

Developers using low-quality repositories may infer that Equinix Metal generally provides a low quality experience.
Many of our repositories are put online with no formal communication with, or training for, customer success. This leads to a below average support experience when things do go wrong.
We spend a huge amount of time supporting users through various channels when with better upfront planning, documentation and testing much of this support work could be eliminated.

To that end, we propose three tiers of repositories: Private, Experimental, and Maintained.
As a resource and example of a maintained repository, we've created https://github.com/packethost/standards. This is also where you can file any requests for assistance or modification of scope.
The Goal
Our repositories should be the example from which adjacent, competing, projects look for inspiration.
Each repository should not look entirely different from other repositories in the ecosystem, having a different layout, a different testing model, or a different logging model, for example, without reason or recommendation from the subject matter experts from the community.
We should share our improvements with each ecosystem while seeking and respecting the feedback of these communities.
Whether or not strict guidelines have been provided for the project type, our repositories should ensure that the same components are offered across the board. How these components are provided may vary, based on the conventions of the project type. GitHub provides general guidance on this which they have integrated into their user experience.

Hi @rainleander how are you enforcing DCO? I also noticed that this issue was closed, but the CircleCI job that was added didn't do anything?

We're having conversations re: DCO - asking why people do or do not want to sign off / agree with it. Nothing, say, legal or intimidating. The current CI is a simple Hello World script that compiles until someone smarter than me has time to build a more thorough test.


Docs for feature: "System" catalog framework to be able to upgrade system charts

(Support minimum_rancher_version and maximum_rancher_version in catalog)

https://github.com/rancher/integration-test-charts/blob/master/charts/chartmuseum/v1.6.0/questions.yml
Charts now support a field called rancher_min_version and rancher_max_version in the questions.yml file to specify the versions of Rancher that the chart is compatible with. When using the UI only app versions that are valid for the version of rancher running will be shown. API validation is done to ensure apps that don't meet the rancher requirements can not be launched. An app that is already running will not be affected on a rancher upgrade if the newer rancher version does not meet the apps requirements.


io.micronaut.core.annotation.Nullable has stereotype @Nonnull(when = When.MAYBE) on it hence fails on null properties supplied

Expected Behavior
io.micronaut.core.annotation.Nullable should make parameter non-required, nullable.
Actual Behaviour
This on is kind of nonsense... so annotation io.micronaut.core.annotation.Nullable has @Nonnull(when = When.MAYBE), so this module - Serde - makes annotated properties required, non-nullable 🥇
:)
When I removed annotation io.micronaut.core.annotation.Nullable after several hours of trials and failures- it worked!
io.micronaut.core.annotation.AnnotatedElement
    /**
     * @return Whether the element is declared as not being null
     */
    default boolean isNonNull() { // this gives `true` for property annotated with `io.micronaut.core.annotation.Nullable`
        return getAnnotationMetadata().hasStereotype(AnnotationUtil.NON_NULL);
    }

Steps To Reproduce
I guess it simple enough from description.
Environment Information
Serge m7
micronaut 3.3.3
Example Application
No response
Version
3.3.3

Hi soberich,
We encountered a similar issue when working on making micronaut-data work with serde. Also see: https://github.com/micronaut-projects/micronaut-core/issues/6795
The problem here is that io.micronaut.core.annotation.Nullable should never appear in the annotation metadata in the first place. In core, there is a transformer that ensures this. However, as discussed in the issue, if you have a custom mapper that applies to Nullable, it is still possible to have the annotation wrongly present in the metadata. Please verify that you do not have such a mapper present (maybe from an old data version).
I will close this as it's a duplicate of the -core issue.

@yawkat I don't have any custom annotation mappers.
What I do have is this line in lombok.config
lombok.addNullAnnotations = CUSTOM:io.micronaut.core.annotation.NonNull:io.micronaut.core.annotation.Nullable

If this is the cause, than I'd say there should be big red header about it, because this kind of feature/bug cost quite some time to resolve. You would never think that @Nullable causes @Nonnull to be implied.
Isn't that too fragile to rely on the fact that something should never be somewhere? Could it be a good idea to throw an exception then with proper error message if it should never be present in metadata?

@yawkat I don't have any custom annotation mappers.
What I do have is this line in lombok.config
lombok.addNullAnnotations = CUSTOM:io.micronaut.core.annotation.NonNull:io.micronaut.core.annotation.Nullable

If this is the cause, than I'd say there should be big red header about it, because this kind of feature/bug cost quite some time to resolve. You would never think that @Nullable causes @Nonnull to be implied.
Isn't that too fragile to rely on the fact that something should never be somewhere?

@soberich could you provide an example with how to reproduce?

with @Nullable

without @Nullable

So virtually with there is no way to indicate it is nullable, unless, of course, Optional

Hope this helps to repro.
Thanks!

You can fix this by upgrading to micronaut-data 3.3.0-M1 since the bug is there. When Micronaut 3.4 is final and this library is final it will be a non-issue

@graemerocher, sorry I could not make it practical.
This issue is regaring micronaut-serialization and if I can extrapolate it to ..-core what does it have to do with *-data?
In a repro there is a data-processor but I believe it not related to that.
So what is the workaround exactly?

@graemerocher @yawkat I'd appriciate a workaround description. It's unclear. Thanks a lot in advance!

The issue is this class in micronaut-data-processor in Micronaut Data 3.2.x https://github.com/micronaut-projects/micronaut-data/blob/3.2.x/data-processor/src/main/java/io/micronaut/data/processor/mappers/support/NullableAnnotationMapper.java
This class doesn't exist in 3.3.x, hence if you upgrade this dependency the problem goes away

@graemerocher in my main app this didn't change anything, so pulling hairs again.
I managed to adjust reproducer so you can see it for yourself.
Works as you said 👍

however some combinations dependencies which present in main code break this balance

It was quite some trials before removing !! GUAVA worked. So of course the reason that over combo succeeds is that

I hope this helps to resolve!

If it's still qualified as not a bug, please, maybe a comment. We are experiencing quite a lot of trouble with build / setup being quite fragile due to this kind of issue. It's just POC, so, it would be great to prove that concept is viable.

Provide a PR or sample that reproduces

@graemerocher there is a repro attached to this issue all along. It never stopped being a working repro. I am not sure, is it not visible for you, @graemerocher ?


set capacity before adding if size is known

Sets the capacity of Lists and RepeatedField if it is known
=> Avoids allocation of intermediate arrays (when a list is growing and growing) or too large arrays (e.g. protobuf allocates 8-size arrays per default, which can depending on the situation be way too large)

Method
Mean
Error
StdDev
Gen 0
Gen 1
Allocated

NursesSat_WithOutputToNull_pr
1.029 ms
0.0100 ms
0.0094 ms
11.7188
5.8594
58 KB

NursesSat_WithOutputToNull_master
1.046 ms
0.0068 ms
0.0063 ms
11.7188
5.8594
62 KB

=> 1.6 % reduction of duration
=> 6.5 % managed allocation reduction

Thanks


Group.UpdateEntity

Hi,
I don't know why UpdateEntity function trigger all the three callback。what if just trigger OnEntityUpdated，Will this lead to other problems？
Here's some code
        /// This is used by the context to manage the group.
        public void UpdateEntity(TEntity entity, int index, IComponent previousComponent, IComponent newComponent) {
            if (_entities.Contains(entity)) {
                if (OnEntityRemoved != null) {
                    OnEntityRemoved(this, entity, index, previousComponent);
                }
                if (OnEntityAdded != null) {
                    OnEntityAdded(this, entity, index, newComponent);
                }
                if (OnEntityUpdated != null) {
                    OnEntityUpdated(
                        this, entity, index, previousComponent, newComponent
                    );
                }
            }
        }

Cheers

Hi @Ecstasyzzz
Yes, all of them are needed to let collectors and indexes know that sth changed.


Sqlx 0.5.x migrate! macro fails to release Postgres advisory lock

Hi there!
I am running into an issue where in sqlx 0.5.x the migrate! macro run() function fails to release the advisory lock on the Postgres database, resulting in the migration hanging indefinitely. With sqlx 0.5.x I am using Tokio 1.x. Note that this problem does not exist with sqlx 0.4.2 and Tokio 0.2.25.
Here is the code for the migration:
  block_on(async {
    sqlx::migrate!().run(&pool).await.unwrap_or_else(|e| panic!("Migration Failed {}", e))
  });

Cargo.toml:
[package]
name = "myProject"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
log = "0.4.14"
log4rs = "1.0.0"
config = "0.13.1"
dotenv = "0.15.0"
futures = "0.3"
serde = { version = "1.0", features = ["derive"] }
sqlx = { version = "0.5", features = [ "runtime-tokio-native-tls" , "postgres", "migrate" ] }
tokio = { version = "1", features = ["full"] }

When I start my application, it prints this and then hangs. The table it should be migrating never actually gets created, though the _sqlx_migrations table DOES get created.
2022-05-17T13:35:55.975877-04:00 TRACE mio::poll - registering event source with poller: token=Token(1), interests=READABLE | WRITABLE
2022-05-17T13:35:55.978731-04:00 INFO sqlx::query - /* SQLx ping */; rows affected: 0, rows returned: 0, elapsed: 219.667µs
2022-05-17T13:35:55.979751-04:00 INFO sqlx::query - SELECT current_database(); rows affected: 0, rows returned: 1, elapsed: 754.209µs
2022-05-17T13:35:55.980445-04:00 INFO sqlx::query - SELECT pg_advisory_lock($1); rows affected: 1, rows returned: 1, elapsed: 578.541µs
2022-05-17T13:35:55.986325-04:00 INFO sqlx::query - CREATE TABLE IF NOT …; rows affected: 0, rows returned: 0, elapsed: 1.953ms

CREATE TABLE IF NOT EXISTS _sqlx_migrations (
  version BIGINT PRIMARY KEY,
  description TEXT NOT NULL,
  installed_on TIMESTAMPTZ NOT NULL DEFAULT now(),
  success BOOLEAN NOT NULL,
  checksum BYTEA NOT NULL,
  execution_time BIGINT NOT NULL
);

2022-05-17T13:35:55.987935-04:00 INFO sqlx::query - SELECT version FROM _sqlx_migrations …; rows affected: 0, rows returned: 0, elapsed: 589.791µs

SELECT
  version
FROM
  _sqlx_migrations
WHERE
  success = false
ORDER BY
  version
LIMIT
  1

2022-05-17T13:35:55.989089-04:00 INFO sqlx::query - SELECT version, checksum FROM …; rows affected: 0, rows returned: 0, elapsed: 404.917µs

SELECT
  version,
  checksum
FROM
  _sqlx_migrations
ORDER BY
  version

2022-05-17T13:35:55.989357-04:00 INFO sqlx::query - BEGIN; rows affected: 0, rows returned: 0, elapsed: 149.125µs

There is no error message printed or anything.
I dug into the code a bit and it seems like in migrator.rs line 136 conn.unlock().await?; it is trying to release the Postgres advisory lock but never can. Because no error is shown, it is hard to debug. Additionally, if I inspect the locks in Postgres via select * from pg_locks where lockType = 'advisory'; I can see the lock get created after migrator.rs line 98 conn.lock().await?;  executes. If I terminate my application process that lock goes away too.
Migrator.rs run function:
pub async fn run<'a, A>(&self, migrator: A) -> Result<(), MigrateError>
    where
        A: Acquire<'a>,
        <A::Connection as Deref>::Target: Migrate,
    {
        let mut conn = migrator.acquire().await?;

        // lock the database for exclusive access by the migrator
        conn.lock().await?;

        // creates [_migrations] table only if needed
        // eventually this will likely migrate previous versions of the table
        conn.ensure_migrations_table().await?;

        let version = conn.dirty_version().await?;
        if let Some(version) = version {
            return Err(MigrateError::Dirty(version));
        }

        let applied_migrations = conn.list_applied_migrations().await?;
        validate_applied_migrations(&applied_migrations, self)?;

        let applied_migrations: HashMap<_, _> = applied_migrations
            .into_iter()
            .map(|m| (m.version, m))
            .collect();

        for migration in self.iter() {
            if migration.migration_type.is_down_migration() {
                continue;
            }

            match applied_migrations.get(&migration.version) {
                Some(applied_migration) => {
                    if migration.checksum != applied_migration.checksum {
                        return Err(MigrateError::VersionMismatch(migration.version));
                    }
                }
                None => {
                    conn.apply(migration).await?;
                }
            }
        }

        // unlock the migrator to allow other migrators to run
        // but do nothing as we already migrated
        conn.unlock().await?;

        Ok(())
    }

I figured this out. It was caused by using futures::executor::block_on instead of using the tokio runtime block_on. A little bit of reading about tokio and how it works helped immensely. Sorry for the disturbance!

Hey @caamartin35, mind sharing the migrate code you ended up using here?

Oop, nvm. I was seeing this same error but the cause was cockroachdb not having this locking feature, thanks to https://github.com/launchbadge/sqlx/pull/2063 it can be skipped.


Reshadow

Reshadows instead of mutating expression
Resolves #3026
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

There may be an issue with this fix applied to "self"
It seems like there used to be a mechanism to do "let self_renamed = untracked_deref(&self)"
But to rebind this would mean doing
"let self = untracked_deref(&self_renamed)"
But this is not allowed as self is a keyword
All tests pass by ignoring the self parameter, so I am unsure of what test case would cause this to be an issue. Maybe a function that consumes self instead of call by reference?

Can you please expand the description a bit? What was the issue and how this change fixes it. Thanks!


Add more EGraph edge and node color options

Context for changes

New features:

Node and edge coloring can now point to any atribute and define personalized colors via a dictionary.
EGraph plot legend is not limited to the "state" attribute of the node but to any attribute.

Bug fixes:

None

Improvements:

This PR heavily refactors the draw_EGraph function. This is done in order to reduce the function complexity, separate concerns in respect to drawing the graph (nodes, edges and general plor attributes are handled in different places) and allow for better code maintenance/readability.

Documentation changes:

None

Example usage and tests
A funky RHG lattice 🌈

import matplotlib.pyplot as plt
from flamingpy.codes.surface_code import SurfaceCode, alternating_polarity

RHG_code = SurfaceCode(2, ec="both", boundaries="open", polarity=alternating_polarity)

# The following two lines correspond to the feature added on this PR
node_colors = ("type", {"primal": "gold", "dual": "b"})
edge_colors = ("weight", {+1: "g", -1: "r"})

dw = {
    "color_nodes": node_colors,
    "color_edges": edge_colors,
    "label": None,
    "legend": True,
    "title": True,
    "display_axes": False,
}

RHG_fig = RHG_code.draw(**dw)
plt.show()

Performance results justifying changes

[x] Not Applicable

Workflow actions and tests

[x] Not Applicable

Expected benefits and drawbacks
Expected benefits:

Ability to draw colorful codes 😎

Possible drawbacks:

None

Related Github issues

[x] Not Applicable

Checklist and integration statements

[x] My Python and C++ codes follow the coding and commenting styles of this project as indicated by existing files. Specifically, the changes conform to given black, docformatter and pylint configurations.
[x] I have performed a self-review of these changes, checked my code (including for codefactor compliance), and corrected misspellings to the best of my capacity. I have synced this branch with others as required.
[x] I have added context for corresponding changes in documentation and README.md as needed.
[x] I have added new workflow CI tests for corresponding changes, ensuring codecoverage 95% or better, and these pass locally for me.
[ ] I have updated CHANGELOG.md following the template. I recognize that the developers may revisit CHANGELOG.md and the versioning, and create a Special Release including my changes.

This issue could possibly be addressed too in this PR 🤔


Wrapping a simple Python script that gets files as argument(s) and uses raw input

Hi!
I failed at multiple attempts to wrap a Python script into an App using Platypus :-(
My script is available at https://github.com/novoid/filetags - it gets a list of files as arguments and then prompts for tags that gets added to the file names (in interactive mode).
Not that hard to wrap I thought.
However, first I had to learn that raw_input() method of Python does not work when wrapped with Platypus:
http://stackoverflow.com/questions/17281607/python-to-mac-app-eoferror-caused-by-raw-input
http://stackoverflow.com/questions/4711589/python-raw-input-causing-eoferror-after-creating-app-with-py2app
Then I tried to wrap filetags.py within a simple wrapper shell script. The only way I could find to start a Terminal with the script was:
osascript -e 'tell app "Terminal" to do script "filetags --verbose ${@}"'

Well this did not work since the parameter ${@} does not get replaced by the shell arguments because I have to use single ticks for the oascript argument and double quotes for the argument within the oascript argument.
Maybe I did not think of any simple solution for this issue. For now, I have to give up and cry for help :-)
So, what do you suggest how I can wrap my script so that I am able to send file(s) to it and still being able to enter strings interactively.
Thanks!

Platypus apps are not an interactive Terminal. They merely capture script output and present it in a graphical user interface. You cannot use sudo or raw_input or anything that requires input from the user. This is clearly stated in the documentation. Closing.


[CP] Reland "Fixes ability to call nextFocus() on a node to focus its desc…

https://github.com/flutter/flutter/issues/137071
Pre-launch Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I signed the [CLA].
[X] I listed at least one issue that this PR fixes in the description above.
[X] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is [test-exempt].
[X] All existing and new tests are passing.

@chunhtai feel free to reopen if this should be CP'd into the release.

When I check out flutter-3.16-candidate.0, the source git hash (e8691444a2c7b968c977e120e185e6c3ff257fa2) is already incorporated into that branch. Are you sure we still need to cherry pick it there?


bug: buttons do not display properly in firefox

From @brandyscarney on December 30, 2015 17:2

Copied from original issue: driftyco/ionic2#831

Apparently firefox does not accept display: flex on buttons, so this actually affects all of our buttons: https://bugzilla.mozilla.org/show_bug.cgi?id=984869

Fixed in recent versions!


mp3tag installation stalls on "Type:"

installation of mp3tag stalls at "Type:"
upon pressing ENTER, installation continues after throwing an error:
C:\Users\user>scoop install mp3tag
Installing 'mp3tag' (2.86) [32bit]
mp3tagv286setup.exe (3.4 MB) [============================================================] 100%
Checking hash of mp3tagv286setup.exe... ok.
Extracting... done.
Running pre-install script...
Type:
New-Item : Cannot process argument because the value of argument "type" is not valid. Change the
value of the "type" argument and run the operation again.
At line:1 char:1
+ New-Item "$dir\mp3tag.cfg"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-Item], PSArgumentException
    + FullyQualifiedErrorId : Argument,Microsoft.PowerShell.Commands.NewItemCommand

Linking ~\scoop\apps\mp3tag\current => ~\scoop\apps\mp3tag\2.86
Creating shim for 'mp3tag'.
Creating shortcut for Mp3tag (mp3tag.exe)
Persisting data
Persisting export
Persisting mp3tag.cfg
The system cannot find the file specified.
Running post-install script...
'mp3tag' (2.86) was installed successfully!

Should be fixed now

thanks!!


Enable flagging all queries for an app as secure before configuration of protector queries

This will eliminate an attack vector caused by latency

This along with #37, #35, #34, and part of #33 will require some additional attributes.  This came to light during work on #33 when coding up the method to populate the security panel with existing plugin configuration data.  It turns out the following scenario is ambiguous:
YADA_PARAMS table:

TARGET
NAME
VALUE
RULE

APP qname
pl
Gatekeeper
1

Is the plugin security related?
If it's a TokenValidator implementation, there's no argument required.
How do we tell the difference between this and any old plugin?  We can't.

To clarify, any other security setting, e.g., execution policy, content policy, url pattern, can be distinguished by the presence of an arg string

TARGET
NAME
VALUE
RULE

APP qname
pl
Gatekeeper
1

APP qname
pr
execution.policy.columns=...
1

But even in this case, what if the user has created the query, but not actually locked it down (this very issue #39).
There is also a confounding condition, namely multiple plugins.  While multiple plugins might not be supported currently (untested) they certainly should be.  The arg strings will merge.  How to tell which plugin class is sec-relelated?
Enter YADA_PROP (YADA properties table):
CREATE TABLE IF NOT EXISTS YADA.YADA_PROP
(
  TARGET VARCHAR2(500),
  NAME VARCHAR(500),
  VALUE VARCHAR(4000)
);

The TARGET can be a YADA qname, app, system, some id string, etc.
NAME and VALUE are strings.
I believe it will also be necessary to include an ID column in the YADA_PARAM table to attach properties to each row.  The YADA_QUERY_CONF and YADA_QUERY_TABLE have defacto PKs already.
For now, these will load into the admin tool for marking and distinction purposes, specifically around security.  In the future, these could be used to short circuit plugin activation in the Service layer, hold system-wide configs (like JAVA_OPTS), ui prefs, etc.


Implementing Breadcrumb for Playlists Page

I realize I am leaving some tech debt around how I am managing state with ngrx. I plan on tackling it all with one fell swoop. I think how it is currently implemented is not the best. Might as well get everything working and refactor from there instead of acting like I know how state is going to be divided


go-http quickstart project fails to build due to upstream change in Jenkins Path

This was my original issue but I believe the change to be in this repo.
https://github.com/jenkins-x/jx/issues/6264
go-http project fails to build. Shows this error
process apparently never started in /home/jenkins/go/src/github.com/matthew/go-demo-6@tmp/durable-704406a9
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
Steps to reproduce the behavior
Create a new quickstart go-http project, see it fail on the build.
Expected behavior
jx create quickstart (for go-http, brand new project) should build.
Actual behavior
process apparently never started in /home/jenkins/go/src/github.com/matthew/go-demo-6@tmp/durable-704406a9
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
Gives that error.
Jx version
The output of jx version is:
➜  jx git:(master) jx version
NAME               VERSION
jx                 2.0.1040
jenkins x platform 2.0.1690
Kubernetes cluster v1.12.4
kubectl            v1.13.2
helm client        Client: v2.14.1+g5270352
git                2.17.0
Operating System   Mac OS X 10.15.1 build 19B88
Jenkins type
[x ] Classic Jenkins
Kubernetes cluster
Testing with Minikube, also w/ EKS
Operating system / Environment
Mac. see above.
Problem seems to be due to this Effort and PR:
https://issues.jenkins-ci.org/browse/JENKINS-58705
https://github.com/jenkinsci/kubernetes-plugin/pull/559/files
Need to update the path for generated Jenkinsfile via quickstart.

/close
Created issue under different repo
https://github.com/jenkins-x-buildpacks/jenkins-x-classic/issues/16


Hoist subdir chdir from setup scripts into GHA yaml

The scripts shouldn't be copy-pasting their own project name.

This commit was carved out of #333, authored by @nicolecheetham.  We should land the straightforward and uncontroversial boilerplate refactoring separately from the new-feature pieces, not only as a general best practice but because the refatoring is holding up related pull requests like #341.

This change is

:lgtm: both reviews.
It looks like macOS CI has been broken for a couple days.  I don't plan to block on it here.


Longest Common Subsequence (LCS) - GFG

Description
Given two sequences, find the length of longest subsequence present in both of them. Both the strings are of uppercase.
Example 1:
Input:
A = 6, B = 6
str1 = ABCDGH
str2 = AEDFHR
Output: 3
Explanation: LCS for input Sequences
“ABCDGH” and “AEDFHR” is “ADH” of
length 3.

Example 2:
Input:
A = 3, B = 2
str1 = ABC
str2 = AC
Output: 2
Explanation: LCS of "ABC" and "AC" is
"AC" of length 2.
I would like to add solution of this problem in C++.
DSA Problem
https://practice.geeksforgeeks.org/problems/longest-common-subsequence-1587115620/1

assign this to me sir

Hello @AbhineshJha @tusharv01
I am working on this issue, kindly work on any other issue

@tusharv01 you did not read the contribution.md, this issue was not created by you so why should it be assigned to you?


Request interceptor cause ui.bootstrap.tpls request modal base templates from server

I included bootstrap.tpls and have a request interceptor but when I call $modal.open all the modal base templates are requested from the server. If I remove the request interceptor the modal works well.

I'm wondering, is this potentially a problem better handled by Angular?
I am not sure whether this is really a UI Bootstrap problem. A simple workaround is to check $templateCache as shown here.
Otherwise, this is not really a problem with UI Bootstrap.


Invalid stage identifier with BasePathMapping depending on SAM ApiResource

Creating an apigateway.cloudformation.BasePathMappingResource that depends on a sam.cloudformation.ApiResource generates this error:
[ 6/11] Mon Oct 15 2018 04:40:45 GMT+0300 (EEST)  CREATE_FAILED
[AWS::ApiGateway::BasePathMapping] ApiBasePath3EEAADC4 Invalid stage identifier specified
(Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID:
55db9c2c-d01b-11e8-9ab5-c3df5de0ac4a)

I believe this problem is caused by this unfixed dependency issue in SAM: https://github.com/awslabs/serverless-application-model/issues/192
I have not yet found a workaround. Is there a way to manually specify a dependency to the stage resource that SAM generates?
Tested with AWS CDK 0.12 (TypeScript)

I have now converted my project to use apigateway.RestApi instead of sam.cloudformation.ApiResource. Thanks for the related assistance also in here @eladb : https://stackoverflow.com/questions/52752201/enabling-cors-for-aws-api-gateway-with-the-aws

@kennu glad to hear. Does the CORS solution work? Would love to add support for it as part of RestApi

Yes, CORS worked. It's nice that in AWS CDK I was able to add a little helper function like this:
function addCorsOptions(apiResource: apigateway.IRestApiResource) {
  const options = apiResource.addMethod('OPTIONS', new apigateway.MockIntegration({
    integrationResponses: [{
      statusCode: '200',
      responseParameters: {
        'method.response.header.Access-Control-Allow-Headers': "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token,X-Amz-User-Agent'",
        'method.response.header.Access-Control-Allow-Origin': "'*'",
        'method.response.header.Access-Control-Allow-Credentials': "'false'",
        'method.response.header.Access-Control-Allow-Methods': "'OPTIONS,GET,PUT,POST,DELETE'",
      },
    }],
    passthroughBehavior: apigateway.PassthroughBehavior.Never,
    requestTemplates: {
      "application/json": "{\"statusCode\": 200}"
    },
  }))
  const methodResource = options.findChild('Resource') as apigateway.cloudformation.MethodResource
  methodResource.propertyOverrides.methodResponses = [{
    statusCode: '200',
    responseModels: {
      'application/json': 'Empty'
    },
    responseParameters: {
      'method.response.header.Access-Control-Allow-Headers': true,
      'method.response.header.Access-Control-Allow-Methods': true,
      'method.response.header.Access-Control-Allow-Credentials': true,
      'method.response.header.Access-Control-Allow-Origin': true,
    },
  }]
}

Btw, just in case someone googles this issue and still gets the the error message: If you use apigateway.RestApi instead of SAM, you need to make sure you configure the stageName properly in deployOptions:
const api = new apigateway.RestApi(this, 'Api', {
  restApiName: props.stage + '-my-api',
  deployOptions: {
    stageName: props.stage,
  },
})

The stage name must match what you put in the base path resource:
new apigateway.cloudformation.BasePathMappingResource(this, 'BasePath', {
  basePath: 'my-basepath',
  domainName: 'mydomain.example.com',
  restApiId: api.restApiId,
  stage: props.stage,
})

By default AWS CDK generates a stage called 'prod' unless you override it. I've used a property to configure it.


Feature request of change protrait file manually to prevent this bug

Sometimes, like in this workflow: https://www.reddit.com/r/FoundryVTT/comments/s9fkw5/in_8_minutes_you_too_can_have_animated_portraits/
Note the answers to fix this issue are 'Turn off Tokenizer'
To fix this, provide an interface  to force tokenizer NOT to composite the portrait file but use it as-is.
Currently there is no option to do so.
Note that this functionality exists in the token: you can override the tokenizer's token by setting the image from the token settings in token prototype, which Tokenizer does not override, but no way to override the portrait to be a particular file and not composited.

Just shift click on the portrait to open the default filepicker and by-pass tokenizer.


[BugFix] Fix count distinct constant unknown error when use cte

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

count distint constant require no columns, this will result in cte comsumer output map is empty, which will generate a empty project node

[FE PR Coverage check]
:heart_eyes: pass : 10 / 10 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/RewriteMultiDistinctWithoutGroupByRule.java
10
10
100.00%

run starrocks_clang-format


Code block not working in new live preview mode.

Hi there, thank you for making this theme.
Code block does not seem to work in live preview mode.
The code block will not show up in live preview mode.
Kindly refer the screenshot below:

facing the same problem, it is because of the theme

really like this theme but still encountering the same issue with preview mode, is there any update for this?

Just wanted to add to this.
I did some digging into the Obsidianite.css file using the dev tools (ctrl+shift+i) and found where the visual problem was. Now, I'm NOT saying that this is the permanent fix (as I haven't fully read or tested if modifying this one part breaks anything else); but changing either the position, width, height, or disabling the background color seemed to fix it. I changed the position from absolute to relative. Now I can read my code while using the live preview feature.
I will warn again that this was a quick fix and not fully tested for other issues.

I will add to my previous note:
Obsidian seems to really like to hold onto old .css data. I'm not 100% certain how I did it, but hard resetting it seemed to get it to take the updated .css file.

Steps I did by accident:
Go to clear the cache data.
Realized that I misspelled 'Obsidian' for the folder I hold all my obsidian vaults.
Renamed it so that it is spelled correctly.
Relaunched Obsidian and boom, all of a sudden it is working.

I don't know how I blundered into getting it to work, but it is now. I'll keep updating if anything changes.

Just changing the Obsidianite.css in your (vault folder) > .obsidian > themes folder works, no need to do anything else.

Hey all, I will provide full support for live preview mode this weekend. If not latest next weekend! Thanks for all your supports!

This seems to still be an issue with the non-legacy editor. Switching to legacy mode also solves the issue.


DontTouchNotFoundException: Component marked dontTouch (DataCache.cacheStateName) not found!

Type of issue: bug report
Impact: no functional change
Other information
I can't include the code that causes this problem, and this isn't something that fails in simple examples. I'm not quite sure how to proceed.
[info]   firrtl.transforms.DontTouchAnnotation$DontTouchNotFoundException: Component marked dontTouch (DataCache.cacheStateName) not found!
[info] It was probably accidentally deleted. Please check that your custom transforms are notresponsible and then file an issue on Github.
[info]   at firrtl.transforms.DontTouchAnnotation$.errorNotFound(OptimizationAnnotations.scala:27)
[info]   at firrtl.transforms.DeadCodeElimination.$anonfun$run$6(DeadCodeElimination.scala:293)
[info]   at firrtl.transforms.DeadCodeElimination.$anonfun$run$6$adapted(DeadCodeElimination.scala:287)
[info]   at scala.collection.immutable.List.foreach(List.scala:392)
[info]   at firrtl.transforms.DeadCodeElimination.run(DeadCodeElimination.scala:287)
[info]   at firrtl.transforms.DeadCodeElimination.execute(DeadCodeElimination.scala:335)
[info]   at firrtl.Transform.$anonfun$runTransform$2(Compiler.scala:257)
[info]   at firrtl.Utils$.time(Utils.scala:183)
[info]   at firrtl.Transform.runTransform(Compiler.scala:257)
[info]   at firrtl.SeqTransformBased.$anonfun$runTransforms$1(Compiler.scala:309)
[info]   ...
If the current behavior is a bug, please provide the steps to reproduce the problem:
What is the current behavior?
Exception.
What is the expected behavior?
No exception.
Please tell us about your environment:
Ubuntu 18
"chisel3" -> "3.1.5",
"chisel-iotesters" -> "1.2.7"
What is the use case for changing the behavior?

This is indicating that by the time DeadCodeElimination ran, there exists a DontTouchAnnotation pointing at a component (something in the circuit) that no longer existed.
When transforms run, they generate a rename map which will update annotations based on things that were renamed or deleted. However, if you have a custom transform that manipulates the circuit but doesn't report a rename map, you can have this issue.
First, check the name of the component that got deleted. Then, try to reason about why this was deleted. Did you add a custom transform? Are you manually writing the annotation and have the name wrong? If it's not related to a custom transform, then it may indicate a FIRRTL bug. If that's the case, trying to narrow it down to a minimum working example would help.

I dont have a custom transform. I will give it a go to narrow down to an
example that I can make public.
søn. 23. jun. 2019, 20.02 skrev Schuyler Eldridge<EMAIL_ADDRESS>
:

This is indicating that by the time DeadCodeElimination ran, there exists
a DontTouchAnnotation pointing at a component (something in the circuit)
that no longer existed.
When transforms run, they generate a rename map which will update
annotations based on things that were renamed or deleted. However, if you
have a custom transform that manipulates the circuit but doesn't report a
rename map, you can have this issue.
First, check the name of the component that got deleted. Then, try to
reason about why this was deleted. Did you add a custom transform? Are you
manually writing the annotation and have the name wrong? If it's not
related to a custom transform, then it may indicate a FIRRTL bug. If that's
the case, trying to narrow it down to a minimum working example would help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freechipsproject/chisel3/issues/1112?email_source=notifications&email_token=AAVLJZX2XIJQGFXSB66VUYTP363BNA5CNFSM4H2ZL3Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLDZ2Y#issuecomment-504773867,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVLJZWWWLNC3VQO7EWPDK3P363BNANCNFSM4H2ZL3QQ
.

It turns out that the problem was that I was reusing TesterOptionsManager objects. When I do, I'll share some state between tests(in the test_run_dir?). This seems to have caused the error, though I have no idea why.
When I create a fresh TesterOptionsManager object for each test, it works.

Good catch. There is mutable state in the TesterOptionsManager and that is likely the problem. The work @seldridge has done with Stage/Phases and related PR's covers this and other issues with the current Driver framework.

Is the mutable state in TesterOptionsManager by design?
It seems like a trip-wire from a users point of view. I would not have expected TesterOptionsManager objects to be changed by executing the tests, as I got the impression that it's an argument to the tests, not something that the tests should operate on.
To me how I launch tests is boilerplate code and I'm happy to switch to a more modern version of it.
Is TesterOptionsManager now obsolete?
Is there an example of the new way to launch tests and avoid the old "Driver" method?


Update stable version in repo from 0.0.0 to 2.0.1

Think about adding version 2.0.1 to stable repository.
Version: stable=0.0.0 (0 days old) => latest=2.0.1 (30 days old)
Installs: stable=0 (0%), latest=26 (14.69%), total=177
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 2.0.1 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

must be fixed: https://github.com/iobroker-community-adapters/ioBroker.vofo-speedtest/issues/208


Review the current parameters for preprocessing

The parameters related to each strategy is here.
Remove straw man strategies might be a good idea.

@pbellec suggests to remove straw man strategies and use the terminology we used in nilearn:
https://github.com/nilearn/nilearn/blob/22a4fa55428acc7de32da99d2335e5107865248b/nilearn/interfaces/fmriprep/load_confounds_strategy.py#L16-L52


[SPARK-14042][CORE] Add custom coalescer support [WIP]

What changes were proposed in this pull request?
This is a work-in-progress PR (to gather feedback) about a new feature that adds support for specifying a custom coalescer to the coalesce() method. Currently I have only added this feature to the RDD interface, and once we sort out the details we can proceed with adding this feature to the other APIs (Dataset etc.)
How was this patch tested?
Added a unit test for this functionality.
/cc @rxin (per our discussion on the mailing list)

Can one of the admins verify this patch?

@rxin any comments?

@nezihyigitbasi, do you plan to add something similar for DF/DS API?

@hbhanawat once we figure out the details I think it makes sense to do that.

@rxin any plans to review this?

The API change looks alright. I'd separate the dataset changes from this one. Are there other things you want to do before this is not WIP?

If the API changes look OK to you, then I don't have anything else before this is not WIP. I only need to resolve conflicts with the master.

@rxin rebased & addressed comments.

Also can you tag all these apis as DeveloperApi? Thanks.'

@rxin thanks for the comments. Updated.

LGTM other than that couple minor feedback.

@rxin thanks, comments addressed. Renamed that file to use lower-case too.

Thanks - let's wait for Jenkins. Can you update the title / description of the pull request?

Test build #2818 has started for PR 11865 at commit 9d91f77.

Test build #2818 has finished for PR 11865 at commit 9d91f77.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait PartitionCoalescer
class PartitionGroup(val prefLoc: Option[String] = None)

Mima tests failing, I guess we can exclude them all. What do you think?
[info] spark-core: found 3 potential binary incompatibilities while checking against org.apache.spark:spark-core_2.11:1.6.0  (filtered 1299)
[error]  * method coalesce(Int,Boolean,scala.math.Ordering)org.apache.spark.rdd.RDD in class org.apache.spark.rdd.RDD does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("org.apache.spark.rdd.RDD.coalesce")
[error]  * class org.apache.spark.rdd.PartitionCoalescer#LocationIterator does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[MissingClassProblem]("org.apache.spark.rdd.PartitionCoalescer$LocationIterator")
[error]  * declaration of class org.apache.spark.rdd.PartitionCoalescer is interface org.apache.spark.rdd.PartitionCoalescer in current version; changing class to interface breaks client code
[error]    filter with: ProblemFilters.exclude[IncompatibleTemplateDefProblem]("org.apache.spark.rdd.PartitionCoalescer")

Yup go for it.

@rxin somehow jenkins didn't start the tests after my last push, can you please kick it off?

Test build #2829 has started for PR 11865 at commit 5a12586.

Test build #2829 has finished for PR 11865 at commit 5a12586.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait PartitionCoalescer
class PartitionGroup(val prefLoc: Option[String] = None)

@rxin tests look OK, do you have any other comments?

Merging in master. Thanks.


DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

I am customizing auth components in @nebular. I used the source code from 'https://github.com/akveo/nebular/tree/master/src/framework/auth/components' this location and made routing according to that. The project shows no errors but does not show the home page in browser and just show the loading page. When I build the project it gives following result with deprecationWarning message in cmd.

How can I resolve this?

@rmdss,
I am almost sure that there is something else going on, but why does it say Port 3000 is already in use?
Also have a look at your develepmont console in your browser and tell us if you get any error messages.


Attachment upload -- improve attachment replacement

Describe the bug
Currently, when I want to replace a given attachment, I have to drop exactly to the center (where dropzone lives). If I drop outside of it, the browser will load the attachment - quite annoying.
To Reproduce
Steps to reproduce the behavior:

Drop a file to a channel
Drop a new file to replace the existing one
Drop a new file outside of dropzone to replace the existing one

Expected behavior
It shouldn't matter where I drop, as long as it is inside the darkened area.
Screenshots

In the above screenshot, files can only be dropped in the centered lightbox.
Desktop (please complete the following information):
any
Smartphone (please complete the following information):
doesn't apply
Additional context
/

Just tested it and it seems to be working fine.


2.0.4 dev

Release notes:

Update to Apple Store guideline
Fix Logo Aspect Ratio
Fix login bug

@thrasher- or @losh11
Unless there are any issues can either of you merge and make a build?

@losh11 rebased and merged....closing


Remove utils.IsRunningOnKindInfraIPv6

What this PR does / why we need it:
Kind ipv6 cluster is not supported any more. utils.IsRunningOnKindInfraIPv6 and all its usages should be removed.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest

/retest

/approve


Merge views and animate second participant

Merge 'PK' and 'Single' mode views
Animate second participant video view

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM


[6.x] Adds lcfirst helper in Str class

Adds a lcfirst helper in Str class that mirrors the existing ucfirst.
Adds a testLcfirst test for the helper.
The helper makes a string first character lowercase.

Won't this just have the effect of making the code twice as slow?

I guess it would be the same level of "slowness" as for Str::ucfirst()

Feel free to macro this into your own project if you require it.

Roger.
One small request if I may, please help me understand why it is not inconsistent to haveStr::ucfirst() without having Str::lcfirst(), because I'm clearly missing a point here.
Thank you in advance for the clarification.


[TACHYON-1641]Add the Chinese version of doc page 'Integrating Under Storage Systems'

Add the Chinese version of documentation page 'Integrating Under Storage Systems'. See https://tachyon.atlassian.net/browse/TACHYON-1641

Can one of the admins verify this patch?

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8504/
Test PASSed.

Thanks @summerDG . Please add the screencast of the page layout:)

Click http://www.tachyon-project.org/documentation/master/en/Integrating-Under-Storage-Systems.html and choose Chinese version.

LGTM. Thanks for the translation.


Fix linking GSE114727_BreastTumorMicroenvironment

Context
see slack message from Hannes
In brief GSE114727_BreastTumorMicroenvironment is triggering test integration failure for Azul
Reason:
the analysis files are linked to sequence files and, also due to the size of the project, Azul takes a long time to reconstruct the graph
project link
Task

[ ] change linking from sequence files to cell suspension

Deadline
as soon as possible because the project will be removed from the portal otherwise

I've prepared a script to get the files' uuids and their input cell suspensions' uuids
Using the uuids I can add the cell suspsions to the matrix creation process
But
I can't figure out how to remove the fastq files from the process via the api - they are 406 so I can't do it manually

to remove a file from a process you have to use the put action
input_to_process_link = "https://api.ingest.archive.data.humancellatlas.org/files/<file_id>/inputToProcesses"
response = api.put(input_to_process_link)
response.raise_for_status()

export failed because of race conditions - both exporter threads were working on the same file and got stuck waiting for the other thread to stop writing to file
index:27/79 - Verifying upload of blob prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json. Waiting for 0.4 seconds...\n","stream":"stderr","time":"2024-08-02T10:16:45.327081114Z"}

{"log":"2024-08-02 10:16:45,215 - TerraExperimentExporter - INFO - submission_uuid:46321950-6b54-4e05-a7c5-d7cef1ad12a9 - export_job_id:66ab64b9f7e68c76e8fe3806 - project_uuid:7c75f07c-608d-4c4a-a1b7-b13d11c0ad31 - process_uuid:1c47090a-a1f8-4293-a257-ad30fb395ce4 - index:26/79 - Verifying upload of blob prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json. Waiting for 0.4 seconds...\n","stream":"stderr","time":"2024-08-02T10:16:45.216093149Z"}

{"log":"2024-08-02 10:16:45,089 - TerraExperimentExporter - INFO - submission_uuid:46321950-6b54-4e05-a7c5-d7cef1ad12a9 - export_job_id:66ab64b9f7e68c76e8fe3806 - project_uuid:7c75f07c-608d-4c4a-a1b7-b13d11c0ad31 - process_uuid:45d8ca4a-ca1d-4d7c-87cd-4cf6413b573b - index:27/79 - Verifying upload of blob prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json. Waiting for 0.2 seconds...\n","stream":"stderr","time":"2024-08-02T10:16:45.089850849Z"}

{"log":"2024-08-02 10:16:44,985 - TerraExperimentExporter - INFO - submission_uuid:46321950-6b54-4e05-a7c5-d7cef1ad12a9 - export_job_id:66ab64b9f7e68c76e8fe3806 - project_uuid:7c75f07c-608d-4c4a-a1b7-b13d11c0ad31 - process_uuid:1c47090a-a1f8-4293-a257-ad30fb395ce4 - index:26/79 - Verifying upload of blob prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json. Waiting for 0.2 seconds...\n","stream":"stderr","time":"2024-08-02T10:16:44.985814481Z"}

{"log":"2024-08-02 10:16:44,825 - TerraExperimentExporter - INFO - submission_uuid:46321950-6b54-4e05-a7c5-d7cef1ad12a9 - export_job_id:66ab64b9f7e68c76e8fe3806 - project_uuid:7c75f07c-608d-4c4a-a1b7-b13d11c0ad31 - process_uuid:1c47090a-a1f8-4293-a257-ad30fb395ce4 - index:26/79 - Writing file: prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json\n","stream":"stderr","time":"2024-08-02T10:16:44.825287534Z"}

{"log":"2024-08-02 10:16:44,937 - TerraExperimentExporter - INFO - submission_uuid:46321950-6b54-4e05-a7c5-d7cef1ad12a9 - export_job_id:66ab64b9f7e68c76e8fe3806 - project_uuid:7c75f07c-608d-4c4a-a1b7-b13d11c0ad31 - process_uuid:45d8ca4a-ca1d-4d7c-87cd-4cf6413b573b - index:27/79 - Writing file: prod/7c75f07c-608d-4c4a-a1b7-b13d11c0ad31/staging_area.json\n","stream":"stderr","time":"2024-08-02T10:16:44.93793913Z"}

exported with a script
to do

[ ] import form
[ ] add info about script
[ ] check staging area


[Server] Add support to get MeshSync version

Description
This PR retrieves the version from MeshSync which is set as an env variable .
Related https://github.com/meshery/meshsync/pull/128.
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #5536 (df1a4b1) into master (2a22fe8) will decrease coverage by 4.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5536      +/-   ##
==========================================
- Coverage   17.47%   13.12%   -4.35%
==========================================
  Files         107      107
  Lines        9993     9993
==========================================
- Hits         1746     1312     -434
- Misses       7821     8401     +580
+ Partials      426      280     -146

Flag
Coverage Δ

gointegrationtests
?

unittests
13.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-58.95%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.88% <0.00%> (-55.19%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
1.14% <0.00%> (-55.18%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
1.92% <0.00%> (-48.08%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
2.00% <0.00%> (-46.67%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.26% <0.00%> (-36.96%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.03% <0.00%> (-23.03%)
:arrow_down:

mesheryctl/internal/cli/root/system/dashboard.go
1.70% <0.00%> (-9.41%)
:arrow_down:

mesheryctl/pkg/utils/healthcheck.go
8.82% <0.00%> (-4.42%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7d66814...df1a4b1. Read the comment docs.

Pod.yml
apiVersion: v1
kind: Pod
metadata:
  name: test
spec:
  containers:
  - name: test
    image: test:v0.0.1
    env:
    - name: ENV2 <--------------
      value: "test2"

Dockerfile
FROM nginx:latest
ENV ENV1="test1"  <---------------
CMD ["nginx", "-g", "daemon off;"]

kubectl describe pod test
Containers:
  test:
    Container ID:   docker://856a77bef30d0c614a4e942ff994854bfbbce8a7ea9e1d6e79a2e30ed012580e
    Image:          test:v0.0.1
    Image ID:       docker://sha256:55281ef707f82df3772c25f45ff304b2e3f54f7374d748f1c2ed2e92aecae7bb
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Fri, 27 May 2022 12:47:04 +0530
    Ready:          True
    Restart Count:  0
    Environment:
      ENV2:  test2 <-----------
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9g8vf (ro)

@leecalcote

@leecalcote I Just realised, that since we are using distroless image for MeshSync we don't have access to the shell. This will fail unless we use alpine or similar as base image in MeshSync.


No module named 'pydantic'

A problem with:
https://github.com/omirete/telepybot/blob/master/examples/send_message.py

I just cant install any telegrambot class... Can you please help with?

Sorry, i had no installed  "pydantic" class. So i install it and all works well!

Hi @Depech101, thank you for posting this issue!
I discovered that Pydantic was not specified as a dependency in the pyproject.toml file. Because of this, it was not being automatically installed when installing the telepybot library.
I have fixed it now with this commit.
Thanks again!


Feature: Adding Ollama support

Feature: Adding Ollama support
Screencast from 2024-10-14 01:07:35 PM.webm
NOTE: I don't have an OpenAI account so I'm not able to verify the changes here didn't break OpenAI, someone with an OpenAI account should verify this still works as expected.
Description

Adding support for Ollama by adding additional env variables
Updated README to reflect changes
Added sample envs for Ollama and OpenAI

QA

Copy .env-ollama.example to .env and update the OLLAMA_BASE_URL to point to your Ollama instance, making sure you keep the /v1 at the end and also set the model to a vision model you have pulled.
Run npm run dev, go to http://localhost:3000 and draw something
Click on Make Real and verify you get a result from Ollama

CC @SawyerHood

CC @shtepcell @0x-sen @kawana77b


net/http/cgi: 'GET Parameters' are not available on Tomcat

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

$ go version
go version go1.19.1 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
Compile on Debian GNU/Linux 11 (bullseye)  with Intel CPU
Run on Raspbian GNU/Linux 10 (buster) with Armv7 (Raspberry Pi 3 Model B)
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3827448816=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I created a CGI program which parse GET Parameters with net/http#Request.ParseForm.
On Apache, that works.
On Tomcat, it doesn't.
The reason is a environment variable "REQUEST_URI" doesn't include parameters on Tomcat, I guess.
Environment variables:
[Apache]
REQUEST_URI="/cgi-bin/testcgi?id=1"
QUERY_STRING="id=1"

[Tomcat]
REQUEST_URI="/cgi-bin/testcgi"
QUERY_STRING="id=1"

I checked the source code of this problem.  (net/http/cgi/child.go)
QUERY_STRING is used only when REQUEST_URI is blank. (Am I right?)

CC @neild


Netpoll prints connection error when wrk stress test ends

possible to show us how to test with wrk or apache bench? coz cant test against fasthttp etc.
got this as response
2022/05/31 14:13:56 readv(fd=59) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=58) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=57) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=56) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=55) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=54) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=53) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=51) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=49) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=48) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=47) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=46) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=45) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=44) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=43) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=41) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=40) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=39) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=38) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=36) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=34) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=33) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=32) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=31) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=30) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=29) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=28) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=27) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=26) failed: connection reset by peer
2022/05/31 14:13:56 readv(fd=25) failed: connection reset by peer

ab -n 100 -c 100 http://<IP_ADDRESS>:8888/
This is ApacheBench, Version 2.3 <$Revision: 1843412 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking <IP_ADDRESS> (be patient)...apr_pollset_poll: The timeout specified has expired (70007)

try with wrk -t 1 -d 10 -c 100 http://<IP_ADDRESS>:8888/
error as mentioned
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package main

import (
        "context"
        "fmt"

        "github.com/cloudwego/hertz/pkg/app"
        "github.com/cloudwego/hertz/pkg/app/server"
        "github.com/cloudwego/hertz/pkg/common/utils"
        "github.com/cloudwego/hertz/pkg/protocol/consts"
)

type Test struct {
        A string
        B string
}

func main() {
        h := server.Default()
        h.GET("/", func(c context.Context, ctx *app.RequestContext) {
                fmt.Fprintf(ctx, "Hello, World!\n")
                //ctx.Redirect(consts.StatusMovedPermanently, []byte("http://www.google.com/"))
        })
        //h.StaticFS("/", &app.FS{Root: "./", GenerateIndexPages: true})

        h.GET("/ping", func(c context.Context, ctx *app.RequestContext) {
                ctx.JSON(consts.StatusOK, utils.H{"ping": "pong"})
        })

        h.GET("/json", func(c context.Context, ctx *app.RequestContext) {
                ctx.JSON(consts.StatusOK, &Test{
                        A: "aaa",
                        B: "bbb",
                })
        })

        h.GET("/redirect", func(c context.Context, ctx *app.RequestContext) {
                ctx.Redirect(consts.StatusMovedPermanently, []byte("http://www.google.com/"))
        })

        v1 := h.Group("/v1")
        {
                v1.GET("/hello/:name", func(c context.Context, ctx *app.RequestContext) {
                        fmt.Fprintf(ctx, "Hi %s, this is the response from Hertz.\n", ctx.Param("name"))
                })
        }

        h.Spin()
}

Got it! Thanks for your report. We will check on this.

I will remove the bug label here, coz the root cause behind this error is that wrk close connection rudely by just reset the connection. More info you could find here: https://github.com/wg/wrk/issues/360.
At this moment netpoll (the default network impl under hertz)  will print this connection reset error directly. We will take a deep look at it and discuss a final solution for this kind of situation. For now you can just ignore the error here.
Thanks again for the report!

cc @Hchenn @joway

it's not professional to say to ignore this. apache bench and wrk cannot show any results. in any case, this http stress testing doesnt work. any work arounds to stress test hertz now? doesnt make sense at all as i have tested so many that works.

Sorry, I forgot about the ab.
The reason that ab -n 100 -c 100 http://<IP_ADDRESS>:8888/ didn't return is that hertz does not close the connection after processing a non-keepalived request. I'll fix it, and for now you may add the -k flag to work around with it.
If it's still not working, pls let me know.

The reason that ab cannot work is server doesn't close the short connection. We looked up a lot of RFC doc and there isn't a specific definition. In TCP, the party that closes the connection actively needs to wait 2RTT time. So if there are too many connections hang up, the server won't accept more connections. We consider that let client wait 2RTT seems more reasonable. So we won't support ab short connection test. Please use other bench tool.

Now you can use ab to benchmark Hertz with short connection.


question: custom actions

Is there an easy way to define custom actions for a Model / Module ?
I have a model, which is having a JSON field (which I don't want to define as a related submodel, as it can have various properties depending on different options of the model itself), that's why I also store it as JSON inside my DB (which is a traditional relational DB)
How can I safely update one (or more) properties from this JSON field, without erasing the others ?
The options I think of:

have a submodel defined, but I've already mentioned I'd like to avoid this for simplicity
use getters to obtain current value, and update entire JSON with the modified values
build a custom action (on the Model or Module) to update just the specified values from the JSON leaving the rest alone. How would I do this ?

Thanks !

With Vuex ORM 0.22.0, you can pass a closure to the data property of the update action to have full control in such case!
store.dispatch('entities/users/update', {
  where: 1,
  data (user) {
    // Let's say `settings` is the JSON field.
    user.settings.role = 'user'
  }
})

Would this make sense for you?

Wow, that's working as expected !
I was starting to implement custom actions and mutations inside the Module (not Model), but this solution it's much simple ;)
Thx man ;)

Glad I could help! Feel free to open another issue if you have any trouble 😃

So I ended up with this multipurpose update solution, valid for entire form / model, which handles dynamically both cases: direct model values or JSON attributes, maybe some others will embrace this solution
model.js - name it's a JSON object, but not a related model
import { Model } from '@vuex-orm/core'

export default class MyModel extends Model {
  static entitiy = 'mymodule'

  static fields () {
    return {
      id: this.attr(1),
      name: this.attr({
        first: 'John',
        last: 'Doe'
      }),
      age: this.attr(18)
    }
  }
}

component.vue
<template>
  <form>
    <input type="text" name="name.first" :value="user.name.first" @update="update" />
    <input type="text" name="name.last" :value="user.name.last" @update="update" />
    <input type="number" name="age" :value="user.age" @update="update" />
  </form>
</template>

<script>
// I am using `object-path` for simplicity of the update
import objectPath from 'object-path'

export default {
  computed: {
    user () {
      return this.$store.getters['entities/mymodule/find'](1)
    }
  },

  methods: {
    update (event) {
      this.$store.dispatch('entities/mymodule/update', {
        where: this.user.id,
        data (user) {
          // this would update `age` or `name.first` and `name.last` based on field `name`
          objectPath.set(user, event.target.name, event.target.value)
        }
      })
    }
  }
}
</script>


Allow passing arguments to rubocop

Thanks for the PR and ping. Didn't notice the PR until now.
This makes sense to me. Only thing missing is an entry in the Configuration section of the README.

Thanks!


Update Sidekick to fit the latest FVM version

Could be nice to update Sidekick to fit the latest FVM version, including new FVM settings and folders structure.

up