chore(ONYX-150): use myCollectionConnection to fetch artworks count within my collection

This PR resolves ONYX-150
Description
This PR updates the logic in the artists preview bottom sheet to use myCollectionConnection to fetch artworks count within my collection
https://github.com/artsy/eigen/assets/11945712/1b43440d-9b53-4350-9f44-298b5146cc12

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

use myCollectionConnection to fetch artworks count within my collection - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (use myCollectionConnection to fetch artworks count within my collection - mounir)

  Generated by :no_entry_sign: dangerJS against 186993c46e93b9b8b4d5fde61ac1badd62692bca


Resolve inconsistencies in using controlled gates & controlled operations

This PR tries to resolve the inconsistencies mentioned in #4172. Specifically,

Equality b/w controlled TOFFOLIs with different qubit ordering on controls, i.e. TOFFOLI(a,b,c).controlled_by(d)  == TOFFOLI(d,b,c).controlled_by(a)  (and other 3Q controlled gates like CCZ, CSWAP). To achieve this, we override the controlled method on CCX, CCZ etc. to return a ControlledGate with sub_gate = X in case of CCX s.t. TOFFOLI(a,b,c).controlled_by(d) == CCCX(a, b, d, c) == TOFFOLI(d,b,c).controlled_by(a) instead of CTOFFOLI
gate_operation.controlled_by now forwards the request to gate.controlled to first create a controlled gate and then apply it on qubits to create a ControlledOperation. This solves the original use case of adding specialized controls, requested in #2142, i.e. cirq.Z(q0).controlled_by(q1) == cirq.CZ(q1, q0).

Note, this is a breaking change because

gate_operation.controlled_by() can now return a cirq.GateOperation instead of cirq.ControlledOperation in cases where the underlying gates have specialized gate.controlled() implementations.

This also leads to a change in diagram of the controlled gates with specialized controlled implementations. For eg: Controlled S gate is now plotted as CZPowGate (@ --- @ ** 0.5) instead of ControlledOperation with Z ** 0.5 as subgate(@ ---- S)

op.controlled_by for 3Q gates like CCX, CCZ,  CSWAP will now return ControlledOperation with sub_operation = <underlying non-controlled gate>. Eg: CCCX (i.e. sub_gate = X) instead of CTOFFOLI (i.e. sub_gate = TOFFOLI) etc.

Thanks for the feedback. I found some more cases and have opened #4172 to discuss the various issues related to controlled gates & operations.
I'll mark this PR as draft for now till the discussion on the issue is resolved.

@balopat  This is ready for review. I'm open to suggestions for a better breaking change description in the PR.

Re: breaking change note - looks good, but I would specifically mention in the breaking changes the consequent change in QFT and quirk diagrams controlled operations. Some people depend on diagrams for their tests...

@balopat I've modified the PR description and added assert_controlled_and_controlled_by_identical as suggested. PTAL.
Also, do you want me to add 100% coverage across all Cirq gates for assert_controlled_and_controlled_by_identical in this PR itself? Or could it be a follow-up PR ?

@balopat  Ping, this is ready for re-review. PTAL.

@MichaelBroughton Can you please take a look at this?

@MichaelBroughton Bump!

I disagree that the testing should be specific to the gates and not in testing. controlling is a global sort of mutation, and so deserves a global sort of validation that it is consistent.

@Strilanc @MichaelBroughton Ping. This is ready for re-review.

Also added a fix for #4515 in this PR to avoid breaking the diagrams twice. See https://github.com/quantumlib/Cirq/pull/4529#issuecomment-926984204 for justification.
This PR is again ready for re-review


Twitter and Nintendo

Domain
t.co
Link
https://t.co/hhZd1fX5Tw
Version
0.0.0
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
Wrong redirect

Already reported in #733.


TabNavigator with single route: bad output range

function TestTab() {
    return <Text>text</Text>;
};

const App = TabNavigator({
    A: {screen: TestTab}
});

results in redbox: Bad output range

This already seems to be addressed in #65, apologies.


Fix websiteName data key

When I got set up with the “Single Content Type” example, the links were not rendering their names within the anchor tags.
The data that was pulled down from Contentful is this:
:id: 1g0qfuEDey2SYYYKEa8WMY
:websiteName: Github
:url: https://www.github.com

But the layout was referencing website_name, rather than websiteName. This PR fixes that both in the layout, as well as the mention of it in the README.

Hey @tysongach,
Thanks for the PR. Totally overlooked that!
Cheers

:tada: Thanks!


Nats\Exception: Subscription not found

Hello. I have some troubles with messages. After ~19 000 messages per second my worker is down with error:
Nats\Exception: Subscription not found: 0c6e8d428d94756d16b1a290a5f385bf in /home/vfeuerbach/v2/tmp/coordinator/vendor/repejota/nats/src/Nats/Exception.php:48
Stack trace:
#0 /home/vfeuerbach/v2/tmp/coordinator/vendor/repejota/nats/src/Nats/Connection.php(420): Nats\Exception::forSubscriptionNotFound('0c6e8d428d94756...')
#1 /home/vfeuerbach/v2/tmp/coordinator/vendor/repejota/nats/src/Nats/Connection.php(603): Nats\Connection->handleMSG('MSG _INBOX.596f...')
#2 /home/vfeuerbach/v2/tmp/coordinator/vendor/repejota/nats/src/Nats/Connection.php(497): Nats\Connection->wait(1)
#3 /home/vfeuerbach/v2/tmp/coordinator/run.php(68): Nats\Connection->request('queue', '{"corid":"djhfj...', Object(Closure))

And another strange thing.. If i make requests like in example i have 40-50ms lat. But if i make unsubscribe lat. is 1-5ms. Example here:
Here: 50ms. lat.
 $conn->request('queue', $msg, function ($response) {
// Processing...
});

Here: 5ms. lat.
 $conn->request('queue', $msg, function ($response) {
// Processing...
});
$conn->unsubscribe('queue');

Update: I make little load testing via ab (ApacheBench). I set params -n 2 and -c 2 (two requests in one time). And i have error:
Nats\Exception: Subscription not found: 546862e7d4954cb50a1a373fd3a2e5a2

That's interesting!
Taking a look 💪

Thans for your answer and time, i have a little data trace for you:
Here is responce data:
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3867}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3867}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3868}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3867}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3868}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3867}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3869}}"
string(101) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.387}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3871}}"
string(102) "{"type":"pong","status":20MSG _INBOX.5970418d5e883 84496f6969eb9a2e670752ce0f5bcfc1 102
{"type":"pong"

As you can see, PHP parse response incorrected.
Here second dump:
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3877}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3877}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3887}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3887}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3888}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3888}}"
string(102) "{"type":"pong","status":200,"message":{"instance":"office_local","process_timestamp":1500529037.3889}}"
string(102) "{"type":"pong","status":2070418d5ef56 76dad8a9ec8321ca2526d27705d44263 102
{"type":"pong","status":20"

And response damaged again :(


IntervalQueryRulePrefix Source is wrong. Needs "prefix" instead of "query"

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[x] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
{
    "prefix": {
         "prefix": "horst"
    }
}

Please describe the actual behavior
{
    "prefix": {
         "query": "horst"
    }
}

Results in:
[{"root_cause":null,"type":"x_content_parse_exception","reason":"[1:551] [prefix] unknown field [query]"}]]
Any steps to reproduce the behavior?
elastic.NewIntervalQueryRulePrefix("horst").Source()

Thanks for reporting. Will be fixed in the next release.


Registry Viewer: Ensure country codes are capitalized

/kind bug

Which area this bug is related to?

/area registry
What versions of software are you using?
Operating System:
iOS
Go Pkg Version:
N/A
Bug Summary
Describe the bug:

Telemetry events coming from Safari are not sending over a properly formatted country code and as a result, Woopra does not recognize the country information.  For example,  region ca should be CA  - see ISO 3166 alpha-2 codes for reference
To Reproduce:

Login to woopra to see these events
Expected behavior

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

Additional context

Any workaround?

Suggestion on how to fix the bug

this doesn't seem to be a problem anymore as I don't see anymore instances of lower case country codes.


Fix signal kyco/core.shutdown

Fix signal shutdown in core.napps.py
Add method _execute_loop to run execute method until the signal
'kyco/core.shutdown' is received.
Remove unused comments.
Fix #101

After send a shutdown some times the thread can't stop. I will investigate it.

@raphaelmcobe , I discovered the error, the package kyco-core-napps has a older implementation using signals with Classes and now we have a specific string to represent a signal. If you running locally all tests pass.


Misspelling of 'Build.ArtifactStagingDirectory'

In the beginning of the article there is the following part:

In YAML pipelines, you can reference predefined variables as environment variables. For example, the variable Build.ArtfactStagingDirectory becomes the variable BUILD_ARTIFACTSTAGINGDIRECTORY.

"Build.ArtfactStagingDirectory" should be changed to "Build.ArtifactStagingDirectory"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 11d3469c-83c2-c2f6-41d0-08f82c330bbc
Version Independent ID: a373c48d-6395-3002-d2d8-bbc1fea2e48e
Content: Predefined variables - Azure Pipelines
Content Source: docs/pipelines/build/variables.md
Product: devops
Technology: devops-cicd-build
GitHub Login: @juliakm
Microsoft Alias: jukullam

I provided a PR: https://github.com/MicrosoftDocs/azure-devops-docs/pull/10763

@Loreno10 Thanks!

Fixed with PR.


Added user and group checks. Auto create socket dir.

Parsec must be run as user parsec and parsec must be member of group parsec-client.
This is disabled if feature testing is specified.
Also auto created /tmp/parsec if it does not already exist with ownership set to user parsec and group parsec_clients. User parsec must be a member of parsec_clients in order for it to be able to change group ownership to it
Signed-off-by: Samuel Bailey<EMAIL_ADDRESS>

I've tested this on my machine with a parsec user. If run as a user other than parsec, it complains about running as incorrect user. If run as parsec but parsec_clients group does not exist, throws error about not finding parsec_clients. If run as parsec and parsec_clients exists but parsec is not a member, throws error about parsec not being a member of parsec_clients. If run as parsec and parsec is a member of parsec_clients, it will create /tmp/parsec if required.
If I add my local user to parsec_clients and run Parsec as parsec, my local user can successfully run cargo test normal_tests. If my local user is not a member of parsec_clients, it fails.

(This isn't going to pass our stock CI as it won't be using the testing feature or the parsec user with parsec_clients group)

I've tested this on my machine with a parsec user. If run as a user other than parsec, it complains about running as incorrect user. If run as parsec but parsec_clients group does not exist, throws error about not finding parsec_clients. If run as parsec and parsec_clients exists but parsec is not a member, throws error about parsec not being a member of parsec_clients. If run as parsec and parsec is a member of parsec_clients, it will create /tmp/parsec if required.
If I add my local user to parsec_clients and run Parsec as parsec, my local user can successfully run cargo test normal_tests. If my local user is not a member of parsec_clients, it fails.

I really like having the ability to do this! It'll make life much easier for admins... but, at the same time, I'd also like to give them an option - at the moment the only way to not have this run is by using the testing feature and that's clearly undesirable.
I was thinking you could add a new section in the config file, something like
[fs-permissions]
service-user = "parsec"
clients-group = "parsec-clients"

If the section exists, the feature is enabled, and it will be enabled in our example config file. We could add these fields (and a boolean flag tracking if it's enabled) in the GlobalConfig, so that other components can use it - Listener, maybe even OnDiskManager.
Thoughts?

If the section exists, the feature is enabled, and it will be enabled in our example config file. We could add these fields (and a boolean flag tracking if it's enabled) in the GlobalConfig, so that other components can use it - Listener, maybe even OnDiskManager.

That sounds like a good idea. It makes it easier for admins to enable or disable this feature, and they can also specify their own Parsec user and group.

I agree with having a separate fs-permissions feature for this but not sure with letting the possibility of changing the name of owner and group. These should ideally be hardcoded so that clients can check it as well.

I agree with having a separate fs-permissions feature for this but not sure with letting the possibility of changing the name of owner and group. These should ideally be hardcoded so that clients can check it as well.

Makes sense. I really wish we could make this synchronisation problem disappear somehow - both around the paths and the usernames/groups

I agree with having a separate fs-permissions feature for this but not sure with letting the possibility of changing the name of owner and group. These should ideally be hardcoded so that clients can check it as well.

So would this mean we have a [fs-permissions] section with a single bool config like strict-user-and-groups without the service-user or clients-group, allowing the admin to turn on or off the security feature without changing names?

@ionut-arm If this feature is meant to be activated by default, do you think we could have it at build time? Like the one in the Rust client?

@ionut-arm If this feature is meant to be activated by default, do you think we could have it at build time? Like the one in the Rust client?

Yeah, I think if we don't want to make any of the values configurable, just compiling it in (or not) makes sense

Isn't this what's already there? The compile time option testing will disable the check, which is enabled by default. (perhaps the name could be changed to parsec-user-and-clients group)

Isn't this what's already there? The compile time option testing will disable the check, which is enabled by default. (perhaps the name could be changed to parsec-user-and-clients group)

Yep, that makes sense, just renaming it should be fine

I've changed the feature to parsec-user-and-clients-group which is enabled as a default feature, instead of using the testing feature which would disable the extra security checks.

I guess on the CI we do not have to active the feature. But we should at some point add tests for a secure deployment where all checks are in place.

I guess on the CI we do not have to active the feature. But we should at some point add tests for a secure deployment where all checks are in place.

I've modified the CI script to add --no-default-features which will remove parsec-user-and-clients-group. The ability to disable a single feature would be nice, but I'm not sure it'll happen any time soon...!

For the problem you described, it might be better to do something similar as in the client: have a no-fs-permission-check feature, disabled by default. You can check in the code if the feature is not there. That way it would be easier to selectively remove the checks 👍

There seems to have been two Travis Builds triggered by this PR. Weird.

With this PR, the parsec and parsec-clients user/group will be mandatory to even run Parsec. This will have to be documented clearly in our book.
Also I am thinking when we will have our first authenticators. The 750 permissions will then have to be 755, no longer needing the parsec-clients group. We would probably also prevent direct/none authentication.
By then this code will have to be modified to comply with that. Should we then stop at checking that the current user is parsec and the the permissions are 750?

With this PR, the parsec and parsec-clients user/group will be mandatory to even run Parsec. This will have to be documented clearly in our book.
Also I am thinking when we will have our first authenticators. The 750 permissions will then have to be 755, no longer needing the parsec-clients group. We would probably also prevent direct/none authentication.
By then this code will have to be modified to comply with that. Should we then stop at checking that the current user is parsec and the the permissions are 750?

Should we just get it into that state now instead of coming up with a stopgap that will definitely be changed at somepoint?

With this PR, the parsec and parsec-clients user/group will be mandatory to even run Parsec. This will have to be documented clearly in our book.
Also I am thinking when we will have our first authenticators. The 750 permissions will then have to be 755, no longer needing the parsec-clients group. We would probably also prevent direct/none authentication.
By then this code will have to be modified to comply with that. Should we then stop at checking that the current user is parsec and the the permissions are 750?

I think some deployments might want to use this setup, even if we don't really recommend it. But maybe we should force them not to anyway - to at least use the peer credential authentication. That might be the "least secure" option we offer, converting the direct authentication.
none authentication is still needed for service discovery operations.

Should we just get it into that state now instead of coming up with a stopgap that will definitely be changed at somepoint?

Not really, because right now we need the parsec-clients group to do the "authentication" for us.

Should we just get it into that state now instead of coming up with a stopgap that will definitely be changed at somepoint?

My view is that yes we should. Only check that the current user is parsec and set the socket dir to be owned by parsec and 0o755. Deployments without authentication would still have to do the whole socket directory creation themselves: I don't think they can do it once after Parsec is running.

Oops sorry for closing 😅
I agree with your points and I think this is fine to go with this now. My main concern is that there will be some changes needed in this code if we remove the parsec-clients requirement when the peer credential authentication is used.


Kyogre tunnel quest

in the kyogre quest:
when entering the 3th tunnel the tunnel is half build/half natural with caves in it.
this might be confusing for people who do the quest first time and accidentally

go in it.

Going to assume this was fixed, since it is several months old.


More GitHub Actions

Adding more GitHub Actions for linting.

mypy needed to be removed b/c needed to have the whole project installed. Will follow-up in a separate PR.

Resolves #14


Windows dll binary

Is there a pre-compiled jar for windows? I fiddling with make files but failed to generate one.

It's OS X only. As stated in the readme, someone would need to work on the build script to add support for other platforms.


Normalize path input

Trying to fix #458 I've realised that we have problems with Windows vs POSIX paths as we had long ago in the JS Toolkit.
The root cause of #458 is that gulp needs glob expressions (as the ones passed to gulp.src) to be in POSIX format. But the globs are made based on the options received by registerTasks, which are provided by the user. So, if the user passes paths in Windows format, we need to convert them to POSIX before making the globs.
Also, the files liferay-theme.json and liferay-plugin.json have paths inside them that may need to be normalized too.
In the JS Toolkit I decided that every path in config files should be in POSIX format (even in Windows). This is because that way projects may be multiplatform and the same source can be used for Windows and POSIX systems. Then, the internal machinery of the JS Toolkit takes care of converting from POSIX to Windows when needed.
I would like to do the same in Themes Toolkit, but it may break compatibility with already existing projects. We may argue that because we are going to release a new major version it doesn't matter, but there's another possibility that we may use, namely that of using native paths in registerTasks and taking care to convert them to POSIX when needed (i.e: when running on Windows).
Still, as I said I prefer to always use POSIX paths in configuration to be multiplatform.
Opinions?

In the JS Toolkit I decided that every path in config files should be in POSIX format (even in Windows). This is because that way projects may be multiplatform and the same source can be used for Windows and POSIX systems. Then, the internal machinery of the JS Toolkit takes care of converting from POSIX to Windows when needed.

I think this is pretty much the only way to do it, really. Especially in places where paths meet globs (and \ is used to escape). So, for consistency, even in the absence of globs, I think using POSIX paths for config is the way to go.

At least in the case of the liferay-theme.json, I don't think the path format is a big issue on Windows (which I test one :-) ) because the path is automatically added for you based on the init tasks. If you need to change it, you can just re-run the init task. I'm not sure about liferay-plugin.json.

@mwilliams2014 liferay-plugin.json is the same as liferay-theme.json but for layouts. So, same rules should apply.


Added Whats new for CUDOS

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please name the file according to standards (i.e. CHANGELOG.md)


implement std::default::Default for execution config

Which issue does this PR close?
Closes #.
Rationale for this change
since most of the options are reasonable defaults we can have trait Default implemented
What changes are included in this PR?

Are there any user-facing changes?

Codecov Report

Merging #570 (9dee39b) into master (51e5445) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #570   +/-   ##
=======================================
  Coverage   76.02%   76.02%
=======================================
  Files         156      156
  Lines       27063    27065    +2
=======================================
+ Hits        20575    20577    +2
  Misses       6488     6488

Impacted Files
Coverage Δ

datafusion/src/execution/context.rs
92.05% <100.00%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


No Notification on IOS Screen from Pushover

Hey Joshua,
your bot works perfeclty fine! I only have one issue. I don't get any notifications on the IOS Screen when I get a Pushover message. The message appears in the pushover app but doesn't on the home screen. Do you have any idea what the problem is?
Greetings

Hey! The pushover API supports multiple priorities, see https://pushover.net/api. You can always change them in the code to adjust it to your own liking. Right now, the only message pushed with high priority is if a free appointment has been identified. Hope this helps.

Hey! The pushover API supports multiple priorities, see https://pushover.net/api. You can always change them in the code to adjust it to your own liking. Right now, the only message pushed with high priority is if a free appointment has been identified. Hope this helps.


fix: Use coalesce when desired default value is not null

First of all, thanks for the work on this module. We've been using it for a couple of years now ❤
Description
Use coalesce when the desired default value of an expression is not null.
Motivation and Context

We maintain an opinionated wrapper module around this one where we used to install the EKS add-ons using their separate Terraform resources but eventually switched to doing it through this module since it supports it.
On our module, we would like to support providing add-on versions while still keeping the default behavior from this module of retrieving the matching version from a data_source if no version is provided.
This would be a snippet from our module.
variable "coredns_version" {
  type    = string
  default = null
}

variable "kube_proxy_version" {
  type    = string
  default = null
}

...
  cluster_addons = {
    coredns = {
      addon_version = var.coredns_version
    }
    kube-proxy = {
      addon_version = var.kube_proxy_version
    }
...

But since null is a valid expression when using the try function; try(each.value.addon_version, data.aws_eks_addon_version.this[each.key].version) is returning null instead of defaulting to use the version from the data_source as we would like.
Using coalesce instead should fix this.
> try(null, "v1.26.2-eksbuild.1")
null
> coalesce(null, "v1.26.2-eksbuild.1")
"v1.26.2-eksbuild.1"

As a workaround, we could re-implement the same logic for retrieving add-on versions from data sources in our wrapper module or maybe use dynamic blocks, but if you don't see anything wrong with this change it would simplify our module a bit.
Breaking Changes
This might be be considered a breaking change since it would change the behavior for end users that are explicitly passing null as input variable to the module, but it probably won't affect many users.
How Has This Been Tested?
After an upgrade from EKS 1.25 to EKS 1.26 with this input:
  cluster_addons = {
    kube-proxy = {
      addon_version = var.kube_proxy_version <-- null
    }
}

plan with try:
No changes. Your infrastructure matches the configuration

plan with coalesce:
Terraform will perform the following actions:

  # module.cluster.module.eks.aws_eks_addon.this["kube-proxy"] will be updated in-place
  ~ resource "aws_eks_addon" "this" {
      ~ addon_version     = "v1.25.6-eksbuild.2" -> "v1.26.2-eksbuild.1"
        id                = "test:kube-proxy"
        tags              = {}
        # (7 unchanged attributes hidden)

      + timeouts {}
    }

I hope I've made myself clear 😛. Let me know your thoughts and if you are OK with this change. And if you wish I can extend it to all try occurrences where null is not the desired default value.

This PR is included in version 19.15.4 :tada:


Support docker --context

Could you support the docker --context flag?
It's used like this, to take the example from the Docker docs:
docker --context production container ls

I suppose you'd need to change something around here:
  -*)
    echo "Unknown option: $1"
    exit_with_usage
    ;;
  *)

and here:
# check if compose v2 is available
if docker compose >/dev/null 2>&1; then
  COMPOSE_COMMAND="docker compose"
elif docker-compose >/dev/null 2>&1; then
  COMPOSE_COMMAND="docker-compose"
else
  echo "docker compose or docker-compose is required"
  exit 1
fi

Shell scripting is not at all my strength so I'm hesitant to dive in myself.

I decided not to implement all possible docker and docker compose flags if they can be provided via an environment variable to keep this tool simple, would this work for your use case?
env DOCKER_CONTEXT=production docker rollout

(See Docker profiles https://github.com/Wowu/docker-rollout/issues/5#issuecomment-1501538614  and remote deployment https://github.com/Wowu/docker-rollout/issues/6#issuecomment-1503198297)

Yes this works OK.
I had thought you could just pass arbitrary additional flags to docker.
i.e.
docker --xyz rollout passes xyz to docker
And docker rollout --xyz passes xyz to compose

Actually, it sounds like a good idea to pass unknown flags, but there's a catch: the script uses docker and docker compose, and those have different flags available.

Not sure I understand the problem; you could pass them like I described in the last comment? Is there something wrong with my suggestion?
Obviously the decision of how to spend your time is entirely yours. Thanks for the tool :)

Oh sorry, I didn't get your idea at first. Would be great, but I'm not sure if I'm able to access flags passed to docker commands, because the docker plugin integration is pretty basic. Will check

It works as I expected, thank you for the suggestion. Arguments before rollout are now passed to docker commands, so --context now works.
Released as https://github.com/Wowu/docker-rollout/releases/tag/v0.6


RCTViewManager   RCTView

Same issue please anyone help

Same issue here, too

But works when pulling from master - so possibly related to https://github.com/alinz/react-native-webview-bridge/pull/217 ?

The issue is still here. I am using
RN: 0.42.0
react-native-webview-bridge: 0.33.0
Can anyone help out?
Thank you so much.

the same issue.
with using
"react-native": "0.40.0",
"react-native-webview-bridge": "^0.33.0"

You can see here to solve this issue.
https://github.com/alinz/react-native-webview-bridge/issues/219

If your react-native version more than 0.40,please to change the header file like this
#import "RCTWebViewBridge.h"
#import <UIKit/UIKit.h>
#import <React/RCTAutoInsetsProtocol.h>
#import <React/RCTConvert.h>
#import <React/RCTEventDispatcher.h>
#import <React/RCTLog.h>
#import <React/RCTUtils.h>
#import <React/RCTView.h>
#import <React/UIView+React.h>
#import <objc/runtime.h>

Nobody can give a correct answer?

Same problem

The functionality has already added into RN core module.
So, the author maybe doesn't maintain the repo anymore...
Look at: https://github.com/alinz/react-native-webview-bridge/issues/206

@kingfun2015 That doesn't work. I suspect it's building RCTView etc. into the library and conflicting. Should be dynamically linked? That's a project setting right?

I have a fix, will post diff later. Basically just move the .h includes from the .m into the .h and change to <> not ""

Fix is in PR #230 if anybody needs it


ConnectNamedPipe fails

Sometimes this function fails although there is a pipe created.
It seems that the CreateNamedPipe function can report that the connection is complete when it's not ready yet.
Changing the code by checking on the 535 (ERROR_PIPE_CONNECTED) seems to overcome this issue.
//failed to connect client pipe
if ((success != 1) && (Marshal.GetLastWin32Error() != 535))
{
    break;
}

@synhershko You have fixed this, so I think you can close it: https://github.com/synhershko/NAppUpdate/blob/bc22bb4909ce5c9fb7ef0c13fdacccf4999b2d24/src/NAppUpdate.Framework/Utils/NauIpc.cs#L134

Nevermind, might need to be fixed here too: https://github.com/synhershko/NAppUpdate/blob/bc22bb4909ce5c9fb7ef0c13fdacccf4999b2d24/src/NAppUpdate.Framework/Utils/NauIpc.cs#L93

Closing as duplicate of #54


Support for -d all in --machine mode and --use-application-binary.

Dream wants to try running the same app on multiple devices.  -d all was created for this use case.
This workflow is neither compatible with IDE tooling nor g3 tooling.
IDE uses --machine.  g3 tooling builds the binary with a separate toolchain and uses --use-application-binary to specify which artifact to deploy.

Related: https://github.com/flutter/flutter/issues/16145
There were some discussions around this, and we concluded it may be better for the IDEs to own the multiple-debug sessions (eg. they just run multiple flutter run --machines, one for each device). The way the user can see the multiple sessions, switch between them for stepping, etc.. otherwise I think we'd end up with a single list of isolates in the IDE that actually represent isolates from multiple devices all mushed together (for example).

FWIW, what I mentioned above works now in VS Code (with some rough edges) - see https://github.com/flutter/flutter/wiki/Multi-device-debugging-in-VS-Code. I don't know if that addresses the original requirement, though.

This is not currently planned, so I'm going to tentatively close this if we're not sure anyone wants it.


New Ubuntu logo

Maybe it's not really a useful pull request but i would like to know what do you think about the new Ubuntu ascii from neofetch master

There shouldn't be any build errors.

I like the new logo, and it makes sense to use it, as it resembles the new ubuntu logo. But can we keep the old logo as ubuntu_old around? Similar to what for example fedora has.

Oh yeah sure! i can bring back the old logo

Let me push the changes.

Great, thank you!

I just realized it has some formatting errors..

let me correct them


Check if deep-extend and _.merge are equivalent

Source code uses both deep-extend and _.merge. Prefer using lodash if possible.

This was fixed with #20.


⚠ Bofrost.be has degraded performance

In d21cbfe, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1399 ms

Resolved: Bofrost.be performance has improved in 87eb6ea.


IGNITE-17082: Rename ignite-config.json to ignite-config.hocon

Also, related todo's are removed. The reason why I decided to
keep using text/plain for HOCON configuration is that
tooling (swagger-codegen, for example) do not support this
media type that is suggested to use for HOCON
(application/hocon). The reason of weak support is that
application/hocon is not the official MIME type.
We have integration tests guaranties that the returned
String can be deserialized as HOCON config.

https://issues.apache.org/jira/browse/IGNITE-17082


CommandAPI Failing to Load on Paper

CommandAPI version
9.3.0
Minecraft version
1.20.4
Are you shading the CommandAPI?
Yes
What I did
I installed CommandAPI and tried to register some basic commands through the API.
What actually happened
I got this error upon loading up the server.
[22:29:49 ERROR]: Caught previously unhandled exception :
[22:29:49 ERROR]: Paper Async Command Builder Thread Pool - 0
java.lang.IllegalStateException: zip file closed
        at java.util.zip.ZipFile.ensureOpen(ZipFile.java:831) ~[?:?]
        at java.util.zip.ZipFile.getEntry(ZipFile.java:330) ~[?:?]
        at java.util.jar.JarFile.getEntry(JarFile.java:518) ~[?:?]
        at java.util.jar.JarFile.getJarEntry(JarFile.java:473) ~[?:?]
        at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:209) ~[paper-api-1.20.4-R0.1-SNAPSHOT.jar:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:587) ~[?:?]
        at org.bukkit.plugin.java.PluginClassLoader.loadClass0(PluginClassLoader.java:169) ~[paper-api-1.20.4-R0.1-SNAPSHOT.jar:?]
        at org.bukkit.plugin.java.PluginClassLoader.loadClass(PluginClassLoader.java:164) ~[paper-api-1.20.4-R0.1-SNAPSHOT.jar:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:520) ~[?:?]
        at dev.jorel.commandapi.CommandAPIBukkit.wrapCommandSender(CommandAPIBukkit.java:410) ~[RPGProject.jar:?]
        at dev.jorel.commandapi.nms.NMS_Common.getCommandSenderFromCommandSource(NMS_Common.java:380) ~[RPGProject.jar:?]
        at dev.jorel.commandapi.nms.NMS_Common.getCommandSenderFromCommandSource(NMS_Common.java:94) ~[RPGProject.jar:?]
        at dev.jorel.commandapi.CommandAPIHandler.lambda$generatePermissions$1(CommandAPIHandler.java:362) ~[RPGProject.jar:?]
        at com.mojang.brigadier.tree.CommandNode.canUse(CommandNode.java:79) ~[paper-1.20.4.jar:git-Paper-385]
        at net.minecraft.commands.Commands.fillUsableCommands(Commands.java:536) ~[?:?]
        at net.minecraft.commands.Commands.sendAsync(Commands.java:488) ~[?:?]
        at net.minecraft.commands.Commands.lambda$sendCommands$6(Commands.java:467) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]

I am currently running paper, and this appears to be a compatibility issue between CommandAPI and Paper.
What should have happened
The commands should have been properly registered and there should not have been an error.
Server logs and CommandAPI config
No response
Other
No response

Are you able to provide the full server log using a site like https://paste.gg/? Just running a Paper server while registering commands doesn't have anything coming up for me. The stack trace indicates that Java failed to load the BukkitPlayer class when running this line in the CommandAPI, which seems odd without any context.
From the stack trace, it looks like the server is responding to a player joining. The code that was being run sends a packet that tells a player which commands are available for them to use. So, it seems that the steps needed to reproduce this error include a player joining the server. Do you have more specific steps for making this error happen?
Do you have any other plugins on the server?

Yes, we did discuss this briefly, over in Discord here. Turns out, I was confusing this issue with #494, and they're not remotely related to one another.
Let's start from the beginning @InTheRiches, with a bit more info. As @willkroboth mentioned above, would it be possible to acquire the full server log (as opposed to just this section of the log with the error message)? A full server log may help us diagnose the issue further, because so far we've been unable to reproduce this issue in any of our test environments against any other versions of Paper, and this issue hasn't been reported by other Paper users (so it's likely something weird going on with your setup?).


[✨ FEATURE]:  Automate issue labelling process

Feature Description 📝
I'm considering automating the process of labeling issues. With this setup, when an issue is created, a GitHub Actions bot will promptly apply appropriate labels, thus saving valuable time for maintainers.
Motivation 🌟
Every developer desires to automate their routine tasks, saving significant time. Additionally, labeling every issue in a repository can become quite monotonous. 🥲
Expected Behavior 🤔
DO WATCH TILL END
Screencast from 26-04-24 04:12:54 AM IST.webm
Additional Information ℹ
will be pulling an all nighter to code this 😅

@dakshsinghrathore Can you close this when you get a chance?


Change open pose

Hi, I would like to request to be able to use other posture estimation libraries that are also available for commercial use, such as tf-pose-estimation and posenet.
Specifically, I need tf-pose-estimation and posenet to be converted to json in openpose format.
Thank you in advance.

Hi,
Can this be changed to allow the use of other posture estimation libraries that are commercially available, such as tf-pose-estimation or PoseNet? This would require invoking tf-pose-estimation or PoseNet and converting its output to JSON in the same format as Openpose.
Thanks.


New version: upgraded dependencies, resolved indirect vulnerabilities and changed the linter

:tada: This PR is included in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Confiure a page-section tag to auto do the site outline like course intro tag

Course intro is up for getting the treatment of DDD and should remain part of core, but it brings up an interesting idea as we revisit this -- is it really that different from the landing pages of HAX.psu as far as page-section based content.
It has a title, a heading, an icon, an image, and it takes up the whole screen
hero content via page-section

full provides the whole screen size
image support for background
slot support for header / additional text
currently no visual support in DDD for icon but not end of the world to add one in

This would allow us to start putting a series of page-section tags on a page that uses the blank theme
#1907 #1917 #1918

irrelevant now as we've progressed


Update requirements.txt

Raising prompt-toolkit version 3.0.30, prompt-toolkit==3.0.29 is not compatible with other deps

Thank you for your contribution


mia_hand_ros_pkgs: 1.0.0-14 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mia_hand_ros_pkgs to 1.0.0-14:

upstream repository: https://bitbucket.org/prensiliasrl/mia_hand_ros_pkgs.git
release repository: https://github.com/Prensilia-srl/mia_hand_ros_pkgs-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: 1.0.0-13

mia_hand_bringup
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_description
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* Added license file in the repo and license text as header of each file.
* Added licence file and licence text as header of each file.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_driver
* Changed #include directive for libserial.
* 1.0.0
* Updated CHANGELOG files.
* Limited max motor PWM in speed command.
* Created libserial IMPORTED_TARGET.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* Added license text at the beginning of each file.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_gazebo
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* Added license file in the repo and license text as header of each file.
* Added licence file and licence text as header of each file.
* 1.0.0
* Merge branch 'master' of https://bitbucket.org/prensiliasrl/mia_hand_ros_pkgs
* Added ChangeLog files of each pkg.
* CMakeLists.txt edited the name of the xml file to install.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, Francesca Cini, frcini

mia_hand_moveit_config
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_msgs
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_ros_control
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* Added license file in the repo and license text as header of each file.
* Added licence file and licence text as header of each file.
* 1.0.0
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

mia_hand_ros_pkgs
* 1.0.0
* Updated CHANGELOG files.
* Updated CHANGELOG files.
* Added srv dependency to mia_hand_driver and joint_state_interface to mmia_hand_description. Added wiki url links.
* 1.0.0
* Adjusted Cmake file of mia_hand_ros_pkgs metapkg for release.
* Added ChangeLog files of each pkg.
* Initial commit.
* Fix package xml files.
* Initial commit.
* Contributors: Andrea Burani, frcini

Hi @andreabu, this is using the same version as the previous release (1.0.0). Perhaps you want to bump the patch version?

Hi Audrow,
the package version should remain the same as previous release, since I did not add or modify any of the functionalities of the package.
The reason why I'm releasing again the package is, in fact, that I'm trying to fix a build error that Jenkins is notifying to me. Basically, in the package I'm exploiting an external library (libserial), which I'm linking against the new library I generate. When I built the package locally, and during pre-release tests, everything compiled without errors. However, after the first release, I started to receive Jenkins build failure notifications via e-mail. The reason for the failure was that libserial header files could not be found through #include directives.
Since this error is happening only on Jenkins, every time I try to fix it I have to release again the package, opening a new pull-request. Till now I haven't figured out a better method for proceeding. If you had any suggestion, it would be welcome. If you also think it is better to bump anyways the version, then I'll do it.
Best regards,
Andrea

Since this error is happening only on Jenkins, every time I try to fix it I have to release again the package, opening a new pull-request. Till now I haven't figured out a better method for proceeding. If you had any suggestion, it would be welcome. If you also think it is better to bump anyways the version, then I'll do it.

It's more usual to bump the patch version.
If the package was never built correctly it doesn't matter much though.
You can also share the build errors here, maybe we can help you undestand what's wrong.


import/no-named-as-default-member rule became less useful in 2.30.0

In 2.30.0 the following code gives a lot of warnings and suggests to import string, number, etc. instead of using the properties from the default import z.

In this case, I think it is clearer to continue prefixing the code with z and not using imported generic words like "string", "number" etc.
I'm not sure why the rule needed to be changed like this. The zod library is likely not the only case where such prefixing makes sense.
Would you be open to give an option to disable this behavior and only create warnings/errors for actual import statements?
I disabled the rule for now.

What happens if you import * as z instead?


testing the model

Hi I have cloned the repository and I want to test it in my computer with my images and video. How should I do it?

Just follow the procedures. Setup conda environment and build the system. Then use the inference command line. Make sure you download the pre-trained models before running the inference command. Create a directory inside the root and keep your images there.

Where can I download the pre-training model?

+1 Where can I find the pre-trained model?


Method-based tag construction with attribute parameters

This replaces the AttrPair method of tag construction of attr := value with having attributes be regular parameters of the apply method of the tag. This allows for significantly improved IDE support with code completion for supported attributes and fewer implicits involved, and opens up the path to improved typing for event handlers and more aggressive inlining.
This PR brings in the new tag construction API and deprecates the old one. AttrPairs will still have a significant role in Slinky for cases such as ExternalComponentWithAttributes and dynamic attributes (can be handled with .withDynamicAttributes(attrPairs*)).

On hold for now. This ends up increasing bundle sizes because undefined properties are not eliminated. The way to solve this would be to use macros, but those aren't supported for named parameters.


Bit drops while audio streaming

We are facing skipping(bit drop) issue in audio streaming and this issue is being produced in several devices. Below are few of them:
Nexus 5x
Nexus 5
Nexus 6p
Moto G5 plus
Samsung J6

What base are you using?
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/tree/master/rtplibrary/src/main/java/com/pedro/rtplibrary/base
Also share me audio configuration used in prepareAudio method.
Any2way you can try change audio configuration directly in this class:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/encoder/src/main/java/com/pedro/encoder/input/audio/MicrophoneManager.java


Add Windows support

All tests pass now on Windows for all sub-projects.  I also added instructions on getting this working on Windows.
There was only an issue with paths in the C compiler (resulting in strings with incorrect escapes e.g. "examples\attackers").  I kept the fix as simple as possible, there are more comprehensive solutions involving std::path::{Path, components, MAIN_SEPARATOR}.
If ease of use and on-boarding is a goal (maybe not, at this early stage), you may consider including a copy of SDL.dll.  I did not include it in the PR, since a binary blob would (and should) raise security concerns, but I wrote some instructions on how to fetch it and where to put it (again, documenting the simplest option, not the best one).
I've also added Visual Studio Code config folder to .gitignore, it seemed silly to open another PR just for that.
@maximecb Oh, and thanks for creating this project! I started something similar a few years ago - similar vision but smaller scope (no JIT - wonderful to see you adding it).

Oh hey, thanks for this @olimpiu. You are the first PR on this repo, and it makes my day :)

All tests pass now on Windows for all sub-projects. I also added instructions on getting this working on Windows.

Really glad to hear that all the tests pass. It's pretty cool to be able to run the same programs on Ubuntu, Mac and Linux.

If ease of use and on-boarding is a goal (maybe not, at this early stage), you may consider including a copy of SDL.dll. I did not include it in the PR, since a binary blob would (and should) raise security concerns, but I wrote some instructions on how to fetch it and where to put it (again, documenting the simplest option, not the best one).

Yeah there may also be some licensing concerns there. I don't know if we'd be legally allowed to include this in the repo without some kind of license? Another issue is needing to update said DLL since we don't have an automatic windows test suite and I have no windows machine to test this on.
That being said, if there's some kind of automatic windows console command that we could use to download the DLL, that could work, though I don't think they have something like curl or wget on windows, eh?

@maximecb Oh, and thanks for creating this project! I started something similar a few years ago - similar vision but smaller scope (no JIT - wonderful to see you adding it).

Glad you like it. My plan is to take some time to iterate on the interpreter before thinking of a JIT, but I'm confident I can build one that will perform well and not be too complex based on past experience.
If you end up writing code for UVM that could be usable for examples, or utility code or anything like that and you'd be willing to share it, I could accept PRs for that too. I've opened an issue on the topic: https://github.com/maximecb/uvm/issues/7


Variable for shell profile user

When running this role with sudo, I'm unable to write the shell profile to the proper user since sudo makes the ansible_user_id root. It would be nice if I could optionally set a user for the shell profile or just add a full path to the file I want written.

@mhadam I completely agree.
It was moved away from a pretty convoluted logic system previously but I'll have a think about reimplementing it. Did you have any specific ideas?

@mhadam,
Any chance you can test branch issue-84 out?
The results are promising!
You can test the shell profiles by specifying golang_shell_profile as an absolute path to the desired shell profile (such as a .bash_profile found at /root/.bash_profile. It will however fail if you specify a file that does not exist.

Thanks so much! I'll try to test this soon and get back with results.

@mhadam,
FYI I've noticed this is failing all tests on a particular task when the variable is undefined. Should you run into that problem, I already have a fix on the way - but it's just on the shell restart task. You can place a failed_when: false on that as an interim fix if you need to.

The branch issue-85 includes the flow control fixes described above.
It depends on this issue merging, but it's working exactly as intended and should fix the issue originally described. It doesn't however prevent the use of sudo, but I'd like to explore that independently.
As previously discussed, I am waiting for a response - however it would be equally acceptable if you were to test against branch issue-85.

Sorry, finally got around to this. Here's the relevant part of the settings I have right now:
GOPATH: /opt/gopath
GOROOT: /usr/local/share/go
golang_shell_profile:
  - /root/.bash_profile
  - /home/vagrant/.bash_profile

The situation is that the role is being used to setup a VM environment to test code. Honestly it may not need to be put in /opt/gopath, but that's how the project was setup when I started working on it.
An error I found - it assumes that the specified .bash_profile exists, so it throws an error when they don't. I'll patch that now.

@mhadam,
It should be noted that golang_shell_profile is expected to be a string, not an array. So if it's a string which is the absolute path to the profile you want configured in the way the role executes, you can set it to /root/.bash_profile (assuming the file exists).
I'll get a commit in tonight to do a basic stat check which will prevent the tasks from executing if they don't exist. I'll update the readme as well, it's a logical decision despite the fact the variable doesn't have a default value.
So if that is in place, is any more work required here to solve the problem, am I missing the mark for what's needed, or are we able to line a new release up? I'm keen to get this one closed as it's last on the list for the next release, but I want to make sure this is completely fixed before-hand.

The changes in #85 will be migrated into this issue after the tests have run.
Brand issue-85 should now be ready for tests, or feel free to test issue-84 after those changes come back here.
After you've run your test again, I'd appreciate it if you shared your results and what else is needed to progress this issue.

All good, thank you!

#92 is closed, #93 has been opened to facilitate release of this feature.


Major PR - v30.0 - links and cloud-config manifests

This PR represents a big upgrade for the BOSH release:
Assumptions

deployment user will be targeting a modern BOSH director (see https://github.com/cloudfoundry/bosh-deployment)
deployment user will be using bosh2 CLI https://github.com/cloudfoundry/bosh-cli/
deployment BOSH director has/will be using cloud-config
you are excited about all things BOSH 2 and are ready to move forward

Changes

new bosh2 deploy manifests in manifests/ replace the examples/ folder; see https://github.com/cloudfoundry-community/docker-boshrelease/tree/links-and-cloud-config/manifests README for deployment details
cf-containers-broker publishes a type: servicebroker link, which can be consumed by https://github.com/cloudfoundry-community/broker-registrar-boshrelease/pull/5
docker job publishes a type: docker-tcp link to allow docker swarm job to discover its TLS certificates
easy to generate and use TLS certificates to secure TCP access to Docker daemon, thanks to new bosh2 deploy manifests
job properties no longer have docker. or broker. namespacing prefixes; this means no more global properties in manifests; instead configure via job properties; and then share those properties via links
example broker services are in separate manifest files (in BOSH language, these are called operator patch files); it is now easy to pick and choose which services to include in a deployment of the cf-containers-broker
bosh2 ssh users will be able to immediately use docker commands without setting up env vars
bosh2 ssh users will have the delightful ctop CLI available
service's dashboard_client.redirect_uri is now automatically constructed from external_host property

Unchanged

Still docker 1.13
Static container definitions
Service broker should run containers the same way it did before

Notices

I have not tested an upgrade from previous versions to this version - BUT - nothing has fundamentally changed in how the containers nor broker deployments work - containers that were statically configured or dynamically provisioned via the broker should continue to run after the upgrade.
But, there are substantial changes to the look of your deployment manifest - no more global properties, instead move properties into instance_groups's jobs. See the manifests/broker/docker-broker.yml for how manifests work now.
You can easily extract your custom service/service plan definitions into new bespoke operator patch files. Have a look in manifests/broker/services/*.yml to see examples. See https://github.com/cppforlife/go-patch/blob/master/docs/examples.md for more on the new BOSH operator patch syntax + behavior.

TODO

[x] ci pipeline to build candidate release + test each base manifest + shipit
[x] replace old register-routing with pure external release + an op-routing.yml patch file
[x] upgrade to ruby 2.3.3
[x] extract remaining example services into operator patch files
[x] 1+ of the services aren't deploying /app/models/plan.rb:46:in block in validate_attrs': undefined method key?' for #<Array:0x005600880dbae0> (NoMethodError)
[x] shipit-rc to update base manifests with new version + sha1
[x] shipit job
[x] PR to cf-deployment to change private to default network https://github.com/cloudfoundry/cf-deployment/pull/109
[x] document a cloud-config for boshlite that's similar to cf deployment
[x] upgrade to redis 3.2 + postgresql 9.6
[x] push redis/pg images + get CI working
[x] cleanup bosh-lint release warnings
[x] cleanup bosh-lint manifest warnings
[x] upgrade cf-subway-boshrelease to links
[x] default to using cf-subway and have 3-node docker cluster
[x] final release of cf-subway-boshrelease and bake into manifests
[x] broker-registrar needs to register subway; not docker
[x] sanity-test-broker
[x] Why is sanity-test failing after basic deploy?
[x] upgrade go1.5 -> go1.8
[x] TLS certs for docker-broker docker, so external systems can connect
[x] remove docker.tls_verify property - let's not make it optional
[x] docker-broker-deployment repo
[ ] Document how to make new service images, including sanity-test command
[ ] cf-deployment networks private -> default PR merged
[x] broker-deregister errand enabled & working
[x] cf-subway should be registered, not docker brokers
[x] delegate sanity-test of each service to the service's own docker image sanity-test command
[ ] final rc before shipit

Ideas for future:

[ ] add bosh-lint to ci image
[ ] run bosh-lint lint-release during bosh-rc job
[ ] run bosh-lint lint-manifest during each testflight job

If you're a user of Docker Swarm aspect of the release, please contact me to discuss how you're using it. AFAIK I've got a manifests/swarm/docker-swarm.yml manifest that works, has TLS certs, etc. But I've no idea how to use it; so perhaps it doesn't work :)

$ cf marketplace
Getting services from marketplace in org system / space dev as admin...
OK

service        plans               description
arangodb22     free                ArangoDB 2.2 service for application development and testing
consul         free                Consul key-value storage
couchdb16      free                CouchDB 1.6 service for application development and testing
elastic13      free                Elasticsearch 1.3 service for application development and testing
etcd           free                Etcd key-value storage
logstash14     free                Logstash 1.4 service for application development and testing
memcached14    128Mb, 512Mb, 1Gb   Memcached 1.4 service for application development and testing
mongodb26      free                MongoDB 2.6 service for application development and testing
mysql56        free                MySQL 5.6 service for application development and testing
nats           free                NATS is a lightweight cloud messaging system
neo4j21        free                Neo4j 2.1 service for application development and testing
postgresql93   free                PostgreSQL 9.3 service for application development and testing
rabbitmq33     free                RabbitMQ 3.3 service for application development and testing
redis28        free                Redis 2.8 service for application development and testing
rethinkdb      free                RethinkDB is built to store JSON documents

@frodenas so many old favourites still with us

Sweet. docker-boshrelease's sanity-test-broker will now invoke each docker image being used to run a sanity-test command upon a provisioned service instance. It's opt-in; I've upgraded frodenas/redis and frodenas/postgresql images:

https://github.com/frodenas/docker-postgresql/blob/master/scripts/sanity-test.sh
https://github.com/frodenas/docker-redis/blob/master/scripts/sanity-test.sh


[FX-2210] Implements fair editorial display

The type of this PR is: Feature
This PR resolves FX-2210
Description
User can see up to 5 articles associated with the fair

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)

#mergeongreen


Evaluation on test set

Hello Robyn team!
Thank you very much for all your efforts. We have been working to implement Robyn-based solutions for a few of our agency clients, and we are a little stuck on the evaluation. Having looked through issues #65, #148 and #158 we've gathered that there is currently no direct way of using an existing Robyn model to make a prediction on an unseen dataset. In #148 we see the mention of constructing custom predictions from the model coefficients. We tried to go this route but weren't able to reproduce the components yet and were hoping that you might give us a hint. Specifically, this is what we are trying:

Using the input data (the same dataset that comes in as 'dt_input') along with prophet decomposition of the target variable, parameters found in pareto_hyperparameters.csv and coefficients found in pareto_aggregated.csv, obtain the values found in pareto_alldecomp_matrix.csv
The reasoning is that the values in pareto_alldecomp_matrix.csv add up to the prediction (depVarHat), so if we can find the procedure of turning inputs into these values, we can essentially do the 'predict' operation on any dataset. Presumably we need something along the lines of the full ridge regression function. Are we on the right track here?
Unfortunately so far we weren't able to put the whole thing together in the right way
We're on Robyn 3.0

Do you think you're able to give us some direction/course-correct us on this?
Thanks,
Twigeo DS team

Hi, thanks for bringing this up. You're definitely on the right track.

First, regarding reproducing depVarHat, the difficult part is that you need to apply adstock and saturation transformation to input data first, then you can multiply the transformed matrix with each the coefficients to obtain depVarHat.
Second, when thinking about forecasting next week with a multivariate regression, we need all the next week's values of all predictors (media, prophet_vars etc) to predict next week's revenue. For prophet_vars, you need to conduct the prophet decomposition with all periods again and forecast trend/season etc for next week. For paid and organic media, you need to set couple of scenarios: 1 might be spending the same amount as last week or weeks, 2. might be manually insert media plan for paid and "plan" the organics, 3. might be forecast all of them (using prophet for example) individually and use them to forecast sales, 4. might be using different optimised media mix from allocator.
Third, uncertainty is not easy to obtain in Robyn because we're neither determining the "significance" of each beta coefficient due to ridge nor doing any Bayesian simulation. Instead, we have to be creative. One idea could be using the coefficient estimates from the latter part of the hyperparameter iterations (e.g. the final 10%, because they're most optimised) and produce the lower and upper bounds based on those. This can be observed in the newly added roas convergence plot.

As you can see, we do consider building the forecast function too. Due to complexity and resource constraints, we can't promise any release dates at the moment though.

feel free to reopen if necessary


created XSL file for adding a new channel

Adds a new channel into the XML.
This is a spicevmc channel needed by space to allow functionalities like  copy/paste.
Tested and works great
Please make sure you read the contributor documentation before opening a Pull Request.

thx for contrib!


cherrypick: configure static directory, default wwwroot (#3682)

Fixes #3681

Pull Request Test Coverage Report for Build 839561468

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 84.249%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

Totals

Change from base Build 837299304:
0.0%

Covered Lines:
18834

Relevant Lines:
21259

💛  - Coveralls


Pick through time oddities

Describe the bug
When using the old method for picking through time, I've noticed a very strange behavior. After adding a selection operator (I've tried two so far) and selecting some reduced section of the dataset, whatever cycle the time slider state is set to will cause dramatic spike (negative or positive) in the curve plot at that cycle.
Helpful additional information

[ ] Did VisIt crash?
[x] Did you get wrong results?

Impact

[ ] High - User productivity significantly degraded
[x] Medium - User productivity partially degraded
[ ] Low - User productivity trivially degraded

Likelihood

[ ] High - occurrence is not specific to platform, data, config, a combination of operators, queries, etc.
[x] Medium - neither low nor high likelihood
[ ] Low - occurrence is specific to combination of multiple factors such as configuration, data, platform, etc.

To Reproduce
There are many ways, but here's a simple example:
OpenDatabase("testdata/silo_hdf5_test_data/wave.visit")

SetTimeSliderState(10)
AddPlot("Pseudocolor", "mesh_quality/skew")

AddOperator("Isovolume")
IsovolumeAtts = IsovolumeAttributes()
IsovolumeAtts.lbound = 0.01
SetOperatorOptions(IsovolumeAtts)

DrawPlots()

val1 = PickByZone(do_time=1, domain=0, element=3910, preserve_coord=0, use_actual_data=1)

Expected behavior
There should be no spike in the curve...
Attachments
Screenshot of above code when time slider state is set to 10.

Screenshot of above code when time slider state is set to 20.

Desktop
Mac and Linux (LC).
Additional context
use_actual_data must be set to 1. This is the default setting, which triggers the old Pick through time pathway.

This appears to be resolved. I'm guessing something fixed this during the DDQOT update.


New version: Telerik.Fiddler.Everywhere version 5.3.0

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow


[Docs] Document changing the webconsole-password

Documentation request
I could not find any information about changing the webconsole-password.
Hardcoding user and password information is obviously a bad idea and completely defeats the use of passwords. Maybe I have missed something, but if not, this is a serious problem.
Suggestion
Include documentation on changing the webconsole-password in the wiki.
Additional context
Since this is an open-source project, one can obviously change the password somehow. An easier option would still be very much appreciated.

I found the source file, containing the password:
https://github.com/free5gc/webconsole/blob/main/frontend/src/config/config.js
But only being able to change the password before building is not a great security practice in my opinion

Hi @kelke
Thanks for your suggestions.
I agree with you that we hard code the password in the webconsole is insecure.
But the webconsole is not born for commercial purpose.
If you want to enhance the security of the webconsole, you could try to modify the existing JWT authentication mechanism for multi-tenant :)

@kelke
We welcome any PR for this.


安装DeepKE时报错

Collecting seqeval==1.2.2
Using cached http://mirrors.cloud.aliyuncs.com/pypi/packages/9d/2d/233c79d5b4e5ab1dbf111242299153f3caddddbb691219f363ad55ce783d/seqeval-1.2.2.tar.gz (43 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [38 lines of output]
WARNING: The repository located at mirrors.cloud.aliyuncs.com is not a trusted or secure host and is being ignored. If this repository is available via HTTPS we recommend you use HTTPS instead, otherwise you may silence this warning and allow it anyway with '--trusted-host mirrors.cloud.aliyuncs.com'.
ERROR: Could not find a version that satisfies the requirement setuptools_scm (from versions: none)
ERROR: No matching distribution found for setuptools_scm
/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/dist.py:771: UserWarning: Usage of dash-separated 'index-url' will not be supported in future versions. Please use the underscore name 'index_url' instead
warnings.warn(
/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
Traceback (most recent call last):
File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/installer.py", line 82, in fetch_build_egg
subprocess.check_call(cmd)
File "/root/anaconda3/envs/deepke/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/root/anaconda3/envs/deepke/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpe9emxw6q', '--quiet', '--index-url', 'http://mirrors.cloud.aliyuncs.com/pypi/simple/', 'setuptools_scm']' returned non-zero exit status 1.
  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-7idph_oq/seqeval_2ca6242e48344c6b9b949e0a720be990/setup.py", line 27, in <module>
      setup(
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/__init__.py", line 86, in setup
      _install_setup_requires(attrs)
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/__init__.py", line 80, in _install_setup_requires
      dist.fetch_build_eggs(dist.setup_requires)
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/dist.py", line 875, in fetch_build_eggs
      resolved_dists = pkg_resources.working_set.resolve(
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/pkg_resources/__init__.py", line 789, in resolve
      dist = best[req.key] = env.best_match(
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1075, in best_match
      return self.obtain(req, installer)
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1087, in obtain
      return installer(requirement)
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/dist.py", line 945, in fetch_build_egg
      return fetch_build_egg(self, req)
    File "/root/anaconda3/envs/deepke/lib/python3.8/site-packages/setuptools/installer.py", line 84, in fetch_build_egg
      raise DistutilsError(str(e)) from e
  distutils.errors.DistutilsError: Command '['/root/anaconda3/envs/deepke/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpe9emxw6q', '--quiet', '--index-url', 'http://mirrors.cloud.aliyuncs.com/pypi/simple/', 'setuptools_scm']' returned non-zero exit status 1.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
(deepke) [root@iZ8vbgeaa0ig6ufzdwoucpZ site-packages]# pip install seqeval==1.2.2
Looking in indexes: http://mirrors.cloud.aliyuncs.com/pypi/simple/
Collecting seqeval==1.2.2

第一步：需要手动pip安装setuptools_scm
pip install setuptools_scm

第二步：需要手动pip安装seqeval==1.2.2
pip install seqeval==1.2.2

最后，再安装pip install deepke即可

非常赞的说明


Should remember Baud rate and Line-ending settings (all settings)

Type: Bug Report
Describe the bug

OS and Version: Windows
VS Code Version: 1.66.2
Serial Monitor Extension Version: v0.1.0
Target embedded device: Infineon PSoC6
Other extensions you installed (and if the issue persists after disabling them): Cortex-Debug (my extension)
A clear and concise description of what the bug is.

Between invocations of VSCode, it should remember all the settings. Currently, baud rate and line-ending are not remembered. These should be really per workspace settings too. Maybe same issue exists with other settings.
To Reproduce
Steps to reproduce the behavior:

Set Baud rate to anything other than 300, and Line Ending to CRLF
Optionally try to use the monitor for some embedded use, if you wish.
Exit VSCode, restart, examine the SERIAL MONITOR tab.
Settings are not what was there before. Reverted back to 300 and None

Expected behavior
Should remember all settings on a workspace/folder basis

Thanks for the feedback! There are a few different ways to persist this data in VS Code. To clarify, assuming we added a vscode-serial-monitor.defaultBaudRate (and similar) setting for workspace and global settings.json files, does this make sense to you as the search order for defaults?

Workspace settings.json. This means the user has explicitly set a default for the workspace.
Global settings.json. This means the user has explicitly set a global default.
Most recently selected value from workspace state. This means the user has not explicitly set a default, but has used the Serial Monitor before in this workspace.
Most recently selected value from global state. This means the user has not explicitly set a default or used the Serial Monitor before in this workspace, but they have used the Serial Monitor before.
Some hardcoded default fallback value.

To clarify, assuming we added a vscode-serial-monitor.defaultBaudRate (and similar)

Yes, exactly.
As to the search order, you are right again. Except, I need to do a bit of research -- my own extension as an example to see what VSCode actually does when I change a setting programmatically. It has been a while since I looked at that code. Quick look at the code, it does the following to change the setting
        const config = vscode.workspace.getConfiguration('cortex-debug');
        vscode.commands.executeCommand('setContext', `cortex-debug:some-setting`, newVal);
        try {
            config.update('some-setting', newVal);
        ....

For config.update(...) a target is not specified but the default target is a workspace and it just works across sessions. I don't remember the mechanics. I inherited some of this code but I don't know what or how VSCode resolves the update vs get across sessions.
But we also have to monitor for setting changes including changes done programmatically
        vscode.workspace.onDidChangeConfiguration(this.settingsChanged.bind(this)),

All of the work to react setting change is actually done by the settingsChanged method and not at the point of updating a setting (programmatically or otherwise)
Maybe we are doing it all wrong but our extension was created a looong time ago, before workspaces existed.
Note: We used the WorkspaceConfiguration API almost exclusively not global/workspace states

Got it, thanks for confirming and providing all those examples! That should be plenty for us to address this issue.

Just one more thing. The settingsChanged is super generic. So we do the following
    private settingsChanged(e: vscode.ConfigurationChangeEvent) {
        if (e.affectsConfiguration('cortex-debug.some-setting')) {
    ...

You may not have to be selective like we had to and assume everything changed.

@haneefdm Support for remembering settings is now active in the pre-release channel! Currently there is no support for manual/explicit user settings in a settings.json, though that is likely coming, though persistance across sessions is supported!

Works


convert string to boolean.

closes https://github.com/r2dbc/r2dbc-postgresql/issues/208

Thanks a lot for your contribution. The changes look pretty decent and we're going forward with merging this PR now.

Thanks Mark.

That's merged, polished, and backported now.


fix newslatter input and button in small size

issue no #800
Fix in center input filed and button

@mdazfar2 Please check this updated fork's PR !


forge test vm.env got val:  logs suppression/silence

Component
Forge
Describe the feature you would like
Component: forge test
So I've been testing my contracts and can't find a way to store a signature generated by a wallet to bytes memory.
During this time I also found a way to bypass this on the .t.sol by using vm.setEnv  and retrieve the value using vm.envBytes
Now my problem is I am using a fuzzer on my test and this got val: log is taking all the space on the terminal exceeding it's default limit that using the search feature of the terminal won't even register them since they've been truncated.
Now, I've tried --silence which did nothing.
This is making it hard for me to view other test's result / console2.log since they've already been truncated.
so is there a way for us to have a flag or config of some sort that would silence vm.env output logs?
Additional context
This is an example of the got val: logs I am talking about

what's your forge --version?

what's your forge --version?

ohhh sorry forgot to add that part
forge 0.2.0 (87283bc 2023-10-06T00:27:02.062949965Z)

I believe I remember this, we forgot to remove a debug println.
please try after foundryup, this has since been fixed

I believe I remember this, we forgot to remove a debug println.
please try after foundryup, this has since been fixed

okay it was not showing now in
Version:  forge 0.2.0 (7b45265 2023-11-21T00:22:00.899582254Z)
still it would be better to have a toggle switch for it, since it is also how i found there was an incorrect in my vm.setEnv
something like --log-vm


nonzero exit code on failures

We should detect when we unwrap, so the compositor has a chance to restart the application on crashes.

@freyacodes just hypothesised that systemd should restart the application when it exits. I'll asign them to this issue, they'll report back here with their investigation's conclusion.

Something like this perhaps
systemd.services."cage-tty1".serviceConfig = {
  RestartSec = 5;
  Restart= "always";
};

I looked at cage briefly, and it doesn't look like it manages restarting its children.

This issue is about the zero exit code of the rust binary I was getting, even when it failed due to missing config. It caused systemd to report success.

I couldn't repro this anymore - saw nonzero exit codes on errors. I'll do some research on cage behaviour with it's only payload being terminated, and ensuring restarts, probably using the snippet above.


Remove duplicate copyright

Noticed these had the copyright twice

and I was not sure whether to leave the one at the top or bottom of the list - in other files the ESF copyright has been put at top or bottom, it varied - seemed to be no standard implemented there.

and I was not sure whether to leave the one at the top or bottom of the list - in other files the ESF copyright has been put at top or bottom, it varied - seemed to be no standard implemented there.


Load ~/.env-vars before ~/.localrc and the config files

Fixes issue reported at
https://github.com/holman/dotfiles/commit/f5fbf5de3f5a6ecfc60814397014e13b24b398b9#commitcomment-9506982 where environment variables defined in ~/.env-vars are not surfaced to the config files named path.zsh and are not available to config files that come after private/env-vars.zsh alphabetically.

Thanks for the pull! I agree that that probably makes sense. I was going to go and merge it, but then realized that .localrc and .env-vars are basically doing the same thing, so instead I just nuked the .env-vars portion. Think that makes sense.

:+1: cool, I thought the same when I saw .env-vars :smile:


Make image ids consistent in servicer fixture

Something I broke out of #1041 because it felt ugly that the main object ids were fu-1 and im-0. Now it's consistently numbered starting 1

@prbot approve


Update Weaver.cs

I believe this is the fix for #1519 refering to a change that was edited in https://github.com/vis2k/Mirror/commit/bb55baa679ae780e127ed5817ef10d7f12cd08c8 but wasn't also edited in the weaver

This PR is not 100% right,  there are many sections where we do need Mirror.NetworkReader
However,  I thank you because your "fix" pointed me to the right problem.
The real problem is in this line:
https://github.com/vis2k/Mirror/blob/cdfc1752f24eb1414ea4b448dd498df5b7fa1cb8/Assets/Mirror/Editor/Weaver/Processors/NetworkBehaviourProcessor.cs#L103
That creates a local variable of type NetworkWriter,  but that specific local variable should be of type PooledNetworkReader.

I'll send a PR in a few hours with the correct fix

I will close this PR then :)


Adding order argument to asarray

A usecase I'm confronted to is to ensure that a given array has either a C or F memory layout.
The layout can be important when optimizing memory access patterns in lower level code. For instance in sklearn KMeans requires C order. Typically xp.asarray(X, order=order)  is used to check that the input order matches the required order (if copy=False), or will trigger a copy if necessary to get the expected order (if copy!=False), before passing the array to lower level code (e.g cython or jitted functions).
Here's an example of API implemented by dpctl.tensor, an array-API compatible array library, that also exposes the order parameter to asarray.

I think we purposely leave strides (and thus order) out of the standard because it's considered too low-level. However this information is totally available through DLPack, I would think this should meet your need?

For my particular needs I have a workaround already, in general I would think that people that really need this can think workarounds in some way, but at the cost of some extra lines of code that are going to be specific to one array library. Having order in asarray could help having better code for developers that do input validation in python.

at the cost of some extra lines of code that are going to be specific to one array library

Sorry but I disagree. If you check the strides obtained through DLPack (see, for example, mpi4py) it's generic to the array library. This is arguably not natural to Python-only developers, and suggestions are welcome in this DLPack thread: https://github.com/dmlc/dlpack/issues/116 🙂
Currently Array API is designed to not standardizing over strides (and thus order) so that people do not have to argue over the execution model. For example, it allows the two extremes, PyTorch (which is always C-order unless you tweak it very hard) and Dask (which has no notion of single-node strides, as it's distributed), to implement Array API support.

Sorry

No need to be :relaxed: thank you for the insights.
I by no mean want to imply that the perspective I offer on the matter goes beyond the scope of the limited project I've started working on, that happens to be somewhat related to the Array API, which made me think this proposal could be relevant. If it resonates with other people experience, that would be interesting ! if it's not the case, let it be. Maybe the issue can remain opened for some time to see if there's other feedback ?
And as you say maybe I don't need strides at all myself. After all, all arrays can be seen as C-contiguous, it's a matter of defining carefully row and column indexes :shrug: . But then it's an abstraction that must be implemented at the level of my own user code if I really want to and it seems very verbose.
In the end I don't think the dlpack interface answers what I'm looking for specifically. Unless I'm missing something, the from_dlpack function isn't supposed to take any other argument (such as strides/order) than the object exposing __dlpack__, and the PyCapsule object doesn't expose attributes readable from python code, which are things I would have been looking for.

This has been brought up a couple of times before, although I cannot locate the most relevant discussion right now. The problem is mainly that the array API standard wants to only standardize things that are implemented or can be implemented in all array libraries. This is not the case for order=. TensorFlow, JAX and PyTorch all do not have Fortran memory order as a user-visible concept, and do not want to add it.
On top of that I'd say that it's not good UX. The problem with NumPy is that, due to the lack of more advanced facilities for automatically optimizing function calls for performance, it exposed a host of things that really should be implementation details (like views and C/Fortran memory order) directly to end users.
For order=, it will have to remain specific to the libraries that have such a concept. It can be implemented as a superset of what's in the array API standard, so there is no problem here.

The layout can be important when optimizing memory access patterns in lower level code. For instance in sklearn KMeans requires C order.

This is very much true. But it's an implementation detail; how to get optimized code internally within a library should be a separate question from what API is exposed to end users.

I hope array libraries that want to expose additional parameters can use the same semantics for similar concepts

I hope to too. AFAIK that's the case here, libraries that have the concept follow NumPy in API design I believe.

This has been brought up a couple of times before

Yeah IIRC I raised the discussion on strides during the meetings at least twice, and others did too. I had the same idea in mind as @fcharras did that it'd allow better interoperability with 3rd party (non-array/tensor) libraries. But in the end people (the stakeholders) are happy to settle on this choice for reasons Ralf and I mentioned above 🙂

Let's close this, since the reasons given seem enough. Thanks again @fcharras and @leofang.


Microsoft Edge click not selecting the clicked option

Let me know if you can't reproduce locally. I have a fix for this locally and can submit a pr if its reproducible outside of my environment but I don't have much spare time to set up a codepen.
This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 3.4.2

Platform/Target and Browser Versions: Microsoft Edge Browser Latest but pretty sure its broken in older versions as well.

Live Link or JSFiddle/Codepen or website with isssue:

What you did
Created swiper and tried to click an option
Expected Behavior
Clicking on an option should select it
Actual Behavior
Clicking an option doesn't select it

Fixed in latest version

Hello, nice to see you fix this question, but I still have the question when I test it by IE. Please help me and thank you very much. example on codepen


systemverilog-plugin: fix packed arrays of enums

This PR fixes size and access to packed array of enum.
UHDM-integration-test: https://github.com/chipsalliance/UHDM-integration-tests/pull/732
yosys-systemverilog run: https://github.com/antmicro/yosys-systemverilog/actions/runs/4935744732

Actually this change makes opentitan to timeout in CI, marking as draft until resolved.

New yosys-systemverilog run: https://github.com/antmicro/yosys-systemverilog/actions/runs/5176142077
now all tests passes.


Error with upper mpdf in last commit

f9a8f33e608697599d44d3b9b0a93e7b9e34f0c3
in this commit uppered php version but not mpdf version,
there for after update load last version of mpdf, that not compatible this your project.

Your right, in fact, checking carefully, the version constraint should be for mpdf, not php. My bad. I'll fix it soon. Or if you can send a pull-request, it would be nice.

Please, update to the latest version.


⚠ ClamAV has degraded performance

In 4bc235c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 50 ms

Resolved: ClamAV performance has improved in 23c7c44.


Amended the preUpdate, appended to the enum, verified with tests

We need to update ApprovedPremisesApplicationStatus in the API spec to add a pending placement request entry:
    ApprovedPremisesApplicationStatus:
      type: string
      enum:
        - started
        - submitted
        - rejected
        - awaitingAssesment
        - unallocatedAssesment
        - assesmentInProgress
        - awaitingPlacement
        - placementAllocated
        - inapplicable
        - withdrawn
        - requestedFurtherInformation
        - pendingPlacementRequest

And then update the transformer lookup in https://github.com/ministryofjustice/hmpps-approved-premises-api/blob/36b4239096d7a17dfdabb4ad231fd77a50d97a31/src/main/kotlin/uk/gov/justice/digital/hmpps/approvedpremisesapi/transformer/ApplicationsTransformer.kt#L39


Add additional operator to data source "dynatrace_service"

Hello guys,
I've done my best attempt at adding the operator field to the data source fields, currently only adding CONTAINS and keeping EQUALS as the default, allowing backwards compatability with how it was.
I'm very much open for feedback or suggestions.
Adresses some of #188

Thanks for contributing!


Fixed spelling issue with authentication.

There was a small spelling issue on the dashboard.

I fell over your project just today. I was using MatBlazor before, but this project seems to be more mature. Maybe I will give it a try :)

thats a great compliment. thanks. please try and provide your feedback. please do raise issues if any critical components are missing. so will try to implement in next release.


Atomic model prox

Re: atomic tests, it's already mostly done in the unactivated solver serialization test

and sure we can have this without python changes


Compiling Dist Stuck on ngtemplates:main task

For some reason grunt gets stuck here
Running "autoprefixer:dist" (autoprefixer) task
File .tmp/app/app.css created.
File .tmp/app/app.css.map created (source map).
Running "ngtemplates:main" (ngtemplates) task
The reason seems to be that there is an error in the html. I added commas between html attributes. However I believe this should be parsed for errors.

How can I know which files are affected?

I use grunt to run html min, so I enable verbose mode
grunt build -v

Grunt will then usually get stuck on the template which has the problem. It does not tell me where in the file the problem is, but opening the file on an IDE usually tells me if any tags have been left open or properties have been incorrectly mentioned.
I rinse and repeat.
(hope someone can give you a better answer)

Thanks ! this is working for me using verbose mode.

This issue should not be closed, it still remains. This happens to me and there is no issue with htmlmin or any other task, I runned them all individually, everything passes but still it gets stuck:
Running "ngtemplates:main" (ngtemplates) task
There is no output of any type to know what is happening. I updated all the dependencies. So better error output handling please.

@eduardoinnorway the issue does lie in html-minifier. Have you tried running with --verbose turned on? You should see it output Minifying file: [html markup] at the point where it's hanging. If you don't see this, make sure you're not running your grunt task as part of an npm script, as it may not take your --verbose flag. I would also recommend using https://github.com/htmllint/grunt-htmllint as part of your build task if you're running into this problem, it should help you catch it.

Running with --verbose helped me discover the bad markup that caused the minifier to choke.

This answer has helped me. Thanks @zsiswick

@dev-d  "grunt build -v" hey its worked for me.... thanks dude  👍


Compilation .coffee from a command line

Hello,
I've searched the sources on how to compile the .coffee with the package, but found out that it can't be done with command coffee, so in my project the htmlized code like div { class='x'} stays uncompiled and passed into html as is. How to pass it to page as it would be a JSX code one?

Hi @majioa, I assume you're talking about the CoffeeScript included on the README? Reactive templating code does not get compiled to HTML. Rather, it's used to generate the DOM during runtime. So, to add your templates to the page, you'd need to do something like this:
$(document).ready -> $('body').append div {class: 'x'}

Does that answer your question?
PS: I really need to convert the README CoffeeScript to JavaScript. I'll try to get that done in the next couple of days.

I've also updated the README to point to the new documentation site, bobtailjs.io, which may prove helpful.


How can I benchmark my MongoDB?

I'm still reading the instructions and it is starting to make sense, but all I want to do is benchmark my MongoDB and MySQL. How do I go about doing this?

This is what I did
ycsb load mongodb -P ../workloads/workloada
If you say this is correct then I can close this issue :D

It worked! Thanks!


node build failed ,server.init is not a function

Describe the bug
TypeError: server.init is not a function
at file:///mnt/d/source/official-website/build/handler-393b2283.js:1047:8
at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
at async loadESM (node:internal/process/esm_loader:88:5)
at async handleMainPromise (node:internal/modules/run_main:61:12)
Reproduction
None
Logs
No response
System Info
{svelte,@sveltejs/*,vite} adapter-node

Severity
annoyance
Additional Information
No response

We can't diagnose anything without a reproduction and without the versions of dependencies you're using. This sounds like you need to make sure that both the adapter and Kit itself are on the latest versions.

I can confirm I had this issue with latest adapter but slightly out of date kit, and bumping to these latest versions fixed it:
  "@sveltejs/adapter-node": "^1.0.0-next.86",
  "@sveltejs/kit": "1.0.0-next.405",

Upgraded the kit version and then resolve this problem

TypeError: server.init is not a function bug was present on Vercel too, the update to "1.0.0-next.405" fixed it.