chore(feat-multi-module-components): release 0.78.0

:robot: I have created a release beep boop
0.78.0 (2023-03-15)
Features

Use aws_iam_role_name field for GitHub Actions fogg apply job (#84) (eccc952)

Misc

bump github.com/aws/aws-sdk-go from 1.44.207 to 1.44.219 (#78) (d3e3927)
bump github.com/aws/aws-sdk-go from 1.44.219 to 1.44.221 (#82) (64aa35b)
bump github.com/chanzuckerberg/go-misc (#71) (47611cc)
bump github.com/fatih/color from 1.14.1 to 1.15.0 (#79) (518acec)
bump github.com/go-git/go-git/v5 from 5.4.2 to 5.5.2 (#51) (f0cf66a)
bump github.com/go-git/go-git/v5 from 5.5.2 to 5.6.0 (#76) (1553792)
bump github.com/hashicorp/go-getter from 1.7.0 to 1.7.1 (#81) (1d67c70)
bump github.com/hashicorp/hcl/v2 from 2.16.1 to 2.16.2 (#80) (b120143)
bump github.com/jinzhu/copier (#73) (767ea87)
bump github.com/runatlantis/atlantis from 0.22.3 to 0.23.2 (#77) (d6b9eb9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vincenthsh/fogg/releases/tag/v0.78.0 :sunflower:


User defined error messages

error should be a built-in function that accepts two arguments. The first should be a type, and the second  a []char. When doing type verification, this expression will emit the second argument as a diagnostic, but will be determined to have it's first argument as a type.
For example,
sizeof ::= (T: type) -> u64 {
  if (T == bool) {
    return 1
  } else {
    return error(u64, "Only bool is currently supported")
  }
}

We might also want a non-expression version. Maybe this is just a one-argument version (only the []char message).

Would this be similar to the panic!() macro from Rust?

No, this is for generating compile-time diagnostics. Functions calling this cannot be called at runtime. This would allow library authors to emit better diagnostics for compilation errors using their libraries.

Ah, so more akin to static_assert from C++?


Error:(2) Attribute "contentPadding" has already been defined

hi
i get this error when i can build project :
Error:(2) Attribute "contentPadding" has already been defined
whats problem ?
tanx

Hi,
The issues was attribute name was conflicting with other.
I have updated attributes with 'cmv_' prefix, now it should work fine.
try new version, 1.0.2.
Thanks


environment setup

Hi!
We are working on a project that is trying to implement this model. However, we are unable to set up the environment.
¨pip3 install -r requirements.txt" fails due to unknown versions of which I can tell are ubuntu packages.
The Dockerfile is incomplete and we cannot make it run without some further information about the actual environment used.
Could you please explain in a bit more detail on how to get the environment running? Thanks!

Hello, I am sorry that you have trouble setting up the environment. Unfortunately, I cannot access the original environment anymore; I know we worked on Ubuntu, but that is the only information I remember. If, in your case, setting up the environment through  pip3 install requirements.txt or using the Dockerfile does not work, I think installing manually the Python and PyTorch packages given in the Dockerfile would be enough to make everything work.

Hey, thank you very much. I will try to do it manually. Have a good day!


Failure to build w/ Bazel using Quickstart instructions for MacOS

Title: Failure to build when following Quickstart instructions
Description:
I tried making sure that I followed the Quickstart instructions to the tee a few times but it seems like there might be a real issue.
Versions
Bazel: 0.11.1-homebrew
Clang: Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>)
Output:
OK        Successfully built LuaJIT
==== Successfully built LuaJIT 2.0.5 ====
==== Installing LuaJIT 2.0.5 to /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build/ ====
mkdir -p /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//bin /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//lib /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//include/luajit-2.0 /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//share/man/man1 /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//lib/pkgconfig /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//share/luajit-2.0.5/jit /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//share/lua/5.1 /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//lib/lua/5.1
cd src && install -m 0755 luajit /private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/thirdparty_build//bin/luajit-2.0.5
/bin/sh: line 0: cd: src: No such file or directory
make[1]: *** [install] Error 1

real	0m8.028s
user	0m17.000s
sys	0m2.452s
make: *** [/private/var/tmp/_bazel_bobbytables/7637c96b2668502b7f32547fe5de8b36/external/envoy_deps_cache_2c744dffd279d7e9e0910ce594eb4f4f/luajit.dep] Error 1
DEBUG: /Users/bobbytables/OpenSource/envoy/bazel/repositories.bzl:84:5: External dep build exited with return code: 2
DEBUG: /Users/bobbytables/OpenSource/envoy/bazel/repositories.bzl:86:9:  External dependency build failed, check above log for errors and ensure all prerequisites at https://github.com/envoyproxy/envoy/blob/master/bazel/README.md#quick-start-bazel-build-for-developers are met.
ERROR: /Users/bobbytables/OpenSource/envoy/bazel/repositories.bzl:169:13: no such package '@envoy_deps//': External dep build failed and referenced by '//external:event_pthreads'
ERROR: /Users/bobbytables/OpenSource/envoy/bazel/repositories.bzl:169:13: no such package '@envoy_deps//': External dep build failed and referenced by '//external:event'
ERROR: Evaluation of query "deps(//source/...)" failed: errors were encountered while computing transitive closure

(It looks like a src directory doesn't exist when a cd is attempted)
I'm hoping this isn't me but if it is, sorry for the noise!

are you following this quickstart?
https://github.com/envoyproxy/envoy/blob/master/bazel/README.md#quick-start-bazel-build-for-developers

Yes.
On Tue, Mar 13, 2018 at 11:09 PM Nicholas Johns<EMAIL_ADDRESS>wrote:

are you following this quickstart?
https://github.com/envoyproxy/envoy/blob/master/bazel/README.md#quick-start-bazel-build-for-developers
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/2801#issuecomment-372890228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf1m_mGam9tHnNKQI_rV-b6YwiirYDNks5teIn4gaJpZM4Spt4n
.

--

Robert Ross

I'm not able to reproduce the issue; I have the same version of bazel and clang as you.  Unless someone else jumps in I would make sure you're on the latest version of master, clear the /private/tmp/_bazel* cache files, run bazel clean and try again.

Roger. I’ll do that in the morning. Thanks for the prompt response!
On Tue, Mar 13, 2018 at 11:23 PM Nicholas Johns<EMAIL_ADDRESS>wrote:

I'm not able to reproduce the issue; I have the same version of bazel and
clang as you. Unless someone else jumps in I would make sure you're on the
latest version of master, clear the /private/tmp/_bazel* cache files, run
bazel clean and try again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/2801#issuecomment-372892174,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf1myqbJeeOWLmepdOJzVeO6tmXsnIhks5teI1HgaJpZM4Spt4n
.

--

Robert Ross

@bobbytables I'm going to close this out. If it's still not working please hop into the osx-dev Slack room and hopefully someone can help out there.

This occurred for me because of my CDPATH env variable. Fix for me was:
rm -rf /private/var/tmp/_bazel_*
bazel clean -expunge
export CDPATH=""
bazel fetch //source/...

I had the same issue and unsetting my CDPATH was also the workaround


Ability to add custom tautulli port

I run tautulli on a different port than port 80. Is there a way to add a custom port to the config without having to change the python script?
requests.exceptions.ConnectionError: HTTPConnectionPool(host='docker.lan', port=80): Max retries exceeded with url: /api/v2?apikey=xxxxxxxxxx&cmd=get_activity (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f80156f6eb8>: Failed to establish a new connection: [Errno 111] Connection refused',))

I'm having no problems just putting that under the url like so:
[tautulli-1]
url = tautulli:8181

@chvvkumar @Grygon is using the proper way

Thank you, that works! I was expecting a seperate line for port specification based on how the other sections were setup :)


Enable building E57Format as a shared library

@pscamodio could you please try this to see if it works for you?
The main differences from your PR are:

It doesn't set BUILD_SHARED_LIBS as an option, but it will respect it. (I don't like libraries polluting the cmake option-space.)
It uses GenerateExportHeader instead of hand-coding the include. This will generate the appropriate include based on the platform (__attribute__((visibility("hidden"))), etc.).

Thank you.
Everything works no.
Your library was the only reason for me to keep xerces around in my codebase.
Now I can package your library as a dll with xerces statically compiled inside and remove one public dependency from my tree.
Thank you

Thanks for prompting this change with your PR @pscamodio!
I would love to eliminate Xerces, but it's so embedded in this code it's not easy. I started to do it, but it really needs a rewrite.


adding instagram and discord in social media

What would you like to share?
adding instagram and discord in social media
Additional information
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

please assign this to me, thank you.

Heyy! Please assign this to me, Thank you!

@Rakesh9100 Issue #1257 already exists. Can be marked as duplicate & closed.

Pls do not create a PR until you have been assigned to an issue @Nihal4777


Generated RelationFilter not allowing null values after seemingly unrelated relation additions

Bug description
I hit an issue where performing a query like prisma.group.findMany({where: {activeGroup: {isNot: null}}}) would fail, only after adding some seemingly unrelated relations.
It seems to boil down to having this in the generated client code:
  export type ActiveGroupRelationFilter = {
    is?: ActiveGroupWhereInput
    isNot?: ActiveGroupWhereInput
  }

instead of this:
  export type ActiveGroupRelationFilter = {
    is?: ActiveGroupWhereInput | null
    isNot?: ActiveGroupWhereInput | null
  }

My schema is below.
The null options re-appear in the client code if I remove either of these pairs of relations:

FriendRequest.fromActiveGroup and ActiveGroup.outgoingFriendRequests
GroupMembership.group and Group.memberships

It seems incorrect that creating these additional relations, and especially why creating the combination of them, leads to the optionality filter on Group.activeGroup becoming impossible to use due to the type change of ActiveGroupRelationFilter.
How to reproduce

Create a project with the above schema
Run prisma generate
Observe the lack of null options in the client code
Remove one of the mentioned pairs of relations
Observe that the null option is back

Expected behavior
Queries such as prisma.group.findMany({where: {activeGroup: {isNot: null}}}) should work even adding the additional relations.
Prisma information
Schema:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://app:app@postgres:5432/app"
}

model Group {
  id           Int    @id @default(autoincrement())
  createdAt    BigInt
  destructTime BigInt
  profileId    Int    @unique
  inviteToken  String @unique

  activeGroup            ActiveGroup?
  memberships            GroupMembership[]
}

model ActiveGroup {
  id      Int @id @default(autoincrement())
  groupId Int @unique

  group Group @relation(fields: [groupId], references: [id])
  outgoingFriendRequests FriendRequest[]
}

model FriendRequest {
  id          Int    @id @default(autoincrement())
  fromActiveGroupId Int
  toActiveGroupId   Int
  time        BigInt

  fromActiveGroup ActiveGroup @relation(fields: [fromActiveGroupId], references: [id])

  @@unique([fromActiveGroupId, toActiveGroupId])
}

model GroupMembership {
  id               Int @id @default(autoincrement())
  registeredUserId Int
  groupId          Int

  group          Group          @relation(fields: [groupId], references: [id])
}

Environment & setup

OS: MacOS
Database: PostgreSQL
Node.js version: 18.7.0

Prisma Version
prisma                  : 4.3.1
@prisma/client          : 4.3.1
Current platform        : linux-arm64-openssl-3.0.x
Query Engine (Node-API) : libquery-engine c875e43600dfe042452e0b868f7a48b817b9640b (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c875e43600dfe042452e0b868f7a48b817b9640b (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core c875e43600dfe042452e0b868f7a48b817b9640b (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt c875e43600dfe042452e0b868f7a48b817b9640b (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.3.0-32.c875e43600dfe042452e0b868f7a48b817b9640b
Default Engines Hash    : c875e43600dfe042452e0b868f7a48b817b9640b
Studio                  : 0.473.0

So far, I've worked around this issue by updating all my queries similar to:
prisma.group.findMany({where: {activeGroup: {isNot: null}}})
to be similar to:
prisma.group.findMany({where: {NOT: {activeGroup: null}}})
It's a bit clunky but seems to be doing the job for now.

Just ran into this issue as well, also due to an unrelated change in the schema.
Upgraded to the new v4.4.0 version, issue persisted there.
But the workaround by @tkeith seems to be working for now (thanks!)

Should return type also be non-null? For example:
prisma.group.findMany({
  where: { activeGroup: { isNot: null } },
  include: {
    activeGroup: true
  }
});

The return type of this still has group.activeGroup: ActiveGroup | null when it should not be null?


Expose the player's own position via Avatar OSC parameters

What's the idea?*
Basically, similar to VelocityX/VelocityY/VelocityZ parameters, I would like to be able to read PositionX/PositionY/PositionZ parameters.
Using the world space constraint technique, this would allow me to create network-synced world space props that work for late joiners, by using animator parameters to represent the X/Y/Z position of the prop. In order to know where to place the prop, I need to be able to see the coordinate system of the world, and reporting the current player position seems like a good reference point to use.
I have a prototype of this prefab up here: seanedwards/vrc-worldobject
Is there another way?
I can probably get the world space position another way, such as a gameobject+shader that renders its own world space orientation/position.

Second this!
I'm currently making an OSC drone system to sync camera coordinate from Unity into VRC.
If we have output for player position and rotation, we could do player auto tracking or auto focusing, It will be highly beneficial for VRChat machinima or cinematic filming.
OSC Drone Demo:
https://twitter.com/YanKMW/status/1497074496867807232

an YAngle to complement AngularY would be great as well.

This would be great, it would allow for Quest-compatible world space objects on avatars (as said above) with only the need for avatar support and a mobile app or computer program :+1:


Switch  section

AnimatedSwitch - UISwitch which paints over the parent view with the color in Swift. :large_orange_diamond:
ViralSwitch - A UISwitch that infects its superview with its tint color.
JTMaterialSwitch - A customizable switch UI with ripple effect and bounce animations, inspired from Google's Material Design.
TKSwitcherCollection - An animate switch collection :large_orange_diamond:
SevenSwitch - iOS7 style drop in replacement for UISwitch. :large_orange_diamond:
DGRunkeeperSwitch - Runkeeper design switch control (two part segment control) :large_orange_diamond:
PMZSwitch - Yet another animated toggle :large_orange_diamond:
Switcher - Custom UISwitcher with animation :large_orange_diamond:
BetterSegmentedControl - An easy to use, customizable replacement for UISegmentedControl & UISwitch. :large_orange_diamond:

@dkhamsing @vsouza approve?

nice job!

@lfarah yes 👍


lxd/apparmor: Deref compress commands

Closes #10724
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

FYI: you have a typo in Closes so it probably wouldn't auto-close upon merge

Fixed the typo :)

@tomponline good to go


Issue 771

Coverage increased (+0.02%) to 91.109% when pulling<PHONE_NUMBER>d52ab5539f76a407b85e69059517c5 on issue-771 into ff7febf3f966b1a9917b17f4f96223a5e8f24bc1 on master.

@homu r+

:pushpin: Commit 7144419 has been approved by kbknapp

:hourglass: Testing commit 7144419 with merge ff5d1a7...

:sunny: Test successful - status


How to import cfg from from maskrcnn_benchmark??

❓ Questions and Help
Sorry to ask a stupid question:
I am confused by  following code in the given demo webcam.py:
from maskrcnn_benchmark.config import cfg
Firstly, there is no maskrcnn_benchmark folder in current directory;
Secondly , the installed package named maskrcnn-benchmark ,instead of maskrcnn_benchmark ,it can not be called directly
Using ipdb to debug,and I figure out the location.....

Why in yacs???the code doesn't call it at all .....

I find that the constructor of  class CfgNode(dict)  in config.py  has been called for 18 times before  cfg.merge_from_file(config_file).....
What it is that happens before loading cfg??

Did you follow the installation steps? If everything works fine, you should be able to run import maskrcnn_benchmark from any folder.
When you run from maskrcnn_benchmark.config import cfg, the CN() constructor is called 18 times, you can verify it here.

Did you follow the installation steps? If everything works fine, you should be able to run import maskrcnn_benchmark from any folder.
When you run from maskrcnn_benchmark.config import cfg, the CN() constructor is called 18 times, you can verify it here.

Thanks for your reply , it really helps!

Closing following to the comments from @LeviViana
If you can't import maskrcnn_benchmark, this means that your installation didn't succeed.

@LeviViana I followed the linked installation steps (option 1) with one edit - changed cudatoolkit to 10.0. However, when I try to run Mask_R-CNN_demo.ipynb in demo, I get this:

I'm not quite sure this isn't working. Any help is appreciated.


ssh: Support newer host key signatures

Right now I only get
debug2: host key algorithms: ssh-rsa,ssh-dss
from gitblit SSHD.
Fedora 33 has changed, it will not accept ssh-rsa (from the server) anymore:
debug1: Offering public key: /home/XXXX/.ssh/id_rsa RSA SHA256:XXXXXXXXXXXXXX agent
debug1: send_pubkey_test: no mutual signature algorithm
Workaround: Set this in .ssh/config:
Host HOSTNAME
PubkeyAcceptedKeyTypes +ssh-rsa
I think SSHD is capable of newer host key sigs

Thank you for reporting it and including a workaround.
Support will be included when PR #1272 is merged. But I guess we need to make sure that the initial server keys get generated with the new chipers, too, so this issue is left as the reminder to implement that.

This just came up on the public Git mailing list. Public key authentication fails because the user is on OpenSSH 8.8, which disables ssh-rsa by default. (Fedora jumped on this early, but it's starting to hit more Linux distributions now.)


getArtifacts method returns a list of Strings

corresponds to https://github.com/WASdev/ci.common/pull/50

this change is handled in https://github.com/WASdev/ci.maven/pull/479


feat: ensure messages from connected peers are always emitted

issue#800

Codecov Report

Merging #806 (52995a6) into main (e846fbb) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #806      +/-   ##
==========================================
- Coverage   73.12%   73.06%   -0.06%
==========================================
  Files         274      274
  Lines       28435    28444       +9
==========================================
- Hits        20794    20784      -10
- Misses       7641     7660      +19

Flag
Coverage Δ

unit-tests
73.06% <100.00%> (-0.06%)
:arrow_down:

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

Impacted Files
Coverage Δ

crates/net/network/src/session/active.rs
83.79% <100.00%> (+0.29%)
:arrow_up:

crates/transaction-pool/src/test_utils/mock.rs
53.11% <0.00%> (-6.60%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.87% <0.00%> (-0.50%)
:arrow_down:

crates/net/network/src/manager.rs
49.15% <0.00%> (+0.21%)
:arrow_up:

crates/stages/src/stages/bodies.rs
93.56% <0.00%> (+0.38%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

how does cloning help here

the buffer size is configured buffer + num senders, by cloning the sender you're getting an additional slot for  the message.
fine with renaming, but unsure to what


Attestations: Email/Phone/Facebook/Twitter

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:
After this PR, I will work on re-defining our verification API using a new library; see https://github.com/OriginProtocol/bridge-server/issues/21

This updates the phone verification to return an actual signature for the attestation. The signature is compatible with the current implementation of ERC725 that we're using.
Adds email verification using Sendgrid
Adds Facebook & Twitter verification using Oauth

Finishes https://github.com/OriginProtocol/bridge-server/issues/22

All of these commits are in https://github.com/OriginProtocol/bridge-server/pull/28 so I'm going to close this and just use that branch. It's a lot of code but it's been reviewed pretty well at this point.


Fix error in validateResponse

fix array key not found issue if params key is not existing in response body

@Evoolo https://github.com/Attestto-com/solana-php-sdk/actions/runs/11785997510/job/33347649654?pr=14


Unable to set partitionKeyExpression for default properties (application fails to start)

Hi,
A configuration that worked with Spring Cloud Egware SR2 and Spring Cloud Stream Ditmars SR3 no longer works with Spring Boot 2, Spring Cloud Finchley M7 and Spring Cloud Stream Elmhurst RC2.
I have this in my application.yml
spring:
  cloud:
    stream:
      default:
        group: foo.bar
        contentType: application/json;charset=UTF-8
        producer:  &defaultProducerBindings
          headerMode: raw
          partitionCount: 12
          partitionKeyExpression: headers[ T(foo.bar.PayloadGateway).PARTITION_KEY ].getBytes()
      bindings:
        output:
          producer: *defaultProducerBindings
          destination: foo-bar

On launching my Spring Boot 2 application, it fails with this message:
Description:

Failed to bind properties under 'spring.cloud.stream.default.producer.partition-key-expression' to org.springframework.expression.Expression:

    Property: spring.cloud.stream.default.producer.partitionkeyexpression
    Value: headers[ T(foo.bar.PayloadGateway).PARTITION_KEY ].getBytes()
    Origin: class path resource [config/application.yml]:16:35
    Reason: No converter found capable of converting from type [java.lang.String] to type<EMAIL_ADDRESS>org.springframework.expression.Expression]

Action:

Update your application's configuration

If, however, I move the expression into the specific binding, my application starts (although at a cost of line duplication for many, many bindings (of the partitionKeyExpression line))
spring:
  cloud:
    stream:
      default:
        contentType: application/json;charset=UTF-8
        producer:  &defaultProducerBindings
          headerMode: raw
          partitionCount: 12
      bindings:
        output:
          producer:
            <<: *defaultProducerBindings
            partitionKeyExpression: headers[ T(foo.bar.PayloadGateway).PARTITION_KEY ].getBytes()
          destination: foo-bar

On stepping through the code, in the first example, the partitionKeyExpression is set on ProducerProperties. Of course, it is also set in the second binding-specific example.
Has this behaviour changed, if so and is intentional, then no problemo :-) Otherwise, I would expect the same configuration as before to still work.
Thank you.
-=david=-

@dharrigan at first glance this looks like boot issue. Also I am not sure how you got Boot 2.0.0.RELEASE to work with Finchley.M& and Stream RC2. That combination wasn't working due to last minute changes in boot. Anyway, please update to Finchley.M8. Meanwhile I'll dig some more

Also, I am suspecting that partially this could be due to the fact that "web" dependencies are now optional which may seem to be irrelevant to this issue at first but they do bring some json dependencies
Try to add this dependency back
<dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
</dependency>

Hi,
That caught me out too initially (I wondered why my /acutator/health wasn't working, even although I brought in the actuator starter). However, they are have been there for a few days now (whilst I'm looking to move to Spring Boot 2) and it makes no difference - the application still reports the same error on startup and fails.
build.gradle.kts
    implementation("org.springframework.boot:spring-boot-starter-json")
    implementation("org.springframework.boot:spring-boot-starter-web")

-=david=-

@dharrigan I've identified and fixed the issue, so please give it a try
I've also raised another issue for 2.1 https://github.com/spring-cloud/spring-cloud-stream/issues/1298 to revisit our entire approach on bootstrapping default properties.

Hi,
That was quick! Thank you! I will certainly retest it shortly.
-=david=-

@dharrigan please do and let us know as we're about to cut RC3

Testing now - I persume I need a particular snapshot version?

Not sure if the snapshots have been synchronized yet, give it a shot, but to be sure:
$> git clone git@github.com:spring-cloud/spring-cloud-stream.git
$> cd spring-cloud-stream
$> rm -rf ~/.m2/repository/org/springframework/cloud/spring-cloud-stream
$> ./mvnw clean install -DskipTests

The above will definitely build and install into your local maven repo the latest snapshots

Hi!
Put this as my gradle dependency "Elmhurst.BUILD-SNAPSHOT". It brought down the correct version with the changes you applied to the BindingServiceProperties. Moving the partitionKeyExpression back to the spring.cloud.stream.default.producer config map worked. My application started up successfully.
I would say that's done :-)
-=david-

You're most welcome.

I am facing this issue with Hoxton.SR1. Its working in some applications and not working in some with same version.


Control the amount of resources consumed by Worker pods

Context

Dissecting network traffic is resource-intensive, requiring substantial CPU and memory.
High traffic volumes lead to significant resource consumption.
Kubeshark sets strict CPU and memory usage limits, causing CPU throttling or pod termination (OOMKilled) when these limits are exceeded.
Resource usage varies with cluster load, making it difficult to control; this can result in frequent OOMKills of worker pods if limits are breached.

Request

Implement a mechanism to control traffic dissection volume, thereby managing resource usage. For instance, with an 80% setting, only 80% of L4 streams would be dissected.
Prevent the exhaustion of resource limits.
Allow users to set a dissection value that could be full, auto, or a percentage. "Full" would dissect all traffic, "Auto" would dynamically reduce L4 stream analysis to stay within resource limits, and a specific percentage (like 80%) would define the proportion of traffic to be dissected.
Ensure non-dissected traffic is still captured, exportable, and analyzable in Wireshark (using the traffic redcorder feature).

Additional Strategies for Resource Management
Utilizing BPF Filters
Encourage users to apply pod regex or namespace filters to drop irrelevant traffic, aiding in resource management.
Adopting PF-RING
Switching to PF-RING from AF_PACKET can enhance efficiency. PF-RING is less memory-intensive as it avoids the excessive memory usage seen with AF_PACKET, which occurs when it retains numerous incomplete connections.

https://docs.kubeshark.co/en/performance


[Proposal] Move to version 1.0.0 to fix projects that depend on SAELens using caret ^ with semver

Proposal
Move the version number to 1.0.0. This does not propose any code changes.
Motivation
sae_vis depends on saelens and uses caret notation ^0.5.0 to pick up SAELens. However, SAELens is now 0.6.0 and it is not picking up 0.6.0. This is because the caret works differently for projects that are lower than v1.0.0 - the caret will allow only 0.5.0 to 0.5.x, not anything 0.6.0 or above.
This means that sae_vis and other projects that depend on SAELens will not pick up 0.6.0 and later unless they specifically update their package dependency version to ^0.6.0.
Pitch
Move the version number to 1.0.0, and use the convention of major.minor.patch where MAJOR = backward incompatible changes, MINOR = backward compatible feature updates, PATCH = backward compatible fixes.
Alternatives
An alternative is to stick with version <1.0.0, but make sure that:

In an update from v0.x.y to v0.x+1.y, ensure that this is actually a backward incompatible change. Otherwise update it to v0.x.y to v0.x.y+1 instead.
Document what the backward incompatible change is when v0.x.y is updated to v0.x+1.y

Additional context
Additional context here (it's on a node blog but semver works the same way), which addresses the debate in general.
The main reason to not move to 1.0.0 is that the maintainer may not think it's "finished" or "ready enough" in a way that others might think a 1.0.0 might require. This is pretty subjective, I leave that up to the maintainers to decide this. I think at the very least, we should do the alternative mentioned above.
Checklist

[x] I have checked that there is no similar issue in the repo (required)

I'd support releasing 1.0.0 and just being diligent about bumping the major version whenever there's a breaking change. That could mean a lot of major version bumps potentially, but just being ruthless and unsentimental about using the major/minor/patch versioning to signal upgrade compatibility is one of the points of semantic versioning anyway. Having code in the pre-1.0.0 state feels confusing since it's less clear if a minor version means a breaking change or not. I guess being pre-1.0.0 is basically declaring the code to be unstable, but it's sort of a cop-out imo and we should just use semantic versions to communicate clearly.
As a side note, it seems troubling that sae_vis depends on SAELens, since SAELens also depends on sae_vis. Are there any issues with circular dependencies between projects like this?

note: added an issue to sae_vis for the circular dependency issue https://github.com/callummcdougall/sae_vis/issues/42

i noticed that python-semantic-release is now bumping the second number in the version when a "feat:" is committed, so anyone including saelens as a package won't pick up the new version (even though it's backward compatible) unless they manually change their pyproject. this makes me a little hesitant to use "feat:" because i don't want to make each release force other people to immediately be on outdated saelens.
it seems like the maintainers of that library feel strongly about starting packages at 1.0.0 according to this discussion: https://github.com/semantic-release/semantic-release/issues/1507
do we have agreement to bump to 1.0.0? i don't want to force a decision since it's a subjective call, but in the meantime i'll avoid using "feat" in the commit messages.

I just pushed an empty commit to bump to v1.0.0, seems like the right thing to do 👍


Uncaught TypeError: cannot read property of null (reading 'useState')

I'm trying to publish a reactjs component package following an awesome tutorial by @alexeagleson, however when i try to test the package in another project, nothing displays and I get the following error...

I have searched for solutions to no avail. What am I doing wrong and how do I get it fixed?
This is my package.json file.. and  my Component file...
  "name": "@okafohenry/react-custom-select",
  "version": "0.0.12",
  "description": "Custom-select: A react component library",
  "scripts": {
    "rollup": "rollup -c"
  },
  "author": "Henry Okafor",
  "license": "ISC",
  "devDependencies": {
    "@rollup/plugin-commonjs": "^24.0.1",
    "@rollup/plugin-node-resolve": "^15.0.1",
    "@rollup/plugin-typescript": "^11.0.0",
    "@types/react": "^18.0.28",
    "react": "^18.2.0",
    "rollup": "^3.20.0",
    "rollup-plugin-dts": "^5.3.0",
    "tslib": "^2.5.0",
    "typescript": "^5.0.2"
  },
  "dependencies": {
    "react-icons": "^4.8.0"
  },
  "main": "dist/cjs/index.js",
  "module": "dist/esm/index.js",
  "files": [
    "dist"
  ],
  "types": "dist/index.d.ts",
  "publishConfig": {
    "registry": "https://npm.pkg.github.com/okafohenry"
  }
}

import React, { useState } from "react";

const CustomSelect = (props: PropsData) => {
  const [ dropdownToggle, setDropdownToggle ] = useState<boolean>(false);

   return(...)
}

Try seperating import statements for react and usestate.

@okafohenry, You need to add the react as peer dependency.

Try seperating import statements for react and usestate.

I tried this, it  didn't work.
No difference at all

@okafohenry, You need to add the react as peer dependency.

Do I need to make the change in package-lock.json ? because the issue still persists

Try seperating import statements for react and usestate.

@Soulpurr I tried this but it didn't work as well

@okafohenry, You need to add the react as peer dependency.

@Ashish-simpleCoder This seemed like the most likely cause, however it didn't resolve my issue.
I also noticed that in the package-lock.json, react remained in the devDependency block


Unreal crash when drawing 3D Tiles

Hi,
We are trying to visualize 3D Tileset https://fileserv.beta.geodan.nl/test/unreal_test/tileset.json in Unreal 5.0.2 with Cesium plugin 1.14.0
but there is a crash when Unreal tries to draw.
Stacktrace:
Unhandled Exception: 0xe06d7363

KERNELBASE
VCRUNTIME140
msvcp140
UnrealEditor_CesiumRuntime!std::_String_val<std::_Simple_types<char> >::_Xran() [C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\INCLUDE\xstring:2337]
UnrealEditor_CesiumRuntime!Cesium3DTilesSelection::Tile::processLoadedContent()
UnrealEditor_CesiumRuntime!Cesium3DTilesSelection::Tileset::_visitTileIfNeeded()
UnrealEditor_CesiumRuntime!Cesium3DTilesSelection::Tileset::_visitTile()
UnrealEditor_CesiumRuntime!Cesium3DTilesSelection::Tileset::_visitTileIfNeeded()
UnrealEditor_CesiumRuntime!Cesium3DTilesSelection::Tileset::updateView()
UnrealEditor_CesiumRuntime!ACesium3DTileset::Tick() [D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp:1631]
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

So it looks like there is something going wrong in D:\build\U5M-Marketplace\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp:1631
In Cesium the tileset is visualized correctly: https://fileserv.beta.geodan.nl/test/unreal_test/index.html

Update: I've tried to simplify the issue by removing from the glTF custom vertex attributes, Draco compression and trying other renderers but in all cases Unreal keeps crashing.
I've got the impression there is something in the glTF what triggers the crash, although the glTF's are valid without warnings (https://github.khronos.org/glTF-Validator/)

A minimal reproducible case:

Cesium viewer: https://bertt.github.io/cesium_unreal_samples/crash

Tileset.json: https://bertt.github.io/cesium_unreal_samples/crash/tileset.json

Glb: https://bertt.github.io/cesium_unreal_samples/crash/crash.glb

When loading tileset.json in Unreal there is a crash.
Sample wich does not crash in Unreal: https://bertt.github.io/cesium_unreal_samples/nocrash/

@bertt thanks for reporting this issue. We've included a fix for it in v1.15.0, which was released at the end of last week.


move trust for ProductBinaries to Unrestricted.

fixes #5485

Causes Restricted and AllSigned execution policies to no longer trust PSHome by default.
To prevent behavior changes to Unrestricted, the trust for PShome was added here.
Update the description of Unrestricted to indicate that it requires the shell (an existing requirement.)

Can we add a test?

Note, issue #5559 was filed when adding tests due to an issue with the tests.  I have marked the affected tests to be skipped.


client send message sequence is out of order?

i did the  test case in example_rpc_client and found it  was abnormal,  the first call helloworld is send at last, who can tell me the reason?
the print result in server is below:
./hg_example_rpc_server verbs
svr address string: "ofi+verbs;ofi_rxm://<IP_ADDRESS>:53128"
Got RPC request with input_val: 1
Got RPC request with input_val: 2
Got RPC request with input_val: 3
Got RPC request with input_val: 0
my_rpc_handler_bulk_cb: Hello world! +1
my_rpc_handler_bulk_cb: Hello world! +2
my_rpc_handler_bulk_cb: Hello world! +3
my_rpc_handler_bulk_cb: Hello world! +0
Got RPC request with input_val: 1
Got RPC request with input_val: 2
Got RPC request with input_val: 3
Got RPC request with input_val: 0
my_rpc_handler_bulk_cb: Hello world! +1
my_rpc_handler_bulk_cb: Hello world! +2
my_rpc_handler_bulk_cb: Hello world! +3
my_rpc_handler_bulk_cb: Hello world! +0
the print result in client is below:
./hg_example_rpc_client verbs ofi+verbs://<IP_ADDRESS>:52200
start
Got response ret: 0, from 1
Got response ret: 0, from 2
Got response ret: 0, from 3
Got response ret: 0, from 0
./hg_example_rpc_client verbs ofi+verbs://<IP_ADDRESS>:61323
start
Got response ret: 0, from 1
Got response ret: 0, from 2
Got response ret: 0, from 3
Got response ret: 0, from 0
./hg_example_rpc_client verbs ofi+verbs://<IP_ADDRESS>:61323
start
Got response ret: 0, from 0
Got response ret: 0, from 1
Got response ret: 0, from 3
Got response ret: 0, from 2

RPCs are sent in order but there is no guarantee that they'll be received in the same order unless we wait for each RPC to complete before sending the next one etc, which is not what this example is doing, it's sending all RPCs in order but then waits for all completions at the same time by calling HG_Progress(). In general, there are multiple reasons why this could happen but in this particular case, I would assume the first RPC hit a EAGAIN because of the libfabric connection manager and was retried internally while the others went through.

@soumagne  thanks  maybe the libfabric is poor compatibility，we use ucx no this problom，thanks  close this issue


Platform: alias math constants on Windows

The non-C/C++ standard defined math constants require
-Xcc -D_USE_MATH_DEFINES when using the ucrt module.  Instead,
provide them through the wrapper MSVCRT module as aliases so that the
user does not need to be aware of this in practice.
Repairs the Windows build of _Differentiation.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @ematejska @dan-zheng @marcrasi

@swift-ci please test Windows platform

@swift-ci please test macOS platform

Please test with following PRs:
apple/llvm-project#1057
@swift-ci please test Linux platform


Cloudinit Images not consistently deleted

When running terraform destroy, cloudinit images will occasionally fail to be deleted. Any subsequent runs will fail redeploying the resources due to the disks already existing.

Can you provide evidences that is not related to you proxmox host configuration/issue?

I have the same issue, when constantly destroying and recreating a machine at the same id. There is no evidence in Proxmox itself, that it couldn't be deleted. Terraform will just state:
proxmox_vm_qemu.rke-machine-4: Destroying... [id=pve-ni-04/qemu/3056]
proxmox_vm_qemu.rke-machine-4: Destruction complete after 3s
proxmox_vm_qemu.rke-machine-4: Creating...
proxmox_vm_qemu.rke-machine-4: Still creating... [10s elapsed]
proxmox_vm_qemu.rke-machine-4: Still creating... [20s elapsed]
╷
│ Error: scsi0 - cloud-init drive is already attached at 'ide0'
│
│   with proxmox_vm_qemu.rke-machine-4,
│   on rke-machine-4.tf line 22, in resource "proxmox_vm_qemu" "rke-machine-4":
│   22: resource "proxmox_vm_qemu" "rke-machine-4" {
│

When you try to recreate your machine. It seems like the cloud-init disk isn't fully de-provisioned at the time of re-creation.

I'm seeing the same issue occasionally during terraform destroy: Error: scsi0 - cloud-init drive is already attached at 'ide0'

Same here and it's not consistent.
As mentioned by @Sm0rezDev at #704, by rolling back to 2.9.11 the issue is mitigated.

not stale

Same issue here

not stale


installation guide

maybe a full installation guide can help (kodi 18 agile + others prerequisites), mostly for who can't speak german and can't install libwidevine from the link in the readme

https://github.com/asciidisco/plugin.video.netflix/issues/30#issuecomment-290922066

very good.
maybe is better to insert this guide in the official readme?

@napgab I'd add it as a separate file. You're very welcome to do so.

Installation guides can be found in the wiki.

Installation guide only shows instruction for Raspberry Pi and Ubuntu. Is this not installable on Window 10 or MacOS?

This works on Windows 10 as well. I can't remember where to find the libwidevine for Windows and I'm surprised it's not mentioned here.


Passing credentials to a container

Wondering if someone might have ideas on how to deal with this scenario: I have a docker image that does a task but that needs credentials to write the output of that task to a shared resource, such as S3. I'd like to run that task as a container service from an application on CloudFroundry. So the application would issue a POST request to /v2/service_instances to create the service, it would run its process, and output the result to S3, and terminate. The benefit to this is the process would run in an isolated container instead of on the application.
I don't know how to pass the credentials and some other configuration from the application to the service. I was thinking the parameters attribute in the request body might allow for this, but I'm not sure how the service would use that data. Ideally it could be read through env variables.
Would love any thoughts on how this could work. Thanks.

If the S3 credentials are fixed for all applications, the easy way is to statically populate them at deploy time using the environment property of the container definition (see CONTAINERS.md). An example would be:
container:
  backend: 'docker'
  image: 'frodenas/postgresql'
  tag: 'latest'
  environment:
    - "AWS_ACCESS_KEY_ID=XXX"
    - "AWS_SECRET_ACCESS_KEY=XXX"

But I guess what you're looking for is to allow each application to provision and/or bind the service passing their own credentials. If this is the case, the Service Broker API v2.6 allows to pass some arbitrary provision parameters. Unfortunately, this broker does not accept yet arbitrary parameters. If you confirm me this is the use case you're looking for then I can update the broker to accept those parameters. The way it will work will be pretty simple, it will inject those parameters into the container using environment variables. An example api request with arbitrary parameters:
{
  "organization_guid": "org-guid-here",
  "plan_id":           "plan-guid-here",
  "service_id":        "service-guid-here",
  "space_guid":        "space-guid-here",
  "parameters":        {
    "parameter1": 1,
    "parameter2": "value"
  }
}

will be injected into the container as these environment variables:
PARAMETER1="1"
PARAMETER2="VALUE"

Let me know if this will work for you.

Hi @frodenas, thanks for this. That case is exactly what we're looking for. For us, the parameters are dynamic so setting them in the request and having them available as environment variables in the container solve this issue.

@dhcole I've just added support for service arbitrary parameters. If you are using the Docker BOSH release, update it to version 16, as it includes the latest cf-containers-broker code.

This is really great. Thanks so much for the quick response and updating the broker to support this.


Feat: Support uploading pdfs

@abi I wanted to discuss how you want to handle the UI for showing multiple images and the response for each image. If you want it separately or just in different sections in the same HTML.

@PiyushMishra318 is this PR still relevant? Is the goal to support multiple images? If so, I am interested in adding that ability.

Yes


Probe to check whether spotless is present or not

Description
The spotless is used the parent pom, that must be used by all jenkins plugins . Reference: https://github.com/jenkinsci/plugin-pom/blob/692c7757f468ea6b1ecf52a39edb8379020816c3/pom.xml#L109C4-L109C74

Please check @alecharp We need to check also the configuration is present or not to verify the spotless

That could be a good idea.

That could be a good idea.

I will take this

Closed after approval

That ticket would have to be recreated during GSoC. No need for this.
To anyone, please see that this ticket should only be addressed during GSoC 2024 if the project is selected.


Cache InfoEvaluator result.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.90%. Comparing base (5d388c1) to head (2495a1b).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #866   +/-   ##
=======================================
  Coverage   91.90%   91.90%
=======================================
  Files          92       92
  Lines       12585    12587    +2
  Branches    12585    12587    +2
=======================================
+ Hits        11566    11568    +2
  Misses        909      909
  Partials      110      110

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


Support v2 convention

There is a new convention in Wix for versioned modules with something like wix-{some domain}.v${someNumber}.
. is a bad delimiter, since it affects the model hierarchy, the autocomplete, and in the serviceJson, docs invented a new property called displayName which effects just the display name and nothing else.
we still want to model it in the same hierarchy, so after building the model of the module, we jsut want to name it differently (if the display name is provided in the service json).
it will affect only the root service json (which is a great thing for us).
I added a test for it here, and I tested in in wix-code-types (copied the builders.js code to the node modules) and it looks good (at least I think)

The mocked service jsons were taken from wix-code-docs repo (with minor adjustments)

Where do u decide which modules to ignore?

in wix-code-types (see here) we read the modules name from the model.json

Do you omit the @wix/ prefix?

yes. in here


Added shepherd_redshift role

Summary of Changes

Created a new role shepherd_redshift to allow RedShift to access S3/Athena

Tested and pushed changes. Merging into main.


transport: authentication handshake failed: EOF when supplied certificates

Proto file(s)
As in GRPC Java Hello World TLS from here
Command line arguments / config
./ghz --cacert=/tmp/sslcert/ca.crt --cert=/tmp/sslcert/client.crt --key=/tmp/sslcert/client.pem --proto ./jdk11/src/main/proto/helloworld/helloworld.proto --call helloworld.Greeter.SayHello -d '{"name":"world"}' -n 2000 -c 20 --connections=10 localhost:8071
Describe the bug
Took the exact same example from the repository without any changes. I then generated certificates necessary in my /tmp/sslcert as you can see. I dockerized the example on latest ubuntu with jdk8. That's all and I am not able to run ghz.
To Reproduce
Take same example from above, run it in docker and try the same command.
Expected behavior
A clear and concise description of what you expected to happen.
Environment

OS: macOS 10.14.4
ghz: 0.36.0

Screenshots
Not necessary.
Additional context
Logs if this helps:
mac:Downloads yeshwanths$ ./ghz --cacert=/tmp/sslcert/ca.crt --cert=/tmp/sslcert/client.crt --key=/tmp/sslcert/client.pem --proto ./example-tls/src/main/proto/helloworld/helloworld.proto --call helloworld.Greeter.SayHello -d '{"name":"world"}' -n 2000 -c 20 --connections=10 localhost:8071

Summary:
  Count:	2000
  Total:	32.88 ms
  Slowest:	0 ns
  Fastest:	0 ns
  Average:	0 ns
  Requests/sec:	0.00

Response time histogram:

Latency distribution:

Status code distribution:
  [Unavailable]   2000 responses

Error distribution:
  [2000]   rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: authentication handshake failed: EOF"```

Forgot to mention:
The script is not able to connect to docker. However, when same application is run outside docker works totally fine. Doesn't this feel weird?

Hello, thanks for opening this issue, I'll try and look into this. Please provide some more information. Specifically how is the server run as it seems to accept command line arguments? Also provide more information how the docker is created and run. For example make sure you're allowing / mapping ports properly. As well I would suggest that the server within the the Docker is started listenning on <IP_ADDRESS> because containers do not default to exposing mapped ports to localhost.

Apparently, there was an issue with my GRPC server and hence thats why it wasnt working when I exposed the port from docker. I have resolved it. Thanks for the support!

For anyone else stumbling upon this, I also had this issue. I dockerized my program that held the grpc listen server and needed to change the listen address from localhost to <IP_ADDRESS> so a seperate dockerized program could establish a connection to it. also ensure that you copy the cert the GRPC server generates for your other programs.

@bath thank you so much, I stumbled upon this issue minutes ago, and I'm fairly certain you just saved me hours of wondering what's wrong!


Enforce visibility

Would you have any appetite in cops to enforce visibility? checks for types, fields, arguments, mutations and arguments?
It seems that the current approach to visibility is to assume visible unless there's an explicit visible? check returns false.
But I can see value in requiring visibility to be set such that it works like an "allow list" instead of a "deny list".
This is something I'm exploring for our own project but if there would be value I can contribute upstream.

Hey! Sounds good, but probably we will make it off by default, what do you think? 🙂


Legacy Damage Sources are not correctly compared with apoli:name damage type condition.

Please refer to:
https://github.com/EdwinMindcraft/origins-architectury/issues/422

You may want to migrate this issue over to Apoli, I think it'd be easier tracked over there.


New lines aren't being applied

When using a text block it would be helpful if it supports new lines. Whenever I add a new line in the text, it's not applied in the design. Not sure if this is a conscious decision? Because of the not supporting of new lines, most blocks have to be converted to a HTML block, which feels overkill.

At the moment, we made the decision to use plain text for the text blocks. We may consider adding Markdown (like on our Pro builder) in the future – either as a separate block or as part of the text block.

Good news, we've added a 'Markdown' option on Text blocks to solve this. When turned on, it will process the text through a Markdown processor which will respect the line breaks and allow for basic formatting syntax.

Hope that helps!

Cool!


IE7 Fix word count on load and paste

Removed the on load word count which wasn’t needed
Fixed the paste word count

Lookks fine :+1:


(Major) Add autofil to the GitHub Actions workflow

Apparently yes @jfy133

My current idea:

Diff the table between master and the PR
Pull the new sample accession codes
Give to autofill

Problems: diff doesn't work when other formatting changes have occured (or people fix upstream mistakes)
New approach, request bot to filter for the table and the new project ID e.g. @spaam-bot please autofill ancientsinglegenome-hostassociated majander2024
Then can use that info to filter the table to prepare the autofill command

e.g.: grep 'Nishimura2024' ancientmetagenome-hostassociated/samples/ancientmetagenome-hostassociated_samples.tsv | rev | cut -f 1 | rev to get the new accessions

X-ref for bot: https://stackoverflow.com/a/70244956

Basic bash script:
#!/usr/bin/env bash

##
## AMDirT autofill wrapper for github actions
##
## Given a specified table and a project name, this script will
##
## 0. Check the specified table is valid name
## 1. filter the specified sample table for the given project name.
## 2. collect collect the sample accession IDs of that project
## 3. give error if there is no output (i.e., 0 accessions)
## 4. run AMDirT autofill with the collected accessions and the specified table name
##
## Copyright 2024 James Fellows Yates on behalf of the SPAAM community under MIT license

verbose=false

while getopts t:p:v flag; do
    case "${flag}" in
    v) verbose=true ;;
    t) table_name=${OPTARG} ;;
    p) project_name=${OPTARG} ;;
    esac
done

## TODO: check valid table name
if [ $verbose ]; then
    echo RUNNING: grep $project_name $table_name/samples/"$table_name"_samples.tsv "| rev | cut -f 1 | rev | tr '\n' ' '"
    echo ""
fi

hits=$(grep "$project_name" "$table_name"/samples/"$table_name"_samples.tsv | rev | cut -f 1 | rev | tr '\n' ' ')

if [ $verbose ]; then
    echo RUNNING: "${#hits} -eq 0"
    echo ""
fi

if [ ${#hits} -eq 0 ]; then
    echo 'Project name or sample accessions were not found in table. Please check project name input (-p).'
    exit 1
fi

if [ $verbose ]; then
    echo RUNNING: AMDirT autofill -n $table_name $hits -l TEMPLATE_$project_name_"$table_name"_libraries.tsv
    echo ""
fi

AMDirT autofill -n $table_name $hits -l TEMPLATE_$project_name_"$table_name"_libraries.tsv

Better version, see: https://github.com/SPAAM-community/AncientMetagenomeDir/pull/1145

TODO:
Parse the comment to extract the table name and project name

Done in  a variety of commits on master, the final being: https://github.com/SPAAM-community/AncientMetagenomeDir/commit/7d564e914c3c98c482c323490cb09052c7ea5755


Upload nightly built conda package

We are already building a conda package of the version2_development branch every night:
https://github.com/ESMValGroup/ESMValTool/blob/62807f38aa501da22f951ab915ea98d72da66691/.circleci/config.yml#L216
It would be nice if we could upload this package to the esmvalgroup conda channel, because installing esmvaltool from conda is much easier for users than from source, and that way they do not have to wait for a release to get the latest recipes.

I am trying this locally first then I will see what we can do to get it uploaded to the channel nightly, man

Hey @bouweandela -- some good news bro - I managed to create a conda package for esmvaltool and actually install the tool from the local channel (using that package):
# Name                    Version                   Build  Channel
esmvaltool                2.0a1                    py36_0    local

(this might be child's play for you but it's the first time I've done it!)
This is what I used:
mkdir logs
apt update > /logs/apt.txt 2>&1
apt -y install build-essential gfortran >> logs/apt.txt 2>&1
wget https://julialang-s3.julialang.org/bin/linux/x64/1.0/julia-1.0.3-linux-x86_64.tar.gz
tar xfz julia-*-linux-x86_64.tar.gz
ln -s $(pwd)/julia-*/bin/julia /usr/bin/julia
conda update -y conda > logs/conda_base.txt 2>&1
conda install -y conda-build conda-verify >> logs/conda_base.txt 2>&1
# Log versions
dpkg -l > logs/versions.txt
conda env export -n base > logs/build_environment.yml
# Build conda package
conda build . -c conda-forge/label/cf201901 -c birdhouse > logs/build_log.txt
# Install Python 3 conda package
conda create -y --name esmvaltool3 > logs/conda_esmvaltool3.txt 2>&1
set +x; conda activate esmvaltool3; set -x
conda install -y esmvaltool --use-local -c conda-forge/label/cf201901 -c birdhouse
conda env export > logs/test_environment3.yml
esmvaltool -h

in my case I had to do it on my local machine (laptop) since symlinking the julia path would not work on Jasmin (unless in a docker container); there were some issues that conda had to clobber paths - I started from an absolute pristine Anaconda base environment (ie the stock one that comes right after installing Anaconda, with no custom pkgs additions), but still had those errors, that were automatically fixed by conda. I ran a test with a real recipe and all works fine.
Now, a couple questions:

why are we still using the birdhouse channel?
can we upload and deploy this built package on a real conda channel soon? (ie conda-forge)

right birdhouse is only for yamale
valeriu@valeriu-PORTEGE-Z30-C:~$ conda install -c local -c conda-forge/label/cf201901 esmvaltool
WARNING: The conda.compat module is deprecated and will be removed in a future release.
Collecting package metadata: done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - esmvaltool -> yamale

come one, surely we can find that one somewhere else, birdshit is not to my linking :grin:

OK, a few more points:

the user actually needs to install esmvaltool in its own environment; this is one one hand clunky and annoying since an installation in the base environment doesn't really work (I noticed a lot of weird older versions of dependencies not being updated and some not installed at all), on the other hand it's nice because it teaches users to have separate envs for separate work projects. I don't understand why the installation in base is not done correctly;
the execution of install to target is long - most of the time is spent installing the R packages (and they do splash a lot of stdout when they finish installing ughh) - can we maybe disentangle the installation with R packages in a separate package tarball and give it a special name eg esmvaltool-2.0a1-py36_1_r?
I am going to try put the conda tarball on a Jasmin channel, that'd make things easier to install esmvaltool at least on Jasmin

Let's close this since we are no longer building the nightly packages. People can just install from source if they want the very latest features.


Few issues

Just got this installed last night (comparing to Tesla-apiscraper) and had a few questions / issues:

My range shows 999 on the blue line for "Drive" dashboard. I was seeing something similar on Tesla-apiscraper, so it might be something with my data. But any way to resolve this?

Could we get an "overall" dashboard that combines a lot (or all) of the dashboards into a single screen? Could also help to rename some of the variables, as some of them look to be common names (Power, Speed, SOC) and then some look to be the attribute (fan_speed, is_climate_on).

Some of the stats on the Drives dashboard are missing (Consumption, Consumed, Efficiency, TR loss, TR start and TR end [these last two values seem to be the same]).

A few dashboards are blank, is this intended? It just started scraping data last night. Dashboards are: vampire drain, updates (I get that there is nothing there), efficiency,

Just wanted to say that this is amazing work and truly appreciate it. Please let me know how I can provide more details.

My range shows 999 on the blue line for "Drive" dashboard. I was seeing something similar on Tesla-apiscraper, so it might be something with my data. But any way to resolve this?

Never heard of this issue before. The range comes straight from the car. I'd suggest that you keep an eye on that. Feel free to report back after logging a few drives.

Could we get an "overall" dashboard that combines a lot (or all) of the dashboards into a single screen? Could also help to rename some of the variables, as some of them look to be common names (Power, Speed, SOC) and then some look to be the attribute (fan_speed, is_climate_on).

If you want to make a PR, please feel free! I'm sure there are a lot of other great ideas and I'd love to see PRs in the future. The same applies to incorrectly named / translated variables :)

Some of the stats on the Drives dashboard are missing (Consumption, Consumed, Efficiency, TR loss, TR start and TR end [these last two values seem to be the same]).

With short trips it sometimes not all information is available. Longer trips should show it, though.  Maybe that's related to the above issue with the 999 range?

A few dashboards are blank, is this intended? It just started scraping data last night. Dashboards are: vampire drain, updates (I get that there is nothing there), efficiency,

Blank dashboards = that data not (yet) available.

My range shows 999 on the blue line for "Drive" dashboard. I was seeing something similar on Tesla-apiscraper, so it might be something with my data. But any way to resolve this?

Never heard of this issue before. The range comes straight from the car. I'd suggest that you keep an eye on that. Feel free to report back after logging a few drives.

Will do. I will log a few more trips over the next few days, so will report back next week. Also performing a soft reboot now.

Could we get an "overall" dashboard that combines a lot (or all) of the dashboards into a single screen? Could also help to rename some of the variables, as some of them look to be common names (Power, Speed, SOC) and then some look to be the attribute (fan_speed, is_climate_on).

If you want to make a PR, please feel free! I'm sure there are a lot of other great ideas and I'd love to see PRs in the future. The same applies to incorrectly named / translated variables :)

Gotcha! Will look into a pull request to combine some of the dashboards. Will openly admin, I am no Linux or Github expert.

Some of the stats on the Drives dashboard are missing (Consumption, Consumed, Efficiency, TR loss, TR start and TR end [these last two values seem to be the same]).

With short trips, sometimes not all information is available. Longer trips should show it, though. Maybe that's related to the above issue with the 999 range?

Do you know "how long" it would be too register? When using another tool out there (TeslaScope) that was being registered each drive - regardless of how short or long (e.g. even a three minute drive was registered and equated).

A few dashboards are blank, is this intended? It just started scraping data last night. Dashboards are: vampire drain, updates (I get that there is nothing there), efficiency,

Blank dashboards = that data is not (yet) available. Edit: There should be empty a few tables etc on the effifiency dashboard ... could you provide a screenshot? How do you run Grafana (docker or manual installation)?

I was running Grafana locally when using Tesla-apiscraper. I had to stop it to have TeslaMate run via docker as there was a conflict. Trying to figure out to log into Grafana when running via Docker to do some of the dashboard modifications mentioned above. Although, I know those would be overwritten on updates. Screenshot provided.

Edit: soft reboot did not resolve it. Comparing it to the debug information from TeslaScope, I assume that Range (est.) is the est_battery_range on the charge_state table. Assuming that, I guess the Range (ideal) is the battery_range from the same table? If so, TeslaScope is pulling it correctly.

Range (ideal) corresponds to the ideal_battery_range. The next release (which is coming very soon) will also log the battery_range.

Gotcha! Will look into a pull request to combine some of the dashboards. Will openly admit, I am no Linux or Github expert.

Awesome! Exporting the dashboards should be relatively straight forward. Just put the exported json data in the grafana/dashboards directory.

Do you know "how long" it would be too register? When using another tool out there (TeslaScope) that was being registered each drive - regardless of how short or long (e.g. even a three minute drive was registered and equated).

Short as in a less than a minute. TR (=ideal_battery_range) measurements should always appear. Consumption related values can only be derived  if there is a known "efficiency factor" for your vehicle. The next release will add a new panel to the efficiency dashboard that enables us to crowdsource the missing factors.

I was running Grafana locally when using Tesla-apiscraper. I had to stop it to have TeslaMate run via docker as there was a conflict. Trying to figure out to log into Grafana when running via Docker to do some of the dashboard modifications mentioned above. Although, I know those would be overwritten on updates. Screenshot provided.

There is an error. What does it say?
Regarding Grafana: you can run it on another port. To do so change that line in the docker-compose.yml:
 ports:
      - 3000:3000

Range (ideal) corresponds to the ideal_battery_range. The next release (which is coming very soon) will also log the battery_range.

Saw your post in the other issue thread. I will update it once it is released.

A minute or less. TR (=ideal_battery_range) measurements should always appear. Consumption related values can only be derived if there is a known "efficiency factor" for your vehicle. The next release will add a new panel to the efficiency dashboard that enables us to crowdsource the missing factors.

Hmm. All three of my recorded drives were over one mile and one minute long. Will keep an eye out on it. Also noticing that this missing data / the 999 range is throwing off the vampire drain as well.

There is an error. What does it say?

When trying to start up via docker-compose and my manual Grafana install was running here was the error:
ERROR: for grafana  Cannot start service grafana: driver failed programming external connectivity on endpoint teslamate_grafana_1 (8836bf77d5faaf99ad4813272f3719c2f3f4d71b1a129f8b95e0fd00de46209a): Error starting userland proxy: listen tcp <IP_ADDRESS>:3000: bind: address already in use ERROR: Encountered errors while bringing up the project.

Regarding Grafana: you can run it on another port. To do so change that line in the docker-compose.yml:
 ports:
      - 3000:3000

I tried that and did not get 3001 to work. Never tried another port. I guess my issue is really that I cannot login to the docker Grafana version when it is running. Is there a documented username / password I am missing? Or is that only going to be achieved by making a pull request and modifying them locally. I then run into the issue of not having a data source, right? Again - total newbie here.

3001:3000 did not work? The teslamte/grafana images does not require you to login (it also pre-configures the data source etc.). However, there is a default user: admin:admin.

🤦♂ tried 3001:3000. My fault. Never the less, I paused Tesla-apiscraper while evaluating TeslaMate. So having my manual install of Grafana running at the same time is not as critical. But now knowing this, I guess I could and could help compare data 😄
Got logged in! Thanks.

:) Great! Just don't let them run permanently at the same time. It could cause your vehicle to not fall asleep anymore.
btw as I wrote in the other thread, there is now a beta release available

It could cause your vehicle to not fall asleep anymore.

She already has some issues falling asleep. Noticed that with TeslaScope, although I think that was more their polling / configuration. I can at least see that overnight, it went into an asleep state. But only for about 50 minutes or so. Did that three times, with a roughly 50 minute online state in-between each. Screenshot below.

Updating and running that version now.

Definitely something is going on with the range from the API / car. Still stuck at 999, post three more drives today and an overnight charging session. Throws off any of the tables or charts that tracks range (charing session, drives, vampire drain, etc.)
I tried to run a similar command from another comment with no luck.
teslapi:~/Documents/tesla-apiscraper $ curl --request GET --header 'Authorization: Bearer something' 'https://owner-api.teslamotors.com/api/1/vehicles/{id}/vehicle_data'

{"response":null,"error":"not_found","error_description":""}

If it makes a difference, it seems to say that my car has API version 6.

Do you know your Vehicle ID? If not I can help you get the steps to get this outlined. Was thinking a blog post in any case.  You can check out more on that here:
http://desigeek.com/blog/amit/2018/08/06/windows-tesla-auth-token-generator/
HTHs.
From: cwanja<EMAIL_ADDRESS>Reply-To: adriankumpf/teslamate<EMAIL_ADDRESS>Date: Friday, August 30, 2019 at 11:08 AM
To: adriankumpf/teslamate<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [adriankumpf/teslamate] Few issues (#125)
Definitely something is going on with the range from the API / car. Still stuck at 999, post three more drives today and an overnight charging session. Throws off any of the tables or charts that tracks range (charing session, drives, vampire drain, etc.)
I tried to run a similar command from another comment with no luck.
teslapi:~/Documents/tesla-apiscraper $ curl --request GET --header 'Authorization: Bearer something' 'https://owner-api.teslamotors.com/api/1/vehicles/{id}/vehicle_data'
{"response":null,"error":"not_found","error_description":""}
If it makes a difference, it seems to say that my car has API version 6.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @bahree - I actually got it working 😄 just had to figure out which ID it was - vehicle ID or the just ID. Ended up getting it working. Trying to chat with Tesla now regarding all of the mismatched data in the API to what my car should be. Really not sure they will be able to help.


SVG horizontal connectors breaking on zooming out

Hi Remco, Kudos for writing this one. :)
I have been using this for my current work. I have also added a minimap with this and some zoom features. But as soon as I zoom out to less than 1, the horizontal lines start breaking.

Do you know a way to fix this?

@shefaligupta hi, did you find the solution? I got the same problem with transform:scale the only one I seem to come up so far is to recalculate lines zoom based on scale value, but it works rather buggy...

@maxganiev - fixed it by only using zoom on the parent container instead of transform.
this.$refs.flowWrapper.style.zoom = 1;

@shefaligupta zoom has poor cross-browser compatibility, and is non-standard feature that is not recommended to use in production https://developer.mozilla.org/en-US/docs/Web/CSS/zoom
if you don't mind that - zoom can be an option, though it has bugs when drawing large schemas.
fyi, if you need cross-browser solution tested on large schemas - more than welcome to my repo (this is now moved to production and connected to real backend service)
https://github.com/maxganiev/flowy-draggable-vue
demo: https://schema-draggable.netlify.app/


deploy

Adding microservice based deployment
Adding deploy controller
Adding deploy CLI

Pull Request Test Coverage Report for Build 1112

60 of 461 (13.02%)  changed or added relevant lines in 7 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-8.2%) to 79.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datmo/cli/main.py
0
6
0.0%

datmo/config.py
2
13
15.38%

datmo/core/util/misc_functions.py
35
117
29.91%

datmo/core/controller/deploy/driver/microservice.py
0
135
0.0%

datmo/cli/command/deploy.py
0
167
0.0%

Files with Coverage Reduction
New Missed Lines
%

datmo/cli/driver/parser.py
1
91.3%

datmo/core/controller/task.py
2
88.7%

Totals

Change from base Build 1100:
-8.2%

Covered Lines:
4017

Relevant Lines:
5040

💛  - Coveralls

Pull Request Test Coverage Report for Build 1112

60 of 461 (13.02%)  changed or added relevant lines in 7 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-8.2%) to 79.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datmo/cli/main.py
0
6
0.0%

datmo/config.py
2
13
15.38%

datmo/core/util/misc_functions.py
35
117
29.91%

datmo/core/controller/deploy/driver/microservice.py
0
135
0.0%

datmo/cli/command/deploy.py
0
167
0.0%

Files with Coverage Reduction
New Missed Lines
%

datmo/cli/driver/parser.py
1
91.3%

datmo/core/controller/task.py
2
88.7%

Totals

Change from base Build 1100:
-8.2%

Covered Lines:
4017

Relevant Lines:
5040

💛  - Coveralls

Pull Request Test Coverage Report for Build 1112

60 of 461 (13.02%)  changed or added relevant lines in 7 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-8.2%) to 79.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datmo/cli/main.py
0
6
0.0%

datmo/config.py
2
13
15.38%

datmo/core/util/misc_functions.py
35
117
29.91%

datmo/core/controller/deploy/driver/microservice.py
0
135
0.0%

datmo/cli/command/deploy.py
0
167
0.0%

Files with Coverage Reduction
New Missed Lines
%

datmo/cli/driver/parser.py
1
91.3%

datmo/core/controller/task.py
2
88.7%

Totals

Change from base Build 1100:
-8.2%

Covered Lines:
4017

Relevant Lines:
5040

💛  - Coveralls

Pull Request Test Coverage Report for Build 1112

60 of 461 (13.02%)  changed or added relevant lines in 7 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-8.2%) to 79.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datmo/cli/main.py
0
6
0.0%

datmo/config.py
2
13
15.38%

datmo/core/util/misc_functions.py
35
117
29.91%

datmo/core/controller/deploy/driver/microservice.py
0
135
0.0%

datmo/cli/command/deploy.py
0
167
0.0%

Files with Coverage Reduction
New Missed Lines
%

datmo/cli/driver/parser.py
1
91.3%

datmo/core/controller/task.py
2
88.7%

Totals

Change from base Build 1100:
-8.2%

Covered Lines:
4017

Relevant Lines:
5040

💛  - Coveralls

Added new issue #268 to account for lowering of coverage, will address later


"Unknown filesystem type on /dev/mapper/docker-202" when trying to build image.

I'm trying to build a new image from one of my base images, and when build runs, it failed with something like this:
Step 1 : RUN npm install -g gulp karma-cli mocha coffee-script
Unknown filesystem type on /dev/mapper/docker-202:16-802820-5a81f86e959d602cfe6b7de45f497e59e05b80f0b8817eb780842dea7dd7fabc-init

I'm on Ubuntu 12.04.
$ docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64

I have my /etc/default/docker configured to pass -g /mnt/docker.
$ mount | grep '/mnt'
/dev/xvdb on /mnt type ext3 (rw,_netdev)

/dev/xvdb/ is backed by an Amazon EBS.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

docker info
Containers: 150
Images: 105
Storage Driver: devicemapper
 Pool Name: docker-202:16-802820-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop2
 Metadata file: /dev/loop3
 Data Space Used: 4.579 GB
 Data Space Total: 107.4 GB
 Data Space Available: 41.57 GB
 Metadata Space Used: 7.287 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.14 GB
 Udev Sync Supported: false
 Deferred Removal Enabled: false
 Data loop file: /mnt/docker/devicemapper/devicemapper/data
 Metadata loop file: /mnt/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-40-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 7.337 GiB
Name: ip-10-146-205-21
ID: WS7K:JB3C:5XHN:HGHN:BM7Y:Q3UA:I64G:P26V:MBMC:DDVG:AYYB:OLMU
WARNING: No swap limit support

uname -a
Linux ip-10-146-205-21 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Wasn't reported since, code changed a lot. Feel free to open a new issue if it's still a problem,


[mpir] Fix build errors under Linux

Fix one of https://github.com/microsoft/vcpkg/issues/32398 issue.
/mnt/vcpkg/buildtrees/mpir/src/428702d56e-def7e839da.clean/missing: line 81: makeinfo: command not found

[X] Changes comply with the maintainer guide.
[ ] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[X] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Compile test pass with following triplets:
x64-linux

I don't think there is a reason to "fix" mpir.
https://groups.google.com/g/mpir-devel/c/qTOaOBuS2E4/m/_8AQjEieAAAJ

Printing a warning will not fix the origina problem.

Printing a warning will not fix the original problem.

After I tested the installation of texinfo locally, mpir[core] was successfully installed on Linux.

Did you check if you can simply disable documentation?
The non-windows build of this port remains troublesome. It uses AUTOCONFIG on linux but not other platforms. Probably because it somehow worked for the original authors. Who probably weren't aware that this requires additional packages from the system. But vcpkg maintainers should be aware today because this regularly pops up for other ports, and then the portfiles become cluttered with more warnings...


Add support to linux arm

Adding support for linux on arm processors.
This is a follow-up to https://github.com/vallyian/protoc-binary/pull/2
After I made sure that it works as expected on my Mac I realized that it still does not work in docker environments where we use linux as a base image.
The current output is:
#0 22.31 Output:
#0 22.31 /service/node_modules/protoc-binary/install.js:12
#0 22.31         throw Error(`${process.platform}-${process.arch} unsupported`)
#0 22.31               ^
#0 22.31
#0 22.31 Error: linux-arm64 unsupported
#0 22.31     at install (/service/node_modules/protoc-binary/install.js:12:15)

@vallyian Please look when you have time :-)


Gripper calibration

Addition of gripper calibration on startup

https://github.com/berkeleyopenarms/blue_configs/pull/2
please pull with these updated configurations

Twiddling with gripper controllers every time the robot starts up will probably create some resource conflict errors with higher level applications -- let's just make this a service that can be optionally called?


Adjust download from GBIF to include iNaturalist observations

As a first pass (instead of hijacking the Bionomia download), make a custom DwC-A occurrence download with
datasetKey = 50c9509d-22c7-4a22-a47d-8c48425ef4a7
basisOfRecord = HUMAN_OBSERVATION
'recordedByID` is defined
...but the idea here is to gather all the unique ORCID IDs that already exist in Bionomia for a simple link on a profile page to a gallery on GBIF rather than harvesting all the occurrence records and presenting them alongside specimens in Bionomia. The profile table in Bionomia would merely be has_inaturalist.

RECORDED_BY_ID is not a parameter in GBIF's predicate API. Ticket: https://github.com/gbif/gbif-api/issues/98

This might now be accomplished through wikidata's P12022

Not sure I am understanding the target and how it would work.

Do you mean showing in Bionomia research grade observations of iNaturalist users which have previously shared their ORCID in their iNaturalist profiles?
Or perhaps it is possible to do the opposite? (link your iNaturalist account from your ORCID profile)
I understand the wikidata property you mention would just apply to deceased people, as usual (plus alive which also have a wikidata entry which contains both their ORCID and iNaturalist IDs).

I am just asking how this works in order to tell my colleagues how to make their iNaturalist records appear in Bionomia.
BTW that could serve to persuade some people to create an ORCID (hopefully without needing to persuade them to also create a wikidata entry for themselves). I know some of them which have just a few preserved specimens in GBIF (without having an orcid) ... but they have many iNaturalist observations.
Thanks
@abubelinha

As a first pass, it's none of the above in your list, unfortunately. Including basisOfRecord = HUMAN_OBSERVATION in Bionomia is well out of scope. The intention here was to merely automate the inclusion of a link to one's iNaturalist profile on their Bionomia profile & using wikidata as the broker to discover that one exists. It would look something like this:

download a stripped-down array of recordedByID values from GBIF where basisOfRecord = HUMAN_OBSERVATION
fish for items in wikidata that may / may not also have an ORCID as well as P12022
add the link to iNaturalist on the Bionomia profile


net/http: TestTransportHeadChunkedResponse flake

--- FAIL: TestTransportHeadChunkedResponse (0.01s)
	transport_test.go:611: ip/ports differed between head requests: "<IP_ADDRESS>:47607" vs "<IP_ADDRESS>:47608"
FAIL
FAIL	net/http	12.768s

http://build.golang.org/log/5f8b7215370338c03fbb75d43befedcbd95ed2c3
/cc @bradfitz @mikioh

Duplicate of #11122
https://go-review.googlesource.com/#/c/11170/


Video recording is not supported by chrome browser when using --user-data-dir

testcafe version 1.9.1
useragent: "Chrome 85.0.4183.121 / Linux 0.0"

Add flag --user-data-dir to chrome browser
Result: Videos will not be recorded
Expected: Videos to record even when using a specific --user-data-dir since it is convenient to define where the browser will store all navigation related data
Remove --user-data-dir from chrome browser
Videos will be recorded

Hello.
When you are using the --user-data-dir flag TestCafe requires to specify the cdpPort argument in the command line. Please try the following command:
testcafe "chrome:emulation:cdpPort=9222 --user-data-dir=your_user_data_dir" test.js --video artifacts/videos --speed 0.3
If it does not help feel free to ask further questions here.

Add a note about it in https://devexpress.github.io/testcafe/documentation/guides/advanced-guides/screenshots-and-videos.html#record-videos


turbolinks:load stoped of work in production environment

Describe the bug
The event turbolinks:load stoped of work in production environment.
To Reproduce
Suddenly three apps of the company that I work, stoped of work some features in production, like: multiselect, an app in vue that expect the turbolinks:load to render the page, and some other app stoped of work the multiselect too.
I "fixed" appending that: Turbolinks.dispatch ("turbolinks: load") on application.js or where is needed.
Steps to reproduce the behavior:

Choose a feature that need of turbolinks:load event
Look at production environment if working normally

Expected behavior
1 - Multiselect instead of normal select with need of turbolinks:load to start.
2 - Render vue js page that was need of turbolinks:load event to start
Details (please complete the following information):

All browsers is not working
All apps are in ruby on rails and deployed on Heroku

Additional context
All work well in development environment.
In production I "fixed" appending that: Turbolinks.dispatch ("turbolinks: load") on application.js or where is needed.

Turbolinks isn't aware of the deployment context, so it sounds it's an issue with your production configuration. It could be that your <script>s are loaded asynchronously in production (i.e. have the async attribute), which can cause problems with the turbolinks:load event on the initial load. defer should work as expected.

After facing this problem myself and digging in Turbolinks source-code I found the issue. Turbolinks implementation of DOMContentLoaded event is faulty. It doesn't check the fact that the event may already have been fired before the script is loaded.
I'll make a push request to fix this issue. As a simple workaround while it gets accepted and merged, you can simply check if your document.readyState equals interactive, and if it does, fire the turbolinks:load event yourself as shown in the snippet below.
if (document.readyState === "interactive") {
  const event = document.createEvent("Event");
  event.initEvent("turbolinks:load", true, true);
  document.dispatchEvent(event);
}


[Addition] 1.14 mods

Checklist

[X] I've checked that my mod suggestion hasn't already been added to one of the lists.
[X] I've checked the latest issues to make sure that this mod hasn't already been suggested.

What is your mod's name?
Read title.
What is your mod's main version?
Other (Forge)
Input a link to your suggested mod. Make sure it isn't hosted on a site listed on StopModReposts.
Read title.
What is your reasoning for including this mod?
Many people play versions like 1.14 including me, and I think it'd be a good addition to put a list with 1.14 mods.
(OPTIONAL) Give some extra information about the mod.
No response

For sure want to support most of the version and this is definitely something we will add sometime, But right now we don't have the workforce to maintain more versions. Tho if someone want to pull request 1.14 that's definitely something that can be done sooner then if the team has to add it.


Hugo deprecation warning

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/HugoBlox/hugo-blox-builder/issues?q=is%3Aissue
[X] This issue is not a question, feature request, or anything other than a bug report directly related to Hugo Blox Builder. Please post those things on Discord: https://discord.gg/z8wNYzb

Description
I receive the following deprecation warning when building my site locally:
WARN  deprecated: site config key paginate was deprecated in Hugo v0.128.0 and will be removed in a future release. Use pagination.pagerSize instead.
Reproduction Link
https://github.com/dodge-research-group/dodgelab-website
Steps to Reproduce

Run hugo server

Expected Result
No warning
Actual Result
WARN  deprecated: site config key paginate was deprecated in Hugo v0.128.0 and will be removed in a future release. Use pagination.pagerSize instead.
What Hugo Module versions does your site use?
module github.com/wowchemy/starter-hugo-research-group
go 1.15
require (
github.com/HugoBlox/hugo-blox-builder/modules/blox-bootstrap/v5 v5.9.8-0.20241016214324-2eaf5f6849fc
github.com/HugoBlox/hugo-blox-builder/modules/blox-core v0.3.1 // indirect
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-decap-cms v0.1.2-0.20241016214324-2eaf5f6849fc
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-netlify v1.1.2-0.20241016214324-2eaf5f6849fc
github.com/HugoBlox/hugo-blox-builder/modules/blox-seo v0.2.3 // indirect
)
What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Safari
Which Hugo Blox template are you using?
Research Group
What version of Hugo are you using?
v0.139.2+extended+withdeploy darwin/arm64 BuildDate=2024-11-23T15:33:51Z VendorInfo=brew

The latest  Hugo update does indeed break Hugo blox (also with errors related to the new googleAnalytics format, see here)

This is not directly related to the template but to a breaking change the Hugo team have made to Hugo. If you wish to use the latest version of Hugo rather than the version of Hugo that is compatible for your site, you will receive these errors from Hugo.
If you wish to upgrade your site to support the latest version of Hugo and the breaking changes the Hugo team have made then you can follow the steps described by the Hugo team in the error message, i.e. to restructure Hugo's paginate configuration into the following data structure: https://github.com/HugoBlox/hugo-blox-builder/blob/e45ef47a097e6828a5ac2717dd8dabfab3a99436/starters/academic-cv/config/_default/hugo.yaml#L28
You will find more relevant support on upgrading sites to support breaking changes from the Hugo developers over on the Hugo forums.

I wanted to confirm that the suggested fix to restructure the paginate configuration in hugo.yaml works and eliminates the deprecation warning with both Hugo v0.139.3 and the current latest v0.139.5. I am currently running this latest Hugo version with the Go v1.23.4 and the Hugo Blox CV Pro template upgraded to the latest commit e45ef47 with no build issues.


Add ConvHipImplicitGemmForwardV4R4Xdlops_Padded_Gemm in solver list

ConvHipImplicitGemmForwardV4R4Xdlops_Padded_Gemm was missing from solver list during PR merging. Add it back in

@daniellowell CI passed. This PR is needed for resnet-50 first layer


Add delay to react app mount

Description
Due to caching preloader don't get sufficient time to show up!
Adding delay to the mounting of the react app can fix the issue!
Screenshots/testimonials

@Vishal19111999 How much delay would be good?


Create a query filter

Allow to limit the request depending on the URL parameters (see https://github.com/hapijs/qs).
Idea:

Block request that has aaa parameter
Block request that has aaa parameter with value yyy.
Block request that has aaa parameter that desn't follows the patter fff.
Pass only request that contains aaa parameter
Pass only request that contains aaa parameter with value yyy.
Pass only request with aaa parameter that follows the patter fff.

The filter could be useful to avoiding attacks passing different queries to the same path.

See: https://github.com/acanimal/clyde-query-filter/issues/1


validation of VariationRegionList axis_count

We should be validating that any set of regions added to the builder have the correct axis count.
I also believe that if we know the number of axes ahead of time there may be possible improvements in the implementation, but I may be confusing axis count and region count.

If we don't already we should probably validate that the regions match this count since that's possible to check with access to only self?

Originally posted by @rsheeter in https://github.com/googlefonts/fontations/pull/742#discussion_r1428604171

for anyone interested in this: it involves adding a custom annotation to the codegen input for this type, which should name a function to be called during the validation pass. grep around for validate in resources/codegen_inputs for some examples.


Problem with PolicyBot (Python) used together with AveragePolicy from MCCFR (C++)

Background: I am using C++ External Sampling MCCFR with a custom Python game (Liar's Dice) as per the example at mccfr_cpp_example.py. PolicyBot is used to evaluate the model against a simple hard-coded Policy.
Problem: It seems that action probabilities dict returned from solver.average_policy() are shuffled which causes the PolicyBot to improperly choose an action.
I was able to fix this locally by using policy keys as legal actions:
(-) action = self._rng.choice(legal_actions, p=list(policy.values()))
(+) action = self._rng.choice(list(policy.keys()), p=list(policy.values()))

Thanks @agoryelov. I am trying to understand. Are you saying that the PolicyBot is making an assumption about how actions are ordered? Can you point us to exactly where that assumption is made and if our one-line solution fixes the problem, can you submit a PR?

Are you saying that the PolicyBot is making an assumption about how actions and probabilities are ordered?

Yeah, I believe that's what it is.
In /open_spiel/open_spiel/python/bots/policy.py, the PolicyBot uses state.legal_actions() to get a list of actions and policy.action_probabilities().values() to get an list of their probabilities. Since the action_probabilities() returns a dict, there is no guarantee that the order of the probabilities will be the same as the order of state.legal_actions().
Using the keys of the probabilities dict ensures the actions are in the correct order, but it would potentially allow the bot to make illegal actions. If that is an acceptable assumption, I can open a PR with this change. Alternatively, the bot can also validate whether action_probabilities has any illegal actions.

Yeah that sounds good, please submit a fix.
There are currently nothing preventing users from constructing policies that assign positive probability to illegal actions, things will just fail if you do it. So it's already the user's responsibility so your fix would not allow anything that's not already allowed.

I just took a look at that class and was surprised to see that it uses the legal actions.. that class should not call legal actions at all, it should justt query the policy. Can you remove that and also modify the comment at the top?
Alternatively we can support both setups with a flag. The legal actions one should only consider legal actions (and reconstruct a policy by normalizing by the sum of probs over legal actions.. in this option we can also assume prob 0 for any actions not present in the dict.)
But the default should really just be a simply query to the policy without any additional assumptions or constraints.

Hi @lanctot, I opened a PR #527 with these changes

Great, thanks!

Fixed by https://github.com/deepmind/open_spiel/pull/527. Thanks again @agoryelov !


max is divided by 2

EDIT: Probably not worth reading this issue, just see #71
I'm pretty sure this line of code is wrong but I can't come up with a unit test to prove it. Patching it to what I think it should be does not break any unit tests.
https://github.com/rust-bitcoin/hex-conservative/blob/7116a460ad2dbf6b2aea9f37ebc933db79927c07/src/display.rs#L169
We are dividing the max string length by 2 as well as multiplying the number of bytes by 2 - we should just do one (I believe).
            let string_len = match f.precision() {
                Some(max) if self.bytes.len() * 2 > (max + 1) / 2 => max,
                Some(_) | None => self.bytes.len() * 2,
            };

Should be I think
```rust
            let string_len = match f.precision() {
                Some(max) if self.bytes.len() * 2 > max => max,
                Some(_) | None => self.bytes.len() * 2,
            };

ooo, (max + 1) / 2 might have been to handle odd length max width, which makes no sense for hex strings. So perhaps this should be
            let string_len = match f.precision() {
                // Do ceil division on max so as to ignore odd length
                // max width which makes no sense for hex strings.
                Some(max) if self.bytes.len() > (max + 1) / 2 => max,
                Some(_) | None => self.bytes.len() * 2,
            };

Sorry for the noise, took me a while to work out the interaction between width and precision - TIL.


feat: nondeterminism monad, and use in backtrack

It's probably worth documenting how exactly the state is handled. I think I get it: Nondet is a lazy list of monadic actions that produce a value along with the state with respect to which the value is actually valid. Importantly, it is up to the monadic actions to be sure that they set their state, if necessary, but for example the bind operation sets the state to ensure the value passed in is valid.

@kmill, I've added a paragraph of documentation about the state.

@kmill, I've added the restoreState in head that you suggested.
Curiously, I can't actually get anything to fail if I remove the restoreStates in bind or head. (The one in ofList is certainly necessary.)

I've also switched over library_search so rather than carrying around MetavarContext state itself, it just relies on Nondet to do it automatically. Seems to work as planned.

I don't have any more questions about Nondet, so let's try this out (and if this breaks library search I trust that you'll fix it quick! :smile:)
bors r+

bors r-

bors d+

bors merge