Feature scaffold and  topbar

Closes #33 and #40
Adds support for scaffold container layout and top with navigation and action icons.
    <scaffold background-color="0xFFF2F2F2">
      <top-app-bar>
      <text color="0xFF000000" font-size="16" font-weight="W600">Home</text>
      <action-icon content-description="back button" >outlined:Create</action-icon>

        <action-icon content-description="back button" >outlined:Notifications</action-icon>
      </top-app-bar>
     </scaffold>

icon uses key value pair to render the material icon icon_type:icon_name
icon type can be default, outlined, filled, sharp, two tone etc
icon name is the name of the icon.
Scaffold link: https://developer.android.com/jetpack/compose/layouts/material#scaffold
App bar link: https://developer.android.com/jetpack/compose/layouts/material#app-bars

Out of curiosity, the citd template example at the top has backgorundColor and content-description. Is there a reason why one is a camelCasing and the other is hyphenated?

@bcardarella  fixed the template, its hiphenated

yes @bcardarella  it was a typo it's background-color for all compose views.


Break button greyed out

https://i.imgur.com/GjnMILV.png

Sorry, didnt realize this method was for digital games only


fix: broken welcome check

Let me know if you find anything else

I belive the check was added later and probably not tested that well

I just went through all the equalites in our code and it seems that was the only case


Add support for Result<'a, 'b> encode/decode.

Looks good. Sorry for the delay in reviewing this. I'll get this merged in.


Quickstart Video Appears Several Times Daily

From ATCC workshop, multiple users are stating that the QuickStart video that appears when you first start using PATRIC is appearing several times a day on their Windows machines (it looks like windows 7) running Chrome, it may happen on other browsers as well.

This will need some debugging on a windows machine to see what is happening.  We can remove the autoplay altogether if desired.  The QuickStart video remembers it has already been played by setting a value on browser local storage.  So if it is playing more than once, it is either failing to set that value (perhaps due to security somewhere) or it is getting cleared out.

Check the browser configuration whether it has "clear cache/history when closing" configured.
see https://k12parentportal.force.com/k12help/s/article/Set-Browser-to-Clear-Cache-When-Closing
for setup.

sorry, wrong click.

I’m not too concerned if this happens after clearing cache, though  people can avoid it by not clearing the local storage when they clear cache as you pointed out.  I assumed, perhaps incorrectly, that this error is happening without clearing cache.

On Jul 27, 2018, at 1:41 PM, hyoo<EMAIL_ADDRESS>wrote:
Check the browser configuration whether it has "clear cache/history when closing" configured.
see https://k12parentportal.force.com/k12help/s/article/Set-Browser-to-Clear-Cache-When-Closing https://k12parentportal.force.com/k12help/s/article/Set-Browser-to-Clear-Cache-When-Closing
for setup.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/2048#issuecomment-408489713, or mute the thread https://github.com/notifications/unsubscribe-auth/AALobms-gzve_0vIvRPAVr1qcoRmrDnUks5uK1DUgaJpZM4VjikA.

Is this still an issue? I don't experience it in day to day things but if I load incognito or with cleared cached I do, which is to be expected.

I haven't seen it lately.

I'm going to assume browser updates have caused it to behave the way we intended or something similar. Closing.


Write initial sklearn algorithm

important to think about modularity of the code

The output:
Is a linear model (will need mathjax) and a graph, see #36.


when nextWorkInProgressHook is null but nextCurrentHook not in updateWorkInProgressHook?

when nextWorkInProgressHook is null but nextCurrentHook not in updateWorkInProgressHook?
https://github.com/wenzi0github/react/blob/8af5b16ac8836f7950510296f276a84268e3374e/packages/react-reconciler/src/ReactFiberHooks.old.js#L721

ok, I got it.
Before updateWorkInProgressHook(), it will change workInProgress.memoizedState to null, and change currentlyRenderingFiber too. That means nextWorkInProgressHook always is null when rerendered by useState().
So, I have the second question, what time nextWorkInProgressHook will be not null.


Add old endpoint docs back in

I removed the old docs when we added the new endpoint. However we should still have documentation for the old endpoint as some customers still use it

🚀 Deployed on https://63f65c0db6005a00530e59f8--cozy-fox-0defec.netlify.app


Link for 'https://aka.ms/bfcomposerhandoffqnamaker' goes nowhere

Describe the bug
When creating a QnA Maker resource, I can select "Handoff to admin".

When I do that, I get this screen:

The URL https://aka.ms/bfcomposerhandoffqnamaker goes nowhere.
Version
Version:  1.4.0-nightly.236875.b9e46c2
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

#6258 has not been completed.  Once that is completed then the documentation link will be updated.  We are also awaiting #7107 to be completed to ensure that we can properly document.


Add substack blog post on ChatGPT profiling experiments to NOS blog.

Should match https://scottloftin.substack.com/p/lets-build-an-ml-sre-bot-with-nos
Checks

[ ] make lint: I've run make lint to lint the changes in this PR.
[ ] make test: I've made sure the tests (make test-cpu or make test) are passing.
Additional tests:

[ ] Benchmark tests (when contributing new models)
[ ] GPU/HW tests

Can we merge this at a later date?

Might want to go ahead and reopen this and merge for a weekly post.

Move to docs/tutorials?

yea which would you prefer? I think this is more of a generic blog post than a tutorial.


Fix scroll event listener to new standard

I messed up my fork for PR #170, so I created a new fork and created a new PR.
@Thomaash I see what you meant, I have changed my code accordingly, it should be much cleaner now. :+1:

Tested on Fedora Linux 29
Chrome Version 78.0.3904.70
Firefox Version 69.0.1 (64-bit)

Okay, so I'm adding Windows 10 (64 bit) tests:

[x] Google Chrome 78.0.3904.87,
[x] Opera 64.0.3417.83,
[x] Vivaldi 2.9.1705.38,
[x] Firefox 70.0.1,
[x] Microsoft Edge 44.18362.449.0,
[x] Internet Explorer 11.418.18362.0.


Stage(Prod) already exists in stack

I am attempting to create a custom domain name and api gateway using SAM.
I have a template which attempts to;

create a 'AWS::ApiGateway::DomainName' resource
create an 'AWS::Serverless::Api'
create a AWS::ApiGateway::BasePathMapping

I have had numerous problems with this deploying. From 'Invalid Stage' to 'Stage already exists' I now have a 'Stage already exists in stack' error when trying to deploy.
Here is my shortened template file;
  DomainName:
    Type: AWS::ApiGateway::DomainName
    Properties:
      DomainName:
        Fn::Sub:
        - ${domain}.${EnvName}.io
        - domain:
            Fn::If:
            - IsMasterBranch
            - 'oms'
            - Ref: AWS::StackName
      RegionalCertificateArn: !Ref CertificateArn
      EndpointConfiguration:
        Types:
        - 'REGIONAL'

  Api:
    Type: AWS::Serverless::Api
    Properties:
      StageName: Prod
      EndpointConfiguration: REGIONAL
      DefinitionBody:
        swagger: '2.0'
        info:
          version: 'v1'
          title: "myapi"

  Deployment:
    DependsOn: DomainName
    Type: AWS::ApiGateway::Deployment
    Properties:
      RestApiId:
        Ref: Api
      Description: "Hack to stop Stage name breaking on deployment"

  BaseMapping:
    Type: AWS::ApiGateway::BasePathMapping
    DependsOn: Deployment
    Properties:
      BasePath: ''
      DomainName: !Ref DomainName
      RestApiId: !Ref Api
      Stage: Prod

This is driving my crazy. Can anyone help?

I'm pretty sure this is the same as: #191

I think you need to remove the AWS::ApiGateway::Deployment resource; SAM will create one of those for you and that's probably where the Stage already exists error is coming from. In your BasePathMapping resource, you should use Stage: !Ref Api.Stage to reference the stage created by AWS::Serverless::Api.

@keetonian I managed to reproduce this without adding my own deployment resource.

@tkeeber Can you try removing the AWS::ApiGateway::Deployment resource and then changing the AWS::ApiGateway::BasePathMapping resource to be this and see if it works. Key changes are removing the deployment, adding a condition on the API GW stage, and removing the BasePath property since if you specify it, it can't be an empty string according to the CFN docs.
  BaseMapping:
    Type: AWS::ApiGateway::BasePathMapping
    DependsOn: ApiProdStage  # logical id of API GW stage created by SAM
    Properties:
      DomainName: !Ref DomainName
      RestApiId: !Ref Api
      Stage: Prod


Fix warning with pytest >= 2.8

Hello,
This is coming up with pytest ≥ 2.8, not sure how backward compatibility is affected, I just wanted to bring the issue to your attention. (Also, as far as I understand, this is the right fix).

@lopter do you think we need to do a version check here? i.e. use the old way for old version of pytest and the new way for new versions?

This doesn't seem like a proper fix for the general case, i.e. it doesn't the same __multicall__ used to do.
However I wonder if the __multicall__/hookwrapper functionality of pytest is needed at all here - it seems doubles shouldn't care about being executed before/after all other plugins, correct?

@The-Compiler that is correct.  All that we care about is that our methods (verify and teardown) are run after each tests completes.

Actually I take that back we need to run before all other plugins.  We may fail a test if expectations are not met.

@lopter do you think we need to do a version check here? i.e. use the old way for old version of pytest and the new way for new versions?

I actually don't know, I just remember looking at what the upgrade path was supposed to be. I guess, a lazy way of doing it is to release a new major version and be compatible with pytest >= 2.8 moving forward.

I took a stab at resolving this in a backwards compatible way here

This was resolved by #102


support for flask-sqlalchemy >= 3.1.0

Flask-SQLAlchemy v3.1.0 removes current_app.extensions["sqlalchemy"].db attribute.
https://github.com/pallets-eco/flask-sqlalchemy/pull/1113

Just pushed a big update that among other things sets the minimum version of Flask-SQLAlchemy to 3.1. Thanks for looking into this, sorry I didn't get to it sooner.


share semmedb, aeolus, eu_pl_adr, splicer SQL code between R/sqlserver and pentaho/postgresql

Enable sharing of semmedb, aeolus, eu_pl_adr, splicer SQL clean & translate code between R/SQLserver and Pentaho/Postgresql.
Also break up the SQL code that populates the STCM table into multiple SQL files that can be run separately.

Thank you @leeevans  for this work!


Make apriltag positions dynamic

Not sure if we want to go back to xml parsing for this or store it in a normal header file, but we want to be able to easily edit the relative positions of the April tags, so that it's easier to calibrate per field.

Charlie - why are creating issues on a closed project instead of using the current offseason project?

Added into current project; deleted the existing issue.  Added labels.
Previous issue was:
Make Field April Tags Dynamic/Configurable during field calibration


Autocreate Zenodo DOIs and create shared access links

Description

Updated PR Description
Zenodo swagger PR: https://github.com/dockstore/swagger-java-zenodo-client/pull/21
This PR has been updated with the feedback from the story time discussion.
This PR requires the creation of a Dockstore-owned personal access token on Zenodo as well as a Dockstore community on Zenodo. This personal access token is used to automatically create DOIs.
Automatic DOI Creation Behaviour

DOIs are automatically created for valid published tags for Workflow-based entries on refresh, GitHub App release, and on publish. During automatic DOI creation, we skip creating a snapshot.
The DOI is only created the first time it is invoked. If tags are recreated, we do not create a new DOI. This can be an enhancement if we want to go down that route.

I originally didn't do it on publish but after manual testing, the user experience to automatically create DOIs for a new workflows that aren't originally published felt clunky. For example, a user creates a new GitHub app workflow that isn't published so no DOIs are created. They publish it. They must now generate push events for DOIs to be automatically created.

There is no option to opt-out.
A new Doi entity is added so that we can track multiple DOIs from multiple sources (user, GitHub, Dockstore). This means that users can have both user-generated and Dockstore-generated DOIs, along with GitHub DOIs.

I have deprecated the old DOI columns instead of removing them so that there is no down time during the release. There is no trigger to keep the new and old columns in sync. Is it worth it to add a trigger?

Note that we don't allow the deletion of entries that were previously published. Since the auto DOI creation only occurs for published tags, this means that DOIs in our database won't be orphaned.
Tags with only Dockstore-generated DOIs can be deleted since they are not frozen...this can result in an orphaned DOI.

Dockstore Zenodo Community

New DOIs, whether user or Dockstore generated, are added to the Dockstore Zenodo community. We do not add old records to the community retro-actively.

Shared Access Links

Three endpoints are added to manage shared access links that allow users to edit the Dockstore-generated DOIs. The access link returns an ID and a token. When this token is appended to the Zenodo DOI URL, the user is able to edit the record if they are logged into Zenodo. I did not store this token in the database because I feared that we could accidentally expose it. Only the link ID is stored and when requested, we can retrieve the token from Zenodo. This editing feature will likely not be used often.
The link has edit permissions and no expiration date. There is an endpoint to delete the access link.
The access link ID is stored in the concept DOI object because this link is applicable to all versions of the DOI

Hoverfly Tests

Created a few Zenodo tests using Hoverfly. These tests aren't super complex due to the limitations of mocked responses, but it's something :slightly_smiling_face:
Created a new testing profile for tests that use Hoverfly because it needs the localtruststore in CircleCI

Follow-up

Hook up to the UI: https://ucsc-cgl.atlassian.net/browse/SEAB-6462

Draft PR Description
Currently in draft mode to get feedback as I figure out some Hoverfly test weirdness in CircleCI.
Zenodo swagger PR: https://github.com/dockstore/swagger-java-zenodo-client/pull/21
This PR adds a enableAutomaticDoiCreation boolean to Entry that is set to true by default.
When set to true, it automatically creates DOIs using Dockstore's own Zenodo personal access token, specified in the web.yml. The auto-creation occurs during refresh and GitHub App release for valid, published tags and involves snapshotting the version prior to creating the DOI. This boolean can be updated using a new endpoint, allowing users to opt-out in the UI. For GitHub app entries, they will need to specify it in their .dockstore.yml.

Should this feature include hosted entries?

This boolean can be updated using a new endpoint, allowing users to opt-out in the UI. For GitHub app entries, they will need to specify it in their .dockstore.yml.
This PR also adds an endpoint to create a shared access link with edit permissions so entry owners can modify their DOIs if they want. There is an option to set an expiration date, but I set it to never expire. The idea is that in the UI, the entry owner can click a button that creates this shared access link. After the first time, the UI can display this link somewhere so the user can modify their DOI. UI PR will be in follow-up ticket.

Should we allow the user to delete this access link?

This PR also adds DOIs to the Dockstore community, using the community ID specified in the web.yml. This is for all DOIs, whether Dockstore-created or end-user-created.
Some questions and thoughts
There is a potential exception if an end user has already requested a DOI for an entry version and our Dockstore user tries to create a DOI for a different version because our Dockstore user does not have permissions to modify some one else's DOI. Due to this, there is a check to see if the entry has 0 DOIs or if all DOIs are Dockstore-owned to ensure that no exception occurs. I think there's a bigger conversation here about how we want to handle this situation so this PR takes the simplest route for now, i.e., not allowing the mixing of end-user-created and Dockstore-created DOIs. Below are some thoughts about it, but I think we should have a follow-up ticket to decide what to do.

Do we solve this with communities? Using a one-time endpoint, we could try to add all DOIs to the Dockstore community. This would give the Dockstore Zenodo user permission to edit the DOI and create versions for DOIs that are owned by end users.
Do we allow multiple users to create DOIs and we store multiple DOIs? (similar ticket https://ucsc-cgl.atlassian.net/browse/DOCK-1922)
How about the reverse where the Dockstore Zenodo user creates the DOI first and the end user wants to create their own DOI?

Shared access links would allow them to create new versions of the DOI, but they would not "own" the DOI

Review Instructions
Describe if this ticket needs review and if so, how one may go about it in qa and/or staging environments.
For example, a ticket based on Security Hub, Snyk, or Dependabot may not need review since those services
will generate new warnings if the issue has not been resolved properly. On the other hand, an infrastructure
ticket that results in visible changes to the end-user will definitely require review.
Many tickets will likely be between these two extremes, so some judgement may be required.
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-5929
https://ucsc-cgl.atlassian.net/browse/SEAB-6371
Security and Privacy
If there are any concerns that require extra attention from the security team, highlight them here and check the box when complete.

[x] Security and Privacy assessed

e.g. Does this change...

Any user data we collect, or data location?
Access control, authentication or authorization?
Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Due to this, there is a check to see if the entry has 0 DOIs or if all DOIs are Dockstore-owned to ensure that no exception occurs. I think there's a bigger conversation here about how we want to handle this situation so this PR takes the simplest route for now, i.e., not allowing the mixing of end-user-created and Dockstore-created DOIs.

I think this makes sense, basically allowing users to go from automatic to user-created but not vice versa

Do we allow multiple users to create DOIs and we store multiple DOIs?

A good observation, I guess we basically had this problem in some way already.

How about the reverse where the Dockstore Zenodo user creates the DOI first and the end user wants to create their own DOI?

I think we should allow this, there's a good chance the user may not know about the automatic doi feature until after it issues one, so we need to allow for this direction (automatic to end-user created)

Regarding the concept of snapshotting and then generating the DOI, some thoughts:
Will automatically snapshotting all tags mess up anyone's release flow?  Once the version is snapshotted, it's frozen.  Our assumption is that a github tag is a permanent fixture, but does everyone use it that way?  For example, imagine a repo where the stable tag is attached to the latest stable release and moves around.  The first stable tag would be snapshotted, and then Dockstore would reject subsequent retaggings.  Do people do stuff like that, and if so, should we support it?
If the answer to the last question above is yes, we might need to figure out what to do if a user accidentally/inadvertently freezes a version before they opt-out.

Regarding multiple DOIs, we've been discussing at least three sources of DOIs:

github-generated
user-generated Zenodo
dockstore-generated Zenodo
If you count "generate our own" custom DOIs, four sources. :)
Would be great if we could track all of them.  Time for a new "DOI" database entity?

Regarding the concept of auto-snapshotting before generating the DOI, some thoughts:
Will automatically snapshotting all tags mess up anyone's release flow? Once the version is snapshotted, it's frozen. Our assumption is that a github tag is a permanent fixture, but does everyone use it that way? For example, imagine a repo where the stable tag is attached to the latest stable release and moves around. The first stable tag would be snapshotted, and then Dockstore would reject subsequent retaggings. Do people do stuff like that, and if so, should we support it?
If the answer to the last question above is yes, we might need to figure out what to do if a user accidentally/inadvertently freezes a version before they opt-out.

Seconding this comment; didn't we find a Broad repo where they had "moving" tags, i.e., they delete their tags, then recreate them at new spots in the branches?
More generally, it makes me think, I wonder if we shouldn't relax the snapshot requirement and make it optional.

Regarding multiple DOIs, we've been discussing at least three sources of DOIs:
* github-generated

* user-generated Zenodo

* dockstore-generated Zenodo

If you count "generate our own" custom DOIs, four sources. :)
Would be great if we could track all of them. Time for a new "DOI" database entity?

I think we should support multiple DOIs as well. It would be easy to have both GitHub and Dockstore integration turned on.

More generally, it makes me think, I wonder if we shouldn't relax the snapshot requirement and make it optional.

I don't think we should be opinion-less on this one though.
From a bioinformatics perspective, I don't think we should be encouraging this behaviour since it is contrary to reproducibility. You could get completely different results from two runs of the same version of the same workflow if they have different code.
From a software engineering perspective, it violates the principle of least surprise and officially insane, according to the git documentation anyway.
I think the compromise here is that if a user is doing DOI issuing themselves, we don't actually automatically invoke a snapshot. We only invoke a snapshot as a pre-requisite to issuing a DOI ourselves.

More generally, it makes me think, I wonder if we shouldn't relax the snapshot requirement and make it optional.

I think the compromise here is that if a user is doing DOI issuing themselves, we don't actually automatically invoke a snapshot. We only invoke a snapshot as a pre-requisite to issuing a DOI ourselves.

Perhaps the auto DOI creation should be opt-in instead of opt-out to reduce the chances of freezing a version before a user notices and opts out? This would also match Zenodo's pattern with their GitHub integration

Some test failures related to the deprecation of the old DOI columns, will fix but in the mean time, re-requesting reviews

Is it worth it to add a trigger?

Does not seem like it, we can schedule a 1.16.1 ticket for example to delete the old columns


Lit.Extensions

This is an intial implementation of the Lit based (class components) in a separate package, these should give us a head start on "standard" Lit, we can refine this PR with extra things
For the LitElement class I didn't add every member since most of those are for internal/advanced use cases I don't think they're needed at least not right now
Also we can scrap this completely and do it on a separate repository

Regarding the "Function" based components that rely on lit only check this stackblitz
https://stackblitz.com/edit/js-rh5qqq?file=index.js
I'm not sure if fable can treat classes as values, but one thing is for sure it has to be a class because you need to extend LitElement which also inherits from HTMLElement which... can only be inherited by classes AFAIK but if we can include that JS script/translate to fable we should be good to go and have around 80 - 90% Lit support besides class based bindings that might be missing
we could ditch haunted completely given that we already have hooks with directives (the only one missing would be useController)

Thanks a lot for this @AngelMunoz! Yes, if we're going to provide bindings for lit-html we should also provide bindings for lit-element (still unsure what are the differences between lit-element and @lit/reactive-element, maybe we just need the latter?). Still wondering if we should explore the function approach before trying to use the class. With decorators, we can just build the JS class on the fly as haunted does or have a class with the common functionality and inherit with the render function as the HookDirective does. The new decorators feature in fable 3.3 is going to allow reflection info on the method. But F#/.NET attributes only accept literal values (strings, numbers and booleans, basically), so for styles and properties initialization we would need something like a hook:
[<LitElement("my-component")>]
let MyComponent () =
    let props = LitElement.init initStyles (fun () ->
       {| name = Prop("default")
          age = Prop(5, attribute=true, hasChanged= fun x y -> x < y) |} // Sadly, you cannot be younger, so age only changes up

    html $"""
Name: {props.name.Value} ({props.age.Value} years old)
"""

This should appear on top of the function and we can make a first run of the function to get the styles and properties. Then we can attach them to the generated class. For lifecycle we can just use the effects hooks. What do you think?

I found the constructors for Number, Object and similar ones but Didn't find String, should we add that in Fable.Core.JS?

I think I was trying to make devs just use F# instead, but we've already added other constructors with F#/.NET equivalents, so probably we can add JS.String as well for completeness.

still unsure what are the differences between lit-element and @lit/reactive-element, maybe we just need the latter?

ReactiveElement is the base class for LitElement I think for our purposes we can simply use the LitElement as our base class, as long as we are able to provide the static property properties we should be able to "react" to changes when consumers change properties or attributes (if the component autor allows it)

or have a class with the common functionality and inherit with the render function as the HookDirective does.

I think the link is pointing to this PR, I think that would be the ideal way to do it taking the example on the stackblitz link above this is the key behavior
const cls = class extends LitElement {
    // react to changes in the attributes

    render() {
      const fnArgs = Object.keys(opts?.props).reduce((curr, propName) => {
        // Lit will observe properties as long as we specify them in
        // the static properties geter
        curr[propName] = this[propName];
        // if the value is not set it's likely that the user specified
        if (opts?.props[propName]?.attribute && !curr[propName]) {
          // attribute property, the attribute property can be a string or a boolean
          if (typeof opts?.props[propName]?.attribute === 'string') {
            // if it's a string it means they used a different attributeNaeme
            curr[propName] = this.getAttribute(attribute);
          } else {
            // otherwise it should be the provided key
            curr[propName] = this.getAttribute(propName);
          }
        }
        return curr;
      }, {});
      // a the end simply invoke
      return viewFn(fnArgs);
    }
  };

then I add the static properties to cls we could also add the static styles there that can be an array of the tagged literal css or even a constructable stylesheet (the ones I added to Fable.ShadowStyles)
I like the args first approach used by haunted rather than the LitElement.init because it kind of lets the author focus on the function rather than the configuration, the configuration can come later when you register the component (because you can't skip that anyways either by decorator or by hand) one thing we should make very very clear to users is that attributes and properties are always optional (if we go for the args first approach) because there is no mechanism that can force a consumer to specify a particular attribute/property
for the configuration I've been thinking over the last two days how to make it more... F#'ish, I was thinking about using a DU somewhat like this
type AttributeConverter =
    | Complex of {| fromAttribute: string option -> obj option -> obj; toAttribute: obj -> obj -> obj |}
    | Simple of string option -> obj option -> obj

type Property =
    | Internal // {  state: true  }
    | Attribute // { attribute: true } -> 'myName' in html
    | CustomAttribute of string // { attribute: differentName }
    | Type of  obj // {  type: Number }
    | HasChanged of  obj -> obj -> bool
    | Converter of AttributeConverter
    | Reflective // { reflect: true }
    | NoAccessor // { noAcessor: true}

let props = [
  "age", [ Internal ] // { age: { state: true } }
  "color",
     [ Type(JS.Object);
       Converter (Simple(fun color -> stringToColor color)) ]
     // { color: { type: Object, converter: (color) => stringToColor(color) } }
]

and then just create the static props for the user with the given definitions
defineComponent ("my-component", MyComponent, props)

I guess we can use the hook to do that or a mix of both approaches?

I'm fairly unfamilar still of how those work (kinda gave me the idea after looking at decompiled source but haven't been able to dive deep with them)

I think we can then re-open this one and add the missing things for the Function based Lit elements

defineComponent ("my-component", MyComponent, props)

Oh something that is missing here as well is the ability to turn on/off the shadow DOM for a particular component which is crucial until constructable stylesheets arrive in all browsers and to have interop with existing css frameworks like boostrap/bulma/etc

reference for the property declaration interface https://github.com/lit/lit/blob/20b4dd3fbfc3b8313be8fb98af61d222a82f96d1/packages/reactive-element/src/reactive-element.ts#L111

I'm doing some progress on the attributes as I thought they could be used but the functions for the HasChanged case get curried and that won't work with Lit, here's a Fable Repl is there something I can use to compile them uncurried?

Sorry, I've fixed the links in my previous comment :)

I think for our purposes we can simply use the LitElement as our base class,

Yes, it seems ReactiveElement is just LitElement minus the rendering with lit-html. I guess it's designed to be wrapper of components in other frameworks: React, Vue, Svelte.

I like the args first approach used by haunted rather than the LitElement.init because it kind of lets the author focus on the function rather than the configuration, the configuration can come later when you register the component

That's true, although I see a couple of problems with using the arguments for the properties in Web Components:

First, this way Fable devs would understand the function can be called directly (as we do with React components), but if I understand it correctly, web components must be instantiated in HTML.
Second, if we have the function arguments, and then the configuration of these later, it will be difficult to check at compile-time that the names and the types match.

one thing we should make very very clear to users is that attributes and properties are always optional

If I understand the Lit examples correctly, if you provide a default value you don't need to deal with undefined options. This would be another point in making the props available trough an init function.

First, this way Fable devs would understand the function can be called directly (as we do with React components), but if I understand it correctly, web components must be instantiated in HTML.

That's a fair point,I think this will require some guidance regarding on "how-to register components"
because even if they have unit as a parameter, some people might feel tempted to call functions from other modules into another function which might break stuff since some components will depend on the correct this value
that's the reason why on the Fable.Lit.Templates I declared such functions private and only exposed a register one precisely because components as they are must be created via html or document.create('my-component')

If I understand the Lit examples correctly, if you provide a default value you don't need to deal with undefined options.

that's true, but at runtime consumers can assign null/undefined to properties and remove the attributes as well even with the init approach we would need to remember users that the runtime doesn't play by the F# rules (which is somewhat similar to the C# <-> F# interop)

@AngelMunoz It still needs some work but I added a draft implementation of the LitElement decorator so we can convert render functions to web components with an init function and react-style hooks. This is what it looks like, I think it's a nice way of defining web components and it makes for a nice transition of an Elmish component to a web component, what do you think?

Hey @alfonsogarciacaro the only thing that might be confusing here is the translation between camelCase and dash-case for attributes
in your example you used hourColor="red" this will always be converted to lowercase by browsers, for properties that's fine because lit uses .hourColor={color} for attributes it is expected to be something along hour-color={strColor}
But based on the comments of the PR, I guess with the Prop optional arguments this can be fixed  Prop("red", customAttr = "hour-color") or somewhat along those lines


Create a starter scaffold repo with our defaults

Create a starter scaffold repo with our defaults, for use with helm create -p for new projects
https://helm.sh/docs/helm/helm_create/

Include ingress config for defaultBackend - example from ADC values.yaml:
ingress:
  defaultBackend:
    enabled: true
    service:
      name: wparctic-wordpress
      port:
        number: 80

and here's where it gets inserted into metacat/helm/templates/ingress.yaml

Bitnami scaffolding is here for reference: https://github.com/bitnami/charts/tree/main/template
One downside of using custom scaffold templates is we do not benefit from up-grades in the helm defaults. So we'll have to watch that and try to keep things synced.
@artntek I created a scaffold repo here: https://github.com/DataONEorg/k8s-helm-template/. Its just a blank repo template, no customization -- please update the README when you add stuff to it.

@artntek I created a scaffold repo here: https://github.com/DataONEorg/k8s-helm-template/. Its just a blank repo template, no customization -- please update the README when you add stuff to it.

Thank you! Will do


Add predicate search box for ACLs in Ratel

For editing ACLs with a decent number of predicates, it'd be great to be able to search for the predicates instead of having to scroll down the list to edit permissions.
Related to #34 which is about general filtering for predicates in the schema list.

Added in bfc50b3


YARN-10978. Fixing ApplicationClassLoader to Correctly Expand Glob for Windows Path

Description of PR
Using File.separator instead of "/" to make  glob expansion OS agnostic.
Fixes following bug: https://issues.apache.org/jira/browse/YARN-10978
How was this patch tested?
Verified on a Windows test cluster. Yarn Auxiliary service starts correctly when the configuration is provided.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m  4s

trunk passed

+1 :green_heart:
compile
23m 18s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 58s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 28s

trunk passed

+1 :green_heart:
mvnsite
2m  3s

trunk passed

+1 :green_heart:
javadoc
1m 37s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 53s

trunk passed

+1 :green_heart:
shadedclient
23m 22s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  1s

the patch passed

+1 :green_heart:
compile
22m 38s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 38s

the patch passed

+1 :green_heart:
compile
20m 53s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 53s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 27s

the patch passed

+1 :green_heart:
mvnsite
1m 54s

the patch passed

+1 :green_heart:
javadoc
1m 16s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 15s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 59s

the patch passed

+1 :green_heart:
shadedclient
23m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 57s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 13s

The patch does not generate ASF License warnings.

215m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3558/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3558

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux a79130b3a38b 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 11fbd9d454e8a11f94cc9b6cb8ebdda3776ef4e9

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3558/2/testReport/

Max. process+thread count
1263 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3558/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@GauthamBanasandra this is in the direction of your current effort.
It looks good to me though.

LGTM as well.


When I clear mention using backspace by placing the cursor right after the mention, it doesn't remove the mention, instead it removes the character before the mention

Project version details:
react-quill : 2.0.0
quill-mention: 4.1.0
I'm using the above package in my nextjs app router which uses nextjs version: 14.1.4
Bug description:

In my Next.js application (version 14.1.4, app router), I'm using react-quill (version 2.0.0) along with quill-mention (version 4.1.0). I've encountered an intermittent issue when attempting to delete a mention using the backspace key. Specifically, when placing the cursor immediately after a mention and pressing backspace, the mention is not removed. Instead, the character before the mention is deleted.
Upon further investigation, I found that the cursor is being positioned inside the mention's enclosing  tag rather than after it, which seems to be causing the issue. This problem is also reproducible in the quill-mention demo provided in the package's README

Additional Information:
Intermittency: The issue occurs frequently but not consistently.
Version Constraints: Upgrading quill-mention causes my Next.js app to crash with the error reported in this issue.
Related Issues: Other users have reported similar problems as noted in issue #374 and issue #265.
Could you please suggest a fix for this issue ? Despite quill-mention being a great and useful library, this glitch in quill-mention significantly impacts its reliability.
Reason for Closing:
Please provide specific reasons when closing this issue to help understand any limitations or further actions needed.
Screen Recording:
A screen recording demonstrating the intermittent bug is attached for reference. Please observe the behaviour when I clear the mention "Eddie Hucquart" (at about 28-30 seconds into the video) in the simple demo section to see the bug in action:
Screen Recording 2024-06-04 at 9.43.59 AM.mov.zip

@MadSpindel Could you help us guide on how to fix this issue ?


Added additional known guids.

The additional guids come from Eric Zimmerman's list here. When there were collisions I picked one arbitrarily.

awesome, thanks!


Add guide on the usage of \PassOptionsToPackage{}

Have second thoughts, users should not deal with this low-level command.


not support https?

this is my config:
listen: "<IP_ADDRESS>:8000"
endpoints:    my etcd cluster setup  on 3 nodes ，the status is normal

"https://<IP_ADDRESS>:2379"
"https://<IP_ADDRESS>:2379"
"https://<IP_ADDRESS>:2379"

open the first page http://<IP_ADDRESS>:8000
Show This Error " client: etcd cluster is unavailable or misconfigured" .

ssl support in in this branch: feature/ssl


Increase performance for m2m preload

Optimized for big data

Hi @kimiby
Thank you for your PR! ;)

+1


Updated README with minor changes

Commit Notes: Rewording of dilatory statements, syntax modification, etc.
I feel that the rewritten usage would be better suited for the README.

Formal Pull Request was not completed due to the nature of the pull

@UniqMartin Updated.

Thanks for thinking about our documentation; it is much appreciated! I'll check back later once you had a chance to address my comments and I'm sure other maintainers also have an opinion on these changes.

@UniqMartin, my pleasure. Changes committed to patch.

Thanks again for thinking about the documentation! I'm not sure what motivated these changes, though; I don't think as-is they add any clarity but perhaps I'm missing the motivation? Cheers!

The main reason I made these changes was simply to re-word the current documentation. I felt that I could rewrite parts of the documentation to be more end-user friendly than it currently was.

Passing on this but thanks for the PR anyway, @fdizile.


APT source whitelist request for Apache QPID

This replaces travis-ci/travis-ci#4060.
The original text by @mbroadst follows

ppa:mcpierce/qpid-testing
Also, as a requirement for automated testing without authentication (i.e. without configuring SASL etc), the following line must be added to /etc/qpid/qpidd.conf:
auth=no

Hi,
In the months since I've opened this up, we have switched to the following official Qpid PPAs:
released - https://launchpad.net/~qpid/+archive/ubuntu/released
testing - https://launchpad.net/~qpid/+archive/ubuntu/testing
The same holds true for the qpidd.conf needing: auth=no

@BanzaiMan any comment on this?

For the time being, please use sudo: required to manage APT sources.

@BanzaiMan but that prohibits me from using the containerized service doesn't it? That was the whole point of proposing this months ago


Asset Share modals are broken by Apache ModSecurity

Describe the bug
Asset share modal POSTs are blocked by ModSecurity rule 950109 ("Multiple URL Encoding Detected").  This prevents modals from working on secure apache installs.
Environment

AEM Version: N/A
Asset Share Commons Version: 1.6.10
Author, Publish or both? Apache Dispatcher

To reproduce

Enable ModSecurity on your apache dispatcher
Attempt to open modals (download, cart, email, license) - they will fail with HTTP 403

Expected behavior
Download, Cart, Email, and License modals open when requested via dispatcher :)
Additional context
The crux of the issue is that the URLs are double encoded.  They are encoded when they are entered by JavaScript into the form as encoded values.  Then when the form submits, they are encoded again.
Stated simply

Path is /content/dam/myasset.jpg
Path in form data is %2Fcontent%2Fmyasset.jpg
Path submitted via POST is %252Fcontent%252Fmyasset.jpg This gets blocked by ModSecurity

Note that the double encoding seems unnecessary.  I tested passing single encoded paths and at least the download modal seems to work correctly.

And to be fully honest, I know the Download, Email, and Cart modals are broken by this.  I actually still have to see if License is affected by this.

This seems to have been caused #298

@sandeep-prasad can you please look into this? I don't remember what we did here :-(

My tested solve doesn't work.  Basically I think ModSecurity is checking for anything that is double encoded, so even spaces that start as %20 and become %2520 in the request are nixed by ModSecurity :-/

It seemed the problem was when extended characters were in the path, they were not being encoded properly in transit and thus could not be understood serverside.

@HitmanInWis can you provide the sample Request that has the double-encoded content? (what the browser is sending).  is the double encoding only incurring in file paths? or in other params as well?
IIRC the explicit encoding (via #298/303) was added because no encoding was taking place on the paths?

@davidjgonzalez, its pretty much all POST requests that send a path.  Easiest to repro is to click a download link on an asset.  There should not be a need to encode the path, because the form contents are already encoded when sent via the AJAX request, thus causing the double encode.

IRA SAMPLES ASSETS.zip
I created a sampling of weirdly named assets to help validate this ... These show existing gaps and also indicate that this problem is going to be much harder to solve :(
I think we need to make sure we're using the right encoders vs escaping throughout as well.


Binary caching with NuGet provider on macOS hangs on authentication to Azure Artifacts in Azure Pipelines

Describe the bug
Since 2023.08.09, vcpkg on macOS is unable to restore/push binary caching artifacts to Azure Artifacts NuGet feeds from Azure Pipelines, using Microsoft-hosted macOS agents.
Environment

OS: macOS
Compiler: N/A

To Reproduce
Steps to reproduce the behavior:

Checkout any tag after 2023.08.09 (e.g. 2023.10.19 or 2024.04.26):
Set VCPKG_BINARY_SOURCES='clear;nuget,FEED_URL,readwrite
Use a simple manifest (e.g. containing a boost port):

{ "dependencies": ["boost-algorithm"] }

./vcpkg install

Expected behavior
vcpkg restores/pushes ports to NuGet binary provider.
Failure logs
-(please attached failure logs)
Additional context
Relates to #14840

I opened a new issue, since my issue was not related to issues after interactive authentication.

This still seems unresolved using the latest vcpkg tag (2024.09.30): vcpkg package management program version 2024-09-30-ab8988503c7cffabfd440b243a383c0a352a023d (using NuGet version 6.10.0).

@stemann, I use your steps try to reproduce the behavior:.

Setting temporary environment variables
 export VCPKG_BINARY_SOURCES='clear;nuget,FEED_URL,readwrite'
./vcpkg install

Pushing NuGet to "FEED_URL" failed. Use --debug for more information.
See https://learn.microsoft.com/vcpkg/users/binarycaching-troubleshooting?WT.mc_id=vcpkg_inproduct_cli for more information.
Stored binaries in 0 destinations in 1.9 s.
Elapsed time to handle boost-exception:x64-osx: 3.3 s
boost-exception:x64-osx package ABI: 282239d84dea465b75758726cfd6b341698f6efe101a10500cb311463fab391d
Installing 41/41<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>Downloading boostorg-algorithm-boost-1.86.0.tar.gz
Successfully downloaded boostorg-algorithm-boost-1.86.0.tar.gz.
-- Extracting source /Users/vcpkg/Jon/vcpkg/downloads/boostorg-algorithm-boost-1.86.0.tar.gz
-- Using source at /Users/vcpkg/Jon/vcpkg/buildtrees/boost-algorithm/src/ost-1.86.0-78901f118f.clean
-- Found external ninja('1.12.1').
-- Configuring x64-osx
-- Building x64-osx-rel
-- Installing: /Users/vcpkg/Jon/vcpkg/packages/boost-algorithm_x64-osx/share/boost-algorithm/copyright
-- Performing post-build validation
Uploading binaries for 'boost-algorithm:x64-osx' to 'NuGet' source "FEED_URL".
Pushing NuGet to "FEED_URL" failed. Use --debug for more information.
See https://learn.microsoft.com/vcpkg/users/binarycaching-troubleshooting?WT.mc_id=vcpkg_inproduct_cli for more information.
Stored binaries in 0 destinations in 2.2 s.
Elapsed time to handle boost-algorithm:x64-osx: 3.8 s
boost-algorithm:x64-osx package ABI: 04dc498658af068003542e41f9d18358b755531f485f3bbe3667c4153506b80f
Total install time: 2.5 min
The package boost-algorithm is compatible with built-in CMake targets of FindBoost.cmake:

  find_package(Boost REQUIRED COMPONENTS algorithm)
  target_link_libraries(main PRIVATE Boost::algorithm)

or the generated cmake configs via:

  find_package(boost_algorithm REQUIRED CONFIG)
  target_link_libraries(main PRIVATE Boost::algorithm)

I want to confirm if this is the error you encountered?
Pushing NuGet to "FEED_URL" failed. Use --debug for more information.
See https://learn.microsoft.com/vcpkg/users/binarycaching-troubleshooting?WT.mc_id=vcpkg_inproduct_cli for more information.

I believe it was just hanging - checking... (will update this comment)


Error: Missing or invalid spatial reference system

Hi,
I'm trying to upload the given ascii file to ION but I get the following error:

Error: Missing or invalid spatial reference system
File: Area of interest.asc

The file contains bathymetry data downloaded as a esri ascii .asc from https://portal.emodnet-bathymetry.eu
Is there anything wrong with the file or is it not supported?
attached file

That file doesn't seem to contain a spatial reference system, which Cesium ion needs in order to reproject if needed.
It looks like there's an option to download a GeoTIFF version of these assets from that portal. Have you tried that?
Note that there are some known issues with bathymetry rendering, see: https://github.com/CesiumGS/cesium-ion-community/issues/1
I'm going to close this issue as this is not specific to CesiumJS, but if you're still having trouble getting your data into Cesium ion, feel free to open a new issue on the the Cesium ion community repo (https://github.com/CesiumGS/cesium-ion-community) or on the Cesium forum (https://community.cesium.com/).

There's another option when you download to get a 32-bit GeoTIFF file.  I downloaded one of those and it had the necessary georeferencing information (though it isn't strictly clear what the vertical reference is, but I didn't look very hard).


Quick create a new Patient inside Scheduling, Medications, etc

🚀 Feature Proposal
Create a button inside every form that has a patient field in it (Scheduling, Medications, etc). The button opens a modal with a simplified version of the New Patient form with only the basic informations. After the creation, the new patient is automatically selected as a option in the patient field.
Motivation
It is a very common feature that I have already seen in others HIS. It improves UI/UX by letting the user dynamically creates a new patient without leaving the current form, making it a little less frustrating.
Example
While inside the Scheduling form, if the user needs to create a new appointment to a patient that has not already been registered, he can dynamically creates it with the Quick Create Patient modal form and promptly continue with the appointment register.

Hello,
I would love to try and get this going for you!
Thanks


Performance problems with using "FastArray" in Matrix3

As of this writing, Matrix3.js contains the following bit of code starting at line 26:
  var createIdentityArray = FastArray === Array ?
                            function() {
                              return [ 1, 0, 0, 0, 1, 0, 0, 0, 1 ];
                            } :
                            function() {
                              return new FastArray( identityFastArray );
                            };

As part of work that is being done to improve the performance of the energy-forms-and-changes-sim (see https://github.com/phetsims/energy-forms-and-changes/issues/99), I was seeing a lot of time spent in this function.  Below is a screenshot that shows the bottom of the call stack with a bunch of long calls to createIdentityArray.  The tool top shows that one of these calls is taking almost 14ms, and there are a bunch of these calls, so all together they are essentially killing the performance of the drag operations.

I tried changes this code not to use FastArray, and the problem seemed to go away.  I showed this to @jonathanolson over zoom, and he was surprised, and basically said that he'd take it from here.

Snapshot comparisons with added performance tests are showing that this should be safe, and the normal Array version in Chrome seems to be the overall fastest (shaving about 4% off of the combined sim load/fuzz from what we had before).
@jbphet can you see how this behaves in EFAC?

This is a vast improvement, so much so that I don't even see the calls to createIdentityArray in the call tree when I profile.  To compare, I picked a drag event from a RequireJS version on master and compared the duration of the call to globalToParentPoint to that in the profile shown in the image above.  Before the change, this was taking 70 ms, not it's taking 0.13 ms.  I'd call that a big win.
Here's a screenshot that shows this.  Note that I had to be zoomed in a lot further than in the profile above to even see the method calls that I was looking for.

@jonathanolson - this is resolved as far as I'm concerned, you're welcome to close it unless there is further work that you believe is warranted.


Remove the duplication in inbound server

Remove the duplication in inbound server for both TCP and TLS stream by generic mechanism of Rust.

It is very possible that tcp and tls service builder could be different later. I am not sure if this is right way

Hi @hzxuzhonghu, use generic pattern to remove the duplicated code is the way I am thinking, there are too many Syntactic sugar in Rust

obsolete since https://github.com/istio/ztunnel/pull/186. thanks!


.size (text to number)

file external .json
[
{"value": "100", "name": "IT"},
{"value": "70", "name": "SAP"},
{"value": "40", "name": "ADsddssS sdfds sM"}
]
// d3plus
var visualization = d3plus.viz()
.container("#viz")
.data(info.json)
.type("tree_map")
.id(["name"] )
.size("value")
.draw();
Please

@jobga please describe the issue you are having, and post a jsfiddle.net snippit showing the problem.
If I had to guess: maybe turn your "value" keys into Numbers instead of Strings (100 instead of "100")


Game Reset Doesn't Work

(NOTE: This issue is a migrated issue from the old git instance)
Because the organization of the scores sub(sub(sub(sub)))) dictionaries has gotten so messy, resetting the game doesn't work.
Need to either update the reset game function, and/or organize game.scores better.

Also, the final results page currently shows the join and new game buttons from index. Need to update to show the actual reset options.

Also, the final results page currently shows the join and new game buttons from index. Need to update to show the actual reset options.


Normalize in orphan check

We now normalize during orphanck and treat ty params in rigid alias tys to be uncovered.
However, for projections specifically, we don't emit a hard error but just a future-incompat dont-report-in-deps warn-by-default lint (tracked in rust-lang/rust#124559).


Steps in wrong place

Unless I'm reading it wrong, steps 4 onwards for "Create an account and set Exchange properties" should actually be step 3 onwards under "Add an email address for your on-premises domain account"?

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

ID: 9978e48b-5b8d-df59-d8d3-d3c90a8efafb
Version Independent ID: 52429f1d-39a1-49fb-c9dd-d4bafa19760d
Content: Deploy Skype Room Systems v2 with Exchange Online (Hybrid)
Content Source: Skype/SfbServer/deploy/deploy-clients/with-exchange-online.md
Service: unspecified
GitHub Login: @jambirk
Microsoft Alias: jambirk

verified with Travis Snoozy and made the requested change.


K8SPG-352 post release changes

CHANGE DESCRIPTION
Problem:
Short explanation of the problem.
Post release changes.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are the manifests (crd/bundle) regenerated if needed?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PG version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

init-deploy
passed

demand-backup
passed

scheduled-backup
passed

start-from-backup
passed

monitoring
passed

telemetry-transfer
passed

We run 6 out of 6

commit: https://github.com/percona/percona-postgresql-operator/pull/436/commits/ef017b3d7a8fcc51827430045692e58acf1b4db2
image: perconalab/percona-postgresql-operator:PR-436-ef017b3d7


read_chunks directly from a census zip file

Should work fine with ZipFile.open; dunno how speed will be.

Added in https://github.com/dougalsutherland/pummeler/commit/585d9cd904e188627b76f8bbc1482181c306d818.


faq: list possible causes for fluctuating optimization levels

List the most probable causes for fluctuating levels of optimization in the output.
May help with questions like https://github.com/pagespeed/ngx_pagespeed/issues/1393

NB build failure seems because of a test flake related to 'inline_google_font_css' that seems to occur frequently lately.
The log ends with
End of log/system_test.log:
nline_google_font_css    -o /tmp/mod_pagespeed_test.root/apache/fetched_directory/wget_output.txt                                                   -O /tmp/mod_pagespeed_test.root/apache/fetched_directory/wget/fetch_until_output.30491 until $(grep -c @font-face) = 1
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Fetched file: 333 bytes (
<html>
  <head>
    <title>inline_google_font_css example</title>
    <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Roboto">
    <style>
      body {
        font-family: 'Roboto', sans-serif;
      }
    </style>
  </head>
  <body>
  The font should be slightly more robotic.
  </body>
</html>
)
TIMEOUT: wget -q    -o /tmp/mod_pagespeed_test.root/apache/fetched_directory/wget_output.txt                                                   -O /tmp/mod_pagespeed_test.root/apache/fetched_directory/wget/fetch_until_output.30491 http://localhost/mod_pagespeed_example/inline_google_font_css.html?PageSpeedFilters=inline_google_font_css output in /tmp/mod_pagespeed_test.root/apache/fetched_directory/wget/fetch_until_output.30491
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:671: fetch_until
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_tests/inliners.sh:60: source
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:249: run_test_helper
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:226: run_test
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test.sh:66: source
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/system/system_test.sh:42: source
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/apache/system_test.sh:101: main
     failure at line 60
in 'inline_google_font_css Can inline Google Font API loader CSS'

re: inline font flakes: are you fully synced? I was hoping I reduced it some after 3f8b6cc3c8d206aaa5365a7d330f06bfdd7f2475
Hmm. GitHub probably merges into master anyway, and this isn't one I could explain, I think.
(One cause was due to some sort of an experiment)

@morlovich The branch was derived from master (yesterdays state), so I think it was fully synced. I can't relate it to the doc change proposed in this PR. I looked into the failure a bit but can't explain it either (yet).


Deadwood mission error

When i do a deadwood mission all is fine until i try to cut a felled tree into smaller pieces with the komatsu harvester while your mod is active. If i try to do that i get a lot of Error: Running LUA method 'draw'. in the log.
log.txt
(there are only 3 entries in my log as i deleted the rest of it for a smaller file size)

Hi, it appears you are using an older state of my mod (unfortunately all of them have version <IP_ADDRESS> since they were queued for mod hub.
Do you know how to create your own zip from the newest commit on this repository? If not, I can create one for you, but only in around 6-8 hours from now

Thanks for the replay, yes i can do it myself and will try again.


Redevelop SPCINV (8)

This compute geodetic crds from ECEF... Currently using pymap3d to handle these.


[fuzzers] do not fail fuzzers with empty input

I'm not sure what you're trying to fix and why you only change those 2 files in  that case,

@kroeckx these two fuzzers (and only these two) fail on empty input (len=0). As far as I can tell this happens because BIO_write doesn't like lenght=0.

You mean BIO_write() returns -1 on those and so the assert fails?

Yes


Feature Request - Add Multiple Groups To Doc Gen Request In package.json to improve documentation grouping - duplicate of #41

Currently all documented items are shoved into one long, unsorted, list.
In package.json change the config to allow multiple title / include configs and to iterate through them to generate a docute sidebar with
  "vuese": {
    "title": "My Project Components",
    "genType": "docute",
    "outDir": "docs",
    "include": ["src/components/ui/*.vue", "src/components/tasks/*.vue", "src/mixins/**/*.vue"]
  }

Generates this
        sidebar: [
            {
                title: 'NOQU Go Components',
                links: [
                        ui component link Z,
                        ui component link A,
                        task component link B,
                        task component link J,
                       Mix in P,
                       Mix in K,
                       Mix in C,
               ]

So, if you could specify an array of title and include objects such as
  "vuese": {
    "genType": "docute",
    "outDir": "docs",
    "include": [
        {
            "title": "UI Components",
            "include": "src/components/ui/*.vue"
        },
        {
            "title": "Task Components",
            "include": "src/components/tasks/*.vue"
        },
        {
            "title": "Mixins",
            "include": "src/mixins/**/*.vue"
        }
    ]
  }

then it should generate the following sidebar with multiple groups and sorted elements
        sidebar: [
            {
                title: 'UI Components',
                links: [
                        ui component link A,
                        ui component link Z
                ]
            },
            {
                title: 'Task Components',
                links: [
                        task component link B,
                        task component link J
                ]
            },
            {
                title: 'Mixins',
                links: [
                       Mix in C,
                       Mix in K,
                       Mix in P
               ]

This is a duplicate of #41 - sorry

I added the grouping feature to the documentation site.

Thank you
On Thu, 21 Mar 2019, 12:29 HcySunYang<EMAIL_ADDRESS>wrote:

I added the grouping feature to the documentation site.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/vuese/vuese/issues/49#issuecomment-475210272, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH-jEtoCPwp7XBbMet-nFoQjOaz6AuZPks5vY3sxgaJpZM4b_Dqb
.


Communication log buffer size

There is currently and issue where sending a large message (styled html) causes the communication log to overflow.
I've gotten corrupted size vs. prev_size as error output, indicating overflow in a separate thread.
Setting a bigger buffer size fixes the issue.
May I also ask why are pointers used so much and have you thought about refactoring to use more of std::string or std::string_view?

Working on an auto-growing communication log buffer in version 1.1.5
Regarding all the pointers in class headers, the goal was to expose only Pure C Interfaces publicly. This way you have the possibility to build the library alone and consume it in many projects without having to worry about the version of the compiler and the version of the standard library used.
This is well explained in the following blog post:
The Perils of C++ Interface DLLs
That being said, I think it's possible to do both. I will think of a way to let the developer choose between Pure C Interfaces or Modern C++ Interfaces.
Thanks for submitting the issue and for this excellent suggestion.

Solved in version 1.1.5


Remove statistics module from alpha-g-wire-noise-statistics

All those features (mean, covariance, std_dev) are already available in the statrs crate.
I didn't notice this when I was implementing this binary. It would be good to just get rid of this whenever I have time to do it.

See alpha-g-pad-noise-statistics


Add simple CST fuzzer

Implements a simple CST fuzzer for testing Kataw CST

@aladdin-add can you find a way to test this?


Input component requires value property if you use a label

When I want to use the Input component with a label and I don't set the value using state, the label will not stay in its up position when the element is not in focus anymore. I prefer to use refs instead of state to get the value out of my inputs, but this option would not work properly.
In order to replicate the problem:

Make an Input with a label, but without a value property
Try typing in the input, this pushes the label out of the way, as expected
Now when the input loses focus, the label returns to its original position, in the same place that the input value is

If it makes any difference I am using react-toolbox with Meteor and am using version 0.16.2.

It should not make any difference. I'm quite busy this week, I'll try it during the weekend

I can confirm this bug with the latest version of the code. The class filled is only applied if there is a value present, and that only occurs if valuePresent returns true. Below is how value present is calculated:
const valuePresent = value !== null && value !== undefined && value !== '' && !Number.isNaN(value);


Use state plane projections for state shapes?

see: https://github.com/veltman/d3-stateplane
https://en.wikipedia.org/wiki/State_Plane_Coordinate_System

Right now we keep all geometries in decimal degrees so we can mix and match. Making this change would mean either creating a division level that isn't interoperable with child geometries or making the conversion down the entire geometry chain.
I get that the coordinate system is marginally better display but ... is that really worth it?

Here's my biggest worry about interoperabiltiy:

the system is highly accurate within each zone (error less than 1:10,000). Outside a specific state plane zone accuracy rapidly declines, thus the system is not useful for regional or national mapping.

Good point, national maps wouldn't work out.

Closing this out per discussion.


GEOPY-704

GEOPY-704 - update version reference in readme and PyPI badge

Codecov Report

Merging #13 (1b08621) into develop (c72cb58) will increase coverage by 3.90%.
The diff coverage is 89.87%.

@@             Coverage Diff             @@
##           develop      #13      +/-   ##
===========================================
+ Coverage    79.88%   83.79%   +3.90%
===========================================
  Files           11       12       +1
  Lines          696      944     +248
  Branches        89      133      +44
===========================================
+ Hits           556      791     +235
- Misses          92       93       +1
- Partials        48       60      +12

Impacted Files
Coverage Δ

omf/fileio/geoh5.py
89.07% <89.41%> (+4.33%)
:arrow_up:

omf/fileio/__init__.py
100.00% <100.00%> (ø)

omf/fileio/utils.py
100.00% <100.00%> (ø)

omf/data.py
77.77% <0.00%> (+2.22%)
:arrow_up:

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


Added types for riteway/match and riteway/render-component

I discovered that render-component and match typing only worked when you also imported from "riteway" in addition to "riteway/match".
This minor update allows both match and render-component to be imported standalone without depending on the main "riteway" import.

Released as v8.0.0-RC2


Geojson Layers

Describe the New Feature
Add capability to display and animate GeoJSON layers in the web application:

[x] Generate a set of GeoJSON variables and upload to S3 bucket following the documented data structure.
[x] Update API to get a list of model configurations.
[x] Update API to get a list of model run times for a given configuration name.
[x] Update API to get a list of valid times for a given model run time.
[x] Update API to get GeoJSON data given a configuration name,  model run time, valid time, and variable name.
[x] Update UI to query available model configurations.
[x] Update UI to query available model run times given a configuration name.
[x] Update UI to query available valid times given a configuration name and a model run time.
[x] Update UI to request and display GeoJSON data.

Acceptance Testing
WRF output data are displayed with a nice user experience.
Time Estimate
3d
Sub-Issues
Consider breaking the new feature down into sub-issues.

[ ] Add a checkbox for each sub-issue here.

Relevant Deadlines
List relevant project deadlines here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority

Projects and Milestone

[ ] Select Project
[ ] Select Milestone as the next official version or Backlog of Development Ideas

New Feature Checklist

[ ] Complete the issue definition above, including the Time Estimate and Funding source.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>/<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project, and Development issue
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

Fixed with #56


fix(yarn.lock): run: yarn upgrade cz-conventional-changelog

for security vulnerability

:tada: This PR is included in version 1.7.3 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Doesn't work on other keyboard layouts

if the keyboard is in Russian, it doesn't work.
I suggest using event.code = KeyZ and event.code = KeyY

A better suggestion would be to use metaCode + Shift + Z for redo

Hey @envyboxkf @groteworld @einerzg
A new issue to address this improvement has been created (#48)
Please, add your thoughts there, and let's discuss the proposed solution :)
Best!

Closing this in favor of #48


Wrong description of StartDate and EndDate

This page indicates StartDate and EndDate are the dates of meeting.  However, when running the Powershell command, it is the modify date of the meeting:
[PS] >Get-CalendarDiagnosticObjects -Identity $h.Name -StartDate 03/20/2022 -EndDate 4/1/2022 | Where-Object {$_.ParentDisplayName -eq "Calendar"}
WARNING: Using filter 'StartDate and EndDate'. Items with OriginalLastModifiedTime between StartDate 3/20/2022 12:00:00 AM and EndDate 4/1/2022 12:00:00 AM will be returned.
WARNING: Streamable properties values may be truncated.

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

ID: a3e0524b-e92d-eefb-5416-557620edfb39
Version Independent ID: 7afae510-9006-4667-5756-92714f0b08f0
Content: Get-CalendarDiagnosticObjects (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@jgriff500, fixed. If you want to modify the fixes or clarify anything, see the edit instructions here:
https://github.com/MicrosoftDocs/office-docs-powershell/blob/main/README.md
Thanks for the feedback.
Closing


docs: Update buildkit-template.yaml

add readinessProbe

Fixes #TODO
Motivation
we got this error could not connect to unix:///run/buildkit/buildkitd.sock after 10 trials, when we test buildkit-daemonless.sh build.
Add readinessProbe to make sure The buildkit service start succeeded.
https://github.com/docker/buildx/blob/bab60779cf4df24e73b5692e98f61a80555d1537/driver/kubernetes/manifest/manifest.go#L57-L63
Modifications

Verification

Need to run make codegen to fix the build


Error in status code in response when calling REST API resource of self-sign up

Description:
When calling REST API resource of self-sign up from browser, it returns 200 (successful) status code for error response as well. When try to create a new user with already existing user name, it returns an error response with 200 status code.
Response is :
{"code":900604,"message":"User creation failed","description":"Error occurred while creating user. ","moreInfo":{"USERNAME":"username"},"error":[]}
Suggested Labels:
Bug
Suggested Assignees:

Affected Product Version:
APIM 3.0.0
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

I’m closing this issue because it has been inactive for more than two years. Please reopen if you still encounter this issue with the latest version.


Update sbt-scalafmt to 2.4.6

Updates org.scalameta:sbt-scalafmt from 2.0.7 to 2.4.6.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-scalafmt" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

I'll take a stab at a PR that upgrades both sbt-scalafmt and scalafmt itself to latest.


Peertube

Your "guide" is too high a bar of entry and completely unnecessary for something this simple.
It would be nice if you could add support for peertube, tho: https://joinpeertube.org/en/
I looked at your extractors and none of them seem to be usable, so this needs to be done on youtube-dl side. (I would've requested peertube to add youtube-dl support if an existing extractor seemed usable.)

You might want to consider an open standard for defining video in pages. So that someone else could make their own peertube-like and add support for youtube-dl, without having to look/act like peertube to youtube-dl.
Something with meta(?) tags or something.

and this is how you know a project doesn't care about users.


DPL-nnn Cardinal - cell banking pipeline

User story
In addition I (Human Genetics) require a separate pipeline that allows the banking of extracted PBMCs, so that the samples can be re-processed if they fail the first time round. For this I require (process map to follow when I obtain the outstanding information):

Create a LCA Blood Bank Plate (96 well).

Be able to print a barcode for this plate.

As I scan in a blood tube barcode the sample is assigned to the next available well. E.g. 1st tube scanned is assigned to well A1, 2nd tube scanned well B1. The plate may not be fully occupied.

Allow rescanning of the same tube so that the same sample can be added to more than 1 well.

Once the plate is filled (partially filled) a manifest is created that shows the order of the samples in the plate. Information about the collection site must also be collected.

This manifest can be used to make a submission for banking

The vacutainer blood collection tubes are returned to a storage location.

From the LCA Blood Bank Plate create LCA PBMC Bank Plate (print barcode).

Transfer to 2D barcoded tube (Sameena – information pending).

Place tubes into storage location.

Output file with original tube barcode, new fluidx tube barcode, and new rack barcode - send to another team that stores them in a freezer.

Who are the primary contacts for this story
Stef L
Acceptance criteria
To be considered successful the solution must allow:

[ ] add a list of acceptance criteria here
[ ] ...

Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

#<issue_no.>
sanger/#<issue_no.>

Additional context
Add any other context or screenshots about the feature request here.

Talk to sample management about how they normally do the transfer into the fluidx tube racks.


The number of crawled paper is very small

Hi plz some one help me with this:
I utilized GNews to crawl News from 2023.10.1 to 2024.3.10 about the "Red Sea Crisis", but only got about 80 papers.
But when I search key word in Factiva for the same duration, it has results about 3000 articles. I am doing NLP analysis so the volume of articles is quite essential.
Is the number of articles being limited by GNews or it simply does not have that much articles on Google News?

This is a related issue suggesting some workarounds: https://github.com/ranahaani/GNews/issues/31

I think the max I can get is 100 a day. Can anyone do better?

No, we tried crawling by the hour, but then we did not get any additional results. They seem to have the same time stamp for all posts published in one day, so you get the same 100 results wherever you start. In the end, we adjusted the research question a bit to work with 100 results per day but crawl through several months of data.

I think I managed to get a few more by iterating every hour but I think this is okay for now- thanks for the response. I think the error warning of 'must be 1 day apart else no results will return' should be altered however because you can get results by looking from hour to hour. However,  iterating by hour doesn't work 100% from my experience.


The node manager issues 2 update notifications per single node update

Bug report
General Information
With latest master (3a4fbd5fefec59ab50efc2c5bd271826e6f495ed at the time of reporting this issue), the node manager issues updates notification twice for a single change. I did not attempt to bissect in order to pinpoint when this issue first occurred as I haven't tested if this behavior is reproducible with older cilium releases.
How to reproduce the issue
Just run cilium. The behavior can be easily observed with hubble enabled by using the hubble CLI:

Start cilium with hubble enabled (--enable-hubble).
Use the hubble CLI to monitor for hubble peer notifications with hubble peers watch (requires latest hubble master).
Trigger a change. For example, when using the dev vagrant VMs, restart the cilium service on one node. In my case, I see the following:

$ hubble peers watch
PEER_ADDED   k8s1 <IP_ADDRESS>
PEER_ADDED   k8s2 <IP_ADDRESS>
PEER_ADDED   k8s3 <IP_ADDRESS>
PEER_UPDATED k8s2 <IP_ADDRESS>    # <-- this is expected
PEER_UPDATED k8s2 <IP_ADDRESS>    # <-- but this is not

I fail to reproduce. Will re-open if I do.


By tracking overall CPU usage for process profiler could detect sample collections irregularities

This is a purely defensive measure but might provide interesting insights. The idea being that if e.g. process 1234 is reporting usage of 1s of CPU and we are sampling at a 100 frequancy we should have 100 samples. It is probably fine for us to observe some irregularities here, but I would think the information can help identify faults in the assumed behaviour of underlying OS facility (perf on Linux). The functionality could be used via performance counters to similarly make observations on other event types.

Since version 2.0, async-profiler records jdk.CPULoad JFR event every second, which includes

the process' user and system CPU load;
overall machine CPU load in %.

JDK Mission Control and IntelliJ IDEA use this information to display nice CPU usage graphs. Other tools may parse JFR output to analyze this information somehow, but I guess this is beyond async-profiler responsibilities.

Thanks!

The way CPU load is recorded by the JVM is confusing:

Process CPU% (of machine) + system CPU%(of machine)
Thread CPU% (of machine)
This makes sense only if you know the number of available cores.

Good point. JFR has jdk.CPUInformation event - I'll make async-profiler record that too.

Forgot to mention, I've added jdk.CPUInformation event.

Forgot to mention, I've added jdk.CPUInformation event.


Feature: Add .gen.toml for configuring include / exclude of files to template

Adds support for a .gen.toml file which allows for templates to configure which files should be processed, either using a whitelist method (include), or a blacklist method (exclude), with include being preferred over exclude if both are present. This mirrors the behavior used by cargo for the configuration options of the same name in Cargo.toml, and uses some of the same code.
closes #144
closes #124
closes #48
closes #43
closes https://github.com/cloudflare/worker-emscripten-template/issues/1

would very much like feedback from @k0pernicus and @DD5HT on this!

No problem, I can look at the PR this evening :)

needs squash before merge

renamed config file name to cargo-generate.toml from .gen.toml. I am not attached to either name, but I believe the new one is a little better.

implemented steve's PR feedback, rebased onto master, and added more detail to readme about how this feature interacts with template tags in filenames.


fix: do not dismount inscription content from view

Try out Leather build f90937e — Extension build, Test report, Storybook, Chromatic

@brandonmarshall-tm, re conversation yesterday. Once an inscriptions is rendered, we leave it rendered, even if scrolled out of the viewport.

Tested, this looks and runs great! It does still un-load when switching accounts which I think is perfectly acceptable. Will definitely let you know if we get any complaints of sluggish behavior as a result of not removing from cache on scroll, but it's working great on my machine.


HTTPie test error

Hi,I'm study 14.2.8 now, there seems like a network error when I try a test. I tried google it but no good answer.
I use the anonymous command http --json --auth : GET http://<IP_ADDRESS>:8888/api/v1.0/posts/ and it returns:
http: error: ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=5000): Max retries exceeded with url: /api/v1.0/posts/ (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x10991c9b0>: Failed to establish a new connection: [Errno 61] Connection refused',)) while doing GET request to URL: http://<IP_ADDRESS>:5000/api/v1.0/posts/
Even when I clone your code and try it, there is the error. So I think it's because the network is wrong somewhere and I can't find what exactly it is.
Thanks for your help.

Are you using the correct port number? I see two ports mentioned in your output, 5000 and 8888. My guess is that you have your server listening on a different port than what you are using in the HTTPie command line.

sorry, that's because I tried the two ports 5000 and 8888 in Terminal and copied different command and  return to paste in this issue.
I also tried curl right now, it returns the same error.
`> curl -v http://<IP_ADDRESS>:5000/api/v1.0/posts/

Trying <IP_ADDRESS>...
TCP_NODELAY set
Connection failed
connect to <IP_ADDRESS> port 5000 failed: Connection refused
Failed to connect to <IP_ADDRESS> port 5000: Connection refused
Closing connection 0
curl: (7) Failed to connect to <IP_ADDRESS> port 5000: Connection refused`

Are you running the server? The error suggests there is no server running on port 5000.

No, I'm not running the server. Should I?
The book says use pip install httpie to install HTTPie, then use an email and password to run the GET request. And the commands run on the terminal directly.

I choose the anonymous way http --json --auth : GET http://<IP_ADDRESS>:5000/api/v1.0/posts/
In fact the only command I know to run a server on port 5000 is python manage.py runserver.
There are the commands runs and returns below:
python manage.py runserver is OK, http --json ... is NOT OK, and a http ...test is OK

http://blog.csdn.net/huang5487378/article/details/60778293 (Last pic)
Yes it should have two terminal tab to start the server first and then start the http command.
Thank you very much.


Update the app Italian resource

Please indent the file using spaces instead of tabs.

Because this translation has not yet been included

It's still reindenting all the file: https://github.com/jonan/ForkHub/pull/320/files
Compare the diff with this one: https://github.com/jonan/ForkHub/pull/324/files
Only the modified lines should appear in the diff.

Now the merge should be possible...

Please add my work on the official repo


instaloader returns likes count is -1 but browser data shows likes count

Describe the bug
edge_media_preview_like is a finite value when seen in a browser i.e window._sharedData.entry_data.PostPage[0].graphql.shortcode_media

but in instaloader's in node object it is -1

To Reproduce
https://www.instagram.com/p/CUrAS88Pr1G/
from instaloader import Instaloader, Post
loader = Instaloader()
post = Post.from_shortcode(loader.context, "CUrAS88Pr1G'')
print(post.likes) # prints -1

Additional context
It seems to happen only for logged in accounts on certain posts (ones with like_and_view_count_disabled = true), post.likes works if I am not logged in
but if you are rate limited on IP post.likes requests login
I have noticed a pop up opens up when I am logged in and then it calls https://www.instagram.com/p/CUrAS88Pr1G/likedby to get data but I just want to get number of likes
Expected behavior
It should return number of likes 1436 as of now
Error messages and tracebacks
None
Instaloader version
instaloader --version is 4.8.1

To Reproduce
https://www.instagram.com/p/CUrAS88Pr1G/
from instaloader import Instaloader, Post
loader = Instaloader()
post = Post.from_shortcode(loader.context, "CUrAS88Pr1G'')
print(post.likes) # prints -1

With this code, i.e. anonymously, Instaloader returns the correct likes count. However, when logged in, the likes count or -1 is shown, depending on the account settings.

With this code, i.e. anonymously, Instaloader returns the correct likes count. However, when logged in, the likes count or -1 is shown, depending on the account settings

What do you mean by "Depending on the account settings", is there a setting I can turn on to see like count when being logged in?

To Reproduce
https://www.instagram.com/p/CUrAS88Pr1G/
from instaloader import Instaloader, Post
loader = Instaloader()
post = Post.from_shortcode(loader.context, "CUrAS88Pr1G'')
print(post.likes) # prints -1

With this code, i.e. anonymously, Instaloader returns the correct likes count. However, when logged in, the likes count or -1 is shown, depending on the account settings.

It seems to not depend on account settings, cause I'm triyng on many thousands of shortcodes and the results (collecting not anonimously) is always -1

See https://help.instagram.com/113355287252104/

See https://help.instagram.com/113355287252104/

Ok. Is there any workaround? Thanks


s3 update failure in sidecar as a result of pull reqeuest 632

We encountered the following error in our sidecar after moving to release: master-2018-11-16-d4887bf that had pull request 632:
/data/prometheus/thanos/upload/01D07R41K7NH577M07Q65NDVR5/meta.json as debug/metas/01D07R41K7NH577M07Q65NDVR5.json: upload s3 object: Invalid canned ACL"
This error does not occur on prior releases of the sidecar.
We attempted to fix this issue by applying a canned ACL to our S3 bucket but the product we are using does not support this yet.  Would it be possible to please add a flag that will disable the sending of the UserMetaData that was added in pull request 632?  We are using the IBM Cloud Object Storage product.
Thank you.

Fix: https://github.com/improbable-eng/thanos/pull/710

Thank you for getting started on this so quickly.  It is greatly appreciated.

Please review if you want it fast (:


Revisit arrays.concat

Expected behaviour
The current implementation flattens the output
Actual behaviour
Is this correct?
References

Hey, can I have this issue ?

Fixed in 0.32.1


TST: AmbiguousTimeError with set_index()

[x] closes #12920
[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

this has been fixed by #13750. added tests.

One typo, looks good!

Current coverage is 85.23% (diff: 100%)

Merging #13814 into master will increase coverage by <.01%

@@             master     #13814   diff @@
==========================================
  Files           140        140
  Lines         50420      50420
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          42974      42976     +2
+ Misses         7446       7444     -2
  Partials          0          0

Powered by Codecov. Last update 31f8e4d...f6696ff

thanks!


add scopenote to rules

This adds the ability to 'comment' on rules in order to assist people applying them, in a way that can be picked up and used by authoring tools and other systems.

Closes #90.


Introduce TopologyRefreshFinishedEvent to get topology refresh metrics

Feature Request
For now, there are 2 events in Lettuce v6.1 about topology refresh.

TopologyRefreshEvent (Triggered when topology refresh has started.)
ClusterTopologyChangedEvent (Triggered when topology refresh has successfully finished and topology has changed.)

I'd like to introduce a new type of event which is triggered each time when topology refresh has finished.
It should be triggered both on successful or failure cases.
Is your feature request related to a problem? Please describe
I sometimes encounter Redis cluster failover problem.
On my service, the failover delay is quite important.
My Lettuce client sometimes takes more than 30 seconds or more to get topology refreshed.
In order to make the topology refresh event more observable, I'd like to introduce this event.
Describe the solution you'd like
Trigger new ClusterTopologyFinishedEvent when refreshPartitionsAsync has finished.
https://github.com/lettuce-io/lettuce-core/blob/64801c788452dd2b938cda5ee103a86f1930de89/src/main/java/io/lettuce/core/cluster/RedisClusterClient.java#L901
# code sample
public class ClusterTopologyFinishedEvent implements Event {
    private final List<RedisClusterNode> before;
    private final List<RedisClusterNode> after;
    private final Throwable exception; // nullable
    private final long startedAt;
    private final long finishedAt;
}

This event should the following information.

Success or failure.
Time elapsed.
(optional) Topology refresh reason(scheduled or adaptive).
(optional) Exception if failed.
(optional) Nodes found.

Describe alternatives you've considered
Without this event, I can implement similar metrics in this way.
However, I think this is not a good idea.
class MyRedisClusterClient extends RedisClusterClient {
    @Override
    protected Partitions loadPartitions() {
        try {
            return timer.record(super::loadPartitions);
        } catch (Exception ex) {
            failed.increment();
            throw ex;
        }
    }
}

Teachability, Documentation, Adoption, Migration Strategy
I think there are many use case for this event.

Logging topology refresh.
Logging topology refresh failure.
Metrics for topology refresh latency.
Metrics for topology refresh frequency.

Inactive issue.


Password authentication

Do I read this right, and I'll need to put my account password into the config and disable MFA? There's so much OAuth fluff involved with getting a Teams app running, but at this crucial step we're supposed to throw it all overboard and have an unprotected account responsible for publishing new revisions of our app..?
Is this a temporary solution, or really the actual thing?

I would also really appreciate an answer to this question. In the readme it is suggested that login by device code will be supported in the future has there been any progress on that? Or are we still expected to disable MFA on an 365 account in order to deploy the Teams App?

I am actually deploying via Azure DevOps Pipelines, but as the documentation was very poor, I have used the readme from this Github action to help me figure out how to set this up.
After looking back over one of the samples for Azure Pipelines:
https://github.com/OfficeDev/TeamsFx/blob/main/docs/cicd/azdo/publish.yml
I notice there is a env var for CI_ENABLED with a comment # To enable M365 account login by non-interactive mode.
I wonder if that same env var can be used in this github action in order to enable deployment without having to disable MFA on the actual M365 account?
From the Azure Pipeline template example:
- task: Bash@3
  env:
    M365_ACCOUNT_NAME: $(M365_ACCOUNT_NAME)
    M365_ACCOUNT_PASSWORD: $(M365_ACCOUNT_PASSWORD)
    M365_TENANT_ID: $(M365_TENANT_ID)
    # To enable M365 account login by non-interactive mode.
    CI_ENABLED: 'true'
    # To specify the environment name which will be used as an option below.
    # You can change it to use your own environment name.
    TEAMSFX_ENV_NAME: 'dev'
    # To specify the version of TTK CLI for use.
    TEAMSFX_CLI_VERSION: 2.*
  inputs:
    targetType: 'inline'
    script: |
      set -evuxo pipefail

We have still not been able to get publish working on the pipeline, even with a non MFA account. Did you have your service principal the same account as the M365 accout? I have a separate SP and M365 account but constantly get an error Invalid Grant, with a message saying the username or password is wrong.
I had to publish it myself using the VSCode TeamsFX plugin.

We have a separate service principal, and an ordinary M365 user with limited privileges, but I made them an additional owner of the AAD app.
Here's our full deployment script, if that helps:
# For the magic variable, see:
# https://github.com/OfficeDev/TeamsFx/blob/80bb31043eba1dd0f434e1300ce0bdbf07d412f6/packages/cli/src/commonlib/m365Login.ts#L148C19-L150
export CI_ENABLED=true
export M365_TENANT_ID="${TENANT_ID}"
teamsfx package --env production --interactive false
echo 'Y' | teamsfx publish --env production --interactive false

Close this issue since this GitHub Action is no longer being maintained. Please follow this guide to setup CICD pipeline using CLI directly.