added codeql gha + greetings gha + config gha + issue templates

This PR Contains

Added Greetings GHA for first timers welcome
Added Codeql GHA for code analysis
Added Config GHA merging pr, opening pr
Added Standard issue templates

cc @yuval-hazaz

@Ayush7614 thanks for this PR
We are not handling issues directly in this repo. All issues for this repo should be open in the main repo amplication/amplication
The current config.yml provides the relevant information
I will close the PR in this issue, and you are welcome to open a new PR about the greetings in the main repo. Once you do that @MoFoGo and @souravjain540 will be able to review it with you to decide on the specific lingo


fix type checks for Godot 4 rc3

Type checks were reworked in Godot 4 rc3 here.

Great catch, thank you.

@daleblackwood Would you mind cutting a release with this fix in it please?


share card changes

@Kunal-deve1oper plz resolve the conflict after that once again push ur code

When  I link share preview is not working...

When I link share preview is not working...

i am looking into it

When I link share preview is not working...

it is working perfectly in my localhost but its not working when we are hosting it .  I used dynamic routing and I do not know why its mot working when we are hosting it


I cannot install this package

I cannot install this package.
ERROR: Could not find a version that satisfies the requirement fastapi-cache2 (from versions: none)
ERROR: No matching distribution found for fastapi-cache2

I tried on python3.6.


Modify AI publication importing to only import "direct" authorships

This is discussed in this basecamp thread starting at Jan 28:  https://3.basecamp.com/4206247/buckets/15288919/messages/3400105791#__recording_3424568680
This seems like it should "work" in theory to help avoid importing the incorrect authorships that are a problem in Activity Insight, but we still need to think through how well it would actually work in practice given the source data in AI and our process for merging duplicate data in RMD.

We will not be able to fix existing authorships where people have mistaken been identified as authors for papers they are not authors on; however, going forward we will only take AI publications that are associated with the user we are pulling information from.
Example, If Jane puts Joe on a paper in AI, but Joe doesn't enter the paper in AI we have been previously been pulling in both Jane and Joe on the paper. Moving forward we will only pull in Jane as an author on the paper. If Joe would like to have the paper pulled in then he will have to enter the paper into AI as well.

We decided that we need to try to do three separate but related things in order to completely handle the incorrect authorship information that is coming out of Activity Insight. Those three things are as follows:
First Item:
We need to modify the code that imports metadata from Activity Insight and creates both Authorship and Contributor records in RMD. As it stands, we import metadata by person from AI and we iterate over all of the publications that the person has recorded in AI and then over all of the authors that they have recorded for each publication (including themselves) to create Authorships and Contributors. The problem is that in come cases, some of the authors that they listed in AI may be incorrect. What we need to do instead is to create only one Authorship record for each publication that we import from AI - this record should link the publication to the person who recorded the data in AI. We'll still need to look at the authorship data from AI to determine this author's position in the list, but we won't use the rest of the metadata to create Authorship records for any other Penn State authors that are listed because they may be incorrect. We'll still create the list of Contributors by iterating over the AI authorship metadata and saving each record, but we need to apply a new rule:  if an author isn't a user in AI, then we need to convert their first name to just a first initial (because the full first name could be incorrect, but the first initial shouldn't be).
Second Item:
This item is useful on its own, but it will be particularly useful with respect to this problem of correcting AI data. We need to modify the process of merging (duplicate) publication records so that it combines all of the Contributors that are associated with each publication that's being merged, removes any duplicates from that set, and associates the resulting set with the resulting publication. The criterion for identifying duplicate Contributors is a match on both first initial and last name.
Third Item:
After the first item has been completed, we need to deal with incorrect Authorships and Contributors that have already been imported into RMD from AI. The easiest way to do this will be to delete all of the Authorship records that are associated with every publication that in turn is associated with an Activity Insight import record and does not contain any data that has been provided by an RMD faculty user. After deleting this data (which will include both correct and incorrect authorship records), we'll need to do a special reimport of just Authorship and Contributor records from AI using the new logic described in the first item. We'll need to import this data even for publication records that have been modified by an RMD admin user, and we'll still need to check for existing Authorship records so as to not create any duplicates.

I'm finished with the first item in development, and I think it's ready to go into production.
I took a closer look at the second item by examining some real metadata to see how it would work. I immediately found an edge case where the proposed solution would not work correctly. In this case, it was a Penn State author who had changed their last name (it looks like they appended a second surname). They entered some publication metadata where they listed themselves as an author, but their new last name was listed even though they were using their old last name whenever the article was published. Another Penn State Author listed the same publication, but correctly listed the first author's old last name. In this case, if we merged contributors as described above, we'd have a list that contained the same person twice - once with the original last name and once with the new last name.
This points me in the direction of doing two additional things for Item #2 one of which is a bit of effort, and the other of which is very minor but important in my opinion:

We should create a link between User records and Contributor records where ever it's possible to do that. This would solve the issue with the edge case above because it would allow us to first compare Contributor records by User, and then only compare by first initial and last name if there is no User match. This also reveals that this is a potentially important/useful piece of information that we could have but currently don't. If we had this information, then for any given user we'd be able to ask the question, "What are all of the names by which this person has ever listed themselves as an author on a publication?". This leads me to:
We should rename the Contributor model. The current name is terrible, and it creates confusion because it doesn't meaningfully describe the data that it holds. At worst, it's actually misleading. I think it should be changed to something like ContributorName. AuthorName is tempting, but for some kinds of publications it may sometimes be inaccurate, and the broader "contributor" would be more appropriate. With this change, especially if the records are associated with users, it would make a lot more sense to say, "What are all of this user's contributor names?" vs. "What are all of this user's contributors". This little change will make it a lot easier to talk and think about these concepts.

I could definitely see where having a list of all of the names by which a user has been known could help us to correctly attribute works to that person from other data sources where the identity of people is ambiguous.

Ugh, scratch the first thing that I listed in that last post. The User/ContributorName connection might still be useful someday, but it's not going to help with merging contributor names. I was forgetting that we wouldn't be able to make that connection reliably in most cases from the metadata in Activity Insight.
I'm a lot less optimistic now that there's a reliable way to automate the merging of contributor names. This might just have to remain a manual process if we want maximum correctness. The good news is that Pure seems to have contributor name metadata that is generally both complete and correct, so the automatic merges involving Pure publications should result in good data in RMD, and so will any manual merge where a Pure publication is chosen to keep. For merges involving only Activity Insight publications, RMD admins will still need to compare the lists of contributor names and fix any mistakes/omissions on the merge target before merging.

The upshot of not being able to reliably merge contributor name data automatically is that we probably won't want to delete existing contributor names for publications that have been merged because we won't be able to automatically merge the names upon reimporting them. We'd just be trading one set of mistakes for another. Unfortunately I can't really see a better course of action than to just live with any incorrect contributor names that we already have until someone eventually stumbles upon them and asks an RMD admin to do a manual correction.

I think I have the process for item #3 worked out (for authorship records only). I'm running it in development currently to see what the results look like.


Choosing the price of the spot instance-Amazon

We are interested to use Cloudbreak to setup HDP clusters on Amazon. Amazon provides spot instances and we want to use as slave machines. It turns out that in cloudbreak we are forced to set a price higher than 0.1$, although in reality the price of the spot instance may fall down to 0.04. I think it makes sens to add more elasticity regarding the price we want to fix. Is there some ongoing work in that direction ?

You're right, we should make the threshold lower. I think there's no specific reason for it being 0.1 and I guess it is only validated on the UI - the backend should accept lower values as well.

Do you think that will be fixed in the upcoming release of cloudbreak ? In the meanwhile, any clue to make it working ? Should I use the native API calls ?

It is already merged in the UI project (https://github.com/sequenceiq/uluwatu/pull/236), so you can expect it to be available on cloudbreak.sequenceiq.com in a few days.

Great thank you !

Also I've checked it now and it turned out that Cloudbreak had a bug that caused all instances to be standard ones instead of spot ones if at least one hostgroup was associated with a non-spot template. I've also fixed it in https://github.com/sequenceiq/cloudbreak/pull/677. It will also be part of the next release.


camelCase or Underscore

Description of the bug:
Hi Team - I just wanted to highlight that fields in the request body are both in camelCase and Underscore in the  REST API Guide LINK . Check "candidate_count" in the first example and "Request body" section in the link. Wanted to confirm the right format.
Actual vs expected behavior:
No response
Any other information you'd like to share?
No response

The API does support both styles, but I can see that being confusing too.

I've updated the generation script & re-ran it. The examples in the REST API docs use camelCase now.

e.g. https://developers.generativeai.google/api/rest/generativelanguage/models/generateText


add blob base fee

Time spent on this PR:
Resolves: #801
Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing

What is the new behavior?

Does this introduce a breaking change?

[x] Yes
[ ] No

Only codecov failing


Remember speed settings across the app

Describe the bug
This is a feature request.
Right now speed settings are being saved only for session. I.e. even if you'll reopen some video where speed level has been changed, level will return to Normal.
To Reproduce

Open Video1;
Change speed to e.g. 2x;
Open Video2 - NOK, speed level will be Normal again;
Open Video1 again - NOK, speed level is Normal too, despite that it has been changed in step 2.

Expected behavior
Save speed level on "per app" basis (one value for all videos).
"Per app" basis is better 'cause of it's simplicity and the fact that usually speed level is constant across most of the videos (e.g. NewPipe does it in such way).
Device (please complete the following information):

Model: Xiaomi Redmi Note 9 Pro 6/64 Gb
OS: crDroid 7.23 (Android 11)
Version: 0.137

Duplicate of #233


Custom color swatch

Hex color swatches are nicely showing up. But not sure why custom swatches by uploaded images are not.
How to make custom swatches appear?

Thanks!

Unfortunately, we can't easily get the color swatches from Magento using API; We can possibly do this with https://github.com/DivanteLtd/magento2-vsbridge-indexer @afirlejczyk can You please take a look at this and propose some solution? I mean: we should probably put the swatches into attribute metadata and use it in VS frontend (currently we're just mapping the attribute label not using any other metadata)
For now, You can use the config based mapping to map the color labels to specific color hex values. Not optimal, but works :)

Related to: https://github.com/DivanteLtd/magento2-vsbridge-indexer/issues/15

Unfortunately, we can't easily get the color swatches from Magento using API; We can possibly do this with https://github.com/DivanteLtd/magento2-vsbridge-indexer @afirlejczyk can You please take a look at this and propose some solution? I mean: we should probably put the swatches into attribute metadata and use it in VS frontend (currently we're just mapping the attribute label not using any other metadata)
For now, You can use the config based mapping to map the color labels to specific color hex values. Not optimal, but works :)

Sorry for the late reply. I will try to play around with it and find a way, will post a solution if I can get there :D


pytest-sugar is not maintained? :thinking:

https://github.com/samuelcolvin/pytest-pretty/blob/0eb06ac11009224982aa68b0ac0759235b4fe8f9/README.md?plain=1#L10
Just wondering why you think pytest-sugar is not maintained:

https://github.com/Teemu/pytest-sugar/commits/master
https://github.com/Teemu/pytest-sugar/graphs/contributors

I have no insider information, but it looks maintained to me. :thinking:

I think I did see at some point a message stating it was unmaintained. I stopped using it, partially for this reason. Could be imagining things though.
In any case, good if it's being maintained [again]!

At the time I wrote this, I had reached out to the maintainer of pytest-sugar a few times and commented on https://github.com/Teemu/pytest-sugar/issues/224 offering to help, with no reply. Hence I assumed it wasn't maintained.
I'll remove this from the readme.

Ah, I hadn't seen that issue and the conversation there. For the said lack of interest by the current maintainers, it looks decently maintained. :smile: Thanks for the feedback and reference to that issue.

readme updated, 503f7d8a0f09062f59c22d01f2bc060b48912b09.


start list of framework integrations

for framework integrations, i suggest that we just link to the repository and document the integrations there rather than in the documentation. the documentation should not be about framework specific tool imho, to keep things easier to understand.

fixed


ordered starting/stopping of groups of tools

be able to start a list of groups in a particular order.
also be able to start tools in a group in a particular, based on a priority option in the group section of the template for that tool.

see also #266


fix: navbar vertical alignment should be centered even when there are…

… many items in it
This PR refers to the issue #373

Thanks for your contribution, however I can't merge it since those clases should be added dynamically when you hover the dark mode button and they should be removed when you stop hovering it. I just released a new version that fixes a problem with that.


ISSUE-28 Extend multipliers usage

PR implementing what @lipka describes in #28, this is enabling the use of multipliers alongside Equal, LessThanOrEqual and GreaterThanOrEqual relation attributes.
The final result will allow the following:
Width(*0.5)
Width(50)
Width(50, *0.5)
Width(>=50)
Width(<=5, *0.5)
Width(<=50)
Width(<=5, *0.5)

I guess Width(*0.5).like(otherView) comes for free, right?

Yup, it's fully backwards compatible :)


build problems with 0.38.0

I haven't yet had a chance to corner this bug, but there's something going on with the upgrade to 0.38.0 (via dependabot):
CGO_ENABLED=1 GOFLAGS="-buildmode=exe" go generate
CGO_ENABLED=1 GOFLAGS="-buildmode=exe" go test -tags=opa_wasm,slow -timeout 30m -run=- -bench=. -benchmem ./...
# github.com/bytecodealliance/wasmtime-go
vendor/github.com/bytecodealliance/wasmtime-go/config.go:3:11: fatal error: wasm.h: No such file or directory
    3 | // #include <wasm.h>
      |           ^~~~~~~~
compilation terminated.

I've got something like this running make build after go get<EMAIL_ADDRESS>and go mod vendor, too:
open-policy-agent/opa-main % make build
make[1]: Entering directory '/Users/stephan/Sources/open-policy-agent/opa-main/wasm'
make: '_obj/opa.wasm' is up to date.
make: '_obj/callgraph.csv' is up to date.
make[1]: Leaving directory '/Users/stephan/Sources/open-policy-agent/opa-main/wasm'
cp wasm/_obj/opa.wasm internal/compiler/wasm/opa/opa.wasm
cp wasm/_obj/callgraph.csv internal/compiler/wasm/opa/callgraph.csv
CGO_ENABLED=1 GOFLAGS="-buildmode=exe" go generate
CGO_ENABLED=1 GOFLAGS="-buildmode=exe" go build -tags=opa_wasm -o opa_darwin_amd64 -ldflags " -X github.com/open-policy-agent/opa/version.Version=0.42.0-dev -X github.com/open-policy-agent/opa/version.Vcs=2e75f0198-dirty -X github.com/open-policy-agent/opa/version.Timestamp=2022-06-22T12:44:04Z -X github.com/open-policy-agent/opa/version.Hostname=Stephans-MBP.fritz.box"
# github.com/open-policy-agent/opa
/usr/local/go/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: library not found for -lwasmtime
clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [Makefile:121: go-build] Error 2


Error installing Rust toolchain with RubyGems

Hi, I wanted to report an error installing the Rust toolchain on Mac ARM (which happens by default if users don't have Rust installed). To reproduce:
RB_SYS_FORCE_INSTALL_RUST_TOOLCHAIN=true gem install wasmtime --platform ruby

Output
Building native extensions. This could take a while...
ERROR:  Error installing wasmtime:
    ERROR: Failed to build gem native extension.

    current directory: /Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext
/Users/user/.rbenv/versions/3.2.1/bin/ruby -I /Users/user/.rbenv/versions/3.2.1/lib/ruby/3.2.0 extconf.rb
checking for cargo... no

current directory: /Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext
make DESTDIR\= sitearchdir\=./.gem.20230328-15890-3en8ju sitelibdir\=./.gem.20230328-15890-3en8ju clean

current directory: /Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext
make DESTDIR\= sitearchdir\=./.gem.20230328-15890-3en8ju sitelibdir\=./.gem.20230328-15890-3en8ju
info: downloading installer
info: profile set to 'minimal'
info: default host triple is aarch64-apple-darwin
info: skipping toolchain installation

Rust is installed now. Great!

To get started you need Cargo's bin directory
(/Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext/.rb-sys/stable/cargo/bin)
in your PATH
environment variable. This has not been done automatically.

To configure your current shell, run:
source
"/Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext/.rb-sys/stable/cargo/env"
make: rustup: No such file or directory
make: *** [/Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1/ext/.rb-sys/stable/cargo/bin/cargo] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/wasmtime-6.0.1 for inspection.
Results logged to /Users/user/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/extensions/arm64-darwin-22/3.2.0/wasmtime-6.0.1/gem_make.out

Ref: https://github.com/ankane/tokenizers-ruby/issues/28

If someone wants to give this a shot, please do! I won’t be able to look at this for a few weeks but could help you through the issue.
I believe the solution here would be to update mkmf.rb to reference the absolute rustup path when RB_SYS_FORCE_INSTALL_RUST_TOOLCHAIN=true. Testing could be a bit of a pain so I’d be fine with manual testing for now.


Add offline indicator (Lithuanian)

@naltatis Could you tell me why there is a difference in de.js and en.js versus lt.js in code line 16 ??
https://github.com/evcc-io/evcc/blob/master/assets/js/i18n/de.js
https://github.com/evcc-io/evcc/blob/master/assets/js/i18n/lt.js
de, en :
16      modalNoReleaseNotes:
17        "Keine Releasenotes verfügbar. Mehr Informationen zur neuen Version findest du hier:",
18      modalCancel: "Abbrechen",

lt:
16      modalNoReleaseNotes: "Naujinimo detalių nėra. Daugiau informacijos rasite čia:",
17      modalCancel: "Atšaukti",

One of those is incorrect? (would be easier to match and check translation changes if line numbers were identical)

Due to line-length and auto-formatting by prettier.

Seems this is also why your PR fails- please use vscode with installed prettiert plugin to maintain consistent formatting when saving.

I'm just doing it on github online...

That will apparently not work...

Changing language files need a UI rebuild. Details are in the Readme.


Karlburke/indexing efficiencies round6

Following merged PR #824 for TEST
Will need to go hand in hand with https://github.com/hubmapconsortium/entity-api/pull/696

Replaced by PR #829
FYI @kburke


Investigate differences between source file and exported file

With #14 merged, if you import animation and export it, the output will be slightly different but not noticeable. It might be a bug in the import process.

The problem is that algorithm calculating rotations from positions is wrong. The issue stems from the fact a) both bones and armatures have local coords system and b) the rotation is dependent on the movement of its parent (it is a rigid body system)


[3pt] My reservations Page: Member 2

When the user clicks the "My reservations" link in the navigation panel they can see a list of their reservations (with information about item name, date and city).

Created the reservation page where users can see his/her reserved cars:


feat: Complete Sequence{Set,} costructors.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

113 of 133 (84.96%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.3%) to 92.701%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

imap-types/src/sequence.rs
113
133
84.96%

Files with Coverage Reduction
New Missed Lines
%

imap-types/src/sequence.rs
1
93.52%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
9043

Relevant Lines:
9755

💛  - Coveralls


use parentheses to remove ambiguity in mix.exs

width Elixir 1.4 I got these warnings:
warning: variable "description" does not exist and is being expanded to "description()", please use parentheses to remove the ambiguity or change the variable name

  /my_app/deps/joken/mix.exs:11
warning: variable "package" does not exist and is being expanded to "package()", please use parentheses to remove the ambiguity or change the variable name

warning: variable "deps" does not exist and is being expanded to "deps()", please use parentheses to remove the ambiguity or change the variable name
  /my_app/deps/joken/mix.exs:12
  /my_app/deps/joken/mix.exs:10
==> joken
Compiling 6 files (.ex)
warning: variable "docs_config" does not exist and is being expanded to "docs_config()", please use parentheses to remove the ambiguity or change the variable name

  /my_app/deps/joken/mix.exs:16

Coverage remained the same at 84.783% when pulling e002ad071e46bb833b14f31d23ec7b8462bebec8 on schurig:patch-1 into 2f61a75bfdf346aeb4ac4973281da768929cd4b2 on bryanjos:master.

Thanks!


Possible to improve resolution as done with timg?

Would be neat to up the quality of the graphics like is done in timg.  I am not sure if this is even possible but if that level of resolution could be achieved everything changes...

I should probably call this out in the readme, but could the bitmap mode introduced in 0.0.3 do what you're looking for? https://github.com/fathyb/carbonyl/releases/tag/v0.0.3

That is better, however timg has no pixelation it is amazing.  So this isn't quite what I am thinking with this request.

They probably mean the Kitty and Sixel graphics protocols, that's what timg uses.


Add New trait and an optional emulator CkTransport for testing

Description
I consolidated the TapSigner.init() and SatsCard.new_slot() functions into a New trait. I also changed slot fields to u8 which they need to be. Since it's a PITA to test new with real cards I also added a CardEmulator (and feature to enable it), which talks to the cktap emulator, see link in README.
Notes to the reviewers
I should have setup how to test with the emulator sooner! it's much easier than using real cards. Eventually I want to setup the CI to run tests against the emulator acting as a SatsCard and TapSigner.
Changelog notice

Add emulator feature for lib and cli packages
Add new and unwrap commands to cli

Checklists
All Submissions:

[x] I've signed all my commits
[x] I followed the contribution guidelines
[x] I ran cargo fmt and cargo clippy before committing

New Features:

[x] I've added tests for the new feature
[x] I've added docs for the new feature

From an api clarity point of view that's a fair concern. But I also don't like having mainly duplicate code. Let me noodle on this a little and see what I can do.

I took out the New trait. The duplicate code isn't that much and I do agree the end user facing API is different enough to have two card specific functions. If the rest looks OK to you I'll merge it.

ACK d53e71c57498aecf3ef5f09880bef071cff6cb74


Add a minor comment related to typescript

Hi, this may seem insignificant but i just spent hours trying to make useMutation in typescript project, after much debugging and github issues reading i realized only typing my mutationFn should have fixed it. :man_shrugging: I saw this during my debugging but didn't realize it is important, just typing it here so it saves someone trouble.

Well said @TkDodo
No overload matches this call.
  The last overload gave the following error.
    Argument of type '(data: { id: string; flag: boolean; }) => void' is not assignable to parameter of type 'MutationKey'.
      Type '(data: { id: string; flag: boolean; }) => void' is missing the following properties from type 'readonly unknown[]': concat, join, slice, indexOf, and 17 more.  TS2769

    24 |
    25 |   const { mutate } = useMutation(
  > 26 |     (data: { id: string; flag: boolean }) => {
       |     ^
    27 |       const { id, flag } = data;
    28 |       return updateFlag(id, flag);
    29 |     }

here is the weird error i was facing, i realized another reason for this was that i was not returning promise :facepalm: silly mistake, closing this since i tried and it doesn't throw weird errors if promise is returned :sweat_smile:


Maljdan/error messages

Pull Request Description
What issue does this change request address?
Closes #221 and Closes #222.
What are the significant changes in functionality due to this change request?
Better error messages when input data is malformed.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Thank you for this.


Module: Implement for Tuple

Feature description
Implementing Module support for Tuple
Feature motivation
Would allow syntax such as:
#[derive(Module, Debug)]
pub struct UNetMidBlock2D<B: Backend> {
    resnet: ResnetBlock2D<B>,
    attn_resnets: Vec<(AttentionBlock<B>, ResnetBlock2D<B>)>,
}

Would a workaround of using struct work in this case? Suggesting in case if someone is stuck on this issue.

Would a workaround of using struct work in this case? Suggesting in case if someone is stuck on this issue.

Yup! That’s the workaround I’ve gone with but raised the issue after a conversation with Nathaniel.

Done via #1186


CauseStackManager called from off main thread error.

Thaumcraft-1.12.2-6.1.BETA15
forge-1.12.2-<IP_ADDRESS>05-universal
spongeforge-1.12.2-2705-7.1.0-BETA-3136
https://pastebin.com/RLZ8uCm0

Why do you think the issue is with Thaumcraft, and not with spongeforge?
Also, I'd avoid Thaumcraft beta 15 - there's a bug in it that makes it unusable.

I didn't think it was, I reported initially to spongeforge and they said to report to Thaumcraft. Reference to that ticket below. I also did since then downgrade after finding that bug out.
https://github.com/SpongePowered/SpongeForge/issues/2196


Cache missing in MCL.scala, line 292

DataFrame lookupTable should be cached since it is used in line 297 and 330.

Same as variable M1 at line 308 which should be cached, since it is used for multiple times.


added Kazakh language

I have added Қазақ тілі (Kazakh) Language in the readme file.

@leonardomso Sir, please review and merge the pull request.


Update test_queries.txt

Deleted duplicated queries.
Deleted example query about scanmin and scanmax. GNPS libraries (E.g.) do not contain integers as scan identifiers, so the queries are failing in the numerical comparison.

I think these are usually meant for real files not just libraires. Duplicates we can remove, but not the substantive queries.


Extend the API to include more repository properties

Adds the properties description, stars_count, forks_count, watchers_count and
open_issues_count.

Thanks!


composer require problem

Hello.
Im trying to install the bugsnag but i cant.
why ?
composer require "bugsnag/bugsnag-laravel:^2.0"
Problem 1     - Installation request for bugsnag/bugsnag-laravel 2.0 -> satisfiable by bugsnag/bugsnag-laravel[v2.0.0].     - Conclusion: remove laravel/framework v8.24.0     - Conclusion: don't install laravel/framework v8.24.0     - bugsnag/bugsnag-laravel v2.0.0 requires illuminate/support ^5.0 -> satisfiable by illuminate/support[5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1,  v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9].     - don't install illuminate/support 5.5.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.16|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.17|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.2|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.33|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.34|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.35|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.36|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.37|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.39|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.40|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.41|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.43|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.5.44|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.6.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.1|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.10|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.11|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.12|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.13|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.14|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.15|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.16|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.17|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.19|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.2|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.20|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.21|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.22|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.23|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.24|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.25|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.26|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.27|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.29|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.3|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.30|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.31|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.32|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.33|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.34|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.35|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.36|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.37|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.38|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.39|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.4|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.5|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.6|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.7|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.8|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.6.9|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.7.17|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.7.18|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.7.19|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.7.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.1|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.10|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.11|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.15|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.2|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.20|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.21|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.22|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.23|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.26|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.27|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.3|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.4|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.5|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.6|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.7|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.8|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.7.9|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.8.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.11|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.12|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.14|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.15|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.17|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.18|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.19|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.2|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.20|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.22|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.24|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.27|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.29|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.3|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.30|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.31|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.32|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.33|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.34|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.35|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.36|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.4|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.8|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.8.9|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.1.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.2.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.3.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.4.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.1|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.13|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.16|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.2|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.20|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.22|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.25|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.30|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.31|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.41|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.6|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.1.8|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.19|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.21|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.24|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.25|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.26|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.27|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.31|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.32|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.37|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.43|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.45|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.6|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.2.7|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.3.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.3.16|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.3.23|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.3.4|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.13|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.17|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.19|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.27|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.36|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.4.9|don't install laravel/framework v8.24.0     - don't install illuminate/support 5.0.x-dev|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.0|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.22|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.25|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.26|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.28|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.33|don't install laravel/framework v8.24.0     - don't install illuminate/support v5.0.4|don't install laravel/framework v8.24.0     - Installation request for laravel/framework (locked at v8.24.0, required as ^8.12) -> satisfiable by laravel/framework[v8.24.0].

my composer.json
{     "name": "laravel/laravel",     "type": "project",     "description": "The Laravel Framework.",     "keywords": [         "framework",         "laravel"     ],     "license": "MIT",     "require": {         "php": "^7.3|^8.0",         "fideloper/proxy": "^4.4",         "fruitcake/laravel-cors": "^2.0",         "guzzlehttp/guzzle": "^7.0.1",         "laravel/framework": "^8.12",         "laravel/tinker": "^2.5",         "laravel/ui": "^3.2",         "livewire/livewire": "^2.3",         "santigarcor/laratrust": "^6.3",         "simplesoftwareio/simple-qrcode": "^4.2",         "spatie/laravel-activitylog": "^3.16",         "spatie/laravel-backup": "^6.14",         "superbalist/laravel-google-cloud-storage": "^2.2"     },     "require-dev": {         "barryvdh/laravel-debugbar": "^3.5",         "facade/ignition": "^2.5",         "fakerphp/faker": "^1.9.1",         "laravel/sail": "^1.0.1",         "lucascudo/laravel-pt-br-localization": "^1.1",         "mockery/mockery": "^1.4.2",         "nunomaduro/collision": "^5.0",         "phpunit/phpunit": "^9.3.3"     },     "config": {         "optimize-autoloader": true,         "preferred-install": "dist",         "sort-packages": true     },     "extra": {         "laravel": {             "dont-discover": []         }     },     "autoload": {         "psr-4": {             "App\\": "app/",             "Database\\Factories\\": "database/factories/",             "Database\\Seeders\\": "database/seeders/"         }     },     "autoload-dev": {         "psr-4": {             "Tests\\": "tests/"         }     },     "minimum-stability": "dev",     "prefer-stable": true,     "scripts": {         "post-autoload-dump": [             "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",             "@php artisan package:discover --ansi"         ],         "post-root-package-install": [             "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""         ],         "post-create-project-cmd": [             "@php artisan key:generate --ansi"         ]     } }

its works with:
composer require bugsnag/bugsnag-laravel:2.22.1
thanks.


Increase the cpplint timeout to 180 seconds.

This should make it less flaky when running on Windows.
This should make flakes like https://ci.ros2.org/view/nightly/job/nightly_win_deb/3051/testReport/junit/(root)/rviz_default_plugins/cpplint_xunit_missing_result/ less likely to happen.

Linux
Linux-aarch64
Windows


DurableTask-sidecar

Hi @cgillum
I am playing with the DurableTask.Dapr POC, and attempting to integrate with some existing test services that I spin up using Tye.    With Tye, it does not register HTTP-Port 3500, it's randomized.
However, your durabletask-sidecar image is expecting to communicate at 3500, which is failing when I attempt to invoke a new instance of my test orchestration as follows (Docker  DurableTask.sidecar:03.3..) ;
2022-09-09T04:46:14.425299Z info: Microsoft.DurableTask.Sidecar[1] Initializing the Durable Task sidecar. Listen address = http://<IP_ADDRESS>:4001, backend type = Dapr.
2022-09-09T04:46:14.593722Z info: Microsoft.DurableTask.Sidecar[2] Sidecar initialized successfully in 246ms.
2022-09-09T04:48:52.023040Z info: Microsoft.DurableTask.Sidecar[6] Received work-item connection from ipv4:<IP_ADDRESS>:34012. Client connection deadline = 9999-12-31T23:59:59.
2022-09-09T04:48:52.029980Z info: Microsoft.Hosting.Lifetime[14] Now listening on: http://[::]:80
2022-09-09T04:48:52.031585Z info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down.
2022-09-09T04:48:52.032581Z info: Microsoft.Hosting.Lifetime[0] Hosting environment: Production
2022-09-09T04:48:52.032671Z info: Microsoft.Hosting.Lifetime[0] Content root path: /app/
2022-09-09T04:49:54.121175Z info: Microsoft.DurableTask.Sidecar[7] Client at ipv4:<IP_ADDRESS>:34012 has disconnected. No further work-items will be processed until a new connection is established.
2022-09-09T04:50:54.121355Z info: Microsoft.DurableTask.Sidecar[5] Waiting for a remote client to connect to this server. Total wait time: 00:00:59.9979291
2022-09-09T04:51:54.122519Z info: Microsoft.DurableTask.Sidecar[5] Waiting for a remote client to connect to this server. Total wait time: 00:02:00.0005585
2022-09-09T04:52:54.123415Z info: Microsoft.DurableTask.Sidecar[5] Waiting for a remote client to connect to this server. Total wait time: 00:03:00.0014612
2022-09-09T04:53:15.365378Z info: Microsoft.DurableTask.Sidecar[6] Received work-item connection from ipv4:<IP_ADDRESS>:34140. Client connection deadline = 9999-12-31T23:59:59.
2022-09-09T04:55:00.545869Z info: Microsoft.DurableTask.Sidecar[0] Creating a new instance with ID = 3fa85f64-5717-4562-b3fc-2c963f66afa6
2022-09-09T04:55:00.640902Z fail: Microsoft.DurableTask.Sidecar[0] An error occurred when trying to create a new instance System.Net.Http.HttpRequestException: Connection refused (<IP_ADDRESS>:3500)  ---> System.Net.Sockets.SocketException (111): Connection refused    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)    at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)    at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsyncHandleSecurityExceptions(Func`1 requestFunc, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsyncHandleUnsuccessfulResponse(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsync(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.InvokeActorMethodWithRemotingAsync(ActorMessageSerializersManager serializersManager, IActorRequestMessage remotingRequestRequestMessage, CancellationToken cancellationToken)    at Dapr.Actors.Communication.Client.ActorRemotingClient.InvokeAsync(IActorRequestMessage remotingRequestMessage, CancellationToken cancellationToken)    at Dapr.Actors.Client.ActorProxy.InvokeMethodAsync(Int32 interfaceId, Int32 methodId, String methodName, IActorRequestMessageBody requestMsgBodyValue, CancellationToken cancellationToken)    at DurableTask.Dapr.DaprOrchestrationService.CreateTaskOrchestrationAsync(TaskMessage creationMessage, OrchestrationStatus[] dedupeStatuses)    at Microsoft.DurableTask.Sidecar.Grpc.TaskHubGrpcServer.StartInstance(CreateInstanceRequest request, ServerCallContext context) in /root/src/DurableTask.Sidecar/Grpc/TaskHubGrpcServer.cs:line 136
2022-09-09T04:55:00.656905Z fail: Grpc.AspNetCore.Server.ServerCallHandler[6] Error when executing service method 'StartInstance'. System.Net.Http.HttpRequestException: Connection refused (<IP_ADDRESS>:3500)  ---> System.Net.Sockets.SocketException (111): Connection refused    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)    at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)    at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsyncHandleSecurityExceptions(Func`1 requestFunc, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsyncHandleUnsuccessfulResponse(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.SendAsync(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken)    at Dapr.Actors.DaprHttpInteractor.InvokeActorMethodWithRemotingAsync(ActorMessageSerializersManager serializersManager, IActorRequestMessage remotingRequestRequestMessage, CancellationToken cancellationToken)    at Dapr.Actors.Communication.Client.ActorRemotingClient.InvokeAsync(IActorRequestMessage remotingRequestMessage, CancellationToken cancellationToken)    at Dapr.Actors.Client.ActorProxy.InvokeMethodAsync(Int32 interfaceId, Int32 methodId, String methodName, IActorRequestMessageBody requestMsgBodyValue, CancellationToken cancellationToken)    at DurableTask.Dapr.DaprOrchestrationService.CreateTaskOrchestrationAsync(TaskMessage creationMessage, OrchestrationStatus[] dedupeStatuses)    at Microsoft.DurableTask.Sidecar.Grpc.TaskHubGrpcServer.StartInstance(CreateInstanceRequest request, ServerCallContext context) in /root/src/DurableTask.Sidecar/Grpc/TaskHubGrpcServer.cs:line 136    at Grpc.Shared.Server.UnaryServerMethodInvoker`3.AwaitInvoker(Task`1 invokerTask, GrpcActivatorHandle`1 serviceHandle)    at Grpc.Shared.Server.UnaryServerMethodInvoker`3.AwaitInvoker(Task`1 invokerTask, GrpcActivatorHandle`1 serviceHandle)    at Grpc.AspNetCore.Server.Internal.CallHandlers.UnaryServerCallHandler`3.HandleCallAsyncCore(HttpContext httpContext, HttpContextServerCallContext serverCallContext)    at Grpc.AspNetCore.Server.Internal.CallHandlers.ServerCallHandlerBase`3.<HandleCallAsync>g__AwaitHandleCall|8_0(HttpContextServerCallContext serverCallContext, Method`2 method, Task handleCall)

My hope is to build out and test orchestrations (using Tye) within my current dev environment, such that I can flip them over to your final DAPR Workflow component solution, once it becomes available.   I do not intend to push your POC into a production env, but assuming the future DAPR Workflow .Net SDK is similar, then any Orchestrations would/should work with the final DAPR component.
I am new to DurableTask, so was hoping you could please provide me with code that you used to create your POC Docker image so I can run the DurableTask-sidecar dapr service as a Tye invocation, to test my WF integration(s).
Thanks in advance!
John

Hi @jkears. The sidecar image internally uses the Dapr SDK for .NET. I haven't tried this myself, but I think you may be able to set a DAPR_HTTP_PORT environment variable on this container to get it to use a port number other than 3500 (this code doesn't hardcode the port number anywhere).

I am new to DurableTask, so was hoping you could please provide me with code that you used to create your POC Docker image so I can run the DurableTask-sidecar dapr service as a Tye invocation, to test my WF integration(s).

Just to make sure I understand, you're asking if you can get access to the Durable Task sidecar source code so you can build it yourself? I haven't used Tye before, but does it require all containers to be built from source, vs. referencing existing images from dockerhub? Or were you thinking you might need to make changes to the code? Just trying to understand.

Hi @cgillum

Just to make sure I understand, you're asking if you can get access to the Durable Task sidecar source code so you can build it yourself? I haven't used Tye before, but does it require all containers to be built from source, vs. referencing existing images from dockerhub? Or were you thinking you might need to make changes to the code? Just trying to understand.

Yes, and yes to both of your questions;
We developed in-house tooling which provides us an ability to capture any business domain and from which, code-generate (using Roslyn),  DAPR based microservices.
We created a VS Code Web View Extension (see image below) that allows us to define microservices that are code-generated from a DSL based model.   We follow an Aggregate-First, Domain Driven Design approach in defining our services.

The above is a sample model from our ERP, specifically I am showing the FinTech Modules, General Ledger Service which consists of a bunch of Aggregates (showing JournalConfiguration and JournalBatch for example).
Our tooling allows us to define services consisting of as many or as few aggregates as would be necessary to describe the each business domain, and with great ease, code-generate the Web-API microservices that run within DAPR.
In development, MS Tye allows us to run all of these generated services all with the same DAPR network.  With Tye we define the various services in the Tye.yml file (which is also code-generated).
Below is the generated Tye file for the above model...

To spin up all code-generated services, we need only run Tye Run...

And with that we can attach to any service to debug code, etc.
Tye also provides a dashboard that allows us to view the logs of each microservice as well as it's DAPR side-car..

To extend this, and in prep for your soon-to-come, DAPR workflow component, we have created a supporting Aggregate type that is of type Workflow.

This will code-generate the above commands to create, integrate,  (not shown as not in POC pause/resume) and terminate commands.   But instead of persisting to MSSQL via EFCore or CosmosDB,  we would use your DurableTask Dapr WF context to create, new instance, terminate, etc...
So ideally, we would like to take what you are doing within the durabletask-sidecar image, and place that into one of our code generated services so that, we can run that service within Tye, as well as learn how it integrates with DAPR SDK .Net.
Once you have released the DT Workflow for DAPR, we would then flip over to use that, and everything should work the exact same but as workflow-actors hosted within each service's side-car.
This will allow us to build out/test workflow in advance of your upcoming DAPR WF Component.
Please let me know if this makes sense or not.
Respectfully,
John

Hi @cgillum,
We completed the code-generated integration and your current WF API fits perfect within our framework.
We still can't test it as we still require the ability to run durabletask-sidecar (image) within it's own service that can be spun up within the Tye DAPR services.
If you could be so kind as to provide the source used to create the durabletask-sidecar image, so that we can complete integration testing that would be fantastic.
Also,  how do we get the event data?  The current API does not seemingly provide us access to data.
For example, we publish this way...

Where on line 53, we are publishing the command as the event by the same name, and where the event payload is the command, and thusly, how within the actual orchestration logic would I gain access to the command that was passed in?

I am assuming that there would be an override where you could specify any Event Payload type on the WaitForExternalEventAsync API such as
`WaitForExternalEventAsync<EventPayloadType?>("DoSomething2Command", TimeSpan...

Hi @cgillum
I apologize for this reminder to you,  however would you please provide the source used to create the POC image so that we can complete testing workflow integrations using the existing POC approach.
Having the image source code would allow us to create an interim host service that we can run along side our existing domain services (via TYE).
This would allow us to test Durable Task-based workflows/SAGAs integration within our existing services, and thus be ready once the final DAPR Workflow component becomes available.
As we are not GO developers (C# only), we unfortunately cannot be of much assistance in the development of the new Workflow component, however we if we are able to integrate with the POC approach such that we build a bunch of workflows/SAGAs, from which we could provide you with additional thoughts, ideas and feedback for consideration within the final GO version of the DAPR Workflow component.
Please let me know if you would our time to test your preview versions of the GO Workflow component (as it becomes available).
Please let me know if you will provide the source code for the POC image.
Thanks
John

So you're saying that Tye doesn't work with existing sidecar images, and that they need to be built as part of the Tye project? I haven't tried using Tye yet, but that seems counterintuitive to me. The prebuilt image is publicly available on Docker Hub with the name/tag cgillum/durabletask-sidecar:0.3.3-dapr.
I went ahead and sent you an invite to the private repo that contains the POC sidecar source code.

Also, how do we get the event data? The current API does not seemingly provide us access to data.

Ah, it looks like I didn't create an API for actually processing the event data from within the workflow.  One hacky solution would be to just case the Task from WaitForExternalEvent into a Task<object>, but that's obviously pretty hacky. I can do an update that includes an overload for getting the data out.

Hi @cgillum ,
Thank you for all of your support!
I am able to create new orchestrations, invoke events (commands per orchestrations step) and terminate orchestrations when I run the POC sidecar project in VS (debug).   I am not sure why that works, while the image approach did not, but either way I am super happy!
I would love to show (you via Zoom) how well this all works, plus discuss how we can become beta-testers of the DAPR Workflow component block.
Cheers
John


[IR][Debug] Add dump and print for debugging (NFC)

[Debug] Add Dump function for Object type (NFC)
Signed-off-by: Wei Pan<EMAIL_ADDRESS>Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Given that this is an utility function, it would be better to make it as a public function rather than a member function. Perhaps we should simply fix tvm::Dump

Ideally we want to minimize the number of member functions being provide. Given that this is an utility function, it would be better to make it as a public global function rather than a member function. Perhaps we should simply fix tvm::Dump.

That is ok to me.  Minor addition to Dump works fine too.  FYI, vscode watch cannot find tvm::Dump, but lldb command line works.

Thanks @wpan11nv


ENH: Adding Modified Rodrigues Parameters to the Rotation class

Reference issue
N/A
What does this implement/fix?
The implements 2 new methods in the Rotation class of the spatial/transform package, as_mrp and from_mrp, which allow the class to accept input and provide output in the form of Modified Rodrigues Parameters.

I see the manuscript has been cited > 2000 times, which may help for justification of breadth of interest, but I'm not immediately familiar with this myself.

I'm not sure myself what the breadth of interest is. I'd never heard of them until I started taking a course on Coursera for spacecraft attitude control. Perhaps it would be better to split this work out into it's own little Python library and then merge it into scipy if it seems popular enough?

MRP fits well into Rotation, it's a small incremental addition which I support. I will review on the weekend.

I've updated the PR to address comments. In the update I have

Made the definition more substantial and made it consistent across from_mrp and as_mrp with one small difference in as_mrp to denote that the rotation returned is <=180
Modified the examples to use unity MRP and Euler angles where it made sense
-Renamed the ss variable. Renaming it to denom wasn't the best choice since it is also used in the numerator for calculating the scalar part of the quat, so I just went explicit and named it "mrp_squared_plus_1"
-Modified tests to have more consistent formatting (not sure if I got what you were after, but it looks more consistent to me now) and use the unity mrp in some cases
-Minor fixes (corrected the shape issue pointed out by @nmayorov , dropped use of the word "shadow" and updated docs accordingly, removed quat in the as_mrp calculation and just used a sign variable to make sure the set of MRPs being calculated corresponded to a rotation of <=180)

New update with latest feedback:

Used @nmayorov's provided definition for MRPs and cleaned up the language a little
Set Euler examples to use degrees
Moved denominator calculation outside of for loop in as_mrp
Other minor fixes (fixed copy/paste error spotted by @nmayorov, fixed formatting in test_rotation)

My latest changes seem to be causing some Windows failures, but I'm having trouble figuring out exactly what's going on. Any help?

My latest changes seem to be causing some Windows failures, but I'm having trouble figuring out exactly what's going on. Any help?

Not related to your changes, I should be able to fix shortly

It looks very good now, I'm merging.
Thank you for the contribution!

It looks very good now, I'm merging.
Thank you for the contribution!

Great working with you, looking forward to future contributions!

Thanks @nbelakovski . Please have a moment to boast about this in the release notes ;)
https://github.com/scipy/scipy/wiki/Release-note-entries-for-SciPy-1.6.0


error Arguments to path.join must be strings

hello~
when I run gradle sagan-client:npmInstall ,
This error appears:
bower meld#~1                                    error Arguments to path.join must be strings
npm ERR! sagan@ prepublish: bower install --config.interactive=false
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sagan@ prepublish script.
npm ERR! This is most likely a problem with the sagan package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bower install --config.interactive=false
npm ERR! You can get their info via:
npm ERR!     npm owner ls sagan
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "G:\develop\gradle-2.2.1\nodejs\node-v0.10.38-windows-x64\bin\node.exe" "G:\2015\workspace\sagan-master\sagan-client\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! cwd G:\2015\workspace\sagan-master\sagan-client
npm ERR! node -v v0.10.38
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm:sagan-client:npmInstall FAILED
how can I solve it.Please forgive my poor English.
thanks a lot.

i solve it by running  bower install --config.interactive=false  in cmd .thank you


When the bookmark is too much, open the stuck

System Details

OS: Windows 10 Version 22H2
Thorium Version: 128.0.6613.189

Problem
When the bookmark is too much, open the stuck
Such as
There are only 10 bookmarks under my Workspace folder, which is very smooth to open.
But I have 500+ bookmarks under my Issues folder, which is a bit stuck when it is opened.
https://github.com/user-attachments/assets/937b76da-1571-4207-8b28-adcdafd64160

@gz83 @a81n9 Yeah, I mean. The reason is you have too many bookmarks in one folder. It's not a prob with Thorium.


prepare release for 4.0.63

For now, you probably can do orbital with your local codegen?
Probably want to wait for Friday for a new release.

Sure, I'll do it locally.


swapRanges: Remove redundant constraint tests

Also fix related hasSwappableElements docs.
hasSwappableElements already tests for isInputRange.


Different URL's needed for destinations used with SAP Cloud SDK and CAP only

Hi CAP Team,
due to the OpenSAP forum question Connecting to ES5 I've invested some time  today to update my project epmbp-consumer-app. As I wanted to show the external service call using SAP Cloud SDK and CAP only I've discovered a difference on how the destination must be defined. The destination that is used by CAP directly has to point to the full URL of the OData Service. If instead the SAP Cloud SDK is used for the calls it is enough to have a generic destination which specifies only the base URL. The Cloud SDK adds the path to the OData Service.
I would hope for a way to add the path to service in the credentials section of the package.json#L40. Maybe there is already such an option but I haven't found it in the documentation.
Looking forward for a reply.
Best regards
Gregor

Hi,
To resolve this problem at a customer, I created a patch to allow configuration of different paths for a single destination. (as described in following question)
The code changes are minimal and can very easily be introduced in the code base using the patch command.
The patch can be found here.
Best regards,
Geert-Jan Klaps

Hi @geert-janklaps,
I've filed the issue 385711 / 2020 via the SAP Service Marketplace to get this hopefully included soon.
Best regards
Gregor


[Docs Bug 🐞 report]:

Describe the bug you found in AsyncAPI Docs.
Async is misspelled as Aync here and here
Attach any resources that can help us understand the issue.

https://github.com/asyncapi/website/blob/c3f18c5bb0d2142f0e580739d4032efa195d77f1/markdown/docs/concepts/asyncapi-document/tags.md?plain=1#L8
https://github.com/asyncapi/website/blob/c3f18c5bb0d2142f0e580739d4032efa195d77f1/markdown/docs/tools/generator/asyncapi-document.md?plain=1#L44

Code of Conduct

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

@eshinn would you like to work on  this issue?

@sambhavgupta0705 I would like to work on it


Unable to connect to Pluggable Database

I configured JasperReportIntegration on tomcat 10. When i connect it go pluggable database it not connect but when i connect it root container than it connected i checked password and every thing many times but not it not connected. please guide me.
when i connected with my pluggable database my conf/application.property have
[datasource:default]
type=jdbc
name=default
url=jdbc:oracle:thin:@<IP_ADDRESS>:1521:xepdb1
username=hll
password=hll
WHEN I CONNECTED ROOT CONTAINER (WHICH IS WORKING)
[datasource:default]
type=jdbc
name=default
url=jdbc:oracle:thin:@<IP_ADDRESS>:1521:xe
username=system
password=oracle

Change your url . For pdb, it is not a SID so you have to use '/'  instead of ':' for connecting to a service_name
[datasource:default]
type=jdbc
name=default
url=jdbc:oracle:thin:@<IP_ADDRESS>:1521/xepdb1
username=hll
password=hll

Thank you, @mikaelkael13 .
Yes, this is correct. I simply use the standard jdbc url syntax for connecting the database.
Does it work now?


Cleanup runtime platform classes

What does the pull request do?

Merges PlatformSupport project into the Avalonia.Base. AppBuilder was moved to the Avalonia.Controls. PlatformSupport was previously added temporary to simplify new android backends and before core libraries were merged.
Where possible NET6/NETSTANDARD implementations of runtime platform interfaces were used. To be specific:

Uses NativeLibrary to load library or export proc. Only NET6 (technically netcore3.0+, but still 'no' for us).
RuntimeFeature.IsDynamicCodeSupported to know if it's possible to load assembly or not. Only NET6 (was added with netstandard2.1).
~Marshal.AllocHGlobal instead of mmap on linux in UnmanagedBlob.~ Reverted after a discussion.

Removes legacy xamarin solution configuration (iPhoneSimulator, Ad-Hoc...). They are not used with new mobile backend, and we don't need them anyway.
Deprecated overload of AppBuilderBase.Start was removed (deprecated since 0.9.0)

Breaking changes
Only binary and only in nightly builds. So, no.

You can test this PR using the following package version. 0.10.999-cibuild0020671-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020694-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020754-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0021076-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Can't open files using VS Code when already one instance is running

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.026Z)
OS Version: Windows_NT ia32 10.0.16299
Extensions:

Extension
Author (truncated)
Version

Bookmarks
ale
0.18.0

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.4.3

gitlens
eam
6.3.0

tslint
eg2
1.0.24

vscode-npm-script
eg2
0.3.3

search-node-modules
jas
1.2.0

vscode-stylefmt
mrm
2.5.0

csharp
ms-
1.13.1

PowerShell
ms-
1.5.1

debugger-for-chrome
msj
3.5.0

stylelint
shi
0.31.0

nodejs-extension-pack
wad
0.1.9

JavaScriptSnippets
xab
1.5.0

html-css-class-completion
Zig
1.14.0

Steps to Reproduce:

Open Visual studio code.
Now Go to desktop and select any *.js file => right click => Open With => Select VS Code to open it. It will not be opened in Visual Studio code.

@kiluavineeth does an uninstall and reinstall of VS Code fix this?


compass project is technically wrong

This tutorial is technically wrong - the 'N' is not calculated correctly

Fixed at https://pxt.microbit.org/projects/compass. Please confirm fix is correct.

LGTM


Add feature of reviewerAssignment

Closes https://github.com/facebook/mention-bot/issues/127

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@wkentaro updated the pull request.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@wkentaro updated the pull request.

@wkentaro updated the pull request.

Yay, thanks :)
I'll merge it in if you add the trailing comma


Pass in background color to underlying webview

Issues addressed:

player.html flags a lint error, to fix it, i declared a variable var playerVars = "<<playerVars>>", and passed it into onYoutubeIframeAPIReady. This approach is similar to that of the variables platform and host. The issue is shown in the screenshot below

The backgroundColor parameter in the YoutubePlayerScaffold isn't used/passed in to the WebView of the YoutubePlayer

@sarbagyastha Do let me know what you think about this

Thanks


Do not stop timer in background; make it possible to cancel a cycle

Is your feature request related to a problem? Please describe.

It is not convenient to have phone with screen always on. Ticking time can be yet another way of distraction.
As for cancelling: sometimes you just have to abandon a cycle. Maybe you started one by accident, or got distracted it the middle and want to start again.

Describe the solution you'd like

I would suggest making it possible to lock the phone so that the timer would continue. Notifications would tell when the cycle has ended.
Just a button to cancel the current cycle (for example it can be somewhere on the screen of paused cycle).

// by the way, contributing.md is empty

// by the way, contributing.md is empty


URL doesn't work anymore

GET request to the URL fails.

@Aravindz which url are you referring to? https://openstreetmap.in/ works fine.

This url
https://{a,b,c}.tiles.mapbox.com/v4/openstreetmap.1b68f018/z/x/y.png?access_token=pk.eyJ1Ijoib3NtLWluIiwiYSI6ImNqcnVxMTNrNTJwbHc0M250anUyOW81MjgifQ.cZnvZEyWT5AzNeO3ajg5tg
This url was working until yesterday. But now this is not working. Can you please resolve it asap??

Unfortunately those tiles are no longer available due to a deprecation of a legacy Mapbox API which was used.
As a quick fix see if this works if you are using leaflet:
var map = L.map('map');

L.tileLayer('https://api.mapbox.com/styles/v1/{id}/tiles/{z}/{x}/{y}?access_token={accessToken}', {
attribution: '© Mapbox © OpenStreetMap Improve this map',
tileSize: 512,
maxZoom: 18,
zoomOffset: -1,
id: 'planemad/ckf4xcet7231819mm2e8njlca',
accessToken: 'pk.YOUR_MAPBOX_ACCESS_TOKEN'
}).addTo(map);

Get a free token from mapbox.com which should be sufficient for upto 50,000 tiles/month. Will try to document this in the repo so others can use it.


modified init gulpfile

updated browserSync usage and pipe main.web.js to root.

Hi,
I tried last night and found gulp file not modified for days.
Hope this pr can help something anyway.
Thanks for your awesome project.

Merged and published


Fix default Intl polyfill language

When we remove example app, default language is English, not German.

Coverage remained the same at 98.605% when pulling 0a5d7f37e38e0fbf29cadd8843c094e53e4dab6b on web2style:dev into dc42825d5400cf8994f92f663e767cca3d63f426 on mxstbr:dev.

Good catch, thank you!


ENH - Update workflows triggers

Since the CI takes so long, it does not make sense to run all the CI workflows when making docs-only changes.
This PR:

:construction_worker: CI should not run on docs
:wrench: Update conda recipe (forgot to update it recently when I updated the feedstock; please do not hate me)

Thank you, this looks brilliant :muscle:


Display a system message, when SageTV auto deletes a favorite recording.

Could you have SageTV display a system message, when SageTV auto deletes a favorite recording, when more disk space is needed? I did not realize that I had "AutoDelete" enabled for a favorite and SageTV was auto deleting recordings.

This could generate a huge amount of undesirable system messages for many users as this is part of normal behavior of the system (i.e. deleting recordings to create more disk space). So I don't think this would be a worthwhile addition.

If I have the "auto delete" favorite option disabled, SageTV displays a message that there is insufficient disk space. There could be an option to ignore certain system messages. An initial message that SageTV will begin auto-deleting recordings, would be nice.

There already are properties you can configure to ignore specific system
messages; but I would strongly recommend against ignoring the one about
being out of diskspace; because when that happens it will not record
anything more until diskspace is freed up...it effectively halts all
recordings when in that state.
On Fri, Apr 1, 2016 at 8:37 PM, 49studebaker<EMAIL_ADDRESS>wrote:

If I have the "auto delete" favorite option disabled, SageTV displays a
message that there is insufficient disk space. There could be an option to
ignore certain system messages. An initial message that SageTV will begin
auto-deleting recordings, would be nice.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/google/sagetv/issues/120#issuecomment-204638914

--
Jeffrey Kardatzke
<EMAIL_ADDRESS>Google, Inc.

An initial system message that SageTV needs to free up disk space and will begin deleting recording would be nice, or a system message that lists which recordings will be deleted to free up disk space.

It might be a better idea to highlight in red, the recordings that will be auto-deleted. Have the disk bar shows that xx recordings will be deleted in the xx:xx minutes to free space. Zap2it marked the new X-files episodes as reruns. If i would have known it was going to delete those recordings I would have moved them to external storage or deleted other recordings. Auto-delete is a nice feature, but it would be nice to know what recordings SageTV is going to auto-delete.

You can get a list from the web interface:
http://servername:8080/sage/Search?SearchString=&searchType=TVFiles&Video=on&DVD=on&search_fields=title&filename=&TimeRange=0&Categories=**Any**&Channels=**Any**&watched=any&dontlike=any&favorite=any&firstruns=any&hdtv=any&archived=any&manrec=any&autodelete=set&partials=none&sort1=airdate_asc&sort2=none&grouping=None&pagelen=100
If you use the link above it should have them in order of deletion given that it deletes oldest to newest. There's also a link on the web interface under Video Disk Space called Auto-Delete Recordings that will take you to a similar list.

Would it be difficult to mark the auto delete recordings with a red banner and also create a screen that lists the auto delete recordings?

Shouldn't be all that hard to do, you could probably write a plugin to do
it pretty easily.
Jeff Kardatzke
Sent from my Android
On Jan 20, 2017 11:26 PM, "49studebaker"<EMAIL_ADDRESS>wrote:

Would it be difficult to mark the auto delete recordings with a red banner
and also create a screen that lists the auto delete recordings?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/sagetv/issues/120#issuecomment-274246005, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANEIDHvi0d_WieEEGR3O7C7nsVaHNV_5ks5rUbMxgaJpZM4H9B4b
.


unpin some dependencies to allow this to install in the pangeo env

@rsignell-usgs this should solve your with qhub and the pangeo env. I ran all the upstream tests against the pangeo env and things works as expected.
@rmcd-mscb it would be nice if we could loosen more pins upstream.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ocefpaf I committed a new version to pypi.  I removed the poetry.lock file from the repo, and added python 3.8 to the classifiers and to the python dependencies. I'm open to other suggestions.    That should come in soon.

@ocefpaf I committed a new version to pypi. I removed the poetry.lock file from the repo, and added python 3.8 to the classifiers and to the python dependencies. I'm open to other suggestions. That should come in soon.

Let's try that first instead of this PR. I believe @rsignell-usgs can wait :-)


Implement Deep Neuron Network based on Keras interface of TensorFlow

Issue Description
What did you expect to see happen?
Add a new feature, i.e. deep neuron network, and new libraries TensorFlow
What did you see instead?
Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements? no impact
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users. not a defect
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.) yes

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

Approved for closure via #912