how to change sign enocode

I was going to sign Iso-8859-1 encoded xml file using xml-crypto.
but I have gotten an problem. Because when i sign a document, it changed encoding utf-8 and then sign.
Because crypto.create() default encoding is utf-8. I checked this package. and it always given a default encoding value.
Is there any solution for this problem? or do i need to hack package?

Ansewer is very simple, will not use this package.

How did you solve this? How are you doing the signatures then? I need help please.

@IT222222 , we're more than welcome to take a PR to address this. @marahe-app , you're unlikely to get much community help if you only post to this thread, which is already closed.


Add Trust Boundaries to DFD Stencil

We've had suggestions from multiple teams to bring back trust boundaries to Gram.

A way to show e.g. same machine,. same network.
Mimic threats/controls on multiple components

A basic implementation would be to add a new rectangular component that can be resized and labeled.

Mockup of the design:


[hotfix][doc] add single quotes to csv ddl property

What is the purpose of the change
add single quotes to csv ddl property
Brief change log
add single quotes to csv ddl property
Verifying this change
n/a
Does this pull request potentially affect one of the following parts:
n/a
Documentation
n/a

@wuchong @JingsongLi


Missing checkout commit feature

Hi there.
I updated to the current version 1.109.0. In this version I am missing the feature "Checkout commit" as advanced options for an online repository.

Is this feature not supported anymore?
I couldn't find any hints in release notes that it has been removed.
Thank you for your support.

its hidden under the repo settings

@larshp ahh, thank you very much.
Its quite hidden :).


Fix invalide hcl file name & optimize tf init time

What type of PR is this?

/kind bug
What this PR does / why we need it:
The original hcl lock file name is wrong, and I rename it to the right one

Special notes for your reviewer:
Does this PR introduce a user-facing change?

None

Additional documentation e.g., design docs, usage docs, etc.:

None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 21 (47.62%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.009%) to 72.356%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/engine/runtime/terraform/terraform_runtime.go
1
2
50.0%

pkg/engine/runtime/terraform/tfops/workspace.go
9
19
47.37%

Totals

Change from base Build<PHONE_NUMBER>:
-0.009%

Covered Lines:
4680

Relevant Lines:
6468

💛  - Coveralls

https://github.com/KusionStack/kusion/issues/266


Update Hosts

Update hosts for Twitter Image and a set of googlevideo server.
Sort a part of address to facilitate inserting.

Thanks for the work, there are some duplicated lines, such as 3640 of 08_googlevideo.txt, these must be involved a long time ago by accident, would you like to resolve those too?

Duplicated lines deleted in af228a2e368ca8d7a93fd5d891478dce952e4580.


add LDAP authentication support.

add sbt dependencies for LDAP.
add LDAPAuthenticatior and test.
add LdapLoginController and sub login page view.
add LDAP ENV and fix message, config.
fix README about LDAP settings.

@kencharos
Thanks for your great work.
Does this PR suport LDAPS and StartTLS?

@roundrop  No, LAPDS and TLS doesn't support now.
But I'm planning to support them after.
Shall I include TSL support in this PR? or, Shall I send new PR after this PR merged?

@kencharos Sorry for my late response.
I'll try it later.
Thanks!

Merged, thanks!


Update UG to include screenshots

Update UG to include screenshots for undo and redo command
closes #101

LGTM.


Icon Cache

Write Icons to our cache instead of
fetching them each time we resume

Please put permissions stuff in its own change.  Also, please make the commit message imperative.  e.g., "Cache icons in PhysicalWebCollection"


[*TV＠FREE#] USA Rugby v Portugal Live S.TREAMS 09.11.2024

Here's why you should watch USA Rugby vs. Portugal Rugby in their 2024 November Tour of international games, streaming live on FloRugby on Saturday, Nov 9.
To kick off their 2024 November Tour of international rugby, the USA Men's Eagles once again are streaming live on FloRugby in their contest against Portugal Rugby at 11 a.m. ET on Saturday, Nov. 9.
We've talked with FloRugby expert Philip Bendon to put together a few great reasons why you should tune in to watch the Eagles rep the red, white and blue on the rugby pitch.
This is the third time in as many years that the USA has competed against Portugal, the last two editions resulting in a tie and loss for the Eagles. 10 of the 23 rostered last summer will play this Saturday in the rematch, with the same balance expected from Portugal.
How To Watch USA Rugby Vs. Portugal Rugby
USA Rugby will head to Estádio Municipal Cidade de Coimbra to take on Portugal in their first European tour test. Here's how to watch the game live.
USA Rugby will be participating in a series of Autumn tests, touring Europe to play matches against Portugal, Spain and Tonga. The former two games, Portugal and Spain, will be broadcast on FloRugby.First up is Portugal, as the Eagles visit Estádio Municipal Cidade de Coimbra in Coimbra, Portugal.
The Lobos, currently ranked No. 15 in the World Rugby Rankings, last played a test in July against South Africa, losing 64-21

dsgffv


Multi-statement queries causes wrong result interpretation

Executing a multi-statement raw sql query towards PostgreSQL, doesn't seem to be supported currently.  For example:
const result = await sql.raw(`
    BEGIN;

    DO $$
    BEGIN
      PERFORM "hello_world"();
    END $$;

    SELECT current_user;

    COMMIT;
  `)
  .execute(client);

The issue seems to be that the executeQuery inside the postgres-driver always expects an object return type from the this.#client.query, when in fact, it could be either an object, or a list of objects. This causes the return evaluation to swallow the result by returning an empty array return { rows: result.rows ?? []}; .
This behavior is documented here  inside the pg package, but unfortunately, the ts type signature for pg, seems to get this wrong as well.
I'm unsure about which type of solution you would prefer moving forward - and which implication it might have. Currently, I'm patching this package with Array.isArray check of the result, but this might not be doable as a whole.

Unfortunately we can't support this. We'd need to change the output for every query since we can't detect compile-time if the query would return an array or multiple arrays. Adding a separate method is not an option either since we'd need to modify the driver interface, which is used by all third party dialects.

Would expanding QueryResult  type be an option? Exposing the raw response from the pg client inside the QueryResult payload.
This comment  The rows returned by the query. This is always defined and is empty if the query returned no rows. for the rows property is misleading, because the response from pg actually have rows.

Alternatively, exposing an optional selector function, would give the developer an option to pick the correct Result response inside the list. For the query defined above, the Result response would look something like this
Result {
    command: 'BEGIN',
    rowCount: null,
    oid: null,
    rows: [],
    fields: [],
    _parsers: undefined,
    _types: TypeOverrides { _types: [Object], text: {}, binary: {} },
    RowCtor: null,
    rowAsArray: false,
    _prebuiltEmptyResultObject: null
  },
  Result {
    command: 'DO',
    rowCount: null,
    oid: null,
    rows: [],
    fields: [],
    _parsers: undefined,
    _types: undefined,
    RowCtor: null,
    rowAsArray: false,
    _prebuiltEmptyResultObject: null
  },
  Result {
    command: 'SELECT',
    rowCount: 1,
    oid: null,
    rows: [ [Object] ],
    fields: [ [Field] ],
    _parsers: [ [Function: noParse] ],
    _types: undefined,
    RowCtor: null,
    rowAsArray: false,
    _prebuiltEmptyResultObject: { current_user: null }
  },
  Result {
    command: 'COMMIT',
    rowCount: null,
    oid: null,
    rows: [],
    fields: [],
    _parsers: undefined,
    _types: undefined,
    RowCtor: null,
    rowAsArray: false,
    _prebuiltEmptyResultObject: null
  }


Used exposed admin proto IDLs

What changed?
Used exposed admin proto IDLs

Why?
Admin proto IDLs were moved to cadence-idl repo (https://github.com/uber/cadence-idl/pull/107)

How did you test it?
Tested by building new local CLI tool and interacting with prod cadence server.

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01815bf8-4d43-432c-9356-7033a5cc9117

0 of 14 (0.0%)  changed or added relevant lines in 2 files are covered.
107 unchanged lines in 15 files lost coverage.
Overall coverage decreased (-0.06%) to 57.973%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/frontend/adminGrpcHandler.go
0
2
0.0%

common/types/mapper/proto/admin.go
0
12
0.0%

Files with Coverage Reduction
New Missed Lines
%

client/history/client.go
2
38.05%

client/history/metricClient.go
2
45.3%

common/cache/lru.go
2
92.2%

common/membership/hashring.go
2
83.54%

common/task/fifoTaskScheduler.go
2
85.57%

common/task/weightedRoundRobinTaskScheduler.go
2
89.12%

service/history/handler.go
2
47.6%

common/persistence/serialization/parser.go
4
65.41%

common/persistence/serialization/thrift_decoder.go
4
61.22%

service/frontend/workflowHandler.go
4
60.28%

Totals

Change from base Build 01814fb2-7f09-4e94-9c6b-ff3fc6b5912f:
-0.06%

Covered Lines:
83955

Relevant Lines:
144817

💛  - Coveralls


Digest Auth in API Authentication

Is there an existing issue for this?

[X] I have searched the existing issues

Summary

Why should this be worked on?
Hi, we need the Digest auth (Authentication Type)
https://en.wikipedia.org/wiki/Digest_access_authentication
to connect to a Rest Api (german Warehouse Management System)

@mabeuck thank you for the feature request!

created a ticket on Jira- https://zemoso.atlassian.net/browse/TNOSB-355


How to left justify first images and right justify last images while using center mode

Hi All,
I'm using slick slider 1.6.0 with AngularJS. I using center-mode in sync version of the slider. But in center mode, I don't want first and last images in thumbnail tray to be center aligned because it leaves unnecessary space to the left and right side of thumbnail tray. Instead, they should be left justified and right justified. Is there any way or hack to achieve this?

I would set centerPadding to zero and pad the slide as needed. Tricky but doable. Good luck.
Closing: Support request.

Hi @leggomuhgreggo we tried to do it, but could not reach up to the point what we want. We have multiple sliders on the same page. And finding this really difficult to do. Will you please some code for same. It would not be appropriate to mess with slick.js.


PP-6994 Add refund POJO model

Following the same ChargeEntity -> Charge POJO pattern, add a POJO
to represent refunds. These will be buildable from Connector database
entities and historic transactions if the database entities have been
expunged.

This commit was included in and superseded by https://github.com/alphagov/pay-connector/pull/2549


Replacing Existing Node with Next.js Fails to Pass Attributes

What happened?
Following the docs on nodes and next js nodes is confusing.
Goal: replace the default heading node as the nodes doc demonstrates.
Following the examples in the nodes seems to lead to either the render function being called with no props other than children, or only the transform step being called and not the render step.
Suggestion
Provide more details on the way the nextjs integration interacts with the described transform and render steps, and provide more complete examples for nextjs.
To reproduce

Create a markdoc file with a h1, h2, h3.
Try this basic example (as implied by the combination of nextjs and non-nextjs docs)

import { Title } from '../title';
import { Tag } from '@markdoc/markdoc';

const TitleWrapper = ({ level, id, children }) => {
    console.log('Wrapper called')
    return (
        <Title level={level} id={id}>{children}</Title>
    )
}

export const heading = {
    render: TitleWrapper,
    children: ['inline'],
    attibutes: {
        id: { type: String },
        level: {type: Number, required: true, default: 1}
    }
}

This does render the component however it is never passed any value for level other than the default.

Attempt #2 Try the following

import { Title } from '../title';
import { Tag } from '@markdoc/markdoc';

const TitleWrapper = ({ level, id, children }) => {
    console.log('wrapper')
    const order = Math.min((level || 1) +1, 6) as TitleOrder;
    return (

        <Title order={order} id={id}>{children}</Title>
    )
}

function generateID(children, attributes) {
 //... skipped for brevity as not relevant
}

export const heading = {
    render: TitleWrapper,
    children: ['inline'],
    attibutes: {
        id: { type: String },
        level: {type: Number, required: true, default: 1}
    },
    transform(node, config) {
        const attributes = node.transformAttributes(config);
        const children = node.transformChildren(config);

        const id = generateID(children, attributes);

        return new Tag(
        `h${node.attributes['level']}`,
        { ...attributes, id },
        children
        );
  }
}

This does allow for multi-level headings however the render function is never called (no log lines printed or component rendered).
Version
@markdoc/markdoc":  0.1.2,  @markdoc/next.js:  0.1.4
Additional context
No response

I also discovered that the node.transformAttributes call seems to be swallowing the level property - I suspect this is a bug (and perhaps why I do require a transform function at all in this case!) but I don't know enough about Markdoc's API to say for certain what's happening.

@arranf the level property should not be being swallowed… it is working for us here: https://github.com/markdoc/docs/blob/main/markdoc/nodes/heading.markdoc.js#L25
Can you share a reproduction of this?

It appears the solution is to map to the render function via the component name which appears to need to be in PascalCase for React components and lowercase for native HTML components

More context on this answer here: #64
If you want to use a custom React component, we recommend creating a Heading component which accepts a level prop, as seen in this discussion. Which then requires returning new Tag('Heading' ...).
However, if you just want to transform your headings (to, for example, always have an ID), then you can use the new Tag(h${node.attributes['level']} ...) pattern.
This is demonstrative of the fact that in React, Heading and h1, h2, etc, are different components. So you have to set the correct component new in your new Tag(...).

To confirm my understanding can you please answer the following?

Assuming I'm using nextjs, for every node will I need a transform function?
If that's true, conceptually does the render property just exist to "register" a mapping between the string "Header" and the Header component?

I think my source of confusion was twofold:

The nextjs docs describe nodes being just like tags - where there is no transform function (I got a little mislead there!)
Not quite understanding the casing needs of the html vs react components (which are documented, I just didn't realise those steps applied in the Nextjs world!

I also discovered that the node.transformAttributes call seems to be swallowing the level property - I suspect this is a bug (and perhaps why I do require a transform function at all in this case!) but I don't know enough about Markdoc's API to say for certain what's happening.

@arranf the level property should not be being swallowed… it is working for us here: https://github.com/markdoc/docs/blob/main/markdoc/nodes/heading.markdoc.js#L25
Can you share a reproduction of this?

I'll go ahead and create one.

I also discovered that the node.transformAttributes call seems to be swallowing the level property - I suspect this is a bug (and perhaps why I do require a transform function at all in this case!) but I don't know enough about Markdoc's API to say for certain what's happening.

@arranf the level property should not be being swallowed… it is working for us here: https://github.com/markdoc/docs/blob/main/markdoc/nodes/heading.markdoc.js#L25
Can you share a reproduction of this?

Repro is here: https://github.com/arranf/markdoc-nextjs-repro

Repro is here: https://github.com/arranf/markdoc-nextjs-repro

@arranf you just have a typo, attibutes -> attributes 🙂


Cannot change tab bar icon color, tab bar background color

Yeap, if you could fix it

Not a fix, but I got a  temporary solution
Open Pod file -> Pods -> CBFlashyTabBarController -> CBTabBarButton.swift
In this file at line 64,65,66 set your desired colour.


Saving a relationship-model doesn't actually trigger the API call

Let's say I have a Post model with an author relationship and I want to create an ember-changeset for the author only, I would do this on the controller/component:
authorChangeset: computed('post', function () {
  let author = this.get('post.author');
  return new Changeset(author);
})

but when I try to persist the author, calling save on the changeset doesn't trigger the API call.
looking at the source code I think I found the issue:
https://github.com/DockYard/ember-changeset/blob/master/addon/index.js#L192
if (typeOf(content.save) === 'function') {
  savePromise = content.save(options);
}

I noticed that post.save is a function, but author.save is undefined. but author.get('save') would actually work. so because it's undefined, the savePromise remains resolve(this) and does nothing.
so my question would be, is there a reason why not to change it to:
if (typeOf(get(content, "save")) === 'function') {
(or is this not supposed to work anyways? bad pattern?)

update 1: actually might be a duplicate of #127 - but that's already fixed/closed and I'm on 1.3.0, so I shouldn't have that issue. (anyways, when creating the changeset the relationship is already resolved)

authorChangeset: computed('post.author', function () {
  let author = this.get('post.author.content');
  return new Changeset(author);
})

actually it works when using .content for the changeset, is that the recommended way?

@roberkules I am running into this as well.
If we have a non-blocking model hook, calling cave on the changeset will not call the persistence methods on the adapter.
If you look at this twiddle: https://ember-twiddle.com/d4c526f3ad2782e785b8685a4e759543

I'm experiencing this too. I guess this was never resolved?

@mhluska What version of ember-changeset are you on?
FYI - sometime in October I plan on tackling some larger issues here and hopefully resolve the issue of getting at things via content.

@snewcomer ember-changeset 1.5.0-beta.0 and ember-changeset-validations 1.2.11

@roberkules @mhluska Ok I think I solved this here (note this is targeting 2.0-beta branch).

We now unwrap the relationship and call save!  3.6.1
https://github.com/validated-changeset/validated-changeset/pull/71


Improve Dark Mode UI of the new Landing Page

Landing Page Team under GSoD'21 @ created the new landing page.
But I feel that the Dark mode UI of that page needs some improvement.
Currently, the UI looks like this:
Some text is not visible as you can see.

What I suggest is to merge the remaining PRs of the Landing Page first, so that the team can work on this issue as a whole.

@Rohitesh-Kumar-Jain There will be following PR once we merged all the 8 PRs and that final PR will consist changes in the index file as well as docusaurus.config in which the dark mode option will be removed. According to the docusaurus documentation if we change the default landing page provided by the docusaurus the dark mode won't be applied so we won't be able to use the dark mode and we need to work in that part as we created the landing page. So as of now there will be another PR for merging all the components in the index file and it will also remove the dark mode toggle option. If you have anymore question let me know. Thank you.

As you can see in the PR preview photos that we attached for all the section PRs you cannot see the dark mode toggle option.

Can't we improve the dark mode UI, instead of removing that 🤔
Ik that will be some work, but If possible add the dark UI as well.
Writing all this work on your resume will add stars to your profile, and will give you something more to speak in interviews about your projects ⭐

@encodeArnab and @sajenjeshan1222 you have removed Dark UI from the whole of the Wechaty, and that's not acceptable.
What I am talking about is that earlier we had a feature for the dark mode for documentation, consider ss on. #1098 and #1126.
What's the point of adding a feature on the cost of removing an exiting one 🤔
Kindly at least restore the dark UI for the rest of the Wechaty, if you don't wish to create the dark theme for the landing page itself.

As you can see in the PR preview photos that we attached for all the section PRs you cannot see the dark mode toggle option.

I was revisiting the prototype that you submitted, and that clearly had the dark mode toggle option...
https://www.figma.com/proto/L5MS8HqF0g5hbHdkgqUH1o/wechaty-landing-page?node-id=143%3A0&scaling=min-zoom&page-id=0%3A1

The new dark mode seems good, not sure the original dark mode had this theme, but this new theme looks good to me.


Asp.net Core 2.0 Window Authentication Cors HttP Post method Issues

Hi team,
when i am working with asp.net core 2.0 My HttpPost method not working  with windows authentication.It is Stopping Prelift Calls

@bharathpbk can you share more information about what you are doing? If you can share your app on GitHub that would be great.

Hi, we are planning to work on a sample of how to do CORS + WIndows Auth, which you can track here: https://github.com/aspnet/AuthSamples/issues/15
Unfortunately we don't have any specific guidance on this at this time. Consider asking on another site such as StackOverflow to get further assistance on this sooner.


Scheduling messages

In Akka, there is the ActorSystem.Scheduler
In Proto.Actor, I would rather like to see some Scheduler interface, where we can provide different kinds of implementations.
e.g. in mem, cron job based etc.
Users can then either inject the scheduler they want into their actors, or, just have a package wide instance of whatever scheduler they want to use.
If we do this as part of the Proto.Actor library, I would like to see this as a separate package to keep the API surface as minimal as possible in the core actor package.

I wrote a Scheduler interface for protoactor-go which is quite similar to the AbstractScheduler interface in Akka. I am curious what your thoughts are on a "cron job-based" scheduler. I know how cron works but I am not seeing how the interface (with methods like schedule and scheduleOnce) works with a cron table. Can you point me to an Akka example?

In .NET we decided to go for a more opt-in model:
https://github.com/AsynkronIT/protoactor-dotnet/tree/dev/src/Schedulers/Proto.Scheduler.SimpleScheduler
It is an external package which can be evolved separately and do not require any internal changes to the core framework.

what about the go part? IS there a scheduler?


drivers: spi_mcux_lpspi: spurious irq interrupt

Describe the bug
The spi_mcux_lpspi.c spi_transceive implementation sometimes fails.
This is due to a spurious interrupt in LPSPI_MasterTransferHandleIRQ.
The issue arises if the SPI clock speed is high and there are other interrupts occurring.
I have found a work around but not a solution:
static void spi_mcux_isr(const struct device *dev)
...
	if (data->handle.state == (uint8_t)kLPSPI_Idle) {
		return;
	}

	LPSPI_MasterTransferHandleIRQ(base, &data->handle);
}

To Reproduce
Steps to reproduce the behavior:

Increase SPI clock frequency: sed -i 's|6400000>|30000000>|g' zephyr/samples/drivers/led_ws2812/boards/mimxrt1050_evk.overlay
Add assert(handle->state != (uint8_t)kLPSPI_Idle); in the top of modules/hal/nxp/mcux/mcux-sdk/drivers/lpspi/fsl_lpspi.c:LPSPI_MasterTransferHandleIRQ
Build sample: west build -p always -b mimxrt1050_evk zephyr/samples/drivers/led_ws2812/ -- -DCONFIG_SAMPLE_LED_UPDATE_DELAY=0 -DCONFIG_SHELL=y -DCONFIG_ASSERT=y
Since the issue is not consistent the error might occur by itself during boot. If not press and hold <ENTER> to stress the system.

*** Booting Zephyr OS build zephyr-v3.4.0-4642-g1084c8b083f0 ***
[00:00:00.000,000] <inf> main: Found LED strip device ws2812@0
[00:00:00.000,000] <inf> main: Displaying pattern on strip
uart:~$
uart:~$
uart:~$
uart:~$
uart:~$
uart:~$
uart:~$
uart:~$
uart:~$ assertion "handle->state != (uint8_t)kLPSPI_Idle" failed: file "WEST_TOPDIR/modules/hal/nxp/mcux/mcux-sdk/drivers/lpspi/fsl_lpspi.c", line 1566, function: LPSPI_MasterTransferHandleIRQ
abort()
[00:00:02.323,000] <err> os: r0/a1:  0x00000004  r1/a2:  0x80000ab0  r2/a3:  0x80000ab0
[00:00:02.323,000] <err> os: r3/a4:  0x800011b4 r12/ip:  0x0000ea60 r14/lr:  0x60008d31
[00:00:02.323,000] <err> os:  xpsr:  0x61000032
[00:00:02.323,000] <err> os: Faulting instruction address (r15/pc): 0x60008d3c
[00:00:02.323,000] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:02.323,000] <err> os: Fault during interrupt handling

[00:00:02.323,000] <err> os: Current thread: 0x80000ab0 (idle)
[00:00:02.370,000] <err> os: Halting system

Expected behavior
No spurious interrupt.
Impact
If thousands of spi_transceives occurs every second at some point the spurious interrupt will run while a thread is in the middle of spi_transceive resulting in e.g. an absurdly high length which will result in the accessing an invalid address at some point:
[00:04:16.814,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:26.320,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:29.384,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:29.584,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:29.784,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:29.984,000] <err> spi_mcux_lpspi: Transfer could not start
[00:06:29.995,000] <err> os: ***** BUS FAULT *****
[00:06:29.995,000] <err> os:   Precise data bus error
[00:06:29.995,000] <err> os:   BFAR Address: 0x20280000
[00:06:29.995,000] <err> os: r0/a1:  0x20280000  r1/a2:  0x00000000  r2/a3:  0x00000000
[00:06:29.995,000] <err> os: r3/a4:  0x20280000 r12/ip:  0xaaaaaaaa r14/lr:  0x6005b76f
[00:06:29.995,000] <err> os:  xpsr:  0x81000032
[00:06:29.995,000] <err> os: Faulting instruction address (r15/pc): 0x6005b6ec
[00:06:29.995,000] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:06:29.995,000] <err> os: Fault during interrupt handling

I just realized the reproduce steps requires waiting for https://github.com/zephyrproject-rtos/zephyr/pull/63275 to be merged or checking out https://github.com/jeppenodgaard/zephyr/tree/jepod/improve-led-ws2812

Hi @jeppenodgaard ,
We have not been able to replicate this issue yet, even at 64MHz SPI clock.  However, it seems you are testing this at 64MHz, and that violates the maximum LPSPI frequency of the RT1050.  From the datasheet, the maximum LPSPI frequency is 30MHz.
Can you test on your hardware at 30MHz or lower, and see if you still have these spurious interrupts?  Thanks

Hi @DerekSnell.
I have also tried with 30 MHz which also causes the issue for me:
Screencast from 10-04-2023 09:49:10 AM.webm

Hi @jeppenodgaard
I have been able to reproduce the spurious interrupt you mention. However, I do not think this is an issue, but rather an expected result of the way that the LPSPI HAL driver manages the TX FIFO. You can see in the implementation of the LPSPI_MasterTransferFillUpTxFifo function that the driver will continue to write data until the FIFO is filled:
https://github.com/zephyrproject-rtos/hal_nxp/blob/d3770a0434cd15df3f89cd7d38932395679979ee/mcux/mcux-sdk/drivers/lpspi/fsl_lpspi.c#L1504.
With a fast SPI clock, it is possible that the LPSPI will partially drain the FIFO as the core fills it. I see this happening with a SPI clock of 30MHz. In the 48 byte transfer, I see the following:

After the first call to LPSPI_MasterTransferFillUpTxFifo (from LPSPI_MasterTransferNonBlocking), 26 bytes remain to be written
After the second call to LPSPI_MasterTransferFillUpTxFifo (from LPSPI_MasterTransferHandleIRQ) 4 bytes remain to be written
After the third call to LPSPI_MasterTransferFillUpTxFifo (from LPSPI_MasterTransferHandleIRQ), 0 bytes remain to be written

At this point, the FIFO can drain rather quickly. The HAL next checks if all bytes have been written: https://github.com/zephyrproject-rtos/hal_nxp/blob/d3770a0434cd15df3f89cd7d38932395679979ee/mcux/mcux-sdk/drivers/lpspi/fsl_lpspi.c#L1743, and since they have it will check to see if the transfer has completed.
At higher clock speeds, the FIFO will have drained at this point, so we will take the conditional branch here, since the transmit complete flag will be set in the LPSPI: https://github.com/zephyrproject-rtos/hal_nxp/blob/d3770a0434cd15df3f89cd7d38932395679979ee/mcux/mcux-sdk/drivers/lpspi/fsl_lpspi.c#L1748
However, we have yet to disable the transmit data interrupt (TDIE is still set), so there will be another interrupt pending at this point
At this point, we will disable the interrupt request flag and set the module as idle, but the last "spurious interrupt" is already pending and will fire. This appears to be the critical difference at high clock speeds- the FIFO will drain before we have a chance to disable the transmit data interrupt, so one additional interrupt will fire.
However, I don't see why this would cause any issues. According to the ARMv7 architecture reference manual, exceptions should chain in this case:

On an exception return, there can be a pending exception with sufficient priority to preempt the execution being
returned to. This results in an exception entry sequence immediately after the exception return sequence. This is
referred to as chaining the exceptions.

So the next "spurious interrupt" on the LPSPI should fire before the running application can configure the SPI to transfer additional data. The LPSPI_MasterTransferHandleIRQ will handle this case, and simply not change the LPSPI configuration.
To summarize, as far as I can tell this "spurious interrupt" is expected by the HAL driver when the LPSPI is using a fast clock speed, and should not cause issues. I assume there was a fault that caused you to report this issue initially. Do you have any details on how I could reproduce that?

Hi @danieldegrasse..
Thank you for looking into this!
Unfortunately I cannot share the code that caused the fault due to licenses and custom hardware, so I am not able to share the setup that can reproduce it.
I think what happens is that because a thread is allowed to use spi_transceive before the pending interrupt has fired, the ISR might run in the middle of e.g. spi_context_buffers_setup.
I reported the issue due to this fault https://github.com/zephyrproject-rtos/zephyr/pull/62243#issuecomment-1721398086 which shows the state of struct spi_mcux_data where totalByteCount has a very high value.

I think what happens is that because a thread is allowed to use spi_transceive before the pending interrupt has fired, the ISR might run in the middle of e.g. spi_context_buffers_setup.

This should not be possible if running in the thread context- since the LPSPI interrupt will already be pending at the exit of the last call to LPSPI_MasterTransferHandleIRQ.  In that case I could see this spurious interrupt causing issues, because it would be possible to start another SPI transfer from an interrupt context

True.
The synchronous SPI API is used.
I must admit I have been trying but not been able to figure out how it happens.

I must admit I have been trying but not been able to figure out how it happens.

Could the issue be reproduced with a toy sample, that calls spi_transceive in a loop? Also, are you only transmitting data, or are you receiving it as well?

I'll try to remove the assert and see if I can reproduce the crash with the sample.
I both transmit and receive. I can share code snippets to show exactly how the SPI buffers are configured.
I get access to the source and hardware tomorrow.

Here's the snippet/implementation:
EscALEvent.Byte is a two uint8_t array.
static uint8_t spi_read_wait_byte = 0xFF;
static uint8_t spi_read_terminate_byte = 0xFF;

void HW_EscRead( MEM_ADDR *pData, UINT16 Address, UINT16 Len )
{
	uint8_t addr_cmd_buf[2];

	const struct spi_buf rx_buf[] = {
		{
			.buf = EscALEvent.Byte,
			.len = sizeof(EscALEvent),
		},
		{
			.buf = NULL,
			.len = 1,
		},
		{
			.buf = (uint8_t *)pData,
			.len = Len,
		},
	};
	const struct spi_buf_set rx_bufs = {
		.buffers = rx_buf,
		.count = ARRAY_SIZE(rx_buf)
	};

	const struct spi_buf tx_buf[] = {
		{
			.buf = addr_cmd_buf,
			.len = sizeof(addr_cmd_buf),
		},
		{
			.buf = &spi_read_wait_byte,
			.len = sizeof(spi_read_wait_byte),
		},
		{
			/* If NULL spi_mcux_lpspi writes 0x00 */
			.buf = NULL,
			.len = Len > 1 ? Len - 1 : 0,
		},
		{
			.buf = &spi_read_terminate_byte,
			.len = sizeof(spi_read_terminate_byte),
		},
	};
	const struct spi_buf_set tx_bufs = {
		.buffers = tx_buf,
		.count = ARRAY_SIZE(tx_buf)
	};

	addr_cmd_buf[0] = Address >> 5;
	addr_cmd_buf[1] = Address << 3 | ESC_RDW;

        spi_transceive(spi_dev, &spi_cfg, &tx_bufs, &rx_bufs);
}

void HW_EscWrite( MEM_ADDR *pData, UINT16 Address, UINT16 Len )
{
	uint8_t addr_cmd_buf[2];

	const struct spi_buf rx_buf[] = {
		{
			.buf = EscALEvent.Byte,
			.len = sizeof(EscALEvent),
		},
		{
			.buf = NULL,
			.len = Len,
		}
	};
	const struct spi_buf_set rx_bufs = {
		.buffers = rx_buf,
		.count = ARRAY_SIZE(rx_buf)
	};

	const struct spi_buf tx_buf[] = {
		{
			.buf = addr_cmd_buf,
			.len = sizeof(addr_cmd_buf),
		},
		{
			.buf = (uint8_t *)pData,
			.len = Len,
		},
	};
	const struct spi_buf_set tx_bufs = {
		.buffers = tx_buf,
		.count = ARRAY_SIZE(tx_buf)
	};

	addr_cmd_buf[0] = Address >> 5;
	addr_cmd_buf[1] = Address << 3 | ESC_WR;

	spi_transceive(spi_dev, &spi_cfg, &tx_bufs, &rx_bufs);
}

Hi @jeppenodgaard, thank you for providing the snippet. Is it clear which function starts the transfer that causes the crash, between HW_EscWrite and HW_EscRead?

Hi @danieldegrasse!
I have not been able to figure out if one or both functions cause the issue.

Hi @danieldegrasse.
I know you have probably been busy since v3.5 has just been release, but any news on this issue?

The issue is not resolved. The label should be removed.

The issue is not resolved. The label should be removed.

Hi @jeppenodgaard- sorry for the delay responding here. I'm not sure how I can make much more progress here without some sample app that reproduces the issue. I understand that you can't share the code itself, but could you possibly reproduce the issue with some sort of application that writes data via the LPSPI in a loop? A reproducible sample will make it easier to narrow down what could be going wrong here.

The issue has not been resolved and a workaround might be required as described in the issue description.


operators redis-operator (0.9.0)

Signed-off-by: iamabhishek-dubey<EMAIL_ADDRESS>Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[X] Are you familiar with our contribution guidelines?
[X] Have you packaged and deployed your Operator for Operator Framework?

[X] Have you considered whether you want to use semantic versioning order?
[X] Is your submission signed?
[X] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[X] Modify more than one operator
[X] Modify an Operator you don't own
[X] Rename an operator - please remove and add with a different name instead
[X] Modify any files outside the above-mentioned folders
[X] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[X] Description of the managed Application and where to find more information
[X] Features and capabilities of your Operator and how to use it
[X] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[X] Human readable name and 1-liner description about your Operator
[X] Valid category name1
[X] One of the pre-defined capability levels2
[X] Links to the maintainer, source code and documentation
[X] Example templates for all Custom Resource Definitions intended to be used
[X] A quadratic logo

Remember that you can preview your CSV here.

/merge possible

@iamabhishek-dubey the operator was unable to start https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-openshift-ecosystem_community-operators-prod/478/pull-ci-redhat-openshift-ecosystem-community-operators-prod-main-4.8-deploy-operator-on-openshift/1465270808485040128#1:build-log.txt%3A4249
You can also debug manually on k8s, I suppose the same error.

feel free to reopen when needed


Fixed issue #500

Added a way to provide the scaledSize for markers in order to fix issue #500

@apneadiving I don't know why the build failed. Might this This job ran on our legacy infrastructure. Please read our docs on how to upgrade. be an issue?

Thanks for the contribution!
Yes I didnt take time to update the travis config... :)


The type 'double' is not exhaustively matched by the switch cases since it doesn't match 'double()'

I'm not sure if this is a bug but when I switch over a double and exhaustively match all possible values (I think), Dart still forces me to add an additional case.
      final steering = switch (bearingDifference) {
        < 0 => SteeringInstruction.right,
        > 0 => SteeringInstruction.left,
        == 0 => SteeringInstruction.straight,
      };

The code above gives this compile time error:
Error: The type 'double' is not exhaustively matched by the switch cases since it doesn't match 'double()'.
Try adding a wildcard pattern or cases that match 'double()'.

Now it might be that I'm really missing a case but the error isn't very helpful here. Am I missing double.nan? (No, because "A double can't equal 'double.nan', so the condition is always 'false'.") Is it double.infinity and double.negativeInfinity? (No, those values are already covered, and adding them doesn't make a difference.) Is it -0? (No. Adding -0 doesn't make a difference.) Is it null? (No, the number is non-nullable.) A specific suggestion would be much more helpful.
Or maybe it's that Dart doesn't know (can't prove) what's missing for continuous values such as double. If that's the case, the error should note that. Something like "Switching over real numbers is not supported. You have to include a default case, even if you know it will never be matched."
Thankfully, the workaround is easy:
      final steering = switch (bearingDifference) {
        < 0 => SteeringInstruction.right,
        > 0 => SteeringInstruction.left,
        == 0 => SteeringInstruction.straight,
        _ => throw StateError(
            'Double $bearingDifference somehow '
            "doesn't belong on the number line and Dart won't tell us why. ¯\_(ツ)_/¯"),
      };

;)
Dart info
- Dart 3.5.4 (stable) (Wed Oct 16 16:18:51 2024 +0000) on "macos_arm64"
- on macos / Version 14.7 (Build 23H124)
- locale is en-US

Exhaustiveness analysis doesn't reason about the exhaustiveness of a set of double or int inequalities or any other number specific properties, it only reasons about properties that are modeled at the type level. So it knows that the immediate subtypes of a sealed type is an exhaustive set, it knows the complete set of values of any given enum, it knows about null vs. non-null, etc, but it doesn't know that < 0, > 0 and == 0 covers all values of type double.

Thanks for the clarification! In that case, I would like to see a more helpful error.
You see, modern Dart switch statements give you a lot of power, e.g. the following code gives you an exhaustiveness error which goes away when you truly cover all cases.
switch((useful, efficient)) {
  case (true, true):
    return "Oh boy!";
  case (false, true):
    return "Well, at least it's efficient.";
}

So it's not out of the question to half-expect a similar analysis on numbers. I, of course, accept that that isn't possible, or at least practical. But the compiler should give a better indication of what's going on than it doesn't match 'double()', ideally.
In other words, the quality of Dart's exhaustiveness analysis in other cases (such as records of booleans) creates an expectation with the programmer. The ensuing surprise is not helped by the error given.


feat: update angularls/init.lua

make the node_modules which in the project have the highest priority, its priority should be higher than mason

By default, the LSPS below the workspace will be preferred. If the workspace does not have LSPS, mason's will be used by default. Two cases of angular18 and 19 have been tested.


Fix aggregate-reports.yml

This looks like it came out of a spelling error test commit somewhere in a rebase. Not sure why the PR checks for the original PR didn't include js - aggregate-reports given that aggregate-reports.yml was included in the list of changes and there is a trigger condition which includes that file.
There was a run of js - aggregate-reports but it does not appear to have gone into the checks.

/azp run js - aggregate-reports

/azp run js - aggregate-reports

Closing. The compliance tools job will always fail because this PR originates from a fork. Use this PR instead -- https://github.com/Azure/azure-sdk-for-js/pull/19005


Build with clang resolves missing libasan link error

My first build was not using clang but my system's default of gcc, and linking failed on missing libasan. I get the impression that the DuckDB developers default is clang. Switching to clang resolved the linking error, and also gives fewer (only one remaining actually) warnings about type mismatches when building the codebase. (I only had to add sqlite-devel to my Fedora system.)
I think it would be good to update the README to instruct people to use clang (unless they know what they are doing). Perhaps the cmake configuration should check for libasan and sqlite-devel to be installed.

Welcome @arjenpdevries , can you give the console output. Also might be worth implementing #94 as a response.

Both GCC and Clang should work fine. Indeed, defaulting to an optimized build should solve this. Neither libasan nor sqlite-devel are required to build the core of DuckDB. Libasan is used for debugging purposes (address sanitizer) and SQLite is used only for the tests. Then if people want to debug and run the tests they can install these libraries.

Console output:
build$ cmake -DCMAKE_BUILD_TYPE=Debug --clean-first -j 4 ..
build$ make > make.log 2> make.err
[..]
/usr/bin/ld: cannot find /usr/lib64/libasan.so.5.0.0 inside /
collect2: error: ld returned 1 exit status
make[2]: *** [src/CMakeFiles/duckdb.dir/build.make:697: src/libduckdb.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:173: src/CMakeFiles/duckdb.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

Attached complete output: make.log (uninteresting) and make.err (various warnings given by gcc that could be addressed).

PS: I just reported it because it is a "first build experience" and I assumed you want that to be as accessible as possible. I understand that maybe I should have chosen Release instead of Debug and then it might not have happened :smile:. Perhaps suggesting Clang as default is not a bad idea though, especially not if that would be your own default (?).

Indeed we absolutely want it to work out of the box. However, it should succeed with any C++11 compatible compiler (and we do also run tests on both clang, gcc and msvc).
In this case it didn't fail because of the compiler, but rather because of the missing dependency (address sanitizer). I think the proper solution therefore would be to disable the address sanitizer by default (i.e. DEBUG compiles only with -O0 -g), we can then make a separate build configuration DebugWithSanitizer that also compiles with the sanitizer.
And indeed those warnings should be fixed, thanks for the list!

We now use release build by default


Logging

Okay, I'll start this off. What I've got so far is logging to a file with timestamps
[2021-04-07 21:28:25,302] Update interval: 120
[2021-04-07 21:28:25,306] Frame increment: 4
[2021-04-07 21:28:27,395] Playing 'test.mp4'
[2021-04-07 21:28:27,398] Video info: 50 frames, 23.976fps, duration: 2.073s
[2021-04-07 21:28:27,402] This video will take 25.0 minute(s) to play.
[2021-04-07 21:28:31,361] Displaying frame 0 of test.mp4 (0.0%)

and printing to the console without.
pi@pizero:~/SlowMovie $ python3 slowmovie.py
Update interval: 120
Frame increment: 4
Playing 'test.mp4'
Video info: 50 frames, 23.976fps, duration: 2.073s
This video will take 25.0 minute(s) to play.
Displaying frame 0 of test.mp4 (0.0%)

However, some messages shouldn't go to the log. Something to do with log levels? (haven't used logging module before) But anything to printed to the console still goes to the journal.
Could keep service flag and run them through an if, or output them to stderr instead and have the service ignore stdout (or vice-versa), or just set the service file to ignore all of it and forget about the journal.
Although python-systemd has a logging handler. That's might be the right way to do it.
Thoughts? Or anything else?

Could we try and use the logging level as a flag to help determine what's shown in the log vs console? We could use logging.info and logging.debug statements in the code. When the log level is set to debug you'd see everything but at default you'd only get the info statements. Similar to the `--service`` flag idea but instead of us having to code the checks just pass that stuff to the logger and let it deal with it.
As far as the individual log file vs the journal I guess I don't have a preference. I think one or the other is sufficient for a file based record and then we'd have console for when running interactively. I've seen lots of programs do it either way.

The timestamps in the log vs. no timestamps in console output is a great touch.
I like using the logging handler to implement those info and debug logging levels like rob mentioned, which also keeps the code simple without duplicated if-statements.
I think I prefer using the journal, seeing as that's more universal than rolling our own logging file. At least that's what it seems like from my understanding of the situation.

Sorted out the logging levels. Using debug for things that should go to the console only.
That still leaves the journal.  By default, services send stdout to the journal. This means thousands of lines of "Displaying frame". With the log file, the journal seems redundant, so I'm leaning towards setting the service it to ignore stdout, and use the log file instead.

What if we pass in the log level as an arg? The console and log file wouldn't need to be hard coded at info and debug. Info could be the default but if you wanted a debug log or to run the console at the info, warning, or error levels you could.
Might be nice for bug report to ask for debug logs.

A pair of args for console level and log level? Or maybe just a --debug flag do dump everything to the log?

I was typing that from my phone so didn't get too detailed. I was thinking a flag where you'd pass a level like --loglevel INFO or --loglevel ERROR. This way the user could set the level depending on what they want to collect. A sane default might be INFO or WARN depending on what we want to actually see in the physical file on a normal basis.
In the file you could translate this to the right log level setting with something like this (not sure if these are the exact attribute names).
logLevels = {"INFO": logging.INFO, "ERROR": logging.ERROR, "WARN": logging.WARN, "DEBUG": logging.DEBUG}

fileHandler.setLevel(logLevels[args.loglevel])

Just a --debug flag would be fine too if all the levels is kind of a lot. Just use an if statement to set the level in the actual handler: logLevel = logging.INFO if not arg.debug else logging.DEBUG

Okay, added. Feel free to fix up the help text and add a short argument if you'd like.

Okay, I think we're ready to merge.


Revert "Delete the topics field from guide links"

This was a temporary change required to purge all of the topics fields from the links. Since we're no longer creating the topics field we no longer have to reset it each time we patch the links.

👍


Artman code generation: emitted test code doesn't build

I use artman to generate Java client libraries for my gRPC-based service. Specifically, I'm using the googleapis and toolkit versions from this commit: https://github.com/googleapis/artman/commit/d065fbb63c5778756eb8b6f42ca417079dae04e4.
The emitted production code builds and runs, but the test code doesn't compile as it's emitted. Two fixes are required to make it build:

Gradle dependencies

The following Gradle dependencies are emitted:
dependencies {
  compile project(":grpc-myproject"),
    'com.google.api:gax:1.15.0',
    'com.google.api:gax-grpc:1.15.0',
    'commons-cli:commons-cli:1.4',
    'commons-lang:commons-lang:2.6',
    // This dependency needs to be update-to-date with the version that gRPC expects.
    'io.netty:netty-tcnative-boringssl-static:1.1.33.Fork26'
}

In order to get the test code to build, I have to add dependencies on JUnit and on the test configuration of the gax-grpc library:
dependencies {
  testCompile 'junit:junit:4.11',
    'com.google.api:gax-grpc:1.15.0:testlib'
}

Mock service imports

The test code emits a mock service .java class which imports the service implementation base class from the wrong package. Specifically:
import mypackage.PackageName.MyPackageServiceGrpc.MyPackageServiceImplBase;

... has to be changed to ...
import mypackage.MyPackageServiceGrpc.MyPackageServiceImplBase;

... in order to get the test code to compile.

Moved to http://github.com/googleapis/toolkit: https://github.com/googleapis/toolkit/issues/1730


DEC-574 fix redactor HTMLField component

Editing the source in an HTMLField component was yielding strange behaviors because the code was not updating the props with the raw user input.  Changed to use the raw user input in the onChange event on the textarea, and added separate functions for the callbacks from Redactor vs the textarea.
redactor_field.js.coffee: buttonSource is now just source in newer versions of Redactor.

:+1:

:+1:


Herald should be able to fail a computation if necessary.

Currently, the herald just processes kingdom updates one by one, if it fails to process a computation it would retry. It is not possible to skip a computation if it fails indefinitely.
We need to allow the herald to permanently fail a computation locally and update to the kingdom if necessary.

It should be possible to update the Kingdom using the ComputationLogEntries service. Adding a log entry with an error type of PERMANENT should put the parent Computation into the FAILED state.
See computation_log_entry.proto.

I would prefer to add another method in the ComputationsService.
It is a little weird to call one service to set computation result, and call another one to fail a computation. Using ComputationLogEntriesService to fail a computation is like a side effect of logging an error.

I like the idea of moving the permanent failure to ComputationParticipant.

CC @efoxepstein who initially added report log entries.

I feel like we want to track error types in ComputationLogEntry too to make it easier to correlate log entries with what went wrong. That said, we could keep the source of truth for the current state at the ComputationParticipant level.

FYI, currently all logging rpcs from the duchy to the kingdom are try-and-ignore-failure style. In other words, if a CreateComputationLogEntry rpc fails, the mill won't revert local changes and retry again later.
When we use the ComputationParticipant to fail a computation, we need to make sure the rpc succeeds.


[kr] Korean translation for lesson 3 sensors-and-actuators of 1-getting-started file

The contents of the lesson 3 sensors-and-actuators of 1-getting-started were translated into Korean.

[x] README.kr.md
[x] assignment.kr.md
[x] pi-actuator.kr.md
[x] pi-sensor.kr.md

@microsoft-github-policy-service agree


switch from nextflow DSL1 to DSL2

From https://github.com/c-BIG/NPM-sample-qc/issues/11
This is rather a question/comment. We noted that the pipeline is written using DSL1. Nextflow DSL2 has been introduced nearly 2 years ago and established pipeline collections such as those in nf-core have migrated their pipelines to DSL2 syntax. Are there any plans to update this pipeline as well? Any particular reasons for using DSL1?

The initial version (8f6883c) of the workflow developed couple of years back using DSL1. Recently we start rework with the existing version for the Singapore NPM project. We'll migrate to Nextflow DSL2 soon.

I'll start work using DSL2 once our ongoing developments fixed and addressed your issues, is this fine with you?

@justinjj24 - yes, sounds good to me.

Hi @justinjj24 and @nicolas-bertin
Wondering if there is any update on this or if there is an official release available to test again?


ModuleFederationPlugin can not directly get shared module default export in .mjs file

Bug report

What is the current behavior?
when import vue in .mjs file，compiler result didn't use compatGetDefaultExport to get default export
// bootstrap.js
import './foo.mjs'
import './foo.js'

// foo.mjs and foo.js
import Vue from 'vue'
import bar from './bar'

console.log('bar', bar)
console.log('vue', Vue)

// webpack config
...
      new ModuleFederationPlugin({
        name: 'core',
        filename: 'remoteEntry.js',
        exposes: {
            ...
        },
        shared: require('./package.json').dependencies,
      }),
...

get following wrong result

What is the expected behavior?
use compatGetDefaultExport when import shared module in .mjs file

Other relevant information:
webpack version:  5.70.0
Node.js version: 16.1.0
Operating System: macos
Additional tools:

thats expected .mjs is es module, so there is no compatability for it..

I have also encountered this issue. If module sharing is cancelled, it is normal

Is there a way to solve this?

I raised this question again
https://github.com/webpack/webpack/issues/17874


RuntimeError: time-out of 2000ms while waiting for the simulator, make sure the simulator is ready and connected to <IP_ADDRESS>:2000

Hi everyone,
Since the old same issue seems to be closed, I create a new one:
I run Carla in my host and launch my ros/C++ code in my guest virtual machine, which communicates with Carla.
I have followed the advices under the old same issue, but none of that works for me.
For example, turn on performance mode of my pc, increase the time out parameter from 10 to 200 and press the Play button (or alternatively Alt+P) after launching Carla, before launching my .launch file.
The spec of my pc is:  AMD Ryzen 5 5600H/16G RAM(8G for my VM)/RTX 3060.
I have googled for two days but still got nothing, really need some help here.
Thanks in advance.

Hello @lzhhh93, if you are referencing an older issue, could you please link to it here?
Could you also outline the steps you are taking so that we can reproduce your issue? Also include the versions of carla you are working with?

for reference:

make sure your virtual machine can connect to your host (ping your host's IP address))
make sure your carla version is the same.
make sure the python version you run client and server is the same.


refactor(connect): remove side-effecty connect calls

There were a number of locations where connect was called in the
event that a user had not previously connected. As this is prone
to error, it's being removed in favor forcing users to call connect
explicitly.

Can remove:
'''
// If given full address, pull out target first to avoid leaking credentials in error messages containing linkName.
var rootUri;
if (target && target.toLowerCase().lastIndexOf('amqp', 0) === 0) {
var address = u.parseAddress(target);
rootUri = address.rootUri;
target = address.path.substring(1);
}
'''
from send/receive, since we're no longer allowing them to send/receive without calling connect first.

Also, just to clarify - the connection code in send/receive is there for four reasons:

So users can call send/receive without calling connect
So send/receive can automagically reconnect when disconnected
So a user can call receive on 30 queues all at once without waiting for links to be established one at a time
So a user can call send with 50 messages all at once without waiting for an initial link to be established

1 and 2 can be dropped, I'm fine with that as long as the client has some way to know that they need to reconnect (especially in the case of receivers).
We need to make sure 3 and 4 still work. 3 should work fine, I believe, since receivers are all on different links and just need to make sure that the connection and session is established (which is completed once connect returns). 4 is the harder one, since all sends go over the same sender link. Looking at the refactored code I'm fairly confident this still works, and I believe I have a test for this case, so I'm not that worried. Mostly just documenting for posterity.


VoiceOver: DOM tree, targets pane and content in 'styles tab' are defined as a table elements

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
GitHubTags:#A11y_VSCode;#A11ySev2;#A11yTCS;#DesktopApp;#Visual Studio Code Client;#VoiceOver;#WCAG4.2.1;#DesktopApp;#Win10;#VisualStudioCode-Win32-Apr2021;#A11yMAS;
Repro Steps:

Launch Visual Studio code application with installed Elements for 'Microsoft edge extension .
Start screen reader
Navigate to 'targets' pane and observe voice over announcement.
Similarly navigate to DOM tree in developer tools and to the 'Styles' tab.

Actual Result:
DOM is defined as table. When trying to interact with the table using (Ctrl+Option+Shift+Down arrow), Voiceover announces as 'Use navigation keys to interact.
Expected Result:
Elements in code editor field should not be defined as a table. They should be defined as list items since we are able to navigate to the elements using down arrow keys.
User Impact:
screen reader users will get the wrong information of content

If you take closer look at the Developer Tools you will see that the role of that widget is a tree which is expected here.
Also your developer tools screenshot does not really show anything invalid.
Thus closing as there is no change needed here, and nothing is broken for the user.


Postgresql db is not local and it gets filled, but db-sync server fills 100gb of storage anyway?

OS
Your OS: Amazon Linux 2 for the server and AWS Postgresql for the database
Versions
The db-sync version (eg cardano-db-sync --version):
PostgreSQL version: 11.5 (AWS RDS Postgresql)
Build/Install Method
The method you use to build or install cardano-db-sync: edited the Docker file to use the remote Postgresql and then installed using Docker
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): Docker
Additional context
Server (EC2) is running the db-sync and writes to the remote database Postgresql. The writing to the DB is working correctly, but the server where db-sync is running is storing lot of data even if the DB is not inside the server anymore.
Why does it happen? Is it a bug of db-sync code? Any way to avoid allocating hundreds of gigabytes in the server?
Thank you!

Writing to a Postgres server that is not on the same machine as db-sync will likely be 4 times or more slower. IT is not even a tested or supported configuration.
If you still want to pursue this untested and unsupported configuration then its up to you to figure out what is wrong. However db-sync only connects to a single postgres instance. I suspect the Docker stuff restores a snapshot to the local instance and then syncs from scratch to the remote instance.

Also, last time I check (less that 3 weeks ago) the size of the PostgreSQL database as 53 Gig. Not sure where you are getting this 100G figure.

Can this be closed?

Hello @erikd , sorry for my late reply!

Writing to a Postgres server that is not on the same machine as db-sync will likely be 4 times or more slower. It is not even a tested or supported configuration.
If you still want to pursue this untested and unsupported configuration then its up to you to figure out what is wrong. However db-sync only connects to a single postgres instance. I suspect the Docker stuff restores a snapshot to the local instance and then syncs from scratch to the remote instance.

Our db-sync has taken days for the syncing as we have the PostgreSQL on a different instance of the db-sync process. This is because we have several services that need to query the PostgreSQL continuoslty and in this way we can create read replicas to reduce the amount of queries to a single DB instance.
Could you elaborate the second part of the message, please? I see 50+GB of storage used in the db-sync machine. What are these snapshots exactly? Are they worth being backed up in case we would need to restore the db-sync/postgresql processes?
Thank you and have a great weekend!

Hello @erikd , any news on this? We need to understand if we should backup the 50GB of db-sync data, thanks! :)


Failed to import Unexpected token

I'm just now giving your fork a try, but after importing, I get this error
assets       | ERROR in ./node_modules/konnors-ninja-keys/src/ninja-keys.js 29:18
assets       | Module parse failed: Unexpected token (29:18)
assets       | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
assets       | |    * @override
assets       | |    */
assets       | >   static baseName = 'ninja-keys';
assets       | |
assets       | |   /**
assets       |  @ ./src/js/layouts/MainLayout.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./src/js/layouts/MainLayout.vue?vue&type=script&lang=js&) 7:0-28
assets       |  @ ./src/js/layouts/MainLayout.vue?vue&type=script&lang=js&
assets       |  @ ./src/js/layouts/MainLayout.vue
assets       |  @ ./src/js/layouts lazy ^\.\/.*\.vue$ namespace object
assets       |  @ ./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./src/js/layouts/AppLayout.vue?vue&type=script&lang=js&
assets       |  @ ./src/js/layouts/AppLayout.vue?vue&type=script&lang=js&
assets       |  @ ./src/js/layouts/AppLayout.vue
assets       |  @ ./node_modules/babel-loader/lib??ref--4-0!./node_modules/vue-loader/lib??vue-loader-options!./src/js/App.vue?vue&type=script&lang=js&
assets       |  @ ./src/js/App.vue?vue&type=script&lang=js&
assets       |  @ ./src/js/App.vue
assets       |  @ ./src/js/main.js
assets       |  @ multi ./src/js/main.js

I'm using Vue2
import "konnors-ninja-keys";

I removed my fork of the original ninja-keys, and added yours "konnors-ninja-keys": "^1.10.0",. Is there anything else I'm missing?

That looks like a parser error. You're probably on an older version of Babel / Webpack if I had to guess.
I don't pre-bundle the library yet, so there's no fully bundled version for you to grab either as a workaround.

Yeah, sadly I'm stuck on older versions without any clear upgrade path until we do a full rewrite. I'll see what I can do to work around it. Thanks!


Fallback on PharData to extract archives if ext-zip is unavailable

Came across this todo while looking for my first PR here. Let's use PharData if ext-zip is not available?

Thank you for this, but ExtractZip is actually removed completely in #83 :( sorry for wasting your time

No worries! I'll have a look at other todos and issues 😉


problem withkinect2_calibration!!!

after capturing a budget of about 120 frames for both the IR calibration, color calibration and sync and respecting all instructions on the Web page, the output are these and when i launch the viewer after the calibration the points in the video are not aligned with the image, but are shifted by a long, the re-projection error is approximately 0.3(is too big?) ,(And the image and the point cloud are shifted ..'..why?)
for the color calibration:
%YAML:1.0
cameraMatrix: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 1.1004687793237374e+03, 0., 1.0069369709567793e+03, 0.,
1.0978066255792717e+03, 4.5910703830681450e+02, 0., 0., 1. ]
distortionCoefficients: !!opencv-matrix
rows: 1
cols: 5
dt: d
data: [ 5.1273018211442180e-02, -4.1309038575363652e-02,
-1.5403380499678277e-02, 1.3607453419991436e-02,
1.2777603635683029e-02 ]
rotation: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 1., 0., 0., 0., 1., 0., 0., 0., 1. ]
projection: !!opencv-matrix
rows: 4
cols: 4
dt: d
data: [ 1.1004687793237374e+03, 0., 1.0069369709567793e+03, 0., 0.,
1.0978066255792717e+03, 4.5910703830681450e+02, 0., 0., 0., 1.,
0., 0., 0., 0., 1. ]
for the depth calibration:
%YAML:1.0
depthShift: -2.2823243656717089e+01
for the ir calibration
%YAML:1.0
cameraMatrix: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 3.6491380051748291e+02, 0., 2.4959685356221763e+02, 0.,
3.6438630560775880e+02, 2.0772319014430403e+02, 0., 0., 1. ]
distortionCoefficients: !!opencv-matrix
rows: 1
cols: 5
dt: d
data: [ 1.0165096942146126e-01, -2.9299799708217533e-01,
-7.8572653956486820e-04, -6.7892402528351662e-04,
1.1590297474610570e-01 ]
rotation: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 1., 0., 0., 0., 1., 0., 0., 0., 1. ]
projection: !!opencv-matrix
rows: 4
cols: 4
dt: d
data: [ 3.6491380051748291e+02, 0., 2.4959685356221763e+02, 0., 0.,
3.6438630560775880e+02, 2.0772319014430403e+02, 0., 0., 0., 1.,
0., 0., 0., 0., 1. ]
for the pose calibration:
%YAML:1.0
rotation: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 9.9894326499132058e-01, -3.1952017133869632e-03,
-4.5849144097694909e-02, 5.5494116217593434e-03,
9.9866726137486050e-01, 5.1311841602970365e-02,
4.5624087488219479e-02, -5.1512054356692150e-02,
9.9762966620726579e-01 ]
translation: !!opencv-matrix
rows: 3
cols: 1
dt: d
data: [ -6.4922819925538416e-02, 1.9525107596072039e-02,
3.7529080315411516e-02 ]
essential: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ 6.8255090272380497e-04, -3.8484842264318329e-02,
1.7553140349080749e-02, 4.0451466438663368e-02,
-3.4642208107197110e-03, 6.3048254960314049e-02,
-1.9864758182739209e-02, -6.4773908118525639e-02,
-2.4360999807420910e-03 ]
fundamental: !!opencv-matrix
rows: 3
cols: 3
dt: d
data: [ -5.2237669512051990e-07, 2.9496242838306074e-05,
-1.0898902090344002e-02, -3.1033795693758629e-05,
2.6615488031678916e-06, -1.0457711038294761e-02,
3.1504366658227895e-02, 2.3710177483597092e-02, 1. ]

I am facing the same problem.
I repeated the calibration process twice and made sure that I am not missing anything.
Please help

Cly@ly-HP-Pavilion-Notebook:~/catkin_ws$ rosrun kinect2_calibration kinect2_calration chess5x7x0.03 record color
[ INFO] [main] Start settings:
Mode: record
Source: color
Board: chess
Dimensions: 5 x 7
Field size: 0.03
Dist. model: 5 coefficients
Topic color: /kinect2/hd/image_mono
Topic ir: /kinect2/sd/image_ir
Topic depth: /kinect2/sd/image_depth
Path: ./
[ INFO] [main] starting recorder...
[ INFO] [Recorder::startRecord] Controls:
[ESC, q] - Exit
[SPACE, s] - Save current frame
[l] - decrease min and max value for IR value range
[h] - increase min and max value for IR value range
[1] - decrease min value for IR value range
[2] - increase min value for IR value range
[3] - decrease max value for IR value range
[4] - increase max value for IR value range
[ERROR] Tried to advertise a service that is already advertised in this node [/kinect2_calib_1498205553081554212/compressed/set_parameters]
[ERROR] Tried to advertise a service that is already advertised in this node [/kinect2_calib_1498205553081554212/compressed/set_parameters]
Please help

@lvxingzhe1991 ,that is ok. you  can proceed with the following steps.


iframe

Hello,
I am having issues with  .
I cannot click the join call button ...
Thank you ...

https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia

If you're using getUserMedia() within an , you can request permission just for that frame, which is clearly more secure than requesting a more general permission. Here, indicate we need the ability to use both camera and microphone:
<iframe src="https://mycode.example.net/etc" allow="camera;microphone">
</iframe>


Add integration with pro-airgapped-server

This PR adds integration with pro-airgapped-server charm.
Fixes CSS-9566
NOTE: Before merging this we need to:

Merge canonical/livepatch-server#1138 and publish the snap package, so that the charm can use it.
Update the SERVER_SNAP_REVISION (in src/constants/snap.py) to match the published snap.

LGTM with a question: do we need to store ua contracts addresses in the state or could we extract them in _config_changed by looking at relation data (if a relation exists)?

@alesstimec We can surely use the relation data, but I thought it'd be more straightforward to subscribe to relation changes (changed and departed events) only in the leader, and then propagate the change to other units by updating the state. Also, this is consistent with other relations we have (e.g., database).

Thanks for this, I really like the shift to just grab the URL during the config changed hook.


How to register my plans in WIP section(s)

I would guess that the proper way would be to add an issue in the https://github.com/gothinkster/realworld/tree/master/spec repository (per item 4 in the Ready to implement Conduit in a new framework?) and add my work to list of issues
My brief chat session in the Gitter room led me to believe how people only post questions and nobody answers them

Hello @adriatic, you can create a discussion about your wip here: https://github.com/gothinkster/realworld/discussions/new
Once complete, you can submit the implementation on CodebaseShow


add anomalous office exchange sessions notebook

Can you please review this PR?
Before it gets approved though, I need to wait for my latest msticpy PR to be approved, so that I can then update two links inside the notebook in this PR.
(I make a reference to the msticpy read the docs and notebook for the anomalous_sequence subpackage. The links are to my temporary branch rather than to master though)

@karishma-dixit this is a great notebook, clear, well documented and easy to understand. I have added some very minor comments but none of it is required, just some suggestions. Great work :thumbsup:

Thanks @petebryan  for reviewing my PR. I have made some of the changes you suggested, and I have also updated the msticpy documentation links to point to the version from master branch rather than from my temporary branch.
I will merge the PR into master now


Fix FAQ links

for #14953
need an answer for what to do with pages marked as drafts.

There is an alternate way to write this links.
Here is the starting format: ../installation/mac/#macosx
This pull requests format: /installation/mac/
Alternate possible format: ../../installation/mac
The document processor ends up with the same link.

Thanks @MHBauer, I will defer this to @moxiegirl because I'm not sure either at this moment what the best choice is here (none of them are ideal IMO) :smile:
In the meantime, could you rebase this PR?

Stayed with the same link style. Rebased.

Thanks @MHBauer. I tested your changes and they look good. I added two notes regarding links to the (Docker Hub) registry that would be nice to get in.

LGTM.  As you are in the file, @MHBauer would you mind removing this line whose link is not resolving

That link resolves for me. It takes a while to load, but seems to work.

hit the wrong button

@moxiegirl the link resolved for me as well, but I suspect your link-checker gets refused because Google groups uses some annoying mechanisms for those links :-)
thanks for contributing @MHBauer ! LGTM

Fixes #14953


set power_limit AssertionError

~  sudo throttlestop tdp                                                                                1 err | 14:30:42
{
    "MSR_PKG_POWER_LIMIT":<PHONE_NUMBER>5687528,
    "first": {
        "MSR_PKG_POWER_LIMIT":<PHONE_NUMBER>5687528,
        "power_limit": 45.0,
        "power_enabled": true,
        "power_clamping_limit": true,
        "power_limit_time_window": 28.0,
        "__types.SimpleNamespace": true
    },
    "second": {
        "MSR_PKG_POWER_LIMIT": 4359064,
        "power_limit": 115.0,
        "power_enabled": true,
        "power_clamping_limit": false,
        "power_limit_time_window": 0.00244140625,
        "__types.SimpleNamespace": true
    },
    "lock": false,
    "__types.SimpleNamespace": true
}

~  sudo throttlestop tdp "{"first": {"power_limit": 65.0}}"                                                      ok | 14:30:50
Traceback (most recent call last):
  File "/usr/bin/throttlestop", line 8, in <module>
    sys.exit(main())
  File "/usr/lib/python3.10/site-packages/throttlestop/__main__.py", line 53, in main
    result = build_MSR_PKG_POWER_LIMIT(power_limits, units)
  File "/usr/lib/python3.10/site-packages/throttlestop/msr.py", line 96, in build_MSR_PKG_POWER_LIMIT
    result = _build_MSR_PKG_POWER_LIMIT_internal(_obj.first, _units, _max_power_limit)
  File "/usr/lib/python3.10/site-packages/throttlestop/msr.py", line 107, in _build_MSR_PKG_POWER_LIMIT_internal
    assert 0. <= _obj.power_limit <= _max_power_limit, _obj.power_limit
AssertionError: 65.0

I don't quite understand why this assertion fails, my cpu max tdp is 115w.
Hope you can help me look at this problem in your busy schedule, thanks in advance!

after reading the code at /usr/lib/python3.10/site-packages/throttlestop/msr.py line 94.
I changed the from  _max_power_limit=60 to _max_power_limit=90 make sure to know you processor TDP
def build_MSR_PKG_POWER_LIMIT(_obj, _units, _max_power_limit=60):
    assert isinstance(_obj.lock, bool)
    result = _build_MSR_PKG_POWER_LIMIT_internal(_obj.first, _units, _max_power_limit)
    result |= _build_MSR_PKG_POWER_LIMIT_internal(_obj.second, _units, _max_power_limit) << 32
    result |= int(_obj.lock) << 63
    return result

you can use nano or vim to change the file

I see why, thank you.
I shouldn't have looked at the code carefully at that time.


Release of version <IP_ADDRESS> of xSQLServer

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #857 into master will decrease coverage by <1%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #857    +/-   ##
======================================
- Coverage      97%    96%    -1%
======================================
  Files          30     31     +1
  Lines        3245   3407   +162
======================================
+ Hits         3160   3290   +130
- Misses         85    117    +32


Error in helm install

Helm install is failing with error

k8smaster@k8smaster:~$ helm install argo/argo-ci --name argo-ci
Error: Job failed: DeadlineExceeded

Here are pod logs,

Error from server (Forbidden): error when retrieving current configuration of:
Resource: "apiextensions.k8s.io/v1beta1, Resource=customresourcedefinitions", GroupVersionKind: "apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition"
Name: "workflows.argoproj.io", Namespace: ""
Object: &{map["apiVersion":"apiextensions.k8s.io/v1beta1" "kind":"CustomResourceDefinition" "metadata":map["name":"workflows.argoproj.io" "annotations":map["kubectl.kubernetes.io/last-applied-configuration":""]] "spec":map["group":"argoproj.io" "names":map["plural":"workflows" "shortNames":["wf"] "kind":"Workflow"] "scope":"Namespaced" "version":"v1alpha1"]]}
from server for: "STDIN": customresourcedefinitions.apiextensions.k8s.io "workflows.argoproj.io" is forbidden: User "system:serviceaccount:default:default" cannot get resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

Looks like issue with the roles. I just followed the instructions present in README file. Are there any steps missing,  before hitting helm installation? Please help!

I have the same problem. Just tried it today multiple times on windows, minikube, virtualbox

I am facing the same problem. Did you resolve it in any way?


[Enhancement] kusionstack/kclvm-builder docker image is missing python pip and llvm lld components

Enhancement
kusionstack/kclvm-builder docker image is missing python pip and llvm lld components.

Added lld components in kusionstack/kclvm-builder and validated in #273


Indicate that Discord is our primary chat platform

Adjust the issue and discussion matrix to suggest users can always use
the Discord
Add comment to indicate that using the Discord by default is welcome
Add Discord as an option to the "Want to add something?" section
Indicate that technical and project issues are for the website
Fix "CNI Plugins" naming in "data.json"
Organize additional information into a table

Overriding admin privs due to @orhun's approval (we need to add you to the org still 😄)


WIP: Change py-solc to py-solc-x

I've managed to update the contracts to version 0.6.2 using py-solc-x, but I've stumbled upon a very strange error: during truffle migrate, I get this error for Migrations.sol:
1_initial_migration.js
======================

   Deploying 'Migrations'
   ----------------------

Error:  *** Deployment Failed ***

"Migrations" exceeded the block limit (with a gas value you set).
   * Block limit:  0x6691b7
   * Gas sent:<PHONE_NUMBER>4415
   * Try:
      + Sending less gas.
      + Setting a higher network block limit if you are on a
        private network or test client (like ganache).

Was wondering whether you have seen this before?

 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.vsfalliance seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@uivlis alas i see it all the time and it's not  the best error. I assume this ran against your local blockchain?

Yes, during bin/test.

You'll wanna make sure the ganache in docker-compose.yaml and the truffle version are up to date

Hmm, I see the truffle version is the latest. I've updated ganache in the previous commit, so that would not be the cause of the issue.

Thanks @rbval for the suggestions, but the issue persisted...

Which version of truffle do you have? I ran your branch with<EMAIL_ADDRESS>

Yep, I ran it with that version, too.

This needs a rebase

I pulled your changes into https://github.com/hCaptcha/hmt-escrow/pull/147. Don't worry you still get credit. Let's see if we can push the new one over the finish line.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: uivlis:x: vsfalliancevsfalliance seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Get-MobileDevice / Get-MobileDeviceStatistics document is incorrect

The details for the -Identity switch are incorrect and the first example you have listed shows an incorrect usage.
The first example is "Get-MobileDeviceStatistics -Identity TonySmith" You can not use display name with that switch according to your own article. Only with the -mailbox switch can display name be used.

Also -Identity says you can use DeviceID and GUID. that is also incorrect.  GUID works fine but DeviceID is not it should Read "ID" or "Identity"

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

ID: a5d1678b-3597-59a2-0f16-63948c3853d2
Version Independent ID: 35ffe226-1c51-81a5-7ddc-b7439f6f3480
Content: Get-MobileDeviceStatistics (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@sgtwtf, thanks for pointing that out. The Identity parameter is of Type MobileDeviceIdParameter, and exists in these cmdlets:

Clear-MobileDevice
Get-MobileDevice
Remove-MobileDevice
Get-MobileDeviceStatistics

You're correct in that DeviceID is not supported, but GUID is. However, other identifier values are also supported. I tested Get-MobileDevice and Get-MobileDeviceStatistics, and I updated the Identity parameter descriptions as follows:

You can use the following values that uniquely identifies the mobile device:

Identity (<Mailbox Name>\ExchangeActiveSyncDevices\<MobileDeviceObjectName> for example, TonySmith\ExchangeActiveSyncDevices\REST§Outlook§5eec4e931e0748a263512fd73770d5ac)
Distinguished name (DN)
GUID (same as ExchangeObjectId)

I also updated any/all examples that used the Identity parameter.


Basic VM example

Hey, here is a UVM Basic VM. It is a REPL for a simple Basic dialect with a canvas that you can use to draw stuff.

I just tried your program. Sorry I didn't get back to you faster! I think your basic program is pretty great. Going to give you small feedback from a usability standpoint:

This is a nitpick/stylistic: the console says "type help for available c
ommands". I wish that commands was on its own line instead of having the c on a separate line.

I wish that there was an "EXIT" command. Imo people are likely to reach for that. Would make it more intuitive. May want to also support "QUIT".

I wish that the prompt started with a > or ] or $ character. Would make it easier to distinguish the commands I type from the printed output.

Could be nice to have a FILL command to fill the entire canvas with a given color? :)

There is no error message when an unsupported command is entered. It just says 0, then ready? I was expecting PRINT "HI" to work, but it wasn't, and I wasn't sure why.

Supported color names in the help are in lowercase, but the color names you expect are actually uppercase RED, BLUE, etc.

I couldn't really figure out how to make an infinite loop happen with GOTO. Hmmm.

I'm being very nitpicky here. I think your basic program is already impressive, but there's definitely lots of little details of polish that could be added and together would make it even stronger and more intuitive to use.

I added an strncmp() function to include/string.h so you can make use of it if useful :)
https://github.com/maximecb/uvm/commit/4153cf10494c87fbb8e135b0afe9143942e8fa80

Appreciate the feedback
Will do/fix 1, 2, 3, 4, 6
For 5 when you enter an unrecognized command like say hello it will treat it as a variable and print its value.
so "LET a 1" will change the value of a to 1. Then typing a will print 1. So when you wrote PRINT, it thought that it was a variable, which had the value 0 since you did not initialize it.
For 7 you can have an infinite loop by loading the command
There are two ways of entering commands: a one off command that gets executed and never runs again and a "loaded" command. The latter can be done by prefixing the command with a number. After loading a command you can run using the RUN command.
For example

For 5 when you enter an unrecognized command like say hello it will treat it as a variable and print its value.
so "LET a 1" will change the value of a to 1. Then typing a will print 1. So when you wrote PRINT, it thought that it was a variable, which had the value 0 since you did not initialize it.

It's your basic VM so I respect your choices, but maybe looking up uninitialized variables should print an error instead of evaluating to zero? Would be more intuitive for new users? Or is that just the way basic typically works?

Ya I can see how it could be confusing based on ur feedback. Will update it to throw an error message.

I have completed everything we discussed. Let me know if I missed something.
Feel free to give more suggestions!

One thing that seems like it would be an improvement would be to update the UI every N iterations.
At the moment if you do a loop like:
10 "hi"
20 GOTO 10
You don't see anything update because it's an infinite loop, but this isn't how "old school" basic would behave. Same if you did a loop to plot things.
Another potential improvement would be to add a PRINT command. My understanding is that your basic basically doesn't need that, but I think people will expect it to be there, even if it's not strictly necessary.
Another thing would be to maybe have some random number generator 🤔
Those are 3 things I can think of. All of that being said, I'm happy to merge your current version if you want. It is already a very cool demo 👌 🙂

oh cool I see you merged it 🎉 🎉 🎉 🎉
I have been working on adding your ideas. They are all done. I have also added a sleep command that allow users to delay the time in between commands.
Currently I am trying to figure out a good UX for help since there are just too many commands now that they won't fit on the screen.
I should be able to push something today. Will create a new PR since this one is merged.

I have also added a way to escape infinite loops by pressing escape ( you don't need to do that for the cavas to update tho)
Here is a cool demo!

Sweet!!! :D


wrap reload -> print to console when reloading

During server development, we use a wrapper that reload the server on each file change. It should print to server console whenever the reload is successful.

master now prints msg when hot reloading http dev server


Make message optional

We have many cases where specifying a message is redundant. It would be great if the message was optional and defaulted to something simple like "Invariant Violation".

This lib is supposed to mirror the behavior of the version included in React. If you want an optional message, you can always do const invariant = require('assert');. Node's assert module doesn't require a message.


Would like to see test cases

Tests for order of operations would be cool
I wonder what else

@jedahan Unit tests are in the works. I am also rewriting the lexer as it is far too convoluted atm.

Unit tests added in this commit.

nice!


Features based on nearby establishments

First thing that comes to mind is late-night crashes near bars. Liquor licenses are open data, although the geocoding may not be perfect.

Closing as is too closely related to https://github.com/Data4Democracy/boston-crash-modeling/issues/5


Use more known formats

Make use of formats added in https://github.com/juhaku/utoipa/pull/571
These are not recognised according to https://swagger.io/specification/#data-types , but are very common.
Maybe we need a feature flag to enable this?

Yeah, we could add a feature flag to enable extra formats. :+1:

error: test failed, to rerun pass `-p utoipa-gen --test path_derive_actix`

Test fails, you can run locally all tests for utoipa-gen with ./scripts/test.sh utoipa-gen

Ok, I'll feature flag this , then finish updating the tests.
(name suggestions? unofficial-integer? non-strict-integers ..?)

(name suggestions? unofficial-integer? non-strict-integers ..?)

Hmmm.. not really :smile: , but your suggestions are pretty good ones. It is good if it is short, punchy and descriptive as much as possible :slightly_smiling_face:
Perhaps the second one? Maybe written with underscores? non_strict_integers?

Add the same feature description to src/lib.rs as well https://github.com/juhaku/utoipa/blob/3e6852db7a6275e7c23000a3a80af591106d55b8/utoipa/src/lib.rs#L80-L82


Design ETM -> CTM coupling

Couple to the CTM from the ETM
Now that the ETM is being coupled to the CTM we can start to think about how to handle this the other way around. What would it take (technically) to connect to the CTM from the ETM?
Below you can see a few impressions and a small idea of what kind of development that would entail, and how that could look like. But this plan needs to be better worked out. Research and discussions are neccesary to make the right choices before we can start development.
A few impressions

A user is coupling a CTM scenario inside the ETM

The ETM after the CTM scenario has been coupled

Pro's and cons
For coupling to the CTM from the ETM, I can think of the following pro's and cons.

Pro's
Cons

+ The ETM can send updates to the CTM
- Development work for both ETM and CTM (availability)

+ Introduces the CTM to ETM users (bigger audience)
- Has to be very user friendly, or there is a chance that people will not find/use it

+ Makes the current one-way coupling more clear

+ Can be implemented in small steps (easy to create an MVP where we can expand on)

Research needed
Below are a few questions that we should answer or research before we can start. This list is by any means not final and should be expanded on as we start working on this issue.

Make choices and a design plan of overall interaction (with input from CTM)

What is needed from the ETM perspective?
What is needed from the CTM perspective? E.g. does the CTM expect the ETM to set inputs with them?
Create specifications of what we would need from the CTM API
Create specifications of API alterations on our side

Divide the plans up into steps of work, MVP, nice-to-haves, and create time estimates

Time estimate for design and specifications 3 days

Thanks for writing this up @noracato.
I find myself confused as to which interaction we're designing. There are four possible paths for a user to take when exchanging data between the CTM and ETM:
Taking data from the CTM and viewing the resulting ETM scenario:

CTM export → ETM: A CTM user, working within the CTM, exports their CTM scenario to the ETM and views the results in the ETM.
CTM → ETM import: An ETM user, working within the ETM, imports their CTM scenario into the ETM then views the results in the ETM.

Taking data from the ETM and viewing the resulting CTM scenario:

ETM export → CTM: An ETM user, working within the ETM, exports their ETM scenario to the CTM and views the results in the CTM.
ETM → CTM import: A CTM user, working within the CTM, imports their ETM scenario into the CTM and views the results in the CTM.

I think what you're describing above is option 2, and the CTM devs are currently implementing option 1?
If so, I think we should be clear that this is still a CTM → ETM integration, although one where the user experience is mostly from within the ETM rather than the other way around.

Pros
+ The ETM can send updates to the CTM

I'm not sure how this follows from being able to import a CTM scenario into the ETM. To me this sounds like option 3?

In the background:

The ETM requests the ETM user_values object from the CTM for this CTM scenario. As the CTM has the ability to generate these objects already, this should be easy.

I like this. I agree that if they're willing to expose this feature through their API, asking the CTM for ETM-compatible values would save us a lot of hassle, and reduces the likelihood of the integration breaking in the future. It's better for this translation of CTM user values to ETM user values to exist in one place – if possible – rather than the CTM and the ETM both having to implement their own versions.

Thanks for writing this up @antw & @noracato . Good to have an overview of the possible paths. I think this is a great starting point for the discussion with our client about which path we want to support within the MVP.


Utilities for trotterizing operators

Adds FermionicSimulationGate metaclass with common methods.
Adds trotterize method.

Note that the only failing test is pylint complaining about wrong import order because I'm importing from GitHub. (Needs more recent OF master and two of my PRs on Cirq.)

Sorry, I did not realize how big this PR got. Let me know if you want me to break it up.

Why does pylint say that cirq should come before numpy? Aren't they both 3rd-party imports?

I don't know, just satisfy it haha.

Fixes #253

Hi @bryano sorry for the delay in reviewing this. Can you please split this into two PR's, with one introducing the gates and the other with the trotterization utilities?

Okay, I'll start splitting it up.

@bryano We've come up on 1 year open for this PR.  Given it's age can I assume it is stale?

@ncrubin Yea, I think everything already got integrated in parts (#370, #371, #388).


Defender deployment has error "Payload Too Large"

When performing a deployment through Defender, the following error may occur:
status: 413,\n    statusText: 'Payload Too Large',\n    data: 'HTTP content length exceeded 10485760 bytes.'

This is caused by all of the contracts being included in the build info file when Foundry does a first compilation, which results in the file being too large.
This is a known issue and a fix to optimize this will be included in an upcoming release of the Defender SDK.
WORKAROUND: Make a small edit (e.g. change whitespace) in the contract that you want to deploy, which forces Foundry to recompile it separately.  Then run the deployment script again.
Full error text below:

2023-12-20T14:44:23.920269Z ERROR apply:ext: evm::cheatcodes: non-empty stderr args=["npx", "<EMAIL_ADDRESS>"deploy", "--contractName", "MyContractName", "--contractPath", "test/contracts/MyContractFile.sol", "--chainId", "84531", "--artifactFile", "out/build-info/7abe818c77d7ceb2e81e23d560c4d690.json", "--licenseType", "MIT"] stderr="npm WARN exec The following package was not found and will be installed: @openzeppelin/defender-deploy-client-cli@0.0.1-alpha.0\n/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/api.js:10\n    return Promise.reject(new api_error_1.DefenderApiResponseError(axiosError));\n                          ^\n\nDefenderApiResponseError: Request failed with status code 413\n    at rejectWithDefenderApiError (/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/api.js:10:27)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async DeployClient.apiCall (/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:44:20)\n    at async deployContract (/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-deploy-client-cli/dist/deployContract.js:29:22)\n    at async main (/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-deploy-client-cli/dist/defender.js:32:25)\n    at async run (/Users/eric/.npm/_npx/b4571ac604df0b0a/node_modules/@openzeppelin/defender-deploy-client-cli/dist/cli.js:6:5) {\n  request: { path: '/v2/deployments', method: 'POST' },\n  response: {\n    status: 413,\n    statusText: 'Payload Too Large',\n    data: 'HTTP content length exceeded 10485760 bytes.'\n  }\n}\n\nNode.js v18.18.2\n"

Fixed in https://github.com/OpenZeppelin/openzeppelin-foundry-upgrades/commit/bd03f00eb43691b65019e7030bac329cfeb92b28


Stack Using Array

Type
Data-Structure
Directory
Data-Structures => Stack => StackUsingArray.extension
Description
A Stack is a linear data structure that follows the LIFO (Last-In-First-Out) policy.
Programming Language

[X] c++
[X] c
[ ] python
[ ] java
[ ] kotlin
[X] javascript
[ ] typescript
[X] c#
[ ] swift
[X] ruby
[ ] scala
[ ] go
[ ] php
[X] haskell
[ ] bash

Hey, Can I work on this can you please assign this issue to me? I can do it cpp language. @ahampriyanshu

Hey, Can I work on this can you please assign this issue to me? I can do it cpp language. @ahampriyanshu

Hi @Devenkapoor7303, please opt a different language.

@ahampriyanshu  I can go with javascript ?

@ahampriyanshu  Can I go with java?

Can i work on it for php?

please assign me task

please assign me task

Hi @Anushka1211300 , please mention your preferred language.

hey, can I make it in java?
stack using an array.

Hey @ahampriyanshu  can you please assign me this task for python? thanks!

Can i work on it for python?

Hello @ahampriyanshu  Can i do the task in python?

please assign me it in go

Please assign me in C language

Hey, I will add more functions in the program in C language. Can you assign it to me?

Hey, can I change the whole code of the file or should I have to only add new functions... Because my approach is same but I can make the code structure or execution better.


Folder reorganization

Eliminated pages folder. Completely switched to NextJs App Router.

Please ignore this pull request. I am working on the Senior Design Project that continues this original work. The pull request was supposed to go to the fork.


alt-svc frame origin checks from rfc

Added the origin checks from the RFC for the alt-svc frame.

Coverage decreased (-0.04%) to 97.112% when pulling cf21f43b34989896cadc57ab4bc6901711da09e6 on HoneyryderChuck:alt-svc-fix into 9b5c65989868d964f9bd7c8d51998e698cc654ce on igrigorik:master.

Coverage decreased (-0.04%) to 97.112% when pulling cf21f43b34989896cadc57ab4bc6901711da09e6 on HoneyryderChuck:alt-svc-fix into 9b5c65989868d964f9bd7c8d51998e698cc654ce on igrigorik:master.

Nope, sorry missed your update earlier. Merging. Thanks!


Add SubscriptionID to Subscription struct

The Lemonsqueezy api docs are not really clear, and maybe incomplete even.
But there is a subscription_id key in the api response, which isnt included in the Subscription struct currently.

Thanks @paulrouge