how to use vuetable-2 at local JSON file ?

Hello.
I want to use it at local JSON file.
I try this code.
<template>
  <vuetable ref="vuetable"
      api-url="../assets/test.json"
    :fields="fields"
  ></vuetable>
</template>

<script>
import Vuetable from 'vuetable-2/src/components/Vuetable'

export default {
  components: {
    Vuetable
  },
  data () {
    return {
      fields: [
        'name', 'email', 'birthdate',
        'address.line1', 'address.line2', 'address.zipcode'
      ]
    }
  }
}
</script>

file file structure.

Bad out this error.

please tell me how to use it at local JSON file.
thank you.

If you want to use assets in vue-cli the best idea is to place them in the static folder. Move your json into static folder and request it with /static/test.json

@kawamataryo You will have to use Data mode by setting api-mode to false, then supply your own local data via data prop. See this codepen.
You can also combine with what @cristijora has suggested to make your code cleaner.
Please be aware, though, that sorting, paging, and page sizing are not yet work in this mode.
<vuetable
  :api-mode="false"
  :data="localData"
></vuetable>

@ratiw @cristijora  Thank you so much. I'll try it.


Unlike calico, loadbalancer IP: nodeport is not accessible, is this expected behavior? any configuration to control this?

I have a nginx service exposed with load balancer IP <IP_ADDRESS>  :
[sre@node-10-41-91-99 eaehhil (tu044:default)]$ k get svc nginx-service NAME            TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE nginx-service   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:32538/TCP   29m
Unlike calico, loadbalancer IP: nodeport (<IP_ADDRESS>:32538)is not accessible.
Check the Cilium service lists in the edge node, rule 15, 18 and 19 shows Cilium will handle loadbalancer IP+ service port, and also node IP + nodeport, but there is no rule for loadbalancer IP + nodeport.
root@node-10-120-127-92:/home/cilium# cilium service list
ID   Frontend                                Service Type   Backend
1    <IP_ADDRESS>:443                           ClusterIP      1 => <IP_ADDRESS>:60443 (active)
                                                            2 => <IP_ADDRESS>:60443 (active)
                                                            3 => <IP_ADDRESS>:60443 (active)
2    <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:4244 (active)
3    <IP_ADDRESS>:80                        ClusterIP      1 => <IP_ADDRESS>:4245 (active)
4    <IP_ADDRESS>:80                       ClusterIP      1 => <IP_ADDRESS>:8081 (active)
5    <IP_ADDRESS>:53                           ClusterIP      1 => <IP_ADDRESS>:53 (active)
                                                            2 => <IP_ADDRESS>:53 (active)
6    <IP_ADDRESS>:9153                         ClusterIP      1 => <IP_ADDRESS>:9153 (active)
                                                            2 => <IP_ADDRESS>:9153 (active)
7    <IP_ADDRESS>:8080                      ClusterIP      1 => <IP_ADDRESS>:8680 (active)
                                                            2 => <IP_ADDRESS>:8680 (active)
                                                            3 => <IP_ADDRESS>:8680 (active)
8    <IP_ADDRESS>:8080                       ClusterIP      1 => <IP_ADDRESS>:8680 (active)
                                                            2 => <IP_ADDRESS>:8680 (active)
                                                            3 => <IP_ADDRESS>:8680 (active)
                                                            4 => <IP_ADDRESS>:8680 (active)
11   <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:4443 (active)
12   <IP_ADDRESS>:9913                      ClusterIP      1 => <IP_ADDRESS>:10254 (active)
                                                            2 => <IP_ADDRESS>:10254 (active)
13   <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:8443 (active)
                                                            2 => <IP_ADDRESS>:8443 (active)
14   <IP_ADDRESS>:80                       ClusterIP      1 => <IP_ADDRESS>:8080 (active)
15   <IP_ADDRESS>:80                        LoadBalancer   1 => <IP_ADDRESS>:80 (active)
16   <IP_ADDRESS>:443                       HostPort       1 => <IP_ADDRESS>:443 (active)
17   <IP_ADDRESS>:80                         ClusterIP      1 => <IP_ADDRESS>:80 (active)
18   <IP_ADDRESS>:32538                     NodePort       1 => <IP_ADDRESS>:80 (active)
19   <IP_ADDRESS>:32538                           NodePort       1 => <IP_ADDRESS>:80 (active)
20   [2001:1b70:820d:221e::a78:7f5f]:32538   NodePort       1 => <IP_ADDRESS>:80 (active)
21   [::]:32538                              NodePort       1 => <IP_ADDRESS>:80 (active)

However if we manually add a rule for loadbalancer IP + nodeport in Cilium (rule 22), then the test connection will be successful.
root@node-10-120-127-92:/home/cilium# cilium service update --frontend <IP_ADDRESS>:32538 --backends <IP_ADDRESS>:80 --k8s-load-balancer --id 22
Deprecation warning: --id parameter will change from int to string in v1.14
Creating new service with id '22'
Added service with 1 backends
root@node-10-120-127-92:/home/cilium# cilium service list
ID   Frontend                                Service Type   Backend
1    <IP_ADDRESS>:443                           ClusterIP      1 => <IP_ADDRESS>:60443 (active)
                                                            2 => <IP_ADDRESS>:60443 (active)
                                                            3 => <IP_ADDRESS>:60443 (active)
2    <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:4244 (active)
3    <IP_ADDRESS>:80                        ClusterIP      1 => <IP_ADDRESS>:4245 (active)
4    <IP_ADDRESS>:80                       ClusterIP      1 => <IP_ADDRESS>:8081 (active)
5    <IP_ADDRESS>:53                           ClusterIP      1 => <IP_ADDRESS>:53 (active)
                                                            2 => <IP_ADDRESS>:53 (active)
6    <IP_ADDRESS>:9153                         ClusterIP      1 => <IP_ADDRESS>:9153 (active)
                                                            2 => <IP_ADDRESS>:9153 (active)
7    <IP_ADDRESS>:8080                      ClusterIP      1 => <IP_ADDRESS>:8680 (active)
                                                            2 => <IP_ADDRESS>:8680 (active)
                                                            3 => <IP_ADDRESS>:8680 (active)
8    <IP_ADDRESS>:8080                       ClusterIP      1 => <IP_ADDRESS>:8680 (active)
                                                            2 => <IP_ADDRESS>:8680 (active)
                                                            3 => <IP_ADDRESS>:8680 (active)
                                                            4 => <IP_ADDRESS>:8680 (active)
11   <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:4443 (active)
12   <IP_ADDRESS>:9913                      ClusterIP      1 => <IP_ADDRESS>:10254 (active)
                                                            2 => <IP_ADDRESS>:10254 (active)
13   <IP_ADDRESS>:443                       ClusterIP      1 => <IP_ADDRESS>:8443 (active)
                                                            2 => <IP_ADDRESS>:8443 (active)
14   <IP_ADDRESS>:80                       ClusterIP      1 => <IP_ADDRESS>:8080 (active)
15   <IP_ADDRESS>:80                        LoadBalancer   1 => <IP_ADDRESS>:80 (active)
16   <IP_ADDRESS>:443                       HostPort       1 => <IP_ADDRESS>:443 (active)
17   <IP_ADDRESS>:80                         ClusterIP      1 => <IP_ADDRESS>:80 (active)
18   <IP_ADDRESS>:32538                     NodePort       1 => <IP_ADDRESS>:80 (active)
19   <IP_ADDRESS>:32538                           NodePort       1 => <IP_ADDRESS>:80 (active)
20   [2001:1b70:820d:221e::a78:7f5f]:32538   NodePort       1 => <IP_ADDRESS>:80 (active)
21   [::]:32538                              NodePort       1 => <IP_ADDRESS>:80 (active)
22   <IP_ADDRESS>:32538                     LoadBalancer   1 => <IP_ADDRESS>:80 (active)

C:\Users\eaehhil>curl <IP_ADDRESS>:32538

Welcome to nginx!

Also, if we delete the nginx-service k8s, Cilium only removes the rules which were automatically created, it won't touch the rule which we manually created earlier.

@whlweb Thank you for this issue! Could you add a sysdump to this issue so we can help you further?

I don't see anywhere in the upstream Kubernetes spec for LoadBalancer that LoadBalancers should be accessible from the LoadBalancer service IP on the targetPort. I'm not sure I understand why you wouldn't just configure the LoadBalancer's port to be the same as the targetPort if you wanted the service to be accessible on that port for both the LB and NodePort service.

Thanks for getting back to me so quickly. Yeah, we’re using different ports for the load balancer and targetPort. It makes sense that Cilium acts this way.
We were just curious because with Calico, the load balancer IP works with both ports in our environment.

OK, in that case I think it's expected behavior. I find it a bit surprising that Calico works that way. If upstream Kubernetes sig-network defines the behavior one way or another then we could revisit this decision, but in the absence of such a call from the Kubernetes spec I think Cilium is operating correctly and as expected for this case.
I'll close this out as resolved for now, but if there is any indication from upstream Kubernetes that LB services should be accessible on the LB IP and backend port then feel free to post back on this PR below with the refercence and we can revisit this assessment.


Use a platform determiner which is available on all platforms

Should fix test failures in Entropy on Mac.

Hi @ryanbrandenburg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Travis ci seems to fail with PR... :shipit: once its green

It would be nice if we can make this repo also run on Mac (travis.yml) as its a core framework piece


unexpected behaviour when hitting back button on backup wizard

A. reproduce.

Go to backup this wallet.
see the welcome screen activity_backup_seed
Hit next;
Hit next;
Hit back
Hit back.
observe the backup failed message

expected:
7. see the welcome screen activity_backup_seed

Fixed


Translation button

As @Jorropo suggested, we can now add the crowdin link (http://berty.crowdin.com/) instead of 'cooming soon' on the contribute page (https://berty.tech/fr/contribute).
@cdeleeuwe can you handle it?
Thanks :)

@cdeleeuwe Merged! Thanks :)


fix: remove upper limit for required terraform version

/run pipeline

:tada: This PR is included in version 2.4.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix: AZTEC_PORT variable for devnet

AZTEC_NODE_PORT -> AZTEC_PORT
Log Availability Oracle contract address on node start

Benchmark results
Metrics with a significant change:

batch_insert_into_append_only_tree_16_depth_ms (8): 16.7 (+30%)
batch_insert_into_append_only_tree_16_depth_hash_ms (8): 0.707 (+30%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 19d2bbea and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
54,212
214,436
855,332

l1_rollup_calldata_gas
259,844
1,019,876
4,060,148

l1_rollup_execution_gas
354,030
1,139,324
4,281,549

l2_block_processing_time_in_ms
1,273 (+1%)
4,773
19,056

note_successful_decrypting_time_in_ms
223 (+2%)
621 (+2%)
2,232

note_trial_decrypting_time_in_ms
33.8 (+13%)
57.1 (+12%)
189 (+1%)

l2_block_building_time_in_ms
21,378
84,638
344,352

l2_block_rollup_simulation_time_in_ms
16,023
63,442
259,362

l2_block_public_tx_process_time_in_ms
5,327
21,120
84,701

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,417 (+1%)
31,905

note_history_successful_decrypting_time_in_ms
1,413 (+1%)
2,716

note_history_trial_decrypting_time_in_ms
171 (+2%)
233 (+4%)

node_database_size_in_bytes
18,673,744
35,823,696 (-1%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
334
44,664
27,457

private-kernel-ordering
214
45,777
14,627

base-rollup
1,741
175,344
933

root-rollup
83.1 (-2%)
4,192
825

private-kernel-inner
443
73,099
27,457

public-kernel-app-logic
275
32,254
25,379

merge-rollup
7.87
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,388
36,001

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
576
1,507

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.0292 (+2%)
655


[Migrated] Package Error: python-dateutil

Originally from: https://github.com/Miserlou/Zappa/issues/1927 by weasteam
Would you please support the newest version of python-dateutil?
ERROR: zappa 0.48.2 has requirement python-dateutil<2.7.0,>=2.6.1, but you'll have python-dateutil 2.8.0 which is incompatible.

dateutil is no longer pegged by zappa, a fresh install should resolve this issue.
Closing.


The .NET6 for Spark is WIP and .NET for Spark 3.3 commitment

The document needs to reflect that there is a renew commitment to update .NET for Spark to .NET6 and there is a commitment to support Spark 3.3
This will avoid Azure Synapse from loosing .NET companies and users  <= Urgent

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

ID: dd4f61cc-556c-692b-da5f-70e3986956d8
Version Independent ID: cd8ea6ca-26bb-d3ce-a758-537209b1080b
Content: Azure Synapse Runtime for Apache Spark 3.3 - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/apache-spark-33-runtime.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @eskot
Microsoft Alias: eskot

@GeorgeS2019
Thanks for your feedback! We will investigate and update as appropriate.

@GeorgeS2019
Thank you for bringing this to our attention.
I've delegated this to content author @ekote, who will review it and offer their insightful opinions.

Got it, thanks @Naveenommi-MSFT and @GeorgeS2019.
@GeorgeS2019, please update me (thru tagging) once the ETA to support microsoft-spark-3-3.jar for .NET 6 will be determined.

@ekote
Could someone let me know who is the PM for .NET for Spark.
Many users are very concerned if there is a serious commitment.
The blocking issue e.g. BinaryFormater, which exists since Dec 2020, remains unsolved.
If the issue since Dec 2020 remains unsolved, many of us lack confidence the future of .NET for Spark,.

@GeorgeS2019 I'm sorry I don't have the details on who the PM for .NET for Spark is, or if there is any.

@ekote, thx, I suspected. I ask other PM

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


[SQLLab] Timestamp column type metadata shows up incorrectly in left panel

If you look up a table in sqllab on the left hand side to see the table metadata, tables with timestamp types show up as:
<class 'superset.models.sql_types.base.literal_dttm_type_factory..TemporalWrapperType'>
Expected results
The correct type.
Actual results
<class 'superset.models.sql_types.base.literal_dttm_type_factory..TemporalWrapperType'>
How to reproduce the bug

Add schema and a table to the left panel for a table with a timestamp type to see the table metadata (we noticed this in Presto)
When the table metadata shows up see "<class 'superset.models.sql_types.base.literal_dttm_type_factory..TemporalWrapperType'>" for the type instead of the correct type

Left panel

Environment
(please complete the following information):

superset version: master

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Got the same error

I'll look into this


Florilège use case

Here is a first draft for Florilège use case:
FLORILÈGE (Gateway to French Plant Genetic Resources)
Designed primarily for the general public, Florilège provides access to all French plant biological resources centers. Its interface allows individuals to browse available plant accessions and gives them the possibility to order them. The listed accessions originate from 19 resources centers and concern around fifty plant species.
Florilège retrieves accession information from different BrAPI-compliant systems such as OLGA, an internal accessions management system, or FAIDARE. Leveraging the BrAPI implementation of these systems ensures standardized data retrieval from multiple sources, making the integration of new data sources that implement BrAPI an effortless process. The implementation of BrAPI is a prerequisite for the integration of any new database in Florilège.
Florilège is developed in Drupal 10, and uses xnttbrapi module (to easily connect to BrAPI compliant external databases)

added content to the manuscript


How to add degree sign?

Hi guys, could you help me with that issue? I just try this simple code:
<html>
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <link rel="stylesheet" href="katex.min.css">
    <script src="katex.min.js"></script>
</head>
<body>

<div id="katexBlock">
</div>

<script>
    var exp = "sin(30^{\circ})";
    var elem = document.getElementById("katexBlock");
    elem.innerHTML = katex.renderToString(exp);;
</script>

</body>
</html>

but result is:

The example works on http://khan.github.io/KaTeX/.  In this case though you don't need to wrap \circ in a group.  Also the \sin operator is the correct way to write "sin".  \sin(30^\circ).  Which version of KaTeX are you using?

I think the problem is that you're not actually escaping the backslash in your equation. Your line should probably read
var exp = "sin(30^{\\circ})";

You also probably should put a doctype at the top of your HTML file, or you might run into strange bugs.

xymostech, thank you! It works!


Upgrading serde_derive from 1.0.41 to 1.0.42 causes: ToTokens is not satisfied

For reference: https://travis-ci.org/bluejekyll/trust-dns/jobs/370662379
error[E0277]: the trait bound `proc_macro2::Op: quote::ToTokens` is not satisfied
  --> /home/travis/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-1.0.42/src/try.rs:12:5
   |
12 | /     quote! {
13 | |         #[allow(unused_macros)]
14 | |         macro_rules! try {
15 | |             (#dollar __expr:expr) => {
...  |
23 | |         }
24 | |     }
   | |_____^ the trait `quote::ToTokens` is not implemented for `proc_macro2::Op`
   |
   = note: required by `quote::ToTokens::to_tokens`
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

I believe you need to bump the version of quote as well. This impl was added in 0.5.2.

Thanks, I meant to try and do this last night, but haven't had a chance to.


macOS MPS support for torched-net?

Hi,
I'm new using all the "torch" things and I wonder if it is possible to somehow use the Metal Performance Shaders (MPS) for Accelerated PyTorch training on Mac with torchmd-net.
Thank you in advance.
David

Hi,
We do not have an osx build available in conda-forge yet. I have tried to build it but without success (I do not have an OSX machine to debug, nor the experience with the OS for that matter) https://github.com/conda-forge/torchmd-net-feedstock/pull/1 . It actually compiles, but a test fails and I do not know how to debug it.
I believe @sef43 was trying to build torchmd-net for OSX AFAIK, maybe he can share his insights :P

Ookay, thank you for your quick reply.

Yes there are two parts to this.

the package builds on macOS, I will share the instructions soon.
MPS acceleration will not be currently supported, this is because not all pytorch operations are supported by MPS yet. I can do a quick investigation and find out what will need to be changed/ worked around.

You can install torchmd-net on MacOS using the Linux build from source instructions.
pip install -e . will work provided you have the dependencies from conda installed.
You will need to set num_workers: 0 in the config yaml files otherwise the error in the feedstock will occur: https://github.com/conda-forge/torchmd-net-feedstock/pull/1
You will need to make it run on CPU, MPS does not work yet:

First problem is:
[W MPSFallback.mm:13] Warning: The operator 'torchmdnet_extensions::get_neighbor_pairs' is not currently supported on the MPS backend and will fall back to run on the CPU. This may have performance implications. (function operator())
But it can fall back to CPU so can still run.

Second problem is:
/AppleInternal/Library/BuildRoots/f0468ab4-4115-11ed-8edc-7ef33c48bc85/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShaders/MPSNDArray/Kernels/MPSNDArrayGatherND.mm:234: failed assertion Rank of updates array (1) must be greater than or equal to inner-most dimension of indices array (2306) zsh: abort      PYTORCH_ENABLE_MPS_FALLBACK=1 torchmd-train --conf ET-QM9.yaml
which is probably this open issue: https://github.com/pytorch/pytorch/issues/94765

There are other unsupported pytorch operations in the get_neighbor_pairs code, e.g:
Warning: The operator 'aten::tril_indices' is not currently supported on the MPS backend
This is not something we can easily do from our end. Will have to wait on PyTorch to have implementations for the operations we need.

Just for completeness, when all required operations are available in that backend the neighbor extension can be made MPS-compatible by adding a new TORCH_LIBRARY_IMPL simply copy-pasting the CPU implementation:
https://github.com/torchmd/torchmd-net/blob/0275e5497ff234b55c3781c270bd0e45df79c0d0/torchmdnet/extensions/neighbors/neighbors_cpu.cpp#L92-L98
TORCH_LIBRARY_IMPL(torchmdnet_extensions, MPS, m) {
  m.impl("get_neighbor_pairs", [](const std::string &strategy,  const Tensor& positions, const Tensor& batch, const Tensor& box_vectors,
				    bool use_periodic, const Scalar& cutoff_lower, const Scalar& cutoff_upper,
              const Scalar& max_num_pairs, bool loop, bool include_transpose) {
      return forward(positions, batch, box_vectors, use_periodic, cutoff_lower, cutoff_upper, max_num_pairs, loop, include_transpose);
    });
}


Please add a documented way to get a list of all supported Perl of every platform

Please add a documented way to get a list of all supported Perl of every platform. Ideally this would be a Perl module. :-)
This would allow us to dynamically create the matrix without having to edit the workflow for every repository whenever there is a newer Perl version available.

It sounds good.
My idea is the following.
name: build
on: push
jobs:
  job1:
    runs-on: ubuntu-latest
    outputs:
      matrix: ${{ steps.perl.outputs.perl-versions }}
    steps:
    # outputs the list of 5.16 or laster versions to outputs.perl-versions
    - id: perl
      uses: shogo82148/actions-setup-perl@v1
      with:
        list-versions: ">=5.16"
  job2:
    needs: job1
    runs-on: ubuntu-latest
    strategy:
      matrix: ${{fromJson(needs.job1.outputs.matrix)}}
    steps:
    - uses: shogo82148/actions-setup-perl@v1
       with:
         perl-version: ${{ matrix.perl }}

Any suggestions?

That looks great.
How about the OS or distribution?

fixed by https://github.com/shogo82148/actions-setup-perl/pull/370


support for gemma2 w sample packing

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Social Handles (Optional)

needs https://github.com/huggingface/transformers/pull/31670 for sample packing to work


Geosearch test

Files in resources/sample_docs/geosearch:

greenland_rivers.wkt: this file isn’t used in any of the tests. It is used to test the file_to_wkt.py script--it converted the HydroRIVER dataset (shp files) for Greenland into the form of a wkt file. The HydroRIVER dataset is omitted from sample_docs.
grand_river.wkt is converted from grand_river.geojson
Other wkt files were written by me to test different functionalities of the Lucene API

Tests (used SimpleWKTShapeParser to load files):

Included 1 test for each of the relevant shapes: LineString, MultiLineString, Polygon, MultiLinePolygon
Included a test for a polygon with “holes” in it
Included a test for Lake Ontario, loaded from GeoJson
Included a test for a segment of Grand River, equivalent to the following:

Also included a script in tools/ (file_to_wkt.py) that converts files into the wkt format.

FYI: There is a bijection between the “relevant” Lucene types and WKL types:

LineString = Line, MultiLineString = Line[]
Polygon = Polygon (supports holes), MultiPolygon = Polygon[]

As a interesting side note, seems like Kibana doesn’t support the latest Lucene “Contains” query feature yet (released in 8.5.0), where we search for polygons containing a certain point/line/polygon. I've tested this feature out in the MultiPolygon and MultiLine tests.

Codecov Report

Merging #1766 (9fc5e4e) into master (5e8743f) will increase coverage by 0.26%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1766      +/-   ##
============================================
+ Coverage     57.31%   57.57%   +0.26%
- Complexity      998     1032      +34
============================================
  Files           167      173       +6
  Lines          9274     9785     +511
  Branches       1281     1345      +64
============================================
+ Hits           5315     5634     +319
- Misses         3522     3676     +154
- Partials        437      475      +38

Impacted Files
Coverage Δ

...main/java/io/anserini/collection/C4Collection.java
76.66% <ø> (ø)

...va/io/anserini/collection/C4NoCleanCollection.java
84.00% <ø> (ø)

.../anserini/collection/CommonCrawlWetCollection.java
74.35% <ø> (ø)

...ava/io/anserini/collection/DocumentCollection.java
57.33% <ø> (ø)

...o/anserini/collection/FeverSentenceCollection.java
83.63% <ø> (ø)

...in/java/io/anserini/collection/JsonCollection.java
84.61% <ø> (+10.54%)
:arrow_up:

.../java/io/anserini/collection/MrTyDiCollection.java
69.56% <ø> (ø)

...io/anserini/collection/MsMarcoV2DocCollection.java
69.38% <ø> (ø)

...nserini/collection/MsMarcoV2PassageCollection.java
79.62% <ø> (ø)

.../java/io/anserini/collection/WarcBaseDocument.java
42.68% <ø> (ø)

... and 41 more

Continue to review full report at Codecov.

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

@lintool I think in that case, it makes sense to remove sample_docs/geosearch/greenland_rivers.wkt altogether. It isn't used in any of the Java test cases since its sole purpose was to test the Python script. But the results of the Python script is already shown with grand_river.geojson and grand_river.wkt, so it may be redundant to do it again over greenland_rivers--let me know what you think.

@lintool I think in that case, it makes sense to remove sample_docs/geosearch/greenland_rivers.wkt altogether. It isn't used in any of the Java test cases since its sole purpose was to test the Python script. But the results of the Python script is already shown with grand_river.geojson and grand_river.wkt, so it may be redundant to do it again over greenland_rivers--let me know what you think.

Agreed. Let's remove sample_docs/geosearch/greenland_rivers.wkt.


[Release] sdk/resourcemanager/agrifood/armagrifood/0.6.1

https://github.com/Azure/sdk-release-request/issues/2965

@Alancere, it seems we created multiple PR for this service.  Is this expected?
Please close the duplicate items to avoid confusion


fix/refresh aliases on ctx change

Fixes: #517
This change shows the count of aliases available, but you were correct in #517 that it doesn't seem to be updating when we change ctx

to update the window title upon cache loaded, I was thinking of firing an autocmd and registering autocmd listener to that event.
on cache.lua, change the call on LoadFallbackData to M.load_cache() to this:
    M.load_cache(M.cached_api_resources, function()
      -- fire autocmd event KubectlCacheLoaded
      vim.schedule(function()
        vim.cmd("doautocmd User KubectlCacheLoaded")
      end)
      if callback then
        callback()
      end
    end)

on buffers.lua, after creating the alias buffer, register:
  -- autocmd for KubectlCacheLoaded
  vim.api.nvim_create_autocmd("User", {
    pattern = "KubectlCacheLoaded",
    callback = function()
      vim.print("KubectlCacheLoaded")
      -- check if win and buf are valid
      local _, is_valid = pcall(vim.api.nvim_win_is_valid, win)
      local _, is_valid_buf = pcall(vim.api.nvim_buf_is_valid, buf)
      -- if both valid, update the window title
      if is_valid and is_valid_buf then
        -- ...
      end
    end,
  })

WDYT?

@mosheavni found the issue, we were setting M.loading = false after the lineage feature was done, but if you have it turned off we never get there.
Moved it up and now it should work

if I open the alias float before the cache was loaded, I see an incomplete number that never changes

Sure thing!

done, let me know what you think of the code :)

Oh I see, you want to update it live and not when reopening it. I'll move the code up a step so it does the reload even for people that disable ctx

:tada: This PR is included in version 1.4.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


shape files for seasons MAC field scanner seasons 1 and 2

Description
We want to ensure that the plot-level means we generate for Terra MAC UAV flights are made using polygon coordinates and plot/entry attribute information  that correspond to the equivalent used in the batch extractors under development.   Is it possible for your team to generate shp file sets for seasons 1 and 2?
Completion Criteria

[x] shp file for seasons 1&2 provided to Rick
[x] instructions for repeating this export placed here and in documentation (https://github.com/terraref/documentation/pull/161)

I'll figure out the direct connection, but not this week.   Hoping to generate plot level means tomorrow.
I assume the shp file sets will contain range and column information- additional info on location attributes is welcome.

@rickw-ward see if these work mac_plots.zip
Here is the code that I used:
pgsql2shp -f season1.shp -h localhost -u bety -P bety bety \
         "SELECT sitename, geometry FROM sites WHERE sitename like '%Season 1 Range%'"
pgsql2shp -f season2.shp -h localhost -u bety -P bety bety \
         "SELECT sitename, geometry FROM sites WHERE sitename like '%Season 1 Range%'"

Note

for season 1

we used the term 'plot' rather than 'range and pass'
for each 'plot' we include separate definitions of both the full plot as well as the E and W subplots.

for season 2, we have definitions that use both the 'plot' and the 'range/pass' naming systems.

Let me know if you need additional information

checking now

@dlebauer please compare shp file set you sent with those in zips below to see offset in E/W axis.  Ours are for inner two rows only, but that doesn't explain offset.   The link below is to an in-season NDVI orthomosaic that shows actual rows (and foundations of gantry and sprinkler heads).
MAC 2 row season 2 sorghumexpfall2016v5_lblentry_1to7.zip
foundation and sprinkler shp files.zip
https://drive.google.com/open?id=0B5btztQSCEFxa1hJS3FpTm5mUnM

@dlebauer This screen  capture shows shift between our two plot polygons.  Sorry- I still can't consolidate into one directory.

I'll take a closer look at the files you sent later today.
Neither version eeds to capture the plot perfectly. I know we discussed at length last year... but perhaps we should create a new set that excludes the range ends and is better centered between columns.

I'll use my .shp files for season 2.   Perhaps the E/W shift of the shp file you sent is due to the conversion formula between coordinate reference systems?

Hopefully it isn't because of conversion between coordinate reference systems. There are obvious limitations to using different definitions of plot boundaries.
My understanding is that our database contains definitions from the F13_TERRA_field_book that were measured with the gantry and were to be considered the canonical plot definitions. That does not make these 'better', and I can change our definitions, but this would need to be done ASAP as we are launching our first re-analyses tomorrow or Friday.

looks like this discussion from last fall: https://github.com/terraref/computing-pipeline/issues/187 should have been resolved by https://github.com/terraref/computing-pipeline/issues/196.
It is unclear why there is still a discrepancy. In https://github.com/terraref/computing-pipeline/issues/187 I proposed that we could have multiple definitions of plots, but now I think we should try to identify a canonical definition of the plots.

@rickw-ward for season 2, it looks like we have defined the same plots as those in your shape files in addition to the other set of plots that do not align. In the image below you can see the plots from your shapefile (grey) with the plots in the database on top (thin red line):

I've deleted the plot definitions that do not align with the ones that you have from the database:
delete from sites where sitename like '%Field Plot%Season 2'
delete from citations_sites where site_id in (select id from sites where sitename like '%Field Plot%Season 2')
delete from sites_cultivars where site_id in (select id from sites where sitename like '%Field Plot%Season 2')

Good news David.  Thanks.

Here are the shapefiles for season 1, 2, 4
season124shpfiles.zip
Let me know if these work for you


Fix padding_idx

Someone mentioned in #923 that the non-streaming Transducer models tend to emit the first non-blank symbol at the very beginning. This PR alleviates this issue by removing the padding_idx in the decoder. Here are some results of pruned_transducer_stateless7 on LibriSpeech:

model
test-clean
test-other
average first symbol time (ms)

padding_idx=0
2.19
5.16
7.6

padding_idx=None
2.22
5.14
127

If someone needs this model, I can upload it to huggingface.

Here is the huggingface link to the new model: https://huggingface.co/marcoyang/icefall-asr-librispeech-pruned-transducer-stateless7-2023-03-10


Readme typos fix 1

Hi @terezka,
just some small doc fixes (thanks for providing such a useful library, BTW).
Kind regards,
Frank

Thanks for the fixes, @frankschmitt!


[feature request] Saving / Loading packed dataset

Hi team,
Can we save and load a packed dataset? I have a used case where I must train multiple models on the same packed dataset with identical sequence lengths. We could speed up the packing process by saving it and loading it for next time.
What do you think?

Hi @ScottHoang,
This would be an excellent feature to have and has been on our mind since we added packed datasets, but haven't been able to get around to yet. If you are open to contributing, would love to see an initial PR on this, and we can help review/get it in good shape.

Sure! I would love to contribute back.  Let me see what I can do

CC @winglian for his thoughts on caching the packed datasets. I believe axolotl already does something like this?

@RdoubleA If our plan is to move to online packing anyway, does this make sense as a direction to go in?

This wouldn't be fully online though, right? And we could still cache an iterable packed dataset?

What’s the benefit? For streamed datasets the packing would be based on the order of random shards, so you wouldn’t reuse the packing. And even if you downloaded the full dataset, how much time is online packing costing you? I doubt it would even impact total training time.

@pbontrager
Is there any update on this? Would be nice to have streaming dataset and still get similar benefits from using packing and FlexAttention on in-memory datasets.

cc @andrewkho, I imagine this would no longer be an issue with the torchdata integration as it packs on the fly?


connect not successful

Hi,
I can't connect the tv.
I try first using the web UI, but the error is the same: not_successful
2020-03-28 09:06:26 ERROR (MainThread) [custom_components.samsungtv_smart.config_flow] Error during setup of host <IP_ADDRESS> using configuration.yaml info. Reason: not_successful
HA and TV are on different subnets, but there is no firewall between them.
Where do you think the problem may be?
thx

Different subnet may have problem related to the routing. Is this the only error taht you see in the log?

Is the only error in the log.
2020-03-28 10:05:13 ERROR (MainThread) [custom_components.samsungtv_smart.config_flow] Error during setup of host <IP_ADDRESS> using configuration.yaml info. Reason: not_successful
The other devices that are on the same subnet as the TV do connect:
2020-03-28 10:04:27 INFO (Thread-3) [roomba.roomba] Connected to Roomba

Yes, but connection to the TV use different protocol and port. Are you using SmartThings in config?

lol, yes the tv was online and pinging tv from HA to verify the connection, during HA reboot
I use SmartThing.
And the popup never appeared on the tv screen.
My TV is QN65Q60RAGXZS

What is your TV model?
You should check settings for external device on your TV menu to be sure that connection check is done the first time.

What is your environment / OS? Are you using HASSIO?

My TV model is QN65Q60RAGXZS
And HA is a docker https://hub.docker.com/r/homeassistant/home-assistant over SynologyNAS (linux OS).
I review the TV menu, for external device item, it's ok too.

Honestly I'm not expert with HassOS / Docker installation but I think that you cannot run this custom_component because it use requests inside component script. You should have a manual installation on linux / rasbian / windows to make it work.

I will try that with a raspberrypi on the same subnet of the TV and I will tell you.
Thank you

Yes sir!.... You're right
In a HASSIO and in the same subnet, my TV model QN65Q60RAGXZS, works!
thx!!

Is any chance to add integration for TV Samsung which is in other VLAN than VLAN with HomeAssistant ?


Implement flake8_fixme

Summary
This PR implements flake8_fixme. Since that ruleset is extremely closely related to flake8_todos, I also made some refactors in the latter linter to remove duplicated logic and expose TodoDirectives across the codebase.
Closes #3859.
Test Plan
cargo t

This is an alias for a PyLint rule, shouldn't we move the relevant rule there? https://pylint.readthedocs.io/en/latest/user_guide/messages/warning/fixme.html

Yeah, it looks like T001 and T003 are aliases for that rule. Let's wait for @charliermarsh's confirmation but they look pretty similar to me.

@MichaReiser Re-requesting reviews since I made some large changes. I think they should help out in the long run for future TODO-related operations as well.


Data reorganization

Refactored data preparation code chunks to individual and task specific R files. Database loading script call on these scripts and inserts into SQLite database. Data now is housed in a central SQLite database which the main script calls. Renaming variables to be more explicit.

I figured I'd let you resolve the conflicts and merge in case there was anything else you wanted to add, but let me know if you want me to.


[JENKINS-21216] - Added support for Folder job type:

Allow type attribute 'Folder' in generated job
Fixed updating generated folder job
Allow using folder template
Removing generated folder jobs
Properly handle attempt to queue folder job
Allow using templates inside fold	ers

Sorry, what is the status for folders support?

Folder support has been added some time ago, see https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands#folder.
I left this PR open, because it shows how to add support for nested definition of folders like shown in the comments above. Currently path notation must be used to define nested folders.
Shall I pick this up and try to add nested definition of folder (and jobs, views, etc)?

I'll close this pull request because it can't be merged reasonably. If there is interest in adding support for creating nested items, please open a JIRA ticket or start a discussion on the mailing list.
Thanks to @vaidasn for working on this!


Bump Tika to avoid PDFBox conflicts

Apache tika 2.x.x wants old version of PDFBox 2.x, bump to tika 3.0.0-BETA that want PDFBox 3.x. With this we can use Tika as PDF reader.

Thanks @Grogdunn
I will merge the version update, but for my understanding did you see an actual failures while using the previous version?


CASSANDRA-18941: Support max SSTable size in sorted CQLSSTableWriter

Thanks for sending a pull request! Here are some tips if you're new here:

Ensure you have added or run the appropriate tests for your PR.
Be sure to keep the PR description updated to reflect all changes.
Write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
Read our contributor guidelines
If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:
<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

Thanks @Maxwell-Guo for spotting those! I am pushing a new commit to update and will check the other PRs too.

Closed the committed patch


Don't fail when multiple dynamic schemas exists

Just pick the first created one

LGTM

Addresses https://github.com/rancher/rancher/issues/4190#issuecomment-204226023

@cjellick I was thinking the same thing about order but https://github.com/rancher/cattle/pull/1606/files#diff-9e32237b2873876bb15aa51dd5138818R42 already existed so I just made the other query consistent.  WDYT?

LGTM


Chaoss Brand guide Documentation

The assets from the brand design will arranged in a PDF document format, summarizing the brand details on file.

@iamkingsleey Has this been worked on?
Do you know if new contributors can still work on this?

Nope, @Busayo-ojo

Is this still open?
cc @iamkingsleey @Busayo-ojo

Yes, it is @Mayaleeeee. I replied to your comment on another issue connected to this.


Uncaught Exception: Date in past. Will never be fired.

Current Behavior
NodeRed crashed with this output:
`11 Nov 09:09:01 - [red] Uncaught Exception:
11 Nov 09:09:01 - [error] Error: WARNING: Date in past. Will never be fired.
at CronTime.sendAt (/srv/node-red/.node-red/node_modules/cron/dist/time.js:93:23)
at CronTime.getTimeout (/srv/node-red/.node-red/node_modules/cron/dist/time.js:110:34)
at Timeout.callbackWrapper [as _onTimeout] (/srv/node-red/.node-red/node_modules/cron/dist/job.js:119:48)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 30min 39.255s CPU time.
nodered.service: Scheduled restart job, restart counter is at 2.
Stopped nodered.service - Node-RED graphical event wiring tool.
nodered.service: Consumed 30min 39.255s CPU time.
Starting nodered.service - Node-RED graphical event wiring tool...
Started nodered.service - Node-RED graphical event wiring tool.
11 Nov 09:09:24 - [info]
Willkommen bei Node-RED
11 Nov 09:09:24 - [info] Node-RED Version: v3.1.0
11 Nov 09:09:24 - [info] Node.js  Version: v20.5.1
11 Nov 09:09:24 - [info] Linux 6.1.0-rpi4-rpi-v7l arm LE
11 Nov 09:09:27 - [info] Paletten-Nodes werden geladen
11 Nov 09:09:30 - [info] Dashboard version 3.6.1 started at /ui`
and was automatically restarted
Expected Behavior
no crash
Steps To Reproduce
unknown
Example flow
No response
Environment

Node-RED version: 3.1.0
Node.js version: 20.5.1
npm version:
Platform/OS: Raspberry OS bookworm
Browser: no connection at this time

at also happened yesterday:
10 Nov 20:03:04 - [red] Uncaught Exception: 10 Nov 20:03:04 - [error] Error: WARNING: Date in past. Will never be fired.     at CronTime.sendAt (/srv/node-red/.node-red/node_modules/cron/dist/time.js:93:23)     at CronTime.getTimeout (/srv/node-red/.node-red/node_modules/cron/dist/time.js:110:34)     at Timeout.callbackWrapper [as _onTimeout] (/srv/node-red/.node-red/node_modules/cron/dist/job.js:119:48)     at listOnTimeout (node:internal/timers:573:17)     at process.processTimers (node:internal/timers:514:7) nodered.service: Main process exited, code=exited, status=1/FAILURE nodered.service: Failed with result 'exit-code'. nodered.service: Consumed 5h 32min 30.470s CPU time. nodered.service: Scheduled restart job, restart counter is at 1. Stopped nodered.service - Node-RED graphical event wiring tool. nodered.service: Consumed 5h 32min 30.470s CPU time. Starting nodered.service - Node-RED graphical event wiring tool... Started nodered.service - Node-RED graphical event wiring tool.

What nodes are you using in your flow that make use of times

inject, cron-plus

could this be caused by this construction:

[{"id":"2db6579cd0f577f4","type":"cronplus","z":"3c59326457645408","name":"cyclic","outputField":"payload","timeZone":"","storeName":"storeInFile","commandResponseMsgOutput":"output1","defaultLocation":"position","defaultLocationType":"env","outputs":1,"options":[{"name":"schedule1","topic":"cyclic","payloadType":"default","payload":"","expressionType":"cron","expression":"0 */10 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}],"x":370,"y":1220,"wires":[["36310bb25d3a61c2"]]},{"id":"32b2a623b9986069","type":"cronplus","z":"3c59326457645408","name":"active","outputField":"payload","timeZone":"","storeName":"","commandResponseMsgOutput":"output1","defaultLocation":"position","defaultLocationType":"env","outputs":1,"options":[{"name":"schedule2","topic":"start-all","payloadType":"default","payload":"","expressionType":"solar","expression":"0 * * * * * *","location":"","offset":"0","solarType":"selected","solarEvents":"sunriseEnd"},{"name":"schedule3","topic":"stop-all","payloadType":"default","payload":"","expressionType":"solar","expression":"0 * * * * * *","location":"","offset":"0","solarType":"selected","solarEvents":"sunsetStart"}],"x":210,"y":1240,"wires":[["2db6579cd0f577f4"]]}]

Yes it could be the cause, but it may also be that the time on your device is changing.
I haven't played with Bookworm yet, but I know the new Raspberry Pi 5 has a built in RTC so how Raspberry Pi OS keeps time will definitely have changed.
I suggest you raise this with the cron-plus node but also look in the journalctl logs to see if the time had been updated by something like ntpd around the time of the failure.

@m-schaeffler if you are seeing an issue with the cron-plus node, then please raise it in its repository - that is not a node the code Node-RED project maintains: https://github.com/Steve-Mcl/node-red-contrib-cron-plus


In Vuex tab, state's property value changes only when mutation occurs

Problem is when I update counter, Mutating only changes state's counter in vuex tab.
Otherwise when I update counter without mutation as described below then state's value doesn't change in vuex tab. And again when I do mutate, then it changes like direct from 2 to 8 .
I have two files which does counter increment and decrement.

Store which has state, getters and mutations

A counter which increments and decrements (but not mutating state)

A another counter which also increments and decrements (mutating state)

When I update counter through - counter( counter.vue ), it increments counter which is property in state.

Code -
this.$store.state.counter++; ( increment ) => this one doesn't affect state's property in vuex tab

When I update counter through - Another counter( Anothercounter.vue ), it increments counter which is property in state with mutation.

Code -
this.$store.commit('increment'); ( increment ) => this one affect state's property in vuex tab
Conclusion - Thing is state's value in Vuex tab only changes when I do mutation on state not when I do binding explicitly.

See here is the screenshot where I have

incremented from second row's increment button

and then decremented from first row's decrement button

You must use mutations to modify the state. Directly modifying the state is not valid and using strict mode will throw an error

Okay thanks for notifying @posva


Anerdw: Watch thegioiphutungoto.net

Anerdw requests the watch of the watch_keyword thegioiphutungoto\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thegioiphutungoto\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Dragonrage in Charcoal HQ


Assign application to specific workspace

Hi,
Is it possible to somehow permanently assign some application (for example Slack) to the specific workspace (for example Workspace 2)? I checked both provided configurations but didn't find any example, nor did I find it in the provided documentation. Probably, I miss something.
Thanks in advance.

https://nikitabobko.github.io/AeroSpace/guide.html#on-window-detected-callback
[[on-window-detected]]
if.app-id = 'com.tinyspeck.slackmacgap'
run = 'move-node-to-workspace S'


use dev-oidc in oidc-compliant mode by default, allow logouts

Description
Change the dev oidc mode to generic-oidc, and enable logouts.
Release notes:
n/a
Checklist

[ ] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)

Codecov Report

Merging #3502 (f061861) into main (d4546c5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #3502   +/-   ##
=========================================
  Coverage     80.50%   80.50%
  Complexity     2398     2398
=========================================
  Files           293      293
  Lines          9520     9520
  Branches        649      649
=========================================
  Hits           7664     7664
  Misses         1603     1603
  Partials        253      253

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Failed to start multiple apps at the same time

I run a local Cloud Foundry instance on VM for studying by cf_nise_installer. If there are two users to start apps at the same time, it fail often. the error message is "failed to accept connections within health check timeout". it seems modifying the startup time doesn't work (cf push ... -t 180). But if starting apps one by one, it success a lot. why?

There is no  memory or port issue.

Hi @YedengfengPig
What happens if you just have one app with multiple instances.  If you stop and then start it, do you get the same type of problem?  Trying to figure out if it is an issue with multiple different apps, or simply multiple instances (of same app or different app, shouldn't matter).

hi @Amit-PivotalLabs
It is an issue with multiple instances.
It looks like a single instance can be started by one time.
Is it because I have only one DEA server?

@YedengfengPig it shouldn't be an issue with having only one DEA server.  A DEA or Diego Cell can handle hundreds of instances, as long as the machine has enough compute resources.  Can you give more details of your deployment?  I don't know much about nise (and you may wish to open an issue against their repo), but maybe you can say what version of cf you're deploying, how it's configured, etc.

Hi @YedengfengPig any update?

hi @Amit-PivotalLabs
4 cpus  24G memory 100G disk  ubuntu 14.04
and this is dea.yml:

status:
port: 28888
user: dea
pass: "c1oudc0w"
nats_servers:

nats://nats:c1oudc0w@<IP_ADDRESS>:4222

dea_ruby: /usr/bin/ruby
pid_filename: /var/vcap/sys/run/dea_next/dea_next.pid
base_dir: /var/vcap/data/dea_next
warden_socket: /var/vcap/data/warden/warden.sock
evacuation_bail_out_time_in_seconds: 115
default_health_check_timeout: 60
crash_lifetime_secs: 3600
directory_server:
protocol: 'https'
v1_port: 12345
v2_port: 32766
file_api_port: 23456
streaming_timeout: 60
logging:
file: /var/vcap/sys/log/dea_next/dir_server.log
syslog: vcap.directory_server
level: debug
domain: <IP_ADDRESS>.xip.io
logging:
file: /var/vcap/sys/log/dea_next/dea_next.log
level: debug
syslog: vcap.dea_next
loggregator:
router: <IP_ADDRESS>:3456
shared_secret: c1oudc0w
index: 0
intervals:
heartbeat: 60
advertise: 5
router_register_in_seconds: 20
resources:
memory_mb: 16000
memory_overcommit_factor: 1
disk_mb: 32000
disk_overcommit_factor: 1
staging:
enabled: true
max_staging_duration: 900
memory_limit_mb: 1024
disk_limit_mb: 6144
cpu_limit_shares: 512
disk_inode_limit: 200000
instance:
memory_to_cpu_share_ratio: 8
min_cpu_share_limit: 1
max_cpu_share_limit: 256
disk_inode_limit: 200000
stacks:

name: cflinuxfs2
package_path: /var/vcap/packages/rootfs_cflinuxfs2/rootfs

placement_properties:
zone: default
cc_url<EMAIL_ADDRESS>

hi @Amit-PivotalLabs
cf-cli:
cf version 6.13.0-e68ce0f-2015-10-15T15:53:50+00:00
cf-release :
name: cf
version: '221'

@YedengfengPig
In the working case, do you know how long it takes to start and mark your application healthy? You will most likely need to look at the DEA log to determine this.
Give you are using a single VM for all of CF, I am thinking that it is just taking too long to start both containers.
The start timeout on cf push is how long the CLI will wait for the application to start before timing out.
You could adjust the health_check_timeout field on your Application via cf curl to a larger value or adjust the default timeout if this is going to be a common occurrence.

ok thanks


Minecraft crashes with MoreCommands and Wurst Client

When i try to launch Minecraft with MoreCommands mod and Wurst Client both installed, it crashes with exit code 0. I have fabric loader and Fabric API.
How can this be fixed?

Could you tell me what version of Wurst, MoreCommands, Minecraft and Fabric you're using?
I cannot replicate this issue with the upcoming release and Wurst v7.15.3 on Minecraft 1.17 with Fabric 0.11.6.


PHP: ran php-cs-fixer again

Ran php-cs-fixer again to fix coding style mistakes

Just core/msan failure on jenkins

LGTM


What's wrong with a new version of Scy Coop? On my friend's pc it's working without issues, but on my pc there is an error.

A newer version of the installer is available, please download the latest version. (If you have already downloaded the latest version and you see this message, it means that the installer does not have Internet access.)
How can i fix it
(My internet is working)

This is repository of the mod.

Here is repo of the intaller: https://github.com/RED1cat/SkyCoopInstaller/issues


OPA adapter not working in Mixer

I followed the instructions in this closed issue, but I just cannot make it work (see my comments at the end of the issue itself):
https://github.com/istio/istio/issues/13098

@liminw can you provide any guidance here?

We are not actively maintaining this feature currently. I suspect the samples may be out of date. @kyessenov or @douglas-reid are able to help answer the questions on Mixer config changes. If there are questions on OPA semantics, I will refer it to @tsandall.
On the other note, according to @mandarjog, the existing Mixer adapters will be deprecated in 1.3 release. With Mixer V2 proposal, some of the existing Mixer functionality will be moved to Proxy.


Support for OpenAPI v3

Is there a plan for this angular swagger implementation to Swagger UI version 3.2.1, which supports  OpenAPI specification?
https://github.com/swagger-api/swagger-ui
Maybe somebody already tried to do it with this project?

Hi !
I'm working on it but it's not finalized, i'll let you know when done


Documentation structure

We should try to follow this overall structure for documentation.

(see https://docs.divio.com/documentation-system/)
Status

[ ] Tutorials

[ ] I think the existing notebooks count as tutorials?

[ ] Explanation Long-form explanation of high-level concepts

[ ] What C-Star aims to do for you
[ ] Case vs blueprint
[ ] Some mention of future plans of providing pre-approved blueprints

[ ] How-to Guides

[ ] How to run an off-the-shelf configuration
[ ] How to set up your own domain from scratch
[ ] How to not get bottlenecked by regridding

[ ] Reference

[ ] API docs can be seen here, but might need filling out a little bit (e.g. following standard formatting, adding examples and cross-links where appropriate)
[ ] Glossary https://github.com/CWorthy-ocean/C-Star/issues/28

[ ] README (Rewrite to follow these recommendations)

Notes:

Want to link everything to everything

Having API docs and a glossary first would allow all written docs to have hyperlinks

The .. Note thing in RST/myst is useful for noting things that haven't yet been implemented (see VirtualiZarr docs for lots of examples of that)
High-level goals

Start from one of our existing written explanations (ask Matt for link)
We want a short and sweet version for the readme
and a more in-depth set of paragraphs for those who decide they want to read more
Diagrams would be worth many words
Development roadmap

Prioritize?

Explanation

Use so that we're all on the same page about goals

Glossary

Highest-level concepts first

Architecture diagram

Might not want to do this too early in case it becomes outdated?
Mermaid diagrams can be auto-generated from code to some extent / designed to be updated

De-prioritize writing Roadmap until after alpha?

Existing content

Split up long notebook on Using C-Star
Make Preparing input data for a ROMS simulation into a how-to guide?

User vs Developer

Distinction between someone who uses a pre-existing blueprint vs creates a new one


test integration with other gulp tasks

How should the gulp tasks karma and protractor integrate with the other gulp tasks?

should they be run, when running gulp watch? (not possible right now due lack of browsersync #228)
own karma-watch tasks? since gulp karma:auto cannot be forced to do checks when files change, neither re-runs it when app files change.
when they're run alone, should they perform style-checks etc? on which files?

From my perspective we should be fine for now with having them separated from the other gulp tasks. I think we need some time to figure out how and when we will run the tests.


⚠ Jenkins Plugins Artifactory has degraded performance

In ce01141, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1622 ms

Resolved: Jenkins Plugins Artifactory performance has improved in abedc33.


Unsupported os windows 10

I download latest swarmwr wrom https://jcenter.bintray.com/com/gojuno/swarmer/swarmer/0.2.2/:swarmer-0.2.2.jar and try tu run with command
java -jar swarmer.jar start
as a result I have an error:
Exception in thread "main" java.lang.IllegalStateException: Unsupported os windows 10, only [Lcom.gojuno.commander.os.Os;@19aa4dfd are supported.
        at com.gojuno.commander.os.ProcessesKt.os(Processes.kt:133)
        at com.gojuno.commander.os.ProcessesKt.access$os(Processes.kt:1)
        at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt:54)
        at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt)
        at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:72)
        at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:32)
        at rx.Observable.unsafeSubscribe(Observable.java:10346)
        at rx.internal.operators.OperatorSubscribeOn$SubscribeOnSubscriber.call(OperatorSubscribeOn.java:100)
        at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
        at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Hey, thanks for report, totally forgot to update https://github.com/gojuno/commander version here with windows support.

@yunikkk but what can I do with comnander? I have only single java file.

Ah, sorry for confusion, commander is other library used by swarmer and its version is too old here. So PR is needed here with commander update. Will do it later today.

Any progress here, guys? Can't run it on any version of Windows.

Yeah, PR in progress, some issues with tests though

Hey guys, try 0.2.3 version I've just published, should work on windows.

now is running
but i don't know what to do next
if I try to run with this parameters

java -jar swarmer.jar start --emulator-name test_emulator_1 --package "system-images;android-27;google_apis;x86" --android-abi google_apis/x86_64 --path-to-config-ini emulator_config.ini --emulator-start-options -prop persist.sys.language=en -prop persist.sys.country=US --redirect-logcat-to test_emulator_1_logcat.txt

i have an error

[Tue May 15 09:55:31 MSK 2018]: runningEmulators: retrying java.lang.IllegalStateException: Adb output is not correct: ..
[Tue May 15 09:55:31 MSK 2018]: runningEmulators: retrying java.lang.IllegalStateException: Adb output is not correct: ..
[Tue May 15 09:55:32 MSK 2018]: runningEmulators: retrying java.lang.IllegalStateException: Adb output is not correct: ..
[Tue May 15 09:55:32 MSK 2018]: runningEmulators: retrying java.lang.IllegalStateException: Adb output is not correct: ..
[Tue May 15 09:55:32 MSK 2018]: Error during getting connectedAdbDevices, error = java.lang.IllegalStateException: Adb output is not correct: .
Exception in thread "main" java.lang.IllegalStateException: Adb output is not correct: .
at com.gojuno.commander.android.AdbKt$connectedAdbDevices$2.call(Adb.kt:39)
at com.gojuno.commander.android.AdbKt$connectedAdbDevices$2.call(Adb.kt)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext(OnSubscribeMap.java:69)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext(OnSubscribeMap.java:77)
at rx.internal.operators.OperatorCast$CastSubscriber.onNext(OperatorCast.java:69)
at rx.internal.operators.OnSubscribeFilter$FilterSubscriber.onNext(OnSubscribeFilter.java:76)
at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.call(OperatorObserveOn.java:224)
at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: rx.exceptions.OnErrorThrowable$OnNextValue: OnError while emitting onNext value:
at rx.exceptions.OnErrorThrowable.addValueAsLastCause(OnErrorThrowable.java:118)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext(OnSubscribeMap.java:73)
... 13 more

@yunikkk can I open new issue?

@hram lets continue here since its basically the same issue.
I've digged commander sources once again and seems like a bug there for windows with output redirection.

https://github.com/gojuno/commander/pull/18

@hram should arrive in #39

@yunikkk now I have new error
> d:\swarmer>java -jar swarmer-0.2.4.jar start --emulator-name test_emulator_1 --package "system-images;android-27;google_apis;x86" --android-abi google_apis/x86 --path-to-config-ini emulator_config.ini
> [Wed May 23 11:43:46 MSK 2018]: Already running emulators: []
> [Wed May 23 11:43:46 MSK 2018]: Creating avd test_emulator_1.
> [Wed May 23 11:43:46 MSK 2018]: Error during creation of avd test_emulator_1, error = rx.exceptions.CompositeException: 1 exceptions occurred.
> [Wed May 23 11:43:46 MSK 2018]: Error during creation of avd test_emulator_1, error = rx.exceptions.CompositeException: 1 exceptions occurred.
> [Wed May 23 11:43:46 MSK 2018]: Error during creation of avd test_emulator_1, error = rx.exceptions.CompositeException: 1 exceptions occurred.
> [Wed May 23 11:43:46 MSK 2018]: Error during creation of avd test_emulator_1, error = rx.exceptions.CompositeException: 1 exceptions occurred.
> [Wed May 23 11:43:46 MSK 2018]: Could not create avd test_emulator_1, error = rx.exceptions.CompositeException: 1 exceptions occurred.
> Exception in thread "main" rx.exceptions.CompositeException: 1 exceptions occurred.
>         at rx.internal.operators.OperatorMerge$MergeSubscriber.reportError(OperatorMerge.java:268)
>         at rx.internal.operators.OperatorMerge$MergeSubscriber.checkTerminate(OperatorMerge.java:818)
>         at rx.internal.operators.OperatorMerge$MergeSubscriber.emitLoop(OperatorMerge.java:579)
>         at rx.internal.operators.OperatorMerge$MergeSubscriber.emit(OperatorMerge.java:568)
>         at rx.internal.operators.OperatorMerge$InnerSubscriber.onError(OperatorMerge.java:855)
>         at rx.internal.operators.OnSubscribeRefCount$2.onError(OnSubscribeRefCount.java:116)
>         at rx.internal.operators.OperatorPublish$PublishSubscriber.checkTerminated(OperatorPublish.java:443)
>         at rx.internal.operators.OperatorPublish$PublishSubscriber.dispatch(OperatorPublish.java:505)
>         at rx.internal.operators.OperatorPublish$PublishSubscriber.onError(OperatorPublish.java:294)
>         at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.checkTerminated(OperatorObserveOn.java:273)
>         at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.call(OperatorObserveOn.java:216)
>         at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
>         at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>         at java.util.concurrent.FutureTask.run(Unknown Source)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>         at java.lang.Thread.run(Unknown Source)
>   ComposedException 1 :
>         java.io.IOException: Cannot run program "C:\Users\my_user_name\AppData\Local\Android\Sdk/tools/bin/avdmanager": CreateProcess error=2, Не удается найти указанный файл
>                 at java.lang.ProcessBuilder.start(Unknown Source)
>                 at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt:73)
>                 at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt)
>                 at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:72)
>                 at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:32)
>                 at rx.Observable.unsafeSubscribe(Observable.java:10327)
>                 at rx.internal.operators.OperatorSubscribeOn$SubscribeOnSubscriber.call(OperatorSubscribeOn.java:100)
>                 at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
>                 at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
>                 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>                 at java.util.concurrent.FutureTask.run(Unknown Source)
>                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
>                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
>                 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>                 at java.lang.Thread.run(Unknown Source)
>         Caused by: java.io.IOException: CreateProcess error=2, Не удается найти указанный файл
>                 at java.lang.ProcessImpl.create(Native Method)
>                 at java.lang.ProcessImpl.<init>(Unknown Source)
>                 at java.lang.ProcessImpl.start(Unknown Source)
>                 at java.lang.ProcessBuilder.start(Unknown Source)
>                 at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt:73)
>                 at com.gojuno.commander.os.ProcessesKt$process$1.call(Processes.kt)
>                 at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:72)
>                 at rx.internal.operators.OnSubscribeCreate.call(OnSubscribeCreate.java:32)
>                 at rx.Observable.unsafeSubscribe(Observable.java:10327)
>                 at rx.internal.operators.OperatorSubscribeOn$SubscribeOnSubscriber.call(OperatorSubscribeOn.java:100)
>                 at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:230)
>                 at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
>                 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>                 at java.util.concurrent.FutureTask.run(Unknown Source)
>                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
>                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
>                 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>                 at java.lang.Thread.run(Unknown Source)

Ahhh, sorry, now its hardcoded unix separator and path.
I guess I'll try to find Windows machine to make it work finally.

@yunikkk we just need to update separator to File.separator
Or use more sophisticated FileSystem.getSeparator to support different file systems dynamically instead of depending on OS

@artem-zinnatullin yeah, but also fix at least https://github.com/gojuno/swarmer/blob/cbeb41e713af4d44ba702304659abbb398c94089/swarmer/src/main/kotlin/com/gojuno/swarmer/Emulators.kt#L105 lol


why is session from 0 to 9 in pre-trained stage?

hello, nice work. I have some questions about the code. why is session from 0 to 9 in pre-train stage? All we need is a pre-trained model which could classify 60 base classes. What's more, in the session_*.txt, should we write the label such as 60,61,62.etc rather than some big number?

Yes, we only pre-train the 60 base classes in our pre-training stage. We use the original session_*.txt file from the TOPIC . The big numbers are actually the img for the specific dataset. The dataloader file will help you translate each image to the corresponding img to class pair


pull request for e2e test at 11/09/2016 13:15:10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Automatically start after login and data directory

Any plans on adding preference options to allow user to set automatic start after login and data directory location?

@caphun no current plans on doing so, but pull requests are also welcome :)


BibleUp destroy method

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
A destroy method to remove all BibleUp links and popover from the DOM
Describe the solution you'd like
b.destroy()
Describe alternatives you've considered
A way to remove the popover is by calling the remove remove method.
bu-popup. remove()

Get all bu-link elements
Replace parent cite and a element withchild Nodes recursively -node.replaceWith(...node.childNodes)`
Lastly, remove popover.

fixed in branch v1.0.0 - ready to merge


Add aws_redis module

This actually needs to be decoupled in two: aws_elasticache and aws_memorydb. They need to be written as separate modules

Added coverage for elasticache


Support Amazon Mobile Analytics

Enable http://docs.aws.amazon.com/mobile/sdkforios/developerguide/analytics.html and http://docs.aws.amazon.com/mobile/sdkforandroid/developerguide/analytics.html to be doable through C#.

Once again, a whole month with no new code. Let me ask again, is this project taken seriously or will I have to listen to marketing lies until one day this SDK is officially pronounced dead?

Thank you for writing to us and providing feedback. We have no plans for deprecating the Xamarin SDK. Based on the current feedback we have slightly de-prioritized adding new services in the Xamarin SDK. We expect to actively resume the work in a few months time.

So, i suppose few months already passed. Do we have some progress here?

@alekseevpg let me tell you, this project has proven itself as completely useless and abandoned time and time again. Your best bet, I am afraid, is creating .NET wrappers yourself, which is, at least in the iOS case, unfortunately far from trivial.

@ddobrev sad but true. Did you already tried to wrap it?

@alekseevpg I have successfully wrapped the Android SDK - if you want, I can ask my employer if I may share the binding with you. However, with the iOS SDK I haven't even tried because the .a file is 72 MB large, this is way too large.

@ddobrev well, I don't have any needs in android sdk for now, but i think it would be great if you can share it with the world anyway :)

We have released 3 versions of the Xamarin SDK and about to release the 4th.  This project has not been abandoned as @ddobrev has noted incorrectly.  Version 3 released support for both iOS 32 and 64 bit versions and added enhancements and additions of AWS Services.
The Mobile Analytics piece was being worked on with the Unity SDK first and then the Xamarin SDK.  Unity SDK was finished on last week opening up the addition to the Xamarin SDK.
Version 4 of the Xamarin (1-3 are already released on GitHub) has been completed and discussions are being had about what best for customers on release of v4 or delaying for push of Mobile Analytics.
Sent from Windows Mail
From: Paul
Sent: Monday, March 23, 2015 5:05 AM
To: 'awslabs/aws-sdk-xamarin'
Cc: Tara Walker
So, i suppose few months already passed. Do we have some progress here?
—
Reply to this email directly or view it on GitHub.

@tawalke, any news on Mobile Analytics support? This is the only SDK part that we need in our app.

Hi Alexey:
This is being worked on and reviewed.  The version 4 will be released next week without it, but it is being currently addressed for release.   It will be uploaded to GitHub upon completion and review.
Sent from Windows Mail
From: Alexey Bogdanov
Sent: Saturday, April 18, 2015 5:04 AM
To: 'awslabs/aws-sdk-xamarin'
Cc: Tara Walker
@tawalke, any news on Mobile Analytics support? This is the only SDK part that we need in our app.
—
Reply to this email directly or view it on GitHub.

@tawalke Good to hear!
How lightweight would it be? Will it have dependencies on other parts of the SDK? I think using Mobile Analytics only will be a very common use case of the SDK. So it would be great if it'll have the smallest possible footprint. @ddobrev also noted that it's important (comparing to iOS SDK binding).

Hi Alexey:
Right now,  I have no details to share, given this is currently in development.
Sent from my Windows Phone

From: Alexey<EMAIL_ADDRESS>Sent: 4/19/2015 2:04 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: Re: [aws-sdk-xamarin] Support Amazon Mobile Analytics (#6)
@tawalke Good to hear!
How lightweight would it be? Will it have dependencies on other parts of the SDK? I think using Mobile Analytics only will be a very common use case of the SDK. So it would be great if it'll have the smallest possible footprint. @ddobrev also noted that it's important (comparing to iOS SDK binding).

Reply to this email directly or view it on GitHub:
https://github.com/awslabs/aws-sdk-xamarin/issues/6#issuecomment-94301829

Hi @tawalke,
Do you have any idea when the Amazon Mobile Analytics support might be available?

It is being developed, but I do not have a definitive ETA when the team will be complete.
Sent from my Windows Phone

From<EMAIL_ADDRESS>Sent: 6/17/2015 4:04 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: Re: [aws-sdk-xamarin] Support Amazon Mobile Analytics (#6)
Hi @tawalke,
Do you have any idea when the Amazon Mobile Analytics support might be available?

Reply to this email directly or view it on GitHub:
https://github.com/awslabs/aws-sdk-xamarin/issues/6#issuecomment-112930546

:+1: for implementing mobile analytics .. it would be really awesome to have this in aws xamarin sdk..

Hi:
This Beta SDK should now be migrated to use the AWS SDK for .NET with  Xamarin has been released.  As noted, this release is under AWS SDK for .NET and is in Developer Preview.  The Xamarin SDK repo has the latest links for this update, as well as, the updates for the updated NuGet packages.
This should resolve you issue as this has the updated services like Mobile Analytics and updated desired codebase.  See links below:
https://github.com/aws/aws-sdk-net
https://github.com/aws/aws-sdk-net#nuget-packages


apache module requires ansible_lib but the dependency is not listed

I installed the apache module using:
$ ansible-galaxy install vbotka.apache
and with no other modules installed on my ansible server, when I attempted to run this module, I received the error:
 TASK [vars: Include OS vars]
 ERROR! the role 'vbotka.ansible_lib' was not found in {list of library directories}
 The error appears to be in '/usr/home/deployment/.ansible/roles/vbotka.apache/tasks/vars.yml': line 10, column 15, but may
 be elsewhere in the file depending on the exact syntax problem.

 The offending line appears to be:

  include_role:
    name: vbotka.ansible_lib
          ^ here

Installing this module appears to correct this problem.  I suspect (though I have yet to test) that adding vbotka.ansible_lib as a dependency should fix this issue.

Both issues were fixed in 1.9.0. Let me know if it's working for you. Details are described in annotated source code.

Closed. But, feel free to reopen if needed.

Closed.


For all ‘invalid request parameter names and case-1 to xx” tests the response is correct ie 422 but the OperationOutcome states Patient not found/Invalid NHS number

It should be INVALID PAPAMETER
Ie

This has now been resolved.


fix(ndt_scan_matcher): fix compiler flags and Eigen aligned allocator to support general SIMD architecture

Related Issue(required)
TBD ;), It will be prepared soon.
Description(required)
To support general SIMD instruction set in ndt_scan_matcher, like Intel AVX-256, ARM NEON

Add Compiler Flags in localization/ndt related CMakeLists.txt
Using eigen's aligned allocator to std::vector of Eigen::Matrix

Review Procedure(required)
Please compile it and check the AVX-2 instruction, like vmodapd in the binary.
Note; if the alignment is failed, the constructors fails to segfault.
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read commit-guidelines
[ ] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

Thank you @kenji-miyake for your help to check the title!
I'm reading now the contribution guidelines...

This commit depends on the vendor side update.
The update is now being reviewed in https://github.com/tier4/ndt_omp/pull/8

https://github.com/tier4/ndt_omp/pull/8 is merged. Re-run all jobs...


.verify has a confusing api

It apparently expects a multihash and a buffer to be compared.
I find this a bit confusing.
Instead shouldn't it simply be a comparison function?

@mkg20001 it should match js-multihashing-async, which now is being redesigned as part of the https://github.com/ipfs/js-ipfs/issues/1670


add: spinnaker clouddriver podAnnotations

Signed-off-by: Masato Kureha<EMAIL_ADDRESS>
What this PR does / why we need it:
Add podAnnotations for clouddriver.yml
ref: https://www.spinnaker.io/reference/halyard/custom/#podannotations
Example: kube2iam for ECR auth-N. (values.yml)
clouddriver:
  podAnnotations:
    iam.amazonaws.com/role: my-ecr-readonly-role-arn

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

  additionalProfileConfigMaps:
    create: true
    data:
      clouddriver-local.yml: |-
        kubernetes:
          podAnnotations:
            iam.amazonaws.com/role: "${aws_iam_role.spinnaker_clouddriver.arn}"

This was not working, so I need this PR patch.
ping @lwander @dwardu89

/lgtm

/test pull-charts-e2e

/ok-to-test

/test pull-charts-e2e

Hey! I am only seeing this pr now, I somehow missed it before, I had added a very similar PR for the same thing here: https://github.com/helm/charts/pull/12719
One of these PRs should be closed, I don't mind which one but if we are going to merge this one then it should also include the changes I made to add pod annotations to the front50 pod. This is required if you are wanting to write spinnaker config to an s3 bucket instead of minio.
Also, I noticed both my PR and this one are failing on pull-charts-e2e but haven't been able to figure out why yet.

@MarkFreebairn You got it. I close this PR for #12719


Remove EOL OpenJDK versions

Part of https://github.com/NixOS/nixpkgs/issues/313216
Issue description
Should we remove End-of-Life (EOL) OpenJDK versions?
This proposal suggests removing OpenJDK versions that have reached their end-of-life status after a specific timeframe. For example, we could remove versions that have been EOL for more than six months.
This approach would simplify JDK maintenance within nixpkgs. Users who require an EOL version, such as Java 16, could still access it through the Temurin JDK.
For an overview of JDK release dates see:

https://en.wikipedia.org/wiki/Java_version_history#Release_table
https://www.java.com/releases/

Should we remove End-of-Life (EOL) OpenJDK versions?

I'm in favor (as a first step we should probably mark them 'insecure' to give people still relying on them a heads-up?)

This approach would simplify JDK maintenance within nixpkgs. Users who require an EOL version, such as Java 16, could still access it through the Temurin JDK

Temurin Java 16 seems also unsupported, though (https://adoptium.net/support/), so we should probably eventually drop those as well? Ideally we should have no software in nixpkgs that relies on unsupported versions, and out-of-tree projects that still use such software could use something like https://codeberg.org/raboof/nix-jabba

Also in favor!


Rename serial blocks

We were discussing this at standup. The API is not obvious and every time someone tries to write a string or a number they drag out writeString or writeNumber and are confused when it doesn't "work". In my opinion, we shouldn't have low-level APIs that need explaining like that in the blocks.
@microsoftsam @abchatra @Jaqster

Then the proper fix is to move out serial into a package. This category is pretty much useless without those.

Can we keep the low api in typescript & remove from blocks?
Also light.graph writing to serial doesn't make sense to me. It is not obvious that it writes to serial. There is no documentation which says so. And if user writes explicit serial.write then light.graph interferes with it.

You can do with writeLine everything you can do with writeString and writeNumber, so the category isn't any less useful.

It just works: in micro:bit when you do a plotbargraph, it automatically displays the data stream. You don't have to read the docs to get it working.
If you remove this feature from light.graph, users will have to discover that feature by accident in the advanced -> serial category.

If we are about cleaning up, we should not call this category 'serial' because it is not (it is data piping over HF2). It is not compatible with serial consoles like Putty or TerraTerm.
I am proposing to remove serial all together and add the blocs needed to surface data logging.

@pelikhan so your suggested TODO items are:

Rename the "serial" category to "data logging"
Add other blocks for data logging (what would these blocks be?)

I'm not sure it should live under advanced -> data which is pretty much undiscoverable. Maybe it would work better if we were able to "graph" a variable and have that block sit under variable.
We should design the overall data-logging experience and have a block that supports it. Having a new block deep down in the advanced section won't help.

@pelikhan That's fine with me, but it sounds like a change that is separate from this PR.  Can we merge this now, and figure out where data logging blocks should live later?

This PR is introducing a new block "plot value".

Happy to sit F2F monday and discuss about this. This fix feels like bandaid. We are removing existing blocks without updating the docs, renaming a block which now does not match the typescript version (we do that in other places, but we should try to avod it) and we have a category that is still not named properly.
If we need to fix serial, we should pull out all the blocks.

It's not a new block, it's a new label on an old block.  Changing the label to "plot value" instead of "write value" makes sense now that we have plotting.

All blocks in that category are consistent with the write terminology and provide access to IO over serial (which is not really serial). If we need a new kid friendly block to plot, it should not go under the serial category.

There is no obvious connection with serial and the new data logging support. If we really want kids to discover and use that feature, we need better support for it in the API/block editor. Renaming the serial block does not solve that issue IMO.

The intent of this PR isn't to solve that issue - just to take a step in that direction by removing/renaming obsolete/confusing blocks.  We can do more cleanup and reorganization later - that shouldn't block this PR though.

Lets wait till Peli is back for this PR. We have time to merge next week.

I do agree with Caitlin on this.

We are shipping a v1 so if we think serial is confusing, we should remove it all together. We can/should not take it back afterwards.

Thanks Caitlin

Ok, will add it in. It should be very consoling.

Ha!  Good one Galen!

RE: #178.
Maybe change to a stream abstraction in the future to allow 'console' output to go to a sim window, LEDs, etc.

Yup, that’s the idea.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Galen Nickel<EMAIL_ADDRESS>Sent: Saturday, November 11, 2017 4:48:29 PM
To: Microsoft/pxt-common-packages
Cc: Peli de Halleux; Mention
Subject: Re: [Microsoft/pxt-common-packages] Rename serial blocks (#145)
RE: #178https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt-common-packages%2Fpull%2F178&data=02|01|jhalleux%40microsoft.com|ee2e5a4068c449c18ac808d52967182c|72f988bf86f141af91ab2d7cd011db47|1|0|636460445122892295&sdata=BTt2DVOGkj33dC5qbdkc7U2Ed%2FVC3YMR23Q%2BddLbhis%3D&reserved=0.
Maybe change to a stream abstraction in the future to allow 'console' output to go to a sim window, LEDs, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt-common-packages%2Fpull%2F145%23issuecomment-343705491&data=02|01|jhalleux%40microsoft.com|ee2e5a4068c449c18ac808d52967182c|72f988bf86f141af91ab2d7cd011db47|1|0|636460445122892295&sdata=Wy9lYghrATy0BFLsM%2Bt81s%2FdCagaFSPBVIMh3kmo3Ms%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KZKKQsX8co2jiFdCVILnkkkyQFT4ks5s1kBdgaJpZM4QGnYI&data=02|01|jhalleux%40microsoft.com|ee2e5a4068c449c18ac808d52967182c|72f988bf86f141af91ab2d7cd011db47|1|0|636460445122892295&sdata=N221VVfYG4IOUqjGJ3HqVTDGXzPn9da1xaPljiSJoJ8%3D&reserved=0.

@ganicke  do you need a tracking bug for serial->console blocks update?

Yea, it will help my metrics...just kidding.


Remove Cairo prerendering dependencies

Should clear up these two issues.
https://github.com/danoneata/chalk/issues/69
https://github.com/danoneata/chalk/issues/68
In theory now you can run the SVG backend without any non-python dependencies. Think that fits a lot of notebook like use cases.

Thanks! Looks good!
Just a couple of minor points that are not strictly related to this PR:

Regarding the logo's aspect ratio, what about using the with_envelope to do the cropping? Something along these lines:

diff --git a/examples/logo.py b/examples/logo.py
index c350660..b6698d1 100644
--- a/examples/logo.py
+++ b/examples/logo.py
@@ -43,12 +43,12 @@ def sunflower(n):
 floret = sunflower(1900).center_xy().scale_uniform_to_x(1).center_xy()
 background = rectangle(1.5, 1).fill_color(black).line_width(0).translate(-0.25, 0)
 logo = text("Chalk", 0.35).fill_color(grey).line_width(0.008).line_color(black).translate(-0.15, -0.1)
-mask = rectangle(1.5, 1).fill_color(white).line_color(white).line_width(0.05).translate(0, 0.6)
+mask = rectangle(1.5, 0.6)

 # assemble
-d = (background + floret + logo).center_xy() + mask
+d = (background + floret + logo).center_xy().align_t().with_envelope(mask.align_t())

I don't know, why but I get different outputs for the examples than those newly added; in particular, I see that

the added tournament-network.svg doesn't have the digits better centered in the circle nodes
the added logo.svg seems to have the text cut.

I've noticed that the mypy tests have failed; I guess we need to type: ignore those lines!?

Good eyes.

Fixed logo
Fix for tournament
Forced MyPy newer version.


Issue with "Seek To" with multiple progress bars

We use ng-repeat to display multiple audio progress bars on a single page. The problem is, within the "ionAudioProgressBar" directive, you have a template definition where on-release is assigned to the scoped sliderRelease() function:
            template:
                '
{{track.title}} - {{track.artist}}
' +
                '
' +
                '<ion-audio-progress track="track"></ion-audio-progress>' +
                '<input type="range" name="volume" min="0" max="{{track.duration}}" ng-model="track.progress" on-release="sliderRelease()" disabled>' +
                '<ion-audio-duration track="track"></ion-audio-duration>' +
                '
',

and the sliderRelease() function:
                scope.sliderRelease = function() {
                    var pos = scope.track.progress;
                    MediaManager.seekTo(pos);
                };

If we release on ANY of the progress bars in our list, it resets the audio for the track that is currently playing whether or not the progress bar that got the release event is associated with the currently playing track or not. Our temp fix is this:
                scope.sliderRelease = function() {
                    var pos = scope.track.progress;
                    if(pos > 0) {
                        MediaManager.seekTo(pos);
                    }
                };

Which would prevent a user from sliding the position all the way back to zero, however it sure beats reseting the track anytime a slider progress bar is touched while scrolling up and down for example. Is there a better way to determine in the directive if it is associated with the currently playing track? Didn't want to necessarily submit a PR with our little if() hack above. Thanks!

I am not sure I understand your use case. Why do you need multiple progress bars? Each progress bar should be nested within a ion-audio-track directive, is that your case?
Maybe you can share your view template.

We have multiple progress bars because we are displaying multiple playable tracks within the same page (a common use case I assume).
Our view template looks as follows:
   <ion-list>
      <ion-item class="trackRepeat" ng-repeat="talk in talks track by talk._id">
          <ion-audio-track track="talk">

                    <ion-audio-controls>
                      <ion-spinner icon="ios"></ion-spinner>

                      <ion-audio-progress-bar display-time></ion-audio-progress-bar>
                    </ion-audio-controls>

          </ion-audio-track>
   </ion-list>

It renders a list of multiple tracks we can play on one page. Thanks!

Hi @ccravens
Yes, that's perfect, with one minor remark: can you try removing the "by talk._id" from the ng-repeat and see if that fixes the problem?

@ccravens any update on this?

With Ionic2 there's no seekTo() function. How do we seek with the new version?

Any news from original poster?

Trying once again :P any update @ccravens ?


dyld: Library not loaded: @rpath/lib_InternalSwiftSyntaxParser.dylib

To run from Xcode, add build settings to link lib_InternalSwiftSyntaxParser.dylib explicitly.
See

SwiftSyntax depends on the lib_InternalSwiftSyntaxParser.dylib/.so library which provides a C interface to the underlying Swift C++ parser. When you do swift build SwiftSyntax links and uses the library included in the Swift toolchain. If you are building an application make sure to embed _InternalSwiftSyntaxParser as part of your application's libraries.

You can either copy lib_InternalSwiftSyntaxParser.dylib/.so directly from the toolchain or even build it yourself from the Swift repository, as long as you are matching the same tags or branches in both the SwiftSyntax and Swift repositories. To build it for the host os (macOS/linux) use the following steps:

https://github.com/apple/swift-syntax#embedding-swiftsyntax-in-an-application
So, the easy way is launching the app from command line swift run

@kishikawakatsumi  thanks

So, the easy way is launching the app from command line swift run
@kishikawakatsumi I know this way
but  i want to debug swift-ast-explorer project

This is a Swift PM managed project. No xcodeproj by default. You can generate xcodeproj by swift package generate-xcodeproj


'NoneType' object is not iterable。SD1.5 512X512

In sd1.5, 512X512 768X768 512X640 doesn't work either

On the contrary, LayerDiffuse uses uses the SDXL algorithm model, and the SD base model is 1.5, which is actually possible, but some effects are not ideal

My problem is exactly the same as yours. I used Ubuntu20.02 and my graphics card was rtx4090. I can also use the sdxl model, but using the 1.5 model will report the same error as you.

我的是4070ti super 遇到同样的问题，大模型选什么都可以，但是 LayerDiffuse 必须使用 SDXL的，使用SD1.5的会报'NoneType' object is not iterable的错误

have you guys solved this issue? could anyone share the solution please? appreciate it very much.


[WIP] Rework test suite

/packit copr-build

Hello @Honny1! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests_oval_graph/test_arf_xml_parser/test_arf_xml_parser.py:

Line 13:1: E303 too many blank lines (3)

I will remove symlinks in #207.

Hi, it's amazing, but next time please create small PRs to make it easier to review ;)


MAISTRA-2548 Reject SMCP if default gateway targets a non-member namespace

Not problematic because the reconcile already fails in this case, as it checks whether the charts try to create any resource outside the mesh.

Not problematic because the reconcile already fails in this case, as it checks whether the charts try to create any resource outside the mesh.

Nevermind I was misreading the intention here- I thought this would limit to control plane namespace, not non-memer namespace