"No changes needed" after failed deploy

Hi,
I tried to do some changes to my chart earlier today and during first deploy, forgot to quote a numeric env var that caused an error during the upgrade. However, after fixing it the subsequent upgrades were reported by Tiller as "no changes needed" and nothing changed to my Deployment, even though the chart now had more ENV vars and a different image tag than what was running in my cluster.
Logs from Tiller:
2017/04/26 13:52:39 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 13:52:40 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 13:52:40 release_server.go:936: Executing pre-upgrade hooks for shotgun-test
2017/04/26 13:52:40 release_server.go:965: Hooks complete for pre-upgrade shotgun-test
2017/04/26 13:52:40 client.go:410: Looks like there are no changes for Secret "shotgun-test"
2017/04/26 13:52:40 client.go:410: Looks like there are no changes for Service "shotgun-test"
2017/04/26 13:52:40 client.go:398: generating strategic merge patch for *runtime.Unstructured
2017/04/26 13:52:40 client.go:263: error updating the resource "shotgun-test":
	 [pos 917]: json: expect char '"' but got char '3'
2017/04/26 13:52:40 client.go:410: Looks like there are no changes for HorizontalPodAutoscaler "shotgun-test-autoscaler"
2017/04/26 13:52:40 release_server.go:324: warning: Upgrade "shotgun-test" failed: [pos 917]: json: expect char '"' but got char '3'
2017/04/26 13:52:40 storage.go:53: Updating "shotgun-test" (v7) in storage
2017/04/26 13:52:40 storage.go:45: Create release "shotgun-test" (v8) in storage
2017/04/26 13:57:06 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 13:57:07 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 13:57:07 release_server.go:936: Executing pre-upgrade hooks for shotgun-test
2017/04/26 13:57:07 release_server.go:965: Hooks complete for pre-upgrade shotgun-test
2017/04/26 13:57:07 client.go:410: Looks like there are no changes for Secret "shotgun-test"
2017/04/26 13:57:07 client.go:410: Looks like there are no changes for Service "shotgun-test"
2017/04/26 13:57:07 client.go:398: generating strategic merge patch for *runtime.Unstructured
2017/04/26 13:57:07 client.go:410: Looks like there are no changes for HorizontalPodAutoscaler "shotgun-test-autoscaler"
2017/04/26 13:57:07 release_server.go:936: Executing post-upgrade hooks for shotgun-test
2017/04/26 13:57:07 client.go:495: Watching for changes to Job slack-shotgun-test-biakf with timeout of 5m0s
2017/04/26 13:57:07 client.go:510: Add/Modify event for slack-shotgun-test-biakf: ADDED
2017/04/26 13:57:07 client.go:699: slack-shotgun-test-biakf: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
2017/04/26 13:57:10 client.go:510: Add/Modify event for slack-shotgun-test-biakf: MODIFIED
2017/04/26 13:57:10 release_server.go:965: Hooks complete for post-upgrade shotgun-test
2017/04/26 13:57:10 storage.go:53: Updating "shotgun-test" (v8) in storage
2017/04/26 13:57:10 storage.go:45: Create release "shotgun-test" (v9) in storage
2017/04/26 13:57:11 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 13:57:11 client.go:164: Doing get for Secret: "shotgun-test"
2017/04/26 13:57:11 client.go:164: Doing get for Service: "shotgun-test"
2017/04/26 13:57:11 client.go:164: Doing get for Deployment: "shotgun-test"
2017/04/26 13:57:11 client.go:164: Doing get for HorizontalPodAutoscaler: "shotgun-test-autoscaler"
2017/04/26 14:02:10 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:02:11 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:02:11 release_server.go:310: Dry run for shotgun-test
2017/04/26 14:02:12 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:02:12 client.go:164: Doing get for Secret: "shotgun-test"
2017/04/26 14:02:12 client.go:164: Doing get for Service: "shotgun-test"
2017/04/26 14:02:12 client.go:164: Doing get for Deployment: "shotgun-test"
2017/04/26 14:02:12 client.go:164: Doing get for HorizontalPodAutoscaler: "shotgun-test-autoscaler"
2017/04/26 14:04:23 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:04:24 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:04:24 release_server.go:936: Executing pre-upgrade hooks for shotgun-test
2017/04/26 14:04:24 release_server.go:965: Hooks complete for pre-upgrade shotgun-test
2017/04/26 14:04:24 client.go:410: Looks like there are no changes for Secret "shotgun-test"
2017/04/26 14:04:24 client.go:410: Looks like there are no changes for Service "shotgun-test"
2017/04/26 14:04:24 client.go:410: Looks like there are no changes for Deployment "shotgun-test"
2017/04/26 14:04:24 client.go:410: Looks like there are no changes for HorizontalPodAutoscaler "shotgun-test-autoscaler"
2017/04/26 14:04:24 release_server.go:936: Executing post-upgrade hooks for shotgun-test
2017/04/26 14:04:24 client.go:495: Watching for changes to Job slack-shotgun-test-avrsp with timeout of 5m0s
2017/04/26 14:04:24 client.go:510: Add/Modify event for slack-shotgun-test-avrsp: ADDED
2017/04/26 14:04:24 client.go:699: slack-shotgun-test-avrsp: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
2017/04/26 14:04:24 client.go:510: Add/Modify event for slack-shotgun-test-avrsp: MODIFIED
2017/04/26 14:04:24 client.go:699: slack-shotgun-test-avrsp: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
2017/04/26 14:04:27 client.go:510: Add/Modify event for slack-shotgun-test-avrsp: MODIFIED
2017/04/26 14:04:27 release_server.go:965: Hooks complete for post-upgrade shotgun-test
2017/04/26 14:04:27 storage.go:53: Updating "shotgun-test" (v9) in storage
2017/04/26 14:04:27 storage.go:45: Create release "shotgun-test" (v10) in storage
2017/04/26 14:04:28 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:04:28 client.go:164: Doing get for Secret: "shotgun-test"
2017/04/26 14:04:28 client.go:164: Doing get for Service: "shotgun-test"
2017/04/26 14:04:28 client.go:164: Doing get for Deployment: "shotgun-test"
2017/04/26 14:04:28 client.go:164: Doing get for HorizontalPodAutoscaler: "shotgun-test-autoscaler"
2017/04/26 14:07:38 storage.go:133: Getting release history for 'shotgun-test'
2017/04/26 14:07:39 client.go:164: Doing get for Secret: "shotgun-test"
2017/04/26 14:07:39 client.go:164: Doing get for Service: "shotgun-test"
2017/04/26 14:07:39 client.go:164: Doing get for Deployment: "shotgun-test"
2017/04/26 14:07:39 client.go:164: Doing get for HorizontalPodAutoscaler: "shotgun-test-autoscaler"

I finally fixed it by using helm rollback to an earlier version (v5, v8 didnt work) and executing the upgrade command again. I'm no expert, but it seems peculiar that my Deployment seems to be refered to as *runtime.Unstructured ?

hey @bcorijn - what version of helm and tiller are you on?

@michelleN sounds very similar to https://github.com/kubernetes/helm/issues/2341 , I run 2.3.1 tiller and client

Check out the Kubernetes docs on Deployment objects. Deployments are rather particular about what you can upgrade and when.

@michelleN: I am also running 2.3.1 tiller and client
@technosophos: I am familiar with Deployment objects, but adding a new environment variable and changing the container image tag should be two perfectly valid changes.

/remove-lifecycle stale

Closing due to inactivity over the past 2.5 years. Please open a new ticket against Helm 3 if this persists. Thanks!


Add support to new Webview API (Refers #3)

Closes #3

After 4 months in the wild, no issue has been reported, neither in desktop nor web. So, I guess, it's good to go.


Authenticating to Eventhub from python sdk using Workload identity federation for AKS in azure

I am using python sdk for EventHub, currently I am authenticating using connection strings, but I would have to change to some better way.
I have enabled workload identity on my aks cluster, I, therefore want to make use of workload identity deferated credentials to authenticate to EventHub. On EventHub, I have added sender access policies to aad application associated with aks cluster federated credentials.
In the code, I am making use of async defaultcredential to authenticate to EventHub via workload identity.
Importing this :
from azure.identity.aio import DefaultAzureCredential as AsyncDefaultAzureCredential

def get_async_credential(self):
        try:
            credential = AsyncDefaultAzureCredential()
            self._logger.info("Async Credential fetched from Azure Auth successfully")
            return credential
        except Exception as ex:
            self._logger.critical("Exception in fetching async credential from Azure Auth: {}".format(str(ex)))
            raise ex

async def get_writer_client(self):
    try:
        self._logger.info("Creating Eventhub Producer Client")
        self._auth = AzureAuth()
        credential = self._auth.get_async_credential()
        event_hub_producer = EventHubProducerClient(
            credential=credential,
            fully_qualified_namespace=self._event_hub_fully_qualified_namespace,
            eventhub_name=self._event_hub_name,
            buffered_mode=self._event_hub_buffered_mode,
            on_error=self.on_error,
            on_success=self.on_success,
            max_buffer_length=10000)
        self._logger.info("Eventhub Producer Client created successfully")
        return event_hub_producer
    except Exception as e:
        self._logger.exception("Event Hub Producer Client creation error:{} ".format(str(e)))

But I am getting following error :
DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
Visit https://aka.ms/azsdk/python/identity/environmentcredential/troubleshoot to troubleshoot.this issue.
ManagedIdentityCredential: cannot schedule new futures after interpreter shutdown

Please let me know whats wrong am I doing here.

@prashansag62 Thanks for reaching out.
@kashifkhan For the error message "cannot schedule new futures after interpreter shutdown", does this come from eventhub?

@xiangyan99 that message is not one that eventhub raises.

@prashansag62 does this help? https://stackoverflow.com/questions/67419800/error-cannot-schedule-new-futures-after-interpreter-shutdown-while-working-thr

@xiangyan99 @kashifkhan , this message is given by threadpoolexecutor package, I am in my code no where making use of this. However, on digging deep, I can see eventhub sdk making use of threadpool executor library, which might be causing this.
We are making use of workload identity for authenticating to keyvault client in the same code, that is working properly, however when doing same with eventhub it is breaking up :(

@prashansag62 it sounds like something is blocking the client from reaching out. Make sure you follow the steps here in terms of firewall settings etc to make sure there is nothing blocking an outbound connection.

It is resolved now :) Thanks a lot for helping on this. Keeping the main thread alive worked !


ns preview - PLAYGROUND RELATED ONLY - Type AppRoutingModule does not have 'ngModuleDef' property.

Environment
Provide the content of the package.json file in the project:
{
"name": "workspace2",
"nativescript": {
"id": "org.nativescript.workspace2",
"tns-android": {
"version": "6.5.3"
}
},
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e",
"android": "tns run android --no-hmr",
"ios": "tns run ios --no-hmr",
"mobile": "tns run",
"preview": "tns preview",
"ngcc": "ngcc --properties es2015 module main --first-only",
"postinstall": "npm run ngcc"
},
"private": true,
"dependencies": {
"@angular/animations": "~10.0.0",
"@angular/common": "~10.0.0",
"@angular/compiler": "~10.0.0",
"@angular/core": "~10.0.0",
"@angular/forms": "~10.0.0",
"@angular/platform-browser": "~10.0.0",
"@angular/platform-browser-dynamic": "~10.0.0",
"@angular/router": "~10.0.0",
"core-js": "^2.6.9",
"@nativescript/angular": "~10.0.0",
"@nativescript/core": "rc",
"@nativescript/theme": "~2.2.1",
"reflect-metadata": "~0.1.12",
"rxjs": "~6.5.5",
"tslib": "1.10.0",
"zone.js": "~0.10.2"
},
"devDependencies": {
"@angular/cli": "~10.0.0",
"@angular/compiler-cli": "~10.0.0",
"@angular-devkit/build-angular": "~0.1000.2",
"@nativescript/tslint-rules": "~0.0.5",
"@types/jasmine": "~3.5.0",
"@types/jasminewd2": "~2.0.3",
"@types/node": "^12.11.1",
"codelyzer": "^5.1.2",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~4.4.1",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "~2.1.0",
"karma-jasmine": "~3.0.1",
"karma-jasmine-html-reporter": "^1.4.2",
"@nativescript/webpack": "~2.0.0",
"protractor": "~5.4.3",
"ts-node": "~8.3.0",
"tslint": "~6.1.0",
"typescript": "~3.9.0",
"node-sass": "^4.7.1"
}
}
Describe the bug
The error occurs after I run tns preview (or npm run preview) and scan the QR CODE.
Bellow is the error log
Copying template files...
Platform android successfully added. v6.5.3
Preparing project...
File change detected. Starting incremental webpack compilation...
webpack is watching the files…
 Watching for file changes.
Webpack build done!
Project successfully prepared (android)
Start sending initial files for device %H:%M:%S (84033bdf-d3d6-43a3-9857-621b7f558e03).
Successfully sent initial files for device %H:%M:%S (84033bdf-d3d6-43a3-9857-621b7f558e03).
LOG from device %H:%M:%S: com.tns.NativeScriptException: Error calling module function
Error: Type AppRoutingModule does not have 'ngModuleDef' property.
File: (file:///data/data/org.nativescript.preview/files/app/tns_modules/@angular/core/bundles/core.umd.js:1682:12)
StackTrace:
ZoneAwareError(file:///data/data/org.nativescript.preview/files/app/tns_modules/@nativescript/angular/zone-js/dist/zone-nativescript.js:1298:33)
at getNgModuleDef(file:///data/data/org.nativescript.preview/files/app/tns_modules/@angular/core/bundles/core.umd.js:1682:19)
at (file:///data/data/org.nativescript.preview/files/app/tns_modules/@angular/core/bundles/core.umd.js:1513:31)
at noSideEffects(file:///data/data/org.nativescript.preview/files/app/tns_modules/@angular/core/bundles/core.umd.js:1321:19)
at ����setNgModuleScope(file:///data/data/org.nativescript.preview/files/app/tns_modules/@angular/core/bundles/core.umd.js:1512:16)
at (file:///data/data/org.nativescript.preview/files/app/bundle.js:42:131)
at ./app/app-routing.module.tns.ts(file:///data/data/org.nativescript.preview/files/app/bundle.js:42:339)
at webpack_require(file:///data/data/org.nativescript.preview/files/app/runtime.js:817:30)
at fn(file:///data/data/org.nativescript.preview/files/app/runtime.js:121:20)
at ./app/app.module.tns.ts(file:///data/data/org.nativescript.preview/files/app/bundle.js:97:85)
at webpack_require(file:///data/data/org.nativescript.preview/files/app/runtime.js:817:30)
at fn(file:///data/data/org.nativescript.preview/files/app/runtime.js:121:20)
at (file:///data/data/org.nativescript.preview/files/app/bundle.js:211:77)
at ./main.tns.ts(file:///data/data/org.nativescript.preview/files/app/bundle.js:276:30)
at webpack_require(file:///data/data/org.nativescript.preview/files/app/runtime.js:817:30)
at checkDeferredModules(file:///data/data/org.nativescript.preview/files/app/runtime.js:44:23)
at webpackJsonpCallback(file:///data/data/org.nativescript.preview/files/app/runtime.js:31:19)
at (file:///data/data/org.nativescript.preview/files/app/bundle.js:2:57)
at require(:1:266)
Error: Type AppRoutingModule does not have 'ngModuleDef' property.
at com.tns.Runtime.runModule(Native Method)
at com.tns.Runtime.runModule(Runtime.java:674)
at com.tns.Runtime.run(Runtime.java:666)
at com.tns.NativeScriptApplication.onCreate(NativeScriptApplication.java:21)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1025)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5448)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1564)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
To Reproduce
generate a new shared project: ng new -c=@nativescript/schematics workspace --shared
enter the project folder: cd workspace
run any these commands: tns preview, npm run preview (with or without --no-hmr flag)
Expected behavior
Run the project on the real device (preview)

@betosalvador preview needs app store updates which we're working on to bring Angular 10 support to the {N} Preview app. We'll ping back once latest updates have been approved and live on the store.

@NathanWalker
nice man, thanks

@NathanWalker any update about this? Angular is amazing for code sharin between web and native btw :D

Having the same issue and waiting for the update...

@betosalvador preview needs app store updates which we're working on to bring Angular 10 support to the {N} Preview app. We'll ping back once latest updates have been approved and live on the store.
In meantime you can just use nsc debug android --no-hmr or nsc debug ios --no-hmr

@NathanWalker  I just tried nsc debug ios --no-hmr and got an error: Applications for platform iOS can not be built on this OS
So what does this mean?  It's not possible to preview iOS with NativeScript/Angular 10.0 on Windows right now because the {N} Preview app needs to be updated in the app store?  I don't have a mac and don't have an android phone, so I really need to use the ios preview app because my app uses the camera.
It seems like this has been an issue for few months now, what should people do?  Thank you!

@betosalvador preview needs app store updates which we're working on to bring Angular 10 support to the {N} Preview app. We'll ping back once latest updates have been approved and live on the store.
In meantime you can just use nsc debug android --no-hmr or nsc debug ios --no-hmr

Is there any news on this? For working with Preview, does it still make sense to wait for this? Is this proposed fix still in the pipeline?

I am having same issue..
Is this fixed or not yet?

I am facing the same issue. My package.json is as follows:
{
"name": "@nativescript/template-blank-ng",
"main": "main.js",
"displayName": "Blank",
"templateType": "App template",
"version": "7.0.6",
"description": "NativeScript Application",
"author": "NativeScript Team<EMAIL_ADDRESS>"license": "SEE LICENSE IN ",
"publishConfig": {
"access": "public"
},
"keywords": [
"nstudio",
"nativescript",
"mobile",
"angular",
"{N}",
"tns",
"template",
"category-general"
],
"repository": "",
"homepage": "https://github.com/NativeScript/nativescript-app-templates",
"bugs": {
"url": "https://github.com/NativeScript/NativeScript/issues"
},
"dependencies": {
"@angular/animations": "~10.1.0",
"@angular/common": "~10.1.0",
"@angular/compiler": "~10.1.0",
"@angular/core": "~10.1.0",
"@angular/forms": "~10.1.0",
"@angular/platform-browser": "~10.1.0",
"@angular/platform-browser-dynamic": "~10.1.0",
"@angular/router": "~10.1.0",
"@nativescript/angular": "~10.1.0",
"@nativescript/core": "~7.0.0",
"@nativescript/theme": "~3.0.0",
"reflect-metadata": "~0.1.12",
"rxjs": "^6.6.0",
"zone.js": "~0.11.1"
},
"devDependencies": {
"@angular/compiler-cli": "~10.1.0",
"@nativescript/android": "7.0.1",
"@nativescript/webpack": "~3.0.0",
"@ngtools/webpack": "~10.1.0",
"typescript": "~4.0.0"
},
"private": "true",
"readme": "NativeScript Application"
}

Angular 11 is in it's pre release state and there's still no solution for this problem with NS preview app that generates for everyone who starts with NS coding with later Angular version. How long do we have to wait before this is fixed?

Trying out nativescript, met with this error from a fresh angular project - what exactly am i supposed to do to take this development experiece for a testrun?

@BobbyTable Run nsc debug android --no-hmr instead of nsc preview it should work on local connected devices, or AVD

@BobbyTable Run nsc debug android --no-hmr instead of nsc preview it should work on local connected devices, or AVD

No, it is not working for me... any other clue guys?

Hi @NathanWalker , I know it has been asked several times but I'm currently starting a new app development and I would be so grateful to have the Angular 10+ fixed with the Playground app Preview so we can go forward using NativeScript Angular.
Would it be possible for your to give us a timeline on when we could have this issue fixed ?
Kind regards,

Hi @NathanWalker,
as mentioned above this issue has been asked several times, but this bug is reported since August and even after 4 months we don't have solution or atleast some kind of way around. It would be nice if You could atleast provide some status update. Right now I am in bad situation. I need to update to angular 10 because one of our internal package is build on it and I need to use it in nativescript project but I cannot do it because of this bug.
Thank you for reply.

Thats so sad. I need it too

Hi @NathanWalker,
as mentioned above this issue has been asked several times, but this bug is reported since August and even after 4 months we don't have solution or atleast some kind of way around. It would be nice if You could atleast provide some status update. Right now I am in bad situation. I need to update to angular 10 because one of our internal package is build on it and I need to use it in nativescript project but I cannot do it because of this bug.
Thank you for reply.

I have tried so many other options and finally moved to react native as I have not seen any proper attention on the issue.

Same, I had to download an early version of tns in order to make it work. Ended up installing version 6.4.1 and from there I was able to run it,
From: Jordan<EMAIL_ADDRESS>Sent: Friday, December 11, 2020 6:41 PM
To: NativeScript/nativescript-schematics<EMAIL_ADDRESS>Cc: Barroso, Dariel (NBCUniversal<EMAIL_ADDRESS>Manual<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [NativeScript/nativescript-schematics] Error: Type AppRoutingModule does not have 'ngModuleDef' property. (#290)
trying to migrate an existing angular app to new shared code nativescript project so cannot downgrade angular app to use this feature. Is there anyone from telerik who can at least let us know if this will be addressed or if there is another way to accomplish this. People starting new projects can not follow the docs on your site to get this working. That is what I did and ended up here.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/NativeScript/nativescript-schematics/issues/290*issuecomment-743483325__;Iw!!PIZeeW5wscynRQ!9GJwMerbKJqqhKYyg8vIi8vG0TMXgN2mu7Dq3pHMVEnsm9pXM9Jp62QYujJ4tJ83vWw$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AHDBP2QMZPMB63HLLPU6SRTSUKUZPANCNFSM4PR2HLMA__;!!PIZeeW5wscynRQ!9GJwMerbKJqqhKYyg8vIi8vG0TMXgN2mu7Dq3pHMVEnsm9pXM9Jp62QYujJ4J_ODx14$.

Currently trying out this out and have came across this issue. is there a way around it on have to downgrade version is the only solution? Thanks

I've ended up using a skeleton from https://play.nativescript.org/ downloaded then cd to MyprojectFolder and tns preview But then stumble upon this issue https://github.com/NativeScript/playground-feedback/issues/190  and the versioning changes mentioned there works for me.

I got the same error, I am just started new project using ng new --collection=@nativescript/schematics test-project --shared, fix some errors in polyfills.ts and tsconfig.json with the help of stackowerflow and github, but this error is not solved for me. I did nothing but starting new project... now I will think twice before using nativescript for future projects, If I got throubles at the start of my project what will it be in future.

@NathanWalker  Is there any timeline to fix this issue so that I can plan for new development.

Would be awesome if this is still going to be fixed. Keep Nativescript alive pls.

any updates before we reach end of 2020? -same issue here.

Still waiting

I had the same issue i solve it by running the app in my physical device using : ns run android instead of running the app by ns preview
To be able to run this command you need: (android configuration)

Android SDK
Java (jdk 12)
ADB

After installation of this things run ns doctor and you will see a message like this:

hope this will help you

I had the same issue i solve it by running the app in my physical device using : ns run android instead of running the app by ns preview
To be able to run this command you need: (android configuration)

Android SDK
Java (jdk 12)
ADB

After installation of this things run ns doctor and you will see a message like this:

hope this will help you

This doesn't help, what are you on about?

Still no solution of this case.
Time to abandon this sinking ship and move on for a more supported framework.
It's too bad, it had so much potential.

Still no solution of this case.
Time to abandon this sinking ship and move on for a more supported framework.
It's too bad, it had so much potential.

@NathanWalker, please do something about the issue. Many people including me, are still waiting in this thread hoping for your answer as it is still open. Either close this or announce something brother.

@NathanWalker, please do something about the issue. Many people including me, are still waiting in this thread hoping for your answer as it is still open. Either close this or announce something brother.

Hi! I'm just studying Nativescript but found with this already, an error and a support failure.  Will continue just for finishing the course, but I'm thinking this is not good framework for serious developments.
Regards

Hi! I'm just studying Nativescript but found with this already, an error and a support failure.  Will continue just for finishing the course, but I'm thinking this is not good framework for serious developments.
Regards

Yeah ! This issue is still on.

Yeah ! This issue is still on.

I went to install NS and start an app with the tutorial on the website. By default, tns create pulls in Angular 11. It seems like the root cause of this issue is NS just doesn't work with Angular 10 or higher. It's a shame that the tutorial just doesn't work...

I went to install NS and start an app with the tutorial on the website. By default, tns create pulls in Angular 11. It seems like the root cause of this issue is NS just doesn't work with Angular 10 or higher. It's a shame that the tutorial just doesn't work...

We recommend using xplat for code sharing.
It’s better supported, more scalable and will lead you to better results. It’s been available as long as schematics here but supports angular versions faster.
https://nstudio.io/xplat/getting-started
xplat uses Nrwl Nx which provides better tooling all around for effective and massive code sharing.
That being said schematics here have been updated to version 11 when angular 11 was released. These commands have been known to work just fine:
https://gist.github.com/NathanWalker/266f597de1a93314bec9efa6d21c15a2
Angular 11.1.0 was just released last week so it’s possible the instructions on website are pulling in that latest version bump and there’s something. I’ll look at angular 11.1.0 this week.

We recommend using xplat for code sharing.
It’s better supported, more scalable and will lead you to better results. It’s been available as long as schematics here but supports angular versions faster.
https://nstudio.io/xplat/getting-started
xplat uses Nrwl Nx which provides better tooling all around for effective and massive code sharing.
That being said schematics here have been updated to version 11 when angular 11 was released. These commands have been known to work just fine:
https://gist.github.com/NathanWalker/266f597de1a93314bec9efa6d21c15a2
Angular 11.1.0 was just released last week so it’s possible the instructions on website are pulling in that latest version bump and there’s something. I’ll look at angular 11.1.0 this week.

Should be stated the playground is merely for demonstrations only and not recommended as a development environment. You should always take the time to setup a proper development environment locally.
Additionally, I just confirmed that from here, both directions work perfect as is: https://gist.github.com/NathanWalker/266f597de1a93314bec9efa6d21c15a2
When using Option A, if you end up with a project that has "@angular/core": "~10.1.1", - that has nothing to do with NativeScript and everything to do with the globally installed Angular cli you have. npm i -g @angular/cli to ensure the latest angular version project base is generated for you.
Always when bumping dependency version, run: ns clean and then run your project.
You can even use Angular's 11.1.0 released just this past week by bumping all dependencies. For example the following also works perfect:
"scripts": {
    "android": "ns run android",
    "ios": "ns run ios",
    "mobile": "ns run",
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@nativescript/angular": "~11.0.0",
    "@nativescript/core": "~7.1.0",
    "@nativescript/theme": "~3.0.0",
    "reflect-metadata": "~0.1.12",
    "tslib": "^2.1.0",
    "@angular/animations": "~11.1.0",
    "@angular/common": "~11.1.0",
    "@angular/compiler": "~11.1.0",
    "@angular/core": "~11.1.0",
    "@angular/forms": "~11.1.0",
    "@angular/platform-browser": "~11.1.0",
    "@angular/platform-browser-dynamic": "~11.1.0",
    "@angular/router": "~11.1.0",
    "rxjs": "~6.6.0",
    "zone.js": "~0.11.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1101.1",
    "@angular/cli": "~11.1.0",
    "@angular/compiler-cli": "~11.1.0",
    "@nativescript/ios": "7.1.1",
    "@nativescript/schematics": "^11.0.0",
    "@nativescript/tslint-rules": "~0.0.5",
    "@nativescript/webpack": "~3.0.0",
    "@types/jasmine": "~3.5.0",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~4.0.2"
  },

Should be stated the playground is merely for demonstrations only and not recommended as a development environment. You should always take the time to setup a proper development environment locally.
Additionally, I just confirmed that from here, both directions work perfect as is: https://gist.github.com/NathanWalker/266f597de1a93314bec9efa6d21c15a2
When using Option A, if you end up with a project that has "@angular/core": "~10.1.1", - that has nothing to do with NativeScript and everything to do with the globally installed Angular cli you have. npm i -g @angular/cli to ensure the latest angular version project base is generated for you.
Always when bumping dependency version, run: ns clean and then run your project.
You can even use Angular's 11.1.0 released just this past week by bumping all dependencies. For example the following also works perfect:
"scripts": {
    "android": "ns run android",
    "ios": "ns run ios",
    "mobile": "ns run",
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@nativescript/angular": "~11.0.0",
    "@nativescript/core": "~7.1.0",
    "@nativescript/theme": "~3.0.0",
    "reflect-metadata": "~0.1.12",
    "tslib": "^2.1.0",
    "@angular/animations": "~11.1.0",
    "@angular/common": "~11.1.0",
    "@angular/compiler": "~11.1.0",
    "@angular/core": "~11.1.0",
    "@angular/forms": "~11.1.0",
    "@angular/platform-browser": "~11.1.0",
    "@angular/platform-browser-dynamic": "~11.1.0",
    "@angular/router": "~11.1.0",
    "rxjs": "~6.6.0",
    "zone.js": "~0.11.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1101.1",
    "@angular/cli": "~11.1.0",
    "@angular/compiler-cli": "~11.1.0",
    "@nativescript/ios": "7.1.1",
    "@nativescript/schematics": "^11.0.0",
    "@nativescript/tslint-rules": "~0.0.5",
    "@nativescript/webpack": "~3.0.0",
    "@types/jasmine": "~3.5.0",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~4.0.2"
  },

Any ETA on this fix yet

grr

I had the same issue i solve it by running the app in my physical device using : ns run android instead of running the app by ns preview
To be able to run this command you need: (android configuration)

Android SDK
Java (jdk 12)
ADB

After installation of this things run ns doctor and you will see a message like this:

hope this will help you

This doesn't help, what are you on about?

This actually does work ...

Run the advanced setup. In my case linux, so select your OS here
run tns doctor if all green go to next step
Plug in mobile device
run ns run android

Let the magic happen

its been months since this issue is reported can one of the devs just release a statement please ? are you going to fix it or not ? if you are please just state the priority of this fix (low normal high ?). It won't kill you to leave a comment saying we are not supporting nativescript anymore

@NathanWalker I followed steps A) in your instruction but I am receiving this error:
'NativeScript encountered a fatal error: Error: Type AppRoutingModule does not have 'ngModuleDef' property.
Some help?

same

If you have Angular 10.x+, move to Angular 8.x guys. That's the only way
now.
On Mon, 1 Mar, 2021, 11:12 pm martijnmichel<EMAIL_ADDRESS>wrote:

same
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/nativescript-schematics/issues/290#issuecomment-788137905,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANF2TZ7JOBA5EUM7ZCKHMPLTBPGWXANCNFSM4PR2HLMA
.

@hartbrkr3399  Thanks for the reply
Kind regards

@hartbrkr3399  Thanks for the reply
Kind regards

After moving, were you able to dodge that error? Because I just said that in a guess lol.

Nope not yet I have other projects to work on the mobile development I'm trying is more of a side thing (also I tried it out only recently to see if its a good fit for our tech stack and as good as it is (perfect) but without angular 10 support its just  a matter of time before angular goes to far and you're stuck with a specific version of nativescript without any new support or tech. if we get a new angular version before we get the required support I'd suggest taking a look at react native for mobile dev)
not hating or bad mouthing nativescript I'm a huge fan boy but reality is work needs to get done and if the tools are insufficient you're setting yourself up for struggle in the long run or unwanted limitations.

Nope not yet I have other projects to work on the mobile development I'm trying is more of a side thing (also I tried it out only recently to see if its a good fit for our tech stack and as good as it is (perfect) but without angular 10 support its just a matter of time before angular goes to far and you're stuck with a specific version of nativescript without any new support or tech. if we get a new angular version before we get the required support I'd suggest taking a look at react native for mobile dev)
not hating or bad mouthing nativescript I'm a huge fan boy but reality is work needs to get done and if the tools are insufficient you're setting yourself up for struggle in the long run or unwanted limitations.

@the-fapeling I understand the sentiment and would like this issue to be fixed too. But this is not a complete blocker from using Nativescript with angular 10. As @abdes-zakari mentioned, you can totally run it fine with angular 10 using the android sdk and running it natively on your device.


mount /tmp

https://keboola.zendesk.com/agent/tickets/8310
https://github.com/keboola/db-writer-mssql/issues/21

hotovo?

in 66713cbef5517bcd148cf8f5f4f7601f54f0b869


bug: j.clients.tfchain.kds.blockchain_info_get()

I put network type on 'TEST' thats maybe the issue
should use an enumerator there

Fixed: https://github.com/threefoldtech/jumpscaleX/commit/db7263cfec904e152aa1402f3bd3ee9c6b047f03


UNDERTOW-1023 Respond 400 Bad Request and log at DEBUG level when exc…

…eeding max-cookies limit

I've just pushed the update of this PR.

Linux Build 314 outcome was FAILURE using a merge of b1257b4c99ff793adaaa26d52c17b4f10eb91cfa
Summary: Execution timeout (new); tests passed: 2756, ignored: 478 Build time: 01:00:07

I updated this PR again because it was conflicted with the latest change. Are there any additional changes you'd like me to make on this PR? Of course, totally fine with me if you prefer to modify it yourself.

As per your review, I made the following changes on this PR:

Invoke Cookies.parseRequestCookies() directly instead of calling it via httpServerExchange.getRequestCookies()
(I think this approach does not create cookie map. If this approach is still not a good apprpoach, please point it out.)
Include the same checking in Http2ReceiveListener.handleRequests() for HTTP/2 connector, too.

In addition to the above, I made the following changes:

Add UndertowOptions.DEFAULT_MAX_COOKIES for the default value

Move the try-catch block of Connectors.setExchangeRequestPath() to after calling
dataChannel.getResponseChannel().setCompletionListener() in Http2ReceiveListener.handleRequests() because the following ERROR happened when I tested exceeding max-cookies and max-parameters.

ERROR [io.undertow] (default I/O-24) UT005085: Connection io.undertow.server.protocol.http2.Http2ServerConnection for exchange HttpServerExchange{ ...(snip)... } was not closed cleanly, forcibly closing connection

I'm closing this PR at this moment. I'll resolving a conflict, then I'll send a new PR to the master branch instead.


operationName configuration

Thanks for a great library. I've been looking for something exactly like this to replace codegen in watch mode.
Is it possible to set the operationName for a given operation? I'm not seeing the option exposed poking around the generated comment. Workaround for now is to manually edit the returned graphql document

What would be an ergonomic API to do this? We can try overloads for query, mutation and subscription and if they cause problems with type inference (probably not but just in case) we can try namedQuery, namedMutation, namedSubscription
Also, mind if I ask - is this mainly to improve debugging, or are there other uses of the name?

@spion yes the idea is primarily helpful for debugging and monitoring. I use apollo studio to be able to break down server performance by operation and it uses operationName to identify operations in the UI. I'm not sure what happens if no operationName is provided, but I would imagine it becomes harder to know where the query originated in the app.

What do you think about this for an API?

type QueryOptions = {
  operationName?: string;
}

function query<Sel extends Selection<$RootTypes.query>>(
  selectFn: (q: $RootTypes.query) => [...Sel],
  options?: QueryOptions;
) {
}

I like that its guaranteed to avoid issues with type inference.
I was thinking something that looks more like GraphQL syntax
query('MyQueryName', q => [
  q.field({arg: 1}, f => [
    f.id,
    f.name
  ])
]);

i.e. if the first argument is a string, its treated as an operation name.
I think we should give that one a try first as it mimics GraphQL more closely - if there are issues, the options argument seems like a rock-solid (as well as more extensible - although not sure if that's needed?) alternative.

i agree your syntax is more graphql like. I also cannot foresee any other options we'd need to add. Would be nice to support that syntax as a function overload vs totally removing the current API if no operation name is needed

Overloads seem to be working just fine :grinning:


refactor: rename caip specifiers

Description

Replace { CAIP10, CAIP19, CAIP2 } types with { AccountId, AssetId, ChainId }
Depends on lib PR #549.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #549
Risk

Being only a type name change, this PR carries low risk.
Testing

Screenshots (if applicable)

@pastaghost does this actually close https://github.com/shapeshift/web/issues/1573, not https://github.com/shapeshift/lib/issues/549?


first acp cycle for new react learning journal. ran create-react-app …

…and created development branch.

Also forgot to mention that the 'development' branch acts as a secondary 'master' branch and is the only branch that should ever be pulled into the 'master' branch.


fix(resource-service): Force checkout event if unstaged changes are present

Signed-off-by: odubajDT<EMAIL_ADDRESS>

@agrimmer does it make sense what data we lose? The truth is in the upstream. If there was an op that didn't succeed, it should be re-executed in a clean state, which is what this PR is aiming to introduce.

With this change, we could lose data that a Keptn service (e.g. dynatrace-service) tried to write.
Do we have appropriate re-try logic in place?

In the current state, it is basically not possible to test StageAndCommitAll function directly, so we tested the scenario, we are aiming for, which is: create changes + reseting the git + checking if the changes are stashed.
The reason why it is not possible to create a direct test is, that in function StageAndCommitAll we need to mock the commitAll function. In this case, both functions are part of the same structure/interface, so it is not possible to mock only one of them. Either both (which is useless for testing) of none (in this case, commitAll is never able to return an error). If we want to test it, we need a big refactoring, which is not in plan in the current state.
From this reason we used only testing the ReseHard function itself, as it is quite clear, that when commitAll returns an error, ResetHArd is executed and should take care of the cleanup. This should cover testing the changes we made in an indirect way.


iconv(): Wrong charset, conversion from UTF7-IMAP' to UTF-8//IGNORE' is not allowed

Describe the bug
when calling getMessages()
I get this error
-  ErrorException  : iconv(): Wrong charset, conversion from UTF7-IMAP' to UTF-8//IGNORE' is not allowed
PHP
7.2.25
OS
centos-release-7-7.1908.0.el7.centos.x86_64

hi, i have some sort of same problem with some of the email.
error: iconv(): Wrong charset, conversion from default' to UTF-8//IGNORE' is not allowed
PHP 7.4.12 (mbstring and xml is installed and actived)
OS CentOS Linux release 8.2.2004
Laravel 5.7


style(frontend): changes footer copyright text

Motivation
Instead of the text © 2024 Developed with ❤ at DFINITY the text Incubated with ❤ by DFINITY Foundation © 2024 should be displayed as copyright text in the footer.
Changes

changes copyright text

Tests
before:
Desktop:

Tablet:

Mobile:

after:
Desktop:

Tablet:

Mobile:

I am not sure I really like the mobile version: was it required like this? maybe more space between the icon and the sentence? or even putting "by Dfinity Foundation" in another row together with the year

@AntonioVentilii Sry, you are right. The text needs to be centered. I just fixed it.
fyi: In the next PR the icon will be made a litte bit smaller.

@BonomoAlessandro may you please update the screenshots in the description?


Published migrations are not being rollbacked on test teardown (beforeApplicationDestroyed)

Testbench Version: 7.7
Laravel Version: 9.*
PHP Version: 8.1
Database Driver & Version: sqlite

Description:
I am facing a strange issue like testbench-dusk cannot load testbench-dusk\laravel\database\migrations during rollback
I have used testbench-core for some tests, and it is working flawlessly, using memory sqlite
So I continued to set up my visual tests but this time I should use a file sqlite db
I used the following setup for migrations

    protected function defineDatabaseMigrations(): void
    {
        $this->loadLaravelMigrations(['--force'=>true]); // force flag,  creates the database without any other scripts usage

        $this->withoutMockingConsoleOutput();
        $this->artisan(VendorPublishCommand::class, ['--tag' => 'my-package-config']);
        // $this->loadMigrationsFrom(database_path('migrations'));
        $this->artisan(InstallCommand::class); // A command that publish third party migrations on database dir (during test in orchestra-dusk\database\migrations\

        $this->loadMigrationsFrom(__DIR__ . '/Database/Migrations'); // load test migrations
    }

The result of my test db migrations was

migration name
scope
path
batch

users_2014
laravel
testbench-dusk\laravel\migrations
1

passwords_2014
laravel
testbench-dusk\laravel\migrations
1

fortify_migrations_2014
published
testbench-dusk\laravel\database\migrations
2

third_package_migrations
published
testbench-dusk\laravel\database\migrations
2

third_no2_package_migrations
published
testbench-dusk\laravel\database\migrations
2

test_migrations
test
myTestsDire\Database\Migrations
3

test_migrations
test
myTestsDire\Database\Migrations
3

As I was repeating my tests again and again, I found out that the rollback didn't work as expected as it was trying to find the published migration files but the main database\migrations path (batch No2) wasn't loaded on Migrator
So it was starting rollback, but every time was stopping silently on the second batch as it couldn't resolve them
As a result I had some errors of double seeding etc
Steps To Reproduce:

load laravel migrations
publish some migrations during test
load some test migrations
check your db.sqlite file after test. It will have stop rollback on the pulished migrations

Workaround
Add this line forcing migrator to load the path
 $this->loadMigrationsFrom(database_path('migrations'));

Can you submit a failing tests for this

You may find one here
https://github.com/orchestral/testbench-dusk/compare/7.x...GeoSot:testbench-dusk:test-default-databases
But at least in that case it ignores to migrate it to. In my case for some reason, it ignores it only during rollback


Provided failing tests for CurrencyFormat helper

referencing https://github.com/zendframework/zf2/pull/2318
We're on icu version 51.2 and still have the problem of wrong formatting for some locale and currency code combination
Please run this test and verify the results

Question: is this a problem specifically in ZF2, or is it upstream in libicu? If the latter, I'm not sure we can do anything about this...

Sorry for the late response. This is not ZF2 specific problem. It's in fact the libicu version acting weird here.
This issue can be closed!


rsync: new package added

Hi, there.
Unfortunately, lsyncd doesn't work without --delete-missing-args properly. Argument is supported in rsync started with 3.1.0. Would be nice to have the version newer than we have in base EL6/EL7 repository. I've tested this spec only in CentOS 6 and CentOS 7 x86_64.

Looks good. I use your spec and spec from Fedora 22 and made this spec with some additional patches and init script for CentOS6.


Add tests for mobject.get_family()

In view of ongoing discussion in #373 , it seems like Mobject.get_family() will be refactored (or eliminated) soon. So I wanted to create a few tests real quick before any more development on that front continues. Quick and easy to review.

All good points, thanks @Aathish04 . Just pushed changes.

Should I merge now or wait until the tests are fixed?

If you don't mind, let's wait a little bit for the fix, and the refactor.

Sounds good

@Aathish04 I had to change VMobject back to Circle because tests didn't pass with a plain VMobject (see comment in the file). I'm merging this as it has two approvals and all tests pass.


 I have tried the following but it shows a mangled form of the STL, probably because it is missing the STL triangle references. What would be the right way of doing this?
import ipyvolume as ipv
# for loading STL:
# pip install numpy-stl
from stl import mesh

slideRMesh = mesh.Mesh.from_file('ObjectClasses/STLs/Slide_rack_text.stl')

ipv.figure()
# we draw the tetrahedron
mesh = ipv.plot_surface(slideRMesh.x, slideRMesh.y, slideRMesh.z, color='orange')
# and set the axes square to the outer bounds:
ipv.xyzlim(np.min(find_mins_maxs(slideRMesh)), np.max(find_mins_maxs(slideRMesh)))
ipv.show()
`

When I try to do this with mplot3D, I can do the following, but the display is a lot worse and non-interactive, so I was hoping to do the same using ipyvolume.
`
# Create a new plot
figure = plt.figure()
axes = mplot3d.Axes3D(figure)

# add the vectors to the plot
axes.add_collection3d(mplot3d.art3d.Poly3DCollection(slideRMesh.vectors))

# Auto scale to the mesh size
scale = slideRMesh.points.flatten()
axes.auto_scale_xyz(scale, scale, scale)
plt.show()

Any ideas how I can use the power of ipyvolume for this? Thanks in advance!

Try something like this, you flatten all the x/y/z so it's all the first vertices of each triangle, followed by all the second vertices for each triangle, then the third vertices for each triangle.  Then each triangle is the nth element from each part of the vertex list:
import ipyvolume as ipv
from stl import mesh

my_mesh = mesh.Mesh.from_file('some_file.stl')

fig = ipv.figure()
n = len(my_mesh.v0)
ipv.plot_trisurf(x=my_mesh.x.ravel(order='F'),
                 y=my_mesh.y.ravel(order='F'),
                 z=my_mesh.z.ravel(order='F'),
                 triangles=np.arange(3*n).reshape(n,3,order='F'),
                 color="orange")
ipv.show()


Mac support

The plugin is great but the lack of support for Xamarin.Mac forces me to remove some function in my app.

Not sure what this PR is, please open an issue.


fix(catch): Update Catch2 to the latest version (#432)

Fixes #432. Because I did not know of a smarter alternative, I had to replace all catch.hpp by hand. Furthermore, I only tested the changes on hello-world and on my M1 Mac.

Yes, this is what's necessary to update Catch. Thanks.
I need to fix our CI before I can test this and merge. The Configlet linter that checks the track config files is showing we have some errors, which breaks our CI entirely. And that check is a prerequisite for executing the actual tests. It was setup this way assuming that the Configlet linter check wouldn't change and break existing code.

After a quick google search, I found an easy way to update Catch2:
find . -name catch.hpp |\
while read filename
do
     cp /path/to/new_catch.hpp $filename
done

Any updates?

@pr1metine Thanks for this work and sorry for the slow responses!
@patricksjackson It seems that the CI now works (although configlet fails), so maybe I can merge this using my admin rights?

Better late than never haha

Done. Thanks!


Environment Variables

Description
New samples to demonstrate new App Lifecycle Environment Variables feature.
Target Release
1.1 Preview3/GA
Checklist

[ ] Samples build and run using the Visual Studio versions listed in the Windows development docs.
[ ] Samples build and run on all supported platforms (x64, x86, ARM64) and configurations (Debug, Release).
[ ] Samples set the minimum supported OS version to Windows 10 version 1809.
[ ] Samples build clean with no warnings or errors.
[ ] [For new samples]: Samples have completed the sample guidelines checklist and follow standardization/naming guidelines.
[ ] If I am onboarding a new feature, then I must have correctly setup a new CI pipeline for my feature with the correct triggers and path filters laid out in the "Onboarding Samples CI Pipeline for new feature" section in samples-guidelines.md.
[ ] I have commented on my PR /azp run SamplesCI-<FeatureName> to have the CI build run on my branch for each of my FeatureName my PR is modifying. This must be done on the latest commit on the PR before merging to ensure the build is up to date and accurate. Warning: the PR will not block automatically if this is not run due to '/azp run' limitation on triggering more than 10 pipelines.

Please give this (and future check-ins a more descriptive name.
"Initial check-in" tells us nothing about the purpose of the change.
I know you have more details in the description but that's not visible without opening the PR. When looking at lists of open items/PRs/etc. it's much more helpful to give things a meaningful and descriptive name.

/azp run SamplesCI-AppLifecycle

/azp run SamplesCI-AppLifecycle


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/74315

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/74316

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115274

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117524


Replace deprecated tox.ini option

Description
I have fixed a broken option in the tox.ini file. This option was replaced in 2020, deprecated, and eventually removed in tox 4. The correct option already appears elsewhere in this tox.ini file.
https://tox.wiki/en/3.18.1/changelog.html#v3-18-0-2020-07-23
This fix is necessary to run tox -e doc per the README.md instructions on tox version 4.
Issue reference
Skipped due to minor nature of issue; no actual code changes.
Here was the build error from tox -e doc:
[...]
doc: commands[0]> sphinx-apidoc -E -o docs/actor dapr/actor
doc: commands[1]> sphinx-apidoc -E -o docs/clients dapr/clients
doc: commands[2]> sphinx-apidoc -E -o docs/proto dapr/proto
doc: commands[3]> sphinx-apidoc -E -o docs/serializers dapr/serializers
doc: commands[4]> make html -C docs
doc: failed with make is not allowed, use allowlist_externals to allow it
  doc: FAIL code 1 (25.60 seconds)
  evaluation failed :( (25.65 seconds)

Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

I'm assuming all of the above are n/a -- there are no meaningful changes to the codebase itself.

Thanks for your contribution @emsearcy!


New version: Unity.Unity.6000.WindowsIL2CPP version 6000.0.13f1

Created by 🥟 Dumplings in workflow run #7048.

Log
Updated: 6000.0.12f1 → 6000.0.13f1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000 version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165881
Handling Unity.Unity.6000.Android...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.Android version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165883
Handling Unity.Unity.6000.iOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.iOS version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165884
Handling Unity.Unity.6000.tvOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.tvOS version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165885
Handling Unity.Unity.6000.visionOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.visionOS version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165886
Handling Unity.Unity.6000.LinuxIL2CPP...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.LinuxIL2CPP version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165887
Handling Unity.Unity.6000.LinuxMono...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.LinuxMono version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165888
Handling Unity.Unity.6000.LinuxServer...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.LinuxServer version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165889
Handling Unity.Unity.6000.MacMono...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.MacMono version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165890
Handling Unity.Unity.6000.MacServer...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.MacServer version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165891
Handling Unity.Unity.6000.UWP...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.UWP version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165892
Handling Unity.Unity.6000.WebGL...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.WebGL version 6000.0.13f1 - https://github.com/microsoft/winget-pkgs/pull/165893
Handling Unity.Unity.6000.WindowsIL2CPP...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Depends on: https://github.com/microsoft/winget-pkgs/pull/165881

/azp run


Fix handling of errors in Darwin framework OTA delegate bridge.

This allows the framework consumer to return an error that will be sent as an error status to the OTA provider client.
Fixes https://github.com/project-chip/connectedhomeip/issues/20653
Problem
The callbacks have an NSError * argument that is not used in a sane way.
Change overview

Stop passing in a non-nil NSError from darwin-framework-tool.
Convert non-nil NSError into an error status response to the server

Testing

Modified handleQueryImageForNodeID in darwin-framework-tool to pass in a non-null error in the "no OTA image" case allocated like so:    auto * error = [[NSError alloc] initWithDomain:MTRInteractionErrorDomain
                                              code:MTRInteractionErrorCodeFailsafeRequired
                                          userInfo:nil];

Ran the ota-requestor app.
Ran darwin-framework-tool in interactive mode, commissioned the ota-requestor app as node id 17, and ran:otasoftwareupdaterequestor announce-ota-provider ${FRAMEWORK_TOOL_NODE_ID} 0xfff1 0 0 17 0

Observed that the ota-requestor app logged:CHIP: [SWU] Received QueryImage failure response: IM Error 0x000005CA: General error: 0xca (FAILSAFE_REQUIRED)

accepted for 1.0: platform change

Fast-tracking: has platform owner review (though not recognized by pullapprove), and one other company review.


[mieb] 'BlipForImageTextRetrieval' object has no attribute 'get_image_features'

ERROR:mteb.evaluation.MTEB:Error while evaluating CVBenchCount: 'BlipForImageTextRetrieval' object has no attribute 'get_image_features'
Traceback (most recent call last):
  File "/data/niklas/mieb/mteb/scripts/run_mieb.py", line 86, in <module>
    results = evaluation.run(model, output_folder="/data/niklas/mieb/results-mieb-final", batch_size=1)
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 464, in run
    raise e
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 425, in run
    results, tick, tock = self._run_eval(
  File "/data/niklas/mieb/mteb/mteb/evaluation/MTEB.py", line 300, in _run_eval
    results = task.evaluate(
  File "/data/niklas/mieb/mteb/mteb/abstasks/AbsTask.py", line 126, in evaluate
    scores[hf_subset] = self._evaluate_subset(
  File "/data/niklas/mieb/mteb/mteb/abstasks/Image/AbsTaskAny2TextMultipleChoice.py", line 62, in _evaluate_subset
    scores = evaluator(model, encode_kwargs=encode_kwargs)
  File "/data/niklas/mieb/mteb/mteb/evaluation/evaluators/Image/Any2TextMultipleChoiceEvaluator.py", line 78, in __call__
    query_embeddings = model.get_fused_embeddings(
  File "/data/niklas/mieb/mteb/mteb/models/blip_models.py", line 123, in get_fused_embeddings
    image_embeddings = self.get_image_embeddings(images, batch_size)
  File "/data/niklas/mieb/mteb/mteb/models/blip_models.py", line 86, in get_image_embeddings
    image_outputs = self.model.get_image_features(**inputs)
  File "/env/lib/conda/gritkto4/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1729, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'BlipForImageTextRetrieval' object has no attribute 'get_image_features'

I think it's an error here: https://github.com/embeddings-benchmark/mteb/blob/2b56317b73047d4a242f9b86f44f08c23b094011/mteb/models/blip_models.py#L86
image_outputs gets value of vision_model(**inputs) since BLIP model doesn't have a get_image_features() method or attribute (see https://github.com/huggingface/transformers/blob/ccbd57a8b665fbb5b1d566c0b800dc6ede509e8e/src/transformers/models/blip/modeling_blip.py#L1450).
Fix in this PR: https://github.com/embeddings-benchmark/mteb/pull/1394

Closing this for now as the PR is merged.


Make checkout progress indicators more responsive

Fix #464

Screenshots please :)

1

2

3

Current coverage is 60.76% (diff: 100%)

Merging #599 into master will not change coverage

@@             master       #599   diff @@
==========================================
  Files            97         97
  Lines          4386       4386
  Methods           0          0
  Messages          0          0
  Branches        453        453
==========================================
  Hits           2665       2665
  Misses         1627       1627
  Partials         94         94

Powered by Codecov. Last update 69a733f...336ee99


fix!: remove unnecessary nonce from message gql queries

Closes #3294

Release notes
In this release, we:

Optimized the getMessageByNonce provider endpoint

Summary

The nonce returned from the gql query was removed from the messageFragment operation as the parameter can actually be re-used in the function  getMessageByNonce and  a separate fragment was created for getMessage
Breaking Changes

Removed the nonce property from Provider.operations.getMessageByNonce(). This can still be retrieved by Provider.getMessageByNonce().

Checklist

[x] All changes are covered by tests (or not applicable)
[x] All changes are documented (or not applicable)
[x] I reviewed the entire PR myself (preferably, on GH UI)
[x] I described all Breaking Changes (or there's none)

This can be done at a later date - this optimization doesn't provide (much value).

Re-opening this so that we may re-introduce breaking changes at a later more appropriate date.


Reexport 'composable' from library in runtime, for module has items returning undefined

Environment

Operating System: Linux
Node Version:     v19.4.0
Nuxt Version:     3.3.2
Nitro Version:    2.3.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/bootstrap-vue/bootstrap-vue-next/blob/main/packages/nuxt/src/module.ts
&
https://github.com/bootstrap-vue/bootstrap-vue-next/blob/main/packages/nuxt/src/runtime/composables.ts
Describe the bug
module.ts
    const arr: Import[] = []
    if (Object.values(normalizedcomposables).some((el) => el === true)) {
      const imports = parseActiveImports(
        {
          createBreadcrumb: false,
          useBreadcrumb: false,
        },
        normalizedcomposables
      ).map(
        (el) =>
          ({
            from: resolver.resolve('./runtime/composables'),
            name: el,
          } as Import)
      )
      arr.push(...imports)
    }

runtime/composables.ts
import foo, {Composables} from 'bootstrap-vue-next'

const {createBreadcrumb, useBreadcrumb, useColorMode} = Composables

export {createBreadcrumb, useBreadcrumb, useColorMode}

When trying to reexport some composables through a runtime file, everything from the import returns undefined...
So in this case, foo, & Composables are undefined, all the time.
Using an actual plugin -> export default defineNuxtPlugin that has import {something} from 'bootstrap-vue-next' works fine. Obviously they work a little different.
Why does the composables.ts only return undefined? How can I fix the issue?
The files build, but when trying to dev the playground, it fails when loading the playground app.
Additional context
When trying to following the guidance from https://nuxt.com/docs/guide/going-further/modules#injecting-composables-with-addimports-and-addimportsdir , it doesn't really work since the composable comes from an import... The module author guide doesn't really reference importing.
I'm probably just doing something wrong. lmk. Unlikely that it's really a "bug"
Logs
One example:

[nuxt] [request error] [unhandled] [500] Cannot destructure property 'createBreadcrumb' of '__vite_ssr_import_0__.Composables' as it is undefined.                     10:41:25
  at ./src/runtime/composables.ts:5:9

I originally was attempting to use https://github.com/epicmaxco/vuestic-ui/tree/develop/packages/nuxt/src as an example for how they're importing components.

Something that I have found out, which makes me believe this is a "bug"
Doing:
import foo, {Composables} from 'bootstrap-vue-next'

const {createBreadcrumb, useBreadcrumb, useColorMode} = Composables

export {createBreadcrumb, useBreadcrumb, useColorMode}

Will not work, however:
export {createBreadcrumb, useBreadcrumb, useColorMode} from 'bootstrap-vue-next'

Does work. It's not necessarily ideal since in my case, I want it to automatically work if Composables changes, not necessarily me need to manually go in every time a Composable is added or removed.


python310Packages.reportlab: 3.6.9 -> 3.6.10

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

There current version is 3.6.11

And please use the SRI hash format

No thanks. I like taking the hash published on PyPI.

During python-updates we updated this package to 3.6.11 already. Can you rebase your remaining changes?

FYI: https://github.com/NixOS/nixpkgs/pull/191460

Closing according to the comments.


Get the test result in the current project

Store the details of a test run so that we know where the results files are. Get results by date, get latest, get just failures
Get-TestResult -Latest -Failures

duplicate of #106


Second half of 2022 missing from fuel_receipts_costs_aggs_eia table

Describe the bug
In the fuel_receipts_costs_aggs_eia of the pudl.sqlite, at least as of Oct 18, 2022 data is incomplete for 'quarterly' and 'monthly' temporal aggregations and missing for 'annual'.
Bug Severity
How badly is this bug affecting you?

High: This bug is preventing me from using PUDL for 2022 fuel costs.

To Reproduce
Steps to reproduce the behavior -- ideally including a code snippet that causes the error to appear.
import pandas as pd
import sqlalchemy as sa

pd.read_sql_table(
    "fuel_receipts_costs_aggs_eia",
    sa.create_engine("sqlite:////.../pudl.sqlite").connect(),
).groupby("temporal_agg").report_date.max()

temporal_agg
annual      2021-01-01
monthly     2022-06-01
quarterly   2022-04-01
Name: report_date, dtype: datetime64[ns]

Expected behavior
A clear and concise description of what you expected to happen, or what you expected the data to look like.
Software Environment?

Operating System. MacOS 13.5.2
Python version and distribution '3.11.5 | packaged by conda-forge | (main, Aug 27 2023, 03:33:12) [Clang 15.0.7 ]'
How did you install PUDL?

PUDL not installed, reading from pudl.sqlite

@UdayVaradarajan, adding you here for visibility or to add any info.

@arengel in previous outputs was the data available through the end of 2022? The input archive looks like it's from February, 2023, and I think EIA updates that bulk data output frequently, so I would imagine it should have been. But just wanted to clarify if this was a regression, or a newly discovered deficiency.

Its a newly discovered deficiency as far as I know, found while updating our input datasets to include 2022.

Okay, good to know.
Unfortunately Zenodo's migration to a new backend at the end of last week has temporarily hosed our archiving infrastructure. @e-belfer is updating it to work with the new API over in this PR. As soon as that's fixed we can make a new bulk electricity data archive and get the most recent data in there.

Doing some old issue cleanup! We've updated the bulk electricity data 3-4 times since this issue was made, and it looks to me like there is 2022 data in the core_eia__yearly_fuel_receipts_costs_aggs table. So I'm closing this issue, but let me know if it has not been addressed as expected!


⚠ AlphaRatio has degraded performance

In 042b090, AlphaRatio ($AR) experienced degraded performance:

HTTP code: 200
Response time: 6871 ms

Resolved: AlphaRatio performance has improved in 5b521de after 6 minutes.


All line endings should be newlines

Remember do not combine whitespace changes with other changes tho

I'm pretty sure everythings been newlines for a while. If particular files have this problem in the future we can open new issues.


network issues

Hi there,
very interesting project, particularly the way you deal with the landscape/portrait stuff, it s transparent for the coder
I have a question about the network issues (event hough I know there is no actual request..)
for example in GetTvShowsInteractor class, we wait for some data received later on and then passed to the nofityTvShowsLoaded method. What if the context disappears meanwhile, like somebody killed the app, in your opinion, should'nt the  callback object be a WeakReference?

For sure the callback should be a weak reference :) This is just a sample and I didn't care about this little details because the sample is focused on UI patterns :)

You should definitely state it in readme This is just a sample and I didn't care about this little details because the sample is focused on UI patterns!


NetInfo returns true when connected to [WiFi|cellular] but Internet is not reachable

When I have mobile data on(cellular internet - device is connected via Edge, 3G, WiMax, or LTE) and my data package is finished (i.e: I cannot use internet) Netinfo always return true.
Environment

Environment:
OS: macOS High Sierra 10.13.3
Node: 8.9.1
Yarn: Not Found
npm: 5.6.0
Watchman: Not Found
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.54 => 0.54

Expected Behavior
Ideally netinfo should return false when there is no internet connectivity. Just turning on the mobile data should not enough for it to depict that device has internet connection.
Actual Behavior
  NetInfo.isConnected.fetch().then(isConnected => {
     alert(isConnected);
   })

Steps to Reproduce
Just turn off the wifi and turn on the data connection on the mobile device which has no sim or with the sim which has no credit. It is happening on both iOS & Android.

Can you edit your post and ensure the repro steps include the specific version you tested this on?

Updated.

Thank you!

We'll need to investigate if this is working as intended. NetInfo is correctly showing that the device is connected to a cellular or WiFi network. The question is - should this also reflect Internet reachability? Personally, I don't think it should, but we should still provide a way for the developer to test reachability towards an arbitrary host.

@hramos  thank you but the issue is I think most of the developers are not much concerned with the fact that device is either connected to wifi/cellular or not, the major concern is to check the internet reachability, to limit the actions which should not performed by the app if there is no internet connection.
For the temporary solution I have just sent a ping request to my WebAPI through code before making a request if it's not reachable so I assume there is no internet connection. Either this is incorrect WebAPI server could be down.
return fetch('URL')
      .then((response) => {
      })
  .catch((error) => {
        if(error == 'TypeError: Network request failed'){
          Alert.alert('Something went wrong', 'Kindly check if the device is connected to stable cellular data plan or WiFi.');
        }
       });

But I am still in favour of the fact that internet reachability check should be provided as a part of the library.

I have airplane mode on.  So WiFi and Cell are turned off.  The API is still reporting that I'm online.
The following function is always returning true for me....
  return new Promise(resolve => {
        NetInfo.isConnected.fetch().then(isConnected => {
          console.log('Device, is ' + (isConnected ? 'online' : 'offline'));
          resolve(isConnected)
        })
    })
}```

As a workaround I had previously implemented the following.  With an update to react-native 0.54.4 the API reports that I'm connected WiFi after disabling Wifi on iPhone X.

```//workaround for a bug on iOS where the isConnected function doesn't
//actually work.
export function isNetworkConnected() {
  return NetInfo.getConnectionInfo().then(connectionInfo => {
    console.log('connection info:', connectionInfo)
    if (connectionInfo.type.match(/unknown/i)) {
      return new Promise(resolve => {
        const handleFirstConnectivityChangeIOS = isConnected => {
          console.log('connection info:', isConnected)
          NetInfo.isConnected.removeEventListener('connectionChange', handleFirstConnectivityChangeIOS);
          resolve(isConnected);
        };
        NetInfo.isConnected.addEventListener('connectionChange', handleFirstConnectivityChangeIOS);
      });
    }
    reachability = connectionInfo.type.toLowerCase();
    return (reachability !== 'none' && reachability !== 'unknown');
  });
}```

Has anyone fixed this problem? I got the same situation with react-native 0.55.4
I can use connectionInfo.type === 'none' for android, but ios always return 'unknown' even with or without wifi...

Does the following work as a workaround?
const connectionInfo = await NetInfo.getConnectionInfo();
const connectionIsLost = connection.effectiveType === 'unknown';

Having the same issue here, has anyone fixed this ?

Does the following work as a workaround?
const connectionInfo = await NetInfo.getConnectionInfo();
const connectionIsLost = connection.effectiveType === 'unknown';

No

Does anyone know solution to this issue? i'm having similar issue

Does anyone know solution to this issue? i'm having similar issue

https://github.com/tegraoss/react-native-connection-status
I made this work around, but it only works in android, in iOS it only makes a pooling so a I don't recommend to use it in production.

Heads up: we moved react-native-netinfo into its own repository, which should allow for making changes and fixes much faster. Please continue the discussion about this issue there: https://github.com/react-native-community/react-native-netinfo/issues/12


Document setting up a station for VideoMode usage

Document which instruments are needed
Document output of VirtualAwg and measuresegment so users can implement their own backend

Done in docs/ folder


Update Calico and Canal

Changes

Update calico-node version used
Update calico/cni
Updated manifests with some changes that have been made upstream
Added liveness and readiness for calico-node in Canal configuration
~Remove un-needed ClusterRole from Canal for calico-node (@mattymo I'm fairly confident that this is not needed but you added it originally so please take a look.)~

Testing
I've tested my changes by using the provided Vagrant with both Calico and Canal as the network_plugin (with network policy enabled) and verified that the "Simple Policy Demo" https://docs.projectcalico.org/v2.6/getting-started/kubernetes/tutorials/simple-policy works as expected.

ci check this

The failures look to be a failure to pull google_containers/k8s-dns-kube-dns-amd64 and google_containers/cluster-proportional-autoscaler-amd64.

CI should run this again.

Thanks @hswong3i I've merged your changes which update Calico to the latest release and also rebased my changes onto latest master.

kicked off additional canal/calico ci steps

I had removed a ClusterRoleBinding and ClusterRole that upon review I think was needed and possibly had caused some of the test failures.

@tmjd patch need rebase with master
I had also using this for more than 2 weeks and all looks good enough ;-)

@tmjd patch need rebase with master
I had also using this for more than 2 weeks and all looks good enough ;-)

@bradbeam @tmjd @woopstar CI looks good and all pass now~~~

ci passed but pipeline back to github failed :-(

ping @bradbeam @tmjd @woopstar


Exams

Note: there is a wrong naming of res in commit "Moving res from argument ...", res is a parameter of function

just by the way: Such a caching is not required const length = arr.length; V8 engine will optimize it automatically


Basilisk

Anyone interested in setting up and maintaining a user.js version for Basilisk?

My initial thoughts: nah
I'm not interested myself. However, it should be easy enough for someone to create it based on the ghacks user.js (deprecated section is by FF version, new prefs (since we came here at least) always get the FF version). It would need testing/checking to see what has been stripped out. Once its been done, then it should be easy to maintain - but the more divergent basilisk becomes from FF the more of a nightmare. I'm not up to speed on basilisk - whats been stripped, what's it goals are long term. And it would require seeing what moonchild & co add for their own prefs. It's probably better suited to a dedicated repo
Anywho... it won't be me. I have enough trouble finding time just for FF stable. And I still need to do a relaxed version (either a relaxed-override.js or a branch), after a couple more section revamps and the mess with storage is sorted. And the wiki needs my attention.
Anyone is free to take our project as a starting point - I'll leave this topic open for a week while I am away, so people can see it and you can all talk about a basilisk user.js home

Where you going @Thorin-Oakenpants ?


What about vue.js , replace react.

What about vue.js , replace react.

same question..

Why would it be a good idea?
The solution is working as is. There is no need to change the frontend framework.


Helm 3.6.3 unknown command "init" for "helm"

Reference Page: https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-new#install-helm
I get the following error when I try to run the below commands:
kubectl create serviceaccount --namespace kube-system tiller-sa
serviceaccount/tiller-sa created
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller-sa
clusterrolebinding.rbac.authorization.k8s.io/tiller-cluster-rule created
helm init --tiller-namespace kube-system --service-account tiller-sa
Error: unknown command "init" for "helm"
Please confirm if this documentation is accurate for the latest available Helm version at the moment:
helm version
version.BuildInfo{Version:"v3.6.3", GitCommit:"d506314abfb5d21419df8c7e7e68012379db2354", GitTreeState:"clean", GoVersion:"go1.16.5"}
Should I have another Helm version installed?
I found these:
https://stackoverflow.com/questions/59261340/helm-init-has-been-removed-in-version-3
https://helm.sh/blog/helm-v3-beta/
So it looks like helm init command has been removed.
If that is the case, can you please update our documentation accordingly?
Thanks,
Cristiano

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 95812617-2cee-fb2c-2c6d-573f222033be
Version Independent ID: bf51864f-646f-2fda-7842-b1f3cf2f9ce2
Content: Creating an ingress controller with a new Application Gateway
Content Source: articles/application-gateway/ingress-controller-install-new.md
Service: application-gateway
GitHub Login: @Caya
Microsoft Alias: caya

Hello @Cristiano-Rosa
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

Any update on this?  The documentation incorrectly refers to helm 2 (and helm init), which is obsolete.  see #65016

Hi - I've assumed ownership of this article. I am reassigning the issue to myself. We currently have a large backlog of GitHub issues so I'm prioritizing these and working them as I am able.  #reassign:greg-lindsay

This is being tracked as internal content issue: 91169
#please-close


fix cv link

👷 Deploy Preview for vargas-work-portfolio processing.

Name
Link

🔨 Latest commit
534a472f3246960af45760f10dcc70d5bbabfb91

🔍 Latest deploy log
https://app.netlify.com/sites/vargas-work-portfolio/deploys/64e3d55c6cb4000009617658


chore(nginx): update nginx to 1.11.6

See https://nginx.org/en/CHANGES

Current coverage is 55.23% (diff: 100%)

Merging #291 into master will not change coverage

@@             master       #291   diff @@
==========================================
  Files             6          6
  Lines           382        382
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            211        211
  Misses          151        151
  Partials         20         20

Powered by Codecov. Last update 76f6f36...99316f6


Revert "CLOUD-46697 Refactor platform parameters"

This reverts commit 6e7206c9960a7d89499c968767666b699feac732.
@akanto @schfeca75 It caused several issues, it's easier to revert now and work on it later.

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1755/


Cannot Build with cuda support

Hi Jean,
Thank you very much for your contributions to open source community.
I would like to use bcnn with CUDA support on. when I set them on in CmakeLists.txt
cmake .. ends up with errors.
I have installed cuda and nvcc --version does return following ;
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Sat_Aug_25_21:08:01_CDT_2018
Cuda compilation tools, release 10.0, V10.0.130

I suspect this could be because of lacking of maybe some symbolic links ?
Have you met this problem ?

Hi Fetullah,
I have not met this problem, could you provide the error message you get when running cmake .. ?

Here is terminal output after i try to built with cuda support on
atas@atas-MS-7B48:~/bcnn/build$ cmake ../
-- The C compiler identification is GNU 5.5.0
-- The CXX compiler identification is GNU 5.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- [bcnn] Targeted system processor: x86_64
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- [bcnn] Build with Cuda
-- [bcnn] Found Cuda libraries: /usr/local/cuda-10.0/lib64/libcublas.soCUDA_cublas_device_LIBRARY-NOTFOUND
-- [bcnn] Build with CuDNN
-- [bcnn] Build with AVX instructions
-- Found OpenMP_C: -fopenmp (found version "4.0")
-- Found OpenMP_CXX: -fopenmp (found version "4.0")
-- Found OpenMP: TRUE (found version "4.0")
-- [bcnn] Found openmp
-- [bcnn] Enabling logging
-- Found OpenCV: /usr (found suitable version "3.2.0", minimum required is "3.0.0")
-- [bcnn] [examples/yolo] Found OpenCV
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
CUDA_cublas_device_LIBRARY (ADVANCED)
    linked by target "bcnn" in directory /home/atas/bcnn

-- Configuring incomplete, errors occurred!
See also "/home/atas/bcnn/build/CMakeFiles/CMakeOutput.log".
See also "/home/atas/bcnn/build/CMakeFiles/CMakeError.log".

seems like a bug triggered by earlier version of cmake
https://github.com/clab/dynet/issues/1457
I changed the minimum version to 3.12.2 and I can build  bcnn


Login requirements?

Hello,
are there any special login-requirements to use Khanos? Always getting "unknown error" when I try to login with an flawlessly working Kanboard-instalation (current version 1.2.20, current app-version from the Playstore) :-(

If you have 2FA turned on you might want to check out #11

Thanks, but 2FA is not enabled :(

Thanks, but 2FA is not enabled :(

Hello @lorddoumer, thank you for using Khanos. I'll need more information about your issue. Do you have a custom role for your user or any custom auth setting you might consider? Any info would be great for me in order to replicate the problem

@Jeoxs no, just using the build in roles (manager, participant, viewer) and the default login (username + password) on an Linux server with Apache running. Set up some users and boards and installed a few plugins:

Gantt
Highlight Code Syntax
Milestone
Time Tracking Editor
Bigboard
Markdown Plus
Taglist
What other information could be helpful? If I can provide anything, please let me know :)

Same problem here. 100% password is alright, very similar setting to @lorddoumer
No special role
login as username and password (no 2fa)
plugins:

Customizer
Essential theme
EnableAttachmentRenaming
Telegram
Wiki
KanboardSearchPlugin
Gantt
Calendar

Same problem here. 100% password is alright, very similar setting to @lorddoumer
No special role
login as username and password (no 2fa)
plugins:

Customizer
Essential theme
EnableAttachmentRenaming
Telegram
Wiki
KanboardSearchPlugin
Gantt
Calendar


React stand alone: Mega Menu MVP enhancement to accommodate HC + AI updates Visual QA

 React stand alone: Mega Menu MVP enhancement to accommodate HC + AI updates Visual QA
Detailed description

Describe in detail the issue you're having.

Visual design QA
QA PDF link: https://ibm.box.com/s/k57zbe7l0ndgq9pitbskkbebmdrohlxb
Original design abstract link: https://share.goabstract.com/6f02a9ae-517f-45b8-b76f-b77273b9a4ad

Is this a feature request (new component, new icon), a bug, or a general
issue?

Visual Design QA

Is this issue related to a specific component?

React stand alone: Mega Menu MVP enhancement to accommodate HC + AI updates
https://ibmdotcom-react-canary.mybluemix.net/?path=/story/components-masthead--with-custom-navigation

What browser are you working in?

Chrome
Additional information

Screenshots or code
Notes

@jyoon25 I spoke to Olivia about the "View all ..." link border not touching the vertical border of the left panel, we decided to leave the gap there so that isn't a problem.


Handle batch proposals

The Chore
We are now getting quite a lot of proposals in and it can be hard to find the ones we want.
Think it is worth considering ways to reduce the info on the summary card so you can see more proposals at once.
Tasks

[ ] Do the UX
[ ] Make summary cards more compact so more can be seen on screen
[ ] Build it
[ ] Test

Additional details / background info

Dupe of #5561


Splitting test classes to avoid reaching debug log size length, enabl…

…es limits parsing from debug logs.

@jlantz This fixes the debug log size length for some test classes. Ready for review and merge.


Fabulous.XamarinForms.SkiaSharp does not handle gestures on Android

Assume we have this:
  View.SKCanvasView(
    paintSurface = drawImpl model,
    invalidate = model.redrawRequested,
    gestureRecognizers = [
      View.TapGestureRecognizer(fun () -> dispatch CanvasTapped)
    ]
  )

On iOS build tapping the canvas correctly fires CanvasTapped, while nothing happens on Android build.
Confirmed on Fabulous 0.41.0.

@cannorin I don't reproduce with only the given code.
I think there is a crash happening somewhere else preventing Fabulous to finish refreshing the UI.
Could you check the application output log when you tap the canvas?
There should be a stack trace in there if something happened.

Ah, I figured out it was because I added an effect to handle long press gesture via created. I removed it and it got working. Since iOS is working with both gestore recognizer and effect added, it seems it's a bug in Xamarin itself rather than Fabulous.Forms. Sorry 😅


Some definitions in the glossary need to be reviewed

For example:

Could be: A sequence of tools run on input data such as an mzML file which produces an output. There are over 185 TOPP tools to choose from.

Could be: TOPP is an application built using OpenMS. TOPP consists of many tools.

Could be: TOPPAS is an application which provides a GUI to create, edit and apply TOPP tools. TOPPAS is no longer supported and has been replaced by KNIME.

Also TOPPAS is only an ".app" on macOS, so maybe remove ".app"


Inequality operator returns value of wrong type if one operand is 0

In Elm 0.19 the inequality operator /= returns incorrect values if one operand is the Int value 0: it appears to return the other operand when it should return True or False.
SSCCE in the Elm 0.19 REPL:
---- Elm 0.19.0 ----------------------------------------------------------------
Read <https://elm-lang.org/0.19.0/repl> to learn more: exit, help, imports, etc.
--------------------------------------------------------------------------------
> 128 /= 0
128 : Bool

The issue is not reproducible in Elm 0.18, which behaves as expected:
---- elm-repl 0.18.0 -----------------------------------------------------------
 :help for help, :exit to exit, more at <https://github.com/elm-lang/elm-repl>
--------------------------------------------------------------------------------
> 128 /= 0
True : Bool

I've filed this as a compiler bug because the root cause appears to be bad code generation.  To verify this I wrote the following Elm module:
module Equality exposing (..)

import Html exposing (Html, div, text)
import Browser

main =
    Browser.sandbox
        { init = 0
        , update = update
        , view = view
        }

update msg model =
    model

view _ =
    div [] [ text (Debug.toString (128 /= 0)) ]

The compiled index.html file includes the following lines in the compiled output of the view function:
				elm$html$Html$text(
				elm$core$Debug$toString(128))

I can't reproduce this problem with any type other than Int, and I can't reproduce it with two non-zero Int values.  I also cannot reproduce any similar problem with the == operator.
I'm running Windows 10 version 10.0.17134.285 64-bit.

This Ellie seems to exhibit the same behaviour.

This Ellie seems to exhibit the same behaviour.

@szabba I don't see why that Ellie exhibits the same behaviour.
All I can see you doing with the x value is putting it in model.x and then testing the truthiness of that.  Because of this bug x, and hence model.x, will have the value 96 rather than True, but in JavaScript 96 is just as truthy as True, so TRUE appears.  Because model.x is never updated, TRUE always appears above the +1 button.
I would expect this Ellie to behave exactly the same once this bug has been fixed and x has the value True instead of 96.

I did consider the value 96 visible in the debugger, for a field that is typed Bool to be the same issue. Sorry, if that was confusing/unhelpful.

Hi! I just wanted to note for future readers that this issue doesn't actually interfere with the functionality. Since the type is supposed to be a boolean, then it will work fine in the rest of the program. The problem can only be discovered by the use of toString, which isn't really a problem. :)

The previous version had (0 /= x) and (x /= 0) result in truthy values, rather than the direct true or false value. The truthy values were observable via Debug.toString, so this will fix #1810. It seems there are other case where it can be observed, though I have not seen any reports of those cases.

This can be observed without toString by putting the bad bool inside any data structure.  Elm 0.19.0 incorrectly evaluates all of the following to False:
{ a = 7 /= 0 } == { a = True }
Just (7 /= 0) == Just True
(7 /= 0, True) == (True, True)
[(7 /= 0), True] == [True, True]

Doesn't even need a data structure, this also evaluates to False in Elm 0.19:
(12 /= 0) == (21 /= 0)

For the record, this is due to an optimization that relied on truthiness in JS. That issue https://github.com/elm/compiler/issues/1810 was fixed.

Hey. I'm new to Elm and its ecosystem and I'm unfamiliar with the release cycle and stuff. When could we expect a release including this fix? Or maybe a recommended approach is to build the compiler from source? How does it usually go with such notable bugs like this one? Thanks.
@evancz


feat(ci): simplify cache

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: CI

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information

Honestly i feel like https://github.com/Swatinem/rust-cache would be a good idea for most of the caches here, especially since it does some extra stuff to make the caches more efficient.
Also we may want to consider adding this: https://github.com/tauri-apps/tauri-docs/blob/dev/.github/workflows/update-docs.yml#L26-L27 to some of the workflows.

I'd prefer being consistent, and I see rust-cache would be better if we were only caching one target folder per job, but sometimes we're caching multiple.

This PR also simplifies a migration, so hopefully someone better on GH actions can give it a try later.


add play 2.9 support

Early support for PLay 2.9 using play 2.9.0-M4 with Scala 2.13 & 3.
We are also using ScalaTestPlus 6.0.0-M3.

Thank you for this PR. Looks like Play 9 does neither support Java 8 nor Scala 3.2. Is that correct? You need to update the test setup.

Thanks for your response. I've updated the Scala version used for the test to 3.3.0-RC6 but I'm unsure on were to update the Java version used. Any insight would be appreciated.

Superseded by #2772


DONE status is reported weirdly

for some reason its not all caps, and is in quotes:

other statuses are reported okay:

This is true.
Reason:
STARTING and NOTINIT are actually sent by the module's "wrapper" (Swift or Kotlin) code while it awaits for the Tor daemon to be ready and bootstrapped.
Once the daemon is bootstrapped the module will probe the Tor daemon (on it's control port) for it's actual network status which returns done most of the time. I had made the "wrapper" replies in capital to differentiate them.
It's in my road-map to actually expose the bootstrapping status  (IE Bootstrapping messages you see in xcode logs for example instead of just STARTING)  but I assumed sockets and hidden services have higher priority based on community feedback and this is good enough for now.
I'll keep the issue open as reference and close when implemented.