Mounting vmedia

How do you go about mounting the /vmedia from the docker command line way?
 But when I look at the drop down under the Launch Virtual Media, it doesn't show the /vmedia folder on the host machine. Am I doing something wrong?

@Swampcritter you may have already tried this but just in case you havent

Click the dropdown and navigate to / folder

Click on /

You may need to scroll to vmedia folder, click into that folder

you should see your ISO
otherwise I have a compose file I can send you which uses a bind mount where I store my own ISO files

AutoMount didn't work for me. Did some quick discovery and...
README/Configuration says to use VIRTUAL_MEDIA variable, but the mountiso.sh script uses VIRTUAL_ISO as the variable. The example docker-compose.yml has it correct.
Change your docker container environmental variable to VIRTUAL_ISO instead of VIRTUAL_MEDIA and your ISO will AutoMount.

LOVE THIS CONTAINER. Thank you @DomiStyle!.

I just added a PR: https://github.com/DomiStyle/docker-idrac6/pull/75 for this.


feat : Implement forget password

Description:
The application currently lacks the "Forgot Password" feature, which is crucial for user account recovery. This issue is to implement the necessary pages and functionality required for the "Forgot Password" feature.
Tasks:

Create Forgot Password Page: Develop a new page or modal for the "Forgot Password" functionality.

Steps to Implement:

Design the user interface for entering email addresses for password reset requests.
Implement the frontend components for the Forgot Password page/modal.

Expected Behavior: Users should be able to access the Forgot Password page/modal to initiate the password reset process.

Backend Logic for Password Reset: Develop backend logic to handle password reset requests and send reset instructions to the user's email.

Steps to Implement:

Define API endpoints or backend routes to handle password reset requests.
Implement logic to generate and store password reset tokens securely.
Integrate with email services to send password reset instructions to users.

Expected Behavior: Upon submitting a password reset request, users should receive instructions on how to reset their passwords via email.

@Niharika0104 Forget password functionality is already implemented

@MAVRICK-1 when I click on forget password it's still on the login form.We need to take another form as this might confuse users.

@Niharika0104  you can use a modal or where user will enter his/her email or redirect it to the another page where the user will enter it's email

@Niharika0104 your task is to create that page or modal

@MAVRICK-1 Thanks I will push the changes as soon as possible

If Niharika could not complete this can i do it?

@Niharika0104 any updates ?

I will push the code changes by tomorrow

@MAVRICK-1 I'm done with resolving the issue.I created page for forget password.And email will be sent if user exists.If user doesn't exists then we need to throw error saying email doesn't exists.But this will not be secure.Do you want me to display that message saying user doesn't exists.I have to use firebase admin api for that.

@MAVRICK-1 can you please update me on this?

@Hemu21 I'm not making it complicated and irrespective of mail exists or not it's returns undefined.So this is the issue,we are not using signinwithemail method which firebase provides to get that error.Firebase are returning undefined for security reasons.Hope u got

@Niharika0104  I understand your point. It will not be secure. we have to consider security issues also. So a small suggestion to you. before sending mail. check the mail exists or not. for that you can use signin with mail. then you will get that user exists or not. if exist sent mail else ask for login. I hope you got my point. I am just suggesting you why because website security and data security is also important right. Happy coding. have a good gssoc journey

@Hemu21 I'm not making it complicated and irrespective of mail exists or not it's returns undefined.So this is the issue,we are not using signinwithemail method which firebase provides to get that error.Firebase are returning undefined for security reasons.Hope u got

@Niharika0104 did you understand what I am telling?

@Hemu21 In  signin method we also need to know password dude and in reset password user doesn't know right password.Well I can know the user email exists or not by using firebase admin sdk

@Niharika0104 you can put dummmy or some other string. anyway it's you wish how you implement is. I just gave you a suggestion.

@Niharika0104 did you understand what I am telling?

@Hemu21 I know the solution for this issue.I just want to get clarification from @MAVRICK-1 whether this message email doesn't exists is required or not.If it is required then I will add that message using firebase admin sdk else I will ommit and also show that mail has been sent even if user is not registered (and obviously mail won't be sent though)

@Hemu21 @Niharika0104 plz don't argue , @Niharika0104 I want something like this Link over here a modal appears , you can redirect to another page also , if the link send to the user it will display link send check your email , if user didn't exist it will show user don't exist

@MAVRICK-1 thanks a lot for clarifying and that exactly what I wanted to hear.So according to the link you provided the popup will always show an password reset mail has been send irrespective of email is registered or not.And that's what I will be doing in this application as well.@MAVRICK-1 By the congratulations u got accepted in gsoc.

@MAVRICK-1 Thanks a lot for clarifying that's exactly why I wanted to hear.So according to the link you provided the password reset mail will be sent irrespective of email is registered or not.I will be doing the same in this application as well.@MAVRICK-1 Congratulations you got accepted into gsoc!

@Niharika0104 For now we haven't integrated , email authentication till now . So there is no way to know the email really exist or not , If email  exist in fire authentication db it will send it to the mail or if not  it will return a error . In future i will implement passwordless login , Which will remove this password problem , you can see the feature on the above given website .

@MAVRICK-1 it doesn't return error when user doesn't exists🙂and  it is always returning undefined.Anyways I will do what's been suggested.Thanks for clarifying again.

@Niharika0104 link go through the documentation .

@Niharika0104 https://github.com/MAVRICK-1/e-commerce_website/blob/dev/src/pages/SignIn/index.js#L150-L162 link for forget password function.
Common Errors in sendPasswordResetEmail
Invalid Email

Error Code: auth/invalid-email
Description: The email address is not valid.
Handling: Inform the user that the email address is invalid.

User Not Found

Error Code: auth/user-not-found
Description: There is no user corresponding to the given email.
Handling: Inform the user that there is no account associated with that email address.

Network Error

Error Code: auth/network-request-failed
Description: A network error occurred (e.g., timeout, DNS error, etc.).
Handling: Inform the user to check their internet connection and try again.

Too Many Requests

Error Code: auth/too-many-requests
Description: Too many requests were sent to the API in a short period.
Handling: Inform the user to wait for a while before trying again.


Overlapping MIDI notes result in "funky" behavior

Malor Mintspark — Today at 8:47 PM

I'm noticing that scale workshop acts a little funky whenever I press 2 keys that have the same midi note at the same time
MIDI device
[...] same behavior on both [sevish and plainsound].

Can't find anything wrong with the code. I must assume the user is sending MIDI notes on the same channel which is undefined behaviour in any case and cannot be fixed.
(Leaving open for now in case someone can debug this.)


refactor: remove I from impl_for_with_lifetimes

The I generic is unnecessary since Item is an associated type and cannot be specified independently of ITER. I think this is technically a breaking change for anyone explicitly naming all the generic parameters. That said, probably nobody is doing that because these are generic for convenience and ergonomics, not explicit typing. Honestly I would probably just turn both args into impl Trait params, but that may just be me.

This is indeed a breaking change, especially if someone does impl_for_with_lifetimes<_, _, SomeType>
That being said we're on 0.0.11 so we're still allowed to make breaking changes in every release, this seems an easy fix for users, and it makes the code cleaner


Unclear how to run this tool with Gekko in Docker container.

When Gekko is running inside a Docker container, is it necessary to rebuild the Gekko Docker container with the BacktestTool inside the same container or is it possible to run this tool outside the Docker container?
Or in other words, how can we get this tool running when Gekko is running inside a Docker container?

I have no idea how Docker works: D You can run Gekko using the system command (ie from the bash level)? I mean node gekko -c -b or sth similar?
Or, if you have the opportunity to copy the file to cointainera without rebuilding? For example, copying binance_0.1.db to gekko / history?

Gekko is in /usr/src/app directory in container. Try:

docker cp backtest.pl backtest-config.pl <container>:/usr/src/app
Try a) if BT doesnt start and print error about missed modules then try b)
a) docker exec -ti --user root <container-id> /usr/local/bin/perl /usr/src/app/backtest.pl
b) docker exec -ti --user root <container-id> /bin/bash and next do https://github.com/xFFFFF/Gekko-BacktestTool#open-source-other-unix-like-os

Let me know do it work or You could prepare short tutorial to README and add pull request :)

Thank you! I've tried the whole evening, building a container with the dependencies being installed by the dockerfile but it didn't work out due to dependency issues. I'll try your suggestion as soon as I have time and report back to you! I managed to build a script which combines all strategies and gekko in one container automatically, if only I was able to include the backtesting tool by using a dockerfile... to be continued!

The binary version was compiled for amd64, while the Raspberry Pi has an ARM processor, so I couldn't find the right binaries. I will give you the details of the error once I'm back at my pc, don't know off the top of my head. I'll also post the dockerfile (which is a modification of the gekko Dockerfile, it now includes a RUN cpan install to install the dependencies in the container). Probably later this day. It would really be nice to have them all running in one container.

If the installation in the cointainer will be problematic - if you need to install perl, compilers and others, maybe you will like this solution more: install dependencies on localhost Raspberry (Perl should be installed by default), compile backtest.pl, and then you will transfer the compiled version to the container, it should work even if you do not have Perl in the cointerator. The disadvantage of this solution is that need unpacking "binaries" (its not true binaries only archived script and all libs) takes a little more time, so the startup is a second longer.
If you want to "compile" on your own, just cpan install PAR :: Packer and then the command: pp -M Time::Elapsed::Lang::* backtest.pl -o backtest and its all. Of course, if everything goes ok.

When executing "perl backtest.pl" in the docker container, I get the following error:
Can't locate DBD/CSV.pm in @INC (you may need to install the DBD::CSV module) (@INC contains: /etc/perl /usr/local/lib/arm-linux-gnueabihf/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/arm-linux-gnueabihf/perl5/5.20 /usr/share/perl5 /usr/lib/arm-linux-gnueabihf/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at backtest.pl line 21.
BEGIN failed--compilation aborted at backtest.pl line 21.
I did include the following line in the Dockerfile (which builds the container):
RUN cpan install Parallel::ForkManager Time::Elapsed Getopt::Long List::MoreUtils File::chdir Statistics::Basic DBI DBD::SQLite JSON::XS TOML File::Basename File::Find::Wanted Template LWP::UserAgent LWP::Protocol::https Set::CrossProduct DBD::CSV Text::Table File::Copy
so all dependencies should be installed. The *.pl files are present in the /usr/src/app/ folder. Perl version in the container is:
This is perl 5, version 20, subversion 2 (v5.20.2) built for arm-linux-gnueabihf-thread-multi-64int

Making progress! After installing all packages manually in the container, it starts to work. I receive the following error though:
USDT-BTC Backtest is failed.
Error in tempfile() using template tmp/tmp_configXXXXX.js: Parent directory (tmp/) does not exist at backtest.pl line 1196.

mkdir tmp

That's very strange, I create the tmp directory in /usr/src/app and double checked if it exists. I still get the same error, but noticed that the error is being removed by the script?

You can comment last line in BT rmtree 'tmp' to prevent removing by BT.
I havent idea why perl mkdir not work. Have You this line on begin of code: mkdir 'tmp' unless -d 'tmp';?

Yes, I have this line:
my $configfile = "./backtest-config.pl";
mkdir 'tmp' unless -d 'tmp';
Permission issue?

Maybe, it would be weird. Any app can use perl to create directory. BT has disabled warnings. Can You try these lines in docker?
https://gist.github.com/xFFFFF/2705dc49b68cc639232c56ce1aadf5b7
Its two methods,  first is system enviroment call, second is perl mkdir. I cant implement system call to BT because will not work on Windows.

So I fixed the issue with the perl dependencies by using cpanm instead of cpan in the dockerfile. I'll post the result when I'm back at my pc. Only issue now is the "tmp" directory. I'll try your gist again when I'm back at my pc and when I discovered how to install the dependency (see comment at gist). Thank you for your dedicated help!

Making progress again. Tool seems to be running fine now, except that it says that the database is locked.
perl backtest.pl -i
Updating Gekko's kraken market data...
Done writing Kraken market data
Import 1 pairs: kraken:EUR:XRP.
EUR:XRP (2018-01-01 00:00:00 - 2018-01-02 00:00:00) is started at 2018-01-02 00:00:00...
events.js:183
throw er; // Unhandled 'error' event
^
Error: SQLITE_BUSY: database is locked
Importing kraken EUR-XRP is failed:
Had 1 errors on 1 jobs. Elapsed time: 2 seconds

You have right with import: https://github.com/xFFFFF/Gekko-BacktestTool/wiki/Troubleshooting#error-sqlite_busy-database-is-locked
Im importing on remote server. For You I recommend using different file for import. After import done You can use delete old, change namefile back and it is it.

This issue can be closed, I will post results when I have a complete script which merges all relevant repositories into one directory and which alters the Dockerfile in order to build a container. Right now the solution is to:

Clone gekko repo
Clone Gekko-BacktestTool repo
(optionally) Clone Gekko-Strategies repo
(optionally) Clone gab0/gekko-extra-indicators
Install all repositories into the gekko repo according to their respective install instructions.

Change the Dockerfile of the gekko repo to:

Excellently! Thanks for your work :) I will create a subpage for Docker and put your tutorial on. I also link in readme :)

Hello! I have the same issue with tmp/.
perl backtest.pl
Error in tempfile() using template tmp/tmp_configXXXXX.js: Parent directory (tmp/) does not exist at backtest.pl line 1196
I do not use docker.
Anyone can help me?


bug: Failed to resolve Vue import

Affected Packages

[ ] @yeger/eslint-config
[X] @yeger/vue-masonry-wall
[ ] @yeger/vue2-masonry-wall
[ ] vecti

Description
I've just realized that the Vue import within the recent releases is being bundled with an absolute path that users can't access.

Error in console

Reproduction
https://stackblitz.com/edit/stackblitz-starters-h4bzau
Additional context
No response
Preferences

[ ] I want to be assigned to and work on this issue myself

Thanks for the report! I know what caused this issue and will push a fix later today.
As a memo for myself, the issue is caused by peer dependencies not being externalized by vite-plugin-lib.

@Yizack Please give v5.0.2 a try, it should be fixed.

It's working perfectly!


Add DotNet Library to Consume Fixer.IO

Nuget package to consume Fixer.IO from Dotnet

any news ?

@hakanensari Please merge


App not installed after upgrading to version 2.2.0

I usually build with PhoneGap CLI-6.2 and cordova-plugin-crosswalk-webview spec="1.8.0".
It seems that I neet to change PG CLI to 6.5 (in order to let PG build IOS with SDK for IoS 11).
If I Change to CLI-6.5 I need to upgrade crosswalk-webview to version 2.2.0.
After building with CLI-6.5 and cordova-plugin-crosswalk-webview spec="2.2.0"
I'm no longer able to update my original App (coming from GooglePlay store and build with CLI-6.2 and crosswalk-webview 1.8) from PhoneGap build page: the installation comes with error "cannot install application", and in order to install I have to delete the app installed from store. Why? what's wrong? I'm scared about releasing it because I don't want my users to face the same problem. Please help me

Hellow! Have you found any solution about this issue?


Add Python 3.12 support

Close: #51

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e8b77a3) 100.00% compared to head (c4bf0be) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #57   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           23        23
=========================================
  Hits            23        23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat(map): Extend supported Key Types for C# codegen

Author Checklist

[x] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
[x] Vital features and changes captured in unit and/or integration tests
[x] Commits messages follow AP format
[ ] Extend the documentation, if necessary
[ ] Merging to main from fork:branchname

coverage: 98.932% (-0.02%) from 98.955%
when pulling 3d68270549134086b6656535eaed9ef4fc5036f0 on jonathan/codegen_map_csharp
into 79653dd19ccdff1ad8940250a938fc1c939ff050 on main.


[aes/doc] Update documentation based on D2S review

In particular, this PR documents:

the use of multi-rail control logic,
the need for a system-supplied reset in case of FI detection,
worst-case entropy consumption rates
the re-use of partial, intermediate results for remasking among DOM S-Boxes.

This is related to lowRISC/OpenTitan#10422.

Thanks for the reviews!


Please support MSYS2 MINGW64

Hi,
I stopped maintaining this project. Adding MSYS2 support should not be that difficult for this project, so feel free to give it a try. I can merge your changes back, just let me know.
With best regards,
Sam

Hi,
I stopped maintaining this project. Adding MSYS2 support should not be that difficult for this project, so feel free to give it a try. I can merge your changes back, just let me know.
With best regards, Sam

Please tell it clear that you stopped maintaining this project on README.md


Fix search tests.

Changes
Updates tests for the changes in #259, since searches now only check for an exact match.
I was too hasty! :runner:

For review: @angaither

pew pew pew pew :ship:


Refactor code for parsing command-line arguments

I was trying to change some of the functionality around parsing command-line args and found that the error handling in parse_arguments is a bit messy.
There are three cases the function has to handle:

The args are valid and the program should start a simulation
The args are valid but the program should abort (e.g. if the user passes the --help argument)
The args are invalid

Previously, the function returned all this information within a CommandArgs struct. I've refactored the code so that the function returns a std::optional<CommandArgs> instead:

If we want to start a simulation, a CommandArgs struct is returned
If the args are valid, but we want to abort, std::nullopt is returned
Else an exception is raised

@jamesturner246 I'm heading off now. I'll merge this so that we don't get merge conflicts while I'm gone. The other ones shouldn't cause problems.

No worries. Sorry for the delay.


Missing example on Logging

Please provide an example of how to write Diagnostics information.
What WriteLine do I use in Code? Debug.WriteLine, Debugger.WriteLine, Console.WriteLine, TestContext.WriteLine or Trace.WriteLine ?
Is a runSettings necessary ?  If so, what do enter and where ?  <CaptureTraceOutput/> has a default of True.
In the VsTest Task, if there's a runSettings involved, it must be specified in the "Settings file", but is there anything else?  does the variable System.Debug have an impact on the "logging" ?
When the build is done, where to look ?  Should the messages appear in the Build result>Logs ?
In the Build result>Tests, under the UnitTest in question: Under Debug, should there be something an entry ?
Confusing

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 16bd8dd1-7650-8c18-2553-38a8bc54e892
Version Independent ID: f9fa517a-7adc-e327-d12e-256295a1ed52
Content: Visual Studio Test task - Azure Pipelines
Content Source: docs/pipelines/tasks/test/vstest.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: dastahel

@patware - any of Console.WriteLine, TestContext.WriteLine or Trace.WriteLine should work. Output is made available as an attachment to the test. You can find them in the 'attachments' section for a failing test in the 'Test' tab of a build/release. Here's a screenshot

If the test passed, these details are not available. There's no need for specifying runsettings to make this work.
System.Debug does not have an impact on this. System.Debug causes tasks to produce verbose output but does not impact the test output itself.
Hope this helps and unblocks you for now.
Will look into adding this to an appropriate doc.

@alexhomer1 - sent you the details of how to address this ask. Please address in the docs and close this issue when done.

Thank you for your feedback. I will update the topic to include your recommendations.


Feature request: Octicons

Would it be possible to support Octicons as alternative icons? As described here.

I'm not sure I want to bundle another font pack with the plugin, as it is already quite large due to Font Awesome being bundled. I may give the option to download additional font packs in settings. Let me think about this.

You can now download additional icon packs in settings.


Dimension scaled kernel

Here is the PR I mentioned with the kernel function scaled by input data dimension. It doesn't add any overhead for the user and seems to qualitatively make the difference between different distance metrics less extreme and the impact of kernel widths more predictable.
Let me know if you think it'd be good to fold in.

Sorry for the long delay, I just haven't had the time to try this with different datasets. I'll do this when I come back from a conference.
Thanks!

Sorry to get back to this so late. So, did you find that keeping the same default width (3) while still dividing it by the number of features worked well on most cases? I initially came to the width=3 value by playing around with small-sized datasets (8-10 columns), and if I remember correctly having 0.3 (3/10) would be too small.

Yeah, I've seen similar things, we're this merged it would probably make sense to change the default width to 25-30 to compensate.

Thanks for this idea. In order to keep the kernel the same (so that people can reason about it more easily), I changed the default parameter of kernel_width instead of changing the kernel function in this commit. IfI also changed the scaling so that it is according to sqrt(K) instead of K (where K is the number of columns), as I think euclidean distance grows at a sqrt rate instead of a K rate usually.

Makes sense, thanks!


Add auth0 login to the UI

Certain pages of the UI (data upload, data review, news editing) should only be accessible to authenticated and authorised users. We will use Auth0 to handle the auth workflow, as documented in the 0005_login ADR.
This story covers adding the @auth0/nextjs-auth0 library to the UI, and adding a login feature, probably following https://auth0.com/blog/ultimate-guide-nextjs-authentication-auth0/#Next-js-Serverless-Deployment-Model. The application will need to be registered with Auth0 first.
Acceptance Criteria:

[x] The Vector Atlas app is registered with Auth0
[x] A user has the ability to log in to the UI, using the Auth0 login
[x] Once logged in, the UI shows the username in an appropriate place on the navbar

A Auth0 login has been created and used to login in successfully. The username used to login is displayed after clicking on an icon on the navbar in the top right corner of the website.


Support for Drag and Drop

This pull request is a Work In Progress and should not be merged until otherwise noted!!
This PR introduces drag and drop support to BrickKit.
Bricks that should be considered eligible for drag and/or drop should provide a delegate for Brick#dragDropDelegate. To opt-in to drag, return a [UIDragItem] in BrickDragDropDelegate#dragItems(for:at:). To opt-in to drop, return a Bool in BrickDragDropDelegate#canHandle(_:) affirming whether the provided UIDropSession has any objects that conform to your brick's supported UTIs, and implement the BrickDragDropDelegate#willDrop(_) and BrickDragDropDelegate#drop(_:to:from:) handlers. For more information, see the DragDropBrickViewController example, as well as Apple's documentation on Drag and Drop in Collection Views.
I have put this PR up here despite its state of completion to kickstart discussion about this feature, as well as provide advice on how BrickLayouts work.
Current list of to-dos:

[ ] Fix current blocking crashers

[ ] Sample app crashes while attempting to reorder layout while previous drop has not completed
[ ] Sample app crashes while attempting to reorder layout to accommodate new cells

[ ] Document all new methods and protocols
[ ] Implement drag and drop in other example controllers to demonstrate drag and drop between collection views within the same app
[ ] Write lots of unit tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fa2d3ad). Click here to learn what that means.
The diff coverage is 2.3%.

@@            Coverage Diff            @@
##             master     #190   +/-   ##
=========================================
  Coverage          ?   89.47%
=========================================
  Files             ?       41
  Lines             ?     4569
  Branches          ?      357
=========================================
  Hits              ?     4088
  Misses            ?      480
  Partials          ?        1

Impacted Files
Coverage Δ

Source/Layout/BrickFlowLayout.swift
91.18% <ø> (ø)

Source/Cells/ImageDownloader.swift
79.31% <ø> (ø)

Source/Cells/BrickCell.swift
98.57% <ø> (ø)

Source/Layout/BrickZIndexer.swift
100% <ø> (ø)

Source/Models/Brick.swift
71.23% <0%> (ø)

...ViewControllers/BrickViewController+DragDrop.swift
0% <0%> (ø)

Source/Cells/BrickPlaceholderCell.swift
0% <0%> (ø)

Source/Models/BrickSection.swift
85.86% <0%> (ø)

Source/ViewControllers/BrickViewController.swift
86.11% <100%> (ø)

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 fa2d3ad...a071886. Read the comment docs.

Before this PR can be merged in, I suspect that BrickKit is going to need to drop support for building against the iOS 10.3 SDK and lower.


Add analytical fluid flow routine for short bearings

We decided to create a fluid flow routine that can be calculated analytically before the numerical one.

Just an update to this issue's status: although the routine was merged, we still need to make sure it is doing what it is supposed to do. @JuliaMota and professor @juvianna, along with myself, are taking care of it. I'm closing this issue and updating #37 to include what needs to be done related to this one.


Full YoloV3 model

I'm wondering if you have tried building the full model (not tiny) for the Edge TPU?

@guichristmann would also be interested to know whether you've tried this.

I have built the full model using the instructions with some modifications. In the keras-yolo3 repo linked in the README, I changed activation=leaky to activation=relu in the non-tiny config file. Then created the keras-model.h5 with the convert.py script (no modification in this script) and used the keras_to_tflite_quant.py (no modification in this script either) to create the .tflite file.
With the latest tensorflow (2.3.0) and keras from pip, edgetpu_compiler failed to compile all operations so I downgraded tensorflow to 2.1.0 and keras to 2.3.1 (both were needed) and voilà:
edgetpu_compiler -s yolov3.tflite
Edge TPU Compiler version 14.1.317412892

Model compiled successfully in 5155 ms.

Input model: yolov3.tflite
Input size: 60.00MiB
Output model: yolov3_edgetpu.tflite
Output size: 60.16MiB
On-chip memory used for caching model parameters: 6.81MiB
On-chip memory remaining for caching model parameters: 9.25KiB
Off-chip memory used for streaming uncached model parameters: 52.54MiB
Number of Edge TPU subgraphs: 1
Total number of operations: 113
Operation log: yolov3_edgetpu.log

Operator                       Count      Status

RESIZE_NEAREST_NEIGHBOR        2          Mapped to Edge TPU
CONCATENATION                  2          Mapped to Edge TPU
PAD                            5          Mapped to Edge TPU
ADD                            23         Mapped to Edge TPU
CONV_2D                        75         Mapped to Edge TPU
QUANTIZE                       6          Mapped to Edge TPU

Does it work on the tpu? Does it have good performance? I don't know, I have not yet run any inference with it but I will as soon as I have time...

@idittansikte awesome! Very interested in your results with respect to whether it runs on the tpu and the performance.

@raryanpur I've tried it now and it loads on the edge with no errors, but I don't get any detections if i dont lower the threshold to 0.  I was thinking if I need to retrain the weigths for relu.
The good news is I guess that it seem to load the model.


*: Use &str instead of Into

This prevents accidental allocations and copies within the library by
forcing the conversion to String to happen as late as possible. With
Into<String> parameters, arguments could be converted multiple times.
The only two types in libstd that can be passed as Into<String> are
String and &str. Accepting &str achieves the same, with the minor
change that a String must be passed by reference:
let name: String = "my_metric".to_string();
let help: String = "some help string".to_string();
let opts = Opts::new(&name, &help);

In most uses of Prometheus, the strings will be &'static str anyway,
so this should not have much of an effect.

I don't get it, how

With Into parameters, arguments could be converted multiple times.

can happen?
I think use Into can avoid copying when it's possible and make code clean, because you don't have to take a reference of a string.

@BusyJay this has already happened in https://github.com/pingcap/rust-prometheus/pull/80#pullrequestreview-7326571.

My commit message may not be entirely clear, but the issue is that Into<String> may result in into being called more than once as it passes through multiple such functions. That happened in #80 where effectively an argument had .into().as_str().into() get called. If passed a &'static str as is likely, this results in two copies and allocations. This is not really a performance issue in this use case, but it does make the wrong thing possible. Passing &str makes the wrong ting impossible: conversion to String happens at the bottom, where the String is stored.

One more thing:

make code clean, because you don't have to take a reference of a string.

In almost all uses of these functions, the names and label names will be &'static str, given in the source. Avoiding passing a string with & is not something that will come up often, because passing a String won't come up often in end user code.

I think both situations here are performance issues rather wrong thing:

take a reference of string then clone it;
clone a reference's data and make a reference again.

I don't think Into<String> is to be blamed in pr #80, it's abused. You can't blame all traits once they are used improperly. The usage you are about to change here, they are used properly and works as expected.

Just take a close look at #80, the Into<String> is ok there too.

Hi @kamalmarhubi
I think Into<String> is ok here.
In most cases, we can't use the code like .into().as_str().into(), and if we use String for &str, we may clone the String again.

@siddontang

In most cases, we can't use the code like .into().as_str().into(), and if we use String for &str, we may clone the String` again.

However the sequence .into().as_str().into() is exactly what happend in #80.
In any case, I'll close this despite misgivings with the current state not being idiomatic. It's not a productive use of anyone's time.

FWIW I started a discussion on urlo because I've found this confusing in the past: https://users.rust-lang.org/t/idiomatic-string-parmeter-types-str-vs-asref-str-vs-into-string/7934

Thanks @kamalmarhubi
I think we must fix the wrong use in https://github.com/pingcap/rust-prometheus/pull/80 :-)
If you have any update for the discussion, we can re-open this PR again.

Update: Into<String> is fine for this use case, and we should just be careful not to call .into() too soon. If we really cared about allocations and copies, Into<Cow<'static, str>> could be worthwhile. Given this is all about metric names, which are only allocated or created once, I think this complication of the signatures is not worthwhile.


Issue looking for GitHub app when running

I have recently updated to revel 1.0, and my colleague pulled the changes. However, when it came time to run it, things got weird:
$ revel run -a .
Revel executing: run a Revel application
Changed detected, recompiling
Parsing packages, (may require download if not cached)...ERROR 15:57:14 harness.go:239: Build detected an error                   error="lstat /Applications/GitHub.app: no such file or directory"
panic: opps
goroutine 31 [running]:
github.com/revel/cmd/utils.(*SourceError).Error(0x0, 0x15bedda, 0x17)
	***gocode/pkg/mod/github.com/revel/cmd@v1.0.3/utils/error.go:49 +0x3ca
github.com/revel/cmd/harness.(*Harness).refresh(0xc000199570, 0x0)
	***gocode/pkg/mod/github.com/revel/cmd@v1.0.3/harness/harness.go:245 +0x6ab
github.com/revel/cmd/harness.(*Harness).Refresh(0xc000199570, 0xc000126ec0)
	***gocode/pkg/mod/github.com/revel/cmd@v1.0.3/harness/harness.go:210 +0xc6
created by github.com/revel/cmd/harness.(*Harness).Run
	***gocode/pkg/mod/github.com/revel/cmd@v1.0.3/harness/harness.go:302 +0x1fa

we eventually resolved this by using the GitHub Desktop app, and the following commands:
$ mkdir /Applications/GitHub.app/
$ mkdir /Applications/GitHub.app/Contents/
$ mkdir /Applications/GitHub.app/Contents/Resources/
$ cp -r /Applications/GitHub\ Desktop.app/Contents/Resources/app/git /Applications/GitHub.app/Contents/Resources/git

I don't know how to reproduce, since it doesn't happen on my machine, but it seems like a bug that revel is expecting expecting to find /Applications/GitHub.app, and I'm hoping that's useful to you even without more info.

The opps error indicates a Error was call on a nil error object Which was done in this bad line of code
revel/cmd#210 fixes the error


Version 0.5

@babbush I think we should bump the version on pip soon due to some critical bug fixes. Here is a list of changes:

Fixed a bug in the Jordan-Wigner transform applied to InteractionOperators which caused some terms to be ignored
Fixed a bug in the Bravyi-Kitaev Superfast Transform which caused some terms to be ignored
Fixed a bug in the binary code transforms functionality which caused creation operators to map to annihilation operators and vice versa
Changed the implementation of the Bravyi-Kitaev transform to use the definition from arXiv:quant-ph/0003137 instead of the one from arXiv:1701.07072, which is now implemented under a different name
Added a utility for constructing "prepare" circuits to simulate Linear Combinations of Unitaries
Renamed SymbolicBinary -> BinaryPolynomial
Changed the convention used in the function for instantiating Majorana fermion operators
Introduced a new way to instantiate FermionOperators and QubitOperators with a single factor
Added the fermionic spin operators Sx and Sy to the special operators module
Added a demo of the Jordan-Wigner and Bravyi-Kitaev transforms

@jarrodmcc let's do it tomorrow.


[hardhat-upgrades] DeployOptions missing deterministicDeployment

When using upgrades.deployProxy the DeployOptions type interface provided is very different than the usual interface provided in the usual hardhat package. In particular, there are several commonly used deployment options that are no longer available. For example:
  const options: DeployOptions = {
    from: deployer,
    gasLimit: 2000000,
    args: [owner],
    deterministicDeployment: SALT,
    log: true,
  };

Is it possible that the Options interface defined in deploy-proxy could extend the usual hardhat Options to overcome this issue or are these parameters no longer possible when working with proxies?

This is similar to https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/85, generalizing the idea to all available deployment options.
It would be nice to do something like this, but the additional issue that we have is that a deployProxy call can potentially perform 3 different deployments (implementation, admin, proxy), and upgradeProxy will additionally send a transaction (the upgrade function call). So the question we need to figure out is: should these deployment options be the same for all of these transactions? Or should it be possible to specify options for each deployment separately?
https://github.com/OpenZeppelin/openzeppelin-upgrades/pull/213 adds a from option that is shared by all deployments and transactions, which I think makes sense. But it is less clear what should happen for gasLimit, for example.
Let me know what you think!

This is similar to https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/85, generalizing the idea to all available deployment options.
It would be nice to do something like this, but the additional issue that we have is that a deployProxy call can potentially perform 3 different deployments (implementation, admin, proxy), and upgradeProxy will additionally send a transaction (the upgrade function call). So the question we need to figure out is: should these deployment options be the same for all of these transactions? Or should it be possible to specify options for each deployment separately?
https://github.com/OpenZeppelin/openzeppelin-upgrades/pull/213 adds a from option that is shared by all deployments and transactions, which I think makes sense. But it is less clear what should happen for gasLimit, for example.
Let me know what you think!

It seems the motivation for wanting these is very particular to each use case. For ours, it would be the deterministic deployment that is of most importance (as this can be used to ensure the contracts will all have the same address on different networks - such as xDai). While it is clear that some of these parameters may need to be specified for each individual deployment within deployProxy there are surely some that could easily be carried over as "universal". From those options provided above, it seems to me that log and deterministicDeployment could all be easily considered as universalDeplyOptions.
Perhaps its best to tackle this issue in two steps: First being the universal deployment options and the latter (if/when needed) the specifics.
As I am most interested in deterministic deployment, my opinion is rather bias. I would be happy to know if this suggestion might be considered for the project and could perhaps even attempt at making/helping with the changes.

It seems the motivation for wanting these is very particular to each use case. For ours, it would be the deterministic deployment that is of most importance (as this can be used to ensure the contracts will all have the same address on different networks - such as xDai). While it is clear that some of these parameters may need to be specified for each individual deployment within deployProxy there are surely some that could easily be carried over as "universal". From those options provided above, it seems to me that log and deterministicDeployment could all be easily considered as universalDeplyOptions.
Perhaps its best to tackle this issue in two steps: First being the universal deployment options and the latter (if/when needed) the specifics.
As I am most interested in deterministic deployment, my opinion is rather bias. I would be happy to know if this suggestion might be considered for the project and could perhaps even attempt at making/helping with the changes.

I have re-evaluated the controversial notion "universal deployment options" and fallen back to something more generic that allows users to specify their own deployer in which they can use whichever DeployOptions they like. This is a non-invasive way of making the requested feature available for those who want it, but leaving things as is for those who are uninterested in such additional overhead.

I have re-evaluated the controversial notion "universal deployment options" and fallen back to something more generic that allows users to specify their own deployer in which they can use whichever DeployOptions they like. This is a non-invasive way of making the requested feature available for those who want it, but leaving things as is for those who are uninterested in such additional overhead.


Automatic index creation fails with Elasticsearch >= 8.6.0

What kind an issue is this?

[x] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.
[ ] Feature Request. Start by telling us what problem you’re trying to solve.
Often a solution already exists! Don’t send pull requests to implement new features without
first getting our support. Sometimes we leave features out on purpose to keep the project small.

Issue description
The automatic index creation feature in elasticsearch-spark has stopped working with Elasticsearch clusters starting from version 8.6.0.
When using default saving mode which saves documents directly to Elasticsearch shards, when Spark creates more than one task to save those documents into Elasticsearch, at least one task fails with the exception like in "Stack trace" section below.
I have spent (together with my colleagues) some time investigating this issue and we have found the following:

we have tested this on different Elasticsearch versions and this issue started occurring on Elasticsearch 8.6.0 and continues to occur even with newest Elasticsearch cluster 8.13.1
it seems that this issue is caused by the Elasticsearch cluster API returning inconsistent replies:

method to check if index exists (i.e. HEAD /<name-of-index>) returns HTTP status 200 meaning that index exists
but method to get search shards (i.e. GET /<name-of-index>/_search_shards for some short period of time returns empty list of shards, but this period (despite being short) is long enough to cause the assertion in RestService.initSingleIndex() to fail
it looks like this behaviour has changed in Elatsicsearch 8.6.0, because on previous versions this issue did not exist

Steps to reproduce

Try to save some documents into non-existing index, with both settings es.nodes.wan.only and es.nodes.client.only set to false (default)

Code:
public class Main {
    public static void main(String[] args) {
        SparkConf sparkConf = new SparkConf()
                .setAppName("Example")
                .setMaster("local[*]")
                .set("es.nodes", "localhost:9200");

        try (JavaSparkContext sparkContext = new JavaSparkContext(sparkConf)) {
            List<Map<String, String>> data = Arrays.asList(
                    Map.of("propertyA", "valueA1", "propertyB", "valueB1"),
                    Map.of("propertyA", "valueA2", "propertyB", "valueB2"),
                    Map.of("propertyA", "valueA3", "propertyB", "valueB3")
            );
            JavaRDD<Map<String, String>> stringJavaRDD = sparkContext.parallelize(data);

            JavaEsSpark.saveToEs(stringJavaRDD, "test-index");
        }
    }
}

See https://github.com/mlyczek/elasticsearch-hadoop-concurrency-issue for full project ready to run.
Strack trace
org.elasticsearch.hadoop.EsHadoopIllegalArgumentException: Cannot determine write shards for [test-index]; likely its format is incorrect (maybe it contains illegal characters? or all shards failed?)
	at org.elasticsearch.hadoop.util.Assert.isTrue(Assert.java:60)
	at org.elasticsearch.hadoop.rest.RestService.initSingleIndex(RestService.java:689)
	at org.elasticsearch.hadoop.rest.RestService.createWriter(RestService.java:634)
	at org.elasticsearch.spark.rdd.EsRDDWriter.write(EsRDDWriter.scala:71)
	at org.elasticsearch.spark.rdd.EsSpark$.$anonfun$doSaveToEs$1(EsSpark.scala:108)
	at org.elasticsearch.spark.rdd.EsSpark$.$anonfun$doSaveToEs$1$adapted(EsSpark.scala:108)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
	at org.apache.spark.scheduler.Task.run(Task.scala:136)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:548)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1504)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:551)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

Full log: full-log.txt
More investigation information
I have prepared a small Python script to show the inconsistent behaviour of Elasticsearch. It more or less mimics the behaviour of RestService.initSingleIndex() (checks if index exists, if not then creates it, waits for YELLOW status and then gets shards, if index does exist, then gets shards right away).
import logging
import threading
import time
import requests
from requests.auth import HTTPBasicAuth
from urllib3.exceptions import InsecureRequestWarning

requests.packages.urllib3.disable_warnings(category=InsecureRequestWarning)

es_url = "https://localhost:9201/"
index_name = "text-index"

my_auth = None

def run():
    while True:
        exists_reponse = requests.head(f"{es_url}/{index_name}", auth=my_auth, verify=False)
        if (exists_reponse.status_code != requests.codes.ok):
            logging.info("Creating test-index")
            response = requests.put(f"{es_url}/{index_name}", auth=my_auth, verify=False)
            logging.info("index create response %s", response)

            logging.info("Waiting for YELLOW")
            health_response = requests.get(f"{es_url}/_cluster/health/{index_name}?wait_for_status=YELLOW&timeout=10s", auth=my_auth, verify=False)
            logging.info("health response %s", health_response)
        else:
            logging.info("index exists")

        logging.info("getting shards")
        search_shards_response = requests.get(f"{es_url}/{index_name}/_search_shards", auth=my_auth, verify=False)
        shards = search_shards_response.json()['shards']
        logging.info(shards)
        if (shards[0] == []):
            time.sleep(0.01)
        else:
            break

if __name__ == "__main__":
    format = "%(asctime)s.%(msecs)03d [%(threadName)s]: %(message)s"
    logging.basicConfig(format=format, level=logging.INFO,
                        datefmt="%H:%M:%S")

    logging.info("Deleting test-index")
    response = requests.delete(f"{es_url}/{index_name}", auth=my_auth, verify=False)
    logging.info(response)

    x = threading.Thread(name="X ", target=run)
    y = threading.Thread(name=" X", target=run)
    x.start()
    time.sleep(0.025)
    y.start()

Below is one of the outputs that I got after running the above script (it is necessary to adjust the sleep time at the end depending on the machine to catch the short period of time when the issue exists):
15:38:18.130 [MainThread]: Deleting test-index
15:38:18.159 [MainThread]: <Response [200]>
15:38:18.170 [X ]: Creating test-index
15:38:18.197 [ X]: index exists
15:38:18.198 [ X]: getting shards
15:38:18.210 [ X]: [[]]
15:38:18.233 [ X]: index exists
15:38:18.233 [ X]: getting shards
15:38:18.241 [X ]: index create response <Response [200]>
15:38:18.241 [X ]: Waiting for YELLOW
15:38:18.245 [ X]: [[{'state': 'STARTED', 'primary': True, 'node': 'dUGB49_fRcGcVonQgXvB_g', 'relocating_node': None, 'shard': 0, 'index': 'text-index', 'allocation_id': {'id': 'Q6Ya3noUTQuN5BLXWvXhcQ'}, 'relocation_failure_info': {'failed_attempts': 0}}]]
15:38:18.254 [X ]: health response <Response [200]>
15:38:18.254 [X ]: getting shards
15:38:18.266 [X ]: [[{'state': 'STARTED', 'primary': True, 'node': 'dUGB49_fRcGcVonQgXvB_g', 'relocating_node': None, 'shard': 0, 'index': 'text-index', 'allocation_id': {'id': 'Q6Ya3noUTQuN5BLXWvXhcQ'}, 'relocation_failure_info': {'failed_attempts': 0}}]]

In the above log, it can be seen that while one thread is waiting for Elasticsearch to finish creating the index, the other thread gets information that index exists, but the list of shards is empty, and after sleeping 0.01 second the list of shards is returned correctly.
Version Info
OS: Linux
JVM: OpenJDK 17.0.9
Spark: 3.3.2
ES-Spark: 8.13.1
ES: >= 8.6.0

Thanks for all of the work in narrowing this down! Do you know if the problem happens with es-hadoop versions older than 8.6 with elasticsearch versions 8.6 or newer? That is, given that es-hadoop has not changed much lately, I'm assuming that the bug is actually in elasticsearch (rather than es-hadoop). But it would be good to have confirmation of that.

Do you know if the problem happens with es-hadoop versions older than 8.6 with elasticsearch versions 8.6 or newer?

Actually you already answered that question by providing a python script that hits elasticsearch directly, so disregard my question!

It looks like the bug is a race condition in es-hadoop that has been there for years, and was probably made more likely when the desired-balance allocator was introduced in 8.6.0. Here's what es-hadoop does when indexing a new document:

Checks if the index exists with a HEAD request
If not, does a PUT to create it, and then calls _cluster/health with wait_for_status=YELLOW
Makes a query to get the shards for the index

The problem is that if two spark tasks are inserting documents into a nonexistent index at the same time, the first task does all the steps above. The second task comes in and sees that the index exists, so it skips the the second step (critically the wait_for_status=YELLOW check). So it immediately queries for the shards, which might not exist yet because the index is still being created.
It looks like we're only using the shards to get a node to write to. And there's no guarantee that the shards returned by _search_shards will even be there when we actually go to write. So the best change here might be to just pick a node at random if the list of shards is empty.

if set of shard is empty, wait for YELLOW
get shards again - now it should pass

There's no guarantee that shards won't move immediately after we fetch them.

throw an exception if seconds attempt for getting shards fails

But there's also no real harm in letting elasticsearch deal with this. If there is some real problem allocating shards at all, then elasticsearch is going to let us know anyway.
For those reasons, I'm just returning a random node if he shard check fails. This will probably almost always only be hit only when two splits are trying to create an index at the same time.


WIP: Use AWS Cognito for user management

Configures an AWS Cognito user pool with two app clients (dashboard, web) and uses Next Auth with CognitoProvider to manage authentication and sessions.
Nukes everything referencing Hydra and Clerk as they are not needed anymore.
Future work

Create custom login/signup pages, right now we have AWS default
Create Cognito workflow trigger on user signup to create database user
Create service methods for finding and querying AWS Cognito users

Vercel fails bc environment variables aren't updated there


Releases missing

Describe the bug
The "Releases" page is now missing, causing the documentation to be out of date.
If this change was expected, please could you let us know how we can download the binaries without compiling them ourselves?
To Reproduce
Go to the repo - https://github.com/tsl0922/ttyd and see there's no longer any releases.
Screenshots

Oh, they seem to be back now.  Not sure if that was a temporary GitHub glitch, but thanks!


auto hints is not available under the scope of cycle statement in python file

VSCode Version: 1.28.2
OS Version: Windows 10
Python Version：3.6.5
Q&A：
auto hints is not available under the scope of cycle statement, such as for or while...etc, in python file,
but if i print something with auto hints outside these scope, then it will work fine

https://github.com/Microsoft/vscode-python/


Tagging my own 3D Data for Segmentation

@ranahanocka @emepetres @bertjiazheng : I found a link in the wiki, any update on this https://github.com/ranahanocka/MeshCNN/wiki/Segmentation ?
I want to tag parts and train my own 3D segmentation model ?

Hi @nitish11  ,
There is no fully automatic tool for segmenting shapes, if there was - you probably wouldn't need to use MeshCNN -> could just use that tool instead :)
You can try searching for unsupervised shape segmentation approaches. For example, one of the co-authors of MeshCNN did such a work on shape segmentation, and another work which propagates one segmented model to others structure.
There might also be some semi-automatic tools for doing this.
In a quick google search, I came across this: Protrusion-oriented 3D Mesh Segmentation

Hi @ranahanocka, thanks for your reply,
I wanted to understand how do we create dataset for training a 3D model segmentation?

Did you try going through the segmentation example from the README?

I tried  through the segmentation example from the README too. And now, I want to apply it on my own dataset, but I don't know any method to create soft_labels for seseg files


JavaDoc/KDoc of CompanionModel.kt misses code examples

The class-doc-comment of CompanionModel.kt contains code examples surrounded by HTML tags. These code examples are stripped off by the KDoc plugin (because of the HTML tags). According to KDoc documentation, Markdown should be used.

@cschabl :+1:
I assume these commits resolved the issue, can I close  it now?

Yes.


feat: add Elastic metrics provider

Description
fixes #3727
Hey @mowies I have started creating custom KeptnMetricsProvider for Elastic and now I have integrated some methods.
For now the methods purpose are-

NewElasticProvider: Creates a new KeptnElasticProvider with an Elasticsearch client.
FetchAnalysisValue: Runs a query to get analysis results and returns the metric value.
EvaluateQuery: Runs a metric query for the last 30 minutes and returns the metric value.
runElasticQuery: Executes a query on Elasticsearch and returns the result.
extractMetric: Gets the metric value from the Elasticsearch result.

also, if you can, please provide some unit tests for your new code :)

Thanks for the contributions, please see the additional comments on the code. One question tho, did you manually tried the implementation with Keptn? Seems to me that currently won't work, as the new provider is not present in the list of supported providers. If possible please add it and try it out manually.
Also additional question, would it be possible to create a full e2e test for the provider? Would be awesome if we could be able to test it as part of our CI

ya I can create full e2e test for the provider btw can you brief me above lines I didn't understood this "manually tried the implementation with Keptn"

Thanks for the contributions, please see the additional comments on the code. One question tho, did you manually tried the implementation with Keptn? Seems to me that currently won't work, as the new provider is not present in the list of supported providers. If possible please add it and try it out manually.
Also additional question, would it be possible to create a full e2e test for the provider? Would be awesome if we could be able to test it as part of our CI

ya I can create full e2e test for the provider btw can you brief me above lines I didn't understood this "manually tried the implementation with Keptn"

What I mean is using the elastic metric provider with Keptn, this means setting up an application, monitor it and fetch some data with the elastic metrics provider, used the data for Evaluations and then use Keptn to deploy the application.

Thanks for the contributions, please see the additional comments on the code. One question tho, did you manually tried the implementation with Keptn? Seems to me that currently won't work, as the new provider is not present in the list of supported providers. If possible please add it and try it out manually.
Also additional question, would it be possible to create a full e2e test for the provider? Would be awesome if we could be able to test it as part of our CI

ya I can create full e2e test for the provider btw can you brief me above lines I didn't understood this "manually tried the implementation with Keptn"

What I mean is using the elastic metric provider with Keptn, this means setting up an application, monitor it and fetch some data with the elastic metrics provider, used the data for Evaluations and then use Keptn to deploy the application.

The thing is I am not familiar with elk much so can it be like once pr is merged then users who use elk can use it?

Thanks for the contributions, please see the additional comments on the code. One question tho, did you manually tried the implementation with Keptn? Seems to me that currently won't work, as the new provider is not present in the list of supported providers. If possible please add it and try it out manually.
Also additional question, would it be possible to create a full e2e test for the provider? Would be awesome if we could be able to test it as part of our CI

ya I can create full e2e test for the provider btw can you brief me above lines I didn't understood this "manually tried the implementation with Keptn"

What I mean is using the elastic metric provider with Keptn, this means setting up an application, monitor it and fetch some data with the elastic metrics provider, used the data for Evaluations and then use Keptn to deploy the application.

The thing is I am not familiar with elk much so can it be like once pr is merged then users who use elk can use it?
I am familiar with code part implementation and till now I feel the provider is mostly correct and the test cases also just a minor change required.

I understand, but part of the implementation should be a e2e/integration test, which will require to deploy the provider and test the correct functioning of the provider with Keptn. In this case I would suggest getting in contact with the author of the issue regarding some more guidance about deploying and using the provider. Therefore we can verify the correct functionality of the provider and potentially also add some configurable parameters, that are needed in the provider

Thanks for the contributions, please see the additional comments on the code. One question tho, did you manually tried the implementation with Keptn? Seems to me that currently won't work, as the new provider is not present in the list of supported providers. If possible please add it and try it out manually.
Also additional question, would it be possible to create a full e2e test for the provider? Would be awesome if we could be able to test it as part of our CI

ya I can create full e2e test for the provider btw can you brief me above lines I didn't understood this "manually tried the implementation with Keptn"

What I mean is using the elastic metric provider with Keptn, this means setting up an application, monitor it and fetch some data with the elastic metrics provider, used the data for Evaluations and then use Keptn to deploy the application.

The thing is I am not familiar with elk much so can it be like once pr is merged then users who use elk can use it?
I am familiar with code part implementation and till now I feel the provider is mostly correct and the test cases also just a minor change required.

I understand, but part of the implementation should be a e2e/integration test, which will require to deploy the provider and test the correct functioning of the provider with Keptn. In this case I would suggest getting in contact with the author of the issue regarding some more guidance about deploying and using the provider. Therefore we can verify the correct functionality of the provider and potentially also add some configurable parameters, that are needed in the provider.
Another option for the e2e test might be to use mock-server for mocking the responses of the provider, like it's done here. Therefore there is no need for you to actually deploy the provider locally. Please have a look at this option.
In that case, we can maybe ask the author of the issue @arkaonline to test the implementation for us once it's ready and merged before actually releasing the feature. But the e2e test mocking the provider is still needed and the PR shouldn't be merged without it.

Okay so let me go through these and first create the e2e test mocking feature. Also yes the issue author can help us to test the full provider.

@Bharadwajshivam28  @odubajDT I can surely help you test it out.
Please share with me the ELK provider files that needs to be added and the steps I need to add them.
Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

so for now I think I should make the e2e tests ready and then @arkaonline can help us in testing the provider once the code is merged?
CC- @odubajDT

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

so for now I think I should make the e2e tests ready and then @arkaonline can help us in testing the provider once the code is merged?
CC- @odubajDT

First, the implementation needs to be finished and covered by unit tests, afterwards we should aim for a integration/e2e test with using the mock server. When this is finished, we can ask @arkaonline to test Keptn with the new provider and afterwards we can proceed with merging the PR.

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

so for now I think I should make the e2e tests ready and then @arkaonline can help us in testing the provider once the code is merged?
CC- @odubajDT

First, the implementation needs to be finished and covered by unit tests, afterwards we should aim for a integration/e2e test with using the mock server. When this is finished, we can ask @arkaonline to test Keptn with the new provider and afterwards we can proceed with merging the PR.

Okay cool so I will Focus on the unit tests and e2e test with the mock server.
Also can you please share some information to start with the e2e test?

You should use chainsaw and mock-server how it's done for example here

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

so for now I think I should make the e2e tests ready and then @arkaonline can help us in testing the provider once the code is merged?
CC- @odubajDT

First, the implementation needs to be finished and covered by unit tests, afterwards we should aim for a integration/e2e test with using the mock server. When this is finished, we can ask @arkaonline to test Keptn with the new provider and afterwards we can proceed with merging the PR.

Okay cool so I will Focus on the unit tests and e2e test with the mock server.
Also can you please share some information to start with the e2e test?

You should use chainsaw and mock-server how it's done for example here

Okay so this for the e2e test right?

@Bharadwajshivam28 @odubajDT I can surely help you test it out. Please share with me the ELK provider files that needs to be added and the steps I need to add them. Also , I believe "Elastic" has to be added as supported provider name in helmchart . is that right ?

Thank you! Yes you are right, we are missing multiple places now. When the implementation will be ready for testing, we will reach out to you. :-)

so for now I think I should make the e2e tests ready and then @arkaonline can help us in testing the provider once the code is merged?
CC- @odubajDT

First, the implementation needs to be finished and covered by unit tests, afterwards we should aim for a integration/e2e test with using the mock server. When this is finished, we can ask @arkaonline to test Keptn with the new provider and afterwards we can proceed with merging the PR.

Okay cool so I will Focus on the unit tests and e2e test with the mock server.
Also can you please share some information to start with the e2e test?

You should use chainsaw and mock-server how it's done for example here

Okay so this for the e2e test right?

Hey @odubajDT I saw the e2e test files you shared so I had one question:
can you please give me information about getting started on e2e tests implementation for the provider I am creating? tbh I am new in e2e testing

@Bharadwajshivam28 any updates on this?

@Bharadwajshivam28 any updates on this?

I am working on this and will finish the logic and unit tests by today and for the e2e tests I will make it finish in upcoming 1-2 days


Revamped chart properties

Rewrote much of the chart properties/settings stuff, hoping to get to
something stable that handles all of the necessary cases without being
too fancy. Currently, it's rough, but it's a start.
The biggest changes are (1) the change in paradigm that properties
(formerly settings) should never be set by the chart and (2) charts can
provide a displayable panel to configure themselves. The first change is
motivated by performance and simplicity. For example, charts shouldn't
and don't need to change their own title, so why were they able to? This
means that the plot window is not specified by properties. The second
change is a nice trick I saw while studying IntelliJ.

sounds good, I will review
On Sun, Nov 8, 2015 at 11:50 PM, John Zeringue<EMAIL_ADDRESS>wrote:

Rewrote much of the chart properties/settings stuff, hoping to get to
something stable that handles all of the necessary cases without being
too fancy. Currently, it's rough, but it's a start.
The biggest changes are (1) the change in paradigm that properties
(formerly settings) should never be set by the chart and (2) charts can
provide a displayable panel to configure themselves. The first change is
motivated by performance and simplicity. For example, charts shouldn't
and don't need to change their own title, so why were they able to? This
means that the plot window is not specified by properties. The second
change is a nice trick I saw while studying IntelliJ.
You can view, comment on, or merge this pull request online at:
https://github.com/CIRDLES/Topsoil/pull/236
Commit Summary

Revamped chart properties

File Changes

M app/build.gradle
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-0 (1)
M app/src/main/java/org/cirdles/topsoil/app/chart/ChartWindow.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-1 (13)
M build.gradle
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-2 (1)
M core/src/main/java/org/cirdles/topsoil/chart/BaseChart.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-3 (11)
M core/src/main/java/org/cirdles/topsoil/chart/Chart.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-4 (18)
M core/src/main/java/org/cirdles/topsoil/chart/Displayable.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-5 (11)
M core/src/main/java/org/cirdles/topsoil/chart/JavaScriptChart.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-6 (24)
D
core/src/main/java/org/cirdles/topsoil/chart/setting/SettingOperation.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-7 (28)
D
core/src/main/java/org/cirdles/topsoil/chart/setting/SettingOperationFactory.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-8 (28)
D
core/src/main/java/org/cirdles/topsoil/chart/setting/SettingScope.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-9 (113)
D
core/src/main/java/org/cirdles/topsoil/chart/setting/SettingTransaction.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-10 (56)
D
core/src/main/java/org/cirdles/topsoil/chart/setting/SettingTransactor.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-11 (43)
M
core/src/main/java/org/cirdles/topsoil/chart/standard/ScatterplotChart.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-12 (13)
A
core/src/main/java/org/cirdles/topsoil/chart/standard/ScatterplotChartPropertiesPanel.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-13 (56)
M
core/src/main/java/org/cirdles/topsoil/chart/standard/UncertaintyEllipseChart.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-14 (13)
A
core/src/main/java/org/cirdles/topsoil/chart/standard/UncertaintyEllipseChartPropertiesPanel.java
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-15 (97)
A
core/src/main/resources/org/cirdles/topsoil/chart/standard/ScatterplotChartPropertiesPanel.fxml
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-16 (17)
A
core/src/main/resources/org/cirdles/topsoil/chart/standard/UncertaintyEllipseChartPropertiesPanel.fxml
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-17 (59)
M
core/src/main/resources/org/cirdles/topsoil/chart/standard/scatterplot.js
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-18 (44)
M
core/src/main/resources/org/cirdles/topsoil/chart/standard/uncertaintyellipsechart.js
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-19 (54)
M
core/src/main/resources/org/cirdles/topsoil/chart/topsoil_js/topsoil.js
https://github.com/CIRDLES/Topsoil/pull/236/files#diff-20 (53)

Patch Links:

https://github.com/CIRDLES/Topsoil/pull/236.patch
https://github.com/CIRDLES/Topsoil/pull/236.diff

—
Reply to this email directly or view it on GitHub
https://github.com/CIRDLES/Topsoil/pull/236.

--
Jim Bowring
C. Richard Crosby Distinguished Teaching Co-Chair
Principal Investigator, www.CIRDLES.org, www.github.com/cirdles
Computer Science
College of Charleston
66 George Street
Charleston, SC 29424
Google Voice:<PHONE_NUMBER> (preferred)
Google Email<EMAIL_ADDRESS>Office:
Harbor Walk East (360 Concord Street) Room 308
843.953.0805
http://stono.cs.cofc.edu/~bowring/
<EMAIL_ADDRESS>R. Buckminster Fuller (1972):
If humanity is to survive aboard our planet, it must become universally
literate and preoccupied with inherently cooperative Comprehensive
Anticipatory Design Science in which every human is concerned with
accomplishing the comfortably sustainable well-faring of all other humans.


Collapse three seperate texture storage methods into render_target_set_override()

Currently, there's three separate methods to override the textures on a render target (added recently in #65227):

render_target_set_override_color(RID p_render_target, RID p_texture)
render_target_set_override_depth(RID p_render_target, RID p_texture)
render_target_set_override_velocity(RID p_render_target, RID p_texture)

This PR collapses them into a single method:

render_target_set_override(RID p_render_target, RID p_color_texture, RID p_depth_texture, RID p_velocity_texture)

You'll really only ever want to set all of the override textures on the render target at the same time, and doing it in a single method call makes it much easier to cache the framebuffer that is created as a result.
The Vulkan renderer already has a sophisticated caching mechanism, so it has no problem. But I'd like to implement caching of these overridden framebuffers for OpenGL (in #67775), where we don't have any caching yet. In XR, this caching is particularly important, because the overridden textures will be swapped every frame.
I already discussed this with @BastiaanOlij on RocketChat and he seemed open to this change!

Thanks!


KeyError

Thanks a bunch for this fix!
I tested a SP500 download but some tickers were rejected: CAT, DRI, GRMN
Companies are good. I ran your suggested native code as a test and same issue.
The following tickers failed to download:
DRI
KeyError                                  Traceback (most recent call last)
 in ()
1 import fix_yahoo_finance as yf
----> 2 data = yf.download("dri", start="2017-01-01", end="2017-4-30")
3 print(data)
/home/kent/anaconda3/lib/python3.6/site-packages/fix_yahoo_finance/init.py in download(tickers, start, end, as_panel, group_by, auto_adjust, progress, *args, **kwargs)
207     # return single df if only one ticker
208     if len(tickers) == 1:
--> 209         data = dfs[tickers[0]]
210
211     return data
KeyError: 'DRI'
Any suggestions? Thank you.

FYI, I observed the same issue with both GRMN, CAT and others when running a looped download of many symbols (my tests are w/ 7000+ tickers). I tested the failed tickers manually using a juypter notebook running the function one ticker at a time. CAT and GRMN specifically seemed intermittent in that sometimes data was retrieved while others no data was retrieved. I reran the loop with only failed tickers and then they then downloaded. Seems there still may be some issues w/ the Yahoo end point.

You're right.  I test again this morning and now they work. Weird....thanks.

I've added thread support in 0.0.9, so it should run faster than a loop.
Just add threads=INT to your code. I use threads=len(tickers)//10) myself...
Upgrade using:
$ pip install fix_yahoo_finance --upgrade --no-cache-dir

Can you please check if this is working better for you?


HTML

HTML
User Story
As a boot camp student
I want the prework notes to be strucred on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

added code


Make isoinfo an optional dependency

How can I start the archiving process? All I see is this:

There is no "start" button.

Turns out I didn't have the command isoinfo which is provided by the cdrtools package. Please add it to the dependencies list in the README.

The functionality of reading disks should not depend on the knowledge of some meta information. So, please:

Make the isoinfo dependency optional by ignoring any of its errors
Document that dependency (cdrtools package)  in the README


 They're making our repo huge, and removing them didn't make our repo smaller because git keeps them around as objects in case we want to check out an old commit that contained them.
What you need to do

Don't run git pull or git merge
Instead, do this:

$ git fetch origin # this command messes everything up locally. If you try to diff <my-branch> with origin/<my-branch> you'll see a ton of diffs
$ git remote add msteffenpach git@github.com:msteffen/pachyderm.git
$ git fetch msteffenpach master
$ git checkout <my-branch>
$ git rebase --onto origin/master msteffenpach/master #Branch is now migrated locally
$ git push -u origin +my-branch # github.com/pachyderm/pachyderm/<my-branch> is now migrated

Once all of your local branches have been migrated (including master—to migrate master just run the steps above with master in place of <my-branch>, except don't run the final git push, since origin/master is already up-to-date), you can run:
$ git remote remove msteffenpach
$ git gc

and that'll delete all of the superfluous binaries above from your local copy of the pachyderm repo
Details
The binaries are:

src/plugin/vault/main (27 MB)
etcd (18 MB)
examples/opencv_dominant_color_example/dominantColor (10 MB)
src/cmd/pfs/pfs (9 MB)
examples/opencv_dominant_color_example/dominant_color (6 MB)

I collected this list using an altered version of the script here: https://stubbisms.wordpress.com/2009/07/10/git-script-to-show-largest-pack-objects-and-trim-your-waist-line/. I'll check this altered version in once the change is finished.
To solve this, I'm going to use git filter-branch to rewrite every commit that contained one of the binaries above, and force push to pachyderm/pachderm. Once I do this, nearly every commit in github's copy of the pachyderm repo will be different. To keep your branches and PRs intact, you'll have to replay any local commits you've made to them onto the new commits that are present in the upstream repo. The commands above show how to do this. How the commands work is visualized below.
How the commands work
Starting state of a clone of the pachyderm repo on your local machine:
my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o(root)
   ↑
   master, origin/master

----------------
After you run `git fetch origin` locally:

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (root)
   ↑
   master

   o──o──o──o──o (new root)
   ↑
   origin/master

----------------
After remote add msteffenpach + git fetch msteffenpach:

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (root)
   ↑
   master, msteffenpach/master

   o──o──o──o──o (new root)
   ↑
   origin/master

----------------
After
$ git checkout my-branch
$ git rebase --onto origin/master msteffenpach/master
$ git push -u origin +my-branch

   o──o──o──o──o (root)
   ↑
   master, msteffenpach/master

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (new root)
   ↑
   origin/master

----------------
After
$ git checkout master
$ git rebase --onto origin/master msteffenpach/master
$ git push -u origin +my-branch

   o──o──o──o──o (root)
   ↑
   msteffenpach/master

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (new root)
   ↑
   master, origin/master

----------------
After
$ git remote remove msteffenpach

   o──o──o──o──o (root)

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (new root)
   ↑
   master, origin/master

----------------
After
$ git gc

my-branch
 │  origin/my-branch
 ↓  ↓
 o──o──o
        ╲
   o──o──o──o──o (new root)
   ↑
   master, origin/master

Closing due to staleness


When CipherText.Save() is converted to string, the hash is huge!

Hello! I am using the Microsoft SEAL dotnet library. I am using this for a project of mine and whenever I save a ciphertext and convert it to a string, the length is 182,468! Is this intended?
Here is my code:
`
var encryptionParams = new EncryptionParameters(SchemeType.BFV);
encryptionParams.PolyModulusDegree = 4096;
encryptionParams.CoeffModulus = CoeffModulus.BFVDefault(4096);
encryptionParams.PlainModulus = new SmallModulus(512);
var context = new SEALContext(encryptionParams);
var keygen = new KeyGenerator(context);
var encryptor = new Encryptor(context, keygen.PublicKey);
var stream = new MemoryStream();
var cipherText = new Ciphertext();
encryptor.Encrypt(new Plaintext(1.ToString()), cipherText);
cipherText.Save(stream);
Console.WriteLine(BitConverter.ToString(stream.ToArray()).Replace("-", "").Length);
`

Long story short - yes, this is normal.
You can get an idea of how the size is computed from thisissue

Is there any way to make the size shorter?

By default, building seal should pick up zlib and use it for serialization on all objects including the cipher, but you should check your build steps to ensure it picks it up. It could provide some substantial savings.
Other than that, the encryption parameters have a direct affect on the size of Plaintexts and Ciphertexts. In order to significantly reduce the size, you would need to adjust your application to be able to use a lower polymodulus degree.

How do you convert the data to a string? Base64? In any  case, the message expansion in encryption is indeed significant, which is why it's important to always utilize the batching capabilities of BatchEncoder (or CKKSEncoder) to as great of an extent as possible.

Thank you so much. I was used the BatchEncoder to cram as many numbers into one ciphertext.


fix： baidu voice init params type error

百度语音的sdk初始化时会对参数进行strip，所以要保证是字符串。否则会报错

[INFO][2023-06-09 11:04:01][bridge.py:30] - create bot baidu for voice_to_text
[WARNING][2023-06-09 11:04:01][baidu_voice.py:59] - BaiduVoice init failed: 'int' object has no attribute 'strip', ignore
[ERROR][2023-06-09 11:04:01][chat_channel.py:267] - Worker return exception: 'BaiduVoice' object has no attribute 'client'

https://github.com/Baidu-AIP/python-sdk/blob/e9add82014dec830a1b84c2b145a9faf40a84fc7/aip/base.py#LL42C11-L42C11

👍


wireguard: 20160708 -> unstable-2016-07-22

Motivation for this change
package name fix and version update.
Things done

[ ] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks for merging!


operator-no-unspaced false positive with a string containing a closing brace

The following pattern is considered a problem, although there are no actual math operators:
.foo {
	background-image: url('data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="412" height="395" viewBox="0 0 412 395"><style>.bar{}</style><g fill-rule="evenodd"><path d="M208.805 393.054c45.057-161.12 43.75-161.848 76.32-276.73l7.832 4.523c4.255 2.458 7.738.448 7.738-4.455V61.606c8.643-30.27 15.416-53.66 17.4-60.693h35.287L412 55.217l-38.498 33.27 29.11 31.473-191.86 273.094c-.938 1.542-2.244 1.19-1.947 0zm20.96-347.278c1.733 0 3.148.958 3.148 2.147V76c0 1.186-1.415 2.15-3.147 2.15H182.37c-1.742 0-3.153-.96-3.153-2.15V47.923c0-1.185 1.41-2.147 3.153-2.147h47.396z"/><path d="m288.265 14.688-52.14 30.1c.605.92.973 1.98.973 3.136v28.078c0 1.457-.565 2.77-1.496 3.83l52.663 30.402c3.59 2.073 6.535.377 6.535-3.764V18.456c0-4.145-2.944-5.836-6.535-3.768zM175.03 76V47.923c0-1.15.368-2.21.966-3.13l-52.14-30.105c-3.588-2.068-6.53-.376-6.53 3.768v88.013c0 4.14 2.938 5.84 6.53 3.76l52.66-30.405c-.926-1.06-1.487-2.37-1.487-3.827z"/><path d="M201.248 393.054h1.947c-45.05-161.12-43.753-161.848-76.32-276.73l-7.833 4.523c-4.253 2.458-7.737.448-7.737-4.455V61.606C102.66 31.336 95.89 7.946 93.9.913H58.617L0 55.217l38.494 33.27-29.11 31.473 191.864 273.094z"/><circle cx="204.572" cy="122.538" r="14.231"/><circle cx="204.572" cy="207.156" r="14.231"/><circle cx="204.572" cy="291.785" r="14.23"/></g></svg>');
}

CLI result:
 2:144   ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:144   ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:151   ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:151   ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:152   ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:152   ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:174   ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:174   ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:175   ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:175   ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:585   ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:585   ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:586   ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:586   ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:946   ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:946   ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:947   ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:947   ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1171  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1171  ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:1172  ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:1172  ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1217  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1217  ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:1218  ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:1218  ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1263  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1263  ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:1264  ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:1264  ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1308  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1308  ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:1309  ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:1309  ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1312  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1312  ✖  Expected single space after ">"   scss/operator-no-unspaced
 2:1313  ✖  Expected single space before "<"  scss/operator-no-unspaced
 2:1313  ✖  Expected single space after "<"   scss/operator-no-unspaced
 2:1318  ✖  Expected single space before ">"  scss/operator-no-unspaced
 2:1318  ✖  Expected single space after ">"   scss/operator-no-unspaced

Removing the closing brace will make it not considered a problem.
Versions:

stylelint-scss: 4.2.0
stylelint: 14.6.0

Looks like a bug!

I have the same bug:
This
 $accordion-button-active-icon: url("data:image/svg+xml;charset=utf-8,<svg version='1.1' id='Capa_1' xmlns='http://www.w3.org/2000/svg' x='0' y='0' viewBox='0 0 512 512' xml:space='preserve'><style>.st0{fill:#{$accordion-icon-color-active};stroke:%231d4dcd;stroke-width:32;stroke-linecap:round;stroke-linejoin:round}</style><path class='st0' d='M256 112v288M400 256H112'/></svg>") !default;
output:
styles/base/_init.scss
 109:316  ✖  Expected single space before "<"  scss/operator-no-unspaced
 109:316  ✖  Expected single space after "<"   scss/operator-no-unspaced
 109:323  ✖  Expected single space before ">"  scss/operator-no-unspaced
 109:323  ✖  Expected single space after ">"   scss/operator-no-unspaced
 109:324  ✖  Expected single space before "<"  scss/operator-no-unspaced
 109:324  ✖  Expected single space after "<"   scss/operator-no-unspaced
 109:371  ✖  Expected single space before ">"  scss/operator-no-unspaced
 109:371  ✖  Expected single space after ">"   scss/operator-no-unspaced
 109:372  ✖  Expected single space before "<"  scss/operator-no-unspaced
 109:372  ✖  Expected single space after "<"   scss/operator-no-unspaced
 109:377  ✖  Expected single space before ">"  scss/operator-no-unspaced
 109:377  ✖  Expected single space after ">"   scss/operator-no-unspaced

but this [another background url] works as expected:
$accordion-button-icon: url("data:image/svg+xml;charset=utf-8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='#{$accordion-icon-color}' stroke='%231d4dcd' stroke-width='32' stroke-linecap='round' stroke-linejoin='round' d='M400 256H112'/></svg>") !default;


Some configuration options don't work correctly

Describe the bug
The configurations hide_label_metrics, hide_items_closed_count, non_mentioning_links, report_title, and output_file don't work correctly in some conditions.
The write_to_markdown function has 15 arguments.
https://github.com/github/issue-metrics/blob/215054856ab0e929a22910979d738624b90c0b3a/markdown_writer.py#L82-L97
However, it is called with 14 arguments in issue_metrics.py because it lacks the argument hide_label_metrics.
https://github.com/github/issue-metrics/blob/215054856ab0e929a22910979d738624b90c0b3a/issue_metrics.py#L324-L338
This causes the argument hide_label_metrics and the following arguments not to work correctly.
To Reproduce
To set a query that does not have subquery type:discussions in it and returns at least one issue.
Expected behavior
The configurations hide_label_metrics, hide_items_closed_count, non_mentioning_links, report_title, and output_file=output_file work.
Screenshots
No response
Additional context
No response

Well that's not good! I'll get a fix up for this. Thanks for the details!!


Leave year adjustment

Hi All,
This app is great, does anyone know what variable controls the leave year?
Currently Leave year starts in January and ends in December, I''m looking to change this so leave year starts Apil and ends on May.
Any pointers welcome :)
Kind Regards
Alex

Hi,
Have you managed to do it? I would also like to introduce such a change.
Cheers,
Adam

Hi Adam,
Not yet, have been looking at the code, but no luck yet. Any pointers from from anyone would really help :)
Kind Regards,
Alex

Agree, a most desired feature.
I have been looking into this myself too and I might try and attempt a pull request to fix.
However, it appears to be a duplicate issue to both #218 and #114
As an fyi, #114 has a bit list of files for where to start


Updating CI files

This commit updates all CI scripts to the latest version

This is currently failing on Jenkins on all platforms, and all environments:
  1) IPLD format resolver (local) "before all" hook:

     Error: second argument must be a CID

      at new Block (node_modules/ipfs-block/src/index.js:22:13)

      at dagEthBlockList.util.serialize (test/resolver.spec.js:25:23)

      at Object.exports.serialize (src/util.js:25:3)

      at Context.before (test/resolver.spec.js:23:26)


Include a timeline scrubber allowing users to examine animations

This was added in the following PR https://github.com/playcanvas/playcanvas-viewer/pull/96


Feature Request: Killing Processes

maybe hitting dd while a process is highlighted does a kill -9 to it?
After slack/gitter/discord/whatever memory and cpu sucking electron "app" runs for 2-3 days w/out restart I need an easy way to kill all the renamed Google Chrome Helpers so I can have my 12gb of memory each one needs back. Because chat obviousely needs more ram than BF1

A shortcut for this would be great, but an alternative suggestion for a shortcut: k prompts for a signal number (with SIGTERM as a default), and K simply does kill -9.

sounds like a good idea. we can show a dialog to kill the highlighted process with the help of blessed.form after pressing k (similar to top)

sounds good! as long as kk is still an instant kill :)

This will be a very useful function!

Would love to see this as well!

@aksakalli how about d shows the dialog, but dd just kills? for people who don't want to be questioned.


Delayed metrics part3

Separate rollup of delayed metrics - part 3
     * Added new config parameter to decide if we want to re-roll entire slot for delayed metrics or only the delayed ones.
     * Changes to astyanax/datastax RW's to update locator with its last update time stamp when reading from metrics_locator table.
     * Update metrics_locator with the locator all the time if it is a delayed metric. If not, update only if its not present in the cache like we do today.
     * Instead of re-rolling the entire slot when we get delayed metrics, we only re-roll the ones that were delayed.
     * Added instrumentation to visualize locators that are being rolled/re-rolled.

Coverage increased (+0.1%) to 78.573% when pulling 3a8caa30c86f51b85e82a1ea5064b838004335c5 on ChandraAddala:delayed-metrics-part3 into e6de32ff53ed32cc348adbff8ae3692415820e1d on rackerlabs:master.

lgtm

@usnavi @shintasmith @VinnyQ @izrik I found out that this does not handle some scenarios and also it is very performance intensive. I have some ideas I want to try. I am closing this PR for now. I will submit a new one later.


Floating box (footnote, citation) is trimmed by page limits

If the citation/footnote is too close to the margin, the floating box gets trimmed like shown below.  This was captured on Google's Chrome Version 54.0.2840.71 (64-bit) for Linux.
From: http://thomaspark.co/project/pubcss/demo/acm-sig-sample-web-theme.html

Thanks for the heads up. It seems to be a Chrome bug with rendering elements that overflow on body, since it displays fine on Firefox and Safari. But I've added a workaround so it should look nice in Chrome now.

That was quick!  Thank you!  :-)
Fix confirmed.


Add a ManifestWork cleanup finalizer to Application so the Applicatio…

…n is not deleted until the associated ManifestWork is also deleted
/hold
Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/lgtm

ApplicationSet did not automatically add the proper ArgoCD finalizer after I insert a custom finalizer inside the ApplicationSet's Application template. This solution is not good for now. We will just have to stick with the ArgoCD finalizer for now.


The Drag and Drop demo does not work

Hey guys,
I was browsing the docs and noticed the drag and drop example with Sortable.js does not work:
http://intercoolerjs.org/examples/sortablelist.html
Sure its a simple fix!

PR #242

Seems fixed by #242

yep!  Thanks for pointing that out :)


Call to undefined function Pulsestorm\Pestle\Runner\main()

Fatal error: Call to undefined function Pulsestorm\Pestle\Runner\main() in /var/www/html/prosehat/pestle.phar on line 7
i'm very new with .phar file.
step I have done :

curl -LO http://pestle.pulsestorm.net/pestle.phar
php pestle.phar list

I got that error when using pastle.phar, can you help me ? thanks

@anggakes  Thanks for giving pestle a try!  Can you let us know which version of PHP you're running?  You can figure ou;t which version of PHP you're using by running the  php -v command.  With this information, we'll be better able to help you.

I'm using hip-hop virtual machine (hhvm) - 3.13.1 on Apache 2 engine
Is hhvm not currently support .phar file ?

@anggakes Could you paste in the full contents of running $ php -v?

@anggakes I was able to reproduce the problem on hhvm -- it looks like you're not alone.  I'd recomend using stock PHP to run pestle.phar until we know more about the issue.
https://github.com/facebook/hhvm/issues/5139
Thank you for reporting -- I wouldn't have known about this otherwise!

Thank you for your response, so the problem is from hhvm.
Thanks alan


Gisaid/Genbank download tweaks

Summary:

What: Update endpoint usage
Ticket: none
Env: https://template-download-frontend.dev.czgenepi.org/

To get fasta file, use the ORG_API.SAMPLES_FASTA_DOWNLOAD endpoint and put the public repository in the request body:
{
        "sample_ids": [sample.public_identifier],
        "public_repository_name": "GISAID",
}

To get submission template, use the new /v2/orgs/{group.id}/samples/submission_template endpoint and pass:
   {
        "sample_ids": [sample.public_identifier for sample in samples],
        "date": today.strftime("%Y-%m-%d"),
        "page": "0",
        "public_repository_name": "GenBank",
    }

Use the "content-disposition" header to get the filename.
Demos:
Notes:
I added resp.headers["Access-Control-Expose-Headers"] = "Content-Disposition" to the submission_template endpoint for the filename to work.  Extra eyes on this would be great since I was just being a sheep and following what i thought should be there...
Checklist:

[x] I merged latest <base branch>
[x] I manually verified the change
[x] I added labels to my PR
[ ] I tested in multiple browsers
[ ] I added relevant unit tests
[ ] I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

👍

Removed chunking from the frontend including the multiple file callout.
Renamed GISAID Submitter ID to GISAID User Name.
Filtered to only send completedSampleIds and not failed ones.


Remove creation ops in clamp

Remove usage of creation ops in clamp to fix unsupported int data type error message

Merged to main


Avoid recursion in String methods

Let's try this once more...
Use a map instead of the same object type so that the String method
doesn't infinitely recurse.

LGTM