Be able to change the favicon

User story: as a publisher, I want to be able to customize my website UX by being able to change the favicon (https://en.wikipedia.org/wiki/Favicon).
referring to comment: https://github.com/datopian/flowershow/issues/541#issuecomment-1674186332
Thanks in advance!

export default {
    nextSeo: {
        // title: "MyBlog blog post",
        // description: "This is a blog about data management",
        additionalLinkTags: [
            {
              rel: 'icon',
              href: "/images/obsidian-icon.ico",
            },
          ],
      },
     // your other configs
};

this should be added to content/config.mjs file

let me know if it work...

let me know if it works...

Not the OP but no luck with the provided code. This is able to pass javascript validation, is there something I'm missing?
const config = {
  title: "Testing",
  description: "A personal blog about InfoSec, Networking, and Electronic Projects.",
  author: "Testing",
  authorLogo: "/images/me.png",
  domain: "https://testing.com",
  // navLinks: [{ href: "https://github.com", name: "Github" }],
  navBarTitle: {
      logo: "/images/logo.png" // optional
  },
  nextSeo: {
      additionalLinkTags: [
          {
              rel: 'icon',
              href: "/images/favicon.ico",
          },
      ]
  },
};

export default config;

Does not work for me either :/
No warning in deployment or in the browser console.
If I have public/assets/images/logo.png file it should work with this config?
const config = {
 # other config parmas
  nextSeo: {
      additionalLinkTags: [
          {
            rel: 'icon',
            href: "/assets/images/logo.png",
          },
      ],
  },
};

Did you check, what is visible in the inspector, in meta section. See if link is getting registered properly in the meta tags.
Also try removing the cache.
On Sat, Sep 9, 2023, at 16:01, Levente Csőke wrote:

Does not work for me either :/
No warning in deployment or in the browser console.
If I have public/assets/images/logo.png file it should work with this config?
const config = {
other config parmas
nextSeo: {
additionalLinkTags: [
{
rel: 'icon',
href: "/assets/images/logo.png",
},
],
},
};
—
Reply to this email directly, view it on GitHub https://github.com/datopian/flowershow/issues/557#issuecomment-1712479347, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF6QX7K6Z2THQ3U4QOV2S3TXZRAP5ANCNFSM6AAAAAA3X27T6Q.
You are receiving this because you were mentioned.Message ID: @.***>

@tardigrde, @avinashkanaujiya, @delversclub, @rc-austinoneil
I can confirm the favicon is not customizable atm. Thank you for flagging your interest in this feature! I'll do my best to include this in the next version.

Closing as duplicate of #277


Add TypeScript preset and update rollup config

This pull request fixes 1 alert when merging 4de3216e32760e9e10e94ba446e55a654f06ca56 into 6c79f0cd75e9ce2ab7893023ec21f19df00a5a90 - view on LGTM.com
fixed alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com


auro-accordion: padding exists when there is no heading content

Describe the bug
When using JUST a trigger and no header, there is 16-24px of padding added. We are expecting no padding when no content is added.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@gusnaughton I need more context for this. Can you include the code you are trying to use and a screenshot of the undesired output.

I'd argue that this is not a bug, but an unexplored feature. The design intent of the accordion is to always have context for the unfolded content.
If there is no header, what is the context of the hidden content.
Please provide examples of the design intent and the please provide the name of the designer so that we can follow up on this.

I am going to loop this in with the thought of redefining how this element works.
Bolting on new features to address small updates is a slippery slope. What I really see here is a request to redefine the scope of the element to allow for more flexibility in trigger and customization of UI without having the element to directly support all these minor one-offs.


Release

:tada: This PR is included in version 1.1.4-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


chore(avm): remove shifts from full row

These values are not used by the circuit builder, rather they are constructed virtually by the prover.

#7327  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Maddiaa0 and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:mint_public): 61.1 (-88%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 177 (+188%)
protocol_circuit_witness_generation_time_in_ms (private-kernel-init): 385 (-19%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,761 (+1%)
1,559 (+1%)
712
757 (-1%)
777

proof_construction_time_sha256_30_ms
11,892 (+2%)
3,250 (+5%)
1,409 (-1%)
1,437 (+1%)
1,463

proof_construction_time_sha256_100_ms
44,126 (-3%)
11,854
5,471 (+1%)
5,394
5,369 (+1%)

proof_construction_time_poseidon_hash_ms
79.0 (+1%)
34.0
34.0
58.0 (+2%)
87.0

proof_construction_time_poseidon_hash_30_ms
1,525 (+1%)
419 (+1%)
201 (+1%)
227 (+1%)
267

proof_construction_time_poseidon_hash_100_ms
5,785 (+1%)
1,577 (+1%)
723
788 (-3%)
797 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,476
9,472
9,452

l1_rollup_execution_gas
611,215
611,362
611,493

l2_block_processing_time_in_ms
763 (-10%)
1,420
2,720 (-2%)

l2_block_building_time_in_ms
20,875 (-2%)
41,987
82,058

l2_block_rollup_simulation_time_in_ms
20,875 (-2%)
41,987
82,058

l2_block_public_tx_process_time_in_ms
17,861 (-2%)
38,768
78,901

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,045
9,865

node_database_size_in_bytes
12,279,888
16,183,376

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
67.2 (-1%)
13,790

GasToken:set_portal
14.4 (-27%)
3,339

Token:constructor
91.8
23,692

FPC:constructor
61.6 (-2%)
13,592

GasToken:mint_public
52.3 (+2%)
10,158

Token:mint_public
:warning: 61.1 (-88%)
19,034

Token:assert_minter_and_mint
:warning: 177 (+188%)
12,925

AuthRegistry:set_authorized
32.1 (+4%)
7,812

FPC:prepare_fee
108 (+3%)
15,062

Token:transfer_public
40.6 (-14%)
31,218

FPC:pay_refund
128 (-6%)
25,260

Benchmarking:increment_balance
2,206
15,267

Token:_increase_public_balance
55.8
15,006

FPC:pay_refund_with_shielded_rebate
116 (+1%)
26,347

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.156 (-4%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3 (-2%)
16.7 (-4%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.597 (-2%)
0.513 (-4%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.0 (-1%)
75.6 (-10%)
132 (-26%)
245 (-1%)
471 (-11%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.490 (-1%)
0.465 (-10%)
0.453 (-26%)
0.444 (-1%)
0.440 (-11%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.5
112 (-1%)
183 (-7%)
353
696 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.503
0.501 (-1%)
0.486 (-6%)
0.478
0.477 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
72.6
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.517
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
74,057
667,850

Transaction size based on fee payment method
| Metric |  |
| - |  |

Merge activity

Jul 3, 6:05 PM EDT: @fcarreiro merged this pull request with Graphite.


Accelerator Azure Devops instructions steps 3.5.2 & 3.5.3 misleading

Describe the bug or the issue that you are facing
Hi,
Following your step by step to import the MLOps v2 accelerator repos into Azure DevOps.
After importing the 3 repos (3.3, 3.4), the next step shows creation of new repo (3.5.2) which the screenshot suggests mlopsv2demo
Step 3.5.3 confusingly shows repo named mlopsv2 (which is none of the names for repos on guide).
Step 3.6 suddenly jumps back to Pipelines, and does not indicate if this is for repo mlopsv2demo for example. Clarification here please.
Also step 3.6.1 shows repo mlopsv2, again none of the repos imported or created new in earlier steps.  Same for step 3.7 etc.
These steps really need to be bullet-proof and explicitly name the repo associated with the step, especially if the screenshot is incorrect.
Thank-you anyway for a great accelerator!
Steps/Code to Reproduce
N/A - described earlier
Expected Output
N/A - described earlier
Versions
N/A - described earlier
Which platform are you using for deploying your infrastrucutre?
Azure DevOps (ADO)
If you mentioned Others, please mention which platformm are you using?
No response
What are you using for deploying your infrastrucutre?
Terraform
Are you using Azure ML CLI v2 or Azure ML Python SDK v2
Azure ML CLI v2
Describe the example that you are trying to run?
N/A - described earlier

Reviewing the issue.

Reviewing the issue.

Thanks, Generally there's an issue where the step-by-step text and naming of repos used is not fully consistent, especially with the screenshots. E.g. sometimes mlopsv2demo is used, other occasions -test is used. And include an instruction if you cane right back out of a repo to a pipeline. Basically instructions a Golden Retriever can follow :)

Reviewing the issue.

Thanks, Generally there's issues where the step-by-step text and naming of repos used are not fully consistent, especially with the screenshots. E.g. sometimes mlopsv2demo is used, other occasions -test is used but a -test repo was never created in the Setting up ADO section. And include an instruction if you come right back out of a repo to a pipeline. Basically instructions a Golden Retriever can follow :)

The screenshot in the 3.5.3 step shows mlopsv2 because that is the project name. I agree this is confusing. Would it be better to name the project something more descriptive like mlopsv2-project?
For 3.6 would it be more descriptive to include the project name?
Example:

3.6 Open the Pipelines section of the mlopsv2 project and click on the 3 vertical dots next to the Create Pipelines button. Select Manage Security

3.6.1 - As I mentioned before the project name is mlopsv2 in the documentation. Maybe calling out in the earlier steps (2.2) when we create the project what the name will be for the rest of the tutorial?


Couple of edge cases are handled wrong

I looked a bit through the code of this plugin (extremely readable btw :) ) and found a bug and couple things which are weird (note though that I don't have any experience writing GIMP plugins and haven't programmed in C for a long time, so I might wrongly think that something is wrong even though it's correct):

The only bug I'm certain about is that a QOI_OP_RUN doesn't cause an update of the array, because it looks like the array was already updated when the last pixel was processed.  But this isn't true when the first pixel is #000000FF, because the previous pixel is initialized with #000000FF, but the array is with #00000000.  The issue is well-known: phoboslab/qoi#258
I'm not entirely sure whether maybe I am the one confusing something, but I think the pixel_index > max_pixel_index + run in line 280 should be pixel_index + run > max_pixel_index.
In the read implementation there appears to be an ++column_index; missing in the QOI_OP_RGB section.
The variable name max_pixel_index is technically speaking wrong, because what it actually stores is the length of the pixel array and the last (i.e. maximal) index is of course one less.  (I know this is extremely nitpicky, but if I'm already unnecessarily complaining I can at least be thorough.)
The dr_db variable which stores the values for dr and db look like the dr_dg and db_dg of the standard, but is completely different. (again: extremely nitpicky)
That's probably just because I don't know C/GIMP, but the QOI_COLORSPACE_COUNT variant of the enum QoiColorspace seems to be unused.

Thanks for the pull request and kind words:) This is my first GIMP plugin so there is a possibility that the code that's interfacing with GIMP is completely wrong. I appreciate the thorough review, and I'll try to comment on all of your points:

Great catch!
That is also correct. I think I had the loop inside of the if earlier and forgot to change the condition.
Yeah I was a bit conflicted when choosing the name. Something like pixels_length or pixel_count would be better.
Are you referring to the fact that the names have a similar structure but that the values they store represent completely different things? I understand that this could confuse someone looking at the code. We could either inline the read from the file data or change the name to something less confusing.
This is a habit I've picked up from this blog post by Casey Muratori. In this case it was unused, but I always include a count member in my enums so that I can easily iterate over them or create an array with space for each variant. Something like this:

for (guint32 colorspace = 0; colorspace < QOI_COLORSPACE_COUNT; ++colorspace) {
    ...
}

All your changes look good to me and I'd be happy to merge them:)

Are you referring to the fact that the names have a similar structure but that the values they store represent completely different things? I understand that this could confuse someone looking at the code. We could either inline the read from the file data or change the name to something less confusing.

As I wrote it's extremely nitpicky.  I just noticed it and thought I tell you about it.  (If you do something about it, I think a rename is better than inlining – the lack of inlining is exactly one of the primary reasons it felt so very readable to me and looked like conforming to a very good coding standard.)

This is a habit I've picked up from this blog post by Casey Muratori. In this case it was unused, but I always include a count member in my enums so that I can easily iterate over them or create an array with space for each variant.

Oh, this is extremely clever!  Next time I write an enum I'm certainly going to do this. :)

Thanks for the input! You actually inspired me to look at this project again and try to fix some things I never got around to do.

[...] the lack of inlining is exactly one of the primary reasons it felt so very readable to me [...]

I'll keep this in mind for the future.


Events Page UI

Issue Type: UI
Description:

Make UI for Events Page
Set the route to /events
Use React Mui/Next UI with Tailwind CSS

Design

Hello shreya024, thanks for opening a issue, your contribution is valuable to us. The maintainers will review this issue and provide feedback as soon as possible.

I want to work on this

I want to work on this

@rick711c Assigned!Go for it

Hey @shreya024   I can Work on it can you assign me please

Hello @shreya024 ,
This is my progress, any further guidance you want me to do?

Hello @shreya024 , This is my progress, any further guidance you want me to do?

@Nishitbaria Add the header,space for filter,and place the dates to the top right corner of cards in the middle column as shown in design


Refactor init.sh for vagrant setup

Something must have changed / broken with regards to the docker
install process, because the ubuntu docker install received from
experimental.docker.com and get.docker.com no longer works.
So, I refactored the vagrant provisioning script to install things
in a more canonical way, hopefully this results in better first
time user and new setup stability

lgtm


Logs from execs/services can get dropped/cutoff

Repro test:
func TestLogDrop(t *testing.T) {
	t.Parallel()

	var logs safeBuffer
	c, ctx := connect(t, dagger.WithLogOutput(&logs))

	_, err := c.Container().
		From(alpineImage).
		WithEnvVariable("BUST", identity.NewID()).
		WithExec([]string{"sh", "-c", `i=0; while [ $i -lt 2000 ]; do echo ` + strings.Repeat("$i", 100) + `; i=$((i + 1)); done`}).
		Sync(ctx)
	require.NoError(t, err)
	require.NoError(t, c.Close())

	scanner := bufio.NewScanner(&logs)
	var i int
	expectedLine := strings.Repeat(strconv.Itoa(i), 100)
	for scanner.Scan() {
		line := scanner.Text()

		// TODO: just for debug
		t.Log(line)

		if strings.HasSuffix(line, expectedLine) {
			i++
			expectedLine = strings.Repeat(strconv.Itoa(i), 100)
		}
	}
	require.NoError(t, scanner.Err())
	require.Equal(t, 2000, i)
}

Never passes locally for me, will make it a few hundred expected lines in before missing one.
Ran into this problem IRL while debugging engine stuff w/ buildkit scheduler debug logs enabled: https://github.com/dagger/dagger/pull/7128
Only workaround was to just run a non-nested dev engine, which made the full logs available via docker logs.

I wouldn't personally consider it a bug that we ever drop logs; having some sort of limit in some part of the telemetry pipeline makes perfect sense, however:

I'm not actually sure that's what's happening here, as opposed to logs being missing due to some actual bug
Even if that is what's being hit, it seems like we hit a lot earlier than ideal. The repro above is only writing 2000 lines, which isn't particularly crazy even if they are being written rapidly.

The fact that docker logs handles it okay seems particularly telling. Obviously we have a lot more going on with our telemetry, but the fact that I can't get all the logs even just locally feels wrong.

In that PR I linked to above, I also sometimes saw errors like OpenTelemetry error: grpc received message larger than max (approximately that, based on memory), which does feel like a genuine bug.

However, I am not seeing that anywhere in the repro above, so I don't know what to make of it. Maybe red herring or maybe the error itself gets dropped sometimes in these cases?

cc @vito

Could this potentially be related to something like https://github.com/dagger/dagger/pull/7227?


query_as!/query! inference returns nullable entries on join when a bound parameter is absent

I've been debugging some joins recently and discovered that query_as! has different behavior when there are parameters bound or not.
This example case is with PostgreSQL and I've modified to use query! just so I could see what records were returned. Both macros seem to have the same erroneous behavior.
        let records = sqlx::query!(r#"SELECT schemas.*, shares.name as share_name FROM schemas, shares WHERE share_id = shares.id AND shares.name = $1"#, "rtyler")
            .fetch_all(db)
            .await;

        println!("RECORDS: {:?}", records);
        let records = sqlx::query!(r#"SELECT schemas.*, shares.name as share_name FROM schemas, shares WHERE share_id = shares.id AND shares.name = 'rtyler'"#)
        //let records = sqlx::query!(r#"SELECT schemas.*, shares.name as share_name FROM schemas, shares WHERE share_id = shares.id"#)
            .fetch_all(db)
            .await;

        println!("RECORDS: {:?}", records);

Outputs the following:
 INFO  sqlx::query           > SELECT schemas.*, shares.name as …; rows: 1, elapsed: 3.396ms

SELECT
  schemas.*,
  shares.name as share_name
FROM
  schemas,
  shares
WHERE
  share_id = shares.id
  AND shares.name = $1

RECORDS: Ok([Record { id: 970be392-5de7-479b-a6a0-b027368bcdf8, name: "samples", share_id: fcb12100-2590-496d-9578-d86e2d3ca831, created_at: 2021-05-30T21:52:44.279493Z, share_name: "rtyler" }])
 INFO  sqlx::query           > /* SQLx ping */; rows: 0, elapsed: 309.032µs
 INFO  sqlx::query           > /* SQLx ping */; rows: 0, elapsed: 419.070µs
 INFO  sqlx::query           > SELECT schemas.*, shares.name as …; rows: 1, elapsed: 2.479ms

SELECT
  schemas.*,
  shares.name as share_name
FROM
  schemas,
  shares
WHERE
  share_id = shares.id
  AND shares.name = 'rtyler'

RECORDS: Ok([Record { id: Some(970be392-5de7-479b-a6a0-b027368bcdf8), name: Some("samples"), share_id: Some(fcb12100-2590-496d-9578-d86e2d3ca831), created_at: Some(2021-05-30T21:52:44.279493Z), share_name: Some("rtyler") }])

Something about binding a parameter seems to correct the behavior :confused:

This has been reported many times already. Postgres doesn't return any nullability information and SQLx'es additional analysis seems to be a bit buggy. See #367, #696, #1126 for other issues about this (that haven't been closed yet).

@jplatte I've subscribed to those other tickets, shall I close this?

As-is I don't think this issue adds anything new, but it seems like your circumstances are a bit different so if you can provide some more information on your case (https://github.com/launchbadge/sqlx/issues/1126#issuecomment-845553872) that might help debug this issue.

riverbank=# EXPLAIN SELECT schemas.*, shares.name as share_name FROM schemas, shares WHERE share_id = shares.id AND shares.name = 'rtyler';
                             QUERY PLAN
--------------------------------------------------------------------
 Hash Join  (cost=22.19..42.42 rows=4 width=104)
   Hash Cond: (schemas.share_id = shares.id)
   ->  Seq Scan on schemas  (cost=0.00..18.10 rows=810 width=72)
   ->  Hash  (cost=22.12..22.12 rows=5 width=48)
         ->  Seq Scan on shares  (cost=0.00..22.12 rows=5 width=48)
               Filter: (name = 'rtyler'::text)
(6 rows)

CREATE TABLE public.schemas (
    id uuid DEFAULT public.gen_random_uuid() NOT NULL,
    name text NOT NULL,
    share_id uuid NOT NULL,
    created_at timestamp with time zone DEFAULT now() NOT NULL
);

CREATE TABLE public.shares (
    id uuid DEFAULT public.gen_random_uuid() NOT NULL,
    name text NOT NULL,
    created_at timestamp with time zone DEFAULT now() NOT NULL
);

Specifically we need the output of EXPLAIN (VERBOSE, FORMAT JSON) <query>, not just EXPLAIN <query>.

Oops, I misunderstood, here ya goes
riverbank=#  EXPLAIN (VERBOSE, FORMAT JSON) SELECT schemas.*, shares.name as share_name FROM schemas, shares WHERE share_id = shares.id AND shares.name = 'rtyler';
                                                QUERY PLAN
----------------------------------------------------------------------------------------------------------
 [                                                                                +
   {                                                                                +
     "Plan": {                                                                                +
       "Node Type": "Hash Join",                                                                         +
       "Parallel Aware": false,                                                                          +
       "Join Type": "Inner",                                                                             +
       "Startup Cost": 22.19,                                                                            +
       "Total Cost": 42.42,                                                                              +
       "Plan Rows": 4,                                                                                +
       "Plan Width": 104,                                                                                +
       "Output": ["schemas.id", "schemas.name", "schemas.share_id", "schemas.created_at", "shares.name"],+
       "Inner Unique": true,                                                                             +
       "Hash Cond": "(schemas.share_id = shares.id)",                                                    +
       "Plans": [                                                                                +
         {                                                                                +
           "Node Type": "Seq Scan",                                                                      +
           "Parent Relationship": "Outer",                                                               +
           "Parallel Aware": false,                                                                      +
           "Relation Name": "schemas",                                                                   +
           "Schema": "public",                                                                           +
           "Alias": "schemas",                                                                           +
           "Startup Cost": 0.00,                                                                         +
           "Total Cost": 18.10,                                                                          +
           "Plan Rows": 810,                                                                             +
           "Plan Width": 72,                                                                             +
           "Output": ["schemas.id", "schemas.name", "schemas.share_id", "schemas.created_at"]            +
         },                                                                                +
         {                                                                                +
           "Node Type": "Hash",                                                                          +
           "Parent Relationship": "Inner",                                                               +
           "Parallel Aware": false,                                                                      +
           "Startup Cost": 22.12,                                                                        +
           "Total Cost": 22.12,                                                                          +
           "Plan Rows": 5,                                                                               +
           "Plan Width": 48,                                                                             +
           "Output": ["shares.name", "shares.id"],                                                       +
           "Plans": [                                                                                +
             {                                                                                +
               "Node Type": "Seq Scan",                                                                  +
               "Parent Relationship": "Outer",                                                           +
               "Parallel Aware": false,                                                                  +
               "Relation Name": "shares",                                                                +
               "Schema": "public",                                                                       +
               "Alias": "shares",                                                                        +
               "Startup Cost": 0.00,                                                                     +
               "Total Cost": 22.12,                                                                      +
               "Plan Rows": 5,                                                                           +
               "Plan Width": 48,                                                                         +
               "Output": ["shares.name", "shares.id"],                                                   +
               "Filter": "(shares.name = 'rtyler'::text)"                                                +
             }                                                                                +
           ]                                                                                +
         }                                                                                +
       ]                                                                                +
     }                                                                                +
   }                                                                                +
 ]

@rtyler yeah our heuristics haven't really been tested on cross joins. However, it looks like you probably want an inner join with shares being the primary table:
SELECT shares.name as share_name, schemas.* FROM shares INNER JOIN schemas on shares.id = share_id WHERE shares.name = 'jtyler'

You usually want to select the most specific data first (in this case shares as you're matching on shares.name), and then join related tables. If you have an index on shares.name and schemas.share_id it'll avoid those costly sequential scans.

@abonander in my experience, the type of join doesn't matter. I'm getting the same issue with inner joins as well.
    struct Test {
        id: i64,
    }

    sqlx::query_as!(
        Test,
        "
SELECT l.id
FROM levels l
INNER JOIN users AS u ON u.id = l.user_id
WHERE u.id IS NULL OR u.id = $1
",
        author_id,
    )
        .fetch_all(connection)
        .await;

# PREPARE test (int) AS
# SELECT l.id
# FROM levels l
# INNER JOIN users AS u ON u.id = l.user_id
# WHERE u.id IS NULL OR u.id = $1;
PREPARE

# EXPLAIN (VERBOSE, FORMAT JSON) EXECUTE test(1);
                                                           QUERY PLAN
---------------------------------------------------------------------------------------------------------------------------------
 [                                                                                +
   {                                                                                +
     "Plan": {                                                                                +
       "Node Type": "Hash Join",                                                                                +
       "Parallel Aware": false,                                                                                +
       "Join Type": "Inner",                                                                                +
       "Startup Cost": 10.89,                                                                                +
       "Total Cost": 22.54,                                                                                +
       "Plan Rows": 2,                                                                                +
       "Plan Width": 8,                                                                                +
       "Output": ["l.id"],                                                                                +
       "Inner Unique": true,                                                                                +
       "Hash Cond": "(l.user_id = u.id)",                                                                                +
       "Plans": [                                                                                +
         {                                                                                +
           "Node Type": "Seq Scan",                                                                                +
           "Parent Relationship": "Outer",                                                                                +
           "Parallel Aware": false,                                                                                +
           "Relation Name": "levels",                                                                                +
           "Schema": "public",                                                                                +
           "Alias": "l",                                                                                +
           "Startup Cost": 0.00,                                                                                +
           "Total Cost": 11.30,                                                                                +
           "Plan Rows": 130,                                                                                +
           "Plan Width": 16,                                                                                +
           "Output": ["l.id", "l.title", "l.user_id", "l.parent_id", "l.data", "l.is_autosaved", "l.created_at", "l.updated_at"]+
         },                                                                                +
         {                                                                                +
           "Node Type": "Hash",                                                                                +
           "Parent Relationship": "Inner",                                                                                +
           "Parallel Aware": false,                                                                                +
           "Startup Cost": 10.88,                                                                                +
           "Total Cost": 10.88,                                                                                +
           "Plan Rows": 1,                                                                                +
           "Plan Width": 8,                                                                                +
           "Output": ["u.id"],                                                                                +
           "Plans": [                                                                                +
             {                                                                                +
               "Node Type": "Seq Scan",                                                                                +
               "Parent Relationship": "Outer",                                                                                +
               "Parallel Aware": false,                                                                                +
               "Relation Name": "users",                                                                                +
               "Schema": "public",                                                                                +
               "Alias": "u",                                                                                +
               "Startup Cost": 0.00,                                                                                +
               "Total Cost": 10.88,                                                                                +
               "Plan Rows": 1,                                                                                +
               "Plan Width": 8,                                                                                +
               "Output": ["u.id"],                                                                                +
               "Filter": "((u.id IS NULL) OR (u.id = 1))"                                                                       +
             }                                                                                +
           ]                                                                                +
         }                                                                                +
       ]                                                                                +
     }                                                                                +
   }                                                                                +
 ]
(1 row)


Reduce permission change verbosity

Current builds are too verbose when changing owners and permissions of files. That was useful when the project was less stable, but let's remove that because it disturbs some users.

Fixed in ce7db32


Refactor cypress tests to playwright

Tests
1. Wallet Connect

[x] 1A. Should connect wallet and choose stake-key to use
[x] 1B. Should connect wallet with single stake key
[x] 1C. Should disconnect Wallet When connected
[x] 1D. Should check correct network (Testnet/Mainnet) on connection

2. Delegation Tests

[x] 2A. Should show delegated DRepId on dashboard after delegating
[x] 2B. Should access delegation to dRep page
[x] 2C. Verify AdaHolder Behavior in Disconnected State
[x] 2D. Verify AdaHolder Behavior in Connected State
[x] 2E. Should delegate to myself
[x] 2F. Should change delegated DRep
[x] 2G. Should verify retire as a DRep (Moved to 3I)
[x] 2H. Verify DRep behavior in Retired State (Moved to 3J)
[x] 2I. Should check validity of DRep Id

3. DRep Registration

[x] 3A. Should show dRepId on dashboard after connecting registered dRep Wallet
[x] 3B. Should access dRep registration page
[x] 3C. Should open wallet connection popup, when Register as DRep from wallet unconnected state
[x] 3D. Should access DRep registration page in Wallet Connected State
[x] 3E. Should reject invalid data and accept valid data
[x] 3F. Should create proper DRep registration request, when registered with data
[x] 3G. Should show confirmation message with link to view transaction, when DRep registration txn is submitted
[x] 3H. Should be able to update metadata
[x]  3I. Should verify retired as DRep
[x] 3J. Verify DRep behavior in retired state

4. Proposals Visibility

[x] 4A. Should access Governance Actions page with/without connecting wallet
[x] 4B. Should restrict voting for users who are not registered as DReps
[x] 4C. Should filter Governance Action Type on governance actions page
[x] 4D. Should sort Governance Action Type on governance actions page
[x] 4E. Should filter and sort Governance Action Type on governance actions page

5. Proposals Functionality

[x] 5A. Should show relevant details about governance action as dRep
[x] 5B. Should view "Vote" button on governance action item on registered as DRep
[x] 5C. Should show required field in proposal voting on registered as DRep
[x] 5D. Should validate proposal voting
[x] 5E. Should re-vote with new data on a already voted governance action
[x] 5F. Should show notification of casted vote after vote
[x] 5G. Should show warning to the users to visit the site at their own risk, when external url is opened
[x] 5H. Should open a new tab, when external URL is opened
[x] 5I. Should view the vote details,when viewing governance action already voted by the DRep

6. Miscellaneous

[x] 6A. Should be accessible from mobile
[x] 6B. Provides error for invalid format
[x] 6C. Navigation within the dApp
[x] 6D. Proper label and recognition of the testnet network

It is completed. PR

6A. test has been moved into new ticket.
https://github.com/orgs/IntersectMBO/projects/20/views/1?pane=issue&itemId=61865747

Blocked by: #937  #938  #897

This ready to be closed now @spannercode ?


Need add event to Codeunit 5986

Hi
Please add an event to function FillInvPostingBuffer and IsHandled for the entire function
position:

Please always put the full detailed signature of the requested events.
You help us implementing the requests faster when your request contains AL code copied from VSCode instead of screenshots.
Please put the code surrounding the place, where you expect a new event call, as a text not as a screenshot.
It helps us finding the right place quickly if you put enough code to identify the unique place.
Please add [Event Request] prefix to the title if you requesting for a new event or for a modification in the existing event.

Please always put the full detailed signature of the requested events.
You help us implementing the requests faster when your request contains AL code copied from VSCode instead of screenshots.
Please put the code surrounding the place, where you expect a new event call, as a text not as a screenshot.
It helps us finding the right place quickly if you put enough code to identify the unique place.
Please add [Event Request] prefix to the title if you requesting for a new event or for a modification in the existing event.

Done

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


light-client: integration test

cf. #373
Adds an integration test for the light client.
The test spins up a light client against a single Tendermint node, where both the primary and a single witness point to that node.
It tries to verify to the highest block 20 times, at an interval of 800ms to give the chain time to advance.
The test uses a custom evidence reporter which panics if the supervisor tries to report a fork, as no fork should happen with this setup.
This PR also fixes a bug where the postcondition of LightClient::verify_to_target was only looking for verified but not trusted blocks in the light store. This bug occurs when the highest block is still the initial trusted block, which happens in this case because we start syncing to the latest height right after fetching and initializing the trusted block.

[x] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[x] Wrote tests
[x] Updated CHANGES.md

@liamsi Looking into it!

The failure came from a ~2min clock drift between the Docker container and the GitHub CI worker. Increasing the clock drift parameter to 5min (to be safe) has fixed it. @liamsi Does that seem like an acceptable fix to you?

@liamsi Does that seem like an acceptable fix to you?

Does sound reasonable. Do you understand why the clock drift is so large?

Do you understand why the clock drift is so large?

I unfortunately don't, would require more investigation. Perhaps someone else knows better? @greg-szabo?

BTW, I also get a lot of [error] sync failed: no witness left  in https://github.com/informalsystems/tendermint-rs/pull/430
Is that always clock drift issue?

BTW, I also get a lot of [error] sync failed: no witness left  in #430
Is that always clock drift issue?

@liamsi Hard to say like that. Might need to add some logging statements to figure out what's the underlying error. Perhaps we could/should even track those somehow.

@xla @liamsi Can one of please you approve for merging? :)


Fixed TypeError in requestHandlerLottery

I was normally playing on my server (everything is unchanged respect to the original version) and when I tried to do a game in the lottery I wasn't able to synchronize my progress, and I was stucked in a loop where I could only retry. Anyway, I checked the logs and this was the error it was poping up:
REQ:  0600a4a507ff
Traceback (most recent call last):
  File "/usr/lib/python3.4/wsgiref/handlers.py", line 137, in run
    self.result = application(self.environ, self.start_response)
  File "/home/bepis/fools2018/networking/server/router.py", line 105, in __call__
    return result.app(environ, start_response)
  File "main.py", line 71, in appBackendRequest
    result = request.handle(data, session_key)
  File "/home/bepis/fools2018/networking/server/request.py", line 31, in handle
    req_result = handlers.HANDLERS[req_code](list(request[5:]), sessid)
  File "/home/bepis/fools2018/networking/server/handlers.py", line 212, in requestHandlerLottery
    bytes([random.randrange(0, 255)])
TypeError: join() takes exactly one argument (4 given)

I'm using Python 3.4.2 and this is the command I run for start the server: bepis@minibian:~/fools2018/networking/server$ /usr/bin/python3 main.py
I didn't tested yet if really everything is working after this fix. At least map loading and lottery does lmao
I'll come back there in some days and I'll tell you if everything works correctly.
Oh, probably it's a really bad workaround. Don't blame me, I'm not good in python :c

I remember this mistake. It was discovered and patched quickly on the live servers, so quickly that the changes didn't even make it to the repository :D
Merging.


mdOptions not binding

The mdOptions attribute is not working for me.
options is defined on my scope like this
$scope.options = [50,100,500,1000];
```
and my table
```
<md-data-table-pagination
md-limit="query.limit"
md-page="query.page"
md-label="query.label"
md-options="options"
md-total="{{data.count}}"
md-on-paginate="onPaginationChange">
</md-data-table-pagination>
```

actually md-on-paginate also doesnt get triggered, but i solved this with $watch on page and limit.

from the code it seems mdOptions is bound to the controller ($pagination).

Any clues?

I suspect you are using version 0.8.x and looking at the documentation for 0.9.x. The attributes md-options and md-on-paginate are new in version 0.9.x. Also, the element has been renamed to just md-table-pagination.

i am having the same issue, here is a fork of your codepen http://codepen.io/anon/pen/ONVBYa
i am setting
$scope.itemsPerPageSelect = [50,100,500,1000];
and
md-options="itemsPerPageSelect" md-table-pagination='itemsPerPageSelect'
and no reaction

i got it, i needed to put in
<md-table-pagination md-options="options"...


Fixed get_time_bounds import from esmvalcore

Description
Removes import of private function from esmvalcore module.
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[ ] 🛠 Tests run successfully
[x] 🛠 The list of authors is up to date
[x] 🛠 Any changed dependencies have been added or removed correctly
[ ] 🛠 All checks below this pull request were successful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

thanks @schlunma - I am fixing this and a hitch in recipe filler due to bkwds incompatibility too in #3369 - you wanna go review that when time comes (for a new Core) and close this? Sorry I double-PR-ed, but wanted to fix the issue with recipe filler then I noticed the cmor issue with get bounds, so I was a goody two shoes and fixed that too :+1:


Docker for master?

It would be nice to have a docker version for the master. I assume this is doable?

Hi @DavidMoffatt-web
Yes it's doable, I will include it I the next release! Just one question, would you like the Dockerfile to build master OR can it just download the appropriate binary from the latest release?

Honestly, I am not sure what the best practice is. Perhaps someone with more experience can chime in? I am just a small-time homelab'er who hosts most of his stuff in docker containers. However, I assume it can always be changed in the future, so likely do what is easiest first, and then change it if it isn't best practice?

@DavidMoffatt-web could please checkout branch chore/run-master-docker and test if the docker environment fits your needs?
Instructions can be found in the same branch README.md
#13

Hrm; I am afraid not - Candidly, I am not quite sure how to launch this as I usually just run a docker compose file that handles pulling the docker image and the rest.

Hrm; I am afraid not - Candidly, I am not quite sure how to launch this as I usually just run a docker compose file that handles pulling the docker image and the rest.

Thanks for the feedback! Docker compose might make more sense because of the volume required by the tool.
Imagine you’re launching the tool with docker compose, what would be the commands you would use to get ir running?

Personally, I use a GUI to launch all my docker compose files; specifically Cosmos (https://cosmos-cloud.io/) but I know portainer and others are popular.  This is to say - I don't know what commands are used on the backend.
I really should probably learn more about how docker functions. It would likely be more helpful in this discussion. I am sorry!


observeProps surprising behavior

When using observeProps, the props stream uses only the initial prop values for the first render.
In my case, I am using Recompose.lifecycle to load or fetch some cached data.However when I had a cached value, ie WORLD, the template was still rendering with the default value HELLO
SmartFooTemplate = Recompose.compose(
  observeProps( (props$) ->
    foo$ = new Rx.BehaviorSubject("HELLO")
    return Rx.Observable.combineLatest(
      props$, foo$
      (props, foo) ->
        Object.assign {},
          props
          foo:foo
          foo$:foo$
    )
  )
  Recompose.lifecycle(
    (self) ->
       foo$.onNext('WORLD')
    (self) ->
       #Stuff I need to run when the component is unmounted.
  )
)
DumbFooTemplate = React.createClass
    render: ->
       @props.foo # = 'HELLO'
       @props.foo$.value #= 'WORLD'

This is actually a problem from lifecycle(). Lifecycle() runs the setup function in the constructor, which is, I guess, in Reacts perfect world a pure function as well (only setting state once). Calling the constructor becomes 'part of' the render function of the parent component, so something that calls .setState() in a constructor is considered an error (impure render function). For that reason, observeProps doesn't call .setState() till it is rendered, but uses .state = ... instead. This, however, does not trigger a rerender, thus you'll end up with old state.
Either lifecycle has to be altered to trigger in componentWillMount() ( @acdlite what is the reason it is on the constructor right now? ) or you should move the fetching/not fetching into the observeProps() function itself :-)

Closing because we got rid of lifecycle().


Fix init of Input CustomSerDe of function

Motivation
Right now, if topic has provided CustomSerDe for input param. still Instance tries to initialize it with DefaultSerDe and fails it argument doesn't supported by DefaultSerDe.
Modifications

Ignore initializing SerDe if CustomSerDe is provided for topic.
Fix test cases.

Result
CustomSerDe will work for input param.

@rdhabalia are you still working on this change? shall we move this to 2.1?

@rdhabalia @srkukarni I moved this to 2.1, feel free to move it back to 2.0

@rdhabalia is this still needed?

As a user, I felt it was a bug because we can pass


Automate creation of topo documentation Links

In general, Links that are required for applying the services that are provided by the ApplicationPattern or the applications of the TinyApplicationController shall be automatically created, so OperationKeyManagement can make them available for consumption (see also ALT issue #479).
Particularly, the Links required during the embedding shall be automatically created by additional forwardings that are addressing ALT://v1/add-operation-client-to-link:

Link creation has been automated as part of the regard-application process.


Field & property overriding

Hi!
I found issue caused by field & property overriding and wrote simple workaround
[ Code to reproduce issue ] ( https://github.com/Roman-Blinkov/msgpack-cli/blob/008c5c28dd16d14e232266de0fabe01df04f7c1e/test/MsgPack.UnitTest/InheritanceTest.cs )
[ Issue fix proposal ] ( https://github.com/Roman-Blinkov/msgpack-cli/commit/008c5c28dd16d14e232266de0fabe01df04f7c1e )
Check #161, please.

Thank you! I merged your request with trivial fixes.


Update custom.css

Force vertical scrollbar on body.
Why
Currently, the page reflows a little bit when zooming since the vertical scrollbar disappears, making the page larger.
How
Forcing the scrollbar means the page doesn't get wider (even a little bit) when zooming.

Thanks for your contribution :raised_hands:
Sorry for the delay in reviewing your code, it looks like this PR totally slipped through my notifications.
I tested the change on macOS with various scrollbar configurations (always visible, visible when scrolling, etc.) and it looks like the approach used in the PR does not prevent the issue in all cases. It also has the side effect of making the scrollbar always visible, even when not needed which is not ideal.
I think a better approach would be to stop enforcing an hidden overflow on the body element through CSS and instead, use JavaScript to do the same when opening the dialog while also constraining the body's width. When the dialog is closed, the overflow and width should be reset to their original values.
I'll investigate a bit more later today and test on more devices to make sure the solution works in all cases, but if it does, I'll update the PR with the new approach.

It also has the side effect of making the scrollbar always visible, even when not needed

It's probably a personal preference, but I don't like when layouts change in width for shorter or longer pages. Forcing the scrollbar means pages all have the same width so it's predictable. That was my intent at least.


Facade custom options not being passed to Producer object

Im trying to instantiate a producer with a remote kafka broker (confluent), but the custom options that im setting on the Kafka facade are not going to the final Producer class.
$producer = Kafka::publishOn('[REMOTE_ADDRESS]', 'cleaners')
        ->withConfigOptions([
            'bootstrap.servers' => '[REMOTE_ADDRESS]',
            'metadata.broker.list' => '[REMOTE_ADDRESS]',
            'security.protocol' => 'SASL_SSL',
            'sasl.mechanisms' => 'PLAIN',
            'sasl.username' => '[API_KEY]',
            'sasl.password' => '[API_KEY]',
        ])
        ->withBodyKey("test", "test")
        ->send();

This throws an exception because these configOptions are not being passed to the Conf object from rdkafka. Probably because of this line:
Junges\Kafka\Producers\Producer.php - Line 22
        $this->producer = app(KafkaProducer::class, [
            'conf' => $this->setConf($this->config->getProducerOptions()),
        ]);

Which limits the config passed to KafkaProducer::class to be only the ones returned from getProducerOptions().
Am i doing something wrong?
It works when i try to use php-rdkafka with the same configs.

Hello @renatobcj, i forgot the $this->customOptions array merge for producer configs. Fixing it now. Thanks for your report.

@renatobcj #38ca04 allows you to set custom options for producers config. Released on v1.1.3. Let me know if it fixes your issue.

@renatobcj v1.2.0 should fix this problem. Please let me know if it's working well now.


Ionic 2 beta 9 Alerts (succeeding alert issue)

Short description of the problem:
When updating to ionic 2 beta 9, I encountered an issue regarding alerts (it was working in beta 7)
The scenario is I have a prompt alert (Alert A) where it has an input and two buttons (Cancel, Ok).
On click of Alert A's "Ok", if the input is invalid, it should prompt a simple error alert (Alert B) which shows the error message and a single button (Ok) to dismiss itself, also Alert A should remain/not be dismissed when Alert B is shown. (so that user can rectify the invalid input in Alert A)
when we upgraded to beta 9, when Alert B is shown, any click on the backdrop or the Alert B's Ok button will not work (i.e Alert B cannot be dismissed)
What behavior are you expecting?
Expect that Alert B can be dismissed / Alert B's button handlers are called.
Steps to reproduce:

Present Alert A
Click on button to show Alert B
Alert B button does nothing, click on backdrop also doesn't dismiss Alert B.

let alertA = Alert.create(
  {title:"Hello Alert A",
   subTitle:"Alert A",
   buttons:[
      {text:'Cancel'},
      {text:'Ok', handler:(data)=>{
               let alertB = Alert.create(
               {title:"Hello Alert B",
               subTitle:"Alert B",
               buttons:[{text:'Ok'}]
               });
               this.nav.present(alertB);
        //return false to not dismiss alert A
        return false;
      }}
   ]
  });
this.nav.present(alertA);

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Upon checking, it seems the enabled property of Alert B component wasn't set which is preventing it to call the button handlers. Upon tracing the code, enabled property is set in its ionViewEnter which wasn't called... It seems like a bug of navcontroller (?) where Alert B's fireDidEnter is not called as Alert A's fireOtherLifecycles property is false.
Which Ionic Version? 1.x or 2.x
2.0.0-beta-9
Plunker that shows an example of your issue
http://plnkr.co/edit/oSep0drzegYmwJ8nlhJL?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.0.0
Ionic Framework Version: 2.0.0-beta.9
Ionic CLI Version: 2.0.0-beta.24
Ionic App Lib Version: 2.0.0-beta.14
OS: Windows 7 SP1
Node Version: v4.4.2

Got the same problem here. I don't know if it is the right way, but I fixed this way:
let alertA = Alert.create(
    {title:"Hello Alert A",
     subTitle:"Alert A",
     buttons:[
      {text:'Cancel'},
      {text:'Ok', handler:(data)=>{
               let alertB = Alert.create(
               {title:"Hello Alert B",
               subTitle:"Alert B",
               buttons:[{text:'Ok'}]
               });
               alertA.dismiss().then(() => {
                 this.nav.present(alertB);
               });
        //return false to not dismiss alert A
        return false;
      }}
     ]
    });
    this.nav.present(alertA);

Dismiss the alertA (which returns a promisse) and then present the alertB.

Hello! Thanks for opening an issue with us. I have started debugging this issue and am gonna put my findings here for the rest of the team. This line is getting called which means that for some reason Ionic is trying to push multiple backdrops. Beta.8 does not have this behavior, looks like a regression in beta.9.

In the meantime, if you would like a workaround you could use a toast as your error message. This may actually be better ux than showing multiple alerts at a time. Thanks for using Ionic!

im facing the same issue with the new version of alerts.. i have the same use case.. @jgw96's suggestion is actually a good one.. im considering using it.. by the way, can anyone tell me how to find what the latest version of ionic beta is out there and what's its complete changelog?

@awe-sim I would definitely suggest using a toast. We are going to fix this issue with alerts, but in my opinion using a toast here is better ux than using multiple alerts. But, as i said, that is totally my opinion (: Here is a link to our changelog. Also, we always do a post on our blog and a tweet when we do a new release. Finally, if you want to try out the bleeding edge of Ionic 2 (although you may run into issues/undocumented changes) you can run npm install ionic-angular@nightly in your ionic 2 project to get our latest Ionic 2 nightly release. Thanks for using Ionic!

thanks @jgw96 for answering all the questions.. :)

hi guys.. any word on this? i was expecting this to be resolved in beta10 but it isnt there.. in the meantime, is there a workaround that i can use by manually editing the source somewhere?

Hello @awe-sim , I have good news! We have just finished a complete refactor of how "overlay components" like alert our presented onto the navigation stack which should fix this issue. I will update this issue when a nightly is released that has these changes so that you can test it out. Thanks!

Hello @awe-sim we have a nightly out now that has the overlay components refactor. If you would like to try it out you can run npm install ionic-angular@nightly to install the nightly. Here is how to use an alert with the new api.
import {AlertController} from "ionic-angular";

constructor(private alertCtrl: AlertController) {};

coolMethod() {
  let coolAlert = this.alertCtrl.create({
    title: "Cool alert",
    message: "I am a cool alert"
  });
  coolAlert.present();
}

Hi @jgw96 .. Thank you for your response. I tried upgrading to the nightly version a couple of times but encountered some errors. After your message, I tried again and this time the upgrade went smoothly. I can see that the API has slightly changed now (the addition of AlertsController) but the issue still remains:
let alert = this.alertsController.create({
	title: 'Destroy World',
	message: 'Are you sure?',
	buttons: [{
		text: 'Cancel',
		role: 'cancel',
		handler: () => {
			console.log('CANCEL');
		}
	}, {
		text: 'OK',
		handler: () => {
			console.log('OK');
			let nestedAlert = this.alertsController.create({
				title: 'Destroy World',
				message: 'Now destroying world. Please stand by.',
				buttons: ['OK']
			});
			nestedAlert.present();
			return false;
		}
	}]
});
alert.present();

The first alert renders fine, but when the second alert renders on top of the first one, it cannot be dismissed either by clicking the buttons or the background. In alert-component.js, this section is being hit for the first alert but not the second one:
AlertCmp.prototype.ionViewDidEnter = function () {
    var activeElement = document.activeElement;
    if (document.activeElement) {
        activeElement.blur();
    }
    var focusableEle = this._elementRef.nativeElement.querySelector('input,button');
    if (focusableEle) {
        focusableEle.focus();
    }
    this.enabled = true;
};

Consequently, since this.enabled !== true, the following code does not run.
AlertCmp.prototype.btnClick = function (button, dismissDelay) {
    var _this = this;
    if (!this.enabled) {
        return;
    }
    // keep the time of the most recent button click
    this.lastClick = Date.now();
    var shouldDismiss = true;
    if (button.handler) {
        // a handler has been provided, execute it
        // pass the handler the values from the inputs
        if (button.handler(this.getValues()) === false) {
            // if the return value of the handler is false then do not dismiss
            shouldDismiss = false;
        }
    }
    if (shouldDismiss) {
        setTimeout(function () {
            _this.dismiss(button.role);
        }, dismissDelay || this._config.get('pageTransitionDelay'));
    }
};
AlertCmp.prototype.bdClick = function () {
    if (this.enabled && this.d.enableBackdropDismiss) {
        var cancelBtn = this.d.buttons.find(function (b) { return b.role === 'cancel'; });
        if (cancelBtn) {
            this.btnClick(cancelBtn, 1);
        }
        else {
            this.dismiss('backdrop');
        }
    }
};

Ahh ok, i think we got it this time. Would you mind trying this on your alerts:
import {AlertController} from "ionic-angular";

constructor(private alertCtrl: AlertController) {};

coolMethod() {
  let coolAlert = this.alertCtrl.create({
    title: "Cool alert",
    message: "I am a cool alert"
  });
  coolAlert.fireOtherLifecycles = true;
  coolAlert.present();
}

Thanks @jgw96 .. This works.. =).. The ionViewDidEnter method is hit successfully for both alerts.. And tapping the buttons or backdrop works as expected.. =)
An observation, though.. When the nested alert is dismissed, the parent alert's ionViewDidEnter is fired for the second time.. I don't see an issue with it, as it appears to set focus to the first field in the alert.. But just letting you know..
Also, I only need to set the fireOtherLifeCycles flag for the nested alert to get it to work properly..
Thanks for your help mate.. I've been blocked at this for a few days now.. Thanks for giving me a way forward.. =)

Hello @awe-sim ! Im so glad we got everything working now, thanks for being patient and working with me on this! So the reason the ionViewDidEnter event is firing on the parent alert a second time is because of fireOtherLifecycles being set to true on the nested alert. By default, alerts have fireOtherLifecycles set to false, so whenever they are closed or opened they do not trigger lifecycle events on whatever view is their parent. To get the second alert to be "enabled" correctly we need those lifecycle events to fire though which is why it works now, but it also means that the lifecycle alerts for the first alert are gonna fire when the nested alert is closed. Unfortunately, at this time i cannot think of a way around this as we never really intended to for two alerts to be open at the same time (although it works now). In the future alerts may be changed to be more native like in the way that two alerts will never be able to be open at the same time and instead will be a queue of alerts. An even better solution for your use case than the one we have put together in this issue may be creating a custom component kind of like toast, but that blocks user interaction like you need. Or, something else you could consider would be to change the workflow slightly to something like this:

Open the first alert
There is an error, the second alert is opened and the first alert is closed with its state saved to a service
User fixes error, first alert is reopened pulling its state from that service

I would suggest asking around on our forums and seeing what ideas the awesome community on there could come up with. Since this issue has been fixed i will be closing this issue, but feel free to comment if you have any other questions, as id be glad to answer. Thanks for using Ionic!

how update the alert color with ionic 2 ??


Comment mode

New comment or update existing

Testing locally
Results for image kio.ee/yalsee/yalsee:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 16.8.2022 11:00:05+0000

Testing locally
Results for image kio.ee/yalsee/yalsee:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 16.8.2022 11:00:05+0000

Testing locally
Results for image kio.ee/yalsee/yalsee:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 16.8.2022 11:00:05+0000

Testing locally
Results for image kio.ee/yalsee/yalsee:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 16.8.2022 11:00:05+0000

Testing locally
Results for image kio.ee/yalsee/yalsee:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 16.8.2022 11:00:05+0000

Testing Locally
Results for image kio.ee/kyberorg/hsr:dev
:heavy_check_mark: Total 0 vulnerabilities found
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 08:43:28+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 08:00:06+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 08:00:06+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 09:00:05+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 11:00:05+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 11:00:05+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 11:00:05+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 12:00:06+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 12:00:06+0000

Testing Locally
Results for image kio.ee/kyberorg/void-app:latest
:fire: Total 440 vulnerabilities found - 275 fixable
:no_entry: 0 critical :fire: 32 high :warning: 254 medium :triangular_flag_on_post: 154 low
Scanned with Trivy v0.29.2 from Aqua Security
Report generated at 4.10.2022 12:00:06+0000


Fix vq_vae.py

There was a problem with the function get_decoder, because when it wants to get the output shape of the encoder, it directly calls the get_encoder function without parameter, so it assumes that the current latent_dim is the default latent_dim: 16. So, to address this issue, it can just pass the current latent_dim parameter when calling get_encoder function.

Thanks!
Ok, I updated them 👍


the order

please move the "step seven" before "step four"

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

ID: 91c13083-9b29-e54b-fd85-8033ec665fcd
Version Independent ID: ce8c4647-69bc-95d4-2192-6e737d5ad5da
Content: BitLocker How to enable Network Unlock (Windows 10)
Content Source: windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock.md
Product: w10
GitHub Login: @brianlic-msft
Microsoft Alias: justinha

@TheAnahaym Can you confirm you mean move Step Seven: Require TPM+PIN protectors at startup to appear before Step Four: Create the Network Unlock certificate? There are a few instances with step 4 and step 7 in this topic so I wanted to confirm. Why does TPM+PIN need to be configured first?

Step four: Create the Network Unlock certificate.
Step seven: Create the certificate template for Network Unlock.
How can you create a certificate before a creation of the proper template? Maybe the creation of the certificate template for Network Unlock is not a part of step seven, but still it must be before the certificate creation, doesn't it?

@TheAnahaym I see, thanks for explaining. I moved that step and republished the topic.


Add Canterbury Institute of Management

University Website:  Canterbury Institute of Management
An example of 2 years ICT course: Master of Information & Communications Technology
Commonwealth Register of Institutions and Courses for Overseas Students: CRICOS Provider 03809A

Thank you team JetBrains!
Ayesh Jayasekara

@AyeshJayasekara First stage of verification passed, official domain for Canterbury Institute of Management is ciom.edu.au as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

The domain WHOIS info for ciom.edu.au is:
Domain Name: ciom.edu.au
Registrant Contact Name: Gajinder Paul
Tech Contact Name: Gajinder Paul
Registrant: AUSTRALIAN CAMPUS MANAGEMENT PTY LTD
Eligibility Type: Higher Education Institution. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@philipto Thank you for taking time to review the pull request. The JetBrains products pack for students will greatly benefit the current and future students. Keep doing what you are doing! Kudos to the team JetBrains!!


Inject dependencies into properties

Would it be possible to inject dependencies not into constructors but on properties, after the instance is created? Like this:
import { inject } from "aurelia-dependency-injection";
import { Router } from "aurelia-router";
import { Logger } from "logger";
import { Cache } from "cache";

export class Parent {

    @inject(Router)
    router;

    @inject(Logger)
    logger;

    @inject(Cache)
    cache;

    somethingNotInjected;

    constructor(somethingNotInjected) {
        this.somethingNotInjected = somethingNotInjected;
    }

}

export class Child extends Parent {

    constructor() {
        super("this can not be injected");
    }

}

This would permit to free constructors from being the only channel to pass dependencies and child classes to know about them, which could be a major restriction when parent classes depends on many (same behaviour occurs in Java CDI, for example).
For now, I'm using the main Container.instance to instantiate the properties on the parent classes, but it obviously doesn't inject the right instance when the child class is associated with a child-container (like Router).

I propose this: https://github.com/aurelia/dependency-injection/pull/85

Closing this since you've got a nice plugin for it now.

Can we move this into the core framework? This way we don't need to use an external package (which may not be supported in the future) and we don't have to bother with two different "@inject" decorators. Also I think in most application this feature is needed (everywhere where you have a base class for the components and which requires injected services).


Sia Daemon v1.3.3

BUG REPORT
Stack Trace or error message
Expected Behavior
How to reproduce it (as minimally and precisely as possible)
Environment

Sia version:
OS:

Uptime is no longer being reported by 1.3.3

I don't appreciate being accused of playing favorites. None of the devs are currently running serious hosting operations anyway. Please keep your comments confined to your existing issue (#3141).


OneOffProductsDomainRequireProduct.php

Hi there!
Missing documentation regarding configuring multiple products.
Sincerely,
Wepwawet

Hi,
it is all described here. Let me quote the relevant part.

kt_onetimeProducts array of product IDs to treat as "one-off" (customer is not allowed to order the same product multiple times)

In other words you should do something like follows:
define('kt_onetimeProducts', array(10, 11, 12, 15)); // Array of product IDs to treat as "one-off" (customer is not allowed to order the same product multiple times

Hi,
it is all described here. Let me quote the relevant part.

kt_onetimeProducts array of product IDs to treat as "one-off" (customer is not allowed to order the same product multiple times)

In other words you should do something like follows:
define('kt_onetimeProducts', array(10, 11, 12, 15)); // Array of product IDs to treat as "one-off" (customer is not allowed to order the same product multiple times


docs(samples): Fix preemption history snippet filter

The : operator seems to perform an equality and not a substring match on the targetLink field. You can check the behavior with the live API reference. Without this change preemption_history always returned an empty list when one provided an instance_name.
This might also seen as an API bug but the code snippet for preemption history can also be simplified this way.

=================================== FAILURES ===================================
________________________________ test_get_image ________________________________

self = <contextlib._GeneratorContextManager object at 0x7f3831d225f0>
typ = None, value = None, traceback = None

    def __exit__(self, typ, value, traceback):
        if typ is None:
            try:
>               next(self.gen)
E               AttributeError: 'SysCapture' object has no attribute '_old'

/usr/local/lib/python3.10/contextlib.py:142: AttributeError

The samples have moved to python-docs-samples


Documentation: Create CODE_OF_CONDUCT.md

This project is currently lacking one.
Here is github's open source documentation on the topic:

https://opensource.guide/code-of-conduct/

And here are other code of conduct templates/resources to reference

http://todogroup.org/opencodeofconduct/
https://www.contributor-covenant.org/

Overall, the code of content should hit on the following points:

Beginners are welcome
This is a safe place to share ideas, comments, code, etc.

I'ld like to work on this.

Done! And thank you very much.


Home Assistant Integration

Describe the solution you'd like:
Great work!
Have you considered making a Home Assistant Integration?

Thank you! At this time, I don't plan to create a Home Assistant integration.


docs: Add hz cli notes on using Windows

What type of PR is this?
docs: Add some notes for hz cli toolkit on using Windows environment.

What this PR does / why we need it (en: English/zh: Chinese):

en: I found some problems when using the hz tool; they are not bugs but some subtle environment-related details that anyone doing the same thing as me would face. So I added some notes to it.
zh:
Which issue(s) this PR fixes:

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

cc@FGYFFFF @justlorain

LGTM~


Add build configurations for Gradle Build Scans

This PR adds build configurations to enable Gradle Build Scans.

Manually merged https://github.com/retz/retz/commit/7f693178c5e9fe46eb820cfd46ec5f3caa0a2a57 .


Guessing gets laggy - maybe debounce syncing...? Not sure of cause

Can't replicate at the moment - closing for now; get more detail if it happens again


add svc flag for exec command.

add svc flag for exec command.

Can you please add a test for this case

unit test created


upgrade: add ignoring resource for modified flag from fleet-agent

related with https://github.com/harvester/harvester-installer/pull/345
original issue: https://github.com/harvester/harvester/issues/2762

The patch to managed chart works. We should also change the state from modified to ready here.
https://github.com/harvester/harvester/blob/75876deec220274d95041f1646ca83946d47d18f/package/upgrade/upgrade_manifests.sh#L365

The patch to managed chart works. We should also change the state from modified to ready here.
https://github.com/harvester/harvester/blob/75876deec220274d95041f1646ca83946d47d18f/package/upgrade/upgrade_manifests.sh#L365

updated

hi @w13915984028, could you help to review this PR?  Thanks!


Error compiling

Hi...there are some errors in pololu-led-strip-arduino while compiling.Any updated library or am I missing some part?

This repository contains the latest version of the library.  You should double and triple check that you followed the installation instructions in the README.

If you continue to have trouble, please give a detailed description of your setup and all the steps you took to reproduce the error, and include the full output from the compiler.

Hi David, problem solved. I copied the last folder of PoloLEDStrip and take it out after library as below:
libraries>PololuLedStrip.
Thanks for your fast reply and concerned.


TdLib .NetCore crash after a while

Hello, i'm using tdlib 1.6.0 in Windows .Net Core, with the lib https://github.com/egramtel/tdsharp to wrap the tdjson into object.
Sorry in advance, i have no logs the bug is not easy to reproduce, i've a customer who can reproduce.
This bug can be reproduced easier if you have a lot of Telegram channel and you receive a lot of message during the day, then after a while the lib just crash.
Maybe a buffer who is full or anything else ?
I've tried to build the 1.5.0 it's worst the app crash faster.
That seems to be like this bug:
https://github.com/tdlib/td/issues/917
but i've tried to build the master yesterday and it's the same case.
Before to use the 1.6.0 in .NetCore i've used the Windows C++ lib, i've no crash with this one but the method to get all chats take a lot of time (5-10 minuts), and with the .NetCore it's really faster.

@jdufaud TDLib 1.6.0 is used by millions bots and millions real users in Telegram X with 0 known ways to crash it. Some of the bots has extremely big load, so this can't be a reason by self.
The mentioned issue could really crash the app often, but it existed only for a few commits. It would be really helpful if you can collect TDLib logs before the crash with default verbosity level. If you can connect to the сrashed app via debugger and collect stacktraces, this would be even more helpful.

I will give you logs as soon as possible

After building TDLib again with the 1.6.0 tags on Git, the library no longer seems to crash. Therefore we can close this issue.


Bug in latest version? 2.16.1

System Info
Using latest @xenova/transformers version 2.16.1, downloaded from npm
using ts-node to just run a sample file, ts-node version is v10.9.2,
module and target in tsconfig.json is esnext
Environment/Platform

[ ] Website/web-app
[ ] Browser extension
[X] Server-side (e.g., Node.js, Deno, Bun)
[ ] Desktop app (e.g., Electron)
[ ] Other (e.g., VSCode extension)

Description
import { Pipeline, PreTrainedModel } from "@xenova/transformers";code where error occurs:
const newModel = await PreTrainedModel.from_pretrained(pretrainedModelName)
const pipeline = new Pipeline({
task: "embeddings",
model: newModel,
});
Looks like pipelines.d.ts Pipeline class does not have _call method in it.
This is code that comes up in my node_modules:
export class Pipeline extends Pipeline_base {
/**
* Create a new Pipeline.
* @param {Object} options An object containing the following properties:
* @param {string} [options.task] The task of the pipeline. Useful for specifying subtasks.
* @param {PreTrainedModel} [options.model] The model used by the pipeline.
* @param {PreTrainedTokenizer} [options.tokenizer=null] The tokenizer used by the pipeline (if any).
* @param {Processor} [options.processor=null] The processor used by the pipeline (if any).
*/
constructor({ task, model, tokenizer, processor }: {
task?: string;
model?: PreTrainedModel;
tokenizer?: PreTrainedTokenizer;
processor?: Processor;
});
task: string;
model: PreTrainedModel;
tokenizer: PreTrainedTokenizer;
processor: Processor;
dispose(): Promise;
}
Error:
➜  dumper git:(new-flow) ✗ node --loader ts-node/esm src/github/github.sample.ts
(node:78794) ExperimentalWarning: --experimental-loader may be removed in the future; instead use register():
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
(Use node --trace-warnings ... to show where the warning was created)
Model type for 'undefined' not found, assuming encoder-only architecture. Please report this at https://github.com/xenova/transformers.js/issues/new/choose.
1
pipeline: [Function: closure] Pipeline {
task: 'embeddings',
model: undefined,
tokenizer: null,
processor: null
}
2
Error: Must implement _call method in subclass
at Function._call (file:///Users/kateyeh/DeepUnit/mono/mono/dumper/node_modules/@xenova/transformers/src/utils/core.js:75:15)
at closure (file:///Users/kateyeh/DeepUnit/mono/mono/dumper/node_modules/@xenova/transformers/src/utils/core.js:62:28)
at UsePinecone.embedStuff (file:///Users/kateyeh/DeepUnit/mono/mono/dumper/src/github/github.sample.ts:36:43)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async main (file:///Users/kateyeh/DeepUnit/mono/mono/dumper/src/github/github.sample.ts:200:26)
Reproduction
import { Pipeline, PreTrainedModel } from "@xenova/transformers";
public async embedStuff() {
const newModel = await PreTrainedModel.from_pretrained(pretrainedModelName)
const query = 'generateTest(testDescription: TestDescription, request?: Request, skipGeneratingCode: boolean = false)'
const pipeline = new Pipeline({
task: "embeddings",
model: newModel,
});
const result = pipeline && (await pipeline(query));
return {
id:'test-id-1234',
metadata: {
query: query,
},
values: Array.from(result.data)
}
}

Your usage appears to be incorrect. Can you instead use the pipeline API to create your pipeline? Example code:
import { pipeline } from '@xenova/transformers';

// Create a feature-extraction pipeline
const extractor = await pipeline('feature-extraction', 'Xenova/gte-small');

// Compute sentence embeddings
const sentences = ['That is a happy person', 'That is a very happy person'];
const output = await extractor(sentences, { pooling: 'mean', normalize: true });
console.log(output);
// Tensor {
//   dims: [ 2, 384 ],
//   type: 'float32',
//   data: Float32Array(768) [ -0.053555335849523544, 0.00843878649175167, ... ],
//   size: 768
// }

// Compute cosine similarity
import { cos_sim } from '@xenova/transformers';
console.log(cos_sim(output[0].data, output[1].data))
// 0.9798319649182318

Additionally, I'm not sure where your code is adapted from (as it is quite non-standard) 😅 Please feel free to share!

Thank you! Honestly, a little embarrassed but was working on this late along with Pinecone and think I just swapped the lower-case p of pipeline with upper case from that and then followed the errors trail to where I was above.

No worries! 🤗 Happy to help :)

Thanks Josh❤😅


dbm-generate-gorm-changelog does not automatically create indexs

So if i have specified indexes in my gorm mappings as explained here
And generate dbm-generate-gorm-changelog - it does not automatically create indexes.

duplicate of #74 ?

Duplicate


IGC9 AWS workshop instructions and user feedback form

Basic workshop information
Time: Thursday (05/09), 3:00-5:00 pm
Location:  Maxwell-Dworkin G115
Requirement: Bring a laptop with internet connection. To connect to WIFI, follow Connect to Harvard Wireless as a guest, "Connecting to Harvard wireless as a visitor" (second section).
Free temporary AWS accounts will be provided during the workshop. We have 30+ registered participants right now and can accommodate at most 40 people.
Optional preparations
Here are the preparations you can do before the workshop. You don't have to do any of those before coming, and can instead do those during the workshop. But those steps can help you get most out of the workshop (so you can spend less time waiting for software installations, etc.)

Sign-up for a GitHub account at https://github.com/join. You will need such an account to provide workshop feedbacks (detailed later). You can further use the account to ask questions and report bugs about GEOSChem-on-cloud, on the GitHub issue tracker. Treat it as an online forum. GitHub is also the currently recommended way to submit your code updates, so it is nice to have an account, anyway. Finally, consider giving a star to the repositories under the GEOS-Chem team. Just click on the "star" button on the upper-right corner of each repository page. This "shows appreciation to the repository maintainer for their work".

Study our Python tutorial at https://github.com/geoschem/GEOSChem-python-tutorial, if you have no Python experience before. The workshop will involve a little bit of Python. But it is also fine to come without prior knowledge.

For Windows users, install Git-Bash as a Linux-like terminal. This is mentioned in more detail in our online guide:

On Windows, I highly recommend installing Git-BASH to emulate a Linux terminal, so you can follow exactly the same steps as on Mac/Linux. Simply accept all default options during installation, as the goal here is just to use Bash, not Git. Alternatively, you can use MobaXterm, Putty, Linux Subsystem or PowerShell with OpenSSH. But the Git-BASH solution should be the most painless and will also work smoothly in later steps where we add port-forwarding options to connect to Jupyter.

Tutorial contents used for the workshop
You will follow the comprehensive online tutorials at http://cloud.geos-chem.org. Due to time constraints, the workshop will only cover two essential parts:

Part 1: Working with EC2. Follow the Quick start guide. You will launch your own server on AWS, run a demo GEOS-Chem simulation, and plot output data in Jupyter notebooks.

Special instructions for Part 1: Different from the standard tutorial, in this workshop you will use the free temporary AWS account instead of signing up for your own account; you will terminate the server at the end of this workshop (after finishing both Part 1 and 2), not at the end of Part 1.

Part 2: Working with S3. Follow Configuring AWSCLI and retrieving data from S3. You will upload your own files to S3 for persistent storage, retrieve GEOS-Chem input data and other public Earth science dataset from S3, and change GEOS-Chem configurations to read the new input data.

Special instructions for Part 2: When obtaining the AWS CLI credentials, follow the " IAM user account" subsection, not the "root account" subsection.

The slides used for Thursday morning's model clinic are also available here, as a summary for the online tutorial.
Reply your feedbacks here!
You will reply to this survey by simply posting comments within this GitHub issue (i.e. the current page you are looking at). See the "comment" cell at the bottom of this page, with a big, green "comment" button (need to login to GitHub first).

Background: Your university name and how long have you been using GEOS-Chem.
Time to finish the EC2 part (Part 1). You may do a rigorous timing, but just a rough number is good enough, such as 30 minutes or 60 minutes.
Time to finish the S3 part (Part 2). Again a rough number is good enough.
General comments, if any. (e.g. unclear documentations, confusing web console)
Are you planning to use cloud computing for your research? If not, what's your concern (e.g. cost, funding, docs, learning curve, already have compute resources, etc)?

To get a feeling of how the replies would look like, see out past survey at #15. All replies under this issue should adhere to the above user-feedback format. For general discussions on workshop plans, please comment under #23.

Here's a sample reply:
Background: XX University, X years of GEOS-Chem experience
Time to finish the EC2 part: X minutes
Time to finish the S3 part: X minutes
General comments: None
Whether to use cloud computing for research: Yes/No/not-sure

Background: SUNY-Albany, 2 years of GEOS-Chem experience
Time to finish the EC2 part: 20 minutes
Time to finish the S3 part: 30 minutes
General comments: Clear documentation makes this easy to use.
Whether to use cloud computing for research: Yes

Background: MIT, 2 months of GEOS-Chem experience
Time to finish the EC2 part: 15 minutes
Time to finish the S3 part: 25 minutes
General comments: Clear instruction step by step.
Whether to use cloud computing for research: Yes

Background: Dal, 2 years of GEOS-Chem experience
Time to finish the EC2 part: 20 minutes
Time to finish the S3 part: 30 minutes
General comments: Clear documentation.
Whether to use cloud computing for research: not  sure

Background: Harvard, no GEOS-Chem experience
Time to finish the EC2 part: 25 minutes
Time to finish the S3 part: 20 minutes
General comments: None.
Whether to use cloud computing for research: not sure

Background: U. Minnesota, 6 years of GEOS-Chem experience
Time to finish the EC2 part: 20 minutes
Time to finish the S3 part: n/a
General comments: None
Whether to use cloud computing for research: not-sure

Background: 9 years of GEOS-Chem experience (U. Washington PhD now at Ramboll)
Time to finish the EC2 part: 30 minutes
Time to finish the S3 part: N/A
General comments: Great workshop! Well done!
Whether to use cloud computing for research: Definitely

Background: U of Birmingham (UK), 0.5 years of GEOS-Chem experience
Time to finish the EC2 part: 20 minutes
Time to finish the S3 part: 30 minutes
General comments: 1> Great step-by-step tutorial! I will surely recommend this to other students.
2> GC on AWS is really cool and easy to use!
Whether to use cloud computing for research: not-sure (funding is key)

We can close out this issue, as it is more than 2 years old.


Pyright job is flaky and temporarily optional

Presumably due to some hosting changes, nodeenv and by extension Pyright are regularly failing  now.
I've marked it as optional for now, but would like to re-activate it ASAP.
Ref https://github.com/ekalinin/nodeenv/issues/324

Instead of commenting out the job dependency, you can use an action input to mark when it's okay for a job to fail FYI

If you wanna open a PR, feel free. For me that was easier than reading docs. ..🤪


document doc release process

The CI auto-generates adoc output, it can be seen here: https://github.com/dfinity/motoko-base/tree/doc-pages
Yes, the playbook fetches the doc from the auto-generated branch, the PR is here: https://github.com/dfinity/dfinity-docs-playbook/pull/38
I update the README to make it clear.

The CI auto-generates adoc output, it can be seen here: https://github.com/dfinity/motoko-base/tree/doc-pages
Yes, the playbook fetches the doc from the auto-generated branch, the PR is here: https://github.com/dfinity/dfinity-docs-playbook/pull/38
I update the README to make it clear.


Bug fix for Java Functional Test - Using timestamp to retry

I've updated the logic @sachinma @bishal-pdMSFT


possible inconsistency with org.jsoup.nodes.Element.text()?

String tmp = "

";
doc = Jsoup.parse(tmp);
if(doc.select("h1").get(0).text().isEmpty()) {
	doc.select("h1").get(0).text("Heading1");
}
System.out.println(doc.html());

prints
`

Heading1

`
However I would have expected that the child element with the i tag gets not removed when setting new text as text() returned an empty String.
Is this intended? I have to use "prepend()" instead of "text()" to avoid this pitfall.
Will #564 be a solution for this?

Yes, this is intended. Per the doc:
Set the text of this element. Any existing contents (text or elements) will be cleared

You can use appendText / prependText if you want to preserve the child nodes.


Add role mention option for subscriptions module

Allow for mentioning roles when a new post is added.

+1


Specify minimum node version in engines field

Closes #192
We use Node 12.10.0 as the minimum version now, as that is required by<EMAIL_ADDRESS>

Additionally, we could specify the minimum npm version in the root package.json, see https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines


Allow the allowFontScaling property to be turned off for the Text controls

It would be helpful to be able to turn off the allowFontScaling property for each of the Text controls in this library.

Should work in v2.2.0 that was just published