Issues found for Azure Virtual Network Manager

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
1, For list-active-connectivity-config, after I add parameter regions, it will still return results from all regions.
2,  Security-type in security configuration should be readonly. Can you remove it from example.
3,  When creating security configuration with only required parameters(resource group/name/networkmanager name), the request will fail.
I checked the debug log. It seems the request body is empty({}), which is not acceptable for our gateway. So can you make a change so that it will contain empty property({“property”:{}}). (I am not 100% sure that it will work, so can you try it after making such change)?
4, in rule collection example, it should be network-group-id="/subscriptions/sub_id/resourceGroups/rgid/providers/Microsoft.Network/networkManagers/TestNetworkManager/networkGroups/TestNetworkGroup"
5, The targetlocation in post-commit should be required.
To Reproduce

Expected behavior

Environment summary

Additional context

network

Hi @yanfa317, I've some issue for 3 point. Does the 'property' marked as required in swagger definition?


examples/airship: Very slow on browsers

This is fast enough on 1.11. Then, this is a performance regression.

git bisect says f8956941b7b199de61d3addfd4a874ecead52101 is the culprit.


Add proxy register and admin command

What changes are proposed in this pull request?

Adds the mechanism for proxy instances to register(heartbeat) with master
Adds corresponding lost proxy detection
Adds a command to list all proxy instances from master, and all supporting code to make that happen

✗ bin/alluxio fsadmin report proxy
1 Proxy instances in the cluster, 1 serving and 0 lost

Address                  State    Start Time       Last Heartbeat Time  Version                          Revision
<IP_ADDRESS>:39997            ACTIVE   20230421-165608  20230421-170201      2.10.0-SNAPSHOT                  c697105199e29a480cf6251494d367cf325123a0

Why are the changes needed?
This change establishes the infra for a better mgmt on the proxy instances in the cluster.
Does this PR introduce any user facing changes?
A command is added.

@jiacheliu3 I have a high level suggestion, now we have many kind of client, some of them are long life process client, for example AlluxioProxy, AlluxioFUSE, HadoopClientBasedAlluxioClient(Presto、Spark、Flink、xxx), if we want to monitor the life time of AlluxioProxy, we can also monitor other long life process client.
So, I suggest to make the concept more generic, we monitor all long life client and accept them to register to Alluxio master, we can also manage them as Live or lost, meanwhile, we can use clientType and clientId to distinguish them.

@jiacheliu3 https://github.com/Alluxio/alluxio/pull/17225#issuecomment-1512346939 How about your idea?

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.10 please

alluxio-bot, cherry-pick this to branch-2.8 please


distinctUntilChanged not working with array

Bug Report
Current Behavior
I'm currently building with Angular a advanced multistep form where a root component checks the validity on a change in the form to disable and activate the next button, to prevent a infinite loop i use a distinctUntilChanged() on the valuechanges of the form.
But when trying to update a array in the form the distinctUntilChanged wil say that there is no change.
this.registerService.form.valueChanges.pipe(distinctUntilChanged((a, b) => JSON.stringify(a) === JSON.stringify(b)))
    .subscribe(() => {
        this.currentStepValid = this.registerService.checkValid(this.activeStep);
});

Expected behavior
I would expect the distinctUntilChanged to fire when an array has been updated
Environment

Runtime: [e.g. Node v${x}, Chrome v${x}]
RxJS version: 6.6.0
Angular: 8.1.2

Additional context/Screenshots
When logging a and b from the distinctUntilChanged it seems that adding a value will not see a change but removing will:
Output when adding:
a: '{"exampleArray": [3, 4]}'
a: '{"exampleArray": [3, 4]}'
Output when removing:
a: '{"exampleArray": [3, 4]}'
a: '{"exampleArray": [4]}'

Please provide reproducible code without involving app code to clarify if this is rx core issue.


Fix name of arm64 platform from linux-arm to linux-arm64

Bug description
We have wrongly named our 64 bit arm platform for linux as linux-arm instead of linux-arm64 (please note that Mac arm64 name is correct darwin-arm64)
This has caused bugs around detection of 32 bit ARM devices and it lead to https://github.com/prisma/prisma/issues/8575
This can also cause other confusion down the road.
How to reproduce
See https://github.com/prisma/engines-wrapper/blob/e0f2a284b4f6bc8ca225d6e2cf044e7d86e671b3/packages/get-platform/src/getPlatform.ts#L201-L203
Expected behavior
arm64 target should be called linux-arm64. Also, please note while fixing this, add linux-arm (32 bit arm) to known but ignored platforms.
Prisma information
Not relevant
Environment & setup
Not relevant
Prisma Version
Not relevant

Related code:
https://github.com/prisma/engines-wrapper/search?q=arm
https://github.com/prisma/engineer/search?q=arm
https://github.com/prisma/engine-images/search?q=arm

This was done in 3.1.0-dev.12


Enhancement in notification center

Desired Behavior

The upper icon is user icon and below is the connection icon. On hover it should provide some specific information

There is some cases where docs link specific to that notification is missing, Any error or information notification log or code should have link to redirect to docs

[database] When a design is imported name of design is missing

Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@sudhanshutech can you tell me how can i reproduce the issue


Fix race condition between setting developer mode and config fetch

Fix #4740
Insure that minimumFetchInterval setting is applied before fetching.  Otherwise there will be indeterministic behavior when trying to verify console changes in an app.
I've verified in a sample and will work on adding a unit test.
I'd like to get the review going since I'd like to get this fix in M71.

- (void)fetchWithCompletionHandler:(FIRRemoteConfigFetchCompletion)completionHandler { should be fixed.
More investigation still needed for
- (void)fetchWithExpirationDuration:(NSTimeInterval)expirationDuration
                  completionHandler:(FIRRemoteConfigFetchCompletion)completionHandler {

Testing was done manually with the new API tests in #5602. They'll be merged once automation is added for them.
All other automated tests passed on commit before changelog update.


Arranged Adopters in alphabetical order : Hactoberfest

Closes: #609

Please review it @claireyuw .

@iamartyaa Thank you for your contribution! I have approved your changes. Will wait till October to merge your PR in order for it to count toward your Hactoberfest participation.

@claireyuw , Please merge the PR.

Hey @claireyuw , Please merge the Pull Request.
Can you add "Hactoberfest-accepted" label to it before merging because this PR is not being tracked by my Hactoberfest portal yet.
Thank you.
It's amazing contributing to it Milvus.


Added Solution for the lc problem 3185

Related Issue
Fix #1620
Description
[Please include a brief description of the changes or features added]
Type of PR

[ ] Bug fix
[X] Feature enhancement
[X] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist

[X] I have performed a self-review of my code.
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have followed the code style guidelines of this project.
[X] I have checked for any existing open issues that my pull request may address.
[X] I have ensured that my changes do not break any existing functionality.
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[X] I have read the resources for guidance listed below.
[X] I have followed security best practices in my code changes.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Please read the following resources before submitting your contribution:

[X] Code Harbor Hub Community Features
[X] Docusaurus Documentation
[X] React.js Documentation
[X] Markdown Guide
[X] MDX Documentation
[X] Mermaid Documentation

Resources for DSA Features on Our Site:

[X] Tabs: Switch Languages
[x] Line Numbering
[X] Math Equations

Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the level1 label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to level2. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Level1:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Level2:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Level3:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

@Ajay-Dhangar changed the complexity as suggested by you .


TopN queries with multiple independent dimensions

It has the following benefits:

Filtering (which is sometimes very expensive) part of the query processing could be done only once for all dimensions.
Reduce the amount of network communication between historicals and brokers, essentially several distinct queries are "multiplexed" in a single one.

It's a common pattern for analytics systems based on Druid to present multiple topN results based on the same filter at the same time. This feature has been asked for in the community: https://groups.google.com/forum/#!topic/druid-user/Hl_axJ4Y7X4

cc @drcrallen


Fix deprecation warning in ci failure

Fixes the ci failure:
Checking project camera...
  info - 'showSnackBar' is deprecated and shouldn't be used. Use ScaffoldMessenger.showSnackBar. This feature was deprecated after v1.23.0-14.0.pre. at example/lib/main.dart:275:31 - (deprecated_member_use)

https://cirrus-ci.com/task/4518227873103872?command=main#L292
This only fix the deprecation warning in camera and webview_flutter, the error in url_launcher_web should be fixed with https://github.com/flutter/plugins/pull/3155

Will, the API is not in stable. I'm going to add the allow warning instead of fixing it.

@ditman updated with ignore warning, PTAL

Landing on red to fix ci.


Exception thrown by breadboard debug

When trying to run breadboard debug for worker.ts, getting this exception:
Failed to load board at "[path elided]/breadboard/packages/agent-kit/src/boards/structured-worker.ts": Failed to load board from source
Error: Dynamic require of "assert" is not supported

Investigating...
@PaulKinlan if anything jumps out at you immediately, LMK.

Figured it out. Need to mark "node:fs/promises", "node:vm" as external.

This is good to know. I will check to see if there are any more.


VSCode crash on start after packages updated on kubuntu 21.10 (development branch)

# /usr/share/code/code
[main 2021-09-06T12:15:47.061Z] update#setState idle
[2930:0906/221547.065651:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[2930:0906/221547.373376:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[2930:0906/221547.534308:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3036:0906/221547.552065:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[2930:0906/221547.640368:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3040:0906/221547.648768:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[2930:0906/221547.743235:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3044:0906/221547.751366:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[2930:0906/221547.839606:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3048:0906/221547.843726:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[2930:0906/221547.952225:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3052:0906/221547.955907:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[2930:0906/221548.067570:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[3056:0906/221548.071281:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[2930:0906/221548.175118:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[2930:0906/221548.175137:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Server response:
Server response:
Недопустимая инструкция (стек памяти сброшен на диск)

Last message is "Unsupported instruction (stacktrace dumped to disk)"

Same here using Ubuntu 21.10 dev.

Traceback:
$ code --verbose
[main 2021-09-06T21:54:34.951Z] Starting VS Code
[main 2021-09-06T21:54:34.951Z] from: /usr/share/code/resources/app
[main 2021-09-06T21:54:34.951Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '634bea06-2fc3-4a0c-aa5c-d7fb1ef5d397',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  logsPath: '/home/hadim/.config/Code/logs/20210906T175434'
}
[main 2021-09-06T21:54:34.953Z] Resolving machine identifier...
[main 2021-09-06T21:54:34.953Z] Resolved machine identifier: d2abc133a0442c638f626ba13c6747cc41ce11a92774dec98b2b99b81139aba3
[main 2021-09-06T21:54:34.953Z] Main->SharedProcess#connect
[main 2021-09-06T21:54:34.964Z] StorageMainService: creating global storage
[main 2021-09-06T21:54:34.965Z] lifecycle (main): phase changed (value: 2)
[main 2021-09-06T21:54:34.966Z] windowsManager#open
[main 2021-09-06T21:54:34.967Z] windowsManager#open pathsToOpen [
  {
    workspace: { id: '80a64860979efd1fcf8717876136a349', uri: [g] },
    exists: true
  }
]
[main 2021-09-06T21:54:34.969Z] IPC Object URL: Registered new channel vscode:006d9618-ae92-4209-a2b8-0c7aea3dcf59.
[main 2021-09-06T21:54:34.969Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 0, y: 102, width: 2289, height: 1288 }
[main 2021-09-06T21:54:34.969Z] window#validateWindowState: 1 monitor working area { x: 0, y: 27, width: 2560, height: 1363 }
[main 2021-09-06T21:54:34.969Z] window#ctor: using window state { mode: 1, x: 0, y: 102, width: 2289, height: 1288 }
[main 2021-09-06T21:54:35.001Z] StorageMainService: creating workspace storage (80a64860979efd1fcf8717876136a349)
[main 2021-09-06T21:54:35.002Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 1, emptyToRestore: 0, emptyToOpen: 0)
[main 2021-09-06T21:54:35.003Z] lifecycle (main): phase changed (value: 3)
[main 2021-09-06T21:54:35.004Z] update#setState idle
[main 2021-09-06T21:54:35.004Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[5021:0906/175435.037401:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.037419:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 1 time(s)
[main 2021-09-06T21:54:35.071Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[5021:0906/175435.189392:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.189447:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 2 time(s)
[5021:0906/175435.381836:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.381850:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 3 time(s)
[5097:0906/175435.393328:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[5021:0906/175435.480713:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.480740:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 4 time(s)
[5101:0906/175435.493576:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[5021:0906/175435.578542:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.578606:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 5 time(s)
[5105:0906/175435.593475:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[5021:0906/175435.717234:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.717259:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 6 time(s)
[5109:0906/175435.721236:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[5021:0906/175435.817297:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.817339:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 7 time(s)
[5113:0906/175435.821641:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[5021:0906/175435.904632:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175435.904653:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 8 time(s)
[5117:0906/175435.908288:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[5021:0906/175436.000169:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[5021:0906/175436.000197:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 9 time(s)
[5021:0906/175436.000206:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.

Run with code --disable-gpu --disable-software-rasterizer as workaround

Any chance to use VSCode without disabling the GPU? Is it something that should be fixed on the VSCode side or Ubuntu side?

b039eaa1-540a-4554-8e58f799-fc055e93.zip

Thanks for the logs, can you also confirm your systemd versions systemctl --version, wondering if you are hitting https://github.com/microsoft/vscode/issues/132609

systemd 248 (248.3-1ubuntu3)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid

Since the gpu process exit codes are similar between https://github.com/microsoft/vscode/issues/132609 and here, will check if the runtime fix helps. I will update here once we have a new build to verify. Couldn't get enough detail from the crash dumps as they appear incorrect after symbolication for this particular crash.

Hello, my vscode also suddenly started to crash on ubuntu + nvidia. Same systemd.
Tried to downgrade from 1.60 to 1.59, no success.
Also tested with nouveau driver, failing.
Nvidia driver 460 and 470, failing.

If possible can anyone try the following steps,

Download https://www.electronjs.org/fiddle
Run with Electron v13.3.0 and it should fail
Run with Electron v14.0.0 and it should work

It will help me confirm the fix I had backported addresses the issue.

Run with Electron v13.3.0 and it should fail
Run with Electron v14.0.0 and it should work

Confirm that

Thanks for confirming!

The latest insider does not work for me:
$ code-insiders --version
1.61.0-insider
1b9403cd461c9c975bcb9e48d84ba9e4ea86559e
x64

$ code-insiders --verbose
[main 2021-09-21T23:28:46.777Z] Starting VS Code
[main 2021-09-21T23:28:46.778Z] from: /usr/share/code-insiders/resources/app
[main 2021-09-21T23:28:46.778Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '5cbd6415-6ff7-4d74-a2a5-2d5be895a0e1',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  logsPath: '/home/hadim/.config/Code - Insiders/logs/20210921T192846'
}
[main 2021-09-21T23:28:46.779Z] Resolving machine identifier...
[main 2021-09-21T23:28:46.780Z] Resolved machine identifier: d2abc133a0442c638f626ba13c6747cc41ce11a92774dec98b2b99b81139aba3
[main 2021-09-21T23:28:46.781Z] Main->SharedProcess#connect
[main 2021-09-21T23:28:46.792Z] StorageMainService: creating global storage
[main 2021-09-21T23:28:46.793Z] lifecycle (main): phase changed (value: 2)
[main 2021-09-21T23:28:46.795Z] windowsManager#open
[main 2021-09-21T23:28:46.795Z] windowsManager#open pathsToOpen [ [Object: null prototype] {} ]
[main 2021-09-21T23:28:46.797Z] IPC Object URL: Registered new channel vscode:8aa05db1-7415-439d-a5d4-98e7f6720eba.
[main 2021-09-21T23:28:46.797Z] window#validateWindowState: validating window state on 1 display(s) {
  width: 1024,
  height: 768,
  mode: 1,
  x: 768,
  y: 336,
  hasDefaultState: true
}
[main 2021-09-21T23:28:46.797Z] window#validateWindowState: 1 monitor working area { x: 0, y: 27, width: 2560, height: 1363 }
[main 2021-09-21T23:28:46.797Z] window#ctor: using window state {
  width: 1024,
  height: 768,
  mode: 1,
  x: 768,
  y: 336,
  hasDefaultState: true
}
[main 2021-09-21T23:28:46.842Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 0, emptyToOpen: 1)
[main 2021-09-21T23:28:46.843Z] lifecycle (main): phase changed (value: 3)
[main 2021-09-21T23:28:46.844Z] update#setState idle
[main 2021-09-21T23:28:46.845Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[8249:0921/192846.879167:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192846.879190:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 1 time(s)
[main 2021-09-21T23:28:46.928Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[8249:0921/192847.076954:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.076974:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 2 time(s)
[8249:0921/192847.265894:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.265918:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 3 time(s)
[8326:0921/192847.279670:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[8249:0921/192847.407715:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.407737:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 4 time(s)
[8330:0921/192847.417157:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[8249:0921/192847.543457:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.543478:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 5 time(s)
[8334:0921/192847.552576:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[8249:0921/192847.682436:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.682455:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 6 time(s)
[8338:0921/192847.687252:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[8249:0921/192847.805284:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.805303:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 7 time(s)
[8342:0921/192847.808835:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[8249:0921/192847.928488:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192847.928502:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 8 time(s)
[8346:0921/192847.932100:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[8249:0921/192848.038422:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[8249:0921/192848.038456:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 9 time(s)
[8249:0921/192848.038465:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:

Using --no-sandbox works for both code and code-insiders.

If things still don't seem right, please ensure you're on version 1b9403c of Insiders

In message above, @hadim use exacly that version and it is not working as expected.

Thanks for verifying, can you provide the following additional data to help debug further

Please attach the crash report from latest insiders based on https://github.com/microsoft/vscode/issues/132455#issuecomment-914822389
Please attach the log output from code-insiders --verbose --enable-gpu-debugging
Does the issue repro when you launch with --disable-gpu-sandbox ?

Please attach the crash report from latest insiders based on VSCode crash on start after packages updated on kubuntu 21.10 (development branch) #132455 (comment)

crash.zip

Please attach the log output from code-insiders --verbose --enable-gpu-debugging

$ code-insiders --verbose --enable-gpu-debugging
Warning: 'enable-gpu-debugging' is not in the list of known options, but still passed to Electron/Chromium.
[main 2021-09-22T12:41:35.306Z] Starting VS Code
[main 2021-09-22T12:41:35.307Z] from: /usr/share/code-insiders/resources/app
[main 2021-09-22T12:41:35.307Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '5cbd6415-6ff7-4d74-a2a5-2d5be895a0e1',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  logsPath: '/home/hadim/.config/Code - Insiders/logs/20210922T084135'
}
[main 2021-09-22T12:41:35.308Z] Resolving machine identifier...
[main 2021-09-22T12:41:35.308Z] Resolved machine identifier: d2abc133a0442c638f626ba13c6747cc41ce11a92774dec98b2b99b81139aba3
[main 2021-09-22T12:41:35.309Z] Main->SharedProcess#connect
[main 2021-09-22T12:41:35.317Z] StorageMainService: creating global storage
[main 2021-09-22T12:41:35.318Z] lifecycle (main): phase changed (value: 2)
[main 2021-09-22T12:41:35.319Z] windowsManager#open
[main 2021-09-22T12:41:35.319Z] windowsManager#open pathsToOpen [
  {
    backupPath: '/home/hadim/.config/Code - Insiders/Backups/1632266998887',
    remoteAuthority: undefined
  }
]
[main 2021-09-22T12:41:35.320Z] IPC Object URL: Registered new channel vscode:c486bd22-4d9c-434f-ba45-715200186835.
[main 2021-09-22T12:41:35.321Z] window#validateWindowState: validating window state on 2 display(s) { mode: 1, x: 550, y: 217, width: 1024, height: 768 }
[main 2021-09-22T12:41:35.321Z] window#validateWindowState: multi-monitor working area { x: 0, y: 27, width: 2560, height: 1363 }
[main 2021-09-22T12:41:35.321Z] window#ctor: using window state { mode: 1, x: 550, y: 217, width: 1024, height: 768 }
[main 2021-09-22T12:41:35.360Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-09-22T12:41:35.361Z] lifecycle (main): phase changed (value: 3)
[main 2021-09-22T12:41:35.362Z] update#setState idle
[main 2021-09-22T12:41:35.362Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[9259:0922/084135.386123:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084135.386142:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 1 time(s)
[9259:0922/084135.585746:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084135.585762:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 2 time(s)
[9259:0922/084135.746237:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084135.746259:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 3 time(s)
[9337:0922/084135.757996:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[9259:0922/084135.881232:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084135.881252:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 4 time(s)
[9341:0922/084135.889835:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[9259:0922/084135.993059:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084135.993081:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 5 time(s)
[9345:0922/084136.000898:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader
[9259:0922/084136.096607:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084136.096628:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 6 time(s)
[9349:0922/084136.100686:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[9259:0922/084136.182529:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084136.182546:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 7 time(s)
[9353:0922/084136.186664:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[9259:0922/084136.275375:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084136.275433:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 8 time(s)
[9357:0922/084136.279006:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[9259:0922/084136.359687:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159
[9259:0922/084136.359707:WARNING:gpu_process_host.cc(1321)] The GPU process has crashed 9 time(s)
[9259:0922/084136.359717:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:

3. Does the issue repro when you launch with --disable-gpu-sandbox ?

No I can't reproduce with that flag. Code works correctly.

I just tested and got the same results as hadlm:  Same 159 exit codes and "GPU process isn't usable" s in the log when using --enable-gpu-debugging, whereas using --disable-gpu-sandbox causes it to work without crashing.

Run with code --disable-gpu --disable-software-rasterizer as workaround

By the way, sometimes need to run it several times to run code without crash.
With --disable-gpu-sandbox it run more stable, but I don't want to disable sandbox.

Thanks for the logs, the root issue has been narrowed down. Merging to https://github.com/microsoft/vscode/issues/133593


"dotnet interactive jupyter install" fails on MacOS BigSur

When installing dotnet interactive to Jupyter, I get this:

dotnet interactive jupyter install

The kernelspec path /Users/thomas/~/.local/share/jupyter/kernels does not exist.
Failed to install ".NET (PowerShell)" kernel.
The kernelspec path /Users/thomas/~/.local/share/jupyter/kernels does not exist.
Failed to install ".NET (C#)" kernel.
The kernelspec path /Users/thomas/~/.local/share/jupyter/kernels does not exist.
Failed to install ".NET (F#)" kernel.

I'm running MacOS BigSur
I have .net 5.0.100-rc.2.20479.15
and .net interactive 1.0.151601+c44fed791093db19261c49b39d7d901e7983a3af

It will take my current path and append ~/.local/share/jupyter/kernels to it so the path it looks for never exists.

@thomasd3 we have addressed part of the problem, could you test again.

it's working now:
~/Downloads ᐅ dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-interactive
You can invoke the tool using the following command: dotnet-interactive
Tool 'microsoft.dotnet-interactive' (version '1.0.152204') was successfully installed.
~/Downloads ᐅ jupyter kernelspec list
Available kernels:
  ifsharp    /Users/thomas/Library/Jupyter/kernels/ifsharp
  python3    /Users/thomas/opt/anaconda3/share/jupyter/kernels/python3
~/Downloads ᐅ dotnet interactive jupyter install

Welcome to .NET Interactive!
---------------------
Telemetry
---------
The .NET Core tools collect usage data in order to help us improve your experience.The data is anonymous and doesn't include command-line arguments. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_TRY_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Installing using jupyter kernelspec module.
Installed ".NET (PowerShell)" kernel.
Installing using jupyter kernelspec module.
Installed ".NET (C#)" kernel.
Installing using jupyter kernelspec module.
Installed ".NET (F#)" kernel.


Document how to get test $ETH on dev-cluster

While waiting for https://github.com/astriaorg/dev-cluster/issues/10 we should document the process to manually get test $eth to a user's wallet address.

Initial tokens are set here: https://github.com/astriaorg/dev-cluster/blob/main/kubernetes/genesis/geth-genesis.json#L20
Lowest bar to getting this workable is to use a new public key and document the seed phrase for it


fix: Property pane - Hidden sections icon select popover not opening properly

Description
In the property pane of the JSON Form widget; were 2 icon selectors both of them in a different collapsed section. As the popover width was being set by targeting the class .bp3-select-popover, the first was getting overridden by the second instance of the popover and thus getting the width of 0 (because of the hidden state of 2nd icon selector).
They now have separate class names based on id.
Fixes #13879
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Cypress

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/13879-collapsed-section-icon

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
56.56 (0)
38.54 (-0.01)
35.87 (0)
56.8 (0)

:green_circle:
app/client/src/components/propertyControls/IconSelectControl.tsx
91.49 (0.19)
76.11 (0)
95.83 (0)
91.47 (0.13)

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
70.59 (-1.96)
100 (0)
92.38 (-0.95)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

/ok-to-test sha=e8ed469

@ashit-rath tested on the DP and it's working fine.


kbs_protocol: use rusttls when rust-crypto feature is enabled

reqwest uses the platform's native TLS stack by default, also when rusttls is enabled.
Force reqwest Client to use rustls TLS stack when rust-crypto feature is enabled. This is what users most likely expect to get.

cc @Xynnn007 . This should also be added to your PR #304 .


feat: port/CategoryTheory.Sites.Limits

OK so I've basically got this file compiling, but it's no good. Typeclass inference can't solve certain universe problems, which means that the instances defined in this file aren't going to fire.

Ok so it looks like a good fix is to change the objects of C to live in Type u. I've done this in mathlib3 at https://github.com/leanprover-community/mathlib/pull/18817 and will then forward-port to this and the instances should then fire.

I think the only thing left with this PR is an erw which is generating two extra goals in lean 4 which it wasn't doing in lean 3. I think one can be closed with (F.obj k).cond but I'm not sure about the other one; it can't be hard though, if lean 3 was closing it automatically.

I think the only thing left with this PR is an erw which is generating two extra goals in lean 4 which it wasn't doing in lean 3. I think one can be closed with (F.obj k).cond but I'm not sure about the other one; it can't be hard though, if lean 3 was closing it automatically.

I got the file to build. The proof was hidden under two layers of definitions, so it was just a matter of unfolding the right stuff.

bors r+


I can't write interfaces in methods anymore

Expected behavior:
 interface ObjINF1 {
    [key: string]: string | number | undefined;
}
interface ObjINF2 {
    id: number;
    title: string;
}
interface ObjINF3 {
    parentId: number;
    name: string;
    desc: string
}
function a1(objArr: ObjINF1[]) {

}
function a2(objArr: ObjINF2[]) {
    a1(objArr)
}

Actual behavior:
function a2(objArr: ObjINF2[]) {
    a1(objArr) // Type 'ObjINF2' is not assignable to type 'ObjINF1'.Index signature is missing in type 'ObjINF2'.
}
// But it's true
function a3(objArr: {
    id: number;
    title: string;
}[]) {
    a1(objArr)
}

why?

It looks like this is a question rather than a bug report. This issue tracker is for tracking bugs and active work on TypeScript itself, rather than a general forum for programmers using TypeScript to get help or ask questions.
You can ask questions on sites like Stack Overflow. We are not able to provide one-on-one support on the issue tracker. Please read the issue template carefully - it has important information on what kinds of reports can be acted on here, as well as links to useful TypeScript resources. Thanks!
To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.


[WIP] Dev/test no build

Support Libraries Version (eg: 23.3.0):
Does this change any of the generated binding API's?
Describe your contribution

Already in use.


Add meta tags

Meta tag data shows up whenever someone shares a link on social media.

Hello @n4itik 👋,
To ensure our development process runs smoothly, we kindly request that you follow the workflow:
Issue Assignment 📝: Before you commence work on any issues, please make sure the issue is assigned to you. If it's a new issue, create one if it doesn't already exist.
Please create an issue first, and after you get assigned, you can start working on it.
Additionally, for future Pull Requests (PRs), please remember to follow the established process and avoid making direct PRs without a related issue. 🙅♂🚫
We appreciate your cooperation in adhering to these guidelines, as they help streamline our development efforts. 🙏
Thank you for your understanding and cooperation. If you have any questions or need further clarification, feel free to ask. 🤝


Docs: Administration - Starting and Stopping (Split PR #5830)

https://github.com/arangodb/arangodb/pull/5830/files

PR in new repo: https://github.com/arangodb/docs/pull/9


voc index always 500(0x 01F4) after several 0.

Hi,
We are using sgp40 with this algorithm, the calling procedure is like the example.
the problem is it ouputs 0x01F4, after about 1minute, and within the 1 minute, it outputs 0x0000
is it caused by drivers?
could this algorithm be used with sgp40 with its driver at (https://github.com/Sensirion/embedded-i2c-sgp40)? or must be used with sgp40 at (https://github.com/Sensirion/embedded-sgp)

we are using the diver at (https://github.com/Sensirion/embedded-i2c-sgp40)

the raw data is right, I think. as it is about 28000, and varies with alcohol.

Hi @mmz211
The algorithm can be used with the embedded-i2c-sgp40 driver and we recommend you to use this one and not the outdated embedded-sgp driver. The problem you see should not be related to the driver you use.
The gas index algorithm will output VOC 0 in the initial phase (first ~60s) to stabilize the raw signal and learn the average VOC index.  During the initial learning phase you should not create any events to allow the algorithm to estimate a proper baseline.
We also recommend that this learning phase happens in a stable environment with fresh air to get the best result.
Since SGP40 is a MOX (metal-oxid) sensor storage, handling and transportation can have a big influence on the initial state. The sensor will "clean" itself if you run it long enough. After longer storage you optimally run it for a couple of hours to get to a stable state.
The algorithm itself will also adapt to the sensor output if you run it long enough. E.g. if you use the default parameters it will eventually end up at an Index of ~100.
Of course you can adapt the parameters if you desire a different behavior. Please check out the documentation if you do so:
https://github.com/Sensirion/gas-index-algorithm/blob/master/sensirion_gas_index_algorithm/sensirion_gas_index_algorithm.h#L217
Can you also share what testing environment you are using and if you use the floating of fix-point version of the algorithm?

Hi, psachs
Thanks for your kindly explanation, things are more clear.
The test environment is our office and with windows.
Most concern is that, the implementation platform is a 16-bit mcu, renasas r5f100, have you have the information of this apect.
Best

Hi sorry for the late answer.
I just did some testing and the problem might be that using the float version of the algorithm does not work on all platform. There is aslo a fixed point version that is targeted for microcontrollers. Can you try and use this version? The interface should be the same, except for working with fixed point values instead of float.
https://github.com/Sensirion/gas-index-algorithm/tree/master/sensirion_gas_index_algorithm_fixpoint

We published an update that should solves an overflow issue on 8 and 16-bit platforms.
Please use Version 3.2.2 of the algorithm and re-open the ticket if you still encounter the issue


✨ Adding Ruby & Rails

I love making Homestead more versatile, but is there a way we can start making these things optional? Would be great if we could set a config variable.
Not sure if there are performance implications with having all of this stuff installed on HS.

Not sure if there are performance implications with having all of this stuff installed on HS.

The performance issues really come down to Postgres running if you're never going to use it.  By adding stuff to settler the only thing we're really impacting is box file size. (And the list of stuff we have to support)


feat: handle error messages for merge action

Description

Group the result of merge command into one standard

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Locally
Postman

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=0491c5e

/ok-to-test sha=71d2ac8

/ok-to-test sha=331c3ae


Input values: Nullable fields and defaults

Lets say we have a resolver with the input orderBy: Order = created, what should happen if we pass {"orderBy": null}?
Example code
Resolver
@strawberry.enum
class Order(Enum):
    ....

def resolver(
    order_by: Optional[Order] = Order.created,
) -> ...:
    if not hasattr(order_by, "value"):
        raise GraphQLError("orderBy is not valid")
    ...

Mutation
query doQuery($orderBy: Order) {
    resolve (orderBy: $orderBy){
        ...
  }
}

Expected cases:

orderBy is omitted: query with variables {} will use the default Order.created
orderBy is incorrect type: query with variables {"orderBy": 1} will return Variable '$order' got invalid value because order = 1 is not a valid type

But when querying with variables {"orderBy": null}, a third case happens: No error raised by graphql, no default value is set. order_by will be None in runtime, and in the example code raise GraphQLError("orderBy is not valid") will be called. Here I would expect case 2, because null is a value which is not of type Order.
I don't find this very well explained in the spec either https://spec.graphql.org/June2018/#sec-Null-Value

GraphQL supports distinguishing an explicit null from omission. For your use case - non-null with a default - it can be specified that way: order_by: Order = Order.created (no Optional). Then the usual validation will return the appropriate error.

@coady I tried your suggestion, but without success. Now the schema is orderBy: Order! = default while before it was orderBy: Order = default. Maybe you misunderstood my ticket.
Can you describe what would be expected if I send {"orderBy": null} while orderBy: Order = default? Shouldn't this result in incorrect type error on schema level?

Can you describe what would be expected if I send {"orderBy": null} while orderBy: Order = default? Shouldn't this result in incorrect type error on schema level?

! indicates the input is non-null:

orderBy: Order! = default will error if {"orderBy": null} is sent
orderBy: Order = default will allow it

@coady No error is raised (by strawberry) for {"orderBy": null}, as described in my issue description:

But when querying with variables {"orderBy": null}, a third case happens: No error raised by graphql, no default value is set. order_by will be None in runtime, and in the example code raise GraphQLError("orderBy is not valid") will be called.

@coady  so sending {"orderBy": null} to orderBy: Order = default, and in runtime the value being None is expected?
Wouldn't it make sense to throw incorrect type error here?

@joeydebreuk in your example I would expect the resolver to receive None because the value has been explicitly set to null by the client. It also matches the behaviour you would get with a plain Python function. i.e.:
def my_func(order_by = default):
	return order_by

assert my_func(order_by=None) is None

I understand how this works in plain Python, but personally I'd expect null not to be of valid type according to the schema. Don't the GraphQL specs describe how this case should be handled? I couldn't find it myself :thinking:

I think the spec does make it quite clear:
https://spec.graphql.org/June2018/#sec-Null-Value

{
  field(arg: null)
  field
}

The first has explictly provided null to the argument “arg”, while the second has implicitly not provided a value to the argument “arg”. These two forms may be interpreted differently.

By passing None when null is passed we can differentiate between the 2 different cases.

@jkimbo Thanks for your help. So if I understand correctly:

orderBy: Order = default means you can omit the value, in this case it will be defaulted
but will also allow null, in which case it will be None

And there is no way to make a distinction between these cases in the schema? So if I for example would want to disallow null, but omitting is allowed, I would have to handle this in my resolver?
eg imagine I have a resolver to update instance in DB, it has a lot of optional fields, fields that shouldn't be updated can be omitted. Lets say name column in DB only allows str not None, I'd have to handle it like:
def update_instance(
    id: ...,
    name: Optional[str] = UNSET,
    some_other_fields: Optional[str] = UNSET,
    # a bunch of other fields
) -> ...:
    if name is None:
        raise GraphQLError("name can not be null")

Yep thats correct. As far as I'm aware there is no way to disallow null but allow omitting in the schema alone. You would have to do the checks in the resolver.
Related: I would consider that any field that has lots of optional fields should probably be split out into multiple fields. To make full use of the benefits of the GraphQL typing it's beneficial to be very specific with your fields and types.

Thanks a lot @jkimbo

And there is no way to make a distinction between these cases in the schema? So if I for example would want to disallow null, but omitting is allowed, I would have to handle this in my resolver?

It is allowed (just poorly documented). Having a default value also makes the input optional, regardless of whether the type is nullable.

orderBy: Order! = default: doesn't allow nulls, sends default if omitted
orderBy: Order = default: allows nulls, and sends default if omitted

Oh yeah that looks like it should work @coady in which case this is a bug in Strawberry.

Oh yeah that looks like it should work @coady in which case this is a bug in Strawberry.

There's no bug that I'm aware of. It does work in strawberry:

strawberry
graphql
description

order_by: Order = default
orderBy: Order! = default
doesn't allow nulls, sends default if omitted

order_by: Optional[Order] = default
orderBy: Order = default
allows nulls, and sends default if omitted

@joeydebreuk can verify that the options @coady has outlined work for you?

Yes. Now I realize where I got mixed up.
I was doing
@query("test")
@strawberry.field
def test_query(
    choice: Order = Order.startsAtDesc,
    optional_choice: Optional[Order] = Order.startsAtDesc,
) -> bool:
    print(f"{choice.value=}")
    print(f"{optional_choice.value=}")
    return True

This runs fine, default work, but schema looks like
choice: Order!
optionalChoice: Order

If I do
@query("test")
@strawberry.field
def test_query(
    choice: Order = Order.startsAtDesc.value,
    optional_choice: Optional[Order] = Order.startsAtDesc.value,
) -> bool:
    print(f"{choice.value=}")
    print(f"{optional_choice.value=}")
    return True

schema looks like
choice: Order! = startsAtDesc
optionalChoice: Order = startsAtDesc

And everything works as expected.


Update psycopg version

Should I use a separate branch for updates? Or combine with bugfixes branch?

Having it separate allows to see if it breaks the CI. If you perform multiple changes, it won't be obvious which one breaks it.

Okay


[Bug] on updating the name of JS object the expected output does not get displayed on the widget dynamically

Steps to reproduce:

Add a Js object
add a widget
Bind the Js object to the widget
Navigate to Js object change the name
navigate to widget property pane
and observe

Observation:
it is observed that the name is updated however the execution has failed. However, it is observed that on refresh the data appears
Expectation:
It is expected the result and the name of the application should get updated dynamically
Video:

is name not getting updated or the values are not shown? @prapullac

@ApekshaBhosale  the name gets updated the value does not get displayed.

Got it! I fixed this will deploy soon!

@ApekshaBhosale
Here we need to observe two things

If a JS function1  is called inside the JS function2 and the name of the JS function1 is changed. The name of JS function1 inside the JS function 2 does not change
When the same JS function 1 is binded inside the widget the name gets updated however the value does not show up

@nidhi-nair Did we handle the first case?

Closing the issue as it is working as expected


JCSMP properties providers for new SolaceIO write connector

This adds a base class and two providers for the new SolaceIO write connector. The basic authentication provider just uses a username and password.
Users can write their own providers to set authentication mechanisms and other session properties, by extending from the base class. As an example, we provide a GoogleCloudSecretProvider, to show how to create your own. This provider can also be used "as is", but it is mainly meant as an example to implement your own.
In upcoming PRs, I will be submitting the rest of the write connector. It is thousands of lines of code, so I am splitting in smaller PRs, to facilitate code reviews.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

assign set of reviewers


[SPARK-39879][SQL][TESTS] Reduce local-cluster maximum memory size in BroadcastJoinSuite* and HiveSparkSubmitSuite

What changes were proposed in this pull request?
This pr change local-cluster[2, 1, 1024] in BroadcastJoinSuite* and HiveSparkSubmitSuite to local-cluster[2, 1, 512] to reduce test maximum memory usage.
Why are the changes needed?
Reduce the maximum memory usage of test cases.
Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
Should monitor CI

Merged to master, branch-3.3, branch-3.2, branch-3.1 and branch-3.0.


Don't require full Keystone creds from relation

The charm actually only cares about the auth API URL but because there's not a relation for just that from Keystone, it instead uses the relation for requesting a new user (keystone-credentials). The interface layer does provide a flag for the case where just the API endpoint info is available, so it's better to use that instead of blocking on the full credentials being available.
This fixes part of lp:1834164 where the integrator charm might not have credentials in the format required by the relation but can still at least provide the API endpoint info.

For reference, the keystone-credentials.available flag is set here based on this set of data being available.


waagent ovf-env.xml file missing after 'waagent -deprovision+user -force'

Description
Outline the issue here:
I prepare VHD-image of my VM.
After running 'waagent -deprovision+user -force' the file /var/lib/waagent/ovf-env.xml is deleted and is not recreated.
When I try to create VM from VHD-image VMAccessForLinux fails in creating new user.
I was able to get the disk of this VM, mount it to running VM and look at /var/log/waagent.log file - it throws an error of missing '/var/lib/waagent/ovf-env.xml' file.
How to fix it?
Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
CLI
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
root@Alexey-HP:/root# az --version | head -1
azure-cli (2.0.10)
OS Version: What OS and version are you using?
Answer here:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:
Bash on Windows

This is not a CLI issue really, but did you follow the steps mentioned in the document

yes, of course I did - pls. see description of the issue

@alexeyshishkin01 We didn't own waagent. Here's the repository you can open issue for this tool: https://github.com/Azure/WALinuxAgent. Thanks.

ok


fix: cursor pointer issue

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[x] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.
[x] I have added necessary documentation (if appropriate)

Linked Issues
Fixes #263
Description
Cursor is changed from arrow to pointer at the required places.
❤Thank you!
Post merge checklist

[x] Follow steps from the guidelines for contributing to this repository.
[x] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@Anish-Sarawgi the issue in still there in this button, fix this.

@120EE0692 I have made the required changes. Please review it once.


Formatter undocumented deviation: multi assignment wrapping

Black formatting
def from_user_altitude_range_to_px4_altitude_range(
    altitude_range: Tuple[float, float],
) -> Tuple[int, int]:
    user_minimal_coordinate, user_maximal_coordinate = (0.0, 0.0, altitude_range[0]), (
        0.0,
        0.0,
        altitude_range[1],
    )

Ruff formatting
def from_user_altitude_range_to_px4_altitude_range(
    altitude_range: Tuple[float, float],
) -> Tuple[int, int]:
    user_minimal_coordinate, user_maximal_coordinate = (
        (0.0, 0.0, altitude_range[0]),
        (
            0.0,
            0.0,
            altitude_range[1],
        ),
    )

Use Ruff 0.0.289 with line length 100.

For what it's worth, I think the Ruff formatting is more readable in this example.

I am reporting all deviations I come across.

Thanks @JonathanPlasse! That’s great and the intended workflow. We’ll collect undocumented deviations, then make decisions on whether to address them or not.

Thanks for reporting this deviation. This is an intentional deviation that I'm open to discussing and that we forgot to document.
Ruff parenthesizes tuples except in a few places, whereas Black strips the parentheses in many places.
# Black
def from_user_altitude_range_to_px4_altitude_range():
    user_minimal_coordinate, user_maximal_coordinate = (0.0, 0.0, altitude_range[0]), (
        0.0,
        0.0,
        altitude_range[1],
    )

    (0.0, 0.0, altitude_range[0]), (
        0.0,
        0.0,
        altitude_range[1],
    )

    assertEquals(0.0, 0.0, altitude_range[0]),

# Ruff
def from_user_altitude_range_to_px4_altitude_range():
    user_minimal_coordinate, user_maximal_coordinate = (
        (0.0, 0.0, altitude_range[0]),
        (
            0.0,
            0.0,
            altitude_range[1],
        ),
    )

    (
        (0.0, 0.0, altitude_range[0]),
        (
            0.0,
            0.0,
            altitude_range[1],
        ),
    )

    (assertEquals(0.0, 0.0, altitude_range[0]),)

Our reasoning behind requiring the parentheses it otherwise can be very hard to spot that it is a tuple. For example, would you have noticed that the assertEquals(0.0, 0.0, altitude_range[0]), is a "useless" tuple? I did not and neither did some contributors to the django project https://github.com/django/django/pull/17181. That's why I propose keeping Ruff's formatting but I'm interested in getting more feedback on this (ideally from other projects trying ruff, are there places where this formatting looks worse?)


Subtitle encoding detection fail

Hello,
subliminal converting subtitles to UTF-8 and for some players not a good idea. For example XBMC using user interface language for determine subtitles language. In my case my XBMC is Turkish and my subtitles downloaded from subliminal showing wrong characters.
Debug of subliminal: http://pastebin.com/raw.php?i=FDKCxZzw
I download same subtitle. This is compare of subliminal vs. opensubtitles web download:
$ charade downloaded_by_subliminal.srt downloaded_from_opensubtitles_website.srt
downloaded_by_subliminal.srt: utf-8 with confidence 0.99
downloaded_from_opensubtitles_website.srt: ISO-8859-2 with confidence 0.874910791543
$

I am going to paste sneak peek of this two subtitles. You can see differences:
http://pastebin.com/raw.php?i=5bE7YZJJ

Hi, i have the same problems, with hungarian lang..

Same problem with croatian language. Croatian subtitles are always CP1250 no matter where they get downloaded from so I don't see a reason for subliminal to recode anything. My media player doesn't support UTF-8 anyway.

same problem in french :/

Please provide examples.

serie :
true.detective.s02e03.720p.hdtv.x264-0sec.mkv
log:
INFO: Listing subtitles with provider 'opensubtitles' for video <Episode [u'true detective', 2x3]> with languages set([<Language [fr]>])
INFO: Found 1 subtitle(s) on opensubtitles
INFO: Listing subtitles with provider 'thesubdb' for video <Episode [u'true detective', 2x3]> with languages set([<Language [fr]>])
INFO: Found 1 subtitle(s) on thesubdb
INFO: Listing subtitles with provider 'podnapisi' for video <Episode [u'true detective', 2x3]> with languages set([<Language [fr]>])
INFO: Found 3 subtitle(s) on podnapisi
INFO: Listing subtitles with provider 'addic7ed' for video <Episode [u'true detective', 2x3]> with languages set([<Language [fr]>])
INFO: Found 5 subtitle(s) on addic7ed
INFO: Listing subtitles with provider 'tvsubtitles' for video <Episode [u'true detective', 2x3]> with languages set([<Language [fr]>])
INFO: Found 0 subtitle(s) on tvsubtitles
INFO: Downloading subtitle <OpenSubtitlesSubtitle [fr]> with score 46 into u'/mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt'
1 subtitle downloaded
contenu :
2
00:01:50,580 --> 00:01:52,165
Est une rivičre
19
00:03:11,286 --> 00:03:12,621
Je suis lŕ.
60
00:06:02,862 --> 00:06:04,543
Deux côtes fęlées.
68
00:06:22,936 --> 00:06:24,730
Burris est ŕ l'intérieur.

chardet /mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt
/mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt: utf-8 (confidence: 0.99)
charade /mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt
/mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt: utf-8 with confidence 0.99
file -bi  /mnt/pchome-mydatas/series/true.detective.s02e03.720p.hdtv.x264-0sec.fr.srt
text/plain; charset=utf-8

Why is subliminal not always just using chardet's encoding? I'm having a problem where it thinks Greek characters decode cleanly with latin-1, where chardet is properly returning Greek.
What's the reason between the complicated encoding detection scheme, over just trusting whatever chardet thinks (which is correct pretty much all of the time, in my experience)?

Subliminal doesn't use any encoding detection by default. It is only triggered when using the -e argument of the CLI.
In the previous versions, subliminal used the detected encoding to decode the subtitle and write it on the filesystem using utf-8. Due to many bug reports without the required information to make the detection algorightm better I decided to deactivate it by default and leave encoding detection to media players.

Sorry, that's what I mean. I use -e UTF8 but I get invalid subtitle encodings (Latin1 encoded to UTF8, so everything looks broken). Overriding the built-in detection with just return chardet.detect(self.content)["encoding"] works every time.
Is there a reason for the convoluted encoding detection that only uses chardet if it fails, over just always using chardet when -e is specified?

I just explained the reason. I don't have enough data to fix encoding for every languages. This code was introduced because chardet wasn't accurate enough and resulted in a lot of garbage for most user. I'm glad chardet works fine in your language but that doesn't help at all.
For that part to be improved I need at least one test case per language per (popular) encoding (for that language), then I will decide how to do to improve that part, most likely it will be a mix of chardet + a way to supply chardet with language information (see https://github.com/chardet/chardet/issues/19#issuecomment-33596664). I will likely use chardet to decide between a limited, language-based set of possible encodings.

Hmm, I see. It's odd that chardet wasn't accurate enough, it's always worked properly for me.
This is the subtitle file that's not working for me, by the way:
http://www.opensubtitles.org/en/subtitles/4910656/total-recall-el

I just created #528, if you want to contribute more test cases please provide the file encoding and the subtitle file.

Will do, I'll add them as they find them.

I also have a problem with subtitles downloaded from NapiProjekt. When I open the file in text editor, it shows UTF-8 encoding, but polish characters are displayed incorrectly. What can I do to help ?

My problem is actually in SickRage, just noticed they added such line recently, and this probably breaks it, as it was working before:
if subtitle.language.alpha3 == 'pol':
setattr(subtitle, 'encoding', 'utf-8')
So the subtitles downloaded by subliminal are in windows-1250, but for unknown reasone SickRage mark them (not convert) as utf-8, which is not working.

SickRage uses a custom version of subliminal, any issue related to SickRage must be reported there.


Potential third mode: mixed

I was thinking how neat it would be if you could have a third brute mode (mixed?) that combined the dns and directory brute. Just a thought but something like you pass a main top level domain, dns wordlist, and a web dir/file list. Then as gobuster discovers subdomains it kicks off a web dir brute, maybe after a quick check for port 80/443. I could have a go at working up a pull request for this if you like...

Thanks for the suggestion @johnnyDEP, but the answer is an emphatic "no" :)
I'm not keen on this because:

This invokes a spray and pray attitude, which isn't really the way I do assessments.
It involves the concern of filtering results, or compartmentalising them, which totally ruins the concurrency aspect.
It would rely on the addition of a pipeline of events that would be painful to tie together.

There are other reasons that are more opinion than fact, so I'll keep them to myself. But in short, I don't really think I would like gobuster to head in this direction.
I do appreciate the suggestion though.
Cheers!
OJ


[Feature Request] Include "Expert Picture Settings" if possible

Not sure how Roku implements the "Expert Picture Settings" in their application, but it would be a nice feature to include if it isn't proprietary or too difficult.

Hi @digital-mystik, unfortunately, Roku doesn't offer a way to mimic the "Expert Picture Settings" via their SDK. Therefore, I won't be able to implement this feature.


chore(release): v0.10.1 🎉

:robot: I have created a release beep boop
0.10.1 (2024-08-03)
Bug Fixes

views: gen hydrated view without "as" label to prevent infidiff (f4307d2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/sql-dao-generator/releases/tag/v0.10.1 :sunflower:


GUI-app Support folder code batch conversion

Add Convert button IsEnabled property control in ViewModel
Encapsulation  Dispatcher.CurrentDispatcher.Invoke() function in ShellViewModel

Third-party-packages

FolderBrowserForWPF

Thanks! This looks pretty good, merging. I might change how you're doing warnings/errors in the C# output pane later but that works for now.


[question] - Acorn AST tree integration

Since rollup uses the Acorn AST tree, wouldn't be somewhat trivial to wire directly the output of the rollup bundle with butternut? This will make the overall process even faster.
Does this makes sense?

Not quite. Rollup changes source string not ast. It's fast because of lack of code generation. Same with butternut. It's still faster without code generation.

Hey @diervo we're going to close this one. We're getting ready to move this plugin to the monorepo and are tying off loose ends. Please feel free to open a new issue at rollup/plugins.


Compatibility with Redactor and ethercreative/seo

It seems that the asset usage is not tracked in the wysiwyg (redactor plugin of craft cms) and in the ethercreative/seo for social image for facebook and twitter.
When you add an image in the redactor or in the social media, the image stays as "Unused" in the asset list.
If you delete the image, it remove the social image in the seo plugin and break the image in the redactor plugin...
craftcms: 3.8.5
redactor: 2.10.12
ethercreative/seo : 3.7.4

Unfortunately it would cause huge queries to support such fields, which would make asset overviews useless performance wise. It is documented in the readme. The only work around would be to cache the results of a background task that indexes all uses of each asset.

And for the work around, it's something we should do on our side...
Not sure to understand well.

I was thinking about forking and building this, starting with Redactor. Was going to have a migration to store relations that aren't in the relations table, have it run a job to index all redactor fields on install, then update it whenever an element is saved. Also adding a utility to re-index if necessary. Curious if you've gotten a chance to work on this enhancement yet!

Update: i did manage to fix this for CKEditor in Craft 5. I'll look into ways to fix this also for the SEO plugin.

Release 4.1.2 has support for the SEO plugin and CKEditor.


quick ixmonad and examples

I meant to get back to you earlier about this. I think developments like this are great, but I've been wondering if they should be split into separate libraries. What do you think of making coq-el-indexed (we can put it in this organization) and release it as a separate package?

That makes sense, although this would be a pretty small package, the only instances I'm aware of are state and cont.
It's completely reasonable to close this until someone has time/interest to actually get a complete implementation done.

It wouldn't be as small as some node.js packages. :-)
What is left for a "complete implementation*?

It's certainly usable as is, so maybe nothing needs to be added

@gmalecha Should we merge this PR?

I don't have any real technical objections to merging this, but I think the question is whether ExtLib should grow and/or shrink. Does it make sense to release separate packages with add-on functionality like indexed monads? What needs to be in the core?

It'll make sense to release a separate package if no future code in ExtLib would depend on such add-ons.
I'd prefer having ExtLib as a growing and shrinking library where the community can contribute functionalities they find generically useful and should not redefine everywhere. When some code were adopted by Coq standard library, we should remove them from here.
Some functionalities could come in different styles (e.g. monad notations), and the Coq team might have difficulty deciding which one to include in standard library. In this case, ExtLib can host one or many of them, allowing users to choose.


Synthesis failed for Google.Cloud.OsLogin.V1Beta

Hello! Autosynth couldn't regenerate Google.Cloud.OsLogin.V1Beta. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.OsLogin.V1Beta API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 22:44:59,518 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/Google.Cloud.OsLogin.V1Beta
2021-03-19 22:45:00,002 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-03-19 22:45:00,006 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-03-19 22:45:00,010 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2021-03-19 22:45:00,013 autosynth [DEBUG] > Running: git config push.default simple
2021-03-19 22:45:00,017 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.OsLogin.V1Beta
2021-03-19 22:45:00,021 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.OsLogin.V1Beta
Switched to branch 'autosynth-Google.Cloud.OsLogin.V1Beta'
2021-03-19 22:45:00,305 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-03-19 22:45:00,312 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-03-19 22:45:00,316 autosynth [DEBUG] > Running: git remote get-url origin
2021-03-19 22:45:00,351 synthtool [ERROR] > Failed executing git checkout master:

error: Your local changes to the following files would be overwritten by checkout:
	google/cloud/dialogflow/v2/answer_record.proto
	google/cloud/dialogflow/v2/conversation.proto
	google/cloud/dialogflow/v2/conversation_profile.proto
	google/cloud/dialogflow/v2/participant.proto
Please commit your changes or stash them before you switch branches.
Aborting

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 312, in _inner_main
    git_source.enumerate_versions(sources, pathlib.Path(temp_dir))
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 202, in enumerate_versions
    source_versions = enumerate_versions_for_source(git_source, temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 166, in enumerate_versions_for_source
    local_repo_dir = str(synthtool_git.clone(remote))
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 85, in clone
    shell.run(["git", "checkout", "master"], cwd=str(dest), check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'checkout', 'master']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Doesn't intercept keyboard/mouse activity when running in Flatpak/Wayland

I'm not sure what exactly causes it, but I use wayland and flatpak, which both aim to isolate the app. Wayland probably does more to isolate discord when it's running than flatpak.
Behavior:
When I'm interacting IN DISCORD, the WayAFK plugin works as expected. But if I'm not clicking/tying in the discord window, then WayAFK thinks I'm AFK.

I may be misunderstanding, but it sounds like it's working as designed. This plugin is a hack:

On startup, WayAFK subscribes to the keydown and mousedown events. Whenever you press a key or use your mouse inside the Discord window, a timer will be reset.

It can't break Wayland or Flatpak's isolation, unfortunately.

Oh I see, I missed that. I'll close

FWIW, if you're immediately going AFK when not typing/clicking, check the plugin settings and make sure the timeout didn't somehow wind up zeroed.


Add prabhusabapathi's files

Add first file
Add second file
Add md file

It is good to see you perform

Merge prabhusabapathi's files


Removed negative numbering

#79
Removed negative numbering from
1.Number of colours
2.Time interval
3.Countdown timer

@ananya-dhiman once checkout #22

Sorry I missed that issue. I have now updated the code such that the user is restricted from typing the negative bar from keyboard along with the min. I have tested and the code runs successfully. Not sure whether this is a necessary change but please check.

@ananya-dhiman
it's working but it would be great if you allow float inputs for time interval (input number 2).

Ok will try to work on that, the rest don't require floats right?

I have updated the code so that it allows decimal values. However it works in such a way that the user needs to type the whole number first and then add the decimal point.For values less than 0 point is added before the number after uits typed. 0 cannot be entered but that isnt hampering the final output as its considering blank as 0. I think it can be added in the blue line below just to remove confusion and as negative part isnt needed.


Mount the internal tls without the subpath

Please mount the internal tls without the subpath to avoid the following problem.
  Normal   Scheduled    10m                  default-scheduler  Successfully assigned cluster-sample-ns/harborcluster-sample-harbor-harbor-core-79f4585c5d-2lv8l to kind-control-plane
  Warning  FailedMount  10m (x3 over 10m)    kubelet            MountVolume.SetUp failed for volume "token-service-private-key" : secret "harborcluster-sample-harbor-harbor-core-tokencert" not found
  Warning  FailedMount  10m                  kubelet            MountVolume.SetUp failed for volume "ca-download" : failed to sync secret cache: timed out waiting for the condition
  Warning  FailedMount  10m                  kubelet            MountVolume.SetUp failed for volume "configuration" : failed to sync configmap cache: timed out waiting for the condition
  Normal   Pulling      10m                  kubelet            Pulling image "quay.io/goharbor/harbor-core:v2.1.2"
  Normal   Pulled       10m                  kubelet            Successfully pulled image "quay.io/goharbor/harbor-core:v2.1.2"
  Normal   Started      10m                  kubelet            Started container core
  Warning  Unhealthy    10m                  kubelet            Readiness probe failed: Get https://<IP_ADDRESS>:8443/api/v2.0/ping: dial tcp <IP_ADDRESS>:8443: connect: connection refused
  Normal   Created      9m33s (x4 over 10m)  kubelet            Created container core
  Normal   Pulled       9m33s (x3 over 10m)  kubelet            Container image "quay.io/goharbor/harbor-core:v2.1.2" already present on machine
  Warning  Failed       9m33s (x3 over 10m)  kubelet            Error: failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting "/var/lib/kubelet/pods/274a0e2e-4e7f-4f95-a832-cf18e36f038d/volume-subpaths/internal-certificates/core/5" to rootfs at "/run/containerd/io.containerd.runtime.v2.task/k8s.io/core/rootfs/harbor_cust_cert/ca.crt" caused: no such file or directory: unknown
  Warning  BackOff      43s (x50 over 10m)   kubelet            Back-off restarting failed container

Closed as internal TLS secret is in the dependencies of the component custom resource.


Graduate ServerSideFieldValidation to Beta

Upstream: kubernetes/kubernetes#108889

@tengqm I see https://github.com/kubernetes/website/pull/32357 is also opened up for the same purpose but @kevindelgado hasn't made any changes there.
So, I would like to keep this PR open and consider closing https://github.com/kubernetes/website/pull/32357. Please correct me if I am wrong, thanks!

@mehabhalodiya

#32593 is targeting 'main' branch, fixing the problem that the gate appeared but not documented.
This PR is targeting 'dev-1.24' branch, updating the changes to the gate in 1.24

Add ServerSideFieldValidation feature #32593 is targeting 'main' branch, fixing the problem that the gate appeared but not documented.
This PR is targeting 'dev-1.24' branch, updating the changes to the gate in 1.24

Thanks for clearing. I missed noticing that! Apologize!
@tengqm But what about closing #32357?

/hold
I'd like the feature gate page pointing to the docs to be added by @kevindelgado
Waiting for #32357 to be merged.

Looks like ServerSideFieldValidation to Beta will not be in v1.24 and will target v1.25
See https://github.com/kubernetes/website/pull/32357#issuecomment-1089020163
/close

/milestone clear


GetClosestMatchProperty makes deserialization of backingfield with getter fail

Hi
The following test shows what might be a bug:
[TestFixture]
public class FallbackToCaseInsensitiveFailsForThisCaseTest
{
    [Test]
    public void CanSerializerAndDeserializeToAndFromFieldWithGetterOfOtherType()
    {
        var serializer = new JsonSerializer()
        {
            ContractResolver = new CR(),
            TypeNameHandling = TypeNameHandling.All
        };

        var stringBuilder = new StringBuilder();
        var textWriter = new StringWriter(stringBuilder);
        serializer.Serialize(textWriter, new SomethingWithAList());

        var stringReader = new StringReader(textWriter.ToString());
        var jsonTextReader = new JsonTextReader(stringReader);
        serializer.Deserialize<SomethingWithAList>(jsonTextReader);
    }

    public class CR : DefaultContractResolver
    {
        public CR()
            : base(true)
        {
            DefaultMembersSearchFlags = BindingFlags.Instance | BindingFlags.NonPublic | BindingFlags.Public;
        }
    }

    public class SomethingWithAList
    {
        readonly List<int> ints = new List<int>();
        public IEnumerable<int> Ints
        {
            get { return ints.Where(x => x > 10); }
        }
    }
}

Would it be possible to make an option to disable the case insensitive property name match?
Regards, Asger

@asgerhallas did you implement your own contract resolver? (I need case sensitive deserialization)


Guacamole redirect URL needs adding to the app registration.

Describe the bug
When deploy Guacamole workspace service cannot log on as the redirect URL is not on the app registration.
Steps to reproduce

Deploy guacamole workspace service
Visit connection_uri

Note: we should consider passing existing tokens to avoid the login loop, or using using the same redirect URL for all oidc services.

One of these should be marked as duplicates:
https://github.com/microsoft/AzureTRE/issues/1352
its about getting the redirect url automatically ...

Duplicate of #1352


[FLINK-34111][bugfix][table] Fix CompactCoordinator data loss upon termination

CompactCoordinator accumulates data in currentInputFiles and only rolls them into inputFiles in snapshotState(). At the same time it relies on separately receiving checkpoint indications from the upstream operator via processElement() (EndCheckpoint). If the job terminates, the final EndCheckpoint can arrive before the snapshotState() gets called. This leads to data loss (all events in currentInputFiles get discarded).

@JingsongLi could you please take a look?

@afedulov You already got me excited that you implemented https://issues.apache.org/jira/browse/FLINK-34111 but I think you've linked the wrong Jira ;)

Haha, indeed. Thanks, fixed.

@flinkbot run azure

@flinkbot run azure


Add 'SaveInheritanceMode.None'

This will allow you to disable inheritance on the absolute latest version without ABSave seeing it as an invalid version

Issue #49 solves this problem.


Re-run handlers cli option

Proposal: Re-run handlers option
Author: René Moser <@resmo>
Date: 2016/03/07

Status: New
Proposal type: core design
Targeted Release: 2.2
Associated PR: N/A
Estimated time to implement: N/A

Motivation
One of the most annoying thing users face using ansible in production is running handlers manually after a task failed or the run was aborted by CTRL-C.
Problems
Handler notifications get lost after a task failed and there is no help from ansible to catch up the notified handlers in a next ansible playbook run.
- hosts: localhost
  gather_facts: no
  tasks:
    - name: simple task
      shell: echo foo
      notify: get msg out

    - name: this tasks fails
      fail: msg="something went wrong"

  handlers:
    - name: get msg out
      shell: echo handler run

Result:
$ ansible-playbook test.yml

PLAY ***************************************************************************

TASK [simple task] *************************************************************
changed: [localhost]

TASK [this tasks fails] ********************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "something went wrong"}

NO MORE HOSTS LEFT *************************************************************

RUNNING HANDLER [get msg out] **************************************************
	to retry, use: --limit @test.retry

PLAY RECAP *********************************************************************
localhost                  : ok=1    changed=1    unreachable=0    failed=1

Solution proposal
Similar to retry, ansible should provide a way to manully invoke a list of handlers additionaly to the notified handlers in the plays:
 $ ansible-playbook test.yml --notify-handlers <handler>,<handler>,<handler>
 $ ansible-playbook test.yml --notify-handlers @test.handlers

Example:
 $ ansible-playbook test.yml --notify-handlers "get msg out"

The stdout of a failed play should provide an example how to run notified handlers in the next run:
...
RUNNING HANDLER [get msg out] **************************************************
	to retry, use: --limit @test.retry --notify-handlers @test.handlers

obsolete by reworked proposal #11

Discussed this in public core meeting, came to a 'expanded proposal':

add command line options and 'unhanded notified handlers' information to .retry files
new --retry option that will:

use the .retry file to rerun the play for those hosts with same options
fire unhanded handlers, even if they are not notified during rerun

There are still limitations as this does not cover 'all cases', but should be able to recover/retry for most plays. For example, handlers that use data from other hosts or tasks that depend on 'changed' status of tasks that do not change on the retry will still be a problem.


Add HTTP proxy support

Added proxy support to current code from work in previous pull request https://github.com/heroku/databasedotcom/pull/86
I also updated the readme to reflect the added configuration possible.

This feature was added in https://github.com/heroku/databasedotcom/pull/154. This should be closed

Any updates on this?

What is blocking this from getting merged? If there is additional work needed I'd be happy to help out. If the feature is unwanted, please say so; I'm trying to avoid having to fork this, but proxy support is required for us to deploy.

@hooptie45 This is the main reason: https://github.com/heroku/databasedotcom/pull/188


Clean up disk.

Following the suggestion from different threads I've found on github.

Is this to solve an issue with running out of disk space?

@leighmcculloch yep, it's an attempt to fix the out of disk space issue. Unfortunately I couldn't find any other way.


Added blur effect to the background image of the hero section on Path…

…spare website

Issues Identification
Closes: #(issue number)
Description
Summary
A brief description of what this pull request does and why it is needed.
Details
Include any detailed information about the changes in this pull request.
Types of Changes
Please check the boxes that apply

[ ] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] My changes do not break the current system and pass all existing test cases
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Screenshots
If applicable, please attach screenshots of the changes made to the user interface.
Additional Information
Please provide any other information that is relevant to this pull request.

resolve conflicts and also where is the issue number the template was given for  a reason

resolve conflicts please

create a new pr closing this one

Create a new pr closing this one

sir, I give the new pr  please check that and this   time I merged all the changes by upstream in my fork repository so please review that sir and if there any problem please guide me than


Crash on client startup 1.18.2

Forge: 40.2.0
After installing the mod, the assembly stopped running.
Going through the mods, I found out that the combined presence of mods such as Patchouli, Create and Architectury causes a crash. You can also add REIPluginCompatibilities to the list.
Checked on different versions of Forge.

crash-2023-03-11_19.29.06-fml.txt
latest.log

The logs you provided claim that Refined Storage Addons is the cause of this crash

I do not know how it works, but the assembly started without removing or replacing mods. On your recommendation, I will delete the file. Refined Storage Addons was installed due to an optional dependency of Universal Grid. Thanks for the answer. Until I close the topic.


Modification to the Breaking Changes language

Preposing we modify the breaking changes wording to allow an issue to be opened first and maintainers notified that this is incoming. Also allows guidance from the community on the type of breaking change we would be willing to take before any work is done.  Also linked @kwirkykat as it was bugging me that it didn't auto link... :grin:

:+1:


Program for Print Your Name

Name - Vishal Arunagiri .
Community - GDSC-RAIT , RAIT ACM .

Choosed right question !! Good


Create "madlib" system

Have the bot fill in a mad lib template based on a subject.

Old idea that isn't really relevant to the current version of the bot.


Index generation from local in upload period

This is a cloned version of https://github.com/Commonjava/mrrc-uploader/pull/45 to fix some merging conflicts and some pylint problems

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

177 of 185 (95.68%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.2%) to 84.851%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mrrc/pkgs/indexing.py
146
154
94.81%

Totals

Change from base Build<PHONE_NUMBER>:
2.2%

Covered Lines:
913

Relevant Lines:
1076

💛  - Coveralls


The performance gap of prd2(250M) and r2d2(250M) checkpoints？This paper only compared the ablation results of 2.3M.

Limited by computing resources, I did not conduct ablation experiments on 250M data. But I think the performance gap of prd2 and r2d2 will be close to 2.3M


Add quick fix for avoid_function_literals_in_foreach_calls

The fix should convert the forEach invocation to a for loop, using the closure's parameter name as the loop variable.

https://dart-review.googlesource.com/c/sdk/+/198560


Sprint Planning over project in GitHub

In order to plan sprints and track the progress of our tickets with the current sprint, we need to setup a planning system. We can use the GitHub projects feature.
Acceptance criteria

[x] The project board only shows tickets that are within the current sprint
[x] The project's title contains the start and end date of the sprint.
[x] The project board contains the different states of the tickets:

[x] To do
[x] In progress
[x] Code review (Must be automated with a workflow)
[x] Ready for acceptance (Must be automated with a workflow)
[x] Ready on acceptance
[x] Ready for production
[x] Ready on production (Ticket is deployed to production and can be reviewed by the product owner)
[x] Done
[x] Released (In order to prevent tickets piling up in the board, we need to release tickets and filter them out from the overview)

Instead of using the status: Released, we could use the Iteration feature: https://github.blog/changelog/2021-10-14-the-new-github-issues-10-14-update/

I've also added a different view called Personal Board that only shows tickets assigned to you. This way you can focus on your work and keep track of it more easily.


camera should rotate around center of bounding box

Fixes #16

@jsoules
The main problem was that the bounding box was not being defined correctly.
A secondary problem arose after correcting the bounding box: the directional and spot lights did not behave as intended when the object was not positioned at the origin. It was difficult to figure out how to fix the issue, so for now I am just using a simple PointLight attached to the camera. Seems fine for now.

I'll look at the code changes too, but I've been playing with this with a number of different views and I'm not actually sure I see any difference?

I'll look at the code changes too, but I've been playing with this with a number of different views and I'm not actually sure I see any difference?

Do you mean the lighting?
I was noticing a shadow for certain angles for the miniwasp surface example:
https://figurl.org/f?v=gs://figurl/volumeview-2&d=747778076c92df4ac817870f6f2ff6864f768962&channel=flatiron1&label=miniwasp_surface_example1


Better handling of overflows of System.Int32 in the REPL

This user experience cannot really be called great. We should think about some more reasonable semantics here.
$ perlang
Perlang Interactive REPL Console (0.1.0+ea4f649)
> 15 * 1024 * 1024 * 1024
-1073741824
> 16 * 1024 * 1024 * 1024
0

Come to think of it, this is not just with the REPL; it's the same with overflows in literal initializers to explicitly typed var statements as well:
> var a: int = 1 * 1024 * 1024 * 1024; print a;
1073741824
> var a: int = 2 * 1024 * 1024 * 1024; print a;
-2147483648
> var a: int = 3 * 1024 * 1024 * 1024; print a;
-1073741824
> var a: int = 4 * 1024 * 1024 * 1024; print a;
0

I don't think this is really good. C# gives you "Overflow in constant value computation" for example 2-4 above. That's a much better and nicer experience for the end user.

For reference, the semantics described above is the same with Java (version 11 tested below). Given this, it cannot be that terrible. :sunglasses:
$ jshell
|  Welcome to JShell -- Version 11.0.11
|  For an introduction type: /help intro

jshell> 15 * 1024 * 1024 * 1024
$1 ==> -1073741824

jshell> 16 * 1024 * 1024 * 1024
$2 ==> 0

I think this is actually fine for now. The C#/Java semantics are reasonable in this case (= allow overflow by default), since the alternative would have a extremely significant performance impact.
We might want to add some checked keyword at some point, but that deserves an issue of its own in that case.


Updated Launcher command in Readme

Added new var to launcher in compose

If you want to test this, you also need to change the docker compose to use the read-metadata-from-schema branch of the survey launcher. i.e.
go-launch-a-survey:
    image: onsdigital/go-launch-a-survey:read-metadata-from-schema