Is it possible to generate speech without reference audio?

Hi, thank you so much for your great work.
Is it possible to generate speech without reference audio after training a new ssr-speech model?
Besides, I want to confirm whether the dataset format shown below is correct.
SPK_ID
├── 1.json
├── 1.wav
├── 2.json
├── 2.wav
├── 3.json
└── 3.wav

Hi, thanks for your interest in our work!
What do you mean by generating speech without reference audio? For the speech editing, we need the reference audio as we want to edit it. For the TTS, we also need one to clone its timbre. Could you please clarify your need?
For the data preparation, please prepare files like this:
{
"segment_id": "audio1",
"wav": "/data/audio1.wav",
"trans": "I like SSR-Speech.",
}
{
"segment_id": "audio2",
"wav": "/data/audio2.wav",
"trans": "SSR-Speech can do both zero-shot speech editing and text-to-speech!",
}
...

And the dataset format can be in this way:
json_folder
├── train.json
├── test.json
├── val.json

We don't rely on speaker ids, all you need is to prepare such json files. Please update to the newest version of this repo.

Hi, thanks for your interest in our work!
What do you mean by generating speech without reference audio? For the speech editing, we need the reference audio as we want to edit it. For the TTS, we also need one to clone its timbre. Could you please clarify your need?
For the data preparation, please prepare files like this:
{
"segment_id": "audio1",
"wav": "/data/audio1.wav",
"trans": "I like SSR-Speech.",
}
{
"segment_id": "audio2",
"wav": "/data/audio2.wav",
"trans": "SSR-Speech can do both zero-shot speech editing and text-to-speech!",
}
...

And the dataset format can be in this way:
json_folder
├── train.json
├── test.json
├── val.json

We don't rely on speaker ids, all you need is to prepare such json files. Please update to the newest version of this repo.

Hi, thanks for your reply!
I ran the dataset preprocessing and training scripts successfully but encountered a problem with inference when using a new ssr-speech model. Is there any specific requirements for dataset? I used 80 wav files with an average length of about 10 secs each.

Hi, thanks for your interest in our work!
What do you mean by generating speech without reference audio? For the speech editing, we need the reference audio as we want to edit it. For the TTS, we also need one to clone its timbre. Could you please clarify your need?
For the data preparation, please prepare files like this:
{
"segment_id": "audio1",
"wav": "/data/audio1.wav",
"trans": "I like SSR-Speech.",
}
{
"segment_id": "audio2",
"wav": "/data/audio2.wav",
"trans": "SSR-Speech can do both zero-shot speech editing and text-to-speech!",
}
...

And the dataset format can be in this way:
json_folder
├── train.json
├── test.json
├── val.json

We don't rely on speaker ids, all you need is to prepare such json files. Please update to the newest version of this repo.

Hi, thanks for your reply! I ran the dataset preprocessing and training scripts successfully but encountered a problem with inference when using a new ssr-speech model. Is there any specific requirements for dataset? I used 80 wav files with an average length of about 10 secs each.

Hi, what kind of error did you face? 10-second audio is fine for the model.

Hi, thanks for your interest in our work!
What do you mean by generating speech without reference audio? For the speech editing, we need the reference audio as we want to edit it. For the TTS, we also need one to clone its timbre. Could you please clarify your need?
For the data preparation, please prepare files like this:
{
"segment_id": "audio1",
"wav": "/data/audio1.wav",
"trans": "I like SSR-Speech.",
}
{
"segment_id": "audio2",
"wav": "/data/audio2.wav",
"trans": "SSR-Speech can do both zero-shot speech editing and text-to-speech!",
}
...

And the dataset format can be in this way:
json_folder
├── train.json
├── test.json
├── val.json

We don't rely on speaker ids, all you need is to prepare such json files. Please update to the newest version of this repo.

Hi, thanks for your reply! I ran the dataset preprocessing and training scripts successfully but encountered a problem with inference when using a new ssr-speech model. Is there any specific requirements for dataset? I used 80 wav files with an average length of about 10 secs each.

Hi, what kind of error did you face? 10-second audio is fine for the model.

I haved trained my model for 5000 steps but it can't generate speech. I set --text_vocab_size and --text_pad_token to 200 since it's a mandarin model, and used default value for other parameters in script e830M.sh. Do you have any suggestions on how to improve this?

Hi, thanks for your interest in our work!
What do you mean by generating speech without reference audio? For the speech editing, we need the reference audio as we want to edit it. For the TTS, we also need one to clone its timbre. Could you please clarify your need?
For the data preparation, please prepare files like this:
{
"segment_id": "audio1",
"wav": "/data/audio1.wav",
"trans": "I like SSR-Speech.",
}
{
"segment_id": "audio2",
"wav": "/data/audio2.wav",
"trans": "SSR-Speech can do both zero-shot speech editing and text-to-speech!",
}
...

And the dataset format can be in this way:
json_folder
├── train.json
├── test.json
├── val.json

We don't rely on speaker ids, all you need is to prepare such json files. Please update to the newest version of this repo.

Hi, thanks for your reply! I ran the dataset preprocessing and training scripts successfully but encountered a problem with inference when using a new ssr-speech model. Is there any specific requirements for dataset? I used 80 wav files with an average length of about 10 secs each.

Hi, what kind of error did you face? 10-second audio is fine for the model.

I haved trained my model for 5000 steps but it can't generate speech. I set --text_vocab_size and --text_pad_token to 200 since it's a mandarin model, and used default value for other parameters in script e830M.sh. Do you have any suggestions on how to improve this?

What do you mean that "it can't generate speech"? What kind of output is it?
From my experiments, 5000 steps are not enough to train a model. You need at least 5000 hrs to train the Mandarin model and the 'val_top10acc_cb1' should be trained over 0.58 to get ideal results. Could you provide your training scale and the loss, if possible?


Fix CI/CD

The following improvements are needed for Continous Integration and Continous Deployments in front-end:

[ ] Fix the front-end pipelines in circleci.
[ ] Setup automatic deployment of the front-end build to the testing environment on a separate server.
[ ] Setup automatic deployment of the front-end build to a production-ready environment on a separate server.

Fixed here: https://github.com/UniversalDot/front-end/issues/5


User defined Client App bootstrapping function

I will squash my commits once  the review is complete.

Closing as I'm going for a different approach laid out by @ericherdzik


Updating the support text and support link

Updating as all users are not expected to have TG so we are adding a form link for support

Next time, please open the PR directly from this repo without forking.
commited the same mistake

fixed here


Update attachManyRelation in Create.php

Limit clearing of related records in attachManyRelation to those of the relationship being stored.
see https://github.com/Laravel-Backpack/CRUD/issues/4552

Hello @madriegh once again, thanks for the PR.
I've merged your commit into other branch where I could push some more stuff on it. It's here: #4554
I will be closing this in favor of that other branch!
🙏 🙏 Cheers


Reorganize as Client and Server

Make sure these changes can run on Heroku. The following show samples of how to do this:

https://daveceddia.com/deploy-react-express-app-heroku/
https://originmaster.com/running-create-react-app-and-express-crae-on-heroku-c39a39fe7851
<EMAIL_ADDRESS>

Merged into master, closing


Fixpoint crashes on compose00 VC

This is seriously much worse than I thought.  If we (just for kicks and giggles, like Facundo does in 26b7733c13bcc8560e66320eb502d80278ca6dd8) start fresh integers from 42, all hell breaks loose.


ReplaceDialog action doesn't work

Version
4.9
Describe the bug
The ReplaceDialog action doesn't work. It starts a new dialog but the current dialog stays on the stack.  That's because the code needs to be calling dc.parent.ReplaceDialogAsync()  It currently just attempts to replace the action.
[bug]

related https://github.com/microsoft/botbuilder-dotnet/issues/3900

Carlos is working on this now, landing today.

@carlosscastro is this not shipping in 4.10?

Closing as dupe. Tracking in https://github.com/microsoft/botbuilder-dotnet/issues/4365. To ship in 4.11. Chris, pinging you once we have a PR out.


SPIKE (3 days) -- Research Tom's Work to Consolidate Sender Error & Warning Messages

Problem Statement
As a Sender, I need to see error and warning messages in a structured way so that I am not confused and overwhelmed by a lot of the same type of messages.
Timebox

3 days

Notes
Refer to the following ticket:

https://app.zenhub.com/workspaces/prime-data-hub-5ff4833beb3e08001a4cacae/issues/cdcgov/prime-reportstream/1285

TO DO

Understand and document the work that Tom did towards this effort
Determine and document a plan for

How to finish the work that Tom started
Return consolidated messages from a Sender submission (via any submission method)
Return consolidated messages without affecting messages that existing users are getting through the API or vbScript or Simple Report

Determine the effort involved
Determine what changes to the CSV uploader will be necessary to display these consolidated messages

For my own understanding, I went through the entire upload flow and compared it with the Figma designs. Here is the current status of each step. Not everything is relevant to to this task, but documenting here in case it is helpful for anyone else

The goal of this task will be to come up with a plan for how to rollup warnings and failures (lines 6 and 8 above.)

Takeaways from Tom's proposed changes https://app.zenhub.com/workspaces/prime-data-hub-5ff4833beb3e08001a4cacae/issues/cdcgov/prime-reportstream/1285

This proposal would simplify the error messages sent to the client, however the messages still would not be a format helpful to match the current figma mocks. It is helpful for displaying unique errors and the the error counts, but not for including the column numbers
For the ResultDetail data class, creating a ResponseMessage interface will make the code more extensible and testable compared to just using a String. This convention should be adopted

Will had changed the system messages to be able to include the row & col for each message.  Also, I think there were decisions made on-the-fly as we were developing, so it's not surprising that the syncing with the mocks is not 100%.

No worries about the mocks not matching 100%, figured I'd document here just in case

Overview
To complete the work Tom started and roll up warning and error messages in order to match the mocks, there are 3 main steps:

(Server) Implement the ResponseMessage interface for each error type defined in the ResponseMsgType enum
(Client) Roll up the error messages by grouping them by ResponseMsgType
(Client) Display consolidated errors in the table format shown in the mocks

I anticipate this taking 5 days for 1 developer to complete.
Details

(Server) Implement the ResponseMessage interface for each error type defined in the ResponseMsgType enum
In Element.kt, instead of creating error/warning strings, instead create a ResponseMessage as defined by:

enum class ResponseMsgType { NONE, PAYLOAD_SIZE, OPTION, ROUTE_TO, REPORT, MISSING, UNEXPECTED, INVALID_DATE, INVALID_CODE, TRANSLATION }

interface ResponseMessage {
    val type: ResponseMsgType
    fun detailMsg(): String
    fun groupingId(): String {
        return ""
    }
}

Implementation of the interface above would consist of creating the message template in the detailMsg() function. The groupingId() method can be used as a key for aggregation of messages. For the example message above regarding invalid dates:
data class InvalidDateMessage(
    override val type: ResponseMsgType = ResponseMsgType.INVALID_DATE,
    val formattedValue: String = "",
    val fieldMapping: String = ""
) : ResponseMessage {
    override fun detailMsg() : String {
        return "Invalid date: '$formattedValue' for element $fieldMapping"
    }

    override fun groupingId(): String {
        return fieldMapping
    }

    companion object {
        fun new(formattedValue: String, fieldMapping: String): InvalidDateMessage {
            return InvalidDateMessage(ResponseMsgType.INVALID_DATE, formattedValue, fieldMapping)
        }
    }
}

ResultDetail` data class should now change to:
data class ResultDetail(val scope: DetailScope, val id: String, val message: ResponseMessage, val row: Int)

The ResponseMessage allows for the data to more easily be consolidated and the row number will be needed to display to the end user.

(Client) Roll up the error messages by grouping them by ResponseMsgType
On the front end (Upload.tsx), the errors will come in as an array of ResultDetail detailed above. In order to create the data needed for the table, loop through the errors array tracking unique errors and row numbers. This will look roughly like:

let consolidatedErrors = {}; // map of error types to an array of their row numbers
errors.forEach(error => {
  if (consolidatedErrors[error.message.type]) {
    // add row number too existing array
  } else {
    // create new key to track row numbers
}

This will create an arrays for each error type that has the full list of rows (for example, [1,3,4,5,8,9,10]. A nice to have is to then simplify even further to [1,3-5,8-10] but this feels like a nice to have, not a must have.
3. (Client) Display consolidated errors in the table format shown in the mocks
Now that the errors are nicely grouped by error type, they can be displayed in a table where one column is the error message, and the second is the row numbers. Since there could still be a large number of rows to this table and the column lengths could be long, truncation should be the fall back with a "See more" that expands the list.

I definitely like the idea of having the message in one column and then the row numbers in a separate column, as opposed to showing text with the rows embedded. There has been talk (just talk for now) of allowing Senders to edit their file in-place on the website. So, I would hate for us to get into a situation where we have to parse out the column & row numbers from the message in order to figure out which cells they would need to edit. The more we keep the individual pieces of information separate up until we need to display it the more flexible we can be with future feature requests.


validate 2.3

coverage: 97.144% (-0.05%) from 97.189% when pulling 1dee7e81420bed017fe394b694a31cc5d591043e on users/alexpeck/val2.3 into e88d5eb5161dec8a4181d835a2a74f1d7e419de0 on main.


file downloader with Python

Create a file downloader with Python in the directory /home/ < username > /OpenGameZone/ < GameName >
Download games from our host

can assign this to me?

can assign this to me?

Yes, I will be happy to help

Write the code in a functional way so that it can be used in other codes.
`python
def download_file(link):
# Write the code here to download the file from the given link
# You can use libraries like requests to download the file
# Example code using requests library:
# import requests
# response = requests.get(link)
# with open('downloaded_file.txt', 'wb') as file:
#     file.write(response.content)

# After downloading the file, you can perform other operations if needed

print(f'File downloaded from the link: {link}')

Example usage of the function:
file_link = "https://example.com/file.txt"
download_file(file_link)`

Sure!!

Thanks for the contribution


Lookup azure tenant id  if not provided

Use rancher/machine FindTenantID to look up the tenant ID if not found in the cloud credential secret in /meta/aks* proxy handlers.

Reverts https://github.com/rancher/rancher/pull/33680

Depends on https://github.com/rancher/aks-operator/pull/44
https://github.com/rancher/rancher/issues/33097

Since you are getting the cc off a lister isn't it possible the requests happen quickly enough to where it doesn't see the annotation on the secret?

Yes this is almost guaranteed to happen. This is kind of forced by the design.

I would just be curious to check it in logs once the UI is using it. Could you add a debug line

done in aks-operator

Yes this is almost guaranteed to happen. This is kind of forced by the design.

Actually in practice I think this will be safe, for now. UI just makes one request to /meta/aksLocations to look up the region before moving on to the next screen, so there will be enough time between that request and the user clicking the "next" button for the annotation to be populated. If the UI ever changes this to combine the full view then this might cause a problem.

Fixed go.mod


Assert expectations on health check response

Currently, health checks only take into account the status code (2xx or 3xx) when configured for HTTP or if the port is open for TCP connections.
Would it be possible to consider asserting expectations on the health check response?  Since the health check is based on haproxy, this could roughly translate into tcp-check expect string?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Added smoothing to BLEU scores

Added Chen and Cherry (2014) smoothing methods for BLEU.
Note that the p_n now needs to be materialized as opposed to how it was previously stored in a generator. It's because the p_n needs to be modified by the smooth_bleu() function.

Additionally, fix related test failures from bleu_score.py:

https://nltk.ci.cloudbees.com/job/nltk/TOXENV=py34-jenkins,jdk=jdk8latestOnlineInstall/lastCompletedBuild/testReport/nltk.test.unit.translate.test_bleu/TestBLEU/test__modified_precision/
https://nltk.ci.cloudbees.com/job/nltk/TOXENV=py34-jenkins,jdk=jdk8latestOnlineInstall/lastCompletedBuild/testReport/(root)/bleu_doctest/bleu_doctest/

Thanks @alvations – nice addition!

@stevenbird I've added the # doctest: +ELLIPSIS option the long floating points doctest. Hopefully that will prevent regression failures.

@dimazest I've changed the smoothing methods into functions instead. The advantage is now we can use other smoothing functions and untangle the smoothing from the BLEU implementation.
I've tried lambdas but it's rather crazy and unreadable so I think the only way is to use an object. I guess if the user really wants speed, he/she will create his own BLEU duck-type or SmoothingFunction duck-class =)

Looks good, just two suggestions.
Maybe it's better to define methods as classes that have __call__ method:

class Smotthing(object):

    def __init__(self, epsilon=0.1, alpha=5, k=5):
        ...

class Method1(Smoothing):

    def __call__(self, p_n, *args, **kwargs):  # might be a good idea to include args as well
        return [(p_i.numerator + self.epsilon)/ p_i.denominator
                    if p_i.numerator == 0 else p_i for p_i in p_n]]

alternatively, closures can be used:
def method1(epsilon=0.1, alpha=5, k=5):
    def inner(p_n, *args, **kwargs):
        return [(p_i.numerator + epsilon)/ p_i.denominator  if p_i.numerator == 0 else p_i for p_i in p_n]]

    return inner

Using __call__ would look a little weird, since the user would have to create N different objects to use N no. of different smoothing techniques. There's be another few more papers on BLEU smoothing and it might turn into a explosion of classes if we use __call__ and naming the classes might be quite hard =)
For now, we can still call it Smoothing/SmoothFunction but I think when more smoothing methods are added this might be called ChenAndCherrySmoothing.

that makes sense.

Thanks @alvations, and also @dimazest for timely feedback.


Space Trash-bin expiration cli

Description
Introduction of a new cli command to purge old trash-bin items.
The command is part of the storage-users service and can be used as follows:
storage-users trash-bin purge-expired.
The purge-expired command configuration is done in the ocisconfiguration or as usual by using environment variables.
ENV STORAGE_USERS_PURGE_TRASH_BIN_USER_ID is used to obtain space trash-bin information and takes the system admin user as the default OCIS_ADMIN_USER_ID.
It should be noted, that this is only set by default in the single binary. The command only considers spaces to which the user has access and delete permission.
ENV STORAGE_USERS_PURGE_TRASH_BIN_PERSONAL_DELETE_BEFORE has a default value of 30 days, which means the command will delete all files older than 30 days.
The value is human-readable, valid values are 24h, 60m, 60s etc. 0 is equivalent to disable and prevents the deletion of personal space trash-bin files.
ENV STORAGE_USERS_PURGE_TRASH_BIN_PROJECT_DELETE_BEFORE has a default value of 30 days, which means the command will delete all files older than 30 days.
The value is human-readable, valid values are 24h, 60m, 60s etc. 0 is equivalent to disable and prevents the deletion of project space trash-bin files.
Likewise, only spaces of the type project and personal are taken into account.
Spaces of type virtual, for example, are ignored.
Related Issue

Fixes https://github.com/owncloud/ocis/issues/5499

Motivation and Context
storage space is expensive, therefor we need a way to decide which files can be deleted and cleanup the trash-bin.
Todos:

[X] add events service
[X] use events to trigger the cleanup task (cli)
[X] get sufficient executant user
[X] error handling
[X] changelog
[X] unit tests
[X] add expiry configuration
[ ] talk to doc-team and provide information

How Has This Been Tested?

unit tests

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[X] Code changes
[X] Unit tests added
[ ] Acceptance tests added
[X] Documentation ticket raised:

:boom: Acceptance test wopiValidatorTests-ocis failed. Further test are cancelled...

@mmattel i could use a little doc magic help 😘

As todo and as discussed yesterday, we need to agree on a way how to describe command line calls. Currently we do have two commands which are:
ocis storage-users uploads
ocis search index --space $SPACE_ID --user $USER_ID
You can find both of them in the corresponding service readme/description.

As todo and as discussed yesterday, we need to agree on a way how to describe command line calls. Currently we do have two commands which are: ocis storage-users uploads ocis search index --space $SPACE_ID --user $USER_ID Note that both start with ocis You can find both of them in the corresponding service readme/description.
My proposal for this is the following:

As we currently and only ship the single binary containing all services, this binary is accessed with ocis and then the service name - this is what is currently reflected in the examples above and also in the readme's and admin docs.
As result we should put "ocis" infront of the example command in the changelog.
I will drop a note in the admin docs about what it means when we do a command example
If we change and not only provide a single but also service binaries, we have to:
Publish them accordingly
Change a lot of doc related stuff in the code, in ocis.dev and the admin docs

@mmattel thanks for your input, yes we discussed it in the scope of this issue, but the topic is broader and should not stop merging this pr. I see this as an thought anchor ;)

@fschade you also have to update the storage-users readme.md with the text of the new cli stuff accordingly. We will then update the admin docs based on that content.

@mmattel storage-users has no README.md yet. This is also not an easy task as it needs to explain what a reva is and also the differences to storage-publiclink , storage-shares and storage-system. Maybe better if that is done in a subsequent PR.

Maybe better if that is done in a subsequent PR.

Fine with that, but needs to be done. We now have the case where a readme needs to be created as discussed in our (big) doc meeting 😄 @fschade I am so in sorry 🤣

@mmattel i agree we need a README, but... it has nothing to do with this pr!
no creeping PR expanding please ;)


Server crashes immediately upon startup

Tried updating my server to using the latest source, but it ends up crashing.  Here's a screenshot of the error message.

Seems, db not updated.
You can use this script to update only items tables

I updated the items tables and everything's working like it should.


Is this a working Helmchart?

Hey @bsgrigorov,
I am wondering if your helm chart is working via ingress or if it only useable via a port-forward. I am not sure where my error is but somehow I am not able to get to cloudbeaver via configured url.
I mostly get an 504 / Bad Gateway. Since I am not allowed to run those Pods in root I added some things here and there.
kind: ConfigMap
metadata:
  name: cloudbeaver-service-conf
  labels:
    app.kubernetes.io/name: cloudbeaver-service
data:
  cloudbeaver.conf: |

    {
      server: {
        serverPort: 8978,
        serverHost: "rsome.url.com",
        serverName: "CloudBeaver Sample Server",

        // Paths are absolute or relative to the server root folder
        workspaceLocation: "workspace",
        contentRoot: "web",
        driversLocation: "drivers",

        rootURI: "/cloudbeaver/",
        serviceURI: "/api/",

        // Webapp configuration file
        productConfiguration: "conf/product.conf",

        expireSessionAfterPeriod: 600000,

        develMode: false,

        database: {
          url: "jdbc:h2:${workspace}/.data/cb.h2.dat",
          initialDataConfiguration: "conf/initial-data.conf",
          pool: {
            maxConnections: 100
          }
        }
      },
      app: {
        anonymousAccessAllowed: true,
        anonymousUserRole: "user",
        supportsCustomConnections: false,

        resourceQuotas: {
          dataExportFileSizeLimit: 10000000,
          sqlMaxRunningQueries: 3,
          sqlResultSetRowsLimit: 100000,
          sqlResultSetMemoryLimit: 2000000
        },
        plugins: {

        }
      }
    }
---
# Source: cloudbeaver-service/templates/persistenvoluemclaim.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name:  cloudbeaver-service-pvc
  labels:
    app.kubernetes.io/name: cloudbeaver-service
  annotations:
    volume.beta.kubernetes.io/storage-class: "cinder"
spec:
  accessModes:
    - "ReadWriteOnce"
  resources:
    requests:
      storage: 5Gi
---
# Source: cloudbeaver-service/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name:  cloudbeaver-service
  labels:
    app.kubernetes.io/name: cloudbeaver-service
spec:
  ports:
  - name: http
    port: 80
#    port: 8978
    protocol: TCP
    targetPort: 8978
  selector:
    app.kubernetes.io/name: cloudbeaver-service
---
# Source: cloudbeaver-service/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name:  cloudbeaver-service
  labels:
    app.kubernetes.io/name: cloudbeaver-service
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: cloudbeaver-service
  strategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app.kubernetes.io/name: cloudbeaver-service
    spec:
      restartPolicy: Always
      containers:
        - name:  cloudbeaver-service
          image: "/cloudbeaver:latest"
          imagePullPolicy: Always
          args:
          - -web-config=/etc/cloudbeaver/cloudbeaver.conf
          ports:
            - containerPort: 8978
              name: http
          env:
          - name: CB_ADMIN_USER
            value: admin
          - name: CB_ADMIN_PASSWORD
            value: admin
          - name: CB_SERVER_NAME
            value: test
          - name: CB_SERVER_URL
            value: some.url.com
          resources:
            limits:
              cpu: 500m
              memory: 450Mi
            requests:
              cpu: 150m
              memory: 220Mi
          volumeMounts:
            - name: data
              mountPath: /opt/cloudbeaver/workspace
              subPath:  cloudbeaver-service
            - name: config
              mountPath: /etc/cloudbeaver/
      securityContext:
        fsGroup: 1000
        runAsNonRoot: true
        runAsUser: 1000

      volumes:
        - name: data
          persistentVolumeClaim:
            claimName:  cloudbeaver-service-pvc
        - name: config
          configMap:
            name: cloudbeaver-service-conf
      imagePullSecrets:
      - name: secrets-harbor-registry-pull-secret
---
# Source: cloudbeaver-service/templates/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: cloudbeaver-service
  labels:
    app.kubernetes.io/name: cloudbeaver-service
  annotations:
    kubernetes.io/ingress.class: traefik

    cert-manager.io/cluster-issuer: acme
    traefik.ingress.kubernetes.io/router.tls: "true"
spec:
  rules:
    - host: some.url.com
      http:
        paths:
        - path: /api
          pathType: ImplementationSpecific
          backend:
            service:
              name: cloudbeaver-service
              port:
                name: http
    - host: some.url.com
      http:
        paths:
        - path: /cloudbeaver/
          pathType: ImplementationSpecific
          backend:
            service:
              name: cloudbeaver-service
              port:
                name: http
  tls:
    - hosts:
      - some.url.com
      secretName: cloudbeaver-service-tls-certs```

Yes ingress works. I use lets-encrypt for cert generation. https://github.com/bsgrigorov/dbeaver-helm/blob/main/chart/values.yaml#L34
Do you have nginx ingress controller installed in your cluster? That is a requirement to use the ingress resource I have written. Also you would need cert manager with lets-encrypt to generate the certs. There are other solutions you could use, but this is the one I have implemented.
https://cloud.yandex.com/en-ru/docs/managed-kubernetes/tutorials/ingress-cert-manager

The TLS connection works fine.
somehow I cannot connect to the backend of cloudbeaver from the ingress..
Could you send me your templated helm chart ? Of course remove all the sensitive data.


Computed properties should return null value by default

This issue needs to be merged into master before work on https://github.com/softlayer/sl-ember-components/issues/588 begins.  If it cannot be then work on it needs to be delayed until the release of v0.10.0


Consider changing impl of Highest sequence number more efficiently

While thinking about how we can avoid redundant deletes it got me thinking we can change read highest sequence nr by issuing a single query per partition rather than using the iterator e.g:
select inuse, sequence_nr from messages where persistence_id = ? and partition_nr = ? order by sequence_nr desc limit 1

As soon as inuse is null/false we can use the sequence_nr from the previous query.
C* keeps a partition index which means that going to the end is efficient (tho not as efficient as getting the first row in a partition).

+1, good idea


Incremental and Unsaved Support

Ideally we would support check as you type, but this require incremental type checking and unsaved file support in the Idris API. This would also allow diagnostics to be reported with a version. Haskell LSP's uses a VFS. Blocked by https://github.com/idris-lang/Idris2/issues/1187.

As far as I can tell the best way to solve this is to rewrite Idris to use a system similar to Rust's salsa. An example of something similar in Haskell is https://ollef.github.io/blog/posts/query-based-compilers.html


ui force to enter an email

Hi, nice UI, but i not need to type an email.
I can't pass empty field, asdasd doesn't work too, so need to type asd@asd please fix it (let folks to create account w/o emails)

Fixed in the linked PR.


kata-check: require kvm modules for amd64

KVM modules are required when using QEMU or firecracker.
Fixes: #1985
Signed-off-by: Marco Vedovati<EMAIL_ADDRESS>

/test

/test

/test

All tests are good, but we need a pair of reviews :-)
Calling in the usual folks :grin: @jodh-intel @grahamwhaley @devimc @jcvenegas


Linux version in the make?

Will there come a version of this that works on Linux as well?

As per #23, no.
Missinghud uses Windows DLL injection, and would require a significant
rewrite for Linux or OSX support.
On Mon, 8 Feb 2016, 23:27 XaeonBE<EMAIL_ADDRESS>wrote:

Will there come a version of this that works on Linux as well?
—
Reply to this email directly or view it on GitHub
https://github.com/networkMe/missinghud2/issues/59.


Separate either (and sum) functionality into own npm package

... or evaluate e.g. https://www.npmjs.com/package/data.either

:+1: for data.either


Update Fauxton dependency

Fauxton is currently pinned at v1.1.19. There's one new tagged version, which includes support for partitioned DBs. There are also a handful of fixes and enhancements on master that have not yet been tagged in a version. Leaving this as a placeholder so we don't forget about updating this in the 3.0 release cycle.

Closed via #2247


Keep errors while submiting to the server

What?
Hi, I'm using useServerAction to save some data into my server. It's working fine but I see a glitch while isPending
The errors in the server are reset and the UI jumbs.
This is my form:
  const { data, executeFormAction, isPending, error, ...rest } = useServerAction(
    onboarding,
    {
      initialData: { name, username },
    },
  )
  const errorData = error?.data
  const fieldErrors = error?.fieldErrors
  return (
      <Input
        label='Your username'
        type='text'
        name='username'
        errors={fieldErrors?.username}
        defaultValue={data?.username ?? errorData?.username}
        onChange={(e) => setUserName(e.target.value)}
        placeholder='Pick a username'
        description={<UsernameDescription username={currentUsername} />}
      />
  )

This is my action:
export const onboarding = authProcedure
  .createServerAction()
  .input(input, { type: 'formData' })
  .output(input)
  .experimental_shapeError(({ err, typedData }) => {
    if (err instanceof ZSAError && err.code !== 'INPUT_PARSE_ERROR') {
      return {
        code: err.code,
        message: err.message,
      }
    }

    return {
      data: typedData?.inputRaw,
      fieldErrors: typedData?.inputParseErrors?.formattedErrors,
    }
  })
  .handler(async ({ input, ctx: { user } }) => {
    await validateUniqueUsername({ data: input, user })

    const result = await finishOnboarding({ user, data: input })
    const value = result.unwrap()
    await updateSession({
      user: { name: value.name, username: value.username },
    })

    redirect('/')
  })

This is my UI. Check the disappearing red errors when submitting
https://github.com/IdoPesok/zsa/assets/49499/b17d4941-0091-4758-a184-23fd6c254177

Am I using it ok? Is there a way of avoiding this glitch?

Also, to keep previous data, I had to use shapeError and get typedData?.inputRaw. How hard would always be to return data already present in the form?
I say this because otherwise, all inputs are empty when one of them have a validation error no?

Hi, thanks for bringing this up!
I understand the issue. Going to compare with other libraries and report back shortly with next steps.
In the meantime -- if you want to try -- you should be able to get this persistence with useActionState. This also supports progressive enhancement.

always be to return data already present in the form?

Do you mean to return inputRaw in a default TZSAError without needing to do shape error?

Do you mean to return inputRaw in a default TZSAError without needing to do shape error?

Yes!

Using state gives me this TS error
I'm in latest zsa. In fact I'm debugging it locally with npm link

What version of React is this?

Also if you are using npm link, do you want to give the input schema functions a shot? Going to merge soon would be awesome if you can test that branch in your project and give feedback.

What version of React is this?

I'm living on the edge xD
{
    "next": "14.3.0-canary.59",
    "next-auth": "5.0.0-beta.19",
    "react": "19.0.0-beta-26f2496093-20240514",
    "react-dom": "19.0.0-beta-26f2496093-20240514"
}

Also if you are using npm link, do you want to give the input schema functions a shot?

I can try that. But would be ideal to use useServerAction
And out of the box get:

data persisted between attempts
Do not erase errors until the response come from the server (action)

But I think that would be ideal without needing to customize errors or other parts of the lib. It would make a straightforward understand of the model

Ah yes, I meant outside of this issue and related to #120 so you don't need to do validate unique username in the handler.

Ah!! yes yes I didn't understand you. Let me check that

Uhm, I'm not sure I'm using in the right way. I'm doing this

But debugging I see this

Looks I'm not returning a ZodType I'm returning a zodobject

Is this wrong?

If I force that my inputSchema is the one used

Then in the frontend it comes without formattedErrors it comes like a zod error

Ok looking more into the code this makes the error appear on the form fields

So if I understand correctly errors to be present not as a ZodError but as formatted errors needs to be processed by the final user (me)?

Hi, the formatted errors come from Zod formatted errors. Same thing with field errors, and form errors. These are standard Zod error schemas that people use. We can be more clear in our docs to explain this.

I see, but my question is. For having formatted errors do I need to use shapeError. I'll try with stable branch but i think it's working without that method

Doesn't matter for now anyway.
My feedback with the PR for input function is this
https://github.com/IdoPesok/zsa/issues/121#issuecomment-2170083331
Basically I'm not sure what I have to pass in the input
I'm passing a z.object but is failing
input(async ({ ctx }) => z.object(...), { type: 'formData'})

Yep, running tests in that PR it also fails

Test are passing in your PR but I saw you left a .only here https://github.com/IdoPesok/zsa/commit/0a085123f15af9aa358ceabc80133909eb2054e9#diff-0003458ed2aa52f7ec50b708d43d47e5f345bd88e8ecf56495befcc271207f1eR909

Sorry for all the spam 🙏 I'm trying to understand.
Doing these 2 changes it works. No need for custom shapeError
Looks like something related with instanceof but no idea why these 2 return false

Maybe is related https://github.com/colinhacks/zod/issues/2241

ALL_MY_FAULT 😂
Oh man, NodeJS is hard.
What happened is your monorepo use NPM and I was linking from my monorepo with pnpm link ~/code/opensource/zsa/packages/zsa and it was taking Zod from pnpm and so the instance was different when checking instanceof
What I did instead is
{
  "zsa": "file:../../../../opensource/zsa/packages/zsa",
  "zsa-react": "file:../../../../opensource/zsa/packages/zsa-react",
}

Fuck, this was a good lesson.
Your PR works great input(function) do what it promise 🎉

I'll move now to investigate the problems in this PR
OFF-TOPIC:
What's the use case for retry. Reading the code it makes everything more complicated. I'm courios to know what made you implement retries in this package. I can't imagine any good cases

Polling and caching

Yep, these are frontend concerns and because zsa already integrates with react-query there's no need to bring that complexity to this code.

Okay, I am going to move this conversation to https://github.com/IdoPesok/zsa/pull/124 as the code is there.

Nice, happy to change anything


Set cookie max Expires to 400 days

Description
Based on Replacement to RFC 6265, the max Expires SHOULD NOT be greater than 400 days.

Expires attributes that are greater than the limit MUST be reduced to the limit.

Thus, browsers crop the expires limit to this amount.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

It is draft-ietf-httpbis-rfc6265bis-latest, not RFC 6265.
The method name withNeverExpiring() will not match the behavior.
It is better to make deprecated the method and add a new one.

I stand corrected. The referenced internet draft is not RFC 6265, but is intended to obsolete and replace RFC 6265.

Authors:
L. Chen, Ed.
Google LLC
S. Englehardt, Ed.
Mozilla
M. West, Ed.
Google LLC
J. Wilander, Ed.
Apple, Inc

That's got some sign-off! This was just published (8/15) - anyone know the voting/implementation lifecycle of RFCs like this?

How is this a breaking change? I checked with Microsoft Edge today, and seems it is using the 400 days as expires of the request cookie. Well, aside from the tests expecting the expires of withNeverExpiring() to obviously change (but we don't have tests for that at the moment), the browser's request cookie will not have the expires at 5 years.

Change PHP code

diff --git a/app/Config/Routes.php b/app/Config/Routes.php
index ff2ac645c..4b1899517 100644
--- a/app/Config/Routes.php
+++ b/app/Config/Routes.php
@@ -36,6 +36,7 @@ $routes->set404Override();
 // We get a performance increase by specifying the default
 // route since we don't have to scan directories.
 $routes->get('/', 'Home::index');
+$routes->get('/yard', 'Home::test');

 /*
  * --------------------------------------------------------------------
diff --git a/app/Controllers/Home.php b/app/Controllers/Home.php
index 7f867e95f..d425bb207 100644
--- a/app/Controllers/Home.php
+++ b/app/Controllers/Home.php
@@ -2,10 +2,20 @@

 namespace App\Controllers;

+use CodeIgniter\Cookie\Cookie;
+
 class Home extends BaseController
 {
     public function index()
     {
-        return view('welcome_message');
+        $this->response->setCookie((new Cookie('cookie', 'monsters'))->withNeverExpiring());
+        return redirect()->withCookies()->to('/yard');
+
+        // return view('welcome_message');
+    }
+
+    public function test()
+    {
+        var_dump($_COOKIE);
     }
 }

Run php spark serve

Check Developer Tools > Network. Reload page. Check for the request cookie "cookie" and look for its Expires value.

Verify date shown.

This is Firefox.

Do we need the withNeverExpiring() method?
Why don't we just make it deprecated?

Yes let's deprecate it. If we have a feature that inherently creates differing behavior across browsers that's a detractor. I also don't like that this is called "never expiring" but sets for five years.
@paulbalandan?

See #6463


fix: Deposit no longer reverts if ETH transfer is not from Keep

We changed the value transfer semantics of the Keep bond. Now the seized bonds originate from the KeepBonding contract. Rather than adding an additional variable to enforce strict transfers from only the KeepBonding contract, we are going to remove the restriction for now.

Isn't it addressed in https://github.com/keep-network/tbtc/pull/602?

Good spot @pdyraga, wasn't aware @NicholasDotSol picked it up.


I/O needs cleaned up

The I/O R/W handlers need cleaned up. I did this (somewhat) on GameYob-Accurate and got a small speed boost. I recommend you do the same. I can start a pull request if you wish.

You can start a PR on my fork.

My fork is currently busted due to unknown ICE. Will start PR when I figure out how to fix it.

Fork fixed. Starting.


Navigating to routes when useHash=false

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[X ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

What is the current behavior?

Disabling hash navigation and navigating to any route that is not the root route renders the following
<% if (webpackConfig.htmlElements.headTags) { %> <%= webpackConfig.htmlElements.headTags %> <% } %> Loading... <% if (webpackConfig.metadata.isDevServer && webpackConfig.metadata.HMR !== true) { %> <% } %>
This only happens using the dev server. Production builds work as expected.  This seems to be the same or very similar to issue #762, which was marked as closed.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

Change on src/app/app.module.ts:50:
RouterModule.forRoot(ROUTES, { useHash: true })
to
RouterModule.forRoot(ROUTES, { useHash: false })

What is the expected behavior?

Expectation is that we navigate to the correct route (e.g. http://localhost:3000/home)

Please tell us about your environment:

Angular version: 2.0.0
Browser: Chrome

I am facing same issue....

The solution to #1056 did not solve the problem either. Tried removing all ^ from package.json, didn't work either.

@nekkon, thanks for pointing out the other issue -- I'll close this one as the problem is exactly the same as described there. Using the suggestion on #1056 issue worked for me: "webpack-dev-server": ">=2.1.0-beta.6" seems to break the useHash: false option.


expand and align the nav list in small screen devices

What it is?
Small style modification of the nav bar
Why?
It previously looked like this:

which is super ugly, because the li is meant to be the same width as the nav bar itself. Besides, it doesn't have any alignment.
Now it should look like this:

And it looks good on small screens as well:

Good job, very special thanks for you, @thomasyimgit  :smile:


core dumps not available in CIs

follow up from https://github.com/istio/istio/pull/2859/files/a2161fc50d0050bdbaa7557e834a047cbabbc552#r164282513
and https://github.com/istio/istio/issues/2906#issuecomment-361426521
it's important to gather core dump and show it working (and possibly add a test so that debugability feature doesn't regress)

have we seen at least 1 envoy core dump in some linkable build artefact so we know this is fixed indeed?

see also https://github.com/istio/issues/issues/196 for user question on whether/how it works

Closing this in favor of https://github.com/istio/istio/issues/6245 which has more info and is newer.

typically we keep the oldest/original issue in case of dup but ok

As I mentioned the new one has more info. =)


Remove RestApia v0.3.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/RestApia/RestApia.Community/releases/download/v0.3.0-dev/RestApia-dev-Setup.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 897)

Hi @NickRimmer,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 897.)

This version publish is unfortunately broken, and there is new higher version already
https://github.com/microsoft/winget-pkgs/pull/184090


fix: Orchestrator report entity error

Description
when recognizer is Orchestrator, report entity error in LU file.

Task Item
close #7151

Screenshots

related to #7201

Coverage increased (+0.02%) to 50.857% when pulling cb7da2090010ff17ee7839718afe15b6aa45dfd3 on zhixzhan/orchestrator-disable-entity into 1de395f4e39b7ed62fa709c6f177ce60d4afe9cc on main.


[DISCUSS] Required number of PR review approvals

Opening this as a community discuss issue to solicit some thoughts and feedback.
Before PR's are allowed to be merged the OpenSearch repository enforces a one approval requirement while the OpenSearch-Dashboards repository enforces two. The technical reason behind this was to test the CI load under two different requirements. The most costly CI task is ./gradlew check since it runs full unit, integration, smoke, and varying cluster tests. Depending on the level of collaboration and PR churn, we wanted to make sure we balanced the CI load to keep up with demand (of course we can always work to throw more compute power if needed).
While we gather some of this information in the early days of the project, we also wanted to solicit thoughts from the community around these kinds of requirements to avoid unilaterally making decisions. I'm curious what the community would like to see? One approval requirement? Two approval? Of course I think this will vary by repository and possibly even by feature implementation (since some features or repositories might demand more expert domain knowledge than others).
Discuss, post thoughts, don't hold back.

@nknize what would be the non-technical reasons/advantages to ask for more than one approval?

I would recommend a 2 PR review to prevent malicious code. Especially for scenarios like these. https://www.zdnet.com/article/open-source-software-how-many-bugs-are-hidden-there-on-purpose/

That's a good question @dblock! I'm curious what others think here and @bbarani raises one good reason. Another might be to try to discourage "buddy commits"?  I'm all for low friction, but I've seen a one approval requirement resulting in back-channeling a buddy to approve your PR so it can be quickly merged?

I don't think there should be a hard minimum on the number of approvals required for change!
Rather, it should be at the discretion of the committer who pushes the change.  And each committer here can gracefully learn over time where that threshold/bar should be.
E.g. some PRs can and should go in, immediately, with zero approvals, such as a trivial change fixing a typo in a comment or exception message.  Others are super hairy and possibly controversial and should see good discussion/iteration from many developers before pushing.  Let our CI builds, or the automatic gradle check for each PR, catch any silly mistakes that cause test failures.  Let's lead by example on how to fully utilize AWS resources to integrate automation to catch such honest accidents.
There are indeed horror stories, like @bbarani's example above, of malicious code sneaking into and being released from important open-source projects.  Yes, it is a real risk, but it is not common, and we should not design our development rules/practices around such rare exceptional cases.  Rather, design them for the common case where a developer is trying to make an honest, good, important, helpful change and we seek to absolutely minimize the friction, especially for new developers.
E.g. not requiring an iCLA is a delightful and refreshingly obvious approach to reducing friction for new developers.  I was at Elastic when they decided to add the "mandatory iCLA" and fought (and clearly failed) to prevent such a nasty requirement of new community members.
Also, remember that even after a change is pushed, other developers in the community can and should still look at what was pushed and raise objections, make a follow-on PR to improve it, ask for revert, etc.  It is not until the bits are set free in an an actual GA release (hmm: do we have a community process for voting on releases yet?) until possible damage from malicious changes and accidental bugs might have impact.
And we can/should seek to statically reduce that possibility, e.g. we already removed Elasticsearch's sneaky and dangerous "phone home" feature in OpenSearch, we should double down on the JVM security manager so OpenSearch runs inside a "self imposed Java jail", etc.

So refreshing to see this kind of healthy dialogue in the open!

do we have a community process for voting on releases yet?

Great question!!! There's a WIP discuss issue for that! that needs fixing and input from you folks that are much smarter than me!

remember that even after a change is pushed, other developers in the community can and should still look at what was pushed and raise objections, make a follow-on PR to improve it, ask for revert, etc.

SUCH an important point about OSS and transparency here! These definitely are not one-way doors and there is always room for improvement.

we should double down on the JVM security manager so OpenSearch runs inside a "self imposed Java jail", etc

Oooh!!!! We need a "help wanted" issue for this! I bet there are some contributors out there willing to make this happen!

So refreshing to see this kind of healthy dialogue in the open!

+1, these are vital ground rules for building a healthy truly open community.

we should double down on the JVM security manager so OpenSearch runs inside a "self imposed Java jail", etc

Oooh!!!! We need a "help wanted" issue for this! I bet there are some contributors out there willing to make this happen!

OK I opened #528 for this!

I agree with @mikemccand, there should be one mandatory reviewer, and that's the automated one (github action, bot, whatever calling the appropriate gradle)
Java is so ripe for static analysis, but lots of projects don't even fail on warnings from javac (I haven't checked the setup here). At apache lucene, we also use the ecj compiler to do a separate pass since it has a bunch of additional checks. For style consistency we just enforce everything is formatted with gradlew tidy (uses spotless) and that's another thing not to worried about. Maybe some of this build logic can be easily poached from lucene's gradle build?
Better to make use of the human time with higher-level review.

there should be one mandatory reviewer, and that's the automated one

I agree with this. The more "fail early" checks that can be automated the better, and leave the overall logic flow to human review.
There's quite a bit poached from lucene's build but a lot more that I think could be leveraged. Another area that could use some help. Spotless is used here so that helps for code consistency, and there's a feature branch to bring in the javadoc enforcements that Lucene has to ensure at least the public facing APIs are documented instead of relying on a separate asciidoc or markdown "documentation" repo that is never enforced to be updated by the original author.

I think we should define maintainer areas of responsibility as suggested here #537.
We have good documentation on how and when to create a PR. But what happens once the PR is raised is missing. e.g. after how long should I wait to follow-up for starting gradle checks or what is the criteria to start it? How is a reviewer selected for a particular module? Once a PR is approved by seasoned reviewers, how long before it is merged or at least how long before any update on the merge is expected.

we already removed Elasticsearch's sneaky and dangerous "phone home" feature in OpenSearch

Some quick followups/corrections about my statement from above:

It is Kibana (NOT Elasticsearch) that has the "phone home" feature
This feature is indeed enabled by default as described here: https://www.google.com/url?q=https://www.elastic.co/guide/en/kibana/master/telemetry-settings-kbn.html%23telemetry-general-settings&sa=D&source=hangouts&ust=1618598703063000&usg=AFQjCNH9NoIuADga_Vgwgjlha-3Pz4OE9A
In OpenSearch, we have not removed this feature, but rather turned it off by default so users can freely decide whether they want to enable it, and also so the OpenSearch developer community can decide what to do with this feature going forward

More details here: https://discuss.opendistrocommunity.dev/t/preparing-opensearch-and-opensearch-dashboards-for-release/5567
Thanks @s1monw and @nknize for clarifying!  High velocity code base here, yay :)

We've generally tried to document the review process here. What should we do with this issue?

Based on the comments above, I've set branches to have 1 approver required.  Happy to revisit this at a later date if we want to add more or remove the constraint.
Thanks!
/C


Instant Article Facebook

This is another question:
I could see the instant article feed from my blog when accessing /blog/feed/fb/  (http://www.twistsystems.com/pt-br/blog/feed/fb/)
However, I can't tell how to publish in Facebook as a Instant Article. Is it possible to do it? In a way the FB post appear with the lightning  symbol?
Thanks

You must setup instant articles in your facebook page and add the feed as the "live feed" and let facebook load the articles from the feed. You can follow FB documentation for complete guide on how to set it up https://developers.facebook.com/docs/instant-articles/publishing/setup-rss-feed

Thanks!!! Pretty straight foward! this could be written on the docs! I could not find the step-by-step...


backport 1.4 2019 05 29

PR: #7982 -- daemon: Remove stale maps only after restoring all endpoints (@brb)
PR: #8014 -- envoy: Do not use deprecated configuration options. (@jrajahalme)
PR: #8017 -- cilium: IsLocal() needs to compare both Name and Cluster (@jrfastab)
PR: #8010 -- daemon/Makefile: rm -f on make clean for links (@aanm)
PR: #8066 -- pkg/endpoint: fix assignment in nil map on restore (@aanm)
PR: #8105 -- Recover from ginkgo fail in WithTimeout helper (@nebril)
PR: #8097 -- proxylib: Fix egress enforcement (@jrajahalme)
PR: #8149 -- envoy: Prevent resending NACKed resources also when there are no ACK observers (@jrajahalme)

@jrajahalme I had to bump the revision number of cilium/proxy in Gopkg.toml so I could be able to backport PR #8014.

This change is

test-me-please

Bumping cilium/proxy version should be OK, as we have earlier already bumped the actual proxy version due to the CVE fixes.

test-me-please

test-missed-k8s

test-docs-please

test-me-please

test-missed-k8s

test-me-please

test-docs-please

test-upstream-k8s

test-missed-k8s

@raybejjani please take a look at the last commit

test-upstream-k8s

test-docs-please

test-missed-k8s

test-me-please

test-upstream-k8s

test-me-please

test-me-please

test-missed-k8s

test-upstream-k8s

test-docs-please

test-me-please

test-me-please

test-me-please

test-me-please

test-missed-k8s

test-upstream-k8s

test-docs-please


question/request.

Hi, first of all, great tool, i like it great job.
My question though. it would someone be a great addition to do a true passive lookup of ip of domain. Some of these lookups do a active lookup if i am not mistaking which could mean that a actor could pickup these signals on their end and change ttp's / ip's or domains, this would result in losing the 'defenders advantage'
regards,
Mike

As far as I am aware, the only one not doing a passive lookup is https://otx.alienvault.com/ for the domain info. Everything else is cached results as far as I know. Please correct me if wrong.

Hi, interesting, yeah thats really the question what does other sources do, you could be right, cached would imply that the lookup has already been done one way or another, which in new adversary infra i can't imagine that would the case though, but not really sure. The last thing i want to do is give of possible signals because of a active lookup triggers unexpected traffic on the adversary infra.

So going through the individual websites, virustotal is cached, abuseipdb is cached, whois is cached, torrelay is cached. The only website I believe would alert the source entity is alienvault which is located under IPInfo. Again, if you find an alternate answer please let me know.


I want to make a built-in anti-clipper feature for Wasabi Wallet.

A few days ago, while sending bitcoin to someone via Wasabi wallet, I sent bitcoin to another address (the attacker's address) because of the clipper. this is not the Wasabi wallet's problem, of course, but my question is: if someone wrote a built-in anti-clipper code for Wasabi wallet and made a pull request, would you accept it? If I was a wallet maintainer I would definitely add this kind of feature. If you give me the green light that if I make this kind of anti-clipper PR you will add it to the main code I would be happy to do this kind of project

Hi,
Useful pull requests are always welcome.
I'm not sure about your proposal, but that might be my lack of understanding.
How would it work? How would you implement it?
Wasabi assumes that the computer the software is running on is secure. Having (clipboard) malware falls under this, so it seems out of scope of the Wasabi software.

Maybe others have more insights/feedback to this...

If code is easy to review, maintain, doesn't add any dependency and feature is slick, then of course. We could even help you.
To be sure please detail the technical concept here before starting to code.

I can describe the way of working as follows. If what is copied to the clipboard is a btc address, Anti-Clipper takes a note of that address and then periodically tests if it is the same address as the one on the clipboard. if it is the same address, no problem. if it is not the same address, it changes it to the old address and notifies the user. The advantage of this anti-clipper is that it catches every clipper, not just clippers that were caught a while ago like antiviruses do. If you have any other questions I will be happy to answer them.

This topic had been discussed many times in the past, in fact, I created a PR to play with and evaluate the alternative https://github.com/WalletWasabi/WalletWasabi/pull/697 however if the user's computer is compromised there is nothing application developers can do.

Here is the same reasoning but better explained: https://github.com/WalletWasabi/WalletWasabi/issues/3658#issuecomment-629918853
NACK.

@btcspectrum Weird that the same problem happened to you with Electrum and you opened an issue with the same description https://github.com/spesmilo/electrum/issues/9230 as this one. ;)


bx-lg class does not work in 2.0.3

In the minified version at<EMAIL_ADDRESS>the  "rem" unit in .bx.lg is missing.
It should be .bx-lg {font-size:3.0rem!important} to work. The unminified version it's ok though.
At first it is not evident because in https://boxicons.com/usage/#sizing you are using a non-exitent icon "smiley-happy" bringing an empty frame in the demostration.
If you use i.e. "smile" you'll see the effect clearly:

BTW thank you for your great work!

please can you check again, its working

This still appears to be an issue, the rem unit is missing in the minified css:
.bx-lg{font-size:3.0!important}

https://github.com/atisawd/boxicons/blob/master/css/boxicons.min.css


[$750] [MEDIUM] Update Recents in Participants page to reflect the type of action taken

Problem
Coming from this discussion.
When taking some action like requesting money or assigning a task, the participants page does not take the type of the action into consideration when creating the list of Recents. We list out the people/ workspace chats we have interacted with the latest even if we have for example never requested money from them.
### Solution
Update the Global create participants page Recents list to showrecents based on the type of action user is taking.
So if they are taking:

creating scan request
creating distance request
creating manual request
creating task
creating split bill

for each of these, try to pick the recents such we list first the chats where the user has most recently done such action. If no data to do this optimization is available, default to the current behaviour
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b6cc63ba2f30aad7
Upwork Job ID:<PHONE_NUMBER>206743552
Last Price Increase: 2024-02-05
Automatic offers:

rojiphil | Contributor | 28122004

cc @trjExpensify - we were chatting about this one today

@mountiny do we need to get this into a Wave or VIP?

It's on the wave6 project board already, but yeah.. needs progressing. Vit can maybe confirm if it needs to stay internal or not.

I think we can try this Externally. We would need to look through the trasactions and then identified the reports which we requested that given type of action latest from

Not sure from your message, flow Global Crete:

I choose Manual request
I choose scan and take picture
on the participant page the recents should list the latest in choronological order chats I have requested money with scan request.

If there was no scan request before, just keep the current logic
If there would be only one or less than current recents, just show that number of chats (so there could be only 1 in recents) this is up for discussion though
Same goes for other types. For tasks this might be hard to do for requests it should be possible as we should have all the transactions locally

Proposal
Please re-state the problem that we are trying to solve in this issue.
We list out the people/ workspace chats we have interacted with the latest even if we have for example never requested money from them. The same problem can be extended to tasks as well. We want to solve this problem by displaying the
recent list in the participant page such that recent reports based on the type of action taken by the user are displayed.
What is the root cause of that problem?
This is a new feature.
The scope is as follows:

Show recent reports based on the following type of actions chosen by user
a) Scan Request creation b) Distance request creation c) Manual request creation d) Split bill creation e) Task creation
For each of the above, try picking recents for the specific type of action. If no such results are available, show the recents based on current behaviour which is the default one.

What changes do you think we should make in order to solve the problem?
For money request action involving various types of requests, the participant list is displayed through IOURequestStepParticipants. This page makes use of MoneyRequestParticipantsSelector here.
So, the first thing to do is to determine the type of money request action by relying on iouRequestType and number of participants like this here:
const actionType = iouType === CONST.IOU.TYPE.REQUEST && participants.length > 0 ? CONST.IOU.TYPE.SPLIT : iouRequestType;

Further, we can pass actionType to getFilteredOptions here.
To implement this, we can add a helper method in TransactionUtils called getTransactionsByRequestType which will help us to get the transactions based on the action type. This helper method implementation can be like this:
function getTransactionsByRequestType(iouRequestType?: string): Array<OnyxEntry<Transaction>> {
    return Object.values(allTransactions ?? {})
        .filter((transaction): transaction is Transaction => transaction != null && (iouRequestType === CONST.IOU.TYPE.SPLIT ? isSplitRequest(transaction) : getRequestType(transaction) ===  iouRequestType))
        .sort((transactionA, transactionB) => {
            const transactionATime = new Date(transactionA?.created);
            const transactionBTime = new Date(transactionB?.created);
            return transactionATime.valueOf() - transactionBTime.valueOf();
        })
        .reverse();
}

Also, since there is no helper method for identifying split request, we can add a helper for this by checking against comment.source like this:
function isSplitRequest(transaction: Transaction): boolean {
    return Boolean(transaction?.comment?.source === CONST.IOU.TYPE.SPLIT);
}

Now, we can retrieve the recent transactions based on the action type like this here:
    const isMoneyRequestActionType = actionType === CONST.IOU.REQUEST_TYPE.MANUAL || actionType === CONST.IOU.REQUEST_TYPE.SCAN || actionType === CONST.IOU.REQUEST_TYPE.DISTANCE || actionType === CONST.IOU.TYPE.SPLIT;
        let recentTransactions = [];
        if (isMoneyRequestActionType) {
            recentTransactions = TransactionUtils.getRecentTransactionsByRequestType(actionType );
        }

And, then, populate a new array recentReportOptionsByAction based on action type like this here:
        if (isMoneyRequestActionType && recentTransactions.some((transaction) => transaction.reportID === String(reportOption.iouReportID))) {
            recentReportOptionsByAction.push(reportOption);
        }

        // Stop adding options to the recentReports by action array when we reach the maxRecentReportsToShow value
        if (recentReportOptionsByAction.length > 0 && recentReportOptionsByAction.length === maxRecentReportsToShow) {
            break;
        }

Similarly for tasks, we can pass CONST.REPORT.TYPE.TASK as actionType in TaskAssigneeSelectorModal here. Further, we can push the reportOption for tasks to recentReportOptionsByAction like this:
            if (actionType == CONST.REPORT.TYPE.TASK && reportOption.isTaskReport) {
                console.log("PROCESSING actionType[TASK], reportID["+reportOption.reportID+"]");
                recentReportOptionsByAction.push(reportOption);
            }

Finally, when available, we can display recent reports based on recentReportOptionsByAction or fallback to the existing recentReportOptions here like this:
         recentReports: recentReportOptionsByAction.length > 0 ? recentReportOptionsByAction : recentReportOptions,
What alternative solutions did you explore? (Optional)

cc @shawnborton would you want to assign this one to yourself to oversee the correct logic implementation?

I would prefer that someone from BZ or the project team oversees it, but happy to help test and guide implementation.

@eVoloshchak can you review the proposal above?

@rojiphil's proposal looks good to me!

iouRequestType?: string

We can use iouRequestType?: ValueOf<typeof CONST.IOU.REQUEST_TYPE>
🎀👀🎀 C+ reviewed!

Melvin, what a prankster

Thank you for the assignment here.
I will start work on this today and provide an update over the weekend.

Not overdue, PR is being drafted by @rojiphil

Update: Will share PR for review by tomorrow this time.

@mountiny @eVoloshchak
Do you think we can consider an increase in the bounty here?
The reason why I think so is that I notice quite a lot of thoughtful work involved due to the sheer number of test cases involved here.

Increased to 750, noting that a regression still cuts the price in half though so please be thorough as possible in testing. Thank you

This should be open, the PR is still in review (recent changes broke the logic a bit)

Agreed!

Still waiting on linked PR to be merged

PR still open

I am still torn on this implementation. It seems to be bringing really complex changes to the App to try to deduce the recent target accounts for various actions, but its not reliable (as we might not have the report actions available after signing in) and the changes are hard to follow.
I am now more inclined towards a solution with backend change similar to the quick action button if we really want this feature. this would simplify the logic and code.
Whenever user takes some action from the global create flows, we would update an NVP with the target reportIDs, it would basically be same as the QAB NVP, but we would keep rolling history of the 5 recent reports for any given flow.
@rojiphil @eVoloshchak you have been battling with the implementation but it seems like there has been numerous small issues with your solution and the code is hard to follow, what is your opinion?

Thinking of this a little further, this is what I could I arrive at:

We can take the advantage of quick actions here which would map to the mentioned flow:

        REQUEST_MANUAL==> MANUAL
        REQUEST_SCAN==> SCAN
        REQUEST_DISTANCE==> DISTANCE
        SPLIT_MANUAL==> SPLIT
        SPLIT_SCAN==> SPLIT
        SPLIT_DISTANCE==> SPLIT
        TRACK_MANUAL==> MANUAL
        TRACK_SCAN==> SCAN
        TRACK_DISTANCE==> DISTANCE
        ASSIGN_TASK==> TASK
        SEND_MONEY==> MANUAL

The following Onyx entries will be added:

	np_recent_manual_requests
	nvp_recent_scan_requests
	nvp_recent_distance_requests
	nvp_recent_split_requests
	nap_recent_tasks

Each of these will hold the flow specific array of reportIDs with rolling history of the 5 recent reports

For every quick action that reaches BE, the BE will push the report ID in the flow specific nvp_recent_* list and send/push the updated entries to FE.

The FE will also optimistically update the flow specific nvp_recent_* Onyx entries by pushing the reportID.

While displaying recent list, the FE will use the flow specific Onyx entries. If not present, the default one will be displayed as shown currently.

We also need to remove the redundant reportID from the recent list in certain cases like leaving a group chat. Also, BE need to update the recent list in such cases and push the updated entries back to FE.
Also, there would be cases where a report is not present in Onyx but is present in recent list. Such reports would also be not shown in recent list. So we might end up with less than 5 entries in recent list on removal of such reports. Hope this is fine.

@mountiny Is this what we are aiming for? Or are there any changes required?

I think we would need to hold internal discussion about this, currently focusing on higher priority tasks though

No update

Not overdue

This task showed up to be quite of a rabbit hole. A proper solution would require a backend changes too something similar along the lines of QAB but we did not really prioritise this. Instead we are trying out this change https://github.com/Expensify/App/issues/46683 and lets see if it will be enough from the UX perspective.
I think we could close this issue out for focus @trjExpensify what do you think? We can always come back to this if we want to prioritize creating a proper fix for this. We would of course pay some reward for the effort

Yep, works for me!

We would of course pay some reward for the effort

@mountiny Thanks for mentioning this. I also think this deserves to be rewarded as quite a lot of effort went into it from my side. Would $500 sound fair here instead of the actual price of $750?
Reasonings:

The PR itself needed a lot of work to cover about 7 different test cases as mentioned in the OP here
Quite a lot of review cycles occurred here which included verification via Timing tests apart from regular re-reviews that spanned for almost about 2 months.

@rojiphil Yes I think thats valid. I would go for 50% of the planned amount so $375, how does that sound? @eVoloshchak

@mountiny, yeah, a 50% payout seems fair to me

I would go for 50% of the planned amount so $375, how does that sound?

Thanks @mountiny.
Maybe we can make this issue daily to close on this sooner.
cc @muttmuure

Handling

$375 - @rojiphil
$375 - @eVoloshchak

@eVoloshchak please submit your request in New Expensify!

$375 approved for @eVoloshchak


Update x/sys and x/net modules to support Risc-V

Updating projects using libraries that were recently updated to support Risc-V.
Go upstream work is tracked on: golang/go#27532
Risc-V software support tracker on https://github.com/carlosedp/riscv-bringup

@simonpasquier just confirmed that with x/sys and x/net updated on upstream, promu builds with no change since these requirements are indirect.
Thanks!


Does not support Common Parameters

The library currently does not support "Common Parameters for All Methods of a Path":
Parameters shared by all operations of a path can be defined on the path level instead of the operation level. Path-level parameters are inherited by all operations of that path. A typical use case are the GET/PUT/PATCH/DELETE operations that manipulate a resource
accessed via a path parameter.
paths:
  /user/{id}:
    parameters:
      - in: path
        name: id
        schema:
          type: integer
        required: true
        description: The user ID
    get:
      summary: Gets a user by ID
      ...
    patch:
      summary: Updates an existing user with the specified ID
      ...
    delete:
      summary: Deletes the user with the specified ID
      ...

Reference: https://swagger.io/docs/specification/describing-parameters/

ooh, thanks for the report.  Will probably get to this soon


Avoid errors by checking presence of special files

It might be possible to avoid some common errors by checking the presence of some special files.

[ ] Check if file is open by checking if .str.lck file exists.
[ ] Check if results are present in model by checking id .strFEM file exists.

@andosca Can we include this in the 21.2.0 milestone? I think it makes sense to make this update together with the new result reader functionality.

Makes sense. Thanks!

@xRadne
where are you thinking to use the presence of the .str.lck ?
When should we warn the user?

.strFEM should be use when the users wants to read certain results (i.e. ReadModel str in Grasshopper)

I suggest the check is done in the method RunFdScript. Right after the processes have been killed on line 160. Then the code should go through all .str paths in the FdScript and check if anyone also have a .str.lck. If it finds a .str.lck then an error should be thrown I think.
https://github.com/strusoft/femdesign-api/blob/8387cdb1ee438620727d142bafa231c2d7efd706/FemDesign.Core/Calculate/Application.cs#L143-L203
The .strFEM check should only be done if there are any ResultTypes or Bsc paths as input to the ReadStr methods (C#, GH, Dyn).

@xRadne
I was going through the code and I am not sure if it is worth to implement the .str.lck check if we have the CheckOpenFiles Method.
Am I missing something?
It looks like that the file is available only when the process is running.
What kind of error are we trying to catch?
'.strFEM' has been done

The reason I would like .str.lck is because the GetOpenFiles is not a perfect solution but just a hack that works for most users.
But .str.lckwill always work since FEM-Design will always create the .lck file when the .str is locked.

Perfect. It makes sense.
I fully understand the reason!  ๑(◕‿◕)๑


Implement ETag and Last-Modified HTTP Header Support

Implement support for ETag/If-None-Match and Last-Modified/If-Modified-Since HTTP headers. This should dramatically speed up static websites as the response bodies will be empty when the file on the server hasn't changed.

This has been fixed with version 0.12.0 commit: a4e506b020b3cd1715aa666684b29872cfa51ac7


Db contrib/db contrib develop

:white_check_mark: Build plexus-interop 0.3.0-281 completed (commit https://github.com/finos-plexus/plexus-interop/commit/07ebd68ced by @nikoant)


SyncTrayzor not Rendering GUI in Internal Browser Window

I have 3 installations of SyncTrayzor running on 3 different computers. All three sync flawlessly and two have no GUI issues at all. On my HP laptop (Win 10 IoT Enterprise LTSC) SyncTrayzor, as mentioned above, syncs without issue, but double-clicking the tray icon to open the SyncTrayzor window reveals only a blank internal window with a functioning syncthing console window at the bottom. I've stopped and restarted, rebooted, exited, refreshed, and nothing seems to work. Interestingly, selecting "Open in external browser" brings up a fully-functional GUI in an external browser window, which is how I currently interact with this instance of SyncTrayzor, but it's not optimal.
The only way I have been able to get something to render in the internal browser is by unchecking the view of the syncthing console. As soon as I do this, the GUI shows in the internal browser, but is frozen - no buttons can be pressed and no settings dealt with. Interestingly, after trying to interact with the frozen GUI, when I choose to view the syncthing console again, the GUI suddenly updates as if my earlier mouseclicks were processed -- an expanded folder view, etc -- but remains frozen.
I'm curious if SyncTrayzor is "borrowing" any particular browser engine that may exist on the computer to render its internal browser GUI and if that is somehow mapped wrong on this installation instance? To the extent it helps, I have Edge, IE, Chrome and Firefox on this laptop.

Did you try to disable hardware rendering?

I'm having the same issue. Did you find any solution?

Unfortunately, no
On Fri, Sep 16, 2022, 8:13 AM deluxestyle @.***> wrote:

I'm having the same issue. Did you find any solution?
—
Reply to this email directly, view it on GitHub
https://github.com/canton7/SyncTrayzor/issues/681#issuecomment-1249289700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AETUX2KLR5HYDUYI7A4PLD3V6RP6XANCNFSM5MC5LHSQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I started having this issue a few days ago as well. I believe it happened after I updated my NVIDIA drivers. It was working fine before that. Disabling hardware rendering fixed the issue for me as well.

I had to disable hardware rendering to get the application to display on my Intel Arc A770. But it worked when I first installed the application! Strange.

I wasn't able to find "disable hardware rendering" but was having this issue on multiple PCs. In the application properties "compatability" tab, enabling the option "Disable fullscreen optimizations" brought the interface back on at least two machines.

Same issue here. Except for me, toggling the Console doesn't make the GUI appear. Nor any of the fixes suggested above.All options related to the Browser in the SyncTrayzor upper menu are greyed out, so I can't press F5 to launch in external browser. The screen just stays stuck on "Starting SyncThing..."
If I attempt to navigate to the GUI directly (by typing the localhost path into my firefox window) i get hit with a prompt for Username and Password. I don't remember ever setting up a user/password for SyncThing, so no clue what to do here.
In the console window, SyncThing seems to actually be working in the background just fine. I just can't access the GUI at all.


Pass more than one parameter

I know it is possible for me to pass a parameter to an action as follows:
$router->add('{controller}/{action}/{id:\d+}');
public function indexAction() {     View::renderTemplate('Sobre/index.html'); }
But how can i pass, two or more parms to the router and get there parms into the action.
Sorry my bad english.

You can have as many variables as you like in a route. You can then get them in the route_params property. For example:
$router->add('{controller}/{action}/{id:\d+}/{slug:\w+}');
Then in the action:
public function indexAction()
{
   $id = $this->route_params['id'];
   $slug = $this->route_params['slug'];
}

Is that what you meant?

Could you not pass an array?

that's what I meant, thank you very much

Could you not pass an array?

I'm afraid not, that's not how the framework works at the moment with parameters.

Could you not pass an array?

I'm afraid not, that's not how the framework works at the moment with parameters.

Hi @daveh will it be possible with the new version? Many thanks

@vince844 I'm not sure what you mean - each URL segment (e.g. /segment1/segment2 etc.) can correspond to a variable, so  you could have something like this: /users/123/orders/345/product-1 and so on. As the URL is a string, each segment can only ever be a simple string too. If you want several values, then just have several route variables / segments.

I want to update the data .So I tried to pass it with the traditional system of php (i.e  list?id=1)...than i am not able to get this id by using $_GET method.

If you're updating data, you should really be using POST. If you have values in a form using the POST method, you can get them in the $_POST array.

I have this route:   $router->add("product/{id}/{slug}","ProductController@index");
I always pass id but slug is optional
how can I define the optional parameter?

@mosafer72 You can't do that with a single route in this framework, you'd have to add two routes:
$router->add('product/{id}/{slug}', ['controller' => 'Product',  'action' => 'index']);
$router->add('product/{id}', ['controller' => 'Product',  'action' => 'index']);

Plus, the controller and action are specified as individual array elements above, not as in your example (unless you've modified the router)

Take a look at this pull request #73 to allow one or more parameters, without need to create a route for every method. I think can be useful for most simple requests.


vite build same package framer-motion

vite build same package framer-motion
Different framer-motion versions may cause AnimatePresence to fail to detect shutdown
@acrool/react-xxx -> Project

create directory ./example/_components/WithYoutubeCard

release test to<EMAIL_ADDRESS>


fix: Removes Assignee from issues.yml

This PR removes the Assignee from the github action so that the created JIRA ticket is not assigned to a user.

Type of change:

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

Required Checklist:

[ ] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation (if appropriate)
[ ] I have run make fmt and formatted my code
[ ] I have tested the CDK constructor in a CFN stack. See TESTING.md

Further comments

were you able to test it or it's not possible to use a github action in a branch to be triggered for a new issue?

@lantoli I tested it here https://github.com/andreaangiolillo/cdk-test/issues/41

@lantoli I tested it here andreaangiolillo/cdk-test#41

nice!


Added setting in feedback policy about screenshot collection

Feature is documented here: https://docs.microsoft.com/en-us/powershell/module/skype/set-csteamsfeedbackpolicy?view=skype-ps

Docs Build status updates of commit 6e0320b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/manage-feedback-policies-in-teams.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 2425b8c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/manage-feedback-policies-in-teams.md
:white_check_mark:Succeeded

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

@MikePlumleyMSFT PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Tweak verify-pipeline so future violations work

There's a rego bug in ec-policies that means the future policy
violations are not handled correctly if data.config is missing
entirely.
This is a quick workaround for the demo. Hopefully the rego bug will
be fixed later properly and the workaround won't be needed.

I'll merge it for demo in 40-ish minutes.


Update cs.json

Updated CZ strings.
But thee is one string "end_password_change" - from context, I am not able to determine, what is this for. Can you explain in detail, what is this string for?

Thank you! The end_password_change is actually not used, and will be removed, so please ignore for now.
Best / Bo
Bo Lincoln, PhD, CEO
Iternio Planning AB

On 1 Dec 2022, at 10:04, Betacart @.***> wrote:
Updated CZ strings.
But thee is one string "end_password_change" - from context, I am not able to determine, what is this for. Can you explain in detail, what is this string for?
You can view, comment on, or merge this pull request online at:
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358 https://github.com/Iternio-Planning-AB/abrp-translations/pull/358
Commit Summary
c98b74d https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/commits/c98b74dc2d90474fee5afd61694f410302ab56ae Update cs.json
File Changes (1 file https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/files)
M cs.json https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/files#diff-dd2253f9178515dc6077d3ee2d8254ec8926e88439b4f7bc4266065024464b18 (10)
Patch Links:
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.patch https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.patch
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.diff https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.diff
—
Reply to this email directly, view it on GitHub https://github.com/Iternio-Planning-AB/abrp-translations/pull/358, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOLDEAU76JOZLV35XXXGUL3WLBS3JANCNFSM6AAAAAASQRH3YE.
You are receiving this because you are subscribed to this thread.

Got it, I leaved it untranslated.
Thanks for quick note!
Jirka
čt 1. 12. 2022 v 10:25 odesílatel Iternio @.***> napsal:

Thank you! The end_password_change is actually not used, and will be
removed, so please ignore for now.
Best / Bo
Bo Lincoln, PhD, CEO
Iternio Planning AB

On 1 Dec 2022, at 10:04, Betacart @.***> wrote:
Updated CZ strings.
But thee is one string "end_password_change" - from context, I am not
able to determine, what is this for. Can you explain in detail, what is
this string for?
You can view, comment on, or merge this pull request online at:
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358 <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358>
Commit Summary
c98b74d <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/commits/c98b74dc2d90474fee5afd61694f410302ab56ae>
Update cs.json
File Changes (1 file <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/files>)
M cs.json <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358/files#diff-dd2253f9178515dc6077d3ee2d8254ec8926e88439b4f7bc4266065024464b18>
(10)
Patch Links:
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.patch
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.patch
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.diff <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358.diff>
—
Reply to this email directly, view it on GitHub <
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358>, or
unsubscribe <
https://github.com/notifications/unsubscribe-auth/AOLDEAU76JOZLV35XXXGUL3WLBS3JANCNFSM6AAAAAASQRH3YE
.
You are receiving this because you are subscribed to this thread.

—
Reply to this email directly, view it on GitHub
https://github.com/Iternio-Planning-AB/abrp-translations/pull/358#issuecomment-1333470536,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPDBIR35SFOC3VZ4Z3YPHLWLBVI5ANCNFSM6AAAAAASQRH3YE
.
You are receiving this because you authored the thread.Message ID:
@.***>


missing tailwindcss dependency?

After running:
yarn create astro -- --template satnaing/astro-paper
yarn
yarn dev

I got:

error   Cannot find package 'tailwindcss' imported from<EMAIL_ADDRESS>
Running yarn add tailwindcss seems to have fixed the issue.

Yep.
Prior to @astrojs/tailwind v2.0.0, tailwindcss wasn't required as a peer dependency. Some days ago, I updated @astrojs/tailwind without installing Tailwind as a peer dep. Then I tested with npm and it was working fine.
But as you mentioned, trying out using yarn seems to have a problem.
I'll update it.
Thank you @mikelehen for pointing this out.

Awesome, thank you!


text not showing in the tablet mode?

It's the expected behavior when the navbar is showing on the left/right side of the screen


Added Fee to Tpos Extension

Hey,
I have added a fee field to the tpos extension so now folks can charge their users for using their tpos service. The feature is optional and defaults to 0% fees. The user gets charged x% more in sats and the extra gets stored in the main wallet.

Great! Could you please pr https://github.com/lnbits/tpos-extension
As we have pulled tpos out of lnbits now we are moving to extensions being actually installable

So I can close this one?

Created One https://github.com/lnbits/tpos-extension/pull/2


Crucible tests run concurrently with other E2E tests and cause test instabilities

Our CI tests run Crucible tests in the background, while the E2E tests execute. This causes instabilities because many tests assume exclusive access to the FHIR server.
See https://microsofthealthoss.visualstudio.com/FhirServer/_build/results?buildId=6653&view=logs&j=e8dae5a1-9466-5eaf-6e12-4a7c123a87b8&t=cd3406d1-7e57-58b1-5267-50c955114b8b&l=724

AB#77966

Closing for now because we dont plan to leverage crucible moving forward.


Dead link on the document: "Get started with Docker Machine and a local VM"

There is a dead link on the bottom of Get started with Docker Machine and a local VM, Docker Machine driver reference.
Is this link url not https://docs.docker.com/machine/drivers/index.md but https://docs.docker.com/machine/drivers/ ?

I want to send a pull-request, but I couldn't find source code for Get started with Docker Machine and a local VM.

Thanks for reporting! Looks like this was already fixed in the repository, but not yet published on the website. See this pull request; https://github.com/docker/machine/pull/3360/files

Thank you for your replying.

See this pull request; https://github.com/docker/machine/pull/3360/files

I see. Okay, I wait for your publishing on the website.

Why re-open?

If fixed, we should close.  The doc will be updated eventually

Sorry for reopening. I would close this issue if the page Get started with Docker Machine and a local VM is updated.

No problem just trying to keep the tracker as clean as possible.


Change all ocurrences of '$runtimeType#$hashCode' to use the idAndType method.

The idAndType method generates a shorter description with a consistent length
consisting of the runtime type and the a 5 hex character long truncated
version of the hash code.
Feel free to suggest a different method name. I'm not happy about idAndType but I couldn't thinking of anything better and figured you would probably have an opinion on what name would fit well with the rest of Flutter.

Please make sure you wait for all the checks to pass before landing, even if you only changed comments. We have tests that verify the bodies of comments.

My fault. Reverted for now. I'll re-land in the morning with the case the IntelliJ refactor tool was missing. Odd IntelliJ was showing 0 analyzer issues.

Oh wow, I didn't even notice it had actually caused a problem! Just goes to show, I guess!


[docs][bug?] cli module is not documented

tauri "1.2.3"
@tauri-apps/api 1.2.0

If I want to use
import { getMatches } from '@tauri-apps/api/cli'

Tauri says you need to enable the Cli module.
The `Cli` module is not enabled. You must enable one of its APIs in the allowlist.

Like every other module, you enable them in the tauri.allowlist property in tauri.conf.json file.
Like,
{
  "tauri": {
    "allowlist": {
      "cli": {
        "all": true
      }
    }
  }
}

But, Tauri says
 Error `tauri.conf.json` error on `tauri > allowlist`: Additional properties are not allowed ('cli' was unexpected)

The only way to use the Cli module is to enable all APIs by using
{
  "tauri": {
    "allowlist": {
      "all": true
    }
  }
}

But I do not want to enable all APIs.
So, Tauri is either missing documentation for the Cli module, or Tauri is missing the allowlist for the Cli module

The cli feature is really in a weird state right now to be honest (and i think we want to remove it from core in an upcoming major release too iirc). It's really only documented here https://tauri.app/v1/guides/features/cli - and it's indeed not configurable via the allowlist but instead by its own config object similar to the system tray feature.

Uh oh, so allowlist.all: true is the only way to parse cli arguments at the moment?


Update publish_docker.yaml

Closes #
Code Changes

[x] list your code changes here

Steps to Confirm

[x] list any manual steps for reviewers to confirm the changes

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation:

[x] documentation complete, PR opened in fidesdocs
[x] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[x] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md
[x] For API changes, the Postman collection has been updated

Description Of Changes
Write some things here about the changes and any potential caveats

@NevilleS this looks like spam


feat(identity): add multi-tenancy config

Which problem does the PR fix?
Closes https://github.com/camunda-cloud/identity/issues/2131
What's in this PR?
This PR introduces two changes:

The multi tenancy feature flag support for Identity
A postgres database for Identity (a requirement to support multi tenancy in Identity)

Still to do

[x] Support customers with their own database connections
[x] Add supporting comments to the relevant sections
[x] Tests?

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[x] There is no other open pull request for the same update/change.
[x] The commits follow our Commit Guidelines.
[x] Tests for charts are added (if needed).
[x] The main Helm chart and sub-chart are updated (if needed).
[x] In-repo documentation are updated (if needed).

After opening the PR:

[x] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

@Ben-Sheppard I've added the needed part, please give it a final look.