Updating the pest file as ident in protobuf can start with an underscore

Hope this can be added to prevent me from having to run a patched version.

bump on this..


Set LC_NUMERIC to "C" on init

This is to work arround the decimal parsing implementation that expects
comma as decimal seperator for de_DE (and maybe other langs to).
Currently $\LaTeX$ looks like this on a German system:

This is more or less straight up taken from our NoteKit implementation, where there was a similar bug, that resulted in broken JSON parsing by jsoncpp. Because the libc LANG isn't scoped, this bug never occurred in NoteKit  since we've already set LC_NUMERIC to "C".

TheLC_NUMERIC will affect the result of functions strtod, strtol, and so on, the first time I've heard about that, learned a lot 🎆 .


Different equation compared to paper?

Hi, @BichenWuUCB. I'm currently playing with your squeezeDet code, but I found some suspicious part in your code, so it would be grateful if you check if this is wrong or not.
In read_batch function in /dataset/imdb.py, conversion code of ground truth bounding box into delta is
delta[0] = (box_cx - mc.ANCHOR_BOX[aidx][0])/box_w
delta[1] = (box_cy - mc.ANCHOR_BOX[aidx][1])/box_h
delta[2] = np.log(box_w/mc.ANCHOR_BOX[aidx][2])
delta[3] = np.log(box_h/mc.ANCHOR_BOX[aidx][3])

Isn't it correct to divide delta[0] and delta[1] with mc.ANCHOR_BOX[aidx][2], mc.ANCHOR_BOX[aidx][3] respectively? Equation (3) in the paper divides it with anchor box width/height, and I personally think that dividing by fixed value (anchor box width/height) is more stable normalization.
Thanks!

@shuuki4 thanks for your question. I guess your question is already answered in #4 . Equation (3) in the paper should be fixed, the code implementation is correct. Sorry for the confusion.

If the code implementation is correct, I think this part of the code (Line 170 of nn_skeleton.py) should be changed:
        box_center_x = tf.identity(
            anchor_x + delta_x * anchor_w, name='bbox_cx')
        box_center_y = tf.identity(
            anchor_y + delta_y * anchor_h, name='bbox_cy')
        box_width = tf.identity(
            anchor_w * util.safe_exp(delta_w, mc.EXP_THRESH),
            name='bbox_width')
        box_height = tf.identity(
            anchor_h * util.safe_exp(delta_h, mc.EXP_THRESH),
            name='bbox_height')

Since delta is divided by ground truth bboxes' width and height, gt boxes' width and height should be used when stretching box_center_x and box_center_y. However, this code uses anchor_w and anchor_h to rescale the box center. Therefore, if the code implementation is correct, this code should also be changed to use ground truth box width/height. Even if this information does not directly affect the learning process, it affects final prediction for raw bounding box coordinates and also affect visualizations, so I think this code should be fixed.
One more concern is that eval.py uses this code (model.det_boxes) for final bounding box prediction. Since there is no ground truth for test data split, it is impossible to rescale delta into real coordinates.  Therefore, I think it is necessary to normalize delta with anchor box width/heights.


use const ref in boost::fusion::vector, fix #511

With this, pinocchio & py-pinocchio are building correctly with robotpkg in fedora 28, which uses boost 1.66.

@nim65s Any news for this PR?

no, sorry, I am in parental leave until 19/11 :)

Still, these are not the commit that should be in this PR… I will try to find it.

Sorry for the noise, I'll open another PR as soon as my tests will be done

Ok. No problem.


DllNotFoundException while I build linux android version

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04, WSL2): Ubuntu 20.04.2 LTS
Target (e.g. desktop cpu, android arm64): android
Bazel version:  3.7.2
Python version:  3.9.4
GCC/G++ version:  9.3.0
Unity version:   2019.4.26
Android NDK version (if building for Android): 19.2.5345600
Xcode version (if building for iOS):

Describe the problem
Hey I think I already succesffuly built the android version on linux using docker.
while I can't run the android version on unity, It shows DllNotFound.
Steps to reproduce the issue
Provide the exact sequence of commands / steps that you executed before running into the problem.

And I already set the load on startup for mediapipe_android, and in side the same place I can see the aar  file.

I'm curious that have I set the wrong opencv path here?

Since my openCV file is inside my  /usr/lib/x86_64-linux-gnu

Full logs
Additional context
Add any other context about the problem here.

You need to build native libraries for Desktop to run scenes on UnityEditor.
So please run the below command and restart UnityEditor.
python build.py build --desktop gpu -vv

You need to build native libraries for Desktop to run scenes on UnityEditor.
So please run the below command and restart UnityEditor.
python build.py build --desktop gpu -vv

Then could you please tell me how can I run Unity Android version, as you can see I switched to Android platform in unity, but failed to get mediapipe.

Have you run the below command successfully?

python build.py build --desktop gpu -vv

No , it shows the following error:
ERROR: /home/st/.cache/bazel/_bazel_st/3695023b97f4d1792ddeaeae288fe1c2/external/com_google_mediapipe/mediapipe/calculators/tensor/BUILD:625:11: C++ compilation of rule '@com_google_mediapipe//mediapipe/calculators/tensor:image_to_tensor_converter_gl_buffer' failed (Exit 1): gcc failed: error executing command
  (cd /home/st/.cache/bazel/_bazel_st/3695023b97f4d1792ddeaeae288fe1c2/sandbox/linux-sandbox/1574/execroot/mediapipe_api && \
  exec env - \
    PATH=/home/st/anaconda3/envs/py3.9/bin:/home/st/anaconda3/condabin:/home/st/.local/bin:/home/st/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/root/anaconda3/bin:/home/st/bin \
    PWD=/proc/self/cwd \
  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.d '-frandom-seed=bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.o' -fPIC -DMEDIAPIPE_PROFILER_AVAILABLE -iquote external/com_google_mediapipe -iquote bazel-out/k8-opt/bin/external/com_google_mediapipe -iquote external/com_google_protobuf -iquote bazel-out/k8-opt/bin/external/com_google_protobuf -iquote external/zlib -iquote bazel-out/k8-opt/bin/external/zlib -iquote external/com_github_glog_glog -iquote bazel-out/k8-opt/bin/external/com_github_glog_glog -iquote external/com_github_gflags_gflags -iquote bazel-out/k8-opt/bin/external/com_github_gflags_gflags -iquote external/com_google_absl -iquote bazel-out/k8-opt/bin/external/com_google_absl -iquote external/org_tensorflow -iquote bazel-out/k8-opt/bin/external/org_tensorflow -iquote external/FP16 -iquote bazel-out/k8-opt/bin/external/FP16 -Ibazel-out/k8-opt/bin/external/com_github_glog_glog/_virtual_includes/default_glog_headers -Ibazel-out/k8-opt/bin/external/com_github_gflags_gflags/_virtual_includes/gflags -Ibazel-out/k8-opt/bin/external/FP16/_virtual_includes/FP16 -isystem external/com_google_protobuf/src -isystem bazel-out/k8-opt/bin/external/com_google_protobuf/src -isystem external/zlib -isystem bazel-out/k8-opt/bin/external/zlib -isystem external/FP16/include -isystem bazel-out/k8-opt/bin/external/FP16/include -w -DMESA_EGL_NO_X11_HEADERS -DEGL_NO_X11 '-std=c++17' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/com_google_mediapipe/mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc -o bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.o)
Execution platform: @local_execution_config_platform//:platform

Use --sandbox_debug to see verbose messages from the sandbox gcc failed: error executing command
  (cd /home/st/.cache/bazel/_bazel_st/3695023b97f4d1792ddeaeae288fe1c2/sandbox/linux-sandbox/1574/execroot/mediapipe_api && \
  exec env - \
    PATH=/home/st/anaconda3/envs/py3.9/bin:/home/st/anaconda3/condabin:/home/st/.local/bin:/home/st/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/root/anaconda3/bin:/home/st/bin \
    PWD=/proc/self/cwd \
  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.d '-frandom-seed=bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.o' -fPIC -DMEDIAPIPE_PROFILER_AVAILABLE -iquote external/com_google_mediapipe -iquote bazel-out/k8-opt/bin/external/com_google_mediapipe -iquote external/com_google_protobuf -iquote bazel-out/k8-opt/bin/external/com_google_protobuf -iquote external/zlib -iquote bazel-out/k8-opt/bin/external/zlib -iquote external/com_github_glog_glog -iquote bazel-out/k8-opt/bin/external/com_github_glog_glog -iquote external/com_github_gflags_gflags -iquote bazel-out/k8-opt/bin/external/com_github_gflags_gflags -iquote external/com_google_absl -iquote bazel-out/k8-opt/bin/external/com_google_absl -iquote external/org_tensorflow -iquote bazel-out/k8-opt/bin/external/org_tensorflow -iquote external/FP16 -iquote bazel-out/k8-opt/bin/external/FP16 -Ibazel-out/k8-opt/bin/external/com_github_glog_glog/_virtual_includes/default_glog_headers -Ibazel-out/k8-opt/bin/external/com_github_gflags_gflags/_virtual_includes/gflags -Ibazel-out/k8-opt/bin/external/FP16/_virtual_includes/FP16 -isystem external/com_google_protobuf/src -isystem bazel-out/k8-opt/bin/external/com_google_protobuf/src -isystem external/zlib -isystem bazel-out/k8-opt/bin/external/zlib -isystem external/FP16/include -isystem bazel-out/k8-opt/bin/external/FP16/include -w -DMESA_EGL_NO_X11_HEADERS -DEGL_NO_X11 '-std=c++17' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/com_google_mediapipe/mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc -o bazel-out/k8-opt/bin/external/com_google_mediapipe/mediapipe/calculators/tensor/_objs/image_to_tensor_converter_gl_buffer/image_to_tensor_converter_gl_buffer.pic.o)
Execution platform: @local_execution_config_platform//:platform

Use --sandbox_debug to see verbose messages from the sandbox
external/com_google_mediapipe/mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc: In member function 'virtual absl::lts_2020_09_23::StatusOr<mediapipe::Tensor> mediapipe::{anonymous}::GlProcessor::Convert(const mediapipe::Image&, const mediapipe::RotatedRect&, const mediapipe::Size&, float, float)':
external/com_google_mediapipe/mediapipe/calculators/tensor/image_to_tensor_converter_gl_buffer.cc:315:12: error: could not convert 'tensor' from 'mediapipe::Tensor' to 'absl::lts_2020_09_23::StatusOr<mediapipe::Tensor>'
     return tensor;
            ^~~~~~
Target //mediapipe_api:mediapipe_desktop failed to build
INFO: Elapsed time: 43.129s, Critical Path: 24.75s
INFO: 541 processes: 136 internal, 405 linux-sandbox.

Well, please fill in required fields -> https://github.com/homuler/MediaPipeUnityPlugin/issues/166#issue-892476363
I guess your GCC version is less than 8 (Ubuntu 18.04?).

Well, please fill in required fields -> #166 (comment)
I guess your GCC version is less than 8 (Ubuntu 18.04?).

Sorry for the inconvinience, I already modify it, yes my gcc version is less than 8

I built it successfully, but still can't find the dll.
This is my opencv_linux.BUILD, I can find the required file at /lib/x86_64-linux-gnu/

and This is my linux_opencv config, I suspect whether it's right or not.

And here is what in the unity

can you please help me ? thanks

I built it successfully, but still can't find the dll.
This is my opencv_linux.BUILD, I can find the required file at /lib/x86_64-linux-gnu/

and This is my linux_opencv config, I suspect whether it's right or not.

And here is what in the unity

can you please help me ? thanks

Well I'm quite confused about what I should set in WORKSPACE and opencv_linux.Build.
According to my understanding :
if I set opencv_linux. build  to
 #          "lib/x86_64-linux-gnu/libopencv_core.so",
 #           "lib/x86_64-linux-gnu/libopencv_calib3d.so",
 #           "lib/x86_64-linux-gnu/libopencv_features2d.so",
 #           "lib/x86_64-linux-gnu/libopencv_highgui.so",
 #           "lib/x86_64-linux-gnu/libopencv_imgcodecs.so",
 #           "lib/x86_64-linux-gnu/libopencv_imgproc.so",
 #           "lib/x86_64-linux-gnu/libopencv_video.so",
 #           "lib/x86_64-linux-gnu/libopencv_videoio.so",

Then I should set WORSPACE to
new_local_repository(
    name = "linux_opencv",
    build_file = "@//third_party:opencv_linux.BUILD",
    path = "/usr",
)

while if I set opencv_linux. build  to
            "lib/libopencv_core.so",
            "lib/libopencv_calib3d.so",
           "lib/libopencv_features2d.so",
            "lib/libopencv_highgui.so",
            "lib/libopencv_imgcodecs.so",
            "lib/libopencv_imgproc.so",
            "lib/libopencv_video.so",
            "lib/libopencv_videoio.so",

Then I should set WORSPACE to
new_local_repository(
    name = "linux_opencv",
    build_file = "@//third_party:opencv_linux.BUILD",
    path = "path to opencv/build",
)

Am I rifght ? I'm quite confused about it..

Then I should set WORSPACE to
new_local_repository(
    name = "linux_opencv",
    build_file = "@//third_party:opencv_linux.BUILD",
    path = "path to opencv/build",
)

No, path must be the installed directory.
new_local_repository define the specified path as its project root directory.
Say you have below files on your local machine.
/path/to/project1/lib/x.so
/path/to/project1/lib/y.so
/path/to/project1/include/x.h
/path/to/project1/include/y.h
/path/to/project2/lib/x.so

In this case, to import project1, your WORKSPACE file would be like this.
new_local_repository(
    name = "project1",
    build_file = "@//third_party:project1.BUILD",
    path = "/path/to/project1",
)

Then, in third_party/project1.BUILD, you can access files under /path/to/project1 (note that you cannot access /path/to/project2/lib/x.so).
cc_library(
    name = "opencv",
    srcs = [
      # relative paths from /path/to/project1
      "lib/x.so",
      "lib/y.so",
    ],
    hdrs = [
      "include/x.h",
      "include/y.h",
    ]),
    includes = [
      "include/",
    ],
    linkstatic = 1,
    visibility = ["//visibility:public"],
)

By the way, you don't need to install OpenCV necessarily.
Run python build.py build --desktop --opencv=cmake -vv, then OpenCV will be built and linked statically.
cf. https://github.com/homuler/MediaPipeUnityPlugin#build-command


Use explicit conversion operator instead of explicit constructor

I also added a type trait test to check whether the conversion operator / constructor is marked explicit.
this change has the advantage of being  clearer imo as it is a conversion operator for conersions not a constructor.
and also it allows users to take the address of convesion operator which I don't know if someone might find that useful.

To me this moves the operation to the wrong side. On an API level we're saying now, that a vector can be converted into another, instead of being constructable from another type.

I immediately cannot think of anything wrong with this approach, it's simpler than the status quo and moves us closer to making vectors into aggregate types, so I'm in favour.

To me this moves the operation to the wrong side. On an API level we're saying now, that a vector can be converted into another, instead of being constructable from another type.

Why is it "wrong" to say that "a Vector2f can convert to a Vector2u" and why is it "right" to say that "a Vector2u can be constructed from a Vector2f"?
If anything, the conversion feels more natural/intuitive to me.

Codegen is affected with -O0 on both GCC and Clang, but I cannot tell if it's significant. With -O1 and above, codegen is the same. See https://gcc.godbolt.org/z/8bPfos17z

SFMLBuildMaster: Build this please.

For the sake of consistency I think sf::priv::Vector4 also needs this treatment.

To me this moves the operation to the wrong side. On an API level we're saying now, that a vector can be converted into another, instead of being constructable from another type.

Yes, because this is what it is do you say when you see this int(1.5f) that you are constructing an int from a float or do you say I convert the float to the int? same here I say I convert this Vector2f to a Vector2i.

SFMLBuildMaster: Build this please.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 56.97%

Totals

Change from base Build<PHONE_NUMBER>3:
0.007%

Covered Lines:
11883

Relevant Lines:
19876

💛  - Coveralls


Leverage eventing-kafka field of config-kafka in consolidated channel and in source

Problem
There's an eventing-kafka field in config-kafka of the distributed channel:
eventing-kafka: |
    receiver:
      cpuRequest: 100m
      memoryRequest: 50Mi
      replicas: 1
    dispatcher:
      cpuRequest: 100m
      memoryRequest: 50Mi
      replicas: 1
    kafka:
      brokers: REPLACE_WITH_CLUSTER_URL
      enableSaramaLogging: false
      topic:
        defaultNumPartitions: 4
        defaultReplicationFactor: 1 # Cannot exceed the number of Kafka Brokers!
        defaultRetentionMillis: 604800000  # 1 week
      adminType: kafka # One of "kafka", "azure", "custom"

To be consistent (see the umbrella ticket, https://github.com/knative-sandbox/eventing-kafka/issues/404), we can also leverage these settings in consolidated channel and also in Kafka source.
To talk about fields specifically:

receiver: could only be used in distributed channel
dispatcher: could be used in distributed and consolidated channel
kafka.brokers: Consolidated channel has a separete field in config-kafka called bootstrapServers. We should leverage that in distributed channel too. eventing-kafka.kafka.brokers then would be used as a default OR if possible, we can get rid of that.
kafka.enableSaramaLogging: could be used in all 3 components (2 channels and the source)
kafka.topic: could be also used in consolidated channel
kafka.adminType: could be also used in consolidated channel

Persona:
Which persona is this feature for?
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.

@travis-minke-sap @eric-sap
May I ask you to review the suggestions in the PR?
How flexible are you in terms of changing the structure of eventing-kafka?
Maybe something like this would be better?
channel:
  receiver:
    cpuRequest: 100m
    memoryRequest: 50Mi
    replicas: 1
    enableSaramaLogging: false
  dispatcher:
    cpuRequest: 100m
    memoryRequest: 50Mi
    replicas: 1
    enableSaramaLogging: false
  topic:
    defaultNumPartitions: 4
    defaultReplicationFactor: 1 # Cannot exceed the number of Kafka Brokers!
    defaultRetentionMillis: 604800000  # 1 week
  kafka:
    adminType: kafka # One of "kafka", "azure", "custom"
source:
  foo: bar

Hi Ali - Thanks for continuing the effort to align the two implementations - it would be great to share this config!  I'll ask that @eric-sap also review as he's been implementing a lot of this configuration on the distributed kafkachannel.
Responding to your proposal...

Seems fine to change the top level organization from eventing-kafka to channel
In general I am ok with making the enableSaramaLogging more granular (receiver/dispatcher) BUT... I think your proposal doesn't include the "controller" which is a separate Deployment/Pod for the distributed kakfachannel.
Keep in mind (just stating the obvious so it's clear) that the values in topic.XYZ are defaults which are used only in the case when the KafkaChannel CRD doesn't specify them (for NumPartitions & ReplicationFactor).   On that note... It would be good for us to add Retention to the KafkaChannel CRD at some point (we had it in our version of the CRD before we converted over).
The kafka.brokers can be moved/renamed as you suggested - whichever language is more "standard" in the kafka world (I've seen both).  I agree that we wouldn't want to have two though - just move and rename to match, etc.  Also, fwiw... Eric just moved that from our Secret to the ConfigMap yesterday in order to better align with consolidated!
The adminType field would be great for the consolidated implementation to support, and that was my goal with #297 but I ran into a blocker making the adminClient interface usable by the consolidated channel.  This is because in order to support azure/custom/etc. I've wrapped the sarama admin client with a slimmed down interface which just creates/deletes topics.  This is all the distributed version needs, but.. the consolidated versions is/was using the adminclient to get a list of consumergroups in order to manage status of the kafkachannel.   Soooo... we'll have to find a solution to that before the adminType field can be supported by the consolidated channel.  Totally do-able I'm sure just need to sort it out ; )

As part of all this work we have a simple wrapper function in pkg/channel/distributed/common/kafka/sarama called EnableSaramaLogging() that should probably be moved to pkg/common.

Adjusting the format of that configmap shouldn't be a big issue, though it would need to be a few bits of changes in various places as the main EventingKafkaConfig struct in pkg/channel/distributed/common/config/configwatcher.go would need to be adjusted to match (which would trigger the need for some one-line-type modifications in the places that use that struct).
As for the particular new format, I have no attachment or druthers for anything existing.

Seems fine to change the top level organization from eventing-kafka to channel

Actually, that wasn't my intention. I just wanted a channel field as a child of eventing-kafka field, so that we can have a source field as well.
It can be like:
kind: Configmap
data:
  eventing-kafka: |
    channel: ...
    source: ...

In general I am ok with making the enableSaramaLogging more granular (receiver/dispatcher) BUT... I think your proposal doesn't include the "controller" which is a separate Deployment/Pod for the distributed kakfachannel.

Ok, let's not do this.

I agree that we wouldn't want to have two though - just move and rename to match, etc

Yes. Apart from naming, I think we should change this to a top level field in config-kafka as it is like that in consolidated. OR, have it in eventing-kafka like distributed channel.
When I think about it, having it under a channel field sounds better now since it is irrelevant for sources (sources define the Kafka servers in their CRDs). See below.
Another go at the config-kafka(with less disruption after I've read the reasons why you organized eventing-kafka field like that):
data:
  bootstrapServers: REPLACE_WITH_CLUSTER_URL         # ------> this will be deprecated (consolidated uses this)
  authSecretName: name-of-your-secret-for-kafka-auth
  authSecretNamespace: namespace-of-your-secret-for-kafka-auth                    # -------> needs discussion
  sarama: |
    Version: 2.0.0 # Kafka Version Compatibility From Sarama's Supported List (Major.Minor.Patch)
    ...
  eventing-kafka: |
    channel:
      receiver:             # -----------> only to be used in distributed ch's dispatcher
        cpuRequest: 100m
        memoryRequest: 50Mi
        replicas: 1
      dispatcher:           # -----------> to be used in both ch's dispatchers
        cpuRequest: 100m
        memoryRequest: 50Mi
        replicas: 1
      kafka:
        brokers: REPLACE_WITH_CLUSTER_URL      # ------------> consolidated will also start using this field
        topic:                # -----------> to be used in both channel impls
          defaultNumPartitions: 4
          defaultReplicationFactor: 1 # Cannot exceed the number of Kafka Brokers!
          defaultRetentionMillis: 604800000  # 1 week
        enableSaramaLogging: false
        adminType: kafka # One of "kafka", "azure", "custom"
    source:                 # reserved for future use, not going to be read right now
      foo: bar

Top level authSecretName and authSecretNamespace are used by consolidated channel for auth with Kafka.
Any suggestions to unify the auth?

👍  On the hierarchy of channel and source under eventing-kafka
👍  On the authSecretName and authSecretNamespace ... This is something that we want to switch over to once we have the time.  Currently we have a separate Controller which watches the secrets (based on a label).  This was done in the past to support dynamically adding Azure EventHub Namespace secrets (which have a limited number of Topics).  I've since removed that capability, and we no longer need/want to watch the secrets and instead want to align with the consolidated implementation by using a specified namespace/name in the configmap as you suggest.  I think you can proceed with adding these fields and we'll have to determine when/how to make use of them (ie - refactoring that controller back into the "other" / "standard" controller).
Thanks again - looking good!

Thanks for the feedback. All agreed!
Then I suggest we move authSecretName and authSecretNamespace from top-level to under eventing-kafka.auth (new field).
So, my final proposal:
data:
  bootstrapServers: REPLACE_WITH_CLUSTER_URL         # ------> this will be deprecated (consolidated uses this)
  authSecretName: name-of-your-secret-for-kafka-auth         # -------> will be deprecated
  authSecretNamespace: namespace-of-your-secret-for-kafka-auth                   # -------> will be deprecated
  sarama: |
    Version: 2.0.0 # Kafka Version Compatibility From Sarama's Supported List (Major.Minor.Patch)
    ...
  eventing-kafka: |
    channel:
      receiver:             # -----------> only to be used in distributed ch's dispatcher
        cpuRequest: 100m
        memoryRequest: 50Mi
        replicas: 1
      dispatcher:           # -----------> to be used in both ch's dispatchers
        cpuRequest: 100m
        memoryRequest: 50Mi
        replicas: 1
      auth:
        secretName: name-of-your-secret-for-kafka-auth         # -------> will be moved here
        secretNamespace: namespace-of-your-secret-for-kafka-auth                   # -------> will be moved here
      kafka:
        brokers: REPLACE_WITH_CLUSTER_URL      # ------------> consolidated will also start using this field
        topic:                # -----------> to be used in both channel impls
          defaultNumPartitions: 4
          defaultReplicationFactor: 1 # Cannot exceed the number of Kafka Brokers!
          defaultRetentionMillis: 604800000  # 1 week
        enableSaramaLogging: false
        adminType: kafka # One of "kafka", "azure", "custom"
    source:                 # reserved for future use, not going to be read right now
      foo: bar

I hope to start working on this in the upcoming weeks.
Just a note to myself: consolidated channel should still support the "to be deprecated" fields for a few releases.

/assign


Added important PyLint messages.

Thank you for your contribution. This change cannot be merged as it does not follow the original repository.


Contributions made (favicon, bug fixes, etc)

Cater for scenario where the environment KEY is empty
Set the workspace intended environment on the workspace instead of on GlobalWorkspace
Allow functions to inherit environment.
Wrap the "GetColumn" output in a <pre> tag. This is useful when the return result has multiple lines. For instance if the Function Command is git -C $PATH status -s
Added column headers to the home page (workspaces.html)
Added a favicon.ico
Added a contribution guide (CONTRIBUTING.md)

awesome :smile_cat: thanks @francoishill!


edit scripts used to make ch and page level coding data

Take a look at my changes to how we create coding data (both ch and page level)

Great! So @claudiacsutter, in this case, we are putting "commits" (fruits!) onto the correctness-coding branch. So make sure to pull that branch so you can have the most updated version of the repo. Let me know if you have questions!


type : "static" in mixin flags an error

It is traditional that when only a statics section is provided, there be (or may be) an annotation that the file contains only static values and methods:
type : "static",

When this annotation exists in a mixin, the compiler flags as an error the fact that type is not a valid key. This should either be accepted since it may exist in much legacy code, or be flagged as a warning. (There's no real need for that annotation; it could be simply removed.)

@derrell @johnspackman Is this still the case or can the issue be closed?

@derrell I think that this may be wrong - I just coded the fix for this, but when I run my test app in the browser it breaks;
Issue240.js:
qx.Class.define("testapp.Issue240", {
  extend: qx.core.Object,
  include: [ testapp.MIssue240 ]
});

MIssue240.js
qx.Mixin.define("testapp.MIssue240", {
  type: "static",

  statics: {
    A: 1
  }
});

Browser output:
Mixin.js:362 Uncaught Error: The configuration key "type" in mixin "testapp.MIssue240" is not allowed!
    at Object.__validateConfig (Mixin.js:362)
    at Object.define (Mixin.js:96)
    at MIssue240.js:1
    at MIssue240.js:1
qx.Mixin.__validateConfig() @ Mixin.js:362
qx.Mixin.define() @ Mixin.js:96
(anonymous) @ MIssue240.js:1
(anonymous) @ MIssue240.js:1
Class.js:867 Uncaught Error: The include definition in class "testapp.Issue240" contains an invalid mixin at position 0: undefined
    at Object.__validateConfig (Class.js:867)
    at Object.define (Class.js:187)
    at Issue240.js:1
    at Issue240.js:1
qx.Class.__validateConfig() @ Class.js:867
qx.Class.define() @ Class.js:187
(anonymous) @ Issue240.js:1
(anonymous) @ Issue240.js:1
Native.js:58 001085 qx.core.Init: Load runtime: 1085ms


Implement while and do-while

Implement while and do while
Description:

The translator has no grammar for the while and do-while loops. These are major features that must be added.
The followings must be implemented:

[ ] 1.  while loop grammar
[ ] 2.  do while loop grammar

/*Syntax -
Entry Control Loop (While) -
while(condition){
block of statements
}
Exist Control Loop (Do while)-
do{
block of statements
}while(condition)
*/
**While Loop example -
#include <stdio.h>
int main () {
/* local variable definition */
int a = 10;
/* while loop execution */
while( a < 20 ) {
printf("value of a: %d\n", a);
a++;
}
return 0;
}
**Do while example:
#include <stdio.h>
int main()
{
int j=0;
do
{
printf("Value of variable j is: %d\n", j);
j++;
}while (j<=3);
return 0;
}

Hey @martinezlucas98, can you please help me out with this project. I really want to contribute in this project. My technical skills include C, C++, Python & Java. i think i can figure this out. Just need some guidance.

Sure, this is more of a YACC and LEX project than a C, C++, java, but its really simple.

YACC is a parser generator based on formal grammar notation similar to BNF; and LEX  generates lexical analyzers.

If you are already familiarized with grammars this should be pretty easy. You could take a look to the java2cpp.y in the alpha branch , the nonterminals STATEMENTS and STDIO might be a good example for understanding how it works.
A grammar for the while loop  could be something like: WHILE LP EXPRESSION RP LC STATEMENTS RC SEMICOLON
You could read the tokens meanings at TOKENS.md, this tokens are defined in java2cpp.l.

If you are interested I can assign you this issue and feel free to submit a PR whenever you feel like! :+1:

Thank you, that's so nice of you. I will go through the project and try to figure this out, and if felt something to discuss i will report you.

@martinezlucas98, I added grammar for while loop and also added printf grammar for "do". Please have a look and suggest if any changes are required. Thank you.

@Shree-Gillorkar
Great!! Just make a pull request to our alpha branch and I will take a look at it as soon as I can.

@martinezlucas98 ya sure, thank you!

Hey @Shree-Gillorkar sorry for the delay, your PR looks pretty good! It just needs a few changes which I mention on your PR. Once you make those changes everything will be good to merge. :+1:

Hey, @Lucas Martinez,  It's okay. Hope you are doing quite well. This is
my 1st open source project on which I am working. I would like to thank you
for encouraging and supporting me in knowing this world of open source
contributors. I made the changes you suggested. Hope I can solve the issue
and lend you a helping hand in this project.
On Tue, 25 May 2021 at 05:38, Lucas Martinez @.***>
wrote:

Hey @Shree-Gillorkar https://github.com/Shree-Gillorkar sorry for the
delay, your PR looks pretty good! It just needs a few changes which I
mention on your PR. Once you make those changes everything will be good to
merge. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/martinezlucas98/java2cpp/issues/10#issuecomment-847435299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQWJG7IYMRBIMHZEMGW7IULTPLS7VANCNFSM44TT7SBA
.

Perfect!! Thank you for your help @Shree-Gillorkar


Buttons inside carousel first touch on mobile does not work

For a carousel that has buttons inside, on mobile, with mouseDrag = false, on first touch the on click event for button is not called. After first touch, everything works perfect.
See this example. The issue is on second carousel with buttons, but you have to change your browser into mobile view. You will notice that on first click, the console log does not appear.
https://codesandbox.io/s/ncpb8

I'm having the same problem
On vue3-carousel - "version": "0.1.29"

Found the solution here #46

I will try, but this is only a workaround. We need a proper fix for this.

possible solution is to use touchmove as a disabler for the touchend event:
<Slide
  v-for="item in items"
  :key="item"
  @touchend="handleClick"
  @touchmove="handleTouchMove"
>

const canClick = ref(true);
const handleTouchMove = () => {
  canClick.value = false;
};
const handleProductClick = (product: MenuItem) => {
  if (canClick.value) {
     // do what you want with the click
  } else {
    canClick.value = true;
  }
}

Having this issue as well, also on 0.1.29


[RFE] map the container image to the actual git commit

Is your feature request related to a problem? Please describe.
In order to proper debug user issues, we need an easy way to map the container image with the actual code running in it.
Describe the solution you'd like
Embed the git commit SHA into the image's metadata would be the cheapest way to achieve this.
Describe alternatives you've considered
Using LD flags and exposing a --version command would be an alternative, but it has the following drawbacks:

requires code changes
requires pulling the image
requires running the image

I think also logging the git release version, commit id and build time would also help debugging.

Good point!
I agree this is useful, especially for production systems.
Let's focus on this on a follow-up PR.
I'll open another issue.
For my understanding:

we should log the commit ID from the running application (the controller)
we should time the build time during go build - so this is just adding a line to the build script
the git release version should also come from the CI system.

@kmabda

@maiqueb agree.
Yes, for production system logging the git commit ID and the git release version are useful info for troubleshooting/filing an issue.


Fixes issue with truncation of application ids when parsing logs

To build the url to job logs in Hadoop/Spark servers (#1695) we currently get the application ids by parsing the Azkaban job logs.
This PR fixes a bug that appears when processing job logs by chunks.
-Application ids can be missed when they are accidentally truncated. For example:
"application_1556244585372_1234567" truncated to "_155624458537_1234567" which will not match the pattern "application_(\d+_\d+)"
-Application ids can also be invalidated. For example:
"application_1556244585372_1234567" truncated to "application_1556244585372_1"

Thanks for addressing the comments. Are you looking into code dedup as well?


Bug in CoreNEURON GPU implementation

Creating separate issue reported by @pkuzyc in #60 :
I tried to use the current commit of CoreNEURON to simulate this PC model, but there is a segmentation fault when I run it. The same error also happens when I run ringtest with this commit. The error message is :

--- Copying to Device! ---
-----------COPYING 0'th NrnThread TO DEVICE ---------------
GPU MEMORY USAGE (MB) : Used = 66.375000, Free = 11373.500000 MB, Total = 11439.875000zsh: segmentation fault (core dumped)  ./coreneuron_exec -e 100 -d  --gpu
is there anything wrong?

It works well. Thank you so much!


ParserSyntaxError: syntax error in feature files

I'm on a Windows 7 OS with:
Ruby 2.2.4...
yard (<IP_ADDRESS>)
yard-cucumber (2.1.6)
cucumber (>= 0.7.5)
gherkin (>= 2.2.9)
yard (>= 0.7.0)
I've copied a piece of an example scenario:
Comments that appear before the feature are associated with the feature
@scenarios
Feature: Displaying Scenarios
As a reader of the documentation I expect that scenario are documented correctly
Comments after the feature description belong to the background or first scenario
Background:
Given this background step
@first @bvt
Scenario: No Step Scenario
@second @bvt
Scenario: Scenario With Steps
Given this first step
When this second step
Then this third step
And I created a rakefile with:
require 'yard'
YARD::Rake::YardocTask.new do |t|
t.files  = ['features/**/example.feature']
end
My output is:
rake yard
[warn]: Error loading plugin 'yard-cucumber'
[warn]: Syntax error in features/consumer/banner.feature:(3,8): syntax error, unexpected ':', expecting end-o
f-input
[warn]: ParserSyntaxError: syntax error in features/consumer/banner.feature:(3,8): syntax error, unexpected '
:', expecting end-of-input
[warn]: Stack trace:
C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/ruby/ruby_parser.rb:545:in on_parse_er ror'         C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/ruby/ruby_parser.rb:50:inparse'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/ruby/ruby_parser.rb:50:in parse'         C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/ruby/ruby_parser.rb:15:inparse'
C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/source_parser.rb:439:in parse'         C:/Ruby22/lib/ruby/gems/2.2.0/gems/yard-<IP_ADDRESS>/lib/yard/parser/source_parser.rb:44:inblock in parse'
Files:           0
Modules:         0 (    0 undocumented)
Classes:         0 (    0 undocumented)
Constants:       0 (    0 undocumented)
Methods:         0 (    0 undocumented)
100.00% documented

Ya.. I'm having a similar issue..
It seems like yard is not recognizing feature files,
(and is still only using the ruby parser)
additionally I also tried adding
:"yard-cucumber":
  menus: [ 'features', 'directories', 'tags', 'steps', 'step definitions' ]
  language:
      step_definitions: [ 'Given', 'When', 'Then', 'And']

to my

~/.yard/config file

too, but that doesn't help.
Not sure what we are doing wrong..
I am just hoping an issue here helps getting inputs from people who actually use yard-cucumber :)

I believe it has something to do with using Ruby 2.2.4.  I wasn't having these issues with Ruby 2.17

Hmm.. I'm debugging my way through yard-cucumber2  and feel that it is the cucumber and gherkin versions  that is the issue (lookin at some requires here) Can you please let me know the cucumber and gherkin versions that you are using with your Ruby 2.17 as opposed to your 2.2.4 ?
(i'm in Ruby 2.2.0 btw.. with cucumber (2.3.2) and gherkin (3.2.0))

Sorry, I don't know what versions of cucumber and gherkin I was using with 2.1.7.  But, the good news is that am no longer having this issue on a Windows machine.  The commits on Mar 14, 2016 must have fixed it.
I am however seeing this issue still when running from CentOS
I believe we can close this ticket and I'll open a new one for the CentOS issue.


Auto-completion together with autoloads

Godot version
4.0.2 rc1
System information
Windows 10
Issue description
In my projects, I often have a Common.gd as autoload and store references to my classes in there. For instance, I have a var game_ref: Game in my autoload, and then I can just call some_method_in_game() by typing
Common.game_ref.some_method_in_game() from anywhere in my code.
But I have noticed that auto-completion cannot fetch some_method_in_game(), unless I specifically cast game_ref to Game. This is an issue with variables in auto-loads, autocompletion for classes in the same script file works.
See these examples:

Auto-completion works as intended here, when I don't use autoloads.

This does not work, some_method_in_game() does not show up.

If I cast it, it works.

My game_ref variable is static typed in Common.gd.

I would like autocompletion to work with autoloads without having to cast the variable. This shouldn't be necessary since the variable already is static typed with the correct class type.
Steps to reproduce
See issue description.
Minimal reproduction project
Demo.zip

Duplicate of https://github.com/godotengine/godot/issues/74058.


Build standalone windows exe

On push with tag run github action and uploads build exe file to the action as an artefact.

All fixed, should be ready for merge!


cannot read property 'indexof' of undefined

When i run ‘pbiviz start' , it's show error:'  cannot read property 'indexof' of undefined',,  what`s happend?

Hello, could you copy full output of error? And which version of tools and node js do you use?

Hi,
I get this error too. Im trying to install the pbiviz package to use the Custom Visual with R and Power BI.
The full output is:
warn Local certificate not found.
warn Checking global instance of pbiviz certificate
error Cannot read property 'index0f' of undefined
Node version: 10.16.03
Power BI version: 2.73.5586.1101
R version: 3.6.1
Windows 7 - 64 bit

hello @MaAngelica, this bug will be fixed in upcoming version of<EMAIL_ADDRESS>soon.


Add option to open a browser window for every new email

Pull request for issue #221

@sbrink This is very very cool. I want to try this out locally on first and assuming it looks good I'll go ahead and merge this in. Thank you!

Just tested this out on a project in macOS, and it worked great!
Thanks @sbrink!


correct form of [Symbol.iterator]

hotfix! i didn't implement this quite right before. esoteric stuff!

Would be nice to add a test case that this fixes, if that's easy enough (from my one PR, the tests seem easy to add to, fwiw).

I agree with @hamzakubba. May I ask you to add a test case? Thanks!

absolutely!

Thank you! I'm on the go until Saturday and will take a look then.


Update to js-ipfs 0.31

https://twitter.com/_alanshaw/status/1023505986747883521
This will make the screenshot feature work again.

@jacobheun can you handle this one?

I’m on it, since as of now we can’t use the vanilla js-ipfs
On 30 Jul 2018, 09:26 +0100, Jacob Heun<EMAIL_ADDRESS>wrote:

Yes, I'll work on getting this pulled in!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Update proximity color

It just changes the "closest player" (DTC) or "closest kill" (CTW) to gray, and "closest save" (CTW) to yellow

@TiTo-418 @iEli2tyree011 fixed in #798 , should be closed


UnmarshalFlag error is not propagated when parsing positional arguments

For example: given a command with a single positional argument named PATH, if parsing of the path fails in its UnmarshalFlag, user only sees "the required argument PATH was not provided" instead of the text from the error returned by UnmarshalFlag.

@jessevdk Thanks!


Build problem

When I try to build the project I get the following problem:
gcc -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=legacy -Wno-compare-reals -Wno-unused-parameter -c lbfgsb/blas.f -o lbfgsb/blas.o clang: warning: argument unused during compilation: '-fimplicit-none' clang: warning: argument unused during compilation: '-finit-local-zero' clang: warning: argument unused during compilation: '-fbounds-check'
warning: unknown warning option '-Wno-compare-reals' [-Wunknown-warning-option]
error: invalid value 'f95' in '-x f95'
error: invalid value 'legacy' in '-std=legacy'

It looks like you are using clang as your compiler instead of gcc (gfortran). (I didn't know clang even compiles Fortran!) Since clang and gcc have different options, you will either have to adjust the makefile so that it works with clang or use gcc/gfortran instead. I don't have any experience with clang, so I can't help you there. Another approach would be to compile the Fortran by hand (without the makefile), and then invoke the makefile to do the rest.
I don't know where your '-x f95' is coming from because it doesn't show up in any of my compile commands, so I suspect that is added by clang.
Have you checked that clang supports Fortran? Your errors and warnings regard Fortran-specific options, which suggests that clang doesn't actually support Fortran.
I would recommend just using the gfortran compiler after checking it is a sufficient version (>= 4.4.6). Specifying gfortran directly will avoid gcc pointing to clang.
$ gfortran --version
$ make compiler=gfortran

Explicitly using gfortran helped start the compilation, but now there is a problem with --relocatable option
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=legacy -Wno-compare-reals -Wno-unused-parameter -c lbfgsb/blas.f -o lbfgsb/blas.o
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=legacy -Wno-compare-reals -Wno-unused-parameter -c lbfgsb/linpack.f -o lbfgsb/linpack.o
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=legacy -Wno-compare-reals -Wno-unused-parameter -c lbfgsb/timer.f -o lbfgsb/timer.o
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=legacy -Wno-compare-reals -Wno-unused-parameter -c lbfgsb/lbfgsb.f -o lbfgsb/lbfgsb.o
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=f2003 -c lbfgsb.f03 -o lbfgsb.o
gfortran -g -Wall -Wextra -fimplicit-none -finit-local-zero -fbounds-check -std=f2003 -c lbfgsb_c.f03 -o lbfgsb_c.o
ar cr liblbfgsb.a lbfgsb_c.o lbfgsb.o lbfgsb/lbfgsb.o lbfgsb/blas.o lbfgsb/linpack.o lbfgsb/timer.o
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: liblbfgsb.a(lbfgsb.o) has no symbols
ld --relocatable lbfgsb_c.o lbfgsb.o lbfgsb/lbfgsb.o lbfgsb/blas.o lbfgsb/linpack.o lbfgsb/timer.o -o lbfgsb.syso
ld: unknown option: --relocatable
make: *** [lbfgsb.syso] Error 1

What ld are you running (ld --version)? It looks like --relocatable has been in GNU ld for a long time so I suspect you are again getting a substitute, i.e. ld is pointing to clang. What build environment are you using anyway?
In any case, and as far as I remember, --relocatable is needed in order to make a system object (*.syso) for Go to include when it compiles your program into a binary, so you will need to find a linker that can do that and then edit the makefile to use that linker. There may be other ways to go about things, like gcc can create a syso directly, so experiment and let me know if you find a build process that works better, or is more direct, or relies on fewer tools/steps, etc.

How are you coming along with this?

Unfortunately I was not able to set your library, I think it is not related with the problems of the library, but with my limited knowledge in build projects. Thank you

Sorry you didn't get it working. If you have any further questions, just reopen this issue.

I had a similar problem, which I fixed by changing --relocatable to -r. Apparently ld in Mac OS doesn't support the full name of this parameter.
Here are all the steps I took to get this working on Mac OS:

Using Homebrew, install gcc (the current version is 5.2.0)
Edit the makefile variables as follows:

Change compiler to gcc-5
Change --relocatable to -r in the ld command

Tell the linker where to find libgfortran with an environment variable change:

From $GOPATH/github.com/afbarnard/go-lbfgsb run LIBRARY_PATH=/usr/local/lib/gcc/5 go build

After this, the library built correctly.

Yes. It worked. Thank you!


Updated redirect when logged in

Solves #34

Hey
I've just setup this project but i am not able to access the admin panel.
I can see the blank page when i fire "/dashboard" route.
Please find the attachment.

Hoping for your response.
Thanks,
Sunny

Still no merge?

I really don't know why you see this blank page. Does it have to do anything with my change?


brain-score.org submission (user:386) | (public:False)

Plugin-only changes from brain-score.org submission. Generated via Jenkins job create_github_pr, build 172. Plugins added: models: [eMMCR_Vanilla_1]

already added


Need to update install instructions

Link to the page
Quote of Error
On the instruction page, there's a directions that one needs to install
qtbase5-dev
When I installed this package on a fresh, stock install of Ubuntu, I got the message "could not find a Qt installation of ''".
I looked for the error in Stackoverflow and found that also running the command
sudo apt-get install qt5-default
seemed to fix this problem.
Proposed changes
I would suggest adding the qt5-default it to the documentation, as well as doing a double check with a clean install of Ubuntu just to make sure there's no additional dependencies missing in the docs. I'm guessing that the devs on this project already had a lot of the qt infrastructure set up on their machines, and a few stray dependencies they forgot were needed might have gotten past the docs.
One other suggestion, I think a lot of people, including myself, would be installing this for Ubuntu, so perhaps a
sudo apt-get install qtbase5-dev
sudio apt-get install qt5-default
Would be useful in a "Installing for Ubuntu" section.

Im trying to start a new project with proton native, but when i execute the command
Im getting this error
` > npx proton-native-cli init Creator
npx: instalou 45 em 13.866s
Creating a new Proton Native app on /home/rafael/dev/pratice/Creator
Installing packages... This may take a few minutes.

<EMAIL_ADDRESS>install /home/rafael/dev/pratice/Creator/node_modules/node-qt-napi
cross-env JOBS=max node-pre-gyp install --fallback-to-build

node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v72 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error Remote end closed socket abruptly.
/bin/sh: 1: pkg-config: not found
gyp: Call to 'pkg-config --libs-only-l Qt5Core Qt5Gui Qt5Widgets' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/rafael/.asdf/installs/nodejs/12.16.3/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:310:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Linux 5.3.0-51-generic
gyp ERR! command "/home/rafael/.asdf/installs/nodejs/12.16.3/bin/node" "/home/rafael/.asdf/installs/nodejs/12.16.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4/qt.node" "--module_name=qt" "--module_path=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=4" "--node_napi_label=napi-v4"
gyp ERR! cwd /home/rafael/dev/pratice/Creator/node_modules/node-qt-napi
gyp ERR! node -v v12.16.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/home/rafael/.asdf/installs/nodejs/12.16.3/bin/node /home/rafael/.asdf/installs/nodejs/12.16.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4/qt.node --module_name=qt --module_path=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4 --napi_version=5 --node_abi_napi=napi --napi_build_version=4 --node_napi_label=napi-v4' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/home/rafael/dev/pratice/Creator/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:310:20)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
node-pre-gyp ERR! System Linux 5.3.0-51-generic
node-pre-gyp ERR! command "/home/rafael/.asdf/installs/nodejs/12.16.3/bin/node" "/home/rafael/dev/pratice/Creator/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/rafael/dev/pratice/Creator/node_modules/node-qt-napi
node-pre-gyp ERR! node -v v12.16.3
node-pre-gyp ERR! node-pre-gyp -v v0.13.0
node-pre-gyp ERR! not ok
Failed to execute '/home/rafael/.asdf/installs/nodejs/12.16.3/bin/node /home/rafael/.asdf/installs/nodejs/12.16.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4/qt.node --module_name=qt --module_path=/home/rafael/dev/pratice/Creator/node_modules/node-qt-napi/bindings/napi-v4 --napi_version=5 --node_abi_napi=napi --napi_build_version=4 --node_napi_label=napi-v4' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: cross-env JOBS=max node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!


Found a very strange error(It seems to reload once (twice total)

I followed the standard documentation line by line without adding any additional steps, then ran it, opened the browser to access it, and found that when loading the page, it seemed to reload once (twice in total) and then I saw this error log through the browser console.

It's the hydration mismatch error. It appears to be coming from the nonce value in the links scripts. I've tried to fix this but to no avail. This article will give you some context on the issue https://www.jacobparis.com/content/remix-hydration-errors

I've just added a documentation bit about this: https://github.com/epicweb-dev/epic-stack/blob/main/docs/troubleshooting.md#hydration-mismatch

The browser strips the nonce from the DOM before executing any JavaScript for security reasons

Great to know! I almost lost my mind debugging this :)


chore: update jetson pytorch baase

Signed-off-by: Naren Dasan<EMAIL_ADDRESS>Description
Updates the base pytorch version for jetson
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

@andi4191 FYI may address your sbsa issues in #1244


UofT-DSI | SQL- Assignment

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)

I designed a logical model for a small bookstore, including entities such as employee, order, sales, customer, book, a date table, etc. Additionally, I have added employee shifts, splitting the day into morning and evening.

What did you learn from the changes you have made?

I learnt about designing logical models for relational databases, including identifying entities, defining relationships, and determining sensible column and table design. Additionally, I gained insights into incorporating additional features such as employee shifts into the model to accommodate specific business requirements.

Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?

I was thinking about incorporating timestamp in milliseconds, a four-digit random combination, and a series number to generate a unique order_id for the small store. This ensures that even as the store grows in future and handles more orders for concurrent branches, each order retains a unique identifier that can be easily tracked and managed.

Were there any challenges? If so, what issue(s) did you face? How did you overcome it?

One challenge I faced was determining the appropriate level of granularity for the logical model while keeping it simple yet comprehensive. I addressed this by carefully considering the bookstore's operations and identifying key entities and relationships essential for its functionality.

How were these changes tested?

The changes were validated through careful review and analysis of the logical model. Additionally, I conducted informal testing by mentally simulating various scenarios to ensure that the model adequately represented the business requirements of the small bookstore.

A reference to a related issue in your repository (if applicable)

N/A

Checklist

[ ✓] I can confirm that my changes are working as intended

You did amazing job on assignment, passed.

You did amazing job on assignment, passed.

Thank you, Sidra.


Creating user on iOS works, but shows loading animation forever

Thanks for this great starter kit. Just one issue I've found.
I'm running a fresh copy from master on the iOS simulator (iPhone 6, 11.4) on MacOS High Sierra.
When I create a new user, it works and adds the user to Firebase (I have confirmed by making my own version connected to my own Firebase database) but it shows the loading circular animation forever.
If I re-click the profile tab icon, I re-see the profile options (Login, Sign Up...). But if I click any of them I re-see the loading animation.
I would expect to see some sort of confirmation when the user is created.
Thanks.

The issue was that the users branch was missing from firebase. But another issue seems to exist so I will open another issue.

Re-opening issue, sorry for closing it by error.

I've submitted a fix. https://github.com/mcnamee/react-native-starter-kit/pull/185


wheel packages

New windows support sounds great so maybe wheel packages help to user to install faster  and without compiler this lib.
There is a lot of packages supporting wheels binaries and could be great if no compilation required to have this app (specially on windows).
Nice work.

This could happen. I've not built a Windows wheel before. Looks like there's some tooling now to build wheels in CI, e.g. https://github.com/joerick/cibuildwheel

+1 to this! If there's any chance that wheels could be built for Linux as well, that would be great.


Initial Committ, top 5 options to start.

Please use this template to ensure easier processing of your pull request
Category

[ ] Content fix
[x] New article
[ ] Example checked item (delete this line)

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
(DELETE THIS PARAGRAPH AFTER READING)

Related issues:

fixes #issuenumber
partially #issuenumber
mentioned in #issuenumber

If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.
(DELETE THIS PARAGRAPH AFTER READING)

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
(DELETE THIS PARAGRAPH AFTER READING)

Guidance

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.
(DELETE THIS PARAGRAPH AFTER READING)

Docs Build status updates of commit 96625a0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/machine-learning-and-managed-metadata.md
:warning:Warning
View
Details

basic-security-set-up-for-microsoft-365.md
:white_check_mark:Succeeded

Community/machine-learning-and-managed-metadata.md

Line 4, Column 9: [Warning-author-not-found] Invalid value for author: 'bhall999' is not a valid GitHub ID.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Thanks, @helloitsliam!


Close idle connections

Regarding https://github.com/sensu/uchiwa/issues/239
By default, the HTTP client will try to reuse HTTP connections however due to the number of requests made to multiple Sensu APIs in a given interval, it could be easy to reach the maximum open file limit.
This is why we want to disable HTTP keep-alive and close all idle connections once the query completed.
CC @bencaron

@bencaron I confirm that https://github.com/bencaron/gosensu/pull/16 is a better fix for the same issue!


Bug in memory optimization

For the activation layer, the forward output tensor of the activation layer is used in calcDerivative - this is added by the manager.
However, the forward input tensor is not used in the calcDerivative and this usage is not removed from the manager.

:octocat: cibot: Thank you for posting issue #1725. The person in charge will reply soon.


Writer Refactor

Some considerations:
I think our current Writer extension mechanism is a bit over-engineered and makes things a bit intransparent for the new user. I wonder if we should consider making a step back, and put state handlers in the custom writer implementation rather than doing them within this external state handler file. I think in most cases Writer apps will be pretty custom and just tie different components together, and you make assumptions on the complete system, like sending a user to the edit citation panel in a certain condition. Often it's hard to implement handleStateChange or handleSelectionChange handlers without knowing the context (e.g. other handlers). I'm really not sure but is there a possibility that we are generally on the wrong track here, when we want to have a transparent programming interface for custom writers?
An extension mechanism would make sense more I think more for concrete implementations. E.g. LensWriter could have it's own extension mechanism.
I may be completely wrong also... I don't want to throw away what we have now... we solve many problems with it when it comes to extensions...  but I have to admit it doesn't feel very intuitive to use.

About extensions: this is what I am saying all the time. I think extension only make sense for a specific application.

I will try to remove the extension stuff and see how it feels.

Oli, can I do this, any negative consequences?
https://github.com/substance/substance/commit/17fc04905a9ae945b6cfa55d0b5febb59e6a2e0f

Another change I've made: Writer now requires a doc instance on construction, the loading stuff must be addressed by the hosting component. Generally it feels good without the extension stuff.
Pls watch this file as I make changes and let me know if anything does not look like a good API.
https://github.com/substance/demos/blob/topic-writer/topic-writer/topic_writer.js
It's kind of hard to decide which things should go into the writer and what should be custom.
For instance.. would you make modals part of the core writer or leave up to the custom implementation? What about the status bar? Not every writer necessarily need it. My demo writer app for instance would just not have it. Next is the save logic+tool. Shouldn't this be done by the implementer, rather then having this abstracted using the backend. Somehow I feel a save button should not go into the content toolbar. But instead be one level above. On the other hand it could be useful to have it as a ready-to-use component. E.g. the save tool should only be active if there are unsaved changes. Not sure about this stuff really.... just that there should be some decisions made for an easy to use Writer API.

Introduced an API for highlights on document. Simplifies the state handler implementation for highlights:
https://github.com/substance/demos/commit/af70f296aa1baa70ced3ea7809e7d26fff61d09e
Please review changes:
https://github.com/substance/substance/commit/704cd9bc8c3d469e6416b69265b79d29e7d7cdfa

Please review and merge if good.
https://github.com/substance/substance/commit/b33ae47a53e9b30297bff1a46b0e8de634d1b26f

I think this should go into surface land as it is purely visual.

But I think we should deal with it in a separate effort.

Hmmm.. And I don't like the squash here. There are also some of my contributions. And particularly, there were some issue fixes.
You can use rebase -i if you want to clean up your commits. But leave mine as they are.

You can find out the original sha using git reflog.

I extracted my commits from the former version of this PR into its own PR.
Then I rebased this one onto the new master (removing conflicts).
For the future:

don't squash contribution of others.
I will never again push to your PR.

Now :+1:

Hey thanks! And sorry for the squash. Will take care of it in next PR.


initial_commit_Boyle_Coello_soiling_model

[X] Closes #739
[X] I am familiar with the contributing guidelines
[ ] Updates entries to docs/sphinx/source/api.rst for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

This is my first contribution, Hence I'm not with the procedure of Pull request.
Please do let me know how to proceed further to complete this pull request.

Welcome! We're happy to help you with the PR process.
Code goes through a number of automated checks and tests, the first being stickler-ci. You should address the formatting issues that stickler identifies first.
@wholmgren @mikofski where to put this function?  I'm thinking a new module is appropriate: soiling.py seems too narrow (I don't know what else it would contain), losses.py too general for the long term (but could be OK for now).

soiling.py seems too narrow (I don't know what else it would contain), losses.py too general

I'm okay with that, for now the only other soiling model I can think of would be the Kimber model, unless maybe Zoe Defreitas decides to publish/contribute something. So I think for now those would be fine inside a losses package, but this might be a good time to revisit the development roadmap. What else would fall into the "losses" camp?

soiling
snow
DC collection losses, cabling, homeruns, combiner boxes
AC collection losses, more cabling? xfmr losses, poi and curtailment, availability
loss budgeting, loss-tree diagram generation
etc

If each of these has several functions or methods, then later, in the future, we could switch to a "losses" folder with submodules (or subfolders eventually) for topics.

Now: pvlib.losses.soiling_hsu where losses.py is a module that contains the function soiling_hsu
Later: pvlib.losses.soiling.soiling_hsu where losses is now a package folder with an __init__.py file containing from pvlib.losses.soiling import soiling_hsu to preserve the existing API, and soiling.py is a submodule containing the function soiling_hsu

or something like that

I will work on the unsuccessful checks and push the updated version.
meanwhile can someone explain me what is codecov/project/library check for and how to correct it.

codecov checks for coverage by unit tests. You can ignore that check until unit tests are added for these new functions.

@nappaillav don't worry about the pvlib.pvlib-python test failures. Let me know if you'd like help with fixing some of the formatting issues.

I'm facing just formatting issues in the following code snippet
`
ra = np.zeros_like(zeta, dtype=float)  # Preallocate memory

ra[zeta == 0] = (1 / (0.4 * ustar[zeta == 0])) * np.log(10.0 / z0)

ra[zeta > 0] = (1 / (0.4 * ustar[zeta > 0]))*(np.log(10.0/z0)

    + 4.7*(zeta[zeta > 0] - zeta0[zeta > 0]))

ra[zeta < 0] = (1 / (0.4 * ustar[zeta < 0])) * (np.log(10.0 / z0)

    + np.log((eta0[zeta < 0]**2 + 1) * (eta0[zeta < 0]+1)**2

    / ((eta[zeta < 0]**2 + 1) * (eta[zeta < 0]+1)**2))

    + 2*(np.arctan(eta[zeta < 0])-np.arctan(eta0[zeta < 0])))

`
Two error code:
W503 line break before binary operator and
E128 continuation line under-indented for visual indent

@nappaillav I've worked through the main function. It turned out to largely be a re-write, based on talking with my colleague Dan Riley about the model itself and the MATLAB implementation.  See the revision here.
Here's what's changed:

move the function to a new module losses.py and adjust the name. We're going to put all the loss models into losses.py for now.
expect inputs as pandas Series, which removes the Times argument.
use pandas for the time series manipulations (code became much simpler after Dan and I agreed on what it is/should be doing).
various adjustments to names for python conventions (lower case).

Dan strongly recommended implementing only the fixed settling velocity model (ModelType=2). In his work since publishing the MATLAB function, he (and the HSU folks) think it's the only reasonable choice among those three velocity models. I've removed the ModelType stuff but not the other two functions accum_array and depo_veloc which (I think) are no longer needed.
By using pandas.Series.rolling, we introduce a small deviation from the MATLAB code. In MATLAB, the time intervals with accumulated rain greater than the cleaning threshold are identified by looping through the rainfall time series, and labeling the beginning and end of each interval. The pandas.Series.rolling can extend the cleaning period past the end of each rain interval by a few time steps. Reading the HSU paper, the authors left much unsaid about identifying the cleaning interval so this code isn't inconsistent with their paper.
Let me know what you think, and update your pull request with the code you accept. I couldn't do a pull request to your fork, I thought that was possible but I guess I don't know git well enough to make it happen.


Review dependency licenses

I think the time has come where we need to review the licenses used in dependencies for Hypatia.
I'm primarily thinking about Pygame, here is the license, I'm worried there may be some incompatibility with the Hypatia license http://www.pygame.org/LGPL i try to read this but then I :sleepy:
I'd really like it if someone went through the licenses for our dependency and enumerated what's required of us for compliance. Some things to keep in mind:

Hypatia will always have a permissive MIT-style-license.
Hypatia will allow people to make commercial closed-source games

The big one is Pygame's license (LGPL-2.1). The website TL;DR Legal has a summary of the LGPL-2.1 license
Please report back with findings

From https://tldrlegal.com/license/gnu-lesser-general-public-license-v2.1-(lgpl-2.1) it seems we must figure out:

What exactly is sublicensing in this context, and how does it affect us, considering we want to use our LICENSE and allow people to, for example, distribute closed-source, commercial games on Steam
"You must either include the original source code or link clearly to a way to obtain it." Okay, so does this mean that Hypatia need only link to Pygame's website, or does this mean that anyone who uses Hypatia will also need to link to Pygame somewhere? "Clearly", how apparent does the link have to be?
"Include copyright: Describes whether the original copyright must be retained." Does this mean we need to keep the Pygame license handy somewhere in the repo? What implications does this have for commercial, closed-source game devs?
"Disclose source: If the software is statically linked (i.e. compiled into) your work, you must release object code or source code such that the user can modify the library. If otherwise (dynamically linked), you must make the source for the library available." God, does this mean that everyone who uses Hypatia/pygame must release their source code and that closed source isn't allowed, or this solely concerning Pygame as the library in question or...
"Include notice: Give prominent notice with each copy of your work that the LGPL'd software is being used. So we need to make the pygame license available and give "prominent notice" (WTF does that mean) that we're using Pygame?

Leaving the LGPL license aside, the other deps have similar stuff:
The BSD license (py-enum34) requires us to at least put the license somewhere (in docs and a credits thingy in the code, that's what Apple and Android do).
The PIL standard license (py-Pillow) says:
By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

Which is slightly different from the MIT license Hypatia uses. But it's the same thing, we put it in a credits section of the code and the docs, and we're fine.

Legal requirements aside, a "Credits" document is always a good idea anyway.

I was thinking more of like somewhere in an options menu in game there's a "credits" button that listed the licenses. But a credits document is good too.

Ah.  Yeah an in-game credits is a good idea too, and in some situations legally required---watch the ending credits for a modern video game sometime, which I know 99% of people skip if possible, heh.

I have no problem with helping promote the software we depend on. :) Just as long as it doesn't feel intrusive to the user.

Pygame needs the attention honestly.

Status update? I'll increase the bounty later.


Won't inject on MCS version

Script doesn't load into the game on Microsoft Store version of Roblox, please help.

It is because those exploits do not have support for the API functions this script is using to work. All of my products are made and tested with and only with Synapse X.


Pull request #1 from PythonNepal/source

@shitalluitel There doesn't seem to be anything here. Can you please look once again.

Thanks @shitalluitel. Can u maintain the ordering. Shital comes before Sudip


Headers not written for multipart messages

MultipartMessage takes responsibility for printing each Message's headers before their bodies, but there ought to be a way to write a MultipartMessage with its headers, too.  Well, in case it’s useful for someone :
You want to do io.Copy(os.Stdout, msg) (drop the .Body part).

Thanks! (I'm still using this library. :)


Community Meeting August 30, 2022

At 11am Eastern, 8am Pacific, 3pm UTC; find your time
Video call link: https://meet.google.com/mpd-cypd-sdp
Or dial: (DE) +49 30 300195060 PIN: 500<PHONE_NUMBER>#
More phone numbers: https://tel.meet/mpd-cypd-sdp?pin=5005991305702
Or join via SIP<EMAIL_ADDRESS>Meeting recordings available on YouTube at https://www.youtube.com/channel/UCfP_yS5uYix0ppSbm2ltS5Q
This issue will collect prospective agenda topics.
Incoming issues: https://github.com/kcp-dev/kcp/issues?q=is%3Aopen+is%3Aissue+-label%3Acommunity-meeting+no%3Amilestone
Milestone epics: https://github.com/kcp-dev/kcp/issues?q=is%3Aopen+is%3Aissue+label%3Amilestone-blocker+label%3Aepic

@adambkaplan do you want to talk about https://github.com/kcp-dev/kcp/issues/1847 at the meeting?

@varshaprasad96 do you want to mention details on https://github.com/kcp-dev/kcp/issues/1490#issuecomment-1230956599 in relation to 0.9 work?

@dinhxuanvu for catalog design overview https://kubernetes.slack.com/archives/C021U8WSAFK/p1661348947897289?thread_ts=1661284823.509559&cid=C021U8WSAFK

Proposal: two doc-days after tagging v0.8.

@stevekuznetsov request for feedback on client-go changes for cluster-aware clients: https://github.com/kcp-dev/apimachinery/pull/53

Catalog API: https://github.com/kcp-dev/catalog/pull/3

cluster-scoped quota #1846

Update on https://github.com/kcp-dev/kcp/issues/1490#issuecomment-1230956599

DNS Support https://github.com/kcp-dev/kcp/pull/1708


Example of use

Can you provide an example of a minimun application? Its not clear how to use the library.
Thanks!

Hi dear,
Provided an Example of Todo list application on the code sandbox.
I hope that helps you.
Feel free to ask if you have any questions.

Thank you so much!


fix: correct function name for B2CRequestAggregatedMeasureMessageReceiver

…

Description
References

Codecov Report

Merging #508 (dc53619) into main (21978a1) will decrease coverage by 40.89%.
Report is 187 commits behind head on main.
The diff coverage is 34.76%.

@@             Coverage Diff             @@
##             main     #508       +/-   ##
===========================================
- Coverage   83.07%   42.18%   -40.89%
===========================================
  Files         456      298      -158
  Lines       10418     5653     -4765
===========================================
- Hits         8655     2385     -6270
- Misses       1438     3190     +1752
+ Partials      325       78      -247

Files
Coverage Δ

source/Application/Actors/CreateActorHandler.cs
0.00% <ø> (-85.72%)
:arrow_down:

...tion/Configuration/Authentication/Authenticated.cs
0.00% <ø> (-100.00%)
:arrow_down:

...n/Configuration/Authentication/NotAuthenticated.cs
0.00% <ø> (-100.00%)
:arrow_down:

...n/Configuration/Commands/CommandSchedulerFacade.cs
0.00% <ø> (-100.00%)
:arrow_down:

...Configuration/Commands/Commands/InternalCommand.cs
0.00% <ø> (-100.00%)
:arrow_down:

...e/Application/Configuration/Queries/QueryResult.cs
0.00% <ø> (ø)

...lication/Configuration/TimeEvents/ADayHasPassed.cs
0.00% <ø> (-100.00%)
:arrow_down:

...Configuration/TimeEvents/TenSecondsHasHasPassed.cs
0.00% <ø> (-75.00%)
:arrow_down:

...tgoingMessages/Common/OutgoingMessageExtensions.cs
0.00% <ø> (ø)

...ion/OutgoingMessages/Common/Xml/DocumentDetails.cs
100.00% <ø> (ø)

... and 57 more

... and 425 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


embed official lbry tweet to this news blogpost

nice addition @ykris45 , I moved it a bit higher in the article.


discoverd: Deployment fixes

Fixes a linearizability bug caused by using GetMeta in concert with event stream that may be connected to a different server.

LGTM


Add secret-handshake

#48in24 exercise

Not sure how to resolve the markdown lint.  It seems to not like
~~~~exercism/note
If you aren't sure what binary is or how it works, check out [this binary tutorial][intro-to-binary].

[intro-to-binary]: https://medium.com/basecs/bits-bytes-building-with-binary-13cb4289aafa
~~~~

but that's an Exercism-specific piece of Markdown from upstream. Several other exercises have docs that use that markdown so this linter might be a problem.

Removed linting of autogenerated .md files, just merge the most recent changes
https://github.com/exercism/cairo/pull/144


[azservicebus] Fixing a bug where our management link would hang in certain circumstances

Fixing a bug where we could end up getting our management link stuck.
The problem was basically a combination of errors:

We were missing the sender settlement mode, which made it so we were only 1/2 in the "receive and delete" mode that we intended to be.
Ignoring that, our AcceptMessage() call was actually load bearing and critical and wasn't getting called in some cases, like if you cancelled the call.


Wireframe : Fan Journey

Overview
Wireframe out what a fan would see in the application.
Reference

Figma Link

Questions

List any questions?
That you are unsure of the answer?

Assumptions

Delivered in figma

Acceptance

A wireframe of the fan experience in the application

Tasks

[ ] A list of tasks that need
[ ] to be done to call this issue done

Closing now, opening new tasks:

Add Profile
Add Admin screen
Add buying panel
Test app on real users

@tjchmielewski


Deal with ENS names

This should work for kicking off profile page fetching but think we might prevent fetching in this case:
https://market-git-feature-accountpage-oceanprotocol.vercel.app/profile/officialoceandao.eth
As a generic solution, if an ETH address is attached to an ENS name, it should take over in all display which is an industry standard as per ENS design guidelines. So instead of 0xxx we show e.g. domain.eth in profile page, user wallet, publisher line. So all logic for showing wallet addresses in UI would be:
ENS name || ETH address

3box names are still valid for the main profile title with this logic:
 3box profile name || ENS name || ETH address

A good start: https://docs.ens.domains/dapp-developer-guide/resolving-names

Research findings

resolving name.eth → 0xxx is easy: `web3.eth.ens.getAddress(‘name.eth’)
this is where web3.js ends as it lacks proper support for using ENS names in place of addresses internally
also no way for reverse resolution which we need, so 0xxx → name.eth, they keep on auto closing https://github.com/ChainSafe/web3.js/issues/3749 without any actual fix
proper ENS support is only coming with that new v4 mega rewrite, see https://github.com/ChainSafe/web3.js/issues/4321

Conclusions

use ENS names purely visual, meaning internally we have to keep on sending ETH addresses to web3.js and ocean.js
most likely makes sense to keep accountId in our Web3Provider as the ETH address, and introduce a new ensName or something which gets filled when found
use ens.js for all ENS needs as that supports reverse resolution, still pending some tests on how big that library is and what dependencies it introduces

haha, not a good start, would be the largest library our market uses, bigger than web3.js. What is wrong with js developers?

Created 2 methods over in #860 and made sure both return exactly the same:
https://github.com/oceanprotocol/market/pull/860/files#diff-81b4b8fa07684c9a5f4f4d93fd28197274a5ad1e83b433d7b8de76c1c3e74709
Tending towards only using getEnsName() hitting the subgraph in all cases, although at least for user account display in menu bar the proper decentralized way would be to use web3 calls with getEnsNamewithWeb3() but given that we need the subgraph variant for the publisher line and profile pages of other accounts, seems overkill only using those huge ENS libraries only for this.

Or we can just try to see what that function does and implement it in the market, if it's reasonable.

I made almost everything work over in #860 regarding functionality, working nicely but of course we get lots of ens subgraph hits on frontpage as this is what the publisher line now does in addition to 3box. There still might be edge cases like multiple domains attached to one address where there might be differences between the direct web3 call & using subgraph for the user wallet display but can deal with this when real problem arises.
Last remaining use case is adjusting profile fetching logic a bit so that /profile/officialoceandao.eth works as a domain, but as web3.js does not properly support ENS names in place of ETH addresses we have to convert this back in background to ETH address and go from there. Oh, and typing generation but would like to keep this issue here for the conceptional part

Example for ENS name in publisher line:

Data Union profile is then good example as they have both, ENS & 3box:

Decided to only display ENS name in place of address, but keep using ETH address in the explorer links & copy action. Reason being that ENS names will work only on networks where ENS contracts are deployed which right now is only ETH networks, which is why https://etherscan.io/address/dataunion.eth would work, but https://polygonscan.com/address/dataunion.eth does not.

Aaaand covered final use case after some refactoring, essentially creating decentralized vanity URLs for publishers:

When I find an ENS name attached to an ETH address passed in the URL, then that will get replaced too so in UI the ENS names take over. Pretty neat so far and needs testing which we have as soon as that typing stuff is figured out

there we go, some preview example profiles:

https://market-git-feature-accountpageens-oceanprotocol.vercel.app/profile/dataunion.eth
https://market-git-feature-accountpageens-oceanprotocol.vercel.app/profile/cloutcontracts.eth


TableView via Storyboard?

When I add this to a tableview in loadView (or viewDidLoad) from a storyboard, the tableview disappears after pulling to refresh.  The code is called in the action block, but the tableview no longer is shown.  View Debugging doesn't show the tableview in the hierarchy.
Anyone else have this issue?
Version 7.1.1 (7B1005)

sorry, I see this is a duplicate issue.  https://github.com/gontovnik/DGElasticPullToRefresh/issues/1


Section default privacy input

related to #199, details at: https://github.com/globalmangrovewatch/gmw-users/issues/143#issuecomment-1179107573
Each section has a privacy setting, but the privacy input is taking its initial value from an input from site creation.

@julia-rom had a good suggestion/question about this. How does a user see/edit the default privacy setting after it has been set?
https://github.com/globalmangrovewatch/gmw-users/pull/261#issuecomment-1228818701

@julia-rom Users won't need to see/edit the default privacy setting again. It'll be a setting that is just set once when the site is created to set the privacy state of all the sections at once.
Because if they can see/edit the default privacy setting and if they edit it, what would that change? All the sections? Just the sections that haven't been changed? That gets complicated. I think after the initial state has been set when the site is created, the user can only change the privacy of each section on the section page.
Thoughts on this?

ok I just wasn't sure where/when the default privacy state was being set, that makes it clearer. I think it makes sense to set it when the site is being created, then be able to alter parts after. When you say section, do you mean an entire form section (Costs, for example), or individual questions? @alanjleonard

Each form section (e.g., Site Details and Location, Site Background, Restoration Aims, etc) has it's own privacy setting. Not individual questions.

ok cool!

When creating a site, add another dropdown with the label of "Default data visibility" and the options of "Public" and "Private". Default to "Public".

As described above, add a dropdown to each section for data privacy. This dropdown defaults to what the default data visibility was set to when the site was created.


bin: update dependency clap to version 4.0

This pull request updates dependency clap svd2rust binary from 2.0 to 4.0.
It has been years since clap has more user friendly interfaces and more rich ecosystem around it. In this version, we adpot to modern clap-verbosity-flag to describe a log level (not --log_level <LEVEL>, but -v, -vv etc., see https://docs.rs/clap-verbosity-flag). The default cases of command lines is changed to kebab-case in modern clap 4.0, other than snake_case in older versions. Other than that, no changes to command line parameters as well as their help messages are applied in this pull request.
The crate clap_conf is written back to 2021 and lacks people to maintain. It's not good to use it in frequently used embedded Rust toolchain, I rewrote it with a toml and serde based toml file parser to adapt to older version toml based toolchain configurations. If this feature should not be used in the future, we may remove this part of code.
The command line helper after this pull request:

No changes to library code is included in this pull request.
For reviewers: if this pull request would include any unacceptible breaking changes in command line, please note here and I will modify code in this pull request.

r? @reitermarkus
(rust-highfive has picked a reviewer for you, use r? to override)

see https://github.com/rust-embedded/svd2rust/pull/656 which does the same thing (regarding clap 4.0)

with #656 being non breaking, I think that's the solution we should go with
I would personally like to have the flags as both snake and camel case though

@Emilgardis I agree.


modified multiple images overlaid figure

Description
modified multiple images overlaid figure
Illustrates code in Readme better
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
https://github.com/napari/napari/issues/385
How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

you can achieve this effect by pressing Command+Shift+4, then Space, and clicking on the window

let me know if this image looks better!


feat(Input): 'autoWidth' prop

The problem
Input fields currently have only two types of sizing: fixed, and fluid. Either the textbox is a specified fixed width, or it automatically expands to become the width of its parent container.
The solution
An autoWidth prop, similar to the autoHeight prop on TextArea, what results in a behavior where as the text inside the input field grows, so does the input element, up until it reaches the width of the parent container (at which point it looks identical to the 'fluid' layout). This ensures that text inside the input is always visible (up until it is even longer than the parent container), which especially improves the user experience for transparent input elements.
Possible problem
I could imagine this opens a can of worms when it comes to things like Search that use input (it would need to expand/shrink whenever a result is selected), or other input, as well as resizing the box when the window resizes. Also opening this issue to see what people's opinion of this is.
Example

eww jQuery equivalent

Thank you for the request.  I'd like to leave this up to users to wrap the Input for now.  My reasoning is that this is not an SUI core feature and this is the first request we've had for it.  If we get more requests for this, I'll consider adding it to SUIR.

Hmm, maybe it makes sense to open up an issue there. Thanks for the feedback!

+1

We don't going to implement this. Similar functionality from TextArea was removed in the previous release.


opsctl deploy

Towards: https://github.com/giantswarm/roadmap/issues/453

Would maybe make sense to also install some actual test here now

Would

Don't hurry boy, we are trying to get PMO deployed first. Baby steps

LMK when this is ready to review :)

$ k logs -f eff0520f-17a8-11ec-bb04-b613c42b326b-deploy-898n8-pod-ffk6f
Requesting the creation of deployment using App method
Disabling self-healing on the Argo application "prometheus-meta-operator"

Error: Applications.argoproj.io "prometheus-meta-operator" is forbidden: User "system:serviceaccount:giantswarm:test-infra" cannot patch resource "applications" in API group "argoproj.io" in the namespace "argocd"
        /root/project/pkg/cmd/deploy/appdeploy/deployer.go:375
        /root/project/command/deploy/command.go:310
        /go/pkg/mod/github.com/giantswarm/backoff@v0.2.0/retry.go:23
        /root/project/command/deploy/command.go:321
        /root/project/command/deploy/command.go:144
        /root/project/main.go:51

To increase verbosity, re-run with --level=debug

Works

$ k --context giantswarm-rfjh2 logs -f 63ddcb66-21d4-11ec-bb04-b613c42b326b-deploy-mq57w-pod-5gmhp
Requesting the creation of deployment using App method
Disabling self-healing on the Argo application "prometheus-meta-operator"

Patching version in unique App CR "giantswarm/prometheus-meta-operator"
Patched version in unique App CR "giantswarm/prometheus-meta-operator"

    chart           prometheus-meta-operator
    repository      prometheus-meta-operator
    ref             v1.51.1
    version         1.51.1
    installation

Requested the creation of deployment using App method

Waiting for deployment
Success!

$ kg --context giantswarm-gaia get app prometheus-meta-operator
NAME                       VERSION   LAST DEPLOYED   STATUS
prometheus-meta-operator   1.51.1    19d             deployed

cc/ @MarcelMue I'm happy to here about your review. This is still a first step, I need to do proper cleanup on the pipeline level (using finally).

That looks interesting but I'm not Marcel so I will let him review once he is back :D

Happy to get you review and other too.


InstagramSearchUsersRequest

hi
how can use InstagramSearchUsersRequest ?

InstagramSearchUsernameResult result = instagram.sendRequest(new InstagramSearchUsernameRequest("example_username"));
InstagramUser user = result.getUser();
Use try catch with this example.

no no
i need get list users
for example get list of users whose users start with h

This is not possible with this library yet. You can do your private api with php or etc..

you need save list in sqlite then you can search it.

no no
i need get list users
for example get list of users whose users start with h

Can I search user by id, not username?


Client::pull returns layers in non-deterministic order

The code for Client::pull uses buffer_unordered under the hood (see here). Because of this, layers are stored in arbitrary order in ImageData::layers. Unfortunately, this makes it impossible to know which layer from ImageData::layers corresponds to which entry in OciImageManifest::layers, unless you recalculate the hash (which seems like a waste of resources).
IMO we should either store the layers in ImageData::layers in their original order, or provide a mechanism to cheaply correlate them to the layers in OciImageManifest::layers (e.g. including an index number).

I actually saw this the other day when I was modifying something else and wondered if it would be a problem. Thanks for filing the issue!


[SCB-651] Fixes bug of qps rate limit value

Added the logic for the first cycle of qps controller so that the number of requests allowed per second equals to its limit value.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.02%) to 87.377% when pulling 2f4912fa7a05234c4ef864df3a0735de3c561c39 on limbojinne:patch-1 into b81196f6eedf220dfb87b77b3a548cd201a7f3ac on apache:master.