Set up a shared DB for storing the scripts

The paper programming environment uses a database for storing the scripts associated with each piece of paper.  In our early prototyping, we've had each user set up a local instance of PostgreSQL.  It would be good to migrate to a shared DB that is accessible from anywhere, but is also secure so that malicious actors can't mess it up.
@mattpen - You've got the most experience with SQL databases on the PhET team.  How would you recommend starting to approach this?

@jbphet - Can you provide some more context?  I'm not familiar with the paper programming environment at all.  Is it making SQL calls directly, or do we need some kind of HTTP/REST layer to control access and validate input?
The only remote access we have setup at phet is a MySQL database on phet-server2.  There is a php script that writes to it locally in response to HTTP requests, and yotta reads from it remotely on bayes. I didn't set this up, but I was able to recreate it when we migrated from phet-server to phet-server2.  So I wouldn't consider myself an expert in distributed database services, but I could probably help.
I would say that if we are opening ports to allow SQL calls from anywhere on the internet directly to the database, we will want to make sure that this is strongly encapsulated from our production website database, hopefully on a different machine entirely.  I'm not sure which machine would be appropriate.  Will this be a production level system, or it is just for research or testing (or something else)?

Let's go ahead and investigate free or paid services to temporarily host something outside of the university servers, at least while we explore. We can move things later as long as we don't lose the database itself :)

We looked into this a bit today and found the knexfile.js (https://github.com/phetsims/papyrus/blob/d409fc80ee7c1924d8e95af56b7dfbf838b8a5c0/knexfile.js#L17-L16) where we can change the URL for the database. We tested by adding a .env file to the root of the project with a different URL at DATABASE_URL, and saw the project try to use it..

We discovered in design meeting that several of us needed to re-select the space name "shared-experiments" in order to get the programs to show up in the queue/editor.

[ ] Fix this! :)

We have the green light to buy the "Pretty Panda" tier on ElephantSQL. Need to check with Oliver on details of the purchase.

As of this moment, we have set up the ability for the server to connect to a DB hosted by ElephantSQL, and are using the free "Tiny Turtle" plan.  The details of the DB name and how to connect to it will be kept out of GitHub as a security measure.

The plan for the ElephantSQL DB has been upgraded to Pretty Panda, and we should now be able to support up to 20 concurrent connections.  I also just sent @jessegreenberg and @BLFiedler invitations to the team admin privileges.  I think the basics of this issue are now covered, so I'll unassign myself.
@jessegreenberg and @BLFiedler - Please let me know if you don't get the invitations or have any issues with getting access to the DB.

Thanks! I received the invitation and have access.

DONE


[akka-http-circe] Any reason for ErrorAccumulatingUnmarshaller to be private?

Hi,
I'm trying to write a rejection handler that will customise the json response in case more than one field is wrong.
The problem is that ErrorAccumulatingUnmarshaller is private, therefore I cannot pattern match on it
private val rejectionHandler: RejectionHandler = RejectionHandler.newBuilder()
    .handle {
      case r@MalformedRequestContentRejection(message, cause) =>
        val errors: List[String] = cause match {
          // Single error - This happens when mixing in FailFastCirceSupport
          case DecodingFailure(msg, ops) =>
            ops.map {
              case DownField(key) => s"Invalid format for field: ${key}"
              case o => s"An error has occurred: $o"
            }
          // Multiple errors - This happens when mixing in ErrorAccumulatingCirceSupport
          // I would like to pattern match but I can't because ErrorAccumulatingUnmarshaller is private
          // case e:ErrorAccumulatingUnmarshaller.DecodingFailures =>

          case e =>
            List("an unexpected error has happened " + e.getMessage)
        }
        complete(BadRequest, errors.mkString("\n"))
    }.result()

Is there another way to achieve that? If not, is there a reason for it to be private?
Thanks,
Paolo

Good catch. Probably we need more API here. Proposal and PR welcome.

More than happy to raise a PR.
I was thinking about two options, but maybe you had something else in mind:
a) just make ErrorAccumulatingCirceSupport object public and possibly DecodingFailures a case class to get the extractor for free
b) move DecodingFailures inside BaseCirceSupport and make sure that both the standard unmarshaller and the error accumulating one throw a DecodingFailures in case of failures. Obviously the standard unmarshaller will put only one DecodingFailure inside the list. This way, we can handle the failures in a common way, regardless if the end user is using the error accumulating feature or not.
How does it sound?

I suggest a) with the following modification: Move DecodingFailures to object ErrorAccumulatingCirceSupport and delete the now obsolete object ErrorAccumulatingUnmarshaller.

Closed by #159.


Include babelify transform

Using this technique, the module is transpiled when used with browserify (if
the babelify transform is available). Otherwise the const keywords breaks
some browsers.

Thanks!!!

Thanks for merging :). This was a show stopper for me :)
2016-03-09 12:32 GMT+01:00 Gabriel Montes<EMAIL_ADDRESS>
Thanks!!!
—
Reply to this email directly or view it on GitHub
https://github.com/gabmontes/tiny-promisify/pull/1#issuecomment-194251996
.

--
Dominik Burgdörfer
Mobile +49 (0)176 9541 6274
E-Mail<EMAIL_ADDRESS>

Published in version 0.1.1!


App: add mainnet mode

As we're deploying mainnet, it would be good to keep the testnet around and be able to switch between them in the interfaces.
Technologically this isn't hard since the same contracts exist on both.
But it might be annoying to juggle 4 chains (test/main x front/side), and we would need to have UX for the switching.

https://github.com/webaverse/contracts/pull/5

https://github.com/webaverse/contracts/pull/5


feat: support dbgenerated id type

This adds support for having dbgenerated() ids in your schema while still being able to use prismock to create entries without explicitly passing the id.
Previously, in a schema file with ids defined like this:
model Thing {
  id String @id @default(dbgenerated("gen_random_uuid()")) @db.Uuid
  ...

Calling prismock.thing.create({}) would result in an object with an undefined id.

Something akin to this would be legendary.


SSL curl error

Goal:
First seen at Chevron by Erick using Splunk. When enabling an HTTP endpoint in splunk it defaults to SSL. When used with our splunk plug-in they got the following error when it was connecting:
[time=2019-12-12 14:05:09.432533 host=llin672.xhl.chevrontexaco.net] Could not run curl query: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

This suggests that the version of the curl library that we use does not support the required authentication mechanism.

It may be as simple as setting the following:
curl_setopt($ch, CURLOPT_SSLVERSION, 6);

A bit more research and the version of openssl that we build with does not support TLS 1.2 - we have openssl v0.9.8e-22 installed on the build machines. So this is the cause of the problem.


Issue #117 Add EAP CD imagestreams and templates

Fix #117

@budhrg LGTM, except a readme. But readme is up to you.


chore: intl package is not required, the API doesn't require _dateFormatter

Closes #
Proposed Changes
Briefly describe your proposed changes:
Checklist

[ ] CHANGELOG.md updated
[ ] Rebased/mergeable
[ ] A test has been added if appropriate
[ ] pub run test completes successfully
[ ] Commit messages are in semantic format
[ ] Sign CLA (if not already signed)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 21.00%. Comparing base (12fd973) to head (994c5eb).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   21.00%   21.00%
=======================================
  Files         117      117
  Lines        7552     7551    -1
=======================================
  Hits         1586     1586
+ Misses       5966     5965    -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Update uk.json

fixed typos, add new translations

Hi @yevhen-kulihin
We use Transifex for our translation files, can you make updates there instead?
https://www.transifex.com/ob1/openbazaar
The next time we do a release we'll pull the latest file from Transifex, and any changes in this repo will be overwritten.
If you sign up there I'll approve you and you can do the updates that way. Thank you!

Thank you, joined


Update pull request test - concurrency

Closes sap/fundamental#
Added concurrency ensures that only a single job or workflow using the same concurrency group will run at a time.
Test

When you have two pull requests the new one will stay in pending and after pending will change to queuing.

Changelog
New

add

concurrency:
  group: ${{ github.workflow }}

Changed

before two test run in parallel

Removed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update coveralls only when pushing to master

Right now, the coverage score is updated on any push (branch independent).
Add a new workflow that updates only when pushing to master.
https://github.com/backpackerds/primitives/blob/master/.github/workflows/test.yml

Nevermind, score is calculated per branch.


Improved css

Update style with better naming (mulish -> title)
Add image shortcode
Remove first capital letter in main content

Would appreciate if other contributors have a look on this one before merging it 🙂


Use ip route replace instead of add

Fixes timing window when route exists during live migration

Neil, are you OK to review this? It's kind of obvious what I'm doing and why.
Fixes bug #180.

retest this please

retest this please


pstoedit: patch to ensure gs-9.22 compatibilty

Motivation for this change
pstoedit calls ghostscript with the DELAYBIND option. This option is not support anymore
in gs-9.22. It is now called REALLYDELAYBIND. Newer versions of pstoedit add a compatibility switch
(-rdb) to activate the new option. However, programs like inkscape, which call pstoedit in the background do not know about this requirement and will fail eventually (i.e. gs refuses to the take old  DELAYBIND option).
With this patch typesetting LaTex formulas in inkscape works again.
Things done
Introduce patch to turn on -rdb command line option by default.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @MarcWeber

@GrahamcOfBorg  build pstoedit

Success on x86_64-linux (full log)
Attempted: pstoedit
Partial log (click to expand)
gzipping man pages under /nix/store/vdi0rb0bcf1arwp671kasfy3vx79r3px-pstoedit-3.73/share/man/
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vdi0rb0bcf1arwp671kasfy3vx79r3px-pstoedit-3.73/lib  /nix/store/vdi0rb0bcf1arwp671kasfy3vx79r3px-pstoedit-3.73/bin
patching script interpreter paths in /nix/store/vdi0rb0bcf1arwp671kasfy3vx79r3px-pstoedit-3.73
checking for references to /tmp/nix-build-pstoedit-3.73.drv-0 in /nix/store/vdi0rb0bcf1arwp671kasfy3vx79r3px-pstoedit-3.73...
shrinking RPATHs of ELF executables and libraries in /nix/store/m6vf4bs02wa0dyl2a840pyqpsjnsm9xm-pstoedit-3.73-dev
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/m6vf4bs02wa0dyl2a840pyqpsjnsm9xm-pstoedit-3.73-dev/lib
patching script interpreter paths in /nix/store/m6vf4bs02wa0dyl2a840pyqpsjnsm9xm-pstoedit-3.73-dev
checking for references to /tmp/nix-build-pstoedit-3.73.drv-0 in /nix/store/m6vf4bs02wa0dyl2a840pyqpsjnsm9xm-pstoedit-3.73-dev...

Success on x86_64-darwin (full log)
Attempted: pstoedit
Partial log (click to expand)
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73/lib/libpstoedit.0.dylib: fixing dylib
strip is /nix/store/7ddbq63v97nk8gkbf7gcsfmby37h6gbl-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/2smz2agdiksqxzc3lm8z69dyyr3ycx6k-pstoedit-3.73-dev/lib
patching script interpreter paths in /nix/store/2smz2agdiksqxzc3lm8z69dyyr3ycx6k-pstoedit-3.73-dev
/nix/store/rj9zcjl3wih24ia2yvar76nwwn364hxg-pstoedit-3.73

Success on aarch64-linux (full log)
Attempted: pstoedit
Partial log (click to expand)
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/laff6h9nb2mdh74qai6i1cb4fl9b7llf-pstoedit-3.73/lib  /nix/store/laff6h9nb2mdh74qai6i1cb4fl9b7llf-pstoedit-3.73/bin
patching script interpreter paths in /nix/store/laff6h9nb2mdh74qai6i1cb4fl9b7llf-pstoedit-3.73
checking for references to /build in /nix/store/laff6h9nb2mdh74qai6i1cb4fl9b7llf-pstoedit-3.73...
shrinking RPATHs of ELF executables and libraries in /nix/store/xmsrxf5bql4cizbf8vca9880ma9zahwr-pstoedit-3.73-dev
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/xmsrxf5bql4cizbf8vca9880ma9zahwr-pstoedit-3.73-dev/lib
patching script interpreter paths in /nix/store/xmsrxf5bql4cizbf8vca9880ma9zahwr-pstoedit-3.73-dev
checking for references to /build in /nix/store/xmsrxf5bql4cizbf8vca9880ma9zahwr-pstoedit-3.73-dev...
/nix/store/laff6h9nb2mdh74qai6i1cb4fl9b7llf-pstoedit-3.73


Makefile targets do not match release versions

the make targets do not match what is released
e.g.
"make 1.14"
expands to
"$(MAKE) k8s kubernetes_version=1.14.6 kubernetes_build_date=2019-08-22"
But the current release version appears to have been built as
"$(MAKE) k8s kubernetes_version=1.14.7 kubernetes_build_date=2019-09-27"
It is impossible (from this repo) to know how to reproduce the actual release since the official images do not use the targets in the makefile.

we’ll release the binaries we internal use soon.

The binaries is released as below:

amazon-eks/1.14.7/2019-09-27
amazon-eks/1.13.11/2019-09-27
amazon-eks/1.12.10/2019-09-27
amazon-eks/1.11.10/2019-09-27
We'll add some automation in our AMI release pipeline for these node-side binaries too.


HTTP Code 500 while download conteiner

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


Detecting RxJS5 from RxJS4

Packaging systems probably would cover this, but if I load RxJS globally (see #1274 ), into the browser, it would be nice to be able to tell RxJS5 apart from RxJS4. This allows me to make a library that would know how to work with either.
All I'd want is a suggestion on what feature is a good candidate to check for.

The lift() is pretty unique for this library, so checking if an Observable has lift() might be one way of duck typing.

If you're looking for interop with any Observable type, I highly recommend looking for Symbol.observable, while I don't think it's implemented in Rx 4, yet, it would be a trivial add for @mattpodwysocki. It should already exist in Most.js, Bacon, etc.
In the short-term, you could just test for subscribe and then always call it with three functions (not an Observer, because that signature has changed).
I'd strongly caution against making assumptions about Observable types provided by third parties, and wrap whatever you get in a type you know from your own library. Any give Observable implementation may have slightly different methods available on it, or scheduling, etc. It's best to keep control of those things yourself within the internals of your library.

@blesh any reason not to start exporting a version number?
import Rx from 'rxjs/Rx';
Rx.VERSION === '5.0.0-beta.1'

Common pattern amongst libs, as I'm sure you know (but others reading this may not)

Also--I'm still of the opinion he should be feature testing instead of version checking though, if reasonable. If you need a certain feature or expect a certain API, test to see whether provided Observable meets that need. Provides better experience when users may want to use your library with other Observable libs that happen to meet those requirements. But without knowing what exactly he's doing, it obviously depends.

@jayphelps we can export a version number, sure. No good reason other than it's not a priority and I'd want it to be automated.
Otherwise, @akauppi what @jayphelps is saying is totally accurate. You should probably feature test before using features from types provided by a third party. The "shape" of the Observable subscribe is going to be the same if your passing functions (and not Observers). But the return value to the subscribe will either have dispose or unsubscribe so test for that.
If you wanted a simple test testing for Rx.Subscriber by itself would be a huge flag that it's RxJS 5. Otherwise you could test Subjects for onNext vs next or something.

I ended up doing this, i.e. checking for the .subscribe name change:
  var RxJS5 = (function() {   // tbd. can autodetect this if we want to support both RxJS4 and 5
    var sub = new Rx.Subject();
    (sub.unsubscribe || sub.dispose)();
    return !!sub.unsubscribe;
  })();

My use case is a bit special. I'm moving a library to RxJS5 and want to keep the old code base (where it differs) along for a while, in case there are problems. But so far, RxJS5 seems solid and I don't intend to actually test and support both.


Problems recording on Firefox

Hello first of all thanks for a great demo.
I'm using web-audio-recorder-js for a web application recording and encoding mp3.
Using Firefox (52 right now a need to use HTML5 instead java solution).
I'm losing a few seconds of audio on my records, after 10 minutes about 10 seconds, that time is added in next record but with audio no recorded, and losing time too. I really appreciate if that has a solution o recommendation.
Right now I need minimum 16GB of memory for Windows and 8GB for macOS using firefox.
Thanks

I have the same problem, it's very unconsistent recording on different platforms


Use role instead of class for struct related exercises

For exercises 37/38 about structs, there are some sample code like this:
// We'll use an enum to specify the character class.
const Class = enum {
    wizard,
    thief,
    bard,
    warrior,
};

// Please add a new property to this struct called "health" and make
// it a u8 integer type.
const Character = struct {
    class: Class,
    gold: u32,
    experience: u32,
    health: u32,
};

Since class is a keyword/feature in many other programming languages, such as Java/Python/C++, users with other programming language experiences probably have to pay special attention to tell if this is a new syntax for zig introduced in the new exercises. This seems unnecessary distraction, and we may change the wording from class to other word like role to avoid such issue. Just my two cents.

I agree, especially because it's a role play.


Implement provider and provision template

Description
The only way to deploy a provision is using a deployment file in YAML format. This way will remain, but it would be useful to be able to use a provision template and just instantiate it. Also, the provider information is always the same (connection details, location, etc..) having this stored in the database will simply things for cloud administrators.
Use case
This feature will simply provision management. The user can have all the information that is always the same stored in the database and reuse it. Although, this feature is available, the deployment file will be always respected.
Interface Changes

OneProvision library.
OneProvision CLI to add new command and sub commands.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge in master:

code
docs
packages
tests


Unable to animate Opacity of a Grid

I have a Grid which consists of several children ( a collection of UserControls). I am trying to animate the Opacity of this Grid using the following code
var rootGridVisual = ElementCompositionPreview.GetElementVisual(RootGrid);
scalarAnim = _compositor.CreateScalarKeyFrameAnimation();
scalarAnim.InsertKeyFrame(0.4f, 0);
scalarAnim.Duration = TimeSpan.FromSeconds(0.5);
rootGridVisual.StartAnimation(nameof(rootGridVisual.Opacity), scalarAnim);
But upon running this code, the opacity of the Grid does not change at all.
Am I missing something here?

Not sure, but I think you'll need two keyframes minimum.

Even then it does not work. I tried the following code
var rootGridVisual = ElementCompositionPreview.GetElementVisual(RootGrid);
scalarAnim = _compositor.CreateScalarKeyFrameAnimation();
scalarAnim.InsertKeyFrame(0, 1f);
scalarAnim.InsertKeyFrame(0.4f, 0.4f);
scalarAnim.InsertKeyFrame(0.7f, 0);
scalarAnim.Duration = TimeSpan.FromSeconds(0.5);
rootGridVisual.StartAnimation(nameof(rootGridVisual.Opacity), scalarAnim);
But it still does not work.
The same code works as expected on a newly created SpriteVisual*.*

Hi @ratishphilip,
Can you provide some details on what you want to achieve? What build # are you on?
When I run your code I do see the grid and children to hide and play the animation. Here is the code
private void Button_Click(object sender, RoutedEventArgs e)
{
        var rootGridVisual = ElementCompositionPreview.GetElementVisual(contentGrid);
        var _compositor = rootGridVisual.Compositor;
        var scalarAnim = _compositor.CreateScalarKeyFrameAnimation();
        scalarAnim.InsertKeyFrame(0, 1f);
        scalarAnim.InsertKeyFrame(0.4f, 0.4f);
        scalarAnim.InsertKeyFrame(0.7f, 0f);
        scalarAnim.Duration = TimeSpan.FromSeconds(0.5);

        rootGridVisual.StartAnimation(nameof(rootGridVisual.Opacity), scalarAnim);

    }

I am on SDK 14295.
My Grid contains several rows and columns. Each of the cell contains a user control (which contains a border and a textblock).
I am able to run a scale animation successfully on the grid. It scales well. But it does not animate the opacity. I am trying to achieve the following:

animate the opacity to 0 while the grid scales up.
animate the opacity to 1 when the grid scales back to its original size.

I am using a scoped batch to execute the opacity and scale animations together.

Another difference I noted in your code is that you are assigning the compositor like this
var _compositor = rootGridVisual.Compositor;

whereas in my code I am initializing the compositor in the OnNavigatedTo override
protected override void OnNavigatedTo(NavigationEventArgs e)
        {
            base.OnNavigatedTo(e);

            InitializeComposition();
        }

private void InitializeComposition()
        {
            _compositor = ElementCompositionPreview.GetElementVisual(this).Compositor;
            ...
        }

Does that make a difference?

@ratishphilip assigning compositor either way should be fine. for opacity do you want to change opacity on each item in the grid or do you want to change opacity of the Grid itself? can you add a sample project for us to see what is going on?

Hi @ratishphilip, Update
we think you might be running into a bug that we had in 14295, which has been resolved in future builds and hence I'm not seeing this issue. You should see this fixed in coming flights.

I found the cause of the issue.
Within the scopedbatch animation I am setting the** Grid.IsHitTestVisible = false**. Due to this the opacity animation does not work.
If I comment that line of code, then opacity works!

Awesome! Closing down the issue.


WIP: support NumPy 2.0 : NEP 52 (Python API cleanup)

Work towards https://github.com/cupy/cupy/issues/8306.
The current checklist is

[x] make sure cupy imports with numpy==2.0.0rc1
[x] make sure pytest tests/cupy passes the collection stage
[x] make sure pytest tests/cupyx passes the collection stage
[x] make main cupy and numpy namespaces match
[x] make ndarray methods match
[ ] function/method signatures:

[ ] keyword-only parameters
[ ] device arguments to various functions (needs decision on the behavior)

[ ] match submodule namespaces:

[ ]  numpy.linalg
[ ] numpy.core,
[ ] numpy._lib
[x] numpy.exceptions
[ ] numpy.strings
[ ] numpy.dtypes is out of scope for this PR.

make main cupy and numpy namespaces match

Done, modulo

[ ] vecdot: is an enhancement
[ ] bitwise_count: is an enhancement
[ ] isdtype: did not touch dtypes yet
[ ] trapz/trapezoid --> numpy deprecated the former and renamed it to the latter. Can be done separately.

Details of namespace comparison is under the fold

```
In [1]: import cupy
In [2]: import numpy
In [3]: dnp = set([x for x in dir(numpy) if not x.startswith('_')])
In [4]: dcp = set(x for x in dir(cupy) if not x.startswith('_'))
In [5]: dnp.difference(dcp)
Out[5]:
{'False_',
'ScalarType',
'True_',
'apply_over_axes',
'asmatrix',
'bitwise_count',
'block',
'bmat',
'bool',
'busday_count',
'busday_offset',
'busdaycalendar',
'bytes_',
'char',
'character',
'clongdouble',
'complex256',
'core',
'ctypeslib',
'datetime64',
'datetime_as_string',
'datetime_data',
'dtypes',
'einsum_path',
'emath',
'errstate',
'f2py',
'flexible',
'float128',
'frompyfunc',
'fromregex',
'geomspace',
'get_include',
'getbufsize',
'geterr',
'geterrcall',
'histogram_bin_edges',
'info',
'insert',
'is_busday',
'isdtype',
'isnat',
'little_endian',
'long',
'longdouble',
'ma',
'matrix',
'matrix_transpose',
'memmap',
'nanpercentile',
'nanquantile',
'ndenumerate',
'nditer',
'nested_iters',
'object_',
'polyder',
'polydiv',
'polyint',
'rec',
'recarray',
'record',
'sctypeDict',
'setbufsize',
'seterr',
'seterrcall',
'show_runtime',
'spacing',
'str_',
'strings',
'test',
'timedelta64',
'trapezoid',
'typecodes',
'ulong',
'vecdot',
'void'}
In [6]: dcp.difference(dnp)
Out[6]:
{'ElementwiseKernel',
'RawKernel',
'RawModule',
'ReductionKernel',
'asnumpy',
'clear_memo',
'cuda',
'disable_experimental_feature_warning',
'fromDlpack',
'fuse',
'get_array_module',
'get_default_memory_pool',
'get_default_pinned_memory_pool',
'is_available',
'memoize',
'sparse'}

</details>

make ndarray methods match

Done modulo

[ ] ndarray.to_device: what should CuPy ndarrays do here?

```
In [1]: import cupy
In [2]: import numpy
In [3]: dnp = set(x for x in dir(numpy.ndarray) if not x.startswith('_'))
In [4]: dcp = set(x for x in dir(cupy.ndarray) if not x.startswith('_'))
In [5]: dnp.difference(dcp)
Out[5]:
{'byteswap',
'ctypes',
'getfield',
'itemset',
'newbyteorder',
'resize',
'setfield',
'setflags',
'to_device',
'tostring'}
In [6]: dcp.difference(dnp)
Out[6]:
{'cstruct',
'get',
'reduced_view',
'scatter_add',
'scatter_max',
'scatter_min',
'set',
'toDlpack'}
</details>

Paused to run locally tests from tests/cupy_tests folder. There are several classes of errors (some working notes are below the fold), the largest source of noise is NEP50 and dtype cast changes. I think I'll take a detour to implement NEP50 before proceeding with a list in the OP.

OK  binary_tests/

    core_tests/
        arrays of different dtypes
        float16 values

OK  creation_tests/
OK  cuda_tests/
    fft_tests/
        DeprecationWarning: `axes` should not be `None` if `s` is not `None` (Deprecated in NumPy 2.0).
        numerical differences for float32

    functional_tests/
        can_cast(scalars)
        arrays of different dtypes
        vectorize_reciprocal: tolerance violation

    indexing_tests/
      CuPy only, TypeError: Cannot cast int64 to uint8 in same_kind casting mode

OK  io_tests/

    lib_tests/
        dtypes differ, wrong values (overflow?)

    linalg_tests/
        cannot cast int64 -> uint64  (this is from cupy.random)
        float16 values fishy
        linalg.cross 3D not allowed in NumPy

    logic_tests/
      in1d is deprecated

    manipulation_tests/
        failing casts
    math_tests/
        NumPy only: OverflowError: Python integer -2 out of bounds for uint32

OK  misc_tests/
OK  padding_tests/
OK  polynomial_tests/
OK  prof_tests/

    random_tests/
       NumPy: TypeError: Cannot cast scalar from dtype('int64') to dtype('uint64') according to the rule 'safe'

   sorting_tests/
        actual CuPy errors (indexing?)

   statistics_tests/
        AssertionError: ndarrays of different dtypes are returned.
OK  test_cublas.py
OK  test_init.py
OK  test_ndim.py
    test_numpy_interop.py
        TestAsnumpy::test_asnumpy_blocking - cupy.cuda.memory.OutOfMemoryError
    test_type_routines.py
        TypeError: can_cast() does not support Python ints, floats, and complex because the result used to depend on the value.
OK  test_typing.py
    testing_tests/
        TestGenerateMatrix_param_7_{dtype=float16 : float16 values fishy

cross-ref https://github.com/numpy/numpy/issues/26370 : https://github.com/cupy/cupy/pull/8314/commits/bed24a3013beb92e2cf03a1c7a4d9173044afdca works around it, might be able to drop the workaround

Decision needed: numpy.in1d emits DeprecationWarnings. https://github.com/cupy/cupy/pull/8314/commits/39cdc5365c350d0b91d0178a7c2189574c613ccb does this:

stop testing cupy.in1d, only test cupy.isin
keep cupy.in1d in the public API.
do we want cupy.in1d also emit DeprecationWarnings? As is, it does not.

More generally, what is the CuPy action when NumPy deprecates something? (match the deprecation, just remove an API when numpy removes it, something else?)

@ev-br Could you resolve conflicts?

Continued in https://github.com/cupy/cupy/pull/8531 : the rebase here is too messy, and I borked the branch. It's easier to  send a new PR than to wrangle with git to salvage this branch.


Trying to install this. Checking the configuration via dev tool hits a message about invalid configuration
Error loading /config/configuration.yaml: mapping values are not allowed here
in "/config/spot-price.yaml", line 28, column 66
I'm using the following:
Home Assistant 2023.1.1
Supervisor 2022.12.1
Operating System 9.4
Frontend 20230104.0 - latest

Hello!
Not sure why this is happening. I tried loading the newest version from this repository and it seemed to work well with Home Assistant 2022.12.7. I will try upgrading to 2023.1.1 to see whether this causes some problems.

Yeah, I upgraded to Home Assistant version 2023.1.1 and the current version of this spotprices2ha seems to be working OK. "Check Configuration" in Developer tools returns "Configuration will not prevent Home Assistant from starting!" so this should be OK too.
How did you install this "spot-prices.yaml" file? Did you copypaste the whole file or the contents of the file?

As always it was user's fault.  Something happened when copied the yaml from github. Copypasted contents of the file and all good. Thanks for help!


Add Lisp team as maintainers of Lisp packages

Set the default value of the meta.maintainers attribute to the Lisp team for all packages in the Lisp ecosystem. Is this what we want?
This will apply to all "libraries" i.e. sbclPackages.*. "Programs" such as stumpwm or Nyxt, or the Lisp compilers themselves, already have maintainers
See #218870

Will it work as desired when args already has meta.hydraPlatforms?
If we want the entire team to have visibility, I would be in favour of replacing myself with the team for the Common Lisp implementations (and whatever Common-Lisp-adjacent you find me maintaining and consider in scope).

Will it work as desired when args already has meta.hydraPlatforms?

hmm right, it gets overridden

Both hydraPlatform and maintainers work now:  02cc867

Ok , I'll set the team in CL implementations too

I am happy to help maintaining lisp packages too, if you want.


Build/Data/Shader is not a directory

Hi, I've been trying to build this repository using the build.sh and build.py (tried both) however in both cases while the code successfully built, I end up with this Build/Data/Shader is not a directory error around the end, it seems like the Shader directory is missing from the Data folder
I can't tell if it's something that was supposed to get built during compilation or not

Ah yeah, those build scripts aren't ported yet, you can build through vscode though.

Install the CMake plugin and build from there first.
I'll try to resolve this.

Can I see the full terminal log when you're building this (on both build.sh and build.py)?

That's weird, it might've been a mistake on my end. Does running this command work out?
cmake -B Build && cmake --build Build -j$(nproc)

That's weird, it might've been a mistake on my end. Does running this command work out?
cmake -B Build && cmake --build Build -j$(nproc)

seledreams@seledreams-Predator-PH315-51:~/development/WickedEngine-Demo$ cmake -B Build && cmake --build Build -j$(nproc)
-- The C compiler identification is GNU 11.2.0
-- The CXX compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found Vulkan: /usr/lib/x86_64-linux-gnu/libvulkan.so
OpenImageDenoise not found, it will be disabled.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/seledreams/development/WickedEngine-Demo/Build
[  4%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/Debug.cpp.o
[  4%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/DirectorySnapshot.cpp.o
[  6%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/DirectorySnapshotDiff.cpp.o
[  8%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileSystem.cpp.o
[ 10%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/DirWatcherGeneric.cpp.o
[ 12%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileWatcher.cpp.o
[ 16%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileWatcherGeneric.cpp.o
[ 16%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileInfo.cpp.o
[ 18%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileWatcherCWrapper.cpp.o
[ 20%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileWatcherImpl.cpp.o
[ 22%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/Log.cpp.o
[ 24%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/Mutex.cpp.o
[ 26%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/String.cpp.o
[ 28%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/System.cpp.o
[ 30%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/Watcher.cpp.o
[ 32%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/Thread.cpp.o
[ 34%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/WatcherGeneric.cpp.o
[ 36%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/platform/posix/FileSystemImpl.cpp.o
[ 38%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/platform/posix/MutexImpl.cpp.o
[ 40%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/platform/posix/SystemImpl.cpp.o
[ 42%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/FileWatcherInotify.cpp.o
[ 44%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/platform/posix/ThreadImpl.cpp.o
[ 46%] Building CXX object Library/efsw/CMakeFiles/efsw.dir/src/efsw/WatcherInotify.cpp.o
[ 48%] Linking CXX shared library libefsw.so
[ 48%] Built target efsw
[ 55%] Building CXX object CMakeFiles/Dev.dir/Source/Resources_BindLua.cpp.o
[ 57%] Building CXX object CMakeFiles/Dev.dir/Source/RenderPipeline.cpp.o
[ 57%] Building CXX object CMakeFiles/Dev.dir/Source/Resources.cpp.o
[ 65%] Building CXX object CMakeFiles/Game.dir/Source/Resources_BindLua.cpp.o
[ 65%] Building CXX object CMakeFiles/Game.dir/Source/LiveUpdate.cpp.o
[ 65%] Building CXX object CMakeFiles/Game.dir/Source/Resources.cpp.o
[ 65%] Building CXX object CMakeFiles/Game.dir/Source/main_SDL2.cpp.o
[ 61%] Building CXX object CMakeFiles/Dev.dir/Source/BindLua.cpp.o
[ 69%] Building CXX object CMakeFiles/Game.dir/Source/Game.cpp.o
[ 69%] Building CXX object CMakeFiles/Game.dir/Source/BindLua.cpp.o
[ 71%] Building CXX object CMakeFiles/Game.dir/Source/RenderPipeline.cpp.o
[ 73%] Building CXX object CMakeFiles/Dev.dir/Source/LiveUpdate.cpp.o
[ 75%] Building CXX object CMakeFiles/Dev.dir/Source/Game.cpp.o
[ 77%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui.cpp.o
[ 79%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_demo.cpp.o
[ 81%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_draw.cpp.o
[ 83%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_tables.cpp.o
[ 85%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_widgets.cpp.o
[ 87%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_impl_sdl.cpp.o
[ 89%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/imgui_BindLua.cpp.o
[ 91%] Building CXX object CMakeFiles/Dev.dir/Source/ImGui/Widgets/ImGuizmo.cpp.o
[ 93%] Building CXX object CMakeFiles/Dev.dir/Source/Editor.cpp.o
[ 95%] Building CXX object CMakeFiles/Dev.dir/Source/main_SDL2.cpp.o
[ 97%] Linking CXX executable Game
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_Text(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:677:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
677 | CALL_FUNCTION_NO_RET(Text, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TextColored(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:686:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
686 | CALL_FUNCTION_NO_RET(TextColored, col, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TextDisabled(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:694:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
694 | CALL_FUNCTION_NO_RET(TextDisabled, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TextWrapped(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:702:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
702 | CALL_FUNCTION_NO_RET(TextWrapped, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_LabelText(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:711:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
711 | CALL_FUNCTION_NO_RET(LabelText, label, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_BulletText(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:719:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
719 | CALL_FUNCTION_NO_RET(BulletText, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TreeNode_3(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:270:30: warning: format not a string literal and no format arguments [-Wformat-security]
270 |     retType ret = ImGui::name(VA_ARGS);
|                   ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1195:1: note: in expansion of macro ‘CALL_FUNCTION’
1195 | CALL_FUNCTION(TreeNode, bool, str_id, fmt)
| ^~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TreeNode_3_3(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:270:30: warning: format not a string literal and no format arguments [-Wformat-security]
270 |     retType ret = ImGui::name(VA_ARGS);
|                   ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1204:1: note: in expansion of macro ‘CALL_FUNCTION’
1204 | CALL_FUNCTION(TreeNode, bool, ptr_id, fmt)
| ^~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TreeNodeEx_4(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:270:30: warning: format not a string literal and no format arguments [-Wformat-security]
270 |     retType ret = ImGui::name(VA_ARGS);
|                   ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1225:1: note: in expansion of macro ‘CALL_FUNCTION’
1225 | CALL_FUNCTION(TreeNodeEx, bool, str_id, flags, fmt)
| ^~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_TreeNodeEx_4_4(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:270:30: warning: format not a string literal and no format arguments [-Wformat-security]
270 |     retType ret = ImGui::name(VA_ARGS);
|                   ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1234:1: note: in expansion of macro ‘CALL_FUNCTION’
1234 | CALL_FUNCTION(TreeNodeEx, bool, ptr_id, flags, fmt)
| ^~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_SetTooltip(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1427:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
1427 | CALL_FUNCTION_NO_RET(SetTooltip, fmt)
| ^~~~~~~~~~~~~~~~~~~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h: In function ‘int impl_LogText(lua_State*)’:
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_BindLua.cpp:276:16: warning: format not a string literal and no format arguments [-Wformat-security]
276 |     ImGui::name(VA_ARGS);
|     ~^~~
/home/seledreams/development/WickedEngine-Demo/Source/ImGui/imgui_iterator.h:1718:1: note: in expansion of macro ‘CALL_FUNCTION_NO_RET’
1718 | CALL_FUNCTION_NO_RET(LogText, fmt)
| ^~~~~~~~~~~~~~~~~~~~
Error: Target (for copy_if_different command) "/home/seledreams/development/WickedEngine-Demo/Build/Data/Shader/" is not a directory.
gmake[2]: *** [CMakeFiles/Game.dir/build.make:203 : Game] Erreur 1
gmake[2]: *** Suppression du fichier « Game »
gmake[1]: *** [CMakeFiles/Makefile2:117 : CMakeFiles/Game.dir/all] Erreur 2
gmake[1]: *** Attente des tâches non terminées....
[100%] Linking CXX executable Dev
[100%] Built target Dev
gmake: *** [Makefile:136 : all] Erreur 2

Now the build script does not copy the build folder, instead left it as is from the previous task done by the cmake itself, which symlinks the Data folder to the one within Build folder.


VanitySlots instant crash upon load.

At first it was a critical injection failure and now the second log shows more than one error NoClassDefFound and ClassNotFoundExeption.
I disabled all other mods to isolate in order to find conflicts and it seems to be a code issue that I'm not sure how to resolve.
https://paste.ee/p/PTJjt

You need cloth config enabled as well.


[Communication]: Added error code assertion back into SMS test

/azp run python - communication - tests

/azp run python - communication - tests


Can't get property 'readonly' of node

Hello team,
Unsure if the following is a bug, or user-error on my part (most likely the latter!)
Thanks in advance for the help and thanks for building such an awesome tool!

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.19.0
Platform / OS version: macOS 10.12.6
Node.js version: 12.6

What steps will reproduce the problem?
test.html:
<!DOCTYPE html>
<html>
<head>
  <title>test</title>
</head>
<body>
  <input type="text" name="test" id="test" readonly="readonly">
</body>
</html>

index.js:
const puppeteer = require('puppeteer');
(async () => {
  const browser = await puppeteer.launch({ headless: false })
  const page = await browser.newPage()

  const node = await page.$('#test')

  const name = await node.getProperty('name')
  console.log(name._remoteObject)
  // { type: 'string', value: 'test' }

  const readonly = await node.getProperty('readonly')
  console.log(readonly._remoteObject)
  // { type: 'undefined' }

  await browser.close();
})();

What is the expected result?
console.log(readonly._remoteObject)
// { type: 'string', value: 'readonly' }

What happens instead?
console.log(readonly._remoteObject)
// { type: 'undefined' }

The IDL attribute name is readOnly (with capital O), not readonly, per https://html.spec.whatwg.org/multipage/input.html#dom-input-readonly. This fixes it:
-  const readonly = await node.getProperty('readonly')
+  const readonly = await node.getProperty('readOnly')


Workaround compatibility issue with nanoseconds fix

We recently (#289) updated this code to compare nanoseconds correctly, but we found some existing apps depending on the wrong order. This puts in a compatibility check (framework only) to restore the broken behavior until those apps have a chance to update.

@swift-ci test


feat: update select logic with spec similarity computation

Related to https://github.com/sustainable-computing-io/kepler-model-server/issues/216, this PR adds a logic to find a node_type from the spec information.
The idea is:

find exact node_type that equals or covers the machine spec
if not found, compute similarity between the machine spec and each node_type and select the most similar node_type
if more than one candidates with the same score, find uncertainty of selection (frequency of selected type over all candidates) and select the most frequent one.

This PR also updates the machine spec discovery in estimator to align with the kepler PR https://github.com/sustainable-computing-io/kepler/pull/1684. The updated logic is to first check availability of mounted spec first. If not available, apply the discover function.
Signed-off-by: Sunyanan Choochotkaew<EMAIL_ADDRESS>

Note that need to update ComponentModelWeights in kepler regressor module to unmarshal also the model_name field.

@sthaha thank you so much for the reviews. Made an update.
Also need the following PR in kepler to be merged first to support model_name attribute in weight file:

[ ] https://github.com/sustainable-computing-io/kepler/pull/1699.

1699 is merged, shall we merge this one now?

1699 is merged, shall we merge this one now?

I think we could but there are following things might be good to resolve first.
(i) I would like to have all green on test. I need some rerun the failed test due to the not-fixed-yet but known issue as raised in https://github.com/sustainable-computing-io/kepler-model-server/issues/247.
(ii) @sthaha may you check your comments are all resolved?
(iii) it might be good to see whether the compatibility is solved with the latest Kepler by having the following CI PR merged first.

[ ] https://github.com/sustainable-computing-io/kepler-model-server/pull/374


Add thorough product addition

Summary:
Adding more detailed product addition including its nutritional information, ingredients, EMB codes etc.
The designs which I plan to implement are :


FI-895/979/1003: US Core support cleanup

Initial attempts at a system that fully supports all the must support reference types
update validator
Bump synthea version
Additional mods to fix must support references
Fix some unrelated data issues
Updated Synthea.jar to master@50f4f58f. NOTE: COVID modules were removed before compilation
Bump logger level to :info to get rid of FHIRPath output
Remove vitalspanel, add dischargeDisposition to more things, add helper methods
Add some safety code to docref/diagnostic report handling
Add new observations for the DAR support, just in case they're the only observation of a given type
Delete a few more non-US-core resource types

I got an error in ruby, see below.  Maybe there is some gem you are assuming everyone has but haven't put in the Gemfile?
M6-PC:uscore-data-script rscanlon$ bundle install
Warning: the running version of Bundler (2.0.2) is older than the version that created the lockfile (2.1.4). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
Using concurrent-ruby 1.1.7
Using i18n 1.8.5
Using bcp47 0.3.3
Using bundler 2.0.2
Using coderay 1.1.3
Using date_time_precision 0.8.1
Using mime-types-data 3.2020.0512
Using mime-types 3.3.1
Using mini_portile2 2.4.0
Using nokogiri 1.10.10
Using fhir_models 4.1.0
Using method_source 1.0.0
Using pry 0.13.1
Using rb-readline 0.5.5
Bundle complete! 3 Gemfile dependencies, 14 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
M6-PC:uscore-data-script rscanlon$ bundle exec ruby uscore-data-script.rb mrburns
Generating Mr. Burns...
Generating Synthetic Patients with Synthea...
  Generated data in 25 seconds.
Loading FHIR Bundles...
  Loaded 43 FHIR Bundles in 1 minutes 26 seconds.
Selecting patients by constraints...
  Scoring Records...
    Selected: ["one_male", "one_elder", "elder_has_device", "has_allergy"]
  Scoring Records...
    Selected: ["has_pulse_ox"]
Selecting patients by profile...
  Scoring Records...
    Done.
  Selected 2 patients (1 seconds).
Modifying selected patients...
Traceback (most recent call last):
	4: from uscore-data-script.rb:151:in `<main>'
	3: from /Users/rscanlon/Projects/uscore-data-script/lib/modifications.rb:42:in `modify!'
	2: from /Users/rscanlon/Projects/uscore-data-script/lib/modifications.rb:42:in `each'
	1: from /Users/rscanlon/Projects/uscore-data-script/lib/modifications.rb:43:in `block in modify!'
/Users/rscanlon/Projects/uscore-data-script/lib/modifications.rb:683:in `get_resource_counts': undefined method `insert' for #<Hash:0x00007fea5b98d9e0> (NoMethodError)
Did you mean?  invert
               inspect
MM6-PC:uscore-data-script rscanlon$ ruby --version
ruby 2.5.6p201 (2019-08-28 revision 67796) [x86_64-darwin18]

Seems likely the above is caused because insert is a new method introduced after ruby 2.5.  I'll upgrade ruby and try again.  But we should state in the readme that you need a minimum version if we are using a feature introduced so recently.

VitalsPanel is not a clear requirement of US Core, and for g10 certification we are not testing it.  I thought we had discussed removing it from here.  Did we remove it and then you didn't clean it out all references to it, or does this not remove vitalspanel?
Ok if it doesn't remove vitalspanel -- we can move that to another ticket.  But if you did remove vitalspanel, make sure that this reference is also removed.
Final constraint testing...
  All constraints satisfied.
  Missing 1 profiles: ["http://hl7.org/fhir/StructureDefinition/vitalspanel"]

Yeah, vitalspanel has been removed, but I forgot to remove it in the checker. I'll pull it out of there.

RE: the insert issue: I think the reason this is wonky is that it used to be doing insert on an Array, but the type of resource_counts has changed back to a Hash during a refactor (I accidentally moved a .sort). Moving that back seems to have fixed it.

Built mrburns (there were 3 people created), uploaded them to my server , and ran against them, and I'm getting the following skips:
USCOBH-11: All must support elements are provided in the Observation resources returned. results...
Could not find dataAbsentReason in the 81 provided Observation resource(s)
Note this dataAbsentReason issue is on other Observations as well.
USCDR-13: All must support elements are provided in the DocumentReference resources returned. results...
Could not find content.attachment.url in the 190 provided DocumentReference resource(s)
USCCT-08: The server returns results when parameters use composite-or results...
Cannot find second value for status to perform a multipleOr search
Also, this skipped on missing references types, but that's fine because we will be pulling them out shortly.
Did you try running a generated set against the inferno program tests?  I may have done something wrong - which would be unfortunate, seeing how long it takes :)

I did test against program on my local machine, and was not seeing any of these issues. I'll investigate.


Please clearify admin UI usage (REACT or jsonConfig)

You specify admin UI to be materialize. On the other side you have an empty jsonConfig.json5 file.
New adapters shoul eithe ruse jsonConfig if the admin UI is ruther simple or react if there admin UI must be more complicated. If you want / must use react, jsonConfig files are obsolete. On the other side you asked for help with jsonCOnfig. In this case react should be removed...

If I remove the empty jsonConfig file then https://www.iobroker.dev/adapter-check  is complaining. Therefore I created if to be compliant.

Hello @mcm1957 , I do not get jsonConfig running.
In package.json I removed the scripts:
"build:react": "build-adapter react",
"watch:react": "build-adapter react --watch",
In io-package.json I switched to:
"adminUI": {
"config": "json"
},
I deleted index_m.html and custom_m.html.
Then added a file admin/jsonConfig.json with my three properties:
{     "i18n": true,     "type": "tabs",     "tabsStyle": {         "width": "calc(100% - 100px)"     },     "items": {         "_options": {             "type": "panel",             "label": "Adapter Settings",             "items": {                 "ip_address": {                     "type": "text",                     "label": "IP Address",                     "default": "<IP_ADDRESS>",                     "tooltip": "Enter the IP address of the device",                     "xs": 6,                     "sm": 6,                     "md": 6,                     "lg": 6,                     "xl": 6                 },                 "port": {                     "type": "number",                     "label": "Port",                     "default": 65534,                     "tooltip": "Enter the port number",                     "xs": 6,                     "sm": 6,                     "md": 6,                     "lg": 6,                     "xl": 6                 },                 "poll_interval": {                     "type": "number",                     "label": "Poll Interval (sec)",                     "default": 30,                     "tooltip": "Enter the polling interval in seconds",                     "xs": 12,                     "sm": 12,                     "md": 6,                     "lg": 6,                     "xl": 6                 }             }         }     } }
Now if I open the adapter settings on the screen an error is raised claiming "Cannot GET /index_m.html".
Any idea what is missing?

check adminUi property at io-package.json.
I can take a look later
I m on mobile only

Got JSON-Config working by deleting

index_m.html
style.css


CLI bundle command: add debug_mode and kernel flags

Context: https://github.com/0xPolygonMiden/miden-vm/pull/1445#discussion_r1713748940 and https://github.com/0xPolygonMiden/miden-vm/pull/1445#discussion_r1713778654
Currently, the bundle CLI command

creates a Library from a directory, and
automatically includes debug symbols.

It would be great if both were configurable: a --kernel flag would create a KernelLibrary instead of a Library, and a --debug flag would specify to include debug symbols (otherwise they wouldn't be).

I'd suggest making --debug the default, and require --debug=false or --no-debug (or something to that effect) to disable that default. Just like cargo/rustc do debug builds by default, and require specifically requesting release builds. We should probably encourage building with debug information, because without it, programs are exceedingly difficult to troubleshoot when something goes wrong in a procedure without that information.