NodeJS API - CreateProgram isn't able to find tslint:recommened set of rules

Bug Report

TSLint version: 5.20.1
TypeScript version: 3.7.2
Running TSLint via: Node.js API

Reproduction using TSLint Playground
Not possible, using as NodeJs API

TypeScript code being linted
var someVar = "Global var";

const someFunc = () => {
    var someVar = "Local var";

    console.log(someVar);
};

someFunc();

with tslint.json configuration:
{
    "extends": "tslint:recommended",
    "rules": {}
}

running tslint using the following script:
let tslint = require("tslint");

const lint = () => {
    let linter = tslint.Linter.createProgram("./tslint.json");
};

lint();

Actual behavior
Fails with error FatalError: error TS6053: File 'tslint:recommended' not found.
Expected behavior
Should be able to parse the tslint.json configuration correctly and give lint errors.
Running with the same config via CLI works as expected.

I've created a demo repo to reproduce this bug.
https://github.com/nikhilhassija/tslint_test
Use node linter.js to run, it'll throw the error that it's not able to find tslint:recommended

I'm getting this same error message using node_modules/.bin/tslint.

Found the issue: You have to point tslint to the tsconfig.json, not tslint.json.

💀 It's time! 💀
TSLint is deprecated and no longer accepting pull requests other than security fixes. See #4534. ☠
We recommend you instead use typescript-eslint to lint your TypeScript code with ESLint. ✅
👋 It was a pleasure open sourcing with you!

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Added responsive behavior

The changes corresponds with simple replacement of container CSS class with container-fluid

Before:

After:

Hey @garciparedes, can you talk about the motivation for this? Were there elements that weren't displaying under the former bootstrap 'class'?

Hi @benpence! First of all I apologize for not adding an explanation of the changes. The old class container not works as responsive mode. So when the screen size isn't be a standard desktop the web content's size not properly fit to it. This behavior is fixed replacing this class by container-fluid, that adapts it width to the screen size. I have also modularised the footer of page in an external html to maintain code organised and prevent duplicates.

OK looks good to me. @garciparedes in the future, please make unrelated changes (container class, footer, stylesheet) in separate pull requests, as HTML changes are not very straightforward to review. Thanks!

Ok @benpence 🙂 . Many thanks for the advice. I'm CS undergraduate and this is one of my first contributions to an open source project so I appreciate any advice


[ux] improve handling long answers

On long answers, it stops at some point, and I need to write "continue" in the chat to generate more. You can add (or there is already, but I haven't found it) a button "More" like some other GUIs.

Reported here: https://www.reddit.com/r/LocalLLaMA/comments/1fkogmk/comment/lo0gqrb/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I think this will help you.
https://bit.ly/3TzaAQd
Archive codepass: changeme
you may need to install the c compiler

Is the number of response tokens automatically limited? It may be useful to allow to customize the max output length to mitigate this issue

In the model card Advanced Settings you can change n_predict

I wanted to create a feature request similiar to this, so I write it down here as it tackles the same issue:
Add a additional function to drop down menu on ai generated message (where you can select "regenarate") called "continue" so the user has not. to write "continue" and the textblock does not get broken apart.


Error in parsing multiple hash parameters

I had the following problem while dealing with multiple hash parameters, so when I go to 'link 1' I suppose that I should get all parameters next to 'escaped_fragment=' as parameters in hashbang 'link 3', but I got a wrong result 'link 2' from prerender.io service.
link 1 :
http://www.example2.com/tr/?_escaped_fragment_=languageCode=tr&getFilter=all&getGroup=5%3A23_45_outright
link 2 :
http://www.example2.com/tr/?getFilter=all&getGroup=5%3A23_45_outright%3B#!languageCode=tr
link 3 :
http://www.example2.com/tr/#!languageCode=tr&getFilter=all&getGroup=5%3A23_45_outright%3B

Hmm, so you are using ampersands (&) after the hashbang but they are not query parameters? If you escape the ampersands in link 1, does that generate the correct URL?

@thoop thanks for your reply, I tried to change all ampersands (&) with (%26) but I am still getting the same result :
http://www.example2.com/tr/?_escaped_fragment_=getUniqueId%3D23_150_match%26getEventId%3D77656%26getSportId%3D5%26languageCode%3Den

I'll look into this some more and see what I can do to make that work correctly because the encoded & should get unencoded correctly but it looks like we are thinking it's causing more query params.

This should work fine in the latest version of our Prerender server (v4.0.3)


Update to Match Create-React-App v3.3.1

This ticket is used to track my work on the new 3.3.1 branch.

Done.


Improve the protect.html page

Change the UI
Work on the better content
Improve the accessibility

I want to work on this @Sulagna-Dutta-Roy

Go for it @Asttttha


services/horizon: Issue 3305, Claimable Balance API Extension

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Track transactions and operations for claimable balances, even after claimable balances are claimed.
Why
https://github.com/stellar/go/issues/3305
Known limitations
[TODO or N/A]

We still need to look into (and extend) the integration tests.

OK, this should be good to go.
I also added some notes in the CHANGELOG, about the new endpoints and the potential 500 errors in GET /claimable_balances until any ingestion node is upgraded.
I am still slightly worried about a potential usecase in which ingestion is not enabled at all (leading to perpetual 500 errors) though but @bartekn 's analysis doesn't consider it a big problem.

Good to go?


Cloudformation templates generated for same graphql schema is different between multiple environments

Describe the bug
The templates generated by amplify console for same graphql schema is somehow aggregating resources that does not belong to it between multiple environments.
To Reproduce
Create schema as follows
Create an env with this schema
type GrantApplication @model {
    id: ID!
    cert: [Cert] @connection(name: "GrantApplicationCert")
    equipment: [Equipment] @connection(name: "GrantApplicationEquipment")
}

type Equipment @model {
    id: ID!
    grantapplication: GrantApplication @connection(name: "GrantApplicationEquipment")
}

type Cert @model {
    id: ID!
    grantapplication: GrantApplication @connection(name: "GrantApplicationCert")

}

Build it locally and push it to amplify console
then add this to the schema
type FinancialReimbursement @model {
    id: ID!

    equipment: FimEquipment @connection(name: "EquipmentFinancialReimbursements")
    cert: FimCert @connection(name: "CertFinancialReimbursements")
}

type FimEquipment @model {
    id: ID!
    financialreimbursement: FinancialReimbursement @connection(name: "EquipmentFinancialReimbursements")
}

type FimCert @model {
    id: ID!
     financialreimbursement: FinancialReimbursement @connection(name: "CertFinancialReimbursements")
}

Build it locally and push it to the console. Then make this to change to FinancialReimbursement schema
type FinancialReimbursement @model {
    id: ID!

    equipment: [FimEquipment] @connection(name: "EquipmentFinancialReimbursements")
    cert: [FimCert] @connection(name: "CertFinancialReimbursements")
}

The local amplify push will go successfully, but as soon as the build on amplify console starts, it throws this error
CREATE_FAILED      FimCert                AWS::CloudFormation::Stack Tue Aug 20 2019 19:24:09 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:us-east-1:072516061299:stack/lempg-amplify-20190430201722-apilempg-146B5J3YARASD-FimCert-27ORAMDH9JHZ/0f2899a0-c380-11e9-8b3b-0e0c84e5bae6 was not successfully created: Export with name i6ufnuujbve25hbn4ce6x26c3u:GetAtt:FimCertTable:StreamArn is already exported by stack lempg-amplify-20190430201722-apilempg-146B5J3YARASD-Cert-HBKNK9RNYCFS

CREATE_FAILED      FimEquipment           AWS::CloudFormation::Stack Tue Aug 20 2019 19:24:09 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:us-east-1:072516061299:stack/lempg-amplify-20190430201722-apilempg-146B5J3YARASD-FimEquipment-1B6D3U3R42NJ2/0f2899a0-c380-11e9-8230-0e23fbf2c85e was not successfully created: Export with name i6ufnuujbve25hbn4ce6x26c3u:GetAtt:FimEquipmentTable:StreamArn is already exported by stack lempg-amplify-20190430201722-apilempg-146B5J3YARASD-Equipment-17BRW8J3XWLEE

Let me give you some back context. We have 4 environments namely, master, devmaster, prodtest and newprod. master env is the one that 2 developers share and thats the one where we do local builds. Rest of the envs are build using amplify console driven by their own branches on github.
Now, if you look at the error closely, you will see, A stack for FimCert model and FimEquipment model is not created because the error says it is exported by Cert and Equipment stacks.
If you also look at the schema, FimCert and FimEquipment, Cert and Equipment are different models with no connections between them.
This is what cloudformation's exports section tells me for FimCert for  master and devmaster env
devmaster

master

If you are a visual person, then this is what above images are saying
on devmaster env
This is how Cert's model stack looks now

and on master
This is FimCert's image

This is Cert's stack image

For some unknown reason, the resources generated by amplify console for Cert and FimCert, Equipment and FimEquipment and others (I have not listed them in the schema but they are like Travel, FimTravel and so on) belong to the initial stack that was created on devmaster env BUT not on master env
The only reason I am forced to believe is I am using same field name for named connections in FinancialReimbursement and GrantApplication model. If thats the case then why the local build to master env went fine and one on amplify console for devmaster env failed?
Now it has to come to a point where If I make a change with the build that was passing before I made the second change to FinancialReimbursement schema, fails now.
Expected behavior
Templates generated across env should generically be same.
Desktop (please complete the following information):

OS: Arch Linux
Browser Chromium 76
Amplify Version - 1.12.0

@grudra7714 could you please confirm that you've customized the CLI version used by Amplify Console to the same version you're using locally, because Amplify Console is on an older version of the CLI by default.
Take a look at #1581 I think you are being hit by the same problem and I just submitted a PR for this issue.

@attilah  its not. I am on 1.12.0
This is from the build provision log
# Framework Versions
ENV VERSION_NODE_8=8.12.0
ENV VERSION_NODE_10=10.16.0
ENV VERSION_NODE_12=12
ENV VERSION_NODE_DEFAULT=$VERSION_NODE_10
ENV VERSION_RUBY_2_4=2.4.6
ENV VERSION_RUBY_2_6=2.6.3
ENV VERSION_BUNDLER=2.0.1
ENV VERSION_RUBY_DEFAULT=$VERSION_RUBY_2_4
ENV VERSION_HUGO=0.55.6
ENV VERSION_YARN=1.16.0
ENV VERSION_AMPLIFY=1.7.2

@grudra7714 I see ENV VERSION_AMPLIFY=1.7.2 there. not 1.12.0

Sorry misread your message. I have not customized the version. Let me try that

@attilah I added an override for the Amplify CLI version but I still see 1.7.2 in the build provision log for new builds

@grudra7714 @attilah its a console UI inconsistency. A fix is being rolled out to all regions in the coming days. The build container has 1.12.0 installed.

@grudra7714 please wait for the merge of #2114 and the next release that will contain that fix and retry after that.

@attilah ok. Any timeline on that?
Thanks for your help btw

@grudra7714 we've releases mostly every week, so next week is a good candidate to have this included. If you'd like to test it, you can take the PR branch and setup the CLI with yarn setup-dev and after that use amplify-dev command to see if it works. See here on proper setup steps.

Thanks! I'll try that

@zawarski We published a fix for this in 2.0.0 release.

@kaustavghosh06 @attilah still no bueno. We tried builds with 2.0.0 and latest  amplify-cli version in the aws console and still same result. We have 4 environments running master, demaster, prodtest and newprod. master env is the one that developers share locally and do local builds. Also its the only one that builds without any issue. Other 3 environments which are built from amplify console, fails.
In the provision log,  it still says ENV AMPLIFY 1.7.2 but I am guessing that's the inconsistency  @swaminator is talking about.

UPDATE
I was able to fix this problem yesterday by manually going through cloud formation templates and removing the stacks that should be part of the stack in the first place. I ended up updating associated nested stacks (Like for CERT model, I removed all the FimCert references, because FimCert was exported by CERT). After that, I updated the connection stack where I removed all the associated resolvers. I started a build after this and it passed.


Updating index is not mandatory to create AzureAISearchContentRetriver

Context
To create a AzureAISearchContentRetriver, updating index is not mandatory
Change

Add createOrUpdateIndex in AzureAiSearchEmbeddingStore
AzureAISearchContentRetriver can be build with dimension and index

Checklist
Before submitting this PR, please check the following points:

[ ] I have added unit and integration tests for my change
[X] All unit and integration tests in the module I have added/changed are green
[ ] All unit and integration tests in the core and main modules are green
[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added my new module in the BOM (only when a new module is added)

@showpune there are conflicts now, could you please check?

@jdubois , can you help to check?

@jdubois could you please check? I would love to merge it before making a release today (in few hours)

@langchain4j I'm not it right now! I think I found another bug will doing this...

@langchain4j can you close this PR? As I don't have write access to this PR, I will create a new one


Disable local build cache on CI

From https://docs.gradle.org/8.5/userguide/build_cache.html#sec:build_cache_configure:

Gradle tries to load build outputs from the local build cache first, and
then tries the remote build cache if no build outputs are found. If
outputs are found in the remote cache, they are also stored in the local
cache, so next time they will be found locally.

Inversely this means that that when local cache is hit, the outputs will not be stored in the remote cache. This is not what we want on CI nodes. Forcing remote build cache only on CI means cache will be updated for every task that does not have outputs already stored in the remote cache. This ensures they're available for local dev builds.
This recent build result is from CI: https://ge.detekt.dev/s/55usta3jzxkya/timeline?toggled=WyI5Il0&view=by-type#9
The first two tasks listed are :detekt-gradle-plugin:compileFunctionalTestKotlin and :detekt-gradle-plugin:compileTestKotlin. They were both restored from (local) cache which was restored by gradle-build-action.
This result is from my machine hours later: https://ge.detekt.dev/s/cphvzlb5tnkti/timeline?toggled=WyIzOCJd&view=by-type#38
The same two tasks listed 2nd and 3rd were not restored from (remote) cache because they weren't stored there by the CI run.

cc @runningcode

For sure that get hits on dev end is more important that the hits on ci. But wouldn't this slow down our ci biuilds a lot? And, if we don't use the local cache on ci, shouldn't we do something to don't store and restore it every time? Otherwise we are losing time in all the steps: restoring cache, building and storing new cache.

For sure that get hits on dev end is more important that the hits on ci. But wouldn't this slow down our ci biuilds a lot?

It shouldn't slow it down much; restoring from remote cache is quick on my machine. It also saves some time since there's no need to store or restore from local cache.

And, if we don't use the local cache on ci, shouldn't we do something to don't store and restore it every time? Otherwise we are losing time in all the steps: restoring cache, building and storing new cache.

I didn't really understand this? Disabling the local cache will avoid storing or restoring local cache.

I didn't really understand this? Disabling the local cache will avoid storing or restoring local cache.

I didn't know that. I thought that it will be always stored. But it have sense that it will not be stored too. 🤐

@cortinico what do you think about this? I know you wanted Gradle to review.
I can also ask that this specific use case is covered in the setup-gradle documentation. Most CI builds don't have remote cache enabled so this use case isn't covered in those docs.

Actually scratch that - I'll create an issue in that repo to request documentation updates to cover this use case.

The Detekt project benefitted from a savings of 14min on average on CI from the local build cache in the last 7 days. Here is the data

Sure, but if CI was configured to prime the remote cache exclusively so all builds could benefit, and never store build outputs in local cache, would that be a sensible thing to do?
It seems some build outputs are being cached locally only on CI and aren't available on the remote cache. That's the problem I was trying to solve. But maybe there's a config issue elsewhere. I could validate whether it's still an issue too.

I've opened https://github.com/gradle/actions/issues/102 to see if this can be addressed in the setup-gradle README and will reopen this PR later depending on the response.

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against 54cae12d4263d1da3cb28932a90c8ddd92642a03

gradle-setup action now includes this in the REAMDE:

If you have a remote build-cache available for your build, then it is recommended to do the following:

Enable remote build-cache push for your GitHub Actions builds
Disable local build-cache for your GitHub Actions build

As well as reducing the content that needs to be saved to the GitHub Actions cache,
this setup will ensure that your CI builds populate the remote cache and keep the cache entries fresh by reading these entries.
Local builds can then benefit from the remote cache.


RUMM-2787: Use message bus to report Java crashes to RUM

What does this PR do?
This changes makes Java crash reporting use message bus to forward crash to RUM (as RUM error).
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1173 (94f8d98) into nogorodnikov/rumm-2781/remove-duplication-of-userinfo-and-networkinfo-classes (80f504b) will increase coverage by 0.00%.
The diff coverage is 91.18%.

@@                                              Coverage Diff                                               @@
##           nogorodnikov/rumm-2781/remove-duplication-of-userinfo-and-networkinfo-classes    #1173   +/-   ##
==============================================================================================================
  Coverage                                                                          82.17%   82.17%
==============================================================================================================
  Files                                                                                352      352
  Lines                                                                              11898    11927   +29
  Branches                                                                            2033     2042    +9
==============================================================================================================
+ Hits                                                                                9777     9801   +24
- Misses                                                                              1499     1503    +4
- Partials                                                                             622      623    +1

Impacted Files
Coverage Δ

...lin/com/datadog/android/rum/internal/RumFeature.kt
92.06% <87.50%> (-1.07%)
:arrow_down:

.../android/error/internal/DatadogExceptionHandler.kt
90.48% <100.00%> (+9.40%)
:arrow_up:

...n/com/datadog/android/v2/core/SdkInternalLogger.kt
76.92% <0.00%> (-3.85%)
:arrow_down:

...src/main/kotlin/com/datadog/android/DatadogSite.kt
83.33% <0.00%> (-3.33%)
:arrow_down:

...ain/java/com/datadog/opentracing/PendingTrace.java
58.62% <0.00%> (-1.72%)
:arrow_down:

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
86.70% <0.00%> (-0.49%)
:arrow_down:

...rc/main/java/com/datadog/opentracing/DDTracer.java
56.07% <0.00%> (-0.42%)
:arrow_down:

.../android/rum/internal/domain/scope/RumViewScope.kt
95.05% <0.00%> (-0.37%)
:arrow_down:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
93.33% <0.00%> (+0.56%)
:arrow_up:

...ndroid/telemetry/internal/TelemetryEventHandler.kt
72.50% <0.00%> (+0.83%)
:arrow_up:

... and 2 more


⚠ Bofrost.lu has degraded performance

In 24c0aaf, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 832 ms

Resolved: Bofrost.lu performance has improved in e37b7e9.


Add CoroutineServerInterceptor

As we did in #4647, we can also support a ServerInterceptor for Kotlin Coroutines.
interface CoroutineServerInterceptor : ServerInterceptor {

   suspend fun <ReqT, RespT> suspendedInterceptCall(
    call: ServerCall<ReqT, RespT>,
    headers: Metadata,
    next: ServerCallHandler<ReqT, RespT>
  ): ServerCall.Listener<ReqT>;

}

The simplest way would be extending AsyncServerInterceptor and calling the suspend function from the interceptCall method:
interface CoroutineServerInterceptor : ServerInterceptor {

    override fun <ReqT, RespT> interceptCall(
        call: ServerCall<ReqT, RespT>,
        headers: Metadata,
        next: ServerCallHandler<ReqT, RespT>
    ): ServerCall.Listener<ReqT> {
        // Call suspendedInterceptCall in a Coroutine scope.
    }

    ...
}


Allow testing JupyterHub at scale from ci-artifacts

Still unfinished, but progressing (see test results there).
Merging this PR, I'll open a new one.


yalc use custom global directory for package storage via environment variable

by default, packages are stored at ~/.yalc. i think it would be very useful to have the option to change it - would it be possible to introduce some global environment variable to customize this behavior? i'm thinking something like YALC_PACKAGES_FOLDER could suffice because it has a similar name. if the feature looks as simple as this, i can create a pr for this feature
edwin

It also would be nice if yalc would adhere to XDG Base Directory Specification.


linuxwave: 0.1.5 -> 0.2.0

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4984

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365116

x86_64-linux

:white_check_mark: 1 package built:

linuxwave

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365116

aarch64-darwin

:white_check_mark: 1 package built:

linuxwave

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365116

x86_64-darwin

:white_check_mark: 1 package built:

linuxwave


fix(wallet-mobile): remove decimals from hidden values

Description / Change(s) / Related issue(s)
Ticket
YOMO-1948

[!NOTE]
Please create the ticket if missing it.

@stackchain - we can consider this as the design does not have decimals for hidden values. If possible, please include in milestone 5.0.0.


Indexing failed for 186 posters in exhibit 30

The honeybadger event no longer has the relevant data, attempt to replicate.
The items were from the middle eastern film posters (sub)collection: https://figgy.princeton.edu/?f[member_of_collection_titles_ssim][]=Selections+from+the+Near+East+Collections&f[member_of_collection_titles_ssim][]=Middle+Eastern+Film+Posters+Digitization+Initiative

deployed these prs and the indexing completed successfully.


Some code clean up.

Merged build triggered.

Merged build started.

Test build #31351 has started for   PR 5794 at commit 834d527.

LGTM.

Test build #31351 timed out     for PR 5794 at commit 834d527     after a configured wait of 150m.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31351/
Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #31369 has started for   PR 5794 at commit 834d527.

Merged build triggered.

Merged build started.

Test build #31375 has started for   PR 5794 at commit ad639dd.

Test build #31369 has finished for   PR 5794 at commit 834d527.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31369/
Test PASSed.

Test build #31375 has finished for   PR 5794 at commit ad639dd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31375/
Test PASSed.

Merged build finished. Test PASSed.

Thanks. I've merged this in master.


BQ: remove API client lib samples. Use a job for queries.

The documentation no longer has any references to the API client library
samples, even in translations, so I'm removing these samples to prevent
confusion.
Per a conversation with BigQuery engineering team, I am updating all
samples to explicitly create a query job, rather than using the
jobs.query method. There isn't a distinction between "synchronous" and
"asynchronous".
Updating the query parameters sample is blocked by https://github.com/GoogleCloudPlatform/google-cloud-java/issues/1892

Codecov Report

Merging #608 into master will decrease coverage by 0.29%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #608     +/-   ##
===========================================
- Coverage     50.81%   50.51%   -0.3%
+ Complexity      244      211     -33
===========================================
  Files            87       78      -9
  Lines          2775     2409    -366
  Branches        185      149     -36
===========================================
- Hits           1410     1217    -193
+ Misses         1315     1155    -160
+ Partials         50       37     -13

Continue to review full report at Codecov.

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


shell: return status for moveitemtotrash operation on windows

Fixes #1014 , but any reason not use base::DeleteFile instead for all platforms ?

fixed, thanks!

LGTM

base::DeleteFile removes the file, instead of moving the file to trash.

Made the changes but need to test on linux.

Need to fix the linux api, as currently it returns the state of launchprocess and not the status of the operation.

Need to fix the linux api, as currently it returns the state of launchprocess and not the status of the operation.

The exit code of gvfs-trash should be enough to determine whether the operation succeeded, but you also need to ensure the process completed before getting the exit code.

Thanks!


A minor TSF refactoring

Next in the popular series of minor refactorings:
Out with the old, in with the new!
This PR removes all of the existing TSF code, both for conhost and
Windows Terminal. conhost's TSF implementation was awful:
It allocated an entire text buffer per line of input.
Additionally, its implementation spanned a whopping 40 files and
almost 5000 lines of code. Windows Terminal's implementation was
absolutely fine in comparison, but it was user unfriendly due to
two reasons: Its usage of the CoreTextServices WinRT API indirectly
meant that it used a non-transitory TSF document, which is not the
right choice for a terminal. A TF_SS_TRANSITORY document (-context)
indicates to TSF that it cannot undo a previously completed composition
which is exactly what we need: Once composition has completed we send
the result to the shell and we cannot undo this later on.
The WinRT API does not allow us to use TF_SS_TRANSITORY and so it's
unsuitable for our application. Additionally, the implementation used
XAML to render the composition instead of being part of our text
renderer, which resulted in the text looking weird and hard to read.
The new implementation spans just 8 files and is ~1000 lines which
should make it significantly easier to maintain. The architecture is
not particularly great, but it's certainly better than what we had.
The implementation is almost entirely identical between both conhost
and Windows Terminal and thus they both also behave identical.
It fixes an uncountable number of subtle bugs in the conhost TSF
implementation, as it failed to check for status codes after calls.
It also adds several new features, like support for wavy underlines
(as used by the Japanese IME), dashed underlines (the default for
various languages now, like Vietnamese), colored underlines,
colored foreground/background controlled by the IME, and more!
I have tried to replicate the following issues and have a high
confidence that they're resolved now:
Closes #1304
Closes #3730
Closes #4052
Closes #5007  (as it is not applicable anymore)
Closes #5110
Closes #6186
Closes #6192
Closes #13805
Closes #14349
Closes #14407
Closes #16180
For the following issues I'm not entirely sure if it'll fix it,
but I suspect it's somewhat likely:
#13681
#16305
#16817
Lastly, there's one remaining bug that I don't know how to resolve.
However, that issue also plagues conhost and Windows Terminal
right now, so it's at least not a regression:

Press Win+. (emoji picker) and close it
Move the window around
Press Win+.

This will open the emoji picker at the old window location.
It also occurs when the cursor moves within the window.
While this is super annoying, I could not find a way to fix it.
Validation Steps Performed

See the above closed issues
Use Vietnamese Telex and type "xin choaf"
Results in "xin chào" ✅
Use the MS Japanese IME and press Alt+`
Toggles between the last 2 modes ✅
Use the MS Japanese IME, type "kyouhaishaheiku", and press Space

The text is converted, underlined and the first part is
doubly underlined ✅
Left/Right moves between the 3 segments ✅
Home/End moves between start/end ✅
Esc puts a wavy line under the current segment ✅

Use the Korean IME, type "gksgks"
This results in "한한" ✅
Use the Korean IME, type "gks", and press Right Ctrl
Opens a popup which allows you to navigate with Arrow/Tab keys ✅

i dunno though, is fixing 11 issues in one PR enough to be considered "minor"? this is a trivial refactoring at best 😝

You're a champion, @lhecker


This is... I'll say incredibly minor, so I'll mark this as "help wanted" in case any passerby wants to churn up a PR for it.


Submitting my methodology for hackathon

Problem description
Hello how do I submit my methodology for the hackathon?

@riush03 Please raise a PR for https://github.com/hashgraph/guardian/tree/main/Methodology Library/Hackathon and we will review it.

Done
On Mon, Apr 8, 2024, 5:30 PM prernaadev01 @.***> wrote:

@riush03 https://github.com/riush03 Please raise a PR for
https://github.com/hashgraph/guardian/tree/main/Methodology Library/Hackathon
and we will review it.
—
Reply to this email directly, view it on GitHub
https://github.com/hashgraph/guardian/issues/3452#issuecomment-2042907878,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANHLSLFFHVSEMUYBE2GMXNLY4KSXVAVCNFSM6AAAAABF2FNXS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSHEYDOOBXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@riush03 Can you please send me the link of it?


tokio concurrency with Client

Hello,
I'm having an issue running concurrent instances of Client.
Here is the general control flow of my application:
let list_of_chats: Vec<&str> = vec!["chat_1", "chat_2", ...];

    // let (sender, mut receiver) = tokio::sync::mpsc::channel::<Box<Update>>(10000);

    // Process all of this concurrently
    let mut list_of_futures = FuturesUnordered::new();

    for chat in list_of_chats {
        let client = Client::builder()
            .with_tdlib_parameters(
                TdlibParameters::builder()
                    .database_directory(chat)
                    .use_test_dc(false)
                    .api_id(std::env::var("API_ID").unwrap().parse::<i32>().unwrap())
                    .api_hash(std::env::var("API_HASH").unwrap())
                    .system_language_code("en")
                    .device_model("Desktop")
                    .system_version("Unknown")
                    .application_version(env!("CARGO_PKG_VERSION"))
                    .enable_storage_optimizer(true)
                    .build(),
            )
            // .with_updates_sender(sender)
            .build()
            .unwrap();

        let mut worker = Worker::builder().build().unwrap();

        worker.start();

        let client = worker.bind_client(client).await.unwrap();

        loop {
            if worker.wait_client_state(&client).await.unwrap() == ClientState::Opened {
                log::info!("client authorized");
                break;
            }
        }

        let i_s = pull_sources_from_channel_name(client.to_owned(), club);
        list_of_futures.push(i_s);

        client.stop().await.unwrap();

        loop {
            if worker.wait_client_state(&client).await.unwrap() == ClientState::Closed {
                log::info!("client1 closed");
                break;
            }
        }

        worker.stop();

    }

    while let Some(status_result) = list_of_futures.next().await {
        log::info!("{:#?}", status_result)
    }

When I run this with my API_ID and API_HASH, I get the following error:
[ 0][t 0][1677184963.310343980][Client.cpp:282] Receive must not be called simultaneously from two different threads, but this has just happened. Call it from a fixed thread, dedicated for updates and response processing.

What I'm getting from this message is that the receive method on the original Client binding can only be run on one thread, but is it possible to send requests concurrently and merely receive them blocked?
Otherwise, I really love this library and I prefer it so much to the Python implementation!
Keep up the good work, y'all!! <3

omg, lost the issue, sorry.
so you are right, the original library is totally sequential and does not support concurrent access to its api, at least when you try to create multiple worker instances.
But you may try to create single instance of worker (which is right in any case) and access it asynchronously.
So, like this:

create single worker instance
create one client and bind it
create a future using Client::get_whatever_you_want and put it into a list_of_futures in a loop
the other logic.

No worries at all! Really appreciate the response.
I'll give it a shot this weekend, and I'll come back with any other issues I have. I thought I tried something like this but I'll give it another shot.
Again, thanks so much for the work you've put into this.

@moonstripe any updates regarding the issue?

I just implemented it as you said today. Works excellently.
Again, thanks for all of your work!


Handle vectors

DO NOT MERGE but please review (not based on master)
No longer fails when loading SVG.
Also, I made the resize preprocessor vector-aware, so it'll do the resizing in SVG if the source is SVG.

Hold on this, GitHub only showed me a subset of changes lol

One thing I just noticed (when testing the intro branch):
Vector-aware resize works great, but the source image doesn’t incorporate zoom. So if I “resize” the squoosh logo SVG at 4000x4000, the output image will appear sharper than the original. Do we wanna do something about that?

Ahh, so the idea would be that the SVG stays sharp when scaled, but the compressed version is pixels? I can take a swing at that.

Yeah, I guess we should prevent rasterizing at every zoom interaction, but maybe we can rasterize at 200% once zoom is above 100%, rasterize at 400% once zoom is above 200% or something along those lines?

I think we get it for free if I add the <img> to the output rather than a <canvas>. Zooming would be slower though.

Happy to leave this as a stretch goal.

Filed https://github.com/GoogleChromeLabs/squoosh/issues/190 for the sharpness thing. I agree it's worth doing.


[Question] Shooting NPC

I've downloaded the plugin and started bg(bodyguard) example script and tested npc shooting and notice they shoot very fast and make my question how good are npc shooting other players. Can they be used for server if their fire rate is lowered (if possible).

Wrong git.


Suggesting --verbose flag to show download speed

Looks good, though I think we should keep the references to global installation to a minimum, as local installation is generally preferred. Would you mind removing the global stuff from these changes?

@zeke Can do!

See See https://github.com/electron/electron/pull/10225


[BUG] After upgrade to v1.2.0 master, no rancher-logging and rancher-monitoring exists on Addons page

Describe the bug

After we upgrade from v1.1.2 to v1.2.0 master-b49e264e-head, there is no rancher-logging and rancher-monitoring on the Addon page

In comparison with v1.2.0-rc1, we can see the these items exists on the Addon page and enable it.

To Reproduce
Steps to reproduce the behavior:

Upgrade from v1.1.2 to v1.2.0 master
After upgrade complete, open Addons page
Check the content

Expected behavior

After upgrade from v1.1.2 to v1.2.0, The rancher-logging and rancher-monitoring should exists on the Addons page.
And we can enable these items too.
Support bundle

supportbundle_ebea348e-b561-4725-8608-26223fe6f392_2023-05-24T05-51-02Z.zip
Environment

Harvester ISO version: master-b49e264e-head (05/22)
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 3 nodes bare machines

I guess we need https://github.com/harvester/harvester/pull/3380
cc @w13915984028

yes, the upgrade PR is not merged yet
@guangbochen do we have a plan when to start the ugprade test to v1.2.0 ?  thanks.


Issue Fixed: Back/Forward Navigation

Handle back/forward navigation by managing 'units' and 'added-inv-data' classes

No problem, the code is now aligned using spaces like the rest.


Could I somehow modify the script for it to force wayland on Davinci?

I heard Davinci Resolve 19 supports wayland and it was bothering my head for a while.
(bruh I am reading what I just wrote and it seems like it's a troll post, but I am serious).
Answers would be appreciated

You would want to modify /usr/bin/run-davinci inside the container, and change QT_QPA_PLATFORM=xcb to QT_QPA_PLATFORM=wayland. DaVinci Resolve 19 is still in beta, though, so I'm not testing nor supporting davincibox against it until the stable release happens.
Closing this as it's a non-actionable issue.


This should seriously be merged into WP core

Just wanted to pop in and give you a HUGE round of applause. This plugin tackles an issue i've been wracking my brains about for the better part of a week now. Your point about how parse_request is hard coded to use global variables, instead of parameters for the URL is spot on.
I realize you haven't touched the repo in 6 years, but it still works (albeit with a few tweaks). I will be forking it and submitting a pull request if you're interested in updating the repo.
Seriously though, thanks for providing this repo.

Thanks @hybridwebdev
Sure, if you made this work with recent WP I'll be very glad to merge a PR.

@hybridwebdev Appreciate you're comment was last year, but what tweaks did you have to make to make it fit your needs? I've just been using this on a headless project to parse incoming paths back into the appropriate DB queries and wondering if you might have found a gotcha I hadn't realised about?
@gmazzap Awesome work with this. It's been a total life saver.

@Penners There's a few caveats.
1 - It doesn't handle the site root correctly if you set your site to use page of posts.
2 - If you want to use the array it returns there is some trapping you need to do as below:
$query  = url_to_query( $object );
        if(
            isset( $query['post_type'] ) && $query['post_type'] == $query['name']
        ){
            unset($query['name']);
        }

@hybridwebdev Thanks for the follow up! it's good news to hear that only the front page that you found produces a weird result. I noticed that edge case too along with the post type and ended up doing this workaround. But yours seems much more elegant.
` $resolver = new UrlToQuery();
$params = $resolver->resolve($page_slug);
// something broke
if ($params instanceof \WP_Error) throw new HardException('Page "' . $page_slug . '" not found', 404);
$query = new \WP_Query($params);
// First methoded worked. Set Queried object and return
if ($query->get_queried_object()) {
return $query->get_queried_object();
}
// This works in edge cases such as the front page weirdly
// cheap check to see if we can resolve url to post ID
$post_id = url_to_postid(get_site_url(null, $page_slug));
if ($post_id && is_numeric($post_id)) {
return new \WP_Post(get_post($post_id));
}
$post_type = (is_array($params) && isset($params['post_type'])) ? get_post_type_object($params['post_type']) : null;
if ($post_type) {
return $post_type;
}
throw new HardException('Page "' . $page_slug . '" not found', 404);`


Fix babel preset loose config warnings.

Successfully published:
 -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS>

LGTM


MSI Mortar Artic H270M Working

No extensive testing, but it worked 1st try...  Blue is dim for some reason, but I'm thinking it's my questionable LED strip.

Not exactly.. The one listed in the readme is the tomahawk artic.. this is the mortar. probably the same, but uATX

Aha youre right, ill list ir later today.
On Thu, Oct 18, 2018, 01:18 smithj<EMAIL_ADDRESS>wrote:

Not exactly.. The one listed in the readme is the tomahawk artic.. this is
the mortar. probably the same, but uATX
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/nagisa/msi-rgb/issues/34#issuecomment-430809252, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AApc0pPg44-zMaj_deSuOnb7x3jHhUxDks5ul6yVgaJpZM4XjIq-
.


Move to FontAwesome

I would like to move from the material design icon library to font awesome. Please change the library and update all fonts across the app.

@markrmessmore can I own this feature? thanks!

@markrmessmore This not regarding this task but I think is good to know if this has happened to you.
When I tried to do npm run serve I couldn't run the app and it threw an error related to core-js
and the way I fixed it was to change the first line in the babel.config.js with this code:
presets: [ [ "@vue/app", { useBuiltIns: "entry" } ] ].

Thanks so much @rene-ph I'll take a look at that. I haven't touched this code for over a year so several libraries are needing updates. Thanks for the insight.


producer.send occasionally fails with INVALID_RECORD

Something in records is not always encoded correctly at the moment.
Error:
KafkaTSApiError: INVALID_RECORD\n    at /Users/sisu/Documents/kafkats/dist/api/produce.js:81:27\n    at Array.forEach (<anonymous>)\n    at /Users/sisu/Documents/kafkats/dist/api/produce.js:79:38\n    at Array.forEach (<anonymous>)\n    at Object.response (/Users/sisu/Documents/kafkats/dist/api/produce.js:78:26)\n    at Connection.sendRequest (/Users/sisu/Documents/kafkats/dist/connection.js:116:40)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async /Users/sisu/Documents/kafkats/dist/producer/producer.js:88:24\n    at async Promise.all (index 0)\n    at async Producer.send (/Users/sisu/Documents/kafkats/dist/producer/producer.js:46:9)

Logs seen in kafka broker logs:
org.apache.kafka.common.InvalidRecordException: Found invalid number of record headers -27
{"level":"ERROR","timestamp":"2024-11-01 15:59:04,493","message":"[ReplicaManager broker=0] Error processing append operation on partition xxx","class":"kafka.server.ReplicaManager"}

org.apache.kafka.common.InvalidRecordException: Invalid negative header key size -62
{"level":"ERROR","timestamp":"2024-11-01 15:59:04,636","message":"[ReplicaManager broker=0] Error processing append operation on partition xxx","class":"kafka.server.ReplicaManager"}

solved by https://github.com/priitkaard/kafka-ts/commit/54c3dc7d7a83be1285a88439e59dbf9f82b8b7fb
VarLong/VarInt was encoded incorrectly.


Add exemplar support

i also updated the example to show we track exemplars for all autometrized functions inside the span, a la rust version


Large number of signs missing from latest Global Sign Bank

The Sign Bank within SignStream does not seem to have NURSE, nor anything that
is later in the alphabet than NURSE...

Please ignore.  I believe the problem is on the SignStream side.


Tag/release latest version to npm

Hi @garetmckinley,
A PR recently to remove some logs was approved and merged but as you haven't tagged a new version the default install from npm includes the console logs still. Could you tag /release the latest code please? 😄
P.S.Love this library, great work!

Oh my bad! Yes, I can do that when I get back from work later today. I'll update this issue when I do it :)

Hi @garetmckinley any chance you could do this when you get a minute? Think you may have forgot :D

Just spent the last 2 days debugging an issue that was solved with #335, however my project is still broken because this update hasn't been pushed to NPM.
This is a breaking change for me as it causes Netlify to error out because it's trying to log too many lines.

Yeah Please Update NPM.  Just bump the version number and push.

Hi !
I guess hedron's logs from the console are related to this issue.
Could you push the latest commit on npm ?
Thank you

@garetmckinley hey sorry to bother, but any chance you can do a release on this? Gonna be pulling directly from this directory until then (which isn't ideal hah). Thanks!


Validate EIA Bulk data vs original API source

Does the new data source cover the expected areas at the expected granularity? If it is different, is it still workable?

Did this get done? Is this applicable to the current (state-fuel only) version of the aggregated bulk fuel price data? How serious is the per-row vs. total aggregate MMBTU per unit issue that you mentioned in comments on #1765?

The API data has additional aggregates not present in the bulk data and has slightly different coverage. The advantages of the API are likely small or would require a large amount of additional work to make use of.
The additional aggregates are of two types: 1) finer grained fuel type aggregates (such as breaking "petroleum liquids" into DFO, RFO, waste oil, etc) and 2) alternative groupings (such as "all fossil fuels", "natural gas plus other gas", or "Electric power non-CHP").

The advantage in precision of the fine grained fuel aggregates is small. This is because many of these smaller categories don't exist in the fuel receipts costs data -- only DFO, RFO, and waste coal contribute any meaningful MMBTU of fuel receipts and even they are only 0.9% of MMBTU combined since 2013.
The additional aggregates (like "all fossil fuels" or "nat gas plus other gas") could be useful in error checking or possibly for deducing more precise aggregates for redacted items. But that would probably be an involved process of setting up a big linear algebra system, debugging it, and managing tradeoffs between tractable solvers and noisy data.

A few other notes:

The API offers data for Puerto Rico and Pacific territories, though much of the data lacks price information. The bulk data does not offer anything from these places. The fuel receipts costs table does not cover PR or territories.
The API offers an additional sectoral aggregate: "Electric power non-CHP".
The API and bulk data offer the same temporal resolutions: monthly, quarterly, annual.
When restricting the API to the same categories as the bulk data, the API has around 20% more records, but closer inspection reveals the additional data to be entirely zeros (at least for a spot check of 2015 Q1).

We're well beyond the EIA API at this point, so this validation will not happen. Closing.


add sync service to plugin

What was wrong?
BeaconChainSyncer is not in Beacon plugin
How was it fixed?
Add BeaconChainSyncer to Beacon plugin
To-Do
Cute Animal Picture

@ChihChengLiang what is the status here? is this just blocked on review before we can merge it in?

@ralexstokes Feel free to give this a review. I currently test this with
python eth2/beacon/scripts/run_beacon_nodes.py

Peers generally sync well, but the delayed peer has trouble in proposing a block.

@ChihChengLiang what kind of trouble? until i have synced the head, i'm not going to know if i need to propose or not so it would make sense to hold off on this

@ChihChengLiang running it now -- i like how easy it is to get two nodes up to get one syncing :)
i see each node boot and run for some time -- bob seems to be running while syncing alice and it is throwing a bunch of errors -- we will need to dive into specifics but essentially bob should ignore any requests to participate as a gossiping node while syncing in my opinion
then we get some errors w/ alice and eventually both nodes stop w/ validation errors
some of this has been fixed in the skeleton lake branch so i'm inclined to rebase this once we merge in the other stuff to test it out

Rebased, but the run_beacon_nodes seemed broken. Have to investigate this tomorrow.

i'll take a look later today

This now depends on #1200. Bob syncs, imports blocks, but fails to validate blocks and attestations, and forks after that.


ACR repository authentication - non-interactively

Summary of the new feature / enhancement
It's awesome to see the investment the PowerShell team is making, and I really love seeing ACR being added as private repository capabilities.
However, my instant thought came to rise, is it also possible to connect to ACR repository non-interactively? Such scenario will be extremely useful when automating tasks.
Proposed technical implementation details (optional)
No response

We support the whole Azure Identity sdk which includes non-interactive options, we plan to write a doc about using it in automation in the future, for our CI we use workload identity federation https://learn.microsoft.com/en-us/dotnet/api/overview/azure/identity-readme?view=azure-dotnet#defaultazurecredential

Also storing the Az Access Token in Secret Store before registering can be used for non-interactive scenarios. Please see the documentation at: https://learn.microsoft.com/en-us/powershell/gallery/powershellget/how-to/credential-persistence?view=powershellget-3.x#add-a-credential-to-a-psresourcerepository

Thanks for the quick responses @SydneyhSmith and @adityapatwardhan. I might have been a bit to fast and should have just tried it out or could have asked the question in the community call when you presented it. Anyway, will give it a go. Thanks once again!

@adityapatwardhan It wasn't even needed. I created it through Azure DevOps using the SPN from the Azure PowerShell task. Shared it for others if they want to see it at: https://gijsreijn.medium.com/build-and-publish-your-powershell-modules-to-azure-container-registry-using-azure-devops-c5aac13b001d

Hi @SydneyhSmith @adityapatwardhan,
I see that the Az.accounts module is mandatory. Can we imagine providing an ACR access token directly instead of using this dependency? At the end of the day, you only use the Az.Accounts module to generate an ACR access token and use it when you try to access your ACR.
Allowing a direct access token parameter that you will forward on your side will help people that don't want or simply can't use the Az.accounts module.
Cheers

@SCOMnewbie we are using Azure Identity directly so you are not tied to Az Accounts you can use any method in this article https://learn.microsoft.com/en-us/dotnet/api/overview/azure/identity-readme?view=azure-dotnet does that help?
Where are you seeing that Az.Accounts is mandatory?


Assertion `read->read_type != SRT_2D' failed. nanopolish_train_poremodel_from_basecalls

i got an error with nanopolish  train-poremodel-from-basecalls --verbose pass.fofn &>log.base
Loading ./pass/DESKTOP_TEOOQR9_20160726_FNFAD22371_MN17911_sequencing_run_07_26_16_Edan_DNA_18470_ch429_read2252_strand.fast5
Loaded 40 reads
nanopolish: src/nanopolish_train_poremodel_from_basecalls.cpp:259: int train_poremodel_from_basecalls_main(int, char**): Assertion `read->read_type != SRT_2D' failed.

Hi @gkutish,
The submodule train-poremodel-from-basecalls is not really part of the core functionality and only for internal development. If you let me know what you're trying to do I might be able to suggest an alternative workflow.
Jared

Jared,my data is high a/t and i wanted to try a model different thanthe template_median68pA.model included with your nanopolishprogram. thanksgerald kutish
---------- Original Message ----------
From: Jared Simpson<EMAIL_ADDRESS>To: jts/nanopolish<EMAIL_ADDRESS>Cc: gkutish<EMAIL_ADDRESS> Mention<EMAIL_ADDRESS>Subject: Re: [jts/nanopolish] Assertion `read->read_type != SRT_2D' failed. nanopolish_train_poremodel_from_basecalls (#69)
Date: Wed, 31 Aug 2016 06:29:24 -0700
Hi @gkutish,
The submodule train-poremodel-from-basecalls is not really part of the core functionality and only for internal development. If you let me know what you're trying to do I might be able to suggest an alternative workflow.
Jared
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Beauty Experts (Sponsored by Content.Ad)
Brilliant New Device To Whiten Teeth In Minutes
http://thirdpartyoffers.netzero.net/TGL3241/57c7214f67a5214f0afast04vuc

Interesting. I would guess that it is best to use the built-in model. If you would like to explore training a new model, you should provide 1D reads to this program, not 2D.


Flutter Client

The readme with the comparison is really great btw.
I am working through how to get flutter talking to the graphql.
With Flutter you can do alot of codegen and so i am thinking though how best codegen the Dart code from the graphql schema.
This looks like a really good library to base it on:
https://github.com/davidmarne/flutter_built_redux
i like his because it also allow to use the same code and code gen for Dat web also. Not many libs have this
Anyway, i am raising this here because there might be others working on this.

This feels a bit out of scope for gqlgen.
if there is something needed to support it like extra introspection endpoints etc I would be happy to add something here. But I think most of this needs to happen client side.
https://github.com/apollographql/apollo-client/issues/2756 Apollo has an open issue maybe it's worth collaborating there?

its is out of scope. I dont think it shoudl be in your repo at all.
Its more of a call out to anyone that wants to do it :)
Its a very good match.
The apollo Issue. I already did my minion +1. They have no responded to the
many +1's and so i figured its better to do it yourself.
On Sun, 29 Apr 2018 at 13:26 Adam Scarr<EMAIL_ADDRESS>wrote:

This feels a bit out of scope for gqlgen.
if there is something needed to support it like extra introspection
endpoints etc I would be happy to add something here. But I think most of
this needs to happen client side.
apollographql/apollo-client#2756
https://github.com/apollographql/apollo-client/issues/2756 Apollo has
an open issue maybe it's worth collaborating there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vektah/gqlgen/issues/99#issuecomment-385244224, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATuCwhHqz8qkT69GA5kNG-fhxZVYdfMnks5ttaN7gaJpZM4TrvRC
.


Easily create build scoped detached resolver instances

Make it easier to create build scoped, completely detached, dependency management instances to be solely used for resolution. In cases were build scoped resolvers are already used and where we already passed in build scoped file resolvers and file collection factories, we can move to new convenience methods that automatically use the build scoped file resolvers.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

@bot-gradle test and merge

The merge queue build has failed. Click here to see all failures.


Debian Sid is not supported

Once deb-get installed after by-passing #350, here is what happens:
# deb-get help
  [!] ERROR! Debian Sid is not supported because it is not derived from a supported Debian or Ubuntu release.

Please use the provided template for reporting bugs.


[Enhancement][Metadata Utilities] Option to split up comma separated values in Metadata Editor

Maybe even support prefixes: When one of the predefined prefixes (see #90) was detected, ask the user if all split up items shall start with that prefix. That would be helpful for Wikipedia tags, since those sometimes are split up in a way the addon can't detect.
Maybe it should also be possible to split by other separators like "&", "and" etc. as well.

 Option to split up comma separated values in Metadata Editor


Edit instrument request: ncas-rapidsonde-1

Instrument
ncas-rapidsonde-1
Attribute
Host Institution
New value
Manchester
Reason
Typo

Spreadsheet updated with correct spelling


[firebase_crashlytics] Fix typo in README

Sorry for missing this PR. It was fixed in another that I saw first: https://github.com/flutter/plugins/pull/1407. Closing


Allow changing the maximum renderable elements in the scene.

Fixes #30597
The problem:
Setting a value in the project settings for: rendering/limits/rendering/max_renderable_elements does not lift the maximum number of elements that can be drawn. For example when loading 50,000 objects to the scene the total number of objects is loaded fine, but only a fixed number is drawn (see screenshot below). This prevents rendering/showing large numbers of e.g. people in a city or a building. Altering the max_renderable_elements value to 1,000,000 makes no difference.

There is a hard-coded value MAX_INSTANCE_CULL in visual_server_scene.h file that cannot be edited through the editor or through code at runtime. It is used to allocate a fixed size array for storing drawable elements. It is related to the DEFAULT_MAX_ELEMENTS value that was exposed in a previous pull request: #1339. For large scenes it is necessary to increase both values.
The solution:
This commit exposes (and renames) the MAX_INSTANCE_CULL, DEFAULT_MAX_LIGHTS_CULLED and DEFAULT_MAX_REFLECTION_PROBES_CULLED to match the previously exposed and related values DEFAULT_MAX_ELEMENTS, DEFAULT_MAX_LIGHTS and DEFAULT_MAX_REFLECTIONS.
These are the enum values in visual_server_scene.h:

MAX_INSTANCE_CULL = 65536
MAX_LIGHTS_CULLED = 4096
MAX_REFLECTION_PROBES_CULLED = 4096
MAX_ROOM_CULL = 32
MAX_EXTERIOR_PORTALS = 128

The last two are never used (now removed) and the first three could not be previously edited through the editor or through code.
Note: the tooltip texts for the ProjectSettings.xml may need rewording. The tooltips from the related values were re-used with an extra explanation.
TL;DR:
Allow changing some hard-coded limits (values) through the editor. No default values have been changed. No difference to anyone who can already work within the hard limits. However, anyone who needs to render large numbers of objects needs this patch (we are using this in-house).

From my understanding the octree implementation is limited to 2^16 (65536) unique objects which is where the limit came from. The rendering/limits/rendering/max_renderable_elements is actually there to allow users to reduce the maximum number of elements in the scene. This can lead to a substantially faster load times on Web and Mobile platforms.
As it stands now, I'm not sure your changes will actually work without breaking culling. That being said, I agree with the intention behind the changes. We shouldn't arbitrarily be limited users to 65536 objects. However, I think a proper implementation is going to require more than resizing the current arrays.
Further, this is a large change that can't be considered for 3.2.x. It needs to wait until 4.0 (which is why I haven't reviewed it until now). I will leave this open until Vulkan is merged into master (should be soon now) and then we can figure out how to make these changes properly with the Vulkan renderer.

Superseded by https://github.com/godotengine/godot/pull/44435 (see the above comment).

Superseded by #44435 (see the above comment). Thanks for the contribution nonetheless!

I believe that is incorrectly marked. #44435 only replaces a hard-coded value with a different hard-coded value, which is exactly the problem this PR is aiming to remove (i.e. hard-coding the value is the problem this PR is fixing).

I believe that is incorrectly marked. #44435 only replaces a hard-coded value with a different hard-coded value, which is exactly the problem this PR is aiming to remove (i.e. hard-coding the value is the problem this PR is fixing).

Increasing the values above the defaults most likely won't work as pointed out by https://github.com/godotengine/godot/pull/35447#issuecomment-583500572.

I made a minimal reproduction project: test_huge_amt_elements.zip
Here's how it renders on Godot 3.2.4 + GLES3 + GeForce GTX 1080: https://www.youtube.com/watch?v=qcbCFRAR5Nc (watch in the highest resolution possible to improve compression quality)
Directional shadows were made red so that you can spot which parts of the octree are effectively shaded more easily.

I made a minimal reproduction project with 100,000 meshes: test_huge_amt_elements.zip
Here's how it renders on Godot 3.2.4 + GLES3 + GeForce GTX 1080: https://www.youtube.com/watch?v=qcbCFRAR5Nc
(watch in the highest resolution possible to improve compression quality)
Right now, meshes are culled when you have 65,536 of them, which is expected. We need to test this with an updated version of your pull request (against the current 3.2 branch) to see whether increasing the value works here.
Directional shadows were made red so that you can spot which parts of the octree are effectively shaded more easily.
You can change the number of meshes created in test.gd.

Thank you so much for the effort of putting together a test case! It definitely demonstrates the problem in 3.x.
I went digging for the code to create a new PR. I'm happy to say that this problem no longer exists in 4.0 (more specifically I tested this in commit 380bb2d...).
More info:
The MAX_INSTANCE_CULL constant still exists in ./servers/rendering/rendering_server_default.h, but it is not being used anywhere in the code. It is not exposed to the editor either. However, there is a new variable (introduced in this commit) called max_renderable_elements  :
https://github.com/godotengine/godot/blob/380bb2d5330ac5c79d701c46d5462f4e0da56403/servers/rendering/renderer_rd/renderer_scene_render_forward.cpp#L3364
The new variable is not hard-coded, and it is exposed to the editor and it works. It defaults to 128,000, which is about double the previous maximum of 65,536 (in 3.x). The test case has to be increased to above the default limit as 100,000 meshes render just fine in 4.0. Increasing the quantity to 150,000 meshes with the default limit manifests the same problem as in 3.x. However, when increasing the limit through the editor to e.g. 200,000, then all 150,000 cubes are rendered, including shadows. It seems that the problem this PR was attempting to solve has already been solved for 4.0. Therefore, I don't see the need to create a new PR for the current version as the next major version of Godot no longer has this problem.
For anyone who reads this: the max_renderable_elements setting can be found in Project -> Project Settings... -> General -> Rendering -> Limits -> Rendering -> Max Renderable Elements.
Here is the same test case but with 150,000 meshes for Godot 4.0:
test_huge_amt_elements_4-0.zip

I made a minimal reproduction project with 100,000 meshes: test_huge_amt_elements.zip
Here's how it renders on Godot 3.2.4 + GLES3 + GeForce GTX 1080: https://www.youtube.com/watch?v=qcbCFRAR5Nc
(watch in the highest resolution possible to improve compression quality)
Right now, meshes are culled when you have 65,536 of them, which is expected. We need to test this with an updated version of your pull request (against the current 3.2 branch) to see whether increasing the value works here.
Directional shadows were made red so that you can spot which parts of the octree are effectively shaded more easily.
You can change the number of meshes created in test.gd.

Thank you so much for the effort of putting together a test case! It definitely demonstrates the problem in 3.x.
I went digging for the code to create a new PR. I'm happy to say that this problem no longer exists in 4.0 (more specifically I tested this in commit 380bb2d...).
More info:
The MAX_INSTANCE_CULL constant still exists in ./servers/rendering/rendering_server_default.h, but it is not being used anywhere in the code. It is not exposed to the editor either. However, there is a new variable (introduced in this commit) called max_renderable_elements  :
https://github.com/godotengine/godot/blob/380bb2d5330ac5c79d701c46d5462f4e0da56403/servers/rendering/renderer_rd/renderer_scene_render_forward.cpp#L3364
The new variable is not hard-coded, and it is exposed to the editor and it works. It defaults to 128,000, which is about double the previous maximum of 65,536 (in 3.x). The test case has to be increased to above the default limit as 100,000 meshes render just fine in 4.0. Increasing the quantity to 150,000 meshes with the default limit manifests the same problem as in 3.x. However, when increasing the limit through the editor to e.g. 200,000, then all 150,000 cubes are rendered, including shadows. It seems that the problem this PR was attempting to solve has already been solved for 4.0. Therefore, I don't see the need to create a new PR for the current version as the next major version of Godot no longer has this problem.
For anyone who reads this: the max_renderable_elements setting can be found in Project -> Project Settings... -> General -> Rendering -> Limits -> Rendering -> Max Renderable Elements.
Here is the same test case but with 150,000 meshes for Godot 4.0:
test_huge_amt_elements_4-0.zip


clientv3: fix typo in README

Fix https://github.com/coreos/etcd/issues/7337.
Replace https://github.com/coreos/etcd/pull/7343.

lgtm


chore(package): update npm-check-updates to version 2.10.5

Closes #32
https://greenkeeper.io/

Codecov Report

Merging #43 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #43   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           7      7
  Lines          92     92
  Branches        7      7
=====================================
  Hits           92     92

Continue to review full report at Codecov.

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


Use gateway instead of direct phabricator url

Make sure that all API calls to Phabricator are made through the gateway.

@sectioneight @Ignas

Coverage remained the same at 91.273% when pulling bced5f50ee20c59d7ebd47245b7e4f86348bad35 on jx_gateway into c97159e0002d00890116ac0155c09f0972a7a466 on master.


[WIP] Allow synchronous processing

Since there's no asynchronous dependencies (yet!), there's the potential to call clusterize() synchronously. This PR makes the necessary (small) changes to allow that as an option.
Added some tests around this, in particular the unnecessary callback parameter.

Oops - this wasn't quite meant to be created in this repo just yet! Have edited the title to denote a work in progress for now. Apologies! Can also close it off if that would be cleaner.

Thanks for the contribution. Let me have a look tonight :)

Hi Colin,
Do you think you can solve by using await / async pattern?
`
main();
async function main() {
await doKMeans();
// do sth else here...
}
async function doKMeans() {
return new Promise((resolve) => {
kmeans.clusterize(engineers, { k: 4, maxIterations: 5, debug: true }, (err, res) => {
resolve();
};
};
}
}
`

Definitely an option, @stanleyfok! Happy to close this off for now.


add clickhouse backup guide

I've just moved my Plausible instance to a different region and went through backing up and restoring plausible_db and plausible_events_db. I thought I'd quickly put that experience into writing.
Still WIP, missing some crucial steps (like users and permissions and backing up all imported_* tables)

I'm using a modified version of docker-compose.yml as follows:
version: "3.3"
services:
  # mail:
  #   image: bytemark/smtp
  #   restart: always

  plausible_db:
    image: postgres:14-alpine
    restart: always
    volumes:
      - ./db-data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=postgres

  plausible_events_db:
    image: clickhouse/clickhouse-server:23.4.3
    restart: always
    volumes:
      - ./event-data:/var/lib/clickhouse
    ulimits:
      nofile:
        soft: 262144
        hard: 262144
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:8123/?query=SELECT%201 || exit 1
  plausible:
    image: plausible/analytics:v1.5
    restart: always
    command: sh -c "/entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
    depends_on:
      - plausible_db
      - plausible_events_db
      # - mail
    ports:
      - 8333:8000
    environment:
      - BASE_URL=https://someurl.knat.network
      - DISABLE_REGISTRATION=true

Directory structure:
total 12K
drwx------ 19              70 root            4.0K Sep  2 01:22 db-data
-rw-r--r--  1 root            root            1.3K Aug 26 04:03 docker-compose.yml
drwxr-xr-x 15 systemd-network systemd-journal 4.0K Sep  2 01:22 event-data

smtp is commented out as the image has no ARM64 version.

In this setup:

There is no need to sleep 10 seconds on plausible container(because depends_on can make sure DB is started first)
There is no volumes to manage as all data lies in event-data and db-data with the same directory, so all the migration step is just docker-compose down and rsync the whole directory to another host and docker-compose up -d, no need to hassle with DB 😉


feat: add typst blue header CV

Repo URL: https://github.com/cammellos/typst-blue-header-cv
Hello, thanks for the project!
In case you'd like to add the link to my repo, feel free to merge!
Thanks!

Thanks for the awesome contribution @cammellos !


Commented out unused top-nav elements

🔗 Issue
 Remove unused top-nav elements that we aren't using yet #194
✍ Description
Commented out the following unused top-nav elements for later use:

Search
The "Dark Mode" icon
Notification bell

📷 Screenshots/Demos

No problem @edwinthinks, I have it removed now


Please update NPM module.

Can you please upgrade the NPM module to resolve the
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.

deprecation warning? This was fixed in this pull request https://github.com/sstur/draft-js-export-html/pull/71 which was merged into master

I need this too! just "npm publish" please

Done.
Sorry about the delay on that.


feat(e2e): add tests for check category filters

Added e2e tests to check filters on category page and search results page

Type of change

[ ] 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 not work as expected)

Screenshots (if applicable)

Additional context

I see some errors in e2e but the test is not failing.
Look at this screen:

any further work here applying Bjorn's suggestions?

I added a new Test where we select some random filter option from the manufacturer and later check if the filter is present in the URL. See this commit.
What do you think @kstala?


Open/Edit with...

You can't open files without filename extensions.

on which platform (macOS/Windows/Linux)?

Windows

Yep, this is because Windows doesn't know how to open the file (probably there pops up a native error message).
This will be fixed if there's the option to always open files in a specific app. Unfortunately Windows makes this function pretty hard to implement and auto-updating the remote file is not available for Windows either.


1.2.7 Set up Recovery Phrase/Walkthrough 2

1. User Story
Info about what the recovery phrase is and why it is important.
2. Acceptance Criteria

Progress circle animation.

3. Related Issues

[ ] Create all related issue for this issue, label them, assign them, and move them to the right projects.

4. Wire Frame
None
5. Design

https://www.figma.com/file/ERJ7bYyBWdqJw1ID9nZJ2N/Designs?node-id=7904%3A10788

button component / progress animation


Move hardcoded into env variables

We have the graphql url and queries hardcoded, move them into env variables so they can be updated at build time.

no instructions provided how to set these env variables, what are their names? what's the build command? example?


Link sites to unique moTi ID and add to reporting

perhaps we just make a new csv that has a xref_pscis_moti .  Not sure if we even will be able to automate the joining of the culvert_id to the chris_culvert_id as our skeena mergin project may have been made from bcbarriers and therefor likely updated. Will confirm and document here.

tiny join work to get the chris_culvert_id is now complete and was done here in this line https://github.com/NewGraphEnvironment/fish_passage_skeena_2022_reporting/blob/216ebbd3234506b2d1cef2a277ba1c3b09affb9e/scripts/pscis_tidy.R#L121
resulting csv is here


[BUG] repeated runs mvn package without clean lead to missing spark-rapids spark-rapids-jni-version-info.properties in dist jar

Describe the bug
If the user invokes repeatedly mvn package on dist without clean, the dist jar ends up with a missing spark-rapids-jni-version-info.properties and the Plugin refuses to initialize.
Steps/Code to reproduce bug
Clean just once:
mvn clean

Run package for dist module using
mvn package -pl dist -am -Dbuildver=321 -DskipTests

Check the resulting jar has the build info for spark-rapids-jni
jar tvf dist/target/rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar  | grep spark-rapids-jni-version-info.properties
   170 Tue Jun 07 14:28:34 PDT 2022 spark-rapids-jni-version-info.properties

Re-run package for dist module using the same command:
mvn package -pl dist -am -Dbuildver=321 -DskipTests

Recheck the build info for spark-rapids-jni, and observe it's missing
jar tvf dist/target/rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar  | grep spark-rapids-jni-version-info.properties
echo $?
1

Expected behavior
mvn package with the same parameters should be reproducible and result in equivalent artifacts without a clean
As a workaround use mvn clean package/install ...
Environment details (please complete the following information)
Any
Additional context
Maybe related to #5603
h/t @NVnavkumar @anthony-chang

Yes, it's related to https://github.com/NVIDIA/spark-rapids/pull/5603

ls -lh rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar
// first time
377M  6  8 10:41 rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar

// second time
7.2M  6  8 10:44 rapids-4-spark_2.12-22.08.0-SNAPSHOT-cuda11.jar


ENYO-1957 Drawer: Handle is unable to display overlapping Images and …

…Icons
Enyo-DCO-1.1-Signed-off-by: Art Dahm<EMAIL_ADDRESS>

Superceded by #138


tuple returned by useMutation

Hi again,
I could be wrong, but I think you meant to document reset instead of promise (I did a quick check and found that no promise is being returned)

Mutate returns a promise. useMutation returns a tuple, and it’s documented as such.


Fixes for Mapnik 7ee9745

Updating to Mapnik 7ee9745 caused a couple of compile failures. Luckily, they were pretty easy to fix.

There's a value_bool element in the mapnik::value variant, which needs handling in the visitors.
The pixel types, such as rgba8_t, moved into the mapnik namespace.

cc @charterchap, @pnorman

:rocket:

:ship:

Thanks!


'slot' does not change normally in transition   in 2.7.14

Version
2.7.14
Reproduction link
codesandbox.io
Steps to reproduce
auto
What is expected?
I hope it's all green
What is actually happening?
One red and one green

so there a very simple solution to this you just need to put green instead of red in app.vue file .

HERE THE FIX :https://codesandbox.io/s/friendly-pond-fr3jfr?file=/src/App.vue

so there a very simple solution to this you just need to put green instead of red in app.vue file .

That's a great idea, and only you could have thought of it

OH!! that's very kind of you .Thank you.


Cannot predict with numpy inputs

Hi,
I trained AutoML model for regression task. But when I use model.predict(), it returns TypeError. So how can I fix this problem?
Best,
Li

Traceback (most recent call last):
File "", line 1, in
File "/home/lilu/anaconda3/envs/am/lib/python3.10/site-packages/flaml/automl/automl.py", line 573, in predict
X = self._state.task.preprocess(X, self._transformer)
File "/home/lilu/anaconda3/envs/am/lib/python3.10/site-packages/flaml/automl/task/generic_task.py", line 637, in preprocess
X = transformer.transform(X)
File "/home/lilu/anaconda3/envs/am/lib/python3.10/site-packages/flaml/automl/data.py", line 394, in transform
elif isinstance(X, DataFrame):
TypeError: isinstance() arg 2 must be a type, a tuple of types, or a union

try:
import pandas as pd
from pandas import DataFrame, Series
except ImportError:
DataFrame = Series = pd = None

Could you check if you have installed pandas?
That may be the cause of the error...


add support for testsuite parameter (#142)

make it possible to spedify a testsuite within phpunit.xml with  attributes and execute the specified 's in parallel

Nice, thanks for this.
I'm just wondering about files but not directories. Your patch supports suites with files but doesn't support directories, does it? (https://phpunit.de/manual/current/en/organizing-tests.html#organizing-tests.xml-configuration)
Actually, I haven't seen a testsuite with files in practice. Is it much harder to add directory support? If not, it would be nice if you could add it.

No problem, I need this for a project with many legacy tests with messed up test structure ;)
I added directory support and (apparently) support for mixed file/directory suites.
I wasn't sure if I should make it complicated with another option to filter duplicates (when mixing files and directories) so I forced, that no duplicate tests are allowed when using --testsuite parameter

I wasn't sure if I should make it complicated with another option to filter duplicates (when mixing files and directories) so I forced, that no duplicate tests are allowed when using --testsuite parameter.

Sounds good. Getting an error is better than having duplicates because of a senseless config and not noticing it.

It's important to mention, that the 's are not executed in order as mentioned in the phpunit docs. For paratests it is only to add specific files to a testsuite that will be also executed.

The order is always mixed up when parallelizing the tests, so +1 for that.
Thanks again and this in going to be version 0.10.0


Fix GVM Method Pointer Lookup Failure

Failure to find a method pointer for a resolved GVM target should fail fast and not attempt to resolve the GVM on a base type (this could lead to calling the incorrect method just because we can't find an entrypoint for the correct one).

@davidwrighton PTAL


Fairer distribution of Cardano fee to delegates in auction fees distribution transaction

Currently, in the fee escrow validator, we require for the fee that has been generated by an auction, to be evenly distributed over the list of delegates in a single tx.
This leads to an asymmetry, as one delegate will have to pay the tx fee for all the delegates to collect their ADA.
We could improve this by taking into account the tx fee, and ensuring that the delegate that is submitting the tx to spend the fee escrow utxo can take out a bit more of the reward, to cover this fee.

Cool solution, did not think about that. Seems simple to implement.
While that will probably break in corner case of auctionFeePerDelegate == minimal ADA.


[W5][W17-2]Kyler Wong Shen Meng

Ready for Review

Nice AddMultiple()!.
Might I suggest that addx be changed to to addm for the command word at line 8 of AddMultipleCommand.java?
Also, perhaps a message could be printed to prompt the user for each add.


Update 05-File-Management Doc

When first using the File Management you will get a 500 error when there is no File type to be found, based off several forum posts and my own personal experience I think this addition will make things clearer for users. I'm personally using version 0.x, if this change is applicable to 1.0 I'd be happy to add it there also.

Hey @joefazz, we're currently cleaning up our PRs. Apologies for not having looked at it in detail earlier, unfortunately it is outdated by now so I'll close it. Please keep opening PRs in the future if you see any issues with our docs 🙏


429 Error

Describe the bug
Hi, I tried to follow the steps described in the readme to run the example app, but I get a 429 error as shown below.  The API key I generated and put into the .env file doesn't have any usage, so I thought the request should go through.  Is it just that the OpenAI API is at capacity, or is there anything further I should try to do to resolve the issue?  Thanks for the help!
Error message below:
[~/code/app/openai-quickstart-node]$ npm run dev

><EMAIL_ADDRESS>dev
> next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /Users/henry/Documents/code/app/openai-quickstart-node/.env
wait  - compiling...
event - compiled client and server successfully in 2.3s (113 modules)
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
wait  - compiling / (client and server)...
wait  - compiling...
event - compiled client and server successfully in 2.4s (132 modules)
wait  - compiling /api/generate...
wait  - compiling...
event - compiled client and server successfully in 536 ms (142 modules)
wait  - compiling /_error (client and server)...
wait  - compiling...
error - Error: Request failed with status code 429
event - compiled client and server successfully in 101 ms (143 modules)
error - Error: Request failed with status code 429
error - Error: Request failed with status code 429

To Reproduce
Follow the 7 steps shown in the readme below, and tried to generate names on http://localhost:3000/
https://github.com/openai/openai-quickstart-node
OS
macOS
Node version
Node.js v18.13.0

Just a brief update that I signed up for a paid account to try to resolve this issue.  It didn't seem to fix it at first yesterday, but when I re-tried this morning, it appears to be working now.  Not sure if this was a temporary issue, but if no one else is experiencing this issue anymore, I'll close this issue.  Thanks!


chore!: Update kube to v0.96

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
see 2 files with indirect coverage changes


bug: pictures are not saved to same directory as RTF file

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure it has not already been reported
[X] I agree to follow the Code of Conduct that this project adheres to

API/app/plugin version
5.0.3
Node.js version
20.15
Operating system
macOS
Operating system version (i.e. 20.04, 11.3, 10)
12.5
Description
Many thanks for this v helpful package! As someone working in healthtech, this is a big help for reasons I'm sure you're familiar with given your work at NHS (:
I noticed that for the noPictures setting, the expected behaviour is that the embedded pictures get stored in the directory of the original file.
@property {boolean} [noPictures] Disable the automatic storing of embedded
 * pictures to the directory of the original file.

However, when I tested the package locally, it seems that the pictures get stored from the directory I run the RTF conversion from, rather than where the input file is stored.
Steps to Reproduce
Create a file temp.ts with the below code and some RTF sample in subdirectory ./data/.
import { UnRTF } from 'node-unrtf'

const f = async () => {
  const unRtf = new UnRTF()
  const html = await unRtf.convert(__dirname + `/data/rtf-sample.rtf`, {
    outputHtml: true,
    noPictures: false,
  })
  return html
}

console.log(f())

Run file with ts-node temp.ts.
Expected Behaviour
pict001.jpg outputs to the local directory ., when it's expected to output to ./data.

Based on the unrtf docs

--nopict
disables the automatic storing of embedded pictures to the current directory.

it looks like storing in the current directory is the expected behaviour, so this doesn't seem fixable.

Hi @calebchiam, thanks for the report!
Good catch, looks like I documented that option incorrectly.
I will update it in the inline jsdoc tags, and review the rest of them whilst i'm at it, to ensure they are correct.
I'll also add an example to the readme for handling the images dumped into the current working directory.


How to change the folder of the output file

/ folder(root) of the master branch is the default folder of the output wiki file, please let me know how to change it to some other folder /somefolder/

i found the answer, Thanks!


Content freshness refresh of ms.date

Content freshness refresh of ms.date

#sign-off Reset of ms.date for content freshness

@KarlErickson
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Fix pxc-release so it's not dependent on monit

We want to use pxc-release but it currently uses monit, and we don't have monit anymore in Kube-land.
https://github.com/cloudfoundry-incubator/galera-healthcheck/tree/5f062bf290ca6f6853fe06205bda99bf615dc332/monit_client
Tasks

[ ] open an issue upstream
[ ] talk to the upstream team (slack #mysql-galera)
[ ] open a PR

Using pxc-release with kubecf proved impractical. Not only it is dependent on monit, but other issues were noticed:

The mysql daemon is started in the pre-start script, calling bpm: https://github.com/cloudfoundry-incubator/pxc-release/blob/f55c4982979fc4c5d5707a872072c0d5fa7e4728/jobs/pxc-mysql/templates/pre-start.sh.erb#L138-L156.
The cluster-health-logger pre-start tries to talk to mysql, assuming it was started on the pre-start script mentioned above: https://github.com/cloudfoundry-incubator/pxc-release/blob/f55c4982979fc4c5d5707a872072c0d5fa7e4728/jobs/cluster-health-logger/templates/setup.erb. The setup that this pre-start performs would need to be executed on the main container, therefore replacing https://github.com/cloudfoundry-incubator/pxc-release/blob/f55c4982979fc4c5d5707a872072c0d5fa7e4728/jobs/cluster-health-logger/templates/bpm.yml.erb#L4.

Other issues may exist that we cannot foresee yet.

@f0rmiga interesting. How is our way forward with regards to database then?
@c0d1ngm0nk3y noticed that the mysql galera database cannot be scaled, apparently on purpose.
So for production we would strongly recommend the use of an external database?
cc @viovanov @troytop

@loewenstein For the pre-release of kubecf we will keep cf-mysql-release in SA mode and promote the use of an external database: https://github.com/SUSE/kubecf/pull/162. When I added the database instance group, I purposedly made it SA to simplify the setup at the time and allow us to move forward with other instance groups. Given that cf-mysql-release is scheduled for deprecation, I don't believe the effort to write and maintain the BPM manifest for all jobs is justifiable. Please, let me know what you think.

@f0rmiga sounds fine, just wanted to make sure it's a conscious decision. Care to comment in #155  and close it?


Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.

After upgrading gradle version to 7.3.3 I got following error while building:
[  +24 ms] Unzipping /Users/runner/.gradle/wrapper/dists/gradle-7.3.3-bin/6a41zxkdtcxs8rphpq6y0069z/gradle-7.3.3-bin.zip to /Users/runner/.gradle/wrapper/dists/gradle-7.3.3-bin/6a41zxkdtcxs8rphpq6y0069z
[+2012 ms] Set executable permissions for: /Users/runner/.gradle/wrapper/dists/gradle-7.3.3-bin/6a41zxkdtcxs8rphpq6y0069z/gradle-7.3.3/bin/gradle
[ +882 ms] Starting a Gradle Daemon (subsequent builds will be faster)
[+60816 ms] FAILURE: Build failed with an exception.
[        ] * Where:
[        ] Build file '/Users/runner/work/1/s/src/android/app/build.gradle' line: 24
[        ] * What went wrong:
[        ] A problem occurred evaluating project ':app'.
[        ] > Failed to apply plugin 'com.android.internal.application'.
[        ]    > Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.
[        ]      You can try some of the following options:
[        ]        - changing the IDE settings.
[        ]        - changing the JAVA_HOME environment variable.
[        ]        - changing `org.gradle.java.home` in `gradle.properties`.
[        ] * Try:
[        ] > Run with --stacktrace option to get the stack trace.
[        ] > Run with --info or --debug option to get more log output.
[        ] > Run with --scan to get full insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 1m 8s

Should I perhaps install java before building flutter?

Yes it's building locally. I've already done all things provided in StackOverflow link.
Change which started build errors:

I suspect it's because of minimum JDK version required for gradle-plugin (JDK 11): https://developer.android.com/studio/releases/gradle-plugin.html#compatibility

Hi, this issue has nothing to do with the extension. If you read the code of the "Tasks", you will see that it just downloads "Flutter SDK" and run bash commands on it.
Issue is related to Azure Agent Pool running your build. Azure-DevOps agents has pre-installed stuff on it which could/n't be latest. You have to check in your pool details, which version Microsoft is using.
 On this page you will see a lengthy list of all the stuff installed on it. Check, Java and Grade version in that.
Here is what the details page looks like

Also, note that the image is of a "hosted agent". If you are running agents locally, you have to figure this out yourself. If your hosted agent shows old versions, that means, Microsoft hasen't updated it yet. You can open a new issue on Microsoft's DevOps Github or you can try this

So it came down to installing java before building flutter. I've done steps provided in your link and now It works. Thanks a lot for your help. Awesome work with this plugin :)

So it came down to installing java before building flutter. I've done steps provided in your link and now It works. Thanks a lot for your help. Awesome work with this plugin :)

That is because you are using too "latest" of the tech. Microsoft, doesn't upgrade agent pools to latest stuff because it can impact other users who have "Production" envs running. As you know, many people don't upgrade production environments to latest unless after big meetings and fully testing the systems.
I am glad it is working for you now.

Had the same issue, will share my solution if anyone needed it,
The issue happened because as @hey24sheep said, the Java version installed were below 11, if you're using macOS-latest, the default version is 8, so i had to change it to ubuntu-latest that had the Java version defaults to 11


TypeError: Cannot read property 'length' of undefined when running AOT

I'm submitting a ...
[X ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

What is the current behavior?
when I run npm run build:aot I get this error.

Starting compilation using the angular compiler.
Angular compilation done, starting webpack bundling.
TypeError: Cannot read property 'length' of undefined
at StaticSymbolResolver.resolveSymbol (D:\project\node_modules@angular\compiler\bundles\compiler.umd.js:25950:35)

What is the expected behavior?
no error

Please tell us about your environment:

Angular version: 2.4.2
npm 3.10.8
Browser: [Chrome ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

What is the TS version?
Did it work with 2.4.1?
Sent from my iPhone

On Jan 10, 2017, at 11:17 PM, Todd<EMAIL_ADDRESS>wrote:
I'm submitting a ...
[X ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
What is the current behavior?
when I run npm run build:aot I get this error.
Starting compilation using the angular compiler.
Angular compilation done, starting webpack bundling.
TypeError: Cannot read property 'length' of undefined
at StaticSymbolResolver.resolveSymbol (D:\project\node_modules@angular\compiler\bundles\compiler.umd.js:25950:35)
What is the expected behavior?
no error
Please tell us about your environment:
Angular version: 2.4.2
npm 3.10.8
Browser: [Chrome ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is an issue in your repository, there is no AOT compilation issue with either Angular 2.4.1 or 2.4.2.

@GenZodd Did you had any success with the build?

yes, thanks for asking. I had to back a couple other packages out and then I got this working. I had a toastr and a loggly npm package that I had to remove and then it worked. Then I update those other packages and it is still working.


fix: rm skip(1) in input-filter

skip(1) in input-filter cause the following issues:

Cannot support searching for items length equal to 1 (such as id, etc)
Cannot support languages like Chinese, Japanese, etc, which need an IME for input, FormControl can only get 'valueChanges' event one time for the whole sentance output by IME

fixed in a separate PR.


Improve contribution guidelines

[x] Improve contribution guidelines (CONTRIBUTING.md), including step-by-step instructions on how to make changes, validate them and open a PR.
[x] Add a link to the CODE-OF-CONDUCT.md document.
[X] Remove the CONTRIBUTING-pt-br.md version.

Done 7a288a4e672d679623619fa36b1a010645ddf1ec