ERROR with UglifyJs when building npm start build:prod

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
Do you want to request a feature or report a bug?
Uglify gives an ERROR when running npm run build:prod
`
ERROR in 1.87152edfeeca0e76c2dd.chunk.js from UglifyJs
SyntaxError: Unexpected token: name (Detail) [./~/angular2-template-loader!./src/app/+detail/detail.component.ts:13,0]

ERROR in 2.d14d91212c6668d117ed.chunk.js from UglifyJs
SyntaxError: Unexpected token: name (About) [./~/angular2-template-loader!./src/app/about/about.component.ts:29,0]
ERROR in main.7ef34497f05b466f628b.bundle.js from UglifyJs
SyntaxError: Unexpected token: name (App) [./~/angular2-template-loader!./src/app/app.component.ts:61,0]
`
npm run build:dev works fine and the only file I've changed is tsconfig.json with target: "es6" because of another bug

What is the current behavior?
Can't uglify the main.bundle.js
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
I changed the tsconfig.json - target: "es6" because it's not recognizing "Set" and others es6 then I did a npm run build:prod :
`
ERROR in 1.87152edfeeca0e76c2dd.chunk.js from UglifyJs
SyntaxError: Unexpected token: name (Detail) [./~/angular2-template-loader!./src/app/+detail/detail.component.ts:13,0]

ERROR in 2.d14d91212c6668d117ed.chunk.js from UglifyJs
SyntaxError: Unexpected token: name (About) [./~/angular2-template-loader!./src/app/about/about.component.ts:29,0]
ERROR in main.7ef34497f05b466f628b.bundle.js from UglifyJs
SyntaxError: Unexpected token: name (App) [./~/angular2-template-loader!./src/app/app.component.ts:61,0]
`

What is the expected behavior?
To uglify the main.[hash].bundle.js
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Mac OS X El Capitan
Angular version: 2.0.0-beta.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

I changed the tsconfig.json - target: "es6" because it's not recognizing "Set" and others es6
I encounter the same issue when including a 3rd party library which is build in es6.

I can reproduce this as well.

Same here. Setting target to es5 works as workaround.

Installing the npm package: typescript@rc and setting the target: "es5" in tsconfig.json solved it for me..
Problem was I couldn't use target: "es5" because my project is using async / await.. But with the new 2.1 version of Typescript it is supported

I've got the same issue when trying to change target to ES6.

Confirming this as well. I am using ES6 target for async/await support, and that causes UglifyJS to fail. Setting ES5 target with Typescript 2.0.10 breaks the async/await... So I'm between a rock and a hard place here.
I'm trying to get things working with newer Typescript.

"I'm trying to get things working with newer Typescript."
Build works with Typescript 2.1.5 & ES5 Target BUT async/await doesn't work!
"__generator is not defined"
__generator is part of async/await code generated by Typescript when the target is ES5 or ES3.
Disabling UglifyJS completely allows production builds with ES6 target, so that's what I'm currently doing as a workaround. Might still test ES5 target with manually copy & pasted __generator and __awaiter from https://blog.mariusschulz.com/2016/12/09/typescript-2-1-async-await-for-es3-es5

I found a solution by using babel. ES6 Typescript -> JavaScript es6 -> babel -> es5.

Workaround with TS 2.1 & ES5 target without babel is to copy & paste __generator & __awaiter vars to index.html or other place to be included on global scope. I tested it and it's indeed working.
Get the code from the following link:
https://blog.mariusschulz.com/2016/12/09/typescript-2-1-async-await-for-es3-es5
Feels a bit dirty but works. Honestly, I think that using babel with TS would be even bigger sin.

please i keep getting this error, how can i resolve this??
Error: No errors
at validate (C:\Users\Adebowale\myauthapp\node_modules\extract-text-webpack-plugin\schema\validator.js:10:9)
at Function.ExtractTextPlugin.extract (C:\Users\Adebowale\myauthapp\node_modules\extract-text-webpack-plugin\index.js:188:3)
at C:\Users\Adebowale\myauthapp\node_modules\angular-cli\models\webpack-build-styles.js:79:83
at Array.map (native)
at Object.getWebpackStylesConfig (C:\Users\Adebowale\myauthapp\node_modules\angular-cli\models\webpack-build-styles.js:76:43)
at new NgCliWebpackConfig (C:\Users\Adebowale\myauthapp\node_modules\angular-cli\models\webpack-config.js:44:51)
at Class.run (C:\Users\Adebowale\myauthapp\node_modules\angular-cli\tasks\serve-webpack.js:23:22)
at C:\Users\Adebowale\myauthapp\node_modules\angular-cli\commands\serve.run.js:37:22
at process._tickCallback (internal/process/next_tick.js:103:7)

UglifyJsPlugin only supports es5 now, so change file tsconfig.json like below:
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "es6"]
  }
}

this config will make build program solve this problem like SyntaxError: Unexpected token: name (App) ,and also be able to recognize "Set" and others es6.

https://webpack.js.org/plugins/uglifyjs-webpack-plugin/

Looks like fixed. Ive just removed all the ts files from my project


expand the cells from the beginning,

Is there any way to expand the cells from the beginning, without crashing due beginUpdate/endUpdates?

Don't reload the cell which is not visible will prevent from crashing.


Ubuntu WSL via Microsoft Store appears to have trashed Windows boot

So I'm having a rather bad day:

Had LXSS installed since the beta in Windows 10 Anniversary Edition. (Ubuntu Trusty). It was working fine.
Needed a newer distro, went to the Microsoft Store to install Ubuntu Xenial. I didn't wipe my old LXSS stuff with lxrun. Wasn't logged into a MS Account.
Installed it and ran the new command line shortcut and it displayed "Please wait, installing" or something to that effect. Hung there for hours, no CPU, network or disk activity. Closed the window to try a reboot.
Windows has been failing to boot since. It hangs on a black screen after the logo comes up, but before the logon prompt. There's a busy mouse cursor I can still move around. It's using both displays so the video driver has loaded. Unresponsive to keyboard input.
I've tried all the options on the recovery disk except for reinstalling Windows. The only System Restore point I have fails to restore the file:
E:\Users\craig\AppData\Local\lxss\rootfs\usr\lib\perl\5.18.2\sys\cdefs.ph
This restore point is from before the new Ubuntu.
chkdisk reports no errors on the drive. MBR is an ordinary windows one, and I ran the startup repair in any case. Hardware hasn't exhibited any other symptoms, has been well behaved running the recovery DVD. Haven't tested the memory yet.
This cdefs.ph doesn't already exist in the FS. The disk has plenty of space.

My next step is to reinstall the OS, but I don't imagine that'll leave you with much to diagnose. I'd be grateful for any troubleshooting tips here (particularly how to get to the event log from a recovery DVD command prompt), but I'm gonna need to press the machine back into service before terribly long so I'd appreciate a prompt response.

Your Windows build number:  (Type ver at a Windows Command Prompt)

April 2018 Update as of 3 days ago. Ver reports 10.0.10586, but that'll just be the recovery DVD.

You'll have to either restore prior to installing Ubuntu from the Store (recommended) or reinstall. You're unable to install both the Store version and the depreciated lxrun version. You must fully uninstall with lxrun /uninstall /full, reboot, and then install from the Store. I also recommend restarting the LXSS manager service before uninstall and after rebooting due to other issues in build 17134.

Looks like WSL's involvement was only coincidence after all. Traipsed through the logs for ages but didn't learn anything. I finally got it to boot by yanking the ethernet cable. Dying NIC perhaps? Still really puzzled by this set of symptoms.
Thanks for the tip DarthSpock, I'll bear that in mind once I've got this stuff solved.


compression?

Hey @cshum it's me again :)
This is more of a request/wish than anything, but I'd be curious if it's possible to push the limits a bit... I wonder if the quality filter or some other potential compression filter can be applied to make images smaller?
For example, I took the gopher image from the examples using
http://localhost:8000/unsafe/filters:hue(290):saturation(100):fill(yellow):format(jpeg):quality(80)/raw.githubusercontent.com/cshum/imagor/master/testdata/gopher.png
and I get this image (136kb)

If I then compress it with tinypng.com it compresses it to 104kb ... not sure if it's lossy or lossless though

I played around with some of our images, and the difference in size can be even bigger...
Is it purely a question of fine-tuning the quality? or is there some other compression that can be used?

The original png is 111kb btw, and tinypng can compress it to 45k

I believe there are several parameters in libvips function, that allows trade off between compression time and compression quality. Which I assume it makes smaller image size but takes slight more time to generate.
https://www.libvips.org/API/current/VipsForeignSave.html#vips-jpegsave
Will try to test out each of those parameters, compare their image size vs. execution times.

Thank you @cshum

The parameter with maximum compression relies on mozjpeg being installed.
https://www.libvips.org/API/current/VipsForeignSave.html#vips-jpegsave
For maximum compression with mozjpeg, a useful set of options is strip, optimize-coding, interlace, optimize-scans, trellis-quant, quant_table=3.

Using the mozjpeg options where mozjpeg is installed, it does produces the similar result 106kb at quality=80

However it seems to be indeed a tradeoff between compression quality and execution time, where mozjpeg can be comparably  slower. https://libjpeg-turbo.org/About/Mozjpeg
Furthermore it also requires additional dependencies to be installed in Dockerfile, or maybe even require different docker images for different jpeg encoder if one conflicts with another...

Thanks @cshum. I'm not sure what's the best strategy here, although from anecdotal experience, tinypng is doing a pretty good job with most images. I think it's based off of pngquant but I'm not sure... There's always a trade-off between compression and performance, but in many cases, especially for websites, smaller images are better, and caching can be very effective at making it worth paying the performance price?
How "pluggable" is imagor at the moment for those kinds of things? alternatively, how much do you think it should provide "out-of-the-box"? I know it's a big ask and definitely not something trivial to implement. However, if imagor had a similar compression as tinypng for most images, it would be a huge win.
Perhaps @jcupitt can suggest something here? :)

For the PNG version, you can get a similar result like this:
vips copy gopher.jpg gopher.png[palette,bitdepth=4,compression=9,dither=0]

To make:

Which is 54kb. These settings depend on the image though -- this pic only has a a few colours, so 4 bits per pixel is plenty, and large, flat areas, so there's no need to dither.
Image optimisers like gifsicle and pngcrush work by exploring the set of options for each file format, tweaking each one and trying to home in on the best combination of parameters that don't disrupt the image too badly. This can produce great results, but can also be horribly slow, since you have to experimentally recompress the image many, many times.
I think file size optimisation is out of scope for libvips. I suppose you could write an optimiser on top of libvips -- but I don't intend to do it!

Oh, one more thing (sorry) libvips has a plugin system, so you could replace (for example) the jpeg compressor at runtime if you wanted. It wouldn't be much work to make a moz save plugin.
As @cshum says, mozjpeg is a lot slower than libjpeg-turbo, so if you are aiming to keep latency low, it's not a good idea.
Anyway, the classic engineering problem: what are you aiming to optimize? Latency, bandwidth, or CPU load?

Thanks @jcupitt. Yes, definitely tricky. perhaps it's out of scope for imagor, although I think it would be really nice to have some compression filters available or some way to plug in something into some kind of pipeline ... very hand wavy, I know, I'm not really sure how to glue this together.
FWIW, the thumbor optimizers offered some compression options as far as I recall, but they would need to all be included in the docker container and the setup wasn't super straightforward.

shumc/imagor:0.8.16 added support for auto WebP conversion, which outputs WebP automatically if browsers support webp (detect via Accept header) and format() filter is not specified.
IMAGOR_AUTO_WEBP=1

This can also be an option if image size is a concern. WebP compresses mostly better than MozJPEG, works with transparent image as well as animated images. It is supported by all major browsers nowadays.

Thank you @cshum ! it looks great.

Hey @cshum ,
thanks for this awesome project :)
For my project, File sizes are also extremely important. I played with https://squoosh.app/ which can reduce file size by an additional 30-50% compared to what Imagor / Libvips does (on the expense of latency).
Would you be open for adding a feature which shinks a binary image through some external toolchain? I am thinking about the following idea:

have a background worker queue which optimizes image file sizes.
for the first request, run Imagor as usual and deliver the image.
before storing the image in the cache, add it to the background worker queue.
the background worker queue will then call external API / CLI / ... for compression (like sqoosh).

=> so after a while, the compressed image is delivered from the cache.
Would you be up for accepting  a pull request going into this direction? :-) I did not start working on this yet, as I first wanted to discuss it :)
All the best,
Sebastian


Join Lines: not multi cursor aware

Testing: https://github.com/Microsoft/vscode/issues/16545
Steps to Reproduce:

set multiple cursors
run "Join Lines" command

=> only happens for the first cursor

@rebornix when I run this action having multiple cursors on a single line, I loose the cursors and get a selection. When I undo and redo, I am not seeing that though:

Changing multi cursors into one selection is not intentional, it's already fixed.
For one single cursor, we move the cursor before the newly added space and next line's trimmed content. For one single selection, we still persist the selection. This is the normal behavior of both Vim and Sublime Text.
When we take multi cursor into consideration, if people put multi cursor in one single line, running Join Lines on every cursor leads to the same result, so these cursors merge into a single one.

Above the behavior after the fix. However, there are still issues about the undo/redo stack. As we need to modify the cursor position after executing the commands, an undo followed by a redo will generate wrong cursor positions. This happens both here and Delete All Left.

@alexandrudima it seems that we are not getting expected cursors while redoing editor.executeEdits, any hint on this? IMHO this one can be fixed in following iteration.

executeEdits goes into model.pushEditOperations which gets a cursor state computer that returns where the cursors end up according to markers logic. We could enhance executeEdits to optionally take a second argument resultingSelections which would be set on the cursor and in the cursor state computer.

This issue was already fixed by community.


Add Transient Dependency Injection for Projects

Add Library (Project) level dependency injection support. Which will do the following

Will be a CodeFactory Project Command To Register Transient Services
Scan for classes that support transient dependency injects
-- Must have 1 constructor
-- Constructor can have no primitive types defined
-- Must be either concrete types or interfaces
Scan and exclude class that are implemented as controllers
Will use Microsoft.Extensions.DependencyInjection IServiceCollection for registration

Completed


[CHERRY-PICK] Add fsadmin getBlockInfo CLI command

@aaudiber There are a lot of merge conflicts (1.8 use thrift but master use grpc), so I manually cherry pick the changes from PR https://github.com/Alluxio/alluxio/commit/a4bced7c5906daf3fdfb6f3a1d6dd3d07904019d.
PTAL, thanks

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1907/
Test PASSed.


Cannot resize columns in Innovator Installer

I cannot resize columns in this view:

I believe it is because the Name column fills the available space.  If you try resizing the other columns, the Name column should resize accordingly.


Adoc Unreadable

The Adoc file is complete but the end doesn't look good and is not much readable

What exactly do you mean by that? Do you want it to be better formatted (list, table or something) or do you want to have the text itself changed? Or maybe both :)

The text is okay since it is referring to the main text file I created..
But the problem a few people are facing is the readibility. The file is not nicely formatted and is untidy..
I'll assign you this task.. I have no specific format but it should be usable, full independence to you to format it the way you like.
Thank you so much for your Involvement :)

All right I'll do my best.

Thank You so much!!

I created a PR. Let me know what you think about it. #30

@FinnKr @Kedap plz reply asap so that I can take further action!!!

@FinnKr @Kedap plz reply asap so that I can take further action!!!

Go ahead. It‘s your repository. I think an additional Asciidoc file is kind of unnecessary if you got the Markdown.

Okay Thanks for the review @FinnKr.. I too feel the same.. closing this issue!


fix warning: "Use of aragon init is deprecated"

Full warning:

ℹ Use of aragon init is deprecated and has been replaced with npx create-aragon-app.

After this change, the command runs with no warnings.

Thank @pemulis I close this one cause I include changes in #99


#35 multi-host phys. NIC + static routes config

Coverage decreased (-1.3%) to 49.966% when pulling f3c023751a9ab05daf49dfb7091f668f69305ad7 on rastislavszabo:master into aba13fee6e92925dd7f45c1af7e4df4fecff71d1 on contiv:master.

Coverage decreased (-1.1%) to 50.101% when pulling f3c023751a9ab05daf49dfb7091f668f69305ad7 on rastislavszabo:master into aba13fee6e92925dd7f45c1af7e4df4fecff71d1 on contiv:master.


admin: switch default regex engine in admin /stats?filter= to RE2, which makes it run much faster

Commit Message: Change admin's /stats?filter=REGEX to be evaluated using RE2. The previous Ecmascript regexes take 4 seconds of server CPU time to filter out 1M stats (10k clusters worth), the RE2 version takes less than 200ms -- 20x faster.
Note that with this change we still have Prometheus as a weak link unless there's a filter or &usedonly.
The slower Ecmascript/std::regex behavior can be restored with an admin POST: /runtime_modify?envoy.reloadable_features.admin_stats_filter_use_re2=false
Benchmark data:
---------------------------------------------------------------------------
Benchmark                                 Time             CPU   Iterations
---------------------------------------------------------------------------
BM_AllCountersText                      460 ms          460 ms            2
BM_UsedCountersText                    37.3 ms         37.3 ms           19
BM_FilteredCountersText                4131 ms         4130 ms            1
BM_Re2FilteredCountersText              186 ms          186 ms            4
BM_AllCountersJson                      497 ms          497 ms            2
BM_UsedCountersJson                    37.7 ms         37.7 ms           19
BM_FilteredCountersJson                4131 ms         4130 ms            1
BM_Re2FilteredCountersJson              187 ms          187 ms            4
BM_AllCountersPrometheus               3514 ms         3513 ms            1
BM_UsedCountersPrometheus               137 ms          137 ms            5
BM_FilteredCountersPrometheus          4439 ms         4439 ms            1
BM_Re2FilteredCountersPrometheus        429 ms          428 ms            2

Additional Description: n/a
Risk Level: low
Testing: //test/server/admin/...
Docs Changes: added doc in admin.rst for the new &safe= option
Release Notes: added release note
Platform Specific Features: n/a

/assign-from @envoyproxy/first-pass-reviewers

/retest

/retest

/retest

/retest


[FLINK-27251][checkpoint] Timeout aligned to unaligned checkpoint barrier in the output buffers

What is the purpose of the change
Support upstream Task switching from Aligned Checkpoint to Unaligned Checkpoint to improve the UC when the back pressure is severe.
When the barrier cannot be sent from the output buffer to the downstream task within the execution.checkpointing.aligned-checkpoint-timeout, the upstream task switches to UC and takes a snapshot of the data before the barrier in the output buffer.
Brief change log

When broadcasting Barrier, if checkpointOptions.isTimeoutable(), register timer.

The time when the timer is triggered is: CP triggerTime + alignmentTimeout
Behavior when the timer is triggered: snapshot all buffers that have not been sent to the downstream before the Barrier

If the UC is enabled and the Aligned Barrier is received, the CP cannot succeed immediately and needs to wait for the outputBufferFuture:

When all barriers are sent downstream quickly, and an empty output buffer is returned, the CP ends.(when the back pressure isn't severe)
Or wait for the timer to trigger, snapshot these output buffers before the barrier, and the CP ends.(when the back pressure is severe)
If the CP is aborted, flink will execute thechannelStateFuture.completeExceptionally(cause)

Verifying this change
This change added new tests and can be verified as follows:

PipelinedSubpartitionTest#testConsumeTimeoutableCheckpointBarrierQuickly
PipelinedSubpartitionTest#testTimeoutAlignedToUnalignedBarrier
PipelinedSubpartitionTest#testConcurrentTimeoutableCheckpointBarrier
SubtaskCheckpointCoordinatorTest#testTimeoutableAlignedBarrierNotPriorityAndChannelStateResult

This change improved old tests and can be verified as follows:

ChannelStateWriteRequestDispatcherTest#doRun
ChannelPersistenceITCase#testReadWritten

Also, this PR will affect the Unaligned checkpoint benchmark. We can view the benefit after merge here.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? docs, it need to update a little doc of UC. link

Thanks for the PR @1996fanrui ! I think the code looks good, I've left a couple of comments, mostly nits.

Hi @pnowojski , thanks a lot for your review, I will fix all comments asap.

Hi @pnowojski , I fixed your all comments and re-submit commits(refer the coding style guideline), please help to review again in your free time, thanks.

Really nicely done :) LGTM. And thank you for your patience and addressing the feedback.

Hi @pnowojski , It's my pleasure, and thanks a lot for your help.
Currently, I have addressed your all comments and 2 checkState. We may also need to discuss the issue of the thread-safe problem of alignmentTimer in close method.
Re UnalignedCheckpointStressITCase:
Currently, TestStreamEnvironment#randomizeConfiguration has unaligned timeout config. code link, it's added in FLINK-19682. And I think you are right, it's very useful during developing. It can find some easily overlooked boundary conditions.

Re UnalignedCheckpointStressITCase:
Currently, TestStreamEnvironment#randomizeConfiguration has unaligned timeout config. code link, it's added in FLINK-19682. And I think you are right, it's very useful during developing. It can find some easily overlooked boundary conditions.

I've thought that the timeout randomisation didn't work/was disabled in the UnalignedCheckpointStressITCase. But maybe indeed it's working there as it's not overwriting it. If that's the case, then all is fine.

It works due to set checkpointing.randomization=true in pom.xml.

All looks good, merging.


KeyError: 'inst', how to generate inst data

I met an error when i run train_pose2vid.py,  it seems I lost inst field of data. So how to generate inst or what step do I not lose?
File "/data/jun/EverybodyDanceNow/train_pose2vid.py", line 68, in main
    losses, generated = model(Variable(data['label']), Variable(data['inst']),
KeyError: 'inst'

the data that i generated are not right, it's ok  after run make_source.py and make_target.py again.


split be/src/util/tdigest.h into headers and cpp files

Enhancement
Now all implementation is included be/src/util/tdigest.h, which will make compile time some long.
Should split these file into header file and source file(be/src/util/tdigest.cpp).

Can i try it, thanks!


Re-check the get fee of the transaction

Describe the task

[x] Do not get fee

[x] Very small transaction fees

Need to check how the fee is showing.

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1364-build-1.0.3-2023-05-15T12-17-52UTC.zip
Please check:

[ ] Error page after import/create account

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1364-build-1.0.3-2023-05-16T05-34-00UTC.zip
Validation passed!


Freezelist and burnlist via UTXO

Currently, the freezelist and the burnlist (which are required to make the redemption process secure and prevent DoS) are updated with RPCs via external processes connecting to databases. Asset custodians must have permission to modify these databases to modify the freezelist and burnlists as part of the redemption process.
As with the whitelisting, we want to remove dependency on connections to external databases. So the proposal is to update the freezelist and burn-list via blockchain transactions. This also has the advantage that permissions are controlled by wallet keys, as opposed to external connections.
The proposal:
Set-up: custodians generate an address from a wallet (or wallets if multisig). This is added as a configuration to Ocean, e.g. -setfreezeaddress=137ncomS9hSfwYtwX7AQczZv4gsy8SrFMH
A unique token is generated (possibly in the genesis block - not the policy asset - maybe requiring more changes) and sent to this address. If not generated in the genesis block, the controllers can issue a 'dummy' token to the custodian for this purpose.
To freeze an address (i.e. freeze all UTXOs with that address in the output) (or maybe freeze specific transaction ID), the custodian sends a special transaction, spending from the setfreezeaddress output, to another setfreezeaddress output, but with an OP_RETURN output containing the address (or TXID) to freeze.
The client then, every new block (i.e. change to UTXO set) checks for outputs locked with setfreezeaddress and adds any new addresses to be frozen (from the corresponding OP_RETURN to the freeze-list. To be valid, the tx must have a signature for the setfreezeaddress (i.e. spend from a previous setfreezeaddress)
To remove from the freezelist, the output of the transaction is spent.
Do the same for the burnlist.

@tomt1664 Great feature, removing dependencies would always be better in terms of encapsulation, installation, and packing. also debugging, testing, development. also in terms of architecture, it's more isolated and coherent. in terms of accounting as well, having all meaningful events in the system stored on chain as "transactions" is smart way to perceive event sourcing in the system, which benefits are tremendous in terms of stability, maintenance and security. I would highly suggest considering packaging this feature as a new "Element" and contribute it back to the Elements project, this would be a great benefit for many enterprises and use cases.


types: use more specific generics to get better autocomplete / export some more

hey, I was making my own utility-types when I suddenly wondered how you made some of yours, so I searched and found out that you already made every type needed 👏
this PR :

updates those types to use ZodiosEndpointDescription instead of unknown for the Api generic
Path generic always extends Paths<Api, M> (instead of nothing or string)
export HeaderParams / PathParams / QueryParams / EndpointApiDescription
add some documentation to make those types a bit easier to find with an example of usage

as a side suggestion, not related to that PR, I was wondering if the type named Response (used to infer the ZodiosEndpointDescription["response"] schema) should really be named the same as the global Response interface ? maybe EndpointResponse could fit and avoid the name-collide ?
EDIT: same comment with Body type clashing with the type defined in typescript/lib/lib.dom.d.ts

Thank you Alex,
Completely agree i should rename the type helpers.
This would be breaking change so i'll upgrade to v10.

I put a dedicated typescript example in a new page for typescript.
This will make it easier to find the information. i'll then be able to improve this page with all type helper descriptions.

Your contribution is available in version v9.4.0 if you need it.


Enhance sqlite exception

Hi,
subclasses of std::exception should have an assignment operator.
I've added test cases to ensure that such operator behaves correctly.
I've also added two constructor that takes const char* instead of const std::string& in order to avoid a possible allocation (in c++11) when creating the exception object.

Coverage decreased (-0.8%) to 95.425% when pulling 67ac88fb1eec6679219cfb19ef0e489a229b8346 on fekir:enhance_sqlite_exception into 670d710f62c2a8e9ded6b41c65ca54202d0cf7ba on SRombauts:master.

Coverage increased (+0.08%) to 96.312% when pulling a826dcacc11148a2d0a8c809418e57c6126f745c on fekir:enhance_sqlite_exception into 670d710f62c2a8e9ded6b41c65ca54202d0cf7ba on SRombauts:master.

Coverage increased (+0.08%) to 96.312% when pulling a826dcacc11148a2d0a8c809418e57c6126f745c on fekir:enhance_sqlite_exception into 670d710f62c2a8e9ded6b41c65ca54202d0cf7ba on SRombauts:master.

Hi @fekir, thanks for this!


dorefa-net convergence in a loacal optimal, training error keep in a high level ?

while I'm training dorefa-net on my own data set. I got training error keep in a very high level which top one training error = 16% for a long time since iterations=270k ? here is my result and experiment setup:
result

setup

With (W,A,G)=(32,32,32)

learning rate

   starter_learning_rate = 1e-2
   end_learning_rate = 1e-5
   total_steps = 3e5
   lr = tf.train.polynomial_decay(
       starter_learning_rate,
       global_step=get_global_step_var(),
       decay_steps=total_steps,
       end_learning_rate=end_learning_rate,
       power=0.5)

input

network

Another experiment With (W,A,G)=(1,2,32), other setup keep the same with above. I got the result like that: after nearly 600k interactions, it's show NO signal to convergence.

Do you have any ideas about the reasons of that? thanks in advance.
..

I run these two experiment at the same time on different GUPs, does this effect anything ?

the first experiment, which  (W,A,G)=(32,32,32), after I change the learning rate to 0.01 and restore training and I got a much better convergence at top_1_error=0.06. but for the  (W,A,G)=(1,2,32) it's still the same. :sob:

Issues are for potential problems with this library. Since you're training with your code, there are a lot of things that could go wrong and we don't have time to look through it.
If you have 6k classes why do you think the error rate you got is not good? If you have a better model of some other architectures, why don't you make changes starting from that model?
From the information you provided, there are also issues in your architecture that are not consistent with how DoReFa-Net is designed. You quantized the activations before bn0 which doesn't have much run-time benefits but hurt performance. Activations before fct is also quantized but we prefer not to do this as discussed in the paper.

thanks!


Consider renaming IonStructField to Field or StructField

...just like the title says...

This is complete on my local dev workstation but is waiting for #22 to be merged.

Implemented here: https://github.com/amzn/ion-element-kotlin/pull/29


Add patch version to repo tags (v1.1.0 instead of v1.1)

The go mod tool does not recognize SemVersion without the patch version. Therfor it falls back to the v0.9.1 version as its the only tag with patch number in your repo. Could you please tag the repo for v1.1.0 and v1.0.0?

+1 for this.
As a workaround I have forked this repo and added the tag myself, then replaced this package in my go.mod like so:
replace github.com/SermoDigital/jose => <PATH_TO_FORKED_REPO>/jose

You can also add this to go.mod:
exclude github.com/SermoDigital/jose v0.9.1

+1 for this.

So is this package still active or should someone create a fork? Because without modules support using this package is going to be awkward.

@kerak19 Here's an open source social experiment that may be worth trying:

Create a fork
Open an issue titled "Official maintenance fork: <>" with a description of your goals for the project
Message the other forkers to inform them of your fork
See if you can actually get people to agree to continue development.

I think someone just has to have enough "skin in the game" to make it happen, but it looks like there aren't any people aside from the author with more than 2 commits, so it's a tough sell.

Hi guys. It's been a while since I've worked here.
I reached out and got confirmation that a fork is the best way to move forward right now.

Do any of you have a vested interested in maintaining a fork of this project and vetting adding others to help?
@ericlagergren, @mark-adams, @zgiber, @ifraixedes, @magiconair, @tw1nk, @yageek, @eliquious, @TheHippo, @supershabam, @kmulvey, @andrefreitas, @tooooolong, @30mw002, @akutz, @andresferreira3191, @bmpickford, @briankassouf, @bryansingh, @cognusion, @cpl-qlik, @davaddi, @gluoo, @robbyoconnor, @sharonjl, @golint-fixer, @husnifirmansyah, @insionng, @jayantnd, @josuehennemann, @jvthanh, @kavonm, @lanziliang, @ll837448792, @melotusme, @mentalpower, @mex7, @mohammed90, @mudzot, @naufalfmm, @niksmith, @onef9day, @oren, @owenliu1122, @pattaraponlertratananont, @peterwillcn, @presto78, @rjansen, @sevaorlov, @showz, @smartrevolution, @bhanditz, @spivegin, @sthapaun, @stonewl897, @svarlamov, @thehippo, @tirithen, @tomwganem, @vadimline, @winonone, @zensh

@ericlagergren Is there a way that you can have the README updated to point to a "blessed" fork or transfer ownership of the repo, assuming someone speaks up?
If within 72 hours no one else responds, I'd be happy to create a fork and bless myself, but it would be primarily just to establish a simple contributor policy, vet potential contributors, and enable them to get patches in and potentially share responsibility (I don't want to be a sole maintainer).

We've mostly moved away from this package because it creates RFC-incompatible JWTs that can only be verified by itself.

I'm not up to maintaining a fork myself... -- go ahead @coolaj86

@coolaj86 i don't know if i'am competent enough - i haven't read the RFCs yet.
Tbh for starters i think Go modules support would be sufficient

Unfortunately, I cannot participate on it for now; I used this package more than 2.5 years ago, I'm competent enough in such RFCs and right now I don't have that much free time.
Thanks for the ping.

Unfortunately I don't have that much free time in this moment. I only
tested this package, don´t really used he.
Thanks
Em qui, 14 de fev de 2019 às 19:07, AJ ONeal<EMAIL_ADDRESS>escreveu:

Do any of you have a vested interested in maintaining a fork of this
project and vetting adding others to help?
@ericlagergren https://github.com/ericlagergren, @mark-adams
https://github.com/mark-adams, @zgiber https://github.com/zgiber,
@ifraixedes https://github.com/ifraixedes, @magiconair
https://github.com/magiconair, @tw1nk https://github.com/tw1nk,
@yageek https://github.com/yageek, @eliquious
https://github.com/eliquious, @TheHippo https://github.com/TheHippo,
@supershabam https://github.com/supershabam, @kmulvey
https://github.com/kmulvey, @andrefreitas
https://github.com/andrefreitas, @tooooolong
https://github.com/tooooolong, @30mw002 https://github.com/30mw002,
@akutz https://github.com/akutz, @Andresferreira3191
https://github.com/Andresferreira3191, @bmpickford
https://github.com/bmpickford, @briankassouf
https://github.com/briankassouf, @BryanSingh
https://github.com/BryanSingh, @cognusion https://github.com/cognusion,
@cpl-qlik https://github.com/cpl-qlik, @DavadDi
https://github.com/DavadDi, @Gluoo https://github.com/Gluoo,
@robbyoconnor https://github.com/robbyoconnor, @sharonjl
https://github.com/sharonjl, @golint-fixer
https://github.com/golint-fixer, @husnifirmansyah
https://github.com/husnifirmansyah, @insionng
https://github.com/insionng, @jayantnd https://github.com/jayantnd,
@josuehennemann https://github.com/josuehennemann, @jvthanh
https://github.com/jvthanh, @kavonm https://github.com/kavonm,
@lanziliang https://github.com/lanziliang, @ll837448792
https://github.com/ll837448792, @melotusme
https://github.com/melotusme, @MentalPower
https://github.com/MentalPower, @MEX7 https://github.com/MEX7,
@Mohammed90 https://github.com/Mohammed90, @mudzot
https://github.com/mudzot, @naufalfmm https://github.com/naufalfmm,
@NikSmith https://github.com/NikSmith, @onef9day
https://github.com/onef9day, @oren https://github.com/oren,
@owenliu1122 https://github.com/owenliu1122, @PattaraponLertratananont
https://github.com/PattaraponLertratananont, @peterwillcn
https://github.com/peterwillcn, @presto78 https://github.com/presto78,
@rjansen https://github.com/rjansen, @sevaorlov
https://github.com/sevaorlov, @showz https://github.com/showz,
@smartrevolution, @bhanditz, @spivegin, @sthapaun, @stonewl897, @svarlamov,
@TheHippo https://github.com/TheHippo, @tirithen, @tomwganem,
@vadimline, @winonone, @zensh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SermoDigital/jose/issues/43#issuecomment-463796659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxKQcTh-YjxBmcAcEbvmGesF-xq54FDks5vNc_-gaJpZM4WUzWL
.

https://github.com/brianvoe/sjwt

+1 for this.
As a workaround I have forked this repo and added the tag myself, then replaced this package in my go.mod like so:
replace github.com/SermoDigital/jose => <PATH_TO_FORKED_REPO>/jose

+1
This is a pretty simple change of adding a proper semver tag.  In the meantime, I also have a fork:
https://github.com/macinnir/jose

Shall we close this issue?

Was it done? If not, then no.

Using go mod, how to avoid to get v0.9.1 but get v1.1
(not as v1.1.0 but as v0.9.2)

make go.mod file

go mod init jwt

go mod tidy

get a pseudo-version for not tagged version

go get github.com/SermoDigital/jose@master

go get: upgraded github.com/SermoDigital/jose v0.9.1 => v0.9.2-0.20180104203859-803625baeddc


Won't compile under OpenCv 3.3

Because EM class is now under cv::ml::EM, not cv::EM

Thank you for noticing the issue.
The code was actually written for OpenCV 2.2 (at the time of my phd) so I
did not expect it would work in the next major releases.
If it is just that easy to make it work for the new version of OpenCV I
will just add a note in the readme.
Notice that I no longer maintain this "projects so I will not update the
code, leaving it as it is: designed for previous versions of the library.
Thank you for using my code.
2017-08-11 15:55 GMT+02:00 Patrizio Bertoni<EMAIL_ADDRESS>
Because EM class is now under cv::ml::EM, not cv::EM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SimoneAlbertini/GMM-Clustering/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHFSxtIcydLvMHnTN3vy3IqORFRPGROLks5sXF1CgaJpZM4O0r-I
.


8099 secondary index cell size

...st PerRowSecondaryIndex because there are no implementations so we may want to hold off if they will be necessary
I am not sure if this is a very good test or if I ported it well. Seems like a lot of boiler plate to test a tiny predicate and kind of fragile in the face of future changes.

I can agree it's not a terribly useful tests, but I've merged it for now. We can decide later if we want to must remove it but I don't want to spend time on that decision right now.


use default representations for Resource

I think flask-restful can use two method:
from flask import Flask
from flask.views import MethodView
from flask_restful import Api

app = Flask(__name__)
api = Api(app)

class UploadFile(MethodView):
    def get(self):
        return 0

api.add_resource(UploadFile, '/', endpoint='index')

and
from flask import Flask
from flask_restful import Resource

app = Flask(__name__)

class UploadFile(Resource):
    def get(self):
        return 0

app.add_url_rule('/', view_func=UploadFile.as_view('index'))

But now. The second method not works.

When the Resource is registered through the Api object, it'll handle doing this. The resource level representations are useful for adding a specialized representation to a specific resource. For example, if you have one endpoint that needs to return XML for whatever reason, you'd register it like this:
class SomeXMLResource(Resource):
    representations = dict.fromkeys(['text/xml', 'application/xml'], MyXMLRepresenter)

If these don't match the requested content type, then the Api object will handle the best match case.

Oh. I know the reason for this.


nothing seems to happen, no console output...

I've used the wallet a year or so ago. Just git pulled master branch and go build ./cmd/atto  , but still:
#> ./atto -b

nothing happens for many minutes
isn't there a debug flag I can set to see what's going on or where it might hang?
Feels like network trouble, but I can reach https://proxy.nanos.cc/proxy

There is no -b flag for atto. You probably meant atto b (short for balance). Take a look at the README or atto -h again. It tells you this:

The address, balance, representative and send subcommands expect a seed as the first line of their standard input.

So atto was doing nothing because you didn't give it a seed. If you stored your seed with pass, do something like pass nano | atto b.


[Feature Request] Support the notification of E-mails.

Could it support to use email, such as Gmail, to send a notification to remind me that the deadline is  close?

Nope, as it's only some client-side pages and scripts, and there's no daemon program to send those emails.
Later I'll find a server and rewrite it with something like Ruby or PHP. But I'm not sure if there will be email notifications or not, as I prefer mobile client apps and integration into other GTD apps better.

Okay, I see.


Fix unable to leave thread

Details

The leave thread option is previously shown in 3-dot menu, but now it's gone. This PR fix it by showing it in details page.
Fixed Issues

$ https://github.com/Expensify/App/issues/44964
PROPOSAL: https://github.com/Expensify/App/issues/44964#issuecomment-2214294438
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Open any chat
Send a message
Reply in thread of the message
Press the chat header
Verify there is a Leave option

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/50919443/3d0701b6-44ae-4654-b251-e90ace44e44c

Android: mWeb Chrome

https://github.com/Expensify/App/assets/50919443/533cd2b8-53b8-4a2d-b1e0-f3df00e1cce0

iOS: Native

https://github.com/Expensify/App/assets/50919443/f02b8d5a-f19f-47e6-8858-12ae0d845852

iOS: mWeb Safari

https://github.com/Expensify/App/assets/50919443/36932b01-25bc-4b2d-a984-3bb41c4b7cab

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/50919443/3dd8102b-2e66-46fd-a2e5-d0c8bf2b07e4

MacOS: Desktop

https://github.com/Expensify/App/assets/50919443/52e07843-19f1-43db-ab95-0b9c55f751f1

Additional recording shows leaving a group thread will call LeaveRoom and leaving the group itself will call LeaveGroupChat
https://github.com/Expensify/App/assets/50919443/1afc5cfd-3e6f-4cdf-a5b5-b2a678f97789

Additional screenshot showing Leave button still shows for other policy expense chat.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@bernhardoj Apologies for the review delay. Please fix merge conflicts. Thanks.

Conflict fixed.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.0.10-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

repro https://github.com/Expensify/App/issues/45828 when running this PR. not sure if related

I don't think it's related to this PR, but I can repro that issue. The BE sent Report no longer exist error when trying to rejoin the thread.

If I reopen the chat, then rejoin works.

Oh, I think it's more likely related to https://github.com/Expensify/App/pull/45370. Before that PR, if we leave a thread, we are navigated to the most recent report, so we need to reopen the thread to rejoin it.
After the PR, leaving a thread will keep the user on the thread report.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.0.10-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.10-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.11-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Rework ZCash support

Fixes #13 .
Factored out Base58Address, and used in other address schemes.

test coverage dropped 1.55%

I saw that but it is hard to believe, as I replaced much code with common code.

To check coverage

Coverage improved

Coverage   94.53%   95.91%   +1.37%

Coverage   94.53%   96.12%   +1.59%


Enhanced theme handling

Added support for dark mode, auto theme based on system settings, and persistent theme state across app restarts. Also fixed alignment issue with a button.

Good work! I just have three questions before moving forward and merging this PR:

We merged another PR in the meantime which means that you should do a rebase.
Did you check the Transactions page? Because it looks like we have more than one issue there with the dark theme
Did you make the change for the dynamic icon on Android? Do you need new graphics to do it?

Apart from this everything looks good to me and from what I saw on Discord @mikev-cw is on the same page

Good work! I just have three questions before moving forward and merging this PR:

We merged another PR in the meantime which means that you should do a rebase.
Did you check the Transactions page? Because it looks like we have more than one issue there with the dark theme
Did you make the change for the dynamic icon on Android? Do you need new graphics to do it?

Apart from this everything looks good to me and from what I saw on Discord @mikev-cw is on the same page

Thanks!! I need to check for the Transaction page before do the fix of pubspec.lock.
For the dynamic icon I remake the logo on svg :)  so i'll try to make the dynamic icon.
I'll fix it soon

Hi! Just checking in, how is it going? Let me know if you have any issue or problem working on this PR :)

Sorry, I was busy with work...
I'll try to work on it this night :)
Il giorno mer 31 gen 2024 alle ore 20:16 Marco Perugini <
@.***> ha scritto:

Hi! Just checking in, how is it going? Let me know if you have any issue
or problem working on this PR :)
—
Reply to this email directly, view it on GitHub
https://github.com/RIP-Comm/sossoldi/pull/124#issuecomment-1919767875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACL5PZF26HAZ2DBIXQTPL5TYRKJ7ZAVCNFSM6AAAAABAFARGIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJZG43DOOBXGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
There are people trying to improve everything, because everything can be
improved, and I want to be one of them!


Comment Error

Since the loss will be 0, not 1!
https://github.com/christiandimaio/A-Py-thonic-Implementation-of-Image-Captioning/blob/21cdd9c397284da1e8fbfd561a67619adfb7af6d/NeuralModels/CaRNet.py#L231

Fixed


Add option to change & disable vibration

It would be great if users could customize when the keyboard vibrates. For example, it would be nice if users could configure the keyboard to vibrate when sliding over the section dividers. That way, you could instinctively know when you've glided enough with your finger.
However, while I understand that vibration can be useful for some, it can be annoying for others. Therefore, it would be awesome if vibration could also be completely deactivated.

I am looking forward to this. Meanwhile, I have checked out iteration-5 and disabled the haptic feedback and installed debug version for now.
I am developer of OpenContacts an android app that you can find on f-droid. Do let me know in case you need help in fixing this. Also, I am thinking that we might have to create a typing tutor kind of thing for this keyboard for people to practice and get faster sooner.

Closing this as duplicate of #71


Extensions are not disabled on a normal sync

Testing #103613

Disable a setting on one machine
Wait for it to sync on another machine. Changes normal settings, sync them, run Sync Now in whatever order you like to make sure the sync should run.
The extension never disables 🐛
Change an extension on the other machine. Only at this point does the disabled state apply, with a message like:

[2020-08-04 11:31:55.658] [userDataSync] [info] Extensions: Failed to synchronize as there is a new remote version available. Synchronizing again...
[2020-08-04 11:31:56.317] [userDataSync] [info] Extensions: Disabled extension connor4312.vsix-viewer 0.0.1
[2020-08-04 11:31:57.127] [userDataSync] [info] Extensions: Updated remote extensions
[2020-08-04 11:31:57.256] [userDataSync] [info] Extensions: Updated last synchronized extensions

Seems to repro on both windows and osx

Actually, I can't repro this now. Maybe there was some caching issue at the time? Feel free to close this if this is expected...

Cant repro it too. There is no caching.
What does the logs look like when you expect the sync to happen and disables the extension? It shall have an entry to update extensions.

The output was the normal 'No changes found during synchronizing extensions'. I'll let you know if I run into again...


Componentize cabot_serial_node + cabot_handle_v2 and combine them into one process .

As the title suggests, zero copy processing has also been implemented .
However, cabot_serial_node has an open issue that prevents it from peforming zero copies processing .

I found some issues with the PR

[x] cabot_serial_node makes two different nodes (CabotArduinoSerial should not be a Node)
[x] pushed_X topics can be removed
[ ] the node cannot be terminated when the port is not available

@yamahatayukiya
Could you please test the code with ACE hardware again?

@dsato80
Thank you for fix .
I built cabot-driver again on Ace1 and confirmed its operation .
Topic output and handle operations worked correctly .


[Draft] Definition version support

Description of your changes
copilot:all

Fixes #
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

We do not need to pass fctx from beginning to end, we can always get app annotation from appfile or application revision. Also, please use bool autoUpdate instead of the whole annotations, thanks!

Thanks @FogDong for reviewing PR.
We have refactored the code to reduce the noise created by fctx map. Please take a look.
Since the appFile is not available in all the functions in the Parser, we would need to pass the autoUpdate variable to each as a separate parameter. Initially we too thought of passing it as a boolean, but considering the number of layers and functions involved, settled on making it more generic so that we can reuse it to pass additional data in future. Hope that makes sense.

Have you checked my comments? For a lot of functions, we don't need to pass anything.
For example, in parser.go,
	if err := util.GetCapabilityDefinition(ctx, p.client, def, workflowStepType, p.FunctionalCtx); err != nil {

Instead of this p.FunctionalCtx, just pass af.AppAnnotation.

Yeah I think we just need the annotation. The app context here seems a little bit misleading.

Could you include a YAML example for an Application using this new versioning scheme? Maybe add something to docs/examples?
I'm trying to understand how this change impacts consumers.


Allow author to hide/unrank

Fixes #899

Not sure what codacy means with that npath complexity

@micheljung pls merge as discussed


[Feature Request]: Individual permissions per app

描述 | Description
Hi @icyleaf
thanks for your work on zealot! We're currently considering it as part of our endeavour to migrate off of AppCenter. What really makes zealot stand out is that is allows for resigning of iOS apps to account for new iOS test devices. Unfortunately there is an additional requirement from our IT operations side: to be able to assign users or user groups to certain apps and therefore effectively limit what apps they can access. Spelled out that would mean:

Give a role to a user for a particular app (user A could be Admin on the app Foo, but only User of App Bar)
Assign and revoke roles for users and apps through the REST API

Ideally, we'd additionally be able to:

Create user groups
Assign and revoke roles for users and user groups (user group App_Foo_Test has role User, App_Foo_Dev has role Developer)
Assign to and revoke membership of users for user groups
Assign to and revoke membership of users for user groups trough the REST API

Do you think that these features would add value to zealot?
Thanks :)

The lack of fine-grained permission segmentation has always been a significant part. In essence, the underlying structure has already established the relationship between users and applications. However, due to the lack of clear understanding, it has not been realized until now. Instead, only a very coarse-grained global permission has been implemented, and all of these are hard-coded logic. To implement new logic, it would require substantial changes.

Is there anything I can do to help build understanding or how I can contribute to the project? I‘m an iOS engineer and my ruby experience is at best limited, especially with rails. But if there’s anything I can assist with let me know.

Feature was merged, use nightly tag to try it after the action is finished.

The version 5.3.0 will be released ASAP.

Close for now, re-open it if any issue.


Extension issue its not work ,

Issue Type: Bug
Extension Name: LiveServer
Extension Version: 5.6.1
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.56.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

its not work


The number 23 next to the word block is just a countdown in case the user does not select an action.

@sublines does this still happen with Atom 1.0.5?

The shortcut I used to open Atom did indeed open the older version 1.0.2.
I have updated the shortcut and didn't get the message since.
However, this did not happen every time that I opened Atom, so I can not say if that was the cause.
By the way: On Windows, Atom is saved on C:\Users\username\AppData\Local\atom
In that folder I have the versions 1.0.2, 1.0.3 and 1.0.5 with all subfolders and files.
Should Atom really keep all past versions stored on the computer and is there a way to have ashortcut to a file that always opens the latest version?

1.0.2 should have been deleted during the update to 1.0.5, but perhaps something went wrong during the update.  Atom always keeps a backup version around just in case.

Closing this since it seems like the update to 1.0.5 solved the problem.
Regarding the shortcut, you might want to check out #4893.


prevent Email Update on Jellyfin Import

Description
With the implementation of the new Email Field, if an admin runs the Jellyfin Import and selects all users, the import overwrites the existing email fields for the users. This change removes the code to update the email field on any existing users. New users will still have the email field set to account.Name
To-Dos

[x] Successful build yarn build
[ ] Translation keys yarn i18n:extract
[ ] Database migration (if required)

Hi. The import button has been overhauled by @NicolaiVdS so this PR is no longer needed. It will be added in the already open PR with some other fixes like when users are added, they are no longer shown


Links are broken on the Morphir homepage

Support Question
None of these seem to work on https://morphir.finos.org:

Thanks for reporting this. It looks like some of these pages were moved around, we'll get it fixed.
cc\ @stephengoldbaum @AttilaMihaly

@michelchan will take a look


[RFC-53] Use Lock-Free Message Queue Disruptor Improving Hoodie Writing Efficiency

https://issues.apache.org/jira/browse/HUDI-3963
What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Related PR is https://github.com/apache/hudi/pull/5416 here.

Hi @leesf Thanks a lot for your review. Really appreciate it !
All comments are addressed. PTAL

@hudi-bot run azure

Hi @leesf. Comments are addressed. PTAL. Thanks :)

Thanks a lot for your review @leesf
Really appreciate it if you can review the related pr :)


Update Linkis-doc

After project is move to Apache repository. We need to modify every possible web-link in Linkis-doc to link to corresponding page in our new repository.

I'm willing to fix it


Wrong intrinsic value check

Hello, thanks for the library!
My use case is to use your library to do a fast greek calculations on a dataframe with options of different underlyings and expirations. Below is the specific case with actual prices (today's close) for four different contracts:
import pandas as pd
import numpy as np
import py_vollib
import py_vollib_vectorized

flag = ['p', 'p', 'c', 'c']
option_prices = [3.72, 1.75, 5.30, 45.70]
under_prices = [127.14, 88.21, 107.96, 107.96]
strikes = [122, 87.5, 114.21, 69.21]
dtes = [0.065, 0.008, 0.085, 0.909]
r = np.array([0.25])

option_price = py_vollib_vectorized.implied_volatility.vectorized_implied_volatility(
    option_prices,
    under_prices,
    strikes,
    dtes,
    r,
    flag,
    on_error='warn',
    return_as='series')

option_price

I am getting the warning on intrinsic value:
/opt/miniconda3/lib/python3.7/site-packages/py_vollib_vectorized/implied_volatility.py:76: UserWarning: Found Below Intrinsic contracts at index [3]
  below_intrinsic, above_max_price = _check_below_and_above_intrinsic(K, F, flag, undiscounted_option_price, on_error)

0    0.532017
1    0.690998
2    0.552891
3         NaN
Name: IV, dtype: float64

The basic check shows that it should be OK.
Fourth line is a deep ITM option with ~0.9 delta, and 45.70+69.21 > 107.96.
I skimmed through the code and unless I am missing something the line 55 in this file shouldn't have np.any?

Alright, this can be closed. I didn't read py_vollib documentation clearly. Now I can see that it is limited to European style options.

Alright, this can be closed. I didn't read py_vollib documentation clearly. Now I can see that it is limited to European style options.

Is there a way to modify the package to try/except the below intrinsic warning so that the IV output will be equal to np.nan or zero?
I am thinking about a fix along what was outlined here but cannot figure out how to apply this fix to the vectorized py_vollib package.
https://github.com/vollib/py_vollib/issues/14#issuecomment-615875343

Is there a way to modify the package to try/except the below intrinsic warning so that the IV output will be equal to np.nan or zero?
I am thinking about a fix along what was outlined here but cannot figure out how to apply this fix to the vectorized py_vollib package.
https://github.com/vollib/py_vollib/issues/14#issuecomment-615875343

@phenn52  your link does not work

@phenn52  your link does not work

@phenn52 your link does not work

Hi Marc - thanks for letting me know. This link should work now
https://github.com/vollib/py_vollib/issues/14#issuecomment-615875343

@phenn52 your link does not work

Hi Marc - thanks for letting me know. This link should work now
https://github.com/vollib/py_vollib/issues/14#issuecomment-615875343

@phenn52 , I am not the author, but I don't understand your question. The example I posted at the beginning does not raise exception, it is just the warning, the returned IV is np.nan already. The problem is that does not work for deep-ITM options in my case. If it works for you - great, you can use it as-is, I believe.

@phenn52 , I am not the author, but I don't understand your question. The example I posted at the beginning does not raise exception, it is just the warning, the returned IV is np.nan already. The problem is that does not work for deep-ITM options in my case. If it works for you - great, you can use it as-is, I believe.

@omdv  How did you calculate the 0.909 DTE for your fourth contract?

@omdv  How did you calculate the 0.909 DTE for your fourth contract?

@phenn52 The above and below intrinsic should already be np.nan, can you provide a reproducible example where they are not?

@phenn52 The above and below intrinsic should already be np.nan, can you provide a reproducible example where they are not?

@marcdemers , Hey. Thanks for your question. While answering it I actually realized where my mistake is and that there is nothing wrong with the library. I used 0.25 for risk-free interest rate, for some reason wrongly assuming that the units are percentages. Once I switched to 0.0025 everything worked well. Thanks again, I started looking at other more complex libraries, but this will work very well.
Below is how I calculate DTE - basically time till settlement normalized by 365 days. Makes sense?
expiration = pd.to_datetime(df['lastTradeDateOrContractMonth']+'T23:59:59', errors='raise').dt.tz_localize(tz='US/Eastern')
df['dte'] = (expiration - dt.datetime.now(tz=pytz.timezone('US/Eastern'))) / pd.Timedelta('365 days')

Below are some results after I fixed the interest rate.
IV values:
0     0.538346
1     0.572795
2     0.645408
3     0.487533
4     0.472895
5     0.579759
6     0.576731
7     0.736465
8     0.924884
9     0.407187
10    1.349943
11    0.479478
12    0.338534
Name: iv, dtype: float64

deltas:
0    -0.078479
1     0.445258
2     0.859731
3     0.497690
4     0.124825
5     0.852474
6     0.815045
7    -0.246076
8    -0.267806
9     0.501942
10   -0.221046
11   -0.016002
12   -0.054273

I didn't yet do detailed comparison but just a quick glance tells me that it is very close to deltas from my broker UI. The bottom two expiring tomorrow and deltas seems to be a bit too high - but I think I know the reason.

@marcdemers , Hey. Thanks for your question. While answering it I actually realized where my mistake is and that there is nothing wrong with the library. I used 0.25 for risk-free interest rate, for some reason wrongly assuming that the units are percentages. Once I switched to 0.0025 everything worked well. Thanks again, I started looking at other more complex libraries, but this will work very well.
Below is how I calculate DTE - basically time till settlement normalized by 365 days. Makes sense?
expiration = pd.to_datetime(df['lastTradeDateOrContractMonth']+'T23:59:59', errors='raise').dt.tz_localize(tz='US/Eastern')
df['dte'] = (expiration - dt.datetime.now(tz=pytz.timezone('US/Eastern'))) / pd.Timedelta('365 days')

Below are some results after I fixed the interest rate.
IV values:
0     0.538346
1     0.572795
2     0.645408
3     0.487533
4     0.472895
5     0.579759
6     0.576731
7     0.736465
8     0.924884
9     0.407187
10    1.349943
11    0.479478
12    0.338534
Name: iv, dtype: float64

deltas:
0    -0.078479
1     0.445258
2     0.859731
3     0.497690
4     0.124825
5     0.852474
6     0.815045
7    -0.246076
8    -0.267806
9     0.501942
10   -0.221046
11   -0.016002
12   -0.054273

I didn't yet do detailed comparison but just a quick glance tells me that it is very close to deltas from my broker UI. The bottom two expiring tomorrow and deltas seems to be a bit too high - but I think I know the reason.

@marcdemers , Hey. Thanks for your question. While answering it I actually realized where my mistake is and that there is nothing wrong with the library. I used 0.25 for risk-free interest rate, for some reason wrongly assuming that the units are percentages. Once I switched to 0.0025 everything worked well. Of course with 25% of annual interest one year expiration deep ITM option was not passing the intrinsic value check. Thanks again, I started looking at other more complex libraries, but this will work very well.
Below is how I calculate DTE - basically time till settlement normalized by 365 days. Makes sense?
expiration = pd.to_datetime(df['lastTradeDateOrContractMonth']+'T23:59:59', errors='raise').dt.tz_localize(tz='US/Eastern')
df['dte'] = (expiration - dt.datetime.now(tz=pytz.timezone('US/Eastern'))) / pd.Timedelta('365 days')

Below are some results after I fixed the interest rate.
IV values:
0     0.538346
1     0.572795
2     0.645408
3     0.487533
4     0.472895
5     0.579759
6     0.576731
7     0.736465
8     0.924884
9     0.407187
10    1.349943
11    0.479478
12    0.338534
Name: iv, dtype: float64

deltas:
0    -0.078479
1     0.445258
2     0.859731
3     0.497690
4     0.124825
5     0.852474
6     0.815045
7    -0.246076
8    -0.267806
9     0.501942
10   -0.221046
11   -0.016002
12   -0.054273

I didn't yet do detailed comparison but just a quick glance tells me that it is very close to deltas from my broker UI. The bottom two expiring tomorrow and deltas seems to be a bit too high - but I think I know the reason.

@omdv  Good catch ;) everything looks good here, good luck with your projects!

@marcdemers , Hey. Thanks for your question. While answering it I actually realized where my mistake is and that there is nothing wrong with the library. I used 0.25 for risk-free interest rate, for some reason wrongly assuming that the units are percentages. Once I switched to 0.0025 everything worked well. Of course with 25% of annual interest one year expiration deep ITM option was not passing the intrinsic value check. Thanks again, I started looking at other more complex libraries, but this will work very well.
Below is how I calculate DTE - basically time till settlement normalized by 365 days. Makes sense?
expiration = pd.to_datetime(df['lastTradeDateOrContractMonth']+'T23:59:59', errors='raise').dt.tz_localize(tz='US/Eastern')
df['dte'] = (expiration - dt.datetime.now(tz=pytz.timezone('US/Eastern'))) / pd.Timedelta('365 days')

Below are some results after I fixed the interest rate.
IV values:
0     0.538346
1     0.572795
2     0.645408
3     0.487533
4     0.472895
5     0.579759
6     0.576731
7     0.736465
8     0.924884
9     0.407187
10    1.349943
11    0.479478
12    0.338534
Name: iv, dtype: float64

deltas:
0    -0.078479
1     0.445258
2     0.859731
3     0.497690
4     0.124825
5     0.852474
6     0.815045
7    -0.246076
8    -0.267806
9     0.501942
10   -0.221046
11   -0.016002
12   -0.054273

I didn't yet do detailed comparison but just a quick glance tells me that it is very close to deltas from my broker UI. The bottom two expiring tomorrow and deltas seems to be a bit too high - but I think I know the reason.

@omdv  Good catch ;) everything looks good here, good luck with your projects!

@marcdemers , Hey. Thanks for your question. While answering it I actually realized where my mistake is and that there is nothing wrong with the library. I used 0.25 for risk-free interest rate, for some reason wrongly assuming that the units are percentages. Once I switched to 0.0025 everything worked well. Of course with 25% of annual interest one year expiration deep ITM option was not passing the intrinsic value check. Thanks again, I started looking at other more complex libraries, but this will work very well.
Below is how I calculate DTE - basically time till settlement normalized by 365 days. Makes sense?
expiration = pd.to_datetime(df['lastTradeDateOrContractMonth']+'T23:59:59', errors='raise').dt.tz_localize(tz='US/Eastern')
df['dte'] = (expiration - dt.datetime.now(tz=pytz.timezone('US/Eastern'))) / pd.Timedelta('365 days')

Below are some results after I fixed the interest rate. IV values:
0     0.538346
1     0.572795
2     0.645408
3     0.487533
4     0.472895
5     0.579759
6     0.576731
7     0.736465
8     0.924884
9     0.407187
10    1.349943
11    0.479478
12    0.338534
Name: iv, dtype: float64

deltas:
0    -0.078479
1     0.445258
2     0.859731
3     0.497690
4     0.124825
5     0.852474
6     0.815045
7    -0.246076
8    -0.267806
9     0.501942
10   -0.221046
11   -0.016002
12   -0.054273

I didn't yet do detailed comparison but just a quick glance tells me that it is very close to deltas from my broker UI. The bottom two expiring tomorrow and deltas seems to be a bit too high - but I think I know the reason.

Hi @omdv, Can you please confirm if this is still working fine for you, for deep ITM contracts, is the iv calculation right?

Have I wrongly installed llvm?

I do see deep ITM option prices are indeed below intrinsic at times, e.g. I get below warning. Various indices are minute wise time series of a deep ITM
/mnt/c/Users/csera/Desktop/temp/5-swans/code/trade_utils/apps/.venv/lib/python3.10/site-packages/py_vollib_vectorized/implied_volatility.py:75: UserWarning: Found Below Intrinsic contracts at index [134, 142, 145, 146, 148, 150, 153, 155, 157, 159, 161, 163, 165, 167, 169, 170, 173, 175, 179, 181, 183, 184, 337, 338, 340, 353, 356, 358, 360, 362, 364, 367, 368, 371, 373, 375, 377, 379, 380, 382, 384, 386, 389, 391, 393, 394, 397, 399, 400, 403, 404, 406, 408, 411, 413, 414, 416, 418, 420, 422, 425, 426, 429, 431, 432, 434, 437, 439, 441, 443, 445, 447, 449, 451, 453, 455, 457, 458, 461, 463, 464, 466, 469, 471, 472, 474, 476, 479, 481, 482, 484, 487, 489, 490, 492, 494, 497, 498, 500, 503, 504, 506, 508, 510, 513, 515, 517, 518, 520, 522, 524, 527, 529, 531, 532, 534, 536, 539, 541, 543, 545, 547, 548, 550, 553, 554, 557, 559, 561, 562, 565, 566, 568, 571, 573, 574, 577, 578, 580, 582, 584, 586, 588, 591, 593, 594, 597, 598, 600, 602, 604, 606, 609, 610, 613, 615, 617, 618, 620, 622, 625, 627, 628, 631, 632, 634, 636, 638, 641, 643, 644, 647, 648, 650, 652, 655, 657, 661, 664, 667, 669, 673, 674, 678, 680, 683, 685, 687, 688, 690, 693, 695, 696, 699, 700, 702, 704, 707, 708, 710, 712, 715, 716, 719, 721, 723, 725, 727, 729, 730, 733, 735, 737, 739, 740]
below_intrinsic, above_max_price = _check_below_and_above_intrinsic(K, F, flag, undiscounted_option_price, on_error)`
and it's okay if IV for them comes out to be 0 or NaN, but in this case I am getting NaN for all other time points as well. If I calculate for a particular point in time I get correct values, but when doing for entire series in vectorized fashion I get all NaNs. Is it expected?


Closing all files in a group except for a markdown file does not update overflow control icon

VSCode Version:1.1.0-alpha
OS Version: Windows 10

Steps to Reproduce:

Open multiple files into one group, ensure a markdown file is open
In the open editors list, close all files except the markdown file

Expected: Markdown editor overflow control should indicate that the group only contains one file
Actual: Overflow control indicates that there are multiple files in the group

@stevencl having a hard time reproducing this, any more reproducible steps? can you reliably reproduce?

Yes, I can repro it each time. For example:

Ah good, the important part is that you close hidden editors :)

I see no sergeant icon at all anymore, so I guess that verifies it

@alexandrudima it is still there, just changed icon (now indicating a stack).

But yeah, I see how Steven points are obsolete now. Marking as verified.

@bpasero - This is what I mean:
(I tried to reproduce the original issue which was without tabs enabled from the screenshot)

@alexandrudima yup you are right


VRAM troubles

You mentioned that you need 16 GB+ VRAM to run at full resolution.
I have the bot working, but it runs out of Memory instantly at any attempt
      RuntimeError: CUDA out of memory. Tried to allocate 512.00 MiB (GPU 0; 7.79 GiB total                             capacity; 5.08 GiB already allocated; 88.56 MiB free; 5.20 GiB reserved in total by                               PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to                               avoid fragmentation.  See documentation for Memory Management and                                                 PYTORCH_CUDA_ALLOC_CONF
Is there any way I can either lower the image resolution or somehow use an optimized fork to run the bot on my pitiful 8GB 3060 Ti. Im just trying to set this bot up to use in me and my friends' discord server. Im also not using docker

In dalle/dalle-flow/executors/stable/config.yml, have you tried setting height and width to smaller numbers? 256x256 or 192x192 are better suited to smaller GPUs.

It still seems to be running out of memory, even at 128x128, it shows
     RuntimeError: CUDA out of memory. Tried to allocate 58.00 MiB (GPU 0; 7.79 GiB total                              capacity; 5.10 GiB already allocated; 60.75 MiB free; 5.25 GiB reserved in total by                               PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to                               avoid fragmentation.  See documentation for Memory Management and                                                 PYTORCH_CUDA_ALLOC_CONF

Ill try rebooting

You can also try disabling SWINIR upscaler to save VRAM.
python jina_parser.py --enable-stable-diffusion --disable-dalle-mega --disable-glid3xl --disable-swinir

I can't seem to find jina_parser.py, do you mean flow_parser.py?

Weird, Im running at 192x192 resolution SwinIR disabled, and it seems to work, but the images just absolutely suck
https://cdn.discordapp.com/attachments/1013495820542300210/1013496189322276914/images_U40nh-fU.png
https://cdn.discordapp.com/attachments/896380287041306635/1013495582796562563/images_pD9IztBp.png

I can't seem to find jina_parser.py, do you mean flow_parser.py?

Yes, that's right, sorry.

 Give me a couple minutes.

You can still somewhat tell the effect of the prompt, but it still just isnt nice

It also runs at a ridiculous 30 it/s

OK, I pushed an optimized branch that only uses ~4500 MB of VRAM.
https://github.com/AmericanPresidentJimmyCarter/dalle-flow/pull/new/optimized-sd
You can check it out with:
cd dalle/dalle-jina
git fetch --all
git checkout optimized-sd

Then just run and it should work.

Sorry for the ignorance, but how do I download this

You did native installation right? Oh, you might not have my remote. First, go the the dalle/dalle-jina folder, then run these commands.
git remote add jimmy https://github.com/AmericanPresidentJimmyCarter/dalle-flow
git fetch --all
git checkout optimized-sd

I don't have a dalle-jina folder

Am I missing something?

There should be a dalle folder, and dalle-jina should be inside it. It is the same folder you from jina flow --uses flow.tmp.yml in. If you're already there, you should just be able to do the above steps.

Im gonna re install quickly I think I messed something up

I have updated the instructions for the README too.
https://github.com/AmericanPresidentJimmyCarter/yasd-discord-bot

Oh thanks, consider this issue closed


GRADLE-3476 Removed 4NT-specific code in bat files

It's not necessary since it doesn't use SHIFT anymore, and actually causes some parameters (those containing dashes, such as "-Dorg.gradle.jvmargs=-Xmx2048m") to be processed incorrectly in TCC/4NT.
Tested in Windows 8 and 10 with both cmd (worked and works) and TCC (didn't work, now does). I don't have a Win98/Me machine to test there, but that execution path shouldn't have changed at all.
It might be possible to simplify the bat file a little bit further... This PR includes the minimal changes necessary to correctly support TCC.

Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[x] Ensured that basic checks pass: ./gradlew quickCheck

For all non-trivial changes that modify the behavior or public API:

[x] Before submitting a pull request, I started a discussion on the
Gradle developer list
or can reference a JIRA issue.
[ ] I wrote a design document. A design document can be
brief but explains the use case or problem you are trying to solve,
touches on the planned implementation approach as well as the test cases
that verify the behavior. Optimally, design documents should be submitted
as a separate pull request. Samples
can be found in the Gradle GitHub repository. Please let us know if you need help with
creating the design document. We are happy to help!
[ ] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
I ran a build on your local machine via the command
./gradlew quickCheck <impacted-subproject>:check.
[ ] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

This issue was initially discussed on the Gradle Forums.

Thanks for your contribution! The PR is merged but is not showing here as I had to rebase it against master.

For internal review: https://code-review.gradle.org/cru/REVIEW-6051


Quote and reply or forward label

See CZO thread
Testing plan: Manually tested
GIFs or screenshots:

@alya FYI to look at the screenshot.  Also the node tests fail, I haven't investigated, but probably we have a test that look at one of these strings.

Fixed up the test :)

./tools/test-js-with-puppeteer user-deactivation.ts works fine for me locally, so I presume the failure is a flake?


Increased cellery login timeout

Purpose

Increased cellery login timeout from 5 minutes to 15 minutes

Codecov Report

Merging #443 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #443   +/-   ##
=======================================
  Coverage   82.35%   82.35%
=======================================
  Files          29       29
  Lines         856      856
  Branches       63       63
=======================================
  Hits          705      705
  Misses        109      109
  Partials       42       42

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7c7c10...66dffcd. Read the comment docs.


Apple progress bar after login password

When i turn on device, my device request password and then show apple progress bar. How can i change it, i want when i turn on device it run apple progress bar first and then login password? thank you so much

You using hibernate mode ?

You using hibernate mode ?

i don't know, i shutdown and turn on

You using hibernate mode ?

i don't know, i shutdown and turn on
Strange, maybe its becouse of slow ssd, dont know

You using hibernate mode ?

i don't know, i shutdown and turn on
Strange, maybe its becouse of slow ssd, dont know

you can see in this video, when him turn on laptop the apple logo will show with progess bar and then password request login, but on my laptop, i turn it on the password request first and then apple logo show with progress bar
https://www.youtube.com/watch?v=SnuQjuIrfc0

You are using FireVault disk encryption, if you turn it off, it will act normally

You are using FireVault disk encryption, if you turn it off, it will act normally

exactly, thank you so much


Instillation Issue

I cant get this to install keep getting the following error:
41 error path git
42 error code ENOENT
43 error errno ENOENT
44 error syscall spawn git
45 error enoent Error while executing:
45 error enoent undefined ls-remote -h -t<EMAIL_ADDRESS>45 error enoent
45 error enoent
45 error enoent spawn git ENOENT
46 error enoent This is related to npm not being able to find a file.
47 verbose exit [ 1, true ]

same here...
npm ERR! path git npm ERR! code ENOENT npm ERR! errno ENOENT npm ERR! syscall spawn git npm ERR! enoent Error while executing: npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent  npm ERR! enoent  npm ERR! enoent spawn git ENOENT npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

i have a solution.
you have to install git.
then works fine.

Yup that fixed it, although I also had to download the zip folder and add it manually but it runs correctly
Just doesn’t support my device after all that

Yup that fixed it, although I also had to download the zip folder and add it manually but it runs correctly
Just doesn’t support my device after all that

Which device you have?

Folx, I updated git but it keeps saying on install:

npm WARN deprecated homebridge-lib2.0.0: Latest version: 3.0.1
npm WARN saveError ENOENT: no such file or directory, open '/home/juancpin/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/juancpin/package.json'
npm WARN juancpin No description
npm WARN juancpin No repository field
npm WARN juancpin No README file
npm WARN juancpin No license field

And then, if I try running homebridge (after adding "ZigBeePlatform" in config.json):

[28/9/2019 19:04:39] Error: The requested platform 'ZigBeePlatform' was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:134:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:327:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:90:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
[28/9/2019 19:04:39] Got SIGTERM, shutting down Homebridge...

Don't know what to do 😢

I have the same problem


cargo-valgrind: 2.0.3 -> 2.1.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Disable check phase as there are failures (2 tests fail)

Better to have 2 disabled tests than no tests.

@risicle please recheck.