KAFKA-3689 - process only distinct connectionIds within processDisconnected()

@ijuma discovered a possible scenario in which connectionQuotas may be doubly-decremented
This PR intends to remove that possibility by first filtering out any duplicate connectionIds. This way each

Thanks for the PR. A few comments:

It would be great to describe a scenario where we could end up with duplicate ids in the disconnected list (a test would be even better).
Depending on the scenario for 1, it may be better for Selector.disconnected to be a Set instead of List.

I'd be interested to hear Jun's thoughts about this.

Thanks @ijuma

I believe this can happen when quickly killing then restarting clients. This could put connectionID into the disconnected list as failedSends once at the end of a poll(). If the same connectionID is added to the disconnected list again then we could see the same id twice.

True, that is a much better solution, I'll try to get that to you today.

I have requested a sit down with Jun to review my observations on this 1657. I'll update both PRs with my notes on that


Allow trackers to have manually set SLAs

This PR allows trackers to have manually set SLAs by setting a custom label.
Closes OSIDB-3374.

Yes Ondro, that is the desired usecase.


Support for PAWAA API

Because of a recent discussion over at the TM1 Forum the idea came up to support the Planning Analytics Administration Server-side Agent API with tm1py. I personally think that is a great idea.
It could help greatly to administrate multiple tm1 instances.
What do you guys think?
Example of available instance information

Possibility to create and update and delete instances

More information on the IBM website.

Hi @scrumthing,
I don't think this is something we would add to TM1Py. We really want to focus on the server REST API and I am not sure accessing the PA agent is documented or officially supported.


Update README.md

added a new letter "Q" and a new tool quiky.email

Hello @wanoo21 , Sorry this list is just for AI Directories, However you can submit your tool on Awesome AI Tools!


Upgrade to z2jh 1.2.0

This is the latest stable version. We want to eventually
move to 2.0 (with some breaking changes) but let's get to
the latest non 2.0 stable version first
Ref https://github.com/2i2c-org/infrastructure/issues/1055

Looked at the very nicely maintained changelog here: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/main/CHANGELOG.md#120---2021-11-04. Seems good :) I'm testing this on staging, and then deploying after.

When upgrading z2jh, it is important to check if there is anything we need to check in the images used for it to work with the new version of z2jh. 1.1.x to 1.2.x doesn't have any such changes though.


Problem with images on /doc/ai/nn/transformer/gpt/5/index

In https://gwern.net/doc/ai/nn/transformer/gpt/5/index#stanley-2023-section, when I click on any image to enlarge it, I see the base64 for the image rather than the image itself. Screenshot:

This is using Chromium on Arch Linux. I see the same behaviour on Firefox and Brave, though. Images on other pages work fine.

From what I can tell, the problem is that p.image-url is shown, which contains code.url, which contains the full URL for the image, which is specified as a long string of inline base64. On other images, the URL is still always shown as part of the Copy URL button, but the URL is assumed to be short enough that the button covers the screen.
So, I guess it would make sense to either replace the src attributes of the images on that page to use local image files, or have a system for detecting them as base64 and not showing the Copy URL button in those cases.

Should be fixed now, thanks.


Test onnx backend

add onnx backend test cases

Please don't merge this PR until I finish all the test cases.

ready to merge, please help check @nudles. And I removed the test cases for example models. I'll start a new Jira for it.


Test quiz section styled and alert added

The spacing and alert for not selecting any option and clicking to next question button has been added.

@tarunsinghofficial  okay sure

@tarunsinghofficial  Changes done!!


Color depends of altitude

Hi,
First, thanks for this awesome class to customize a MKPolyline.
I'm wondering if this is possible to add a gradient which depends of the altitude. Each points (lat/lng) of my polyline have an altitude value. The min altitude represents green color, the max altitude red color.
I don't find any information to do it. An idea ?
A rendering sample made with Google Map JS API

Thanks again.

Hi there! Thanks, it's so cool to see people using something I've made! I'm actually doing the exact thing you ask in one of my apps so I can help you on this one.  What you want to do is calculate a hue value for each point based on your elevation data, and create a gradient between the previous point's colour and the current point's colour in the drawMapRect function, for each part of the path.
Here's the class I made so you can see how I've done it. I might add it to this repo if it's something lots of people want.
 //
 //  PedalPathRenderer.swift
 //  Pedal
 //
 //  Created by Joel Trew on 24/04/2016.
 //

 import MapKit

 class PedalPathElevationRenderer: MKOverlayPathRenderer {

    var polyline : MKPolyline
    var elevations: [Int]
    var maxElevation: Int?
    var border: Bool = false
    var borderColor: UIColor?

    //MARK: Initializers
    init(polyline: MKPolyline, elevations: [Int]) {
        self.polyline = polyline
        self.elevations = elevations
        super.init(overlay: polyline)
        self.maxElevation = calculateMaxElevation()
    }

    //MARK: Override methods
    override func drawMapRect(mapRect: MKMapRect, zoomScale: MKZoomScale, inContext context: CGContext) {

        var baseWidth: CGFloat
        if zoomScale > 0.1 {
            baseWidth = self.lineWidth * 2
        } else {
            baseWidth = self.lineWidth / zoomScale
        }

        /*
         Set path width relative to map zoom scale
         */

        var firstColor:UIColor = UIColor(hue: self.getHueFor(elevation: elevations[0]), saturation: 1, brightness: 1, alpha: 1)
        var lastColor: UIColor = UIColor(hue: self.getHueFor(elevation: elevations[1]), saturation: 1, brightness: 1, alpha: 1)

        if self.border {
            CGContextSetLineWidth(context, baseWidth * 1.5)
            CGContextSetLineJoin(context, CGLineJoin.Round)
            CGContextSetLineCap(context, CGLineCap.Round)
            CGContextAddPath(context, self.path)
            CGContextSetStrokeColorWithColor(context, self.borderColor?.CGColor ?? UIColor.whiteColor().CGColor)
            CGContextStrokePath(context)
        }

        for i in 0...self.polyline.pointCount-1 {
            let point: CGPoint = pointForMapPoint(self.polyline.points()[i])
            let path: CGMutablePathRef  = CGPathCreateMutable()

            lastColor = UIColor(hue: self.getHueFor(elevation: elevations[i]), saturation: 1, brightness: 1, alpha: 1)
            if i==0 {
                CGPathMoveToPoint(path, nil, point.x, point.y)
            } else {
                let previousPoint = self.pointForMapPoint(polyline.points()[i-1])
                CGPathMoveToPoint(path, nil, previousPoint.x, previousPoint.y)
                CGPathAddLineToPoint(path, nil, point.x, point.y)

                CGContextSaveGState(context);
                let colorspace = CGColorSpaceCreateDeviceRGB()
                let locations: [CGFloat] = [0,1]
                let gradient = CGGradientCreateWithColors(colorspace, [firstColor.CGColor, lastColor.CGColor], locations)

                let pathToFill = CGPathCreateCopyByStrokingPath(path, nil, baseWidth, CGLineCap.Round, CGLineJoin.Round, self.miterLimit)
                CGContextAddPath(context, pathToFill)
                CGContextClip(context);

                let gradientStart = previousPoint;
                let gradientEnd = point;

                CGContextDrawLinearGradient(context, gradient, gradientStart, gradientEnd, CGGradientDrawingOptions.DrawsBeforeStartLocation);
                CGContextRestoreGState(context)
            }
            firstColor = UIColor(CGColor: lastColor.CGColor)
        }

        super.drawMapRect(mapRect, zoomScale: zoomScale, inContext: context)
    }

    /*
     Create path from polyline
     Thanks to Adrian Schoenig
     (http://adrian.schoenig.me/blog/2013/02/21/drawing-multi-coloured-lines-on-an-mkmapview/ )
     */
    override func createPath() {
        let path: CGMutablePathRef  = CGPathCreateMutable()
        var pathIsEmpty: Bool = true

        for i in 0...self.polyline.pointCount-1 {

            let point: CGPoint = pointForMapPoint(self.polyline.points()[i])
            if pathIsEmpty {
                CGPathMoveToPoint(path, nil, point.x, point.y)
                pathIsEmpty = false
            } else {
                CGPathAddLineToPoint(path, nil, point.x, point.y)
            }
        }
        self.path = path
    }

    private func getHueFor(elevation elevation: Int) -> CGFloat {
        let maxElevation = CGFloat(self.maxElevation ?? 50)
        let hue = CGFloat(elevation).map(from: 0...maxElevation+5, to: 0.0...0.4)
        return 0.4-hue

    }

    private func calculateMaxElevation() -> Int {
        return self.elevations.maxElement() ?? 0
    }

 }

 extension CGFloat {
    func map(from from: ClosedInterval<CGFloat>, to: ClosedInterval<CGFloat>) -> CGFloat {
        let result = ((self - from.start) / (from.end - from.start)) * (to.end - to.start) + to.start
        return result
    }
 }

Hopefully this will help you out with your issue. 😄

Joel

Ok good luck :) , you're welcome to share your solution here if you find a better way

@NasH5169 What's the solution, can you share it to me. Thanks


Refactor with more OOP

Refactoring around Task and Batch classes could simplify things, and make it practically possible to use temporary directories. Initial GIL paranoia wrt parallelisation led to slightly unwieldy current implementation.

Although writing decontamination statististics to a temporary location would be neat, I don't think this is worthwhile


Update TupleEngagementExample.tex.md

HTML image tags may need to be wrapped similar to this two examples
no need to merge this, but wanted to show sample.

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

doing the ![]( ) wrapping, you can see the tex.md renders into the proper tags as well.


Load Static Assets from CDN

Now all static site assets are loaded from cdn.llnl.gov.
Fixes #5

I'd like to get the vernsion numbering of ge cdn data for LLNL fixed up before I merge this just to make sure that we don't end up with a 404 at some point.


Permissions for deleting a file

The permissions necessary for deleting a file are inconsistent across platforms.

POSIX only requires write and execute permissions on the parent directory. The file's permissions do not matter.
Windows requires write permissions on the file itself. The permissions of the parent directory do not matter.

The permissions of the parent directory are also relevant for renaming a file on POSIX, but not on Windows.
The differences are exemplified by these two simple programs:
# File permissions
path = "foo"
File.touch(path)
File.chmod(path, :none)
File.delete(path) # works on POSIX, raises on Windows ("Permissions denied")

# Parent directory permissions
path = "bar/baz"
Dir.mkdir(File.dirname(path))
File.touch(path)
File.chmod(File.dirname(path), :none)
File.delete(path) # works on Windows, raises on POSIX ("Permission denied")

These differences are an obstruction to stdlib's portability goal.
However, they are based on intrinsic properties of the underlying operating systems.
Deviating from that may lead to surprising behaviour in a similar way as non-portable code does.
There's no clean way out, either way there need to be some compromises.
The POSIX semantics of requiring write permission to the parent directory make a lot more sense to me. Deleting a file is the inverse of creating one, which requires the same write permission on the parent directory. So I'm in favour of aligning Windows behaviour to POSIX.
But I'm not entirely sure this is the correct choice. Messing with the OS permission system in this way feels a bit sloppy.
There are two existing PRs for this:
#13462 adjusts Windows behaviour of File.delete to make the file writable in case it is readonly. This isn't exactly the same as POSIX behaviour. I suppose it won't work if the user is not allowed to remove the readonly attribute. And the permissions of the parent directory still wouldn't matter on Windows.
#9903 is a similar approach, though less elegantly, and it only affects FileUtils.rm_r.
I don't see a clear answer what's the best path of action. For making an informed decision, it would probably be helpful to see how other portable APIs handle these differences.

Ruby might not be the best example for portability because Windows support is somewhat of an afterthought.
But as a close relative, the equivalent Ruby programs are quite similar for comparison.
# File permissions
path = "foo"
File.write(path, "")
File.chmod(0o000, path)
File.delete(path) # works on both POSIX and Windows

# Parent directory permissions
path = "bar/baz"
Dir.mkdir(File.dirname(path))
File.write(path, "")
File.chmod(0o000, File.dirname(path))
File.delete(path) # works on Windows, raises on POSIX ("Permission denied")

It seem's that Ruby also overwrites the readonly permission on Windows, in the same way as proposed in #13462 (https://github.com/ruby/ruby/blob/c7067ed13d6cbe7fd8ba25418d2881f40fc4cbab/win32/win32.c#L7774C54-L7784). But it does nothing about parent-directory permissions.

Ruby might not be the best example for Windows-portability, but it's easy to compare because the sample programs are pretty similar:
# File permissions
path = "foo"
File.write(path, "")
File.chmod(0o000, path)
File.delete(path) # works on both POSIX and Windows

# Parent directory permissions
path = "bar/baz"
Dir.mkdir(File.dirname(path))
File.write(path, "")
File.chmod(0o000, File.dirname(path))
File.delete(path) # works on Windows, raises on POSIX ("Permission denied")

Ruby applies the same overwrite of readonly attribute (https://github.com/ruby/ruby/blob/c7067ed13d6cbe7fd8ba25418d2881f40fc4cbab/win32/win32.c#L7774C54-L7784) as in https://github.com/crystal-lang/crystal/pull/13462. But it does nothing about the parent directory permissions.

That's a good point. So the discrepancy is in the expression of permissions. They mean different things.
So I guess that makes SetFileAttributesW a reasonable choice.
Interestingly, the Windows explorer seems to have no problem with deleting a read-only file either. So I suppose it's probably doing the same thing. One more argument for that.
However del foo complains about permission denied.


Proposal: minimum grid scale parameter

Thank you very much for this package, @hunkim98! It's exactly what I have been looking for to create a pixel art editor with for my custom IDE. Doing a test implementation, I have come across a few issues and also some ideas for improvement, which I would like to share (and will create separate tickets for). Let me start with the following feature request.
When zooming out of your image, the grid takes up more and more space in relation to the actual pixels. At a certain scale, one can no longer make out the pixels at all, but only sees the grid. This becomes more apparent the bigger the image gets.
To solve this, I propose a parameter (perhaps called gridMinimumScale), which allows to set a minimum scale below which the grid gets automatically disabled.

@KR155E Thank you for your interest in our package! It is great that you are considering to use this library for your custom IDE. I would love to hear more about the IDE you are planning to create later on.
I also had similar thoughts on your proposal to make the grid invisible when the canvas is zoomed out to a certain level. I will definitely implement this as soon as I can. I am thinking of setting the gridMinimumScale inside the component directly (Users will not be able to set this gridMinimumScale).
I will look into other issues you have opened one by one. If there is an issue that you would like to solve on your own or need some explanation, please feel free to tag me.😃

That is great to hear, @hunkim98, thanks for your feedback.
The IDE I mentioned is called VUEngine Studio and is designed specifically for Nintendo Virtual Boy homebrew development with our own game engine. I would love to have an embedded pixel art editor to allow people to create graphical game assets in the right format right in the IDE, without having to rely on external graphic programs. Here's a screenshot of my current implementation of dotting.

Fascinating! I will give you updates on your requested features as I solve them one by one! I will definitely try your IDE too.


3.3.2 is no longer hosted on Maven Central

Tried to follow your install instructions and the plugin could not be found. After debugging it via mvnrepository, I found that 3.3.1 was the last version upload to mavenCentral.  Version 3.3.2 is available on plugins.gradle.org.
Unsure if it was intentional to switch repositories but if so, the README needs an update to include this repository instead of mavenCentral().
Otherwise we'll wait for your 3.3.2 version to show up on mavenCentral()

Sorry about that - it should be in Central shortly. It was pushed to central, the staging repository was closed, and then I got distracted and never hit the release button.


Wrong statement about "Use updated experience for classic settings where possible."

The setting "Use updated experience for classic settings where possible." is not on by default for new environments, or at least not all environments. All production and sandbox environments I've deployed in Canada over the last 6 months have had this setting off by default, including two I deployed literally today.

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

ID: d941b293-2873-2c2c-6f44-9a4c28aa98e5
Version Independent ID: e704ed8d-7769-b9ff-7028-d684044788c0
Content: Manage behavior settings - Power Platform
Content Source: power-platform/admin/settings-behavior.md
Service: power-platform
Sub-service: admin
GitHub Login: @sericks007
Microsoft Alias: sericks

Thanks for your comment, @justyrofoam. This issue has been assigned to the doc author for review.


Enhance CV and MV idempotency via deterministic ID generation

Description
This PR enhances the Covering Index (CV) and Materialized View (MV) write operations by introducing deterministic ID generation. Deterministic IDs uniquely identify each document in a CV/MV based on its data, enabling idempotency. This ensures consistent results during retries or restarts of index refreshes. By eliminating duplicates, this approach maintains data integrity and operational consistency, even in failure scenarios.
Algorithm
The ID generation logic follows the precedence below:

User-Provided ID Expression

Enables users to define custom ID generation logic based on specific columns or expressions.
If empty, no ID column is generated, which is useful for testing or disabling the feature.

Aggregated MV

If MV queries involves aggregation, IDs are generated using SHA-1 on concatenated output columns.
SHA-1 is chosen for balancing collision resistance, performance, and space efficiency, compared to other options in Spark such as  hash, xxhash64, md5 and sha-2.

Default Behavior

Otherwise, no ID column is generated and idempotency is not guaranteed.

Side Effects
This deterministic document ID approach introduces these impacts and requires further exploration to determine if a better solution is viable for long-term scalability and performance.

Spark Computation Overhead

For aggregated MV, the SHA-1 hash and string concat operations are performed on all output columns for each row.

OpenSearch Ingestion Overhead

Each document write involves a document ID lookup to identify and deduplicate existing documents.

OpenSearch Document Size

The SHA-1 hash used for document IDs (160 bits) consumes more space compared to OpenSearch's default UUID-based IDs (128 bits).

Possibility of Collision

While the likelihood of collisions with SHA-1 is extremely low (e.g., negligible even at PB-scale data), a collision could result in data loss by overwriting an existing document.

Documentation
https://github.com/dai-chen/opensearch-spark/blob/support-covering-index-and-mv-idempotency-rework/docs/index.md#create-index-options
Related Issues
https://github.com/opensearch-project/opensearch-spark/issues/88
Check List

[ ] Updated documentation (docs/ppl-lang/README.md)
[x] Implemented unit tests
[ ] Implemented tests for combination with other commands
[x] New added source code should include a copyright header
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM. A couple of points to emphasize in the documentation:

The id_expression generates a unique _id to be used during OpenSearch write operations with upsert semantics, guaranteeing idempotency.
It would be beneficial to provide more examples about the common and available id_expression options supported.

Sure, will update the documentation. Meanwhile will block this PR merge until the follow-up PR for testing dashboard query. Thanks!

I'm testing with AOSS and found time-series collection seems not support create/index request with doc ID specified. If this is true, that means the approach in this PR as well as Flint skipping index (both relies on doc ID) won't work. Will double confirm.

Using the AOSS time series collection, it was confirmed that the following exception is thrown when attempting to create or update a document with ID:
24/12/19 23:58:46 WARN TaskSetManager: Lost task 39.0 in stage 3.0 (TID 3447) ([2600:1f14:38a0:a801:1a95:8524:74ed:54a8] executor 4): java.lang.RuntimeException: failure in bulk execution:
[0]: index [flint_glue_default_mv_idempotent_test_1], id [51fd2d0929ebb39c79ee9492ba064f654e56709c], message [OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document ID is not supported in create/index operation request]]]
[1]: index [flint_glue_default_mv_idempotent_test_1], id [53b97544fb9831e0714a12ca243930539af06c3d], message [OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document ID is not supported in create/index operation request]]]
[2]: index [flint_glue_default_mv_idempotent_test_1], id [5896fb03aa01e3962215b19eddefa07a8764fc55], message [OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document ID is not supported in create/index operation request]]]
[3]: index [flint_glue_default_mv_idempotent_test_1], id [1ec78f9c430d1e7dfc682b76b0f8e27eb7e3c32d], message [OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document ID is not supported in create/index operation request]]]
[4]: index [flint_glue_default_mv_idempotent_test_1], id [fcd5f0c77810f6382ff00ec942e7f1fcb529d61f], message [OpenSearchException[OpenSearch exception [type=illegal_argument_exception, reason=Document ID is not supported in create/index operation request]]]
	at org.opensearch.flint.core.storage.OpenSearchWriter.flush(OpenSearchWriter.java:64)
	at shaded.flint.com.fasterxml.jackson.core.json.WriterBasedJsonGenerator.flush(WriterBasedJsonGenerator.java:983)
	at org.apache.spark.sql.flint.json.FlintJacksonGenerator.flush(FlintJacksonGenerator.scala:257)
	at org.apache.spark.sql.flint.FlintPartitionWriter.write(FlintPartitionWriter.scala:64)
	at org.apache.spark.sql.flint.FlintPartitionWriter.write(FlintPartitionWriter.scala:24)
	at org.apache.spark.sql.execution.datasources.v2.DataWritingSparkTask$.write(WriteToDataSourceV2Exec.scala:493)
	at org.apache.spark.sql.execution.datasources.v2.WritingSparkTask.$anonfun$run$1(WriteToDataSourceV2Exec.scala:448)
	at org.apache.spark.util.Utils$.tryWithSafeFinallyAndFailureCallbacks(Utils.scala:1410)
	at org.apache.spark.sql.execution.datasources.v2.WritingSparkTask.run(WriteToDataSourceV2Exec.scala:486)
	at org.apache.spark.sql.execution.datasources.v2.WritingSparkTask.run$(WriteToDataSourceV2Exec.scala:425)
	at org.apache.spark.sql.execution.datasources.v2.DataWritingSparkTask$.run(WriteToDataSourceV2Exec.scala:491)
	at org.apache.spark.sql.execution.datasources.v2.V2TableWriteExec.$anonfun$writeWithV2$2(WriteToDataSourceV2Exec.scala:388)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:93)
	at org.apache.spark.TaskContext.runTaskWithListeners(TaskContext.scala:174)
	at org.apache.spark.scheduler.Task.run(Task.scala:152)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$4(Executor.scala:632)
	at org.apache.spark.util.SparkErrorUtils.tryWithSafeFinally(SparkErrorUtils.scala:64)
	at org.apache.spark.util.SparkErrorUtils.tryWithSafeFinally$(SparkErrorUtils.scala:61)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:96)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:635)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

The implications of these findings are as follows:

Flint's skipping index creation will fail because it automatically uses source file path as the document ID.
The deduplication approach proposed in this PR will not function as intended.
A similar deduplication approach (upsert with document ID) for future UPDATE mode support will also be ineffective.

For this PR, it remains functional with both AOS and AOSS search collections. However, since I couldn't find a way to determine the type of an AOSS collection, I will temporarily remove the auto-generated ID column logic for aggregate MVs. A separate PR will be submitted once an alternative approach is identified.


burn record of wall should be separated into  three column

1.the id owner
2. the  Non-anonymous
3. the  Anonymous
users can choose  sorting burn records According to the time or the burn amount
“TH.AMOUNT & TH.MESSAGE” Not enough detailed&Not easy to identify

Moved: https://github.com/BitShares/web_wallet/issues/546


Support Android 15 UI changes

From Google via https://developer.android.com/about/versions/15/behavior-changes-15

Apps are edge-to-edge by default on devices running Android 15 if the app is targeting Android 15 (API level 35)... Apps using Material 2 Compose components might be negatively impacted because Material 2 components don't automatically apply insets.

The Android app uses Material 2 components extensively. Evaluate necessary changes to avoid UI issues when Android 15 is released Fall 2024.

Closed by #52


Extend schema to contain table name, and migrate cost model's ColumnRef property usage to schema

From Chi:

yes we should do that, feel free to create an issue...
this is so-called "column name inference"
assign a name for unnamed columns, and use user-specified names for projections
and for the top-level node, if we have physical property implemented, it will always be a gather node
unless all plan nodes are singleton

ColumnRef and Schema seem to have a lot of purpose overlap, I think that we can merge their functionality together.

After reading more into ColumnRef, I am not as sure that it is redundant... Seems like a lot going on

yes, they are all column-level properties; but they are different -- schema is more focused on column type + name, while column ref indicates how the column is computed (which will then be used by the cost model to derive the cost)

with https://github.com/cmu-db/optd/issues/202, I feel the final state of this property will be like:

after aggregation: we will get something like Distinct(ColumnRef)
after projection, i.e., select v1 + 1 from table: we will get something like Add(v1, 1)
after join, we will get something like Correlated(X, Y, original_column_ref)

so it could be more complex that what it is right now


Remove python 3.6 references

Fixes: https://github.com/apache/beam/issues/25002

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn @aaltay

Run Python Dataflow ValidatesRunner

LGTM


Added Docker support

Codecov Report

Merging #7 into master will decrease coverage by 0.06%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master      #7      +/-   ##
=========================================
- Coverage   16.66%   16.6%   -0.07%
=========================================
  Files           4       4
  Lines         252     253       +1
=========================================
  Hits           42      42
- Misses        200     201       +1
  Partials       10      10

Impacted Files
Coverage Δ

bindata_assetfs.go
0% <0%> (ø)
:arrow_up:

main.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


TAML, Assets and Modules implementation

Initial implementation of the TAML, Asset and Module systems ported from T2D.
This is everything necessary for the base implementation and doesn't override any existing functionality. It comes with a blank example asset and a ShapeAsset that loads a shape file and stores the TSShape for later reference.

Technically TAM was an acronym at that point, but yeah, it did look like a typo, huh ;)
I tweaked the title to be clearler.

Oh, I see! Sorry :joy:

notes thusfar:
changes the signature of addProtectedField, so will need to go through and add &defaultProtectedWriteFn, entries, like so:
https://github.com/GarageGames/Torque3D/blob/2044b2691e1a29fa65d1bdd163f0d834995433ce/Engine/source/T3D/fx/particle.cpp#L207-L208
to
addProtectedField( "sizes", TYPEID< F32 >(), Offset(sizes, ParticleData), &protectedSetSizes,
&defaultProtectedGetFn, &defaultProtectedWriteFn, PDC_NUM_KEYS,
there's a fairly full (though incompatible) list https://github.com/lukaspj/Torque3D/commit/fa89f62d022ffd17e8b6c8158da1d9fa14920374
do note that as a function-pointer, new AbstractClassRep::WriteDataNotify() should be replaced where possible with &defaultProtectedWriteFn as in the above example as well.

Scratch the above, we found a less intrusive fix.


New Feature: Support User-provided Mix Spatial Mapping, And spatial_mapping_hint Definition Can Be Provided in the Mapping File for Mix Spatial Mapping Auto-generation.

New feature: Supporting Mixed Spatial Mapping
We have introduced a new feature that enables the inclusion of mixed spatial mapping in the mapping file, alongside the original single-layer-dimension spatial mapping. For examples, please refer to the files located under the /tests/main/test_with_mix_spatial_mapping folder.
New parameter in the input mapping file:
spatial_mapping_hint: Dict: {hardware_dimension: [supported_layer_dimensions]}. This parameter only works when spatial_mapping is not provided or partially provided in the mapping file. Now the generated spatial mappings will only be on the layer dimensions defined in spatial_mapping_hint. It will be assumed to include all layer dimensions if this parameter is not provided.
New parameters can be provided from the top:
enable_mix_spatial_mapping_generation:

True --> SpatialMappingGeneratorStage will auto-generate mix spatial mapping.
False --> SpatialMappingGeneratorStage will stick to spatial mapping of single layer dimension.

maximize_hardware_utilization:

True --> SpatialMappingGeneratorStage will only keep two spatial mapping candidates for each hardware dimension, which has the highest hardware utilization, for a faster simulation time.
False --> SpatialMappingGeneratorStage will keep all spatial mapping candidates it found.

Adds/Changes:

SpatialMappingGeneratorStage now can also generate mix spatial mappings.
SpatialMappingConversionStage now can also interpret mix spatial mappings.
Pytest cases are added to the /tests/main/test_with_mix_spatial_mapping folder for testing scenarios involving mixed spatial mapping. Additionally, a dedicated test case with a spatial_mapping_hint definition can be found in test_tesla_npu_like.py.

Bug Fixes:

The abortion in SpatialMappingGeneratorStage has been fixed for cases where only parts of the spatial mapping are user-provided.
An error in LomaStage, where the same layer dimension was mapped to different hardware dimensions, has been resolved. Now, these spatial mappings on different hardware dimensions are merged before being sent to LomaStage.

New fixes:

Corrected an erroneous API call in the original pytest cases.

Updated pytest cases to include five tests, each addressing different scenarios related to mixed spatial mapping features:

When only spatial_mapping is provided while spatial_mapping_hint is not provided (Test: test_with_mix_spatial_mapping/test_ascend_like.py).
When both spatial_mapping and spatial_mapping_hint are provided (Test: test_with_mix_spatial_mapping/test_edge_tpu_like.py).
When an incomplete spatial_mapping is provided, and spatial_mapping_hint is provided (Test: test_with_mix_spatial_mapping/test_meta_prototype_like.py).
When only spatial_mapping_hint is provided (Test: test_with_mix_spatial_mapping/test_tesla_npu_like.py).
When the number of dimensions provided in the spatial_mapping_hint exceeds the dimensions available in the hardware (Test: test_with_mix_spatial_mapping/test_tpu_like.py).


High CPU and janky experience while using Edge Tools Screencast

Environment (please complete the following information):

MacOS 12.3
15" Macbook Pro (2017)
VS Code: 1.65.2
Edge dev tools v1.4.5

Describe the bug:

I just cloned this repo and while playing around with the edge dev tools / debugger, I'm noticing high CPU rates. Especially so when the screencast is in view. Navigating the sample app is quite janky / unresponsive. This has a massive impact on the overall experience of using the screencast.
Repro steps:

Clone https://github.com/codepo8/simple-to-do, open vscode and start debugger with http-server
Expected behavior:

For the overall experience to feel snappy without high cpu levels
Additional context:

Thanks for filing this issue Daniel. It seems like something we will need to investigate further.
Pinging @codepo8 here as he might have questions for you that would help narrow this down.

I am getting the same problem.
Reset all devtools settings to default but same
Version 103.0.1264.62 (Official build) (64-bit)

I got excited about this feature after discovering it this morning!  But yes, I experience the same sluggishness and I'm not advocating it to the team for now:

Same issue, on MacOS 13.3.1 (Macbook Pro M2), VSCode version 1.78.1
The CPU usage is very high in headless mode.

When I launch the debug session on Edge without the headless feature, I have much less CPU usage:


Cannot read property '_bodyLoadedPromiseFulfill' of null

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.6.0
Platform / OS version: Jessie
URLs (if applicable):
Node.js version: 8.11.2

What steps will reproduce the problem?
I can't figure out from the stacktrace what action in my code is causing it
TypeError node_modules/puppeteer/lib/NetworkManager.js:280

node_modules/puppeteer/lib/NetworkManager.js:280:23_onLoadingFinished
events.js:116:13emitOne
events.js:211:7emit
node_modules/puppeteer/lib/Connection.js:232:12_onMessage
node_modules/puppeteer/lib/Connection.js:119:19_onMessage
events.js:116:13emitOne
events.js:211:7emit
node_modules/ws/lib/websocket.js:720:20receiverOnMessage
events.js:116:13emitOne
events.js:211:7emit
node_modules/ws/lib/receiver.js:414:14dataMessage
node_modules/ws/lib/receiver.js:346:17getData
node_modules/ws/lib/receiver.js:133:22startLoop
node_modules/ws/lib/receiver.js:69:10_write
_stream_writable.js:397:12doWrite
_stream_writable.js:383:5writeOrBuffer
_stream_writable.js:290:11write
node_modules/ws/lib/websocket.js:795:35socketOnData
events.js:116:13emitOne
events.js:211:7emit
_stream_readable.js:263:12addChunk
_stream_readable.js:250:11readableAddChunk
_stream_readable.js:208:10push
net.js:597:20onread

@adamgotterer do you have request interception enabled? It will help a lot if you'll come up with any repro for this.

I've also seen this happen in 1.5.0.
I can't reliably reproduce this bug. We have the code running with a production workload and it happens what seems like randomly. I've tried URLs that failed on the same code a second time and it succeeds. We are using Puppeteer as a way to render and extract data about a webpage. We have lots of debug logging and request ID attached to all our logs as a way to track a single request life cycle.
When this exception occurs it has a request id but it has no debug information prior to the exception. What's add about it is there is debug information that is supposed to be outputted before even connecting to puppeteer. I'm starting to wonder if something from a previous request is leaking into the current request.
It's going to require some more digging...

I am also seeing this issue, and the rejection is not handled in the code:
(node:48040) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '_bodyLoadedPromiseFulfill' of null
    at NetworkManager._onLoadingFinished (/Users/dennisy/scrape/node_modules/puppeteer/lib/NetworkManager.js:280:23)
    at CDPSession.emit (events.js:180:13)
    at CDPSession._onMessage (/Users/dennisy/scrape/node_modules/puppeteer/lib/Connection.js:232:12)
    at Connection._onMessage (/Users/dennisy/scrape/node_modules/puppeteer/lib/Connection.js:119:19)
    at WebSocket.emit (events.js:180:13)
    at Receiver.receiverOnMessage (/Users/dennisy/scrape/node_modules/ws/lib/websocket.js:720:20)
    at Receiver.emit (events.js:180:13)
    at Receiver.dataMessage (/Users/dennisy/scrape/node_modules/ws/lib/receiver.js:414:14)
    at Receiver.getData (/Users/dennisy/scrape/node_modules/ws/lib/receiver.js:346:17)
    at Receiver.startLoop (/Users/dennisy/scrape/node_modules/ws/lib/receiver.js:133:22)

Seeing the same issue when running an integration test with puppeteer:
    TypeError: Cannot read property '_bodyLoadedPromiseFulfill' of null

      at NetworkManager._onLoadingFinished (node_modules/puppeteer/lib/NetworkManager.js:252:23)
      at CDPSession._onMessage (node_modules/puppeteer/lib/Connection.js:233:12)
      at Connection._onMessage (node_modules/puppeteer/lib/Connection.js:119:19)
      at Receiver.receiverOnMessage (node_modules/ws/lib/websocket.js:720:20)
      at Receiver.dataMessage (node_modules/ws/lib/receiver.js:414:14)
      at Receiver.getData (node_modules/ws/lib/receiver.js:346:17)
      at Receiver.startLoop (node_modules/ws/lib/receiver.js:133:22)
      at Receiver._write (node_modules/ws/lib/receiver.js:69:10)
      at Socket.socketOnData (node_modules/ws/lib/websocket.js:795:35)

@mkotsur any chance you can give me some details so that I can repro this?

Well, I can... I can even tell what the fix is. And may be you can tell if there is a way to monkey-patch this, perhaps...
So, the code is (I can't promise it will be working for a long time, though):
import * as puppeteer from "puppeteer";

const launch: () => Promise<[puppeteer.Browser, puppeteer.Page]> = async () => {
  const browser = await puppeteer.launch({
    headless: false
    // , slowMo: 250
  });
  const page = await browser.newPage();
  return [browser, page];
};

const shutDown = async (browser: puppeteer.Browser, page: puppeteer.Page) => Promise.all([page.close(), browser.close()])

// THE INTERESTING PART STARTS HERE
  try {
    await page.goto("https://vault.rosx.technology");
    await page.click("header button");
    await page.waitForSelector('input[name="pf.username"]');
    await page.type('input[name="pf.username"]', "ertbnm+6pbwenc1esl3s@sharklasers.com");
    await page.click("#els-continue");
    await page.waitForSelector('input[name="password"]');
    await page.type('input[name="password"]', "123qwe");
    await page.click('button[type="submit"].els-primaryBtn', {delay: 1000});
    await page.waitForNavigation();
    await page.waitForSelector("h1");
  } finally {
    console.log("Closing the page and the browser");
    await page.close();
    await browser.close();
  }

I can fix this behaviour by going to the method mentioned at the top of the stack trace and changing:  if (!request) into if (!request || !request.response()). After this everything works just fine.
Are you aware of any more or less clean way of monkey patching this method in my project?

@mkotsur this is awesome, thanks. I can repro and I see what's going on; let me see if I can do a test that reproduces this.

@mkotsur I filed upstream: https://crbug.com/883475, but wasn't able to reproduce this behavior in a test.

Are you aware of any more or less clean way of monkey patching this method in my project?

Fix should be merged sometime soon; once it is, you can install the tip-of-tree version of puppeteer with the fix using the puppeteer@next tag:
npm i puppeteer@next


feat(token): support being logged into multiple greenkeeper instances…

… at the same time
In preparation for Greenkeeper Enterprise

LGTM :shipit:


loss function in training phase

According to paper, I think that the groundtruth and output of model are continuous rather than binary. Is that right?
If it is right, which loss function was chosen to train the model? The CrossEntropy loss requires that the target be binary.
Or is a soft label for CE loss?

Yes, we use continuous labels and outputs.
We use a sigmoid cross entropy loss: https://www.tensorflow.org/api_docs/python/tf/nn/sigmoid_cross_entropy_with_logits#args

The CrossEntropy loss requires that the target be binary.

This is not true. Please read the argument.
https://www.tensorflow.org/api_docs/python/tf/nn/softmax_cross_entropy_with_logits#args_1
The link Orly gives has detailed math in it.
In the two class setting (sky / non-sky), the sigmoid cross entropy is the same as the softmax cross entroy. It's just a matter how you want to prepare your logits (in one channel vs in two channels).

Got it. Thanks for your explaination.


Enhance README format and structure as per template

reformat and restructure according to this template: https://github.com/stakater/README/
add in missing content. the Readme should clearly define what the project is/does and how it should be used.
review and add appropriate badges at the top of the readme

@wajeeha09 Pending items once the application is running:

Add details in README related to customization of Coin Exchange, being a "white label" exchange, especially how to change the name/ logo/ theme for the exchange
Add screenshots with use case headings
confirm Fiat and Crypto currencies that are supported.


Update docker-compose.yml file to new API key

As a Developer
I need to create a new API key
So that I can join my team's IBM cloud account
Details and Assumptions

update makefile to call new API file
Eveyone must do it in order to login to admin's cloud act
docker-compose file lives in shopcarts/.devcontainer

Acceptance Criteria
Given a new API key
When I do make file
Then I should be able to log into the shopcart account

Directions:
STEP 1: Create an API Key for the project account
Login to IBM Cloud
Switch to the account your project is using
Go to Manage > Access (IAM) > API keys
Press the Create button to create a new key and name it: Project Key
Download it and rename it project_apikey.json
Move it to your ~/.bluemix folder
STEP 2: Add the API key to your project dev environment (only one student needs to do this for the team)
Go to the directory of your local project repo
Edit the file: .devcontainer/docker-compose.yaml
Modify the volumes: statement to look like this
volumes:
- ..:/app
- ~/.bluemix/project_apikey.json:/home/vscode/apikey.json
Save the file and commit it.
DONE:
Now whenever you bring up the project repo, and use make login it will log you into the project IBM Cloud account.

please re-do and update the api key for under services!
the PR was reversed so you only need to add: ~/.bluemix/project_apikey.json:/home/vscode/apikey.json
thanks!


Clarify values in Step 9

After reading all the feedback, it is still not clear how to provide the values in step 9 (audience and issuer).
Reading through several responses the audience should be set to the AppId of the Azure VPN enterprise app, however this is not clear by reading through the documentation.
The issuer value is still a mystery to be. Please provide clear and consecutive steps how to obtain the value.

@ptreptau -
Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

Thank you I found the correct values through a 3rd party website:
The suggested URL for correction is: https://docs.microsoft.com/en-us/azure/vpn-gateway/openvpn-azure-ad-tenant
Fill in the following values in step 9:
Tenant: TenantID for the Azure AD tenant
https://login.microsoftonline.com/{AzureAD TenantID}/
Audience: ApplicationID of the "Azure VPN" Azure AD Enterprise App
{AppID of the "Azure VPN" AD Enterprise app}
Issuer: URL of the Secure Token Service
https://sts.windows.net/{AzureAD TenantID}/

@ptreptau - Thank you for your inputs and providing the document details. I have reached out to the internal team here to get the document updated. I will keep you posted once I have an update.

@ptreptau -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


No crashreport can be found after a session crash

Hyprland Version
v0.30.0, 1b48642fd15c433c53876f1b933dcd46265caf8f
Bug or Regression?
Bug
Description
After a session crash (see https://github.com/hyprwm/Hyprland/issues/3484 and https://github.com/hyprwm/Hyprland/issues/3489 for references), I could not find a crash report.

Without XDG_CACHE_HOME , .~/.hyprland folder stay empty. I found a crashreport from august though (I deleted it for testing this issue, no backup).
With this variable set, hyrpland folder stay empty after a crash.

I could not find it either with find / -name "hyprlandCrashReport*"
But it seems to be generated as shown in this pic:

How to reproduce

Set or unset XDG_CACHE_HOME
Wait for a crash
check if a crash report exist

Crash reports, logs, images, videos
No response

check with 24c04a8b7c874ead168bb2418f4325cb8bdaca5b

Didn't work without XDG_CACHE_HOME, I try with it and let you know

that's odd because I don't have XDG_CACHE_HOME set either and I do get crash reports.

Well, after a 2-hour session with  https://github.com/hyprwm/Hyprland/commit/4b3efc73c5d059e828f79952d80ff79c97521c3d compiled in debug mode, I still haven't had the crash. I notice that everything is slower though, dunno if it can impact the crash. Gonna try with the same commit but without the debug flag.
Also, xdg-desktop-portal-hyprland  consume 20% of my cpu all the time.

Also, xdg-desktop-portal-hyprland consume 20% of my cpu all the time.

use -git it was fixed

Updated. In case my crash doesn't happen anymore, I tried with a SIGTERM signal and the crash report was saved

closing


Task/i2c slave driver issue 90

For discussion only. No actual merge requested.

For discussion only. No actual merge requested.

You can mark a PR as a draft to prevent it being merged in its current state.  Mind doing that? :)

Sure thing. I'll close this and make a new draft pr. Didn't know GH supported that. Cool.

Nono, mark this one as draft, you can change it!

Oops. I didn't see that as an option.
-Todd
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, October 25, 2020 3:28 AM, Rahix<EMAIL_ADDRESS>wrote:

Nono, mark this one as draft, you can change it!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Never mind, let's move over to the other PR.


Ability to send images by chat

Add multichannel ability to the conversation. Allows a user to send a image to the bot and being analyzed by voice to the customer.

MMS send/receive feature is not yet supported by Azure Communication Services. Nevertheless, WhatsApp integration is feasible (https://learn.microsoft.com/en-us/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview).


[linux] defcfg does not work on debian.

Re-setting of xkbmap using 'output (uinput-sink ... "setxkbmap ...")' doesn't work now.
This occurs after June 1 and 2 2022 updates.

Sorry, sleep 1 to sleep 2 solved this problem.

I'll close this issue.


statCache not consistently populated

I created a repository to help illustrate this issue. I would have preferred using something like JSBin but not sure how I would use it to describe this issue. Regardless, the repo is here: https://github.com/Macrofig/glob-test
If I have a pattern, say /test/**/*.*, Glob finds and populates the cache and statCache objects properly.  But if I have a pattern like /test/**/*.{js,stache}, some items are not populated in the file. In my case, it seems to be the stache files but I am not certain that is the case.
We were previously using version 5.0.3 of Glob and this pattern wasn't an issue. We are updating to version 7.0.4 and experiencing this bug. Specifically, through Karma. We were also updating Karma from 0.12.31 which was using Glob 3.x. The current version of Karma uses 7.x.
Doing some research, it seems like this PR introduced this issue but I'm not entirely sure I understand the use case for #158 so I can't be certain what the fix is. I'd love to help with a PR but I would need some guidance.
Thoughts, ideas? Is it maybe my pattern that is incorrect? Thanks!

Adjusting the glob pattern may help. An example:
diff --git a/.angular-cli.json b/.angular-cli.json
index 4b69daf..90d31c6 100644
--- a/.angular-cli.json
+++ b/.angular-cli.json
@@ -66,7 +66,7 @@
         },
         {
           "input": "../../../docs",
-          "glob": "**/*.{jpg,jpeg,png}",
+          "glob": "**/*+.{jpg|jpeg|png}",
           "output": "content/guide"
         }
       ],

No longer an issue on v9


Do HMR better

As discussed, I believe this turns out to be because of how react-hot-loader does component swapping - see their docs for details. So let's merge anyway, as it's the best we can do.


add parameter for base_link

This PR builds upon PR #41 and fixes issue #40.
In most robotics setups the tf tree looks similar to this example: map->odom->base_link->lidar_frame
In many cases, the base_link does not coincide with the lidar_frame.
With the current parameters, it is only possible to rename the base_link, using the lidarFrame parameter. The result is a direct connection from odom to lidar_frame and the base_link is not used at all: map->odom->lidar_frame
My proposed solution is the introduction of an additional base_link parameter.
Now, when the node gets launched the transform from the lidar_frame to base_link gets stored.
The odometry is calculated in the lidar_frame and the result is a transform from odom to lidar_frame so that multiplying the lidar_frame to base_link transform results in the desired odom to base_link transform.
By default, the original hardcoded frames are used and these steps are completely ignored when the base_link is the same as the lidar_frame. So this PR does not result in any changes for existing setups.

Looks good.


The third argument in numpy.ndarray.__pow__() should be optional

Environment data

Language Server version: 2021.5.3
OS and version: Windows 7
Python version (& distribution if applicable, e.g. Anaconda): 3.8.8 Anaconda

Sample
import numpy as np

a: np.ndarray = np.array([])
b = a ** 2  # Operator ** not supported for types "ndarray" and "Literal[2]".

Expected behavior
No warning.
Actual behavior
See comment in sample.
Suggestion
File: ".../dist/bundled/native-stubs/numpy/core/_multiarray_umath.pyi"
Line: 1258
Replace
def __pow__(self, value, mod) -> ndarray:

with
def __pow__(self, value, mod=...) -> ndarray:

What version of numpy are you using? These stubs are generated from the compiled modules and are not intended to be used in type checking, only to provide extra completions and docstrings. If you are using the most recent version of numpy, their types should take precedence.

I'm using numpy v1.19.2. I'll try an update.

Yeah, you definitely do not want to be type checking with numpy before 1.20. 1.21 should have many many more typing improvements.

Thank you for the info. With the new version of 1.20.1, the typing is far better now.


Review the FAQs

There are some issues in the FAQs:

FAQ 6 is a non-answer
FAQ 8 seems to contradict what we say in FAQ 9 and in the homepage
FAQ 16 and FAQ 17 point back to the wrong answer

+1 please go ahead!


Add Gemfile.lock

Summary
When creating a gem, it is generally recommended to exclude the Gemfile.lock file from the gem's distribution. The Gemfile.lock file is specific to the development environment and ensures that the exact versions of dependencies used during development are installed. However, when someone else uses your gem in their project, they should rely on the gem's specified dependency versions in the gemspec file, not the Gemfile.lock.
In the gemspec file, you typically use the git ls-files command to include all the necessary files in the gem. The reject block is used to exclude certain files or directories that shouldn't be included in the gem.
Here's an example of how you can exclude files in the gemspec:
s.files = `git ls-files -z`.split("\x0").reject { |f|
  f.match(%r{^(test|spec|features|tmp|node_modules|packages|coverage|Gemfile.lock)/})
}

Summary by CodeRabbit

Chores

Updated .gitignore to no longer ignore Gemfile.lock.
Modified GitHub Actions workflow to remove Gemfile.lock before setting up Ruby.

Refactor

Improved file inclusion logic in shakapacker.gemspec to exclude unnecessary directories, enhancing the file selection process.

@tomdracz OK now? :-)


docs: DLT-1787 implement custom TOC

Dialtone documentation site - Collapsible TOC
Obligatory GIF (super important!)

:hammer_and_wrench: Type Of Change
These types will not increment the version number, but will still deploy to documentation site on release:

[x] Documentation

:book: Jira Ticket
https://dialpad.atlassian.net/browse/DLT-1787
:book: Description

Created a custom TOC.
Removed @vuepress/plugin-toc dependency and usages.
General clean up.
Replaced TokensToc to use the same TOC component than everywhere, we shouldn't have two TOC components.

:pencil: Checklist
For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.
[x] I have considered the performance impact of my change.

For all CSS changes:

[x] I have used design tokens whenever possible.
[x] I have considered how this change will behave on different screen sizes.
[x] I have visually validated my change in light and dark mode.

:camera: Screenshots / GIFs
https://github.com/dialpad/dialtone/assets/87546543/feb96153-6992-4ab3-8ddd-56f7d5a32309

@juliodialpad,
Thanks for getting the TOC positioning consistent!
I've come to really like that this works across all pages, not just the Tokens page. Is there a debounce adjustment that can be made so the TOC reflects the current view more quickly?
View the attached video. The TOC expand/collapse and showing active item seems to only update once scrolling is complete.
https://github.com/dialpad/dialtone/assets/1165933/3f74897b-4a05-4d7b-a566-1e01570e76a3

@juliodialpad,
Thanks for getting the TOC positioning consistent!
I've come to really like that this works across all pages, not just the Tokens page. Is there a debounce adjustment that can be made so the TOC reflects the current view more quickly?
View the attached video. The TOC expand/collapse and showing active item seems to only update once scrolling is complete.
Screen.Recording.2024-07-09.at.3.15.09.PM.mov

We're using a VuePress plugin to automatically update the route based on the position (check the URL) but looks like it updates the position after a fixed amount of time (for performance reasons).
Here's their code and that value cannot be changed by us: https://github.com/vuejs/vuepress/blob/9fb4bb00925d9409e6732118e996411c6a82c85d/packages/%40vuepress/plugin-active-header-links/clientRootMixin.js
We could create our own implementation of it, but definitely out of scope for this PR.

We could create our own implementation of it, but definitely out of scope for this PR.

Yeah cool. No biggie. We'll keep on eye on it and maybe consider doing that if we think it feels wrong over time or people complain enough or causes confusion. I approve from design perspective for now. Thanks!!


Publish main to live on 9/26 @ 10:30 am

Docs Build status updates of commit 6687c33:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Sync-CsOnlineApplicationInstance.md
:white_check_mark:Succeeded
View (skype-ps)

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


chore: non-obvious type fixes not concerning IMA

This PR provides a batch of type fixes that are:

non-trivial from the perspective of code behavior
not concerning (I will create a separate PR for those)

In my local testing setup, they run clean all tests including regression.

Codecov Report

Merging #1173 (ada9f57) into master (0db75e0) will decrease coverage by 0.08%.
The diff coverage is 66.07%.

Additional details and impacted files

Flag
Coverage Δ

packit-e2e
71.24% <66.07%> (-0.10%)
:arrow_down:

testsuite
54.49% <53.57%> (-0.11%)
:arrow_down:

unittests
14.39% <0.00%> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

keylime/revocation_actions/update_crl.py
0.00% <0.00%> (ø)

keylime/cloud_verifier_common.py
78.91% <37.50%> (-1.51%)
:arrow_down:

keylime/cert_utils.py
69.41% <50.00%> (-0.47%)
:arrow_down:

keylime/crypto.py
91.66% <60.00%> (-1.73%)
:arrow_down:

keylime/registrar_common.py
59.58% <70.00%> (+0.07%)
:arrow_up:

keylime/cloud_verifier_tornado.py
67.21% <75.00%> (+0.15%)
:arrow_up:

keylime/tpm/tpm_main.py
73.66% <87.50%> (-0.39%)
:arrow_down:

@mdrocco once the commits are squashed into a single one this LGTM.


Make sure that the DCO is applied to every commit

Fixes #1988
Please include details of what it is, how to use it, how it's been tested
PR Type

Bugfix Pull Request

So far members of the "Ansible" organization were not always signing the DCO.

@MarkusTeufelberger I'm not sure whether it's needed legally: making commits as Red Hat employees seem to automatically cover that... (yet I may be wrong). So it's probably up to @gundalow to decide

I think this actually applies only to people in https://github.com/orgs/ansible/people - and they probably are not all employed by RedHat or have a contract with RH that all their contributions (at work and during off-work hours) are covered by this.
Even Linus Torvalds signs-off his commits...

How is this a feature that make contributions easier if it only affects 57 Github accounts?
I'm all for removing the DCO by the way. Until then, then existing rules for contributing should be followed though - they currently are not.

@MarkusTeufelberger fair enough.
FTR, I've suggested @gundalow to implement a CLA bot (there's a few ready to use and easy to set up available in the wild) and he was going to check this with legal. Hopefully, we'll be able to replace DCO by a one-time signature which will address all those pain points...

Neither DCO nor CLA is required to contribute to https://github.com/ansible/ansible by the way. https://github.com/ansible/awx seems to require the DCO, but I don't find many signed-off commits there and I'm not sure if it is even possible to contribute as an external there or if anyone even tries to do that these days. The difference between external engagement between these 2 projects is striking and I partially also blame the DCO or similar restrictions.
A CLA would cover different things than a DCO, but it is a bit easier to set up at least. A bit harder to do in a corporate setting though (depending on the scope of the CLA). I also wouldn't feel comfortable to give up rights of my contributions to a place ultimately owned by IBM.

As discussed in IRC meeting 2019-04-17 I will discuss this with Red Hat's Legal Team.
Until then things will continue as-in.

@jctanner can you by any chance follow this up to resolve it now? As far as I understand, gundalow will not be around due to holidays but we'd still like to be able to move forward on "paper work" issues like this ...

I am personally against this ticket as I am looking towards making occasional contribution as simple as posible. In fact I am for matching the Ansible contributuon policy, which has no such condition. I bet that the Ansible community would be quite unhappy if it would also be introduced there.
One major PITA with this is that it renders github web-edits useless as they would not have the DCO signature, making very hard to fix minor issues in existing PRs, or even trivial fixes which can be proposed from inside the browser (like bumping requirement versions).

I'm personally strongly against the DCO too, but this PR is about actually applying it as outlined in the DCO... There are other places where abandoning the signoff requirement can be discussed, this PR is about making sure that contributors (no matter from which organization!) are actually signing off their commit in accordance to the DCO. People leave companies and organizations all the time, it is often hard after the fact to research if someone was an employee of Red Hat for example and wrote the contribution in their capacity as employee.

There are other places where abandoning the signoff requirement can be discussed

Yes. Let's call that off-topic here and push that out to https://github.com/ansible/molecule/issues/1548.

I will close this as this PR is not actionable right now. We already have a ticket to track it and we can re-open it once we can make a decision.

What's the tracking ticket?
This PR is about enforcing the DCO properly (there are commits in this repo made after Red Hat took over without the DCO being signed!), not getting rid of it.

@MarkusTeufelberger  AFAIK https://github.com/ansible/molecule/issues/1548 is tracking that subject and I will do my best to get this DCO non-removed. Lets continue there, @gundalow is finally back and I hope we fix it next week.

There are still/again very recent commits in this repository that are not correctly signed-off. Please either reopen + merge this PR to make sure this doesn't happen without the bot complaining or remove the DCO as discussed in #1548
The current situation is that some select people (everyone in the "Ansible" organization on GitHub) don't have their DCO requirements checked by the bot, so they seem to assume that the DCO is not applicable to them. This PR fixes this. This is perfectly actionable until a decision about the DCO as such has been taken.


Better Communication

Hello fellow coders, late time we did not have good communication, this lead to a last minute dash in to finish the project.  Lets brainstorm a way to fix this issue

Bump


Use pathToGroup function argument in ServletLimiterBuilder

Looks like there's a bug in ServletLimiterBuilder where the method partitionByPathInfo wasn't using the pathToGroup function. Fixed and updated the tests

Thanks for the fix.  Love all the additional tests!


Add a hook to transform items returned by async paged iterators

This is needed to complete https://github.com/Azure/azure-sdk-for-python/issues/11344 where the async paged index returns need to have a function called on each item:
https://github.com/Azure/azure-sdk-for-python/blob/2598959164c9d1e87f20060e8ca76ec563d180d6/sdk/search/azure-search-documents/azure/search/documents/_service/aio/_indexes_client.py#L77-L78
cc @lmazuel @xiangyan99

Looks like the existing cls parameter could be used for this.


Investigate monkey patch of PrismJS

I have an idea for a new feature for jQuery Terminal
This is the code for the highlight function from PrismJS:
highlight: function (text, grammar, language) {
	var env = {
		code: text,
		grammar: grammar,
		language: language
	};
	_.hooks.run('before-tokenize', env);
	if (!env.grammar) {
		throw new Error('The language "' + env.language + '" has no grammar.');
	}
	env.tokens = _.tokenize(env.code, env.grammar);
	_.hooks.run('after-tokenize', env);
	return Token.stringify(_.util.encode(env.tokens), env.language);
},

There is a need to test with different grammars if those hooks make a difference. I was told they do.

I'm not sure if there are any differences but for the sake of having the same code as prism. I've added the hooks.


Reload features from Parquet metadata

Resolves #5482.
Attaches feature metadata to parquet files serialised using Dataset.to_parquet.
This allows retrieving data with "rich" feature types (e.g., datasets.features.image.Image or datasets.features.audio.Audio) from parquet files without cumbersome casting (for an example, see #5482).
@lhoestq It seems that it is sufficient to attach metadata to the schema prior to serialising and features are loaded back with correct types afterwards automatically.
I used the following script to test the implementation:
from pathlib import Path

import datasets

dataset_name = "Maysee/tiny-imagenet"
ds = datasets.load_dataset(dataset_name, split=datasets.Split.TRAIN)
output_directory_path = Path(__file__).parent.joinpath("example_test_outputs", dataset_name.replace("/", "_"))
output_directory_path.mkdir(exist_ok=True, parents=True)
output_filepath = output_directory_path.joinpath("ds.parquet")
ds.to_parquet(str(output_filepath))

reloaded_ds = datasets.load_dataset(str(output_directory_path), split=datasets.Split.TRAIN)

assert ds.features == reloaded_ds.features

Prior to the change in this PR this script raises an AssertionError and the Image features lose their type after serialisation. After the change in this PR, the assertion does not raise an error and manual inspection of the features shows type Image for the respective columns of reloaded_ds .
Some open questions:

How/where can I best add new unit tests for this implementation?
What dataset would I best use in the tests? I chose Maysee/tiny-imagenet mainly because it is small and contains an ?Image` feature that can be used to test, but I'd be happy for suggestions on a suitable data source to use.
Currently I'm calling datasets.arrow_writer.ArrowWriter._build_metadata as I need the same logic. However, I'm not happy with the coupling between datasets.io.parquet and datasets.arrow_writer it leaves me with. Suggest to factor this common logic out into a helper function and reuse it from both of these. Do you agree and if yes, could you please guide me where I would best place this function?

Many thanks in advance and kind regards,
MFreidank

Cool ! I think you just need to remove the unused import in io/parquet.py
src/datasets/io/parquet.py:4:1: F401 'pyarrow as pa' imported but unused

and we're good to merge :)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Cool ! I think you just need to remove the unused import in io/parquet.py
src/datasets/io/parquet.py:4:1: F401 'pyarrow as pa' imported but unused

and we're good to merge :)

done!


Feature/delete item

In this branch I did:

Add action controller to delete a specific vehicle
When the user clicks the Delete item link in the navigation panel they can see a list of all items with title and Delete button.
When the user clicks the Delete button, the selected item is marked as removed and does not show on the main list anymore

Front end PR

Hi @JavierAybar  👋🏼,
Approved 💯
Your work is complete for now! We will double check everything, when the navigation is done! it's time to merge it :shipit:
Congratulations! 🎉
Highlights✅
Linters are passing.
Page functions as described.


upgrade pekko libs and aws lib

these jars support scala 3 (as a bonus)

Did you release AwsSpiPekkoHttp for Scala 3?

Did you release AwsSpiPekkoHttp for Scala 3?

the version in this PR has a v3 jar published

Perfect!


Private but not followed.

Your question here... i have followed all the step but in the end its show "Private but not followed"
can you plz help or or show me the step without follow that person and get all the photos of an insta private account

This is not possible.
You have to be an approved follower of a private profile to access and download it.

Hi Thanks for your Reply
Its Possible its shows the same what ive told u
okay, its not possible without following or being follow to the user?

As I said before: You have to be an approved follower of a private profile to access and download it.
Anyway you can access and download a private profile if your are a approved follower and use the approved account as login.


Azure Blobstorage Binding and State Store: Migrate to Track2 Azure SDK

Signed-off-by: Bernd Verst<EMAIL_ADDRESS>Description
Azure Blobstorage Binding: Migrate to Track2 Azure SDK
Fixes #1530

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

Somehow the refactoring in commit 8811d5e64fa0feb4cc3b1c10ebdda3610aa0a236 introduced a huge performance regression for the binding.
Will have to look into it tomorrow, or revert.

/ok-to-test

/ok-to-test

/ok-to-test


Support destinations in NameTrees with encoded keys (issue 14847)

Initially I considered updating the NameOrNumberTree-implementation to handle encoded keys, however that quickly became somewhat messy (especially in the NameOrNumberTree.get-method) since only NameTrees using string-keys.
Hence the easiest solution, as far as I'm concerned, was thus to just update the Catalog.destinations-getter instead. Please note that in the referenced PDF document the Catalog.destination-method will thus fallback to fetch all destinations, which should be fine since this is the very first case of encoded keys that we've seen.
Also changes the NameOrNumberTree.getAll-method to prevent a possible run-time error, although we've so far not seen such a case, for any non-Array Kids-entries found in a NameTree/NumberTree.
Finally, to improve overall consistency and to hopefully prevent future bugs, the patch also updates a couple of other NameTree call-sites to correctly handle encoded keys. (Note that the Catalog.attachments-getter was already doing this.)

/botio test


iScroll breaks on new Safari for iOS 11.3 update?

We're using iScroll5 on a <div> element with position:fixed set. Everything has been working perfectly so far but since a few days scrolling on mobile Safari (iPhone) doesn't work properly anymore.
I first thought that it's a bug on our side but then I saw that Nike is using iScroll in the same way and the issues are very similar, see the video here: https://youtu.be/69ujxDii_Rw
Can someone confirm this problem on Safari for iOS 11.3 or is this maybe even a known issue?

@valnub  - we're seeing the same problem.  it seems like the scroll events are being passed through to the container elements. causing scrolling of the container as well as the child.

We solved the issue by disabling document scrolling when the layer is open and enabling it when layer is closed:
  function enableDocumentScrolling() {
      const body = document.getElementsByTagName('body')[0];
      body.style.position = 'static';
      body.style.top = 'auto';
      body.style.bottom = 'auto';
      body.style.overflow = 'auto';
  }

  function disableDocumentScrolling() {
      const body = document.getElementsByTagName('body')[0];
      body.style.position = 'fixed';
      body.style.top = 0;
      body.style.bottom = 0;
      body.style.overflow = 'hidden';
  }

I had what I seems to be at least partially the same issue when using our app on iOS 11.3. I was able to fix it by upping the setTimeout around the initialization from 0 to 1000, along with setting the eventPassthrough property to false when initializing.

@Saintless The issue happens when iScroll is initialized to early, therefore your setTimeout workaround works but it's not good practice. It's better to listen for the usual events (ready, onload, deviceready...) and then initialize iScroll rather than using setTimeout.


Can not restore snaphots with dot in name

It is not possible to open snapshot restore dialogue if snapshot name contains dots.
No console error occur.
I refer to click on following gui element at .../#/snapshot
<i class="fa fa-download normal-action pull-right" data-toggle="collapse" href="#log-2018.01.17_details" aria-expanded="true">
</i>

+1

same here :(


Translate country name/adjective on frontpage

The word "Armenian" is not translated on the homepage.

@SDGArmenia I believe this is now fixed. Can you confirm?


Could you show a basic example such as a sphere?

I am trying to use your library in a regular THREE.js project by following the example at https://github.com/gkjohnson/three-gpu-pathtracer/blob/main/example/basic.js. But I got lost with the texture mapping. Could you show a basic example such as a sphere?

Here's a fairly basic example. It's still a bit long that maybe that can be addressed in future releases:
https://jsfiddle.net/c2asgdqu/3/


Remove volto-subblocks

This is meant to be a discussion topic. At this time, there is no deadline for this change, but you never know what the future will bring.
volto-subblocks is an old implementation for having sortable inner blocks and there are now at least two better ways of doing the same thing.
There are two possible ways to achieve removal of volto-subblocks.

using the standard ObjectListWidget from core volto
using an inner blocks editor, therefore changing all widgets to restricted blocks

While the second implementation is probably more easily extensible and maybe future proof, the first one is way easier and quicker to implement. I would probably still go with the first one, since volto-subblocks really needs to go, but this is open to feedback and discussion.

@pnicolli My vote would go to use the ObjectListWidget. We're using it extensively everywhere, it's a good fit.

@pnicolli The ObjectListWidget supports a schemaExtender (which predates Volto's schemaEnhancers), so you the framework is capable of holding the different fields as a single object list field. https://github.com/plone/volto/blob/eef928fd8be30d0a66c1fdb923bb43ec9757e10a/src/components/manage/Widgets/ObjectListWidget.jsx#L237-L239

@JeffersonBledsoe You're right, I misread @pnicolli comment regarding second option.
This would move the addon in the direction of kitconcept's design of the forms block. Cool!


chore: Disable tests for tagged build

If we run tests and build release artifacts we run into travis's 50
minutes timeout. So instead we only build release artifacts and trust
that they have already been run on the branch build

bors r+


Add Trap::trap_code

The public Trap in wasmtime is right now very opaque compared to the internal information which is available about the trap reason. This exposes the trap code of a wasm trap, which is useful to for example differentiate traps from host functions to traps coming from wasm itself.

Thanks for the PR! I don't think we'll want to expose the cranelift-internal TrapCode as part of the public API of the wasmtime crate, though. That's an internal implementation detail of wasmtime, so I think it'd be best to instead have a public #[non_exhaustive] enum perhaps defined in wasmtime itself?

@alexcrichton That's a good suggestion, for my personal use case I'd prefer that it were exhaustive but I get that for versioning it's best for it to not be.

@alexcrichton Done!

Thanks again for this!


Add firmware version node

Fixes #31

Pull Request Test Coverage Report for Build 55

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.8%) to 95.775%

Totals

Change from base Build 53:
1.8%

Covered Lines:
112

Relevant Lines:
116

💛  - Coveralls

Pull Request Test Coverage Report for Build 55

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.8%) to 95.775%

Totals

Change from base Build 53:
1.8%

Covered Lines:
112

Relevant Lines:
116

💛  - Coveralls


check slice capacity to avoid unnecessary memory allocation

When I use function https://github.com/ClickHouse/ch-go/blob/main/compress/writer.go#L21-L52, find https://github.com/ClickHouse/ch-go/blob/main/compress/writer.go#L23 don't need to createmake([]byte, maxSize+headerSize)when cap(w.Data) >= maxSize+headerSize
And for EncodeColumn, when b.Buf has enough capacity, then no need to create make([]byte, size*len(v)), here are some examples:
https://github.com/ClickHouse/ch-go/blob/main/proto/col_decimal64_unsafe_gen.go#L31-L45
https://github.com/ClickHouse/ch-go/blob/main/proto/col_int64_unsafe_gen.go#L31-L45

Hey, compiler should optimize w.Data = append(w.Data[:0], make([]byte, maxSize+headerSize)...) anyway in the way that you are proposing.

cool, thanks for answer.


eos smart contract dosen't update

Hi guys! I'm creating a simple game by following the tic tac toe tutorial. But when recompiling the .wast and the .abi file, the cleos set contract doesn't recognize the changes made. Even when creating a new account, the new code is not recognized.

I have tried the other posts, but not found a solution. Any help is greatly appreciated.

Hi @compjotr, what's the change that you have made to the code before and after? If you make a change that will be skipped by the compiler (for example, declare an unused variable), it will result in the same code.

@andriantolie i have made real changes. Added a function that is also added to the abi file, but the compiled contract dosen't see it. Also print statements, to all functions to see if they are running.

That's strange. How do you compile the contract and how do you set the contract?

➜  rock_paper_scissors git:(master) ✗ eosiocpp -o rock_paper_scissors.wast rock_paper_scissors.cpp
➜  rock_paper_scissors git:(master) ✗ eosiocpp -g rock_paper_scissors.abi rock_paper_scissors.cpp
987970ms thread-0   abi_generator.hpp:68          ricardian_contracts  ] Warning, no ricardian clauses found for rock_paper_scissors
987970ms thread-0   abi_generator.hpp:75          ricardian_contracts  ] Warning, no ricardian contract found for create
987970ms thread-0   abi_generator.hpp:75          ricardian_contracts  ] Warning, no ricardian contract found for restart
987970ms thread-0   abi_generator.hpp:75          ricardian_contracts  ] Warning, no ricardian contract found for close
987970ms thread-0   abi_generator.hpp:75          ricardian_contracts  ] Warning, no ricardian contract found for move
987970ms thread-0   abi_generator.hpp:75          ricardian_contracts  ] Warning, no ricardian contract found for hi
Generated rock_paper_scissors.abi ...
➜  rock_paper_scissors git:(master) ✗ cleos set contract letsplay rock_paper_scissors
Reading WAST/WASM from rock_paper_scissors/rock_paper_scissors.wast...
Assembling WASM...
Publishing contract...
991663ms thread-0   main.cpp:2756                 main                 ] Failed with error: Assert Exception (10)
Error for localnet :
991662ms thread-0   http_plugin.cpp:405           handle_exception     ] FC Exception encountered while processing chain.push_transaction
991662ms thread-0   http_plugin.cpp:406           handle_exception     ] Exception Details: 10 assert_exception: Assert Exception
account.code_version != code_id: contract is already running this version of code
{}
thread-0  eosio_contract.cpp:151 apply_eosio_setcode
{"_pending_console_output.str()":""}
thread-0  apply_context.cpp:62 exec_one

rock_paper_scissors git:(master) ✗ eosiocpp -o rock_paper_scissors.wast rock_paper_scissors.cpp
rock_paper_scissors git:(master) ✗ cleos set contract letsplay rock_paper_scissors

You did the above commands from the same folder? In that case, the one that is uploaded is not the one that you just generated, but instead is the one inside .../rock_paper_scissors/rock_paper_scissors/rock_paper_scissors.wast

Nice, cleaned up and run like you suggested, but same issue i'm afraid. I copied the function from the hello world contract, and try to run it, but the compiled code is not changed.

Still, the functions doesn't print the print statements to the terminal, any idea why?

Set contract-console = true in your config.ini and restart your nodeos

Thanks dude. saved me a lot of time and trouble. Have a good day!


Bump min Rust to 1.36 because of Travis test failure

smallvec is required for version-sync test

bors r+

bors try

bors try

bors r+


Add a CLI flag for disabling the command execution

Is your feature request related to a problem? Please describe.
The default config of git-cliff now runs typos to fix the typos in the commits:
https://github.com/orhun/git-cliff/blob/3c2fb6072612a38ab7c6ea41e7c2ae34435fde99/cliff.toml#L66-L71
Thus generating a changelog for the whole git history takes some time.
Describe the solution you'd like
We should add a command-line flag for disabling command execution in the cases where the user wants to generate a changelog without running external commands.
For example, git-cliff --no-exec will skip executing the commands defined in replace_command.
Describe alternatives you've considered
None.
Additional context
See #316 for additional discussion about typos implementation.

Hello @mamaicode 👋🏼
Yup, are you interested in making a PR? 🐻

Yep! Will look into this

Kindly ping 🐻 do you need any guidance on this?


Fix passing of command options to beforeBuild hook; add tests

It looks like one line of #232 got lost in the feat/demberize merge.

Thank you - that is definitely my error.


Please support building shared libraries instead of static libraries

Is your feature request related to a problem? Please describe.
Shared libraries make tracking dependencies much easier in the context of maintaining a port.
I am working on the FreeBSD port for filament and it would be very desirable if filament would be able to build shared libraries. This was it would be clear what other libraries binaries depend on.
Describe the solution you'd like
Project should respect cmake's standard variable BUILD_SHARED_LIBS.

Duplicate of issue #1075


[User Story 12] Blade's health bar

Description
As a player, I can destroy the blades by pushing metallic objects 3 times to the blades

Risk
Priority
Story Points
Ideal Hours

Medium
High
3
6

Tasks

[x] #72
[x] #73
[x] #95

finish all the tasks


Issue Configuring SET-2010 for different topologies

Describe the bug
Setup: SLSC connected via local nework. Using Veristand 2019 R3 f1.
Description: When I select different topologies for SET-2010, error -1074114556 appears.
To Reproduce
Steps to reproduce the behavior:

Open Veristand 2019 R3 f1. Create System definition file
Under Hardware/SLSC, right click -> Add SLSC Chassis. Connect with -> Hostname or IP Address. Hostname or IP Address -> IP address of SLSC Chassis.
Go to Modules. Select 'SLSC Switch' on Slot 1
Go to Slot 1 (SLSC Switch) node. Then click 'Autodetect' menu item. After a few seconds, you should see Model Number -> "SET-2010: 64 CH Routing Base SLSC Card" and Topology -> BaseCard
So far so good.
Now expand 'Slot 1 (SLSC Switch)' node. Then select 'Endpoint Configuration' node. You should see many items in the Endpoint list, each of which has 'Load (Default)' configuration assigned. Now scroll the list all the way down. After "XJ2Ch31n" endpoint, there are Instrument & Fault items such as 'XJ3Inst0p' and 'XJ3FaultD'. (Good)
Now under Custom Devices, create Routing and Faulting Custom Device
Go to Routing and Faulting/Endpoint Aliases
Click on Endpoint dropdown listbox, and check what's available. Notice that endpoints from J1Ch0p to XJ2Ch31n are all listed in the endpoints, but no instrument or fault items (such as 'XJ3Inst0p' or 'XJ3FaultD') are populated in the dropdown listbox. (Bad) Do not add anything here and go to the next step.
Now, go back to Hardware/SLSC/SLSCChassis/Modules/Slot 1 (SLSC Switch)
In the UI, change the Topology setting from 'BaseCard' to 'Slot2FaultCard' Error -1074114556 shows up. As a result, after the error occurs, click on the Slot 1 (SLSC Switch)/Endpoint Configuration node. The Endpoint list is now empty.

Expected behavior
At step 9, I should see the Instrument endpoints and Fault items.
At step 11, the error should not occur.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows 10
Veristand 2019 R3 f1

Additional context
Add any other context about the problem here.
My goal is to use SET-2010 such that my signals going through the module into Fault state.

FYI: I posted the same issue on NI forum here

Unfortunately this is a compatibility issue between the legacy topology format on the SET-2010 and the NI-SLSC Switch driver.
The SET-2010 was originally designed to work with an unofficial SLSC switching library, which allowed for the selection of multiple topologies simultaneously. When NI-SLSC Switch was created, the decision was made to follow NI-SWITCH's precedent and only allow for a single topology to be active. As a side-effect, the legacy daughter-card topologies on the SET-2010 are underspecified for NI-SLSC Switch, as they rely on the BaseCard topology being active as well. Only the default (BaseCard) topology will work out of the box.
The NI-SLSC Switch API does provide a way to use a custom JSON switch definition, rather than using the JSON stored on the module directly. The SLSC Switch custom device makes use of this; if you configure the module by using "Load from JSON" rather than auto-detecting, that JSON file will also be used at runtime.
You can attempt to create your own JSON file that "combines" the topology definitions from the SET-2010 (the BaseCard topology and whichever daughter card topologies are needed), and use the combined topology to configure the custom device and deploy. The format for the SLSC Switch JSON definition is described in the SLSC MDK; the JSON definitions for the SLSC-12251 and 12252 are installed as examples to C:\Program Files (x86)\National Instruments\Shared\NI-SLSC Switch\Modules.
Alternatively you could use the SLSC EDS custom device to control the modules, rather than this custom device.

@rtzoeller thank you for explaining what's causing this issue. I will see if I can create my own JSON file.

Hi @rtzoeller I am not sure if this issue should stay open or be closed. Please advise.

Thanks for following up on this; it can be closed.