Focus problem still occurs

Issue #25 still occurs.
When pressing "a" for going into details page, the focus is not on play button. You have to press up or down so you can press the play button. Also moving up from the description it loses focus again.

Can you send a video of this. I cannot reproduce it. Mine focuses on the play button and goes down smoothly and then back to the play button smoothly.

Sended a video on Discord PM

Fixed in v1.2.3


Add iOS native<->JS integration tests.

Does any other open PR do the same thing?
Not exactly, but there are some PRs & issues related to tests:
https://github.com/react-community/react-native-maps/pull/577
https://github.com/react-community/react-native-maps/pull/1170
https://github.com/react-community/react-native-maps/issues/1104
(These are mainly aimed at adding Appium integration testing.)
What issue is this PR fixing?

This PR adds iOS integration tests using RCTTest, the iOS native test framework built into React Native.
See the React Native docs for further information on how this is used in RN.
These tests are useful to verify the interface between native & JS code. They should help us avoid regressions, especially because changes have to work across Apple & Google Maps (& possibly others in future!).

Only one test is implemented, which is a currently failing test case for the issue fixed in https://github.com/react-community/react-native-maps/pull/2150. If that PR is merged before this one, the test should pass.

Documentation for how to run the tests & add a new test is in docs/testing.md.

Further work

Screenshot tests should be an extremely useful way to avoid regressions.
In theory these should work in the same way as other tests, but I have not tried this yet.

Some way of running the test components interactively in the simulator/on device, similarly to the example app (possibly even within the example app?).

Test cases! Only one test case is currently implemented as a proof of concept, and even this is incomplete.

A way of running the same tests on Android. Check out the RN docs if you'd like to tackle this.

How did you test this PR?
See the new documentation in docs/testing.md for information on how to run these tests & add new ones.

@rborn / @alvelig / other maintainers - would it be possible for you to please take a brief look at this & let me know if you agree with the general approach in this PR? Happy to make further changes if you'd like.
I would like to continue work on some other parts of the library (mainly marker performance/rendering issues), and ideally I would like to test further changes with a similar approach.
Really appreciate it, thanks guys!

@lachenmayer @alvelig I totally agree with tests the only "issue" I see is how we run this, we'd need a CI server/service that could integrate this as it's impractical for us to run tests on our local machines every time we have to merge a PR

@lachenmayer sure, sorry have been very busy lately. LGTM despite, I have not tested it yet. Do you want it to merge now or maybe develop further to see how screenshot tests can be implemented?

@alvelig Don't think I will get screenshot tests added this week - might be easier just to merge this & try it out on https://github.com/react-community/react-native-maps/pull/2150? Will take a brief look today, if it's easier than expected then I will update on here.
@rborn to be honest I have no idea how to run Apple stuff in CI - I think the RN project does have everything running in Travis, but that is probably going to be a lot of effort to set up too (if anyone reading this is a CI wizard, any help would be appreciated!). The situation right now is that contributors have to create entire repro repos - if you have the main repo checked out it really should not be that much effort to run the test suite with new changes checked out. I agree that it's not ideal but it's at least a step in the right direction. IMO the onus should be on the person who committed a change to also provide a passing test case - if it's not possible to run the test case when reviewing, you can just take it on faith that the provided test case passes.

Ok, so let's merge and create 2 issues: one about CI and the other about screenshot tests, just to separate and distribute tasks. What do you think?

Sounds good :)
I can update the PR template linking to the docs I've added here. Would be great if you could check these out in particular to see if they make sense (they're probably going to be the most visible long-term change effected by this PR!) https://github.com/lachenmayer/react-native-maps/blob/2cc937def02d8c2113c4f09ed725160f20e1319a/docs/tests.md
A similar test framework exists for Android: https://facebook.github.io/react-native/docs/testing.html#android
I unfortunately don't have a lot of experience with non-RN Android dev... Though it's very likely we'll port the current app I'm working on over to Android, so this may become relevant for me again in a couple of weeks/months time.
Re. an inventory of actual functionality: a lot of the current APIs are currently "Google Maps only" or "Google Maps iOS only", as it seems that the API was mirrored on the Apple Maps API (is that correct?). The biggest goal we should be striving towards in my opinion is to remove those Google-specific bits of functionality. Based on the "rule of 3", it might make sense to try to implement a further mapping API backend to discover a more or less "universal API". Whether that's worth it remains to be seen - currently I'm only interested in the Google Maps API, and a more fruitful way to avoid some of the API inconsistencies may even be to extract the Google Maps-specific stuff from this library.

An interesting comparison may be the https://github.com/mapbox/react-native-mapbox-gl API

@lachenmayer I'm not a CI wizard, but I can try to have a look at Travis and see if I can make it work.
This will take a while as I'm pretty busy right now. I'll also have to check if I have the right permissions (or beg for them😹)
@alvelig I agree with 2 separate threads - CI and tests and of course the roadmap
🤗

FYI @rborn just seeing that Fastlane are working on a mobile CI tool - might be a bit early days but looks like it could be really cool when it's ready :) https://github.com/fastlane/ci

@lachenmayer saw that too, didn't have time to look into yet though, I also saw this that might be used: https://github.com/invertase/bridge

Closing as being an old issue and not a clear reply. Thanks for all the effort 😻


Increase n_restarts_optimizer

Fixes https://github.com/scikit-optimize/scikit-optimize/issues/282

Current coverage is 85.45% (diff: 100%)

Merging #283 into master will not change coverage

@@             master       #283   diff @@
==========================================
  Files            25         25
  Lines          1375       1375
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1175       1175
  Misses          200        200
  Partials          0          0

Powered by Codecov. Last update 6a354cc...d7c1314

Thanks for this!


Change the interface of etcd-related class

What changes are proposed in this pull request?

Change the serialize/deserialize interface for future use(#17959)
Expose the TTL and timeout of the lease used in ServiceDiscoveryRecipe
Expose the path prefix of the ServiceDiscoveryRecipe for future use

Why are the changes needed?
etcd will be used in the near future for more areas than worker service discovery. so expose more information for future use.
Does this PR introduce any user facing changes?
nope

alluxio-bot, merge this please


Vetting and Discovery plugin documentation

Coverage remained the same at 72.051% when pulling a8bb7dc0b8e9305920820bf10c4d19b2061d3244 on plugin-docs into fe4c2bc2dd011bffab970bb258d430565e1229ba on develop.


Bubble sort in python3-medium issue

Pull Request Type
What kind of change does this PR introduce?
Solved an issue/task
What is the current behavior?
I made a code to perform bubble sort  for an array of integers in ascending order.
Issue Number: [Medium Issue (Python) #1523]
What is the new behavior?
I added a code to perform bubble sort for a given array of integers, previously the code wasn't there.
Other information
Output of my program:

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


BaseTypeFhirConverter Does Not Support Long Cql Types

isCqlType in BaseTypeFhirConverter does not check for Long:
if (value instanceof BigDecimal                 || value instanceof String                 || value instanceof Integer                 || value instanceof Boolean) {             return true;         }

Integer64 is only defined in FHIR >=R4B. We don't support R4B, but I'll fix it for the R5 converter.


Randomly High Frame Times

Issue details
I was making a game, utilizing a fixed timestep for the first time, when I noticed that when my player (a red rectangle) was moving, occasionally it would jump forward many extra pixels. Thinking it was the timestep, I tried many different things, but eventually found that for whatever reason Libgdx was just occasionally getting really high frame times, accompanied with FPS drop. As a test, I made a new blank Libgdx project with no tools checked and nothing but Desktop selected. This new project still had the occasional high frame times and FPS drops.
Reproduction steps/code
I've tested this on four different computers, all with the same results. This doesn't seem to be a universal problem (as many people have successfully developed with Libgdx), but I did find some threads (I would link, but I can't seem to find them right now) on the forums about what sounds like a similar issue, but they didn't come to a resolution. Below is a barebones version of the code I was using to see the problem. For my game I wanted vSync disabled and the framerate to be unlimited, but the problem occurs regardless of whether vSync is enabled or the framerate is limited. I've also included some logs of the output of the run of the below program. I've put the in delta time seconds, only so it's easier to read.
public class Barebones extends ApplicationAdapter {

	private float time;

    public void create () {

    }

    public void render () {
        Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);
        time = Gdx.graphics.getRawDeltaTime();
		System.out.print((time*1000)+", ");
		if((time*1000)>2f){
			System.out.print("High Frame Time");
		}
		System.out.println();
    }

    public static void main (String[] args) throws Exception {
    	LwjglApplicationConfiguration config = new LwjglApplicationConfiguration();
    	config.vSyncEnabled = false;
    	config.foregroundFPS = 0;
        new LwjglApplication(new Barebones(), config);
    }
}

Log1
Log2
Log3
The logs are quite large; I recommend just Ctrl+F and look for the word High. This will show the frame times that are significantly higher than the usual ones.
Version of LibGDX and/or relevant dependencies
Using Libgdx version 1.9.3.
Affected Platforms
I've only seen this behavior on Windows, but i haven't tried it on other platforms, beacuse what I was making was for the desktop only.

Duplicate of #3348


[HOLD for payment 2023-07-12] [$1000] Web - Send money - The tab with Bank account and Debit card is in the middle Cash page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to staging.new.expensify.com
Log in any account
Open any chat
Click on the + button in the compose box
Choose Send money
Enter amount
Click Pay with Expensify

Expected Result:
The tab should be at the bottom
Actual Result:
The tab with Bank account and Debit card is in the middle Cash page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/78819774/5ae33eea-986a-4fb0-a017-9dd855f4547a
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0164181e7781294f63
Upwork Job ID:<PHONE_NUMBER>250982912
Last Price Increase: 2023-06-27

Proposal
Please re-state the problem that we are trying to solve in this issue.
Send money - The popover with Bank account and Debit card is in the middle Cash page
What is the root cause of that problem?
Seems the anchorPositionVertical here assigned the wrong value here.
150
What changes do you think we should make in order to solve the problem?
We should take out the - 150 from the anchorPositionVertical or reduce it to - 20 which will reduce the distance from the top.
anchorPositionVertical: domRect.top, OR anchorPositionVertical: domRect.top - 20,

This is on my test list

I've requested a test account in betatify and will test soon

Assigning External, Tom helped me confirm that this is an issue:

Adding the Design label too for feedback to confirm this should be above the button -- thank you!

For reference, when you click the downcaret in the button for the settlement options menu it's here:

I think the menu should launch just right above the green button, like 8px above it or something.

Ok, I'll remove your assignment since we are set on the Design feedback.

@Santhosh-Sellavel - when you get a chance, can you review the proposal that was shared here:
https://github.com/Expensify/App/issues/21259#issuecomment-1601628639
Thank you!

Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - Send money - The tab with Bank account and Debit card is in the middle Cash page
What is the root cause of that problem?
When https://github.com/Expensify/App/commit/ac1a3efb803bd36b3d738e7994ec7fb0956eee61 was applied expected behavior changed, before it was anchorPositionTop and was was changed to anchorPositionVertical which resulted in different behavior since default anchorAlignment was bottom.
https://github.com/Expensify/App/blob/05f289b239eb98cabaad316bb19a816ec3468941/src/components/PopoverMenu/index.js#L35-L38
To sum up anchor position was in top of element before and after changes it was in bottom of element.
What changes do you think we should make in order to solve the problem?
We should rewrite computation of anchor position considiring above matter
https://github.com/Expensify/App/blob/ef52c5da96ceaaca8e023a6bc7459be967dd0d19/src/components/KYCWall/BaseKYCWall.js#L72-L73
anchorPositionVertical: domRect.top - 8,

What alternative solutions did you explore? (Optional)

@Pujan92's proposal looks good to me!
C+ Reviewed
🎀 👀 🎀

@alitoshmatov Thanks for the proposal, but the same has been proposed by @Pujan92 already.

Reassigning another bug team member, I'm going OOO until Monday, July 10, and will take it back then if it's not closed by then.
Required action from the 🐛 team: Check on the PR state and it might be ready for payment late next week.

@Santhosh-Sellavel @cristipaval  PR is ready for review!

Hello team,
I am interested if my bug report is eligible for bug report payment because I have reported this issue in 15th of June but the same issue was reported by internal team last week and I see that I reported it one week before internal team but the bug which I reported was considered as duplicate here. Please check it out and let me know, how the guidelines work for this condition, thank you!

Alright, removing the other 🐛 team member. I'm back online and see that this is our current state:
Prepare for payment

@Santhosh-Sellavel / @Pujan92 - to prepare for payment tomorrow, please apply for this job:
https://www.upwork.com/jobs/~0164181e7781294f63
Thank you!

Applied @alexpensify , Thanks!

@alexpensify I will collect via NewDot!

@Pujan92 - I've prepared the payment in Upwork.

@Pujan92 - I've prepared the payment in Upwork.

@alexpensify accepted, Thanks.

Alright, @Pujan92 has been paid via Upwork!

@Santhosh-Sellavel - can you please complete the check list and then I can close this GH. Thank you!
https://github.com/Expensify/App/issues/21259#issuecomment-1622147879

Could you please somebody answer my question here, https://github.com/Expensify/App/issues/21259#issuecomment-1615818004

@alexpensify I will complete it over the weekend, and collect my dues. Caught up with other Priority items. Thanks!

Could you please somebody answer my question here, #21259 (comment)

@alexpensify I think they are eligible for reporting bonus, please have a look and issue them thanks!

Thanks for flagging, I'm reviewing the timeline and will follow up tomorrow regarding the reporting bonus concerns.

@alexpensify  thank you

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/18692
[x]  [@Santhosh-Sellavel] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/18692/files#r1264102939
[x]  [@Santhosh-Sellavel] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No updated need, should have been caught during reviewer testing based on the checklist.
[x]  [@Santhosh-Sellavel] Determine if we should create a regression test for this bug. No need, applause had caught this, they might cases for this already!
[c]  [@Santhosh-Sellavel] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
[ ]  [@alexpensify / @lschurr] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

cc: @cristipaval Let me know if you differ on any of the above!

@dostongulmatov - I've started the process in Upwork for the payment since I see you did report this one. It might have gotten lost in the shuffle but please accept. After, I can complete the payment process. Thanks!

@alexpensify  thank you very much accepted the payment

Awesome, I've completed the payment process via Upwork!

Requested Payment on ND

Thank you for that update. I closed the job in Upwork and am going to close this GH. Great work team!

Approved $1500 (with bonus) for Santhosh


error：3840

rror.descriptionError Domain=NSCocoaErrorDomain Code=3840 "Unescaped control character around character 3342." UserInfo={NSDebugDescription=Unescaped control character around character 3342.}

_sharedClient.responseSerializer = [AFJSONResponseSerializer serializerWithReadingOptions:NSJSONReadingAllowFragments];
Can't work for me!
What's the solution?

For general help, please ask on StackOverflow.


Kong  disregards x-forwarded-proto and redirects to http

Summary
I made a request to a route connected to an upstream service and added a trailing slash. Kong returns a 301 moved permanently to the same uri without the slash, but the incorrect proto. I request https://domain.com/url/ and the location header was http://domain.com/url
My Kong is behind an aws classic load balancer which redirects https traffic to http and sets the x-forwarded-proto to https.
Steps To Reproduce

Set up a reverse proxy to an upstream service at http://domain.com/someurl
Put Kong behind an AWS classic load balancer.
Terminate the ssl with the load balancer and forward requests over http
make a request that forces kong to redirect (like adding a trailing slash)

Additional Details & Logs

Kong version 0.14.1

an additional note for the poor souls who are using chrome and receive "cancelled" on these requests and suddenly see another call to the return location using the incorrect proto - try firefox and see that Kong returns a 301.

It sounds like you might not be setting the trusted_ipsproperly in your Kong config. Would you mind pasting your config values here?

of course! [face palm] I know about trusted ips and x-forwared-*, I forgot
about setting trusted ips.
trusted_ips (Empty Object)
thanks, I'll close the issue.
On Tue, Nov 27, 2018 at 2:13 AM Robert<EMAIL_ADDRESS>wrote:

It sounds like you might not be setting the trusted_ipsproperly in your
Kong config. Would you mind pasting your config values here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kong/kong/issues/4021#issuecomment-441848810, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AdtdKG4n2WE2pWNxXi7oFija1bnw4Vdsks5uzIOPgaJpZM4YzjCF
.

trusted ips need to be configured for x-forwarded-* to take affect. https://docs.konghq.com/0.14.x/configuration/#trusted_ips


Vimux isn't working

I have already installed the vimux
Plug 'benmills/vimux' in .vimrc but it's not loading when i do
it says Unkown function: FunVimTmuxCommand

Hey @aruzmeister thanks for the issue! FunVimTmuxCommand isn't a command. Check out the docs to see the full list of commands[1]. I think you want VimuxRunCommand() if you're using a function or VimuxPromptCommand if you want to call it as a command.
In vim, if you type :Vimux<tab> you should be able to see the commands available. Or if you type :call Vimux<tab> you can see the functions available.
[1] https://github.com/benmills/vimux/blob/master/doc/vimux.txt#L63


Helm installation does not reflect helm's --namespace argument, but hardcodes kube-system (or rather hides it in the values.yaml)

Describe the bug
Normally one can install a helm release into a discrete namespace by using helm install --namespace foo ....
This does not work with the retina chart, as it puts the helm release into that namespace, but the resources into the kube-system namespace.
e.g. https://github.com/microsoft/retina/blob/main/deploy/legacy/manifests/controller/helm/retina/values.yaml#L47
If there is a technical reason for doing so, this should be documented. If not, this should be fixed to get the usual behaviour.
To Reproduce
Steps to reproduce the behavior:

Install using the following command:

helm upgrade --install retina oci://ghcr.io/microsoft/retina/charts/retina \
    --namespace retina \
    --create-namespace \
    --version $VERSION \
    --namespace kube-system \
    --set image.tag=$VERSION \
    --set operator.tag=$VERSION \
    --set logLevel=info \
    --set enabledPlugin_linux="\[dropreason\,packetforward\,linuxutil\,dns\]"

Issue helm ls -n retina and find the release there, but no pods or daemonsets (as kubectl get pod,ds -n retina shows)
Check for daemonsets in the kube-system namespace using kubectl get pod,ds -n kube-system
Voilá!

Expected behavior
The chart should respect helm's --namespace argument
Platform (please complete the following information):

OS: openSUSE Leap 15.6
Kubernetes Version: v1.30.4+k3s1
Host: self-hosted VM
Retina Version: 0.0.16

In addition, the operator daemonset always gets deploy to kube-system, even if its configMap is created in e.g. the retina namespace.
https://github.com/microsoft/retina/blob/main/deploy/legacy/manifests/controller/helm/retina/templates/operator.yaml#L6

@kastl-ars
Thank you for creating an issue. During my investigation, there's two things to mention:

The operator was always going to get deployed to kube-system. Now the daemonset can get deployed in any namepsace provided by the user.
The commands you provided needs to be updated. The --namespace option will get overrided if the namespace chart value exists (which in this case does) and that is why you'll never see it deployed elsewhere. You'll need to use the --set namespace=X option instead. I've tested this and it works!


Unable to connect using 0.11.2, while using 0.10.0 works fine.

I've been using 0.10.0 for a year - working quite well though I'd like to start using the features I'm seeing in 0.11.x.  I just upgraded...and broke!  After testing, it seems like it's not dependency related - I tried downgrading twisted, zope, pillow - that didn't fix it.  Using the current versions of the dependencies but 0.10.0 I'm able to connect and function again.
My test run:
(venv-vncdotool) root@daisy:/opt/venv-vncdotool# pip install -U vncdotool
Collecting vncdotool
Requirement already up-to-date: Pillow in ./lib/python2.7/site-packages (from vncdotool)
Requirement already up-to-date: Twisted in ./lib/python2.7/site-packages (from vncdotool)
Requirement already up-to-date: olefile in ./lib/python2.7/site-packages (from Pillow->vncdotool)
Requirement already up-to-date: Automat>=0.3.0 in ./lib/python2.7/site-packages (from Twisted->vncdotool)
Requirement already up-to-date: zope.interface>=3.6.0 in ./lib/python2.7/site-packages (from Twisted->vncdotool)
Requirement already up-to-date: constantly>=15.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool)
Requirement already up-to-date: hyperlink>=17.1.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool)
Requirement already up-to-date: incremental>=16.10.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool)
Requirement already up-to-date: six in ./lib/python2.7/site-packages (from Automat>=0.3.0->Twisted->vncdotool)
Requirement already up-to-date: attrs in ./lib/python2.7/site-packages (from Automat>=0.3.0->Twisted->vncdotool)
Requirement already up-to-date: setuptools in ./lib/python2.7/site-packages (from zope.interface>=3.6.0->Twisted->vncdotool)
Installing collected packages: vncdotool
Found existing installation: vncdotool 0.10.0
Uninstalling vncdotool-0.10.0:
Successfully uninstalled vncdotool-0.10.0
Successfully installed vncdotool-0.11.2
(venv-vncdotool) root@daisy:/opt/venv-vncdotool# vncdo -v -v --delay=500 -s xxx::xxx -p ppp key esc
INFO:root:connecting to xxx:xxx
INFO:twisted:Starting factory <vncdotool.command.VNCDoCLIFactory instance at 0x7f22db652d88>
INFO:twisted:Using protocol version 3.300
INFO:twisted:Cannot connect authentication failed
INFO:twisted:Stopping factory <vncdotool.command.VNCDoCLIFactory instance at 0x7f22db652d88>
INFO:twisted:Main loop terminated.
(venv-vncdotool) root@daisy:/opt/venv-vncdotool# pip install vncdotool==0.10.0
Collecting vncdotool==0.10.0
Requirement already satisfied: Pillow in ./lib/python2.7/site-packages (from vncdotool==0.10.0)
Requirement already satisfied: Twisted in ./lib/python2.7/site-packages (from vncdotool==0.10.0)
Requirement already satisfied: olefile in ./lib/python2.7/site-packages (from Pillow->vncdotool==0.10.0)
Requirement already satisfied: Automat>=0.3.0 in ./lib/python2.7/site-packages (from Twisted->vncdotool==0.10.0)
Requirement already satisfied: zope.interface>=3.6.0 in ./lib/python2.7/site-packages (from Twisted->vncdotool==0.10.0)
Requirement already satisfied: constantly>=15.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool==0.10.0)
Requirement already satisfied: hyperlink>=17.1.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool==0.10.0)
Requirement already satisfied: incremental>=16.10.1 in ./lib/python2.7/site-packages (from Twisted->vncdotool==0.10.0)
Requirement already satisfied: six in ./lib/python2.7/site-packages (from Automat>=0.3.0->Twisted->vncdotool==0.10.0)
Requirement already satisfied: attrs in ./lib/python2.7/site-packages (from Automat>=0.3.0->Twisted->vncdotool==0.10.0)
Requirement already satisfied: setuptools in ./lib/python2.7/site-packages (from zope.interface>=3.6.0->Twisted->vncdotool==0.10.0)
Installing collected packages: vncdotool
Found existing installation: vncdotool 0.11.2
Uninstalling vncdotool-0.11.2:
Successfully uninstalled vncdotool-0.11.2
Successfully installed vncdotool-0.10.0
(venv-vncdotool) root@daisy:/opt/venv-vncdotool# vncdo -v -v --delay=500 -s xxx::xxx -p ppp key esc
INFO:root:connecting to xxx:xxx
INFO:twisted:Starting factory <vncdotool.command.VNCDoCLIFactory instance at 0x7f5eefbd1680>
INFO:twisted:Using protocol version 3.300
INFO:root:connected to user's user desktop (server:3)
DEBUG:vncdotool.client:keyPress esc
DEBUG:vncdotool.client:keyDown esc
DEBUG:vncdotool.client:keyUp esc
INFO:twisted:Stopping factory <vncdotool.command.VNCDoCLIFactory instance at 0x7f5eefbd1680>
INFO:twisted:Main loop terminated.

I had issues with this as well... For me, I connect to local androids on wifi only for my farm. I ended up clearing the password (set to blank) and its happy now.

This could have been fixed by #105, would be appreciated if anyone can confirm if master is working for them.


x/build/cmd/racebuild: apt-get update problems on linux gomotes

What version of Go are you using (go version)?
Tip for Go, x/build

$ go version
go version devel go1.19-c847a2c9f0 Fri Jul 1 01:36:45 2022 +0000 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
linux/amd64
What did you do?
Ran "racebuild" with tip Go and a recent LLVM commit, e.g.
go build .
./racebuild   --goroot=/ssd2/ygo  --rev=b6374437af39af66896da74a1dc1b8a0ece26bee --gorev=3e97294663d978bf8abb7acec7cc615ef2f1ea75
870 Steel Stock Rd, Clarksville, Tennessee 37040, United States
What did you expect to see?
Successful run.
What did you see instead?
Many of the linux-line systems targeted by racebuild run "apt" commands to download things like git onto the gomote, so as to use git to download the LLVM repo.  These apt commands, e.g. things like this seem to be failing. Here is an example from a linux-arm64 gomote:
$ apt-get update
Get:1 http://security.debian.org/debian-security buster/updates InRelease [73.5 kB]
Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
Reading package lists...
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
$ echo $?
100
$

Not sure exactly what the issue is here, but it is impacting the ability to update race builders for most of the supported architectures (windows is not impacted, but lots of other os/arch combinations are).

@golang/release

The solution to this is updating our Debian builders more often. A quick fix may be to add the --allow-releaseinfo-change flag to the apt-get update command in racebuild.

We should consider updating to bullseye (current stable), which is supported by the Debian Security Team (rather than the LTS team) in #40561

I believe the builders in question have been updated to Debian Bullseye. Is there any additional work that needs to happen to close this issue?

No objections on my part.

Thanks @thanm. Apologies for this taking a bit longer than anticipated.


feat: Implement gene search functionality and gene information page (#11)

Issue: #11
Tasks:

[x] Implement home page with search bar
[x] Implement Gene Details Page
[x] Write tests

Some notes:

We ommit tests in docker builds : see .dockerignore
AnnonarsClient does not properly handles exceptions
SearchBar selection for genomeRelease is not tested
HomeView performSearch is not tested
GeneDetailView navigation bar redirections with # in url is not tested


"View dashboard" button is disabled

Two issues in the "Analyze audit logs and reports" section:

The first sentence is: "If you chose to write audit logs to Azure Monitor logs." It would be clearer if it used "Log Analytics Workspace" instead of "Azure Monitor logs" because that's the term used in the configuration section.
In the "If you chose to write audit logs to Azure Monitor logs" part, it says that the "View dashboard" button can be used but the button is disabled. Somewhere else I read that it might be disabled because database-level auditing is not enabled but the documentation doesn't mention that kind of limitation. It is also an odd requirement given that server-level auditing seems to be the recommended approach.

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

ID: 0c27fe13-a824-84a5-e314-892a27c1dec5
Version Independent ID: 510b5427-c927-84df-563f-31dfe13fc771
Content: Azure SQL Auditing for Azure SQL Database and Azure Synapse Analytics - Azure SQL Database
Content Source: articles/azure-sql/database/auditing-overview.md
Service: sql-database
Sub-service: security
GitHub Login: @Rupp29
Microsoft Alias: arupp

@kimjamia Thank you for the detailed feedback.
This is being assigned to the content author to evaluate and update the documentation as appropriate.

Thanks for the feedback.
For item #1, As you mention "Azure Monitor logs" is probably not the best term, I'm changing the document to say "Log Analytics". Thanks for this suggestion to clarify the content.
For item #2, the View Dashboard is enabled when you have a target of "Log Analytics" and/or "Event Hubs".
Having only blob storage as an audit log target shows the buttons as disabled.
In the documentation example, it shows Event Hubs as the option which will enable the View Dashboard button.
(this specific documentation does not cover all possible options)
Attached is a screenshot with buttons enabled where I have Log Analytics and/or Even Hubs as target storage.
When I flip the toggle to Server Audits, the View Dashboard is still enabled, but the Log Analytics is disabled, as I do not have a target of Log Analytics or Event Hubs for a server audit.
Server Level auditing may be the "recommendation", as having both Server and DB auditing creates duplicate data, but sometimes a user can configured a server audit to capture high level server events and a specific database audit is configured to capture something specific to that database using AuditActions or different PredicateExpressions. It all depends on the users requirements. In other words, it is possible to capture different events at the server level and different events at the database level where little or nothing is duplicated, but if you use default settings you get duplicate data (hence the recommendation).

Hi @kimjamia , thanks for contacting Microsoft! It seems your question has been addressed so I'm going to go ahead and close out this Git Issue. However, if you still need help, please let us know in the comments!
Thanks again for reaching out and hope you have a wonderful rest of your day :)
Masha from the SQL Docs team
#please-close

Thanks for the clarifications, @Rupp29, and sorry for not replying earlier.
I do have Log Analytics enabled on the server-level but the "View dashboard" button is still disabled. I don't have Event Hub or Storage Account logging enabled.

I'm unable to repo this behavior. In my SQL DB Auditing configuration, the View Dashboard is disabled unless I configure Log Analytics (at which time "View Dashboard" is enabled). The only way I can disable the "View Dashboard" button is if I also disable Database Auditing on the previous screen and then I have both button disabled:


Can't update group info as a non-host admin

Describe the bug, optionally with screenshots
I am an admin of a group but not its host. If I try to modify the group metadata, say "banner color," the button spins but never updates.

Dupe of #1386


Git Deployment of ASP.NET Core fails with 'error MSB1009: Project file does not exist'

We have been deploying through Continuous Integration to Azure App Services for quite a bit, today, our builds are broken due to a change on the dotnet CLI.
Right now we see on Kudu that the current CLI version is 1.0.0-preview3-004056. If the App is an ASPNETCore app (xproj / project.json) it's failing to find the project.
The App Service activity log shows:

Manually running dotnet build on Kudu console shows:

Repro repo available: https://github.com/ealsur/mvpstream

Can you try adding this global.json at the root of your project?
If you don't have it, then it uses whatever is the latest Core sdk on the box, which changes over time (we now have the new Preview3, which is incompatible).

Thanks David! I added the global.json to the repro repo and it worked.
On our production repo we never had a global.json file and has always been working, this might happen to other people if the CLI on Kudu is the one that's coming with the project.json > csproj migration (just a guess).

Well, the reason you never had problems is that there was no newer SDK. If you were to install the new Core sdk on your production repo, it would break as well.
Basically, not having global.json is analogous to depending on a Nuget package without specifying what version you want, and always getting the latest. It works until it stops working :)

Linking to forum thread with the same issue.
Also, pasting the actual error as text for SEO purpose:
MSBUILD : error MSB1009: Project file does not exist

So I already had a global.json file but it was targeting an older version of the SDK. I updated to the file linked to above and its still failing with the same erorr.

@leedjones can you share your Web App name, directly or indirectly? I'll take a look at what's going on.
The new tooling is csproj based, and incompatible with the xproj/package.json tooling. See here.

thanks @davidebbo - i've created a dummy site for you: http://dummy18112016.azurewebsites.net
Many thanks :)

You have two Web Apps there, each with a slot. Can you give an additional hint as to which one has the issue? Thanks!

Sorry, I should have added. Theyre all failing with the same error

Investigating...

@leedjones could you try something:

Go to Kudu Console
Go into D:\home\site\repository
Run git clean -dxf to clean the repo
Try deploying again

I'm still unclear what's going on, but I see another error in some of your logs:
error NU1001: The dependency Microsoft.EntityFrameworkCore.SQlite >= 1.0.0 could not be resolved.

Not sure if it's related, but I do know how to fix this one, which is a casing issue. I believe nuget made some recent changes that made it become case sensitive. In your project.json, please change (not the Sqlite casing):
"Microsoft.EntityFrameworkCore.SQlite": "1.0.0"

to
"Microsoft.EntityFrameworkCore.Sqlite": "1.0.0"

Tried the git clean on both apps via the Kudu console and tested a redeployment. Failed again with the same error.
I changed the SQLite casing (not sure how the casing got mixed up like that anyway?) but that too failed.
Out of interest, and just a guess, but, I have an application setting which tells Azure which project to deploy out of a multi project solution. So I have two projects in the same solution and deploy different projects in different web apps based on the app setting. This has worked fine until two days ago; has anything changed around that?

I wouldn't think anything changes, but let me dig into that.

I don't understand what changed, but I know how you can fix it. Instead of setting PROJECT, try setting:
SCM_BUILD_ARGS=--aspNetCore "FOO\src\FOO" --solutionFile FOO\FOO.sln

I replaced the name of your project by FOO here to not reveal it, so do change that.
Still trying to understand root issue, but prioritizing getting you unblocked for now.

Hmmm...I have absolutely no idea how or why that fixed it, but it did!!
Thanks for the help @davidebbo - much appreciated.
Should I leave that setting in permanently now or is it just a temporary fix while the old PROJECT setting is fixed?
Thanks again 👍

@leedjones , I took a quick look at your kudu, your global.json should be put under D:\home\site\repository the same place where you put .git

Indeed, what @watashiSHUN says is an alternative solution.
In addition to that, we will look into what it takes to make things work directly without you needing to move your global.json to the root (which is admittedly unnatural).
Reopening to track this.

@watashiSHUN I do have the global.json on the same repo directory still getting the issue. I have been deploying without .sln  until yesterday (  VSCode with Yo ).  This started today and and didn't make any difference even after I added a .sln file.

@shiranGinige can you share your Web App name, directly or indirectly? Thanks.

@davidebbo I created  to re-pro. However, got a different error this time.
remote: GETSDKTOOLINGINFO : error : The project is configured to use .NET Core SDK version 1.0.0-preview2-003133 which is not installed
or cannot be found under the path D:\Program Files (x86)\dotnet. These components are required to build and run this project. Download
the version of .NET Core SDK specified in global.json or update the SDK version in global.json to the version that is installed. [D:\h
ome\site\repository\MyProj.xproj]
Thanks!

@shiranGinige Is that the version you specified in global.json? Try 1.0.0-preview2-1-003177 instead, as in the example above in this thread.

@davidebbo  sorry should have mentioned that before. I did try that. The result was the same.

@shiranGinige Ok, I will look at your test site temp001 later today and try to figure out what's going on.

@shiranGinige
this is because the dotnet cli version you specified in global.json is not installed in azure, here is the list of available ones:

I changed version on https://temp001.azurewebsites.net to 1.0.0-preview2-1-003177 as mentioned by @davidebbo, and the command failed before is now running successfully:
"D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" "D:\home\site\repository\YOURSITE.sln" /nologo /verbosity:m /p:AutoParameterizationWebConfigConnectionStrings=false;Configuration=Release;UseSharedCompilation=false
you can verify the version and try to deploy again

Thanks @watashiSHUN. It's strange as @shiranGinige wrote

sorry should have mentioned that before. I did try that. The result was the same.

But it definitely should work with that version, and apparently it does. @shiranGinige can you try again?

Just tried it and worked! Turns out I'm not very good with version numbers! What I had tried was "version": "1.0.0-preview2-003137" not "version": "1.0.0-preview2-1-003137" . Thanks for your helps guys!

@shiranGinige Glad to hear!

@davidebbo I might have opened a bug at the wrong place (https://github.com/dotnet/cli/issues/4804), but this msbuild/dotnet building is a giant mess on Azure...
Running msbuild with the xproj does not do the same thing on Azure vs my computer. On Azure I get plenty of typescript errors, on my computer I see that "dotnet build path/to/folder" is being executed and it builds fine.
So I went in my deployment script then replaced msbuild with that dotnet command.
But then I started to get this error mentioned in this thread "Project file does not exist".
So I replaced the dotnet build path to
cd to/path
dotnet build

Then it started to work. Same thing with publish.

@jsgoupil I would think that instead of messing with the path, all you had to do is add a global.json as described here. It's the right thing to do to make sure you declare the sdk version that you need as part of your project.

Thanks @davidebbo. I have posted a blog post about all this stuff.
Deploying on Azure is messy with .net core http://blog.jsgoupil.com/deploying-net-core-on-azure-a-complete-mess/

So, being completely new to all of this, I've created a brand new web app from .net core using:
dotnet new -t web
This doesn't create any src or test folders, everything appears to be in the root folder.
Does that mean I leave out the projects key in the global.json?
Do I need to re-structure the project the template created?

@thetrav your question is probably outside the scope of this issue, which is specific to errors people are getting when git deploying their Core apps to Azure Web Apps.
Maybe start with dotnet core forum? https://forums.asp.net/1255.aspx

@davidebbo I am deploying my Core app to Azure Web Apps.
I listed the process I followed for creating the app so you could reproduce if necessary.
When I invoke git push azure master I get the same error reported in this issue:
MSBUILD : error MSB1009: Project file does not exist.

The suggested solution, global.json appears to require a specific project structure.
When I added the suggested global.json and invoked the same git push command, I received the same error.
Worth noting I've also got the output:
Lock file has not changed. Skipping lock file write. Path: D:\home\site\repository\project.lock.json

So it's possible that your build process isn't picking up the new file due to some optimisation

@thetrav please share a test repo and we'll try to figure out why your global.json is not getting picked up. Please make sure it's at the root of the repo.

@davidebbo
https://github.com/thetrav/dotnetcoretest

Your global.json has the sdk version as 1.1.0. No such version exists (sdk versions are not the same as framework versions). Please try with the exact global.json I pasted in my first reply above.

Yeah that works perfectly, no folder structure changes required.  Thanks for the help @davidebbo

Close this thread as the main issue of getting the correct version of dotnet cli is resolved, there's still some problems with finding the relevant global.json which is addressed by #2253

@watashiSHUN putting global.json where .git is solved my issue with this but how should i know this from the documentation, I was placing it where the .sln was, thanks though!

@dannythomas13 kudu runs build command at repository root (@davidebbo maybe we should put this sentence in the document)
your problem would be solved if dotnet cli knows which version to launch depending on the global.json in your project/solution directory and NOT THE CURRENT (repository root). This issue is already being tracked on github, and until then we probably don't want to hack it ourselves in kudu.

yup, working fine with the suggested global.json, thank you


[stencil] enforce linting

Description
Add and enfore linting rules in the apps bootstrapped using stencil.
Goals

[ ] eslint config
[ ] prettier config
[ ] rules to enfore them and docs on how to apply them in major text editors -- VSCode, JetBrains IDEs etc.

Implementational Details
Any popular TypeScript and JavaScript linter would be a good fit for the task, ESLint and Prettier are preferred.
Product Name
Stencil
Organisation Name
SamagraX
Tech Skills Needed
TypeScript
Mentors
@techsavvyash
Complexity
Low
Category
Code Formatting and Linting

do we need to add this in a github action?

No, we need to setup linting for the stencil project that will be generated

we just need to setup eslint ?

we just need to setup eslint ?

working on it

And prettier

will close it today

Great, looking forward to the PR

will close it by end of today

@techsavvyash how do i run this locally as in stencil setup docs it is refferencing to different repo

@techsavvyash how do i run this locally as in stencil setup docs it is refferencing to different repo

The steps remain the same, replace the repository URL with this one. Thanks for pointing out the inconsistencies in docs, will update that

Hi @techsavvyash is anyone still working on this if not can you assign it to me?

Hey @techsavvyash, @utnim2 was raised a pr, that was not closed till now, is there any issue with that pr, or if there is any issue with that pr, mention that, i will raise my pr

Hey @Sandeep0306
The current PR does not quite solve for this ticket. The crux is to have a consistent and enforced linter and formatter in every project bootstrapped using stencil. So, as a part of this ticket, you'd have to raise a PR in the SamagraX-stencil/stencil-cli editing the .eslintrc and .prettierrc files and adding precommit hooks to lint and format the files on commit/save. Another additional task would be to add a GitHub actions step for linting the codebase.
Feel free to go ahead and raise your PR, or to work collaboratively with @utnim2 in perfecting their PR.
You can always reach out in case you face some issues.

Hi @techsavvyash sir could you please confirm that do i need to update the .prettierrc file as based on this configuration, it looks like single quotes are enforced for string literals, and trailing commas are added to all elements in arrays and objects
{```
"singleQuote": true,
"trailingComma": "all"
}
also sir i am using husky for pre commit hooks am i working in the right direction

Hey @vsvishalsharma,
Yes you are in the right direction. Thanks for the PR, I have left a comment on your PR, it would be great if you could take that into account and raise the required PR as well, will merge both of them together and assign this one to you.


Master

Added a —hd option that outputs a higher resolution version of the picture.

Why not add an option to manually specify sizeScale?

thank you @nabijaczleweli for the suggestion. I just implemented it.

I hope to add this soon, been lazy

I am bad at merges, added this in 25f5c88dd84ce8b3405d306063c6fe46aa52a585 using --bricks


Fix typo and reuse predefined value

Fix typo: then => than
Use predefined variable to increase consistency.

Checklist

[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #

Relates to #

/skip-e2e

some checks didnt pass, but I don't think it's related with this change.
Please let me know, if something is missing :)

@JorTurFer @zroubalik I presume we can skip semgrep

it's not Semgrep, it's the e2e tests check. IDK why, even though we create it in other check, it randomly appears...

/skip-e2e

/skip-e2e


ext install: auto go away while focus out from one window to another

I think Ctrl+Shift+P dialog should persist until unless I select option by hit enter key or click on cross* icon or press Esc key to close this dialog.
Unfortunately when my mouse focus out from code window to other or click somewhere else. Package control dialog disappear and then need to start search again!.

Unfortunately, as designed, until we do a new UI for this. #448


Issue "UpdateRenderInfo" PluginEvent at EndOfFrame, rather than OnPre…

…Cull. This may fix some right-eye tearing issues.

Not ready to merge, but ready to test. Some users are seeing crashes, which can be traced back to Unity Rendering plugin. One symptom I've noticed is that RM renderInfo array suddenly appears to be empty instead of containing correct projection matrices and viewports. I'm wondering if there is a timing/threading issue that can be avoided by moving UpdateRenderInfo. I haven't seen any crashes for 3 days of normal use, and I would usually see this crash at least once or twice in that time. Other uses, particularly on AMD GPU setups, see a random crash much more often.
Hoping this fixes: https://github.com/OSVR/OSVR-Unity/issues/190

Here is a zipped folder with two executables: https://drive.google.com/open?id=0B0X-T5b2-zcOeHpRZFFpc3ZGeEE
ct_updaterenderinfo.exe is the build from this pull request. We hope it doesn't crash.
ct_master.exe is the build from this master. On my first test since opening this PR, ct_master.exe crashed after 24 minutes, with the error we are trying to fix. Crash logs included for reference, as well as the server config file I'm using with the latest x64 bit OSVR-Core snapshot.
I am running ct_updaternederinfo.exe now and will update later.

Still no crashes with ct_updaterenderinfo.exe, after a 15-minute test and a 1-hour test.

another hour of no crashes

a couple more hour-long tests without any crashes...

@jfrank-razer can anyone at Razer reproduce these tests? Important fix if it prevents random crashes. Hasn't crashed yet on two of my PCs, Win 10 GTX 980 and 1080, but other users' setups, especially those with AMD graphics, encounter this issue more often. Would love to get more feedback and merge this in if it works.

Finally saw the crash with these changes. Next test is swapping in Unity Rendering Plugin that uses the RenderManager C API, instead of the C++ API. Here is a 64bit osvrUnityRenderingPlugin.dll which can be used to test, just replace it in the Plugins folder: https://drive.google.com/file/d/0B0X-T5b2-zcOSmNaS09PQ2c1YkE/view?usp=sharing

Keeping this open for now, but the issue was probably solved by https://github.com/OSVR/OSVR-Unity-Rendering/pull/34. Will close this PR when I'm able to verify this.


Fix opening multiple files from the finder in the same window

Fixes #9574
Previously, we were storing the project directory paths as the initialPaths key in load settings, which were accessed in the browser process by reading the URL hash. However, this URL hash was not always available, subjecting us to timing issues when opening multiple files in the same folder in rapid succession.
We now store the project directory paths directly on AtomWindow instances on creation, then RPC changes from the render process to the browser process with a custom code path.
Shout out to :airplane::finnadie:’d @as-cii on this for pairing with me.
@izuzak @amytruong This changes browser process code on which test coverage is extremely thin. If you could help test different aspects of opening stuff with Atom once this lands on beta, that would be super helpful.

Thanks for jumping on this, @nathansobo and @as-cii.
As far as I can tell, this doesn't completely fix the problem for me. When I follow the steps shown in https://github.com/atom/atom/issues/9574#issuecomment-157411492, I get better behavior now, but still not expected.
In that GIF, I first open a single file from atom/atom, then three more. That cause four windows to be created -- one for the first file, and one for each of the three after that.
When I use a build of this PR, following the same steps causes two windows to be created -- one for the first file, and one for the three I open after that. The behavior I expected to see was that one window would be created in total -- after I open the first file, the same window would be used when I opened the other three (because they're from the same project/folder).
Do you see the same behavior? I this behavior by any chance expected?
I'm not sure if this is the same issue, but @benogle pointed out that https://github.com/atom/atom/issues/9526 seemed similar. Perhaps the problem pointed out in that issue is the missing piece to this?

@izuzak Thanks for finding that. Fixed. When this goes green I'm going to merge into beta.

@nathansobo I'm not sure if I'm missing something, but I can now reproduce the original problem (described in https://github.com/atom/atom/issues/9574) with multiple windows being opened, both on master and on beta.
Do you see the same behavior on master? I'm wondering if something got lost again like in that other PR. :confused:

@izuzak Yep. I just cherry picked it back in. I was merging with --strategy ours expecting the only conflict to be in the package.json for the version, which in retrospect was really really dumb. I combed through the last few merges to try to spot any other places I might have made a mistake, but I think this is the only one. My apologies. Coding at a conference isn't always the best idea.

:boom: Things are working now, @nathansobo -- thanks!


feat(invite-alert): OK button now mutes all open documents

When clicking the OK button in the alert window, it now sends a message over a broadcast channel to all listening documents. That way you confirm it on all open tabs / windows

Discussed elsewhere: this has a memory leak since the BroadcastChannel is never closed


Fill in README

Adds some install, usage, and development instructions to the README.
closes #28
TODO:

[ ] finalize production names for aleph & concat, do search & replace
[ ] roadmap / goals section
[ ] update install instruction after npm publish

Made some quick changes and broke stuff out into CONTRIBUTING.md, let me know what you think and we can merge

👍 looks good


File package was rebased making yocto builds fail

This looks like it took care of itself ten hours ago:
`commit e292e935b077a95ae093d4b425c7e95b177b030b
Author: Richard Purdie<EMAIL_ADDRESS>Date:   Tue Mar 21 22:17:57 2017 +0000
Revert "file: update SRCREV for 5.28 to fix fetch fail on missing commit"

This reverts commit 87c17b352daa63bc4f62e8802982288ab1839f1b.

Upstream restored the original hashes.

Signed-off-by: Richard Purdie<EMAIL_ADDRESS>


Invites backend

This pr adds the necessary model (the invite model) and the api calls to manage invites.
Invites are able to be:

created.
Viewed by booking that they were created for.
Viewed by the user that was invited
Rejected
Accepted (this creates a booking for the invited user)

Closes #209

Please note the interface to create a booking has been changed.
Instead of POST /:deskId/:userId and the times in the body, ALL 4 parameters are now expected to be in the body (as it should have been from the beginning, sorry!)
I.e. make a post request to /bookings with startsAt, endsAt, deskId and userId in the json body.


No source detected in ue4.26/ue4.27

Hi, this is some really amazing work. I am trying to read the Live Link data in UE but I dont see any source detected there. I used your PyLiveLinkFace lib to verify if any data was actually being sent and it is receiving the data from MeFaMo correctly. Do you have any idea what the issue might be? Thanks

solved.


Remove glTF loading from WMR package

XRTK - Mixed Reality Toolkit Pull Request
Overview
Remove glTF loading from WMR package
Supports: https://github.com/XRTK/XRTK-Core/pull/801
for glTF loading on WMR, a custom Visualizer would be needed to load the platform or custom glTF model

/azp run

Hmm, will look in to the bug raised by the build, but curious why is didn't show up in my local builds.

Let's open a new issue to recreate the glTF visualizer once the glTF package is published. We can go ahead and get this merged in and a release made for this change tho. Just needs the updated reference to the core preview package


ci: remove doker build

:white_check_mark: Build TheIdServer 4.4.1-ws-fed-metadata1-0055 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/3b48f366ed by @)


[Message] Create message object

Message object should be improved so that it makes more sense to the developers.
Also check webhooks MessageEventDTO

MessageDTO is not exposed to developers.
Message have received new properties to help developers.


Intel HAXM vs. Hyper-V - Which should

I am trying to setup hardware acceleration for my xamarin project using Visual Studio 2019. I am having an Intel CPU that would both support the HAXM and Hyper-V path. Now I am puzzled about this line within the documentation:

For the best experience on Windows, it is recommended that you use HAXM to accelerate the Android emulator.

Why does Microsoft vote for HAXM over there own Hyper-V? Which route should I take when having the choice and why? TIA

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

ID: 4e37d642-2051-8d70-9968-dfb484122a6a
Version Independent ID: 178ea80c-2b99-0c44-eeb6-9db319439b33
Content: Hardware Acceleration for Emulator Performance (Hyper-V & HAXM) - Xamarin
Content Source: docs/android/get-started/installation/android-emulator/hardware-acceleration.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @davidortinau
Microsoft Alias: daortin

@sp4rc We changed this guidance last year when there were a number of reliability issues with the Hyper-V powered emulator. Those are since resolved and I'll revert the guidance given it's the most compatible way forward.
Thank you for opening the issue!


Feature/#40 move to strongly typed

Coverage decreased (-0.5%) to 94.013% when pulling f2c7d4484c867315a4c509e5c8632eb59fb07a62 on feature/#40-move-to-strongly-typed into cd757887ed6dc303dff5c39668485498c9710093 on develop.

Coverage decreased (-0.5%) to 94.013% when pulling a4cac78657451e10aa783f520c1292d8cbaf0c27 on feature/#40-move-to-strongly-typed into cd757887ed6dc303dff5c39668485498c9710093 on develop.


Feature/layer norm after option tf

for BERT checkpt load, transform TF needs LN after
BERT is based on the original T2T architecture,
where the layer norms happen after the transformation.

This makes that optional, and also allows setting eps
in the layer norm to make sure that BERT checkpoints
can be loaded.

Also RA attention needs to be supported in decoders,
for some reason that never got added.

Closes #529


Document how bot icons work

Please document

where the bot icon comes from, for store, LOB and sideloaded apps.
how to update it
how long the existing bot icon is cached
Users and developers are confused about this, and we get bug reports that end up being customer error (which suggests we're doing something wrong, but let's start by documenting the current state).

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

ID: 3af8496d-46be-a691-11e1-16734f71f891
Version Independent ID: be0ff3e1-8bef-5ca7-8d9c-566e89e3fd41
Content: Bots in Microsoft Teams - Teams
Content Source: msteams-platform/bots/what-are-bots.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: anclear

We are looking into this and update the document accordingly.

@aosolis - Could you please confirm if the below changes look fine or do we need to add more information?
@surbhigupta12 -Could you please help us to update the document?
Please add the point after the GIF image in below document-
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/what-are-bots
If your app has a bot or message extension, your icons also will be included in your [Microsoft Azure Bot Service registration].(https://learn.microsoft.com/en-us/azure/bot-service/bot-service-manage-overview?view=azure-bot-service-4.0&tabs=userassigned#settings)

Hello @v-ypalikila - We are checking with engineering team for the above points and let you know, so that we can update the documentation accordingly.

Hello @surbhigupta12 - Please help to update the documentation like below:
1) Where the bot icon comes from, for store, LOB and sideloaded apps and how to update it =>
There are three ways by which we can add/update the bot icon and other bot related information:
A) From your bot settings in Azure
If you update your bot icon from the bot settings in Azure, this updates the conversation bot icon and the bot icon that displays when you send your new message from the Compose Area in Teams where you bot has installed.
This does not update the bot's 'profile' and/or app image. These must be updated from a new manifest.
B) Using app manifest used for loading a custom app.
C) Once you uploaded the app in Teams Admin Center, you can update the bot icon through the Teams admin center.
3) How long the existing bot icon is cached: We are not sure about this, Could you please provide your input for this? Also, could you please review above 2 points and share your thoughts?
2) How long the existing bot icon is cached => Bot Icon is cached until user signs out and sign in again.


Illuminate\Foundation\Testing\TestCase createApplication frequency

createApplication is called before every test (by virtue of it being called in setUp). This loads the Laravel environment multiple times per TestCase, which is over-kill.
I am developing a test-suite; in which test cases have 5 tests each. Each TestCase adds 17mb of memory usage to the overall memory usage, and I have a feeling it's because of the frequency of this method.

Anyone ever found a proper solution?

@LasseRafn we greatly sped up our process using this snippit:
    public function createApplication()
    {
        if (!isset(static::$application)) {
            static::$application = require __DIR__ . '/../bootstrap/app.php';
            static::$application->make(Kernel::class)->bootstrap();
            Hash::driver('bcrypt')->setRounds(4);
        }

        return static::$application;
    }

But the big down side is that this->mock() pollutes your IOC container between tests!
I just today found a solution: you can clone your $app class on each start of your test and set this as your $this->app. This both fixes your speed issues and your app container getting polluted :D

In your base testClass use the following:
    use CreatesApplication { createApplication as laravelCreateApplication; }
    public function createApplication(): Application
    {
        // skip recreating the application every time to reduce overhead.
        if (!isset(static::$application)) {
            static::$application = $this->laravelCreateApplication();
        }

        // we clone because it's the IOC container and $this->mock() would otherwise pollute it.
        $clonedApp = clone static::$application;
        $clonedApp::setInstance($clonedApp);
        return $clonedApp;
    }


Implement Score Tracking Feature

Add a score tracking feature to the Tic Tac Toe game that displays the numbers of win each player throughout the multiple rounds. The score should be resettable and visually integrated into the game's interface for a seamless user experience.
Please assign this task to me @iamparas0 .

@shrashti-19 You’ve got this, go for it!

hi i can solve the issue assign to me

the issue is already assigned to me.

I have done the required functionality and screenshots are also attached for your reference.
For pushing into feature-branch denied permission is coming.
Kindly check and let me know, if possible assist @Dharshini3011 @iamparas0

hi i can solve the issue assign to me

the issue is already done waiting to previewed by the team.

@iamparas0  why it is not showing in the leaderboard?


Is Scintilla_ahk2 also available in V2 code

It would be cool if I could use this highlighter for the V2 convertor, is this library also available in v2?

Sorry I missed this.  This lib is for v2.  I'll have to double check to make sure the example is still working.
Have you tried this in v2?

Great, it seems to be working well now.

Ah, I actually didn't change anything.  I only separated the example from the lib as lexikos suggested in another issue.
I did however add the Scintilla.dll file just for convenience, but I may remove it again in the future.  I mention this in the README, to download the scintilla DLL.
I'm guessing that may have been the "issue" you were dealing with when you opened this?  The DLL was meant to be downloaded separately at the time.  Either that or you downloaded a DLL that was updated and there were compatibility issues.
As it stands now this lib is out of date.  I plan to add new API stuff from the new Scintilla dll eventually.


⚠ Bofrost.be has degraded performance

In 038faf6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 4367 ms

Resolved: Bofrost.be performance has improved in 9768bae after 8 minutes.


[bug] MacOS: reported window size does not match created size

Describe the bug
When I create a window with a particular inner size (e.g. 400x300), and then ask the window for its inner_size, I get doubled dimensions (e.g. 800x600). It happens in both window Resize events and when just getting a handle to the event and calling inner_size() on it.
I suspect that the discrepancy has something to do with display scaling; perhaps the input size gets scaled up but the reported size is the raw number of displayed pixels. But I am only speculating. I did try changing the scaling factor on my display but it didn't seem to affect the doubling ratio.
In my application, the asymmetry between the input size and reported size breaks things, because I save the window sizes and relaunch the windows next time the app runs. The windows sizes escalate fast!
Reproduction
The easiest way to demonstrate this is to slightly modify one of the examples from this repository. Open parent-window/main.rs and change this line in create_child_window:
child.build().unwrap();

to
  let child_window = child.build().unwrap();
  println!("initial size: {:?}", child_window.inner_size())

Then run the example and click the button. The window is created with .inner_size(400.0, 300.0); but on my computer I get:
initial size: Ok(PhysicalSize { width: 800, height: 600 })

Play with the dimensions of creation to confirm it seems to always double
Expected behavior
No response
Platform and versions
(just run from inside the tauri source tree)
❯ cargo tauri info

Environment
  › OS: Mac OS 12.4.0 X64
  › Node.js: 18.6.0
  › npm: 8.13.2
  › pnpm: Not installed!
  › yarn: 1.22.17
  › rustup: 1.24.3
  › rustc: 1.62.0
  › cargo: 1.62.0
  › Rust toolchain: stable-aarch64-apple-darwin

Packages
WARNING: no lock files found, defaulting to npm
  › @tauri-apps/cli [NPM]: 1.0.0 (outdated, latest: 1.0.5)
  › @tauri-apps/api [NPM]: Not installed!
  › tauri [RUST]: no manifest (no lockfile),
  › tauri-build [RUST]: no manifest (no lockfile),
  › tao [RUST]: no manifest (no lockfile),
  › wry [RUST]: no manifest (no lockfile),

App
  › build-type: bundle
  › CSP: unset
  › distDir: {{ dist_dir }}
  › devPath: {{ dev_path }}

App directory structure
  ├─ .husky
  ├─ .docker
  ├─ tooling
  ├─ core
  ├─ audits
  ├─ target
  ├─ .changes
  ├─ .devcontainer
  ├─ .scripts
  ├─ examples
  ├─ .github
  ├─ .git
  └─ .vscode

Stack trace
No response
Additional context
I've only tested this on a mac.

This is actually the same as https://github.com/tauri-apps/tauri/issues/4931. Copying my explanation from there:

The reported values seem to be correct. Keep in mind that the struct they return is called PhysicalSize/Position, so they return the actual hardware specs. These structs do have a to_logical method if you prefer to work with these numbers; this method takes the scale_factor you mentioned as an argument.

Thanks @FabianLars! That's very helpful.
Do you think it would make more sense for it to be consistent? I.e. that if the creation API uses "logical" sizes, that the resize event should too? (Or vice versa?)

Hmm, honestly, i don't know 🤔 Apart from that we can't change it before v2/v3 anyway, it's tricky situation imo. Like in the window creation using logical sizes makes more sense and is "easier" to use/understand, and using physical sizes in the events makes it possible for us to basically just forward them as they are. It may also be a problem that we need the current monitor and its scale factor.
idk i just leave it to the others, tho i would just leave it as it is 🤷

@FabianLars
My use case is that I'm persisting the latest sizes of the windows so that when the app is relaunched, I can recreate those windows with those sizes. I'm happy to write the conversion code, but I suspect my use case case is common.

It may also be a problem that we need the current monitor and its scale factor.

If so, that creates the same problem in userspace; if it's not easy to get that info, then no one will know what to pass into to_logical()
So I think the ergonomics here could be improved. I'll post a proposal; perhaps we can create another event type?

but I suspect my use case case is common.

Yep it is, at least common enough to convince Lucas to create a plugin for it 😄https://github.com/tauri-apps/tauri-plugin-window-state

If so, that creates the same problem in userspace; if it's not easy to get that info, then no one will know what to pass into to_logical()

I think it's easier to get it on the application side than in tauri itself tbh, but that may be just me. But getting it being tricky inside tauri, or even tao, was what i had in mind when i said that.
Anyway, i may completely misremember&misjudge that part of the codebase.

perhaps we can create another event type?

What do you have in mind?

Lucas to create a plugin for it

I hadn't been aware of that, thanks. I haven't tried it, but skimming the code, I suspect it suffers from the same problem.

What do you have in mind?

Well this won't work if getting the scaling factor is difficult from inside Tauri, but I was thinking of just a ResizeLogical(LogicalSize) event that happens in addition to the regular one. Then we can just choose which one matters. But first I wanted to play with it to make sure I understand the one and puts (e.g. how you get the scaling factor)

I suspect it suffers from the same problem.

Nope, it shouldn't. It saves the events as they are (as physical), and the sets pos/size via the Physical enum variants: https://github.com/tauri-apps/tauri-plugin-window-state/blob/dev/src/lib.rs#L79-L86

(e.g. how you get the scaling factor)

Oh sorry i misunderstood stuff earlier and thought you know that already. All you need is access to the Window, in the context of the global window event handler you'd do let window = event.window();.
Then you get the window's current monitor like this: let monitor = window.current_monitor().unwrap().unwrap(); (double unwrap for simplicity) and get the scale factor via monitor.scale_factor();
A combined example would look something like this
tauri::Builder::default()
  .on_window_event(|event| match event.event() {
    tauri::WindowEvent::Resized(size) => {
      if let Some(monitor) = event.window().current_monitor().unwrap() {
        let logical = size.to_logical(monitor.scale_factor());
      }
    }
    _ => {}
  });

@FabianLars Ha, I should have come here first, hadn't seen your update. Yeah, I had assumed getting the scale factor was hard based on probably misinterpreting one of your comments earlier; when I sat down to do it was a line of code away.
I also found the Physical enum variant of set_size, which I suspect is the real answer to my question; I should just do that too!
At any rate, thanks for the help.


Material design charts are broken for some chart types

GoogleVisualr currently makes some incorrect assumptions about naming for the Google Chart API counterparts for various charts when using the {material: true} option.
For example, it assumes that the material counterpart to google.visualization.LineChart is google.charts.Line`.
This is correct for line and bar charts, but incorrect for area, map, and pie charts. There is no google.charts.Area, so if you pass in {material: true} the graph doesn't render and you get a JavaScript error.

Misread Google's documentation. Those types don't yet support the material flag anyway.


Support new float:round langlib function

Purpose
Fixes #35543

LGTM except for two loops written to get a numerical results. There are easy ways to get them without looping and added them as comments.

changed the logic please check


FR: Conditional config should accept traditional Windows path format

Is your feature request related to a problem? Please describe.
The following conditional config does not work on Windows
[[--scope]]
--when.repositories = ["C:/src/github.com"]
# also doesn't work:
#--when.repositories = ["C:\\src\\github.com"]

[--scope.user]
email =<EMAIL_ADDRESS>
Instead, the --when must use DOS device paths to work properly:
--when.repositories = ["\\\\?\\C:\\src\\github.com"]

Describe the solution you'd like
Traditional DOS paths should be recognized ("C:/src/github.com" or "C:\\src\\github.com").

Yeah, it's broader problem as we use .canonicalize() everywhere. I think most of them should be replaced with dunce::canonicalize() (or removed.)


:bug: FIX - Pet battle deployment definition

Pet battle deployment definition in the summary did not match with the previous code section, so the student could be missed about the right content to copy and review.

good catch @rmarting thank you!! 🚀


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit eaec1de:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit eaec1de:
:clock10: Full build: the average full build time is 5 min(s) 18 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit eaec1de:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Should lexeme turn tuple<char...> into string?

While I accept the rationale in https://github.com/tzlaine/parser/issues/54, I still expect that when I wrap a sequence of chars into a lexeme, I would get a string. Isn't "lexem" implying a one whole?
Feel free to close it, if you disagree with my reasoning. The following is an example demonstrating this.
#ifdef WITH_BOOST_SPIRIT
#include <boost/fusion/adapted/struct/adapt_struct.hpp>
#include <boost/spirit/include/qi.hpp>
namespace bp = boost::spirit::qi;
#else
#include <boost/parser/parser.hpp>
namespace bp = boost::parser;
#endif

int main()
{
#ifdef WITH_BOOST_SPIRIT
  auto alnum = bp::ascii::alnum;
  auto alpha = bp::alpha;
#else
  auto alnum = bp::ascii::alnum;
  auto alpha = bp::ascii::alpha;
#endif

  auto myParser = bp::lexeme[(bp::ascii::alnum | bp::char_('_')) >> bp::ascii::digit];

  std::string input = "m1";
  std::string result;

#ifdef WITH_BOOST_SPIRIT
  auto begin = input.begin();
  bool b = bp::phrase_parse(begin, input.end(), myParser, bp::ascii::space, result);
#else
  auto b = bp::parse(input, myParser, bp::ws, result);
#endif

  if (b)
    std::cout << ":-) " << result << std::endl;
  else
    std::cout << ":-(" << std::endl;
}

I think this is now superseded by #55.


GH-5: Q1 2022 dependency updates (resolves #5).

See #5 for details.

I ended up reverting husky to the 4.x version, as there are syntax changes and it doesn't introduce any vulnerabilities.

The initial commit message doesn't follow the usual guidelines because 7.x failed to run and I didn't notice it before pushing.

If someone can cut a dev release, happy to test these updates withfluid-lint-all.

It's been six months and now we have to test even more updates, notably newer versions of markdownlint change the behaviour of strong and strong emphasis.  I would suggest closing this one out and creating a new one.

Turns out they don't change it in a way that matters to the package itself, only how we use it downstream.  I'll leave it to the package maintainers to decide when an update is warranted.


Supports Dev Kit JS v3.7.0 to optimize tokenization flow

Proposed Changes
I split the property address generation and authentication completion into two promises.
Implementation
The return value of createAndAuthenticate function for the new Dev Kit is:
https://github.com/dev-protocol/dev-kit-js/blob/f66e71efb5ee745042ce32f4e420d650725fb042/lib/property-factory/createAndAuthenticate.ts#L18-L22
Resolve the promise as soon as the Property address is created. waitForAuthentication function returns a Promise that resolves when authentication is complete.
Reflecting these in the Hooks, I implemented as follows. Please refer to the comment out:
https://github.com/dev-protocol/stakes.social/blob/b15850fc28412baebe7d08a2995017bb41f6a588/packages/web/src/fixtures/_pages/Tokenization/AuthForm.tsx#L102-L123
I also wrote a dummy code to try authentication locally easily:
https://github.com/dev-protocol/stakes.social/blob/b15850fc28412baebe7d08a2995017bb41f6a588/packages/web/src/fixtures/dev-kit/client.ts#L135-L161

@aggre is there a loading boolean available so I can disable the tokenization button while creation/authentication are happening?


Run clang-format across the whole codebase

Fully automated with
find src include -name '*.cpp' -o -name '*.hpp' | xargs -n1 clang-format -i
clang-format -i main.cpp

Yeah, agreed. Let's try to automate as much as possible with CI/CD.
(It's pretty impressive how many things clang-format is capable of doing.)


Go-Live Vision

Currently, the UI is a bit too convoluted to be easily usable, and there is no processing algorithm provided.
The road map would be as followed:

Create processing algorithm from current UI, supporting (all) the parameters (AUG)
thin the UI based on ohsome dashboard (SEP)
evaluate whether thinned UI is useful for QGIS users
test
adapt metadata and go live (OKT)

Updated course of action:

fix issues in #60
fix issues in #59
Release as "experimental" so people can easily install it. Only publish this inside of HeiGIT and have the people testing.
Implement feedback
Release


feat: add unit tests for components using AI tools

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ani Sarkisyan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


I am curious about the communication score and have a question.

Hi, thanks for developing such a great tool.
I am using your tool to analyze two conditions (ex Case vs Control).
The ultimate goal I am trying to find using your tool is a metabolite interaction that is upregulated or downregulated in Case vs Control (like DEG).
So I did a comparative analysis the way you answered a question someone posted before and I have a question for you here.
** (The comparative analysis method I referenced): https://github.com/zhengrongbin/MEBOCOST/issues/3
Q. If the interaction score for a particular metabolite pair is 3.4 (Comm_score) in Bcell~case to Bcell~case and -1.2 (Comm_score) in Bcell~control to Bcell~control, can we interpret that the autocrine interaction is upregulated in Bcell~case relative to Control ?
Thanks.

Hi, Yes, I think you can understand in that way, as long as your data was processed and normalized together, and communication score was significant at least in one of the conditions.Best Regards!Rongbin ZhengOn Apr 27, 2023, at 2:34 AM, mybioinformatics @.***> wrote:
Hi, thanks for developing such a great tool.
I am using your tool to analyze two conditions (ex Case vs Control).
The ultimate goal I am trying to find using your tool is a metabolite interaction that is upregulated or downregulated in Case vs Control (like DEG).
So I did a comparative analysis the way you answered a question someone posted before and I have a question for you here.
** (The comparative analysis method I referenced): #3
Q. If the interaction score for a particular metabolite pair is 3.4 (Comm_score) in Bcellcase to Bcellcase and -1.2 (Comm_score) in Bcellcontrol to Bcellcontrol, can we interpret that the autocrine interaction is upregulated in Bcell~case relative to Control ?
Thanks.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thanks for the quick reply :)
If you can develop a function to do differential tests in the future, I think people will be more interested and use it more.
I hope your tool gets published in a good journal !!!

Thank you for the comment! We understand the importance of performing a comparison analysis between conditions, and we are definitely on the way to upgrading.


Not playing nice with router.extendRoutes

Some projects will fetch data from an external source and use router.extendRoutes to create pages based on the source's response contents. In my case I fetch the data from Sanity and, given a _type and slug, I'll generate a page using one of my ignored page components.
Before adding @nuxtjs/i18n to my project, I was able to pass an array of route objects and Nuxt was using to create the pages I wanted. With this module enabled, Nuxt will try to render all of those pages for each of the available locales.
This is what doesn't work as expected (plus I couldn't find any examples of using the module like this). I have a PR ready for review (#1281) that is solving this issue on my local env. Since I'm not familiar with the codebase and all the ins and outs of the module I'm opening this issue first.
Version
@nuxtjs/i18n: v7.0.3
nuxt: v2.15.8
Nuxt configuration

[x] Applies to a site deployed to a static server (site generated with nuxt generate)
[ ] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration
// nuxt.config.js

const mapPages = ([key, { component, result }]) => ([key, { component: join(__dirname, component), result }])
const pages = { // on my codebase this is a groq query to Sanity
  "legal": {
    "component": "./pages/-legal.vue",
    "result": [
      {
        "_id": "unique-id-value-for-the-document",
        "lang": "en",
        "slug": "cookies-policy"
      },
      {
        "_id": "i18n.unique-id-value-for-the-document.es",
        "lang": "es",
        "slug": "politica-cookies"
      }
    ]
  }
}

const dynamicPages = Object.fromEntries(Object.entries(pages).map(mapPages))

export default {
  buildModules: [
    ['@nuxtjs/i18n', {
      locales: ['en', 'es'],
      defaultLocale: 'en',
      detectBrowserLanguage: false,
      vueI18n: {
        fallbackLocale: 'en',
        messages: {
          en: { welcome: 'Welcome' },
          es: { welcome: 'Bienvenido' },
        },
      },
    }],
  ],

  router: {
    extendRoutes (routes) {
      const buildRoutes = ([key, { result, component }]) => result.map(({ lang, slug, _id }) => {
        const name = _id.includes('i18n.') ? result.find((i) => i._id === _id.split('.')[1]).slug : slug
        const route = _id.includes('i18n.') ? `/${lang}/${slug}` : `/${slug}`
        return { name: `${name}___${lang}`, path: route, component, chunkName: `pages/${key}`, url: route }
      })

      return sortRoutes([
        ...routes,
        ...Object.entries(dynamicPages).map(buildRoutes).flat(),
      ])
    },
  },
}

Dont' mind the unnecessary Object.entries(Object.fromEntries()), my config is split in two parts and one of them is shared accross different projects and I just copy/pasted the relevant parts for the issue.

Reproduction Link
https://codesandbox.io/s/test-nuxt-i18n-forked-2us3p
Steps to reproduce

Open the reproduction link
Open the browser URL from CodeSandbox on a new tab
Open the routes section inside vue-devtools, you should se something like this:

What is Expected?
I expect @nuxtjs/i18n to either:

allow me to pass an array of valid routes without messing with them
handle everything automagically for me (this might be hard to implement and would require users to provide those routes with everything the module could need to make it work)

What is actually happening?
The module is assuming each of those routes needs their localized counter parts and pushing them to the router. This breaks the theme-switcher functionality and pushes non-existent pages to the router, resulting in one build error for each of those.
It also prefixes the paths with each locale, resulting in some cases in a duplicated locale. Looks like this only happens because the module doesn't expect someone to provide custom routes.

 The approach shown on the config section of this issue is what made the most sense to me since it consist of manually writing the same route Nuxt and the module would generate for me.

Without investigating too much, maybe it would work for you to set the pages option (https://i18n.nuxtjs.org/options-reference#pages) based on the API response instead?

Without investigating too much, maybe it would work for you to set the pages option (i18n.nuxtjs.org/options-reference#pages) based on the API response instead?

Yeah, that's what I'm using for most pages. I forgot to add some details to justify my setup.
I'm using ignored pages (four different kinds) to generate pages at the root level. They're landings the marketing team uses to onboard new users and I have no way to know where they'll go except at build time when I fetch them from the CMS.
Let me know if this makes it clearer or you have any more questions. I can provide more details if that's the case 👍

not stale

Same issue here, we are using _.vue to fetch pages from an API based on the page path. Together with the prefix_and_default strategy and without default locale, the route to _.vue is gone. Manually defining that route via extendRoutes isn't working.

is there any progress on this issue?

Same issue here, we are using _.vue to fetch pages from an API based on the page path. Together with the prefix_and_default strategy and without a default locale, the route to _.vue is gone. Manually defining that route via extendRoutes isn't working.

+1

Same issue

try to use hooks like so:
 hooks: {
    "build:extendRoutes": (routes, resolve) => {
      routes.push({
        name: "RouterName",
        path: "/path",
        component: resolve(__dirname, "components/components.vue")
      });
    }
  },

Closing this as v7 is not being actively worked on (critical hotfixes only), if this still applies to v8 and later please open a new issue!


Check scipy version for PixelThreshold attack

Signed-off-by: Beat Buesser<EMAIL_ADDRESS>Description
This pull request adds a check for the version of scipy in PixelThreshold attacks to add support for scipt>=1.8.
Fixes #1568
Type of change
Please check all relevant options.

[x] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Codecov Report

Merging #1589 (00a8e5e) into dev_1.10.0 (bdab55a) will decrease coverage by 17.16%.
The diff coverage is 60.00%.

@@               Coverage Diff               @@
##           dev_1.10.0    #1589       +/-   ##
===============================================
- Coverage       88.75%   71.58%   -17.17%
===============================================
  Files             250      250
  Lines           20694    20698        +4
  Branches         3689     3690        +1
===============================================
- Hits            18366    14817     -3549
- Misses           1424     4996     +3572
+ Partials          904      885       -19

Impacted Files
Coverage Δ

art/attacks/evasion/pixel_threshold.py
18.84% <60.00%> (-72.30%)
:arrow_down:

art/estimators/object_detection/utils.py
0.00% <0.00%> (-100.00%)
:arrow_down:

art/attacks/evasion/shapeshifter.py
5.89% <0.00%> (-93.30%)
:arrow_down:

art/attacks/evasion/pe_malware_attack.py
14.28% <0.00%> (-84.80%)
:arrow_down:

art/attacks/evasion/wasserstein.py
11.94% <0.00%> (-83.28%)
:arrow_down:

art/attacks/evasion/dpatch.py
12.96% <0.00%> (-78.40%)
:arrow_down:

art/attacks/evasion/boundary.py
14.45% <0.00%> (-78.32%)
:arrow_down:

...attacks/evasion/geometric_decision_based_attack.py
13.65% <0.00%> (-77.57%)
:arrow_down:

art/attacks/evasion/saliency_map.py
22.89% <0.00%> (-77.11%)
:arrow_down:

...imators/object_detection/tensorflow_faster_rcnn.py
18.82% <0.00%> (-75.89%)
:arrow_down:

... and 59 more