Interacts poorly with per-type indentation settings

When one has a config.cson that specifies per-type indentation, my expectation would be that the config settings are the default for new files and are responsible for the tab width on tabbed files, but that this package overrides these settings based on what is detected. That doesn't appear to be what happens. Instead, it looks like this package gets overridden by the per-type setting.
Steps To Reproduce

Put the following in your config.cson:
".js.source":
 editor:
   tabLength: 8
   tabType: "hard"

Open up a .js file with blatant two-space indentation.

Expected Results
The editor is set to two-space indentation.
Actual Results
The editor is set to eight-space hard tab indentation. If you watch carefully, you can sometimes see the indentation status briefly flash "2 Spaces" before getting thwacked to "Tabs (8 wide)".

(I've been doing some investigation.) I know this isn't a complete solution, but it looks to me like part of the problem is that there is a way for the spacing settings to get updated other than the two methods that this package overrides. Specifically, TextEditor.update is the underlying method, and it is indeed sometimes called directly. As such, it might make sense to override it instead of the other methods, e.g. something like this in auto-detect-indentation.coffee:
    originalUpdate = editor.update
    ...

    # Trigger "did-change-indentation" event when indentation is changed.
    editor.update = (params) ->
      value = originalUpdate.call(editor, params)
      if params.softTabs or params.tabLength
        @emitter.emit 'did-change-indentation'
      value

A little more info: Near as I can tell, the actual settings race is between this package and this bit from text-editor-registry.js in Atom core (around line 333), https://github.com/atom/atom/blob/master/src/text-editor-registry.js#L333-L343:
      for (const [settingKey, paramName] of EDITOR_PARAMS_BY_SETTING_KEY) {
        this.subscriptions.add(
          this.config.onDidChange(settingKey, configOptions, ({newValue}) => {
            this.editorsWithMaintainedConfig.forEach((editor) => {
              if (editor.getRootScopeDescriptor().isEqual(scopeDescriptor)) {
                editor.update({[paramName]: newValue})
              }
            })
          })
        )
      }

One of the so named EDITOR_PARAMS_BY_SETTING_KEY is in fact:
  ['editor.tabLength', 'tabLength'],

Just one more note before I give up on this for the day. I have a really janky workaround, which mostly works. In auto-detect-indentation.coffee, if you delay the indentation setup by a moment, then it will typically end up running after the per-type setup. That is, change this:
    indentation = IndentationManager.autoDetectIndentation editor
    IndentationManager.setIndentation editor, indentation, true

to this:
    # Wait just a moment to allow for the default value to get set up by the
    # per-type configuration code. Then run the detector.
    soon = ->
      indentation = IndentationManager.autoDetectIndentation editor
      IndentationManager.setIndentation editor, indentation, true
    setTimeout soon, 250

The problem I've noticed is that this doesn't work when restarting Atom, when saved window state gets restored. I haven't figured out why that is.
In any case, I hope all this commentary is useful to you.

BTW, the referenced bug was closed as "fixed in 1.12," but it looks to me like the problem still exists in that version.


Revert

This reverts commit 0aea1c0528ae7667e4af494ac0de7ded3865533d while investigating bot breakage.

@swift-ci test and merge

@gottesmm ^

@shahmishal ^

Merged to unblock CI


Swift 4.0 branch 06 02 2017

Method cannot be marked @objc because the type of the parameter 3 cannot be represented in Objective-C

We don't merge from release branches over to master.


modify lasp enforce_once rule to include when value moves from 1 to 2

Did this improve things?

I haven't upgraded our internal project to this version and deployed it yet.

OK, keep us posted.


fix: 8724 fixed alignment issue of delete member confirm modal

Description

added icon props on ads modal component.
updated style of delete member confirm modal alignment

Fixes #8724
Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please refer linked issue

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/8724-alignment-issue-delete-member-confirm-modal

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
54.81 (-0.01)
36.55 (0)
33.46 (0)
55.35 (0)

:red_circle:
app/client/src/components/ads/DialogComponent.tsx
87.5 (-1.39)
65.38 (1.74)
85 (-4.47)
86.84 (-1.4)

:red_circle:
app/client/src/selectors/commentsSelectors.ts
83.61 (-1.64)
61.76 (-2.95)
73.33 (0)
88.24 (-2.35)

Duplicate PR - https://github.com/appsmithorg/appsmith/pull/8816


Missing information about columns

Issue in ./help/ingestion/quality/monitor-data-ingestion.md
The documentation does not contains any info on what each column means. For example: what does it means "Records in profile" and how is different from "Records in Dataset"?
Also, the screenshot is old. It has fewer columns than the current one.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-176373.


Diagrams don’t render on Obsidian mobile

The following code block doesn’t work on obsidian mobile (no rendering)
BlockDiag
blockdiag {
  Kroki -> generates -> "Block diagrams";
  Kroki -> is -> "very easy!";

  Kroki [color = "greenyellow"];
  "Block diagrams" [color = "pink"];
  "very easy!" [color = "orange"];
}

it works perfectly on MacOS.
Thank for you help.

@JPhRt do you have a X86 (Intel) processor or an ARM (Apple Silicon) one? Cause I also experience this issue on ARM.

I experience this same issue. Only kroki-plantuml diagrams seem to render on a current Android 14 mobile device. Other diagrams do not show at all. And in reading view none of the diagrams show up.

I also encountered this issue today and was able to resolve it locally. I put my changes into this merge request. It seems to me somehow on ARM the plugin no longer had access to the Buffer object. Manually including it in rollup fixed it for me.


Support init_on_device

Similarly to init_empty_weights, we support a context manager defaulting all constructors to a specified device:
with init_on_device(torch.device("cuda")):
   model = MyModel() # Directly loaded in the device we want

Additionally we now suppport require_mps that allows one to start testing on other backends provided by torch

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I guess we can also extend to specific dtypes as well now.

Which dtype did you have in mind? For floating types there is a default you can set in PyTorch directly.

You mean https://pytorch.org/docs/stable/generated/torch.set_default_dtype.html ? Does fp16/bf16 also work? If so my bad.

Yes it works pretty well. We use it in Transformers here for instance.


chore: fix yet another common flake

as we try to install the same services multiple times, there are race
conditions.
also there's a common error when trying to look at the plan. therefore we now
install confluent-kafka right in the first step, so it has some time to spin up
before the test.

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

v5.1.14
GitHub release

Your semantic-release bot :package::rocket:


Refactoring folder structure and routing

PLEASE actually check this out in case something is broken. I did a check but I really want to be sure.


ssb-patchwork 3.17.7 crashing when clicking on icon "Chose profile image..."

The bug
ssb-patchwork crashing when clicking on icon "Chose profile image"
To Reproduce

After starting the app click on "Profile".
Click on "Edit Your Profile".
Click on icon "Chose Profile Image...".
The app crashes and disappears all together...

Expected behavior
Expecting to be able to add an Image  and keep editing the profile.
Notify maintainers

Metadata

system: "x86_64-linux"
host os: Linux 5.4.51, NixOS, 20.09pre234242.c71518e75bf (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.7
channels(root): "nixos-20.09pre234242.c71518e75bf"
channels(k): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

It fails with
(ssb-patchwork:2): GLib-GIO-ERROR **: 13:07:02.956: Settings schema 'org.gtk.Settings.FileChooser' is not installed

Which appears to be fixable just the way it was fixed in #84449 in commit d89ed04ea4670664d637fc80129ad03561b53fea, that is, by adding wrapGAppsHook in the arguments and in the nativeBuildInputs
I would like to add that I see all kinds of programs that use image/file choosers crash upon attempting to open such, one other example being, iirc, Zim (the local desktop wiki software).

Mentioning maintainers: @asymmetric @NinjaTrappeur

This issue is a duplicate of https://github.com/NixOS/nixpkgs/issues/76743
Potential fix:

https://github.com/NixOS/nixpkgs/pull/83705

I currently work around that by lauching ssb from a terminal. It seems to inject the appropriate gsettings schema.

I currently work around that by lauching ssb-patchwork from a terminal. It seems to inject the appropriate gsettings schema.

The way I obtained the error message was by launching it from a terminal. It clearly doesn't do that for me. I use awesomewm and xterm.


Merge branch 'develop' into main

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

GitHub release
v0.1.5

Your semantic-release bot :package::rocket:


Feature suggestion - time limit on 'open-stream'

Hi. We're planning on a wrapper for the 'satellite open-stream' which will run a CLI process only for the duration of the pass. This could be simplified (for us!!) if open-stream had an optional command line param to "Terminate after XX amount of time" [with a non-error exit code].
Do you think that would be a useful option, which would be 'trivial' to add...?
Thanks.

if we implement this, perhaps we should also implement persistent connection retries (until timer is up). @danada how do you feel about this?
we may also take into consideration cases where payload streaming exceeds the pass window (perhaps due to network connectivity issues), should the cli auto-terminate? we should be able to detect when the stream is completed using the last byte marker sent by StarPass.

I think that if we do add some sort of termination timer it should be a user-provided limit (at least in the first implementation). Like @davidk81 mentioned, there are situations where data can still arrive on the stream after LOS (sometimes even minutes after LOS), so we'll have to be careful how we decide to terminate the stream.
StarPass does indeed send a last message marker, but I don't think this is transmitted between streamer and clients. It might also be possible to automatically terminate the client after no messages are received for some amount of time (5 minutes, for example).

currently CLI has built-in exponential back-off retry, total retry duration is something like 1min or less. this should be enough for normal use cases, but during our own chaos testing (with simulated server failures), occasionally the CLI is unable to reconnect within the retry duration.
I believe most of our users for the CLI are using external tools to monitor the CLI process, and using the linux timeout command to kill the CLI after desired duration.

let's implement --timeout-seconds feature.

If specified, CLI will exit gracefully (code 0) once timeout reached
In the event recoverable disconnects happen, CLI should attempt to reconnect until timeout is reached
It may still be possible for unrecoverable errors to occur, if it does, program should exit with non-zero exit code

@chelliwell #136 introduced a new feature that should cover this feature suggestion. The new feature accepts a user-provided timestamp that gets compared to the timestamp attached to a message when it is captured at the ground station. This ensures data that continues to arrive after LOS isn't lost even if the provided timestamp = LOS. More usage information is inside the linked issue.

Sorry for the delay in updating this issue. We released the time-based auto-close feature back in November 2020: https://github.com/infostellarinc/stellarcli/releases/tag/v0.8.0
We are heading towards a more deterministic way of closing the stream, though, using the LOS event as a trigger to close the CLI. No timeline for this yet, but it is part of our effort to simplify StellarStation usage patterns.


Support InfluxDB/Telegraf style tags

Hi
So the telegraf agent (made by the creators of InfluxDB) allows tags to serialized into a modified statsd protocol as well.
https://github.com/influxdb/telegraf/issues/39#issuecomment-145928948
https://github.com/influxdb/telegraf/tree/master/plugins/statsd#influx-statsd
But they chose a different way to serialize the data.
Ideally this package should support both for portability

Thanks for the information @WiR3D-kNiGhT.
Could you let us what would be the potential use cases please ? I am worried that adding a different payload format could confuse dogstatsd-ruby users.
Yann

Hi @yannmh
The use case is portability, being able to support tags and move easily from using influx and telegraf to datadog. Because at the moment no ruby statsd client supports the influx serialization, so it makes sense to use a client that already supports tags, and by being the defacto client for telegraf/influx statsd you also always ensure to any user of telegraf/influx that it's easy to move to datadog


Mail 3.0.0 not working with Grails 3.2.6 and JVM 1.8 for spring security register flow

Hello:
I am using spring security ui and building a registration flow. The user is registered fine, but the email is never received. My server is running on tomcat 9.
I am having an issue with Mail 3.0.0, Grails 3.2.6 and JVM 1.8. I configured mail in build.gradle:
compile 'org.grails.plugins:mail:3.0.0'
I am using windows live/outlook for sending emails. I couldn't get gmail to work either.  Any help will be greatly appreciated.
Thanks,
Bilal

It looks like the issue is resolved by using a gmail account, by not using the two factor authentication.
https://github.com/gpc/grails-mail/issues/31
Thanks for great help on github regarding this issue. The issue can be closed.


Get coordinates onPaneClick

Hello, I recently had a problem, I need to get coordinates onPaneClick, how can I do this?

You should be able to obtain the position this way:
const bounds = reactFlowRef.current.getBoundingClientRect();
const position = reactFlowInstance.project({
      x: event.clientX - bounds.left,
      y: event.clientY - bounds.top
});

where reactFlowRef is the ReactFlow component ref and reactFlowInstance is obtained from onLoad callback.

Thanks, I didn't pay attention to this method. Naming in this method so strange.


workbench 2019 support pymapdl?

Dos this pymapdl support workbench 2019?I am now going to use ACT for secondary development, but there are few related documents

Hello,
Documentation for supported versions can be found here:
https://mapdldocs.pyansys.com/getting_started/versioning.html
Sadly, there's no support for pymapdl within Ansys R2019, and the earliest version we officially support right now is Ansys 2021R1.

OK, Our company's workbench cannot be upgraded to 2021 temporarily. For the 2021 version, is there any documentation on how to call pymapdl?

Yes.  Here's the latest docs:
https://mapdldocs.pyansys.com/
You'll want to start here:
https://mapdldocs.pyansys.com/user_guide/index.html

In python, before we use a module, we need to install it first. Is there a way to install this module in the workbench?

Is there a way to install this module in the workbench?

Workbench uses IronPython for their scripting language, and it will not be possible to be able to install a CPython module within Workbench.  If you want to script MAPDL, you'll need to be able to install Python (probably using Anaconda Distribution), and then call MAPDL from there.
Moving forward, it's quite likely that we'll have direct MAPDL support within workbench as a module, but it will only be done if there's a CPython interface within Workbench.

OK, thinks


Unable to cache external resorce

My Options look like this
{
  caches:{
    main:[
      'https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css',
      'http://s.mlcdn.co/animate.css',
      'polyfills.*.js',
      'vendor.*.js',
      'main.*.js',
      '/',
      'sw.js'
    ],
    additional:[
      'assets/service-worker.js',
      'assets/img/angular-logo.png',
      'assets/css/loading.css',
      'assets/css/styles.css',
      'assets/css/forms.css'
    ],
    externals:[
      'https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css',
      'http://s.mlcdn.co/animate.css'
    ]
  }

External Resources are loaded but when i refresh them in offline mode, only local resurces are loaded and external resources are met with a 404
PS: These caches are loaded with AppCache manifest rather than service worker

First of all, why do you put sw.js in the caches? It doesn't make sense for both SW and AppCache.
AppCache doesn't support cross-origin caches over HTTPS. Do you use https on your site?
Thanks.

Yeah I solved it by moving to https
And thanks for pointing it out my mistake


Wrong status and health check urls if random management port

If I configure a random management port (management.server.port=0) in the eureka client's spring boot application properties, eureka calculates the statusPageUrl and healthCheckUrl with the incorrect port, i.e. not the actual management port, but the one for the default server.
I think that this is an unintended consequence of the fix for https://github.com/spring-cloud/spring-cloud-netflix/issues/2732, as the management web server initialization event is being disregarded, which it shouldn't for determining these specific urls.
I'm using the latest spring boot (2.7.5) and spring cloud (2021.0.4)

To be honest, trying to support random ports at all is like a house of cards. Marking for votes.

Mismo error, el error se extiende a prometheus cuando se configura con eureka

Facing the same issue. For local testing the setup i'm using is managment.server.port=0 and server.port=0. Spring boot admin can not access actuator/** resources because eureka uses wrong port. Would be nice to have a solution for this


feature req: --cookie-file option instead of --http-cookie

My suggestion is to add --cookie-file (or similar) option. It's easier and faster to dump cookie file from browser (or with cUrl -c option) than pass multiple cookies with --http-cookie option.
livestreamer --cookie-file cookies.txt hlsvariant://"whatever.com/master.m3u8" best

This is a brilliant addition,ive just come across that youve added this feature,but because its so new theres no documentation about it,so could someone please tell me how to add a cookie.txt file to this line ?
url = "http://<IP_ADDRESS>:88/hls://" + url + " headers={'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.104 Safari/537.36'}'"
Many thanks.
Ian.

This is a brilliant addition,ive just come across that youve added this feature,but because its so new theres no documentation about it,so could someone please tell me how to add a cookie.txt file to this line ?

Not sure what made you think so, but it has not been implemented yet.

Ah thank you.
Thats why ive been trying for days without success to add a cookie.txt file.
So the cookie itself still has to be added to the line ?

So the cookie itself still has to be added to the line ?

Correct.

Thanks Chrippa, I'm aware this is a GiTHub and not a help forum (but if you could point me in the right direction for that it would be great as google hasn't helped) could you show me the correct syntax for adding a cookie to the livestreamsvr example above please,the documentation is a bit vague and ive been struggling with this for ages.

url = "http://<IP_ADDRESS>:88/hls://" + url + " headers={'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.104 Safari/537.36', 'Cookie': 'cookie1=value;cookie2=value'}"
or
url = "http://<IP_ADDRESS>:88/hls://" + url + " headers={'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.104 Safari/537.36'} cookies={'cookie1': 'value', 'cookie2': 'value'}"

Awesome your a star,
Placing it at the end was the one position ive not tried lol.
Thanks ever so much.
Ian.


Cobra viper to kingpin yaml refactor

This builds on PR #91 and removes the dependency on Viper for managing the configuration.

@pgier Could you rebase onto master given that #91 has been merged ?

Ok, rebased onto master, but hold off on merging this one for a bit, I believe there is a bug.

Never mind, it seems to be working fine, I was just seeing the warning from issue #101

Want to rebase with the new CI docker testing?

The change has been rebased, I think this is ok to merge.  The travis build looks done, but I'm not sure why it's still showing as in progress.

Strange, no idea what's up with Travis.

@SuperQ I think it's good to merge


Add option to add aria-label to input box.

I've made it optional.

Thanks, but I really don't think it should be optional, it's less space-consuming if we just add a aria-label such as "color input field" as adding a whole new option.
Moreover strings is a prototype of i18n support and not meant for this kind of purpose :/

Exactly that's why I put it in strings. The aria label should be based on language. Hard coding will not allow other languages.

@adityatoshniwal
Yeah, but this would be the only aria-label with i18n support. We could do all this stuff (including base-sentences in english) in the i18n branch and for all others too. If we have only one which is variable we may as well drop it and hardcode it.

@Simonwep - the aria-label on the buttons are of not much use. Buttons are read by the strings options which allow i18n. Since there is no visible label for input like the buttons have, it has to be aria-label.

Well, there are buttons with no content at all such as the previous-color button and there are many aria-labels on div elements too.

Since there is no visible label for input like the buttons have, it has to be aria-label.

What do you mean by that? I thought we were talking about the aria-label on the input-field? And the aria-labels on the buttons should be more descriptive which might not be necessary for the button-content itself.

I would not argue further, sorry. Thought it would have been a better option. I'll make the changes to hard code it.
Thanks.

I want to move further i18n development to the corresponding branch and finish that once and for all, adding single aria-labels some with and some without translation possibilities doesn't make much sense.
If you want to add this feature you can always make a PR to this branch / file and use the _t(key, fallback) function to access translations / strings.

OK. Thanks.


Product ID is missing

Hi,
Any one encountered this error while uploading a 17mb file to downloadable product?
"Product ID is missing"
max_execution_time = 1200
memory_limit = 128M
post_max_size = 64
upload_max_filesize = 50M
Regards,

Contact your hosting company and show them a screenshot of your error, or
email them the error message. Ask them to assist by increasing the
following values, until you are able to upload your 17mb file. Your hosting
company may have restrictions on these values.
memory_limit
upload_max_size
post_max_size
upload_max_filesize
max_execution_time
max_input_time
Preferably to the following values.
memory_limit = 256M
upload_max_size = 64M
post_max_size = 64M
upload_max_filesize = 64M
max_execution_time = 300
max_input_time = 1000
Editing php.ini File
The  php.ini file is the default PHP configuration file. Most of your
shared hosting companies does not allow access to this file. If you are
certain that you have access to php.ini file on your server, you may
proceed with the following steps.

Access it using your FTP program.
Backup a copy of this file before attempting to edit it.
Open it and find the following values, one at a time (They are
located at different lines within the file)

memory_limit
upload_max_size
post_max_size
upload_max_filesize
max_execution_time
max_input_time

Preferably, edit them to the following values.

memory_limit = 256M
upload_max_size = 64M
post_max_size = 64M
upload_max_filesize = 64M
max_execution_time = 300
max_input_time = 1000
On Thu, Jul 2, 2020 at 10:29 AM Muhammad Zohaib<EMAIL_ADDRESS>wrote:

Hi,
Any one encountered this error while uploading a 17mb file to downloadable
product?
"Product ID is missing"
max_execution_time = 1200
memory_limit = 128M
post_max_size = 64
upload_max_filesize = 50M
Regards,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/boxbilling/boxbilling/issues/598, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24K7LPVBBW37CHZVQVXK3RZSKTDANCNFSM4OO6HMUA
.

Well, I am the hosting provider :)
Sorry... it was my mistake i was changing php.ini for PHP 7.2 and i have restricted BoxBilling to use PHP 7.1.


Feature Request: MAC/IP address

Be cool if we could monitor for MAC and IP addresses as attributes, I have an issue where I occasionally get MAC duplicates and it would be nice if I could trigger alerts when that happens.

I'm playing around in the code-base a bit and it seems to be a pretty straightforward addition, so I'd be happy to open up a PR for this.
However I don't really see any usecase in exposing this data.
The issue you mention seems to be quite specific and something that should be solved (prevented) by configuration rather than by notifying and manual intervention.

I am also thinking about the use-case for this one? MAC address is not really useful for docker itself.

If you got a PR, please raise ... I will close this ticket for now.


Task Matrix Row Coder - (re) Implement the Zoom/current feature

[ ] Zoom explodes Descriptor to fit most of the viewport
[ ] Zoom brings in all the annotaitons on Descriptor/Character state
[ ] Zoom brings in metadata concerning the distribution of coding across OTUs

will be implemented as matrix column codder


Random Row Validation - Not performant on large MySQL tables

Random Row validation uses ORDER BY RAND() on MySQL tables which is not performant on large tables.
Recommendation to calculated MIN() and MAX() and generate Random IDs for monotonically increasing PKs

Closing this since PR#856 did not speed up random row generation significantly


Piwik failing to install

After installing piwik, when I click to create a new grain (Untitled), it keeps hanging with spinning circle for many minutes. Then I checked debug log and it says "waiting for mysql to be available at /var/run/mysqld/mysqld.sock"

You may wish to file a bug about Piwik against the GitHub repository for Piwik on Sandstorm: https://github.com/zarvox/piwik

Closing in favor of zarvox/piwik#6


Training loss jumping up when resuming training.

Hey there,
when I load the model and optimizer state dict from a checkpoint and try to resume training, the training loss suddenly spikes up, removing a lot of the progress the previous training run brought. After a while it goes down again, but the training process is set back by a large margin.
Would you, by chance, know what causes this behavior?
Thanks a lot in advance!

Hello,
I haven't noticed this in my previous experiments, but maybe lowering the learning rate or doing learning rate warm-up for the first 1000~5000 steps can help stabilize the fine tuning?
Best,
Victor

I'll try that, thanks for the idea!
I am currently fine-tuning the ImageNet base on the Ego4D dataset and the qualitative results are already looking quite good.

Good luck with that! Also the domain gap could be a reason for the loss jumping for the first steps, as ImageNet and EgoD4 are quite different.


[AIRFLOW-2842] GCS rsync operator

Hello,
Here is an ticket related to GCP on Jira:
https://issues.apache.org/jira/browse/AIRFLOW-2842
Lots of love

https://issues.apache.org/jira/browse/AIRFLOW-2842


add spatie packages

Usually, I don't accept PRs that add many links all at once - but I'll make an exception for you as your packages are really useful :+1:
P.S I might make some edits to the descriptions so that they maintain the overall style

Cool, thanks!
Had I read the guidelines more thoroughly I would have known that. When a make a PR again in the future, I'll make sure it's one link per PR.


Reduce the cost of check for duplicate states

Reduce the cost of checking for duplicate states. Previously, all of the samples was compared, which is unnecessary; this PR has it just check the first 50 samples in all states (unless there are les than 50 total samples), which is much faster. This is almost certainly sufficient in essentially all cases. This is an optional test that only occurs with verbose on.
This could potentially be made shorter and a little faster with clever use of numpy.unique(), but it's not clear that would really help that much besides shortening the number of lines code, since with this change, the speed cost is mostly removed. numpy unique does an unnecessary sort as well.

For whatever reason, seem to be failing on a test_convariance test?

That looks like its happening due to a bug which was still around when we still had list returns, I think you need to do a git rebase of this from the pymbar4 branch and that will fix itself.

Thanks, tried again!

OK, works now!

As I mentioned in the review, what if we drew a random 50 indices instead of the first 50? I think it would a simple thing which adds to the robustness of the check. Would that add too much overhead for what this fixes?

I'll give it a try later today.

OK, did a version with random 50!

Based on previous approval, merging.

The coverage report should get less noisy once we merge into master. I'll see about making it quieter

OK, did a version with random 50!

Groovy


Trash files in repo

FYI @EisenbergEffect there are few trash files incorrectly pushed up.
core.567.!opt!google!chrome!chrome
core.573.!opt!google!chrome!chrome
core.618.!opt!google!chrome!chrome
core.620.!opt!google!chrome!chrome
core.638.!opt!google!chrome!chrome
core.642.!opt!google!chrome!chrome

Fixed.


tools: Add shared API-Extractor config to repo root

Intended to replace the configs in the build-common package, since it is meant for repo-internal use only. Packages may extend the new config via file path reference, rather than by package import.
The new config captures our stricter ruleset, and also adds the explicit-release-tag requirement. Packages will either need to fix violations when adopting, or explicitly (and temporarily) opt out of those rules in their local configs.
Also updates the api-markdown-documenter package to use the new config as a test case. Other packages can be upated in the future.

PR updating api-markdown-documenter to require explicit release tags: #17258


[release/6.0.1xx] Ensure release tags are automatically created when 6.0.102 is released

Automation is in place but there were some permissions issues that broke it in 6.0.101.  These issues have been resolved but there is no way to validate the E2E until the next release.  This applies to SBRP as well as the source-build repo.

@rbhanda - I am not finding that the 6.0.102 release tags were created in https://github.com/dotnet/source-build-reference-packages or https://github.com/dotnet/source-build.  Can you investigate on your side to see why the automation failed to create these?

Thanks a lot for flagging this. I have pushed the tags manually as of now. We are investigating why the automation did not tag these.

After discussion with the release team, there does not seem to be a requirement to tag source-build and source-build-reference-packages after moving source-build into installer.


[Compute] Fix #24624: az sig image-version create: Fix the error that the --os-vhd-storage-account must be a managed disk or snapshot

Issue - close: #24624
Related command

az sig image-version create
Description

Since the API version of gallery_image_versions is changed to 2022-03-03, the models are changed. GalleryArtifactVersionFullSource and GalleryDiskImageSource are inherited from GalleryArtifactVersionSource, and GalleryArtifactVersionSource is replaced.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

WARNING: source is not a known attribute of class <class 'azure.mgmt.compute.v2022_03_03.models._models_py3.GalleryImageVersionPublishingProfile'> and will be ignored
WARNING: uri is not a known attribute of class <class 'azure.mgmt.compute.v2022_03_03.models._models_py3.GalleryArtifactVersionSource'> and will be ignored

I see that the log provided by the customer contains two warnings about model errors. Could we check whether the GalleryImageVersionPublishingProfile has similar problems?


Too many open files when dialing

Completed requests may still hang onto their response body, which prevents new requests from being sent.
18:25:29.508 func·002 ▶ CRITICAL could not send request to http://www.sparrho.com/: Get http://www.sparrho.com/: dial tcp <IP_ADDRESS>:80: too many open files

This seems to happen when the requested concurrency is very high, e.g. 400 in the test case.


Failed to list profile on EM05-CE

My configuration:
wwan card : EM05-CE (works with Windows LPA)
eSIM chip (since there is no integrated esim onboard the EM05-CE)  : A G+M chip salvaged from iPhone (tested usable with LPAC PCSC mode and Android OpenEUICC)
The error:
sudo lpac-mbim --device=/dev/cdc-wdm0 profile list
INFO: Connect
INFO: Open channel with AID a0000005591010ffffffff8900000100
Error executing command: error: operation failed: Failure

Traceback (most recent call last):
  File "/usr/local/bin/lpac-mbim", line 164, in <module>
    main()
  File "/usr/local/bin/lpac-mbim", line 149, in main
    payload = handle_type_apdu(req["payload"]["func"], req["payload"]["param"])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/lpac-mbim", line 75, in handle_type_apdu
    channel_id = open_channel(param)
                 ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/bin/lpac-mbim", line 51, in open_channel
    output_cmd = run_mbimcli(f'--ms-set-uicc-open-channel="application-id={aid}",channel-group=1').split('\n')
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'split'

mmcli modem info:
  --------------------------------
  General  |                 path: /org/freedesktop/ModemManager1/Modem/0
           |            device id:
  --------------------------------
  Hardware |         manufacturer: Quectel
           |                model: Quectel EM05-CE
           |    firmware revision: EM05CEFCR08A07M1G_LNV
           |         h/w revision: QUECTEL Mobile Broadband Modul
           |            supported: gsm-umts, lte
           |              current: gsm-umts, lte
           |         equipment id:
  --------------------------------
  System   |               device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
           |              drivers: option, cdc_mbim
           |               plugin: quectel
           |         primary port: cdc-wdm0
           |                ports: cdc-wdm0 (mbim), ttyUSB0 (at), wwp0s20f0u2i1 (net)
  --------------------------------
  Status   |                 lock: sim-pin2
           |       unlock retries: sim-pin2 (3)
           |                state: connected
           |          power state: on
           |          access tech: lte
           |       signal quality: 29% (recent)
  --------------------------------
  Modes    |            supported: allowed: 2g, 3g, 4g; preferred: none
           |              current: allowed: 2g, 3g, 4g; preferred: none
  --------------------------------
  IP       |            supported: ipv4, ipv6, ipv4v6
  --------------------------------
  3GPP     |                 imei:
           |        enabled locks: fixed-dialing
           |          operator id: 46011
           |        operator name: CHN-CT
           |         registration: roaming
           | packet service state: attached
  --------------------------------
  3GPP EPS | ue mode of operation: ps-2
  --------------------------------
  SIM      |     primary sim path: /org/freedesktop/ModemManager1/SIM/0
  --------------------------------
  Bearer   |                paths: /org/freedesktop/ModemManager1/Bearer/0

Hello,
I have an EM05-G in my Lenovo laptop and I was also getting the same issue.
I have solved the issue by switching to the second SIM slot, which in the case of my system (not sure if it's true in general) it's apparently the slot connected to the eSIM: mbimcli -p -d /dev/cdc-wdm0 --ms-set-device-slot-mappings=1
After this, I have successfully enumerated the profiles on the eSIM. I have not attempted anything further.

So problem was only related to the selected slot right?
I close the issue for the moment :)


ServiceWorker returns "503 OK (from ServiceWorker)" on accessing dynamic content while offline

Hi, using beta16 i cannot access cached dynamic content. Chrome shows a "503 OK (from ServiceWorker)" and no content is loaded, even though its listed in the caches in chrome. beta11 works fine.

same problem here, what went wrong?

With beta 14 it worked fine for me

I believe it's connected with https://github.com/angular/mobile-toolkit/commit/6f930b8a3550aff34e172bb29867c9155cdb0220

External dynamic contents won't cached with beta-16 (including 6f930b8).
Stephen's blog article says as following:

by creating a dynamic cache group, matching files that are fetched by the Service Worker will also be cached.

but the firebase dynamic group doesn't seem working correctly.

Actually, the contents is not available in offline

cc/ @stephenfluin

Any update on this?

I was also having issues around caching dynamic content on beta16.  I am not sure if they are exactly the same as yours.  I found with the "freshness" strategy none of my api requests were hitting the cache.  This was due to the fetch method making a request and resolving the promise with the actual response from the server which was 503.  Because of this the fetchFromCache code block is never executed and you are left with 503s.  See explanation below.
As a side note the "performance" strategy was working for me, the only caveat being dynamic content is only cached on the second page load due to async nature of the service worker.  My api calls are completing before the service worker is controlling the page.  This is fine for me but at first I was expecting to load the page once and take it offline and everything work, which it didn't.
freshness.ts
The call to fetchAndCache fails but returns a response object with a 503 status code.
const unrestrictedFetch = group
      // Make a request to the network and cache the result, irrespective of the
      // timeout.
      .fetchAndCache(req, delegate)
      // If this operation fails (note that a failed HTTP status code is still
      // counted as success, treat it as an unavailable response.
      // TODO: allow more control over what constitutes request failure and
      // what happens in the case of failure.
      .catch(() => ({response: null} as ResponseWithSideEffect));

// By default, wait for the network request indefinitely.
let networkFetch = unrestrictedFetch;

When networkFetch resolves the first if block checks if response is null and if it is executes.  In this case we have a valid response object so the cache isn't hit.
return networkFetch
      .then(rse => {
        if (rse.response === null) {
          // Network request failed or timed out. Check the cache to see if
          // this request is available there.
          return group
            .fetchFromCache(req)
            .then(cacheRse => {
              // Regardless of whether the cache hit, the network request may
              // still be going, so set up a side effect that runs the cache
              // effect first and the network effect following. This ensures
              // the network result will be cached if/when it comes back.
              const sideEffect = () => maybeRun(cacheRse.sideEffect)
                .then(() => unrestrictedFetch)
                .then(netRse => maybeRun(netRse.sideEffect));

I changed the condition as below and it works for me now.
if (rse.response === null || !rse.response.ok) {

same issue here, I'm trying to implement google maps via angular google maps library, and I'm getting 503 for async loading of the library


Tc integration

@DGuhr, I suggest you add it as a separate directory (authz-openfga-ex) instead updating the exiting approach?

@akoserwal done.


add function abc type to work with IDEs

class function(ABC, Callable):

    @abstractmethod
    @property
    def __name__(self) -> str: pass

    @abstractmethod
    def __call__(self, *args, **kwargs) -> object: ...

User functions  and builtin functions are all functions.

reject this. function is for user function only.


Package.json error on workspaces object

VSCode Version: 1.36.1
OS Version: Linux64 4.15.0-55-generic

Steps to Reproduce:

add in "workspaces":{"nohoist":["somepackage"] } in package.json

Does this issue occur when all extensions are disabled?: Yes

As the error message said, workspaces needs to be an array while you write an object, is this expected?

According to a post on yarn blog, the new workspaces configuration format should be as below:
// flow type definition: export type WorkspacesConfig = {   packages?: Array<string>,   nohoist?: Array<string>, };

@fabricioferreira thanks, then we should update it.

Yup workspaces takes an array as well as an object as well.

The package.json schema is loaded from http://schemastore.org/json/
Please file a bug (or even PR) at https://github.com/schemastore/schemastore/issues

Thanks will PR and file an issue as well

filed a PR https://github.com/SchemaStore/schemastore/pull/756

Thanks!


[RFE] GitHub Action to update the ca-certificates package

Current situation
We have a GitHub Action for the kernel package that helps to keep maintenance branches up-to-date. However, if the ca-certificate package gets outdated and is not able to accept new certificates, OS updates are not possible.
Impact
When ca-certificates is outdated, some HTTPS connections fail, which could also be the one used for updating the OS itself. This is a danger for long-term maintenance releases.
Ideal future situation
A GitHub action files PRs for all branches when new ca-certs updates are available.
**Implementation options
It can be a simple symlink bump like done for the kernel and then run the ebuild … manifest command to update the checksum.
Additional information
We can do a manual update first and prepare the package for easier automation. ← Done

Recently nss 3.72 was released.
It looks like we really need the Github Actions to keep that up-to-date.
The default hg repo of nss does not look easy to deal with.
I would fetch its Github mirror to parse the latest tag with _RTM suffix.
Then it will get easier to write the new Github Action for ca-certificates.

Good idea, I had only thought about extracting the release tar balls from the HTML folder listing, and sorting them to find the highest version.

I will soon write the Github Actions.


black character at the end of lualine integration

When lualine integration is used such as
winbar = {
    lualine_b = {
        "navic",
        color_correction = 'static'
    }
}

It mostly works, except for one black character before the final separator, which I am not sure the cause of or how to remove.

ah that solved that problem, but now the spacing is all a bit weird (as would be expected by removing padding)

Is there a way to fix the black character while still having normal padding?

ah that solved that problem, but now the spacing is all a bit weird (as would be expected by removing padding)

Is there a way to fix the black character while still having normal padding?

You could adjust the padding values of adjacent components to remedy this.

I ran into this as well, only when navic's highlight option was set to true.
Highlight true:
Highlight false:
I realized it was only happening on some colorschemes, so I did some digging and found out that the blank character is highlighted by your colorscheme's StatusLine rule. Make sure it's not set in your colorscheme, or that it's set to the same color as your lualine background.


Automatic build of hosting environment fails with error: Cannot read property 'primaryKeyInfo' of undefined

How did you install the Amplify CLI?
don't remember
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
11.0.4
What operating system are you using?
macos
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
n/a
Describe the bug
The deployment of hosting environment (CI/CD) fails with error: "Cannot read property 'primaryKeyInfo' of undefined"
Expected behavior
Successful deployment hosting environment (CI/CD)
Reproduction steps

Setup automatic deployment of hosting env or connect branch (on github repo) and turn on CI/CD
merge feature branch (on github) and merge it into the branch that CI/CD is connected to
wait for auto-build of hosting env to finish

Project Identifier
e5395aca83e5f807ca8567fa4bd16441
Log output

# Put your logs below this line
                                 # Starting phase: build
2023-04-11T15:57:09.763Z [INFO]: Amplify AppID found: XXXXX. Amplify App name is: XXXXXX
2023-04-11T15:57:09.860Z [INFO]: Backend environment dev found in Amplify Console app: XXXXXX
2023-04-11T15:57:13.169Z [WARNING]: - Fetching updates to backend environment: dev from the cloud.
2023-04-11T15:57:16.020Z [WARNING]: - Building resource api/XXXXXX
2023-04-11T15:57:18.736Z [INFO]: ⚠ WARNING: owners may reassign ownership for the following model(s) and role(s): User: [owner], XXXXXXXXXXXXXXXXGroup: [owner], XXXXXXXX: [owner], XXXXXXXX: [owner], XXXX: [owner], XXXXXXXX: [owner], CancellationReason: [owner], DenialReason: [owner], XXXXX: [owner]. If this is not intentional, you may want to apply field-level authorization rules to these fields. To read more: https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access.
2023-04-11T15:57:22.309Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema.graphql or place .graphql files in a directory at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema
2023-04-11T15:57:22.333Z [WARNING]: - Building resource api/XXXXXXXXXXXAPI
2023-04-11T15:57:37.012Z [WARNING]: - Building resource api/internalAPI
2023-04-11T15:57:37.029Z [WARNING]: - Building resource auth/XXXXXX
2023-04-11T15:57:37.077Z [WARNING]: - Building resource storage/s3XXXXXX
2023-04-11T15:57:37.180Z [WARNING]: ✔ Successfully pulled backend environment dev from the cloud.
2023-04-11T15:57:38.218Z [INFO]: ✅
2023-04-11T15:57:41.637Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2023-04-11T15:57:42.283Z [WARNING]: - Initializing your environment: dev
2023-04-11T15:57:44.973Z [WARNING]: - Building resource api/XXXXXX
2023-04-11T15:57:47.483Z [INFO]: ⚠ WARNING: owners may reassign ownership for the following model(s) and role(s): User: [owner], XXXXXXXXXXXXXXXXGroup: [owner], XXXXXXXX: [owner], XXXXXXXX: [owner], XXXX: [owner], XXXXXXXX: [owner], CancellationReason: [owner], DenialReason: [owner], XXXXX: [owner]. If this is not intentional, you may want to apply field-level authorization rules to these fields. To read more: https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access.
2023-04-11T15:57:51.081Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema.graphql or place .graphql files in a directory at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema
2023-04-11T15:57:51.082Z [WARNING]: - Building resource api/XXXXXXXXXXXAPI
2023-04-11T15:57:55.764Z [WARNING]: - Building resource api/internalAPI
2023-04-11T15:57:55.785Z [WARNING]: - Building resource auth/XXXXXX
2023-04-11T15:57:55.829Z [WARNING]: - Building resource storage/s3XXXXXX
2023-04-11T15:57:55.906Z [WARNING]: ✔ Initialized provider successfully.
2023-04-11T15:57:57.777Z [WARNING]: - Uploading files.
2023-04-11T15:57:57.867Z [WARNING]: - Uploading files.
2023-04-11T15:57:57.871Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.030Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.053Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.336Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.345Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.367Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.392Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.427Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.484Z [WARNING]: - Uploading files.
2023-04-11T15:57:58.660Z [WARNING]: - Building resource api/XXXXXX
2023-04-11T15:58:00.819Z [INFO]: ⚠ WARNING: owners may reassign ownership for the following model(s) and role(s): User: [owner], XXXXXXXXXXXXXXXXGroup: [owner], XXXXXXXX: [owner], XXXXXXXX: [owner], XXXX: [owner], XXXXXXXX: [owner], CancellationReason: [owner], DenialReason: [owner], XXXXX: [owner]. If this is not intentional, you may want to apply field-level authorization rules to these fields. To read more: https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access.
2023-04-11T15:58:04.377Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema.graphql or place .graphql files in a directory at /codebuild/output/srcXXXXXXXXX/src/XXXXXX/amplify/backend/api/XXXXXX/schema
2023-04-11T15:58:04.379Z [WARNING]: - Building resource api/XXXXXXXXXXXAPI
2023-04-11T15:58:09.039Z [WARNING]: - Building resource api/internalAPI
2023-04-11T15:58:09.055Z [WARNING]: - Building resource auth/XXXXXX
2023-04-11T15:58:09.084Z [WARNING]: - Building resource storage/s3XXXXXX
2023-04-11T15:58:09.479Z [WARNING]: - Uploading files.
2023-04-11T15:58:18.065Z [INFO]:
2023-04-11T15:58:18.068Z [INFO]: UPDATE_IN_PROGRESS amplify-XXXXXX-dev-121608 AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:12 GMT+0000 (Coordinated Universal Time) User Initiated
                                 UPDATE_IN_PROGRESS storages3XXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:16 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS apiXXXXXX                 AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:16 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS authXXXXXX                AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:16 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    storages3XXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:16 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    authXXXXXX                AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:17 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:58:18.277Z [INFO]:
2023-04-11T15:58:18.277Z [INFO]: UPDATE_IN_PROGRESS amplify-XXXXXX-dev-121608-apiXXXXXX-XXXXXXXXXXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:17 GMT+0000 (Coordinated Universal Time) User Initiated
2023-04-11T15:58:33.177Z [INFO]:
2023-04-11T15:58:33.184Z [INFO]: UPDATE_IN_PROGRESS FunctionDirectiveStack AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:24 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS User                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:24 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    FunctionDirectiveStack AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:25 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    User                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:25 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXX                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX               AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX            AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX                  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX                  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXX                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX               AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXXXXXXXXXXGroup  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX            AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX                  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXXXXXXXXXXGroup  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:29 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX                  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:29 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:29 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXData                AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:30 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:30 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX               AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:30 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:31 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX               AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:31 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXData                AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:31 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:31 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS XXXXX                  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:32 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    XXXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:32 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:58:33.468Z [INFO]:
2023-04-11T15:58:33.469Z [INFO]: UPDATE_COMPLETE XXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:32 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:58:53.116Z [INFO]:
2023-04-11T15:58:53.118Z [INFO]: UPDATE_COMPLETE    apiXXXXXX                              AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:50 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXTrigger             AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:51 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionhandleXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXTrigger              AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXXXXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXDataTrigger           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXXXXXXXXXXX          AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXApiFnc              AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXX  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXXTrigger             AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionhandleXXXXXX       AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionXXXXXXXXXXXXXXXXXXXXX         AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXXXXXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXTrigger              AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXDataTrigger           AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXXApiFnc              AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXX  AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXXXXXXXXXXXX          AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    functionXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:52 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:58:53.324Z [INFO]:
2023-04-11T15:58:53.324Z [INFO]: UPDATE_COMPLETE functionXXXXXXXXXXXXXXXXXXXXXAWS::CloudFormation::Stack Tue Apr 11 2023 15:58:53 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:59:23.088Z [INFO]:
2023-04-11T15:59:23.090Z [INFO]: UPDATE_IN_PROGRESS                  apiinternalAPI                         AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:53 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                  apiXXXXXXXXXXXAPI                      AWS::CloudFormation::Stack Tue Apr 11 2023 15:58:53 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     apiinternalAPI                         AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:04 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     apiXXXXXXXXXXXAPI                      AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:16 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                  functionXXXXXXJwtRsaCustomAuthorizer   AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:17 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                  APIGatewayAuthStack                    AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:17 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXJwtRsaCustomAuthorizer   AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:18 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     APIGatewayAuthStack                    AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:18 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE_CLEANUP_IN_PROGRESS amplify-XXXXXX-dev-121608              AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:20 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXDataTrigger           AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXXTrigger             AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXTrigger              AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXX  AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXXXXXXXXXXXX          AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXXXXXXXXXXXX         AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXJwtRsaCustomAuthorizer   AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     authXXXXXX                             AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     functionXXXXXXXXXXXXXXXXXXXX           AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     APIGatewayAuthStack                    AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:21 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                     storages3XXXXXX                        AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:22 GMT+0000 (Coordinated Universal Time)
2023-04-11T15:59:53.081Z [INFO]:
2023-04-11T15:59:53.083Z [INFO]: UPDATE_COMPLETE apiXXXXXXXXXXXAPI                AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:32 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE apiinternalAPI                   AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:32 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE functionXXXXXXXXXXXApiFnc        AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:33 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE functionhandleXXXXXX AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:33 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE apiXXXXXX                        AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:44 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE amplify-XXXXXX-dev-121608        AWS::CloudFormation::Stack Tue Apr 11 2023 15:59:45 GMT+0000 (Coordinated Universal Time)
2023-04-11T16:00:13.279Z [INFO]:
2023-04-11T16:00:14.525Z [INFO]:
2023-04-11T16:00:14.575Z [INFO]:
2023-04-11T16:00:14.624Z [INFO]:
2023-04-11T16:00:14.674Z [INFO]:
2023-04-11T16:00:14.724Z [INFO]:
2023-04-11T16:00:14.774Z [INFO]:
2023-04-11T16:00:14.824Z [INFO]:
2023-04-11T16:00:14.824Z [INFO]:
2023-04-11T16:00:14.874Z [INFO]:
2023-04-11T16:00:14.924Z [INFO]:
2023-04-11T16:00:14.974Z [INFO]:
2023-04-11T16:00:15.024Z [INFO]:
2023-04-11T16:00:15.074Z [INFO]:
2023-04-11T16:00:15.124Z [INFO]:
2023-04-11T16:00:15.174Z [INFO]:
2023-04-11T16:00:15.224Z [INFO]:
2023-04-11T16:00:15.274Z [INFO]:
2023-04-11T16:00:15.324Z [INFO]:
2023-04-11T16:00:15.374Z [INFO]:
2023-04-11T16:00:15.424Z [INFO]:
2023-04-11T16:00:15.474Z [INFO]:
2023-04-11T16:00:15.524Z [INFO]:
2023-04-11T16:00:15.574Z [INFO]:
2023-04-11T16:00:15.624Z [INFO]:
2023-04-11T16:00:15.674Z [INFO]:
2023-04-11T16:00:15.724Z [INFO]:
2023-04-11T16:00:15.774Z [INFO]:
2023-04-11T16:00:15.824Z [INFO]:
2023-04-11T16:00:15.875Z [INFO]:
2023-04-11T16:00:15.924Z [INFO]:
2023-04-11T16:00:15.974Z [INFO]:
2023-04-11T16:00:16.024Z [INFO]:
2023-04-11T16:00:16.074Z [INFO]:
2023-04-11T16:00:16.125Z [INFO]:
2023-04-11T16:00:16.175Z [INFO]:
2023-04-11T16:00:16.227Z [INFO]:
2023-04-11T16:00:16.277Z [INFO]:
2023-04-11T16:00:16.326Z [INFO]:
2023-04-11T16:00:16.378Z [INFO]:
2023-04-11T16:00:16.427Z [INFO]:
2023-04-11T16:00:16.477Z [INFO]:
2023-04-11T16:00:16.566Z [INFO]:
2023-04-11T16:00:16.615Z [INFO]:
2023-04-11T16:00:16.626Z [WARNING]: - Uploading files.
2023-04-11T16:00:16.666Z [INFO]:
2023-04-11T16:00:16.716Z [INFO]:
2023-04-11T16:00:16.769Z [INFO]:
2023-04-11T16:00:16.816Z [INFO]:
2023-04-11T16:00:16.869Z [INFO]:
2023-04-11T16:00:16.869Z [INFO]:
2023-04-11T16:00:16.920Z [INFO]:
2023-04-11T16:00:16.969Z [INFO]:
2023-04-11T16:00:17.020Z [INFO]:
2023-04-11T16:00:17.020Z [INFO]:
2023-04-11T16:00:17.070Z [INFO]:
2023-04-11T16:00:17.119Z [INFO]:
2023-04-11T16:00:17.170Z [INFO]:
2023-04-11T16:00:17.220Z [INFO]:
2023-04-11T16:00:17.270Z [INFO]:
2023-04-11T16:00:17.320Z [INFO]:
2023-04-11T16:00:17.371Z [INFO]:
2023-04-11T16:00:17.421Z [INFO]:
2023-04-11T16:00:17.471Z [INFO]:
2023-04-11T16:00:25.051Z [INFO]:
2023-04-11T16:00:25.102Z [INFO]:
2023-04-11T16:00:25.152Z [INFO]:
2023-04-11T16:00:25.168Z [INFO]:
2023-04-11T16:00:25.169Z [INFO]:
2023-04-11T16:00:25.172Z [WARNING]: - Uploading files.
2023-04-11T16:00:25.227Z [WARNING]: - Uploading files.
2023-04-11T16:00:34.997Z [WARNING]: ✖ There was an error initializing your environment.
2023-04-11T16:00:34.999Z [INFO]: 🛑 Cannot read property 'primaryKeyInfo' of undefined
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2023-04-11T16:00:35.061Z [INFO]:
2023-04-11T16:00:35.061Z [INFO]: Session Identifier: XXXXXXXx
2023-04-11T16:00:35.061Z [WARNING]: - Creating Zip
2023-04-11T16:00:35.129Z [INFO]: ✅ Report saved: /tmp/XXXXXX/report-1681228835074.zip
2023-04-11T16:00:35.130Z [WARNING]: - Sending zip
2023-04-11T16:00:36.980Z [WARNING]: ✔ Done
2023-04-11T16:00:36.981Z [INFO]: Project Identifier: 565591091cacd6f12abbca01e80ca35f
2023-04-11T16:00:37.013Z [ERROR]: !!! Build failed
2023-04-11T16:00:37.014Z [ERROR]: !!! Non-Zero Exit Code detected
2023-04-11T16:00:37.014Z [INFO]: # Starting environment caching...
2023-04-11T16:00:37.014Z [INFO]: # Environment caching completed
Terminating logging...

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @jk171505 :wave: thanks for raising this! Was this project recently upgraded to build with Amplify CLI 11.0.4? If so, do you remember the version it was previously using?
Additionally, can you try setting the respectprimarykeyattributesonconnectionfield feature flag to true in amplify/cli.json?

Hi @josefaidt ! thanks for quick response. I believe that was 10.5.2.
I'm not sure if this matters, but the push works without any issues, only CI/CD fails. I tried to connect my feature branch and set CI/CD on it but it fails with the same error.

@josefaidt, setting this flag (respectPrimaryKeyAttributesOnConnectionField) to true didn't help... I'll try to enforce previous version of amplify on CI/CD

Hey @jk171505 we were able to isolate the issue and successfully reproduce with the following schema and command:
type Post @model {
  postId: ID! @primaryKey
  node: PostNode! @belongsTo(fields: ["postId"])
  title: String!
}

type PostNode @model {
  id: ID!
  post: Post! @hasOne
}

➜  amplify codegen model-introspection --output-dir .

⚠  WARNING: Some types do not have authorization rules configured. That means all create, read, update, and delete operations are denied on these types:
         - Post
         - PostNode
Learn more about "@auth" authorization rules here: https://docs.amplify.aws/cli/graphql/authorization-rules
✅ GraphQL schema compiled successfully.

Edit your schema at /Users/josef/Documents/projects/aws-amplify/reproductions/1399/amplify/backend/api/1399/schema.graphql or place .graphql files in a directory at /Users/josef/Documents/projects/aws-amplify/reproductions/1399/amplify/backend/api/1399/schema
Cannot read property 'primaryKeyInfo' of undefined
TypeError: Cannot read property 'primaryKeyInfo' of undefined
    at AppSyncModelIntrospectionVisitor.generateModelPrimaryKeyInfo (/snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-model-introspection-visitor.js:134:67)
    at AppSyncModelIntrospectionVisitor.generateModelMetadata (/snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-model-introspection-visitor.js:82:34)
    at /snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-model-introspection-visitor.js:43:49
    at Array.reduce (<anonymous>)
    at AppSyncModelIntrospectionVisitor.generateModelIntrospectionSchema (/snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-model-introspection-visitor.js:42:64)
    at AppSyncModelIntrospectionVisitor.generate (/snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-model-introspection-visitor.js:29:47)
    at Object.plugin (/snapshot/repo/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/plugin.js:55:24)
    at /snapshot/repo/build/node_modules/@graphql-codegen/core/cjs/execute-plugin.js:36:54
    at /snapshot/repo/build/node_modules/@graphql-codegen/core/node_modules/@graphql-codegen/plugin-helpers/cjs/profiler.js:7:49

Marking as a bug

Hi @josefaidt, I am still getting the same error running the following command with Amplify CLI 12.10.1.
: amplify codegen models --model-schema schema.graphql
Cannot read properties of undefined (reading 'primaryKeyInfo')
TypeError: Cannot read properties of undefined (reading 'primaryKeyInfo')
    at AppSyncModelDartVisitor.getModelIdentifierFields (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:856:51)
    at AppSyncModelDartVisitor.generateGetters (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:268:47)
    at AppSyncModelDartVisitor.generateModelClass (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:168:14)
    at /snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:116:43
    at Array.forEach (<anonymous>)
    at AppSyncModelDartVisitor.generateModelClasses (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:115:50)
    at AppSyncModelDartVisitor.generate (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/visitors/appsync-dart-visitor.js:31:21)
    at Object.plugin (/snapshot/amplify-cli/build/node_modules/@aws-amplify/appsync-modelgen-plugin/lib/plugin.js:55:24)
    at /snapshot/amplify-cli/build/node_modules/@graphql-codegen/core/cjs/execute-plugin.js:36:54
    at /snapshot/amplify-cli/build/node_modules/@graphql-codegen/core/node_modules/@graphql-codegen/plugin-helpers/cjs/profiler.js:7:49

I am getting this error only when I am specifying the fields values of @belongsTo.
It's exactly the same issue but let me know if you would like me to open a separate issue.

So I found a root cause for my issue and this is probably is quite an edge case. My models are structure similarly as the following example:
type Post
  @model
  myId: String!
  content: String!
  comments: [Comment] @hasMany
}

type Comment
  @model
  myId: String!
  content: String!
  post: Post @belongsTo(fields: ["myId"])
}

In this scenario, myId field will be removed from the Comment model per the following code snippet in packages/appsync-modelgen-plugin/src/visitors/appsync-visitor.ts:
if (isCustomPKEnabled) {
  // The native platforms need to remove targetNames fields in belongsTo model
  if (['java', 'swift', 'dart'].includes(this.config.target ?? '')) {
    Object.values(this.modelMap).forEach(model => {
      model.fields.forEach(field => {
        const connectionInfo = field.connectionInfo;
        if (
          connectionInfo &&
          connectionInfo.kind !== CodeGenConnectionType.HAS_MANY &&
          connectionInfo.kind !== CodeGenConnectionType.HAS_ONE &&
          connectionInfo.targetName !== 'id'
        ) {
          // Need to remove the field that is targetName
          connectionInfo.targetNames.forEach(targetName => removeFieldFromModel(model, targetName));
        }
      });
    });
  }
}

I applied the same fix as aws-amplify/amplify-codegen#570 but it's still doesn't work because it compares the primaryKeyName to targetName which seems to exist only for a legacy reason.
I ended up making the following changes to the code and everything worked perfectly.
if (isCustomPKEnabled) {
  // The native platforms need to remove targetNames fields in belongsTo model
  if (['java', 'swift', 'dart'].includes(this.config.target ?? '')) {
    Object.values(this.modelMap).forEach(model => {
      const primaryKeyFields = getModelPrimaryKeyComponentFields(model);
      const primaryKeyName = (primaryKeyFields?.length > 0) ? this.getFieldName(primaryKeyFields[0]) : undefined;
      model.fields.forEach(field => {
        const connectionInfo = field.connectionInfo;
        if (
          connectionInfo &&
          connectionInfo.kind !== CodeGenConnectionType.HAS_MANY &&
          connectionInfo.kind !== CodeGenConnectionType.HAS_ONE &&
          connectionInfo.targetName !== 'id' &&
          !(this.config.target === 'introspection' &&
            primaryKeyName && connectionInfo.targetNames.length > 0 &&
            primaryKeyName === connectionInfo.targetNames[0])
        ) {
          // Need to remove the field that is targetName
          connectionInfo.targetNames.forEach(targetName => removeFieldFromModel(model, targetName));
        }
      });
    });
  }
}

Note that this only happens for native platforms (android, ios, flutter) when respectprimarykeyattributesonconnectionfield is set to true.
Let me know if you want me to create a separate ticket for this. Otherwise, please re-open this issue and I can try writing some tests and create PR.


Juju 2.9 not supported

Steps to reproduce
Use  juju 2.9.46

juju deploy mongodb --channel=6/beta       (or 6/edge)
juju status

Expected behavior
The app goes in active status. Non-support for juju 2.9 is nowhere mentioned, so I expect the charm to support it.
Actual behavior

The app goes into error state with the message hook failed: "install" . The reason seems to be that juju 2.9 does not support secrets (see log output below).
╰─$ juju status                                                                                130 ↵
Model  Controller  Cloud/Region         Version  SLA          Timestamp
mongo  lxd         localhost/localhost  2.9.46   unsupported  08:58:17+01:00

App      Version  Status  Scale  Charm    Channel  Rev  Exposed  Message
mongodb           error       1  mongodb  6/beta   149  no       hook failed: "install"

Unit        Workload  Agent  Machine  Public address  Ports  Message
mongodb/0*  error     idle   0        <IP_ADDRESS>          hook failed: "install"

Machine  State    Address        Inst id        Series  AZ  Message
0        started  <IP_ADDRESS>  juju-f31241-0  jammy       Running

Versions

Operating system:
Ubuntu 22.04.4 LTS

Juju CLI:
2.9.46-ubuntu-amd64

Juju agent:  2.9.46

Charm revision:  149 and 154

LXD: 5.0.3
Log output

Juju debug log:

unit-mongodb-0: 08:54:40 ERROR unit.mongodb/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-mongodb-0/charm/./src/charm.py", line 1431, in <module>
    main(MongodbOperatorCharm)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/framework.py", line 344, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/framework.py", line 833, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/framework.py", line 922, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/./src/charm.py", line 327, in _on_install
    config=self.mongodb_config,
  File "/var/lib/juju/agents/unit-mongodb-0/charm/./src/charm.py", line 217, in mongodb_config
    return self._get_mongodb_config_for_user(OperatorUser, set(self._unit_ips))
  File "/var/lib/juju/agents/unit-mongodb-0/charm/./src/charm.py", line 778, in _get_mongodb_config_for_user
    external_ca, _ = self.tls.get_tls_files(UNIT_SCOPE)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/lib/charms/mongodb/v0/mongodb_tls.py", line 271, in get_tls_files
    if not self.is_tls_enabled(scope):
  File "/var/lib/juju/agents/unit-mongodb-0/charm/lib/charms/mongodb/v0/mongodb_tls.py", line 73, in is_tls_enabled
    return self.charm.get_secret(scope, Config.TLS.SECRET_CERT_LABEL) is not None
  File "/var/lib/juju/agents/unit-mongodb-0/charm/./src/charm.py", line 1139, in get_secret
    secret = self.secrets.get(label)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/lib/charms/mongodb/v0/mongodb_secrets.py", line 136, in get
    if secret.meta:
  File "/var/lib/juju/agents/unit-mongodb-0/charm/lib/charms/mongodb/v0/mongodb_secrets.py", line 84, in meta
    self._secret_meta = self.charm.model.get_secret(label=self.label)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/model.py", line 269, in get_secret
    content = self._backend.secret_get(id=id, label=label)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/model.py", line 3049, in secret_get
    result = self._run('secret-get', *args, return_output=True, use_json=True)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/venv/ops/model.py", line 2686, in _run
    raise RuntimeError(f'command not found: {args[0]}')
RuntimeError: command not found: secret-get
unit-mongodb-0: 08:54:41 ERROR juju.worker.uniter.operation hook "install" (via hook dispatching script: dispatch) failed: exit status 1
unit-mongodb-0: 08:54:41 INFO juju.worker.uniter awaiting error resolution for "install" hook

Additional context

Hi @cbartz Thanks for your issue. Only 5/edge supports Juju 2.9 and we plan to drop support to 5/edge very soon.
Please use Juju 3 :)
I will create a JIRA ticket to update the docs to mention that we only support 3+ on Charmed MongoDB6. Thank youv ery much for helping us improve our documentation :)

@MiaAltieri Thank you for this information. Are cross-model relations with a mongodb_client consumer from a juju 2.9 model supported?
I see secret-related information in the databag
╰─$ juju show-unit data-integrator/0
data-integrator/0:
  opened-ports: []
  charm: ch:amd64/jammy/data-integrator-21
  leader: true
  life: alive
  relation-info:
  - relation-id: 21
    endpoint: data-integrator-peers
    related-endpoint: data-integrator-peers
    application-data:
      mongodb: ACTIVE
    local-unit:
      in-scope: true
      data:
        egress-subnets: <IP_ADDRESS>/32
        ingress-address: <IP_ADDRESS>
        private-address: <IP_ADDRESS>
  - relation-id: 22
    endpoint: mongodb
    cross-model: true
    related-endpoint: database
    application-data:
      data: '{"database": "test-database", "external-node-connectivity": "true", "requested-secrets":
        "[\"username\", \"password\", \"tls\", \"tls-ca\", \"uris\"]"}'
      database: test-database
      endpoints: <IP_ADDRESS>
      replset: mongodb
      secret-user: secret://b0a940a2-3e33-4f38-81fd-73d93ab544ac/cnompr2knc4j9aa9vb80
    related-units:
      mongodb/0:
        in-scope: true
        data:
          egress-subnets: <IP_ADDRESS>/32
          ingress-address: <IP_ADDRESS>
          private-address: <IP_ADDRESS>
  provider-id: data-integrator-0
  address: <IP_ADDRESS>

on. Are cross-model relations with a mongodb_client consumer from a juju 2.9 model supported?

I believe no - since in older implementations of Charmed MongoDB on Juju 2.9 (i.e. the 5/edge charm) - we shared client relation data on the mongodb_client interface directly in the relation_databag (i.e. URI, passwords, etc) - But in now, Juju 3 we use Juju Secrets, meaning that sensitive information in the mongodb_client interface is now shared in secrets (i.e. the secret-user field you have shared above) To view the contents of that secret you can do juju show-secret --reveal secret://b0a940a2-3e33-4f38-81fd-73d93ab544ac/cnompr2knc4j9aa9vb80
It might be possible that Juju has ways of reading secrets in Juju 2.9, but I am not sure if that functionality exists or not. If you would like I can ask a Juju Secrets expert from our team. :)

I did a quick test creating a cmr with juju 2.9, it seems to work (relation databag looks different)
╰─$ juju_29 show-unit data-integrator/0                                                                                130 ↵
data-integrator/0:
  opened-ports: []
  charm: ch:amd64/jammy/data-integrator-21
  leader: true
  life: alive
  relation-info:
  - relation-id: 0
    endpoint: data-integrator-peers
    related-endpoint: data-integrator-peers
    application-data:
      mongodb: ACTIVE
    local-unit:
      in-scope: true
      data:
        egress-subnets: <IP_ADDRESS>/32
        ingress-address: <IP_ADDRESS>
        private-address: <IP_ADDRESS>
  - relation-id: 1
    endpoint: mongodb
    cross-model: true
    related-endpoint: database
    application-data:
      data: '{"database": "test-database", "external-node-connectivity": "true"}'
      database: test-database
      endpoints: <IP_ADDRESS>
      password: Wvwg8kqQqHRnsfY83h6QC5gZAl5Hy1sd
      replset: mongodb
      uris: mongodb://relation-3:Wvwg8kqQqHRnsfY83h6QC5gZAl5Hy1sd@<IP_ADDRESS>/test-database?replicaSet=mongodb&authSource=admin
      username: relation-3
    related-units:
      mongodb/0:
        in-scope: true
        data:
          egress-subnets: <IP_ADDRESS>/32
          ingress-address: <IP_ADDRESS>
          private-address: <IP_ADDRESS>
  provider-id: data-integrator-0
  address: <IP_ADDRESS>

@MiaAltieri  It seems the docs are still not updated, have you created the JIRA ticket?

@cbartz - My apologies. I have now added something in the overview page to reflect that the charm operates on Juju 3. The tutorial also instructs the reader to deploy the charm on Juju 3. Is this what you would expect to see?
I can ask our docs team if it is needed on every single documentation page.

@MiaAltieri I would expect something like this, but mentioning that juju 2.9 is not supported.
As for the tutorial, I found https://github.com/canonical/mongodb-operator/blob/6/edge/docs/tutorial/t-setup-environment.md#install-and-prepare-juju which shows  juju 2.9 as status output.

Hi @cbartz - thanks for this.
AFAICT we do specify the minimum requirements and state juju v3.0 or higher - is what your see here sufficient?
As for the tutorial - please view charmhub/discourse - By default Canonical uses Discourse / Charmhub as their default place for storing/viewing documentation.  What we have here is part of a github workflow that is currently a WIP.
But this is a good reminder. I should remove what docs we have in the repo until this workflow is corrected.

@MiaAltieri Hi, thank you. The documentation on charmhub.io/mongodb has a problem in my browser (cannot open certain sections), so I missed it.

Hi @cbartz - yes unfortunately there is something wrong with Charmhub, from what I can tell from our internal message board it seems that the webteam is working to address it


update Docusaurus and other deps, fix broken styles

Why & how
Superseeds:

#3022

This PR updates Docusaurus to latest beta (beta.18) and most of the other dependencies.
Due to changes in Docusaurus code, I had to adjust the config and add a bunch of fixes to our custom styles, which become broken after the update. I also had to duplicate the GA move in the config, otherwise the website won't start.
Test plan
I have run the updated version of the website on localhost and I used the currently shipped website as a 1:1 comparison, so the style issues was easier to spot, however, there still might be small display problems which I was not able to catch. If you see any regression in preview deploy, please let me know!

I think this looks good! Are there particular places we should look for breakages? I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)

Are there particular places we should look for breakages?

Generally every layout have at least one issue, sidebars too, only home page looks correct after upgrade, so it's hard to point on the specific thing. I usually test few pages, with focus on the origin diversity:

homage (custom JS)
versioned doc page (docs plugin)
blog post list and blog post (blog plugin)
community page (custom MD)

I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)

The fix has been deployed yesterday in separate PR, so you probably should see a data spike on the GA dashboard now, if everything is working correctly.

Oh actually I do think I found an issue -- I thought it was a general issue but it's not reproing off prod: https://github.com/facebook/react-native-website/issues/3061

I have fixed the mobile menu hover issue and the deploy preview should be updated.
Please let me know, if now it looks fine for you.


#147 - Major application configuration overhaul

Most parts of the application were either moved, deleted or adjusted, which results with a lot of changes.
Important stuff that was done:

Updated Docker containers
Configured Laravel, which is contained in the backend folder

Laravel path configuration had to be adjusted in various places like bootstrap, AppServiceProvider.

Moved year old backend to the backend/static to make it separate from Laravel, it's going to be removed later.
Removed vue cli in favor of vite (with laravel and vue plugins) for frontend building.

Development environment does not run properly, but assets can be compiled for local web server.

The frontend seems to work correctly without many changes (excluding the MapBox map, which will be investigated in next pull requests)

This pull request is done with intention to make next ones smaller. :slightly_smiling_face:

MapBox map should be fixed now


Declare Expect of multiple variables without validation.

Deny definition of Expect without validator function for more than one variable.
Action.do.contract({
    ('foo', 'bar'): Expect(),
})

Code above has unclear semantic. What is supposed to do?
If variables are somehow related to each other, this relation should be expressed in the validator function.
Or if variables are not related to each other, code above could be rewritten to:
Action.do.contract({
    'foo': Expect(),
    'bar': Expect(),
})

Superseded by #627


implemented backend interaction with s3 bucket

Co-authored-by: Liliana<EMAIL_ADDRESS>in the config s3.js there are a couple functions that do the interactions with the s3 bucket.  This also adds multer as a dependency.
The imageRouter.js is essentially just there to test the s3 uploads were working.  Talking with Jake, the actual upload will need to take place as part of the submissions record maintenance.

What work was done?
Added functions that connect to s3 bucket for upload of files.

Why was this work done?
to support future development of the record maintenance for submissions

What feature / user story is it for?
work completed as part of https://trello.com/c/VuvmvlAt/776-create-an-aws-s3-cloud-storage-protocol-for-storing-data

[ ] Bug fix (non-breaking change which fixes an issue)

[X] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

[ ] This change requires a documentation update

Change Status

[X] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

Has This Been Tested

[X] Yes
[ ] No
[ ] Not necessary

Not very knowledgeable on S3 bucket but it doesn't look like there's anything that could potentially affect the current state of the BE or anything that could be a problem in the future. Very nice job @PVigar88 and @Liliana-Leyva!


Add test signing support

Tool information

Tool name: Test signing support
Tool license: N/A
Add or update? Config update
Desired version: N/A
Approximate size: 0
If this is an add request:

Brief description of tool: Test signing allows the loading of test signed kernel drivers. Test signing can't be enabled using MS-hosted agents currently because the configuration change needs a reboot to take effect.
URL for tool's homepage: N/A
Provide a basic test case to validate the tool's functionality: 1. Build and test sign WDK driver. 2. Load the driver using devcon, pnputil or equivalent Windows APIs. If test signing is correctly enabled, the driver will successfully load.

Area for Triage:
C/C++
Question, Bug, or Feature?:
Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Ubuntu 20.04 LTS
[X] Windows Server 2016 R2
[ ] Windows Server 2019

Note: not tested on Server 2019
Can this tool be installed during the build?
No. This requires a reboot.
Tool installation time in runtime
Time of a reboot
Are you willing to submit a PR?
Yes

Hello @jamesmistry,
We had a similar request in the past where we have discussed all points related to the feature. Please check it by the link..
Unfortunately, due to unpredictable impact, we are not able to add the feature at this time, but we will keep this request on mind and let you know if we have any updates.
In case of any questions, do not hesitate to contact us.

I would like to request that this be reopened. Several MSFT Windows teams are open sourcing Windows drivers and are leveraging Azure Pipelines for the automation. Currently, with test signing disabled, this forces us to maintain custom, self-hosted agents/machines. With new restrictions on self-hosted agents being put in place we're even more reliant on the default pool machines.
To your comment above related to "unpredictable impact" would you care to elaborate? It's a sandbox environment, right? Anything that breaks is just thrown away anyways. IMO, this "unknown" should not be reason enough to block this feature.

@nibanks are there any drawbacks of the "test-mode" besides the ones provided here?
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option#behavior-of-windows-when-loading-test-signed-code-is-enabled

I'm not expert enough to be able to claim knowledge of all impacts of enabling test-signing, but generally all Windows testing uses it. Additionally, all our self-host machines always have it enabled and never have any problems. I would be surprised if any app development was affected unless it explicitly depended on test-signed drivers not being able to be loaded. I don't think that kind of behavior should block enabling of this. We should be able to use this for driver development.

@miketimofeev so are you Ok with enabling test-signing?

@nibanks let's give it a shot on windows-2022 first as it's in beta state at the moment anyway. If there are no complaints for some period of time we can consider enabling it on windows-2019 as well.

Great! Sounds good. I'm most interested in the older builds, but I'm totally fine with starting with 2022.
BTW, I was thinking, you might want a new Area: Drivers label for things related to drivers and driver development. This and https://github.com/actions/virtual-environments/issues/3858, as well as all the "update WDK" issues would fall into that category.

Windows Server 2022 image with enabled Test signing mode has been deployed.

@al-cheb WS2022 is just the first step. We need this on all Windows versions. My understanding was that we'd start with 2022, and if all goes well (after x weeks?) it'd be enabled for the rest. Can we keep this open until it's everywhere please? WS2022 can't even be used yet anyways because of a number of other issues.

@nibanks let's get back to this in the mid of October. We will track if there is no complaints for win-2022 and then enable the mode on win-2019

@nibanks, Windows Server 2019 image with enabled Test signing mode has been deployed.


Animate on new item, Custom Marker Render.

I am dynamically adding items from a socket connection.
When a new marker item is added I navigate on a tour to the location of that marker item.
On each custom marker there is an animation.
var group = new THREE.Group();
item.add(group);
var myAnimation = new TimelineMax({repeat: 0});
myAnimation.delay(1);
myAnimation.to(group.position, 2, { z: 0, ease:Power2.easeInOut});
myAnimation.to(group.scale, 2, { x: 1, y: 1, z: 1 });

This animation does not play when the new item is added, however when the globe initializes all the markers play the animation.  How can I get a callback on new Marker add?

I don't have enough context from what you have provided, but the lib exports a named method called tween that you can use.
tween is used in the render method that is called in requestAnimationFrame, so any animations that uses it should be updated in the main Globe's animation cycle: https://github.com/chrisrzhou/react-globe/blob/master/src/Globe.ts#L224-L227
You can also do something without the method exported by the library in https://codesandbox.io/s/knhlr.  I think a drawback of not using the main rendering cycles is creating new requestAnimationFrames that could have performance issues.
I think better support to allowing the component to accept renderers (callback) so that it can apply them in the main render cycle would be more ideal.


TODO: Implement method DBPolymorphicForeignKey::scaffoldFormField

Description

Opt-out of form field generation - Scaffolding should be performed on he has_many end, or set programmatically.
Investigate suitable FormField

See: https://github.com/silverstripe/silverstripe-framework/blob/cf78a9d785b9959a92dfb52c2a456bea80a4c567/src/ORM/FieldType/DBPolymorphicForeignKey.php#L23

I'm gonna close this one - as the comments note, scaffolding should be performed on the has_many end. If developers want a field for the has_one, they should explicitly add one to their form.