TypeError: Cannot read property 'type' of undefined

Hi all,
I follows step in README.md when i run yarn deploy:db I faced this error
~/w/este > yarn deploy:db
yarn run v1.12.3
$ rimraf 'database/schema.graphql' && yarn prisma deploy
$ prisma deploy
Deploying service `default` to stage `default` to server `local` 1.2s
Service is already up to date.

post-deploy:
project database - Schema file was created: database/schema.graphql

Running graphql get-schema --project database ✔
error Command failed with exit code 1.
error Command failed with exit code 1.

Running yarn codegen...
$ yarn codegen:schema && yarn codegen:relay && yarn codegen:graphql
$ graphql get-schema -p api -o server/api/schema.graphql --all false
$ relay-compiler --src . --include 'client/**' 'components/**' 'hooks/**' 'mutations/**' 'pages/**' --schema server/api/schema.graphql --noFutureProofEnums true
HINT: pass --watch to keep watching for changes.

Writing js
Unchanged: 23 files
$ graphql codegen && yarn codegen:graphql:fix
TypeError: Cannot read property 'type' of undefined
    at getWhere (/Users/alex/ws/este/node_modules/prisma-binding/dist/utils.js:45:9)
    at /Users/alex/ws/este/node_modules/prisma-binding/dist/utils.js:38:20
    at Array.map (<anonymous>)
    at getTypesAndWhere (/Users/alex/ws/este/node_modules/prisma-binding/dist/utils.js:33:23)
    at Object.getExistsFlowTypes (/Users/alex/ws/este/node_modules/prisma-binding/dist/utils.js:15:17)
    at PrismaFlowGenerator.renderExists (/Users/alex/ws/este/node_modules/prisma-binding/dist/PrismaFlowGenerator.js:43:36)
    at PrismaFlowGenerator.render (/Users/alex/ws/este/node_modules/prisma-binding/dist/PrismaFlowGenerator.js:29:2039)
    at /Users/alex/ws/este/node_modules/prisma-binding/dist/bin.js:99:38
    at step (/Users/alex/ws/este/node_modules/prisma-binding/dist/bin.js:33:23)
    at Object.next (/Users/alex/ws/este/node_modules/prisma-binding/dist/bin.js:14:53)

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Running yarn codegen ✖
✨  Done in 33.40s.

What wrong with me?
Thanks.

I am rewriting Este to Prisma Client. Ask there. Sorry.


Get an error when running on Ubuntu x86

panic: Unsupported CPU, maybe it's too old to run Sonic.
goroutine 1 [running]:
github.com/bytedance/sonic/internal/native.init.0()
/home/runner/go/pkg/mod/github.com/bytedance/sonic@v1.5.0/internal/native/dispatch_amd64.go:164 +0x30a

https://github.com/bytedance/sonic/issues/255
The GTC server(gogs) use the sonic
I'm not sure if sonic should be deleted for this situation, it's faster than the go original json


Patch requests not working

It seems like patch requests are not working, I try to make calls with a private client app and also postman, but the response I get is always a 400.
Seen to output in Vs I saw this Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 PATCH "myUrl" application/json-patch+json 177
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware:Debug: PATCH requests are not supported
the request starting and then "PATCH requests are not supported", could someone help?

Please provide a repro (a simple action and an example of request you are sending), it's weird that the request is handled by the static file provider.

FYI, this debug message indicates that the static files middleware doesn't handle the request as it uses an incompatible verb: in this case, it allows the rest of the pipeline to be invoked. The 400 response likely comes from somewhere else.

@psp589 maybe you can use branch oauth2_withSimpleModuleOfPCCOM in our xkproject repo as a base code for adding a little sample to the web api controller that shows them a sample of our problem.

Sorry it was my bad I was doing the request in the wrong way


Entity Health & Damage Config Values don't carry over into Multiplayer Servers

Setting a new health and/or damage value for any of the entities in the config file don't carry over to a Multiplayer Server, eventually resetting the config file completely after a server restart occurs. The health and damage values do work for Singleplayer Mode however.
Health/Damage Config taking effect in a Singleplayer World:

Health/Damage Config taking effect in a Multiplayer Server:

Minecraft Version: 1.20.1
Forge Version: 47.2.0
Alex's Caves Version: 1.1.0
TACT Version: 1.1.0+1.20.1
Citadel Version: 2.5.3-1.20.1
Here's the modlist:
modlist.txt

eventually resetting the config file completely

That sounds more like the Forge config issue where it can think the config file is invalid and resets it. Make sure that you do not have the config file open in any program when put onto server. That you add or edit the config file while server is off and then close your editing program and then launched server.
These entity attribute values only apply at game launch. They do not take effect while the game is running. And trying to edit and save the config file with certain programs like notepad++ will cause forge to reject the file and reset the config file.

eventually resetting the config file completely

That sounds more like the Forge config issue where it can think the config file is invalid and resets it. Make sure that you do not have the config file open in any program when put onto server. That you add or edit the config file while server is off and then close your editing program and then launched server.
These entity attribute values only apply at game launch. They do not take effect while the game is running and so, editing them while game is running doesn’t make much sense. And trying to edit and save the config file with certain programs like notepad++ will cause forge to reject the file and reset the config file.

It seems to be working now, idk why it was working in the beginning because I didn't use Notepad++ to edit it, and the server was down when I added the edited config file in, wasn't opened in another program or anything
It all seems good now and working fine, my apologies


Environment selection fails with VS 2017

Hi!
I was happy to see that environment detection finally works. I gave it a spin, and my milage was rather mixed depending on... stellar constellations? Sometimes it works, sometimes is doesn't.
First of all, it's strange that even though I got two VS instances installed (one regular, and one insider (preview) version, both kept up do date), CMake Tools shows only two variations to chose from: x86 and amd64 toolsets. Moreover, it picks up the "older", non-preview toolset which I use far less frequently. (Bleeding edge tools and C++, ALWAYS). The output window reads:

Loading CMake Tools from c:\Users\Matty\Source\vscodecpp.vscode.cmaketools.json
Detected available environment "Visual Studio Community 2017 - x86
Detected available environment "Visual Studio Community 2017 - amd64
Detected available environment "Visual Studio Community 2017 - x86
Detected available environment "Visual Studio Community 2017 - amd64
Started new CMake Server instance with PID 9096
[vscode] Configuring using the "Ninja" CMake generator

but upon clicking the status bar button, I can only select from x86 and amd64, as if some name collision would occur.
Second, sometimes CMake configure just fine, and sometimes it fails to find the compiler, even after selecting amd64.
CMakeError.txt
CMakeOutput.txt
Third, after opening a trivial (CMakeLists.txt + Main.cpp) folder, it says:

CMakeTools extension was unable to initialize: Error: spawn cmake ENOENT [See output window for more details]

and the output window reads: Error: spawn cmake ENOENT
Something seems off. Am I doing something wrong?

VSWhere is used to find Visual Studio installations. If it's returning installs with the same name, the earlier returned ones will be overridden. Could you show the output of VSWhere using the -legacy -all -format json -products * flags?

Output as follows
PS C:\Users\Matty> & 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' -legacy -all -format json -products *
[
  {
    "instanceId": "f8ffb12d",
    "installDate": "2017-03-07T19:32:57Z",
    "installationName": "VisualStudio/15.2.0+26430.16",
    "installationPath": "C:\\Kellekek\\Microsoft\\Visual Studio\\15",
    "installationVersion": "15.2.26430.16",
    "isPrerelease": false,
    "displayName": "Visual Studio Community 2017",
    "description": "Free, fully-featured IDE for students, open-source and individual developers",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "channelId": "VisualStudio.15.Release",
    "channelPath": "C:\\Users\\Matty\\AppData\\Local\\Microsoft\\VisualStudio\\Packages\\_Channels\\4CB340F5\\catalog.json",
    "channelUri": "https://aka.ms/vs/15/release/channel",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660284#15.1.26430.16",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660300"
  },
  {
    "instanceId": "VisualStudio.14.0",
    "installationPath": "C:\\Kellekek\\Microsoft\\Visual Studio\\14.0\\",
    "installationVersion": "14.0"
  }
]

However, best and latest should include prerelease versions as well. I use this 10X more often, than the latest stable.
PS C:\Users\Matty> & 'C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe' -legacy -all -prerelease -format json -products *
[
  {
    "instanceId": "e391d431",
    "installDate": "2017-04-19T12:02:47Z",
    "installationName": "VisualStudioPreview/15.3.0-pre.4.0+26711.1",
    "installationPath": "C:\\Kellekek\\Microsoft\\Visual Studio\\Preview",
    "installationVersion": "15.3.26711.1",
    "isPrerelease": true,
    "displayName": "Visual Studio Community 2017",
    "description": "Free, fully-featured IDE for students, open-source and individual developers",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "channelId": "VisualStudio.15.Preview",
    "channelPath": "C:\\Users\\Matty\\AppData\\Local\\Microsoft\\VisualStudio\\Packages\\_Channels\\48CDB76F\\catalog.json",
    "channelUri": "https://aka.ms/vs/15/pre/channel",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660470#15.3.26711.01",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660485"
  },
  {
    "instanceId": "f8ffb12d",
    "installDate": "2017-03-07T19:32:57Z",
    "installationName": "VisualStudio/15.2.0+26430.16",
    "installationPath": "C:\\Kellekek\\Microsoft\\Visual Studio\\15",
    "installationVersion": "15.2.26430.16",
    "isPrerelease": false,
    "displayName": "Visual Studio Community 2017",
    "description": "Free, fully-featured IDE for students, open-source and individual developers",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "channelId": "VisualStudio.15.Release",
    "channelPath": "C:\\Users\\Matty\\AppData\\Local\\Microsoft\\VisualStudio\\Packages\\_Channels\\4CB340F5\\catalog.json",
    "channelUri": "https://aka.ms/vs/15/release/channel",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660284#15.1.26430.16",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660300"
  },
  {
    "instanceId": "VisualStudio.14.0",
    "installationPath": "C:\\Kellekek\\Microsoft\\Visual Studio\\14.0\\",
    "installationVersion": "14.0"
  }
]

This does not address the "sometimes" failing detection with ENOENT errors and such. Any ideas on those?

Unfortunately, it does not at all for me. Running vswhere gives
PS C:\Program Files (x86)\Microsoft Visual Studio\Installer> .\vswhere.exe -legacy -all -format json -products *
[
  {
    "instanceId": "8d6ed86d",
    "installDate": "2017-03-03T07:02:25Z",
    "installationName": "VisualStudio/15.2.0+26430.16",
    "installationPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Community",
    "installationVersion": "15.0.26430.16",
    "displayName": "Visual Studio Community 2017",
    "description": "Free, fully-featured IDE for students, open-source and individual developers",
    "enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
    "channelId": "VisualStudio.15.Release",
    "channelPath": "C:\\Users\\buffo\\AppData\\Local\\Microsoft\\VisualStudio\\Packages\\_Channels\\4CB340F5\\catalog.json",
    "channelUri": "https://aka.ms/vs/15/release/channel",
    "releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=660284#15.1.26430.16",
    "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=660300"
  }
]

Visual Studio 2017 is not detected at all. :(

@buffos, uhm... have you read through the output? (Either you or I am making a fool of myself.)

"installationPath": "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community",
"displayName": "Visual Studio Community 2017",

How much more of 2017 do you want to see in the output?

@MathiasMagnus I see 2017 of course the output of vswhere.

This could be for different reasons, e.g. if vcvarsall.bat is missing or not everything is installed. E.g. Windows SDK (which weights few gigs) is required.
Can you build with CMake from command line?

@buffos What you might try is when you open a CMake Tools capable folder, check inside the ${workspaceroot}/build folder and catch the batch scripts that the extension executes and uses for build environment detection. They are fairly shortlived (2-4 seconds, depending on your HW), but if you open them with any editor, than they cannot be deleted (because they are opened). There you can see how and where CMake Tools is trying to invoke vcvarsall.bat.
It might get you closer to why the extension fails to find your install.

@MathiasMagnus  thx a lot
@ytimenkov It builds fine from the command line
Maybe because  I have MinGW installed to and it sees that first and tries to work with that.
Can I tell the tools to ignore MinGW and search for another environment

@buffos

Can I tell the tools to ignore MinGW and search for another environment

try setting mingwSearchDirs to an empty array.
But VS and MinGW installations are searched in parallel so I don't expect this to help.

Indeed no luck, but ok Until I find out what is wrong, I can always build with VS Studio.

I find a way to "fix" it, but it does not make sense.
I set "cmake.loggingLevel": "verbose" and now it prints it detects VS....

@buffos CMakeTools allow to select multiple environments. I.e. you may select both MinGW and VS at the same time. Could you try selecting / deselecting different environments?

@ytimenkov . where is that option? in the status bar it allows me to select one, and it only shows MinGW.
Thank you for your time.

@buffos If you don't see Visual Studio in the status bar then for some reason CMake Tools couldn't detect it. There are few things you can do:

Menu 'Help' -> 'Toggle Developer Tools' to open console, CMake Tools should dump detection issues there (in addition to verbose logging mode).

Or  to work around:

Run vscode from Developer Command prompt.
Use Visual Studio 15 2017 generator. It produces msbuild projects which don't require environment set up. CMake uses registry and msbuild itself uses .props files to locate paths.

@ytimenkov Here is the part relevant to the problem. It reports error running a bat file. I went to the location and the bat file runs manually fine. There is also a rejected promise in the console.
extensionHost.ts:320 [Extension Host] Restarting CMake Tools backend extensionHost.ts:320 [Extension Host] Shutting down CMake Tools backend extensionHost.ts:320 [Extension Host] CMake Tools has been stopped extensionHost.ts:320 [Extension Host] Starting CMake Tools backend extensionHost.ts:320 [Extension Host] [cmake output]: cmake version 3.9.0 extensionHost.ts:320 [Extension Host] [cmake output]:  extensionHost.ts:320 [Extension Host] [cmake output]: CMake suite maintained and supported by Kitware (kitware.com/cmake). extensionHost.ts:320 [Extension Host] cmake exited with return code 0 extensionHost.ts:320 [Extension Host] Loading environments extensionHost.ts:320 [Extension Host] Loading CMake Tools from c:\Users\buffo\Code\python\prj - selfDrivingCars\carnd-project\11.path.planning\.vscode\.cmaketools.json extensionHost.ts:320 [Extension Host] Detecting environment: Visual Studio Community 2017 - x86 extensionHost.ts:320 [Extension Host] Detecting environment: Visual Studio Community 2017 - amd64 extensionHost.ts:320 [Extension Host] Detecting environment: Visual Studio Community 2017 - arm extensionHost.ts:320 [Extension Host] Error running C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat  extensionHost.ts:320 [Extension Host] Error running C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat  extensionHost.ts:320 [Extension Host] Error running C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat  extensionHost.ts:320 [Extension Host] Environments loaded extensionHost.ts:320 [Extension Host] Detected available environment "MinGW - C:\MinGW extensionHost.ts:320 [Extension Host] Started new CMake Server instance with PID 55040 shell.ts:443 Invalid backend promise: Error: Invalid backend promise     at CMakeToolsWrapper.<anonymous> (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:267:44)     at Generator.next (<anonymous>)     at C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:13:65     at __awaiter (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:9:12)     at CMakeToolsWrapper.shutdown (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:264:16)     at CMakeToolsWrapper.<anonymous> (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:280:24)     at Generator.next (<anonymous>)     at C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:13:65     at __awaiter (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:9:12)     at CMakeToolsWrapper.restart (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:278:16)     at CMakeToolsWrapper.<anonymous> (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:75:28)     at Generator.next (<anonymous>)     at fulfilled (C:\Users\buffo\.vscode\extensions\vector-of-bool.cmake-tools-0.10.2\out\src\wrapper.js:10:58)     at process._tickCallback (internal/process/next_tick.js:103:7)

@buffos Which parameters did you pass to VsDevCmd.bat? It should be something like:
VsDevCmd.bat -no_logo -arch=amd64
As for rejected promise, it may be not an issue, just a side effect. It is definitely not related to environment detection.

@ytimenkov Did not pass anything.  I thought it was auto detecting and I did not need to do anything.)

Closed.
If this issues still persists in the current 0.11.0-beta4, feel free to reopen this one or create a new one.


No way to get the request client HTTP version

There is no way that I can find anywhere in ASP.NET Core or Kestrel to simply get the HTTP client version for a request/connection. I see in Kestrel that the server does a great deal of work to accurately determine this, and then the result is hidden in internals not available to the end user. Plus, the http context consumes the raw protocol packets and then they're irreversibly disposed, so there's just no way for the user to re-perform this work, even if we felt like doing the same work twice that Kestrel and friends are unnecessarily hiding from us.
Slightly on to another barely related topic, imo the raw header strings should be preserved also since the parser does irreversible transformations on keys and values, but I think that suggestion should go to kestrel server.
Anyway yeah, forgive me if the HTTP version is available (should exist at context or connection scope), but I can't find it and it really ought to be available.

HttpContext.Request.Protocol?

@Tratcher What little documentation and reference I could find states that this will simply be http but I have not run tests to confirm, I simply took those references at their word.

Any references? We can get those fixed. "http" should be the Scheme, not the Protocol.

@Tratcher I'll try to find them, but I'll invest first in doing some actual tests. Hopefully I'm just wrong and can close this out.

Yeah you're right, and the info was wrong, and I was wrong for not testing it before spamming here with a false issue! Sorry about that. :)


fix: Add workarounds to prevent filesystem corruption on Apple Virtualization VMs.

This is a workaround for #4840. Apple introduced a new VZNVMExpressControllerDeviceConfiguration in macOS 14 Sonoma's Virtualization Framework, emulating an NVMe disk for Linux guests. This emulated disk is slower than the virtio disk from my initial testing, but it does not have the filesystem corruption issue present on the default virtio interface in most Linux kernels. macOS guests cannot use this device configuration, but they do not experience the filesystem corruption issue in the first place. On macOS 12+ hosts that cannot use VZNVMExpressControllerDeviceConfiguration, the cache mode of virtio drives in Linux VMs are changed to .cached because it is verified to also fix the filesystem corruption: https://github.com/utmapp/UTM/issues/4840#issuecomment-1824340975
This PR:

Added a configuration in the UI to let users select whether the disk should use the NVMe interface. It only affects Linux VMs; on macOS VMs, this configuration does nothing.
Uses NVMe as the default for new Linux VMs on macOS 14+
Added localization for Chinese (Simplified and Traditional) and Japanese.
On macOS 12+ hosts, the caching mode for virtio drives in Linux VMs is changed to .cached

This successfully workarounds the file corruption problem. I didn't notice any new issues so far with NVMe.

Updated to include setting the caching mode to .cached for macOS 12 hosts. Now, there is uncertainty about whether to continue using nvme as the default for creating new VMs, as .cached virtio drives seem to address the filesystem problem and perform better than nvme drives.

I'd say for Linux, we use uncached when NVMe is available (macOS >= 14) and viritio + cached. Your PR is spot on.
My reasoning is that it seems that uncached is the de facto default even on 32 GB RAM systems. I couldn't find any information about the logic behind automatic and when it switches to cached vs uncached. It might be dependent on total RAM. It makes sense to use uncached as we don't waste host RAM for caching guest disk, which it does by itself already. Thus we avoid double caching of guest disk access. I could imagine there might be workloads that could benefit from host caching, but I think we should keep the defaults as close as possible to the underlying framework.
BTW It might be good idea to let user decide which mode is the best for their use case, but that would have to be an advanced setting with some explanations. The same applies to synchronization modes. But I think that should be first discussed with @osy as UI changes are needed. Looking at QEMU support, where one can adjust almost everything on a very low level, I'd say this is something that would be consistent with the general look and feel of UTM.

I see that NVMe defaults to false. I thin we should have good defaults for new users. Otherwise if NVMe isn't enabled by default for macOS >= 14 and caching for older macOS, then people will still experience corruption and will have to live with it (and blame Linux or UTM) or research what to do. In both cases they will waste their lives dealing with this.

Defaulting to NVMe isn't great because it might render some VMs unbootable. It might be a good idea to figure out how to add more info about NVMe and why it was introduced and pros/cons.

Defaulting to NVMe isn't great because it might render some VMs unbootable. It might be a good idea to figure out how to add more info about NVMe and why it was introduced and pros/cons.

This PR does not change the options of existing disks. Instead, when a user creates a new VM, the new disk created with this VM will be set as an NVMe drive on macOS 14+ hosts by the following lines in the wizard:
https://github.com/utmapp/UTM/blob/6c02a1a360ec2f528e1b967bb87071c3d209afc4/Platform/Shared/VMWizardState.swift#L256-L259
This is what I meant by "default". Not magically using NVMe for every disk, but to decide what to use for newly created VMs.

Thanks, this makes sense.

I did some more testing and for some workloads, like unit tests, I see about 15-20% slowdown with NVMe drive which is getting significant for my use case. I'm going to run my VMs in virtio mode with host caching.

I haven't used UTM much last week, so can't say one way or another. stress-ng and parallel cp work fine with caching + viritio, so probably that's a good compromise between stability and performance. We might want to add a note somewhere about the fact that host disk image caching is enabled with Linux guests when NVMe is off.

NVME disk works fine on linux kernel 5.x (ubuntu 22.04.3) , but always fail on macOS Sonoma 14.2 debian 12.4.0

When I tested with Fedora, it was using the upstream Fedora kernel (the 6.5 branch kernel) and did not exhibit this issue. It now appears that macOS 14.2 might have modified the NVMe device. Experiencing a straightforward NVMe I/O error is something we haven't encountered before. I'm re-testing in the same environment using stress-ng to see if I can reproduce it. It's possible that the NVMe disk also requires the caching mode to be set to cached now.

Strange, my environment used with pre-14.2 with a fast 10-minute stress-ng cannot reproduce this. @wangqiang1588 does this always occur or does it happens randomly?

Strange, my environment used with pre-14.2 with a fast 10-minute stress-ng cannot reproduce this. @wangqiang1588 does this always occur or does it happens randomly?

I Install debian 12.4.0 twice , it happens twice.

install debian from iso, give 24GB memory 、 12 cpu kernel 、500GB disk
send 113 GB android aosp zip file from scp command (success)
unzip 113GB aosp file ( success )
repo init -b android-security-11.0.0_r72 (success)
repo sync -j4 --fail-fast -l ( local sync a lot of files then  fails here, twice)

always fails on "repo sync" command
then i change it to  caching + viritio ,same steps , success
same steps ubuntu 22.04.3 linux kernel 5.15 nvme disk  never failure happens
looks like some nvme driver changed after 5.15 kernel  make this failure

On NixOS unstable channel + Linux kernel 6.6.7 using uncached NVMe all my tests are passing. No disk corruption during stress-ng, parallel cp or system upgrade.

On NixOS unstable channel + Linux kernel 6.6.7 using uncached NVMe all my tests are passing. No disk corruption during stress-ng, parallel cp or system upgrade.

maybe the number of files make this bug, "repo sync" make a lot of files at very short time (*.h, c ,.java ...)

Fedora 39 Test ,not found this bug, looks like only happen on linux kernel 6.1 , let me try to upgrade debian's kernel

today upgrade macOS Sonoma 14.2 to  14.2.1  every thing works again .
maybe this is a bug of macOS Sonoma 14.2 .

Can confirm tart works perfectly for me (see reference to cirruslabs/tart above). No disk corruption after two days. Tart uses NVME disks.  Host: Sonoma 14.2.1. Guest: Ubuntu 24.04 (Noble Numbat). Kernel 6.6.7.

@osy I just rebased from main.
One change I've made is that I reverted the nvme as default and prefers virtio with cached mode because there are new reports that the nvme mode is still causing errors in some cases where the virtio + cached mode works just fine.

🎉 can’t wait.
Please include this important fix for Linux vm’s in 4.5

Any news on when this might get merged and released?

An early beta release with this fix is much appreciated as some other projects did. Otherwise it is practically not possible to use a stable linux vm with apple virtualization, no?

For reference this seems to be solved here some time ago  https://github.com/lima-vm/lima/pull/2026
And there seems to be no issues about corruption after that.

@osy I apologize for pinging, do you think this could be merged? UTM experience is just so buggy without this.

This will be included in the next release. If you need this now, you can follow the build instructions along with the prebuilt dependencies. Having multiple people ask about a release isn't going to speed it up. If you want to help maintain this project please let me know.

This will be included in the next release. If you need this now, you can follow the build instructions along with the prebuilt dependencies. Having multiple people ask about a release isn't going to speed it up. If you want to help maintain this project please let me know.

I'm already using a version built by myself with the patch, but I need to keep it up-to-date and it isn't signed.
As I said, I apologize for pinging, I just wanted to make sure that this didn't accidentaly slip your mind. I understand the effort an open source maintainer needs to put into his projects, so, thank you! No claim or demand on my part.
If I can help with testing this (and reporting my test findings) I'll do it. But I don't think I have the bandwidth to become a maintainer for this project.

I guess this is a fairly helpfull issue. People put info, solution and test. I dont think there is a room for apologize since this is a corruption issue, there is a fix and there are sincere people trying to be helpful. Since this is 4 month old fix and it is we people tend to forget among other things people are just trying to land a kindly reminder.


Mongoid + countries with simple_form

I found an odd bug, not sure if others are seeing this.
I'm using mongoid-5.1.1 + simple_form-3.3.1 + countries-1.2.5 + country_select-2.5.2
I have a field in a model as such:
field :country, type: ISO3166::Country, default: 'US'

However, when I show it in a simple_form, the values of country that gets saved is not selected when the form is redisplayed. I've tried multiple variations of the following
=f.input :country, label: t('city.country'), as: :country, priority: ['CA', 'US', 'AU', 'NZ']
=f.input :country, label: t('city.country'), as: :country

The only way this works is by changing Country type to string
field :country, default: 'US'

Any thoughts?

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.


feat: rust-walkdir SRC

Recursively walk a directory - Rust source code
Log: rust-walkdirrust-walkdir SRC would be added.
Issue:
https://github.com/deepin-community/sig-deepin-sysdev-team/issues/382

/lgtm


Cannot connect to Docker Hub

Expected behavior
I launched Kitematic (Beta) on my MacBook Pro (High Sierra). I expected I could login into Docker Hub, because I'm on the internet.
Actual behavior
The login process stalls. I get no message and it lasts for minutes. The only way I could stop the waiting is to quit Kitematic from the MacOS dock.

Information about the Issue
Could this be caused by a non-http(s) protocol that is blocked by the company's firewall? I have no clue...
Steps to reproduce the behavior

... start Kitematic (beta)
... push the login button on the top of the Kitematic window.

duplicate issue from #4094 (sorry...)

@stefjoosten The link you provided there is no solution. people keep saying same problem on windows 7, 10 and mac but no solution is given.


mIoU scores different between validation (during training) & testing (post training evaluation) using same data

As title, I used same data for validation & testing evaluation.  However, the mIoU is different from training & testing.
What's the differences that make a same dataset has different mIoU when doing validation and testing? Thanks.

@WeiChihChern Have you discovered the reason for this?


Blog: Shows author tag instead of full name

What happened?
See title.
Related: #488.

The GraphQL API does not allow you to fetch a user's full name. In this instance, the "actor" represents a user with the ability to retrieve the avatar, login, and url.

Since the ID is not provided the actor resource, it is very difficult to move further with this feature.


timestamp.NULL seems like a bad smell

https://github.com/amzn/ion-js/blob/timestampUpdates/src/IonTimestamp.ts#L463
We should return null instead of timestamp.NULL wherever timestamp.NULL is used.

This looks like it was addressed in #361 and can be closed?

yes, closing


Fix EG samples

Samples were failing based on new validation - https://dev.azure.com/azure-sdk/internal/_build/results?buildId=751823&view=ms.vss-test-web.build-test-results-tab&runId=16879826&resultId=100018&paneView=debug

/azp run net - eventgrid - tests


Added Tooltip Text to All Elements

Fixes #486
Describe the changes you have made in this pr -
I have added a Tooltip text (alert) to all the elements present in the modules.js File. I have added it to Testbench and Sequential files too.
Screenshots of the changes (If any) -

Coverage remained the same at 83.902% when pulling df9d49fdad3d0403a50641a3fa43fdd7a81fdbed on Shivansh2407:patch-17 into 097930075bb42cc181a9742cfbd6d3e83431f826 on CircuitVerse:master.

@ankitkataria and @sakshi1499 I am facing a problem while extending the tooltip to testbench.js and sequential.js . As soon as I add the tooltip there, it does not shows up on reloading ?
Please let me know how to proceed with this ?

Added for all the elements. 👍 Please review and merge

@tachyons take a look at this.

@tachyons Please review.

Thank You @tachyons Sir 👍


Insert users from another SQL DataBase

Can I insert some records of users directly to table AspNetUsers?
What fields is required for using UserManager?
I have Id, UserName and EMail. Can I change password?
I need insert an any GUID in the field ConcurrencyStamp. Am I right?

I'm adding GUID and now this is working.


can't open output file

Hello, I have a problem. I'm using ubuntu terminal in windows10 after generating the subtractedkey with the command -o out.txt i can't access the file. You do not have permission to access the file, I have try to chmod 777 with no succes also when trying to delete the file with rm out.txt give me > rm: cannot remove 'out.txt': No such file or directory. I have try to change the output name and same issue. I have like 5 file output now with different name .. i can't acces them or delete them

how do you are opening the file?
BYW this is not related with the tool, this is a linux problem or some other issue, i can't help with this issue.


Unable to deploy stack on CE 2.15 when using a CIFS portainer_data mount

Bug description
I have a bunch of stacks which I've been able to run fine using the previous version of portainer.
Just upgraded to CE 2.15, and now when I try to deploy any of my previous stacks, I'm getting the below error:
"failed to deploy a stack: unexpected character "\x00" in variable name near "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\n[ENV VARS HERE]"
I'm manually specifying env vars using the portainer UI, which override default values in the .env file for each of my stacks. The stacks are being pulled from my github repo.
Expected behavior
Should deploy.
Portainer Logs
Per above.
Steps to reproduce the issue:
Per above.
Technical details:

Portainer version: CE 2.15
Docker version (managed by Portainer): 20.10.17
Kubernetes version (managed by Portainer):
Platform (windows/linux): linux
How are you running portainer: via compose:
version: '2.4'
services:
portainer:
image: portainer/portainer-ce:latest
container_name: portainer
security_opt:
- no-new-privileges:true
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- data/portainer:/data
ports:
- 9443:9443
restart: unless-stopped

Just rolled back to 2.14.2 and was able to deploy a stack with the exact same config successfully.

Can you share the stack file you're using? I wonder if there's special characters or some formatting weirdness that's causing this to fail in 2.15.

The stacks are manually configured through the portainer UI. They are all pulling from my private repo.
There isn't anything exotic going on. Each of the git folders I'm pulling from have a .env, docker-compose-yml, and environment.yml. The only thing I'm doing with might not by typical, is overriding the .env var values, by manually setting these variables as part of the portainer stack config.
I've got 8 different stacks set up this way. Got the same error above for every stack I tried using 2.15 (probably tried 4-5). I then rolled back to 2.14.2 and all 8 successfully deployed again. I also tried completely wiping all previous volumes, images etc. and deleting out all the old stack configs/ recreating fresh. And no go.
Also, on your point -- I spot checked the .env and environment.env files for one of the stacks. And there weren't any extra carries or formatting issues.
This shouldn't be too hard for someone else to replicate.

I haven't been able to replicate this behavior locally at all. I've used a basic WordPress stack to test - you can see it in this repo - which includes a .env file defining one of the two variables used in the docker-compose.yml. Regardless of whether I only set the MYSQL_DATABASE_PASSWORD variable through the UI or I set both (overriding the .env file) the stack deploys successfully.
If you're not comfortable with sharing your stack publicly, perhaps you could share a redacted version if it privately with me so that I can dig further? You can either drop me a DM in our community Slack channel or email me at<EMAIL_ADDRESS>

Let me try your config tonight and see if I can help narrow down on this.
FYI, I'm also running environment.yml files for my stacks (don't think this would be the issue) and some of the .env vars are left as blank on the source repo (this might be the issue). I define any blank .env vars as part of the portainer stack config.
They seemed to be the main differences. But I'll share a problematic compose config too once I re-confim.

Ok, your config also gives me the issue. So, looks like a problem with my portainer container itself.

To confirm how I can do a completely fresh install of portainer. Can I simply dump all of my persistent data outside of the /compose/ dir (which I believe has my stack configs), recreate the portainer container, drop my compose dir back in, and then start-up?

To confirm how I can do a completely fresh install of portainer. Can I simply dump all of my persistent data outside of the /compose/ dir (which I believe has my stack configs), recreate the portainer container, drop my compose dir back in, and then start-up?

We generally recommend removing the portainer_data volume and recreating a fresh one - what you could do here for testing is simply create a new empty data volume and reference it from your docker run command instead of portainer_data. That way you'd get a fresh install without having to nuke your previous install.

Ok, I got the same issue as above even after completely nuking my previous portainer volume. I have this in the original post, but just to note again, here is my current portainer compose config:
---
version: '2.4'
services:
  portainer:
    image: portainer/portainer-ce:latest
    #image: portainer/portainer-ce:2.14.2
    container_name: portainer
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ${DATA_PATH}/portainer_latest:/data
      #- ${DATA_PATH}/portainer:/data
    ports:
      - 9443:9443
    restart: unless-stopped

.env:
DATA_PATH=[REDACTED]

You've noted Linux as your environment above, can you be more specific? Distro, platform, etc? The closer I can get to your setup the more likely I am to be able to replicate.

Did your test of the wordpress stack match my screenshot above? outside of the 'test' var values?

Did your test of the wordpress stack match my screenshot above? outside of the 'test' var values?

Yes, matched exactly.

You've noted Linux as your environment above, can you be more specific? Distro, platform, etc? The closer I can get to your setup the more likely I am to be able to replicate.

I'm running Debian 11 via a VM. Let's take this over to slack, and I'll be sure to drop any solution back here.

For anyone interested -- @jamescarppe found the issue. It was due to my portainer_data volume path being served via a CIFS mount. Should be able to deploy these stacks without issue on 2.15 if the volume is on the same machine as portainer.

I've updated the issue title to suit the new issue. I'm discussing this internally with the engineering team now - initial theories are that this might be a result of some changes we made to how we use BoltDB in order to provide improved scalability, but once I learn more I'll update here.

any updates on this?

I can say I am also having this issue on CE 2.16.2.  This completely prevents me from using Portainer in my current setup - The CIFS share is on a completely different machine as it's easier to backup all of my docker files at once from that location.
Is there any work around for this without needing to move the portainer data locally?

any updates on this?

I just rolled the dice on Portainer 2.19, and it still has the same issue. Portainer 2.14.2 continues to be the last version which allowed CIFS mounts for volumes.

@buswedg
Can you add cache=none option to your CIFS mount and then try?
Eg:
mount -t cifs //x.x.x.x/path/to/share /path/to/mountpoint -o username=<username> -o password=<password> -o cache=none
If its a docker volume then
volumes:

  mycifs:

    driver: local

    driver_opts:

      type: cifs

      o: addr=<ip address>,user=username,password=password,cache=none

      device: //IP/path/to/share


Reversible vtxo in async payment

This PR adds the necessary abstraction to process different types of VTXOs. It allows adding the ReversibleVtxoScript type used as output of async payments.
Vtxo script type

A vtxo script is defined as a taproot contract with at least 1 forfeit closure (User && ASP) and 1 exit closure (A after t). It may contain others closures implementing specific use cases.
common.VtxoScript abstracts the taproot complexity of vtxo script.
a vtxo script is compiled, transferred and parsed using descriptor string.
the default vtxo script is tr(_,{ and(pk(USER), pk(ASP)), and(older(T), pk(USER)) })
the reversible vtxo script is tr(_,{ { and(pk(SENDER), pk(ASP)), and(older(T), pk(SENDER)) }, { and(pk(RECEIVER), pk(ASP) } })
while spending a VTXO, the spender must provide the associated descriptor and the signer public key (in order to signal to the ASP the forfeit leaf to use)

TL;DR

[common] add VtxoScript interface
[tx-builder] use VtxoScript to craft vtxo tree transactions
[api-spec] add descriptor instead of pubkey while registering inputs
[api-spec] add signingPubKey when spending a VTXO
[api-spec] specify descriptor instead of offchain address while registering outputs
[db] replace Vtxo.Pubkey by Vtxo.Descriptor

PS: This PR does not add the necessary change to support the "Reverse" UX in the SDK even if it's technically possible today for the sender to spend (via reverse forfeit leaf) an async payment VTXO. It may need extra work to keep track of the reversible VTXOs and coin-select them.
@altafan @tiero @sekulicd @bordalix  please review

May be worth to lay down the ground work of key path spending for cooperative cases? We may not need to migrate right now, but at least figuring out the abstraction of needs some more work in the future, better now


Javascript API to subscribe to "events" for preference changes/initialization/etc

As a web developer, I want to add the Fides components to my site and have a simple way to subscribe to “events” that are triggered when the consent preferences are either initialized to default values, or updated based on a user’s preferences, so that I can write custom Javascript code to manage tags or enforce consent on my own systems.
Details
We need to provide as much backwards-compatibility as possible with the existing fides.js API, which is a simple read-only window.Fides.consent object that includes the user’s consent preferences
We need to ensure that events are triggered whenever the preferences change, including:

Initializing the script to “defaults” based on the user’s geolocation
User saving their preferences from the modal
User rejecting all notices from the banner
User accepting all notices from the banner

etc.
AC

When I’ve added Fides consent to my site, then I can subscribe to Javascript events to be notified when the window.Fides.consent object is initialized
When I’ve added Fides consent to my site, then I can subscribe to Javascript events to be notified when the window.Fides.consent object is updated by the user (saving preferences from modal, rejecting notices from banner, accepting notices from banner, etc.)

I gave this some thought and poked around at other generic JavaScript projects, and it does seem like there are three good options:

Using the super normal window.dispatchEvent() function; https://developer.mozilla.org/en-US/docs/Web/Events/Creating_and_triggering_events
Providing some React props like onInit, onSave and call those. This only allows for a single listener for each callback so it isn't nearly as flexible as the first option
Importing the Node EventEmitter class and emitting events to all subscribed listeners. This supports multiple listeners but adds a lot more code

My preference is to do 1&2: trigger window events for vanilla JS installations, but also provide an explicit callback for React projects that import us. I don't think it's worth adding the EventEmitter module or similar; once you go that direction, it feels better to go all the way and support native ESM imports and React props 👍

Closed by https://github.com/ethyca/fides/pull/3454

moving to done


Create flag to disable pages for demo

Description
This removes the dummy landing page and the dummy move info page on staging.  It does not remove those pages for other environments
Reviewer Notes
using 'disable' creates a double negative situation, so not sure it's too confusing.  but saying 'showForDemo" seemed strange since we are showing everything else for the demo, even without the flag. . .open to feedback.
Setup
Locally, the flag is set to false (we are not disabling the page locally).  To check locally, set flag with ?flag:disableForDemo=true
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 5fe7764fe06a00154b45c1b3f4cad77f309d1b32


missing prebuilt arm64 binaries

I'm having this warning while building an Electron app on mac m1:
prebuild-install http 404 https://github.com/JoshuaWise/better-sqlite3/releases/download/v7.5.0/better-sqlite3-v7.5.0-electron-v99-darwin-arm64.tar.gz

@Hakentha does it work with typeorm?

PRs are welcome

Duplicate of https://github.com/JoshuaWise/better-sqlite3/issues/601


Cramjam wrong architecture error when installing on M1 with conda (mambaforge)

[X] I read the conda-forge documentation and could not find the solution for my problem there.
Issue:
I'm working on Apple M1 with a mambaforge deployment of conda.
When trying to save a dataframe to parquet using fastparquet I'm getting the following error:
ImportError: dlopen(/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so, 2): no suitable image found.  Did find:
/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so: mach-o, but wrong architecture
/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so: mach-o, but wrong architecture
Seems like conda is giving me the wrong version of cramjam?
MRE:
conda create -n cramjam
conda install cramjam ipython
ipython
import cramjam
ImportError: dlopen(/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so, 2): no suitable image found.  Did find:
/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so: mach-o, but wrong architecture
/Users/rpelgrim/mambaforge/envs/cramjam/lib/python3.9/site-packages/cramjam.cpython-39-darwin.so: mach-o, but wrong architecture
import cramjam does work when doing a pip install cramjam. But fails again if I then do a subsequent conda install fastparquet.
$ conda list
# Name                    Version                   Build  Channel
ca-certificates           2021.5.30            h4653dfc_0    conda-forge
cramjam                   2.3.2                    pypi_0    pypi
fastparquet               0.7.1            py39h20ef057_0    conda-forge
fsspec                    2021.8.1           pyhd8ed1ab_0    conda-forge
libblas                   3.9.0           11_osxarm64_openblas    conda-forge
libcblas                  3.9.0           11_osxarm64_openblas    conda-forge
libcxx                    12.0.1               h168391b_0    conda-forge
libgfortran               5.0.0.dev0      11_0_1_hf114ba7_23    conda-forge
libgfortran5              11.0.1.dev0         hf114ba7_23    conda-forge
liblapack                 3.9.0           11_osxarm64_openblas    conda-forge
libopenblas               0.3.17          openmp_h5dd58f0_1    conda-forge
llvm-openmp               12.0.1               hf3c4609_1    conda-forge
ncurses                   6.2                  h9aa5885_4    conda-forge
numpy                     1.21.2           py39h1f3b974_0    conda-forge
openssl                   1.1.1l               h3422bc3_0    conda-forge
pandas                    1.3.2            py39h7f752ed_0    conda-forge
pip                       21.2.4             pyhd8ed1ab_0    conda-forge
python                    3.9.7           h54d631c_0_cpython    conda-forge
python-dateutil           2.8.2              pyhd8ed1ab_0    conda-forge
python_abi                3.9                      2_cp39    conda-forge
pytz                      2021.1             pyhd8ed1ab_0    conda-forge
readline                  8.1                  hedafd6a_0    conda-forge
setuptools                57.4.0           py39h2804cbe_0    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
sqlite                    3.36.0               h72a2b83_0    conda-forge
thrift                    0.13.0           py39h93dc1e2_2    conda-forge
tk                        8.6.11               he1e0b03_1    conda-forge
tzdata                    2021a                he74cb21_1    conda-forge
wheel                     0.37.0             pyhd8ed1ab_1    conda-forge
xz                        5.2.5                h642e427_1    conda-forge
zlib                      1.2.11            h31e879b_1009    conda-forge

$ conda info

    active environment : cramjam
    active env location : /Users/rpelgrim/mambaforge/envs/cramjam
            shell level : 2
       user config file : /Users/rpelgrim/.condarc
 populated config files : /Users/rpelgrim/mambaforge/.condarc
          conda version : 4.10.3
    conda-build version : not installed
         python version : 3.9.6.final.0
       virtual packages : __osx=11.3.1=0
                          __unix=0=0
                          __archspec=1=arm64
       base environment : /Users/rpelgrim/mambaforge  (writable)
      conda av data dir : /Users/rpelgrim/mambaforge/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/rpelgrim/mambaforge/pkgs
                          /Users/rpelgrim/.conda/pkgs
       envs directories : /Users/rpelgrim/mambaforge/envs
                          /Users/rpelgrim/.conda/envs
               platform : osx-arm64
             user-agent : conda/4.10.3 requests/2.26.0 CPython/3.9.6 Darwin/20.4.0 OSX/11.3.1
                UID:GID : 501:20
             netrc file : None
           offline mode : False

see discussion with @milesgranger in this issue for more context

Is there a way to have the conda install fastparquet use the existing version of cramjam that I got from pip?

Unless @martindurant has a solution, I can poke around at this maybe sometime this week or next.
Martin is probably annoyed with me by now about this :sweat_smile: , I'll keep saying that it seems weird conda/recepies can't play well with an already pre-compiled binary. Especially b/c it works in this case (installing it separately from PyPI) and these specific wheels have zero Python dependencies. :disappointed: We're already at a point that we have to retry builds b/c they may end up on less powerful VMs and exceeds an hour limit; vs simply taking the already existing wheels from PyPI.
I really like having it distributed on conda, but it makes it a pain to do so in this case.  "There must be a better way."

I am asking some conda people, we'll see. Indeed, for fastparquet I have always found the conda path smoother than the wheel one (we didn't have non-source distribution for a long time).

This issue is mainly caused by the python interpreter and is skipping of .py->.pyc on osx-arm64.  This happens due issue of cross-compiling and building python.
I tested described issue on defaults after building maturin (downgraded to use rust >= 1.53.0), and  cranjam. The error seems not to exists there for me.  We don't provide those two packages on defaults for now, so I would recomment for the time being to use either pip (might not work for fastparquet).  I provide the test versions in my private channel 'ktietz' if someone is interested in them.

@katietz - removing fastparquet from my environment.yml and installing it through pip did the trick here for me. Thanks so much!

Nice!
I also wonder if something like this would work for you?
name: test
channels:
  - conda-forge
dependencies:
  - fastparquet
  - pip:
    - cramjam

@milesgranger - yes, that works too. thanks! 🙏

Should we remove the previous conda release that installs incorrectly? That can be done by submitting a patch PR, if we think it's important (I've never done this before myself)

I think we need to mark the previous osx-arm64 builds as "broken", actually.  I'll look into that.

https://github.com/conda-forge/admin-requests/pull/359


fix itersect operator takes too long time to execute

Proposed changes
Issue Number: close https://github.com/apache/incubator-doris/issues/10182
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No)
Has document been added or modified: (No)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

could you elaborate on the cause of the problem? and please update title follow by commit format specification


Allow app to fetch resources on route load

This required a TOVE change to let the app request resources by ID (ex. give me the project with id 5). This is necessary so a route like /projects/5/workflows/23/transcriptions will load correctly when navigating directly to it.

Closed in #65


Add a validation for the movie's imdbId

There was a missing validation to get a movie's imdbId. It was only checking if there was an anchor with a href attribute, but not if the href attribute contained 'imdb'. So if there was no imdb anchor, the regex was still called, but on an undefined value.
Update the tests movies to work, since the movies in the tests are no longer in theaters (may need to find a permanent solution).
Added 2 tests to test the 2 validations : theathers not found & movie not found.

Coverage increased (+2.5%) to 100.0% when pulling 20e76d326e65b46b25724c20cc52118aad368bc0 on jpgdev:fix_validation into 79725c44b901877386955031cc91229728a7ec3f on anault:master.


Make sure that the GC passes run over our functions

Codecov Report

Merging #271 (6837a47) into main (7726538) will decrease coverage by 3.87%.
The diff coverage is 48.38%.

@@            Coverage Diff             @@
##             main     #271      +/-   ##
==========================================
- Coverage   78.05%   74.17%   -3.88%
==========================================
  Files          14       16       +2
  Lines        3244     3187      -57
==========================================
- Hits         2532     2364     -168
- Misses        712      823     +111

Impacted Files
Coverage Δ

src/compiler.jl
79.08% <ø> (+0.45%)
:arrow_up:

src/compiler/utils.jl
44.82% <44.82%> (ø)

src/compiler/optimize.jl
97.77% <100.00%> (-0.04%)
:arrow_down:

src/compiler/passes.jl
100.00% <100.00%> (ø)

src/compiler/orcv2.jl
0.00% <0.00%> (-72.39%)
:arrow_down:

src/compiler/interpreter.jl
31.11% <0.00%> (-60.38%)
:arrow_down:

src/logic.jl
75.00% <0.00%> (-5.00%)
:arrow_down:

src/compiler/validation.jl
60.07% <0.00%> (-2.52%)
:arrow_down:

src/api.jl
48.00% <0.00%> (-1.62%)
:arrow_down:

src/pmap.jl
79.23% <0.00%> (-1.10%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Adding documentation

Most (if not all) of the codebase is undocumented or lacking comments. I would be willing to go through and add Intellisense-style commenting to any methods and classes I can think of appropriate comments for, if warranted.

XML comments are fine, but I'm of the opinion that the codebase is well organized and easy to read without comments.

Yeah, the code is easy to understand by itself, just thinking about mods/plugins being quicker to develop without having to jump into the server/client code non-stop.

Yeah, XML comments are a good idea. Particularly in TrueCraft.API.

Okay, I'll start looking at it. Thanks for the confirmation.

I don't think this issue is necessary at this point. Feel free to send more documentation PRs.


Chore: Increase number of workers for Playwright GitHub action

Increase the number of workers to three for the Playwright GitHub action.

I didn't realize when I set up E2E tests that I set it to 1. 3 workers should be good like we had on the next/runtime when I worked at Netlify.
https://github.com/netlify/next-runtime/blob/main/playwright.config.ts#L15


Update Debian GNU/Linux packaging scripts

new GIT snapshot
improved package descriptions
minor copyright file fixes
add merge-lumina-i18n script (update translations using lumina-i18n repo)

You may want to un-bashify merge-lumina-i18n.sh (and move out of debian/) so everyone could use it. But I'm lazy (and on Bash anyways).

Looks good. I will take a look at the merge i18n script later, but for now it is fine to leave in the debian directory.


problem with start_params

in this url for example : https://t.me/mybot?startapp=bbId38341612
when open it with telegram desktop, WebApp.initDataUnsafe.start_param working fine and get bbId38341612
but when I want open that with iphone 13 , always WebApp.initDataUnsafe.start_param is undefined, my project on react.js
and "@twa-dev/sdk": "^7.0.0",
help me to fix that
I check https://github.com/TelegramMessenger/Telegram-iOS/issues/1091
but still have problem

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

I have the same problem =(

What is yout app version?

I have the same problem =(

What is your app version?

last

I work in unity (webgl) via telegram bot mini api
July 31, 2024
Bot API 7.8

in this url for example : https://t.me/mybot?startapp=bbId38341612
when open it with telegram desktop, WebApp.initDataUnsafe.start_param working fine and get bbId38341612
but when I want open that with iphone 13 , always WebApp.initDataUnsafe.start_param is undefined, my project on react.js
and "@twa-dev/sdk": "^7.0.0", help me to fix that
I check TelegramMessenger/Telegram-iOS#1091
but still have problem

I have solved this problem!!!
/newapp in the bot wrote and filled in all the data!
t.me/My_bot - was
t.me/My_bot/appname - became

same issue,
"?startapp=command" works on fine desktop to fill start_param
but when i try using this on android then start_param stays undefined

@bobpepers
What is your exact app version?
What link do you use for testing?

@bobpepers
What is your exact app version? What link do you use for testing?

I'm building a React application using the latest version of @twa-dev/sdk (v7.10.1). My test link is: https://t.me/SecretTip_dev_bot?startapp=SecretTip
The following code works fine on desktop (Ubuntu 24.04):
await ctx.replyWithHTML(message, {
  reply_markup: {
    inline_keyboard: [
      [
        {
          text: 'Open Mini App',
          url: miniAppUrl, // URL that opens the mini-app directly in Telegram
        },
      ],
    ],
  },
});

However, when testing on Android, the start_param is not available when using the startapp=testParameter. One key requirement for my Telegram mini-app is that it needs to be opened from a Telegram group because I rely on the initData to determine the group from which the app was initiated.

Is bug fixed? Maybe some workarounds?

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

This was it. I didn’t realize setting up a web app through BotFather was something I had to do. It worked fine on desktop, so I didn’t catch that it was necessary step for phones. Thank you.

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

I have ennabled the miniapp in the bot settings, but I still can't get the start_param in iOS and Android

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

This was it. I didn’t realize setting up a web app through BotFather was something I had to do. It worked fine on desktop, so I didn’t catch that it was necessary step for phones. Thank you.

Hi @bobpepers ，Can you tell me where webapp_name is set?

If you want to get the webapp_name, use /newapp to create an app for your bot.

Still getting this error on Telegram for Android v11.1.3 (5243)
When opening miniapp using t.me/bot_name?startapp=testParameter - start_param is available on Windows Desktop, but unavailable on MacOS Desktop, iOS and Android
Default webapp t.me/bot_name/webapp_name?startapp=testParameter works fine

in this url for example : https://t.me/mybot?startapp=bbId38341612
when open it with telegram desktop, WebApp.initDataUnsafe.start_param working fine and get bbId38341612
but when I want open that with iphone 13 , always WebApp.initDataUnsafe.start_param is undefined, my project on react.js
and "@twa-dev/sdk": "^7.0.0", help me to fix that
I check TelegramMessenger/Telegram-iOS#1091
but still have problem

I have solved this problem!!! /newapp in the bot wrote and filled in all the data!
t.me/My_bot - was t.me/My_bot/appname - became

i also have same problem my link is like https://t.me/masterversess_bot?startapp=${referralId}` this and i am not getting the start_param in initdata why canyou please help me what will i do . do i need to update the url

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

This was it. I didn’t realize setting up a web app through BotFather was something I had to do. It worked fine on desktop, so I didn’t catch that it was necessary step for phones. Thank you.

Hi @bobpepers ，Can you tell me where webapp_name is set?

same issue for me https://t.me/masterversess_bot/Masterverses?startapp=7472847113 i updated my link like this and it showing bot not found webapp_name is the bot name? can you please help if you get solution

Go to botfather, create /newapp and fill all the details. add weburl you will get complete link in myapps

This didn't solve it for me. Still the same issue. I have also inspected the window.location.href param and printed that to my DOM and no start_param is provided on Mac or iPhone. This approach should be version-agnostic since I imaging your library infers the start_param from the href since its an iframe at the end of the day.

for anyone having problem like this, try talk to BotFather and setup a webapp for your bot. After finish, depends on your setting the link will be like t.me/bot_name/webapp_name then when you open t.me/bot_name/webapp_name?startapp=Rick your webapp will be able to get startapp params

This was it. I didn’t realize setting up a web app through BotFather was something I had to do. It worked fine on desktop, so I didn’t catch that it was necessary step for phones. Thank you.

Hi @bobpepers ，Can you tell me where webapp_name is set?

same issue for me https://t.me/masterversess_bot/Masterverses?startapp=7472847113 i updated my link like this and it showing bot not found webapp_name is the bot name? can you please help if you get solution

Go to botfather, create /newapp and fill all the details. add weburl you will get complete link in myapps


Added support to set access tier on a blob

/azp run android - storage- ci

/azp run android - storage - ci


Read traversal and COW

My case: I have always two clones, one for updating and the other for read traversal, every time a "transaction" is done I clone again the tree to force the next update to copy the nodes.
The problem with cow: even for this case it may occur that the reader traverses a subtree that's sill being modified (i.e. and incomplete). The cause is that mutableFor() changes t.root immediately and the changes are applied to the new root. The same happens for children derived from mutableChildren() that changes the also n.children[i].
The solution is to delay the change to the original pointer (root or children) until all changes in the subtree are finished.
I prepared a first patch wit the idea, only for t.root: https://github.com/google/btree/compare/master...gallir:cow
If it's correct and you agree I can prepare a patch for children and items if needed.

More info about the proposal.
I'm actually using https://github.com/tidwall/btree fork and implemented the entire idea on it:

The equivalent to what I proposed above: https://github.com/gallir/tidwall.btree/commit/d659c208d5a646cabda77a9804cb314cc8f92cb0

Replaced mutableChildren() for insert and remove: https://github.com/gallir/tidwall.btree/commit/1cae1dd6d7762bbc692a95639e720b18df628e9a

Replaced mutableChildren in growChildAndRemove(): https://github.com/gallir/tidwall.btree/commit/ac1d4aba272c671b9e4d40515c3d00cff8841342

Replaced mutableChildren in maybeSplitChild(): https://github.com/gallir/tidwall.btree/commit/56f9d35a1ed48dc3bf30086234bf8a905908541b

I'm testing it with real data and update from our production system (at dotw.com) and getting a lot less misses during concurrent traversals.
Although during the process I learnt that most of the time the nodes were and are not being reused with the exception of the merge node due to the check of the cow pointer if you do a clone after ever serie of updates. To improve it you have to avoid cloning and by doing it the current mechanism for freeing and reusing don't make too much sense for cases where updates are atomic/mutually exclusive.


Index all the fields on a SourceIdentifier

In the requesting service, we want to be able to find items with a specific SourceIdentifier.  We need to be able to match on all three fields, not just the value (which isn't guaranteed unique).
This patch changes the index config so we'll index all three fields, and will allow us to start querying against them.
For https://github.com/wellcomecollection/catalogue-api/issues/8

What makes it not unique?

If you look in the ID minter table, we key on a combination of (value, identifierType, ontologyType). This means if you search for "value" (either in the table or in the API index), you may find multiple identifiers.
e.g. this is totally possible:
value     | identifierType       | ontologyType
----------+----------------------+--------------
b12345678 | sierra-record-number | Work
b12345678 | mets                 | Work

If you wanted to find, say, (b12345678, sierra-record-number, Work), there's no easy way to do it.

Do you then want this to be a nested field? As you won't be able to do that query here due to object flattening explained above.


No support for vk_ext_debug_utils during instance creation

Template
If you dont understand something just leave it.
If you can provide more detailed information than the template allows for, please ignore the template and present all of your findings.

Version of vulkano: 0.29.0
OS: Ubuntu 20.04
GPU (the selected PhysicalDevice): nVidia RTX 2080
GPU Driver: TODO
Upload of a reasonably minimal complete main.rs file that demonstrates the issue: The triangle example demonstrates it just fine.

Issue
The library supports enabling debug output after the Vulkan instance has been created with code like this...
let debug_report_callback = DebugCallback::new(&instance, MessageSeverity::all(), MessageType::all(), |msg|{
    println!("Debug callback: {:?}", msg.description);
});

However, it doesn't support debugging output during instance creation.  In C/C++ this is accomplished by passing the VkDebugUtilsMessengerCreateInfoEXT type in the pNext chain of the VkInstanceCreateInfo.  See this block of code for an example from the Khronos Vulkan-Samples repository.
Instance creation failing is one of the hardest issues for new developers to deal with because many tutorials and examples simply assume success.

@Rua thanks for the quick turnaround.  However, I had a couple of questions that maybe you can clarify.
First, I don't understand the motivation for supporting an array of DebugUtilsMessengerCreateInfo for the instance creation.  I suppose that someone who is writing a rendering system that uses some kind of plugin architecture might want to allow multiple plugins to each define their own callbacks, but it seems like an esoteric use case.
Second, I assumed the desired flow for a simple use case would be something like
let debug_create_info = ...
let instance = Instance::with_debug_utils_messengers(create_info, [debug_create_info]).unwrap();
let debug_messenger = DebugUtilsMessenger::new(instance.clone(), debug_create_info);

But this approach doesn't work, because passing the debug_create_info on the second line counts as a move and so it can't then be used on the third line.  This one may be a result of my inexperience with Rust and there may be some way around it that I'm not yet fluent enough to understand, but right now I seem to have to create a distinct DebugUtilsMessengerCreateInfo instance for each of the calls.

Vulkan supports multiple messengers, so I figured I might as well make Vulkano support more than one.
You have to create a new DebugUtilsMessengerCreateInfo each time, yes, but it implements Clone so you can make a copy of it pretty straightforwardly. Note that the reference to the debug callback is now in an Arc, so the callback itself can be reused and shared across multiple messengers.

@Rua thanks for the feedback.  I could have sworn I tried clone and got an error about something not being copyable, but it worked just fine when I tried it now.
There's definitely use cases for calling DebugUtilsMessenger::new more than once, but it never even occurred to me that you might want to have more than one callback at instance creation time.  The closest I can find to the spec saying whether multiple instances are valid or not is here.
To capture events that occur while creating or destroying an instance, an application can link a [VkDebugReportCallbackCreateInfoEXT](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/man/html/VkDebugReportCallbackCreateInfoEXT.html) structure or a [VkDebugUtilsMessengerCreateInfoEXT](https://www.khronos.org/registry/vulkan/specs/1.3-extensions/man/html/VkDebugUtilsMessengerCreateInfoEXT.html) structure to the pNext element of the VkInstanceCreateInfo structure given to vkCreateInstance.

Which I regard as ambiguous, even though it uses the singular form, since it also refers to the pNext element of VkInstanceCreateInfo rather than referencing the pNext chain.
My nVidia driver on Ubuntu supports it and calls both callbacks if I provide more than one.  I'll try to find time to try it out on Windows and see if I get the same results.

Note further down:

VUID-VkInstanceCreateInfo-sType-unique
The sType value of each struct in the pNext chain must be unique, with the exception of structures of type VkDebugUtilsMessengerCreateInfoEXT

Well spotted, thanks
On Mon, Apr 18, 2022, 3:09 PM Rua @.***> wrote:

Note further down:
VUID-VkInstanceCreateInfo-sType-unique
The sType value of each struct in the pNext chain must be unique, with
the exception of structures of type VkDebugUtilsMessengerCreateInfoEXT
https://www.khronos.org/registry/vulkan/specs/1.3-extensions/man/html/VkDebugUtilsMessengerCreateInfoEXT.html
—
Reply to this email directly, view it on GitHub
https://github.com/vulkano-rs/vulkano/issues/1872#issuecomment-1101807280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALWNSVYZIJG7RMX56TFLDDVFXMSHANCNFSM5TBMKHJA
.
You are receiving this because you authored the thread.Message ID:
@.***>


trigger rebuilds of packages when one of their build time dependency is rebuilt

When we bump torch from 2.3 to 2.4, there are breaking ABI changes in libtorch. This requires us to rebuild all packages that have a build time dependency on torch like torchvision, vllm etc
We need a way to tell fromager that if a package is being rebuilt, then packages that have a build time dependency on it need to be rebuilt as well. We don't want to do this for all packages since packages like setuptools have frequent releases which would trigger a rebuild of everything

Option 1: add a flag in settings that would indicate that if this package is rebuilt then rebuild all packages that have a build time dependency on it.
Cons:

No clear way to keep build tags in sync for packages that were rebuilt because of some other package
We don't need a rebuild in all cases. For example there might be scenarios where we are updating torch and there is no breaking ABI changes - in this case we don't need to trigger a rebuild of all the other packages that depend on it

One of the goals with using the changelog approach was to keep the config and tag computation simple. I feel like I remember in one of those conversations saying we could just trigger a full rebuild, if we had to, by adding something to the global changelog. Does that still address the problem? How often do we anticipate incorporating changes to a package that require its consumers to be rebuilt, too?

The global changelog will trigger a rebuild of everything. In this scenario we want rebuild only a subset of packages. It hard to say how often we will require the consumers of a package to be rebuilt which is why i am leaning towards option 2 since it allows us to control that

If we're only doing this once in a while, maybe we can live with rebuilding more than is needed? What's the risk of doing nothing at all here?

Our pipelines will most likely timeout and will probably need multiple retries until it builds all of them

If we're only doing this once in a while, maybe we can live with rebuilding more than is needed? What's the risk of doing nothing at all here?

Our pipelines will most likely timeout and will probably need multiple retries until it builds all of them

We can control those timeouts, right?
I don't remember seeing any timeouts when we set up the most recent new release branch downstream, FWIW.

I think @tiran saw some timeouts when we shifted to the new index but yeah we can control that

Your solution would solve the Torch ABI issue. But Torch is not the only package can cause problem. In fact any package with a shared library dependency on any other Python package OR system package can get broken by an update.

I think adding a changelog with rebuild set to true will solve the problem for any such package no?
I think a complete solution would be to combine your idea to detect this issue with the changelog entry solution

One problem with this is properly re-computing the build tag for the dependency on subsequent builds.
Take this sequence:

Initial build of packages A and B. Both packages have build tag 1.
An update to package A triggers a new build of package B. Both packages now have build tag 2.
An update to package C, unrelated to A or B. The build tag for B is computed as 1, because there was no changelog entry for B in step 2.
A second update to package A, again triggering a new build of package B. Package A gets build tag 3, but B's build tag is computed as 2 again (because there is still not a new changelog entry for B) and so the rebuilt package is not uploaded to the index.

A few options to consider:

We could record build tag information in the graph file, but that makes it harder to reproduce a build result from scratch when that build history is not available. Builds are no longer idempotent.
We could, instead, throw an error that package B needs a rebuild but does not have a changelog entry to enforce the build tag calculation in subsequent builds. That feels like it's going to be annoying, so I think I would not want it to be the default.
We could say that the build tag of B is calculated not just from its changelog length, but also include A's. That could become very complex if there are 2 packages that might trigger a rebuild of B and if any of those packages have triggers of their own.
We could add the behavior from suggestion 2 to the linter, instead of the build command. That would allow someone to catch the error much earlier in the process, in a pre-commit CI job.


Subscription error response does not comply with the GraphQL specification

According to the GraphQL specification if an error occurs the response should contain a non-empty errors array.
In case of queries and mutations, this works correctly. E. g. the following response is returned:
{
  "errors": [
    {
      "message": "Internal Server Error(s) while executing query"
    }
  ],
  "data": null
}

However, in case of subscriptions, a single error object is returned:
{
  "error": {
    "message": "Internal Server Error(s) while executing query"
  }
}

This seems to be a violation of specs, and could cause issues for clients that expect a specification-compliant response.
Tested versions: 6.0.1, current (as of commit 0f948f8) master

Just checked this issue again with 7.0.1 (perhaps the same with 6.0.1) from the network log it appears that it does send errors array, but Playground displays it incorrectly?

@BlasiusSecundus Just tested this with GraphiQL and there I see the subscription is really sending the correct response, like you've also confirmed already with the dev console. Not sure if this still happens with Playground, but maybe raise an issue with that project instead?

I'll check again if it can be reproduced with the new, updated Playground.

@BlasiusSecundus Is this still a thing or can we close the issue?

Most likely yes. This test is actually verifying that the correct error message is sent by the server: https://github.com/graphql-java-kickstart/graphql-spring-boot/blob/master/graphql-spring-boot-test/src/test/java/com/graphql/spring/boot/test/GraphQLTestSubscriptionErrorTest.java
Received message from web socket: {"type":"error","id":"2","payload":{"errors":[{"message":"Internal Server Error(s) while executing query","locations":[]}]}}
I have to check Playground.


Issue 274: test if CI accesses secrets on repo forks

Tell us what you do here

[ ] implementing verified source (please link a relevant issue labelled as verified source)
[ ] fixing a bug (please link a relevant bug report)
[ ] improving, documenting, customizing existing source (please link an issue or describe below)
[x] anything else (please link an issue or describe below)

Relevant issue
Reproducing a suspected defect where:

secrets provided in DLT_SECRETS_TOML are not picked up by the CI test runs on forks in both cases:
a) making a PR against the master of my fork
b) making a PR against the master of the dlthub repo
changing a single source causes multiple sources to be tested. Adding a new source, however, only causes a run of the new source

I received the shopify secret and added it to github actions.
This reproduces the issue https://github.com/dlt-hub/verified-sources/issues/247
More PR info
Slack conversation with @rudolfix is already running.

This is an additional test case for the error reproduced in https://github.com/dlt-hub/verified-sources/pull/246

Fixed by https://github.com/dlt-hub/verified-sources/pull/249


Initial creation of codeql.yml

Purpose

Added standard CodeQL for static code analysis

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x] Other... Please describe:
- security - code analysis

Closing as added through tooling


allow client to publish UUID

Signed-off-by: Naiming Shen<EMAIL_ADDRESS>
publish UUID by client, currently for the benefit of diag process.

changed to New Pub/Sub APIs
changed struct name to OnboardingStatus
tried it out on gamma, seems fine.


errors when 'npm install react-codemod'

When I try to install react-codemod via npm, I'm seeing a fatal 'bad object' error:
npm install<EMAIL_ADDRESS>npm ERR! git rev-list -n1 5a5fe8b470e37470744a51678c24ef03b4a8c96b: fatal: bad object 5a5fe8b470e37470744a51678c24ef03b4a8c96b
npm ERR! git rev-list -n1 5a5fe8b470e37470744a51678c24ef03b4a8c96b:
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v7.7.1
npm ERR! npm  v4.1.2
npm ERR! code 128

npm ERR! Command failed: git rev-list -n1 5a5fe8b470e37470744a51678c24ef03b4a8c96b
npm ERR! fatal: bad object 5a5fe8b470e37470744a51678c24ef03b4a8c96b
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

I'm seeing the same error.

FWIW, docs say to clone from GitHub and then npm install deps locally: https://github.com/reactjs/react-codemod#setup--run
This worked for me, after seeing the git rev-list failure trying to install from npm.

See also: https://github.com/reactjs/react-codemod/issues/137#issuecomment-297790305

It's not meant to be installed from npm.
Please follow the usage instructions.

is there any chance we could get npm support?  My tools work better if this was available via npm; since it isn't I'm going to have to jump through some hoops to get this setup to work.

@gaearon

It's not meant to be installed from npm.
Please follow the usage instructions.

It would be helpful to say in the instructions that react-codemod isn't meant to be run locally, only globally. Many tools are capable and supportive of being run locally, but are only documented to be run globally. We shouldn't assume that lack of documentation for local running is the same as statement of non-support.


Fix RTL min. size not triggering text cache update.

Needs testing, might fix #61712

I confirm that this fixes #61712 for me.
There's one minor issue that remains (but might not be related to #61712 in the first place).
In 4.0 alpha 8, the stretch_shrink tooltip for SubViewportContainer looks like this:

And in current master + this PR, it has an extra line at the bottom:

Seems to be working fine.
I can't reproduce the extra new line.

Thanks!
I'll check the newline issue, might be linked to my (joke) editor theme or a different from EDSCALE (I notice the tooltips don't exactly wrap the text as the same place for us).


Darwin: CF-855.17 is broken

hydra.nixos.org has Darwin build errors (such as cabal2nix) because CF is broken in master: http://hydra.nixos.org/build/25570197. Does anyone know what that package is and how it might be possible to fix it?

Being a darwin error is not to be a 15.09 milestone bug.

Are there any benefits fixing darwin stuff on 15.09? As far as I know darwin users just use master branch

Yeah, I haven't noticed much interest in changing it. Also, our Hydra is relatively weak on Darwin platform, so having another branch to build might not go too well.

This issue is really bad for Haskell users on Darwin. cabal2nix won't build because of CF, and neither will stack. It would be great if someone with access to a Mac could take a look at http://hydra.nixos.org/build/25570197 and fix that. @cstrahan, @jwiegley, or @copumpkin maybe?

@copumpkin Knows far more about the Frameworks stuff than I do.

I'll try to take a look this weekend if nobody gets to it first.

This has since been fixed.  See http://hydra.nixos.org/build/27208901, for example.
Close?


Feature/add family flow

Separated economic questions and personal questions. Personal questions are only asked when creating a new family.
Sorted Options in Snapshot Spinner
Created a SelectedFirstSpinnerAdapter class that is used by both the snapshot spinner and the survey questions. Essentially, the selected item will always be first in the place and there can be placeholders enabled)
Made Spinner have default option (says "Select an Option") (Fixes #159)
Made questions all update based off of saved responses (Fixes #143)
Hides back button on survey questions when it's the first question
Added review page that works for economic questions and new family
Fixed problem with scrolling on survey questions when keyboard is up
Fixed problem with size not being adjusted on questions when keyboard is up
Made back button functional

when u touch 32 files but get a quality review on your first try @krconv


Need to implement Files2folders-like native functionality in windows.

Description of the new feature / enhancement
Powertoys need a new, current functionality in Windows 11 contextual menu that allows easy handle of multiple (sometime hundreds) of files. This new option in the contextual menu will mimic and enhance what is seen currently on mac. I am referring to Files2Folders, a right-click shell extension that will automatically create a folder based on the selected filename and move that file into that folder. Files2Folders works in Windows 11, however, the last update was in 2014, it is not resolution-scaling-aware, and it looks outdated. However, it does the job really well.
Scenario when this would be used?
When multiple archives are selected and the user what to move them into one folder, individual folders each, folder them up by extension or date. If you select multiple files, a box will pop up asking for a folder name. That folder name will be created, and all selected files will then be moved into the new folder.
Supporting information
Files intro folder like mac does.
https://www.dcmembers.com/skwire/download/files-2-folder/
https://lifehacker.com/files-2-folder-creates-new-folders-pre-populated-with-5885278

/dup #9269


Add virtual environment to the README setup instructions

Hi,
I had to reinstall openhabian op rpi 3b, so choose the latest version based on debian12.
but now miflora doesn't run as should be.
the error in journalctl -u miflora:
mei 19 19:45:41 domoberry python3[867]: Traceback (most recent call last): mei 19 19:45:41 domoberry python3[867]:   File "/opt/miflora-mqtt-daemon/miflora-mqtt-daemon.py", line 14, in <module> mei 19 19:45:41 domoberry python3[867]:     from unidecode import unidecode mei 19 19:45:41 domoberry python3[867]: ModuleNotFoundError: No module named 'unidecode' mei 19 19:45:41 domoberry systemd[1]: miflora.service: Main process exited, code=exited, status=1/FAILURE mei 19 19:45:41 domoberry systemd[1]: miflora.service: Failed with result 'exit-code'. mei 19 19:45:41 domoberry systemd[1]: Failed to start miflora.service - Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon. mei 19 19:45:41 domoberry systemd[1]: miflora.service: Scheduled restart job, restart counter is at 3. mei 19 19:45:41 domoberry systemd[1]: Stopped miflora.service - Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon.
so I did run : pip3 install -r requirements.txt manualy (as per previous issues) and got:
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Should miflora be installed in a virtual enviroment so it doesn't conflict with any other package?

Hey there! I myself am a big fan of python venvs and would support that change. Could you please provide a PR with the relevant steps in the README? Thanks!

Hi Thom,
This is new to me.
Should I clone your repo, make changes is the readme and create a Pull Request?
The openhabian-config repo should be amended to, is this a separate action, or are taking care of that?

PR #176 for README and #177 for template.service


Better Examples Overview

closes #162

Hello @PhiSpel! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file examples/01b_first_example_obstacle.py:

Line 8:80: E501 line too long (101 > 79 characters)
Line 16:8: W291 trailing whitespace
Line 18:80: E501 line too long (110 > 79 characters)
Line 19:80: E501 line too long (114 > 79 characters)
Line 20:80: E501 line too long (101 > 79 characters)
Line 29:80: E501 line too long (101 > 79 characters)
Line 32:80: E501 line too long (94 > 79 characters)
Line 33:80: E501 line too long (130 > 79 characters)
Line 35:80: E501 line too long (92 > 79 characters)
Line 44:80: E501 line too long (118 > 79 characters)
Line 44:119: W291 trailing whitespace
Line 53:80: E501 line too long (118 > 79 characters)
Line 54:80: E501 line too long (91 > 79 characters)
Line 55:80: E501 line too long (82 > 79 characters)
Line 63:80: E501 line too long (96 > 79 characters)
Line 68:80: E501 line too long (85 > 79 characters)
Line 69:80: E501 line too long (94 > 79 characters)
Line 71:80: E501 line too long (110 > 79 characters)
Line 73:80: E501 line too long (98 > 79 characters)
Line 76:80: E501 line too long (134 > 79 characters)
Line 79:80: E501 line too long (86 > 79 characters)
Line 83:80: E501 line too long (101 > 79 characters)
Line 84:80: E501 line too long (108 > 79 characters)

In the file examples/02_converging_flow.py:

Line 7:80: E501 line too long (82 > 79 characters)
Line 19:80: E501 line too long (101 > 79 characters)
Line 30:80: E501 line too long (96 > 79 characters)
Line 32:80: E501 line too long (98 > 79 characters)
Line 35:80: E501 line too long (111 > 79 characters)
Line 38:80: E501 line too long (83 > 79 characters)
Line 41:80: E501 line too long (113 > 79 characters)
Line 44:13: E702 multiple statements on one line (semicolon)
Line 46:7: E702 multiple statements on one line (semicolon)
Line 46:14: E702 multiple statements on one line (semicolon)
Line 47:15: E702 multiple statements on one line (semicolon)
Line 53:80: E501 line too long (128 > 79 characters)
Line 58:80: E501 line too long (105 > 79 characters)
Line 61:80: E501 line too long (80 > 79 characters)

This PR is now part of #200


IoTEdge 1.4 LTS TLS certificate configuration

Dear IoTEdge team,
I have followed the guide of this Link:
https://learn.microsoft.com/en-us/azure/iot-edge/how-to-manage-device-certificates?view=iotedge-1.4&tabs=windows
And I have noticed that the /var/aziot folder is by default created with 750 permissions.
This cause the IoTEdge runtime to fail. Services are not rebooted and docker containers not activated.
I changed the permissions to 755 for the following folders:
/var/aziot
/var/aziot/certs
/var/aziot/secrets
Because I've performed these commands:
sudo mkdir /var/aziot/certs -p
sudo mkdir /var/aziot/secrets -p

and the parent folder /var/aziot was not present (-p option).
Certificates have file permissions like the one listed in the official documentation.
I've experienced this with all the 1.4.x versions of EFLOW on Windows Server 2019/2022.
Is it right to use 755 permissions on the mentioned folders?
If yes, my suggestion is to update the documentation in order to avoid the failure of the runtime.
Thank you for helping!
Alberto S.

What error do you see? Is it similar to this? https://github.com/MicrosoftDocs/azure-docs/issues/102589#issuecomment-1350223722

@micahl Thank you!
@jlian Yes it is similar. The problem is that the official guide is not mentioning that these folders:
/var/aziot
/var/aziot/certs
/var/aziot/secrets

needs 755 permissions. Certificates permissions are fine, but by default the permissions on the above directory are not enough (750 is making the runtime failing).
This is my current situation:

after creating this:
sudo mkdir /var/aziot/certs -p
sudo mkdir /var/aziot/secrets -p

I have changed the permissions to 755 on all these three directories:
/var/aziot
/var/aziot/certs
/var/aziot/secrets

I have noticed that in the other issue that you have mentioned, the ownership of the above directories is different. Maybe this is the problem?
Thank you!

@jlian
I've tested this: https://github.com/MicrosoftDocs/azure-docs/issues/102589#issuecomment-1352232066
And now it is working.
I think that this:  https://github.com/MicrosoftDocs/azure-docs/issues/102589#issuecomment-1352232066
is the solution so we can close this issue.
Thanks a lot!

Hi @sitaalbeMarp,
Glad you were able to fix your issue. Thanks to @jlian and @micahl
Thanks,
Francisco

To summarize, your problem was fixed once you did the chown?

FYI the docs update for permissions are now done
https://learn.microsoft.com/azure/iot-edge/how-to-manage-device-certificates#permission-requirements
Thanks @PatAltimore

@jlian, @PatAltimore
Thank you!


Atom selection not synchronized when clicking on the 3D representation

The selection state isn't always synced up between the 2d, 3d and text displays.
Here's a gif illustrating some of this: (generated with mol = mdt.from_name('caffeine'); mol.draw())

There are 3 specific symptoms here:

After deselecting all atoms, the text display continues to show the last selected atom
The 2D selections usually aren't getting updated along with the 3D
Every time I select an atom in 3D, the 2D representation jumps a little a bit

Some notes:
For point 1, that was due to a bug in ipywidgets (https://github.com/ipython/ipywidgets/issues/738) that I should have fixed.  I need to make sure that the fix got released and that it does fix this problem.
Point 2 I'll have to look into using this molecule.  I have occasionally seen specific atoms that just don't ever show up as selected in 2D, maybe this has to do with that.
Point 3 has been haunting me for awhile...  I think this is another reason to move off of D3.

@avirshup Regarding point 1, I just confirmed that it is fixed when using ipywidgets v6.0.0b1.  What's the process for upgrading us, just changing requirements.txt both here and in mdt?  Or do we not want to upgrade until it's out of beta?

Yeah, requirements.txt is is the only thing to change for now. I'll be merging in some preliminary conda environment.yml files, which will complicate matters, but we can worry about those later.
I'm certainly fine with the dev version having dependencies on a beta ipywidgets, although I'm less comfortable with having a beta dependency in the next stable release.
(BTW, when this nbmolviz next gets released, I think it's worth AT LEAST a bump to 0.7, given how much it's been improved :) )

Alright that sounds reasonable.  I've been putting it off, but I think it looks pretty broken when the last atom doesn't deselect.  I'll go ahead and do PRs for upgrading those and hope that the ipywidgets people get it stable before we next want to release.

Point 2 fix is here: https://github.com/Autodesk/molecule-2d-for-react/pull/17

Point 1 fixed in two PRs:
https://github.com/Autodesk/notebook-molecular-visualization/pull/37
https://github.com/Autodesk/molecular-design-toolkit/pull/114

@avirshup The fixes for 1 and 2 are merged.  Do you mind if I close this issue and create a new one for fixing the "jumpiness", probably by moving off of D3?

@justinmc - sounds good; just tested everything and it's working well!
And yeah, the D3 issue is not nearly as important as the other two, so feel free to close this one.

This issue will track the D3 jump: https://github.com/Autodesk/molecule-2d-for-react/issues/9


Add example for multiple plugin instances

Added a example use case of multiple plugin instances in README.md.

Thanks