Errors in log file

Hey,
we experience since our upgrade to pipelinedb 0.8.3 the following error in our log file as soon as we do inserts to a stream:
ERROR:  could not open file "base/16384/16528": No such file or directory
We started from a fresh new initialized database directory. Do you need some more informations and/or a dump of our database directory to figure out more?
Best,
Sebastian

Hi @Degola,
Does this happen on every insert or sporadically? A couple of things would help us debug this:

More of the log output surrounding the specific error message, if any
Output of SELECT pipeline_version()
Output of SELECT * FROM pg_class WHERE oid = 16528

That should help us get started. Thanks!

Hey @derekjn,

More of the log output is the same message over and over again but before it starts. In between we have some messages like this (which are expected and handled properly):

ERROR:  duplicate key value violates unique constraint "events_country_product_id_unique_user_id"
DETAIL:  Key (product_id, unique_user_id)=(5603ff12dc9a75146c8b4567, 561d22881a136a75417b23d0) already exists.
STATEMENT:  INSERT INTO events_country (product_id, unique_user_id, insert_date, value) VALUES ($1, $2, $3, $4)

Output of SELECT pipeline_version():

analytics=# SELECT pipeline_version();
                                                                     pipeline_version
-----------------------------------------------------------------------------------------------------------------------------------------------------------
 PipelineDB 0.8.3 at revision d76a82f3d988ba5a483bc3b0a8ef43a0a6a07577 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit

Output of SELECT * FROM pg_class WHERE oid = 16528:

analytics=# SELECT * FROM pg_class WHERE oid = 16528;
    relname     | relnamespace | reltype | reloftype | relowner | relam | relfilenode | reltablespace | relpages | reltuples | relallvisible | reltoastrelid | relhasindex | relisshared | relpersistence | relkind | relnatts | relchecks | rel
hasoids | relhaspkey | relhasrules | relhastriggers | relhassubclass | relispopulated | relreplident | relfrozenxid | relminmxid | relacl | reloptions
----------------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+----------------+---------+----------+-----------+----
--------+------------+-------------+----------------+----------------+----------------+--------------+--------------+------------+--------+------------
 facts__country |         2200 |   16530 |         0 |    16385 |     0 |       16528 |             0 |        0 |         0 |             0 |             0 | f           | f           | p              | v       |        4 |         0 | f
        | f          | t           | f              | f              | t              | n            |            0 |          0 |        |
(1 row)

table events_country:

CREATE TABLE events_country (
  product_id VARCHAR(24),
  unique_user_id VARCHAR(24),
  insert_date TIMESTAMP WITH TIME ZONE,
  value VARCHAR(2),
  CONSTRAINT events_country_product_id_unique_user_id UNIQUE (product_id, unique_user_id)
);
CREATE INDEX events_country_unique_user_id ON events_country (unique_user_id);

table facts__country:

CREATE VIEW facts__country AS SELECT
  product_id::VARCHAR(24) AS value__product_id,
  unique_user_id::VARCHAR(24) AS value__unique_user_id,
  insert_date::TIMESTAMPTZ AS value__insert_date,
  value::VARCHAR(2) AS value__value
FROM
  events_country;

Hope that helps.

Can you also share any stream and continuous views definitions?

I can repro with:
create continuous view v as select count(*) from stream join facts__country f on stream.x::text = f.value__product_id;
insert into stream (x) select x from generate_series(1, 10) as x;

@Degola we just pushed a fix out for this. The release binaries will be updated in an hour or so. Thanks for reporting!

All published binaries have now been updated.

Awesome, thanks!


Analysis that store the height

Hi,
I've implemented an Analysis instance that stores the maximum height of the e-class:
instance Analysis Integer SRTree where
    makeA = evalHeight
    joinA h1 h2 = max h1 h2
    modifyA cl eg = eg

evalHeight :: SRTree Integer -> Integer
evalHeight = \case
    Bin _ e1 e2 -> 1 + max e1 e2
    Uni _ e1 -> 1 + e1
    Var _ -> 1
    Const _ -> 1
    Param _ -> 1

This doesn't work and I suspect the reason is the appearance of loops when applying saturation. But, inspecting the library code it feels like this should terminate, as I understand the first e-graph is built from the bottom of the tree to the root, storing the height information in each e-class. If I have a new e-node that will connect to an e-class creating a loop, it would simply add one to the height already stored in data.
Is there any place that it triggers a new recalculation and possibly enters a loop?

never mind, it actually works as intended. I'm getting a weird exponential growth because of another thing. I'll investigate and let you know if I figure it out

@folivetti thanks for looking into it more carefully :)
In these sorts of situations, I think it is a good idea to try and shrinken the example to pinpoint what exactly is making this go wrong (e.g. by commenting out rewrite rules...) even though it is still quite complicated.
Good luck, let me know if you find a problem


Human Inborn Errors of Immunity: 2022 Update. - Table 1

Part of https://github.com/monarch-initiative/mondo/issues/7362
Focussing on Table 1.
Spreadsheet to use is here: https://docs.google.com/spreadsheets/d/1PY5b4urSuz3tPvEjWflzV3R-up5OJTapzxB_rD3NwD8/edit#gid=0
Step 1 : Confirm high-level classification in Mondo
Step 2: Classify diseases based on Table 1 from PMID:35748970

Step 1: High-level classification in Mondo
Classification in [PMID:35748970]

Classification in Mondo

Sabrina's questions (I have a path forward depending on the answers):

Mondo classification: where should "inborn error of immunity" be classified? Should it be under 'immunodeficiency disease' (OMIMPS:300755) instead of 'immune deficiency disease' (OMIM:242850)?

Please confirm that "combined immunodeficiency" is a "inborn error of immunity"

The following terms are not in the publication. Are these terms used in the literature/medical world?

non-SCID combined immunodeficiency
T+ B+ severe combined immunodeficiency

@pnrobinson and @ahamosh,
Could you please answer the 3 questions above? Thank you!

242850 is an edge case garbage entry in OMIM.  I will try to get Joanna to throw it out.  The OMIMPS:300755 is the big PS for immunodeficiencies, but doesn't include the SCIDs, which are PS601457.  Both phenotypic series are inborn errors of immunity. Non-SCID combined immunodeficiencies is what they are calling combined immunodeficiencies. I haven't seen that term in the literature lately  T+B+ immunodeficiency is general not so severe as to be a SCID.

There should be a top level term called inborn errors of immunity, but this is not a child of immunodeficiency, it is vice versa
Why are the separate terms immunodeficiency and immune deficiency? Please merge

Thank you for the quick answer, @ahamosh and @pnrobinson

Why are the separate terms immunodeficiency and immune deficiency?
This is related to this issue where we found conflicting information about these terms being actually the same concept.

I think I have enough information to move forward. Thank you!

Step 1 TO DO
To do:

[ ] obsolete 'immune deficiency disease' MONDO:0009453 (OMIM:242850) based on “historical disease”
[ ] ‘inborn error of immunity' (MONDO:0003778) should have “exclude subclass” - immunodeficiency disease (MONDO:0021094)
[ ] ‘inborn error of immunity' (MONDO:0003778) should be child of 'immune system disorder' (MONDO:0005046)
[ ] merge terms representing SCID grouping terms: MONDO:0031520 (OMIMPS:601457) and MONDO:0015974
[ ] 'severe combined immunodeficiency' (MONDO:0015974) should be child of 'combined immunodeficiency' (MONDO:0015131) - note it should already be
[ ] Obsolete ‘non-SCID combined immunodeficiency' (MONDO:0018814) based on it being a grouping term that is not used in the literature. (note that all children would become children of  'combined immunodeficiency' (MONDO:0015131)
[ ] Obsolete ‘T+ B+ severe combined immunodeficiency’ (MONDO:0044201) based on it being a grouping term that is not used in the literature. (note that all children would become children of  'combined immunodeficiency' (MONDO:0015131)

Step 2: Classify diseases based on Table 1 from PMID:35748970

[ ] All diseases in sub-table 1 (T-B+ Severe Combined Immune Deficiency (SCID)) should be children of 'T-B+ severe combined immunodeficiency' (MONDO:0044200)
[ ] All diseases in sub-table 2 (T-B- SCID) should be children of 'T-B- severe combined immunodeficiency' (MONDO:0017855)
[ ] All diseases in sub-table 3 (Combined Immunodeficiency (CID), Generally Less Profound than SCID) should be children of 'combined immunodeficiency' (MONDO:0015131)

Note:

some of the OMIM numbers in the table are a mixed bag of phenotypes and genes
If some Mondo diseases are currently under the 'severe combined immunodeficiency' (MONDO:0015974), but are not in subtable 1 or 2: the MONDO:0015974 parent should be removed, and these terms should probably be under  'combined immunodeficiency' (MONDO:0015131)***
- if these are not mentioned at all in table 1, the terms should be investigated to determine whether these are  ‘inborn error of immunity' (MONDO:0003778)


Don't fire again until success on previous request

This should probably not just keep firing when content is delayed from loading/rendering as is the case with any network calls.
Should we watch for SUCCESS events and block until then?

I had the same issue, it's not perfect but I've implemented a delay property you can pass to your component. It will wait before re-attaching the scroll handler and triggering the next loadMore call.
https://github.com/flocks/react-infinite-scroll
<InfiniteScroll
   delay={1500}
   hasMore={this.props.hasmore}
   loadMore={this.getNextPage}
   pageStart={1}
>

delay is in milliseconds.


Deepspeed checkpoints are completely undertrained

Hey @kohya-ss and @BootsofLagrangian
Thank you for your hard work on Deepspeed integration!  As I see this feature in dev branch.
I tried to use deepspeed in my pipelines but got some issues.
It seems that result checkpoints are undertrained with deepspeed. Can it be related to non-synchronised gradients issue? I'm currently in dev branch with the latest version.
Here is one image in dataset:

And here are results of same setting with and without deepspeed:

The difference between these 2 versions only in 3 flags:
--deepspeed --zero_stage=2 --offload_optimizer_device="cpu"

and accelerate reconfiguration.
I'm using 3xH100 gpus for experiments and LION optimizer. And in my understanding this result seems like it was actually trained on 1 GPU (but all 3 gpus was utilized 100%)

First, thanks to report issue. Is there similar phenomena on different dataset?

@BootsofLagrangian yes, on all datasets when using LION optimizer.
I'm not sure, maybe LION optimizer should not work as good as Adam's optimizers with Deepspeed... But it doesn't break a training process so I expect it to work...

@BootsofLagrangian yes, on all datasets when using LION optimizer. I'm not sure, maybe LION optimizer should not work as good as Adam's optimizers with Deepspeed... But it doesn't break a training process so I expect it to work...

Yes, DeepSpeed officially supports Adam, AdamW and Fused Adam only. The behavior of other optimizer is unpredictable.
Can you try DeepSpeed with Adam or AdamW? not 8bit or bitsandbytes family.


restart-explorer: fix extract_dir

it was missing extract_dir

Closes #9660

Relates to https://github.com/ScoopInstaller/Extras/pull/9701

[X] I have read the Contributing Guide.

/verify


Polkadot Vault. Onboarding with multiple keys - broken ui

Description

test data:
https://github.com/user-attachments/assets/d1829bed-f3c6-4150-8dd5-3a2ccbeb7c06
Environment
https://github.com/novasamatech/nova-spektr/commit/2815bd75d37e585a2acca65c5110c33d0fe83767

Status verification: ✅


Add average choice to load extension

This commit adds a functionality to choose if one wants to see 1, 5 or
15 minutes average.
Resolves issue #604

Nice work, @tadeoos! The feature is well-implemented, you documented it, and filed it against next.
Thanks for the contribution, and welcome to P9k!


Sever-side testing issue with SimpleSchema in Velocity

Hi. I'm using the more or less "standard" meteor schema validation  package aldeed:simple-schema with the no less "standard" testing package Velocity (mocha syntax).
I'm using tap-i18n in the fields labels like so (CooffeScript):

Authors.attachSchema(new SimpleSchema(
    'firstName':
        type: String
        max: 100
        label: -> TAPi18n.__('author_firstName_label')
    'lastName':
        type: String
        max: 100
        label: -> TAPi18n.__('author_lastName_label')
))

Everything is working fine, in both English and French, except for server-side testing. Here's the mocha tests log:

[velocity-mirror] Mirror is initializing...
SETUP GLOBALS
Warning: language en is not supported in this project, fallback language (en)
/home/laurent/.meteor/packages/meteor-tool/.<IP_ADDRESS>y1ep5f++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
throw(ex);
^
TypeError: Object # has no method 'en'
at Object.__ (packages/tap:i18n/lib/tap_i18n/tap_i18n-server.coffee:28:16)
at __ (both/collections.coffee:14:11)
at Object.Authors.attachSchema.SimpleSchema.firstName.label (both/collections.coffee:76:13)
at packages/aldeed:simple-schema/simple-schema.js:826:1
at Array.forEach (native)
at Function..each..forEach (packages/underscore/underscore.js:105:1)
at [object Object].SimpleSchema.getDefinition (packages/aldeed:simple-schema/simple-schema.js:824:1)
at checkObj (packages/aldeed:simple-schema/simple-schema-validation.js:217:1)
at packages/aldeed:simple-schema/simple-schema-validation.js:262:1
at Array.forEach (native)

Looks like i18n can't find the json translation files, even the default english one. I tried everything and ended up creating a symbolic link from my en.i18n.json file to my /private directory with  the following code as an ugly workaround:

if Meteor.isServer and process.env.IS_MIRROR
    translation = JSON.parse(Assets.getText('en.i18n.json'))
    __ = (key, options) -> translation[key]
else
    __ = TAPi18n.__

Authors.attachSchema(new SimpleSchema(
    'firstName':
        type: String
        max: 100
        label: -> __('author_firstName_label')
    'lastName':
        type: String
        max: 100
        label: -> __('author_lastName_label')
))

Note that TAPi18n.loadTranslations({en: translation}) wouldn't work either.
Any idea how to fix that in a nice way?

Hi,
This should be fixed in v1.5.
Please checkout v1.5 branch to your /packages directory and let me know if it works for you.
Thanks,
-Daniel
Meteor Developer

I'd love to try and let you know the result, but I'm new to Meteor and I couldn't find documentation on how to install a specific branch of a package. Cloning the repository in /packages directory and checking the v1.5 branch out apparently wasn't the way to do it. Any link to a doc or a tutorial ?

I found out how to build locally from source. v1.5rc2 branch fixed this issue. Thanks! :+1:

Hi,
I've the same problem.
@laurentpayot, can you tell me how to build locally from source ?
Thanks !
Cammille.

FYI, by the end of the week v1.5 will be published.
-Daniel
On Mon, Jun 8, 2015 at 9:41 PM, Cammille<EMAIL_ADDRESS>wrote:

Hi,
I've the same problem.
@laurentpayot https://github.com/laurentpayot, can you tell me how to
build locally from source ?
Thanks !
Cammille.
—
Reply to this email directly or view it on GitHub
https://github.com/TAPevents/tap-i18n/issues/65#issuecomment-109999105.

Thank you for this information ! I will wait for v1.5...
Cammille
On Mon, 8 Jun 2015 at 18:59 Daniel C<EMAIL_ADDRESS>wrote:

FYI, by the end of the week v1.5 will be published.
-Daniel
On Mon, Jun 8, 2015 at 9:41 PM, Cammille<EMAIL_ADDRESS>wrote:

Hi,
I've the same problem.
@laurentpayot https://github.com/laurentpayot, can you tell me how to
build locally from source ?
Thanks !
Cammille.
—
Reply to this email directly or view it on GitHub
<https://github.com/TAPevents/tap-i18n/issues/65#issuecomment-109999105
.

—
Reply to this email directly or view it on GitHub
https://github.com/TAPevents/tap-i18n/issues/65#issuecomment-110073252.

v1.5.0 published

:+1:

Thanks!


Typo "NuGet.config"→"NuGet.Config"

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/prev-versions/nuget-installer-0?view=azure-devops
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 - thank you for your contribution. this change doesn't seem to be necessary however. Closing the PR.


chore: update login with Amazon instructions in CLI

update login with amazon instructions with more friendly URL that has better information.
Issue #, if available: this is an update of https://github.com/aws-amplify/amplify-cli/pull/5294/ after some more user testing.
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LGTM. @attilah merge when ready.


automatic-timezoned: 1.0.45 -> 1.0.49

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/maxbrunet/automatic-timezoned/releases.
meta.description for automatic-timezoned is: "Automatically update system timezone based on location"
meta.homepage for automatic-timezoned is: "https://github.com/maxbrunet/automatic-timezoned"
meta.changelog for automatic-timezoned is: "https://github.com/maxbrunet/automatic-timezoned/blob/v1.0.47/CHANGELOG.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.47 with grep in /nix/store/r3yi4pk0n9275lab94y0rd5dmymgcrrv-automatic-timezoned-1.0.47
found 1.0.47 in filename of file in /nix/store/r3yi4pk0n9275lab94y0rd5dmymgcrrv-automatic-timezoned-1.0.47

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
automatic-timezoned

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r3yi4pk0n9275lab94y0rd5dmymgcrrv-automatic-timezoned-1.0.47 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A automatic-timezoned https://github.com/r-ryantm/nixpkgs/archive/74c60d17988d4f8702b6deca1466078aa7c6b7f9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r3yi4pk0n9275lab94y0rd5dmymgcrrv-automatic-timezoned-1.0.47
ls -la /nix/store/r3yi4pk0n9275lab94y0rd5dmymgcrrv-automatic-timezoned-1.0.47/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

automatic-timezoned

Maintainer pings
cc @maxbrunet for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/maxbrunet/automatic-timezoned/releases.
meta.description for automatic-timezoned is: "Automatically update system timezone based on location"
meta.homepage for automatic-timezoned is: "https://github.com/maxbrunet/automatic-timezoned"
meta.changelog for automatic-timezoned is: "https://github.com/maxbrunet/automatic-timezoned/blob/v1.0.49/CHANGELOG.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.49 with grep in /nix/store/lg899wc126vsl74yccmmcpg82byywml7-automatic-timezoned-1.0.49
found 1.0.49 in filename of file in /nix/store/lg899wc126vsl74yccmmcpg82byywml7-automatic-timezoned-1.0.49

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
automatic-timezoned

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lg899wc126vsl74yccmmcpg82byywml7-automatic-timezoned-1.0.49 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A automatic-timezoned https://github.com/r-ryantm/nixpkgs/archive/c4d0a6590b7ea7ab8d60d0955659fe3b09b8ac4f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lg899wc126vsl74yccmmcpg82byywml7-automatic-timezoned-1.0.49
ls -la /nix/store/lg899wc126vsl74yccmmcpg82byywml7-automatic-timezoned-1.0.49/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

automatic-timezoned

Maintainer pings
cc @maxbrunet for testing.


MIPS: Instruction Disassembly/Lifting Completion

The following is the list of instructions which we currently disassemble and lift (Fully or Partially). If you have any instructions which differ from this table, there is likely a bug or a documentation failure, please let us know (also if you could provide the opcodes that would be great).

Bug: sltu doesn't properly set value to 0 in LLIR.
In disassembling 00 62 18 2b, binja correctly gets sltu $v1, $v1, $v0, but the LLIR tree looks instead like:
if ($v1 u< $v0) {
  $v1 = 1
} else {
  $v1 = $v0
}

The real interpretation in the "else" case should be $v1 = 0.

This list is missing lwl (Load Word Left) and lwr (Load Word Right) as I mentioned on #1140

It's also missing (at least) cop2 from the coprocessor, as mentioned on #1131

Thanks for aggregating these -- makes it easier to track when we're working on them. If there's one in particular that is slowing you down versus the others please let us know, or you can subclass our architecture and implement it yourself even. See, eg: https://github.com/Vector35/binaryninja-api/tree/dev/examples/x86_extension

Yep, just found that you had this generic issue. In my case the missing lifting is breaking the whole lifting for the function, so that one is the one that matters me the most.
I just found out that you can do it yourself as you mention, so I might try that soon.

daddu and ld are not being lifted (current stable 1.3)

Thanks -- updated the original list.

dsll32 doesn't even disassemble.

Seems like the MIPS coprocessor registers aren't classified as "system registers", so e.g. HLIL optimizes a function full of side-effectful mtc0 and mfc0 instructions down to nothing.
Also, maybe ehb should be lifted to an intrinsic?

The CACHE instruction OP is not decoded correctly.
Examples:

bc 85 00 00 is cache 5, 0($a0), but binja shows cache load, ($a0)
bc 88 00 00 is cache 8, 0($a0), but binja still shows cache load, ($a0)
bc 89 00 00 is cache 9, 0($a0), but binja still shows cache load, ($a0)

The cache op is 5 bits, 20:16, split into two subfields:

17:16: Which cache
20:18: Operation

The above cases were (if my numbers are right):

5: data cache load tag
8: instruction cache store tag
9: data cache store tag


CaseStudy hero #20

Casestudy Hero block used in Work page
Fix #20
Test URLs:

Before: https://main--tbx-olympus--solomon71.hlx.page/drafts/saugat/casestudy-hero
After: https://casestudy-hero--tbx-olympus--solomon71.hlx.page/drafts/saugat/casestudy-hero

Hey @saugatmalla - see this feedback concerning revealing ~5% at bottom of viewport. https://www.loom.com/share/247f669f19fd4f45ad585f7a22b7cc82

Hey @saugatmalla - see this feedback concerning revealing ~5% at bottom of viewport. https://www.loom.com/share/247f669f19fd4f45ad585f7a22b7cc82

Hey @solomon71, I have kept some space at the bottom, using 90vh value, let me know if we need to change that value.

@saugatmalla - thx. Let's go with 95vh

Approved


Creating a new service

Thanks for creating this drupal-ionic app. I'm new to drupal and ionic. When I go to add a service, the "Server" drop down menu is empty? It's required field. I can't find any info about it.
The form is at: admin/structure/services/add
The field description is: "Select a the server that should be used to handle requests to this endpoint."
Any suggestions?

@dano2 You need to install the REST Server module that comes with the Services module.

Thanks signal. That worked! If only the Service's help file would have just said that :(
I followed the rest of the instructions, but sadly when I go to create an account I get "There has been an error creating your account". The access file shows '"POST /api/v1/user/register HTTP/1.1" 404'. Everything is installed, configured and saved. Cache's cleared.
app_config.constant('drupal_instance','http://mydomain.com/');
app_config.constant('api_endpoint','api/v1/');  //path to endpoint configured on server is api/v1/
Also, drupal saves the CORS configuration on one line. Not sure that matters. So... "api/| * * POST|Origin,X-Requested-With,Content-Type,Accept"
Did I miss something obvious that would cause the 404?


Cmake build - Library names

Trying to build the ilmbase / openexr libraries using the latest cmake build scripts, I see that the library contains the version directly in their names, see the pkg_config file generated :
Name: IlmBase
Description: Base math and exception libraries
Version: 2.3.0
Libs: -L${libdir} -lImath-2_3 -lIexMath-2_3 -lHalf-2_3 -lIex-2_3 -lIlmThread-2_3 -pthread
Cflags: -pthread -I${OpenEXR_includedir}

And the following symlink are installed (at least on macOS) :
-- Installing: .../lib/libIex-2_<IP_ADDRESS>.dylib
-- Installing: .../lib/libIex-2_3.24.dylib
-- Installing: .../lib/libIex-2_3.dylib

Is this the intented behavior ? This break some of the cmake FindIlmbase, FindOpenEXR used in others projects.

Oops.. building from the wrong branch (master instead of release/2.3).
Closing the issue.


⚠ API - Lens has degraded performance

In 915b0b9, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 734 ms

Resolved: API - Lens performance has improved in 8e647cf after 8 minutes.


Adds a tiny auth check to overwriting logic

Description
Very simple auth check for setLastOverwritableIndex.
Contributing Agreement

[x] I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

closing, solved by #151


add course bug

It is possibile to add new course even if the course is not presente in the database. I could be correct but before I need to have an object course into the database. For example a solution could be to ask to the user to add the new course if not present in the database

As we said, we change the flow:
home->add schedule->add course if not exists->home


GEODE-4917: Remove dead and redundant code from LinkedStructSet.

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[n/a - superficial changes only] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

precheckin green other than spotless.  My love, my enemy.

Precheckin green.


Some versions of cloudposse/security-group/aws went away.

Found a bug? Maybe our Slack Community can help.

Describe the Bug
Some modules in the eks stack require security-group 0.3.3, which does not exist in the cloudposse/security-group terraform registry.
EKS Node Groups
EKS Worker Groups
Security Groups

Expected Behavior
Versions should exist.
Steps to Reproduce
Steps to reproduce the behavior:
# main.tf
    module "eks_node_group" {
      source = "cloudposse/eks-node-group/aws"
      # Cloud Posse recommends pinning every module to a specific version
      version     = "0.24.4"
      namespace                 = var.namespace
      stage                     = var.stage
      name                      = var.name
      attributes                = var.attributes
      tags                      = var.tags
      subnet_ids                = module.subnets.public_subnet_ids
      instance_types            = var.instance_types
      desired_size              = var.desired_size
      min_size                  = var.min_size
      max_size                  = var.max_size
      cluster_name              = module.eks_cluster.eks_cluster_id
      kubernetes_version        = var.kubernetes_version
    }

Run terraform init and you'll see the versions are unhappy.
Error: Unresolvable module version constraint

There is no available version of module "cloudposse/security-group/aws"
(.terraform/modules/jhub.eks_node_group/security-group.tf:3) which matches the
given version constraint. The newest available version is 0.4.0.

You can also just go to the version lists on the terraform registry to see the discrepancy in versions:
If you look here you'll see that security_group version is 0.3.3, but https://registry.terraform.io/modules/cloudposse/security-group/aws/latest doesn't list a version 0.3.3, only 0.3.1, 0.4.0.

+1

This was resolved today. Sorry about that.


Support FilteredList requests.

Describe your ideas
FilteredList specific operations for ClickHouse.
supports three different type of list

ALL,
PERSISTENT_ONLY,
EPHEMERAL_ONLY

it's an optimization, and data transfer between Keeper and ClickHouse can be reduced.
@JackyWoo cc

Ok thanks


feat(atomic): date and numeric facet formatting

Adds formatting for both the facets and the breadcrumbs
KIT-528
https://coveord.atlassian.net/browse/KIT-528

Format should be {{start}} to {{end}} & localized, both for the facets & breadcrumb. That way it's has a clear default & it's easily modifiable using i18n


Supporting multiple kubelet root dirs across a  cluster with CephFS in Kubernetes

Description:
We're running a Kubernetes (k8s) cluster with some machines where each machine has a different kubelet root directory configured as follows:
Machine 1: /container/k8s
Machine 2: /data/k8s
Machine 3: /var/lib/kubelet
The default CephFS configuration examples typically use a single hostPath like this:
Yaml
hostPath:
path: /var/lib/kubelet/...
However, this doesn't account for our multi-root directory setup. How can we configure ceph-csi (specifically for CephFS) to work seamlessly across all nodes considering their differing kubelet root directories?
Question:
What is the recommended approach to ensure that ceph-csi with CephFS can handle multiple kubelet root directories on a 3-node k8s cluster? Are there any best practices or specific configurations within ceph-csi or Kubernetes to accommodate such a scenario?

@Bpmm9012 yes it's possible but it complicates things as we need to have many daemonset templates which will use different kubelet path(s) which will have customer taints/tolerations to tell where the pod should go, IMHO we can document it but it will be difficult to maintain this yaml, @Bpmm9012 have you tried some symlink or something similar?


NaN checker does not check outputs of optimizers

Hi,
I noticed this while debugging fp16 support for the Adam optimizer, so I thought I'd write it down here before it was forgotten.
I had problems with NaNs in my pipeline, but couldn't really figure out where they came from. So I called tf.add_check_numerics_ops(), but it turns out that if the Adam optimizer creates a NaN (in my case, because the default epsilon of 1e-8 was too small for fp16), it is not actually checked.
Instead, you get the error on a later Read op (when the NaN is attempted used), which can be very confusing, especially since there's a lot of Read ops and it's not always easy to figure out which one the error message is about.

Are you calling add_check_numerics_ops after calling AdamOptimizer? In add_check_numerics I see that it adds check numerics ops to all ops present in the graph

Yes, I called it after AdamOptimizer. I believe the optimizer is special because nothing reads from its outputs (before the next iteration), and that's why it falls through the cracks.

Closing due to inactivity. Feel free to open a new github issue if the problem still persists in recent versions.


Allow immutable properties

KDE allows immutability of most settings, which would be good to add to this (e.g. for deployments of a KDE desktop using home-manager). This is done by adding [$i] to the section header (e.g. [KDE][$i]) to make all the values in that section immutable.
I suggest doing this by adding this type of setting:
programs.plasma.configFile.kdedrc5.Module-device_automounter = {
   _immutable = true;
   autoload = false;
};

In writeConfig, you can add the [$i] to the end of the section header for this section.
I'm not 100% sure how writeConfig works (especially the python script), but I imagine it wouldn't be too difficult.

Nice suggestion. I have thought about it before, it just was a little much work at the time seeing as adding "[$i]" already worked, but I do agree this is a better way of doing this. I will probably implement this once we get some other things out of the way (of course prs are welcome too)!


v2.9.0 doesn't work with latest Fabric Server (1.21.3)

The console says the mod needs Java 17, but the server needs at least Java 21

Minecraft 1.20.5 and above requires Java 21.
If you have any other issue please provide the full log.

i am using 1.21.3 with java 21.0.5
here is my full log:
https://pastebin.com/32t5acWF

No i fixed it now, the problem was the forge loader version that is installed with crafty
no fabric api is needed


Fix Gradle JDBC driver dependencies to be runtime

It is generally bad practice to define JDBC or other dynamically loaded with
standard API to be required as compile time dependencies as the purpose of
these is to load them in at runtime and only rely on their generic API. When
you define a dependency like this as compile scope instead of runtime you
open yourself up to developers using MySQL, or H2 specific APIs without
realizing this dependency because the build will never catch it.

Good change, i'm looking forward to removing the MySQL runtime dependency and requiring users who wish to use any JDBC connector to provide the classes on the classpath though :)


[KIT IDEAS]

[ ] MPD Neurax Edition
[ ] Action Figure Kits, Equator and TotalFreedom editions (inspired by Parsa__'s action figure)
[x] VesperSoup Kit
[ ] Utilities kit, contains useful items and signs

Merging with #4


Tighten Workgroup definition

Say what a Workgroup is in the definition. Also lightly tweak the descriptions used in Workstep and Workflow.
This is an editorial change - it doesn't change conformance or requirements.

@chaals ... please! Correct typo!


POST_BUILD_COMMAND

Am I correct in assuming that building a post_build.sh that contains:
source antenv/bin/activate
python3 manage.py makemigrations
python3 manage.py migrate
python3 manage.py runserver

and add it to:
az webapp config appsettings set --name <app-name> --resource-group <app-resource-group> --settings POST_BUILD_COMMAND="/home/site/wwwroot/post_buid.sh" DJANGO_ENV="production" DBHOST="<postgresql-name>.postgres.database.azure.com" DBUSER="root@<postgresql-name>" DBPASS="Pollsdb1" DBNAME="pollsdb"

will truly automate the update process?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 791bd216-532f-7f28-fa51-d95798397310
Version Independent ID: 4f7ff676-e4a5-cc41-6a43-ecb8fa1095fb
Content: Tutorial: Deploy Python (Django) with Postgres - Azure App Service
Content Source: articles/app-service/containers/tutorial-python-postgresql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@orion1900 Thanks for your comment. We will review your issue and will revert to you.

@orion1900, Apologies for the delay. You can customize build automation and container start-up process with custom container.  You could add a startup script  -These commands or scripts are executed after the built-in Docker container is started, but before your application code is started. Kindly let us know if this helps or if I have misunderstood your specific question.
az webapp config appsettings set --name  --resource-group  --settings POST_BUILD_COMMAND="echo foo, scripts/postbuild.sh"

Michel, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion.


Creates a simple text mask for the current workPath for action-encode

This allow for creating more files with known names such as encoding in multiple bitrates for hls streams
such as
            {
                "module": "@nexrender/action-encode",
                "output": "encoded_playlist_%v.m3u8",
                "params": {
                    "-acodec": "aac",
                    "-vcodec": "libx264",
                    "-pix_fmt": "yuv420p",
                    "-map": [
                        "0:0",
                        "0:0",
                        "0:0"
                    ],
                    "-b:v:0": "2000k",
                    "-b:v:1": "1000k",
                    "-b:v:2": "500k",
                    "-f": "hls",
                    "-hls_time": "5",
                    "-hls_list_size": "0",
                    "-var_stream_map": "v:0,name:high v:1,name:medium v:2,name:low",
                    "-master_pl_name": "master.m3u8",
                    "-hls_segment_filename": "${workPath}\\encoded%d_%v.ts",
                    "-s": "540x960"
                }
            }

Hey there @Thiago-Dantas 👋
Sorry for the long response. I have a minor change proposal, would you be able to also update the docs to reflect this feature?
Otherwise, people would probably never know it is possible to use something like this.
Cheers!

Hey there @Thiago-Dantas 👋
Sorry for the long response. I have a minor change proposal, would you be able to also update the docs to reflect this feature?
Otherwise, people would probably never know it is possible to use something like this.
Cheers!

Hey @inlife just added an usage example under Usage

Hey @inlife just added an usage example under Usage

amazing work, thank you @Thiago-Dantas! 👍

amazing work, thank you @Thiago-Dantas! 👍


Fix ConcurrentContainer lifecycle issues

This commit would fix the issue.

'isChildRunning' API would return true only after all the containers are actually stopped.
ConcurrentContainer start would be permitted only after all the containers running status is false.
ConcurrentContainer stop would be permitted if the container is in running status or if previously stop API is not called.
Move the logic to verify whether to permit the stop call to KafkaMessageListenerContainer and ConcurrentMessageListenerContainer.
Add 'stopAbnormally' in a Lock.
Set the ConcurrentContainer running status to true after childStarted 7) Set the ConcurrentContainer running status to false after childStopped 8) Call childStarted in ConcurrentContainer from KafkaMessageListenerContainer right before publishing ConsumerStartedEvent.

@LokeshAlamuri ,
let's step back and try to understand what is the problem at all.
Would you mind explaining the reasoning behind your work?
I thought you have implemented fenced before for the situation when child container can be started when its parent is stopped.
So, that mean that we are able to stop any particular child container and I don't see a reason why don't allow to that.
But I feel like this is fully different story and that is not what you are trying to achieve here.
However I still cannot fully understand what you are doing and why.
Thanks

I thought you have implemented fenced before for the situation when child container can be started when its parent is stopped.
So, that mean that we are able to stop any particular child container and I don't see a reason why don't allow to that.

Fenced child container issue is very clear and straightforward. Assume ConcurrentContainer is stopped. But, if we are having reference to child container,  it is still possible to start the child container. It is not correct. Because, it is having reference to the ConcurrentContainer. It is nothing but corrupting the ConcurrentContainer.  I have provided Junit clearly how this scenario could be replicated.

But I feel like this is fully different story and that is not what you are trying to achieve here.
However I still cannot fully understand what you are doing and why.

I am here trying to fix the ConcurrentContainer lifecycle issues and especially isChildRunning API. As discussed earlier, isChildRunning API should return false only when all the containers are stopped. This is the most critical thing for any application. It indicates, when exactly the spring-kafka component is completely stopped.

It is nothing but corrupting the ConcurrentContainer.

How does it corrupt it with its start if we don't stop ConcurrentContainer?
You can chose some child container to be stopped for any reason and then start it back when ever you need.

It indicates, when exactly the spring-kafka component is completely stopped.

Right. And that's what I mean with having ConcurrentContainer running until at least one of its child container is running.
Or I even feel more natural to have ConcurrentContainer always running until its stop() explicitly called.
This way we still maintain the same set of this.containers and its up to target application to decide what to do with every child container.
Why do you find this logic as wrong?

It indicates, when exactly the spring-kafka component is completely stopped.

Right. And that's what I mean with having ConcurrentContainer running until at least one of its child container is running. Or I even feel more natural to have ConcurrentContainer always running until its stop() explicitly called. This way we still maintain the same set of this.containers and its up to target application to decide what to do with every child container. Why do you find this logic as wrong?

Looks good to me. Only one issue, if we keep the running  status of the ConcurrentContainer  to true, even after one or all the containers are stopped, from the API perspective imagine once, who wants to track the system, they cannot use the running status any more and have to always iterate over the containers to see every thing is functioning properly or not.
But, If we have set the running  status of the ConcurrentContainer  to false,  from the API perspective it tells ok something is wrong and then they can have the logic to handle the situation. running status to true indicates all is good. In this model, running flag is  really useful.

It is nothing but corrupting the ConcurrentContainer.

How does it corrupt it with its start if we don't stop ConcurrentContainer? You can chose some child container to be stopped for any reason and then start it back when ever you need.

As mentioned in my previous comment, I am not trying to stop ConcurrentContainer.  I am only trying to stop the fenced containers from starting once again since they are holding the reference to the ConcurrentContainer. That is the fix we gave  for the issue https://github.com/spring-projects/spring-kafka/issues/3371.

set the running status of the ConcurrentContainer to false, if any of the container fails

Right, but then it is chicken-egg problem.
I see the situation when other child containers are still running, however the whole ConcurrentContainer says that nothing is running, so it is OK to call its run and we are in a leakage situation where ConcurrentContainer spawns new containers without stopping others.
Even if we fix this via refresh the whole state in the start, I still feel like this is an overhead and pointless number of operations.
With running controlled just only by the ConcurrentContainer, then it is OK to deal with every its children individually.
And we really refresh the state when we restart the whole ConcurrentContainer explicitly.
The combination of isRunning() and isChildRunning() should cover all the possible situations and simplify target logic.

set the running status of the ConcurrentContainer to false, if any of the container fails

Right, but then it is chicken-egg problem. I see the situation when other child containers are still running, however the whole ConcurrentContainer says that nothing is running, so it is OK to call its run and we are in a leakage situation where ConcurrentContainer spawns new containers without stopping others. Even if we fix this via refresh the whole state in the start, I still feel like this is an overhead and pointless number of operations. With running controlled just only by the ConcurrentContainer, then it is OK to deal with every its children individually. And we really refresh the state when we restart the whole ConcurrentContainer explicitly. The combination of isRunning() and isChildRunning() should cover all the possible situations and simplify target logic.

Ok then i will keep the running status logic as before and will revert the necessary changes in my PR. Once done, we can have  further discussion. Thank you.

Gentle reminder. I have updated the PR as per our discussion.

I have updated the PR as per our discussion. Please review and give your comments.

Thanks for the great contribution @LokeshAlamuri; looking forward for more!
We will try to back-port the fix to those supported versions...

OK. We cannot back-port it to previous versions.
Apparently there is still something missing there.
So, leaving it only in the main.
Feel free to contribute PRs for those supported versions.
However they will make only for the next release: we do current today.
Hope the problem you are trying to fix is not that critical if we deal with container lifecycle properly.


Update to tf.data

Tensorflow gives several warnings about the deprecation of the currently used methods and training always fails on latest tensorflow 1.x version with fifoqueue '_2_batch/fifo_queue' is closed and has insufficient elements (requested 1, current size 0)

I have the same problem.  I think this is a problem with the dataset. My problem is that the filename of the dataset is wrong (there is a additional "\n"). I suggest that you confirm the dataset again.

I have the same problem. I have confirmed that there is no problem with the dataset and the path is correct. Why is that?

(0) Out of range: FIFOQueue '_2_batch/fifo_queue' is closed and has insufficient elements (requested 1, current size 0)
[[{{node batch}}]]
(1) Out of range: FIFOQueue '_2_batch/fifo_queue' is closed and has insufficient elements (requested 1, current size 0)
[[{{node batch}}]]
[[DecodeJpeg_1/_1793]]

(0) 超出范围：FIFOQueue '_2_batch/fifo_queue' 已关闭且元素不足（请求 1，当前大小为 0） [[{{node batch}}]] (1) 超出范围：FIFOQueue '_2_batch/fifo_queue'已关闭且元素不足（请求 1，当前大小 0） [[{{node batch}}]] [[DecodeJpeg_1/_1793]]

I have the same problem with this error, is that related to my created csv?

I have the same problem. I have confirmed that there is no problem with the dataset and the path is correct. Why is that?

Hi. Have you solved the problem?

(0) 超出范围：FIFOQueue '_2_batch/fifo_queue' 已关闭且元素不足（请求 1，当前大小为 0） [[{{node batch}}]] (1) 超出范围：FIFOQueue '_2_batch/fifo_queue'已关闭且元素不足（请求 1，当前大小 0） [[{{node batch}}]] [[DecodeJpeg_1/_1793]]

I have the same problem with this error, is that related to my created csv?

Hi. Have you solved the problem?


allow fqcn string to be passed to Illuminate\Database\Eloquent\Model::observe

Can you remove the class_exists check.

Done
--
Mike Dugan
<EMAIL_ADDRESS>http://dugan.io
On February 27, 2015 at 9:30:32 AM, Taylor Otwell<EMAIL_ADDRESS>wrote:
Can you remove the class_exists check.
—
Reply to this email directly or view it on GitHub.

I also just noticed this is master branch.