load model workaround

Add support to load the model in an alternate way.

Codecov Report

Merging #60 into master will decrease coverage by 0.43%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
- Coverage    88.2%   87.77%   -0.44%
==========================================
  Files          28       28
  Lines        1560     1570      +10
  Branches      208      209       +1
==========================================
+ Hits         1376     1378       +2
- Misses        163      171       +8
  Partials       21       21

Impacted Files
Coverage Δ

pelops/features/keras_model.py
55.55% <25%> (-13.68%)
:x:

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 40371cc...0e46ae1. Read the comment docs.


Sass not supported

Project readme claims support of Sass:
Stylesheets with SASS (not required, it supports regular css too).
Yet it doesn't seem to be supported at all:
Error in ./src/app/test/test.sass
Module parse failed: /xxx/src/app/test/test.sass Unexpected token (1:0)
You may need an appropriate loader to handle this file type.
*
    color: orange

I am really ignorant on this CSS pre processors. Isn't 'scss' the same as 'sass'? We are using .scss as the extension. But we can activate .sass as well.

SCSS and SASS format differ (SCSS is a bit enhanced CSS - mainly scoping, SASS goes even further and allows e.g. to omit { } ;).
Googled a bit and fix is suprisingly simple - just modify regexes from /\.scss$/ to /\.(scss|sass)$/,.

yup, is pretty much that. Create a PR if you want or I can fix that myself.

PR #225 should fix it, closing this issue.


about "world.debug.draw_line"

CARLA version:  0.9.15
Platform/OS:   ubuntu20.04
Problem you have experienced:  When using world.debug.draw_line(start_point, end_point, thickness=thickness, color=color, life_time=1000), the drawn line looks like a laser. Can it be a regular solid line or other line styles?
Other questions: Does Carla have a function to fill a region with color?

Hello, I have also encountered a similar issue, whether using “draw_line” or “draw_box”, this laser lane occurs. However, according to #7833 you didn't seem to have this problem on version 0.9.14, while I have it on 0.9.13. I am also very confused about this.


How is Cargo combined for release?

Describe the problem you are trying to solve
I'm trying to understand how Cargo is released via rustup to allow combining then hard linking the various binaries.
This is especially helpful given Cargo's static linking. Even libstd takes up several megabytes per binary if not dynamically linked or built with -Z build-std --target <triple>.
Notes
This is a surprisingly hard question to find an answer to! Some results from searching:

https://stackoverflow.com/questions/34171811/merging-two-programs-in-linux-while-preserving-functionality

Busybox calls this a "multi-call binary" with details here:
https://www.redbooks.ibm.com/abstracts/tips0092.html
I don't think that's what's being done here.

I did some digging and found that there isn't much magic here. The binaries in "~/.cargo/bin" just reference the binaries within "~/.rustup/toolchains//bin"


[GSSoC'2021] Add Bubble Sort in Python

Hello mentors, I would like to add bubble sort in python so please assign this to me.
@tarun26091999 @shreyanspoddar @nakul-19 @OjusWiZard @raksha009 @rudrakshi99 please  assign this to me.

Hello mentors I can do this issue using python please assign me this issue.

Hello mentors ,
I m Anamika jain .
I wants to contribute to this issue .
please assign this issue to me.
@vedant-jain03 @AmanUpadhyay8 @tarun26091999 @dheerajkotwani @anubhavitis

Hello sir , I want to contribute for this issue please assign me this issue .under GSSOC


Periodic cutoff of local position from EKF2

Describe the bug
I am observing periodic cutoff of local position data from the EKF2 with the setup as mentioned below.
At the cut-offs, the optical flow is giving valid data.
Setup

Intel aero drone
PX4 v1.9.2 with PX4Flow driver enabled
Px4Flow
Parameters:

EKF2_AID_MASK = 2 (Optical flow)
EKF2_HGT_MODE = Barometer

Teraranger One data sent from a computer companion to FCU through mavros.

To Reproduce
Steps to reproduce the behaviour:

Flash an intel aero drone with v1.9.2 PX4 firmware with PX4 driver enabled.
Connect PX4Flow over the telemetry port on the intel aero drone.
Visualize the local_position data on QGroundControl
Initially, the local position data gives good data then the periodic cut-off starts after 10-30 secs or so.

Screenshots

Logs
Here are the logs.
The .ulg file can be found here intel-ulg-file.tar.gz.
I was hoping someone could provide some suggestions to start debugging this issue.
Ashwin

This looks indeed very wrong. Could it be that the flow orientation is incorrect or something trivial like that?

Hey, @julianoes  I usually use an IRIS+ drone for R&D. Checked the mounting/physical-orientation on the IRIS+ and the SENS_FLOW_ROT is set to Yaw 270(default) which seems to be working well. The intel drone (which is having this issue) is set up exactly the same way. So I don't think it is the orientation.
Additional info: I am getting good data on the OPTICAL_FLOW_RAD.integrated_x and OPTICAL_FLOW_RAD.integrated_y when this phenomenon occurs.
For those who are interested to know about the mounting of PX4flow here is the link

I would suggest to use master because some improvements for flying with Flow have been merged but I'm not sure if master still works on Intel Aero. The problem is that Intel Aero is not supported anymore by Intel.


Add qzg

Adds @qzg to the list of repos to pull in.

@mshuler Could you merge and deploy this when you can? Thanks!


Allow multiple ref on power lines

Currently refs are only rendered when there is only one, when there are multiple it doesn't render.
This situation arises when there are multiple power circuits on the same towers.
It should be as simple as splitting the ref property by ; and putting each ref on it's own line within the label, like OSM does with highway numbers
Screenshot

Link to where this issue occurs on OpenInfraMap
https://openinframap.org/#15.05/46.17554/-70.6596
Link to the corresponding entity on OpenStreetMap
https://www.openstreetmap.org/way/979914198#map=17/46.17661/-70.66375

It should be said that if those refs are actually related to power circuits, they should go in relations involving the power line.
Like frequency and operating voltages.
We're still waiting this proposal be finished : https://wiki.openstreetmap.org/wiki/Proposed_features/Power_routing_proposal
Intermediate scheme has been rolled out in France, waiting for the final answer on this particular topic : https://www.openstreetmap.org/user/InfosReseaux/diary/392777
These two relations involve similar power lines, with respective ref:FR:RTE:

https://www.openstreetmap.org/relation/5995928
https://www.openstreetmap.org/relation/5995937

Yes, I will definitely take another look at this once the routing proposal is finalised.
Incidentally in Great Britain, the ref does refer to the actual power line, not to the circuits (which only have names, not refs).

It is good to have different references, respectively to physical lines and circuits over them.
It ease any conflation or data linkage.


allow HTTP filters to be marked as optional

#14982 added new fields to the API to allow HTTP filters to be marked as optional -- i.e., if a filter is not known to a client, the client will ignore that particular filter instead of NACKing the entire config.  gRPC is implementing this now, and we'd like Envoy to have the same behavior.
CC @htuch

@htuch, can we tag this so that it doesn't go stale?  Thanks!

It doesn't look like this was fully fixed.  It looks like https://github.com/envoyproxy/envoy/pull/16119 added support for the HttpFilter.is_optional field but did not add support for the FilterConfig.is_optional field in typed_per_filter_config.  Instead, it looks like it plumbed a list of optional filters down from the HCM config down into the RouteConfig validation code, which is used to determine which entries in typed_per_filter_config are optional.
I don't think that approach will actually work once Envoy has the kind of caching xDS client layer that @adisuissa is working on for https://github.com/envoyproxy/envoy/issues/13009, because I don't think that caching layer would be able to tie the RDS watch to an individual Listener that uses it, since there could actually be multiple Listeners that use the same RDS resource, and those two Listeners could have different lists of optional filters.
Given that, I think Envoy still needs to support the FilterConfig.is_optional field.

@wbpcode

It doesn't look like this was fully fixed. It looks like #16119 added support for the HttpFilter.is_optional field but did not add support for the FilterConfig.is_optional field in typed_per_filter_config. Instead, it looks like it plumbed a list of optional filters down from the HCM config down into the RouteConfig validation code, which is used to determine which entries in typed_per_filter_config are optional.

Maybe I should this question https://github.com/envoyproxy/envoy/pull/27210#discussion_r1188400642 here.
Not sure why we need is_optional for pre route config. Since for the upgrade case, the new filter and its pre-route config should be optional, otherwise it will still break the old version envoy.

Not sure why we need is_optional for pre route config. Since for the upgrade case, the new filter and its pre-route config should be optional, otherwise it will still break the old version envoy.

To avoid route config rejection?

Not sure why we need is_optional for pre route config. Since for the upgrade case, the new filter and its pre-route config should be optional, otherwise it will still break the old version envoy.

I'm not sure what you mean by "pre route config".
The reason for needing is_optional in the per-route/vh filter configs is the same as the reason for needing is_optional in the HCM config.  When the data plane receives the RDS resource, it needs to validate that resource -- and that validation needs to evaluate only that RDS resource in isolation, without any knowledge of which HCM instance(s) the RouteConfig may be used with, as per discussion in #26097.  The validation needs to look up the filter implementation based on the type_url and make sure that the filter implementation is supported; if not, it needs to NACK the RDS resource.  The is_optional field allows the data plane to know that if the filter implementation is not supported, it's okay to ignore it instead of NACKing the RDS resource.

Not sure why we need is_optional for pre route config. Since for the upgrade case, the new filter and its pre-route config should be optional, otherwise it will still break the old version envoy.

I'm not sure what you mean by "pre route config".

sorry, I mean the pre-route/vh filter configs here.

The reason for needing is_optional in the per-route/vh filter configs is the same as the reason for needing is_optional in the HCM config. When the data plane receives the RDS resource, it needs to validate that resource -- and that validation needs to evaluate only that RDS resource in isolation, without any knowledge of which HCM instance(s) the RouteConfig may be used with, as per discussion in #26097. The validation needs to look up the filter implementation based on the type_url and make sure that the filter implementation is supported; if not, it needs to NACK the RDS resource. The is_optional field allows the data plane to know that if the filter implementation is not supported, it's okay to ignore it instead of NACKing the RDS resource.

If allow the user config is_optional in the per-route/vh filter configs, then it may have the case: HCM marks the filter's is_optional as false, then per-route/vh marks the filter's is_optional as true. I'm thinking why we need such case.
I guess that for the case: HCM still using the old config (doesn't include the new filter yet), then the RDS pushes a new config which includes a new filter's pre-route/vh filter configs, then we need to mark that new filter's pre-route/vh filter configs as optional. Then envoy won't NACK that config.

sorry, I mean the pre-route/vh filter configs here.

I am guessing that you actually mean per-route, not pre-route. :)

If allow the user config is_optional in the per-route/vh filter configs, then it may have the case: HCM marks the filter's is_optional as false, then per-route/vh marks the filter's is_optional as true. I'm thinking why we need such case.

Yes, that config is possible.  In that case, if the filter is not supported by a data plane, then the data plane will accept the HCM config but reject the RDS resource.
There's probably no use-case where that's actually desirable, but I don't see how we can do better without breaking cachability.

I guess that for the case: HCM still using the old config (doesn't include the new filter yet), then the RDS pushes a new config which includes a new filter's pre-route/vh filter configs, then we need to mark that new filter's pre-route/vh filter configs as optional. Then envoy won't NACK that config.

Yes, if a filter is actually not supported by the data plane, then the filter's config needs to be marked as is_optional in both the HCM config and in the per-route/vh config.

sorry, I mean the pre-route/vh filter configs here.

I am guessing that you actually mean per-route, not pre-route. :)

thanks! finally knowing where I make the thing confused :)

closed by #27263


Update CycloneDX Protobuf schema to v1.6

Current Behavior
We currently use the CycloneDX Protobuf schema v1.4:

https://github.com/DependencyTrack/hyades/blob/main/proto/src/main/proto/org/cyclonedx/v1_4/cyclonedx.proto
https://github.com/DependencyTrack/hyades-apiserver/blob/main/src/main/proto/org/cyclonedx/v1_4/cyclonedx.proto

Proposed Behavior
Update the schema to v1.6: https://github.com/CycloneDX/specification/blob/master/schema/bom-1.6.proto
Note that v1.6 may not be backward-compatible with v1.4, because up until v1.6, the schema was not checked for backward-compatibility. We need to check how this affects us. If Kafka records were produced with CycloneDX schema v1.4, can we consume them with v1.6?
Since that version, the Protobuf schema is tested with buf: https://github.com/CycloneDX/specification/blob/master/.github/workflows/test_proto.yml
That should make it more stable / backward-compatible for future releases.
Checklist

[X] I have read and understand the contributing guidelines
[X] I have checked the existing issues for whether this enhancement was already requested

We will likely need a deserializer that:

Tries to deserialize using the new schema version
If that fails, tries to deserialize using the old schema version
If that succeeds, converts from the old to the new format

Here's a quick draft for how that might look like:

FallbackKafkaDeserializer.java
/*
 * This file is part of Dependency-Track.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 *
 * SPDX-License-Identifier: Apache-2.0
 * Copyright (c) OWASP Foundation. All Rights Reserved.
 */
package org.dependencytrack.event.kafka.serialization;

import org.apache.kafka.common.errors.SerializationException;
import org.apache.kafka.common.serialization.Deserializer;

import java.util.function.Function;

public class FallbackKafkaDeserializer<T, R> implements Deserializer<T> {

    private final Deserializer<T> delegateDeserializer;
    private final Deserializer<R> fallbackDeserializer;
    private final Function<R, T> fallbackMapper;

    public FallbackKafkaDeserializer(
            final Deserializer<T> delegateDeserializer,
            final Deserializer<R> fallbackDeserializer,
            final Function<R, T> fallbackMapper
    ) {
        this.delegateDeserializer = delegateDeserializer;
        this.fallbackDeserializer = fallbackDeserializer;
        this.fallbackMapper = fallbackMapper;
    }

    @Override
    public T deserialize(final String topic, final byte[] data) {
        if (data == null) {
            return null;
        }

        final SerializationException originalException;
        try {
            return delegateDeserializer.deserialize(topic, data);
        } catch (SerializationException e) {
            originalException = e;
        }

        final R fallback;
        try {
            fallback = fallbackDeserializer.deserialize(topic, data);
        } catch (SerializationException e) {
            e.addSuppressed(originalException);
            throw e;
        }

        return fallbackMapper.apply(fallback);
    }

}

That enables consumers to start working with the new schema, even though they may still receive records using the old schema.


Sth we have in old Eclipse - double click on tab/feature title

Type: Feature Request
When I double click e.g. Console tab in Eclipse, this Console expands to entire window.
After second double click, things are going back to previous state.
Today dbl click to e.g. Terminal header just collapses it, we still have "V" arrow for collapsing.
VS Code version: Code 1.73.1<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

duplicate https://github.com/microsoft/vscode/issues/47661


Blog app: add devise

Blog app: add devise
In this branch,
I  @aubinleyoung, @Donmark2k ,  and @Johnadibe implement the following;

Build a web app that requires the user to log in  with a combination of email and password..
Use devise gem for authentication.

Thank you @andersonlebon for your review 👍


Operations on Set/Map/List lose concrete type information

This is a follow-up to issue #871. I'm still seeing this problem on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Basically anytime a method such as filter or map or concat is used on a Set for example, it returns an Iterable. This means I have to litter my code with casts to Set to reassure the typescript compiler. This is very bad because every cast is a potential bug later on when code around the cast is updated.
I could also use toSet() and the likes, but it's extra runtime work which should not be necessary. And the code is still polluted by all those calls, trying to get back to the concret type.
How to reproduce:
Set<string>().map(a => a) === typeof Set<string>;

Hi @lwouis
I had the same issue and decided to use toSet() for right now.
By checking type definitions we can see that in version 4 this will no longer be an issue, but in version 3 List extends Iterable, where actually methods filter and map are defined
map<M>(
      mapper: (value?: V, key?: K, iter?: /*this*/Iterable<K, V>) => M,
      context?: any
    ): /*this*/Iterable<K, M>;

But I might be wrong 🙂

Unfortunately this is a known problem with v3 but is fixed in the v4 release candidates


Dependency Problems. -Module not found, Toggle.JS

Hi,
I am receiving missing module errors upon running my project while using this wrapper.
My project is based on React and no webpack/compiler has been used.
-Module not found, Toggle.JS, modules missing etc.
I like to check if the error is due to my react project not using any compiler?

Same problem

Module not found: Can't resolve 'material-ui/Toggle'

What version of material-ui are you using?
If you are using v3 then you will have the import error you are receiving. The new file paths start with  @material-ui/core which does not match the import paths in this package.
The package has fallen a little behind with upgrading to the new version of material-ui.
Hope this helps

I found out that they have a new prerelease version 5.0.0-Beta.3 that upgrades imports to the the newest version of MUI. you can see the release here: https://github.com/erikras/redux-form-material-ui/releases


only set upstreamTsContext.AlpnProtocols to 'istio' in ISTIO_MUTUAL mode

context: https://github.com/istio/istio/issues/6928

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ijsnellf
Assign the PR to them by writing /assign @ijsnellf in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2ad85ef3a04ff3170b564736ee722949ef5b5b12
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

/assign @costinm @hklai , could you pls take a look ? looks like merge to master requires 'merges-blocked-needs-admin' now, let me know if you think it's better to check in this PR into 1.0 branch.

Rebase to release-1.0 branch

@quanjielin looks like this is needed in 1.0. The easiest way is to click on the edit button next to the PR title, and then change the base from master to release-1.0.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
08046de65baee2420cbf9a13147072cf4d986fb3
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
08046de65baee2420cbf9a13147072cf4d986fb3
link
/test istio-unit-tests

prow/istio-presubmit.sh
08046de65baee2420cbf9a13147072cf4d986fb3
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

rebase got messed up(took master changes yesterday), will close this one and open another one.


Could you explain the variable 'data' in main_cls.py line 77. Thanks.

It's a dummy input for PyTransformer to build model graph. You can change it to whatever you want with dimensions 4 (batch, channel, height width) .

Ok, I got it. Thanks a lot.
| |
刘子力
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 12/16/2019<EMAIL_ADDRESS>wrote：
It's a dummy input for PyTransformer to build model graph. You can change it to whatever you want with dimensions 4 (batch, channel, height width) .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry for bother you again. I don’t understand the operation in relation.py line61-78. And why some relations are deleted from ’tmp’?
| |
刘子力
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 12/16/2019<EMAIL_ADDRESS>wrote：
Ok, I got it. Thanks a lot.
| |
刘子力
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 12/16/2019<EMAIL_ADDRESS>wrote：
It's a dummy input for PyTransformer to build model graph. You can change it to whatever you want with dimensions 4 (batch, channel, height width) .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry for bother you again. I don’t understand the operation in relation.py line61-78. And why some relations are deleted from ’tmp’? | | 刘子力 | |<EMAIL_ADDRESS>| 签名由网易邮箱大师定制 On 12/16/2019<EMAIL_ADDRESS>wrote： Ok, I got it. Thanks a lot. | | 刘子力 | |<EMAIL_ADDRESS>| 签名由网易邮箱大师定制 On 12/16/2019<EMAIL_ADDRESS>wrote： It's a dummy input for PyTransformer to build model graph. You can change it to whatever you want with dimensions 4 (batch, channel, height width) . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

I apply layer equalization to those at least 3 consecutive conv_layers are connected without branching. Since there is no such structure in segmentation and classification model, It only affect ssd model (which i am currently testing).

Thanks for your answer. I have learned.
| |
刘子力
|
|
<EMAIL_ADDRESS>|
签名由 网易邮箱大师 定制
On 12/16/2019 18:24, jakc4103 wrote:
Sorry for bother you again. I don’t understand the operation in relation.py line61-78. And why some relations are deleted from ’tmp’? | | 刘子力 | |<EMAIL_ADDRESS>| 签名由网易邮箱大师定制 On 12/16/2019<EMAIL_ADDRESS>wrote： Ok, I got it. Thanks a lot. | | 刘子力 | |<EMAIL_ADDRESS>| 签名由网易邮箱大师定制 On 12/16/2019<EMAIL_ADDRESS>wrote： It's a dummy input for PyTransformer to build model graph. You can change it to whatever you want with dimensions 4 (batch, channel, height width) . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I apply layer equalization to those at least 3 consecutive conv_layers are connected without branching. Since there is no such structure in segmentation and classification model, It only affect ssd model (which i am currently testing).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


[Bug] Readme doesn't mention what it does.

What is this project? What does it do? :)

hi @emil-nasso it's an IRC library which can optionally spin off a stand-alone process for each IRC connection.


Update README.md

Extend readme with simple explanation what this software does.

@nvtkaszpir Than you so much for improving the documentation!
Next time, I will merge quicker… too many other things got into my way…

not a problem, was merged faster than expected ;)


Linter improvements

Hey @jbonzo, is there an action here? I can likely take it over. If not, can we close this out?

I'll close.


copr: Add vectorize rand

Signed-off-by: Rustin-Liu<EMAIL_ADDRESS>PCP #5751

What have you changed?
Add vectorize rand.
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
None
Does this PR affect tidb-ansible?
None
Refer to a related PR or issue link (optional)
#5751
Benchmark result if necessary (optional)
None
Any examples? (optional)
None

@sre-bot  /run-all-tests

The last thing is to make a PR in https://github.com/tikv/copr-test and trigger the integration-copr-test here

@sre-bot  /run-integration-copr-test copr-test=pr/99

Have you created the copr-test pr?

Thank you, passed.

/run-integration-copr-test copr-test=pr/99

/run-integration-copr-test copr-test=pr/99

@Rustin-Liu Thanks for the interest! Could you implement rand_with_seed first? rand and rand_with_seed uses the same algorithm (but with different seed) in TiDB, so that you need to ensure that their algorithm is the same in TiKV as well. Otherwise the distribution character and the cryptography character may be different (since they are PRNGs), which may lead to some problems.

Thanks for the interest! Could you implement rand_with_seed first? rand and rand_with_seed uses the same algorithm (but with different seed) in TiDB, so that you need to ensure that their algorithm is the same in TiKV as well. Otherwise the distribution character and the cryptography character may be different (since they are PRNGs), which may lead to some problems.

The buildin already implement rand_with_seed and it use same algorithm with rand.
So I think I can implement rand_with_seed later.

@breeswish The buildin already implement rand_with_seed and it use same algorithm with rand.
So I think I can implement rand_with_seed after rand.

That builtin has not ever been enabled before, so you may not rely on it.

@breeswish The buildin already implement rand_with_seed and it use same algorithm with rand.
So I think I can implement rand_with_seed after rand.

That builtin has not ever been enabled before, so you may not rely on it.

Thank you. Got it.

You won't get the extra 50 points if you commit it in the same PR. I suggest you add tests cases for rand with seed in utils first, in this PR. And then make a PR with rand_with_seed based on this branch.

You won't get the extra 50 points if you commit it in the same PR. I suggest you add test cases for rand with seed in utils first, in this PR. And then make a PR with rand_with_seed based on this branch.

Thank you. Because breeswish  said I should implement the rand_with_seed first, so I add the rand_with_seed on this branch.

And your implementation of rand_with_seed is incorrect. There is a subtle difference between how it handles Constants and ColumnRefs

@sre-bot /run-integration-copr-test copr-test=pr/99

And your implementation of rand_with_seed is incorrect. There is a subtle difference between how it handles Constants and ColumnRefs

I reset it to only implement rand.  I will try to implement rand_with_seed after this pr.

@breeswish  PTAL~
I will try to implement rand_with_seed after this pr.  Because both of rand and rand_with_seed have to use util fn get_rng, so I need implement rand_with_seed after this pr.

And your implementation of rand_with_seed is incorrect. There is a subtle difference between how it handles Constants and ColumnRefs

Could you please give me some examples or suggestions for handle ColumnRefs?

I will try to implement rand_with_seed after this pr. Because both of rand and rand_with_seed have to use util fn get_rng, so I need implement rand_with_seed after this pr

IMO, you can implement and merge Rand with seed first

Could you please give me some examples or suggestions for handle ColumnRefs?
Thank you very much.

you can check if it is a columnef in meta_ctor where you have access to original expr; store a Some(RefCell) if it's constant or None if it's columnref.

@sre-bot /run-integration-copr-test copr-test=pr/99

Please add these test cases from MySQL for rand_with_seed because they're deterministic behavior
rand(0)
0.15522042769493574
0.620881741513388
0.6387474552157777
0.33109208227236947

rand(-1)
0.9050373219931845
0.37014932126752037
0.13563467109169314
0.5677254223895496

rand(1)
0.40540353712197724
0.8716141803857071
0.1418603212962489
0.09445909605776807

I think this may require you to refactor your random algorithm. Here are the snippets I copied from MySQL source code:
// definition of rng
struct rand_struct {
  unsigned long seed1,seed2,max_value;
  double max_value_dbl;
};

// gen()
double my_rnd(struct rand_struct *rand_st)
{
  rand_st->seed1= (rand_st->seed1*3+rand_st->seed2) % rand_st->max_value;
  rand_st->seed2= (rand_st->seed1+rand_st->seed2+33) % rand_st->max_value;
  return (((double) rand_st->seed1) / rand_st->max_value_dbl);
}

// create rng
void randominit(struct rand_struct *rand_st, ulong seed1, ulong seed2)
{                                               /* For mysql 3.21.# */
  rand_st->max_value= 0x3FFFFFFFL;
  rand_st->max_value_dbl=(double) rand_st->max_value;
  rand_st->seed1=seed1%rand_st->max_value ;
  rand_st->seed2=seed2%rand_st->max_value;
}

// for seed by arg
void Item_func_rand::seed_random(Item *arg)
{
  /*
    TODO: do not do reinit 'rand' for every execute of PS/SP if
    args[0] is a constant.
  */
  uint32 tmp= (uint32) arg->val_int();
  randominit(rand, (uint32) (tmp*0x10001L+55555555L),
             (uint32) (tmp*0x10000001L));
}

// for seed by time
randominit(&sql_rand,(ulong) server_start_time,(ulong) server_start_time/2);

We'll also fix the behavior of  TiDB later.

@breeswish  @andylokandy  I create a draft for Rand implement. Do you have any suggest？
And I am confusing about how to handle overflow station, should we warning it in ctx or just return an err?

mysql> select rand(9223372036854775807)
0.9050373219931845

mysql> select rand(-1)
0.9050373219931845

mysql> select rand(9223372036854775808)
0.15522042769493574

mysql> select rand(0)
0.15522042769493574

where<PHONE_NUMBER>854775807 is i64::max_value()

@sre-bot /run-integration-copr-test copr-test=pr/99

@sre-bot /run-integration-copr-test copr-test=pr/99

We have three places to test in this PR: the Rng struct, the rand() rpn function and the rand_with_seed rpn function. I suggest to test them like that:

For MySQLRng struct

test MySQLRng::new() returns rngs that gen() different values on the first call, and the gen() returns different values with the same rng on several calls.
test MySQLRng::new_with_seed() with concrete test cases, eg. rand(0/-1/1/9223372036854775808), and test their results from the first call and second call also.

For rand() and rand_with_seed() rpn function

copy tests above separately, (tests of MySQLRng::new() for rand() and MySQLRng::new_with_seed() for  rand_with_seed()). And add null case for  rand_with_seed().

We have four places to be tested in this PR: the Rng struct, the rand() rpn function and the rand_with_seed rpn function. I suggest to test them like that:

For MySQLRng struct

test MySQLRng::new() returns rngs that gen() different values on the first call, and that the gen() returns different values with the same rng on several calls.
test MySQLRng::new_with_seed() with concrete test cases, eg. rand(0/-1/1/9223372036854775808), and test their results of the first call as well as the second call.

For rand() and rand_with_seed() rpn function

copy the tests above separately, (tests of MySQLRng::new() for rand() and MySQLRng::new_with_seed() for  rand_with_seed()). And add null case for  rand_with_seed().

I have a question about test<PHONE_NUMBER>854775808, because this value is over flow i64 how  we test it? Use i128 and convert it to i64?

I have a question about test<PHONE_NUMBER>854775808, because this value is over flow i64 how we test it? Use i128 and convert it to i64?

Oh, I made the mistake. You can ignore it.

I'm concern about the builtin parts. And the rest look good to me. This PR indeed took you too much time  :-(   I'm sorry.

/test

/test

@breeswish @TennyZhuang PTAL

Hi, could you also change the non-vectorized version to align with your latest change? We can award you 200 points in total in one PR, for you have done {rand, rand_with_seed} for {vec, non_vec}.

I think I can implement it  tomorrow.

PTAL~

/test

@breeswish PTAL

/award-point 200

PTAL~

/merge


Issues with input package generation

I've found a few issues with the input packages
Inputs can generate an invalid terraform variable when the manifest file defines a dot separated fields such as "data_stream.dataset".
https://github.com/elastic/integrations/blob/e234ffb8ad8dd70cc73a216cc2ed329620485077/packages/log/manifest.yml#L27
I was able to resolve this by inserting this after line 258 of fleet-terraform-generator/internal/module/generate.go
	// Replace any periods with underscore so that a valid TF variable is generated.
	if strings.Contains(name, ".") {
		name = strings.ReplaceAll(name, ".", "_")
	}

Inputs with dot separated fields such as "data_stream.dataset" as the JSON key causes terraform to fail.
https://github.com/andrewkroh/terraform-module-fleet/blob/ffa10318d2e4dd57010233ac0e2f1b6f84ceac92/fleet_integrations/log_logs_logfile/module.tf.json#L54
Terraform generates the following error:
│ Error: Reference to undeclared resource
│
│   on ../../fleet-terraform-generator/out/log_logs_logfile/module.tf.json line 56, in module.fleet_package_policy:
│   56:       "data_stream_variables_json": "${jsonencode({\n  custom = var.custom_yaml\n  data_stream.dataset = var.data_stream_dataset\n  paths = var.paths\n  processors = var.processors_yaml\n  tags = var.tags\n})}",
│
│ A managed resource "data_stream" "dataset" has not been declared in module.integration_log_logs.

Wrapping this in quotes prevents this error but I haven't been able to figure out how to update the code to do this.

I know there's nothing you can do for this one but for the SQL Metrics it looks like there is an issue with the integrations manifest.yml causing the generator to fail to create the variable for data_stream.dataset.

I pushed two changes:

b0b04bdd75a990ef749986573e1e2570b6fef882 Quote variable names containing dots in expressions

cb99e50177e627673164fb2201e9557e23a3e6c3 Replace dots with underscores in TF module variables

I know there's nothing you can do for this one but for the SQL Metrics it looks like there is an issue with the integrations manifest.yml causing the generator to fail to create the variable for data_stream.dataset.

Yeah, that looks like a bug in that the manifest.yml does not contain a data_stream.dataset variable. Whereas other input packages do declare the variable. The package even tries to use the variable at https://github.com/elastic/integrations/blob/b723d42a8282f5e00caa865ff020932da21d511f/packages/sql_input/agent/input/input.yml.hbs#L11.

Created an issue at https://github.com/elastic/integrations/issues/6529


TESTCOV: Sputnik Factory

Draft PR for Sputnik Factory test coverage.
Related to #118 #119 #120 #121 #122 #123 #124 #125
Recomendations are very welcome.

Currently working on #121


Problem with the views, controller and routes

Laravel CRM Version: last version
PHP Version: 8.1

Description:
Hello, if I install the crm-starter project, I do not have any view, controller or route to modify, how can I download the complete project with all the data.

The laravel-crm is a vendor package, do you have experience working with Laravel packages? You can overwrite any vendor file if you need, there are few approaches to this however. I've been looking at adding some information in the docs for this. Otherwise you can searcg google for "how to overwrite vendor files in laravel"
Also you can publish views from any package and customize them.


Meetup events shows no pics

Problem and Investigation
Images from meetup.com are not showing on the new /events page anymore

@M-ZubairAhmed You seem to be using a place holder image when the regex for img src doesn't yield any results.

Also, when I checked the events data, their description doesn't have any img tag.
We should check out the API docs of meetup again :3

That's a potential issue.

@buoyantair yes can you check with meetup api the recent one?
, as before we use to get the complete html doc along with image tags hence the above structure.

@M-ZubairAhmed Yeah noticed :3 Will check and fix this err :3


[Question] How can I continue running the script that comes after a request is succesfully, for the repeat requests?

First, I must say I love this package. It works very well for me.
However, I have one question:
How can I continue the 'success' part of the ajax script after the request is succesfully done after a reconnect?
    $.ajax({
    	type: "PATCH",
        url: api_address + "patchable"
        dateType: "JSON"
    	}).done(function(){
    		done_actions(this)
        }).fail(function(jqXHR, textStatus, errorThrown){
    	if (jqHXR.status == 0){
    		// not connected offline-js will retry after succesful connection. Keep everything as it is.
    	}else{
                    // Probably validation error or so
        	showPopupMessage(jqXHR, 'danger');
            }

        }).always(function(){
        	thiscontainer.removeClass('spinner');
        });

Now, after reconnect the ajax request is done succesfully. But the done_actions are never called. Is it possible to call those, depending on the ajax request (I have multiple)?

Since this was asked in https://github.com/HubSpot/offline/issues/81 2 years ago and not answered - i don't think there is a solution to this problem right now. AFAIK offline,js only saves the payload you are sending, nothing else. So the actual answer you might get from the Server is transmitted to the browser, but no one's home to catch it ...

Bummer, this kinda seems like a big deal.

It is. I'd suggest using offline.js just for checking the online/offline status und not for catching actual requests. As long as Service Workers aren't supported by all major browsers, the only viable solution seems to

check if online with offline.js and if offline
save the payload of the request via localStorage/indexedDB (or using something like localForage.js)
wait until connection is restored and fire the stored requests one by one

This actually works quite well and is not that complicated. I use AppCache to store the page files at the moment, which is deprecated and should be replaced by Service Workers in the future.


Preparing React Accessible Accordion for React 18

It seems that broadly speaking it will be compatible, but our generated ids will have to use the useId hook,

it's even more important in React 18 because of how our streaming server renderer delivers HTML out-of-order. Solutions that may have worked previously, like using a counter to generate IDs, don't work in 18.0 because you can't rely on a consistent sequence. (cite)

We were using the counter to generate IDs approach, so we'll have to adopt useId.
Because we have React as a peerDep we'll have to detect if useId is available and fallback to our existing counter approach.
As such these autogenerated ids will change in a release of RAA for React 18.
Are there any other issues that we should address for React 18?

We are also looking for React 18 support for accordions. @holloway is there a plan to merge this PR #342?

@trigunam yes, within a week if testing goes well.

@trigunam This has been published as 5.0.0. Please let me know if this works for you.

It's working now. Thank you @holloway

Great, thanks!


fix(SequentialChain): only passes output

Context in this issue

https://github.com/hwchase17/langchain/issues/4116

see comment on issue!


Release Google.Cloud.BigQuery.Connection.V1 version 2.4.0

Changes in this release:
New features

Add cloud spanner connection properties - serverless analytics (commit 3b22371)
Add cloud spanner connection properties - database role (commit 3b22371)

Created release for Google.Cloud.BigQuery.Connection.V1-2.4.0


Issue with topbar and typeahead

I'm not completely sure if this is an issue that I should post here, but after many hours of trying to solve it by overwriting CSS I've decided to post it here. I'm sorry if it's just me doing something wrong.
The issue is that if I use a typeahead within a topbar, it ends up looking like this: http://i.imgur.com/ArzwzrE.png
Here's a plunker in which it happens: http://plnkr.co/edit/PsjaLIq4obXHlaPYKZqW

Sorry this is something you'll need to to override with CSS because that's the issue here. Foundation's topbar CSS is particularly aggressive and we don't include any additional CSS in our library.

Alright, I'll keep trying then, thanks!


a little new here, could use some help.

i just ran through all the steps and set up the server but I don't know how to connect to the server correctly or create an account on it, I'm using profanity as my xmpp client.
edit: also am i able to make multi user rooms and if so how?

Since profanity does not support in band registration (IBR) yet you might want to create an account with another client like gajim or Conversations. Afterwards connecting with profanity should work.


[FEATURE] more keys in event::Keys

Is your feature request related to a problem? Please describe.
I'd like to use the Alt key to show my menubar.
Describe the solution you'd like
Adding more key presses to the event and the Key's enum
Describe alternatives you've considered
Using different keys

is there a way to directly access the backend im using? Im using crossterm, it seems like this would be a lower level feature and it would involve a lot of conditional compiling. But it feels like its worth exploring


Fix travis tests

Was getting an error when attempting to retrieve go vet. I don't know why we were doing this, since it appears to already be present. Other repos weren't retrieving it anymore.
Upstream libraries from AppC discovery and some of its dependencies were no longer Go 1.3 compatible. We don't use 1.3 either. So removed testing on 1.3 and added in testing on 1.6.

@zquestz @alextoombs

@jpoler @klobucar

LGTM

@alextoombs had to make a go vet fix to proc for go tip...

go vet getting some teeth!
On Wed, May 18, 2016 at 5:01 PM, Ken Robertson<EMAIL_ADDRESS>wrote:

@alextoombs https://github.com/alextoombs had to make a go vet fix to
proc for go tip...
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/apcera/util/pull/38#issuecomment-220192876

--
Apcera, Inc
San Francisco, CA
(908) 625-6950


3ed85e70

My apologies if this was submitted already, teal square at the bottom of the third example seems to have been forgotten

Agreed. I don’t see any simple rules that wouldn’t require adding pink bars to either side of the cyan square.


Implement include search path

Problem Description
At the moment ASM6502 opens all included files relative to the current working dir. This leads to problems for example in the following case:
main.a65:
.include "subdir/a.i65"

subdir/a.i65:
.include "b.i65"   ; b.i65 in the same directory as a.i65

In this case b.i65 can not be loaded because it is searched in the directory of main.a65 and not within subdir.
Solution
This is tricky to solve in a standard-conformant C89 way without resorting implementation specific functions like POSIX, because the C standard has no knowledge of a) directory separators and b) directory change functions.
What it has is getenv to read environment variables. The most portable solution would be to introduce an environment variable ASM6502 including a search path. This PATH could then be searched if a file is not found in the current directory.
What remains are the different directory separators under different operating systems. The safest way to provide  it is to define it via operating system specific makefile and pass it to the C compiler. Path scanning is a bad idea, because as an example RISC OS consideres . as path separator, clashing with the file extension under other operating systems.

The common procedure for this is:
"file.inc"  <- look in local dir first, then use search path
  <file.inc>  <- use the search path
Search path is norally a system path (i.e. an include/ folder within the package install path), or a path
based on a combination of the system path, the $PATH environment variable, and/or a compiled-in
list of folders.
I have a preliminary version of this, where
- use current dir first (for "" includes)
   - use application path (installation path of the assembler), both the main folder as well as the
     processor folder
Added will be the inclusion of the VASM_INCLUDE environment variable.
Fred
On Thursday, April 13, 2023 at 05:35:42 AM EDT, Bernd Böckmann @.***> wrote:
Problem Description
At the moment ASM6502 opens all included files relative to the current working dir. This leads to problems for example in the following case:
main.a65:
.include "subdir/a.i65"
subdir/a.i65:
.include "b.i65"   ; b.i65 in the same directory as a.i65
In this case b.i65 can not be loaded because it is searched in the directory of main.a65 and not within subdir.
Solution
This is tricky to solve in a standard-conformant C89 way without resorting implementation specific functions like POSIX, because the C standard has no knowledge of a) directory separators and b) directory change functions.
What it has is getenv to read environment variables. The most portable solution would be to introduce an environment variable ASM6502 including a search path. This PATH could then be searched if a file is not found in the current directory.
What remains are the different directory separators under different operating systems. The safest way to provide it is to define it via operating system specific makefile and pass it to the C compiler. Path scanning is a bad idea, because as an example RISC OS consideres . as path separator, clashing with the file extension under other operating systems.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Smaller repo?

The current repository is 1gb. It would be nice to have an option to clone a lot less.

You can create a shallow clone of this repository using the depth parameter of git clone
example to only get the last 5 revisions:
git clone --depth=5 https://github.com/openZH/covid_19.git

This should reduce the size drastically if you don't need the history.

Awesome ! Thanks !


feat: drop env vars for v1

Fixes #N/A
Description
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

15 of 16 (93.75%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 78.053%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/operator/operator.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/provisioning/scheduling/nodeclaim.go
2
89.13%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.02%

Covered Lines:
8827

Relevant Lines:
11309

💛  - Coveralls


[Feature] Support EVA-MAE style

Support train vit-Base in EVA-MAE style.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

Working in progress. I am pretraing the model.

Preparing links for ckpts

Please fix the UT


CRI support specify snapshotter during pod creation instead of a global config

What is the problem you're trying to solve
Our K8s has a mixed deployment of Kata and Runc containers, where Kata containers runs untrusted workloads and Runc for the trusted workloads. For the best performance and security reason, we use devmapper snapshotter for Kata containers.
However, with current containerd-cri implementation, snapshotter config is global, which means we cannot specify certain pods (trusted) to continue using overlayfs while only Kata containers to be on devmapper. This limitation causes the following issues:

Slower image pulling: Devmapper backed image unpacking is 50% slower than OverlayFS, this will slow down many of the trusted pods image pulling. https://github.com/containerd/containerd/discussions/6625
Unnecessary data disk partition reservation: instead of making use of the OS boot disk the for overlayfs snapshot data, now we need to reserve a relatively large disk partition for devmapper thin pool for only a small set of untrusted images, most of the disk spaces allocation is a waste of cost/space.
Slower snapshot prepare when SandboxChange (usually after a node reboot), which causes slower container start up. https://github.com/containerd/containerd/issues/6119
Device mapper is generally harder to operate (device thin pool data allocation is not released until the device is remove or run fstrim, if a container keeps writing + deleting to rootfs it will eventullay run out-of-space) and less mature and we would like to adopt in minimal scope.

Describe the solution you'd like
Pod annotation can carry snapshotter type to tell CRI. It seems to be a containerd CRI limitation, for example, we can use ctr run --snapshotter devmapper/overlayfs. Similar to runtimeClass, it would be great to support dynamic snapshotter override with Pod annotations.
Will Containerd consider to accept such extended feature or something along the line?
Additional context
No response

Option 1: Extend the runtime class to support snapshotters

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
runtime_type = "io.containerd.runc.v2"
snapshotter = "default"
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc-stargz]
runtime_type = "io.containerd.runc.v2"
snapshotter = "stargz"

Option 2: Use a pod annotation like io.kubernetes.cri.snapshotter. The allowlist of the snapshotter should be defined in /etc/containerd/config.toml .

cc @ktock

SGTM

option 1: SGTM.
cc @dmcgowan

One limitation I can see with Option 1 is that the RuntimeHandler is not passed in from the PullImageRequest (PodSandboxConfig  does not have it, either). So seems to me there's not an easier way to do Option 1 without Kubelet support?

IMO Option 2 is also a good way for such purpose and does not conflict with Option 1 in if the future  CRI client supports passing the RuntimeHandler, e.g. override priority annotation > runtimeConfig.Snapshotter > defaultConfing.Snapshotter.

@AkihiroSuda @mikebrow @jterry75 @fuweid Does this general direction sound reasonable to you? If yes, I can draft a proposal on how the pod annotation should be handled.
type PullImageRequest struct {
	// Spec of the image.
	Image *ImageSpec `protobuf:"bytes,1,opt,name=image,proto3" json:"image,omitempty"`
	// Authentication configuration for pulling the image.
	Auth *AuthConfig `protobuf:"bytes,2,opt,name=auth,proto3" json:"auth,omitempty"`
	// Config of the PodSandbox, which is used to pull image in PodSandbox context.
	SandboxConfig        *PodSandboxConfig `protobuf:"bytes,3,opt,name=sandbox_config,json=sandboxConfig,proto3" json:"sandbox_config,omitempty"`
	XXX_NoUnkeyedLiteral struct{}          `json:"-"`
	XXX_sizecache        int32             `json:"-"`
}

type PodSandboxConfig struct {
	// Metadata of the sandbox. This information will uniquely identify the
	// sandbox, and the runtime should leverage this to ensure correct
	// operation. The runtime may also use this information to improve UX, such
	// as by constructing a readable name.
	Metadata *PodSandboxMetadata `protobuf:"bytes,1,opt,name=metadata,proto3" json:"metadata,omitempty"`
	// Hostname of the sandbox. Hostname could only be empty when the pod
	// network namespace is NODE.
	Hostname string `protobuf:"bytes,2,opt,name=hostname,proto3" json:"hostname,omitempty"`
	// Path to the directory on the host in which container log files are
	// stored.
	// By default the log of a container going into the LogDirectory will be
	// hooked up to STDOUT and STDERR. However, the LogDirectory may contain
	// binary log files with structured logging data from the individual
	// containers. For example, the files might be newline separated JSON
	// structured logs, systemd-journald journal files, gRPC trace files, etc.
	// E.g.,
	//     PodSandboxConfig.LogDirectory = `/var/log/pods/<podUID>/`
	//     ContainerConfig.LogPath = `containerName/Instance#.log`
	//
	// WARNING: Log management and how kubelet should interface with the
	// container logs are under active discussion in
	// https://issues.k8s.io/24677. There *may* be future change of direction
	// for logging as the discussion carries on.
	LogDirectory string `protobuf:"bytes,3,opt,name=log_directory,json=logDirectory,proto3" json:"log_directory,omitempty"`
	// DNS config for the sandbox.
	DnsConfig *DNSConfig `protobuf:"bytes,4,opt,name=dns_config,json=dnsConfig,proto3" json:"dns_config,omitempty"`
	// Port mappings for the sandbox.
	PortMappings []*PortMapping `protobuf:"bytes,5,rep,name=port_mappings,json=portMappings,proto3" json:"port_mappings,omitempty"`
	// Key-value pairs that may be used to scope and select individual resources.
	Labels map[string]string `protobuf:"bytes,6,rep,name=labels,proto3" json:"labels,omitempty" protobuf_key:"bytes,1,opt,name=key,proto3" protobuf_val:"bytes,2,opt,name=value,proto3"`
	// Unstructured key-value map that may be set by the kubelet to store and
	// retrieve arbitrary metadata. This will include any annotations set on a
	// pod through the Kubernetes API.
	//
	// Annotations MUST NOT be altered by the runtime; the annotations stored
	// here MUST be returned in the PodSandboxStatus associated with the pod
	// this PodSandboxConfig creates.
	//
	// In general, in order to preserve a well-defined interface between the
	// kubelet and the container runtime, annotations SHOULD NOT influence
	// runtime behaviour.
	//
	// Annotations can also be useful for runtime authors to experiment with
	// new features that are opaque to the Kubernetes APIs (both user-facing
	// and the CRI). Whenever possible, however, runtime authors SHOULD
	// consider proposing new typed fields for any new features instead.
	Annotations map[string]string `protobuf:"bytes,7,rep,name=annotations,proto3" json:"annotations,omitempty" protobuf_key:"bytes,1,opt,name=key,proto3" protobuf_val:"bytes,2,opt,name=value,proto3"`
	// Optional configurations specific to Linux hosts.
	Linux                *LinuxPodSandboxConfig `protobuf:"bytes,8,opt,name=linux,proto3" json:"linux,omitempty"`
	XXX_NoUnkeyedLiteral struct{}               `json:"-"`
	XXX_sizecache        int32                  `json:"-"`
}

I agree with option 1 is a good long term goal. I am a fan of hanging more configuration off of runtime handler, then the user can set what runtime class to use on their pod spec. Regarding the runtime handler name not being passed on image pull, there was some discussion in this KEP about setting a kubernetes.io/runtimehandler annotation on pods to specify this, which would then be passed via the annotations field on CRI's ImageSpec. I think the idea was to potentially add a dedicated field on ImageSpec for this in the future, but at least annotations allows us to experiment.
I don't remember how far along this got, though. @marosset do you know if kubernetes.io/runtimehandler will be set automatically on the pod based on the runtime class used, or is it currently up to the user to set it manually?
Option 2 could work, but if we're going to require the user to set an annotation either way, it seems better to just have them set the runtime handler if we want runtime class based configuration in the future.

@kevpar Option 1 SGTM, to overcome the runtime handled not passed in for PullImage API, I propose the following:

Snapshotter is specified in containerd config.toml for each runtime, e.g. kata-qemu-devmapper
Use experimental annotation for the runtimeClass, the annotation key is specified in containerd config.toml
For all CRI APIs, we check the existence of the annotation, and get/set corresponding snapshotter.

Does this sound good to folks? I actually already had an internal POC that was working fine, if there's no object to the proposal, I can draft a PR, or if anyone else wants to start working on it, please let me know.

@kevpar Option 1 SGTM, to overcome the runtime handled not passed in for PullImage API, I propose the following:

Snapshotter is specified in containerd config.toml for each runtime, e.g. kata-qemu-devmapper
Use experimental annotation for the runtimeClass, the annotation key is specified in containerd config.toml
For all CRI APIs, we check the existence of the annotation, and get/set corresponding snapshotter.

Does this sound good to folks? I actually already had an internal POC that was working fine, if there's no object to the proposal, I can draft a PR, or if anyone else wants to start working on it, please let me know.

This sounds good to me. I posted on Slack the other day about this proposal, and there didn't seem to be disagreement on the approach.
I was planning to take a look at implementation, but if you have a working PR already feel free to post and I'm be happy to take a look/collaborate.

@kevpar @AkihiroSuda @mikebrow @fuweid
Hi all, I submitted a PR https://github.com/containerd/containerd/pull/6899 to support this feature according to Option1 and related discussions. The high level ideas are listed o the PR description. Could you help review and feel free to give any feedback/comments. Thanks!

@kevpar @AkihiroSuda @mikebrow @fuweid

Per discussion in https://github.com/containerd/containerd/pull/6899, the following is a list of open tasks for fully close this issue but are not blocker for the PR to merge:

[ ] Add CI integration tests for the new feature
[ ] A KEP to drive the collaboration between kubelet and CRI, this KEP includes details regarding passing runtime via PullImageRequest, snapshot usage aggregation and Kubelet GC handling etc.
[ ] After kubelet is able to pass the runtime down to CRI, deprecate the experimental
[ ] Refine the snapshotter validation logic per https://github.com/containerd/containerd/pull/6899#discussion_r874599711

(Sorry for joining the party late)
One concern I have is along the lines of the discussion in https://github.com/containerd/containerd/pull/6899#issuecomment-1123019135, i.e. kubelet cannot bookkeep the imageFs usage correctly when multiple snapshotters are involved.
Kubernete's KEP-4216 is making sure that kubelet can pull/detect/delete the images with their Runtime Class being considered (i.e. almost all concerns in @shuaichang 's checklist above), but I don't see any effort mentioning in the KEP the bookkeeping of the imageFS. Specifically, kubelet currently only reads the imagefs usage of containerd's global snapshotter ([1] [2]), so if we pull a lot of images thru a non-global snapshotter, the disk usage will be ignored.
I cannot think of any easy way to address this, mostly because kubelet's cri_stats_provider doesn't know which pods are using which snapshotter. Probably need a separate KEP or increase the scope of KEP 4216. I will bring thing up in KEP-4216 as well.
[1] https://github.com/containerd/containerd/blob/bbac058cf31359d7ca7b2a98f48bce086b817dcf/internal/cri/server/images/imagefs_info.go#L54
[2] https://github.com/kubernetes/kubernetes/blob/26923b91e8cbd2d409e5d177ddd509429b76cb35/pkg/kubelet/stats/cri_stats_provider.go#L401


[mesheryctl] Unhandled error in system logs when Meshery is not running

Description
With Meshery not running and the current context of meshconfig set to "platform: docker", mesheryctl system logs does not gracefully handle this situation (see logs).
Expected Behavior

Docker platform: Prompt user with a question to start Docker.
Kubernetes platform: Prompt user with a question to deploy Docker.

Screenshots/Logs
➜  ~ mesheryctl system logs
Starting Meshery logging...
Error: exit status 255
Usage:
  mesheryctl system logs [flags]

Flags:
  -h, --help   help for logs

Global Flags:
      --config string    config file (default location is: /Users/lee/.meshery/config.yaml)
  -c, --context string   (optional) temporarily change the current context.
  -v, --verbose          verbose output
  -y, --yes              (optional) assume yes for user interactive prompts.

Environment:

Meshery Version: v0.5.11
Context platform: docker

@leecalcote Could not reproduce the issue either. We do check if Meshery is running before we try to get the logs for both platforms.

Regarding system logs, I will assume that I neglected to use ./mesheryctl and used mesheryctl instead (or something like that). I have updated the test case status above.

Hmm. This is odd. The exit code above must have come from somewhere...

@leecalcote Still having this issue?

It would be nice not to show that logging is starting when Meshery isn't running (so, skip the first message, if Meshery isn't running.
$ mesheryctl system logs
Starting Meshery logging...
No logs to show. Meshery is not running.

It would be nice not to show that logging is starting when Meshery isn't running (so, skip the first message, if Meshery isn't running.
$ mesheryctl system logs
Starting Meshery logging...
No logs to show. Meshery is not running.

It would be nice not to show that logging is starting when Meshery isn't running (so, skip the first message, if Meshery isn't running.
$ mesheryctl system logs
Starting Meshery logging...
No logs to show. Meshery is not running.

Hey @leecalcote , would love to help out here! Any guidance on how can i proceed would help? 🙂

@verma-kunal You have to just change the UX to what is mention in the comment.

@verma-kunal You have to just change the UX to what is mention in the comment.

Umm, i am actually not sure if i understood this right! It would really help if you could explain this a bit more, because I am new to the project & have not yet started using meshery
Thanks 🙂

I'll try & reproduce this issue! Would reach out if stuck anywhere! 🙂

@verma-kunal Instead of showing "Starting Meshery logging..." right away, wait to see if Meshery is running and then show it. Else, show that Meshery is not running and there are no logs to show.
It would be just moving the logging code after the check.

I am not sure why, its been stuck here since 15min, after stopping Meshery 😅

The way we check if Meshery is running might be shortsighted. It may not actually be an indicator of the running status of Meshery.
// @piyushsingariya @hexxdump

I am not sure why, its been stuck here since 15min, after stopping Meshery 😅

@verma-kunal can you dig a little deeper where exactly the code get stuck??

@verma-kunal can you dig a little deeper where exactly the code get stuck??

Yeah, so when i view the logs when Meshery is up & running, its showing as soon as i run the command!

But, when Meshery is stopped by mesheryctl systerm stop & then i try to view the logs, its taking a lot of time for me, to produce any result! (Like mentioned above)
Not sure if thats because of my system RAM (though its 8GB) or something else!

Nice, that's also a part of the issue that you need to fix now!

Nice, that's also a part of the issue that you need to fix now!

Oh, sure! Would love to help
So, as I am new to this project & the technologies and have just setup Meshery on my system, so some resources would definitely help me here to understand how to go about this.
The Meshery CLI guides may help here right?
Any other suggestions would mean a lot
Thanks

Also - https://docs.meshery.io/project/contributing/contributing-cli

Thanks for sharing! Will refer these

Hey all, i am actually traveling to college right now, so it might take me a bit of time to set things up, before i start working on this issue!
Would love to stick to this & work upon, but if you all feel to give a chance to any other folks from the community, i'll support that decision as well 🙂
Thank you!

Hey Can I work on this ?

Hey @chinmaym07 , thank you for doing this!
it would be great if we could have a conversation on how you solved this issue, if thats alright with you.
Really interested to know & would help me to gain more knowledge of mesheryctl 🙂
Let me know your thoughts!


docs: Add ReleaseNotes for release

ReleaseNotes.txt is required for each release.
Basically two releases each year, like in May and November.
Signed-off-by: Zhangfei Gao<EMAIL_ADDRESS>Signed-off-by: Zhiqi Song<EMAIL_ADDRESS>

/lgtm


import application json file

users should be able to import application json file generated with different version of dovetail UI, then fixed errors if any

Is this a FE issue? Closing for now


cmdb error after upgrading to 4.0.0

Steps to reproduce

Upgrade to 4.0.0
Remove .cme from home directory
Scan a network
execute cmedb

Command string used
cmedb
Platform
Kali Linux x64 (Non-VM)
Detailed issue explanation
After Upgrading to CME 4.0.0 and running a scan, trying to enter into the cmedb to review results, an error occurs.
Traceback
Traceback (most recent call last):
File "/usr/local/bin/cmedb", line 11, in
load_entry_point('crackmapexec==4.0.0.dev0', 'console_scripts', 'cmedb')()
File "/usr/local/lib/python2.7/dist-packages/crackmapexec-4.0.0.dev0-py2.7.egg/cme/cmedb.py", line 119, in main
cmedbnav.cmdloop()
File "/usr/lib/python2.7/cmd.py", line 112, in cmdloop
import readline
File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93, in import
result = _import(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/readline.py", line 6, in
from pyreadline.rlmain import Readline
File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93, in import
result = _import(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pyreadline/init.py", line 12, in
from . import logger, clipboard, lineeditor, modes, console
File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93, in import
result = _import(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pyreadline/clipboard/init.py", line 13, in
from .win32_clipboard import GetClipboardText, SetClipboardText
File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93, in import
result = _import(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pyreadline/clipboard/win32_clipboard.py", line 37, in
import ctypes.wintypes as wintypes
File "/usr/lib/python2.7/dist-packages/gevent/builtins.py", line 93, in import
result = _import(*args, **kwargs)
File "/usr/lib/python2.7/ctypes/wintypes.py", line 19, in
class VARIANT_BOOL(_SimpleCData):
ValueError: type 'v' not supported

So this seems to be an error with Gevent ,which leads me to belive it hasn't been installed correctly.
Did you install CME in a virtualenv?

Getting a similar error here on the latest Kali VM:
root@kali:/opt# cmedb
Traceback (most recent call last):
  File "/usr/local/bin/cmedb", line 11, in <module>
    load_entry_point('crackmapexec==4.0.0.dev0', 'console_scripts', 'cmedb')()
  File "/usr/local/lib/python2.7/dist-packages/crackmapexec-4.0.0.dev0-py2.7.egg/cme/cmedb.py", line 118, in main
    cmedbnav = CMEDatabaseNavigator(config_path)
  File "/usr/local/lib/python2.7/dist-packages/crackmapexec-4.0.0.dev0-py2.7.egg/cme/cmedb.py", line 31, in __init__
    self.workspace = self.config.get('CME', 'workspace')
  File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
    raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'CME'

Follow the instructions at https://github.com/byt3bl33d3r/CrackMapExec/issues/174 for solution.

Cosing since I can't reproduce and no updates.


Allow users to select City Name in hotels page

Go to Navigation bar, click on Travel
Select Hotel Booking
Allow users to select a city

What to do?

On the top, there is a bar showing Showing Mumbai Hotels.
When user clicks on that bar, open a dialog ( popular with a list of popular cities from our server )
Also add a search bar on that dialog that searches for the city starting with the typed name

Endpoints to use :

get-all-cities
get-city-by-name/city_prefix

I would like to work on this.

Sure :)


accounts is borrowed for 'info

12 | #[program]
   | ^^^^^^^^^-
   | |        |
   | |        `__accounts` dropped here while still borrowed
   | borrowed value does not live long enough
   | lifetime `'info` defined here
   | argument requires that `__accounts` is borrowed for `'info`

I don't why life time error happen when I add 'b  on lib.rs
pub fn battle_log<'b: 'info, 'c: 'info, 'info>(
        ctx: Context<'_, 'b, 'c, 'info, BattleLog<'info>>,
        battle_info: BattleInfo,
        warrior_card_collect_mints: Vec<Pubkey>
    ) -> Result<()> {
        battle_log_process(ctx, battle_info, warrior_card_collect_mints)
    }

I want to extract the logic of creating an account into a function, and then it will report an error, asking me to add the relationship between b and info.

The result is written in this way, but it cannot pass the limit of the problem I posted.

This is due to how internal codegen works. However, there is a draft PR (https://github.com/coral-xyz/anchor/pull/3340) to make all lifetimes of Context the same to make it easier for people to work with it.

solution:
don't add 'info in the front of params with context. like payer: &'info Signer<'info> .
Right example:
fn process_warrior_cards_usage<'info>(
    warrior_card_usage_data_len: usize,
    warrior_card_usage_ai: &'info AccountInfo<'info>,
    collect_mint: Pubkey,
    attacker: Pubkey,
    program_id: &Pubkey,
    payer: &Signer<'info>,
    rent_lamports: u64,
    system_program: &Program<'info, System>
) -> Result<()> {


Register Notification model on Admin

Having the Notification model on Admin can help users in order to inspect if they are being generated accordingly, as a query tool.

@fgmacedo , am I supposed to implement this or you've already started working on it :sweat_smile: ?
I am just making sure so that we don't have to work on the same feature.

@v1k45 You  can go on! I'm trying to integrate django-notify-x into an existing project, so I can start to see how the things are working. Until now I only saw the tests running. This may take a while.

Yeah, will do it tomorrow, it's almost 3:00 am here.

Take your time, here is 7:00 pm.

@fgmacedo please add the .mo and .po files if necessary :).


Enhancement to RaSCSI Android app

Info

Which version of Pi are you using:
Which github revision of software:
Which board version:
Which computer is the RaSCSI connected to:

Describe the issue
Just curious if an option to shutdown the Pi can be added to the Android RaSCSI app?  Think that would be easier than going to the web interface everytime.

@timmcross The feature already exists. It's the bottom right icon in the server information.
By the way, please note that this site is not a support site for the RaSCSI control app. The control app is a separate project.


Updated readme

There was old 10.5.1 version used in example, updated to 10.6.0.
Invalid engine was imported in example, changed from ejsEngine to etaEngine.

Hey @gjuoun, are you still developing this project? I would like to keep it up to date with latest oak.


Introduce Id data-type and eliminate the boilerplate PShow: Ident

The boilerplate should be eliminated if we introduced an Id data-type:
> data Id v = Id {name :: Name,  unid :: Int }
And then we can have:
> data ChanIdT = ChanIdT
> type ChanId = Id ChanIdT

See instance PShow Ident in \sys\defs\src\TxsShow.hs

See also #213


Moves to an .xcworkspace so we don't imbed subprojects

We may need to release PINCache and update the cartfile to point to it before we can merge this.

After this commit PINRemoteImage can't be install via carthage, because it has duplicate PINOperation in it


Incorrect import in windicss.vue example

There is an incorrect import in the windicss.vue component.
This is currently making the build fail.
import { reactive } from '@vue/reactivity'
import { onMounted, ref, watch } from 'vue'

should be
 import { onMounted, ref, watch, reactive } from 'vue'

Yeah,  right! I'll fix it.

fixed @Armand-Lluka


unable to pass DataFrame or RDD to elasticsearch using Spark  !!

Hi,
I am not able to use "saveToES" function cause when  i open pyspark prompt by passing  bin/pyspark --jars ../elasticsearch-hadoop-2.1.2.jar command .
I am not able to import org.elasticsearch.spark.* module.Can someone guide how to do that in python code using spark and elasticsearch connector
I run the coomand as :   saveToEs(df, "offers/product");

@gaurav6351 For help and questions, please use the forum not the issue tracker.
Thank you,


QUESTION : Source map not config?

Hi, Thanks for this awesome boilerplate! I try like 100 and yours is nearly best!
One thing I miss and can't make it work is sourcemap, even I add
    devtool: process.env.NODE_ENV === 'development' ? 'cheap-module-eval-source-map' : 'source-map',

But no sourcemap is create, maybe I miss something?
Thanks!

Now I know what I miss (always after asking lol), I forget to add it to both dev and prod config!
Cheers


OnIceConnectionChange state

Hi, i have an uwp app with webrtc and i want to connect wowza streaming server with PeerConnection. in this case app send offer and server return answer , then i set remotedescription and nothing is happen. app is running but streaming is not working. i checked PeerConnection Events and i found this; last OnIceConnectionChange is "Checking". But i think it should be "connected".
Thanks your help

Did you ever get this working with Wowza?  We've had good results with Janus but have not tested with others.

Issue moved to webrtc-uwp/webrtc-uwp-sdk #35 via ZenHub


Disable automatical preview mode warning

Neovim version (nvim -v | head -n1)
NVIM v0.9.5
Operating system/version
Elementary OS 5.1 Horus
How to reproduce the issue

Toggle the automatical preview mode
Get an obtrusive warning
have to skip the warning each time it's toggled on and off

Expected behavior
The mode is toggled silently or at the very least get notified in a non-obtrusive manner (provide a call-back to define that behavior even)
Actual behavior
Got a warning whenever automatic preview mode is toggled

You can disable auto preview and type p to toggle it manually.

I would like to still use auto previews but without this somewhat nagging warning.

I will show the msg at the bottom except your ch is equal to 0. And I don't think your attention will be at the bottom if you are focusing on the preview window.

I don't think your attention will be at the bottom if you are focusing on the preview window.

It does show up at the bottom, but I'd have to press Enter every time I toggle auto preview on and off.

bottom except your ch is equal to 0.

Sorry. I'm not following

but I'd have to press Enter every time I toggle auto preview on and off.

No need to type any keys for me, it's an issue with your config.

That's the current behavior

h 'shortmess'


#53 needs to be reopened... sharer.php is deprecated

the title actually says it all...
=> https://github.com/Julienh/Sharrre/issues/53

Dear,
I left  you a message  on  your voice mail, have you listened to  it already? If not, here is the link  http://kyrdevofa.edge-guard.com/e6nhnzmx
Faithfully, tadakute


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
66201e46a066d1ce8524d5a5c558945cb83891b0
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Refact] Make time-dependent HamEvo use PyQ

Edit: previous issue text:

Currently the calculation of HamEvo is being done directly in the convert_ops.py file of each backend, ignoring the same code that exists in PyQTorch / Horqrux. This was done as a temporary step before a larger effort to clean up the HamEvo calculation.
Related to #134.

The above is mostly solved already: https://github.com/pasqal-io/qadence/pull/531
However the logic for the time-dependent HamEvo is still done in the convert_ops.py. Once  https://github.com/pasqal-io/pyqtorch/pull/228 is done, we can look into moving also the time-dependent logic.

Assigning this to you @dominikandreasseitz since that's what you just started doing 😄

Completed with PR #568


SOG;PF Fuse Timed Claymore Compat Issue

The Fuse Timed Claymore and variants don't function properly.
They are set to be activated by command and so will wait to start their 10 second timer until after you trigger it.
The intended function is to place the Claymore and run as it autostarts the timer when placed.
A few fixes I see are hiding the 10 Second Fuse Claymore(s) and just adding the "timer" trigger to the Remote Claymore(s), changing  ACE_Explosives_Placeable = x to 0 & useAction = x to 1 so the vanilla system is used for it, or doing some wizardry to make it so you can place the 10 Second Fuse Claymore(s) and activate them immediately (ie. ACE Menu>Explosives>Place>10 Second Fuse Claymore>Place>Interactions>Insert Fuse/Activate).

Realized I don't think this is the right Github


document runtime/container engine

separate readme
link to readme for all generated solutions
Docker/Multipass recommended
describe podman/colima, with caveats that there are known issues
eventually: how to run locally (no container/vm)
eventually: how to run on a jump server
eventually: how to deploy in airgapped environment

First pass of RUNTIMES.md at:
https://github.com/cloud-native-toolkit/automation-solutions/blob/main/common-files/RUNTIMES.md
^^ Individual readmes for each solution will be updated with Docker/Multipass instructions, and link to the shared runtimes doc for additional detail.
Ultimately, the TROUBLESHOOTING.md and RUNTIMES.md files will be replaced by links to the operator guide, once it goes live.
I also added both runtimes and troubleshooting docs to the operator site at:
https://github.com/cloud-native-toolkit/site-operator-guide/tree/main/docs/resources

All solutions in automation-solutions have been updated:
https://github.com/cloud-native-toolkit/automation-solutions/pull/199
Each solution should be regenerated as automated testing is added.
Details: https://gsicsi.slack.com/archives/C039DRPL77U/p1660840741635939


import tensorflow.contrib.rnn.python.ops.core_rnn_cell_impl as rnn_cell ImportError: No module named core_rnn_cell_impl

Tensorflow 0.12.1
Traceback (most recent call last):
File "kgcvae_swda.py", line 13, in
from models.cvae import KgRnnCVAE
File "/home/ubuntu/NeuralDialog-CVAE/models/cvae.py", line 8, in
import tensorflow.contrib.rnn.python.ops.core_rnn_cell_impl as rnn_cell
ImportError: No module named core_rnn_cell_impl
Which tensorflow version works fine with it?

I am able to run the code using tensorflow (0.12.1). I will do a pass on the code in the next few days to make it compatible with whichever latest version of Tensorflow. You could also change the import line to import the correct rnn_cell based on your local TF version.

@alifirst  The code is updated to 1.3.0.


Error: Couldn't find Type of name Mutation in the GraphQL Schema.

I'm having problems making queries and creating / updating / deleting things in django graphql through the graphql plugin of vuex orm.
From the interface provided by django to execute queries, I can perfectly use my mutations and consult any particular data or any collection of them.
The error I receive is the following:

As far as I understand the plugin, this error is given in the schema constructor but i don't understand why.
I'm going to write an example of how I create an object called "TipoProducto" from the django interface:
mutation myMutation {
 createTipoProducto(input: {nombre:"Pizza", descripcion:"foobar"}) {
     tipoProducto {nombre, descripcion}
 	status
 }
 }

This code will return the object with its attributes and a status 200 if it was successful.
My model in vuex orm:
import { Model } from '@vuex-orm/core';
import Product from './Product'

export default class TipProd extends Model {
    static entity = "tipProds"

    static fields () {
        return {
            id: this.increment(),
            nombre: this.attr(''),
            descripcion: this.attr(''),

            producto: this.hasMany(Product, 'tipProd_id')
            }
        }
    }

This is the method I try to use to create a new object "TipoProducto":
    methods: {
             async register (tipProduct) {
                await TipProd.insert({
                    data:
                        tipProduct
                });
                const tipProd = TipProd.query().last()
                await tipProd.$mutate({ name: 'createTipoProducto' });
    }

where data: tipProducto are the attributes taken from a form
I can not find the way that vuex orm correctly structured the query to create an object. What am I doing wrong?
I have apollo dev tools installed but it does not register any query or any other operation since it fails before being made.
I am aware that some methods could fail if I do not respect the naming conventions for schema operations from Django but it is not the case, I am not even able to do a simple fetch
Sorry for the english and thanks.

I had a silly mistake in my API, where I wrote Mutations instead of Mutation


Pharokka Database Install Failed.

I was installing pharokka but for some reason I can not install the databases with this command: install_databases.py -d
So I manually downloaded the databases from the following link:  https://zenodo.org/record/7563578/files/pharokka_v1.2.0_database.tar.gz(pharokka) But I still can not make it work. Is there any way that I can complete database installation and start using pharokka?
Since I am new to the bioinformatics I am not exactly sure what to do after downloading databases manually.
Your help is much appreciated.

Hi Sujeet,
Would you be able to give me some more information about what you tried? Maybe screenshots if that is ok?
Assuming you have put the manually downloaded database in your current directory (it is called pharokka_v1.2.0_databases), you will need to add
-d pharokka_v1.2.0_databases
to your pharokka command.
e.g.
pharokka.py -i input.fasta -o output -d pharokka_v1.2.0_databases
Otherwise, you could specify the full path to wherever the database is:
e.g.
pharokka.py -i input.fasta -o output -d ~/pharokka_v1.2.0_databases
George

Hi George,
Thank you so much for your quick reply. I just realized the mistake I was doing and I tried the solution you mentioned and it worked. I realized the the problem was because of my limited understanding.
Anyway thank you so much for your help.

No problem Sujeet, I hope you find the output useful.
I was in your shoes not too long ago - the more bioinformatics you do the better you get :)
George


Support Rocky Linux and add workarounds for issues with OFED installations

This is likely to trigger a major version as Rocky Linux requires Ansible 2.11 or later as previous versions classify Rocky as an Unknown distribution.
Included in this merge request:

ofed_grub_backup to disable/enable backing up grub config, as the backups fail if the files do not exist
ofed_nobest to add the --nobest flag to package installs when there's a dependency conflict with libibverbs
Checks and manages the openibd service
Basic configuration of /etc/infiniband/openib.conf to work-around kernel module issues
Documentation for these things.

Thanks very much. Looks good to me.

We don't have any released versions of this role. Shall we go for 1.0.0?

We don't have any released versions of this role. Shall we go for 1.0.0?

I tagged the commit prior to the merge with 1.0.0 and tagged a 2.0.0 release with your commits.


Define how to collect statistics

Description
We would like statistics as to how many and how large files are scanned on behalf of a given app owner.
This task includes defining how to best identify these numbers and  create a script that does so.
Additional Information
No response
Tasks

[ ] identify key metrics
[ ] Create script
[ ] Document script in Altinn Pedia

Acceptance Criterias
No response

Not prioritized


Clarify the AWS RequestHandlers in the documentation

Describe the bug
I'm using Spring Cloud Function 3.0.6.RELEASE and am referring to the documentation about the AWS Request Handlers. For both the FunctionInvoke and the SpringBootRequestStreamHandler it states that both are the most generic ones:

The most generic is ...

In the same section, there is also a hint about the environment variable of FUNCTION_NAME to specify the function name if you have multiple beans of type Function. While trying to develop a Lambda function with Spring Cloud Function AWS I realized that this environment variable is not working with the FunctionInvoke (here only SPRING_CLOUD_FUNCTION_DEFINITION works) handler but only with SpringBootRequestStreamHandler.
Is my assumption correct and can I file a PR to maybe clarify this section for other (new) developers?

I see your point

thanks for the fast fix 👍


Add protocol field, and make name and description be pub visible

Adding a protocol field will allow Workflow consumers (such as L2 Oracle) to apply app-specific post-processing with respect to the protocol string.
Making name and description public helps with logging the received workflow in a concise way.

Closing, found a much better alternative for L2 Oracle, can re-open if needed!


Allow different resolutions in x and y direction for ol.source.ImageStatic

fixes #2844 based on the work references in the e-mail to ol3-dev there

@ahocevar I think this is now truly ready, thanks for your comments already

Yep, looks right now. Thanks, and please merge!


contractcourt: catch error when no historical bucket exists

For older nodes, this bucket was never created, so we'll get an error if
we try and query it. In this commit, we catch this error like we do when
a given channel doesn't have the information (but the bucket actually
exists).
Fixes #6155

Fixed a test failure in TestFetchHistoricalChannel now that the bucket not found error is never returned for a fresh node.


ISSUE-1412 Receive Page split into horizontal pager

The design is not 100% pixel perfect because didnt have time, but I guess its quite enough for a demo. Also scroll is not broken because i disabled the horizontal pager one so u can still swipe between bottom pages.

@HonzaR whats the next coarse of action? Should I fix up the PR or?

@HonzaR whats the next coarse of action? Should I fix up the PR or?

Yes, let's update the PR to resolve the review comments, if you like? Make sure to fix the CI actions reports. I'll approve the CI run for you then. Thank you.

@HonzaR  u can recheck, but probably lint will fail - even tho I am using project code style

@HonzaR u can recheck, but probably lint will fail - even tho I am using project code style

Hi @Milan-Nerevar, Thank you for the update commits! The static code analysis checks are still failing. It's a good approach to check your changes locally before pushing. See the predefined Gradle tasks in our Setup documentation. Would you like to fix those too?


Consider changes related to native DBT_PROJECT_DIR support in dbt-core

Follows from:

https://github.com/dbt-labs/dbt-core/pull/6659 (merged but not released, as of March 9, 2023)

I don't know if any changes are needed, especially because we want to be mindful of preserving backwards compatibility.
As of now, we have:
https://github.com/meltano/hub/blob/main/_data/meltano/utilities/dbt-snowflake/dbt-labs.yml#L86-L88
settings:
// ...
- label: Projects Directory
  name: project_dir
  value: $MELTANO_PROJECT_ROOT/transform

This almost maps to DBT_PROJECT_DIR except that the name of the plugin is dbt-snowflake (or similar), so the mapped env var would be something like DBT_SNOWFLAKE_PROJECT_DIR.

Correction: our source code does already use this env var (same name).
https://github.com/meltano/dbt-ext/blob/a53bf00b766190d092f07840c047b51db08f6d1f/dbt_ext/extension.py#L43-L46
And this PR merging today will ensure it gets mapped from the related setting names:

https://github.com/meltano/hub/pull/1156

@tayloramurphy and @pnadolny13 - I don't think there's anything for us to do here, but just wanted to call it out in case you see something I don't see.
As of the next dbt-core release, DBT_PROJECT_DIR will be parsed natively, meaning for those versions of dbt that support it, we will no longer need to cd into the directory or pass --project_dir.


feat(containers): add support for 0.22.0-alpha2

upgrades Zeebe version to 0.22.0-alpha2
adds ZeebeContainer#withAdvertisedHost

bors r+


pythonPackages.pysnooper: init at 0.1.0

Motivation for this change
pysnooper is a python logging library, providing quick logging via decorator
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Should be ok know, could you re-check. Also thanks for patience.

Re-pushed with suggested changes

@GrahamcOfBorg build python2.pkgs.pysnooper python3.pkgs.pysnooper

Pushed again

@seqizz https://github.com/cool-RR/python_toolbox/issues/3 seems to have been resolved.

Switched to fetchFromGitHub to get the latest release. Yet not sure how to test this :confused: I can't see the tests on pysnooper build when I try, since there is no way to say "force rebuild" on nix-shell or nix-build as far as I can find.

Pushed 0.1.0

@grahamcofborg build pythonPackages.pysnooper python3Packages.pysnooper

I think github is confused, suggested change is already done..
I wish I could've helped maintaining the nixos repo more, since I can see the MR/issue pile :no_mouth: But you can see the quality of my commits already :grimacing:

After this much time, I guess I know a bit more what I am doing :smiley:
Upgraded to latest version, also built fine on my box.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/81

@GrahamcOfBorg build python27Packages.pysnooper python37Packages.pysnooper python37Packages.python-toolbox


#13404: Add data parallel support for lenet  model

Ticket
Link to the github Issue
Problem description
Add data parallel implementation for lenet model - WIP
What's changed
Added data parallel support for lenet on n300 along with demo, e2e, device and test perf.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Do you have CI links?

@tt-rkim
We don't have CI links at the moment. I've been updating the code by replacing torch ops with ttnn ops, which are supported in the latest main branch for single-device implementations. However, I'm encountering issues when trying to run it in a data parallel setup. Once these issues are resolved, we can provide the CI links.

OK

Please message when done

Still blocking on you. Thanks

We are currently blocked on this  due to a reshape issue - #15422 in the model and have not triggered the CIs furthur.

OK thanks. Please message in #tt-metal-pr-review-requests when ready

Currently blocked due to reshape issue: https://github.com/tenstorrent/tt-metal/issues/15422 (expected to be fixed by this week, as mentioned by @naif)
cc: @boris-drazic , @uaydonat , @tt-rkim


Make [MXCrypto decryptEvent] asynchronous

This feature needs to be done after event storage improvement refactoring.

It has been done in https://github.com/matrix-org/matrix-ios-sdk/pull/204

Synchronousness is currently required for:

decrypting events in MXEventTimeline both for live and past messages
decrypting not sent messages
decrypting in some cases the last message for room summaries

Basically, the change will impact all methods using decryptEvent: