My Project cannot access ginkgo library

Hello everyone!!! I am a newbie using ginkgo library. I have run the examples but I have some problem when I create a new program. Web tutorials only focus on code but not the steps to create a program. I try creating a cpp file and running the code (https://github.com/ginkgo-project/ginkgo/wiki/Tutorial-2:-Implement:-Matrices) but it did not work. It supported: fatal error: ginkgo/ginkgo.hpp: No such file or directory #include <ginkgo/ginkgo.hpp> . Thank you!!!

Unfortunately, our tutorials skip over some important steps to set up the build environment, most importantly

If you have Ginkgo installed (make install) on your system, you need to specify the include/ path of your installation prefix (-Ipath/include) that you potentially set using -DCMAKE_INSTALL_PREFIX=path (the default value is /usr/local on Linux). If Ginkgo is not installed, you need to specify the both the path to ginkgo/include and ginkgo/build/include or which ever folder you called cmake from.
You need to link to the Ginkgo libraries. For this, you need to set the library path -Lpath/lib again based on the installation prefix, and explicitly link to the libraries like -lginkgo -lginkgo_reference ... for all executors that you compiled. If Ginkgo is not installed, you need to manually copy the library files (libginkgo*.so*) to a common directory and reference this directory both as a linking path with -L as well as an -rpath if you built Ginkgo with shared libraries (which is the default).

You can see how this works in the build.sh files in examples/
Either way, I cannot recommend using CMake enough, as it takes care of almost all issues for you. But still, we will update the tutorials to reflect the build setup in more detail.

I am sorry to bother you but I do not understand that way. I have ubuntu 18.04. I installed ginkgo on your system. I can access ginkgo in terminal: cd ginkgo. I have run all examples in build/examples and all is ok.
for example: my name program: "test" belongs to desktop. I access my program in terminal: cd Desktop/test. In directory test, I have the file: main.cpp. I try running main.cpp something like: "g++ main.cpp -o main" and it has error because it understands ginkgo library. So how can I fix the link to the ginkgo libraries?

By installed, do you mean you executed sudo make install successfully? Is ginkgo.hpp present in /usr/include/ginkgo/?
At the very least, you have to link to the Ginkgo shared libraries.
g++ main.cpp -o main -lginkgo -lginkgo_reference -lginkgo_omp -lginkgo_cuda -lginkgo_hip

When I execute: "sudo make install", it reported: "make: *** No rule to make target 'install'.  Stop." ... ginkgo directory does not exist in /usr/local/include

Are you executing sudo make install in the build directory in ginkgo? Did you successfully follow the steps from the first tutorial to configure and compile Ginkgo?

Yes, I do all. I also run all the examples. Do you have teamviewer? you can access my computer and try it. Thank you about this!

And on my first question:

Are you executing sudo make install in the right directory?
What is the output when you just run make?
Is there a Makefile present in the ginkgo/build directory

I executed in build directory.
do you mean: run main.cpp by make something like: make main.cpp ?
Yes

No, I mean just executing make without any parameters

the output:
[  0%] Built target ginkgo_hip_device
[  1%] Built target ginkgo_hip
[  1%] Built target ginkgo_cuda_device
[  9%] Built target ginkgo_cuda
[  9%] Built target ginkgo_omp_device
[ 15%] Built target ginkgo_omp
[ 15%] Built target ginkgo_reference_device
[ 21%] Built target ginkgo_reference
[ 29%] Built target ginkgo
[ 29%] Built target cuda_test_base_exception_helpers
[ 30%] Built target cuda_test_base_math
[ 31%] Built target cuda_test_base_cuda_executor
[ 31%] Built target cuda_test_components_merging_kernels
[ 31%] Built target cuda_test_components_sorting_kernels
[ 31%] Built target cuda_test_components_prefix_sum
[ 32%] Built target cuda_test_components_precision_conversion
[ 33%] Built target cuda_test_components_cooperative_groups_kernels
[ 34%] Built target cuda_test_components_searching_kernels
[ 34%] Built target cuda_test_components_fill_array
[ 35%] Built target cuda_test_factorization_par_ilut_kernels
[ 35%] Built target cuda_test_factorization_par_ict_kernels
[ 36%] Built target cuda_test_factorization_ilu_kernels
[ 36%] Built target cuda_test_factorization_par_ilu_kernels
[ 37%] Built target cuda_test_matrix_csr_kernels
[ 38%] Built target cuda_test_matrix_hybrid_kernels
[ 38%] Built target cuda_test_matrix_coo_kernels
[ 38%] Built target cuda_test_matrix_dense_kernels
[ 38%] Built target cuda_test_matrix_ell_kernels
[ 38%] Built target cuda_test_matrix_sellp_kernels
[ 39%] Built target cuda_test_preconditioner_isai_kernels
[ 39%] Built target cuda_test_preconditioner_jacobi_kernels
[ 39%] Built target cuda_test_solver_cg_kernels
[ 39%] Built target cuda_test_solver_bicg_kernels
[ 39%] Built target cuda_test_solver_cgs_kernels
[ 39%] Built target cuda_test_solver_gmres_kernels
[ 40%] Built target cuda_test_solver_ir_kernels
[ 40%] Built target cuda_test_solver_lower_trs_kernels
[ 40%] Built target cuda_test_solver_upper_trs_kernels
[ 41%] Built target cuda_test_solver_fcg_kernels
[ 42%] Built target cuda_test_solver_bicgstab_kernels
[ 42%] Built target cuda_test_stop_residual_norm_kernels
[ 43%] Built target cuda_test_stop_criterion_kernels
[ 43%] Built target cuda_test_utils_assertions_test
[ 43%] Built target core_test_base_types
[ 44%] Built target core_test_base_sanitizers
[ 45%] Built target core_test_base_utils
[ 45%] Built target core_test_base_range
[ 46%] Built target core_test_base_polymorphic_object
[ 46%] Built target core_test_base_allocator
[ 47%] Built target core_test_base_combination
[ 48%] Built target core_test_base_dim
[ 48%] Built target core_test_base_array
[ 48%] Built target core_test_base_extended_float
[ 48%] Built target core_test_base_perturbation
[ 48%] Built target core_test_base_exception
[ 48%] Built target core_test_base_version
[ 48%] Built target core_test_base_exception_helpers
[ 49%] Built target core_test_base_abstract_factory
[ 50%] Built target core_test_base_executor
[ 50%] Built target core_test_base_iterator_factory
[ 50%] Built target core_test_base_composition
[ 51%] Built target core_test_base_lin_op
[ 51%] Built target core_test_base_math
[ 51%] Built target core_test_base_range_accessors
[ 52%] Built target core_test_base_matrix_data
[ 52%] Built target core_test_base_mtx_io
[ 53%] Built target core_test_factorization_par_ilut
[ 53%] Built target core_test_factorization_par_ilu
[ 53%] Built target core_test_log_logger
[ 53%] Built target core_test_log_stream
[ 53%] Built target core_test_log_convergence
[ 54%] Built target core_test_log_record
[ 54%] Built target core_test_matrix_hybrid
[ 54%] Built target core_test_matrix_dense
[ 54%] Built target core_test_matrix_identity
[ 55%] Built target core_test_matrix_coo
[ 56%] Built target core_test_matrix_permutation
[ 57%] Built target core_test_matrix_ell
[ 57%] Built target core_test_matrix_coo_builder
[ 57%] Built target core_test_matrix_sparsity_csr
[ 57%] Built target core_test_matrix_sellp
[ 57%] Built target core_test_matrix_csr
[ 58%] Built target core_test_matrix_csr_builder
[ 58%] Built target core_test_preconditioner_isai
[ 59%] Built target core_test_preconditioner_ilu
[ 60%] Built target core_test_preconditioner_jacobi
[ 61%] Built target core_test_solver_cg
[ 61%] Built target core_test_solver_cgs
[ 62%] Built target core_test_solver_gmres
[ 62%] Built target core_test_solver_ir
[ 62%] Built target core_test_solver_bicgstab
[ 63%] Built target core_test_solver_lower_trs
[ 63%] Built target core_test_solver_upper_trs
[ 63%] Built target core_test_solver_fcg
[ 63%] Built target core_test_solver_bicg
[ 64%] Built target core_test_stop_iteration
[ 64%] Built target core_test_stop_combined
[ 64%] Built target core_test_stop_time
[ 64%] Built target core_test_stop_stopping_status
[ 65%] Built target core_test_utils_assertions_test
[ 65%] Built target core_test_utils_matrix_generator_test
[ 65%] Built target reference_test_base_composition
[ 65%] Built target reference_test_base_combination
[ 66%] Built target reference_test_base_perturbation
[ 66%] Built target reference_test_components_precision_conversion
[ 66%] Built target reference_test_components_fill_array
[ 67%] Built target reference_test_components_prefix_sum
[ 68%] Built target reference_test_factorization_par_ilu_kernels
[ 68%] Built target reference_test_factorization_par_ict_kernels
[ 68%] Built target reference_test_factorization_par_ilut_kernels
[ 68%] Built target reference_test_log_convergence
[ 68%] Built target reference_test_matrix_hybrid_kernels
[ 69%] Built target reference_test_matrix_ell_kernels
[ 69%] Built target reference_test_matrix_permutation
[ 70%] Built target reference_test_matrix_identity
[ 71%] Built target reference_test_matrix_coo_kernels
[ 71%] Built target reference_test_matrix_csr_kernels
[ 71%] Built target reference_test_matrix_dense_kernels
[ 71%] Built target reference_test_matrix_sparsity_csr_kernels
[ 71%] Built target reference_test_matrix_sellp_kernels
[ 72%] Built target reference_test_matrix_sparsity_csr
[ 73%] Built target reference_test_preconditioner_isai_kernels
[ 73%] Built target reference_test_preconditioner_ilu
[ 73%] Built target reference_test_preconditioner_jacobi
[ 74%] Built target reference_test_preconditioner_jacobi_kernels
[ 75%] Built target reference_test_solver_gmres_kernels
[ 76%] Built target reference_test_solver_lower_trs
[ 76%] Built target reference_test_solver_cgs_kernels
[ 77%] Built target reference_test_solver_cg_kernels
[ 77%] Built target reference_test_solver_bicg_kernels
[ 77%] Built target reference_test_solver_fcg_kernels
[ 77%] Built target reference_test_solver_bicgstab_kernels
[ 77%] Built target reference_test_solver_lower_trs_kernels
[ 77%] Built target reference_test_solver_upper_trs
[ 78%] Built target reference_test_solver_upper_trs_kernels
[ 78%] Built target reference_test_solver_ir_kernels
[ 79%] Built target reference_test_stop_criterion_kernels
[ 79%] Built target reference_test_stop_combined
[ 79%] Built target reference_test_stop_iteration
[ 79%] Built target reference_test_stop_residual_norm_kernels
[ 80%] Built target reference_test_stop_time
[ 80%] Built target reference_test_utils_assertions_test
[ 80%] Built target omp_test_components_precision_conversion
[ 80%] Built target omp_test_components_prefix_sum
[ 81%] Built target omp_test_components_fill_array
[ 81%] Built target omp_test_factorization_par_ilu_kernels
[ 82%] Built target omp_test_factorization_par_ict_kernels
[ 82%] Built target omp_test_factorization_par_ilut_kernels
[ 82%] Built target omp_test_matrix_sparsity_csr_kernels
[ 82%] Built target omp_test_matrix_csr_kernels
[ 82%] Built target omp_test_matrix_ell_kernels
[ 83%] Built target omp_test_matrix_coo_kernels
[ 84%] Built target omp_test_matrix_dense_kernels
[ 84%] Built target omp_test_matrix_hybrid_kernels
[ 85%] Built target omp_test_matrix_sellp_kernels
[ 85%] Built target omp_test_preconditioner_isai_kernels
[ 86%] Built target omp_test_preconditioner_jacobi_kernels
[ 86%] Built target omp_test_solver_gmres_kernels
[ 86%] Built target omp_test_solver_cgs_kernels
[ 86%] Built target omp_test_solver_cg_kernels
[ 86%] Built target omp_test_solver_ir_kernels
[ 87%] Built target omp_test_solver_fcg_kernels
[ 87%] Built target omp_test_solver_bicg_kernels
[ 88%] Built target omp_test_solver_bicgstab_kernels
[ 88%] Built target omp_test_solver_upper_trs_kernels
[ 89%] Built target omp_test_solver_lower_trs_kernels
[ 89%] Built target omp_test_stop_residual_norm_kernels
[ 90%] Built target omp_test_stop_criterion_kernels
[ 91%] Built target custom-logger
[ 92%] Built target custom-matrix-format
[ 92%] Built target custom-stopping-criterion
[ 92%] Built target adaptiveprecision-blockjacobi
[ 92%] Built target ginkgo-overhead
[ 92%] Built target ginkgo-ranges
[ 92%] Built target ilu-preconditioned-solver
[ 93%] Built target ir-ilu-preconditioned-solver
[ 93%] Built target inverse-iteration
[ 93%] Built target iterative-refinement
[ 93%] Built target minimal-cuda-solver
[ 94%] Built target mixed-precision-ir
[ 94%] Built target nine-pt-stencil-solver
[ 94%] Built target performance-debugging
[ 95%] Built target poisson-solver
[ 95%] Built target preconditioned-solver
[ 95%] Built target simple-solver
[ 96%] Built target simple-solver-logging
[ 96%] Built target three-pt-stencil-solver
[ 97%] Built target twentyseven-pt-stencil-solver
[ 97%] Built target make_run_all_benchmarks
[ 97%] Built target conversions
[ 98%] Built target matrix_generator
[ 98%] Built target matrix_statistics
[ 99%] Built target preconditioner
[ 99%] Built target solver
[100%] Built target spmv

To be honest, I have no idea why sudo make install would not work, since CMake always provides an install target for the Makefile. Can you try again and if it doesn't work, post the contents of your CMakeCache.txt file in here?

WWOWW. "sudo make install" do work. So need I do it to link my program to the library?

Yes, you need to add all of the -l... flags I mentioned before to your g++ call.

the output when I run:
This is Ginkgo 1.2.0 (develop)
running with core module 1.2.0 (develop)
the reference module is  1.2.0 (develop)
the OpenMP    module is  1.2.0 (develop)
the CUDA      module is  1.2.0 (develop)
the HIP      module is  not compiled
terminate called after throwing an instance of 'gko::StreamError'
what():  /home/ubuntu/ginkgo/core/base/mtx_io.cpp:695: read_description_line: error when reading the header line
Aborted (core dumped)

It sounds like you are trying to open a matrix file that either doesn't exist or that doesn't have the correct file format (MatrixMarket format)

I have fixed. Thank you very muchhhhh!!! I try doing it 2 weeks but I don't know how to link to the library. Thank you for supporting!

You're welcome, and have fun with Ginkgo :) I'll close the issue for now.


Storybook error when using I18nProvider in decorator: "NextRouter was not mounted."

What version of this package are you using?

next: 13.4.10
next-translate: 2.5.0
next-translate-plugin: 2.5.0
storybook: 7.0.27

What operating system, Node.js, and npm version?

MacOS Ventura 13.4
Node 18.16.0

What happened?
I am using Storybook. When I add a decorator to .storybook/preview.tsx to wrap <I18nProvider> around the stories, this causes a "NextRouter was not mounted." error.

If I remove the decorator, it works as expected.
I have reproduced the error in an example repo at https://github.com/EricImpact/next-translate-example/
What did you expect to happen?
I expect the story to load successfully.
Are you willing to submit a pull request to fix this bug?
If you can point me in the right direction, I'm happy to investigate.

Setting up next-router-mock with Storybook fixed this, so closing now.
For others with the same issue, use this:
https://www.npmjs.com/package/next-router-mock


Feature object per page

Hello, some small changes to the API , basically adds some getters to obtain / alter the behaviour of some components.

what is your goal? why do you need to expose those fields?

Well sorry, I was trying to get an access to the ObjectsPerPage property in the transport class.
Basically, I was expecting to find it in RedmineManagerFactory (to be injected later in Transport).
Finally, I discovered it in RedmineManager class.
I will cancel the push request.


Change way of handling local adapter

Hi
First of all thanks for a great software!
By using local storage I came across the same issue like described in #109 . This is my proposition for solving it

Hmm on my local machine tests are passing. Can you provide information about which tests are failing? I don't have access to your Jenkins server.


Unable to Export

Unity 2018.3.2f1
After creating new Shader generator, naming it and clicking Export. this exception occurs:
`Shader error in 'Raymarching/Tester': invalid subscript 'projPos' at Assets/uRaymarching/Shaders/Include/DeferredDirect.cginc(50) (on d3d11)
Compiling Vertex program with UNITY_PASS_DEFERRED
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_COLORSPACE_GAMMA UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR`

sorry, my bad. Had to change Shader Template before exporting


feature: Allow plugins to configure their own laziness

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
Sometimes, setting up Lazy to use lazy-loading can be a little repetitive. The user needs to find a list of commands for the plugin, and then they need to specify them all. This isn't very resilient to plugin updates where commands are added or removed.
Describe the solution you'd like
Plugin developers should be able to specify a file in lua/lazy/_automatic/<pluginName>.lua[^1]which gets required[^2] by Lazy itself. The automatic setup file should return a table with all of the Lazy triggers: cond, event, cmd, and ft. It should not be able to set anything else, including priority.
This automatic setup should only be triggered if lazy is set to true. User-specified values should overwrite pre-determined values.
Describe alternatives you've considered
See "Is your feature request related to a problem".
Additional context
The trouble with this is finding a way to use "path safe" plugin names, as require interprets a dot . as a slash /.
[^1]: I modeled the name after Telescope's _extensions submodule. It can be whatever.
[^2]: Something like require("lazy._automatic" .. pluginName) would work, plus it looks clean.

Another thing I forgot to mention is if we should let this functionality manage dependencies (I think we shouldn't, it's too easy to screw up and doesn't account for non-plugin dependencies).

That's already planned.

That's already planned.

Ah, my bad.

@folke, if you need help implementing this, I'm more than welcome to help.

I first need to think this through to keep everything performant.
I'm probably going to disallow the usage of functions inside plugins' specs, so that all that data can be cached and only needs to be updated when a plugin updates.
I would actually allow using these files even when the default for lazy is false, since if something's not working due to lazy-loading, it's the plugin dev that needs to fix it anyway.
I'll keep this issue open for now.

I'm also looking to support https://github.com/nvim-lua/nvim-package-specification directly.


Extra test cases for Collection .intersect() and .disjoint()

Collection.intersect() was partly broken (or at least utterly inconsistent) between versions 2.4.2 and 2.4.6. Simple test case:
def foo = [[0, 0], [0, 1]]
def bar = [[0, 1], [1, 1]]
assert [[0, 1]] == foo.intersect(bar)

would fail in the aforementioned versions as [] would be returned. This is fixed in 2.4.7 but to avoid future regressions, it is nice to have test covering this case, as suggested by @glaforge and @sbglasius on Twitter.
A basic search didn't reveal any similar test cases (some Foo intersection comparison can be found but it can be seen as a different test case).

Thanks! More tests are always a good thing. :smile:


Embedding configuration to be saved to Redux

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-446
Link to staging deployment URL
https://ui-wzpx3bx8u3r593588rdk5mwnmh.scp-staging.biomage.net/
Links to any Pull Requests related to this
N/A
Anything else the reviewers should know about the changes here
Regarding the best way to store the default config, I have come up with a mixed approach of both considerations 1 and 2 in the ticket.
The UI will store the default state of the embedding config, but we will want to have a default state saved in DynamoDB as well. This is for two reasons:
(a) if the config were to change in a non-destructive way (e.g. a new field or parameter is added), we want to make sure we can automatically 'upgrade' experiments the next time the user does some pre-processing, and without a migration script;
(b) we will still load the state from DynamoDB for purposes of traceability. If in the future we were to change a default value to something else, experiments that have identical settings files in DynamoDB would run differently before and after the update, so we would have a reproducibility problem.
As such, the proposed way to implement this is for the reducer to perform the creation of the object in the order of initial state -> current state -> state from DynamoDB. This meets the requirements of (a). We should also persist the config in DynamoDB from the data ingest script, which meets the requirements of (b).
Changes
Code changes
Added a new redux store and appropriate actions to save embedding configurations globally.
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[ ] Unit tests written
[x] Tested locally with Inframock
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[x] Relevant Github READMEs updated
[x] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[x] Photo of a cute animal attached to this PR

Love the animals :d In terms of the details about the changes that you listed, I will add us a ticket for the We should also persist the config in DynamoDB from the data ingest script, which meets the requirements of (b). part

Love the animals :d In terms of the details about the changes that you listed, I will add us a ticket for the We should also persist the config in DynamoDB from the data ingest script, which meets the requirements of (b). part

Love the animals :d In terms of the details about the changes that you listed, I will add us a ticket for the We should also persist the config in DynamoDB from the data ingest script, which meets the requirements of (b). part

My understanding is that it is already a ticket, BIOMAGE-450.

Love the animals :d In terms of the details about the changes that you listed, I will add us a ticket for the We should also persist the config in DynamoDB from the data ingest script, which meets the requirements of (b). part

My understanding is that it is already a ticket, BIOMAGE-450.

Unit tests added.

Unit tests added.


VAST not load with NuxtJS, no ad event triggered.

I use the latest version of plyr but i cant get my VAST ads working in my NuxtJS project.
I used the almost the same config like this: https://codepen.io/nightsurge/pen/NVQGyJ
Have anyone a workarround, fix or a reason why the VAST wont start ?
I get no error and the xml is loaded but in debug i dont see any ad event.

I'm getting this error trying to use nuxtjs too Uncaught SecurityError: Blocked a frame with origin "http://localhost:3000" from accessing a frame with origin "http://imasdk.googleapis.com". Protocols, domains, and ports must match.

@thomasmax-97 this looks more like an issue with VAST ads than Nuxt tbh. Also, probably a configuration there to be done.


Github Maven Repository Token Expired

Getting the following when doing a fresh Gradle Sync:
Caused by: org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not GET 'https://maven.pkg.github.com/komputing/KHash/com/github/komputing/khash/sha256/1.1.3/sha256-1.1.3.pom'. Received status code 401 from server: Unauthorized

Checked that the credentials given are correct based on the README.md, but they were correct in our repository.
Would be great if you could provide updated information.
Kind regards

The same, please help

It seems you need to generate your own token on github. @ligi would be helpful to mention this explicitly in the readme


Aider .env precedence is wrong, does not behave as documented.

Issue
Aider does not load the correct OPENAI_API_KEY. I have it defined in both my home directory and my .git root (which also happens to be my current directory).
Expectation
Aider uses the OPENAI_API_KEY from my git root / current directory, not the one in my home directory.
Behaviour
Aider is using the key that's specified in my home directory, this behaviour can also be seen if I set the key as a User or System environment variable, that defined env var will take precedence over .env files, which feels incorrect and also does not align with the documented behaviour.
Documentation
https://aider.chat/docs/config.html#configuration

Aider has many options which can be set with command line switches. Most options can also be set in an .aider.conf.yml file which can be placed in your home directory or at the root of your git repo. Or by setting environment variables like AIDER_xxx either in your shell or a .env file.

https://aider.chat/docs/config/dotenv.html#config-with-env

Aider will look for a .env file in these locations:
Your home directory.
The root of your git repo.
The current directory.
As specified with the --env-file  parameter.
If the files above exist, they will be loaded in that order. Files loaded last will take priority.

Hypothesis & Workarounds
I have not found a workaround to get hierarchical environment variables working. I tried using --env-file on the command line, and still the home dir env takes precedence.

Initially I suspected that perhaps the OPENAI_API_KEY was already loaded into my shell, and Aider was letting the shell's environment take precedence over .env (behaviour I would still find confusing). However, I have verified that this is not the case. OPENAI_API_KEY is not defined in the shell before launching Aider.
I can confirm that if I define OPENAI_API_KEY on the CLI before launching Aider, that value takes precedence.
I can confirm that if I use --openai-api-key on the CLI, that has the highest precedence.

Thus, the behaviour seems to match ConfigArgParse of command line > environment variables > config file values > defaults, where environment variables are trampling .env files.
What I do not expect, is that ~/.env is being loaded between the launch of Aider and the ConfigArgParse, populating the environment and causing the config file values to not work as expected.
I have tried using AIDER_OPENAI_API_KEY to see if that auto loads in ConfigArgParse and tramples the environment, that does not work either.
I see python-dotenv is a transient dependency of lite-llm, but that should have behaviour that works in my favour, not against it.
python-dotenv==1.0.1
    # via litellm

Screenshot
I echo the API key via /run to demonstrate that the environment is not populated correctly, when Aider tries to make a commit in this configuration (because its using GPT-3.5 as weak model) it will fail as it will use 'homedir' as the API key instead of the correct key defined in my project.

Version and model info
Aider v0.43.4
Model: claude-3.5-sonnet / gpt-3.5-turbo
Git repo: 497 files
Repo-map 1024

Thanks for reporting this. I can reproduce the problem.

The fix is available in the main branch. You can get it by installing the latest version from github:
python -m pip install --upgrade git+https://github.com/paul-gauthier/aider.git

If you have a chance to try it, let me know if it works better for you.

LGTM! Thanks! 🚀


feat: add Chinese (Taiwan) translation

Add Traditional Chinese (Taiwan) translation.

Sorry, we don't support foreign translations. As we don't speak Chinese we won't be able to update translations when new keys are added without relying on someone to update them for us


chore: add issue templates

Codecov Report

Merging #132 (25270bf) into main (6a0dfb1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #132   +/-   ##
=======================================
  Coverage   99.10%   99.10%
=======================================
  Files           9        9
  Lines         446      446
  Branches       62       62
=======================================
  Hits          442      442
  Misses          4        4

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Persistent attack/defense effects do not go away if no attacks/defenses are made

Attack/defense effects persist until the next attack and defense is attempted. Critical defense success/80 produces both effects, yet if the victim is not attacked, there is no reason to call defense, and if the player understands what happened, there is no reason to attack. Better convert into a round effect?! But what if there are several attacks b/c the character is faster?

Could the scripts treat action effects in such a way that if the action effect is not being cancelled for an entire round, it gets cancelled as if it were a round effect?

Along the same lines, special damage registered manually does not get recognized for its effects. endofround.mmm could update status markers to do that.


xcversion simulators failing on invalid cert

I'm trying to install new runtimes for the current Xcode selected, but getting a cert issue.
I added the 'Download' output so I knew what was trying to download

$ xcversion simulators --install='iOS 8.2'
Installing iOS 8.2 Simulator for Xcode 8.2.0...
Download https://devimages.apple.com.edgekey.net/downloads/xcode/simulators/com.apple.pkg.iPhoneSimulatorSDK8_2-<IP_ADDRESS>4581536.dmg
curl: (60) SSL certificate problem: Invalid certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
[!] Failed to download iOS 8.2 Simulator.
$

What OS version and ruby version are you running @bennid ?
What is the output of system_profiler SPSoftwareDataType and ruby -v?

$ ruby -v
ruby 2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin15]
$ system_profiler SPSoftwareDataType
Software:
System Software Overview:

  System Version: macOS 10.12.6 (16G29)
  Kernel Version: Darwin 16.7.0
  Boot Volume: Macintosh HD
  Boot Mode: Normal
  Computer Name: bedouglas-mac
  User Name: Ben Douglas (bedouglas)
  Secure Virtual Memory: Enabled
  System Integrity Protection: Enabled
  Time since boot: 58 minutes

I did work around this by creating ~/.curlrc with "--insecure" in it


Update LocalRest to increase fiber stack size

Previously the stack size of fibers in LocalRest were too small, they were changed to be 16MB by default.

Running ./build/agora-unittests
0   agora-unittests                     0x000000010fc3868e _D4core7runtime18runModuleUnitTestsUZ19unittestSegvHandlerUNbiPSQCk3sys5posix6signal9siginfo_tPvZv + 62
1   libsystem_platform.dylib            0x00007fff76800f5a _sigtramp + 26
2   agora-unittests                     0x000000010fc3dc01 _D4core6thread5Fiber5stateMxFNaNbNdNiNfZEQBnQBlQBh5State + 1
3   agora-unittests                     0x000000010f7c33f4 _D6geod249LocalRest18BaseFiberScheduler8dispatchMFZv + 228
4   agora-unittests                     0x000000010f7c320e _D6geod249LocalRest18BaseFiberScheduler5startMFDFZvZv + 46
5   agora-unittests                     0x000000010f5468d7 _D6geod249LocalRest__T9RemoteAPITC5agora4test4Base7TestAPIZQBl__T7spawnedTCQBpQBmQBk8TestNodeZQBdFSQCn6common6ConfigQhZv + 727
6   agora-unittests                     0x000000010f58edcf _D3std11concurrency__T6_spawnTPFS5agora6common6ConfigQhZvTQBaZQBoFbQBlQBmZ4execMFZv + 79
7   agora-unittests                     0x000000010fc3a385 thread_entryPoint + 373
8   libsystem_pthread.dylib             0x00007fff7680a6c1 _pthread_body + 340
9   libsystem_pthread.dylib             0x00007fff7680a56d _pthread_body + 0
Program exited with code -11

Another weird stack trace...

Yeah there seem to be somewhat random failures in Travis. I really thought the segfaults were finally resolved..

Part of https://github.com/bpfkorea/agora/issues/209

Blocked by https://github.com/bpfkorea/agora/pull/381 and https://github.com/Geod24/localrest/pull/23

Superseded by https://github.com/bpfkorea/agora/pull/379.


Update README.md to add megablocks requirement for mixtral

Update README.md to add megablocks requirement for mixtral

Updated


Again! Error while integrating Stage View

Version: You have Microsoft Teams Version <IP_ADDRESS>0 (64-bit). It was last updated on 1/20/2022.
Facing Something went wrong. Please try again. when trying to integrate Stage View in an adaptive card and following tab-stage-view sample for reference. I have implemented a personal tab and using it in stage view.

manifest.json
"staticTabs": [
{
"contentUrl": "/tab-auth/simple",
"entityId": "simpleAuth",
"name": "Test Authentication Tab",
"scopes": [
"personal"
],
"context": [
"personalTab",
"channelTab"
],
}
]
adaptiveCardJson
"body": [
...,
{
type: 'ActionSet',
actions: [
{
type: "Action.Submit",
title: "Auth Tab",
data: {
msteams: {
type: "invoke",
value: {
type: "tab/tabInfoAction",
tabInfo: {
contentUrl: "/tab-auth/simple",
websiteUrl: "/tab-auth/simple",
name: "Test Authentication Tab",
entityId: "simpleAuth"
}
}
}
}
}
]
},
]
Error Screenshot

@i066088 - We are already tracking this issue here #196 . We have informed engineering team about re-occurrence of the issue and will inform once we get any update. If you want ,you can close this instance and follow that thread for updates.

@Prasad-MSFT  thanks a lot for the update. I see #196 is closed. So I created a new one. If #196 is re-open, I will close this one.

@i066088 -  Could you please check it in Microsoft Teams Version <IP_ADDRESS>416 (64-bit).
Please let us know if you are facing issue in this version.
We will also check the issue in Teams version <IP_ADDRESS>0 (64-bit) because currently this version is not visible to us.

@v-chetsh I would like to. But I do not know how to download the Microsoft Teams Version <IP_ADDRESS>416 (64-bit).
I find my team client is always updated silently.
Could you give any hints where I can find the Microsoft Teams Version <IP_ADDRESS>416 (64-bit)?
thanks a lot.

https://microsoft-teams.en.uptodown.com/windows/versions
That's one place that has an archive of older versions. You can check from here

@Prasad-MSFT  Thanks for the link. I open the link But I cannot find the Microsoft Teams Version <IP_ADDRESS>416 (64-bit).

@i066088 - Could you please try updating your Teams with latest version and check it once.

@v-chetsh thanks a lot. It works on Microsoft Teams Version <IP_ADDRESS>4 (64-bit). It was last updated on 2/4/2022.

@v-chetsh
From this link https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/tabs-link-unfurling
I see the following description:
"
When the user enters a URL on the Teams desktop client, the bot is invoked and returns an Adaptive Card with the option to open the URL in a stage. After a stage is launched and the tabInfo is provided, you can add the ability to pin the stage as a tab.
"
Could you give some hints about how I can add the ability to pin the stage as a tab?
thanks in advance.

@i066088 - Could you please refer below samples and try it once:
https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/meetings-stage-view

@i066088 - Could you please confirm if your issue has resolved with above suggestion or still looking for any help?

We are closing the issue for now. Please feel free to reopen if required. Thanks!


Unable to set foreign key

I'm trying to setup a foreign key with an ON UPDATE and ON DELETE setting, but the call I make seems to have no effect.
Here's my code:
db.foreignKeys = true

let categories = db["Categories"]
let categoryID = Expression<Int64>("id")
et name = Expression<String>("name")

db.create(table: categories) { t in
    t.column(categoryID, primaryKey: .Autoincrement)
    t.column(name)
}

let bookmarks = db["Bookmarks"]
let bookmarkID = Expression<Int64>("bookmark_id")
let url = Expression<String>("url")
let comment = Expression<String?>("comment")
let categoryFK = Expression<Int64?>("category_id")

db.create(table: bookmarks) { t in
    t.column(bookmarkID, primaryKey: .Autoincrement)
    t.column(name)
    t.column(url)
    t.column(comment)
    t.column(categoryFK)
    t.foreignKey(categoryFK, references: categories[categoryID], update: SchemaBuilder.Dependency.Cascade, delete: SchemaBuilder.Dependency.Cascade)
}

Am I using the foreighKey function on the last line, correctly? No relationship is setup by the end of the this code being executed.
Many thanks in advance, and awesome job on SQLite.swift!

That line looks right to me. What makes you think the relationship isn't getting set up?
Try prepending the code above with db.trace(println) to log the queries.
You can also shorten that last line by using the dot-abbreviated form:
t.foreignKey(categoryFK, references: categories[categoryID], update: .Cascade, delete: .Cascade)

Also: note that every connection needs to run db.foreignKeys = true for foreign key constraints to work.

Wow, thanks for the quick reply!
Ah that's so awesome! From the printouts I can see that the correct statement is being written. The thing that made me think that the foreign key wasn't being setup was that Base wasn't showing the foreign key. Is this something you'd expect or see in a client you use? Am I thinking of constraints in the wrong way perhaps? I can share screenshots if it helps. Using:
t.column(categoryFK, references: categories[categoryID])

works and shows in Base.
Cool, thanks for the tip.
Ah cool, I put that in when using t.column(, references:) as an exception was raised without it.

I wonder if Base has a bug in how it looks for foreign keys? Can you query the sqlite_master table to verify?

Yep, it's there:
CREATE TABLE "Bookmarks" ("bookmark_id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "name" TEXT NOT NULL, "url" TEXT NOT NULL, "comment" TEXT, "category_id" INTEGER, FOREIGN KEY("category_id") REFERENCES "Categories"("id") ON UPDATE CASCADE ON DELETE CASCADE)
So I'm good?

I'd test with some dummy data, but you should be good to go.

Awesome, BRB

Hold tight, I'll have to look at this when I get back home in a few hours to confirm it works fine

Tested. All good. Weird that it's not showing on Base. I'll shoot them an email to give them a heads up. Thanks Stephen

unable to set db.foreignKeys = true !!!

Value of type 'Connection?' has no member 'foreignKeys'


exhibitor: fix paths for zookeeper shell scripts

Motivation for this change
Exhibitor wants to change its local file and therefor in preInstall phase all files are copied from /nix/store to /var folder. However since starting zookeeper shell scripts are wrapped by nix (especially zkServer.sh after https://github.com/NixOS/nixpkgs/commit/6e9c7f0ad51a8fd3ce9114fb9eedd2e9284efa85#diff-f80d089d8c5ac8a5901041c8810cb128) exhibitor still starts from the /nix/store, tries to modify files there and fails.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.
Tested on NixOS box by running the updated service and validating that it's working as expected

Not a huge fan of the hackery in the prestart script but it'll do for now, I guess, until someone decides to revamp it. Mind submitting a PR against 18.09 too for this? The service module is just broken, right?


#18 - Fixed bug where addUser/removeUser with region param would atte…

…mpt to add/remove a region user

I thought I merged this in - whoops!


Real-world implementation problems

Dear developers,
I hope this message finds you well. I am writing to express my gratitude for the geolfit library and raise some concerns about its practical implementation.
I would like to inquire about budget allocation in the experimental plan. Once we have the experimental design ready, the marketing specialist may wonder how to allocate the budget. For example, suppose there are three treatment geos and a budget of $3k for an experiment duration of four weeks. Should the budget be allocated proportionally, such as $1,000 for each geo and $250/week, or should it be allocated depending on historical budget or geo market size? Any guidance or best practices on this matter would be highly appreciated.
Thank you for your time and efforts in developing the geolfit library. I look forward to hearing your feedback and suggestions.
Best regards,
Albert

Hi @albertsalgueda, thank you for reaching out to us and for using GeoLift!
This is a really good question. Most digital platforms will work best when they are allowed some freedom to optimize the spending of the budget. With this in mind, we would recommend leaving the $3000 budget for the set of test regions and let the platform spend it according to the best-suited optimization event/conversion. Does that make sense?


Add version: lightspark.lightspark 0.8.5-git

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

cc @denelon @palenshus: "Azure-Pipeline-Passed" label needs to be added to this PR.

@ItzLevvie we're doing some work on validation. See if approving works on this one (assuming you are ready to approve).


Interest in Contributing to Model Creation AI Assistant (Co-Pilot) Project for GSOC

Discussion
Dear @dselman,
My name is Muhammad Samiullah. I am writing to express my keen interest in the Model Creation AI Assistant (Co-Pilot) project and my desire to contribute to Accord Project as part of Google Summer of Code. After reviewing the project details and requirements, I believe my skills and background make me well-suited to take on this challenge.
I have a strong foundation in TypeScript programming and have experience working with chat-based AI models such as ChatGPT. My background in open source contribution at OpenSearch project and Microsoft Learn modules equips me with the necessary technical expertise to design and implement the user interaction and AI integration as outlined in the project description.
To kick-start my involvement in this project, I have opened an issue on GitHub to initiate further discussion and share my thoughts on how I can add value to the initiative. My tentative plan is to research and analyze similar AI co-pilot efforts in the industry, such as those by GitHub, Repl.it, and Google, to gain insights into best practices and potential challenges. I wanted to know what exactly the organization is expecting from the contributor.
I am eager to discuss how I can best contribute to the Co-Pilot project and hear your guidance on preparing a comprehensive project proposal. Your insights and mentorship will be invaluable as I embark on this exciting opportunity.
Thank you for considering my interest, and I look forward to the possibility of collaborating with you and the Accord Project team.
Context
I am part of GSoC 2024, and I need guidance to get started.

@dselman kindly guide?


outputDir option does not work in combination with ruby

Just noticed that when "sass.compiler" is "ruby", the output folder is always "/css", no matter what "outputDir" defines. Only of the compiler is set to "libsass", outputDir works as designed.

Correction: It's sufficient to set the "sass.compiler" to "ruby" to have this effect.

Can't reproduce.
How is your .brackets.json file?

Thanks for your quick reply.
Here's the .brackets.json I've tested:
{
"language.fileExtensions": {
"dwt": "html"
},
"sass.compiler": "ruby",
"sass.compass": true,
"sass.options": {
"sourceComments": false,
"outputStyle": "nested",
"outputDir": ""
}
}
It does not matter how the "outputDir" option is set, the actual output folder for all .scss files is always "/css", i.e. folder named "css" under the project root. This also happens if you omit the "outputDir" completely.
If I change the compiler to "libsass", "outputDir" works as documented.
BTW: I'm using ruby under Windows, if that helps.

@derwaldgeist I can only reproduce the issue using compass (It doesn't depend on the compiler which is used)

Until this isn't fixed you can add a config.rb file at the root of your project:
css_dir = "output/dir/relative/to/your/project/roort"

Thanks, I did not know about this Ruby option! I'll test it.

@nicolo-ribaudo: I first also thought it was related to compass. But then, strangely, it also happened when I disabled compass. Maybe it is enough that compass was enabled once?

config.rb works just using Compass. More info at http://compass-style.org/help/documentation/configuration-reference/

I first also thought it was related to compass. But then, strangely, it also happened when I disabled compass. Maybe it is enough that compass was enabled once?

That is strange :confused:
Options aren't cached, so the result shouldn't be affected by what you did before.

Hi Nicolo,
I now tried the config.rb workaround. It works in principle, but does not give me the desired result. The folder css_dir points always seems to be relative to the project's root folder. Yet, I would like to store the generated css files right where the source files are located, at an arbitrary level of my project structure. The reason behind this is that I am using polymer, and I would like to keep the web components together with their sass and css. Even if I state css_dir="." or css_dir="./", it is always the root folder where the generated css is stored - not the folder where the source file was located. In the compass config documentation, I could not find any option to define a real "sass-file-relative" path. Even if I use css_path instead, this is always using the project root as it's own root. Strangely, css_path="" or css_path="./" would store the css files in a folder "/css" (instead of "/styles"), and css_dir="" stores the files right in the project root folder. It would be easy if I knew about a variable that stores the source file path, but the compass doc does not mention any, and I'm not a Ruby expert.


Web interface

Is it possible to do a web interface too for the non-android users?

hi! im sorry, doing a cross platform approach with the project is a lot of work. so probably, no. tho, there are great options when it comes to similar apps but web-based, movie-web.app is one of them!


InstanceCollection only returns one instance, despite multiple running instances

I'm experiencing an issue where Capistrano only deploys to a single server, despite having multiple running servers in my AutoScalingGroup.
My setup on AWS:
A launch template (id: lt-xxx, name: preprod)
An autoscaling group (name: preprod)
2 running instances launched by the ASG (Ids: i-x1 and i-x2)
Below is the output of instantiating an Elbas::AWS::AutoscaleGroup, calling instances.running, and creating a new Elbas::AWS::InstanceCollection with the IDs I can see in the ASG:
asg = Elbas::AWS::AutoscaleGroup.new preprod
=> #<Elbas::AWS::AutoscaleGroup:0x000000000351efc0
 @aws_client=#<Aws::AutoScaling::Client>,
 @aws_counterpart=
  #<struct Aws::AutoScaling::Types::AutoScalingGroup
   auto_scaling_group_name="preprod",
   auto_scaling_group_arn="arn:xxx",
   launch_configuration_name=nil,
   launch_template=#<struct Aws::AutoScaling::Types::LaunchTemplateSpecification launch_template_id="lt-xxx", launch_template_name="preprod", version="$Latest">,
   mixed_instances_policy=nil,
   min_size=0,
   max_size=2,
   desired_capacity=2,
   default_cooldown=300,
   availability_zones=["eu-west-1b", "eu-west-1a"],
   load_balancer_names=[],
   target_group_arns=["arn:xxx"],
   health_check_type="EC2",
   health_check_grace_period=300,
   instances=
    [#<struct Aws::AutoScaling::Types::Instance
      instance_id="i-x1",
      availability_zone="eu-west-1b",
      lifecycle_state="InService",
      health_status="Healthy",
      launch_configuration_name=nil,
      launch_template=#<struct Aws::AutoScaling::Types::LaunchTemplateSpecification launch_template_id="lt-xxx", launch_template_name="preprod", version="3">,
      protected_from_scale_in=false>,
     #<struct Aws::AutoScaling::Types::Instance
      instance_id="i-x2",
      availability_zone="eu-west-1a",
      lifecycle_state="InService",
      health_status="Healthy",
      launch_configuration_name=nil,
      launch_template=#<struct Aws::AutoScaling::Types::LaunchTemplateSpecification launch_template_id="lt-xxx", launch_template_name="preprod", version="3">,
      protected_from_scale_in=false>],
   created_time=2019-02-25 14:44:39 UTC,
   suspended_processes=[],
   placement_group=nil,
   vpc_zone_identifier="subnet-xxx,subnet-xxx",
   enabled_metrics=[],
   status=nil,
   tags=[],
   termination_policies=["Default"],
   new_instances_protected_from_scale_in=false,
   service_linked_role_arn="arn:aws:iam::xxx:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling">,
 @name="preprod">

 asg.instances.running
=> [#<Elbas::AWS::Instance:0x00000000094de348
  @aws_client=#<Aws::EC2::Client>,
  @aws_counterpart=#<Aws::EC2::Instance:0x00000000094a4530 @client=#<Aws::EC2::Client>, @data=nil, @id="i-x1">,
  @id="i-x1",
  @public_dns="xxx.eu-west-1.compute.amazonaws.com",
  @state=16>]

 collection = Elbas::AWS::InstanceCollection.new ["i-x1", "i-x2"]
  => #<Elbas::AWS::InstanceCollection:0x0000000008976be0
 @aws_client=#<Aws::EC2::Client>,
 @ids=["i-x1", "i-x2"],
 @instances=
  [#<Elbas::AWS::Instance:0x000000000885dad8
    @aws_client=#<Aws::EC2::Client>,
    @aws_counterpart=#<Aws::EC2::Instance:0x00000000087f9e70 @client=#<Aws::EC2::Client>, @data=nil, @id="i-x1">,
    @id="i-x1",
    @public_dns="xxx.eu-west-1.compute.amazonaws.com",
    @state=16>]>

As you can see, when I instantiate the ASG, I can see 2 instances (i-x1 and i-x2), but calling
asg.instances.running

or
Elbas::AWS::InstanceCollection.new ["i-x1", "i-x2"]

I only get the first instance.
The issue seems to be in Elbas::AWS::InstanceCollection#query_instances_by_ids, which only looks at the first reservation in the response from describe_instances.
I'm submitting a PR, which changes the method to:
def query_instances_by_ids(ids)
  aws_client
    .describe_instances(instance_ids: @ids)
    .reservations.map(&:instances).flatten
end

Thanks for this, can you add a spec for multiple reservations as well? It should be pretty easy to add in spec/aws/instance_collection_spec.rb. You can just make a new DescribeInstances_MultipleReservations stub in spec/support/stubs just like the existing DescribeInstances one.


In table with related data last ChildRowContent appears not to have the same styling applied as previous rows

Bug type
Component, Docs (mudblazor.com)
Component name
MudTable
What happened?
In a table with related data the last ChildRowContent does not have the horizontal lines between the rows like previous ChildRowContent. I replicated this issue in Chrome and Edge. It is present in the documentation. This happens on every page in the last ChildRowContent.
Image for reference:

Expected behavior
All ChildRowContent should have the same styling applied.
Reproduction link
https://try.mudblazor.com/snippet/mkcQFPlpfXtrfYTD
Reproduction steps

Run the code snippet
Open last "Address Details"
Compare to previous "Address Details"

Relevant log output
No response
Version (bug)
6.0.17
Version (working)
No response
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I fixed this with a very small css tweak, I will PR sometime tomorrow after work. :)


Implementation of Recipes page in UI

We should implement Recipes pages where users can use the provided functionality - browse different recipes, select recipe categories, see interesting articles about them and the most valued reviews. This information is roughly presented and can be changed at any time by all assignees.

Finish work, can be opened if new features are going to be added or modify existing ones.

Finish work, can be opened if new features are going to be added or modify existing ones.


adjust margins and paddings

with the new design of google chat, i feel more the need to also adjust some margins and paddings. would it be feasible to include those and make them configurable?

The current design of the code just transforms a consistent set of colors to different consistent set of colors throughout the styling. This might not apply to spacing. But hard to say without trying.
Where do you see the need for this?

so actually i just reviewed it, and i would actually say its not only paddings and margins, but also hiding things completely and resizing things. as a start, i would like to change the look and feel of the sidebar on the left:

from https://gsuite.google.com/intl/de/products/chat/
i dont need the preview text in the sidebar, and the pictures could be smaller. additionally the spacing in between is a lot. as a target, i would think the slack style is appropiate:


doc: use correct identifiers for InputEventJoystick{Motion, Button}

fixes #3655

Maybe it would be meaningful to change it in https://github.com/godotengine/godot/blob/master/core/os/input_event.cpp#L109-L120 and https://github.com/godotengine/godot/blob/master/modules/gdscript/gd_editor.cpp#L2327-L2328 for consistency?

alright, rebased


[ENG-4152][ENG-4160] File and item metadata managers

Tickets:

ENG-4152
ENG-4160

Purpose
Start of the manager components for the File Metadata form and the Node Metadata form.
Summary of Changes

Add manager components
Add translation strings

Side Effects
No, this isn't hooked to anything yet.
QA Notes
Nothing to test yet.

@futa-ikeda No validators for custom metadata. We just take whatever we're given.


Remove SST-BF from the README as it is not supported

The "Functionality of the Kubernetes Power Manager" section currently includes SST-BF, which is not actually supported by Kubernetes Power Manager. The SST-BF section should be removed.

Thanks for making the update.


chore(babel-plugin): babel-loader should not added when config is not modify

Summary
the default Babel configuration will not have additional impact on the compilation results, except for increasing the build time, so we don't need add babel if user not modify / add any config.
Related Links

Checklist

[ ] Tests updated.
[ ] Documentation updated.

!canary


Updated docs for Vidoomy blocking supported

🏷 Type of documentation

[x] update bid adapter
[x] new feature

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself

@nimasrn - please clarify this support. The requirement is that your adapter first prioritize ORTB-level parameters as you note in the example: .bcat,.battr, etc.
For Prebid Server, do you also accept these parameters as bidder-specific params? i.e. $.imp[].ext.prebid.bidder.vidoomy.{bcat, battr, etc}
That's what placing these values in the bidder params table implies. You should be aware that Prebid Server supports the ORTB Blocking module, so it's not clear why bidder-specific blocking params would be useful. But there's nothing wrong with supporting them as long as ORTB-supplied values are utilized.

Yes, We support and first prioritize ORTB-level parameters for bcat, badv, bapp, btype and battr.


Implement schema support for disassembly

This PR adds a number of new features to the disassembler, foremost the ability to consume a message descriptor that makes the disassembly heuristics much smarter. Changes include:

Given a descriptor, correct disassembly of:
a. ZigZag values.
c. Unsigned values.
b. Bools.
c. Subnormal floats.
d. Packed fields.
Given a descriptor, remarks with field names and enum value names.
Smarter collapse of braces during printing.
Better alignment of disassembler remarks.
Flags for showing the spec (showing it in -help is rude) and whether to show bitpatterns of floats (off by default now).

(I am probably going to attempt to break this into a sequence of three PRs that improve the printing and flag-parsing facilities of the library, followed by schema-awareness.)

This PR is now in a reviewable state.

(I am probably going to attempt to break this into a sequence of three PRs that improve the printing and flag-parsing facilities of the library, followed by schema-awareness.)


adding PHPCompatibilityWP checks

Hello-
This adds the ability to test for PHPCompatibility, including compatibility for WordPress per https://github.com/PHPCompatibility/PHPCompatibilityWP.
This addition would allow for themes, plugins, etc. to be checked against different versions of PHP and would be in addition to the existing sniff that checks for codings standards only.
Please let me know if you have questions or require changes.
Thanks!

@damonsharp this is great to see! Can you go ahead and modify the tests to account for the new check. Additionally could you comment with a 1-2 sentence snippet of how this either is different or enhances the existing WordPress standards that are apart fo the container?

@sean-e-dietrich I added the requested clarification to the description above as well as requested tests, but if I'm missing something, let me know. Thanks!

@damonsharp this looks good and it includes standards for both PHPCompatability general and for WP. The only thing I'm going to ask is if you can remove the .idea directory within your PR.


Error in documentation (Typescript) for inheriting-styles-from-a-superclass

https://lit.dev/docs/components/styles/#inheriting-styles-from-a-superclass
super.styles,
gives the following error
'super' property access is permitted only in a constructor, member function, or member accessor of a derived class.

Thanks for the issue, transferred to the lit.dev documentation site repository.
The preview is currently broken:
https://user-images.githubusercontent.com/15080861/134965647-cb8b9b6f-6168-45d7-9245-3be538495d6f.mp4

thanks


Bug with scopes/class methods and searchkick gem

I was following the searchkick manual.
https://github.com/ankane/searchkick#indexing
As written, I defined a search_import scope to define eager loaded values for custom indexed data.
I tried both defining a scope (as stated in the guide) and a class method. Both raises an error when I run reindex:
class Article
  scope :search_import, -> { all.with_associations(:published_version) }
end

class Article
  def self.search_import
    all.with_associations(:published_version)
  end
end

They both raises NoMethodError: undefined method 'identity' for #<#<Class:0x007f961a2a97b8>:0x007f961a2a8520>
Runtime information:
Neo4j database version:
neo4j gem version: 7.0.6+ (master HEAD)
neo4j-core gem version: 6

I think I've fixed it.  Just released patch versions: 6.0.9, 6.1.12, and 7.0.8.  Give that a try! ;)

Wow, it was really a code bug!
I tested the patch. Now I got no error, but the eager load is not working...
class Article
  include Neo4j::ActiveNode
  include Neo4j::Timestamps
  include Searchkick::Model
  searchkick
  def self.search_import
    all.with_associations(:published_version)
  end

  def search_data
    attributes.merge(
      'published' => !published_version.nil?
    )
  end
end

irb(main):016:0> Article.reindex
 CYPHER 19ms MATCH (n:`Article`) RETURN n ORDER BY n.uuid LIMIT {limit_1000} | {:limit_1000=>1000}
 Article#published_version 4ms MATCH (article516) WHERE (ID(article516) = {ID_article516}) MATCH (article516)-[rel1:`published_version`]->(result_published_version:`Version`:`Quotable`) RETURN result_published_version | {:ID_article516=>516}
 Article#published_version 2ms MATCH (article101) WHERE (ID(article101) = {ID_article101}) MATCH (article101)-[rel1:`published_version`]->(result_published_version:`Version`:`Quotable`) RETURN result_published_version | {:ID_article101=>101}
 Article#published_version 6ms MATCH (article74) WHERE (ID(article74) = {ID_article74}) MATCH (article74)-[rel1:`published_version`]->(result_published_version:`Version`:`Quotable`) RETURN result_published_version | {:ID_article74=>74}
 Article#published_version 5ms MATCH (article131) WHERE (ID(article131) = {ID_article131}) MATCH (article131)-[rel1:`published_version`]->(result_published_version:`Version`:`Quotable`) RETURN result_published_version | {:ID_article131=>131}

... MANY OTHERS...

 Article#published_version 4ms MATCH (article80) WHERE (ID(article80) = {ID_article80}) MATCH (article80)-[rel1:`published_version`]->(result_published_version:`Version`:`Quotable`) RETURN result_published_version | {:ID_article80=>80}
  Article Import (280.1ms)  {"count":38}
D, [2016-05-27T10:53:52.457240 #56982] DEBUG -- :   Article Import (280.1ms)  {"count":38}
=> true

I think it comes down to this:
https://github.com/ankane/searchkick/blob/master/lib/searchkick/model.rb#L53
It's calling searchkick_klass which is going to get Article and so even if you do Article.search_import.reindex (I assume that's what you meant to do) it's just going to use the base class.
I think there could be a couple of ways of fixing this, depending on how general you want the solution to be.  It looks like the reindex method is simply aliased to searchkick_reindex if reindex doesn't already exist.  Thus you could write your own reindex for your model and call searchkick_reindex` yourself (I suspect that's what the aliasing is all about).
Alternatively you could define a searchkick_klass method to overwrite the class reader here:
https://github.com/ankane/searchkick/blob/master/lib/searchkick/model.rb#L11
You could even define that on QueryProxy (thus defining it on AssociationProxy since AssociationProxy defers all missing methods to QueryProxy) so that it could simply just work anywhere.  If that work, it might be a simple gem neo4j-elasticsearchfor anybody who wants to have the same hack.  Probably theREADMEcould explain thatsearchkick` works with Neo4j normally but if you want to do this special stuff you would need the gem (and maybe in the future the gem might contain other helper code)


Support Codex embeddings

Current implementation OpenAI embeddings are hard coded to return only text embeddings via. GPT-3. For example,
    def embed_documents(self, texts: List[str]) -> List[List[float]]:
...
        responses = [
            self._embedding_func(text, engine=f"text-search-{self.model_name}-doc-001")
            for text in texts
        ]

    def embed_query(self, text: str) -> List[float]:
...
        embedding = self._embedding_func(
            text, engine=f"text-search-{self.model_name}-query-001"
        )

However, recent literature on reasoning shows CODEX to be more powerful on reasoning tasks than GPT-3. OpenAIEmbeddings should be modified to support both text and code embeddings.

Probably worth deprecating now that codex support is being killed


Document outline ideas

This is an initial implementation of the document outline, it will show up when Perspex xaml files are opened.
I plan to add the following:

[ ] Highlighting occurrences of the filter string within the ui containers, similar to the solution explorer filter.
[ ] ability to collapse/expand nodes.
[ ] displaying the name attribute

Awesome!

Nice, also showing full path to the items found in the filters

Current state of the document outline, more things to work on:

[ ] async refresh of the document outline pane.
[ ] collapsed nodes should be parsed on demand (when the user is expanding that node), they will be auto-expanded when the user is filtering.
[ ] reuse view-models so that we don't need to create them on each key-stroke.


Can't switch between 2 windows of the same app.

You can't switch between 2 windows of the same application because the windows' preview always shows under the taskbar, so when you put the taskbar on the top, the preview goes up and is not visible as it's outside of the screen.
Repro steps:

open 2 notepad windows
minimize the windows
click in notepad in the taskbar.
Issue: Notepad's window preview is not visible, hence you can't open the minimized notepad again (unless you use Alt+Tab)

Thank you for reporting this issue! I realize this is probably the most annoying issue with setting the taskbar to the top. Unfortunately, I do not know of a way to fix it by adjusting the registry. There are a few workarounds. However, these might not be very usable depending on how you are used to use Windows.

I enabled the 'Task View' button on the taskbar. Whenever I want to switch to a different window I click on the icon first, afterwards I select the window I want.
Another possibility is to 'Win+tab'. This is practically the same as clicking the 'Task View' button. By using 'Win+tab' instead of 'Alt+tab' I find it easier to select the desired application window.

I am sorry I do not have a better solution for this at the moment. It is a direct consequence of the new taskbar UI from Microsoft and the fact that everything seems to be built hardcoded. I did not find any registry settings which change the direction (below taskbar vs above taskbar) the windows are shown.

Not sure if it will help, but evidently at one time Windows 10 had the same, or similar issue, and I found this post talking about it.  I'm not a developer, but maybe it might give you some ideas of what else to look for??  Windows not being brought to front

A temporary solution to this is right clicking (instead of left clicking), so you get the list of recent files. The open files will appear at the top of the list.
It's not exactly the same, but it works.

@aberdean: Thanks for this! But it doesn't work in some important usage cases. For example, in Chrome, you will not get a list of recent windows, just a list of recent tabs. More of my personal issue: it doesn't work with my Windows Explorer substitute, Director Opus. I often have a lot of DOPUS windows open at a time, it is crucial to be able to switch between them quickly. I blame Microsoft.

A temporary solution to this is right clicking (instead of left clicking), so you get the list of recent files. The open files will appear at the top of the list.

@Xendiadyon Ditto. I recommend that for anyone who really needs access to the grouped applications list.

Due to my specific message posted in issue 25 this upcoming feature in Taskbar11 is now halted. However, I would recommend using @Naamloos Open Source solution for the time being. It works fairly well combined with Taskbar11 and should be a temporary fix.
More details about the issue can be read here
Issue 25 - Top Taskbar Issues
Temporary solution until version 22533 and higher
https://github.com/Naamloos/TopCenterStart11


Suggestion: Remove "Facade" from class names

I just took my first peek at VRTK 4 and the I came across "InteractorVisibilityModifierFacade".
I couldn't help be reminded of the notorious AbstractSingletonProxyFactoryBean ;-)
Would anything really suffer if was renamed InteractorVisibilityModifier ( or even "InteractorVisibilityMod") ? I suspect clarity and code aesthetics would improve if the "Facade" suffix was dropped throughout the framework with very little downside that I can see.
I am trying to imagine teaching use of VRTK to non-professional developers and I'm wincing at the thought of introducing these class names.
It might seem like a minor thing but naming matters and good APIs have good naming conventions. I'm a Python dev originally and this feels a bit too "enterprisey" for comfort

a InteractorVisibilityModifier is a class that would modify the interactor visibility
a facade class is not doing anything other than being a facade to underlying systems
that's why InteractorVisibilityModifierFacade is the correct name, because that class is purely a facade to the underlying systems.

I wasn't disputing it's correctness.

The facades work together with the prefab they come with. To prevent confusion between the

prefab
actual component this is a facade to
and the facade itself

we need a specific name. I'm not bound to "facade" but I don't see a better solution either. This shouldn't feel enterprise-y, it should feel like proper CS terms are used that can therefore be looked up easily in case a user never heard about the term before.

it should feel like proper CS terms

However, a large chunk of the (presumed) intended audience for VRTK aren't computer scientists. :) Unity supports a broad range of usage patterns and programming experience and the real hardcore devs are probably off rolling their own frameworks.
I'd have no real issue with the naming if it was only ever visible in the source - but because it's used in the inspector UI different standards should apply. It's part of your UI. You hopefully wouldn't give a UI control a label with 30 odd characters in it.
I guess my point is simply that any names visible in the Editor UI should be short, clear and natural-sounding.
(It's not just "noobs don't know what facades are!" either) Even to someone like me - it sends a bit of a negative signal about how approachable and cleanly designed the framework is going to be. A bit like buying a gadget and seeing the wires are sticking out of the box...)

I agree to a certain degree.
I am more than happy to discuss alternatives and I can't come up with any. The solution can't be dropping the "facade" suffix because my above explanation of the same prefix being used elsewhere.
If a user gets confused by a suffix I don't think we can help them, even with the planned detailed documentation.

If a user gets confused by a suffix

I'd dispute the term "confused" as it makes it sound like the user is at fault. Developers are often drawn towards elegance and simplicity in their choice of tools. I wouldn't characterize an aversion to verbosity as a flaw...
I haven't dug in deeply enough to be much help in suggesting alternatives but I'm pleased to see the new VRTK release has made so much progress. I've been stuck in native GoogleVR land for the last few months...

I think we're fine for now because the documentation and any instruction to the user will be:

Drag n drop the prefab named X into the scene
In the inspector set the following settings up

The latter is fine - there is only one component visible to the user on prefabs - the facade.
Once a user wants to drill down to any code they will need the term "facade" to understand it. There is no way around it and using proper terminology here will ensure the user doesn't get confused.

Closing the issue as we want to keep the repo clean, but discussions can continue on here.


[Jupyter] Bugfix: notebook path relative to server_root_dir

Jupyterlab users can configure the server_root_dir to be different than the CWD of the backend process

reading thru the context of what this fixes, would it make sense to default root_dir to JUPYTER_SERVER_ROOT rather than CWD?

reading thru the context of what this fixes, would it make sense to default root_dir to JUPYTER_SERVER_ROOT rather than CWD?

I tried that, but it appears that the JUPYTER_SERVER_ROOT is only set for the client and is unset for the backend process. It looks like server_root_dir is always set in the backend, and so defaulting to CWD is just to be overly safe


Upgrade metadata table to v4.0 fails on Derby

What version of Flyway are you using?
4.0
What database are you using (type & version)?
Apache Derby <IP_ADDRESS> - (1582446)
What operating system are you using?
CentOS7
What did you do?
I try to switch from v3.2.1 to v4.0
What did you expect to see?
Metadata table should be altered on first migrate call
What did you see instead?
Error code 30000, SQL state 42X01: Syntax error: Encountered "NOT" at line 1, column 69.

Thanks for the fix! Merged.


Fix failing test action in main

gotta do some debugging to figure out what went wrong. apparently it was all checkmarks until it merged into main which suggests its some kind of faulty cache logic 🤷♀

original run:

reran:

so it looks like its not getting added to PATH when NOT cached?


sap_hana_install: Replace ansible.posix.firewall

The firewall module is not part of ansible.builtin, so we should replace it.
We could either use the firewall role from the Linux/RHEL System Roles collection or use the command or shell module to run the firewall-cmd command.

Fixed in PR #84.


Mob stage issue

(Required) What is your Quests version / build number (do not say "latest")?
Quests-3.2.1
(Required) Please describe the problem and how to replicate it. Any console errors?
I made a quest for fighting mobs and I can start the quest. When I try defeating the mob however, it did not count the kill. The count is still 0/1

Thanks for using Quests! I was unable to replicate the issue, so unless you can provide a particular quest where this is happening, there isn't much I can do. You may use a site like Pastebin to post the data from your quests.yml file.


As a user, I want to use the sampleData API to load JSON data

The pixiedust.sampleData() allows for loading CSV data from a url. However, it does not support JSON data. Updating the API to support JSON can make it easier to load data from other sources (e.g., bCharts)

the sampleData API has been updated to allow loading of JSON data.
pixiedust.sampleData(dataframe, type='json')
where available options for type includes json or csv and defaults to csv when not included.
example,
import pixiedust

df = pixiedust.sampleData('https://raw.githubusercontent.com/ibm-watson-data-lab/open-data/master/cities/cities.json', type='json')

display(df)


Small optimizations to headers

There have been quite a few changes to that code in the time being, so this PR would need to get updated if we want to merge it through. Closing for now, but if you want to update and re-open feel free 👍


Add az container module

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[ ] Each new command has a test.

(see Authoring Command Modules)

@yolo3301,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

CI failed because missing azure-mgmt-container pkg. It's pending to be published.

@tjprescott All your comments are addressed except --no-wait option for creation and test cases. In the email thread, we have agreed to have test cases in a followup PR so that we can have az container merged and released first.
@lostintangent @derekbekoe Thanks for the feedback. I will address those comments along with the followup PR.

@tjprescott Forgot to mention that but I did reply in the comment. Our RP API doesn't support update yet. Will need to work on that later.

@yolo3301 your RP supports PUT, which is what generic update was designed for.  Every other RP in the CLI includes this command and it should be in this PR.

Merging. @yolo3301 will take a look at the remaining failing parts of the build.
It's the doc source map, and readme/HISTORY checks.


Make children prop so that it is not required

I would like to used the sidebar as a standalone component and be able to manage the app content separate.  This is possible right now, but it reports a warning that the prop 'children' is marked as required in the 'Sidebar'.

This way of using the library is not officially supported by the library right now. As I'm sure you've found out, you have change a lot of the default styling to make it work in a reasonable fashion (removing all the invisible overlays).
In the end the warning goes away in production mode. The warning is still annoying, but it doesn't prevent you from using the library how you like.


fix: move host-scanner namespace

Overview
In this PR we are moving the previous dedicated host-scanner's namespace (kubescape-host-scanner), to the current in use for kubescape operator (kubescape).
Additional Information
This is useful to avoid communication issues between namespaces when a policy engine is installed on the cluster.
How to Test
Build kubescape by your own from this branch and run it against a cluster with the following command: ./kubescape scan --enable-host-scan.
Check if host-scanner is deployed in kubescape namespace.
Checklist before requesting a review

[x] My code follows the style guidelines of this project
[ ] I have commented on my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my code
[x] If it is a core feature, I have added thorough tests.
[x] New and existing unit tests pass locally with my changes

I did not merge yet, I will like to merge only once our tests are ready.
Maybe we should remove the host scanner test just for this release so this release won't be blocked.

@alegrey91
in applyYAML function, we need to make sure we don't tearDownNamespace...

Yes, we already checked. The teardown function has a control that verify if the namespace was already present before host-scanner installation.

Doesn't it mean the namespace deletion clause in tearDownNamespace will never be reached?  Because if true, maybe we better just remove all this redundant code.

Thanks. This should break the system tests. Let's have a PR ready in the systemtests so we can merge the tests right before we release

Hi @dwertent, I tried to run this command in order to check for possible errors from system tests, but I didn't find any error: ./systest-cli.py -t host_scanner -b development --logger DEBUG --kwargs ks_branch="feat/add-log-coupling-for-host-scanner"
What could be the problem with this new fix in your opinion?


getDays function returns a floating number for dates between 3/10/2019 and 3/11/2019

Describe the bug
The momentjs is returning value 0.9583333333333334 when calculating number of days between 3/10/2019 and 3/11/2019
To Reproduce
Steps to reproduce the behavior:

Go to https://jsfiddle.net/vuycz14f/
Run JSFiddle
Note the value for label - Without Math.floor
It is 0.9583333333333334

Expected behavior
The value should be 1
Code -
var ad = moment("3/10/2019", "MM/DD/YYYY");
if (ad._isValid) {
var ds = moment("3/11/2019", "MM/DD/YYYY");
if (ds._isValid) {
console.write(moment.duration(ds.diff(ad)).asDays()); //expected - 1 ; actual = 0.9583333333333334
}
}
Desktop (please complete the following information):

OS: Windows NT: 10.0.16299
Browser Chrome
Version 74.0.3729.169

Moment-specific environment

The time zone setting of the machine the code is running on - CST - Central
The time and date at which the code was run - 5/24/2019 3:05PM

Please run the following code in your environment and include the output:
Fri May 24 2019 15:06:19 GMT-0500 (Central Daylight Time)
(index):44 5/24/2019, 3:06:19 PM
(index):45 300
(index):46 Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36
(index):47 2.24.0

+1 for this, was surprised to find someone else with the same issue (time zone PST, run just now).

Thanks for opening this report.
I commented at https://github.com/moment/moment/issues/5131#issuecomment-500325301 about the same issue.

Indeed it was a DST thing, switching the subsequent integer conversion from Math.floor to Math.round did the trick to my satisfaction.

It seems be fixed in the lastest code. I can't reproduce it at https://jsfiddle.net/vuycz14f/.


[Question] Adding / Creating groups in a community

Hi! is it possible to create a group in a community or add a group to a community? Given that I'm the admin.
Thanks!

Not yet :( We'll check that!

+1

+1


Change theme to master

Deliver fix commit to live branch to enable automatic index update for API Browser https://docs.microsoft.com/en-us/python/api/?view=botbuilder-py-latest

Docs Build status updates of commit 9398520:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update DP params and maximumPrivacyBudget for integration tests under…

… ACDP composition

Update default query DP params in integration tests so privacy budget will not be exceeded under ACDP composition
Update maximumPrivacyBudget in the privacyBudgetManager in InProcessEdpSimulator to realistic value
Document sample ACDP calculations in unit tests

This change is

src/main/kotlin/org/wfanet/measurement/integration/common/reporting/v2/InProcessLifeOfAReportIntegrationTest.kt line 1070 at r1 (raw file):
Previously, iverson52000 (Albert Hsu) wrote…
@riemanli  @tristanvuong2021 We need to update the DP params in this integration test to avoid exceeding privacy budget under ACDP. In this test, I saw sometimes the expectedResult.reach.value is 0 and actualResult is not because of noise, so the assertion assertThat(actualResult).reachValue().isWithinPercent(0.5).of(expectedResult.reach.value) will not work? The updated code is what I saw in other tests to handle this case? Does the change make sense to you?

Hey Albert thanks for bringing it up. I actually have a PR #1423, and the issue here should be resolved there.


python3.pkgs.setuptools-git-versioning: init at 1.13.5

Description of changes
This is used by several projects as a build-time dependency, and I would like to package it to give us options about how we should handle those cases. I did see https://github.com/dolfinus/setuptools-git-versioning/issues/77, and I'm not sure what the best way is yet.
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg build python310Packages.setuptools-git-versioning

Result of nixpkgs-review pr 248019 run on x86_64-linux 1

2 packages failed to build:

python311Packages.setuptools-git-versioning
python311Packages.setuptools-git-versioning.dist

2 packages built:

python310Packages.setuptools-git-versioning
python310Packages.setuptools-git-versioning.dist

error: builder for '/nix/store/kwriig3zcm1jq3x4qkfx2dg20yblzkk8-python3.11-setuptools-git-versioning-1.13.5.drv' failed with exit code 4;
       last 10 log lines:
       > Check whether the following modules can be imported: setuptools_git_versioning
       > pytestCheckPhase
       > Executing pytestCheckPhase
       > ImportError while loading conftest '/build/source/tests/conftest.py'.
       > tests/conftest.py:7: in <module>
       >     from tests.lib.util import create_file, execute, rand_str
       > tests/lib/util.py:13: in <module>
       >     import toml
       > E   ModuleNotFoundError: No module named 'toml'

Good catch, I didn't test it on Python 3.11. I can fix this upstream.

Oh, it uses toml in tests to write, which is not in the Python 3.11 standard library. So we've got to add the dependency in our derivation.

I'm building the whole bootstrap right now from staging.

Sounds like hard work. 😵

Sounds like hard work. 😵

For my computer 🥲

I verified that the tests pass on Python 3.11 now after adding toml to nativeCheckInputs. Let's kick it off again:
@ofborg build python310Packages.setuptools-git-versioning python311Packages.setuptools-git-versioning

Result of nixpkgs-review pr 248019 run on x86_64-linux 1

4 packages built:

python310Packages.setuptools-git-versioning
python310Packages.setuptools-git-versioning.dist
python311Packages.setuptools-git-versioning
python311Packages.setuptools-git-versioning.dist


UPC Code Scanner Unimplemented

Due to time and resource constraints; this item has been bumped to the next iteration due to its low priority

Due to iteration 4's focus on bug fixes, this story has been removed from the scope of the project


Documentation example has an error

In the documentation at https://select2.github.io/announcements-4.0.html, the following snippet has an error:
var $element = $('select').select2(); // the select element you are working with

var $request = $.ajax({
  url: '/my/remote/source' // wherever your data is actually coming from
});

$request.then(function (data) {
  // This assumes that the data comes back as an array of data objects
  // The idea is that you are using the same callback as the old `initSelection`

  for (var d = 0; d < data.length; d++) {
    var item = data[d];

    // Create the DOM option that is pre-selected by default
    var option = new Option(data.text, data.id, true, true);

    // Append it to the select
    $element.append(option);
  }

  // Update the selected options that are displayed
  $element.trigger('change');
});

The line with var option = new Option... should read:
    var option = new Option(item.text, item.id, true, true);

This was fixed in https://github.com/select2/select2/pull/3547.
In the near future I'll be pushing a docs update which will include this.


After loading the id attribute is missing

After loading a SVG file the id attributes are missing from the loaded SVG file.
Before:

After:

Is there any way to load the svg together with the id attributes?

Hey @Rednas83, came here with the same problem.
Using this option with SVGO in your webpack config keeps the IDs: https://github.com/visualfanatic/vue-svg-loader/issues/60#issuecomment-441359653
{
  test: /\.svg$/,
  loader: 'vue-svg-loader',
  options: {
    svgo: {
      plugins: [
        { cleanupIDs: false },
      ],
    },
  },
},

If your project is bootstrapped using the Vue CLI and you're using vue-cli-plugin-svg-loader, you can use this in your vue.config.js:
pluginOptions: {
  svgLoader: {
    svgo: {
      plugins: [{ cleanupIDs: false }]
    }
  }
}

Please follow @2xAA solution, IDs are "cleaned" by default by SVGO.


Problem with images

Hi,
I have tried to include an image into a blog post:

= ... baking bread
:hp-tags: bread
== Recipe 1:

1000 g flour (wheat or spelt)
60% - 65% water (60% with spelt)
2% salt
yeast

Knead, proof over night, pre-heat oven (incl. baking stone) and a cast iron pot with lid (Dutch oven) to 265 C or the maximum temperature of you oven.
Form the loaf and proof (on a sheet of baking parchment) until well risen.
Move loaf with the parchment into the pre-heated pot, return to the oven, turn down the oven to 250 C and bake for 1 hour.
image::https://goo.gl/photos/Y3Me5nvBQ9xfdHsp9[Fresh Loaf]

As you see, the image does not render. Where did I go wrong?

Hi @thomaszahr
The url point on a google page, not on  an image file.
Could you try with this url https://lh3.googleusercontent.com/vn3bs-PMEBTTnDjQdQl_rN655mNtUZtoabAGbNqiB_U3qqx1irQ02nLiz3Anbl4RXgHOTsgqcny_OYZTXQ5SRaG2KWTbuJxZSd0wuU5-hWP3CmcZ77t-Qkjmz9N4glnK69clapk=w716-h954-no ?

thanks, that was it.

🎉🎉


I wish that g.Log() can provide similar functionalities to the WithField and WithFields functions of the logrus library.

I wish that g.Log() can provide similar functionalities to the WithField and WithFields functions of the logrus library.

@im-pingo I think you can use SetPrefix for the Logger, after then each logging content will print logging content with your custom prefix.


Add support for place=province equivalent to place=state

This adds support for place=province nodes, giving them the same label text treatment as already supported place=state nodes.  The status quo for Canadian provinces is that their place nodes have been tagged place=state but should they be changed to place=province we'd still want labels on the map.   It looks like place=province is currently used in a few other countries including Turkey, Thailand, and Japan.  We should make sure these are direct country subdivisions before merging this.

Confirmed that this works on the current planet (before restoration of place=state nodes).
I think this can be done a bit more compactly with a single "in" expression, something like:
filter: ["in", ["get", "class"], "state", "province"]

Here's a overpass query showing all place=province nodes worldwide: https://overpass-turbo.eu/s/1V25
It looks to me like the place=province nodes are used consistently across Turkey, Thailand, South Korea, and Japan to represent direct national subdivisions.  Beyond that, the tag is used sporadically in Italy, Saudi Arabia, Burundi, and Peru.  These uses are less clear to me but there are only a few of them.  place=province is clearly documented as being for "a subdivision of a country similar to a state".  So I'm fairly confident this is a good change and if any current uses are for lower level divisions they should be changed anyway.


Multi-client support for Robustness framework

Looks ready except the last requested change in simple_test.go

We'd like to start tracking upstream master to avoid divergence as much as possible.
@rahulchheda Please change the base branch to master and also resolve the conflicts. Thanks.


Look of the OOTB empty SaaS offering section

Are we happy with the way the empty SaaS offering section looks?  If we are shipping both origin / OCP with nothing in that section (which is the current plan) then this is what everyone will see when they install openshift OOTB.

cc @sspeiche @serenamarie125 @cshinn @spadgett @smarterclayton

@cshinn had some changes to add a margin around the catalog which made it look better visually.  Chris did you put up a PR for that?

ah right i remember that, it allowed some of the background to show through around the edges, that would probably help

I don't have a super strong opinion one way or the other on this. Might be worth checking with visuals.

i think having the background image take up most of the screen like in your third screenshot is a bit much, can we have the white extend closer to the bottom and have a consistent margin going all the way around left/bottom/right?

@jwforres something more like this?

yeah, its a lot of white, im not sure which is better :-\

@jwforres I just had someone ask if the background image is customizable.  It is, correct?
imo, I'd go with the background image.  As this becomes customizable, if we had the SaaS area under Browse Catalog, we would want it to take up as little space as needed.

On Tue, May 2, 2017 at 3:10 PM, Serena Doyle<EMAIL_ADDRESS>wrote:

@jwforres https://github.com/jwforres I just had someone ask if the
background image is customizable. It is, correct?

It is because in theory all of our CSS can be overridden by extension CSS.

imo, I'd go with the background image. As this becomes customizable, if we
had the SaaS area under Browse Catalog, we would want it to take up as
little space as needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin-web-catalog/issues/198#issuecomment-298731698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZk7XWrPJUDXeYUolGQcZ1D1cM8-Gqdks5r13-UgaJpZM4NORfj
.

@jwforres @cshinn -
I think there should be more space above and below those four selectable application types, and those four icons should be slightly smaller. Right now, they seem a little crowded.
Also, to help out in the case that there is just one catalog item or row of items shown (as in Chris's third screenshot), it might be nice to have a minimum of two rows-worth of white container space. This would help the ratio of background:white container.

@jwforres @cshinn
Here is what I mean by always having at least 2 rows of white container space (I know that these catalog items are not aligned with CI/CD, but this is just for visual illustration purposes):

(Basically, even if there is only one row of catalog items, there is at minimum two rows worth of container space. This helps to balance the space out when there are no selectable application types at the top.)

@jennyhaines having the two rows of white looks great! One quick question, can we still have the blue borders on the right and left sides like @cshinn has?  If so, do you mind adding the side margins to your mock? Let us know what you think.

+1 @beanh66 I think the look with the margins is nicer.

@beanh66 @serenamarie125 @cshinn - Here it is with the margin included. I think this also looks nice!

I think we may be on the road to Abilene here. Do we prefer the image at the bottom to the white background? @serenamarie125 @kybaker @jennyhaines @rhamilto @jwforres @beanh66

I'd like to see what the visual designers come up with given the new requirements.  I'm not sure any of the modifications to the existing design are successful.

@cshinn @rhamilto - I think that the last of the options (with the minimum 2 rows or whitespace) is the most successful from a visual standpoint because the white does not completely overtake the page, nor does it look so small that the blue background overtakes everything.

My personal inclination is towards the initial version, (white background) but I think the bordered version looks good as well. @rhamilto out of curiosity, which new requirements did you have in mind?

@cshinn I think I like what @jennyhaines is suggesting the best.

I think we may be on the road to Abilene here. Do we prefer the image at the bottom to the white background?

For what it's worth, I prefer the current style (white background). The edge to edge white looks better to me when there's more content in the catalog, which hopefully is the normal case. We'll also be showing the templates, not just the builders, now that we've finished https://github.com/openshift/origin-web-console/pull/1492

Is this considered done now that #261 merged?

i think we still have an issue left in IE11 based on the comments in #261  i'll update the title and reduce to a p3

will also remove from the 3.6 milestone, not urgent that we fix this

Reviving this discussion as the release of 3.7 is drawing near.  Here is an updated screenshot of origin:

Note the background image may change with https://github.com/openshift/origin-web-catalog/pull/541
Are we good with the way the way things look and can close this issue?

@rhamilto Is that how it looks on IE11? I think the IE11 bug was the only remaining concern.

@rhamilto Is that how it looks on IE11? I think the IE11 bug was the only remaining concern.
Looks ok to me.

I think this is fixed then. Closing the issue. If anyone disagree, please comment or reopen.
Thanks @rhamilto


Telegraf show wrong CPU temperature

Telegraf shows the wrong CPU temperature in Grafana.
CPU:

GPU:

You are totally right,

cpu_temperature returns milli celcius as an integer.
gpu_temperature returns celcius as a float

to get the proper CPU temperature in celcius you can use this...

Works! Thanks!

@PatrickScheich happy to merge a PR on this for the v1.7.1


请问近期有制作pycharm插件的开发计划嘛？Are there any plans to develop a PyCharm plugin in the near future?

如题，我的开发环境更多的是是在pycharm下
My development environment is mostly in PyCharm.

Hi, sorry for the late response. But we at the company don't have a plan for PyCharm yet. The nearest possible timeline should be in six months. Of corse, if community developers make one sometime, that would be best.