Helm reports that tiller is already installed in the cluster, but it's not deployed

$ helm init
Creating /home/myuser/.helm
Creating /home/myuser/.helm/repository
Creating /home/myuser/.helm/repository/cache
Creating /home/myuser/.helm/repository/local
Creating /home/myuser/.helm/plugins
Creating /home/myuser/.helm/starters
Creating /home/myuser/.helm/cache/archive
Creating /home/myuser/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /home/myuser/.helm.
Warning: Tiller is already installed in the cluster.
(Use --client-only to suppress this message, or --upgrade to upgrade Tiller to the current version.)
Happy Helming!
$ kubectl get pods --namespace kube-system | grep tiller
$

Output of helm version:
$ helm version
Client: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
<hangs...>
Output of kubectl version:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:26:04Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.11", GitCommit:"1df6a8381669a6c753f79cb31ca2e3d57ee7c8a3", GitTreeState:"clean", BuildDate:"2018-04-05T17:16:46Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS 1.8.11

What's the status of the tiller pod? Can you check using kubectl?

The tiller pod is not running, as to why it's not running is not clear.
$ kubectl -n kube-system get po
NAME                                    READY     STATUS    RESTARTS   AGE
heapster-75f8df9884-k8d8w               2/2       Running   0          6d
kube-dns-v20-5bf84586f4-56nh2           3/3       Running   0          6d
kube-dns-v20-5bf84586f4-qm4m7           3/3       Running   0          6d
kube-proxy-b8wmb                        1/1       Running   0          6d
kube-proxy-l5pkd                        1/1       Running   0          6d
kube-svc-redirect-96pm7                 1/1       Running   0          6d
kube-svc-redirect-j9sg6                 1/1       Running   0          6d
kubernetes-dashboard-5977dcf768-lkcst   1/1       Running   0          1d
tunnelfront-584dfdc655-k69ct            1/1       Running   0          6d

I'm getting the same thing on gce and k8s 1.10.1
$ helm version
Client: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}
Error: cannot connect to Tiller
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:26:04Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

$ helm reset --remove-helm-home --force --debug
Deleting /zfs/home/chris/src/apisnoop/dev/gce/.helm
Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.
$ helm init --service-account=tiller --wait --debug
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    app: helm
    name: tiller
  name: tiller-deploy
  namespace: kube-system
spec:
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: helm
        name: tiller
    spec:
      containers:
      - env:
        - name: TILLER_NAMESPACE
          value: kube-system
        - name: TILLER_HISTORY_MAX
          value: "0"
        image: gcr.io/kubernetes-helm/tiller:v2.8.1
        imagePullPolicy: IfNotPresent
        livenessProbe:
          httpGet:
            path: /liveness
            port: 44135
          initialDelaySeconds: 1
          timeoutSeconds: 1
        name: tiller
        ports:
        - containerPort: 44134
          name: tiller
        - containerPort: 44135
          name: http
        readinessProbe:
          httpGet:
            path: /readiness
            port: 44135
          initialDelaySeconds: 1
          timeoutSeconds: 1
        resources: {}
      serviceAccountName: tiller
status: {}
---
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: null
  labels:
    app: helm
    name: tiller
  name: tiller-deploy
  namespace: kube-system
spec:
  ports:
  - name: tiller
    port: 44134
    targetPort: tiller
  selector:
    app: helm
    name: tiller
  type: ClusterIP
status:
  loadBalancer: {}
...
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/repository
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/repository/cache
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/repository/local
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/plugins
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/starters
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/cache/archive
Creating /zfs/home/chris/src/apisnoop/dev/gce/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /zfs/home/chris/src/apisnoop/dev/gce/.helm.
Error: could not ping Tiller: context deadline exceeded

I got it fixed, here are the steps which I took.  The tiller container appeared to be stuck in an unknown state.  Let me know if this works for you.

$ kubectl delete service tiller-deploy -n kube-system
service "tiller-deploy" deleted
$ kubectl delete pods tiller-deploy-b6fbf658-57t6t -n kube-system --force=true --timeout=0s
pod "tiller-deploy-b6fbf658-57t6t" deleted
$ kubectl -n kube-system delete deploy tiller-deploy
2
Deploy Helm 2.6.2 with Kubernetes 1.8.11

$ helm init --service-account default

It's also useful to take a look on the ns events.
$ kubectl get events -n kube-system

LAST SEEN   TYPE      REASON              KIND         MESSAGE
3m15s       Warning   FailedCreate        ReplicaSet   Error creating: pods "tiller-deploy-7b45545f56-" is forbidden: error looking up service account kube-system/tiller: serviceaccount "tiller" not found
8s          Warning   FailedCreate        ReplicaSet   Error creating: pods "tiller-deploy-7b45545f56-" is forbidden: error looking up service account kube-system/tiller: serviceaccount "tiller" not found
8m43s       Normal    ScalingReplicaSet   Deployment   Scaled up replica set tiller-deploy-7b45545f56 to 1
49s         Normal    ScalingReplicaSet   Deployment   Scaled up replica set tiller-deploy-7b45545f56 to 1


community: support bind_tools for ChatMlflow

Thank you for contributing to LangChain!

[x] PR title: "package: description"

Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..."  for template changes, "infra: ..." for CI changes.
Example: "community: add foobar LLM"

Description:
Support ChatMlflow.bind_tools method
Tested in Databricks:

[x] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[x] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

cc @prithvikannan

This implementation looks great!
Can we add some tests to validate tool submission check logic and tool type parsing validation to ensure that changes in agent handlers in the core library doesn't create any breaking changes with this added agent handling capability?

@baskaryan Could I get a review on this PR?

@baskaryan Could you help me merge this PR? Thanks!

@jacoblee93 @efriis Could you help merging this PR? Thank you!


Load models once, reuse after sleep from preloaded model

This revision loads both the detector and classifer models once upon first starting the program in fetch_and_alert.py and then passes the loaded models to detect_img.py so it doesn't load them both each time. These loading functions come from the animl-py module, currently specifically the "model_load" branch within githib.
Resolves #39

This depends on having a .pt MD model and the dev branch of animl-py "model-load" within site packages of python3.8 of the conda env


Revised PWA docs per June 22 meeting

Changes discussed in the meeting and made here:

Move Push Notifications section of get-start to become separate article.
Expand and rearrange TOC.
etc.

Docs Build status updates of commit 4b57d40:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/progressive-web-apps/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/02/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/get-started.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/microsoft-store.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/offline.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/push-notifications.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/pwabuilder.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/serviceworker.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/webappmanifests.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/whats-new/pwa.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

We'll need to think about how we can bring them into PR #1429 later, since I'm moving/changing a lot of the content in that PR.

I actually did this. My last commit in the feature branch now contains most of your changes applied to my branch: https://github.com/MicrosoftDocs/edge-developer/pull/1429/commits/d2e6d0d746c36017dd42fad3a797f208afb1b75e

Docs Build status updates of commit acc908f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/progressive-web-apps/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/02/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/get-started.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/microsoft-store.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/offline.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/push-notifications.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/serviceworker.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/webappmanifests.md
:white_check_mark:Succeeded
View

microsoft-edge/progressive-web-apps-chromium/whats-new/pwa.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

These changes were merged into PR 1429 https://github.com/MicrosoftDocs/edge-developer/pull/1429


Broken execution since #6

Hi,
It looks like that since #6 which was proposed by myself, the tool fails silently when migrating maven repository as no default Maven Snapshot Version Behavior is defined and tool needs one.
@DarthFennec: initially in my PR I proposed a value when user didn't set anything (to avoid editing all the repo he wants to migrate) and with your proposal to have a list of chosen value, this was lost making it mandatory to edit all the repos.
I'll propose something as soon as I got a minute

Odd, I seem to have a default value of unique when I run it. In fact, you specified the default value here, and I set it in the UI here. So by all means you should be seeing defaults, no?

Mmmh looks like you're right, from a fresh setup it works as expected but not when loading an existing config


feat: expose loadConfigFromFile API

For advanced usage like https://github.com/antfu/vite-ssg to have better controls over user configs

Is resolveConfig not enough for the use case?

Is resolveConfig not enough for the use case?

I found a workaround by asking users to have this line in their config and inject the env on the go:
Vue({
  ssr: !!process.env.VITE_SSG
})

My use case is fulfilled and I am ok with closing. However, I think there are still some limitations toward programmatic usages:
Both build() and resolveConfig() accept a inlined UserConfig for their first argument. While resolveConfig() returns ResolvedConfig which also contains Vite's internal plugins. There is no easy way to read users' raw config to have some context-aware operations without writing a custom loader for the config.
For example:
const config = await resolveConfig()

// manipulate the config, injecting plugins, etc.

await build(config) // errors on both type and runtime

By exposing loadConfigFromFile() we can have something like:
const config = await loadConfigFromFile('vite.config.js')

// manipulate the config, injecting plugins, etc.

await build(config, '') // assuming passing an empty string to disable the config file merging.

I found a workaround by asking users to have this line in their config and inject the env on the go:
Vue({
  ssr: !!process.env.VITE_SSG
})

My use case is fulfilled and I am ok with closing. However, I think there are still some limitations toward programmatic usages:
Both build() and resolveConfig() accept a inlined UserConfig for their first argument. While resolveConfig() returns ResolvedConfig which also contains Vite's internal plugins. There is no easy way to read users' raw config to have some context-aware operations without writing a custom loader for the config.
For example:
const config = await resolveConfig()

// manipulate the config, injecting plugins, etc.

await build(config) // errors on both type and runtime

By exposing loadConfigFromFile() we can have something like:
const config = await loadConfigFromFile('vite.config.js')

// manipulate the config, injecting plugins, etc.

await build(config, '') // assuming passing an empty string to disable the config file merging.

Yeah makes sense.

Yeah makes sense.


Set defaultTaskImage for Windows runtimeTemplates to w16

https://github.com/Shippable/pm/issues/10308

Verified on RC.


33256

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

[x] I attest that the connector works and I verified by deploying and testing all the operations.
[ ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[ ] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[ ] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[ ] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@SpillChek2 I'm just checking in to see how things are going with updating your connector artifacts as per the given feedback. Please feel free to reach out with any questions you may have, Thanks.

@SpillChek2 I am closing this PR as there is no response from you, You can reopen the same PR whenever you are ready, Thanks


Community Support

Is there an active community around the ANT Framework for developers to seek help and share experiences?

Community does not exist separately.
You can raise a problem in the issue section.


[Bug]: error unsurported sim

Description
One of my sims is labeled unsuported and yet its on the same network
Steps to reproduce
1.open stax app
2. click on sim tab
Expected result
both should be supported
Actual result
unsuported  sim
Link to screenshots/screen recordings
https://drive.google.com/file/d/1Sh648sHLDrofDDnw8EyYihnIwtwa0GZU/view?usp=sharing
Device name
No response
Android OS
techno pop 5p
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

This bug has been reported by another person, we have logged it for fixing.


switched to cluster api v1.2.2, cleanup

@peknur, do you have any idea why we use vendoring here?

@peknur, do you have any idea why we use vendoring here?

Not sure what was original reasoning for that but I think that we could delete that vendor folder for now. We can always restore it if we see some problems before stable release. Will you do it in this PR or should we create separate PR for that?


Set Up basic front-end elements and QR generation

Please add a general .gitignore file for typescript apps (or alt least put the node_modules folder in it). 👍👍


[e2e]: nodejs create main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v39.0.459
Run: https://github.com/slsa-framework/example-package/actions/runs/10696097104
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.create.main.default.slsa3.yml
Trigger: create
Branch: v39.0.459
Date: Wed Sep  4 06:17:50 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v39.0.460
Run: https://github.com/slsa-framework/example-package/actions/runs/10714851283
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.create.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.create.main.default.slsa3.yml
Trigger: create
Branch: v39.0.460
Date: Thu Sep  5 06:13:13 UTC 2024
Tests are passing now. Closing this issue.


Is OpenSSL::SSL::VERIFY_NONE chainable?

We have a RestAPI wrapper for all Apis with http.rb included.
The HTTP request is composed depending on what the API needs or requires.
Now there is one API where we need to disable the SSL Verify.
Can this be included in the generic HTTP object?
 def http(headers = {})
    http = HTTP.headers(__request_params.merge(headers)).timeout(timeout)
    http = http.follow if __request_follow == :follow
    http = http.cookies(__rest_cookies) if __rest_cookies
    http = http.basic_auth(__rest_basic_auth) if __rest_basic_auth
    http
  end

  def get(url = '', headers = {})
    request do
      http(headers).get("#{@rest_url_base}#{url}", params: __rest_query)
    end
  end

  ...

I would like to add this as option within the http-method or is it needed to append it to the get like this?
  def ssl_context
    return unless  __rest_sll_verify_none

    ctx = OpenSSL::SSL::SSLContext.new
    ctx.verify_mode = OpenSSL::SSL::VERIFY_NONE
    ctx
  end

  def get(url = '', headers = {})
    request do
      http(headers).get("#{@rest_url_base}#{url}", params: __rest_query, ssl_context: ssl_context)
    end
  end

I'm unclear what you are asking here. Note that we do not recommend setting OpenSSL::SSL::VERIFY_NONE.


Typo mistake (?)

The air temperature was road temperature and vice versa.

@tubalainen Sorry, i must have missed the PR here.
This is fixed in the latest version of the package.
This package will be pushed and included in home assistant together with some additional other fixes in this PR:
https://github.com/home-assistant/home-assistant/pull/22139

Fix is already in the package.


oem/ami: add support for publishing AMIs in us-gov-west-1

A few general changes:

Use https for EC2 endpoint URLs
Remove parallelism from prod-publish, was launching enough Java
processes at once to trigger OOM :(
Only share snapshots with Amazon in us-east-1: only needed for
marketplace listing and marketplace only uses us-east-1.

LGTM


we should be building x86 artifacts for android, not x64 ones

Related to https://github.com/flutter/flutter/issues/2642, I think we need to build our android emulator artifacts for x86, not x86-64 (x64). Running adb shell getprop ro.product.cpu.abi against the android emulator, genymotion, and xamarin all return x86, and when trying to run on an emulator, I see the error message:
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/com.example.flutter_sunflower-1/lib/x86/libsky_shell.so" is 64-bit instead of 32-bit

We're currently building for (and uploading to) android-x64 (https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipes/flutter/engine.py#93).

The Android emulator can support 32-bit or 64-bit x86 system images.  I think we should continue building for x86-64.

The Android emulator can support 32-bit or 64-bit x86 system images.

Confirmed this yesterday.
However, it's not clear to me if GenyMotion (a very popular android emulator) is x86 only (or not).

I just pulled the latest from alpha branch, and I'm trying to run one of the sample apps on genymotion. Here's my output:
spierce7:myapp spierce7$ flutter run
Downloading Dart SDK 1.16.0-dev.3.0...
######################################################################## 100.0%
Building flutter tool...
Downloading engine package sky_engine...      2.5s
Downloading engine package sky_services...    1.0s
Downloading engine artifacts android-arm...   5.8s
Downloading engine artifacts android-x64...   9.6s
Downloading engine artifacts ios...           7.9s
Downloading engine artifacts darwin-x64...    3.6s
Installing app.apk on device.
Running lib/main.dart on Google Nexus 5, 5 1 0, API 22, 1080x1920...
error: Unable to find Dart library 'package:mojo_services/mojo/ui/view_containers.mojom.dart'.
Failed to run the Flutter compiler. Exit code: 1

Oops; flutter has exited unexpectedly.
Crash report written to flutter_03.log; please let us know at https://github.com/flutter/flutter/issues.
spierce7:myapp spierce7$ flutter run
Installing app.apk on device.
Running lib/main.dart on Google Nexus 5, 5 1 0, API 22, 1080x1920...
error: Unable to find Dart library 'package:mojo_services/mojo/ui/view_containers.mojom.dart'.
Failed to run the Flutter compiler. Exit code: 1

Oops; flutter has exited unexpectedly.
Crash report written to flutter_04.log; please let us know at https://github.com/flutter/flutter/issues.

You might need to run pub get to update your dependent packages.  The tool is supposed to do that for you if you run flutter upgrade.  We should find a way to check the state of the current directory and suggest this fix.
@devoncarew I would have expected flutter run to run pub get automatically.  Maybe it should consider the modified time on the flutter tools stamp file to decide whether to run pub get?

https://github.com/flutter/flutter/pull/3206 <--- Teaches the tool to run pub get automatically in this situation.

Ran pub get, and then tried again. Slightly different output, but same result:
spierce7:myapp spierce7$ flutter run
Building APK...
Warning: signing the APK using the debug keystore.
Generated APK to build/app.apk.
Installing app.apk on device.
Running lib/main.dart on Google Nexus 5, 5 1 0, API 22, 1080x1920...
Starting: Intent { act=android.intent.action.RUN dat=/data/local/tmp/dev.flx flg=0x20000000 cmp=com.yourcompany.myapp/org.domokit.sky.shell.SkyActivity (has extras) }
Error type 3
Error: Activity class {com.yourcompany.myapp/org.domokit.sky.shell.SkyActivity} does not exist.
Error running application on Google Nexus 5, 5 1 0, API 22, 1080x1920.

@spierce7 This looks expected to me.  There are still a few things missing.

[ ] flutter run does not know how to detect the right abi of the device and switch between prebuilt engines (FYI @devoncarew) adb shell getprop ro.product.cpu.abilist or adb shell getprop ro.product.cpu.abi will do so, we just need to teach the flutter tool to call that and use that info.
[ ] We're only uploading x86-64 artifacts, not x86-32, @jason-simmons and I spoke about this yesterday, there are probably some minor fixes to make to our BUILD.gn files or sky/tools/gn wrapper to make building Android x86-32 easy, once that's done I can teach the bots how to do so.

@jason-simmons and I spoke about this today, I believe he's willing to push this over the finish line, so that 32-bit emulators work correctly.

Looking at our infra bots, it looks like we're building and uploading both x86 and x86-64 for Android:
https://chromium.googlesource.com/chromium/tools/build.git/+/master/scripts/slave/recipes/flutter/engine.py#96

I see x86 artifacts, debug only: https://storage.googleapis.com/flutter_infra/flutter/2efc78cc24eac9439a5315ed9333fa8599aab3a1/android-x86/artifacts.zip

Yep, we have both x86 and x64 debug artifacts for android. We'll need to add profile and release artifacts, too, for the gradle work.
@jason-simmons do you want to own this, or should I take it?

We've intentionally not added --release artifacts for non-shipping configurations (e.g. desktops, emulators).  One could argue that there are x86 Android shipping configurations (devices), but last time I checked the usage numbers on those were very low, maybe that's changed?
Looks like it's 1.5%: http://hwstats.unity3d.com/mobile/cpu.html  Many of them support arm emulation too last I knew.

1.7% for Android based on that page. As of 2015, there were apparently 1.4 billion Android devices, so that's over 23 million potential users right there.

@jason-simmons are you working on this one?

I'm not currently involved in this - feel free to assign it elsewhere

I believe this can be replaced by #9253 which is more clear on the topic.  We should provide both x86 and x64 build products.


fix: alert rule and tests association

fixes #158
Changes the alert rule test_ids schema attribute to be computed so that it is not considered in the TF plan.
Also, since the alert rule returns a field tests when getting by id and receives a field testIds when updating the alert rule, had to implement a map from the GenericTest to get only the testId.
One drawback of this approach (not a huge one IMO) is that the state may not always be accurate. This is because a test <-> alert rules association can be changed from the test perspective and not get reflected on the alert rule perspective. Anyways, it will eventually update the state when the next alert rule update is performed.
The compilation and test failure is because the following PR needs to be merged and released and then updated the version here: https://github.com/thousandeyes/thousandeyes-sdk-go/pull/122

closing in favour of https://github.com/thousandeyes/terraform-provider-thousandeyes/pull/168


Packaging for fedora

Hi,
I can take up packaging this for fedora. I do not think srpm is a good practice as during updates it is not included easily. It becomes more tedious to push updates to users.
if it is desired I can take this up as making RPM is pretty easy.
kindly advice.

Hmm. Sounds good. ok will work on it .

Hi
@Johnny: Thank you for the hint about copr. I'm working on that. (Setup a public web server...)
@Frankie: Would be great if you could test the scripts and spec files in my git repo and give me feedback.
On Monday 05 January 2015 05.29:10 Frankie Onuonga wrote:

Hmm. Sounds good. ok will work on it .

Reply to this email directly or view it on GitHub:
https://github.com/sampsyo/beets/issues/375#issuecomment-68707291

Adrian Freihofer
Gschwaderweg 29
8610 Uster
043 497 84 01

Sure thing @afreof

The packages are now provided by copr. At least building the packages and run beets from command line is now possible. For installation instructions please go to https://github.com/afreof/fedora-beets.

Cool! Is it time to add these instructions to the beets docs? If so, would someone mind opening a small PR that adds the right stuff?

Currently not all features of beets are tested. One issue which I already found is the web service. It basically works but a click on the play button triggers an exception on the server:
Exception happened during processing of request from ('<IP_ADDRESS>', 38346)
Traceback (most recent call last):
  File "/usr/lib64/python2.7/SocketServer.py", line 595, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib64/python2.7/SocketServer.py", line 334, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib64/python2.7/SocketServer.py", line 653, in __init__
    self.finish()
  File "/usr/lib64/python2.7/SocketServer.py", line 712, in finish
    self.wfile.close()
  File "/usr/lib64/python2.7/socket.py", line 279, in close
    self.flush()
  File "/usr/lib64/python2.7/socket.py", line 303, in flush
    self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe

I guess it is related to missing java script files. The Debian beets package depends on libjs-backbone, libjs-jquery and libjs-underscore. Currently none of them is available on my system. Does beets need them for playing audio files on the web page?

That traceback is benign; you can safely ignore it.

For Fedora 21 x86_64, beets is packaged. It's the right time to update the documentation now. I propose to update the documentation by the following installation steps:
yum install dnf dnf-plugins-core
dnf copr enable afreof/beets
yum update
yum install beets
With Fedora 22 (may 2015) the procedure will be simplified, since dnf is targeted to become the default package manager.

Thank you! I've added some instructions to the getting-started guide. Can you let me know if anything looks wrong?

Sorry the delay. Yes, this is fine. Thank you.

Thank you for your expertise, @afreof!

beets is now (Fedora 22 onwards) in the official Fedora Repository. The copr repository is obsolete.


Add papermill init test case

Issue #, if available:
#78
Description of changes:
Add a presubmit job to test notebooks using papermill. Only
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/retest

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test-presubmit-workshop-e2e

/test presubmit-workshop-e2e

/test presubmit-workshop-e2e

Executing:   0%|          | 0/5 [00:00<?, ?cell/s]/usr/local/lib/python3.6/dist-packages/IPython/paths.py:67: UserWarning: IPython parent '/home/jovyan' is not a writable location, using a temp directory.
  " using a temp directory.".format(parent))
/usr/local/lib/python3.6/dist-packages/IPython/paths.py:67: UserWarning: IPython parent '/home/jovyan' is not a writable location, using a temp directory.
  " using a temp directory.".format(parent))

Executing:  20%|██        | 1/5 [00:00<00:03,  1.32cell/s]
Executing:  60%|██████    | 3/5 [02:22<00:43, 21.74s/cell]
Executing:  80%|████████  | 4/5 [02:23<00:15, 15.47s/cell]
Executing: 100%|██████████| 5/5 [02:23<00:00, 11.07s/cell]
Executing: 100%|██████████| 5/5 [02:25<00:00, 29.04s/cell]

test runs pretty well

/approve

Let me know if you need lgtm to merge

@PatrickXYS
Let's merge it

/approve

/lgtm


Why not consider another language outside of dart for Flutter like as NodeJS or Java?

Why not consider another language outside of dart?, for example, like the development of software for android that allows java and kotlin, why don't they allow more languages for Flutter?, for example, one that is more intuitive, that does not require such a high learning curve and that is not so ugly like Dart, for example Java or NodeJs. I don't think that node or java is executed on the host system, but that it serves as a translator of instructions at the time of being compiled just like dart.
Currently there are many people who already know how to develop in nodejs or java, there are already repositories with very modern and old libraries that cover almost all kinds of needs, why reinvent everything by creating a new programming language causing problems for new application developers?
Something similar happens with Kotlin and Go, despite being good languages, they are not convincing or earn a place in the most used programming languages due to their unintuitive and complex learning when you already come from the world of structured development from java or javascript. Why every time Google creates a new technology ends up creating a new language complicating all things? Why doesn't it work on improving what already exists and what people already know instead of making a student who finished learning a language have to spend more years of your life just trying to understand more languages?
Definitely dart is a good language just like go or kotlin, but not giving the option to use a language that is already widely known is cruel for many people.
I open this ticket to propose the option of considering integrating Javascript language (nodejs), Java and/or rust. If you want to create new languages, do it, but give more alternatives please.
Flutter was a very good idea to replace Electron, now that microsoft is planning to kill the project after killing atom editor and integrate microsoft edge in their hybrid apps, but the dart language sucks and there are no better cross-platform alternatives to build native apps for windows, mac and linux since react native does not natively support the creation of applications for linux, although in design I am more convinced by flutter, but the language is a great wall to migrate projects.

duplicate
https://github.com/flutter/flutter/issues/15128
https://github.com/flutter/flutter/issues/15922
https://github.com/flutter/flutter/issues/14382

Hi @yhojann-cl, Considering some of the responses from the flutter team, I believe you should have answers to your question.
https://github.com/flutter/flutter/issues/15128#issuecomment-370222976
https://github.com/flutter/flutter/issues/14382#issuecomment-370938183
Closing as duplicate, in favor of the linked issues

Thanks for the answers, anyway I want to argue why there should be more alternatives to Dart.
Async and await legacy issues
A typical problem is that currently you cannot use await inside a function that is not asynchronous, this problem was fixed in the new version of the ecmascript standard, but dart inherited bad practices with design errors included:

Error: 'await' can only be used in 'async' or 'async*' methods.

Private methods are a patch
It is an object-oriented language but it was not designed to maintain a context between private and public data. For example, like some legacy Javascript problems it is necessary to use special characters to represent properties of class attributes instead of creating native annotations, for example, need use underscore for declare private fields instead of use a single private declaration, but for statics attributes use a static declaration instead of a another special char, like as<EMAIL_ADDRESS> it's ridiculous and a poor solution inheriting from other standards instead of creating your own declarations like any other programming language does, like java.
Using loose package import
Dart uses a manual package import system without any strict structure, which is why it falls into the same problems as old programming languages like ph where each developer created structures as they pleased, this was a problem that php knew how to solve from php7 copying part of php and other stricter languages like python, but dart has stayed in the past allowing messy developments with spaghetti code.
Unintuitive and unsafe class constructors
The creators of Dart have designed a new way to create constructors by saving all the code of a constructor and passing its data, also avoiding the use of getters/setters through get and set properties like c#, but this causes serious problems like those that are reflected when using lombok in Java.
Why did java implement in its recommendations the use of manual getters/setters and constructors for data transfer objects or models like DTO and DAO?, probably this answer is unknown to the maintainers of Dart, since what is sought is to maintain the integrity of the transfer data, being able to apply filtering of input data in setters and output in getters, it also gives the opportunity to create annotation controls additional validation checks, concatenation of multiple streams into setters and the like, but all of this is lost with lombok's automatic getter/setter creation library, something similar to what dart does but in a more aggressive way. It saves a lot of time creating code but at the same time you lose a lot of control over the integrity and security of the data and when creating these controls in dart you end up creating more code than in java and in a more messy way, which is why it is more There are more likely to be security bugs in a development built on dart than on java.
Is Dart the best language for Flutter?
Dart is a language that copied not only the syntax of other languages joining java with javascript, but also copied their problems and did not know how to solve them, instead they applied temporary and obsolete patches which are already being abandoned by their own programming languages. Dart is an unintuitive language with horrible and insecure class construction syntax. Dart may have a lot of performance but it is far from being a programming language on a par with others that already exist. Does anyone know why Go or Kotlin were not used for Flutter, being languages also developed by Google? Being Go the language with good performance and multiplatform? If Google had really considered Go or Kotlin to be good languages, they wouldn't have had to waste time building a new one. Most likely, in a few more years they will manufacture another programming language, forgetting Dart as they are used to doing with their technologies and products.
It's a pity, Flutter is a good project with a good layout, everything that is sought in a modern era, being able to build multiplatform applications natively without duplicating code as was done in the past, when you had to program for internet explorer 6, for firefox , opera and others, you ended up with many projects for a single web page, but the standards came to change that and now google floods us again with more languages that do not contribute anything new, Flutter would be the definitive project if they had used a programming language more common and robust, making use of current standards instead of imposing long learning curves, and then abandoning users to their fate, there is not even official Dart documentation in Spanish or other languages.
The technology doesn't exist yet
I understand that this thread, like others, has been closed and will probably be silenced, I understand that this topic will not reach beyond the eyes of a couple of people, Google is not what it used to be, when it created good projects that benefited people , nowadays they do not feel remorse to unsubscribe services like Google Play Music no matter how many people use it, they do not care if there are still people who use their languages or technologies, in order to advance they are leaving many people behind and many of us are looking for an alternative that thinks of us as people and allows us to develop and create without the fear of running out of support in such a short time, it has already happened with Electron and Dart is not a good option, there are very few options that exist, despite of living in the year 2022 there is still no technology that allows us to program in a calm and confident way in a good multiplatform language for desktop and mobile systems in a robust way ta, safe and with a good design, today we are almost forced to develop on multiple platforms with multiple frameworks to create a single solution and Flutter was a good idea but poorly executed. Now we have to wait for some other project to appear that can give us that environment.
While Microsoft is desperately fighting to sink cross-platform projects so that Windows sales do not decline, while Oracle continues to buy open source projects to destroy them so that they do not stop selling their products, we are waiting for a company that thinks in us as people and in the diversity of systems in a universal way, unfortunately that era has not yet arrived, but it will come.

@yhojann-cl Closing an issue doesn't mean that your request is being ignored, it's just not practical to do something that you are proposing at this time, since flutter works with limited resources. That also doesn't mean Dart is a perfect language. No framework or SDK or language is perfect, We can only strive to make it better and it is a result of a consistent effort of hundreds of contributors who are helping the flutter ecosystem make better.
If you think Dart or flutter lacks some feature or is not built in a way it should have been you are welcome to file an issue in a dedicated repo, Make a proposal prepare a design doc (if required) and also we welcome pull requests. But if your proposals are way too off (which requires a built-up from the ground) like using a different language. Then I think you should consider this comment https://github.com/flutter/flutter/issues/14382#issuecomment-370938183


support for nested keys?

This is just to initiate a discussion around supporting nested keys. @lukemorales have you seen trpc router examples https://trpc.io/docs/v9/merging-routers? It would be great if we could think about how to support nested and merging keys. Most of the time, people like to organise in a central location.
`

@Shajansheriff thanks for starting the discussion!
I think supporting nested keys is a natural evolution of the package, it will be a fun experiment with Typescript to make that happen.
I really liked the idea of merging the keys, and inspired by that I've got a similar API:

It uses the default key a user provided to create the query scope to populate the fields on a single object.
How does that sound to you?

I feel like providing both APIs (creating smaller scopes and merging into a single one, and creating a single huge factory) will be useful for cases that depend on how people like to structure their code.
I'm thinking createQueryKeys + createMergedQueryKeysFactory (name TBD) will serve people that like smaller files and slices of objects that they can then merge into a big one, and the next step would be to create a createQueryKeysFactory that creates a single huge object


brew install aws-ddbsh fails with cmake fatal errors

Describe the bug
The goal was to install aws-ddbsh on macOs from a pre-built binary as linked from this article
To Reproduce
Steps to reproduce the behavior:

Log in to macOs 14.7 as a non-root user.
Up to date homebrew installation -- homebrew v4.4
Run brew update --> "Already up-to-date."
brew doctor --> "Your system is ready to brew."
Install AWS brew tap  brew tap aws/tap
ddbsh install attempt brew install aws-ddbsh
fatal error occurs "/tmp/aws-ddbsh-20241003-3081-rsvjis/ddbsh/ddbsh/ddbsh.hpp:16:10: fatal error: 'string' file not found
16 | #include " (screenshot of terminal output follows)

Expected behavior
Successful installation of ddbsh package, to be followed by AWS key configuration steps etc.
Desktop (please complete the following information):

OS: MacOS Sonoma 14.7 (23H124)
Browser [chrome, firefox]
macOs Terminal built-in utility v2.14 (453)
cmake version 3.30.4

Additional context
none.

I tried to reproduce this with the latest version of OSX (15) and the same cmake version and I wasn't able to:
❯ sw_vers -productVersion
15.0

~
❯ brew update
==> Updating Homebrew...
Already up-to-date.

~
❯ brew doctor
Your system is ready to brew.

~
❯ brew tap aws/tap

~
❯ brew install aws-ddbsh
==> Fetching dependencies for aws/tap/aws-ddbsh: cmake and aws-sdk-cpp
==> Fetching cmake
==> Downloading https://ghcr.io/v2/homebrew/core/cmake/manifests/3.30.4
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/f753ea54b3e26a109755f3343971fbcab85e9944f43fb130a074afed97fcb601--cmake-3.30.4.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/cmake/blobs/sha256:19ddd00b4b6d7cab
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/20acdb4f924f7385a94a11ecfceeaa21346de342ea5b66bf3047808672af088a--cmake--3.30.4.arm64_sequoia.bottle.tar.gz
==> Fetching aws-sdk-cpp
==> Downloading https://ghcr.io/v2/homebrew/core/aws-sdk-cpp/manifests/1.11.405
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/875ac6cbfac5d9dad3d9f61d2c63087bb3d97c2aef70ace29c4a4b6b461a1d95--aws-sdk-cpp-1.11.405.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/aws-sdk-cpp/blobs/sha256:f47c49fa29
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/9f411f338b561d661110593e6b4d84bd668906a4030837a24ce79f1369ca554b--aws-sdk-cpp--1.11.405.arm64_sequoia.bottle.tar.gz
==> Fetching aws/tap/aws-ddbsh
==> Cloning https://github.com/awslabs/dynamodb-shell.git
Updating /Users/roberto/Library/Caches/Homebrew/aws-ddbsh--git
==> Checking out tag v0.8
HEAD is now at 172de29 added support for on-demand throughput limit
HEAD is now at 172de29 added support for on-demand throughput limit
==> Installing aws-ddbsh from aws/tap
==> Installing dependencies for aws/tap/aws-ddbsh: cmake and aws-sdk-cpp
==> Installing aws/tap/aws-ddbsh dependency: cmake
==> Downloading https://ghcr.io/v2/homebrew/core/cmake/manifests/3.30.4
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/f753ea54b3e26a109755f3343971fbcab85e9944f43fb130a074afed97fcb601--cmake-3.30.4.bottle_manifest.json
==> Pouring cmake--3.30.4.arm64_sequoia.bottle.tar.gz
🍺  /opt/homebrew/Cellar/cmake/3.30.4: 3,424 files, 54.7MB
==> Installing aws/tap/aws-ddbsh dependency: aws-sdk-cpp
==> Downloading https://ghcr.io/v2/homebrew/core/aws-sdk-cpp/manifests/1.11.405
Already downloaded: /Users/roberto/Library/Caches/Homebrew/downloads/875ac6cbfac5d9dad3d9f61d2c63087bb3d97c2aef70ace29c4a4b6b461a1d95--aws-sdk-cpp-1.11.405.bottle_manifest.json
==> Pouring aws-sdk-cpp--1.11.405.arm64_sequoia.bottle.tar.gz
🍺  /opt/homebrew/Cellar/aws-sdk-cpp/1.11.405: 64,181 files, 701.8MB
==> Installing aws/tap/aws-ddbsh
==> cmake -S ddbsh -B build
==> cmake --build build
==> cmake --install build
🍺  /opt/homebrew/Cellar/aws-ddbsh/0.8: 7 files, 747.8KB, built in 16 seconds
==> Running `brew cleanup aws-ddbsh`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

hello @rvamz
thanks for looking into this.
I have resolved the issue by completely removing old versions of Xcode command line tools and installing again at version 16 (I had several older versions installed).
I can now brew install aws-ddbsh and you are welcome to close this issue.
David

Thank Roberto and David.
On Oct 3, 2024 9:05 PM, David Grainger @.***> wrote:
hello @rvamzhttps://github.com/rvamz
thanks for looking into this.
I have resolved the issue by completely removing old versions of Xcode command line tools and installing again at version 16 (I had several older versions installed).
I can now brew install aws-ddbsh and you are welcome to close this issue.
David
—
Reply to this email directly, view it on GitHubhttps://github.com/awslabs/dynamodb-shell/issues/22#issuecomment-2392588808, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFFPV5ABRPZJEQFJPY7A4LZZXLS3AVCNFSM6AAAAABPI647LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSGU4DQOBQHA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Discussion: Reassure v1.0

Reassure seems to have reached level when it can be considered feature complete for it's basic role of measuring React Native / React render performance using RNTL / RTL. The basic workflow for baseline vs current testing proven to be reasonable. The file formats (.perf, output.json) seem to be adequate, esp. including metadata part.
Therefore, I wanted to start a short discussion whether we are ready for v1 or is there something still missing that should be considered essential.
From my perspective:

The recent addition of measureFunction API has left measurePerformance somewhat inadequately named. Therefore, I think we should rename it to measureRender. We can keep measurePerformance with deprecation warning to ease user migration.
The improvements suggested in our issues are nice additions but they do not seem to constitute core features for this tool.

CC: @thymikee @Xiltyn @adhorodyski @jbinda @gedu

If we can find a way to reuse existing integration tests and use them as perf tests, that would be great.
Not sure if someone solved it or have a workaround.
I have more than 1000 tests and want to reuse 50-100 tests as perf test out of those. If we can have a way to automatically convert them in to perf test

Yes, from my side makes sense the rename update and move to 1.0

I’m good with cutting the stable version at this point. It’s fine to keep measurePerformance as an alias for backwards compatibility, no need to deprecate it just yet as it will likely slow down the upgrade.
Once v1 is cut, we can think about next steps for this library and what we want to prioritize.

Reassure v1 has been released! 🎉


merge from template-arlac77-github

.github/workflows/pr_labeler.yml

chore(actions): merge from template .github/workflows/pr_labeler.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.485%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
61

Relevant Lines:
61

💛  - Coveralls


Is this repository still maintained?

Hi,
I’ve read various comments about this, but I haven’t seen any responses from the author (@vassilis-panos ), so I thought I’d ask as well: Is this repository still maintained, or should we start looking for other solutions?
I noticed there is a fork, and it would be helpful to understand if we should consider migrating to it or if any updates are planned.
Thank you

Updated to Core 24.12.0 / Supervisor 24.11.4 and also found this integration is no longer available.  What are the alternatives available?

@TheSimTek https://github.com/litinoveweedle/SmartIR is the fork that many people have moved to. I hope this repo can come back to life, but right now the fork appears to be the only option.

Hi @cmsj ,
also I'm migrating to it.
This repo seems abandoned.
Thank you

Thank you.  Will migrate to the fork.

I could add that the migration to the fork is simple with minimal code change.


turn off/on screen by tapping on it

I do not want the screen to stay turned always on so I wrote following script (and make it a service) to turn on and off backlight screen on touch event.
This works with my 'official' raspberry 7' touch screen.
It also turn off the screen after some time.
Might be nice to integrate something like this and to see if it is possible to stop the steaming all together and not just the screen.
#!/bin/bash
loop_count=0
echo 'start'
while :
do timeout 0.2s evtest /dev/input/event0 > touchscreen_log.txt
        grep -q "type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0" touchscreen_log.txt
        if (($?==0))
        then
                echo 'touch detected'
                power=$(cat /sys/class/backlight/rpi_backlight/bl_power)
                if (($power==0))
                then
                        echo 'turn off display backlight'
                        echo 1 | sudo tee /sys/class/backlight/rpi_backlight/bl_power
                else
                        echo 'turn on display backlight'
                        loop_count=0
                        echo 0 | sudo tee /sys/class/backlight/rpi_backlight/bl_power
                fi
                sleep 1
        fi
        loop_count=$[$loop_count+1]
        if (($loop_count>1000))
        then
                echo 'standby'
                loop_count=0
                echo 1 | sudo tee /sys/class/backlight/rpi_backlight/bl_power
        fi
done

This package is designed as a non-interactive service.  Neat add-on though.
To add service control, just add lines to stop and start the service 'systemctl start displaycameras' and 'systemctl stop displaycameras' to the relevant events (in addition to the screen backlight control).

Yes right. Why I din't think it bu myself ;-)
Thanks for the reply.


Remove legacy theme

See ya legacy theme 👋
should fix #238.

@hakimelek our team still hasn't moved over to new colors. Removing the legacy colors before everyone moves over will break our A/B testing culture :D Let's not merge this in until we make sure at least internally all our teams have moved over to new colors

Codecov Report

Merging #247 into next will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##           next   #247   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        39     38    -1
  Lines       442    411   -31
===================================
- Hits        442    411   -31

Impacted Files
Coverage Δ

src/ThemeProvider.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Segmentation fault (core dumped)

I encounter the same issue regardless of the installation method, whether it's:
Installing via pip install genesis-world, or
Cloning the repository with:
bash
Copy code
git clone https://github.com/Genesis-Embodied-AI/Genesis.git
cd Genesis
pip install -e .
When running the script ik_motion_planning_grasp.py, I consistently get a Segmentation fault error. However, this issue does not occur when executing the script inside a Docker container, where it works perfectly.
Here are the details of my environment:
GPU: RTX 3090
OS: Ubuntu 20.04
cuda: 12.4
I replicated the installation process described in the Dockerfile on my local machine, step by step, but the result remains the same.
I even exported the Python package list from the Docker container and installed the exact same packages in a local virtual environment, yet the segmentation fault persists.
Additionally, I always get the following warning, regardless of whether I run the script in Docker or locally:
[Genesis] [13:21:20] [WARNING] qpos_start exceeds joint limit. Relaxing joint limit to contain qpos_start for planning.
Questions:
Why does the script work flawlessly inside the Docker container but fails with a segmentation fault on my local machine, even with an identical Python environment?
What does the warning message mean, and is it indicative of a potential issue?
Thank you for your help!

I encountered the same problem when running reinforcement learning cases, where I encountered a segmentation fault (core dummy)


Add SSR support

Some components use window in the implementation. Trying to use Reactackle in SSR mode throw an error Window is not defined

https://github.com/bcrumbs/reactackle/issues/99

https://github.com/bcrumbs/reactackle/issues/99


Feature Added(Profile Picture from GitHub) by Cyril Mishra

@CyrilMishra Please post a screenshot User Profile with visible Avatar here


housekeeping: gcloud -> google-cloud

Relates to https://github.com/GoogleCloudPlatform/google-cloud-node/issues/1909
This updates our module dependencies to the latest iteration of datastore and updates any old references of gcloud-node to google-cloud-node.

@stephenplusplus I can't add you as a reviewer, but regardless PTAL

I can't merge since I was booted out of the org! But LGTM. @lukesneeringer

@stephenplusplus is Travis failing because environment variables are available on PRs?

Technically yes, it's just a non-graceful exit because we're in a PR, so it's not supposed to do any actual API talking. Does it pass locally?


fix interviewtime not optional

fix issue with interviewtime not being optional
if interviewtime is not given, command can still be executed and on the addressbook, interviewtime is reflected as "No interviews set"
example input: add cn/Google n/Test p/98765432<EMAIL_ADDRESS>a/311

closes #158
closes #154
closes #109
closes #139

LGTM


Fix message about colour when the app crashes

Fixes #1355.
Currently when the app crashes for whatever reason, in the terminal a message about colour.cyan(...) is not a function appears, when what should be appearing is a message suggesting that the user run npm install to make sure all modules are present.
This PR also adds a test to ensure this regression doesn't happen again. Writing the tests was a real odyssey, although you wouldn't know it from the code I committed in the end... ask me about it sometime!

Tests fail for me locally. Am I missing something?

What's the error you get?


attaching a purged PolicyRoute to an interface that is not purged results in an error

Attaching a PolicyRoute for which purged == true to an interface with purged == false does add the ExtraConfig for the policy to the interface (interfaces <iface> policy route <policy_route_name>). This fails because the policy does not exist: it's config has not been deployed because purged == true. I believe the implementation that adds the ExtraConfig (ifacePolicyRoute) should do so iff self.policy.purged == false.

I think the same goes for attaching a PolicyRouteRule to a PolicyRoute.


GraphId is still used widely in tests and examples.

The deprecated @GraphId should be removed from the majority of tests and examples.
See also #417 .

@GraphID is still used on the example at https://neo4j.com/developer/neo4j-ogm/

Yes, that's sadly true. Paging @lju-lazarevic


Add support for cloud-init Networking Config Version 2

Cloudbase-init already supports networking config format v1 (https://cloudinit.readthedocs.io/en/20.1/topics/network-config-format-v1.html) and the legacy ENI (https://cloudinit.readthedocs.io/en/20.1/topics/network-config-format-eni.html).
Cloudbase-init does not support yet the Networking Config Version 2 (https://cloudinit.readthedocs.io/en/20.1/topics/network-config-format-v2.html).

Hi @ader1990
Could you please close this issue ? It was solved by f0fe66b in release 1.1.5.


Can't connect to TCP server using BAMBOO_TCP_PORT

Im trying to launch a tcp minecraft server and bamboo is either not routing properly or im accessing it wrong.
Here's the relevant parts of the Haproxy.cfg file being generated:
       # This is the default proxy criteria
        acl ::ozzadar-fnbcenre-minecraft-aclrule hdr(host) -i ozzadar-fnbcenre-minecraft.klouds.org
        use_backend ::ozzadar-fnbcenre-minecraft-cluster if ::ozzadar-fnbcenre-minecraft-aclrule

[...]

listen ::ozzadar-fnbcenre-minecraft-cluster-tcp :1080
        mode tcp
        option tcplog
        balance roundrobin

        server ::ozzadar-fnbcenre-minecraft-<IP_ADDRESS>-31394 <IP_ADDRESS>:31394

backend ::ozzadar-fnbcenre-minecraft-cluster
        balance leastconn
        option httpclose
        option forwardfor

        server ::ozzadar-fnbcenre-minecraft-<IP_ADDRESS>-31394 <IP_ADDRESS>:31394

I've tried accessing from both
ozzadar-fnbcenre-minecraft.klouds.org and
ozzadar-fnbcenre-minecraft.klouds.org:1080
Any help appreciated,
Thanks!
-Ozzadar

My feeling is that the ACL is blocking you. Is the protocol on that port HTTP? You might want to try a boolean ACL to say 'anything on this port goes to this backend, regardless of content'.

I don't have much experience with ACLs. Should I check for TCP and just not create the http side of things?
It looks like it tries to give it a TCP and an HTTP connection

I think setting the acl to -m bool true should work. Not sure, never used a boolean ACL before.

Unfortunately, I don't know what you mean here. Do you mean
acl ::ozzadar-fnbcenre-minecraft-aclrule hdr(host) -i ozzadar-fnbcenre-minecraft.klouds.org -m bool true

?
I don't think that could be it because I'd have no idea what that would accomplish :(
(Ive been googling and trying things for an hour now and can't figure it out.)
I noticed the tcp backend is using 'listen' instead of 'backend' and that it's name "appname-cluster-tcp" is not referenced anywhere else in the template.
Like I said, these ACL rules are all kinds of confusing to me. =/

acl ::ozzadar-fnbcenre-minecraft-aclrule -m bool true

nope didn't work :( tried both with and without the -i

Try to remove the hdr(host), a TCP lb should just work with the BAMBOO_TCP_PORT, take look at the marathon config to check that you are using BRIDGED networking and letting marathon assign a random port. If you use HOST networking, mesos will assign a random port that will not be used ,but Bamboo will create the LB using that random ports (which are not really working).
Things to check:

Marathon deploy using BRIDGED networking.
Let marathon assign a random port.
Assign a BAMBOO_TCP_PORT.
It should work just with that.

If that doesn't work, can you access your app using the port assigned by marathon? (The link in the marathon task description).


Can't create desktop session inside Windows Sandbox

I made a powershell script using WinAppDriver, and it works just fine on my regular Windows installation, however I can't seem to make it work inside the new Windows Sandbox (a recent Windows Insider feature)
$desktopOptions = New-Object openQA.Selenium.Remote.DesiredCapabilities
$desktopOptions.SetCapability("app", "Root")
$desktopdriver = New-Object openQA.Selenium.Remote.RemoteWebDriver("http://<IP_ADDRESS>:4723", $desktopOptions)

POST /session HTTP/1.1
Accept: application/json, image/png
Content-Length: 73
Content-Type: application/json;charset=utf-8
Host: <IP_ADDRESS>:4723
User-Agent: selenium/3.14.0 (.net windows)

{"desiredCapabilities":{"app":"Root"},"capabilities":{"firstMatch":[{}]}}
HTTP/1.1 500 Internal Error
Content-Length: 137
Content-Type: application/json

{"status":13,"value":{"error":"unknown error","message":"Failed to locate opened application window with appId: Root, and processId: 0"}}

I'm not able to get the desktop session with the appTopLevelWindow capability. Is there another way to create a desktop session?
EDIT:
After a little more investigation, nothing works inside the sandbox. Applications run without any issue, but WinAppDriver sessions will always fail to locate them with "unknown error". Is there any way to have a more verbose output?

Hi, I've came across the same issue as yourself, did you find a solution to this that didn't involve a coordinate based solution?

No, sorry.


terraform-fmt hook behaviour change

Previously the terraform-fmt hook made changes to the files, whereas now it only shows the difference and errors out. I did some digging and found that it was an intentional change as part of this PR: https://github.com/gruntwork-io/pre-commit/pull/46
It would be nice to have the old behaviour as an option. Generally my terraform files are syntactically valid, but incorrectly formatted, the previous behaviour took away the pain point of needing to run terraform fmt after every change. The differences don't need to be analysed, so there's no need for the --diff --check.
Thanks for providing these hooks, they've been super useful!

A PR to support some sort of flag that enables the old behavior (overwriting the files) is welcome!

A PR to support some sort of flag that enables the old behavior (overwriting the files) is welcome!

@brikis98 do you think the following can solve the problem rather than a flag:
terraform-fmt.sh can run terraform fmt
terraform-diff.sh can run terraform --diff --check

I would agree the changes to format  in  v0.1.12 don't make sense.
If I wanted to know all the errors I would have run lint or validate on the files first. IMHO running format should just auto-correcting issues as the formatter deems fit. It should fail on invalid syntax or logic issues immediately so they can be fixed and need to be re-run, hence why you should validate first if you need to. I don't care about issues it finds regarding spacing, etc that is why I am using the auto-formatter.
Also the diff may matter from the perspective of debugging a CI or a dry-run perspective, but for the default it doesn't. Changes should happen immediately on disk.
I would propose the default behaviour be restored and if you don't want changes made on disk a --dry-run flag be added to the arguments for the hook.

+1 for restoring previous functionality

Yeah at the moment the way to go is to use v0.1.11 in the meantime.
Maybe in the future I can try to implement @skoblenick approach if you guys agree.

@brikis98 I filed a PR that allows for both options via a flag (--no-autofix). I reverted the default behaviour to what used to be in place in v0.1.11 as I thought this is more in-line with other pre-commit hooks (e.g. trailing-whitespace, sort-simple-yaml, end-of-file-fixer).
Obviously we can invert the logic pretty easily if needed, but I'd like to hear your thoughts first!

A PR to support some sort of flag that enables the old behavior (overwriting the files) is welcome!

@brikis98 do you think you can review my PR https://github.com/gruntwork-io/pre-commit/pull/53 ? Thanks!

is this going to be released any time soon? 0.1.17 still does not actually modify the files?

Is there any further thoughts on this behavior being added even as an optional argument?

I found this functionality in another repository:
https://github.com/antonbabenko/pre-commit-terraform?tab=readme-ov-file#terraform_fmt
    - repo: https://github.com/antonbabenko/pre-commit-terraform
      rev: v1.92.2
      hooks:
          - id: terraform_fmt


Parallelize test execution

Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

I think we can close this one since similar changes were done here: https://github.com/open-metadata/OpenMetadata/pull/10064


Success error code when run outside of a Cargo project

There's no error status returned when run without a Cargo.toml of some kind. This is not in line with other cargo subcommands.

I'll hopefully get on it this weekend or early next week :+1:

This has now been implemented and tested. Pushing to master and publishing a new tarpaulin release tonight :+1:


Typo in the install guide README.md

Please fix the small typo in side the
1. Install all requirements for the project using pip install -r ./requirements.text  to `1. Install all requirements for the project using `pip install -r ./requirements.txt :)
Also the numbering does not work

Fixed by https://github.com/PokemonGoF/PokemonGo-Bot/pull/60


Scrollable list in modal view

Thank you for your awesome work. I have one question. I have an model view with an scrollable list within. With disableBodyScroll(document.querySelector("#modalView")); the body is not scrollable but im not able to scroll in the list within the modal. If a add disableBodyScroll(document.querySelector("#scrollableListInModalView")); to the list in the modal, the list is scrollable and the body is also not scrollable, this is fine! But when I scroll, for example on the modal header,  the body starts scrolling. Is there a way to solve this problem ?
Thank you

Nop does not work. But it's okay for me. I thought there would be a simple solution for this problem. But i can live with that.

Hi @SimonKlausLudwig - seems like the current logic is working with just 1 scrollable section on the screen at any one time.
For cases like yours where both modal header and list needs to be scrollable, the logic would need to be re-worked slightly (the refactor seems simple enough).
I'll try to get a PR for you to test if it resolves the issue for you (maybe sometime this week).

Closing due to inactivity (re-open if you feel the need to).


Containers does not appear after creation in My images Tab

Expected behavior

Open Kinematic My Images Tab
Create in console new image
New image appear in list

Actual behavior

Open Kinematic My Images Tab
Create in console new image
New image does not appear in list

New image appear only after relaunch
Maybe some refresh button should be there)

Basically the issue is that creating an image from the command line doesn't dispatch this action. I'm not exactly sure why. Working on that. However, It's interesting to note that pulling an image from the command line does dispatch this action.
In other news, there technically is a refresh button. Clicking the "My Images" tab will reload the image list. Not the greatest UX though.

@mhelmetag thanks for debugging this - It seems to be related to the events dispatched where a build doesn't trigger anything, but a pull would


proxy.golang.org: 400 bad request github.com/tomoyamachi/reg

What version of Go are you using (go version)?

$ go version
go version go1.13beta1 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOHOSTARCH="amd64"
GOHOSTOS="linux"

Ubuntu Disco Dingo, go1.13beta1 downloaded from the Golang site.
What did you do?
go get -d github.com/future-architect/vuls
cd ~/go/src/github.com/future-architect/vuls
  # see that it has a `go.mod` already, so ..
go install

What did you expect to see?
Either a successful build or some kind of build failure
What did you see instead?
A bad request from proxy.golang.org:
go<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>400 Bad Request

I repeated the command, to rule out transient glitch.  I then ran GOPROXY=direct go install which continued past that point to get to a different inscrutable error but one which is more likely tied to the project itself.  Limiting this issue to the observed proxy error.

to get to a different inscrutable error but one which is more likely tied to the project itself

That suggests that the proxy probably should have instead returned a 404 or 410 to prompt the go command to fall back to direct.
CC @hyangah @katiehockman @heschik

If you visit the URL directly you'll see that it says "invalid version". That could be improved, but I don't know how much we should invest in it until #30748 is fixed; odds are nobody will see it anyway.

@bcmills<EMAIL_ADDRESS>is (for better or worse) a pointer to v0.16.1. Do you know why the go command is still reading v0.16.2-0.20190418055600-c6010b917a55.mod? This seems like a variation of the wrong .zip bug that was fixed in 1.13?

@heschik, the validation rule in 1.13beta1 is that the base tag for the pseudo version must be on the commit itself or one of its ancestors, so v0.16.2-0.20190418055600-c6010b917a55.info is an allowed name for that commit.
I suppose we could tighten up that validation so that the base tag must be on some actual ancestor rather than the commit itself. I don't have a solid intuition one way or the other on that (cc @jayconrod).

Hrm, that's odd. I get a different result from what @it-philpennock observed:
$ GO111MODULE=on go1.13beta1 get -d<EMAIL_ADDRESS>go: finding github.com/tomoyamachi/reg v0.16.2-0.20190418055600-c6010b917a55
go: finding github.com v0.16.2-0.20190418055600-c6010b917a55
go: finding github.com/tomoyamachi v0.16.2-0.20190418055600-c6010b917a55
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>proxy returned info for version v0.16.1 instead of requested version

nb: I was installing github.com/future-architect/vuls and tomoyamachi/reg is a dependency of that.

Ah, here we go. I guess we try to download the .mod without bothering with the .info if it's already in the go.mod and go.sum files.
For completeness:
$ GO111MODULE=on go1.13beta1 get -d github.com/future-architect/vuls
go: finding github.com/future-architect/vuls v0.8.2
verifying<EMAIL_ADDRESS><EMAIL_ADDRESS>reading<EMAIL_ADDRESS>410 Gone

$ git clone https://github.com/future-architect/vuls
Cloning into 'vuls'...
remote: Enumerating objects: 24, done.
remote: Counting objects: 100% (24/24), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 5310 (delta 10), reused 16 (delta 8), pack-reused 5286
Receiving objects: 100% (5310/5310), 5.33 MiB | 27.58 MiB/s, done.
Resolving deltas: 100% (3679/3679), done.

$ cd vuls

vuls$ go list all
go<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>400 Bad Request

FWIW, there are other bogus versions mentioned in that same go.mod file:
vuls$ GOPROXY=direct go1.13beta1 list all
go<EMAIL_ADDRESS>invalid pseudo-version: does not match version-control timestamp (2019-06-13T06:46:14Z)

CL 184720 will tighten up the validation so that this pseudo-version is treated as actually-invalid.
However, there remains a bug in the proxy for valid pseudo-versions naming commits that have subsequently had canonical tags applied:
example.com$ go mod init example.com
go: creating new go.mod: module example.com

example.com$ go version
go version devel +fbde753a58 Tue Jul 2 13:52:21 2019 +0000 linux/amd64

example.com$ GOPROXY='' go get -d<EMAIL_ADDRESS>go: finding golang.org/x/text v0.1.1-0.20171213102548-c4d099d611ac
go: finding golang.org v0.1.1-0.20171213102548-c4d099d611ac
go: finding golang.org/x v0.1.1-0.20171213102548-c4d099d611ac
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>proxy returned info for version v0.2.0 instead of requested version

example.com$ GOPROXY=direct go get -d<EMAIL_ADDRESS>go: finding golang.org/x/text v0.1.1-0.20171213102548-c4d099d611ac
verifying<EMAIL_ADDRESS><EMAIL_ADDRESS>reading<EMAIL_ADDRESS>410 Gone

example.com$ GOPROXY=direct GOSUMDB=off go get -d<EMAIL_ADDRESS>1ac
go: downloading golang.org/x/text v0.1.1-0.20171213102548-c4d099d611ac
go: extracting golang.org/x/text v0.1.1-0.20171213102548-c4d099d611ac

Another instance of this error message spotted in the wild, fingers crossed on my part that you've already fixed it with the above?
In github.com/minio/mc a go build hits:
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>400 Bad Request

This is the case Bryan mentioned in https://github.com/golang/go/issues/32879#issuecomment-507861612. We don't know what we're going to do about it yet, but it's on our radar.

@it-philpennock, I just checked go get -d<EMAIL_ADDRESS>and go build ./... within a clone of the same, and they both seem to be working now. (There have been some changes in the proxy configuration in the time since your last comment.)
Are you still observing this issue? If not, I'll close it out.

Works for me now. Thanks.

Closing per last two comments.


[BUG] Fix docker logging on WSL

The problem is that docker logs don't appear (and probably never have) when using exo in WSL.
I spent some time debugging this with John and my understanding of the problem is as follows:
for logging we have three components that need to communicate: the docker daemon, the exo daemon and the syslog daemon. In practice, the exo daemon and the syslog daemon always reside on the same network interface so we can thing of them together as "exo".
On Linux they both run natively on the host. Simple. On MacOS exo runs natively and the docker daemon runs in a VM. In WSL the situation is reversed and the docker daemon runs on the host and exo runs in the WSL VM.
The problem appears to be that UDP packets aren't forwarded from the Windows host, where the docker daemon is running, to the WSL VM in which exo is running. I can't find any documentation about this but I can find multiple people on the internet complaining that this is a limitation of WSL[0].
I can't really see a solution that doesn't involve either swapping away from UDP or giving up on WSL support.
[0] Complaining people:
https://old.reddit.com/r/bashonubuntuonwindows/comments/klxbzv/wsl_win10_udp_data_transfer/ghdvj7z/?context=3
https://old.reddit.com/r/bashonubuntuonwindows/comments/fzauf2/win_ubuntu_wsl2_udp_recieve_issue/
https://github.com/MicrosoftDocs/WSL/issues/950
https://github.com/microsoft/WSL/issues/4825
https://stackoverflow.com/questions/66296434/pod-udp-hostport-not-working-in-docker-desktop

Switching from UDP to TCP is problematic because the Docker daemon fails if connections can't be established, and then does not reconnect if the connection is severed. This means that upgrades or other interruptions of the syslog server will cause all logging to stop working. Though, upgrades already run the risk of losing messages with UDP, it would be nice to use something more reliable.
One option is that we can do our own log forwarding process, just like we do for unix processes. Let Docker talk TCP or some other protocol to that, then we forward it along UDP to our syslog server. If we basically just do the simplest possible Syslog forwarder service, we can probably get away with it, but I don't love the idea of extra processes to manage/consider.
There is also some kind of log buffering "dual logging" system in the more recent docker engine. I think we can query/replay recently buffered logs, so we could also create a forwarding system that works that way, instead of overriding the logging driver.
Alternatively, we can explore proper Windows support, abandoning WSL, though I think that might actually be a step backwards for most Windows users, as far as I can understand.
This thread does seem to suggest UDP should work: https://old.reddit.com/r/bashonubuntuonwindows/comments/fzauf2/win_ubuntu_wsl2_udp_recieve_issue/
@BenElgar What do you think?


kind: Use <IP_ADDRESS> instead of <IP_ADDRESS>

Use <IP_ADDRESS> instead of <IP_ADDRESS> as the forward DNS server. This has worked better on local testing, let's see if CI is happier with this.

/test

just checking - as this PR was from Jarno's fork, are we confident that the CI actually tested the change?


Clean up cancel loops

let's remove the cancel macro - pull the loop body to a function and simplify logic

Think I already handled this


Fix typescript-resolvers doc

Perhaps you should squash all 3 commits into a single one

Thank you @aryzing !


Bump lib versions 2022 10 17 051754

GitHub Issue
bumping lib versions
Changes
see commits
Packages Added
N/A
Checks
Before making your PR, please check the following:

[ ] Critical lint errors are resolved
[ ] App runs locally
[ ] App builds locally (run the build command for any impacted package and check for any errors before the PR)

so we are going to want to regular merge this (not squash and merge)


Fix delta history array length

This PR

Fixes a bug

Describe the changes below:
The length of the deltaHistory array in TimeStep is meant to be deltaSmoothingMax (e.g. every for loop iterating over this array does deltaSmoothingMax iterations), but deltaIndex is only reset to 0 once it reaches deltaSmoothingMax, which effectively extends the array's length to deltaSmoothingMax + 1
For example, with deltaSmoothingMax set to the default value of 10, you'll find that the deltaHistory array eventually contains 11 elements instead of 10

👍


ModuleNotFoundError

The error occurred on model/transformers/init.py
ModuleNotFoundError   No module named 'model.transformers.data'

The error occurred on model/transformers/init.py
ModuleNotFoundError No module named 'model.transformers.data'

Hey,
did u solved that issue?
If, yes can u let me know how u solved it.

Those files are from huggingface transformers. These missing files are actually not used but if necessary you should be able to just copy from the official repo.


ffmpeg: enable vulkan in small variant

Closure size: 493.6M -> 494.8M
Fixes https://github.com/NixOS/nixpkgs/issues/281631
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

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

Hm, hold on I'm getting this error for some reason:
[AVHWDeviceContext @ 0xdde280] Unable to open the libvulkan library!
Device creation failed: -1313558101.
Failed to set value 'vulkan=vk:0' for option 'init_hw_device': Unknown error occurred
Error parsing global options: Unknown error occurred

It works in ffmpeg-full of the same revision.

It does work when you also enable libplacebo? Is that a requirement for VK somehow @Tungsten842?

While trying vulkan videgoo
I am not sure if this is caused by the fact that this is based on staging.
[AVHWDeviceContext @ 0x1a09280] Unable to open the libvulkan library!
Device creation failed: -1313558101.
Failed to set value 'vulkan=vk:0' for option 'init_hw_device': Unknown error occurred
Error parsing global options: Unknown error occurred

It does work when you also enable libplacebo? Is that a requirement for VK somehow @Tungsten842?

It does work when you also enable libplacebo? Is that a requirement for VK somehow @Tungsten842?

It doesn't seem so: https://github.com/FFmpeg/FFmpeg/blob/8e23ebe6f971ec4177be73b453960d83c264b7b5/configure#L3108
Does it work on top of master instead of staging?

It does work when you also enable libplacebo? Is that a requirement for VK somehow @Tungsten842?

It doesn't seem so:
https://github.com/FFmpeg/FFmpeg/blob/8e23ebe6f971ec4177be73b453960d83c264b7b5/configure#L3108
Does it work on top of master instead of staging?

This is based on master/nixos-unstable (c3e128f3c0ecc1fb04aef9f72b3dcc2f6cecf370).

It's apparently not getting linked to the vk loader somehow.

Huh, I followed a hunch and removed vulkan-headers from buildInputs because libplacebo didn't add them and that made it work.

Interesting, it is linked and actually works in ffmpeg_4 but not anything newer.

Opened https://trac.ffmpeg.org/ticket/10809#ticket

Opened https://trac.ffmpeg.org/ticket/10809#ticket

Anyway, can't we just enable libplacebo as well?
Arch enables it.
Fedora enables it.
Debian too.
And it includes a ton of useful filters: https://ffmpeg.org/ffmpeg-filters.html#libplacebo

libplacebo is like +16M closure size.

Would it be possible / appropriate to add this to headless as well?

Could you open a separate issue on this and ping all current maintainers?


SyntaxError: The requested module 'mem-fs' does not provide an export named 'loadFile', SyntaxError: The requested module 'mem-fs' does not provide an export named 'isFileTransform', sharedFs.pipeline is not a function

Type of issue

Hello, I installed yo + generator-code as a dev dependancies by yarn then when ever I try to run npx yo code in the first time I got

import { loadFile } from 'mem-fs';
         ^^^^^^^^
SyntaxError: The requested module 'mem-fs' does not provide an export named 'loadFile'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:131:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:213:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:431:15)
    at async pre (E:\VSCODE Extensions\locales generator\node_modules\yo\lib\cli.js:83:3)
    at async E:\VSCODE Extensions\locales generator\node_modules\yo\lib\cli.js:193:3

So I navigated to mem-fs library to export it and after export it I got the following error

file:///E:/VSCODE%20Extensions/locales%20generator/node_modules/mem-fs-editor/dist/actions/commit.js:1
import { isFileTransform } from 'mem-fs';
         ^^^^^^^^^^^^^^^
SyntaxError: The requested module 'mem-fs' does not provide an export named 'isFileTransform'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:131:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:213:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:431:15)
    at async pre (E:\VSCODE Extensions\locales generator\node_modules\yo\lib\cli.js:83:3)
    at async E:\VSCODE Extensions\locales generator\node_modules\yo\lib\cli.js:193:3

So as a try I tried to remove export it because I couldn't find it in mem-fs so i replaced it by true and the tool is running but after questions and when it comes to the last step to generate the files I got that error

Writing in E:\VSCODE Extensions\locales generator\localesgen...
Error code

sharedFs.pipeline is not a function

Please release a new update to fix those issues

My environment

OS version/details: Windows 10 64-bit
Node version: 20.9.0
yarn version: 1.22.21
Version of yo : 5.0.0

Expected behavior

Just run and ask the questions then generate the files

Current behavior

Just a collection of errors

Also tested on the following without success:

OS version/details: Alpine, Debian bookworm
Node version: 18.19.0, 20.9.0
yarn version: 1.22.21, 4.0.2
Version of yo : 5.0.0

Switching to using npm resolves the issue so I'm not sure why it is failing with yarn. Not sure, but this might also be related to https://github.com/yeoman/yo/issues/800.

It's failing even with pnpm. Again, switching to npm resolves the issue.

Figure out where is your global node_module, for example, I am using yarn
Now step all is in global node_module

Step: here is something to check

Open mem-fs-editor -> package.json to check peerDependencies
👇

open mem-fs -> package.json to check current lib version

Go to the up level of the global node_module folder

yarn add mem-fs
npm install mem-fs

If use pnpm, you may check same & install as this

Then you can check installed mem-fs version also
Now try to use yo


FancyZones no longer allow snapping elevated (admin) applications

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.657]
PowerToys version: 0.15.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Create zones.
Launch elevated process (e.g. Win+X > Windows PowerShell (Admin))
Hold Shift and drag the window into the zone.

Expected behavior
Window snaps to the zone.
Actual behavior
Window does not snap to the zone.
Notes
This used to work before updating to 0.15.1. I believe the previous version I was on was 0.14.1.

It works OK if PowerToys are launched elevated too. Did the mode PT launch in as the default changed between the versions?

@LukaszMendakiewicz
yes, the default has changed.
You can set it back to the old behavior using the general settings option "Always run as administrator".

Thanks for clarifying. The release notes do mention:

Removed requirement to always 'run as admin'

But I don't think it communicates clearly enough that the default changed from running as admin to not, and it can affect the observed behavior.

We are planning to add a notification when we detect that an elevated window is moved while PT is running non elevated. We just didn't have the time to do it in 0.15.x

#1015 is the tracking issue, going to close this since we are tracking there.  @LukaszMendakiewicz it is better for us to take this route so we aren't always running elevated (also most people don't use elevated processes (but we 100% know this is a scenario we must support))


Add interface type to represent core stager run

Probably we can reduce the number of functions from the interface but this one is analogous with the current behavior for now /cc @krobertson @jpoler

LGTM. One note about a few general nits.

Rebased and addressed nits, thanks!


Add command to get hat decorations

What is this

Client application need to know the current state of the editor hats.
Currently the only way to retrieve the hat decorations is to monitor the vscode-hats.json file watching for changes.
This change allows the hats to be retrieved from Cursorless via a command.
This will allow better performance and reduce complexity as on issuing a command the state of the hats can be retrieved.

Not ready for merge.


Don't fail if the app can not init Firebase

but log a warning in logs
Solve #192
How to test

You may need to run flutter clean to remove existing Firebase files
On iOS and Android, try to launch without the file:

ios/config/<flavor>/GoogleService-Info.plist or
android/app/src/<flavor>/google-services.json
The app should work, but a warning should be logged

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 54.71%. Comparing base (cddfd38) to head (e6193e4).

Files
Patch %
Lines

lib/tools/logs/logger.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #356   +/-   ##
=======================================
  Coverage   54.71%   54.71%
=======================================
  Files         168      168
  Lines        3670     3670
=======================================
  Hits         2008     2008
  Misses       1662     1662

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

This does not work on Android.
I get the following error when trying to launch Titan on Android without the google-services.json :
* What went wrong:
Execution failed for task ':app:processDevDebugGoogleServices'.
> File google-services.json is missing. The Google Services Plugin cannot function without it.


Docs links from CRMScript intellisense are broken

When opening a Docs links from the CRMScript intellisense, they are all redirect to the homepage (so 404).
Example:

Tested on sod.superoffice.com, SuperOffice CRM Online 10.1 Build Release_10.1.4_2022.06.08-01

Register as bug ID 29551.

This bug is solved, and SOD now has the correct links again, will be in production soon.


Carthage support

ConsitencyManager is best paired with 🚀 Data (which does support Carthage), but it would be great if folks could consume the framework directly via Carthage.

It looks like CM already supports Carthage 😄