How to enable user registeration?

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hi to all,
How can i enable user registration?
Thanks.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23
💻 Operating System and Arch
Rocky 9
🌐 Browser
Firefox
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

Self registration is tracked in https://github.com/louislam/uptime-kuma/issues/1638 and blocked by https://github.com/louislam/uptime-kuma/issues/128
Testing the assoicated PR and reporting the findings in the attached PR is appreciated. For further details see https://github.com/louislam/uptime-kuma/pull/3571

(forgot to close as resolved)


grandperspective: init at 3.0.1

Description of changes
Official description:

GrandPerspective is a small utility application for macOS that graphically shows the disk usage within a file system. It can help you to manage your disk, as you can easily spot which files and folders take up the most space. It uses a so called tree map for visualisation. Each file is shown as a rectangle with an area proportional to the file's size. Files in the same folder appear together, but their placement is otherwise arbitrary.

Project home page: https://grandperspectiv.sourceforge.net/
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1857

@SuperSandro2000 , thank you for the review. Should be OK now.


Unable to Run The Quickstart

I've already installed all the requirement and have tested it. The python bindings and openfoam adapter work well.  I also have installed the gymprecice library and it seems there is no problem. But when I tried to run the Quickstart, I met this problem.
I also check the tutorial case, I met the same error. There is no error in the fluid solver log.
I'm using WSL 20.04 and Python 3.8.10 for this.

I found the possible source of the error. pyprecice==<IP_ADDRESS> will produce this error even when not using gymprecice. The latest version (<IP_ADDRESS>) will solve this problem but there is incompatibility issues with the gymprecice module.

Since there's problem with the pyprecice <IP_ADDRESS> and there are some bugs with the gymprecice when using pyprecice <IP_ADDRESS>, this problem will be solved by installing pyprecice <IP_ADDRESS>rc2 instead. Need to update the dependencies requirement for pyprecice.

Many thanks for raising this issue. The segmentation fault is due to a breaking change in the recently released Cython v3.0.0. Please see the bug fix https://github.com/precice/python-bindings/pull/183. The problem can be simply resolved by adding cimport numpy to cyprecice/cyprecice.pyx in precice Python-binding.
Regarding OpenFOAMv2206, you need to explicity set writeControl, executeControl, executeInterval, rather than using the default configurations provided by `#includeEtc "caseDicts/postProcessing/forces/forceCoeffsIncompressible.cfg":
/*--------------------------------*- C++ -*----------------------------------*\
  =========                 |
  \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox
   \\    /   O peration     | Version:  v2206
    \\  /    A nd           | Website:  www.openfoam.com
     \\/     M anipulation  |
\*---------------------------------------------------------------------------*/

type            forces;
libs            ("libforces.so");

writeControl    timeStep;
executeControl  timeStep;
executeInterval 1;

log             off;

type        forceCoeffs;

rho         rhoInf;
rhoInf      1;

Hello, I am having a similar issue when trying to run the examples.  -DPRECICE_PETScMapping=off&& \
    make -j 16 && \
    make install

# Set PKG_CONFIG_PATH to include preCICE pkgconfig directory
ENV PKG_CONFIG_PATH /usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
RUN echo 'export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH' >> /etc/bash.bashrc

WORKDIR /workdir/

# number of cores to use for wmake
ENV WM_NCOMPPROCS 8

# get precice openfoam adapter
RUN wget https://github.com/precice/openfoam-adapter/releases/download/v1.2.3/openefoam-adapter-v1.2.3-OpenFOAMv1812-v2306-newer.tar.gz
RUN tar -xzvf openefoam-adapter-v1.2.3-OpenFOAMv1812-v2306-newer.tar.gz
WORKDIR /workdir/openefoam-adapter-v1.2.3-master/

# Source OpenFOAM bashrc and build precice adapter and make adapter
RUN . /usr/lib/openfoam/openfoam2212/etc/bashrc && \
    ./Allwmake

WORKDIR /workdir/

# install python libraries
COPY requirements.txt /workdir/requirements.txt
RUN pip install -r /workdir/requirements.txt
RUN pip install pyprecice==<IP_ADDRESS>rc2
RUN pip install gymprecice==0.1.0

and requirements.txt:
numpy==1.26.2
scipy==1.11.3
torch==2.1.1
gymnasium==0.28.0
pyprecice==<IP_ADDRESS>rc2

As you can see, I already tried with pyprecice==<IP_ADDRESS>rc2 as the previous comments, but I am getting a similar segmentation fault. Precice test are passed OK.
root@342ca8ca91a8:/workdir/host/tutorials/quickstart# python -u baseline_uncontrolled.py
No OpenFOAM tutorials? : /usr/lib/openfoam/openfoam2212/tutorials
No OpenFOAM tutorials? : /usr/lib/openfoam/openfoam2212/tutorials

...
The baseline case (no-controll) is running!
This task is expected to be completed in about 5 minutes on a system with two cores @ 2.10GHz.
...

[342ca8ca91a8:00264] *** Process received signal ***
[342ca8ca91a8:00264] Signal: Segmentation fault (11)
[342ca8ca91a8:00264] Signal code: Address not mapped (1)
[342ca8ca91a8:00264] Failing at address: 0x4f0
[342ca8ca91a8:00264] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f2bea481520]
[342ca8ca91a8:00264] [ 1] /usr/local/lib/python3.10/dist-packages/cyprecice.cpython-310-x86_64-linux-gnu.so(+0x302d8)[0x7f2b0dadb2d8]
[342ca8ca91a8:00264] [ 2] python(_PyEval_EvalFrameDefault+0x802)[0x55be82018f52]
[342ca8ca91a8:00264] [ 3] python(_PyFunction_Vectorcall+0x7c)[0x55be8203070c]
[342ca8ca91a8:00264] [ 4] python(_PyEval_EvalFrameDefault+0x802)[0x55be82018f52]
[342ca8ca91a8:00264] [ 5] python(_PyFunction_Vectorcall+0x7c)[0x55be8203070c]
[342ca8ca91a8:00264] [ 6] python(_PyEval_EvalFrameDefault+0x802)[0x55be82018f52]
[342ca8ca91a8:00264] [ 7] python(+0x16e4e1)[0x55be8203e4e1]
[342ca8ca91a8:00264] [ 8] python(_PyEval_EvalFrameDefault+0x6152)[0x55be8201e8a2]
[342ca8ca91a8:00264] [ 9] python(_PyFunction_Vectorcall+0x7c)[0x55be8203070c]
[342ca8ca91a8:00264] [10] python(_PyEval_EvalFrameDefault+0x802)[0x55be82018f52]
[342ca8ca91a8:00264] [11] python(_PyFunction_Vectorcall+0x7c)[0x55be8203070c]
[342ca8ca91a8:00264] [12] python(_PyEval_EvalFrameDefault+0x802)[0x55be82018f52]
[342ca8ca91a8:00264] [13] python(+0x239e56)[0x55be82109e56]
[342ca8ca91a8:00264] [14] python(PyEval_EvalCode+0x86)[0x55be82109cf6]
[342ca8ca91a8:00264] [15] python(+0x2647d8)[0x55be821347d8]
[342ca8ca91a8:00264] [16] python(+0x25e0bb)[0x55be8212e0bb]
[342ca8ca91a8:00264] [17] python(+0x264525)[0x55be82134525]
[342ca8ca91a8:00264] [18] python(_PyRun_SimpleFileObject+0x1a8)[0x55be82133a08]
[342ca8ca91a8:00264] [19] python(_PyRun_AnyFileObject+0x43)[0x55be82133653]
[342ca8ca91a8:00264] [20] python(Py_RunMain+0x2be)[0x55be8212641e]
[342ca8ca91a8:00264] [21] python(Py_BytesMain+0x2d)[0x55be820fccad]
[342ca8ca91a8:00264] [22] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f2bea468d90]
[342ca8ca91a8:00264] [23] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f2bea468e40]
[342ca8ca91a8:00264] [24] python(_start+0x25)[0x55be820fcba5]
[342ca8ca91a8:00264] *** End of error message ***

I think that, when working, the docker container would be a very useful starting point for other users too, as versions compatibility seems to be an issue.

Hi, Many tahnks for raising the issue. I agree with having a Docker/Singularity container to deal with the dependency issue. I will work on creating the container and aim to push it to the repository within the next few days.

That would be very helpful! Looking forward to it.

Hi, I have the same issue that @alsolera I will also appreciate a Singularity container. Thanks for the support.


update for new packages

@lavalamp where do these examples live.  They need some updates.

This change is

Oh, while I'm thinking about it.  This breaks a blind go get of everything in client-go.

Hm, we should probably make travis build these examples. I'll open an issue.
LGTM

FYI I've made similar fixes (which are obsolete now) and a few more cleanups in #61. Might be worth merging some of those changes too.


MinimongoError: The positional operator did not find the match needed from the query

Here's the code throwing this error:
        Meteor.defer(() => {
            Campaigns.update(
                {_id:nowPlaying,detail:{$elemMatch:detail}},
                {$set:{'detail.$.listened_for':length}}
            )
        })

This is executed server-side, not on client.
Here's the full log:
gxbsm
2021-02-11 19:40:53+02:00Exception in defer callback: MinimongoError: The positional operator did not find the match needed from the querygxbsm
2021-02-11 19:40:53+02:00 at MinimongoError (packages/minimongo/common.js:1087:17)gxbsm
2021-02-11 19:40:53+02:00 at findModTarget (packages/minimongo/local_collection.js:1947:17)gxbsm
2021-02-11 19:40:53+02:00 at packages/minimongo/local_collection.js:1160:24gxbsm
2021-02-11 19:40:53+02:00 at Array.forEach (<anonymous>)gxbsm
2021-02-11 19:40:53+02:00 at packages/minimongo/local_collection.js:1144:28gxbsm
2021-02-11 19:40:53+02:00 at Array.forEach (<anonymous>)gxbsm
2021-02-11 19:40:53+02:00 at Function.LocalCollection._modify (packages/minimongo/local_collection.js:1134:27)gxbsm
2021-02-11 19:40:53+02:00 at packages/zegenie:redis-oplog/lib/mongo/mutator.js:119:27gxbsm
2021-02-11 19:40:53+02:00 at Array.forEach (<anonymous>)gxbsm
2021-02-11 19:40:53+02:00 at Mongo.Collection.update (packages/zegenie:redis-oplog/lib/mongo/mutator.js:117:14)gxbsm
2021-02-11 19:40:53+02:00 at Mongo.Collection.update (packages/zegenie:redis-oplog/lib/mongo/extendMongoCollection.js:60:29)gxbsm
2021-02-11 19:40:53+02:00 at server/methods/listens.jsx:129:23gxbsm
2021-02-11 19:40:53+02:00 at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)gxbsm
2021-02-11 19:40:53+02:00 at packages/meteor.js:550:25gxbsm
2021-02-11 19:40:53+02:00 at runWithEnvironment (packages/meteor.js:1286:24)

Aaaah - positional operators! Meteor has an incomplete implementation in mini-mongo
How come it worked in dev, that call was never made?

I am taking a closer look as we speak - FYI

Great, thanks! Gonna add a few more errors. I didn't actually test this one properly it seems. I've been laser-focused on the chats not updating, and those were all working pretty smooth hehe.

Can you check your packages folder for the commit your are using of this lib?
mutator.js:117 has nothing offending in it in the current version
Thanks

Sorry spoke too soon -- this is the offending line
LocalCollection._modify(after, modifier)

Currently on 2.0.15. Only installed it for the first time a few hours ago :)

This is blocking me from using this package in a project. The offending query on my side is:
collection.update({
      _id: {
        $in: notificationIds,
      },
      'notifications.userId': this.userId,
    }, {
      $set: {
        'notifications.$.readOn': new Date(),
      },
    },{
      multi: true,
    });

Also tried with $elemMatch in the query:
collection.update({
      _id: {
        $in: notificationIds,
      },
      notifications: {
        $elemMatch: {
          userId: this.userId,
          readOn: {
            $exists: false
          }
        }
      }
    },{
      $set: {
        'notifications.$.readOn': new Date()
      }
    }, {
      multi: true
    });

Without the _id part in the query, so only the notifications part, it does work properly.
Had to revert to cultofcoders:redis-oplog to make this work.
Any progress on this issue yet @ramezrafla ?
Error in my case:
Exception while invoking method 'markNotificationRead' MinimongoError: The positional operator did not find the match needed from the query
    at MinimongoError (packages/minimongo/common.js:1087:17)
    at findModTarget (packages/minimongo/local_collection.js:1965:17)
    at packages/minimongo/local_collection.js:1160:24
    at Array.forEach (<anonymous>)
    at packages/minimongo/local_collection.js:1144:28
    at Array.forEach (<anonymous>)
    at Function.LocalCollection._modify (packages/minimongo/local_collection.js:1134:27)
    at packages/zegenie:redis-oplog/lib/mongo/mutator.js:116:27
    at Array.forEach (<anonymous>)
    at ns.Collection.update (packages/zegenie:redis-oplog/lib/mongo/mutator.js:114:14)
    at ns.Collection.update (packages/zegenie:redis-oplog/lib/mongo/extendMongoCollection.js:60:29)
    at ns.Collection.Mongo.Collection.<computed> [as update] (packages/aldeed:collection2/collection2.js:217:19)
    at MethodInvocation.markNotificationRead (imports/api/methods/notifications.js:12:31)
    at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1771:12)
    at packages/ddp-server/livedata_server.js:719:19
    at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)
    at packages/ddp-server/livedata_server.js:717:46
    at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)
    at packages/ddp-server/livedata_server.js:715:46
    at new Promise (<anonymous>)
    at Session.method (packages/ddp-server/livedata_server.js:689:23)
    at packages/ddp-server/livedata_server.js:559:43
RedisOplog: RaceDetectionManager started

@jasongrishkoff
Can you test pls with the new minimongo?

Hi @ramezrafla I actually stopped using this package back in February - there were too many issues, so I just went back to plain old oplog and scaled everything up. Unfortunately I can't test this for you :(

@ramezrafla it still does not work. I made a quick monkey patch (works for only simple case) for myself which looks like this:
mutator.js
116           let options = {}; 117            118           const positionalKey = Object.keys(updateSelector).filter(value => value.split('.').length > 1); 119           if (positionalKey.length === 1) { 120             const split = positionalKey[0].split('.'); 121             const valueToSearch = updateSelector[positionalKey]; 122             options.arrayIndices = [before[split[0]].findIndex(value => value[split[1]] === valueToSearch)]; 123           }    124              125           LocalCollection._modify(after, modifier, options);

FYI, was playing around with the package and can confirm this still isn't working for me either.

@jasongrishkoff
If I implement @Miraell 's fix above, will it work for you?

Same error with the monkey patch.  Code I'm firing looks kinda like this:
            var detail = {type:'listen',user:this.userId}
            History.update(
                {_id:id,detail:{$elemMatch:detail}},
                {$set:{
                    'detail.$.seconds':120,
                }}
            )

I'm having problems with the positional operator server side with:
Groups.update({"members.user_id": "asdfkjslea3q489"}, {$set: {"members.$.name": "New Name"}}, {multi: true})

The error is:
Error [MinimongoError]: The positional operator did not find the match needed from the query

Going to need to revert to cult-of-coders:redis-oplog for the time being, as there are too many positional operators used in my codebase.  Pity, because zegenie:redis-oplog gets the merging of published documents with different fields right (which cult-of-coders:redis-oplog doesn't).

@JackAdams
Could you test the monkey patch above (https://github.com/ramezrafla/redis-oplog/issues/9#issuecomment-985488735)
I don't use positional operators so can't test them.
If it works, I'll make the chance and push to production

Seems to have fixed the problem for me; no error and correct update made in the document in the db.  This being the case, I'm going to forge ahead with zegie:redis-oplog for now.  Thanks for all the work on this @ramezrafla , I really appreciate it.

Great!
We have been using this version of redis-oplog in production with tens of thousands of users simultaneously. So we know it works for our application. As new use cases come up, I'll try to incorporate without jeopardizing its mission to be scalable.
Will update and push to production shortly.

Out of interest, have you managed to have tens of thousands of concurrent users, with multiple subscriptions each, making frequent writes, and still use mongo unsharded?

Yes! That's the purpose of this package. No sharding yet. The cache within zegenie:redis-oplog dramatically reduces hits to the DB. Since each user is connected via websocket, we can keep their recurrent data. When we write to the DB, we don't need to repull (like original redis-oplog), we simply update the local cache.
Which brings the next question, with positional operators in place, please check that the data in the client is also updated (not just DB).

Happy to confirm that changes are being correctly propagated to the client after and update using the positional operator.

Super happy to hear about scalability. Even with cult-of-coders:redis-oplog the database was really hurting with a lot of users making frequent writes. (Full respect to Theo and his team, too, by the way -- redis-oplog was a huge step forward for Meteor scalability.)

Excellent! Theo handled a lot of the interfacing with redis and the internals of Meteor. There is a bit of hacking in there to override internal pub/subs. So he did all the heavy lifting.

@ramezrafla . Maybe hold of pushing that patch to production. I just did and have a lot of users reporting issues. Will update when I know more.

Been testing a bit and the fix for the issues I was seeing is to make sure it's an array, when trying to find the array index to use for positional operator. (This is because I was using a string of dot separated fields to query nested objects, not arrays, which is common enough, so the suggested fix to the patch below should definitely be used if this patch is going to production.)
let options = {};
const positionalKey = Object.keys(updateSelector).filter(value => value.split('.').length > 1);
if (positionalKey.length === 1) {
  const split = positionalKey[0].split('.');
  const valueToSearch = updateSelector[positionalKey];
  if (_.isArray(before[split[0]])) {
    options.arrayIndices = [before[split[0]].findIndex(value => value[split[1]] === valueToSearch)];
  }
}
LocalCollection._modify(after, modifier, options);

This code block replaces:
LocalCollection._modify(after, modifier)

Excellent @JackAdams
If that works, we can push in production.
I am not using the test suites, to simplify things. In hindsight, maybe a mistake.

I've pushed that modified patch to production and so far, so good.  I'll let you know if we run into any problems.

Okay. Better not put that patch into production. It seems to be giving some false positives for the old version of alanning:roles, which was a popular package and may still be in production in some apps. Given the way the data for the roles is structured in user docs I can sort of guess what's happening. I need to test a bit more.

I don't think it was anything to do with the patch, in the end. But this is really weird. On the mongo console:
meteor:PRIMARY> db.users.findOne({_id:"ZqRoBNapiGcQTtTBT", nonExistentField: "nonExistentValue"})
null

Which is what I expected. But in the mongo shell:
> Meteor.users.findOne({_id:"ZqRoBNapiGcQTtTBT", nonExistentField: "nonExistentValue"})
{
  _id: 'ZqRoBNapiGcQTtTBT',

Which shouldn't be happening at all.  This only happens when I've got Meteor.users.startCaching() in the server code.
Any idea what might be happening? (Note: this happens with or without the patch.)
I've just tested this with other collections and that seems to be consistent. As long as there's an _id that matches, it doesn't matter what other fields there are, the findOne method returns the document. This is not the case for find, which works as expected.


ERROR:root:Unpacking GTX3 exception

I am getting following exception for some of my gt3x files:
ERROR:root:Unpacking GTX3 exception: cannot reshape array of size 5120 into shape (40,3)
ERROR:root:Error rescaling log data: unsupported operand type(s) for *: 'NoneType' and 'float'

Please send a minimal working example or the data.

Unfortunately due to the sensitive nature of the gt3x file I am unable to share it. Here is the stack trace:
TypeError                                 Traceback (most recent call last)
SOME_PATH/site-packages/gt3x-0.1.1-py3.6.egg/gt3x/gt3x_functions.py in rescale_log_data(log_data, acceleration_scale)
472                 # apply scaling and return
--> 473                 return log_data * scale_factor
474         except Exception as e:
TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'
During handling of the above exception, another exception occurred:
...
...
---> 15         actigraph_acc, actigraph_time, meta_data = gt3x.read_gt3x(gt3x_filepath)
...
...
SOME_PATH/site-packages/gt3x-0.1.1-py3.6.egg/gt3x/gt3x_functions.py in read_gt3x(f, save_location, create_time, rescale_data, verbose, trim)
563
564         if rescale_data:
--> 565                 actigraph_acc = rescale_log_data(log_data = log_data, acceleration_scale = float(meta_data['Acceleration_Scale']))
566         else :
567                 actigraph_acc = log_data
SOME_PATH/site-packages/gt3x-0.1.1-py3.6.egg/gt3x/gt3x_functions.py in rescale_log_data(log_data, acceleration_scale)
474         except Exception as e:
475                 logging.error('Error rescaling log data: {}'.format(e))
--> 476                 exit(1)
477
478
NameError: name 'exit' is not defined

I can understand. Here is one example file which causes similar exception:
ERROR:root:Unpacking GTX3 exception: cannot reshape array of size 10544 into shape (30,3)
ERROR:root:Error rescaling log data: unsupported operand type(s) for *: 'NoneType' and 'float'
example_unpacking GTX3 exception.gt3x.zip


Fix typo mistake on calls to SSL_ctrl in ssl.h

Fixed typo mistakes on calls to SSL_ctrl in ssl.h

Note that this is really just cosmetics, but still useful, as the old names were confusing.

BTW, this should be cherry-picked back to 1.1.1, should it not.  @paulidale ?

I don't mind this going to 1.1.1.  It isn't a bug fix though.

I don't mind this going to 1.1.1. It isn't a bug fix though.

I don’t think our policy mandates ‚bugfixes only‘. It rather says ‚no new features‘. And typo fixes are improvements which don’t add new features. So +1 for cherry-picking.

These variable name typos serve as documentation, so in a sense they are fixing "documentation bugs" :-) I'd be ok with this going to 1.1..1

Good for 1.1.1 and master.

Merged to 1.1.1 and master.  Thanks for the contribution.


AfterGame overlay doesn't stretch all the way

Thus leaving few pixel of board underneath
You can see it on rigt side. It's especially visible with Classic board

Happens only in AI Game and in bigger screen sizes.


Weightconstraints created with create_only_btb or create_only_bfb do not behave as expected.

We have a project where we need weight constraints to propagate only in one direction. Weight constraints created with create_only_btb or create_only_bfb do not behave as expected. When constraints are created with create_explicit the constraint behaves as expected if only one thread is used.
With explicit disabled the result is as if bfb or btb are not given

add_weight_constraint(a, [(b, 1), (c, 1)], 1, bfb)

model
model a c
model a b
model a b c

add_weight_constraint(a, [(b, 1), (c, 1)], 1, btb)

model
model a c
model a b
model a b c

With explicit enabled the result is as expected

add_weight_constraint(a, [(b, 1), (c, 1)], 1, explicit+bfb)

model
model a
model a c
model a b
model a b c

add_weight_constraint(a, [(b, 1), (c, 1)], 1, explicit+btb)

model
model c
model b
model b c
model a b
model a c
model a b c

With threads and explicit enabled it fails completely

add_weight_constraint(a, [(b, 1), (c, 1)], 1, explicit+bfb)

random results

add_weight_constraint(a, [(b, 1), (c, 1)], 1, explicit+btb)

random results

Current workaround
To achieve btb, I currently add an auxiliary literal (bfb can be achieved by inverting l in the weight constraint):
l = add_literal()
add_clause([-a,l])
add_weight_constraint(l, [(b, 1), (c, 1)], 1, 0)

Of course this adds an unnecessary literal...

@rkaminsk
I addressed two obvious problems in dev. Could you please check whether things now work for you as expected?

Yes, this seems to work. In your commit you wrote that you cannot transform to clauses if only one propagation direction is requested. Wouldn't it be enough to only add "half" of the clauses?

I'm sure you are right and the commit is probably a little lazy. However, I'm not fully convinced that it's actually worth to complicate the code even further.


cluster-operator: recreate local harbor container registry CRD when missing

It's possible for users to accidentally delete all V1ContainerRegistry resources, including the one referencing the local Harbor.  Doing this would mean that all nodes will no longer be able to pull from Harbor.
I was thinking about dealing with in the neon-node-agent's container registry controller, but this seems better suited to neon-cluster-operator as part of it's cluster management role.  In this case, neon-cluster-operator would detect this and recreate the local container registry resource.

done


Added Arel::Nodes::InfixOperation to Visitors::ToSql#visit_Arel_Nodes…

PR to address https://github.com/rails/arel/issues/393 .
I'm thinking about adding tests for the other managers as well, I believe this change will benefit them too. For now I'll leave it as it is for verification from @drbawb and the the maintainers too. I can add more tests if the change is acceptable.

Per #523, Arel development is moving to rails/rails.
If this PR is still relevant, please consider reopening it over there.


Introduce heroku/jvm-standalone buildpack

Currently, the heroku/jvm buildpack can be used without any other buildpack. It will then install OpenJDK (and some Heroku specific related extras). This enabled customers to run any application that requires a JVM without needing to build their application with a buildpack.
The downside to this approach is that other buildpacks cannot use heroku/jvm in a conditional way. This wasn't a problem for the JVM buildpacks in this repository as they all required a JVM in any case. Heroku's Ruby buildpack is a different story. It doesn't require a JVM unless JRuby is used. With the current design, adding heroku/jvm to a "group" would always install OpenJDK, even when JRuby wasn't used.
This PR removes the ability to use heroku/jvm in a standalone fashion to enable other buildpacks to nicely compose.
For users that require the old behavior for their applications can now use the heroku/jvm-standalone buildpack instead. It uses the same code and is a drop-in replacement.
Open Tasks
Tasks that need to be completed before merging:

[ ] Create docker.io/heroku/buildpack-add-cnb-require-jdk repository
[ ] Create docker.io/heroku/buildpack-jvm-standalone repository

Closes GUS-W-13829430

Closing in favour of #546.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3238

Questions ?
Please refer to the Backport tool documentation


Adding Jenkins file for PPC64LE JDK11

Hi @oscerd to enable JDK11 jobs for power for camel- 3.x request to review and merge it

Camel 3 will be EOL soon. I would probably focus on 3.x or 3.22.x, btw I'll merge it later in the week

https://ci-builds.apache.org/job/Camel/job/Camel Build 3.21.x (ppc64le)/job/camel-3.21.x/


Docs for using SmartStreams w/ input parameters

Both writing a new filter and consuming w/ --extra-params is needed in the docs.
Will be referenced in TWiF 11.

We handle the development lifecycle for SmartModules with smdk now. Our how-to handles the usage of inputs and how they can be leveraged
https://www.fluvio.io/smartmodules/smdk/overview/


Improve readability

There are some conflicts due to the last changes. Would you inform me if your changes are done? I'll update this merge request after that.


IX Ag grid( ag-grid-community) version upgradation

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

Suggestion / feature request
Currently I am integrating the AG Grid (https://ix.siemens.io/docs/controls/grid) component with my application, I discovered that there is a dependency on an older version of the program (ag-grid-community).
I'm using the most recent versions of ag-grid-react and ag-grid-community, and I'm having some issues with the ix-aggrid version while using this.
Exception while installing packages:
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/ag-grid-community
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer ag-grid-community@"^28 || ^29 || ^30" from<EMAIL_ADDRESS>npm error node_modules/@siemens/ix-aggrid
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

duplicated of #1131


[ BUG ] TypeError: react_native_css_interop_1.StyleSheet.getFlag is not a function (it is undefined), js engine: hermes

Describe the bug
When I want to change the theme using the ThemeToggle component, I get the following error:
TypeError: react_native_css_interop_1.StyleSheet.getFlag is not a function (it is undefined), js engine: hermes
To Reproduce
Steps to reproduce the behavior:

Clone the starter-base app
Add ThemeToggle component wherever you want

Expected behavior
The theme should change smoothly.
Screenshots

https://github.com/user-attachments/assets/97300852-4384-467c-87ef-6ec216d7f111
Platform:

Type: [Emulator]
OS: [e.g. Android]

Additional context
/app/_layout.tsx:
import "~/global.css";

import { Theme, ThemeProvider } from "@react-navigation/native";
import { Slot, SplashScreen } from "expo-router";
import { StatusBar } from "expo-status-bar";
import { NAV_THEME } from "~/lib/constants";
import { useColorScheme } from "~/lib/useColorScheme";
import { PortalHost } from "@rn-primitives/portal";
import { useEffect, useState } from "react";
import { useFonts } from "expo-font";
import AuthProvider from "~/providers/AuthProvider";
import { GestureHandlerRootView } from "react-native-gesture-handler";
import { setAndroidNavigationBar } from "~/lib/android-navigation-bar";
import AsyncStorage from "@react-native-async-storage/async-storage";

const LIGHT_THEME: Theme = {
  dark: false,
  colors: NAV_THEME.light,
};
const DARK_THEME: Theme = {
  dark: true,
  colors: NAV_THEME.dark,
};

export {
  // Catch any errors thrown by the Layout component.
  ErrorBoundary,
} from "expo-router";

export const unstable_settings = {
  initialRouteName: "/",
};

// Prevent the splash screen from auto-hiding before getting the color scheme.
SplashScreen.preventAutoHideAsync();

export default function RootLayout() {
  const [isColorSchemeLoaded, setIsColorSchemeLoaded] = useState(false);

  const { colorScheme, setColorScheme, isDarkColorScheme } = useColorScheme();

  const [loaded, error] = useFonts({
    "Geist-Black": require("~/assets/fonts/Geist-Black.ttf"),
    "Geist-Bold": require("~/assets/fonts/Geist-Bold.ttf"),
    "Geist-Light": require("~/assets/fonts/Geist-Light.ttf"),
    "Geist-Medium": require("~/assets/fonts/Geist-Medium.ttf"),
    "Geist-Regular": require("~/assets/fonts/Geist-Regular.ttf"),
    "Geist-SemiBold": require("~/assets/fonts/Geist-SemiBold.ttf"),
    "Geist-Thin": require("~/assets/fonts/Geist-Thin.ttf"),
    "Geist-UltraBlack": require("~/assets/fonts/Geist-UltraBlack.ttf"),
    "Geist-UltraLight": require("~/assets/fonts/Geist-UltraLight.ttf"),
  });

  useEffect(() => {
    (async () => {
      const theme = await AsyncStorage.getItem("theme");
      console.log("🚀 ~ INITIAL LOADING THEME:", theme);

      if (!theme) {
        AsyncStorage.setItem("theme", colorScheme);
        setIsColorSchemeLoaded(true);
        return;
      }

      const colorTheme = theme === "dark" ? "dark" : "light";

      if (colorTheme !== colorScheme) {
        setColorScheme(colorTheme);
        setAndroidNavigationBar(colorTheme);
        setIsColorSchemeLoaded(true);
        return;
      }

      setAndroidNavigationBar(colorTheme);
      setIsColorSchemeLoaded(true);
    })().finally(() => {
      SplashScreen.hideAsync();
    });
  }, []);

  if (!isColorSchemeLoaded) {
    return null;
  }

  if (!loaded && !error) {
    return null;
  }

  return (
    <ThemeProvider value={isDarkColorScheme ? DARK_THEME : LIGHT_THEME}>
      <GestureHandlerRootView style={{ flex: 1 }}>
        <AuthProvider>
          <StatusBar style={isDarkColorScheme ? "light" : "dark"} />
          <Slot />
          <PortalHost />
        </AuthProvider>
      </GestureHandlerRootView>
    </ThemeProvider>
  );
}

I had a similar issue, I updated Nativewind to 4.0.36 and issue was solved. Give it a try!

I had a similar issue, I updated Nativewind to 4.0.36 and issue was solved. Give it a try!

That's what I came to write! Thanks..

For some reason this error occurs if you're on the 4.1 version of nativewind. Seems like a regression?


Extrude until contact/overlap

I'd like a way to run mesh.extrude() where it extrudes until contact with the previous mesh (and then stops on a point by point basis). Is there a way to do this? At the moment some parts exceed through the mesh.

Yes - I will try implementing it now.

I implemented this but i'm not sure if it works the intended way (i may not understand the vtk filter...):
https://vedo.embl.es/autodocs/content/vedo/vedo/mesh.html#Mesh.extrude_and_trim_with
Also there is another possibility by "sweeping" a Line along a spline:
from vedo import *

sphere = Sphere([-1,0,4]).rotate_x(25).wireframe().color('r')
circle = Circle([0,0,0], r=2, res=100).color('b6')

extruded_circle = circle.extrude_and_trim_with(
    sphere,
    direction=[0,-0.2,1],
    strategy="bound",
    cap=True,
    cap_strategy="intersection",
)

circle.lw(3).c("tomato").shift(dz=-0.1)

show(circle, sphere, extruded_circle, axes=1).close()

and:

from vedo import *

aline = Line(Circle().coordinates)
spline = Spline([(0,0,0), (1,1,1), (2,3,3), (1,1,4), (0,1,5)]).lw(5)
pts = spline.coordinates

surfs = []
for i in range(1, len(pts)-1):
    p0, p1 = pts[i-1:i+1]
    surf = aline.sweep(p1 - p0)
    surfs.append(surf)
surface = merge(surfs, flag=True)
surface.c("gold").lw(0.1).pickable(True)

show(spline, surface, aline, axes=1).close()

Oh I forgot the other option is to use Ribbon() and then merge the pieces the same way.


Improve naming of anonymous/class-in-function Modules

This provides a fix for #1223 where modules that are either anonymous or defined in function bodies now produce non-purely-numeric names.
This is an amalgamation of a fix proposed by @aswaterman (which actually is necessary to fix classes in modules) and the use of an _Anon prefix for anonymous modules.
This includes tests and more documentation for desiredName.

Related issue: Fixes #1223

Type of change: bug report | documentation

Impact: No functional change

Development Phase: implementation
Release Notes

Better naming of anonymous modules and modules defined in functions

@mergify backport 3.2.x


Keepalive connection hung up after 304 response

Bug in keepalive=transparent mode (default).
Workaround: start with key keepalive=nobackend.

Fixed by
2dddda66f25dc152d206ba3416944cb98c6ed287


Bug in Trapezoid Calculator

Describe the bug
Nothing is displayed correctly after clicking on Trapezoid calculator
Screenshots

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


Not able to find 'YOUR_MINECRAFT_GAME_LOCATION/config/better-respawn' to edit

In the fabric mods installation step 4:
After you launch the game, go to YOUR_MINECRAFT_GAME_LOCATION/config/better-respawn, and modify the properties file with ...

I am unable to find the file. Do I need to run the script and then edit it, or launch the game once before and then this file is generated?
I cannot see any config folder currently in my .minecraft folder location.

My experience was the config only shows up after I launched the mod-ed game for the first time.

I am unable to launch with azure login due to key error.
However I was able to start with a local LAN game, but I can't see the folder after that as well.

Please the better-respawn .jar file into the mods directory and launch the fabric mod game. Then you will see the config directory.

When you run java -jar fabric-installer-0.11.2.jar, look at the install location that it. Here is my example on MacOS.


['Transaction 3 has invalid value (expected 0, actual 2500).'] while get_account_data

What it means expected 0, actual 2500

Hey @rav1112 this message indicates that a transaction containing a signature fragment had a non-zero value amount.  This is not valid; see https://iota.stackexchange.com/a/936/283 for more info.

Yes because I have send the some iotas. So how can we avoid this as I need all the transactions.

@rav1112  I have a same problem. Can you solve it?


Handling multipart transmittances from 6s

Changes to the engines/six_s.py file to handle 6s outputs that now can provide separated upwards, downwards, direct and diffuse transmittance.
Note: parse_file function is specific to how we've changed the output files. The outputs are also specific to an edited version of 6s.
Separated 6s transmittance:

Total 6s transmittance from separated values and dev-branch total transmittance:

Comparisons to Modtran:
At low AOD

At high AOD

@evan-greenbrg As mentioned earlier, awesome work! Would you mind adding a few plots to this PR showing a comparison to MODTRAN-based multipart transmittances (similar to the ones you had in your slide deck)?

Added!

This is super helpful, thanks @evan-greenbrg .  What's left to go in this draft?

@pgbrodrick Mostly just discussion. That, and I was waiting to double check if there were changes to engines/sRTMnet.py that are needed to accommodate the new allocation into the multiipart lut keys.


test: add e2e test for kubelet configs

What type of PR is this?
/kind test
What this PR does / why we need it:
add e2e tests to ensure that passed in custom kubelet config is used to start kubelet service
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[x] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

There is another Test_Ubuntu2204DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig test that validates kubelet config. Maybe it worth adding seccomp validation there?

was contemplating about a new one or append to an existing one. the KubeletServingCertificate seems to be on vm tags rather than the kubelet custom configs. i am not sure why it contains customKubeletConfig to start with.
the intent is to populate the new e2e scenarios to focus on customKubeletConfig properties if that make sense.

blocking for CCOA

can i please get exception for this one? only touches e2e (i think)..

blocking for CCOA

can i please get exception for this one? only touches e2e.. and a bit unit test

please reopen the PR against the dev branch, after which we can approve and merge


fix: [SQLite3] Forge::modifyColumn() messes up table

Description
Fixes #8410
OCI8 test failure will be fixed in #8459
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

@dgvirtual Can you test this?

@dgvirtual Can you test this?

I will try today. Just

@dgvirtual Can you test this?

I would like to. How do I pull the changes into the code on my machine, what should I google for to find how its done?

@dgvirtual If you like CLI, I recommend https://cli.github.com/
gh pr checkout #8457

Of course you can get from my repository:
https://github.com/kenjis/CodeIgniter4/tree/fix-sqlite3-modifyColumn

Hi, so I rerun the routine that I applied when filing bug report #8410.
There is still one change that happens, and I am not sure how bad it is; default of column with TINYINT datatype changes from integer zero to string zero:
+----------------+----------+-------------+----------+---------+-------------+
|  Field Name      | Type       | Max Length | Nullable  | Default  | Primary Key |
+----------------+----------+-------------+----------+---------+-------------+
before:
| paid                 | TINYINT  |                     | No           | 0            | No               |
after (note col Default):
| paid                | TINYINT  |                      | No           | '0'          | No               |
Same happens if I change the type to INT or DECIMAL.

@dgvirtual Thank you for testing.
I've fixed.
Before modifyColumn():
CREATE TABLE `db_invoices` (
	`id` INTEGER PRIMARY KEY AUTOINCREMENT,
	`user_id` INT NOT NULL,
	`month` VARCHAR NOT NULL,
	`invoice_series` VARCHAR NOT NULL,
	`total` DECIMAL NOT NULL,
	`paid` TINYINT NOT NULL DEFAULT 0,
	`paid_date` VARCHAR NULL DEFAULT NULL,
	`created_at` DATETIME NOT NULL,
	`updated_at` DATETIME NOT NULL
)

After modifyColumn():
CREATE TABLE `db_invoices` (
	`id` INTEGER NULL,
	`user_id` INT NOT NULL,
	`month` VARCHAR NOT NULL,
	`series` VARCHAR NOT NULL,
	`total` DECIMAL NOT NULL,
	`paid` TINYINT NOT NULL DEFAULT 0,
	`paid_date` VARCHAR NULL DEFAULT NULL,
	`created_at` DATETIME NOT NULL,
	`updated_at` DATETIME NOT NULL,
	CONSTRAINT `pk_db_invoices` PRIMARY KEY(`id`)
)


MultiInput in sap.m.table with keyboardMode Edit

OpenUI5 version: tested with several versions, also 1.93
Browser/version (+device/version): Google Chrome Version 93.0.4577.82
Steps to reproduce the problem:

having a sap.m.table with keyboardMode = Edit
MultiInput in Columns
type something into the MultiInput and press Enter

What is the expected result?
the typed value should be a new token and the focus should still be inside the MultiInput, since i want to type in multiple values.
What happens instead?
the token is created but the focus is lost and the table changed the keyboardMode from Edit to Navigation.
i need the keyboardMode Edit to navigate through the table with tab. but i need the enter function to work with the MultiInput. Changing the keyboardMode is supposed to be with F2. why it has to change also the mode with enter? if this is working as intended, can you add another keyboardmode that hast the tab-navigation functionality but not the enter one ?

Hello @WiNNiep00h,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Patric

i saw the changes are in Ui5 1.96.0 and i tested it with the same testapplication but the behavior in my test case didn't change at all. Did you test the MultiInput inside a sap.m.table Column with keyboardmode "Edit" ? i tried to debug the MultiInput but the only thing i saw is that its never calling the "oEvent.setMarked();" inside the if case (the only thing you changed was adding the "this.getDOMValue()" in the if case)

Hi @WiNNiep00h ,
Could you share your test scenario?
Here's a sample which we made to test the issue: https://jsfiddle.net/evfpuso6/
Cheers

@d3xter666 in your example i was not able to add multible tokens into the MultiInput. i changed your example code to show you my problem: https://jsfiddle.net/g98m45dx/6/
in the "Test" Column you can add tokens into the MulitInput by submit the value with Enter. But if you do so, the keyboardMode of the table is changing from Edit to Navigation and the Focus is lost. if you press inside the Mutliinput again and add more tokens it is working in the Navigation Mode, but you can not change to the next row with Tab. i hope it is clear now what i mean. my wish would be that pressing Enter inside a MultiInput will not end the Edit Mode of the table.

Thanks for the snippet @WiNNiep00h !
Now the issue should be finally fixed with the latest changes in master branch :)


Obsoleted disease terms lost in diseaseToPhenotype dataset

As reported in a recent community post, some diseases that used to have disease2phenotype relationships (ETL code) don't have it anymore.
In the hpo-phenotypes.jsonl 22.09 input file we can find entries linked to an obsoleted ID ("ORPHA:217607") that the user has reported.
> gsutil cat gs://open-targets-data-releases/22.09/input/ontology-inputs/hpo-phenotypes.jsonl | grep '"Familial dilated cardiomyopathy"'

{"databaseId": "ORPHA:217607", "diseaseName": "Familial dilated cardiomyopathy", "qualifier": null, "HPOId": "HP:0001712", "references": ["ORPHA:217607"], "evidenceType": "TAS", "onset": null, "frequency": "HP_0040281", "sex": null, "modifiers": null, "aspect": "P", "biocuration": "ORPHA:orphadata[2022-06-11]", "resource": "HPO"}
{"databaseId": "ORPHA:217607", "diseaseName": "Familial dilated cardiomyopathy", "qualifier": null, "HPOId": "HP:0025169", "references": ["ORPHA:217607"], "evidenceType": "TAS", "onset": null, "frequency": "HP_0040281", "sex": null, "modifiers": null, "aspect": "P", "biocuration": "ORPHA:orphadata[2022-06-11]", "resource": "HPO"}
...

Because the ORPHA:217607 ID has been obsoleted in EFO, my impression is that we are dropping all the records.
Using the disease index we can rescue the obsoleted IDs in the same way that we rescue them for the purpose of evidence. An example of how the relevant ID is found in our disease index linked to MONDO_0016333 (with the annoying ORPHA == Orphanet conversion).
❯ gsutil cat 'gs://open-targets-data-releases/22.09/output/etl/json/diseases/*.json' | jq 'select(.id == "MONDO_0016333") | [{id:.id, obsoleteTerms:.obsoleteTerms}]'

[
  {
    "id": "MONDO_0016333",
    "obsoleteTerms": [
      "Orphanet_217607"
    ]
  }
]

Half-baked feature, bug or enhancement, depending on how you see it ;)

The PIS ingest human phenotype ontology from obolibrary and structures it without much transformation.
I would suggest to add a resolveDiseases step in the disease object generation, similar when ingesting disease/target evidence, to check if the provided disease identifier is an obsoleted id for an existing term. I know, I'm proposing to check against a dataset that is just being generated, so that's adds a bit of complexity.
I'm wondering if such logic could be abstracted so a "validation" step would be executed any time a disease is ingested by the ETL (regardless what data type of source it provides). It would prevent introducing discrepancies.

@JarrodBaker could you help us scope the task? would it require much work in the ETL?

@d0choa , I wonder whether we can close this issue, as it's related to a release from last year.

I'll close it, but if you think it's still relevant, please, feel free to re-open it.

https://community.opentargets.org/t/duplicated-diseases-in-22-06/702/5

This is newly opened bug report is related to this issue: https://github.com/opentargets/issues/issues/2929
Practically, etl needs to resolve disease in all datasets where we get disease information not only evidence.

@remo87 , would you mind getting together with @tskir to find out whether this is still relevant and what are the next steps?
Thanks!

@remo87 and @tskir , has there been any progress on this and is this still relevant?

very relevant unfortunately


Fix typo

a -> an

@changeworld : Thanks for your contribution! The author, @MarkusVi, has been notified to review your proposed change.


Update my ppp

Codecov Report
Base: 75.56% // Head: 75.56% // No change to project coverage :thumbsup:

Coverage data is based on head (dc49db8) compared to base (2c3d306).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #194   +/-   ##
=========================================
  Coverage     75.56%   75.56%
  Complexity      529      529
=========================================
  Files            77       77
  Lines          1543     1543
  Branches        179      179
=========================================
  Hits           1166     1166
  Misses          332      332
  Partials         45       45

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

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


New RPC/Utility.h contains declarations for Utility.cpp.

Extracted from an impending pull request...

@mtrippled @miguelportilla
Basically trivial.

:+1:

:+1:

Commit message is wrong, should read "declaration"

warning C4099: 'ripple::RPC::Coroutine::Impl'

The compile warning isn't connected to this change - it's been there for a few days and I already have a pull request to deal with it!  :-)

(Pushed a new commit with a better message....)

This doesn't really help anything yet why can't we include it in another future commit that uses it?

I pulled it out of a longer, unrelated change because it got in the way.  I don't actually have anything in line to use it.


Documentation about Deployment object is incorrect about .spec.selector

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
The documentation page about deployments states:

If specified, .spec.selector must match .spec.template.metadata.labels, or it will be rejected by the API.

I tested this and it's not the case. In fact, it's often very useful to have a different selector than the metadata labels, e.g. if you want to have something like a build_id (that changes every deployment) as a pod label.
This stackoverflow question is a good example: https://stackoverflow.com/a/39474037/42754
Proposed Solution:
I think it's as simple as removing the sentence? If you agree, then I raised a PR for it: https://github.com/kubernetes/kubernetes.github.io/pull/4348
Page to Update: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/
(for reference, I'm testing with Kubernetes v1.7)

This isn't valid. See #4348 for reason why.


python312Packages.azure-mgmt-cdn: 13.0.0 -> 13.1.0

Changelog: https://github.com/Azure/azure-sdk-for-python/blob/azure-mgmt-cdn_13.1.0/sdk/cdn/azure-mgmt-cdn/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 307670 run on x86_64-linux 1

2 packages failed to build:

azure-cli
azure-cli.dist

4 packages built:

python311Packages.azure-mgmt-cdn
python311Packages.azure-mgmt-cdn.dist
python312Packages.azure-mgmt-cdn
python312Packages.azure-mgmt-cdn.dist


Add support for Unicode symbols in prompt

Fixes #316

Thanks for the pull request :)

No problem! :)


CLC workflow for CDC NCIRD/DVD ONT & Illumina NEBNext Sequencing Protocol

@dmaccannell - i pulled together CLC workflows for both the CDC's Nanopore and CDC Illumina/NEBNext protocols that are in the CDC/DVID manual. These should be self contained, and run out of the box on CLCv20.
If anyone at CDC, PHL or elsewhere is using Clint's protocols and also uses CLC  - perhaps these will be useful.
CDC Nanopore Amplicon SARSCOV2 Protocol CLC Worklow v0.1.zip
CDC Illumina NEBNext SARSCOV2 CLC Workflow v0.2.zip
Any feedback is welcome. Readme/pdfs inside the zips have additional details.

I'll merge it in.


possible to convert xml to txt

OS:
PyQt version:

You may try this one.

I use this: https://github.com/Isabek/XmlToTxt

I use this: https://github.com/Isabek/XmlToTxt


Update book.py to conform with PEP 8

Thanks for the updates; I really appreciate it 👍 . I didn't get it into the last release as I just saw your PR, but I'm going to test changes now and merge them in :).

@codycodes hey, you need icon.png inside src if you symlink this folder to the workflows folder otherwise you will run out of icon. You should have in src everything is necessary to the workflow's bundle.

Also, why do you have two instances one instance of info.plist in src and another one in the root level? You just need it in src.

@xilopaint thanks for letting me know! I think I understand what you mean by symlinking now; to clarify though:
A dev can symlink the ./src folder to a "blank" alfred workflow folder (.../user.workflow*) as an easy way to start working on some code? This would make sense to me. I got confused when my icon vanished and I wasn't sure how to set this up. I'll add those changes in; thanks for catching this!


[PGE-176600623] Replace isLockedInFrame with utils.inIframe

Replace isLockedInFrame with utils.inIframe
#176600623

Question: should this be tested locally?

looks like related code was removed in https://github.com/sharethrough/Prebid.js/pull/1053 and is no longer needed


Fix #1478 - Project files are not being flushed to disk after being written

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Fixes #1478.
The proposed fix calls stream.write() rather than stream.end() to write the file's contents. Then it calls fs.fsync() and finally stream.end() to close the file.
On my test system, this affected some timings and revealed a race condition in the unit tests for nodes, which I traced down to the Flows startFlows() function being incorrectly stubbed away. The wrong object was used in the stub, causing the startFlows() function to still be called, but there was no corresponding call to stopFlows().
Checklist

[X] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[X] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage decreased (-0.08%) to 86.148% when pulling 4f71d7851bfc7e948a037c43f4b070f80c10d65c on jturner-22:master into 2b9aa94f3a4fd432f4fdbf82428d09d4b8f6d74a on node-red:master.

Coverage decreased (-0.08%) to 86.148% when pulling 4f71d7851bfc7e948a037c43f4b070f80c10d65c on jturner-22:master into 2b9aa94f3a4fd432f4fdbf82428d09d4b8f6d74a on node-red:master.

Coverage decreased (-0.07%) to 86.162% when pulling ea780238f45805e1f60be7a07ff704e474eede1e on jturner-22:master into 2b9aa94f3a4fd432f4fdbf82428d09d4b8f6d74a on node-red:master.

Coverage increased (+0.006%) to 86.234% when pulling 5dc654e64f72fc38915cbb2ffbd27b4c25048419 on jturner-22:master into 2b9aa94f3a4fd432f4fdbf82428d09d4b8f6d74a on node-red:master.

Coverage decreased (-0.07%) to 86.162% when pulling f6f1a608f8fa20ffd73229c032563f36618e63c9 on jturner-22:master into 2b9aa94f3a4fd432f4fdbf82428d09d4b8f6d74a on node-red:master.


Notify downstream services on unpublish

Trello Card

Content schema change in https://github.com/alphagov/govuk-content-schemas/pull/638.


Footnote precedes a reference to it

Description
Sometimes a footnote precedes a reference to it. For example:
= Lorem
#lorem(580)

== Ipsum
#lorem(10)#footnote[#lorem(20)] #lorem(2000)

Here, the reference to a footnote is located at Page 2, but the footnote itself is located at Page 1. As far as I know, a footnote should never precedes a reference to it. And so, if I understand correctly, this is a bug.

Reproduction URL
No response
Operating system
macOS
Typst version

[X] I am using the latest version of Typst

Yes, this is a bug. In complex scenarios, it is a bit hard (but possible, just not yet implemented) to avoid, but this case is rather simple, so it should definitely work.

Similarly this code :
#v(96%)

= Header #footnote[footnote]

Gives up this image :

It is reverse to the original example but similar issue : the footnote is present is at the next page of the position of the reference.

Similarly this code :
(...)
It is reverse to the original example but similar issue : the footnote is present is at the next page of the position of the reference.

This is different as that's related to footnotes' migration behavior, where the element where the footnote originally appeared is moved to the next page / column to ensure it appears together with the footnote entry, but there are times where (due to lack of space at the bottom, e.g. footnote entry is too long) this isn't possible. Still, your case seems simple enough that it should work - but I'd open a new issue for separate investigation.

I think this is a regression as the example works fine on 0.11, so I will mark it as such.

Minimal reproduction:
#set page(width: 10cm, height: 3cm, margin: 0.8cm)

Foot #footnote[foot] \ foot

I think it's related to orphan prevention; the first line fits in the first page, but moves to the second page due to \ foot (removing it keeps both the first line and the footnote in the same page).

Alright, I've managed to debug it a bit. Here's what's happening:

Without the footnote, both lines (/ the first two) fit, not triggering orphan prevention:
#set page(width: 10cm, height: 3cm, margin: 0.8cm)

Foot \ foot

Therefore, on the very first layout pass, as there are no known footnotes yet, both lines are laid out normally as separate frames, as they both fit. This calls distributor.frame which searches for footnotes in the lines, adding them to be placed as part of column insertions. This triggers a relayout.

The relayout triggered by the footnote shrinks the available space in the page by the height of the footnote entries section. This triggers the second line to move to the next page, which in turn triggers the first to move as well by orphan prevention - this triggers another relayout.

However, in this second relayout of the first page, despite both lines being moved to the next, the footnote is still pending to be placed in the first page, as it was never removed from column insertions, and so it is placed.

The two lines are then placed in the next page normally.

We can see that, ignoring the timeline of events, the main problem is that placing the lines is what's causing them to be moved in the first place; moving them to the next page wouldn't trigger this need, but then they wouldn't have had to be moved at all...
The minimal case I'm showing, in fact, is actually pathological, in the sense that text + footnotes cannot fit in one page, so the footnote variant cannot be upheld either way. But 0.11.1 arguably handles it better: the footnote is placed on the same page (which is weird; it should be moved), though it "fits" by not fitting (the first frame is empty and the text is automatically moved due to lack of space).

Even then, 0.12 exhibits the same problem for non-pathological cases, as shown.
#set page(width: 10cm, height: 5.3cm, margin: 0.8cm)

Foots

Foots

Foots

Foot #footnote[foot] \ foot

0.12:

0.11:

With that conclusion, we can find some other interesting cases:
#set page(width: 10cm, height: 6.3cm, margin: 0.8cm)

#box(height: 0cm)[a]

= a #footnote[abc]

= b #footnote[dominoes]

Foot #footnote[foot] \ foot

0.12:

0.11 (no stickiness so it's not as interesting...)

In fact, we no longer have to blame orphan prevention for this... sticky blocks are also affected in general. Main problem seems to be that we "remember" footnotes of moved things.
#set page(width: 10cm, height: 6.3cm, margin: 0.8cm)

#box(height: 0cm)[a]

= a #footnote[abc]

= b #footnote[dominoes]

#block(breakable: false, height: 3cm)

That all makes sense. I was aware of the possibility of this happening, just didn't realize that widow/orphan prevention would trigger it. :/


feat(dialog): add ariaLabel and focusOnOpen config options

Based on the discussion on https://github.com/angular/material2/pull/6360#discussion_r133581835, these changes add the ability to set the aria-label of a dialog, as well as the element that should be focus when the dialog is opened.

Rebased and reworked the PR so the focusOnOpen is a boolean @jelbourn. Users can still control what element gets focused first via the cdk-focus-initial attribute.

Addressed the feedback @jelbourn.


A checker workflow should only be associated with at most 1 other entry

We should add some constraints for this, and some nice UI messages.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-232

When a checker workflow is added to an existing tool/workflow, the checker is created from scratch. So when adding this way the checker should only ever be added to one entry. I'm not sure how the case could come about that the checker gets added to more than one entry.
We could add some code to check that the no workflow exists with the path we generate for the checker, and if one does then it fails. Again, this shouldn't happen.

https://github.com/dockstore/dockstore/pull/2714


Update readme and add a contributing section

Codecov Report

Merging #527 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #527   +/-   ##
=======================================
  Coverage   90.83%   90.83%
=======================================
  Files          79       79
  Lines        5422     5422
=======================================
  Hits         4925     4925
  Misses        318      318
  Partials      179      179

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 48065d5...61173cc. Read the comment docs.


Fetch ignition config from S3

Fixes https://takescoop.atlassian.net/browse/SEC-8
Instead of passing ignition config (which contains secrets) into EC2 instances via userdata (which is available within every k8s pod via EC2 metadata endpoint), we now pass in a ignition config as userdata which will download the actual ignition config from S3.

@bendrucker Any idea on how to test this? I can hook the commit in kubernetes repo and apply in playground. But I'd like to know whether there's a better way.

@bendrucker I managed to successfully run terraform plan on the existing playground cluster, which means that all syntax issues have been fixed. Will create a new cluster for deeper testing tomorrow.

We decide to postpone this task a sprint to focus on something else (e.g. SOC2). For my own record, testing to create a new cluster in playground failed
/app/environments/playground # terraform apply --target module.test-typhoon

......
Error: Error applying plan:

5 errors occurred:
	* module.test-typhoon.module.typhoon.module.workers.aws_iam_role_policy.worker_read_ignition_configs: 1 error occurred:
	* aws_iam_role_policy.worker_read_ignition_configs: Error putting IAM role policy read-ignition-configs: MalformedPolicyDocument: Resource test-typhoon-ignition-configs/worker.yaml must be in ARN format or "*".
	status code: 400, request id: eb9eed93-be6d-4cd5-a79f-011da3e17891

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[2]: 1 error occurred:
	* aws_route.accepter_to_requester.2: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/20 already exists.
	status code: 400, request id: dd6d4c16-3106-4266-8c1c-30d62267fe53

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[1]: 1 error occurred:
	* aws_route.accepter_to_requester.1: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/20 already exists.
	status code: 400, request id: e8dcaeb4-f84e-413d-9ff2-8d877c172e21

	* module.test-typhoon.module.typhoon.aws_autoscaling_group.bastion: 1 error occurred:
	* aws_autoscaling_group.bastion: "test-typhoon-bastion terraform-20200114173735200800000007": Waiting up to 10m0s: Need at least 1 healthy instances in ELB, have 0. Most recent activity: {
  ActivityId: "79e5be94-89fc-a741-5cff-b9f919513637",
  AutoScalingGroupName: "test-typhoon-bastion terraform-20200114173735200800000007",
  Cause: "At 2020-01-14T17:38:17Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.",
  Description: "Launching a new EC2 instance: i-0eeb4f77e048214dc",
  Details: "{\"Subnet ID\":\"subnet-080e0159b302a74d0\",\"Availability Zone\":\"us-west-2c\"}",
  EndTime: 2020-01-14 17:38:51 +0000 UTC,
  Progress: 100,
  StartTime: 2020-01-14 17:38:19.049 +0000 UTC,
  StatusCode: "Successful"
}

	* module.test-typhoon.module.peering_main.aws_route.accepter_to_requester[0]: 1 error occurred:
	* aws_route.accepter_to_requester.0: Error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/20 already exists.
	status code: 400, request id: 90589754-58c2-4806-819a-998436a278bb

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Error: failed to retrieve lock info: unexpected end of JSON input

@bendrucker I successfully created a playground cluster, was able to connect via bastion and to list pods. We can sign this off and wait for the next cluster migration!

@beyondbill If you resolve the conflicts here, happy to try to get this released!

@bendrucker All conflicts resolved!


Add Eric Karschner to Contributors list

@EricKarschner37, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


Open classpath attribute on toolchain

This should allow to specify own classpath loaded with different loaders
ie rules_jvm_external instead of jvm_maven_import_external used by this
repo
Fixes https://github.com/simuons/rules_clojure/issues/30

This PR moves toolchain_type to root package and renames it to toolchain


add sorting by distance to frontend

Closes #57

Sorry something weird happened to the action before https://github.com/lokalkauf/lokalkauf-frontend/actions/runs/85819096 so I had to repush to trigger another action. Therefore I had to add some random commit. If the Action is successful now this can be merged.


Native token -> TF Token (Ex: ibc denom)

Requests by YFoundry. Still needs cleanup work
Also going to remove balance option from other contract, makes things too complex for little upside

Going tp merge the 2 together (cw20 migrate + native-migrate). Since most logicis really similar & makes testing easier


feat(#major); aave v3; add metis

Test: https://andromeda.thegraph.metis.io/subgraphs/name/messari/aave-v3-metis

@ishraq8 can you QA this when you have a chance?
https://subgraphs.messari.io/subgraph?endpoint=https://andromeda.thegraph.metis.io/subgraphs/name/messari/aave-v3-metis&tab=protocol


RDK-35406 : XCAST unregisterApplications API

Reason for change:
XCAST unregisterApplications API
Test Procedure: None
Risks: Low
Change-Id: I205386a77bf5a20a08ba6012265e975d1804f2c8 Signed-off-by:Anooj Cheriyan<EMAIL_ADDRESS>

New PR created: https://github.com/rdkcentral/rdkservices/pull/3182


Feature request: Rework new-element creation flow

We should rework our current fairly rudimentary interface for creating new elements.
Context and Motivation
Implementation Plan

[ ] Show the full path of the element in the name box (almost like IntelliJ when you create a new element)

[ ] Beautify the element creation modal - refer to new project modal in IntelliJ

[ ] Clicking the plus + button in project explorer will open up the modal, where the right-clicking will not

[ ] CONSIDER Adding multi/nested context-menu for new element, change + to open modal to create new element instead

[ ] CONSIDER We can explore the design from VS Code dropdown in Settings that shows more information about the currently focused item in the dropdown, or Gmail when hovering on each Inbox folder

Also consider the following refactor at code-level

[ ] Restrict the usage of type classifier and consider using the element instead the only mechanism that really needs the type classifier is element creation, which we could refactor to have a plugin that produces a single configuration for the creation ceremony: e.g. type ElementCreatorConfiguration = { key: string; label: string; icon: React.ReactNode; ... }
[ ] Reorganize elements in the dropdown to create new elements: core elemtns goes first, but should be sorted alphabetically, extensions go later and sorted alphabetically as well
[ ] Remove ModelClassifierUtils


ONNX Export

I have been struggling to install vedadet on my local computer. I have encountered errors after the command pip install -v -e ., the error was about the CUDA. I spent an enormous amount of time trying to fix it, still didn't succeed. However, I was able to install, run and export to ONNX on Colab. Here is my simple code that I want to share with others:
https://gist.github.com/kanybekasanbekov/9b5c9293e26905255b29c421e881e129
I hope it will be useful to someone.

@kanybekasanbekov I still can not build on colab, could you upload and share your onnx file ? many thanks

hi, thank you @kanybekasanbekov . Can you share me your detect face code with that model onnx.


Commands do not work in headings

What do they need to work in headings?

See: https://tex.stackexchange.com/questions/528811/why-do-some-packages-not-work-in-section-titles
The general problem is that the text of each section title get written to the .toc file, and a problem often arises because most commands expand to something other than text. You can try putting \protected in front of the problematic command, but an example would be more helpful. (And it's a command not working in the section title, not a package.) –
Teepeemm
Feb 17, 2020 at 14:33
1
That's a standard issue: not all TeX macros are allowed in the argument of \section & Co when hyperref is loaded. You need \texorpdfstring, in your case \section{La vie au \texorpdfstring{\boldsiecle{ii} \BC}{iie av. J.-C}} or similar. The first argument is what will be typed in the pdf file, the second argument is the content of the bookmark. –
campa
Feb 17, 2020 at 16:06
2
Try \section[simple title for TOC]{My complicated title with macros} –
Fran
Feb 17, 2020 at 16:40


Default parameter in SFileAddFileEx

I had only been building against the 9.22 release and not master, so I had not run into this yet. However, in 4ad0bff21da0163917e1552960e6a43679586b89 a default parameter was added for SFileAddFileEx. Back in https://github.com/ladislav-zezula/StormLib/issues/11#issuecomment-32148918 you mentioned that default parameters were removed from the APIs due to making the StormLib interface C only. However, one seems to have sneaked in. This seems to be the only instance of this issue within the public API in master.

Hi. Yes, at certain time, someone wanted the public interface to be read-only. However, at current time, nobody has problems with the default parameter and for the sake of a compilability of a library that is no longer developed, I'll leave it as it it.

Fair enough. I'll just have to keep this in mind.


Bump @dcos/mesos-client 0.1.9

We thought we've resolved the issue, but that time bundle distribution messed up thus the old version persisted in the dist folder. With this bump I reassured that the updates went through.
Closes DCOS-19946

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Fail consistently on Jenkins
navigates to health tab [0fc].Node Health Tab [0fa] Navigate to tab [0fb] navigates to health tab [0fc]
"before each" hook for "filters by health [0fe]".Node Health Tab [0fa] Health Tab [0fd] "before each" hook for "filters by health [0fe]"
navigates to node detail page.Nodes Detail Page Navigate to node detail page navigates to node detail page
shows the contents of the Mesos sandbox.Tasks Table Task row Files tab shows the contents of the Mesos sandbox
"before each" hook for "correctly shows health".Tasks Table For a Service Running task without healthcheck "before each" hook for "correctly shows health"

But locally they pass
  (Tests Finished)

  - Tests:           341
  - Passes:          331
  - Failures:        0
  - Pending:         10
  - Duration:        14 minutes, 51 seconds
  - Screenshots:     0
  - Video Recorded:  true
  - Cypress Version: 0.19.1

Alfred test this

Alfred test this

Alfred test this

Alfred test this

Note: I made a commit to retrieve the expected data from the mesos master that fixed the tests.
But I notice that there is a WIP commit from @nLight which probably has to get fixed first and we'll have to override my commit since that should solve the issue that occurred.


Failed to get (Track 01)(-LBA) error.

AppVersion
32 bit, AnsiBuild, 20230413T211754
Describe the bug
Failed to get (Track 01)(-LBA)
Screenshots
AppVersion
32 bit, AnsiBuild, 20230413T211754
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
/c2 val3 was omitted. set [0]
valid extension was omitted. -> set .bin
CurrentDirectory
D:\audio\ALICE-001
WorkingPath
Argument: ALICE-001.bin
FullPath: D:\audio\ALICE-001\ALICE-001.bin
Drive: D:
Directory: \audio\ALICE-001
Filename: ALICE-001
Extension: .bin
StartTime: 2023-05-30T14:11:07+0900
Set the drive speed: 62266KB/sec
DiskSize of [D:\audio\ALICE-001]
Total:<PHONE_NUMBER>072 bytes
Used:<PHONE_NUMBER>056 bytes
---------------------------
Space:<PHONE_NUMBER>016 bytes
=> There is enough disk space for dumping
This drive (DVDR   PX-760A  ) supports [OpCode: 0xd8, SubCode: 1]
This drive (DVDR   PX-760A  ) supports [OpCode: 0xd8, SubCode: 2]
This drive (DVDR   PX-760A  ) supports [OpCode: 0xd8, SubCode: 8]
Checking reading lead-out -> OK
Checking SubQ adr (Track) 13/13
Checking SubRtoW (Track) 13/13
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -3298/   -5000
Failed to get (Track 01)(-LBA)
EndTime: 2023-05-30T14:11:51+0900
Disc title
Legend of Rance Kichiku Densetu (Soundtrack CD of Alicesoft Rance III Option set)
Disc ringcode
ALICE-001 SP-PUA
Log file
ALICE-001_20230413T211754.txt
ALICE-001_disc.txt
ALICE-001_drive.txt
ALICE-001_mainInfo.txt
Other text files are empty.
I ripped -5000 to -1149 by audio mode.
ALICE-001_subReadable.txt
LBA[-02328, 0xfffff6e8]: P[00], Q[010010021073002349004cff]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[00], Point[10], AMSF[02:10:73], StartTimeOfTrack[23:49:00]}, RtoW[Unknown[63], Unknown[63], Unknown[63], Unknown[63]]
LBA[-02327, 0xfffff6e9]: P[00], Q[020000000000000000002175]{Audio, 2ch, Copy NG, Pre-emphasis No, MediaCatalogNumber [             ], AMSF[     :00]}, RtoW[Unknown[63], Unknown[63], Unknown[63], Unknown[63]] <=== Absolute 0 sector with MCN!?
LBA[-02326, 0xfffff6ea]: P[ff], Q[01010000017400000001ba98]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[01], Idx[00], RMSF[00:01:74], AMSF[00:00:01]}, RtoW[Unknown[63], Unknown[63], Unknown[63], Unknown[63]]

Absolute 0 sector with MCN!?

Yes.
Uploaded. DiscImageCreator_test.zip

D:\audio\ALICE-001>D:\DiscImageCreator_test\Release_ANSI\DiscImageCreator cd E ALICE-001 48 /c2 /s 2
AppVersion
32 bit, AnsiBuild, 20230530T152632
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
/c2 val3 was omitted. set [0]
valid extension was omitted. -> set .bin
CurrentDirectory
D:\audio\ALICE-001
WorkingPath
Argument: ALICE-001.bin
FullPath: D:\audio\ALICE-001\ALICE-001.bin
Drive: D:
Directory: \audio\ALICE-001
Filename: ALICE-001
Extension: .bin
StartTime: 2023-05-30T15:48:27+0900
Set the drive speed: 8467KB/sec
DiskSize of [D:\audio\ALICE-001]
Total:<PHONE_NUMBER>072 bytes
Used:<PHONE_NUMBER>816 bytes
---------------------------
Space:<PHONE_NUMBER>256 bytes
=> There is enough disk space for dumping
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 1]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 2]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 8]
Checking SubQ adr (Track) 13/13
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8187/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8564/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8400/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8293/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8338/  -10000
Failed to get (Track 01)(-LBA)
Checking SubRtoW (Track) 13/13
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track) 13/13
Creating .scm (LBA) 164400/164400
No C2 errors
Moving .scm to .img
Creating cue and ccd (Track) 13/13
Creating bin (Track) 13/13
Creating (Track all).img
[F:ConcatenateFromPregapToLeadout][L:2989] GetLastError: 2, 指定されたファイルが見つかりません。

DiscImageCreator_test.zip

It seems fail between Track 00 reading and Track 01 (-LBA) reading.

More fixed.
DiscImageCreator_test.zip

Still not solved last 2 test versions.
ALICE-001 (Track 00).bin is generated, but ALICE-001 (Track 01)(-LBA).bin is not generated.
D:\audio\ALICE-001>D:\DiscImageCreator_test\Release_ANSI\DiscImageCreator cd E ALICE-001 48 /c2 /s 2
AppVersion
32 bit, AnsiBuild, 20230530T211530
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
/c2 val3 was omitted. set [0]
valid extension was omitted. -> set .bin
CurrentDirectory
D:\audio\ALICE-001
WorkingPath
Argument: ALICE-001.bin
FullPath: D:\audio\ALICE-001\ALICE-001.bin
Drive: D:
Directory: \audio\ALICE-001
Filename: ALICE-001
Extension: .bin
StartTime: 2023-05-30T21:34:31+0900
Set the drive speed: 0KB/sec
DiskSize of [D:\audio\ALICE-001]
Total:<PHONE_NUMBER>072 bytes
Used:<PHONE_NUMBER>160 bytes
---------------------------
Space:<PHONE_NUMBER>912 bytes
=> There is enough disk space for dumping
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 1]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 2]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 8]
Checking SubQ adr (Track) 13/13
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8277/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8035/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8532/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -8098/  -10000
Failed to get (Track 01)(-LBA)
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -7777/  -10000
Failed to get (Track 01)(-LBA)
Checking SubRtoW (Track) 13/13
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track) 13/13
Creating .scm (LBA) 164400/164400
No C2 errors
Moving .scm to .img
Creating cue and ccd (Track) 13/13
Creating bin (Track) 13/13
Creating (Track all).img
[F:ConcatenateFromPregapToLeadout][L:2989] GetLastError: 2, 指定されたファイルが見つかりません。

D:\audio\ALICE-001>D:\DiscImageCreator_test\Release_ANSI\DiscImageCreator cd E ALICE-001 48 /c2 /s 2
AppVersion
32 bit, AnsiBuild, 20230530T225943
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
/c2 val3 was omitted. set [0]
valid extension was omitted. -> set .bin
CurrentDirectory
D:\audio\ALICE-001
WorkingPath
Argument: ALICE-001.bin
FullPath: D:\audio\ALICE-001\ALICE-001.bin
Drive: D:
Directory: \audio\ALICE-001
Filename: ALICE-001
Extension: .bin
StartTime: 2023-05-31T06:55:29+0900
Set the drive speed: 0KB/sec
DiskSize of [D:\audio\ALICE-001]
Total:<PHONE_NUMBER>072 bytes
Used:<PHONE_NUMBER>752 bytes
---------------------------
Space:<PHONE_NUMBER>320 bytes
=> There is enough disk space for dumping
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 1]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 2]
This drive (DVDR   PX-760A   1.07 08/18/07  15:10     ) supports [OpCode: 0xd8, SubCode: 8]
Checking SubQ adr (Track) 13/13
Creating (Track AA).bin & .sub (LBA)   164499/  164499
Searching last non-zero byte (size)      0/235080
There is not non-zero byte in the (Track AA)
Creating (Track 00).bin & .sub, (Track 01)(-LBA).bin & .sub (LBA)    -7830/  -10000
There is non-zero byte in the (Track 01)(-LBA): -2088 byte => -522 sample
Last non-zero byte before (Track AA): -178489 byte => -44622 sample
Checking SubRtoW (Track) 13/13
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track) 13/13
Creating .scm (LBA) 164400/164400
No C2 errors
Moving .scm to .img
Creating cue and ccd (Track) 13/13
Creating bin (Track) 13/13
Creating (Track all).img
Hashing: ALICE-001.img
Hashing: ALICE-001 (Track 01).bin
Hashing: ALICE-001 (Track 02).bin
Hashing: ALICE-001 (Track 03).bin
Hashing: ALICE-001 (Track 04).bin
Hashing: ALICE-001 (Track 05).bin
Hashing: ALICE-001 (Track 06).bin
Hashing: ALICE-001 (Track 07).bin
Hashing: ALICE-001 (Track 08).bin
Hashing: ALICE-001 (Track 09).bin
Hashing: ALICE-001 (Track 10).bin
Hashing: ALICE-001 (Track 11).bin
Hashing: ALICE-001 (Track 12).bin
Hashing: ALICE-001 (Track 13).bin
EndTime: 2023-05-31T07:01:55+0900
ALICE-001.zip


Unclear where to place @SuppressWarnings("TopLevel")

Please document where to place @SuppressWarnings("TopLevel") in order to suppress the TopLevel warning. The warning message points at the package declaration in the file, where it cannot be placed.
It also tried to annotate the package in package-info.java, where @SuppressWarnings is forbidden, and the classes in the file for which the warning is generated, but this seems to have no effect.

I think someone reported this internally also - as you discovered, it can't be suppressed with @SuppressWarnings. The best option for now is to pass the flag -Xep:TopLevel:OFF.
Just out of curiosity, why can't the sources be moved to a path that matches the package declaration?

They can be moved, though in my case I prefer not to.
It is one small class with 5 subclasses. The superclass has the name of the file, the subclasses only exist to implement specific marker interfaces and are empty except for a constructor that calls the super constructor, no other code is in them. Thus they do not really warrant their own file and are better grouped with the superclass. Moving them to separate files would also clutter the package directory, and moving them to a separate package is no option because they are not public and should not be.
It is ok for me to pass the compiler option, though actually the warning is nice, it has let us find a different instance of multiple top-level classes that we actually want to avoid. I think annotating the top-level class(es) in the file would make sense to surpress the warning.
In any case, the documentation should be updated.

Ah, right. I'll update the documentation. The section in http://errorprone.info/bugpattern/TopLevel about suppression is auto-generated, and assumes there's always going to be an enclosing element.
And I think we can also make the check respect @SuppressWarnings if it's applied to the class.
For your example, can you use nested static classes instead of declaring the subclasses at the top level?
class Foo {
  private static class Bar extends Foo {}
}

Yes, I could used nested static classes. Maybe that is actually a good idea in my case, as it further reduces visibility (which might not always be wanted, but for me it is good). Thanks.


negation of failure should not be cut transparent

Hi,
I get two times false:

But according to the ISO core standard, the first query should
give false, and the second query should give true.

Basically (+)/1 should open a context like call/1, and then flip the result
from true to false, and from false to true. You can compare with GNU Prolog:

Fixed, thanks for the notice!

Do you think this is also fixed:

The expected result is also:

Fixed. Cuts inside goals of call/1 were not local to the goal. Thanks.

Nice!


Cannot pip install qiskit in empty conda env

Information

Qiskit version: 0.13.0
Python version: 3.7
Operating system: OSX

What is the current behavior?
ModuleNotFoundError: No module named 'numpy'
    **************************************************
    * numpy was not installed in your system.  Please run
    *     pip install numpy
    * before installing pyscf.
    **************************************************

However this is exactly what we tell people to do in the install instructions: https://qiskit.org/documentation/install.html
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

I'm having the same issue too, I installed numpy separately, now it's showing a runtime error
 ERROR: Command errored out with exit status 1:
     command: /home/tron/anaconda3/envs/quantum/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-4zrsxjjn/pyscf/setup.py'"'"'; __file__='"'"'/tmp/pip-install-4zrsxjjn/pyscf/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install-4zrsxjjn/pyscf/pip-egg-info
         cwd: /tmp/pip-install-4zrsxjjn/pyscf/
    Complete output (12 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-4zrsxjjn/pyscf/setup.py", line 245, in <module>
        raise RuntimeError
    RuntimeError
    ****************************************************************
    *** WARNING: BLAS library not found.
    * You can include the BLAS library in the global environment LDFLAGS, eg
    *   export LDFLAGS='-L/path/to/blas/lib -lblas'
    * or specify the BLAS library path in  PYSCF_INC_DIR
    *   export PYSCF_INC_DIR=/path/to/blas/lib:/path/to/other/lib
    ****************************************************************
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

hi,
can i look into this , if yes, kindly send a screenshot of the complete procedure(entered code) where the issue is getting created.

It's better using IBMQ Notebooks instead of using Anaconda

Have you tried to install numpy before because it was not installed in your system.
Try pip install numpy or pip3 install numpy.

@nonhermitian Clearly Qiskit requires a few python packages to be installed in order to work. Maybe we should update the documentation to include instructions for the prerequisites?

Yes, I believe the documentation needs updating.

The real bug here is probably in aqua's requirements list: https://github.com/Qiskit/qiskit-aqua/blob/master/setup.py#L42 and https://github.com/Qiskit/qiskit-aqua/blob/master/requirements.txt#L14 there are no precompiled binaries published on windows in general https://pypi.org/project/pyscf/#files which includes win64 and not just win32. Pip is trying to build pyscf from source which it can't do because pyscf isn't setup to make that easy (it will also likely fail later in the installation on a binary lib dependency).
To fix this we probably should fix the marker exclusion or just remove pyscf from the requirements list in aqua and get that staged for the next aqua release.

I think the pyscf as optional would be nice.


Add field org_name for custom organisation in plan record?

Please complete the following fields as applicable:
What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
3.0.3
Expected behaviour:
Filling in a custom organisation should not create an org,
but should remain "text" in the plan record
Actual behaviour:
filling in a custom organisation in a org field in the project detail page
creates a real org. It seems to be the main way to fill in this org_id field:
create an org, and then attach its foreign key to it. Now we have lots
of unmanaged orgs with texts ranging from "" to "I do not know".
Why not use the old way, i.e. add an extra (text) field org_name that can store
that custom org? A single field org_id seems like a simpler solution from a model
perspective, but it creates as many orgs as there are plans.
Of course that does not fix the old unmanaged orgs.
And you'll have to make a preference choice between org_id and org_name,
or just make sure (at model level) that only one is filled in.
Steps to reproduce:

Update your config so that restrict_orgs is set to true. This will prevent users from creating orgs.
We moved away from the old single field in the plans table because of the duplication of org names in that table (e.g. 'university of somewhere', 'University of Somewhere', 'U of Somewhere', etc.) and a desire to move towards the use of the ROR api to support machine actionable DMP functionality. At the time of development we did not think that users would be impatient and NOT select an item from the autocomplete or that they would start typing 'No funder' or 'I don't know' instead of just leaving it blank. Unfortunately it was quite common. The above flag prevents this going forward.
I'm in the process of cleaning up our system and can report that it is unfortunately a tedious and manual process. I have some scripts that you can use to help identify potential duplicates but it still requires a human to verify.

https://github.com/CDLUC3/dmptool/blob/9787013edac62b3cccc4181b85f1204eb5057e9d/lib/tasks/utils/org_cleanup.rake#L67

👍🏻 yes, that's the direction we're heading in the DMPTool in a few weeks. We have pulled the ROR DB down to a local table for faster access and have an autocomplete that references names in the ROR list as well as the orgs table. The user MUST select an item from the list or tick a checkbox saying that their org is not in the list. Once the tick that checkbox a hidden field is displayed that allows them to type one in. This way its a conscious decision.
If we can see it working well after a few months, we will contribute it back to this codebase

We have a similar issue: We set restrict_orgs=false to prevent new users signing up with rubbish organisations. However, we weren't aware of that this would also apply to the "Funder" field on the plan cover page. Sometimes, there can be quite 'exotic' funders, so free-text would be useful. Does anyone have an idea for a workaround?


feat: array ext with span

Feature Request
Describe the Feature Request
At the moment array ext mostly takes @Array, to be convenient it should also work with Span.
Will work on this whenever https://github.com/keep-starknet-strange/quaireaux/pull/74 is done.

Hey ! I would love to work on this one ! Can you specify the Span type please, I cant find it inside the doc.
Thanks

I found this one :
// Span.
struct Span {
snapshot: @Array
}
Let me know if its right

Hey,
Yep, it is that one.
We first need #74 to be merged, and it is still changing a bit, it is also linked to some bugs, so it could be that it'll take some time.
I also wrote in this issue that was going to work on it whenever 74 is solved/merged 🙁


fix: 支持创建时指定多个安全组

这个 PR 实现什么功能/修复什么问题:
支持创建时指定多个安全组
是否需要 backport 到之前的 release 分支:

release/2.10.0

/area region
/cc @swordqiu @yousong

Codecov Report

Merging #3598 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3598      +/-   ##
=========================================
- Coverage    6.96%   6.96%   -0.01%
=========================================
  Files         497     497
  Lines       83439   83463      +24
=========================================
  Hits         5813    5813
- Misses      77130   77154      +24
  Partials      496     496

Flag
Coverage Δ

#aFlag
6.96% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/cmdline/helper.go
46.36% <0%> (-0.22%)
:arrow_down:

pkg/mcclient/options/servers.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/guests.go
0.59% <0%> (-0.01%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0% <0%> (ø)
:arrow_up:

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 c06537e...d4e168e. Read the comment docs.

/lgtm

/lgtm

/approve

/approve