Unsupported DO...END block in migration

    (electric 0.7.1) lib/electric/postgres/proxy/injector/operation.ex:825: Electric.Postgres.Proxy.Injector.Operation.Electric.Postgres.Proxy.Injector.Operation.SyntaxError.error_response("Unsupported DO...END block in migration", %PgProtocol.Message.Query{query: "DO $$ \nDECLARE \n    schema_exists BOOLEAN;\nBEGIN\n    SELECT EXISTS (\n        SELECT 1\n        FROM information_schema.schemata\n        WHERE schema_name = 'electric'\n    ) INTO schema_exists;\n\n    IF schema_exists THEN\n        CALL electric.electrify('public.\"DataTable\"');\n        CALL electric.electrify('public.\"Column\"');\n        CALL electric.electrify('public.\"IntegrationInstance\"');\n        CALL electric.electrify('public.\"ColumnReference\"');\n        CALL electric.electrify('public.\"Row\"');\n        CALL electric.electrify('public.\"CellValue\"');\n        \n        -- Hotfix the electric schema\n        ALTER TABLE electric.ddl_commands\n        DROP CONSTRAINT ddl_table_unique_migrations;\n        CREATE EXTENSION IF NOT EXISTS pgcrypto;  \n        ALTER TABLE electric.ddl_commands \n        ADD COLUMN query_digest text GENERATED ALWAYS AS (digest(query, 'shake128')) STORED;\n        ALTER TABLE electric.ddl_commands ADD CONSTRAINT ddl_table_unique_migrations UNIQUE (txid, txts, version, query_digest);\n    END IF;\nEND $$;\n"})

@gorbak25 thanks for the bug report. could you include the sql of the migration please
the error message mentions the use of do blocks... the proxy disallows these because the sql parser doesn't read the body of the do and so we can't figure out what's being done in order to capture the operations.
is there any driving need to use a do block for your migration? The above seems to be checking for the existence of the electric schema before applying the operations. could you skip this check?

@magnetised Thanks for getting back to me! I've got 2 places where I'm using DO $$ ... END $$; blocks.
The first one was used in 0.6.3 to electrify the tables and this bug report refers to it
DO $$
DECLARE
    schema_exists BOOLEAN;
BEGIN
    SELECT EXISTS (
        SELECT 1
        FROM information_schema.schemata
        WHERE schema_name = 'electric'
    ) INTO schema_exists;

    IF schema_exists THEN
        CALL electric.electrify('public."DataTable"');
        CALL electric.electrify('public."Column"');
        CALL electric.electrify('public."IntegrationInstance"');
        CALL electric.electrify('public."ColumnReference"');
        CALL electric.electrify('public."Row"');
        CALL electric.electrify('public."CellValue"');

        -- Hotfix the electric schema
        ALTER TABLE electric.ddl_commands
        DROP CONSTRAINT ddl_table_unique_migrations;
        CREATE EXTENSION IF NOT EXISTS pgcrypto;
        ALTER TABLE electric.ddl_commands
        ADD COLUMN query_digest text GENERATED ALWAYS AS (digest(query, 'shake128')) STORED;
        ALTER TABLE electric.ddl_commands ADD CONSTRAINT ddl_table_unique_migrations UNIQUE (txid, txts, version, query_digest);
    END IF;
END $$;

Fortunately after converting it to
ALTER TABLE public."DataTable" ENABLE ELECTRIC;
ALTER TABLE public."Column" ENABLE ELECTRIC;
ALTER TABLE public."IntegrationInstance" ENABLE ELECTRIC;
ALTER TABLE public."ColumnReference" ENABLE ELECTRIC;
ALTER TABLE public."Row" ENABLE ELECTRIC;
ALTER TABLE public."CellValue" ENABLE ELECTRIC;

it just works.
The second occurrence unfortunately is not easy to get rid off. I've got some helper tables maintained using triggers and i want for ON DELETE CASCADE triggers to work on them during logical replication. To achieve that I'm dynamically generating sql which will enable the triggers:
DO $$
DECLARE
    rec RECORD;
    v_sql TEXT;
BEGIN
    -- Enables ON DELETE CASCADE ON UPDATE CASCADE triggers during logical replication
    FOR rec IN (
        SELECT 'ALTER TABLE "' || s1.t || '" ENABLE ALWAYS TRIGGER "' || s1.tgname || '";' AS sql
        FROM
        (
            SELECT 'CellValue' AS t, tgname FROM pg_trigger WHERE tgrelid='"CellValue"'::regclass AND tgconstrrelid='"CellValueForEvaluation"'::regclass
            UNION
            SELECT 'DataTable' AS t, tgname FROM pg_trigger WHERE tgrelid='"DataTable"'::regclass AND tgconstrrelid='"DataTableTopoColumnOrder"'::regclass
        ) AS s1
    )
    LOOP
        v_sql := rec.sql;
        EXECUTE v_sql;
    END LOOP;
END $$;

Is there an alternative to this?
PS. I've managed to get my app running on 7.1 by splitting the schema into 2 parts - one for the proxy, the second one for postgres.

@gorbak25 glad you got it to work. The problem with do blocks is that, because they allow for full plpgsql programs, not just sql statements, it's nigh on impossible for us to extract the actual ddl statements out of them, which means we can't do our syntax re-writing or various validations.
however, your use case above is valid. I'm thinking perhaps some CALL electric.passthrough($$ body of migration$$) or CALL electric.safe(); -- body of migration follows statement that we could add that would allow for these kinds of opaque commands to come through, with clear guidelines to the developer that Things Will Break(tm) if they touch any electrified tables inside it.
Will think about it and come back to you. You shouldn't have to split the migrations like that.

CALL electric.i_want_to_break_electric($$ ... $$) would work best :) Having an escape hatch for non standard stuff would be beneficial for me!

I just ran into this problem as well.  Do I understand correctly that we aren't allowed to create functions with plpgsql?

For reference, here is what the Oban migration is trying to execute.
06:28:11.360 [info] execute "DO $$\nBEGIN\nIF NOT EXISTS (SELECT 1 FROM pg_type\n               WHERE typname = 'oban_job_state'\n                 AND typnamespace = 'public'::regnamespace::oid) THEN\n    CREATE TYPE \"public\".oban_job_state AS ENUM (\n      'available',\n      'scheduled',\n      'executing',\n      'retryable',\n      'completed',\n      'discarded'\n    );\n  END IF;\nEND$$;\n"

Also regarding overall plpgsql support, we make pretty extensive use of plpgsql in our project, but if I temporarily comment out all Oban migration code, I get through all of our migrations, so from what I'm seeing so far it seems DO END blocks are the only issue.

@justindotpub We will support passthrough for DO...END blocks one way or another. We just haven't come up with a satisfactory design for it yet.
You can work around this limitation in the proxy by applying some migrations directly to Postgres while still using the Proxy for migrations that touch electrified schema.

Migrations are also generated with this syntax by DrizzleORM
DO $$ BEGIN
  CREATE TYPE "objective_state" AS ENUM('open', 'closed');
EXCEPTION
  WHEN duplicate_object THEN null;
END $$;

Yep, I just ran into this as well. I was hoping Drizzle would be less problematic than Prisma. I had no clue Electric wouldn't be handle DO END blocks.
It seems like a major use case is that they have exception blocks, but I'm not sure.
I don't see a great way to make Electric work with Drizzle without this.

👋 we've been working the last month on a rebuild of the Electric server over at a temporary repo https://github.com/electric-sql/electric-next/
You can read more about why we made the decision at https://next.electric-sql.com/about
We're really excited about all the new possibilities the new server brings and we hope you'll check it out soon and give us your feedback.
We're now moving the temporary repo back here. As part of that migration we're closing all the old issues and PRs. We really appreciate you taking the time to investigate and report this issue!


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/backports-datetime-fromisoformat-feedstock#3.


Show language support on website

We can filter language support in the search, but on the font page itself, we actually have no clue what multiple languages a font may support. It'd be nice if that is shown somewhere for people to see.
The information is already downloaded in metadata.json, so it's more of a design job rather than requiring any functional changes.

Closed in favour of #558.


chore(release): publish v1.0.0-rc.2

Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>

Codecov Report

Merging #1492 (a98e5d7) into main (67ddebe) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1492   +/-   ##
=======================================
  Coverage   71.16%   71.16%
=======================================
  Files         333      333
  Lines       12181    12181
  Branches     1480     1480
=======================================
  Hits         8669     8669
  Misses       2697     2697
  Partials      815      815

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 67ddebe...a98e5d7. Read the comment docs.


Inferencer Warning After Updated To Latest

I got this warning in the inferencer during validation phase at each step. Is it serious? Can I turn it off?
[0811 17:09:52 @inference.py:82] WRN Inferencer._datapoint was renamed to _on_fetches

What inferencer do you use?

I'm using the default InferenceRunner. Some more details:
def get_valid_data_generator(data, data_shape, label, label_shape, batch_size = 16):     ds = Dataset(data, label)     shape_aug = [         imgaug.CenterCrop(data_shape),     ]     ds = AugmentImageComponents(ds, shape_aug, (0, 1), copy=True)     augmentors = [         imgaug.CenterCrop(label_shape),     ]             ds = AugmentImageComponent(ds, augmentors, index = 1, copy=True)     ds = BatchData(ds, batch_size)     return ds
And the setup in TrainConfig:
InferenceRunner(get_valid_data_generator(x_valid, base_shape,                                                                        y_valid, mask_shape,                                                                        batch_size = 32),                             ClassificationStats('predmap', 'segmapx')),

Thanks. So you wrote a inferencer, and the methods were recently renamed, so it prints a warning.


Big video latency between ios9 and firefox and chrome!

My test environment:

Access web of  http://demo.openwebrtc.org:38080/ on Iphone or chrome.
chrome or firefox on PC.
iPhone 5 with iOS9;
Framework:   using myself build based on cerbero on 24 oct. or   @casey 10.10.2015 build: https://drive.google.com/open?id=0B49chjTf6eU1SWJKYlJ6WWJqZTA
build on SimpleDemo on xcode 7.0.1 based on  EricssonResearch/openwebrtc-examples#125 @stefanalund

Step:

iphone 5(iOS9) and chrome load the test page of  http://demo.openwebrtc.org:38080/
select audio and video on iphone 5(iOS9) and chrome,  then 'join'. all device  an see local video.
select 'call' on iphone 5.
wait about 0.5 seconds, on chrome/firefox, we can see black video for remote.
wait about 2~5 seconds, on chrome/firefox, we can see remote video.
wait about  10~30, sometimes we can see the first remote video on iphone. sometimes always cannot see remote video on iphone.
even when we can see the first frame remote video on iphone, but we cannot see the remote video again(cannot see real video. ).

Question:

1, Anybody has pay attention to this issue?  or enly my test environment issues?
2, Has anybody  done some tests between iphone and chrome/firefox.

Note:

When I setup the test page of on my local LAN, I have gotten the same result. so the latency is not networks problem.
I have tracked the offer/answer, the video should be using VP8.

Could you please rebuild? We landed this fix https://github.com/EricssonResearch/openwebrtc/pull/488 probably after you built your own. Hopefully the delay should be resolved, or at least significantly decreased.

Sorry, if you rebuilt from master on the 24th of Oct you would have gotten that fix. Trying with an iPhone 5 now...

@stefanalund， thanks for you quickly answer.

I have checked my build environment, even if I have built it with cerbero, but I didn't update to the latest version on 24 oct. :(

So today I have updated my cerbero to latest version of f97b902 which is committed on 29 oct, then I rebuild it again. and integrate my build framework into SimpleDemo on xcode 7.0.1.

Test result:

Most of my test, the result  is always similar  to this issues.
Even if sometime we can setup the peer video, but the result is very worse.

on the chrome/firefox,we can see the remote Iphone  video, which is about 4 seconds latency.
on the Iphone,  sometime we can see the remote chrome/firefox  video, the latency is bout 20~30 seconds, or we can see partly I frame key, or sometime we cannot see remote chrome/firefox  video again.

Do you mean that the video performance is worse after rebuilding with latest master? That is troublesome.

@stefanalund    That is my test result on iphone 5 which ios9 based on the latest master version of f97b902 which is committed on 29 oct,
I think the video performance is a big problem, we should pay attention to this issue. After all we cannot  communication between OWR on iOS9 and chrome/firefox on PC/Android.
And I will try to find iphone 6 and iphone 6s, After I find it, I will try to do  this test on Iphone 6/6s later.

I agree, this is something we will look into.

More info:

Sometimes we need longtime to connect the peer videos,  and we can see the log of 'Failed to set local offer sdp: Called in wrong state: STATE_RECEIVEDINITIATE' in the chrome.

@stefhak @adam-be do you know why Chrome warns about this Called in wrong state: STATE_RECEIVEDINITIATE?

I have tested this issue on Iphone 6 and iphone 6s.
Test result:

Peer video connection is fast than Iphone 5.
The latency from IPhone to chrome is about 2s, it is ok.
The latency from chrome to IPhone is about 30s or bigger, it is  bigger latency!  :bomb:

This is our top focus at the moment. We'll keep this issue updated with news.

This is not acceptable. iOS 9 has made the performance significantly worse, it seems. We are investigating.

Sorry for not responding earlier. I proposed a change to openwebrtc-examples, https://github.com/EricssonResearch/openwebrtc-examples/pull/129, now merged. Is that included when testing (it may take care of Called in wrong state: STATE_RECEIVEDINITIATE

I've now tested (with a locally run server, and EricssonResearch/openwebrtc-examples#129 applied), and things work fine for me Bowser <-> MacOsX/Chrome and Bowser <-> MacOsX/Firefox. Bowser runs on an iPhone5S with iOS 9.0.2, and it does not matter if "Call" is clicked on Bowser or Chrome/Firefox.

@stefhak
My test environment:

1, For the web server,  I have tried to use the  http://demo.openwebrtc.org or local web server which I gotten from https://github.com/EricssonResearch/openwebrtc-examples/web@5ff94dfd94 (which has included openwebrtc-examples/web@0a40d1fe  EricssonResearch/openwebrtc-examples#129 applied),
2, I have build latest latest cerbero@119ed50eb1e, and you need manually add libiconv.tbd #509 .
3, I used SimpleDemo to test the framework or the web server.      https://github.com/EricssonResearch/openwebrtc-examples/ios/SimpleDemo@5ff94dfd94
4, test SimpleDemo<EMAIL_ADDRESS>5, iPhone 5 with iOS 9.0.2

Today, I have tested again based on my test environment,  I got the same result as this issue.
Question:

1, What's mean "Bowser is version 0.5", how can I build it or got it for my iPhone 5 with iOS 9.0.2?

@stefhak  Are there any updates for this issues? thanks.

@bamboolsu A number of improvements have been made to openwebrtc and to some gstreamer plugins that could help; you need to rebuild though. There is a new version of Bowser in app store review, I think it contains these improvements @stefanalund would know more.

I have tried the version of<EMAIL_ADDRESS>which is submit on Dec 8 2015.  This issue still exist on my test version.
Test result:

Even if sometime we can setup the peer video, but the result is very worse.

on the chrome/firefox,we can see the remote Iphone  video, which is about 1~4 seconds latency. The result is better than I first report the issue.
on the Iphone,  sometime we can see the remote chrome/firefox  video, the latency is bout 10~20 seconds, or we can see first I key frame and later we cannot see remote chrome/firefox  video again.

We're in the process of making a complete solution for zero copy video from camera to renderer/encoder and from decoder to renderer. It may be that we take a step backward on the way to making a giant leap forward.
Please know that we are working hard to fix these delay and performance issues on iOS permanently.

Thanks for all your great efforts. ：）

I have done some  tests  for version of cerbero@c64ec4f440f.
I got the following results, The  realtime video is worse between iphones.:

1,  iphone 6s  ---->>>> iphone 5;
** for iphone 5, about 15~30s, we can see the first remote(iphone)I frame video, then about 30s we can see other I frame or we never see the video again.
2, iphone 5  ---->>>> iphone 6s;
** for iphone 6s, we never see the remote video.
3, android phone ---->>>> iphone 6s;
** for iphone 6s,  about 1~3s,  we can see the first remote I frame video, then about 30s we can see other I frame or we never see the video again.
4,  iphone 6s  ---->>>> android phone;
** for android phone,  about 1~3s latency.
.

test steps:

1,  build framework for
2, build ipa for iphone by using openwebrtc-examples/ios/SimpleDemo
3, load page of http://demo.openwebrtc.org:38080/ in iphone or android phone;
4, join one session and then call;

test environment:

1, iphone 5 with ios9.2 and iphone 6s with ios 9.1;
2, cerbero@c64ec4f440f.
3, the test page is: http://demo.openwebrtc.org:38080/
4, ipone code is webview for openwebrtc-examples/ios/SimpleDemo

We wish we will good result after @stefanalund  said that "We're in the process of making a complete solution for zero copy video from camera to renderer/encoder and from decoder to renderer. "

@superdump
"We're in the process of making a complete solution for zero copy video from camera to renderer/encoder and from decoder to renderer. It may be that we take a step backward on the way to making a giant leap forward."
Then when we can comlete the feature of  'zero copy video' ?  and when can see the real video between  ios and android(or between ios and ios)?


Update order of languages on libraries page fix #73

My Account Number: 34830d09415a8479c28723528e87eb5e20721addac21522255b04b5baa8046c5

@thesanjeevsharma I forgot to create a new branch and started working on another feature, my bad. by i replaced the previous files with a previous commits'

@thesanjeevsharma i re-forked the project. will be submitting a pull request in a few minutes.

I created a new pull request hope it has the changes you requested. https://github.com/thenewboston-developers/Developer-Portal/pull/75


Deploy test

Hi Brian,
These changes should allow you to do a successful deploy to dryad-dev.cdlib.org (if everything is set up right for your authorized keys and the rest on the server) and it uses capistrano to deploy.
cap development deploy
And then the app should be functioning on the dryad-dev.cdlib.org server once you deploy.

Looks good @sfisher I just redeployed to dev and all looks good


Why adding LOCAL_IO_PUTC(a0) in tests? What is the checking?

3 months back I downloaded and have been running compliance tests, things were fine.
Updated test have LOCAL_IO_PUTC(a0); in the test case causing failure.
What is the expectation here from the test case?  What is testing here by this in all test cases? Please comment on this.
FN_WriteStr:
    mv          t0, a0;
10000:
    lbu         a0, (t0);
    addi        t0, t0, 1;
    beq         a0, zero, 10000f;
    **LOCAL_IO_PUTC(a0);**
    j           10000b;
10000:
    ret;

Can you also describe the failure you are seeing

Compilation ?
Execution ?
Signature Comparison ?

Can I ask which target you have been using to execute the tests ?

riscvOVPsim ?
rocket ?
spike ?
...

There are 5 macros which need defining for each target, and it is acceptable for these macros to have no code associated at all. so in the following file
riscv-target/riscvOVPsim/compliance_io.h
you will see that defining 'RVTEST_IO_QUIET' creates macros which are NULL for the following
#define RVTEST_IO_INIT
#define RVTEST_IO_WRITE_STR(_SP, _STR)
#define RVTEST_IO_CHECK()
#define RVTEST_IO_ASSERT_GPR_EQ(_SP, _R, _I)
#define RVTEST_IO_ASSERT_SFPR_EQ(_F, _R, _I)
#define RVTEST_IO_ASSERT_DFPR_EQ(_D, _R, _I)
otherwise they associate a number of IO and ASSERT capabilities
Thx
Lee

Hi Lee

When I run with the target specified to spike, I am getting error as follow and not generating tests otherthatn rv32i. Could you tell me anything should I need to taken care here (I am using command make -d RISCV_TARGET=spike & make RISCV_TARGET=spike -isa=rv32imc).

When I generate with default target like make all_variant and when I ran with  I see the execution error(self-check fail) as follow

UVM_INFO [tracer] @406400.0ns: => @406400 #80 C0 8000003c [5391e193] ori      x3, x3, 0x539         OK
UVM_INFO [tracer] @415900.0ns: =>     x30 = 8000a040
UVM_INFO [tracer] @415900.0ns: => @415900 #81 C0 80000040 [0000af17] auipc    x30, 0xa OK
UVM_INFO [tracer] @416000.0ns: =>     STADDR = 8000a000       STDATA = 00000539
UVM_INFO [tracer] @416000.0ns: => @416000 #82 C0 80000044 [fc3f2023] sw       x3, -0x40(x30)      OK
UVM_INFO [tracer] @416000.0ns: => Detected store tohost with value = 00000539 .. stopping checks (83 instructions, 82 checked)
UVM_ERROR (0) @ 416000.0ns: uvm_test_top.riscv_env.tracer [tracer] Self-Check FAIL: tohost exit code != 1 (539)
Actually, As per your comment, I need things specific only to spike(our target is a spike) that can remove the macro that is not needed for us.
Thanks & Regards
Dore M R

Hi Dore M R
can you try executing
$ make RISCV_TARGET=spike
Please provide the full log including STDOUT and STDERR
The errors you are showing look like system reported errors, I do not even see the applications being compiled.
What machine are you running ?
Finally, if you just type
$ spike
what is printed ?
Thx
Lee

I tried executing both
$ make clean
$ make RISCV_TARGET=spike. same fail.
added the run log in attachment, please find it.

our spike and compilers are set. didn't get how to define compiler name.
spike path: /wdc/apps/riscv/bin/spike

$spike
usage: spike [host options]  [target options]
Host Options:
-p                 Simulate  processors [default 1]
-m                 Provide  MiB of target memory [default 2048]
-m<a:m,b:n,...>       Provide memory regions of size m and n bytes
at base addresses a and b (with 4 KiB alignment)
-d                    Interactive debug mode
-g                    Track histogram of PCs
-l                    Generate a log of execution
-h                    Print this help message
-H                 Start halted, allowing a debugger to connect
-C                 Enable log & commitlog
--isa=          RISC-V ISA string [default RV64IMAFDC]
--pc=        Override ELF entry point
--hartids=<a,b,...>   Explicitly specify hartids, default is 0,1,...
--ic=::      Instantiate a cache model with S sets,
--dc=::        W ways, and B-byte blocks (with S and
--l2=::        B both powers of 2).
--extension=    Specify RoCC Extension
--extlib=       Shared library to load
--rbb-port=     Listen on  for remote bitbang connection
--dump-dts  Print device tree string and exit
fail.log.txt

By the look of your log, the test for I-MISALIGN_LDST-01 is failing (all others are passing)
what version of spike are you running, maybe spike has been changed in the way it handled misaligned ld/st ?
out of interest what happens if you run with the OVPsim simulator ?
$ make RISCV_TARGET=riscvOVPsim

@MRDore
Going back to your initial issue, you mention that you think that
LOCAL_IO_PUTC(a0)
is causing a problem
Are you still thinking this is the case ?
because it looks like only one test is failing as I described above.
thx
Lee

I don't know the exact version, we installed on 28 -Jan-2018.
@eroom1966
FN_WriteStr:
mv          t0, a0;
10000:
lbu         a0, (t0);      // I think  problem is here
addi        t0, t0, 1;
beq         a0, zero, 10000f;  // expecting 0 as a output from the memory but its not
LOCAL_IO_PUTC(a0);
j           10000b;
10000:
ret;

@MRDore
But this does not make sense, this code is never executed if the target is spike ?
the file that defines these macros are under
riscv-target/soike/compliance_io.h
all the macros are defined as empty, meaning they compile no code.

#ifndef _COMPLIANCE_IO_H
#define _COMPLIANCE_IO_H

//-----------------------------------------------------------------------
// RV IO Macros (Non functional)
//-----------------------------------------------------------------------

#define RVTEST_IO_INIT
#define RVTEST_IO_WRITE_STR(_SP, _STR)
#define RVTEST_IO_CHECK()
#define RVTEST_IO_ASSERT_GPR_EQ(_SP, _R, _I)
#define RVTEST_IO_ASSERT_SFPR_EQ(_F, _R, _I)
#define RVTEST_IO_ASSERT_DFPR_EQ(_D, _R, _I)

#endif // _COMPLIANCE_IO_H

the code fragments you have referenced are for the riscvOVPsim target, not the spike target.
thx
Lee

@eroom1966
Maybe in November, downloaded the compliance and I used the command to make all_variant, test cases generated without those macros and worked fine with our simulator & spike.
Now I wanted to test the updated compliance tests with the same and followed the same process got stuck.
Could you tell me how to generate updated compliance test cases with the target as a spike?

@MRDore
I think I am a little confused, so would like to clarify some information you have supplied
If you use the command
$ make all_variant
This will compile code (by default) specifically for riscvOVPsim, including the use of the macros from here
riscv-target/riscvOVPsim/compliance-io.h
If you wish to compile for spike, then the command should be
$ make RISCV_TARGET=spike all_variant
This will compile code using the macros from here
riscv-target/spike/compliance-io.h
using this flow, the code fragment you referred to in your original post for FN_WriteStr, should not exist, if it does there is an error in the compilation
if you are targeting your own simulator

those macros and worked fine with our simulator & spike.
you need to define those macros, probably the same as spike, and again, if there is a call to FN_WriteStr in the resulting elf file, this is probably an error.

Finally, from the log you provided earlier, only one test failed on spike, which is I-MISALIGN_LDST-01, do you agree ?
If so this may be because of the SPEC changes for the 2.3 ratification has changed the way spike handles the misaligned load and stores - this will need investigating
Thx
Lee

@eroom1966
I agree only one test case failed in rv32i, still more tests are there to generate right, why it stops the test generation? or is there any switch to control this?
Instead of the spike, I wish to target our simulator, is it possible with the compliance environment?
Thanks
Dore M R

@MRDore

I agree only one test case failed in rv32i, still more tests are there to generate right, why it stops the test generation? or is there any switch to control this?

The test generation/execution runs in groups, so you can manually run the other groups individually
$ make RISCV_TARGET=spike RISCV_ISA=
It would be worthwhile for the group if you could debug why spike has changed behavior, and whether this is correct.

Instead of the spike, I wish to target our simulator, is it possible with the compliance environment?

Yes, simply add your simulator as a new target, and define the macros in
riscv-target//compliance_io.h
These macros can be defined as empty, they are only required for additional debug capabilities
Thx
Lee

@eroom1966
$make clean
$ make RISCV_TARGET=spike RISCV_DEVICE=rv32ua, this is not working I tried all groups, it took an integer(rv32i group) first and generation fails with the same error as follow.  is this due to our spike issue? Could you provide me with the passed logs which targeted spike and tested with individual groups other than rv32i(don't want integer)?
_

ffffffff
ffffffff
... FAIL
Check         I-NOP-01 ... OK
Check          I-OR-01 ... OK
Check         I-ORI-01 ... OK
Check     I-RF_size-01 ... OK
Check    I-RF_width-01 ... OK
Check       I-RF_x0-01 ... OK
Check          I-SB-01 ... OK
Check          I-SH-01 ... OK
Check         I-SLL-01 ... OK
Check        I-SLLI-01 ... OK
Check         I-SLT-01 ... OK
Check        I-SLTI-01 ... OK
Check       I-SLTIU-01 ... OK
Check        I-SLTU-01 ... OK
Check         I-SRA-01 ... OK
Check        I-SRAI-01 ... OK
Check         I-SRL-01 ... OK
Check        I-SRLI-01 ... OK
Check         I-SUB-01 ... OK
Check          I-SW-01 ... OK
Check         I-XOR-01 ... OK
Check        I-XORI-01 ... OK

FAIL: 1/55
make[1]: *** [verify] Error 1
make[1]: Leaving directory `/wdc/proj/riscv/mustang/users/dore.m.r/compliance_test/26feb/riscv-compliance/riscv-compliance'
make: *** [all_variant] Error 2

_
Spike issue I will check and I will try by adding our simulator as a target.
Thanks & Regards
Dore M R

@MRDore
make RISCV_TARGET=spike RISCV_DEVICE=rv32ua RISCV_ISA=rv32ua

Thanks, @eroom1966.


animated zoom in at "What we do section"

Repro : open https://byidmore.com , and scroll down to "what we do" section, hover one of project.

Reality : project screenshoot zoom in on hover, but no animation.
Expectation : we want to added animatino when user hover on project screenshoot. For reference please visit the following page https://www.android.com, scroll down to "android in real life"
Note : please read readme to know about project and how to contribute, thanks.

closed


[mlr] add MulticastListenersTable on BBR

This PR adds the Multicast Listener Table for BBR:

[x] Implements Multicast Listener Table on BBR

[x] Adds registered MAs to MulticastListenerTable
[x] Reject when the table is full or the multicast address is invalid and return failed status
[x] Respond with unsuccessful status along with failed addresses
[x] Expire Listeners from MulticastListenerTable per second (using MinHeap for better performance)

[x] MLR ehnahcement

[x] Re-register only failed multicast addresses (used to register all registering multicast addresses)

[x] Reference Device only APIs

[x] Some APIs are defined for reference devices and tests.

[x] Add tests

[x] Add unit test: test_multicast_listener_table.cpp (runs for 1.2-bbr only)
[x] Add functional tests

MLR PR List:

#5236 Parent send MLR.req on behave of Children
#5292 Add MulticastListenersTable on BBR <== This PR
#5248 Send MLR.req for locally Netfi MAs MERGED
#5250 Add the MLR log region  MERGED

Hi @librasungirl @abtink @jwhui
This PR implements the Multicast Listeners Table on BBR.
For now, the PBBR only saves MAs to the table and respond with failed addresses.
BMLR on backbone and other MLR related backbone features on BBR will be implemented upcoming PRs.
Please take a look.
Thanks,

@simonlingoogle , please help resolve conflicts.


Add ephemeralStorageSize option to defineFunction

Environment information
System:
  OS: macOS 14.7
  CPU: (10) arm64 Apple M1 Max
  Memory: 210.70 MB / 32.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v20.11.1/bin/yarn
  npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
  pnpm: 8.15.6 - ~/.nvm/versions/node/v20.11.1/bin/pnpm
NPM Packages:
  @aws-amplify/auth-construct: 1.5.0
  @aws-amplify/backend: 1.7.0
  @aws-amplify/backend-auth: 1.4.0
  @aws-amplify/backend-cli: 1.4.2
  @aws-amplify/backend-data: 1.2.0
  @aws-amplify/backend-deployer: 1.1.9
  @aws-amplify/backend-function: 1.7.5
  @aws-amplify/backend-output-schemas: 1.4.0
  @aws-amplify/backend-output-storage: 1.1.3
  @aws-amplify/backend-secret: 1.1.4
  @aws-amplify/backend-storage: 1.2.2
  @aws-amplify/cli-core: 1.2.0
  @aws-amplify/client-config: 1.5.2
  @aws-amplify/deployed-backend-client: 1.4.1
  @aws-amplify/form-generator: 1.0.3
  @aws-amplify/model-generator: 1.0.9
  @aws-amplify/platform-core: 1.2.0
  @aws-amplify/plugin-types: 1.4.0
  @aws-amplify/sandbox: 1.2.5
  @aws-amplify/schema-generator: 1.2.5
  aws-amplify: 6.8.2
  aws-cdk: 2.167.1
  aws-cdk-lib: 2.167.1
  typescript: 5.6.3
No AWS environment variables
No CDK environment variables

Describe the feature
I would like to add an option to defineFunction to specify the size of ephemeral storage.
defineFunction({
  entry: './test-assets/default-lambda/handler.ts',
  ephemeralStorageSize: 1024, // <- like this
})

See:

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda.Function.html#ephemeralstoragesize
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-lambda-function-ephemeralstorage.html

Use case
When using defineFunction with Amplify Gen2, function has an ephemeral storage size of 512 MB.
I will get an error No space left on device when dealing with large size files in Lambda functions.
I would like to increase the size of the ephemeral storage with ephemeralStorageSize option.

Hey @fossamagna, thank you for filing this issue and the contribution. Marking this as feature request.
For folks looking to increase this you can override/extend the configuration on the backend.ts filke
const backend = defineBackend({
  myFunction,
});

backend.myFunction.resources.cfnResources.cfnFunction.ephemeralStorage = {
  size: 1024,
};

@ykethan
Thanks for showing us how to do the configuration.
I would be happy to review your Pull Request for this issue.


Add possibility to specify a different repo for tool versions

I would like to use this: https://github.com/working-group-purescript-es/purescript/releases/tag/v0.15.0-alpha
But I think the repo is hardcoded, right?

Here's the current list of possible inputs:
https://github.com/purescript-contrib/setup-purescript/blob/main/action.yml
Perhaps we could change the version key so it accepts more than latest or a SemVer version. Instead, it could accept latest, a SemVer version, a Git tag, or a full URL like the one you specified and attempts to download it based on how it's parsed. We'd need to write a string-parsers parser for it.


Release v15.0.0

Description
Merge all the beta changes into master to release new v15
Checklist

[ ] Updated the Readme.md (if required) ?

This PR should get merged in first: https://github.com/PolymeshAssociation/polymesh-sdk/pull/811

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


star-rating feature #24

#40  completed check it and merge it.

yo @Mukesh-ghildiyal just wanted to know where are you storing the ratings ?

right now from nowhere but i can store it in local storage if you allow

i am not the maintainer i was just curious

hii @Mukesh-ghildiyal,
I am thankful and appreciate your willingness to contribute and the time and thought you’ve put into this idea.
However, I’ve decided to keep the project more focused on displaying quotes without adding a review or rating system for now. The simplicity of the current setup is something I’d like to maintain, as it aligns with the original goal of the project.
Thanks again for your understanding and your effort!


Add Python3 Support

What does this PR do?
Add python3 support to btrfs
Motivation
Make the check compatible with Py2 and Py3
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2579 into master will decrease coverage by 17.68%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #2579       +/-   ##
==========================================
- Coverage   84.58%   66.9%   -17.69%
==========================================
  Files         632       4      -628
  Lines       35508     142    -35366
  Branches     4321      12     -4309
==========================================
- Hits        30036      95    -29941
+ Misses       4173      43     -4130
+ Partials     1299       4     -1295


ACCUMULO-4170 Clarify ClientConfiguration javadocs

ACCUMULO-4170 Clarify ClientConfiguration javadocs
Updated the javadoc information with the ClientConfiguration class.
Specifically reworked the default search path information to be
displayed as a list rather than inline, thereby easing readability.
Reworded a few of the sentences and moved the path order up to the class
level rather than the method level.

Thanks @keith-turner. I've rendered the javadocs for all versions on my local machine and they render correctly.

I can merge this.  @jmark99  does #307 currently have the changes you want for 1.8?  If so I will look at that when merging forward.

Yes, @keith-turner , #307 has the correct documentation for 1.8. This documentation is also valid for the current master line of development. These was a slight modification to the loadDefaults() method between 1.7 and 1.8 that necessitated a small change to the documentation.

@jmark99 I squashed+merged the changes.   There was one diff, I ran mvn compile and it reformatted some stuff.


Deserialization from UTF-8

The page says that Json.Deserialize(ReadOnlySpan<Byte>) is capable of understanding UTF-8 text, but this is not true!
For instance:
foreach (var file in _env.ContentRootFileProvider.GetDirectoryContents(path)) {
  Span<byte> fileContents = stackalloc byte[(int)file.Length];

  file.CreateReadStream().Read(fileContents);
  _dataSchemas[file.Name[..^".json".Length]] = JsonSerializer.Deserialize<DataSchema>(fileContents)!;
}

will fail, because a .json file created inside Visual Studio 2022 (as a text file) contains an UTF-8 BOM (0xef, 0xbb, 0xbf) and the deserializer complains about that 0xef byte in the first position.
Either Json.Deserialize is not compatible with UTF-8 (which is allowed to have a BOM), or it have a bug that don't consider BOM at all, so we have to treat this exception ourselves:
if (fileContents[0] == 0xef) {
  _dataSchemas[file.Name[..^".json".Length]] = JsonSerializer.Deserialize<DataSchema>(fileContents[3..])!;
} else {
  _dataSchemas[file.Name[..^".json".Length]] = JsonSerializer.Deserialize<DataSchema>(fileContents)!;
}

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

ID: 588ae32f-3429-143f-824c-5ab2d046d24a
Version Independent ID: 002f9f2a-48d1-0671-a079-b99b9f6bab58
Content: How to serialize and deserialize JSON using C# - .NET
Content Source: docs/standard/serialization/system-text-json-how-to.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

This is the intended behavior, see https://github.com/dotnet/runtime/issues/37327#issuecomment-637857177:

its by design that the Stream-consuming APIs look for the BOM, while the byte[] and string-consuming APIs don't. The general idea behind this is that the BOM is a marker that says "the rest of the data after this BOM is UTF-xx text". Once you have a ROS<byte> or a string that is that text, any U+FEFF that occurs is part of the text itself and shouldn't be stripped.

In your case, I think the best option is to directly deserialize the Stream returned by CreateReadStream(). This has the added advantage that it bypasses your incorrect use of Read() and your dangerous and inefficient use of stackalloc.

Thanks @svick. I'm going to close this issue now.


Create Jira issues for community activities doesn't work for external pull requests (OSOE-676)

If an external contributor opens a pull request from their fork, the "Create Jira issues for community activities", just as all other workflows, will need approval to run. So, we won't get notified about somebody opening a pull request until somebody notices the pull request and approves the runs, like this:

Even if the workflow is approved to run, it'll fail because it won't be able to access organization secrets:

This is not an issue for issues and discussions.
Figure out a way around this. Can't we somehow run the workflow outside the context of the PR?
Jira issue

I found the easiest way to do this would be a scheduled job that would run every day or 12 hours. What do you think @Piedone ?

That'd be certainly a way, yes, but these are eventually disabled for less active repos:

Warning: To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

Some of our repos in question would certainly be affected.

Then the next option would be to create a webhook service tenant e.g. in Lombiq Tenants that would check these PRs through a GitHub webhook and make a REST API call to GitHub and trigger the "Create Jira issues for community activities" GitHub Action. Or simply a scheduled REST API call to trigger this action, then the webhook is not needed.

Yeah, that would work. Have a private repo just for this, that triggers the workflow for all affected OSS repos of ours, like once every day. There, I'd have a single script that triggers all such repos (so not like we need a separate workflow for each repo, all can be in one).
Need to document what one needs to do there when initializing a new repo.

Yeah, that would work. Have a private repo just for this, that triggers the workflow for all affected OSS repos of ours, like once every day.

That's not exactly what I was thinking, but that might be even better. Let's go with that then. Could you create this new private repo then, please? I will start the work there. The repo name could be GitHub-Jira-Sync e.g.

I found a better option; my original message I started to write is below for some tips for the webhook approach, should it still become useful.
Instead of the pull_request trigger we should use the pull_request_target one, see the docs:

Note: Workflows triggered by pull_request_target events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. For more information about the pull_request_target event, see "Events that trigger workflows."

This sounds exactly what we need, but please test (you need to do this with a fork PR for a repo where that user doesn't have write access).
So, I think what we need to do:

Update all affected repos of ours, including the open-source template repo.
Update the docs in this repo.
Check all of our active open-source repositories for PRs we missed.

Ah, I misread. I thought you wanted to have this in the Lombiq Tenants repo; didn't understand as it being OC code. But doing this in an OC workflow seems easier, also because the LOMBIQBOT_GITHUB_PERSONAL_ACCESS_TOKEN organization secret can be used as the personal access token for the trigger requests.
Note that this will need changing all workflows in all affected repos to include the webhook trigger too, and also docs how someone can implement the same thing in their repos.
BTW simply triggering "Create Jira issues for community activities" via a webhook will not be enough, since you need to somehow run the code only for newly opened repos.

By the description of the activity I thought that running it would create all missing issues for all new PRs: "Creates Jira issues for community activities happening on GitHub, like issues, discussions, and pull requests being opened. Pull requests are only taken into account if they're not already related to a Jira issue (by starting their title with a Jira issue key)."
So this isn't the case?


Fixed #28660 -- Remove CryptPasswordHasher.

See https://code.djangoproject.com/ticket/28660.

As noted on the ticket, it would need to go through a deprecation if we decide to remove it.


How can I have a offset from the top as the scrollEnd position?

May be have an input as [scrollToOffset]="50"?

It would be very useful!

scrollYTarget="50"  should do what you wants....otherwise I haven't understood.

use scrollOffset option.


Executable still needs modules

Hello,
The executable I generated gives the following error on startup:
pkg/prelude/bootstrap.js:1178
throw error;
^
Error: The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module 'D:\snapshot\BROT2\node_modules\grpc\src\node\extension_binary\node-v64-win32-x64-unk
nown\grpc_node.node'

If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.
at Object. (D:\snapshot\BROT2\node_modules\grpc\src\grpc_extension.js:43:17)
at Module._compile (pkg/prelude/bootstrap.js:1254:22)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:711:10)
at Module.load (internal/modules/cjs/loader.js:610:32)
at tryModuleLoad (internal/modules/cjs/loader.js:549:12)
at Function.Module._load (internal/modules/cjs/loader.js:541:3)
at Module.require (internal/modules/cjs/loader.js:648:17)
at Module.require (pkg/prelude/bootstrap.js:1159:31)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (D:\snapshot\BROT2\node_modules\grpc\src\client_interceptors.js:145:12)

I want to be able to run it on a pc that doesn't have any of the modules installed. I tried adding it in a require call and in package.json but that doesn't seem to work.

I am facing the same issue.


[Backport 2.x] [Tiered caching] Integrating IndicesRequestCache with CacheService controlled by a feature flag

Description
Backports https://github.com/opensearch-project/OpenSearch/pull/12533
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@msfroh Can you help with this backport PR as well?


Rancher server needs static public IP

Please assign static IPs to Rancher and Harbor for workshop preparation.

amended the script to honor the static IP flag for rancher and rke2 in azure/rancher-harbor-acr scenario. See cd266d0803f6817a0e52e61c859e586b0f35551f


Add an ARCHITECTURE.md to the repo

Currently it is difficult to get a "big picture" understanding of Bevy's code base. Adding an ARCHITECTURE.md - described by Maklad here - would be a good first step toward providing mental scaffolding.
This was previously brought up in the CONTRIBUTING.md issue.

I'm not entirely convinced this should exist. It's hard to maintain, high visibility and requires a lot of expertise to write.
What would you want to see in this?

I gave it a look, and it looks like that it's so high level that it doesn't require constant maintenance. I'm not particularly convinced to put it as a separate piece of information. I would rather include it in elsewhere. I think the bevy crate-level documentation would be a not perfect, but good place.

I prefer that. I would also like to make sure we have good READMEs for each of the non-standard folders in the repo, and eventually eliminate the top level docs folder completely.

I would also like to make sure we have good READMEs for each of the non-standard folders in the repo

Maybe crates/README.md could be used to give a bird's eye view of the architecture of the codebase, like rust-analyzer does with ARCHITECTURE.md

I think that's a nice place for that information :)

What would you want to see in this?

A code map is the important part. What are the workspaces, how are they tied together, what's making them tick.

Maybe crates/README.md could be used to give a bird's eye view of the architecture of the codebase, like rust-analyzer does with ARCHITECTURE.md

This would probably work. The key points are this should be maximally discoverable and should form a basis to which an understanding of Bevy can start being hung off of. I think a good example of the target specificity would be Blender's code layout and directories explained.

The Blender code layout just gave me the idea that we could have a diagram of all the in-engine plugins all grouped by feature.
Another thing that can be taken is the layered approach: core, reflect and tasks on the bottom; ecs and app in the middle; and all the plugins on the top.


Add CA cert buildpack

Signed-off-by: Andy Brown<EMAIL_ADDRESS>
Summary

Will resolve #308. Relies on https://github.com/paketo-buildpacks/occam/pull/84 being merged so that the DockerContainerRun has WithVolume functionality.
Adds support for the CA Certificate buildpack and adds integration tests for how this can be used.
Note for reviewers: We made the choice to add a separate test context for the CA Certificate cases, rather than include them in the all encompassing "utility buildpack" test. This is because the CA Certificate apps are more complex, and I didn't know if it would make it less clear what the other utility buildpacks are doing. I can move them all into one test if y'all think that would be better though.
See https://github.com/paketo-buildpacks/paketo-website/pull/112#pullrequestreview-604354630 for Paketo Website docs changes.
Use Cases

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[X] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.

Maybe in the same testdata have 1 dir for client-key-pairs, 1 dir for bindings, and separate dirs like node_server, npm_server etc?

Consolidated test apps per your suggestion in https://github.com/paketo-buildpacks/nodejs/pull/341/commits/df3be442dc9ce155db065af8d3010a2b16b8da24. The only repetitive part I could not get around were the cert.pem and key.pem in the server. There was no way that I could see how to  pass these in from outside the app, and symlinks don't play nicely.


Unsupported attribute — but tfstate and output has the attribute

I cannot figure this out, it's happened a couple of times and this time I'm unable to work around it.
The error I'm getting from terragrunt is

terragrunt.hcl:25,47-50: Unsupported attribute; This object does not have an attribute named "id".

My issue is that the id which I'm trying to reference is present in the tfstate, why can it not see it?
Shortened code below terragrunt.hcl

dependency "vm01" {
config_path = "../vm01"
}
include {
path = find_in_parent_folders()
}
terraform {
source = "//core/azurerm_virtual_machine_extension"
}
locals {
vm_name = "vm01"
}
inputs = {
name                  = local.vm_name
virtual_machine_id    = dependency.vm01.id
.....
}

output.hcl

output "id" {
value = azurerm_windows_virtual_machine.vm.id
}

tfstate pulled directly from backend storage account

{
"version": 4,
"terraform_version": "0.14.7",
"serial": 4,
"lineage": "abcde-guid-abcde",
"outputs": {
"id": {
"value": "/subscriptions/abcde-guid-abcde/resourceGroups/rg-name/providers/Microsoft.Compute/virtualMachines/vm01",
"type": "string"
}
}
...........
}

terragrunt output from vm01

[terragrunt] 2021/03/16 10:26:32 Running command: terraform output -json
{
"id": {
"sensitive": false,
"type": "string",
"value": "/subscriptions/abcde-guid-abcde/resourceGroups/rg-name/providers/Microsoft.Compute/virtualMachines/vm01"
},
"resource_group_name": {
"sensitive": false,
"type": "string",
"value": "rg-name"
},
"virtual_machine_id": {
"sensitive": false,
"type": "string",
"value": "abcde-vm01guid-abcde"
}
}

The outputs are nested under outputs, so the path to id is dependency.vm01.outputs.id. See the dependency block reference for more info.

Wow, thankyou!


Examples ordered by complexity

Pony distribution and sandbox contain dozen of examples. It would be handy for the newbies if they are ordered, from simplest to the most complex, e.g. by prefixing them with numbers, like "01.helloworld", "02.circle" etc.
Having top comment in examples, what feature they try to show, would also help.

Thanks for the feedback.
The problem with numbering the examples is what order to put them in. Clearly "helloworld" should be first, but then what? The examples are a collection of unrelated examples, each intended to illustrate a language feature or usage idiom. They don't really form a coherent set that it's sensible to work though in order.
However, you are entirely correct that they should have a top comment explaining what they're trying to demonstrate. I'll try to add this soon.

Newbies would appreciate any reasonable order.
Major feature for the language would be ability to order project source files linearly. Early files would not depend on following files, and either the compiler or the IDE would ensure it.
Linearized project could then be read like a book, giving the programmer clear start and clear way how to continue. New maintainer wouldn't have to pick up something randomly, reading code wouldn't mean jumping back and forth all the time.

Restricting the source files to be used in a defined order would indeed make programs easier to read for newbies. Unfortunately it's a completely unreasonable limitation when writing code, once programs get at all complex they need to be able to have dependency cycles between files and even packages.
Here's a really simple example, the built in types String and Bool.

Bool has a method string() that generates a string representation of the bool, ie either "true" or "false".
However, String has a method eq() that compares 2 strings and it naturally returns a Bool.
So this example cannot work with ordered files.

And here's a slightly more advanced example. In our unit test package, the test controller PonyTest creates a test runner _TestRunner for each test. The runner runs the test and sends the result back to the controller for collation and reporting. So the PonyTest and _TestRunner have to be mutually dependent, it's just not possible to define one before the other.
The only general purpose language I can think of with a restriction anything like this is C/C++ which has an ordering restriction within each file, but not an ordering of files. This ordering restriction was not done as a language feature but due to technical limitations (C was defined a very long time ago when computers were much less powerful). It causes massive headaches when writing programs and people go to great lengths to work round it. Every modern language removes this restriction, and not just because they're trying to make things harder to newbies.
The only way to make a complex program easy for newbies to understand is to:

Think about this carefully when designing it.
Encapsulate everything and use lots of interfaces.
Choose names carefully.
Throw in lots of comments.

Unfortunately the language / compiler / IDE can't enforce any of that.
Restricting file order is no substitute for writing good, clear code and makes non-trivial programs impossible.

I have seen this approach (with numeric prefixes)  in C++ implementation of a Lisp variant ( https://github.com/akkartik/wart ). It was very pleasant to read. Ordering is also supported by one (non-public) Forth implementation.
It is possible to code in such linear way in C++ (thanks to forward definitions). Perhaps, with lot of effort (interfaces and traits located in separate files), it may be feasible in Pony too.

As you say, it may be possible in Pony. It would require some extra effort in the compiler (eg we'd need to provide forward declarations), but that's not a problem.
The key issue is that it makes writing programs much harder. Making code easy for newbies to read is indeed important, but it is far more important to make programs easy to write and easy to read for people familiar with the code.
Plus, as I mentioned above, there are much better ways to make code understandable.
So I'm afraid there's no way we'll be doing this.

Maybe a compromise would be to somehow label each example by difficulty: beginner, intermediate, advanced, expert. (like ski slopes). The labeling could be by subdirectories, or just a tag of some kind in the top-level comment.

Yes, for example by appending 1 .. 3 asterisks after the name.

Labelling with difficulty is not a bad idea. Using asterisks in filenames (or any other wildcard or special meaning character) is general not good as it leads to hassles on the command line. But there's plenty of other things we could do.
The problem now is deciding what difficulty each one is. This is of course entirely subjective and very much depends on the user's previous experience. Does anyone have any decent metrics for how to categorise the examples?

We currently looking at reworking all of the example code to make things easier for beginners. We'll consider this request as part of that process.


Fix type validation to check all possible branches from INSERT & UPDATE

Issues

Three different points were doing type validation: Row::new, value::from_expr and validate::validate_types.
There were several missing points, no null check for validation or missing type check.

I decided to merge into Value rather than validate because TryFromLiteral also does type validation but it was not detachable to add to validate module.
Previous validate_types wasn't able to work with some cases, e.g. Update -> update requires type validation only using Value and DataType but validate_types runs based on Row.
I also divided validate into Value::validate_type and Value::validate_null.
If the codes make Value using Value::from_expr or Value::try_from_literal, those also check types so only null validation is required.
The other cases requires validation of both null and types.

@KyGost Now I think.. tests/validate/types.rs has enough test cases to check all possible branches from INSERT & UPDATE.

Looks good!


Set email input basic browser validation

Basic form validation on the client side. Prevents accidental clicks or page reloading to show common errors.

Thanks @davidglezz

Is it me or does this change no longer exist in v2.6 ?

Removed on this commit, probably a mistake when merging:
https://github.com/PrestaShop/ps_emailsubscription/commit/3038ea2a16e618422c0f58450a07b51d2e8773b5#diff-379ede661ac5ff63283a80bc5010fcd3


add "mo" to indicate montly price

closes #697

Coverage remained the same at 82.822% when pulling fe3484111684e23ca978a4c13a369b0f5fa1b9f2 on abemassry:enable-backups-price-detail into 584a21bb5e57c53c64e5a76029bcafbae3d795bc on linode:master.


Add --cap-add as and --cap-drop to swarm services

Fixes https://github.com/docker/docker/issues/25885
Having this in place we can now use capabilities in the following CLI calls respectively in the corresponding API calls.

service create
service update

Signed-off-by: Alexander Berger<EMAIL_ADDRESS>

This PR is required for https://github.com/docker/docker/pull/26849.

As per review on Docker PR I don't think we should do this.

@justincormack @alex-berger should we close this PR?

Hey, thanks a lot @alex-berger.
We want to be able to support adding capabilities.
Right now we're stuck because of portability - there's many commands supported by docker run that are not portable or don't make sense in a cluster environment and we're trying to find the best way to add them.
Will keep you posted but we do appreciate the contribution


Use a dom differ instead of a container?

Hi Luigi, thanks for creating an awesome tool. As I was fiddling around with your library, I thought it might be interesting to add a dom differ (like this or this) to handle transition between pages instead of requiring the barba-wrapper and barba-container elements.
This would be cool because you could just add the library to an existing static site and it would make navigation faster for folks with modern browsers, and degrade gracefully for those that don't.
Had you considered something like this? Am I overlooking something obvious?

Hello @davidmerfield , interesting.
Technically I think it's feasible but, it will make barba.js much more complex, and that's just for the convenience of not adding a barba-wrapper and barba-container.
Also, without having a common "container" between two pages, I think create custom transition would be much harder.
Also, dom diffing comes with a performance cost.
Happy to discuss this further if you have any idea

Fair enough, I agree it adds a lot of complexity. It sounds like you've prioritized the inter-page transitions which I totally understand. I think I'm going to experiment and try to make something which uses a differ. Will let you know how it goes!


0015 derive seq

Thank you for your Pull Request! We have developed this task checklist from the
Development Process
Guide
to help with the final steps of the process. Completing the below tasks helps to
ensure our reviewers can maximize their time on your code as well as making sure
the oak codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task
or check off that it is not relevant to your Pull Request. This checklist is
part of the Github Action workflows and the Pull Request will not be merged into
the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull z
Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the
tidyverse style guide. Run
styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should
consider realistic data scenarios and edge cases, e.g. empty datasets, errors,
boundary cases etc. - See
Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you
fully follow the
deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords
and families. Refer to the
categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the
NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it
has an @export tag) or documentation aimed at users (rather than developers)
[x] Build oak site pkgdown::build_site() and check that all affected
examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@edgar-manukyan - Ready for your review.

Thanks so much Ramiro, looks fine to me. Just left two comments in case you want to address them. Are we going to add tests at some point?

I am happy to write the unit tests, but could you provide some input and output examples such that the tests are based on realistic examples, and also cover corner cases. (you guys have more experience here).


Recent change in versioning on the workflow client broke tests

• Failure [1.593 seconds]
Version
/go/src/github.com/deis/workflow-e2e/tests/version_test.go:16
  prints its version [It]
  /go/src/github.com/deis/workflow-e2e/tests/version_test.go:15

  Expected
      <string>: 2.0.0-dev-916fe94

  to equal
      <string>: 2.0.0-dev

Good catch and thanks, @helgi .  This change was lost amongst my pile of ToDo's; will fix pronto


support structs with fields that are struct literals

Something is not working for structs that look like:
type Foo struct {
    Bar struct {
        Key string
    }
    Value string
}

This should look like "Bar", "Value", but something isn't working properly and Value cannot be found.  A failing test case has been added to the repos.

I was never able to reproduce this and as far as I know this works fine.


Forked driver instance ignores waitForAngularEnabled

Bug report

Node Version: 6.10.0
Protractor Version: 5.11
Angular Version: n/a
Browser(s): Chrome
Operating System and Version  OS X 10.11.6
Test framework: mocha

After upgrading from v4.0.14 to v5.1.1 all tests using browser.forkNewDriverInstance() started to fail. I tried using waitForAngularEnabled instead of ignoreSynchronization but got the same result.
Example test:
it('', () => {
    const otherBrowser = browser.forkNewDriverInstance();
    otherBrowser.ignoreSynchronization = true;
    return otherBrowser.get('https://google.com')
      .then(() => otherBrowser.$('body').isDisplayed())
      .then(isDisplayed => expect(isDisplayed).to.be.true);
  });

Error:
Error while waiting for Protractor to sync with the page: "window.angular is undefined.  This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping.  See http://git.io/v4gXM for details"

Edit
It only happens when using mocha

I've noticed this happening with jasmine as well, FWIW

forkNewDriverInstance is also called on browser.restart, which means after every test the browser properties including waitForAngularEnabled) are reset to their defaults. I suspect forkNewDriverInstance should be passing in the current browser to createBrowser as the parent such that the properties are copied - does this have any unexpected consequences?

I am facing the exact issue with Node, Protractor and Chrome driver upgrades to the above mentioned versions. I am using Jasmine framework. Copying the parent browser properties to the new browser instances doesn't fix the issue.
Are there any more updates on the issue ?

This bug also causes that after restarting a browser the user profile may not be the same. Therefore, it makes impossible to perform tests that should ensure that values have been saved before the browser is closed if these are kept in localStorage or cookies.

I,m facing the same issue and tried with the fix provided by slotik and no luck :(
Anticipating the fix for the same ASAP.

In my case, the following worked:
browser2 = browser.forkNewDriverInstance();
browser2.waitForAngularEnabled(false).then(() => {
  browser2.get("yourUrlHere");
}

(and don't forget to use browser2.element(by.whatever...), that's another showstopper...)

annoying... not working

Found a solution for this:
this.newBrowser = originBrowser.forkNewDriverInstance(); this.newBrowser.internalIgnoreSynchronization = true; this.newBrowser.get('{SOME_NO_ANGULAR_URL})
Works on Protractor 5.4.2. Did not try on other versions.

@izhdykelis actually it does not inherit a lot of other options, so if you have some configs set, you would want to copy them from original driver instance as well.


Data table component

First iteration of the data table component.
It does not have support for inline editing options and should be trivial to add to a 'card'; note that the necessary styling/layout is not implemented.

It would be really nice to have a CR on this and get it merged in master before we do the next release.

Thanks @jkruder :+1:


Bug Fixes: Update Status for Matrixed PipelineTask

Changes
Prior to this commit, we were not checking the status for matrixed tasks and customTasks and only checking that status of singular TaskRun/RunObject. This is a bug since a matrixed PT would not have a nil TaskRun/RunObject since the TaskRuns/RunObjects fields would be used instead. Example functions: AdjustStartTime, IsBeforeFirstTaskRun, isScheduled, isStarted. Added test coverage.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Bug Fix: A matrixed pipelineTask will accurately reflect the status of isStarted(), isScheduled(), IsBeforeFirstTaskRun(), IsConditionStatusFalse() with the correct start time based on it's TaskRuns or custom RunObjects.

please add tests :pray

Added test cases for IsConditionStatusFalse() and isStarted().
cc: @jerop, @lbernick

Thanks for the fix and improvements on code, just one quesiont

@Yongxuanzhang Good call, updated doc string


DRAFT: Add examples-ros environment based on robostack

Related

What
Make it easier to run the ROS example by adding a robostack-based environment to pixi.
In theory this should work:
pixi run launch-turtlebot

The example can then be run as:
pixi run -e examples-ros python examples/python/ros_node/main.py

However it looks like the example has bit-rot over time and probably needs some bug fixes.

I've managed to launch rqt_graph too:


Require Minimum/Maximum Character Limit for ngx-input-tag ?

Hi,
I use your tag input component in my Angular project for my forms.
Great job ! :+1:
However, I can't fill a tag of more than 25 characters (spaces included).
Ex :

journée-du-patrimoine-fra (works well)
journée-du-patrimoine-fran (doesn't work)

Is this normal ? Otherwise, how to get no restriction about the maximum number of characters ?
Thk's !

Hmmm there shouldn't be a restriction. Sounds like a bug to me. I'll see if I can take a look over the next week.


Am I missing the obvious? (cargo build/run integration)

Do you still have to manually build the binary you wish to profile with e.g. cargo build?
I mean, if a Cargo.toml exists I'd expect the following to work:
cargo profiler  callgrind or cargo --release profiler  callgrind

I mean, if a Cargo.toml exists I'd expect the following to work:
cargo profiler  callgrind or cargo --release profiler  callgrind

BTW, profiler prints nothing after interrupting with Ctrl+C.

I'd expect it to be ordered like this cargo profiler callgrind --release but have to agree on the general thought.

@regexident Right, I meant profiler --release, the original syntax isn't even valid in cargo.

Ah my bad, can't believe I missed that. Should get that implemented.

This is in the works, should be up by tomorrow.

Bonus points for also supporting cargo profiler callgrind --release -- --some=thing -v --flag, which would then pass over --some=thing -v --flag to the running executable. 💯 *cough*

yep, this was referenced in #7. The open PR addresses most of the issues. all that needs to be addressed is binary arguments as well as custom output directories, and we're golden. seems like people are looking for similar improvements, which is good.

This is available in v1.3.0. Closing this issue, as #7 references binary arguments which still remains an open issue.

Thanks @pegasos1, beginning to look really great! Two issues:

compilation is hidden, --verbose can't be passed to cargo in any position
building and running examples, normally via cargo run --example some_example, doesn't work yet - we're already running binaries, so maybe, for super tight integration, profiler could check for available examples and build the one passed to it, like cargo profiler callgrind some_example ?

Even though it's a different issue, my comment is a much more serious problem at the moment. Not all programmes terminate naturally or it'd be impractical to wait that long.

@petevine, I'm going to open up some new issues addressing these, they should be fairly straightforward to implement. Thanks so much for pointing these out!
Also, completely overlooked the comment. Do you know if there's currently a way to catch Ctrl +C via std? I found this  crate that could help us do this, as well as this  conversation.

You can check out/comment on #14 #15 #16

Not sure about a cross-platform std solution - from the links you provided it seems it's still WIP. But on *nix you should be fine using @burntsushi's crate.
Also e.g. parity uses the ctrlc crate.


Using db.fn.count does not type check

I have an almost identical query to the following example:
const { count } = db.fn

db.selectFrom('toy')
  .select(count<number>('price'))
  .execute()

Basically, I just want to know the number of rows of a table. However, I get a type error which says roughly:
Argument of type 'RawBuilder<number>' is not assignable to parameter of type 'SelectExpression<TableExpressionDatabase<Database, "table", "table">, "table">'.
          Type 'RawBuilder<number>' is not assignable to type 'DynamicReferenceBuilder<any>'.
            Property '#private' in type 'RawBuilder' refers to a different member that cannot be accessed from within type 'DynamicReferenceBuilder'.

I can get the count if I ignore the type error and do as any (and do as { count: number} to the result). Perhaps I've misunderstood the use of db.fn.count?
EDIT: it looks like it type checks if I do count<number>('x').as('count'), but I still can't get the return value to be { count: number }.
EDIT 2: just read the whole bit on db.raw. I believe I understand what's happening now. I'll close the issue.

const { count } = db.fn

const res = await db.selectFrom('toy')
  .select(count<number>('price').as('count'))
  .executeTakeOneOrThrow()

res in the above example should be { count: number }. There's even a test case for it and it works. Could you provide a reproduction of the case where it fails?

Hi @koskimas, thanks for picking this up. I made a mistake with executeTakeOne, which can be undefined, so it's all good. Apologies for the false alarm.
May I suggest adding the as bit to the documentation here? I was quite confused why it did not work.
I'll be quite happy to contribute to the project too once I get some experience using it!

May I suggest adding the as bit to the documentation here? I was quite confused why it did not work.

Definitely! Thanks for bringing this up.

The documentation is now updated. It should be up in a couple of minutes.


Model fitting error: " Can't pickle local object 'make_subject_model..lda_logp' "

Hey, I am working on my MSc Thesis and found your toolbox, which appeared to be very useful for my study. Before anything, I would like to congratulate you on the development of the tool.
Turns out that I was trying to use it and built a simple pipeline (according to your documentation guidance) to apply to my data. Unfortunately, I am getting the following error, which appears after trying to fit the model to the data.
~\Documents\GitHub\MScMonkeyGaze\apply_glambox.py in run_glambox()
    201
    202     # perform MCMC sampling
--> 203     model.fit()
    204     print('DEBUG | 4')
    205

c:\users\boss\anaconda3\envs\env37\lib\site-packages\glambox\_model\model.py in fit(self, method, **kwargs)
    289             to GLAM model object
    290         """
--> 291         self.trace = fit_models(self.model, method=method, **kwargs)
    292         self.estimates = get_estimates(self)
    293

c:\users\boss\anaconda3\envs\env37\lib\site-packages\glambox\_model\fit.py in fit_models(models, method, verbose, draws, n_vi, step, **kwargs)
     72                 else:
     73                     step_method = None
---> 74                 trace = pm.sample(draws=draws, step=step_method, **kwargs)
     75             elif method == 'VI':
     76                 vi_est = pm.fit(n=n_vi, **kwargs)

c:\users\boss\anaconda3\envs\env37\lib\site-packages\pymc3\sampling.py in sample(draws, step, init, n_init, start, trace, chain_idx, chains, cores, tune, progressbar, model, random_seed, discard_tuned_samples, compute_convergence_checks, **kwargs)
    435             _print_step_hierarchy(step)
    436             try:
--> 437                 trace = _mp_sample(**sample_args)
    438             except pickle.PickleError:
    439                 _log.warning("Could not pickle model, sampling singlethreaded.")

c:\users\boss\anaconda3\envs\env37\lib\site-packages\pymc3\sampling.py in _mp_sample(draws, tune, step, chains, cores, chain, random_seed, start, progressbar, trace, model, **kwargs)
    963     sampler = ps.ParallelSampler(
    964         draws, tune, chains, cores, random_seed, start, step,
--> 965         chain, progressbar)
    966     try:
    967         try:

c:\users\boss\anaconda3\envs\env37\lib\site-packages\pymc3\parallel_sampling.py in __init__(self, draws, tune, chains, cores, seeds, start_points, step_method, start_chain_num, progressbar)
    359                 draws, tune, step_method, chain + start_chain_num, seed, start
    360             )
--> 361             for chain, seed, start in zip(range(chains), seeds, start_points)
    362         ]
    363

c:\users\boss\anaconda3\envs\env37\lib\site-packages\pymc3\parallel_sampling.py in <listcomp>(.0)
    359                 draws, tune, step_method, chain + start_chain_num, seed, start
    360             )
--> 361             for chain, seed, start in zip(range(chains), seeds, start_points)
    362         ]
    363

c:\users\boss\anaconda3\envs\env37\lib\site-packages\pymc3\parallel_sampling.py in __init__(self, draws, tune, step_method, chain, seed, start)
    240         # We fork right away, so that the main process can start tqdm threads
    241         try:
--> 242             self._process.start()
    243         except IOError as e:
    244             # Something may have gone wrong during the fork / spawn

c:\users\boss\anaconda3\envs\env37\lib\multiprocessing\process.py in start(self)
    110                'daemonic processes are not allowed to have children'
    111         _cleanup()
--> 112         self._popen = self._Popen(self)
    113         self._sentinel = self._popen.sentinel
    114         # Avoid a refcycle if the target function holds an indirect

c:\users\boss\anaconda3\envs\env37\lib\multiprocessing\context.py in _Popen(process_obj)
    221     @staticmethod
    222     def _Popen(process_obj):
--> 223         return _default_context.get_context().Process._Popen(process_obj)
    224
    225 class DefaultContext(BaseContext):

c:\users\boss\anaconda3\envs\env37\lib\multiprocessing\context.py in _Popen(process_obj)
    320         def _Popen(process_obj):
    321             from .popen_spawn_win32 import Popen
--> 322             return Popen(process_obj)
    323
    324     class SpawnContext(BaseContext):

c:\users\boss\anaconda3\envs\env37\lib\multiprocessing\popen_spawn_win32.py in __init__(self, process_obj)
     87             try:
     88                 reduction.dump(prep_data, to_child)
---> 89                 reduction.dump(process_obj, to_child)
     90             finally:
     91                 set_spawning_popen(None)

c:\users\boss\anaconda3\envs\env37\lib\multiprocessing\reduction.py in dump(obj, file, protocol)
     58 def dump(obj, file, protocol=None):
     59     '''Replacement for pickle.dump() using ForkingPickler.'''
---> 60     ForkingPickler(file, protocol).dump(obj)
     61
     62 #

AttributeError: Can't pickle local object 'make_subject_model.<locals>.lda_logp'

My code is identical to what you show in the "Quick Start" section, but with my data as input.
Thanks in advance for all the help!

Hey, Thank you for your interest in GLAMbox. Could you provide us with more detail on the versions of python, pymc, and theano that you are using? You can find these with pip list. Thank you! Armin

Hey Armin,
I’m the Master’s student supervised by Dr. Bruno. Thank you for your
answer!
The mentioned packages’ versions are:

python: 3.7.11
pymc3: 3.7
theano: 1.0.4

Thanks in advance for the help.
Pedro Madeira
Armin Thomas @.***> escreveu em sex., 24/09/2021 às
00:03 :

Hey, Thank you for your interest in GLAMbox. Could you provide us with
more detail on the versions of python, pymc, and theano that you are using?
You can find these with pip list. Thank you! Armin
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/glamlab/glambox/issues/26#issuecomment-926223011, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVO5U6HR7OXUEONBIMROYTUDOW3VANCNFSM5EFVLMIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
|| Pedro Madeira 50448 MIEB

Thanks for the answer! The versions are:

python: 3.7.11
pymc3: 3.7
Theano: 1.0.4

Hi @pdmadeira! Thank you for reporting this and apologies for the delay.
These pickling errors are sometimes associated with running the model on multiple cores.
Could you try running the fitting with setting the cores to 1 (model.fit(cores=1)) and see if this helps?

Hey @moltaire,
Thanks for your suggestion!
The algorithm is running fine with the single-core model fitting. It just takes a lot of time - it is running for 75 hours now. Tell me if that is expectable or not, or if I can adjust something to make it faster (if possible).

Hey @pdmadeira -- to make sure that the original error is not specific to your dataset, could you try simulating data (as described here: https://glambox.readthedocs.io/en/latest/examples/Example_1_Individual_estimation.html) and seeing whether you get the same pickling error when fitting for these data with multiple cores? Regarding your other question, you can generally shorten the sampling time by reducing the number of MCMC tuning and draw steps during model fitting (see the documentation for model.fit); However, if you do this, make sure that your parameter traces converge within the number of steps that you sample (see, e.g., the convergence_check function in https://glambox.readthedocs.io/en/latest/examples/Example_1_Individual_estimation.html). Hope this helps!

@athms just tried  the input data you use in Example_1. The error continues to occur with multi-core fitting, only working with the single-core approach.

Hi @pdmadeira, Great! Thank you for running these tests for us. It is likely that this specific pickling error in multi-core fitting results from the combination of the given theano and pymc versions with windows. We are looking into this and hope to fix this soon. Thanks for raising this issue. Is everything else working fine for you?

I'm exploring the examples and the tuning of the algorithm now, but if you could spend some advice... for a dataset including 2 subjects and 13k/14k samples regarding each one, which values do you suggest for the MCMC tune and draws parameters?


select multi date

Hii rajeshwar
Thanks for this awsome plugin,
Is there anyway to select mutli dates, I did some modification on the $scope.dateSelected function
but it did'nt worked for me.

You can only select one date with this component.


Good to have  a tutorial page for new users

The readme is not very clear.  I am wondering if there is a tutorial page on using orbit for linux systems. I am interested in getting a trace of the calls to a library of interest, including the ability to capture input  and return values.

Thanks for reminding us.  Better docs and tutorials are planned, but we should make them a higher priority.  What OS are you targeting by the way?

I am using Ubuntu 18.04 LTS. I appreciate all the hard work that goes into
making something like this. One reason I believe software development
continues to be not very strong is because of lack of tools that are
simple, robust and stable. I often find it frustrating to see tools / etc
with poor documentation.
I think being able to log the various calls to shared libraries, their
statistics,  including serialization of input / output should be an
infrastructure service that is simply available to users. Lack of these is
what causes software development buggy and not robust.
Regards,
Ramesh
On Tue, Jul 7, 2020 at 2:59 PM Pierric Gimmig<EMAIL_ADDRESS>wrote:

Thanks for reminding us. Better docs and tutorials are planned, but we
should make them a higher priority. What OS are you targeting by the way?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/orbit/issues/775#issuecomment-655094609, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB35RLOZOSBFMWAAMW6L7XLR2N5BNANCNFSM4OSFE42A
.

I think being able to log the various calls to shared libraries, their statistics,  including serialization of input / output should be an infrastructure service that is simply available to users. Lack of these is what causes software development buggy and not robust.

I totally agree, this is exactly why Orbit was started.

I am using Ubuntu 18.04 LTS.

On Linux, Orbit relies on uprobes and uretprobes to perform dynamic instrumentation.  We are using the perf_event_open api to enable the u(ret)probes.  Unfortunately, this a kernel feature that was introduced in the 4.17 kernel. To get Orbit working on Ubuntu, you'll have to either upgrade the kernel to 4.17 or upgrade Ubuntu to at least 19.04.  Once that's done, you'll have to build Orbit following the steps outlined here.
To profile locally, you'll then have to start OrbitService as root locally and launch a UI instance:
sudo ./OrbitService

then
./Orbit --local

Recently, I had to upgrade my kernel version to something like 5.6. I will
look into it and see how it goes. Finally, if possible, it will be good if
orbit can be provided as a debian package.
Regards,
Ramesh
On Tue, Jul 7, 2020 at 6:02 PM Pierric Gimmig<EMAIL_ADDRESS>wrote:

I think being able to log the various calls to shared libraries, their
statistics, including serialization of input / output should be an
infrastructure service that is simply available to users. Lack of these is
what causes software development buggy and not robust.
I totally agree, this is exactly why Orbit was started.
I am using Ubuntu 18.04 LTS.
On Linux, Orbit relies on uprobes and uretprobes to perform dynamic
instrumentation. We are using the perf_event_open api to enable the
u(ret)probes. Unfortunately, this a kernel feature that was introduced in
the 4.17 kernel. To get Orbit working on Ubuntu, you'll have to either
upgrade the kernel to 4.17 or upgrade Ubuntu to at least 19.04. Once that's
done, you'll have to build Orbit following the steps outlined here
https://github.com/google/orbit/blob/master/DEVELOPMENT.md.
To profile locally, you'll then have to start OrbitService as root locally
and launch a UI instance:
sudo ./OrbitService
then
./Orbit --local
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/orbit/issues/775#issuecomment-655182616, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB35RLOCDUUZYHG3A52POKDR2OSR3ANCNFSM4OSFE42A
.

5.6 should be more than enough.  Concerning the Debian package, it will be available soon.
Thanks for your comments Ramesh, don't hesitate to reach out if you run into issues compiling Orbit.
Cheers,
Pierric

I tried the latest release available and then realized it's rather old. I tried to install the master branch of the repo directly but I can't really manage to use. Reading the previous comments in this thread I discovered that I can run Orbit.exe -local to get inside the application but I can't figure out how to start the service. This is on windows, hope you can give me some steps on how to run the profiler locally, thanks!

I tried the latest release available and then realized it's rather old. I tried to install the master branch of the repo directly but I can't really manage to use. Reading the previous comments in this thread I discovered that I can run Orbit.exe -local to get inside the application but I can't figure out how to start the service. This is on windows, hope you can give me some steps on how to run the profiler locally, thanks!

Hi Oscar. Unfortunately, windows local profiling is currently not supported with the current master version. For this you need to fallback to the 1.0.2. release.

#4272 is actually adding a comprehensive documentation. Closing this for now. Please re-open if there is anything missing.


Change Notification Schedule Policy

When dispatching notifications through channels, we want to add the option of setting the schedule.
We would like to add an "All time" option so that alarms can be dispatched in any time.

Create New Issue from feedback: https://github.com/spaceone-dev/feedback/issues/22

I have summarized the points that are not currently working in more detail.
As you can see in the picture, the current console is blocked for full time, which means 0:00 to 24:00.

In the current development, selecting 0:00 to 23:00 means full-time.
This is the part that tells us why we need the full time option.

The places where the schedule is used in the code are user_channel_service and project_channel_service.
We want to improve it by adding full-time options.

The detailed progress is as follows.

Full-time option function development
Add the full-time option to the corresponding api's protobuffer.
Test run in local environment
Discuss API spec finalization with @whdalsrnt
Test run in dev environment after PR


MENU OPTIONS CHANGE AFTER LOGIN

MENU OPTIONS CHANGE AFTER LOGIN
Acceptance Criteria
GIVEN a book search engine
WHEN I am logged in to the site
THEN the menu options change to Search for Books, an option to see my saved books, and Logout

Search your books populates after login or signup


Fixing a typo

There were a few instances of "Analying" instead of "Analyzing".

Thanks!!

Just saw the same :-) #redeploy
Loving this so far btw! Exciting and new...

wince< ya I may not have deployed this after this merge yet thanks for the feedback!


[NPM] NPM Debug CLI

This PR contains the code for the NPM Debug CLI that interacts with the data plane parser + converter and traffic analyzer.
To use this CLI, simply build the NPM binaries and then execute it with the flag debug. i.e /usr/bin/azure-npm debug.

@huntergregory

Write this as
var result TYPE
var err error
if () {
	result, err := c.Get(name)
} else {
	result, err := c.GetFromFile(name, cacheFile, saveF)
}
if err != nil {
	// print error
}
// print result

Whenever I see variable declarations moving further from their use, I get suspicious (that something more significant is wrong with the flow)... maybe once the branches of the if/else approach the size of the dedup or get over a handful of lines each, I would argue against this.
@nddq
Since these cmds are in a RunE, you don't need to print errs here, you can just return them and let the root invocation log and exit. And I'm not sure of this, but I think all of GetNetworkTupleFile func args need to be valid, so should we || instead of &&?

Do you have the team's go linter? You have some weird formatting like a new line before the end of a function sometimes, which GitHub doesn't like.
Could you skip the else bracket in plugin/main.go? Just say return after the if statement? Seems a little cleaner.

Then just a couple questions for my own understanding:

When would there be more than 1 os arg in main.go, and why do you skip the rest of the function when this is the case?
Why are we switching from klog to log? Also, did you mean to delete the "Start NPM version" log line?

Can you point out a case of weird formatting for me because I don't seem to find any. I run the golangci-lint every time I planned to commit the code so this should not be an issue.
Did you mean the else bracket after if len(os.Args) > 1? This is actually the entry point for NPM :)
To loop back to my previous answer, I want to start the CLI only when there is a debug command right after calling the binaries, otherwise, it would start NPM itself. That's why I have a check for the os.Args.
This is my mistake, I some how had the old main.go file. I fixed that in my most recent commit!

@rbtr

Since these cmds are in a RunE, you don't need to print errs here, you can just return them and let the root invocation log and exit. And I'm not sure of this, but I think all of GetNetworkTupleFile func args need to be valid, so should we || instead of &&?

Yep you are correct, I will fix that.


DeepSeek Chat

Hi! Do you plan on releasing the DeepSeek Chat models?

what is DeepSeek Chat ?

Actually they just released the LLM version! Thank you so much DeepSeek ❤


Update rustc to nightly-2022-12-05

Update rustc to nightly-2022-12-05.
@vakaras could you take care of this?

bors r+


D3D_g_Stream (internal) bug

As I was working on v4.0 revamped for the group of OOVPA signatures not able to overlap each other. I found out that XREF_D3D_g_Stream internally wasn't entirely accurate wording according to the manual scan function.
https://github.com/Cxbx-Reloaded/XbSymbolDatabase/blob/7b9e2d484f91aeca04b5ae9320777481e892305b/src/lib/manual_d3d8__ltcg.h#L645-L648
Which means XREF_D3D_g_Stream internally used as XREF_D3D_g_Stream[#]_pVertexBuffer instead.
With that aside, I ran some analysis references in Ghidra to find out that each "actual" XREF_D3D_g_Stream offset is +0x30 after XREF_D3D_g_Stream[#]_pVertexBuffer for both non-LTCG and LTCG titles. I managed to run unit test for both variable addresses to ensure they are 8 bytes off from each other.

Resolved in #218 pull request.


[gbc] Use latest stack

I've canceled the CI builds intentionally since the image is not updated.

Looks like this did not actually fix the issue 😞


zappa package doesn't include dist-packages

zappa --package bundles site-packages from the virtualenv. But, on some distributions, pip installs stuff into dist-packages. So, there is a problem that these platforms (e.g. AMI linux) that they don't include pip-installed packages when they zappa --package
Context
Do zappa --package on with an AMI linux box, or some other platform that does strange things to pip, so it installs stuff into dist-packages.
Expected Behavior
I would like to see all the stuff from dist-packages in the zappa package, so my thing works the same even if I build it on Amazon Linux.
Actual Behavior
The site-packages is included in the zappa package. The dist-packages are not. The stuff I installed with pip in my virtualenv is not included in the zappa package if I ran it on a wacky OS, and my thing doesn't work because it's requirements are not met.
Possible Fix

update create_handler_venv in zappa/core.py so it does stuff with dist-packages for the relevant platforms
update detect_flask_apps and detect_django_settings in zappa/utilities.py so they check dist-packages too
Is this maybe related to why /tests/tests.py#L70 is commented out?

Steps to Reproduce

Make yourself at home in an AWS Linux AMI
Create a virtualenv and activate it.
pip install a bunch of stuff, such as the requirements for you app
See for yourself how there is a bunch of stuff installed in dist-packages
do zappa --package
compare the size of the lambda.zip with one made on non-debian distribution (it's smaller, because it doesn't include the packages from your virtualenv)
see how the thing fails with unmet dependencies if you deploy it
see how the lambda.zip does not contain your requirements

Your Environment

Zappa version used: latest
Operating System and Python version: Amazon Linux AMI
The output of pip freeze: any
Link to your project (optional): N/A
Your zappa_settings.py: N/A (I think)

FWIW, this bare-bones app is adequate for reproducing the problem
https://github.com/monkeypants/debug_zappa_905

Ran into similar problems just trying to stand up a prototype on my locals.  I recommend using a sanitized docker image, something like danielwhatmuff/zappa for building and deploying.  I've baked it into my CI deploys (we use CircleCI) and haven't had an issue since.  I know it's not a fix and ideally it would be platform agnostic, but it's a workaround that I don't feel is too intrusive or counter intuitive to best practices.

yeah, the  danielwhatmuff/zappa docker image looks like a solution. I'm currently using Jenkins on Ubuntu to work around the problem.

➕ :one: on this, using the new cloud9 IDE from amazon for lambda development, and it sticks everything in dist-packages.  zappa package spits out a 40kb file 😭

❗ ❗ ❗
unset PYTHON_INSTALL_LAYOUT
and recreating the virtualenv worked.  https://forums.aws.amazon.com/thread.jspa?messageID=698785

This is caused by package system-rpm-config installed as part of "@Development tools" group defining PYTHON_INSTALL_LAYOUT=amzon. Without this variable set, everything works fine, because package is installed into site-packages directory which is in search path.

Amazon-Linux is such a beast sometimes o.O .
I was running into an issue that presented as similar to this issue, though it was related to packages being improperly installed in the system site-packages folder. Amazon-Linux's pip executable is pip-3.6 while the virtualenv uses pip3.6. If you find yourself experiencing maddening deploy issues on Amazon-Linux, check to make sure you are using the correct spelling for pip.
Not really a fix for this ticket, but this is the most similar ticket I came across, so there it is for posterity.

For me this caused Unable to import module 'handler': No module named 'werkzeug' on zappa update.