Remove dependency on DotEnv

The dependency on DotEnv assumes that secrets and configuration are always stored as environment variables (and in plain text). While it is a noble way to encourage developers to stay away from storing their secrets in version control, it prevents developers from using their own mechanisms for securing their secrets.
For example, one might prefer to store their secrets encrypted in Redis and decrypt on the fly as needed. Or they might even want to use environment variables, but encrypted so that other applications running as root or the same user can't easily learn their secrets.

Thanks for the update! I didn't even consider that option lol.


Is the pdb data open-sourced?

Hi. Do you open-source the training data (single-chain/ complex protein pdbs)?

Soorry for bothering you guys! The data is released at https://modelscope.cn/datasets/DPTech/Uni-Fold-Data/summary


Realtime-Chat-Application (#1417)

Real-Time-Chat-Application
FrontEnd Technologies - HTML, CSS
BackEnd Technologies - JavaScript, Node.js
Used Socket.io module for a two-way connection between client and server.

Change in code will create new PR


Parsing year problem

I got a problem when I parsed a string with format %Y%m%d. Here is a test case:
use time::Date;

fn main() {
  let date = Date::parse("20200703", "%Y%m%d");
  dbg!(date);
}

This prints:
[src/main.rs:5] date = Err(
    InvalidYear,
)

But, it works fine in the following case:
use time::Date;

fn main() {
  let date = Date::parse("2020 0703", "%Y %m%d");
  dbg!(date);
}

[src/main.rs:5] date = Ok(
    Date {
        year: 2020,
        ordinal: 185,
    },
)

It also looks like it can distinguish the month and the day when they come together, but it cannot do the same thing for the year. So, I guess this might be a bug?

I look into the code of parsing years. It looks like it assumes the string of a year might have at most 6 digits so that it can handle a year greater than 9999. However, I think may be better to assume the string is 4 digits and accept a string that has more than 4 digits only when it begins with a +.
How do you think about this?

I've actually been aware this would likely happen, but never bothered to test it. You're 100% correct that the parser assumes can be up to six digits, as the valid years are ±100,000.
Given that the formatter inserts a + (per the ISO spec) when the year is more than four digits, I think parsing it the same way would make sense. It should be a relatively minor change, just adding a conditional to change the max from 6 to 4 if a + is parsed. I can do this at some point, likely after Tuesday (midterms for college).

How about I do it later and submit a pull request?

If you'd like, sure! Just be sure to add a test case.

I just submitted a pull request. Please check if it is good for you.


update flyway version

Hi,
Our conductor setup consists of multiple instances. If we start the instances simultaneously, sometimes we got the following error:
2021-02-01 12:42:08,339 [main] ERROR error migration DB
org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException:
Script failed
-------------
SQL State  : 23505
Error Code : 0
Message    : ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
  Detail: Key (typname, typnamespace)=(schema_version, 2200) already exists.
Line       : 17
Statement  : CREATE TABLE "public"."schema_version" (
    "installed_rank" INT NOT NULL,
    "version" VARCHAR(50),
    "description" VARCHAR(200) NOT NULL,
    "type" VARCHAR(20) NOT NULL,
    "script" VARCHAR(1000) NOT NULL,
    "checksum" INTEGER,
    "installed_by" VARCHAR(100) NOT NULL,
    "installed_on" TIMESTAMP NOT NULL DEFAULT now(),
    "execution_time" INTEGER NOT NULL,
    "success" BOOLEAN NOT NULL
) WITH (
  OIDS=FALSE
)

        at org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117)
        at org.flywaydb.core.internal.metadatatable.MetaDataTableImpl.createIfNotExists(MetaDataTableImpl.java:104)
        at org.flywaydb.core.internal.metadatatable.MetaDataTableImpl.lock(MetaDataTableImpl.java:111)
        at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:175)
        at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:173)
        at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
        at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:173)
        at org.flywaydb.core.Flyway$1.execute(Flyway.java:959)
        at org.flywaydb.core.Flyway$1.execute(Flyway.java:917)
        at org.flywaydb.core.Flyway.execute(Flyway.java:1373)
        at org.flywaydb.core.Flyway.migrate(Flyway.java:917)
        at com.netflix.conductor.postgres.PostgresDataSourceProvider.flywayMigrate(PostgresDataSourceProvider.java:94)
        at com.netflix.conductor.postgres.PostgresDataSourceProvider.get(PostgresDataSourceProvider.java:43)
        at com.netflix.conductor.postgres.PostgresDataSourceProvider.get(PostgresDataSourceProvider.java:28)

This issue is related to flyway (conductor is using flyway:4.0.3, this issue is fixed in 5.1.0):
https://github.com/flyway/flyway/issues/1067
https://github.com/flyway/flyway/issues/1983
In this PR, I updated the flyway version to the latest one which solves this issue.

@mactaggart @rickfish Could you please help with reviewing this PR.

Pull Request Test Coverage Report for Build 5034

9 of 11 (81.82%)  changed or added relevant lines in 2 files are covered.
17 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.08%) to 70.256%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mysql-persistence/src/main/java/com/netflix/conductor/mysql/MySQLDataSourceProvider.java
4
5
80.0%

postgres-persistence/src/main/java/com/netflix/conductor/postgres/PostgresDataSourceProvider.java
5
6
83.33%

Files with Coverage Reduction
New Missed Lines
%

postgres-persistence/src/main/java/com/netflix/conductor/postgres/PostgresDataSourceProvider.java
1
78.26%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraEventHandlerDAO.java
8
68.42%

cassandra-persistence/src/main/java/com/netflix/conductor/dao/cassandra/CassandraMetadataDAO.java
8
55.44%

Totals

Change from base Build 5027:
-0.08%

Covered Lines:
13067

Relevant Lines:
18599

💛  - Coveralls

I am a couple of dev versions behind so maybe it is because of that but I made the same changes in the Postgres module and I get this error at startup (we have a schema named conductor-unita in our 'unit' database):
[ERROR] 2021-02-02 14:24:31,388 PostgresDataSourceProvider - error migration DB
org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "conductor_unita" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
at org.flywaydb.core.Flyway$1.execute(Flyway.java:196)

Hi @rickfish
Thanks for the review.
Flyway changed the default schema history table name from schema_version to flyway_schema_history https://github.com/flyway/flyway/issues/1848.
So, it's not recognized your history table and you got an error.
I updated the configurations to use schema_version as default.
can you pls try to run it again with the new commit?

Hi @rickfish ,
Any update? Did you get a chance to look into it?

Hi @apanicker-nflx / @aravindanr,
Could you pls review and merge this PR?
This issue blocking us, and force us to work with a forked repo.
We have a requirement to destroy and deploy new conductor clusters which consist of multiple instances,
When we deploy a new cluster with an empty database we get the following error:
ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index"
This PR fixes this issue, by updating the flyway version (which causes this bug).


Color Artifacts in Preview with Custom Template Using Trained Nerfacto Model

Describe the bug
I created a custom template using Nerfstudio and employed a pre-trained Nerfacto model. However, when previewing the results, the colors appear very strange and do not match the expected output.
To Reproduce
Steps to reproduce the behavior:
Screenshots

Additional context
The pre-trained model was validated before and produced accurate results with the default templates.
The issue only arises when using the custom template.
I have verified that the model weights and parameters are correctly loaded.
There might be a problem with the way the custom template handles the color outputs from the model.

@Zacharie06 , what custom template are you referring to?

@Zacharie06 , what custom template are you referring to?

SA3D. The problem is sovled after I adding average_init_density=0.01 to ModelConfig. Thank you :)


init.groovy: switch to cl branch for master-builder mantle job

The mantle project has created a branch for CL specifically no longer
guaranteeing that the master branch will build successfully on CL.

Our release jenkins uses the jenkins4 branch, but CI uses master. So we'll probably want this both places?

I'll backport to jenkins4 once we land this.


Could not resolve com.soywiz.korlibs.klock:klock:1.4.0.

Hello,
I followed the instructions in the README, but I'm getting the following error :
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':shared:compileKotlinIOS'.
> Could not resolve all task dependencies for configuration ':shared:iOSCompileKlibraries'.
   > Could not resolve com.soywiz.korlibs.klock:klock:1.4.0.
     Required by:
         project :shared
      > Could not resolve com.soywiz.korlibs.klock:klock:1.4.0.
         > Could not parse module metadata https://dl.bintray.com/korlibs/korlibs/com/soywiz/korlibs/klock/klock/1.4.0/klock-1.4.0.module
            > Unsupported format version '1.0' specified in module metadata. This version of Gradle supports format version 0.4 only.

* 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 5s

For reference, here are the instructions that I followed.
def klockVersion = "1.4.0"

repositories {
    maven { url "https://dl.bintray.com/korlibs/korlibs" }
}

kotlin {
    sourceSets {
        commonMain {
            dependencies {
                implementation "com.soywiz.korlibs.klock:klock:$klockVersion" // Common
            }
        }
    }
}

settings.gradle
enableFeaturePreview('GRADLE_METADATA')

* What went wrong:
Execution failed for task ':lib:compileKotlinJvm'.
> Could not resolve all files for configuration ':lib:jvmCompileClasspath'.
   > Could not resolve com.soywiz.korlibs.klock:klock:1.4.0.
     Required by:
         project :lib
      > Could not resolve com.soywiz.korlibs.klock:klock:1.4.0.
         > Could not parse module metadata https://dl.bintray.com/korlibs/korlibs/com/soywiz/korlibs/klock/klock/1.4.0/klock-1.4.0.module
            > Unsupported format version '1.0' specified in module metadata. This version of Gradle supports format version 0.4 only.
   > Could not find com.soywiz:klock-jvm:1.4.0.
     Searched in the following locations:
       - file:/Users/asmirnov/Library/Android/sdk/extras/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - file:/Users/asmirnov/Library/Android/sdk/extras/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - file:/Users/asmirnov/Library/Android/sdk/extras/google/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - file:/Users/asmirnov/Library/Android/sdk/extras/google/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - file:/Users/asmirnov/Library/Android/sdk/extras/android/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - file:/Users/asmirnov/Library/Android/sdk/extras/android/m2repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - https://repo.maven.apache.org/maven2/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - https://repo.maven.apache.org/maven2/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - file:/Users/asmirnov/.m2/repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - file:/Users/asmirnov/.m2/repository/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - https://dl.google.com/dl/android/maven2/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - https://dl.google.com/dl/android/maven2/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - https://jcenter.bintray.com/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - https://jcenter.bintray.com/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - http://kotlin.bintray.com/kotlin-eap/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - http://kotlin.bintray.com/kotlin-eap/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - http://kotlin.bintray.com/kotlin-dev/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - http://kotlin.bintray.com/kotlin-dev/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - https://kotlin.bintray.com/kotlinx/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - https://kotlin.bintray.com/kotlinx/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
       - https://dl.bintray.com/korlibs/korlibs/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.module
       - https://dl.bintray.com/korlibs/korlibs/com/soywiz/klock-jvm/1.4.0/klock-jvm-1.4.0.pom
     Required by:
         project :lib

I moved klock to another bintray repository and another group with the hope of being able to synchronize it to jcenter. Right now I cannot do that because of artifact conflicts.
This is the right path:
https://dl.bintray.com/korlibs/korlibs/com/soywiz/korlibs/klock/klock/1.4.0/
so it seems that you are missing something here. Notice the double Klock in the path.
Repository: https://dl.bintray.com/korlibs/korlibs
Group: com.soywiz.korlibs.klock <-- yes, the group includes klock in the last part
Artifact: klock
Version: 1.4.0

Yes, I added "com.soywiz.korlibs.klock:klock:$klockVersion"``correctly to my ``build.gradle; I also have the right repository (https://dl.bintray.com/korlibs/korlibs).
However, removing `enableFeaturePreview('GRADLE_METADATA')`` seems to fix the issue.

Better reading stuff:
            > Unsupported format version '1.0' specified in module metadata. This version of Gradle supports format version 0.4 only.

The main problem here is that I'm using metadata 1.0 (Gradle 5.4.1).
I initially avoided metadata completely so it works with different gradle versions, but since I wanted to update to Kotlin 1.3.31 and can't import kotlinx.coroutines in native without metadata (I need it starting with the korio library in my stack), and it seems that metadata is the way to go, I decided to add metadata again. More info about this issue:
https://github.com/Kotlin/kotlinx.coroutines/issues/1105

Yeah, this works for me:
build.gradle:
sourceSets {
        commonMain {
            dependencies {
                ...

                implementation "com.soywiz.korlibs.klock:klock:$klockVersion"
                implementation "com.soywiz.korlibs.klock:klock-metadata:$klockVersion" // Common
            }
        }
        ...
        commonJvmMain {
            dependencies {
                ...
            }
        }
        jvmMain {
            dependsOn commonJvmMain
            dependencies {
                implementation "com.soywiz.korlibs.klock:klock-jvm:$klockVersion" // JVM
            }
        }
        jvmTest {
            dependencies {
               ...
            }
        }
        androidMain {
            dependsOn commonJvmMain
            dependencies {
                implementation "com.soywiz.korlibs.klock:klock-android:$klockVersion" // Android
            }
        }

settings.gradle:
//enableFeaturePreview('GRADLE_METADATA')

should it be api instead of implementation?
is having enableFeaturePreview('GRADLE_METADATA') commented ok because of   having dependency "com.soywiz.korlibs.klock:klock-metadata:$klockVersion"?

@Sonphil were you able to successfully resolve this for iOS specifically using the metadata solution? Can you post your build.gradle if so

@AdibaM No, I haven't resolve this

I'm going to close this. Please reopen if this is still an issue.

@4ntoine Your solution saves my life.


bridge load latency / awkward intermediary state

Describe the bug
Can we preload this better? This partially loaded image looks bad when we are waiting for things to load
Are we waiting on some SDK calls?

This looks better @pjenviri , but why is there a loading state at all?
for example this loads intantly https://jumper.exchange/
would be good to identify the delays

There was a short period (when getting/setting the chains & assets information). So, we updated it to check whether the needed information was all set before showing up on the UI.


local-exec provisioner error

Hello! hoping to get some help or insight to this error when deploying the TF scripts.  I ran pip3 install --pre azure-cosmos which updated.  but still getting this local-exec provisioner error.  Am I missing another dependency?

Hello!
Can you please provide us with the OS details on which the deployment failed? It will help us in debugging the issue.
The easiest way to deploy AzureGoat is via Cloudshell. I will request you to take a look at the following video:
https://www.youtube.com/watch?v=_FIrMr8hDHY&list=PLcIpBb4raSZGdYHKpqIu5Boc2ziga4oGY&index=6

Thankyou Jeswin!  I was running from a Windows 11 Pro - Surface Book (azure cli version 2.25, terraform version 1.2.6).  But -- anyway -- deployed it through Cloudshell as you mentioned and it deployed beautifully smooth. thankyou!


Request #104: allow arrays for postfix::config values.

Also update the spec file for postfix::config to test for arrays.

So you're passing an array but using it as string with spaces. Why not just pass a string with spaces?

This PR hasn't been updated for a long time, so I am closing it for now.
Please reopen if you still wish to address this PR.


Not working on 14.1.1 (23B81) Sonoma

Describe the bug
Seems like the app stopped working after the Sonoma update some time ago. I already tried reinstalling and revoking/granting all the permissions but still no luck.
Counter stays at 0.
Desktop (please complete the following information):

macOS version: 14.1.1 (23B81) Sonoma
2018 MBP

Additional context
I'd realy appreciate any update for the app as it's the only reason my MBP is workable

@KruinKop I have 14.1.1 installed and it works for me. Is anything showing up in your debug window?

Just checked it and it's showing a blank screen.. I will try to reinstall and check permissions again

well that did the trick, I also reinstalled karabiners which is some keybinding software. looks like they may have interfered with eachother.. Anyway thanks for the fast response and many thanks for this great program!


Bug(linter): some global objects are not included

Description
Currently, the no-undef rule treats console as an undefined global variable, this results in an unnecessary diagnostic message.
Reproduction
console.log(1);

Possible cause
Currently, oxc linter only uses BUILTINS to detect global variables, which misses detection of certain runtimes, such as browser and node.js, where global objects such as console are included. Does oxc need a config to specify runtime like eslint?

Let's port https://eslint.org/docs/latest/use/configure/language-options#specifying-environments

Hey! I'd be interested in taking the crack at this, I just need a bit more info so I don't go down the wrong path from the start.
My initial understanding based on the description and the comment was, that the env option is supposed to be parsed out from the eslint config, which is already read on this line, but then I realised that it's never used anywhere, so that's probably not the way to go.
Should a new env cli argument be added, which users can set and then based on the value of that, BUILTINS should be dynamically created with the appropriate values?

Hey! I'd be interested in taking the crack at this, I just need a bit more info so I don't go down the wrong path from the start.
My initial understanding based on the description and the comment was, that the env option is supposed to be parsed out from the eslint config, which is already read on this line, but then I realised that it's never used anywhere, so that's probably not the way to go.
Should a new env cli argument be added, which users can set and then based on the value of that, BUILTINS should be dynamically created with the appropriate values?

@simonxabris It seems like the --env cli flag https://eslint.org/docs/latest/use/command-line-interface#--env is the thing that we want to port from eslint. All behaviours should match exactly to that of eslint.

To add, I think we should also port
https://github.com/typescript-eslint/typescript-eslint/blob/1ed0733c7fea0dcb4f10dc0a54a4dafde57511df/packages/scope-manager/src/lib/
as just porting the eslint config will still mean that using a type e.g. ReturnType will still complain

just porting the eslint config will still mean that using a type e.g. ReturnType will still complain

Can you elaborate on this?

I think we should also port

This file looks crazy lol. We already have a scope manager, what usecases do we need to add?

Can you elaborate on this?

e.g.
  ⚠ eslint(no-undef): Disallow the use of undeclared variables
    ╭─[../../<PATH>.tsx:11:1]
 11 │
 12 │ export function ExampleTable({ data }: { data: ReturnType<typeof useData>['data'] }) {
    ·                                                ──────────
 13 │     const columns: ColumnDef<Data>[] = [
    ╰────
  help: 'ReturnType' is not defined.

I think, even if we ported the eslint configurations, these errors would still be reported

This file looks crazy lol. We already have a scope manager, what usecases do we need to add?

i think we just need to add those items to the scope (mainly types) (depending on env specified)


chore: add BillingService.ts test coverage

BillingService coverage

Adds test coverage for BillingService.ts (95%)
Adds LCOV as a reporter (though /coverage is ignored). This is useful to combine it with Coverage Gutters VS code extension to see the coverage
Adds a __mocks__ directory that would contain external libraries mocks (e.g Stripe)
Moves BillingService.ts string errors to a separate Errors.ts file
Sets collectCoverage: false on jest config to improve test speed
Adds coverage script to package.json

Pull Request Checklist:

[ ] Please make sure all jobs pass before requesting a review.
[ ] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
[ ] Have you lint your code locally before submission?
[ ] Did you write tests where appropriate?

Related Issue?
Screenshots (if appropriate):

This is ready for review @simlarsen, the build fails on the Probe service but probably #884 fixes that


fine tuning the cython-linter + fix W391 code

using just python 3.12
removing E701 and E703, E302,E303,E306 from ignored, already fixed
removing W391 too, fixed here

Looks good. Thanks!

Some of these could be fixed by the script mentioned https://github.com/flintlib/python-flint/pull/191#issuecomment-2317451322 which we should probably include as bin/lint_fix.py or something.


[FEAT] - Add footer section

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Add the footer section

hey @Evavic44 can the footer design template be attached so we can know what to do? and also, can this be assigned to me?
thanks 🙏🏼

Thanks, @winniffy. I'm already pushing a fix for this. Might raise a few issues to complete it. 🙂

Thanks, @winniffy. I'm already pushing a fix for this. Might raise a few issues to complete it. 🙂

alright then. thanks.


Display custom attributions

This are the changes required to display the custom attributions that were added to the viz.json in cartodb/cartodb#5270.
@javier what do you think? this is a bit hacky but it was the only way I found to set the attributions in the order I wanted (CartoDB attribution first and then the rest...). Thanks!

I think it's fine :+1:


setGlobalNetworkType doesnt work

Hi,
@tonyofrancis
Setting setGlobalNetworkType doesn't work properly in new release, i have toggled off onlyWifi switch and my downloading got stuck with status downloading.
Please have a look :)

@zubairehman this is a bug. Working on a fix

right. @tonyofrancis could you please expose a method (like setGlobalNetworkType) through which we can control queue size? coz till now i am stuck with queue size and not able to change the size at runtime.

@zubairehman Just implemented setDownloadConcurrentLimit(limit) on Fetch. So you will be able to change it during run time. Testing now.

Just released fetch 2.2.0-RC2 with a few fixes for the globalNetworkType and you can now set concurrent download limit on Fetch during runtime. See change log.

@tonyofrancis, thanks for the update. Unfortunately setGlobalNetworkType still has bugs, i was connected with my 4g and onlyWifi toggle was on but still my download didn't stop (it should stop). its was working fine in 2.1.0-RC15 release. Moreover setting setDownloadConcurrentLimit doesn't work either, i tried setting it at runtime but no affect

@zubairehman can you share your code via email? My email is on my profile. Think I can better assist that way.

@zubairehman Had a change to look at your code and also published a new version of Fetch 2.2.0-RC3.
In your code I noticed you are calling FetchHelper.getFetchInstance() inline in many places thought your app. Eg:FetchHelper.getFetchInstance().downloadConcurrentLimit(limit);
The issue is every time you call FetchHelper.getFetchInstance() inline you, are actually creating a new instance/object of Fetch and applying the settings to that instance and then that instance is garbage collected because there is no other reference to it. Your FetchHelper.getFetchInstance() method should instead do one of the following:

return Fetch.Impl.getDefaultFetchInstance()
Or
return an existing instance of Fetch that is held by FetchHelper

Also there is no need to keep calling the close method. You should only call close when you no longer need the Fetch instance.
Hope its okay to post the answer here. This will help others. Please let me know if this answer helps.

thanks @tonyofrancis, its working now and thank you soo much for your time you spent debugging my code :)

No worries. Got a change to see the many ways others use the library so I can make it better.


flacon: 9.2.0 -> 9.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/flacon/versions.
meta.description for flacon is: "Extracts audio tracks from an audio CD image to separate tracks"
meta.homepage for flacon is: "https://flacon.github.io/"
meta.changelog for flacon is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.3.0 with grep in /nix/store/4zq7rxnx961jsf3i1bprm5676bnyb5s8-flacon-9.3.0
found 9.3.0 in filename of file in /nix/store/4zq7rxnx961jsf3i1bprm5676bnyb5s8-flacon-9.3.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
flacon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4zq7rxnx961jsf3i1bprm5676bnyb5s8-flacon-9.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flacon https://github.com/r-ryantm/nixpkgs/archive/225da992bc6374e627f850d1ea99a803f25f7056.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4zq7rxnx961jsf3i1bprm5676bnyb5s8-flacon-9.3.0
ls -la /nix/store/4zq7rxnx961jsf3i1bprm5676bnyb5s8-flacon-9.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flacon

Maintainer pings
cc @snglth for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/flacon/flacon/releases.
meta.description for flacon is: "Extracts audio tracks from an audio CD image to separate tracks"
meta.homepage for flacon is: "https://flacon.github.io/"
meta.changelog for flacon is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.4.0 with grep in /nix/store/p42wyvf1kdby9yyzh60q3dy033dqc6d5-flacon-9.4.0
found 9.4.0 in filename of file in /nix/store/p42wyvf1kdby9yyzh60q3dy033dqc6d5-flacon-9.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
flacon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p42wyvf1kdby9yyzh60q3dy033dqc6d5-flacon-9.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flacon https://github.com/r-ryantm/nixpkgs/archive/16d7225c87336f3db3bc1d0f2a65353929878b0c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p42wyvf1kdby9yyzh60q3dy033dqc6d5-flacon-9.4.0
ls -la /nix/store/p42wyvf1kdby9yyzh60q3dy033dqc6d5-flacon-9.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flacon

Maintainer pings
cc @snglth for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/flacon/flacon/releases.
meta.description for flacon is: "Extracts audio tracks from an audio CD image to separate tracks"
meta.homepage for flacon is: "https://flacon.github.io/"
meta.changelog for flacon is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.5.0 with grep in /nix/store/d8fvxd91b83k1hb7635m27xkngl2bcz6-flacon-9.5.0
found 9.5.0 in filename of file in /nix/store/d8fvxd91b83k1hb7635m27xkngl2bcz6-flacon-9.5.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
flacon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d8fvxd91b83k1hb7635m27xkngl2bcz6-flacon-9.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flacon https://github.com/r-ryantm/nixpkgs/archive/4e44410ea937f81e09dea52c5c21454ae58d1c16.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d8fvxd91b83k1hb7635m27xkngl2bcz6-flacon-9.5.0
ls -la /nix/store/d8fvxd91b83k1hb7635m27xkngl2bcz6-flacon-9.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flacon

Maintainer pings
cc @snglth for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/flacon/versions.
meta.description for flacon is: "Extracts audio tracks from an audio CD image to separate tracks"
meta.homepage for flacon is: "https://flacon.github.io/"
meta.changelog for flacon is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.5.1 with grep in /nix/store/wnkgz8i138xyiib12rb4adf296q9cdz5-flacon-9.5.1
found 9.5.1 in filename of file in /nix/store/wnkgz8i138xyiib12rb4adf296q9cdz5-flacon-9.5.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
flacon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wnkgz8i138xyiib12rb4adf296q9cdz5-flacon-9.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flacon https://github.com/r-ryantm/nixpkgs/archive/f988244e9fff4b8a5ed0e3e31c4e0e5664159298.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wnkgz8i138xyiib12rb4adf296q9cdz5-flacon-9.5.1
ls -la /nix/store/wnkgz8i138xyiib12rb4adf296q9cdz5-flacon-9.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flacon

Maintainer pings
cc @snglth for testing.


New SimpleIcons images are not getting displayed

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] badge-maker NPM package

:beetle: Description
Simple-icons added a new release https://github.com/simple-icons/simple-icons/releases/tag/4.5.0
and new icons like

Express js - https://simpleicons.org/icons/express.svg
Google colab - https://simpleicons.org/icons/googlecolab.svg
Shields.io - https://simpleicons.org/icons/shields-dot-io.svg
etc.  were added in this release

But these images are not getting displayed while i am adding name of the logo in badges
https://img.shields.io/badge/google_colab-F9AB00?style=for-the-badge&logo=googlecolab&logoColor=white

I've even tried doing google-colab instead of googlecolab
https://img.shields.io/badge/google_colab-F9AB00?style=for-the-badge&logo=google-colab&logoColor=white

https://img.shields.io/badge/express_js-000000?style=for-the-badge&logo=express&logoColor=white

https://img.shields.io/badge/shields_io-000000?style=for-the-badge&logo=shields.io&logoColor=white

Whereas old icons are coming correctly
https://img.shields.io/badge/slack-4A154B?style=for-the-badge&logo=slack&logoColor=white

https://img.shields.io/badge/socket_io-010101?style=for-the-badge&logo=socket.io&logoColor=white

:link: Link to the badge
https://img.shields.io/badge/google_colab-F9AB00?style=for-the-badge&logo=google-colab&logoColor=white
https://img.shields.io/badge/google_colab-F9AB00?style=for-the-badge&logo=googlecolab&logoColor=white
https://img.shields.io/badge/express-F9AB00?style=for-the-badge&logo=express&logoColor=white
https://img.shields.io/badge/shields_io-000000?style=for-the-badge&logo=shields.io&logoColor=white

Please refer to #5369 for information on how updates to SimpleIcons get incorporated

Please refer to #5369 for information on how updates to SimpleIcons get incorporated

Thanks for the update

Thanks for the update


Configuration with name 'compile' not found.

Hello,
I am trying to implement this module in my and i face below issue,
On android side
-Caused by: org.gradle.api.plugins.UnknownPluginException: Plugin with id 'maven' not found.
after resolving it will got another error like
Build file '/Users/metizsoft_m1/NumberScanDemo/node_modules/react-native-openalpr/android/build.gradle' line: 106
A problem occurred configuring project ':react-native-openalpr'.

Configuration with name 'compile' not found.

On Ios Side got below Error
Showing All Issues
File not found: /usr/lib/libstdc++.6.0.9.dylib

iOS issue is described here https://github.com/RobertSasak/react-native-openalpr/issues/105#issuecomment-831113831


The doc on the getting started page referencing to a version that doesn't exist

Just a quick remark: The following yaml referencing to version: '>=0.16.0-rc.3' which doesn't exist! and it failed when installing it.
https://weaveworks.github.io/tf-controller/getting_started/#:~:text=kubectl apply -f https%3A//raw.githubusercontent.com/weaveworks/tf-controller/main/docs/release.yaml

We're testing the release pipeline of RC3 for now. Please change it to RC2 in the mean time.
Sorry for inconvenience.

RC3 has been released.


Multilingual Support

Laravel Version: 5.6.29
PHP Version:7.2.7
Laravel-admin: 1.5.x-dev

This is a excellent template for Laravel to be used. How can I integrate multilingual support? Like, I want to place 2 flags on the top-right corners. So when I click on them, it should translate, without going back to the previous page.

Laravel has already built-in multilingual support:
https://laravel.com/docs/5.6/localization.
Sorry for any inconvenience.


Recommend filters not decrease buffer limits

Commit Message: Recommend filters not decrease buffer limits
Additional Description: Just changing flow_control.md to recommend not calling set(En|De)coderBufferLimit when it would decrease the buffer limit, as that's likely to conflict with other filters, vs. increasing the limit is unlikely to cause conflicts. This is inspired by #23774, in which it turned out that a code solution to this awkwardness is not reasonable, so a documentation solution is the next best thing.
Risk Level: None, it's documentation.
Testing: No, it's documentation.
Docs Changes: Yes, it is.
Release Notes: n/a
Platform Specific Features: n/a

/assign @KBaichoo


Npm releases

Hi there,
Was wondering if there is an automated process to release to npm, and if not are you guys open for PR? Would be great if all commits to master generate a version to npm even its just a patch/development version.
I am looking to use draft-js as a node module dependencie and the current version on npm does not have some of the fixes

@zpao, thoughts?

For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same shortcut syntax you use for npm install: "repository": "npm/npm"

Via https://docs.npmjs.com/files/package.json
So in this case, dropping "draft-js": "facebook/draft-js" into your package.json would use the repo’s master branch. It’s effectively a dev version of Draft.

@gscottolson only problem with that is that we have a build step so it wouldn't actually work. You'd have to install dev dependencies and run the build process.
I personally think doing automated releases after every commit is pretty obnoxious and extraneous. I think releases should have a bit of coherence and planning around them, otherwise you're constantly fighting to keep up. Doing pretty frequent releases is totally fine though. We've only been out a week and I think at this point we probably have enough feedback and fixes to do another release. I haven't been watching closely so I'm not sure if we can call it a 0.1.1 or 0.2, nor do I know if there are things almost done that we'd like to get out. So I'll leave that up to @hellendag. What I think would be good is if we keep a running changelog so that each PR modifies that (I've been following the keepachangelog pattern with "unreleased" in the fbjs project) so that it's really easy to track and decide at any point in time what the next release should be called.

As @zpao  has stated, unfortunately we cant just point to the git-hub repository. I also think that maybe a release on each commit could be an overkill and I also like the idea of running a change-log.
On the other hand would be great to have a way to test development branch via NPM, What could be done to work around the build step constraints that block us from being able to point to the git-hub repository directly?  Is there any other viable solution?

We'll never be able to point here*. Some pieces could eventually be worked out (eg, using @providesModule) but other things like JSX and Flow annotations need to be compiled out. Even ES6 classes could probably stay in for a GH-only version.
I think this is especially painful in this first week as things get fixed quickly but won't actually be an issue longer term.

(ok so we could do a really crappy thing and move devDeps into regular dependencies and then do the actual build step when installed but I really don't like that. It would work but I'd have to cry myself to sleep at night)

Thanks for the clarification, @zpao. I hope you get a restful night of sleep. :night_with_stars:

Why not just frequently release with @alpha/@beta/@test tags on npm? As @zpao pointed out, this repo was released only a week ago, but the API will likely change in the starting phase (at least new functions will be introduced like https://github.com/facebook/draft-js/blob/master/src/component/selection/getVisibleSelectionRect.js), which makes a quick release cycle imperative to test these out. Especially since this is mostly based on feedback and users needs.

I am happy with most of the suggestions in here, would be great however to have a new draftjs npm release soon, maybe something like 0.1.1

Aiming for Tuesday. :)

Trying to do releases as often as I can while making sure our use cases on FB remain stable. Hopefully it's been sufficient. :)


Slickgrid not displaying correctly inside jquery accordion.

I have three grids inside a jquery accordion and they display correctly when the page first loads. Once the page is refreshed the grids are all shrunken like in the first picture. I did the edit from the slickgrid fork that was suggested by user 6pac https://github.com/6pac/SlickGrid/commit/687d38d755933830bcd889a3658b9dab8132060d
this yielded the results in picture two. The column headers now look better but the cells are not displaying correctly. I also have a this question posted on stack overflow with a 50 point bounty. Any help is appreciated. Thank you
http://stackoverflow.com/questions/29991072/slickgrid-inside-jquery-accordion-columns-not-displaying-properly

If it's not the 'display:none' issue, could it also be the border-box issue ? https://github.com/6pac/SlickGrid/pull/4#issuecomment-99757214

Only solution i found was to do a full reload which gives off flicker. Had to keep project moving but hope to find a solution to this problem. Thanks for all your help!
window.location.reload();

Look at issue #1066
It's probably caused by the same little bug, which I seem to have solved by adding a single line in slick.grid.js

A patch for this issue (and #1066) has been added to the 'alternative master' repo.
Repo: https://github.com/6pac/SlickGrid
Latest release: https://github.com/6pac/SlickGrid/releases
Blog post: http://low-bandwidth.blogspot.com.au/2015/06/slickgrid-with-jqueryui-and-bootstrap.html
The latest release has added examples for Bootstrap and the jQueryUI Accordion that may help provide a standardised page for testing, and demonstrate a known good configuration.
You don't stipulate your browser, so I'll be interested to see how the examples look to you.


[RFC]Created circle.yml for CircleCI

Created a file for CircleCI testing

This PR is related to https://github.com/nistats/nistats/issues/21

This sounds good, but the point is to feed the documentation, that remains currently empty.
For the moment, I would suggest to rely on sphync-gallery and simply run the examples (see Nilearn).
Best,


Add missing pip requirement in host

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Addresses #1
@bstaber -- I think this will fix things. When I reviewed your recipe I missed that pip was missing from the host requirements. It must just be present in the staged-recipe CI. I didn't increment the build number since it failed, but usually you'll want to do this if you're patching a CI thing and not a version or some run requirement.

Geat, thanks again !


26b Release: REPL

The next thing any programmer expects from a programming language is a REPL (read-eval-print loop). That is, they expect, when a program is launched without any arguments, to see an interactive prompt that lets them type statements, one line at a time. This is what the python REPL looks like:
$ python
Python 3.8.12 (default, Aug 30 2021, 16:42:10)
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print('Hello World!')
Hello World!

Our users will be expecting pseudo to implement a REPL as well, so let's respond to that expectation. For now pseudo does not have a REPL, but by the end of this chapter it will!
https://github.com/nyjc-computing/pseudo-9608/blob/1fab24d9e7ff6a9b64d6b55aa7c546423083c095/pseudocode/__init__.py#L119-L122

REPL vs script
The key differences between REPL mode and script mode are:

in REPL mode, the user is continually prompted for more code, while script mode exits after running the script
The global frame persists after each statement in REPL mode, but resets between scripts
Any errors that occur in a script causes execution to halt, while errors in  REPL mode are simply reported without program exit

REPL mode
Let's start with the simplest possible REPL: a while loop that reads user input with input(), evaluates the input with Pseudo.run(), and prints the result with ... well, print(): [55c907831488d37d3347f589a5813e9b784f58d2]
https://github.com/nyjc-computing/pseudo-9608/blob/55c907831488d37d3347f589a5813e9b784f58d2/pseudocode/__init__.py#L118-L128
$ pseudo
Pseudo 0.4.0
### OUTPUT "Hello World!"
Hello World!
###

Simpler than we thought! This is still lacking all the complexity required to handle other tasks, such as arrow key movement, command history, and multi-line statements. But it's a start!

Preserving global frame
The global frame is re-instantiated with every call to Pseudo.run():
https://github.com/nyjc-computing/pseudo-9608/blob/55c907831488d37d3347f589a5813e9b784f58d2/pseudocode/__init__.py#L70-L80
This means that in our REPL, each line is running with a completely new frame. We wouldn't even be able to declare a variable and then assign to it.
The simplest way to keep the frame around after run() is to instantiate the frame once, when Pseudo is instantiated, and then keep using it. If we want a new frame, we just make a new instance of Pseudo.
Let's make those changes:
https://github.com/nyjc-computing/pseudo-9608/blob/7c8fa649bb0fc9b5fe1fe858ff70ee7d9812ae3b/pseudocode/__init__.py#L51-L61
$ pseudo
Pseudo 0.4.0
### DECLARE Variable : STRING
### Variable <- "Hello World!"
### OUTPUT Variable
Hello World!
###

And now we can run() single lines with a persistent frame.

Report without exit
We actually already accomplished this earlier in REPL Mode; by simply reporting errors without calling sys.exit(), our REPL continues to run instead of exiting.

So there are a bunch of issues to be addressed, but not in this chapter:

#77 REPL Mode should enable cursor navigation (with arrow keys)
#78 Command history for REPL Mode
#79 Multi-line statement support for REPL Mode


meltano add transformer dbt - extra lines in meltano.yml

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3393
Originally created by @vischous on 2022-04-12 21:13:27

After running meltano add transformer dbt the meltano.yml related config looks like this
  transformers:
  - name: dbt
    pip_url: 'dbt-core~=1.0.0 dbt-postgres~=1.0.0 dbt-redshift~=1.0.0 dbt-snowflake~=1.0.0
      dbt-bigquery~=1.0.0

      '
  files:
  - name: dbt
    pip_url: git+https://gitlab.com/meltano/files-dbt.git@config-version-2

Note the 2/3 extra new lines

View 2 previous comments from the original issue on GitLab


[BUG] Zigbee devices stopped working after HA update

Hi,
I upgraded my Home Assistant to version 2022.11.0 and now all my Zigbee devices have stopped working. I’m using a Combee II and after unplugging it I got ZHA to reload as that originally had the status of failed. Once reloaded if I try and turn off or on my devices I get the following errors:

Logs

[0x0503:11:0x0300]: async_initialize: all attempts have failed: [TimeoutError(), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>')]
[0x33F1:1:0x0406]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>')]
[0x2BFB:11:0x0008]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), TimeoutError(), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>')]
[0xF7F2:1:0x0102]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.NWK_ROUTE_DISCOVERY_FAILED: 208>'), DeliveryError('Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>')]
[0x1E20:1:0x1000]: Couldn't get list of groups: Failed to deliver packet: <TXStatus.MAC_CHANNEL_ACCESS_FAILURE: 225>

Everything was working fine before upgrading to 2022.11.0.
Any help will be great. Thanks

MAC_CHANNEL_ACCESS_FAILURE Has nothing to do with the upgrade. It means you have significant interference and the zigbee stick can’t communicate. Ensure your coordinator is not near an SSD, Make sure it is on an extension cord and plugged into usb 2 port if possible.

Hi dmulcahey, thanks for commenting. I appreciate your feedback. I have already done those things and as I mentioned in my post everything was working until I upgraded. I have now rolled back to 2022.10.5 without changing anything and my ZHA is working again. So I can only think it must be the upgrade to 2022.11.0 as why was it broken with the new version and works with 10.5?

TXStatus.MAC_CHANNEL_ACCESS_FAILURE = the coordinator is trying to sending but the radio channel is blocked (Zigbee device is not allowed sending if some other device is sending and is first listening before try sending, therefor you is getting it the TXStatus).
If your coordinator is supporting radio scan to see how its looking in the air from the radio view and also one WiFi scan with your mobile with one app and you can  see how its in the real.  One thing WiFi and Zigbee channels numbers is not the same so need matching frequencies if its overlapping.

TXStatus.MAC_CHANNEL_ACCESS_FAILURE = the coordinator is trying to sending but the radio channel is blocked (Zigbee device is not allowed sending if some other device is sending and is first listening before try sending, therefor you is getting it the TXStatus).
If your coordinator is supporting radio scan to see how its looking in the air from the radio view and also one WiFi scan with your mobile with one app and you can see how its in the real. One thing WiFi and Zigbee channels numbers is not the same so need matching frequencies if its overlapping.

Hi MattWebstb, thank you for your reply and that is interesting. I have now changed my Wifi channels as I noticed my Zigbee channel is 11.
But can you see why I’m thinking it’s been caused by the update when it only started happening after updating and now I’ve rolled back to 10.5 it’s working again?

If Zigbee is on 11 (the lowest channel) your WiFi shall being oi the middle and upper part of the band for not blocking the Zigbee coordinator.
Also downloading one WiFi scanner for your mobile is good then can see if you have some neighbors spamming the air.I cant telling if its somthing in the code that is triggering the log message but if its true sent from the coordinator its what is see in the "air" and if the radio channel is blocked it cant sending any thing and we cant forcing it to do (its the standard for this devices and is one must for certifying the Zigbee stack that is controlling all things in the device).

Closing, as MAC_CHANNEL_ACCESS_FAILURE is a not a zha-quirks issue.
If you still need support, I'd recommend joining the HA Discord and asking in the #zigbee channel.
Otherwise, you can also try the forums but they're not as actively monitored by the devs.


Fix #1032, Send->Write name update for SB write cmds

Describe the contribution
Fix #1032 - updated "Send" to "Write" in command names that write files.  Includes function names, command code names and comments.
Testing performed
Standard build and run unit tests, passed.  Made user's guide w/ no errors/warnings.
Expected behavior changes
None, name change to fix misnomer
System(s) tested on

Hardware: cFS Dev Server
OS: Ubuntu 18.04
Versions: Bundle main + this commit

Additional context
Additional update pending #1102 merge
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB:2021-01-27 APPROVED
Just changes "send" to "write" where appropriate to ensure code written matches how it actually work

CCB:2021-01-27 APPROVED
Just changes "send" to "write" where appropriate to ensure code written matches how it actually work

Fixed static analysis errors.

Fixed static analysis errors.


Partner page option 2

closing this because we went for option 1: https://github.com/open-energy-transition/oet-website/pull/29


Esc does not work in INSERT mode after multicursor is on.

Just give me an E120 error and do not exit from multicursor mode.
My vimrc and my vim --version output

@Burlter could you please provide us with:

a minimal vimrc to reproduce the issue (your vimrc is almost 100 lines)
the exact keys that you press to trigger this issue

As a reminder, per the README:
https://github.com/terryma/vim-multiple-cursors#q--pressing-i-after-selecting-words-with-c-n-makes-the-plugin-hang-why
Thanks,
Antoine

I press <C-n><C-n><C-n>csometxt<Esc>. If i do not use vim-autoclose, it works perfectly. minimal vimrc


[FEATURE]: solution for running Supabase on Vercel Edge functions

Describe what you want
Supabase setup currently uses postgres.js which doesn't work on Vercel Edge functions.
Solution:
(Need to add this to the docs)
Use @vercel/postgres package to connect to Supabase db - as recommended in their Official Supabase X T3 Turbo Template

this is a workaround, but makes supabase queries really slow


Add support for watchOS

Same as in #10. Due to the technology used this should be very possible to achieve.

SpriteKit isn't available for watchOS.


test, masquerade: Add dual stack vmi to vmi ping

What this PR does / why we need it:
As part of migrating the network tests to dual stack we need to check
that ping at masquerade between VMs is working with ipv4 and ipv6.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @oshoval @EdDev

Thanks
LGTM
but please see Edy comment about the commit message

Thanks
/lgtm

/cc @AlonaKaplan

/approve
/hold feel free to remove the hold once you will answer my small comment.


Fixed Ctrl+C correct exiting

Hi @mixalbl4-127 ,
Thanks for creating the PR.
Could you please explain the problem and your solution so that we can learn what you are trying to fix?

Hi @huan
when you make for example Connect.desktop shortcut in folder with sshpass command for easy connect and try to abort it using ctrl+c its not working because of setsid

Hi @mixalbl4-127 , please add an entry in README (I have created it for you). After that, this PR will be ready to be merged.
Thank you very much for your contribution!

@huan done :)

Thank you very much, @mixalbl4-127 !


Abstract disk operations for different disk drivers

Which issue(s) this PR fixes:

Issue longhorn/longhorn#7672
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context
Deps on https://github.com/longhorn/go-spdk-helper/pull/72

ping @innobead


Config map length fix, fix bug with missing events by closing the websocket

Codecov Report

Merging #367 (750a958) into main (7065837) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #367   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          239       239
  Lines        12888     12889    +1
=========================================
+ Hits         12888     12889    +1

Impacted Files
Coverage Δ

internal/blockchain/ethereum/ethereum.go
100.00% <100.00%> (ø)

internal/config/config.go
100.00% <100.00%> (ø)

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 7065837...750a958. Read the comment docs.


Make util functions promises

For better reliance, we should make

registerParachain
setBalance
startCollator
and the // Then launch each parachain part of index

functions that return a promise that resolves when the process is done.
Checkout how I implemented it here: https://github.com/paritytech/polkadot-launch/pull/55/files
I volunteer to make these changes

@pepyakin @shawntabrizi  ?

@pepyakin @shawntabrizi Did you get any chance to read this?

I don't think there is any downside in making those function return promises

Yeah, just do it. :)

yeah go ahead :)

cool :)

This is now merged into master and can be closed


[WIP] Import Doxygen XML output in documentation on ReadTheDocs

Codecov Report

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

@@          Coverage Diff           @@
##           master    #244   +/-   ##
======================================
  Coverage    97.2%   97.2%
======================================
  Files          42      42
  Lines        1970    1970
======================================
  Hits         1915    1915
  Misses         55      55

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 fd8a326...73bc50e. Read the comment docs.

To view the output, run:
$ docker run --rm -v <DTK root dir>:/scratch dalg24/clang-format:breathe sphinx-build /scratch/docs/source /scratch/docs/build

and open docs/build/index.html.

I disabled the import of the Doxygen XML output on Travis CI.  Please review.  The PR will need a final cleanup before merge.

So is scope is basically a plugin you wrote that is called by sphinx?

Yes it is essentially a plugin.  I cannot take the credit for it.  I was largely inspired by https://gist.github.com/kakawait/9215487

Ready to merge


Improve CodeEdit's callhint highlight visibility

This makes the currently edited parameter more visible in the script editor's code completion hint.
This can be remade for 3.x if we agree on the design here.
This closes https://github.com/godotengine/godot-proposals/issues/3074.
Preview
Before

After

Thanks!


Refs #3839 - Fix error where there is no query supplied

When you add a listing block with no criteria, it will give a backend error.
Fixes #3839

@davisagli I made another PR to main branch. https://github.com/plone/volto/pull/6423


Adds missing command for install (mac)

Required for users who didn't previously have Rust installed.
Instructions from #30 were insufficient without more google search on how to install. Answer found on tokenizers page

Noting I had to use pip3 and I also had to install setuptools_rust for the pip command to succeed

Should be merged

Thanks! I made a minor edit; will merge this one and then #161.


[ISSUE] Skill can connect to Ask Navidrome but requests don't process (HTTP Error 403)

Describe the issue
Asknavidrome recieves but is unable to process requests from the alexa skill.
When using the "OPEN InvocationName" command the developer console or device responds with ready but the log shows this error:
2023-06-03 23:25:29,994 - asknavidrome.subsonic_api - ERROR - Failed to connect to Navidrome
When using the "ASK InvocationName to DoAnything" command the console/device can't proceed and the log has this error:
2023-06-03 23:26:47,948 - root - ERROR - General Exception: HTTP Error 403: Forbidden
Operating System
Docker Compose (under Portainer on Ubuntu).
To Reproduce
Ask the device or dev console to "OPEN InvocationName"
Then ask the device or dev console to "ASK InvocationName to play music by ArtistName" or "ASK InvocationName to play music"
Logs
2023-06-03 23:25:28,807 - werkzeug - INFO - <IP_ADDRESS> - - [03/Jun/2023 23:25:28] "POST / HTTP/1.1" 200 -
2023-06-03 23:25:29,994 - asknavidrome.subsonic_api - ERROR - Failed to connect to Navidrome
2023-06-03 23:25:30,029 - werkzeug - INFO - <IP_ADDRESS> - - [03/Jun/2023 23:25:30] "POST / HTTP/1.1" 200 -
2023-06-03 23:26:14,473 - root - ERROR - General Exception: HTTP Error 403: Forbidden
2023-06-03 23:26:14,473 - root - ERROR - Request Type Was: IntentRequest
2023-06-03 23:26:14,473 - root - ERROR - Intent Name Was: NaviSonicPlayMusicByGenre
2023-06-03 23:26:14,475 - werkzeug - INFO - <IP_ADDRESS> - - [03/Jun/2023 23:26:14] "POST / HTTP/1.1" 200 -
2023-06-03 23:26:47,948 - root - ERROR - General Exception: HTTP Error 403: Forbidden
2023-06-03 23:26:47,948 - root - ERROR - Request Type Was: IntentRequest
2023-06-03 23:26:47,948 - root - ERROR - Intent Name Was: NaviSonicPlaySongByArtist
2023-06-03 23:26:47,951 - werkzeug - INFO - <IP_ADDRESS> - - [03/Jun/2023 23:26:47] "POST / HTTP/1.1" 200 -
Comments
Navidrome instance is externally accessible by android apps and web browsers using the same credentials in the docker compose file)
Asknavidrome service is externally accessible (although shows a 405 method not allowed page when viewed by a browser)
I use cloudflare tunnels to access the containers.

Hi,
The 405 when accessing the skill is normal if a none complete request is sent so that should be nothing to worry about.
The issue looks to be an internal one in that the skill container cannot connect to your navidrome instance.
To troubleshoot further I would open a shell in the skill container and use curl / to try and get to your navidrome instance to see what is happening.  The external side looks good from your logs, the intent requested gets to the skill container fine.

Thank you for the suggestion.
From inside the asknavidrome container I can curl the navidrome instance - the returned results include a message about needing to enable javascript but I expect that doesn't mean anything given curl probably can't process JS.
I can also access a bunch of URLS (google, bing etc).
Looks to me like the container can reach both the internet and the navidrome instance.
Could it be something on the amazon end?

It does look like something like that, can you post your skill config file, redacting the passwords and IDs please?  When in the skill container and attempting to CURL the Navidrome instance there should be no mention of JavaScript, it looks like the request is going somewhere else.  Here is an example of what I get (replace NAVIDROME-URL with your URL (the contents of the NAVI_URL environment variable):
/opt/asknavidrome # curl https://NAVIDROME-URL/rest/ping

<subsonic-response xmlns="http://subsonic.org/restapi" status="failed" version="1.16.1" type="navidrome" serverVersion="0.47.5 (86fe1e3b)"><error code="10" message="Missing required parameter "u""></error></subsonic-response>

We can ignore the error, that's expected as we haven't authenticated, you should be getting something starting with "subsonic-response" though.  If you're not getting that I suspect the path the skill has to the Navidrome REST API is incorrect.

When I curl with my URL from inside the container I get pretty much the exact same result you posted (although I seem have a more recent version of navidrome).
<subsonic-response xmlns="http://subsonic.org/restapi" status="failed" version="1.16.1" type="navidrome" serverVersion="0.49.3-SNAPSHOT (a984bbbc)" openSubsonic="true"><error code="10" message="Missing required parameter "u""></error></subsonic-response>
I'm using compose so all my config is in the file..
  navisonic:            image: 'ghcr.io/rosskouk/asknavidrome:latest'     container_name: REDACTED     environment:       - 'NAVI_SKILL_ID=REDACTED'       - 'NAVI_URL=https://REDACTED'       - 'NAVI_USER=guest'       - 'NAVI_PASS=REDACTED'       - 'NAVI_SONG_COUNT=50'       - 'NAVI_PORT=443'       - 'NAVI_API_PATH=/rest'       - 'NAVI_API_VER=1.16.1'       - 'NAVI_DEBUG=3'                   ports:       - '5000:5000'     logging:       driver: "json-file"       options:         max-size: "10m"         max-file: "1"     deploy:       restart_policy:         condition: on-failure         delay: 5s         max_attempts: 3         window: 120s

Hi,
This seems strange. I'll try updating my Navidrome instance as soon as I can to see if I can recreate the issue.  The problem looks like it is just the skill not being able to connect to your Navidrome instance and once that's resolved it should just work

I was getting similar issue trying to hit my public navidrome url sitting behind cloudflare,
I dumped auth tokens and replicated exact requests libsonic is doing down to diff in User-Agent.
And it looks like cf is very aggressive about pythons3 urllib's 'User-Agent': 'Python-urllib/*.
Give it it a try if you are using that, also probably should not be using public url anyway.
#works (curl user agent)
curl -v https://<you url>/app
# 403
curl -v https://<you url>/app -H 'User-Agent: Python-urllib/22.1'

@TemporalUncertainty

I seem to have run into the same issue, I assume its related to how clear passwords are no longer in use for the newer deployments and now needs token? If so is there a way to configure this to work with the newer design?
f your targeting API version 1.12.0 or earlier, authentication is performed by sending the password as clear text or hex-encoded. Examples:
http://your-server/rest/ping.view?u=joe&p=sesame&v=1.12.0&c=myapp
http://your-server/rest/ping.view?u=joe&p=enc:736573616d65&v=1.12.0&c=myapp
Starting with API version 1.13.0, the recommended authentication scheme is to send an authentication token, calculated as a one-way salted hash of the password.
This involves two steps:
For each REST call, generate a random string called the salt. Send this as parameter s.
Use a salt length of at least six characters.
Calculate the authentication token as follows: token = md5(password + salt). The md5() function takes a string and returns the 32-byte ASCII hexadecimal representation of the MD5 hash, using lower case characters for the hex values. The '+' operator represents concatenation of the two strings. Treat the strings as UTF-8 encoded when calculating the hash. Send the result as parameter t.

For example: if the password is sesame and the random salt is c19b2d, then token = md5("sesamec19b2d") = 26719a1196d2a940705a59634eb18eab. The corresponding request URL then becomes:
http://your-server/rest/ping.view?u=joe&t=26719a1196d2a940705a59634eb18eab&s=c19b2d&v=1.12.0&c=myapp
https://www.subsonic.org/pages/api.jsp#versions


Browser support

It seems like safari browser doesn't render it properly.
I tried
https://vuetifyjs.com/en/getting-started/browser-support/
Please let me know how this can be applied.
Babel polyfill gives me tons of errors on building as well

What version of safari are you having problems? What's the problem? Do you have any errors? This is just an extension that should have nothing to do with the browser support (in theory). Please be more specific when you fire an issue.

Sorry about that.
Was using safari 10, the issue was node_modules are not being transpiled by babel.
I had to add this
.webpackConfig({
module: {
rules: [{
test: /.jsx?$/,
use: [{
loader: 'babel-loader',
options: Config.babel()
}]
}]
},
}
on my webpack.mix.js
Maybe you can include an option for this in the package since laravel opt to not transpile node_modules folder.


sysutils/api-backup: add json download functionality

This PR adds a new API endpoint /api/backup/backup/download/json that can be used to download a backup of the config.xml in JSON:
{"status":"success","filename":"config.xml","filetype":"application\/xml","content":"REDACTED"}

This is necessary for some cases where a "real" API is needed. The existing API endpoint /api/backup/backup/download is nice for shell scripts or when using curl to perform backups. However, it does not behave like any other OPNsense API, making it cumbersome to implement in existing systems/applications.
So this additional API endpoint provides a OPNsense-like API with the same goal: provide an easy way to perform automatic backups of the system configuration. And it does not increase code complexity in any meaningful way, so everyone wins. :)

@fabianfrz You're the maintainer of this plugin... so what do you think about this proposal? :)

@fraenki The change itself looks ok but it may cause an out of memory since the object is then multiple times in memory. This would only affect large deployments and is out of my/your control anyway.
Actually the current response would be a valid XML payload, so in theory perfectly fine REST, howver your change is fine as well :)
I guess you can merge it by yourself.

@fabianfrz Thanks for the in-depth review. Much appreciated! :)

@fichtner Please merge to stable/23.1 for next release :)


Create op.txt

Odesа Polytechnic National University.
https://op.edu.ua

@illiaUzun-academic First stage of verification passed, official domain is op.edu.ua as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@illiaUzun-academic Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Warmup with Custom Payload

Hi
We are facing issue related to Custom payload for every function but it is not working. can you please help us to solved this issue.
Thanks,
Niket Shah

Hi @niketshahpip
Can you elaborate a bit on what's exactly your issue?
What version of serverless and warmup plugin are you using?
etc.

Hi @juanjoDiaz
I want to Create Custome Payload for each method
`service: sample
plugins:

serverless-plugin-lambda-warmup

provider:
name: aws
runtime: java8
user: ${opt:user, 'dm-dev'}
pass: ${opt:pass, 'pass-dev'}
iamRoleStatements:
- Effect: Allow
Action:
- dynamodb:DescribeTable
- dynamodb:Query
- dynamodb:Scan
- dynamodb:GetItem
- dynamodb:PutItem
- dynamodb:UpdateItem
- dynamodb:DeleteItem
Resource: ${self:provider.dynamodb-arn-table}/*
package:
artifact: ${self:provider.package-name}
custom:
warmup:
enabled: true # Whether to warm up functions by default or not
folderName: '_warmup' # Name of the folder created for the generated warmup
cleanFolder: false
name: 'Test'
events:
- schedule: 'cron(0/5 * * * * *)' # Run WarmUp every 5 minutes Mon-Fri between 8:00am and 5:55pm (UTC)
package:
individually: true
prewarm: true # Run WarmUp immediately after a deploymentlambda
concurrency: 1 # Warm up 5 concurrent instances
allowed-headers:
  - Content-Type
  - X-Amz-Date
  - Authorization
  - X-App-Version
  - Accept-Language
  - User-Agent
  - source_type
documentation:
  models:
    -
      name: "EmptyModel"
      contentType: "application/json"
      schema:
        $schema: "http://json-schema.org/draft-04/schema#"
        title: "Empty Schema"
        type: "object"

functions:
CustomersByIds6:
handler: function.custId
warmup:
payload: {"id":1216}
concurrency: 1
enabled: true
events:
- http:
path: test
method: get
cors:
origin: "*"
headers: ${self:custom.allowed-headers}
allowCredentials: true
integration: lambda
response:
statusCodes:
200:
pattern: ''
template:
application/json: ''
documentation:
description: >
Get method for test
methodResponses:
- statusCode: '200'
responseModels:
            "application/json": "EmptyModel"

CustomersByIds7:
handler: function.test2
warmup:
payload: {"id":1217}
concurrency: 1
enabled: true
events:
- http:
path: test2
method: get
cors:
origin: "*"
headers: ${self:custom.allowed-headers}
allowCredentials: true
integration: lambda
response:
statusCodes:
200:
pattern: ''
template:
application/json: ''
documentation:
description: >
Get method for test2
methodResponses:
- statusCode: '200'
responseModels:
            "application/json": "EmptyModel"

Outputs:
NewOutput:
Description: "Package Name used."
Value: builds/${opt:package-name}
`
in a given snippet, I give custom payload but when I check it my event in cloud watch.

payload: {"id":1217} is equivalent to payload: '{"id":1217}' (it's a string).
If you want to pass it as an object you have to options.
1.- Using yaml object notation
payload:
  id: 1217

Indicating that the string shoudl be treated as an object:
payload: {"id":1217}
payloadRaw: true

I strongly recommend the first one since I'm planning to get rid of the payloadRaw option as soon as I can 🙂
Does this help?

ok Let me test it.

Any news on this?

Closing because of lack of activity


OAuth2 InsecureTransportError

I start weconnect-mqtt via systemd with these parameters:
/usr/local/bin/weconnect-mqtt --mqttbroker mqtt.lan --netrc /usr/local/etc/weconnect.conf --pictures --picture-format png --convert-times Europe/Berlin --republish-on-update --interval=300

Every 5 minutes the service is restarted with an error:
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]: Traceback (most recent call last):
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/bin/weconnect-mqtt", line 8, in <module>
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     sys.exit(main())
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 343, in main
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     mqttCLient.run()
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 782, in run
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     self.updateWeConnect()
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 462, in updateWeConnect
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     self.weConnect.update(updateCapabilities=self.updateCapabilities, updatePictures=self.updatePictures, selective=self.selective, force=True)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/weconnect.py", line 194, in update
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     self.updateVehicles(updateCapabilities=updateCapabilities, updatePictures=updatePictures, force=force, selective=selective)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/weconnect.py", line 205, in updateVehicles
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     data = self.fetchData(url, force)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/weconnect.py", line 373, in fetchData
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     statusResponse: requests.Response = self.session.get(url, allow_redirects=False)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/requests/sessions.py", line 602, in get
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     return self.request("GET", url, **kwargs)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/we_connect_session.py", line 69, in request
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     return super(WeConnectSession, self).request(
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/openid_session.py", line 194, in request
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     url, headers, data = self.addToken(url, body=data, headers=headers, access_type=access_type, token=token)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/openid_session.py", line 238, in addToken
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     self.login()
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/we_connect_session.py", line 76, in login
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     response = self.doWebAuth(authorizationUrl)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/we_connect_session.py", line 253, in doWebAuth
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     afterLoginResponse = self.get(afterLoginUrl, allow_redirects=False, access_type=AccessType.NONE)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/requests/sessions.py", line 602, in get
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     return self.request("GET", url, **kwargs)
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/we_connect_session.py", line 69, in request
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     return super(WeConnectSession, self).request(
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:   File "/usr/local/lib/python3.10/dist-packages/weconnect/auth/openid_session.py", line 188, in request
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]:     raise InsecureTransportError()
Dec 14 14:07:52 mqtt weconnect-mqtt[45693]: oauthlib.oauth2.rfc6749.errors.InsecureTransportError: (insecure_transport) OAuth 2 MUST utilize https.
Dec 14 14:07:52 mqtt systemd[1]: weconnect.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 14:07:52 mqtt systemd[1]: weconnect.service: Failed with result 'exit-code'.
Dec 14 14:07:52 mqtt systemd[1]: weconnect.service: Scheduled restart job, restart counter is at 2149.
Dec 14 14:07:52 mqtt systemd[1]: Stopped WeConnect.
Dec 14 14:07:52 mqtt systemd[1]: Started WeConnect.

weconnect conf looks like:
# For WeConnect
machine volkswagen.de
login<EMAIL_ADDRESS>password xxxxxxxxxxxxxxxxxxx
account yyyy

# For the MQTTBroker
machine mqtt.lan
login weconnect
password xxxxxxxxxxxxxxxxxxxxxxxxx

This configuration used to work for 8 weeks or so and suddenly stopped working 10 days ago. Is this a bug? Any hints?

No, you need to accept new terms and conditions. Easiest is to logout the app and in again. It will ask you to consent.

That helped. Many thanks!

Hi, in my case the simple logout and accepting terms didn't work.
What finally helped was login to (https://id.vwgroup.io/account) , change country, logout, login, accept terms, change country back, logout, login as described here https://github.com/tillsteinbach/WeConnect-cli/issues/152.
Hope this helps others.


Removing x-forwarded-for from the list

As per CUSTESC-24546, this header is NOT removed by the "Remove visitor IP headers" rule

Actually, following the comments in the Jira, we need to leave this line there.
But let's add a comment then!
Maybe something like:

x-forwarded-for (Please note that only the x-forwarded-for header added by another CDN or proxy is removed: the initial client IP from the eyeball will be present in the header)

Hi @pedrosousa
Should we close this PR? Should I raise a new one?
Or can you edit the content based on my latest comment?
Thanks!

Hi @lougayou
It's on my personal backlog! I'll update the text, check the final version with Maurizio, and then merge.


Whitelist NinjaKiwi domains

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[x] App Broken
[x] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name: energized ultimate

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

*.api.ninjakiwi.com
*.static-api.nkstatic.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client: NextDns

Version: Latest version

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail: There was another post about this from a ninja kiwi dev but apparently it’s in the white list but it’s still being blocked this domain is used for game backups and player avatars and etc

Thank you for making Energized Protection great, with your kind help!
A project by Ador with ❤

#638


FR: entity-button (show_name) / glance (show_icon)

It might be nice to be able to hide the name of an entity button if the icon is sufficient.. i.e. as remote control commands etc. yaml could look like:
cards:
  - type: entity-button
    entity: switch.receiver
    show_name: false
    icon: mdi:power
  - type: entity-button
    entity: script.mute
    show_name: false
    icon: mdi:volume-off

(also 'tap_action:' defaulting to 'action: toggle' could clean up yaml files nicely on entity-buttons)
Likewise, if you've got a glance card and want to hide the icon and show just the name and state i.e. for a series of same sensors that could tighten up the front-end nicely.
card:
  type: glance
  # could also maybe add persistent flag for 'show_icon:' flag here
  columns: 2
    entities:
      - entity: sensor.room_temp
        show_icon: false
      - entity: sensor.room2_temp
        show_icon: false

https://github.com/kuuji/button-card
Allowed for these types of functions and others and since recent upgrades that custom-component has been throwing way too many errors to be livable...
Having both flags default to true would allow users to keep configurations as is...

@jakeapp can you break out the glance card FR into a separate issue?


Delete repeating log without value

What this PR does / why we need it:
Currently MTQ Operator is using GenerateContainers func to evaluate the target pod and figure out if it can release blocked migration, the current log result repeating logging which make it hard to debug.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

NONE

Looks reasonable to me.
/lgtm

/cherry-pick release-v1.1.0

/retest-required

/hold
you need to run make generate

/unhold
@xpivarc no reason to hold if required test are failing

/unhold @xpivarc no reason to hold if required tests are failing

A hold can be handy to stop the retest bot from needlessly retesting a PR that won't pass

/unhold @xpivarc no reason to hold if required tests are failing

Actually, this PR is approved&lgtmed so there would be an automatic retest without it

/lgtm cancel

/cherry-pick release-v1.0.0

/cherrypick release-1.0


Rework guard parsing

Hello,
I use the repository for a project in my company and I want to help a bit to contribute to the amazing work you guys doing.
I figured out that guard only support (implicitly) and operator which accept x numbers of rules and the implementation is very specific to this operator.
If we take graphql-shield (a huge guard module for graphql api in typescript) as a example they implement some others operators :

and
or
not
chain
race

I would like to rework the actual implementation to make a recursive parsing on operators and so be able to parse things like :
#[graphql(guard(
     and(
         or(
             RoleGuard(role = "Role::Admin"),
             RoleGuard(role = "Role::Guest")
         ),
         UserGuard(username = r#""test""#)
     )
))]

You can find explanations about each operators here.
It's my first work on this project and on macros in general so I started look deep into generate_guards() and I understand how the function work. I start working on a first version of the implementation and I will submit a PR in draft soon.

Great, look forward to it! Post guard I think you can delete it, it's not too useful. Attributes parsing for procedural macros is recommended use darling crate, which is very handy. 😃

I don't know darling, I started doing the parsing the same functions that you used. Maybe I can make a v2 with darling after I practice with macros

I don't think implement the not operator seems relevant because we can't return the error defined in the check function of the user.
What do you think about it @sunli829 ?

I don't think implement the not operator seems relevant because we can't return the error defined in the check function of the user.
What do you think about it @sunli829 ?

you're right. 😁

Implemented with https://github.com/async-graphql/async-graphql/pull/296


Port to an easier assembler setup for better assembly!

Hello, Love the Font editor you created, I may ask, Can you port it to a much better setup such as compiling on x64 (64bit) operating systems while maintaining DOS compatibility for generating executables, Flat Assembler G, or NASM alternatively, could do the job nicely.
Again, I appreciate the good work. Thank you.

Can you clarify what issues you are having with FASM?  I have no problems building the DOS executable on my 64-bit system (Windows here, so mileage may vary).  Also, I've never used FASMG, but I expect it should be able to assemble FASM-syntax source for the same target,.. would be strange if it cannot.
Another reason for using FASM is that FASM for DOS works just as well.  So if you already have a DOS environment for the resulting executable, you can also run FASM there and build it from the same source.  Works fine for me in DOSBox/PCem/86box.


Top Up issue back again full force

Describe the bug
User tries to top-up for MYST using crypto, or google.
To Reproduce
Steps to reproduce the behavior:
Go to Wallet
Click Top-up
Select Currency
Select the amount
Click the Start payment button
Send payment to the mentioned address,
Expected behavior
Wallet balance should increase to the amount which was purchased.
Screenshots
Desktop (please complete the following information):
OS: [e.g. Windows 10]
App Version [e.g. 4.1.0]
Additional context
Mysterium Ids who faced this issue and coingate links (when user does not know ID):
0x4b0070b110ef2587cba310d39225cf97264732fc
0x71c2516da944e9c71ec86f35655eb6e823294e64
0x2e998981e507adfe48fb71782054c907e85344d5
0x2e998981e507adfe48fb71782054c907e85344d5
0x65a47d8ab4099ecedf5b3d131d75aa8609a1803f
0x0313bfd1ba12860619403ba637baf05790256759
0x398cd8a90a868c3fd27914bef7f6e05e75392ebd
0x1aa5cb40e606f11b32c8d96e34d50c10aa16f54f
0x7a96372968f4d6aca996477f30930934f7f99feb
0xca846866d22f3b3c99064daa131dd37d031bee0c
0x0313bfd1ba12860619403ba637baf05790256759

https://pay.coingate.com/invoice/996f2ffb-8ebe-41a0-be09-41ac12a53084
#239857
https://pay.coingate.com/es/invoice/7c6bce47-aae2-4730-92df-df381834a80e
#25917964

Same issue here, quite annoying.

2 days and no word on this issue from anyone is insane, I just tried again and lost more money. What an unreliable service.

@CODJointOps Please give me your Mysterium ID. I will approve payment immediately

@CODJointOps Please give me your Mysterium ID. I will approve payment immediately

0xba75a9c7b14b485d0571094577c9307b44197d63


🌟 Adding more beginner friendly projects

🎉 Add more and more projects to this bundle ✨
👍Pull requests are always welcome 🔭

Can I add BMI calculator?

Can I add BMI calculator?

Sure go for it 👍
Make sure you make a BMI-calculator folder and put your python files in it.


Bring back request logging with logback-classic

Several users reported that they have issues with the logback-access implementation.
See #1801, #1812, #1737. It would be great to allow these users to continue to use logback-classic,
while they can't move their appenders to logback-access.

Coverage decreased (-0.1%) to 81.916% when pulling a63adc11aa4241b2fc51bdcb3577a90a781453d6 on logback_classic_request_log into 2b278ef352b32e9468553c364bb240af5d73de7b on release/1.0.x.

Should we update the logging documentation and release notes too?

Yes, thanks. Updates the docs and 1.0.4 release notes.

@arteam we should probably merge this into master too

Should we try and merge release/1.0.x into master?  There seems to be a few commits not present in master

I've cherry-picked this feature to the master branch f4f8258 and 867a101.

You're right, I found this mistake too. I fixed it with a follow-up commit
4c57844. It's strange, that this pull request passed all the tests. The
1.0.4 version should correctly provide the request log discovery.
Am 15.11.2016 18:10 schrieb "Matt Nelson"<EMAIL_ADDRESS>
@mattnelson commented on this pull request.
In dropwizard-request-logging/src/main/resources/META-INF.
services/io.dropwizard.request.logging.RequestLogFactory
https://github.com/dropwizard/dropwizard/pull/1813#pullrequestreview-8649700
:

@@ -1 +1,2 @@
io.dropwizard.request.logging.LogbackAccessRequestLogFactory
+io.dropwizard.request.logging.old.LogbackClassicRequestLogFactory

Should this file be located at /META-INF/services/ instead of
/META-INF.services/?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dropwizard/dropwizard/pull/1813#pullrequestreview-8649700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABo1gP6cxbQ3O9wASSLz6LhzT2zpkmemks5q-ecigaJpZM4Ku2wH
.


Version 0.7.0 is not compatible with mfem-4.5.2

/wrkdirs/usr/ports/science/axom/work/axom-0.7.0/src/axom/sidre/core/MFEMSidreDataCollection.cpp:1508:33: error: no member named 'GetElementIntRule' in 'mfem::QuadratureSpaceBase'
                qf->GetSpace()->GetElementIntRule(0).GetOrder(),
                ~~~~~~~~~~~~~~  ^
1 warning and 1 error generated.

clang-14
FreeBSD 13.1

I'm by no means an MFEM expert but is this as simple as just changing GetElementIntRule to GetIntRule?
The only main difference I'm seeing between v4.4 and v4.5 is that QuadratureSpace is now a child of an abstract QuadratureSpaceBase, which is the type actually now being returned by GetSpace. QuadratureSpace still has GetElementIntRule, but QuadratureSpaceBase does have a GetIntRule implemented which appears to achieve the same result for QuadratureSpace and is further generalized for the newly implemented FaceQuadratureSpace.
I'd like to use MFEM v4.5 with SidreDataCollection so I am interested in seeing a solution to this.


Deneb upgrade feature consideration

Built into Deneb:

EIP 4844

To be built into Deneb:

EIP 4788 (BEACON_ROOT)

EIP: https://eips.ethereum.org/EIPS/eip-4788
CL: eip4788
spec elf: @ralexstokes

EIP 7044 (Fix Voluntary Exit Domain)

EIP:  https://github.com/ethereum/EIPs/pull/7044
CL: https://github.com/ethereum/consensus-specs/pull/3288
spec elf: @hwwhww

EIP 7045 (Increase attestation inclusion range)

EIP: https://github.com/ethereum/EIPs/pull/7045
CL: https://github.com/ethereum/consensus-specs/pull/3360
spec elf: @djrtwo

Under discussion:

EIP 6988
EIP 6475 (consensus-specs: #3336)

refer #3421


Avoid showing NaN when no builds have run

I couldn't run tests locally since I don't have MySQL installed, sorry

Nice

looks good. Thanks @segiddins


Adds transaction hash to completed tx view

Also hides the "View on Mintscan" button if not on cosmoshub
closes #16

Cool, thanks


Refactor console functionality

Console functionality (and console colors) are spread out in the project. Refactoring the code will make it easier to make the project crossplatfom.

Refactored the cpp version of the project.