404 error for HPO and Variant is wrong

Based on my test, the 401 code is fine for all 4 items (gene/hpo/individual/variant). But the 404 code is wrong for HPO and Variant, see below:
404 means a user has logged in (no matter what account), but the item he/she is looking for does not exist.
If a gene id not exist (like ENSG00000119685sdsd below), it returns code 404 as status, with a message that "Gene not found" in data:

However, if a HPO and variant not exist, it returns 200 (which is success code), and a bundle of wired thing in data.

By the way, the message format is better to be the same. Below is a 401 error for a gene, the key for error message is error, but in the first figure above, the key is message. It took me quite a long time to figure out...

@YuanTian1991, how do you do get the inspect debug to show the errors the way you screenshot? I'm using Chrome and Safari and, looking at Network tab but I can't figure out how you do.
BTW, right now variant returns 404 (so I think it's ok for you, right?) but hpo returns 500.
Could you review this issue and update us with what you'd like to see?

Hi @alanwilter
The frontend relies on redux to fetch data from API. So you can modify the code in redux/action to get the result printed in the console. For example here:
https://github.com/phenopolis/phenopolis_browser/blob/3278be74f668be98d1de6edfa9e71ab311905204/frontend/src/redux/actions/hpo.js#L9
and here:
https://github.com/phenopolis/phenopolis_browser/blob/3278be74f668be98d1de6edfa9e71ab311905204/frontend/src/redux/actions/variant.js#L9
After this line, add console.log(res). Then you should be able to see the returned data from Chrome devtool console.

Thanks @YuanTian1991, I did the changes above and when searching for an existing item, I can see the data object in the console, but when I try e.g. ENSG00000119685sdsd I got nothing, so I can't reproduce what you see.
So, I'd ask you to tell us if is still there an issue, and if yes, what is it. I use Inspect, tab Network and I can see 404 for gene and variant that do not exist, but when I try a fake hpo I got 500. So I'm asking to try this yourself and tell us what we still need to do, otherwise I'd close this ticket.

BTW @YuanTian1991 I think this is wrong in variant.js, line:
            payload: { code: 404, message: 'HPO not exist.' },

it should be Variant not exist.

Hi @alanwilter I have checked now it seems working well. The key thing I changed is to use status 400 as "404" missing item for variant.
However, I don't know why we can't use same standard to all 4 items? Like for gene/patient, we use 404 to indicate missing item, but for HPO we use 500, for variant we use 400?

Improved with #346


Docking score of Zinc Database

thanks for the work， and would you please help me the location or pathway to docking score with zinc database that you mentioned in the paper。

Hi,
Sorry for late answer. Currently we are not authorized to share the ZiNC subset with docking scores, but I'll try to obtain an approval for it and share the dataset.
As a workaround, you can dock the molecules from ZiNC on your own, using scripts from the package. Please refer to ZINC Baseline paragraph from the paper for details how we sampled the molecules.


My project is gone after the recent issue. My backups are also gone.

Describe the bug

Please help me recover my project.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-nbdlzn
Steps to reproduce
NA
Expected behavior
NA
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Same happened here. My username is ferhat38

Who do we reach out to?
Is there a support center I can reach out to?

same here. it deplolyed on its own as well and will not load my project. also using a different localhost port

same here


[MDS-2]I want you to upgrade the depended Apache Arrow library.

https://multiple-dimension-spread.atlassian.net/browse/MDS-2

LGTM


Implement basics of to_spec

Implements https://github.com/holoviz/lumen/issues/311

Codecov Report

Merging #317 (2942cc0) into master (74c5c27) will decrease coverage by 0.23%.
The diff coverage is 34.92%.

@@            Coverage Diff             @@
##           master     #317      +/-   ##
==========================================
- Coverage   68.00%   67.76%   -0.24%
==========================================
  Files          68       68
  Lines        6882     6925      +43
==========================================
+ Hits         4680     4693      +13
- Misses       2202     2232      +30

Impacted Files
Coverage Δ

lumen/state.py
72.67% <ø> (ø)

lumen/dashboard.py
77.96% <20.00%> (-2.60%)
:arrow_down:

lumen/target.py
77.24% <20.00%> (-1.39%)
:arrow_down:

lumen/base.py
82.99% <33.33%> (-1.46%)
:arrow_down:

lumen/views/base.py
61.64% <75.00%> (+0.07%)
:arrow_up:

lumen/filters/base.py
68.95% <100.00%> (+0.25%)
:arrow_up:

lumen/pipeline.py
61.57% <100.00%> (+0.19%)
:arrow_up:

lumen/sources/base.py
62.28% <100.00%> (+0.06%)
:arrow_up:

lumen/variables/base.py
78.23% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Organize the first week of pattern creation by creating issues in this repository and dividing the work with frontend dev

The goal is to develop the components in the following wireframes:

[ ] Members Dashboard => this is the replacement for the old home
[ ] Single Assembly Page
[ ] Single Campaign Page
[ ] Single Working Group Page
[ ] Single Proposal Overlay

For an explanation of the patterns, see the AppCivist UX Running Notes

replaced by Issue 1 on the new repo


GitHub actions: solve version conflict for frontend test

Problem: frontend test fails on new pull requests as latest prettier version is incompatible with Node v12.

Fix: this PR hardcodes latest available compatible prettier version (v.2.8.8).
This should fix failing tests for the following PRs:
https://github.com/kserve/models-web-app/pull/70 (should use the initial commit 11a7842 though, changes to other 2 files are unnecessary)
https://github.com/kserve/models-web-app/pull/74
https://github.com/kserve/models-web-app/pull/76

Thanks for the PR @tmvfb!
/lgtm
/approve


[eslint] duplicate conditions in indices and nodes API

What is the bug?
eslint shows two APIs have duplicate conditions.
yarn lint
yarn run v1.22.5
$ eslint .

/opensearch-js/api/api/indices.js
  1112:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if
  1115:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if
  1118:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if
  1127:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if

/opensearch-js/api/api/nodes.js
  169:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if
  180:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if
  183:14  error  This branch can never execute. Its condition is a duplicate or covered by previous conditions in the if-else-if chain  no-dupe-else-if

✖ 7 problems (7 errors, 0 warnings)

How can one reproduce the bug?
After eslint PR is merged

Go to '.eslintrc.json'
Remove ' "no-dupe-else-if": "off"'
Run yarn lint
See error

What is the expected behavior?
Research on this
Remove duplicate conditions

duplication:
https://github.com/opensearch-project/opensearch-js/blob/5328c314608dda8d783799d32be3fe927ae1e935/api/api/nodes.js#L116-L131

Good day @ananzh !
I want to let you know that I am working on this issue. Thank you for this opportunity!


setting --storage.tsdb.min-block-duration and --storage.tsdb.max-block-duration

Hi, I'ld like to specify both of these settings manually but can't find any way in the operator API to do it, is it possible?

I see, @Bplotka seems its not happening :/

Can you elaborate on the use case you why you would want to tune these flags?

It's for using thanos, @Bplotka can elaborate better than me

Yea, for thanos, running local compaction is not advised, so --storage.tsdb.min-block-duration should equal to --storage.tsdb.max-block-duration and all should equal to 2h.
I think currently Prometheus default for --storage.tsdb.max-block-duration is some calculation based on retention, so current Thanos manifests are wrong in Prom operator. (If I am right with defaults)

That makes sense. I'm struggling to figure out whether I would just like a "Thanos mode" or allow overriding these values. (cc @mxinden)
Thanks for elaborating, this should definitely be possible.

Yea, I think just Thanos is fine for now, until some strong argument will appear someday for general override option. Also for Thanos --storage.tsdb.min-block-duration=--storage.tsdb.max-block-duration=2h is totally enough (: Not need to actually modify anything further.

--storage.tsdb.min-block-duration=--storage.tsdb.max-block-duration=2h

Yeah that was my thought exactly. I would like to discuss a deeper Thanos integration with @mxinden once he's back from vacation (monday). Ideally the sidecar is automatically added and configured appropriately from the Prometheus object as well. This would likely be an experimental feature at first, but I think it would be a good idea.

I came across this posting a while back and we were wondering if it is still optimal to keep min = max = 2 hr?  We would like to keep less metrics in memory and were hoping to reduce this time but wanted to confirm it would not cause issues.  Can someone please let me know what to expect if I were to lower this to min = max = 1 hr?
Thanks,

As compression gets better the closer we get to the 2h time, you’re not going to win a whole lot with this. There is a general problem in prometheus in regard to needing better memory management for the head block, which is currently all in memory. That’s what needs to be improved.

Thank you for the follow-up.

Is there a way to lower the 2-hour mark for testing purposes only?
I need to migrate a setup of Prometheus Operator and Thanos sidecar (running a very old Thanos version - 0.4) to latest Thanos (0.15). For that some tests need to be conducted whether the uploaded data in the object store is correct and will be nice if that can be done faster with smaller pieces of data.

This level of configuration is needed for the Thanos Receive component.
https://github.com/thanos-io/thanos/issues/2114


implemented configurable Bigtable write batch size.

Make BulkMutation Batch Size Configurable (v0.5.1)

I am a prism dev
Who wants to stabilize heroic
So that I can focus on new functionality

Design & Implementation Notes

See this section in the Stability RFC for details

Looks reasonable to me 👍  might be good to get another pair of eyes on it but +1


DeepExplainer no longer supports DenseData

DeepExplainer previously supported DenseData for background data, but now it seems it no longer does.  I noticed however that the documentation says that only background data of numpy or pandas dataframe is supported for Tensorflow:
https://github.com/slundberg/shap/blob/890d85b49228c061a0d46ad76e0bbaa6b506d015/shap/explainers/deep/__init__.py#L42
If the documentation says this, is this then by design, and there was a conscious decision to no longer support DenseData for the background?  Or was that a minor bug and we should actually still support DenseData like the other APIs (and wouldn't it make sense to use KMeans to summarize the background)?

Good point. It was not an intentional design choice. It was just I didn't consider weighting the samples when first building deep explainer. I don't think it would be hard to do. In fact we could just wrap any dataframe or numpy array as dense data when in init to keep a consistent interface. This is also something we could do for TreeExplainer eventually since for our new feature_dependence="independent" assumption we need a dataset just like DeepExplainer.


Fix on allow-hostnames

https://github.com/vinteumorg/Floresta/pull/286#issuecomment-2499116642
As mentioned in this comment the hostanames features was relying on a feature gate on windows (only on tests). Instead, i made the resolve_connect_host function to always specificate localhost while setting the ipv4.... This change was tested and developed on a native windows system.

cc @Davidson-Souza

satisfacting clippy

ACK b27cec1


Working through the tutorial

See https://hexworks.org/posts/tutorials/2018/12/12/how-to-make-a-roguelike-project-setup.html

Apologies for adding this pull request on the upstream branch!


Stack Overflow when using Pandoc

Gist:
https://gist.github.com/RobbieMcKinstry/5f19e10b7c685d08ac21441801846dbd
Expected behavior and actual behavior
Expected: I expect the Tilt Pandoc template to render markdown files.
Observed: I'm getting a stack overflow exception.
Steps to reproduce the problem (from a clean middleman installation)

Create a new Middleman project.
Add the sample.html.md file from the gist to ./source/sample.html.md
Update config.rb to render markdown files using pandoc.
That is, append set :markdown_engine, 'pandoc' to the default config.rb as per the gist.
Install pandoc locally. brew install pandoc
Launch the middleman server with bundle exec middleman --verbose
Navigate to http://localhost:4567/sample.html

You should now be able to observe that the webserver has thrown a stack overflow error and that the webpage does not render. I included my stack trace as the stderr.txt in the gist.
Additional information
I noticed ruby-pandoc is not included in the Gemfile.lock. However, the tilt version in my Gemfile.lock is 2.0.7  (which includes support for pandoc) so it should depend on ruby-pandoc. Manually installing ruby-pandoc didn't do anything for me.
Pandoc version: pandoc <IP_ADDRESS>

Ruby version: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
Middleman version: Middleman 4.2.1
OS version:  OSX 10.12.4

Damn I forgot to include the gist. Will edit immediately....

Updated to include gist.

I think Pandoc needs a Tilt renderer?

@tdreyno Can you elaborate on that at all? :)
I'm not sure what you mean.


Fix Jsx Integration Test

I'm submitting a...
[x] Bug Fix
[ ] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[x] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[x] Tests for the changes have been added

Description
So I think that the reason these tests weren't passing before was due to the refactor making the paths in tsconfig out of date, they needed one else ../. Then I ran into a class of issues that's described in these GitHub issues while running yarn run integration:consumer:ngc:
https://github.com/angular/vscode-ng-language-service/issues/183
https://github.com/angular/angular/issues/16382
I fixed that issue by changing baseUrl to be ./ and now when I run yarn run integration:consumer:ngc I don't get any errors.
Sorry it took me so long to get to this @dherges!
Does this PR introduce a breaking change?
[ ] Yes
[x] No

@KyleMcNutt glad you figured out! Enjoy the christmas days!


Debugger is not working properly with LTO build in Mac OS X

Can't load debugging symbols in gdb session, when building JerryScript with LTO=ON option.
Reading symbols from build/bin/debug.darwin/jerry...
warning: `/tmp/lto.o': can't open to read symbols: No such file or directory.
(no debugging symbols found)...done.
(gdb) _

https://github.com/Samsung/jerryscript/pull/759 patch for just avoiding this issue in daily work. :)

https://github.com/Samsung/jerryscript/commit/4f4407121bb52de99be9b00f980a7802a54dcc53


handle 'genesis' events such as rebases

I'm sure this will change slightly after the lexicon refactor lands, but this is still strictly better for this codepath

gonna close this, its been effectively redone in other PRs


make store service configurable

The store service was born out of a misunderstanding ... we need to clean that up. This PR changes the default signing key store to nats, but allows configuring and using the old store service to running existing installations without changes to the deployment (if updating the configuratin).
The change does not need a migration as signing keys are just regenerated on the fly.
I don't know if the web ui will re download the signing key if it expired. I don't think it has a way of detecting that as the browser will handle the download. Maybe they should just forget the signing key ... every 5min? so it is periodically refetched?
I can see the ocis web ui being left open for a long time, so I set the new signing key TTL default to 12h. In the past it never expired, which IMO is a pad practice.
cc @mmattel @wkloucek @kobergj @kulmann

Removing the store service is great, as it reduces the list of services not having a description about their purpose 🤣 @kobergj

Migration is not needed as the keys are ephemeral and can just be regenerated.

I forgot to not start the store service by default. will change the default services.


Replace misattributted quote with an appropriate Hawking one

Context
This quote was not updated when the file was renamed in #27600. I am correcting that to avoid spreading any misinformation about quote attribution, with a quote I think is appropriate for our docs.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

The merge queue build has started. Click here to see all failures if any.


Add active members metric

Fixes #498.
On main Nova dashboard:

On team detail page:

Oh yeah, here's it with the total number of members on a team (including inactive) too:


Updated maintainers rubygem

Description
Updated maintainers rubygem
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing this for https://github.com/opensearch-project/opensearch-ruby/pull/26


Fix building with G++ on Mac OS X

Patch courtesy of Roger.

Thanks to both of you for the PR by proxy. :-)


Chunk problem

Hello, thanks for your work.
I might have found an odd behaviour.
It seems that with a single chunk or two chunks, the time order changes.
See
import datetime

from Historic_Crypto import HistoricalData

signal = 'ETH-EUR'
granularity = 86400
days = 300 # try 300 or 301
date_start = (datetime.datetime.now() - datetime.timedelta(days + 1)).strftime('%Y-%m-%d-00-00')
date_end = (datetime.datetime.now() - datetime.timedelta(1)).strftime('%Y-%m-%d-00-00')

print(HistoricalData(signal, granularity, date_start, date_end).retrieve_data(), signal)

As in the comment, try with 300 (single chunk) and 300 (two chunkes)
300 => from new to old
301 => from old to new

Hi Carlo,
Thanks for spotting this, I assumed that the sort_index argument would take care of this - it is likely due to the different calls within the if/else branch relating to the 300 or larger sample.
Best,
David


Add support for dry-run, show-config, human-readable file names

Features implemented:

--dry-run: talks to the Reddit API and just displays the list of images to download
--human-readable: Use human readable file names instead of MD5 hashed file names
--show-config: Shows the configuration that reddsaver uses (with sensitive credentials masked)

Can't we combine the best of both worlds in the naming scheme, i.e.: canonical_filename_hash? Then we avoid duplicated downloads and get a nice filename also.

Can't we combine the best of both worlds in the naming scheme, i.e.: canonical_filename_hash? Then we avoid duplicated downloads and get a nice filename also.

Thanks @CitronSorcier  - I've appended the post name, a unique string that looks like t3_AbcDE. So even if you use the canonical format, there will be no duplicated downloads.

Thanks @CitronSorcier  - I've appended the post name, a unique string that looks like t3_AbcDE. So even if you use the canonical format, there will be no duplicated downloads.


Add Update Method to DbSet

Why not add Update method to DbSet class
Method Signature: DbSet.Update(Func<T, bool> predicate, T);
So to update a row in a table:
Employee employee = new Employee{FirstName = "Mohamed"};
context.Employees.Update(x => x.Id == 1, employee);
this line should produce this sql statement: update Employee set FirstName = 'Mohamed' where Id = 1;
If for example, user want to update multiple rows this method will help him/her.
example: context.Employees.Update(x => 1 == 1, new Employee{DepartmentId= 1});
this line  should produce this sql statement: update Employee set DepartmentId = 1 where 1 =1;

EF core should have more functionalities for C/U/D operations without using change tracker - directly composing and execution the query. Most of the times we don't need the change-tracker. It only adds overhead.

Many developers use AsNoTracking method, so these types of C/U/D operations should be implemented

Duplicate of #795


Add option to allow reviewers to only see submissions in external review status

Fixes #2819
Add description here.

@frjo, I just noticed that this setting is only used on /apply/submissions/all and for submission detail page but not for submissions listed on reviewer dashboard. I think we were only looking at the list of all submissions at the time we build it https://github.com/HyphaApp/hypha/issues/1182 and missed the dashboard.


Letter complete experience.

Play a sound when the user presses the correct letter.

@steveruizok Are you working on this? If not, I can give it a try :)

Go for it!
My only notes would be NOT to play a sound when the wrong key is pressed; we have a different game where that's the case and it's the most annoying thing in the world lol

Haha yeah, that sounds about right
Is there an idea to animate the current letter as well? I dont know how "kid-friendly" the game is supposed to be, but a slight bounce or something feels like it would fit quite well!

This was fixed in #9 😊


VS 2022 & Android 12 supported?

Please let me know if Visual Studio 2022 and Android 12 targeting are supported.

Yes. Syncfusion Essential UIKit supports Visual Studio 2022 for Windows with Android 12. To learn more about UIKit Control, please check the following user guide documentation.
https://help.syncfusion.com/xamarin/uikit/gettingstarted#extension-for-windows


Added a bit more content to special variables in shell

Added some descriptions to a few of the special variables which I found initially confusing.

@ronreiter please review and merge


Transmit the prefetch list to snapshotter during runp pod.yaml

Hello, in this PR, I start an NRI plugin and subscribe to pod creation event. The plugin invokes the RunPodSandbox method to obtain  prefetch list file path recorded in pod.yaml when monitoring the pod creation command. Then send the prefetch list file path to snapshotter through the specified socket API. After receiving prefetch list file path, snapshotter will save the content and add --prefetch-files parameter when building nydusd command to customize prefetch files content. I will submit the modifications to snapshotter in the next PR.

cc @sctb512 @changweige

@billie60 It seems to have a broken build CI https://github.com/containerd/nydus-snapshotter/actions/runs/5282088960/jobs/9556557174?pr=493

Please refine the commit name. At least, remove the WIP prefix

cc @changweige PATL again, thanks!

Is the commit Merge branch 'main' into prefetchfiles-nri purposed carried on this PR ? Could you squash or fix it?

test

Can we have a doc to describe how to deploy the NRI plugin and an associated e2e test would be greater

Hopefully, we can have following PRs:

Add related documents
Define a Makefile target to build the plugin in the CI job
Add e2e test


Bid/Ask for options chains are either all zero or mostly zero

This issue started 10/5/21 as far as I am aware. Options bid/ask information (particularly for ticker = ^SPX) starting coming up almost exclusively as zeroes. The expiration list populates, but when I iterate over the expirations, the mkt data for bid ask comes up as largely zero. Last price is populated but the last trade date timestamp looks stale. Any thoughts on where this is a permanent issue or something that will resolve over time?
import yfinance as yf
import pandas as pd

spx = yf.Ticker("^SPX")
spx_expirations = spx.options

for spx_exp in spx_expirations:

    spx_opt = spx.option_chain(spx_exp)
    spx_join = pd.merge(spx_opt.calls,
                          spx_opt.puts,
                          on ='strike',
                          how ='inner')
    spx_join.sort_values(by=['strike'], ascending=True)
    spx_df = spx_join.drop(columns=['lastPrice_x','lastTradeDate_x','change_x', 'percentChange_x', 'volume_x', 'openInterest_x', 'impliedVolatility_x', 'inTheMoney_x', 'contractSize_x', 'currency_x', 'lastTradeDate_y', 'lastPrice_y', 'change_y', 'percentChange_y', 'volume_y', 'openInterest_y', 'impliedVolatility_y', 'inTheMoney_y', 'contractSize_y', 'currency_y'
    ])
    print(spx_df)

Tested October 13 with an exact copy of your code.
Prices are returned normally. Attaching two examples:
       contractSymbol_x  strike   bid_x  ...    contractSymbol_y    bid_y   ask_y
0    SPX231215C00100000   100.0  4114.2  ...  SPX231215P00100000     0.00     0.0
1    SPX231215C00200000   200.0  4015.9  ...  SPX231215P00200000     0.15     0.7
2    SPX231215C00300000   300.0  3917.7  ...  SPX231215P00300000     0.00     2.2
3    SPX231215C00400000   400.0     0.0  ...  SPX231215P00400000     0.00     0.0
4    SPX231215C00500000   500.0  3719.7  ...    SPX231215P06900000  2566.80  2590.8
131  SPX231215C07000000  7000.0     8.5  ...  SPX231215P07000000     0.00     0.0
132  SPX231215C07100000  7100.0     7.5  ...  SPX231215P07100000     0.00     0.0
133  SPX231215C07200000  7200.0     6.7  ...  SPX231215P07200000  2857.30  2881.3
134  SPX231215C07300000  7300.0     6.0  ...  SPX231215P07300000  2956.80  2980.8

[135 rows x 7 columns]

      contractSymbol_x  strike   bid_x  ...    contractSymbol_y  bid_y  ask_y
0   SPX230616C00200000   200.0     0.0  ...  SPX230616P00200000    0.0   10.0
1   SPX230616C00400000   400.0  3844.5  ...  SPX230616P00400000    0.0   10.0
2   SPX230616C00600000   600.0     0.0  ...  SPX230616P00600000    0.0   30.0
3   SPX230616C02700000  2700.0     0.0  ...  SPX230616P02700000   82.4   88.5
4   SPX230616C03300000  3300.0  1143.9  ...  SPX230616P03300000  165.9  177.4
5   SPX230616C03350000  3350.0     0.0  ...  SPX230616P03350000    0.0    0.0
6   SPX230616C03500000  3500.0     0.0  ...  SPX230616P03500000  204.3  216.3
7   SPX230616C03600000  3600.0     0.0  ...  SPX230616P03600000  226.5  237.7
8   SPX230616C03700000  3700.0     0.0  ...  SPX230616P03700000  250.3  265.7
9   SPX230616C03725000  3725.0     0.0  ...  SPX230616P03725000  256.5  272.3
10  SPX230616C03775000  3775.0     0.0  ...  SPX230616P03775000    0.0    0.0
11  SPX230616C03800000  3800.0     0.0  ...  SPX230616P03800000  275.8  290.7
12  SPX230616C03850000  3850.0   727.8  ...  SPX230616P03850000  289.0  307.3
13  SPX230616C03900000  3900.0   694.0  ...  SPX230616P03900000  303.4  324.2
14  SPX230616C03950000  3950.0     0.0  ...  SPX230616P03950000  317.3  337.8
15  SPX230616C03975000  3975.0     0.0  ...  SPX230616P03975000    0.0    0.0
16  SPX230616C04000000  4000.0   600.0  ...  SPX230616P04000000  333.0  353.9
17  SPX230616C04025000  4025.0     0.0  ...  SPX230616P04025000    0.0    0.0
18  SPX230616C04050000  4050.0     0.0  ...  SPX230616P04050000  350.2  371.3
19  SPX230616C04075000  4075.0     0.0  ...  SPX230616P04075000    0.0    0.0
20  SPX230616C04100000  4100.0   559.7  ...  SPX230616P04100000  366.5  385.7
21  SPX230616C04125000  4125.0     0.0  ...  SPX230616P04125000  375.9  397.3
22  SPX230616C04150000  4150.0     0.0  ...  SPX230616P04150000  384.6  403.8
23  SPX230616C04175000  4175.0     0.0  ...  SPX230616P04175000  393.2  414.8
24  SPX230616C04200000  4200.0   497.7  ...  SPX230616P04200000  402.5  424.1
25  SPX230616C04225000  4225.0     0.0  ...  SPX230616P04225000  411.9  433.5
26  SPX230616C04250000  4250.0   467.3  ...  SPX230616P04250000  421.5  443.1
27  SPX230616C04275000  4275.0   451.4  ...  SPX230616P04275000  431.3  452.9
28  SPX230616C04300000  4300.0   436.5  ...  SPX230616P04300000  441.3  462.9
29  SPX230616C04325000  4325.0   422.9  ...  SPX230616P04325000  451.4  470.6
30  SPX230616C04350000  4350.0   407.6  ...  SPX230616P04350000  461.8  478.6
31  SPX230616C04375000  4375.0   394.2  ...  SPX230616P04375000  472.3  491.5
32  SPX230616C04400000  4400.0   379.4  ...  SPX230616P04400000  483.9  503.1
33  SPX230616C04425000  4425.0     0.0  ...  SPX230616P04425000    0.0    0.0
34  SPX230616C04450000  4450.0   352.0  ...  SPX230616P04450000  505.9  525.1
35  SPX230616C04475000  4475.0   339.3  ...  SPX230616P04475000  516.3  537.9
36  SPX230616C04500000  4500.0   326.1  ...  SPX230616P04500000  527.9  549.5
37  SPX230616C04525000  4525.0     0.0  ...  SPX230616P04525000  540.6  559.8
38  SPX230616C04550000  4550.0   299.7  ...  SPX230616P04550000  552.6  571.8
39  SPX230616C04575000  4575.0     0.0  ...  SPX230616P04575000  563.8  587.8
40  SPX230616C04600000  4600.0   275.7  ...  SPX230616P04600000  576.3  600.3
41  SPX230616C04625000  4625.0   263.7  ...  SPX230616P04625000  589.1  613.1
42  SPX230616C04650000  4650.0     0.0  ...  SPX230616P04650000    0.0    0.0
43  SPX230616C04700000  4700.0   229.5  ...  SPX230616P04700000  629.2  653.2
44  SPX230616C04725000  4725.0   218.8  ...  SPX230616P04725000    0.0    0.0
45  SPX230616C04750000  4750.0   208.4  ...  SPX230616P04750000  657.5  681.5
46  SPX230616C04800000  4800.0   192.3  ...  SPX230616P04800000  687.0  711.0
47  SPX230616C04825000  4825.0     0.0  ...  SPX230616P04825000  702.2  726.2
48  SPX230616C04850000  4850.0   173.6  ...  SPX230616P04850000  717.8  741.8
49  SPX230616C04875000  4875.0     0.0  ...  SPX230616P04875000    0.0    0.0
50  SPX230616C04900000  4900.0     0.0  ...  SPX230616P04900000    0.0    0.0
51  SPX230616C04950000  4950.0     0.0  ...  SPX230616P04950000    0.0    0.0
52  SPX230616C05000000  5000.0   125.4  ...  SPX230616P05000000  819.6  843.6
53  SPX230616C05100000  5100.0   100.8  ...  SPX230616P05100000  891.4  915.4
54  SPX230616C05700000  5700.0     0.0  ...  SPX230616P05700000    0.0    0.0

[55 rows x 7 columns]

Thank you! Yes I noticed the same after a couple days started pushing
prices through again (albeit a bunch of options with zero bid ask, just far
less of them).
On Wed, Oct 13, 2021 at 12:42 PM Victor Silva @.***>
wrote:

Tested October 13 with an exact copy of your code.
Prices are returned normally. Attaching two examples:
   contractSymbol_x  strike   bid_x  ...    contractSymbol_y    bid_y   ask_y

0    SPX231215C00100000   100.0  4114.2  ...  SPX231215P00100000     0.00     0.0
1    SPX231215C00200000   200.0  4015.9  ...  SPX231215P00200000     0.15     0.7
2    SPX231215C00300000   300.0  3917.7  ...  SPX231215P00300000     0.00     2.2
3    SPX231215C00400000   400.0     0.0  ...  SPX231215P00400000     0.00     0.0
4    SPX231215C00500000   500.0  3719.7  ...    SPX231215P06900000  2566.80  2590.8
131  SPX231215C07000000  7000.0     8.5  ...  SPX231215P07000000     0.00     0.0
132  SPX231215C07100000  7100.0     7.5  ...  SPX231215P07100000     0.00     0.0
133  SPX231215C07200000  7200.0     6.7  ...  SPX231215P07200000  2857.30  2881.3
134  SPX231215C07300000  7300.0     6.0  ...  SPX231215P07300000  2956.80  2980.8
[135 rows x 7 columns]
  contractSymbol_x  strike   bid_x  ...    contractSymbol_y  bid_y  ask_y

0   SPX230616C00200000   200.0     0.0  ...  SPX230616P00200000    0.0   10.0
1   SPX230616C00400000   400.0  3844.5  ...  SPX230616P00400000    0.0   10.0
2   SPX230616C00600000   600.0     0.0  ...  SPX230616P00600000    0.0   30.0
3   SPX230616C02700000  2700.0     0.0  ...  SPX230616P02700000   82.4   88.5
4   SPX230616C03300000  3300.0  1143.9  ...  SPX230616P03300000  165.9  177.4
5   SPX230616C03350000  3350.0     0.0  ...  SPX230616P03350000    0.0    0.0
6   SPX230616C03500000  3500.0     0.0  ...  SPX230616P03500000  204.3  216.3
7   SPX230616C03600000  3600.0     0.0  ...  SPX230616P03600000  226.5  237.7
8   SPX230616C03700000  3700.0     0.0  ...  SPX230616P03700000  250.3  265.7
9   SPX230616C03725000  3725.0     0.0  ...  SPX230616P03725000  256.5  272.3
10  SPX230616C03775000  3775.0     0.0  ...  SPX230616P03775000    0.0    0.0
11  SPX230616C03800000  3800.0     0.0  ...  SPX230616P03800000  275.8  290.7
12  SPX230616C03850000  3850.0   727.8  ...  SPX230616P03850000  289.0  307.3
13  SPX230616C03900000  3900.0   694.0  ...  SPX230616P03900000  303.4  324.2
14  SPX230616C03950000  3950.0     0.0  ...  SPX230616P03950000  317.3  337.8
15  SPX230616C03975000  3975.0     0.0  ...  SPX230616P03975000    0.0    0.0
16  SPX230616C04000000  4000.0   600.0  ...  SPX230616P04000000  333.0  353.9
17  SPX230616C04025000  4025.0     0.0  ...  SPX230616P04025000    0.0    0.0
18  SPX230616C04050000  4050.0     0.0  ...  SPX230616P04050000  350.2  371.3
19  SPX230616C04075000  4075.0     0.0  ...  SPX230616P04075000    0.0    0.0
20  SPX230616C04100000  4100.0   559.7  ...  SPX230616P04100000  366.5  385.7
21  SPX230616C04125000  4125.0     0.0  ...  SPX230616P04125000  375.9  397.3
22  SPX230616C04150000  4150.0     0.0  ...  SPX230616P04150000  384.6  403.8
23  SPX230616C04175000  4175.0     0.0  ...  SPX230616P04175000  393.2  414.8
24  SPX230616C04200000  4200.0   497.7  ...  SPX230616P04200000  402.5  424.1
25  SPX230616C04225000  4225.0     0.0  ...  SPX230616P04225000  411.9  433.5
26  SPX230616C04250000  4250.0   467.3  ...  SPX230616P04250000  421.5  443.1
27  SPX230616C04275000  4275.0   451.4  ...  SPX230616P04275000  431.3  452.9
28  SPX230616C04300000  4300.0   436.5  ...  SPX230616P04300000  441.3  462.9
29  SPX230616C04325000  4325.0   422.9  ...  SPX230616P04325000  451.4  470.6
30  SPX230616C04350000  4350.0   407.6  ...  SPX230616P04350000  461.8  478.6
31  SPX230616C04375000  4375.0   394.2  ...  SPX230616P04375000  472.3  491.5
32  SPX230616C04400000  4400.0   379.4  ...  SPX230616P04400000  483.9  503.1
33  SPX230616C04425000  4425.0     0.0  ...  SPX230616P04425000    0.0    0.0
34  SPX230616C04450000  4450.0   352.0  ...  SPX230616P04450000  505.9  525.1
35  SPX230616C04475000  4475.0   339.3  ...  SPX230616P04475000  516.3  537.9
36  SPX230616C04500000  4500.0   326.1  ...  SPX230616P04500000  527.9  549.5
37  SPX230616C04525000  4525.0     0.0  ...  SPX230616P04525000  540.6  559.8
38  SPX230616C04550000  4550.0   299.7  ...  SPX230616P04550000  552.6  571.8
39  SPX230616C04575000  4575.0     0.0  ...  SPX230616P04575000  563.8  587.8
40  SPX230616C04600000  4600.0   275.7  ...  SPX230616P04600000  576.3  600.3
41  SPX230616C04625000  4625.0   263.7  ...  SPX230616P04625000  589.1  613.1
42  SPX230616C04650000  4650.0     0.0  ...  SPX230616P04650000    0.0    0.0
43  SPX230616C04700000  4700.0   229.5  ...  SPX230616P04700000  629.2  653.2
44  SPX230616C04725000  4725.0   218.8  ...  SPX230616P04725000    0.0    0.0
45  SPX230616C04750000  4750.0   208.4  ...  SPX230616P04750000  657.5  681.5
46  SPX230616C04800000  4800.0   192.3  ...  SPX230616P04800000  687.0  711.0
47  SPX230616C04825000  4825.0     0.0  ...  SPX230616P04825000  702.2  726.2
48  SPX230616C04850000  4850.0   173.6  ...  SPX230616P04850000  717.8  741.8
49  SPX230616C04875000  4875.0     0.0  ...  SPX230616P04875000    0.0    0.0
50  SPX230616C04900000  4900.0     0.0  ...  SPX230616P04900000    0.0    0.0
51  SPX230616C04950000  4950.0     0.0  ...  SPX230616P04950000    0.0    0.0
52  SPX230616C05000000  5000.0   125.4  ...  SPX230616P05000000  819.6  843.6
53  SPX230616C05100000  5100.0   100.8  ...  SPX230616P05100000  891.4  915.4
54  SPX230616C05700000  5700.0     0.0  ...  SPX230616P05700000    0.0    0.0
[55 rows x 7 columns]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ranaroussi/yfinance/issues/846#issuecomment-942490664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV6GPOBD7EH7H6FRNG3TUCLUGWZF5ANCNFSM5FOX2UJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


PackageParser: Illegal reflective access by com.google.protobuf.repackaged.UnsafeUtil

When running with java 11 the IJ bazel console shows a stream of:
INFO: From Parsing java package strings for //services/foo:foo:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.repackaged.UnsafeUtil (file:/Users/$USER/Library/Application%20Support/IntelliJIdea2018.3/ijwb/aspect/tools/PackageParser_deploy.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.repackaged.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Looks like https://github.com/bazelbuild/intellij/pull/433 was an intended fix. IIUC the flags need to be in BUILD.aspect instead. Eg https://github.com/wcurrie/intellij/pull/1/files#diff-87833d0278b7ae3937c9d438dea20e33R22
Could we get this applied upstream please?

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.


Question: How to decrease execution time

Hi,
This is a question about execution time. I have seen that it takes 4-6 minutes to complete its job in Gitla CI which is long time for a pipeline. To be able to use it effectively I need to find a way to reduce this time. I have seen some good implementations for Java / Maven projects. It looks like it is possible to download libraries which are required by owasp for scanning (in a docker image) and then refer this to the dependency so that it will not try to install them again. it reduces time for 4 minutes to 1 minute.
I am wondering if this can be achieved for this package also for a Vue app. Which options should I use to define library path (which can be provided by a docker ) or any other suggestion?
Kind regards
Emre

I am also facing the similar issue. when i try to run owasp-dependency-check plugin for javascript project and point it to package-lock.json to scan,it takes around 20-25 mins to execute and generate report in the specified path.

I had this problem and after looking on various related sites for documentation, there are basically two answers:

Generate an NVD API Key and pass the key in as a command line arg - this gives some level of prioritisation in the NVD API calls
Use a data feed URL to bulk download historic CVEs as data files. There is a public mirror available, although on some pages there are discussions about the data feed mechanism being retired now that the V2 API is available (this would seem like a mistake, unless and until the API can handle the required volumes)

The CLI documentation describes the arguments needed to use both the API Key and the data feed.
I found some level of improvement from using the API Key, but the thing that really made a difference was the data feed mechanism which brought my compliance CI jobs back down to just a few minutes. Also, make sure you are using caching - set the data directory where the tool stores its cache files and database, then make sure that is cached and restored in your CI pipeline.

This NPM package serves as a wrapper for the official CLI only. So this question should be directed to the authors (https://github.com/jeremylong/DependencyCheck).
Try the CLI (https://jeremylong.github.io/DependencyCheck/dependency-check-cli/index.html) directly and if the time is the same (similar) than this package cannot do much more.


RFE : declare commons-net as an optionnal dependency

In the current state of java-totp, the commons-net is only used for NtpTimeProvider feature.
My suggestion would be to declare commons-net as an optional dependency, and update the documentation, to indicate that use of NtpTimeProvider requires an additional explicit declaration of  commons-net.
This would reduce the default transitive dependencies to the minimum required.
Resources :
https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
Workaround for user of you library that wish to reduce their transitive dependencies : exclude commons-net from their pom :
     <dependency>
      <groupId>dev.samstevens.totp</groupId>
      <artifactId>totp</artifactId>
      <exclusions>
        <!-- Exclude commons-net, it is used by samsstevens-topt for Ntp implementation, we don't use this -->
        <exclusion>
          <groupId>commons-net</groupId>
          <artifactId>commons-net</artifactId>
        </exclusion>
        <!-- Exclude jcommander, it is used by xzing in commandline, we don't use this -->
        <exclusion>
          <groupId>com.beust</groupId>
          <artifactId>jcommander</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

PS : thanks for providing this nice and simple library. 👍🏻👍🏻

Makes sense to me - I've created a quick PR which I think achieves this if you want to give it a look over?


Avoid issue with DI gen for arrayexprs.

As title. Alters a test looking for breakpoints on lines that uses
arrayexprs to not use arrayexprs as #7752 leads to the arrayexpr
referencing the source line repeatedly.
Fixes #7787

Am putting this into 0.55.1 (https://github.com/numba/numba/milestone/62). #7752 is in 0.55.1 and this fixes the problem caused by #7752 as reported in #7787.

Seems to be ok now: https://dev.azure.com/numba/ff1fe4d0-ed73-4f1c-b894-1d50a27e048f/_apis/build/builds/10911/logs/78
Note the:
(numba.tests.test_gdb_dwarf.TestGDBDwarf) ... ok
2022-01-26T12:47:43.3256589Z test_array_arg

in the details:

Details:
2022-01-26T12:47:31.0132118Z # Now run tests based on the changes identified via git
2022-01-26T12:47:31.0133611Z NUMBA_ENABLE_CUDASIM=1 $SEGVCATCH python -m numba.runtests -b -v -g -m $TEST_NPROCS -- numba.tests
2022-01-26T12:47:33.4847832Z Git diff identified 5 tests
2022-01-26T12:47:33.4849256Z Parallel: 5. Serial: 0
2022-01-26T12:47:33.4997556Z test (numba.tests.gdb.test_array_arg.Test) ... skipped 'needs subprocess harness'
2022-01-26T12:47:42.7649721Z test_basic (numba.tests.test_gdb_dwarf.TestGDBDwarf) ... ok
2022-01-26T12:47:43.3256589Z test_array_arg (numba.tests.test_gdb_dwarf.TestGDBDwarf) ... ok
2022-01-26T12:47:52.0595187Z test_conditional_breakpoint (numba.tests.test_gdb_dwarf.TestGDBDwarf) ... ok
2022-01-26T12:47:58.7994477Z test_break_on_symbol (numba.tests.test_gdb_dwarf.TestGDBDwarf) ... ok


Refactor environmental variable discovery into backend service

Environmental variable discovery in notebooks and scripts is
now handled by backend service extensible for additional
languages
Fixes #385
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@ajbozarth - mind taking a look at this, having some trouble with the typescript =)

I know this is WIP - but a quick comment.  I think this should be a GET request rather than a POST.  It could be modelled after the server contents API where a path is provided and a file's content is returned.  In this case, the response is JSON consisting of a list of env variable names.

Will add some details on my commits and how to test Thursday AM

In case anyone is interested in testing before the frontend piece is functional, here is a small script to request the API from a python file.
import json
import requests

relative_path = "elyra/examples/load.py"  # this must be relative to your base Jupyter server url
url = "http://localhost:8888"
token = "076face883f53f9dba6184ed99a9500ac077193e3a3fb0d7"  # run 'jupyter server list' to get token

server_url = f'{url}?token={token}'
api_url = f'{url}/elyra/contents/properties/{relative_path}'

with requests.Session() as session:
    session.get(server_url)
    xsfr_header = {'X-XSRFToken': session.cookies.get('_xsrf')}

    response = session.get(url=api_url,
                           headers=xsfr_header)
    print(json.dumps(json.loads(response.content), indent=4, sort_keys=True))

Here's a simple R script for testing as well, just throw it into a .r file
Sys.setenv(R_TEST = "testit", "A+C" = 123)

One issue I could use help with is related to pipeline node properties -- it's not rendering the Add Environment Variable button and I can't quite figure out why.

Next step will be testing. I've removed the frontend unit test as it is no longer useful. Looks like a few integration tests are failing as well, but hopefully that can be fixed after some frontend code cleanup.
My current plan of action for backend tests is to create a folder structure as below.

contents

file_parser.py
handlers.py
__init__.py
tests

test_contents_parser.py
resources

test_python_script.py
test_notebook.ipynb
...

The resources folder will contain various test files (.py, .r, and .ipynb). Each resource will be tested using the following snippet, comparing results to the expected output:
operation = FileParser.get_instance(filepath=[test_filepath])
model = operation.get_resources()

And then I'm thinking there should be a test resource for at least each of the following cases:

Python script with environment vars (and various ways of accessing them)
R script with environment vars (and various ways of accessing them)
Python-based Notebook with environment vars (and various ways of accessing them)
R-based Notebook with environment vars (and various ways of accessing them)
Python script with no environment vars
R script with no environment vars
Notebook with no environment vars
A file that does not exist

This is really great - the tests are excellent.
I'm wondering about the "no-language" and "unsupported-language" cases. I'm thinking we might want to log a warning message, but return an empty model - as if there were no entries found - since the client shouldn't get penalized for using a notebook or script language in which we don't support or can't detect. What do you think?

Yeah I was thinking that the error message popup is pretty intrusive for something that should be happening behind the scenes. I hadn't thought that it could be as simple as just returning an empty model though -- I like it!

Did we look into making the parsers more stateless?

Did we look into making the parsers more stateless?

I'm sorry, but how are they stateful?  All results are returned in a single call to get_resources().

Did we look into making the parsers more stateless?

I'm sorry, but how are they stateful? All results are returned in a single call to get_resources().

A parser is associated with the file path when you call get_instance, no? You can't for example have a python parser and say parse(fileA) and parse(fileB), right?

Also, what is the difference between the two class hierarchies for the same type of files (e.g. PyrhonFileParser and PythonScriptParser)?

Please check: https://github.com/akchinSTC/elyra/pull/3

@lresende - you've thrown a lot here, so I'm going to respond with sections indicating the various topics.
@kiersten-stokes - Please chime in if you like and I apologize in advance if I'm stating things to which you might disagree.
Statelessness

A parser is associated with the file path when you call get_instance, no?

Correct.

You can't for example have a python parser and say parse(fileA) and parse(fileB), right?

If there was a requirement to handle multiple files in a single request, then this might be valid, but there is no such requirement.  In addition, the current implementation is completely stateless so I'm not following your point.
FileParser().get_instance(path).get_resources() is a single-use instance per request - so how is it stateful?  No state lives across requests.  A request is received, processed, and completely satisfied prior to return.
I can't tell what parse(fileA) is - it looks like a function. However, one perfectly valid implementation of parse() would be:
def parse(filepath):
    return FileParser().get_instance(filepath).get_resouces()

Are you concerned about the heap size growing and shrinking with each file?  Please explain.
If we were to ever introduce the ability to support multiple files in a single request, I would keep this design but change get_resources() to async def (which we should probably do anyway now that I think about it) and then have the handler gather up the futures for each  FileParser.get_instance(file).get_resources() call in a list - and use asyncio.gather(*futures) so that they're processed in parallel.
Class Hierarchies
Regarding the class hierarchy and looking at your diagram, a better name for the ScriptParser hierarchies is probably CodeParser.
The file parsers understand the file structure corresponding to the file's suffix.  Clearly, a Notebook file parser needs to be different than a text file parser, but language-specific file parsers were implemented in anticipation of possibly handling files that have other structures.  For example, if we had a COBOL requirement, the COBOLFileParser would likely only process statements in the PROCEDURE DIVISION - similar to the NotebookFileParser only looking for code cells.
As you can see at the moment, the PythonFileParser and RFileParser classes are literally typed subclasses of FileParser which contain their appropriate script parser instances.
Each FileParser then has-a ScriptParser (or CodeParser if you prefer).  These parsers get down to the brass tacks of parsing a piece of code in the respective language.  It is necessary to have separate classes because Notebook _ files_ are language-agnostic, while their code cells are language-specific.
Rewrite
Looking at your rewrite, you've changed a couple of names (I do like ContentReader over FileParser), collapsed the file parsers into essentially two sets - generic text and notebook "readers", and then use static instances of the "code parsers".  Nothing really stands out as being any more stateless than what's implemented.
I personally think using a generic text parser for all things other than notebook files is a mistake, but everyone has their opinions - I know I certainly do. :smile:

Thanks for your feedback @kevin-bates.
To me, when you do FileParser().get_instance(filepath).get_resouces() that is using a stateful parser that, from that time, only works for the given filepath. While I agree a reader should be stateful as it provides code chunks from a given file, the parser should be generic and stateless, which is what I was trying to implement with ContentParser.parse(filepath) which in the current implementation should be equivalent to FileParser().get_instance(filepath).get_resouces() but you can do things like:
parser = ContentParser()
propertiesA = parser.parse(fileA)
propertiesB = parser.parse(fileB)

Note that I am not saying we have a requirement to parse multiple files, but the example above exemplifies the stateless characteristics as you can reuse the same parser to parse multiple files.
Related to the reader, when you say collapsed the file parsers into essentially two sets - generic text and notebook "readers", the idea behind this was to abstract reading code chunks, in notebooks we have a way to read them from code cells, while in files we read line by line. Are there any other characteristics and/or differences that I forget to identify/abstract? Everything else is not the responsibility of the reader, but should be handled by the parser which is dependent on the code language, no?
In summary, the idea behind my suggested changes was:

ContentParser is a Facade/Driver that hides all the complexity from the consumer

Stateless, and retrieve helpers described below when actually parsing a given file

The ContentParser uses a reader to retrieve code chunks, there is a reader for each way of reading code chunks:

File reader read code chunks line by line
NotebookReader read code chunks from code cells

Once the ContentParser read a code chunk, it parses it based on the code language using a PythonScriptParser or RScriptParser.

Yep - this will work just fine.  Can you please coordinate with @kiersten-stokes to merge your changes?

I left two minor comments, which are non-blocker. Otherwise LGTM. Let me know when it's ready to merge and I can merge.

@lresende Alright final touches are in and have been tested. I think it's ready!


[ISSUE #4540] Added service test cases for admin

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

@moremind Hello, common.cache.MemorySafeWindowTinyLFUMapTest.testWindowTinyLFU UT is failing in the build for some reason, I didn't make any changes to that file and it is passing in local

Codecov Report

Merging #4579 (652efa8) into master (9f602df) will increase coverage by 0.40%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4579      +/-   ##
============================================
+ Coverage     68.85%   69.25%   +0.40%
- Complexity     7746     7777      +31
============================================
  Files          1033     1033
  Lines         29609    29598      -11
  Branches       2682     2678       -4
============================================
+ Hits          20386    20498     +112
+ Misses         7617     7479     -138
- Partials       1606     1621      +15

see 28 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[QA] Pressing CAPS Lock Causes Avatar to Walk Automatically

Explorer Alpha build versions:

v0.20.0

Issue Description:
When pressing the CAPS Lock key, the avatar starts walking by itself without any additional input.
STR:

Launch explorer.
Navigate to any scene.
Press the CAPS Lock key on your keyboard.
Observe the avatar's movement.

Expected behaviour:
The CAPS Lock key should not affect avatar movement and should only toggle between uppercase and lowercase text input.
Current behavior:
https://github.com/user-attachments/assets/55b20819-7b1d-4633-96ae-32ff77afe402

Duplicated


Filter for ticks

What do you think about turning in addition values into somethink like filter of x? I mean the following possibility:
axis: {
  x: {
    tick: {
        values: function (x) {
           if(x.getDay() === 1) {
               return x;
           }
        }
    }
  }
}

Also that would be great to have such a possibility for y axis as well, for example, when you need to show areachart with y-values from 80 to 100% range that would be much nicer to display every second tick and gridline (i.e. 80, 82, 84, ...)

@masayuki0812
I can take this one.
How do i enlist?


Add brief section about external dependencies

Adds a brief note on what versions of external dependencies were used in CI. In future releases this section should link to an easy to understand test matrix for users.

LGTM


IMPROVEMENT in the README FILE of Code-Canvas

It would look better if this part is added at the end and also few more things can be added such as technology stack, etc
I would like to work on it. Please assign it to me under GSSOC'23.

assigned to @Anikinee
Complete this within 3-4 days and
Include a screenshot or deploy link to assess your project and thereafter include your project in the main code following the contributing.md guidelines.

assigned to @Anikinee Complete this within 3-4 days and Include a screenshot or deploy link to assess your project and thereafter include your project in the main code following the contributing.md guidelines.

Okay, thank you for assigning.


Deployment Keeps Showing Back-Off restarting failed container

I'm deploying external-dns with the attached yml file, but when it's in the cluster the deployment keeps showing up with "Back-off restarting failed container".  This happens when nothing else deployed to the cluster except the config file secret and the external dns deployment.
I'm not sure why this is happening, any suggestions?
AksExternalDNS-Deploy.txt
Here is the last message in the log for the deployment:
time="2019-05-09T14:43:09Z" level=fatal msg="failed to sync cache: timed out waiting for the condition"

There's an error in the ClusterRoleBinding. ExternalDNS never gets bound to the external-dns Role via the binding:
  apiVersion: rbac.authorization.k8s.io/v1beta1
  kind: ClusterRoleBinding
  metadata:
    name: external-dns-viewer
    namespace: external-dns-admin
  roleRef:
    apiGroup: rbac.authorization.k8s.io
    kind: ClusterRole
    name: external-dns
  subjects:
  - kind: ServiceAccount
    name: external-dns
<   namespace: default
>   namespace: external-dns-admin

Change the last line from namespace: default to namespace: external-dns-admin and let us know if that works.

Thank you for the help!  That appears to have worked!


[android] asynchronous blurring

The two new methods seems very particular to be included in ImageLoader, maybe you can improve the API to pass a transformation to be used in the particular place it's used.

So, the idea here is that you will cache the blur version of the images. Is it that important? aren't you worried that the blur versions will evict the more important ones, or create a constant eviction/rotation overall?

Well, my reasoning is that blurring is a costly operation and that should be cached. We don't blur that often to pose problems for the cache but if the user navigates back to the same screen he won't have to wait for blurring. It will be there (assuming he wasn't all over the app and the cached bitmap got evicted)

what if we don't blur at all? I know is a design decision, @marcelinkaaa what do you think if we get a blurred image that kind of fill reasonable well any background/contrast?

Are you guys talking about the blur just like on the first attached image?
Then - we should keep it. In the album section we should show entire album cover and blur makes the width of the screen fill in nicely.
But there is a little inconsistency on how we show things later - look at image 2 & 3.  On one the cover from the either left or right to the picture on the current screen is placed under a black overlay, on the other picture it is not.

@grzesiekrzaca I think we should tackle the inconsistency first, maybe that could give me more arguments to remove the blur.

I'm still very cautious on this change, big images in the same cache used for our list adapters will impact the performance heavily. Can you enable the picasso debug feature and tell me if you see a meaningful difference in the amount of eviction for the thumbnails images?

If the eviction number is high, think we should have multiple cache instances (saving to different locations, based on their names) something like:
ImageLoader.getInstance("myfiles", context)
ImageLoader.getInstance("search", context)
ImageLoader.getInstance("apollo", context)
and ideally be able to configure the maximum disk storage of each so we don't take too much space.

I think multiple instances would mean smaller caches and even more evictions. (Talking about the "worst cache" even if others are more stable) I'll look at the cache performance tomorrow and propose a course of action.

About the cache (values were taken from an S5):
Memory cache size is 19173961 bytes (~18,2 MB)
Disk is 52428800 bytes (50MB - max disk cache size)
When it comes to small images (thumbnails in My Files) the cache can hold hundreds of them
example: image://album/13-resize:96x96- 96 x 96 at 36864 so just  36KB
but when it comes to My Music things are not that great. There is no resize set so whatever the size it gets into the cache (That makes the disk portion of the cache redundant. And can lead to problems with super large images (OOMs) [on the main problem branch I added a hard 768x768 clamp. Now I'm thinking about computing that value depending on the size of the device(same could be done for thumbnails)]). This is usually around 200x200 and 600x600 (at least for me):
image://album/27- 200 x 200 at 160000 ~156 KB
image://album/79- 600 x 600 at 1440000 ~1,37 MB (this is displayed in a 540 x 540 square so an overkill even without consideration that it's just 3cm of screen and probably even less detailed image would look good )
but there are outliers like
image://album/1- 1072 x 1072 at 4596736 ~4,4 MB
and
image://album/13- 1460 x 1460 at 8526400 ~8,13 MB
the blurred image:
image://artist/Marcin Przybyłowicz-resize:1080x589-blurred- 1080 x 589 at 2544480 ~2,42 MB
So at the moment just going to the My Music (artists/albums) and scrolling through a page or two fills up the cache.
Also, the search screen images are quite big and quickly get thrown out of memory cache.
http://static.frostwire.com/images/overlays/jyant_love_overdose_overlay_1.jpg-resize:1080x572- 1080 x 572 at 2471040 ~2,36 MB
Speaking of the blurred bitmap there are 2 solutions (if we don't want it in the cache):

Don't store it in the cache. :)
Store smaller bitmap in the cache. (It's blurred so upscaling would make the blur stronger)
image://artist/Marcin Przybyłowicz-resize:540x295-blurred- 540 x 295 at 637200 ~622,2 KB

@aldenml

option 3: get rid of effing blurring :p
@aldenml should be answering soon

hehe
well yeah, that's an option too :) but I was trying to stay true to what @marcelinkaaa has said:

"Then - we should keep it.".

@grzesiekrzaca thanks for the analysis and numbers, question: Do you think is it possible (and good idea) to have a way to specify if an image will be cached or not, but still use ImageLoader?
@marcelinkaaa there are multiple technical benefits in no having the blur effect. Do you think an alternative solution (like a fixed background image) is acceptable from the UI point of view?

If calculating this blur on a downscaled version of the image doesn't cost much in terms of CPU/load time, let's just calculate it every time.
If it's expensive, then let's store a very small version of it, like you say, the smaller the more accentuated it will be and it won't cause too many evictions.
I'd also try to have multiple cache buckets for different purposes, kind of what we used to have, but using a single caching component (ImageLoader), this way when you browse my music, you don't get rid of things like the promo images on the home page.
also for search results, let's try to make sure we downsize all images coming in from some search results (like the youtube ones)

agree with on the fly calculation, and if possible use RenderScript for that, it should be off CPU and faster (API >= 17)

here's an old example w/renderscript, might need some fixes
https://futurestud.io/tutorials/how-to-blur-images-efficiently-with-androids-renderscript

Disabled caching and switched to renderscript

Now I'm starting to feel more comfortable with the change

after addressing my latest comments, I'm ready to merge this


SW-3731 Backfill planting site populations

Backfill the plant totals for planting sites, zones, and subzones. This overwrites
any existing values with the correct totals across all plantings.
This should be deployed as its own release so that it only runs when all the
server instances are already aware of these tables.

Current dependencies on/for this PR:

main

PR #1197

PR #1198

PR #1199   👈

This comment was auto-generated by Graphite.


prevent frozen redraw state on application error

view this diff ignoring whitespace by adding this query string ?w=
https://github.com/lhorie/mithril.js/compare/next...sjungwirth:next?w=1
This change is to prevent the frozen state where redraws will no longer happen in the case when an application error is encountered while redrawing. This can happen due to bad API responses or simply sloppy code, but it shouldn't result in the shutdown of the application.
Example:
A mobile user loses connectivity and is unable to reach the API to get data for the next view. Currently this can easily result in unexpected data in the view  which causes an exception such as Uncaught TypeError: Cannot read property 'id' of undefined. At least let the user try again after restoring connection, or performing other offline actions, instead of permanently freezing the redrawing engine.

jsfiddle demonstrating the problem: http://jsfiddle.net/sjungwirth/hcw0ufLb/1/

thanks!


App version?

Every phone has a camera. Can this be translated into an iOS or Android app so that the phone cam is used. Thereby no PC required!

A Google search indicates that it is possible to write Android Apps using Python, but getting them to work with OpenCV would be a problem. Using a single smart phone would not be convenient. You would have to securely mount the smartphone high above the board, and be able to climb up even higher to see the screen. I did think about using an old Android phone just to take pictures, but the Raspberry Pi Zero was clearly a better option.

Great. The point is that whatever the hardware, it should not necessitate the use of a computer. If it's a raspberry pi it should really be a standalone unit capable of being switched on, initialised etc. :)

The CamChess website gives instructions for installing CamChess on a $35 Raspberry Pi 4B. The camera is attached to a $5 Raspberry Pi Zero, which connects to the 4B via a USB cable, which both powers the Zero and carries data. When you power up the 4B, both the 4B and the Zero automatically boot up. You can run CamChess automatically on start up by running a start up script in the 4B. Similarly, you can run the camera server automatically on start up by running a start up script on the Zero. I plugged a keyboard and screen into the 4B. Alternatively, you could plug in an Official Raspberry Pi Touchscreen, but I have not tried that. You would then have a completely stand alone unit. There are also a variety of little screens that can be connected to a Raspberry Pi via GPIO pins, and you could use push buttons connected to GPIO pins rather than a keyboard. You would have to replace the Python code for the user interface to do that, but you would no longer need a desktop, and could save memory by running Raspberry Pi Lite. A $5 Raspberry Pi Zero would probably be too slow to run CamChess, but the new $15 Raspberry Pi Zero 2 W may be fast enough.

Another possible project would be to keep the Raspberry Pi Zero as a camera server and connect it to a smart phone via the USB cable. It appears to be possible for an Android application to use the USB port for TCP/IP communication. You could, in principle, run CamChess in an Android application, but you may have to translate CamChess into Java, and would certainly have to make other changes. I expect it would be easier on a Linux phone (e.g. PinePhone), but there are not many of those around, and they do not make good mobile phones.

A much easier project would be to run CamChess on the same Raspberry Pi that runs the camera server. (You would not then need a separate camera server and could simplify the Python code.) You would then just have one Raspberry Pi fixed above the chess board. You could control the Raspberry Pi using a remote desktop. I have used VNC Viewer on an old iPad 2 to do that.

Great ideas there. I have zero coding skills :(


playbooks unified vs not unified

Are both playbooks necessary? unified and normal? If not, we should remove one of them.

https://gitlab.com/automationiberia/aap-cac/superadmin-workshop-template/-/merge_requests/1

+1 to have only a single playbook :-D
IMHO, the controller and the CasC will be more clean to manage. But we need more opinions, we can discuss about this and the rest of issues on Friday.


Check message origin

Previously we've been sending window.postMessages with a wildcard * on the origin, this PR specifies origins and makes assertions of where messages are sent from in the DOM tree.

As far as I understand the supervisor iframe cannot reliably determine the root window origin, however, when we receive a message we can determine if it came from the root window, so we store the message origin and subsequent responses will be addressed to that same origin.


MyST website toolbar should switch colors with the dark / light theme

I noticed some visual elements don't change their colors with dark / light mode. Just noting here for future reference:
Attribution icons

Social media and theme button itself

Ah, perfect, thanks for catching these!!
I switched over to/created scienceicon system a few weeks ago:
https://www.npmjs.com/package/scienceicons
Must have missed a few dark mode flags!

Fixed the license icons, the other ones need the nav to change in our custom theme (and have a dark-mode logo for myst!).

Nice, I like it, it would be pretty easy to add I think!

We would add a logo_dark here
Access it here
And then do the actual logo switch here

There is an existing react code example of doing this here. Happy to help with the various PRs if you are up for it!

For what it's worth, here's the configuration structure and behavior around logos and site titles in the pydata theme
https://pydata-sphinx-theme.readthedocs.io/en/stable/user_guide/branding.html#different-logos-for-light-and-dark-mode

I just opened myst-theme PR #130.
I still haven't had the chance to test it but I believe it should work (or be very close to working).

So cool! Thank you for the PR @eurunuela, it looks great and I will test it out soon -- and thanks @choldgraf for the links over to the pydata theme!

Merged in your logo_dark work, it should be deployed in the next few days! Thanks again @eurunuela for your help with this. 🚀
I am excited that actually it was (I think) pretty easy to customize the themes. I think there needs to be easier ways to share various parts of the configuration between themes (right now I just copied the bit of YAML you wrote to the article theme). @fwkoch was giving some thoughts to this as well in sharing frontmatter (e.g. math macros) for projects, so hopefully we can align there as well. Before we get too much further we should probably circle back to more mature theme customizations like what @choldgraf shared to make sure we are moving towards supporting those types of options.

I'm gonna move this one over to mystmd.org since the remaining actions are needed in that theme-specific repo


1710 user experience

1710 O365 update user experience is not reflected on the table.
Expecting same as 1706

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

ID: d1da48af-4783-bd17-67f3-f265df93503f
Version Independent ID: 17432b22-04cb-f47f-1634-e5b7fc99c37d
Content: Manage Office 365 ProPlus updates - Configuration Manager
Content Source: sccm/sum/deploy-use/manage-office-365-proplus-updates.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @MSBeatriz for the feedback. Yes, I think that's right. Good point to explicitly include that version along with 1706 (and remove the now unsupported versions: 1706 and earlier).


Build CI

This tries to build the docker image inside PR for better debugging.

base image is jammy (22.04)
python version is 3.11

It looks like baltrad hlhdf does not compile with python 3.11. I'm trying to investigate, but this seems to be a numpy compat issue, cc @andershenja.

@mgrover1 @DanielMichelson @andershenja
I'm not able to fix the issues with hlhdf. I've tried a bit in this fork https://github.com/openradar/hlhdf but I'm no expert at all in C/numpy expecially when it comes to heave use of macro's. So if there is someone capable of fixing these issues, just let us know.
I'll skip the baltrad install for now to see, if LROSE is working.

@mgrover1 Going to merge this. Checking build and push of the image to the ghcr.io.


python3Packages.poetry*: use native namespaces

Motivation for this change
Follow up to: https://github.com/python-poetry/poetry/issues/2800
Upstream doesn't want to kill python2 support, but I do.
This does allow for python3 (and by extension, nixpkgs) to use these packages when located at different store paths.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

didn't realize this was 1677 rebuilds, rebasing on staging

$ nix-build -E 'with import ./. {}; python3.withPackages (ps: with ps; [ poetry poetry-core ])'
this derivation will be built:
  /nix/store/1dqfri5phj687wqh14wq7n48lbg816wi-python3-3.9.6-env.drv
building '/nix/store/1dqfri5phj687wqh14wq7n48lbg816wi-python3-3.9.6-env.drv'...
created 383 symlinks in user environment
/nix/store/qpikiv6cfj8618rn4x6lk3zsz68pch0v-python3-3.9.6-env


fixes #23097 zsh completion on docker rm -f

fixes https://github.com/docker/docker/issues/23097
- What I did
List all containers on docker rm -f
- How I did it
Simply list all containers when docker rm followed by -f or --force.
- How to verify it
$docker run -d --name test nginx
$docker rm <TAB> container test will not appear.
$docker rm -f <TAB> container test appears.
- Description for the changelog
List all containers on docker rm -f
- A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Tianyi Wang<EMAIL_ADDRESS>

ping @sdurrheimer can you review / assist? Thanks!

I will test this as soon as possible.

LGTM :+1:

LGTM 🐮


GM! Where is v2 happening and how can General magic help finish it off?

GM Wesley! We would love to make sure tokenlog v2 is ready by september to be used by Grassroots Economics for voting on their Commons :-D
@rbsal97 would be our project manager to take it on, tagging him here so I don't lose track!

Hi Wesley! Would like to have some more information and details for us to Fastrack and make preparations for this project.
My TG and Discord lines are open for faster discussions.

Hi @GriffGreen @rbsal97
Thanks for reaching out. As you might know, I haven't been able to develop / maintain this lately.
Been pretty much stale for years now. The V2 is probably at 80% or something right now at the next branch
https://github.com/wslyvh/tokenlog/tree/next
Which should be a more stable/robust and performing version (build on Next.js)
Let me know how you want to approach this? Do you want to contribute to this repo or should we look at migrating this into an org/repo that the commons team has access to?

Had some time to start things up again @rbsal97
V2 development has been going on at the next branch. As said, I think it's roughly 80% done.
https://github.com/wslyvh/tokenlog/tree/next
You can try and test it out at (DAI voting on this repo)
https://tokenlog.vercel.app/wslyvh/tokenlog
What's left here is saving the votes itself.

on the front-end, votes are passed through the components to the context/vote-context to a function called vote.
There's a TODO comment there which should POST /votes the vote to the back-end.

On the back-end, this doesn't exists yet.
The votes service exists at /api/votes but doesn't exists or handle it yet.
It should do some basic checks (vote is valid, no race-conditioning, etc.) and pass the vote on to the repository/voting to save it to the DB.

It seems like that's it, although it probably requires a bit of testing and fine-tuning
(it's been a while, sorry)
V2 requires 2 env variables
DB_CONNECTIONSTRING - which should be a valid MongoDb connection string (I use Mongo Cloud, Atlas)
GITHUB_ACCESS_TOKEN - a valid personal access token to access the Github API
Happy to help get a dev up to speed.
Also open to migrating the repo into an org that the team has better access to

Hi @wslyvh
Our dev is currently looking at it. He mentioned he can implement the last changes. We will be sending you the timeline once we finalize it with him. We can also create a bridged channel on discord for better communication. We will be also migrating this repo to GM for better access.
@GriffGreen

Hi @wslyvh,
Our dev has already mapped out the missing components but he asked if you have time for a quick call just to ensure we are on the same page.


Version mismatch between GUI and epinio info

For example with the epinio-0.9.0 helm chart epinio info reports server version 0.9.0 correctly, but the GUI claims to be 0.11.0.
The same thing happens with 1.0.0-rc2, where the GUI claims to be 1.0.0-rc1.
The GUI should report the version from the API and not have its own version baked in (at least I assume that is the issue here).

At some point, we decided to show the  chart version in the UI because we thought that this should the be version the user should know (because it's the collection of all the things that make up Epinio). Then we changed our minds and reverted that change because the rest of the components are kind of optional and can be replaced by others or other versions.
On 1.0.0-rc2 it's correct, because the server version is still rc1. We didn't have to release another version of the binary because the fixes were only on the chart.

This should be fixed in v1.0.0:

https://github.com/epinio/epinio/releases/tag/v1.0.0
https://github.com/epinio/helm-charts/releases/tag/epinio-1.0.0

I'm closing this one since it's fixed. @richard-cox will create another story to change how we decide which version to show in the UI. Instead of hardcoding that we will get if from the /info endpoint (like the epinio info command does).


Scrollbar slightly off

The rightside scrollbar is slightly off position (see first image), I'm using latest chrome and latest ttyd from git.
An easy fix seems to be to simply unset the width off xterm-viewport, or perhaps setting it to 100%, the calculations that set the width seems to be off.

This seems to be fixed on latest master.


fix titles

I've had inexplicable issues with the R-Studio Monocle reviewing/every time I try to change the title it keeps making 4000 other changes, so at least I've fixed these two

(P.S. if you see 4000 unrelated changes in a PR, I would guess it means you accidentally started from the wrong branch and not latest main?)


Add an option for FancyZone to remember window's size before snapping

Please add it so then when dragging the window out of the zone, it restores back to the size before you snapped it, just like in Windows Snap.

Hi @uEFImaster
thank you for your feedback.
Closing this as duplicate of #166
Feel free to add your comments there.
Thanks.


How to change the definition of remote video

I am using the video-sample demo of the api-example-unity-agorachat project，The video call between the two parties can be realized, but I find the image quality of the remote video is very poor, how to modify it

Do you think the resolution is poor or frame rate is low？

Do you think the resolution is poor or frame rate is low？


updated README installation command

The command says pip install prometheus_client (underscore) but the steps above and PyPi says prometheus-client (dash)
Signed-off-by: Alexa Griffith<EMAIL_ADDRESS>

Closing and reopen as it looks like you did sign the DCO and I am hoping that it passes this time.


Redirection to homepage after login

Hello, when I log through EVE Authorization it redirects me back to the homepage. I couldn't even get to the map by www.[domain]/map. It also redirects me back to the homepage. Could you please advice me what am I doing wrong. Thanks.

I've had the same issue intermittently and had to click login one or two more times before I was finally able to fully log in.
One other thing I noticed (a user recently reported it): are you by any chance using IPv6 to connect to your server? I've had issues with proxy servers/IPv6 addresses since the database field for IP addresses was too short, as described in #407
Do your PHP error or pathfinder CREST logs show anything while you're trying to log in?

#407 is already fixed. What bothers me is that I don't get any errors. It just redirects with no message at all.

I have the same issue.

It's the login time variable set to 240 by default. If it's been 240
minutes since the initial login session, you'll select a character and it
will fail the login time rest but restart the timer--clicking it a second
then then works.
On Wed, Dec 21, 2016 at 1:47 AM VivianMeally<EMAIL_ADDRESS>wrote:

I have the same issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/exodus4d/pathfinder/issues/410#issuecomment-268261209,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ8ssO-5HoHLzN_YeCJc5_iJN28Y-vp2ks5rJ-qEgaJpZM4LKmJ4
.


New package: Flydigi.FlydigiPCSpace version <IP_ADDRESS>_2

Microsoft Reviewers: Open in CodeFlow

Verify:

The application omits the _2 from the version number. This is probably okay.