#86 and #87 - Eslint and coverage updates

Fixes #86 - tightens eslint rules, bringing about greater consistency in coding style
Fixes #87 - initial code coverage integration with Istanbul and NYC. I've no experience with Tape as a testing framework, so this might be rough, but it gets us at least part of the way

Additionally:

Reduces complexity of _processRoute and _buildRoutes methods. DRYs up some logic in _buildRoutes, removes some dead code, reduces control flow nesting
Cleans up propTypes declaration, removing two that were unused, and adding a couple that weren't there previously, but are used in the code

Nice!! Clean

Cheers!
On Wed, Apr 12, 2017 at 3:03 AM, Sven Anders Robbestad <
<EMAIL_ADDRESS>wrote:

Merged #88 https://github.com/svenanders/react-breadcrumbs/pull/88.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/svenanders/react-breadcrumbs/pull/88#event-1039606990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkeu8tA5SEBy_2u4JxK8N9dgJunhXDcks5rvHdMgaJpZM4MTflh
.


Oscean is really big!

The osceans are really big, and i cant figure out if there's a way to scale them down?:)
I'm trying to match the scale to the following assets:

Also, non of my changes seam to apply when i run the game, only in the editor?

Which scene are you using? water_shader_examples? What settings are you changing? The way I have water_shader_examples.tscn set up, the WaterMaterialDesigner automatically sets shader parameters based on the GerstnerWave resources in the editor.
By the way, the size of ocean waves will not scale with DeepOcean.scale, you have to edit the waves.
Lower the steepness in this wave from 10 to something smaller. Play with the other settings as well.

Then go to DeepOcean and press "Editor Rebuild"

Oh! I might have just misundertstood how one's ment to interact with the add-on^^' I'll give ur instructions a go:)

So now it works! I just didn't use the plug-in properly:P Thank u for the help!^^

No problem! Of course this means I should document the plugin better. I'm thinking of making a wiki with explicit howto's like this.

That sounds like a good idea:)

I'm also having this same question, but I'm using a Plane mesh with the 'outset_ocean material.tres'. How can I downscale in this case? I don't have this helper node, as I'm just using the shader in a mesh.


Unable to run app.py (ModuleNotFoundError)

I am trying to run through local development and I haven't been able to get app.py to run backend URL output. The error that shows up is :

from flask_cors import CORS, cross_origin
ModuleNotFoundError: No module named 'flask_cors'

I did run the command: 'pip install -r requirements.txt' in the virtual environment that I created, but the error persists.
When running 'pip freeze' command, I get the following

Further, if I try to install flask_cors module, using 'pip install -U flask-cors', the output shows requirement already satisfied.

@tealnshack have you tried running pip install -U flask-cors?

Yeah, when I do it, the package is visible but when I run the command to start the web server the same error pops up despite the package being installed in the virtual environment


Can I ignore some field

Greeting. I find the package is useful and hope you don't mind that I ask a silly question.
In the example, it show the default log string like this.
{"@version": 1,
 "account": "pyr",
 "lineno": 1,
 "levelno": 30,
 "filename": "test.py",
 "thread":<PHONE_NUMBER>44928,
 "@timestamp": "2015-03-30T09:46:23.000Z",
 "threadName": "MainThread",
 "relativeCreated": 51079.52117919922,
 "process": 10787,
 "source_host": "phoenix.spootnik.org",
 "processName": "MainProcess",
 "pathname": "test.py",
 "args": [],
 "module": "test",
 "msecs":<PHONE_NUMBER>525146,
 "created":<PHONE_NUMBER>.9999006,
 "name": "root",
 "stack_info": null,
 "funcName": "<module>",
 "levelname": "WARNING",
 "message": "foo"}

However, I think the outpout information is too much for me. I learn that the necessary field the logstash need is  @version and @timestamp. So can I set fmt to ignore some field then the result can be like this.
{"@version": 1,
 "@timestamp": "2015-03-30T09:46:23.000Z",
 "message": "foo"}

@memwey How did you resolve this problem can you help me out with any sample example

@memwey @AmanKrSoni is it possible to ignore some fields? Can you tell me how did u do it?


cifar10 example is not scalable with multiple GPUs

I slightly adapted the cifar10 example in this fork, basically removing python-fire and adding the torch.distributed.launch function, so that it can be executed as a standalone script with clearml-task.
I executed the following script with nproc_per_node in [1, 2, 3, 4] on a AWS g4dn.12xlarge instance (x4 T4 GPUs). I got the following results:

batch size=16, nproc_per_node=1 => Runtime: 29:53
batch size=16, nproc_per_node=1 => Runtime: 05:34
Here I disabled DataParallel as mentionned in https://github.com/pytorch/ignite/issues/2447
batch size=32, nproc_per_node=2 => Runtime: 17:11
batch size=48, nproc_per_node=3 => Runtime: 11:33
batch size=64, nproc_per_node=4 => Runtime: 08:47

I am increasing the batch size by 16 each time I add a GPU, so that each GPU has the same number of samples. I didn't change the default number of processes (8) for all of them, because I didn't oberserve that the GPUs were under-used (below 95%)

GPU utilization as reported by clearml

I was expecting to observe a quasi-linear time improvement, but it isn't the case. Am I missing something?
PS: Here are the requirements I used to execute the script
torch==1.7.1+cu110
torchvision==0.8.2
pytorch-ignite==0.4.8
clearml==.1.1.6
tensorboardX==2.4.1

@H4dr1en Thanks for that report. It looks weird, I have done similar experiments when I worked in a research center with GPU cluster and it was fine regarding scalability.
Did you try disabling clearml ? Transferring the results to the server can create disruptions and interruptions during learning.

Thank for your answers!
From what you reported, scaling the training speed linearly with the number of GPUs should be achievable, so there could be something wrong that could be fixed.
As a context, I do observe similar bad scalability for my own use case within g4dn.12xlarge instances, so I hope that if we can find the bottleneck with the cifar10 example, it would also unlock my other project.

@H4dr1en can please you try original cifar10 example on your infrastructure using 1, 2, 4 GPUs and report back runtime here ?
# for older pytorch
python -u -m torch.distributed.launch --nproc_per_node=1 --use_env main.py run --backend="nccl"
# for >=1.9
torchrun --nproc_per_node=1 main.py run --backend="nccl"

# for older pytorch
python -u -m torch.distributed.launch --nproc_per_node=2 --use_env main.py run --backend="nccl"
# for >=1.9
torchrun --nproc_per_node=2 main.py run --backend="nccl"

# for older pytorch
python -u -m torch.distributed.launch --nproc_per_node=4 --use_env main.py run --backend="nccl"
# for >=1.9
torchrun --nproc_per_node=4 main.py run --backend="nccl"

I'll put here my times on 1 and 2 GPUs GTX1080Ti to compare.

Thanks @vfdev-5 ! Here are my results:

Config
Total time
Training epoch time, validation train/test times

PyTorch 1.7.1+cu110, RTX 3070, 1 GPU
00:02:30
00:00:05, 00:00:01.8, 00:00:00.9

PyTorch 1.7.1+cu110, RTX 3070, 2 GPU
00:01:29
00:00:03, 00:00:01.3, 00:00:00.5

PyTorch 1.9.1+cu111, RTX 3070, 1 GPU
00:02:19
00:00:05, 00:00:01.8, 00:00:01

PyTorch 1.9.1+cu111, RTX 3070, 2 GPU
00:01:26
00:00:03, 00:00:01.3, 00:00:01

PyTorch 1.7.1+cu110, g4dn.12xlarge, 1 GPU   (7Gb of GPU RAM used!)
00:14:55
00:00:35, 00:00:02.4, 00:00:03

PyTorch 1.7.1+cu110, g4dn.12xlarge, 2 GPU
00:02:28
00:00:05, 00:00:01.7, 00:00:00.7

PyTorch 1.7.1+cu110, g4dn.12xlarge, 4 GPU
00:01:53
00:00:04, 00:00:01.7, 00:00:00.5

Thanks for the results @H4dr1en !
Definitely, there is something unclear with 1 GPU case for g4dn.12xlarge.

Btw, is it fair to compare the speed this way? ie. in multi-gpu context, each GPU get a smaller batch_size

Well, I'd say we are interested how quickly the task was done. By the task we have to measure the number of processed images. If in multi-gpu context we load each GPU as in the a single GPU case, we have to reduce the number of iteration to run, otherwise the wont accomplish the same task, I think.

EDIT: in the logs for PyTorch 1.7.1+cu110, g4dn.12xlarge, 1 GPU (7Gb of GPU RAM used) case, do you see something like "Apply torch DataParallel on model" ?

But the behaviour above for 1 GPU on g4dn.12xlarge is probably a separate issue. Sorry I was not very explicit on the issue description, my main concern is the following:
If we define the factor of improvement as f(n_gpu) = training_time(n_gpu) / training_time(2 * n_gpu)
I would expect to have a factor of improvement approaching 2, and it seems to never be achieved. What could be the reason for that?

I would expect to have a factor of improvement approaching 2, and it seems to never be achieved. What could be the reason for that?

I think in case of cifar10 a larger model can give something as a linear scaling (up to a certain limit).
See also results for Pascal VOC: https://github.com/pytorch-ignite/examples/issues/75#issuecomment-1028098725 where factor ~ N GPUs for N = 1, 2 and 4


Drag and Drop not working on Linux Mint

Describe the bug
Drag and Drop works on Windows and Fedora Gnome, but doesn't work on Linux Mint
To reproduce

Open LocalSend
Open Neno (Linux Mint's file manager)
Drag file from Nemo over the LocalSend window
Observe that LocalSend recognizes I'm holding files over it, as it displays the message "Place items to share."
Drop the items by releasing the mouse button
Observe that no items have been queued for sharing

Expected behavior
I expected drag-and-drop to work on Linux Mint, like it does for other OSes
Screenshots
No response
Desktop (please complete the following information)

OS: Linux Mint
Version: 21.2, 21.1

Smartphone (please complete the following information)
No response
Additional context
No response

I am on Linux Mint 21.3 x86_64 and I can't reproduce this issue.

Same problem on Linux Mint 21.3 Virginia

I believe that LocalSend doesn't have sufficient permissions to read the dropped file. Can you try to move your desired file into the "Downloads" folder and then drop it from there?

I believe that LocalSend doesn't have sufficient permissions to read the dropped file. Can you try to move your desired file into the "Downloads" folder and then drop it from there?

@Tienisto Should we add handling for such cases ? Like a Snackbar alert saying "LocalSend can't read this file..."

Yes, I guess. But I am not sure if my assumption is correct @Shihabus-Sakib-Rad

I believe that LocalSend doesn't have sufficient permissions to read the dropped file. Can you try to move your desired file into the "Downloads" folder and then drop it from there?

Thanks for this observation @Tienisto !
I tried this, and observed the following:

Drag-and-drop works on files from Downloads
Drag-and-drop doesn't work on files from Documents, Pictures, Music, Videos, or the Home folder

Any idea how if LocalSend can handle this at install, or if I'd have to tweak something in Linux Mint, or if moving files to Downloads is the only workaround?

Did you install LocalSend via flatpak? Flatpak only allow LocalSend to read and write to Downloads folder by default. You may need to allow full disk access.

Did you install LocalSend via flatpak? Flatpak only allow LocalSend to read and write to Downloads folder by default. You may need to allow full disk access.

Yup, I installed it via Flatpak. It seemed like the best choice to have automatic updates :)
I just looked it up, and it seems like Flatseal is a recommended permissions manager for Flatpak apps. Is that my best option?
https://github.com/tchx84/Flatseal

See #256


Create a timestamp locked "vault" for funds in Firefly

Description
Feature request from user "Stefanoste"
When it comes to crypto the biggest concern is security, we all know sometimes shit can happen  and even with nano  ledger time to time you can feel unsafe
Firefly is fantastic and in terms of security I am sure will be like no one , but why don't enforce it even more and add a kind of "vault" inside ??
The "vault" is a  timestamp lock where you decide to lock some/all funds and be available "X-time " after you requested to  unlock
Let's say I have 10gi , because I don't really need it to be all available in the wallet ,for security , I decide to lock 5gi with the option to make them available again  (two/four/eight or what ever ) hours after the unlock  request
When you request unlock you get notified
If someone for whatever reason accesses my wallet can only steal the amount available and not the rest unless of course will wait whatever time need it to unlock "vault"
Motivation
Explain why this feature is needed.
Requirements
Write a list of what you want this feature to do.

Open questions (optional)
Use this section to ask any questions that are related to the feature.
Are you planning to do it yourself in a pull request?
Yes/No.

I believe that this could possibly be integrated into Firefly, but then the lock only applies to the Firefly app.  The problem, however, is that anyone with access to the seed can still move the tokens.  There is no lock on the ledger.  Sending cannot be prevented if someone is working with the stolen seed on another computer.  But it may be possible with smart contracts.

if use smart contract

I believe that this could possibly be integrated into Firefly, but then the lock only applies to the Firefly app. The problem, however, is that anyone with access to the seed can still move the tokens. There is no lock on the ledger. Sending cannot be prevented if someone is working with the stolen seed on another computer. But it may be possible with smart contracts.

smart-contract should solve this limitation, so even if you have the seed you will not be able to move funds unless you execute the request first and wait
Maybe considering to allow "vault" a maximum amount up to 80/90% of the available to avoid running out of money in case of emergency/needs and maximum lock period up to 6/8 hours as a security feature


Re-enable registration feature and add on-boarding instructions

Turn the registration feature back on and include account-related pages as necessary.

@brendangadd Since users are required to use the Azure SSO with their Cloud account and they need to be on-boarded before using the AAW, is there a set of instructions or contact details we could add to the public-facing "Register" page to prompt new users?

@bbronzan Since the platform is not yet available to the public, I'm not sure we can give meaningful registration information on public internet just yet.

Ok no problem, so the current on-boarding of users will remain the same then? If so, the ability to register wouldn't need to be enabled yet so we can turn it off again until a later time. I guess this ticket could be placed back into the backlog for now. Let me know.

Closing since we handed off this component.


URI rewriting fails on Apache < 2.2

(via marcus.bointon wiki comment)

What steps will reproduce the problem?
1. Request /min/builder/ on Apache 2.0 with mod_rewrite enabled

Due to the use of the new 2.2 IfModule syntax, rewriting fails. Minify
should use the older, still-supported syntax for the open tag:

<IfModule mod_rewrite.c>

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 17 Jun 2009 at 6:31

It already does:
http://code.google.com/p/minify/source/browse/tags/release_2.1.2/
min/.htaccess
Does it still fail for you on Apache 2.0?

Original comment by<EMAIL_ADDRESS>on 30 Jun 2009 at 4:52

Changed state: NeedInfo

@ramonck: Feel free to create a new issue with a more thorough description of
what
you're trying to do, or better, send a message to the google group.

Original comment by<EMAIL_ADDRESS>on 29 Nov 2009 at 5:26

I have a similar issue on ProxyPass, minify doesn't work with virtual addresses
even
if local (ProxyPass to another server) it seems to work only on static + local
links.
it would be nice if minify used PHP5 features for fetching the files
dynamically.

Original comment by<EMAIL_ADDRESS>on 27 Nov 2009 at 9:21

Original comment by<EMAIL_ADDRESS>on 8 May 2010 at 7:43

Changed state: Invalid


Pickles_types: extract tests into own directory (berkeley version)

berkeley version of #14055

!ci-build-me

!approved-for-mainnet


win-8 is in Quarantined state due to "C:\temp directory is full".

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
win-8 is in Quarantined state due to "C:\temp directory is full".

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

To clear the error by removing old files under C:\Users\swarming\AppData\Local\Temp.


chore(Data/List): Use Std lemmas

Make use of Nat-specific lemmas from Std rather than the general ones provided by mathlib. Also reverse the dependency between Multiset.Nodup/Multiset.dedup and Multiset.sum since only the latter needs algebra. Also rename Algebra.BigOperators.Multiset.Abs to Algebra.BigOperators.Multiset.Order and move some lemmas from Algebra.BigOperators.Multiset.Basic to it.
The ultimate goal here is to carve out Data, Algebra and Order sublibraries.

bors d+

bors merge


Is there a way to use this universally in any situation outside of GW2? For example a .exe file?

I absolutely love the ability to use a radial menu so that i do not have to look away from my screen to find awkward key locations.
Is there a way to use this menu universally and system wide in any application/game?
Or could you maybe suggest another program that would achieve this feature?
So far the only ones I have found are either awkward to use mid game (radial menu v4 - AHK) or do not centre in the middle of the screen when activated cause half of the menu to be inaccessible when turning the screen using action camera.
Thanks!

That's an interesting idea! Unfortunately, you'd need to do fairly extensive modifications to this project to make it work standalone as an overlay. Anyone who wants is more than welcome to try and fork this as baseline if it helps, but it's not something I have the time to do unfortunately.


fix xwayland tearing

Describe your PR, what does it fix/add?
fixes #6287. tested with vrrtest
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
needs to be updated again in #6268 since there will be no wlr_surface
Is it ready for merging, or does it need work?
ready

thanks :) generally looks alright but I will wait for others to report

It looks like this patch fixed direct scanout with xwayland clients for me


Add option to ignore hidden markers

I added an option to ignore hidden markers when creating the cluster in the function "createClusters_".
The default value is set to false, which reflects the current state.

I think I've had a similar problem: https://github.com/googlemaps/js-marker-clusterer/pull/44
My approach is a bit different though. I'm adding all marker and only return those that are visible.
That way I can dynamically change the visibility of a marker. Is that something you've tested, maybe I've missed something in your change.

I just had a look at the code I wrote then, I am manually calling repaint() on the marker clusterer object after I changed the visibility of the markers. I do not think that is a big problem, apart from that it works like a charm.
Does your solution work without having to call repaint() ?
Anyways..it does not seem like this repository is actively maintained..

I see! I think my change did the same, I just needed more code ;-)
I'm thinking about forking this repo and merge some of the pull requests.

@maechler going to merge this in our fork over here https://github.com/gmaps-marker-clusterer/gmaps-marker-clusterer/pull/7

Great! thanks. It's nice to see that the code is now in a repository where it can be maintained!

works great!
ship it.


ClickHouse-Grafana seems to be incompatible with Explore UI in Grafana 6.0

Looks like there is some incompatibility.  The queries are not generated  -  see Generated SQL showing simply "true"

@PeterZaitsev I try to reproduce this behavior on latest master docker-compose.yaml with a changed image to grafana:6.0.2 and failed
looks like the current master branch works fine with grafana 6.0 explore mode without apply
https://github.com/Vertamedia/clickhouse-grafana/pull/129

I also tested lates master with grafana 6.7 and grafana 7.0
and explore also works fine

Thank you. Indeed this was fixed in one of the releases since I reported the issue


Barchart example: alignment not working properly

@silvia-odwyer
In an example, alignment is broken.
Also please add bar chart to ”gitignore”.

@silvia-odwyer please test #7

@silvia-odwyer PR #7 is merged to master, so I will close this


[fix] Missing cache types in BlockFileCacheTest

Proposed changes
Issue Number: close #xxx
Fix BE UT (macOS). See https://github.com/apache/doris/actions/runs/8864918612/job/24340617696.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Add coq-lsp to Coq Platform

Dear Coq Platform maintainers, this is to inform you that I'd like to add coq-lsp to the 8.17 preview set of packages.
Relevant issues / PRs:

https://github.com/coq/opam-coq-archive/pull/2432
https://github.com/coq/coq/pull/16964

The depending PRs are ready / merged, thus I'm requesting inclusion, IIUC the guide states 4 TODO points:

Packages are typically included on user request via a github issue.

This issue should work.

Requests should contain a justification.

coq-lsp is of help to IDE users (VS Code client exists, server is usable within the standard) , moreover, coq-lsp is posed to replace SerAPI and sertop, so making testing easy is IMHO important.

The author(s) or current maintainer(s) of the package shall agree to the inclusion of their package in the Coq Platform. This means that they agree to put reasonable effort into releasing a version of the package compatible with each new Coq release shortly after every Coq release and to maintain some relative stability between each release. The agreement of the authors is given via a comment in the respective github issue.

I agree and commit to all of this.

All the dependencies of a platform package are also officially part of the platform.

That's the case now (serlib being the only annoying dep, and is already there).

Additionally, if you tell me which file to touch (sorry I couldn't manage to figure this out today) I'll be happy to do the pull request myself.

Thanks @Zimmi48 for both the suggestion to do this and the help with setting the right meta-data.
We have discussed a bit on the coq-lsp side and we think 0.1.4 (or 0.2.0) should offer the right compatibility story for the 8.17 release, so that's the version we will target for inclusion.
The main compatibility story is that client and server need to agree on the (only important) extension our LSP has, the goals request.
We have now a plan that should handle different versions reasonably.

Hi @MSoegtropIMC , is there any hope to include coq-lsp in the 2023.03 platform?


Update unit tests to cover all examples from README.md

There were some examples in README.md not covered by unit tests. I have added them to the tests now. All tests are passing, fortunately :-)

Thank you for this PR. Merged! 👍


Fix typo in git ignore

Also, added newline at the end of this file, according to the POSIX standard.

Codecov Report

Merging #757 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #757      +/-   ##
==========================================
- Coverage   71.20%   71.19%   -0.02%
==========================================
  Files         343      343
  Lines       28321    28321
==========================================
- Hits        20166    20163       -3
- Misses       6848     6851       +3
  Partials     1307     1307

Impacted Files
Coverage Δ

os/gspath/gspath_cache.go
86.95% <0.00%> (-6.53%)
:arrow_down:

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 2c0cfa2...b97e397. Read the comment docs.


feat(ci): Add check for go mod tidy

Supersedes #182
Adds a check to make sure that go mod tidy produces no diff for the go.mod or go.sum files.
Also updates some of our actions versions while we are here.

Validation can be seen in the first commit for adding the new check. go.mod wasn't tidy and so the added check fails. We fix it in the second commit.


Is it compatible with Expo 50?

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
[X] I'm running the latest version

Question
Hello,
I am using expo 50.
"dependencies": {
    "expo": "~50.0.14",
...

When I tried to run npx expo install @config-plugins/react-native-ble-plx, I got the following error:
› Installing 1 other package using npm
> npm install --save @config-plugins/react-native-ble-plx
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/expo
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer expo@"^49" from<EMAIL_ADDRESS>
npm ERR! node_modules/@config-plugins/react-native-ble-plx
npm ERR!   @config-plugins/react-native-ble-plx@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
...

I can see - it is compatible with Expo 49 in the readme, but I can't install the package with Expo 50. Isn't it compatible with 50?
Thank you,

Hi @Santa0727
We checked compatibility with expo 50 and found no problems. In issue #1176 (https://github.com/dotintent/react-native-ble-plx/issues/1176) is an example using expo 50.

This bugs me 😅

You shouldn't use additional @config-plugins.
@dominik-czupryna-withintent Do you think it can somehow added anyways?

I was able to successfully make a build 10 days ago with "expo": "~50.0.4",
When I want to build my app ("expo": "~50.0.17",) with eas, I encounter this error https://github.com/expo/expo-cli/issues/4391
Error: [ios.dangerous]: withIosDangerousBaseMod: Unrecognised filter type - 127

npx expo prebuild runs fine on my local machine.
Here are my investigations with yarn why @expo/config-plugins
yarn why @expo/config-plugins
yarn why v1.22.21
[1/4] 🤔  Why do we have the module<EMAIL_ADDRESS>[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "<EMAIL_ADDRESS>info Has been hoisted to "@expo/config-plugins"
info Reasons this module exists
   - Hoisted from "expo#@expo#config-plugins"
   - Hoisted from "react-native-ble-plx#@expo#config-plugins"        <----- for some reason it's there
   - Hoisted from "expo#@expo#cli#@expo#config-plugins"
   - Hoisted from "expo#@expo#config#@expo#config-plugins"
   - Hoisted from "expo-splash-screen#@expo#prebuild-config#@expo#config-plugins"
info Disk size without dependencies: "1.82MB"
info Disk size with unique dependencies: "3.91MB"
info Disk size with transitive dependencies: "8.42MB"
info Number of shared dependencies: 60
=> Found "expo-updates#<EMAIL_ADDRESS>info This module exists because "expo-updates" depends on it.
info Disk size without dependencies: "1.73MB"
info Disk size with unique dependencies: "3.82MB"
info Disk size with transitive dependencies: "8.32MB"
info Number of shared dependencies: 60
✨  Done in 0.24s.

On my app.config.ts I added this
plugins: [
    "expo-router",
    [
      "react-native-ble-plx",
      {
        isBackgroundEnabled: true,
        modes: ["peripheral", "central"],
        bluetoothAlwaysPermission:
          "Allow $(PRODUCT_NAME) to detect your bluetooth device"
      }
    ],

@Santa0727
Can you please let us know if eas build --platform=ios is working on your side?

Hi @flexbox,
Thank you for your response.
The build command works on my side, and it builds ipa file.
I've used expo managed workflow on my local. Is it impossible to use without ejecting expo?

@flexbox
I mean you shouldn't install https://www.npmjs.com/package/@config-plugins/react-native-ble-plx because react-native-ble-plx is shipped with an Expo config plugin on its own.
@Santa0727
You don't need to eject expo, you just need to prebuild the native code because without using native code this package won't work.

Hi, I am not sure now, where should we add these configurations ?
{
isBackgroundEnabled: true,
modes: ["peripheral", "central"],
bluetoothAlwaysPermission:
"Allow $(PRODUCT_NAME) to detect your bluetooth device"
}

@kennyyen
in your app.json or app.config.js https://docs.expo.dev/config-plugins/introduction/
{
  "expo": {
    "plugins":
      [
        "react-native-ble-plx", // https://github.com/dotintent/react-native-ble-plx?tab=readme-ov-file#api
        {
          isBackgroundEnabled: true,
          modes: ["peripheral", "central"],
          bluetoothAlwaysPermission: "Allow $(PRODUCT_NAME) to detect your controller with bluetooth"
        }
      ],
  }
}

Thank you for the response, I did tried to put them in my app.json, and when I do
npx expo install react-native-ble-plx
I get this
Skipping config plugin check: Plugin is an unexpected type: object

Thank you for the clarification ! It works just fine as before !

@kennyyen great news!
If your problem is solved can you please close the issue?
It sparks joy for maintainers ✨


Search Option in Collection

Can we have search option in Collections

Hello, @Harsh070707 I want to work on this problem, so can you describe the issue in detail?


valid-package-file-require false positive when filename conflicts with package name

If I have
require( 'ext.MyModule' );

and ext.MyModule.js exists, then the rule marks this as an error, even though this is a perfectly valid name for a package that includes that file.
Rather than doing a complex file check, it might just be better to look for an allowed extension ("js","json", others?)
CC @jakobw @Ladsgroup

Sorry for the late response. I quite like the solution in #21. Only looking for an extension wouldn't have been sufficient since erroring when omitting the extension in a path like ./foo was exactly the point of this rule. Checking for either the extension or the directory prefix to exist makes sense though!


Chown files to a custom user after building (fix file ownership)

Changes
Fixes #219, without causing the issues caused by #141

Adds a chownFilesTo input
chowns the files to whatever the input string is

Use it like this:
- uses: Bradshaw/unity-builder@main
  env:
      UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
      UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
      UNITY_SERIAL: ${{ secrets.UNITY_SERIAL }}
      UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
  with:
      unityVersion: ${{ matrix.unityVersion }}
      targetPlatform: ${{ matrix.targetPlatform }}
      chownFilesTo: "1000:1000"

And it does this after building:
if [[ -n "$CHOWN_FILES_TO" ]]; then
  if [[ -n "$BUILD_PATH_FULL" ]]; then
    chown -R $CHOWN_FILES_TO $BUILD_PATH_FULL
  fi
  if [[ -n "$UNITY_PROJECT_PATH" ]]; then
    chown -R $CHOWN_FILES_TO $UNITY_PROJECT_PATH
  fi
  if [[ -n "$CUSTOM_BUILD_PATH" ]]; then
    chown -R $CHOWN_FILES_TO $CUSTOM_BUILD_PATH
  fi
fi

That's it... That's the fix 😅
I still think the internal Docker user should be something other than root, but that requires a heavier refactor and breaks a whole bunch of backwards-compatibility.
This is entirely optional and does absolutely nothing if the chownFilesTo input is unset or left blank
Checklist

[x] Read the contribution guide and accept the code of conduct
[x] Readme not needed
[x] Tests not needed
[ ] Documentation needs updating, probably

Just to confirm. This is an alternative solution to making the images run as a user (in a sense that one does not need the other), correct?

Codecov Report

Merging #250 (e80f4d5) into main (a1f68ab) will increase coverage by 0.11%.
The diff coverage is 100.00%.

:exclamation: Current head e80f4d5 differs from pull request most recent head d36a0be. Consider uploading reports for the commit d36a0be to get more accurate results

@@            Coverage Diff             @@
##             main     #250      +/-   ##
==========================================
+ Coverage   60.52%   60.64%   +0.11%
==========================================
  Files          20       20
  Lines         684      686       +2
  Branches      134      135       +1
==========================================
+ Hits          414      416       +2
  Misses        269      269
  Partials        1        1

Impacted Files
Coverage Δ

src/model/aws.ts
7.46% <ø> (ø)

src/model/build-parameters.ts
100.00% <ø> (ø)

src/model/docker.ts
21.42% <ø> (ø)

src/model/kubernetes.ts
6.45% <ø> (ø)

src/model/input.ts
100.00% <100.00%> (ø)

Just to confirm. This is an alternative solution to making the images run as a user (in a sense that one does not need the other), correct?

Right, this is closer to a workaround than a full-on fix, and does not need any changes to be made to the images
That said, I think it's worthwhile to do anyway. When running an image as a user, it needs to be a user that has been defined in the image (AFAIK), so someone wanting to have files owned by a given user on the host machine would need to build custom images.

Will merge if you can confirm that this works :)

The config

The files

The developer


Client refactor: code reformatting

Description of the changes being introduced by the pull request:

Move file download related modules inside client directory
Remove (un)safe_download functions
Apply black and isort to the newly moved files
Apply the new pylint config from api/pylintrc and fix the various linter issues
Remove the use of six and future and make the rest of the imports vendoring-compatible

Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Force pushed the new commits. The differences are in

35587c4, thanks for catching the error
2f0bbd0
Dropped the "logging-not-lazy" commit and simply ignored the warning with 101ab3d

I chose the lazy way of just ignoring the logging warning now, since there is already an issue capturing the need of a decision: #1334


Session removed when calling signInWithOtp

Bug report
Describe the bug
Session is removed upon calling signInWithOtp.
Expected behavior
User session should remain valid as this is just a call to sign in a user via OTP.
Screenshots
https://user-images.githubusercontent.com/5667828/218892527-7e772880-16fb-411a-b81b-64e63f07319d.mov
System information

OS: MacOS
Browser: Chrome
Version of supabase-js: 2.7.0
Version of Node.js: v16.14.2

Additional context
Check out the video and see how the auth token is removed from storage after a call to signInWithOtp is performed.

Is the token expired when calling the function?

Sorry only now I can replay to this. It is not, even if the session has just been set, it is removed as I call this method.

Ok, can you include your supabase client code where you're setting up the client? Also any relevant code like onAuthStateChange() and sign-in code.
What framework are you using, if any?
Or even better, I know maintainers will typically ask for a basic repo which reproduces the issue.

Hey @hrestrepop, this is expected behaviour. When calling any of the sign-in methods, we need to remove any existing sessions first before signing in the user.  There should be a user session before the sign-in process is completed.
Let me know if this helps or if I'm misunderstanding something here. Thanks!


Write clients do not transition to read when idle

Background info:
Deli has an idle client timer that removes clients from the quorum if they have not submitted anything for 5 minutes.
When deli removes a client due to being idle, it will insert a leave op into the stream.
The problem:
When a write client does not submit ops for over 5 minutes, deli will insert a leave op for them due to that idle timer. However some point after that, the client will try inserting a noop and will get a nack. It then reconnects as write to submit that noop. So once a write client connects, the idle client timer is mostly useless because that idle write client will end up reconnecting as a write client each time.
Possible ideas:

Client runtime should see that a leave op was inserted for their client id and do "something". Maybe it should transition from write to read, or maybe it should be smart enough to reconnect as read if it was nack'd due to a no-op
Maybe this problem magically goes away once we rework how no-ops function

Screenshot showing a client being idle for 5 minutes. It then trys to insert a no-op, gets nack, then reconnect as a write client in order to submit it

Parking on @vladsud for now.
@tanviraumi fyi

I believe this problem should be mostly gone due to changes in noop frequency.
And given we are planning to change noops, I'll wait on this issue a bit.

Please note comment in https://github.com/microsoft/FluidFramework/pull/7230/files/95f5b3e92eba51779d82051f1f4a9dc0275a577e#r694390403 RE runtime should never be exposed to such state. If this case no longer happens, then we should add an error logging statement to prevent it from happening in the future.

That's the same as issue #5557.
Copying my note from that issue that I think matters:
This is definitely happening in prod, where clients do stay idle that long on socket.
That's one of the top disconnect reasons actually.
We can address it by client reconnecting as read whenever it seems its own leave op.
It feels like for most part it's not that important. However there are some cases where it may make a difference.
For example, clients that can't reconnect, i.e. agents, including summarizer.
It would be wrong to keep an agent alive doing some expensive CPU calculations while we know that results of this computation can't be committed to a file. So I think disconnecting / reconnecting sooner is good thing to do.
Note that noop frequency changes likely would make this issue go away (need to trace when it happened and if we see confirmation in telemetry).
But it forces different question - why client should stop sending noops and reconnect as "read" to avoid sending noops for nothing?
This is important question as it impacts other areas. For example today Container.setAutoReconnect() flow relies on connections being dropped at 15 min frequency. This is going to change (due to joinSession workflow changes - client will call it every 15 min to refresh token), and thus client should be in driver sit RE deciding when to drop / downgrade connections.

There are two interpretations / subsets of the problem:

Client does not realize about it getting leave op, and sends noop after that, cause return to "write" mode.
Client continuously sends noops (as result of other clients being active) and thus never transitions to "read" mode.

1 is fixed by PR #5557 that I just merged
2 should be tracked either by https://github.com/microsoft/FluidFramework/issues/5629, or/and by Deli ignoring noops in its calculus and forcing this client to leave.
As such, I'll resolve this isssue


[BC break] Remove old InjectTemplateListener behavior

Removed old pseudomodule template name resolution which ignored subnamespaces and used __NAMESPACE__ variable in convoluted and non-intuitive ways.
Whitelisted classname based template name resolution introduced in ^2.3.0 is now default
Template resolution follows these rules:

strip \Controller\ namespace if present
strip trailing Controller in classname, unless classname is exactly Controller
inflect CamelCase to dash
replace namespace separator with slash

See https://github.com/zendframework/zendframework/pull/5670
This breaks backwards compatibility in some cases, check couple changed tests.
Affected modules can achieve compatibility with v2 and v3 simultaneously by adding whitelist entry to template map and moving templates or by mapping namespace to old location.
Needs documentation. If anyone is willing to write it for me I definitely won't object to that

@Xerkus Could you please add some verbiage into doc/book/migration/to-v3-0.md detailing the impact of this for users? I can then merge.
Thanks!

@Xerkus You can even leave a comment on the issue if you want, and I can then draft up the migration doc changes.


vscode-icons installation failure

Expected Behavior

Flawless installation.
Current Behavior

> choco install vscode-icons -y
Chocolatey v0.10.11
Installing the following packages:
vscode-icons
By installing you accept licenses for the packages.
Progress: Downloading vscode-icons <IP_ADDRESS>80620... 100%

vscode-icons v<IP_ADDRESS>80620 [Approved]
vscode-icons package files install completed. Performing other installation steps.
Extension 'robertohuertasm.vscode-icons' not found.
Make sure you use the full extension ID, including the publisher, eg: ms-vscode.csharp

Failed Installing Extensions: robertohuertasm.vscode-icons

Possible Solution

Steps to Reproduce (for bugs)

On a fresh choco bootstrap: choco install vscode-icons -y

Context

Your Environment

Package Version used:
Operating System and version:
Chocolatey version:
Install/uninstall gist:

Looks like the publisher of this extension has changed. As a result, an update to the package will be required.

On 14/03/2019 11:32, Gary Ewan Park wrote:

Looks like the publisher of this extension has changed. As a result,
an update to the package will be required.

The publisher seems to be now 'VSCode Icons Team' now.
Thanks.
--
Jérôme Benoit aka fraggle
Piment Noir - https://piment-noir.org
OpenPGP Key ID : 27B535D3
Key fingerprint : B799 BBF6 8EC8 911B B8D7 CDBC C3B1 92C6 27B5 35D3

@jerome-benoit exactly.
So this line:
https://github.com/chocolatey/chocolatey-coreteampackages/blob/master/manual/vscode-extensions/vscode-icons/tools/chocolateyInstall.ps1#L2
Will need to be changed, and a new package version pushed.

Updating that package was on my TODO list (updating to make use of chocolatey-vscode.extension). So I'll take care of updating with the correct publishers as well.

changes have been made, and a new version should be pushed to chocolatey soon.


Feature include redux architecture to dev

#30 should be the valid one, as it's the same as this PR, plus the endpoint change


Current search bar is clunky

Feature request:
A new Searching experience to the user by creating a more user-friendly and modern Search bar.
Is your feature request related to a problem? Please describe:
Currently the Search Box we're using looks a bit broad, clunky and unsightly.
Whenever a user start typing in the field it adapts its shape according to the input which doesn't look good and provides bad experience. Also, it's not that responsive, especially when it comes to the mobile viewport.

Describe the solution you'd like:
I want to provide a new searching experience to the user by bringing an interactive and responsive search bar I already created.
Which will remove the clunkiness of the old one.
Here's a glimpse of search bar:

It will perfectly match the overall Color Scheme of our website.
Will give interactive and flexible experience to the user.
A little animation used here will provide nice experience to the user.
The small space used here will help user focus on more important contents of the page.

@vaishali614, what are your thoughts on this?
If it's okay shall I start working ?

@leoshrey The new search bar looks great, but I feel the whole navbar needs to be revamped.
Let me know if you can work on the whole navbar.

Ya, that's what I also thought, we should revamp the whole Navbar.

Let me know if you can work on the whole navbar.

Sure, I'll work on that too.
I think I should create a specific issue for that, so that it can be simple.
Firstly, I should revamp the search bar (solve this issue) and then the whole Navbar.
What are your thoughts ?

Ya, that's what I also thought, we should revamp the whole Navbar.

Let me know if you can work on the whole navbar.

Sure, I'll work on that too.
I think I should create a specific issue for that, so that it can be simple.
Firstly, I should revamp the search bar (solve this issue) and then the whole Navbar.
What are your thoughts ?

Okay, sounds good. Go ahead.

Okay, sounds good. Go ahead.

Sure


Error with the update in Best practice for instantiating Prisma Client with Next.js

Probably fixed via https://github.com/prisma/docs/pull/5978 already?

This has indeed been resolved! If you find another issue with the docs, feel free to open another one in the future @rathoreyuvraj19 🙌


Inference Instructions

Hi thank you for your work on StoryDALL-E. I am currently in need of experimenting with the outputs so could you share your inference instructions?

A gentle reminder to this issue. I am very interested in this project and would like to run the model on my local system

Hi,
Thanks for your interest in this work! Apologies for the delay in uploading inference instructions. The codebase now has inference scripts for minDALLE, which has also been used in our demos.


Change "Vendor" filter to "Publisher"

Closes #411

Firefox 55.0.0 (Linux 0.0.0): Executed 0 of 0 ERROR (0.079 secs / 0 secs)

Hm, looks like a test flak in Travis. Going to close and reopen the pull to kick the tests.

@jeff-phillips-18 @dtaylor113 For some reason, tests aren't running in Travis.

@jeff-phillips-18 @dtaylor113 For some reason, tests aren't running in Travis.

Travis is now using Firefox 55.0.0 which has issues running the unit tests.

@dtaylor113 Thanks, testing if latest-esr works for Travis in #432

Closing and reopening to kick the Travis tests


Add doctests and integration tests for repeating forms

Really grateful for your test cases, they revealed some weak points in the existing code. The doctest/long project xml files/test files have been updated and everything works as expected. Once merging this, you'll be ready to add unit tests (if you want 😉 )

Just wanted to sneak the docs update in there while I was thinking about it. I def need a checklist for things to do when adding a new category of endpoints 😅


ADBDEV-1885. Add --compression-type. Refactor compression in helper

Add a flag to set compression type. gzip is the only currently supported value. To disable compression, --no-compression or --compression-level 0 are to be set. gzip is also the default value for this parameter.
In helper, introduce backup_helper_pipes.go. This defines wrappers for buffer writers encapsulating various compression types (currently "no compression" and "gzip"). This allows to drop (somewhat) complex Writer closure algorithm in backup_helper.go.
Update helper_test and compression_test according to new changes.

@Stolb27 please add other reviewers whose contribution you think could be useful.

I suppose we should add the same validation for the new flag: --no-compression and --compression-type are exclusive
https://github.com/arenadata/gpbackup/blob/c06438097db52307acab3681a3dbba829f49044e/backup/validate.go#L102

Thanks @hughcapet . Fixed in https://github.com/arenadata/gpbackup/pull/2/commits/a34b75eb0d68606b4b8be02a352bd97a2f8f04bb. In this commit, I have also modified the compression type & level validation function, introducing a more flexible implementation.

@leskin-in
Do we really need unreleased yet changes from upstream master? These commits aren't included in any tag. But may contain unstable changes.
Please change base (and rebase previously) branch to origin/master if not.

@Stolb27 ,
we are going to open a PR to upstream, and then backport changes into our master branch. For this reason, there is no use in branching from our master or some older version (with tag) of upstream's master.

@Stolb27 ,
the mentioned problem is fixed in https://github.com/arenadata/gpbackup/pull/2/commits/80bb1c4e90515f571117c0a1ff0862d1851504c4.
The change effectively means gprestore is backward-compatible.

I think we may close this one. Further review is moving to upstream #523


add nullability annotations

Why i open PR
Why nullability annotations need
In this day, Many iOS App Project build on Swift. But JTCalendar is not suitable for those. So, I want to fix it.
In the first step, add nullability annotations. Optional is very important in Swift. Specially extention Reactive struct for RxSwift. This PR is gonna help to Many Project on Swift.
Work
I just add nullability annotations to few Method and Properties.

Thanks, I wanna do it for a long time

I released your changes as 2.2.5 version.

Thanks!
I really glad to be part of it!


cmd buffer on cli

does it use readline library?

does not seem to support vi or Emacs edit modes
behaves inconsistently in recall and history limits
centos 6.6 latest 0.9.0 download

@corylanou what are the details of the CLI history buffer?
This is not an actionable issue or bug, closing issue.
@biskit<EMAIL_ADDRESS>(private convo) or<EMAIL_ADDRESS>(public list) are more appropriate channels to ask open-ended questions. GitHub is for bug reports and feature requests.

to rephrase:
documentation says .influx_history holds upto 10000 commands

scrolling up or down does not move up or down history all the time (hangs scrolling)
editing works with emacs mode sometimes and does not sometime

typically happens after moving back and forth the history a few times.


Use myself agent and environment

Hi, I want to use a robot named mir100 in  maze in gazebo, which is a robot simulator, I am not sure if it's convenient to use tensorforce to apply various RL algorithms to realize the navigation task and compare their behaviors. Any advice? Thank you.

I would definitely say that this is the case, at least that's one of the main motivations for Tensorforce. Deep RL is obviously a rather early research topic, so things may not always be working smoothly, but again, Tensorforce aims to help practitioners avoid many of the common issues. Feel free to get in touch via Gitter if you want to discuss things more.


Validate HEAD requests properly before clicking on password reset link received via an email

SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to<EMAIL_ADDRESS>Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.
What version of UAA are you running?
We are using 76.13.0.
How are you deploying the UAA?
I am deploying the UAA

using a bosh release I downloaded from bosh.io

What did you do?

User tries to reset his password by clicking "Reset password" on UAA Login screen.
User provides email and clicks "SEND RESET PASSWORD LINK"
User opens the link and receives "Sorry, your reset password link is no longer valid. You can request another one below."

Current observation
Users having these issues are using Outlook and probably Outlook's Safelink protection invalidates the link even before user can.
What did you expect to see? What goal are you trying to achieve with the UAA?

Passwort reset window opens to set a new password

What did you see instead?
Error panel saying "Sorry, your reset password link is no longer valid. You can request another one below."
Assumption
Outlook's safelink protection opens the link as HEAD request which is handled as GET. Potential fix would be to handle HEAD requests properly before clicking on password reset link received via an email

you have created 2 PRs, are there more to come from your side ?

@strehle That's all from my side


b2b Suite - Names incorrect after login

PHP Version: 8.2   | Shopware Version: <IP_ADDRESS> and <IP_ADDRESS>  | Affected area / extension: Extension:B2B-Suite

Expected behaviour:
The name at the top right should always be the name of the account.
Actual behaviour:
If I am in a sales representative account and log in as a customer, everything works fine.  Presumably because the session is not ended as soon as you log in as a customer from the sales representative account.
How to reproduce:

Log in as external customer (Marked as sales representative)
Log in as one customer listed within this account
Log out
Log in as external customer (Marked as sales representative)

[public] Shopware automated response: This issue is linked to the internal issue: B2B-1269
[created from B2B-1269, comment 492527]

We solved this issue by decorating the following files:
`
// SalesRepresentativeSubscriber
public function redirectSalesRepresentative(ControllerEvent $event): void
{
if (!$this->authenticationService->is(SalesRepresentativeIdentity::class) && $this->getRequestAction($event) === 'clientLogin') {
return;
}
    parent::redirectSalesRepresentative($event);
}

private function getRequestAction(ControllerEvent $args): string
{
    $attributes = $args->getRequest()->attributes;

    if (!$attributes->has('_b2b')) {
        return '';
    }

    return $attributes->getAlpha('_b2b_controller_action');
}/`

`
// SalesRepresentativeController
public function indexAction(): array
{
if ($this->storage->get(SalesRepresentativeIdentity::AUTH_ID_KEY)) {
$this->salesRepresentativeLoginAction();
}
    return parent::indexAction();
}

public function clientLoginAction(Request $request): void
{
    $salesRepresentativeAuthId = $this->storage->get(SalesRepresentativeIdentity::AUTH_ID_KEY);

    if ($salesRepresentativeAuthId) {
        $this->salesRepresentativeLoginService->logoutFromClient();
        $salesRepresentativeIdentity = $this->authenticationService->getIdentityByAuthId($salesRepresentativeAuthId);
        $this->authStorageAdapter->setIdentity($salesRepresentativeIdentity);
    }

    parent::clientLoginAction($request);
}

`

We solved this issue by decorating the following files:
SalesRepresentativeSubscriber:
public function redirectSalesRepresentative(ControllerEvent $event): void
    {
        if (!$this->authenticationService->is(SalesRepresentativeIdentity::class) && $this->getRequestAction($event) === 'clientLogin') {
            return;
        }

        parent::redirectSalesRepresentative($event);
    }
    private function getRequestAction(ControllerEvent $args): string
    {
        $attributes = $args->getRequest()->attributes;

        if (!$attributes->has('_b2b')) {
            return '';
        }

        return $attributes->getAlpha('_b2b_controller_action');
}

SalesRepresentativeController:
public function indexAction(): array
    {
        if ($this->storage->get(SalesRepresentativeIdentity::AUTH_ID_KEY)) {
            $this->salesRepresentativeLoginAction();
        }

        return parent::indexAction();
    }

    public function clientLoginAction(Request $request): void
    {
        $salesRepresentativeAuthId = $this->storage->get(SalesRepresentativeIdentity::AUTH_ID_KEY);

        if ($salesRepresentativeAuthId) {
            $this->salesRepresentativeLoginService->logoutFromClient();
            $salesRepresentativeIdentity = $this->authenticationService->getIdentityByAuthId($salesRepresentativeAuthId);
            $this->authStorageAdapter->setIdentity($salesRepresentativeIdentity);
        }

        parent::clientLoginAction($request);
    }


How to send messages to phone numbers other than default?

As written in the "Usage" section it should be possible to send messages to phone numbers that are not the default one configured.
But this function is neither documented somewhere at https://www.callmebot.com/ nor do I receive those messages.
Also, when I try to send those messages through the browser directly, I receive "APIKey is invalid" as a result.
So how is that functionality considered to work?

I check it.

Same here, thanks for checking!
A possible current workaround could be to create another adapter registered to the second number and integrate this additionally.

Yes, that's a good workaround 👍. I use it so for my phone number and my wife's phone number.
Create the code is not the problem... but the time to create 😅.
I hope, I can work on this next week.

Any news on this feature request?


[BUG]: .confirmSetup promise doesn't resolve

What happened?
I'm trying to handle errors for .confirmSetup call.
const { setupIntent, error } = await this.stripe.confirmSetup({
  elements: this.stripeElements,
  redirect: 'if_required',
  confirmParams: {
    return_url: window.location.hash,
  },
});

debugger;

if (error) {
  this.handleError(error);
...

When I use 4000 0000 0000 0002 card it properly triggers card_error with generic_decline and the piece above stops on debugger line (and I can handle the error).
But as soon as I try to use Apple Pay and select the card from Wallet, which I know will trigger the same error (card_error + generic_decline) - nothing happens. I never get to debugger statement, I don't have any response, nothing happens at all.
One thing to note thought - I can see failed request to /v1/token with 402 status code and response body having proper error information, but it never gets returned from .confirmSetup.
P.S. I've tried both Discord and Support chat. In Discord I was told that yes, it looks like a bug and I can follow up in Support chat to get status update for this issue. Past 5 days - Support chat doesn't know about it and thinks I'm requesting a new feature.
Environment
Safari Version 15.6.1 (176<IP_ADDRESS>.16) on macOS Monterey 12.5.1 (21G83)
Reproduction
No response

@oaleynik Thank you for flagging this. We are actively investigating this issue and will report back with results.

@cyuen-stripe thanks for response! Let me know if you need anything else from me - I will be happy to provide more info 👍🏻

@oaleynik We're able to reproduce the issue with the information you provided and determined that it's an underlying issue with Stripe.js script. The Stripe.js loader is a wrapper around that, so we don’t track those issues here. We are tracking and prioritizing this issue internally.

@cyuen-stripe makes sense. Who can I contact to to get status of that issue?

@oaleynik This issue is being worked on right now. We don't have an ETA, but we will post back here when the fix is deployed.

Any update on this? We've been seeing the same issue with ApplePay - everything just hangs for some customers through the payment element. @cyuen-stripe is there any sort of work around we can do in the meantime or any further information on how/when it occurs?

I've also been getting this same issue in the last few days - we've had to temporarily disable support for ApplePay as a result of it. I've not been able to identify a pattern of devices/OS version that this seems to be a problem with, but we were getting a frustratingly high failure rate, so had to pull the functionality.
Looking forward to an update on when this will be resolved.

We're still working towards a solution for this.

Same issue here with Apple Pay and Stripe Element. Also difficult to identify a pattern between devices and OS. We see it happening on Mac and iPhones

Ping to keep this alive

I had a message from a contact at Stripe this week who said the following about this issue:
I caught up with a colleague earlier today who stated that we may have found a fix, but we still need to do more thorough testing to make sure it doesn't impact other aspects of the service.
Really hoping this is the case and we can reliably use ApplePay soon.

Hi all - we've just deployed a fix for this. Apologies for the delay, and feel free to open this issue back up if you still see the problem persisting!

@jackieosborn-stripe thank you, Jackie!

I'm still not able to resolve this promise.
I'm directly loading the stripe script from https://js.stripe.com/v3/.


Release DataFusion 15.0.0

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I plan on creating DataFusion 15.0.0-rc1 on Friday 2nd December (4 weeks since the previous release).
Describe the solution you'd like

[ ] Update version & generate changelog
[ ] Cut RC and start vote
[ ] Vote passes
[ ] Release to crates.io
[ ] Publish documentation

Describe alternatives you've considered
Additional context

@tustvold  do you know of anything critical in  arrow 30.0.0 https://github.com/apache/arrow-datafusion/pull/4818 for datafusion (aka should @andygrove hold the release for it)? I couldn't think of anything

Nothing critical, just some nice to haves

Thanks, I will go ahead with creating the RC for 16.0.0. This issue is for 15.0.0 so will close this. New issue is https://github.com/apache/arrow-datafusion/issues/4776


Fix sanity checker

Somehow the script hack to get the color support working doesn't report the exit codes correctly.
I might have a look into this later, but for now canFind("Error:") should work too.

For reference, it failed before the PR to dlang-tour/english was merged:

Is this invalid now? @wilzbach


TimeScale xAxis last tick not visible

Hello,
See my plunk here : http://plnkr.co/edit/LyWEV9?p=preview
I'm using chart.js 2.0.0 and angular-chart.js last version.
I have a time scale on data for a week but the last tick on Sunday is not visible, not displayed or displayed out of canvas I don't know.
Not sure if this is from Chart.js or angular-chart or how I'm using both but have to try here as I would bet on it more than the angular wrapper (maybe I'm wrong)
Thanks,

I think this is from the time scale. Bars on time scales are hard to support. I'll try and think of some ways we can improve this.

It was "almost" working with Chart.js v2.0.0-beta-2.
Almost because the timestamp of last tick had to be 1ms more than start of the last day (sunday). Except that little manual trick it was fine.

@peterzebird I upgraded your plunkr to v2.1.2 and it's looking a little better
http://plnkr.co/edit/guSgb1u6rzZITHhIv4VM?p=preview

Plunkr with v2.5.0: http://plnkr.co/edit/5HhT4fA27RZCWsHdRDRs?p=preview

Hi !
I'm drawing charts with Chart.js 2.5.0 on my project.
Unfortunately, the issue is still in the news. The last item is never shown.
@etimberg Below, a picture coming from your plunker.

Nevertheless, in my case I find a workaround by setting the max value to the last value of labels (containing timestamp) + a delta.
var delta = intervalTimeSelected * nbMillisecondsFromUnitSelected;
chart.options.scales.xAxes[0].time.max = lastValue + delta;

intervalTimeSelectedvar intervalTimeSelected = chart.options.scales.xAxes[0].time.unitStepSize;

nbMillisecondsFromUnitSelected// We could have a switch on chart.options.scales.xAxes[0].time.unit to determine
// nbMillisecondsFromUnitSelected. Here, it's just an example.
if (chart.options.scales.xAxes[0].time.unit === "minute") {
  var nbMillisecondsFromUnitSelected = 60000;
}

I update your plunker with my workaround: http://plnkr.co/edit/AHnqqpwL7OajQiWn966Q?p=preview
I change values from $cope.graph.data

This bug is affecting me as well. Why was this issue closed if it still exists? Is it being tracked elsewhere?

@kennyjwilli I don't believe it is. I've been looking for hours now. I think the issue is just being ignored.

@ampalmer1 the solution to this specific issue was fixed in 2.5.0 as the last 'Sunday' tick mark is now visible. Further, when I run the fiddle I created above I can see part of the last bar.
This issue did not cover the fact that the last bar may or may not be visible. There is another issue that covers that.
In general, it seems very unclear how bars on a time scale should behave. Unlike an axis that is built from string labels, a time axis is a continuous range of values. We could have bars nicely spaced at 12:00AM each day, or we could have a bar at 12:00AM and 12:01AM and would need to ensure that they do not overlap but are also both visible to the user and tooltips.
I am happy to look at a PR that improves this, but it needs to be a comprehensive solution rather than a quick fix that only works for certain cases.

@etimberg Thanks for the reply.
The main issue always linked is #2415. Unless I am misunderstanding the problem, it sounds like it only occurs when data spans multiple years. The issue I (and I assume @ampalmer1 and others) have is the missing last bar. See @VictorRos's plnkr.
There is also #3297 which sounds exactly like this problem but is again linked back to #2415. If that is where this issue is being tracked, I think the title and description should be updated to document the general problem :smile:

@kennyjwilli #2415 is the one I was thinking of. I will update the title to be more descriptive.


Targeting lure/lure with Cave Bot is too fast on high level characters.

This leads to monsters losing targeting range, which results in a loss of xp.

Fixed in v2.2.1, an upcoming small patch. Closing this issue.


Update README

Simplify README and provide correct build instructions.

I realize this conflicts some with #44, but I think this is a step in the right direction to simplify the README with correct build instructions now.


Add and use dependencies from another playground permalink

I would like to reuse code saved in one playground in another, different playground without having to copy-paste the contents of the original, or having to publish it. This could be useful in several scenarios:

📚 Publishing some light library and reusing it in multiple pastes. If there are many copies of a paste with small differences (which I suspect is a common pattern), this could reduce total paste size and improve compile times for the playground runners by caching the dependencies' object files.
🐛 If someone is using a paste to demonstrate an issue with their code, reusing it as a dependency with some small tweak would naturally highlight the changes made and may aid their comprehension of the solution.
👨🏫 For education purposes, I could see a teacher create a paste that exposes public evaluation functions which must be called to clear some assignment. This would enable the student to focus on the assignment tasks and enables the teacher to know that the evaluation code was not tampered with.

👋 To use it, the playground could reserve a special module name pattern that would dynamically pull in other gists when referencing public items within it. 🚲 Bikeshedding notwithstanding, perhaps something like:
use gist_16aa5441c37dc67c7ce0c8b4b48c194b::{some_pub_fn, other_pub_fn};
// or under some namespace:
use playground::gist_16aa5441c37dc67c7ce0c8b4b48c194b::{some_pub_fn, other_pub_fn};

👩💻 I'm unsure exactly how this could be implemented. Maybe proc macros? A build.rs script that downloads the gist file before compilation? (this could even be reused outside of a playground environment [very carefully]). If using these features introduces undesirable attack surface, parsing the paste for use statements ahead of time could still be workable.
🔐 I don't think this would cause a material change to possible abuse cases. Obviously, gists saved by the playground are never changed so using another gist as a dependency could not cause pastes to break or cause some observable change in behavior. Total compilation+runtime would still be bounded by the playground runner. Dependencies would still have to be trees, and any code that uses this "paste splitting" feature could be automatically rewritten into a single file to review manually if needed.
Thoughts?

An interesting idea! Allow me to respond inline with a stream of consciousness...

Publishing some light library and reusing it in multiple pastes.

Believable, but it's hard to know how many people would use such a feature, and thus how much of a return-on-investment we might get.

If there are many copies of a paste with small differences (which I suspect is a common pattern), this could reduce total paste size

I don't exactly follow how — are you saying that someone would perform the work to extract the common code into this new library style and then just reference that?

improve compile times for the playground runners by caching the dependencies' object files.

I don't think this is a likely outcome. We really never want to share things between compilation sessions of different users.

If someone is using a paste to demonstrate an issue with their code, reusing it as a dependency with some small tweak would naturally highlight the changes made and may aid their comprehension of the solution.

Having a diff of sorts does seem useful, but I'm not following how it would work with this solution. If someone brings it in as a dependency, how would they then edit the dependency?

I could see a teacher create a paste that exposes public evaluation functions which must be called to clear some assignment. This would enable the student to focus on the assignment tasks

I agree (and I use the playground a lot for teaching purposes!).

and enables the teacher to know that the evaluation code was not tampered with.

How does this co-exist with the previous "with some small tweak"?

I don't think this would cause a material change to possible abuse cases.

I agree in general. The main problem I could see would be some form of DOS attack if we allowed recursive dependencies (especially if they were self-referential). That should be avoidable by only going one level deep.

Implementation wise, I can share some semi-planned future work that might make this more achievable. For a long time, people have been wanting to create multiple files, both for modules as well as multiple crates. I've been thinking about extending the playground's gist format to include a special TOML file (or something) that would allow us to store multiple files / a Cargo.toml / etc. If that happens, we could load that and rename the crate, leveraging normal Cargo packages.
That would make this feature mostly a front-end task focused on shuffling around the files appropriately.

We really never want to share things between compilation sessions

Reasonable.

If someone brings it in as a dependency, how would they then edit the dependency?

Maybe this was a bit of a stretch, basically the 'library' code would have to be organized in a way to enable dependents to swap out parts. This should be possible to design intentionally, but I agree that it would not work for arbitrary code.

I've been thinking about extending the playground's gist format to .. store multiple files .. If that happens, we could load [a previous gist] and rename the crate, leveraging normal Cargo packages. That would make this feature mostly a front-end task focused on shuffling around the files appropriately.

This sounds like a great way to implement this feature.


Added two other required columns and added indexs

@ub0005 Looks good. But one thing:
Have we also updated the PATCH request for storage ids? (Just to make sure we have CRUD also...)

@ub0005 Looks good. But one thing: Have we also updated the PATCH request for storage ids? (Just to make sure we have CRUD also...)

Yes, @NISH1001 Patch requests take care of these additional fields automatically, no code modification is required, as we changed the models and schemas.

LGTM.

LGTM.


Feature/rvi Robust Variational Inference

Check progress

I added a couple tests and test models to go with them.
Start with this one:
./runTests.py test/unit/variational/rvi_std_normal_test

You're fitting a normal(0, 1) there and the idea is that you can slowly un-comment and add print statements to run_rb and make sure everything is working the way you expect.
There is a slightly harder test as well:
./runTests.py test/unit/variational/rvi_two_normals_test

On the algorithm side, should we be using RMSprop? From the last e-mail Jonathan sent "we use RMSProp as our base stochastic optimizer, so we can pretty much safely choose a step size 0.1 to start for any problem."
I was looking at the paper and it kinda hand-waved that the technique technically only applies to SGD but would probably work for these adaptive timestep things as long as the adaptation isn't based on things long in the past. If nobody knows we can ask.
On the C++ side, I've found it really handy to keep the clang sanitizer on lately (https://clang.llvm.org/docs/AddressSanitizer.html). It does a good job at catching memory errors. This is what my make/local looks like:
CXX=clang++
O=1
CXXFLAGS=-g -fsanitize=address -ftemplate-backtrace-limit=0 -fno-omit-frame-pointer
LDFLAGS=-g -fsanitize=address -fno-omit-frame-pointer

So if I get a segfault, there's already debugging enabled so I can run the debugger, and the sanitizer catches stuff that might not even totally blow up the program.

I added a couple tests and test models to go with them.
Start with this one:
./runTests.py test/unit/variational/rvi_std_normal_test

You're fitting a normal(0, 1) there and the idea is that you can slowly un-comment and add print statements to run_rb and make sure everything is working the way you expect.
There is a slightly harder test as well:
./runTests.py test/unit/variational/rvi_two_normals_test

On the algorithm side, should we be using RMSprop? From the last e-mail Jonathan sent "we use RMSProp as our base stochastic optimizer, so we can pretty much safely choose a step size 0.1 to start for any problem."
I was looking at the paper and it kinda hand-waved that the technique technically only applies to SGD but would probably work for these adaptive timestep things as long as the adaptation isn't based on things long in the past. If nobody knows we can ask.
On the C++ side, I've found it really handy to keep the clang sanitizer on lately (https://clang.llvm.org/docs/AddressSanitizer.html). It does a good job at catching memory errors. This is what my make/local looks like:
CXX=clang++
O=1
CXXFLAGS=-g -fsanitize=address -ftemplate-backtrace-limit=0 -fno-omit-frame-pointer
LDFLAGS=-g -fsanitize=address -fno-omit-frame-pointer

So if I get a segfault, there's already debugging enabled so I can run the debugger, and the sanitizer catches stuff that might not even totally blow up the program.

@bbbales2 Thanks! They'll definitely be helpful.
I believe what you said about rmsprop is true. Before we detect stationarity(so before SASA+ kicks in), we'd set the learning rate with RMSprop. I think Jonathan is saying that a-naught in SASA+ would be set to 0.1
Using an address sanitizer would be great since I'm working with alot of pointer arithmetic and would hopefully catch where I messed up.

@bbbales2 Thanks! They'll definitely be helpful.
I believe what you said about rmsprop is true. Before we detect stationarity(so before SASA+ kicks in), we'd set the learning rate with RMSprop. I think Jonathan is saying that a-naught in SASA+ would be set to 0.1
Using an address sanitizer would be great since I'm working with alot of pointer arithmetic and would hopefully catch where I messed up.

Yeah maybe the RMSprop starting with 0.1 is for once there is a SASA+-like component in there. I saw the adapt_eta function in there and that would definitely be a nice function to replace/clean up eventually. Leave it for now if it gets a good starting timestep tho.

Yeah maybe the RMSprop starting with 0.1 is for once there is a SASA+-like component in there. I saw the adapt_eta function in there and that would definitely be a nice function to replace/clean up eventually. Leave it for now if it gets a good starting timestep tho.

Okay. RVI will now run successfully when n_chains > 1 (I haven't finished up with split rhat for the single chain version to work).
I've toyed around with the parameters and the one that I've set to in the last commit seems to work best(at least in the sense of retrieving mu).
There are a few of interesting observations:

Regardless of the number of chains, khat for each chain would all return infinity. This means that the result would be calculated from only the last W iterates, instead of the MCSE and ESS based cutoff.
 For the std_normal model, running with 2 chains would terminate super fast(sets T_naught as 50 out of 1000 max iterations) and return the final mu as -0.4(terrible). On the other hand, 4 chains would run all the way up to 1000 iterations, and return -0.0009 as its final result. So I think running a minimum of 4 chains would be good for half-decent results.

Okay. RVI will now run successfully when n_chains > 1 (I haven't finished up with split rhat for the single chain version to work).
I've toyed around with the parameters and the one that I've set to in the last commit seems to work best(at least in the sense of retrieving mu).
There are a few of interesting observations:

Regardless of the number of chains, khat for each chain would all return infinity. This means that the result would be calculated from only the last W iterates, instead of the MCSE and ESS based cutoff.
 For the std_normal model, running with 2 chains would terminate super fast(sets T_naught as 50 out of 1000 max iterations) and return the final mu as -0.4(terrible). On the other hand, 4 chains would run all the way up to 1000 iterations, and return -0.0009 as its final result. So I think running a minimum of 4 chains would be good for half-decent results.

Hmm, if it's running, on the test cases, my feeling is we should go ahead and pipe this out to the cmdstan level so we can start running full models on it (that'll give us more confidence that the basic algorithm is working, even as more stuff is added).
What possible flags do we need to pass in from the outside? I copy-pasted our current variational inference options below, I imagine we need to add more (like how many internal chains to use). Maybe we should remove some too. If you can write down what extra arguments we need (and default values and possible ranges), I can put up a cmdstan branch that has the stuff in it (and once you see the example you'll know how to change it yourself) and this way we can have a full working cmdstan:
variational
      Variational inference
      Valid subarguments: algorithm, iter, grad_samples, elbo_samples, eta, adapt, tol_rel_obj, eval_elbo, output_samples

      algorithm=<list element>
        Variational inference algorithm
        Valid values: meanfield, fullrank
        Defaults to meanfield

        meanfield
          mean-field approximation

        fullrank
          full-rank covariance

      iter=<int>
        Maximum number of ADVI iterations.
        Valid values: 0 < iter
        Defaults to 10000

      grad_samples=<int>
        Number of Monte Carlo draws for computing the gradient.
        Valid values: 0 < num_samples
        Defaults to 1

      elbo_samples=<int>
        Number of Monte Carlo draws for estimate of ELBO.
        Valid values: 0 < num_samples
        Defaults to 100

      eta=<double>
        Stepsize scaling parameter.
        Valid values: 0 < eta
        Defaults to 1

      adapt
        Eta Adaptation for Variational Inference
        Valid subarguments: engaged, iter

        engaged=<boolean>
          Boolean flag for eta adaptation.
          Valid values: [0, 1]
          Defaults to 1

        iter=<int>
          Number of iterations for eta adaptation.
          Valid values: 0 < iter
          Defaults to 50

      tol_rel_obj=<double>
        Relative tolerance parameter for convergence.
        Valid values: 0 <= tol
        Defaults to 0.01

      eval_elbo=<int>
        Number of iterations between ELBO evaluations
        Valid values: 0 < eval_elbo
        Defaults to 100

      output_samples=<int>
        Number of approximate posterior output draws to save.
        Valid values: 0 < output_samples
        Defaults to 1000

Hmm, if it's running, on the test cases, my feeling is we should go ahead and pipe this out to the cmdstan level so we can start running full models on it (that'll give us more confidence that the basic algorithm is working, even as more stuff is added).
What possible flags do we need to pass in from the outside? I copy-pasted our current variational inference options below, I imagine we need to add more (like how many internal chains to use). Maybe we should remove some too. If you can write down what extra arguments we need (and default values and possible ranges), I can put up a cmdstan branch that has the stuff in it (and once you see the example you'll know how to change it yourself) and this way we can have a full working cmdstan:
variational
      Variational inference
      Valid subarguments: algorithm, iter, grad_samples, elbo_samples, eta, adapt, tol_rel_obj, eval_elbo, output_samples

      algorithm=<list element>
        Variational inference algorithm
        Valid values: meanfield, fullrank
        Defaults to meanfield

        meanfield
          mean-field approximation

        fullrank
          full-rank covariance

      iter=<int>
        Maximum number of ADVI iterations.
        Valid values: 0 < iter
        Defaults to 10000

      grad_samples=<int>
        Number of Monte Carlo draws for computing the gradient.
        Valid values: 0 < num_samples
        Defaults to 1

      elbo_samples=<int>
        Number of Monte Carlo draws for estimate of ELBO.
        Valid values: 0 < num_samples
        Defaults to 100

      eta=<double>
        Stepsize scaling parameter.
        Valid values: 0 < eta
        Defaults to 1

      adapt
        Eta Adaptation for Variational Inference
        Valid subarguments: engaged, iter

        engaged=<boolean>
          Boolean flag for eta adaptation.
          Valid values: [0, 1]
          Defaults to 1

        iter=<int>
          Number of iterations for eta adaptation.
          Valid values: 0 < iter
          Defaults to 50

      tol_rel_obj=<double>
        Relative tolerance parameter for convergence.
        Valid values: 0 <= tol
        Defaults to 0.01

      eval_elbo=<int>
        Number of iterations between ELBO evaluations
        Valid values: 0 < eval_elbo
        Defaults to 100

      output_samples=<int>
        Number of approximate posterior output draws to save.
        Valid values: 0 < output_samples
        Defaults to 1000

Flags up to adapt would all be needed. Tol_rel_obj and eval_elbo would be replaced with the following:

max_runs = 10000
maximum number of iterations
eval_window = 100
Evaluation window length, and iterations between evaluations
rhat_cut = 1.1
Rhat threshold to stop preliminary optimization loop
mcse_cut = 20
Mcse threshold to set iterate averaging limit
ess_cut = 20
Ess threshold to set iterate averaging limit
num_chains = 4
Number of optimization chains to run
adapt_iterations = 100
Number of iterations to set initial stepsize

Flags up to adapt would all be needed. Tol_rel_obj and eval_elbo would be replaced with the following:

max_runs = 10000
maximum number of iterations
eval_window = 100
Evaluation window length, and iterations between evaluations
rhat_cut = 1.1
Rhat threshold to stop preliminary optimization loop
mcse_cut = 20
Mcse threshold to set iterate averaging limit
ess_cut = 20
Ess threshold to set iterate averaging limit
num_chains = 4
Number of optimization chains to run
adapt_iterations = 100
Number of iterations to set initial stepsize


How to set training labeled sample number in SGAN

There doesn't have a ratio of unlabeled and labeled training data in the code.

Hello. Did you find this?


Revised and merged the subtraction operator articles

Supported by dotnet/samples#929

closing and re-opening for a new build.


Linkage Analysis Pipeline in Galaxy

Linkage Analysis Pipeline in Galaxy
Supervisor: Mehmet Tekman
For degree: Bachelor
Status: Open
Keywords: Linkage, Haplotypes, pipeline
Global Biological/Research context
Classical linkage analysis is the method of looking for genes that are inherited together in a family tree, which has been now superseded by variant analysis in the era of high-throughput sequencing, but is still relevant in rare disease studies. The Galaxy project is a free and open-source web-based platform for bioinformatic research, and offers users an interactive drag-and-drop avenue to perform their analyses. This project would involve wrapping tools into Galaxy, and chaining them together in a workflow for public user access. Optionally, training material can be written to guide users through the analysis. Applicants need only to know basic HTML/XML and Markdown.
Project context
This project would complement rare disease and pedigree analysis
Objectives of the project

Tidy and merge existing PRs of linkage analysis tools
Construct a robust linkage analysis workflow using the above tools
Write a training material

Proposed agenda for the project

Establish a suite of a linkage analysis tools
Establish a workflow and training material

Prerequisites

XML
Conda

currently in progress


fix: removed whitespace as possible valid number

Possible fix for #76
I changed the checkIsValidNumber function in this case, as I don't think a whitespace should be considered a valid number. If it makes more sense, I could move this "bail" to the component as well.

Hi @stinodes, thanks for raising the issue and coming up with a fix!
I had a look at the code and thought it could be improved with a regex so I did some refactoring myself (PR #79). Therefore, I don't think this PR is required anymore, but thanks again for the great PR and even adding tests as well!

No worries, using a regex might be better indeed. It was my pleasure.
Cheers!


Create a cvs file of the ontology during release

The file will be used by non-ontology experts. Ideally the file should not contain top level classes that can be confusing for agronomists.

Creating a csv report on useful terms seems exactly what ENVO does using SPARQL reports creation pipeline, linked in #10 and
https://github.com/AgriculturalSemantics/agro/issues/10#issuecomment-223766814

Since the "subset reports" will be SPARQL-driven, perhaps the other reports from #11 can be done en passant:

Over in ENVO, we create simple tabular files for non-owl-inclined software developers to work with. These are dubbed "reports" and are simplistic exports of the ontology content. As this is SPARQL-driven (via arq and jena), perhaps you'd like to take a crack at impementing (and improving?) this @marieALaporte?
Our  sparql files produces reports. The Makefile drives this in these lines

Note to @KrishnaTO  to review ENVO's make recipe for reports


960px grid

I wonder why you are using 960px grid. This is commonly used because it is easy to divide by 2,3,4,5,6 - so great for 12columns grid. But your grid is implicit, so you are not limited to such size and you can use something, what would use far better the available viewport for different types of common devices, and it would be your great advantage.

I do have a few different wrappers with max-widths, one of which is 960px, but I wouldn't say I'm using a 960px grid. For my landing page, I like the readability of the 960px, even on my larger screen, so that was just a choice for that particular website, which I think is still a pretty common width.
There's also the grid break point for large screens at 960px, but that's just my lower bound for what I'm describing as a large screen. My breakpoints don't target particular device sizes because they're always changing, so they're just estimates for how something should look on a particular screen size.
I'd recommend using the best wrapper for the particular content and if the largest one at 1200px isn't large enough, I can consider adding wrapper-xlarge as an option or you don't need to use a wrapper at all, since the grid is always 100% of the width of the parent container.


pulp omitted from requirements

the conda-forge recipe is failing because we left pulp out of requirements.txt. It's in environment.yml

conda-forge/staged-recipes#13708

conda-forge/staged-recipes#13708


rework GetPageCountAsync as an extension method

https://github.com/adamfoneil/Dapper.QX/blob/9b3c7fe53c75d2feb0fc8a7409f1fd58077a3fdb/Dapper.QX/PageableQuery.cs#L22
This would make it work with any Query<T>. As it is, you have to use PageableQuery<T> as base type.

There will need to be a way to clear the Page property on a query, which means the extension method must attach to something that knows about a Page property. This means there's either an interface requirement or a delegate you have to pass that clears any Page property (or whatever you chose to name it) on your query. The added interface dependency undermines an extension method's usability

This could also possibly work by modifying the query's SQL to remove the {offset} token. That way, I wouldn't have to worry about clearing a Page property -- I could just not see the offset injector and run a "pageless" query to get the page count.

If you're going to remove the {offset} token, it would be better to remove the whole ORDER BY clause itself for the performance benefit.


btce upgrade info

26/08/15	BTC-e code API update
(source btce)

Hi there, is btce branch working ? Ty for you work

Hey, I tried for a while to get BTC-E working but their API is total garbage and wasn't going to work well with tribeca, so I gave it up. The branch is still there.

Not going to write to BTC-E.


Be more compliant with the OpenServiceBroker specification

The Open Service Broker specification specifies that the Metadata fields
in the catalog response are opaque objects. There is a convention that
the specification recommends be adhered to, which matches the structs
defined in this library (ServiceMetadata and ServicePlanMetadata), but
this convention is not mandated by the specification.
Changing the Service and ServicePlan structs to accept an "interface{}"
as the relevant Metadata allows implementers to provide any metadata
information, including the existing structs.
This proposed change is backwards compatible, but allows for more flexibility when using this library.

@liorokman sorry no one has gotten back to you sooner on this. Is this still something you would like in the broker API?

@deniseyu Yes, please.
--
Thanks,
Lior

@liorokman does #51 cover your use case?

Yes, #51 does cover my use case.

Great, we will follow up on #51 very soon so I'll close this. Thanks @alex-slynko @liorokman


Fix italicizing for multiline props #54

Slack doesn't handle single italization for multi line text. This means we need to italicize each line in multi line prop.
Related issue: https://github.com/netguru/props/issues/54

how about a spec?:)

bin/guard turned on during implementation?:)

@lubieniebieski of course! :smile: When I saw what it can do, I started using it immediately.

👍 💙


another idea : deep learning on web browser.

Wow thats a great ieda, I mean, if you could transfer the model to be well trained on the MCU to the website, it must be amazing!


Fix base branch reference for coveralls

What this PR does / why we need it:
Use PULL_BASE_REF for referencing the base branch for coverage (prow env var docs)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/hold

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/test pull-kubevirt-goveralls

/unhold

/retest

/test pull-kubevirt-goveralls

/test pull-kubevirt-prom-rules-verify
/test pull-kubevirt-manifests

/test pull-kubevirt-generate

/test pull-kubevirt-goveralls

/retest

/retest

@rmohr should be good now, PTAL. Thanks!

/lgtm
It does still not look correct, but it should unblock a postsubmit. We can iterate on it in a follow-up PR.

/retest

/retest

/retest

Now the unit tests ran into timeout (which is not typical according to the job history)


Before we can scaffold your project, we have a few questions
? What should we call this project? YumTools
? Select a frontend framework / library react
? Would you like to use StorybookJS? No
? Would you like to have git initialized? Yes
? Show verbose logs? Yes
Setting up your D.I.R.T Stack application...
Setting up project with log mode: Verbose
[info] » Setting up Django project...
[info] » executing scaffoldDjango...
[info] » creating project with name: YumTools
[info] » in directory:  /home/yumshot/Documents/Repos/TestTools/YumTools
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#".] {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v19.7.0
After testing, camelCase and lowercase work perfectly fine.

Currently unable to reproduce the issue on Ubuntu 22.04 LTS using the options specified above. I will leave this open so that we can gather more information.
More details about my environment
NodeJs v16.17.0
npm v8.15.0
Python 3.10.9

I was unable to produce the bug again, moved OS to arch linux
OS - Garuda Linux x86_64
KERN - 6.2.8-zen1-1-zen
WM - i3 (X11)
SHELL - bash 5.1.16
TERM - pipenv

I will note though that the pip install version of pipenv did not work, and I had to get the repo from an AUR to get it working. Im sure it could just be an env variable, however might be something to keep a note of for future / possible distro specific issues


Pre-run script with cli vs tower web

I have been playing around with submitting pipelines via both our Tower Enterprise deployment and the CLI (version 0.6.2).
In the Tower Compute Environment, I added a couple of lines for the pre-run script, and the pipeline ran fine.
However, when attempting to run the same pipeline with the CLI, the pre-run script from the compute environment was ignored, so that I had to specify its contents via a new pre-run script:
tw launch marco-test-pipeline-setonix --pre-run=/home/mdelapierre/bin/tower-prerun.sh

Any clue on why this is the case? Thanks,

Thanks @jordeu !
Do you have a tentative ETA for when the next tw-cli version with this bugfix will be officially released here on github?

This will be part of v0.7.0 release that should be available at the end of the week.

Thanks for sharing the info :-)

FYI just added the latest version of tower-agent and tower-cli to the Spack recipes:  https://github.com/spack/spack/pull/33545

Ey, very nice @marcodelapierre. Thanks!


Use ampbinner_10X.py on fasta file

Would it be possible to use the AmpBinner in 10X Mode on .fasta files?
Thank you in Advance!

The quality values in the fastq do not really matter. You can convert the fasta to fastq, just add an arbitrary quality value.
For example, you can use this seqtk: https://github.com/lh3/seqtk
seqtk seq -F 0 input.fasta > out.fastq
It will add '0' as the quality char, which corresponds to quality value 15.

Thank you Really Much, that solved it!


incompatible with nerfstudio 0.3.4 and wont run on 0.2.2

im running 0.3.4 and when im trying to ton install with pip i have this error message
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
nerfstudio-method-template 0.1.0 requires nerfstudio>=0.3.0, but you have nerfstudio 0.2.2 which is incompatible.
torchaudio 2.1.0+cu118 requires torch==2.1.0+cu118, but you have torch 1.13.1 which is incompatible.
Successfully installed google-auth-oauthlib-0.4.6 nerfstudio-0.2.2 tensorboard-2.9.0 tensorboard-data-server-0.6.1 torch-1.13.1 torchvision-0.14.1 zipnerf-0.1.0
so i tried to uninstall both nerfstudio and torch 1.31.1 and try to run pip install -e. again to see if it'll take the right package but no
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
nerfstudio-method-template 0.1.0 requires nerfstudio>=0.3.0, but you have nerfstudio 0.2.2 which is incompatible.
torchaudio 2.1.0+cu118 requires torch==2.1.0+cu118, but you have torch 1.13.1 which is incompatible.
Successfully installed nerfstudio-0.2.2 torch-1.13.1 zipnerf-0.1.0
zipnerf 0.1.0 requires nerfstudio==0.2.2, but you have nerfstudio 0.3.0 which is incompatible.
please help me out i think im in a big loop

** update **
when i finally have no more error message when install -e. and trying to run ns-train zipnerf i get this error message
(nerfstudio) C:\Users\Pigiste1\nerfstudio\zipnerf-nerfstudio-main>ns-train zipnerf-nerfstudio-main C:\Users\Pigiste1\nerfstudio\data\shutterstock_1080988859.mov
Traceback (most recent call last):
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\runpy.py", line 194, in run_module_as_main
return run_code(code, main_globals, None,
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\Scripts\ns-train.exe_main.py", line 4, in
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\scripts\train.py", line 49, in
from nerfstudio.configs.method_configs import AnnotatedBaseConfigUnion
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\nerfstudio\configs\method_configs.py", line 50, in
from nerfstudio.field_components.temporal_distortions import TemporalDistortionKind
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\nerfstudio\field_components_init.py", line 17, in
from .encodings import Encoding, ScalingAndOffset
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\nerfstudio\field_components\encodings.py", line 35, in
import tinycudann as tcnn
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\tinycudann_init.py", line 9, in
from tinycudann.modules import free_temporary_memory, NetworkWithInputEncoding, Network, Encoding
File "C:\Users\Pigiste1\miniconda\envs\nerfstudio\lib\site-packages\tinycudann\modules.py", line 19, in
raise EnvironmentError("Unknown compute capability. Ensure PyTorch with CUDA support is installed.")
OSError: Unknown compute capability. Ensure PyTorch with CUDA support is installed.

Going to close because this repo is for the nerfstudio-template, not the nerfstudio repo. Also questions like this are best answered in the discord. It looks like the pytorch installed in incorrect, it needs to be a CUDA version. Make sure you have a nvidia GPU, and search online for pytorch install guides with CUDA support.