Apply AlignAssignmentStatement to Enum declarations

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues to ensure it has not already been reported.

Summary
It would be really nice if the alignment of Enum declarations could be maintained or formatted automatically.
Example:
# Current:

[Flags()] enum GreekAlphabetEnum {
    Alpha = 0b0000000000000001;
    Beta = 0b0000000000000010;
    Gamma = 0b0000000000000100;
    Delta = 0b0000000000001000;
    Epsilon = 0b0000000000010000;
    Zeta = 0b0000000000100000;
    Eta = 0b0000000001000000;
}

# Desired:
[Flags()] enum GreekAlphabetEnum {
    Alpha   = 0b0000000000000001;
    Beta    = 0b0000000000000010;
    Gamma   = 0b0000000000000100;
    Delta   = 0b0000000000001000;
    Epsilon = 0b0000000000010000;
    Zeta    = 0b0000000000100000;
    Eta     = 0b0000000001000000;
}

Proposed Design
Another hashtable key for AlignAssignmentStatement such as CheckEnum = $true eg.
@{
    # Rules: https://docs.microsoft.com/en-us/powershell/utility-modules/psscriptanalyzer/rules/
    Rules = @{
        PSAlignAssignmentStatement = @{
            Enable         = $true
            CheckHashtable = $true
            CheckEnum      = $true
        }
    }
}

I think this is a duplicate of https://github.com/PowerShell/PSScriptAnalyzer/issues/1739


Feature/metobs data header parsing

Description
Parse metobs header into a dictionary. Still, store the raw header string.

The _parse_data function should probably be split into two, one for the header and another for the data. But maybe leave it like this for now?

I fixed the split here.

Awesome!


FlatList re-creates child items when numColumns > 1

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
When adding items to a FlatList where numColumns > 1 I see behavior where existing list items are unmounted and replaced by new ones. This was discovered when trying to animate (fade in) new list items to a FlatList with 2 columns.
This was first reported and closed due to not being verified in the latest version here: https://github.com/facebook/react-native/issues/23066
React Native version:
System:
OS: macOS 10.15.4
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 1.33 GB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.14.0 - /usr/local/bin/node
Yarn: 1.22.5 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /Users/rick/.rvm/gems/ruby-2.6.5/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 26, 27, 28, 29, 30
Build Tools: 27.0.3, 28.0.3, 29.0.2
System Images: android-23 | Google APIs Intel x86 Atom_64, android-24 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom
Android NDK: 21.3.6528147
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>58069
Xcode: 12.1/12A7403 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_241 - /Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
In the snack given below we have a FlatList with numColumns > 1 and a button to add list items. Notice that when data is added for a component list item, and it's positions is to be in the second column, the component item in the first column is unmounted and destroyed and a new item is created and mounted.
Expected Results
I expect, that when I add new data to a FlatList, and there is previous data that has not changed (data or key), those Component items that existed before the data is updated, remain mounted. This appears to work as expected when numColumns is not set, or set to 1.
Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/@asymptotik/flatlist-enthusiastic-item-construction

This issue has been reported multiple times(#23066, #25548, #19426) but have been closed everytime without a solution. I hope this gets resolved this time.

People must not be using numColumns much :(
Seeing this as well with a 2 column list for tablets.  Adding one new item will trigger the re-render 40+ items per my settings.  Moving it to 1 column just renders the new addition as expected.
Since flexWrap "wrap" can't be used with VirtualizedList, and my items are (unfortunately) a little to heavy for low end tablets to re-render in mass, it's unusable currently.
Hope there is a hero out there. :)

Has anyone solved this problem?

still an issue!


The parameters of multici.multinomialCI might be wrong

According to the document https://cran.r-project.org/web/packages/MultinomialCI/MultinomialCI.pdf , the second parameter of multici.multinomialCI  should be significance level. However, the confidence level is feed into the function call in line 20 of the file bound.py.

Thank you for pointing out the issue. We have fixed the bug in the code. Please note it does not change any conclusion from our paper, although figure 1 looks different now.


Add support for binding HealthChecks middleware to a port

From @anurse on Thursday, October 12, 2017 7:46:43 PM
This is useful for ensuring that the health checks are only visible to infrastructure components and not available on the public internet. Using a different port for health checks makes that easier to configure.
Copied from original issue: aspnet/Diagnostics#414

This was done for preview1. UseHealthChecks accepts a port. See samples in the aspnet/Diagnostics repo


⚠ Bofrost.hr has degraded performance

In 9f96bdd, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 19322 ms

Resolved: Bofrost.hr performance has improved in 2506b69 after 6 minutes.


SPI Support in the Octal Bone Script Library?

Any thoughts on how my project should do SPI communication?  I'm worried that 3rd party node modules would conflict since they are accessing pins to communicate.  Any help or suggestions would be greatly appreciated.
BTW the OBS is working great for our needs so far.  Thanks so much for developing and maintaining!
-roger

I don't think SPI is currently possible with code as is. You should find a device tree and load it to work on it. https://github.com/beagleboard/bb.org-overlays/tree/master/src/arm
I am afraid lot of code changes needs to be done to support this and I currently don't have time to work on it. If you are willing to do, please create PR.

This library is abandoned. Please check notice in README for further information.


Update pom property version.fabric8 to 3.0.1

[merge]

replaced with https://github.com/fabric8io/fabric8-maven-plugin/pull/1067


micromamba

How can I get this plugin working with micromamba with antigen / oh-my-zsh in addition to conda / miniconda (conda works great!)? I see micromamba referenced here: https://github.com/conda-incubator/conda-zsh-completion/blob/2cc833a65037399bffaa149780beb2dd5376859e/_conda#L1C2-L1C32

The top of the file reads
#compdef conda mamba micromamba

so if you can get it to work for conda it should also work for mamba and micromamba.

I figured it out, had to do with the order of the mamba hooks being initialized in zshrc. Thanks!

@bmahlbrand awesome! Thank you for following up and closing this issue.


Secure web socket (wss) support for reverse proxying

I created a reverse proxy host for my ezbeq instance. Everything works fine over regular http, but when connecting over https, the console returns the following error:
Mixed Content: The page at 'https://ezbeq.mydomain.net/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://ezbeq.mydomain.net/ws'. This request has been blocked; this endpoint must be available over WSS.
Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
at new Nge (https://ezbeq.mydomain.net/assets/index-bb2f419b.js:249:10427)
at https://ezbeq.mydomain.net/assets/index-bb2f419b.js:249:11538

Nevermind! This is a reverse proxy config issue and nothing to do with ezbeq.

Hi there @chippoman, would you be willing to share your nginx config that allowed you to successfully do this? Thank you!

I just ran into this when trying to run ezbeq in kubernetes and since I was already building the container and it's harder to hack on the nginx ingress config, I just rewrote the UI JS to use wss. This could probably be fixed fairly trivially by setting the protocol (ws vs wss) based on window.location.protocol. I personally am hosting this on a .dev domain which requires HTTPS so this was a must.
To demonstrate, this is all I'm doing with the container:
FROM ubuntu:24.04
ENV EZBEQV=2.2.0

RUN apt-get update \
  && apt-get install --no-install-recommends -y python3-pip python3-dev build-essential \
  && rm -rf /var/lib/apt/lists/* \
  && pip install --no-cache-dir --break-system-packages ezbeq==${EZBEQV} \
  && sed -Ei -e 's~ws://~wss://~g' /usr/local/lib/python3*/dist-packages/ezbeq/ui/assets/index-*.js \
  && mkdir -p /srv/ezbeq # mount the config here and set env var EZBEQ_CONFIG_HOME to this

CMD ["ezbeq"]

(this is for use with an HTP-1 which does not have other dependencies like minidsp-rs)

@Frick you can try 2.2.1 which incorporates that change to the UI code

@3ll3d00d that did the trick! I was able to remove my sed line from the above Dockerfile. Thanks for the quick adjustment! 😄
Now if you have updates to the Python package auto-build ezbeq-docker with the same version, I'll just use the ghcr.io release instead of my container. 😁


Create globally definable default settings

Update to add global default options
Fix resize timeout undefined error
Make resize timeout user definable option

Merged and published. Thanks!
On Sat, Oct 8, 2016 at 4:24 AM, Aron Kerr<EMAIL_ADDRESS>wrote:

Update to add global default options
Fix resize timeout undefined error
Make resize timeout user definable option

You can view, comment on, or merge this pull request online at:
https://github.com/punkave/jquery-projector/pull/2
Commit Summary

Update to add global default options

File Changes

M jquery.projector.js
https://github.com/punkave/jquery-projector/pull/2/files#diff-0 (64)

Patch Links:

https://github.com/punkave/jquery-projector/pull/2.patch
https://github.com/punkave/jquery-projector/pull/2.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/punkave/jquery-projector/pull/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fY6A_0oQY1mU-zckihQU4qOSbpAhks5qx1NWgaJpZM4KRqLM
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

(Are you using this with Apostrophe? It'll land there in our next
patchlevel, most likely Friday.)
On Mon, Oct 10, 2016 at 1:38 PM, Tom Boutell<EMAIL_ADDRESS>wrote:

Merged and published. Thanks!
On Sat, Oct 8, 2016 at 4:24 AM, Aron Kerr<EMAIL_ADDRESS>wrote:

Update to add global default options
Fix resize timeout undefined error
Make resize timeout user definable option

You can view, comment on, or merge this pull request online at:
https://github.com/punkave/jquery-projector/pull/2
Commit Summary

Update to add global default options

File Changes

M jquery.projector.js
https://github.com/punkave/jquery-projector/pull/2/files#diff-0
(64)

Patch Links:

https://github.com/punkave/jquery-projector/pull/2.patch
https://github.com/punkave/jquery-projector/pull/2.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/punkave/jquery-projector/pull/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fY6A_0oQY1mU-zckihQU4qOSbpAhks5qx1NWgaJpZM4KRqLM
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Yes I am. Thanks for merging it in so quickly. 👍

You got it!
Please do sign up for the Apostrophe developer directory if you'd like:
https://tomboutell1.typeform.com/to/NeqckD
On Tue, Oct 11, 2016 at 11:13 PM, Aron Kerr<EMAIL_ADDRESS>wrote:

Yes I am. Thanks for merging it in so quickly. 👍
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/punkave/jquery-projector/pull/2#issuecomment-253107827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fUL6UXmx2xuZwHJISn-TXekznm8qks5qzFBcgaJpZM4KRqLM
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com


java: detect wrapped streaming error

GAX now wraps streaming errors, so tests must look to wrapped errors
instead.
cc @igorbernstein2

Superseded by #1827

Oops, sorry I forgot to update toolkit after my changes


HSEARCH-5181 Add compatibility with OpenSearch 2.15.0

https://hibernate.atlassian.net/browse/HSEARCH-5181

https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/detail/PR-4211/2/pipeline


Form OnSubmit doesn't work.

I found strength thing:
import React, { Component } from "react";
import FieldGroup from "./FieldGroup";
import { connect } from "react-redux";
import { Form, Button } from "react-bootstrap";

class UserUpdateForm extends Component {
  constructor(props) {
    super(props);

    this.handleUserUpdate = this.handleUserUpdate.bind(this);
    this.handleChangeName = this.handleChangeName.bind(this);
    this.handleChangeNickname = this.handleChangeNickname.bind(this);
    this.state = {
      name: this.props.current_user.name,
      nickname: this.props.current_user.nickname
    };
  }

  handleChangeName(event) {
    this.setState({
      name: event.target.value
    });
  }
  handleChangeNickname(event) {
    this.setState({
      nickname: event.target.value
    });
  }

  handleUserUpdate(event) {
    event.preventDefault();
    const url = event.target.action;
    console.log(url);
    return false;
  }
  render() {
    return (
      <Form
        onSubmit={this.handleUserUpdate}
        action={this.props.action}
        method="patch"
        id={this.props.id}
      >
        <FieldGroup
          role="form"
          id={`${this.props.id}Name`}
          type="text"
          label="User Name"
          placeholder="Enter User Name"
          onChange={this.handleChangeName}
          value={this.state.name}
        />
        <FieldGroup
          role="form"
          id={`${this.props.id}Nickname`}
          type="text"
          label="User Nickname"
          placeholder="Enter User Nickname"
          onChange={this.handleChangeNickname}
          value={this.state.nickname}
        />
        <Button className="btn btn-primary btn-large centerButton" type="submit">Send</Button>
      </Form>
    );
  }
}

export default connect(state => ({
  current_user: state.current_user
}))(UserUpdateForm);

The Sign In/Sign Up form work, but UserUpdate not. Actually, onSubmit doesn't work.  I don't see console.log(url).
App: https://on-money.herokuapp.com
Git: https://github.com/yashka713/on_money_front/blob/deploy/src/forms/UserUpdateForm.js
login<EMAIL_ADDRESS>password: password
You should click on User profile and then click to FontAwesome Icon.
Thx :)

@yashka713

here is not the place for React or ReactBoostrap problems (it's better to use stackoverflow.com for that)
googling your problem and in the first link found an answer: https://stackoverflow.com/questions/37239799/can-not-submit-form-react-bootstrap
You should wrap your Form with native  tag (and place onSubmit handler there)

@sidoruk-sv
I tried add form, Form and even remove Modal window. The problem wasn't solved.
Also, input doesn't allow to use white spaces. That's very strangely.

@yashka713 it is some kind of mess with react-bootstrap components.
I don't know what <FieldGroup/> can be.
Its name is similar to react-bootstrap's <FormGroup> but for input elements, react-bootstrap provide  components.
So I tried to rewrite your example (as I understood) it's worked as expected:
https://jsfiddle.net/n5u2wwjg/19845/
P.S. as I understand you expect that form will be submitted automatically, - using default action and method attributes.
It will, but:

method attributes can only be get | post (https://www.w3schools.com/jsref/prop_form_method.asp);
it's better to handle server request through xhr/fetch instead of native <form> behavior (or even better - through some state management library - for example https://www.valentinog.com/blog/react-redux-tutorial-beginners/#React_Redux_tutorial_Form_component_and_Redux_actions)

@sidoruk-sv
The reason why I am writing here, that's because it doesn't work in my App, not in "jsgiddle" or "codepen".
<FieldGroup/> - https://react-bootstrap.github.io/components/forms/#forms-controls.
I think, onSubmit should work with narrow function, but it doesn't work.
The next problem is that <input> doesn't allow to write white spaces.
If I remove <form> from Component <input> still skips  white spaces. You can see this on a site, from 1st comment.

@sidoruk-sv
My main purpose - onSubmit starts function :)

StackOverFlow: https://stackoverflow.com/questions/49792505/react-form-onsubmit-is-not-working-and-input-not-allow-to-use-white-spaces

@sidoruk-sv
You are right, problem is in the react-bootstrap. I will close Issue.


Allow filtering for service_ids or team_ids in table pagerduty_incident

Is your feature request related to a problem? Please describe.
When querying longer time ranges (e.g. last 14 days) in a PagerDuty account with a lot of services and high amount of total incidents, the query takes a lot of time (last 30 days = 25 minutes).
Describe the solution you'd like
The PagerDuty API allows additional filter parameters like service ids or team ids which could limit the requested amount of data and therefore the query runtime significantly. I would like to implement the additional filter parameters so they are used when the user adds a where clause for team id and / or service id to the query
Additional context
I would be happy to also implement the options to filter by service id or team id, but not sure how this could be achieved with the current table structure, since service and team infos are json objects in the results without a dedicated team_id or service_id column.

Adding column level qualifiers for common fields so they can be targeted in requests makes a big difference to performance and a lot of sense in this case.
Question - Does the PagerDuty API support filtering on those fields?

Yes, both are available in the api and the used SDK. https://developer.pagerduty.com/api-reference/9d0b4b12e36f9-list-incidents

In case of the team id,  one incident could belong to multiple teams. Is there also a good way to reflect this in the new columns?  And have I understood it correctly that the option would be add additional columns?
If there are examples from other tables available this would help


VSCode creates log files in the config directory and these accumulate ad infinitum

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

VS Code Version: 1.85.2, applies to any current version AFIK
OS Version: Linux

Description: By default, VSCode creates log files at the location ~/.config/Code/logs/, e.g. /home/username/.config/Code/logs/20240522T223215/window1/renderer.log This is not a proper location for log files and they never get cleaned up. The .config directory is for configuration and meant to be backed up by the user. It is not meant to be filled with logs by the application.
I've noticed the issue because platformio generated hundrets of MBytes of logs in merely a few hours, all of them looking like "2024-05-22 22:42:50.155 [error] [Extension Host] Errored result: [object Object]". These occuring in that frequency and being completely useless at the same time is a different topic. However, a misbehavior can easily fill hard drives in completely unexpected locations.
Steps to Reproduce: Check your config dir see how many MBytes of logs you have in there.
Solution: The log directory should, by default, be placed somewhere else, e.g. in /tmp/.code-username/ or using mkstemp(). Observe practices how to create temporary files to avoid issues. For instance "/tmp/.code-username" might already exist and/or be a file or symlink to something else.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

It is also present in the latest version.

I can also confirm the issue with 1.89.1.
It's due to how the default logsHome is computed:
https://github.com/microsoft/vscode/blob/eccc47493a39ad1e6ecf9b754989d3744759a10f/src/vs/platform/environment/common/environmentService.ts#L76
On Windows and macOS, it's fine.
On Linux, the logs shouldn't be placed in the .config directory.
It should be placed in $XDG_STATE_HOME($HOME/.local/state) instead of $XDG_CONFIG_HOME.
Reference: https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html


Migration to iced's "pure" widget design

This is a proposal for a migration to iced's "pure" widget design. See https://docs.rs/iced/latest/iced/pure/index.html.
It targets iced current main branch.
The second commit suggests slight improvements, which are independent of the migration.
Fixes https://github.com/iced-rs/iced_audio/issues/23

Updated to latest iced release.

Nice! I'll try to have a look when I have time.

I thought current state was good enough for supporting Styles but it seems it's not! I'm working on an application for which I want the widgets in a Component and the old Style handling gets in the way. I'm looking into this issue ATM, so I'll probably push some fixes in the coming days.

Alright, great!

Style handling migrated!
FWIW, my issue with the integration of iced_audio widgets in a Component didn't have to do with theme / style handling. I needed to restrict the Component's Renderer implementation to iced::Renderer since iced_audio only supports this Renderer currently. Theme & Style handling needed a migration anyway.
IMO this repository would require a clippy cleanup :) I can do this in another PR if this one gets merged.

Nice!
on_drag_start is necessary to be able to call begin_automate for vst plugins. It could be renamed, if course.

on_drag_start is necessary to be able to call begin_edit for vst plugins. It could be renamed, if course.

All right! I'll add it back in and see if I can find another name.

on_drag_start could be called on_press?

I wanted to propose on_grab as I thought it would be symmetrical with on_release. What do you think? Otherwise, on_press is fine! :)

Ideally, it should be implemented for all widgets. I just didn't have the need for it for any other widgets than knobs when I implemented it.

Yes, that's what I thought too. I'll had it to all widgets.

Another thing is that it would be good if it remained possible to check if the knob is currently in the dragging state.

Yes, it's still possible. Even though the State isn't fully handled by the user, pure widgets can still use an internal State. In last commit, I renamed dragging_status as is_dragging because it is now more than a boolean, but it still tracks the dragging status.
Considering the plugins requirements you mentioned, my plan is:

If user defines on_release only, call it only if a significant movement happened since the widget was "grabbed".
If user defines both on_grab and on_release, trigger both regardless of the actual movements.
Of course, user can define none of the optional callbacks, in which case only on_change is triggered when a significant movement happens.

Does this seem appropriate to you?

on_drag_start could be called on_press?

I wanted to propose on_grab as I thought it would be symmetrical with on_release. What do you think? Otherwise, on_press is fine! :)

on_grab sounds good to me.

Yes, it's still possible. Even though the State isn't fully handled by the user, pure widgets can still use an internal State. In last commit, I renamed dragging_status as is_dragging because it is now more than a boolean, but it still tracks the dragging status.

I don’t think I follow you here, is it still possible for the user to decide whether to do data updates depending on if the knob is dragging?

Considering the plugins requirements you mentioned, my plan is:

If user defines on_release only, call it only if a significant movement happened since the widget was "grabbed".
If user defines both on_grab and on_release, trigger both regardless of the actual movements.
Of course, user can define none of the optional callbacks, in which case only on_change is triggered when a significant movement happens.

Does this seem appropriate to you?

Sure, I think it would work!

is it still possible for the user to decide whether to do data updates depending on if the knob is dragging?

The user doesn't get access to is_dragging in current implementation. However the on_change callback, in which the user is supposed to update the NormalParam which is fed back to the widget, is only fired when the widget is being dragged or the mouse wheel is scrolled. An external update of the NormalParam, such as resulting from a device event or automation, won't fire on_change. Does this address your concern?

Not 100%, but it’s ok :-)

Could on_grab and on_release take closures producing messages instead of just messages?

I'm thinking of having the option of generating messages lazily. But it's not important, it can be added if needed.

The last two commits should address all the topics we discussed.

Excellent! The iced dependency still needs default-features = false, though.

The iced dependency still needs default-features = false, though.

Sorry about that. That should be fixed now.


Case sensitivity in matching dictionary objects impedes translation from Vensim

Currently the translator expects vensim keywords to be all caps: SIN, LN, etc. However, vensim allows  you to use mixed case: Sin, sin, etc.

Added some changes in the last commit to allow Capwords Case and lower case, in addition to the original UPPER CASE case. Any unusual cases (CamelCase, etc) won't work, but I think we capture most of it.
https://github.com/JamesPHoughton/pysd/blob/master/pysd/translators/vensim2py.py#L86-L96
The basic strategy is to add to the parser grammar instances of the keyword with each of the above cases, and force them to upper case before translation:
https://github.com/JamesPHoughton/pysd/blob/master/pysd/translators/vensim2py.py#L276
@BaharEs, I know you were working on something similar. Any thoughts on this implementation?

@JamesPHoughton, thanks for the update. You're right, I encountered this
problem before, and in my case, I solved the problem by adding the
lower/CamelCase worlds to the dictionary in vensim2py.py file.
More specifically, I added these exact tokens to the dictionary in
vensim2py.py: < "ln":"np.log", "Min":"min", ":OR:":"or", ":AND:":"and" >.
I'm quite sure that in my version of Vensim, "Min" function is not lower
case, neither UPPER case, and thus you would still have the same problem.
Also, please note that logical "and" & "or" appear as ":AND:" & ":OR:" in
the Vensim file, so, you may want to fix those as well.
On Mon, Sep 28, 2015 at 6:54 AM, James Houghton<EMAIL_ADDRESS>wrote:

Added some changes in the last commit to allow Capwords Case
https://docs.python.org/2/library/string.html#string.capwords and lower
case https://docs.python.org/2/library/stdtypes.html#str.lower, in
addition to the original UPPER CASE
https://docs.python.org/2/library/stdtypes.html#str.upper case. Any
unusual cases (CamelCase, etc) won't work, but I think we capture most of
it.
https://github.com/JamesPHoughton/pysd/blob/master/pysd/translators/vensim2py.py#L86-L96
The basic strategy is to add to the parser grammar instances of the
keyword with each of the above cases, and force them to upper case before
translation:
https://github.com/JamesPHoughton/pysd/blob/master/pysd/translators/vensim2py.py#L276
@BaharEs https://github.com/BaharEs, I know you were working on
something similar. Any thoughts on this implementation?
—
Reply to this email directly or view it on GitHub
https://github.com/JamesPHoughton/pysd/issues/40#issuecomment-143736361.

I think this is fixed, just need to add a test case to make sure and then close it out.

The eventual solution was to make the grammar recognize function names irrespective of case and then force the matched string to lowercase before calling the translation dictionary.
I believe this is sufficiently tested in https://github.com/SDXorg/test-models/tree/master/tests/function_capitalization, along with new unit tests.
These tests pass as of https://github.com/JamesPHoughton/pysd/commit/08468b78555d3fa52bfc840657b7dea68a8eabf7, so I'm confident this will stay fixed going forwards.


TyphoonStoryboard swift not working

Storyboard inject is not working in swift. Always I'm getting null.
I have created two Assembiles (Application and Presentation) and added into plist.
//
//  Application.swift
//

import UIKit
import Typhoon

class Application: TyphoonAssembly {

    func appDelegate() -> AnyObject {
        return TyphoonDefinition.withClass(AppDelegate.self, configuration: { definition in
            definition!.injectProperty(#selector(setter: AppDelegate.homeStoryboard), with: self.homeStoryboard())
            definition!.injectProperty(#selector(setter: AppDelegate.loginStoryboard), with: self.loginStoryboard())
        }) as AnyObject
    }

    @objc func homeStoryboard() -> AnyObject {
        return TyphoonDefinition.withClass(TyphoonStoryboard.self, configuration: { (definition) in
            definition?.useInitializer(#selector(TyphoonStoryboard.init(name:factory:bundle:)), parameters: { initializer in
                initializer!.injectParameter(with: "Home")
                initializer!.injectParameter(with: self)
                initializer!.injectParameter(with: Bundle.main)
            })
        }) as AnyObject

    }

    @objc func loginStoryboard() -> AnyObject {
        return TyphoonDefinition.withClass(TyphoonStoryboard.self, configuration: { (definition) in
            definition?.useInitializer(#selector(TyphoonStoryboard.init(name:factory:bundle:)), parameters: { initializer in
                initializer!.injectParameter(with: "Login")
                initializer!.injectParameter(with: self)
                initializer!.injectParameter(with: Bundle.main)
            })
        }) as AnyObject

    }

    @objc func aboutStoryboard() -> AnyObject {
        return TyphoonDefinition.withClass(TyphoonStoryboard.self, configuration: { (definition) in
            definition?.useInitializer(#selector(TyphoonStoryboard.init(name:factory:bundle:)), parameters: { initializer in
                initializer!.injectParameter(with: "About")
                initializer!.injectParameter(with: self)
                initializer!.injectParameter(with: Bundle.main)
            })
        }) as AnyObject

    }

}

//
//  Presentation.swift
//

import UIKit
import Typhoon

class Presentation: TyphoonAssembly {

     private var application: Application!

    func sideMenuViewController() -> SideMenuViewController? {
        return TyphoonDefinition.withClass(SideMenuViewController.self, configuration: { (definition) in
            definition?.injectProperty(#selector(setter: SideMenuViewController.homeStoryboard), with: self.application.homeStoryboard)
             definition?.injectProperty(#selector(setter: SideMenuViewController.aboutStoryboard), with: self.application?.aboutStoryboard)

        }) as? SideMenuViewController
    }

    func homeViewController() -> HomeViewController? {
        return TyphoonDefinition.withClass(HomeViewController.self, configuration: { (definition) in

        }) as? HomeViewController
    }

    func aboutViewController() -> AboutViewController? {
        return TyphoonDefinition.withClass(AboutViewController.self, configuration: { (definition) in

        }) as? AboutViewController
    }

}

//
//  AppDelegate.swift
//

import UIKit
import SlideMenuControllerSwift

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?
   @objc var  homeStoryboard  : AnyObject?
    @objc var loginStoryboard : AnyObject?

    fileprivate func createMenuView() {

        let homeViewController =  homeStoryboard?.instantiateViewController(withIdentifier: "HomeViewController") as! HomeViewController
        let sideMenuViewController = homeStoryboard?.instantiateViewController(withIdentifier: "SideMenuViewController") as! SideMenuViewController

        let nvc: UINavigationController = UINavigationController(rootViewController: homeViewController)
        UINavigationBar.appearance().tintColor = UIColor.white
        UINavigationBar.appearance().barTintColor = UIColor.darkGray

        sideMenuViewController.homeViewController = nvc

        let slideMenuController = ExSlideMenuController(mainViewController:nvc, leftMenuViewController: sideMenuViewController)
        SlideMenuOptions.contentViewScale = 1
        slideMenuController.delegate = homeViewController as? SlideMenuControllerDelegate
        self.window?.backgroundColor = UIColor(red: 236.0, green: 238.0, blue: 241.0, alpha: 1.0)
        self.window?.rootViewController = slideMenuController
        self.window?.makeKeyAndVisible()

    }

    func logout() {
        let loginViewController = loginStoryboard?.instantiateViewController(withIdentifier: "Login") as? LoginViewController

        if self.window?.rootViewController?.presentedViewController != nil {
            self.window?.rootViewController?.dismiss(animated: false)
        }

        if let loginViewController = loginViewController {
            self.window?.rootViewController?.present(loginViewController, animated: false, completion: nil)
        }
    }

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.
        self.createMenuView()
        return true
    }

    func applicationWillResignActive(_ application: UIApplication) {
        // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state.
        // Use this method to pause ongoing tasks, disable timers, and invalidate graphics rendering callbacks. Games should use this method to pause the game.
    }

    func applicationDidEnterBackground(_ application: UIApplication) {
        // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later.
        // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.
    }

    func applicationWillEnterForeground(_ application: UIApplication) {
        // Called as part of the transition from the background to the active state; here you can undo many of the changes made on entering the background.
    }

    func applicationDidBecomeActive(_ application: UIApplication) {
        // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface.
    }

    func applicationWillTerminate(_ application: UIApplication) {
        // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:.
    }

}

How inject storyboard in swift. Why homestory board object is getting null in AppDelegate?

Hm.. Your assemblies looks right from first sight. I believe it worked for objc. Try to debug it via Xcode debugger. Look at TyphoonStartup.m source, and put breakpoint at line 119. Make sure that initialFactory and initialAppDelegate are not nil and line 128 runs.


Add dependabot rules to ignore updates from .NET

PR Summary
Ignore taking update from .NET pre-release feed. .NET update should be taken only when the SDK / runtime is to be updated.
PR Context
By adding the dotnet pre-release feed to nuget.config in root, dependabot is filing PRs for every package that is published. We do not need to update for every release.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan please rebuild static

@PoshChan please rebuild all

@adityapatwardhan, successfully started rebuild of PowerShell-CI-static-analysis

@adityapatwardhan, did not find matching build context: PowerShell-CI-Windows; allowed contexts: PowerShell-CI-static-analysis


(maint) Update references from drone to harness

Following the move of the repo we have renamed links to harness

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


chore(deps): :arrow_up: update nx monorepo

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@angular-devkit/architect
0.1800.3 -> 0.1800.4

@angular-devkit/build-angular
18.0.3 -> 18.0.4

@angular-devkit/core
18.0.3 -> 18.0.4

@angular-devkit/schematics
18.0.3 -> 18.0.4

@angular/animations (source)
18.0.2 -> 18.0.3

@angular/cdk
18.0.2 -> 18.0.3

@angular/cli
18.0.3 -> 18.0.4

@angular/common (source)
^18.0.2 -> ^18.0.3

@angular/common (source)
18.0.2 -> 18.0.3

@angular/compiler (source)
18.0.2 -> 18.0.3

@angular/compiler-cli (source)
18.0.2 -> 18.0.3

@angular/core (source)
^18.0.2 -> ^18.0.3

@angular/core (source)
18.0.2 -> 18.0.3

@angular/elements (source)
18.0.2 -> 18.0.3

@angular/forms (source)
18.0.2 -> 18.0.3

@angular/language-service (source)
18.0.2 -> 18.0.3

@angular/material
18.0.2 -> 18.0.3

@angular/platform-browser (source)
^18.0.2 -> ^18.0.3

@angular/platform-browser (source)
18.0.2 -> 18.0.3

@angular/platform-browser-dynamic (source)
^18.0.2 -> ^18.0.3

@angular/platform-browser-dynamic (source)
18.0.2 -> 18.0.3

@angular/platform-server (source)
18.0.2 -> 18.0.3

@angular/router (source)
^18.0.2 -> ^18.0.3

@angular/router (source)
18.0.2 -> 18.0.3

@angular/service-worker (source)
18.0.2 -> 18.0.3

@nx/angular (source)
19.2.3 -> 19.3.0

@nx/cypress (source)
19.2.3 -> 19.3.0

@nx/devkit (source)
19.2.3 -> 19.3.0

@nx/esbuild (source)
19.2.3 -> 19.3.0

@nx/eslint (source)
19.2.3 -> 19.3.0

@nx/eslint-plugin (source)
19.2.3 -> 19.3.0

@nx/jest (source)
19.2.3 -> 19.3.0

@nx/js (source)
19.2.3 -> 19.3.0

@nx/node (source)
19.2.3 -> 19.3.0

@nx/playwright (source)
19.2.3 -> 19.3.0

@nx/storybook (source)
19.2.3 -> 19.3.0

@nx/vite (source)
19.2.3 -> 19.3.0

@nx/web (source)
19.2.3 -> 19.3.0

@nx/webpack (source)
19.2.3 -> 19.3.0

@nx/workspace (source)
19.2.3 -> 19.3.0

@schematics/angular
18.0.3 -> 18.0.4

nx (source)
19.2.3 -> 19.3.0

[!WARNING]
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

angular/angular-cli (@angular-devkit/architect)
v0.1800.4
Compare Source

angular/angular (@angular/animations)
v18.0.3
Compare Source
benchpress

Commit
Type
Description

ebf00aa0659
fix
adjust supported browser names for headless chrome (#56360)

core

Commit
Type
Description

dbd0fa00f8c
fix
async EventEmitter should contribute to app stability (#56308)

625ca3e2b3f
fix
signals should be tracked when embeddedViewRef.detectChanges is called (#55719)

localize

Commit
Type
Description

d6dd3dbdb09
fix
add @angular/localize/init as polyfill in angular.json (#56300)

migrations

Commit
Type
Description

c07e1b33569
fix
resolve error in standalone migration (#56302)

angular/components (@angular/cdk)
v18.0.3
Compare Source
material

Commit
Type
Description

f6b993fdb7
fix
dialog: Make autofocus work with animations disabled (#29195)

6dd1689b51
fix
dialog: Make focus behavior consistent across zoneful/zoneless apps (#29192)

81d4527f91
fix
radio: mark radio-group for check on touch (#29203)

0f4d1862d3
fix
schematics: estimate missing hues in M3 schematic (#29231)

faf348438d
fix
snack-bar: fix overrides mixin name typo (#29180)

nrwl/nx (@nx/angular)
v19.3.0
Compare Source

nrwl/nx (@nx/cypress)
v19.3.0
Compare Source

nrwl/nx (@nx/devkit)
v19.3.0
Compare Source

nrwl/nx (@nx/esbuild)
v19.3.0
Compare Source

nrwl/nx (@nx/eslint)
v19.3.0
Compare Source

nrwl/nx (@nx/eslint-plugin)
v19.3.0
Compare Source

nrwl/nx (@nx/jest)
v19.3.0
Compare Source

nrwl/nx (@nx/js)
v19.3.0
Compare Source

nrwl/nx (@nx/node)
v19.3.0
Compare Source

nrwl/nx (@nx/playwright)
v19.3.0
Compare Source

nrwl/nx (@nx/storybook)
v19.3.0
Compare Source

nrwl/nx (@nx/vite)
v19.3.0
Compare Source

nrwl/nx (@nx/web)
v19.3.0
Compare Source

nrwl/nx (@nx/webpack)
v19.3.0
Compare Source

nrwl/nx (@nx/workspace)
v19.3.0
Compare Source

nrwl/nx (nx)
v19.3.0
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache
Error while updating Nx Cloud client bundle

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm error code ETARGET
npm error notarget No matching version found for<EMAIL_ADDRESS>npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-07-26T14_05_43_252Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm error code ETARGET
npm error notarget No matching version found for<EMAIL_ADDRESS>npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_10_21_910Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm error code ETARGET
npm error notarget No matching version found for<EMAIL_ADDRESS>npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_10_50_584Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @nx/esbuild --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_11_17_318Z-debug-0.log

File name: package.json
Command failed: npm install --ignore-scripts
npm error code ETARGET
npm error notarget No matching version found for<EMAIL_ADDRESS>npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_11_18_015Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_11_44_244Z-debug-0.log

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache
npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-07T19_11_44_934Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
Command failed: npx nx _migrate --run-migrations --if-exists
Command failed: /tmp/tmp-18776-l20MME7LOS8U/node_modules/.bin/nx _migrate --run-migrations --if-exists

File name: package.json
temporary-error

File name: package.json
temporary-error

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
Command failed: npx nx _migrate --run-migrations --if-exists
Command failed: /tmp/tmp-29269-13P3Os8M3PP0/node_modules/.bin/nx _migrate --run-migrations --if-exists

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm warn deprecated<EMAIL_ADDRESS>This module is not used anymore, and has been replaced by @npmcli/package-json
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm warn deprecated<EMAIL_ADDRESS>V0 is gone and the best V1 polyfill is now @ungap/custom-elements
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm error code ECONNRESET
npm error network aborted
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-02T22_48_30_996Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cdk --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-02T22_49_36_897Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm warn deprecated<EMAIL_ADDRESS>This module is not used anymore, and has been replaced by @npmcli/package-json
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm warn deprecated<EMAIL_ADDRESS>V0 is gone and the best V1 polyfill is now @ungap/custom-elements
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm error code ECONNRESET
npm error network aborted
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-06T02_22_32_949Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cdk --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-06T02_23_47_252Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm warn deprecated<EMAIL_ADDRESS>This module is not used anymore, and has been replaced by @npmcli/package-json
npm warn deprecated<EMAIL_ADDRESS>You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm warn deprecated<EMAIL_ADDRESS>V0 is gone and the best V1 polyfill is now @ungap/custom-elements
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported.  Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm error code ECONNRESET
npm error network aborted
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-12T11_21_19_232Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cdk --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-12T11_22_30_091Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npm install --ignore-scripts
npm warn deprecated<EMAIL_ADDRESS>This module is not used anymore, and has been replaced by @npmcli/package-json
npm warn deprecated<EMAIL_ADDRESS>You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm warn deprecated<EMAIL_ADDRESS>V0 is gone and the best V1 polyfill is now @ungap/custom-elements
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. When upgrading to Storybook 8 with 'npx storybook@latest upgrade', you will get prompted and will get an automigration for the new package. Please migrate when you can.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported.  Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm error code EEXIST
npm error syscall rename
npm error path /home/ubuntu/.npm/_cacache/tmp/4e3af6f9
npm error dest /home/ubuntu/.npm/_cacache/content-v2/sha512/da/dd/d7b2daca50bcf8d4c34c045f9c27ded3c8777243c1c2b7ffe9a84aea0ef36353d6100676712076b5d555ec8bb17799be7f68edadb83c5d7933dd53bc6ef5
npm error errno -2
npm error ENOENT: no such file or directory, rename '/home/ubuntu/.npm/_cacache/tmp/4e3af6f9' -> '/home/ubuntu/.npm/_cacache/content-v2/sha512/da/dd/d7b2daca50bcf8d4c34c045f9c27ded3c8777243c1c2b7ffe9a84aea0ef36353d6100676712076b5d555ec8bb17799be7f68edadb83c5d7933dd53bc6ef5'
npm error File exists: /home/ubuntu/.npm/_cacache/content-v2/sha512/da/dd/d7b2daca50bcf8d4c34c045f9c27ded3c8777243c1c2b7ffe9a84aea0ef36353d6100676712076b5d555ec8bb17799be7f68edadb83c5d7933dd53bc6ef5
npm error Remove the existing file and try again, or run npm
npm error with --force to overwrite files recklessly.
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-20T09_35_08_063Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npx --no-install nx migrate @angular/cdk --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>npm error npx canceled due to missing packages and no YES option<EMAIL_ADDRESS>npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-10-20T09_36_19_195Z-debug-0.log

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate @angular/material --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>/usr/local/bin/node: line 19:  5960 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate @nx/web --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>/usr/local/bin/node: line 19: 23934 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate @nx/web --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>/usr/local/bin/node: line 19: 23928 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate @angular/core --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>/usr/local/bin/node: line 19:  3384 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate @nx/angular --from=<EMAIL_ADDRESS>--to=<EMAIL_ADDRESS>/usr/local/bin/node: line 19:  8216 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache
/usr/local/bin/node: line 19: 12559 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
/usr/local/bin/node: line 19: 12528 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
/usr/local/bin/node: line 19: 14753 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
/usr/local/bin/node: line 19: 27189 Segmentation fault      (core dumped) /opt/containerbase/tools/node/22.11.0/bin/node --use-openssl-ca "$@"


No 'Access-Control-Allow-Origin' header is present on the requested resource.

Hello,
I am using Laravel 5.4.19 and laravel-cors 0.8.4. I get following error since a few days on a specific route.
XMLHttpRequest cannot load https://domain.net/users. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:4200' is therefore not allowed access.

Every route is working properly, except /users.
/config/cors.php
<?php

return [
    /*
     |--------------------------------------------------------------------------
     | Laravel CORS
     |--------------------------------------------------------------------------
     |

     | allowedOrigins, allowedHeaders and allowedMethods can be set to array('*')
     | to accept any value.
     |
     */
    'supportsCredentials' => false,
    'allowedOrigins' => ['*'],
    'allowedHeaders' => ['*'],
    'allowedMethods' => ['*'],
    'exposedHeaders' => [],
    'maxAge' => 0,
    'hosts' => ['*'],
];

Hi @alexgaal, some time ago I faced with this problem and solved it thanks to @davidnknight's comment on #15. Search for the comment on 26 Sep 2014.
Effectively, in my case, the problem was generated by a fatal error on the controller. For the behavior you describe it may be the same issue. Check the the controller of the route /user and the PHP error log seeking for any error on that controller.

run this command
php artisan config:clear
and test again

This CORS errors are caused by fatal php errors, so issue is actually solved.

I have same error. In postman It works perfect. But when calling this api form the angular side then it gives same error as you have mentioned.

May you have a brief overview of your request headers?

Hi Guys,
I am facing  similar issue. I am using Amazon AWS and route 53.  I changed my domain name from 'api.temphawk.com' to 'api.temphawk.com/core' and now every api works fine except one 'api.temphawk.com/core/alert/history'. This api works fine when I open it on Postman but gives these errors when called from angular side.
It gives the following error in chrome.

And this error in mozilla.

Could anyone please help ?

hey i am new in angular 2 in getting  this error    XMLHttpRequest cannot load http://localhost/angulardemo/src/app/data/tododata.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:4200' is therefore not allowed access.
my service code
...............................
import { Component, OnInit } from '@angular/core'
import { Todo } from '../todo.data/todo';
import { TODOS } from '../todo.data/todo.data';
import { Injectable } from '@angular/core';
import {Http, Response} from '@angular/http';
import {Observable} from 'rxjs/Observable';
import * as _  from 'lodash';

import 'rxjs/add/operator/map';
import 'rxjs/add/observable/of';
import { jsonData } from '../data/datajson';

@Injectable()
export class HeroService {
  _url: string = jsonData.url;
  todos: Todo[] = [];
  todo: Todo;
  Data: any;
  constructor(private http: Http) {
  }
  getHeroes(): Observable<Todo[]> {
    if (this.Data) {
      return Observable.of(this.Data);
    }
    else {
      return this.http.get(this._url)
        .map((response: Response) => {
          this.Data = response.json();
          return response.json();
        })
    }
  }
  getdetail(id: number): Observable<Todo> {
    return this.getHeroes().map(
      todos => todos.find(todo => todo.id === id)[0]
    )
  }
  editData(value: Todo) {
    this.todos = _.map(this.todos, (todo) => {
      return todo;
    });
  }
  addTodo(value:Todo){
      this.Data.push(value);
  }
}

@nitdevv this has nothing to do with angular 2. The API you are calling doesn't have cors enabled in the backend. This error will vanish once cors is enabled in the API backend.

Enable service side for CORS
in spring use
@CrossOrigin(origins = "http://localhost:4200", maxAge = 3600)
@RestController
public class XYZController {
In case your angular application is running at port 4200
and you spring application is running other port say 8080
hen without enabling CORS it would not be work


Add CLI (or use sly)

A CLI for "installing" things would be nice. And could be relatively easy by using Sly CLI by @JacobParis. That comes with the benefit of sharing the maintenance burden as well.
Thoughts on a collaboration here?

I think this would be a great addition and I'd love to make it easier for folks use. Admittedly, this is something I'm not super familiar with but would happy to collab!
One thing that concerns me is that I haven't wrapped my head around is making changes in the future. Maintaining a library is not something I've done before so I'd like to make sure I have a good understanding what types of changes come with more/less risk using this approach. I haven't looked into that much.

Good idea, I dont think it would be hard to get sly up and running for now. Plus given you have kept the implementation of the components to just tailwind and not config files needed I dont think a custom CLI would even be needed at this point.
In terms of making changes in the future I dont think you need to worry. With this type of copy-paste library I think the burden is on the user to be aware of this. If you update a component they can pull in a fresh one from the cli, but need to be aware that if they have modified this themselves beyond your defaults it will be overwritten. The riskier change is if you modify the structure in some way so their existing components no longer work, but again, I think its on the user to either make the required changes or just keep the previous version of the component in their repo.

I've merged the changes so Sly users can now select Draft UI and install from there
re: ongoing updates

from a clean working tree, users can install and overwrite the components and then use the git diff view to see if there's any changes they want to port back over. This isn't ideal, but users are in charge of their own code
Sly could offer a --merge flag of some sort that would run a sort of git merge over the existing files and write the conflict markers, so the IDE would show it as a merge conflict and then users can pick/choose their changes at that time
If users are allowed to check for updates and pull in changes from the registry, then we'd need a way of storing the local "version" of each component so Sly doesn't bug people indefinitely to update. That would probably require adding a list of added files to the sly.json (similar to the "dependencies" field in a package.json)
there is a version field in each registry and in each item. Currently nothing is being done with that and they're all at 1.0.0

Thank you all so much for your help with this <3


Check readiness endpoint before pod launch

Description
Currently cni-plugin does not wait for felix (or calico node, or other endpoints) to be ready before launching pods, this sometimes causes stale conntrack entries, and hence traffic loss. This PR make cni plugin wait for an endpoint(user needs to populate the endpoint) before launching pods.

Related issues/PRs
Fixes https://github.com/projectcalico/calico/issues/4955

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

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

@caseydavenport WDYT?

Product code LGTM, so now we need a test for it. Could you add a test similar to this one:
https://github.com/projectcalico/calico/blob/4f040281d686bbb353b713c5d495e2df2a2344c4/cni-plugin/tests/calico_cni_k8s_test.go#L2516
It should do something like adding in a bogus ReadinessGate and asserting that the CNI plugin returns an error, and then another test with a valid readinessGate that asserts all is OK.
Thanks @VivekThrivikraman-est !

@coutinhop @caseydavenport When we run k8s cni tests, calico-node/felix etc would not be running, so for test with valid endpoint which endpoint can I use?

Product code LGTM, so now we need a test for it. Could you add a test similar to this one:
https://github.com/projectcalico/calico/blob/4f040281d686bbb353b713c5d495e2df2a2344c4/cni-plugin/tests/calico_cni_k8s_test.go#L2516
It should do something like adding in a bogus ReadinessGate and asserting that the CNI plugin returns an error, and then another test with a valid readinessGate that asserts all is OK.
Thanks @VivekThrivikraman-est !

@coutinhop @caseydavenport When we run k8s cni tests, calico-node/felix etc would not be running, so for test with valid endpoint which endpoint can I use?

Off the top of my head, I think running a simple http.ListenAndServe() that returns a 200 OK response in a goroutine would suffice for the test. What do you think?

Off the top of my head, I think running a simple http.ListenAndServe() that returns a 200 OK response in a goroutine would suffice for the test. What do you think?

Ok will create a dummy endpoint.

Have added Test cases for positive and negative scenario.

LGTM, just a couple of comments below...
Thanks for bearing with us @VivekThrivikraman-est! The next (and final) step would be to update the docs. I think we should add a mention to readiness_gates (and perhaps a new section explaining it) to https://projectcalico.docs.tigera.io/reference/cni-plugin/configuration (https://github.com/projectcalico/calico/blob/master/calico/reference/cni-plugin/configuration.md).
Once again, thanks!

Have added a new section explaining Readiness Gates, please check. Thanks!

/sem-approve

Pushed changes for fixing below lint error:
tests/calico_cni_k8s_test.go:3066:11: Error return value of w.Write is not checked (errcheck)05:29
w.Write([]byte("Ok"))

/sem-approve

/sem-approve

Thanks a lot @caseydavenport and @coutinhop for reviewing, guiding and merging ! Regarding operator I can give it a try.


[NVPTX] libdevice support, enable NVPTX backend in topi tests

Math function support has been missing for NVPTX backend. This PR attempts to fix the final missing piece.
All topi tests pass with nvptx backend.

@tqchen ready for a review. can you have a look?

@tqchen fixed lint and passed CI.


Rename ModelExperimental files that don't conflict with Model

This PR renames several ModelExperimental files that don't have Model counterparts:

ModelExperimental3DTileContent
ModelExperimentalAnimationChannel
ModelExperimentalArticulation
ModelExperimentalArticulationStage
ModelExperimentalDrawCommand
ModelExperimentalRuntimeNode
ModelExperimentalRuntimePrimitive
ModelExperimentalSceneGraph
ModelExperimentalSkin
ModelExperimentalStatistics
ModelExperimentalType

For all of these files, the "Experimental" part of the file / class name has been removed.

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Found a bug while I was testing (though it's happening on main too):
In the 3D Tiles Next CDB Yemen Sandcastle:

Select style buildings based on height
Switch to the Airport view
Move the camera around the area. Eventually this error will pop up:

This is the stack trace:
"Original stack:
Original stack:
Original stack:
Error
    at new DeveloperError (http://localhost:8080/Build/CesiumUnminified/index.js:11257:11)
    at Check.typeOf.number.greaterThan (http://localhost:8080/Build/CesiumUnminified/index.js:11324:11)
    at new MetadataTable (http://localhost:8080/Build/CesiumUnminified/index.js:87532:31)
    at parseFeatureMetadataLegacy (http://localhost:8080/Build/CesiumUnminified/index.js:105204:29)
    at http://localhost:8080/Build/CesiumUnminified/index.js:105350:34
    at async Promise.all (index 0)
Handler stack:
Error
    at new RuntimeError (http://localhost:8080/Build/CesiumUnminified/index.js:13876:11)
    at ResourceLoader.getError (http://localhost:8080/Build/CesiumUnminified/index.js:87690:24)
    at http://localhost:8080/Build/CesiumUnminified/index.js:105366:32
    at async Promise.all (index 0)
Handler stack:
Error
    at new RuntimeError (http://localhost:8080/Build/CesiumUnminified/index.js:13876:11)
    at ResourceLoader.getError (http://localhost:8080/Build/CesiumUnminified/index.js:87690:24)
    at handleError6 (http://localhost:8080/Build/CesiumUnminified/index.js:106215:22)
    at http://localhost:8080/Build/CesiumUnminified/index.js:106201:12
Handler stack:
Error
    at new RuntimeError (http://localhost:8080/Build/CesiumUnminified/index.js:13876:11)
    at http://localhost:8080/Build/CesiumUnminified/index.js:108229:26"

Possibly related to https://github.com/CesiumGS/cdb-to-3dtiles/issues/69?

The most common errors are related to RWID or APID pointing to empty buffer views (presumably because these features don't have this metadata). An easy fix would be to exclude these from the property table, but then these properties would need to be marked optional.

The renaming looks good, and I searched through the code to make sure nothing was missing.
Thanks @j9liu!


appearance is not implemented

SSoverlays on Nebula (and probably every other codebase) doesn't work because appearance is not implemented, meaning things like appearance copies don't work.
Implementing some features of appearance (which is apparently a /image?) would go a long way towards improving the renderer. The most important things I can think of are:

[x] Appearance reading (var/image/appearance = atom.appearance)
[x] Appearance copy (atom.appearance = appearance) (#1542)
[x] Implicit appearance copy (atom.appearance = atom) (#1542)
[ ] Appearance overlays variable access

The fourth part is still an issue.
[ERRO] world.log: Exception occurred: Invalid appearance var "overlays"
=DM StackTrace=
   /datum/controller/subsystem/zcopy/fixup_appearance_planes code/controllers/subsystems/zcopy.dm:629
   /datum/controller/subsystem/zcopy/tick_mimic code/controllers/subsystems/zcopy.dm:471
   /datum/controller/subsystem/zcopy/fire code/controllers/subsystems/zcopy.dm:224
   /datum/controller/subsystem/zcopy/Initialize code/controllers/subsystems/zcopy.dm:169
   /datum/controller/subsystem/DoInitialize code/controllers/subsystem.dm:174
   /datum/controller/master/Initialize code/controllers/master.dm:183

=C# StackTrace=
System.Exception: Invalid appearance var "overlays"
   at OpenDreamRuntime.Procs.DMProcState.ThrowInvalidAppearanceVar(String field) in c:\Users\User\phaze\OpenDream\OpenDreamRuntime\Procs\DMProc.cs:line 890
   at OpenDreamRuntime.Procs.DMProcState.DereferenceField(DreamValue owner, String field) in c:\Users\User\phaze\OpenDream\OpenDreamRuntime\Procs\DMProc.cs:line 872
   at OpenDreamRuntime.Procs.DMOpcodeHandlers.DereferenceField(DMProcState state) in c:\Users\User\phaze\OpenDream\OpenDreamRuntime\Procs\DMOpcodeHandlers.cs:line 1557
   at OpenDreamRuntime.Procs.DMProcState.Resume() in c:\Users\User\phaze\OpenDream\OpenDreamRuntime\Procs\DMProc.cs:line 415
   at OpenDreamRuntime.DreamThread.Resume() in c:\Users\User\phaze\OpenDream\OpenDreamRuntime\DreamThread.cs:line 223

if (appearance:overlays:len) is runtiming.

#2104 close this?

Fixed by #2104.


Image renderer not available for 3D only data sets

The image renderer is not selectable from the list of renderers if the data set does not contain any 2D Variables.
To reproduce:

Load the data set from Glade vapor/Bugs/2366
Try to create an Image renderer

Works with the installer, but vapor dumps core on close when running from source build

Works with the installer, but vapor dumps core on close when running from source build

I cannot reproduce this.

Nor can I. Closing.


Chart - Number of views per day

Add data for Number of views per day

https://github.com/openvitae-tech/blackboard-lms/pull/354


Build a Dataset One Example at a Time Without Loading All Data Into Memory

Is your feature request related to a problem? Please describe.
I have a very large dataset stored on disk in a custom format.  I have some custom code that reads one data example at a time and yields it in the form of a dictionary.  I want to construct a Dataset with all examples, and then save it to disk.  I later want to load the saved Dataset and use it like any other HuggingFace dataset, get splits, wrap it in a PyTorch DataLoader, etc.  Crucially, I do not ever want to materialize all the data in memory while building the dataset.
Describe the solution you'd like
I would like to be able to do something like the following.  Notice how each example is read and then immediately added to the dataset.  We do not store all the data in memory when constructing the Dataset.  If it helps, I will know the schema of my dataset before hand.

# Initialize an empty Dataset, possibly from a known schema.
dataset = Dataset()

# Read in examples one by one using a custom data streamer.
for example_dict in custom_example_dict_streamer("/path/to/raw/data"):

    # Add this example to the dict but do not store it in memory.
    dataset.add_item(example_dict)

# Save the final dataset to disk as an Arrow-backed dataset.
dataset.save_to_disk("/path/to/dataset")

...

# I'd like to be able to later `load_from_disk` and use the loaded Dataset
# just like any other memory-mapped pyarrow-backed HuggingFace dataset...
loaded_dataset = Dataset.load_from_disk("/path/to/dataset")
loaded_dataset.set_format(type="torch", columnns=["foo", "bar", "baz"])
dataloader = torch.utils.data.DataLoader(loaded_dataset, batch_size=16)
...

Describe alternatives you've considered
I initially tried to read all the data into memory, construct a Pandas DataFrame and then call Dataset.from_pandas.  This would not work as it requires storing all the data in memory.  It seems that there is an add_item method already -- I tried to implement something like the desired API written above, but I've not been able to initialize an empty Dataset (this seems to require several layers of constructing datasets.table.Table which requires constructing a pyarrow.lib.Table, etc).  I also considered writing my data to multiple sharded CSV files or JSON files and then using from_csv or from_json.  I'd prefer not to do this because (1) I'd prefer to avoid the intermediate step of creating these temp CSV/JSON files and (2) I'm not sure if from_csv and from_json use memory-mapping.
Do you have any suggestions on how I'd be able to achieve this use case?  Does something already exist to support this?  Thank you very much in advance!

Hi! Yes, the problem with add_item is that it keeps examples in memory, so you are left with these options:

writing a dataset loading script in which you iterate over custom_example_dict_streamer and yield the examples (in _generate examples)
storing the data in a JSON/CSV/Parquet/TXT file and using Dataset.from_{format}
using add_item + save_to_disk on smaller chunks:from datasets import Dataset, concatenate_datasets
MAX_SAMPLES_IN_MEMORY = 1000
samples_in_dset = 0
dset = Dataset.from_dict({"col1": [], "col2": []})  # empty dataset
path_to_save_dir = "path/to/save/dir"
num_chunks = 0
for example_dict in custom_example_dict_streamer("/path/to/raw/data"):
    dset = dset.add_item(example_dict)
    samples_in_dset += 1
    if samples_in_dset == MAX_SAMPLES_IN_MEMORY:
        samples_in_dset = 0
        dset.save_to_disk(f"{path_to_save_dir}{num_chunks}")
        num_chunks =+ 1
        dset = Dataset.from_dict({"col1": [], "col2": []})  # empty dataset
if samples_in_dset > 0:
    dset.save_to_disk(f"{path_to_save_dir}{num_chunks}")
    num_chunks =+ 1
loaded_dsets = []  # memory-mapped
for chunk_num in range(num_chunks):
    dset = Dataset.load_from_disk(f"{path_to_save_dir}{chunk_num}")
    loaded_dsets.append(dset)
final_dset = concatenate_datasets(dset)

If you still have issues with this approach, you can try to delete unused datasets with gc.collect() to free some memory.

This is really elegant, thank you @mariosasko!  I will try this.


Adding font property to allow non-system font's to be used

I needed the ability to change the font being used in the toast. If no font is specified, it will still use the system font.

This is great, thanks :)

Custom styling is supported in Toast 3.0.


Fix blank events in first login

In the #155 commit, there is a missing cleanup "status=unauthorized"

Good catch!
Thanks a lot


Add the Quick Start guide

Creates a sample quickstart the users could follow

Submitter checklist

[x] The PR request is well described and justified, including the body and the references
[x] The PR title represents the desired changelog entry
[x] The repository's code style is followed (see the contributing guide)
[x] Test coverage that demonstrates that the change works as expected
[x] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

Seeps to be the Ryuk issue:

Will YOLOmerge it, need the documentation links & works on my machine


[ROCm] Adding a macro wrapper for the ROCm/CUDA routine to get the error string

This PR adds a macro wrapper GPU_GET_ERROR_STRING that resolves to the GPU platform specific error string function.
I tdo not know whether or not, the name GPU_GET_ERROR_STRING conforms to the TF coding standards, and any suggestions to change it something more conforming/consistent are welcome.
This is a trivial change, please review and merge....thanks

@tatianashp @whchung @chsigg

@chsigg gentle ping
also thank you for all the PRs you have merged so far.

@chsigg this PR seems to have gotten stuck in the merge pipeline :(