I am also lacking the option "Edit Session"
Hello fossasians !!
I am Ayush final year undergrad ,passionate , techy & hacker at heart .Finding my way through life.
I would love to learn alongside you and forgive me if i do mistakes.
around here and hoping to contribute to open-event-server and may be get a full time role.
This is the error msg.
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: open-event-frontend -> ember-g-map -> ember-cli-babel
Running without permission to symlink will degrade build performance.
See https://cli.emberjs.com/release/appendix/windows/ for details.
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-g-map\node_modules\ember-cli-babel
app/sentry.ts:17:9 - error TS2783: 'tracesSampleRate' is specified more than once, so this usage will be overwritten.
17 tracesSampleRate: config.sentry.tracesSampleRate,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ app/sentry.ts:37:9
37 ...config.sentry
~~~~
This spread always overwrites this property.
| building... [Bundler][BABEL] Note: The code generator has deoptimised the styling of C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\paypal-checkout\dist\checkout.lib.js as it exceeds the max of 500KB.
ENOENT: no such file or directory, scandir 'C:\Users\lenovo\AppData\Local\Temp\broccoli-16896bNweEX1Qtb9F\out-905-broccoli_merge_trees\assets\locales'
Stack Trace and Error Report: C:\Users\XXXX\AppData\Local\Temp/error.dump.bbca52422ebee0795519b710f29dc246.log
(node:16896) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, scandir 'C:\Users\lenovo\AppData\Local\Temp\broccoli-16896bNweEX1Qtb9F\out-905-broccoli_merge_trees\assets\locales'
at Object.readdirSync (fs.js:872:3)
at Class.postBuild (C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-l10n\index.js:146:20)
at Class.superWrapper [as postBuild] (C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-cli\node_modules\core-object\lib\assign-properties.js:34:20)
at C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-cli\lib\models\builder.js:152:28
at Array.reduce (<anonymous>)
at Builder.processAddonBuildSteps (C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-cli\lib\models\builder.js:149:43)
at Builder.build (C:\Users\lenovo\Documents\Fossasia\open-event-frontend\node_modules\ember-cli\lib\models\builder.js:209:18)
(node:16896) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:16896) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
cleaning up...
<div class="inline feild">
<label for="location">{{t 'Location'}}</label>
<div class="ui checked checkbox">
<Input
@type="checkbox"
@checked="pre_checked"/>
</div>
</div>
<Widgets::Forms::LocationInput
@inputId="location"
@lat={{this.data.event.latitude}}
@lng={{this.data.event.longitude}}
@placeName={{this.data.event.locationName}}
@searchableName={{this.data.event.searchableLocationName}}
@zoom={{15}}
{{!--@placeholder={{t "Location is required to make this event live"--}}>
@iamareebjamal Added info.
Regarding fossasia/open-event-frontend#4604 let's have a short call. Generally the best would be if we have a proper implementation. But, I wonder inhowfar indepth migrations are needed apart from ensuring the database are intact. In regards storage of email notifications, we have not really used this feature extensively. So, there would not be data loss if you think things could be simplified in the migrations process. But, my knowledge here is limited. Does this make sense at all?
