One-Time Secret (Independent Publisher)

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[X ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[ X] I attest that the connector works and I verified by deploying and testing all the operations.
[ X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[ X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[ X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[ X] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ X] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ X] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ X] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ X] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree

Hello @alduzzen1985,
Thank you very much and congratulations on your new submission. Our Certification Engineers will review it within 1-2 weeks.
Please let us know if you have any questions.
Thank you very much again for working with us.

@alduzzen1985 thank you so much for working hard on this connector. As we ask all our independent publisher to verify their connector testing by providing screenshots. May i ask you please to provide some screenshots showing your connector testing?
Thank you so much.

[[certify-connector]]

Hello @alduzzen1985,
I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

Hello @alduzzen1985,
I hope you are doing well.
Your connector is in production deployment and queued up for the next deployment schedule. This process typically takes 3-4 weeks. Please note that the documentation for your connector will not be generated until the deployment process is in the final steps.
Please let us know if you have any questions.
Thank you very much for working with us.

Hello @alduzzen1985,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.


Consensus module batching to save gas

Background
Given that gas on Etherium is quite expensive we should implement batching of arbitrary items in the consensus module. It should be optional and not every queue item should require. E.g. for now the only usecase is to batch items for the evm arbitrary logic execution.
Proposal
Instead of simply batching jobs by the time they have arrived, we should give our users a bit more freedom so they could define a minimum batch size they want to be a part of. If there are only 4 jobs in the queue and one of the jobs has a minimum batch size parameter set to 5, they wouldn't be a part of the current batch. If those 3 other jobs have minimum batch size set to <=3, then all those 3 would be a part of a new queue. Given the nature of our scheduler, our customer's jobs could be spawned every couple of minutes and it might be too expensive for them to be "alone" in the batch if they are the only one. With this, we give them control so they can choose the minimum batch size which is the best case for them and how much they are willing to pay for gas.
If one job was too long in the queue because no queue was found, then we give the user control to either: cancel the job or add it to any available queue of any size.
Done when

[ ] there are new methods in a consensus module that are supporting batching

It's important to keep in mind that the gas savings that are gained by batching are those that are associated with bridge overhead, mostly validator signature evaluation. You might want to think about how much signature evaluation costs in comparison to typical jobs. If the majority of gas costs are incurred by the jobs themselves, this is less useful.
Another thing to think about is how valuable a typical job is. If the job is very valuable, then gas cost does not matter as much.
Another thing to think about is how timely a typical job must be. If it must be very timely, then the user will not want to risk having to wait for a batch.
I personally would skip this batching idea until you have more information on how useful it would be.

That being said, it seems relatively simple and well suited to the use case.

@Vizualni I align here that we may be overoptimizing ahead of getting everything else we need to get done. Although the risk of losing course for Friday is low, let's leave this for after we conclude the current effort. It's a nice-to-have, but not critical and maybe not clear how it will be best used in this moment.

This is done.


Make the delete button more obvious

Tried a bunch of tab managers, all were OK but flaky and didn't work correctly for one reason or another. This one, Tab Manager v2, was the ONLY extension that worked pretty much 100% out of the box. While I can think of a few UI tweaks to improve (like making the "delete" button more obvious for closing tabs), it's very decent and has become invaluable for me. Well done!

I plan to add a delete button when the user hovers on a tab.

Fixed in 9444bc43ca995ee4506c07df778594b6b3574d9d


brew: pass through TRAVIS_ variables.

My guess is this will allow code coverage to be submitted again.

My guess is this will allow code coverage to be submitted again.

It did.


detect() returns empty list if video has no cuts

I used the example code
scene_list = detect(path, ContentDetector())

for some videos like this one, however I got an empty list. Obversly there is one scence in the video and I expect to get at least one element. I don't  know whether it is a bug or due to misuse.

To always get at least one scene. you can use a SceneManager and set start_in_scene to True when calling get_scene_list:
video = open_video(video_path)
scene_manager = SceneManager()
scene_manager.add_detector(ContentDetector())
scene_manager.detect_scenes(video)
scene_list = scene_manager.get_scene_list(start_in_scene=True)

The default behaviour of the API is to not return any scenes if no cuts were detected, in order to be more consistent with ThresholdDetector.  For the next release I'll add a start_in_scene argument to detect, but for now you can use the above snippet.

Fixed in v0.6.1 branch, will be included in next release of PySceneDetect. Thanks for the report.


Adding Back to Top Button

I am interested to solve this issue

i want to work on this issue under jwoc label


[RFC] Add support for bgcolor, fontcolor and frameopacity

This changes the default background style.
This also slightly changes the highlighting behavior.
If you are satisfied with this change, I will add the tests.
Closes #40

Codecov Report

Merging #48 into master will decrease coverage by 3.92%.
The diff coverage is 76.00%.

@@             Coverage Diff             @@
##            master      #48      +/-   ##
===========================================
- Coverage   100.00%   96.07%   -3.93%
===========================================
  Files            2        2
  Lines          155      153       -2
===========================================
- Hits           155      147       -8
- Misses           0        6       +6

Impacted Files
Coverage Δ

src/ProfileSVG.jl
94.79% <50.00%> (-5.21%)
:arrow_down:

src/svgwriter.jl
98.24% <93.33%> (-1.76%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #48 (f7c4bd1) into master (409d541) will decrease coverage by 0.54%.
The diff coverage is 96.55%.

@@             Coverage Diff             @@
##            master      #48      +/-   ##
===========================================
- Coverage   100.00%   99.45%   -0.55%
===========================================
  Files            2        2
  Lines          162      185      +23
===========================================
+ Hits           162      184      +22
- Misses           0        1       +1

Impacted Files
Coverage Δ

src/svgwriter.jl
98.36% <93.75%> (-1.64%)
:arrow_down:

src/ProfileSVG.jl
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Question: how about jsonslicer?

Since you have comparisons with a couple of alternatives, which is very useful: have you considered adding a comparison to https://github.com/AMDmi3/jsonslicer?

why not!
updated readme.

Lovely, thank you!


set nullPointMode to null as default

/assign @oxddr

/assign @mm4tt @jkaniuk

/ok-to-test
/lgtm
/approve
Thanks! This is great


Redis instead of RocksDB ?

Do you think it would be possible to use Redis instead of RocksDB as a key/value store ?
Has any work been already carried out on the subject ?
If yes, is this work publicly available ?
If not, could you provide pointers (in the code) to look at ?
Many Thanks

The interface to RocksDB is https://github.com/openblockchain/obc-peer/blob/master/openchain/db/db.go. It uses column families and snapshots which are specific to RocksDB. Wrapping these in interfaces so OBC can potentially support other DBs more easily is probably a good idea.
Why are you interested in using Redis over RocksDB? I usually think of Redis as a fast remote in-memory store where as OBC needs an embedded key/value store that is persisted to disk.

Closing for now. Please reopen if you wish to discuss further or need more info.


add xiaokang_zhang info

Add Xiaokang Zhang's information in source/people/main.rst
Add a profile of Xiaokang Zhang. source/people/xzhang.rst
Add a picture of Xiaokang Zhang. source/people/xiaokang_zhang.jpg

This looks good to me @zxkjack123. Thanks!
I'll let @gonuke merge once he's had a chance to look over your changes as well.

Looks good to me..  - merging and publishing.  Thanks @zxkjack123


Pretty docstring printing

This PR resolves the feature issue #123 . I modified the iterate_flattened_separately utility function to enable looping over a manually sorted dictionary. This allows me to print the docstring at first in every configuration child dictionary.
The prettified doc printing is implemented in the _format_entry function where the docstring is handled individually. As suggested I used grey for the colored output which is also part of the legend now. Also the configuration entry specific documentation is now printed grey.

The failing integration check does not to be caused by my changes. Am I right?

Coverage decreased (-0.1%) to 87.925% when pulling b45be70f719a252d23047bd0e3e78e46e60eb2ba on timmeinhardt:pretty_docstring_printing into 8d16197f88d01ab8521c872e0be7b902d8ce545d on IDSIA:release/0.7.0.

Coverage decreased (-0.02%) to 88.033% when pulling 766abbff583646285c920da79fa504910982f084 on timmeinhardt:pretty_docstring_printing into 8d16197f88d01ab8521c872e0be7b902d8ce545d on IDSIA:release/0.7.0.

Hi, thanks for your work. The PR looks pretty solid to me. I quite like the fact that you also changed the color of the inline comments. :+1:
There is just one small detail, which I might want to fix at some point: the __doc__ entry is now still part of the configuration. That means it is e.g. cluttering the database. I think eventually it would be nicer, if __doc__ was only used for printing the config, but not stored anywhere. But that is a detail, and can wait. :-)

No worries. I am happy that I could contribute to your framework!
Actually I thought about removing the __doc__ from the dictionary but was not sure whether this is in your interest. Another thing I noticed is for code written with your framework to achieve a high linting score one has to deactivate several warnings. E.g. the unused-variable warning in every configuration function. This can either be done globally or with inline blockwise disable comments. If deactivated inline a # pylint:disable=unused-variable comment is currently treated as an inline comment and therefore printed as part of the configuration.

Hey, thanks for the hint. I've just added a filter for these IDE and linter directives.


Support for webpack-dev-server in development mode

The s2i run script only supports nodemon for hot deployments when DEV_MODE=true.  To use webpack-dev-server, I can set DEV_MODE=false and then override NPM_RUN but that results in my build and deploy env using different values for DEV_MODE and NODE_ENV.
Perhaps the run script can be updated with a new environment variable so hot deployments can be started with a different package than nodemon.

would it make more sense to use the centos7-s2i-web-app image?  You still would need to override the NPM_RUN variable in the run script
The only "requirement" here is that in the assemble script, it runs "npm run build", so you would need that defined

Looks like that will do the trick - I hadn't seen that image as it doesn't look like it's listed in the OCP instance I'm using.  Thanks.


charts/ui: allow setting custom registry

We were relying on the custom registry value used for s3gw, but we may want to use a different one.
Signed-off-by: Joao Eduardo Luis<EMAIL_ADDRESS>

better to adjust the values.yaml file to include a reference to this option before merging.


Upgrading sncRedisBundle from 3.6 to 4.4

Hi, I am currently upgrading my project versions and thus, sncRedisBundle.
Was previously running on 3.6, all fine but I cannot seem to find any documentation regarding how to upgrade the doctrine caching.
This was my previous :
snc_redis:
   clients:
     # Define your clients here. The example below connects to database 0 of the default Redis server.
     #
     # See https://github.com/snc/SncRedisBundle/blob/master/Resources/doc/index.md for instructions on
     # how to configure the bundle.
     default:
       type: "predis"
       alias: default
       dsn: "%env(REDIS_URL)%"
     doctrine:
       type: "%app.redis_type%" # use parameter instead of env because snc-redis does not work
       alias: doctrine
       dsn: "%env(REDIS_URL)%"

services.yaml :
   App\Service\RedisClient:
    lazy: true
    class: App\Service\RedisClient
    arguments<EMAIL_ADDRESS>'%enable_redis%']

Nothing in the cache.yaml
But snc_redis no longer supports doctrine in that way.
Could use some help on how to make it work with this current version ?
Many thanks !

Hi, this is addressed in https://github.com/snc/SncRedisBundle/blob/master/UPGRADE.md. What exactly you struggle with?

Hi,
Thanks for the answer.
Setting up the cache pools to make it work like previously is what I'm struggling with.
Cant seem to find where it is explained.
Also, are there other changes that are required for the bundle to work ?

You should read https://symfony.com/doc/current/reference/configuration/doctrine.html#caching-drivers  and https://symfony.com/doc/current/cache.html
Here is a simple example
snc_redis:
   clients:
     default:
       type: "predis"
       alias: default
       dsn: "%env(REDIS_URL)%"
framework:
  cache:
    pools:
      cache.doctrine:
        adapter: cache.adapter.redis
        provider: snc_redis.default
doctrine:
  orm:
    query_cache_driver:
      type: pool
      pool: cache.doctrine


[Bug] Mysql JDBC Catalog  limit 10000 offset 5000 无法下推

Search before asking

[ ] I had searched in the issues and found no similar issues.

Version
2.11
What's Wrong?
select * from mysql.db.table   limit 10000 offset 5000 ;
下推查询为
select * from mysql.db.table   limit 15000；
与实际预期不符。

No response
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

/attempt #33603


typo fix

closes #17.

I've forgotten why we don't return the Room object upon creation here, but I'm sure there's a good reason.


Provide an example of execution code ?

Hello,
I have a translation.json file that I would like to translate in several languages, I have my google API credentials. But I'm not familiar with java.
Would you mind providing an example of working code (a simple "how-to") to accomplish this task?
Thks for sharing !

The API enum is not exposed which is a problem.


the document is not right

the document uses httpbin site as example
but the examples are not right;
HttpResponse response =Unirest.get("http://httpbin.org/get?shuju={fruit}")                 .header("Content-Type", "application/json")                 .routeParam("fruit", "apple")                 .asString();
in the document lack "/get?shuju="

httpbin has been removed from the examples


Cannot detect handleFileInput complete

When I upload multiple files, I need to wait for the serialization to complete before calling the upload interface. But I have no way of knowing if handleFileInput completes.
Maybe handleFileInput could return a Promise?

sounds like a good addition, will work on it for the next version

@siaikin update the module to 0.2.7 to use this feature, tell me if it fits your usecase so I can close this comment. Hope this helps!


feat: add generator for virtual piece loader

Add loader file generator command for virtual pieces of<EMAIL_ADDRESS>PR Inspired by - https://discord.com/channels/737141877803057244/1049419304405311564/1175132383033438218

@sapphiredev pack

Tested with a newly generated project:


Add Gitlab Container Registry

I have tested cosign for gitlab container registry and work!
My verify result:
$ cosign verify -key cosign.pub registry.gitlab.com/eminks/denemler:latest
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key
  - Any certificates were verified against the Fulcio roots.
  - WARNING - THE CERTIFICATE EXPIRY WAS NOT CHECKED. set COSIGN_EXPERIMENTAL=1 to check!
{"Critical":{"Identity":{"docker-reference":""},"Image":{"Docker-manifest-digest":"sha256:c93fa5b332de47c9f031284c7aa7a95988536e515571b73fa6294a0f54b289aa"},"Type":"cosign container signature"},"Optional":null}

Based on: #40

Thanks! This is great!


Generated spec does not preserve property order in structs

Problem
When generating a spec from code, the order of properties in structs are not preserved.
Input
main.go
package main

type MyStruct struct {
	One   string
	Two   string
	Three string
}

// swagger:response MyStruct
type swagRespMyStruct struct {
	// in: body
	Body MyStruct
}

func main() {}

swagger generate spec -o swagger.json
Output
...
    "MyStruct": {
      "type": "object",
      "properties": {
        "One": {
          "type": "string"
        },
        "Three": {
          "type": "string"
        },
        "Two": {
          "type": "string"
        }
      },
...

Expected Output
...
    "MyStruct": {
      "type": "object",
      "properties": {
        "One": {
          "type": "string"
        },
        "Two": {
          "type": "string"
        },
        "Three": {
          "type": "string"
        }
      },
...

Possible Solution
Maybe tags can be used to sort them?
type MyStruct struct {
	One   string `x-order:1`
	Two   string `x-order:2`
	Three string `x-order:3`
}

Environment
swagger version: master
go version: go1.11.5 linux/amd64
OS:  Debian 8.11 linux/amd64

This was recently merged: https://github.com/go-swagger/go-swagger/pull/1907

Is it a duplicate of #125?

@AlekSi no it is not. Generate spec and Generate Models do not work the same way and don't share much.


selector does not need to match metadata.labels

I don't think it's the case that if specified, .spec.selector must match .spec.template.metadata.labels, or it will be rejected by the API.
This stackoverflow question is a good example of why you might want them different: https://stackoverflow.com/a/39474037/42754

Fixes https://github.com/kubernetes/kubernetes.github.io/issues/4346

This change is

I signed the CNCF CLA.

Aha, oops. Thanks for correcting me. I'll try rewording it

I'll reopen when I have reworded.

After giving it some thought, I'm unable to come up with better wording. I think it's best left as it is. Thank you @janetkuo for explaining it to me.

@tomfotherby feel free to cc me in your new PR


Autofix: SizeOfRawData not being set in final PE in some cases.

Modified the check_section_compression function to update the SizeOfRawData of the biggest section after removing bloat. This ensures that the PE is not malformed when using tactic 7.

[!CAUTION]
Disclaimer: This fix was created by Latta AI and you should never merge before you check the correctness of generated code!
The fix provided by Latta AI might not be complete and it can serve as an inspiration.

This bug was fixed for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt fixing issues on your repository, you can block this account.

Solution doesn't work.
Solution not suitable to the problem.
Problem has been fixed.


dear author

could you support class NSPointArray NSHashMap NSMapTable?

Hi @BetrayalPromise,
Sure, I'm happy to add support for more collections. Can you be a bit more specific, which helper methods would you need for those classes you mentioned?
Thanks!


python setup.py develop ERROR

when I ran "python setup.py develop python setup.py develop --CMAKE_PREFIX_PATH home/minjun/Projects/RAISIM/raisimLib/raisim/linux/" in terminal, an error came out.
(raisim) minjun@minjun:~/Projects/ME491_2022_project$ python setup.py develop --CMAKE_PREFIX_PATH /home/minjun/Projects/RAISIM/raisimLib/raisim/linux/
running develop
/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running egg_info
writing raisim_gym_torch.egg-info/PKG-INFO
writing dependency_links to raisim_gym_torch.egg-info/dependency_links.txt
writing requirements to raisim_gym_torch.egg-info/requires.txt
writing top-level names to raisim_gym_torch.egg-info/top_level.txt
reading manifest file 'raisim_gym_torch.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'raisim_gym_torch.egg-info/SOURCES.txt'
running build_ext
-- pybind11 v2.9.0
-- Found OpenMP_C: -fopenmp
-- Found OpenMP_CXX: -fopenmp
-- Found OpenMP: TRUE
CMake Error at CMakeLists.txt:71 (find_package):
Could not find a package configuration file provided by "raisim" with any
of the following names:
raisimConfig.cmake
raisim-config.cmake

Add the installation prefix of "raisim" to CMAKE_PREFIX_PATH or set
"raisim_DIR" to a directory containing one of the above files.  If "raisim"
provides a separate development package or SDK, be sure it has been
installed.
-- Configuring incomplete, errors occurred!
See also "/home/minjun/Projects/ME491_2022_project/build/temp.linux-x86_64-cpython-310/CMakeFiles/CMakeOutput.log".
Traceback (most recent call last):
File "/home/minjun/Projects/ME491_2022_project/setup.py", line 68, in
setup(
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
return run_commands(dist)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
dist.run_commands()
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 968, in run_commands
self.run_command(cmd)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/dist.py", line 1217, in run_command
super().run_command(command)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 987, in run_command
cmd_obj.run()
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/command/develop.py", line 34, in run
self.install_for_development()
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/command/develop.py", line 114, in install_for_development
self.run_command('build_ext')
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 319, in run_command
self.distribution.run_command(command)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/dist.py", line 1217, in run_command
super().run_command(command)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 987, in run_command
cmd_obj.run()
File "/home/minjun/Projects/ME491_2022_project/setup.py", line 38, in run
self.build_extension(ext)
File "/home/minjun/Projects/ME491_2022_project/setup.py", line 65, in build_extension
subprocess.check_call(['cmake', ext.sourcedir] + cmake_args, cwd=self.build_temp, env=env)
File "/home/minjun/anaconda3/envs/raisim/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '/home/minjun/Projects/ME491_2022_project', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/home/minjun/Projects/ME491_2022_project', '-DPYTHON_EXECUTABLE=/home/minjun/anaconda3/envs/raisim/bin/python', '-DCMAKE_PREFIX_PATH=/home/minjun/Projects/RAISIM/raisimLib/raisim/linux/', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.

Is this a typo when I ran "python setup.py develop python setup.py develop --CMAKE_PREFIX_PATH home/minjun/Projects/RAISIM/raisimLib/raisim/linux/" in terminal, an error came out.?
If not check if you have entered the correct directory.  type cd home/minjun/Projects/RAISIM/raisimLib/raisim/linux/ and check if the directory really exists.


Consider using fmt library as a placeholder until we can use C++20 mode.

The existing code makes use of printf-style formatting of error / screen message strings. These are awkward since the byte length of a long differs between posix and Windows, leading to the use of very ugly macros (or worse, plain wrong code).
C++20 solves this (and soo many other things) with the introduction of the format library as part of the Standard Library.
It's available as https://github.com/fmtlib/fmt, and is included in eg spdlog as well. It supports gcc 4.8 upwards (C++11), but is available in a C++98 version as well.

We have updated to modern compilers which have C++20 format available natively.


#6706 New token providing ShellSettings.RequestUrlPrefix

Solves this issue https://github.com/OrchardCMS/Orchard/issues/6706

SettingsTokens class provides tokens for SiteSettings data and with this pull request also to RequestUrlPrefix that is within ShellSettings not in SiteSetting. Do you think it is better I move ShellSettings to another class?
I didn't did it because the other property of ShellSettings are more dangerous to offer through a token (security reasons). So to offer only a token that it is also a Setting I decided to put it in the same class.

I thought this feature worked properly however I have seen that ShellSettings.RequestUrlPrefix always returns null when it is resolved when the token is going to be replaced.
The following url: ~/{ShellSettings.RequestUrlPrefix}/mypage was translated after execute tokesn to ~//mypage because ShellSettings.RequestUrlPrefix returns null.
The funny thing is I didn't notice that because this is translated to ~/RequestUrlPrefix/mypage
So, the reason I didn't noticed it didn't work is the same that shows it is useless the feature I proposed.


Add new dashboard for fluent-bit

How to categorize this PR?

/area logging
/kind enhancement
/priority normal
What this PR does / why we need it:

Prometheus scrapes metrics from fluent-bit
New dashboard added for fluent-bit.
Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
@vpnachev @vlvasilev
Release note:

There is new dashboard for fluent-bit in garden's Grafana

/status author-action


[ar] Update Arabic localization of tag strings

Describe your changes
This pull request will update the Arabic localization strings
for all tag and tag-search related terms.
Related issue number or link (ex: resolves #issue-number)
No issue assigned.
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@arezk84 LGTM

هل لديك أية تعليقات أ/@arezk84؟


Update path

Hi first of all, thanks for releasing ReLinker!
Pleaes correct me if I am wrong here: I noticed there's no way to update the app once ReLinker has been applied.
In #71 it only checks whether the workaroundLib file exists but not if the Version matches, (e.g. after the App was updated and the native interface may have changed).
In snipped linked in your article the Chromium folks seem to have worked around this by unpacking the library once on every app start.

Hi there,
You can update your app with ReLinker, you just need to take care of versioning yourself. It is true that ReLinker will not extract the same library name twice, so the easiest way to setup some sort of versioning system is to append a version number to the library name.
In general, I feel that versioning is outside the scope of this project.

@janseeger Hi there. I've gone ahead and added versioning support with #11


Speed up merkle tree growth

This PR dramatically reduces the time needed to grow the MerkleTree object, allowing block syncing in snarkOS to happen in a reasonable time frame. Only when the new leaves share nearly no ancestors a large portion of the tree needs to be rebuilt, otherwise a lot of the pre-exsting hashes can be reused.
The results of this change were validated by using both MerkleTree::{new, rebuild} when synchronizing blocks and comparing the trees; no issues were found for the first few thousand blocks taken from the testnet. snarkOS tests also pass with MerkleTree::rebuild implicitly being used in tests (when blocks are committed).
In addition, memory use in MerkleTree::new is reduced by using an ExactSizeIterator instead of a slice for the leaves argument.
A snarkOS-side PR will follow once a new version of snarkVM is released.
Fixes https://github.com/AleoHQ/snarkOS/issues/459.
A comparison of the currently used MerkleTree::new with the new MerkleTree::rebuild:

Added 2 commits with extra optimizations that provide an additional ~19% average perf improvement; used a logarithmic scale this time so the difference is easier to see:

I've run synchronization for a bit longer (53k blocks, 21 minutes) and MerkleTree growth complexity seems to be logarithmic (as opposed to linear) now:


Progress bar does not disappear after fast network response

I found a problem with the new, latest version (8.0.3) where the progress bar does not disappear after a fast network response (also the style goes beyond a with of 100%).
The problem seems to be related to the ProgressBarDelay and the order in which events are fired.
With the default delay of 500ms and a response under 500ms, the progress bar remains. By reducing the delay (Turbo.setProgressBarDelay()) or artificially slowing down the request by throttling, the problem disappears.
This issue is maybe related to #1153.

@calleluks this doesn't ring a bell, but I'd love to chase it down.
I haven't seen this at all, do you have any way to consistently reproduce it ? Could you provide a minimal reproduction example?
If I understand correctly, the response has to be slow enough to trigger showing the progress bar, but fast enough that it should be instantly discarded ?

Thanks @Intrepidd, I really appreciate it!
Unfortunately, I'm having trouble coming up with a minimal example... I'll let you know as soon as I succeed!

I'm seeing the same issue with a 3ms request and I can reproduce it reliably with my app. It's a golang backend using Turbo and Stimulus on the frontend. Would that be a useful reproduction if I can cut it down to a minimal example?

I guess so! I'm wondering if I should be able to reproduce with no backend at all and just html files,or a python simple http server backend. Maybe my machine is not fast enough.
I'll try to reproduce this way but any other reproduction is welcome

I tried to reproduce by navigating back and forth between 2 very fast pages but could not replicate the issue.
Do you see it happen on a simple visit ? Are there any HTTP redirections involved ?

We're also seeing this with Turbo 8. We have a bunch of regression screenshots as part of our test suite, some of them now contain the progress bar at the top which wasn't the case before. We'll look into this and see if we can find a way to reproduce it.

Update: After a little digging, we saw that in our case, this only happened in the test environment. We were using lolex (now called @sinonjs/fake-timers) to advance JS time inside our tests. Per default, lolex overrides a whole lot of timing functions, which I believe caused these issues (the Turbo progress bar uses setIntveral for example). We have now replaced lolex with some simple JS and the problem seems to be fixed for us.


KeyError: 'wkb'

I am still using geosnap 0.5.0 because I was never able to install 0.6.0 properly due to the version conflict of some of python packages. Now the code that used to work before does not work anymore. I added an example below. I guess that the error will be resolved if I install version 0.6.0, so I tried to install it in multiple different environments, Linux, Windows, Google Colab, and Binder, but I was never able to successfully install geosnap 0.6.0. Any help will be greatly appreciated.

from geosnap import datasets
from geosnap import Community
from geosnap.io import store_ltdb
sample = "downloads/LTDB_Std_All_Sample.zip"
full = "downloads/LTDB_Std_All_fullcount.zip"
store_ltdb(sample=sample, fullcount=full)
this will create a new community using data from Washington DC (which is fips code 11)
dc = Community.from_census(state_fips="11")
dc.gdf.head()
-------------------------------------After I run the code above. I got an error below--------------
KeyError                                  Traceback (most recent call last)
c:\users\suzie.conda\envs\geosnap\lib\site-packages\pandas\core\indexes\base.py in get_loc(self, key, method, tolerance)
2645             try:
-> 2646                 return self._engine.get_loc(key)
2647             except KeyError:
pandas_libs\index.pyx in pandas._libs.index.IndexEngine.get_loc()
pandas_libs\index.pyx in pandas._libs.index.IndexEngine.get_loc()
pandas_libs\hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
pandas_libs\hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
KeyError: 'wkb'
During handling of the above exception, another exception occurred:
KeyError                                  Traceback (most recent call last)
 in
1 # this will create a new community using data from Washington DC (which is fips code 11)
----> 2 dc = Community.from_census(state_fips="11")
3 dc.gdf.head()
c:\users\suzie.conda\envs\geosnap\lib\site-packages\geosnap_community.py in from_census(cls, state_fips, county_fips, msa_fips, fips, boundary, years)
1668
1669         df_dict = {
-> 1670             1990: datasets.tracts_1990(states=states),
1671             2000: datasets.tracts_2000(states=states),
1672             2010: datasets.tracts_2010(states=states),
c:\users\suzie.conda\envs\geosnap\lib\site-packages\geosnap_data.py in tracts_1990(self, states, convert)
308         t["year"] = 1990
309         if convert:
--> 310             return _convert_gdf(t)
311         else:
312             return t
c:\users\suzie.conda\envs\geosnap\lib\site-packages\geosnap_data.py in _convert_gdf(df)
95     else:
96         with multiprocessing.Pool() as P:
---> 97             df["geometry"] = P.map(_deserialize_wkb, df["wkb"])
98         df = df.drop(columns=["wkb"])
99
c:\users\suzie.conda\envs\geosnap\lib\site-packages\pandas\core\frame.py in getitem(self, key)
2798             if self.columns.nlevels > 1:
2799                 return self._getitem_multilevel(key)
-> 2800             indexer = self.columns.get_loc(key)
2801             if is_integer(indexer):
2802                 indexer = [indexer]
c:\users\suzie.conda\envs\geosnap\lib\site-packages\pandas\core\indexes\base.py in get_loc(self, key, method, tolerance)
2646                 return self._engine.get_loc(key)
2647             except KeyError:
-> 2648                 return self._engine.get_loc(self._maybe_cast_indexer(key))
2649         indexer = self.get_indexer([key], method=method, tolerance=tolerance)
2650         if indexer.ndim > 1 or indexer.size > 1:
pandas_libs\index.pyx in pandas._libs.index.IndexEngine.get_loc()
pandas_libs\index.pyx in pandas._libs.index.IndexEngine.get_loc()
pandas_libs\hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
pandas_libs\hashtable_class_helper.pxi in pandas._libs.hashtable.PyObjectHashTable.get_item()
KeyError: 'wkb'

this error happens because geosnap's census database uses a different storage convention and the old version of the software doesn't understand the new implementation. Instead of manually converting  shapely objects to WKB representation and back, we use the built-in parquet functionality from geopandas.
So the error happens because you're using an old version of geosnap that expects a  wkb column which no longer exists in the current data. The best way to get around this would be to install the current version of geosnap using anaconda. If you install using any method other than anaconda, there's no way to ensure you'll avoid version conflicts in the underlying C dependencies like GDAL. We test the package on all three platforms (and they're all passing), so you should be able to use the latest version fine as long as you stick with conda.
If for some reason you can't use anaconda and you're stuck on version 0.5.0, then you can still use all of geosnap's functionality, you just won't have access to the built-in datasets. The census data are just there for convenience because we use them so often, but the package operates just fine if you bring your own data (e.g. using something like from_geodataframes method)
closing as duplicate of #296

Um.. I tried to install using
conda install -c conda-forge geosnap
but I was never able to install it succesfully. Is there anything else that I need to do? it just keeps doing like below
(geosnap_test) PS C:\Users\Suzie> conda install -c conda-forge geosnap
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: \

try creating a new empty environment then installing geosnap there
conda create -n geosnap
conda activate geosnap
conda install geosnap -c conda-forge

you will also probably have better luck with the mamba package manager
so you might want to do conda install mamba -y then swap the mamba command anywhere you would normally use conda (e.g. mamba install geosnap)

I have no luck. I was just wondering how I can still use ltdb data while using geosnap 0.5.0. Disconnecting data service was frustrating because I made and have been using an application that brings ltdb data.

The reason that I got stuck last time was that I was not able to install geosnap 0.6.0 using mamba nor conda. But this time I tried to install miniconda, and installed mamba and then I was able to install geosnap 0.6.0 using mamba on my Windows10.  I was not even able to install geosnap 0.6.0 using conda in my Ubuntu. It looks like Ananconda got sick recently?!
Anyways, your mamba solution worked out great for me with miniconda.  But somehow it looks like when I use select LTDB dataset on geosnap 0.6.0, something invisible stuff in datasets is different. I just updated from geosnap 0.5.0 to geosnap 0.6.0 and the code that used to work with ltdb data in the previous version does not work anymore in the new version.  Is there any changes on the datasets especially in relation to the geometry data or type possibly?  Maybe is there any changes on data type? Are you aware of anything in terms of the issue? I still could not find what the difference is between the old dataset and the newt dataset, but somehow it gives me an error when I use the same new dataset and run clustering algorithms (I mean the content of dataset looks different but they are technically different in terms of data type, non-value or infinity.....but not sure what the difference is)

glad to hear you were able to get things working with the newest version. There's no change in the way the data are processed--the function is unchanged since the original implementation except that we use a different storage format. It's possible that missing values get treated differently somehow during read/write, but there's nothing different in our tests, or when I've used the data in my own work.
It sounds like any lingering issues are probably analysis-specific, and it's probably best to explore the LTDB data a bit until you can identify what's going on


[Feature request] Splitpayments: show all wallets of user in dropdown menu instead of manual input of keys

Is your feature request related to a problem? Please describe.
For larger splits, it takes a lot of effort to add many destination wallets.
Describe the solution you'd like
A dropdown menu that shows all wallets of the user for fast adding.
Additional context
@Egge7 uses this for Plebrap.space

What if I'm splitting to wallets that i do not own (not associated with my user)?

It would be interesting to learn how most people use this (splitting of payments between wallets owned by one user vs. different users).
The last item of the drop down could be "WALLET/INVOICE Key" which makes another input box show up


Default column handling of noForwardIndex and regeneration of forward index on reload path

Related OSS Issue: https://github.com/apache/pinot/issues/6473
Related OSS PRs:
https://github.com/apache/pinot/pull/9333
https://github.com/apache/pinot/pull/9740
Document outlining the breakup of PRs and the approach to solve various sub-problems of this issue: https://docs.google.com/document/d/1MNLLhYCg5e-UFBQ6wTBODd41sDsbjevwRfwoGuNowWw/edit?usp=sharing
This PR adds support for the following operations related to forward index disabled columns:

Adds default column handling for MV forward index disabled columns. Creates an inverted index for default MV columns with forward index disabled instead of a forward index.
Adds a utility class to generate the forward index from the inverted index and dictionary.
Adds support to enable the forward index on existing columns with the forward index disabled.
Adds support to create a temporary forward index if other indexes are added for columns where the forward index is disabled.

This PR does not add support for the following (and there will be follow up PRs to handle these):

Dealing with duplicated entries within a multi-value row.
Derived column handling.

Tests includes:

Segment reload path for default columns and existing columns
Query path to ensure queries work when the forward index is re-enabled

cc @siddharthteotia @Jackie-Jiang @vvivekiyer

Codecov Report

Merging #9810 (03d37ce) into master (78504b9) will decrease coverage by 52.96%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #9810       +/-   ##
=============================================
- Coverage     68.69%   15.72%   -52.97%
+ Complexity     5423      175     -5248
=============================================
  Files          1961     1912       -49
  Lines        104982   102959     -2023
  Branches      15883    15686      -197
=============================================
- Hits          72115    16191    -55924
- Misses        27799    85576    +57777
+ Partials       5068     1192     -3876

Flag
Coverage Δ

integration2
?

unittests1
?

unittests2
15.72% <0.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ndex/loader/BaseForwardIndexBasedIndexHandler.java
0.00% <0.00%> (ø)

...ocal/segment/index/loader/ForwardIndexHandler.java
0.00% <0.00%> (-85.63%)
:arrow_down:

...tedIndexAndDictionaryBasedForwardIndexCreator.java
0.00% <0.00%> (ø)

...egment/local/segment/index/loader/LoaderUtils.java
0.00% <0.00%> (-94.12%)
:arrow_down:

...ocal/segment/index/loader/SegmentPreProcessor.java
0.00% <0.00%> (-84.26%)
:arrow_down:

...t/index/loader/bloomfilter/BloomFilterHandler.java
0.00% <0.00%> (-41.50%)
:arrow_down:

...loader/defaultcolumn/BaseDefaultColumnHandler.java
0.00% <0.00%> (-57.50%)
:arrow_down:

...x/loader/defaultcolumn/V3DefaultColumnHandler.java
0.00% <0.00%> (-90.91%)
:arrow_down:

...ent/index/loader/invertedindex/H3IndexHandler.java
0.00% <0.00%> (-74.08%)
:arrow_down:

...t/index/loader/invertedindex/JsonIndexHandler.java
0.00% <0.00%> (-72.84%)
:arrow_down:

... and 1458 more

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

@somandal  - looks good overall. Since this is quite big already and we have iterated upon it few times, I am merging it. I think the runtime of MV column should be looked into once to see there isn't any performance issue.
Secondly, it will be good to take another pass at the new file added to see if some methods can be refactored into smaller ones.
Thanks for working on this.

@somandal - looks good overall. Since this is quite big already and we have iterated upon it few times, I am merging it. I think the runtime of MV column should be looked into once to see there isn't any performance issue.
Secondly, it will be good to take another pass at the new file added to see if some methods can be refactored into smaller ones.
Thanks for working on this.

Thanks so much, appreciate your patience with this long PR!
I'll look into:

Secondly, it will be good to take another pass at the new file added to see if some methods can be refactored into smaller ones.

As for this:

I think the runtime of MV column should be looked into once to see there isn't any performance issue.

The MV test taking 7-8 minutes is spending most of that time on verification and not on reload. So I don't anticipate a major issue in the reload path for performance purposes, but I can definitely look into whether there are any optimization opportunities.


[TF:TRT] Update Rejected Algorithms for Newer TRT Versions

Lower performance on TRT algorithms fixed as of TRT 8.0.3, so the gated patch only applies between 8.0.0 and 8.0.3

@bixia1 @DEKHTIARJonathan

Converting PR to draft to re-address logic for TRT < 8.0 and TRT >= 8.2.  Changes will be ready this afternoon

This PR ensures that both the TRT 7.x and 8.0.0 rejected tactics as introduced in PR 50408 are properly gated

@MattConley Can you please check @bixia1's comments and keep us posted ? Thanks!

@MattConley can you please address this comment

I think this PR is correct in that it will have the intended effect. I can add tests in #53760. The entire surrounding code is precarious. In particular, the enum defined to identify shuffle algorithm is only valid for TRT 8.0 and TRT 7.2. So actually the code would logically ban random formats of unary layer for TRT 7.1 (although alg selector is not currently active for TRT 7.1).

The existing code is buggy in that it bans formats in TRT 8.2 for a layer that is not a shuffle layer, despite what the code intends, so we should probably prefer this change over existing code

@MattConley please squash the commits.

@MattConley Can you please check @bixia1's comments and keep us posted ? Thanks!

Squashed the changes together, thanks @bixia1 and @christopherbate


fixes DialogRoute memory leak

part of #141198

Fixes memory leak on DialogRoute
Adds opt-in test

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

cc: @polina-c

@chingjun , can you review to trigger google testing on this?

@polina-c it seems the Google test is failing can you provide a brief idea on what is Google test? And how should I be able to fix the test failing?
I saw logs and it says "Please contact a Google developer to investigate"

Google testing is testing of the change for internal Google projects. Its failure means one of two:

The change introduced a bug to Flutter, and public test coverage is not good enough to catch it. So, we need to fix the bug and maybe add some test coverage.
The internal project is using Flutter in a wrong way and should be fixed.

I checked logs. There is no failures in Flutter code, but there is change of behavior of an application: widget that is expected to be visible, is not.
Unfortunately, I cannot share more details.
Is it possible to fix the leak with less changes to the original code? Without overriding buildTransitions?

I see, unfortunately we need to override for disposing CurvedAnimation properly
The previous widget function was outside of class and the curved animation was getting used inside directly so there was no way to dispose it properly
But I'll try to come up with a better solution, and test-out other options
Also if I push code with changes will Google test now re-run itself? Or we have to manually trigger it again?

I see, unfortunately we need to override for disposing CurvedAnimation properly
The previous widget function was outside of class and the curved animation was getting used inside directly so there was no way to dispose it properly
But I'll try to come up with a better solution, and test-out other options
Also if I push code with changes will Google test now re-run itself? Or we have to manually trigger it again?

Thanks for explanation.
To be clear, I am not confident that your change is wrong. It may be that application is doing something wrong. We just do not know.
Can you explain why override is needed? Why the methid cannot be just moved inside and the animation stored as a new member variable?
I think google testing will re-run, but I can be wrong.

Previous implementation was passing the widget function into the super constructor so handling variable initialisation and disposal was not possible since we can't initialise them while not constructed.
So the best solution i thought was to override it.

How about putting the builder into separate class like _DialogRouteAnimation, that would also would hold the instance of the CurvedAnimation.

Creating private constructor like

DialogRoute._(this._animation, {required super.pageBuilder, super.barrierLabel, super.transitionDuration,  super.transitionBuilder});

Converting existing constructor to factory constructor:

factory DialogRoute({
...
  }) {
    final animation = _DialogRouteAnimation();
    return DialogRoute._(animation,
         transitionBuilder: animation.buildMaterialDialogTransitions,
...

Then you will be avle to dispose the animation:
  @override
  void dispose() {
    _animation.dispose();
    super.dispose();
  }

Seems like an awesome idea, I'll try this

@polina-c seems like it's not related to override logic as the test is still failing.
I am still not sure, I think it's most likely a new animation handling snippet.
Since now the google test will initiate automatically, I'll test-out some ideas I have.

@chingjun @polina-c I see it's bit tricky, if we override buildTransitions it does not display a widget that should be visible, Adding factory constructor fixed this issue but that mean it will break any other class that extends to DialogRoute
How about if we make override less invasive?
previously we were overriding entire widget which may have been cause of missing widget?
instead of:
  @override
  Widget buildTransitions(BuildContext context, Animation<double> animation, Animation<double> secondaryAnimation, Widget child) {
    _fadeCurve ??= CurvedAnimation(
      parent: animation,
      curve: Curves.easeOut,
    );
   return FadeTransition(
      opacity: _fadeCurve!,
      child: child,
    );
  }

we could try this:
  @override
  Widget buildTransitions(BuildContext context, Animation<double> animation, Animation<double> secondaryAnimation, Widget child) {
    _fadeCurve ??= CurvedAnimation(
      parent: animation,
      curve: Curves.easeOut,
    );
   return FadeTransition(
      opacity: _fadeCurve!,
      child: super.buildTransitions(context, animation, secondaryAnimation, child),
    );
  }

Let me know if we have better way to handle it or if above mentioned solution worth try. :)

@chingjun , it is good learning  that change of type of constructor is a breaking change. Thanks.
Okay, as we got failure, my previous comments are not relevant.
 Let's see how it works.

@chingjun @polina-c Google test is passing now


Could not load module ‘System.Random.Internal’ when building from source using Cabal on MacOS

Version
v2021-07-30
Platform
macOS Catalina
Installation method
Built from source
Network configuration
mainnet
Context
I've been following the Cardano developer documentation for building the cardano-wallet CLI but every time I try to build from source using cabal it throws this error shown below.
src/Cardano/Wallet/DB/Sqlite/Types.hs:122:1: error:
    Could not load module ‘System.Random.Internal’
    It is a member of the hidden package ‘random-1.2.0’.
    Perhaps you need to add ‘random’ to the build-depends in your .cabal file.
    Use -v (or `:set -v` in ghci) to see a list of the files searched for.
    |
122 | import System.Random.Internal
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
cabal: Failed to build cardano-wallet-core-2021.7.30 (which is required by
exe:local-cluster from cardano-wallet-2021.7.30, test:integration from
cardano-wallet-2021.7.30 and others).

I've seen a couple of issues already that sort of relate to this issue but non of the proposed solutions fix the problem.
Description
Steps to Reproduce

Download the latest Cardano node 1.28.0
Follow this documentation https://developers.cardano.org/docs/get-started/installing-cardano-wallet on macOS for building the Cardano Wallet from source using cabal.

Expected behavior
Build from source successfully.
Actual behavior
Throws Could not load module ‘System.Random.Internal’ when running cabal build all

Hi @atx-barnes, thanks for reporting.
It seems like those instructions are wrong.
We will get them corrected, but in the mean time, the command to build cardano-wallet with Cabal is simply:
cabal build all -frelease

If you have previously run cabal configure or cabal build with the wrong flags, then remove cabal.project.local beforehand.

@rvl
Hi I had the same problem once I removed  cabal.project.local and run cabal build all -frelease it returns Cannot find the program 'ghc'. User-specified path 'ghc-8.10.5'
Thank you

@henry8th out of interest, what version of ghc do you have installed? ghc --version

@rvl after running into the issue same issue I ran the following:
  379  rm cabal.project.local
  380  cabal build all -frelease
  382  cabal configure --with-compiler=ghc-8.10.7 --constraint="random<1.2"
  383  cabal build all -frelease

But that also returned:
Building library for cardano-wallet-core-2021.9.9..
[59 of 95] Compiling Cardano.Wallet.DB.Sqlite.Types ( src/Cardano/Wallet/DB/Sqlite/Types.hs, /home/cardano/cardano-src/cardano-wallet/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-wallet-core-2021.9.9/build/Cardano/Wallet/DB/Sqlite/Types.o, /home/cardano/cardano-src/cardano-wallet/dist-newstyle/build/x86_64-linux/ghc-8.10.7/cardano-wallet-core-2021.9.9/build/Cardano/Wallet/DB/Sqlite/Types.dyn_o )

src/Cardano/Wallet/DB/Sqlite/Types.hs:122:1: error:
    Could not load module ‘System.Random.Internal’
    It is a member of the hidden package ‘random-1.2.0’.
    Perhaps you need to add ‘random’ to the build-depends in your .cabal file.
    Use -v (or `:set -v` in ghci) to see a list of the files searched for.
    |
122 | import System.Random.Internal
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
cabal: Failed to build cardano-wallet-core-2021.9.9 (which is required by
exe:local-cluster from cardano-wallet-2021.9.9, test:integration from
cardano-wallet-2021.9.9 and others).

Essentially I've ran:
  372  git clone https://github.com/input-output-hk/cardano-wallet.git
  373  cd cardano-wallet
  374  git fetch --all --recurse-submodules --tags
  375  git checkout tags/v2021-09-09
  376  cabal configure --with-compiler=ghc-8.10.7 --constraint="random<1.2"
  378  cabal build all -frelease

Hi thanks for your reply I fixed it by removing --constraint=random<1.2
from cabal configure
On Tue, 14 Sep 2021, 07:57 John Imison, @.***> wrote:

@henry8th https://github.com/henry8th out of interest, what version of
ghc do you have installed? ghc --version
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/cardano-wallet/issues/2824#issuecomment-918864851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP52P6ZHQAI4H34TXLU5UMLUB3W5DANCNFSM5CF2EX6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@henry8th nice one, thank you for that!  Worked a treat for me too.

Closing as this is probably out of date by now. Feel free to reopen if this or a similar issue persists.


Include a nice message on login

CMs should be greeted with some sort of reminder that the work they're doing is important and valued. idk if this takes the form of patient stories, cat pictures, or just a big thumbs up emoji.

I vote for cat pics
On Mon, Feb 15, 2016 at 10:49 PM, Colin<EMAIL_ADDRESS>wrote:

CMs should be greeted with some sort of reminder that the work they're
doing is important and valued. idk if this takes the form of patient
stories, cat pictures, or just a big thumbs up emoji.
—
Reply to this email directly or view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/issues/82.


Release macOS 10.9 wheels instead of 10.15?

Can we release 10.9, to support older macOSes?
More details in https://github.com/dwavesystems/dwave-neal/pull/71. In the meantime, wheel>0.34 says it has:

Added automatic platform tag detection for macOS binary wheels

I've tested this auto-detection and it seems it produces 10.9 wheels on our other packages (e.g. greedy), but not for minorminer. Might be we actually use something that requires 10.15?

I didn't set up builds for macOS and I don't use that platform myself.  I don't do anything terribly exotic on the OS side of things, I don't see why 10.15 would specifically be required.

Obsoleted by switch to cibuildwheel.


Clean command tries to drop extensions that are installed by superuser

Which version and edition of Flyway are you using?
Flyway 7.2.0 CE
If this is not the latest version, can you reproduce the issue with the latest one as well?
Reproduces in 7.0.0 CE, 7.1.0 CE, 7.2.0 CE
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Maven plugin
Which database are you using (type & version)?
Postgres 11.3
Which operating system are you using?
MacOS
What did you do?
We have a docker environment with a Postgres 11.3 instance that is initialised with a couple of extensions in the databases it hosts. We use one of these databases to perform a Flyway migration during our Maven build:
\c template1
CREATE SCHEMA debug;
CREATE EXTENSION IF NOT EXISTS intarray;
CREATE EXTENSION IF NOT EXISTS btree_gist;

\c postgres
CREATE USER a WITH PASSWORD 'a';
CREATE USER flyway_build WITH PASSWORD 'flyway_build';

CREATE DATABASE a WITH OWNER a;
CREATE DATABASE b WITH OWNER flyway_build;

The Maven build is configured to run Flyway as the flyway_build user. With Flyway 6.5.7, this all worked fine.
When Flyway 7.x.x tries to perform a clean during the build, it fails because it tries to drop the intarray extension, which is owned by postgres.
Workarounds

Make the Flyway user a superuser and move the CREATE EXTENSION to the migration scripts.
Upgrade to Postgres 13 where these extensions can be installed by regular users.

What did you expect to see?
Flyway not requiring superuser rights for a clean, and Flyway not to drop extensions that it cannot install itself (or better: that are not created by the migrations that it runs itself, since extensions may affect more than just the schemas that the Flyway user can access).
What did you see instead?
Flyway requires superuser rights for a clean, or fails to drop extensions that were installed by another user.
I would rather not give Flyway superuser rights, because migrations during build are then allowed to do more (like installing extensions) than migrations in production.

⚡ lightning fast, many thanks!

Did flyway not used to drop extensions? We recently started using 7.2.1 upgrading from 6.4.0 and noticed that extensions that were installed before clean are being removed now and breaking scripts that did not expect that.

In Flyway V7 we added several breaking changes, and dropping extensions is one of them
You can read about the changes in the V7 blog post and in the release notes

I'm facing a similar issue. My cloud provider creates some functions in the schema and because of that Flyway fails to clean up the database. Is it possible to delete only entities that the current user is the owner of?


license?

is this released as open source software? if so, can you explicitly declare the license?

Hey,
Yes it is released as an open source software. I will update the license.
Thanks for bringing it up.
Best,
Chaitanya

LICENSE is updated.


Update copy for Display Group Import

Description
Updated copy based on AC.
Type of Change

update

Coverage remained the same at 32.905% when pulling 7ae6b0910cfdfabb64c3f4fe4a06bc4ccd737d15 on johnwcallahan:M3-XXX-import-groups-copy into fdbcc388b292e78029c4b3d118216317562f25ee on linode:feature/group-tags.


Update status for SE-0101, SE-0103, SE-0117

These are not yet in apple/swift/CHANGELOG.md, but have been implemented:

SE-0101: https://github.com/apple/swift/pull/3854
SE-0103: https://github.com/apple/swift/pull/3853
SE-0117: https://github.com/apple/swift/pull/3882

Thanks!


Fix initNameNode with hardcoded dns name

LGTM

One minor nit, but should be good to merge!

I have not looked closely at code formatting. Not sure if line break is correct, let me know if you prefer "+" sign at the end of the previous line, I have it at the start of the second line.

Thanks @rmvz. The line wrap is fine. We used to have an automated formatter prior to the gradle changes. It would be great to add it back in gradle to make this a bit easier! Merging now.


Documentation - Suggestions

I started to work on the documentation (see #41) and I have a few suggestions:

Include source-code documentation into sphinx
Provide the documentation in both german and english
Rethink the README - currently it is a mix of quickstart, documentation for specific apis and links to more documentation on autogenerated api-clients; IMO it should only contain a short description of the repo, how to install it and where to find more documentation
Provide an Issue template for documentation related issues and tag them as documentation, which would make it easier to plan and track documentation progress and allow to filter bugs and other issues.
Host the documentation on readthedocs (@LilithWittmann thats something you should look into)

@lukaspanni should be now building to https://deutschland.readthedocs.io/en/latest/.

@LilithWittmann same here.

Just saw this issue again, still not working ...
Maybe @LilithWittmann can fix this.

still not working today ;-)


BFRImageViewController index 0 beyond bounds crash

I've been getting the following crash coming back in my crash reporting recently. I'm not sure if this is caused by something that I am doing or if it's in the library itself. Nonetheless I thought it would be useful to post the crash report here for you.
Summary:
BFRImageViewController.m line 194
-[BFRImageViewController reinitializeUI]
Fatal Exception: NSRangeException
*** -[__NSArrayM objectAtIndexedSubscript:]: index 0 beyond bounds for empty array

Crash report:
Fatal Exception: NSRangeException
0  CoreFoundation                 0x1b8b5496c __exceptionPreprocess
1  libobjc.A.dylib                0x1b886d028 objc_exception_throw
2  CoreFoundation                 0x1b8bad500 -[__NSCFString characterAtIndex:].cold.1
3  CoreFoundation                 0x1b8a389f8 -[__NSArrayM objectAtIndexedSubscript:]
4  BFRImageViewer                 0x1020d6cec -[BFRImageViewController reinitializeUI] + 194 (BFRImageViewController.m:194)
5  BFRImageViewer                 0x1020d6244 -[BFRImageViewController viewDidLoad] + 93 (BFRImageViewController.m:93)
6  UIKitCore                      0x1bc60c0e4 -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled]
7  UIKitCore                      0x1bc610d18 -[UIViewController loadViewIfRequired]
8  UIKitCore                      0x1bc611104 -[UIViewController view]
9  UIKitCore                      0x1bc536400 -[_UIFullscreenPresentationController _setPresentedViewController:]
10 UIKitCore                      0x1bc529ac4 -[UIPresentationController initWithPresentedViewController:presentingViewController:]
11 UIKitCore                      0x1bc62109c -[UIViewController _presentViewController:withAnimationController:completion:]
12 UIKitCore                      0x1bc623d0c __63-[UIViewController _presentViewController:animated:completion:]_block_invoke
13 UIKitCore                      0x1bc624270 -[UIViewController _performCoordinatedPresentOrDismiss:animated:]
14 UIKitCore                      0x1bc623c58 -[UIViewController _presentViewController:animated:completion:]
15 UIKitCore                      0x1bc623eec -[UIViewController presentViewController:animated:completion:]
16 UIKit                          0x1eeada618 -[UIViewControllerAccessibility presentViewController:animated:completion:]
17 Lebs                           0x100846c5c VGalleryCell.didTapScrollView() (<compiler-generated>)
18 Lebs                           0x10084701c @objc VGalleryCell.didTapScrollView() (<compiler-generated>)
19 UIKitCore                      0x1bc827248 -[UIGestureRecognizerTarget _sendActionWithGestureRecognizer:]
20 UIKitCore                      0x1bc82f9e8 _UIGestureRecognizerSendTargetActions
21 UIKitCore                      0x1bc82d16c _UIGestureRecognizerSendActions
22 UIKitCore                      0x1bc82c6a0 -[UIGestureRecognizer _updateGestureForActiveEvents]
23 UIKitCore                      0x1bc820564 _UIGestureEnvironmentUpdate
24 UIKitCore                      0x1bc81fd20 -[UIGestureEnvironment _deliverEvent:toGestureRecognizers:usingBlock:]
25 UIKitCore                      0x1bc81fad4 -[UIGestureEnvironment _updateForEvent:window:]
26 UIKitCore                      0x1bcc92a60 -[UIWindow sendEvent:]
27 UIKitCore                      0x1bcc6e600 -[UIApplication sendEvent:]
28 UIKit                          0x1eea81550 -[UIApplicationAccessibility sendEvent:]
29 UIKitCore                      0x1bcce8a58 __dispatchPreprocessedEventFromEventQueue
30 UIKitCore                      0x1bcceb010 __handleEventQueueInternal
31 UIKitCore                      0x1bcce4194 __handleHIDEventFetcherDrain
32 CoreFoundation                 0x1b8ad0108 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
33 CoreFoundation                 0x1b8ad005c __CFRunLoopDoSource0
34 CoreFoundation                 0x1b8acf7c8 __CFRunLoopDoSources0
35 CoreFoundation                 0x1b8aca694 __CFRunLoopRun
36 CoreFoundation                 0x1b8ac9f40 CFRunLoopRunSpecific
37 GraphicsServices               0x1c2d5a534 GSEventRunModal
38 UIKitCore                      0x1bcc55580 UIApplicationMain
39 Lebs                           0x1007f957c main + 24 (AppDelegate.swift:24)
40 libdyld.dylib                  0x1b8948e18 start

Thanks for leaving it @joshgare  - what version are you on and when did it start?

Hi @DreamingInBinary,
We are currently using v1.2.7 in our app. Firebase is telling me that the crash has been occurring since January 3rd 2020.

We haven't ran into this ourselves, but it looks like your images might be off or perhaps you're manually setting the starting index out of bounds.

@DreamingInBinary hit the nail on the head 🎉 - there is a case where the starting index could exceed the number of images the controller is initialised with. I will add a check in my code. Many thanks for pointing me in the right direction.

No problem :)


Adds key methods/functionality to SchemaResourceLoader and correspond…

…ing tests.

Codecov Report

Merging #218 into master will increase coverage by 0.22%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #218      +/-   ##
==========================================
+ Coverage   92.71%   92.93%   +0.22%
==========================================
  Files         136      136
  Lines        2415     2420       +5
  Branches      128      128
==========================================
+ Hits         2239     2249      +10
+ Misses        176      171       -5

Impacted Files
Coverage Δ

...ala/hydra/avro/resource/SchemaResourceLoader.scala
100% <100%> (+26.31%)
:arrow_up:

Continue to review full report at Codecov.

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


How to extend action message ?

I want to add a field for action: message_id,  used to match sent and received messages. Other potential extension requirements include timestamp...
Currently I seem to need to modify the internal implementation of Agent (MessageSchema or ActionSchema). Is there a better way ?

You'd have to make a change to the implementation unfortunately. I also want to add a message id field.
If you saw the other issue regarding action parameter descriptions, I proposed adding an optional field called __meta__ that we can use to store this kind of metadata.
Copying from that issue, here's an example of what I'm thinking with a message id and timestamp in the meta field. (note that I moved the meta field out of the action field in this example. I think this might be a better format.)
{
  "to": "John",
  "from": "Jane",
  "__meta__": {
    "message_id": "abc123",
    "timestamp": "2023-08-01 01:00 UTC",
    "thoughts": "I should greet John",
  },
  "action": {
    "say": {
      "content": "Hello, John!"
    }
  }
}

I'm thinking we could change Space._route to add a message id to the meta field automatically. Here's how I'm thinking you would then send a message:
sent_message = self._send({
  "to": "John",
  "__meta__": {
    "thoughts": "I should greet John",
  },
  "action": {
    "say": {
      "content": "Hello, John!"
    }
  }
})

Not much of a difference except that it would return the full message as it was sent, including any additional meta fields and the from field populated. So sent_message would then contain:
sent_message == {
  "to": "John",
  "from": "Jane", # this is added by the _route method
  "__meta__": {
    "message_id": "abc123", # this is added by the _route method
    "timestamp": "2023-08-01 01:00 UTC", # this is added by the _route method
    "thoughts": "I should greet John",
  },
  "action": {
    "say": {
      "content": "Hello, John!"
    }
  }
}

Note that you don't need to store sent_message since it will automatically be added to the _message_log list, but this would allow you to inspect the complete message if needed after sending. So you could pull out the message_id field or others if you need to.
Then we can also change how the return and error actions work, to use the message id instead of sending the entire original message (which is a flawed approach). Here's how a return message would look:
{
  "to": "Jane",
  "from": "John",
  "__meta__": {
    "message_id": "def456", # this is the id for the `return` message
  },
  "action": {
    "return": {
      "original_message_id": "abc123", # Note the original message id here
      "return_value": "Hi, Jane!",
    }
  }
}

Then I think the return and error actions wouldn't need to change. You'd still use the same signature:
def _action__return(self, original_message: dict, return_value: str):
    ...

But the original_message field would be determined by the library by automatically correlating message id's. And we could add a method for doing this manually when needed. Something like:
def _find_message(self, message_id: str) -> dict:
    """Returns the message with the given id."""

What do you think of this? I'm in the middle of implementing a lot of these changes now. I hope to have a 1.3 out in a few days and I hope to include something like this.

I like the idea, "meta" is very useful for extensions.
I have some opinions about the fields of the route automatic operation:
sent_message == {
  "to": "John",
  "from": "Jane", # this is added by the _route method
  "__meta__": {
    "message_id": "abc123", # this is added by the _route method
    "timestamp": "2023-08-01 01:00 UTC", # this is added by the _route method
    "thoughts": "I should greet John",
  },
  "action": {
    "say": {
      "content": "Hello, John!"
    }
  }
}

from: I have a use case: there is an Agent  work like a message transfer station, which will forward message from another system (non-Python system, Agent cannot be implemented internally), when it forwards the message, it does not want to modify the from field.
message_id:  The Actor model is inherently an asynchronous system, sometimes we need to implement synchronous semantics. Interestingly, we can implement it only on the client side of the message sent(This is a proof of Actor's flexibility, synchronization semantics can be built on it, and it is only implemented inside a certain Actor, the system remains ignorant of it)，the following is an example

class SyncAgent(Agent):
    '''
    a synchronous Agent
    '''

    def __init__(self, id):
        super().__init__(id)
        self._future_resolves = {}

    def _receive(self, message):
        threading.Thread(target=super()._receive, args=(message,)).start()

    @access_policy(ACCESS_PERMITTED)
    def _action__return(self, original_message: dict, return_value):
        if original_message.get("message_id"):
            in_comming_message_id =  original_message['message_id']
            future = self._future_resolves.get(in_comming_message_id)
            if future:
                future.set_result(return_value)

    def _send_and_wait(self, message, timeout=None):
        with ThreadPoolExecutor(max_workers=1) as executor:
            future = Future()
            task = executor.submit(lambda f: f.result(timeout=timeout), future)
            message_id = random.randint(1, 100000000)
            self._future_resolves[message_id] = future # todo: threadsafe
            message["message_id"] = message_id
            self._send(message)
            return task.result() # block and wait the result or TimeoutError

    @access_policy(ACCESS_PERMITTED)
    def _action__test(self, content: str):
        """test"""
        message = {
            "to": "John",
            "thoughts": "",
            "action": "test",
            "args": {
                "content": f"hi {random.randint(1,10000)}"
            },
        }

        result = self._send_and_wait(message)
        print("result: ", result)

This SyncAgent generates a message_id on the Agent side, immediately enters the block after sending a message, and waits (or times out) for a message with the same message_id, which requires getting the message_id immediately after sending a message. If message_id is sent by _route, can _send method return message_id as return value
Based on the above two use cases, it seems that the agent can directly manipulate meta to bring flexibility, which raises the question: which behavior of _route should be mandatory, or should the message from the agent be transmitted as transparently as possible.

It is also worth noting here:
    def _receive(self, message):
        threading.Thread(target=super()._receive, args=(message,)).start()

The current execution mechanism of Agent action is blocking. It needs to wait for an action to complete before receiving and executing the next message.  We can decide the concurrency mechanism of action execution inside the Agent(like SyncAgent). But it's not clear to me that there is value in adding this mechanism as an option to the base class.

 I think we're very aligned in how we're thinking about all this. I've wondered about many of these choices and it's really helpful to hear your perspective.
On the added fields: from, message_id, etc. I think you bring up a really good point. I like the idea of moving this responsibility entirely to the Agent class like you're suggesting.
This way the Space classes would be entirely focused on routing, based on the to and from fields and it would not affect anything in the message.
I also love the synchronous messaging example you gave. I've had that thought as well and I think it supports the idea of having the agent determine all message fields. This way the entire implementation of synchronous messaging could be in the agent class. This seems like it would allow more flexibility overall.
So I'm going to include this in the coming changes. All the fields will need to be set by an Agent. Space._route would only be interested in the to and from fields for routing but would not touch anything in the message.
And regarding the _receive method and whether it should parallelize processing automatically. I like that possibility a lot but I'm not confident I want to add that yet. Mainly because I've got a big set of updates already and I'd like to think about this some more. But I agree this could be a very useful option. I'm going to add this as a note under the Improve Multiprocessing issue so that it isn't forgotten. Maybe after the next release we can play around on a PR for this.
Let me know if this all sounds good to you!

So I'm going to include this in the coming changes. All the fields will need to be set by an Agent. Space._route would only be interested in the to and from fields for routing but would not touch anything in the message.

Awesome !
I think this will better support Late_binding, let the decision-making be postponed to the object (Agent) as much as possible. Alan Kay once said:

OOP to me means only messaging, local retention, and protection and hiding of state-process, and extreme late-binding of all things.

The Actor model is very similar to what Alan Kay did in Smalltalk in the early days(Joe Armstrong & Alan Kay).
It is an excellent decision for agency to choose Actor as the calculation model.

I also love the synchronous messaging example you gave.
And regarding the _receive method and whether it should parallelize processing automatically. I like that possibility a lot but I'm not confident I want to add that yet.

I am not sure about the concurrency and synchronization of Actors. I only have some rough ideas at present,  Erlang / Elixir seems like a good place to learn, but I currently only have a rough understanding of them.
I currently think about the behaviors that the Agent should support in the context of FIPA. What are your plans for the behaviors that the Agent will support?

Thank you! Interestingly, I didn't choose the actor model directly. I developed the basics of the framework iterating on my own agent system, and at one point I realized that I was approaching the Actor model. That's when the idea became clearer, and soon after I decided to open source.
Regarding FIPA, I'm not familiar but you gave me some good reading to do. :)
I'm aware of other similar "plug-and-play" like protocols that this resembles but I don't have a specific protocol I'm thinking of. I'm somewhat taking a "let's justify what we need as we go" approach and trying to minimize assumptions. That said I do like to review prior work to see how others have done it.
Overall I want to support practical development of agent systems. Since it's not entirely clear what the best approaches are, or that there is a "best" approach, I think experimentation is necessary at this time. So I want the library to be flexible but I also want to support developing real production systems once you've found an approach that works for you.
So I don't have a concrete set of features beyond what's on the readme or the issues page, but I look at those features as just a first milestone. Beyond that I have a number of ideas and things I'd like to include but I'm open to anything that would fit the goal of enabling others to develop their own agent systems.

I'm somewhat taking a "let's justify what we need as we go" approach and trying to minimize assumptions.

I like this idea of "let's justify what we need as we go" !

Overall I want to support practical development of agent systems. Since it's not entirely clear what the best approaches are, or that there is a "best" approach, I think experimentation is necessary at this time. So I want the library to be flexible but I also want to support developing real production systems once you've found an approach that works for you.

Fully agree and support this way of exploring.

This issue has been addressed with the 1.3 changes (https://github.com/operand/agency/pull/97). Specifically, you can now add a meta field to all messages. See: https://github.com/operand/agency/tree/main/docs#using-the-meta-field
Closing for now but feel free to reopen if needed.


Modular data services

Description
To support the usage and implementation of other databases including redis, qdrant, and pgvector, I modified the compose files to use an include for the three microservices corresponding to data serving and retrieval (vector-db, retriever, and dataprep).
Issues
Tangentially related to #439
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds new functionality)

Dependencies
N/A
Tests
Ran existing test on xeon to verify that these changes didn't affect the existing redis implementation. Manually mutated the file to modify the DATA_SERVICE environment variable (as well as corresponding variables such as PG_CONNECTION_STRING) and verified that this works with pgvector and qdrant.

looks good to me

Error is coming from outdated docker-compose on the runner. Minimum required docker-compose version for include is 2.20

@sunnstix,
Please resolve the conflicts. We have made some changes in docker compose files.


No further position received from stream

🐛 Bug Report
With location permissions being set to "Accuracy: reduced" I only receive a position when starting the stream - but no further position.
Expected behavior
At least with lowest accuracy submitted via settings there should be a constant position stream.
Reproduction steps
Code, that starts the stream.
_positionStream = Geolocator.getPositionStream(
        locationSettings: _getLocationSettings()
    );
    _positionSubscription = _positionStream!.listen((Position? position) {
      if (position != null && state.status.isActive) {
        add(PositionTracked(
            delivery: delivery,
            position: position
        ));
      }
    }, onError: (error) async {
      try {
        if (state.status.isActive) {
          LocationPermission permissions = await _checkPermissions(
              openAppSettings: true
          );

          if (permissions == LocationPermission.always ||
              permissions == LocationPermission.whileInUse) {
            add(TrackingStopped());
            add(TrackingStarted());
          }
        } else {
          throw error;
        }
      }
      catch (_) {
        rethrow;
      }
    });

  LocationSettings _getLocationSettings() {
    if (Platform.isAndroid) {
      return AndroidSettings(
          accuracy: LocationAccuracy.best
      );
    } else if (Platform.isIOS) {
      return AppleSettings(
        accuracy: LocationAccuracy.best,
        pauseLocationUpdatesAutomatically: true,
        showBackgroundLocationIndicator: false,
      );
    } else {
      return const LocationSettings(
        accuracy: LocationAccuracy.high,
        distanceFilter: 100,
      );
    }
  }

I also tried setting the accuracy to a lower mode step by step. But even with lowest there is no further action on the stream. onError did not get hit. I also added a onDone for testing purpose. But that did not get hit either.
The only received position was received within onData - so there was no extra call on something else.
Configuration
Version: 1.x
Platform:

[x] :iphone: iOS
[ ] :robot: Android

Which version of the plugin are you using?

geolocator: ^9.0.2

On android, this will not work:
    final position = await Geolocator.getCurrentPosition(
      desiredAccuracy: LocationAccuracy.lowest,
      timeLimit: Duration(seconds: 20),
    );

This is our current workaround:
    final position = await Geolocator.getCurrentPosition(
      // On android .lowest does not work for some reason. Use low instead, or it will load forever.
      desiredAccuracy: Platform.isAndroid ? LocationAccuracy.low : LocationAccuracy.lowest,
      timeLimit: Duration(seconds: 20),
    );

Dear @i-dentify,Can you please post the output of flutter doctor -v? Therefore, I can reproduce this issue. And can you also add some detailed information on how you are testing this (e.g. simulator, real-device, indoor/outdoor, permissions granted)?

Dear @i-dentify,Can you please post the output of flutter doctor -v? Therefore, I can reproduce this issue. And can you also add some detailed information on how you are testing this (e.g. simulator, real-device, indoor/outdoor, permissions granted)?

I am testing in iOS Simulator with "City run" as selected option. Permissions are set as "While in use" with precise location accuracy being disabled.
flutter doctor -v
[✓] Flutter (Channel stable, 3.10.6, on macOS 13.4.1 22F770820d darwin-x64, locale de-DE)
    • Flutter version 3.10.6 on channel stable at /usr/local/Caskroom/flutter/3.0.3/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (vor 13 Tagen), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/mario/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /Users/mario/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.10121639/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/mario/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.10121639/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.4)
    • IntelliJ at /Users/mario/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.4)
    • IntelliJ at /Users/mario/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9225.16/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.80.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • TC26 (mobile)              •<PHONE_NUMBER>2720                       • android-arm64  • Android 10 (API 29)
    • iPhone 14 Pro Max (mobile) • 49DCCDA8-EB9E-4397-8DC4-A2FCE80D1FAA • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 13.4.1 22F770820d darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 114.0.5735.248

[✓] Network resources
    • All expected network resources are available.

• No issues found!


[MySQL Compat] SUM result types

As discussed in https://github.com/dolthub/go-mysql-server/pull/1476#issuecomment-1352731490 --
The result type for SUM aggregations in go-mysql-server does not match MySQL's. Even though the actual SumBuffer that performs the computation internally uses either float64 or Decimal, the type for the resulting column in the planned schema defaults to the type of the underlying column.
As an example: in MySQL, summing a column of INT (i.e. int32) results in a DECIMAL result for the output row. This is the same when summing any other integral type, regardless of whether the type has overflowed or not. In go-mysql-server, summing a column of INT returns INT. In fact, summing any integral type returns the same integral type.
The general rule for MySQL types in SUMs is as follows:

Any accurate numeric type (e.g. INT, BIGINT, SMALLINT, TINYINT, DECIMAL, etc) sums into DECIMAL.
Any approximate numeric type (e.g. FLOAT, DOUBLE) sums into DOUBLE.

Would you be interested on a PR to mimic this behavior much more closely?

Yes. We would definitely take a PR here.

Hey @vmg,
GMS behavior here has changed.
We currently always return DOUBLE regardless of the input types (this might also be the cast for COUNT).
We can start fixing this soon. Unless you still want to :)

Is there any progress?
we got float64 even from select unix_timestamp('2000-01-01')


test with pvinis repo with the two-dot diff

Summary:

This is in preparation of using the new branch structure of the purge repo, using one branch per version.
GitHub does not support getting a patch file from two-dot diffs by appending .diff in the url, so I keep them in https://github.com/pvinis/rn-diff-purge/tree/master/diffs.
Test Plan:

We just test it by upgrading a project.

@pvinis what's the status of adding diffs/ dir to https://github.com/react-native-community/rn-diff-purge?

planned for today :)
I came back from holidays yesterday evening and I'm just leaving the office.

Done. We now have the old list in old/master, that has the tags like version/x.y.z, and the new table in master, with all the diffs in the diffs branch, and purge-web pointing to rnc.
I'll close this issue since everything is in sync now, and we store the diffs ourselves.


unclear which icinga role is used

In icingaagents.yml reference is made to a dependency (role: icinga). This is not present in the repo and not declared anywhere.
I'm assuming a role is being used from Galaxy - can you specify which one?

RCIAM does not rely on a specific monitoring tool, so it's cleaner to move GRNET-specific playbooks to a different repository. The icingaagents.yml playbook has been removed with commit 1abfe64
🙏  Thanks for bringing this up, Bruce!


Added Anagrams.c

Added Anagrams.c
Added Anagrams.c < Solved the anagrams problem in C>
The program takes input from the user as two strings and provides the output as number of letters to be deleted to make them anagrams< Added anagrams.c>
Fixes #248
Addition of Anagrams.c
Please delete options that are not relevant.

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

Checklist:

[x ] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ x] I have commented my code, particularly in hard-to-understand areas
[x ] I have made corresponding changes to the documentation
[x ] My changes generates no new warnings
[ x] I have added tests that prove my fix is effective or that my feature works
[ x] New and existing unit tests pass locally with my changes
[ x] Any dependent changes have been merged and published in downstream modules

Wrong files uploaded
Making changes from the master branch


Added missing deploy task to recipe/common

recipe/common.php currently does not define a deploy task and is the only recipe that's missing it.
Newcomers may stumble over this behavior, as the documentation asks you to run dep deploy as one of the first steps.
This PR fixes this.
It's compatible with recipes that are based on common, as overwriting tasks is allowed (e.g. common > symfony > contao).
Note: It appears that this task was previously defined (see #296).

[ ] Bug fix #…?

[x] New feature?

[ ] BC breaks?

[ ] Tests added?

[x] Docs added? --> updated.
Please, regenerate docs by running next command:
$ php bin/docgen

Makes sense.