Autologin Feature

I would like to suggest a feature for an automatic login on the startup of the deskop app. E. g. Windows credentials could be used, or a "save password" feature.

Same from my side.
Default settings in the login are desirable in the DeskAPP. This is already possible in the WebAPP via a browser. Could a "remember password" function be set up? Or something similar that makes it easier for the user to log in?

No comments?

Community sites are monitored and/or acted upon on a best-effort basis (like in any open source project). For now, this feature won't receive priority.

Why does this feature not receive priority? User acceptance raises and falls with a convenient use, and logging in twice is not very convenient.  Even in kopano-desktop this feature is implemented since years.

I agree with that. From my point of view the DeskAPP is basically more important than the WebAPP, as it can be used in much the same way as Outlook. I also have to deal with several accounts with my customers, so Outlook is usually busy and the DeskAPP is therefore a great help.


test: http2-enable watcher and iso format logs

Description
Configures smoke watch controller to use http2 watch mode.
Relates to #1280
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Unit, Journey, E2E Tests, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

Successful smoke test w/ PEPR_HTTP2_WATCH env var set: https://github.com/defenseunicorns/pepr/actions/runs/11371525952

all tests have passed. We need this for the UDS Smoke test.


Update yaml

When updating yaml to v1.10.0 can't parse following code
empty block scalar: >

 # comment

See https://github.com/prettier/prettier/issues/8349

This is the expected behavior, see https://github.com/eemeli/yaml/commit/7eafeb821d4a89d4de26f5b3798ee6e009e99b12 and yaml/yaml-test-suite#37 for more info.

Thank  you.


Update access-control.md - Add AJO Category and Permissions with Corr…

…ect Description
Need to add a section for Journeys permissions as AJO Integrations with CJA prevent a user from accessing CJA Connections unless Journeys perms have been added when there are existing AJO Connections due to the integration.
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/access-control/privacy/ootb-permissions#:~:text=access to rules.-,Journeys,-Approve %26 publish Journeys

had to sign the CLA
-reopening now

Changes were copied over to the internal site,


How to get only console logs in output?

How to get only console logs in output?
Hi, currently I have set my logs to only log program output but I am still getting a lot of unwanted information. Is there a way to get just my logs and also none of the namespaces etc

Also is there an easy way like in Node.js to log in color without having to configure custom providers?

This issue was moved to aspnet/Extensions#1773


Build process does not place the kernel config (Image.config/bzImage.config) in the output directory

Since the nitro-cli build-enclave process expects to find an Image.config/bzImage.config in the NITRO_CLI_BLOBS path, it would be convenient if the default make target copied the as-built config into the output blobs path.

Verified that this works for both BUILD_ARCH=x86_64 make and BUILD_ARCH=aarch64 make, leaving the corresponding Image.config or bzIamge.config.


Add click option to layers control

Adds a click option to the Layers Control, which disables mouseover expanding and enables click expanding.
Layers control is collapsed on map click, which is the same behavior as on tablets.

Automatic click/touch expansion of L.Control.Layers has been implemented since this was reported.


Background music

There is no background music when you are on the start screen. It would be nicer to have some.

Then add some


closes #481: create initial doc structure in master

This PR adds the skeleton outline from the docathon to the master doc tree. It also streamlines the doc build process ('make docs' in the schemas root dir). Read the Docs automatically builds docs on commit. See ga4gh-schemas.readthedocs.org/.
Note that this PR includes only the top-level index.rst and intro.rst. Content from the docathon may be merged when it is finalized (perhaps selectively, by top-level doc area).
After this PR is merged:

Someone with github admin rights needs to update the RTD webhook.
I will selectively merge relevant changes from master into documentation.

@dglazer: Please review the above website to ensure that this fits with your expectation about changes to master and comment on this issue with feedback.

+1 -- this is a clear improvement over the (almost non-existent) doc infrastructure in master, and will make it much easier to incrementally merge in changes from the documentation branch.
A few small comments -- completely up to you which ones you want to address now, vs, in subsequent PRs:

doc/source/intro.rst isn't baked yet. I have a slight preference for just submitting a placeholder for now (like you do with the other sections), but I'm also okay with leaving it as is, since it's not bad, and we can iterate
the RTD website you link to (http://ga4gh-schemas.readthedocs.org/en/latest/api/index.html) doesn't seem to quite match this PR -- for example, I don't see a Schemas entry in the top-level ToC, and I don't see any sub-headings under the Appendix entry.
related -- I expected that RTD website to not only have a Schemas entry, but to have it auto-populated based on the .avdl in master. That wouldn't be great doc yet, but it would be current.

@diekhans: Please hold on merge. I'll address @dglazer's comments with an updated PR.

Explanation of updated PR:

Removed intro content. Can be merged anytime from documentation branch.

In sphinx, headings come from the target doc, not the index. If the target doc is missing, sphinx warns and omits it from the toc. This is why some toc elements were missing. (Others were missing because I had inadvertently omitted them.)

I added schema docs back as requested. NOTE: this means that the commit now includes the schema rst files, which in turn means that we are now on the hook for updating these files when the .avdls change. A note to this effect is now in doc/README.rst.

Thanks Reece -- most of these changes look like what I expected.
I'm confused about the schema docs, though, and might have sent us down a blind alley.

a) the first version of this PR had no schema docs
b) I pictured a version that would work like the documentation branch, with schema docs dynamically built from the .avdl (manually for now and automatically down the road). There wouldn't be any checked-in .rst files corresponding to the .avdl files, so doc/source/schema would be almost empty (as is https://github.com/ga4gh/schemas/tree/documentation/doc/source/schemas)
c) the current version of this PR has checked-in copies of snapshotted .rst files, presumably built from the current .avdl files in master

If (b) is doable, I still think it's best, since it puts us on a path to gradually improve the docs as we merge in improved comments on the .avdl. But if not, then I'd prefer (a), which is a subset of where we want to be, not (c), which creates a bunch of files we'll shortly want to remove.

I just created this PR against the documentation branch that removes the
pandoc dependency:
https://github.com/ga4gh/schemas/pull/483
I haven't merged it yet.  Dose it make sense to merge this into master
with #481 as well?
Mark

That depends - does it work with the existing .avdl files in master?

dropping pandoc works with existing .avdl, although there might some
formatting ugliness.
Although I though the goal was to get the tools merged, not all
the documentation working.
David Glazer<EMAIL_ADDRESS>writes:

That depends - does it work with the existing .avdl files in master?
—
Reply to this email directly or view it on GitHub.*

On Mon, Nov 9, 2015 at 5:31 AM, David Glazer<EMAIL_ADDRESS>wrote:

If (b) is doable, I still think it's best, since it puts us on a path to
gradually improve the docs as we merge in improved comments on the .avdl.
But if not, then I'd prefer (a), which is a subset of where we want to be,
not (c), which creates a bunch of files we'll shortly want to remove.

This explanation may help:
https://github.com/reece/schemas/blob/master/doc/README.rst.
RTD is simple: they run their installation of sphinx-build against a repo's
doc tree with the repo's conf.py. That's it. We don't get any other
official entry points. This implies that all files necessary for
documentation must be present in the commit.
I have confirmed that java is not available on RTD, which means that
on-the-fly conversion is not possible.
I have one strong and one weak opinion about our path forward.
The strong opinion is that RTD is a big enough win that we should make it
work and that there are acceptable options to substantially mitigate the
avdl-rst consistency issues (see below). If we don't make RTD work, we will
end up owning the entire doc build process, and that would be unfortunate.
If we agree that RTD is our target automated doc platform, then my weak
opinion is that we should proceed with the PR as-is. In the spirit of
constant, imperfect incremental progress, I'd rather have some schema
content with blemishes rather than none. (Actually, I have this feeling
about the rest of the pages too.)
I'm first in line for disliking checking in intermediates. This as a
stop-gap measure that moves the ball forward toward automated builds; it's
not a long term plan.
Here are 3 options to wean us off of the committing the intermediate doc
files:

Best option: UCSC's contractor is planning to build a sphinx domain
for protobuf. They could almost certainly arrange to build docs directly
from avdls, akin to the sphinx autodoc module that transparently builds
docs from .py files. This would be an elegant solution to the entire issue.
Another option is to write a test to check for avdl-rst consistency.
That would treat avdl-rst consistency kinda like unit tests and code style
compliance checks, and block code merges if they fail.
Mark floated the idea of building rsts on travis and pushing to a new
doc repo that would be picked up by RTD.

I personally don't like 3 for the same reason I think we shouldn't own the
doc build machinery.
-Reece

I completely agree with moving ahead and refining.  Also, RTD is
a great place to publish and the reference server is there.
Running a doc build as a temporary solution doesn't really worry
me all that much.  However, RTD is motivating for a common place
to find documentation (for Python people).
To eliminate Java in the Avro sphinx domain would require
writing a parser for avdl files.  I am loathed to spend
significant abouts of money on something that will be thrown
away quickly.  I don't think it's a three-hour job.  Plus it
will slow down the work on protocol buffers, since they are
resource limited.
I am only weakly against checking in the intermediates.  It's
more cruft and will show up in the code review process.  I guess
if they were automatically build every time a rst or avdl is changed,
they will end up in people's pushes and then not get stale.
My concern about travis is just that it might be annoying to get
it working, but it would work fully withing github/RTD and be
triggered by the original commit, so it seems different that
running out own build process.
By all means, charge ahead.   Any doc is an improvement.
Reece Hart<EMAIL_ADDRESS>writes:

On Mon, Nov 9, 2015 at 5:31 AM, David Glazer<EMAIL_ADDRESS>wrote:

If (b) is doable, I still think it's best, since it puts us on a path to
gradually improve the docs as we merge in improved comments on the .avdl.
But if not, then I'd prefer (a), which is a subset of where we want to be,
not (c), which creates a bunch of files we'll shortly want to remove.

This explanation may help:
https://github.com/reece/schemas/blob/master/doc/README.rst.
RTD is simple: they run their installation of sphinx-build against a repo's
doc tree with the repo's conf.py. That's it. We don't get any other
official entry points. This implies that all files necessary for
documentation must be present in the commit.
I have confirmed that java is not available on RTD, which means that
on-the-fly conversion is not possible.
I have one strong and one weak opinion about our path forward.
The strong opinion is that RTD is a big enough win that we should make it
work and that there are acceptable options to substantially mitigate the
avdl-rst consistency issues (see below). If we don't make RTD work, we will
end up owning the entire doc build process, and that would be unfortunate.
If we agree that RTD is our target automated doc platform, then my weak
opinion is that we should proceed with the PR as-is. In the spirit of
constant, imperfect incremental progress, I'd rather have some schema
content with blemishes rather than none. (Actually, I have this feeling
about the rest of the pages too.)
I'm first in line for disliking checking in intermediates. This as a
stop-gap measure that moves the ball forward toward automated builds; it's
not a long term plan.
Here are 3 options to wean us off of the committing the intermediate doc
files:

Best option: UCSC's contractor is planning to build a sphinx domain
for protobuf. They could almost certainly arrange to build docs directly
from avdls, akin to the sphinx autodoc module that transparently builds
docs from .py files. This would be an elegant solution to the entire issue.
Another option is to write a test to check for avdl-rst consistency.
That would treat avdl-rst consistency kinda like unit tests and code style
compliance checks, and block code merges if they fail.
Mark floated the idea of building rsts on travis and pushing to a new
doc repo that would be picked up by RTD.

I personally don't like 3 for the same reason I think we shouldn't own the
doc build machinery.
-Reece
—
Reply to this email directly or view it on GitHub.*

On Mon, Nov 9, 2015 at 10:49 AM, Mark Diekhans<EMAIL_ADDRESS>wrote:

To eliminate Java in the Avro sphinx domain would require
writing a parser for avdl files. I am loathed to spend
significant abouts of money on something that will be thrown
away quickly. I don't think it's a three-hour job. Plus it
will slow down the work on protocol buffers, since they are
resource limited.

Completely agree. In my "best option" suggestion re: the contractor, I was
referring to protobuf but inadvertently referred to avdls (I intended
.proto).
I also would not spend another moment even thinking about avdls if we're
committed to conversion (which I think we are).
I was trying to suggest that you (Mark) tack on to the existing contracting
engagement to build docs from protobuf definitions. This should be doable
and is probably even easy (but I don't know how!).
-Reece

Yes, protobuf domain will not be dependent on non-python code and it's
already part of the contract.
Mark
Reece Hart<EMAIL_ADDRESS>writes:

On Mon, Nov 9, 2015 at 10:49 AM, Mark Diekhans<EMAIL_ADDRESS>wrote:

To eliminate Java in the Avro sphinx domain would require
writing a parser for avdl files. I am loathed to spend
significant abouts of money on something that will be thrown
away quickly. I don't think it's a three-hour job. Plus it
will slow down the work on protocol buffers, since they are
resource limited.

Completely agree. In my "best option" suggestion re: the contractor, I was
referring to protobuf but inadvertently referred to avdls (I intended
.proto).
I also would not spend another moment even thinking about avdls if we're
committed to conversion (which I think we are).
I was trying to suggest that you (Mark) tack on to the existing contracting
engagement to build docs from protobuf definitions. This should be doable
and is probably even easy (but I don't know how!).
-Reece
—
Reply to this email directly or view it on GitHub.*

All sounds good -- we know where we're heading (with auto-built RTD docs
from .rst and .proto), and we have a plan for getting there (with the
contractor wiring up .proto -> RTD).
I'll defer to Reece and Mark on which intermediate steps move us there best
-- if checking in the generated .rst files for now is better than the
alternatives, fine with me.
On Mon, Nov 9, 2015 at 11:03 AM, Mark Diekhans<EMAIL_ADDRESS>wrote:

Yes, protobuf domain will not be dependent on non-python code and it's
already part of the contract.
Mark
Reece Hart<EMAIL_ADDRESS>writes:

On Mon, Nov 9, 2015 at 10:49 AM, Mark Diekhans<EMAIL_ADDRESS>wrote:

To eliminate Java in the Avro sphinx domain would require
writing a parser for avdl files. I am loathed to spend
significant abouts of money on something that will be thrown
away quickly. I don't think it's a three-hour job. Plus it
will slow down the work on protocol buffers, since they are
resource limited.

Completely agree. In my "best option" suggestion re: the contractor, I
was
referring to protobuf but inadvertently referred to avdls (I intended
.proto).
I also would not spend another moment even thinking about avdls if we're
committed to conversion (which I think we are).
I was trying to suggest that you (Mark) tack on to the existing
contracting
engagement to build docs from protobuf definitions. This should be
doable
and is probably even easy (but I don't know how!).
-Reece
—
Reply to this email directly or view it on GitHub.*

—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/schemas/pull/482#issuecomment-155156884.

I'd prefer committing the rsts, but not strongly. Mark, are you cool with keeping the rsts in now so that the docs are not completely barren? We can remove them when proto-to-rst is in place or earlier if you take on the travis build, whichever happens first.

Just bouncing ideas; I am totally cool with it!
it's certainly the approach that is the least work.
Another approach would be to keep the parse schema in json format
if that make it easier.
Reece Hart<EMAIL_ADDRESS>writes:

I'd prefer committing the rsts, but not strongly. Mark, are you cool with
keeping the rsts in now so that the docs are not completely barren? We can
remove them when proto-to-rst is in place or earlier if you take on the travis
build, whichever happens first.
—
Reply to this email directly or view it on GitHub.*

On Mon, Nov 9, 2015 at 1:11 PM, Mark Diekhans<EMAIL_ADDRESS>wrote:

Another approach would be to keep the parse schema in json format
if that make it easier.

I don't think so. If we're going to store an intermediate, it might as well
be a fully baked intermediate if you know what I mean.

@diekhans -- Planning on merging?

+1 this is great

+1, progress, hurray!


[Core] Remove some obsolete code

PR Details
Description
I've managed to remove some obsoletes and unused code in the Core module that did not require much refactoring to remove.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@manio143 Can my PR be merged now? Thanks


[iOS] leakage of confidential information

There is a security vulnerability where device tokens can be read from iOS device since it is stored in NSUserDefaults, particularly below file,
iOS/WindowsAzureMessaging/WindowsAzureMessaging/Helpers/SBLocalStorage.m
Any plan to fix this?

Push tokens are not considered sensitive. There are no plans to change the storage implementation at this time.


[Unit/Element transformation] translate/rotation value copy/paste buttons do nothing

repro is simple, select a unit or element, press "c" and then either move the unit/element you have selected and press "p" nothing will happen with translate, didn't test with rotation but i'm willing to bet the same thing happens.

More details I guess, Copying just copies "nil".

Should be fixed


Fix #99, Apply header guard standard

Describe the contribution

Fix #99

Testing performed
CI
Expected behavior changes
None
System(s) tested on
CI
Additional context
None
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB:2022-02-16 APPROVED


Compatibility issue between 2.0.0 and 3.0.0

Hi there are some signature incompatibilities between 2.0.0 and 3.0.0. Could you please provide a change log or something, so it would be easier to see what changed exactly between each version? I would be interested in contributing to the project in the future, but I would need some more clarity in the road map and planned features to set my self up. Thank you!
The signature issue was fixed by downgrading to from 3.0.0 to 2.0.0.
Related trace:
> make compile                                                                                [13:06:44]
elm make src/Server.elm --output build/Server.js
Detected problems in 1 module.
-- TYPE MISMATCH ------------------------------------------------ src/Server.elm

The 1st argument to `worker` is not what I expect:

38|     Webapp.Server.worker
39|>        { worker =
40|>            { init = init
41|>            , update = update
42|>            , subscriptions = subscriptions
43|>            }
44|>        , ports =
45|>            { writeResponse = writeResponse
46|>            , onHttpRequest = onHttpRequest
47|>            , onWebsocketEvent = \_ -> Sub.none -- onWebsocketEvent
48|>            , writeWebsocketMessage = \_ _ _ -> Cmd.none -- writeWebsocketMessage
49|>            }
50|>        , protocol =
51|>            { routeDecoder = routeDecoder
52|>            , updateFromRoute = updateFromRoute
53|>            , updateFromClient = updateFromClient
54|>            , serverMsgEncoder = Protocol.Auto.encodeProtocolMsgFromServer
55|>            , clientMsgDecoder = Protocol.Auto.decodeProtocolMsgFromClient
56|>            , headerDecoder = headerDecoder
57|>            , errorEncoder = Json.Encode.string
58|>            }
59|>        }

This argument is a record of type:

    { ports :
          { onHttpRequest :
                (
                Json.Encode.Value -> Webapp.Server.FrameworkMsg Msg x serverMsg
                )
                -> Sub (Webapp.Server.FrameworkMsg Msg x serverMsg)
          , onWebsocketEvent :
                (
                Json.Encode.Value -> Webapp.Server.FrameworkMsg Msg x serverMsg
                )
                -> Sub (Webapp.Server.FrameworkMsg Msg x serverMsg)
          , writeResponse :
                Request
                -> Response
                -> Cmd (Webapp.Server.FrameworkMsg Msg x serverMsg)
          , writeWebsocketMessage :
                Webapp.Server.Websocket.Connection
                -> Webapp.Server.Websocket.Key
                -> String
                -> Cmd (Webapp.Server.FrameworkMsg Msg x serverMsg)
          }
    , protocol :
          { clientMsgDecoder : Json.Decode.Decoder Protocol.MsgFromClient
          , errorEncoder : String -> Json.Encode.Value
          , headerDecoder :
                ServerState -> Json.Decode.Decoder Protocol.RequestContext
          , routeDecoder : Url.Url -> Maybe Route
          , serverMsgEncoder : MsgFromServer -> Json.Encode.Value
          , updateFromClient :
                Protocol.RequestContext
                -> Time.Posix
                -> Protocol.MsgFromClient
                -> ServerState
                -> ( ServerState, Task String MsgFromServer )
          , updateFromRoute :
                ( Method, Protocol.RequestContext, Maybe Route )
                -> Time.Posix
                -> Request
                -> ServerState
                -> ( ServerState, Cmd Msg )
          }
    , worker :
          { init : Flags -> ( ServerState, Cmd Msg )
          , subscriptions : ServerState -> Sub Msg
          , update : Msg -> ServerState -> ( ServerState, Cmd Msg )
          }
    }

But `worker` needs the 1st argument to be:

    { ports : Webapp.Server.Ports Msg x serverMsg
    , protocol :
          Webapp.Server.Protocol
              Msg
              x
              serverMsg
              clientMsg
              endpoint
              header
              ServerState
    , worker : Webapp.Server.PlatformWorker Flags ServerState Msg
    }

Hint: It looks like it takes too few arguments. I was expecting 1 more.

make: *** [build/Server.js] Error 1

Also it would be great to have tags or releases to be able to identify which commits to check out for specific versions.

Also the issue comes from the headerDecoder signature taking Posix -> ServerState -> Json.Decode.Decoder Protocol.RequestContext instead of the provided Protocol.RequestContext
Actual fix for 3.0.0:
headerDecoder : Posix -> ServerState -> Json.Decode.Decoder Protocol.RequestContext
headerDecoder p serverState =
    Json.Decode.oneOf
        [ Json.Decode.map Protocol.Cookied (Json.Decode.field "cookie" Json.Decode.string)
        , Json.Decode.succeed Protocol.Anonymous
        ]

Can you clarify why exactly headerDecoder need a posix argument in 3.0.0 compared to previous versions?

Thanks @medmouine for the prompt. I've written a release note for 3.0.0 https://github.com/choonkeat/elm-webapp/releases/tag/3.0.0 where I linked to freshly written comments wrt type signature changes in the commits.
Hope the notes helps 🙇

Can you clarify why exactly headerDecoder need a posix argument in 3.0.0 compared to previous versions?

The new Time.Posix argument holds the current time and is useful when you need to verify if the JWT has expired


Exposes FormProps to Consumer When Working with TypeScript

Are you submitting a bug report or a feature request?

I am not sure if this is the right repo for this but I really don't want to submit this issue to DefinetelyTyped  which has gazillion of things going on.
Consider the component below which is on TypeScript:
import * as React from 'react';
import { reduxForm, Field, FormErrors, FormProps } from 'redux-form';

interface FormData {
    name?: string;
    lastname?: string;
}

const validate = (values: Readonly<FormData>): FormErrors<FormData> => {
    const errors: FormErrors<FormData> = {};

    if(values.name === undefined) {
        errors.name = 'name needed';
    }

    if(values.lastname === undefined) {
        errors.lastname = 'lastname needed';
    }

    return errors;
};

interface SelectionWithFormProps {
    readonly value: string;
    readonly onChange: (val: React.ChangeEvent<HTMLSelectElement> | React.FormEvent<HTMLSelectElement> | string) => void;
}

class SelectionWithForm extends React.Component<FormProps<FormData, {}, {}> & SelectionWithFormProps, {}> {
    render(): JSX.Element {
        return

                <Field placeholder="First name" name="name" component="input" />
                <Field placeholder="Last name" name="lastname" component="input" />

                    <button className="button button--primary" type="button" onClick={this.props.handleSubmit}>
                        Provide full name
                    </button>

;
    }
}

export default reduxForm<Readonly<FormData>, SelectionWithFormProps, {}>({
    form: 'SelectionWithForm',
    validate: validate,
    onSubmit: (values, dispatch, props) => {
        console.log('submit is being handled...');
        props.onChange(values.name + ' ' + values.lastname);
    }
})(SelectionWithForm);

What is the current behavior?

When you try to consume this, you will see that redux form properties are also available to consumer:

which I imagine does not make sense and more importantly then IntelliSense, this effects the compilation, too.
What is the expected behavior?
I would expected it to just expose SelectionWithFormProps as the shape for valid props to pass through SelectionWithForm.
Sandbox Link

You can see the sample here: https://github.com/tugberkugurlu/redux-form-typescript-repro/tree/2f1ef56d3ac6c7d2df4dcba950f871fd72d8a925 follow the readme on how to get it up and running.
You should be able to open it up on VS Code to observe the IntelliSense behavior. You can also trigger the compilation through npm run build
What's your environment?

redux-form: 6.5.0
@types/redux-form: 6.3.2
typescript: 2.2.1
Node.js: 4.4.7

And yeah, one disadvantage of DefinitelyTyped is definitely the amount of things going on,
so nothing really stays up-to-date.
It would be amazing to have it maintained on our side (see #1211), because TypeScript is the most well-adopted typing variation of JS.
Unfortunately, there's nothing we can do at the moment, as no one here is maintaining that type file.


Move all logos from the root directory to a separate folder

I'm a novice in Godot source code, so I can only try the only possibility I think to fix CI errors

What's the motivation / proposal for this change?
The organization of files and folders in the repository is something that the maintainers take care of, so a first-time contributor proposing to move files around without justification is a bit difficult to review.

What's the motivation / proposal for this change?
The organization of files and folders in the repository is something that the maintainers take care of, so a first-time contributor proposing to move files around without justification is a bit difficult to review.

Sorry, I thought at first that the logo in the root directory was not used in src

maybe, close it?

I would close it for now yes.
For the record, we did discuss a while ago that some of the files in the root folder could be moved around to reduce the number of folders+files in the root, but that includes not only the logos but also some of the python files (and the LOGO license file I guess). I'll work on this at some point probably.


Alert and graphic in the same message ?

I haved configured the send of alerts with Telegram using the script "Zabbix-in-Telegram": https://github.com/ableev/Zabbix-in-Telegram.
But, I want know if is posible that the script send the graphic in the same message of alert and how I can do this. Today, the script  send the graphic after the alert and in a second message.

+1 on this

@hardwareadictos @lasilva19 RTFM.
zbxtg;single_message


Confirm Content from old Wiki is in new Pages - Attention: Need to delete unused field on dlrs__LookupRollupSummaryScheduleItems__c

https://github.com/SFDO-Community/declarative-lookup-rollup-summaries/wiki/Attention:-Need-to-delete-unused-field-on-dlrs__LookupRollupSummaryScheduleItems__c

Does not exist on the Pages site.

Transferred to FAQ page on new pages


fix: warning and code formatting on Autocomplete

Q
A

Bug fix?
no

New feature?
no

Issues
-

License
MIT

Fix broken formatting on https://symfony.com/bundles/ux-autocomplete/current/index.html#passing-extra-options-to-the-ajax-powered-autocomplete
Current result:

Follow-up of:

#1702

I fixed other issues with code formatting.

This is great, thanks Alexis!


[PE] Debug information

Hello,
Is it possible to add a keyword in PE module to target PDB path?
With possibly regex?
like:
rule my_program
{
    condition:
        pe.pdb.contains("\\path_to_the_program\\the_program.pdb")
}

yea its possible with CV_INFO_PDB70/20 :(, will someone do it? probs :D


doc: added description about versioning.

Now thumberd seems to not have own version by default.
BAC, Is using the following build-option premised?
-ldflags '-X main.version v1.3'

If so, I think it is good for non-golang-users to describe about it. How about you?

Thank you


View places on a map

Description:
View by region within a park
Eg: Garibaldi: a few specific regions within the park that are areas of focus eg: Rubble Lake, Diamondhead Parking lot leading to Elfin Lakes.
[Description of the ticket]
Acceptance Criteria:
Given
When
Then
Given
When
Then
Development Checklist:

[ ] Mobile Responsive
[ ] ...
[ ] ...

Dependencies

Blocked by
Blocking

Wireframe(s):
Workflows:
Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

Defining a site/place/area etc: a specified area in PPA, where the focus of this place is defined for recreation purposes


aragorn: fix build on darwin

Use environment-specified $CC for C compiler

Motivation for this change
ZHF 20.09 https://github.com/NixOS/nixpkgs/issues/97479
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

WFM macos 10.14, linux x86_64


Failed when running : dotnet build RideTheComet -t:Run -f net6.0-android

C:\Users\Gordon\Documents\Applications\Comet
λ dotnet build RideTheComet -t:Run -f net6.0-android
Microsoft (R) Build Engine version 17.2.0+41abc5629 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  Retrying 'FindPackagesByIdAsync' for source 'https://pkgs.dev.azure.com/dnceng/9ee6d478-d28
  8-47f7-aacc-f6e6d082ae6d/_packaging/825db618-e3eb-4426-ba54-b1d6e6c944d8/nuget/v3/flat2/xam
  arin.androidx.navigation.ui/index.json'.
  The SSL connection could not be established, see inner exception.
    Unable to read data from the transport connection: An existing connection was forcibly cl
  osed by the remote host..
    An existing connection was forcibly closed by the remote host.
  Restored C:\Users\Gordon\Documents\Applications\Comet\RideTheComet\RideTheComet\RideTheCome
  t.csproj (in 16.3 sec).
C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.301\tools\Xamarin.Android.Co
mmon.targets(521,3): error XA1018: Specified AndroidManifest file does not exist: C:\Users\Go
rdon\Documents\Applications\Comet\RideTheComet\RideTheComet\AndroidManifest.xml. [C:\Users\Go
rdon\Documents\Applications\Comet\RideTheComet\RideTheComet\RideTheComet.csproj]

Build FAILED.

C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.301\tools\Xamarin.Android.Co
mmon.targets(521,3): error XA1018: Specified AndroidManifest file does not exist: C:\Users\Go
rdon\Documents\Applications\Comet\RideTheComet\RideTheComet\AndroidManifest.xml. [C:\Users\Go
rdon\Documents\Applications\Comet\RideTheComet\RideTheComet\RideTheComet.csproj]
    0 Warning(s)
    1 Error(s)

Why does it ask projects to restore? I don't have any?

Oh I'm on either preview 3 or hopefully more likely the GA but who knows?

Make sure your on GA version of Maui. Also, check the nuget.config. Something is sending it to 'https://pkgs.dev.azure.com/dnceng/9ee6d478-d28
8-47f7-aacc-f6e6d082ae6d/_packaging/825db618-e3eb-4426-ba54-b1d6e6c944d8/nuget/v3/flat2/xam
arin.androidx.navigation.ui/index.json' I am pretty sure you don't need any of the preview things in the nuget.config anymore.

I have just abefore I saw Comet opened a stackoverflow post to find out how to work out what version of Maui I'm on. Thanks for your insanely quick replies, but here in the UK it's now the weekend... AND BEER :)

So you have something wrong with your nuget setup, I would delete the nuget.config if there is one, or remove some of your preview bits from the nuget sources.
Upgrade to the latest Maui, and you should be good.

Okay, two what seem to be obvious questions but for which I cannot find the answer.
How do I check the Maui version I'm on?
How do I upgrade?
I use Visual Studio and I'm on 2022 community edition 17.3.0 Preview 1.1. I use Visual Studio Installer to check things, but all seems good.
Sorry, but probably a noob question, but I am new to this and just feeling my way around :)

@Redth ^^

Okay, two what seem to be obvious questions but for which I cannot find the answer.
How do I check the Maui version I'm on?
How do I upgrade?
I use Visual Studio and I'm on 2022 community edition 17.3.0 Preview 1.1. I use Visual Studio Installer to check things, but all seems good.
Sorry, but probably a noob question, but I am new to this and just feeling my way around :)

dotnet workload update

Ok so
λ dotnet workload update
No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.
Skipping NuGet package signature verification.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.workload.emscripten.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.sdk.tvos.
Updated advertising manifest microsoft.net.sdk.maui.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.workload.mono.toolchain.
No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.

Successfully updated workload(s): .

Then
 dotnet new -i Clancey.Comet.Templates.Multiplatform
The following template packages will be installed:
   Clancey.Comet.Templates.Multiplatform

Clancey.Comet.Templates.Multiplatform is already installed, version: 0.4.344-beta, it will be replaced with version .
Clancey.Comet.Templates.Multiplatform::0.4.344-beta was successfully uninstalled.
Success: Clancey.Comet.Templates.Multiplatform::0.3.45-beta installed the following templates:
Template Name        Short Name  Language  Tags
-------------------  ----------  --------  -----------------------------------------------
.NET MAUI Comet App  comet       [C#]      Comet/MAUI/Android/iOS/macOS/Mac Catalyst/WinUI

Then
λ dotnet new --install Clancey.Comet.Templates.Multiplatform::0.4.344-beta
The following template packages will be installed:
Clancey.Comet.Templates.Multiplatform::0.4.344-beta
Clancey.Comet.Templates.Multiplatform is already installed, version: 0.3.45-beta, it will be replaced with version 0.4.344-beta.
Clancey.Comet.Templates.Multiplatform::0.3.45-beta was successfully uninstalled.
Success: Clancey.Comet.Templates.Multiplatform::0.4.344-beta installed the following templates:
Template Name        Short Name  Language  Tags

.NET MAUI Comet App  comet       [C#]      Comet/MAUI/Android/iOS/macOS/Mac Catalyst/WinUI
Then

λ dotnet new comet -n RideTheComet --force
The template ".NET MAUI Comet App" was created successfully.

Yay, I'm away for the ride - when I get a mo :)

Thanks all


SignUp bug -Error with a  strange error message.

Preflight Checklist

[ ] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Describe the bug
There was a strange bug that  occured when i tried to sign up.
I was not able to signup for some unknown reason, and the error message that i got was bit strange -
it stated " permission denied for table auth_user".
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

Add additional instructions and considerations for the assignee

[ ] Jupiter

[ ] Saturn

[ ] Neptune

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here (include commit numbers and branches if relevant)

@Gagan-Saffron I guess this is regarding some problem in the backend.

@Gagan-Saffron
thanks for reporting this issue !
Can you refer to the contribution guidelines, you forgot to add this to the project board and you didn't follow the issue template ! (steps to reproduce, expected behavior ...)

I think this was related to the heroku database hitting a limit.  Closing unless we see this error again


New Language Grammar contribution Pine Script

https://github.com/jeyllani/highlightjs-pine

Changes

Added entry into SUPPORTED_LANGUAGES.md
Updated CHANGES.md
Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md

Is it possible to request a repo to host this grammar ?


DuplicatedByteBuf is deprecated

Expected behavior
No warnings during build.
Actual behavior
[WARNING] /Users/masakazu/git/pulsar/pulsar-common/src/main/java/io/netty/buffer/RecyclableSlicedByteBuf.java:[69,37] [deprecation] DuplicatedByteBuf in io.netty.buffer has been deprecated

Steps to reproduce
mvn install -DskipTests

System configuration
Pulsar version: master c51eaad
OS: macOS 10.12

We may be able to get rid of RecyclableSlicedByteBuf if we upgrade Netty to 4.1.
https://github.com/apache/incubator-pulsar/pull/679#issuecomment-321988130


Missing interpretation for std::map<std::string, TVector3>

Not sure if this is really something missing or an issue on my side, I expect TVector3 to be sufficiently standard that it should work.
Here is a sample file:
https://www.dropbox.com/s/f1x6xvro5fq03g1/uproot_issue_tvector3?dl=0
It is in the Model tree, branch Model.scoringMeshTranslation.
Thanks for the help on this!

It's not on your side—TVector3 is standard, but generic std::map (for any contents) has not been implemented. Your sample file will help with implementing it, though! (Until now, I've only seen examples of maps of strings, and strings are a special case, not generalizable. I'll have to get past a few deadlines before I can work on it though, and it will probably only go into Uproot4 because that's where the main-line development is now.)

Is uproot4 already usable? Should I make the switch to anticipate this?

The goal is to have it ready by the beginning of July. That date is a little uncertain, but it will be close.
Since Uproot 3 → 4 is a big upgrade like Awkward 0 → 1, I'm doing the same thing of giving it a different package name, making it possible to use both in the same Python process, which could be necessary if some things in the new library don't work right away or old scripts need to be converted.
This tutorial on Uproot mixes in some Uproot 4 examples. It's in a state where we can read jagged arrays from TTrees, though it's still unfinished in many ways (reading objects from TTrees, for instance).

It's a card in the new project: https://github.com/scikit-hep/uproot4/projects/1#card-40289893

This is finished in Uproot4: https://github.com/scikit-hep/uproot4/blob/fd823404093a3bae0b664665e724400add5ebb2e/tests/test_0034-generic-objects-in-ttrees.py#L1244-L1295


Implement /wd/hub/session/:sessionId/element/:id/rect endpoint for better compatibility with Selenium 3

Selenium 3 introduced new mandatory element property called rect. This PR adds the properly to Selendroid

Thanks for taking a stab at this :)
I added a couple of comments

@marcelogomez This PR was created more than half a year ago. It looks like the project is not maintained for quite a while. Do you plan to support it in the future? Are there better alternatives?


libbpf: 0.8.1 -> 1.0.0

Description of changes
Update libbpf to the latest release.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @thoughtpolice @vcunat @martinetd

Please wait with this.

All deprecated APIs and features removed!

This means IIRC that what they moved to libxdp is gone now, but we don't package libxdp yet.  Example breakage: knot-dns build.

Cross-ref: https://github.com/xdp-project/xdp-tools/issues/220

Thanks @vcunat! It looks like you're working on libxdp (they were fast fixing that particular error!) so leaving follow up to you, but please ask if there's anything actionable for others :)

Multiple packages have issues building, apparently:

[ ] knot-dns: that's for myself and upstream colleagues, WIP
[ ] pahole
[ ] bcc
[ ] bpftrace? (hidden by bcc)
[ ] suricata

bcc -> ah, that'd be why upstream released 0.25.0 probably... unfortunately that breaks bpftrace in turn; this hasn't been fixed upstream and I'll get around to it eventually but I didn't go as far as to check libbpf 1.0...
pahole -> I'll have a look

pahole 1.24 got released last week and builds fine with libbpf 1.0.0 -- on the other hand it does not build with libbpf 0.8.0 (btf.h too old) so we need to upgrade both together.
@saschagrunert can you pick https://github.com/NixOS/nixpkgs/compare/master...martinetd:nixpkgs:libbpf_1.0 up ?

Rebased on top of the latest master branch.

@martinetd: the point was to add the pahole update which is not in nixpkgs master.

(Sorry I meant to link to https://github.com/martinetd/nixpkgs/commits/libbpf_1.0 -- doesn't change much anyway; as pointed out that's not in master yet because it wouldn't work here on its own)
I can also confirm bcc 0.25.0 works with libbpf 1.0.0 -- this one also compiles with libbpf 0.8.1 (positively surprised here!) so I can open a separate PR for it as soon as I got bpftrace sorted out to work with it; although we can also group it together with this I have no preference.
(I'd also like to upgrade the llvm toolchain used for bcc/bpftrace while we're doing this -- llvm 11 is getting a bit old and while it appears to work I'd be more comfortable with llvm13... and -that- definitely belongs in a different PR... It's just a matter of specifying llvmPackages = llvmPackages_13 in all-packages. But as long as the newer version works I see no reason to push for this here; will do that after bpftrace fix)

I prefer to decouple PRs, unless there's some particular reason.  (generally and here I can't see any such reason)

makes sense to me.
for bpftrace: https://github.com/iovisor/bpftrace/issues/2340
tl;dr -- the master branch there does build with bcc 0.25.0 as they removed the dependency on the problematic function, but it's a huge step from bpftrace 0.15.0 so I'm a bit reluctant to go with it unless they cut a new version tbh.
I also have a patch that fixes it for 0.15 before checking master branch was completely different, so we can go with that if that looks better...
Either approach should work fine with older libbpf as well, so no problem with doing that in another PR -- I'll open one once I get a reply from upstream about a new release.

It seems, systemd has no support for libbpf v1.0.0 yet:
https://github.com/systemd/systemd/blob/1a0e065e9f154f46fd68cd45f46310bc7df7a51c/src/shared/bpf-dlopen.c#L49

It seems, systemd has no support for libbpf v1.0.0 yet:

Good point; I had a quick look at the symbol list and it's not just bumping the soname: bpf_create_map, bpf_map__resize, and bpf_probe_prog_type got removed.
Can you/do you want to open an issue in their repo?
In the meantime I'm starting to think we might want to just add libbpf 1.0.0 as a new package and let people pick one, that should allow a smoother transition....

In the meantime I'm starting to think we might want to just add libbpf 1.0.0 as a new package and let people pick one

Yes.  Or at least when someone appears who can benefit from upgrading to >= 1.0.0.

bpftrace 0.16.0 got released just now so opened https://github.com/NixOS/nixpkgs/pull/189078 for it. It works with older libbpf as expected, so can be done separately and we'll just have to rebase.
That leaves knot-dns, systemd (just replied in that issue, thanks @veehaitch ) and.. suricata ?
@magenbluten (suricata maintainer) as he wasn't part of this issue until now.
Unless we want to just leave both as previously suggested and move forward; I don't need anything in libbpf 1.0 at this point.

closing as https://github.com/NixOS/nixpkgs/pull/193591 got merged

Update for the dependencies above: https://github.com/NixOS/nixpkgs/pull/187978#issuecomment-1227122103

suricatta got merged in another PR a couple of weeks ago, but only in their master branch so that'll require a backport to their 6.x branch if we want an update; I don't think there's any hurry though so won't bother asking
systemd merged my PR and it's in v252-rc1; they plan on backporting it to stable after it's had some testing on master (probably after release?) so we'll get it sooner or later as well now

I don't think there's any hurry for these; but I'd like to get pahole in ( https://github.com/NixOS/nixpkgs/pull/194551 ) as it's had some nice performance improvement through parallelism of the BTF encoder if one of you could take a look :)


WIP: Card expandable component

This Pull Request meets the following criteria:

[ ] Tests have been added/adjusted for my new feature
[ ] New Components are registered in index.js of my project

Closes #261

Closing on behalf of #515


rewrite new lyrics style

dynamic brightness (now for real) and saturation, new track change animation (now without artifacts), better overall performance (visibility hidden -> display none) and other minor changes

need feedback on saturation filters

need feedback on saturation filters

need feedback on saturation filters

looks nice @SunsetTechuila !
are we ready to merge your work?
i looked into the code and tested. everything seems fine

No oversaturated or undersaturated backdrops?

No oversaturated or undersaturated backdrops?
its the most suitable amount to me.

are we ready to merge your work?

now we can

done @SunsetTechuila ❤
nice work


Toggleable UI Elements For Twitch

We essentially need two menus, one listing the active chat (and viewers), that submits chat messages when they're submitted in game. Garry has some decent examples for this.
We also need a list of commands chat can look at, what form this takes necessarily is up to interpretation but perhaps a scrolling list would work. Or a list for chat vs bits/subscriber commands.

@Geeknerd1337 most obs streamers have the chat logs already?


CMS messages and Django messages

I am not sure that using Django's messages for CMS is a good idea since they get rendered in two places -- by CMS toolbar and in site templates.
What was the reasoning behind using them?

We are still successfully using the django messaging system and there is Cl.API.Message() to open a message within the toolbar


Implement the overall report endpoint

POST
/admin/widgets/main
Params
start_date=2017-01-01 00:00:00&end_date=2017-12-31 23:59:59&group=month&all=0
So library needs to accept dates, and a group by option.

completed


New Tips: Frontend performance

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:  all for it!!
Thanks for the daily stuff till now!! was waiting daily for it :smile:

:+1:

:+1:

:+1:

:+1:

👍🏻

:+1:

:+1:

👍🏻

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

+1

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

+1

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

👍

:+1:

:+1:

:+1:

:thumbsup:

:+1:

:+1:

:+1:

:+1:

:+1:

👍

:+1:

:+1:

:+1:

:+1:

👍

👍

👍 (going through all the tips, so awesome!! Thank you so so much for doing this, super helpful :))


Can I use React as front end then Laravel as backend? The source files will be pulled from the Gitlab.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
ap-southeast-2
Amplify Hosting feature
Backend builds
Question
Can I use React as front end then Laravel as backend? The source files will be pulled from the Gitlab.
Is that possible in Amplify?
My React files are already deployed in amplify but I do not know how to connect my Laravel files.  Can the Amplify CLI help with that?
My React and Laravel files are separated. Each one is in a folder.
Thank you.

Hi @drdrie thank you for opening this issue. Currently you are able to deploy your react app/front end on hosting and are able to use any backend via the use of APIs. Since you mentioned Laravel for you backend, you can hosting that somewhere else, such as in an EC2 and then connect it to your front end hosted on Amplify via APIs.
Let me know if you have any more questions.


Review "Power Cycle Uptime" plugin, consider extending to support additional filters

Perhaps the plugin can be modified to accept a list of systems to be checked, instead of a list to not be checked?

This will be resolved once #896 is implemented.


NOTICK: Fixup virtualnode exception handling

I wonder if we should add some unit and/or integration tests to ensure that we are indeed handling short hash Id passed in the wrong case and non-existent ids correctly?

I wonder if we should add some unit and/or integration tests to ensure that we are indeed handling short hash Id passed in the wrong case and non-existent ids correctly?

Yep agreed can do


Doesn't work anymore?

hello, I wanted to inform you the plugin doesn't work anymore

Hi, what platform are you running on and which version of RemNote are you using? Also, which version of the plugin are you using?


Fix transform not being run

Changelog

Revert the revert. Let me know if there's a better way.
Fix issue with transform function resolution in createExplorer.js, details below
Add test for transform option

Details
The transform function was not being resolved correctly - lib/createExplorer.js#L16
Here's a simple demo for what was going wrong:
λ node
> let sync = false

> 'someValidFunc' || (sync) ? 'identitySync' : 'identityPromise'
'identitySync'

> 'someValidFunc' || (sync ? 'identitySync' : 'identityPromise')
'someValidFunc'

And because the loaded config was not being transformed properly, stylelint was breaking(stylelint/stylelint#2768).
Closes #72

@davidtheclark travis build did not run for this.. And in travis build requests, I can see 'Build type disabled via repository settings (pull_request).' Should we enable builds for PRs again?

Yes let's switch that back on in Travis. I did a t mistakingly.

Yes let's switch that back on in Travis
Done.

One more thought: Can we add a test to ensure that if your transform function errors, those errors make it through, aren't swallowed up?

Can we add a test to ensure that if your transform function errors, those errors make it through, aren't swallowed up?

Okay. I'll do that as well.

After doing the changes for node 4, I'd like to improve tests as well. I am considering using jest and adding integration tests with stylelint plus code coverage.

I am considering using jest and adding integration tests with stylelint plus code coverage.

Yeah, I've been using Jest a lot lately and really liking it. And integration tests would be awesome.

@sudo-suhas: If you are planning on working on these refactors soon, I'm thinking we should hold off on releasing this sync feature for now and then do a major release that includes all the changes. Dependents like stylelint then would not be caught off guard, and if the refactoring introduces any other problems they will not be automatically introduced to end users.

@davidtheclark I am in two minds about this. What you are suggesting does make sense. However, #68 was a rather important fix no? I was planning to work on the refactors over the next week or so. You can take a call on this.

@sudo-suhas: We could release just that fix. I can do this today.

The first commit of this PR, a revert commit, includes the changes for that fix. It should be enough to rebase right?

Just released 2.2.2 with the --config fix. If you rebase your branch and fix any commits, it should be fine, I think.

Surprisingly, conflict only in the changelog.
A small clarification, in the changelog, for v2.2.1, it is denoted as 2.2.0-1. Is this intentional?

I adjusted the notation to 2.2.0, 2.2.1.

Also, shouldn't the changes available in 2.2.0 be listed?

I don't know ... I feel like that was just a flawed release that should not be used. That's why I grouped those two releases into one entry.

Yea, Okay 👍

@davidtheclark I had noticed that you usually squash and merge PRs. If we were to do for this one, it will be difficult to track the actual changes(other than revert). Should I merge the rest of the commits locally?

You can use rebase & merge if you like your commit history!  I like rebase & merge if the commit history is clear.

@davidtheclark I am regretting having merged this in. Should we create a 3.0 branch and have all refactoring there instead? I could cherry pick the changes in this PR to that and you could force push master to 69b4cb6b.

@davidtheclark One last thing. I think until 3.0 branch is ready and merged in, the readme should accurately reflect the state of the last release. So shall I add a PR reverting this one or can you force write HEAD to  69b4cb6. While I know that force write is generally frowned upon, in this case, I just want to avoid the noise of revert*3.

the readme should accurately reflect the state of the last release

I don't think we have to worry that much about it. This situation is pretty standard. We could add a note to the top of the readme saying it reflects master here's a link to the README for a previous version. I'd rather do that than Git magic.

Alright 👍 I'll defer to your better judgement and experience here


Specify supported node versions in package

cf. https://docs.npmjs.com/files/package.json#engines
cf. https://developer.ibm.com/node/2017/02/23/node-js-versions-supported-node-application-metrics-versions-4-6-7-remain-supported-support-versions-0-10-0-12-5-dropped/
Its only advisory, but it makes it clear in the package what the support policy is.
/cc @NikCanvin

LGTM


Fix path for swagger-ui

LGTM

This is what I see on a v0.15.0 cluster:
arob@k8s-v15-master:~$ curl localhost:8080
{
  "paths": [
    "/api",
    "/api/v1beta1",
    "/api/v1beta2",
    "/api/v1beta3",
    "/healthz",
    "/healthz/ping",
    "/logs/",
    "/metrics",
    "/static/",
    "/swagger-ui/",
    "/swaggerapi/",
    "/validate",
    "/version"
  ]
}arob@k8s-v15-master:~$ curl localhost:8080/swaggerui
Moved Permanently.

arob@k8s-v15-master:~$

I changed /swaggerui (wrong) to /swagger-ui (right).

Ugh. Thanks. That's inconsistent with the line I cited, which should be changed to match or removed if unnecessary.
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/ui/installsupport.go#L45
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/master/master.go#L560
@nikhiljindal


Setup Linters

Description
This PR involved the installation of the linters and the necessary dependencies required by the project.

Hi @MenendezON and @iankiema
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
STATUS: APPROVED 🟢
Congratulations! 🎉


udpate references docs page

this should fix some display issues with this page

so far this doesn't fix it

Closed in favor of #2185


Refactor move file

I want to move file to another location but there is no way :(
like: https://www.jetbrains.com/idea/help/move-refactorings.html

???

This issue was moved to Microsoft/TypeScript#6487

this looks like a general suggession and not limited to sublime-text. moving to the ts repo.
and to answer @tamascsaba question, this is a feature that is not supported at the moment you will need to manually move the file and fix your references/imports acaccordingly

Thanks, for the answer.


adding the logging variable allowClusterResourcesFromAllNamespaces

Q
A

Bug fix?
no

New feature?
yes

API breaks?
to check

Deprecations?
no

Related tickets
fixes #X, partially #Y, mentioned in #Z

License
Apache 2.0

What's in this PR?

Why?

Additional context

Checklist

[ ] Code meets the Developer Guide
[ ] User guide and development docs updated (if needed)
[ ] Related Helm chart(s) updated (if needed)

To Do

[ ] If the PR is not complete but you want to discuss the approach, list what remains to be done here

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alex Vaque seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add note about limitations of the gen-ssl-key-cert

Coverage decreased (-0.05%) to 61.575% when pulling 63ea33f56a1d52a75c6dd0c3035f5191b773ad19 on add-note-to-script into 6bd4a245f1dc210d04085664e70a0a66c978bf88 on master.

I think it makes sense to makes this clear in the README documentation as well and perhaps add documentation on how one can test this without ooni-probe.

Can we merge this? I think it's better than nothing.

Sure, merging.


The app always exit when I press back in any view

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.24 (v3 is not supported)
react-native v0.51.0

Expected behaviour
Don't exit the app and  return to the previous view and push the views correctky
Actual behaviour
There is no actual animation when I'm opening a new view with push, and when I press back the app always exit at any point.
<Router createReducer={reducerCreate}>
  <Stack key='main'>
    <Scene key='splash' hideNavBar='true' type={ActionConst.REPLACE} component={Splash} />
    <Scene key='signup' hideNavBar='true' type={ActionConst.REPLACE} component={SignUp} />

    <Drawer
      hideNavBar
      key='drawer'
      contentComponent={SideMenu}
      drawerImage={require('./assets/images/icons/menu_trigger.png')}
      drawerWidth={300}
      drawerOpenRoute='DrawerOpen'
      drawerCloseRoute='DrawerClose'
      drawerToggleRoute='DrawerToggle'
    >

      {/* Home Tabs */}
      <Tabs
        key='home'
        tabs
        tabBarStyle={styles.tabBarStyle}
        hideNavBar='true'
        showLabel={false}
        tabBarPosition='bottom'
        titleStyle={titleStyle}
        navigationBarStyle={navBar}
        onRight={() => Actions.push('filter')}
        rightButtonTextStyle={filterTextStyle}
        hideBackImage={true}
        leftButtonImage={require('./assets/images/icons/menu_trigger.png')}
        rightButtonImage={require('./assets/images/icons/filter_icon.png')}
        activeBackgroundColor='#262a62'
        inactiveBackgroundColor='#444881'
        lazy
      >
        <Scene
          key='businesslist'
          component={BusinessList}
          icon={TabIcon}
          title='🏬 Negocios'
        />
        <Scene
          key='featured'
          component={Featured}
          title='♥ Destacados'
          icon={TabIcon}
          passProps={true}
        />
        <Scene
          key='events'
          component={Events}
          title='🎉 Eventos'
          icon={TabIcon}
          passProps={true}
        />
      </Tabs>

      <Scene
        key='business'
        component={Business}
        getTitle={props.title}
        navigationBarStyle={navBar}
        titleStyle={titleStyle}
        navBarButtonColor='#FFF'
        passProps={true}
        renderLeftButton={() =>
          <TouchableOpacity onPress={Actions.pop}>
            <Feather style={styles.leftButton} name='x' size={30} color='white' />
          </TouchableOpacity>
        }
        onLeft={Actions.pop}
      />

      <Scene key='contact' hideNavBar='true' backTitle={'Regresar'} component={Contact} passProps={true} />
      <Scene key='tutorial' hideNavBar='true' backTitle={'Regresar'} component={Tutorial} passProps={true} />
      <Scene key='filter' component={Filter} passProps={true} navigationBarStyle={navBar}
        title={'Filtros de búsqueda'}
        titleStyle={titleStyle}
        leftButtonImage={require('./assets/images/icons/close_icon.png')}
        onLeft={Actions.pop}
        type={ActionConst.REPLACE}
      />
      <Scene key='team' hideNavBar='true' backTitle={'Regresar'} component={Team} passProps={true} />

      {/* Gifts Tabs */}

      <Tabs
        key='gifts'
        tabs
        tabBarStyle={styles.tabBarStyle}
        showLabel={false}
        tabBarPosition='bottom'
        titleStyle={titleStyle}
        navigationBarStyle={navBar}
        hideBackImage={true}
        leftButtonImage={require('./assets/images/icons/menu_trigger.png')}
        activeBackgroundColor='#262a62'
        inactiveBackgroundColor='#444881'
        type={ActionConst.PUSH}
        lazy
      >
        <Scene
          key='allgifts'
          component={Gifts}
          icon={TabIcon}
          title='🎁 Regalos disponibles'
        />
        <Scene
          key='mygifts'
          component={MyGifts}
          title='🎁 Mis regalos'
          icon={TabIcon}
          passProps={true}
        />
      </Tabs>
    </Drawer>
  </Stack>
</Router>

This is my index.android.js
render() {     return (       <Router />     );   }

You need to handle to BackButton within your Router, just add this where you implemeted it :
  onBackPress() {
    if (Actions.state.index === 0) {
      return false
    }
    Actions.pop()
    return true
  }

...
...
<Router
  backAndroidHandler={this.onBackPress}
  createReducer={reducerCreate}>

If you want to do more about the transitions, please check #2628

Thank you, now it's working!
But I still have the issue regarding the push of the views... the views aren't being pushed, looks like they are being replaced because there is no animation and when I go back after "push" 2 views, it's returning to the home and not to the previous one.

If you want to do more about transitions, please have a look at #2628, it will help you with this!
The other part with returning to home when pressing backButton is weird.. I see you already implemented the routerReducer, have a look at the logs : is there a list of routes similar as it should be with what you are doing in your navigation logic?

The issue I have began when I change from react-native-drawer to use the Drawer of this package, as you can see my index.android.js contains only this render() { return ( <Router /> ); }.
My logs are showing that I'm pushing the views not replacing them.
And in order to load the home of my app, I'm loading a very first Scene which is the splash
<Scene key='splash' hideNavBar='true' type={ActionConst.REPLACE} component={Splash} />
In that Component I'm reseting to drawer to avoid the user perform back in home and return to the splash scene with this
Actions.reset('drawer')
Probably I'm making a mistake there.
What do you think?


Crash or hanging problem!

hi,
Howto reproduce this problem:

open some big contents text file(over 5000 lines or more..for example..)
and type the following text at the end. ("blabla.bla")
delete each character from the end. then always before ".", it hangs or not responsible.

if i turn off highlight-line package, then there is no problem.
please fix this Issue..
OS: Windows 8.1 Pro
Atom version: 0.201.0
Thank you,
Best Regards,
kleinstein.

oh i'm very sorry.
it's not highlight-line. it was because of highlight-selected.
sorry. i close this issue..


Sending two messages at the same time

Please describe your problem in as much detail as possible:
    .on("playSong", (message, queue, song) => message.channel.send(
        `Playing \`${song.name}\` - \`${song.formattedDuration}\`\nRequested by: \`${song.user.tag}\``
    ))
    .on("addSong", (message, queue, song) => message.channel.send(
      `Added \${song.name}\` - \`${song.formattedDuration}\` to the queue by \`${song.user.tag}\``
  ))

when ever a song is added to the queue or it is playing it will add one more message each time it plays
Further information:
for example
adds song to queue
bot : added to queue
adds song to queue again
bot : added to queue
bot : added to queue
and so on and every time it is increased by one

DisTube version: 2.8.18
discord.js version: 12.5.3
Node.js version: 14.17.6
Operating system: windows 10

I highly recommend to use distube@v3-beta with discord.js@v13

this is discord.js@12

Because the listener is run multiple times


Setting to show Source Control Provider even for single repository

Closes #38785
Signed-off-by: Shivam Mittal<EMAIL_ADDRESS>

Thanks! 🍻
Renamed the setting to scm.alwaysShowProviders.


Editing a monograph with a section causes the monograph to be inaccessbile

To Reproduce:

Create a new monograph without attaching a file
Add a section to that monograph
Edit the monograph
Get redirected to a 404, "The page you were looking for doesn't exist."

It's still in the solr index, you can still see the monograph in search results, but the show page 404s.

Can someone try to reproduce this? Maybe it's just too late on a Friday for me to think straight

I just tried this. If I follow your instructions exactly, it works fine. But the first time through instead of editing the monograph, I edited the section, and I noticed that on the edit page the monograph got removed. Is it possible you edited the section instead of the monograph?
The monograph-for-this-section reverting to blank is something we should fix.

Hm, nope, I can't reproduce this. In trying to reproduce it, I created three links to the same section in my test monograph:

Paired up with Seth today. I am able to reproduce this bug on the DCE sandbox with the current tip of master (34a5a78) deployed. When I was unable to reproduce it we had 24191b4 deployed. Gist of the production log when I try to access the monograph:
https://gist.github.com/acozine/3b4c7433b9402945ed08350b359c2f54

I've looked into this some more. The key seems to be that on a Monograph edit page, there's a dropdown menu called "Representative Media". Currently it's populated with both Sections and FileSets. If the Monograph has no representative file (so no FileSets), then one of the Sections will be the default. When the edit is saved, the section's id is now the monograph's representative id. But a Section is not a FileSet so I guess bad things happen.
We can override CC's defaults and only let a Monograph's FileSets, not Sections, be in this Representative Media dropdown.

But do we want this?

Do we want to include all of the Monograph's Section's FileSets as an option, not just the Monograph's FileSets?

Maybe something like this in /app/forms/curation_concerns/monograph_form.rb
    def select_files
      # We only want FileSets here, not Sections
      # Use model.file_set_ids, not model.member_ids
      file_sets ||=
            PresenterFactory.build_presenters(model.file_set_ids, FileSetPresenter, current_ability)
      Hash[file_sets.map { |file| [file.to_s, file.id ] }]
    end

I think for this bug it's ok to punt on the larger question, we can always make a new story later. For now only the Monographs's files (FileSets) will be in the Representative Media drop down.


Add descriptors to generated protos

There is a great deal of information in the descriptors that unfortunately is lost with the current approach.
Most protubuf libraries provide access to the raw descriptors, this PR brings this lib inline with that philosophy by
adding the encoded descriptor to the generated modules and exposing them via a descriptor function.

Ping. Any movement here?

This PR provides a needed public interface for type introspection via the descriptor functions. My project has previously been using the non-public and undocumented __message_props__, but this approach has the obvious downside.

One other consideration is whether to update tony612/google-protos so that the .pb.ex files there also have descriptor functions.

In fact, I don't really want to merge this PR because the generated code is redundant and I guess most people won't use descriptor function. If you want to get some metadata, you can use the __message_props__ function. Could you explain your use cases?

The message_props loses a lot of information. Any custom options that are provided to a field or method are lost, even the json name option is not present. These extensions are often critical when building applications where options are used. Providing the descriptor in this way you get:
1: free support for any and all new options (including custom options)
2: a public API to get at this information described in protos
We've built heavily on this lib because we thought it is great but the lack access to the descriptor has made building tools with it very challenging.
We've been unable to correctly use json names, access options related to Kafka event definitions, graphql annotations, http related options, permissions. There are many options to use (custom defined). If not by exposing the descriptor, how will this lib support accessing those?

Protobuf libraries in almost every other language allow you to pull out custom options.
👍 to the Kafka & JSON name use cases.

As an example of what bit me today... I want to use Jason to serialize these protocol buffer messages so I want to implement a protocol impl for each one. We use the standard json_name option in some places to specify what name we use but in most place we just want the normal camel casing. The json name option being unavailable means I can't fall back to the descriptor. Since this has lost fidelity in this way it is impossible for me to create tools based on this lib to generate compatible json representations.
If I had the descriptor available I wouldn't need to wait for a change to be made to this lib. I could get the information and move on.

@tony612 Any updates here?

@hassox Custom options is in my plan, but I need some time to finish it. For this PR, do you think using an protoc option can help you? Like
protoc --elixir_out=gen_ descriptor:. *.proto

You can refer to the current implementation https://github.com/tony612/protobuf-elixir/blob/173f6836dc840eee29f7acf62693403218913267/lib/protobuf/protoc/cli.ex#L24
So that people who don't need this won't be disturbed by the strange binary in generated code. Then I'll be very happy to merge this PR.
btw, I think some features like JSON converting can be supported by protobuf-elixir itself.

The challenge is when we try to build tooling around our shared contracts we need options that are already accessible and familiar in the descriptor but will never end up in the main library. We use options for http, graphql and Kafka at the moment and likely will add more.
Waiting for the library to explicitly handle an option just doesn't work out. If the descriptors were present, we could potentially contribute a bunch back to the library and help to flesh out elixir support for protocol buffer tooling built around the existing lib. That becomes difficult when there is a loss in consistency.
I don't mind making it an option though. How would you feel about making it opt out rather than opt in?

@hassox The reason is I didn't see many requirements for this feature. So I'd rather making it opt out now instead of changing everyone's generated code by adding a strange function they don't know. I want to keep the generated code simple and easy to read.

@tony612 I've updated to use a CLI option. Can you take a look mate?

@hassox Done. Thanks!


when use compel with inpaint controlnet, the result mask area is blue

original image

without compel

with compel, but you can see the original cloth part is preserved which is awesome, but the color turned to blue

this happend when negative embed present

i have removed the exploitative content, please repeat your tests with an image prompt based on a different topic (eg an animal or a car)


mgmt, upgrade features RP

tests pass under resources
basically, only this is manual change https://github.com/Azure/azure-sdk-for-java/pull/23211/commits/fae32ca8ff2f0832c0237b5b070acf749a495377

/check-enforcer override

all CI pass, just check-enforcer not done


Add docs for Caddy widget

Adds the docs for a new Caddy widget.
Details regarding the widget see here: https://github.com/benphelps/homepage/pull/1503

Thanks. I think this needs to be the admin port e.g. 2019


Fix ESLint warnings

npm start shows 5 warnings. They seem easy to fix.
I can fix them if you're ok

ok


Xterm steel electron accelerator Command

Xterm seem to be steeling electron accelerator
Keys like:
cmd+Alt+left
cmd+Alt+right
cmd+Alt+up
cmd+Alt+down
Might be related to #487
Details

Browser and browser version: (Electron)
OS version: OSX
xterm.js version:  lastest master e0639e1b62dbbb0a110dcc36ab8c668f7c2af1c3

You need to prevent the key events from being passed to xterm by attaching a keydown handler http://xtermjs.org/docs/api/Terminal/#attachcustomkeydownhandlercustomkeydownhandler
xterm.js will consume any key events that a terminal app may find useful.


hardware config: fix git add logic

Fixing the git add hardware config logic in case the user provides a relative path. We're doing two things:

Failing loudly if the git add command fails. At that point, we already know git is in $PATH. If the git add fails, the evaluation will likely fail in a flake setting. Better fail early with a helpful git error message.
We're resolving the hardware config path in the CLI parsing layer to make sure this path has the meaning the user intented it to have.

The CI failure is related to a test case where we have git but the local repo is not git-tracked.
I guess we should check if the local repo is git-tracked before failing?

CI fixed. This is ready for review.

@mergify queue


Download all Blobs in Container

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Problem
I am trying to download all blobs in a container with a single action
Desired Solution
Either a dropdown on the download selected button to allow a Download All or when you right click on the container it offers a download all selection
Alternatives and Workarounds
Currently the select all functionality is paginated, you have to:

Select the container
Ctrl + A
Select Download
Navigate to the next page
Repeat

Additional Context
My use case is primarily revolving around the Azure Image Builder packerlog service which creates a new folder and file in a container.  I want to be able to download all of these folders to analyse the blob data locally and removing the need to manually paginate the data would make this process significantly easier

Make sure to pay attention to the conversation on https://github.com/microsoft/AzureStorageExplorer/issues/6139


Waiting for events on a RustConnection hangs

This is either a bug, or I am not understanding how to handle a connection correctly.
Code:
pub struct Daemon {
    conn: RustConnection,
    root: u32,
}

impl Daemon {
    pub fn new() -> Result<Self> {
        let (conn, screen) = RustConnection::connect(None)
            .map_err(|e| eyre!("could not connect to X.org").with_error(|| e))?;

        let root = conn.setup().roots[screen].root;

        Ok(Self {
            conn,
            root,
        })
    }

    pub fn next_event(&self) -> Result<Event> {
        self.conn
            .wait_for_event()
            .with_context(|| "while trying to wait for the next event")
    }
}

Daemon::next_event hangs indefinitely.

Under normal circumstances, wait_for_event should never hang. I think we need context for the rest of the program. Do you have a window open? If so, is the window mapped? If so, do you have any event masks selected on the window?

I am not opening a window. I am trying to grab keys to bind them to a command, kind of like sxhkd. This minimal example is not grabbing any keys, though. It just connects to X.org by calling the new method. It stays in a loop, waiting for new events using next_event. Currently it just prints them out.
I am currently not on my pc, so I cannot send you my code right now. I’ll do that ASAP

My main.rs:
use color_eyre::Result;
use thkd::Daemon;

fn main() -> Result<()> {
    let mut daemon = Daemon::new()?;
    let event = daemon.next_event()?;
    eprintln!("{event:?}");

    Ok(())
}

Could you run setxkbmap while your program is running? That "almost surely" generates an event on all X11 connections. For example, setxkbmap de switches to a German keymap.
I guess what is happening is that you are not asking for any events and thus not getting any. And "wait for next event" obviously hangs when no next event arrives.

If you want to get key events from a window thaht you're not controlling you need to use xinput afaik. Here's an example of your code doing that, pardon my unwraps.
Using deps below.
[package]
name = "any"
version = "0.1.0"
edition = "2021"

[dependencies]
x11rb = { version = "0.9.0", features = ["xinput"]}
x11-dl = { version = "2.19.1"}

And your modified code
use x11rb::connection::Connection;
use x11rb::protocol::Event;
use x11rb::protocol::xinput::{DeviceId, DeviceUse};
use x11rb::protocol::xproto::{ChangeWindowAttributesAux, ConnectionExt, CreateWindowAux, EventMask, WindowClass};
use x11rb::rust_connection::RustConnection;

fn main() {
    let mut daemon = Daemon::new();
    let event = daemon.next_event();
    eprintln!("{event:?}");
}
pub struct Daemon {
    conn: RustConnection,
    root: u32,
}

impl Daemon {
    pub fn new() -> Self {
        let (conn, screen) = RustConnection::connect(None).unwrap();

        let screen = &conn.setup().roots[screen];
        let root = screen.root;

        // Get registered devices
        let devices = x11rb::protocol::xinput::list_input_devices(&conn).unwrap().reply().unwrap();
        for device in devices.devices {

            // Find keyboards
            if device.device_use == DeviceUse::IS_X_KEYBOARD {
                // I only have one keyboard plugged in and it's "openeded" but you might have more and need to
                // first run `x11rb::protocol::xinput::open_device(&conn, device.device_id).unwrap().reply().unwrap();`

                // Select events for the keyboards
                x11rb::protocol::xinput::xi_select_events(&conn, root, &[
                    x11rb::protocol::xinput::EventMask {
                        deviceid: device.device_id as u16,
                        // These are REALLY hard to find outside of c-macros,
                        // they exist as generated code in https://github.com/AltF02/x11-rs/blob/master/x11-dl/src/xinput2.rs
                        // If you add that as a dependency you can use these constants.
                        // I would just hardcode them if you don't need x11-dl as a dependency for something else
                        mask: vec![(x11_dl::xinput2::XI_RawKeyPressMask | x11_dl::xinput2::XI_RawKeyReleaseMask) as u32]
                    }
                ]).unwrap().check().unwrap();
            }
        }

        Self {
            conn,
            root,
        }
    }

    pub fn next_event(&self) -> Event {
        self.conn
            .wait_for_event()
            .unwrap()
    }
}

The underlying problem is that you're not listening to the relevant events. Since you don't have a window up you only get some meta-events about the state of the server, @psychon's suggestion gives an event but if you're looking for keypresses outside your window you need to go through a device and xinput.
I hope that helps!

Could you run setxkbmap while your program is running? That "almost surely" generates an event on all X11 connections. For example, setxkbmap de switches to a German keymap.
I guess what is happening is that you are not asking for any events and thus not getting any. And "wait for next event" obviously hangs when no next event arrives.

I'll try this first, then I'll try doing the x11-dl solution.

I just got this:
MappingNotify(MappingNotifyEvent { response_type: 34, sequence: 0, request: KEYBOARD, fi
rst_keycode: 8, count: 248 })
MappingNotify(MappingNotifyEvent { response_type: 34, sequence: 0, request: MODIFIER, fi
rst_keycode: 0, count: 0 })

XI_RawKeyPressMask

This works, thanks!


Version 1.0.6 of gaxios doesn't seem to have any *.js files in it

Saw this while investigating "Error: Cannot find module 'gaxios'"  error that started happening for my program today. See below, it seems version 1.0.2 has "build" directory but version 1.0.6 that was released today does not.
@azina:node_modules$
@azina:test$ npm install<EMAIL_ADDRESS>...
+<EMAIL_ADDRESS>updated 1 package and audited 524 packages in 0.638s
found 0 vulnerabilities

@azina:test$ ls node_modules/gaxios/
LICENSE  README.md  build  package.json

@azina:test$ npm install<EMAIL_ADDRESS>...
+<EMAIL_ADDRESS>updated 1 package and audited 524 packages in 0.76s
found 0 vulnerabilities

@azina:test$ ls node_modules/gaxios/
LICENSE  README.md  package.json

+1 from me, Just came across the same problem now also investigating Error: Cannot find module 'gaxios'

@google/gcp-metadata module use is with an unpinned version causing our build to crash too.

+1

@xavhan Yeah, I'm struggling with the same module :)

+1

For the maintainers: please delete that bad package from npm ASAP, this brakes @google-cloud/trace-agent especially when deploying to google cloud functions (where the package-lock.json and yarn.lock files are not respected).

We're having the same issue as @codyzu described. We've managed to get round it by adding gaxios as a dependency in our package.json and the fixing the version at 1.0.4. This works for the short term.

  This release obviously should not have gone out :(  I just pushed 1.0.7 which resolves the issue.  Apologies again!


custom resolvers: must load eslint-import-resolver-{x} form first

Allowing explicit packages to have precedence means that webpack is being loaded to resolve instead of eslint-import-resolver-webpack.
Blocks v1.9.0 release. (#372)

@benmosher I've just spent an hour working out why my config wasn't working, and it's because of this issue. I have eslint-plugin-import 1.9.0, with eslint-import-resolver-webpack 0.3.1.
Any chance of releasing this fix soon?

@avaragado just published 1.9.1 with just this patch.
How did you end up with 1.9.0 installed? I hid it behind the next tag on npm so that it wouldn't be public-facing, ideally.

@benmosher Looking through my command-line history, it seems it was presented under the 'Wanted' column of npm outdated. The 'Latest' column showed 1.8.1. I guess I jumped the gun.

I was worried that might happen. 😞  I think 1.9.x is semver-valid if your package.json has something like ^1.8.1. So that's on me, I didn't realize npm would install versions past the latest tag.

Yeah, that's the situation I was in. npm update ignores those tags, it seems, and follows the semver specified in package.json.
I've updated to 1.9.1 and it works, so thanks!


feat: conversion rate price for tokenized vaults

Addition

A new aggregation mode, available only for LST based on STRK.
Modified get_data function to handle the ConversionRate case.
New storage slot for registered LST token addresses
add and remove LST token address
Tests

Two possible sources of overflow coming from the conversion rate price computation. The first one is on our side, if we provide a price too big. The occurence is excluded because handled by the oracle itself. The second is on the token contract itself, if it returns a preview_mint too big.


Add advanced options when deriving from PollingFileSystemWatcher

Can we merge this? Any other comments?

Can we merge this? Any other comments?

You should add tests for the new extension point. Adding sample projects is something we don't do. Other than that it looks fine.

BTW, I have no opinions on the sample. I like the cleanup/renames in the APIs.

I'm working on adding unit tests for already merged code: https://github.com/dotnet/corefxlab/pull/2273
I'll add some unit tests here next.

I'll add some unit tests here next.

I'm fine with a follow-up as this is the labs repo. I'm even ok with merging this if you remove the sample project as a part of that.
The problem with sample projects is that there is no effective way to maintain them. How do we validate they work? What value do they provide if we can't validate? (Outside of "they compile", which can be done in an existing test project.) They are a tax that can't be absorbed on the scale that we operate. If we embraced them we would have thousands of projects to compile and otherwise maintain. If we had a well constrained process for managing them that didn't add overhead to the core development cycle maybe.
I do think it is good to have scenario tests that cover samples and help ensure that we're explicitly covering what we have written up in blogs/docs/etc. Have thousands of additional tests in existing projects is fine. :)

Sample removed.
As for testing, I'm not sure how to test this part. There are two main challenges: 1) The methods are protected and 2) FileSystemEntry is of type ref struct.
The first one I got around with Moq, but I can't find a way to get FileSystemEntry to get passed in as an argument.
    [Fact]
    public static void ShouldIncludeEntryTest()
    {
        Mock<PollingFileSystemWatcher> mock = new Mock<PollingFileSystemWatcher>();
        mock.Protected()
            .Setup<bool>("ShouldIncludeEntry", It.IsAny<FileSystemEntry>())  // The type 'FileSystemEntry' may not be used as a type argument
            .Returns(false)
            .Verifiable();

        var watcher = mock.Object;
        watcher.Start();

        mock.Verify();
    }

It.IsAny<DateTime> works fine, so I assume that this error has something to do with ref struct, but I'm not sure how to work around it.

As for testing, I'm not sure how to test this part.

You have to manually create your own mock as we don't use a mocking framework. Just derive from the watcher and track whatever you need to. An example: https://github.com/dotnet/corefx/blob/master/src/System.IO.FileSystem/tests/Enumeration/ErrorHandlingTests.netcoreapp.cs

@JeremyKuhne Merge?


Capitalize instances of "python" in user-facing text

Whenever there are user facing references like in settings, commands or descriptions, we should capitalize "Python".

We are reserving this issue for Grace Hopper's Open Source Day, which will take place on September 22nd, 2023. If you're part of the event and would like to submit a contribution to this issue, please let us know, and we'll be happy to assign it to you.
For other community members who are not participating in the event, we appreciate your interest in contributing! We kindly request that you wait until after September 22nd to work on this issue. If no one from the event has been assigned to it by then, we'll gladly assign it to you. Thank you for your understanding and support!

Hi Luciana, I would like to work on this issue!

@Jyothirmaikottu You can look at the following files where python is used and are user facing texts:
https://github.com/microsoft/vscode-mypy/blob/main/package.nls.json
https://github.com/microsoft/vscode-mypy/blob/main/package.json
https://github.com/microsoft/vscode-mypy/blob/main/README.md

https://github.com/microsoft/vscode-mypy/pull/159 and https://github.com/microsoft/vscode-mypy/pull/161


Actually true is false, and false is true

don't ask.

Coverage remained the same at 15.799% when pulling 16c8b5d425578953eb011861c25c8cbaa10eb6d3 on minor-fix-to-forever-loading-403-exclusive into 61f97154a12aaf1a850ee9504670336c2f28e8a0 on master.

I don't understand this change, but if I did, maybe I'd come to understand that $scope.loading = true; does not mean "It is true that the page is still loading." and rather means something else ("It's true that the page is as loaded as it's ever gonna be.", say.)
If $scope.loading = true does not mean "the page is truly loading" and $scope.loading = false does not mean "the page is not loading", well, is there some renaming available that would make this loading indicator code easier to understand?

Revamped loading to be loaded. Should make more sense now.

Coverage remained the same at 15.799% when pulling 00f45db2fa79067ceef987483522cd8809579b1b on minor-fix-to-forever-loading-403-exclusive into 61f97154a12aaf1a850ee9504670336c2f28e8a0 on master.

:+1:

👍


Improve UI/UX

[x] Add icons
[x] Add "add to calendar" button Out of scope for this issue, moved to #13
[x] Update CSS for better looks & responsiveness
[x] Improve form error messaging
[ ] Replace background
[x] Rotate pins randomly
[ ] Add favicon
[x] Add OpenGraph
[x] Make pins with thumbnail background... readable
[x] Implement mandatory image description
[x] Add placeholders to forms
[ ] Scroll to new pin on error

Pins are readable since b2cc09cd1721a8065640a99f42027b1131800347!

Implemented improved form handling & custom error messages in 24e91493ad4fd4f1e735a05b99d660fa515fdb25!

Mandatory image descriptions added in 683e99e35c2c359f7d2a8753b0af1efc2182f79d!

Scroll to new pin on error added in 72177b23dd9b7179e9b83a13625c085a61786336


How do I get the requestSession using an external url?

As the title says, requestSesssion is obtained using a path relative to this plugin. How do you get the requestSession by passing in an external url?

It is difficult to get external URL running in a cordova project. This is why we focused on HTML pages available offline in your project using a relative path. If you still want to open any URL you may need to update the plugin.

It is difficult to get external URL running in a cordova project. This is why we focused on HTML pages available offline in your project using a relative path. If you still want to open any URL you may need to update the plugin.

Thank you for your reply,I got it.


Add libusbsio DLLs to Windows build script

Fixes https://github.com/Nitrokey/pynitrokey/issues/170
This is reported to fix the nitropy.exe.  @daringer Can you please test it on your system and also check whether the installer works?

ping @daringer

I can't test it at the moment due to packaging issues. This is what I get while trying to run the installer:

nitropy.exe - System Error
The code execution cannot proceed because python36.dll was not found. Reinstalling the program may fix this problem.

If this is on my side only, please let me know how to fix it.

Does not work built from this branch - complaining about missed spsdk modules.
Rebasing and  trying again in fix-dlls-rebased. Leaving this branch intact for now.

For comparison: current build v0.4.16, without the fix

Does not work built from this branch - complaining about missed spsdk modules.

That is expected due to the incompatible spsdk 1.6.0 release.

Works after the rebase! Looks good to me.
I run the update, and it finished under 10 seconds. nk3 test passes too.
Anything else worth checking before merging?

Did you test the installer, the binary or both?

Anything else worth checking before merging?

No, not from my side.

Single binary only. Did not touch the installer. I did not see any changes in this regard in code - shall I look into it anyway?

No, just wanted to know whether it magically repaired itself after your last report.

Ok! Will check it then on the next release.