stats_integration_test failing on Bazel CI

Seems like Envoy is red on Bazel CI since Monday:
Last green build: https://buildkite.com/bazel/envoy/builds/318
First red build: https://buildkite.com/bazel/envoy/builds/319
The stats_integration_test is failing, here's a log: https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/c6b3f0ac-027d-4295-87e8-1a75bd7510b2/test/integration/stats_integration_test/attempt_1.log
Could you please have a look?
FYI @htuch @keith
also FYI @laszlocsomor (current Bazel Green Team sheriff)

@lizan FYI

I think we should run MemoryLargeClusterSizeWithStats selectively and only check exact number in CI since it is environment dependent. @cmluciano do you have time to work on it?

@lizan yes I can work on this. Do you think guarding this test with a flag that we only trigger in the envoy ci would suffice?

Is the issue that we are running with one C++ std library in CI and a different one in development?
Can we just always run with the same C++ std library in dev and CI?

Alternatively we can pick one libstdc++ implementation and only run the expected-memory tests when using that one. But it would be easier to work with if we were able to reproduce CI failures when testing locally, so just changing the bazel default to whatever we use in CI seems like the best plan.

@jmarantz one in our CI is different one in bazel CI.

Alternatively we can pick one libstdc++ implementation and only run the expected-memory tests when using that one. But it would be easier to work with if we were able to reproduce CI failures when testing locally, so just changing the bazel default to whatever we use in CI seems like the best plan.

We don't know which exact STL class is causing the change between versions so it would be hard to detect. If you're running our build docker image you always get same.

I was thinking that there must be some build config change to switch STL versions, which we could then augment with something that adds a -DSTL_LIB_XXXX type compile-flag, which we could then use to switch off the tests.  But I don't see that in https://github.com/envoyproxy/envoy/pull/6866
I noticed that when I run stats_integration_test locally now, it fails, but it works in CI.  This is not a great situation; we have to fix this by either making the comparison sloppy, by checking against 2 alternative expected values, or by using an ifdef to have it only run in one mode.
What is Bazel CI and how does that differ from our normal CI that gets run on every PR?

I have a heuristic that tells me which mode we're in by measuring the tcmalloc stats after allocating some strings. The difference is subtler than I thought, but we can use it to turn off the test. But I think we probably would be better off getting our dev builds and Bazel CI to use the same libraries as we use in CI. @lizan how hard do you think that would be?

From limited testing with my heuristic I think there's some other difference between what we are doing in CI and what's happening on our local machines, beyond libc++.
We may need more approximate metrics for tracking memory consumption if we can't get our dev and test environments to behave consistently.

At the inception of this test I also found the memory to fluctuate between a few of my dev machines which caused me to go with approximate value rather than the hard EQ.
@jmarantz Is the value you hit locally greater or less than what we get in CircleCI?

The latest BuildKite master build  yields m_per_cluster == 49449 and I get the same value when I run the test locally.
I'm trying to diff the .bazelrc files b/t the various CI systems now.

Anything outside of our build docker image is inconsistent, IMO we can do either (or both):

bake a config/environment into the build image and do exact eq if that exists.
do a approximate value comparison

From limited testing with my heuristic I think there's some other difference between what we are doing in CI and what's happening on our local machines, beyond libc++.

The libraries that bazel is not managing are: libc, libm, libgcc, pthread and libstdc++ (or libc++), so all of those libraries can affect this number.

Looks like @jmarantz has a WIP with #7208

Yup, I have gotten it to work with default build, and am now verifying it with //test/... --config libc++ a

Thank you everyone for getting at this so quickly! :))
By the way, would you like to get Bazel CI status checks for your PRs, too? That way you could immediately see if it something fixes a breakage (or if something breaks it). I should be able to just turn it on in our settings, but wanted to check with you first.

I still don't know, btw, whether this will work with Bazel CI, or what the difference is between the two CIs and our dev environment. It had seemed all consistent until roughly this week.
RE Bazel CI status checks: can you clarify what that means? What would that do beyond our own integrated CI?

RE Bazel CI status checks: can you clarify what that means? What would that do beyond our own integrated CI?

Bazel CI is a service that the Bazel team provides for free to Bazel and its ecosystem. We provide a user-friendly UI to view test results (thanks to the great folks at Buildkite) and high-performance machines for Linux/Docker, Windows (both currently on 32-core GCE VMs) and macOS (18-core iMac Pros). It comes with RBE support for remote builds and caching, too. It's also super easy to configure (just specify in a YAML file which targets you want to build / test on which platform, we handle the rest). Our mandate is to build the best CI possible for and together with Bazel users. :)
The idea is basically: Everyone gets a free CI and Bazel gets more testing to ensure that we don't accidentally break our users. The only thing we ask for is that projects keep their CI green, because otherwise we can't get any signal whether a change to Bazel broke you or not.
If that sounds cool, you could use it in addition to or instead of other CI solutions that you're currently using. (FYI the initial discussion when we added Envoy to our CI was here: https://github.com/bazelbuild/continuous-integration/pull/653)

@mattklein123 who I was discussing this with before I went on vacation.

cc @lizan who is in charge of making our CI better. ^


The Folder is empty after running

E:\A-Hack\A-ToolsBar\Cracer安全工具包\漏洞利用\Nuclei-基于yaml的poc框架\cent-模板下载工具\cent-nuclei-templates

Hi,
I will test that on a Windows machine

I also have same problem on ubuntu
how can I resolve this problem?
thanks

i have same error like this post .. how to solved ?

same problem

In file pkg/jobs/jobs.go change /tmp/ to .tmp/

Same problem for me. firstly I ran cent -p cent-nuclei-templates -k and all of the repos "CLONED" but the folder was empty. so I added the '-C' to print console output, and this is the output:
┌──(root👻DrDv)-[~]
└─# cent -p cent-nuclei-templates -k -C
cent started
Command timed out: git clone https://github.com/ARPSyndicate/kenzer-templates /tmp/cent1671694059/repo4
Command timed out: git clone https://github.com/1in9e/my-nuclei-templates /tmp/cent1671694059/repo2
Command timed out: git clone https://github.com/0x727/ObserverWard_0x727 /tmp/cent1671694059/repo1
Command timed out: git clone https://github.com/daffainfo/my-nuclei-templates /tmp/cent1671694059/repo9
Command timed out: git clone https://github.com/AshiqurEmon/nuclei_templates.git /tmp/cent1671694059/repo5
....
....
....
Command timed out: git clone https://github.com/z3bd/nuclei-templates /tmp/cent1671694059/repo50
Command timed out: git clone https://github.com/zinminphyo0/KozinTemplates /tmp/cent1671694059/repo51
Command timed out: git clone https://github.com/c-sh0/nuclei_templates /tmp/cent1671694059/repo52
Command timed out: git clone https://github.com/Akokonunes/Private-Nuclei-Templates /tmp/cent1671694059/repo53
Removing duplicate templates...
[!] Removed duplicates
cent finished, you can find all your nuclei-templates in cent-nuclei-templates

┌──(root👻DrDv)-[~]
└─# ls -la cent-nuclei-templates/
total 12
drwx------ 3 root root 4096 Dec 22 09:27 .
drwx------ 4 root root 4096 Dec 22 09:27 ..
drwx------ 7 root root 4096 Dec 22 09:27 .git

Hi @DrorDvash,

Hi @DrorDvash, @Rahimianes @breaking153 @rabeltester44, can you check now?
i have implemented this tool https://github.com/go-git/go-git

I can confirm it is working properly now, on Cent v1.1
Thanks!

Closing this issue as revolved.
Feel free to reopen again if you find problems related to this issue
Thank you

I also have same problem on ubuntu how can I resolve this problem? thanks
the problem not resolved for me with "go version go1.20.1 linux/amd64"

How can I resolve that?


fix: set cache items on-chain to false, for non-existent cms

Scenario:
Deploy a candy machine successfully and verify that it was created. When finished with it, run sugar withdraw and close it down but don't modify the cache file.
Run deploy again, to create a new candy machine. The command will correctly determine that the existing candy machine is not on-chain so will create a new one, but because all the cache item on-chain values are true, it will not upload the config items resulting in an invalid candy machine that says it was successfully deployed.
This fixes the issue by writing all on-chain values to false in the cache file if we have an existing candy machine pubkey in the cache file but it is not found on-chain.
@KartikSoneji if you have a chance to take a look at the logic, I'd appreciate it.

I think it would be better to add it before sending the transaction, in case the tx times out.
Maybe somewhere here:
https://github.com/metaplex-foundation/sugar/blob/3d5246cf8d3d1eba61a225a5ca8cc776d220123f/src/deploy/process.rs#L152-L164

I think it would be better to add it before sending the transaction, in case the tx times out. Maybe somewhere here:
https://github.com/metaplex-foundation/sugar/blob/3d5246cf8d3d1eba61a225a5ca8cc776d220123f/src/deploy/process.rs#L152-L164

This is before the initialize candy machine transaction is sent, but I suppose it is an unnecessary write in the case where the candy machine address in the cache file is empty, so I'll move it up to where you suggest.

Quick question, what does the .0 do here?
The project seems to compile fine without it.
https://github.com/metaplex-foundation/sugar/blob/2d3591e1ff5197d6382d416fff9c47aee8f4e88d/src/deploy/process.rs#L165-L169

Quick question, what does the .0 do here? The project seems to compile fine without it.
https://github.com/metaplex-foundation/sugar/blob/2d3591e1ff5197d6382d416fff9c47aee8f4e88d/src/deploy/process.rs#L165-L169

CacheItems is a wrapper type around an IndexMap, so normally you'd need the .0 to index into the actual type, but I forgot I implemented Deref for it, which allows the compiler to extract the inner value automatically.
pub struct CacheItems(pub IndexMap<String, CacheItem>);

Quick question, what does the .0 do here? The project seems to compile fine without it.
https://github.com/metaplex-foundation/sugar/blob/2d3591e1ff5197d6382d416fff9c47aee8f4e88d/src/deploy/process.rs#L165-L169

CacheItems is a wrapper type around an IndexMap, so normally you'd need the .0 to index into the actual type, but I forgot I implemented Deref for it, which allows the compiler to extract the inner value automatically.
pub struct CacheItems(pub IndexMap<String, CacheItem>);

Ah ok, good to know.


Souvenir stickers dont appear

Sorry, and thanks, im just reporting that souvenir stickers didnt appear when open a souvenir package

Inventory changer isn't detailed so,you can't open cases or something


chore: remove samples

Samples have migrated: https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/main/talent/snippet Removing duplicate samples, do not merge until snippetbot is happy.

Sample locations were updated in cl/489239623, this is ok to merge.


updating  terraform eks module version from 6.3.0 to 8.2.0

I am updating terraform eks module version from 6.3.0 to 8.2.0 in my project. since this is very new to me do i need do the node (instnace) refresh since we are using  asg instance refresh every time?  when i am upgrade eks modules moving forward !. Right now the only change i see in my project

**module.eks.kubernetes_config_map.aws_auth[0] will be created

resource "kubernetes_config_map" "aws_auth" {**

module.eks.null_resource.update_config_map_aws_auth[0] will be destroyed

resource "null_resource" "update_config_map_aws_auth" {

module.eks.null_resource.wait_for_cluster[0] will be created

resource "null_resource" "wait_for_cluster" {

id = (known after apply)
}

I'm sorry but thats quite an old version thats not been supported for some time - however, instance refresh changes are usually safe, they just control the manner in which nodes are replaced in the autoscaling group


License question

Hi all, hi @sukunis ,
just a quick question regarding the license that was just added in https://github.com/German-BioImaging/RDM4mic/commit/1b1453e95818e017829bc77778c4a88f09a2f868 . Does it necessarily have to be this license? In NFDI4BioImage, we might want to rely on the materials published here and we're aiming for a CC-BY 4.0 license for sharing materials. We also might want to do paid courses, where only not-NC licenses would work. CC-BY-NC-SA is quite a constraint. Thus, I was wondering if there is a strong reason for this license.
Thanks!
Best,
Robert

Hi @haesleinhuepf,
after the discussion at the last meeting, we decided to use the CC-BY 4.0 licence, unless someone wants to publish their material with a different licence, which is then marked in the material.
Best,
Susanne


Update install-kubectl.md

we need run source /etc/bash_completion command after source <(kubectl completion bash) in linux

/assign @bradamant3

we need run source /etc/bash_completion command after source <(kubectl completion bash) in linux

In ubuntu 16.04, I don't need to run source /etc/bash_completion.
Which linux do you use?

I am using ubuntu 14.04 D;

@ghanbari @CaoShuFeng can you sort out whether the command is required, whether we should specify the version of ubuntu, whether we should specify multiple ubuntu versions and their individual requirements? Thanks!

@ghanbari 👋 Please feel free to reopen this PR with information about affected versions.


readme.md typo

typo

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Tests pass?
❌

Fixed issues
-

Merged. Thanks!


Fix Bootstrap 5 usage

Closes #327

@cpsievert thanks for the fix
the build fails though (notice the failed checks)
https://travis-ci.com/github/itsjavi/bootstrap-colorpicker/builds/227649344


CADL extension

https://github.com/Azure/autorest.java/wiki/CADL-to-Java#detail

add emitter for CADL in cadl-extension, it outputs m4 with extended data (e.g. namespace, usage for Choice, usage=convenienceMethod in operation and models)
add simple wrapper for preprocessor and javagen in cadl-extension/src
update related code-model in Java
add ImplementationDetails class in client-model, for ClientMethod, ClientModel, and EnumType
add mapPredefinedModel for model that to be provided by other libs (for now, just for azure-core)
add one test in cadl-tests of https://github.com/Azure/autorest.testserver/blob/dpg_cadl/cadl/dpg-update1.cadl
add CI for JAR, NodeJS, and the testserver test above

@alzimmermsft I will wait for your PR.


Add public, logFile and preset flags

New options:
-public 1
-logFile /var/lib/valheim/log/valheim-server.log
-preset "hardcore"

By default the public flag is set to true as per the docs.
I think the preset flag is "normal" by default, but leaving it out if the user does not specify it is a better idea imo.

Maybe it is possible to create an enum for the -preset flag for all possible options?

Maybe it is possible to create an enum for the -preset flag for all possible options?

You certainly could.
I'm not sure about the log-file option.  Is there a good reason to not use journald?

I'm not sure about the log-file option. Is there a good reason to not use journald?

I think that since the option is available for a regular valheim dedicated server that it could also be available here.
Not sure if it is possible to redirect logs to another file without the -logFile flag.


Self registration beta test research

User feedback (based on hypothetical concepts) suggests that allowing users to self register for their COVID-19 tests could have a number of benefits:

Shifts burden of data entry from one (the test administrator) to many (the patients)
Saves time and effort for the test administrator at the time of test
Allows parents or guardians to register kids from home
Allows patients more privacy when answering questions
Lowers the risk of accidental typos in data entry

However, these are untested hypotheses. The purpose of this beta test is to see whether real patients and testing sites will use this feature, how they use it, and what bugs, improvements, or innovations come up under real life conditions. Doing this will allow us to get feedback on a live product while also limiting our risk by rolling it out to a limited number of customers.
Tasks

[ ] Conduct Metabase analysis and internal research to identify potential participants
[ ] Conduct research with potential participants
[ ] Secure agreement from testing sites to participate in beta test (goal: 3)
[ ] Prep materials for beta test - operational guidance with instructions and best practices
[ ] Prep materials for beta test - sign up sheet for patient research
[ ] Prep materials for beta test - questions for test admins to consider during beta test
[ ] Prep research guide for debrief research sessions with test admins
[ ] Schedule debrief research session with test admins the day after testing to discuss experience
[ ] Schedule debrief research session with design team after 1-2 more weeks of use
[ ] Synthesize findings
[ ] Deliver findings


Using MessagePack for backend data storage

Since the use case I see is just storing Python dictionaries; I see no reason we shouldn't use MessagePack vs that of Pickle or Shelve.
This shows performance data for deserializing JSON with MessagePack vs Python's JSON library: http://wtanaka.com/node/8100

Current implementation uses Shelve which is Pickle under the hood; according to what I can find; this is significantly slower than directly serializing JSON with Python standard library. We are losing performance here
https://kovshenin.com/2010/pickle-vs-json-which-is-faster/

This also looks like a viable alternative: http://labs.codernity.com/codernitydb/

I would like to say that using a no-sql approach will in the long-term bite us in the ass, as such, I would like to suggest using actual tables for data store: http://www.sqlalchemy.org/
There is a lot more you can do with a relational database then with simple key-value.

I would like to say that using a no-sql approach will in the long-term bite us in the ass, as such, I would like to suggest using actual tables for data store: http://www.sqlalchemy.org/
There is a lot more you can do with a relational database then with simple key-value.

I don't see a use case for a full schema based data store.
There is a lot of overhead with SQL, (creating schemas, normalizing data, joins across bot domains, etc). Something like SQLite I have considered; but again, I'd rather keep it simple. JSON is more than adequate for the 90% use case.
I curious as to what you think the bot will need to have a full relational database to do

There are quite few good uses for relational storage for a bot.
If we want to be flexible we'd want to expose this storage to plugins.
Here is a big IRC bots repository with a lot of plugins some of which use SqlAlchemy.
https://github.com/CloudBotIRC/CloudBot/search?p=1&q=Table&type=Code&utf8=✓
Not to say it would simplify working on webUI if we go with Flask (Flask-SqlAlchemy), I don't see how we could have Arcbot plugin storage flexible if we use NoSQL...

Decided on using PeeWee for the database backend. It's an extremely lightweight ORM.
http://docs.peewee-orm.com/en/latest/index.html
I still need to consider a few things

[ ] Thread-safe database transactions
[ ] Abstraction to the plugin interface

Also decided that I'll expose both an ORM and a key store since peewee gives us both:
http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#KeyStore

Should use JSONKeyStore in that case.
On Oct 13, 2015, Patrick Hennessy<EMAIL_ADDRESS>wrote:

Also decided that I'll expose both an ORM and a key store since peewee
gives us both:
http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#KeyStore

Reply to this email directly or view it on GitHub:
https://github.com/Arcbot-Org/Arcbot/issues/22#issuecomment-147570180

-- Sent with K-@ Mail - the evolution of emailing.

Done for now: 0ba4785c39da325d5b23adb40ece8160728949f3


feat: add theila

Theila is the UI component for Sidero Labs products.
Signed-off-by: Noel Georgi<EMAIL_ADDRESS>

Thank you for your contribution.

#3238 siderolabs/theila: Theila is the UI for all things Sidero Labs

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v2.11.0

That was super fast, thanks :heart:


I#1428

Coverage decreased (-0.6%) to 57.854% when pulling 25dd371a9c48b4a62bb1ac4d7d5d09986f90ffd8 on i#1428 into 972bfe8a59c61585f600d6bbdcb4fce0c56f8231 on release-3.5.0.


Make sure full screen button is visible in 1024 width (projector)

@willdurand Does this issue concern the presentation mode button if so does the title suggest keeping it visible underneath 1024 width ?

Yes and yes.
It is the little "play" button (aka presentation mode button or fullscreen mode button).  If you downgrade your screen size, you'll notice that it disappears (for responsiveness purpose). Yet, we need it as most video projectors have a low resolution.

Perfect ! I'll get on this, I wanted to make sure we were talking about the same button.

fixed now, and deployed!


This relates to #186: we're managing state for ANOTHER statemachine in THIS statemachine.


Why Flow why not TypeScript

I mean why isn't the whole library in typescript?

Because TypeScript is flawed by design and Flow is a stricter type system.

I think you should give a try to TypeScript then you can build your own opinion based on a real comparison of pros and cons. And most people would say TypeScript is a definite winner ;) Awesome package btw

I use both TS and Flow, thanks for the advice though.

I don't endorse the OP's tone and didn't really want to bring this old thread back to life, but I think that this is worth reconsidering.
I don't know flow, and I'm ready to believe that it's technically a better type system than TypeScript. However that's not the only thing we should consider when choosing technologies, especially in open-source projects. Criteria such as community and ecosystem are just as important.
Concretely speaking, flow is a barrier to entry for contributing to popperjs, and I'm willing to bet that the library is used in many more TS than flow projects out there. Switching would surely improve developer experience overall, while encouraging community contributions.
Let's put ourselves in the shoes of a FE developer who's looking at learning a type system today: which one would they choose?

Are you particularly attached to flow or would you agree to have a discussion about a potential migration?

Flow is pretty similar to TypeScript, especially with this codebase's types (v3's types are even simpler)
TL;DR for contributing here is:

$Shape<> is Partial<>
{| |} are exact objects
Type predicates can be seen in the instanceOf file
Just use type keyword instead of interface

Add the Flow VS Code extension (and possibly disable TS typechecking for the project) and that's it

Maintaining a Flow codebase allows to easily auto generate typescript types. Doing the opposite is quite difficult, because Flow is a way stricter type system

Okay, good to know, so you're saying that we're sticking with flow here because it's a "2 for the price of 1" scenario—this makes sense, although using popper in TS didn't feel as smooth to me as using a TS-first library like unified. But you're right that the types were there and totally usable with a bit of tweaking.
I still think that there would be more community contributions if the codebase was in TS, but it also looks like you're doing a pretty good job at keeping on top of questions/requests (🙌), so maybe we don't need more contributors for the sake of having more contributors.
I wouldn't be surprised if some day we realize that it would make everyone's life easier if we to switched over to TS, but it seems fair to stick with flow right now. Thanks a lot for the extra rationale and thoughts here and thanks for the library 🍿

Happy to see that Floating UI is no TypeScript 🎉


s3 bucket settings not defined in the MR are removed after upgrade to v0.46.0

What happened?
I upgraded provider-aws from version 0.45.2 to version 0.46.0, this resulted in removal of s3 bucket settings that were not defined in MR manifest.
Unfortunately part of s3 bucket settings (notificationConfiguration) must be managed by separate tool outside of Crossplane, and this worked in previous versions.
Enabling management policies and using ["Observe", "Create", "Update", "Delete"] didn't resolved the issue.
How can we reproduce it?

Create s3 bucket using below manifest and provider-aws v0.45.2 (or older):

apiVersion: s3.aws.crossplane.io/v1beta1
kind: Bucket
metadata:
  name: bucket-name
spec:
  deletionPolicy: Delete
  forProvider:
    locationConstraint: us-east-1
    objectOwnership: BucketOwnerEnforced
    paymentConfiguration:
      payer: BucketOwner
    publicAccessBlockConfiguration:
      blockPublicAcls: true
      blockPublicPolicy: true
      ignorePublicAcls: true
      restrictPublicBuckets: true
    serverSideEncryptionConfiguration:
      rules:
        - applyServerSideEncryptionByDefault:
            kmsMasterKeyId: kms-key-id
            kmsMasterKeyIdRef:
              name: kms-key-name
            sseAlgorithm: aws:kms
          bucketKeyEnabled: true
    tagging:
      tagSet:
        - key: key
          value: value

Manually configure "Event Notifications" (notificationConfiguration)
Upgrade provider-aws to v0.46.0
Observe "Event Notifications" settings being removed

What environment did it happen in?
Crossplane version: 1.14.5

Having two different points of truth is not supported by this provider. If something has been overwritten, it might be due to the controllers always considering the MR as the target definition.
If there is a bug, maybe with LateInitialize, please let us know.

I would like behavior from circled description, but enabling management policies and using ["Observe", "Create", "Update", "Delete"] didn't worked:

I found that this PR https://github.com/crossplane-contrib/provider-aws/pull/1974 introduced notification configuration reset, even when it has never been set in the MR. Shouldn't this be dependent on management policies?

I can't really say much about Management policies as they are a feature that is coming from https://github.com/crossplane/crossplane-runtime. It is not honored by the provider itself.
However, https://github.com/crossplane-contrib/provider-aws/pull/1974/files#diff-a8eef2da98b1ec4eedcdafbeb44237c0a1065cd0bf9c3f34124cb67c143113efR290 is run during the update step.

I tried with ["Observe", "Create", "LateInitialize", "Delete"] and that resulted in creation of default s3 bucket, without any settings from spec.forProvider object.
Is there a way to use the provider for objects creation with defined spec, and do not update them after?

I tried with ["Observe", "Create", "LateInitialize", "Delete"] and that resulted in creation of default s3 bucket, without any settings from spec.forProvider object.
Is there a way to use the provider for objects creation with defined spec, and do not update them after?

Is there a way to use the provider for objects creation with defined spec, and do not update them after?

I don't think it is implemented. But you can try the official provider: https://github.com/upbound/provider-aws


left-padding-is-broken in tokenizers

question answering does not work with left padding due to an upstream issue in the fast tokenizers
tokenizers issue #1229
this workaround should prevent scandeval from encountering this issue

Following my bug report, left padding has been fixed in the tokenizers library.


Added apache license

@kotfic @doutriaux1 please review

@LGTM

haha meant for @dorukozturk you both share "do" prefix. Sorry about it.


Rogue "0"

Reading the Declaration Files documentation and noticed that on the Templates pages there are random zeros next to the articles (see attached images). This can be found on the main Template page and all subsequent templates.
Rogue zeros are marked with red circles on the screenshots.

I bet this is the check for headers to show the sidebar


Add functionality

Added functionality for second button:
- Pressing (without holding) the button on the same side (but opposite end) as the 'T' in 'TTGO' will now turn the screen off before timeout.

I see you press one button to make it immediately sleep, the other button to wake it up.


Export to PDF and Excel

In export, if there is export to excel and PDF option is available than its more user-friendly and productive.

I guess it depends a bit on the data you have in your table and what users are going to do with it. I'd recommend generating a pdf server-side as client-side implementations have their limitations and they're not consistent across devices and browsers. But I still think this would be a nice feature so I'll add it as a feature request, would be nice to add it as a plugin.


Set special "header_placement" TargetGroupAttribute

Is your feature request related to a problem? Please describe.
We have a specific need to set a "special" (read: not publicly exposed) attribute on our NLB target groups. It is not commonly used, but we found this project to be the closest to a solution for us to set those attributes natively without having to run some external script to set those.
The specific key we have to set is proxy_protocol_v2.client_to_server.header_placement.
Describe the solution you'd like
Either introduce a new annotation to set this "header placement" attribute, or maybe even open this up to allow any arbitrary attribute to be set via annotation?
I know embedding JSON in attribute values can soon get ugly, but I've seen similar things on the ALB ingress controller.
Maybe an annotation like:
aws-nlb-helper.3scale.net/extra-annotations: '[{"Value": "on_first_ack", "Key": "proxy_protocol_v2.client_to_server.header_placement"}]'

We should be able to directly Unmarshal this into an []*elbv2.TargetGroupAttribute (hopefully) and log errors accordingly.
Describe alternatives you've considered
Write another operator that would do 99% of what this one does ;-)
Additional context
We are happy to contribute this, whichever way you prefer (specific annotation for this attribute or implement the "generic" annotation).

Welcome @moensch, thank you very much for the proposal!
Give me some days to play a bit with those extra attributes and get back to you as soon as posible.
:)

Keep in mind the specific attribute in question is undocumented and only available/usable after being specifically enabled for your account and region by AWS support upon request.
If we’re going with the “smaller” change (not the option to allow arbitrary attributes) I’m happy to start putting a PR together.

Hello @moensch, for the time being, we don't see that many settings can be tweak to go for the arbitrary attributes.
Having specific logic for the attributes, allows to add some validations on the operator side, makes it easier by setting specific annotations for each setting rather than messing with structured data in annotations. In case the number of options that can be tweak grows, probably going using a custom resource definition for NLB settings may be also a good option.
Feel free to start putting a PR if you like, and thanks for contributing! :)
The code is still in early stages, we will be working on improving the code and add testing asap.


[EBPF] Fix generation of embedded BTF archive in KMT VMs

What does this PR do?
Fixes the path where the minimized-btfs.tar.xz file is located when using KMT.
Motivation
Fix a bug introduced by https://github.com/DataDog/datadog-agent/pull/25592 where the path to the BTF file was not updated properly in the KMT python code.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[QUERY] Support providers/Microsoft.Management/getEntities

Library name and version
Azure.ResourceManager 1.5.0
Query/Question
In the deprecated version Microsoft.Azure.Management.ManagementGroups there is a way to send requests to this endpoint
I could not find any way to do this in the new sdk Azure.ResourceManager.
Am I missing something or this does not exist? if it doesn't is there a way to add this to the new version of the sdk?
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

We're working on this features, will let you know once it's ready.


Feature Request: ids_to_text method

Hi, it'd be nice if there was a method to convert ids to text. This would allow Bling Fire to used with text generation models. Here's similar code from Hugging Face's Transformers:
from transformers import AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained("bert-base-cased")
print(tokenizer.decode([1188, 1110, 170, 2774])) # prints "This is a test"

Hmm... for generation it makes sense. I did not want to add it initially because model still may encounter UNK tokens, in this case reconstruction of a string from a sequence of ids is not possible (because of UNKs). I guess a generation model should never generate an UNK so reconstruction should be possible... Ok, let me add it.

Is there any update about this request?

Done in 0.1.8 release

Here is an example code: https://github.com/microsoft/BlingFire/blob/master/scripts/blingfire_example.py

Big thanks @SergeiAlonichau, this is really great! 🎉  Added it to the Ruby library, and going to try it out with text generation models.


Bjorncs/configserver di graph cleanup

It might be that commit number 2 leads to issues. AFAIR reflection is used in JRT to find the Java method to invoke based on the method name in the request, so such methods need to be public

It no longer uses reflection to find the methods. They are now "hard-wired" using the MethodHandler interface :)


Get raw data (NSData/NSString) from JSON

Hi,
I want to store tweets (JSON) as an array of NSString or NSData (and not array of JSONValue). I got raw NSString for a tweet using the 'description' property. Now I'm having trouble converting it back to JSONValue format so it's parameters can be accessed.
Is there a way to get raw JSON data and then convert it back to the Swifter's JSONValue format? Would be a big help.

Hi @bluekemon ,
have you tried using the parseJSONString method? You can find it here  :)

Hey @zntfdr,
I did try parseJSONString and parseJSONData after I saw them being used in Swifter.swift file. But Xcode throws an error - "Type 'JSON' has no member 'parseJSONString'". I've imported SwifteriOS in my file, so why can't Xcode see the functions?

It's a static JSON function:
in order to call it you have to writeJSON.parseJSONString (...), please let me know if it works :)

Yes, was doing exactly that. Apparently Xcode is not able to "see" the parseJSONString method, or any other public test methods that I add to JSON.swift. Am I forgetting to include some file?

Well, that's strange!
Can you see the JSON enum at all? Can you access to any of the JSON instance properties?
If not, then the file probably is not included among the targets of your build.

Actually, the parseJSONString and parseJSONData methods have been left as internal and not public. Also, using the .description property on the JSONValue will not give you the "raw string" you're looking for, but simply a parsed string generated by JSON (which is not reversible).
In order to achieve what you want, here's how I would do it:
Instead of using JSONValue, create a wrapper class that simply takes the values you need. Inherit NSCoding so that you can convert the class object to NSData using NSKeyedArchiver
When you need to do the reverse and convert them back into the wrapper class, you'll just need to use NSKeyedUnarchiver.
Read more about NSCoding, NSKeyed(Un)Archiver here

@zntfdr and @meteochu : Thanks so much for your help! I will try both these things and see if it works.

It would actually be great to have Codable / Decodable support for this. So just getting the Data is actually going to be a heck of a lot more convenient right now. With Codable it's going to be a piece of cake to get what we want from the resulting JSON. The JSON type is a lot of un-necessary overhead to parse through to get what we want. Simply returning Data would be much helpful.

I have a pull request #203 that addresses this issue. I've since thought of a better, simpler way to approach it but haven't had time to implement that, so it's been sitting idle. I plan to revisit soon!

@zachrwolfe I completely agree. A merge of your PR would be great addition to the lib. Until then, I'll have to try out your commit (87a8625).

Here I am chasing the chicken (using Decodable). Slightly inefficient, but works.
swifter.getUserFollowing(for: .id("16532709"), cursor: nil, count: nil, skipStatus: true, includeUserEntities: false, success: { (json, prev, next) in
     let jsonData = String(describing: json)
     let jsD   = jsonData.data(using: .utf8)!
     do{
            let json = try JSONDecoder().decode([userIDS].self, from: jsD)
          }catch{
                    print("ANN: JSON Error")
         }
      }, failure: { (error) in
                print("ANN: Error ", error.localizedDescription)
            })

Haha, whatever works I guess 😆


Why the images use ?

a href="#" go to the state '' when I use angular-ui-router.
It(href="#") seems to be unnecessary, and brings some problems.

Hi @yyuna. It's because of accessibility: https://github.com/emotionLoop/visualCaptcha/issues/9
The samples have some code to avoid the scrolling to top issue, but I'm open to better suggestions.

@BrunoBernardino
Maybe you could use href="javascript:void(0)" instead of href="#" :D

There are some big discussions about that and while my personal preference goes with javascript:void(0);, I've seen issues with accessibility-focused browsers with that vs #, and that's why I went with that.
In any case, you're free to change it for yourself! :)


clone to new folder crashes vscode

Issue Type: Bug
click a 'clone in vscode' link from azure devops
navigated to C: drive created new folder
rename new folder and select it to use as repository location
VS Code version: Code 1.35.0 (553cfb2c2205db5f15f3ee8395bbd5cf066d357d, 2019-06-04T01:17:12.481Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.79GB (36.18GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

gitlens
eam
9.8.1

tslint
eg2
1.0.43

Angular2
joh
7.1.6

Can you be a little more explicit with the repro steps? At which point does VS Code launch? (I'm not familiar with the devops intergration)

the devops integration is just a link of the form vscode://vscode.git/clone?url...
link should trigger vscode to open.

crashes vscode

What do you mean by crashes? Can you show me a screen recording?


Requesting an example of how to implement a COM interface

I have a fairly simple C++ program that turns on a blink(1) based on a capture device's mute state.
I'd love to port that code to Rust, if possible, but I don't know how to implement the IMMNotificationClient or IAudioEndpointVolumeCallback interfaces.
I noticed that there is the implement macro, but the documentation seems a bit sparse. If there is an example of how to do this, could you point me toward it, and if not, I humbly request one!

The implement macro currently only supports WinRT interfaces, but I am working on adding support for COM interfaces like IAudioEndpointVolumeCallback and should be coming soon.

The implement macro currently only supports WinRT interfaces, but I am working on adding support for COM interfaces like IAudioEndpointVolumeCallback and should be coming soon.

Thanks for working on this, I need to be able to implement DirectShow filters 😅

Thanks for working on this, I need to be able to implement DirectShow filters 😅

I'm also affected by this, in the meantime, is there some way to implement interfaces by hand?

Implementing COM interfaces from scratch is non-trivial but very much possible. It does take quite a bit of knowledge of how COM works under the hood though. You can have a look at https://github.com/microsoft/com-rs (specifically the code gen aspects of that crate) for some clues.

Duplicate of #81 - working on it.

I'm also affected by this, in the meantime, is there some way to implement interfaces by hand?

Here's an example of implementing drag&drop com interfaces by hand. It is doable but less than ideal. A macro would be very welcome indeed :)

That's all I am working on at the moment. 😉


User is not informed of their death

Problem lies within line 137 on main.cpp. Fairly sure that it's not writing (correctly) to the framebuffer.

We might want to the restart prompt on a delay (from 1/10 to 255/10 seconds, step of 1/10)


UnpicklingError: While running in Local and Colab

While Running demo I am encountering UnpicklingError. I have used latest pytorch and pytorch 1.4. It gave same error. I am encountering this in colab and local machine both.
`UnpicklingError                           Traceback (most recent call last)
<ipython-input-3-d26975ab34c8> in <cell line: 10>()
      8
      9 # Process video
---> 10 video_app(video_path,
     11           spiga_dataset='wflw',               # Choices=['wflw', '300wpublic', '300wprivate', 'merlrav']
     12           tracker='RetinaSort',               # Choices=['RetinaSort', 'RetinaSort_Res50']

5 frames
/usr/local/lib/python3.10/dist-packages/torch/serialization.py in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
   1256             "functionality.")
   1257
-> 1258     magic_number = pickle_module.load(f, **pickle_load_args)
   1259     if magic_number != MAGIC_NUMBER:
   1260         raise RuntimeError("Invalid magic number; corrupt file?")

UnpicklingError: invalid load key, '<'.`

I am facing the same issue... Any suggested fixes?

download the models manually fixed it for me

how are you plugging in the modes after downloading it... seems to create problems for me

how are you plugging in the modes after downloading it... seems to create problems for me

i put them in a folder called weights
C:\Users\Jack\SPIGA\spiga\models\weights

I have uploaded the models to a Hugging Face model card and the demos should be available again. The problem was somehow related to an incompatibility of the Python version used (above python 3.8), the torch.hub functions used to download the weights and the storage in google drive.


failed to compile. ambiguous call to writer->Put

Problem
Step to reproduce
Build examples/all-cluster-app/esp32
The error mesage shows:

Click to expand!
FAILED: esp-idf/main/CMakeFiles/__idf_main.dir/__/third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp.obj
/home/xuan/.espressif/tools/riscv32-esp-elf/<IP_ADDRESS>_64eb9ff-8.4.0/riscv32-esp-elf/bin/riscv32-esp-elf-g++ -DHAVE_CONFIG_H -DMBEDTLS_CONFIG_FILE=\"mbedtls/esp_config.h\" -DUNITY_INCLUDE_CONFIG_H -DWITH_POSIX -Iconfig -I../third_party/connectedhomeip/examples/all-clusters-app/all-clusters-common -I../third_party/connectedhomeip/third_party/nlio/repo/include -I../third_party/connectedhomeip/src -I../main/include -I../third_party/connectedhomeip/examples/common/screen-framework/include -I/data/git/esp-idf/components/newlib/platform_include -I/data/git/esp-idf/components/freertos/include -I/data/git/esp-idf/components/freertos/port/riscv/include -I/data/git/esp-idf/components/esp_hw_support/include -I/data/git/esp-idf/components/esp_hw_support/port/esp32c3/. -I/data/git/esp-idf/components/esp_hw_support/port/esp32c3/private_include -I/data/git/esp-idf/components/heap/include -I/data/git/esp-idf/components/log/include -I/data/git/esp-idf/components/lwip/include/apps -I/data/git/esp-idf/components/lwip/include/apps/sntp -I/data/git/esp-idf/components/lwip/lwip/src/include -I/data/git/esp-idf/components/lwip/port/esp32/include -I/data/git/esp-idf/components/lwip/port/esp32/include/arch -I/data/git/esp-idf/components/soc/include -I/data/git/esp-idf/components/soc/esp32c3/. -I/data/git/esp-idf/components/soc/esp32c3/include -I/data/git/esp-idf/components/hal/esp32c3/include -I/data/git/esp-idf/components/hal/include -I/data/git/esp-idf/components/esp_rom/include -I/data/git/esp-idf/components/esp_rom/esp32c3 -I/data/git/esp-idf/components/esp_common/include -I/data/git/esp-idf/components/esp_system/include -I/data/git/esp-idf/components/esp32c3/include -I/data/git/esp-idf/components/driver/include -I/data/git/esp-idf/components/driver/esp32c3/include -I/data/git/esp-idf/components/esp_ringbuf/include -I/data/git/esp-idf/components/efuse/include -I/data/git/esp-idf/components/efuse/esp32c3/include -I/data/git/esp-idf/components/riscv/include -I/data/git/esp-idf/components/espcoredump/include -I/data/git/esp-idf/components/esp_timer/include -I/data/git/esp-idf/components/esp_ipc/include -I/data/git/esp-idf/components/esp_pm/include -I/data/git/esp-idf/components/vfs/include -I/data/git/esp-idf/components/esp_wifi/include -I/data/git/esp-idf/components/esp_wifi/esp32c3/include -I/data/git/esp-idf/components/esp_event/include -I/data/git/esp-idf/components/esp_netif/include -I/data/git/esp-idf/components/esp_eth/include -I/data/git/esp-idf/components/tcpip_adapter/include -I/data/git/esp-idf/components/mbedtls/port/include -I/data/git/esp-idf/components/mbedtls/mbedtls/include -I/data/git/esp-idf/components/mbedtls/esp_crt_bundle/include -I/data/git/esp-idf/components/app_update/include -I/data/git/esp-idf/components/spi_flash/include -I/data/git/esp-idf/components/bootloader_support/include -I/data/git/esp-idf/components/nvs_flash/include -I/data/git/esp-idf/components/pthread/include -I/data/git/esp-idf/components/esp_gdbstub/include -I/data/git/esp-idf/components/esp_gdbstub/riscv -I/data/git/esp-idf/components/esp_gdbstub/esp32c3 -I/data/git/esp-idf/components/wpa_supplicant/include -I/data/git/esp-idf/components/wpa_supplicant/port/include -I/data/git/esp-idf/components/wpa_supplicant/include/esp_supplicant -I/data/git/esp-idf/components/app_trace/include -I/data/git/esp-idf/components/asio/asio/asio/include -I/data/git/esp-idf/components/asio/port/include -I/data/git/esp-idf/components/bt/common/osi/include -I/data/git/esp-idf/components/bt/include/esp32c3/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/porting/nimble/include -I/data/git/esp-idf/components/bt/host/nimble/port/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/ans/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/bas/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/dis/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/gap/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/gatt/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/ias/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/ipss/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/lls/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/tps/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/util/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/store/ram/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/nimble/host/store/config/include -I/data/git/esp-idf/components/bt/host/nimble/nimble/porting/npl/freertos/include -I/data/git/esp-idf/components/bt/host/nimble/esp-hci/include -I/data/git/esp-idf/components/cbor/port/include -I/data/git/esp-idf/components/unity/include -I/data/git/esp-idf/components/unity/unity/src -I/data/git/esp-idf/components/cmock/CMock/src -I/data/git/esp-idf/components/coap/port/include -I/data/git/esp-idf/components/coap/port/include/coap -I/data/git/esp-idf/components/coap/libcoap/include -I/data/git/esp-idf/components/coap/libcoap/include/coap2 -I/data/git/esp-idf/components/console -I/data/git/esp-idf/components/nghttp/port/include -I/data/git/esp-idf/components/nghttp/nghttp2/lib/includes -I/data/git/esp-idf/components/esp-tls -I/data/git/esp-idf/components/esp-tls/esp-tls-crypto -I/data/git/esp-idf/components/esp_adc_cal/include -I/data/git/esp-idf/components/esp_hid/include -I/data/git/esp-idf/components/tcp_transport/include -I/data/git/esp-idf/components/esp_http_client/include -I/data/git/esp-idf/components/esp_http_server/include -I/data/git/esp-idf/components/esp_https_ota/include -I/data/git/esp-idf/components/protobuf-c/protobuf-c -I/data/git/esp-idf/components/protocomm/include/common -I/data/git/esp-idf/components/protocomm/include/security -I/data/git/esp-idf/components/protocomm/include/transports -I/data/git/esp-idf/components/mdns/include -I/data/git/esp-idf/components/esp_local_ctrl/include -I/data/git/esp-idf/components/sdmmc/include -I/data/git/esp-idf/components/esp_serial_slave_link/include -I/data/git/esp-idf/components/esp_websocket_client/include -I/data/git/esp-idf/components/expat/expat/expat/lib -I/data/git/esp-idf/components/expat/port/include -I/data/git/esp-idf/components/wear_levelling/include -I/data/git/esp-idf/components/fatfs/diskio -I/data/git/esp-idf/components/fatfs/vfs -I/data/git/esp-idf/components/fatfs/src -I/data/git/esp-idf/components/freemodbus/common/include -I/data/git/esp-idf/components/idf_test/include -I/data/git/esp-idf/components/idf_test/include/esp32c3 -I/data/git/esp-idf/components/jsmn/include -I/data/git/esp-idf/components/json/cJSON -I/data/git/esp-idf/components/libsodium/libsodium/src/libsodium/include -I/data/git/esp-idf/components/libsodium/port_include -I/data/git/esp-idf/components/mqtt/esp-mqtt/include -I/data/git/esp-idf/components/openssl/include -I/data/git/esp-idf/components/spiffs/include -I/data/git/esp-idf/components/wifi_provisioning/include -I/data/git/connectedhomeip/src/platform/ESP32 -I/data/git/connectedhomeip/src/include -I/data/git/connectedhomeip/src/lib -I/data/git/connectedhomeip/src -I/data/git/connectedhomeip/third_party/nlassert/repo/include -I/data/git/connectedhomeip/third_party/nlio/repo/include -Iesp-idf/chip/src/include -Iesp-idf/chip/include -Iesp-idf/chip/gen/include -I../third_party/connectedhomeip/config/esp32/components/esp32_mbedtls -I/data/git/connectedhomeip/examples/common/QRCode/repo/c -march=rv32imc -ffunction-sections -fdata-sections -Wall -Werror=all -Wno-error=unused-function -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wextra -Wno-unused-parameter -Wno-sign-compare -ggdb -Wno-error=format= -nostartfiles -Wno-format -Og -fstrict-volatile-bitfields -Wno-error=unused-but-set-variable -std=gnu++11 -fno-exceptions -fno-rtti -std=gnu++14 -Os -DLWIP_IPV6_SCOPES=0 -DCHIP_HAVE_CONFIG_H -D_GNU_SOURCE -DIDF_VER=\"v4.3-beta3-195-g6be10fab0\" -DESP_PLATFORM -std=gnu++14 -MD -MT esp-idf/main/CMakeFiles/__idf_main.dir/__/third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp.obj -MF esp-idf/main/CMakeFiles/__idf_main.dir/__/third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp.obj.d -o esp-idf/main/CMakeFiles/__idf_main.dir/__/third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp.obj -c ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp
In file included from /data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert-production.h:29,
                 from /data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert.h:1725,
                 from /data/git/connectedhomeip/src/lib/support/CodeUtils.h:118,
                 from ../third_party/connectedhomeip/src/system/SystemPacketBuffer.h:33,
                 from ../third_party/connectedhomeip/src/transport/raw/MessageHeader.h:36,
                 from ../third_party/connectedhomeip/src/app/util/basic-types.h:29,
                 from ../third_party/connectedhomeip/src/app/util/af-types.h:55,
                 from ../third_party/connectedhomeip/src/app/util/af.h:69,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server.h:46,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:41:
../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp: In function 'bool emberAfDoorLockClusterGetLogRecordCallback(chip::app::Command*, uint16_t)':
../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:158:80: error: call of overloaded 'Put(uint64_t, EmberAfDoorLockEventType&)' is ambiguous
             SuccessOrExit(err = writer->Put(TLV::ContextTag(2), entry.eventType));
                                                                                ^
/data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert-internal.h:125:38: note: in definition of macro '__nlSHOULD_ASSERT'
 #define __nlSHOULD_ASSERT(condition) condition) { /* do nothing */ } else if (1
                                      ^~~~~~~~~
/data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert.h:1400:81: note: in expansion of macro '__nlEXPECT'
 #define nlEXPECT(aCondition, aLabel)                                            __nlEXPECT(NL_ASSERT_EXPECT_FLAGS, aCondition, aLabel)
                                                                                ^~~~~~~~~~
/data/git/connectedhomeip/src/lib/support/CodeUtils.h:312:32: note: in expansion of macro 'nlEXPECT'
 #define SuccessOrExit(aStatus) nlEXPECT((aStatus) == CHIP_NO_ERROR, exit)
                                ^~~~~~~~
../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:158:13: note: in expansion of macro 'SuccessOrExit'
             SuccessOrExit(err = writer->Put(TLV::ContextTag(2), entry.eventType));
             ^~~~~~~~~~~~~
In file included from ../third_party/connectedhomeip/src/credentials/CHIPCert.h:34,
                 from ../third_party/connectedhomeip/src/credentials/CHIPOperationalCredentials.h:28,
                 from ../third_party/connectedhomeip/src/transport/AdminPairingTable.h:26,
                 from ../third_party/connectedhomeip/src/messaging/ExchangeACL.h:21,
                 from ../third_party/connectedhomeip/src/messaging/ExchangeContext.h:27,
                 from ../third_party/connectedhomeip/src/app/util/af-types.h:58,
                 from ../third_party/connectedhomeip/src/app/util/af.h:69,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server.h:46,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:41:
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:896:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int8_t)'
     CHIP_ERROR Put(uint64_t tag, int8_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:933:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int16_t)'
     CHIP_ERROR Put(uint64_t tag, int16_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:943:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int32_t)'
     CHIP_ERROR Put(uint64_t tag, int32_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:953:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int64_t)'
     CHIP_ERROR Put(uint64_t tag, int64_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:986:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint8_t)'
     CHIP_ERROR Put(uint64_t tag, uint8_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1023:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint16_t)'
     CHIP_ERROR Put(uint64_t tag, uint16_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1033:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint32_t)'
     CHIP_ERROR Put(uint64_t tag, uint32_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1043:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint64_t)'
     CHIP_ERROR Put(uint64_t tag, uint64_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1076:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, double)'
     CHIP_ERROR Put(uint64_t tag, double v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1081:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, float)'
     CHIP_ERROR Put(uint64_t tag, float v);
                ^~~
In file included from /data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert-production.h:29,
                 from /data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert.h:1725,
                 from /data/git/connectedhomeip/src/lib/support/CodeUtils.h:118,
                 from ../third_party/connectedhomeip/src/system/SystemPacketBuffer.h:33,
                 from ../third_party/connectedhomeip/src/transport/raw/MessageHeader.h:36,
                 from ../third_party/connectedhomeip/src/app/util/basic-types.h:29,
                 from ../third_party/connectedhomeip/src/app/util/af-types.h:55,
                 from ../third_party/connectedhomeip/src/app/util/af.h:69,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server.h:46,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:41:
../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:159:77: error: call of overloaded 'Put(uint64_t, EmberAfDoorLockEventSource&)' is ambiguous
             SuccessOrExit(err = writer->Put(TLV::ContextTag(3), entry.source));
                                                                             ^
/data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert-internal.h:125:38: note: in definition of macro '__nlSHOULD_ASSERT'
 #define __nlSHOULD_ASSERT(condition) condition) { /* do nothing */ } else if (1
                                      ^~~~~~~~~
/data/git/connectedhomeip/third_party/nlassert/repo/include/nlassert.h:1400:81: note: in expansion of macro '__nlEXPECT'
 #define nlEXPECT(aCondition, aLabel)                                            __nlEXPECT(NL_ASSERT_EXPECT_FLAGS, aCondition, aLabel)
                                                                                ^~~~~~~~~~
/data/git/connectedhomeip/src/lib/support/CodeUtils.h:312:32: note: in expansion of macro 'nlEXPECT'
 #define SuccessOrExit(aStatus) nlEXPECT((aStatus) == CHIP_NO_ERROR, exit)
                                ^~~~~~~~
../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:159:13: note: in expansion of macro 'SuccessOrExit'
             SuccessOrExit(err = writer->Put(TLV::ContextTag(3), entry.source));
             ^~~~~~~~~~~~~
In file included from ../third_party/connectedhomeip/src/credentials/CHIPCert.h:34,
                 from ../third_party/connectedhomeip/src/credentials/CHIPOperationalCredentials.h:28,
                 from ../third_party/connectedhomeip/src/transport/AdminPairingTable.h:26,
                 from ../third_party/connectedhomeip/src/messaging/ExchangeACL.h:21,
                 from ../third_party/connectedhomeip/src/messaging/ExchangeContext.h:27,
                 from ../third_party/connectedhomeip/src/app/util/af-types.h:58,
                 from ../third_party/connectedhomeip/src/app/util/af.h:69,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server.h:46,
                 from ../third_party/connectedhomeip/src/app/clusters/door-lock-server/door-lock-server-logging.cpp:41:
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:896:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int8_t)'
     CHIP_ERROR Put(uint64_t tag, int8_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:933:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int16_t)'
     CHIP_ERROR Put(uint64_t tag, int16_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:943:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int32_t)'
     CHIP_ERROR Put(uint64_t tag, int32_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:953:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int64_t)'
     CHIP_ERROR Put(uint64_t tag, int64_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:986:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint8_t)'
     CHIP_ERROR Put(uint64_t tag, uint8_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1023:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint16_t)'
     CHIP_ERROR Put(uint64_t tag, uint16_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1033:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint32_t)'
     CHIP_ERROR Put(uint64_t tag, uint32_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1043:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, uint64_t)'
     CHIP_ERROR Put(uint64_t tag, uint64_t v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1076:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, double)'
     CHIP_ERROR Put(uint64_t tag, double v);
                ^~~
/data/git/connectedhomeip/src/lib/core/CHIPTLV.h:1081:16: note: candidate: 'CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, float)'
     CHIP_ERROR Put(uint64_t tag, float v);
                ^~~
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

Compiler version:
riscv32-esp-elf-g++ 8.4.0
Some details
The riscv32 toolchains defines int32_t from long int instead of int. This table shows all common used int type alias on riscv32-esp:

type alias
base type on riscv32-esp

int8_t
signed char

uint8_t
unsigned char

int16_t
short int

uint16_t
short unsigned int

int32_t
long int

uint32_t
long unsigned int

int64_t
long long int

uint64_t
long long unsigned int

In the chip code, the field entry.eventType is a enum, and we are not specific the underlying integer types, so it takes the default int.
Then the problem happen.
As you can see, there is no type alias takes int, and we are not define a function CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int) for compiler. So when the compiler try to invoke chip::TLV::TLVWriter::Put, it confused.

The compiler first tries  chip::TLV::TLVWriter::Put(uint64_t, EmberAfStatus&), but it is not defined. So the compiler should make a implicit cast.
The compiler tries using the underlying integer types CHIP_ERROR chip::TLV::TLVWriter::Put(uint64_t, int) or similar overloads, then it fails due to they are not defined.
The compiler tries to cast from EmberAfStatus to other compatible int type, but it find so many candidates, and it doesn't know which one should be take, so it fails again.

Proposed Solution
I think there are more solutions we can choice:

explicit specify the underlying integer types for EmberAfStatus and other types which may be written to TLV. (But it need C++17)
explicit static_cast EmberAfStatus to int32_t when we call chip::TLV::TLVWriter::Put.
update the riscv32-esp toolchains, and define int32_t from int instead of long int.

It seems this problem is introduced by 80120a20e6a33636c453b072acf22cf77f974f92. @erjiaqing @vivien-apple
And also related #6345

Since the original type is enum, the explicit static_cast sounds a reasonable solution.
As discussed in esp-idf#6906, type alias on riscv32-esp is from the upstream RISC-V toolchain.

Is this fixed by #7266?

Fixed


How to monitor prometheus itself

Towards https://github.com/giantswarm/giantswarm/issues/24746
From @marieroque
The idea is to find a way to monitor the prometheus health.
Hence, we would be able to determine if a scraping issue is coming from an unhealthy prometheus or another reason.

Do we still need this @marieroque ?


BCM700D WiFi doesn't get detected

Describe the bug
I have a BCM700D WiFi curtain motor. When I try to add it (it has a static IP, so I also entered the IP), it says "Sorry, there is no support for this device.".
In the logs, I see:
Device matches None with quality of 0%. DPS: {"updated_at":<PHONE_NUMBER>.2633364, "101": 27, "102": "STOP"}
But this matches abalon_bcm700d_curtain.yaml, so I don't know why this doesn't get detected.
When I power cycle the motor, I get the notification that there are connection issues. When I press the "Learn" button on the device for 5 seconds, I get "Sorry, there is no support for this device." again.
To Reproduce
Trying to add a BCM700D WiFi curtain motor.
Expected behavior
I expect it to connect.
After a power cycle:

After pressing the learn button:

This is everything in the log:

It works now, thank you!


GTOPDB & SmallMolecule

As noted by @andrewsu, GTOPDB:836 is showing up as a SmallMolecule, (it's coming that way out of automat, but that's because NN is tagging that entity as a SmallMolecule).
It looks like we're calling most gtopdb ligands smallmolecules, with a few being molecular mixtures.  But this one is CXCL11, which is a peptide.   We should take a look at the gtopdb classes and make a better mapping.    Probably we should move some of these over into protein/polypeptide.

It looks like we get GTOPDB mappings solely from Unichem (in https://github.com/TranslatorSRI/Babel/blob/ff1fed8ca7378e4b7d5ece9aaa6a62493c4aa6ea/src/datahandlers/unichem.py#L5) -- should we include GTOPDB-PUBCHEM.COMPOUND mappings from GTOPDB's ligands.csv file as well?

I get nervous about including the same mappings from different sources.  My general thought on chemicals is that we want as much as possible from unichem.  That said, we might want to include mappings for things that don't have inchikeys (like this one probably)
It's a little tricky b/c I think we would normally include this chemical in the protein pull rather than the chemical pull, so we might need to split processing of ligands across those two pulls?


Running docker environment get "sudo: unable to resolve host linuxkit-025000000001" and the notebook can not be accessed from the host browser

When running docker script (/path/to/tvm/docker/bash.sh tvmai/demo-cpu), shell shows

sudo: unable to resolve host linuxkit-025000000001

Then after running jupyter notebook from container, the notebook can not be opened from host browser.
It doesn't seem that the container 8888 port is properly expose to the host. My environment:

MacOS 10.14 Beta (18A384a)
Docker version 18.06.1-ce, build e68fc7a

Thanks for bringing it up, please move the general usage discussion to https://discuss.tvm.ai/
In your particular case, it seems due to a docker problem on your side, we are using --net=host option to expose the port. See https://github.com/dmlc/tvm/blob/master/docker/bash.sh#L20

I run into the same error using MBP. Did you solve the problem? thx

Because this is a restriction on MAC or Windows, likely you can get around it by not using --net=host, and lookup the VM address of the docker host, open browser to connect to that part, alternatively, you can try directly map the port used by the notebook

For Mac users, you can modify docker/bash.sh to export port of the container to the host.
diff --git a/docker/bash.sh b/docker/bash.sh
index 23b2e209..2ad7fc53 100755
--- a/docker/bash.sh
+++ b/docker/bash.sh
@@ -35,7 +35,7 @@ DOCKER_IMAGE_NAME=("$1")

 if [ "$#" -eq 1 ]; then
     COMMAND="bash"
-    CI_DOCKER_EXTRA_PARAMS=("-it --net=host")
+    CI_DOCKER_EXTRA_PARAMS=("-it -p 8888:8888")
 else
     shift 1
     COMMAND=("$@")

@viirya do you mind open a PR to fix this? We can certainly change the setting depends on the os we detect

@tqchen Ok. I will do it.


Optimize Valestrom

It's ridiculous how much time it's taking

Did profiling investigations, filed more specific #317 #318 #319.


Unable to mount file system on AmazonLinux but works on Ubuntu

I can compile and run goofys, but always get following error:
"2019/06/27 16:10:16.818151 main.FATAL Unable to mount file system, see syslog for details"
I tried to use pre-compiled binary with same error, however it works fine on Ubuntu.

what does syslog say?

I had some issues with mounting gooyfs on AmazonLinux, but was able to figure out a configuration that worked. Maybe this will help.

Create your mount, such as /mnt/gooyfs
Create /root/.aws/credentials with your standard AWS credentials (you can use the aws-cli as it comes with the distro if you don't feel comfortable creating the file yourself)
Set those permissions to 600 for the credentials file and 700 for the .aws directory
Store gooyfs somewhere reasonable (such as /usr/sbin/gooyfs) and make sure it's executable chmod a+x gooyfs
Create a symlink ln -s /usr/sbin/gooyfs /bin/mount.gooyfs -- I found that setting a path to the binary itself doesn't work (/bin/sh: /usr/sbin/gooyfs: No such file or directory is the error mount -a gives), but a link does for some reason
In the /etc/fstab, add a line similar to this /bin/mount.gooyfs#s3-bucket-name /mnt/gooyfs fuse _netdev,allow_other,--file-mode=0644,--dir-mode=0777,--http-timeout=5m 0 0
Verify mount with mount -a


Add new fields to customizer

The ability to customize the labels so that a state could customize the text to be more appropriate for their voting situation.  Two examples: in an all-mail state, we’d want the option to change it to say “Dropboxes” instead of “Polling Location;” or, a state might want to change “Absentee Voting Information” to “Mail Ballot Information.”
@yulheecho can you confirm which fields will need to be customized?

Based on my understanding from discussions with Amy, it should be:

Left Sidebar/Navigation > Polling Location
Map Detail > Polling Location
Voter Resources > State Elections Office
Voter Resources > Election Information
Voter Resources > Registration Confirmation
Voter Resources > Absentee Voting Information
Voter Resources > Voting Location Finder
Voter Resources > Ballot Information

@acohen84 can you confirm this is an exhaustive list? If not, let us know what the final editable fields should be.
Thanks!
Yulhee

@alexkonrad @yulheecho Yes, that looks right.  Thanks!

Hi @acohen84 Here's a solution that @mickeysanchez came up with. Let us know if this is sufficient and we'll finalize this.

This is exactly what I was imagining, but I’d like to shorten the second line of text to: “The following text is not shown in the customizer preview, but will appear in your embedded tool.”  Important follow up question: will there be spell check?
Thank you for translating my garbled idea into reality!
From: yulheecho<EMAIL_ADDRESS>Sent: Thursday, January 07, 2016 10:57 AM
To: votinginfoproject/vip-embeddable-tool
Subject: Re: [vip-embeddable-tool] Add new fields to customizer (#172)
Hi @acohen84https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_acohen84&d=CwMCaQ&c=2qwu4RrWzdlNOcmb_drAcw&r=QSGvWTnpGC3fpc0QTTn54xRRMxXVsM3JULa8D3VP4i4&m=Vf6kQcAKjw406fta361OagNzZnvYsdMnADzZcZ920sA&s=mw_y-l287rlARCtApBQqP6vNeIQFFwcHtm3cM8vpeak&e= Here's a solution that @mickeysanchezhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mickeysanchez&d=CwMCaQ&c=2qwu4RrWzdlNOcmb_drAcw&r=QSGvWTnpGC3fpc0QTTn54xRRMxXVsM3JULa8D3VP4i4&m=Vf6kQcAKjw406fta361OagNzZnvYsdMnADzZcZ920sA&s=0wu4heuHsMalT-xD1zvfE3U1cwGcxCLA76xKA1Ccb1A&e= came up with. Let us know if this is sufficient and we'll finalize this.
[collapsed]https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_8332232_12174908_5580cd60-2Db52d-2D11e5-2D939e-2D527255cc174f.png&d=CwMCaQ&c=2qwu4RrWzdlNOcmb_drAcw&r=QSGvWTnpGC3fpc0QTTn54xRRMxXVsM3JULa8D3VP4i4&m=Vf6kQcAKjw406fta361OagNzZnvYsdMnADzZcZ920sA&s=B1xZj68zElUkDudXduu-nmTlJ1Hj2AEFsoYTXcp5Xqg&e=
[expanded]https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_8332232_12174907_557e0ea4-2Db52d-2D11e5-2D96f4-2D49a62bc3e7d8.png&d=CwMCaQ&c=2qwu4RrWzdlNOcmb_drAcw&r=QSGvWTnpGC3fpc0QTTn54xRRMxXVsM3JULa8D3VP4i4&m=Vf6kQcAKjw406fta361OagNzZnvYsdMnADzZcZ920sA&s=vVKPOspvq66LXkf-W0pEJn8x0C29GTA0RNTrS_0l-Dk&e=
—
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_votinginfoproject_vip-2Dembeddable-2Dtool_issues_172-23issuecomment-2D169706006&d=CwMCaQ&c=2qwu4RrWzdlNOcmb_drAcw&r=QSGvWTnpGC3fpc0QTTn54xRRMxXVsM3JULa8D3VP4i4&m=Vf6kQcAKjw406fta361OagNzZnvYsdMnADzZcZ920sA&s=6-QukjjUYMZ0Dx4l3Nqs0SVq9YzwNvmT2Oo4jYUYMJA&e=.

hi @ZachMarko @acohen84 Sounds great! Regarding the spell check, yes, we should be able to support this feature, given we still have some hours available from what we allocated for this feature, and that @mickeysanchez was able to find a javascript library that would make this possible. We'll keep you posted with our progress.
Thanks!

Thanks @yulheecho!  I worry that someone changing the text would inadvertently spell something wrong and would like to nip that in the bud if we can.

Hi all.  Just wanted to check in on this.  Thanks!

@acohen84
I've pushed up this addition on staging for you to check out: http://s3.amazonaws.com/vip-voter-information-tool-staging/cms/index.html
Spell check is working, however there is one issue:
On Chrome, the final word in a box does not spellcheck unless you press spacebar after entering it.
The spellcheck we are using is a built in browser feature and works differently across all browsers. We are looking for a workaround for this, but it is unlikely that we can fix the issue unless we take another approach to spellchecking entirely (like using a javascript library). We will keep searching for a workaround for now, but let us know how you'd like us to proceed.

Sorry for my slow response - this looks great and is exactly what I was envisioning.  I'm comfortable with deploying as is, and continuing to look for a workaround.  Sound good?


rpc: re-export jsonrpsee HttpClient and WsClient

celestia-rpc provides convenience functions to return a HttpClient and WsClient, but no way to actually name them other than importing jsonrpsee directly.
celestia-rpc should reexport these (and potentially all of jsonrpsee_http_client, jsonrpsee_ws_client and maybe others, haven't checked) so that downstream users need not directly depend on celestia-rpc's version of jsonrpsee.

we could also just reexport the jsonrpsee itself

Heh, yeah, that's what I ended up doing in my extension trait lib. 🙂

We've been discussing the re-export of jsonrpsee and we think we'd like to avoid it for now. I tried to found examples how is it usually done for crates exposing traits for jsonrpsee but unfortunately I couldn't find a lot of examples (looking at dependant crates on crates.io).
So instead we've thought about wrapping the jsonrpsee clients, so that user don't need to depend on it directly to properly type them, but if some more advanced client or client configuration is needed, then it'll require setting it up on user's end with jsonrpsee directly.
wdyt @SuperFluffy ?


Code must run on gpus?

I tried to run released code on CPUs, however, there's an error.
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
Traceback (most recent call last):
  File "./tools/test_float.py", line 148, in <module>
    main()
  File "./tools/test_float.py", line 101, in main
    init_dist(args.launcher, **cfg.dist_params)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 20, in init_dist
    _init_dist_pytorch(backend, **kwargs)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 33, in _init_dist_pytorch
    torch.cuda.set_device(rank % num_gpus)
ZeroDivisionError: integer division or modulo by zero
Traceback (most recent call last):
  File "./tools/test_float.py", line 148, in <module>
    main()
  File "./tools/test_float.py", line 101, in main
    init_dist(args.launcher, **cfg.dist_params)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 20, in init_dist
    _init_dist_pytorch(backend, **kwargs)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 33, in _init_dist_pytorch
    torch.cuda.set_device(rank % num_gpus)
ZeroDivisionError: integer division or modulo by zero
Traceback (most recent call last):
  File "./tools/test_float.py", line 148, in <module>
Traceback (most recent call last):
  File "./tools/test_float.py", line 148, in <module>
    main()
  File "./tools/test_float.py", line 101, in main
    main()
  File "./tools/test_float.py", line 101, in main
    init_dist(args.launcher, **cfg.dist_params)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 20, in init_dist
    init_dist(args.launcher, **cfg.dist_params)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 20, in init_dist
    _init_dist_pytorch(backend, **kwargs)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 33, in _init_dist_pytorch
    _init_dist_pytorch(backend, **kwargs)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/dist_utils.py", line 33, in _init_dist_pytorch
    torch.cuda.set_device(rank % num_gpus)
ZeroDivisionError: integer division or modulo by zero
    torch.cuda.set_device(rank % num_gpus)
ZeroDivisionError: integer division or modulo by zero
Traceback (most recent call last):
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/launch.py", line 261, in <module>
    main()
  File "/home/mi/miniconda3/envs/open-mmlab/lib/python3.7/site-packages/torch/distributed/launch.py", line 257, in main
    cmd=cmd)

Sorry, our codes only support GPU inference.

Would running the BPR algorithm on a CPU cause a bottleneck?


Optimizations for collectAllBatched and collectAllPar

Hi 👋 I was doing a series of optimizations for Caliban's GraphQL query executor (which relies heavily on ZQuery.collectAllX) and I noticed that there was a fair bit of time spent on calls to ZQuery.collectAllBatched / ZQuery.collectAllPar, especially for larger collections. I had a look at the code and thought to give it a go with rewriting the Result.collectAllX and Continue.collectX to use mutable datastructures and "naked" iterations in order to avoid boxing of primitives and allocations as much as possible.
I run the collectAllBatched benchmarks with, run with the -prof gc to profile GC allocations as well and in a nutshell:
Smaller collections (100 items):

Increases throughput by ~40%
Reduces GC allocations by ~35%

Larger collections (1,000 items):

Increases throughput by ~100%
Reduces GC allocations by ~50%

Benchmark results (click to expand)
series 2/x:
[info] Benchmark                                                       (count)   Mode  Cnt       Score      Error   Units
[info] CollectAllBenchmark.zQueryCollectAllBatched                         100  thrpt   20  192050.951 ± 2643.135   ops/s
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate           100  thrpt   20    6501.672 ±   87.545  MB/sec
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate.norm      100  thrpt   20   35500.014 ±   10.690    B/op
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.count                100  thrpt   20     735.000             counts
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.time                 100  thrpt   20     417.000                 ms
[info] CollectAllBenchmark.zQueryCollectAllBatched                        1000  thrpt   20   18757.456 ±   39.011   ops/s
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate          1000  thrpt   20    6022.526 ±   11.236  MB/sec
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate.norm     1000  thrpt   20  336684.148 ±   81.987    B/op
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.count               1000  thrpt   20     681.000             counts
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.time                1000  thrpt   20     402.000                 ms

PR:
[info] Benchmark                                                       (count)   Mode  Cnt       Score      Error   Units
[info] CollectAllBenchmark.zQueryCollectAllBatched                         100  thrpt   20  269064.461 ± 2661.240   ops/s
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate           100  thrpt   20    5786.653 ±   60.588  MB/sec
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate.norm      100  thrpt   20   22552.009 ±   14.255    B/op
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.count                100  thrpt   20     654.000             counts
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.time                 100  thrpt   20     378.000                 ms
[info] CollectAllBenchmark.zQueryCollectAllBatched                        1000  thrpt   20   36614.670 ± 1175.908   ops/s
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate          1000  thrpt   20    6085.911 ±  195.697  MB/sec
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.alloc.rate.norm     1000  thrpt   20  174296.063 ±    7.125    B/op
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.count               1000  thrpt   20     688.000             counts
[info] CollectAllBenchmark.zQueryCollectAllBatched:gc.time                1000  thrpt   20     388.000                 ms

Please let me know what you think of these changes. I understand that it relies very heavily on mutable code and "naked" iterations, which might not be ideal, but I think it might be worth it to consider given the improvements in performance.
PS: I extracted the logic into generic collectAllImpl methods to keep things DRY, but I'm happy to add the code back to each method if you prefer that.

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

Decided to go in a different direction but thanks for your work on this!


Possibility to customise checkboxes names in yii\grid\CheckboxColumn

Now:
/**
  * @var string the name of the input checkbox input fields. This will be appended with `[]` to ensure it is an array.
  */
public $name = 'selection';

Use case: I need to submit multiple pairs of values (not such rare in practice).
Convenient way is to use input array keys, for example:
<input type="checkbox"
           name="myName[<?= $model->id; ?>]"
           value="<?= $model->someAttribute; ?>" />

Of course another way is to do it with data attributes, but you''ll need to specially handle them with js.
Now you cannot manage keys for autogenerated checkboxes in CheckboxColumn depending on current model, only values.
Braces [] are appended automatically.
Would be nice something like this:
'checkboxOptions' => function ($model, $key, $index, $column)  {

    return ['key' => $model->id, 'value' => $model->someAttribute];
},

related to #7806

Won't be implemented in 2.0.


SocketError when running echoslam

When I try to run echoslam with -gamestateintegration in my launch properties and the example configuration file supplied in the ReadMe I get two different kinds of SocketError depending on how I format the uri:
PS D:\Workspace\dota-gsi> .\target\debug\echoslam.exe --uri "http://<IP_ADDRESS>:3000" Error: SocketError(Os { code: 11001, kind: Uncategorized, message: "Host not found." })
PS D:\Workspace\dota-gsi> .\target\debug\echoslam.exe --uri "http://<IP_ADDRESS>:3000/" Error: SocketError(Error { kind: InvalidInput, message: "invalid port value" })
Folders I have tried placing the cfg file:

D:\SteamLibrary\steamapps\common\dota 2 beta\csgo\cfg (the one specified in the ReadMe for Windows)
D:\SteamLibrary\steamapps\common\dota 2 beta\game\dota\cfg
D:\SteamLibrary\steamapps\common\dota 2 beta\game\dota\cfg\gamestate_integration (folder used by DotaBuff and Overwolf, both of which work fine)

Any assistance would be appreciated.

So I figured it out in the end, turns out you need to omit the http:// part of the uri when supplying it to the GSIServer object, and no matter if you specify localhost or <IP_ADDRESS> in your cfg file you must use <IP_ADDRESS> in the uri to the GSIServer.
However, now that I have it running I have found multiple other problems. #1, many of the fields in GameState are private, such as Map and the game time which is what I wanted to access. #2, while the prints work, there are also a whole lot of error printouts clogging up the output window making me unsure whether the parsed objects are really up to date, as there are several seconds between each successful parse. The following is the error message that is presented: [2023-05-23T15:17:55Z ERROR dota] Failed to parse JSON body: EOF while parsing a value at line 1 column 0
Am I missing something or is this library just not that functional, and I should turn elsewhere?

So I'm not sure what changed but when testing it again I'm getting a whole lot of successful parses, way more than 1/s which is more than enough for my use case. Still having the issue with some of the field being private, but I can parse the JSON on my end to bypass this, and do a PR to this repo to fix it properly some time soon (going on vacation soon so won't be until July probably). Closing this issue as all my questions are answered currently.

Hey @andersastor. I was just on vacation myself during June, sorry I'm only now reaching back to your questions.
The library should still be considered beta, so some errors are expected. I'm thinking of allowing users of the library to pass their own structures to dictate how the GameState JSON will be parsed. In the meantime, will try to dig into any parsing errors, but any PRs you can open are welcome.
Thank you!

Hey @andersastor, quick update: I figured out the issue with JSON parsing. The buffer we were using to read data from the socket was not big enough to accommodate some payloads (sometimes Dota sends 70kb of JSON!). This would cause us to read partial JSONs that would fail parsing. Eventually, we would read a payload small enough so parsing would work again.
As a fix, I just pushed a commit that increases the size of the buffer as we read large JSONs (and also bumped the initial capacity to be at 70kb). I'll publish a new version of the crate that should have your issue solved.
Thanks again for reporting this!


[FEATURE] add support for construct tx with a sighash different than SIGHASH_ALL

would be very powerful, if can be possible to construct transactions , with the other sighash types different than SIGHASH_ALL, like these ones:
https://raghavsood.com/blog/2018/06/10/bitcoin-signature-types-sighash
https://bcoin.io/guides/crowdfund-tx.html
https://learn.saylor.org/mod/book/view.php?id=36341&chapterid=18919
Thanks

duplicated


Release does not run on mac silicon

Hello! Love the idea this project is providing. Knowing zero typescript, I did not try to build from source and instead just use the release. It complained that the executable is damaged but I assume there's maybe something different required for mac silicon (which is what I tried to install on)
Thank you!

Prerequisites

[ ] Using npm
[ ] Using an up-to-date main branch
[ ] Using latest version of devtools. Check the docs for how to update
[ ] Tried solutions mentioned in #400
[ ] For issue in production release, add devtools output of DEBUG_PROD=true npm run build && npm start

Expected Behavior
Installs
Current Behavior
Complains that executable is damaged

Steps to Reproduce
Download and try to install on mac silicon
Possible Solution (Not obligatory)
Build path specifically for apple silicon?
Context

Using a mac air with M1 chip
Your Environment

Node version :
electron-react-boilerplate version or branch :
Operating System and version : Mac OS m1
Link to your project :

Hi @nickvazz, thanks for reporting!
Which .dmg did you try to install? Please make sure that you install the [DrumHero-0.2.1-arm64.dmg](https://github.com/peancored/drum-hero/releases/download/v0.2.1/DrumHero-0.2.1-arm64.dmg) version.
If that doesn't work please let me know.

Just tried that, you're right, something is not right with that version. However, the other .dmg works for me (I'm also on mac M1). Could you please try that one while I try to fix the arm-64 version?

This is with the arm64 version

And with non amd64

Nevermind this  last image, when using the non-amd64 executable, It looks like it was able to be installed - i might have had the previous version still mounted

In order to fix that issue, you need to follow these steps.
As for the arm64 version, it's weird, I can install it locally when I build, but when I upload to github, download and install the app is broken. It might take a while to investigate what's going on.

Instead once it starts up,

Found the solution:
The binary isn't signed so you'll have to remove the file from quarantine once you install the arm64 ver.
# Change the path if necessary
xattr -r -d com.apple.quarantine /Applications/DrumHero.app

it worked!
That worked for installing the arm64.dmg without getting the damaged error. Now it seems like the application flickers with what looks like the UI at startup, then becomes a blank white
almost
My guesses as to what could be happening:

Is there some sort of cache or something where the initial file path of things it's looking for is? When i had first installed the non amd64 version as you suggested, it did give me a popup of a folder selection menu, but never after initial startup.

Does it crash if there are too many songs? I have roughly 1500 songs I've downloaded

If the songs are damaged in a clone hero sense, does it crash? some of those downloads could be duplicates of broken files but haven't combed through yet

Thanks for the help and still very excited to try! :)

Awesome!

Please, remove the ~/Library/Application Support/drum-hero folder and try opening the app again. Don't skip the selection menu 🙂
It should not, I have 3000+ songs and it works fine
There might be some issues indeed if a song is broken, this is the case that I haven't tested. But something tells me that that's what's happening, since the blank screen shouldn't happen under any circumstance.

Try an isolated folder maybe with a limited number of songs and see whether it works correctly?

Oh actually, before you delete it, can you share your ~/Library/Application Support/drum-hero/config.json with me? It will help debug the issue.

config.json

When I delete the directory and relaunch, it gives me the option to select a directory of songs again.
Deleting the directory and pointing at a single song directory seems to work - so maybe it crashes with bad files 🤷🏾

Thanks for the help debugging!

The issue is that song: "/Users/nickvazz/Clone Hero/Songs/Motörhead - Motörhead"
Its config has some weird encoding. If you remove that folder and rescan the songs, everything should work as expected.

The issue here is specifically related to the .ini encoding in the song folder, here's what the config contains:
		"fb99959a-38e5-4eac-9f3f-6afe3dbe6c4b": {
			"id": "fb99959a-38e5-4eac-9f3f-6afe3dbe6c4b",
			"dir": "/Users/nickvazz/Clone Hero/Songs/Motörhead - Motörhead",
			"��[\u0000s\u0000o\u0000n\u0000g\u0000]\u0000": true,
			"\u0000": true,
			"\u0000a\u0000r\u0000t\u0000i\u0000s\u0000t\u0000 \u0000": "\u0000 \u0000M\u0000o\u0000t\u0000�\u0000r\u0000h\u0000e\u0000a\u0000d\u0000",
			"\u0000n\u0000a\u0000m\u0000e\u0000 \u0000": "\u0000 \u0000M\u0000o\u0000t\u0000�\u0000r\u0000h\u0000e\u0000a\u0000d\u0000",
			"\u0000a\u0000l\u0000b\u0000u\u0000m\u0000 \u0000": "\u0000 \u0000M\u0000o\u0000t\u0000�\u0000r\u0000h\u0000e\u0000a\u0000d\u0000",
			"\u0000y\u0000e\u0000a\u0000r\u0000 \u0000": "\u0000 \u00001\u00009\u00007\u00007\u0000",
			"\u0000g\u0000e\u0000n\u0000r\u0000e\u0000 \u0000": "\u0000 \u0000H\u0000e\u0000a\u0000v\u0000y\u0000 \u0000M\u0000e\u0000t\u0000a\u0000l\u0000",
			"\u0000i\u0000c\u0000o\u0000n\u0000 \u0000": "\u0000 \u0000g\u0000h\u00003\u0000d\u0000l\u0000c\u0000",
			"\u0000t\u0000a\u0000g\u0000s\u0000 \u0000": "\u0000 \u0000m\u0000a\u0000s\u0000t\u0000e\u0000r\u0000",
			"\u0000u\u0000n\u0000l\u0000o\u0000c\u0000k\u0000_\u0000i\u0000d\u0000 \u0000": "\u0000 \u0000g\u0000h\u00003\u0000_\u0000d\u0000l\u0000c\u00001\u00005\u0000",
			"\u0000c\u0000h\u0000a\u0000r\u0000t\u0000e\u0000r\u0000 \u0000": "\u0000 \u0000<\u0000c\u0000o\u0000l\u0000o\u0000r\u0000=\u0000o\u0000r\u0000a\u0000n\u0000g\u0000e\u0000>\u0000N\u0000e\u0000v\u0000e\u0000r\u0000s\u0000o\u0000f\u0000t\u0000<\u0000/\u0000c\u0000o\u0000l\u0000o\u0000r\u0000>\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000b\u0000a\u0000n\u0000d\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000g\u0000u\u0000i\u0000t\u0000a\u0000r\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000b\u0000a\u0000s\u0000s\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000d\u0000r\u0000u\u0000m\u0000s\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000k\u0000e\u0000y\u0000s\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000g\u0000u\u0000i\u0000t\u0000a\u0000r\u0000g\u0000h\u0000l\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000d\u0000i\u0000f\u0000f\u0000_\u0000b\u0000a\u0000s\u0000s\u0000g\u0000h\u0000l\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000p\u0000r\u0000e\u0000v\u0000i\u0000e\u0000w\u0000_\u0000s\u0000t\u0000a\u0000r\u0000t\u0000_\u0000t\u0000i\u0000m\u0000e\u0000 \u0000": "\u0000 \u0000-\u00001\u0000",
			"\u0000a\u0000l\u0000b\u0000u\u0000m\u0000_\u0000t\u0000r\u0000a\u0000c\u0000k\u0000 \u0000": "\u0000 \u00001\u00006\u00000\u00000\u00000\u0000",
			"\u0000p\u0000l\u0000a\u0000y\u0000l\u0000i\u0000s\u0000t\u0000_\u0000t\u0000r\u0000a\u0000c\u0000k\u0000 \u0000": "\u0000 \u00004\u00002\u0000",
			"\u0000v\u0000i\u0000d\u0000e\u0000o\u0000_\u0000s\u0000t\u0000a\u0000r\u0000t\u0000_\u0000t\u0000i\u0000m\u0000e\u0000 \u0000": "\u0000 \u00000\u0000",
			"\u0000d\u0000e\u0000l\u0000a\u0000y\u0000 \u0000": "\u0000 \u00000\u0000",
			"\u0000s\u0000o\u0000n\u0000g\u0000_\u0000l\u0000e\u0000n\u0000g\u0000t\u0000h\u0000 \u0000": "\u0000 \u00001\u00009\u00008\u00002\u00008\u00002\u0000"
		},

That .ini file contains meta information about the song - its name, album, difficulty, etc.
But in that specific .ini config the keys and values are not properly encoded, and that's why the app breaks when trying to display song names in the list (song.name is undefined).
I don't think it's necessarily because the song itself is damaged, so you won't be able to tell that from config, unfortunately.


Bluetooth Issue

When scanning for bluetooth printers, i get a system dialog popup with the list.  If I search using the method "findPrinters" it refers to bluetooth printers like they should popup in the array and not in a system dialog box. This is not the case.  Nothing happens with bluetooth.  Is this normal?

Looking at the latest code in this plugin for iOS:

"findPrinters" is only calling "findNetworkPrinters", and the bluetooth code is commented out. So, I would not expect to find BT printers with this current code.
"findBluetoothPrinters" will return a list of "already connected" printers, or if none are currently connected it will show the iOS system dialog that allows "pairing".

So, it sounds like your printer is not connected to your iOS device, since you are seeing the system dialog.
If it IS connected and still NOT showing up in the list, then the problem is likely that you have not added the MFi protocol string to your info.plist. If this hasn't been added to your plist, then connected printers will not show up. For Brother printers, this MFi protocol string is "com.brother.ptcbp".
NOTE: Beware that if you support MFi printers in your app (as evidenced by this Protocol String in your info.plist), you are required to acquire a PPID (Product Plan ID) and list this in your AppStore submission notes; otherwise your app will be REJECTED by Apple. Each MFi device manufacturer will have a different process. The Brother process begins here:
https://secure6.brother.co.jp/mfi/Top.aspx
-Rob

Food for thought.  Thanks for the response. This is why the app stores are broken. So many random rules and restrictions that most devs don't know about.

BlueTooth is now working on iOS.
I have tested this on QL820NWB
PR: https://github.com/MenelicSoftware/cordova-plugin-brother-label-printer/pull/48
New plugin version is 1.6.0