How to set the config to create a stand_alone commandline demo ?

Here is the function that loads the model and tokenizer. What would be the _config ??
using @ex.automain would result in the follwing warning:
WARNING - timm.models.helpers - No pretrained weights exist or were found for this model. Using random initialization.
Here is the function.
def prepare_model(_config):
_config = copy.deepcopy(_config)
loss_names = {
    "itm": 0,
    "mlm": 0.5,
    "mpp": 0,
    "vqa": 0,
    "imgcls": 0,
    "nlvr2": 0,
    "irtr": 0,
    "arc": 0,
}
tokenizer = get_pretrained_tokenizer(_config["tokenizer"])

_config.update(
    {
        "loss_names": loss_names,
    }
)

model = ViLTransformerSS(_config)
model.setup("test")
model.eval()

# device = "cuda:0" if _config["num_gpus"] > 0 else "cpu"
device = "cpu"
model.to(device)
return tokenizer,model, device

fixed it. My code works. There was a problem with my environment.


[BUG] Valid transaction rejected by signTx with error code -1

below the cbor of the transaction
84aa00828258205ebb7fd41693ca030241d4b26f7feb31ca6760f1884170c416d912b20d42576501825820f445815a4829226f388c85fbc276ad3e6e362cfa5926b5a7c1c2a9e40871927c010184a2005839006be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d791f4c0646398c6943842fa92ce580086198de6cf0748dd25963c8ce15c01821a001e8480a1581c7392e007a94557f29c92396263fe1e9611d6855572f5436f40b09e9fa14c416666696c6961746520233701a2005839006be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d791f4c0646398c6943842fa92ce580086198de6cf0748dd25963c8ce15c011a0085e558a2005839006be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d791f4c0646398c6943842fa92ce580086198de6cf0748dd25963c8ce15c011a000ee098a2005839006be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d791f4c0646398c6943842fa92ce580086198de6cf0748dd25963c8ce15c011a038ecff2021a0007ae32031a01b54bf408000b5820690cd9a2915e8da05e9ff28d3e6574fcc4c853945a4d58a6546de2597df0e1490d81825820f445815a4829226f388c85fbc276ad3e6e362cfa5926b5a7c1c2a9e40871927c010e81581c6be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d7910f0010a2005839006be8e97edf291dea073bfccddb3e49b4fcf9b6a55e473afbec74d791f4c0646398c6943842fa92ce580086198de6cf0748dd25963c8ce15c011a03e4b22ea20581840000d87980821988a81a00a86a7c06815902b25902af010000323232323232323232322225333573466664444646466660260084660266602666026a00426ae8cd5d11bac3574200626ae8cd5d11bac30110031323232330163375e602800266e95200433574066e9520003357406ae8400ccd5d01ba8375a6ae84010cd5d01aba10023357406ae84d5d100119aba037506eb4c050010cd5d01ba8375a6026008024024266644464664a666ae68c005200010031533357346002900108020b1b8735573a0026aae78004dd50019aba1301535742002464646464646464646464646464646466e3cdd71aba1010001375c0026ae84004d55cf0009baa00135742002603e0026ae84004c074004c068004c06c004d5d08009bac3574200260300026ae84004c058020928180a1aba13758602660286ae84c050018d5d11aba200135573c6ea8018940088c8c8c8c8c8c8cccc0680040188cdc49bad357420026eb4c8d5d09aba2357446ae88d5d11aba2001301900d00635742002602c00260260026028002646ae84d5d11aba2357446ae88d5d11aba23574400260266ae84c04c01492809991980590a502223322533357340042944004c0100084c00c004dc79bae357426020008664664601646ae80c0080040052f588eb8dd6191aba1357446ae88d5d11aba2357446ae88d5d11aba2001001300f35742601e00291011c1f8d0e1cc67adec0ad6231ac540ccec1fcc310485fa68d74c9ae2db10000300200114985888cc00c84008888cc014008c00c004c0088888c8ccc018c010004c00c004008cc01000c0088894ccd55cf8008018998011aba1001357440024646004466004004002460044660040040026ec5262357426ae880048d5d09aba23574400246aae78dd5000912999ab9a00200114a0444464664a666ae68c005200010031533357346002900108020a999ab9a300148010401458dc39aab9d00135573c0026ea80101f5f6

The error message thrown by nami.signTx is:
{
    "code": -1,
    "info": "Inputs do not conform to this spec or are otherwise invalid."
}

pasting the above transaction in cbor.me is clear that the inputs (entry 0 of the transaction body) are valid (according to the cardano-ledger cddl:
82                                # array(2)
   82                             # array(2)
      58 20                       # bytes(32)
         5EBB7FD41693CA030241D4B26F7FEB31CA6760F1884170C416D912B20D425765 # "^\xBB\u007F\xD4\u0016\x93\xCA\u0003\u0002AԲo\u007F\xEB1\xCAg`\xF1\x88Ap\xC4\u0016\xD9\u0012\xB2\rBWe"
      01                          # unsigned(1)
   82                             # array(2)
      58 20                       # bytes(32)
         F445815A4829226F388C85FBC276AD3E6E362CFA5926B5A7C1C2A9E40871927C # "\xF4E\x81ZH)\"o8\x8C\x85\xFB\xC2v\xAD>n6,\xFAY&\xB5\xA7\xC1©\xE4\bq\x92|"
      01                          # unsigned(1)

Hey @michele-nuzzi!
I am exploring the Nami dead issues and trying to resolve at least some of them. While I assume that this is no longer an issue for you, I wanted to clarify what was happening here for you, and others who may have similar questions.
This behavior is the expected behavior, as specified in CIP-30.
I cannot be 100% sure what happened in this case, because I do not have all the information about the inputs being consumed in this transaction and what keys you were attempting to sign with. However, according to CIP-30, the wallet is expected to throw a TxSignError if partialSign is not true and the wallet cannot provide a signature for all required keys.
While I don't know the specifics of what key was signing, looking at the transaction I can see that there was a required signer. I am assuming that was different from the signer needed to consume the inputs. Therefore, the TxSignError should've been thrown, according to the specification.
The "Inputs" word in the error message is a bit complicated, since it is not referring to transaction inputs, but instead the arguments passed to the function call. That error message also comes from CIP-30, which could be improved but this is not the place.
Hopefully, that clears up confusion!


get_model line in test.py

I have a question about line 67 in test.py:
model = get_model(model_name, n_classes, version=args.dataset)
model_name is a string but the first argument in get_model is a dict so the code raises an exception here.
Am I missing something?

https://github.com/meetshah1995/pytorch-semseg/blob/81997cd5af36759773a67b11cf148d3876b13a69/ptsemseg/models/__init__.py#L14
I think that this line get the model name from dict, and use _get_model_instance  get an instance of the arch you want to use, what's your error?

Thanks for your response. The problem is that get_model is being passed a string, not a dict, as the first argument in line 67 of test.py.

oh, I get it, maybe you could add if ... else in  get_model  function to solve this error,such as;
if isinstance(model_dict,str):
        model = _get_model_instance(model_dict)
else:
        name = model_dict['arch']
        model = _get_model_instance(name)

if isinstance(model_dict,str):
model = _get_model_instance(model_dict)
else:
name = model_dict['arch']
model = _get_model_instance(name)

This wont help because later we use it again as a dictionary

#131 check this issue. It has been answered here


victor-hugo and jane

Hi,
first of all thank you for this beautiful theme.
I'm trying to develop a hugo website in netlify using victor-hugo boilerplate and Jane as theme.
When I work locally, I have no problem, when I open the build webiste in netlify, I have no dist/jane.min.css file in remote website.
Probably I must copy and paste some file from victor-hugo/site/themes/hugo-theme-jane/src to victor-hugo/src, but I do not know wich. Could you give me some help?
Thank you

I am not familiar with victor-hugo. It looks a good boilerplate. If I have time, I will take a look.
For Jane-Theme project, there is a named webpack.config.js file in the root folder. This file has many config, and it is an important develop file.


charmxi crashes with unnamed param in SDAG when clause

Original issue: https://charm.cs.illinois.edu/redmine/issues/249

If I say

when foo(int /* no name, because I'm not using it */) atomic {
  // Do stuff based on the message having arrived
}

charmxi crashes, by dereferencing a NULL pointer to the non-existent name, in SdagConstruct::generateWhen()
It should instead generate an appropriate dummy symbol in which to unpack that value (if needed), and otherwise ignore it.

Original date: 2013-08-28 19:15:28

Consult with Jonathan as needed, please use this bug fix as a motive to familiarize yourself with Charmxi as infrastructure supporting various HLL efforts.

Original date: 2013-10-24 21:34:29

The parameter is ignored, if it's unnamed.

Original date: 2013-10-24 21:50:11

The change to fix this is not quite right. Whatever sent the message that matched the when clause will still have PUPed that entry method argument, regardless of it not being referenced in the implementation. By ignoring some variables on the receiving side entirely, the corresponding values in the packed up message will end up assigned incorrectly.
Take a look at my modified test on branch '249'. It asserts that the value of b is as expected. As I describe above, that assertion fails.
Please amend the code to address this, and squash your subsequent commits with my test when you merge to mainline, so that we're not left with an explicit 'break the test' commit.

Original date: 2013-10-25 03:43:42

I see your point. But ignoring the variable in the entry method does not make sense as there can be multiple when statements using the same entry method and some of them might have unnamed parameters while some of them have not.
Then creating a dummy name seems less complicated than ignoring the variable. There could be more than one unnamed parameters in a when construct and the generated dummy name should be distinct, so it requires to keep a counter probably.
Creating a dummy name does not really have a disadvantage over ignoring the variable, right?

Original date: 2013-10-25 03:52:59

When I opened the bug, I assumed dummy variables were necessary. Seeing the alternate design, I believe they really are necessary.
There is a nominal disadvantage to using dummies over skipping unused arguments entirely. Namely, if we could ask the PUPer to 'advance' past the arguments that we don't care about, we would save a bit of memory used and code executed. However, the PUP buffer would have to carry extra information to tell us how far to advance in its buffer, since non-primitive types can take arbitrary variable amounts of space when PUPed.
The only hypothetical optimization to the dummies that I can see would be only having one for each type, rather than one for each formal parameter. This shouldn't make an actual difference, since the compiler should be able to see that the individual variables are never used and optimize them out. I would skip this optimization as overcomplicated.

Original date: 2013-10-25 17:09:54

Ok, I've created dummy variables instead. Can you have a look at branch 249 before I merge my changes to the main branch. Thanks!

Original date: 2013-10-25 17:18:07

Just to confirm, it passes the modified test now?

Original date: 2013-10-25 17:22:00

yes, it does.

Original date: 2013-10-25 17:37:27

Since we're looking at this now, I may as well suggest being more selective about which list(s) of state variables the dummy variable gets added onto. Since we know it's never going to be referenced, it only needs to be on the list of variable unpacked from the incoming message - it doesn't need to be saved for the body of the when or any of its children.
The code is fine to integrate as is, but it would be good if you could figure out the above optimization (with Jonathan's help, as needed).

Original date: 2013-10-25 20:47:35

My latest commit to the branch does this optimization now. I've tested it and it works.
If I'm not missing anything, it should be fine.

Original date: 2013-10-25 21:23:53

Could you push your updated code?

Original date: 2013-10-25 21:26:43

Oh sorry, I've pushed!

Original date: 2013-10-25 21:43:07

The code looks good. Please integrate it to mainline with git merge --squash, and delete the branch afterward.

Original date: 2013-10-27 21:20:52

Confirmed test passes on mainline.


Decoding adjustments

I've rebased some of my old encoding related pull requests on master. Thanks to @grosser and @jeremy  some of this stuff is finally getting into mail :)
Part of this pull request are:

some more tests based on some strange stuff we've seen that broke the mail lib
adjusted the b_value_decode to return the original string instead of some part of it (str is overwritten by the match).
Japanese users love to use emoji which are sometimes non-defined UTF-8 characters. So telling the encode method to simply skip those gives us at least a decoded string without the characters that can't be displayed anyway. Better than the encoded version.

Please consider merging this, we've been using those since quite a while and I'd really appreciate it if I could get rid of my patch branch. Thanks!

Test cases ~passing on master 😊


Fix links inside distributed/index.md

Can one of the admins verify this patch?

@tensorflow-jenkins test this please.

PR merged. Thanks!


Step 6 the field Type does not exist in RCS

Create a connected application

Sign in to your RCS account.
In the Globalization feature workspace, in the Related links section, select Environment setup.
On the Environment setup page, on the Action Pane, select Connected applications.
Select New to create a connected application.
In the Name field, enter the name of the application to connect.
In the Type field, select Dynamics 365 Finance.
In the Application field, enter the URL of the environment to connect.
In the Tenant field, enter the tenant of the environment.
Select Save.

Step 6 the field Type does not exist in RCS

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

ID: 3197c22f-c401-5af8-ef6e-c6fbcdda4084
Version Independent ID: 3197c22f-c401-5af8-ef6e-c6fbcdda4084
Content: Connected applications - Finance | Dynamics 365
Content Source: articles/finance/localizations/e-invoicing-connected-applications.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @gionoder
Microsoft Alias: gionoder

@kfend, can you please investigate?

Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Limit Service Account permissions

For the initial release permissions for service accounts are going to be locked down so they only can be used with explicitly granted system indexes
Exit Criteria

[ ] modify authz workflow to filter out all permissions other than index permissions with system index grant
[ ] add/modify test case that confirms cluster-wide permissions are not accessible
[ ] add/modify test case where index permissions without system index grant is filtered out
[ ] add/modify test case where index permissions with system index grant is allowed (happy path)

Looks good to me!

[Triage] Thank you for filing this issue @peternied. This issue has clear expectations for action items (completing the check list) so going to mark as triaged.

modify authz workflow to filter out all permissions other than index permissions with system index grant

@peternied What if this did not rely on a role at all and instead extension initialization included a reserved_indices setting that can be used on initialization for extension to reserve indices.
With this setting, the ExtensionsManager will have a mapping from <extension_unique_id> -> reserved set of indices.
Can the service account not be mapped to any roles at all and only carry the identity of the extension?
Within the SystemIndexAccessEvaluator it can lookup if a request is coming from an extension's service account and determine if the extension is making the request on only its set of reserved indices and no other indices or else fail the request.
The implementation of service account tokens I did in https://github.com/opensearch-project/opensearch-sdk-java/pull/892 to show the SDK integrated with security for extensions does this if you'd like to see an example.

This task has already been triaged, pointed, and scheduled in the current sprint, I'm not sure what you are asking?

@peternied I'm concerned that it could be confusing to have a role like
extension_a_svc_account_role:
  reserved: true
  hidden: false
  static: true
  description: "Allow full access to all indices and all cluster APIs"
  cluster_permissions:
    - "*"
  index_permissions:
    - index_patterns:
        - "*"
        - ".opensearch-observability"
      allowed_actions:
        - "*"
        - "system:admin/system_index"
  tenant_permissions:
    - tenant_patterns:
        - "*"
      allowed_actions:
        - "kibana_all_write"

but effectively we introduce logic to whittle it down to
extension_a_svc_account_role:
  reserved: true
  hidden: false
  static: true
  description: "Allow full access to all indices and all cluster APIs"
  index_permissions:
    - index_patterns:
        - ".opensearch-observability"
      allowed_actions:
        - "*"
        - "system:admin/system_index"

behind the scenes. (At least that's what I'm understanding this issue to be from the description). Is my understanding incorrect?
If we can modify the SystemIndexAccessEvaluator to lookup at extension's settings based on its principal then we can determine if that principal is associated with the system indices being acted upon. I think its simpler and logic does not need to be introduced to "whittle down" a role.

@cwperks that is the correct observation.  It is intentional to be strange, because its easy to implement and easy to revert without breaking deployed services accounts if/when we invest more into this space.  Since extensions are not in active development, features such as service accounts are minimally built up to support these scenarios and we can improve on them as provides value.
Since this is already costed and included in the sprint change this design is a signal to remove it from the sprint.  Lets move the meta discussion to an internal channel were we figure out how to handle this item.


docs: Disable iLogtail self-circuit breaker feature in k8s deployment.

Add note on disabling iLogtail self-circuit breaker feature in k8s deployment

 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.

@CyshallChan Could you please sign the CLA?

@CyshallChan Could you please sign the CLA?

可以了


New release ?

Tests in the latest release (0.6.0) are broken with numpy >=1.24 (see #856). This is fixed in master, but not in the latest release (which is about 1.5 years old). Perhaps it's time for a new release?

Yes, thanks for pointing this out - I intend to make a release soon.

Thanks for the release @keflavich


Fix help message for 'id query'

Looks like a bad copy&paste:
$ cargo crev id
cargo-crev-id 0.10.1
[...]
SUBCOMMANDS:
    current     Show your current Id
    distrust    Distrust an Id
[...]
    query       Distrust an Id

Thanks!


Allow to use MongoDB in "readPreference=secondary" mode

Problem
Prisma requires MongoDB to run in a cluster mode, which in theory means that secondary nodes can be used for read only purposes, thus allowing more capital efficiency (by elevating read operations from primary node). However when this setting is set readPreference=secondary Prisma throws an error stating that it uses transactions and can only do so on primary node.
As far as I understand mongo supports transactions across cluster / shards, so am wondering if this limitation is only on prisma side and could be implemented In the future?

This is a current limitation on prisma, that could be enhanced in the future.
As of 4.2, mongo supports transactions on replica nodes. However, such transactions are only eventually consistent, and read-after-write's consistency can only be guaranteed to if the read operation was pinned over the replica where the transaction occurred. That's why
Multi-document transactions that contain read operations must use read preference primary.
Because with Prisma is common to create transactions that perform read operations, we can't capitalize on the readPreference=secondary for prisma unless we limited reads on transactions (which is impractical in the case of nested associations / connecting records); or if Prisma routed transactions that didn't incur in read operations to a connection pool with that setting enabled (which has a different set of trade-offs)

same issue here
is there a way to create a workaround, where writes automatically being sent to primary? e.g. a new connection being established with readPreference=primary, just for a write?
or, is there a way to let us pass an additional parameter to a query, that let's devs specify a connection or connection attributes
p.s. Currently i've created a new instance of Prisma, just for writes… not ideal - have to rewrite a lot of code


tezos-encoding + derive: keep track of lifetime in NomReader

The NomReader trait is implicitly parameterized by the lifetime of the input byte slice. This commit makes the quantification on this explicit. This is needed to implement NomReader for structures which keep a reference to some slice of the input, for example to implement lazy deserialization.

Thanks for the PR! Overall a big fan of adding something like this.
Pretty happy with the first commit - most comments focused on the second (perhaps could be split out into a second PR if needed)


cosmos spring multi-tenant samples

Purpose
Adding samples for multi-tenancy in Spring Cosmos DB for database and container level isolation.
These are based on PRs for:
container level multi-tenancy: https://github.com/Azure/azure-sdk-for-java/pull/33400
database level multi-tenancy: https://github.com/Azure/azure-sdk-for-java/pull/32516

...

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x] Other... Please describe: code samples

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Should we move common files like those for User, Order and TenantStorage to a common directory that can be shared to reduce duplication? Or do we want each to be fully self-contained so we do not do that?

Should we move common files like those for User, Order and TenantStorage to a common directory that can be shared to reduce duplication? Or do we want each to be fully self-contained so we do not do that?

Just because this is a sample, prefer it to be a bit more contrived than usual.

Hi, @TheovanKraay

container level multi-tenancy: https://github.com/Azure/azure-sdk-for-java/pull/33400
database level multi-tenancy: https://github.com/Azure/azure-sdk-for-java/pull/32516

Is it possible to demonstrate the 2 features by spring profile instead of 2 sample projects?
Here is an example: https://github.com/chenrujun/service-bus-dead-letter-queue-sample/blob/e2ab89fde4b6fce2dbb4163efc50a2a4c7d3a2a3/README.md#receive-message-by-jmslistener

I left some comments about the first sample. The comments can apply to both of the 2 samples. Please update the 2 samples according to my comments.

Ok, I will address them.

@TheovanKraay

Whilst I like the idea, can we keep it as it is for now? It will be a lot of effort to re-factor.

OK.

Hi, @TheovanKraay

container level multi-tenancy: Azure/azure-sdk-for-java#33400
database level multi-tenancy: Azure/azure-sdk-for-java#32516

Is it possible to demonstrate the 2 features by spring profile instead of 2 sample projects? Here is an example: https://github.com/chenrujun/service-bus-dead-letter-queue-sample/blob/e2ab89fde4b6fce2dbb4163efc50a2a4c7d3a2a3/README.md#receive-message-by-jmslistener

Whilst I like the idea, can we keep it as it is for now? It will be a lot of effort to re-factor. Also, in practice, changing tenant isolation level also changes how you will architect the data model (e.g. co-locating types and different throughput settings etc), and I think one is likely to go one way or another for a given multi-tenant app, but not both. So, I am not sure real-world apps will have different profiles for different isolation levels using Cosmos. @trande4884 any thoughts on this?

I agree to hold off on the Profile change. I think it could be discussed for a future PR if we want to go that route, but I have not seen any activity from our users on Profile usage so I'm not sure that is the best route to go in our samples. I also just like the standalone samples as they are very clear to the user as to what is needed.


Drop emit of last semicolon in single-line object literal types

Tracking follow-up to #33402
When synthetic object literal type nodes are printed on a single line, they come out like
type X = { a: string; b: string; };

While working on semicolon formatting features, I briefly had the formatter remove the semicolon after b: string;. The result was well-received but I ultimately decided the logic didn’t belong in the formatter; if this was going to be the canonical formatting of single-line object type literals, they should simply come out of the emitter that way.

Why semicolons?  Why not just
type X = { a: string, b: string };

I only usually use semicolons in interfaces.

This is also how I write single-line object types. Honestly I’m a little worried that any change I make here will incite an angry mob composed of people with a particular lint rule. So I guess the answer to your question is “fear of public ridicule,” or I guess more seriously, a preference not to shake things up for everyone without a good reason. Which is why I’m not totally confident that I will make this change at all.

Personally I'd prefer comma.
Prettier users will get their ; for free*
type X = { a: string, b: string };
// emitted as
type X = { a: string; b: string };

for better or worse (definitely worse, because it will replace my ,)


Support OpenGL ES 2.0/3.0 on Desktop systems

Migrated from (3) (and other discussion) in https://github.com/elucideye/acf/issues/102#issuecomment-487247357
The current code assumes OpenGL ES 2.0 or 3.0 on iOS and Android, but OpenGL for all other platforms.  This is a limiting assumption, since it is possible to run OpenGL ES 2.0/3.0 on other platforms.  Both the back end ogles_gpgpu lib and the aglet test lib support this configuration, so ACF can be updated to support it too.

See #110


Rancher doesn't work with arm32v7 (Raspberry Pi4 Cluster)

Hi, I just imported a  k3s RasPi 4 cluster into Rancher and it's stuck in pending state.

Yep, appears that  rancher/rancher-agent:v2.3.0 does not work with my ARMv7 Processor rev 3 (v7l) in the new RasPi 4.

Issue persists even when pulling the image using the Docker CLI
pi@node-1:~ $ docker pull rancher/rancher-agent:v2.3.0
v2.3.0: Pulling from rancher/rancher-agent
no matching manifest for linux/arm/v7 in the manifest list entries

Related:

https://github.com/rancher/rancher/issues/2101
https://github.com/rancher/rancher/issues/10868

Have the same problem. Rancher is not working on the pi 4 (hypriotos as rancheros is also not working)

Also having the same problem.
Did you found a working solution meanwhile ? I am failing updating the image for the cattle-node-agent and cattle-cluster-agent to use this instead:
rancher/rancher-agent:v2.2-head-linux-arm64

I did not find a workaround, but I'm curious if this new Docker feature could work:
https://docs.docker.com/docker-for-mac/multi-arch/

so long time

NAME                                        READY   STATUS             RESTARTS   AGE
pod/cattle-node-agent-26zqp                 0/1     ImagePullBackOff   0          6m25s
pod/cattle-cluster-agent-745db996cc-2lwzr   0/1     ImagePullBackOff   0          6m25s

NAME                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/cattle-node-agent   1         1         0       1            0           <none>          6m26s

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/cattle-cluster-agent   0/1     1            0           6m26s

NAME                                              DESIRED   CURRENT   READY   AGE
replicaset.apps/cattle-cluster-agent-745db996cc   1         1         0       6m26s

yes, just rancher/rancher-agent  no rancher-agent-armhf  image
only  linux-amd64，linux-arm64，windows-amd64
ubuntu arm64  K3S docker ：No container started

I was previously able to import a K3S cluster on PI-4's into  Rancher, but the PI-4's were running Ubuntu,  I've had to go back to Raspbian for various reasons and am now experiencing this problem.  Strange.      I'll have to try and reboot on Ubuntu to see what image it is using (could ubuntu on pi-4  support linux-arm64?)
I'd really like to stick with Raspbian - or is this a dead-end since images haven't been built for so long...

ok, doesn't seem to be an issue between ubuntu or raspbian.   i can no longer get ubuntu connected either.    Is it possible an earlier release of rancher-agent briefly support the Pi 4 ?

This is the exact error - same message on both unbuntu and raspbian -
Feb 27 19:35:44 Pi4-51 k3s[9563]: E0227 19:35:44.292758    9563 kuberuntime_image.go:50] Pull image "rancher/rancher-agent:v2.3.5" failed: rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/rancher/rancher-agent:v2.3.5": failed to unpack image on snapshotter overlayfs: no match for platform in manifest sha256:e6aa36cca0d3ce9fea180add5b620baabd823fb34f9d100b7a8d3eb734392c37: not found

So a bit more investigation reveals that rancher-agent:v2.3.5 doesn't support arm64.  but doing a docker pull on rancher/rancher-agent:v2.3.5-arm64 succeeds on raspbery pi 4:
pi@raspberrypi:~ $ sudo docker pull rancher/rancher-agent:v2.3.5-linux-arm64
v2.3.5-linux-arm64: Pulling from rancher/rancher-agent
Digest: sha256:8809281719c6cca7a11c1d61dea44475e7388f6a36e2b9b3fb84275b98a8d39e
Status: Image is up to date for rancher/rancher-agent:v2.3.5-linux-arm64
pi@raspberrypi:~ $ sudo docker pull rancher/rancher-agent:v2.3.5
v2.3.5: Pulling from rancher/rancher-agent
no matching manifest for unknown in the manifest list entries
pi@raspberrypi:~ $
So I downloaded the yaml that was provided by Rancer import.  Added '-linux-arm64' to the end of the images (two statements in the yaml).   And then applied the YAML.   And get further - but still not working.
Here is where it is now failing:
Feb 27 17:10:29 raspberrypi k3s[31210]: I0227 17:10:29.400171   31210 controller.go:107] OpenAPI AggregationController: Processing item v1beta1.metrics.k8s.io
Feb 27 17:10:35 raspberrypi k3s[31210]: E0227 17:10:35.046920   31210 pod_workers.go:191] Error syncing pod fbb3be69-7c04-48fe-b4ea-b8f02d516e7c ("cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"), skipping: failed to "StartContainer" for "agent" with CrashLoopBackOff: "back-off 2m40s restarting failed container=agent pod=cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"
Feb 27 17:10:49 raspberrypi k3s[31210]: E0227 17:10:49.053513   31210 pod_workers.go:191] Error syncing pod fbb3be69-7c04-48fe-b4ea-b8f02d516e7c ("cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"), skipping: failed to "StartContainer" for "agent" with CrashLoopBackOff: "back-off 2m40s restarting failed container=agent pod=cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"
Feb 27 17:11:02 raspberrypi k3s[31210]: E0227 17:11:02.044207   31210 pod_workers.go:191] Error syncing pod fbb3be69-7c04-48fe-b4ea-b8f02d516e7c ("cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"), skipping: failed to "StartContainer" for "agent" with CrashLoopBackOff: "back-off 2m40s restarting failed container=agent pod=cattle-node-agent-jjjl4_cattle-system(fbb3be69-7c04-48fe-b4ea-b8f02d516e7c)"

So a bit more investigation reveals that rancher-agent:v2.3.5 doesn't support arm64. but doing a docker pull on rancher/rancher-agent:v2.3.5-arm64 succeeds on raspbery pi 4:

Yes, this has already been established by my earlier posts above.

Same situation.
I also tried to install the 2.4.0-rc1 but nothing changed.

+1

最后咋解决的啊

最后咋解决的啊
应该无解

+1

+1
Any news whether there will be a fix?

+1 here too !!! Just got 3 x RPi 4 and while I got it working with Ubuntu 64 bit with Rancher (as Arm64 is supported) there are lots of docker images out there that don't support Arm64 and work with Arm32  / Armhf

+.5
I am experiencing the same issue - but on a Raspberry Pi 2B

Same issue, tried various 2.3.x version in the past and upgraded to 2.4.3 today with no luck. k3s cluster is a mix of pi 2/3's.
9s          Warning   Failed              pod/cattle-node-agent-r6t8w                  Failed to pull image "rancher/rancher-agent:v2.4.3": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/rancher/rancher-agent:v2.4.3": failed to unpack image on snapshotter overlayfs: no match for platform in manifest sha256:4eb38352d8221640dd13257974028758579211853ac0a10aa9ac90223a30f43d: not found

I've tried K3S and docker with the same results. the system wants to pull rancher-agent:2.4.3. if I force it to use master-head-linux-arm64 by modifying the docker command it does download and attempts to run but fails with the error
standard_init_linux.go:211: exec user process caused "exec format error"
trying a couple other versions results in the same issue.

+1

Found this blog:

https://qiita.com/yamaneko_usg3/items/56a55d7e461c8bf0c67a

Since I already have a rancher server, I have to import an rpi3 k3s cluster.
With above instruction, I can deploy the rancher-agent:v2.5.3-linux-arm64 successfully on my raspberry pi 3/B+ k3s cluster to import it into my Rancher server.
More detailed instructions: >>
1. Prepare (Optional)

Get k3os-rootfs-arm64.tar.gz from https://github.com/rancher/k3os.
Create your own config.yaml for server/master or agents/workers.

for server

...
hostname: pi1.local.net
k3os:
  k3s_args:
  - server
...

for workers

...
hostname: pi2.local.net
k3os:
  server_url: https://pi1.local.net:6443
  token: $NODE_TOKEN_FROM_SERVER
  k3s_args:
  - agent
...

2. K3s server on a raspberry pi 3 b+

Create the bootable SD card  with 2020-02-13-raspbian-buster-lite.img.
(Optional) touch /boot/ssh
Add a "arm_64bit=1" line to /boot/config.txt
Append the "cgroup_memory=1 cgroup_enable=memory" options to /boot/cmdline.txt
Boot up the rpi3 b+.
Login (or SSH) into the pi.
Get k3os-rootfs-arm64.tar.gz
sudo tar xzvf  k3os-rootfs-arm64.tar.gz --strip-components=1 -C /
Create or cp /k3os/system/config.yaml for server
sudo rpi-update. (check if this can be skipped.)
Reboot
Login (or SSH) into the pi1.local.net server.
If everything goes fine, you could see followings.

Welcome to k3OS!

Refer to https://github.com/rancher/k3os for README and issues

By default mode of k3OS is to run a single node cluster. Use "kubectl"
to access it.  The node token in /var/lib/rancher/k3s/server/node-token
can be used to join agents to this server.

3. Import k3s cluster into your Rancher server.

Browse to your Rancher server's web UI.
Select Add Cluser > Import an existing cluster then check the notifications.
Login (or SSH) into the pi1.local.net server.
curl  --insecure -sfL https://your.rancher.server/v3/import/XXXXX.yaml  > rancher.yaml
vi rancher.yaml

:%s,image: rancher/rancher-agent:v2.3.5,image: rancher/rancher-agent:v2.3.5-linux-arm64

kubectl apply -f rancher.yaml
Check this k3s cloud is imported successfully.

4. Add some workers

Login (or SSH) into the pi1.local.net server.
cat /var/lib/rancher/k3s/server/node-token
Do the same things 2.1~2.11 except 2.9.
Edit config.yaml for k3os.token with above node-token contents.
Reboot
After a few minutes, you can see your worker node at the rancher server.

That's all folks.
Good luck!

3\. Add a "arm_64bit=1" line to /boot/config.txt

Does this line convert the OS dynamically into 64-bit or what?
Else, how is it possible to run a 64-bit app on a 32-bit OS?

k3os and rpi-update might be the magic.
But please check if rpi-update is a must.

Same problem with raspberry pi 4

same problem

As listed the issue is you are not running the 64bit version of Raspbian. I'm running three PI4's with SSD only.
Steps I followed to get my cluster up:
Adjust Raspbian to run 64bit, adding this line informs rpi-update to update with the 64bit version.
Update: /boot/config.txt with
arm_64bit=1
Run
rpi-update
to update the pi to 64bit
To confirm run
uname -a
(Source: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=250730)
1 - Setup Master
run the following to install K3S:
curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644
Validate that it's up:
sudo kubectl get nodes
sudo systemctl status k3s.service
Make sure the cluster is up and happy before adding the workers.
2 - Setup the Worker
On the master export the token from:
sudo cat /var/lib/rancher/k3s/server/node-token
On the worker:
export K3S_TOKEN="paste above token here"
export K3S_URL=https://:6443
curl -sfL https://get.k3s.io | sh -
Then create the cluster in Rancher, Import custom.
Run the two commands to add the user and add the master:
kubectl create clusterrolebinding cluster-admin-binding --clusterrole cluster-admin --user pi
sudo kubectl apply -f https:///v3/import/2r3131231231231231231231231313123.yaml

Ok this worked,
I also changed the deployment file to the image name **rancher/rancher-agent:v2.5.1-linux-arm64 ** in this step
curl --insecure -sfL https://
/v3/import/dlzwxczz5vcrx4xk5kq4t97s8l2bm6zwf2cptx946txjjsbtxhv4kk.yaml | kubectl apply -f -

Something is now changing the deployment to set the image name back to rancher/rancher-agent:v2.5.1

1+

To append onto what @SolaceZA  and @felts94  suggested, I was able to use my existing Rancher 2.4.5 to adopt a current 1.16 K3S cluster.
I was able to convert existing pi's to arm64 using @SolaceZA  suggested steps. This process seems to have worked nicely without damaging anything I was paying attention to.
to @felts94 point I did find(though I am not sure if this is a sequencing problem or an actual issue) that I needed to edit BOTH the deployment/cattle-cluster-agent and daemonset/cattle-node-agent and explicitly force the use of *-linux-arm64 images. From here the cluster seems okay and I can confirm that I have been able to add nodes repeatedly using this method.

+1
pi@raspberrypi:~ $ sudo docker run --platform linux/arm/v7 -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher
Unable to find image 'rancher/rancher:latest' locally
latest: Pulling from rancher/rancher
Digest: sha256:10e938f788e725d1d2ed7bc909bae8c7a83b756c520fb2596bf559e44e13587d
Status: Image is up to date for rancher/rancher:latest
WARNING: image with reference rancher/rancher was found but does not match the specified platform: wanted linux/arm/v7, actual: linux/amd64
docker: Error response from daemon: image with reference rancher/rancher was found but does not match the specified platform: wanted linux/arm/v7, actual: linux/amd64.
See 'docker run --help'.

Please find a solution. We love rancher!

I'm also seeing this issue on a RPi 4 with the latest Rasperry Pi OS with bullseye.  Pointing to the image tage v2.6.2-linux-arm64 allows me to download the image, however, it will not run on k3s due to an incompatible architecture:
standard_init_linux.go:228: exec user process caused: exec format error

Reopening this issue because we recently had someone in the Rancher Users Slack asking for help importing an ARM cluster as well.

I asked about it internally. They said that Rancher is not expected to work with ARM32 and there is no plan to support it.
For ARM64, it's experimental and not officially supported, although it is expected to work. Two of my colleagues said they got Rancher to run on ARM64 and manage clusters that were also running it. They said that when you import an ARM64 cluster into Rancher, the agent image is pulled based on the architecture of the node, so there shouldn’t be any special configuration needed for it to work.
There's a bit more information about Rancher ARM64 here, for example the requirement that for a custom cluster, the CNI plugin must be Flannel. https://rancher.com/docs/rancher/v2.6/en/installation/resources/advanced/arm64-platform/ But there is no plan for ARM64 to be officially supported.

Doesn't graviton use ARM64? It seems odd to not support ARM nodes in EC2


wether the pre-training dataset K710 is available ?

just as paper presented, the pre-training on K710, i.e., the combination of K400, 600, 700,  results shorter training cost on downstreaming task, I wonder whether this annotation file is available?

Hi! Please Check DATASET.md. The annotation file can found here.


Switch to covariant in DDC

This is the DDC issue for #27486.

This should be done now.  Are there language tests for this?

Removing blocked; analyzer support in https://github.com/dart-lang/sdk/issues/28167 was completed.
@kevmoo who should this one be assigned to?

@mit – @devoncarew should run w/ that...

This looks DDC specific; assigning to @vsmenon to triage -

Looks like nothing further is needed beyond updating tests.  Tests work with @checked replaced with covariant:
https://codereview.chromium.org/2653493004


Spendable/Receivable are shown as Nan if undefined

On channel details page the value is shown as NaN; if the spendable amount/receivable amount is undefined.

Closing with PR #9


Introduce KMT specific prepare task

What does this PR do?
Introduce KMT specific prepare task for building test packages for both system-probe and security-agent.

Motivation

Additional Notes
This PR https://github.com/DataDog/ami-builder/pull/174 in ami-builder changes the directories where test packages are placed within the microvms.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/trigger-ci -v RUN_KMT_TESTS=on

/gitlab resync-code

/trigger-ci -v RUN_KMT_TESTS=on

/merge


[Test CI] Automatically comment on PRs that add any types

We want the libdefs in this repository to remain high quality. As such, we want to minimize any types as much as is reasonably possible. In some cases an any type of some kind (including things like Object, Function, etc) is unavoidable -- so we can't simply ban them altogether.
To minimize the number of unnecessary any types, it would be good to have Travis check for these and comment on any pull requests that add them -- pointing out that they should be avoided if at all possible.
Perhaps something like a --strict flag could be added to the validate-defs command that emits warnings on these kinds of things?

@marudor did a great job adding some linting in here... are we done with this or is something still missing?

Still open.
We have // $ExpectError checks, but not any checks. I'm planning on doing them.

I created a lint rule for any, Function and Object for a private project. I added it to a fork of eslint-plugin-flow-typed yesterday when I saw this. I can send a PR if you want? Not sure about the name though.

@relekang send a PR for sure

I did, and now I realised nobody is watching the repo. So leaving a note here :)
Also, would it be interesting to add fastlint or lint-filter to the travis build to be able to indicate that new PR are breaking this?

I found [eslint-plugin-flowtype/no-weak-types]https://github.com/gajus/eslint-plugin-flowtype#eslint-plugin-flowtype-rules-no-weak-types and created a PR to this repo with config for that and will close my PR against eslint-plugin-flow-typed.

#335 doesn't quite solve this issue since the errors aren't surfaced in the PR in some way, but it's definitely a big step in the right direction!

@jeffmo Looks like Hound CI has support for eslint and does inline comments of lint warnings. Might be an option?


Moved tokens from process memory to file with async access

This is a great idea! Can this be an option for the users to configure. I can see a need for both cases, the in-memory storage (more secure) and on disk storage for your use case.

Good point. I will make these changes next week.

This is a great idea! Can this be an option for the users to configure. I can see a need for both cases, the in-memory storage (more secure) and on disk storage for your use case.

Good point. I will make these changes next week.

@cccs-is Just made the changes. Let me know if you have any other comments/concerns.

Thanks!

Feel free to merge in main (since I cannot)

Ah, I forgot about that.


Add a hovering effect

I want to add a hovering effect to the 'fill them' heading. Please provide me with the opportunity to do so @prakhartiwari0

@ritikaaaa177 can you provide a descriptive explanation of what changes you want to make?

And, also are you making this contribution under GSSOC23?

And, also are you making this contribution under GSSOC23?

Yes, Yes I am contributing it under GSSOC 23


New XML element detected

New XML element detected: cm:compliance-reference. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>New XML element detected: cm:compliance-see-also. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>New XML element detected: cm:compliance-solution. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>$ risu --version
risu: 1.7.3
Ruby Version: 1.9.3
Rubygems Version: 2.4.3

Thanks I will get these added.
-Jacob
--
Jacob Hammack
<EMAIL_ADDRESS>(210) 355-0036
http://www.hammackj.com

On Jan 19, 2015, at 7:08 AM, Michael Boman<EMAIL_ADDRESS>wrote:
New XML element detected: cm:compliance-reference. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>New XML element detected: cm:compliance-see-also. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>New XML element detected: cm:compliance-solution. Please report this at http://github.com/arxopia/risu/issues/new or via email to<EMAIL_ADDRESS>

Got the following error when using mysql2 backend (hostnames has been replaced by X, but lenght is unmodified):
[!] Mysql2::Error: Data too long for column 'cm_compliance_info' at row 1: UPDATE items SET plugin_name = 'VMware vCenter/vSphere Compliance Checks', cm_compliance_info = 'By ensuring that all systems use the same relative time source (including the relevant localization offset), and that the relative time source can be correlated to an agreed-upon time standard (such as Coordinated Universal Time...UTC), you can make it simpler to track and correlate an intruder...s actions when reviewing the relevant log files.  Incorrect time settings can make it difficult to inspect and correlate log files to detect attacks, and can make auditing inaccurate. In addition incorrect time settings can introduce login issues with SSO as all SSO component rely on coordinated time.\nNOTE: Update NTP_SERVER to the appropriate value for the local environment.\n', cm_compliance_actual_value = '\n\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\nXXXXXXXXXXXXXXXX - NTP Server : XXXXXXXXXXXX\n\n', cm_compliance_check_id = '1f2c54b9675f65282985bcb41f08ebeb', cm_compliance_policy_value = '\nregex: NTP Server : \nexpect: NTP Server : XXXXXXXXXXXX$\n', cm_compliance_audit_file = 'VMware_vSphere_5.x_Hardening_Guide.audit', cm_compliance_check_name = 'vCenter : config-ntp', cm_compliance_result = 'PASSED' WHERE items.id = 11
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:286:in query' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:286:in block in execute'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract_adapter.rb:425:in block in log' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.0.0/lib/active_support/notifications/instrumenter.rb:20:in instrument'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract_adapter.rb:420:in log' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:286:in execute'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/mysql2_adapter.rb:220:in execute' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/mysql2_adapter.rb:247:in exec_delete'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/database_statements.rb:102:in update' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/query_cache.rb:14:in update'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/persistence.rb:489:in update_record' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/locking/optimistic.rb:70:in update_record'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/attribute_methods/dirty.rb:74:in update_record' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/callbacks.rb:307:in block in update_record'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.0.0/lib/active_support/callbacks.rb:373:in _run__195586141842112430__update__callbacks' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.0.0/lib/active_support/callbacks.rb:80:in run_callbacks'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/callbacks.rb:307:in update_record' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/timestamp.rb:70:in update_record'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/persistence.rb:466:in create_or_update' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/callbacks.rb:299:in block in create_or_update'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.0.0/lib/active_support/callbacks.rb:403:in _run__195586141842112430__save__callbacks' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.0.0/lib/active_support/callbacks.rb:80:in run_callbacks'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/callbacks.rb:299:in create_or_update' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/persistence.rb:106:in save'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/validations.rb:51:in save' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/attribute_methods/dirty.rb:32:in save'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:270:in block (2 levels) in save' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:326:in block in with_transaction_returning_status'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/database_statements.rb:200:in transaction' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:209:in transaction'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:323:in with_transaction_returning_status' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:270:in block in save'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:281:in rollback_active_record_state!' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:269:in save'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/persistence.rb:230:in block in update' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:326:in block in with_transaction_returning_status'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/database_statements.rb:202:in block in transaction' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/database_statements.rb:210:in within_new_transaction'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/database_statements.rb:202:in transaction' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:209:in transaction'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/transactions.rb:323:in with_transaction_returning_status' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.0.0/lib/active_record/persistence.rb:228:in update'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/parsers/nessus/nessus_sax_listener.rb:366:in end_report_item' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/parsers/nessus/nessus_sax_listener.rb:199:in on_end_element'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/parsers/nessus/nessus_document.rb:72:in parse' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/parsers/nessus/nessus_document.rb:72:in parse'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/cli/application.rb:465:in parse_file' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/cli/application.rb:416:in block in run'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/cli/application.rb:414:in each' /home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/lib/risu/cli/application.rb:414:in run'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/gems/risu-1.7.3/bin/risu:37:in <top (required)>' /home/micbom/.rvm/gems/ruby-1.9.3-p551/bin/risu:23:in load'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/bin/risu:23:in <main>' /home/micbom/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in eval'
/home/micbom/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `'

I will get this fixed and push as soon as I can. Thanks

Almost have this complete, just adding unit tests now. Sorry for the delay.


38 slider section

relates #38

Looks great, we'll need to change the paragraph beside the Download button cause it's a repeat but we'll be doing that when we have finalised the content. Once we have the navbar added, that page is pretty much done.

great


Setup Travis

@imajes or @michaeldv only you guys have power to do that.
Please follow the 2 first steps of this guide.
The .travis.yml is already in place.

@michaeldv any feedback on that? :grimacing:

@maurogeorge @imajes I've set it up, please check https://travis-ci.org/michaeldv/awesome_print

@michaeldv thanks man!
Closing since was fixed.


⚠ Bofrost.be has degraded performance

In 5d916cc, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 940 ms

Resolved: Bofrost.be performance has improved in a5e5842.


bug: Create app using ionic 1

Type: bug
Ionic Version: 1.x
Platform: all
How can I create app using ionic v1.
I have tried using ionic start firstProject blank --v1. But it always create with latest version of ionic.
Currently I have Angular app which is in Angular 1 and i want to replicate same with ionic 1.
How can I create the app with ionic version 1?
Thanks,

Hello @hiren443, would you mind running ionic --version and posting the output here, please?

This issue was moved to driftyco/ionic-cli#2286


Stop! Hammer time.

This PR adds a hammertime controller.
Here is a short video explaining what it does:

It uses the nodeobservatory to monitor the nodes of all klusters.
If for a kluster no node has posted an update within 20 seconds it instructs the cluster to have a little hammer time.
In hammer time the controller manager is shutdown to avoid having the service controller remove all nodes from loadbalancer.
We do this to keep the payload running and accessible should a network problem between apiserver and kubelets prevent nodes from posting their status. This is especially usefully for our cross region setups.

🤣 Approved! So few pixels in the 80s...

Y No merged??

@BugRoger Still isn't approved yet...

reopen. This is still valid.

Approved x2

I added a single metric to track when a cluster has a little hammer time. Merging this now

Nice. Finally!


Fix reading basedir from config and cli flag

Fixes #64

Merged here. I rebased your commit on to dev so we could properly release/tag.
https://github.com/vattle/sqlboiler/commit/d2eccc98adfeb23868f21d677963e7a2d3e095ae
Thank you for your contribution :)


fix: masonry scroll handler should rely on event.currentTarget issue#1414

https://github.com/bvaughn/react-virtualized/issues/1414
The scroll handler should rely only on the scrolltop of event.currentTarget as any of the ancestor elements' will propagate up to the container element. Relying on event.target seems incorrect.
Added a test case which would fail if reverted to the previous code.
Also, updated the function simulateScroll. As passing currentTarget to Simulate is not supported ( https://github.com/facebook/react/issues/4950 ), changed the simulateScroll function to set the scrollTop on the desired element.

Codecov Report

Merging #1420 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1420   +/-   ##
=======================================
  Coverage   90.35%   90.35%
=======================================
  Files          59       59
  Lines        1742     1742
=======================================
  Hits         1574     1574
  Misses        168      168

Impacted Files
Coverage Δ

source/Masonry/Masonry.js
95.45% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fix syntax highlight

I apply style to gollum.css.
Fix #190.

+1

Fixed by #237 .
I close this pull request.


Table name is not following eloquent naming conventions

On example when I want to create a table named "bank_accounts" the Laravel model is expected to be named "BankAccount.php"
Declaration of $table field would not be required

Hi, this is a nice package but I think that the developers have stopped working on it. Maybe you can try this package: https://github.com/Muhammadinaam/speed-admin. It supports Laravel 8+.


Build instructions don't work

focus  master $ nix-shell

[nix-shell:~/editors/focus]$ zig build run -Drelease-safe=true
/home/omer/editors/focus/lib/focus/imp_repl.zig:11:21: error: unable to load '/home/omer/editors/focus/imp/lib/imp.zig': FileNotFound
const imp = @import("../../imp/lib/imp.zig");
                    ^
focus-local...The following command exited with error code 1:
/nix/store/k8a77g27gbaslzzy1dyg876kjp5a4320-zig/bin/zig build-exe /home/omer/editors/focus/bin/focus.zig -lc -lGL -lSDL2 -lSDL2_ttf -lSDL2 -lpcre2-8 -OReleaseSafe --cache-dir /home/omer/editors/focus/zig-cache --global-cache-dir /home/omer/.cache/zig --name focus-local -I /nix/store/s8644w8zd853agllpykf824wqhgd7gmy-libglvnd-1.3.2-dev/include -I /nix/store/sk8sxkdy4yjanq04wgc97a5ydn6czrrv-SDL2-2.0.14-dev/include/SDL2 -I /nix/store/sk8sxkdy4yjanq04wgc97a5ydn6czrrv-SDL2-2.0.14-dev/include/SDL2 -I /nix/store/s1dh28fpvxw2wf8zc4h93lmskcw7l70w-SDL2_ttf-2.0.15/include/SDL2 -I /nix/store/1i5n540vmik93mm9ak56p06d6v9qh00i-libGL-1.3.2-dev/include -I /nix/store/9f78zqb1nmarxq19smnn8bz6z54jn8rr-xorgproto-2021.3/include -I /nix/store/qplprjvdgh5dl2k6z7fv714yql3layhj-libX11-1.7.0-dev/include -I /nix/store/sk8sxkdy4yjanq04wgc97a5ydn6czrrv-SDL2-2.0.14-dev/include -I /nix/store/s1dh28fpvxw2wf8zc4h93lmskcw7l70w-SDL2_ttf-2.0.15/include -I /nix/store/fybws5k08alqwynxqhld99dldis5ln78-pcre2-10.36-dev/include -L /nix/store/pby9yzkvp4sdxnn182nj3cww2gshnmp1-libglvnd-1.3.2/lib -L /nix/store/bp5rqzywc936gyfdq9vqwrr77ag2nsy2-SDL2-2.0.14/lib -L /nix/store/bp5rqzywc936gyfdq9vqwrr77ag2nsy2-SDL2-2.0.14/lib -L /nix/store/s1dh28fpvxw2wf8zc4h93lmskcw7l70w-SDL2_ttf-2.0.15/lib -D _REENTRANT -D _REENTRANT --main-pkg-path /home/omer/editors/focus --enable-cache
error: the following build command failed with exit code 1:
/home/omer/editors/focus/zig-cache/o/ba8a08373158cac6b54e3069dcbe1e24/build /nix/store/k8a77g27gbaslzzy1dyg876kjp5a4320-zig/bin/zig /home/omer/editors/focus /home/omer/editors/focus/zig-cache /home/omer/.cache/zig run -Drelease-safe=true

Oops. Do git clone https://github.com/jamii/imp ../imp. I added a note to the readme.

I'm now getting this error:
$ ./zig-cache/focus-local
./zig-cache/focus-local: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/bp5rqzywc936gyfdq9vqwrr77ag2nsy2-SDL2-2.0.14/lib/libSDL2-2.0.so.0)
./zig-cache/focus-local: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /nix/store/bp5rqzywc936gyfdq9vqwrr77ag2nsy2-SDL2-2.0.14/lib/libSDL2-2.0.so.0)
./zig-cache/focus-local: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /nix/store/v8q6nxyppy1myi3rxni2080bv8s9jxiy-glibc-2.32-40/lib/librt.so.1)
./zig-cache/focus-local: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /nix/store/cz6fki95gy7zfhpp0vx7pcd0963f8716-libpng-apng-1.6.37/lib/libpng16.so.16)

Same error with and without nix-shell.


API created with services cannot view in devportal.

Description:
Create API using service
Go to dev portal.
Click API overview page
Endpoint URL will be null and error throws in UI.

https://github.com/wso2/product-apim/issues/9836

This is not reproducible in the the latest built pack


[5.4] Fixed Sparkpost error on 5.4

See issue #17277

Wrong branch. Use 5.4 branch if you want 5.4.

@taylorotwell Whoooops you are right, sorry!


add support for scrollbars of RecyclerView

Thank you very much for pulling request.
Could you  pull request to the dev branch rather than master branch?
Thank you!

Sure, I'll make a new PR and close this one.


Add VEX V5 controller

Thank you ! Looking at a photo of the device it seems to match Nintendo iconography for face buttons. Can you confirm your mapping is based on position (eg. south face button is SDL mapping key "a") per https://github.com/mdqinc/SDL_GameControllerDB?tab=readme-ov-file#mapping-guide ?

Sorry, I don't know too much about controller mapping so I'm not too sure what you mean. I did not map it using the letters on the buttons, I just pressed the buttons on my controller that corresponded to the diagram on https://generalarcade.com/gamepadtool/.


Task 1 completion

have you completed the task 1?

Ya I think so. What about your's @reshnashrestha ?

I have done it to my best but still not sure with peak frequency one.
Have you figured it out?

Hey guys you can check out our (group1) work under task1 folder in the main branch.


QD support for ZC Bcast API

Fixed by this(https://github.com/UIUC-PPL/charm/pull/2353/commits/8cc566a6660e3be1060b003284e830c2f83f6a70) commit in this(https://github.com/UIUC-PPL/charm/pull/2353) PR.

#2353 has been merged


[WIP] Import transitive constraints from glide

When calculating constraints, we want to include any constraints specified by our dependencies, including if those constraints are specified in the dependency using another tool (e.g. glide). This is crucial to facilitate piecewise migration to dep. Full use case documented in #821.
Status:

[x] Add test cases for dep init
[ ] Get dep init working
[ ] Add test cases for dep ensure
[ ] Get dep ensure working
[ ] Check that #917 is fixed

fixes #821
fixes #917

Don't worry about #917, that should be addressed in a separate PR.

I suggest that we split this PR into more manageable chunks:

Have dep call the importers during DeriveManifestAndLock (i.e. use external config during solve).
Add tests (and possible warnings/etc) for conflicting "preferred versions" from external config.
Fix for #917.

This will make it easier for less difficult items to get into master, and hopefully shorten the review cycle.
That said, FYI I'm out the rest of this week and will only be checking in periodically.

Getting back to this today. Unfortunately, it's hard to test against my more complex real-world projects because rejection of https://github.com/golang/dep/pull/830 means that with this change, not only can your glide.yaml not use a short hash, none of your dependencies' glide.yaml can use a short hash. Almost all our projects use libraries that break this rule and therefore cause the overall import to fail.
I've started looking into whether short hashes can be supported for import-only; however, it doesn't appear that SourceManager currently provides a way to translate a short hash into a long hash. The options I can see are:

Add a public function (GetRevisionForRevision?) to the SourceManager interface that accepts a short hash and returns a long hash. Then this could be called by the glide importer before InferConstraint.
Have InferConstraint take a flag that tells it whether to accept short hashes or not. This seems ugly but would be expedient.
Implement tool-specific versions of InferConstraint in each importer, so that InferConstraint doesn't need to deal with different revision semantics in different contexts. This seems like a lot of work and hard to make very DRY. Also, I'm not sure if that would then imply there should then be tool-specific SourceManagers as well.

@sdboyer @carolynvs would love your thoughts on how to proceed.

Unfortunately, it's hard to test against my more complex real-world projects because rejection of #830 means that with this change, not only can your glide.yaml not use a short hash, none of your dependencies' glide.yaml can use a short hash.

#830 is not a blocker for this. it was rejected as the proposal requested that we allow the use of shortened SHA1s anywhere. i was, however, explicit that autoconverting from short hashes in glide.yaml (or other systems) would be fine: https://github.com/golang/dep/pull/830#issuecomment-315948109

Have InferConstraint take a flag that tells it whether to accept short hashes or not. This seems ugly but would be expedient.

@carolynvs made a suggestion along these lines the other day in slack, and it seems fine to me. not a hack at all, really. at least, not any more than InferConstraint() already is: it takes a string, and relies on interrogating the source, rather than pure symbolic logic (which is what the rest of the system does), to determine what well-formed constraint the string should corresponds to.

Yup! We have an issue on the backlog (#987) to gracefully handle dealing with short hashes found in external config.

FYI, #1027 was just merged, which handles expanding short revisions into full ones automatically in the importers.
@chriswhelix  Let me know if you are still blocked one this one now that we have that.

@carolynvs thanks, I'd been keeping an eye out for that, I'll pick this up again tomorrow probably.

Current status: "dep init" seems to work well to import an initial config, but "dep ensure -update" won't continue to honor the transitive constraints used during init. The ensure solver will need to start using the import logic currently in rootAnalyzer. Putting that work on hold until @carolynvs finishes https://github.com/golang/dep/pull/1100.

@chriswhelix do you have any update on this pull request? @carolynvs has merged #1100 into master.

@uberbits I missed that that had merged, I'll take another look at this.

@chriswhelix many thanks! The ability to read glide.yaml constraints is critical for our rollout of dep, or any other company with a large existing project base an complex graph. With this change, we can start migrating leaf projects vs migrating entire clusters which include external (open-source) dependencies which are out of our control.

@uberbits next step is making the solver use the importers during ensure. @carolynvs can probably provide some guidance on approach. It's looking like I may not be able to get back to this for a couple weeks, so feel free to pick it up.

@alsamylkin

@chinmayr picking up on behalf of @alsamylkin

@uberbits Please ping me with any questions that come up here. I'm finally back online regularly and have time to help.

Closing this PR because it is being continued in PR #1277.


Using declaration (C# 8) not properly highlighted

Issue Description
Using declaration (C# 8) not properly highlighted
Steps to Reproduce
Write a code with "using declaration".
Expected Behavior
Both words: "using" and type definition should be properly highlighted.
Actual Behavior
The word "using" is not highlighted.

Environment information
VSCode version: 1.56.2
C# Extension: 1.23.12
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   5.0.203
 Commit:    383637d63f
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19043
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\5.0.203\
Host (useful for support):
Version: 5.0.6
Commit:  478b2f8c0e
.NET SDKs installed:
3.1.402 [C:\Program Files\dotnet\sdk]
5.0.203 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

azure-account
ms-vscode
0.9.8

csharp
ms-dotnettools
1.23.12

jsonpath-extract
davidmarek
1.2.3

mssql
ms-mssql
1.10.1

preview-vscode
myh
1.3.0

remote-wsl
ms-vscode-remote
0.56.4

rest-client
humao
0.24.5

vscode-asa
ms-bigdatatools
0.8.3

vscode-azurefunctions
ms-azuretools
1.4.0

vscode-azureresourcegroups
ms-azuretools
0.4.0

vscode-hasher-extended
espresso3389
1.1.1

xml
DotJoshJohnson
2.5.1

Thanks for reporting this issue. It is really an issue with the C# textmate grammar located at https://github.com/dotnet/csharp-tmLanguage not with this extension. You can set "csharp.semanticHighlighting.enabled":true to enable semantic highlighting which will then work correctly.


[Suggestion] useScript

I'm curious if the community would find this change to the call signature of useScript at all useful:
function useScript(src: string, shouldLoad: boolean = true, removeOnUnmount: boolean = false): Status { ... }

shouldLoad could be used for something, like, an environment or privacy flag:
useScript('//some-script.js', isProduction) // or
useScript('//some-script.js', !isTest) // or
useScript('//some-script.js', user.isAnonymous)

removeOnUnmount could be used to remove the created script when the component calling useScript unmounts. Examples could be "one-shot" third party scripts that someone might just want to be present for a specific page of the app. Something like a HubSpot form that serves a specific use case, like Signing Up for an account.
If these sound like good ideas I'm happy to open a PR making the aforementioned changes.

Hi @curtvict,
Yeah, it's a cool idea, I'll be happy to review your PR.
What about a signature like this ?
interface UseScriptOptions {
  shouldLoad?: boolean
  removeOnUnmount?: boolean
}

useScript(src: string, options?: UseScriptOptions): Status { ... }


GitHub Actions error: There was a problem refreshing your current auth token. GitHub Actions is temporarily unavailable

Motivation
I've seen this error on a few PRs recently:

ERROR: (gcloud.compute.ssh) There was a problem refreshing your current auth tokens: ('Unable to retrieve Identity Pool subject token', '{ "message": "GitHub Actions is temporarily unavailable. Please visit https://www.githubstatus.com/ for the status of our services.", "ref": "Ref A: 28C40F7FA2C5465FB3AD96C4A3038863 Ref B: BN3EDGE0617 Ref C: 2023-06-19T19:58:02Z" }')

https://github.com/ZcashFoundation/zebra/actions/runs/5315173045/jobs/9624283153?pr=6934#step:8:83
Specifications

Complex Code or Requirements

Testing
This might be a tricky one to test.
Related Work

Have we seen this again recently? We might want to consider closing if not

Seems like it might have gone away by itself?


Change to allow installation of latest RHSSO patch

add tasks for running cli
add tasks and config for downloading latest patch, and apply via cli

Fixes #14

@guidograzioli LGTM!


feat: add support for stats and status commands

Codecov Report
Attention: Patch coverage is 81.56780% with 87 lines in your changes missing coverage. Please review.

Project coverage is 81.56%. Comparing base (dad5e9a) to head (35818a9).

Files with missing lines
Patch %
Lines

tests/mockServer.ts
60.95%
41 Missing :warning:

src/control.ts
86.95%
21 Missing :warning:

src/error.ts
69.38%
15 Missing :warning:

src/client.ts
93.24%
10 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##              main       #5       +/-   ##
============================================
- Coverage   100.00%   81.56%   -18.44%
============================================
  Files            1        5        +4
  Lines            3      472      +469
  Branches         1       49       +48
============================================
+ Hits             3      385      +382
- Misses           0       87       +87

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


TextBox and PasswordBox Placeholder text and header properties thru attached properties

From: #30

We can use the new functionalities by using the TextBoxRevealStyle (modified to handle placeholder and header) for TextBoxes and PasswordBoxRevealStyle (based on the TextBoxRevealStyle) and applying the attached properties.
HeaderText: Inserts label on top of the data entry control
HeaderSize: Specifies the size of the header text
HeaderForegroundBrush: Specifies the foreground brush of the header
PlaceHolderText: The control's placeholder text (watermark)
PlaceHolderForegroundBrush: Specifies the foreground brush of the placeholder
Sample usage:
<TextBox Name="TextBoxBox1" HorizontalAlignment="Left"  Margin="5"  Width="120" Style="{StaticResource TextBoxRevealStyle}" fw:TextBoxHelper.PlaceHolderText="Username" fw:TextBoxHelper.HeaderText="Enter username"/>
<PasswordBox Name="PasswordBox1" HorizontalAlignment="Left"  Margin="5"  Width="120" Style="{StaticResource PasswordBoxRevealStyle}" fw:TextBoxHelper.PlaceHolderText="Password" fw:TextBoxHelper.HeaderText="Enter password"/>

Thanks!!
I can't took time now. I'll review it in this week end :smile:
Please, wait for a while.
I had a quick glance throw, almost LGTM.

Hi, @fangeles02.
How about it?
If you change the above points, and commit&push to your fangeles02:fluentTextBox branch, I will merge it.
Thanks.

Hi SourceChord,
I'll try to commit and push tomorrow morning, I am on a long vacation that's why I haven't commit into it lately. ??
Thanks.
Get Outlook for Androidhttps://aka.ms/ghei36

From: minami_SC<EMAIL_ADDRESS>Sent: Sunday, November 11, 2018 5:01:25 PM
To: sourcechord/FluentWPF
Cc: Fernan; Mention
Subject: Re: [sourcechord/FluentWPF] TextBox and PasswordBox Placeholder text and header properties thru attached properties (#31)
Hi, @fangeles02https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffangeles02&data=02|01||eed5662f4d9f4b1b02b108d647b442b3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636775236861875525&sdata=8vlppCsSRJ88vdcUnZDJf5m9ijO9wLWynSTHTvpHu7A%3D&reserved=0.
How about it?
If you change the above points, and commit&push to your fangeles02:fluentTextBox branch, I will merge it.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsourcechord%2FFluentWPF%2Fpull%2F31%23issuecomment-437653890&data=02|01||eed5662f4d9f4b1b02b108d647b442b3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636775236861875525&sdata=waCd4tS2kWIzpPvMKJgJHmCCagMOW1rL1CFP1XBaKog%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZJ7CdctJFTS0V8oO5SOANZJaS7n1yBGks5ut-dlgaJpZM4YDYhy&data=02|01||eed5662f4d9f4b1b02b108d647b442b3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636775236861875525&sdata=rotCHjSyEi%2BaUAoxRJHfi8aspf5dk8itLWSCinnfpFM%3D&reserved=0.

Thanks!

I'm looking forward to it :smiley:

Hi,
I have applied changes on latest commit 🙂

Hi,@fangeles02
Thanks for commit 😄
CommandBar & AppBarButton is good idea.
But, it seems to be a work in progress, and your latest commit has too many features.
Pull Request should contains only one thing.(see also)

Style of TextBox/PasswordBox changes.(as I suggested)
Add some controls.

CommandBar
AppBarButton

PointarTracker's change

These changes should not be included same PullRequest.
Could you remove these changes?
Or, May I delete these points after merging?
Thanks.

Oops. Sorry about that, it was not intended to be included on commit, im still new to github and branches 😅
I'll commit again tomorrow.
Thanks 😅

Hi,
I removed the AppBarButton and CommandBar on latest commit. (I think Visual Studio Team Explorer is more stable than github app lol)
Thanks.

Thanks 👍
But, there is still unnessecery changes.

Brushes.xaml
RevealStyles.xaml.cs
Button.xaml & PointerTracker.cs

These change seems that intended to support border color follows change of system theme.
But, currently RevealBrush doesn't follows system theme.
I'm now trying to fix RevealBrush's behavior.

Could you revert above changes?
I like Visual Studio's diff view, too 😄
And, I also use SourceTree.
By the way,we can look around whole changes of the PR by file changes tab.
https://github.com/sourcechord/FluentWPF/pull/31/files
It is very usefull for checking all changes of the pull request.

New Pull Requets
#35


WIP: Add state to Service in core

Description:
NOT FINISHED: I'd like to get some input before I continue adding states to all  relevant services.
The aim is to be able to find all services required to be called to achieve a certain state including state attributes.
This is today useful in scenes and in the future could be useful to be able to put the home in different states automatically based on machine learned state data.

Add state_to_set keyword argument to Service class.
Add state_to_set keyword argument to register method in ServiceRegistry.
Add full_services property in ServiceRegistry to get services including service object.
Add async_get_services in service helper to get all services per domain that can be used to set a certain state. Only add services to return value that have valid attributes if service does not set a state but sets state attibutes.
Update logic in state helper async_reproduce_state.
Add schema and state_to_set to mock_service.
Add test for new core full_services property.
Replace state helper tests with pytest versions.
Add tests for service helper.
Update components service state.
Update alarm_control_panel service state.
Update alert service state. Need to look into required attributes in combination with service state.
Update automation service state.
Update cover service state.
Fix fan service schema and update service state.
Update service state for light.
Not finished: register states with all relevant services.

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Could you explain what is the intended usecase of this?

Yes, sorry, forgot about that.
The aim is to be able to find all services required to be called to achieve a certain state including state attributes.
This is today useful in scenes and in the future could be useful to be able to put the home in different states automatically based on machine learned state data.

Thanks for the feedback @balloob and @pvizeli. I'll try to work more on this towards the end of the week.

Any update on this?

Yeah, I had some comments above to your comments.

I just realized that we're probably approaching this problem from the wrong angle.
What if instead of going down this route, we instead add a new method to each component called async_reproduce_state(hass, state).
That way each component can do exactly the logic it thinks it needs. It will also automatically scale for any component ever. Also we don't have to think about edge cases like multiple services etc, a component can make it as complicated as needed.
For example for the light component:
# New API, so will not contain a sync version.
@asyncio.coroutine
@bind_hass
def async_reproduce_state(hass, state):
    if state.state == STATE_ON:
        yield from async_turn_on(hass, state.entity_id)
    elif state.state == STATE_OFF:
        yield from async_turn_off(hass, state.entity_id)
    else:
       raise UnreproducibleState()

In the helper we can then call
component = getattr(hass.components, state.domain)

if not hasattr(component, 'async_reproduce_state'):
     _LOGGER.error("Unable to reproduce state for %s", state.entity_id)
    return

yield from component.async_reproduce_state(hass, state)

Yes, that was what me and @pvizeli was discussing. See my comment here: https://github.com/home-assistant/home-assistant/pull/8851#discussion_r132495008
I like the idea, but I still don't see how we can solve the services that are registered in the platforms.

States are standardized by the component, platforms just implement them. Platform specific services offer things that are not part of the main component.
I think that it is fine to ignore platform related services when trying to reproduce a state. We should move to use async_reproduce_state because it makes sure that we don't add features to the core that are only there to support 1 piece of functionality. It is also less ambigious (no 2 services returned etc)

What would be the downside of saving the EntityComponent' instances on hass`?
Leaving platforms in the dust would be a breaking change and a limitation that would continue to hurt us more and more as we grow. I don't like that at all.

Why can't reproducestate  be in platform?

It could, but today we can't know from a State instance alone what platform is involved. The entity_id only gives us the domain, ie the component, by default.

EntityComponents are an implementation detail. The only communication among components should be done via state machine, services.
Could you name a platform that would require custom logic today to reproduce a state?

Something that is impossible today and I find missing is to ask an arbitrary entity to update.

There are two platforms that would need that currently, ecobee climate and mysensors switch.

@andrey-git let's move that discussion to a new issue. Feel free to tag me.
@MartinHjelmare could you elaborate a bit more why they need custom logic? From glancing at MySensors it's passing in IR_CODE? That seems like something that is cached when you call the method and thus should probably be passed as configuration to begin with?
I think that having 2 platforms today is a good indication that moving the logic to be in each component is the right choice. By doing so, we're taking the same approach as with restore state: we're not going to push all logic into 1 place but instead have each component take ownership of the functionality as they know their quirks the best.

The mysensors service is used to send different ir codes, in different cases dynamically, to different entities, via automations.
In the longer term I have a plan to move the MySensorsIRSwitch to under the remote component, and deprecate the MySensorsIRSwitch switch platform. So for mysensors it would probably work out ok in the long term, even with this new idea.
As I said, I like your idea in general. What I don't like is that now we're saying that the option for developers to add a service in a platform is a 3rd class option, that we're not really going to support. Why should we even offer that option when our core is clearly not meant to support that as it is now?

Anyway, I'll close this, since we want to do a different approach.
I'll probably not going to work on the new approach immediately, so if someone else wants to take that on, go ahead.

Adding services to platforms allows developers to expose services that do not fit in the abstraction that the component offers. If enough platforms need it, it can be considered to be added to the component. Until it's part of the component, it is indeed not going to be first class supported.


⚠ Bofrost.at has degraded performance

In ef4f084, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1173 ms

Resolved: Bofrost.at performance has improved in 9897fb8 after 18 minutes.


The skiplist is not concurrent but could be used concurrently

The arena in skiplist does not support concurrent operations(https://github.com/tikv/agatedb/pull/116), but it could be used concurrently when allow_concurrent_write is set to true.
Concurrent tests such as bench_read_write_skiplist will crash with [SIGSEGV](signal: 11, SIGSEGV: invalid memory reference) when reducing the arena capacity, for example changing the https://github.com/tikv/agatedb/blob/master/skiplist/benches/bench.rs#L47 size from 512 << 20 to 512.
Supporting the concurrent arena allocator type may be necessary.

It seems like originally you guys wanted to implement thread-local arena for the skiplist but later things went off the rail. Therefore, I suggest in lieu of making the arena concurrent-compatible, we may just utilize the thread_local crate and fulfill the original intention. And maybe I can fix it.


.github: Add Scorecard workflow

👋 This pull request was generated using the installer tool for OpenSSF Scorecard's GitHub Action.
Scorecard helps open source maintainers improve security best practices by running a series of automated checks.
🐛 Report any issues with this tool here.

📣 As part of Cisco Open's efforts to improve open source security posture, we are requiring OpenSSF Scorecard to be installed on all cisco-open member repositories. Manually merging PR due to lack of maintainer response.


Ios bugfix textarea keyboard

修复textarea 弹起落下后 textarea 无法点击

Current coverage is 88.44% (diff: 100%)

Merging #1699 into ios-feature-20161208 will not change coverage

@@           ios-feature-20161208      #1699   diff @@
======================================================
  Files                        41         41
  Lines                      2233       2233
  Methods                     354        354
  Messages                      0          0
  Branches                    500        500
======================================================
  Hits                       1975       1975
  Misses                      258        258
  Partials                      0          0

Powered by Codecov. Last update 557d1fa...b3687b3


Add experimental overload of confirmation() that takes a range.

Wouldn't it be useful to be able to specify a range of expected counts for a confirmation rather than a specific number? For instance, if you expect an event to occur exactly zero or one times:
await confirmation(expectedCount: 0 ... 1) { thingHappened in
  // ...
}

Or maybe you expect that an event will occur at least 10 times, but maybe many more?
await confirmation(expectedCount: 10...) { thingHappened in
  // ...
}

Well... good news, everyone! Here's an experimental overload of confirmation() that allows you to do exactly that!
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Linux

@swift-ci please test

Looks good to me. I think the tests for this would need to be extended if we decided to no longer consider this experimental, but for now this is fine.

DM me any specific tests you have in mind and I can add them when time permits.


Update dependency lodash to 4.17.21 [SECURITY]

This PR contains the following updates:

Package
Type
Update
Change

lodash (source)
dependencies
patch
4.17.19 -> 4.17.21

GitHub Vulnerability Alerts
CVE-2021-23337
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
CVE-2020-28500
All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. Steps to reproduce (provided by reporter Liyuan Chen): var lo = require('lodash'); function build_blank (n) { var ret = "1" for (var i = 0; i < n; i++) { ret += " " } return ret + "1"; } var s = build_blank(50000) var time0 = Date.now(); lo.trim(s) var time_cost0 = Date.now() - time0; console.log("time_cost0: " + time_cost0) var time1 = Date.now(); lo.toNumber(s) var time_cost1 = Date.now() - time1; console.log("time_cost1: " + time_cost1) var time2 = Date.now(); lo.trimEnd(s) var time_cost2 = Date.now() - time2; console.log("time_cost2: " + time_cost2)
CVE-2020-8203
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The function zipObjectDeep allows a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires zipping objects based on user-provided property arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.

Release Notes

lodash/lodash
v4.17.21
Compare Source
v4.17.20
Compare Source

Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!


merge with @types/expo

There is also https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/expo . Would you like to merge  ?

The status is that most of the changes in this repo has been merged into @types/expo. Some things are still missing, though, so the code in here does not compile if you replace expo.d.ts with the one from @types/expo.
I'll keep this issue open until everything has been resolved.

All the type definitions in have been merged into @types/expo, and this code no longer needs custom type definitions, so closing this issue.


Accounts Aging report API

Notion card
https://www.notion.so/saeloun/Backend-for-Accounts-Aging-report-4ad19cb2f9cb4204a356e533757a7f31
Summary
The accounts Aging report should be available to the owner or admin to check which of their clients are taking longer time settle their invoices.
Preview
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Local, RSPec, Postman
Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[ ] I have added automated tests for my code

JSON Response-

{
    "report": {
        "clients": [
            {
                "id": 2,
                "name": "Flipkart",
                "amount_overdue": {
                    "zero_to_thirty_days": 0,
                    "thirty_one_to_sixty_days": 0,
                    "sixty_one_to_ninety_days": 0,
                    "ninety_plus_days": "2000.0",
                    "total": "2000.0"
                }
            }
        ],
        "total_amount_overdue": {
            "zero_to_thirty_days": 0,
            "thirty_one_to_sixty_days": 0,
            "sixty_one_to_ninety_days": 0,
            "ninety_plus_days": "2000.0",
            "grand_total": "2000.0"
        }
    }
}

cc @akhilgkrishnan

Adding search for inclusive dates. Working fine in query.
For eg today is 17th Nov then the result would be with dates -
```
amount_overdue: {
“0-30 days”: , =17 nov - 17 oct
“31-60 days”: , =17 sept- 16 oct(31 day)
“61-90 days”: , =17 aug - 16 sept
”90+ days”: , 17 year back - 16 aug
“total”:
}
<img width="1144" alt="Screenshot 2022-11-17 at 10 36 36 AM" src="https://user-images.githubusercontent.com/5313625/202361721-ef9107a5-0db7-44f9-b5f0-54bde7995c93.png">

@apoorv1316 the cypress tests are failing on this pr, can you please check.

@mohinid Can you please share the postman request screenshot along with all the required params and other info.

@mohinid Can you please share the postman request screenshot along with all the required params and other info.

Sure.

@mohinid please modify all views to remove queries and use view services/presenters

Hi Vipul, did some refactoring. please review now.

@mohinid Can you please share the postman request screenshot along with all the required params and other info.

@apoorv1316 you need to hit this url- http://localhost:3000/internal_api/v1/reports/accounts_aging with a get request.
You should be able to see a list of all clients in the current company(check what the current workspace ID of the user is) and their overdue amount based on the date range, In the end, you should be able to see the total sum of overdue invoices in date range as well as grand total as shown in the response below.

Let me know if you need more info.
Please test for all scenarios by creating invoices in the different date ranges. You can set due_date- some past date and status-overdue from DB.

@mohinid please see name changes on https://github.com/saeloun/miru-web/pull/781/commits/d946bc46885d41302e0b16571a5ee701f9b8cf31
The code should be easier to read
Rebase and merge PR on green

Thanks!

@apoorv1316 please approve and merge today. All changes are implemented.


Error messages are sent to stdout instead of stderr

I've observed that all messages are being directed to stdout.
print("@")
print(1/0)

stdout:
@
divzero_error: division by zero
stack traceback:
	string:2: in function main_

stderr:

The stacktrace (and all errors thus far encountered) do not seem to redirect to stderr.

Thanks, but keep in mind that Berry is designed for embedded systems where there does not exist any equivalent to stdout. Hence we don't make this distinction when printing errors, they follow the same route.
I don't see any value added to add a significant amount of code to support separate printing routes for stdout which embedded systems don't have.
Any specific use for it?


How do i disable Redisson Cache mechanisam

Am using EhCache in my sprint boot Hibernate application.
Now am using Redission library to store the data to Redis.
Am getting Multi-Cache exception when both EhCache and Reddison being used together.
Caused by: javax.cache.CacheException: Multiple CachingProviders have been configured when only a single CachingProvider is expected
Is there a way to avoid Redission Caching and use only EhCache.

the only way is to delete META-INF\services\javax.cache.spi.CachingProvider file in jar


Add > Container Orchestrator Support Does not exist in Visual Studio 2022

This document references Add > Container Orchestrator Support menu item which does not seem to exist in Visual Studio 2022 anymore.

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

ID: 7aee46f8-9db1-33ef-b637-fc8e8881fab9
Version Independent ID: 6c469f9f-9751-669f-3dd4-c4fb49c9ae19
Content: Work with multiple containers using Docker Compose - Visual Studio (Windows)
Content Source: docs/containers/tutorial-multicontainer.md
Product: visual-studio-windows
Technology: vs-container-tools
GitHub Login: @ghogen
Microsoft Alias: ghogen

@groogiam -- Greg, thank you for your feedback.  Please consider these resources:

Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
Check the Visual Studio MSDN Forum.
Stack Overflow
Reddit

@ghogen -- Gordon, please look into this issue.

It appears the menu item is displayed if the project and solution files are not in the same directory.

@groogiam
Hmm, so you're seeing that the menu item only appears if the project and solution files are in separate directories? This could be a product bug.

@groogiam
I tried a Web project, and found that even with the solution and project in the same folder, I see the Add Container Orchestration support menu option. If you can specify the exact repro case, I can see if it is intentional or not.

The menu was not there and then I recreated the project and it was. I thought it was attribute to solution setting but there could have been something else going on. At this point its probably not worth pursuing since I was eventually able to get it to display. We can close the issue if you are unable to reproduce it. Thanks for looking into it.