Refactor config rule by taking inspiration on Prometheus alerting rule

I think we need to analyze Prometheus Alerting rule template and take inspiration.
The goal is be a bit closer to what the ecosystem already provide (so people are not lost if they use Loki Ruler or Prometheus alerting).

expr instead of logql
for for duration interval?
annotations with summary and description

The optional for clause causes Prometheus to wait for a certain duration between first encountering a new expression output vector element and counting an alert as firing for this element. In this case, Prometheus will check that the alert continues to be active during each evaluation for 10 minutes before firing the alert. Elements that are active, but not firing yet, are in the pending state. Alerting rules without the for clause will become active on the first evaluation.

It looks confusing to use for as duration/cron interval since the behavior is different. WDYT?
annotations.summary could replace name and we could add a annotations.description so it can be used in the template, but the behavior is slightly different because with Prometheus alerting rule these fields can be templated with logs labels (i.e app) while on our side this is not possible as we use the name/annotation.summary as an identifier in the database and for logging.
Even the expr is not very accurate to me because Prometheus (PromQL) is indeed based on expressions:

Alerting rules allow you to define alert conditions based on Prometheus expression language expressions and to send notifications about firing alerts to an external service.

But Loki (LogQL) is based on queries, it can be confusing as expr could mean "label filter expression" and/or "line filter expression" (etc): we don't want an expression but a full LogQL query based on multiple expressions instead. It look like if we set expr instead of logql we become closer to Prometheus but farest to Loki (at least this is my feeling).
So, i'm not sure about theses but if it's ok for you, it's ok for me 😃

Templating can also be inspired:
{{ $labels.<labelname> }}

labels instead of label + double brace instead of simple brace ? So we are ISO with Prometheus.
There are some fields we could get inspired but the problem is that they use snake_case while we use camelCase:
group_wait: 0s
group_interval: 1m
repeat_interval: 1h

Maybe there is something to do getting inspiration from theses fields
inhibit_rule is also interesting

errorFilters should be errorIgnorePatterns (or something like that)

Throttle, use releaseThreshold instead of count ?
CompositeRules, use threshold.rules & threshold.alerts objects ?
{
  "compositeRules": {
    "threshold": {
      "rules": {
        "trigerredCount": 5,
        ...
      },
      "alerts": {
        "count": 20
      }
    }
  }


About jacobi

Hi, I can't figure out the derivative formula used in the file of costFunction.hpp, can you give me some references about this,especially for formula 8) in the paper?

Hi @rlczddl , I derived most of it by hand, equation 8 is defined there: https://github.com/rFalque/embedded_deformation/blob/63ea6e0960d4beb96a0e0528705b91dafd14bed3/embedded_deformation/include/embedded_deformation/costFunction.hpp#L530
If you want to implement your own cost function, I highly recommend you the autodiff from CERES, it works really well. The time difference with a provided jacobian is marginal in many situations.

Thanks for your answer. I also successfully derived the jacobian matrix by hand. The residual term of this algorithm is relatively simple and easy to deduce and I would like to ask if there is any skill in deriving jacobian matrix for complex residual terms?

I like that website http://www.matrixcalculus.org/. You can export code in python and kind of translate it for Eigen.
Otherwise, Matlab and Python have tools for doing so. Still, I highly recommend you to give a try to this http://ceres-solver.org/automatic_derivatives.html ;)

Thank you again. I'll get to know what you said.


[cosmetic-suggestion] increase elevation profile legibility by adding a border line

It's hard to understand the elevation profile when yellow (dirt terrain) is over greyish white (background);
I suggest to "highlight" the elevation profile by adding a borderline (this is just an idea about to overcome the issue...);
here is a simple mockup:
now:

tweaked:

Thank you for your suggestion, I have re-implemented the website from scratch and added that to the future version.
You can check it out here: https://gpx.studio/gpx.studio/ and provide feedback on this new repository: https://github.com/gpxstudio/gpx.studio.

@vcoppe Great job! It's a good enhancement.
Let's close this report.


add profile image to plugin posts

Fixes #4

@jasonblais
1 - Nice catch! I made the image smaller to be inside the profile image boundary. Now it looks like this:

2 - I changed the appearance to be consistent with the profile image. I asked the brand team about the icon in the channel header. They told that this is ok. But I've just realized that I showed them a screenshot of that icon when it is in the dropdown, with a label, like this:

And it may be a different case when the icon is alone, without any label:

Do you think it could violate the guidelines?

@kosgrz What if we used the same channel header icon as is used for Zoom? It's a generic video icon so would apply to any audio/video plugins
https://github.com/mattermost/mattermost-plugin-zoom

@jasonblais good idea! I changed the icon to the video icon used in the Zoom plugin. Some screenshots:


[Feature Request] Support for MacOS

Including Intel based and M1/M2 based versions.

availability in homebrew would likely help with uptake


Bump upper bounds of package dependencies.

This PR makes the following adjustments to upper bounds of dependencies:
-   , containers  >=<IP_ADDRESS> && <0.7
+   , containers  >=<IP_ADDRESS> && <0.8

-   , QuickCheck  >=2.14.1  && <2.14.4
+   , QuickCheck  >=2.14.1  && <2.16

Tested with:
cabal test all --constraint=containers==0.7 --constraint=QuickCheck==2.15

Fixes #92.

Related issues:
https://github.com/haskellari/qc-instances/issues/92
https://github.com/haskellari/qc-instances/issues/94


/external/org_tensorflow/third_party/py/python_configure.bzl", line 210, column 33, in _create_local_python_repository

Win10
1.D:\out\mediapipe>python
Python 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

workspace(name = "mediapipe")
android_sdk_repository(name = "androidsdk",
build_tools_version = "30.0.3")
android_ndk_repository(name = "androidndk")
ndk=r21e

D:\out\mediapipe>bazel --version
bazel 5.0.0

D:\out\mediapipe>bazel build -c opt --config=android_arm64 mediapipe/examples/android/src/java/com/google/mediapipe/apps/hairsegmentationgpu
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Repository local_execution_config_python instantiated at:
D:/out/mediapipe/WORKSPACE:404:14: in
C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/tensorflow/workspace2.bzl:876:19: in workspace
C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/tensorflow/workspace2.bzl:89:27: in _tf_toolchains
C:/users/admin/_bazel_admin/kldacohl/external/tf_toolchains/toolchains/remote_config/configs.bzl:6:28: in initialize_rbe_configs
C:/users/admin/_bazel_admin/kldacohl/external/tf_toolchains/toolchains/remote_config/rbe_config.bzl:158:27: in _tensorflow_local_config
Repository rule local_python_configure defined at:
C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/py/python_configure.bzl:276:41: in
ERROR: An error occurred during the fetch of repository 'local_execution_config_python':
Traceback (most recent call last):
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/py/python_configure.bzl", line 210, column 33, in _create_local_python_repository
python_lib = _get_python_lib(repository_ctx, python_bin)
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/py/python_configure.bzl", line 130, column 21, in _get_python_lib
result = execute(repository_ctx, [python_bin, "-c", cmd])
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/remote_config/common.bzl", line 230, column 13, in execute
fail(
Error in fail: Repository command failed
ERROR: D:/out/mediapipe/WORKSPACE:404:14: fetching local_python_configure rule //external:local_execution_config_python: Traceback (most recent call last):
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/py/python_configure.bzl", line 210, column 33, in _create_local_python_repository
python_lib = _get_python_lib(repository_ctx, python_bin)
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/py/python_configure.bzl", line 130, column 21, in _get_python_lib
result = execute(repository_ctx, [python_bin, "-c", cmd])
File "C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/remote_config/common.bzl", line 230, column 13, in execute
fail(
Error in fail: Repository command failed
ERROR: Analysis of target '//mediapipe/examples/android/src/java/com/google/mediapipe/apps/hairsegmentationgpu:hairsegmentationgpu' failed; build aborted: Repository command failed
INFO: Elapsed time: 6.337s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 0 targets configured)
D:\out\mediapipe>

helloworld
D:\out\mediapipe>bazel build -c opt --config=android_arm64  --action_env PYTHON_BIN_PATH=C:/Users/ADMIN/AppData/Local/Programs/Python/Python37/python.exe //mediapipe/examples/android/src/java/com/google/mediapipe/apps/basic:helloworld
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: C:/users/admin/_bazel_admin/kldacohl/external/org_tensorflow/third_party/repo.bzl:122:14:
Warning: skipping import of repository 'pybind11' because it already exists.
WARNING: D:/out/mediapipe/mediapipe/framework/BUILD:54:24: in cc_library rule //mediapipe/framework:calculator_cc_proto: target '//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: D:/out/mediapipe/mediapipe/framework/tool/BUILD:182:24: in cc_library rule //mediapipe/framework/tool:field_data_cc_proto: target '//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
INFO: Analyzed target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/basic:helloworld (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: D:/out/mediapipe/mediapipe/gpu/BUILD:383:27: Compiling mediapipe/gpu/gl_context_options.pb.cc failed: (Exit 1): clang failed: error executing command external\androidndk\ndk\toolchains\llvm\prebuilt\windows-x86_64\bin\clang -gcc-toolchain external/androidndk/ndk/toolchains/aarch64-linux-android-4.9/prebuilt/windows-x86_64 -target ... (remaining 57 arguments skipped)
clang: error: no such file or directory: '/w'
clang: error: no such file or directory: '/D_USE_MATH_DEFINES'
clang: error: no such file or directory: '/std:c++17'
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/basic:helloworld failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1.981s, Critical Path: 0.95s
INFO: 128 processes: 128 internal.
FAILED: Build did NOT complete successfully

D:\out\mediapipe>


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.16.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cebb0aceb21ad91429617a40e3a17444fabf1529"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "cebb0aceb21ad91429617a40e3a17444fabf1529",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "mm/kmemleak: avoid scanning potential huge holes\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.8 by commit cebb0aceb21ad91429617a40e3a17444fabf1529. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000660


Visualize non boost geometry types

From the documentation, it looks like this tool works for boost geometry types. I wondering if we can get this to visualize custom geometry types. At the moment, I am working with AlignedBox from Eigen Geometry library. Any suggestions about visualizing this would be greatly appreciated.

Yes, you can: https://github.com/awulkiew/graphical-debugging-vscode#user-defined-types

I haven't used eigen but AFAIU you'd have to  define AlignedBox as a box with m_min and m_max points
https://github.com/libigl/eigen/blob/master/Eigen/src/Geometry/AlignedBox.h#L307
similar to Boost.Geometry box:
https://github.com/awulkiew/graphical-debugging-vscode/blob/master/resources/boost.json#L196-L203
after defining VectorType used for m_min and m_max as point:
https://github.com/libigl/eigen/blob/master/Eigen/src/Geometry/AlignedBox.h#L40
similar to Boost.Geometry point:
https://github.com/awulkiew/graphical-debugging-vscode/blob/master/resources/boost.json#L35-L42
Alternatively you could define AlignedBox using 4 coordinates extracted from matrices/vectors like it is done for Boost.Polygon rectangle_data:
https://github.com/awulkiew/graphical-debugging-vscode/blob/master/resources/boost.json#L35-L42
If you had problems let me know.


[Bug]: [Go SDK]: State API writes may become corrupted with Go 1.23

What happened?
When using the Beam State API in the Go SDK, it's possible that data may become corrupted when performing a Write.
A change to the Go compiler for Go 1.23+ made the issue more frequent/severe/reproducible.
It is not recommended to use Go 1.23+ for Beam Go pipelines using the State API until this issue is resolved. If your job doesn't use the State API, then it is unaffected.
It's not known if the behavior can cause a similar issue elsewhere in the SDK at this time. Other calls such as writing data to data sinks are first written to a buffer, or properly copied to a buffer, avoiding the same problem, or at least rendering it less likely.

In particular, the data written to the state API, might become overwritten or zeroed out before actually being sent over the GRPC channel, corrupting the write. Consider a length prefix byte that is zeroed, or changed prior to being sent to the runner.

The root cause of the issue is that Beam Go is incorrectly implementing go's https://pkg.go.dev/io#Writer interface for writing to State calls. In particular, it's incorrectly retaining a reference to the input byte buffer, passed into the write call.
https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/runtime/harness/statemgr.go#L481
The buffer is simply passed to the FnAPI StateAPI write request, then being sent to another channel for actually sending it on the State channel.
https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/runtime/harness/statemgr.go#L498
This send happens asynchronously, sending it to a different goroutine for serialization.
https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/runtime/harness/statemgr.go#L704
While this is ultimately a blocking call, the other half is due to Beam Go lightly subverting Go's escape analysis in the name of performance, using ioutilx.WriteUnsafe.
eg used here. https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/core/graph/coder/varint.go#L44
This was deemed required for performance for small writes in order to avoid usually unnecessary
allocations to the heap. Typically these allocations would be stack allocated, and then not re-used.
However in Go 1.23 a change to the compiler "can now overlap stack frame slots of local variables". It's my suspicion that this allowed the stack frame referred to to by the byte buffer to be zeroed out or re-assigned, corrupting the data.

The fix is to copy the bytes properly when sending them over the state API. This avoids the bytes being changed prior to being sent.
A more robust fix would be to re-write coder handling entirely, to avoid using the io.Reader and io.Writer interfaces, which opened up the issue in the first place.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[X] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Infrastructure
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Not sure why the change didn't auto close this.


hpc-coveralls-1.0.3 (LTS 5.10) test suite failure

Citing from http://hydra.cryp.to/build/1675284/log/raw:
Linking dist/build/test-all/test-all ...
/tmp/nix-build-hpc-coveralls-1.0.3.drv-0/hpc-coveralls-1.0.3/dist/build/libHShpc-coveralls-1.0.3-5ZrCpZMz8K72HaPPcLeoRd-ghc7.10.3.so: undefined reference to `hpccozu5ZZrCpZZMzz8K72HaPPcLeoRd_Pathszuhpczucoveralls_version1_closure'
collect2: error: ld returned 1 exit status

Could this error be related to the fact that we build those packages with shared linking enabled?
Cc: @snoyberg

Pinging @guillaume-nargeot

I can't seem to reproduce the error, but I have a hunch what might be causing it. The symbol name hpccozu5ZZrCpZZMzz8K72HaPPcLeoRd_Pathszuhpczucoveralls_version1_closure leads me to believe that a module is depending on something from Paths_hpc_coveralls, but Paths_hpc_coveralls isn't listed in the other-modules stanza of hpc-coveralls.cabal.

We compile with --enable-split-objs. Maybe that makes a difference?

I dug more into the Nix build output, and it turns out the culprit is the --enable-executable-dynamic flag. Without it, I can compile the tests just fine on GHC 7.10.3, but with it I get the linker error mentioned in https://github.com/fpco/stackage/issues/1338#issue-145624417.
And now that I actually look at the hpc-coveralls GitHub issues, this has already been discovered before. Oh well, the fix is pretty simple: https://github.com/guillaume-nargeot/hpc-coveralls/pull/59

hpc-coveralls-1.0.6 is on Hackage now, which incorporates the fix for this issue. I can now successfully build it with either cabal configure --enable-executable-dynamic && cabal build or stack build --ghc-options=-dynamic. (I'm not sure if stack has an equivalent to --enable-executable-dynamic, but I think --ghc-options=-dynamic achieves the same thing.)

This should be resolved then, so I'll close this.


Weekly Survey Metrics Report Revamp

We would like to revamp the Weekly Survey Metrics Report now that we have completed the Ops Report and have added more metrics to the report for recently released surveys. Please see below. This is a lower priority request, higher priority items should take precedent.
General Report Flow Updates

[x] 1. Retitle report as: Connect Weekly Survey Module Metrics

[x] 2. Add table of contents to report and separate metrics into sections (similar to how Ops Report is presented now).
-Suggested categories: Baseline Survey, SSN Survey, Menstrual Cycle Survey, Quality of Life Survey, Connect Experience Survey, Survey Metrics by Language Completed
-Tables and Figures should also be renumbered to go with the section it is in

[x] 3. Add 'general information' summary to report.
Suggested summary language: This Weekly Survey Module report contains metrics related to Connect survey completion including baseline surveys and follow up surveys. Additional metrics will be added as new surveys are released. Metrics related to the biospecimen surveys can be found in the Weekly Survey Metrics. Metrics related to overall baseline study activity completion, including baseline survey completion, can be found in the Weekly Operations Report. [add info about analytic data set?] The Survey Module report is run on a weekly basis and encompasses data through [add info from data run].

[x] 4. For 'Survey Metrics by Language Completed', at beginning of section please add note about when Spanish was added.
Note: Spanish was made available in MyConnect beginning August 1, 2024.

Updates to current metrics

[x] 5. Table 10. Portion of SSN Given by Submission Status of SSN Survey
-Add' Among Verified Participants' to end of table title
-Label 'Total' column and row as 'Total Verified'
-Make 'Total' column a column percent

[x] 6. Add column percent to Table 12. Completion of 3-Month Quality of Life Survey by Baseline Data Complete

[x] 7. Add footnote to table 13: 3-Month Quality of Life Survey Completion Rate by Site Defined Sex Among Eligible Participants
Footnote: Sex defined as the de-identified sex data reported by sites at time of invitation.

[x] 8. Add footnote to table 14: -Month Quality of Life Survey Completion Rate by Age Among Eligible Participants
Footnote: Age defined as the de-identified age data reported by sites at time of invitation, not current age at time of survey completion.

[x] 9. Spelling error in 'Table' title for Table 17. 3-Month Quality of Life Survey Completion Rate by Demographic Among Eligible Participants

[x] 10. Table 18. 3-Month Quality of Life Survey Completion Time from Start to Submit Among Eligible Participants
-Percentages don't add up to 100%. Can you please look into this? Should be out of the ~19,000 that submitted the QOL survey.
-Please add to end of table title 'That Submitted the Survey'
-Please change 'total' row label to 'Total Submitted QOL Survey'
-Please add cumulative percent column to the right (similar to Table 6.1-6.4)

[x] 11. Please add footnote to Table 20. Preferred Language by Site
Footnote: Preferred language is based on language of signed consent form and current user profile language status'

[x] 12. Add Connect Experience Survey to tables 22, 22a, and 22b for Survey completion by survey language. Can abbreviate the survey to 'CES' and place after 'QOL'.

New Metrics to Be Added

[x] 14. Please add similar tables to Table 13-16 (QOL survey completion by age, race, sex) but for the Initial Survey.
-All 3 tables (including race) can be pulled from the de-identified site reported demographic variables.
-Instead of 'not started, started', submitted', please use these categories: 'All, 2 or 3 sections, BOH only, None' (from table 4.1 in Ops Report).

[x] 15. Add a new categorical table for QOL survey completion stratified by time from verification to survey release among both prospective and backlog participants (one table total)
-Metric title: QOL Survey Completion By Time from Verification to Survey Release
-Survey completion categories should be 'Not Started', 'Started', 'Submitted'.
-Time from Verification to Survey Release should be: 'More than 1 Year' (~July 2021-Dec 2022), '6 Months - 1 Year' (~Jan 2023-June 2023), '3 Months - 6 Months' (~July 2023-Dec 2023), 'At 3 Months' (anyone prospective)

[x] 16. Add a new metric that looks at among those who completed the QOL survey, how many people went back in to complete their baseline surveys on the day of or after completing the QOL survey (some of this data was looked at when pulling the extra duplicate report data for Michelle). Should be stratified by each baseline survey section and the biospecimen surveys.
-Metric title: Baseline Survey Completion On Day of or After QOL Survey Completion

[x] 17. Repeat request 16 but for the Connect Experience Survey

Hi Amelia, thanks for making this checklist! It makes it MUCH easier to keep track of everything. I had some down time and these were all pretty quick changes.
Please let me know if I misinterpreted any of the new requests. I made the assumption that number 14 should only be out of those who completed CES, and that the rows in number 15 should be those verified at those dates: 'More than 1 Year' (~July 2021-Dec 2022), '6 Months - 1 Year' (~Jan 2023-June 2023), '3 Months - 6 Months' (~July 2023-Dec 2023), 'At 3 Months' (anyone prospective). Also we already had a short intro just to explain the module acronyms. Please let me know if you want that kept, removed, or moved. A good alternative spot might be under the "Baseline Survey" header.
CCC-Weekly-Module-Metrics_RMD.pdf

Hi @KELSEYDOWLING7 yay! I had noticed you made the checkmarks on a recent github issue so thought it might be easier to do the same thing here! And wow, that was fast! This is looking great - I just have a few small edits:

[ ] 1. Short intro just to explain the module acronyms - Agree, lets move that portion of the intro to the baseline survey section!

[ ] 2. Table of Contents - Sections themselves look good. Just need to add a table of contents page at the top where when you click the section in the TOC it jumps to that section (similar to Ops Report)

[ ] 3. Table 4.2-4.2b on baseline data completeness - can you please change the order of the categories so 'both survey and samples' is at the top and 'neither' is at bottom so it goes in order from most to least completed? (similar to how we changed it for table 5.2 for the CES). Sorry I didn't catch this earlier

[ ] 4. For the initial request 14 to add age, race, sex tables for the Initial Survey - sorry for the confusion! This should be among 'all verified participants' (not only those who completed CES). For your tables I think the only things that need to change are:
-Make the total out of Verified Participants and change the total labels to reflect that
-Change title to: 'Initial Survey Completion Rate by Site Defined Sex/Age/Race Among Verified Participants'
-Make total column a column percent, but leave other cells as row percents
-Move the 3 tables to the baseline survey section

[ ] 5. Table 4.10 QOL Survey Completion By Time from Verification to Survey Release - this looks good! Just a few minor tweaks:
-For the title and category label row can you make it 'Time from QOL Survey Release' to clarify it's the QOL survey and not initial survey release time?
-Can you leave the row percents as is, but make the total column a column percent please?

[ ] 6. Table 4.11 Baseline Survey Completion on Day of or After QOL Survey Completion - this also looks good! To shorten the category labels could change 'Completion Time' label to 'Survey Completed After QOL' and then list the surveys below (e.g. BOH, MRE, SAS, ...., None etc)

[ ] 7. Table 5.8 Baseline Survey Completion on Day of or After CES Survey Completion - suggest making the same changes to Table 5.8 for CES

Good morning, few questions/comments. Table 5.8 already has the abbreviations for CES so I believe we should be good there. Then, I'm a bit confused at what the new title should be for 4.10. Can you clarify specifically what you'd like the title and category row label to be?

Good morning @KELSEYDOWLING7!
For table 5.8 - it should have the same changes applied in number 6/table 4.11 where the category row label would state 'Survey Completed After CES' and then the survey labels in the rows are shortened to just refer to the survey itself and drop 'completed after CES' in each label
For Table 4.10 -
Just need to add another 'QOL' into the title and label so
Title: QOL Survey Completion By Time from Verification to QOL Survey Release
Row label: Time from Verification to QOL Survey Release

Sorry, maybe I'm missing something? I think 5.8 already has all that:

CCC-Weekly-Module-Metrics_RMD.pdf

Hi @KELSEYDOWLING7 I was envisioning something more like below for Table 4.11 and 5.8. What do you think? That way the 'completed after QOL/CES' doesn't have to be repeated in each row.

Table   4.11. Baseline Survey Completion On Day of or After QOL Survey Completion |
-- | --
Survey   Completed After QOL | N(%)
BOH | N(%)
MRE | N(%)
SAS | N(%)
LAW | N(%)
BUM | N(%)
BU | N(%)
MW | N(%)
COVID | N(%)
None | N(%)
Total   Submitted QOL Survey | N(%)

Forgot to add, I still need to review the changes to the rest of the report which I will do shortly!

Sure thing, do we have that date anywhere?

Yes, July 5th, 2022 is when all 4 sections were available in prod

How does this sound:
Starting July 5th, 2022, all four Initial Survey Modules were in MyConnect. In order of how the sections appear on MyConnect, the Initial Survey Sections are:
BOH= Background and Overall Health (Module 1)
LAW= Where you Live and Work (Module 4)
MRE= Medications, Reproductive Health, Exercise, and Sleep (Module 2)
SAS= Smoking, Alcohol, and Sun Exposure (Module 3)

@KELSEYDOWLING7 yes, I think that sounds perfect!

Hi @KELSEYDOWLING7 final suggested edits hopefully!

[ ] Table 1.9-1.11 - titles still mention CES survey. Should only reference the initial survey and footnotes added back in.
-Can you change titles to 'Initial Survey Completion Rate by Site Defined Sex/Age/Race Among Verified Participants'
-Can you also add in the same footnote as the other age/race/sex:
Footnote for sex: Sex defined as the de-identified sex data reported by sites at time of invitation.
Footnote for race: Race defined as the de-identified race data reported by sites at time of invitation.
Footnote for age:  Age defined as the de-identified age data reported by sites at time of invitation, not current age at time of survey completion.

[ ] Move menstrual cycle survey metric(s) from Weekly Survey Report to Weekly Biospecimen Report - after discussion with biospecimen team, think it makes more sense to delete this from the Survey Report and instead move it to the Biospecimen Report because the menstrual cycle survey is dependent upon the answers and data from the biospecimen survey which those metrics are found in the Biospecimen Report. @erincschwartz can suggest where to add this on the Wkly Biospec Report. The entire section for the menstrual cycle can be deleted from the Survey Report.

[ ] Update general summary to note menstrual cycle survey and COVID survey metrics can also be found in the Weekly Biospecimen Report.
-Suggest revising 3rd sentence in summary to: Metrics related to the baseline biospecimen surveys, menstrual cycle survey, and COVID survey can be found in the Weekly Biospecimen Metrics reports.

[ ] Update baseline survey summary as outlined in comment above

[ ] Table 4.11 and 5.8 updates discussed above

So do we want to remove the mention of the Menstrual cycle survey from these tables as well? The other biospecimen surveys (BU, BUM, and COVID) are on there too. Should those be removed?

If not, please see below:
CCC-Weekly-Module-Metrics_RMD.pdf

@KELSEYDOWLING7 no, I would leave the mention of the menstrual cycle and covid surveys in those metrics but for the one metric that is specific to menstrual cycle only that one can be moved to the biospec weekly report

Got it, ok that table/section was removed in that last version I just posted

Thanks @KELSEYDOWLING7 I just reviewed the latest version and it looks great! The footnotes need to be added in to the age/race/sex tables 1.9-1.11. After that, this looks perfect and is ready for prod on Monday!

Oh weird! The footnotes were all in the code but weren't rendering. That's resolved now, please let me know if we're good to close the issue. We're also updating the report automation this afternoon for Monday.
CCC-Weekly-Module-Metrics_RMD.pdf

@robertsamm  As of yesterdays report, is this good to close?


import error when editing tailwind.css

I wanted to create a new nuxt (2.12.1) project, with tailwind, either
(1) with the create-nuxt-app
(2) with installing tailwind module with npm after choosing None during initial use of create-nuxt-app and following the set up instructions in the readme.
Then, when I add anything to the initial tailwind.css
@import "tailwindcss/base";

body {
  @apply bg-black;
  // or:
  //  background-color: black;
}

@import "tailwindcss/components";
@import "tailwindcss/utilities";

I will get two warnings:
Module Warning (from ./node_modules/postcss-loader/src/index.js):     friendly-errors 15:01:12
Warning

(10:1) @import must precede all other statements (besides @charset)
                                                                      friendly-errors 15:01:12
 @ ./assets/css/tailwind.css 4:14-166 14:3-18:5 15:22-174
 @ ./.nuxt/App.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js

and
Module Warning (from ./node_modules/postcss-loader/src/index.js):     friendly-errors 15:01:12
Warning

(8:1) @import must precede all other statements (besides @charset)
                                                                      friendly-errors 15:01:12
 @ ./assets/css/tailwind.css 4:14-166 14:3-18:5 15:22-174
 @ ./.nuxt/App.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js
                                                                      friendly-errors 15:01:12

Whereas the styling works as expected, I would expect there to be no warnings.

Well honestly this warning is legit and at the same time is fails for loading the rest of the file.
I recommend to have a main.css file that you import, see https://codesandbox.io/s/nuxt-tailwindcss-bsq8w

Thank you. This does indeed fix the warning.


Can not compile it with VS2017 Debug option

Hi，I can not build this project with DEBUG option, I am using VS2017.

Hey,
Actually I've made a decision to remove the debug build configuration from the main project because it was simply too slow. I didn't find it useful and as such I didn't want to maintain it.
Even in release mode basic breakpoints can provide some basic insight (though not all data is available there).
I think that it shouldn't be too much work to recreate the debug configuration based on the release configuration.

Hi Tomasz,
You are doing a great job!
I built the DEBUG configuration just for learnning. I am using VS2017 and OpenCV 4.01.
 1. If I add a preprocessor 'OPENCV_TRAITS_ENABLE_DEPRECATED', the DEBUG configuration can be compiled normally. otherwise, Some errors will be generated in the follow function:
     template<typename _Tp> inline
    _Tp& Mat::at(int i0, int i1)
   {
         CV_DbgAssert(dims <= 2);
         CV_DbgAssert(data);
         CV_DbgAssert((unsigned)i0 < (unsigned)size.p[0]);
         CV_DbgAssert((unsigned)(i1 * DataType<_Tp>::channels) < (unsigned)(size.p[1] * channels()));
         CV_DbgAssert(CV_ELEM_SIZE1(traits::Depth<_Tp>::value) == elemSize1());
         return ((_Tp*)(data + step.p[0] * i0))[i1];
    }
    The error is: Error C2039 'channels': is not a member of 'cv::DataType<_Tp>' .
 2. After I added the preprocessor 'OPENCV_TRAITS_ENABLE_DEPRECATED', I built the project and run it with  '-type features' param successfully, and so as the two Python scripts.
     But, When run it with '-type example' param, the under line will throw a exception:
      **CV_DbgAssert(CV_ELEM_SIZE1(traits::Depth<_Tp>::value) == elemSize1());**
     Should I  bypass this exception?
     Thanks a lot.

The calling stack is :
cv::Mat::at<FaceLandmarking::Math::Vector >(int i0, int i1)
FaceLandmarking::Regression::MaskRegressorBuffer::setValue(int x, int y, FaceLandmarking::Math::Vector offset)
FaceLandmarking::Regression::MaskRegressor<194>::computeOffset(const FaceLandmarking::FeatureExtraction::HsvImage & image, FaceLandmarking::Math::Point point, unsigned __int64 pointNumber, unsigned __int64 iterations)
FaceLandmarking::FaceLandmarker<194>::adjustMasks(const cv::Mat & frame, FaceLandmarking::Mask::FaceMask<194> & mask, int steps, int iterations)
FaceLandmarking::FaceLandmarker<194>::adjustMasks(const cv::Mat & frame, int steps, int iterators)
FaceLandmarking::App::example<194>(std::experimental::filesystem::v1::path dataPath)

I'm also using VS 2017, bun an older version of OpenCV 3.3.1 (as I've started working on this project quite some time ago).
But I'm not sure if it's actually a version related problem.
It seems that be default OpneCV supports processing of it's built in types only. And I'm storing in the matrix object of my own class Math::Vector<float>, which doesn't have required traits.
Here is an openCV thread regarding this problem: https://stackoverflow.com/questions/7195649/opencv-matrix-of-user-defined-type
Does this project work for you in the release mode with the -example flag?

Hi,Tomasz
Yes! The project can work.
And I added a little function to OpenCV:
template inline
_Tp& Mat::myat(int i0, int i1)
This function just remove the 'CV_DbgAssert' lines.
Now I don't care it.

Please tell me how to improve precision？Especially on side face. You can see some landmarks below:

Pressing space bar (when using the -example option) should perform one step
of mask adjustment.
Niedz., 24.03.2019, 00:44 użytkownik ywwyewenwei<EMAIL_ADDRESS>napisał:

Please tell me how to improve precision？Especially on side face. You can
see some landmarks below:
[image: image]
https://user-images.githubusercontent.com/46886131/54873013-8df72500-4e08-11e9-87d5-d20501849596.png
[image: image]
https://user-images.githubusercontent.com/46886131/54873015-94859c80-4e08-11e9-9b29-9a365079b9f3.png
[image: image]
https://user-images.githubusercontent.com/46886131/54873016-9a7b7d80-4e08-11e9-9c54-b53421102b7c.png
[image: image]
https://user-images.githubusercontent.com/46886131/54873017-a0715e80-4e08-11e9-9dab-a47fe126cada.png
[image: image]
https://user-images.githubusercontent.com/46886131/54873020-a6673f80-4e08-11e9-9299-08499764289b.png
[image: image]
https://user-images.githubusercontent.com/46886131/54873021-ac5d2080-4e08-11e9-8e1b-9275acbbc1d4.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TomaszRewak/Face-Landmarking/issues/1#issuecomment-475914464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFh2pBvl1IhfJorprB4WT6inW4HmRLp0ks5vZrxqgaJpZM4b9Z-F
.

Thanks a lot.

Thanks for taking your time to play with my project. If you have any more
question, feel free to ask.


Sample file does not include sample-service.

Hi The documentation mentioned sample-service folder however it is missed out from the zip file https://github.com/Azure-Samples/azure-iot-samples-ios/archive/master.zip. It will be great if someone can have a look.

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

ID: ff6bc4fa-3dde-5d65-82a2-f96da962bc16
Version Independent ID: 8faa4629-38be-408f-a736-2ce5bdece3e5
Content: Cloud-to-device messages with Azure IoT Hub (iOS)
Content Source: articles/iot-hub/iot-hub-ios-swift-c2d.md
Service: iot-hub
GitHub Login: @kgremban
Microsoft Alias: kgremban

@duongthaiha Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thank you for flagging this inconsistency for us. The service APIs in the C SDK have been deprecated, which is why the sample-service application was removed from the github repo. I updated the article to use the Azure portal to send a cloud-to-device message to test the sample-device application instead.


Constants for new commands

Adds the keys for parameters, responses and subcommands for AuthenticatorCredentialManagement, AuthenticatorBioEnrollment, AuthenticatorLargeBlobs and AuthenticatorConfig.
The least boring part of this PR is the extra sub command for ClientPin, that is checked in fido_commands.cc. As GetPinUvAuthTokenUsingPinWithPermissions returns the same map as GetPinToken, it is just a copy of that check. So still not too exciting. :)

Your latest comment reminded me of a switch over sub commands I do in fido_commands.cc (see latest commit). To fix the missing default, I caught it in a non-exiting way. Since all functions there now return value or error (like Rust Result), I want to move to less CHECK and more return. This PR starts making this right!

Sounds good. Indeed CHECK is for unrecoverable errors, while Result can be recovered.


Classlist is formatted as one line

With the new 0.4.0 version, classlists are formatted to one line like so:
From:
 def button(%{variant: :gray} = assigns) do
    ~H"""
    <button
      type={@type}
      class={[
        "phx-submit-loading:opacity-75 rounded-lg disabled:pointer-events-none disabled:opacity-80 flex items-center justify-center border border-gray-300 bg-gray-200 text-gray-700",
        "text-sm hover:bg-gray-300 active:bg-gray-300 px-4 py-[10px]",
        @class
      ]}
      {@rest}
    >
      <%= render_slot(@inner_block) %>
    </button>
    """
  end

To:
def button(%{variant: :gray} = assigns) do
    ~H"""
    <button
      type={@type}
      class={["flex items-center justify-center rounded-lg border border-gray-300 bg-gray-200 text-gray-700 disabled:pointer-events-none disabled:opacity-80 phx-submit-loading:opacity-75", "py-[10px] px-4 text-sm hover:bg-gray-300 active:bg-gray-300", @class]}
      {@rest}
    >
      <%= render_slot(@inner_block) %>
    </button>
    """
  end

This makes it harder to read, when there is a lot of classes.
BTW i love the new features!

@rmand97, please check in your .formatter.exs that Phoenix.LiveView.HTMLFormatter comes after TailwindFormatter, like so:
plugins: [TailwindFormatter, Phoenix.LiveView.HTMLFormatter]


Overall distance never higher than 7

I actually noticed on line 167 of the client-side main.lua that the distance was forced to 7, so when we set a distance on our target options greater than 7, it's never taken into account. For props this might be understandable, but for large polyZones it forces you to look at the floor, ceiling, wall or props less than 7 away. Logically, if I'm in a fairly large zone, and the target is pointing at the floor of the same zone that's more than 7 away from me, I should be able to access it.

fairly large zone

I'd personally never use large zones as targets, and I don't want to remove a rather reasonable restriction on target distance.


KeyCloak 10 Support

Can the this be bumped to support KeyCloak 10?

@DRLDoom I haven't test it, you can try it by yourself.
And based on the tests which were done by @wilderk at issue #51, this plugin will work well with Keycloak 10.x.

On my side the plugin is fully working with keycloak <IP_ADDRESS> and nexus 3.19.1-01 ;)

@ggdn Good news, thanks for your feedback :)

Close the inactive issue, if this plugin has any problem with Keycloak 10.x, just reopen this issue or create a new one. Thanks :)


Add timestamp and duration to Diagnostics Source events

Given the precedence of what we have here https://github.com/aspnet/Hosting/pull/543 I'm adding timestamp data to these events - this ensures that everyone is working from the same base data when talking timings.
In addition, I'm adding duration to the finish events so that consumers only have to subscribe to finish events in order to determine what the duration for a given piece of middleware is. This change is localized to the scope of code where we know that we have listeners interested in the result and hence isn't on the primary execution path.

Hi @avanderhoorn, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@lodejard @rynowak @Eilon

@kichalla please review & merge when you have a chance.

In addition, I'm adding duration to the finish events so that consumers only have to subscribe to finish events in order to determine what the duration for a given piece of middleware is.

If users subscribe only to the finish event, then the startTimestamp would be zero causing the duration to be incorrect. Should we always capture startTimestamp then? (but yeah i see you mention about primary execution path)

I agree with the case you mentioned... As you mentioned, one approach is to

Hi @avanderhoorn, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Whoops didn't meant to close... reopend.

Ok, I've updated things to fix the line breaks. Additionally, I've updated things so that the startTimestamp is always captured. If we are worried about always capturing that, we can update things to only capture it if either the MiddlewareFinished or MiddlewareException are being listened to, but that check could be more expensive than just capturing the value.

:shipit:

Ah yeah I like this fix - I'd like the data to always be accurate, when available.

f387d04af12fcfd5fc79d3c09c36df3cfbdefc41


Support caching all observables

This refactors how we define conversions, so that we can automatically cache all values produced by observables. It also shows the current value in the debugger, fixing https://github.com/jupyterlab/jupyterlab-data-explorer/issues/36


Change where delegate property is set to ensure it is populated when first viewWillAppear: is called

The following line in the generateView method of the OnboardingViewController class causes the viewWillAppear: method of the _currentPage to be executed:
[_pageVC setViewControllers:@[_currentPage] direction:UIPageViewControllerNavigationDirectionForward animated:YES completion:nil];

Because this method call occurs prior to the setting of the content view controllers' delegate property, when the _currentPage's viewWillAppear: is executed, its delegate property will be nil.
This pull request moves the following lines further up in the generateView method so that the delegate value is available from within the  _currentPage's viewWillAppear: method as expected.

Another good catch! Thanks for all the contributions!


Can't seek auto on slide bar player

I have problem when I seek on slide bar player, it always replay

Hi @Kimsoer
Can you please share a small video clip for reference?

here is video link https://drive.google.com/file/d/187usBvMkCh58tjMi_iqxvO5ddouKH6Y6/view?usp=sharing

@Kimsoer
Please send a code snippet of how are you using it?

Step 1: Initialize :
FlickManager flickManager;
VideoPlayerController videoPlayerController;
videoPlayerController = VideoPlayerController.network("$url");
flickManager = FlickManager(
videoPlayerController: videoPlayerController,
);
Step 2: call usage:
AspectRatio(
aspectRatio: 16 / 9,
child: FlickVideoPlayer(
flickManager: model.flickManager)
)

Are you doing any setstate() on onChange of Slide bar?
Please try to run the example app added in the plugin and let me know if you get the same issue. Thanks.
It may be implementation issue too.

@Kimsoer Let me know if you are able to resolve it. Closing this issue meanwhile. Please open if still you are stuck.


Log Manager #348

Log manager user logout, register event. Proxy create, drop event log.
Used table -> EventLog
Issue -> https://github.com/okulbilisim/ojs/issues/348
Logout Reference -> http://stackoverflow.com/a/13302526/2438520
Doctrine postUpdate, postPersist, postUpdate Reference -> http://docs.doctrine-project.org/en/latest/reference/events.html#postupdate-postremove-postpersist

:clap:

:+1:


Color RGB Lost after obj2gltf conversion

Hi githubers,
i have obj models with texture in format ::
v X  Y  Z  R G B
With R belong [0,1], when i converted with obj2gltf. My new GLTF lacks colors and appair all in white color.
After examinating the obj2gltf parser. Maybe, it does not take into account that format of obj model with colors alongside with vertexs coordinates...
Any possible fix folks for that kind of issue???
Thanks,
Momo

Yeah it doesn't take vertex colors into account yet. See https://github.com/AnalyticalGraphicsInc/obj2gltf/issues/102.


Bump xDS Interop Tests to Python 3

This PR updates all xDS interop tests to run the test runner on a Python 3.X interpreter. The build was recently broken when a minor version release of the rsa package (a transitive dependency) dropped support for Python 2.7. Theoretically, this bump in interpreter version is all that should be required, but it's possible that there's some incompatibility between the new interpreter version and the test runner code.
I won't merge until my manual test finishes, but it looks promising, so I want to get presubmits running.
Generated with: find tools/internal_ci/linux/ -name '*xds*docker*sh' | xargs sed -i 's/virtualenv "\$VIRTUAL_ENV"/virtualenv "\$VIRTUAL_ENV" -p python3/g'

Manual run passed: https://fusion2.corp.google.com/invocations/8def7472-d1ae-4278-a940-9fd9b5cb2f05/details

Thanks a lot for the fix.
We will need to backport this to the release branches.
Would the old versions all work with python 3? If no, we may need to pin RSA to an older version. :facepalm:

Would the old versions all work with python 3?

That depends on how the test runner code has changed over time. I seem to remember that the internal version was running on 3.4 at one point, so I think this will probably just work for all branches, but if not, it might require a little massaging.


null is not an object (evaluating  'Orientation.lockToPortait')

To Reproduce

In App.js

import FullscreenVideo from 'react-native-fullscreen-video';

render(){
        return (
              <View style={{flex: 1}}>
                  <FullscreenVideo src=require('Assets')
                       controls/>
              </View>
         )
}

More

node version

$ node -v
v10.17.0

$ npm -v
6.11.3

react-native : 0.62.2
react-native-fullscreen-video : 0.0.9

I'm getting this issue too, did you manage to fix it?

Hi @elrhomariyounes and @DTX-Elliot,
have you added the depedency to your projects' package.json?
"react-native-orientation": "^3.1.3"
After almost 3 years I've tested the simple example, and it works like a charm with Android SDK version 30 and RN v0.52.0. I'll try to update the RN to see what happens.

Hi, yes I have although the example is now working. Not sure what it was but after a restart it's fixed. Thanks anyway!


coreos/azure bump etcd version to v2.1.0-alpha.0

lgtm. /cc @errordeveloper

@idosh thanks for you contribution! Could you please clarify why alpha should be required upstream?

No special reason, just thought to test it and it worked.

@errordeveloper do you have any concerns merging this change? If you think we should hold on supporting 2.1.0 until it is out of alpha I would certainly understand.

@roberthbailey @idosh I am just not quite sure if there is a need to merge an upgrade to alpha version of software that most part of Kubernetes depends on.

@idosh, if you need to use newer version of etcd downstream, we could provide a way of setting it without having to modify the code.

It isn't necessary.
You can close the PR, if you don't want to use alpha version

@idosh It looks like the consensus above is to not switch to the new version of etcd quite yet while it's in alpha. I'm closing this, but please feel free to open an issue if you'd like to do what @errordeveloper suggested and add a way to set it without having to modify code.
Thank you for thinking to keep us on the bleeding edge! :-)


Save pyasic data to db

Save data to SQLite so that it can be loaded into a dashboard (next PR)

Get miner data (using pyasic)
Preprocess data (dict -> pd.Dataframe)
Write data to SQLite db or csv file

Previous discussion: https://github.com/UpstreamData/pyasic/issues/114

Looks good to me, if its working in testing that should be great!


Identification of all participants with Rainbow table

Let F(x) be a hash function that is used to anonymize participants, where x is a data from the bio-metric passport.
Your security model is based on the assumption that if an attacker E knows value y where y=F(x), then attacker E will be unable to deduce y because of properties of F.
However you oppose an attacker E that has access to information about all valid values of x (data from each valid passport is known to E). So the attacker can just take all valid values of x (x1, x2... xN), compute F(x) for each of them (even if there 140 millions, that's not a problem), and then just search for value that corresponds for a y value of a certain voter.
So if the attacker E has access to the data in all that was used to determine if a certain user can vote, and access to all passport data, then the attacker is able to identify each voter.
It is impossible to make a voting system were:

The voting criteria is based on data known to possible attackers (your case!)
Voting results are fully verifiable by each participant (that is what you claim)
Voting is fully anonymous (that is what you claim)
Duplicate voting is prohibited (that is what you claim)

See also: https://en.wikipedia.org/wiki/Rainbow_table
PS: I recommend to delete this issue after acknowledging the problem

Isn't the current timestamp used to create the hash? Then the attacker cannot create identical hashes to compare it in the votes DB

Isn't the current timestamp used to create the hash? Then the attacker cannot create identical hashes to compare it in the votes DB

Not current timestamp but current date. So all hashes for single day are same. It's not a problem to compute hashes for 100-1000 different days.

We acknowledge the potential risk of a dictionary attack on our system. To counteract this, we have implemented the use of a blinding factor on the side of the identity provider. Simplified, this approach involves creating a document nullifier by applying the Poseidon hash function to a combination of the passport hash and a blinding factor. This method effectively obstructs an attacker's ability to identify users through a dictionary attack by obfuscating the direct relationship between the passport information and its representation in our system.
We are also working on applying Active authentication to deterministically generate the document nullifier.
With active authentication, the chip securely stores a private key within a secure module, which is never disclosed. We anticipate that this level of security is so robust that not even government entities could gain access to it.
Also, we are not using "current date" to create a document nullifier (hash).


chore: add a config struct for transfers generator

This change is

Codecov Report
Attention: Patch coverage is 90.90909% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 78.13%. Comparing base (e617688) to head (7b08114).

Files
Patch %
Lines

...s/blockifier/src/test_utils/transfers_generator.rs
90.90%
3 Missing :warning:

Additional details and impacted files
@@                               Coverage Diff                               @@
##           avi/concurrency/improve-transfers-flow-test    #1945      +/-   ##
===============================================================================
+ Coverage                                        78.09%   78.13%   +0.03%
===============================================================================
  Files                                               62       62
  Lines                                             8866     8881      +15
  Branches                                          8866     8881      +15
===============================================================================
+ Hits                                              6924     6939      +15
  Misses                                            1504     1504
  Partials                                           438      438

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

+reviewer:@barak-b-starkware

crates/blockifier/src/test_utils/transfers_generator.rs line 61 at r3 (raw file):
Previously, barak-b-starkware wrote…
WDYT sharing code with ConcurrencyConfig?

Done.
I think it is best to have the default for the transfers generator be defined in the constants of these files and not be the default of the general ConcurrencyConfig. This way, it is easier to play around with these numbers when we use the benchmark.

crates/blockifier/src/test_utils/transfers_generator.rs line 115 at r3 (raw file):
Previously, avi-starkware wrote…
Everything that is not in the config is essentially derived from the config at initialization.
Note that the starting sender_index doesn't matter. We need it as a member of the struct to keep track of who the next sender should be, but since we loop around senders, any sender we start with would be symmetric and produce similar behavior.

If all are derived from the config, either expand or push them into it.
If the sender_index is redundant, how about removing it and using the default values or something similar?

crates/blockifier/src/test_utils/transfers_generator.rs line 115 at r3 (raw file):
Previously, barak-b-starkware wrote…
I can move it to the refactor PR if you want to merge it, LMK :pray:

In the current PR, I need the sender_index field to keep track of the current sender. Note that the TransfersGenerator struct persists between calls to execute_transfers and the next sender in a new call to execute_transfers is the sender that follows the last sender in the previous call to execute_transfers. Therefore, we need to always keep track of the current sender_index and this is done via the sender_index field in the TransfersGenerator struct.
The starting value always defaults to 0 currently.
There is no reason to change it in the refactor PR, since there we keep track of the sender via sender_iterator.


[ed25519] Use verify_strict for signature verification in ed25519 precompile

Problem
simd 152 is merged. This PR is change # 1, which updates ed25519 precompile signature verification to use the strict verification.
Summary of Changes
Replaced signature verification in the ed25519 precompile to use strict verification under a feature gate.
Fixes #

Example test:
https://github.com/0x0ece/agave/commit/ba98faacb61ce19862ee2edfe277fdaf9c10432d

I ran the benches on my devserver and it does seem that verify_strict increases cost by ~4-5%.
Standard verification
test bench_ed25519_len_032 ... bench:      53,174.08 ns/iter (+/- 320.90)
test bench_ed25519_len_128 ... bench:      53,227.03 ns/iter (+/- 460.80)
test bench_ed25519_len_32k ... bench:     105,673.43 ns/iter (+/- 215.66)
test bench_ed25519_len_max ... bench:     157,801.53 ns/iter (+/- 393.42)

Strict verification
test bench_ed25519_len_032 ... bench:      56,098.69 ns/iter (+/- 652.68)
test bench_ed25519_len_128 ... bench:      56,373.39 ns/iter (+/- 408.99)
test bench_ed25519_len_32k ... bench:     109,504.36 ns/iter (+/- 2,027.92)
test bench_ed25519_len_max ... bench:     163,012.00 ns/iter (+/- 644.40)

The bench is expected, however all precompiles cost like a tx sigverify, and sigverify is already using verify_strict.
If anything, users were charged 4-5% extra before, after this change they’ll be charged “correctly” (And are prob undercharged when using secp256k1, but this is off topic here)

Hm, it does seem like the CU price for sigverify and precompile ed25519 are assigned different values in the cost model. @tao-stones, can you help if the current cost model for ed25519 is adequate? Looking at the commit history of the cost model, I can't seem to find how the cost models were originally assigned.

Do you have ref to the code? TBH I was quoting something I saw in firedancer, so maybe we have implemented the wrong thing...

Hm, it does seem like the CU price for sigverify and precompile ed25519 are assigned different values in the cost model. @tao-stones, can you help if the current cost model for ed25519 is adequate? Looking at the commit history of the cost model, I can't seem to find how the cost models were originally assigned.

Hey @samkim-crypto, precompiled costs were determined by benching (under sdk/benches). Transaction sigverify process is optimized, so it'd have different performance than ed25519 or secp256k1, iirc.

Do you have ref to the code? TBH I was quoting something I saw in firedancer, so maybe we have implemented the wrong thing...

@0x0ece, I believe the costs for the precompiles are defined in the solana-cost-model crate (here)

Hm, it does seem like the CU price for sigverify and precompile ed25519 are assigned different values in the cost model. @tao-stones, can you help if the current cost model for ed25519 is adequate? Looking at the commit history of the cost model, I can't seem to find how the cost models were originally assigned.

Hey @samkim-crypto, precompiled costs were determined by benching (under sdk/benches). Transaction sigverify process is optimized, so it'd have different performance than ed25519 or secp256k1, iirc.

@tao-stones, if I run the benches, I consistency get about 4-5% increase in the timing both in my local and dev machines. Do you think it is reasonable to increase the constant factor here by 5%?

if I run the benches, I consistency get about 4-5% increase in the timing both in my local and dev machines. Do you think it is reasonable to increase the constant factor here by 5%?

the message length matters, currently tx can have 1K at most. iirc, it was benched with 3k message len to be reasonably conservative. Assuming 5% increase you are seeing are with different message len?

Yeah I did some more formal testing and I seem to be getting about 4% max increase on any message lengths on my dev machine. It does seem reasonable to increase the cost constant by 4%, so either 79 (maybe 80).


feat: code interpreter

Python code interpreter. Requires python3 (unsafe mode) or docker (safe mode). It will let fabrice program and run all sort of apps

Replaced by #145


Markdown for newlines

Related but different to the other issue I raised.
When the gDoc contains a newline (via SHIFT+ENTER, as opposed to a paragraph break), markdown can mark that up using double-space at the end of the line. However that functionality appears to be absent from this addon.

If we could detect the shift-enter, we could use a \ line termination.
As I mentioned on the other bug, unfortunately, there's no way to detect a shift-enter line break in a Doc from Apps Script (that I'm aware of). The bold text renders properly, but without the line break. See https://github.com/evbacher/gd2md-html/wiki/Markdown-playground#formatted-text-and-soft-line-breaks for a test.
It might be possible to detect line-break characters (\r), but that might be expensive. If I have a chance, I'll check it out.

Never mind. We can do this. I'll get it in when I get a chance.

Oh, that's great! I'm glad you found a way!
On Feb 6, 2018 07:20, "Ed Bacher"<EMAIL_ADDRESS>wrote:

Never mind. We can do this. I'll get it in when I get a chance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evbacher/gd2md-html/issues/18#issuecomment-363306421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuLL8bzF2YE33Sn2JMhGqVs-ynfWY1mks5tR9L9gaJpZM4R3CFG
.

Fixed in v 1.0β10. Please reopen (or open another bug) if still a problem.


view details page create/ react-routes action added/

Issue #18  📐

I Oscar Vaquera have worked for #18

Done

Added react-routes to app.jsx
Added shoe_details component/page
Modify the Button component (Needed to update to make redirect to shoe_details page)
New Images added
package.json updated (react-routes was installed)

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #18

Screenshots 📷
Here are the pictures of changes that I have made 🔽

I saw some browser compatibility issues where the screen was reacting differently in duck duck go and in chrome. Please ignore the first commit, i’ve already fix the issue on the second one. Thank You!


Fix error in pen tool

Closes #
The pen tool was causing a DocumentError: LayerNotFound because it was trying to delete the preview layer that did not yet exist.

I think I would prefer if we were to split the make operation into two parts and only do the delete explicitly where it is needed, that should help with readability


Estebanreyl/dataplane runtime sdk v2 prerelease

This preview release  contains the fully functional runtime sdk ready to be packaged as a nuget for the ACR runtime API. It was built from the recently approved  https://github.com/Azure/azure-rest-api-specs/pulls?utf8=✓&q=is%3Apr+estebanreyl
This release:

Adds support for most of our Blob end point API's
Adds support for multiple Image manifest types
Adds oauth2 support (since v1 was overtaken by v2 before it could be approved)
Includes many fixes as described by the last two swagger releases

Renames many functions as described below:
GetManifestAttributesAsync: Manifests.GetAttributesAsync
GetManifestAsync: Manifests.GetAsync
UpdateManifestAttributesAsync: Manifests.UpdateAttributesAsync
CreateManifestAsync: Manifests.CreateAsync
DeleteManifestAsync: Manifests.DeleteAsync
GetManifestListAsync: Manifests.GetListAsync
GetTagAttributesAsync: Tag.GetAttributesAsync
GetTagListAsync: Tag.GetListAsync
UpdateTagAttributesAsync: Tag.UpdateAttributesAsync
GetRepositoryListAsync: Repository.GetListAsync
GetRepositoryAttributesAsync : Repository.GetAttributesAsync
DeleteRepositoryAsync : Repository.DeleteAsync
UpdateRepositoryAttributesAsync : Repository.UpdateAttributesAsync
New functions include:
Blob.GetAsync
Blob.CheckAsync
Blob.StartUploadAsync
Blob.CancelUploadAsync
Blob.GetStatusAsync
Blob.GetChunkAsync
Blob.CheckChunkAsync
Blob.MountAsync
Blob.StartUploadAsync
Blob.UploadAsync
Blob.EndUploadAsync
Blob.DeleteAsync
RefreshTokens.GetFromExchangeAsync
AccessTokens.GetAsync
AccessTokens.GetFromLoginAsync
V2Support.CheckAsync
New ease of use constructor and acrClientCredentials also added.
Closes: Azure/azure-rest-api-specs#6773

@AlexGhiondea, @erich-wang, a review would be appreciated.

Is this SDK autogenerated?

@AlexGhiondea, I believe it is auto generated with some modifications.
@amishra-dev I will look into this. We could rename it RegistryBlob or ACRBlob
@estebanreyl can you confirm?

The blob naming comes directly from the swagger generation. We could update that and then eventually have it go through but at the end of the day our blob paths would be under the container registry client and should thus be unambiguous especially since their namespace is distinct from that of Azure Storage blob which in C# being a strongly typed language should make it hard to make the mistake since blob by itself for us is just a method disambiguation level. Additionally, renaming them to ACRBlob or DockerBlob are not very representative as the blobs in question aren't either unique to ACR, nor docker. In fact blobs in our case just represent arbitrary data streams.

@adewaleo , @amishra-dev The blob naming comes directly from the swagger generation. We could update that and then eventually have it go through but at the end of the day our blob paths would be under the container registry client and should thus be unambiguous especially since their namespace is distinct from that of Azure Storage blob which in C# being a strongly typed language should make it hard to make the mistake since blob by itself for us is just a method disambiguation level its not even an object type but an instance. Additionally, renaming them to ACRBlob or DockerBlob are not very representative as the blobs in question aren't either unique to ACR, nor docker. In fact blobs in our case just represent arbitrary data streams.

This makes sense @estebanreyl. I think @amishra-dev 's fear is that someone could be using both namespaces (Microsoft.Azure.ContainerRegistry and Azure.Storage.Blobs) in the same program. i.e methods to work with azure storage account blobs and azure container registry blobs, both of which are binary streams of data.
But as @estebanreyl  has said, these are auto generated from our swagger and as C# is strongly typed users are unlikely to have issues mixing the two.

@amishra-dev , with the recent mail thread do you still think any classes / methods still need to be remained? Could you give examples where you feel the current naming could be unclear?


Ngrok 3200

When moving the link to another device the tunnel expires?

Yes, the tunnel is deactivated if you exit from Blackeye


[AutoPR servicefabric/data-plane] typo: servicefabric/data-plane/Microsoft.ServiceFabric

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4834

(message created by the CI based on PR content)


Restrict YAML parser to not create Java objects

Type of change

Bugfix
Enhancement / new feature
Refactoring
Documentation

Description

Checklist

[ ] Update/write design documentation in ./documentation/design
[x] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=smoke

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 10
PASS: 10
FAIL: 0
SKIP: 0
BUILD_NUMBER: 254

Commit message changed


Use the same beam resolution for validation as in the reference paper

Have you generated the reference files with the threading disabled in update_nhs?

No. I'll do it again.

Hold on, this is TLSPH only. The NHS is never updated.


Platypus not passing .webloc files

I'm seeing a strange issue with .webloc files. When I create an app that accepts dropped files, whatever I drag is passed as an argument, except, for some strange reason, .webloc files.
Steps to reproduce:
Create a Platypus app that accepts all dropped files
Write a script that outputs argv
Drag a .webloc file
I'm attaching an example app. All the script does is this:
<? print_r($argv); ?>
So, whatever I drag to it is output in the window. Except .webloc files.
Foo.app.zip

I have managed to reproduce this, very strange indeed! Will examine.

I have managed to reproduce this, very strange indeed! Will examine.

At first I thought maybe a .webloc file is not covered by the UTI public.item but it appears it is

I'm also noticing this with textClippings. When I drag a textClipping onto a window, it is not passed, but it does seem to be working by dragging onto the app icon.

I cannot reproduce this issue on Big Sur, closing.


Improve single-object queries

With a GraphQL schema like
type Parent { id: ID! }
type Child { id:ID!, parent: Parent }

and a query like
{ parents { child { id } }

the SQL query that we end up running uses windowing (with lateral joins) even though that's unnecessary here: we know we only expect one child per parent, and windowing, which is needed for sorting/limiting, has no real effect, but slows the query down.
In this situation (and the mirror situation where the parent stores the child's id and Child.parent is derived) we can use a non-windowed query.
We need to detect if the mappings stored invalid data by having more than one child per parent. That can be done by querying for number of parents + 1 since that will guarantee that at least one parent will get two children in the error case.
The work for this should happen in prefetch and it should generate an EntityCollection::All rather than an EntityCollection::Window in this case.
Special care must be taken in the cases where Parent or Child are interfaces.

Fixed by PR #1734


Use cobra to unify the flags processing

PCP Issue

difficult: easy
score: 50
min score required: 0
Recommended Skills: Go

Description
By now, pd-ctl uses pflag to process the flag for itself and uses cobra to process flags for its subcommands. In fact, pd-ctl itself is a command too. We could use cobra to unify all the processes.
Requirements:

Remove pflag library
Use cobra to process all flags and commands
Distinct global and local flags
Have meaningful usage message

Reference:

github.com/spf13/pflag
github.com/spf13/cobra

/pick-up-challenge

/pick-up-challenge


Retrieve archived vault details from API

Task Description
During recovery of the App through mnemonic, if we retrieve all the previously associated vaults and decrypt them, it will be a heavy operation. Hence we will get the archived vault details once the user clicks on the vault from the list.

Is this issue still relevant?


images: Update bpftool

This new version includes new feature probes for eBPF instruction set extensions and bounded loops.

/test-1.22-4.19

/test-1.22-4.19

/test-1.22-4.19

Hey Paul, bpf-next was merged into net-next last weekend, and there are dependencies for probing for BBR. Do you have a chance to build the latest bpftool from bpf-next? That would be really great, thanks!

/test

/test

k8s-1.23-kernel-net-next is another case of https://github.com/cilium/cilium/issues/15474. This pull request doesn't include the fix from https://github.com/cilium/cilium/pull/19061, but Jenkins rebased the tests such that the new test ran and failed. Safe to ignore. Reviews are in, so marking ready to merge.

This seems to have a merge conflict.

Oh, no...

/test

Runtime failed with known flake https://github.com/cilium/cilium/issues/18958. Thankfully it failed while collecting coverage so we know all privileged unit tests passed.
k8s-1.22-kernel-4.19 failed with known flake https://github.com/cilium/cilium/issues/18318.

Reviews are in. Marking ready to merge.


Convert CharacterGroups to tags

Adds TemplateTags
Adds a CharacterGroup tag type
Renames old CharacterGroup model to OldCharacterGroup
Adds model connections
Migrates old-style character groups to tags
Adds scopes to interact with groups
Rewrites part of characters#index and most of the group partial to handle new underlying infra
Updates factories and model setup to handle new underlying parts
Updates character relocator to check for new-style groups

This is below coverage because OldCharacterGroup is still in (for migration reasons) and untested (because nothing calls it). Unsure whether to drop the coverage or make a dummy test or what.


Please mentioned that how to live reverb in apache server.

Hello Team,
We have created one application using Laravel Reverb. Now we want to live it and not adea about how to do it in apache server so please add some basic information in documentation so its easy to do.
Thank You.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


SIGSEGV when running parallel du on large goofys directory

$ go run du/du.go /path/to/linux-4.10/ > /dev/null
du: readdirent: software caused connection abort
du: readdirent: software caused connection abort
du: readdirent: software caused connection abort

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7b4892]

goroutine 1926 [running]:
github.com/kahing/goofys/internal.(*DirHandle).ReadDir(0xc421762380, 0xc4200dedc0, 0x2, 0xc42030a6a0, 0x2, 0x2)
        /home/gaul/work/go-workspace/src/github.com/kahing/goofys/internal/handles.go:1223 +0x912
github.com/kahing/goofys/internal.(*Goofys).ReadDir(0xc4200dedc0, 0x7f396654b090, 0xc42163d860, 0xc4217348c0, 0x0, 0x0)
        /home/gaul/work/go-workspace/src/github.com/kahing/goofys/internal/goofys.go:904 +0x1ec
github.com/jacobsa/fuse/fuseutil.(*fileSystemServer).handleOp(0xc42017a200, 0xc420122240, 0x7f396654b090, 0xc42163d860, 0x7f2820, 0xc4217348c0)
        /home/gaul/work/go-workspace/src/github.com/jacobsa/fuse/fuseutil/file_system.go:164 +0xa23
created by github.com/jacobsa/fuse/fuseutil.(*fileSystemServer).ServeOps
        /home/gaul/work/go-workspace/src/github.com/jacobsa/fuse/fuseutil/file_system.go:108 +0x12a

Extra logging reveals an object without a Size:
{
  ETag: "\"0700e5a8ffa2b7a6722f24fb16569a05\"",
  Key: "linux-4.10/arch/tile/kernel/sysfs.c",
  LastModified: 2017-03-07 10:40:38 +0000 UTC
}

does this object always not have a size?

Different errors on different runs.  Now I encountered:
panic: runtime error: slice bounds out of range

goroutine 64772 [running]:
github.com/kahing/goofys/internal.(*DirHandle).ReadDir(0xc420ec0000, 0xc4200dcdc0, 0x2, 0xc42dcde220, 0x2, 0x2)
        /home/gaul/work/go-workspace/src/github.com/kahing/goofys/internal/handles.go:1216 +0xc8e
github.com/kahing/goofys/internal.(*Goofys).ReadDir(0xc4200dcdc0, 0x7f6a1a629470, 0xc42d099770, 0xc420d9e180, 0x0, 0x0)
        /home/gaul/work/go-workspace/src/github.com/kahing/goofys/internal/goofys.go:904 +0x1ec
github.com/jacobsa/fuse/fuseutil.(*fileSystemServer).handleOp(0xc4201a9100, 0xc420122540, 0x7f6a1a629470, 0xc42d099770, 0x7f3820, 0xc420d9e180)
        /home/gaul/work/go-workspace/src/github.com/jacobsa/fuse/fuseutil/file_system.go:164 +0xa23
created by github.com/jacobsa/fuse/fuseutil.(*fileSystemServer).ServeOps
        /home/gaul/work/go-workspace/src/github.com/jacobsa/fuse/fuseutil/file_system.go:108 +0x12a

I also got a strange response from ListObjects is empty -- no IsTruncated field.


Create and use a common component for selecting CF/Org/Space that can go in the app header bar

Move this control to the blue bar and use consistently.

Includes work to only show filter if there's multiple options


blob: TestBlobService_Get is flaky

--- FAIL: TestBlobService_Get (0.02s)
    service_test.go:221:
        	Error Trace:	/home/runner/work/celestia-node/celestia-node/blob/service_test.go:221
        	            				/home/runner/work/celestia-node/celestia-node/blob/service_test.go:294
        	Error:      	Received unexpected error:
        	            	empty shares received
        	Test:       	TestBlobService_Get
    --- FAIL: TestBlobService_Get/not_included (0.00s)
        testing.go:1490: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test

@vgonkivs temporarily added https://github.com/celestiaorg/celestia-node/blob/main/blob/service_test.go#L1 to skip the test on mac os to help with CI passing, just in case it suddenly looks fixed

Had a private discussion with @walldiss regarding this case and figured out that GetSharesByNamespace can behave differently:

Row1 = [Namespace1, Namespace3]
Namespace1 < Namespace2
Namespace2 < Namespace3
Requesting Namespace2 will return empty shares + non-inclusion proof.

Row1 = [Namespace1]
Row2 = [Namespace3]
Namespace1 < Namespace2
Namespace2 < Namespace3
Requesting Namespace2 will return empty shares + empty proof.

Before that, we have never considered non-inclusion proofs for the Blob Module. cc @Wondertan
@nashqueue do you need non-inclusion proofs as a result of GetProof if the blob does not exist? If yes, how we can handle case 2. where no shares and no proofs?

🖐Hello! Welcome to #CelestiaCommunity
We are happy to announce  ($TIA) is now available on DEX #PancakeSwap 💪
👉  Our ONLY Contract:
CA:      0xf2caebbb49a7733a7c5cff571af849a6b52d346c
🥞 BUY ON PANCAKESWAP:
https://pancakeswap.finance/swap?outputCurrency=0xf2caebbb49a7733a7c5cff571af849a6b52d346c
▫Name:   Celestia
▫Symbol : TIA
▫Decimals : 18
📆Launch on  #BINANCE at Oct 31, 16:00 (UTC)


actual flight

Hi, Keipour
I met some questions when I made the real experiment. I used Pixrecer R15 hardware, and upload FMUv4 firmware as following the PX4 user guide, After this, i try to make the fully-actuated UAV take off, but When I pushed the throttle lever to the maximum using the remote control, the fully-actuated hexacopter still couldn't take off. So I dare not switch the flight mode to offboard, have you encountered this situation again?
I used to use a regular Mavros interface, which can also be used in simulation environments.  I see this interface in github readme, is it necessary when I use ROS for offboard flight? How should i use this？

Hello @LizhichengDlut, it has been some time since I have left the project and @mmousaei might be a better help.
We have seen a behavior where the rotors just rotate with the idle speed no matter what input is provided when other firmwares/hardwares are being used (other than Pixracer), which should be easy to fix but we never needed it and never tracked down the issue to fix the bug; but Pixracer should be compatible (unless if something has drastically changed from R14 to R15) and you should not be seeing that behavior.
Flying with the remote controller should be independent from MAVROS and it should take off regardless when using the remote.
We have not tested with the regular MAVROS, so cannot tell if that is compatible or not. I would suggest using the software developed with this firmware as explained in the README.
Hope that helps.
Azarakhsh

Thanks for your reply,  it might be much helpful
How is the inclination direction of a drone set, that is, the rotation direction and position of each rotor, as well as its inclination direction and corresponding channel number, are there corresponding file descriptions?
Hope reply soon

Thanks，I find it , the first rotor is channel 1? right?


Bumping version to 1.5.0rc1, Add model contracts

This PR is about:

Bumping dbt-core version to 1.5.0rc1
Implementing model contracts (new functionality in v1.5.)
(High level explanation of these changes in this discussion under Model Contracts section)

Some remarks about model contracts implementation:

It is implemented by running 2 queries: Create table and Insert into (similar as in dbt-redshift - example query).
It couldn't be implemeted as single CTAS query (as in dbt-snowflake - example query), as in Trino we can't
define column types in CTAS query.

dbt-core model contracts works on enforcing column names and types in table, and columns constraints:
not null, unique, primary key, foreign key, check
Trino doesn't support any of them, except that not null is supported in some connectors.
It is a tricky one, as not null is supported in some connectors, but it isn't in others (memory, hive).
It isn't documented in Trino docs (it isn't explicitly mentioned in connector page - hive connector docs, nor in CREATE TABLE docs)
So I'm not sure if we should support it now, as user would ask questions why it's not working with
'X' catalog, when we can't point them directly to connector documentation.

Please let me know what you think.

@hovaesco

Looks good, why tests for Galaxy are disabled? Have you investigated it?

For some tests, we're receiving this error on galaxy:
TrinoUserError(type=USER_ERROR, name=NOT_SUPPORTED, message="Timestamp precision (3) not supported for Iceberg. Use "timestamp(6)" instead."

I made only these tests disabled on galaxy. I've duplicated them, decorated with @pytest.mark.iceberg and defined type as timestamp(6) there.
So everything is also tested on galaxy, but with this timestamp precision adjustment.
WDYT of that approach?

Yes, it's known limitation. Maybe you could just adjust TrinoColumnEqualSetup for TIMESTAMP(6) and you could get rid of TrinoColumnEqualSetupIceberg.

Yes, it's known limitation. Maybe you could just adjust TrinoColumnEqualSetup for TIMESTAMP(6) and you could get rid of TrinoColumnEqualSetupIceberg.

@hovaesco adjusted to this comment

LGTM, please submit a PR to dbt docs.

Hmm wouldn't it be better to prepare PR, but submit it just after releasing dbt-trino 1.5.0 final? Maybe we shouldn't update dbt docs before releasing our stuff? To avoid situation where someone is asking about feature mentioned in docs, but not released yet


How about it's performance on KITTI 3D ?

Hi,
Thanks for your interest in our work!
We have not tried to train or test on KITTI 3D mainly due to that the codebase we are using, VoteNet, does not work well with outdoor Lidar pointcloud.
See issue here: https://github.com/facebookresearch/votenet/issues/53
We think that applying our idea to 3D lidar pointcloud detection should be beneficial and we are also working on related follow up research projects. Stay tuned!


Turn configuration options into const generic params

Depends on https://github.com/nagisa/rust_tracy_client/pull/87.
This is a bit of a so preoccupied with whether they could, they didn’t stop to think if they should moment, but I realized we can make our primitive config options const generic params. The benefit is that the optimizer can eliminate a bunch of branches and dead code that would have been very hard to prove safe to remove before. There's precedent for doing something similar in other crates: https://docs.rs/sharded-slab/0.1.7/sharded_slab/pool/struct.Pool.html#method.new_with_config.
Also, I don't think this makes the API worse, it's basically just different syntax (unless you want this stuff to be dynamic in which case you're screwed):
   tracing_tracy::TracyLayer::new()
                        .with_stack_depth::<32>()
                        .with_fields_in_zone_name::<false>(),

Thoughts?

Thoughts?

NACK if its an either/or ordeal. I know there are folks who configure their layers dynamically. But. We could make an API allow both dynamic and static configuration:
TracyLayer::<S, Z>::with_stack_depth<NewS: StackDepthOption>(s: NewS);
TracyLayer::<S, Z>::with_fields_in_zone_name<NewZ: FieldsInZoneNameOption>(s: NewZ);

impl StackDepthOption for u16 { /* dynamic */ }
impl StackDepthImpl for typenum::N0 { /* static */ }
impl StackDepthImpl for typenum::N1 { /* static */ }
// ...

impl FieldsInZoneNameOption for bool { /* dynamic */ }
struct True;
impl FieldsInZoneNameOption for True { /* static */ }
struct False;
impl FieldsInZoneNameOption for False { /* static */ }

etc. Or it could be a trait with methods. If those methods return constant values, I suspect the compiler will be able to figure inlining them in.

Oooooh, that's quite clever! I went forward with that approach, but only differentiated between zero and non-zero u16s since the main optimizable difference for the stack depth param.

Hm, yeah, I’m not sure this is worth it in this exact proposed shape. I’m going to cut a release shortly with all the changes so far and perhaps draft a counter proposal to this...

That works! I've been procrastinating on replying to #78, so I'll try and do that tonight. The main point is that I agree we should probably temporarily go back to not manual lifetimes until we figure out a proper fix.

cf. #91

#91 is better than this as long as ConstConfig or something equivalent is provided out-of-the box.


Separate start and end depots

This PR:

[x] Closes #604.
[x] Adds and passes relevant tests.
[x] Has well-formatted code and documentation.

Notes:
Please read our contributing guidelines first.
In particular:

You must add tests when making code changes.
This keeps the code coverage level up, and helps ensure the changes work as intended.
When fixing a bug, you must add a test that would produce the bug in the master branch, and then show that it is fixed with the new code.
New code additions must be well formatted. Changes should pass the pre-commit workflow, which you can set up locally using pre-commit.
Docstring additions must render correctly, including escapes and LaTeX.
Finally, it is essential that all contributions in this PR are license-compatible with PyVRP's MIT license.
Please check that this PR can be included into PyVRP under the MIT license.

@leonlan I think this is good to go now, could you have a look?


Get rid of vertical scrolling on popup.html somehow

Seems like chrome sets a max height of 600px for chrome extension plugins in their API. Gonna see if I can override it.


fix/update-zilclient (DONT MERGE FIRST)

fixed the confirm method after decoupling zilpay from zilclient
modified signer method on zil side

TODO

pull the latest tradehub sdk from master after the tradehub sdk pr is merged (see related PR)
commit the updated yarn.lock

Related PR

https://github.com/Switcheo/tradehub-api-js/pull/35

merged tradehub sdk at 291b670e12e75a2f2e103653a84eac6a71311a90


Refactoring TRuntimeObjects

As it stands, TRuntimeObjects has the following behaviour:

I would like to fill a histogram, add a GValue, make a cut, etc.
The FillHistogram function looks in a TList of TObjects for that name and finds the pointer to it.
A dynamic_cast is performed to make sure that object is the type of histogram I hoped it was.
If dynamic_cast fails, it creates the appropriate object with that name (this already feels like a porential failing point if there are now two objects with that name...the search doesn't look for another object with that name)
The histogram is then filled

This happens on every single FillHistogram call. It means we are doing a linear search via string comparisons for every histogram. We are then performing a dynamic_cast every single time. There are also some TDirectory->cd() things going on every time that seem a bit slow, but I'll leave that for now....
So, I see a few problems. We can stick with string comparisons for now, just for refactoring purposes and not breaking backwards compatibility. We can use a log(n) lookup like a std::map rather than a TList on the whole set of lists. We can probably get away with static_casting and exception handling instead of the heavy dynamic cast. We can add a list for each type of object to avoid casting completely.
I don't necessarily think the seperate lists is breaking any generality either. The class already has separate fObjects and fGates lists. Furthermore, we only need these maps to hold TH1* or TH2* as the Fill call is inherited and our more advanced histograms (Sym) has the same signiture. Removing the list lookup and dynamic casts will save around 15% of the CPU cycles.
Let me know if you see anything wrong with this or have any other suggestions.

I think it is reasonable to replace the TList with a map. And using multiple maps for the different dimensions makes sense (it's the same thing we do in proof).
I don't think that there is a way to get rid of the string comparisons, not without sacrificing the ease of creating and filling new histograms.

I'm going to leave this open but not worry about it for now. I did a test by changing the dynamic casts to static casts. Turns out it doesn't change the behavour of the code whatsoever (as far as I can tell) when it comes to histogram names. Crashing a TDirectory into a TH1 might be an issue though. Doing this didn't have any significant speed ups. I'll continue looking into it, but I think there are other areas that can be improved.

There's a bunch of cd'ing in this code. Not sure what it does... Removing it speeds up the code by a further 10%...I commented them out and made the same histograms. Even tried making some with the same name in a different directory. Running at 42 s now, down from 82 s. There might be minor improvements left, but I think 50% reduction in running time is very good to produce histograms. To put this in context, this run takes 157 s to create an analysis tree. Making histograms takes 1/4 the time as building analysis tree with the current code. I don't think there is any room to shave off another factor of 2.


Empty state icon not hidden from screen readers

Describe the bug
The icons used in the app/components/empty_state_component.html.erb are decorative and should be hidden from screen readers. This component is used in several places, but you can test its behavior on the Notifications page.
To reproduce
Steps to reproduce the behavior:

Clear your notifications if you have any
Go to the notifications page
Turn VoiceOver on: command + F5
Read out the page contents with control + option + Right Arrow
Notice that the bell icon is announced as image with no accessible title
Turn VoiceOver off: command + F5

Expected behavior
VoiceOver should skip the bell icon
Actual behavior
VoiceOver reads "image" without any additional context
Screenshots
https://user-images.githubusercontent.com/22390758/178143470-8615bf51-5b77-4a86-be2f-3dc60b829e27.mov
Additional context

Accessibility in inline_svg
More on accessible SVGs

@joemasilotti noticed this one is similar to #551 and #554 so happy to take it

Closed by #562.


Failed to run as a self-contained app in Aguacongas.TheIdServer project

I am trying to build and run this repository in my local machine. So it is built successfully in my machine but when I am trying to run the application I am getting this error.
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'D:\AdminUI\TheIdServer\src\Aguacongas.TheIdServer\bin\Debug\net7.0'.
Failed to run as a self-contained app.

The application was run as a self-contained app because 'D:\AdminUI\TheIdServer\src\Aguacongas.TheIdServer\bin\Debug\net7.0\Aguacongas.TheIdServer.runtimeconfig.json' was not found.

I have tried to clean and rebuild the solution but it is not resolved. FYI, I have set the below project as start up projects

Aguacongas.TheIdServer
Aguacongas.TheIdServer.BlazorApp
Aguacongas.TheIdServer.Duende

Can you please help me to resolve this issue?

Hi, thx to contribute.
You just need to start Aguacongas.TheIdServer.Duende, check the launchSettings.json to start the project on port 5443 for HTTPS.
Aguacongas.TheIdServer cannot be started it's a lib.
Aguacongas.TheIdServer.BlazorApp can be started but it's not configured by default. The app is hosted in Aguacongas.TheIdServer.Duende.

@aguacongas Have you any steps to run the whole application?I have connected the my local database successfully and start only  Aguacongas.TheIdServer.Duende but still I am not able to run application. Also , I am trying to connect with my existing duende server but don't know where I need to provide the the identity server URL? Can you please help me in it?

can be Aguacongas.TheIdServer.BlazorApp disabled from load in duende and only have duende enabled? Aguacongas.TheIdServer.BlazorApp i want it to be private..?
is it possible?

@ekjuanrejon. Use the MultiTiers sample then