UpdateLocation not working on real mode

Hey,
I get error {routing context :100} when testing UpdateLocation in real mode.
is there an issue on the core ?
Thx

no its from sigploit, it shall be updated tonight
essentially routing context is provided as a parameter from your provider and should be the same in the request

does sigploit work on live ? i'm new here @brad7172 @SigPloiter

Some Map Ops. are fine but some others still need to be fixed.
It will be updated tonight @pinoccio00

Any update @SigPloiter ?
P.S: I have found more issues on the stacks.

if you find issues then post it to know it

Lets update the code first to know if you have resolve them, only then i can re-test and see if it was related or not.
You told us that yesterday night you will make a new release, i don't see any update.

this is not a blog, this is to open issues so if you have issues upload
logs that supports your claims, so fixing happens at once.
you will see the updates when they are ready
On Sun, Jun 23, 2019 at 6:08 PM brad7172<EMAIL_ADDRESS>wrote:

Lets update the code first to know if you have resolve them, only then i
can re-test and see if it was related or not.
You told us that yesterday night you will make a new release, i don't see
any update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/176?email_source=notifications&email_token=AF265PZBV5OEEBRCXRSXGTLP36NWHA5CNFSM4H2WYGTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLBX2I#issuecomment-504765417,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF265P6GHIJYBYXOVPABKBLP36NWHANCNFSM4H2WYGTA
.

its updated now
and if you have any issues it will be good to contribute and provide them otherwise they are just claims, so it will be good to contribute with issues or just wait till updated releases

boss please i really need your help i want to hear from you<EMAIL_ADDRESS>


UI bugs inside tab Inspect > Graph inspect id

Current situation:

The list is behind the controls of the tab itself. Running under Grafana 7.0.6 and plugin 0.9.0. This function cannot be used as it is.

thx for your report, i'll fix it

Same issue. Running on mac. Tried Grafana 6 and Grafana 7. Tried on different versions of grafana-flowcharting, and on different browsers (Chrome, Firefox, and Safari). Really hard to use without being able to link fields through UI.

I have not found a work around, tried to zoom and do some other things but no luck

Fix in progress
Le mer. 21 oct. 2020 à 19:55, majerus1223<EMAIL_ADDRESS>a
écrit :

I have not found a work around, tried to zoom and do some other things but
no luck
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/algenty/grafana-flowcharting/issues/209#issuecomment-713751750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALGVW5LE2BP7GENFFYZHMFDSL4N75ANCNFSM4PDSFXPA
.

--
Arnaud GENTY
Responsable et Ingénieur de production IT (SAP/J2EE).
Tel : (+33)<IP_ADDRESS>.14
Email<EMAIL_ADDRESS>

Thank you very much!

Fixed at https://algenty.github.io/flowcharting-repository/ARCHIVES.html
Need feedback

Let me try to install this in grafana cloud

Finally was able to get this installed, our instance has problems installing a manual version. Looks good thanks!

When installing the plugin available on github, grafana disables due to the subscription, I'm a beginner and I don't have much knowledge with linux, if someone can provide a tutorial on the correction (installation) of the bug, thank you


test: split up ClangImporter.enum-anon

This splits up the test into two halves in order to allow the test to
pass on Windows.  Loosen the test to allow the enumeration to be
imported with signed and unsigned types as Windows uses signed
enumerations by default.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@jrose-apple - okay, split up the test and set it up so that it passes on Windows as well

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


[Feature] Rational Function Analyzer

Description
The Rational Function Analyzer is a specialized tool designed to provide detailed insights into the properties of rational functions, which are mathematical expressions formed by the ratio of two polynomials. This analyzer is particularly useful for students, mathematicians, and engineers who need to explore the behavior of these functions for academic, research, or practical applications.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Please assign me this issue.

@divyansh-2005 this is basically a fraction analyzer, correct?

yes

Pls review this @jessicachawla

Exactly, hence closing the issue @divyansh-2005 @jessicachawla


DateTime(5) when formatted to display Weekday indicating wrong output

DateFormat('EEEE').format(DateTime(int))  Indicating wrong output when integer is 5.
Expected output for DateFormat('EEEE').format(DateTime(5)) is Friday.
Received output - Saturday
for (int index = 1; index <= 7; index++) {       print(DateFormat('EEEE').format(DateTime(index)).toString());     }

Hi Team, even am facing this issue in my project-due for release next week. Can you please let me know the fix if any at the earliest. Thanks in advance.

Hi @AksharPrasanna
Can you please provide your flutter doctor -v, your pubspec.yaml and a minimal complete reproducible code sample?
Thank you

Thank you @pedromassangocode
Please find the details below -

Output of flutter doctor -v
[✓] Flutter (Channel stable, 1.20.3, on Mac OS X 10.15.5 19F101, locale en-IN)
    • Flutter version 1.20.3 at /Users/aksharprasanna/projects/flutter
    • Framework revision 216dee60c0 (13 days ago), 2020-09-01 12:24:47 -0700
    • Engine revision d1bc06f032
    • Dart version 2.9.2

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/aksharprasanna/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/aksharprasanna/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[!] Xcode - develop for iOS and macOS (Xcode 11.7)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.7, Build version 11E801a
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        sudo gem install cocoapods

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.0

[✓] Connected device (1 available)
    • ONEPLUS A6010 (mobile) • 175572d • android-arm64 • Android 10 (API 29)

! Doctor found issues in 2 categories.

pubspec.yaml
name: dateTime_issue
description: A new Flutter project.

publish_to: 'none'

version: 1.0.0+1

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  intl: ^0.16.1
  flutter:
    sdk: flutter
  cupertino_icons: ^0.1.3

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

Sample Code
import 'package:flutter/material.dart';
import 'package:intl/intl.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);
  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            for (int index = 0; index < 40;index ++)
              Text('DateFormat(\'EEEE\').format(DateTime(${index})) - ' +
                  DateFormat('EEEE').format(DateTime(index)).toString()),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ),
    );
  }
}

Hi @AksharPrasanna
From what I can see, the issue is related to a Dart language plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you


CentOS 7 timeout issue re-appears.

Getting a consistent timeout check when running against a local vagrant CentOS7 box. It's dying on the httpd -t syntax check. I was successfully able to repeat the command timeout from the command line after logging in to the vagrant box. I clocked it as taking nearly 30 seconds to return from the command line. I fixed it by adding a global ServerName directive in the httpd.conf file:
ServerName <IP_ADDRESS>
What's happening is that when doing a syntax check on a config, the system is trying to come up with a fully-qualified domain name for the server, so you're stuck waiting for a dns lookup that fails.
http://linux.101hacks.com/unix/httpd-apr-sockaddr-info-get-error/ pointed me in the right direction for a fix.
Lots of options: create a servername.conf file in conf-available; write it directly in httpd.conf; or maybe create a sites-available file template without a virtual host directive to set it up. (I think I'll probably do that last as a workaround for now, until I see if you find a better way to do it.)

Never mind. Cranial flatulence. That last won't work because the first time the timeout happens is before any of the site config files get written. So it has to be done while writing the main config file(s).

Not sure if I completely agree with this being an issue. If you aren't using a real FQDN/something with DNS, you can also just put an entry in your hosts file.
Did you have a suggestion for how the cookbook could address this without doing hacky stuff?

If "hacky stuff" was better defined I'd have a shot at answering the question, but here's a few ideas. You decide how many of them are too 'hacky' to be permitted.
a) Include a ServerName <IP_ADDRESS> directive in the global area of the file.
b) If the cookbook user adds a "server_name" attribute to the apache node, write it out in the global file.
There are varying degrees of "hack" in both of those, with the second having the purist's advantage of only being present if the user wants/needs it there. And if you seriously want to keep the httpd.conf file genetically pure, you could take either of those two ideas above and refocus the output file, maybe using servername.conf instead of the main config file, and park it in the optional extra conf files dir. (That was actually what I did to get around the delay when I was checking it from the command line.)
When I get the chance today I'm going to look for a way to force the creation of a servername.conf file before the cookbook calls httpd -t for the first time (it escaped me the first time, but just because I didn't see it, doesn't mean it doesn't exist; I've had attacks of 'code blindness' before) because that seems to me to be the only way I might be able to solve this myself this side of forking the cookbook for my own use.
And when I'm (re)building production servers I do have FQDN's around. But sometimes I want to spin up a box (inside my desktop or in the cloud) just to try out an idea and see if it's going to be feasible. It's for those ad hoc use cases where fixing this would be useful. I know it's an edge case, but it's still useful.

I was thinking about this some more, and I realized why we haven't seen this issue in our own tests (not recently, anyway) - https://github.com/svanzoest-cookbooks/apache2/blob/master/.kitchen.yml#L60
We use the fqdn cookbook to solve this when testing in vagrant/test-kitchen type environments.

@Paladin as far as 'hacky' goes, I just wouldn't want anything to be added to the cookbook that could potentially filter into a production environment - existing users shouldn't have to change their workflows to avoid whatever addition is made.

Hmmm. I'll have a look and see if it'll do what I need for this.

Hmm. If my understanding is correct (not always a certainty) the fqdn cookbook solves my issue, but I had to use it slightly differently than you did. You included it in the definitions for the test suite, I need to include it in the platform, because both the tests and the build fail without it. So I added it to the CentOS 7 platforms. I think I need it for the Ubuntu 15 image I'm working with, too, but that's from my cloud provider, not opscode, so it's too early to say if it's needed there, as well.
I may pull it out and  manually include the recipe, eventually, simply because it may not be needed on anything but these test boxes; for the moment that's what I'm building in C7 and U15, so I'll jump that bridge when it gets to me.


Contact DMO for logistics (AMD ELDP)

W/ KEVIN G
--- Cloud one we're not fully ready for, so we will need a local thing
--- Jotunheimr (kafka, dockers, etc) running in cloud (if and how omar can do that). We need to use the one that we're certain work (rather than just confluent packages, but we cant control them fully)
--- If we can revise: 1. Dynamically Create a View of Material UI components insert into the tree.

Local deployment version ready per Nghia. If we need to local demo we can, but we're getting close on the CORTEX integration. If we can nail down the last cloud pieces we will be in good shape.

Running with ALDP survey until otherwise informed


global search cant find the file in .git

vscode:1.52.1
os: macos 11.1
global search cant find the file in .git
// conf in user setting, workspace dont reset this conf
"search.exclude": {
    "**/node_modules": true,
    "**/bower_components": true,
    "output": true,
    "**/CVS": true,
    "**/.git": true,
    "**/.svn": true
},
"files.exclude": {
    ".*": false,
    "**/CVS": true,
    "*.a": true,
    "**/a.out": true,
    "**/.DS_Store": true,
    "**/.git": true,
    "**/.hg": true,
    "*.o": true,
    "*.so": true,
    "**/.svn": true
},

You can set "search.useIgnoreFiles": false

You can set "search.useIgnoreFiles": false

the problem is "search.exclude" is not effect( "**/.git": true,).
"search.exclude": {
    "**/node_modules": true,
    "**/bower_components": true,
    "output": true,
    "**/CVS": true,
    "**/.git": true,
    "**/.svn": true
},

If you want to search in .git, you need to set that to false

make it enable, "search.exclude" will effect.

make it enable, "search.exclude" will effect.

If you want to search in .git, you need to set that to false

ensure it enable, "search.exclude" will effect.

If you want to search in .git, you need to set that to false

ensure it enable, "search.exclude" will effect.


make shap play nicer with sklearn<0.18

an alternative is to pin sklearn >= 0.18, otherwise there are some import errors with older versions

Thanks!


Paginate

We need to do this in the web client. Investigate what that would entail

For next meeting, @acoffman to come up with an estimate for effort on this.


feat(blog): created initial blog page

Fixes https://github.com/BitByte-TPC/alumni/issues/162
Description:-

This PR creates a blog page

@ANIRUDHNARANG0 Please remove all files except the HTML templates. Views, models, and files are being handled in other issues. Also, refactor your blog page logic according to the views in PR #161

@ANIRUDHNARANG0 Please resolve conflicts. Shift the entire content to home.html in blog folder. Also, please refactor your design. You don't have to just throw elements in the page. Take inspiration from /jobs for search bar and card design. Also, remove the 'want to start a new blog' line.


Azure DevOps Plugin - Pull Request Dashboard PullRequestsDashboardProvider loading teams at startup

Expected Behavior
Azure DevOps plugin will start in ~1s
Actual Behavior
The whole backend service waits till the PullRequestsDashboardProvider loads all teams&projects from Azure DevOps which

creates unnecessary depenency: consider Azure DevOps service returns http 503 (as it often throws) or is not available for a long time..it will "screw" backstage environment on startup... am I right?
takes really long time.. e.g. like tens of seconds in our environment to load as we have lots of projects and lots of teams ...then it sometimes ends up wit error like azure-devops warn Failed to load azure team information, Error: connect ETIMEDOUT <IP_ADDRESS>:443 type=plugin

Steps to Reproduce
Configure  azure devops plugin, have tens of projects, tens of teams, start the backend...and wait...and wait..
Context
The pod needs to start as quickly as it can. No single plugin shall be as slow as this... or is this an issue with local development only?
Your Environment
OS:   Linux <IP_ADDRESS>-microsoft-standard-WSL2 - linux/x64
node: v16.10.0
yarn: 1.22.5
cli:  0.14.0 (installed)

Dependencies:
  @backstage/app-defaults                                  0.1.8
  @backstage/backend-common                                0.10.9
  @backstage/backend-tasks                                 0.1.8
  @backstage/catalog-client                                0.7.1
  @backstage/catalog-model                                 0.10.1
  @backstage/cli-common                                    0.1.8
  @backstage/cli                                           0.14.0
  @backstage/config-loader                                 0.9.5
  @backstage/config                                        0.1.15
  @backstage/core-app-api                                  0.5.3
  @backstage/core-components                               0.8.9
  @backstage/core-plugin-api                               0.6.1
  @backstage/dev-utils                                     0.2.22
  @backstage/errors                                        0.2.2
  @backstage/integration-react                             0.1.22
  @backstage/integration                                   0.7.4
  @backstage/plugin-api-docs                               0.7.3
  @backstage/plugin-app-backend                            0.3.26
  @backstage/plugin-auth-backend                           0.10.2
  @backstage/plugin-auth-node                              0.1.2
  @backstage/plugin-azure-devops-backend                   0.3.5
  @backstage/plugin-azure-devops-common                    0.2.2
  @backstage/plugin-azure-devops                           0.1.15
  @backstage/plugin-badges-backend                         0.1.20
  @backstage/plugin-badges                                 0.2.23
  @backstage/plugin-catalog-backend                        0.21.5
  @backstage/plugin-catalog-common                         0.1.4
  @backstage/plugin-catalog-graph                          0.2.11
  @backstage/plugin-catalog-graphql                        0.3.3
  @backstage/plugin-catalog-import                         0.8.2
  @backstage/plugin-catalog-react                          0.6.15
  @backstage/plugin-catalog                                0.8.0
  @backstage/plugin-circleci                               0.2.38
  @backstage/plugin-cloudbuild                             0.2.36
  @backstage/plugin-code-coverage-backend                  0.1.24
  @backstage/plugin-code-coverage                          0.1.26
  @backstage/plugin-cost-insights                          0.11.21
  @backstage/plugin-explore-react                          0.0.12
  @backstage/plugin-explore                                0.3.30
  @backstage/plugin-gcp-projects                           0.3.18
  @backstage/plugin-github-actions                         0.4.36
  @backstage/plugin-graphiql                               0.2.31
  @backstage/plugin-graphql-backend                        0.1.16
  @backstage/plugin-home                                   0.4.15
  @backstage/plugin-jenkins-backend                        0.1.15
  @backstage/plugin-jenkins                                0.5.21
  @backstage/plugin-kafka-backend                          0.2.19
  @backstage/plugin-kafka                                  0.2.29
  @backstage/plugin-kubernetes-backend                     0.4.9
  @backstage/plugin-kubernetes-common                      0.2.4
  @backstage/plugin-kubernetes                             0.5.8
  @backstage/plugin-lighthouse                             0.2.38
  @backstage/plugin-newrelic                               0.3.17
  @backstage/plugin-org                                    0.4.3
  @backstage/plugin-pagerduty                              0.3.26
  @backstage/plugin-permission-backend                     0.5.1
  @backstage/plugin-permission-common                      0.5.1
  @backstage/plugin-permission-node                        0.5.1
  @backstage/plugin-permission-react                       0.3.1
  @backstage/plugin-proxy-backend                          0.2.20
  @backstage/plugin-rollbar-backend                        0.1.23
  @backstage/plugin-rollbar                                0.3.27
  @backstage/plugin-scaffolder-backend-module-cookiecutter 0.2.1
  @backstage/plugin-scaffolder-backend-module-rails        0.3.1
  @backstage/plugin-scaffolder-backend                     0.16.1
  @backstage/plugin-scaffolder-common                      0.2.1
  @backstage/plugin-scaffolder                             0.12.3
  @backstage/plugin-search-backend-module-elasticsearch    0.0.10
  @backstage/plugin-search-backend-module-pg               0.2.8
  @backstage/plugin-search-backend-node                    0.4.7
  @backstage/plugin-search-backend                         0.4.4
  @backstage/plugin-search                                 0.7.0
  @backstage/plugin-sentry                                 0.3.37
  @backstage/plugin-shortcuts                              0.2.0
  @backstage/plugin-sonarqube                              0.2.17
  @backstage/plugin-tech-insights-backend-module-jsonfc    0.1.10
  @backstage/plugin-tech-insights-backend                  0.2.6
  @backstage/plugin-tech-insights-common                   0.2.3
  @backstage/plugin-tech-insights-node                     0.2.4
  @backstage/plugin-tech-insights                          0.1.9
  @backstage/plugin-tech-radar                             0.5.6
  @backstage/plugin-techdocs-backend                       0.13.5
  @backstage/plugin-techdocs                               0.13.4
  @backstage/plugin-todo-backend                           0.1.23
  @backstage/plugin-todo                                   0.2.1
  @backstage/plugin-user-settings                          0.3.20
  @backstage/release-manifests                             0.0.2
  @backstage/search-common                                 0.2.4
  @backstage/techdocs-common                               0.11.9
  @backstage/test-utils                                    0.2.5
  @backstage/theme                                         0.2.15
  @backstage/types                                         0.1.3
  @backstage/version-bridge                                0.1.2

@jvilimek thanks for the creating this issue, I don't have the same scale as you so have not noticed this.
@marleypowell do you have any ideas what we could do to improve this?

@jvilimek thanks for the creating this issue, I don't have the same scale as you so have not noticed this.
@marleypowell do you have any ideas what we could do to improve this?

I think we could use new PullRequestsDashboardProvider instead of PullRequestsDashboardProvider.create so that teams are only loaded when they are first required.
https://github.com/backstage/backstage/blob/master/plugins/azure-devops-backend/src/service/router.ts#:~:text=const pullRequestsDashboardProvider %3D,create(logger%2C azureDevOpsApi)%3B

Thanks a lot guys! How can I help? Shall I test the change once ready?
There might still be issues with the timeouts when loading projects/teams from DevOps even when it is loaded for the first time ("on demand") even outside of the startup. Maybe some per-project/partial load would help as well.. How can I isolate the readTeams routine to test it in our environment? As I guess it would be quite long running in our environment... just checked and we have 83 projects, 815 users, not sure about how many teams accross the projects...

Yeah it might even warrant being broken apart into smaller request bites, it sounds like (depending on what the client request patterns look like). Either way, caching old results and presenting stale data while revalidating in the background might also be worth it? We have a couple such data providers actually in our internal instance. They periodically go fetch data from heavy / slow sources and throw the condensed results in a memcache, from which we have lightning fast accesses to the frontend

@marleypowell Hi there. Long time no activity here. In the mean time I have disabled the azure devops in our instance. Any hope this can be fixed/improved soon?

@marleypowell Hi there. Long time no activity here. In the mean time I have disabled the azure devops in our instance. Any hope this can be fixed/improved soon?

Hi sorry I've been quite busy. I will try and find time to have a look tommorow.

@jvilimek I've done a fix to solve the initial load problem but I am still looking into chunking requests to solve this problem:

There might still be issues with the timeouts when loading projects/teams from DevOps even when it is loaded for the first time ("on demand") even outside of the startup.

Thanks a lot, I will try to give it a try soon


[GHI] Fix/lis75 nrt streamflow

Description
Added routing to AGRMET Ops mode, and added "557WW streamflow convention" option for output

This PR compiles with intel (strict checks) and gnu (-g).


Run id file should be written prior to execution when resuming

This matches behavior for a non-resume (regular flow.py run).  This way is simply more useful, following user feedback.
Core test added.

@romain-intel NFLX tests show one failure.  Could you please confirm if things are OK with this change?


squirrel has a spelling error in it's abilities effect

api.json
.pets."pet-squirrel".level1Ability.effect.amount is incorrectly spelled ammount

#34 solves this


Fix terminal client local file hosting

Please sign our contributor license agreement at https://cla.futo.org

.

@MAlba124 I see you in the db, not sure what went wrong with the bot, sorry about that

LGTM, thanks for the contribution.
Merged for next release in branch v3: https://github.com/futo-org/fcast/commit/1cd91f91e97581428be1eddb9f94e3f083ed7528