[Enhancement][Chart Name]

No OpenId configuration  openid_auth_domain with default helm deployment config
I install the helm chart from this repo on which I would like to configure  open-id (keycloak) as auth domain as it is mentionned in the official doc: https://opensearch.org/docs/latest/security-plugin/configuration/openid-connect/
But this config doesn't seem to appear in the cluster-master pod deployed :opensearch-cluster-master-0  as I only get:

kerberos_auth_domain:
basic_internal_auth_domain:
proxy_auth_domain:
jwt_auth_domain:
clientcert_auth_domain:

Solution
I know there is something to do with the following config map in values.yaml that creates a secret for security config:
l. 314

securityconfig:
data: {}
# config.yml: |-

As in https://github.com/opensearch-project/helm-charts/issues/125#issuecomment-981804970
My question is: Is there a way to pass the open-id config as such and disable internal_auth in deployment:
set internal_auth_domain enabled to false and:

openid_auth_domain:
http_enabled: true
transport_enabled: true
order: 0
http_authenticator:
type: openid
challenge: false
config:
subject_key: preferred_username
roles_key: roles
openid_connect_url: https://keycloak.example.com:8080/auth/realms/master/.well-known/openid-configuration
authentication_backend:
type: noop

Thank you for your time.

Hey @Foglia-m, looks to me like this goes with config.yml, you can pre create a secret that has config.yml and try passing in to configSecret .

Hello @Foglia-m any luck with you issue ?
I'm trying to set up OIDC too but it seems to me that I can't update config.yml properly with the Helm chart... I tried mounting a secret an add it to securityConfig.configSecret, i tried securityConfig.config.data, I even tried to change the path of securityConfig to /usr/share/opensearch/config/opensearch-security/, but nothing seems to do the trick.
I deleted reference to basic_internal_auth_domain and still can login to dashboard with basic auth...


Reserve IP subpool for a site

Describe the bug
I have been using the suggestion given when I've opened issue: https://github.com/cisco-en-programmability/terraform-provider-dnacenter/issues/70
However since version 1.0.8, it is no longer working. I've tested it with both 1.0.8-beta and 1.0.9-beta.
I get the following errors:
tf_log_debug.txt
It is working fine with version 1.0.7-beta and below.
Is there now a different way to do this or is it a bug ?
Environment (please complete the following information):

Cisco DNA Center version and patch:  <IP_ADDRESS>
Terraform version: 1.2.1

Hi @artur-tekieli , could you pass your tf_file please?

ip_pool_reserve.tf.txt

@artur-tekieli , thanks for report, in version 1.0.10-beta bug should be solved, try it a update us please.


Design & Implement a toast redirect message

"Create an interstitial page to be shown the first time a user is redirected to smooth out the experience for both firecloud app redirect and forums."
Engineering:

We can detect the first time that a user visits firecloud.terra.bio and show them a welcome message/page. Likely using local storage.

Dependencies:

Visual Design
Product decision on how this will work.

Open Questions:

Can we use Rex response to help with this?

What if this was on the firecloud.org pages so whenever a user went directly there, we reminded them what was happening. Then we wouldn't have to store state. We rely on the user's behavior of going to the other place vs the new place. Thoughts?

Talking with the team, we want this to be a toast notification, so it's not as annoying as an interstitial, that links out to some nice documentation. We want this to be connected to the redirect query parameter, so users see it when they've been redirected.
Brad will talk with Robert M to get text

We should also strip off the query parameter after we get it.

The notification should time out after 30 seconds

the query parameter in question is fcredir=1, e.g. https://bvdp-saturn-dev.appspot.com/?fcredir=1#workspaces

Coming out of the soft redirect new AC:
Redirected users see a notification welcoming them to the new UI. This notification should tell users that they can optionally revert to the classic FireCloud UI, via a link in the left-hand nav.
AC:
The notification should indicate that the legacy version will be available until “August 2019” with a link to the blog post that will explain more
This notification should allow the user to navigate the Terra site while it is displayed
It should persist until the user dismisses it.

@bradtaylor thoughts on wording and other suggestions?


How to create schema dynamically with realm?

Hi guys, I'm looking for a way to create schema dynamically with realm.
I want to create many tables with different names but same schema, like conversation data with different users in different tables. I tried to create subclass at runtime but it didn't work well.
I wonder is there a way to do it with realm?
Thank you very much!

Hey @zhaoxy2850, thanks for reaching out about this. We don't have any public support for creating schemas at runtime at this time but I recommend reading through this issue.
As suggested by @bdash in #4811, if you want to rely on Realm internals (which are subject to change at any time), you could likely use -[RLMRealmConfiguration setCustomSchema:] and then pass the RLMRealmConfiguration instance with the custom schema configured on it to +[RLMRealm realmWithConfiguration:error:]. You can see examples of this in our unit tests.
If you have any further questions, please feel free to ask and we'll try to help where possible.

@istx25 Thanks, I will try it.

@istx25 I have tried your method. But it seems that “customSchema”  is a readonly property. I'm sure  that my realm is the latest version. I wonder how to deal with it.
        RLMRealmConfiguration *config = [RLMRealmConfiguration defaultConfiguration];         config.fileURL = [NSURL URLWithString:path];         config.readOnly = NO;         RLMSchema *schema = [[RLMSchema alloc] init];         [config setCustomSchema:schema];
error :  No visible @interface for 'RLMRealmConfiguration' declares the selector 'setCustomSchema:

Hey @istx25,
I am trying to do the same, anyway, to solve that issue you need add:
#import <Realm/RLMRealmConfiguration_Private.h>

At that point you have the customSchema property available.


Advanced Layout test stutters when new items are added in the list

To reproduce, run the Advanced Layout test in /dev/benchmarks/complex_layout and scroll up and down the list.

This appears to be a problem in the compositor when caching a texture for a list item.  For some reason, that takes something like 10 frames.

If you disable the raster cache (i.e., set RASTER_CACHE to 0), the scrolling is much smoother.

Is this still an issue?

Closing since this doesn't seem to be a problem on the latest master 1.22.0-10.0.pre.385.

flutter doctor -v
[√] Flutter (Channel master, 1.22.0-10.0.pre.385, on Microsoft Windows [Version 10.0.19041.508], locale en-US)
    • Flutter version 1.22.0-10.0.pre.385 at C:\Development\flutter_master
    • Framework revision 73b6398932 (4 hours ago), 2020-09-28 11:07:32 +0800
    • Engine revision 3a73d073c8
    • Dart version 2.11.0 (build 2.11.0-161.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at C:\Users\marku\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.6.5)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.6.30320.27
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.0)
    • Android Studio at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\193.6626763
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] Connected device (6 available)
    • SM G950F (mobile)           • ce12171c51cc001c03 • android-arm64  • Android 9 (API 28)
    • sdk gphone x86 arm (mobile) • emulator-5554      • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)           • windows            • windows-x64    • Microsoft Windows [Version 10.0.19041.508]
    • Web Server (web)            • web-server         • web-javascript • Flutter Tools
    • Chrome (web)                • chrome             • web-javascript • Google Chrome 85.0.4183.121
    • Edge (web)                  • edge               • web-javascript • Microsoft Edge 85.0.564.51

• No issues found!


TTS Pronunciation Corrections Editor

An editor similar to ACT's TTS options would be amazing, see an example of this below that corrects the pronunciation of 'Regen' when it's cast on me.
Just a tab that lets users input text to match, and it's corrected pronunciation.

Duplicate of #63, but it's good to hear that other people are thinking about this too 😄

And now I understand what those Lexicons are ha - thank you!

And now I understand what those Lexicons are ha - thank you!

Yeah the fix for character names and Locations is in one file, and miscellaneous is just a fix on general words.


Constant name "hashes" doesn't conform to UPPER_CASE naming style

https://github.com/lbonanomi/gRist/blob/0bb7eceee04bd597966217117892ae3e98250892/grist.py#L26

Issues for naming style are now ignored.


ignore JetBrains WebStorm IDE config folder

Ignore the .idea folder to avoid tracking changes as a result of using the JetBrains WebStorm IDE.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Just as a note, you should always include your IDE's temporary files in your global gitignore for your git user.
See: https://help.github.com/articles/ignoring-files/

Thanks! Great tip and noted (I didn't know that!)


HDDS-9932. Compose annotation for tests parameterized with ContainerTestVersionInfo

What changes were proposed in this pull request?
ContainerTestVersionInfo is used in several classes to parameterize test methods.  The goal of this change is to reduce code duplication by defining a composite annotation.
(Will create follow-up tasks for other similar common parameter types.)
https://issues.apache.org/jira/browse/HDDS-9932
How was this patch tested?
Tests changed by this PR were executed normally (no change in test count, etc.).
Before:
Tests run: 136, Failures: 0, Errors: 0, Skipped: 8, Time elapsed: 13.51 s -- in org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.915 s -- in org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestDeleteBlocksCommandHandler
Tests run: 56, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 20.63 s -- in org.apache.hadoop.ozone.container.common.TestBlockDeletingService
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.429 s -- in org.apache.hadoop.ozone.container.common.TestKeyValueContainerData
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.279 s -- in org.apache.hadoop.ozone.container.common.TestStaleRecoveringContainerScrubbingService
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.321 s -- in org.apache.hadoop.ozone.container.keyvalue.impl.TestBlockManagerImpl
Tests run: 177, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 46.47 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainer
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.134 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerCheck
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.250 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerMarkUnhealthy
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.854 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerMetadataInspector
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.85 s -- in org.apache.hadoop.ozone.container.ozoneimpl.TestContainerReader
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.389 s -- in org.apache.hadoop.ozone.container.ozoneimpl.TestOzoneContainer

After:
Tests run: 136, Failures: 0, Errors: 0, Skipped: 8, Time elapsed: 14.63 s -- in org.apache.hadoop.ozone.container.common.impl.TestContainerPersistence
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.825 s -- in org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestDeleteBlocksCommandHandler
Tests run: 56, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 21.34 s -- in org.apache.hadoop.ozone.container.common.TestBlockDeletingService
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.335 s -- in org.apache.hadoop.ozone.container.common.TestKeyValueContainerData
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.658 s -- in org.apache.hadoop.ozone.container.common.TestStaleRecoveringContainerScrubbingService
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.310 s -- in org.apache.hadoop.ozone.container.keyvalue.impl.TestBlockManagerImpl
Tests run: 177, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 48.81 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainer
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.884 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerCheck
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.064 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerMarkUnhealthy
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.305 s -- in org.apache.hadoop.ozone.container.keyvalue.TestKeyValueContainerMetadataInspector
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.66 s -- in org.apache.hadoop.ozone.container.ozoneimpl.TestContainerReader
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.223 s -- in org.apache.hadoop.ozone.container.ozoneimpl.TestOzoneContainer

CI:
https://github.com/adoroszlai/ozone/actions/runs/7223199990

Thanks @hemantk-12 for the review.


Should we support a ?? operator as a replacement for the coalesce function?

If we don't do this before ~0.3, it becomes much harder to remove the coalesce() function

Shouldn't this be added to 0.3 milestone?

Shouldn't this be added to 0.3 milestone?

I'll put it on my todo list :)

I'll put it on my todo list :)

* The operator should be right-associative (right to left) unlike all the other binary operators in Bicep

@majastrz I'm not sure about this. If the ?? operator would be right-associative, it'd mean that in case of:  a ?? b ?? c it'd become a ?? (b ?? c) and therefore first we'd need to evaluate b, if null then c, and finally a. If it would be left-associative, we'd first evaluate a and if it's non-null - we can return it without evaluating b and c.
That said, I think it should be left-associative and after compilation it should be coalesce(a, coalesce(b, c)).

Dropping a note to remember once this is merged - we need to update docs example:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-functions-comparison?tabs=bicep#example

* The operator should be right-associative (right to left) unlike all the other binary operators in Bicep

@majastrz I'm not sure about this. If the ?? operator would be right-associative, it'd mean that in case of: a ?? b ?? c it'd become a ?? (b ?? c) and therefore first we'd need to evaluate b, if null then c, and finally a. If it would be left-associative, we'd first evaluate a and if it's non-null - we can return it without evaluating b and c.
That said, I think it should be left-associative and after compilation it should be coalesce(coalesce(a, b), c) or coalesce(a, coalesce(b, c)), which both will give us proper order of evaluation

Yeah, the result should be the same regardless. What is interesting is that c# does right-to-left for the ?? operator but JS and TS do left-to-right. (I got the original requirement from c#.) I'll consult our compiler design mentors to make sure there aren't any unforeseen consequences with this approach, but I think you're right.

I just ran this template:
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {},
  "functions": [],
  "variables": {
    "input3": [
      [null, null, null],
      [null, null, 1111],
      [null, 1111, null],
      [null, 1111, 1111],
      [1111, null, null],
      [1111, null, 1111],
      [1111, 1111, null],
      [1111, 1111, 1111]
    ],
    "input4": [
      [null, null, null, null],
      [null, null, null, 1111],
      [null, null, 1111, null],
      [null, null, 1111, 1111],
      [null, 1111, null, null],
      [null, 1111, null, 1111],
      [null, 1111, 1111, null],
      [null, 1111, 1111, 1111],
      [1111, null, null, null],
      [1111, null, null, 1111],
      [1111, null, 1111, null],
      [1111, null, 1111, 1111],
      [1111, 1111, null, null],
      [1111, 1111, null, 1111],
      [1111, 1111, 1111, null],
      [1111, 1111, 1111, 1111]
    ],
    "copy": [
      {
        "name": "coa3",
        "count": "[length(variables('input3'))]",
        "input": "[
          equals(
            coalesce(coalesce(variables('input3')[copyIndex('coa3')][0],variables('input3')[copyIndex('coa3')][1] ),variables('input3')[copyIndex('coa3')][2] ),
            coalesce(variables('input3')[copyIndex('coa3')][0], coalesce(variables('input3')[copyIndex('coa3')][1] , variables('input3')[copyIndex('coa3')][2])))]"
      },
      {
        "name": "coa4",
        "count": "[length(variables('input4'))]",
        "input": "[
          equals(
            coalesce(variables('input4')[copyIndex('coa4')][0] , coalesce(variables('input4')[copyIndex('coa4')][1], coalesce(variables('input4')[copyIndex('coa4')][2], variables('input4')[copyIndex('coa4')][3]))),
            coalesce(coalesce(coalesce(variables('input4')[copyIndex('coa4')][0], variables('input4')[copyIndex('coa4')][1]), variables('input4')[copyIndex('coa4')][2]), variables('input4')[copyIndex('coa4')][3]))
        ]"
      }
    ]
  },
  "resources": [],
  "outputs": {
    "out3": {
      "type": "array",
      "value": "[variables('coa3')]"
    },
    "out4": {
      "type": "array",
      "value": "[variables('coa4')]"
    }
  }
}

The result was the following:
Outputs                 :
                          Name             Type                       Value
                          ===============  =========================  ==========
                          out3             Array                      [
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true
                          ]
                          out4             Array                      [
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true,
                            true
                          ]

Now we have proof that associativity of this operator with the coalesce() function implementation doesn't matter. 😊

Now we have proof that associativity of this operator with the coalesce() function implementation doesn't matter. 😊

I think this may well be the most esoteric ARM template deployed to Azure 👏


Please add source map support

I can't get gulp-sourcemap to work with your plugin.
I suppose the reason is that you don't support the gulp-sourcemap plugin:
https://github.com/floridoo/gulp-sourcemaps/wiki/Plugins-with-gulp-sourcemaps-support
Pretty please, with sugar on top - add it.

@joacim-boive this project does support source maps: https://github.com/tracker1/gulp-header/blob/master/index.js#L8


[FluxCD Integration] Update the gitops.kubesphere.io/v1alpha1 CRD to Support FluxCD Application

/kind feature

General Design
File Change

API

pkg/api/gitops/v1alpha2
├── application.go (UPDATE)
├── helmtemplate.go (ADD)
├── constants.go
├── groupversion_info.go
├── groupversion_info_test.go
├── image-updater.go
├── image-updater_test.go
└── zz_generated.deepcopy.go

Controller

controllers/fluxcd
├── git-repository-controller.go
├── application-controller.go (ADD)
├── helmtemplate-controller.go (ADD)

application.go
update ApplicationSpec field like below:
// ApplicationSpec is the specification of the Application
type ApplicationSpec struct {
	Kind    Engine           `json:"kind"`
	ArgoApp *ArgoApplication `json:"argoApp,omitempty"`
	FluxApp *FluxApplication `json:"fluxApp,omitempty"`
}

// constants.go
type Engine string

const (
	ArgoCD Engine = "argocd"
	FluxCD Engine = "fluxcd"
)

and FluxApplication is like below:
type FluxApplication struct {
	Spec FluxApplicationSpec `json:"spec,omitempty"`
}

type FluxApplicationSpec struct {
	Interval    metav1.Duration            `json:"interval"`
	Source      FluxApplicationSource      `json:"source"`
	Destination FluxApplicationDestination `json:"destination"`
	Config      FluxApplicationConfig      `json:"config"`
}

I think a GitOps Application should be better to abstract into three parts [Source, Destination and Config] .
the Source part is a SourceRef link to the FluxGitRepo or FluxHelmRepo we created
type FluxApplicationSource struct {
   SourceRef CrossNamespaceObjectReference `json:"sourceRef"`
}

// use case
// sourceRef:
    // kind: HelmRepository
    // name: podinfo
    // namespace: default

the Destination part:
type FluxApplicationDestination struct {
	KubeConfig *KubeConfig `json:"kubeConfig,omitempty"`
	TargetNamespace string `json:"targetNamespace,omitempty"`
}

and the Config part:
type FluxApplicationConfig struct {
	// the following four fields are the same in both flux Kustomization and flux HelmRelease CRD
	Suspend bool `json:"suspend,omitempty"`
	Timeout *metav1.Duration `json:"timeout,omitempty"`
	DependsOn []meta.NamespacedObjectReference `json:"dependsOn,omitempty"`
	ServiceAccountName string `json:"serviceAccountName,omitempty"`

	// Two Application Type
   	// same as fluxcd spec exclude the above four fields.
	HelmRelease   HelmReleaseSpec   `json:"helmRelease"`
        // same as fluxcd spec exclude the above four fields.
	Kustomization KustomizationSpec `json:"kustomization"`
}

helmtemplate.go
helmtemplate thing is already exist in helmcharts.source.toolkit.fluxcd.io . we can use the same design like this.
example:
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmChart
metadata:
  name: podinfo
  namespace: default
spec:
  interval: 5m0s
  chart: podinfo
  reconcileStrategy: ChartVersion
  sourceRef:
    kind: HelmRepository
    name: podinfo
  version: '5.*'

this helmchart named podinfo is persisted. Because we directly told flux source-controller to create and maintain this thing. But another way to create a helmchart thing is indirectly by creating helmrelease. the flux helm-controller will detect the charts field in the yaml file to create a ephemeral helmchart. the ephemeral helmchart will be deleted when the corresponding helmrelease is deleted.

helmtemplate-controller.go
If we want to reuse the helm chart. We should create a controller to make the information of a helm chart persisted and may create some CRUD operations on it. And argocd application controller also can use the information of the helmtemplate.

application-controller.go
the main job of application-controller is to Reconcile Flux Kustomization and Flux HelmRelease resource.
use case:
the UI will provide Three GitOps Application Type [ Helm | Kustomization | Template ]
the application-controller will first check the kind of engine whether is "fluxcd".

when user choose Helm Type and create a new helmrelease  the helmtemplate-controller will detect the ADD Event of helmcharts.source.toolkit.fluxcd.io emited by the new created helmrelease. Then the helmtemplate-controller will create a  persisted helm chart same as the helm chart that created by the flux-helm-controller. Finally the application-controller will create the normal helmrelease.
when user choose Template Type the application-controller will find the corresponding helmtemplate according to the name. And application-controller will use the info that helmtemplate provided to fill out the helmrelease.spec.chart field then create it. But the flux helm-controller will also create a ephemeral helmchart. It's a little bit weird.

Is that possible to keep using the same version v1alpha1?

Is that possible to keep using the same version v1alpha1?

Sure.

@lxm

We also need to establish a releation between helmrelease and helmchart using labels or annotaions.

when user choose Helm Type and create a new helmrelease the helmtemplate-controller will detect the ADD Event of helmcharts.source.toolkit.fluxcd.io emited by the new created helmrelease. Then the helmtemplate-controller will create a persisted helm chart same as the helm chart that created by the flux-helm-controller. Finally the application-controller will create the normal helmrelease

there's a option that whether user want to save the chartinfo as a template, we need to check this.

In addition, is it possible for us to make such a template mechanism for kustomizate

Four use-cases
1. User just wants to create a HelmRelease without saving the information (spec.fluxApp.spec.config.helmRelease.chart) to a Template.
apiVersion: gitops.kubesphere.io/v1alpha1
kind: Application
metadata:
  name: chengleqi-test-application-1
  namespace: my-devops-projecthmhx2
spec:
  kind: fluxcd
  fluxApp:
    spec:
      source:
        sourceRef:
          kind: GitRepository
          name: fluxcd-github-repo
          namespace: my-devops-projecthmhx2
      config:
        helmRelease:
          chart:
            interval: 5m0s
            chart: ./helm-chart
            version: "0.1.0"
            valuesFiles:
              - ./helm-chart/values.yaml
              - ./helm-chart/aliyun-values.yaml
            reconcileStrategy: Revision
          template:
          deploy:
            - destination:
                kubeConfig:
                targetNamespace: app
              interval: 1m0s
              upgrade:
                remediation:
                  remediateLastFailure: true
                force: true
              install:
                createNamespace: true

2. User wants to create a HelmRelease and save the config to a Template.
apiVersion: gitops.kubesphere.io/v1alpha1
kind: Application
metadata:
  name: chengleqi-test-application-2
  namespace: my-devops-projecthmhx2
  labels:
    gitops.kubesphere.io/save-helmtemplate: "true"
  ...

Add the gitops.kubesphere.io/save-helmtemplate: "true" label. It's the only change compare with the first case.
3. User want to create a HelmRelease use Template that saved before.
apiVersion: gitops.kubesphere.io/v1alpha1
kind: Application
metadata:
  name: chengleqi-test-application-3
  namespace: my-devops-projecthmhx2
spec:
  kind: fluxcd
  fluxApp:
    spec:
      source:
      config:
        helmRelease:
          chart:
          # template field reference a template that created before by the name
          template: my-devops-projecthmhx2-chengleqi-test-application
          deploy:
            - destination:
                kubeConfig:
                targetNamespace: app
              interval: 1m0s
              upgrade:
                remediation:
                  remediateLastFailure: true
                force: true
              install:
                createNamespace: true

4. Multi-Cluster Applications
the spec.FluxApp.config.helmRelease.deploy is an array for multi-clusters settings.
apiVersion: gitops.kubesphere.io/v1alpha1
kind: Application
metadata:
  name: chengleqi-test-application-4
  namespace: my-devops-projecthmhx2
spec:
  kind: fluxcd
  fluxApp:
    spec:
      source:
        sourceRef:
          kind: GitRepository
          name: fluxcd-github-repo
          namespace: my-devops-projecthmhx2
      config:
        helmRelease:
          chart:
          # template field reference a template that created before by the name
          template: my-devops-projecthmhx2-chengleqi-test-application
          deploy:
            - destination:
                kubeConfig:
                  secretRef:
                    name: stage-kubeconfig
                targetNamespace: app
              valuesFrom:
                - kind: ConfigMap
                  name: stage-settings
              values:
                clouds:
                  provider: qingcloud
              install:
                remediation:
                  retries: 3
            - destination:
                kubeConfig:
                  secretRef:
                    name: prod-kubeconfig
                targetNamespace: app
              valuesFrom:
                - kind: Secret
                  name: dbpass
              values:
                clouds:
                  provider: aliyun
              upgrade:
                remediation:
                  remediateLastFailure: true
                force: true
              interval: 1m0s


[FEAT] Support Ticket Acknowledgment (resolved)

Description
When a support ticket that is already opened and acknowledged on the website is resolved, the user should be informed.
Acceptance Criteria
Support Ticket Acknowledgment:

A user opens a support ticket on the website.
The ticket is acknowledged by the support team.

Ticket Resolution:

The support team resolves the ticket.
The user is informed about the resolution.

Notifications:

Users are notified when their support ticket has been resolved.
Users are informed if there are any issues with their ticket resolution.

Purpose
The purpose of the support ticket resolution notification feature is to:

Ensure users are informed about the status of their support tickets.
Enhance user satisfaction by providing timely updates on ticket resolution.

Requirements
Ticket Model:

user_id: Integer, required
ticket_id: Integer, required, unique
status: String, required (open, acknowledged, resolved)
description: Text, required

Database:

Store ticket data including user ID, ticket ID, status, and description.

Expected Outcome

[ ] Users receive a notification email upon ticket resolution.
[ ] Users can view the status of their ticket on the website.
[ ] The system handles unresolved tickets gracefully.
[ ] Users receive appropriate notifications regarding the status of their support ticket.

Endpoint: GET API/v1/resolve-ticket
Description: Marks the user's support ticket as resolved using the ticket ID provided.
Response:
Status code: 200 OK
{
  "message": "Support ticket resolved successfully."
}

Status code: 400 Bad Request
{
  "error": "Invalid or unresolved ticket."
}

Status Code: 409 Conflict
{
  "error": "Ticket already resolved."
}

We are not building a ticketing system


[REVIEW] Skylar "The Help-Mate"

Project link
https://github.com/Jas-Script/Skylar_TheHelpMate

Looks great, here are some suggestions https://www.youtube.com/watch?v=iqIFD02OkVE

Great you have a code of conduct but the file name is incorrect as doesn't appear on the community insights page
Repo doesn't have a description
Hide packages and releases if not used
Add issue and pull request templates


Support print

This PR was successfully deployed to production by CircleCI build 354 at 2017-11-10 11:36 GMT.


Containerization of the Django application

Summary | Résumé
Created containerization for the Django application. The application now runs in a devcontainer. Additionally, I added a containerized Postgres database that will be the primary database of the application.
Closes #4

Sylvia and I paired on this one and ended up using the default generator to build the templates


In the UI as built from master on March 6, saving a new workitem sets the type to planner (aka the question mark)

See attached screenshot - to recreate:

Create a new workitem of type other than planner
Save the workitem

Closing as out of date - no longer an issue.


Is node-webcrypto-ossl a dependency still?

index.mjs imports node-webcrypto-ossl which is not listed in package.json. However, from your logs it seems you intended to remove this in favour of @peculiar/webcrypto. Should one of these things be fixed?

Thanks for finding this! I'm surprised nobody hit this since Sept. It's fixed in 2.3.5.

Thank you! Could you please also add an engines property to package.json, since @peculiar/webcrypto is meant for node 10 and above.


Index with name namespace does not exist

What did you do?
I deployed the operator using the kube-prometheus manifests generated from ksonnet. I made no changes to the config.  Under which circumstances?
I keep having these in the logs :
prometheus-operator-8564487f49-fk4q5 prometheus-operator level=info ts=2018-07-25T13:08:23.178607644Z caller=operator.go:737 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
prometheus-operator-8564487f49-fk4q5 prometheus-operator W0725 13:08:23.178702       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
prometheus-operator-8564487f49-fk4q5 prometheus-operator W0725 13:08:23.233926       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
prometheus-operator-8564487f49-fk4q5 prometheus-operator W0725 13:08:23.335822       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist

Environment

Prometheus-Operator
Prometheus-Operator image quay.io/coreos/prometheus-operator:v0.22.2
(also tried with quay.io/coreos/prometheus-operator:master with the same issue)

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T22:30:22Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.6-gke.1", GitCommit:"cb151369f60073317da686a6ce7de36abe2bda8d", GitTreeState:"clean", BuildDate:"2018-04-07T22:06:59Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

GKE 1.10.5-gke.3
Comments
This issue may be related to https://github.com/coreos/prometheus-operator/issues/823#issuecomment-407743185

With https://github.com/coreos/prometheus-operator/pull/1697 merged I am closing here. Let me know if you are facing any further issues with this. Thanks for reporting!

I had the same problem.
[root@pre-k8s-master001 grafana]# kubectl logs  prometheus-operator-68575f45f7-8qtdg -n monitoring
ts=2019-02-19T06:30:19.735142713Z caller=main.go:116 msg="Starting Prometheus Operator version '0.22.1'."
level=info ts=2019-02-19T06:30:19.837633185Z caller=operator.go:294 component=prometheusoperator msg="connection established" cluster-version=v1.9.7
level=info ts=2019-02-19T06:30:19.837939772Z caller=operator.go:174 component=alertmanageroperator msg="connection established" cluster-version=v1.9.7
level=info ts=2019-02-19T06:30:20.228156591Z caller=operator.go:564 component=alertmanageroperator msg="CRD updated" crd=Alertmanager
level=info ts=2019-02-19T06:30:20.263576592Z caller=operator.go:1145 component=prometheusoperator msg="CRD updated" crd=Prometheus
level=info ts=2019-02-19T06:30:20.273001148Z caller=operator.go:1145 component=prometheusoperator msg="CRD updated" crd=ServiceMonitor
level=info ts=2019-02-19T06:30:20.33107803Z caller=operator.go:1145 component=prometheusoperator msg="CRD updated" crd=PrometheusRule
level=info ts=2019-02-19T06:30:23.231197005Z caller=operator.go:190 component=alertmanageroperator msg="CRD API endpoints ready"
level=info ts=2019-02-19T06:30:23.234017177Z caller=operator.go:400 component=alertmanageroperator msg="sync alertmanager" key=monitoring/main
E0219 06:30:23.324927       1 operator.go:276] Sync "monitoring/main" failed: creating statefulset failed: statefulsets.apps "alertmanager-main" already exists
level=info ts=2019-02-19T06:30:23.325421564Z caller=operator.go:400 component=alertmanageroperator msg="sync alertmanager" key=monitoring/main
level=info ts=2019-02-19T06:30:23.338583806Z caller=operator.go:400 component=alertmanageroperator msg="sync alertmanager" key=monitoring/main
level=info ts=2019-02-19T06:30:29.346855949Z caller=operator.go:310 component=prometheusoperator msg="CRD API endpoints ready"
level=info ts=2019-02-19T06:30:29.352612732Z caller=operator.go:737 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
W0219 06:30:29.352731       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
W0219 06:30:29.352842       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
W0219 06:30:29.438861       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
level=info ts=2019-02-19T06:30:29.72760105Z caller=operator.go:737 component=prometheusoperator msg="sync prometheus" key=monitoring/k8s
W0219 06:30:29.727687       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
W0219 06:30:29.727779       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist
W0219 06:30:30.331680       1 listers.go:63] can not retrieve list of objects using index : Index with name namespace does not exist

Starting with v0.23.0 this is fixed


Project Crossover Grading

Project Pluto Link
Key Features:

Student Bell Schedule Management: Students can input their school schedule, to see how long is left in each period.
Announcements Page: Students can see announcements posted by authorized users, as they are saved in a database.
Student Planner: Students can save their events in a planner to help manage their tasks. They can create new tasks, view all their tasks, mark tasks as complete, and delete tasks.
Weather w/ clothing advice: Students can see what the weather will be like at school, and recieve clothing advice on what types of clothes to wear for those weather conditions.

Frontend Code
Backend Code
Grading Requirements:
USAGE OF...

[ ] Frontend
[ ] Backend
[ ] API
[ ] Agile

Category
Critera
Grade

Hook
Key features achieved (shown in running demo to graders)
/4

Knowledge
HOW IT IS MADE! Key features blogged (shown in demo time to graders)
/4

Value
Most useful or valuable aspect of project
/1

Bell Schedule Feature (Aniket, Kevin)
Code

Weather API

Login.md:
https://github.com/Soham360/sturdy-fiesta/blob/main/login.md?plain=1

Announcements Frontend:
https://github.com/Soham360/sturdy-fiesta/blob/main/annoucements.md?plain=1

Weather API
https://github.com/DasMoge124/EDNP-BACKEND/blob/master/src/main/java/com/nighthawk/spring_portfolio/mvc/weather/WeatherAPIController.java

Criteria/Key Features:

[ ] Frontend
[ ]  Backend
[ ]  API
[ ]  Database
[ ]  Agile

HOOK:
Points: 3.6-4.0
Reason:
KNOWLEDGE:
Points: 3.6-4.0
Reason:
VALUE:
Points: 0.6-1.0
Reason:
WOW FACTOR:
Reason:

Big Trackta Grading
Criteria/Key Features:

[x] Frontend
[x]  Backend
[x]  API
[x]  Database
[x]  Agile, several students interacting with answering questions.

HOOK:
Points: 3.6-4.0
Reason:
Rachit asked to input schedule, interactive. Applicable to students
3.6
KNOWLEDGE:
Points: 3.6-4.0
Reason:
Shared 2 APIs, talked about classes. API takes a long time to load.
3.5
VALUE:
Points: 0.6-1.0
Reason:
Applicable to students. Very nice!
.8
WOW FACTOR:
Reason:
Useful and applicable to students.
8.9/10

Criteria/Key Features:

[X] Frontend
[X] Backend
[X] API
[X] Agile

HOOK:

Points: 4.0/4.0
Reason: A compelling and highly relevant topic that resonates with a broad audience.

KNOWLEDGE:

Points: 4.0/4.0
Reason: Demonstrated a profound understanding of the implementation of the utilized technologies.

VALUE:

Points: 0.9
Reason: The project, when scaled, holds immense societal and individual value, particularly for those affected by cancer. It was intentionally designed to have a broad-reaching impact.

WOW FACTOR:

Reason: I really appreciate the amount of effort put into engaging the audience.

TOTAL SCORE: 8.9/9

Criteria/Key Features:

[x]  Frontend
[x]   Backend
[x]   API
[x]   Database
[x]   Agile, several students interacting with answering questions.
c

HOOK: Points: 3.6-4.0 Reason: want to make a better Saturn, added schedule 3.7
KNOWLEDGE: Points: 3.6-4.0 Reason: Login, CRUD, Person Class 3.8
VALUE: Points: 0.6-1.0 Reason: weather api is unrelated to other parts of project 0.8
WOW FACTOR: Reason: useful for students
Total score: 8.5/9

Team 1: teacher pet

[x] Frontend
[x] Backend
[x] API
[x] Agile

HOOK: 3.8
Points: 3.6-4.0
Reason:
KNOWLEDGE: 3.9
Points: 3.6-4.0
Reason:
VALUE: 0.9
Points: 0.6-1.0
Reason:
WOW FACTOR:
Reason: 0.9

HOOK: 3.8
Points: 3.6-4.0
Reason: Interesting, planner drew me in as a student and seemed very useful.
KNOWLEDGE: 3.8
Points: 3.6-4.0
Reason: Using API for the weather, CSS/HTML for website, and Javascript for buttons and planner part. Seemed very knowledgable about how different parts worked.
VALUE: 1
Points: 0.6-1.0
Reason: Very valuable as a student, seems like a good tracker for my task and helpful for everyday life.
WOW FACTOR: Good
Reason: I though the planner and weather feature was very useful, though I can check most of this on my laptop or phone. It would be cool to see more interesting, tailored features, such as it deciding a specific outfit with your taste not just giving a general image.
8.6/9

Grader
Grade

Mr. Mortensen
8.1

Grace
8.9

Rohin
8.9

Isabelle
8.55

Mati
9.0

Daisy
8.6

Average: 8.66

HOOK: 3.8
Points: 3.6-4.0
Reason: Fun project, practical use case as well.
KNOWLEDGE: 3.8
Points: 3.6-4.0
Reason: Deep understanding of project and project is well connected.
VALUE: 1
Points: 0.6-1.0
Reason: Valuable as a student, I personally would use this.
WOW FACTOR: Good
Reason: I though the planner and weather feature was very useful, though I can check most of this on my laptop or phone. It would be cool to see more interesting, tailored features, such as it deciding a specific outfit with your taste not just giving a general image.
8.85/9


Creating Cassandra secondary index via the RP

It does not appear that Cassandra secondary indexes can be created using any of the RP utilities - Azure CLI, PowerShell, or ARM/BICEP (Terraform). It would be really helpful to explicitly provide that information on this page or in the Cassandra wire protocol support page.
Thanks

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

ID: c3ede148-5185-9c06-031e-912f7ba20893
Version Independent ID: fc777b48-ece9-8881-20ee-f7e567729049
Content: Indexing in Azure Cosmos DB for Apache Cassandra account
Content Source: articles/cosmos-db/cassandra/secondary-indexing.md
Service: cosmos-db
Sub-service: apache-cassandra
GitHub Login: @TheovanKraay
Microsoft Alias: thvankra

@Craigmeister68 Thank you for your feedback. We will review this and make changes as appropriate.

@craigmeister, I was looking at our documentation and I didn't see any way to create indexes (primary or secondary) at all using the resource providers. My understanding is that we should use CQL to perform that type of task.
Could you elaborate on how this secondary indexing behavior is different than you expected?

@Craigmeister68 as above, secondary indexes can only be created via CQL. Is your feedback that we should explicitly state that they can only be created via CQL in the doc? Or were you asking how to create them via RP utilities?

I was asking for an explicit statement in the doc that secondary indexes can only be created by CQL commands and not through the RP - ARM templates, Azure CLI or PowerShell.

#sign-off

#please-close


Controlled joint number inconsistency

The number of controlled joints can be obtained using:
Scene::getNumJoints()

or
UnconstrainedEndPoseProblem::N
UnconstrainedTimeIndexedProblem::N

The result is the same. Consolidate the calling convention!

Is there a distinction between controlled and uncontrolled joints, and if so, how? (i.e. the scene may contain uncontrolled joints that are externally set [grippers], while the problem should only encompass controlled joints)


Allow customizing the thumb glow radius

This PR adds a new constructor argument, thumbGlowRadius, that sets a custom thumb glow radius.

Your additions look good. Since previous commits create merge conflicts, though,  I'll just add these changes manually.


Figure out why baselines aren't used in unit tests

Deleting the baselines from https://github.com/googleapis/artman/tree/master/test/testdata (with the exception of google-cloud-fake-v1_package.yaml) doesn't cause any tests to fail. I have verified this is true all the way back to commit https://github.com/googleapis/artman/commit/0995314b8003173db52dd156e349c6136c8fa04a (from 18 Apr, 2017). I'd like to figure out if this was intentional or accidental, and if we want to get them working again or just delete them.

This was accidental but I assert it is desirable.
When I did the refactor, I moved this conceptually into tests like this one. This conceptually does something similar, but usually for subsets of the entire thing.
I propose the fix should just be to delete the extraneous files, which are almost certainly a year out of date. (Thanks for catching that!) I do not feel like we are losing anything by not having this.


Waiting: Automate/at least document the process of creating a Force review app

This is definitely a rough cut, but figured something is better than
nothing. Tried to heavily document so that the script so that when
things break, at least devs know the intent here.
Waiting on https://github.com/artsy/force/pull/4379

QA:
TL;DR

took ~11 mins to automate the review app creation process
ran without warning.

As just @joeyAghion, I'll do a couple of tweaks for dev UX, but I think this is actually a well-documented script, and not a runbook.
dl@phoenix:~/src/force * (review-app-setup-for-force)
$ time ./docs/review_app_setup.sh auct-281-automated

NAME="$1"

echo $NAME
auct-281-automated

# Generate the Kubernetes YAML needed to provision the application.
hokusai review_app setup $NAME
Created hokusai/auct-281-automated.yml

# Create the Docker image of your current working direct of Force, and push
# it to Artsy's docker registry.
#
# --force is needed as the current working directory is dirty with (at least)
# the YAML file generated above.
# --skip-latest as we're making no claim that this is the "latest" build of the
# service.
# --tag to name the image.
#
echo "WARNING: This is likely going to take ~10 mins on your MBP."
WARNING: This is likely going to take ~10 mins on your MBP.
echo "Be patient and grab some baby carrots."
Be patient and grab some baby carrots.
hokusai registry push --force --skip-latest --verbose --tag $NAME
==> hokusai exec `docker login -u ****** -p ***** https://585031190124.dkr.ecr.us-east-1.amazonaws.com`

==> hokusai exec `docker-compose -f /Users/dl/src/force/hokusai/build.yml -p hokusai build`

Building force
Step 1/11 : FROM node:10.13-alpine
 ---> 93f2dcbcddfe
Step 2/11 : WORKDIR /app
 ---> Using cache
 ---> baba70a7dbb8
Step 3/11 : RUN apk --no-cache --quiet add       bash       build-base       curl       dumb-init       git       python &&       adduser -D -g '' deploy
 ---> Using cache
 ---> ab4b43ecb0ad
Step 4/11 : COPY package.json yarn.lock ./
 ---> Using cache
 ---> 5e842a765257
Step 5/11 : COPY patches ./patches
 ---> Using cache
 ---> 17e07c2bb132
Step 6/11 : RUN yarn install --frozen-lockfile --quiet
 ---> Using cache
 ---> b185f2ec21d5
Step 7/11 : COPY . ./
 ---> a03a910ef451
Step 8/11 : RUN yarn assets &&     yarn build:server &&     chown -R deploy:deploy ./
 ---> Running in 6f812c66d51a
yarn run v1.10.1
$ NODE_ENV=production yarn build
$ yarn clean && yarn webpack
$ rm -rf .cache && rm -f manifest.json && rm -rf public/assets && mkdir -p public/assets && echo '[Force] Cleaned build directory'
[Force] Cleaned build directory
$ node --max_old_space_size=2048 -r dotenv/config -r @babel/register node_modules/.bin/webpack --config ./webpack
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`

[!] No existing `.cache` directory detected, initial launch will take a while.

Webpack: Starting ...
[Force compileCSS] Compiling...
[Force compileCSS] Complete.

[Force] NODE_ENV=production

[Force] Building client-side production code...
Done in 390.13s.
yarn run v1.10.1
$ BUILD_SERVER=true NODE_ENV=production yarn webpack
$ node --max_old_space_size=2048 -r dotenv/config -r @babel/register node_modules/.bin/webpack --config ./webpack
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`
Webpack: Starting ...

[Force] NODE_ENV=production

[Force] Building server-side code...

Removing intermediate container 6f812c66d51a
 ---> 784fb29f94f0
Step 9/11 : USER deploy
 ---> Running in d861785cd173
Removing intermediate container d861785cd173
 ---> f3a3519da29e
Step 10/11 : ENTRYPOINT ["/usr/bin/dumb-init", "--"]
 ---> Running in 92ee28ead4f2
Removing intermediate container 92ee28ead4f2
 ---> d8048cab4736
Step 11/11 : CMD ["yarn", "start"]
 ---> Running in 311dd2f6d59d
Removing intermediate container 311dd2f6d59d
 ---> 1f9d85663c78
Successfully built 1f9d85663c78
Successfully tagged hokusai_force:latest
==> hokusai exec `docker tag hokusai_force:latest<PHONE_NUMBER>24.dkr.ecr.us-east-1.amazonaws.com/force:auct-281-automated`

==> hokusai exec `docker push<PHONE_NUMBER>24.dkr.ecr.us-east-1.amazonaws.com/force:auct-281-automated`

The push refers to repository [585031190124.dkr.ecr.us-east-1.amazonaws.com/force]
39a9a85cf40a: Pushed
a7ef794a4700: Pushed
4542ca3b11d1: Layer already exists
1738bfe79d08: Layer already exists
b09aebae497a: Layer already exists
164064f9fa87: Layer already exists
8d0b8ee659aa: Layer already exists
2faeaaebb113: Layer already exists
387bc77dd3f2: Layer already exists
df64d3292fd6: Layer already exists
auct-281-automated: digest: sha256:1bc8ed4b10eae8f2b55994e0a508909d99851e3e1df8cdaca020aaa9e904693d size: 2425
Pushed hokusai_force:latest to<PHONE_NUMBER>24.dkr.ecr.us-east-1.amazonaws.com/force:auct-281-automated

# Edit the K8S YAML to reference the proper Docker image
# sed -i '' 's/:staging/:auct-281/g' hokusai/auct-281.yml
#
# The weird `-i ''` is needed on MacOS:
# https://stackoverflow.com/a/44864004
# WARNING: This might not work on Linux.
sed -i '' "s/:staging/:$NAME/g" hokusai/$NAME.yml

# Edit the K8S YAML to remove the instructions that enforce that the service
# can only be accessible via Cloudflare
#
# First, remove the `loadBalancerSourceRanges:` line
sed -i '' '/loadBalancer/d' hokusai/$NAME.yml

# Then, delete all the IP address lines.
#
# WARNING: This is a bit sketchy as this will
# delete any line of the form "- [number][number][number].". This is my best
# approx for an regex for an IP address, and I'm sure that there are better
# ones.
sed -i '' "/- [[:digit:]][[:digit:]][[:digit:]]./d" hokusai/$NAME.yml

# Provision the review app
hokusai review_app create $NAME --verbose
namespace "auct-281-automated" created
deployment.extensions "force-web" created
horizontalpodautoscaler.autoscaling "force-web" created
service "force-web" created
Created Kubernetes environment /Users/dl/src/force/hokusai/auct-281-automated.yml

# Copy Force staging's ConfigMap to your review app
hokusai review_app env copy $NAME --verbose
==> hokusai exec `kubectl --context staging --namespace default get configmap force-environment -o yaml`

==> hokusai exec `kubectl --context staging --namespace auct-281-automated apply -f /var/folders/c1/5m0hqhyn16qgq4lylv00vgv80000gq/T/tmptPxeRl`

# Copy the staging-shared nginx config to your review app
hokusai review_app env copy $NAME --configmap nginx-config --verbose
==> hokusai exec `kubectl --context staging --namespace default get configmap nginx-config -o yaml`

==> hokusai exec `kubectl --context staging --namespace auct-281-automated apply -f /var/folders/c1/5m0hqhyn16qgq4lylv00vgv80000gq/T/tmpalxyRq`

# To enable authentication via Force's server, we need to allow XHR requests
# from Force's client to server. As such, Force's server needs to have the
# proper name of the domain that the requests are coming from. Otherwise,
# authentication requests won't work!
hokusai review_app env set $NAME \
  APP_URL="https://$NAME.artsy.net" \
  COOKIE_DOMAIN="$NAME.artsy.net" \
  FORCE_URL="https://$NAME.artsy.net"

# Now you need to create a CNAME for your review app and wait. This is required
# as Gravity only allows authentication requests from requests of originating
# from the artsy.net domain
echo "Hey you human!"

...
echo "..."
...
echo "..."
...
echo "..."
...
echo "..."
...
echo "..."
...
echo "..."
...
echo "..."
...
echo "..."
...
echo "yeah, I'm talking to you"
yeah, I'm talking to you
echo "you need to configure a CNAME record so that $NAME.artsy.net resolves to" \
     "the service's external IP:"
you need to configure a CNAME record so that auct-281-automated.artsy.net resolves to the service's external IP:
echo $(kubectl get service force-web --namespace $NAME --context staging -o json \
  | jq .status.loadBalancer.ingress[].hostname)
kubectl get service force-web --namespace $NAME --context staging -o json   | jq .status.loadBalancer.ingress[].hostname
"ac157ee03bfae11e9aff2127c3b176f7-175025084.us-east-1.elb.amazonaws.com"
echo "you may do this in the DynDNS interface. Credentials are in 1pass"
you may do this in the DynDNS interface. Credentials are in 1pass

echo "After that, fini. Thank you for review app-ing"
After that, fini. Thank you for review app-ing

exit 0

real    11m40.583s
user    0m9.388s
sys     0m5.530s

This is ready for review.

@eessex @izakp Updated to address most of your comments, but as commented, don't totally understand https://github.com/artsy/force/pull/4412#discussion_r315787578, so didn't address that yet.


Updated documentation to include example section

Added an extra section called example, let me know if anything else is needed to be added or if you would like to move the section elsewhere.

Hi Asim,
I should elaborate better the task. It is not meant to add only an empty title named "Example" in the docs but creating a new live examples like those listed at https://github.com/iusehooks/usetheform#code-sandboxes . Hope it is clearer.
Thanks.

Hi Asim,
I should elaborate better the task. It is not meant to add only an empty title named "Example" in the docs but creating a new live examples like those listed at https://github.com/iusehooks/usetheform#code-sandboxes . Hope it is clearer.
Thanks.


Add schema crawler

Tool

Name
Repository
Author
Project Page

SchemaCrawler
repo
Sualeh Fatehi
web

Reason of Change

[x] New tool to review (please review the tool in the form of a short description in the same CR)
[ ] Verified new tool to merge (I used it already)
[ ] Tool deprecated / no longer maintained
[ ] Tool details changed (project page moved, etc.)
[ ] Repository maintenance

Purpose
I suppose it could help us with the quick PoC and databases review. You connect this to a DB and get schema visualized with all the dependencies. Could be useful in the projects with legacy data.

@mdyzma, we can setup a database only with schema of client DB and empty content - that's what we do already in some cases.


[che] Add test with running workspace with anyuid addon enabled

Need to add test that would cover Unable to start Che workspaces on OCP with 'anyuid' enabled [1]  issue.
Basically, it looks like that starting from 3.7  version of origin pvs are owned by root & root group. It works with arbitary users since it is part of the root group, and the user created in the workspace image (which is used in workspace pod when anyuid is enabled) does not belong to this group and pvc are not writable for this user. The root access for pvc is probably related to the following origin issue [2]. Workaround [3] on che side was adding user to the root group.
The test should do the following

apply anyuid addon
start new workspace
make sure that the workspace has been started successfully

[1] https://issues.jboss.org/browse/CDK-305
[2] https://github.com/openshift/origin/issues/14076
[3] https://github.com/eclipse/che-dockerfiles/pull/198

@agajdosi Can't we just extend https://github.com/minishift/minishift-addons/tree/master/test/integration here for this use case?

@praveenkumar I was thinking the same yesterday, if we agree that we are ok with testing Che addon with anyuid enabled (or maybe all default add-ons enabled) then I can just update current feature file (test). WDYT @ibuziuk

@ibuziuk Thanks for sharing this information, reasons for having 2 tests are now pretty clear. Will add the case with anyuid enabled as separate test.

Yes we should have both test case with/without anyuid.

@ibuziuk @agajdosi This test should be part of minishift repository, so that we can test each PR or at least nightly with this test.

@LalatenduMohanty do you mean minishift-addons ? minishift repo does not seem to contain che by default - https://github.com/minishift/minishift/tree/master/addons

do you mean minishift-addons ? minishift repo does not seem to contain che by default - https://github.com/minishift/minishift/tree/master/addons

Good point. The reason we have kept Che in minishift-addons because it was not stable at that time.  may be it is time to re-evaluate it.  Personally I want to have the test in the minishift repo even if Che is not part of the repository.

I would be really happy if che would be a part of the default set of addons!

Personally I want to have the test in the minishift repo even if Che is not part of the repository.

Well, that might be a bit misleading IMO if addon is not part of the defaults. It would be great if we could add both addon and tests to the minishift though.

Personally I want to have the test in the minishift repo even if Che is not part of the repository.

@LalatenduMohanty Still the code should live at m-addons (if Che addon remains here) and we should only import the package. Right now I am however not sure (suspicious of circular dependency) if that would be possible (need to check for possible solutions).
What bothers me more is that AFAIK there is no way to use dep to handle the feature files, so we would need to take care of updating duplicate files at 2 locations.

This test should be part of minishift repository, so that we can test each PR or at least nightly with this test.

Because of stuff above^^ we should maybe consider not having Che addon tests as part of the repository, but having minishift-addons tests as part of PR/nightly/release checks. After tests implemented in minishift repository we can just clone minishift-addons repo and run whatever we want from there.
Or we just add Che addon itself and its tests to minishift. If that would make @ibuziuk really happy, we should consider :wink:

Hi all, I am closing this issue as we moved Che to Minishift repository. Corresponding issue: https://github.com/minishift/minishift/issues/2597.


(forums) Make user stories for unregistered users (Burgess and Gio)

This issue focuses on developing user stories for unregistered users on our board games forum. We'll explore passive interactions like browsing and reading, understand access limitations, and identify factors motivating registration. By mapping the unregistered user journey, we aim to enhance the forum's design to encourage registration and active participation.

This issue focuses on developing user stories for unregistered users on our board games forum. We'll explore passive interactions like browsing and reading, understand access limitations, and identify factors motivating registration. By mapping the unregistered user journey, we aim to enhance the forum's design to encourage registration and active participation.

In brainstorming some possible ideas for functionality for unregistered users, I came up with these user stories, albeit some might me repetitive given the restricted functionality for these type of users:

Jamie visits the ChiGame forum and browses top threads. Intrigued by several discussions, they realize they can't join in without an account.
Casey stumbles upon a compelling ChiGame forum debate about a trending game. Wanting to reply, they're prompted to log in or register.
Jordan, a frequent ChiGame forum reader, bookmarks intriguing threads for future reading, yet is aware they can't directly interact or post replies.
Alex discovers the "User Reviews" section on ChiGame. They read multiple reviews, and really like this one particular review. They wish to upvote the comment, but cannot because they are a registered user.
Taylor finds a fascinating game walkthrough thread on ChiGame. They're keen on asking questions but are blocked by the login prompt.
Jordan, on another visit, notices a captivating "Game Theories" thread but sees a lock icon, indicating some threads may have restrictions for unregistered users.
Casey, eager to share a game tip, starts typing a response in a ChiGame thread but is redirected to the registration page upon hitting "Submit".
Jamie wishes to be notified of new replies in a popular ChiGame thread but sees a reminder that thread subscription is only for registered members.
Alex, after reading a heated ChiGame debate, wishes to report a possibly rule-breaking comment but can't access the "Report" function without an account.

Feel free to leave any comments on any additional functionality we can include on this!

Overall, I like these stories. A couple of thoughts:
Stories 1, 2, 5, and 7 describe a similar use case, so it may make sense to consolidate them into one:
"Jaime visits a ChiGame forum and, intrigued by a thread debating a trending game, types a reply out to one of the comments. On submitting, he is redirected to a login page describing comments can only be used for registered user."
Otherwise, these are great stories to me!

Design note, you might want to not even let users type replies until they're logged in.
Since imagine if you see a box, are allowed to type in it, then only upon submitting do they tell you you can't submit (then likely wiping your input).
Instead adding a "please sign in to comment" prompt in place of a comment box would be a "kinder" design (aka have better UX)

I like these suggestions and I think the comment on UX is better! I had preferably put down two just to gather which functionality we would like to incorporate, but I second this!
This is the revised set of user stories:

Jaime visits a ChiGame forum and, intrigued by a thread debating a trending game, and intending to reply is met with "Please sign in to comment" prompt to be able to submit a reply.
Jordan, a frequent ChiGame forum reader, bookmarks intriguing threads for future reading, yet is aware they can't directly interact or post replies.
Alex discovers the "User Reviews" section on ChiGame. They read multiple reviews, and really like this one particular review. They wish to upvote the comment, but cannot because they are a registered user.
Jordan, on another visit, notices a captivating "Game Theories" thread but sees a lock icon, indicating some threads may have restrictions for unregistered users.
Jamie wishes to be notified of new replies in a popular ChiGame thread but sees a reminder that thread subscription is only for registered members.
Alex, after reading a heated ChiGame debate, wishes to report a possibly rule-breaking comment but can't access the "Report" function without an account.

Closing this issue for now as well!

@giomhern @bburgess19 Please take these user stories and publish them as a wiki page! This way we (or anyone else) won't have to find this specific issue to figure out what y'all's user stories are.

Issue Score: Excellent
Comments:
Great job! I appreciate y'all using the issue tracker to hold conversation about the user stories.
Thank you for actually creating the wiki page.
In the future, please remember to only close with a comment that describes why the work was done and also what work was done by each developer.
Great work and keep going!


Added monochrome option and updated dependencies

I added a monochrome option because I wanted JSON without ANSI escapes.

Nice feature, thanks @QazCetelic! 👍🏻


"partial" is inconsistent in C#

A user requested adding partial annotations even for "just types", because they want to extend their types with more stuff that's not in the JSON.  Looking at this further, I discovered that when we generate helpers, we make ALL classes partial, despite only the top-level ones being extended by the helpers.
We need to decide whether

partial is there to let users extend the types.  Then it should be there even for "just types".

partial is just there for the helpers.  Then we need to remove it from all the non-top-level classes.

I think I weakly prefer the former.  If we go with the latter I think we should at least have the option to make all classes partial.

Thanks for considering this. Nice job with quicktype too!
With generated code I often find it's useful to be able to add some additional properties that aren't in the schema but may be used internally by code. Ideally I like to be able to keep my generated code in separate files to the additional custom code, so any time the schema is updated the generated code can be replaced without loosing any additional properties etc.
For instance, at the moment I'm working on JSON for a report that has detail items and a summary calculated from the detail items. To calculate the summary I need some fields on the detail items that, for business reasons, I don't want to expose in the schema for the detail items.
Ideally I would like to be able to do a query for my detail items, and project the result into the detail objects for the report (including the additional properties), then calculate the summary using the additional properties on those objects, and then serialize to json with the additional properties being excluded because the I have JsonIgnore attributes in the custom partial classes.
I can do this at the moment using the "Complete" generation option for C#, but for our solution we don't really use the serialization helper classes, so I would ideally like to be able to generate partial classes for the "Attributes Only" and "Just Types" options.
Example:
//Foo.generated.cs

public partial class Foo
{
    [JsonProperty("bar")]
    public string Bar { get; set;}
}

//Foo.custom.cs

public partial class Foo
{
    [JsonIgnore]
    public string SomethingExtraNotInSchema { get; set; }
}

@dvdsgl Do you have strong opinions on this?

I prefer the latter as well–all generated classes should be partial in C#.
At first I'd say that classes like Converter and Serialize should not be partial, but this could be a subtle way to avoid the collision problem in #276 (provided that we sufficiently distinguish member names).

Fixed in #602


1.11.0 alpha 4 is incompatible with optifine G9

IR 1.11.0 alpha 4 is incompatible with optifine G9.
The conflict was caused by MixinItemRenderer.class in the client directory in the mixin directory in the me directory in the IR 1.11.0 alpha 4.jar.
Steps to Reproduce:
It always happens when I try to use IR 1.11.0 alpha 4 and optifine_U_G9 at the same time.
However, this problem is easily solved.
If you delete MixinItemRenderer.class and delete the part that mentions MixinItemRenderer.class from indrev.mixins.json directly under IR 1.11.0 alpha 4.jar, optifine_U_G9 and IR 1.11. 0 alpha 4 can coexist.

Thanks for reporting, however deleting classes isn't the way to go to fix these issues and Optifine compatibility isn't something I'm personally concerned about, there are other replacements for its features that don't break everything, and when they do we can actually do something about it since they are open sourced.


No error reported by job when uploading an invalid Json file from local file

Hi
Using

Google.Cloud.BigQuery.V2 v1.3.0.
Visual Studio Community 5017 v15.9.12

A job which upload an invalid local Json file has an invalid state, which do not reflect the real state of it.
The state of the job which upload the file is invalid (looks non updated) after the upload completion method has returned (PollUntilCompleted). Note that creating a new job object, using the same Reference Id, gets a job with a valid state which indicates an error.
The following code reproduces the issue (change the projectId to yours) :
var projectId = "...";
var client = BigQueryClient.Create ( projectId, credentials );

var datasets = client.ListDatasets();
var dataset = datasets.FirstOrDefault ( d => d.Reference.DatasetId == "TestDataset" );
if ( dataset == null )
	dataset = client.CreateDataset ( "TestDataset" );

var tables = dataset.ListTables();
var table = tables.FirstOrDefault ( t => t.Reference.TableId == "TestTable" );
if ( table == null )
{
	var builder = new TableSchemaBuilder();
	builder.Add ( "A", BigQueryDbType.String );
	builder.Add ( "B", BigQueryDbType.Int64 );
	builder.Add ( "C", BigQueryDbType.Float64 );

	var schema = builder.Build();
	table = dataset.CreateTable ( "TestTable", schema );
}

// this json has a missing new line delimiter
var json = "{A=\"Hello\",B=5,C=0.42}\n{A=\"Hello\",B=5,C=0.42}{A=\"Hello\",B=5,C=0.42}\n{A=\"Hello\",B=5,C=0.42}";
var bytes = Encoding.UTF8.GetBytes ( json );
var memoryStream = new MemoryStream ( bytes );

var uploadOptions = new UploadJsonOptions()
{
	ProjectId = projectId,
	Autodetect = false
};

try
{
	var job = client.UploadJson ( table.Reference, null, memoryStream, uploadOptions );
	Console.WriteLine ( $"Job id is {job.Resource.Id}" );
	job.PollUntilCompleted();

	Console.WriteLine ( $"Job should be completed, status is {job.Status.State}" );
	if ( job.Status.ErrorResult != null )
			Console.WriteLine ( $"Job has finished with error : {job.Status.ErrorResult.Message}" );
	else	Console.WriteLine ( $"Job has finished with no error" );

	job.ThrowOnAnyError();

	var jobBis = client.GetJob ( job.Reference );
	Console.WriteLine ( $"Job bis status is {jobBis.Status.State}" );
	if ( jobBis.Status.ErrorResult != null )
			Console.WriteLine ( $"Job bis has errors : {jobBis.Status.ErrorResult.Message}" );
	else	Console.WriteLine ( $"Job bis has no error" );

	Console.WriteLine ( $"Job status is still {job.Status.State}" );
	if ( job.Status.ErrorResult != null )
			Console.WriteLine ( $"Job still has error : {job.Status.ErrorResult.Message}" );
	else	Console.WriteLine ( $"Job still says it has no error" );
}
catch (Exception e)
{
	Console.WriteLine ( e.Message );
}

State of job is invalid : job.Status.State is "RUNNING".
State of jobBis is valid : jobBis.Statis.State is "DONE" and the state contains errors as expected.
Regards.

I strongly suspect this is the problem:
job.PollUntilCompleted();

That doesn't change the current BigqueryJob - it fetches a new BigqueryJob.
If you just change that to:
job = job.PollUntilCompleted();

I suspect you'll find it behaves as expected.

Oh !
I never suspected something like that.
I used the example code from https://cloud.google.com/bigquery/docs/loading-data-local as a base code... a base code that didn't mention anything like that.
May I propose to make this more clear by design ? having a PollUntilCompleted ( ref BigQueryJob ) so that the ref could be null if unused, or used to pass an updated object as well. It would make it clear that you can get an updated object in return of the method.
Or simply by renaming the method to include a Get somewhere. PollUntilCompletedAndGetJob() or GetJobOnceCompleted.
Thanks for the reply.
Regards.

We can't change the method name or signature now - but I'll definitely get the samples changed; thanks for pointing that out.

Changing the name no, but you could mark it as deprecated (using Obsolete attribute) and have a new method with a different name or design that would be recommended to use instead.
But anyway, having samples that highlight this would be probably enough.

I'd rather not make it obsolete - particularly as it (deliberately) matches the Operation<TResponse, TMetadata> methods as well. I'll get the samples fixed and improve the XML documentation - I think that should be sufficient.


Rename confirm with enter not registering

@bryphe following #1417 where I believe you consolidated some functionality the rename commit action on hitting enter no longer works i.e. you it opens as expected and still closes with <esc> but does not register hitting <enter>

Thanks for catching this, @Akin909 ! Really appreciate all your help with stabilizing changes.
Ah es, I meant to wire up the <enter> key to this too (wanted the text inputs in the sidebar to have an onComplete event, and it made sense to have shared functionality instead of implementing new commands/keybindings for this all the time).


Unsupported assets

Crashes when attempting to load.
Version: "5.5.0x1-CollabPreview"
https://mega.nz/#!t4hS3CpK!P--shnW7NiOs_sYRRxIHhDUl87YX_k4ajSlWMDwL5lU

fixed in b319e92b3e6ddb98440322e3c3db4aecc895262c

Working now, thanks!


Isn't 0,0 bottom left?

Thanks for the great alternative to http://lokspace.eu/3d-printer-auto-bed-leveling-mesh-visualizer/
but isn't the 0,0 position in the bottom left corner?

Yes, but for some strange reason matplotlib defaults to placing the Y axis 0 at the top. The original "fix" for this to keep the zeros together was to move X labels at the top, but that also isn't very standard if you ask me and the title also had to be removed to do so.
I have adjusted things so that the mesh level output list gets reversed on Y axis before being handed off to numpy. This flips things upside down. I then flip it by Y axis again in the heatmap rendering settings, effectively moving 0 to the bottom and flipping things right side up again for the viewer.
Along with this, I have moved X labels back to the bottom and included the title again. Enjoy!


Extra docs for compiling Windows binaries

Added some extra documentation to detail how to use configure to compile Windows binaries.

Saying that you can run ./configure --host=x86_64-w64-mingw32 in Windows, without explaining which are the pre-requisites are going to be confusing for many people that don't know about mingw32, so I would explain that a little bit about how to setup mingw32 in your machine.

Saying that you can run ./configure --host=x86_64-w64-mingw32 in Windows, without explaining which are the pre-requisites are going to be confusing for many people that don't know about mingw32, so I would explain that a little bit about how to setup mingw32 in your machine.

That's a fair comment! My setup was so that I could compile Windows binaries on Linux (using WSL).
Main reason I want to add these to the docs is that if you're developing YARA on Windows, it wasn't immediately clear on how to compile it from source (I had to check some of the GitHub actions to get some context). Hopefully this addition will make it clear on a method of doing this, but happy to keep tweaking it until it is as clear as possible?

Sure, a more detailed explanation that covers how to build YARA on Windows using Mingw32 is welcome.

Closing this off as I haven't figured out how to quite make this work yet...


chore(master): release 1.3.2

:robot: I have created a release beep boop
1.3.2 (2023-03-14)
Miscellaneous

update readme (4bf3a7d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/docker-project-services/releases/tag/v1.3.2 :sunflower:


Reinstalled removed apps

I just noticed that some of the apps have been reinstalled. The date given for the reinstalled apps is a few days after I ran the script. Is it possible that Windows Update reinstalled these programs?

Hi,
Yes that is entirely possible. In fact, often enough you will find that
Windows Update will reinstall the apps.
Unfortunately there really is no permanent way to keep the apps removed
forever, unless you move to Windows 10 LTSB.
On Sat, Apr 7, 2018, 1:39 PM YenLegion<EMAIL_ADDRESS>wrote:

I just noticed that some of the apps have been reinstalled. The date given
for the reinstalled apps is a few days after I ran the script. Is it
possible that Windows Update reinstalled these programs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Sycnex/Windows10Debloater/issues/17, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHCc4LBKNXRjUrQOAZyMBpFkOD74oJimks5tmSP9gaJpZM4TLPmF
.

I've been using the sysprep debloater at most of my customer engagements and so far it's worked very well and very consistently.  The only "updates" we've seen that do this (so far anyway) have been build upgrades.  None of the cumulative updates have reinstalled them as far as I've seen.  But the script could be re-applied if needed, using a variety of delivery means.

@YenLegion May I close this or would you like it to remain open?


Issues with a few stretchy accents

Issue Summary
Most stretchy accents are appearing as we'd expect in MathJax [reverse vector (x20d6), tilde (x303), underbar (x332), vector (x20d7), and circumflex (x302)], but we're having trouble with three of them: double bar overhead (x33f), double headed arrow accent (x20e1), and vinculum (x305).
 Is the only way to solve these by using different characters for the accents, i.e.,

<mover>           <mrow>             <mi>x</mi>             <mi>y</mi>             <mi>z</mi>           </mrow>           <mrow>             <mo stretchy="true">=</mo>           </mrow>         </mover>

<mover>           <mrow>             <mi>x</mi>             <mi>y</mi>             <mi>z</mi>           </mrow>           <mrow>             <mo stretchy="true">↔</mo>           </mrow>         </mover>

<mover>           <mrow>             <mi>x</mi>             <mi>y</mi>             <mi>z</mi>           </mrow>           <mrow>             <mo stretchy="true">¯</mo>           </mrow>         </mover>
Technical details:
MathJax Version: master - latest commit: MathJax.js v2.7.9
Client OS: Windows
Browser: Version 93.0.4577.63 (Official Build) (64-bit)
Renderer: HTML-CSS

MathJax needs to have data about how to stretch each stretchy character, and not every potentially stretchy character has that data (most of it was taken from the font's OpenType MATH table, which lists the stretchy characters).  But you can add more characters to the delimiter table as needed.  For example, adding
MathJax.Hub.Register.StartupHook("HTML-CSS Jax Ready", function () {
  var HTMLCSS = MathJax.OutputJax['HTML-CSS'];
  var DELIMITERS = HTMLCSS.FONTDATA.DELIMITERS;
  DELIMITERS[0x0305] = {dir: "H", alias: 0x00AF};
  DELIMITERS[0x033F] = {dir: "H", alias: 0x003D};
  DELIMITERS[0x20E1] = {dir: "H", alias: 0x2194};
});

to your configuration would define the stretchy data for the three missing (by making them act like the ones that you mentioned, for which stretchy data is available).  Is that good enough?

@dpvc Yep, that seems good enough, and I tested it and they looked great. Thank you! Hey, also, I noticed you replied to this question from a few days ago but I have a couple other questions from July that haven't been answered yet: https://github.com/mathjax/MathJax/issues/2742 and https://github.com/mathjax/MathJax/issues/2739. Do you think you or someone else could please take a look at these some time soon too? Thanks!

I'm trying to work through a backlog of questions, and have been working from recent backwards.  Due to personal reasons, I have not been able to respond to nearly anyone for the past month or more, and now my teaching schedule limits by availability.  There is also a funding issue that is also limiting my hours for MathJax; perhaps the ACS would be willing to become a MathJax sponsor?

Do you think you or someone else could please take a look at these some time soon too?

There really is no one else to do it.  There are two developers for MathJax, and your questions fall into my area of expertise, so I am the one who has to answer them.  The line breaking questions are a bit more complicated than this one, and will take more time to answer, so gave you a response here first, since it would get you something more quickly.  I will get to the others as soon as I am able.

@dpvc Thank you for the explanation. When the more recent question was answered but not the older ones, it made me wonder if they got lost somehow. I am in the process of checking with ACS leadership about sponsorship and will follow up on that as soon as I can.


Full-white display on GNOME/Mutter 46

I'm running Bazzite, Mesa 24.0.5. My first guess is that this is an incompatibility with Mutter 46, as I did not have this issue running Nobara, with a newer(git) Mesa version, but still running under GNOME 45.

Issue remains after updating to GNOME 46.1. This might be fixed with Mesa 24.1, will keep this issue posted.


Add request HTTP headers to "fn invoke"

As a user I'd like to specify HTTP headers like fn invoke blah blah --http-header 'Blah: blah'

Doesn't seem unreasonable.

there are two features that I'd like to see as part of the CLI: #546 and this. They both related, the one is all about HTTP headers to make HTTP requests complete and the second one is all about providing a short path to get invoke annotation in order to use it with OCI cURL (or any other HTTP CLI tool).

Just to double check, do you mean something that replicates:
curl -H 'My-header: foo' http://localhost:8080/t/myapp/getheaders-trigger

If so this should be easy enough to do. Just need to watch out for someone doing something like:
fn invoke myapp getheaders --content-type 'application/json' --http-header 'My-header: Foo' --http-header 'Content-Type: text/plain'

Yeah, my original idea was about doing exactly what you’ve shown. But later I start evaluating this particular feature. Eventually all I need is already implemented in the cURL and the invoke endpoint I can get from fn inspect fn ––endpoint app fn.
.
So, not sure if it’s really worth it.


Roll engine 48ad8a08e45f..0bfca375b3f5 (4 commits)

git@github.com:flutter/engine.git/compare/48ad8a08e45f...0bfca375b3f5
git log 48ad8a08e45f..0bfca375b3f5 --no-merges --oneline
2019-09-25<EMAIL_ADDRESS>Force exit felt tool on sigint, sigterm (flutter/engine#12443)
2019-09-25<EMAIL_ADDRESS>Roll src/third_party/skia 6abaff3041a3..559ffe4a23ce (2 commits) (flutter/engine#12444)
2019-09-25<EMAIL_ADDRESS>[fuchsia] Wire up OpacityLayer to Scenic (flutter/engine#11322)
2019-09-25<EMAIL_ADDRESS>delete golden files; switch to flutter/goldens (flutter/engine#12434)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.

This PR has been implicated in a benchmark regression: https://github.com/flutter/flutter/issues/41394


Switch to GitHub Actions CI.

Opening mostly as a POC
TODO:

[x] Split debug and production tests so that they run in parallel
[ ] Remove CircleCI from repo (hooks, integrations) before merging
[ ] Update repo branch protections rules

Fixes #1359

I'm gonna proceed with this.
I'll split the actions later.

@jmervine please remove the project and probably the org from CircleCI, I don't have the rights to do it myself

Done


[Maestro 1.36.0] It's not possible to specify a device when using Maestro on Windows.

Describe the bug
When attempting to run Maestro Studio or a YAML flow, it's not possible to specify the device. In Windows, it's necessary to set the host to run the Studio or a flow. However, despite setting the host, it seems to ignore the device specified in the command prompt and instead runs the flow or Studio on the first device registered on the ADB.
To Reproduce
Steps to reproduce the behavior, e.g.:

Start the simulator
Run maestro --device emulator-5554 --host <IP_ADDRESS> studio
The Studio does not display the device specified in the command.

Environment information (please complete the following information):

Maestro version 1.36.0
Platform: Android 14
Framework: Native Android
Device model and OS version: Google Pixel 6
Physical device
Host: Windows

I have also encountered this problem.

thanks @7maucdn
closing as duplicate of #1799


Date Error message incomplete

Expected behaviour
Full Date error message displayed to respondent
Actual behaviour
Partial error message displayed to respondent
Steps to reproduce the behaviour
Start business survey 0205 (or any other RSI related survey)
Provide 2 dates that generate an error message (e.g. dates the same, From is after To date)
Submit form - note error message
Technical information
Browser
Chrome
Operating System
Windows 7
Screenshot

Fix for this is currently in master. @stevevic can you close it?

Confirmed fixed on master


Extract MiqTask#human_status to avoid code duplication

@miq-bot add_label core, refactoring

😍   LGTM, but it's failing a test for some reason.

👍 LGTM

The tests were failing as the MiqWidget.status and MiqReportResult.status were not fully consistent. I missed the during the first review. The first commit in the batch now fixes the inconsistency.


ADGUARD的推度連結被錯誤封鎖

Which tool do you use?
AdGuard
Which List do you use?
AdRules AdBlock List Normal
Which content should be unblocked?
email-link.adtidy.org
Why should the content be unblocked?
這是ADGUARD推廣郵件裡的連結，現在卻打不開了。

不过确实是这末提示的


Add HTTPS Redirection

Pull request
Proposed changes

Add HTTPS redirection.
Types of changes

[x] New feature (non-breaking change which adds functionality).
[ ] Enhancement (non-breaking change which enhances functionality)
[ ] Bug Fix (non-breaking change which fixes an issue).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist

[x] I have read the README document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

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 29.167%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7

Relevant Lines:
24

💛  - Coveralls


Add files via upload

Add French & Turkish translation. Thanks for this app that still works on old devices contrary to other wallets I could find on F-Droid. It helped me buy a premium download account when my bank wouldn't allow me for some reason. If there's something else to add to these feel free to ping me.

Thanks.


tag no_inst_fleet_unit_tests

Tag no_inst_fleet_unit_tests.py so that the test skips,to be incorporated  into the continuous integration

closed with https://github.com/ergs/d3ploy/pull/80


pam_oath: require OATH and pam_unix credentials to be valid

Motivation for this change
Can people interested in this functionality check this out?
requisite checks the OATH token first then password and fails immediately if the token isn't valid, plus fails if the unix password fails.
re https://github.com/NixOS/nixpkgs/pull/22393 https://github.com/NixOS/nixpkgs/issues/14997
cc @spacefrogg @clefru @spacekitteh @spinus @wizeman @vcunat @obadz @cleverca22 @fpletz
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@grahamc this is very nice test set, cheers.
I wouldn't hard code requisite, some people (like me :-) use some of those modules as alternative to password login and not two factor. I agree that two factor should be default one, but I would allow to chose the pam option. For example: `oath.pam-control = "require|requisite|optional|etc....". What do you think?

Tomasz Czyż<EMAIL_ADDRESS>writes:

@grahamc this is very nice test set, cheers.

:) I think it would be good to have at least some tests for future PAM
modules in order to prevent this sort of issue in the future.

I wouldn't hard code requisite, some people (like me :-) use some of
those modules

Which modules? Some of them, I think are sufficient as a single factor.
OATH though is a pretty crappy first factor. Are you using OATH like
this?

as alternative to password login and not two factor. I
agree that two factor should be default one, but I would allow to
chose the pam option. For example: `oath.pam-control =
"require|requisite|optional|etc....". What do you think?

I'm not inclined to do the work to make this possible, because I think
it is a dangerous option to give. In general, I think our PAM module
isn't expressive enough to support such a level of configurability. I
think at some point adding an extraConfig option where you can just
add whatever you want would be better.

Please make sure this or a variant hereof is on master before February 27th :)

Done, @globin :)


Feature request: support high resolution metrics

Use case
Amazon CloudWatch announced support for high resolution metric extraction from structured logs (EMF). Customers can now provide an optional StorageResolution parameter within the EMF specification with a value of 1 or 60 (default) to indicate the desired resolution (in seconds) of the metric.
We should consider adding support for this new optional parameter to Metrics.
The EMF log should have this format:
{
  "_aws": {
    "CloudWatchMetrics": [
      {
        "Metrics": [
          {
            "Name": "Time",
            "Unit": "Milliseconds",
            "StorageResolution": 60 // <- new key
          }
        ],
        ...
      }
    ]
  },
  "Time": 1
}

As part of this issue we should also update the API docs, documentation, and unit/integration tests.
Solution/User Experience
Proposed DX:
using AWS.Lambda.Powertools.Metrics;

public class Function {

  [Metrics(Namespace = "ExampleApplication", Service = "Booking")]
  public async Task<APIGatewayProxyResponse> FunctionHandler(APIGatewayProxyRequest apigProxyEvent, ILambdaContext context)
  {
    // Publish a metric with standard resolution i.e. StorageResolution = 60
    Metrics.AddMetric("SuccessfulBooking", 1, MetricUnit.COUNT, MetricResolution.HIGH);
    // Publish a metric with high resolution i.e. StorageResolution = 1
    Metrics.AddMetric("FailedBooking", 1, MetricUnit.COUNT, MetricResolution.HIGH);
    // The last parameter (storage resolution) is optional
    Metrics.AddMetric("SuccessfulUpgrade", 1, MetricUnit.COUNT);
  }
}

To support the proposal, a new MetricResolution enum should be added, as well as changes to the Metrics.AddMetric method.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[X] Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

Not sure what happened here, I duplicated the issue by mistake - sorry.
Closing in favor of #197


Can Kosmos-2 run in lower precision?

It is being loaded like this but there are no options regarding precision
What optimizations there are that can be used for low VRAM gpus?
Thank you
    model_source = "microsoft/kosmos-2-patch14-224"

    model = AutoModelForVision2Seq.from_pretrained(model_source).to("cuda")
    processor = AutoProcessor.from_pretrained(model_source)

Also what other optimizations there are available?


Saved files never get closed

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Each time a file is saved atom reopens it in read mode and never closes the file descriptor. This causes problems on network shares if the file is unlinked (stale .nfsXXX files), e.g. after git checkout.
Steps to Reproduce

touch /tmp/foo
atom /tmp/foo
save /tmp/foo (from file menu or ctrl+s)
lsof /tmp/foo will show atom process holding /tmp/foo open in read mode
repeat steps 3&4, to get more file descriptors open (I got to over 2000 just by keeping cltr+s pressed for long enough)

Expected behavior: close file after save
Actual behavior: file is kept open after save (file descriptor is not released)
Reproduces how often: every time
Versions
$ atom --version
Atom    : 1.26.0
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0

$ apm --version
apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.26.0
python 2.7.5
git 2.16.5

$ cat /etc/redhat-release
Red Hat Enterprise Linux Client release 7.6 (Maipo)

Additional Information
Possibly related to #17355

@TomekTrzeciak FYI, your Atom version is 11 releases out of date

@Aerijo, I don't have access to more recent version, but that should change later this month. I'll update this ticket then.

I've tested  on the latest release (1.37) and this issue appears to be fixed.


Issue Creating Scheduled Toast Notifications

Hello,
Could you test creating scheduled toast notifications without ever calling the CreateToastNotifier.Show() function?
If my app just creates scheduled toast notifications, it doesn't seem to work. One thing I tested was creating a build that creates notifications immediately using .show(), then replacing it with the one that uses AddToSchedule and then it starts working. There must be something that .show() is doing that AddToSchedule isn't, because until I call show() I never see my app in the Notification & Actions section of the Windows Settings. But, I don't see anything in the documentation on scheduled notifications that indicate this....
https://github.com/MicrosoftDocs/windows-uwp/blob/docs/windows-apps-src/design/shell/tiles-and-notifications/scheduled-toast.md
Doesn't work...
            var toast = new ScheduledToastNotification(toastContent.GetXml(), DateTime.Now.AddSeconds(5));
            DesktopNotificationManagerCompat.CreateToastNotifier().AddToSchedule(toast);

Will work...
                ToastNotification toast = new ToastNotification(toastContent.GetXml());
                DesktopNotificationManagerCompat.CreateToastNotifier().Show(toast);

                var toast = new ScheduledToastNotification(toastContent.GetXml(), DateTime.Now.AddSeconds(5));
                DesktopNotificationManagerCompat.CreateToastNotifier().AddToSchedule(toast);

I can build a version that creates 1 notification using .show() then delete it and replace it with the version that only uses .AddToSchedule() to create notifications and everything works.
What does calling .show() do in the background that .AddToSchedule() isn't doing? I see that using .show() winds up putting my app in the Notifications & Actions, where .AddToSchedule() never would.

Hey @andrewleader, I noticed you have a repo for testing toast notifications https://github.com/andrewleader/NotifTestApps
Got any ideas? Have you tested ScheduledToastNotifications before?