Add docs for cross-repo publishing using CircleCI

📚 Documentation
Thanks to #764, we can publish the site to a different repo by setting projectName in docusaurus.config.js to the destination.
However, this behaves differently on CircleCI. The deployment script reads environment variable CIRCLE_PROJECT_REPONAME, which represents the name of the repository of the current project, and overrides the projectName configured in docusaurus.config.js
See https://github.com/facebook/docusaurus/blob/812a30be5727d88ae62a7c15473796a9b2bc1297/packages/docusaurus/src/commands/deploy.ts#L45
const projectName = process.env.PROJECT_NAME ||
    process.env.CIRCLE_PROJECT_REPONAME ||
    siteConfig.projectName;

To correctly cross-repo publishing the site, the user will need to configure environment variables in CircleCI config
- run:
  name: Deploy to GitHub Pages
  command: yarn run deploy
  # Set environment variables so that project is deployed correctly
  environment:
    GIT_USER: [git username]
    ORGANIZATION_NAME: Computerization
    PROJECT_NAME: computerization.github.io

I feel like this somehow needs to be documented so as not to confuse users using CircleCI
Have you read the Contributing Guidelines on issues?
Yes

can i work on this ?

can i work on this ?

Sure, please

can i work on this ?

Sure, please

okay i am working on this..thank you

hey, not very familiar with this problem
but shouldn't we instead make projectName in the config be the source of truth, and eventually read an env variable from there?
Like
const projectName = process.env.PROJECT_NAME ||
    process.env.CIRCLE_PROJECT_REPONAME ||
    "myHardcodedProjectName";

module.export = {
  projectName,
}

but shouldn't we instead make projectName in the config be the source of truth, and eventually read an env variable from there?
Like
const projectName = process.env.PROJECT_NAME ||
    process.env.CIRCLE_PROJECT_REPONAME ||
    "myHardcodedProjectName";

module.export = {
  projectName,
}

The problem here is that, instead of letting siteConfig be the source of truth, it is being overridden when running docusaurus deploy from CircleCI.
You can see that the CircleCI built-in variable CIRCLE_PROJECT_REPONAME, which is name of source repo, overrides the siteConfig.projectName in the config. And here we are setting another environment variable CIRCLE_PROJECT_REPONAME to override this CIRCLE_PROJECT_REPONAME
This is an undocumented behavior and I feel like it should be noted somewhere in the documentation.
But yeah, I too wonder why would the maintainers have CIRCLE_PROJECT_REPONAME override the config and not use the config as the ultimate truth... :confused:

@yechs i am new here....can you point me which doc to change or i have to add new doc for this ? help me please

I'm not very familiar with these problems, not sure I can help, but happy to merge a PR if you feel it improves the doc
It'd be nice to specify if you are on v1 or v2.

v1 docs is in ./docs
v2 docs is in ./website/docs

I'm not very familiar with these problems, not sure I can help, but happy to merge a PR if you feel it improves the doc
It'd be nice to specify if you are on v1 or v2.

v1 docs is in ./docs
v2 docs is in ./website/docs

i can do both i think ....

@slorber  hi do you have discord or gitter ? i have something to discuss... :)

Yes I'm on discord, probably busy today though but next week should be fine

@slorber okay..please give me your discord id .....

I'm just Sebastien Lorber there ^^

@slorber  thank you

The Docusaurus team is actively working on Docusaurus v2.
After a very long alpha, Docusaurus v2 is now in beta.
We believe that the v2 beta is already better than v1, and v2 is ready for maintstream adoption.
Apart from critical issues and security fixes, we don't plan to invest much time on Docusaurus v1 anymore.
We are all closing v1 issues.
Maybe the current issue is already fixed in Docusaurus v2.
Please try to upgrade, and if the issue is still there on Docusaurus v2, open a new issue.


fix: 867 Hide status bar in Splash Screen

Description
It is usually considered better to hide the status bar in splash screen and in most of the apps the status bar is hidden in splash screen
Related issues and discussion
Fixes #867
Screen-shots, if any

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines .

Hi @teolemon, ready to merge


Attempt to fix docs.rs build

Description
I'm not quite shure why exactly the build at docs.rs has failed, but one thing was overlooked for shure: Having the uhid feature, now we must enable all-features for this build.
Type of change

[x] Metadata (non-breaking change which affects build on docs.rs)

Code Checklist

[x] I have performed a self-review of my own code

thx for the attempted fix! As the build still fails with the same error as before, the issue looks to be more tightly coupled to the binrw crate.
Looking into reproducing the error locally now.


Catching *nix signals (segfault in particular)?

As part of supporting multiple versions of LLVM in inkwell, I ran into a case where perfectly valid input to a certain function for non existent data (similar to looking up a key that doesn't exist in a hash table) would cause a segfault in a small subset of versions of LLVM. This is presumably a LLVM bug since it works fine in previous versions.
Thinking about this, I'm wondering: How terrible of an idea is it to set up a signal handler(IE via the signal crate) to catch that segfault and return the error case that I would have normally returned in LLVM versions that don't segfault?
I'm thinking at best the segfault could just be a null pointer dereference, but in the worst case it could have done something crazy like corrupted the whole stack...
Is this a crazy idea? What if I first look at the LLVM source code and am able to verify that the bug(maybe there's a fix I can look at in a newer version)'s segfault is relatively harmless in each offending version (ie null ptr deref or reading (but not writing) to invalid memory?).

I believe the common belief is that you shouldn't try to "catch" a segfault or mask it in any way. The way I've heard it described, segfaults are just another way to find out there's a programming bug somewhere so the correct thing to do would be to crash loudly so someone can fix the bug.
That said, because you want to still support the segfaulting versions you'll probably want to do something so users don't encounter segfaults during normal use. I can think of a couple ways to deal with the issue while still supporting the offending versions, listed from least to most hacky:

Use #[cfg] so whenever you try to invoke the function from an offending version it'll always return an error (or panic) saying "this function is unavailable due to a bug in this version of LLVM"
Try to detect input which may result in segfaults before the LLVM function is invoked and return an error
Write a catch_segfault() wrapper function that'll invoke a closure and try to catch any segfaults, transforming them into errors. I'm not sure how you'd do this.

Thanks for looking into it! I've thought about those ideas too, and I think the problems are as follows:

cfg wrapper - the function in question is a really useful one and I feel like the library is far less useful without it for the offending versions (again, it does still work in the case of the input representing something that exists) and the offending versions are in the later versions, not the older ones so it's more likely to be missed than not
checking input - the input is just a string, so its hard if not impossible to validate (again, like a key in a hash table that may or may not be there but checking to see if not there segfaults)

re: C++ thread: The way I understood it, "You can't catch segfaults" is in reference to the try/catch mechanics of C++. You can't catch it with that because it's not a C++ exception. But you can totally set up a signal handler for SIGSEV and "catch" it that way, which is what the signal library does but in rust. The point about segfaults always being UB is probably a good point, though.
I guess there's just no good solution...

But you can totally set up a signal handler for SIGSEV and "catch" it that way, which is what the signal library does but in rust.

Signal handlers are just callbacks that get fired when that particular signal is received, so how do you plan to resume code flow? As far as I can tell, you'd need to stash away a return pointer and then jump to it in the signal handler if a segfault was encountered. I guess you could always execute the thing in another thread and use a "segfault encountered" flag to return the error, but I'm not sure if that'll work because LLVM isn't Send or Sync.

So I was able to work around this issue for the LLVM versions in question by calling a similar function that took the exact same input params and early returned if it returned an Err, discarding an Ok. I was lucky that other function existed


Fixed bug for resources proposed by people with periods in their names

r @weronica

See #80

LGTM


26: Changed from .includes to regex

Pull Request Template
Description
Please include a summary of the change and which issue is fixed or added.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
Fixes #26
Checklist

[x] My contributions and commit messages follows the style guidelines of this project
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes
[x] The Pull Request has an informative and human-readable title
[x] Changes are limited to a single goal (avoid scope creep)
[x] Code can be automatically merged (no conflicts)
[x] I confirm that I have read any Contribution guidelines (CONTRIBUTING)
[x] I confirm that I wrote and/or have the right to submit the contents of my PR, by agreeing to the Developer Certificate of Origin, by adding a 'sign-off' to my commits

Jamen, vi slöar till det och kollar med chatgpt vad regexpen gör också, bara för att se om jag tänkte rätt ..."Putting it all together, the regular expression /[.*+?^${}()|[]\]/g is used with the replace() method to find and replace any occurrences of the special characters . * + ? ^ $ { } ( ) | [ ] . Each occurrence is replaced with the literal string $&, where $& represents the matched substring. The purpose of this regular expression is to escape the special characters within the baseUrl string, ensuring that they are treated as literal characters rather than having their special meaning in regular expressions.".
Plötsligt händer det - chatgpt har rätt i ett svar!
Ser bra ut vad jag kan se i övrigt, approve, men som sagt nu kikade jag bara, och har inte testat detta IRL med körning.


Nivida xavier

did you tested before on nvidia xavier, or do you know if it will work there?

Hi, I do not own one, so I have not tested it. But if you are able to install the onnxruntime, it should work.

i installed onnxruntime, but it needs to upgrade pip to last one.

i cloned the repo https://github.com/ibaiGorordo/onnx-Ultra-Fast-Lane-Detection-Inference.git, installed the requirements.
then clone this repo https://github.com/PINTO0309/PINTO_model_zoo/tree/main/140_Ultra-Fast-Lane-Detection,  then download_tusimple.sh the output file ultra_falst_lane_detection_tusimple_288x800.onnx will passed into python file as model. then run the python script.
is this steps right?

Everything sound good, yes. Make sure to modify the model_path to the path of your model.

Okay, i will testing on nvidia xavier now and will feedback you, if you are interest.

Nice! I am glad to see that it works.
Also, I have not implemented it yet, but there is also another .onnx model for lane detection here:
https://github.com/PINTO0309/PINTO_model_zoo/tree/main/141_lanenet-lane-detection
In this case, it will be necessary to modify this repository slightly to make it work.

Thank you! I would love to hear about the inference speeds of those models.
Let me know if you face any issues.

i start run script video but i got video like this the frames show with this type there are small delay maybe 1 sec, but i will test again to ensure with delay time.

i will download the video and check if there any delay after that

i downloaded the video but nothing change still have a delay maybe 5 to 10 sec per frame.
i'm going to test the next one  https://github.com/PINTO0309/PINTO_model_zoo/tree/main/141_lanenet-lane-detection.

do you know how conver onnx to TR?, i guess it will work fine if i converted to TR

Check the repository I linked, he also converted both models into TensorRT:
https://github.com/PINTO0309/PINTO_model_zoo#19-others

i found there are some file generated when i bash from first time  i tried to pass this file model_float32.tflite to python code but it's appear error.
onnxruntime.capi.onnxruntime_pybind11_state.InvalidProtobuf: [ONNXRuntimeError] : 7 : INVALID_PROTOBUF : Load model from models/saved_model_tusimple/model_full_integer_quant.tflite failed:Protobuf parsing failed.
Do you what this mean?

i tried with tflite but it's slower than onnx it's like not moving.
i need to check that gpu is running

can you share with me video link for your testing.
because it's very very slow, with dealy unxpected.

my question when run python3 videoLaneDetection.py is there any option to enable GPU, the output is not accepted compare to your video https://www.youtube.com/watch?v=0Owf6gef1Ew this very very fast than nvidia xavier.

That video was recorded in a desktop GPU, so probably will be faster. You can check if you are running in the GPU like this:
import onnxruntime as ort
ort.get_device()

It might be better to test the other model because I think it should be faster (I have not tested it yet).

i tried tflite but were very slow than onnx

Yeah, in your case, probably the TensorRT is the best option.

so how i can get TensorTr form onnx or Tflite

https://www.youtube.com/watch?v=Z65hbhXCnvQ  This video with ONNX.

https://www.youtube.com/watch?v=eCS6jtwo3Oo TFLITE it's very very slow.

So after watching those videos what you recommend to get real time Lane Line Detection?

I think there are two options for TensorRT, you can either use the onnx model but with the tensorrt library, or in the folder witht eh models, there should be a tensorrt_saved model to be used in tensorflow. I have not done any testing in tensorrt, so I might be wrong.
But, with that speed, it might be worth to switch to the other model.

i didn't find inside model_saved tensorRT.
do you have any recommdation for other models?

You can either try with the other model I mentioned (lanenet).
Or another option is to try some of the models in this repository (But it is probably harder to setup):
https://github.com/Turoad/lanedet
So, probably start with lanenet.

So, i will try lannet first and show results with you.
also will work on lanedet for comparing.
thanks for you effort.

Good luck!

Yeah that looks better.
Also, you might find interesting this project also in Xabier but he even combines depth estimation and object detection:
https://github.com/iwatake2222/self-driving-ish_computer_vision_system

thanks @ibaiGorordo.
BTW i tested TfLite repo on axvier but it's still not working fine.
i will test Pytorch repo and let you know.


[ENH] Add PC algorithm

Fixes #11
Closes: #10
Changes proposed in this pull request:

PC algorithm implementation with separate skeleton discovery stage (has all the features of causal-learn I think(?), except for missing-value support)
Adds the abstract class for Constraint Based learning algorithms
Adds the Context class
Adds an example showing how to run PC algorithm
Adds a metric submodule for comparing graphs

Before submitting

[ ] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.
[ ] I've updated or added any relevant docstrings following the syntax described in the
Writing docstrings section of the CONTRIBUTING docs.
[ ] If this PR fixes a bug, I've added a test that will fail without my fix.
[ ] If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

https://output.circle-artifacts.com/output/job/42854568-1d11-48d3-b89a-660449f4b9c0/artifacts/0/dev/index.html

Codecov Report

Merging #18 (03bfa3f) into main (a67b95c) will decrease coverage by 0.66%.
The diff coverage is 73.45%.

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

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   76.90%   76.23%   -0.67%
==========================================
  Files           7       13       +6
  Lines         342      787     +445
  Branches       55      159     +104
==========================================
+ Hits          263      600     +337
- Misses         63      138      +75
- Partials       16       49      +33

Impacted Files
Coverage Δ

dodiscover/constraint/pcalg.py
65.41% <65.41%> (ø)

dodiscover/constraint/utils.py
68.75% <68.75%> (ø)

dodiscover/context.py
69.56% <69.56%> (ø)

dodiscover/_protocol.py
61.53% <73.91%> (+0.66%)
:arrow_up:

dodiscover/constraint/skeleton.py
75.88% <75.88%> (ø)

dodiscover/constraint/_classes.py
81.15% <81.15%> (ø)

dodiscover/metrics.py
91.66% <91.66%> (ø)

dodiscover/ci/g_test.py
62.71% <0.00%> (+1.69%)
:arrow_up:

dodiscover/ci/oracle.py
100.00% <0.00%> (+52.63%)
:arrow_up:

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

https://output.circle-artifacts.com/output/job/4ffd2aba-0ca5-4a98-ab4d-29c694a00382/artifacts/0/dev/index.html

This PR is quite big. Would it be possible to have each of the listed changes as a separate PR? Otherwise it is almost impossible that there is a proper review. Optimally, a PR should not have more than ~250 lines (preferably less). Except this is simply moving stuff over that has been review before already.

That's doable! The challenge here is that the CI is still evolving as well. Sorry some files are changing there.
If you're okay with the skeleton, abstract class, etc. being PRed without tests first that's fine.
Then the final PR for the PC algo would have the corresponding tests?

You can also choose another PR (i.e. the branch) as a reference ('based on'), then if you make changes in, e.g., the CI stuff, it would be reflected here as well. Also, if there are inconsistencies, you can simply resolve them once the PR is approved. E.g., if the PR is about the PC-algorithm, we don't care about the details of the CI tests as long as we assume that there is 'something'. Then once the PR for the PC-algorithm is approved, you can simply adjust/base it to the latest changes of the CI tests.
Wouldn't it be possible to add tests for the classes independently of the PC algo? Just some basic tests (if they are necessary at all), like adding/deleting edges behave as expected etc. And then you can add further ones with the PC commit.

This PR is quite big. Would it be possible to have each of the listed changes as a separate PR? Otherwise it is almost impossible that there is a proper review. Optimally, a PR should not have more than ~250 lines (preferably less). Except this is simply moving stuff over that has been review before already.

@bloebp @robertness and @darthtrevino I've now broken up the PR a bit. I'm leaving this open to demonstrate the PC example for discussion, but for the code itself:

first it would be good to merge #19 to consolidate issues with the CI
second, I have added the skeleton learning method, which can be its own PR in #20
Once those are merged in, I can then add the abstract base class for constraint-based structure learning algos. #21
Finally, the PC algo along with its tests and examples can be added in this PR after it is rebased on top of the main branch

^ Apologies for the gigantic PRs. I am more used to doing things in bite-sized chunks, but getting a repo setup sometimes takes a bit of wrangling. Will be better about it :p
Hopefully the breakups now make reviewing more streamlined and easy.

Closed in favor of #30


It's using the new Makefile I wrote for the tutorial, and that I improved yesterday evening for sandbox. Now F* caching is project-wide and should work.
Use only one dependency, workspace-wide, to hax-lib, so that we can actually run cargo update hax-lib
put the makefile at one place, and have proxy makefiles that just include them

The output layout is much better, and rebuilding now starts where it left off.

Seems like this was merged into https://github.com/cryspen/libcrux/pull/475

https://github.com/cryspen/libcrux/pull/475 is now merged.
Could you check if there were some changes here that did not make it into that PR?
Otherwise, let's close this.

Nice, let's close this, there are a few thing, gonna make another PR


Configuration files for Prism

@XVincentX can you please add detail to this ticket?

This was being done to bring Prism in line with Spectral, but we just removed Spectral config files. Let's close this and revisit some time in the future if users ask for it.


Fix logloss test failure

Description
Their was a problem with computation of gth logloss because the probability value was too close to 0 or 1 so log(prob) produced a nan value. I added probability clipping to avoid problems with logloss computation (the same approach is used in original algorithm)

/intelci: run

Two more general comments on this file

using oneapi::dal::detail::operator<<; doesn't seem to be used / have an effect. Can it be removed?
I don't like the check_val() helper function. It shadows where the original error happened. I think it should be a macro instead. (Or am I running the test incorrectly?)

$ /localdisk2/mkl/huberand/oneDAL/bazel-bin/cpp/oneapi/dal/backend/primitives/objective_function/test_logloss_dpc

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
test_logloss_dpc is a Catch v2.13.10 host application.
Run with -? for options

-------------------------------------------------------------------------------
test random input - double without L1 - no fit intercept - double
-------------------------------------------------------------------------------
cpp/oneapi/dal/backend/primitives/objective_function/test/logloss_dpc.cpp:53
...............................................................................

cpp/oneapi/dal/backend/primitives/objective_function/test/fixture.hpp:50: FAILED:
  REQUIRE( abs(real - expected) < atol )
with expansion:
  nan < 0.000001

This only points into the check_val() function, and does not have a backtrace from which line it came. So I cannot tell which of the many tests using check_val() actually failed. I really don't like that.

Two more general comments on this file

using oneapi::dal::detail::operator<<; doesn't seem to be used / have an effect. Can it be removed?
I don't like the check_val() helper function. It shadows where the original error happened. I think it should be a macro instead. (Or am I reading the log incorrectly?)

$ ./bazel-bin/cpp/oneapi/dal/backend/primitives/objective_function/test_logloss_dpc

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
test_logloss_dpc is a Catch v2.13.10 host application.
Run with -? for options

-------------------------------------------------------------------------------
test random input - double without L1 - no fit intercept - double
-------------------------------------------------------------------------------
cpp/oneapi/dal/backend/primitives/objective_function/test/logloss_dpc.cpp:53
...............................................................................

cpp/oneapi/dal/backend/primitives/objective_function/test/fixture.hpp:50: FAILED:
  REQUIRE( abs(real - expected) < atol )
with expansion:
  nan < 0.000001

This only points into the check_val() function, and does not have a backtrace from which line it came. So I cannot tell which of the many tests using check_val() actually failed. I really don't like that.

Two more general comments on this file

using oneapi::dal::detail::operator<<; doesn't seem to be used / have an effect. Can it be removed?
I don't like the check_val() helper function. It shadows where the original error happened. I think it should be a macro instead. (Or am I reading the log incorrectly?)

$ ./bazel-bin/cpp/oneapi/dal/backend/primitives/objective_function/test_logloss_dpc

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
test_logloss_dpc is a Catch v2.13.10 host application.
Run with -? for options

-------------------------------------------------------------------------------
test random input - double without L1 - no fit intercept - double
-------------------------------------------------------------------------------
cpp/oneapi/dal/backend/primitives/objective_function/test/logloss_dpc.cpp:53
...............................................................................

cpp/oneapi/dal/backend/primitives/objective_function/test/fixture.hpp:50: FAILED:
  REQUIRE( abs(real - expected) < atol )
with expansion:
  nan < 0.000001

This only points into the check_val() function, and does not have a backtrace from which line it came. So I cannot tell which of the many tests using check_val() actually failed. I really don't like that.

I agree with this point. Actually I'm adding some new functionality and updating the tests in a separate branch, I think I will change it to MACROS there.


[!] Invalid Podfile file: unexpected token at 'TypeError: Cannot read properties of undefined (reading 'configurations')

Environment
react-native -v: 70.6
npm ls react-native-macos<EMAIL_ADDRESS>node -v: 19
npm -v: 8.19.3
yarn --version: 1.22.19
xcodebuild -version: 14.1 (14B47b) (M1 Pro Macbook)

Steps to reproduce the bug
trying to run npx react-native-macos-init on newly created react-native app for ios. ios app run perfectly but macos command failing.
Expected Behavior
No response
Actual Behavior
No response
Reproducible Demo
No response
Additional context
full error
[!] Invalid `Podfile` file: unexpected token at 'TypeError: Cannot read properties of undefined (reading 'configurations')

    at Object.dependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/react-native-macos/node_modules/@react-native-community/cli-platform-ios/build/config/index.js:102:37)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:47:61

    at Array.reduce (<anonymous>)

    at getDependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:44:51)

    at get react [as react] (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:99:18)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:16:51

    at Array.forEach (<anonymous>)

    at filterConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:15:38)

    at Object.func (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:27:32)

    at Command.handleAction (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli/build/index.js:142:23)

info Run CLI with --verbose flag for more details.
'.

 #  from /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/macos/Podfile:6
 #  -------------------------------------------
 #    platform :macos, '10.15'
 >    use_native_modules!
 #    use_react_native!(
 #  -------------------------------------------
Couldn't install Pods. Updating the Pods project and trying again...
> pod install --repo-update

[!] Invalid `Podfile` file: unexpected token at 'TypeError: Cannot read properties of undefined (reading 'configurations')

    at Object.dependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/react-native-macos/node_modules/@react-native-community/cli-platform-ios/build/config/index.js:102:37)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:47:61

    at Array.reduce (<anonymous>)

    at getDependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:44:51)

    at get react [as react] (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:99:18)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:16:51

    at Array.forEach (<anonymous>)

    at filterConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:15:38)

    at Object.func (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:27:32)

    at Command.handleAction (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli/build/index.js:142:23)

info Run CLI with --verbose flag for more details.
'.

 #  from /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/macos/Podfile:6
 #  -------------------------------------------
 #    platform :macos, '10.15'
 >    use_native_modules!
 #    use_react_native!(
 #  -------------------------------------------
Couldn't install Pods. Updating the Pods project and trying again...
Command `pod install` failed.
└─ Cause: Invalid `Podfile` file: unexpected token at 'TypeError: Cannot read properties of undefined (reading 'configurations')

    at Object.dependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/react-native-macos/node_modules/@react-native-community/cli-platform-ios/build/config/index.js:102:37)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:47:61

    at Array.reduce (<anonymous>)

    at getDependencyConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:44:51)

    at get react [as react] (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/loadConfig.js:99:18)

    at /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:16:51

    at Array.forEach (<anonymous>)

    at filterConfig (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:15:38)

    at Object.func (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli-config/build/commands/config.js:27:32)

    at Command.handleAction (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/@react-native-community/cli/build/index.js:142:23)

info Run CLI with --verbose flag for more details.
'.

 #  from /Volumes/Office/TestProj/rn-mac-app/AwesomeProject/macos/Podfile:6
 #  -------------------------------------------
 #    platform :macos, '10.15'
 >    use_native_modules!
 #    use_react_native!(
 #  -------------------------------------------

Command failed: npx --quiet pod-install --non-interactive --quiet Error: Command failed: npx --quiet pod-install --non-interactive --quiet
    at checkExecSyncError (node:child_process:885:11)
    at Object.execSync (node:child_process:957:15)
    at installPods (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/react-native-macos/local-cli/generator-macos/index.js:136:16)
    at generateMacOS (/Volumes/Office/TestProj/rn-mac-app/AwesomeProject/node_modules/react-native-macos/local-cli/generate-macos.js:33:3)
    at Object.<anonymous> (/Users/sohelkabir/.npm/_npx/20f1505fae2cef5b/node_modules/react-native-macos-init/lib-commonjs/cli.js:254:9)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/sohelkabir/.npm/_npx/20f1505fae2cef5b/node_modules/react-native-macos-init/lib-commonjs/cli.js:10:58)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processImmediate (node:internal/timers:442:9) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 54235,
  stdout: null,
  stderr: null
}

react-native-macos maybe incompatible with 0.70.6
Fails with 0.70.6
# On Windows 11
npx react-native init fails                # Installs react-native 0.70.6
cd fails
npx react-native-windows-init --overwrite
npx react-native autolink-windows          # Works
npx react-native-macos-init                # Installs react-native 0.68 and shows warnings about unmet peer dependencies
npx react-native autolink-windows          # Fails

Works with 0.68.5
# On Windows 11
npx react-native init works --version 0.68.5
cd works
npx react-native-windows-init --overwrite
npx react-native autolink-windows              # Works
npx react-native-macos-init
npx react-native autolink-windows              # Works !
npx react-native run-windows                   # Also works: "Welcome to React Native" app appears

We only support up to 0.68 right now. The next macOS release will be 0.71 in the coming months


Generated error report when using autocomplete in import 'xxx.dart'

Analyzer Feedback from IntelliJ
Version information

IDEA AI-182.5<IP_ADDRESS>14842
2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36
AI-182.5<IP_ADDRESS>14842, JRE 1.8.0_152-release-1248-b01x64 JetBrains s.r.o, OS Windows 7(amd64) v6.1 Service Pack 1, screens 1600x900, 1600x900

Exception
Dart analysis server, SDK version 2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36, server version 1.23.0, error: Analysis failed: D:\Projects\Flutter\filestring-flutter\fluttersink\lib\singleview\single_view_index.dart context: exception_20190313_143149_028
NoSuchMethodError: Class 'LibraryElementInBuildUnit' has no instance getter 'session'.
Receiver: Instance of 'LibraryElementInBuildUnit'
Tried calling: session
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
#1      LibraryElementForLink.noSuchMethod (package:analyzer/src/summary/link.dart:3736:48)
#2      LibraryElementInBuildUnit.session (package:analyzer/src/dart/element/element.dart:5206:25)
#3      LibraryImportScope._lookupInImportedNamespaces (package:analyzer/src/dart/resolver/scope.dart:542:30)
#4      LibraryImportScope.internalLookup (package:analyzer/src/dart/resolver/scope.dart:397:15)
#5      EnclosedScope.internalLookup (package:analyzer/src/dart/resolver/scope.dart:137:27)
#6      Scope.lookup (package:analyzer/src/dart/resolver/scope.dart:1063:12)
#7      AstRewriteVisitor.visitMethodInvocation (package:analyzer/src/generated/resolver.dart:83:35)
#8      MethodInvocationImpl.accept (package:analyzer/src/dart/ast/ast.dart:8671:49)
#9      MapLiteralEntryImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:8242:13)
#10     UnifyingAstVisitor.visitNode (package:an

This should have been fixed by 7418238 which is in Dart 2.3.0.


fix(bookings): pass correct params

These are the correct params https://github.com/PlaceOS/drivers/blob/bookings_fix/drivers/place/calendar.cr#L136-L143

Hey @stakach , I've noticed that the owner param isn't being used anywhere. https://github.com/PlaceOS/drivers/blob/4fb96ba75fb16513b54fe4bce77bfbd2ca1a2bcc/drivers/place/bookings.cr#L109
Is it supposed to be used for something or can I remove it?

Yeah I think I was intending it for allowing another user to be the organizer of the booking
So we should probably do something like:
host_calendar = owner.presence || @calendar_id
If we want the calendar entry being owned by the specified account. Also in Google land the resource calendar cannot own a meeting, it needs to be assigned to the service account I think

Thanks @stakach , good to know about what google needs too.
For book_now
https://github.com/PlaceOS/drivers/blob/8d8e401ea1ccce08f47d5cfc2036991437e886c4/drivers/place/bookings.cr#L109-L132
Do we want those meetings to be automatically started or should they just remain as pending? I can add these 2 lines in between lines 129-130 to do that but just wanted to check what functionality we want.
@last_booking_started = event["event_start"]
define_setting(:last_booking_started, event["event_start"])

@stakach I've made this commit
https://github.com/PlaceOS/drivers/pull/67/commits/d6ebd15fb0db50f4bbc87010576bf3e48e5f9bad
Logic is:

For google setups, setting?(String, :calendar_id) should be defined as the service account which means @calendar_id = service_account and room_is_organizer = false
For o365 setups, setting?(String, :calendar_id) should not be defined which means @calendar_id = system.email and room_is_organizer = true

The room is always added as an attendee for both google/o365 setups.

@stakach , I'm calling poll_events here which works fine if the room is the owner of the booking.
https://github.com/PlaceOS/drivers/blob/bookings_fix/drivers/place/bookings.cr#L130
However, if we pass the owner param so another user can be the host/organizer of the booking, this creates the booking in the owner's calendar but takes a few seconds to actually also be in the room's calendar. This means the poll_events call on line 130 won't actually update self[:bookings] as the booking will not be in the room's calendar yet.
The 2 ways I can think of dealing with this are:
Option 1: Introduce a sleep period after creating the booking before calling poll_events on line 130 so that when poll_events is called, the booking does exist in the room's calendar.
Option 2: Manually insert the booking which we have from event here https://github.com/PlaceOS/drivers/blob/bookings_fix/drivers/place/bookings.cr#L119 into self[:bookings]


Extract crawler interfaces into module

Extract crawler interfaces into separate module and make jar of this module

@AndriyBaibak 1 hour


CloudConfigurationManager.GetSetting in 3.2.3 returns null

I'm not sure if I'm missing something when using CloudConfigurationManager to load my setting from app.config for my .NET client.
   <appSettings>
      <add key="AzureSubscriptionId" value="XXX" />
      <add key="AzureTenantId" value="XXX" />
      <add key="AzureClientId" value="XXX" />
      <add key="AzureClientSecret" value="XXX" />
    </appSettings>

And use the following:
string subscription = CloudConfigurationManager.GetSetting("AzureSubscriptionId");
But in Debug mode, it returns null.
The directive is using Microsoft.Azure;
Version of Microsoft.WindowsAzure.ConfigurationManager Nuget package is 3.2.3

@thuansoldier can you try the recently released package and let us know if this resolves your issue, if not please let us know.
https://www.nuget.org/packages/Microsoft.Azure.ConfigurationManager/

Hi Guys,
I have the same issue. I am using the latest version of the CloudConfigurationManager [Microsoft.Azure.ConfigurationManager] and the application could not get the app settings.
Error I get is "System.DllNotFoundException: 'Unable to load DLL 'fusion.dll' or one of its dependencies: The specified module could not be found. "
I am using .net core 2.1 and it is a console app.
Below is the code snippet
`var connectionString = Microsoft.Azure.CloudConfigurationManager.GetSetting("StorageConnection");
var storageAccount = CloudStorageAccount.Parse(connectionString);
var blobClient = storageAccount.CreateCloudBlobClient();
var container =  blobClient.GetContainerReference("Test");
container.CreateIfNotExistsAsync();
        Console.ReadKey();`

Any idea why this is happening.

I have a library that uses CloudConfigurationManager. This library is in .net framework 4.7.x.
This library is consumed by Azure Function, written in framework 4.7.x. Everything is fine.
However, I wanted to write test case against the library in .net core. And that is where I got this Fusion.dll error.
My question is not whether any fix available. Rather, why should I not move to Scripting languages. Because, this is not the first time. and the product, .Net Core, is still primitive.


Updated the STO FY25 Q2 and the released feature list based on Q1 work

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ x] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Local Preview screenshot:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6645006aa3559160973d4d34--harness-developer.netlify.app


Feat(eos_cli_config_gen): Add interface documentation for PIM knobs

Enhancement summary
Interface-level PIM and associated knobs are not covered in the generated markdown device documentation in eos_cli_config_gen.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
N/A
Describe the solution you would like
N/A
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

@ClausHolbechArista just had a look at eos_cli_config_gen README and I can find the following documentation:

ethernet interfaces: https://github.com/gmuloc/ansible-avd/blob/devel/ansible_collections/arista/avd/roles/eos_cli_config_gen/README.md?plain=1#L974
port-channels: https://github.com/gmuloc/ansible-avd/blob/devel/ansible_collections/arista/avd/roles/eos_cli_config_gen/README.md?plain=1#L1421
Vlan interface: https://github.com/gmuloc/ansible-avd/blob/devel/ansible_collections/arista/avd/roles/eos_cli_config_gen/README.md?plain=1#L1498

to me it looks like we could close this issue but maybe you had noticed anything else?

The point of this issue is the generated markdown documentation. We could add a multicast section and have general multicast settings and interface specific settings under that.

Ah i see - I read it as update the read me but this is really update the documentation templates - my bad!

Ah i see - I read it as update the read me but this is really update the documentation templates - my bad!

Not at all, the description was vague. I have updated it a bit, to make it less ambiguous.


KA-lite for mac uninstall and now not allowing clean install

From @kevhyde on April 7, 2017 4:39
Summary
I am not experienced in programming. I installed KA lite on my mac today and got it working as far as the questions and user accounts etc. I could not show ka lite where my compressed downloaded videos were by scanning. Nothing was being found. I could not see the .kalite folder and tried to show a new data file location in preferences so I could link to torrented video. This stopped my ka lite working. I then deleted the KA-lite folder and contents from applications. Then I found a github page here that gave terminal commands to remove invisible .kalite folders from the system. I've done this. When I try to install the KA-lite again, it goes through the motions of installing but then at summary stage advised that installation failed
System information
KA-lite version 0.17
mac OS yosemite 10.10.5

Version: 0.17
safari

Thanks very much for any suggestions, Kevin
Copied from original issue: learningequality/ka-lite#5434

@kevhyde thanks for reporting this - I've moved it to our installers repository.
I can't tell for sure what can cause the installer to fail, maybe @mrpau-eduard @mrpau-richard can suggest to remove some additional artifacts from the old installation which can block a fresh install?

Hi @kevhyde you can download this file ka-lite-remover.sh then run it on your machine.
Steps to run this script:

Download the ka-lite-remover.sh from github.
Open terminal.
Run bash ~/path/to/script/ka-lite-remover.sh

This script will remove all the dependencies of the old KA-Lite installation.
You need to run this script to remove the *.plist, kalite executable and the kalite resources.

Thanks for your help. Sorry but I'm not that experienced in this kind of programming. Can I just double check the process you've outlined above? To download the ka-lite-remove.sh do I just copy and paste the lines of code? Then copy them into terminal?
I just can't see where I can download a script file or something. If you could explain it in real dummies language that would be appreciated as this does look like the fix I"m looking for.
Thanks, Kevin

Hi @kevhyde!  :slightly_smiling_face:

Right-click (or was it Option+ click on Mac?) this link ka-lite-remover.sh and choose Save (link) as to download the ka-lite-remover.sh script file to, let's say, your Desktop.
Open Terminal.
Type cd Desktop and press Enter.
Type bash ka-lite-remover.sh  and press Enter.

Let us know what appears in the Terminal after this.

@mrpau-eduard what needs to be done for the Mac installer automatically perform various steps pf ka-lite-remover.sh during uninstallation (except user data)?

Hi guys, thanks very much for your help. That has@radinamatic that has worked thanks and now I have ka lite installed, have changed my contents folder location and added torrented videos and it's all running. This is a great system of learning that you've been creating here, thanks very much. Kevin

@kevhyde Glad it helped... 🙂
Have fun using KA Lite!!!
Cheers!

Cool, let's keep the issue open until @mrpau-eduard or @mrpau-richard can tell if the Mac Installer uninstallation can be modified easily so this doesn't happen to others ?

Hi @benjaoming - I did a back-read and it seems that Kevin did not do a clean uninstall as we documented at  Uninstallation of the installed KA Lite package..
Here's what he did:

...This stopped my ka lite working. I then deleted the KA-lite folder and contents from applications. Then I found a github page here that gave terminal commands to remove invisible .kalite folders from the system. I've done this...

I don't know if the "terminal commands" he mentioned were the ones in ka-lite-remover.sh.
The "normal" way to uninstall an app in macOS is to just drag it to the Trash.  However since we did some customizations during setup, we created the ka-lite-remover.sh for a clean uninstall and renamed it as KA-Lite_Uninstall.tool after a successful installation.
So there's no need to modify the Mac installer and we can just point users to the doc.
I think we can close this now. 😸

Hi there, no you’re right. Initially I ran a couple of terminal commands I found in forums that deleted some things but I still couldn’t install ka lite again.
Then I used the ka-lite-remover.sh script you guys suggested and it worked for me and allowed a reinstall without problem.
I think the problem was that I’d deleted the application folder as you’ve suggested and then I couldn’t do a proper uninstall. I’m learning now :)
Thanks, Kevin

On 11/04/2017, at 11:52 am, Cyril Pauya<EMAIL_ADDRESS>wrote:
Hi @benjaoming https://github.com/benjaoming - I did a back-read and it seems that Kevin did not do a clean uninstall as we documented at Uninstallation of the installed KA Lite package. https://github.com/learningequality/ka-lite-installers/tree/master/osx#uninstallation-of-the-installed-ka-lite-package.
Here's what he did:
...This stopped my ka lite working. I then deleted the KA-lite folder and contents from applications. Then I found a github page here that gave terminal commands to remove invisible .kalite folders from the system. I've done this...
I don't know if the "terminal commands" he mentioned were the ones in ka-lite-remover.sh.
The "normal" way to uninstall an app in macOS is to just drag it to the Trash. However since we did some customizations during setup, we created the ka-lite-remover.sh for a clean uninstall and renamed it as KA-Lite_Uninstall.tool https://github.com/learningequality/ka-lite-installers/blob/master/osx/post_installation.sh#L21 after a successful installation.
So there's no need to modify the Mac installer and we can just point users to the doc.
I think we can close this now. 😸
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/learningequality/ka-lite-installers/issues/446#issuecomment-293110792, or mute the thread https://github.com/notifications/unsubscribe-auth/AZvlhn56SV-5yPoERY30rpBKiPo0kutmks5rusDMgaJpZM4M2pph.

Thanks for verifying and I'm glad to hear it's working-out good for you @kevhyde.
I'm closing this now. 😸

So there's no need to modify the Mac installer and we can just point users to the doc how to do a clean uninstall.

Just to understand you clearly: If a user drags KA Lite to Trash (the conventional uninstall), will things break or not?

I can see that it's part of the official docs: http://ka-lite.readthedocs.io/en/develop/installguide/install_all.html#mac-osx  -- strange link, should probably separate the uninstall guides - this for now this is the link to the UNinstall :)

Hi @benjaoming

Just to understand you clearly: If a user drags KA Lite to Trash (the conventional uninstall), will things break or not?

Yes it is, It will break the uninstallation process.
Using the KA-Lite_Uninstall.tool will do the following:

Unset the environment variables: KALITE_PYTHON and KALITE_HOME.
Remove the .plist and preferences files, kalite executable and the ka-lite resources.
When run stand-alone, it confirms removal of the KA-Lite data directory as specified by the KALITE_HOME env var.

The installation process for the Mac OSX is outdated it should be updated. We will update it. Thank you for noticing it.


system.attribute defined in an assembly that is not referenced

so I think this is related to Windows 10's May 2018 cumulative update (three new KB's appeared in my update history, and I stripped my templates down to confirm the impact) - kb4131372 and kb4103727 are the prime candidates (the third update was for Adobe Flash).
I'm getting this error rather immediately when I try to compile/run my various cshtml's... usually the errors happen after a moment building the code.
the only attribute that I can find anywhere is RazorEngine's HasDynamicModelAttribute.
any ideas?

additionally, I hadn't changed the code prior to this error... I came back to my computer and it had rebooted.
I'm going to look at adding a reference during the build, which is an easy workaround... but also worth noting the issue in case anyone else experiences it.

so... wierdly enough, adding a reference to System.Runtime in MY app's app domain seemed to have solved the issue.
Since i'm doing this in PowerShell (which may be related to the updates causing it), it's just a quick call to System.Reflection.Assembly.Load (I use LoadWithPartialName to pull from the GAC, but a fully qualified should work too)


[3rdparty, document] Updated Documentation that covers performance tuning techniques for AMD Instinct GPUs.

Motivation
Updated Documentation that covers performance tuning techniques for AMD Instinct GPUs.
Modifications
Triton Kernels Optimization:

Detailed key environment variables such as num_stages, waves_per_eu, BLOCK_M, BLOCK_N, BLOCK_K, matrix_instr_nonkdim, and OPTIMIZE_EPILOGUE.
Provided example Triton kernel configurations with @triton.autotune decorator.
Torch Tunable Operations:
Explained the TunableOp feature in PyTorch and its relevance to SGLang.
Listed key environment variables: PYTORCH_TUNABLEOP_ENABLED, PYTORCH_TUNABLEOP_TUNING, and PYTORCH_TUNABLEOP_VERBOSE.
Included usage examples for enabling tuning and verbose logging.
Torch Compilation Enhancements:
Offered suggestions for optimizing GEMM and convolution operations using PyTorch's Inductor.
Highlighted key configurations like Max Autotune, Fine-Grained Control, Backend Selection, Freezing for Inference, and Debugging.
Provided example bash commands for different tuning scenarios.

Checklist

[O] Update documentation as needed, including docstrings or example tutorials.

@yichiche Thanks for the contribution. It is merged.


Symbolic link not created in /usr/bin in Ubuntu 18.04

What version of electron-installer-debian are you using?
v0.8.1
What version of node and npm are you using?
8.11.1 and 6.0.1
What operating system are you using?
Ubuntu 18.04
Can you compile the example app successfully?
yes
What did you do? Please include the configuration you are using for electron-installer-debian.
{
  "name": "test",
  "bin": "test",
  "userDataDir": "test",
  "productName": "test",
  "genericName": "test",
  "homepage": "https://test.com/",
  "icon": "res/dev/app.png",
  "section": "test",
  "categories": [
    "Network",
    "test"
  ],
  "mimeType": [
    "text/html",
    "text/xml",
    "application/xhtml_xml",
    "image/webp",
    "x-scheme-handler/http",
    "x-scheme-handler/https",
    "x-scheme-handler/ftp"
  ],
  "requires": [
    "GConf2",
    "libXScrnSaver",
    "lsb"
  ],
  "depends": [
    "gawk",
    "git",
    "gconf2",
    "gconf-service",
    "gvfs-bin",
    "libc6",
    "libcap2",
    "libgtk2.0-0",
    "libudev0 | libudev1",
    "libgcrypt11 | libgcrypt20",
    "libnotify4",
    "libnss3",
    "libxtst6",
    "libxss1",
    "python",
    "xdg-utils"
  ]
}

What did you expect to happen?
It should create a symbolic link in /usr/bin/myelectronapp
What actually happened?
No symbolic link created. But it was able to unpack the package in /usr/lib/myelectronapp

Can you please rerun the command, but prepend DEBUG=electron-installer-debian beforehand?

Okay will do. I'll be back.

I get this error DEBUG=electron-installer-debian --src osiris-linux-x64/ --dest dist/ --arch amd64 --config res/dev/linuxPackaging.json /bin/sh: 1: --src: not found

Run DEBUG=electron-installer-debian electron-installer-debian --src test-linux-x64/ --dest dist/ --arch amd64 --config res/dev/linuxPackaging.json

Thu, 16 Aug 2018 05:39:06 GMT electron-installer-debian Symlinking binary from ../lib/Osiris/osiris to /tmp/electron-118716-11332-bgzt9h.ns10w/Osiris_0.1.0_amd64/usr/bin/Osiris

Also, I'm confused why it's creating a symlink on build process. Shouldn't it be created when installing using sudo dpkg -i app.deb? Please enlighten me.

Set the bin option to whatever the customized Electron binary is named.

Also, I'm confused why it's creating a symlink on build process.

I'm not sure how it would know where the binary is. Also, adding a postinstall script by default would make it much more difficult to provide support for custom postinstall scripts.


Create Python Stone/Paper/Scissor Game

This is a stone paper game .

@Arindam200 Bro see now I have add it in project folder.
Bro If I am doing it wrong please help me how to do because I am new to this.

star this repo!
Keep contributing!

@Arindam200 thanks bro, I have given star.

@Arindam200 Bro I am new to this, will you help me in tutorial . How to contribute to projects in github and merge and all.

@Arindam200 bro it is showing excluded


Add note explaining Razor Pages property binding on GET

Fixes https://github.com/aspnet/Docs/issues/5657

@Rick-Anderson previously shot this one down. https://github.com/aspnet/Docs/issues/4655 :gun: lol

@guardrex In conversations with both @rynowak and @isaac2004 on Friday, it was recommended that we add this. In the past, I've also seen customers ask Damian how to do this. There's a need for it. If not in this doc, we should put it somewhere else.

Preach'in to the choir my friend. I opened #4655 because I wanted to do it.

I can see both sides too, but it's a problem if customers are going to a PM for the answer.

Or bothering people on the docs team :)

This absolutely needs to be part of the docs for the cases where folks want to need to use it. This is not a bad practice or something we tell users to avoid.

@rynowak  can we add something like:
Binding on Get is generally not required.
It would be nice to provide some background on why Get is excluded by default. Are there case where blindly adding binding on get is problematic? There must be a good reason it was excluded.
For example, you might need to add binding to Get when ...

@scottaddie  play the video:  @DamianEdwards explains risk and add those caveats.

@rynowak @Rick-Anderson Please take another look.


fix: dispose player implementation

Description
The implementation to dispose a player on the native side was missing for many platforms.
Checklist

[x] The title of my PR starts with a [Conventional Commit] prefix (fix:, feat:, docs:, chore: etc).
[x] I have read the [Contributor Guide] and followed the process outlined for submitting PRs.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
[x] I have updated/added relevant examples in [example].

Breaking Change

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Related Issues
See https://github.com/bluefireteam/audioplayers/issues/1467#issuecomment-1503685651

Yes, completely forgot about the dispose statement, which we didn't have before. So it should work as before after upgrading, but it's better for resources to be able to dispose the player, if not needed anymore.


Capability to load external resources in CLI config YAML files

We need to have cellarium.ml.transform.Filter to load filter_list from e.g. a text or csv file. This information is not in a checkpoint, so CheckpointField does not quite work. Perhaps we could unify CheckpointField and whatever this feature will generate into a same mechanism: loading a resource file (could be a pickled dictionary), caching it, and returning a specific key.

There turns out to be a very simple way to add things similar to CheckpointField using yaml tags and constructors (https://matthewpburruss.com/post/yaml/)
A general object loader could look like this:
@dataclass
class ObjectLoader:
    file_path: str
    loader_fn: Callable
    attr: Optional[str] = None
    convert_fn: Optional[Callable] = None

    def __new__(cls, file_path, loader_fn, attr, convert_fn):
        obj = loader_fn(file_path)
        if attr is not None:
            obj = getattr(obj, attr)
        if convert_fn is not None:
            obj = convert_fn(obj)
        return obj

Corresponding yaml file would look like this:
model:
  transforms:
    - class_path: cellarium.ml.transforms.ZScore
      init_args:
        meang_g:
          !ObjectLoader
          file_path: onepass_ckpt_path
          loader_fn: cellarium.ml.core.CellariumModule.load_from_checkpoint
          attr: mean_g
          convert_fn: null


fix: Add ignore rules for tfsec and correct remaining issues to ensure tfsec passes

What does this PR do?

Update tfsec to include ignore rules for common errors due to example usage. Notes have been added next to the rules for a brief explanation as to why in the tfsec.yaml file
Remove *.tfvars and instead rely on default variables to avoid warnings on tfsec
Fix various nits/issues raised by tfsec (security group descriptions, see individual ignore rules added within *.tf files
Bastion EC2 removed from AMG OpenSearch example. Looks like it was a local testing artifact but no path to pem file - if we need to add this back in we can add an EC2 with SSM Session Manager access instead of public facing instance and pem key

Motivation

Fix tfsec failed errors on CI

More

[ ] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[x] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

pre-commit will fail on tflint - this is already fixed in my other PR https://github.com/aws-ia/terraform-aws-eks-blueprints/pull/530/commits/1f61842e7bd801b962f954afb01c5dfbe68c17c4 so not re-adding here for duplication


Is Modal example oudated?

It seems like the modal example, located at https://vuejs.org/examples/modal.html is outdated for 2.0 or just broken. I could not find a way to make the close event work as is, and had to resort to setting the showModal to false in the button click.

It didn't close when you pressed the OK button?

yup

Could you share more information please? For example, what browser and operating system are you using? Are you seeing errors on the JavaScript console?

PS: Works fine here on Chrome, FF & IE 11

Closing due to lack of response.


Add Qgis 2.18.28

Hi!
Here in company, we still use qgis 2.18, due to some issues with Qgis 3.4/3.8.
It's possible add the last version 2.18.28 to the repository?

It's possible add the last version 2.18.28 to the repository?

Sure. If you send a PR adding it we can create a maintenance branch.
Closing this b/c it is a package request that requires a volunteer to do it. Not really a problem for the current team to address.

Have some tutorial to do this??
I want to volunteer.

If you are familiar with git/github and qgis build you can start with https://conda-forge.org/docs/maintainer/adding_pkgs.html


guided missiles

It would be awesome if we had some blocks that would allow us to launch guided missiles. Looking through some real-life examples, there is a ton of complexity behind this ecosystem. There's missiles pre-guidance via GPS or Radar, in-flight guidance or lack of, tons of types of on-missile guidance with different capabilities and weaknesses, lots of different sizes, payloads, cruising speeds, etc.
Furthermore, a lot of the real-life terminology doesn't quite apply since we're dealing with atmosphere and geographic coordinates a lot less often.
So I think we should take the most interesting parts of the current missile systems and distill them down into a simple but interesting  game system.
Here's my initial thoughts on how we could set it up:
Guided missile launcher
These are designed to be launched from a ship/base and destroy a fast-moving target. They are smaller and more maneuverable than ballistic missiles, with lower top speed, better acceleration, and less damage.

Tier I - launches straight ahead but will lock onto targets within small radius from its nose, high chance to be fooled by countermeasures
Tier II - can launch straight ahead or be guided by radar with lock-on, larger self-guidance radius, lower chance to be fooled by countermeasures, larger damage radius
Tier III - can launch straight ahead or be guided by radar with lock-on, faster lock-on, larger self-guidance radius, lowest chance to be fooled by countermeasures, same damage as Tier II (just better tracking)

Guided missile (electronic) countermeasure block
These are designed to scramble the tracking of guided missiles
Small ship and Large ship, tiers I & II
Ballistic missile launcher
These are designed to be launched from a ship/base and destroy a slow-moving or static high-value target a large distance away. They are larger and less maneuverable than ballistic missiles, with less acceleration and less accurate tracking, but a much higher top speed, greater damage, and immune to countermeasures (they must instead be intercepted). They do not track their targets once launched - they go to a static point determined from radar targeting. They are very expensive.

Tier I - "Ballistic missile" - fair acceleration, high top speed, large damage radius
Tier II - "ICBM" - lower acceleration, highest top speed, huge damage radius

Ballistic missile interceptor launcher
These are designed to be launched from a ship/base and destroy a very fast-moving, high-value target traveling in a predictable path (i.e. a ballistic missile). They are specially tuned to intercept ballistic missiles with a fair amount of accuracy and a large explosion radius.

Tier I - less maneuverable than guided missile but more than ballistic, fair top speed, medium explosion radius
Tier II - more maneuverable, faster, larger explosion radius

I think we could start with the guided missiles and countermeasures, as those will get the most use and be the easiest to balance. Then we could move on to long range ballistic missiles and their interceptors if that's even something people find valuable (it takes a looooong time to build stuff in this game right now, that much destructive potential could suck).

Sounds good, this should be ready in a day or two?
I would recommend looking at http://danikgames.com/blog/moving-target-intercept-in-3d/ if you have not already. It's for a constant velocity projectile but since you can adjust inflight it should work.

Well I was hoping the targeting could just use all the same functions already provided by radar and weapon control, with a little modification. But yes that little modification would probably end up taking a while.

Weapon Control and Keen's turrets use the same formula, which is the link I provided. It's a bit easier to understand on danikgames.com I think.

Gotcha, will check it out.

Still working on accuracy
https://www.youtube.com/watch?v=Y2Z6q2I7-Lg

That is crazy awesome. The first 30 seconds of that video is the coolest thing I've ever seen in SE modding history.
You have to post this on reddit, or let me.

I don't have reddit but you can go ahead. I might be able to add cluster missiles too.

https://www.reddit.com/r/spaceengineers/comments/3liryd/guided_missiles_coming_to_se_mods/

Cluster missiles would be very cool.
I love how you explode the missile with a rock, ingenious.

I love how you explode the missile with a rock, ingenious.

https://www.youtube.com/watch?v=U2iiPpcwfCA

Epic

I might drop cluster missile as I am not really happy with the way they turned out. If you have any suggestions for improving them, there is a test missile in https://github.com/Rynchodon/Autopilot/tree/Guided-Missile.

Cool, will check it out!

Working on a launcher for the cluster missiles.

Looking good. Could you upload what you have now so I can get started on modifying the script?

These are implemented and in-game. Good job guys! Closing this issue.


'minifyHtml.minify is not a function'

win22H2 "@minify-html/node": "^0.10.7"
import * as minifyHtml from "@minify-html/node"

const minified = minifyHtml.minify(
    Buffer.from("
  Hello, world!
"),
    {
        keep_spaces_between_attributes: true,
        keep_comments: true
    }
);

Thanks for raising, the import line should be:
import minifyHtml from "@minify-html/node"

This is a typo in the README example. It does work from TypeScript with ESModule interop enabled, but doesn't work from a module script, as the functions are actually placed in the default export as an object. I've updated the README now.

Previously I was getting the function resolved as I was hoovering on the method in vscode but it would not run it.
I have changed the code as you suggested and now I am getting another error. Are there other dependencies which I am not aware of? I am trying to use this tool in esbuild. plugin esbuild-html-css-loader is where I am running it from.
thread '<unnamed>' panicked at 'assertion failed: `(left == right)`
  left: `PendingException`,
 right: `Ok`', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.10.1\src\napi\error.rs:49:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
X [ERROR] internal error in Neon module: assertion failed: `(left == right)`
  left: `PendingException`,
 right: `Ok` [plugin esbuild-html-css-loader]

Upon first glance that looks like an upstream issue with the Neon library, can you raise an issue with them? If you can provide a sample HTML that triggers this, feel free to post it here and I'll try to reproduce and debug it from my end as well. Set RUST_BACKTRACE=1 to output a Rust stacktrace when this occurs.

Sure, I'll create a simple example. I haven't yet opened an issue at Neon, will wait for your response.
process.env['RUST_BACKTRACE'] = 'full'
return minifyHtml.minify(Buffer.from(`

        Next

`))

thread '<unnamed>' panicked at 'assertion failed: `(left == right)`
  left: `PendingException`,
 right: `Ok`', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.10.1\src\napi\error.rs:49:5
stack backtrace:
   0:     0x7fff51d21342 - napi_register_module_v1
   1:     0x7fff51d3245b - napi_register_module_v1
   2:     0x7fff51d1f8aa - napi_register_module_v1
   3:     0x7fff51d2108b - napi_register_module_v1
   4:     0x7fff51d230b9 - napi_register_module_v1
   5:     0x7fff51d22d3a - napi_register_module_v1
   6:     0x7fff51d23941 - napi_register_module_v1
   7:     0x7fff51d236cd - napi_register_module_v1
   8:     0x7fff51d21d6f - napi_register_module_v1
   9:     0x7fff51d23390 - napi_register_module_v1
  10:     0x7fff51d41475 - napi_register_module_v1
  11:     0x7fff51d317d4 - napi_register_module_v1
  12:     0x7fff51d403e0 - napi_register_module_v1
  13:     0x7fff51d19eb4 - napi_register_module_v1
  14:     0x7fff51c5114d - <unknown>
  15:     0x7fff51c52ced - napi_register_module_v1
  16:     0x7fff51c5225a - napi_register_module_v1
  17:     0x7fff51c52b93 - napi_register_module_v1
  18:     0x7ff6e4877100 - v8::internal::compiler::Instruction::Output
  19:     0x7ff6e528d35d - v8::internal::Builtins::code
  20:     0x7ff6e528cf69 - v8::internal::Builtins::code
  21:     0x7ff6e528d22c - v8::internal::Builtins::code
  22:     0x7ff6e528d090 - v8::internal::Builtins::code
  23:     0x7ff6e5371f81 - v8::internal::SetupIsolateDelegate::SetupHeap
  24:     0x7ff6e52f5894 - v8::internal::SetupIsolateDelegate::SetupHeap
  25:     0x7ff6e52f5894 - v8::internal::SetupIsolateDelegate::SetupHeap
  26:     0x7ff6e53299c3 - v8::internal::SetupIsolateDelegate::SetupHeap
  27:     0x7ff6e53c27b5 - v8::internal::SetupIsolateDelegate::SetupHeap
  28:     0x7ff6e531b0cc - v8::internal::SetupIsolateDelegate::SetupHeap
  29:     0x7ff6e52f3d9b - v8::internal::SetupIsolateDelegate::SetupHeap
  30:     0x7ff6e51be3ca - v8::internal::Execution::CallWasm
  31:     0x7ff6e51be4eb - v8::internal::Execution::CallWasm
  32:     0x7ff6e51bf29a - v8::internal::Execution::TryCallScript
  33:     0x7ff6e5197e6a - v8::internal::MicrotaskQueue::RunMicrotasks
  34:     0x7ff6e5197c0a - v8::internal::MicrotaskQueue::PerformCheckpointInternal
  35:     0x7ff6e48df288 - node::CallbackScope::~CallbackScope
  36:     0x7ff6e48df14e - node::CallbackScope::~CallbackScope
  37:     0x7ff6e4819fc7 - v8::base::CPU::has_fpu
  38:     0x7ff6e482ba51 - v8::internal::wasm::WasmCode::safepoint_table_offset
  39:     0x7ff6e4913c17 - uv_timer_stop
  40:     0x7ff6e49101bb - uv_async_send
  41:     0x7ff6e490f94c - uv_loop_init
  42:     0x7ff6e490faea - uv_run
  43:     0x7ff6e48deb15 - node::SpinEventLoop
  44:     0x7ff6e47e92c4 - std::basic_ios<char,std::char_traits<char> >::setstate
  45:     0x7ff6e486d058 - node::InitializeOncePerProcess
  46:     0x7ff6e486e895 - node::Start
  47:     0x7ff6e46874fc - CRYPTO_memcmp
  48:     0x7ff6e589fdd8 - v8::internal::compiler::ToString
  49:     0x7fff97d37614 - BaseThreadInitThunk
  50:     0x7fff986426a1 - RtlUserThreadStart

I have raised an issue at Neon.

Cross-posting the answer here: https://github.com/neon-bindings/neon/issues/959#issuecomment-1408619573
According to the source of minify-html the options object is required, but, the code provided is missing the 2nd argument. There's also a small error in the Rust when attempting to change the error message.
Let me know if there are any questions. Cheers!

Thanks @kjvalencik, I've updated the code to use cx.try_catch. Is this the preferred way of casting to a type, and using a different error message if it fails? I was thinking that cx.argument returns a pure Rust-like Result, but it sounds like it actually throws an exception (i.e. mutates internal state), so if there's a more idiomatic or faster way instead of try_catch please let me know.
@jimasun I've fixed the Node.js library to not cause the assertion failure panic in the latest version 0.10.8, please let me know if it works on your end. Note that the second object is a required parameter, which is declared as such in the TypeScript definitions.

Thank you, it works fine now and the error is clear about the second argument.
[ERROR] the second argument is not an object

Thanks @kjvalencik, it sounds like using try_catch is fine so I'll leave it as is. I appreciate your detailed clarification of the Neon API and helping us out here.

I would suggest to make the options optional since it is more clean rather than providing an empty {} object.


How implement cell like TimeSeparator but with more complex layout

I want create cell  that placed in horizontal center of chat (content of cell can changes)
    private func commonInit() {
        //panelView - colored background view with rounded corners
        self.panelView.add(subviews: [iconView, label])
        self.contentView.add(subviews: [panelView])
    }

    override func layoutSubviews() {
        super.layoutSubviews()

        let maxSize = self.contentView.bounds.size
        let iconViewBounds = CGRect(origin: CGPoint(x: VoipMessageCellUI.insets, y: VoipMessageCellUI.insets), size: VoipMessageCellUI.iconSize)

        let maxLabelSize = CGSize(width: maxSize.width - (iconViewBounds.maxX + VoipMessageCellUI.insets),
                                  height: maxSize.height - VoipMessageCellUI.insets * 2 )
        let labelSize = self.label.sizeThatFits(maxLabelSize)
        let labelOrigin = CGPoint(x: iconViewBounds.maxX + VoipMessageCellUI.insets, y: (maxSize.height - labelSize.height)/2)

        let labelBounds = CGRect(origin: labelOrigin, size: labelSize)

        self.iconView.bma_rect = iconViewBounds
        self.label.bma_rect = labelBounds

        let panelSize = CGSize(width: labelBounds.maxX + VoipMessageCellUI.insets, height: maxSize.height)
        let panelBounds = CGRect (origin: CGPoint(x: (maxSize.width - panelSize.width), y: 0), size: panelSize )

        self.panelView.bma_rect = panelBounds
        self.panelView.center = self.contentView.center
// Code below i comment/uncomment withouth success
//        self.panelView.layoutSubviews()
//
//        self.panelView.bma_rect = panelBounds
//        self.panelView.center = self.contentView.center
    }

Some times after refreshing panelView.bounds become zero (((

Hey,
Did you find a way to do that ?


PX4 SITL hangs on error instead of exiting with error

For the case where for instance the tool ant is not installed, PX4 SITL just seems to hang instead of exiting with an error. Only after pressing Ctrl+C twice, we are finally exited.
...
[100%] Built target px4
SITL ARGS
sitl_bin: /home/julianoes/src/Firmware/build/px4_sitl_default/bin/px4
debugger: none
program: jmavsim
model: none
src_path: /home/julianoes/src/Firmware
build_path: /home/julianoes/src/Firmware/build/px4_sitl_default
empty model, setting iris as default
SITL COMMAND: "/home/julianoes/src/Firmware/build/px4_sitl_default/bin/px4" "/home/julianoes/src/Firmware"/ROMFS/px4fmu_common -s etc/init.d-posix/rcS -t "/home/julianoes/src/Firmware"/test_data
INFO  [px4] Creating symlink /home/julianoes/src/Firmware/ROMFS/px4fmu_common -> /home/julianoes/src/Firmware/build/px4_sitl_default/tmp/rootfs/etc
0 WARNING: setRealtimeSched failed (not run as root?)

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
/home/julianoes/src/Firmware/Tools/jmavsim_run.sh: line 61: ant: command not found
  SYS_AUTOSTART: curr: 0 -> new: 10016
  ...
  PWM_MIN: curr: 1000 -> new: 1075
INFO  [dataman] Unknown restart, data manager file './dataman' size is 11405132 bytes
INFO  [simulator] Waiting for simulator to connect on TCP port 4560
^CERROR [px4] Startup script returned with return value: 2
pxh>
Exiting...
pxh> Shutting down
/home/julianoes/src/Firmware/Tools/sitl_run.sh: line 164: kill: (22035) - No such process
make[4]: *** [platforms/posix/CMakeFiles/jmavsim.dir/build.make:57: platforms/posix/CMakeFiles/jmavsim] Error 1
make[3]: *** [CMakeFiles/Makefile2:20576: platforms/posix/CMakeFiles/jmavsim.dir/all] Interrupt
make[2]: *** [CMakeFiles/Makefile2:20583: platforms/posix/CMakeFiles/jmavsim.dir/rule] Interrupt
make[1]: *** [Makefile:6346: jmavsim] Interrupt
make: *** [Makefile:171: px4_sitl_default] Interrupt

I hate this bot.


no settings icon

I have gone through the content of icons available and was unable to find settings icon. It would be a good idea to get that implemented into the list of icons available.

I agree, a gear icon would be awesome.

Just found out, that there is a cog icon


Add source field to SecuLog & Bump version to 0.15.1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/ingest/log.rs
0.00% <ø> (ø)

:loudspeaker: Thoughts on this report? Let us know!


fixed regkey examples

fixed quotes, blanks and added dword example value.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@adeejoseph PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Improve transaction status feedback from wallet

Story
As a user
I want to see what node the transaction was sent to and track it's progress (success/failure) when submitting transactions via the desktop wallet
So that I can understand the status
Recording
https://user-images.githubusercontent.com/46783148/214906347-9f31385e-af3b-40dd-8d21-28df6fd03e99.mov
Tasks

[ ] Identify transaction types and feedback available (conversation with Botond, Valentine?)
[ ] Work out the ideal flow from / in wallet and/or to block explorer...
[ ] Team and stakeholder review
[ ] Visual Design
[ ] Team review
[ ] Etc.

Acceptance Criteria

[ ] I can
[ ] I can
[ ] I can

Sketch
From the Miro board:

Additional details / background info

Child tickets:

https://github.com/vegaprotocol/vegawallet-desktop/issues/487
https://github.com/vegaprotocol/vegawallet-desktop/issues/488
https://github.com/vegaprotocol/vegawallet-desktop/issues/489

On Friday 10th, @notbot00, @ValentinTrinque and I met to review the proposed routes. We agreed to pursue option 2 (toasts) AND option 3 (transaction history view), in addition to changes to the transaction details modal.
I have created tickets for those three tasks. I don't think there are any dependencies, they could be completed in any order.


merge() with how="cross" does not work

What happened:
Running dd.merge(left, right, how="cross") fails with
MergeError: Can not pass on, right_on, left_on or set right_index=True or left_index=True

What you expected to happen:
Minimal Complete Verifiable Example:
left = pd.DataFrame(
    {
        "key": ["K0", "K1", "K2", "K3"],
        "A": ["A0", "A1", "A2", "A3"],
        "B": ["B0", "B1", "B2", "B3"],
    }
)
right = pd.DataFrame(
    {
        "key": ["K0", "K1", "K2", "K3"],
        "A": ["C0", "C1", "C2", "C3"],
        "B": ["D0", "D1", "D2", "D3"],
    }
)
dd.merge(left, right, how="cross")

Anything else we need to know?:
Environment:

Dask version: '2021.09.0'
Python version: 3.7.10
Operating System: MacOS
Install method (conda, pip, source): pip

Hi @johanbog for what I'm reading in the docs the reason why dd.merge() with how="cross" does not work, it's because it's not supported. dd.merge documentation
merge source code
If what you want is a feature request, you might want to open an issue requesting this feature.

In the meantime we could raise a clearer exception.

@jsignell that sounds like a great idea. I can take a crack at that but I have few questions
Looking at the code where merge is defined more explicitly here https://github.com/dask/dask/blob/9f0b00f039a7775dccccffe59d6802468508d9f7/dask/dataframe/core.py#L4614-L4634
Should the raise go in the definition in .multi, like somewhere in here?
https://github.com/dask/dask/blob/9f0b00f039a7775dccccffe59d6802468508d9f7/dask/dataframe/multi.py#L466
probably right before https://github.com/dask/dask/blob/9f0b00f039a7775dccccffe59d6802468508d9f7/dask/dataframe/multi.py#L496
Would that be a good place?

Cool! Yeah I think it should go in multi right above the line that you are pointing to.


Change Dockerfile name in root of repo

Describe the Bug
The Dockerfile at the root of the Bolt repo is used for bolt-server. Users who stumble on the Bolt repo and expect that file to build an image that includes Bolt don't expect a testing container used for bolt-server. See https://github.com/puppetlabs/tasks-playground/issues/12
To do
Rename the Dockerfile (and maybe move it) for clarity of it's purpose.

Notes: Ping Morgan about the Distelli pipelines this might affect.

Currently Travis is configured to push a bolt-server image to PCR internal https://pcr-internal.puppet.net/pe-and-platform/repositories/bolt-server with https://github.com/puppetlabs/bolt/blob/master/scripts/deploy.sh which uses this Dockerfile. Part of this work should include evaluating  if that is needed any longer or if it needs to be published somewhere else with a different pipeline.

It appears that the bolt-server is used in orchestrator CI. https://github.com/puppetlabs/orchestrator/blob/4ef187220b690b70875161d54b9720585179a757/test-resources/docker-compose-linux.yml

So is pupperware. Putting up a PR now


Docs: fix missing backtick

Add missing backtick in Redis code example docs: fix missing backtick Test #338

View rendered docs/configuration.md

This is the same change as https://github.com/probot/probot/pull/1523.  Reported to GitHub.


PMID:15210864

decreased protein level during meiotic interphase
normal spore germination frequency
delayed first meiotic nuclear division
normal meiosis I progression (timing of meiosis I is normal)

decreased protein level during meiotic cell cycle FYPO:0004991
decreased protein level during meiotic interphase FYPO:0004992
normal spore germination frequency FYPO:0004993
delayed meiosis I FYPO:0004994
normal onset of meiosis I FYPO:0004995
I did the last one as "onset" to parallel the way I've defined "delayed"

edit file: 6adc5c7b7a97cd970a52f947b6202ff47111b8f7
release: 9615de7a68bece38aa177aaedef1da62debe40c9


Test: sandbox ready splash screen

Refs #122828

[x] anyOS @kieferrm
[x] anyOS @alexdima

Complexity: 2
Create Issue

The code responsible to rendering a splashscreen before the workbench UI appears was rewritten to be sandbox ready.
Test:

when you start VSCode (not in fullscreen) or reload the window you briefly see the layout as a shape reflecting the sidebar width and editor size as it was left (see screenshot below)
change your theme from light to dark or vice versa and verify the splash is also reflecting this (might require a few seconds after changing the theme to persist due to debouncing)

Works as expected.  It seems to me that the splash screen now is rendering noticeably faster (at least on my Windows machine) which makes the effect more pronounced. Nice work!

Oh nice 👍


‘DELETE’ does not have an automatic prompt，but ‘CREATE’，‘INSERT’... has

Describe the bug
My English is terrible.
When I enter 'D', "DELETE" is not automatically completed.
When I enter 'C', "CREATE" is automatically completed

To Reproduce
Steps to reproduce the behavior:

Connect database
input sql： d

Expected behavior
"DELETE" should be prompted
Screenshots

Desktop (please complete the following information):

SQLTools Version: v0.24.0
VS Code Version: v1.71.0
OS: Windows 10
Driver:

[ ] MySQL/MariaDB

Additional context
When I enter 'd', it automatically prompt "DESCRIBE" and "DROP", no "DELETE"

This is caused by an issue in a component we use:
https://github.com/cloudera/hue/issues/2983

I see, thank you

这是由我们使用的组件中的问题引起的：
cloudera/hue#2983
I see, thank you

@gjsjohnmurray I saw your PR on hue repo. I'm wondering if in the mean time we could release using a git package install on the package.json. what do you say?

@mtxr based on https://github.com/cloudera/hue/issues/2983#issuecomment-1304006283 maybe it's worth waiting a month or two. But if you prefer to go ahead sooner I'll be happy to review a PR.


Optionally hide OwnershipCard relation toggle

Signed-off-by: Andre Wanlin<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Provides the ability to hide the relations toggle on the OwnershipCard as well as setting a default relation type
Current State

Hidden Toggle

Relation Type of Aggregated with Toggle Hidden

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks! :tada:

Another big thanks @benjdlambert :)


Remove workspace pvc for container builds except FBC builds

Resolves the PVC errors.
PVC is not needed for TA pipelines

/lgtm


add e2e test for metric api scaler with all possible authentication

API authentication was introduced in this PR https://github.com/kedacore/keda/pull/1137. We need to add e2e tests for this.

@zroubalik I am starting with this :)


chore(deps): update dependency cypress to v3.8.1

This PR contains the following updates:

Package
Type
Update
Change

cypress
devDependencies
patch
3.8.0 -> 3.8.1

Release Notes

cypress-io/cypress
v3.8.1
Compare Source
Released 12/26/2019
Bugfixes:

We fixed a bug where cypress run --headless would not run Chrome-family browsers headlessly. Fixes #5949.
We fixed an issue where, on some systems with IPv4 and IPv6 enabled, Cypress would fail to connect to the Chrome DevTools Protocol while launching Chrome, leading to test failures. Fixes #5912.
The strict cookie validation added in 3.5.0 for cy.setCookie(), cy.clearCookie(), and cy.getCookie() has been removed. Fixes #5642.
We fixed a regression in 3.8.0 where using .type() on number inputs to type non-number characters or the {enter} special character would not type the correct value. Fixes #5968 and #5997.
Configuration values set from the plugin file now display with the correct background color in the Configuration panel in the Test Runner Settings. Fixes #6024.
We removed the 'Me' and 'An Organization' selections in the Test Runner when setting up a project to more closely match the Dashboard UI. This also fixes an edge case where a user with no default organizations could potentially be unable to set up a project. Fixes #5954.

Misc:

We updated the fallback error message for visibility checks to be less confusing. Addresses #5982.
The type definitions for cy.location() have been improved. Addresses #5574.

Dependency Updates:

Upgraded get-port from 5.0.0 to 5.1.0. Addressed in #6004.
Upgraded chrome-remote-interface from 0.28.0 to 0.28.1. Addressed in #6008.
Upgraded which from 1.3.1 to 2.0.2. Addressed in #6017.
Upgraded ansi_up from 1.3.0 to 4.0.3. Addressed in #4331.
Upgraded jimp from 0.6.4 to 0.9.3. Addressed in #4331.

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

:tada: This PR is included in version 2.153.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Issue With Bootstrap 4 : Months Calendar Box is showing vertical

My calendar is not showing as per example horizontal monthly view... all months calendar box showing vertical... please help snapshot below.
Code

 $(function () {
            var currentYear = new Date().getFullYear();
            $('#calendar').calendar({
                allowOverlap: true,
                displayWeekNumber: true,
                enableContextMenu: true,
                enableRangeSelection: true,
                minDate: new Date(2019, 01, 10),
                maxDate: new Date(2019, 12, 31),
                roundRangeLimits: true,
            })
    });

Hi, currently this plugin is not adapted for BS4, if not wrong there´re some repos that have it, reference to #170


Allow changing EnableUnfocusedAcrylic at runtime when UseAcrylic is true in Focused and Unfocused Appearance

Summary of the Pull Request
Closes #15943
References and Relevant Issues
#15943
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed
PR Checklist

[ ] Closes #15943
[ ] Tests added/passed
[ ] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[ ] Schema updated (if necessary)

I am strict about commit messages (and pull request titles!) because the way I write change logs means I read a lot of them.
I often look at the repository like this:

Each line is the title of a pull request :smile:
I often tell people to read this blog post as a style guide: https://cbea.ms/git-commit/

Thanks for doing this!
Before I merge it, can you change the title to explain the change in brief?
Rather than "Fix bug 1234", it is easier to read if it is like (for example) "Evaluate the numbers before displaying them". It makes it so you can get a good idea of the code change without having to look at another bug ID.

@DHowett
You think it's valuable for every PR even if it's very small/ low priority to have a title that explains the change in brief?
I thought because it was such a small fix and like something I left out of https://github.com/microsoft/terminal/pull/15923 I didn't need to get into detail too much hence I left out extensive documentation and the title.

Rather than "Fix bug 1234", it is easier to read if it is like (for example) "Evaluate the numbers before displaying them". It makes it so you can get a good idea of the code change without having to look at another bug ID.

Thanks for letting me know how it helps you!
And the resources of "How to Write a Git Commit Message"

I am strict about commit messages (and pull request titles!) because the way I write change logs means I read a lot of them.

What is a change log, can you give me a link to your last change log? I'd like to see it.  I guess it's like a summary of what has been changed in the terminal in a certain timeframe, maybe between each new version that will be released?

@DHowett
Btw I updated the Title , not sure whether this is good or too short.
I'd choose this because it's very clear and not sure how to make it more concise without losing clarity.
Would "Fix bug when changing EnableUnfocusedAcrylic at runtime" be better? It's more concise, but less clear about the specifics of the bug. Let me know what's easier for you when writing your change log

@DHowett
I Updated the title, what would you rather have?
This: "Fixed bug when changing EnableUnfocusedAcrylic at runtime"
or this: "Allow changing EnableUnfocusedAcrylic at runtime when UseAcrylic is true in Focused and Unfocused Appearance"

You think it's valuable for every PR even if it's very small/ low priority to have a title that explains the change in brief?

Yup, I do! If every change can be summarized in a single short line, it becomes easier for the project maintainer to read.
When I say changelog, I mean my release notes. I start with a list of all commits and reword them one by one to explain the user-facing impact, and add a "thank you" note for the contributor!
This is our last really big changelog: https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0
The new title is perfectly fine, thank you for doing it! I'll sign off and approve your change now. :smile:


Temp file

done

@Ajaypawar02, why are you trying to merge all of your personal code into the official Animated Drawings repo? Was this PR a mistake?

hello,
Currently i am working on this repo.I am getting Bus error(core dumped) or
segmented error (code dumped)
can you please check the mesa_view.py folder
getting error in _initialize_shader().
i am getting this error whenever i am making USE_MESA: True
Thank You
On Thu, 22 Jun, 2023, 2:00 am hjessmith, @.***> wrote:

Closed #195
https://github.com/facebookresearch/AnimatedDrawings/pull/195.
—
Reply to this email directly, view it on GitHub
https://github.com/facebookresearch/AnimatedDrawings/pull/195#event-9599012555,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTSMKYQ5V6SQNRQ23C6HW3XMNKX3ANCNFSM6AAAAAAZPGC3NQ
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Sanitized crack

Pulled hashes from one of my e-commerce sites

Congrats! Contact me at<EMAIL_ADDRESS>


Alter redirect after register

Description

Alter the redirect after register from home to log in (in seeker
registration and owner registration).

Manual Tests

I registered as a new user and saw that I was redirected to the login page.

Issues closed by this PR
Fix #169

LGTM


SSO!

Work in progress

Got it rebased w/ entitlement changes and redirect URL updated (CIAM team updated the format).


Dependencies updates

Hello,
In my opinion, all dependencies are very common and/or lightweight, except datashader which requires dask/xarray/pillow among others. Since it is used in only one plot function, should we moved this inside an extra dependency? If someone runs scatter_density without datashader installed, we could log an error explaining how to install the extra.
Alternatively, instead of throwing an error, we could also plot a subset of cells if datashader is not installed and add a warning like "Cells are subset. To show all cells, install datashader with 'pip install pytometry[performance]'"
But maybe you plan to implement other plot functions with datashader? In that case, I agree that it would be really preferable to keep it in the main dependencies. What do you think @mbuttner, @grst?
Also, what about moving nbproject in the dev dependencies? Is there a reason to have this in the main dependencies?

Hi @quentinblampey
thank you for your suggestions! I agree with the suggestion to move the datashader package inside an extra dependency for the plotting library and only display subsets of cells with a corresponding warning message.
I am personally very keen at showing all cells wherever possible, which poses quite a challenge in flow cytometry and CYTOF. However, let me stress the importance of having a lightweight package first and extend the visualization functionality second. We can still discuss how to integrate the plotting functions at a later stage.

If scatter_density is the only function that requires datashader, I think we can follow @ivirshup's suggestion to get rid of it altogether and replace it with np.histogram2d (see https://github.com/scverse/governance/issues/64#issuecomment-2051856781).
UMAPs/embeddings with millions of cells are also slow with matplotlib and can benefit from datashader (with categorical data it's not as trivial as to use histogram2d). But for embeddings, in my experience, there's not a lot to gain from showing all cells vs. subsampling. Plus any performance uprades for sc.pl.umap should probably be solved on the scanpy side.

About nbproject: It is currently used for the testing of notebooks of the package, so I suggest to keep it.

Thanks @grst, I'll try the np.histogram2d solution and do a PR if it looks promising.
Concerning nbproject, if it's used only for testing, then we can move it to the "test" dependencies, right?

Concerning nbproject, if it's used only for testing, then we can move it to the "test" dependencies, right?

I think there should be an additional group docs with all the packages required to run the tutorial, including nbproject.

Closed as completed.


Identity credential unavailable error non json imds

To close #35938

API change check
API changes are not detected in this pull request.


Remove old updateReleaseInfo parameter

Why are the changes needed?

Remove old updateReleaseInfo parameter:

Intelij Idea display error msg.
https://github.com/apache/maven-deploy-plugin/pull/4

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #1098 (7ed3229) into master (9dfbd2b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1098   +/-   ##
=========================================
  Coverage     78.80%   78.80%
  Complexity       80       80
=========================================
  Files           175      175
  Lines          6451     6451
  Branches        764      764
=========================================
  Hits           5084     5084
  Misses          923      923
  Partials        444      444

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 9dfbd2b...7ed3229. Read the comment docs.

thanks, merging to master