Callback method inconsistent both in Android/IOS

We have configuerd our App with background_locator 1.2.2 + to record the lat/long every 2 mins (once) and then sending it to the backend inside callback method.
But few times its not sending every 2 minutes instead it sends any time between 8 to 15 minutes particularly when the App is in the Background state.
The interesting behavior is during this inconsistent interval time between 8 to 15 mins it is recording lat/longs locally in small intervals, every few seconds and then it is sending the data in bulk to the backend after a period of time which is not what it should be doing.
Have the Flutter Development team encountered such issue in the past?
What is the solution you recommend?
Thanks in advance

Hi @venkateshironman
Thank you for opening an issue.
Some people had similar problem with latest version of android, so I have released a new version with a fix.
Please use the latest version of the library (1.4.0), the problem should be solved.

@mehdok Thanks  a ton for quick and prompt response really appreciate it
Is this fix works for IOS as well?
Thank you

I believe iOS don't have this problem at all.
Do you have any problem with iOS?

@mehdok yes we have found same issue in iOS

Interesting, it would be nice if you could provide more info, some code, logs, or any useful data that you could think of;


add validation for base64 url without = padding

Fixes Or Enhances
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

Change:
As flagged in this issue, validation fails for some strings encoded using base64.RawURLEncoding function.
The discussion around whether padding should be considered optional or not is rather long. Some of it can be found here: https://github.com/golang/go/issues/4237. Following which, RawURLEncoding was introduced in base64 package.
The general rule of thumb regarding padding seems to be that you MUST be padding when encoding, but SHOULD be able to handle both padded and unpadded inputs when decoding. Therefore, we should provide support for validating unpadded encoded inputs.
Instead of modifying the "base64url" tag to accept unpadded inputs, it makes more sense to have a separate tag - "base64rawurl". This way it would be clear to the developer and they would use one or the other, or both back to back, depending on their usecase.
PS: formatting changes in doc.go because of go 1.19 updates. Please lmk if I should revert them.
Closes #1002
@go-playground/validator-maintainers

Coverage increased (+0.005%) to 74.188% when pulling c8bccf36498372d2b335960a1b4de662490c7bdb on yasoobh:master into c7e0172e0fd176bdc521afb5186818a7db6b77ac on go-playground:master.

Will this change be added to any version soon?

Any chance to have the last code review needed? 🥹

@deankarn you are awesome! many thx for this gorgeous lib!


Added solution of rotate_image in c++

This patch is about including solution of rotate image problem of leetcode in c++ language. This is the most optimal approach for solving this problem.

Can you please review this code ...

@iamdestinychild Can you please review this ?

@iamdestinychild ...

@vbhavsar  Can you please review this pr ....


Terminal errors and browser warnings in 0.6.2

Getting terminal errors and browser console warnings when upgrading from 0.6.1 to 0.6.2 for icons with names ph:table and ph:code:

Should be fixed in v0.6.3 :)

Thanks, that was fast 🙏🏽 🙏🏽 🙏🏽

Hey @Atinux, it looks like the problem is actually still there in v0.6.3:

Also, aliases like 'brand': 'IconBrand' with a global component named IconBrand.vue are now not working anymore.

Damn I did not expect people to use alias -> components 😅
Fixed in v0.6.5
Also I do not have any warning locally, you can run the playground/ I added a case for it: https://github.com/nuxt-modules/icon/blob/c206f6e7105f92507b8d4f280eea3e0f8467a355/playground/app.vue#L49-L53

It seems resolved now 🙏🏽
Of course, alias -> components is one of the best features ;)


runtests.py ignores specified tests and just runs all tests

For example, running:
$ $ python runtests.py TestDispatcher

executes all tests. According to the help, this should only execute tests in the TestDispatcher class:
$ python runtests.py --help
usage: runtests.py [-h] [-v] [-q] [-f] [-c] [-b] [-R] [-m] [--profile]
                   [tests [tests ...]]

positional arguments:
  tests               a list of any number of test modules, classes and test
                      methods.

optional arguments:
  -h, --help          show this help message and exit
  -v, --verbose       Verbose output
  -q, --quiet         Quiet output
  -f, --failfast      Stop on first fail or error
  -c, --catch         Catch ctrl-C and display results so far
  -b, --buffer        Buffer stdout and stderr during tests
  -R, --refleak       Detect reference / memory leaks
  -m, --multiprocess  Parallelize tests
  --profile           Profile the test run

Examples:
  runtests.py                           - run default set of tests
  runtests.py MyTestSuite               - run suite 'MyTestSuite'
  runtests.py MyTestCase.testSomething  - run MyTestCase.testSomething
  runtests.py MyTestCase                - run all 'test*' test methods
                                       in MyTestCase

Yeah, it you want to run a specific tests, you have to execute the proper test module, e.g. python -m numba.tests.test_dispatcher -v TestDispatcher.

Perhaps there's a way to fix it, though.

I looked at this, and plain unittest wouldn't do better (it gives an AttributeError instead of running the test suite).

runtests.py is now the primary interface to testing and does this properly, closing.


Use amazon's servers by goofys mount S3 bucket,Copy the file to the bucket,1.2GB File need about 3 minutes,Why such a long time?（os：ubuntu 14.04 ，region：cn-north-1）

dup of #206


Issue making client/server for fivem

What version are you using?
Latest not sure of the version i just downloaded using the github readme
What were you trying to do?
Create Fivem client template using "python collei fivemclient"
What were you expecting to happen?
To get no errors when running this and successfully create the file
What actually happened?
i got the issue of getting the classic "Couldn't fetch latest version of CitizenFX.Core.Client: Code 404"
What are your system specifications?
No response
Anything else you might want to add?
No response

Any idea how i can fix this?

I'm still wondering why it happens in the first place, as I have been unable to replicate this on 4 different devices (Windows 10, Windows 11, Arch Linux and Debian) on 3 different internet connections (Fiber, 4G and DOCSIS).

i have the latest pip and python 3.12.4 im not really sure why either honestly it worked fine then randomly happened


Improve formatting and acronyms

Reference issue
The issue describing the bug or feature that this PR addresses.
Tasks

[ ] Unit tests added that reproduce issue or prove feature is working
[ ] Fix or feature added
[x] Documentation updated (if relevant)
[ ] Unit tests passing after adding fix/feature
[ ] Apps updated and tested (if relevant)

Hi mdvthu, I apprectiate the effort but I wouldn't bother as I'm already working on a PR that will fix all this stuff.

Dear scaramallion
I'm keen to contribute.
I thought I'd try to start with something small!
I'll keep a look out for other necessary improvements.
Best wishes
Mark
On 27 July 2018 01:47:30 BST, scaramallion<EMAIL_ADDRESS>wrote:

Hi mdvthu, I apprectiate the effort but I wouldn't bother as I'm
already working on a
PR that will fix all
this stuff.

#192 and #184 seem like a good place to start. require_calling_aet should be changed to accept a bytes or list of bytes and require_called_aet should be changed to a bool, with corresponding changes in Association._run_as_acceptor. Then just update the docstrings and the apps to match and make sure there's full test coverage for the changes.


Read Transfer event for transfer transactions

The change fixes issue related to transfer tokens transaction.
Sometimes there is a valid transaction without event. In this case flag hmt_transferred will be True, but actually this is wrong hmt_transferred should be False. Changed code checks Transfer event of transaction and if it exists switches hmt_transferred to True.
Moreover self.balance() may also return wrong value if one of blockchain node still doesn't have information about transaction, code takes balance from tx_receipt.

@alidzm please, provide a description to this PR.

I wish we didn't pin the dependencies

I wish we didn't pin the dependencies

@alidzm , we you worked around cryptography package error about the SO by adding a different ubuntu imagem in docker, we have keep version as *, as version cryptography v37 is announced to be long-term.

@alidzm please, provide a description to this PR.

@Dzeranov Done


Work on greedy graph coloring.

See https://github.com/bobluppes/graaf/issues/88.

I removed the empty dir 'coloring' and renamed 'greedy_graph_coloring_test.cpp' to 'graph_coloring_test.cpp'
If a separate dir is used that contains the tests, it seems that it won't execute without other changes.

I removed the empty dir 'coloring' and renamed 'greedy_graph_coloring_test.cpp' to 'graph_coloring_test.cpp' If a separate dir (coloring) is used for contain different files with test cases (to reflect the directory structure in the include dir), it seems that it won't execute the tests in these files without other changes.

Thanks for reporting! Sounds like I will have to adjust the CMake setup in order for this to work. I will do so in a follow-up

closes #88


Use an Enum to denote the index type rather than a String

What
Use an enum for the index type parameter rather than a string.
How

Deprecate the methods which present a string parameter for the index type
Create a new enum CDTQIndexType
Add new methods to replace the deprecated methods.
Add conversion methods to support going from the text representation to the enum representation.
Behaviour change: Using the string version for the index type will result in an exception being thrown if it is not possible to match the text to one of the defined enum values

Why
Using an enum will reduce confusion for users, where they are attempting to provide a custom index type
when the purpose of the parameter is to pass a fixed set of index types.
Reviewers
reviewer @mikerhodes
Issues
#231

As far as I can see the functionality is there. Looks like clang format needs running over the changed lines, and there were a couple more comments.

Ran Clang-format and did some commit reworking

+1

@brynh I'm not going to change in indentation in the tests, because they currently match what is present from file, (at least when I stare at it in xcode)

+1


Add Thread Certification 9.2.10 to automated test.

Current coverage is 72.16% (diff: 100%)

Merging #761 into master will decrease coverage by 0.36%

@@             master       #761   diff @@
==========================================
  Files           106        105     -1
  Lines         15837      15828     -9
  Methods        2159       2155     -4
  Messages          0          0
  Branches       1882       1882
==========================================
- Hits          11488      11423    -65
- Misses         3734       3791    +57
+ Partials        615        614     -1

Powered by Codecov. Last update eb2277a...43bd473


HDDS-3291. Write operation when both OM followers are shutdown.

What changes were proposed in this pull request?
Add IPC client time out, so that the client will fail with socket time out exception in cases of 2 OM node failures.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3291
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
Tested it in docker compose cluster with 1 minute, and see that it failed finally, instead of hanging.
To repro this test, we need to change leader.election.time.out value also to large value, as we need this request to be submitted to ratis, and as ratis server keeps on retry then only we will see this issue.
2020-03-27 16:25:27,625 [main] INFO  RetryInvocationHandler:411 - com.google.protobuf.ServiceException: java.net.SocketTimeoutException: Call From c5263a1df1ad/<IP_ADDRESS> to om2:9862 failed on socket timeout exception: java.net.SocketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/<IP_ADDRESS>:56460 remote=om2/<IP_ADDRESS>:9862]; For more details see:  http://wiki.apache.org/hadoop/SocketTimeout, while invoking $Proxy19.submitRequest over nodeId=om2,nodeAddress=om2:9862 after 15 failover attempts. Trying to failover immediately.
2020-03-27 16:25:27,626 [main] ERROR OMFailoverProxyProvider:285 - Failed to connect to OMs: [nodeId=om1,nodeAddress=om1:9862, nodeId=om3,nodeAddress=om3:9862, nodeId=om2,nodeAddress=om2:9862]. Attempted 15 failovers.
For now, the changed config affects all rpc clients in the system, in the future if we want to add a new RPC client time out, we can add a new config. For now, using the same config of ipc client.

Thank You @arp7 for the review.


Dropbox Feature is outdated

The Dropbox feature has 2 major issues:

It does not work out of the box, it requires adding another method into the “DropboxDownloader” -> public override void Download(string url, string destFolder, Action<long> onChunkDownloaded) and this method is when we convert it 1 to 1 to Dropbox Code not multithreaded.

Dropbox got a Terms of Service Update back in September 2021 which changes the OAuth workflow, the new workflow says it's no longer possible to create “Long living Tokens” but the App can request an “Short living Token” from the Dropbox Server which can be used as temporary credentials while using the patcher. Here is an example in c# of the new OAuth workflow Github Dropbox API Example. Using just an “Short living Token” makes the patcher not connect any more after some hours with the same token.

I'm currently editing the Files for my own game so once I've done it I can send a Pull Request or sharing the Code to the PATCH Authors to review and use.

Hey there Lukas, could you please send me the working examples of the DropboxDownloader please? Can't make it work properly. Thanks!


WIP: Neon uint32

Re-opening later, need to push some tests and I don't want to trigger builds on CI that will fail anyway


mds: fix mds placement

mds pod created from UI and default mds pod
can be created at same node

/assign @malayparida2000 @iamniting

/unhold

/cheery-pick 4.17

/cheerypick release-4.17

/cheery-pick release-4.17

/chery-pick release-4.17

/cherry-pick release-4.17


feat(RHTAPREL-732): release: use pr values for RPA pipeline

This commit allows the release-service-catalog URL and revision to be overwritten by environment variables so when the release-pipelines suite runs as part of CI, developer pipelines can be run.
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/lgtm

/retest

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/lgtm

/approve


How to install sharp for AWS Lambda from musl-based Linux (Alpine, Void)

Using Alpine Docker image to build and deploy AWS lambda function.
Trying this command to install proper pre-compiled binaries:
rm -rf node_modules/sharp && SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm i --arch=x64 --platform=linux --target=8.10.0 sharp

But installation automatically detects Alpine Linux and downloads wrong binaries( musl )
Which leads to this error when running this lambda function:
{
  "errorMessage": "libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory",
  "errorType": "Error",
  "stackTrace": [
    "Module.load (module.js:565:32)",
    "tryModuleLoad (module.js:505:12)",
    "Function.Module._load (module.js:497:3)",
    "Module.require (module.js:596:17)",
    "require (internal/module.js:11:18)",
    "bindings(/var/task/node_modules/bindings/bindings.js:112:48)",
    "Object.<anonymous> (/var/task/node_modules/sharp/lib/constructor.js:10:34)",
    "Module._compile (module.js:652:30)",
    "Object.Module._extensions..js (module.js:663:10)"
  ]
}

If there is a way to specify that I want to use specific binaries like libvips-8.7.0-linux-x64.tar.gz instead of libvips-8.7.0-linuxmusl-x64.tar.gz?

@lovell maybe it's possible to add family param in platform.js to allow a user to specify it in addition to auto-detection mechanism?

Hello, I'm not sure I understand the use of the musl-based Alpine to prepare code for the glibc-based AWS Lambda runtime environment. That's going to cause problems for any native dependencies, not just sharp.


Fixed Tileset Editor bug related to polygon size

Fixes #27035

Crash was due to null case not taken into account for polygon.size, added if case to fix the problem of not checking for polygon.size() == 0

@Chaosus Any ideas why Travis CI build is failing? build is successful on my local machine.

I think you should use clang-format tool (best way to do it using VSCode extension) - see https://docs.godotengine.org/en/latest/community/contributing/code_style_guidelines.html

@Chaosus Thank you.

You welcome. You should also squash the commits together as its also required to our pipeline - see https://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#mastering-the-pr-workflow-the-rebase

#27063 has been fixed by #27200, please rebase to keep only the TileSet Editor changes.
For future PRs, please do one PR for each unrelated change to avoid such issue.

Still needs to be rebased. Please make sure that the resulting commit log is clear.
See http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html

@akien-mga Yes I did try, there seems to be a problem with the branch I'll sort it out in 1-2 days

I completely forgot this PR, I superseded this with mine: #27602

@MarianoGnu Please don't merge a PR when it has a messy commit history. This PR has 4 commits for a +2 change, that doesn't fit our contribution guidelines.

I even asked twice for a rebase above, please read pending comments before merging.

We can skip cherry-picking this 4 commits anyway, they're superseded by #27602.


[jest-each] Update "Importing" section of the doc

Summary
Fixes the doc for ES5 import.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8425   +/-   ##
=======================================
  Coverage   62.32%   62.32%
=======================================
  Files         266      266
  Lines       10733    10733
  Branches     2615     2614    -1
=======================================
  Hits         6689     6689
  Misses       3461     3461
  Partials      583      583

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 1404933...49a0c56. Read the comment docs.


Write an artman release playbook

Closing since the releases are automated in CircleCI. To release a new version, just update the version number in Dockerfile and draft a new release on GitHub using vX.Y.Z as a tag.


Feature: use the Nexus Publish plugin

What this PR changes/adds
Uses the Nexus publish plugin to publish Snapshots and release versions to OSSRH.
Why it does that
To not have to release manually.
Linked Issue(s)
Closes #1426
Closes #834
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

@ndr-brt @juliapampus @alexandrudanciu I'd really love to get this merged quick, so we can close out M4.

Codecov Report

Merging #1428 (c3137fb) into main (627615f) will increase coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1428      +/-   ##
============================================
+ Coverage     67.61%   67.69%   +0.08%
============================================
  Files           719      719
  Lines         15935    15978      +43
  Branches       1043     1043
============================================
+ Hits          10774    10817      +43
  Misses         4687     4687
  Partials        474      474

Impacted Files
Coverage Δ

...ment/transferprocess/model/TransferRequestDto.java
100.00% <0.00%> (ø)

...ontractdefinition/model/ContractDefinitionDto.java
100.00% <0.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 627615f...c3137fb. Read the comment docs.


Upgrade embedded Postgres dependency and Postgres version

so that we can test features in newer version of Postgres.

can we make this configured as a system property of the build, so we can run several jobs in Travis with different DBs ?

Sure, please check https://github.com/reactiverse/reactive-pg-client/pull/226/commits/758aee911be14ebee020baf36bc99e0860d56197.

Would it be desirable to integrate this with docker rather than using the embedded package? This way can test pretty much any version and don't have to rely on the embedded library to be updated and such.
I should be able to set it up pretty fast. It's what I use in my builds.

Hi, testing with docker is supported currently and please check https://github.com/reactiverse/reactive-pg-client/blob/master/README.adoc#testing-with-docker

Hi yes, sorry I meant for travis tests/builds.


Consider removing abstractions in favour of clarifying requirements to data serialization

The following might result in a slightly simpler API:

get rid of the namespaced data abstraction altogether and change the Push method to take in raw byte pairs (nid, data) instead. This would simplify the API and reduce the number of introduced types / interfaces (see https://github.com/lazyledger/nmt/pull/3#discussion_r470297938)

I think clarifying the requirements on how the data should be serialized and sorted is favourable over adding serialization concerns into the NMTs API.
ref: https://github.com/lazyledger/nmt/pull/3#issuecomment-673587678
related discussion: https://github.com/lazyledger/nmt/pull/3#discussion_r468190574

This would also simplify using an nmt here https://github.com/lazyledger/rsmt2d/issues/8:
If the tree would take in just bytes, the API could be abstracted into a Merkle Tree interface that would be the same for a regular merkle tree and a namespaced one. Alternatively, we can use a wrapper that takes in raw bytes instead.

#14 removed the namespace.Data interface. One thing we can still consider is to even remove the explicit separation between id and data when calling Push: https://github.com/lazyledger/nmt/blob/4b4c58a9e7c071db650b27a69dccde4821411d07/nmt.go#L241-L248
Thinking about it, if the tree knows the size of the namespace ID it is sufficient. But that is of very low priority and we can think about this later.

#14 removed the namespace.Data interface. One thing we can still consider is to even remove the explicit separation between id and data when calling Push: https://github.com/lazyledger/nmt/blob/4b4c58a9e7c071db650b27a69dccde4821411d07/nmt.go#L241-L248
Thinking about it, if the tree knows the size of the namespace ID it is sufficient. But that is of very low priority and we can think about this later.


Inferred type of an iteration variable always optional?

Type of issue
Missing information
Description
It seems that the inferred type of an iteration variable is always optional. Why is that? The documentation does not explain that.
E.g.
var list = new List<string>();
foreach (var item in list) { } // item has type _string?_ instead of the expected _string_

Interestingly the compiler does not complain when I explicitly specify the iteration type:
var list = new List<string();
foreach (string item in list) { } // item has the expected type _string_

Page URL
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/statements/iteration-statements
Content source URL
https://github.com/dotnet/docs/blob/main/docs/csharp/language-reference/statements/iteration-statements.md
Document Version Independent Id
8b6cb66c-8bef-fed0-1677-acee6bd3e052
Article author
BillWagner

Hi @cveld
First, to make sure I'm interpreting your issue correctly, I think that by saying "the type is optional", you mean the implied type is a nullable reference type.
If that's correct, it is mentioned here in the language reference.
We should add a link to that section from here (possibly in a similar note).
I'll add this to our backlog, and add the "help wanted" label if anyone wants to submit a PR before we make our next update.

Can you also explain why this is happening? And is there any way to enforce a non-nullable reference type? I guess I can switch over to the c# 9 way:
List<string> list = new();

or even:
List<string> list = []

@cveld
Two parts to the answer: First, Both of those are valid. They create empty collections. Neither contains a null value.
Second, this section explains why any reference variable declared with var is a nullable reference type: You can rely on the compiler's null state static analysis to ensure you don't dereference null. That's the important part for your code: you won't thrown any null reference exceptions, because the compiler will warn you if you dereference null, or assign a possibly null value to another variable that isn't known to be non-null.


Fix nested prefabs with custom MRTK inspectors

Overview
When creating custom controls via EditorGUILayout.blah that isn't a property field, unity is not able to correctly track changes between the original component in the prefab and modifications at the scene layer (or higher level prefab layers). Usually Unity out-of-box highlights/bolds the modified field and allow right click options to control the property.
This change is to go through the custom inspector and identify where MRTK code needs to use EditorGUILayout.PropertyField or use the EditorGUI.PropertyScope to enable this functionality back in Unity.
Changes

Fixes: #4369

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

Friendly ping to reviewers @julenka @keveleigh  @davidkline-ms  @thalbern .
This PR has been out for 3 weeks.

/azp run


[KOGITO-1162] Added services_image_version option

https://issues.redhat.com/browse/KOGITO-1162
Migrated some constant to infrastructure package as I don't think smoke package should rely on cmd and/or controller packages.
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

smoke tests passed with images 0.8.0-rc1

great work, looks good to me, is it ready to merge?

yes it is :)


Fix yarn production dependencies and bump laravel mix to version 5

What

Fix yarn production dependencies
bump laravel mix to version 5

Why
Some build problems were occuring because of wrong development and production dependencies
Issue
Fixes https://github.com/CIMonitor/CIMonitor/issues/161

Tested this thoroughly and it works really smooth! Merged.


Added ec2-api-tools <IP_ADDRESS>

Added ec2-api-tools https://aws.amazon.com/developertools/351

Thanks :smile:

Nice :+1:


Logstream and metadata management Implementation

changed all the raw pointer to shared pointer and merge to the origin/master


release.sh: exit -1 must display an ERROR log line

When release.sh exits with code -1, then it must display an ERROR log line so that the error is quickly identified.

Something like wrapping each command as follow?
if ! command; then
  >&2 echo "[ERROR] ..."
fi


matching tangram-es glsl fix for globals init

Matching @blair1618 fix of glsl global init bug https://github.com/tangrams/tangram-es/commit/63120ab16910ea7dfd91dbb1c2374f0b0699f5c7#commitcomment-14197819

Tests are failing with GLSL errors on material uniforms, have you verified this locally? It may be caused by certain scenarios.
https://circleci.com/gh/tangrams/tangram/1952

I did. I did a make lint and run a local python server to see if everything was looking right

But it looks like there are problems when you use these uniforms in styles.
Can you try with material blocks?
On Thu, Nov 5, 2015 at 11:48 AM, Patricio Gonzalez Vivo <
<EMAIL_ADDRESS>wrote:

I did. I did a make lint and run a local python server to see if
everything was looking right
—
Reply to this email directly or view it on GitHub
https://github.com/tangrams/tangram/pull/212#issuecomment-154118975.

Trying gotham.yaml (https://github.com/tangrams/tangram-sandbox/blob/gh-pages/styles/gotham.yaml). Seams fine.

Lint produce no errors

Hmm, could be a test error, I'll dig in.
On Thu, Nov 5, 2015 at 1:09 PM, Patricio Gonzalez Vivo <
<EMAIL_ADDRESS>wrote:

Trying gotham.yaml (
https://github.com/tangrams/tangram-sandbox/blob/gh-pages/styles/gotham.yaml).
Seams fine.
[image: screen shot 2015-11-05 at 1 05 47 pm]
https://cloud.githubusercontent.com/assets/346914/10977256/fbad4660-83bd-11e5-8f4e-a886d6ffd1a5.png
Lint produce no errors
[image: screen shot 2015-11-05 at 1 09 11 pm]
https://cloud.githubusercontent.com/assets/346914/10977329/6edb45a6-83be-11e5-9a3f-fffc2f4667d7.png
—
Reply to this email directly or view it on GitHub
https://github.com/tangrams/tangram/pull/212#issuecomment-154140929.

The test accurately shows that remotely loaded styles are broken, e.g.:
scene.load('https://raw.githubusercontent.com/tangrams/eraser-map/gh-pages/eraser-map.yaml')
Need to investigate why. Something is wrong with light/material injection in that case.

I was looking at eraser-map running with this changes... looks fine too : /

Just a couple of icons not found:
MPZN ZoomControl: Conditional zoom control active.
zoom-control.js:32 MPZN ZoomControl: No touchscreen detected, exiting.
module.js:91 Tangram v0.3.3: Scene.makeWorkers: initializing worker 0
module.js:91 Tangram v0.3.3: Scene.makeWorkers: initializing worker 1
module.js:91 Tangram v0.3.3: Scene.makeWorkers: initialized worker 0
module.js:91 Tangram v0.3.3: Scene.makeWorkers: initialized worker 1
module.js:91 Tangram v0.3.3: Vertex Array Object extension available
2module.js:91 Tangram v0.3.3: StyleManager.compile(): compiled all styles
module.js:91 Tangram v0.3.3: Scene: build geometry finished
module.js:91 Tangram v0.3.3: Scene: rendered 0 primitives (0 features in selection map)
module.js:91 Tangram v0.3.3: worker 0: updated config
2module.js:91 Tangram v0.3.3: worker 1: updated config
module.js:91 Tangram v0.3.3: worker 0: updated config
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9646/12319/15: [  {"network":81,"response_size":13410,"parsing":3,"rendering":19,"features":133,"geometries":1316,"buffer_size":94080,"geom_ratio":"9.9"} ]
points.js:89 Style: in style 'icons', could not find sprite 'residential' for texture 'pois'
points.js:89 Style: in style 'icons', could not find sprite 'footway' for texture 'pois'
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9645/12321/15: [  {"network":133,"response_size":5189,"parsing":1,"rendering":1,"features":17,"geometries":145,"buffer_size":10392,"geom_ratio":"8.5"} ]
points.js:89 Style: in style 'icons', could not find sprite 'residential' for texture 'pois'
points.js:89 Style: in style 'icons', could not find sprite 'pitch' for texture 'pois'
points.js:89 Style: in style 'icons', could not find sprite 'residential' for texture 'pois'
4points.js:89 Style: in style 'icons', could not find sprite 'residential' for texture 'pois'
points.js:89 Style: in style 'icons', could not find sprite 'wood' for texture 'pois'
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9644/12322/15: [  {"network":275,"response_size":9263,"parsing":1,"rendering":2,"features":63,"geometries":1108,"buffer_size":80340,"geom_ratio":"17.6"} ]
points.js:89 Style: in style 'icons', could not find sprite 'pitch' for texture 'pois'
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9646/12320/15: [  {"network":24,"response_size":23440,"parsing":13,"rendering":54,"features":283,"geometries":3891,"buffer_size":277344,"geom_ratio":"13.7"} ]
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9645/12320/15: [  {"network":98,"response_size":9138,"parsing":2,"rendering":10,"features":104,"geometries":1437,"buffer_size":102576,"geom_ratio":"13.8"} ]
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9648/12321/15: [  {"network":110,"response_size":27736,"parsing":3,"rendering":27,"features":227,"geometries":2873,"buffer_size":202152,"geom_ratio":"12.7"} ]
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9650/12320/15: [  {"network":141,"response_size":11537,"parsing":1,"rendering":10,"features":135,"geometries":2346,"buffer_size":162852,"geom_ratio":"17.4"} ]
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9644/12319/15: [  {"network":153,"response_size":18859,"parsing":2,"rendering":17,"features":229,"geometries":1570,"buffer_size":113340,"geom_ratio":"6.9"} ]
module.js:91 Tangram v0.3.3: Tile: debug for osm/15/9650/12321/15: [  {"network":172,"response_size":20862,"parsing":3,"rendering":13,"features":194,"geometries":2662,"buffer_size":187788,"geom_ratio":"13.7"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9647/12319/15: [  {"network":189,"response_size":59431,"parsing":5,"rendering":28,"features":640,"geometries":7325,"buffer_size":517896,"geom_ratio":"11.4"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9647/12320/15: [  {"network":224,"response_size":88251,"parsing":6,"rendering":35,"features":1046,"geometries":12236,"buffer_size":874668,"geom_ratio":"11.7"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9650/12322/15: [  {"network":280,"response_size":51291,"parsing":6,"rendering":17,"features":378,"geometries":5265,"buffer_size":372300,"geom_ratio":"13.9"} ]
2points.js:89 Style: in style 'icons', could not find sprite 'meadow' for texture 'pois'
points.js:89 Style: in style 'icons', could not find sprite 'pitch' for texture 'pois'
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Scene: rendered 42174 primitives (4135 features in selection map)
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9645/12322/15: [  {"network":408,"response_size":4793,"parsing":1,"rendering":1,"features":16,"geometries":56,"buffer_size":3960,"geom_ratio":"3.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9646/12321/15: [  {"network":25,"response_size":11823,"parsing":11,"rendering":41,"features":112,"geometries":1284,"buffer_size":90396,"geom_ratio":"11.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Scene: rendered 42230 primitives (4521 features in selection map)
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9649/12320/15: [  {"network":104,"response_size":22694,"parsing":3,"rendering":27,"features":206,"geometries":2714,"buffer_size":190284,"geom_ratio":"13.2"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9645/12319/15: [  {"network":136,"response_size":10800,"parsing":0,"rendering":12,"features":143,"geometries":1513,"buffer_size":109272,"geom_ratio":"10.6"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9644/12320/15: [  {"network":149,"response_size":11706,"parsing":0,"rendering":10,"features":173,"geometries":2077,"buffer_size":147132,"geom_ratio":"12.0"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9644/12321/15: [  {"network":160,"response_size":9532,"parsing":1,"rendering":8,"features":84,"geometries":1505,"buffer_size":108300,"geom_ratio":"17.9"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9650/12319/15: [  {"network":169,"response_size":29480,"parsing":1,"rendering":21,"features":343,"geometries":4615,"buffer_size":322944,"geom_ratio":"13.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9647/12321/15: [  {"network":195,"response_size":35254,"parsing":2,"rendering":17,"features":396,"geometries":4938,"buffer_size":351612,"geom_ratio":"12.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9648/12320/15: [  {"network":214,"response_size":48727,"parsing":3,"rendering":18,"features":471,"geometries":5875,"buffer_size":423828,"geom_ratio":"12.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9649/12321/15: [  {"network":236,"response_size":42671,"parsing":3,"rendering":23,"features":569,"geometries":5392,"buffer_size":384072,"geom_ratio":"9.5"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9648/12319/15: [  {"network":264,"response_size":82908,"parsing":4,"rendering":22,"features":656,"geometries":7827,"buffer_size":554652,"geom_ratio":"11.9"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9649/12319/15: [  {"network":292,"response_size":71740,"parsing":8,"rendering":37,"features":463,"geometries":5392,"buffer_size":379644,"geom_ratio":"11.6"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9647/12322/15: [  {"network":341,"response_size":8697,"parsing":3,"rendering":4,"features":86,"geometries":1125,"buffer_size":79356,"geom_ratio":"13.1"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9646/12322/15: [  {"network":348,"response_size":10076,"parsing":1,"rendering":9,"features":139,"geometries":1379,"buffer_size":99120,"geom_ratio":"9.9"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9649/12322/15: [  {"network":365,"response_size":50921,"parsing":8,"rendering":32,"features":558,"geometries":5790,"buffer_size":415668,"geom_ratio":"10.4"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Tile: debug for osm/15/9648/12322/15: [  {"network":411,"response_size":62203,"parsing":5,"rendering":11,"features":285,"geometries":3526,"buffer_size":247320,"geom_ratio":"12.4"} ]
:8000/dist/tangram.debug.js:28448 Tangram v0.3.3: Scene: rendered 97182 primitives (4521 features in selection map)
module.js:91 Tangram v0.3.3: Scene: rendered 78933 primitives (4521 features in selection map)

Nope, see my comment, it is when you load a scene after initial load. That is what the test is for.

I don't understand what you mean.

Maybe is not cleaning the previous blocks of "setup"

Please check the test log for more info. Load the scene, then run this command:
scene.load('https://raw.githubusercontent.com/tangrams/eraser-map/gh-pages/eraser-map.yaml')
It will fail...

This was failing because the material and lighting systems expected to be able to fully replace their respective shader blocks when styles are rebuilt. This doesn't work when they are also injecting into a general injection point that might also be getting blocks from other sources. I was able to fix this by moving some re-init code around to ensure all shader blocks are reset.
Another alternative I had working was to separate out the setup block so that material and lights each had their own main injections, material-main and lighting-main:
https://github.com/tangrams/tangram/commit/90d619df6bb014723517c4a025d143cdbc14391a
That said, I think this solution is probably simpler and more inline with ES anyway.

@blair1618 do we have a device in the office we can test this with? I'd like to do so before merging.

We tested on a Galaxy Note 4 Edge (I think that's the name) that Diana
brought in.
On Nov 6, 2015 9:29 PM, "Brett Camper"<EMAIL_ADDRESS>wrote:

@blair1618 https://github.com/blair1618 do we have a device in the
office we can test this with? I'd like to do so before merging.
—
Reply to this email directly or view it on GitHub
https://github.com/tangrams/tangram/pull/212#issuecomment-154600647.

Verified the issue and the fix on the Samsung Galaxy Note Edge.

:clap: :clap: :+1:


Added equal padding to all sides when saving to bitmap

The RenderToBitmap(double x, double y) method only adds padding to the left and top side of the bitmap. This fix adds padding to bottom and right as well. Perhaps there should be a Thickness as input instead though? It would make more sense but is a breaking change.

Thank you! Yes, this change makes sense.
I would be a bit sceptical about changing that to Thickness since this is a WPF-specific type, and we're trying to be as WPF-agnostic as possible now, because we want to support both WPF and Avalonia in future.
At least let's try to not add WPF dependencies to our public API without very good reasons.


Fails to call base constructor if base has static constructor

Adding static field to base class will add implicit static constructor to this class and method ExtractFieldsFromParent fails to extract fields from this class
       if (baseType?.BaseType is not null && baseType?.Constructors.Length == 1)
as there are two constructors now, even if one is implicit static one.
This affect analyzer too.
Simplest repo:
 class TestBase{
    private static readonly int _s_t5=1;
    private readonly int _t1;

    public TestBase(int t1){
        this._t1 = t1;
    }
  }

 [AutoConstructor]
  internal partial class Test : TestBase
    {
    }

Fixed by #61


What is  Program.mkSimple ?

The sample code uses this line of code:
let runner = Program.mkSimple init update view
what is mkSimple?  Is it makeSimple?  If so, can it be renamed to something more intuitive?

and while we are at it, what is "dispatch" in the sample ?
let view (model: Model) dispatch =
It is of type 'a from the same namespace of my project
and it is used here
command=(fun () -> dispatch Pressed)
I assumed it was a function signature but not really?

Those came from Elmish. You can find the documentation here.

Is that an idiom that can't be replaced then?  It doesn't follow any F# or general functional naming conventions AFAIK

Closing the issue.
Currently we will stick to the Elmish convention.
If you want to make a suggestion to replace those conventions, please open a new issue.


✨ [Feature]: Add Space Component?

What problem does this feature solve
It can provide uniform spacing for each component.
What does the proposed API look like

alignment
direction
size
...

@kagol

@lanrenbulan We need this component, welcome to submit PR to provide this component.🙏


Explicitly configure ReadTheDocs build to use conf.py

Fixes https://github.com/pydata/xarray/issues/9905
I got an email indicating that this configuration will be required as of January 20, 2025.

thanks, @shoyer


Median difference vs. difference in medians for the paired plot

When we work with paired data, it's usually about median difference, not the difference in medians.
Mean change is equal to change in means, but this doesn't hold for medians in general.
> set.seed(100)
> a <- rnorm(100, mean = 1)
> b <- rnorm(100, mean=10)
> median(a-b)
[1] -8.987909
> median(a) - median(b)
[1] -8.986542
# Close, but not exactly equal (finite sampling)

> set.seed(100)
> a <- runif(100, 0, 10)
> b <- runif(100, 10, 20)
> median(a-b)
[1] -9.998856
> median(a) - median(b)
[1] -9.968535
# Close, but not exactly equal

> set.seed(100)
> a <- rlnorm(100)
> b <- rlnorm(100, meanlog = 1)
> median(a) - median(b)
[1] -1.585291
> median(a-b)
[1] -1.586252
# very close

> set.seed(100)
> a <- rlnorm(100)
> b <- rlnorm(100, meanlog = 1, sdlog = 3)
> median(a-b)
[1] -1.275271
> median(a) - median(b)
[1] -1.245357
#quite close

> set.seed(100)
> a <- rbeta(100, 10, 1)
> b <- rbeta(100, 1, 10)
> median(a)-median(b)
[1] 0.8524503
> median(a-b)
[1] 0.8345763
# quite close

But
> set.seed(100)
> a <- runif(100, 0, 10)
> b <- rnorm(100, 5, 1)
> median(a-b)
[1] -0.04137754
> median(a) - median(b)
[1] 0.1726379

> set.seed(100)
> a <- rnorm(100, 1, 1)
> b <- rlnorm(100, 0, 1)
>median(a-b);
[1] -0.1147998
>median(a)-median(b)
[1] 0.0107118

> set.seed(100); a <- runif(100, -1, 3); b <- rlnorm(100, 0, 2); median(a-b); median(a)-median(b)
[1] -0.2062541
[1] 0.2443354

> set.seed(100); a <- c(runif(50, -4, -1), rnorm(50, 2, 4)); b <- rnorm(100, 0, 4); median(a-b); median(a)-median(b);
[1] 0.2922939
[1] -1.24893

and so on.
Another example:
http://onbiostatistics.blogspot.com/2015/12/median-of-differences-versus-difference.html
Actually, I have never seen difference in medians being reported for paired data. It was rather Hodges–Lehmann estimator of the pseudo-media, approached by the median change when the distribution of changes is symmetric, or the relative effect.
I looked at the code and it says it's about difference in medians:
median(treatment) - median(control)
Would you consider adding median difference too?

Many thanks for the note, we'll aim to correct this.
I hope the summer interns can get to it by August. But if you can see a way to do it yourself, please let us know—and send a pull request when ready.


test cases not displaying value of num

Challenge Truncate a string has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
my code passes just find, it's just these included tests aren't displaying the value of num correctly.
truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length) should return "A-tisket a-tasket A green and yellow basket".

truncateString("A-tisket a-tasket A green and yellow basket", "A-tisket a-tasket A green and yellow basket".length + 2) should return "A-tisket a-tasket A green and yellow basket".

My code:
function truncateString(str, num) {

  // if num > str.lenght, return str
  // else if num <= 3
  //   truncate(str-num).concat('...'), return str
  // else, truncate str starting at 0 index to num-3 index
  // str.concat("..."), return str

  //assuming equal to as well since
  //  there would be no reason to truncate str if
  //  the correct num of char can be shouwn
  //  w/o the elipses

  if (num >= str.length) {
    return (str);
  } else if (num <= 3) {
       str = str.substr(0, num);
       str =  str.concat("...");
  } else {
       str = str.substr(0, num-3);
       str = str.concat('...');
  }

  return (str);
}

truncateString("A-tisket", 3);

@yuens1002 thanks for the feedback. Can you elaborate on what you mean by the value of num doesn't display correctly? A screenshot of what you are seeing would be great.

test cases 3 &4 are showing his for the value of num
 "A-tisket a-tasket A green and yellow basket".length)

instead of a whole number like the rest of the test cases

@yuens1002 those were on purpose and valid JavaScript. So there isn't any problem with this challenge. Closing this issue as there is nothing wrong with the challenge. Happy coding!

function truncateString(str, num)
{
if(str.length > num)
{
if(num>=3)
{
str=str.slice(0,num-3);
}
else
{
str=str.slice(0,num);
}
str=str.concat("...");
}
return str;
}


Hi

Could you please specify the license type correctly?

On the start page of the project should not be just written 'view license'. It should be written the name of the license instead. That would it make easier to generate FOSS reports for React projects.

@Wissperwind could you be more specific? There is a license field in the package.json and a LICENSE file in the repo.


transform_if_impl optimization: avoid reduction

I think it is faster this way, avoiding separate reduction.

Thanks! However, I think I would be better not to use back() method in the algorithm since it uses different command queue (and that command queue must be created). Instead, use the iterator to the last element and call its read(command_queue queue)  method.

Coverage increased (+0.006%) to 83.344% when pulling 4bd324e6ff368139b2f2d1b5eac55f50df0ffe2d on Slonegg:master into 86211062a771ab0b494116b4223b63a292ad7d11 on boostorg:develop.

Coverage increased (+0.006%) to 83.344% when pulling 4bd324e6ff368139b2f2d1b5eac55f50df0ffe2d on Slonegg:master into 86211062a771ab0b494116b4223b63a292ad7d11 on boostorg:develop.

Thanks for the patch! Boost.Compute is currently in bug-fix-only mode until Boost 1.62 is released. Once that's out we can get this merged.

Merged! Thanks again!

The changed file leads to errors on Intel CPUs if you try to reduce equal points in stl files:

Intel(R) Xeon(R) CPU X5550 @ 2.67GHz
Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz

In the following example, the points are reduced to 0 on Intel CPUs, but for example on AMD graphic card Sapphire Nitro Radeon(TM) R9 380X the points are reduced to 3670291 on my tested computers.
Operating system is Windows 7 x64
Compiler is VS 2012
#include
#include
#include

const int NUMBER_OF_POINTS = 3679636;
const int NUMBER_OF_EQUAL_POINTS = 6;

struct Float3D
{
	float x;
	float y;
	float z;

	Float3D(float _x, float _y, float _z) : x(_x), y(_y), z(_z) {};
	Float3D() : x(0.0), y(0.0), z(0.0) {};
};

BOOST_COMPUTE_ADAPT_STRUCT(Float3D, Float3D, (x, y, z));

BOOST_COMPUTE_FUNCTION(bool, Float3D_Equal, (Float3D l, Float3D r),
{
	return (l.x == r.x && l.y == r.y && l.z == r.z);
});

BOOST_COMPUTE_FUNCTION(bool, Float3D_Less, (Float3D l, Float3D r),
{
	if (l.x == r.x)
	{
		if (l.y == r.y)
		{
			return (l.z < r.z);
		}
		else
			return (l.y < r.y);
	}
	else
        return (l.x < r.x);
});

int main()
{
	// show devices
	int i=0;
	for (const auto &device : boost::compute::system::devices())
	{
		std::cout << "Device number: " << i << std::endl;
		std::cout << "  Device name: " << device.name() << std::endl;
		std::cout << "  OpenCL Version: " << device.version() << std::endl;
		std::cout << "  Vendor: " << device.vendor() << std::endl;
		std::cout << "  Global Memory Size: " << device.global_memory_size() << std::endl;
		i++;
	}

	// select device
	boost::compute::device device;
	std::vector devices = boost::compute::system::devices();
	std::string selection;
	std::cout << "Device number: ";
	std::cin >> selection;
	device = devices[std::stoi(selection)];
	boost::compute::context context = boost::compute::context(device);
	boost::compute::command_queue queue = boost::compute::command_queue(context, device);

	std::default_random_engine generator;
	std::uniform_real_distribution distribution(-5.0, 5.0);

	// generate 3D data
	std::vector different_vector;
	different_vector.reserve(NUMBER_OF_POINTS);

	for (int i = 0; i < NUMBER_OF_POINTS; i++)
	{
		different_vector.push_back(Float3D(distribution(generator), distribution(generator), distribution(generator)));
	}

	std::uniform_int_distribution distribution_int(0, NUMBER_OF_POINTS);

	std::vector data_vector;
	data_vector.reserve(NUMBER_OF_POINTS * NUMBER_OF_EQUAL_POINTS);

	for (int i = 0; i < NUMBER_OF_POINTS * NUMBER_OF_EQUAL_POINTS; i++)
	{
		data_vector.push_back(different_vector[distribution_int(generator)]);
	}

	// remove equal points
	boost::compute::vector device_data_vector(data_vector, queue);

	size_t size_begin = device_data_vector.size();

	boost::compute::sort(device_data_vector.begin(), device_data_vector.end(), Float3D_Less, queue);

	auto newEnd = boost::compute::unique(device_data_vector.begin(), device_data_vector.end(), Float3D_Equal, queue);
	device_data_vector.resize(newEnd - device_data_vector.begin());

	std::cout << device_data_vector.size() << " of " << size_begin << " points left" << std::endl;

	return 0;
}
The error does not occure with some other value for NUMBER_OF_POINTS.

Interesting, thanks for the report. @Slonegg, can you look into this? We may have to revert before the next release if this breaks Intel platforms.

Not until weekends for sure @kylelutz but if it is driver issue, maybe it's worth submitting this to Intel devs. Maybe add workaround like command queue flush or something to workaround issue on Intel.


Client: ApiBackend implementation

Summary
Implement the API backend of the client.
Details and comments

[x] Save
[x] Read
[x] Refactor LocalBackend().save() & read() to use an id
[x] Add conf
[x] Unit tests
[x] Setup API in CI for unittests
[x] Update API README.md
[x] Update CONTRIBUTING.md

Bug

[x] Fix breaking if file does not exist (#35)

Closes #11
Closes #31
Closes #35

@IceKhan13 & @AnsahMohammad ready for your review :)

I setup the API in the CI in order to have unit test on API backends function as well.
For the id of local backend, I wanted something we can calculate/anticipated so I did a mix between the day and the name of the trial. This way is (almost) sure it gonna stay unique and still readable.

@IceKhan13 I applied your feedbacks and also add some little stuff ^^

Woohoo! 🚀


add process_id to handshake, refactor out status into top-level enum

Made an update replacing the optional status Enum with an optional boolean named success. It's a bit cleaner this way.


Code compilation error SScript

Describe your problem here.
I tried to compile the Psych code and I got this error: HEEELP
FNF-PsychEngine-main/.haxelib/SScript/4,0,1/src/macro/Macro.hx:10: characters 96-100 : SScript is not available, thanks to everyone for their support.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

bro if i see one more issue about this i swear :sob:
look at the DOZEN other issues about this

use SScript 4.1.0, and update to the latest experimental branch

you also can use SScript 6.1.80, just use the experimental branch


Problems with going above topline in a line that doesn't fit the window

The changed test would have looked wrong pre 9.0.1551 (cursor hidden behind the precedes character) but did not actually affect the cursor position. Change test to one that does, and would have failed pre 9.0.1551.

I think there are already screendump tests that verify that the cursor is no longer placed on top of the smoothscroll marker. I think coverage is fine now that we are using the common function where we should.

Changed this PR to fix and outline some problems with moving the cursor in a long line above the top of the window (also including the small previous test change). This didn't work properly for "b" and "ge" with 'smoothscroll', adding adjust_skipcol() for those motions fixes that.
However, there are similar problems when 'smoothscroll' is disabled, 'cpo'+=n is set and 'scrolloff' is small. I'm not sure what should be done about this. Either fix the extra == 1 algorithm in curs_columns() (w_skipcol is set there but incorrectly under the mentioned conditions), or perhaps use adjust_skipcol() even when 'smoothscroll' is not enabled? I added a FIXME test that accepts the wrong result.
Also; moved these calls outside of the loop as they didn't seem to belong there:
+++ b/src/move.c
@@ -1960,12 +1960,14 @@ adjust_skipcol(void)
            curwin->w_skipcol -= width2;
        else
            curwin->w_skipcol -= width1;
-       redraw_later(UPD_NOT_VALID);
        scrolled = TRUE;
-       validate_virtcol();
     }
     if (scrolled)
+    {
+       validate_virtcol();
+       redraw_later(UPD_NOT_VALID);
        return;  // don't scroll in the other direction now
+    }

     int col = curwin->w_virtcol - curwin->w_skipcol + scrolloff_cols;
     int row = 0;

I'll include it.  However, the tests pass even without the code changes.  I suppose you could reproduce the problem you fixed, can you turn that into a test?

However, the tests pass even without the code changes. I suppose you could reproduce the problem you fixed, can you turn that into a test?

Commenting out adjust_skipcol() in bck_word()/bckend_word() results in these failures on my end:
Found errors in Test_display_cursor_long_line():
Run 1, 19:26:20 - 19:26:22:
command line..script /home/luuk/dev/vim/src/testdir/runtest.vim[569]..function RunTheTest[52]..Test_display_cursor_long_line[23]..VerifyScreenDump line 67: See dump file difference: call term_dumpdiff("testdir/failed/Test_display_cursor_long_line_3.dump", "testdir/dumps/Test_display_cursor_long_line_3.dump"); difference in line 1: "|<+0#4040ff13#ffffff0@2|b+0#0000000&@2>b@68"
command line..script /home/luuk/dev/vim/src/testdir/runtest.vim[569]..function RunTheTest[52]..Test_display_cursor_long_line[26]..VerifyScreenDump line 67: See dump file difference: call term_dumpdiff("testdir/failed/Test_display_cursor_long_line_4.dump", "testdir/dumps/Test_display_cursor_long_line_4.dump"); difference in line 1: "|<+0#4040ff13#ffffff0@2|b+0#0000000&>b@70"


Feature/convert medyan

This PR adds conversion support for MEDYAN (http://medyan.org) output files, as well as a filter to translate the scene since MEDYAN spatial values are all positive.
Pull request recommendations:

[ ] Name your pull request your-development-type/short-description. Ex: feature/read-tiff-files
[ ] Link to any relevant issue in the PR description. Ex: Resolves [gh-12], adds tiff file format support
[ ] Provide relevant tests for your feature or bug fix.
[ ] Provide or update documentation for any feature added by your pull request.

Thanks for contributing!

Codecov Report

Merging #20 (cdc516a) into master (8534bb9) will increase coverage by 1.08%.
The diff coverage is 87.60%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
+ Coverage   83.57%   84.66%   +1.08%
==========================================
  Files          34       67      +33
  Lines        1017     1839     +822
==========================================
+ Hits          850     1557     +707
- Misses        167      282     +115

Impacted Files
Coverage Δ

...ariumio/tests/converters/test_cytosim_converter.py
100.00% <ø> (ø)

...iumio/tests/converters/test_physicell_converter.py
100.00% <ø> (ø)

simulariumio/filters/add_agents_filter.py
20.00% <20.00%> (ø)

simulariumio/filters/reorder_agents_filter.py
45.45% <45.45%> (ø)

simulariumio/exceptions.py
62.50% <50.00%> (-4.17%)
:arrow_down:

simulariumio/filters/multiply_time_plot_filter.py
52.63% <52.63%> (ø)

simulariumio/filters/multiply_time_filter.py
69.23% <69.23%> (ø)

simulariumio/readdy/readdy_converter.py
77.14% <71.42%> (+0.44%)
:arrow_up:

...umio/filters/params/multiply_time_filter_params.py
75.00% <75.00%> (ø)

...filters/params/multiply_time_plot_filter_params.py
75.00% <75.00%> (ø)

... and 76 more

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 8534bb9...cdc516a. Read the comment docs.


[Bug]: Lack of Input Validation for txHash Parameter

What happened?
Lack of Input Validation for txHash Parameter
Vulnerable Code
https://github.com/etherisc/flightdelay-ui/blob/develop/src/app/api/purchase/[tx]/route.ts
The vulnerability arises from the direct use of the txHash parameter from the request without validation.
Here is the relevant line of code:
export async function GET(request: NextRequest, { params } : { params: { tx: string } }) {
const reqId = nanoid();
const txHash = params.tx; // No validation performed on txHash
const signer = await getBackendVoidSigner();
// fetch rating data from flightstats
const { policyNftId, riskId } = await checkPolicyCreated(reqId, txHash, signer);

if (policyNftId === BigInt(0)) {
    return Response.json({ error: 'Policy not created yet' }, { status: 202 });
}

return Response.json({
    policyNftId, riskId
}, { status: 200 });

}
Description.
The GET function is responsible for checking the status of a transaction related to policy creation on a blockchain. It accepts a txHash parameter from the request, which is expected to be a valid Ethereum transaction hash.
However, the code does not perform any validation on this parameter before using it.
This lack of validation can lead to several security and operational issues.
Impact.
Malformed Requests: Without validation, the function may accept malformed transaction hashes, leading to errors when interacting with the blockchain.
This can cause the application to crash or behave unpredictably.
Denial of Service (DoS): An attacker could send a large number of malformed or invalid transaction hashes to overload the system, potentially leading to a denial of service for legitimate users.
Security Risks: While traditional injection attacks are unlikely with transaction hashes, accepting unvalidated input can still pose risks, especially if the input is used in other contexts where injection might be possible.
Data Integrity: Using invalid transaction hashes could lead to incorrect or misleading data being processed or returned, affecting the integrity of the application's operations.
Severity.
Critical: The severity is critical due to the potential for application crashes, denial of service, and data integrity issues. The lack of validation exposes the application to a range of potential exploits that could disrupt service and compromise reliability.
Proof of Concept (PoC).
Setup: Deploy the application and ensure it is accessible via a network request.
Execution: Send a request to the GET endpoint with an invalid or malformed txHash.
curl -X GET "http://your-server/api/endpoint?tx=invalidTxHash"
Observation: Observe the server logs and application behavior for errors or crashes resulting from the invalid input.Suggested Fix
Implement Input Validation: Validate the txHash parameter to ensure it matches the expected format and length for a transaction hash (typically a 66-character hexadecimal string starting with "0x").
function isValidTxHash(txHash) {
return /^0x([A-Fa-f0-9]{64})$/.test(txHash);
}
export async function GET(request: NextRequest, { params } : { params: { tx: string } }) {
const reqId = nanoid();
const txHash = params.tx;
if (!isValidTxHash(txHash)) {
    return Response.json({ error: 'Invalid transaction hash format' }, { status: 400 });
}

const signer = await getBackendVoidSigner();
const { policyNftId, riskId } = await checkPolicyCreated(reqId, txHash, signer);

if (policyNftId === BigInt(0)) {
return Response.json({ error: 'Policy not created yet' }, { status: 202 });
}
   return Response.json({
       policyNftId, riskId
   }, { status: 200 });

}
Error Handling: Provide meaningful error messages to users when validation fails, helping them understand and correct the issue. This can improve user experience and reduce frustration.
Logging and Monitoring: Implement logging of invalid transaction hash attempts to monitor potential abuse or attack patterns. This can help in identifying and mitigating denial of service attacks.
What operating system are you seeing the problem on?
Other (please mention in the description)
What browsers are you seeing the problem on?
Other (please mention in the description)
What wallet extension are you using?
Other (please mention in the description)
Rules

[X] I agree to follow this project's rules

The worst that will happen if you call it with an invalid txHash parameter is that the api returns an error instead of the message that the tx was not found. There is no way to change state or anything through the use of this api, so no harm can be done apart from returning the error.
Also the internal API part is not intended to be used on its own. If you do, we do not provide any guarantees for things to work as expected.


Document syscfg for stm32f3 devices

This should covert 100 % of the syscfg register from the stm32f3 devices.

I left quite a view TODOs regarding naming and doubled values, as I'm unsure how to go about this
Some files could be split to smaller chunks, to reduce the duplication (however some devices slightly differ in their description strings and syscfg control register are sometimes quiet different between the devices)
I split up the FPU_IE into it's five flags, as it seems, that they are independent of each other (correct me if I'm wrong about this)
This PR is split into many small commits intentionally. This should make it easier to sqaush it into larger more reasonable commits after all review comments are addressed.

I split up the FPU_IE into it's five flags, as it seems, that they are independent of each other (correct me if I'm wrong about this)

I agree, this seems like the sensible thing to do.

I haven't had time to check all the external interrupt remaps yet. It would be lovely if there was some way to combine them across different devices - perhaps they could be factored out into an exticr.yaml which the individual devices include, if possible?

I initially created a branch dedicated to this, as I too saw this as an obvious improvement. But I discarded  it.
I really did not see a pattern. This is really dependent on the package and therefor on the available gpio pins. E.g. sometimes PFx might exist, sometimes not. I initially split out EXTIx A...D, because I thought every chip must have these. IIRC this was not the case, and the build process will happily accept every documentation I'll throw at it, as enumerated values are not checked against the svd file (as they do not exist initially).
Also, I might have made mistakes, as these flags are documented in descending order in the reference manual (EXTI3, EXTI3, ..., EXT0, EXTI7, ..., EXTI4) and in the yaml file I've written them down as in ascending order.

Thanks for the thorough review. Neat Idea with the script. Should've used something like this in the first place. :sweat_smile:
I've gone through all the view notes and rechecked them against the reference manual again, just to be sure! :)
I'll cleanup the commits and remove left TODO notes to make this PR mergable.

Thanks! Everything looks good to me now, let me know when it's ready to merge.

I rebased to clean up the commit history. The only thing changed is c5eaa4b, which does apply naming-patches, as discussed in https://github.com/stm32-rs/stm32-rs/pull/375#discussion_r460446094, to different occasions.
This is ready to merge, now! :)


Removing title bar

Title bar looks ugly especially with the solarized theme, Any way to remove it (especially on full screen) would make it look nice(r)

http://hackerspace.kinja.com/removing-the-windows-title-bar-with-autohotkey-1015709275

Just hit [ALT] + [RETURN] and the terminal is displayed in full screen mode without any title bar. This even works with CMD and Powershell

alt + return also works in wsl-terminal.


Move Strat parameters out of darwin.js and into strategy.js

System information

Have I written custom code (as opposed to using zenbot vanilla): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04

Describe the feature request
Feature Request: Move the strategy parameter ranges from within darwin.js to inside the strategy.js files for each strategy.
Goal
I think it would be best to move the default ranges to the strategy files as I feel it would 1) clean up darwin.js 2) be a more natural place to find it for new users 3)easier to implement if you are creating a custom strat

Your right, I missed that one.


Add test and other QA-type functionality

Features discussed:

A way to unit test the acorn file itself. This is just asserting input/outputs of the file without actually launching anything
A way to cause integration tests to be ran which would launch an ephemeral instance of the acorn and a job to execute tests against that environment and handle the output
Some nice UX around linting/formatting the acorn file(s)

We also discussed about a lot of enhancements to this this in acorn hub, building workflows around these features

Discussed here: https://github.com/acorn-io/acorn/discussions/575

bad idea in general


Implement recovery behavior for LocalTrajectoryUploader

@wally-the-cartographer merge

Merge requested by authorized user cschuet. Merge queue now has a length of 1.


No cloud in Larastan constraints

Tests fail because we are low on version constraints.
This is too new https://github.com/laravel/framework/pull/53623

https://github.com/larastan/larastan/blob/b421a041af1a51e1b628476cb46826f7538a3055/.github/workflows/tests.yml#L69-L72

Yeah, I have no idea why it happens. Because it passes the first time, but when analyzed from outside of the directory it fails 🤯


Allow Creation of Internet Monitor

Associate specified VPCs with Internet Monitor.

Allow specification of Cloudwatch alarms based on thresholds set.


feature: add cpu period and quota for containers

Signed-off-by: Allen Sun<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
This adds --cpu-quota and --cpu-period to container options.
--cpu-period should be in range [1000,1000000], and --cpu-quota should be in [1000, ∞).
Ⅱ. Does this pull request fix one issue?

fixes https://github.com/alibaba/pouch/issues/1031
Ⅲ. Describe how you did it
none
Ⅳ. Describe how to verify it
none
Ⅴ. Special notes for reviews
none

Codecov Report

Merging #1067 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1067      +/-   ##
==========================================
+ Coverage   16.48%   16.48%   +<.01%
==========================================
  Files         158      159       +1
  Lines        8841     8783      -58
==========================================
- Hits         1457     1448       -9
+ Misses       7281     7231      -50
- Partials      103      104       +1

Impacted Files
Coverage Δ

daemon/mgr/spec.go
0% <ø> (ø)
:arrow_up:

pkg/opts/cpu.go
0% <0%> (ø)

daemon/mgr/spec_cgroup_cpu.go
0% <0%> (ø)
:arrow_up:

cli/common_flags.go
0% <0%> (ø)
:arrow_up:

cli/container.go
0% <0%> (ø)
:arrow_up:

pkg/kernel/kernel.go
72.72% <0%> (-7.28%)
:arrow_down:

daemon/mgr/spec_volume.go
0% <0%> (ø)
:arrow_up:

cli/cli.go
0% <0%> (ø)
:arrow_up:

daemon/mgr/container.go
5.21% <0%> (+0.1%)
:arrow_up:

... and 3 more

LGTM


[TFL] Handle TFLite models that return rank-0 tensors

Simple test models often return a single tensor<f32> type. However as tflite cannot distinguish rank-0
and rankless tensors so they appears a tensor<*xf32>. Create a pass that occurs after tflite-to-tosa
and shape inference that updates function return types, specifically the following input
func.func @main(%a : tensor<f32>, %b : tensor<f32>) -> tensor<*xf32> {
  %val = tfl.add(%a, %b) : tensor<*xf32>
  return %val : tensor<*xf32>
}

converts to
func.func @main(%a : tensor<f32>, %b : tensor<f32>) -> tensor<*xf32> {
  %val = tosa.add(%a, %b) : tensor<f32>
  %cast = tensor.cast %val : tensor<*xf32>
  return %cast : tensor<*xf32>
}

We can note that the return value is upcasted before returning. We can remove the cast and propagate the more
specific type to the function information.

Verified to be fixed in iree-samples


issues in test_docstring_parameters

The way that walk_packages is called in the docstring tests that got ported to scikit-learn means that the tests only work when called from a specific location. Also it misses all subpackages.
The right call should look like
                      for pckg in walk_packages(prefix='mne.',
                                                path=mne.__path__)

We currently call:
for importer, modname, ispkg in walk_packages(mne.__path__, prefix='mne.'):

And I think you're just suggesting to change the arg to a kwarg as path=mne.__path__, but path is the first argument so this shouldn't matter. I must be missing something...?

Huh, ok. I didn't look at the code, but the code @agramfort copied to sklearn looked very different. Your seems to be fine.

He probably copied over an old version long ago. Thanks for checking back in any case


NO MRG: Try skipping CircleCI builds

This is a test only PR. Do not merge it.
Tries to re-render with a development version of conda-smithy to test skipping CircleCI builds when they are not needed.
In addition, PR ( https://github.com/conda-forge/conda-smithy/pull/206 ) was used to enable a Travis CI setting to skip a build when .travis.yml is not present. Given this includes PR ( https://github.com/conda-forge/conda-smithy/pull/207 ), this removes .travis.yml as well. Thus this will also test if Travis CI builds can be skipped to.
cc @pelson

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Note the linter ran and now AppVeyor is running, but no other CIs are running. This makes perfect sense as this is a Windows only feedstock.

This has served its purpose for testing. Closing it out.


Fix idom.run uvicorn self.servers exception

This PR makes idom.run utilize the same code as uvicorn.run in order to prevent unexpected exceptions.
See https://github.com/encode/uvicorn/pull/1845 for details
Checklist
Please update this checklist as you complete each item:

[x] Tests have been included for all bug fixes or added functionality.
[ ] The changelog.rst has been updated with any significant changes.
[x] GitHub Issues which may be closed by this Pull Request have been linked.

The fix nox commit doesn't seem to have fixed nox.
On a tangent, we should probably set main as a protected branch to prevent direct commits.

Yeah, my bad. I deleted the old ReactPy releases not realizing that once I deleted the last one the name would become available again so was stressing trying to get a release out ASAP.

Also, main is protected. It's just that, as the owner of the repo I'm able to bypass those restrictions.

@rmorshea Do you agree with removing VictoryBar tests due to our module_from_template deprecation? That test is super flaky anyways.

If we remove the tests we should probably just remove the feature entirely.

I don't feel like this PR is appropriate to remove `module_from_template, so I backed those changes out.


Refactor: Replace scan diff hook options by new commands

Currently, the iac scan diff command handles three options to simplify git hooks: --pre-commit, --pre-push and --pre-receive. The objective of the main-iac-cli-hooks integration branch is to replace them with new iac scan subcommands, as described in this updated document.
This PR will refactor elements of the code in order to:

make the implementation of the subcommands (not in the scope of this PR) easier
factorize code

The duplicate code in precommit.py, prepush.py an prereceive.py can be ignored for now.

Sounds good to me except the files that you asked not to review.

I agree regarding the branch, I expected it to be needed but it isn't. I've rebased on main directly.
Unfortunately, I can't edit the target branch in the PR, so I've created a new one (#619) and will close this one once the other is merged on main.


[CT-919] dbt docs generate works in click

resolved by https://github.com/dbt-labs/dbt-core/pull/6681


More information on the notification

I wish I could see more information about the notification itself like a preview of the message posted. For now it's just showing the title, repo and type.
[Issue] Issue title
company/repo - updated X hours ago

@username commented:
Lorem ipsum

Sure we can take a look in to this. Depending on how many notifications you have, this may cause rate limiting issues.
Also from a UI stand point, I'd rather that you click "in to" the notifications to a new view which has further details.


Current project status?

There have been no commits for almost 2 years, and the installation instructions seem out of date, as reported in #49.  This leads me to wonder if the project is still maintained?  It seems that other forks are more active.  Thanks for any info you can shed.

As far as I'm concerned it is still maintained, but pretty much feature complete. The only main bug I'm concerned about is #46, and the tough thing to fix there is the migration path for older caches. Packaging and documentation could do with improvement (eg. #47). Apart from that my point of view is that glacier-cli is mainly feature complete, works as intended and so doesn't need to be "active".

OK great, thanks for the info and rapid reply!

my point of view is that glacier-cli is mainly feature complete

wouldn't it make sense then to bump the version number to 1.0.0 ? Current version at the moment is 0.1.0 which does not signal "feature complete"

wouldn't it make sense then to bump the version number to 1.0.0 ? Current version at the moment is 0.1.0 which does not signal "feature complete" :)

Sure. Maybe we should fully convert to Python 3 (shebangs etc), and also sort out CI in Travis or similar. There are (were?) some tests, but I'm not sure if they've rotted.

Maybe we should fully convert to Python 3 (shebangs etc)

changing shebangs is not necessary, if you install glacier-cli with pip install . the generated glacier-cli script automatically has a shebang with the python version you used to install it.
concerning the tests and travis I created  #79


Help request: Building on Windows 10 64 bit with MinGW-W64 getting undefined reference

Greetings,
Was wondering if I could get some help building on Windows 10 64 bit with MinGW-W64? Getting undefined reference. Not sure where the issue is, maybe something because of Windows 10?
versions:
go version go1.5.1 windows/amd64
gcc (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 5.2.0
instant client <IP_ADDRESS> 64 bit
Path has C:\app\instantclient_11_2_64;C:\app\Go\bin;C:\app\mingw64\bin
Flags:
CGO_CFLAGS=-IC:\app\instantclient_11_2_64\sdk\include
CGO_LDFLAG=-LC:\app\instantclient_11_2_64\sdk\lib\msvc\ -lstdc++ -loci
go install -v test
test/_third_party/github.com/rana/ora
# test/_third_party/github.com/rana/ora
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndBfile.cgo2.o:bndBfile.cgo2.c:(.text+0xc9): undefined reference to `OCIBindByPos'
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndBfile.cgo2.o:bndBfile.cgo2.c:(.text+0x150): undefined reference to `OCIDescriptorAlloc'
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndBfile.cgo2.o:bndBfile.cgo2.c:(.text+0x1ad): undefined reference to `OCIDescriptorFree'
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndBfile.cgo2.o:bndBfile.cgo2.c:(.text+0x24e): undefined reference to `OCILobFileSetName'
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndBinSlice.cgo2.o:bndBinSlice.cgo2.c:(.text+0x5b): undefined reference to `OCIBindArrayOfStruct'
C:\Users\myuser\AppData\Local\Temp\go-build291446222\test\_third_party\github.com\rana\ora\_obj\bndFloat32.cgo2.o:bndFloat32.cgo2.c:(.text+0x45): undefined reference to `OCINumberFromReal'
...

Any thoughts?
Appreciate any help provided.

Just a half-blind shot in the gray: OCIBindByPos2 is missing (which shall be used with 11.2).
These are defined for ora in version.h. Maybe the version macro defined there is bad or something?

Michael,
Would you try downloading and compiling with http://gopkg.in/rana/ora.v3
and see if there is a difference?
On Tue, Oct 13, 2015, 1:45 PM Tamás Gulácsi<EMAIL_ADDRESS>wrote:

Just a half-blind shot in the gray: OCIBindByPos2 is missing (which shall
be used with 11.2).
These are defined for ora in version.h. Maybe the version macro defined
there is bad or something?
—
Reply to this email directly or view it on GitHub
https://github.com/rana/ora/issues/40#issuecomment-147847236.

Thank you @rana for your help.
I tried with version 3 or ora and had the same issue. I also tried ora with the instant client <IP_ADDRESS> and same errors. I do not think it is an issue with the code. I also tried the go Oracle driver that is a translation of the Python cx_Oracle and it gave very similar errors.

Michael,
Would you uninstall mingw64, install (TDM GCC)[http://tdm-gcc.tdragon.net/download] and test?

Thought the same thing, same errors :/

Hello @MichaelS11, I think you might have misspelled your CGO_LDFLAGS variable, it should have a S in the end.  Fail on my part. Thank you very much!


Enable tabindex on grid

Enable tabindex property on the grid so that it is focusable. For this ensure that markup is generated as follows

      ...

      ...

  ....

Note that care is taken to assign tabindex=”0” only to one gridcell that will be focused when user navigates the grid by pressing tab keys. The grid itself and rows are having tabindex=”-1” to prevent user focus. It should be ensured that only one gridcell has tabindex=”0” whereas the rest of the gridcells must have tabindex=”-1”.
This should be generated as part of markup generated as output of grid_for method.

Closing as focus is now switched towards basic content accessibility instead of building rich widgets.


(PUP-4000) Make optional Struct value imply optional key

This commit changes the TypeCalculator so that a Struct with optional
values becomes assignable from a Struct where the keys corresponding
to those values are missing. It also changes the instance_of logic so
that a Hash missing such keys is considered an instance of the struct.

CLA signed by all contributors.

Sorry, back to the drawing board on this one.

Repoening this since I think the approach taken has some merits that I want to discuss.

I want to see the problem fixed clearly without any optimizations. We have tickets to later measure and optimize - lets to such things then.

I'd argue that the "optimization" is a natural part of this PR since it was made possible by the introduction of the is_optional_type? method. It also makes the instance_of_PStructType more similar to the assignable_PStructType since they use the same approach.

I don't like the introduction of is_optional_type - unnecessary specialized check. It is hard enough to read and reason about the type system methods without optimizations - if we can use straight forward code like:
(o.keys - h.keys).empty? && h.all? { |k,v| instance_of(v, o[k]) }

instead of over > 10 lines of code with conditionals and counters and stuff - then I very much prefer
the former.
I like the tests though :-)

Code simplified and tests retained :-)


Readying SRCFLib for wider use

Additions

@Result.collect, a generator-based result collector for multi-step tasks.
str(Result) to produce a tree of multi-step results.
State.created for tasks and plumbing that produce a new record or object.
NFS ACL and netgroup management, for member/sysadmin creation tasks.
The last few missing chunks of member/group creation and cancellation (emails coming soon).

Changes

ResultSet has been merged into Result: any results can now contain sub-results.
Tasks are now near-fully idempotent, avoiding non-idempotent plumbing unless necessary.
MySQL and PostgreSQL plumbing have been patched up and battle-tested.
Installation of psycopg2 now correctly references the non-binary version.
Namespaces no longer import their submodules, which should speed up imports of srcflib from other code.

Pending
(to come in follow-up PRs)

Emails to users/groups from tasks.
Single-function script generation.
Replacement of controllib job actions with srcflib calls.

Installation of psycopg2 now correctly references the non-binary version.

I gather psycopg2-binary is the recommended version.  Why are we avoiding it?


[Bug] firmware_update.available doesn't reset to null

The problem
Apologies in advance if this is not a bug. Before the update to <IP_ADDRESS>.388.1_0 became available for my router, the value in the available property was set to null. It changed as expected when the update became available but now, after the router is updated, the value is still stuck on that version. Is this the expected behavior?
For reference, this is how the current state looks like for the entity
auto_update: false
installed_version: <IP_ADDRESS>.388.1_0
in_progress: false
latest_version: <IP_ADDRESS>.388.1_0
release_summary: null
release_url: null
skipped_version: null
title: null
current: <IP_ADDRESS>.388.1_0
available: <IP_ADDRESS>.388.1_0
entity_picture: https://brands.home-assistant.io/_/asusrouter/icon.png
icon: mdi:update
friendly_name: RT-AX58U Firmware update
supported_features: 0

Your device model
RT-AX58U
Firmware type
Merlin
Firmware version
<IP_ADDRESS>.388.1_0
Integration version with the issue
0.14.3
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Core 2022.12.6
Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Hello,
Could you please check, whether reload of the integration will fix the problem? You can reload the integration from the HA integrations page - click on 3 dots - Reload

it didn't work. I also rebooted HA but nothing. But I assume this is not supposed to happen, right?

Nope, this should not be in such a way. I will try to reproduce this problem with my device in order to locate and fix the bug.

great thanks. Let me know if there's anything I can do to support the investigation

Hey. Does the state of your firmware_update entity set to false? Or is it true?
The false means in the frontend it shows this way

The attributes of the update entity are really supposed to look like this unless you remove and set up the integration from scratch.
So if the state is correct, then it is not a bug of the integration. This is the normal HA behaviour

The state looks correct, I guess there's no bug then 😅 thanks for taking the time to look into it 🙇

No problem (:


JS installation (from source) not working as documented?

Describe the bug
When installing the JS code from source a bin_parser executable isn't created in ./node_modules/.bin.
To Reproduce
Steps to reproduce the behavior:

Follow the installation instructions (here) from source, up to and including npm install .

Expected behavior
I expected then to be able to run ./node_modules/.bin/bin-parser ... as described in the next part of the documentation.
Desktop (please complete the following information):

OS: Ubuntu Desktop 18.04
Version: 0.0.20

Additional context
I followed the installation instructions but I am not a JS expert and have a vanilla npm install provided by Ubuntu 18.04.
Related to openjournals/joss-reviews#766.

It looks like npm behaves differently when installing from source. This may be a bug in npm, but I am not sure, I am not a JavaScript expert myself.
I added a line in the installation instructions to address this.


hashValue is the same on any two instances of Google_Proto_Any as long as the packed message type is the same

iOS: 16.x
Swift: 5.7
protoc: 3.21.9
SwiftProtobuf: 1.17.0
Should this unit test pass?
func testHashValuesAreNotEqualBetweenDifferentUnderlyingValues() {

    let myComponent1 = MyComponent.with { component in
        component.titles = ["Hello", "World"]
    }

    let myComponent2 = MyComponent.with { component in
        component.titles = ["Ipsum", " Lorem"]
    }

    let any1 = try! Google_Protobuf_Any(message: myComponent1)
    let any2 = try! Google_Protobuf_Any(message: myComponent2)

    XCTAssertNotEqual(any1.hashValue, any2.hashValue)
}

A hash is just that, a hash; nothing says two different message will always have a unique hash value.  But on top of that Google_Protobuf_Any is sorta unique. Since it has to deal with messages where the wrapped type might not be known at runtime (to reflect it back out, etc.), it special cases hash and only factors the typeURL in because otherwise there might be cases where the hash comes out different when the messages are actually equal. You can read about this in the implementation (that's the 1.17.0 release, since that's what you said you were using).

Should this unit test pass?

As Thomas pointed out, the only hard requirement for a hash implementation is that equal values must have equal hashes.  You cannot in general assume anything about the hash value of unequal values.  In addition, Any does not know anything useful about the value it contains.  For example, if an intermediate system is decoding and re-encoding some message, it may not actually have an implementation of the type stored in the Any, just the name of the type and the raw encoded data.  And it cannot compute a hash from the raw encoded data without understanding the meaning of that data (e.g., two messages may have the same integer value stored in different formats).
Do you have a reason why you believe those two messages should have different hashes?

A hash is just that, a hash; nothing says two different message will always have a unique hash value.
My expectation was that if I know the two values are the same, then they'd have the same hash value. I understand that there can be collisions and that it shouldn't be taken to mean things are the same or different generally. Thanks for the explanation both!

The Java equivalent seems to pass mind you...


[Payjoin] Address does not show up when accessing receive via the wallet page

When accessing the receive page via the wallet page; payjoin address is not created.

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Fixed on 0.4.0


MINOR: Assert ExecutionException details in testCreatePartitions

Due to the accidental duplication of case e: ExecutionException,
the verification code was not actually running.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mumrah We have -Xlint:unused enabled though (which is the supported version of the flag you mentioned). For what it's worth, I saw the warning when compiling with Scala 2.13, but I didn't check if 2.12 had the same warning.


433mhz dimmer

Hi I got a Nexa WMR-252 for christmas. It is a 433mhz reciver that you place in your ceiling light. I wonder how if someone have code for doing it with homebridge. So i can controll it with my phone and turn the light % up and down.
Pre thanks,
Anton

If it is 433mhz then it is pretty easy to control.  First you need to know what the codes that are for the remote buttons.  Every RF remote button has a unique code.  I am guessing your dinner has a code that the device seems and reduces the light down 10%.
I have a Raspberry setup with an RF receiver on it. A receiver cost less than $10.  I can point any RF remote at it and press a button. The raspberry then shows me the code.  Once I know the code then I use codesend that is part of an rfoutlets script to send them which is entered it my config file as an accessory.
If you want more details I can come back and comment to give you specifics on setting this up.  I didn't write any of the code by the way.  It is all done by people before us and works great.

I do aswell have a raspberry pi. I would love to get your way of doing it. I haven't jet been able to install it jet but hopefully soon. I just dont know how to get the dimming codes when i have installed it. The code for on and off have I been able to get for other devices so that should be no problems. But the dimming codes am i unsure if i will be able to get. I think that that's probably done by a normal "wall" dimmer.
Thanks for the help!

Did you get a RF receiver and transmitter yet?

@ehusar Yes I got a normal 433mhz transmitter and reciver but I haven't installed the wall dimmer jet.

Now have I finally gotten it installed. It works by using the Telldus-Live plugin!
Thanks for the help!


added competitive Programming various resources

Closes #238
added competitive programing site "Leet Code" and also added youtube resources "Love Babbar" and "CodeHelp-by Babbar"

I want to work on this please assign it to me


users should be able to log in, just missing backend endpoint

Attached a screenshot of your UI please.

this is after pressing sign in, since there's no way to create an account on my branch

The only errors showing now is due to the user not existing in the database since there is no user info stored yet and user creation hasn't been finished. I'm planning on getting pinia implemented before Friday, and if I have to I'll make a user manually and create a users table locally


Switch to GitHub Actions, implements #26

Codecov Report
Base: 95.44% // Head: 95.44% // No change to project coverage :thumbsup:

Coverage data is based on head (fc17367) compared to base (9543413).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #27   +/-   ##
=========================================
  Coverage     95.44%   95.44%
  Complexity      480      480
=========================================
  Files           135      135
  Lines          1054     1054
  Branches         32       32
=========================================
  Hits           1006     1006
  Misses           42       42
  Partials          6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add CmakeList.txt install

Thanks for the patch, but it is not right.
First, common and stacktrace are not the libraries we intend to be installed and used by 3rd party code. They're "convenience archives" that are linked into libtcmalloc, libtcmalloc_minimal etc.
Second, what is that thing about DESTINATION set to lib/gperftools ?

This is still not right. See above.
What kind of convenience w.r.t. system integration are you referring to? (I am genuinely curious)
Autotools-based ./configure && make works and enables all kinds of integrations. Or at least intended to.


⚠ Bofrost.lu has degraded performance

In 8c63849, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 994 ms

Resolved: Bofrost.lu performance has improved in 3c0a2df after 17 minutes.


Feature Request Debrid Integration

I hope you can add debrid in future update.

what is debrid?

no follow up, not clear