ES6: No provider for NavController! (MyApp -> NavController)

Short description of the problem:
NavController not injecting in the latest beta.
What behavior are you expecting?
NavController to inject in the constructor method
Steps to reproduce:
ionic start ExampleProject blank --v2
cd ExampleProject
ionic platform add android
ionic platform add ios

In the app/app.js file add the following code:
import {App, Platform, NavController, Alert} from 'ionic-framework/ionic';
import {Inject} from 'angular2/core';
import {HomePage} from './pages/home/home';

@App({
    template: '<ion-nav [root]="rootPage"></ion-nav>',
    config: {} // http://ionicframework.com/docs/v2/api/config/Config/
})
export class MyApp {
    constructor(@Inject(Platform) platform, @Inject(NavController) navController) {
        this.rootPage = HomePage;

        platform.ready().then(() => {

        });
    }
}

Ionic Version: 2.x
Run ionic info from terminal/cmd prompt:
Cordova CLI: 6.0.0
Gulp version:  CLI version 3.9.1
Gulp local:
Ionic Version: 2.0.0-beta.1
Ionic CLI Version: 2.0.0-beta.17
Ionic App Lib Version: 2.0.0-beta.8
ios-deploy version: Not installed
ios-sim version: 5.0.6
OS: Mac OS X El Capitan
Node Version: v0.12.7
Xcode version: Xcode 7.2.1 Build version 7C1002

This is intended behavior, as weird as it seems at first.  Nav here is a child of MyApp, (specifically a ViewChild, because it's in MyApp's template), which means there is no NavController injector available to MyApp.
You can use @ViewChild to access Nav specifically (which extends NavController):
import {App, Platform, NavController, Alert} from 'ionic-framework/ionic';
import {Inject, ViewChild} from 'angular2/core';
import {HomePage} from './pages/home/home';
import {SomeOtherPage} from './pages/someotherpage/someotherpage';

@App({
    template: '<ion-nav [root]="rootPage"></ion-nav>',
    config: {} // http://ionicframework.com/docs/v2/api/config/Config/
})
export class MyApp {
    @ViewChild(Nav) nav;

    constructor(@Inject(Platform) platform) {
        this.rootPage = HomePage;

        platform.ready().then(() => {

        });
    }

    ngAfterViewInit(){
      //this.nav is now defined
      setTimeout(() => {
        this.nav.push(SomeOtherPage);
      }, 2000);
    }
}

I'm not sure if there's a more Javascript-y way to use ViewChild, as I'm pretty sure the above is TypeScript, but all of the starters use the TypeScript compiler so it will work just fine either way (for more discussion on that see: #5493).
Going to close this as it's not a bug, but please feel free to comment if you have any other questions/issues.

This seems kind of sketch.  What if you just throw a more identifiable exception when someone tries to do this in the @App file.

@nraboy If I understand @tlancina correctly, this issue is unrelated to @App, but is instead an issue strictly because the NavController is a child of this particular component. If you had done this in an @Component or @Page you would wind up with the same problem.
I definitely feel that the error reported is vague as it seems to be a problem with available providers rather than the instantiation context. An error indicating the trouble is as a result of attempting to access a ViewChild through injection would be considerably more helpful.
While I think the intuitive approach for attempting to access this component is through injection, the ViewChild decorator seems to be in line with Angular2's design approach and is reasonably well documented by Angular2 here. Currently I believe the most useful thing that could be done to handle these sorts of issues would be to provide better documentation, especially regarding the Nav Controller. Several recent issues posted on the Ionic Forums seem to be related to the subject, which implies a lack of understanding by the community for this feature.

+1 on documentation

I got the error message:

Missing class properties transform.

at @ViewChild(Nav) nav;

I think in app.js, you can just do the following to get a handle to the NavController, where this.app is reference to App
let nav = this.app.getComponent('nav');

Thanks for the feedback everyone, this was not a well documented case, so I've updated the docs on using getComponent to get a reference to a child Nav (vs using @ViewChild) from the root component: http://ionicframework.com/docs/v2/components/#navigating_from_root.
When I originally answered I thought getComponent had been deprecated, but it was only for getting a hold of Menu references, which you now do with MenuController.  I'm not sure what the roadmap is, but I believe there was some discussion of having a MenuController like controller at some point for managing NavControllers that would be available from the root component as well.

@ViewChild(Nav) nav;

Should be somewhere in big bold red letters. Hours of googling finally did some good

Scenario - I have implemented push notifications in ionic2.
On getting notification and clicking on it, i want to redirect to different pages based on the additional data that comes from the server.
I want to move this logic to a separate ts file and and enable push notification by calling init method of the new file created which contains all the code in the root component.
I tried writing a separate component with @Page decorator with no template in it.
But since i need NavController for navigating to different pages i injected NavController but i always get No Provider error for my component. What am i doing wrong, any pointers?
import {Injectable} from 'angular2/core';
import {Push} from 'ionic-native';
import {Page, NavController, NavParams} from 'ionic-angular';
import { ROUTER_DIRECTIVES } from 'angular2/router';
import {DeviceService} from './device/device.service';
import {LunchService} from './lunch/lunch.service';
import {LunchDetail} from './lunch/lunchDetail';
export interface NotificationEventResponse extends PhonegapPluginPush.NotificationEventResponse {
    additionalData: NotificationEventAdditionalData;
}

export interface NotificationEventAdditionalData extends PhonegapPluginPush.NotificationEventAdditionalData {
    additionalData?: any;
}

@Page({
    templateUrl: '',
    providers: [LunchService],
    directives: [ROUTER_DIRECTIVES]
})

//@Injectable()
export class MyPush{
    lunchDetails:any;
    nav: NavController;
    navParams: NavParams;

    constructor(nav:NavController, private _lunchService: LunchService, private _deviceService:DeviceService){
        console.log(this.nav);
        console.log(this._deviceService);
        console.log(this._lunchService);
    }

    push = Push.init({
        android: {
            senderID: "226903902584"
        },
        ios: {
            alert: "true",
            badge: true,
            sound: 'false'
        },
        windows: {}
    });

    enablePush(){
        console.log()
        this.push.on('registration', (data) => {
            console.log(data.registrationId);
            this._deviceService.setDeviceId(data.registrationId);
            this._deviceService.saveDeviceId(data.registrationId)
            .subscribe(
                data => {},
                error => {}
            );
        });

        this.push.on('notification', (data:NotificationEventResponse) => {
            if(data.additionalData.additionalData.type == "lunch"){
                this._lunchService.setCachedData(data.additionalData.additionalData.lunch);
                this.nav.push(LunchDetail,{finalDate:null});
                alert("Hi, Am a lunch push notification");
            } else if (data.additionalData.additionalData.type == "snack"){
                alert("Hi, Am a snack push notification");
            } else{
                alert("This is a generic push");
            }
        });

        this.push.on('error', (e) => {
            console.log(e.message);
        });
    }
}

I made it work using :
this.app._rootNav.setRoot(pageComponent);

Here  is where I found the solution.

Forced that shit to work with getter and Injector
constructor(
    protected injector: Injector
  ) {

...

  get navCtrl(): NavController {
    return this.injector.get(NavController);
  }

Here is solution to get nav controller in any provider
import {Injectable} from '@angular/core';
import {NavController, App} from "ionic-angular/index";
import { LoginPage } from "../../pages/login/login";

@Injectable()
export class ExampleProvider {

    private navCtrl: NavController;

    constructor(private app:App) {
        this.navCtrl = app.getActiveNav();
    }

    //...

    // example usage
    private Logout() {
        //...
        this.navCtrl.setRoot(LoginPage);
        this.navCtrl.popToRoot;
    }
}

I use this approach to detect unauthorized response from server in myAuthHttp which is Http wrapper (this wraper is used in all app instead standard Http and allow to send PUT/GET/POST/DELETE request with authentication token which expires after some time). But better solution will be to raise some 'event' from this provider and  UI should detect it and go to login page - but how to do it?


Added explicit default for ASDF_DATA_DIR environment variable

Fix for #6

@andrewthauer , you're right, absolutely! Plugin asdf alias could use library asdf_data_dir (see https://github.com/asdf-vm/asdf/blob/master/lib/utils.bash#L39. I'll try to use it soon, then resubmit another updated PR.

@andrewthauer , please, have a look at this revised PR: I have switched from a direct reference to environment variable to a call to the asdf's library function asdf_data_dir, as anticipated. Also, in order for all library functions from $ASDF_DIR/lib/utils.bash to be available while sourcing command.bash, I have disabled execute bit on the file. It would be also feasible to have $ASDF_DIR/lib/utils.bash sourced explicitly at the very start of the file. Would you prefer the latter?

@log2 - I confirmed the other day this execute bit flip would be required and also works on my end. Thanks for the change!


Update to React 17

Request to update library to use latest React v17. This will necessitate a few other updated libraries as well, namely react-dom and react-test-renderer. Thanks!
Current version used by react-truncate (see package.json):
"react": "^16.14.0"
Proposed version:
"react": "^17.0.0"

I am currently facing installation errors because of this. Did you get an alternative that can be used in react 17?

I am currently facing installation errors because of this. Did you get an alternative that can be used in react 17?

Our alternative for the time being is using CSS to perform truncation. We have an internal components library our company uses that requires react-truncate, and we are opting not to use our internal library right now because of the React v16 dependency.

the same installation problem here.
@Chase-Dickerson thanks for the suggested alternative solution.

Me too

seems like this library is asleep. Had to use --force on npm install


Creating update(diff) dats for sets containing multiple dats (like VGM)

I am trying to create a diffdat between vgm 20220131 and 20220218. Have 2 dirs (20220131 and 20220218 obviously)
Tried SabreTools.exe ud -dc -sf, SabreTools.exe ud -dc with -out=VGM_DIFF\
Result was almost the complete set, only the 1st dat parsed (amstrad in this case) was ommitted.
Currently running SabreTools.exe ud -di and it seems to be working, but performance is cough shite

With regards to the cascaded diffs:
My understanding is that a good number of the files would be the same between the two input directories, so the outputs will likely be light. Unfortunately, due to how the --skip-first flag works, it anticipates that all of the inputs are the same or similar and literally only skips outputting the first file. So the behavior you're seeing there is accurate to what I'd expect.
I don't fully understand by what you're expecting on the output in this particular case. I'd expect that most of the files are there on output, but only with the files filtered out. I will probably have to reach out to you and test locally to see if the code is doing what I'd expect or not.
With regards to the snarky comment around performance, I'm open to performance improvement PRs :)

update:
it seems that ud -dc doesnt take in account multiple dats (in this case its a few 100 dats per set)
solution now is merge to superdat for the sets to compare, and run a up -di on them. did not try up -dc -sf, might be faster.. but imo ud -dc -sf should be able to run on dirs with multiple dats

As mentioned offline, I could not replicate the issue that was being seen above. Just waiting on a test with the latest WIP and the full massive DAT set that triggered this originally.

tested with wip version from appveyor (02-22).. results are the same.
PM'd datset and result from conversion to superdat before diffing.


Add hash for game

Hi, I added this game to TGDB: http://thegamesdb.net/search/?string=Super+Soukoban&function=Search but the scraper can't find it.
Of course, the game is in No-Intro set: http://datomatic.no-intro.org/?page=show_record&s=49&n=2865

Seeing as there's an issue already open to update all hashes, would it not be best to add your game/link there? ( issue 20 )
If a new issue was opened for every game that's missing from this scraper, poor @sselph would be spending dozens of hours closing down each one individually lol

Done, sorry.

I added the


implement processk8ssecretdeletequueue

func processK8sSecretDeleteQueue() {
	id := "AEGIHK8D"
	log.InfoLn(&id, "processK8sSecretDeleteQueue: <implement:me>")

I am not sure what to do about that.
Does it make sense to delete the associated k8s secret if the registration is deleted; or is it better to let the secret linger.
Since no one is using that secret, it won‘t be a big deal; and resetting the value of that secret will not be of any practical use.
I think it is better to remove that log line and add a comment, telling why the operation is not needed, but this is left as a placeholder for future use if needed.

I think it’s better to keep it there as a noop.
Since deleting k8s secrets is a destructive operation, it’s better be done by the cluster admins in a controlled mannner.
Anyone can create a script to delete stuff.
An alternative approach could be to do a aegis -d workloadName -k
(where -k signifies "delete this from cluster too")
Though is practically identical to
aegis -d workloadName

kubectl delete secretName

For now, I’m closing this as WONTFIX. It’s not worth adding the logic here to save an extra line of kubectl delete.

I will just remove the loglines there to keep the logs clean.


Horizon reports reingest range overlap with newly ingested ledgers without

Horizon 2.4.1
Tried to run reingest:
./horizon --db-url="postgresql://horizon:horizon@<IP_ADDRESS>/horizon?sslmode=disable" --stellar-core-db-url="postgresql://stellar:stellar@<IP_ADDRESS>/stellar?sslmode=disable" --stellar-core-url="http://<IP_ADDRESS>:11626" --network-passphrase="Public Global Stellar Network ; September 2015" --history-archive-urls="http://history.stellar.org/prd/core-live/core_live_001" db reingest range 30681321 30681340 --force
What did you expect to see?
Expected ranges to be ingested.
 Then, after figuring out force flag, I specified wider range and it stuck on ledger 30681343. Number was consistent, so I reduced highest ledger number to 30681340, but now it hangs upon completion. Am I doing anything wrong? Can somebody provide a minimal working example of reingest? There is no other instance of Horizon running.

Tried reingesting without captive core, still no success:
./horizon --db-url="postgresql://horizon:horizon@<IP_ADDRESS>/horizon?sslmode=disable" --stellar-core-db-url="postgresql://stellar:stellar@<IP_ADDRESS>/stellar?sslmode=disable" --stellar-core-url="http://<IP_ADDRESS>:11626" --network-passphrase="Public Global Stellar Network ; September 2015" --history-archive-urls="http://history.stellar.org/prd/core-live/core_live_001" --history-retention-count=0 --enable-captive-core-ingestion=false db reingest range 30681321 30681340 --force
INFO[2021-06-17T09:46:52.322Z] Ingestion system initial state                current_state="reingestHistoryRange(fromLedger=30681321, toLedger=30681340, force=true)" pid=23786 service=ingest
INFO[2021-06-17T09:46:52.322Z] Preparing ledger backend to retrieve range    from=30681321 pid=23786 service=ingest to=30681340
INFO[2021-06-17T09:46:52.413Z] Range ready                                   duration=0.091337033 from=30681321 pid=23786 service=ingest to=30681340
Nothing happens after that. posgtres shows no locks. Is there any configuration in which Horizon will reingest a range and commit DB transaction after reingesting?

There is no other instance of Horizon running.

I tried the same command using Captive-Core in 2.4.1 and it ingested it without a problem. Looking at the blocked queries output from your Postgres I think you actually have other Horizon running. I created this Docker image you can run to see it's working.

Then, after figuring out force flag, I specified wider range and it stuck on ledger 30681343

It's possible if you are not use Captive-Core because then the process will wait indefinitely for ledger to appear in Stellar-Core DB. Without Captive-Core Horizon assumes all the required ledgers are in Stellar-Core DB. Thus, you should use Captive-Core.


Create "or" mechanism for grep module

See the review comments on https://github.com/HubbleStack/Nova/pull/260 for examples. We either need to fix those examples with new misc.py checks, or allow for OR-ing in grep.py.

This issue was moved to hubblestack/hubble-salt#43


Remove flaky test marker for DCOS-41819

High-level description
Remove flaky test marker for DCOS-41819
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-41819

Checklist for all PRs

[X] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[X] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[X] Read the DC/OS contributing guidelines
[X] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot sync

@mesosphere-mergebot label Ready for Review

@mesosphere-mergebot sync

@mesosphere-mergebot sync


iss1

Currently, the optimised spatial filter (OSF) is being applied to all trials at the same time. It should be applied per epoch.

Now the OSF is applied per epoch.

Reopen: The computed weights from the OSF should be displayed in the command window. Also, add a Spatial Filter func. which can be used with custom SF weifgts.

Feature no longer required thanks to new design of visualEEG.


Update camtasia to 3.1.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you, but this is a regression and has conflicts.


Image handling and file handling

I would be great to have a image and file handling methods in firebaseUI for convertion of Actual image or file to BASE64 String and back , with faster and better UI in case the listview or recyclerview has images or file handling.

The Firebase Database is a JSON database. While you can BASE64 encode images and store them in the database, it is not well-suited for this. Until Firebase adds native support for storing images and other file types, it makes little sense to add it to FirebaseUI.

why is it not recommended to use base64 on such database?

Well we designed Firebase for small, quickly changing data. Having 10mb strings in there just doesn't fit into this model and ends up causing a lot of performance issues down the road.
Sadly, we wont be adding any file handling via base64 into FirebaseUI :(


[red-knot] Implement type narrowing for boolean conditionals

Summary
This PR enables red-knot to support type narrowing based on and and or conditionals, including nested combinations and their negation (for elif / else blocks and for not operator). Part of #13694.
In order to address this properly (hopefully 😅), I had to run NarrowingConstraintsBuilder functions recursively. In the first commit I introduced a minor refactor - instead of mutating self.constraints, the new constraints are now returned as function return values. I also modified the constraints map to be optional, preventing unnecessary hashmap allocations.
Thanks @carljm for your support on this :)
The second commit contains the logic and tests for handling boolean ops, with improvements to intersections handling in is_subtype_of .
As I'm still new to Rust and the internals of type checkers, I’d be more than happy to hear any insights or suggestions.
Thank you!

This is fantastic work!
I do have a few comments: feel free to push back if any of my comments don't seem right, it's quite possible I've missed something important!

Thanks for the review! Will address it soon

I think i've addressed all comments, it is ready for another review now :)


fix(TDI-38396): fix null snowflake account

Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)

What is the current behavior? (You can also link to an open issue here)
jdbc:snowflake://null.snowflakecomputing.com/?null returned  as a result of SnowflakeConnectionProperties.getConnectionUrl() when account is null
What is the new behavior?
Specific error message provided
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
https://jira.talendforge.org/browse/TDI-38396

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: failure :x:


Missing NodeJS dependency http-parser-2.7

A NodeJS dependencies was added to the RedHat Base repository for 7.4, therefore it was removed from  EPEL. CentOS wont see those additions until 7.4 is released, which does not have a set release date yet.

Added hot-fix to scale/dockerfiles/framework/scale/env-shim.sh

Resolved in 866d855a2f7c394183303718748dd9124404b4b7


ubluetooth library

I was hoping you would know what firmwares include the ubluetooth library (e.g.import ubluetooth). I’ve read that it is included in recent Spike firmwares, but I can’t import it on the new 51515 controller I own. https://www.eurobricks.com/forum/index.php?%2Fforums%2Ftopic%2F180029-spike-prime-powerup-remote-in-python-noob-needs-help%2F

I believe it is v1.1.x Spike-only.
Running a GitHub search on your repo I believe  answered my question. https://github.com/gpdaniels/spike-prime/search?q=ubluetooth

I believe it is v1.1.x Spike-only.
Running a GitHub search on your repo I believe  answered my question. https://github.com/gpdaniels/spike-prime/search?q=ubluetooth


Need to pull web edition upgrade article and scripts into gsDevKitHome

https://github.com/glassdb/webEditionHome/blob/master/docs/upgrade/upgradeToGemStone3.2.md

Additional feedback on upgrade issues from Johan:

There’s a couple of issues I hit and needed to work around:

after the seaside upgrade script, gemtools login was broken and an error occurred when logging in using topaz. This fixed it:
SystemLoginNotification subscriptions remove: #MetacelloGemStonePlatform.
SystemLoginNotification subscriptions remove: #MetacelloGemStonePlatform.
[1] seems to give the impression you can load GLASS1 using the loadGLASS1.tpz. This is not the case for Gemstone 3.1 at least. I hit a ‘ConfigurationOfGofer’ load error with that and I had to use the GsUpgrader>>upgradeGLASS1 script.

[1] https://github.com/glassdb/webEditionHome/blob/master/docs/upgrade/upgradeToGemStone3.2.md#6-execute-application-load-topaz-file


Bug fix/synchronous replication catchup

Forward port of reduced size of exclusive look during replication sync up.

Jenkins: http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/1828/
All blue!


feat: parse stdtx msg

The StdTx field on the transaction struct varies on it's Msg.Value field. This utility function gives you the possibility to pass any message, and get a properly typed Msg.Value instead.
As it is a PoC, I only implemented it for the Send transaction.

PR too oudated


allow custom API hosts

Currently, pypi.org is hardcoded into the request. Ideally this should be configurable to allow usage with a mirror.

(non maintainer here)
FWIW, that mirror would currently have to serve the (non-standardised) JSON API (info at https://warehouse.pypa.io/api-reference/json.html).
If you had such a repository, the key LOC is https://github.com/astrofrog/pypi-timemachine/blob/33e10adee1745d84904617fc0408797bdd69dab0/pypi_timemachine/core.py#L12.
It would be interesting to make use of modern PEPs to get this project working without the JSON API (PEP-691, and PEP-700, which includes upload time in the simple response).

Coming back a year later to say that I prototyped this in #10. So long as the mirror serves PEP-700 metadata, it will work nicely.


Et7f3/update dependencies

I don't see esy-harfbuzz done https://dev.azure.com/revery-ui/revery/_build/results?buildId=2196&view=logs&jobId=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&taskId=be5e7cb1-b8ca-569b-a02f-a5442c8a3f8a&lineStart=28&lineEnd=29&colStart=1&colEnd=1

On my windows I get
error: build failed with exit code: 1
  build log:
    # esy-build-package: building<EMAIL_ADDRESS>    # esy-build-package: pwd: X:\usr\root\.esy\3_\b\esy_harfbuzz-1.9.1005-05f2d027
    # esy-build-package: running: "./esy/prep.sh"
    C:\Users\root\AppData\Local\Temp\__esy-bash__693853452__1__.sh: line 3: ./esy/prep.sh: No such file or directory
    error: command failed: "./esy/prep.sh" (exited with 127)
    esy-build-package: exiting with errors above...

  building<EMAIL_ADDRESS>esy: exiting due to errors above

see https://github.com/Et7f3/reason-fontkit/blob/Et7f3/update_dependencies/src/config/discover.ml#L41

Maybe ragel is inside a transitive dependencies if it fail again.


Remove helm_docs_use_helm_tool, helm_generate_schema and helm_verify_values options

All repos using the Helm module now have these options enabled, making them useless and adding extra complexity.

/approve
/hold

/unhold


Update Plugin.cs

Update to 1.0.14f1
Changed search string for new JavaScript variable names.  Update file hash

Works great, thanks a lot for this contribution! \o/


Unpin qt version

Description
Because of this bug
https://bugreports.qt.io/browse/QTBUG-88688
Debian based image cannot be used to test Qt 5.15.2 release.
A possible option is to switch to the ubuntu based image. This is done in this PR. But this increase build time.
The possible workaround I to build a custom docker image for this. But then someone needs to maintain it.
The debug process is hidden in  #1935 which is a register of the brute force approach.

Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

I can look into building container for the test, thanks for the note!

I can look into building container for the test, thanks for the note!

I could prepare such script and instruction.
I suggest preparing a separate repository in napari and add a schedule to automatically rebuild every week and push on docker hub.
Until now, my experience is limited to preparing Dockerfile and manual upload to docker hub (for package imagecodecs).

I can look into building container for the test, thanks for the note!

I could prepare such script and instruction.
I suggest preparing a separate repository in napari and add a schedule to automatically rebuild every week and push on docker hub.
Until now, my experience is limited to preparing Dockerfile and manual upload to docker hub (for package imagecodecs).

I created a napari org in docker hub before to release docker version of napari, we can add another repo there, I can send an invite to you, can you share your account in an email to<EMAIL_ADDRESS>

I sent You mail.


GH issue #5872 improve regex for endDelimiter and rollbackEndDelimiter

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

@jasonlyle88 once your setup is fixed could you confirm that this one fixes your issue?

That would be good defensive programming.  It may be worth a tech debt ticket.

@filipelautert @wwillard7800 we need to merge fix for the pro-test with this pr
https://github.com/liquibase/liquibase-pro-tests/pull/1444


OCPBUGS-15380: Fixing flaky tests in osp17.1

On D/S CI we observed two tests flaking. This change is improving stability on those.

/jira refresh

/jira refresh

/jira refresh

/test test-kuryr

/retest

LGTM

/lgtm

/cherry-pick release-4.13


Compute vehicle speed/velocity

Having this:
for frame in video:
    detections = model(frame)
    tracked_objects = tracker.update(detections=detections)
    for object in tracked_objects:
        velocities = object.estimate_velocity

How can I convert the velocities in km/h?
Currently I'm doing the following np.linalg.norm(obj.estimate_velocity,1). However the results does not have sense... The results are being to close to 0.

Hello @pg37013 . Assuming that your Detection instances in your detections list  have the pixel coordinates of its points, then the estimated velocity returned by object.estimate_velocity will be in pixels/frame (so, how many pixels in the horizontal and vertical directions does the tracked point moves between consecutive frames).
To convert it to km/h, you will need some reference length relating pixels to kilometers (for example, if you know the real size of the objects you detected, you can use that). Secondly, you also need the FPS of the video to relate the time between consecutive frames and an hour.
Please, if you need more help or guidance, don't hesitate to ask.

Hello @aguscas
So, suppose that I have velocities = object.estimate_velocity. How can I convert that to km/h?
 How can I make de conversion?

So, you know the width in meters (x_meters m), and also you know it in pixels (x_pixels pixels), and similarly for the height.
width = x_meters m = x_pixels pixels
height = y_meters m = y_pixels pixels
Now, let's relate the velocity units meters/second with pixels/frame :
pixels/frame = (pixels/meters) * (meters/second) * (second/frame) = (pixels/meters) * (1/fps) * (meters/second)
So the velocity can be expressed as
velocity = velocity_in_pixels_per_frame * pixels/frame = velocity_in_pixels_per_frame * (pixels/meters) * (1/fps) * (meters/second)
So the velocity in meters per second is:
velocity_in_meters_per_second =  velocity_in_pixels_per_frame * (pixels/meters) * (1/fps)
So in particular, looking in the horizontal and in the vertical directions:
horizontal_velocity_in_meters_per_second = horizontal_velocity_pixels_per_frame * (x_pixels/x_meters) * (1/fps)
vertical_velocity_in_meters_per_second = vertical_velocity_pixels_per_frame * (y_pixels/y_meters) * (1/fps)

In summary, just compute:
object.estimate_velocity @ np.diag( [(x_pixels/x_meters),  (y_pixels/y_meters)] ) /fps
If this answer is not clear enough, please tell me

So, you know the width in meters (x_meters m), and also you know it in pixels (x_pixels pixels), and similarly for the height.
width = x_meters m = x_pixels pixels
height = y_meters m = y_pixels pixels
Now, let's relate the velocity units meters/second with pixels/frame :
pixels/frame = (pixels/meters) * (meters/second) * (second/frame) = (pixels/meters) * (1/fps) * (meters/second)
So the velocity can be expressed as
velocity = velocity_in_pixels_per_frame * pixels/frame = velocity_in_pixels_per_frame * (pixels/meters) * (1/fps) * (meters/second)
So the velocity in meters per second is:
velocity_in_meters_per_second =  velocity_in_pixels_per_frame * (pixels/meters) * (1/fps)
So in particular, looking in the horizontal and in the vertical directions:
horizontal_velocity_in_meters_per_second = horizontal_velocity_pixels_per_frame * (x_pixels/x_meters) * (1/fps)
vertical_velocity_in_meters_per_second = vertical_velocity_pixels_per_frame * (y_pixels/y_meters) * (1/fps)
In summary, just compute:
object.estimate_velocity @ np.diag( [(x_pixels/x_meters),  (y_pixels/y_meters)] ) /fps
If this answer is not clear enough, please tell me

Will close this issue due to inactivity. Feel free to create another one if this was still unclear


Uses a separate DTLS session for datachannel

It would probably be nicer to use the same DTLS session

Do you bundling data with audio and/or video? The other side would have to be in on that as well.
I guess the real issue is to add support for bundling.

Yes, I guess that's what I meant ;)


Salary Prediction

💥 Proposal
Salary Prediction using machine learning algorithms

Hi @Soumya-Kushwaha ,I think I can work on this because my previous project is somewhat related to this.please assign it to me

Hey @khusheekapoor @Soumya-Kushwaha I would love to work on this issue. I am planning to achieve salary prediction model using Linear regression or decision tree algorithm.
The dataset i will be using is this : https://www.kaggle.com/datasets/thedevastator/jobs-dataset-from-glassdoor
Please assign this issue to me.

@Vethan123 @asthabarwal since we are following the first-come-first-serve policy, we will not be able to assign you this issue. However, you can create another issue and use the same algorithm on a different dataset.

@Soumya-Kushwaha please provide us with the algorithm which you will be using and the dataset link. Thank you

@Soumya-Kushwaha - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


Springless JPA extension

@zhfeng is there any chance to get the required changes to Camel 4?

Yeah, I already deprecated transactionManager in CAMEL-18742 but have not got a chance to remove it in Camel 4. I will create a ticket on Camel to track it.

https://issues.apache.org/jira/browse/CAMEL-19225

I open an upstream PR to remve transactionManager

https://github.com/apache/camel/pull/10954

This should be fixed.


&& and and have different syntax highlighting.

Godot version
3.0+
System information
N/A
Issue description
The syntax highlighting colours for and, or etc. are not the same as for &&, || etc. This might confuse some people.

Steps to reproduce
if (ring_collected && ring_sprite.animation == "Sparkle" and ring_sprite.frame >= 6):

&& and || are symbols, not keywords. (Besides, they have been deprecated in 4.0, so I wouldn't spend too much effort trying to make them look like keywords.)

We could just remove them instead of deprecating. They are very easy to replace.


Use persistence query rather than persistent view for building projections

No need anymore, just reliably delivery to an ActorPath that produces a recoverable stream


Publishing Executables to the registry

There should be a warning message when a user tries to publish executables to the yotta registry. Something like
$ yt publish
Publishing v0.0.1 of My Module...
WARNING: This module is an executables, it is generally a bad idea to publish executables to the
 registry as they are not re-usable. Are you sure you with to publish this executable to the
 registry? (Y/N)

Something, anything, to somehow discourage this behaviour. I would prefer outright rejection of executables from the registry, but it is what it is.

Yeah, there should be: applications can't be depended on by other modules, so the utility of publishing them is limited.


can't access to my ng-model inside of lx-tab

Hi,
I use the last version of lumx and I want to set a form inside of lx-tab but I can't access to my scope.
Here is my code :
 <lx-tabs lx-active-tab="vm.activeTab">
            <lx-tab lx-label="Lorem Ipsum 1">
                <form name='inputForm'>
                    <input type="text" ng-model='commonInput' name='common_input'>
                    <button ng-click="test()">test</button>
                </form>
            </lx-tab>

            <lx-tab lx-label="Lorem Ipsum 2" ng-disabled="vm.tabIsDisabled">

Lorem Ipsum Content 2

            </lx-tab>

            <lx-tab lx-label="Lorem Ipsum 3">

Lorem Ipsum Content 3

            </lx-tab>
        </lx-tabs>

$scope.$watch('commonInput', function(newVal, OldVal) {
                    console.log(newVal, OldVal); //just showed once with the value undefined undefined even if I fill the input
                });

$scope.test = function(){
                console.log($scope.commonInput); //always show undefined even if I fill the input
            };

can anyone help pliz?

It's an Angular good practice to store your model into an object. Don't bind primitive element to angular ng-model.


Unable to runon OSX

I am following the tutorial and when I try run flocker-deploy deployment-node1.yml fig.yml I get the following error.
main function encountered error
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 783, in __bootstrap
self.__bootstrap_inner()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
---  ---
File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/vendor/lib/python2.7/site-packages/twisted/python/threadpool.py", line 196, in _worker
result = context.call(ctx, function, *args, **kwargs)
File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/vendor/lib/python2.7/site-packages/twisted/python

@usmanismail That doesn't look like a complete traceback, could you try again to paste the whole thing please?

Hi.  Thanks for your interest in Flocker.  It looks like the error report (the Python traceback) in the description has been truncated.  Can you provide the complete traceback as well as the contents of the two yml files you're using?  Thanks.

deployment-node1.yml
"version": 1
"nodes":
  "<IP_ADDRESS>": ["web", "redis"]

fig.yml
web:
  image: clusterhq/flask
  links:
   - "redis:redis"
  ports:
   - "80:80"
redis:
  image: dockerfile/redis
  ports:
   - "6379:6379"
  volumes: ["/data"]

Full Log Output
flocker-deploy deployment-node1.yml fig.yml
bash: flocker-reportstate: command not found
main function encountered error
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 783, in __bootstrap
    self.__bootstrap_inner()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
--- <exception caught here> ---
  File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/vendor/lib/python2.7/site-packages/twisted/python/threadpool.py", line 196, in _worker
    result = context.call(ctx, function, *args, **kwargs)
  File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/vendor/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/vendor/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/usr/local/Cellar/flocker-0.3.2/0.3.2/libexec/lib/python2.7/site-packages/flocker/common/_ipc.py", line 90, in get_output
    raise IOError("Bad exit", remote_command, e.returncode, e.output)
exceptions.IOError: ('Bad exit', ['flocker-reportstate'], 127, '')

@usmanismail Thanks for the debug output! What is running on <IP_ADDRESS> and what steps did you take to configure that node for usage as part of a Flocker cluster?

Just docker on a ubuntu server, the tutorial does not mention any install
steps for target servers.
Are there docs for what needs to be setup there.
On Thu, Feb 19, 2015 at 12:04 PM, lukemarsden<EMAIL_ADDRESS>wrote:

@usmanismail https://github.com/usmanismail Thanks for the debug
output! What is running on <IP_ADDRESS> and what steps did you take to
configure that node for usage as part of a Flocker cluster?
—
Reply to this email directly or view it on GitHub
https://github.com/ClusterHQ/flocker/issues/1168#issuecomment-75092010.

Thanks for the feedback on the tutorial!
Please note the right hand side of the tutorial at https://docs.clusterhq.com/en/0.3.2/gettingstarted/ indicates that you should choose to deploy either using Vagrant or AWS. For more detailed install instructions, see here: https://docs.clusterhq.com/en/0.3.2/indepth/installation.html#installing-flocker-node
We are aware of this usability issue with the docs and are actively working to improve them :) See https://clusterhq.atlassian.net/browse/FLOC-1326


Disable web buttons on forms after clicks on request send

Some buttons (eg Login, Run Action) in the current st2web allow for clicking them again sending duplicate requests which might not be desired. If the response time is high, this also leads to a bad UX.
A good way to handle it would be to handle the button click, disable the button, and show a loader/status bar/alert/text somewhere instead. Does require reviewing all buttons to properly assign them error and other help/status texts.
A simpler quick fix should be to just disable (all?) buttons that lead to synchronous responses (page change) while the response is pending.

+1 good idea

I want to work on it.

How long is the re-run disabled for? So if it's a long running workflow for instance, when does the button get re-enabled?


Ignore NoSuchWindowError in workbox-window test

R: @philipwalton
Fixes #2150
Just a hunch that ignoring this error might work around what appears to be a timing problem in Travis CI. (I can't reproduce it locally.)

@philipwalton ping


ColorPicker: add new component based on Coloris

https://github.com/mdbassit/Coloris

I'll go for https://iro.js.org/colorPicker_api.html which is way more flexible and allows us to replace the current picker in PF without breaking changes and add features later (like alpha, hsla, rgba, wheel, swatches etc).


v0.1.4

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/56202
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" ec49150d416cad448248f112253cce01c9fcdc7f
git push origin v0.1.4


successful bootstrap logs tons of misleading error messages

What happened:
I started the broker, and the log is full of error messages that are misleading.
What you expected to happen:
No misleading error messages.
How to reproduce it:
Start the broker, and look at the log.
No runtime label
There were nearly 30 of these messages. It was looking at images that are not service bundles, so they would not be expected to have a runtime label.
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"
time="2018-03-29T20:39:50Z" level=info msg="No runtime label found. Set runtime=1. Will use 'exec' to gather bind credentials"

Version out of bounds
These messages shouldn't be logged at all. They are looking at images that are not service bundles, hence why the version field is empty.
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."
time="2018-03-29T20:39:50Z" level=warning msg="Spec [  ] failed validation for the following reason: [ APB Spec version [] out of bounds 1.0 <= 1.0 ]. It will not be made available."

the information is useful for debugging problems.

Maybe the report could say

out of bound spec versions: 10
valid specs: 5
blah blah blah : 3
total specs processed : 18

I'll get a better example

@jmrodri ^

If there is an error with a spec, the error should come with some info about which spec it was so a human can investigate.
If a spec loads successfully, it's still worth logging that at INFO I think, again with enough info to know which spec.
If an image is determined to not be a service bundle, that should normally be omitted from log output. It's not helpful unless you're investigating a very particular problem getting a bundle to be recognized. I'd log this at DEBUG, and again be real clear about which image it is.
Knowing how many were loaded from each configured registry could be helpful in the summary. That's a quick way to sanity-check "I know there are X bundles in this registry, and I see that X bundles were loaded from it."

@mhrivnak ^

Closing stale issues


pagingViewController.select(index: 1) not working

Hi, I'm poor in english.
I appreciate your library.
I modify my project source from v.1.7.0 to v2.0.1
pagingViewController.select(index: 1) work on v.1.7.0.
but, is not work on v.2.0.1.
So, I experiment some cases.
When I print("index: (index)") in func pagingViewController(_: PagingViewController, viewControllerAt index: Int),
my project print like below.
index: 0
index: 1
index: 1
index: 1
index: 0
index: 1
but, example(Header Example) project print like this.
index: 1
index: 0
index: 2
My project has also three tabs.
Is this cause select(index: 1) not work?
Thanks a lot!

Hi @srgrbth! Can you target the master branch and see if it works there? I’ll release the fixes with a new version soon!

It is solved now! Awesome, thanks! Looking forward to the new release.

@rechsteiner Hi, in master branch, it is work. I also looking forward to new release. Thanks a lot!

Great! The new version was just released now: https://github.com/rechsteiner/Parchment/releases/tag/v2.1.0


modify service name to include launchConfig as well

@alena1108 @ibuildthecloud @cjellick
The background to this change started from https://github.com/rancherio/rancher/issues/1419
Basically, @sangeethah spotted a bug where we weren't able to support even the basic case of a "spread" algorithm via the anti-affinity rule with a sidekick.  Since the anti-affinity rule label gets merged between the 2 launchConfigs and applied to the deployment of the primary and secondary instances, it automatically conflicted with trying to collocate them on the same host.
Adding the launchConfig value into the ${service_name} macro allows for a more granular anti-affinity rule.

LGTM


Update _config.yml

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

test


Find how to help teams integrating Pillarbox in the best way

As a development team we would like to know how we could best help teams integrating Pillarbox.
Acceptance criteria

Teams have been contacted to discover how we could help them in the best possible way.

Tasks

[ ] Discuss options.
[ ] Communicate with the teams.

Continue to submit PRs that might help.
Offer help to the development teams (programmers and designers).

No answer from RSI. @JordanMontel will try again.

Hasn't moved since a long time. Closed. Will reopen another one if needed.


free tier colab notebook for cogvideoX

Runs on T4 GPU for free on Colab GPU

you can add to friendly link instead of the header and add chinese and jap readme to


Problem with Admin permissions in Superset 2.0.0

Dashboards of all users are not shown to anyone except Admin role. Even when Admin role is copied and assigned to user it's impossible to see other users' dashboards.
How to reproduce the bug

As Admin user create any dashboard (no matter if it's published or not) and it will be available in "Dashboards" menu.
Go to List Roles
Select Admin role and in Actions list select Copy role and rename it whatever you want e.g. "copied" (so role has the same permissions as Admin.
Create (if not exist) new user and assign copied role to it.
Login as user with assigned copied role and no dashboards are shown in Dashboards menu.

What is more when you assign Admin role to user from point 4. above dashboards will be shown.
Expected results
Dashboards view should be managed by permission, not role name.
Screenshots
If applicable, add screenshots to help explain your problem.
Admin role:

copied role:

Dashboard view for Admin role (the same user):

Dashboard view for copied role (the same user):

Environment
(please complete the following information):

browser type and version: FF/Chrome (all browsers are affected)
superset version: 2.0.0 and latest (29th of July)
python version: python --version
node.js version: node -v
any feature flags active: no

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset. (both 2.0.0 and latest)
[x] I have checked the issue tracker for the same issue and I haven't found one similar. (I think this is #20638 similar, but solved problem only for published dashboards for others problem still exists.)

Additional context
Add any other context about the problem here.

Update: the same applies for other features (alerts in my case) managed by user with attached Admin permission. When user is co-owner of Alert he is able to modify alert or turn it on or off. But for other users can only list and see configuration but when trying to apply changes gets Forbidden 403 error.

User is using copied Admin role, so has the same permissions as Admin but is not able to do the same things.

I have the same issue while trying to create a chart, i get forbidden.

Can confirm superset init fixes the issue.

superset init doesn't work for me, problem still exists.

Since we're now on 3.1, on the verge of 4.0, we're not supporting 2.x  or prior versions actively. If anyone is experiencing this issue in current versions, please file a new issue with updated context and repro steps. Thank you for understanding :)


Add support for command [JSON.TYPE]

Implement get the key's value type that  [JSON.GET] command returned
Add unit and integration tests

@JyotinderSingh can I accomplish this command for dice. if yes, please assign it to me. thanks.

@JyotinderSingh can I accomplish this command for dice. if yes, please assign it to me. thanks.

Assigned.

@JyotinderSingh can I accomplish this command for dice. if yes, please assign it to me. thanks.

Assigned. Thanks for adding this issue.

Thanks for fixing this!


In which timezone are we going to show user the time?

Ideally we should use the user's time zone, but I'm unsure how that'd work with React hydration, etc. Also we should be properly using <time> elements.


Unable to deploy lambda function to new environment in different region.

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v15.6.0
Amplify CLI Version
4.52.0
What operating system are you using?
Mac
Amplify Categories
function
Amplify Commands
push
Describe the bug
I have created a new environment with a different name in a different AWS region from my current environment.
I am unable to push changes through to this new environment. Specifically, the lambda functions are failing to be deployed successfully.
When I execute amplify push to the new environment, I get the following error in my console:
Reason: Resource handler returned message: "Layer version arn:aws:lambda:ap-southeast-1:XXXXXXX:layer:imagery-mydev:1 does not exist. (Service: Lambda, Status Code: 400, Request ID: XXXXXX, Extended Request ID: null)" (RequestToken: YYYYY HandlerErrorCode: InvalidRequest)
I have a lambda function that is dependent on a lambda layer. I notice that the environment name is hardcoded into the function-cloudformation-template.json file as
 "Layers": [{"Fn::Sub":"arn:aws:lambda:${AWS::Region}:${AWS::AccountId}:layer:imagery-mydev:1"}],
where imagery is the name of the later and mydev is the name of the existing environment and not the new one I am trying to push changes to.
I suspect the hardcoding in the cloudformation template is to blame. Any ideas on alternatives so it picks up the environment automatically rather than hardcoding? I'm a newbie when it comes to cloudformation so not sure what could be used?
I have also noticed that if I checkout my original environment and then choose to add a new function via the CLI with access to the layer, this new function also has a hardcoded environment when referencing the layer.
One option I have considered as a workaround is to change the name of the new environment in the new region to the same as the other environment. It appears the lambda layers are being deployed successfully into the new environment prior to the attempt to create the dependent lambda functions.
Expected behavior
It should successfully push the lamda functions to the new environment in the different region.
Reproduction steps

amplify env add new_env
amplify checkout new_env
amplify push

GraphQL schema(s)
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @greendinosaur, we have merged a feature that will allow you to have your Lambda functions depend on the latest deployed layer version. It should be included in the next release.
The hardcoding of the env name in the layer ARN is currently necessary because Lambda layer versions are immutable, and your new environment may not have the same version number deployed.

Will the new feature default to use ${env} in the cloudformation json file and some kinf of variable to indicate use the latest version of the layer?
I can see this being useful when you want to deploy to a new environment. The deployment can create the new lambda layer with a version number of 1 and then use this in the new lambda function.
Otherwise, the problem I had today will persist and people will have to manually edit the cloudformation file in order to deploy a lambda function requiring a lambda layer to a new environment.

Will the new feature default to use ${env} in the cloudformation json file and some kinf of variable to indicate use the latest version of the layer?

Essentially although the mechanism is different, see https://github.com/aws-amplify/amplify-cli/pull/7375 for more information on the upcoming release.
I recommend using amplify update function for the time being to point your Lambda function to the layer version in your new environment, instead of manually updating the cloudformation.

the issue with using amplify update function is I can only do this once I've deployed the function to the new environment as the cloudformation template has the environment layer hardcoded. Once I've deployed, I can use amplify update function to manage it

Hi @greendinosaur, if you update to the latest version of Amplify CLI and migrate your Lambda layers, you can run amplify update function to point your function to depend on the latest deployed layer version in the relevant environment.
For reference, here is the documentation on the v5 layer migration: https://docs.amplify.aws/cli/migration/lambda-layers-update
Closing this issue. If you run into any issues, please comment below and we can re-open and investigate further.


Exclude python binding tests from Kokoro CI

When these got moved around, some of these exclusions were dropped. These tests don't build on Kokoro+RBE yet.
Since we have big directory exclusions, we could move back to a hybrid path/tag exclusion mechanism. This is a bit cumbersome for excluding every target in a directory. It's nice for fine-grained control if we start to support some of these though.

Sorry - I even patched this in from upstream and tested specifically here but must have been holding it wrong...

No worries. My guess is that you didn't test on Kokoro+RBE


An introduction to Neumorphism UI in android studio

Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
Proposed title of article
An introduction to Neumorphism UI in android studio
Introduction paragraph(s):
This is a design trend concept used to make soft Widgets based on object shadows. It uses highlights and shadows to create UI elements that appear as if they were floating above the surface. In this concept design object seems to extrude from the background.
Neumorphism leans heavily on layers, shadows, and angles to dictate hierarchy and context while embracing a minimal design.
Neumorphism began from design concepts posted on Dribble. One of these designs was posted by Alexander Plyuto.
Neumorphism concepts have led to the development of products like UI kits, tutorials, and libraries to fit in various development platforms such as CSS, Dart(Flutter UI), SwiftUI, etc. In this guide, we'll discuss how to implement Neumorphism UI designs in android studio with hand on examples.
Key takeaways:
What is Neumorphism
Background
How Neumorphism works
Implementating Neumorphic UI in android studio
Usage
References:
Design concept: https://dribbble.com/shots/8557373-Skeuomorph-Mobile-Banking-Dark-Mode
https://github.com/fornewid/neumorphism
https://uxdesign.cc/neumorphism-in-user-interfaces-b47cef3bf3a6
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Thank you for the topic suggestion @Rose-stack , however this is outside of our preferred topic areas. We lean more heavily towards programming-centric topics as opposed to design-centric topics. Please feel free to suggest an alternate topic area to explore.

@molly80 ,this is a programming tutorials using Android studio

@ninjaginja This a programming tutorial using android studio, It employs the concept of Neumorphism to develop an android application.

@ninjaginja Changed the Tittle a little bit to "How to implement Neumorphism UI in the android studio"


How do I use this?

The readme says that to eg write with sudo, I should run
:w suda://%

but when I do this with a file in /usr/local/include on macOS, all I get is
"suda:///usr/local/include/zmq.hpp"
E212: Can't open file for writing: no such file or directory
Press ENTER or type command to continue

Also, for opening a file with sudo via
:e suda://%

all I see is an empty file.

Ha, the plugin was not actually installed (user error).
Maybe you could add a note to the readme that one should disable any autosave functionality, otherwise it'll prompt for password every 5 seconds … apparently sudo timeout does not apply here.


[Improve][Zeta]Optimize the logic of RestHttpGetCommandProcessor#getSeaTunnelServer()

Purpose of this pull request
Optimize the logic of RestHttpGetCommandProcessor#getSeaTunnelServer()
Does this PR introduce any user-facing change?
no
How was this patch tested?
exist tests.
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

cc @liugddx

Please fix the ci error.


add Shan (shn) translation literals

This PR adds translation literals for Shan (shn) language.

Hi!
Thanks a lot for your contribution! Let's see if the styling tests pass and I'll merge :)

Could you change only the language and translation_litterals files? It will make the PR cleaner and more focused on your contribution :)

@clefourrier Hi, I just dropped the last commit that changed other files. Let me know if any further adjustments are needed, Thanks :)


As an NUS student, I want to download the timetable in a jpg form so that I can easily view the timetable on my mobile phone without accessing the website.

Will not be implementing this.


feat: Added model fields for auto deployment configuration

Description
Adds the model fields for auto deployment configuration.
PR fixes following issue(s)
Partially Fixes #30068
Media
Type of change

New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Introduced Auto Deployment capabilities, including options to enable/disable, track last deployment time, and specify branch names for automatic deployment processes.

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>


Is there a proxy method?

Because of my specific network environment, I have to use a proxy to access the internet. I haven't see any method in this project. Can you give me some advice? Thanks!

Hi,
You can set proxy (environment variable) using os module.
import os
os.environ['HTTP_PROXY'] = os.environ['http_proxy'] = 'http://http-connect-proxy:3128/'
os.environ['HTTPS_PROXY'] = os.environ['https_proxy'] = 'http://http-connect-proxy:3128/'
os.environ['NO_PROXY'] = os.environ['no_proxy'] = '<IP_ADDRESS>,localhost,.local'

Then run knockknock functions.


[Feature/Certificate] Restart node when certificate updated

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?
This PR aims at creating a new field in the struct NodeState called CertificateExpireDate, and then automate the Nifi cluster rolling upgrade when the certificate is renewed (handle by the cert manager).
The idea is that we will give the field CertificateExpireDate the value of the current certificate renewal date, during each reconcile we will check if the CertificateExpireDate field has the same value as the current certificate renewal date, if no, we will do a rolling upgrade of the cluster and then assign the new renewal date to each node.
Why?
When the certificate handle by the cert manager was renewed it was necessary to restart the Nifi nodes manually.
Additional context

Checklist

[x] Implementation tested
[x] Error handling code meets the guideline
[x] Logging code meets the guideline
[x] User guide and development docs updated (if needed)
[ ] Append changelog with changes

ToDo

[ ] Test implementation after rebase

Have you tried out the certificate auto-reload feature that NiFi now supports out of the box?
Link
If you set nifi.security.autoreload.enabled in nifi.properties, any changes to the JKS keystore get auto-loaded without a restart.
Admittedly, I've not tried this in a k8s environment though - so might not be as slick as advertised here!

Have you tried out the certificate auto-reload feature that NiFi now supports out of the box? @r65535

I never heard about that so yes I'll try to use the feature before going further with this PR.

Have you tried out the certificate auto-reload feature that NiFi now supports out of the box? @r65535

I never heard about that so yes I'll try to use the feature before going further with this PR.

If cert-manager automatically renews certificates and the configured Secrets get updated, then Kubernetes will automatically update the volumes mounted to the running Pods:
https://kubernetes.io/docs/concepts/configuration/secret/#mounted-secrets-are-updated-automatically
If this is the case, then we might be able to take advantage of that feature of NiFi automatically. There's one condition where Kubernetes will not automatically update Secrets mounted as volumes in Pods when a mount subPath is used. I double checked and made sure nifikop doesn't set this:
https://github.com/konpyutaika/nifikop/blob/88743195e24bbf7d0c02ab3a238dd2dfb01a544b/pkg/resources/nifi/pod.go#L308-L342

After further investigations with the help of @juldrixx we are not sure that the option nifi.security.autoreload.enabled is enough to apply new certificates. If any of you has an exemple that would tell me otherwise your welcome ! @r65535 @michael81877

After further investigations with the help of @juldrixx we are not sure that the option nifi.security.autoreload.enabled is enough to apply new certificates. If any of you has an exemple that would tell me otherwise you're welcome ! @r65535 @michael81877

We chatted about this a little bit afterwards. This auto-reload feature works for the NiFi Jetty web server only. It doesn't apply to any SSLContextServices attached to controller services or processors. We think they could, but that's not how it's currently written.
However, a less disruptive approach to node restarts would be to have the operator watch the Certificates its creating, detect renewals, and restart (e.g. disable/re-enable) all controller services and processors with SSLContextService in deployed NifiDataflow. This is certainly a more complex approach to node restarts, but it's also less disruptive. I'm not necessarily suggesting you take this approach, but the NifiDataflow controller already performs controller service/processor restarts when there are flow changes.

After further investigations with the help of @juldrixx we are not sure that the option nifi.security.autoreload.enabled is enough to apply new certificates. If any of you has an exemple that would tell me otherwise you're welcome ! @r65535 @michael81877

We chatted about this a little bit afterwards. This auto-reload feature works for the NiFi Jetty web server only. It doesn't apply to any SSLContextServices attached to controller services or processors. We think they could, but that's not how it's currently written.
However, a less disruptive approach to node restarts would be to have the operator watch the Certificates its creating, detect renewals, and restart (e.g. disable/re-enable) all controller services and processors with SSLContextService in deployed NifiDataflow. This is certainly a more complex approach to node restarts, but it's also less disruptive. I'm not necessarily suggesting you take this approach, but the NifiDataflow controller already performs controller service/processor restarts when there are flow changes.

The problem is not on the dataflow side but on the pure NiFi side. When the certificate has expired, NiFi does not automatically reload it. So when we try to access the interface, we are blocked because the certificate is no longer valid. We have to force NiFi to reload the new certificate by restarting it. Maybe our way of solving the problem or the problem itself is not the right one.

After further investigations with the help of @juldrixx we are not sure that the option nifi.security.autoreload.enabled is enough to apply new certificates. If any of you has an exemple that would tell me otherwise you're welcome ! @r65535 @michael81877

We chatted about this a little bit afterwards. This auto-reload feature works for the NiFi Jetty web server only. It doesn't apply to any SSLContextServices attached to controller services or processors. We think they could, but that's not how it's currently written.
However, a less disruptive approach to node restarts would be to have the operator watch the Certificates its creating, detect renewals, and restart (e.g. disable/re-enable) all controller services and processors with SSLContextService in deployed NifiDataflow. This is certainly a more complex approach to node restarts, but it's also less disruptive. I'm not necessarily suggesting you take this approach, but the NifiDataflow controller already performs controller service/processor restarts when there are flow changes.

The problem is not on the dataflow side but on the pure NiFi side. When the certificate has expired, NiFi does not automatically reload it. So when we try to access the interface, we are blocked because the certificate is no longer valid. We have to force NiFi to reload the new certificate by restarting it. Maybe our way of solving the problem or the problem itself is not the right one.

If i'm not mistaken, accessing the UI is what the nifi.security.autoreload.enabled feature allows for when certs are rotated. NiFI's Jetty web server uses the FrameworkServerConnectorFactory, which reloads certs from disk, to create connections. It uses Jetty's KeyStoreScanner and TrustStoreScanner to reload certs. As long as they get updated in the pods, then they should get updated if that NiFi property is set.

I have recreated the problem. I set a Duration of 1h and a RenewBefore of 5m, so the certificates expire after 1h. When the certificates have expired, the user interface is not accessible and the operator cannot communicate with NiFi. Whether the nifi.security.autoreload.enabled function is enabled or not makes no difference.
The certificate files in the pods aren't updated either. I will try to understand why.

After further investigations with the help of @juldrixx we are not sure that the option nifi.security.autoreload.enabled is enough to apply new certificates. If any of you has an exemple that would tell me otherwise you're welcome ! @r65535 @michael81877

We chatted about this a little bit afterwards. This auto-reload feature works for the NiFi Jetty web server only. It doesn't apply to any SSLContextServices attached to controller services or processors. We think they could, but that's not how it's currently written.
However, a less disruptive approach to node restarts would be to have the operator watch the Certificates its creating, detect renewals, and restart (e.g. disable/re-enable) all controller services and processors with SSLContextService in deployed NifiDataflow. This is certainly a more complex approach to node restarts, but it's also less disruptive. I'm not necessarily suggesting you take this approach, but the NifiDataflow controller already performs controller service/processor restarts when there are flow changes.

The problem is not on the dataflow side but on the pure NiFi side. When the certificate has expired, NiFi does not automatically reload it. So when we try to access the interface, we are blocked because the certificate is no longer valid. We have to force NiFi to reload the new certificate by restarting it. Maybe our way of solving the problem or the problem itself is not the right one.

If i'm not mistaken, accessing the UI is what the nifi.security.autoreload.enabled feature allows for when certs are rotated. NiFI's Jetty web server uses the FrameworkServerConnectorFactory, which reloads certs from disk, to create connections. It uses Jetty's KeyStoreScanner and TrustStoreScanner to reload certs. As long as they get updated in the pods, then they should get updated if that NiFi property is set.

I dug around trying to figure out why it wasn't working.
When you mount the secret in the pod via a volume, it generates a symlink pyramid where the first symlink truststore.jks points to a second symlink ..data/truststore.jks which points to ..2022_08_31_19_45_44.079808492/truststore.jks. In the nifi.properties, it is told to look at truststore.jks but in reality the scan that tracks the state of the file monitors ..2022_08_31_19_45_44.079808492/truststore.jks. Now when the Certificate is updated, the secret is also updated and then reinjected into the pods but not under ..2022_08_31_19_45_44.079808492/truststore.jks but under another timestamp ..<NEW_TIMESTAMP>/truststore.jks. From the point of view of the symlink we specify in the nifi.properties this update is transparent but not to the scan that monitors the file. For him it has not been updated but deleted and stops monitoring it.
So it seems that the function can't be used unless you know a method to delete this timestamp directory (I didn't find it).

Thank you for spending the time to track this down. That makes sense. It looks like they have a unit test that specifically handles symlink targets. I wonder if it's in a newer version of Jetty?
https://github.com/eclipse/jetty.project/blob/cb127793e5d8b5c5730b964392a9a905ba49191d/tests/test-integration/src/test/java/org/eclipse/jetty/test/KeyStoreScannerTest.java#L208-L238

I've talked to the folks at NiFi and @michael81877, and it doesn't seem like this is expected behavior (link to discussion). I have opened a ticket at NiFi to have this fixed. Now the question is what to do with the PR. We can keep the feature but make it optional to have a system that would work in NiFi versions without the fix, or we drop it and hope that on the NiFi side the fix is done for the next release and that it fixes the problem.

Yeah perhaps we can still pursue node restarts and make that a flag as a part of the SSL config. Then it wouldn't matter what NiFi version the operator is controlling. And then starting from whatever version of NiFi has the fix, the restarts are no longer necessary.

@erdrix @michael81877 ready for another review 😄


Sort Of 2D Array

🚀 Feature
We are given a 2D array of order N X M and a column number K ( 1<=K<=m). Our task is to sort the 2D array according to values in the Column K.
Examples:
Input : If our 2D array is given as (Order 4X4)
39 27 11 42
10 93 91 90
54 78 56 89
24 64 20 65
Sorting it by values in column 3
Output : 39 27 11 42
24 64 20 65
54 78 56 89
10 93 91 90
Have you read the Contributing Guidelines on Pull Requests?
yes
Motivation
Competitive programming
Pitch
Interview questions

@shraddhavp can i be assigned this in Java?

@shraddhavp can i be assigned this in Java?


Is there a need for the local cache?

Windows has its own cache of services and chars, so do we really need the local cache that winrt currently has?
The local cache is not currently populated by DiscoverServices, so subsequent calls for a single service or char will hit windows again, windows will serve from its ble cache, and then we add to local cache.
It seems like the local cache could be eliminated.

@tony-gutierrez You're right! The way it's currently implemented it will only ask the windows ble cache.
I think we could improve this by first checking the windows ble cache with BluetoothCacheMode::Cached and if that fails let windows query the device with BluetoothCacheMode::Uncached.
One thing I'm not sure anymore but IIRC we need to keep a reference to the characteristic to get notifications for it

My understanding is that BluetoothCacheMode::Cached will automatically query the device if there is no cached value. So it shouldn't fail.
Deets here: https://docs.microsoft.com/en-us/uwp/api/windows.devices.bluetooth.bluetoothcachemode?view=winrt-19041

Actually the way it's implement currently is correct, as all services need first to be discovered they should already be in cache once we request one.

Yeah, that is what happens. On second discovery, it misses local cache, and hits windows. On 3rd it would probably hit the local cache. I am just thinking we don't need the local cache. We might need to track chars like you said, but I don't think the local cache check before reading a service is not needed.

There is now expanded information on the cache at the MS url linked above.

Was able to get a good perf improvement in my version by using Cached mode, in addition to not trashing the local cache on disconnect. Have not tested eliminating the local cache and just relying on windows, but seems like a logical next step.

Was able to get a good perf improvement in my version by using Cached mode, in addition to not trashing the local cache on disconnect. Have not tested eliminating the local cache and just relying on windows, but seems like a logical next step.

As far as I can see we're already using BluetoothCacheMode::Cached everywhere. If we can rely on the windows caching then we could definitely remove our custom cache, after all it'll be less code and less of a chance to get out of sync with the device.

Ah, somehow my code started with some Uncached, from a fork I guess. I'll be in touch if I get a chance to remove local cache.

Removing cachedServices seems to cause 2 problems:

You lose the ability to maintain cachedServices during disconnect, which for my use case allows for rapid retries of a failed procedure.
Notify seems to break, it stops announcing characteristic value changes.

Closing this for now.


Backwash cycle data

Monroe would like us to collect data on cycles delimited by backwash dateTimes. At each backwash, start a new cycle, and track:

entranceWaterLevel (height of water above the sand filter)
filteredWaterTurbidity (affluent turbidity)
pC* = -log(turbOut/turbIn) (removal efficiency of the filter)

This also involves modifying the collect form to take a dateTime object for backwash data collection.

@jacuerp we technically already track all of this, and we can calculate pC* from the values we already track. We are trying to get better backwash times by asking about backwash in plantData, so I'm not sure what specific changes this issue is suggesting. Please elaborate!


Update ClinVar

Clinical users find it useful to have the most recent version of ClinVar in the gnomAD browser. Therefore ClinVar data must be routinely downloaded, parsed, and loaded. Instructions are here. This should probably happen at a monthly frequency (?).

Monthly is ideal but if that's too much to ask for, then quarterly would be reasonable.

Related: #984

Updating of ClinVar variants pipeline is fixed thanks to help from the methods team on the VEP troubles.
Leaving this issue open until relevant changes in the code is merged, but the ClinVar variants are now referring to a September 2022 release. I will put in on my schedule to update this at least Quarterly, if not Monthly.

Monthly is ideal but if that's too much to ask for, then quarterly would be reasonable.

Relevant changes are now merged, I will put in on my schedule to update this at least Quarterly, if not Monthly.


Remove inheritance from requests exceptions

Codecov Report

Merging #2178 into v2 will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##               v2    #2178      +/-   ##
==========================================
- Coverage   97.59%   97.59%   -0.01%
==========================================
  Files          56       56
  Lines       10424    10423       -1
==========================================
- Hits        10173    10172       -1
  Misses        251      251

Impacted Files
Coverage Δ

botocore/exceptions.py
99.47% <100.00%> (-0.01%)
:arrow_down:

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 151ddb0...52129e8. Read the comment docs.


fix layout of fig e2

@cshen6 the layout is weird on this figure - can you try to fix it? :)

fixed!
I also replied some comments from SD on the overleaf version, @jovo.


playlist broken

when ever i watch a video with a playlist it only shows the top part of it and none of the videos show up. here a example shot: http://puu.sh/dCRju/ec4faa3c0f.png

Install Stylish addon.
Go to youtube.com
Write new style -> For youtube.com...
Copy this code:
.playlist-videos-list {
    height: 260px !important;
    overflow: auto !important;
}

Name the style. Save.
With this style fix, you can scroll properly on the playlist.

I found the the problem is at line 23932. Removing that line fixes the problem.

@Imold where do i remove that line? im not good at coding at all ._.

@banther7: Are you using the Developer Version of the Userscript? If not I can't help you, but if you are then open the Add-ons Manager and select "User Scripts". Then find "YouTube Center Developer Build" and click on "Options". In the pop up click "Edit this User Script". Now in the window that opens go to "Edit" and select "Jump to line...",  type 23932 ENTER // and click on save.
Then just exit that window, and click OK on the pop up. That should fix it.

This issue only happens in the small player
->the extended one shows the playlist, but it's below the player then and not on it's side

@ReporterX i get this issue: http://puu.sh/fwSb9/4350af3e62.png

@banther7 Which link? Let me try it.

it occurs on any video that i watch that has a playlist

@banther7 Are you using the latest developer build?
I don't experience this issue. There might be some other addons, scripts or adblock filters which break the youtube website. You may try to disable all addons (except Greasemonkey) and all scripts (except YTC Dev Build)

@ReporterX im not even using the greasemonkey script...

@banther7 If you are not using greasemonkey, you are not using YTC.
Or do you mean you are not using the YTC script?
Well in any case what you are experiencing has nothing to do with YTC.

@ReporterX I hope that I am misunderstanding you, but you do realize that there is also an add-on version of YTC that does not require Greasemonkey (or its derivatives)?

@banther7 Try the developer version, you can download it from here: https://github.com/YePpHa/YouTubeCenter/wiki/Developer-Version

@ErdeFB OK. Which version and what version number?
What is your browser and browser version?
Have you tried disabling all addons except YTC addon? Does the issue still exist?

 I did not in any point confirm that I suffer from the same bug. But for the purpose of ruling out possibilities, I am running up-to-date Chromium with the latest YTC developer version (at the time of writing) as an add-on.

@ErdeFB It is to see if the bug you mentioned above is caused by YTC. Anyway I don't experience this bug. It might be caused by other addons and such.

@ReporterX I did not mention any bug above. >_>

@ErdeFB Sorry, mixed up banther7's issues with yours. Must be too tired. XD


[BUG] pyside6 add layout item

Expected Behavior
add a chart with PySide6 Layout
Current Behaviour
self.layout.addItem(self.chart)

TypeError: 'PySide6.QtWidgets.QBoxLayout.addItem' called with wrong argument types:
PySide6.QtWidgets.QBoxLayout.addItem(Chart)
Reproducible Example
import sys

import ccxt
from PySide6.QtCore import QThread, Signal
from PySide6.QtWidgets import QApplication, QMainWindow, QVBoxLayout, QWidget
from lightweight_charts import Chart

class CandleFetcher(QThread):
    candle_received = Signal(dict)

    def __init__(self, exchange, symbol, interval):
        super().__init__()
        self.exchange = exchange
        self.symbol = symbol
        self.interval = interval
        self.ws = ccxt.async_support.Exchange.websocket(self.exchange, f'{symbol}@kline_{interval}')

    async def run(self):
        async with self.ws as response:
            async for data in response:
                if 'k' in data:
                    candle = data['k']
                    self.candle_received.emit(candle)

class _CandlestickChart(QWidget):
    def __init__(self):
        super().__init__()

        self.chart = Chart()
        self.layout = QVBoxLayout(self)
        self.layout.addItem(self.chart)
        #self.chart.show()

    def update_candle_chart(self, candle):
        timestamp = candle['t']
        open_price = float(candle['o'])
        high_price = float(candle['h'])
        low_price = float(candle['l'])
        close_price = float(candle['c'])
        volume = float(candle['v'])

        self.chart.add_candle(timestamp, open_price, high_price, low_price, close_price, volume)

class MainWindow(QMainWindow):
    def __init__(self):
        super().__init__()

        self.candle_chart = _CandlestickChart()
        self.setCentralWidget(self.candle_chart)

        #self.candle_fetcher = CandleFetcher('binance', 'BTC/USDT', '1m')
        #self.candle_fetcher.candle_received.connect(self.candle_chart.update_candle_chart)

        #self.candle_fetcher.start()

if __name__ == "__main__":
    app = QApplication(sys.argv)
    app.setStyle('Fusion')
    #app.setPalette(get_darkModePalette(app))
    window = MainWindow()
    #window = FramelessWindow(titleBarClass=TitleBar)
    window.show()
    app.exec()

Environment
- OS: mac 12.1
- Library:latest

Hey @brusand,
There are a few things wrong with your code:

You need to use the QtChart object rather than the Chart object

QtChart is not an instance which Pyside can interpret; it is based on the QWebEngine, which can be accessed in chart.webview.

If you're still having issues, take a look at the example in the documentation.
Louis

i create this class on my project and it works like a charm
from lightweight_charts import LWC
from PySide6.QtWebEngineWidgets import QWebEngineView
class PySide6Chart(LWC):
    def __init__(self, widget=None, volume_enabled=True):
        try:
            self.webview = QWebEngineView(widget)
        except NameError:
            raise ModuleNotFoundError('QWebEngineView was not found, and must be installed to use QtChart.')

        super().__init__(volume_enabled)

        self.webview.loadFinished.connect(self._on_js_load)
        self.webview.page().setHtml(self._html)

    def run_script(self, script): self.webview.page().runJavaScript(script)

    def _on_js_load(self):
        self.loaded = True
        for func, args, kwargs in self.js_queue:
            getattr(super(), func)(*args, **kwargs)

    def get_webview(self): return self.webview


split close and external url buttons on hover

also add title text to show their actions

Working fine.


Update score-board.js

Add closedNotificationsChallenge

Ahh thank you 😊
I'm busy the next week, will merge & release this afterwards

Ahhh shit sorry totally forgot.
Merging now, release tomorrow.
Thank you again for the PR 😊


Documentation references version 2.0.0, which does not exist

The documentation in README.md incorrectly references version 2.0.0 for the following dependencies:
dependencies {
  implementation("com.openmobilehub.android.storage:plugin-googledrive-gms:2.0.0")
  implementation("com.openmobilehub.android.storage:plugin-googledrive-non-gms:2.0.0")
}

Version 2.0.0 has not been released yet. Please update the documentation to reflect the correct version or remove the reference to 2.0.0 until it is officially released.
Additional Suggestions:
To avoid similar issues in the future, it would be helpful to parameterize the documentation so that the version numbers can be dynamically pulled from the source code during the documentation generation process. This way, any version updates will automatically be reflected in the documentation, reducing the need for manual fixes.
Thanks!

Hi @dzuluaga 👋
We've updated the documentation by removing specific version numbers and replacing them with placeholders:
dependencies {
  implementation("com.openmobilehub.android.storage:plugin-googledrive-gms:<version>")
  implementation("com.openmobilehub.android.storage:plugin-googledrive-non-gms:<version>")
}

We believe this is an appropriate approach, as many opinionated libraries use similar methods (e.g., Retrofit, Lottie).
Finding the current version of the package should not be an issue, as each package includes a version badge at the top of the page.
Let us know if we can close the issue.

Closing since it was fixed with #85

@maciekBudzinski can you elaborate how developers will  know the version to use?

Hi @dzuluaga
Current version of the package is always listed at the top of the Readme with a Maven Central badge close to it, like so:

Do you think it should suffice or should I add additional info somewhere in the docs?

Got it. I think we can add a brief explanation across all repos about where to obtain the <version> from.
It might help to add a note next to the version placeholder (<version>) in the README, explaining that developers should refer to the Maven Central badge for the latest version number. Something like this:
com.openmobilehub.android.storage:core:<version>
(Replace `<version>` with the latest version number shown in the Maven Central badge above)

This could make things clearer for developers.

Ok, I've made all changes in #104


fix/order tracker not match orders with undefined ids

Regenerating PR https://github.com/hummingbot/hummingbot/pull/5079 because the original was merged to the master branch.
Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
PR created to solve the issue https://github.com/hummingbot/hummingbot/issues/5056
Change the fetch order logic in the client order tracker to not look for orders using the exchange order id if it has not been provided as a parameter. Without this change if the exchange order id is not specified it will be None, and the fetch method will match orders in the tracker without exchange order id.
Also in this PR the update logic from a trade update has been changed to never update the exchange order id. That id should be only updated by the order update.
Tests performed by the developer:
Added unit tests for the described scenarios.
Test Summary:

Setup multiple test bots using a single Binance account (same API key)
3 bots running using PMM strategy and the rest are running Avellaneda MM and Liquidity mining strategy
Let the test bots run for almost 24 hours
Regularly check the filled records by running history --verbose and by browsing the TradeFill table
Verify amounts seen in the table that differ from the specified order amount in the strategy and confirmed that these are partial fills

Tips for QA testing:
It is not easy to replicate the scenario running the client. The best approach is to have several client instances running using the a Binance connector with the same user account (it could be for different trading pairs in each instance).
Fixes #5056
This PR comes from https://github.com/CoinAlpha/hummingbot/pull/70

Closing PR and @aarmoa will create a new branch and a new PR.


Investigating inference errors on ZCU104: verifying the correctness of .xmodel judgments in Vitis AI

During the quantization process, I used the following commands: python quantize.py --quant_mode calib --subset_len 1 and python quantize.py --quant_mode test --subset_len 1 --batch_size=1 --deploy to generate DetectMultiBackend_int.xmodel. Then, I converted it into an .xmodel file executable on the DPU, integrating hardware information. However, when deploying the .xmodel model on the ZCU104 development board, numerous errors occurred, making it difficult to determine whether the issue lies with the inference script or the .xmodel itself. I would like to ask if anyone can confirm that the quantization steps were error-free and that the .xmodel file was generated correctly. I have attached a screenshot of the quantization results below.（PS：The version of Vitis-AI is 2.5.）

能不能上传一下量化的代码

你好，这是我参考的github：https://github.com/kevinsu20/Vitis-ai-zcu104-yolov5.git
，里面有我参考的量化代码
On Mon, Dec 2, 2024 at 3:44 PM 9temp @.***> wrote:

能不能上传一下量化的代码
—
Reply to this email directly, view it on GitHub
https://github.com/Xilinx/Vitis-AI/issues/1491#issuecomment-2510794112,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMWJ7IXR37KO2YQGAQDY4RD2DQFWTAVCNFSM6AAAAABRIELJZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQG44TIMJRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>