Debugging hotkeys enabled all the time

Current, if the cursor is with the REPL window, one has to manually click the Juno editor using the mouse or the touchpad to return to the editor and hence be able to command the debugger through the hotkeys again. This significantly drags the speed of debugging work.
It'll be vastly beneficial to have the hotkeys, e.g. F10 and F11, still enabled when the cursor is at the REPL. This can bring uninterrupted and seamless debugging experience.

Now we can set those keybindings within REPL with whitelistedKeybindings config and the custom keymaps.


Inquery about how to refine on higher resolution.

Firstly, Thank you for your outstanding work. I benefit a lot.
I have some issues with the strategy of refining on higher resolution.
It is firstly trained on the lower resolution and obtains a pre-trained model. Is it then using the pre-trained model as the initial weight to predict the residual on higher resolution? (I mean trained again and again, from 1/8 scale to 1/4 scale to 1/2 scale then to full scale).
Does it mean that if I want to refine fully, I must refine 3 times (train extra 3 times)for refining at the highest resolution?
Looking forward to your reply.

Hi @Magicboomliu , thank you for your kind words!
The model with refinement (1/8 & 1/4) in our paper can be trained from random initialization, without requiring to train the 1/8 model first, as shown in our training scripts: https://github.com/haofeixu/gmflow/blob/main/scripts/train_gmflow_with_refine.sh
Thanks.


updated base image, packages and default sample app name

[x] update base image
[x] bumps node and npm packages
[x] cleansup sample app for integraiton tests
[x] sets default node count to 1 to ensure lowest greenfield cost

This PR is currently blocked. Something seems like it has changed upstream (with jsii maybe) and now cdk is taking 5x more memory to synth which often leads to a JS out of heap issue. Going to see if I can find a temp solution before CDK 2.

Unblocked this PR by upgrading to CDK2.


All-in-one template

Do not merge yet!
Tests are using fabric8-arquillian with google cloud engine. Template is created in a separate namespace which is removed after test execution.
Encrypted variables are not exposed to PRs from forked repositories https://docs.travis-ci.com/user/pull-requests#Pull-Requests-and-Security-Restrictions

@jpkrohling @objectiser could you please review? This has a downside that travis runs only on branches in this repo, due to security reasons.
@yurishkuro would it be possible to use jaegertracing google account for gcloud (more described in the email I sent)?

@pavolloffay Do you mean we just created that account and share pwd?

Probably yes, or create a separate account for it? We just have to enable google cloud engine for it and generate API key to be used here.

Just wondering whether it is worth using gcloud when only useful for all-in-one.
Ideally we need a solution for production templates and also for openshift.

Just wondering whether it is worth using gcloud when only useful for all-in-one.

Why do you make this assumption?

Might be good to try hawkular first just to get an idea.

Update: I wasn't able to run C* on f1-micro cluster on gcloud :-1:. We have two options test PRs locally with minikube as an intermediate solution and ask QE to setup environment with minikube where this can be tested.
This is not working locally with minikube (services are not exposed as in standard cluster). I'm porting it to http://arquillian.org/arquillian-cube/ which seems to work fine.
The goal of tests is to verify if deployment is successful and if templates are valid. I don't think we should write here end-to-end tests, this should be handled in a different layer (down e.g. crossdock).
I think readiness probes should do the job and verify if the app is UP and running correctly. @jpkrohling might have more experience with this.

@pavolloffay The goal of the tests should be to make sure the template has worked successful. For all-in-one it may not be such an issue, but when the components are deployed separate in the template, doing an end-to-end test will confirm that the components have been successfully started and are communicating correctly with each other. So may be not so relevant in this case, but when we have the production template I think it would be good to have.

The readiness probe will just check whether it's all ready to receive requests, not that it's working (in the business sense). I'm actually OK in using the readiness checks for this purpose here, but I would prefer to have a small set of smoke tests that can be reused.

Updated code is there. I have tested it against minikube and gcloud, all worked well. This should work with any k8s cluster (when kubectl can successfully connect).
Things to consider:

file structure: do we want to have a directory for each template (each dir is also maven module with tests), or move tests to a different substructure. Templates are always in root dir not in maven's resources.

Maybe having tests separated would be better, so can be used against either template. So I'd be ok with templates at the top level and separate tests - do you have specific pros/cons?

I think that tests for each template can differ a little bit. But I agree that having a shared artifact with tests is beneficial.

@objectiser so you are proposing:

root with all templates
root/tests-parent/all-in-one/
root/tests-parent/common // with shared tests probably deployed in maven (to be reused in oc templates)e.g. create span and verify.

I maybe like more:

directory per template + one directory with shared tests

I think it's cleaner to keep tests with templates, easier to navigate and see what is using what.
cc @jpkrohling ?

Have no strong preference, so +1

Don't forget to add the apache headers with copyright "Jaeger Authors"

PR updated, test it locally, please.

@pavolloffay Test ran ok, and was able manually start minikube and deploy template.
Just wanted to check - I was able to launch the Jaeger UI using minikube service jaeger-all-in-one - but when I tried to find an external IP, it showed them as 'pending':

[gbrown@localhost jaeger-kubernetes]$ kubectl get services
NAME                      CLUSTER-IP   EXTERNAL-IP   PORT(S)                                        AGE
jaeger-all-in-one         <IP_ADDRESS>   <pending>     80:32719/TCP                                   2m
jaeger-all-in-one-agent   <IP_ADDRESS>    <pending>     5775:32474/UDP,6831:31330/UDP,6832:30622/UDP   2m
kubernetes                <IP_ADDRESS>     <none>        443/TCP                                        9h

Does something else need to be defined in the template to expose the ports?

Just wanted to check - I was able to launch the Jaeger UI using minikube service jaeger-all-in-one - but when I tried to find an external IP, it showed them as 'pending':

providing an external address is a feature of the cloud provider, and minikube does not support it properly

Just want to pitch in about testing - I agree that there should be done simple e2e smoke test, not just a health ping. We have an e2e test for all in one image, but the test itself is not specific to all in one, we can reuse it. Let's have an issue in the main repo about what needs to be changed in that test to work for both.

+1 I would like to use the same tests for k8s and oc.
If you agree let's not block this and iterate on tests in next PR/s.

@yurishkuro are those tests written in Java? I could you point me to the code?

No, it's in Go https://github.com/uber/jaeger/blob/master/crossdock/main.go

I'm not sure if we can reuse them if we are going to use arquillian-cube. IIRC it does some magic to connect to the not exposed services in the cluster.
The code does not look difficult to re-implement in java, but it is ugly to repeat it.


DOC: <Issue related to /v0.2/docs/how_to/tools_prompting/> fix import in example code

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
The first code block on https://python.langchain.com/v0.2/docs/how_to/tools_prompting/#creating-our-prompt has
from langchain.tools.render import render_text_description
this did not work for me, I got an error that I didn't have the module "langchain". I fixed it by changing that line to
from langchain_core.tools import render_text_description
instead.
Idea or request for content:
Change from langchain.tools.render import render_text_description to from langchain_core.tools import render_text_description on https://python.langchain.com/v0.2/docs/how_to/tools_prompting/#creating-our-prompt

https://github.com/langchain-ai/langchain/blob/master/docs/docs/how_to/tools_prompting.ipynb?short_path=f4ea763#L165

thank you for flagging and fixing @maccam912!


Update Atlantic salmon variant examples (e107)

Salmo salar variant examples are not correct for the newest Ssal_v3.1 assembly. This PR replaces those examples with correct ones.
Please test this using my web sandbox.

Hey @msmanoj, could you please merge this PR whenever possible? Thanks in advance! 😊


Interceptor API policy and generic util to combine overrides and defaults

Purpose
$subject

Codecov Report
Patch and project coverage have no change.

Comparison is base (1c0c4b7) 79.22% compared to head (880dc4e) 79.22%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #907   +/-   ##
=======================================
  Coverage   79.22%   79.22%
=======================================
  Files          11       11
  Lines         592      592
  Branches      257      257
=======================================
  Hits          469      469
  Misses        123      123

Flag
Coverage Δ

devportal-domain-service
?

idp-domain-service
79.22% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add bindists for FreeBSD 11 and 12.

These bindists are create from lang/ghc port of FreeBSD Ports tree and contain various FreeBSD-specific patches. This commit also introduces bindists compatible with FreeBSD 12+, following this PR: https://github.com/commercialhaskell/stack/pull/4359

This also should fix https://github.com/commercialhaskell/stack/issues/3515

Awesome, thanks!


Fixes a typo in Eady example

What does non-linearized around a geostrophic flow mean (line 64)?
Perhaps better assumes a geostrophic base flow...?

The typo fix is good of course, but the fixes to commenting style will not produce the intended result when this example is compiled to markdown using Literate; I don’t think we want two extra primary headers.
To nonlinearize around something is similar to linearizing around something, except keeping the nonlinear terms! But @navidcy’s suggestion could be more clear and usual semantics.

Oh, I thought that missing spaces was a typo in the comments...
I sort of got what nonlinearize meant but I have to admit that I have never seen the terminology anywhere. It's not a good idea to invent new terminology in an example .jl file... some people will be confused with it I'm sure.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #527   +/-   ##
======================================
  Coverage    62.6%   62.6%
======================================
  Files          70      70
  Lines        2054    2054
======================================
  Hits         1286    1286
  Misses        768     768

Continue to review full report at Codecov.

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


Performance Monitoring Sample is not Compiling

"Downloads/GoogleApisForiOSComponents-master-2/Firebase.Core/source/Firebase.Core/CSC: Error CS1566: Error reading resource 'GoogleToolboxForMac' -- 'Could not find file "Downloads/GoogleApisForiOSComponents-master-2/Firebase.Core/externals/GoogleToolboxForMac"' (CS1566) (Firebase.Core)
Also GTMSessionFetcher, leveldb-library, nanopb, Protobuf is missing,

Hi @rkszone! To make the sample work, you will need to run the sh ../build.sh -t externals command inside of the component's folder as stated in docs. For example:
cd ./Firebase.PerformanceMonitoring
sh ../build.sh -t externals

After this, you will be able to run the sample.
If you have any doubt, don't hesitate to ask.
Best!
Israel Soto.

Hi Team,
This Performance Monitoring is Updated to version <IP_ADDRESS>,  But on Nuget its showing <IP_ADDRESS>, I tried to compile and use dll of this "Performance Monitoring" project in my App project.  But is showing below error. not able to understand what i'm doing wrong, is version <IP_ADDRESS> available on nuget.
clang: Error: linker command failed with exit code 1 (use -v to see invocation) (App.iOS)
Error MT5211: Native linking failed, undefined Objective-C class: FIRHTTPMetric. The symbol 'OBJC_CLASS$_FIRHTTPMetric' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (App.iOS)
Error MT5211: Native linking failed, undefined Objective-C class: FIRPerformance. The symbol 'OBJC_CLASS$_FIRPerformance' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (App.iOS)
MTOUCH: Error MT5211: Native linking failed, undefined Objective-C class: FIRTrace. The symbol 'OBJC_CLASS$_FIRTrace' could not be found in any of the libraries or frameworks linked with your application. (MT5211) (App.iOS)
Error MT5202: Native linking failed. Please review the build log. (MT5202) (App.iOS)


abc fails to compile on arm64 with conda clang

Version

On which OS did this happen?
macOS
Reproduction Steps
Attempt to build Clang in Conda on Mac for arm64
Expected Behavior
yosys should build
Actual Behavior
Aside from a litany of warnings about the use of sprintf, compilation appears to fail due to these calls:
src/base/acb/acbTest.c:424:31: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'int' in initializer list [-Wc++11-narrowing]
            int pLitsF[2] = { Gia_ManCo(pOne, i)->Value, Gia_ManCo(pOne, i+1)->Value };
                              ^~~~~~~~~~~~~~~~~~~~~~~~~
src/base/acb/acbTest.c:424:31: note: insert an explicit cast to silence this issue
            int pLitsF[2] = { Gia_ManCo(pOne, i)->Value, Gia_ManCo(pOne, i+1)->Value };
                              ^~~~~~~~~~~~~~~~~~~~~~~~~
                              static_cast<int>(        )
src/base/acb/acbTest.c:424:58: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'int' in initializer list [-Wc++11-narrowing]
            int pLitsF[2] = { Gia_ManCo(pOne, i)->Value, Gia_ManCo(pOne, i+1)->Value };
                                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
src/base/acb/acbTest.c:424:58: note: insert an explicit cast to silence this issue
            int pLitsF[2] = { Gia_ManCo(pOne, i)->Value, Gia_ManCo(pOne, i+1)->Value };
                                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                         static_cast<int>(          )
src/base/acb/acbTest.c:425:31: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'int' in initializer list [-Wc++11-narrowing]
            int pLitsS[2] = { Gia_ManCo(pTwo, i)->Value, Gia_ManCo(pTwo, i+1)->Value };
                              ^~~~~~~~~~~~~~~~~~~~~~~~~
src/base/acb/acbTest.c:425:31: note: insert an explicit cast to silence this issue
            int pLitsS[2] = { Gia_ManCo(pTwo, i)->Value, Gia_ManCo(pTwo, i+1)->Value };
                              ^~~~~~~~~~~~~~~~~~~~~~~~~
                              static_cast<int>(        )

This appears to be caused by abc making use of casts between unsigned and int. The Apple clang compiler appears to be okay with this, as are most other paltforms. However, for some reason the conda version of clang doesn't like it.
I've opened this issue in case there is something I'm doing wrong here, but adding casts around it has solved the problem.

This is on macos using the Conda build of clang:
[  5%] ABC: Using CC=arm64-apple-darwin20.0.0-clang
[  5%] ABC: Using CXX=arm64-apple-darwin20.0.0-clang
[  5%] ABC: Using AR=ar
[  5%] ABC: Using LD=arm64-apple-darwin20.0.0-clang

which identifies itself as clang:
$ arm64-apple-darwin20.0.0-clang --version
clang version 14.0.6
Target: arm64-apple-darwin20.0.0
Thread model: posix
InstalledDir: /opt/homebrew/Caskroom/miniconda/base/envs/eda/conda-bld/yosys_1676471780717/_build_env/bin

Now I do see that the Conda EDA team missed that flag. What was throwing me off is that it's listed as a warning there, but I was experiencing an actual error.
I'll leave the PR open on abc since it does fix the issue, however. Thanks for the quick response!


Add a legend below permafrost MAGT mini-maps

Closes #193.
This PR adds a legend below the permafrost MAGT mini-maps. This legend was implemented using HTML and CSS, similar to a legend on the Historical Sea Ice Atlas. The legend is proportional to the MAGT mini-map color maps, including the pure white +/- 1 degree Celsius "uncertainty threshold" between the blue and red gradients. The legend also adapts to the user's selection of imperial or metric units.
I've given the legend a fixed pixel width of 700px, but this shouldn't be a problem if we do end up showing only the report's qualitative text at narrow browser resolutions like we had discussed.
To test, load a report with visible permafrost MAGT mini-maps. You should see the legend below the maps. Try switching between imperial and metric units near the top of the report page to verify that the legend converts properly.

This looks great.  I really like the attention to detail with the styling of the gradients.  One thing that seemed odd at first was how the legend goes up to +20ºC, like, that's warmer than average summer air temperatures!  But this is model output and it's not clear if any of the values actually hit that -- we are validly showing the data the best we can, and this legend makes that data more accessible and prompts interesting questions.  Excellent!


[as2_behaviors_perception] cv::aruco::drawAxis deprecated in new version opencv

ROS2 Version
humble
Version
v1.0.9
Installation
source
What happened?
I am trying to build aerostack2 as2_behaviors_perception with gcc 13.2 and opencv 4.6, but the build failed with such log:
/tmp/binarydeb/ros-humble-as2-behaviors-perception-1.0.9/detect_aruco_markers_behavior/src/detect_aruco_markers_behavior.cpp:194:18: error: ‘drawAxis’ is not a member of ‘cv::aruco’
  194 |       cv::aruco::drawAxis(output_image, camera_matrix_, dist_coeffs_, rout, tout, 0.08625);
      |                  ^~~~~~~~

cv::aruco::drawAxis has been deprecated on opencv-contrib 3.4.7/4.1.1 from Apri 2019 and removed on 3.4.18/4.6.0 from Mar 17, 2022.
Need to migrate from cv::aruco::drawAxis to cv::DrawFrameAxes?
How to reproduce your issue?

gcc 13.2
opencv 4.6

Relevant log output
No response

Fixed in #509


New auto-width columns mean less info in main screen

Not sure when the change was made, but now if you add/remove columns, it changes the width of the columns for some reason. This seems like it would be a good idea - but it actually means that less info actually appears on the page under some circumstances. Here's a link to a screenshot after removing just a few columns - tons of wasted whitespace:
https://i.imgur.com/wg34ifB.png
That said, I still keep a tab open to ec2instances.info, simply because it's 3.14159x10e7 times more informative than Amazon's horrible single page list of every variety of instance available. Just wondering if there's an easy way to remedy the vast expanses of whitespace issue.

Thanks for reporting this, but I don't seen anything wrong with that screenshot. What do you suggest we show if there are just a handful of shown columns?

Sorry, I should have shown the full page - there are many more columns, the problem is, they've now been forced off to the right, so I have to scroll over to them. Makes it hard to keep track of which instance type i'm looking at.
https://i.imgur.com/f4SzuFl.png

Any thoughts?

It's definitely a problem, but my focus so far has been on the scraping logic, my CSS knowledge is close to none.
Hopefully someone more competent at CSS can help us with a fix, I'd love to see a PR tackling this issue.

I certainly understand - thanks for the reply!

Hmm I can't reproduce this one. Can you share specifically which columns you have enabled and what browser you're using? I tried Chrome + Firefox with various column setups.

Hmm. Odd. It happens for me in Firefox, Chrome, Opera, and Vivaldi, on both my home PC and work Macbook.
Just go to the main page, select the 'columns' button, then start disabling columns, and watch as each column resizes itself into the empty space where the other column was.  In fact, easiest way to see it - disable all columns expect the first one - 'Name' - then start adding them back.  It used to be that if you dropped a column, all the other columns on the right would stack inward into the space. That way I could just disable a column like 'instance storage', and the 'linux pricing' would nudge to the left, and I'd be able to see it onscreen. Now it's a matter of poking the columns on and off just right in order to get the pricing visible, asn the columns will get wider than the text within them.

Strange - I can't even repro by going all the way down to the "Name" column and then adding them back (tried various combinations). The leftmost columns like "Name", "API Name", "Memory" all properly shrink to make space for the new columns until the horizontal space is properly filled.
Here's a video of Safari which behaved the same as Chrome + FF for me: https://youtu.be/oVLiVxK4w8g

This all boils down to what I originally titled the post - previously, the columns didn't do this change in width at all. if you removed a column on screen, all the columns to the right of it would shift over one - the remaining columns on the screen didn't just make themselves wider.  In your video, when you get it down to one column - is there any value in having a screens-width whitespace after the text in a cell, rather than just keeping that one remaining column the width of the containing text? likewise if there's only three columns, or whatever.
In my opinion - for whatever that is worth - the columns should stay fixed in width to the widest cell in the column. But this is really such a minor issue - I think it's pretty pointless to keep after it!

I think I understand now, though I still can't repro this: https://i.imgur.com/f4SzuFl.png. The columns on the left should definitely be shrinking there.
As for the behavior change... we just link to libraries for the table but the versions are pinned and haven't changed in quite some time, so not sure how to explain that.


Midnight cap pipe

Closes #695

I would like to discuss this a bit further before approving. It seems to me a little risky to split slots like that, I know that right now probably it's ok, but it doesn't seem like the best solution to me.
First, I think this doesn't address @pe0ny's concerns about the sleep being split in half, right? What Heidi wanted was for the sleep to happen all at the end of a day, and the next day starts when the user wakes up.
And secondly, I was thinking: As what we are really looking for is a way to fix what the user sees... Why don't we just fix them when showing them to the user? So, if he sleeps from 10 PM to 8 AM next day, we store that big slot in the DB, but when we transform those slots into timeline items, we decide if we need to split that, cap them or directly not show them because they belong to the previous/next day.
Do I make sense? @amulware @sofokli1 @pe0ny

We decided to not do any fancy shenanigans with starting the day before/after sleeping, since there are way too many edge cases to handle. Discussion can continue here: #704
With regards to only making this change when showing data to the user: I think doing it at generation is easier. Otherwise, when fetching data for a day, we have to fetch one additional time entry for the day before, which seems strange to me and complicates the query.

Ok then. If we are going to split the slot, I agree it's not worth it to do it any other way. If we ever do the other thing, we can discuss this again 😀


Add MySQL swagger files for GA stable version 2021-05-01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[x] SDK of Js
[x] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@Suna-MS Is this just promoting 2020-05-01-preview to a stable version?

@j5lim, Thanks for the reviewing.  Yes, this is just promoting 2021-05-01-preview to a stable version

Please help merge this PR.

This RP introduces new resource types in new api version and client SDK has a different package. The old package will be used for legacy resource types. So it's ok to merge with cross version breaking changes failures.


System certificates are ignored with the rustls version

When using rattler-build with the openssl version (i.e. from conda-forge), it succeeds when you have corporate SSL certificates in your system certificates. When you use the rattler-build version with rustls (i.e. the musl one from the build artifacts), it ignores the system certificates.

Should be easily fixed by applying the same trick we did in pixi: https://github.com/prefix-dev/pixi/pull/310

Shouldnt this issue be in rattler-build though?

Yes, I thought this was an option that needed to be specified in rattler.


Create Schema for Minion using Mongoose

Everything in Mongoose starts with a Schema. Each schema maps to a MongoDB collection and defines the shape of the documents within that collection. This task involves making a schema for minions. You can refer to createMinion function in server/db.js file to complete this task.

I can create the schemas for our project.
I would like to work on this issue.

Please assign me this issue

I would like to work on this issue, please assign it to me

Please assign this issue to me as I have no issue to work on currently. I have already submitted my PR for the issues assigned to me:)

@sharmaaditya570191 I want to work on this issue . Please assign this to me


Fixes issue #506

Fixes #506. Add appropriate error message when referencing non-existing package in a bind operation. Update unit test.

rebased and merged


[Enhancement] Change opacity value to "alpha" icon

The layer opacity currently shows "{value}α".
I would like to try and replace this with an icon (maybe a big α ?) It could have three states:

white: layer is fully opaque
gray: layer has some transparency
black (or black outline?): layer is fully transparent

This way the opacity "area" of the layer item would have a constant width, which is nicer if we want to stick another icon next to it.

+1 for this

Hi there, is anyone currently working on this? I'd like to start working on this.

@zakarh assigning to you, thanks for your interest. Don't hesitate to post here if you have trouble getting started!

Ah I actually can't assign it to you directly, but feel free to get started! I will try to figure out why I can't assign it.

Awesome, thanks for the letting me know. I'll get started on this.

I added code so the alpha icon now has three opacity states. Also, I thought that numbers would better represent the opacity state so I didn't use colors. Here is a link to a video on dropbox where I demo this feature.

1α represents 100% opacity.
0.5α represents 50% opacity.
0α represents 0% opacity.


feat: remove ngZone.run for ready events

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[x] Refactoring
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #194
What is the new behavior?
ready event runs outside of an Angular zone.
Does this PR introduce a breaking change?

[x] Yes
[ ] No

https://github.com/ddubrava/angular8-yandex-maps/pull/197/files


Bug: in data class definitions for connector_id (not as per specification)

I am not sure if this is a bug, also my python knowledge is a little weak (i am mostly a Java programmer). But i noticed that all the dataclass definitions in the call.py file has incorrectly named the field connectorId as connector_id which is not as per the specification (this is for v16).
And this is causing issues when building the payload objects using these data classes. For example when i am calling the below code, the code itself works. But since this is not as per the specification, when testing with a live charging station, this is failing.
cpRequestPayload = call.TriggerMessagePayload(requested_message="TriggerMessage",connector_id=1)

    cpRequest = Call(
        unique_id=str(uuid.uuid4()),
        action=cpRequestPayload.__class__.__name__[:-7],
        payload=cpRequestPayload
    )

Since i couldn't find anyone raising an issue over this, i am guessing im doing something wrong OR is it that my charging station is not designed correctly?

@no-veternarian23
I don't think this is a bug.
In CP, the naming convention changes from camel case to snake case at this point .
Therefore, when writing CP code, you essentially write in snake_case.


[cuda] Build failure on x64-windows

Package<EMAIL_ADDRESS>Host Environment

Host: x64-windows
Compiler: MSVC 19.41.34123.0
vcpkg-tool version: 2024-10-18-e392d7347fe72dff56e7857f7571c22301237ae6
vcpkg-scripts version: unknown

To Reproduce
vcpkg install libtorch
Failure logs
-- Executing NVCC-NOTFOUND --version resulted in error: 1
CMake Error at ports/cuda/vcpkg_find_cuda.cmake:69 (message):
  Could not find CUDA.  Before continuing, please download and install CUDA
  (v10.1.0 or higher) from:

      https://developer.nvidia.com/cuda-downloads

Call Stack (most recent call first):
  ports/cuda/portfile.cmake:9 (vcpkg_find_cuda)
  scripts/ports.cmake:192 (include)

Did you read what you have posted?

Embarrassing!

You need to install CUDA locally now.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Adjusted Various Default Item Globbing Strategies

The Directory.Build.props/targets was split to differently effect the /src and /samples directories.  This allows setting EnableDefaultNoneItems == true for just the nuget package projects under the /src directory.
Also the DefaultItems.props/targets was adjusted to mimic  the .netcore web application style of globbing.

Hi @leusbj.
I'm taking some time to review this as it alters quite a few things about the way the project it put together. The splitting of the Directory.Build.props/targets files looks good.
I am a little nervous of the changes to the DefaultItems sections. There are existing issues which were closed which don't look like they are preserved in the new methodology. Also, the adding items then removing them is a known performance issue - especially with large projects (and web applications can have large numbers of static files). This is why the original system used then DefaultItemExcludes extensively.
Another issue seems to be that the web.*.config files are no longer handled the same. At the moment the transforms based on the Configurations (Debug, Release, etc.) are included as none for compile time transform. Other versions are assumed to be content so they can be used in deployment scenarios (such as msdeploy with azure pipelines). I don't think that is taken into account now either.
I do quite like the way you've added the Razor files in, as it will probably make using RazorGenerator.MsBuild easier - although I do tend to use that in libraries not the 'head' Web Application Project; others may well use it in a single project scenario.
I also appreciate that there is a lot more documentation / comments in your versions of these files than the originals (perhaps why you aren't aware of the reasons behind some of the original 'code').
Would you be willing to split this into smaller parts so we can review them individually, and get things brought in more easily, rather than a single, more monolithic 're-write'?

@CZEMacLeod sure thing, I’ll retract this PR and share one with just the break up of directory.build.props/targets.


Fix markdown autolink issues.

[x] Rescue C auto-linked content raised ArgumentError

require 'redcarpet'
markdown = Redcarpet::Markdown.new(Redcarpet::Render::HTML, :autolink => true, :space_after_headers => true)
markdown.render 'https://github.com码'

=> "
https://github.com\xE7\xA0\x81
\n"

[x] Incorrectly autolink when UTF-8 character stick with the end of URL

live example (from: http://codecampo.com/topics/822):

require 'redcarpet'
markdown = Redcarpet::Markdown.new(Redcarpet::Render::HTML, :autolink => true, :space_after_headers => true)
markdown.render '（https://github.com）'

=> "
（https://github.com）
\n"

The workaround borrowed from https://github.com/ruby-china/ruby-china/blob/master/lib/markdown.rb, with minor modifications by me (English comments, minor code structure modifications).

Per https://github.com/chloerei/campo/pull/44#issuecomment-121502932, :wave:


How cli support postcss, angular-cli.json file how to configure

Bug Report or Feature Request (mark with an x)
- [ x ] feature request

Versions.
@angular/cli: 1.0.0
node: 6.9.2
os: win32 x64
@angular/common: 4.0.0
@angular/compiler: 4.0.0
@angular/core: 4.0.0
@angular/forms: 4.0.0
@angular/http: 4.0.0
@angular/platform-browser: 4.0.0
@angular/platform-browser-dynamic: 4.0.0
@angular/router: 4.0.0
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.0
Repro steps.

The log given by the failure.

Desired functionality.
How cli support postcss, .angular-cli.json file how to configure
Mention any other details that might be useful.

We don't support postcss configuration in version 1 of the CLI. An addon system is planned for the future that would allow build customization though.


Null pointer during validating all pending order authorizations

Hi i'm getting this null pointer exception:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.<>c.<ValidateOrderAsync>b__25_1(IChallengeContext x)
   at System.Linq.Enumerable.SelectArrayIterator`2.ToArray()
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.ValidateOrderAsync(IOrderContext order)
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.AcquireNewCertificateForDomains(String[] domains)
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.RunOnceAsync()
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.RunOnceAsync()
   at FluffySpoon.AspNet.LetsEncrypt.LetsEncryptRenewalService.<StartAsync>b__16_0(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

I'm currently running the app on the latest version of .net core 2.1, but I couldn't upgrade your package to the latest version (1.118.0). I'm now using version 1.109.0.
Could this be the issue?
Thanks in advance

Why weren't you able to upgrade?

This is the nuget log:
NU1107: Version conflict detected for Microsoft.AspNetCore.Connections.Abstractions. Install/reference Microsoft.AspNetCore.Connections.Abstractions 2.2.0 directly to project API to resolve this issue.
 API -> FluffySpoon.AspNet.LetsEncrypt 1.118.0 -> Microsoft.AspNetCore.Connections.Abstractions (>= 2.2.0)
 API -> Microsoft.AspNetCore.App 2.1.1 -> Microsoft.AspNetCore.Connections.Abstractions (>= 2.1.1 && < 2.2.0).

Yes, it does unfortunately. We keep our packages up to date - you should consider doing the same.
I think updating to the latest version should resolve the issue.


Add most languages submitted by ghost and some cleanups

The languages I didn't add I personally don't think they are worth to add or some of them are not even programming languages. Please have a look at this PR @ChessMax After this PR is merged I think all of ghost's issues could be closed.

Thanks! Great job!

Thanks! Great job! I'm also doubt about adding all those basic dialects. Need to think, but I'm thinking not to add ...

Don't let him infiltrate your list with useless languages. He has successfully added to the list various commercial BASIC variants. After the job done he deleted his account and became ghost :smile:

BASIC languages have their own list: https://github.com/JohnBlood/awesome-basic


Consolidate and document deployment

Currently, configuration and scripts for deploying gnomAD and SCHEMA are scattered among:

cluster/*
packages/api/deploy/*
packages/production-server/deploy/*
projects/gnomad/deploy/*
Makefile

The ideal goal is a base configuration (browser, API, Elasticsearch, Redis, Mongo) for deployment on Kubernetes that can be shared between projects and extended with project-specific requirements (ex. read data for gnomAD).

Mostly done in e5a19deb701f641f548dcb595a3bcb9fd2e4cbfe.

Claiming success on this after adding more documentation in df6c0f732443f2e74130f6722aa41150ec758e19.

Claiming success on this after adding more documentation in df6c0f732443f2e74130f6722aa41150ec758e19.


Make this

make this for fed

it shows where the rocket gose after u shoot

why

looks cool asf


Rephrase the notes and examples in DataFrame.query

Small follow up to rephrase the examples in DataFrame.query.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1313   +/-   ##
=========================================
  Coverage          ?   92.84%
=========================================
  Files             ?       34
  Lines             ?     7339
  Branches          ?        0
=========================================
  Hits              ?     6814
  Misses            ?      525
  Partials          ?        0

Impacted Files
Coverage Δ

databricks/koalas/frame.py
93.54% <100%> (ø)

Continue to review full report at Codecov.

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

Thanks! Merged


Gamescope doesn't launch [NVIDIA]

Gamescope seems to be broken under Hyprland on Nvidia, while it does work under sway for me.
Distro: Arch Linux
Tried both gamescope and gamescope-git from AUR
$ gamescope glxgears
No CAP_SYS_NICE, falling back to regular-priority compute and threads.
Performance will be affected.
wlserver: [backend/headless/backend.c:68] Creating headless backend
vulkan: selecting physical device 'NVIDIA GeForce GTX 1660': queue family 2
vulkan: physical device supports DRM format modifiers
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x3231564E (VkResult: 0)
vulkan: supported DRM formats for sampling usage:
vulkan:   0x34325241
vulkan:   0x34325258
vulkan: physical device queue doesn't support presenting on our surface
vulkan_make_output failed
xkbcommon: ERROR: couldn't find a Compose file for locale "c" (mapped to "c")
zsh: segmentation fault (core dumped)  gamescope glxgears

this is a hyprland bug tracker, not gamescope


Hooks do not exist in Svelte, consider renaming these actions by removing the "use" part

Hooks do not exist in Svelte. They are a React feature. Please consider renaming all these by removing the use from the action name.
Compare: use:counter and use:useCounter.

See, I was even confused by the naming convention. I assumed all the useX were actions, but looks like they are stores. Call them what they are, custom stores, not hooks.
And for the actions, remove the action part of the name

Thanks, @kevmodrome for the suggestions, totally makes sense.

Resolved, I think we should preserve the type actionin the actions, used them as suffix rather than prefix, now they read as for example, use:draggableAction.

So - I think it's quite redundant to call them somethingSomethingAction - can I suggest maybe doing something like this:
For actions:
import { clickOutside } from 'svelte-legos/actions
and for the custom stores:
import { counter } from 'svelte-legos/stores
As soon as you use them in Svelte it's obvious what they are: use:x - it's an actions. $counter it's a store :)


pre-release communications

instructional video?
welcome to the new version email draft
curate github issues so we are ready to receive bug reports
schedule, plan, and communicate a weekly support/feedback call

Can you help with this if you get a chance, whatever you think makes sense (too early for video probably).. Maybe start on drafting the e-mail? Thanks! :)


Ability to open PowerToys Run without keyboard shortcut

Description of the new feature / enhancement
I would like to be able to open PowerToys Run without having to use the shortcut. In tablet mode, this is somewhat necessary. An option would be running PowerToys.PowerLauncher.exe (probably with some argument like 'show'). Right now, that just does nothing, it would be great if it would cause the Run window to show up.
Scenario when this would be used?
Allows accessing PowerToys if no keyboard is connected for example with a shortcut.
It would also enable users to create other invocation methods.
Supporting information
I was not able to find any documentation on something like this, so I assume it does not exist. If 'C:\Program Files\PowerToys\modules\launcher\PowerToys.PowerLauncher.exe' does in fact accept arguments that allow such behaviour, the documentation should be updated.

The PowerToys Systray Flyout has a Run shortcut, this should solve this issue

To be honest this is inadequate. This method takes at least 3 clicks/taps to get to the run window and the flyout takes about a second to open.
What I'm requesting is some way to open the run window directly, for example using a custom shortcut, AutoHotkey script, gesture, whatever.
If it's this tedious to access the run window, I'd rather use the windows search.


Append architectural fuzzer check to fuzzing_round

Verify model correctness before delivering violation

Thank you for the PR!
Some of the tests in CI are failing. Could you, please, fix those?

Tested fuzzing run with changes (arch fuzzer at end of fuzzing round, 1.3-dev branch) and confirmed working


istioctl 1.11.0 build issue

Bug description
istioctl 1.11.0 build issue when running make istioctl istioctl.completion
And error is below:
==> make istioctl istioctl.completion
make: *** No rule to make target `/private/tmp/istioctl-20210813-16296-1l75wdb/out/darwin_amd64/istioctl', needed by `/private/tmp/istioctl-20210813-16296-1l75wdb/out/darwin_amd64/release/istioctl.bash'.  Stop.
make: *** Waiting for unfinished jobs....
ISTIO_OUT=/private/tmp/istioctl-20210813-16296-1l75wdb/out/darwin_amd64 ISTIO_BIN=/Users/brew/Library/Caches/Homebrew/go_mod_cache/bin GOOS_LOCAL=darwin bin/retry.sh SSL_ERROR_SYSCALL bin/init.sh
Skipping envoy debug. Set DEBUG_IMAGE to download.

[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior

macOS build passed

Steps to reproduce the bug

git checkout the 1.11.0 tag
setup couple env vars (like TARGET_ARCH)
run make istioctl istioctl.completion

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
How was Istio installed?
Environment where the bug was observed (cloud vendor, OS, etc)
macOS
Additional details
This is the regression upgrade build from 1.10.3 to 1.11.0
relates to https://github.com/Homebrew/homebrew-core/pull/83195

cc @ericvn since I thought you had some PRs here recently

I have not had any issues with doing the build on my Mac on both master and release-1.11, and verified by checking out the 1.11.0 label as well. Looking at the brew script, I notice ENV["BUILD_WITH_CONTAINER"] = "0", which is causing the build to be done differently than normal, so tried adding that to my environment. Build still works.
The message implies that Make cannot figure out how to make .../out/darwin_amd64/istioctl' which is needed by the out/darwin_amd64/release/istioctl.bash. This does agree with the BUILD_WITH_CONTAINER=0 since it need's the darwin istioctl` build to generate the completion. More investigation continuing.

I'm still not able to recreate the failure (with BUILD_WITH_CONTAINER set to 0 or 1).
https://github.com/istio/istio/pull/34093 did change the dependency from istioctl to ${LOCAL_OUT}/istioctl which is needed when things are run in a build_container. Since the message is implying that there is no rule for ${LOCAL_OUT}/istioctl, it could be the cause. Trying to trace back the value of LOCAL_OUT through the Makefiles and script, things should be setup correctly.

OK. I am now able to recreate the problem. I notice that -j6 is added as a make MAKEFLAGS which allows additional threads, and that uncovers the issue noted here.

https://github.com/istio/istio/pull/34093 had an issue where during the container build the completion targets would fail as the linux version, because we are in the container, of istioctl was not getting built:
/work/out/linux_amd64/istioctl completion bash > /work/out/darwin_amd64/release/istioctl.bash
/bin/bash: /work/out/linux_amd64/istioctl: No such file or directory
make[1]: *** [Makefile.core.mk:436: /work/out/darwin_amd64/release/istioctl.bash] Error 127

The solution for that problem was to change the dependency to match the executable that was being run, so istioctl=>${LOCAL_OUT}/istioctl which caused the linux istioctl to be built and used to create the completion files. I'm not sure how this worked before the changes, and it may not have when run on a Mac.
That solution manifests itself when run in a non BUILD_CONTAINER environment when using multiple make threads as noted here.
A solution for this issue is to only use a single thread in the non BUILD_CONTAINER environment which requires no changes here.
Another solution is to create a new target  ${LOCAL_OUT}/istioctl which does the build (same as istioctl). This allows the threads to see both targets and things build normally.


feat: Mandatory dimensions feature

Problem
Mandatory Dimensions Feature
Env
MANDATORY_DIMENSIONS="dev:clientId,fare;test:fare"
https://github.com/user-attachments/assets/44cbe739-ebaa-466f-b6b4-e34a1b0805c2

@mahatoankitkumar we could have changed the Tenant structure itself
pub struct Tenant {
   name:
   mandatory_dimensions :
}

and create this object on every request

@mahatoankitkumar we could have changed the Tenant structure itself
pub struct Tenant {
   name:
   mandatory_dimensions :
}

and create this object on every request
@pratikmishra356 Lets not change the structure of Tenant right now, as this implementation will be discarded afterwards.

@mahatoankitkumar I see no checks for move api , we should have validation on move api also right ?

@mahatoankitkumar I see no checks for move api , we should have validation on move api also right ?

yeah right.


allow to listen to 'join'/'leave'/'create'/'dispose' events from outside

I'll leave this pull-request open for a while for discussion before merging. This is a suggestion from @derwish-pro.
The register method now returns an EventEmitter instance, which allows you to listen to "create", "dispose", "join" and "leave" events from outside the room scope.
Example
gameServer.register("chat", ChatRoom).
    on("create", (room) => console.log("room created!", room.roomId)).
    on("join", (room, client) => console.log("client", client.id, "joined", room.roomId)).
    on("leave", (room, client) => console.log("client", client.id, "left", room.roomId)).
    on("dispose", (room) => console.log("room disposed!", room.roomId));

Feedback is very welcome! Cheers!

Thank you, that's wonderful!


Feature request: Add support for files formats .. TXT, ZIP, DOC, DOCX, XLS, XLSX, RTF, PPT, PTTX..

Support for a few more common office type files formats .. TXT, ZIP, DOC, DOCX, XLS, XLSX, RTF, PPT, PTTX

Thanks for using this plugin and sorry for the inconvenience. Didn't have time work with this project for a while.
I add the custom attachment types support in 2.2.0, now you can set whatever formats you want with it.


Improve aliasing

Fixes #1861

We still need a configurable Locale or something actually.

Well, at least it looks fine to me.
And the build succeeds. :wink:


Add expectations for default member deser

This adds expectations for the default member deserialization so that an error will be thrown if the type being deserialized isn't correct.
See https://github.com/aws/aws-sdk-js-v3/pull/2515 for the other half of this.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We'd have to handle that separately from the InternalFailure wrapping. We could also have InternalFailure embed the error that caused it so we could unpack it.

I think a TypeError emerging from deserialization code could be wrapped in a SerializationException without having to go through InternalFailure. The only concern would be whether or not we could also reuse the message in the TypeError for the SerializationException (eventually, I didn't define a message at first, whoops). We would have to be sure that nothing else could throw a TypeError with a message we didn't want customers to receive. That consideration may make us choose a different TypeError, or a specialized subclass of it.


Update Cloudflared to latest version

📑 I have found these related issues/pull requests
Was trying to find a current request for this but doesn't seam like one was created for this in a while.
🏷 Feature Request Type
Other
🔖 Feature description
Was looking, and it seems that Cloudflared has been updated a bunch of times since the current version bundled in the current version of Uptime Kuma.
Current Version: 2024.4.0
Latest Version: 2024.8.3
✔ Solution
This isn't an urgent item at all and can be potentially updated with V2.0, but as I do use the Cloudflared config to reverse proxy my instance, having it on the latest version would be great to have to ensure that there aren't any issues or bugs.
❓ Alternatives
No response
📝 Additional Context
No response

If there is a reason for this comment, we can push out a patch release. As you did not say so, I am assuming the regular release cadence is sufficient.
We try to update dependencys before releases, but if you want to help us in this regard, single PRs updating dependencys (and looking at the change logs) would be appreciated.

Ahh, didn't know that the dependencies were updated before each release, guess it had been a while since the last one so didn't know.
Was just wanting to clarify if they are updated with each release, so I'll close this one then, as just wanting to validate if this would be updated going forward in future updates.


fix: Improving nodejs geeting started page

Which problem is this PR solving?
This solve some minor issues with the getting started page for nodejs as outlined in this as well as others outlined below

Added Webstorm .idea files to gitignore so that they are ingored. .idea files are similar to the .vscode files which are also ingored
Updated the intro to inform the user that only metrics and traces are shown in the example application and that logs are still experimental
Added typscript initialisation
Replaced the installation of @opentelemetry/api  with @opentelemetry/sdk-trace-node since it wasnt specified in the install step

Short description of the changes
Minor improvmenenrs to the getting started docs for nodejs

Whoops, this looks a bit messy. Why all the edits in the submodules? Ideally, the changes should only affect this repo.

I dont know what happend but when I created a new branch some documents somehow updated themslves with new values.   Those files that are not nodejs.md (besides the .gitgnore wher I added webstorm .idea files to .gitingore) were not changed my me. Or what am I missing?

@James-Kaguru My guess is you likely had an older version of the repo you branched off of. What I've found works is either:

Delete my work --> branch off latest synced main
Delete my submodules -> rebase off main -> branch again

Since we pull in several submodules, and submodules aren't necessarily the greatest, it's easy to end up in a state like this.

@cartermp thanks for the advice ...since I have already commited those changes does it mean that I should create another pull request and close this one?

@cartermp thanks for the advice ...since I have already commited those changes does it mean that I should create another pull request and close this one?

We can try to clean up the PR on your behave, but it is important that you then pull those updates to your local tree and then make sure that future commits do not contain updates to the submodules (do a git status before commit/push to verify, if you verify your changes locally via npm run serve you also should be safe, since this will make sure you have the latest git submodules installed


Garrison ULTRA Remote Logs solution

Change(s):

New solution for Garrison ULTRA Remote Logs

Reason for Change(s):

New solution

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

@microsoft-github-policy-service agree company="Garrison Technology Ltd"
Garrison Technology Limited, registered in England and Wales with registered number: 09286531. Our registered address is 117 Waterloo Road, London, SE1 8UL. Our VAT number is GB209458886
Except for the email issued by Garrison to enable access to the Garrison ULTRA Trial Service, Garrison does not conclude contracts via email. This email (including any attachments and any subsequent emails in this chain) is SUBJECT TO CONTRACT and STRICTLY CONFIDENTIAL.
This email incorporates Garrison’s email policy which can be found herehttps://www.garrison.com/legal.
From: microsoft-github-policy-service[bot] @.>
Sent: 16 October 2024 11:11
To: Azure/Azure-Sentinel @.>
Cc: Ralph de Kanter @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] Garrison ULTRA Remote Logs solution (PR #11285)
@rdekanterhttps://github.com/rdekanter please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/pull/11285#issuecomment-2416349544, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BL4XCVDKMOK3ZJWMP2QKT2TZ3Y3UBAVCNFSM6AAAAABQBDCCKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGM2DSNJUGQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @v-prasadboke, we haven't had a response here in a while. Could you please advise on what else we need to do to get this merged? Thanks!

Hello @rdekanter & @theolukensgarrison can you provide me write access to this branch.
Also please update this branch from master.
Need to check validation failures.
And apologies for the delay in response

@v-prasadboke - we have updated to the main branch and you have a pending access invite.

Hi @v-prasadboke, just reaching out again. What is there left for us to do here? Thanks!

Hi @v-prasadboke, just reaching out again. What is there left for us to do here? Thanks!

Hello @theolukensgarrison im checking what permissions are failing or missing

Hello @rdekanter & @theolukensgarrison, I have some doubts about the connector. We are checking this internally if anyhow we can overcome this failure


save more gas

Saving more gas
Core changes:

[contracts/src/Rollup.sol#L532]
delete i++
add unchecked { i += 1; }

Notes:

change base on this.
at the end of the loop can save more gas by using unchecked { i += 1; }
@LEAFERx

Hey @easonnong, thanks for your contributions.
Looping in @ujvl to confirm whether gas optimization of our contracts is currently on our priority list or not.
Anyways, my suggestions would be 2-fold:

Create a list of all plausible gas optimizations in the Specular contracts, post that list in the PR description and then make changes. It would be much more coherent to review such a PR as compared to reviewing all gas optimizations in different PRs in a sort of irregular flow.
Regarding your unchecked maths optimization, it would be great if you could provide the list of reasonings behind why you think an unchecked block is safe for all the instances that you decide to introduce them at, in the PR description.

Apart from that, great work :)


[RFR] Add the extra field to action aliases

Different chat adapters have special capabilities which are sometimes very handy and nice. Slack has attachment colors and parsing/unfurling options for better formatting; HipChat has Connect features; and so on.
It’s hard for users to add support for those right now, because you have to modify the schema and the DB connector in st2, and only then submit a PR to hubot-stackstorm utilizing the new parameter. More importantly, if we had a lot of requests for this, our schema would be overblown with rarely used parameters.
A solution for this,—which has been discussed some weeks ago, but I only got around to it now,—is an extras object inside the alias with a “free” schema. It will allow people to easily add support for extra features with relative ease and without modifying st2 (which would imply only getting a feature out in the next st2 release and complicating the schema). While this is not ideal architecturally (a reason the schema exists in the first place is to have order, and this breaks it a bit), I feel like pros outweigh the cons, and it’s worth to introduce this. We still maintain strict schema outside extras, after all.
Another neat feature this PR includes is rendering extras with Jinja, sharing the context with ack or result, depending on the placement. E.g. different colors depending on the execution status.
This can also be useful for possible usage of action aliases outside chat (e-mails, sms, tweets, and whatnot).
An example:
name: "tesla.honk_horn"
action_ref: "tesla.honk_horn"
description: "Honk your horn"
formats:
  - “honk-honk”
result:
  format: "**Honk Honk**"
  extras:
    color: “<% if result.succeeded %> green <% else %> red <% endif %>”

What do you think?

https://stackstorm.slack.com/archives/stackstorm/p1457592739007163

Yeah, I was in favor of extra approach in the past so I'm +1 on the overall idea.

Docs and some tests for this change would be nice, besides that, LGTM :+1:

Updated the test fixtures to account for the new schema, and docs are coming along as a part of a more general chatops PR that DZ requested. I want to do an example in hubot-stackstorm, too, to show how to use extras with some actual code.
Changed to extra.

I see the need for extra and am +1 to the idea and PR.
Free schemas generally pose are good and bad for exactly the same reason i.e. you can put anything. In this case it is not really a free schema but an adapter specific schema so depending on the eventual chat service/tool the supported properties are fixed. The corollary is that it is likely that an alias will have adapter specific properties which as I understand this impl may or may not apply.
Thoughts on mitigation

As long as alias formatting degrades gracefully it should be acceptable. Can this be guaranteed?
Can we document the fixed set of properties for slack or hipchat? Even if we start with slack by giving a few examples it should be acceptable.
extras is generic as it does not suggest where the property will be interpreted - can we make this specific like extra_adapter_info - yeah this is gross and I do not like the name but suggesting the direction.

Another neat feature this PR includes is rendering extras with Jinja, sharing the context with ack or result, depending on the placement. E.g. different colors depending on the execution status.

This is really nice :)

+1

I'm excited to see this, nice work Ed!

As long as alias formatting degrades gracefully it should be acceptable i.e. if there is a slack specific property then will hipchat ignore or barf. Can this be guaranteed? If not can we doc this information?

It will ignore. If you want to support a certain extra, you extend hubot-stackstorm and check for the extra in a formatter for the adapter you want. Other formatters will not even know it's there.

Can we document the fixed set of properties for slack or hipchat? Even if we start with slack by giving a few examples it should be acceptable.

Yeah, I'm working at the example for attachment colors, and then we can doc it. I'll also get a post with guidelines out, and maybe we can squeeze the guidelines into the docs, too (we really should).

extras is generic as it does not suggest where the property will be interpreted - can we make this specific like extra_adapter_info - yeah this is gross and I do not like the name but suggesting the direction.

I actually did plan for it to be generic. This part is debatable, but we can add adapter-agnostic params here, too: I was considering playing with confirmations, for example. We can even add client-specific params here—like a subject line if someone wants to use chatops with e-mail or something (an unlikely case, just the first I could come up with). Hence the very generic name.

Also see https://github.com/StackStorm/hubot-stackstorm/pull/101

Feel free to merge this once you add some tests and changelog has been updated :+1:

@Kami: nice! The test fixtures are already updated (and there's nothing else to test because the field doesn't really do anything), I'll update the changelog tomorrow and merge.

@emedvedev Cool :)
I thought it might also be a good idea to just add a test case which makes sure extra parameter is actually stored / written in the DB, but that's not a big deal (as long as we have some higher level tests which exercise this parameter).

@emedvedev

I actually did plan for it to be generic. This part is debatable, but we can add adapter-agnostic params here, too: I was considering playing with confirmations, for example. We can even add client-specific params here—like a subject line if someone wants to use chatops with e-mail or something (an unlikely case, just the first I could come up with). Hence the very generic name.

I would recommend keeping a very limited scope of properties and say extra is only for properties we transparently pass down to an adapter. Enabling arbitrary features without taking care to define the properties leads to extremely brittle APIs. A loose definition of generic i.e. we have no clue what the schema can be since its adapter specific to magic new features are available via extra can get very sketch.


Reorganize the algorithms

PR to reorganize the algorithms

[ ] Need to merg this PR #286  first

Pull Request Test Coverage Report for Build 277

11 of 11 (100.0%)  changed or added relevant lines in 11 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 91.31%

Totals

Change from base Build 274:
0.07%

Covered Lines:
2669

Relevant Lines:
2923

💛  - Coveralls


Network discovery implemented

For more information and documentation, visit this page.
I created APK if you want to test it on Android. Open the app on 2 phones (they should be connected to wifi), start server on 1 phone, and click "Refresh LAN" on the other. Don't try to connect it to Editor, it doesn't use newest version of Mirror.
You'll probably want to remove some unneeded stuff, like test method. Also, style changes are required.
It has room for improvements, see TODO list for more info.

Thanks for submitting this as a PR.
I'm going to request that vis2k and Paul do not close this PR right off the bat as this would solve a majority of "How do you do LAN Discovery?" questions day-in and day-out that we get in the Mirror Discord chat.
I know the games they are making may not suit LAN discovery, but since this PR is a likely component replacement for UNET's broken Network Discovery.

@in0finite sorry for late reply. this is very useful.
is there any way you could make the code shorter and more clean? maybe go over it again?
also how did you test this? is there a simple example that we can add to mirror examples?

I am not sure how can I make it shorter / cleaner. I removed the test coroutine and made some improvements in latest commit (here is a complete changelog). All that is left is to make style changes.


⚠ Processors has degraded performance

In 1ce446c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: Processors performance has improved in c329360.


Building on windows, problem with Eigen lib

The windows step-by-step guide is pretty nice.
However, when following through, I encounter a problem when trying to build the Eigen lib (v3.3.4).
Any ideas?
The project file is not created. Any idea of additional dependencies (BLAS or others)?
Thanks.
Paul
Here part of the output:
-----------------------------------------------------------------------------------
-- A library with BLAS API not found. Please specify library location.
-- LAPACK requires BLAS.
-- Could NOT find CHOLMOD (missing: CHOLMOD_INCLUDES CHOLMOD_LIBRARIES)
-- Could NOT find UMFPACK (missing: UMFPACK_INCLUDES UMFPACK_LIBRARIES)
-- Could NOT find SUPERLU (missing: SUPERLU_INCLUDES SUPERLU_LIBRARIES SUPERLU_VERSION_OK)

-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- Could NOT find BLAS (missing: BLAS_SEQ_LIBRARIES BLAS_LIBRARY_DIRS)
-- Could NOT find MPI_C (missing: MPI_C_LIBRARIES MPI_C_INCLUDE_PATH)
-- Could NOT find MPI_CXX (missing: MPI_CXX_LIBRARIES MPI_CXX_INCLUDE_PATH)
-- A version of Pastix has been found but pastix_nompi.h does not exist in the include dir
ectory. Because Eigen tests require a version without MPI, we disable the Pastix backend.
-- Could NOT find SPQR (missing: SPQR_INCLUDES SPQR_LIBRARIES)
-- Found unsuitable Qt version "" from NOTFOUND
globbed:
CMake Error at D:/Tools/Boost/share/cmake/boost/BoostConfig.cmake:15 (include):
  include could not find load file:

    C:/Projets/PCL/SuperBuild_boost_1_50/CMakeExternal/Install/Boost/share/boost-/cmake/Bo
ostConfig.cmake
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.9/Modules/FindBoost.cmake:236 (find_package)
  test/CMakeLists.txt:342 (find_package)

Boost  found.
-- Could NOT find GOOGLEHASH (missing: GOOGLEHASH_INCLUDES GOOGLEHASH_COMPILE)
-- Could NOT find ADOLC (missing: ADOLC_INCLUDES ADOLC_LIBRARIES)
-- Could NOT find MPFR (missing: MPFR_INCLUDES MPFR_LIBRARIES MPFR_VERSION_OK) (Required i
s at least version "2.3.0")

We address this while working on the dev-0.9.3 branch.

Moved to dev-0.10.0

@pfrydlewicz  I am trying to reproduce this issue,  I got the log very similar to the your, and  the configuration is successful.. Basically Eigen is header only Library and Cmake is used for Installing only.
Can you provide with your complete log
Here is my build log:
H:\eigen_Test\eigen\build>cmake -Ax64 -DCMAKE_INSTALL_PREFIX="H:\eigen_Test\inst
all" ..
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.24215.1
-- The CXX compiler identification is MSVC 19.0.24215.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio
14.0/VC/bin/x86_amd64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio
14.0/VC/bin/x86_amd64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o 14.0/VC/bin/x86_amd64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studi
o 14.0/VC/bin/x86_amd64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test standard_math_library_linked_to_automatically
-- Performing Test standard_math_library_linked_to_automatically - Success
-- Standard libraries to link to explicitly: none
-- Performing Test COMPILER_SUPPORT_OPENMP
-- Performing Test COMPILER_SUPPORT_OPENMP - Success
-- Performing Test EIGEN_COMPILER_SUPPORT_CPP11
-- Performing Test EIGEN_COMPILER_SUPPORT_CPP11 - Success
-- Found unsuitable Qt version "" from NOTFOUND
-- Performing Test EIGEN_COMPILER_SUPPORT_CXX11
-- Performing Test EIGEN_COMPILER_SUPPORT_CXX11 - Success
-- The Fortran compiler identification is unknown
-- A cache variable, namely BLAS_DIR, has been set to specify the install direct
ory of BLAS
-- Looking for BLAS -- mkl.h not found
-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Found Threads: TRUE
-- Looking for MKL BLAS: not found
-- Looking for Goto BLAS: not found
-- Looking for Open BLAS: not found
-- Looking for Eigen BLAS: not found
-- Looking for Eigen BLAS: not found
-- Looking for Atlas BLAS: not found
-- Looking for PhiPACK BLAS: not found
-- Looking for CXML BLAS: not found
-- Looking for DXML BLAS: not found
-- Looking for SunPerf BLAS: not found
-- Looking for SCSL BLAS: not found
-- Looking for SGIMATH BLAS: not found
-- Looking for IBM ESSL BLAS: not found
-- Looking for IBM ESSL MT BLAS: not found
-- Looking for ACML BLAS: not found
-- Looking for ACML BLAS: not found
-- Looking for ACML BLAS: not found
-- Looking for Apple BLAS: not found
-- Looking for NAS BLAS: not found
-- Looking for Generic BLAS: not found
-- Looking for Generic BLAS: not found
-- Looking for Generic BLAS: not found
-- Looking for Generic BLAS: not found
-- Looking for Generic BLAS: not found
CMake Warning at cmake/FindBLAS.cmake:1371 (message):
  BLA_VENDOR has been set to All but blas libraries could not be found or
  check of symbols failed.

  Please indicate where to find blas libraries.  You have three options:

  - Option 1: Provide the installation directory of BLAS library with cmake
  option: -DBLAS_DIR=your/path/to/blas

  - Option 2: Provide the directory where to find BLAS libraries with cmake
  option: -DBLAS_LIBDIR=your/path/to/blas/libs

  - Option 3: Update your environment variable (Linux: LD_LIBRARY_PATH,
  Windows: LIB, Mac: DYLD_LIBRARY_PATH)

  To follow libraries detection more precisely you can activate a verbose
  mode with -DBLAS_VERBOSE=ON at cmake configure.

  You could also specify a BLAS vendor to look for by setting
  -DBLA_VENDOR=blas_vendor_name.

  List of possible BLAS vendor: Goto, ATLAS PhiPACK, CXML, DXML, SunPerf,
  SCSL, SGIMATH, IBMESSL, Intel10_32 (intel mkl v10 32 bit),Intel10_64lp
  (intel mkl v10 64 bit, lp thread model, lp64 model), Intel10_64lp_seq
  (intel mkl v10 64 bit, sequential code, lp64 model),Intel( older versions
  of mkl 32 and 64 bit), ACML, ACML_MP, ACML_GPU, Apple, NAS, Generic
Call Stack (most recent call first):
  cmake/FindLAPACK.cmake:138 (find_package)
  test/CMakeLists.txt:30 (find_package)

-- A library with BLAS API not found. Please specify library location.
-- LAPACK requires BLAS.
-- Could NOT find CHOLMOD (missing: CHOLMOD_INCLUDES CHOLMOD_LIBRARIES)
-- Could NOT find UMFPACK (missing: UMFPACK_INCLUDES UMFPACK_LIBRARIES)
-- Could NOT find SUPERLU (missing: SUPERLU_INCLUDES SUPERLU_LIBRARIES SUPERLU_V
ERSION_OK)
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- Could NOT find BLAS (missing: BLAS_SEQ_LIBRARIES BLAS_LIBRARY_DIRS)
-- Performing Test SCOTCH_Num_4
-- Performing Test SCOTCH_Num_4 - Failed
-- Performing Test SCOTCH_Num_8
-- Performing Test SCOTCH_Num_8 - Failed
-- Could NOT find MPI_C (missing: MPI_C_LIB_NAMES MPI_C_HEADER_DIR MPI_C_WORKS)

-- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX
_WORKS)
-- Could NOT find MPI_Fortran (missing: MPI_Fortran_LIB_NAMES MPI_Fortran_F77_HE
ADER_DIR MPI_Fortran_MODULE_DIR MPI_Fortran_WORKS)
-- Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND MPI_Fortran_FOUND)
-- Performing Test PTSCOTCH_Num_4
-- Performing Test PTSCOTCH_Num_4 - Failed
-- Performing Test PTSCOTCH_Num_8
-- Performing Test PTSCOTCH_Num_8 - Failed
-- A version of Pastix has been found but pastix_nompi.h does not exist in the i
nclude directory. Because Eigen tests require a version without MPI, we disable
the Pastix backend.
-- Could NOT find SPQR (missing: SPQR_INCLUDES SPQR_LIBRARIES)
-- Found unsuitable Qt version "" from NOTFOUND
-- Performing Test COMPILER_SUPPORT_FASTMATH
-- Performing Test COMPILER_SUPPORT_FASTMATH - Failed
-- Performing Test COMPILER_SUPPORT_FPFAST
-- Performing Test COMPILER_SUPPORT_FPFAST - Success
-- Could NOT find Boost
-- Could NOT find GOOGLEHASH (missing: GOOGLEHASH_INCLUDES GOOGLEHASH_COMPILE)
-- Could NOT find ADOLC (missing: ADOLC_INCLUDES ADOLC_LIBRARIES)
-- Could NOT find MPFR (missing: MPFR_INCLUDES MPFR_LIBRARIES MPFR_VERSION_OK) (
Required is at least version "2.3.0")
-- Could NOT find GMP (missing: GMP_INCLUDES GMP_LIBRARIES)
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- Could NOT find FFTW (missing: FFTW_INCLUDES FFTW_LIBRARIES)
-- Found OpenGL: opengl32
-- Could NOT find GLUT (missing: GLUT_glut_LIBRARY)
CMake Warning (dev) at unsupported/test/CMakeLists.txt:121 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "MSVC" will no longer be dereferenced when the policy
  is set to NEW.  Since the policy is not set the OLD behavior will be used.
This warning is for project developers.  Use -Wno-dev to suppress it.

CUDA_TOOLKIT_ROOT_DIR not found or specified
-- Could NOT find CUDA (missing: CUDA_TOOLKIT_ROOT_DIR CUDA_NVCC_EXECUTABLE CUDA
_INCLUDE_DIRS CUDA_CUDART_LIBRARY) (Required is at least version "7.0")
-- Found unsuitable Qt version "" from NOTFOUND
-- Qt4 not found, so disabling the mandelbrot and opengl demos
-- ************************************************************
-- ***    Eigen's unit tests configuration summary          ***
-- ************************************************************
--
-- Build type:        Release
-- Build site:        inpu7d0034
-- Build string:      win7-19.0.24215.1-sse2-64bit
-- Enabled backends:
-- Disabled backends: Cholmod,  UmfPack,  SuperLU,  PaStiX,  METIS,  SPQR,  Qt4
support,  Boost.Multiprecision,  GoogleHash,  Adolc,  MPFR C++,  fftw,  OpenGL,

-- Default order:     Column-major
-- Maximal matrix/vector size: 320
-- SSE2:              Using architecture defaults
-- SSE3:              Using architecture defaults
-- SSSE3:             Using architecture defaults
-- SSE4.1:            Using architecture defaults
-- SSE4.2:            Using architecture defaults
-- AVX:               Using architecture defaults
-- FMA:               Using architecture defaults
-- AVX512:            Using architecture defaults
-- Altivec:           Using architecture defaults
-- VSX:               Using architecture defaults
-- ARM NEON:          Using architecture defaults
-- ARMv8 NEON:        Using architecture defaults
-- S390X ZVECTOR:     Using architecture defaults
-- C++11:             OFF
-- SYCL:              OFF
-- CUDA:              OFF
--
CXX:               C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/x8
6_amd64/cl.exe
 CXX_FLAGS:         /DWIN32 /D_WINDOWS /W4 /GR /EHsc /EHsc /wd4127 /wd4505 /wd47
14 /D_CRT_SECURE_NO_WARNINGS /D_SCL_SECURE_NO_WARNINGS
 Sparse lib flags:

-- ************************************************************
--
-- Configured Eigen 3.3.4
--
-- To build/run the unit tests, read this page:
--   http://eigen.tuxfamily.org/index.php?title=Tests
--
-- Configuring done
-- Generating done
-- Build files have been written to: H:/eigen_Test/eigen/build

@pfrydlewicz  can we close this issue.

Closing due to lack of activity; please reactivate as needed.

The windows step-by-step guide is pretty nice.
However, when following through, I encounter a problem when trying to build the Eigen lib (v3.3.4).
Any ideas?
The project file is not created. Any idea of additional dependencies (BLAS or others)?
Thanks.
Paul
Here part of the output:
-----------------------------------------------------------------------------------
-- A library with BLAS API not found. Please specify library location.
-- LAPACK requires BLAS.
-- Could NOT find CHOLMOD (missing: CHOLMOD_INCLUDES CHOLMOD_LIBRARIES)
-- Could NOT find UMFPACK (missing: UMFPACK_INCLUDES UMFPACK_LIBRARIES)
-- Could NOT find SUPERLU (missing: SUPERLU_INCLUDES SUPERLU_LIBRARIES SUPERLU_VERSION_OK)

-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- Could NOT find BLAS (missing: BLAS_SEQ_LIBRARIES BLAS_LIBRARY_DIRS)
-- Could NOT find MPI_C (missing: MPI_C_LIBRARIES MPI_C_INCLUDE_PATH)
-- Could NOT find MPI_CXX (missing: MPI_CXX_LIBRARIES MPI_CXX_INCLUDE_PATH)
-- A version of Pastix has been found but pastix_nompi.h does not exist in the include dir
ectory. Because Eigen tests require a version without MPI, we disable the Pastix backend.
-- Could NOT find SPQR (missing: SPQR_INCLUDES SPQR_LIBRARIES)
-- Found unsuitable Qt version "" from NOTFOUND
globbed:
CMake Error at D:/Tools/Boost/share/cmake/boost/BoostConfig.cmake:15 (include):
  include could not find load file:

    C:/Projets/PCL/SuperBuild_boost_1_50/CMakeExternal/Install/Boost/share/boost-/cmake/Bo
ostConfig.cmake
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.9/Modules/FindBoost.cmake:236 (find_package)
  test/CMakeLists.txt:342 (find_package)

Boost  found.
-- Could NOT find GOOGLEHASH (missing: GOOGLEHASH_INCLUDES GOOGLEHASH_COMPILE)
-- Could NOT find ADOLC (missing: ADOLC_INCLUDES ADOLC_LIBRARIES)
-- Could NOT find MPFR (missing: MPFR_INCLUDES MPFR_LIBRARIES MPFR_VERSION_OK) (Required i
s at least version "2.3.0")

I got the similar error when i tried to build Eigen lib (v3.3.7) . Have you solved this problem?  If yes, could you share your solution?


can we implement an adb server?

Hi,
Could you clarify your question? What are you trying to do. There is already a great adb server made by google. Also, there is an adb server in this package. It's used in the unit tests! :-) Please check it out and see if it suites your needs.

@agirllmy - adb server is actually open source (written in C/C++) and may be modified by anyone.
As for it`s quality - it is not as high as you expect from most popular mobile OS in the world, but it at least updated and supported
What about creating own implementation in java - it will not be easy to maintain at least 3 platforms and supporting hundreds of features which adb now have, nevertheless it is possible and may be an interesting project

Check out AdbProtocolHandler - it implments the server side adb protocol. You need to inject a AdbResponder to handler commands sent to a specific device. Note: Only the protocol is implemented here, it's used in the unit tests, it can not talk to any device in any way. For this, please use the adb server in the Android Open Source Project (AOSP) found here.

I want to implement a java program which can talk to a device by using adb protocol，just like the function of adb server.

As I suspected. This will lead you down into a rabbit hole of dealing with hardware, etc. It is not a huge task, especially if you drop x-platform constraints. Some JNI will most likely be needed to access usb hardware. There probably already are libraries for this you can use. For the adb protocol, see the documentation, the adb protocol implemented in this rep and also the source code linked above. Good luck in your endeavors! :)


Better Discord JavaScript Error Occurred in the main process

Error Popup: https://prnt.sc/j26fuh

Download BandagedBD.exe from here
https://github.com/rauenzi/BetterDiscordApp/releases

BandagedBD fixes the javascript error but seems to stop BD from running at all.

This appears even when I use Bandaged BD


Support for OAuth token authentication

Aware that this project is in maintenance mode, but I just pushed something that came up in the TalkShopify slack to my fork of this repository: https://github.com/Shopify/shopify_theme/compare/master...gavinballard:add_oauth_token_support.
If this is OK to get merged let me know and I will update the PR with tests, README and CHANGELOG updates et cetera.

You could just drop support for the username and password.
You can make authenticated API requests by using the Private Apps Password, so you could just use password. Maybe something like this:
def self.shopify
  token = config[:access_token] || config[:password]
  headers 'X-Shopify-Access-Token', token
  base_uri "https://#{config[:store]}"
  ShopifyTheme
end

I'm pretty sure that would be a reverse compatible change, and would reduce the codepaths we'd need to worry about.
I'd totally accept a pull request on this. Thanks for the work @gavinballard!


%20 being added into searches

I love your workflow! I've noticed that spaces are now being replaced with %20 in the workflow recently, is there a fix I can do at my side? Thanks!

I love your workflow! I've noticed that spaces are now being replaced with %20 in the workflow recently, is there a fix I can do at my side? Thanks!

I noticed this too! Are you on Alfred 5?

@skobylite this may be fixed in Alfred 5.0 EA11 (released today).
Alfred 5.0 EA11
• Fix Early Access regression in URL query argument handling throughout Alfred
• Open URL workflow object
• Improve flexibility of URL placeholder handling by offering two new options to Encode {query} and Encode {var:}
• These are checked by default, and are best left checked under normal use of this object
• When unchecked, options are passed to the URL processor unchanged, giving developer control over encoding
• Overhaul Accessibility for the Open URL object, with correct tab focus ordering, and better VoiceOver descriptions

Pretty sure this is fixed in the official Alfred 5 release, so closing this one.


RFC: Drop compress option?

There is a standard way to disable compression support in fetch via Accept-Encoding header (works right now in node-fetch):
const res = await fetch("https://something.com/", {
  headers: { "Accept-Encoding": "identity" }
});

Do we really need a Node-only option here?

bonus question: Is there a way to discard the hole 'accept-encoding' from even being sent in the first place?
noting === identity also
Guess that what's compress true/false is all about...

would be annoying if we removed the default accept-encoding and all of the sudden you would have to add it anywhere you want it.

what if... they added "Accept-Encoding": "identity" but durning the request it gets removed only if it match 'Identity'?

We need this feature: https://github.com/node-fetch/node-fetch/issues/465#issuecomment-435816667
We want to request the content with gzip, defalte, br but do not decompression in node-fetch. compress options is the only way to do this so in this case compress option should not be deprecated. (or rename to decompress like axios does)?

identity means "request the content without compressing it"
not "request the content as it's being sent without decompressing the receiving content"
So if you want the raw data as gzip then compress has a value. Think I wanted to use it myself at some point.

I disagree that the compress option should be removed, but I do think it should be deprecated and renamed decompress since it controls decompressing the response rather than compressing the request.
Consider the scenario where the developer wants to implement their own decompression algorithm, maybe for coursework experimentation:
const res = await fetch("https://something.com/", {
  headers: {
    'Accept-Encoding': 'deflate'
  },
  compress: false
});

However, it does seem we should consider changing the behavior when setting compress: false to also set Accept-Encoding: identity.  Consider this next example -- the response body may or may not be compressed since no Accept-Encoding header is sent; however, this is likely not what the developer intended:
const res = await fetch("https://something.com/", {
  compress: false
});

They probably intended this:

```js
const res = await fetch("https://something.com/", {
  headers: {
    'Accept-Encoding': 'identity'
  },
  compress: false
});

I can see a value in keeping this option... specially for those who wish to just proxy/forward a compressed response along.
However. I think the name compress is slightly confusing. as the name applies that it should compress something while posting data.
it should be named something else...

it could be decompress: true.
or something closer to 'Accept-Encoding' and 'Content-Encoding' could be decode: true.


[moltenvk] add new port

Add new port for moltenVK library.
This port only supports macOS platform to provide a compliant API to Vulkan based on native Metal.

Hi @magicfoo thanks for this PR.
Since this port only supports macOS platform. Please update baseline with the following content:
moltenvk:x86-windows=fail
moltenvk:x64-windows=fail
moltenvk:x64-windows-static=fail
moltenvk:x64-uwp=fail
moltenvk:arm-uwp=fail
moltenvk:arm64-windows=fail
moltenvk:x64-linux=fail

/azp run

I noticed that this port failed on OSX pipeline.
I get this info from CI system in fetch-dependencies-x64-osx-rel-err.log
HEAD is now at 204cd13 Merge pull request #134 from Tobski/patch-1
fetchDependencies: line 109: cmake: command not found

Could you please check this?

I noticed that this port failed on OSX pipeline.
I get this info from CI system in fetch-dependencies-x64-osx-rel-err.log
HEAD is now at 204cd13 Merge pull request #134 from Tobski/patch-1
fetchDependencies: line 109: cmake: command not found

Could you please check this?

Do you have more details please? It doesn't fail on my laptop. MoltenVK needs xcode 11.3 (catalina). Note that from my tests, few ports including glib will start failing with the new xcode 11.3. My other PR fixes by the way.

Thanks for your feedback.
I will rerun and let's wait for the new test result from CI system.

/azp run

It seems that it still failed on osx pipeline.

Hi @magicfoo
Could you please resolve the conflicts?

Pinging @magicfoo
Is work still being done for this PR?

Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.


NSFS | NC | Actions | fix RHEL 9 rpm suffix

Explain the changes

docker build was bumped base image to RHEL9 in https://github.com/noobaa/noobaa-core/pull/7571, so the rpm suffix should be updated as well.

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

[ ] Doc added/updated
[ ] Tests added

@romayalon @tangledbytes
Few questions here:

Is the RPM really bound to a specific RHEL version?
Will the RPM work on both RHEL 8 and RHEL 9?

In the case that it is not bound, we can remove the suffix of the OC
We need to ensure we support RHEL 9 and RHEL 8.

@liranmauda As I mentioned on slack, currently it only builds RHEL9, if we want to support both RHEL8 and RHEL9 this change https://github.com/noobaa/noobaa-core/pull/7571 should be reverted and we should make it configurable by the user. the issue is that there was no nightly rpm build since this change was merged.

I don't think we should revert, We should only patch the single line that changes the 'libraries': ['/lib64/libboost_thread.so.1.75.0']
We should do it dynamically, On RHEL9 keep it, and on RHEL 8 change it to 1.66 back.
We should also use the correct base for supporting both RHEL versions.
Opened: https://github.com/noobaa/noobaa-core/issues/7608
In this PR case, we should keep the RHEL version in the RPM name, and el9 represents it correctly.

@liranmauda In any case, make rpm and the affected actions should be changed when we have both RHEL8 and RHEL9 support