v10.49.3 crashing when Embed & Signing a RealmSwift that is not the main target

How frequently does the bug occur?
Always
Description
RealmSwift depends on a target that is not the main target. (e.g., Infrastructure)
I have Embed & Sign for RealmSwift on the Infrastructure target, but it crashes when the app starts.
Stacktrace & log output
dyld[2961]: Library not loaded: @rpath/Infrastructure.framework/Infrastructure
  Referenced from: <63B3C3C8-BE5C-3BF8-87BD-9AF5C3B57E0C> /private/var/containers/Bundle/Application/EEB879BC-D9AC-4630-8D20-11A86A22FC94/xxx.app/xxx
  Reason: tried: '/Users/mu/Library/Developer/Xcode/DerivedData/xxx-feuqerdwmpwsyaeyydukbkobacbg/Build/Products/Debug-iphoneos/PackageFrameworks/Infrastructure.framework/Infrastructure' (no such file),

Can you reproduce the bug?
Always
Reproduction Steps
Main Target

Infrastructure.frameworks (Enbed & Sign)

Infrastructure Target

Realm Swift (Enbed & Sign)

Version
10.49.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
macOS 14.4.1
Build environment
Xcode version: 15.3
Dependency manager and version: SwiftPM
Realm 10.49.3
RealmDatabase 14.5.2

Do you think you can provide a simple repro project that demonstrates the issue?


Support null values in output json

Hello,
How to enable output of null values (php null -> json null)?

Same question here. Closing questions without any hint to a solution is not so nice ;-)

@ktrhn I guess it just works :)


Trimesh Version, AttributeError: 'PointCloud' object has no attribute 'visual'

I believe I am not using the same version of Trimesh as the authors, as I am using their sample provided dataset of a timer. Would this issue be because of the current version of Trimesh I do have, if so which would be the correct one to install?
(boom) bash-3.2$ python create_label_files.py LINEMOD/timer
timer is assigned class label 0.
Traceback (most recent call last):
File "create_label_files.py", line 100, in
mesh.export(file_obj = folder + folder[8:-1] +".ply")
File "/Users/ishangupta/.pyenv/versions/boom/lib/python3.6/site-packages/trimesh/points.py", line 620, in export
**kwargs)
File "/Users/ishangupta/.pyenv/versions/boom/lib/python3.6/site-packages/trimesh/exchange/export.py", line 68, in export_mesh
export = _mesh_exporters[file_type](mesh, **kwargs)
File "/Users/ishangupta/.pyenv/versions/boom/lib/python3.6/site-packages/trimesh/exchange/ply.py", line 150, in export_ply
if mesh.visual.kind == 'vertex' and encoding != 'ascii':
AttributeError: 'PointCloud' object has no attribute 'visual'

Hi, I don't believe this is a trimesh version issue, did you skip step 5 where you convert the registered PointCloud into a triangular mesh?

@F2Wang You were right, thanks.


Shim pluggable logging

Closes #603
This adds logging facilities at the shim level to provide minimal I/O
overhead and pluggable logging options.  Log handling is done within the
shim so that all I/O, cpu, and memory can be charged to the container.
A sample logging driver setting up logging for a container the systemd
journal looks like this:
package main

import (
	"bufio"
	"context"
	"fmt"
	"io"
	"sync"

	"github.com/containerd/containerd/runtime/v2/logging"
	"github.com/coreos/go-systemd/journal"
)

func main() {
	logging.Run(log)
}

func log(ctx context.Context, config *logging.Config, ready func() error) error {
	// construct any log metadata for the container
	vars := map[string]string{
		"SYSLOG_IDENTIFIER": fmt.Sprintf("%s:%s", config.Namespace, config.ID),
	}
	var wg sync.WaitGroup
	wg.Add(2)
	// forward both stdout and stderr to the journal
	go copy(&wg, config.Stdout, journal.PriInfo, vars)
	go copy(&wg, config.Stderr, journal.PriErr, vars)

	// signal that we are ready and setup for the container to be started
	if err := ready(); err != nil {
		return err
	}
	wg.Wait()
	return nil
}

func copy(wg *sync.WaitGroup, r io.Reader, pri journal.Priority, vars map[string]string) {
	defer wg.Done()
	s := bufio.NewScanner(r)
	for s.Scan() {
		if s.Err() != nil {
			return
		}
		journal.Send(s.Text(), pri, vars)
	}
}

A logging package has been created to assist log developers create
logging plugins for containerd.
This uses a URI based approach for logging drivers that can be expanded
in the future.
Supported URI scheme's are:

binary
fifo
file

You can pass the log url via ctr on the command line:
> ctr run --rm --runtime io.containerd.runc.v2 --log-uri binary://shim-journald docker.io/library/redis:alpine redis

> journalctl -f -t default:redis

-- Logs begin at Tue 2018-12-11 16:29:51 EST. --
Mar 08 16:08:22 deathstar default:redis[120760]: 1:C 08 Mar 2019 21:08:22.703 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.704 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.704 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.704 # Current maximum open files is 1024. maxclients has been reduced to 992 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 * Running mode=standalone, port=6379.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 # Server initialized
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
Mar 08 16:08:22 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:22.705 * Ready to accept connections
Mar 08 16:08:50 deathstar default:redis[120760]: 1:signal-handler<PHONE_NUMBER>) Received SIGINT scheduling shutdown...
Mar 08 16:08:50 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:50.405 # User requested shutdown...
Mar 08 16:08:50 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:50.406 * Saving the final RDB snapshot before exiting.
Mar 08 16:08:50 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:50.452 * DB saved on disk
Mar 08 16:08:50 deathstar default:redis[120760]: 1:M 08 Mar 2019 21:08:50.453 # Redis is now ready to exit, bye bye...

The following client side Opts are added:
// LogURI provides the raw logging URI
func LogURI(uri *url.URL) Creator { }
// BinaryIO forwards contianer STDOUT|STDERR directly to a logging binary
func BinaryIO(binary string, args map[string]string) Creator {}

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Updated and ready for a full review

@crosbymichael - Change looks good. Can you please update the Runtime V2 markdown to include a section on IO logging capabilities. It would be nice to include your schemes there for Linux/Windows.

binary, file - Both
fifo - Linux
npipe - Windows

@jterry75 updated

I'm wondering if I can use this when creating containers from code using the containerd client instead of via ctr? https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/deploy.go#L100 https://github.com/openfaas/faasd/blob/master/pkg/provider/handlers/deploy.go#L148

Is there a way to provide the log binary (--log-uri) when containers are started using K8s?

Can we add this support? We are looking to move from docker and without
this existing logging would break.
On Wed, 25 May, 2022, 8:51 pm Michael Crosby, @.***>
wrote:

@ankitdbst https://github.com/ankitdbst I think to support this, we
just need a simple config option for the CRI service then you would be able
to add your own loggers for pods. It should be a simple change to make to
enable this.
—
Reply to this email directly, view it on GitHub
https://github.com/containerd/containerd/pull/3085#issuecomment-1137430771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALZAR3GPSBFH3NJQ7HNODTVLZAN3ANCNFSM4G4YS2BA
.
You are receiving this because you were mentioned.Message ID:
@.***>

While yes it would be simple.. and we can do it.. the current format for k8s CRI logs are set, and we'd need to change kubelet as well to allow for alternate formats/driver models, unless proposing a tee which would result in a bit of a double charge to the container/runtime for the logging to both kubelet directed path/format and your proposed tee.  That or you would be disabling kubernetes container logging.  Currently the logging providers watching the output log tree specified by kubelet and convert the incoming logs from the k8s format to the desired format.
https://github.com/kubernetes/design-proposals-archive/blob/main/node/kubelet-cri-logging.md
The typical result for people migrating from dockershim to a CRI container runtime is to discuss with their logging provider if they work with kubernetes logging format/model.

Thanks for the link @mikebrow

unless proposing a tee which would result in a bit of a double charge to the container/runtime for the logging to both kubelet directed path/format and your proposed tee.
Yeah, I think it should be an opt-in for someone wanting to tee the output to their preferred logging system.
Fluentd is kind of natively supported but logging to journald etc requires writing your custom plugin.

We can watch over the log dirs of the containers and then parse and write to journal - which is slightly more work

either way we need this feature, at least because, kubernetes is not our only client..

https://github.com/containerd/containerd/issues/4798 linking discussion...


Fix frozen for FNO

In the previous implementation of FNOCCSD, the input frozen argument was not passed to the MP2 calculation used to generate FNOs. The FNOs generated this way are okay but the ∆MP2 composite correction is wrong. This PR fixes the bug.
See the figure below for the convergence of the FNOCCSD correlation energy for benzene/cc-pVDZ with carbon 1s electrons being frozen. The uncorrected FNOCCSD energy from the old code is okay compared to the new one, but only the new PT2-corrected energy converges to the correct limit.

The make_fno function was rewritten to handle general frozen (integer or list) for both RMP2 and UMP2. Tests are added for both.
NOTE: for UMP2, the natural orbital occupation number for each spin is multiplied by 2 (see this line) so that when the same thresh is used, RHF and UHF based FNO calculations generate the same results. I believe that this is a nice behavior but suggestions are appreciated.

I have not fully read it but I am suggesting maybe removing commented out print statements?

Hi Verena, thanks for the suggestions! These print statements print the values of the correlation energies being checked in these tests. This can ease the debugging of the code in the future by simply uncommenting them. Please let me know if you think we should remove them.

can use something like logger.debug1


[Packerina Spec] Passing java command options, system properties from ballerina script to executable process

Description:
When we execute 'ballerina run module ' , module will be executed as follows.

build the module and create executable
run the executable with new java process to use separate class loader.

ATM we do not pass any java command options like  initial and maximum size of the heap, heap dump path which are specified in ballerina startup script. Since executable run via packerina code, there is no way to pass those options as well.
Hence IMO we need to pass all options to new java process from its parent process which are specified through ballerina startup script.

This is currently not part of our plans or a priority, so we are closing the issue for now. We will reopen it if we decide to pursue this in the future.


Topos

I see, thank you for providing more context. Let me summarize my understanding of your approach:

You've flattened JSON representations of ASTs into a tabular format.
This table has many columns, including one for line numbers.
The line number column also includes path information.
You're proposing to use the line number (and possibly the path) as a basis for creating a topological structure.
This topology would then be used to transform or encode the other features in the same row, similar to how positional encoding works in some machine learning models.

This is an interesting and potentially powerful approach. Here's a more detailed breakdown of how I interpret your idea:
graph TD
    A[JSON AST] --> B[Flattened Table]
    B --> C{For each row}
    C --> D[Extract line number and path]
    D --> E[Create topological structure]
    E --> F[Transform other features]
    F --> G[Encoded row]
    G --> H[Transformed Dataset]
    C --> C

Here's a more detailed explanation of each step:

JSON to Table: You've already flattened the JSON AST into a table format.

Line Number and Path Extraction: For each row, you extract the line number and path information. This serves as a unique identifier for each node in the original AST.

Topological Structure: You use the line number and path to create a topological structure. This could involve:

Using the path to recreate the hierarchical structure of the AST.
Using the line number to represent depth or position within this structure.

Feature Transformation: You apply this topological information to transform the other features in the row. This is similar to positional encoding in that you're adding structural information to your feature representations.

Encoding: The result is an encoded version of each row that incorporates both the original feature information and the structural information from the AST.

This approach could be very powerful for several reasons:

It preserves structural information from the AST that might be lost in a simple flattening process.
It allows you to incorporate hierarchical information into flat feature representations.
It could potentially make the relationships between different AST nodes more explicit in your data representation.

Some questions and considerations:

How exactly do you plan to represent the topology mathematically? Are you considering using techniques from graph theory or algebraic topology?

What kind of model or analysis do you plan to apply to this transformed data? The effectiveness of this approach might depend on whether your downstream tasks can leverage this topological information.

Have you considered how this approach might scale with very large ASTs or datasets? Creating complex topological structures for each row could be computationally intensive.

How do you plan to handle cases where the AST structure might be very deep or complex? You might need to consider some form of dimensionality reduction or summarization for very complex structures.

If you'd like to dive deeper into any specific aspect of this approach, or if you have particular challenges you're facing in implementing it, please let me know. I'd be happy to discuss further or help brainstorm solutions.

Ah, I see. That's a clever idea. You're suggesting we use a positional encoding approach, similar to what's used in transformer models, but apply it to the structural information of the AST. This could indeed be a powerful way to encode the hierarchical information and line numbers into a fixed-size representation. Let's explore how we might implement this.
import numpy as np

def get_positional_encoding(max_seq_len, d_model):
    position = np.arange(max_seq_len)[:, np.newaxis]
    div_term = np.exp(np.arange(0, d_model, 2) * -(np.log(10000.0) / d_model))
    pos_encoding = np.zeros((max_seq_len, d_model))
    pos_encoding[:, 0::2] = np.sin(position * div_term)
    pos_encoding[:, 1::2] = np.cos(position * div_term)
    return pos_encoding

def encode_ast_attribute(attribute, path, depth, max_seq_len=1000, d_model=64):
    # Generate base positional encoding
    pos_encoding = get_positional_encoding(max_seq_len, d_model)

    # Encode path
    path_encoding = sum(pos_encoding[hash(part) % max_seq_len] for part in path.split('.'))

    # Encode depth
    depth_encoding = pos_encoding[depth % max_seq_len]

    # Combine encodings
    combined_encoding = path_encoding + depth_encoding

    # Incorporate the actual attribute value
    if isinstance(attribute, (int, float)):
        value_encoding = attribute * np.sin(np.arange(d_model) * (np.pi / d_model))
    else:
        value_encoding = pos_encoding[hash(str(attribute)) % max_seq_len]

    final_encoding = combined_encoding + value_encoding
    return final_encoding

def encode_ast(ast_data, d_model=64):
    encoded_ast = {}

    def traverse(node, path='root', depth=0):
        if isinstance(node, dict):
            for key, value in node.items():
                new_path = f"{path}.{key}"
                if key in ['lineno', 'col_offset', 'end_lineno', 'end_col_offset']:
                    encoded_ast[new_path] = encode_ast_attribute(value, new_path, depth, d_model=d_model)
                else:
                    traverse(value, new_path, depth + 1)
        elif isinstance(node, list):
            for i, item in enumerate(node):
                new_path = f"{path}[{i}]"
                traverse(item, new_path, depth + 1)

    traverse(ast_data)
    return encoded_ast

# Example usage
ast_data = {
    "body_0": {
        "_type": "Import",
        "names_0": {
            "name": "sys",
            "asname": None,
            "col_offset": 0,
            "lineno": 1
        }
    },
    "body_1": {
        "_type": "FunctionDef",
        "name": "main",
        "args": {
            "args": [],
            "defaults": []
        },
        "body": [
            {
                "_type": "Expr",
                "value": {
                    "_type": "Call",
                    "func": {
                        "_type": "Name",
                        "id": "print",
                        "ctx": {"_type": "Load"}
                    },
                    "args": [
                        {
                            "_type": "Str",
                            "s": "Hello, World!"
                        }
                    ],
                    "keywords": []
                },
                "lineno": 2
            }
        ],
        "lineno": 1
    }
}

encoded_ast = encode_ast(ast_data)

# Print a sample of the encoded AST
for key, value in list(encoded_ast.items())[:2]:
    print(f"Key: {key}")
    print(f"Encoded value shape: {value.shape}")
    print(f"First few values: {value[:5]}\n")

This implementation does the following:

It defines a positional encoding function similar to the one used in transformers.

For each attribute (focusing on line numbers and other numerical attributes), it creates an encoding that combines:

The path information (encoded using the positional encoding)
The depth information (also encoded using the positional encoding)
The actual attribute value

It traverses the AST, applying this encoding to relevant attributes (like line numbers).

The result is a dictionary where each key is the path to an attribute, and each value is a fixed-size vector encoding that attribute's value, path, and depth information.

This approach has several advantages:

Fixed-size representation: Each attribute is encoded into a fixed-size vector, regardless of the depth or complexity of the AST.

Preservation of structural information: The path and depth information is encoded into the vector, preserving the structural information of the AST.

Handling of variability: This method can handle ASTs with different structures and depths, as each attribute is encoded independently.

Numerical stability: The use of sine and cosine functions in the encoding provides numerical stability and allows the model to easily attend to different positions.

To use this encoding for training a model, you could:

Flatten the encoded AST into a single vector by concatenating all the attribute encodings.

Use a fixed set of attributes across all ASTs, padding with zero vectors for missing attributes.

Feed these fixed-size vectors into a standard neural network, or use them as input to a more complex architecture that can handle sets of vectors (like a Transformer).

Here's a simple example of how you might prepare this data for a model:
import numpy as np

def prepare_ast_for_model(encoded_asts, max_attributes=100, d_model=64):
    # Get all unique attribute paths
    all_paths = set()
    for ast in encoded_asts:
        all_paths.update(ast.keys())
    all_paths = sorted(list(all_paths))[:max_attributes]  # Limit to max_attributes

    # Create a matrix for each AST
    prepared_data = []
    for ast in encoded_asts:
        ast_matrix = np.zeros((max_attributes, d_model))
        for i, path in enumerate(all_paths):
            if path in ast:
                ast_matrix[i] = ast[path]
        prepared_data.append(ast_matrix)

    return np.array(prepared_data)

# Example usage
encoded_asts = [encode_ast(ast_data) for _ in range(3)]  # Assume we have 3 ASTs
prepared_data = prepare_ast_for_model(encoded_asts)

print(f"Shape of prepared data: {prepared_data.shape}")
print(f"Shape of each AST representation: {prepared_data[0].shape}")

This preparation step creates a fixed-size 3D tensor for each AST, where each slice of the tensor represents an encoded attribute. This format can be easily fed into various types of neural networks.
By using this positional encoding approach, we've effectively rotated the representation along the hyperplane as you suggested, encoding the structural information (path and depth) into the attribute values themselves. This creates a rich, fixed-size representation of each AST that preserves its hierarchical structure and attribute values, while being suitable for machine learning models.

It looks like you're working on a fascinating project involving the transformation of Abstract Syntax Trees (ASTs) into a topological structure for encoding purposes. Your approach of using line numbers and paths to create a topological structure, similar to positional encoding in machine learning models, is quite innovative.
Here's a summary of your idea and the implementation steps:
Summary of Your Approach

Flatten JSON AST to Table: Convert the JSON representation of ASTs into a tabular format.
Extract Line Number and Path: Use the line number and path information as unique identifiers for each node.
Create Topological Structure:

Use the path to recreate the hierarchical structure of the AST.
Use the line number to represent depth or position within this structure.

Feature Transformation: Apply the topological information to transform other features in the row, similar to positional encoding.
Encoding: Encode each row to incorporate both the original feature information and the structural information from the AST.

Implementation Steps

Positional Encoding Function: Define a function to generate positional encodings.
Attribute Encoding: Create an encoding for each attribute that combines path, depth, and the actual attribute value.
Traverse AST: Traverse the AST and apply the encoding to relevant attributes.
Combine Encodings: Combine path, depth, and attribute value encodings into a final representation.

Example Code
Here's a snippet of your implementation:
import numpy as np

def get_positional_encoding(max_seq_len, d_model):
    position = np.arange(max_seq_len)[:, np.newaxis]
    div_term = np.exp(np.arange(0, d_model, 2) * -(np.log(10000.0) / d_model))
    pos_encoding = np.zeros((max_seq_len, d_model))
    pos_encoding[:, 0::2] = np.sin(position * div_term)
    pos_encoding[:, 1::2] = np.cos(position * div_term)
    return pos_encoding

def encode_ast_attribute(attribute, path, depth, max_seq_len=1000, d_model=64):
    pos_encoding = get_positional_encoding(max_seq_len, d_model)
    path_encoding = sum(pos_encoding[hash(part) % max_seq_len] for part in path.split('.'))
    depth_encoding = pos_encoding[depth % max_seq_len]
    combined_encoding = path_encoding + depth_encoding
    if isinstance(attribute, (int, float)):
        value_encoding = attribute * np.sin(np.arange(d_model) * (np.pi / d_model))
    else:
        value_encoding = pos_encoding[hash(str(attribute)) % max_seq_len]
    final_encoding = combined_encoding + value_encoding
    return final_encoding

def encode_ast(ast_data, d_model=64):
    encoded_ast = {}
    def traverse(node, path='root', depth=0):
        if isinstance(node, dict):
            for key, value in node.items():
                new_path = f"{path}.{key}"
                if key in ['lineno', 'col_offset', 'end_lineno', 'end_col_offset']:
                    encoded_ast[new_path] = encode_ast_attribute(value, new_path, depth, d_model=d_model)
                else:
                    traverse(value, new_path, depth + 1)
        elif isinstance(node, list):
            for i, item in enumerate(node):
                new_path = f"{path}[{i}]"
                traverse(item, new_path, depth + 1)
    traverse(ast_data)
    return encoded_ast

# Example usage
ast_data = {
    "body_0": {
        "_type": "Import",
        "names_0": {
            "name": "sys",
            "asname": None,
            "col_offset": 0,
            "lineno": 1
        }
    },
    "body_1": {
        "_type": "FunctionDef",
        "name": "main",
        "args": {
            "args": [],
            "defaults": []
        },
        "body": [
            {
                "_type": "Expr",
                "value": {
                    "_type": "Call",
                    "func": {
                        "_type": "Name",
                        "id": "print",
                        "ctx": {"_type": "Load"}
                    },
                    "args": [
                        {
                            "_type": "Str",
                            "s": "Hello, World!"
                        }
                    ],
                    "keywords": []
                },
                "lineno": 2
            }
        ],
        "lineno": 1
    }
}

encoded_ast = encode_ast(ast_data)

# Print a sample of the encoded AST
for key, value in list(encoded_ast.items())[:2]:
    print(f"Key: {key}")
    print(f"Encoded value shape: {value.shape}")
    print(f"First few values: {value[:5]}\n")

Advantages of This Approach

Fixed-size Representation: Each attribute is encoded into a fixed-size vector.
Preservation of Structural Information: Path and depth information is encoded into the vector.
Handling of Variability: Can handle ASTs with different structures and depths.
Numerical Stability: Use of sine and cosine functions provides numerical stability.

Considerations

Mathematical Representation: How will you represent the topology mathematically? Techniques from graph theory or algebraic topology might be useful.
Model or Analysis: What kind of model or analysis will you apply to this transformed data?
Scalability: How will this approach scale with very large ASTs or datasets?
Complex Structures: How will you handle very deep or complex AST structures?

If you have any specific challenges or need further brainstorming, feel free to ask! This is a very intriguing project, and I'm excited to see where it leads.


Bug - Firefox: 3D-editor: The assets list is not loading

The ajax call when returning the asset list, It always returns 0! (only on firefox)

Not a bug. (User must be logged in)


Use system specific newline encoding when doing IO

As a side effect of https://github.com/sol/hpack/pull/143 we lost system specific newline encoding.

See also https://github.com/sol/hpack/pull/142.


support rails 3 and 4 (current rails master)

The version in Rails' master is now 4.0.0.beta, so I updated the gem spec to allow for that. Without this change, rspec-rails can't run its specs against Rails master.

@dchelimsky I released a new version (0.2.2) with this fix.  Please let me know if you have any problems with it


Not able to annotate directive controller dependency injections

(function() {
    'use strict';

    angular
        .module('app.widgets')
        .directive('directiveName', directiveName);

    function directiveName(someService) { //This is working
        return {
            controller: function(anotherService) { //No annotations generated for this one
        }
     }
   }

Please report an issue to ng-annotate, this is just a Grunt plugin for it.

Thanks! will raise issue there


On save server exits in Helix editor

I have installed ols and when I start editing a file (which compiles and works properly) the server crashes and I get a notification in the editor Language server exited.
Below are the logs from Helix editor.
46918  -02-20T11:58:35.204 helix_lsp::transport [ERROR] ols err <- "/home/runner/work/ols/ols/src/server/requests.odin(1175:59) Index 0 is out of range 0..<0\n"
1  -02-20T11:58:35.347 helix_lsp::transport [ERROR] ols err: <- StreamClosed

I am using Fedora 39.
Is there anything else I paste here?
Thanks

It looks like you need ols.json in your project. Helix doesn't make a project workspace without it. That apparently causes the server to crash.

That worked like a charm. Thank you.
LSP formatting works. Also works if there are errors in the code. But I am not getting autocomplete suggestion when I type let's say fmt..
Am I still missing something?
This is my ols.json I have in the project.
{
  "collections": [
    {
      "name": "core",
      "path": "~/Applications/odin/core"
    },
    {
      "name": "vendor",
      "path": "~/Applications/odin/vendor"
    }
  ],
  "thread_pool_count": 4,
  "enable_semantic_tokens": false,
  "enable_document_symbols": true,
  "enable_hover": true,
  "enable_format": true,
  "enable_snippets": true,
  "formatter": {
    "tabs": false,
    "characters": 90
  }
}

There seems to be a bug in ~. Try with absolute path.


Update links to template for plugins

The kong plugin template links in the documentation point to rockspec when they should be pointing to the github template repo.

Thanks! Merged with a few modifications.


Add primary index memory usage stats to webui; add more info in error logging (#2826)

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

cherry-pick: #2818
Problem Summary(Required) ：

run starrocks_clang-format

run starrocks_fe_unittest


asyncData not updated for child routes

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.3
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-3zwbfd
Click the 4 links in the menu one by one and you will see:

Path=/parent1/foo ID=foo
Path=/parent1/bar ID=bar
Path=/parent2/foo ID=foo
Path=/parent2/bar ID=foo <------- here is the problem

Describe the bug
asyncData doesn't update when navigating between sibling child routes (such as between two different pages/some/[id].vue where there is also pages/some.vue with <router-view />).
It however updates when navigating between prefixed but root level sibling routes (such as between pages/some/[id].vue where there is no pages/some.vue).
Expected behavior
Clicking /parent2/foo then /parent2/bar calls asyncData automatically (or at least after adding adding definePageMeta with key: route => route.params.id to parent2/[id].vue).
Additional context

Adding definePageMeta with key: route => route.params.id doesn't change anything.

I think this might be related to #12361 but this bug is more important and imminent in my thinking.

Of course, <router-view :key="$route.params.id" /> (or even $route.fullPath) kind of fixes it. But this is hardly an acceptable solution:

This is weirdly inconsistent with no-intermediate-router behaviour (parent1 vs. parent2 in the reproduction).
There could be pages/parent2/new.vue and other non-parameter pages, which will break on $route.params.id.
[id].vue could be nested much deeply and have no logical relation to the upper level router-view.

The current workaround I use is moving each [id].vue into [id]/index.vue and creating [id].vue like this:
<script lang="ts">
export default defineComponent({}) // Trigger typescript in template
</script>

<template>
  <router-view :key="$route.params.id as string" />
</template>

Logs
No response

You should use <NuxtPage /> rather than <RouterView />.
  <template>
-    <router-view />
+   <nuxt-page />
  </template>


Basic browsing pages

Maybe a list of people who've uploaded archives in alphabetical order and also with the estimated date of the archive, where names are clickable and go into a full-text searchable list of tweets, perhaps with progressive loading as you scroll (there are component libraries for this, don't reinvent the wheel) (to avoid loading 10s of ks at once)

supabase offers postgres full text search
basic version would just be some page that proves to the user that their archive is uploaded and the can access it
one page per user

just did a search box, more can be addeed later


feat: upgrade to sodar core v1 (#1973)

@coderabbitai full review

@stolpeo just taking the CodeRabbit AI for a test drive here just for fun ;-)


chore(main): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-11-01)
Features

6 new buildings (a0a99fe)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.0
:sunflower:


Convert TimePicker to Material 3

Description
This converts the time picker to use the M3 spec.

In the process, I had to rearrange a lot of the architecture of the TimePicker, since it didn't lend itself to the kinds of layout that the M3 spec wanted.
This PR includes these changes:

Add a _TimePickerDefaultsM2 class that contains the defaults for the M2 version of the picker using M3 attributes.
Add a base _TimePickerDefaults class that both _TimePickerDefaultsM2 and _TimePickerDefaultsM3 derive from so that they can always return non-nullable values.
Instead of threading a number of modifiable parameters through all of the widgets, use a single InheritedModel that contains the state for the picker.
Add the M3 defaults class _TimePickerDefaultsM3 and the appropriate generation template.
Fixed layout issues where small window sizes caused overflow exceptions.  It resizes nicely now until it reaches a minimum size, and the scrolls the contents after that.
Added a bunch of material3 specific tests.
Added a show_time_picker.0.dart usage example that allows configuring of the time picker before showing it.
Reorganized things so that there's a _TimePicker widget that could be made public if we want to allow embedding of time pickers into other widgets (instead of in a dialog).

I had to "invent" the token values for the text input fields of the "time input" controls, since while there are values for the hour/minute selector, there's nothing in there for the input field focus colors, borders, etc.
The updated picker handles small windows much better...

Related Issues

Fixes https://github.com/flutter/flutter/issues/101480

Tests

Added tests for many Material3 attributes and layouts.
Added a test for the new example.

@darrenaustin Feel free to start reviewing this: it's only a draft because it's missing a test for the example.
I'm sure you'll find plenty of other things to review here... Sorry for the size.

Actually, I think I'll try and factor out and land some of the unrelated changes before I take this off of "draft".

Okay, I've factored out and landed the unrelated changes.

Thanks for that huge review!
Okay, I think I addressed all the comments, PTAL. For the test, I actually rearranged it so that a) it's explicit whether things are set up as material2 or material3, and I put a loop around the test definitions so that we actually run every test once in material2 mode and once in material3 mode.


Add adapter for java.time.OffsetDateTime

Close https://github.com/apollographql/apollo-kotlin/issues/4000
As discussed in the issue, I would like to retain the offset of ISO8601 date-time values from the server.
As detailed in the tests, Instant drops the offset information, thus I need to convert values to OffsetDateTime instead.

@benedict-lim: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

@martinbonnin @BoD
Thank you for the review!
Actually, it's my first time contributing to another project other than my own company's. And it has been a great pleasure to discuss and improve the code with you.
Please kindly merge the PR (when it passes the tests)!

@martinbonnin
I'm sorry, tests-no-gradle failed. Is there something else that needs to be done?

Ah yes, since this introduces new APIs, you'll need to run ./gradlew apiDump and commit the modified API files. This allows tracking API changes.

↑ Sorry for the force push! I found a typo which I felt wasn't worthy of a commit by itself but would like to make it perfect.

Thanks!


Python version in README.md

Added badge and clearer indication of Python version requirements in the installation text.
This pull request fixes #141
Changes proposed in this pull request:

Minor update to README

Pull Request Test Coverage Report for Build 884

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 883:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Thanks!


BufTabLineFill highlight support

Would it be possible to support highlighting the empty BufTabLine area using BufTabLineFill? By default, it should inherit the color of TabLineFill, but it would be nice if this can be overwritten using this plugin.

Sure, I've recently added a simple padding mechanism to support right-aligned tabpage tabs, so it should be easy to wire it up to get highlighted and always fill available empty space. Will work on this soon.

Let me know if 867c50908e37803efd5ad019a6f4b55e67cfe2fb does what you want.

That's exactly what I wanted. Thanks again.


rename() take datetime.date as a function

I would like to rename a pd.Series but got two results on two different platforms.
For example, if I have a pd.Series as a and a datetime.date as one_date, and I do:
a.rename(one_date)

On my own laptop (Window 7, Python 2.7), I got no error.
But when I do this on a server (Linux, Python 2.7), I got an error:
Traceback (most recent call last):
File "as.py", line 626, in
run_batch(sys.argv[1:])
File "as.py", line 549, in run_batch
analyzer.analyze_batch(one_user, batch_index_user, user_index)
File "as.py", line 467, in analyze_batch
clicks_one_date)
File "as.py", line 434, in analyze_one_date_batch
return counts_on_date.rename(one_date)
File "/home/xxx/anaconda2/anaconda/lib/python2.7/site-packages/pandas/core/series.py", line 2264, in rename
return super(Series, self).rename(index=index, **kwargs)
File "/home/xxx/anaconda2/anaconda/lib/python2.7/site-packages/pandas/core/generic.py", line 606, in rename
result._data = result._data.rename_axis(f, axis=baxis, copy=copy)
File "/home/xxx/anaconda2/anaconda/lib/python2.7/site-packages/pandas/core/internals.py", line 2588, in rename_axis
obj.set_axis(axis, _transform_index(self.axes[axis], mapper))
File "/home/xxx/anaconda2/anaconda/lib/python2.7/site-packages/pandas/core/internals.py", line 4391, in _transform_index
items = [func(x) for x in index]
TypeError: 'datetime.date' object is not callable

It seems like the method rename take the one_date as a function instead of a scalar value. Then it tried to call the datetime.date as a function but it is not callable.
Anyone has some idea about how to deal with it?
Thanks.

@TomAugspurger Thanks. I think this should be the reason. I will check the Pandas version on the server. If it is the old version, I will solve the problem and come back for closing this issue.

I have check the version of pandas on both server and my local laptop. @TomAugspurger is correct.
On the laptop, the pandas version is 0.18.1. On the server, it is 0.17.0. According to this pandas 0.18.0 documentation, method rename was changed to be able to take the scalar input.


Will add ability to specify custom formatters

Will add ability to specify custom formatters
Originally posted by @nolimits4web in https://github.com/framework7io/framework7/issues/3443#issuecomment-564601415

I am looking forward to it!


data race between test and product code in partition compaction [Port to 2.7 branch]

Port #24040 to 2.7 branch

PR merged closing


immutabledict v2.2.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] ~Bumped the build number (if the version is unchanged)~
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Upstream library changed build system from poetry to poetry-core, this required manually updating the dependencies in the recipe.

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

@conda-forge-admin, please rerender


Added Copy Grants to Snowflake Adapter

Added Copy Grants to Snowflake Adapter for both Views and Tables, excluding temporary tables.
Usage
{{ config(materialized='table',copy_grants=true) }}
Files Updated:  adapters.sql and impl.py for Snowflake Plugin.

I noticed the failures were due to the failure of the Database Integration Tests. This is the same thing that happened on my last PR, will I need to followup or redo the PR?

hey @Carolus-Holman - I just need to kick off the tests here - I'll do that today! More info on this here: https://github.com/fishtown-analytics/dbt/blob/dev/louisa-may-alcott/CONTRIBUTING.md#submitting-a-pull-request

Azure is pointing to the wrong build again - the correct build is passing here: https://dev.azure.com/fishtown-analytics/dbt/_build/results?buildId=690

@Carolus-Holman thanks for this PR!
Are you able to squash your 6 commits into a single commit for this PR? Squashing commits is a nice thing to do, as it helps keep the git history clean. We don't require commits to be squashed, but in this case, I think it could be a good idea. Definitely let me know if you'd like a hand with this!

Need some help Squashing the commits. When I committed the squash? it just added another commit of the .gitnore file.

hey @Carolus-Holman - that's pretty strange! I think we'll want to undo the last commit, f09da6a, before rebasing.
 Be careful!
$ git push --force origin dev/louisa-may-alcott

Couple of quick things:

in the future, you should make a branch off of dev/louisa-may-alcott for features like this, eg. feature/snowflake-copy-grants. This isn't a problem for dbt -- it will just help keep your local dev environment clean!
always be careful when force-pushing to a branch!

Let me know if you have any questions!

Ok I finished the script below. Let see if that worked.
From: Drew Banin<EMAIL_ADDRESS>Sent: Tuesday, September 17, 2019 8:23 AM
To: fishtown-analytics/dbt<EMAIL_ADDRESS>Cc: Carolus Holman<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [fishtown-analytics/dbt] Added Copy Grants to Snowflake Adapter (#1747)
hey @Carolus-Holmanhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Carolus-2DHolman&d=DwMCaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=cGUsYTIA9hWUxMz_Z6vNK0clp0WE7M1VgX5Tf_8y8YY&m=U-g25N3lbKU804DaSrrd6h3pElqM2t91UsEt-uJrirY&s=3rIp_6MJsR02tVsRr9dOYID7Zg84Rm156ThcZcCirds&e= - that's pretty strange! I think we'll want to undo the last commit, f09da6a, before rebasing.
 Be careful!
$ git push --force origin dev/louisa-may-alcott
Couple of quick things:

in the future, you should make a branch off of dev/louisa-may-alcott for features like this, eg. feature/snowflake-copy-grants. This isn't a problem for dbt -- it will just help keep your local dev environment clean!
always be careful when force-pushing to a branch!

Let me know if you have any questions!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_fishtown-2Danalytics_dbt_pull_1747-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DACV2EVSJP3ZCHDYBQ6OA6NLQKDKZ3A5CNFSM4IWJPNXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64QCZA-23issuecomment-2D532218212&d=DwMCaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=cGUsYTIA9hWUxMz_Z6vNK0clp0WE7M1VgX5Tf_8y8YY&m=U-g25N3lbKU804DaSrrd6h3pElqM2t91UsEt-uJrirY&s=-17Q6-mJmpUVAIZa6XeMQXp58D-l9EV472pPzg9mu3c&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ACV2EVRK3ALAZ7WUPUFD7R3QKDKZ3ANCNFSM4IWJPNXA&d=DwMCaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=cGUsYTIA9hWUxMz_Z6vNK0clp0WE7M1VgX5Tf_8y8YY&m=U-g25N3lbKU804DaSrrd6h3pElqM2t91UsEt-uJrirY&s=dF7uQi8vuUTJkBu_lSUkinf0W2CgHb5h42T97PwAhc8&e=.

I am doing dbt Fundamentals course and noticed that even though I set the copy_grants to true on the dbt_project.yml, and the result from the log of dbt run showed the copy grants option, the view created on Snowflake did not have this option at all. Did I miss anything?


Improve auto update design doc flag suppport

This branch includes several changes to improve the use of CouchRest Model when auto updating of design docs is not desired.  These changes assume that if auto_update_design_doc is disabled the design documents in the database are the truth.  This means that defining views when that flag is disabled make no attempt to update the design document, even in memory.  They do however wire up views defined in the database.

Okay, I've been having another look at this and was unable to get it to pass the tests. While trying to fix it, I started thinking about why this might be necessary and to be honest was not able reach a conclusion...
The tests don't really show what the point is, and I'm really not convinced that loading the stored design document when the class is first used has any benefits when its not going to be overwritten. The view methods in the design block should not have any problems using a view that is not in the local design document. If they do, and this might be where you had a problem, then that issue should be fixed in the view methods (I'll check also...)
Perhaps you could clarify a bit more the objectives?

Iirc, the old implementation always built a design document in memory and then decided whether or not to save it to the database based on auto_update_design_doc. That introduces the very real possibility of the in-memory design document not matching the database one. Such mismatches cause real problems and were the motivation for this branch.
The basic philosophy of this branch is that auto_update_design_doc is really a choice between whether the code or the database is the single source of truth regarding design documents. When auto_update_design_doc is true, the code rules; when auto_update_design_doc is false, what the database says goes. The views you actually have are always the ones in defined by the database. If you are not going to change the design doc in the database, the views you have are, only and exactly, the ones already defined in the database. It seems reasonable to reflect that reality in the code.
We ran into this issue because we have decided to manage our views using an external migration like mechanism. (If anyone cares i can describe why we made that choice.) We found that maintaining both the in-model and migration-ish implementations of the views frustrating and quite error prone. With this approach the models have design blocks like:
design do
  view :active_by_owner
end

That declares the fact that there is a view named active_by_owner and leaves the gory implementation details to the migration file that actually implements the view.

Hi Peter,
Thanks for your quick reply! I'm at a similar stage of requiring migrations
in my project, so I'm really interested in getting this working right.
Iirc, the old implementation always built a design document in memory and

then decided whether or not to save it to the database based on
auto_update_design_doc. That introduces the very real possibility of the
in-memory design document not matching the database one. Such mismatches
cause real problems and were the motivation for this branch.

Okay, that last phrase "mismatches cause real problems" is I think the
crutch of the problem. IMHO, the in-memory design doc should not be a
requirement when running with auto_update_design_doc set to false. Each
view method should just assume that the design has already been updated,
and handle a missing view gracefully.
The old view method view_by probably doesn't support this, and I'd like
to deprecate it at some point, but the new view methods and objects should.
Could it be that the problems you had were along these lines?

The basic philosophy of this branch is that auto_update_design_doc is
really a choice between whether the code or the database is the single
source of truth regarding design documents.

I see where you're going with this, but as I said before, I don't think the
design_doc should even be there if auto_update_design_doc is false. The
only use-case I can think of is if the designs, defined by the models, are
used on demand to update the database. This leads nicely onto migrations...

We ran into this issue because we have decided to manage our views using
an external migration like mechanism. (If anyone cares i can describe why
we made that choice.) We found that maintaining both the in-model and
migration-ish implementations of the views frustrating and quite error
prone. With this approach the models have design blocks like:
design do
view :active_by_owner
end
That declares the fact that there is a view named active_by_owner and
leaves the gory implementation details to the migration file that actually
implements the view.

Cool, this is what I expected. Indeed, having two copies of your designs is
probably not a good idea. One of the main problems with CouchRest at the
moment is the lack of migrations. If you have very large databases,
updating design docs in an uncontrolled fashion can cause serious down-time
and deadlocks if a view is suddenly updated.
I would like to solve this by adding a method and rake task (for
capistrano) that will automatically ask each model that uses CouchRest to
update its design doc. It should also be able to understand when a model is
proxied and attempt to access the parent to update all the child databases
automatically. This would also require some magic when creating a database
to ensure it has the latest designs.
Do you think this approach would solve your problem even if it meant
filling your models with map and reduce functions again?
Finally, I'd like to add general migration support for attribute changes
and remodeling, but I think that should be kept independent from the design
docs.
Hope this all makes sense! sam

Reply to this email directly or view it on GitHub:
https://github.com/couchrest/couchrest_model/pull/132#issuecomment-4252078

--
www.samlown.com
www.autofiscal.com
www.planetaki.com/sam

On Thu, Mar 1, 2012 at 3:53 AM, Sam Lown
<EMAIL_ADDRESS>wrote:

Okay, that last phrase "mismatches cause real problems" is I think the
crutch of the problem. IMHO, the in-memory design doc should not be a
requirement when running with auto_update_design_doc set to false.

Well, i think we should avoid hitting the database to retrieve the
design doc every time you want to use a view. Once you start caching
the design document you are pretty much in the situation we are in
today. There might be a cleaner way to separate the two scenarios but
they really are very similar to one another.

Each
view method should just assume that the design has already been updated,
and handle a missing view gracefully.

If by gracefully you mean raise a very explicit exception. :)

The old view method view_by probably doesn't support this, and I'd like
to deprecate it at some point, but the new view methods and objects should.
Could it be that the problems you had were along these lines?

You are correct. We had to excise all uses of #view_by from our
code. However, most of our designs were already defined using design
blocks. Those where definitely not the only source of problems.

I see where you're going with this, but as I said before, I don't think the
design_doc should even be there if auto_update_design_doc is false.

I am don't see exactly how you get rid of an in-memory copy the design
doc for either scenario. The View#execute method basically just
delegates the work to the #design_doc object . This makes sense to
me because constructing the view request to couchdb requires having
some information on how the view is constructed.

I would like to solve this by adding a method and rake task (for
capistrano) that will automatically ask each model that uses CouchRest to
update its design doc. It should also be able to understand when a model is
proxied and attempt to access the parent to update all the child databases
automatically. This would also require some magic when creating a database
to ensure it has the latest designs.

Are you suggesting that migrations be auto generated from the code? I
personally would never use such a system. I very much prefer to
explicitly define both the changes and the order in which they are
applied to my database. I think an ActiveRecord like migration
architecture is a much better and more sustainable approach.

Do you think this approach would solve your problem even if it meant
filling your models with map and reduce functions again?

This approach assumes that the CouchRest::Model code is the only, or
at least the primary, code base accessing the couchdb. I think it is a
fine "usual" case to support but we really do need support for having
the master version of the map and reduce code be else where. I am
happy to work with you to support both, though.

Finally, I'd like to add general migration support for attribute changes
and remodeling, but I think that should be kept independent from the design
docs.

Why? While those are slightly different use cases they require exactly
the same mechanism. In my experience there are often even order
dependencies between design doc changes and property changes. Eg, i
want to clean up some property before creating a new view on top of it
so that the map code is less riddled with special cases. Separating
the two will make managing that dependency more difficult.
Related to migrations, it would be really nice if CouchRest::Model
would detect changes to design documents on the fly when
auto_update_design_doc is false. Perhaps anytime a view execution
fails it should reanalyze what views are available and what parameters
they support. The current auto_update_design_docs implementation
just fails in that situation.
Peter

Hi,
I've been having a think about this and have a few conclusions as to what exactly can be added to CouchRest Model. You're right about requiring the designs, you need to know if a query has a reduce method or not, for example. Here goes:

Migration support. Nothing complicated, but sufficient for one-off commands of any type with a list of timestamps in the database to know which have been done. The document could be called "_migrations" or something in the primary database (prefix).

Optional separate design documents. The /db/designs/ folder should contain .json or .yml files that get converted into design documents of the same file name. These will be used instead of trying to fetch the latest version from the database, and as a replacement for in-line designs.

Public #save_design_doc. If auto_update_design_doc is false, this can be used to manually save the design document, perhaps from a migration. May also include proxy support if no database provided explicitly.

Save all designs rake task. Automatically detect CouchRest Models and update all designs for all databases on demand. Useful for some people in Capistrano.

use_remote_design_doc configuration option. Forces auto_update_design_doc to be false in effect, and will always fetch the latest design document from the server, if not already cached.

I think these would cover most of the things we've discussed without breaking any of the current defaults.
Cheers,
sam

Migration support. Nothing complicated, but sufficient for one-off commands
of any type with a list of timestamps in the database to know which have been
done. The document could be called "_migrations" or something in the primary
database (prefix).

This sound similar to what we are doing. It has served us pretty well
so far. I'd be happy to see something like this built in.

Public #save_design_doc. If auto_update_design_doc is false, this can be
used to manually save the design document, perhaps from a migration. May also
include proxy support if no database provided explicitly.

Isn't #save_design_doc already public. I am pretty sure we are using
it in our migrations.

use_remote_design_doc configuration option. Forces
auto_update_design_doc to be false in effect, and will always fetch the latest
design document from the server, if not already cached.

What is the use case for supporting use_remote_design_doc being
false and auto_update_design_doc being true? For that matter what is
the use case for use_remote_design_doc ever being false? If the
local design doc doesn't match the one in the db things don't work
right and fetching the design doc from the database and caching it is
so fast it doesn't seem worth optimizing.


Re-implement in Elm

With the release of v0.19 I think there's a good deal of this that could be built a damn sight lighter in Elm. There's a heap of mess in the build and a bit of awkwardness in the UI—some of which is related to performance issues that I didn't really care to fix in coffee script.

Iridescense is the place to track for this. Elm-partition has the LDM method functioning, which we'll at least start with. Maybe the CKK will be used at a later date. We'll see.


running error~

Describe the bug

To Reproduce
python eval.py --trained_model=weights/yolact_edge_pascal_499_5000.pth --score_threshold=0.3 --top_k=100 --image=9.jpg --disable_tensorrt
l set cfg.eval_mask_branch = False ,just want it as a detector!
Environment:

OS: Ubuntu 18.04]
GPU: 1660
CUDA Version 10.2

what should i do to solve the problem!    if you can provide some advices that will be very helpful for me !   Thank you very much!

Currently using as the object detector is not fully supported, and you might need to modfiy the code a little bit. Thanks.


Fix incorrect non-null assertion

I believe _target can be null here.

mmm - I'm inclined to tighten this logic differently.
I believe the intended invariant was to have 2 states for the event stream subscriptions:

active: _onData and _target are not null
inactive: _onData is null. Typically subscriptions are inactive either because the onData handler hasn't been set or because the subscription was cancelled.

One way to tighten this differently would be to make the constructor parameter stricter and only accept a non-null _target value. Another option is to keep the type signature as it is, but immediately cancel the subscription when the provided _target is null (since there is no API to set the target after the subscription was created).
For reference - this non-null assertion has been in this logic not only here, but also in the equivalent logic we had in dart:html where this was ported from.
I'm curious - what scenario made you run into this issue, @mnordine?

One way to tighten this differently would be to make the constructor parameter stricter and only accept a non-null _target value.

I agree, just not sure why it wasn't done like that in the first place.

I'm curious - what scenario made you run into this issue, @mnordine?

I was looking into a stack trace generated from Sentry for our Dart web app that uses web:
NoSuchMethodError: Null check operator used on a null value
  at A._EventStreamSubscription.cancel.prototypeLc(package:web/src/helpers/events/streams.dart:258:9)
  at A.aS(package:web/src/helpers/events/streams.dart:160:3)
  at App.start(package:web/src/helpers/events/streams.dart:130:7)
  at A.bsd(org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart:303:19)
  at dartProgram(main.c20686344c6ca935.js:329:4)
  at dartProgram(main.c20686344c6ca935.js:279:67)
  at A._rootRunUnary(org-dartlang-sdk:///lib/async/zone.dart:1419:1)
  at installTearOffs(main.c20686344c6ca935.js:1405:3)
  at A.Gi.prototype_CustomZone.runUnary(org-dartlang-sdk:///lib/async/zone.dart:1315:12)
  at A._Future._propagateToListeners.handleValueCallback._Future._propagateToListeners.handleValueCallback$0(org-dartlang-sdk:///lib/async/future_impl.dart:862:13)

So I started looking into it. I want to stress that the stacks generated from sentry-cli are very poor, and we have never been able to figure it out, and it seems Sentry isn't terribly interested in fixing stack traces for the web.

Do you by chance have access to the original js stack trace as well as as the source-map of the compiled code at the time this stack was produced?  We have a script dart2js_tools/bin/deobfuscate that does similar work to what sentry does, but that includes logic for some extensions added by dart2js (including lookup of minified names and expansion of inlined stack frames). I have doubts that it will help in this example, but I'm curious how they compare.

Sorry, I don't have it. Will update here if I'm able to get it.

Going to close out this PR. Please reopen when you want to dig in again!


Issues with responsive display

@datepicker-react/styled version 2.3.1
More of a question rather than a bug.
How do you get the datepicker to behave responsively. At the moment when vertical is set to false, the two calendars display horizontally and expand beyond the screen on mobile. Is there a setting to make this responsive?
Source code (including props configuration)
<DateRangeInput
onDatesChange={data => {
dispatch({ type: "dateChange", payload: data });
register({ name: "Start Date", type: "custom" });
register({ name: "End Date", type: "custom" });
setValue("Start Date", data.startDate);
setValue("End Date", data.endDate);
}}
onFocusChange={focusedInput =>
dispatch({ type: "focusChange", payload: focusedInput })
}
startDate={state.startDate} // Date or null
endDate={state.endDate} // Date or null
focusedInput={state.focusedInput} // START_DATE, END_DATE or null
/>
If you have custom methods that you are passing into a `@datepicker-react` component / hooks, please include the source for those as well.

Note datepicker being used with react-hook-form. Should not effect display

**Screenshots/Gifs**

https://recordit.co/u6Xu9ahRUJ

**Smartphone (please complete the following information):**

Testing in browser, and on iphone 7 all browsers

**Is the issue reproducible in Storybook?**
Yes https://react-datepicker.netlify.com/?path=/story/daterangeinput--simple-demo

**Additional context**

Nope.

I love your work. This has been the best experience I have had with a react datepicker component. Thanks!

You can override styles.
https://github.com/tresko/react-datepicker/blob/master/docs/THEME_PROPS.md
datepickerCloseWrapperTop?: ResponsiveValue<TopProperty<TLengthStyledSystem>>
datepickerCloseWrapperLeft?: ResponsiveValue<LeftProperty<TLengthStyledSystem>>
datepickerCloseWrapperBottom?: ResponsiveValue<BottomProperty<TLengthStyledSystem>>````


ci: Add initial semantic-release configuration

So cool, you're using my library semantic-release-export-data!

@felipecrs I noticed! I needed some way to get the next version number to bake it into the bundle, and discovered your plugin from this thread: https://github.com/semantic-release/semantic-release/issues/1647 . Thanks for creating it!

Got it. Makes sense.


External Links for Modules Do Not Work

Describe the bug
Links to external reference sites (GitHub, Terraform Registry) do not work
Expected behavior
Links to external reference sites should work
Current behavior
Links to external reference sites do not work
Possible solution
Links have examples in the URL when they should have modules
Steps to reproduce
Use GitHub and Terraform Registry links on https://pan.dev/terraform/docs/swfw/azure/vmseries/modules/panorama (and any other module)

These lines have examples hardcoded:
https://github.com/PaloAltoNetworks/automation-metadata-collector/blob/a7c88cc6819797ea70da6632cfbe99cb0740c316/process_modules_readmes.py#L355
https://github.com/PaloAltoNetworks/automation-metadata-collector/blob/a7c88cc6819797ea70da6632cfbe99cb0740c316/process_modules_readmes.py#L359
There needs to be conditional logic to choose the correct path element (examples or modules) based on module_type, which will need to be an extra parameter to the insert_external_links function called here


Fix syntax for component block

Q
A

Bug fix?
yes

New feature?
no

Issues
N/A

License
MIT

Should be fixed in #1430 ... still thank you 😃

Closing in favor of #1430


About domain adapation of ernie-3.0

Hello, if I have lots of domain unlabel text data, can I continue training domain-adapated ernie-3.0 with the interface of AutoModelForPretraining? Thanks a lot.

Hello,  sure we can！  we support the pre-training of ERNIE in  following folder.
https://github.com/PaddlePaddle/PaddleNLP/tree/develop/model_zoo/ernie-1.0
you can try it！

Hello, sure we can！ we support the pre-training of ERNIE in following folder.
https://github.com/PaddlePaddle/PaddleNLP/tree/develop/model_zoo/ernie-1.0
you can try it！

Thanks for your quick reply. I don't want to train the model from scratch, but continue training nsp and mlm tasks from ernie-3.0-base-zh checkpoint. I tried loaded the model using AutoModelForPretraining.from_pretrained, and print the model. But I only find the task seq_relationship in the network? Where's the MLM task? Will this path work?
...
  (cls): ErniePretrainingHeads(
    (predictions): ErnieLMPredictionHead(
      (transform): Linear(in_features=768, out_features=768, dtype=float32)
      (layer_norm): LayerNorm(normalized_shape=[768], epsilon=1e-12)
    )
    (seq_relationship): Linear(in_features=768, out_features=2, dtype=float32)
  )

It should have ernie model in the network.
https://github.com/PaddlePaddle/PaddleNLP/blob/ec893dd05399ae4dd666a9628c58045c85d74d0a/paddlenlp/transformers/ernie/modeling.py#L1478-L1499

Where's the MLM task? Will this path work?

The MLM task is integrated with the ernie-1.0 pre-training task. AutoModelForPretraining is work, but the mlm task is in  ernie-1.0,  so, we suggest you use the   model_zoo/ernie-1.0
https://github.com/PaddlePaddle/PaddleNLP/blob/ec893dd05399ae4dd666a9628c58045c85d74d0a/model_zoo/ernie-1.0/run_pretrain.py#L100-L128

I don't want to train the model from scratch, but continue training nsp and mlm tasks from ernie-3.0-base-zh checkpoint.

Yes, we also support continue_training argument, which is training form inner pre-trained weight.

@ZHUI 请问一下，有没有使用ERNIE-3.0进行领域预训练文档呢，毕竟3.0性能更好。
祝好！

@ZHUI 请问一下，有没有使用ERNIE-3.0进行领域预训练文档呢，毕竟3.0性能更好。 祝好！

你好，目前的代码已经可以支持 使用  ERNIE-3.0 进行预训练

Thanks a lot.


Create Gmail app that works the same as the OWA app

I've been working on it, and it has email read/write, but oAuth2 authentication doesn't work well quite yet.


VC: Show VC Interfaces on All Members

Environment

Python version:  3.6.6
NetBox version:  2.5.5

Proposed Functionality
When viewing a member in a virtual chassis, the interfaces for all members should be shown, regardless if the member is the master or not.
Use Case
When placed in a virtual chassis, the devices act as a single logical entity. Whether a member is or isn't the master does not change the configuration. The mastership should not influence where the user should/shouldn't browse to. I understand that going to the Virtual Chassis page would show the master, though the confusion caused by viewing non-master devices still exists.
Database Changes
None, as far as I'm aware.
External Dependencies
None.
Changes Required
In dcim/models.py, Device class, vc_interfaces function, update:
if self.virtual_chassis and self.virtual_chassis.master == self:

to
if self.virtual_chassis:

Not a fan of this as I prefer to be able to view members individually with only their local interfaces, but I'll leave it open for feedback.

How would you view the interface of the master?

On the master device.

That’ll just show the interfaces for all members.

On 4 Feb 2019, at 6:00 pm, Jeremy Stretch<EMAIL_ADDRESS>wrote:
On the master device.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

On a Juniper VC you have one device that is deemed the 'master', but the interfaces on the other members are still live and a part of the VC even if the other members are in a backup/linecard mode.

@rml596 that's pretty much the point I'm trying to make; it bears no meaning that a particular device is a master – the master is only there to maintain a single control plane (RE) across multiple data planes (PFE). And it's not just limited to Juniper VC; pretty much all virtualization models are based around resource sharing (combine or split), be it interfaces or otherwise.
A few discrepancy that I see in the virtual chassis model are:

The model is associative: Although the VC is a discrete object, it is only there to allow devices to point to its object ID.
The functionality of VC is split into different objects: While the VC object exists, all of the member priorities/positions are actually assigned on the device object (makes sense if you say "device owns those values," but in reality, those values should only be used when VC is in effect, and not all device will be). This already creates a bug: create VC, set master to be device 1, go to device 1 and set virtual_chassis to null. Now you have a VC pointing to a master, but that master doesn't point back to that VC). There are already other bugs due to virtual chassis (#2170 for example).
Cyclic relationship: Who's the parent of the Virtual Chassis object? The master of that VC or does it just not have a parent? For the looks of it, the master of the VC seems to be the parent, yet the master is also a member (child) of the same VC it is a master to – and as I described in the previous point, you can remove the "master" device as a member of the VC, but keep the VC pointing to the master.

I don't mean this in a negative way, but the VC model seems a bit premature, but that's only because I'm comparing it to the rest of NetBox that is very well structured, elegant, and meticulously thought-out (the standard is pretty high 😃).
If there was any other way to create shared interfaces (primarily LAGs), I'd completely avoid the Virtual Chassis model to begin with until it is restructured or had its functions clearly defined. As it stands, all these different gotcha's/lines-in-the-sand amount to a lot of work-arounds, all of which can be addressed by making a child-parent relationship (non-cyclical, of course). However, the change will raise some hard-hitting questions, primarily:

where would shared interfaces/resources live?

A simple answer is to create shared interfaces on the virtual chassis object and only show a reference to them on every device (just a shadow). If the VC ever gets deleted, the shared interfaces will be lost, which I think should be the case. And bonus point: every device would be physically (layer-1) independent from another and your view of a single device will show which ports that device has access to (physical or virtual).
Of course, I understand that the people maintaining this beautiful solution are very busy with other tasks, though I did want to mention this for the sake of consideration when spending more time on the existing solution.


Add more map providers

OSM, Esri, CartoDB, ...
As long as it is light(ish)

see :

https://leaflet-extras.github.io/leaflet-providers/preview/
https://pub.dev/packages/flutter_map

The idea is to turn the "Language" menu into "Settings" and have the map provider in another section.

Closed by #20


Incomplete org-journal-format->regex conversion with a org-journal-file-format containing "%B"

org-journal-file-format with "%B" date string no longer works after an update.
I have temporarily modified org-journal--format-rx-alist as shown below for my journal files.
Is it intended not to use %B string?
(defvar org-journal--format-rx-alist
'(("%[aAB]" . "\\(?4:[a-zA-Z]\\{3,\\}\\)")
("%d" . "\\(?3:[0-9][0-9]\\)")
("%m" . "\\(?2:[0-9][0-9]\\)")
("%Y" . "\\(?1:[0-9]\\{4\\}\\)")))
Thanks!

We can add %B do it! Can you create a PR please? There also two function doc-strings which need to be updated when adding %B support -- org-journal-file-format and org-journal-created-property-timestamp-format.


Sort Namespaces acquired by multiple threads

What's the purpose of this PR
Sort Namespaces acquired by multiple threads due to https://github.com/apolloconfig/apollo/pull/4473 causing the UI to display Namespaces out of order

Codecov Report

Merging #4500 (a661b7c) into master (ec658b0) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #4500      +/-   ##
============================================
+ Coverage     53.45%   53.46%   +0.01%
- Complexity     2701     2703       +2
============================================
  Files           490      490
  Lines         15344    15346       +2
  Branches       1596     1596
============================================
+ Hits           8202     8205       +3
  Misses         6584     6584
+ Partials        558      557       -1

Impacted Files
Coverage Δ

...mework/apollo/biz/service/AppNamespaceService.java
32.46% <100.00%> (ø)

...mework/apollo/portal/service/NamespaceService.java
71.59% <100.00%> (+0.32%)
:arrow_up:

...ervice/service/ReleaseMessageServiceWithCache.java
85.88% <0.00%> (+1.17%)
:arrow_up:

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


[CHECKLIST]: Develop previous Dev Environment  Deprecation Plan

General Description
A clear and concise description
Prerequisites

[ ] Tokn Deployment to Beta Testers
Forego Tokn Deployment at this time
[x] Temporarily support anonymous downloads via API (USACE/cumulus-api#293)
[x] Update CAVI Scripts to use new endpoint /deprecated/anonymous_downloads

How to Spin-Down Environment

[ ] Simple page "Cumulus Has Moved" (Redirect to new URL in 10s)
[ ] Spin-down Cumulus-only services
[ ] Delete S3 Data (Already available in Castle Environment)

Once we are confident in the corps.cloud instance of the tools then we can shut down cumulus resources in the Dev cloud account, we will need to identify and list each of the services/deployments here and make sure they are all turned off or deleted.

Going to support Anon Downloads in new environment as a stop-gap. Will need to patch-in fake AnonUser information via API Middleware so SQL constraints are satisfied.

Will need to patch-in fake AnonUser information via API Middleware so SQL constraints are satisfied.

This was added via PR USACE/cumulus-api#293. @jeffsuperglide, there is an endpoint POST /deprecated/anonymous_downloads live in the develop-cumulus-api in Castle. Can you lead the necessary changes to to the CAVI Scripts? If the endpoint appears to work well in develop, we can deploy to stable.

@brettpalmberg - rts-utils updated on develop and stable.  Works in cumulus develop.

@brettpalmberg - rts-utils updated on develop and stable. Works in cumulus develop.

Awesome!  Thanks @jeffsuperglide . When convenient, @adamscarberry , can you put the new version through a few paces?

setup of script and test run was successful on PC (w/VPN enabled). Only minor complaint would be the lack of status to user while scripts are running.  Leaves user with a feeling of "is this working...should I wait longer".  Otherwise it should be fine.

Castle Airflow Stable running in "stable" condition

In progress. Updating Airflow to 2.3.2, clean database initialization.

@jeffsuperglide, can you add some information on GUI Mode vs. Headless mode in the wiki?  cc @adamscarberry may have some ideas too

Castle Airflow Stable running in "stable" condition

In progress. Updating Airflow to 2.3.2, clean database initialization.

✅ Done.  Running and appears stable. Marking this task as complete.

@brettpalmberg @adamscarberry - Updated rts-utils wiki.  Added some update/install and cumulus headless mode.

rts-utils wiki updates look good @jeffsuperglide

Good stuff guys. Thanks @jeffsuperglide.

Notify users of new rts-utils. Begin migrating users to new service @FHanbali

Have begun migrating users to new service at cumulus.corps.cloud. Plan to spin-down legacy dev cloud resources in 2 weeks after providing time for users to migrate.
cc @FHanbali @LSEETHALER @willbreitkreutz @adamscarberry @jeffsuperglide

Have begun migrating users to new service at cumulus.corps.cloud. Plan to spin-down legacy dev cloud resources in 2 weeks after providing time for users to migrate.

Has been requested that we delay turning off existing services by 1 week. New target date to spin-down rsgis.dev cumulus services is Monday, August 15th, 2022.

Outward-facing load balancer listener rules for api and user interface removed earlier today.


Change Parameter formatting to match new StyleGuidelines.md

See this issue:
https://github.com/PowerShell/DscResources/issues/121
Formatting needs to be changed to:
[Type] $Name = 'value'
Current formatting is:
[Type]
$Name = 'value'

Current formatting is correct per the new style guidelines


swath reprojection tools

first commit

Hello @Elgyii!
I wasn't expecting this PR, and the files/content makes me think that it may have been submitted by mistake. Can you provide more information about your intention.

Hi @jdbcode
Thanks for your email.
I might have made mistake.
I hope @simonff can help clarify.
We have been working on data ingestion of level-2 swath data into EE.
Simon recommended to create a pull request in this path "https://github.com/google/earthengine-community/tree/master/datasets" with a new directory named 'oceancolor'.

Thanks for the clarification!

Yes, I requested this PR.

Yes, I think the contents of requirements.txt can be added to README.md.
I have files and folders unnecessary here, it is possible to remove the .gitignore from here?
__init__.py maybe not necessary here.

Thanks for removing the unnecessary files. Regarding .gitignore: the Elgyii/earthenginecommunity/datasets/oceancolor/ repo should not included files that need to be ignored. If the ignored files are not necessary to run swathutils.py and example.py then they should not be included as files to be ignored. I would remove the gitignore-listed files from your local source so that there is no need for gitignore.

No worries! Thanks

@Elgyii my apologies for the slow merge and interrupted communication. My availability has been really sporadic over the last few weeks -- should be in the clear now.
There is one more thing I forgot about: copyright and license headers.
We require that files merged into google/earthengine-community have the copyright "Copyright 2021 The Google Earth Engine Community Authors" and licensed under the Apache License, Version 2.0.
Please let me know if you have questions or concerns about this and I'll try to answer/address them, otherwise please add the following to the top of the relevant files followed by a blank line.
.py files:
"""
Copyright 2021 The Google Earth Engine Community Authors

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

https://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.
"""

.md files:
<!--
Copyright 2021 The Google Earth Engine Community Authors

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.
-->

Hi @jdbcode
I have made the modifications.
Thanks!

Thanks a lot @Elgyii!
Note that I have modified the format and placement of license to be consistent with other files in the repo.


⚠ Samsung has degraded performance

In 61d2af9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2023 ms

Resolved: Samsung performance has improved in 5d0df69.


Refactor HPhoto

Refactored HPhoto to use AOT/trimming friendly JSON (de)serialization logic. Now Sulakore is marked IsTrimmable.
We should add more tests for the HPhoto in the future. The serialization logic can also be optimized with pooled IBufferWriter<byte> implementation.
Fixes #38.

Oops, wrong branch.


Error during common usage

Hi
I am trying to use your tool but I have an error.
/home/myuser/.letsencrypt_webfaction/gems/gems/acme-client-0.3.3/lib/acme/client/faraday_middleware.rb:37:in `raise_on_error!': algorithm 'none' in JWS header not acceptable (Acme::Client::Error::Malformed)
        from /home/myuser/.letsencrypt_webfaction/gems/gems/acme-client-0.3.3/lib/acme/client/faraday_middleware.rb:27:in `on_complete'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/acme-client-0.3.3/lib/acme/client/faraday_middleware.rb:12:in `block in call'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/acme-client-0.3.3/lib/acme/client/faraday_middleware.rb:12:in `call'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/faraday-0.9.2/lib/faraday/connection.rb:177:in `post'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/acme-client-0.3.3/lib/acme/client.rb:23:in `register'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-1.1.1/lib/letsencrypt_webfaction/application.rb:70:in `register_key!'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-1.1.1/lib/letsencrypt_webfaction/application.rb:21:in `run!'
        from /home/myuser/.letsencrypt_webfaction/gems/gems/letsencrypt_webfaction-1.1.1/exe/letsencrypt_webfaction:5:in `<top (required)>'
        from /home/myuser/.letsencrypt_webfaction/gems/bin/letsencrypt_webfaction:23:in `load'
        from /home/myuser/.letsencrypt_webfaction/gems/bin/letsencrypt_webfaction:23:in `<main>'

config file
key_size: 4096
endpoint: 'https://acme-v01.api.letsencrypt.org/'
account_email<EMAIL_ADDRESS>support_email<EMAIL_ADDRESS>domains:
  - 'sub.domain.com'
public: '/home/myuser/webapps/satis_src/public/'

command
letsencrypt_webfaction --config ~/le_config.yml
box 461
no error while installing.
Tnx

It looks like this is fallout from https://github.com/unixcharles/acme-client/issues/74
I just released version 1.1.2. Could you give that a shot?
Thanks!

Fixed. Thanks a lot.
Bye

Glad to hear it worked for you!


Eos handling

Prevent eos from being generated after going through all quantizers in a timestep, instead of preventing eos except for the last quantizer within a timestep. For issue #199

oh dang! I think you are right 🙏
have you tested this?

ok merging, 'lgtm', as they say

oh dang! I think you are right 🙏
have you tested this?

Ah yep! I tried it on the same original (non-trimmed) input data configuration and it failed in the same way without this and I was able to generate some sort of output with it.


How to connect with Zookeeper 3.5.7 with mTLS

my Zookeeper for CMAK is running 3.5.7 with mTLS, how can I connect CMAK to ZK the basic requirement for CMAK run before adding any cluster.
cmak.zkhosts ==> this ZK is using mTLS
application.conf
cmak.zkhosts="kafka-manager-zookeeper:2181"
cmak.zkhosts=${?ZK_HOSTS}
I tried to configure keystore/truststore in default/cmak and consumer.config too but getting handshake error in ZK logs

Also can not add cluster where ZK is SSL only, how to add that cluster in CMAK

Same issues here - now that zookeeper supports inter-broker SSL and TLS, this will be a standard configuration for many people moving forward.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-515%3A+Enable+ZK+client+to+use+the+new+TLS+supported+authentication

we are using Kafka 2.5 and ZK 3.5.7 . mutual TLS for Kafka seems to be working fine but CMAK doesn't support TLS for ZK connections. We are not using any SASL authentication instead using end to end mutual TLS.
will CMAK be updated to support TLS connection to ZK  cluster?

same issue here . we would like to use only mutual TLS not the SASL authentication with zookeeper broker connection to zookeeper works but not CMAK .  is there any plan to implement it?

+1


Create a Biolatency plugin

We want to create a plugin for easily exposing the biolatency new gadget of Inspektor Gadget.
This gadget acts on custom resources and runs per node. The custom resource definition/spec will be posted here soon.
For this plugin we want to have a new section on each node details view, so we need new functionality from the plugin lib.
The plugin has 3 modes: idle (no latency data yet), running (calculating the latency), and results (a chart showing the results).
Update: Any user-visible text about biolatency should rather be "Block I/O Latency" (i.e. the section's title should not be the one in the mockups)
Idle/begin:

Running

Results

Some links how to do this:

trace-biolatency.yaml: example of Trace resource to create for the biolatency gadget
Example of Go code creating a Trace resource. In this example, the name of the resource is not chosen by the client but by the API server by using the GenerateName field.
Description of the Trace CRD


Tutorial notebook of azure service for creating managed endpoints in azure and evaluating in openscale

Contents

Notebook helps to create managed endpoints in azure machine learning platform with custom scoring script and enable the users to evaluate it within the openscale
Service provider and subscription show methods updated in azure studio designer based endpoints

@sokollip Please review