CSV Datetime formats can't be converted

System information:

Operating system (distribution) and version
Windows 10
DBeaver version
21.0.0
Additional extensions

Connection specification:

Database name and version
CSV File

Driver name

Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
Hi there
I have a file folder that automatically imports CSV files saved in it, into DBeaver as tables. I am having trouble converting the date format. Automatically, all fields get imported as characters and my attempts to manually change the dates using the importer haven't work.
In my syntax, I've tried the following:

When datetime is in Epoch format:  to_timestamp(TRUNC( CAST( "time" AS bigint ) / 1000 ) )
When datetime is human readable: cast("timestamp" as date)
Convert(datetime, "timestamp)

It seems like the date conversion functions might not be recognized. In all examples my error looks like this:
SQL Error: Syntax error: Encountered " "AS" "AS "" at line 3, column 34.
Was expecting:
")" ...
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs

Hello @Robynishere1,
Can you provide step-by-step tutorial on how to reproduce your issue?
To be honest, I'm a bit confused. Are you talking about "flat files" driver for CSV files? Or you're trying to perform data transfer from CSV file to the table in your database? Please provide more context.

Hi there!

Save a CSV in a folder and refresh the CSV- downloads database
*   CSV’s in the folder appear in the tables list
*   Photo of DBeaver Tables:

@.***D71A41.C541A8D0]
 *   Photo of File location with CSV Files:

@.***D71A42.914DFCD0]
 *   Snapshot of select all statement:

@.***D71A43.743F8590]
 *   Snapshot of error message appears after each attempt to convert date from string:

@.***D71A43.743F8590]

All date fields are imported as characters/strings. And none of the syntax I have mentioned work.
Manually trying to import the CSV has resulted in duplicate tables, with date fields that seem to be a datetime format but they cannot be used in aggregations because the functions for formatting are not recognized still.

Hope this helps!
Robyn
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Who @.>
Sent: Tuesday, March 16, 2021 7:08 AM
To: @.>
Cc<EMAIL_ADDRESS>@.***>
Subject: Re: [dbeaver/dbeaver] CSV Datetime formats can't be converted (#11737)
Hello @Robynishere1https://github.com/Robynishere1,
Can you provide step-by-step tutorial on how to reproduce your issue?
To be honest, I'm a bit confused. Are you talking about "flat files" driver for CSV files? Or you're trying to perform data transfer from CSV file to the table in your database? Please provide more context.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/11737#issuecomment-800288003, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQOHNX2NOZ4LAS67V4OEZDTTD5Q6XANCNFSM4ZG3YFKQ.

Unfortunately, I can't see any attachments nor images 😕
This may happen when you're answering through your mail, not github itself.

The photos don't seem to be working in the github comments.

If they're attached as a link, that's okay - if you enable Preview mode, they should be here.
Otherwise, you can use free image hosting like https://imgur.com/.

Hi
I've attached the text and images via a word doc. Let me know if that helps!
Thanks!
description of issue.docx

Unfortunately, it is not a bug, which can be fixed, but a limitation of CSV driver. As a workaround you can import the table into another database which support date/time format via DBeaver import/export tools.

Thank you for confirming, can I leave this feedback as a feature request?

You should ask CSV for this feature https://www.cdata.com/drivers/csv/. Also another CSV driver versions may support date format.


fix(builder): exit if an error occur compiling go

Without this any error is omitted by the for loop.
To test this change any .go to contain an error and compile the builder make -C builder/ build.

Code LGTM.

Jenkins, test this please.

Jenkins, test this please.

Good catch. We didn't intend to ignore errors in compiling deis-builder. Code LGTM.


feed full container id on weave start to DNS/IPAM

We erroneously assumed that docker start returned the full container id. It doesn't and as a result we populated DNS with records with ids other than full container ids. And that's also what we told IPAM. As a result, DNS and IPAM didn't clean up after the container's death, resulting in stale DNS entries and leaked IPs.
Fixes #881.

@bboreham perhaps you want to grab this from @inercia?


24h format

Like that :

+1

+1

+1
還有個問題，關於moment非en語系時，這樣比較正常
                                    '
' +                                          'AM' +                                         'PM' +                                     '
' +

:+1:

+1

+1

+1

:+1:

+1

I've added an initial support for 12/24h time. See PR #86

+1

+1

+1

+1

+1

Forked project with 24h format : https://github.com/mpicciolli/angular-material-picker

+1


dropped default config test

Testing the default configuration seems to be a mere code duplication of the default config dictionary in config.py. Also, the test fails for the expected behavior of RasaNLUConfig(). The method correctly returns the content of config.json if the file exists instead of the default config dictionary and thus the test breaks.

The config_defaults.json is included in the documentation (https://rasa-nlu.readthedocs.io/en/latest/config.html#default). It shouldn't be removed. You are right, the test should probably be changed to load config_defaults.json (so something like RasaNLUConfig("config_defaults.json") instead of RasaNLUConfig()).
But the test serves two purposes:

avoids to commit accidental local changes of configuration parameters
makes sure the documentation is in sync with the configuration parameters

@twerkmeister don't forget to merge this one :)


Issue Building Production Ready Build

Hi,
I am using your guideline in order to build a production ready build. My development environment build fine. However, I am getting the following errors in production mode when running:
npm run webpack-production
4>ERROR in ./angularApp/main-aot.ts
4>Module not found : error : Can't resolve '../aot/angularApp/app/app.module.ngfactory' in 'C:\Projects\amber\src\Clients\AmberUI\angularApp'
4> @ ./angularApp/main-aot.ts 5:0-80
Could you please assist?
I have also noticed that the aot folder is not being generated.
Kind Regards,
Rachidi

Its okay that the aot folder is not being generated on disk. Did you do a fresh npm install? I can not reproduce this. Have you changed any configuration?

Closing this because of no activity. Think this is done now. Feel free to open up another issue if you encounter problems.


Graph does not shows tooltip

Hello.
I have encountered to an issue that tooltip is not displayed in line chart.

It does not shows all the time. It usually happens when putting mouse cursor inside the graph before it receives the data and rendering with it.
Does some one knows about this?

I've been experiencing the same issues. The first and last value will display, but none of the rest. I have noticed this issues occurs where I use an array stored in a variable which is populated by a for loop. If I use hard coded i.e. values: [[12341, 0.5], [54838, 0.9], [82382, 1.2], [29724, 0.65]], it works just fine. I need to populate an array with a response from the back-end so I can't hard-code it.


IAM Permissions for Shared VPC Usage in Project Factory

In the former version of the project factory, it was possible to assign the networkUser Role on the host project to groups via the project factory template, but this feature is missing from the new version. It would be great to have this feature back, because it's less nice to have to use the workaround via the network stage, since this is an extra workflow run and really adds a lot of time to the creation of projects.

Thanks Vincent, @simonebruzzechesse was starting to work on it, we'll update the issue as work progresses. It should be a reasonably quick task.


Allow usage of Backbone.Collection for Backbone.View

Currently we can only use only Models for Views and not the Collections.

My bad, got to know that a Model type of which collection is to be passed has to be given, this serves the purpose well.


CLOUDFLARE.md assumes you are running HAOS which goes against the point of this project

I was trying to follow https://github.com/iainbullock/tesla-http-proxy-docker/blob/main/tesla_http_proxy/CLOUDFLARE.md but ran into issues right away as it is assuming you can run the nginx addon in HAOS. This sort of goes against the point of this project as it was created for people who are running home assistant in docker. Hopefully @juchong can help create a new version that uses strictly docker?

The guide was written by a contributor to describe their own setup.
You don't need to use HAOS which as you say defeats the purpose of the project.
My setup as author is based on everything running in its own independent docker container, i.e. Home Assistant; nginx; tesla-http-proxy-docker.
If using Cloudflare (which I also do), then you can run cloudflared in it's own docker too.
Have a good at installing using the main instructions, and raise a new Issue here if you need any support

Sorry didn't mean to close - let me know if you have any further questions

I was able to work out how to get everything running with parts of that doc and the blog post. I think it is all working but I am not able to get the HA integration working sadly. I have my docker compose setup a little differently and I think that is messing with the PROXY SSL CERTIFICATE location when I go to configure the integration. I am not seeing any logs though so I don't know why it is failing.

Hmm seems my refresh token might not be working.
"error": "login_required", "error_description": "The refresh_token is invalid"

I ended up using https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613 to. generate a new refresh token and was able to get it working! Thanks for all the work on this project!

Glad you got it sorted, thanks for posting the update


Typescriptify Article.js and add more helpful types to ModalContainer.tsx

I can no longer live without Typescript.

Hah, totally understand, same here 😄
LGTM 👍 merge when 🍏


x/build/cmd/relui: add ability to schedule workflows

There are at least several different use-cases where we'd like to be able to schedule workflows in advance. Relui should be able to keep track of these and start workflows as appropriate.
I've written out each use-case below, but a crontab time format is probably sufficient.
Once
Will run the job at the specified date and time.
This is useful for scheduling major and minor releases in advance.

k
v

Run at
2022-08-16 10:49

Interval
Runs a job every interval as specified.
This would handle nightly releases, or other automated tasks that we do regularly, like tagging repos or updating dependencies.

k
v

Interval Duration
Minute, hour, day, week, month

Interval Quantity
1,2,3...

Run at
2022-08-16 10:49

Date-based
Runs a job every nth day of week or month.
This may be useful for updating buildlet images and binaries.

k
v

Interval Duration
Minute, hour, day, week, month

Run at
2022-08-16 10:49

Remaining work:

No workflows currently fail. If a workflow has been scheduled, it should notify when it stalls. The code to do this exists, but has not been tested, due to workflows with approval steps never failing.

We saw a workflow failure over the weekend that properly logged at https://cs.opensource.google/go/x/build/+/master:internal/relui/listener.go;l=183;drc=67d624370c7018c64d7dcb4a4ee2ffcf5b029a07. So it should be fine to hook it up to a real email client.


Use incremental backups as base for new backups to save storage cost

Hi @ddebeau,
Before this change, incremental backups where created based on a full. This caused increased storage and cost because the same deltas were stored N times, until a new full is created.
This change creates a proper chain from full to all the intermediate backups which allows only deltas to be uploaded. Cost should drop dramatically as we only keep what is necessary
The DB and dependency tree was already there, so this change is backwards compatible. Once deployed, new incs would be based on the latest snapshot

Tests should be passing. The problem is the secret keys which are not available to forks

Hi @ddebeau I think that makes sense. The parameter max_backups does not seem to make sense when using incrementals anymore. max_incremental_backups_per_full seems to be the proper way to limit the count maybe? Once a new full is added we can make it delete all the previews chain. Max backups its not critical anymore as its the most efficient way to store backups. Once we add a new full, the last chain would be obsolete but potentially useful if you want to recover a point in time. Please let me know your thoughts and I can change the docs / behavior.

I can think of a couple ways to solve the issue:
Remove old backup chain when backup limit is reached
max_backups = 7
max_incremental_backups_per_full = 3

f
fi
fii
fiii
fiiif
fiiifi
fiiifii
fiii

Generate new full backup when backup limit is reached
max_backups = 7
max_incremental_backups_per_full = 3

f
fi
fii
fiii
fiiif
fiiifi
fiiifii
fiifiii

Removing the old backup chain once the limit is reached is transfer efficient at the expense losing backups. Generating a new full backup is transfer inefficient but you don't lose backups.
I tend to have very large full backups (~ 1 TB) so generating a new full backup when the limit is reached would be very inefficient for me. I think we should delete the old backup chain once the backup limit is reached. As long as the behavior is well documented that should be fine.

@ddebeau added the requested changes and included some docs regarding the limiter. There is one edge case that I had to solve by creating a full. A trivial example would be if  max_incremental_backups_per_full is disabled (only creates incs) but a max_backups is set. There would be no way to perform a cleanup. What it's doing is create a new full and removing the last chain which in this example is all the backups except the last full. Let me know your thoughts.

@ddebeau added the requested changes and included some docs regarding the limiter. There is one edge case that I had to solve by creating a full. A trivial example would be if max_incremental_backups_per_full is disabled (only creates incs) but a max_backups is set. There would be no way to perform a cleanup. What it's doing is create a new full and removing the last chain which in this example is all the backups except the last full. In a normal scenario with properly configured settings, it would never create a full but simply delete the entire oldest chain just like your first example in the comment above. Let me know your thoughts.

If I have a very large data set (~3 TB) that is rarely modified it would be beneficial to retain the old full backup and delete just the incremental backups. The old full backup would then be used for the new incremental backup. That is the existing behavior:
https://github.com/ddebeau/zfs_uploader?tab=readme-ov-file#single-full-backup

I am in the exact same scenario, one huge full (3 TB as well) and my incrementals are additions but almost never deletions. Would you just delete all the incrementals and create a new inc against the original full? Kind of compressing all the incs into one? If the changes are mostly additions, it would be the same bytes, just a single file. I assume this is useful if between the full and incs there were a lot of deletes, and hence saving all that space. Is that the case? My only concern with a very old full is that it just may have stale data. Over time you would be saving more and more duplicates (say you deleted files that were part of the original full). A "start from scratch" (ie new full) would eliminate all the deleted data. I am ok with making this change though as I do not plan to use max_backups anymore but rather keep a linear history and add a new full every 6 months / delete the old ones which is the minimum time for S3 deep archive. Only reason is to free up the deletions from time to time if any. Thanks

I am in the exact same scenario, one huge full (3 TB as well) and my incrementals are additions but almost never deletions. Would you just delete all the incrementals and create a new inc against the original full? Kind of compressing all the incs into one?

Yes, I think that would make sense since we want to minimize transfer time.

If the changes are mostly additions, it would be the same bytes, just a single file. I assume this is useful if between the full and incs there were a lot of deletes, and hence saving all that space. Is that the case? My only concern with a very old full is that it just may have stale data. Over time you would be saving more and more duplicates (say you deleted files that were part of the original full). A "start from scratch" (ie new full) would eliminate all the deleted data.

If folks are concerned with the old full backup becoming too stale they could start using max_incremental_backups_per_full. For my use case it takes a very long time for the old full backup to become too stale.

I am ok with making this change though as I do not plan to use max_backups anymore but rather keep a linear history and add a new full every 6 months / delete the old ones which is the minimum time for S3 deep archive. Only reason is to free up the deletions from time to time if any. Thanks

Would you use ZFS Uploader to do that? It seems you could do that with max_backups and max_incremental_backups_per_full.

Would you use ZFS Uploader to do that? It seems you could do that with max_backups and max_incremental_backups_per_full.
Since my connection is insanely fast and symmetrical I can upload it in a few hours. My factor is cost which is not well defined beyond count and how often it’s running (cron + one of the limits). I planned to use a lifecycle of 6 months plus max_incrementals_per_full. That said, with careful tuning I may be able to avoid the compression mechanism by creating a new full before the max is reached and after the 6 months limit.
I will start with the changes now

@ddebeau changes applied. I think this makes more sense now. Let me know what you think

working great!

No need to upload 125 GB on each inc but rather just what changed


Add full-screen-only option

Hello!
I was inspired to add this option from cmd-johnson/atom-battery-status, and I followed their code to implement this. I think it sticks with the simplicity that this package is aiming for. 😄
Hopefully I matched your programming style, I did my best to put my code in the right places. I've never developed on an :atom: package before.

Thanks for the PR! I just merged it, it looks nice indeed! If you don't mind I will just fix a couple of style things, but other than that it looks alright.

Go right ahead! Thanks for the merge 😄


Error syncing with GitHub, check credentials

When attempting to synchronize with GitHub, the following message is displayed: 'Error syncing with GitHub, please verify your credentials.' Could you please guide me on the steps to successfully complete the synchronization?

@imranux One of the reasons could be that your Personal Access is expired. More information could be found here: https://docs.tokens.studio/sync/github

@esthercheran can this issue be closed?

@six7 This issue must be reopened. The guide directed to is what caused the issue to begin with. Causing major issues at my organization, and completely blocking my workflow. I am happy to provide diagnostic information if asked.


Added '--local-rank' alias to fix DDP with PyTorch 2.x

Contribution in a nutshell
As reported in #1897, DDP as applied for a training recipe would fail on my PyTorch 2.0 install. This adds an alias to the SB CLI that also accepts the new --local-rank (in addition to --local_rank) and solves the issue.
Scope

[x] Fixes PyTorch 2.0 DDP training.

Notes for reviewing (optional)
There should be no backward compatibility concerns, as this is only a new alias for a flag passed by pytorch.
Pre-review

[x] (if applicable) add an extra_requirements.txt file
[x] (if applicable) add database preparation scripts & use symlinks for nested folders (to the level of task READMEs)
[x] (if applicable) add a recipe test entry in the depending CSV file under: tests/recipes
[x] create a fresh testing environment (install SpeechBrain from cloned repo branch of this PR)
[x] (if applicable) run a recipe test for each yaml/your recipe dataset
[x] check function comments: are there docstrings w/ arguments & returns? If you're not the verbose type, put a comment every three lines of code (better: every line)
[x] use CI locally: pre-commit run -a to check linters; run pytest tests/consistency
[x] (optional) run tests/.run-doctests.sh & tests/.run-unittests.sh
[x] exhausted patience before clicking « Ready for review » in the merge box 🍄

The CI error is strange. Did a dependency break things?

The CI error is strange. Did a dependency break things?

No worries, sometimes the test are failing. I'm rerunning the test pipeline.


Backoff on context creation and add sup

We are not retrying to decode anymore
Context creation is done async with some backoff if need be
v8 and custom decoder sup are now under same sup to avoid taking down more than they should

At some point do we want to provide more fleshed out error messages? For example if someone get's no_context that might not mean anything to them.
Also running more than 1 v8 vm for when we get lots of data at the same time. We've seen spikes up to 15ms for single function runs, I suspect most of that is waiting for other contexts to finish.

Could be, but this does not impact downlink so I am not too worried about the 15ms

Without comparing this code to Ferd's instructions for back-off & retry, this looks good. (I'm assuming that you've followed the same pattern as used elsewhere in the code since you probably wrote most of those earlier instances anyway...)

Yes same as before


Outdated default IO query limit in documentation

Describe the bug
The documentation states that the default query limit for loading data from the cloud is 100,000 rows. #779 bumped this value to 10,000,000 rows.
To Reproduce
Steps to reproduce the behavior:

Go to the data loading documentation.
CMD + F into "100,000".

Screenshots

Additional context
I opened a PR to update this value (#1706)

Thank you for sharing

Thank you @jlondonobo for fixing the doc in this PR! https://github.com/mage-ai/mage-ai/pull/1706


AppliedManifestFailed when creating ManifestWorks with jobs

When creating simple ManifestWorks with jobs, i.e.:
apiVersion: work.open-cluster-management.io/v1
kind: ManifestWork
metadata:
  namespace: cluster1
  name: simple-job
spec:
  workload:
    manifests:
      - apiVersion: batch/v1
        kind: Job
        metadata:
          name: simple-job
          namespace: default
        spec:
          template:
            spec:
              containers:
              - name: kubectl
                image: quay.io/sighup/kubectl-kustomize:1.21.6_3.9.1
                command: ["/bin/sh", "-c"]
                args:
                  - pwd
              restartPolicy: Never
          backoffLimit: 0

The job gets correctly created in the ManagedCluster:
% k get job --context kind-cluster1
NAME         COMPLETIONS   DURATION   AGE
simple-job   1/1           5s         5m24s

% k describe job simple-job  --context kind-cluster1
...
Events:
  Type    Reason            Age    From            Message
  ----    ------            ----   ----            -------
  Normal  SuccessfulCreate  5m34s  job-controller  Created pod: simple-job-sj76d
  Normal  Completed         5m29s  job-controller  Job completed

However for some reason the ManifestWork reports AppliedManifestFailed:
Conditions:
        Last Transition Time:  2022-12-05T12:36:38Z
        Message:               Failed to apply manifest: Job.batch "simple-job" is invalid: [spec.selector: Required value, spec.template.metadata.labels: Invalid value: map[string]string(nil): 'selector' does not match template 'labels', spec.selector: Invalid value: "null": field is immutable, spec.template: Invalid value: core.PodTemplateSpec{ObjectMeta:v1.ObjectMeta{Name:"", GenerateName:"", Namespace:"", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, Spec:core.PodSpec{Volumes:[]core.Volume(nil), InitContainers:[]core.Container(nil), Containers:[]core.Container{core.Container{Name:"kubectl", Image:"quay.io/sighup/kubectl-kustomize:1.21.6_3.9.1", Command:[]string{"/bin/sh", "-c"}, Args:[]string{"pwd"}, WorkingDir:"", Ports:[]core.ContainerPort(nil), EnvFrom:[]core.EnvFromSource(nil), Env:[]core.EnvVar(nil), Resources:core.ResourceRequirements{Limits:core.ResourceList(nil), Requests:core.ResourceList(nil)}, VolumeMounts:[]core.VolumeMount(nil), VolumeDevices:[]core.VolumeDevice(nil), LivenessProbe:(*core.Probe)(nil), ReadinessProbe:(*core.Probe)(nil), StartupProbe:(*core.Probe)(nil), Lifecycle:(*core.Lifecycle)(nil), TerminationMessagePath:"/dev/termination-log", TerminationMessagePolicy:"File", ImagePullPolicy:"IfNotPresent", SecurityContext:(*core.SecurityContext)(nil), Stdin:false, StdinOnce:false, TTY:false}}, EphemeralContainers:[]core.EphemeralContainer(nil), RestartPolicy:"Never", TerminationGracePeriodSeconds:(*int64)(0xc008138068), ActiveDeadlineSeconds:(*int64)(nil), DNSPolicy:"ClusterFirst", NodeSelector:map[string]string(nil), ServiceAccountName:"", AutomountServiceAccountToken:(*bool)(nil), NodeName:"", SecurityContext:(*core.PodSecurityContext)(0xc0063d06c0), ImagePullSecrets:[]core.LocalObjectReference(nil), Hostname:"", Subdomain:"", SetHostnameAsFQDN:(*bool)(nil), Affinity:(*core.Affinity)(nil), SchedulerName:"default-scheduler", Tolerations:[]core.Toleration(nil), HostAliases:[]core.HostAlias(nil), PriorityClassName:"", Priority:(*int32)(nil), PreemptionPolicy:(*core.PreemptionPolicy)(nil), DNSConfig:(*core.PodDNSConfig)(nil), ReadinessGates:[]core.PodReadinessGate(nil), RuntimeClassName:(*string)(nil), Overhead:core.ResourceList(nil), EnableServiceLinks:(*bool)(nil), TopologySpreadConstraints:[]core.TopologySpreadConstraint(nil), OS:(*core.PodOS)(nil)}}: field is immutable]
        Reason:                AppliedManifestFailed
        Status:                False
        Type:                  Applied
        Last Transition Time:  2022-12-05T12:36:38Z
        Message:               Resource is available
        Reason:                ResourceAvailable
        Status:                True
        Type:                  Available
        Last Transition Time:  2022-12-05T12:36:38Z
        Message:
        Reason:                NoStatusFeedbackSynced
        Status:                True
        Type:                  StatusFeedbackSynced

I think this may be preventing the ManifestWork to properly report FeedbackRules (please correct me if I am wrong):
apiVersion: work.open-cluster-management.io/v1
kind: ManifestWork
metadata:
  namespace: cluster1
  name: simple-job
spec:
  manifestConfigs:
    - resourceIdentifier:
        group: batch
        resource: job
        namespace: default
        name: simple-job
      feedbackRules:
        - type: JSONPaths
          jsonPaths:
            - name: succeeded
              path: '.status.succeeded'
  workload:
    manifests:
      - apiVersion: batch/v1
        kind: Job
        metadata:
          name: simple-job
          namespace: default
        spec:
          template:
            spec:
              containers:
              - name: kubectl
                image: quay.io/sighup/kubectl-kustomize:1.21.6_3.9.1
                command: ["/bin/sh", "-c"]
                args:
                  - pwd
              restartPolicy: Never
          backoffLimit: 0

No status feedback whatsover:
     Status Feedback:

I think it was successfully applied based on the original spec but because it auto populated some other spec fields the subsequent update apply is no longer successful.
@qiujian16 @zhujian7 do we doc this?

it should not impact statusfeedback as long as the condition is available. I think the configuration missing version part:
manifestConfigs:
    - resourceIdentifier:
        group: batch
        version: v1
        resource: job
        namespace: default
        name: simple-job

for apply part, job is a bit different due to default label/selectors. we should document it. And you could try using serversideapply configuration. something like this:
manifestConfigs:
    - resourceIdentifier:
        group: batch
        version: v1
        resource: job
        namespace: default
        name: simple-job
      feedbackRules:
        - type: WellKnownStatus
      updateStrategy:
        type: ServerSideApply

Thanks @qiujian16 ,
as for the resourceIdentifier adjustments:

I guess there is no version field (maybe apiVersion instead?): error: error validating "mf.yaml": error validating data: ValidationError(ManifestWork.spec.manifestConfigs[0].resourceIdentifier): unknown field "version" in io.open-cluster-management.work.v1.ManifestWork.spec.manifestConfigs.resourceIdentifier; if you choose to ignore these errors, turn validation off with --validate=false
making the resource plural (jobs instead of job) does the trick:      Status Feedback:
        Values:
          Field Value:
            Integer:  1
            Type:     Integer
          Name:       succeeded

For the apply part, the updateStrategy: type: ServerSideApply does the trick:
      Conditions:
        Last Transition Time:  2022-12-27T11:21:40Z
        Message:               Apply manifest complete
        Reason:                AppliedManifestComplete
        Status:                True
        Type:                  Applied
        Last Transition Time:  2022-12-27T11:21:40Z
        Message:               Resource is available
        Reason:                ResourceAvailable
        Status:                True
        Type:                  Available
        Last Transition Time:  2022-12-27T11:21:40Z
        Message:
        Reason:                StatusFeedbackSynced
        Status:                True
        Type:                  StatusFeedbackSynced

FYI @zhiweiyin318 @elgnay I think we should add some doc on how to create a manifestwork with job

add some doc on how to create a manifestwork with job

Created a task to trace this effort: https://github.com/open-cluster-management-io/work/issues/173


Feature/security update

Summary
Following guidance found here: https://github.com/facebook/create-react-app/issues/11174
Moves react-scripts to devDependencies and autofixes security vulnerabilities.
Testing Guidance
Run npm audit --omit=dev when checking for true alerts.

Codecov Report
Base: 73.62% // Head: 94.16% // Increases project coverage by +20.53% :tada:

Coverage data is based on head (72883cc) compared to base (792811b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #309       +/-   ##
===========================================
+ Coverage   73.62%   94.16%   +20.53%
===========================================
  Files         190      114       -76
  Lines        9270     3049     -6221
  Branches      768      354      -414
===========================================
- Hits         6825     2871     -3954
+ Misses       2037      178     -1859
+ Partials      408        0      -408

Flag
Coverage Δ

backend
94.16% <ø> (ø)

frontend
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/src/api/infernoApiService.ts

client/src/api/RequestsApi.ts

client/src/store/testSession.ts

...mponents/TestSuite/TestRunButton/TestRunButton.tsx

...lient/src/components/RequestDetailModal/styles.tsx

client/src/components/LandingPage/LandingPage.tsx

...src/components/_common/__mocked_data__/mockData.ts

client/src/components/Header/styles.tsx

...nt/src/components/RequestDetailModal/CodeBlock.tsx

...c/components/TestSuite/__mocked_data__/mockData.ts

... and 66 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Process Flow Page - Some design changes

Describe the bug

change text ProcessFlow -> Process Flow in tab and main heading
No Templates Found message should be left

https://www.berrycast.com/conversations/42d4220b-5da2-5a4c-a7b4-1d9c2dafc372

This message should be in left align

https://www.berrycast.com/conversations/90baa46e-eea0-5455-999c-ef9dc499828c


Add bwcVersion 1.3.6 to 2.2

Signed-off-by: Suraj Singh<EMAIL_ADDRESS>Description
Backport bwc version changes from PR https://github.com/opensearch-project/OpenSearch/pull/4381 to 2.x branch. This is currently causing gradle check failures.
e.g. https://github.com/opensearch-project/OpenSearch/pull/4450
Issues Resolved
Due to issue https://github.com/opensearch-project/OpenSearch/issues/3218, the PR needs to be created manually.
Check List

[ ] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #4453 (352e61c) into 2.2 (afea282) will increase coverage by 0.00%.
The diff coverage is 85.71%.

@@            Coverage Diff            @@
##                2.2    #4453   +/-   ##
=========================================
  Coverage     70.61%   70.62%
- Complexity    56708    56749   +41
=========================================
  Files          4557     4557
  Lines        272875   272880    +5
  Branches      40055    40056    +1
=========================================
+ Hits         192688   192713   +25
+ Misses        64006    63963   -43
- Partials      16181    16204   +23

Impacted Files
Coverage Δ

...ndices/breaker/HierarchyCircuitBreakerService.java
86.17% <83.33%> (-0.60%)
:arrow_down:

server/src/main/java/org/opensearch/Version.java
82.71% <100.00%> (+0.08%)
:arrow_up:

...va/org/opensearch/test/store/MockFSIndexStore.java
0.00% <0.00%> (-73.92%)
:arrow_down:

.../opensearch/test/store/MockFSDirectoryFactory.java
18.05% <0.00%> (-50.00%)
:arrow_down:

...cluster/coordination/PendingClusterStateStats.java
20.00% <0.00%> (-48.00%)
:arrow_down:

.../admin/cluster/reroute/ClusterRerouteResponse.java
60.00% <0.00%> (-40.00%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...luster/routing/allocation/RoutingExplanations.java
62.06% <0.00%> (-37.94%)
:arrow_down:

...n/decider/SnapshotInProgressAllocationDecider.java
34.78% <0.00%> (-34.79%)
:arrow_down:

...ion/admin/cluster/node/info/PluginsAndModules.java
53.12% <0.00%> (-34.38%)
:arrow_down:

... and 469 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[stable/gangway] trusted ca, existing configmap

Is your feature request related to a problem? Please describe.
Currently we have to supply the trusted ca file when we're installing Gangway. It's making the assumption that the trusted ca file is available to the individual or machine installing the tool.
Describe the solution you'd like
Ability to provide the name of an already existing configmap, containing the rootca.crt
Describe alternatives you've considered
Templating extraVolumes and extraVolumeMounts in the deployment, but it seems like an overkill for this specific use.
Additional context
In the oauth2-proxy we've solved it with the extraVolumes and extraVolumeMounts, a similar solution for Gangway would look like:
values.yaml
gangway:
  cluster_ca_path: /path/to/rootca.crt

extraVolumes:
  - name: rootca-cert
    configmap:
      name: my-rootca-configmap

extraVolumeMounts:
  - mountPath: /path/to/
    name: rootca-cert

deployment.yaml
        volumeMounts:
...
{{- if ne (len .Values.extraVolumeMounts) 0 }}
{{ toYaml .Values.extraVolumeMounts | indent 8 }}
{{- end }}
      volumes:
...
{{- if ne (len .Values.extraVolumes) 0 }}
{{ toYaml .Values.extraVolumes | indent 6 }}
{{- end }}

And documentation about creating a configmap, containing the file referenced in the cluster_ca_path.
I don't know if there's a usecase for mounting more files into the Gangway pod, that would justify this solution?

@rk295 would you care to comment on this? I'd be happy to make a pullrequest with either solution, i.e. existingConfigmap or extraVolume[Mount]s

Just incase you've not seen it, this was altered slightly last week in #17361.
I like the idea, you are right in that we shouldn't rely on the user who has the ability to install/upgrade the deployment having access to the cert.
As for how we achieve that, I think I would have also gone with allowing the user to specify a pre-existing configmap and referencing that 👍
I'm not using Gangway anymore so don't really know if there are other things that you would want to mount into the pod. I certainly don't remember any when I used it last 🤷♂
PR welcome!


Refactor fleet-manager Directory for Better Organization

What would you like to be added:
Refactor fleet-manager Directory for Better Organization
Why is this needed:
the fleet-manager folder is messy and hard to use right now. It makes keeping the code in good shape and understanding it tough, especially for people new to the project.

/assign


Conflict with html-inline-css-webpack-plugin and csp-html-plugin-webpack-plugin

Description
When html-inline-css-webpack-plugin is used alongside csp-html-plugin-webpack-plugin, the CSP plugin generates invalid hash values in the content security policy. This issue does not occur when html-inline-css-webpack-plugin is not used.
Steps to Reproduce

Clone the reproduction repository (csp branch): Reproduction repository.
Install dependencies and build the project: npm i && npm run build.
Examine the generated CSP hashes in the built HTML files. Alternatively, view the deployed site for reference: Deployed site.

Expected Behaviour
The csp-html-plugin-webpack-plugin should generate valid CSP hashes regardless of the use of html-inline-css-webpack-plugin.
Actual Behaviour
When html-inline-css-webpack-plugin is used, the hashes generated by the CSP plugin are invalid and do not match the content in the HTML.
Environment
html-inline-css-webpack-plugin: 1.11.2
csp-html-plugin-webpack-plugin: 5.1.0
Webpack: 5.96.1
Node.js: 22.10.0
OS: macOs Sequoia 15.0.1 (24A348), Ubuntu 24.04

It seems that removing the following SCSS definitions resolves the issue. With these definitions removed, the CSP plugin and the inline CSS plugin use the same CSS, resulting correct hashes:
> * {
   // style definition
}

I have identified the issue. It was caused by cheerio in slackhq/csp-html-webpack-plugin.
You can find more detail under this issue:
slackhq/csp-html-webpack-plugin#126


Yellow warning icon on parse package in Xamarin Studio Mac

On Xamarin Studio 5.10.871 (latest as of this writing), adding the parse NuGet package into my iOS project (Parse 1.6.2, also latest as of this writing) -- after install and restart of Xamarin Studio, the package is marked with a yellow exclamation warning icon.  When you hover over this icon, it says "Package is not restored".
This issue persists between updating the package (I had it ever since I first installed Parse .NET SDK 1.6.1).
I noticed that if I followed the instructions in the last comment here:
https://github.com/ParsePlatform/Parse-SDK-dotNET/issues/34
and restarted Xamarin Studio, the issue was resolved.  I just wanted to mention this to hopefully get the fix permanently applied to the NuGet package so I won't have to keep applying it and other users won't have to experience the issue.
Thanks!

As mention on #34, this is a bug with Xamarin Studio that has been fixed on the beta channel (no idea why they haven't updated yet).
Seeing as we can't personally fix this bug, I'm going to close this for now.


[WFCORE-5506] Make Bouncy Castle bcutil-jdk15on license to use explic…

…itly the MIT license file shipped with the server
Jira issue: https://issues.redhat.com/browse/WFCORE-5506

@yersan thanks


Cannot load module via CommonJS/Browserify.

When I try to load this module into my angular application via CommonJS/Browserify the module is not found.
In this form dependencies are loaded in like so:
var myModule = angular.module('app', [
    require('angular-pretty-xml').name,
]);

The dependency we are requiring has to have a wrapper that looks like so:
'use strict';
/*global module,require*/
var angular = require('angular');
require('angular-pretty-xml/src/angular-pretty-xml.js');
module.exports = angular.module('prettyXml');

The wrapper is defined in the package.json:
{
    "name": "app",
    "browser": {
        "angular-pretty-xml": "./app/client/wrappers/angular-pretty-xml.js"
    }
}

This approach works with every other module I've tried so far.
I noticed that the this module does not follow the same structure as others.
It doesn't have the same wrapper that is.

Fixed issue, pull request #3


Fix SearchBar styles & update StoryBook stories for custom styles

Hey, I just made a Pull Request!
Fix for #17740 to remove unnecessary FormControl margin & update StoryBook to reflect how to remove the notchedOutline properly.
Closes #17740
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Broken tests because @octokit again...

@camilaibs To be fair, I broke it so...

Why was the endAdornment in the SearchAutocomplete moved into InputProps?
I see the DefaultTemplate story has custom styles, I was wondering why since it has "Default" in the name.

@camilaibs To be fair, I broke it so...

Why was the endAdornment in the SearchAutocomplete moved into InputProps?
I see the DefaultTemplate story has custom styles, I was wondering why since it has "Default" in the name.

Other than these 2 questions I see all is good.

Great questions! Let me try to answer:

I see the DefaultTemplate story has custom styles, I was wondering why since it has "Default" in the name

The template is called "default" only because there is no other variant in our storybook so far (I mean no other homepage template). The "default" in the template's name was not intended to imply that all components used to compose it are standard variations. The search bar in the default homepage template has been styled since the template was created, before changing the base search bar input from InputBase to TextField.

Why was the endAdornment in the SearchAutocomplete moved into InputProps?

It's just an alternative way to customize the endAdorment introduced with the text field change. It does the same thing the endAdorment prop does. Since I had to customize the class name, I moved the endAdorment to the InputProps as well to group all the inner input customizations in the same prop.

we pass the className to the input because we want to target the input, since endAdornment is part of the TextField props I believe is better to keep it at that level, Idk if TextField does anything special with it before passing it to the input so...

I put back the endAdornment, the visual result is the same, so that's fine with me 🙂 .
If I understand correctly the TextField API here, the endAdornment is not a TextField prop but an InputBase prop. In the end, the SearchBar endAdornment prop is passed via InputProps anyway, so it was only kept in the SearchBar props for backward compatibility after the TextField started being used by SearchBar...

Nice, pushed a last change to fix a small issue I saw with the HomePageSearchBar's input classes that could be overridden by mistake if a single class was provided, this should be ready for merge.

@emmaindal Seems we need a new issue specifically for the search modal...

shouldn't it be considered for a patch release, e.g. 1.14.2 rather than waiting till June?

Issuing a separate 1.14.2 release takes some manual effort from the maintainers -- @beveradb you could probably file a separate issue specially requesting this release, but when I take a close read of the Release Versioning Policy, I do see:

Security fixes may be backported to older releases based on the simplicity of the upgrade path, and the severity of the vulnerability.
Bug reports are valid only if reproducible in the most recent release, and bug fixes are only applied to the next release.

... That "bug fixes are only applied to the next release" line kinda sounds like this type of change is not eligible for its own patch release.

As @beveradb & @grvpandey11 already commented, this issues is somehow a showstopper for updating to 1.14.0. Not in a technical / functional way, but from a UI / UX perspective. @backstage/maintainers, could you double check to make a patch release for this issue? ✌

@benjdlambert / @Rugvip / @freben what do you think about a bugfix release? Otherwise we have to implement a temporary workaround, to unblock the GA4 switch :/

Alright, it's a bit far to the next main-line release still: https://github.com/backstage/backstage/pull/18174


Fix None being added to sys.path

#847  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dongreenberg and the rest of your teammates on  Graphite


Using python's xdg-caching can cause flakes

Currently when running python test on linux, we are mounting /tmp/xdg-cache-home to the docker container that runs the tests in the attempt to prevent unnecessary downloads of pip packages (with the theory that more downloads leads to increased flakiness) - the idea is that while there is a new docker container for each test suite, the xdg cache remains per-VM.
This approach no longer seems to be useful:

It turns out that XDG cache doesn't work reliably when multiple docker containers are using it concurrently (the concurrent run can see corrupt files). We are using concurrent docker containers in our multilang test suite to speed up the execution and we are currently getting flakes seeing flakes caused by this.
support for caching makes our docker_run scripts more complicated and we really don't want that.
since we migrated to kokoro, the caching is limited anyway - as each run gets a fresh VM, we need to download packages anyway for every build (and that actually seems to causing way less flakiness the problem with concurrent XDG caching)

This should fix https://github.com/grpc/grpc/issues/14311.

CC @nathanielmanistaatgoogle

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Corrupt JSON data (indicates timeout or crash):
    bm_fullstack_streaming_pump.BM_PumpStreamServerToClient_SockPair__1.counters.new: 1

[microbenchmarks] No significant performance differences

@nathanielmanistaatgoogle, I updated the commit message. To be honest, I feel that duplicating the reasoning from the PR in the commit message violates the DRY principle, but I don't feel strongly about that at all. PTAL.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

@nathanielmanistaatgoogle  ah, neat. Thanks for the tip

Corrupt JSON data (indicates timeout or crash):
    bm_fullstack_streaming_pump.BM_PumpStreamServerToClient_SockPair__64.counters.new: 1
    bm_fullstack_streaming_pump.BM_PumpStreamServerToClient_SockPair__64.opt.old: 1

[microbenchmarks] No significant performance differences


How to use Alexa Presentation states for launching browser

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Hi, I am working on SmartScreen SDK 2.8.0 and trying to integrate this in the EvoConnect product. My requirement is to launch the browser only when we have anything to display in the browser, otherwise it will be active in the background (Foreground some other app will be active). I was just exploring the different state we maintain in AlexaPresentation like renderDocument, focusChanged, cardCleared, etc. I just want to understand whether I can use these events for this requirement of launching the browser on a need basis?
If we are in renderDocument state, make the browser as an active app running in foreground and if we are in cardCleared state then push the browser to the background. Or this should be handled in another way. Can anyone comment on this.
What is the expected behavior?

NA
What behavior are you observing?

NA
Provide the steps to reproduce the issue, if applicable:

NA
Tell us about your environment:

What version of the AVS Device SDK are you using?
  <2.8.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[ X] Other - tell us more: Setup Box

Tell us about your OS (Type & version):

[ X] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Have you tried the same use case with AVS Device SDK SampleApp?

[ X] The issue is not applicable to the AVS Device SDK SampleApp.
[ ] The issue is not reproducible on the AVS Device SDK SampleApp.

Hi @abkant,
The Smart Screen SDK uses CA interfaces for rendering visual content (TemplateRuntime and APL). The C++ layer sends across IPC messages from the GUIClient.cpp to the JS layer for rendering the payloads using the apl-client-js library.
aplRender, clearDocument, renderPlayerInfo, and clearPlayerInfoCard messages received on the JS layer can be used to get notified of a rendered/cleared window. In the Smart Screen Sample Application, https://github.com/alexa/alexa-smart-screen-sdk/blob/master/modules/GUI/js/src/app.tsx#L702, several windows (fullscreen, playerInfo and overlay) are present and render within a single browser. It's possible to render a window per browser or app and close the app when the window is closed.

Closing due to inactivity. Please reopen if needed.

Thanks for the clarification.
I have a few more queries for my trials done as following  and hence reopening this
1. Launch the browser much ahead (may be at the listening/thinking state) before receiving the render Directive - Browser displays the display card successfully
2. Launch the browser just when we receive render Directive - Browser misses the display card and nothing gets displayed in the browser. If we receive another render Directive in this situation, the browser is able to display the card successfully.
	We see that there is a handshake done between SDK and Browser for every new websocket connection is established. Is this is the reason why display card is missed.

3. Relaunch/reload the browser in between of the active directive - Browser misses the display card and nothing gets displayed in the browser. If we receive another render Directive in this situation, the browser is able to display the card successfully.

Can you please help us in understanding the dependency of SSDK with browser in more depth. As our requirement was to launch the browser only when we receive render Directive, for all other cases we can skip launching the browser.
With these trials it seems like browser should be active always, is this the requirement of SSDK? Can you please comment.


split: suffix length refactor

Refactoring suffix length processing, distinguishing between dynamic auto-widening vs. pre-calculated auto-width and addressing an edge case of passing 0 as a value for suffix length in command line option,
i.e. split -a0 file
or split --suffix-length=0 file

@sylvestre would you mind reviewing this one?

@tertsdiepraam with latest changes, could you please let me know if you have other comments/suggestions?

@tertsdiepraam looks like it is good to merge. The GNU test failures are unrelated - something is not right with tail

Thanks!


NVS support in bootloader (IDFGH-1184)

Environment

Development Kit:      [ESP32-PICO-Kit]
Kit version (for WroverKit/PicoKit/DevKitC): [v4]
Module or chip used:  [ESP32-PICO-D4]
IDF version (run git describe --tags to find it): v3.2
Build System:         [Make]
Compiler version (run xtensa-esp32-elf-gcc --version to find it): 1.22.0-80-g6c4433a
Operating System:     [macOS]
Power Supply:         [USB]

Problem Description
I have a custom bootloader with some recovery mechanism implemented for my product.
The bootloader needs some persistent data to perform its operation (E.g boot counter, external WD time to configure etc.).
The easiest way to save such data in a reliable matter is NVS.
Unfortunately, in is not available in the bootloader binary and it is not trivial to compile it into the bootloader.
It would be really helpful to have NVS support in the bootloader, especially for mass-production products.

I don't think it is entirely practical, have you considered using the same strategy as otadata using 2 sectors to store raw binary data?

That is exactly what am I currently doing... 2 sectors containing the same data with CRC checksum on each.
Upon boot I read them and fix the corrupted one if something bad happened.
But - NVS is far more generic and capable, and I feel like I'm re-inventing the wheel.
It can't be that I'm the only one who finds NVS useful in the context of the bootloader...

Hi,
I am having the same problem, I implement my own bootloader state machine and had to implement my own i2c driver to use in bootloader context (which was a pain).
An NVS support could greatly ease the pain of flash storage access in bootloader.

Not arguing against it's usefulness, but bootloader runs from ram and can't conflict with the app sections it is going to then load to ram so minimal footprint is desirable.

Hi @shlomos @avrahamshukron ,
Thanks for sending this request and giving some information about your requirements. Is there any more details you can give about exactly what conditions you are checking for during the early boots? We have some current plans for adding optional bootloader support for detecting cases like the device getting stuck in boot/WDT loops.
Adding NVS support in the bootloader is a non-trivial amount of work, and it's relatively risky because we don't support bootloader OTA updates - the NVS partition format would need to remain compatible with the bootloader for the life of the product, and any bugs in the bootloader NVS implementation will remain there for the life of the product.
However I totally appreciate that the alternative is fairly primitive and fiddly by comparison.
The more details you can give us about exactly what case(s) you are checking for, what persistent information you need (and which parts of this information are written by the app vs written by the bootloader), the more chance there is that we can figure out a way to accommodate these use cases.

Our product is basically an IoT device that will be deployed by the thousands in field.
Once deployed, the cost of retrieving it back for maintenance is too high so our software and firmware needs to be reliable enough and contain recovery mechanisms.
But there's a catch 22 here:
We must be able to upgrade the firmware in order to keep communication with our servers.
So we came up with the following scheme that revolves around 2 software images:

Recovery image - basic image that can connect to our servers and can flah other OTA partitions.
Normal image with the complete functionality.

There bootloader job is to load the correct image based on some logic that we devised. This logic uses some non-volatile data, such as boot counter (SOFT_BOOT_COUNTER), external WD configuration (EXT_WD_TIME) and weather to load the recovery or normal image (IMAGE_SELECT).
On power-on reset, the bootloader will load the recovery image.
On soft reset:

If 'BOOT_COUNTER > 10', it'll perform hard reset using external WD (which will be experienced as POR) it'll load whatever is stored in IMAGE_SELECT.

If the counter was less or equal 10, it'll increment it by 1.

Arm external WD to EXT_WD_TIME

It'll look at IMAGE_SELECT and load the appropriate image and pass control to it.

This is the basic flow, I left a few details out for brevity and because some of it is confidential.
Hope that helps...


GestureDetector's onTapDown isn't working as expect with InAppWebView

Environment
Flutter version: v1.17.3
Plugin version:  3.4.0+1
iOS version: 13.5
Xcode version:  11.5
Device information:  iPhone 8 Plus
Description
Widget _buildWebView() {
    return GestureDetector(
      onTapDown: (TapDownDetails details) {
        print(details.globalPosition.dx);
      },
      child: InAppWebView(
        initialOptions: InAppWebViewGroupOptions(
          crossPlatform: InAppWebViewOptions(
            javaScriptEnabled: true,
            disableContextMenu: true,
            useShouldOverrideUrlLoading: true
          ),
          ios: IOSInAppWebViewOptions(
            allowsLinkPreview: false,
          ),
        ),
        initialUrl: project.url,
        onWebViewCreated: (InAppWebViewController controller) {
          setState(() => _webController = controller);
        },
      ),
    );
  }

Expected behavior:
GestureDetector onTapDown triggers when you tap on the web page
Current behavior:
GestureDetector onTapDown only trigger if you tap and hold for a short sec

I think you should use the InAppWebView.gestureRecognizers property. Have you tried it?

GestureDetector.onTapDown as written in the Official API: This is called after a short timeout, even if the winning gesture has not yet been selected.

An example using gestureRecognizers:
InAppWebView(
  gestureRecognizers: Set()
    ..add(
        Factory<TapGestureRecognizer>(() => TapGestureRecognizer()
          ..onTapDown = (TapDownDetails details) {
            print(details.globalPosition.dx);
          })),
  initialUrl: "https://flutter.dev/",
  initialOptions: InAppWebViewGroupOptions(
    crossPlatform: InAppWebViewOptions(
        debuggingEnabled: true,
    ),
  ),
  onWebViewCreated: (InAppWebViewController controller) {
    _webViewController = controller;
  },
),

GestureDetector.onTapDown as written in the Official API: This is called after a short timeout, even if the winning gesture has not yet been selected.

you need to press down much longer to get the event trigger if it wraps the InAppWebView comparing to a regular Container widget.

An example using gestureRecognizers:
InAppWebView(
  gestureRecognizers: Set()
    ..add(
        Factory<TapGestureRecognizer>(() => TapGestureRecognizer()
          ..onTapDown = (TapDownDetails details) {
            print(details.globalPosition.dx);
          })),
  initialUrl: "https://flutter.dev/",
  initialOptions: InAppWebViewGroupOptions(
    crossPlatform: InAppWebViewOptions(
        debuggingEnabled: true,
    ),
  ),
  onWebViewCreated: (InAppWebViewController controller) {
    _webViewController = controller;
  },
),

this doesn't seem to work

you need to press down much longer to get the event trigger if it wraps the InAppWebView comparing to a regular Container widget.

Are you using an emulator? I tested it on a real device and it works.

this doesn't seem to work

Could you post full code?

Are you using an emulator? I tested it on a real device and it works.

I tried it on both simulator and an iPhone 8 Plus, have to tap and hold for half a sec to trigger the onTapDown event whereas it's almost instant if you wrap a regular container in GestureDetector

Could you post full code?

@override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: InAppWebView(
        gestureRecognizers: Set()
          ..add(Factory<TapGestureRecognizer>(() => TapGestureRecognizer()
            ..onTapDown = (TapDownDetails details) {
              print(details.globalPosition.dx);
            })),
        initialOptions: InAppWebViewGroupOptions(
          crossPlatform: InAppWebViewOptions(
            debuggingEnabled: true,
          ),
        ),
        initialUrl: 'https://pub.dev/',
      ),
    );
  }

This doesn't work at all

I tried it on both simulator and an iPhone 8 Plus, have to tap and hold for half a sec to trigger the onTapDown event whereas it's almost instant if you wrap a regular container in GestureDetector

also, this is very inconsistent, sometimes it's instant sometimes you have to tap and hold

Ok, so I need to investigate it more!
As you can see, InAppWebView Widget is just an AndroidView on Android and an UiKitView on iOS:
https://github.com/pichillilorenzo/flutter_inappwebview/blob/master/lib/src/in_app_webview.dart#L288
So, it could be that the problem is related to the Flutter native views in general.
Have you encountered this problem with other native widgets? Have you tried it?
Thanks

I tested with another Flutter native view widget and it is the same.
So I think the problem lies on native views in general.
I have done some tests and it seems that it doesn't call the TapGestureRecognizer.acceptGesture method for some reason. It always cancels the tap event.
Instead, if you use the Listener widget, it seems to work:
Listener(
  onPointerDown: (event) {
    print(event);
  },
  child: InAppWebView(
    initialOptions: InAppWebViewGroupOptions(
      crossPlatform: InAppWebViewOptions(
        debuggingEnabled: true,
      ),
    ),
    initialUrl: 'https://pub.dev/',
  ),
),

I get the PointerDownEvent#f7e74(position: Offset(89.6, 444.7)) event instantly.
If you don't want to use the Listener widget, you could implement your custom gesture recognizer class, for example, extending the TapGestureRecognizer class, and pass it to the InAppWebView.gestureRecognizers property.

I tested with another Flutter native view widget and it is the same.
So I think the problem lies on native views in general.
I have done some tests and it seems that it doesn't call the TapGestureRecognizer.acceptGesture method for some reason. It always cancels the tap event.
Instead, if you use the Listener widget, it seems to work:
Listener(
  onPointerDown: (event) {
    print(event);
  },
  child: InAppWebView(
    initialOptions: InAppWebViewGroupOptions(
      crossPlatform: InAppWebViewOptions(
        debuggingEnabled: true,
      ),
    ),
    initialUrl: 'https://pub.dev/',
  ),
),

I get the PointerDownEvent#f7e74(position: Offset(89.6, 444.7)) event instantly.
If you don't want to use the Listener widget, you could implement your custom gesture recognizer class, for example, extending the TapGestureRecognizer class, and pass it to the InAppWebView.gestureRecognizers property.

Thanks, this works!


"Cannot convert a symbolic Tensor ({}) to numpy array"

I tried to use the interface from DeepXDE as mentioned here- "https://github.com/tensorflow/tensorflow/issues/48167#issuecomment-966596156" but encountered an error.  While I understand the error, I'm not sure how to resolve it. Any help in this regards is appreciated.
I'm using:
dde.optimizers.config.set_LBFGS_options(maxcor=50,ftol=1*np.finfo(float).eps,maxiter=100000,maxfun=100000,maxls=50)
self.optimizer = dde.optimizers.tfp_optimizer.lbfgs_minimize(self.trainable_var,self.loss)

The error:
"Cannot convert a symbolic Tensor ({}) to numpy array"
It seems like the function only accepts numpy arrays but I have a TF symbolic tensor. Any way to resolve this?
Originally posted by @rohitvuppala in https://github.com/tensorflow/tensorflow/issues/48167#issuecomment-1162519845

Accidentally opened an issue in the wrong repo where the comment originated, but this repo/package is unrelated to the issue.

@mohantym Could you please delete the issue?

Hi @rohitvuppala!
In 2.6 or earlier versions, The error on symbolic tensor was getting resolved when eager execution was disable or numpy version was upgraded to 1.21.5 or downgraded to 1.19.5 . From the 2.8 version onwards, Numpy version has upgraded to 1.21 which solved these issues in most cases. Please create a new issue if you need further assistance.
Thank you!

@mohantym Thank you didn't realize the bug might be related to tensorflow.
My tensorflow version is 2.8.1, numpy version is 1.22.4 and I did disable eager execution. Is the bug still related to tensorflow?

@rohitvuppala !
Sometimes it can get fixed through Numpy version upgrade/downgrade But Few issues need a code fix on the model side too. Could you update the template  with minimal stand alone code which will help us expedite the issue.
Thank you!


defaultChecked for Combobox sends wrong event on first click

When you have a switch or a ComBox with defaultChecked={true} the first click will not work

[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
The first click will result in a state change to "off"
Current Behavior
The first click does nothing and sends e.target.checked = true
Steps to Reproduce (for bugs)
Code at Sandbox:
https://codesandbox.io/s/l2qk3kpzqz

Load the Sandbox code
Click on the Switch
Nothing happens at first

Context
Your Environment

See Code Example for the dependencies

Tech
Version

Material-UI
current

React
16.2.0

browser
Firefox/Chrome

@oers This is a good catch, thanks for raising! We need to forward the defaultChecked property down to the input. Do you want to work on it?
https://github.com/mui-org/material-ui/blob/c0a712a986064c8c935a3063d9be2c54eb9b5bfc/src/internal/SwitchBase.js#L114-L126

Curious why defaultChecked is @ignoreed in the Selection controls?

@mbrookes It's a native input property.

Oops, so it is! 😊

This issue also affects the normal checkbox and nit just the switch.
@oliviertassinari I don't know enough React (yet) to feel comfortable to be able to fix this issue.

@oers The logic managed by a shared component internal/SwitchBase.js, so fixing it will fix it for all for all the selection controls.


close_console: Always unlock as the lock is always held [1.1.1]

This is a cherry-pick of  #17365 to 1.1.1 branch as it does not cherry-pick cleanly.
Fixes #17364

This pull request is ready to merge

Merged to 1.1.1 branch. Thank you for the review.


1Password Extension shows Twitter and other services when retrieving login. [Fixed in the latest 1Password 5.5 betas]

Since iOS 8.3 the extension now also shows other services that accept URL's. Not sure if this is solvable by the extension or is just a iOS 8.3 bug.

Hi @renssies,
Thanks for taking the time to write in :+1:
This is not an App Extension API bug, it's a 1Password one. We are aware of this issue and we already fixed it in the latest 5.5 betas for iOS. So, I'll be closing this issue.
Cheers!

Hi! Does this mean apps using the existing 1Password extension won't have to update/re-submit to get access to this bug fix?

Hi @noahemmet,
Exactly. You don't have to to make any changes or to resubmit your app. The fix is already in 1Password 5.5 betas.
As soon as we ship those fixes your app's share sheet will be fixed too :smile:
Thanks!

Hi again! Could I please be added to the 5.5 beta list? Thanks!

Hi @noahemmet,
Please drop us a line to<EMAIL_ADDRESS>along with a link to this issue.
Thanks!


Ericchoi/main/event hub/2024 01 01

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

from: namespaces-preview.json

going to need to fix/duplicate this to match the filename 'namespaces.json'

Refers to: specification/eventhub/resource-manager/readme.md:235 in 8c4c11c. [](commit_id = 8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e, deletion_comment = False)

I think LintDiff is confused by the filenames changing - they never should have had '-preview' suffixes - namespace-preview changing to namespace seems to have confused the 'new code detection' part of linting.

Only linter errors from Clusters.json should matter for this review:
Here is the current crop:
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="DeleteResponseCodes" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [DeleteResponseCodes](https://github.com/Azure/azure-openapi-validator/blob/main/docs/delete-response-codes.md)|

| Messges |
| --------|
| Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L280) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="EnumInsteadOfBoolean" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|⚠ [EnumInsteadOfBoolean](https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md)|

| Messges |
| --------|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L463) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="GetCollectionOnlyHasValueAndNextLink" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [GetCollectionOnlyHasValueAndNextLink](https://github.com/Azure/azure-openapi-validator/blob/main/docs/get-collection-only-has-value-and-next-link.md)|

| Messges |
| --------|
| Get endpoints for collections of resources must only have the `value` and `nextLink` properties in their model.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L354) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="LroErrorContent" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [LroErrorContent](https://github.com/Azure/azure-openapi-validator/blob/main/docs/lro-error-content.md)|

| Messges |
| --------|
| Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L215) |
| Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L274) |
| Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L318) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="LroLocationHeader" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [LroLocationHeader](https://github.com/Azure/azure-openapi-validator/blob/main/docs/lro-location-header.md)|

| Messges |
| --------|
| A 202 response should include an Location response header.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L209) |
| A 202 response should include an Location response header.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L268) |
| A 202 response should include an Location response header.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L309) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="PageableOperation" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|⚠ [PageableOperation](https://github.com/Azure/azure-openapi-validator/blob/main/docs/pageable-operation.md)|

| Messges |
| --------|
| Based on the response model schema, operation 'Clusters_ListNamespaces' might be pageable. Consider adding the x-ms-pageable extension.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L326) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="ParameterNotDefinedInGlobalParameters" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|⚠ [ParameterNotDefinedInGlobalParameters](https://github.com/Azure/azure-openapi-validator/blob/main/docs/parameter-not-defined-in-global-parameters.md)|

| Messges |
| --------|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L49) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L88) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L130) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L170) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L232) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L291) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L331) |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L373) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="PatchResponseCodes" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [PatchResponseCodes](https://github.com/Azure/azure-openapi-validator/blob/main/docs/patch-response-codes.md)|

| Messges |
| --------|
| Long-running PATCH operations must have responses with 200, 202 and default return codes. They also must not have other response codes.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L221) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="PutResponseCodes" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [PutResponseCodes](https://github.com/Azure/azure-openapi-validator/blob/main/docs/put-response-codes.md)|

| Messges |
| --------|
| Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L159) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="ResourceNameRestriction" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [ResourceNameRestriction](https://github.com/Azure/azure-openapi-validator/blob/main/docs/resource-name-restriction.md)|

| Messges |
| --------|
| The resource name parameter 'clusterName' should be defined with a 'pattern' restriction.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L118) |
| The resource name parameter 'clusterName' should be defined with a 'pattern' restriction.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L325) |
| The resource name parameter 'clusterName' should be defined with a 'pattern' restriction.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L367) |
" type="ValidationResult"/>
</testcase>
<testcase classname="Microsoft.EventHub/stable/2024-01-01/Clusters.json" name="SystemDataDefinitionsCommonTypes" file="Microsoft.EventHub/stable/2024-01-01/Clusters.json">
  <failure message="| Rule |
|------|
|❌ [SystemDataDefinitionsCommonTypes](https://github.com/Azure/azure-openapi-validator/blob/main/docs/system-data-definitions-common-types.md)|

| Messges |
| --------|
| System data references must utilize common types.
Location: [Microsoft.EventHub/stable/2024-01-01/Clusters.json](https://github.com/Azure/azure-rest-api-specs/blob/8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e/specification/eventhub/resource-manager/Microsoft.EventHub/stable/2024-01-01/Clusters.json#L418) |
" type="ValidationResult"/>
</testcase>

from: namespaces-preview.json

Its probably not going to matter actually.

In reply to:<PHONE_NUMBER>

Refers to: specification/eventhub/resource-manager/readme.md:235 in 8c4c11c. [](commit_id = 8c4c11ca5fa709eda1ed03e85572dc8c8f1c985e, deletion_comment = False)

Looks good to me. Signing off the API. You can update descriptions again as you wish before requesting merge.

@ericchoi319
Just noticed you now have model validation errors where examples need to be updated to match the OpenAPI spec changes. These need to be fixed before merge.

I'm confused about why Avocado is failing here, saying that these APIS need to be in the default set. Anyone know if it matters? @raych1 @rkmanda

/pr RequestMerge


[Refactor] split stage and reference age

Development
Description
add split stage and reference age
Implementation

split stage
reference age
save file

Required Hidden Data
NaN
Checklist

[x] Detail implementation description at the top of notebook
[x] Data input and output paths are correct
[x] Free of spurious comments
[x] Free of unnecessary notebook updates (e.g. cell executions count)

add description at the top of the notebook


[ISSUE 245] fix wrong recover logic after reseting offset

issue: https://github.com/openmessaging/dledger/issues/245

@RongtongJin @tsunghanjacktsai  Plz have a look~


AFL_TMPDIR is being ignored

If the environment variable AFL_TMPDIR is set the .cur_input file still gets written into the standard output directory. The problem is that out_dir gets used to build the path for out_file instead of tmp_dir.
Also the code to check if an input file already exists in TMP_DIR has two problems:

It does not check if file_extension is defined
I am pretty sure the parenthesis in the following line is at the wrong position and could lead to problems:
char tmpfile[strlen(tmp_dir + 16)];

Hi, thanks.
I agree with both problems, well spotted.
We need to investigate.

@CaBeckmann can you please peer review the fix when hexcoder is done? Thanks!

I am done now.

The change looks good and works for me. Thanks for the quick solution!
There was one thing I noticed while testing: When you use AFL_TMPDIR session resumption only works if you manually delete the .cur_input file. I am not sure if this is something that can be easily fixed though.

@CaBeckmann that check is to ensure that not the same AFL_TMPDIR is used for more than one instance. In the case of a restart though we can conclude that everything is fine, so I disabled the check for resuming.
I am closing this now - reopen if you find any other issues :)


Remove #[derive(Debug)] from library structs

Fixes #326.

@tikue Thank you for the review.

Woo! Thank you!


DPDK L3Fwd test (stacked PR)

This PR adds the l3fwd test to dpdkutil.py, dpdksuite.py, and dpdkperf.py
It is a stacked PR, building on the content from:
Routing tables: az route and linux kernel routing with ip route by mcgov · Pull Request #3020 · microsoft/lisa (github.com)
MANA: enable rdma-core source installation by mcgov · Pull Request #2981 · microsoft/lisa (github.com)

#3048 has been merged


video transcoding when sending

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #support.

iMessage does not seem to like videos created with (probably not limited to) Google Cam.
However changing the color profile metadata allows the videos to send fine
See https://github.com/streamio/streamio-ffmpeg/issues/205
Would be great if BB could allow the checking and changing of this metadata before sending it over iMessage

The problem with bundling ffmpeg is that the binary for it is fairly large and adds a good bit of size to the app. I've tried to do it when sending mov videos and it works, but in this case, im not sure how i'd detect a google cam video and convert it.


Mirroring in spanning mode

Sometimes the screensaver (though set to span) instead mirrors to the second display.

Hi @Kamik423
A debug log with the time where you see this happen would be super helpful. Can you give me that ? Thanks !

Also, there was a bug with display detection and spanned mode which may just be your issue, it's fixed in latest betas. I'd suggest you try this one:
https://github.com/JohnCoates/Aerial/releases/download/v1.5.1beta4/Aerial.saver.zip

Ok. The latest beta had a warning for non-catalina users, so I was careful with that. I'll try it out. Thanks!

Yep that's why I picked beta4, it should be safe for you, I highly suggest you avoid 5 and (coming in a minute) 6 for now on!

ok. I cannot currently cause the issue to occur by calling the screensaver again and again. Maybe it only gets corrupted after runnings some while. I have logging enabled and will post if it happens again.

No worries. Let me know if that happen!

If it helps, I was encountering a similar-sounding issue on a late 2018 MBP 15" connected to an external display via HDMI.
macOS 10.15 Catalina public beta 3 (19A487m)
I can't recall if I checked every mode, but I have a feeling I did, and each time the screensaver started - both on clicking Preview from Preferences and letting screensaver start after timeout, it would only display on the external monitor, never on the Internal screen; and would not engage spanning mode.
Logs showed correct multi-monitor detection. I do not have any custom videos added, so that explains a warning for a missing customvideos.json, however I am unsure of the purpose of TVIdleScreenStrings.bundle.
aerial-log.txt is a log for a run which rendered only on the secondary screen ( id 458669855), beginning at Display Detection, and ending at the successful completion of playing the second video file.
To my untrained eye, I can't see any particular error messages that might relate to this specific issue under Catalina - if it's the same root cause I do not know.

Hi @crampus !

macOS 10.15 Catalina public beta 3 (19A487m)

Ha !

it would only display on the external monitor, never on the Internal screen; and would not engage spanning mode.

So, this is actually a Catalina bug with all 3rd party screensavers, including Aerial. They only work on the (last?) monitor in a multi monitor setup. I reported this to Apple and waiting for a fix.

however I am unsure of the purpose of TVIdleScreenStrings.bundle.

This was a bug in beta6 (this is some of the text stuff displayed on screen, that was missing in that version). This is fixed in beta7.

To my untrained eye, I can't see any particular error messages that might relate to this specific issue under Catalina - and honestly I don't even know if it's the same root cause...

Yeah this is a different issue. I would highly suggest you have a look to the Catalina thread (read the top post) to see the various issues related to Catalina ! Check it out here (includes link to beta7 which you should upgrade to, expect a few more betas as we're working around bugs with Catalina !) : https://github.com/JohnCoates/Aerial/issues/801#issue-451690608

Thanks @glouel, extra brave, this is my daily driver and I use it for work every day as a support tech 😅
I have been keeping an eye on the main post, but didn't dive in too deep to see what else is hidden in there. Figured I'd see if I could be helpful with this one at least.
I rarely use external monitors (All the monitors that look nice next to MBP Retina are too expensive and don't come with stands... 😬)

Thanks @glouel, extra brave, this is my daily driver and I use it for work every day as a support tech 😅

Indeed ! Hopefully next beta will fix the multi monitor issue !

I rarely use external monitors (All the monitors that look nice next to MBP Retina are too expensive and don't come with stands... 😬)

🤣

Closing this, reopen if you have an issue again but pretty sure it's fixed.

Just chiming in to let you know that this has not happened again on my machine either.