InvalidParameterValueException - Getting this for various rules

Deployed this into an AWS Govcloud account.
module "managed-config-rules" {
  source  = "niaid/managed-config-rules/aws"
  version = "2.1.0"

  rule_packs = [
    "Operational-Best-Practices-for-NIST-800-53-rev-4",
  ]

  rules_to_exclude = [
    "rds-in-backup-plan",
    "multi-region-cloudtrail-enabled",
    "root-account-mfa-enabled",
    "ec2-instance-managed-by-systems-manager",
    "root-account-hardware-mfa-enabled",
    "cloudtrail-enabled",
    "ec2-instances-in-vpc",
    "restricted-common-ports",
    "restricted-ssh"
  ]
}

If I uncomment those rules in the rules_to_exclude I get errors relating to them.  Example below.
╷
│ Error: reading ConfigService Config Rule (rds-in-backup-plan): couldn't find resource
│
│   with module.managed-config-rules.module.account[0].aws_config_config_rule.rule["rds-in-backup-plan"],
│   on .terraform/modules/managed-config-rules/modules/account/main.tf line 1, in resource "aws_config_config_rule" "rule":
│    1: resource "aws_config_config_rule" "rule" {
│
╵
╷
│ Error: putting ConfigService Config Rule (multi-region-cloudtrail-enabled): operation error Config Service: PutConfigRule, https response error StatusCode: 400, RequestID: 761425bf-177f-412e-8674-3091e908aff4, InvalidParameterValueException: The sourceIdentifier MULTI_REGION_CLOUDTRAIL_ENABLED is invalid. Please refer to the documentation for a list of valid sourceIdentifiers that can be used when AWS is the Owner.
│
│   with module.managed-config-rules.module.account[0].aws_config_config_rule.rule["multi-region-cloudtrail-enabled"],
│   on .terraform/modules/managed-config-rules/modules/account/main.tf line 1, in resource "aws_config_config_rule" "rule":
│    1: resource "aws_config_config_rule" "rule" {
│
╵

That output is from Atlantis, so the formatting from it is a bit wonky.

Hi, @jseiser! Thanks for bringing this to our attention. We're working on a fix in this PR: https://github.com/niaid/terraform-aws-managed-config-rules/pull/48

Hello again. The latest 2.1.1 release should fix the errors you're seeing. Please try bumping the module version and let me know if that works.

Sorry for the late reply, the new version worked.


migrated some enemy logic

migrated some enemy stuff to enemydatamanager (bad name but idc anymore)
redid like all the enemyspawnmanager logic so its dynamic and doesnt force me to write everything myself this all makes it like way more inefficient lowk but its ok cuz now i can add new enemies easier

honestly this wasnt even needed. its just the changing stuff to dynamic that was needed. might migrate back to  enemyspawnmanager later


Port Ozzie to Inertia

Technologies used:

Inertiajs
Vue3
TypeScript

Improvements to Markdown Parsing

Integration of GitHubs own API for markdown parsing has solved some of the markdown rendering bugs that existed prior.
Also, we can now bask in the glory of proper syntax highlighting in fenced code blocks 🎨 .

Individual project page

Clicking the repository name on the dashboard no longer scrolls to the project. Instead, a new 'repository page' opens.
UI has been tidied up (in my opinion 🙈 ).
The external icon has been replaced with the actual GitHub Icon.

PR View
The modal has been replaced with a page that anchors the PR in the context of its parent project. Notice the top of the page uses the same UI elements as the project page. With Inertia this means the transition between project page and PR and back again is slick.

Issue View 🔥

Finally, you can now view issue descriptions from within Ozzie.
Again, notice the re-use of UI elements.

Page Caching
All the pages are cached after initial render to improve performance. This is important since markdown is parsed using the GitHub API so we only want to call it once.
The cache is cleared when stats are fectched.

Thanks so much @jonsugar!


KubeService liveness/readiness probes

BREAKING: I'm going to look at enhancing the KubeService to optionally write some kind of readiness file to disk that a Kubernetes probe script could examine to determine the worker health. In theory, this will have to work on all platforms (Windows, Linux, and OS/X) as well as for unit testing.
I believe the best way will be to have the service developer enable this by passing the the fully qualified path to the status file as the new optional statusFilePath parameter to the KubeService constructor.  By default, this will be NULL, indicating that no file should be created.
You'll need to code your health probe to examine this file.  If the file doesn't exist, your probe should assume that the service hasn't been started yet.  If the status file does exist, it will have one of the following text values with no line ending characters:
not-started
starting
running
unhealthy
terminated

Note that there's one related breaking change: KubeService.SetRunning() has is now async and has been renamed to SetRunningAsync().  You'll need to update your services,

Implemented for: v2.0.0


Simple Slab Land

Dry heat advection-diffusion equation in an atmospheric single stack coupled to a prognostic surface temperature equation reflecting a slab land. Dry setup. This case is mainly for software design before implementing more complex cases.
Design: https://github.com/CliMA/CouplerMachine/blob/ln/slabland/experiments/SlabLand/README.md
Conservation tests: under the 16 June section

it seems like a lot of the files in this PR are not specific to the slab land experiment, and looks like some are already in the repo (e.g. utilities/sphere_utils).

it seems like a lot of the files in this PR are not specific to the slab land experiment, and looks like some are already in the repo (e.g. utilities/sphere_utils, grid stuff, numerics (filters...), even physics). maybe can be reorganized to have a single copy of these files?

Good point. These are copied from the RQA interface. We are keeping these folders under each example separate, because the RQA interface was evolving as we were writing these different test cases, so we wanted to have a stable backend for each case. Once the Aleph.jl repo/module (where the RQA code will live) is ready though, we will import these files from there.


Are we supposed to use firebase in this process?

I am not sure if we should use firebase, as it would create a new functions folder with another index.js file. What should we put in this file?

Hey @mdmjg - Any NodeJS runtime will work with this module (including firebase functions!).
All you would need to do is follow the process you've currently followed, generating a sample function (index.js).
Once this is done, structure your function as according to this example
https://github.com/jthegedus/firebase-gcp-examples/tree/master/firebase-functions-express
That shows how to use Express with Firebase Functions. Once this is done, follow the "Demo" folder/ Readme.md of this project to integrate the module with the express server setup on the function.
Hope this helps!
(Closing this as it's sort of out of the scope of this module)


Null reference exception in Escaping.escape

  System.NullReferenceException: Object reference not set to an instance of an object
  at<EMAIL_ADDRESS>(System.Collections.Generic.IEnumerable`1[System.Char]& next) [0x00028] in Chiron.fs:401
  at Microsoft.FSharp.Core.CompilerServices.GeneratedSequenceBase`1[T].MoveNextImpl () [0x00017] in /private/tmp/mono--fsharp-20170301-46369-1vnanly/src/fsharp/FSharp.Core/seq.fs:781
  at Microsoft.FSharp.Core.CompilerServices.GeneratedSequenceBase`1[T].System-Collections-IEnumerator-MoveNext () [0x00000] in /private/tmp/mono--fsharp-20170301-46369-1vnanly/src/fsharp/FSharp.Core/seq.fs:812
  at Microsoft.FSharp.Collections.SeqModule.ToList[T] (System.Collections.Generic.IEnumerable`1[T] source) [0x00000] in /private/tmp/mono--fsharp-20170301-46369-1vnanly/src/fsharp/FSharp.Core/seq.fs:559
  at Chiron+Escaping.escape (System.String s) [0x00010] in <58e26eef7a9f4a1fa7450383ef6ee258>:0
  at Chiron+Formatting.formatString (System.String _arg7) [0x00000] in Chiron.fs:692
  at Chiron+Formatting.formatJson (System.Int32 level, Chiron+Formatting+JsonFormattingOptions options, Chiron+Json _arg1) [0x00082] in Chiron.fs:661

For the last release, unknown tag.
Repro:
Object (Map [("key", String null)]) |> Json.serialize

The internal type escape@401-1 exists in Chiron 6.2.0. Upgrading to 6.2.1 should solve this issue along with #64.

Testing...

No, I'm already using Chiron 6.2.1

Then the stack trace is suspect. escape@401-1 does not exist in Chiron 6.2.1.

Well, that's because there are no tags on this repo and I took an arbitrary commit to get some sort of debug symbols... :-s

Does the repro fail for you?

I just tried pdb2mdb with this result:
$ xbuild /t:Rebuild ... fsproj && mono --debug ...exe
Symbol file Tests/bin/Debug/Chiron.dll.mdb doesn't match image Tests/bin/Debug/Chiron.dll

On Windows, I have no issues with a build from clean. I'll have to see if I can get a mono build going this evening.

Did you see it? :)

As a little hack, I wrote this:
type Json with
    static member WriteCaringForNull (key: string) value =
        json {
            if isNull value
            then do! Json.writeNone key
            else do! Json.write key value
        }


Add spring test support for CallActivity mocking

Following code is not working for Spring tests:
CallActivityMock deployFlowMock = ProcessExpressions.registerCallActivityMock(testDeployFlow).onExecutionAddVariable("var", "val");         deployFlowMock.deploy(processEngine);
As I think it happens because of using different contexts for mocks. I went deep to the mocking code and saw that all stubs are registered with Mocks.register(name, instance); and it puts into static ThreadLocal map. But Spring doesn't see this things.
Could you provide an API which will register mocks depends on current context (which we can define with annotation, for example)?

Since I also think this would be a very useful feature, I hat a take at this. My intermediate result is in https://github.com/fml2/camunda-bpm-mockito/tree/feature/Mock-CallActivity-in-Spring-context.
Please gurus look at this and tell me whther the approach is a promising one.
For now, I can't figure out how to get a SingletonBeanRegistry (used in my class) given an ApplicationContext (usually available in a spring based test).

I appreciate your contribution. Unfortunately, I was having trouble reviewing this ... I am locally not able to build this ... I guess this is some problem on my machine, please give me a day or two to fix this.

Have you had a chance to look at this?


AppItemID unmarshal error in production

in production appstore return "app_item_id":"xxx"

Appstore returns app_item_id as number on my environment.
Both sandbox and production.
Is your receipt type for iOS7 or above?
Does anyone get same error?

this issue was resolved by #29
so i close this.


Tomcat 7 / CentOS 7 fails to install

Created a base CentOS7 box, set the base version to Tomcat 7:
 node.default['tomcat']['base_version'] = '7'
 include_recipe 'tomcat'

Get this error about Tomcat 6 (why 6? why is it trying to install Tomcat 6)?
   Recipe: tomcat::default

       * No candidate version available for tomcat6
       ================================================================================
       Error executing action `install` on resource 'yum_package[tomcat6]'
       ================================================================================

       Chef::Exceptions::Package
       -------------------------
       No candidate version available for tomcat6

       Resource Declaration:
       ---------------------
       # In /tmp/kitchen/cache/cookbooks/tomcat/recipes/default.rb

        31:   package pkg do
        32:     action :install
        33:   end
        34: end

       Compiled Resource:
       ------------------
       # Declared in /tmp/kitchen/cache/cookbooks/tomcat/recipes/default.rb:31:in `block in from_file'

       yum_package("tomcat6") do
         action [:install]
         retries 0
         retry_delay 2
         default_guard_interpreter :default
         package_name "tomcat6"
         timeout 900
         flush_cache {:before=>false, :after=>false}
         declared_type :package
         cookbook_name "tomcat"
         recipe_name "default"
       end

   Running handlers:
   [2015-06-01T21:25:19+00:00] ERROR: Running exception handlers
   Running handlers complete

I looked at your code and tried to hack it to install only Tomcat 7:
  node.default['tomcat']['packages'] = ["tomcat7"]

but it gave me a similar error:
       No candidate version available for tomcat7

I have the same issue in Ubuntu 14.04, tried to override and still wants to install tomcat6 instead of 7.

This cookbook does not appear to be "role/wrapper cookbook"-friendly. In my testing, I had to eschew my wrapper cookbook methodology only for Tomcat and instead set the version in my environment attributes file for Chef Zero.

This sounds to me like an issue with the attribute precedence... It sounds like it could be resolved by setting your attribute in the wrapper cookbook with a higher precedence??
Could you try using normal or override instead of default ?
You can find more info on this here

I did try the override. It just doesn't work :S I end up writing my own :)
Thanks!

:)
I remember I was also struggling back when I first tried to use this (and other) cookbooks, but I can't say for sure what I'd tried...
It's now working for me with the override in an environment.
Not sure if that's suitable for your scenario?

digging a little further into the issues, I see that this very same issue also appears in #102 - and it's actually very well documented there .
The problem / solutions are explained perfectly in this article.
I would argue there's not much we can do apart from clearly documenting this in the README.md , so that ppl know to use a role / environment vs. overriding the attributes (e.g. if you override base_version, which seems to be the most common case, you should make sure to override all the others deriving from it).
another option could be to replace usages of the derived attributes where we read the value, with:

inlined value (i.e. instead node['tomcat']['config_dir'], use sth like "/etc/tomcat#{node['tomcat']['base_version']}")
a function that contains the logic, so it would compute the value every time

First off I'm very sorry that it's taken so long to get back to you on this issue.  For a significant period of time there was no active Chef Software Inc. maintainer for this repository and things languished.  We're now actively maintaining this cookbook again, and as part of that I've rewritten the cookbook with new custom resources for installing Tomcat from Apache Org sources.  This will ship in an upcoming 2.0 release and then we'll remove the existing recipes and providers in a future 3.X release.  With those new providers I believe the need for this change goes away so I'm going to close this out.  I encourage you to give the new providers a try and let me know if we can tackle more Tomcat management without the attributes bloat the current code suffers from.  They're on the master branch and once the documentation and testing improves a bit they'll be released as a 2.0 cookbook.


New release: v0.10.0 Wolfram Warptangent

Downloads still point to <IP_ADDRESS> Hydrogen Helix.
x86 builds for Linux/OSX in https://github.com/monero-project/monero/releases are not ready or not uploaded yet.
Ticketing for housekeeping.

Resolved. Thanks @fluffypony.


[WIP] Add ClientRequestContext.serviceRequestContext

Motivation:
When a user writes a service that invokes a request using an Armeria client, the client cannot access the ServiceRequestContext.
This can cause various unexpected behaviors and hard to spot.
Modifications

Add ClientRequestContext.serviceRequestContext()

When the methods hasAttr() and attr() are called, the ClientRequestContext looks for the ServiceRequestContext if it doesn't have the attribute.
attrs() returns the combined iterator of ClientRequestContext and ServiceRequestContext.

Result:

You can get the ServiceRequestContext of a service that invokes the client's request and its attributes without copying.
Close #1083

I have two issues to solve:

The ServiceRequestContext is inserted when a ClientRequestContext is created if the thread has the ServiceRequestContext in its thread-local.

It's because I wanted to make the field final so we don't have to worry much about thread-safety.
However, this will make the ClientRequestContext has its ServiceRequestContext forever when even the context is popped out.

The Attribute returned from the ClientRequestContext.attr() can change the value of the Attribute in ServiceRequestcontext.

I'm not sure if we need to make only gettable.

I'm wondering if we need to make it only gettable.

Perhaps we should set the attribute at ClientRequestContext? We will have to change AttributMap implementation a little bit for this though.

This is ready. 😉

All fixed. PTAL 🙇

@trustin All fixed. 🙇

Yes, let me wrap the Attribute from the root using attr() and attrs(), so that a new value for the Attribute is set only to the current map, not the root. Thanks!

Let me squash commits to resolve conflicting. 🙏

All fixed. PTAL. 🙇

All fixed. 😉

This is ready for the another round. 😉

@anuraaga Would you mind taking a look at this again? 😄

Thanks a lot @anuraaga, @ikhoon and @trustin for reviewing. 😉

I had a random finding - should we return root for ServiceRequestContext.current if it's available?
https://github.com/line/armeria/blob/master/core/src/main/java/com/linecorp/armeria/server/ServiceRequestContext.java#L70
I'm not entirely sure but I think it might be appropriate, the root is still active even though it's shadowed by a client context.

should we return root for ServiceRequestContext.current if it's available?

Yes, I agree. Let me make a PR for that. Thanks!


Be more inclusive with gender, add pronouns

https://github.com/hackumass/hackathon-dashboard/blob/0f259585496ea55313223ba35bc69df2679a828a/app/views/event_applications/_form.html.erb#L48
Open to other suggestions, but would suggest adding a non-binary option. I think we should also add another question in the form for preferred pronouns, and propagate that through the UI and maybe even include it on badges that we print out for participants.

Done.


Registry v2 manifest api does not give last_update data

The registry v1 had last_update attribute on a tag which allowed easily to check when the image was uploaded/updated. V2 doesn't seem to have this. This request is for implementing such last_update timestamp to the manifest api.

@garo What is your use case for this feature?  It's unlikely that this will be added to the manifest specification.

@RichardScothern We have a docker orchestration service which is used to deploy our containers. The tools allows a developer to commit a new version from an image to production and while doing that, it would display when the image was last updated.
This worked really well with the v1 registry as we could get that data, but now I can only determine if an image exists, but as far as I know, I can't get any history when that image was created from the registry itself.
To show an example, the tool displays this kind of information when a user is about to deploy a newer version:

Previous revision: a2b8d7c9b23788da3d94a5e51d1f8025afa98d0e
The container 2fe7fd8adceefac1bfb874f8848cbdef6326e20b you are about to deploy was last updated at 18h42m37.17792401s ago

The only method this information is available in the v2 registry is via the notification API.  You could consume that and store the timestamp somewhere.  Unfortunately that's the best I can offer.


Issue 1199: Remove the vestigal traces of custom memory allocators, part 1, updated

memry removal.

This should be no-brainer. These functions never seemed to do anything useful. The only oddity was with alloc_string which rounded the allocation upwards to nearest multiple of 4. Based on my review of code, I could not identify any value in this feature, so even alloc_string was simply transformed to malloc.
memry.* are removed. All code is adjusted to simply call malloc and free instead.
listio.* are removed. The list reading function in these files appears to have been unused, and contained the only invocation of strsave define, which was one of the alloc_string users, so I removed both of them.
https://code.google.com/p/tesseract-ocr/issues/detail?id=1199

Archive copy of issue (but full text is included above): https://web.archive.org/web/20151128081631/http://code.google.com/p/tesseract-ocr/issues/detail?id=1199

I'm not sure about the alloc_string() removal. The other things seem fine.

@zdenop, please close this PR.


modify z control build shell

please meanwhile update cgminer-openwrt-packages/cgminer/data/config.avalon7.actrlboard file.

@yangjun2017 Thanks. We add a new target profile now.


Pub get flutter_test version solving failed on Beta 1.17.0-3.4.pre

I just updated path in my project because I needed the latest one and I get this error
Because every version of flutter_test from sdk depends on path 1.6.4 and yaip depends on path ^1.7.0, flutter_test from sdk is forbidden.
I started trying out and preparing my project on Beta to get ready to go live to Playstore. Now I read from here https://www.gitmemory.com/issue/flutter/flutter/55453/618436399 that its been updated on master and dev channels but not on beta and stable channels. Kindly updated it on the remain channels as well so that I don't have to downgrade my path version as I really need the latest.

Hi @MichaelSowah
Can you please post your pubspec.yaml?
This works fine on beta channel
environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  path: ^1.7.0

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.3

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter doctor -v
[✓] Flutter (Channel beta, v1.17.0-3.4.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.17.0-3.4.pre at /Users/taha/Code/flutter_beta
    • Framework revision e6b34c2b5c (2 days ago), 2020-05-02 11:39:18 -0700
    • Engine revision 540786dd51
    • Dart version 2.8.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.1

[✓] Connected device (4 available)
    • SM M305F            • 32003c30dc19668f • android-arm64  • Android 10 (API
      29)
    • AOSP on IA Emulator • emulator-5554    • android-x86    • Android 9 (API
      28) (emulator)
    • Chrome              • chrome           • web-javascript • Google Chrome
      81.0.4044.129
    • Web Server          • web-server       • web-javascript • Flutter Tools

• No issues found!
taha@MacBook-Pro And

Thank you

environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
http: ^0.12.1
flutter_svg: ^0.17.4
cached_network_image: ^2.2.0
sembast: ^2.4.3
path: ^1.7.0
path_provider: ^1.6.7
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.3
dev_dependencies:
flutter_test:
sdk: flutter

environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
http: ^0.12.1
flutter_svg: ^0.17.4
cached_network_image: ^2.2.0
sembast: ^2.4.3
path: ^1.7.0
path_provider: ^1.6.7
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.3
dev_dependencies:
flutter_test:
sdk: flutter

@TahaTesser
this is my
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
http: ^0.12.1
flutter_svg: ^0.17.4
cached_network_image: ^2.2.0
sembast: ^2.4.3
path: ^1.7.0
path_provider: ^1.6.7
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.3
dev_dependencies:
flutter_test:
sdk: flutter

Hi @MichaelSowah
Please add dependency_overrides move path to dependency_overrides and it should solve the issue
dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.3
  http: ^0.12.1
  flutter_svg: ^0.17.4
  cached_network_image: ^2.2.0
  sembast: ^2.4.3
  path: ^1.7.0
  path_provider: ^1.6.7

dependency_overrides:
  path:

dev_dependencies:
  flutter_test:
    sdk: flutter

The updated version will be present on stable and beta channels when it is ready. Closing as this is not a bug.


chromadb fails to install on windows 10 and python 3.9

`Building wheels for collected packages: hnswlib
Building wheel for hnswlib (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for hnswlib (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [5 lines of output]
running bdist_wheel
running build
running build_ext
building 'hnswlib' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for hnswlib
Failed to build hnswlib
ERROR: Could not build wheels for hnswlib, which is required to install pyproject.toml-based projects`
I have also install the latest Microsoft Visual C++ redistributions but it is still giving the error

install python3.9 dev and install again,

don't it work on windows because on my friend's system with same specification it is working.

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two

In your case, you should choose Windows 10 SDK

I'm a little confused. The issue opened is about running on Windows 10 and the suggested fix is installing the SDK for Windows 11.
I have ran in to this erropr multiple times and I am still yet to find a solution🙈
Could anyone advise?

The above fixes still dont work for me.
This code will be the last of me!!😡

You mad?

@HoiDam please be kind. It does sound frustrating.

@HoiDam please be kind. It does sound frustrating.

Yaaa. But it works in my machine

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

this really worked for me. Thanks a lot!!! :)

Yes, this solved my exact same problem. thanks.

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

It worked on my windows machine too!

what to do after installing these files

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

It worked on my windows machine too!

Please, where can I navigate and find the  "Individual components" ??
Thanks.

HHAHAHAHHAHAHAHA

Interesting

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

Thanks a lot for this.
It worked perfectly :)

This works for me as well. Thank you.

Ok got it.... so a long winded solution for my use case but here it goes:

download https://visualstudio.microsoft.com/visual-cpp-build-tools/

however you have to navigate to "Individual components", find select those that were called out above:

finish the install

reboot computer

Then did a !pip install chromadb==0.3.26 selecting this specific version which worked for me

Solutions I tried but didn't work for me, however worked for others:

!pip install wheel

!pip install --upgrade setuptools

The solution worked for me too :)

For those who are looking for where to find individual components, you will have to click on "Download Build Tools"  as shown in the snapshot attached. Install the .exe file and you will see a window that pops up with a tab called "Individual components"

I still couldn't install chromadb after downloading and installing build tools. However, here is what worked for me in steps below:
I had lots of problems installing chromadb but I finally installed it today using a pip command.
Here is what worked for me:
1-	In VS, go to Tools>Get Tools and Features.

2-	Under workloads, make sure Desktop development with C++ is installed.

3-	Create a conda Virtual Environment and choose Python version 3.10. You can do it the Anaconda Command prompt using the following command: conda create -n env-01 python 3.10
4-	In Anaconda Prompt, make sure you are in the project directory where you installed the environment and type: conda activate env-01
5-	Try pip install chromadb
If it works, then you can use this environment for your project in Visual Studio Code.
Some references about setting up environments in Visual Studio Code.
https://code.visualstudio.com/docs/python/environments

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

Thanks my friend, it worked very well

Hi,
I tried and installed my machined VC++ and checked control panel - >program & features.
After i tried to install chromadb then system throw same error

I think my path not taking VC++ redistributable pakage at that time of compiling.
Kindly help me out

The above fixes still dont work for me.
This code will be the last of me!!😡

I can feel you man.

I have installed sdk 11 and msvc too but it still shows this
      error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\VC\\Tools\\MSVC\\14.38.33130\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for typed-ast
Failed to build Pillow typed-ast
ERROR: Could not build wheels for Pillow, typed-ast, which is required to install pyproject.toml-based projects

this is the question stackoverflow:
Link
i'm using python 3.11.

I tried above solution but it isn't working for me. I am using Windows 10 and Python 3.9

I've met the same issue on Windows 11 Python 3.11.8
Solution:

Install Python 3.10
py -3.10 -m pip install chromadb

Had the same issue. Reinstalling MSVC didn't work.
I was trying to install chromadb on a Python 3.12 environment.
The main issue comes from installing the dependency hnswlib  but was not able to find a solution.
I rebuilt the environment with Python 3.10 and it works just fine.

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

Thanks a lot for this.
It worked perfectly :)

What is i am using Windows 10? should i install windows 11 SDK in any case?

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

Thanks a lot for this.
It worked perfectly :)

What is i am using Windows 10? should i install windows 11 SDK in any case?

It looks like the answer your question is in the message you replied to.

In your case, you should choose Windows 10 SDK

Thanks a lot for the solution solved the build issue with ChromaDB installation!

i tried every possible ways but i couldnt resolve this issue. I was trying to install dependencies for localGPT. Please  share any solutions for this.

Same issue here, I just gave up and installed on WSL, worked perfectly.

The solution proposed above works for me too. Thanks

You need to download https://visualstudio.microsoft.com/visual-cpp-build-tools/ first.
Next, navigate to "Individual components", find these two
In your case, you should choose Windows 10 SDK

This Steps Are work for me in windows 11


Checking equality of geometries

when cloning geometries, shape is wrong

from ccpi.framework import ImageGeometry, AcquisitionGeometry
import numpy as np

ig1 = ImageGeometry(3,4)
ig1_cl = ig1.clone()

print(ig1.shape)
print(ig1_cl.shape)

The following lines should change:

for Imagegeometry here
self.shape = tuple(order) to self.shape = shape

same here.
Then, to check if two geometries are equal: an __eq__ method as
def __eq__(geom1, geom2):

    dict1 = geom1.__dict__
    dict2 = geom2.__dict__
    flag = True
    for k1, k2 in zip(dict1.items(), dict2.items()):
        if k1!=k2:
#            flag = False
#    return flag
#            print('{} is not equal with {}'.format(k1, k2))
            raise ValueError('Geometries are not equal: {} is not equal with {}'.format(k1,k2))

check of geometries is done in BlockOperator and it's done rather brutally in colum_wise_compatible and row_wise_compatible by checking the geometry object dictionary.
It actually doesn't work with SIRF objects.


Incorrect version of some dotnet tools in release/3.1

Similar to https://github.com/dotnet/source-build/issues/1876, this issue exists in release/3.1 as well.  See SDK diff here: https://gist.github.com/dseefeld/4a005f6efd54848b2c44a41252a94d7b

3.1 is EOL in two months.  This issue is obsolete.


Fix usage of Enum as constant

Set reduced_value so that Enums can be properly used as constants.
The value is Dictionary (code for its creation is from GDScriptCompiler::_populate_class_members, just moved to GDScriptAnalyzer::resolve_class_member). Saved it in new EnumNode::dictionary property so that compiler uses the same one.
Also fixed that outer Enums were not considered constants - there should be no difference. It also should not matter if an enum is accessed directly, through instance or through class, so removed if clause in reduce_identifier_from_base.
While at it I saw that case for GDScriptParser::ClassNode::Member::ENUM: was the only one that was not having StringName name variable for readability, fixed that inconsistent injustice.
Fixes #54018.
Fixes #70213 (continuation from  #70220).
Fixes #70495.

I really like this solution a lot! Make sense to me! It's much smarter & should supersede #70569, so I'll close that!

Well, there are other tests that do have that. Like that one that even has recursive things. And it passes.
But if you have any specific snippets of code for the test - write me in chat and I'll add it.

I tested this PR, it works great with other scripts, with inner classes (different levels of nesting), with local constants. Perhaps these cases should also be added to the tests in order to fix these features and reduce the likelihood of regressions.
The only issue I've found is that assigning an enum to a variable doesn't raise an error/warning and doesn't convert the enum to a dictionary. As a result, the behavior is a little strange.
extends Node

func _ready() -> void:
    const E = MyClass.MyEnum
    var e := MyClass.MyEnum
    e = {1: 2, 3: 4}

    print(E) # { "VALUE_A": 0, "VALUE_B": 1, "VALUE_C": 2 }
    print(e) # { 1: 2, 3: 4 }

    const C1 = E.VALUE_A
    const C2 = e.VALUE_A # !!!

    print(C1) # 0
    print(C2) # 0

Thank you for that @dalexeev!
Hmm, that last example does raise some interesting points. There are lots of places where enums are implicitly considered to be dictionaries, but if we reduce them to that too early, there's a chance that we lose the "enum-ness" of them. So perhaps we really do need to check whether a variable is a meta-type more often, and convert to dictionary mostly at the end?

Strange I cannot reproduce const C2 = e.VALUE_A - I do get correct error about it being non-constant expression.
As for Cannot use enum constant as type hint. - important omitted part: local constant. So this is an issue, but a separate one about lookup.

So perhaps we really do need to check whether a variable is a meta-type more often, and convert to dictionary mostly at the end?

The difficulty resides in the fact that constants need a reduced_value to work properly. Not giving it soon enough makes the engine crash.

I think what I was getting at is that a lot of checks maybe shouldn't just be p_node->is_constant or p_node->get_datatype().is_constant, they should be split into
  if (p_node->get_datatype().is_metatype) {
    // Handle ENUM and CLASS
  } else {
    // Handle "true" constants
  }
}

My PR was keeping an ENUM as a constant without reduced value all the way through to the compiler. The compiler checked whether it was a metatype, and if it was, I think created the dictionary then.

Strange I cannot reproduce const C2 = e.VALUE_A - I do get correct error about it being non-constant expression.

test-enum.zip
gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0

I do believe this is a good solution (in fact, I was investigating this earlier and thought about pretty much the same code as this).
@anvilfolk I understand your concern but I fear this check may have to be done in a lot of places, which is prone to errors since it's easy to forget. If we can conflate all to constant values it makes easier to deal with this in general.

Ok, I don't know if it is belongs strictly to this PR but I fixed the issue @dalexeev mentioned.
The fix is that a subscript cannot be typed as constant if a base is not.
Have trouble writing the test for that though. While the project has reproducible error (meaning lack of thereof) in editor (no complaints during editing and no error in runtime), but during testing the same code complains about things being non-constant (as it should) without the change, don't know what the reason for that.

Hm. Reverted that fix. When I said that I don't know if it belongs here I meant that the underlying issue is not about enums specifically and affects classes too. Unfortunately while the fix (I think) is correct there is some difference between classes - some of them are constants and some of them are not. Like identifiers for built-in types are not considered constant. So Vector3.UP is a subscript on a non-constant base at the moment.

Does this one work? It's an interesting one, because presumably E is the same as MyClass.MyEnum.
extends Node

func test(p : MyClass.MyEnum):
  print(p)

func _ready() -> void:
  const E = MyClass.MyEnum
  var a := E.VALUE_A
  var b: E = E.VALUE_A
  print(a)
  print(b)

After (very sleeeepily) thinking about it a bit more, I don't think there's any issue so long as E's datatype is_metatype, kind = ENUM and builtin_type = DICTIONARY. We don't lose any information in this case, I think, and can still check for metatype. It gets used as a constant anywhere where it's relevant, but the information about it being an enum metatype is still there.

No, this one does not work because const E is a local constant and they are not looked at during resolving datatype. If E is a member constant instead then yes, it does work.

I also think the other issues mentioned could be solved in a different PR, especially since this one fixes a crash so it's better to merge earlier rather than later.


Slow first run

We use angular 7.2, IOS 11. On first  click phone call - big delay 10 sec, after that all works fine

I have the same problem right now..
Has anyone already found a solution?

The problem is, that the process is called from wrong thread

Hi @davidseek , just tried your solution and it works well.
Do you plan to PR this ?
Many thanks

@rohfosho - please could you look into merging commit #33ec0d2554266869ad04ccdefb79fbab10614109 into master?
My app depends on it :)


SIOSocket is not sending or receiving calls reliably.

Hi,
I'm not sure any one here has faced the same issue. I'm working on iOS 8 and iPhone 5s. What I observe is intermittently (and repeatedly) socket emit and on to and from the server doesn't work. Sometimes the events are emitted but it doesn't reach the server. In other cases, event is sent by the server but not received by the client. It looks like I have no control over it and makes the app functionality very flaky.
Any thoughts or ideas on this issue? Thanks...

You are not alone. Maybe the threading issues will fix this?
Otherwise I am considering using https://github.com/acmacalister/jetfire and only ws on my iOS-interface... Or maybe this socket.io framework: https://github.com/francoisp/socket.IO-objc

After updating to the latest copy (with thread fixes) app is almost DEAD! Doesn't send or receive messages...i will take a look at other ones...thanks.

I have facing the problem of sending data and receiving data. Can u  show me of them?


Max water container problem in JavaScript

💥 Max water container problem in JavaScript
Given n non-negative integers a1, a2, ..., an , where each represents a point at coordinate (i, ai).
n vertical lines are drawn such that the two endpoints of the line i is at (i, ai) and (i, 0).
Find two lines, which, together with the x-axis forms a container, such that the container contains the most water.
Input: heights = [1,8,6,2,5,4,8,3,7]
Output: 49
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


database credentials

Hey! What should I do for this step: Modify /api/src/config/database.json for database credentials? Thanks!

You need to either install MySQL locally or use online free hosting (remotemysql.com) for testing and get the credentials.
Example credentials:
Username: root
Password: 74TMPD8B
Then edit the file accordingly:
{
  "development": {
    "username": "root",
    "password": "74TMPD8B",
    "database": "graphql",
    "host": "<IP_ADDRESS>",
    "dialect": "mysql"
  },
  "production": {
    ...
  }
}


editWorkflowSettings

Great library, this has been extremely useful!
We are attempting to edit the workflow settings of a folder and have been unable to.
Have you had any luck with calling the editWorkflowSettings method?  Hoping for any insight you'd have.
const workflowSettings = await cascadeAPI.readWorkflowSettings({
  identifier: {
    type: "folder",
    path: {
      siteId: site.id,
      path: "/",
    },
  },
});
console.log("Settings before: ", workflowSettings);

which the readWorkflowSettings gets a valid response, and reading the swagger docs I'd assume I'd then be able to call it right back with the following:
  await cascadeAPI.editWorkflowSettings({
    workflowSettings: workflowSettings.workflowSettings,
    applyInheritWorkflowsToChildren: true,
    applyRequireWorkflowToChildren: true,
  });

but it fails with an 'undefined' error.  Once we can get past this simple test, I'm hoping to then make the additional adjustments we'd like.
Thanks!

@elwingert I can't get it to work either. I tried both with the library as well as a standalone http client (Bruno). I'm in contact with HH and they are looking into it. Not sure if it's an API limitation or a bug, but once I know more, I'll let you know.

@elwingert Okay so it turns out that there is a discrepancy between the SOAP and REST API. Apparently the REST implementation expects the identifier to be at the top level.. editAccessRights is another endpoint that has this "issue". It also means that we can't simply feed the read response back into the edit response like we can with other endpoints because for whatever reason they've decided to include the identifier nested in the workflowSettings object. I've requested that they change the responses to move the identifier to the top level for these two endpoints... but who knows if they will do that. I will need to make adjustments for this in the library. Just for context, these are what we found to work:

You can add /folder/{id} to /editWorkflowSettings and it works
Move the identifier object outside of the workflowSettings object:

{
  "identifier": {
    "id": "id",
    "path": {
      "path": "_dev/test",
      "siteId": "id",
      "siteName": "Staging"
    },
    "type": "folder",
    "recycled": false
  },
  "workflowSettings": {
    "workflowDefinitions": [],
    "inheritedWorkflowDefinitions": [],
    "inheritWorkflows": false,
    "requireWorkflow": false
  }
}

Thanks @kuklaph for all of your help with this one and tracking down the "issue", very much appreciated!  We'll give the temporary solution a try and await your adjustment (i can't call it a fix, as it doesn't seem like anything wrong with what you've done) to the library as well.

No problem, glad it got figured out and thanks for pointing it out. 1.0.6 has been pushed here as well as npm. You should now see the identifier param outside at the top-level object as a required parameter for both editWorkflowSettings and editAccessRights endpoints. Going to close this, but feel free to let me know if you find anything else.


Fix so $intercomProvider.asyncLoading(true) works when using require.js

This provides a fix to https://github.com/gdi2290/angular-intercom/issues/24

thanks! :+1: I can tag a release in a couple hours unless you need it sooner

The sooner the better on our end
Cheers!

thanks, pushed up as 2.1.0


extrakeys: rename swap/swap64 to fix OpenBSD 7.1 compilation

OpenBSD defines swap64 in <endian.h>.

This error was reported against wally by @grubles building c-lightning, the build failure log can be seen here: https://github.com/ElementsProject/libwally-core/issues/334.

Do you use the library by including it instead of linking against it?

When building the normal libwallycore.a/.so file for linking into an application, no - we have a workaround for including the secp objects into the shared library (1). However for windows builds, cordova plugins, javascript and and the python packages we do, as there is no workaround to including the  secp256k1.c file in these cases (we don't control the build machinery).
We don't explicitly include <endian.h> and only BSD seems to be affected, so it seems to be transitively included by one of the python module build dependencies. In theory we could undefine the conflicting macro before including the source, and I am happy to ask grubles to test that. But we are not alone in this requirement, c-lightning separately builds its libhsm python module via secp256k1.c inclusion, and I believe any other python module will do as well (at least if they want to be manylinux/PyPI compatible). So it seems easier to namespace the calls here and avoid continuing fallout down the road.

Do you use the library by including it instead of linking against it?

When building the normal libwallycore.a/.so file for linking into an application, no - we have a workaround for including the secp objects into the shared library (1). However for windows builds, cordova plugins, javascript and and the python packages we do, as there is no workaround to including the secp256k1.c file in these cases (we don't control the build machinery).

Oh I see... I wasn't aware that people are actually doing this...
Just for my understanding: Wouldn't the normal way be to declare secp256k1-zkp to be a dependency and assume it's installed? What stops you from doing so? The missing releases/versioning? Or would this not work even if we had proper releases (because of all the special builds such as js and python).

Just for my understanding: Wouldn't the normal way be to declare secp256k1-zkp to be a dependency and assume it's installed? What stops you from doing so? The missing releases/versioning? Or would this not work even if we had proper releases (because of all the special builds such as js and python).

A possibly overlong overview:
If you were building an executable then yes, you could reasonably expect that to work with both static and dynamic linking. We do support building against an externally specified libsecp, but only for builds without elements support, and only for the case where you are building wally to link with your app specifically - at which point, we disclaim responsibility for you massaging your build environment to make it work.
However this libsecp fork has a lot of experimental modules, while we don't use them all yet, a system-wide installed libsecp would need to have the ones we need enabled, and that would open us up to missing modules, interface changes and working around bugs in installed versions which isn't feasible for us to support given our available resources and the large number of platform and language targets. Currently that's c, c++, android native, python, java, swift, cordova, javascript, embedded, wasm and more if you count our forks with languages we haven't merged yet (go, rust, ...), in BTC only and BTC + Elements variants.
On top of that, we support different options for embedded dev (Jade, bitbox02, homebrew HW) to reduce memory usage (e.g. secp contexts), and we need to be able to CI multiple build types on the same machine (dozens, for the manylinux python builds, 5 for native android cross-compiles).  And we've had to patch in our own bug fixes in the past. So the only solution we've found is bundling secp-zkp as a submodule, and building as we currently do.
In the specific case of python, its build system expects c-extensions to be fully self contained source files which are built by the packaging system, resulting in a single shared library with all symbols resolved except libpython.so and some blessed target specific libs (which go back to 2010 and obviously don't include libsecp). We used to have more flexibility in part-building our python module outside of the python tools but as time goes on various approaches have been shut down until all we have left is the current one.
Each other platform we build secp via include for has a similar story.

@jgriffiths I see, that makes sense... I kind of hoped that this is something we don't need to support but it seems I'm wrong. :D

@real-or-random Thanks!


Confirm Behavior of Puppet/Chef using DSC Resources with Get missing MOF parameters

Puppet and Chef can use DSC Resources. However, they use them in a different way to the DSC LCM. It would be good to confirm if Puppet/Chef has any issues with resources when the input parameters in Get-TargetResource differ from the MOF.
This is to confirm that this style guideline will not cause any problems for Puppet/Chef users of the DSC resource kit.

Puppet does not call Get-TargetResource at all. Both the dsc and dsc_lite modules use Invoke-DscResource to call Test and Set.
The dsc module parses the mof file on build to establish which parameters should be replayed into a puppet type definition.
I personally can't see a reason why the style guideline would cause a problem for Puppet.

Hi, Puppet employee here, primary contributor to the puppetlabs-dsc and puppetlabs-dsc_lite modules. As @indented-automation said, we use Invoke-DscResource to call the Test and Set methods directly, as those map to our workflow the best. You can see an example here and here. We do not use the Get methods as Puppet tracks state differently than DSC does.
What would make things difficult for us if the parameter sets for each of the functions are different. In the puppetlabs-dsc module we rely on parsing existing MOF files to build Puppet types. If there are significant differences in parameter sets, we could have problems determining which to include. This is less of a problem in the puppetlabs-dsc_lite module, as we leave it up to the user to specify which parameters to include.

Thanks @jpogran ! Appreciate the response and the detail + links. Now we just need to find out from the team at Chef. Hopefully it is the same situation. I'm not really considering Ansible here, but perhaps we should?


404 error page

Related Issue
Closes: #452
Description of Changes

Checklist:

[x]  My code adheres to the established style guidelines of this project.
[x]  I have conducted a self-review of my code.
[x]  I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

do not include header! and nav

cool design!

 do not include header! and nav

Check this out

change the dummy text
Optimize mobile mode please!

remove error.png as you have error.svg

last fix CI- npx prettier --write .
In your local

button effect is not good, see your previous change which you showed in description

button effect is not good, see your previous change which you showed in description

done or not?


Enable the IR checker post optimizer with RT longs

The first two commits are not strictly necessary. However, I felt they significantly help understanding of what the optimizer is doing.

It looks like the change in subtyping checks (3rd commit) causes long literals to become allocated as RT long:
 $c_jl_Math$.prototype.multiplyExact__J__J__J = (function(a, b) {
   var ahi = b.RTLong__f_hi;
   if (((ahi === 0) ? (b.RTLong__f_lo !== 0) : (ahi > 0))) {
-    var this$1 = $m_RTLong$();
-    var lo = this$1.divideImpl__I__I__I__I__I((-1),<PHONE_NUMBER>, b.RTLong__f_lo, b.RTLong__f_hi);
-    var hi = this$1.RTLong$__f_org$scalajs$linker$runtime$RuntimeLong$$hiReturn;
+    var this$1 = new $c_RTLong((-1),<PHONE_NUMBER>);
+    var this$2 = $m_RTLong$();
+    var lo = this$2.divideImpl__I__I__I__I__I(this$1.RTLong__f_lo, this$1.RTLong__f_hi, b.RTLong__f_lo, b.RTLong__f_hi);
+    var hi = this$2.RTLong$__f_org$scalajs$linker$runtime$RuntimeLong$$hiReturn;
     var ahi$1 = a.RTLong__f_hi;
     if (((ahi$1 === hi) ? (((-2147483648) ^ a.RTLong__f_lo) > ((-2147483648) ^ lo)) : (ahi$1 > hi))) {
       var overflow = true;

I'm trying to identify where the "offending" subtyping check is in the optimizer.

I have not gotten to a conclusion here yet. But it seems the issue is due to casts inserted on the receiver when inlining method calls: We need these when, say, calling + on a literal long for the IR to be correctly typed. OTOH, inserting them (which is what the 3rd commit causes) prevents farther inlining and folding of runtime long methods.


Folder Key error

Folder Key error when entering command python manage.py backup_website

It can't find your base folder in Google Drive. Have you created one and shared it with your service account?

You do it in Google drive using Google's web interface. https://drive.google.com/drive/u/0/home

that issue solved now its showing FileNotFound Error

This is only designed work with a Postgres database. I use it in a linux docker container and not Windows directly

okay

can you have any idea why this error is coming


Restructure the megapack

Consider restructing the megapack into the following structure:
papers/
assets/
misc/ (or resources/?)
to avoid the root directory being cluttered with the PDFs as it currently is. Also investigate a different possibility of hosting the assets. I have access to zainp.com to host some stuff via FTP, but I'd like to keep everything centralised in GitHub. It's not an issue per se, but I don't necessarily need people downloading the assets directory.

In fact, an easy solution for the assets folder is to move it to a separate branch. If anybody wants to get on with doing that, please do!


V2: Support forward references in recursive types

Example:
JSON = Union[str, int, float, bool, None, Mapping[str, 'JSON'], List['JSON']]

Given how popular this feature request was for MyPy (https://github.com/python/typing/issues/182), I think it would be nice if it "just worked" for Pydantic. Since pydantic-core already supports recursive types, it's just a matter of properly handling the recursive forward references.
@dmontagu I wonder if we could use similar work to what you did with generics for these sorts of recursive references? Ultimately I think we need to convert this into a DefinitionReference core schema, but I suspect we'll have to do a bit of smart stuff like your generics but with the forward references to detect the recursive forward reference and not just try to "resolve" it.

Even if we don't support this, we almost certainly need a better error message:
from typing import List, Mapping, Union

from pydantic import BaseModel

JSON = Union[str, int, float, bool, None, Mapping[str, 'JSON'], List['JSON']]

class A(BaseModel):
    x: JSON
    model_config = dict(arbitrary_types_allowed=True)

Traceback (most recent call last):
  File "/Users/davidmontague/Library/Application Support/JetBrains/PyCharm2023.1/scratches/scratch_8.py", line 8, in <module>
    class A(BaseModel):
  File "/Users/davidmontague/Programming/pydantic/pydantic/pydantic/main.py", line 124, in __new__
    _model_construction.complete_model_class(
  File "/Users/davidmontague/Programming/pydantic/pydantic/pydantic/_internal/_model_construction.py", line 185, in complete_model_class
    cls.__pydantic_validator__ = SchemaValidator(inner_schema, core_config)
pydantic_core._pydantic_core.SchemaError: Error building "typed-dict" validator:
  SchemaError: Field "x":
  SchemaError: Error building "nullable" validator:
  SchemaError: Error building "union" validator:
  SchemaError: Error building "function" validator:
  SchemaError: Error building "dict" validator:
  SchemaError: Error building "nullable" validator:
  SchemaError: Error building "union" validator:
  SchemaError: Error building "function" validator:
  SchemaError: Error building "dict" validator:
  SchemaError: Error building "is-instance" validator:
  SchemaError: 'cls' must be valid as the first argument to 'isinstance'

Some notes on this, taken from a comment I just made on a discussion.

Once the type alias syntax introduced in this PEP https://peps.python.org/pep-0695/#generic-type-alias is introduced, I think that will be the obvious way to handle it, though that will require python 3.12+.
Also, it looks like there is active work toward backporting the TypeAliasType into typing_extensions, and once it is added, I think that will be the obvious way to support it in earlier python versions. See https://github.com/python/typing_extensions/issues/159 and https://github.com/python/typing_extensions/pull/160 for reference.
For what it's worth, I think the pydantic implementation may end up looking similar to this: https://github.com/pydantic/pydantic/commit/ef5dd26c36e90a331fdb6a0a920c3ce619094366. I later reworked this to try to automatically infer the alias name. Ultimately that was a lot more complicated and likely would have perf and other implications, but fortunately TypeAliasType is similar enough to the type RecursiveType type I introduced in that commit that I think the same implementation/tests/etc. should work.

(@adriangb seems you are already on top of this, and I'm happy to defer to your plan here if you had a different implementation in mind, just adding a comment here before I forget.)


[WIP] Alternative construction mechanism for HLS config

Summary
This PR adds an alternative construction mechanism for specifying synthesis methods in HLSConfig directly using classes of type HighLevelSynthesisPlugin. When specified in this way, the synthesis methods do not need to be registered in the package metadata.
As an example:
from qiskit import QuantumCircuit
from qiskit.circuit.library.generalized_gates import PermutationGate
from qiskit.transpiler import PassManager
from qiskit.transpiler.passes.synthesis.high_level_synthesis import HLSConfig, HighLevelSynthesis
from qiskit.transpiler.passes.synthesis.high_level_synthesis import ACGSynthesisPermutation

qc = QuantumCircuit(6)
qc.append(PermutationGate([1, 2, 3, 0]), [1, 2, 3, 4])

hls_config = HLSConfig(permutation=[ACGSynthesisPermutation()])
pm = PassManager(HighLevelSynthesis(hls_config=hls_config))
qc_synthesized = pm.run(qc)

As in this case the synthesis method is registered in the package metadata, the line
hls_config = HLSConfig(permutation=[ACGSynthesisPermutation()])
is equivalent to
hls_config = HLSConfig(permutation=[("acg", {})])
Details and comments
This is a spinoff from #9250 which pulls out the alternative construction mechanism into a separate PR (following the reviews' comments).
This is still WIP, as it may also make sense to allows passing additional run parameters even when the synthesis plugin is specified as a class (ACGSynthesisPermutation) and not by the name ("acg"), and likewise it may make sense to avoid specifying empty lists of parameters (at some point suggested by @kdk).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0006%) to 84.924%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/synthesis/high_level_synthesis.py
6
7
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.0006%

Covered Lines:
66708

Relevant Lines:
78550

💛  - Coveralls

Thanks @mtreinish! I have updated the docstrings of HLSConfig and HighLevelSynthesis.


feat: color-history

This PR introduces a couple of breaking changes and major enhancement to the color-history API.
Breaking Changes

deprecated recentColors prop as it tried to do way too many things.

as a replacement, two new props have been added:

added showHistory prop to control the recent colors list visibility.
added colorHistory prop which is used to provide a list of colors.

New Features
#20 Disabled the ability to provide shareable colors after the app is bootstrapped, which prevents lazy components or dynamic ones from specifying the recent colors.
The new colorHistory prop allows the user to pass an array of color strings which will be used as the source of the history, the internal store implemented in #20 will be ignored and local data will be used to control the recent colors. This means all verte components passing colorHistory will be isolated and will not share the same colors.
The use of .sync modifier will solve this problem:
<Verte :showHistory="true" :colorHistory.sync="list"></Verte>

<Verte :showHistory="true" :colorHistory.sync="list"></Verte>

This allows the developer to be able to maintain and control the recent colors as they see fit.
The docs have been updated to reflect those changes.
closes #26

Codecov Report

Merging #27 into master will decrease coverage by 0.33%.
The diff coverage is 43.33%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   31.56%   31.23%   -0.34%
==========================================
  Files           6        6
  Lines         415      429      +14
  Branches       68       73       +5
==========================================
+ Hits          131      134       +3
- Misses        273      284      +11
  Partials       11       11

Impacted Files
Coverage Δ

src/store.js
61.11% <33.33%> (ø)
:arrow_up:

src/components/Verte.vue
30.61% <44.44%> (-1.54%)
:arrow_down:

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 0f9922d...fad914a. Read the comment docs.


After rancher upgrade, ingress in GKE cluster does not point to new targets once workload is scaled up

Rancher versions:
rancher/rancher: Upgrade from v2.0.0 to v2.0.1-rc1
Steps to Reproduce:

Create a GKE cluster in Rancher v2.00
Create workload with scale 2 and ingress pointing to the workload. The ingress points to all the pods in the workload
Upgrade the rancher server to v2.0.1-rc1
Increase the scale of the workload.

The ingress does not point to all the new pods in the workload.
Targets the ingress points to, is obtained using:
wget --header='host: myingress.default.<IP_ADDRESS>xip.io' http://<IP_ADDRESS>/name.html

Problem does also exists on Rancher v2.0.0 without the v2.0.1-rc1 update.

@gwiersma did you wait for the ingress to be up before testing? there is a known issue where it takes awhile before the ingress is available.

@soumyalj  i didn't reproduce your issue, but going though your gke ingress in your setup, it is getting stuck and seems to be routing stuff that is in cache. (I delete all your pods and restarted them, all the container name get changed but http response is still the same). I deleted the old ingress and started a new one and it is working. Let me know if you reproduced it again, i can spend time digging into it to see if there is anything that is not probably configed or we are not following GKE's best practice in how to use ingress.

@deniseschannon Yes i did. The steps i executed:

Start deployment
Create ingress and point to the specific workload
Tested the ingress controller successfully
Scaled my workload from 5 replicas to 10 replicas
10 new pods are scheduled and the 5 old pods are being removed
When all of the 10 new pods are available and the 5 old pods are removed, the Ingress controller responds with a 503.
After deleting the current ingress controller and creating a new ingress controller that points to the same workload, it works.

So it seems that the ingress controller does not dynamically scales the backend workloads.

Tested with upgrade from v2.0.0 to v2.0.1-rc2. Tested with the steps above. This time, when the workload scaled up, the ingress was able to get the updated set of pods. It takes 3 to 5 minutes for the ingress to get the update.


How to change zoomControl position?

I'm trying to set the position of the zoom control. I've been able to do this with no issues using other libraries, but with this one it seems no matter what I do, the zoom control (+ and - buttons) are always positioned in the bottom right corner
I've tried
  :zoom-control="true"
  :zoom-control-options="{ position: 9 }"

And I tried positions from 1 to 11, and nothing seems to make any difference.
Any ideas what I'm doing wrong?
https://developers.google.com/maps/documentation/javascript/reference/control#ControlPosition
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/google.maps/index.d.ts#L282-L338

Hi @vesper8
You should use the zoomControlPosition prop:
https://github.com/inocan-group/vue3-google-map/blob/develop/src/components/GoogleMap.vue#L210-L213
Example:
zoom-control-position="LEFT_BOTTOM"


URIError parsing url Params encoded with encodeURIComponent

It appears that decodeURI is called on urls before _extractParameters calls decodeURIComponent on params extracted from the url. This can cause a URIError when the param has already been partially decoded to contain a character that wouldn't be legal in a URI.
Example url: 'http://foo.com/bar/'+encodeURIComponent('foo%/bar')
Here's a fix that works for us, though I'm not confident I've tested with router and backbone history options we're not using:
https://github.com/jashkenas/backbone/pull/3425

Hey @asparagino, thanks for reporting this! I've always wondered if there were edge cases in which decodeURI would bite us. But now I know! :smiley:
We actually use decodeURI to deal with unicode escapes in Firefox (and maybe other browsers). I'll do some research to see what we can do here instead.

Hey @asparagino, thanks for reporting this! I've always wondered if there were edge cases in which decodeURI would bite us. But now I know! :smiley:
We actually use decodeURI to deal with unicode escapes in Firefox (and maybe other browsers). I'll do some research to see what we can do here instead.

+1 for this - I work for a newsy site with "seo friendly" urls, and pages like trove.com/a/1-Tax-Move-Most-Retirees-Must-Make-by-Dec-31-or-Pay-a-50%25-Penalty.cMdE1 will fail, because decodeURIComponent("1-Tax-Move-Most-Retirees-Must-Make-by-Dec-31-or-Pay-a-50%-Penalty") raises an exception, whereas the same URL without the url-encoded percent sign will succeed: trove.com/a/1-Tax-Move-Most-Retirees-Must-Make-by-Dec-31-or-Pay-a-50-Penalty.cMdE1

FYI, the decodeURI call was added in #2949 to deal with the fact that some browsers (i.e. Firefox) returns window.location with unicode characters percent encoded.

I think this is fixed by #3434. Mind giving that a try?

I might be making some leaps here but I think the correct behavior is for the browser to return a valid URI, The value of the href attribute MUST be the absolute URI reference and the percent character by itself (not as part of a uri-encoded octet) is not a valid character in a uri Because the percent "%" character always has the reserved purpose of being the escape indicator, it must be escaped as "%25" in order to be used as data within a URI. {page 9}
I wouldn't expect this to be solved anytime soon so the fix in Backbone is still a great idea, but do you think there would be some value in following up with browser vendors besides Firefox about clarifying and implementing the standard behavior?

do you think there would be some value in following up with browser vendors besides Firefox about clarifying and implementing the standard behavior?

I hope so! :smiley:

bug filed for WebKit: https://bugs.webkit.org/show_bug.cgi?id=140080
and Internet Explorer: https://connect.microsoft.com/IE/feedback/details/1076886

@macgyver - from debugging this, it looks the problem here is the url decoding process within backbone.
Even if you construct a valid url part, by calling encodeURIComponent on each param as you construct a url, decodeURI is called on location.href first, then the url is split apart and decodeURIComponent is called on each param.
So it's not that the browser returns an invalid URI in the location object, backbone has partially decoded and de-escaped %25 to % already with a decodeURI call, and the second attempt with decodeURIComponent is what throws the URIError.
#3434 looks good. I think it's a better fix than my hack in #3425 and I'll let you know if I pick up any further edge cases in testing.

Thanks for taking a look @asparagino!


gradlew error

I am attempting to run your build script on a clean new setup. My host machine's OS is Ubuntu 22.04.3 LTS.
After creating and connecting to the container, then trying to build ...
docker build -t atak-civ-4.6 .

docker run -ti -v /home/username/plugins:/home/atakdev/atak-civ/plugins atak-civ-4.6

cd plugins/my-plugin/

./gradlew assembleCivDebug

I get the following error ...

Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
Caused by: java.lang.ClassNotFoundException: org.gradle.wrapper.GradleWrapperMain

Any assistance would be most appreciated.

I am not sure about what you are doing.
If I follow your command, you are not logged into the docker.
You need to launch ./gradlew assembleCivDebug from the docker and not from the Windows/Linux environement.


Is The connected factory solution is talking to real OPC UA server?

We have a requirement to implement the application for industrial IOT using OPC UA server. I am completely new to Industrial IOT opc.
I would like to know high-level architecture of connected factory quick start application and either it is talking to real OPC UA severs..Please help me on this.
Thanks in advance

@reddyeswar1 Can you please provide more details if you have followed any of the Microsoft documents?
MicrosoftDocs Github issue is mainly related to the document issue. If this is not the case I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.

@reddyeswar161 Following up to see if you have looked into my previous comment.

@reddyeswar161 As there was no response we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


feat(config): update several Zooz devices to their 800 series revisions

waiting for confirmation that fingerprints are unchanged
fixes: https://github.com/zwave-js/node-zwave-js/issues/6183

@zwave-js-bot automerge


Update with striplog figures

The most recent implementations of Striplog allows one to return the figure from striplog.plot(). If we can get the axes for the stiplog figure, then we can sculpt is using PathPatches. This will make drawing the feature plot faster, it will also allow easier overlay of the striplog on cross-sections.
import numpy as np
import matplotlib.pyplot as plt
from matplotlib.patches import PathPatch

x = np.random.normal(0, 1, 1000).cumsum()
x -= x.min()
y = np.arange(x.size)

fig = plt.figure(figsize=(4, 10))
ax = fig.add_subplot(111)
bgim = ax.imshow(np.random.rand(y.max(), x.max()), cmap='Greys',
                 extent=[-10, 50, 0, 1000])
im = ax.imshow(x[:, None], extent=[x.min(), x.max(), y.min(), y.max()],
               cmap='gist_earth', aspect='auto', origin='lower')
paths = ax.fill_betweenx(y, x, facecolor='none')
patch = PathPatch(paths._paths[0], visible=False)
ax.add_artist(patch)
im.set_clip_path(patch)
ax.invert_yaxis()
plt.show()

Very cool. To clarify: you see this replacing the existing method or drawing patches?
It seems like there could be a problem with interpolation — just like with the usual way to paint lithologies on curves using a colourmap, at most resolutions, you end up with colours between the discrete colours, when in fact you want it to change abruptly.
I guess it is possible to paint/fill with a different curve? How would the striplog data (say, lithologies) have to look to paint with that? Would it have to be a curve, essentially? Can we pain with arbitrary (i.e. legend) colours, or would we have to make a fake colourmap that maps to the legend?

I propose that this is a better way to draw logs using patches.
To be clear, the color-filled image can be anything we want (just as before), and we can use clip it using any log (it could be the striplog variable width, or it could be a fixed width "bar".
In this example, I am "painting" with an entirely different set of data than the log. I'll work up an example with an actual striplog.

BTW: this method / trick was shared by Joe K.


Temperature measure using D435 camera relasense.

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

Is it possible to know the tempratue with in 1 meter distance of person using this D435 camera? Please reply asap.

Hi @pp3993
No, these are not thermal cameras. The infrared band it can detect is much closer to the visible light.

is there any realsense series of camera that can do both work of detecting face and temprature as well?

@pp3993  There was a case this month about synching a RealSense D435i camera with a FLIR camera.
https://github.com/IntelRealSense/librealsense/issues/6801
FLIR recently released a software product for their cameras that provides temperature sensing for COVID-19 screening.
https://www.theengineer.co.uk/supplier-network/product/flir-systems-launches-flir-screen-est-software-to-improve-skin-temperature-screening-for-covid-19/

Hi @pp3993   Do you require further assistance with this case please, or can it be closed?   Thanks!

Thankyou @MartyG-RealSense . I am closing this now thanks for your help!!!!

I'm pleased I could help - thanks for the update!


feat(error): added error for not Integer values

close #46

PTAL @simonecorsi @dnlup

@simonecorsi PTAL

PTAL!

TBH I still thinking we should just use debuglog without providing the option to pass custom logging function and avoid checks that complicates code readability, but for now let's merge we can change this later!


Performance Improve Password Generator

Added Performance Improvements for the Password generator

Created new Method which counts how many Criterion a String met (max. 4). This change has been made to reduce the amount of iterating of the same characters over and over to check each Criterion once per iteration and not all at the same time.
Changed the way of the occurence of the Common Sequences will be checked. Before a String has been lowered all the time which was very expensive. Now it won't be lowered anymore instead the Contains will now ignore the Case which is way faster.
The way the Password will be checked if it has been leaked has changed. The Implementation has requested many times if the Password has been leaked before the Password has been completly generated. Now it will check it at the end and will create a new Password if the generated one has been leaked (Much faster)
Added Do While loops instead of While loops (won't be a huge improvement) sinve we have to go through at least one time we do not have to check the Condition in first place.
Changed the type of the Password to a Span because iterating over a Span is slightly faster than a String

I think that was every improve
I also added some Documentation

Tested it and the result looked fine
No Compilation erros or other erros


Translation override issues

In Illuminate\Translation\FileLoader the method loadNamespaceOverrides is setting an incorrect file path.
For packages, I setup my language folder structure the same as the main laravel app does ie:
- package
    - src
        - resources
            - lang
                - en
                    buttons.php
                - fr
                    buttons.php

When I publish my package, the file path defined in the loadNamespaceOverrides method doesn't find the language files.
If the path is changed to the following everything works as expected and is also similar to how package views are overriden.:
$file = "{$this->path}/vendor/{$namespace}/{$locale}/{$group}.php";

In my package Service Provider I have my publish command for languages as follows:
$this->publishes([__DIR__ . '/resources/lang/' => base_path('resources/lang/vendor/myPackage')], 'lang');

I'm also calling the loadTranslationsFrom method in my package Service Provider as follows:
$this->loadTranslationsFrom(__DIR__.'/resources/lang', 'myPackage');

Thanks for reporting. We're open to pull requests if you have any time. :)


Fixing up "Performance recommendations for immersive headset apps"

only a few small changes

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/performance-recommendations-for-immersive-headset-apps.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Stipple.init: vue_app_name does not affect HTML root element name

If I choose a custom name for my vue app via supplying the vue_app_name kwarg to Stipple.init, the Genie app doesn't work, because the generated HTML root element (as created by the page() function) still has the standard name. This results in a javascript error (#xyz not found)
I believe the problem lies with the vm() = root() function in Elements.jl, which does not refer to what was previously supplied to Stipple.init:
function root(app::M)::String where {M<:ReactiveModel}
  Genie.Generator.validname(typeof(app) |> string)
end

That sounds like the root() cause, indeed!
Have you tried overwriting root(), e.g.
Stipple.root(::MyModel) = "my_highly_desired_alternative_name"

Please let me know if that helps.

close enough :)! This helped:
function root(app::Type{M})::String where {M<:ReactiveModel}
    "I_am_so_happy_I_can_use_this_name"
 end

(needed to overwrite the Type{M} function)
If it only always was that easy to get to the root of the problem 👀


Deck.NET compiles significantly faster than bridge build

1~2 seconds is all Deck.NET takes to compile the same HelloWorld program that the Bridge.NET CLI generates with bridge new, but Bridge.NET takes 4~5 seconds. That's a 250%~400% slowdown.
https://deck.net/8863ecb5e31cf900c46c25aab17f6234
...
(Identical ticket in the CLI project: https://github.com/bridgedotnet/CLI/issues/31)

Visual Studio also compiles a small Bridge.NET Hello World application in 1-2 seconds, while bridge build on the same computer takes 6-7 seconds.
Any ideas on why?


chore: avoiding barrel file imports for cloudscape

Overview
avoiding barrel file imports for cloudscape components
apologies for a large CR, only the imports have been changed
Verifying Changes
Legal
This project is available under the Apache 2.0 License.

closing as stale PR


Certain features are not working on ARM-based CPUs packages (eg: macOS Silicon)

Context
F3D is shipped on different platform, including macOS ARM64.
However, that package come with limitations, lets try to improve that.
Improvement to do

[x] Exodus:

In the Exodus plugin, we are using the official VTK reader which uses HDF5 internally.
We are using cross-compiling from an x86_64 host to generate ARM-based packages like for Apple Silicon architecture.
However, HDF5 fails to compile when cross-compiling for some reason (or it does not compile on ARM at all?).
When GitHub releases Apple Silicon runners, let's try to fix that.

[x] Raytracing:

Does not work with ARM64 yet

[x] CI Testing

While we can cross-compile for AMR64, we have no way to actually test the results, investigate how to fix that

Can we close this one @mwestphal ?

 -DENABLE_exodus=${{ contains(env.CMAKE_OSX_ARCHITECTURES, 'arm64') && 'OFF' || 'ON' }}
Exodus is not fixed, lets try to enable it in CI.

All topics have been fixed.

Doc should be udpdated


RuntimeError: DOM is not defined

If builtins is specified, each property on the builtins object defines a builtin variable for the runtime; these builtins are available as named inputs to any defined variables on any module associated with this runtime

Unfortunately, I get an error: "RuntimeError: DOM is not defined"  ;(
Runtime.load(notebook, { data }, cell => {
      if (cell.name === 'chart') {
        return new Inspector(this.ref.nativeElement);
      }
});

is there a way to set builtin variables, and render notebook into DOM element?

I got the same issue with md. I fixed it by adding this:
notebook.modules[Object.keys(notebook.modules)[0]].variables.push({name: 'md', value: () => library.md})

Perhaps you could fix it by adding this:
notebook.modules[Object.keys(notebook.modules)[0]].variables.push({name: 'DOM', value: () => library.DOM})

It's a temporary hack, likely to break when it's fixed.

I wanted to replace my md to get it to do what I wanted under node with jsdom. Here's my whole file so far (build.mjs run with node --experimental-modules build/build.mjs):
import jsdom from 'jsdom'
import fetch from 'node-fetch'
const DOM = new jsdom.JSDOM(``, { pretendToBeVisual: true })
global.window = DOM.window
global.document = DOM.window.document
global.requestAnimationFrame = DOM.window.requestAnimationFrame.bind(DOM.window)
global.fetch = fetch
import notebookRuntime from '@observablehq/notebook-runtime'
import notebook from '../notebook'

const {Runtime, Library} = notebookRuntime
const library = new Library()
const md = (strs, ...vars) => { let s = ''; for (let i=0; i < strs.length; i++) { s += strs[i] + vars[i] || '' }; return s }
notebook.modules[Object.keys(notebook.modules)[0]].variables.push({name: 'md', value: () => md})
Runtime.load(notebook, library, variable => {
  return {
        pending: () => {
          console.log(`loading ${variable.name}`)
        },
        fulfilled: value => {
          console.log(`loaded ${variable.name}:`, value)
        },
        rejected: err => {
          console.error(`error loading ${variable.name}:`, err)
      console.error(err.trace)
        }
  };
});

Hey @ertle - the code you're posting -
Runtime.load(notebook, { data }, cell => {
      if (cell.name === 'chart') {
        return new Inspector(this.ref.nativeElement);
      }
});

Given the function signature of Runtime.load(notebook, [builtins], observer), this is defining builtins as an object like { data } (or what ES6 interprets as { data: data }. I'm guessing that you want data to be one of the builtins - if that isn't the case, just remove the function argument entirely. But if that is what you want, you can combine the default Library with the custom data property:
Runtime.load(notebook, Object.assign({}, new Library, { data }), cell => {
      if (cell.name === 'chart') {
        return new Inspector(this.ref.nativeElement);
      }
});

And then you should be rid of the DOM is not defined bug. The Library includes all of the default builtins, one of which is DOM, and by providing an alternative data-only builtins object, the example you posted was missing DOM.
This solution is probably the same for @benatkin - it's better to extend the builtins by adding md to an extended library than it is to define a new cell.

@tmcw the Library has md, though - it seems to expect it to be defined in the notebook. I'm about to post my whole project to the Observable forum, so you can have a look at it then.

Maybe since my cells are defined as md\foo`rather than{ return md`foo` }it's addingmdto theinputs` in each cell that uses it. or maybe it's actually the reverse...

Here's a worked example of redefining md as something runnable in a node environment:
import marked from "marked";
import jsdom from "jsdom";
import fetch from "node-fetch";
const DOM = new jsdom.JSDOM(``, { pretendToBeVisual: true });
global.window = DOM.window;
global.document = DOM.window.document;
global.requestAnimationFrame = DOM.window.requestAnimationFrame.bind(
  DOM.window
);
global.fetch = fetch;
import notebookRuntime from "@observablehq/notebook-runtime";
import notebook from "./notebook";

const { Runtime, Library } = notebookRuntime;
const library = new Library();
const md = (strs, ...vars) => {
  let s = "";
  for (let i = 0; i < strs.length; i++) {
    s += strs[i] + (vars[i] || "");
  }
  return marked(s);
};

Runtime.load(notebook, { ...library, md: Promise.resolve(md) }, variable => {
  return {
    pending: () => {
      console.log(`loading ${variable.name}`);
    },
    fulfilled: value => {
      console.log(`loaded ${variable.name}:`, value);
    },
    rejected: err => {
      console.error(`error loading ${variable.name}:`, err);
      console.error(err.trace);
    }
  };
});

md won't work off the bat because it uses d3-require to lazily load marked - same with the tex literal - right now node.js compatibility is not in scope for notebook-runtime or notebook-stdlib, so this is all a bit wild west.

@tmcw thanks! That makes sense. I knew I was missing something.
I just posted my notebook.


docs: Update the security e-mail address.

This repository is now managed by the Axim Collaborative and security issues
with it should be reported to<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>This work is being done as a part of https://github.com/openedx/wg-security/issues/16

:tada: This PR is included in version 21.5.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix ensureValueDefined option of SelectInputView

The change in #725 made sure that the first option is always displayed
as a default value in a select box without blank item. This broke the
`ensureValueDefined' option: A value would only be defined if the
select box did not have selected item.
Instead explicitly check that if the model has a value defined for the
property. If not, calling save is enough now since the first item
has already been selected.

Coverage remained the same at 99.026% when pulling 823e22f3f3f4329d953d5dc7c8c37e0f1c8492b3 on tf:select-input-view-ensure-value-defined into 6820d5dd2552be61431762440690e0d2aa32ee72 on codevise:master.

Coverage remained the same at 99.026% when pulling 823e22f3f3f4329d953d5dc7c8c37e0f1c8492b3 on tf:select-input-view-ensure-value-defined into 6820d5dd2552be61431762440690e0d2aa32ee72 on codevise:master.


Improve logging consistency throughout the codebase

Currently, logging is pretty ad-hoc: different modules use logging levels pretty arbitrarily, and there is important information in trace levels and unimportant info in log. We should take a pass on the code base and figure out what information we usually end up wanting, what information we want for debugging purposes, and what we never even look at.

Hi @bartsmykla! Sure thing, feel free! I'm having second thoughts about labeling this as "good first issue" though, as figuring out what logging levels are appropriate in each instance, and figuring out what other logging statements will be useful, actually requires a decent familiarity with how the system works internally. If you feel up to the challenge of trying to familiarize yourself with the codebase (and maybe start small?) then go for it! I'd be happy to review PRs!


Clean up backend.run(...) interface

The backend.run(...) interface has accumulated a lot of cruft over the years. We need to start paring down this interface to only things which are essential.
Some things that I think can go (should validate all of these):

remove Schedule and List[Schedule] from the allowed types of circuits. We nominally stopped supporting these types already in January 2022.
qubit_lo_freq
meas_lo_freq
schedule_los
noise_model - should be attached to the Backend, not to the call to run().
seed_simulator - again should be an argument on the simulator/backend

More controversial, but I think still worthwhile:

drop the memory argument and only expose the behavior of memory=True. Rationale: if you really want statistics, use the Sampler instead.
meas_return - if we only support memory=True, then it only makes sense for this to be 'single'

For future consideration:

meas_level - OpenQASM 3 allows expressing different measurement levels with separate measure commands in the OpenPulse grammar. I think it makes sense to develop equivalents in Qiskit and then read out the requested measurement level from the circuit itself

@coruscating could you validate whether or not the LO parameters are used by qiskit-experiments?

@blakejohnson We don't use these LO parameters in experiments.
Regarding only supporting single-shot memory by default: will the memory keyword being overloaded between level 1 and 2 be addressed? Or are we disabling the ability to get single-shot counts?

@coruscating if we only expose a memory-like interface, then I think that would imply that we only support single-shot values. I suspect that many qiskit-experiments probably expect average values, though.

I think the LO parameters only work for schedule jobs that we don't support any more any way.
I don't have a strong opinion on the memory change. I would like qiskit-experiments to be able to handle single and average return formats seamlessly for analysis that works with the average any way. I think the main concern is data volume for parallel single qubit experiments. You can save a factor of a few hundred (the number of shots) when running something like Rabi across a device. If running a multi-qubit circuit, I think you care about the individual shots or could use the Sampler any way (because you likely have a discriminator).
I never use the online simulators, but why attach an option like seed_simulator to the backend rather than passing it with run? I am curious because any run() option you could choose to make something that you set on the backend instead.

but why attach an option like seed_simulator to the backend rather than passing it with run?

I think the rationale is that noise_model and seed_simulator are options to configure a backend. Whereas the rest are execution time options.
In addition to what @blakejohnson suggested, we should also mention that one can use backend.configuration().meas_levels to determine which levels are supported (the vast majority doesn't support 0 anymore).

I've been looking at adding noise_model and seed_simulator to the IBMBackend cot'r. This doesn't really make sense, because no one is supposed to directly call this cot'r. The IBMProvider only "gets" a backend, but does not actually construct it.
The idea is that the backend is an object in itself, with all its properties. Therefore it makes sense to add these either through the IBMBackend.options or through IBMBackend.run(), which is the way it is now.
Any thoughts? @jyu00 , @kt474 , @blakejohnson ?

Therefore it makes sense to add these either through the IBMBackend.options

Yeah that's what we meant by "attached to the Backend", sorry for the confusion.
By the way, these options should only be available to simulator backends. For reference, this is how it was done in ibmq-provider: https://github.com/Qiskit/qiskit-ibmq-provider/blob/master/qiskit/providers/ibmq/ibmqbackend.py#L845-L853


Add "Resources" and organize content under it

Following the latest community discussions and the Kubeflow docs restructure proposal, we should add the concept of "Resources", with the following structure:

Resources (remove "Tutorials, Samples, and Shared")

Kubeflow Samples
Codelabs, Workshops, and Tutorials
Blog Posts
Videos
Shared Resources and Components

/priority p1

I am closing in preference of https://github.com/kubeflow/website/issues/2759, feel free to reopen if we want to add a resources again in future.
/close