Create is not indexing the models relationships

Software
Version

PHP
8.1

Elasticsearch
7.9.3

Laravel
9.11

Laravel Scout
9.4

Describe the bug
When I create a new record of a model, it's not filling the relationship info.
My model is:

<?php

namespace App\Models;

use App\Http\Resources\ProductVariantResource;
use ElasticScoutDriverPlus\Searchable;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;

class Outfit extends Model
{
    use HasFactory, Searchable;

 ...

    public function occasions()
    {
        return $this->belongsToMany(ProductOptionValue::class)->whereHas('option', function ($query) {
            $query->where('slug', 'occasion');
        });
    }
...

    public function searchableAs()
    {
        return 'outfits';
    }

    public function toSearchableArray()
    {
        return [
            'id' => $this->id,
            'type' => $this->type,
            'build_type' => $this->build_type,
            'status' => $this->status,
            'title' => $this->title,
            'gender' => $this->gender,
            'channel' => $this->channel,
            'note' => $this->note,
            'occasions' => $this->occasions->map(function ($occasion) {
                return [
                    'id' => $occasion->id,
                    'title' => $occasion->title,
                ];
            })->toArray(),
            'styles' => $this->styles,
            'seasons' => $this->seasons,
            'ages' => $this->ages,
            'body_types' => $this->body_types,
            'price' => $this->price,
            'featured' => (bool) $this->featured,
            'is_in_stock' => (bool) $this->is_in_stock,
            'order' => $this->order,
            'created_by_outfit_builder' => (bool) $this->created_by_outfit_builder,
            'is_template' => (bool) $this->is_template,
            'user_id' => $this->user_id,
            'user_name' => $this->user ? trim($this->user->first_name.' '.$this->user->last_name) : null,
            'date' => $this->created_at->timestamp,
            'products' => ProductVariantResource::collection($this->variants),

        ];
    }
}

The creation is done like this
$outfit = Outfit::create($data['outfit']);
        $outfit->user_id = auth()->user()->id;
        $outfit->save();

        // Sync and create new collections
        $collectionsIds = [];

        foreach ($data['outfit']['collections'] as $collection) {
            if (is_numeric($collection['value'])) {
                $collectionsIds[] = $collection['value'];
            } else {
                $collection = Collection::create([
                    'name' => $collection['value'],
                    'user_id' => auth()->id(),
                ]);
                $collectionsIds[] = $collection->id;
            }
        }

        $outfit->collections()->sync($collectionsIds);

        // Sync product_values
        $productValuesIds = [];

        foreach ($request['outfitOptions'] as $options) {
            foreach ($options as $value) {
                $productValuesIds[] = $value;
            }
        }
        $outfit->values()->sync($productValuesIds);
        $outfit->variants()->sync(collect($request['selected'])->pluck('id')->toArray());

And the result ES index is
{
  "took" : 0,
  "timed_out" : false,
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 1,
      "relation" : "eq"
    },
    "max_score" : 1.0,
    "hits" : [
      {
        "_index" : "outfits",
        "_type" : "_doc",
        "_id" : "1",
        "_score" : 1.0,
        "_source" : {
          "id" : 1,
          "type" : "clothing",
          "build_type" : null,
          "status" : 1,
          "title" : "teste",
          "gender" : "male",
          "channel" : "all",
          "note" : null,
          "occasions" : [ ],
          "styles" : [ ],
          "seasons" : [ ],
          "ages" : [ ],
          "body_types" : [ ],
          "price" : null,
          "featured" : false,
          "is_in_stock" : false,
          "order" : null,
          "created_by_outfit_builder" : true,
          "is_template" : false,
          "user_id" : 201,
          "user_name" : null,
          "date" :<PHONE_NUMBER>,
          "products" : [ ]
        }
      }
    ]
  }
}

As you can see, it only saves the model data, not its relationships.

Current behavior
Model is indexed only with its attributes
Expected behavior
Model should be indexed with its relationships too

Ok, if I add an $outfit-update([]) just after creating and syncing the model, all the relationships will index, except for products.
Is there some special with this line?
'products' => ProductVariantResource::collection($this->variants),
It does index perfectly if I run the scout CLI command.

Ok, if I add an $outfit->update([]) just after creating and syncing the model (or $outfit->touch()), all the relationships will index.


Added support for " remote_config_encoding",fixes #162

Description
Added support for the configuration item remote_config_encoding. When the configuration item is "plain", it will not be processed. When the configuration item is "base64", it will attempt to base64 decoding of the subscription address.
Linked Issues
fixes #162
Additional context
This is my first PR.I tested my code ,but I don't know the workflow.  If I am at fault, please correct me  :)

Thank you for this contribution! I will need some time to review your changes. In the meantime, please adjust according to the checks in the CI. :heart:

Thanks again for the effort 🤩

❤


Remove image options from ibm-spectrum-scale-csi-operator-cr.yaml file

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
We should remove below options from "https://github.com/IBM/ibm-spectrum-scale-csi/blob/master/operator/deploy/crds/ibm-spectrum-scale-csi-operator-cr.yaml" as we have mechanism using env variable to set these images for testing/dev now. This will help us restricting user to not try untested attacher,provisioner,driver-registrar,scale driver images. Scale driver images are hard-coded and matched with operator code.
# Attacher image name, in case we do not want to use default image.
# ==================================================================================
#  attacher: "quay.io/k8scsi/csi-attacher:v1.0.0"

# Provisioner image name, in case we do not want to use default image.
# ==================================================================================
#  provisioner: "quay.io/k8scsi/csi-provisioner:v1.0.0"

# Driver Registrar image name, in case we do not want to use default image.
# ==================================================================================
#  driverRegistrar: "quay.io/k8scsi/csi-node-driver-registrar:v1.0.1'"

# SpectrumScale CSI Plugin image name, in case we do not want to use default image.
# ==================================================================================
#  spectrumScale: "quay.io/ibm-spectrum-scale/ibm-spectrum-scale-csi-driver:v1.0.0"

Expected behavior
Remove image options from ibm-spectrum-scale-csi-operator-cr.yaml file

We do need a way to override images for customers who do not have internet access from clusters. If env vars is the way to set these then that is fine too, but we'll need some user documentation on how to use it.

Hi Smita, I agree to override images alteast for testing env which is already there in the dev yaml ( I hope) but for customers who do not have internet access from production clusters, cann't they download the required images offline and  load them to local openshift repository because today evan OCP 4.3 installation happens that way.

I don't think I want to remove the interface from the CR, because I personally think we should leave that option open, because the Environment can easily be overridden. We provide the environment so we can have a different delivery stream for test and RC. Generally speaking I view the use case for the Custom  Resource Settings as being a mechanism for the  user to lock their config in place via CR.

Hi Team, I hope we are not targeting this for 1.1.0 so removing the 1.1.0 milestone.

We decided to keep image option as is. Closing this as no action required.


Verification of Kubernetes Service Connection fails due to wrong API URL

When adding a new service connection for kubernetes, the verification fails as Azure DevOps misses a slash "/" before the api-path.
Error:
Failed to query service connection API: 'https://HOST/k8s/clusters/c-qz6w5api/v1/nodes'. Status Code: 'NotFound', Response from server: '{"Code":{"Code":"NotFound","Status":404},"Message":"clusters.management.cattle.io "HOSTapi" not found","Cause":null,"FieldName":""} '
It uses "https://HOST/k8s/clusters/c-qz6w5api/v1/nodes" but it should be "https://HOST/k8s/clusters/c-qz6w5/api/v1/nodes".

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 72b90dd0-49f9-4ed4-3010-9a64dde6ae5a
Version Independent ID: 6e679d50-4e94-eee3-8793-af884cc909ca
Content: Service connections in Azure Pipelines and Team Foundation Server - Azure Pipelines
Content Source: docs/pipelines/library/service-endpoints.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

we have fixed it in the latest code.

we have fixed it in the latest code.
@bansalaseem Can you be more specific which is the latest code? We have the issue on Azure DevOps Server 2019.1.1.


GRC tables need to expand full width

Signed-off-by: Chunxi Luo<EMAIL_ADDRESS>Signed-off-by: Chunxi Luo<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/25597
isWidthLimited is introduced in https://github.com/stolostron/console/pull/1112

/cc @KevinFCormier @RobDolares @showeimer


looks like the search component is not matching what is in Podman Desktop

Is your enhancement related to a problem? Please describe
there is a blue outline, the magnifying glass is with a gray background and the search field is with a darker background

Describe the solution you'd like
this is what I have for containers:

Describe alternatives you've considered
No response
Additional context
No response

Duplicate of #292, the color variables are not working and haven't been able to figure it out yet.

I believe it's two separate issues as Input component is coming from the 3rd party library

Search is just a variant of Input, and in both cases it was the variables not taking effect - anyway, your fix is solving both when I test.


[sync materialized view]refresh not failed after modify table column type

Steps to reproduce the behavior (Required)
CREATE TABLE `t2` (
                                            `k1` date,
                                            `k2` int,
                                            `k3` int
                                        ) ENGINE=OLAP
                                        DUPLICATE KEY(`k1`)
                                        COMMENT "OLAP"
                                        PARTITION BY RANGE (k1) (
                                        START ("2020-10-01") END ("2022-03-04") EVERY (INTERVAL 15 day)
                                        )
                                        DISTRIBUTED BY HASH(`k1`) BUCKETS 3;
CREATE MATERIALIZED VIEW mv2
                                     PARTITION BY k1
                                     DISTRIBUTED BY HASH(k1) BUCKETS 10
                                     REFRESH ASYNC
                                     AS SELECT k1, k2
                                     FROM t2;
ALTER TABLE t2 MODIFY COLUMN k2 VARCHAR(20);
INSERT INTO t2 VALUES ("2020-10-10",'test_str',1);
SELECT * FROM INFORMATION_SCHEMA.task_runs order by create_time desc limit 1;

Expected behavior (Required)
task failed
Real behavior (Required)
task succeed
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

+----------------------------+
| current_version()          |
+----------------------------+
| BRANCH-2.4-RELEASE f823e8b |
+----------------------------+

please assign this issue to me.


Paste to terminal (Alt + R) - Does not work with Linux

Hi,
I'm using Rbox, alltogether with integrated terminal (https://github.com/platformio/platformio-atom-ide-terminal).
When I use Alt+R, trying to paste code to the Atom terminal, but it does not work.
What should I do to get this function properly work?
Cheers.

Hi, Could you please try "Shift+Alt+R".
Thanks.

On my Linux machine, Alt+R does send code to the Termination terminal, but only if a new terminal was manually opened first, and then if R was started in this terminal (the command is just R).


content-negotiation: move decorator to flask-resources

From base.py to flask-resources/context.py.

Done


support for deep object hierarchies

Hi,
here is a feature request: It would be nice if one could write:
url.query({user: {name: "Kimba", email<EMAIL_ADDRESS>
instead of manually creating the nesting. Thanks for URI.js!

I would really love this to be implemented, as it is really hard to work with nested parameters now. You have to juggle two libs for both parsing and building urls.

+1 I need to be able to parse: ?utf8=✓&d=&lesson_filters[time]=0,20&lesson_filters[neighborhoods][]=City Center&lesson_filters[neighborhoods][]=West Side&lesson_filters[neighborhoods][]=&lesson_filters[activities][]=&lesson_filters[studios][]=
From a rails form, grouped checkboxes.

:+1: @rodneyrehm, what was the reasoning behind not using JSON.stringify -- cross-browser compatibility? perhaps a custom build (compatible and modern) would be handy?
const uri = URI("/path/to/api");
const expected = {
  query: {
    $or: {
      $regex: ["hello", "world"]
    }
  }
};
uri.addQuery(expected); // [Object object]

what about a custom handler?
const uri = URI("/path/to/api");
const expected = {
  query: {
    $or: {
      $regex: ["hello", "world"]
    }
  }
};

// defers until toString is called
uri.addQuery(options, JSON.stringify);

// should also allow for strings
// uri.addQuery(JSON.stringify(options));

const request = URI(uri);
const actual = request.query(JSON.parse); // would call decodeURIComponent() first
assert.deepEquals(actual , expected); // true

i can help out, just need to understand the decisions

what was the reasoning behind not using JSON.stringify -- cross-browser compatibility?

I'm not sure I understand what you want achieve with JSON.stringify here?

@rodneyrehm: just providing a custom serializer, we have deeply nested objects but from the previous comments some users are expected ?user[name]=john&user[age]=20 where we are expected query='{"user":{"name":"john","age":20}}'

I see. if you need to cater to JSON, you're likely better off overwriting URI.parseQuery and URI.buildQuery accordingly.

I think this is a very important improvement, because nested parameters/arrays are used quite often. I came across this problem recently. I thought it was a bug before, but later I noticed that this feature isn't supported as of now.

+1 need it

Mottie's tablesorter plugin has a "sort-to-hash" feature, which stores the current state of a sorted/filtered table in the URL hash.  It requires custom decodeHash and encodeHash methods to translate the state between a JSON object (which contains a deep hierarchy) and a URL fragment.
It would be cool if URI.js could be used to automatically do this.


patience to support early stopping

Please support patience to stop early without waiting for max no of epochs.
Since there are multiple validation losses for various subsets but based on first element of the list checkpoint is saved, similarly based on it, can patience be implemented in the repo?
Else instead of returning if no-save-checkpoint as soon as it enters save_checkpoint in checkpoint_utils  calculate is the new valid_losses[0] is best or not and increment a counter and early stop once it exceeds the counter as in https://github.com/RayeRen/multilingual-kd-pytorch/blob/master/train.py#L126

https://github.com/pytorch/fairseq/pull/904

Added in 1512a0e6213c9a84c5bb1eb918147bd6e96092cd


how do we add a calendar or daterange picker?

I am trying to add a appointment booking form, needed a daterange picker in the form.

Haven't heard anything here for a while. Close the issue now.


Ignore ConnectionAssetDetails after the first one in a Connection.

The Stream RFC is being clarified to indicate that only a single pair of ConnectionAssetDetails should be used per Connection. Thus, we should ensure that the StreamSender ignores subsequent frames of this type if they are sent more than once.
If the sendMoney is called with an overt Denomination, then all such frames should be ignored, with a WARN to indicate if there's a divergence.

We never actually look at this frame beyond the preflightCheck in the sender.


Revert "chore(jetbrans-gateway): update JetBrains IDEs"

Reverts coder/modules#96
Breaks dev.coder.com like
Error: Error in function call
on .terraform/modules/jetbrains_gateway/main.tf line 129, in resource "coder_app" "gateway":
  129:   display_name = data.coder_parameter.jetbrains_ide.option[index(data.coder_parameter.jetbrains_ide.option.*.value, data.coder_parameter.jetbrains_ide.value)].name
    ├────────────────
    │ data.coder_parameter.jetbrains_ide.option is list of object with 2 elements
    │ data.coder_parameter.jetbrains_ide.value is "[\"GO\",\"232.9921.53\",\"https://download.jetbrains.com/go/goland-2023.2.2.tar.gz\"]"
Call to function "index" failed: item not found.

@spikecurtis I am investigating why this breaks down the template as the changes are totally unrelated to the error we get.
This is again a strong point in favor of that we should have versioning

I think what might have happened is that the registry was updated with new options, but the dogfood template still refers to the old versions in it's set of options.

@spikecurtis If you see the change, we only use WS and GO on dogfood, but I removed PY and IC. So, it should not be related, apparently.


Degraded performance and upload failure when projects reach >200 versions

Observed/problematic behavior
I have a project on Hangar (https://hangar.papermc.io/William278/HuskHomes) with two channels; Alpha and Release.
I publish to the alpha channel continuously; every time a commit is made to my project, a version is published to Hangar via the API to this channel. This enables users to download bleeding edge versions if they so desire; only main releases are published to the release channel (in accordance with TOS)
I've now published about 200 versions to Hangar, and have noticed degraded performance as I continue to publish more; specifically:

Viewing the "versions" page on the site, I occasionally receive "request timed out after 4000ms" errors
I can no longer upload additional versions; I receive a 500 Internal Server Error through the API. I suspect this is because the underlying logic to fetch the list of versions is timing out

Expected behavior
Hangar gracefully handles me having more than 200 versions on a project, lets me continue to upload new versions, and smoothly browse existing ones
Steps to reproduce
Have a project with over 200 versions, and attempt to upload another version, either through the API or the frontend.
You can also experience the timeout issue by going to https://hangar.papermc.io/William278/HuskHomes/versions and observing the errors in the bottom-right
Other
No response

Opening the versions page doesn't seem to be slow (although it's not a paginator so lol). Just to clarify, when uploading via the website, did this happen when clicking 'create' in the final step, or before that?

Sorry for the slow reply!
This occured both when hitting "Create" in the final page and when doing an upload via the API.

This should be resolved with https://github.com/HangarMC/Hangar/commit/98733f665108e8783bd74b48b53f69ac5bb5973a


Run apt_update when defining debian repos

As per the puppetlabs/apt documentation, there should be a notify => Exec['apt_update'] when defining repos using apt::sources, otherwise there is no guarantee that the packages in the new repo will be available the next time Apt tries to install a package.

Sounds reasonable.  Could you add unit test coverage of the resource relations somewhere like spec/classes/jenkins_repo_debian_spec.rb?

@jhoblitt cheers. I've added another commit with a check for the notifies attribute on the jenkins apt::source resource.


Add an endOfLine option to the console transport

It would sometimes be useful to be able to customise the EOL character used by the Console transport.  My use case is where I want to log a task as started, then add a check once it's completed.  Setting endOfLine to '' would allow this:
log.info('Running task... ');
doTask();
log.info('done\n');

An alternative would be to allow setting the end-of-line character per log (e.g. log.info('Running task...', {eol: ''})), but I don't see a sane way of doing that while allowing string interpolation.

Let's rename this eol to be consistent with the file transport

Cherry-picked into 2.x. Thanks!


feature: support for default config name/path for the CLI

When using the mirrord CLI it would be nice if it would check for an existing config file to use instead of having to specify it everytime you run it.
On execution is could look for mirrord.json, mirrord.yaml, and mirrord.toml in the current directory and use the first file available.
Having a mirrord config file in a project repository is convenient when launching a development environment. Having to not specify the config file would be even more convenient.
This feature will not revolutionize mirrord, but it would make it a little bit nicer :)

Thanks for the suggestion! I believe to avoid breakage it'd be best to have it as a flag, wdyt?

My personal opinion is that it should pick up the config file without any extra arguments. This it what the majority of cli tools do.
I am not sure I would categorize this feature as breaking.

I would like to contribute to this issue. This is something I thought that the CLI should have instead of having to mention the mirrord.json path every time. Can it be assigned to me ?

Thanks @waveywaves  - happy to accept contribution. Please note that it should be a new flag and not a default behavior.

Sounds okay to me


Would you be willing to take ownership of google-apis-rs?

Hello,
There is this excellent project that has just been deprecated:
https://github.com/Byron/google-apis-rs/
The background is given in these discussions:

https://rust-lang.zulipchat.com/#narrow/stream/318791-t-crates-io/topic/Can.20I.20reclaim.203.20Google.20CLI.20crates.2Cpublished.20by.20someone.20else.3F
https://rust-lang.zulipchat.com/#narrow/stream/318791-t-crates-io/topic/On.20Google.20APIs.20and.20Sebastian.20Thiel's.20crates

The Rust ecosystem is risking to be left without a comprehensive way to interact with Google APIs. There are other initiatives but they are not this rigorous in terms of the coverage. This page gives a nice overview of what google-apis-rs is capable of:
https://byron.github.io/google-apis-rs/
Would you be willing to adopt the repository and maintain it moving forward, with the community's effort of course?
Thank you!
/cc @danoscarmike, @codyoss

TL;DR; no, I do not think we can help here.
First, apologies for the late response. We only recently restarted the project to create a Google Cloud SDK for Rust.
We did look at Byron/google-apis-rs.  We decided to on in a different direction.  This is not a reflection on the quality or features available in said project. We just have different priorities and other considerations. For example, we need tooling that is consistent across more languages than Rust.
I do not want to be ambiguous or unclear: we are aiming to support all the Google Cloud APIs. That leaves some APIs (like Ads) that would not be included in this project. For Google Cloud, we hope to make the APIs so good that people would want to move to the crates published out of google-cloud-rust.
For APIs beyond Cloud: the tooling we are creating should be able to support those APIs too, and we would support any community efforts to support those additional APIs. We cannot commit to supporting said APIs ourselves.  And please give us some time to get Cloud working before we explore Ads or Geo or something else.


duperemove: fix hash & build

Description of changes
Newest tag (v0.14) got modified, thus also changing the src hash. It also introduced a regression requiring -Wno-error=format-security to be passed to CFLAGS for it to build.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 268837 run on x86_64-linux 1

1 package built:

duperemove


Display debugging information in case of failure

Until now, when the networking_mapper plugin failed, we didn't really
know anything about the data it was using.
This change uses the "bloc/rescue" capabilities in ansible to display
all of the passed parameters to the plugin in case of failure, making
debugging easier for everyone.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
/lgtm


Load XML elements with addresses

Pivotal story: 91602732
Load data from XML uploads into a SQLite database for the following elements:

election_administration
polling_location
early_vote_site
candidate
street_segment

Looks :top: to me.


[incubator/haproxy-ingress] Added features

What this PR does / why we need it:
Updates haproxy-ingress to v0.7-beta.7.

New features:

pod affinity
PodSecurityPolicy
init containers

Fixes a few things:

missing securityContext in DaemonSet
priorityClassName: added quote
fixed pod annotations in DaemonSet
use livenessProbe instead of readinessProbe for side-car container

Pod affinity allows adding anti-affinity so that only one haproxy-ingress controller may run per node, which is useful when setting externalTrafficPolicy: Local.
The PodSecurityPolicy and init containers allow modifying some sysctls, like fs.file-max and fs.nr_open, in a privileged init container. This is useful if the number of file descriptors is not high enough for the configured number of connections in haproxy (maxconn).
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

/ok-to-test

/lgtm


flutter/lib/src/: refactoring if-chains into switch expressions

Based on issue #144903, this pull request aims to bring the codebase more in line with the Flutter repo style guide:

Avoid using if chains or ?: or == with enum values

// before
bool get shown {
  if (overlayEntry == null) {
    return false;
  }
  if (animationController != null) {
    return animationController!.status == AnimationStatus.completed ||
        animationController!.status == AnimationStatus.forward;
  }
  return true;
}

// after
bool get shown {
  return overlayEntry != null && switch (animationController?.status) {
    AnimationStatus.forward || AnimationStatus.completed || null => true,
    AnimationStatus.reverse || AnimationStatus.dismissed => false,
  };
}

This pull request is similar to a previous PR with the same name but has a bit more thorough refactoring overall.

@nate-thegrate Are you interested in getting contributor access by the way? I'd be happy to sponsor you.

@justinmc That would be awesome, thank you very much!


Disable MinimalCoreWin when OpenConsoleUniversalApp is false

This fixes the build the rest of the way in VS 16.7. Something about the
way we were using the Store/Container flags caused some of our projects
to end up linking kernel32.lib only (MinimalCoreWin==KernelOnly).
The best way to solve it once and for all is to make sure MinimalCoreWin
is always set.
References 313568d0e5c.

@msftbot merge this in 1 minute


[webcamvideostream.py] updated to allow another start() after a stop()

When calling .stop() the stream should be released.
In the original code the stream was not released. This makes it impossible to .start() the stream again after a .stop()

The changes in this PR is a duplicate of what is already in #177

The changes in this PR is a duplicate of what is already in #177


Replace obsolete @PostConstruct annotation or implement InitializingBean

The problem
Some autoconfiguration classes uses obsolete javax.annotation.PostConstruct annotation (e.g. GrpcMetadataConsulConfiguration).
Spring boot 3 still supports it, but doesn't include corresponding dependency. And because of this, configuration classes won't load. So I need to include javax.annotation:javax.annotation-api:1.3.2 dependency explicitly in my project to make this work. This is tedious and human factor prone.
The solution
Two solutions available:

Remove annotation entirely and implement org.springframework.beans.factory.InitializingBean interface.
Replace javax.annotation.PostConstruct with jakarta.annotation.PostConstruct. Spring boot includes jakarta.annotation dependency since release 2.2 and drops javax.annotation since 3.0.

Additional context
This ticket relates to #778.
I could make PR. But one of proposed solutions should be chosen first. I personally prefer option 1. IMHO it's more reliable since annotations have been already broken once and I never heard that spring broke InitializingBean in some way.

Oh, I see it's already done in 98f29e4e.


Fix MNT: Add noarch: python

This should fix the noarch PR https://github.com/conda-forge/csbdeep-feedstock/pulls
Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.
requirements: host: python >= 3.6 should not contain a space between relational operator and the version, i.e. python >=3.6
requirements: run: python >= 3.6 should not contain a space between relational operator and the version, i.e. python >=3.6

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: host: python >= 3.6 should not contain a space between relational operator and the version, i.e. python >=3.6
requirements: run: python >= 3.6 should not contain a space between relational operator and the version, i.e. python >=3.6

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

OK, so the noarch is trickier than I thought vs. pip any.
So maybe this isn't the way to go, because it requires no selectors at all, not even for versions.
So the existing csbdeep requirement of h5py <3 for python <3.9 is a deal-breaker.
The TF issue that made this requirement is closed, because it's been fixed in TF 2.4.x, and TF TF 2.1 isn't supported. So setting TF >2.4 here is a solution.
But this of course precludes support for old TF envs, but I'm not sure the [tf1] option was possible using the conda install?

Sorry @psobolewskiPhD, I don't know what's going on here. What am I supposed to do?

Ok, thanks for the explanation! I'll close these PRs for now, we can re-open/visit them if need-be.


Revert "arch: Replace ar and nm with gcc-ar and gcc-nm"

Summary
This reverts commit b05737d78fb0e746f46a19f2cdd9d4dc59e54985.
Because it broke clang-based builds.
Impact
Testing

Summary
This reverts commit b05737d.
Because it broke clang-based builds.

@yamt could you point out which config break? https://github.com/apache/incubator-nuttx/pull/4451/checks show that the change pass CI on macOS.

Summary
This reverts commit b05737d.
Because it broke clang-based builds.

@yamt could you point out which config break? https://github.com/apache/incubator-nuttx/pull/4451/checks show that the change pass CI on macOS.

clang build of sim/linux at least.
i don't think we are testing it on the ci.

i suppose LTO build will be an optional config.
i guess it makes more sense to make these conditional on, say, CONFIG_GCC_LTO.
how do you think?

i suppose LTO build will be an optional config.
i guess it makes more sense to make these conditional on, say, CONFIG_GCC_LTO.

Could be, b05737d doesn't really enable lto, but make enable lto more easier.

how do you think?

For sim clang support, the better fix is SIM_TOOLCHAIN_CLANG/SIM_TOOLCHAIN_GCC and arch/sim/Toolchain.defs.

i suppose LTO build will be an optional config.
i guess it makes more sense to make these conditional on, say, CONFIG_GCC_LTO.

Could be, but b05737d doesn't really enable lto, but make enable lto more easier.

how do you think?

For sim clang support, the better fix is SIM_TOOLCHAIN_CLANG/SIM_TOOLCHAIN_GCC and arch/sim/Toolchain.defs.

i'm not sure it's better or not. but i agree it's consistent with the other boards.
are you going to fix this that way?

i suppose LTO build will be an optional config.
i guess it makes more sense to make these conditional on, say, CONFIG_GCC_LTO.

Could be, but b05737d doesn't really enable lto, but make enable lto more easier.

how do you think?

For sim clang support, the better fix is SIM_TOOLCHAIN_CLANG/SIM_TOOLCHAIN_GCC and arch/sim/Toolchain.defs.

i'm not sure it's better or not. but i agree it's consistent with the other boards.
are you going to fix this that way?

or are you asking me to do it? either way is ok for me.

We can add an issue. The change isn't huge if you don't have free time, I can do it in this week.

after thinking a bit, i guess the problem is not only for sim.
for example, it shouldn't be used in case of CONFIG_ARMV7M_TOOLCHAIN=CLANG, right?
i prefer this to be reverted for now unless we can fix it quickly.
(i don't think i can fix and test non-sim bits so quickly)

Fix https://github.com/apache/incubator-nuttx/pull/4482

@yamt, since https://github.com/apache/incubator-nuttx/pull/4451 is related to https://github.com/apache/incubator-nuttx/pull/3836. I would propose revert them in batch. Also, it's better to make a demo how to enable lto without gcc driver.

@yamt, since #4451 is related to #3836. I would propose to revert them in batch. Also, it's better to make a demo how to enable lto without gcc driver.

lto thing has been on my low-priority todo for a while. if anyone can beat me, it's welcome.
otoh, this one is more critical as it's breaking my (private) ci and workflows right now.
if you are going to merge https://github.com/apache/incubator-nuttx/pull/3836 without waiting for "lto demo", it's fine for me. (IMO it isn't reasonable to require me the demo in the first place.)
otherwise, let's fix this independently from https://github.com/apache/incubator-nuttx/pull/3836 .

Ok, let's merge this PR first.


Optionally rotate images to minimize bounding box

Codecov Report

Merging #7 into master will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
+ Coverage   88.91%   88.94%   +0.03%
==========================================
  Files          76       76
  Lines        2445     2452       +7
==========================================
+ Hits         2174     2181       +7
  Misses        271      271

Flag
Coverage Δ

#unittests
88.94% <100.00%> (+0.03%)
:arrow_up:

Impacted Files
Coverage Δ

xfuse/convert/st.py
59.52% <ø> (-2.70%)
:arrow_down:

xfuse/convert/visium.py
82.60% <ø> (-2.01%)
:arrow_down:

xfuse/__main__.py
88.38% <100.00%> (+0.15%)
:arrow_up:

xfuse/convert/utility.py
89.18% <100.00%> (+1.88%)
:arrow_up:

Continue to review full report at Codecov.

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


verification pipeline

check if grid starts at 0 or 1
import ML file with appropriate time structure

add cory as comparison as well
create visual output (gif for full season)

retrieve date based on ml output data


Improve test stability issues caused by resources failing to start due to "address in use" errors

Found in the dotnet/aspire-samples tests (e.g. this CI failure).
Sometimes when running app host integration tests using DistributedApplicationTestingBuilder, resources can fail to start due to the port that was randomly assigned by DCP already being in use by the time the resource goes to start:

This results in a test that fails, but that will most likely pass on re-run. We should look at how we can improve this so that tests are more reliable, e.g. doing automatic retries when resources fail to start.

Is there something to be done about the "address in use" problem in general? I've had to resort to creating a script that first executes kill on various processes before starting Aspire in order to make restarts more palettable. This could presumably also be solved by making hot reloading more functional; not requiring a full restart when you change/add a new environment variable for example.

Is there something to be done about the "address in use" problem in general?

The challenge is always that it's inherently racy if you want to know what the port is before you assign it to the process. Also it's not clear when it does fail if it's due to some other random process using the port or a previous instance of something launched by Aspire that wasn't shut down properly, or even random collisions in situations like parallel startup. I think adding some kind of support for startup retries could help here. I might attempt to see if I can add some startup-failure detection and retry logic to the testing infrastructure in dotnet/aspire-samples at the app host level, e.g. when a resource state changes to FailedToStart, scrape its logs and look for "port/address already in use" messages and in those cases, issue a "Start" command.

Aspire being bad at ending its child processes

This was improved in between 9.0.0-rc.1 and 9.0.0, so I'd love to hear if you're seeing any improvement after updating to the latest version.

This could presumably also be solved by making hot reloading more functional; not requiring a full restart when you change/add a new environment variable for example.

For sure, this is something we're thinking of improving but likely more in the mid-to-long term rather than short term.

This issue is not just a "test stability issue" Aspire 9 seems to have lots of problems stopping projects. In Aspire 8, I routinely started and stopped solutions without issue. In Aspire 9 on OSX with Podman Desktop and the Rider Aspire plugin, about half the time there are stuck ports preventing Aspire from starting.

@karolz-ms @danegsta FYI
@yoDon can you try seeing what it's like without using the Rider plug-in, i.e. starting/stopping from the cmd line using dotnet run? Trying to see if we can narrow down the scope.

@DamianEdwards
Yes, I am able to reproduce the issue using AppHost dotnet run on OSX + Podman Desktop (no Rider involvement)
I'm also mentioning a non-test-related issue that I reported around this, incase it's helpful to connect the two: https://github.com/dotnet/aspire/issues/6704


Performance improvement: do not query database when not needed for a dual database/redis setup

I propose this PR as a transparent version of the feature request #1257 I opened.
In case the feature request is not approved (for example for bringing complexity to lucia interfaces), this PR solves my performance issues on a dual database/redis setup while not impacting existing code.
The only side effect I see is that the validateSession() or getSession() would no longer potentially throw a AUTH_INVALID_USER_ID exception when no getUserAttributes function is defined in a dual user/session adapters setup. But not having a user when a session exists should never happen anyway.

Hm, I'll admit session adapters aren't prioritized but I don't think this is the direction I want to go. IMO, this should be an adapter level implementation, not Lucia's. I know building custom adapters isn't really straightforward right now, but it should be fairly easy with the recent v3 proposal.
class CustomAdapter extends RedisSessionAdapter implements Adapter {
  private db: Database;

  constructor(db: Database, client: RedisClient) {
    super(client);
    this.db = db;
  }

  public getSessionAndUser(): Promise<
    [session: DatabaseSession, user: DatabaseUser]
  > {
    const session = await this.getSession();
    if (!session) return [null, null];
    return [session, { id: session.user_id }]
  }
}

I still do not see what is the point of querying the database if there is nothing to query, my PR was only a performance optimization.
But ok, I'll wait for v3.


Randomized Benchmarking tutorial fails with the latest release

Informations

Qiskit Experiments version: 0.2.0
Python version: 3.9.7
Operating system: Window

What is the current behavior?
In randomized benchmarking tutorial, running code line [14] shows [TypeError: 'method' object is not iterable]()
Steps to reproduce the problem
from  https://qiskit.org/documentation/experiments/tutorials/randomized_benchmarking.html
run [14]
What is the expected behavior?
Running through the tutorial without error in the latest release.
Version info should be provided in the tutorial.
Suggested solutions
add () after child_data
for i, sub_data in enumerate(par_expdata.child_data()):

This issue was resolved.  The section that shows figures from the sub experiment data is now:
# Print sub-experiment data
    for i in qubits:
        print(f"Component experiment {i}")
        display(par_expdata.child_data(i).figure(0))
        for result in par_expdata.child_data(i).analysis_results():
            print(result)

closing the issue.


Attaching data to resource

Hey thanks for this library!
One question is the simplest way to assign data directly to the resource body. Right now you call .Data() but it seems to force us to map each property of a struct manually to that instance of the map ?
I wondered how you got around this limitation without requiring a node on the body for assignment; eg
type MyStruct struct {
Name string
}

// instead of
body := res.Data()
body["name"] = myStructInstance.Name

// or
body["data"] = myStructInstance

Any insights?

Hey Mike!
You are right, it is a limitation. Since I use a map at least one node e.g. 'data' is required.
This leads to (maybe, not wanted) JSON like:
"data": {
          "name": "Patrick"
}

I agree, it's a bit cumbersome to force a manual property mapping. Especially when you prepared your DTOs.
Instead of calling bytes, error := encoder.ToJSON(root)
a workaround might be eg
properties := hal.PropertyMap{}

links := halResource.Links()
embedded := halResource.EmbeddedResources()

properties[links.Name] = links.Content
properties[embedded.Name] = embedded.Content

//this requires to add a node named 'data' with your DTO assigned.
data := halResource.Data()["data"]
//use Indirect() when assigned value is a ptr
val := reflect.Indirect(reflect.ValueOf(data))

for i := 0; i < val.NumField(); i++ {
	//look out, no camel casing when field identifiers are exported!
	properties[val.Type().Field(i).Name] = val.Field(i).Interface()
}

bytes, err := json.Marshal(properties)

Best regards
Patrick

an even more convenient option solving the camelcase issue:
func toJSON(halResource hal.Resource, dataKey string) ([]byte, error) {
	links := halResource.Links()
	embedded := halResource.EmbeddedResources()

	properties := hal.PropertyMap{}
	properties[links.Name] = links.Content
	properties[embedded.Name] = embedded.Content

	data := halResource.Data()[dataKey]

	if data == nil {
		return json.Marshal(properties)
	}

	val := reflect.Indirect(reflect.ValueOf(data))

	for i := 0; i < val.NumField(); i++ {
		fieldName, ok := val.Type().Field(i).Tag.Lookup("json")

		if !ok || fieldName == "-" {
			continue
		}

		properties[fieldName] = val.Field(i).Interface()
	}

	return json.Marshal(properties)
}

But this works on a resource's top level, only. Embedded resources still require a manual property mapping. I plan providing a more convenient solution with the next go2hal release. Maybe, this month.

issue closed with v0.3.0 release

Excellent approach. I apologize for just now returning to this...we've been heads down on a release.
I'm going to bump us up to v0.3.0! By the way this is being used at InVisionApp :)

:)


[i2c, dv] Add stress_all test

This PR includes

Use pre_start and post_start to configure vseq
Add i2c_stress_all_vseq
Remove redundant csr_spinwait in *_vseq
Move cfg variables from i2c_env_seq into i2c_seq_cfg

Signed-off-by: Tung Hoang<EMAIL_ADDRESS>

@weicaiyang @rswarbrick I have updated the PR to address you comments


Remove Compass dependency

Hi!
I created distribution Ink Framework, in which there is no relationship with Compass library. I decided to implement the missing functions related with the generation of the declaration @font-face.
By removing the dependence we can easily take advantage of the framework on Windows or in environments where there is limited possibility of using Ruby.
I used the library libsass, which is becoming popular due to its portability and excellent performance.

+1

The prospect of losing the compass dependency and make the install instructions a lot simpler looks very, very good. I'll have to look at it more in depth though, as this touches a lot of stuff.
@pedrocorreia and @gnpfonseca, chip in!

@fabiosantoscode: Well, I know it's hard to make that changes in entire framework.
My changes are not so big - only two functions and some @imports. It's a proof of concept.
By the time the mixins will be available until that time Ink Framework will continue to be compatible with Compass, without having to install in the system strange things;) Mixins are good ;)
My work is not that good, what can be, but was relatively simple to replace the Compass :)
Basicly you can use compass-mixins repository in exchange for bower-compass-core.
(https://github.com/Igosuki/compass-mixins)

Very cool! I tried to do a fork awhile back to use node-sass but the syntax support wasn't then very up to date with the latest SASS version. This has changed since node-sass 3.0 onward.
Not only this would make the framework technology stack much smaller but also would make it so it's much easier to install and modify.

The whole idea of using compass in the first place was to "offload" the work of writing the necessary tools onto a well maintained and seemingly trustworthy third party. So, to me, it seems reverting to creating and maintaining our own mixins/functions is rather counterproductive. What you seem to be proposing is to replace a dependency on a tool with another one and i can't see any advantage in that.
There are several solutions for compiling compass on pretty much all platforms:

http://mhs.github.io/scout-app/
http://koala-app.com/

Im sure there are more. So with that said, i'll have to say that this does not seem to be the way to go.
Thanks for your contribution anyway!

@pedrocorreia this removes the dependency on Ruby altogether, allows us to pin the sass version using package.json, which makes it easier to install a canonical Ink to produce canonical builds.
This fixes problems like me having to bug you to compile the CSS when we release Ink because on my machine it looks very different.

@pedrocorreia this removes the dependency on Ruby altogether, allows us to pin the sass version using package.json, which makes it easier to install a canonical Ink to produce canonical builds.
This fixes problems like me having to bug you to compile the CSS when we release Ink because on my machine it looks very different.

As said before we would be replacing a dependency on compass, and subsequently ruby, by 3 others:

libsass
a chosen wrapper that uses libsass to do the actual compiling, i.e. node-sass
https://github.com/Igosuki/compass-mixins

There was a reason why we chose to use compass as our work horse. It's a stable, it has been developed and maintained for 7 years and also was written by a member of the SASS core team.
So, replacing a reliable tool for a less reliable one, does not seem a wise choice.

I'm sorry, but when I last checked, Ink Framework using bower-compass-core library for some reason. I don't know why, but it has dependency on this library. If you intend to use pure compass why you need to import such thing?
This library provides mixins same as compass-mixins. Only difference is comapss-mixins provides also some compass functions. It's good start to make Ink Framework more independent and more easy to implement.

I'm not the right person to respond to your question about bower-compass-core, but,
As @pedrocorreia said, it might not be too wise to swap this dependency right now, since compass is so mature and reliable. You detected a @font-face dependency, but there are some more, such as transforms and box-shadows, which in your PR just expand to a compress() function call with lots of arguments. I don't know a lot about compass or sass, but I would make the ubeducated guess that is just because this is not using the actual compass.
As much as I'd love, for simplicity's sake, to remove ruby from this project's dependencies altogether, it might not be a good idea right now.

The bower-compass-core is a subset of compass stylesheets, created and maintained by me so i really don't think of it as a third-party dependency. Since compass has quite a few files this was a simple way of reducing the number of stuff we need to the bare minimum.
It seems that we're discussing the tools rather than the the resulting product here. Ink is a CSS, HTML and JavaScript framework/library and these are the things that we should be worried about.
When we chose our tools, and we have done this based on previous experience, our CSS was originally created with LESS, we chose the ones that best fitted our criteria and needs, so without any disrespect to your opinion @tomick, in the almost year and an half since we moved to SASS/Compass, you're the only one to have an issue with this, and that is hardly sufficient to convince me that it needs to be changed.
Best regards.


Unaligned memory issues

Hello,
I installed MINIZ to encode image with spng, on MacOS 10.14.6 (Intel Core i7).
I got two 'Unaligned Memory Access' errors, but I was able to fix them:
Line 1116--1119
    mz_uint match_len = pLZ_codes[0];
    //mz_uint match_dist = *(const mz_uint16 *)(pLZ_codes + 1);
    mz_uint match_dist = 256 * (mz_uint)pLZ_codes[2] + (mz_uint)pLZ_codes[1];

Line 1163:
    //*(mz_uint64 *)pOutput_buf = bit_buffer;
    memcpy(pOutput_buf, &bit_buffer, 8);

And with these modifications it works!
I get lots of warnings relating to 'comma' use, but that is another story.
You are using them correctly, but a ';' would do the same job, and not trigger so many warnings...
Thank you very much for the excellent work!
Greetings from Cambridge, UK

Can you please create a pull request with your fixes?


Builder in the Nether issue

I have a clearing quarry card going in the nether, and for some reason, it is mining dirt... I'm really confused as to why this is since dirt doesn't spawn in the nether.  I am in Minecraft 1.10.2, playing in the Modpack AllTheMods.  I also have a builder running a normal quarry in the overworld, but it voids dirt.

I am the only person on the world, it's working now.  I don't really know how to explain what just happened.  It's working normally now so i guess the problem is fixed? lol

BTW, I love your work.  RFTools is amazing.  Never had a problem before now and it seems to have fixed itself!

Self-fixing mod :-)

If a modpack doesn't include RFTools I won't play it! Simple as that :P


fix(documentation) Removed a few misprints

I removed a few misprints and I also propose a few modifications for a few sentences.
I have no tests, as this is documentation.
Proposed changelog entries

Entry 1: fix(documentation) Remove a few misprints
[…]

Submitter checklist

[X] The Jira / Github issue, if it exists, is well-described.
[X] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).

Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.

[X] There is automated testing or an explanation for why this change has no tests.
New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
For dependency updates, there are links to external changelogs and, if possible, full differentials.
For new APIs and extension points, there is a link to at least one consumer.
Any localizations are transfered to *.properties files.

Maintainer checklist
Before the changes are marked as ready-for-merge:

[ ] There is at least one (1) approval for the pull request and no outstanding requests for change.
[ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
[ ] Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
[ ] Proper changelog labels are set so the changelog can be generated automatically.
[ ] If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
[ ] java code changes are tested by automated test.

thx for corrections


Assertion condition conflicts with know type

TypeScript Version:  3.9.0--dev.20200319
Search Terms: assertion condition, narrow assertion condition, assertion condition union
Code
type MyUnion = { [key: string]: any } | string[];

function assertObject(value: any): asserts value is Record<string, any> {
    if (value === null || typeof value !== "object" || Array.isArray(value)) {
        throw new Error("Assertion failed");
    }
}

function getValue(): MyUnion {
    return { foo: "bar" };
}

const value = getValue();

assertObject(value);

// Error as it does not know if it is a string[] or { [key: string]: any }
console.log(value["propName"]);

I've also observed that TypeScript is using the already known type at caller (i.e. MyType) to narrow after the assert function is called. This is resulting in never as a result.
I am not sure this part is behaving as expected, but seems to be related to the bug reported.
type MyType =
	| {
			[key: string]: {
				[k: string]: number;
			};
	  }
	| string;

const a: MyType = { foo: { bar: 123 } };

function assertUndefined(value: any): asserts value is undefined {
	if (value !== undefined) throw new Error();
}

assertUndefined(a.foo);

// `a.foo` is `never`
console.log(a.foo);

Expected behavior: assert condition should narrow the type to one of the values in the union.
Actual behavior: it seems to be merging what is knows about the type at the caller with what the assertion returns.
Playground Link: https://www.typescriptlang.org/v2/en/play?ts=next#code/C4TwDgpgBAsiCqA7Alge0VAvFA3lA2gNYQgBcUAzsAE7KIDmAuuQIaIhQC+UAPpTXXr5GAbgBQYgGYBXRAGNgaDCwoUI1YAHkARgCsICgBQA3FgBtpEVuwCUrVeuAUopi9GTOASgdTUAJgA8VLQMADRQbCAAfLhiUPFQyJJQJuaWWJjYiNJmZrx8oJCoya7pAISZUABEqHoGwFX5UACC1NQsIAB0Hq3tIKluNjaxCaNQwAAW1KgA7lCIEHMAom2+hlXNDhpKUJIsyGYQflU24qOcYhdSsgo79BDAAGppEIZ2sAgo6CMJ1A-S1AweEkqFQ5Cq2hY1EanHEVzk6CoLheWCg9yeLze4jEKjUGh0+iMpQgpwkAHoyVAVtNqBFnMhgFA-KgIM5EKhGYR2XMkolGR4IvwQkJGFBfLgCMQyELBMwIuwuGIEYgKKhDp0zKh6ANLPgqmBpmAAHIsAC2ECqjFOUCAA
Related Issues: #37241

string[] is a subtype of Record<string, any>, so the narrowing condition does nothing.
You could write something like this to indicate that you're excluding arrays from the result:
function assertObject(value: any): asserts value is { push?: never; [key: string]: any }```

Thanks, Ryan. I was suspecting this could be the case, but I did the lazy thing and brought the issue here.
But how about the second case I've added? Does TypeScript strictly follow the assertion or it merges with the type information it has on the caller?


8.1 Support?

I'm using concrete for the first time and would love to use this extension but I'm on version 8.1 and the installation reports that this isn't supported. Any plans to update to be compatible with 8.1?
Thanks

Hello,
I have it installed on 8.0.1 and it's working just fine. Ryan made sure it worked on v8 several months ago.
What problem are you experiencing?

My mistake… when I went to Extend concrete5/Add Functionality I saw a different add on (vivid ecommerce) and it wasn’t compatible. I accidently unzipped my files to  packages/community_store/community_store-master so it wasn’t showing up.
I’ve corrected this and all seems to be working now. Thanks!
From: Nour Akalay<EMAIL_ADDRESS>Sent: Friday, February 24, 2017 9:47 AM
To: concrete5-community-store/community_store<EMAIL_ADDRESS>Cc: kbeindorf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [concrete5-community-store/community_store] 8.1 Support? (#191)
Hello,
I have it installed on 8.0.1 and it's working just fine. Ryan made sure it worked on v8 several months ago.
What problem are you experiencing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/concrete5-community-store/community_store/issues/191#issuecomment-282308872 , or mute the thread https://github.com/notifications/unsubscribe-auth/AKHFlegmsxsLhZAZCEqhyJqhdUlskJJoks5rfu1sgaJpZM4MLMo_ .


Exception POSTing to AudioVideoPlaybackBot

Describe the issue
I have deployed the AudioVideoPlaybackBot to an azure instance without any revisions to the code, aside from config. When I submit a POST request to the JoinCall route, the service returns an exception in the message body (see below).
Code Snippet
Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: clientCallbackError
Message: Unexpected exception happened on client when authenticating request.
Scenario Id: 46b2df76-cb9b-4919-b349-4efbba79b2ea
 ---> Microsoft.Graph.Communications.Core.Exceptions.ClientException: Code: clientCallbackError
Message: Unexpected exception happened on client when authenticating request.
 ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.Identity.Client, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae' or one of its dependencies. Reference assemblies should not be loaded for execution.  They can only be loaded in the Reflection-only loader context. (Exception from HRESULT: 0x80131058) ---> System.BadImageFormatException: Cannot load a reference assembly for execution.
   --- End of inner exception stack trace ---
   at Sample.Common.Authentication.AuthenticationProvider.AuthenticateOutboundRequestAsync(HttpRequestMessage request, String tenant)
   at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.<SendHttpRequestAsync>d__4`2.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.<SendHttpRequestAsync>d__4`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<ValidateAndWrapAsync>d__12`1.MoveNext()

Expected behavior
Bot should successfully join the call.
Graph SDK (please complete the following information):

Graph.Communications nugets are all V1.1.0-prerelease.581.  I'm not sure if this is the same as the Graph SDK.

Call ID
Join Url: https://teams.microsoft.com/l/meetup-join/19%3Ameeting_ZjYxMmUzNmQtMDMxMy00Mzc0LTlhMzMtMTZjY2E1MTM2ZTc1%40thread.v2/0?context={"Tid"%3A"e4f0d009-006e-474f-a3a9-f7b80ffd9534"%2C"Oid"%3A"240bda36-4529-41a3-8ca6-d507f629e56f"}
Logs
No logs collected.
Additional context

I also met the same problem.

Thanks for reaching out folks.  We seem to be having issues with the recent update to MSAL libraries.  Trying to work through it.  If you by any chance troubleshoot the issue please do let us know.

Thanks @ksikorsk, I'm not sure whether it's relevant but I see this delay-signing warning in the build output:
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9\Microsoft.WindowsAzure.targets(3039,5): warning : CloudServices49 : The assembly 'Microsoft.Identity.Client.dll' is delay-signed.

As a temporary measure, if you load this changelist the samples should work:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/commit/3eb960ae62bb6e94b9906572bdbe39fa9b444be2
Last 2 checkins are the culprits.

Hey folks... we resolved the exception.  Thanks for your patience:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/pull/98


HotChocolate.Language.SyntaxTree12.22.2

Type: Incomplete
Summary:
HotChocolate.Language.SyntaxTree12.22.2
Details:
Adding OTHER for Declared License
Resolution:
https://www.nuget.org/packages/HotChocolate.Language.SyntaxTree/12.22.2/License
Affected definitions:

HotChocolate.Language.SyntaxTree 12.22.2

@AE49 I'm assuming OTHER was a mistake since all of the other HotChocolate curations submitted were MIT. Okif I update this to MIT?

@capfei Yes, MIT - thanks.


Train on pretrained baseline models

Hi,
Is there a way to use the pretrained baseline models as base for the training, rather than just the pretrained backbones?
I want to train a model on a new dataset and don't want to retrain it with the provided four.

We will add a pertained parameter to solve this. Please wait. Or you can add it by yourself currently.

have you add a pertained parameter ? @lb1100

Have you tried to add it yourself @chenbolinstudent ?

Sorry about the late reply. Now added. In config.yaml, at the same level of RESUME, add a PRETRAINED: "path/to/pretain/model" will use a pretained model.


zip import vulnerability fixed

fixed the vulnerability by adding size and  number of entries maximum and by calculating the compression ratio

Rejected


gitsigns spacing and colour

ive noticed a couple of problems with gitsigns re: spacing and colour
Spacing

if you look at gitsigns on the left of my screen you'll see changes to 3 consecutive rows.
in scrollview on the right there is additional space between each sign, as well as the mark
looks like this is because the #lines is less than the height of the window, so the scrollview needs to stretch the placement of things to cover the entire height. this can be confirmed by just changing the height of the nvim window:

Colour
the colour for added lines is incorrect. it shows up as yellow but, as you can see from the left of the image above, gitsigns has it configured as green

The spacing issue is addressed as of PR #130. When scrollview_always_show is used and a sign for gitsigns would correspond to multiple rows of the scrollview column, all those rows will be used.
@sho-87, can you provide steps for reproducing the other issue? Something like:
$ git clone <REPO>
$ git checkout <COMMIT>
$ nvim
# plus a list of edits to the file to reproduce the issue

@dstein64
to reproduce, here is a fresh config that bootstraps lazy and grabs scrollview and gitsigns at specific commits:
init.lua:
local lazypath = vim.fn.stdpath 'data' .. '/lazy/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
  local lazyrepo = 'https://github.com/folke/lazy.nvim.git'
  vim.fn.system { 'git', 'clone', '--filter=blob:none', '--branch=stable', lazyrepo, lazypath }
end ---@diagnostic disable-next-line: undefined-field
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
  {
    "lewis6991/gitsigns.nvim",
    commit = "078041e",
    config = function(_, opt)
      require('gitsigns').setup {
        signcolumn = true,
    }
    end
  },
  {
    "dstein64/nvim-scrollview",
    commit = "1d80f72",
    config = function(_, opts)
      require("scrollview").setup(opts)
      require("scrollview.contrib.gitsigns").setup(opts)
    end,
    opts = {
      always_show = true,
      column=40,
    }
  },
})

git init in a directory, create a new file, and commit it. I just used some random text like:

jkh
jklsdfh
sdf
sdf
sdf
sdf
sdf
sdf
sdf
sdfdsf
asdasdasd
isdfsdf

nvim using the config above
add a new line to the end of the file and you'll see this, which is the correct colour for an addition:

go to the line above and change it, and this is where it goes wrong:

the marker is still there for the line addition, but the colour that used to be the correct blue has now turned into purple

The second issue is fixed in 5a7eb7e6c1b921761615b57a6140d73b1cc2b034. A gitsigns change hunk could be comprised of a change and an addition. The existing code was assuming it was only a change, with no addition.
@sho-87, thanks for reporting the issue and providing the detailed reproduction steps. If you're still encountering a problem, please let me know with a new Issue or a comment here.

awesome! thanks for your speed


Allow theming to define a line number threshold for breakability for source code blocks

I find myself defining the %unbreakable option for short code blocks a lot as it looks weird if only a few lines are kept on the original page. Even for longer source code blocks, it would be nice to define a threshold for the number of lines I think are acceptable to move over to the other page as I think the resulting white space of the code now moving to the new page is bearable.
In other words, I would like to be able to set e.g. the threshold to 10, meaning that if the page breaks are applied in a way that if up to only 10 lines appear on the first page, consider the block unbreakable and just move it over to the next page completely. That would give me essentially a maximum of ten lines of source code length of whitespace at the end of a page.
Another option would be to offer a setting for the number of lines until the overall block is considered breakable. A 10 for that would consider source blocks up to 10 lines unbreakable, everything beyond that breakable.

The breakable/unbreakable logic is already extraordinarily complicated, and I'm not looking to add more complexity to it. There's also no easy way to know how many lines were placed on a page to know whether it was too few. We just know that it did or didn't fit.
I do see two options that we could explore that would at least give you some control.
One idea is to be able to specify how much room must be left on the page (a fixed value) to start a code block on that page. That would allow you to avoid the problem of having the code block get split after 1 or 2 lines. The key could perhaps be named code-min-height-start. We would ignore this setting if the code block has only 1 line since a single line code block is never split (and thus has the opportunity to fit even if there isn't the requisite amount of room remaining on the page).
Another idea is to be able to specify a line threshold that makes a code block automatically breakable. If the code block has no more than this number of lines, it won't break. The key could perhaps be named code-breakable-min-lines.
The problem with the second option is that it does not address the case when the first line of a long code block is orphaned. That's why I think the first option gets you most of the way there.

We definitely don't have to make it more complex than necessary. I just found myself marking all rather short code blocks with %unbreakable to avoid the split into two even shorter parts and thought, it might be neat to be able to prevent that by default. I didn't even think about longer code blocks with potentially very few lines before the break before filing the issue and thinking about other scenarios.
The code-min-height-start would nicely solve both scenarios IIUC. If it's easier to implement, even better.

The code-min-height-start would nicely solve both scenarios IIUC. If it's easier to implement, even better.

Great! I'll see what I can do.

We definitely don't have to make it more complex than necessary.

Let's just say that Asciidoctor PDF finds a way to challenge me every day ;)

After doing some testing, it became clear that these two options are mutually exclusive and thus both necessary. Here are the names I arrived at:

code-breakable-min-lines
the minimum number of lines a code block must have in order to be breakable; default is 2
code-orphans-min-height
the amount of usable space that must be remaining on the page (below the caption) in order to start a code block; default is 0

I think these two options give you a very reasonable amount of control over how code blocks break. We might even be able to extend them to other blocks in the future, but let's see how this goes first.
It's important to not that there's nothing we can do about widows. Once a page is used, it's used.

I haven't decided what milestone to put this in. I'd prefer it to be 3.0.x, but I might be able to be convinced otherwise.

Thanks for the insight, Dan. Option names look fine to me. No particular vote on the version. The project I'd use this in first uses a binary built from source anyway. Happy to give this a spin pre-release.

We'll go with Asciidoctor PDF 3.0, which isn't long off. This PR will be a two-parter, so I'll reopen to let the next one close it.

Both parts are in!


Some of the tutorial codes are outdated and not working.

Here are some of the links
iOS theme to Material theme migration
maintining both themes in a single app

No, they are up to date


Backend - Creating Controller for Individual Logged Game

Create controller for entity as described in:
https://spring.io/guides/gs/accessing-data-mysql/
https://studygyaan.com/spring-boot/how-to-connect-mysql-database-in-spring-boot-project
and incorporate information discussed in the 9/14 meeting on what data is collected.

There are changes to be made, but this can be implemented later as we are working on something else currently.
The changes include adding time/date functionality to the Session controller.


Unable to cast object of type 'LINQPad.Uncapsulator.Uncapsulator' to type 'System.Runtime.CompilerServices.INotifyCompletion'

I use Uncapsulator for testing private members.
in one of my use cases I saw this error:
Unable to cast object of type 'LINQPad.Uncapsulator.Uncapsulator' to type 'System.Runtime.CompilerServices.INotifyCompletion'
run this code in Linqpad to see the error:
await new RssService().Uncapsulate().IngestSubEpisodes(new List { new Episode { Id = "1" } });
public class RssService
{
private static readonly SemaphoreLocker _locker = new SemaphoreLocker();
private readonly DatabaseSimulator _context = new DatabaseSimulator();
protected async Task IngestSubEpisodes(List<Episode> episodes)
{
	var options = new ParallelOptions { MaxDegreeOfParallelism = 1 };
	await Parallel.ForEachAsync(episodes, options, async (episode, token) =>
	{
		var subEpisodes = await _locker.LockAsync(async () =>
		{
			return await _context.SubEpisodes;
		});
	});
}

}
public class Episode { public string Id; }
public class SubEpisode { public string Id; public string EpisodeId; }
public class SemaphoreLocker
{
private readonly SemaphoreSlim _semaphore = new SemaphoreSlim(1, 1);
public async Task<T> LockAsync<T>(Func<Task<T>> worker)
{
	await _semaphore.WaitAsync();
	try
	{
		return await worker();
	}
	finally
	{
		_semaphore.Release();
	}
}

}
public class DatabaseSimulator
{
public Task<List> SubEpisodes
{
get
{
return Task.FromResult(new List { new SubEpisode { Id = "1" } });
}
}
}

I can't reproduce this... are you using the latest version?


Help please extension installation problem

Hi, just tried to install the extension but i cannot seem to enable it. chrome seems to block it. i am in developer mode - any advice would be brilliant. Thanks

When you add an extension pack locally that doesn't go through the
Chrome Store, you will see this message.
You can use the official Chrome Store package.
https://chrome.google.com/webstore/detail/uk-drive-practical-test-b/emnhllljokeicdcnjccdagoddjlimilh


Cas 13520 add documentation for new task, imbaseline

@bemonts, we've created casadocs task description for imbaseline. Could you review the content? Please feel free to merge if the description is fine.

See my comments under the review. Thanks a lot @SatokoTakahashi and @tnakazato !

@SatokoTakahashi and @tnakazato , after merging this to master, I noticed that it ends up under "analysis" tasks. Should the better place not be "Single Dish tasks", which I think includes all other single dish tasks?
See:  https://casadocs.readthedocs.io/en/latest/api/casatasks.html
What do you think?
I have been trying to move this, but don't manage, and suspect that the path to casatasks.single instead of casatasks.analysis needs to be changed in the XML (to which I have no access), but I am not sure. I am trying to find out with the team here, but if you have any feedback (either on whether this is preferred, and/or how to do this), please let me know. Thanks a lot!

@bemonts, I think analysis category is fine. That is because imbaseline is so generic that it can process images produced by interferometry imaging like tclean (in short, imbaseline is a variant of imfit).

@tnakazato: Ok, no problem, we will keep it under "analysis. Thanks again!!


Release v2.1.0

There will be a release of uvgRTP in the near. Most of the functionality and fixes for this release are already in the master. This issue is here to manage the process of release and make sure everything goes smoothly.
Code Changes

[ ] Make RCE_H26X_PREPEND_SC the default (I have to tell everyone to add this flag) and add a flag to disable it.
[ ] Remove crypto.hh and debug.hh from include folder. Possibly also clock.hh (users should propbably just use chrono). socket.hh is also unnecessary, but unsure what is the best way to remove it (maybe converting it to pointers in rtcp.hh).
[ ] Run doxygen for public API
[ ] Update other documentation to newest version of API and resolve issue #108

During Release

[ ] Update https://github.com/ultravideo/uvgRTP/blob/master/cmake/ProjectDetails.cmake
[ ] Make sure automated tests run without revealing major errors, including encryption
[ ] Select commit and create tag
[ ] Publish release
[ ] Add built uvgRTP with RELEASE_COMMIT option

I'm also thinking of removing Qt project files. Qt themselves have deprecated their build system in favor of CMake and uvgRTP isn't even a qt project.


COVID-19の予防と治療 Prevention, treatment, and sequelae treatment about COVID-19

Sorry to disturb everyone.
But I have to tell everyone in this way: There ARE ways to prevent and treat COVID-19.
I made a PPT to introduce in detail the methods of prevention and treatment of COVID-19, even including the treatment of sequelae of COVID-19.
I once converted this PPT into a video and uploaded it to YouTube, but YouTube said, "YouTube does not allow the dissemination of false medical information that contradicts the COVID-19 medical information issued by the WHO or the local health department", and then deleted the video.
I argued that information that contradicted the local health department or the WHO is not necessarily false. For example, Trump's brother also died of COVID-19, indicating that they are simply unable to give useful medical advice.
But YouTube are unwilling to adopt my opinion.
I think that the community of programmers is an open community. Programmers are smart people and have a more open mind. Maybe people here can judge my recommendation more rationally.
Please click this link for the PPT:
https://github.com/hanfuqishe/covid-19
Sorry again, and thanks.

Hello, @hanfuqishe . This issue does not seem to be an improvement proposal for the development of this website(https://stopcovid19.metro.tokyo.lg.jp/). I'm sorry, I would like to close this issue.


Add Navigation Rail Sidenav Component

Feature Description
This was just added to the official Material Design spec. Navigation rails provide ergonomic movement between primary destinations in apps. YouTube and Google Photos are a couple of examples that use this component.
Use Case
The rail is a side navigation component that displays three to seven app destinations and, optionally, a Floating Action Button. Each destination is represented by an icon and a text label.
The rail can function on its own at larger screen sizes, such as desktop and tablet. When users transition between screen sizes and devices, the rail can also complement other navigation components, such as bottom navigation.
Preview

Hi, are there plans to implement this feature soon? Its much awaited!

This would be a really nice addition to the new MDC components.
It's a shame the specs do not have an option to place the text next to the icons instead of only underneath.

Does this automatically mean that 'extra' functionality will not be added to the Angular Navigation Rail?

can't wait to see this come through

Has this been implemented? I am eagerly awaiting to use this new rail mode for minimizing my nav bar, but still allowing the user to go right to the nav item they want, saving a click.

Has this gone somewhere?


Stub out Virtualized Grid Example

Hi @clauderic, I am trying to get this working with react-virtualized <Grid>. I  am running into an issue I'm hoping you can spot and address. In hopes of tempting you to help me out, I've stubbed out an illustrative example in the storybook demo page 😸  which I hope can be tweaked and added to the repo for future purposes.
Basically, everything works, except that drag-scrolling down long distances generates errors in the console. The error is easy to reproduce. Run the demo locally, click on the . "Virtualized Grid" example, and drag scroll down, hard and fast. The error happens here:
https://github.com/clauderic/react-sortable-hoc/blob/master/src/SortableContainer/index.js#L681
I would be extremely grateful for a fix to this. Thanks for an awesome library.

It looks to work for me. The only issue here is that the ordering seems to be unstable, if you drag and pause, the items shift. This does not happen if you keep the mouse 'wiggling'. Example below (gif):

https://codesandbox.io/s/dazzling-rhodes-q6jku, a simple demo


fix failing daily build

ah! thanks for reminding me to check the version :-)
looks good: https://github.com/Checkmk/grafana-checkmk-datasource/actions/runs/5935855868
current version is 3.1.0 and the attached files are 3.1.1-testbuild.smth

sweet :)


Minor clean-ups of class command

What do you mean with clean-ups? Looks like you're primarily removing dead code, right?

yes, exactly.

In general, a more precise commit message would make reviewing easier. I think a "clean-up" commit is ok, as long as a small summary follows the short description.


chore(ci): add controller debug logs when e2e was failed

Description
Modules

[x] Others

Checklist

[x] run code format and lint check
[ ] add unit test
[ ] add necessary doc

cc @xuchuan


ENH: odo support

Hello,
Maybe you should consider to support odo
http://odo.readthedocs.org/
Kind regards

Hi,
I've quickly looked at odo.
It seems awesome.
Some thoughts and questions:

pandaSDMX has native Support for Pandas. From there you can use odo.
One could think of odo Support for sdmx files and
pandasdmx.api.Response instances. Both can contain data and all kinds
of metadata. Metadata can be stored anywhere but not in Pandas. Files
can be stored in databases etc. Data can be exported vis Pandas to
other formats such as xslx.
Convert functions: Should odo Registration go into
pandasdmx.init.py so they are registered on each import?
What of the above would make sense?
Could you give some implementation help or even send a PR?

Leo
On 09/10/2015, femtotrader<EMAIL_ADDRESS>wrote:

Hello,
Maybe you should consider to support odo
http://odo.readthedocs.org/
Kind regards

Reply to this email directly or view it on GitHub:
https://github.com/dr-leo/pandaSDMX/issues/18

Hi @dr-leo ,
You might have a look at https://github.com/blaze/odo/issues/317
Kind regards

Thanks, PhemtoTrader.
Some more thoughts:

I now think any odo-related functions should go into api.py. This
seems to require importing Pandas there as well.

Scope of odo Support:

a) To begin with, an 'sdmx_to_pandas' function should convert a
pandasdmx.api.Response instance to PD.DataFrame, i.e. a wrapper around
Response.write().
b) One could also consider some 'sdmxml_file_to_pandas' function that
converts an XML-file as received from an SDMX Server into a
PD.DataFrame. Maybe odo's URL's could be leveraged. Passing a file or
filepath to odo would be the low-hanging fruit. But maybe it is useful
to Support sdmxml-files stored in a database, too.

Things that will likely be out of scope:

a)	Append: SDMX datasets cannot be appended. At least I don’t know
how. Well, if one makes certain assumptions one could convert both to
PD-DataFrame and append those. But this seems not very interesting,
right?
b)	Discover / shape: An SDMX dataset has no meaningful shape. A
dataset consisting of time series may have various time-periods such
as annual, monthly, daily etc. It is meaningless to speak of a shape
here as the indices cannot be merged etc. Only once a PD.DataFrame has
been created from an SDMX Response it makes sense to calculate the
shape.

Finally, I have to say that I won’t have the time needed to dive
into odo deeply enough to do this, at least not in the next six months
or so. If I ever find the time to work on pandaSDMX beyond bug-fixing,
I think I should spend it on a reader for SDMXJSON so that OECD and
IMF SDMX Services are supported.

So it would be phantastic if you could contribute a few lines of code
on odo Support. I would happily do a v0.3.2 release for that and
acknowledge your contribution. I have added another small yet cool API
Extension, namely a getattr method for the api.Response class to
bypass the 'msg' Attribute. So one can now write: 'resp.dataflows'
instead of 'resp.msg.dataflows'.
Leo
On 11/10/2015, femtotrader<EMAIL_ADDRESS>wrote:

Hi @dr-leo ,
You might have a look at https://github.com/blaze/odo/issues/317
Kind regards

Reply to this email directly or view it on GitHub:
https://github.com/dr-leo/pandaSDMX/issues/18#issuecomment-147216691


LIIKUNTA-129 | Add recommended sport places on venue page

Description
Add section for showing other similar places.
Issues
Closes
LIIKUNTA-129:
Screenshots

Codecov Report

Merging #102 (b25f14b) into main (fe608c1) will decrease coverage by 0.79%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #102      +/-   ##
==========================================
- Coverage   69.50%   68.71%   -0.80%
==========================================
  Files         106      120      +14
  Lines        1666     1729      +63
  Branches      381      393      +12
==========================================
+ Hits         1158     1188      +30
- Misses        507      540      +33
  Partials        1        1

Impacted Files
Coverage Δ

src/common/components/card/Card.tsx
14.92% <0.00%> (-1.21%)
:arrow_down:

src/common/components/card/DefaultCard.tsx
0.00% <ø> (ø)

...ch/venuesByOntologyWords/VenuesByOntologyWords.tsx
5.88% <5.88%> (ø)

...ts/upcomingEventsSection/UpcomingEventsSection.tsx
70.58% <83.33%> (+1.83%)
:arrow_up:

src/pages/venues/[id]/index.tsx
71.96% <85.71%> (+0.39%)
:arrow_up:

src/common/components/section/Section.tsx
92.85% <92.85%> (+1.19%)
:arrow_up:

src/domain/shortcuts/shortcutsData.tsx
100.00% <0.00%> (ø)

src/common/icons/IconOutdoorGyms.tsx
100.00% <0.00%> (ø)

src/common/icons/IconOutdoorActivities.tsx
100.00% <0.00%> (ø)

... and 12 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 fe608c1...b25f14b. Read the comment docs.


selection sort visualizer

I have created a folder named Selection sort visualizer where I have created a javascript based website where user can clearly see how a selection sort works.

Dear @abhianand0110, as per the guidelines mentioned, this is not a valid PR


Merge to publish

@jasonjoh,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/add-mobile-support.md
:white_check_mark:Succeeded

docs/breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/rest/terms-of-use.md
:white_check_mark:Succeeded

docs/rest/toc.yml
:white_check_mark:Succeeded

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.


Week 1

Package
Name
Maijla Ikiz
Class
Tech-2
Repo link
Project Team Creator
Summary
Personally, I feel like I have not made much progress this week, even though I have done all the assignments and managed to set everything up. I came up with a new concept  (I had come up with something during the kick-off class at first), as documented in my wiki, but I am not yet confident or sure about it, meaning I have not spend a crazy amount of time thinking about details etc. This will probably change once I discuss my concept on monday with friends and the teacher.
I think I learned the most during back-end class, I am not a command line god yet, but I now feel less scared when having to use it. I was able to successfully install the needed packages and create a boilerplate for my matching application repo. I look forward to the template engine!
Resources used
During this first week the only resources I used were a markdown cheatsheet and a Node.js getting started guide during back-end class.
Any thoughts?
Even though I have some programming knowledge and experience, I did find it hard to get started with Node.js! Especially since I barely do anything with my terminal. The assignments on the back-end class repo only told us what to do, but not exactly how or where to look. Yea some links were provided, but those were mostly long guides (for example when we had to create a boilerplate for our application, I had no idea how to do the package.json part, only after some googling did I find that I had to run the npm init --yes command. I understand the importance of being able to read through these guides and follow along, but I would have preferred it if the important steps or chapters of these guides were highlighted or mentioned in the repo or something like that... I feel like it would have taken less time for me to get everything setup. Other than that I am having a lot of fun 😄

Thanks voor de goede feedback en volgens mij (zag ook je issue voor week 2) ben je inmiddels lekker op weg!


code not working aftere implimentation

used you sample code as it is given in the sample and config json file is copied to config folder in sails js application. getting following error. need your help
error: A hook (controllers) failed to lo
error: Error: watch testConfigurationFile.
at exports._errnoException (util.js:87
at FSWatcher.start (fs.js:1234:19)
at Object.fs.watch (fs.js:1262:11)
at Object.load (C:\ToggleFeatureSample
it\lib\feature-loader.js:12:15)
at Object.load (C:\ToggleFeatureSample
it\index.js:41:26)
at Object. (C:\ToggleFeatur
llers\TestfeatureController.js:14:8)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (modu
at Module.load (module.js:344:32)
at Function.Module._load (module.js:30
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at C:\nodejs\node_modules\sails\node_m
at Array.forEach (native)
at requireAll (C:\nodejs\node_modules
s:44:9)
at buildDictionary (C:\nodejs\node_mod
ctionary\index.js:68:14)

Hi @nikhiljahagirdar
Sorry to hear that you're experiencing issues with the module. Let's see if I can help.
Based on the error message, it seems like it cannot find the testConfigurationFile.json file. You also mentioned:

"...config json file is copied to config folder..."

The example posted in the README assumes that the sample script and the testConfigurationFile.json file are in the same folder. Have you tried updating the flipit.load filepath so that it's pointing to the correct json file?

Hi @nikhiljahagirdar ,
It has been some time since you opened this issue and have been given a response. I'll close this issue, since it does not seem like it's an issue that's blocking you.


[Ewerton Lopes] - celo sage - Como melhorar a segurança de seu smart contract

Thanks for submitting this tutorial for Celo Sage
Before you hit "Create Pull Request", make sure you have read the Tutorial Contribution Guidelines and reviewed the Sample Tutorial Structure.
Please confirm the following before submitting your tutorial for review -

[X] My tutorial follows the Tutorial Contribution Guidelines.
[X] The title of the Pull Request matches the title of my tutorial.
[X] I've followed the tutorial template structure.
[X] I've proofread the tutorial for spelling and grammar mistakes.
[X] I've thoroughly explained the code, with inline code comments and text explanations.
[X] I've run a linter & prettifier to format my code blocks.
[X] I've run the tutorial to test it and the code works.

NOTE: We cannot review your Pull Request if it does not meet the standard outlined above.
Reviewers - @joenyzio & @viral-sangani

Updated as requested


exception propagation via promise.set_exception

Hello!
Thanks for the handy project.
I'm not a multithreading expert, but this code works for me.

thank you for contribution!


Add new indonesian translation

Add new Indonesian translation

Thanks! A few things:

We can't accept any commits without tests. Please add (and translate!) a /test_cases/id.json and make sure that the tests pass.
We don't want or need any .DS_Store files—please remove them!

Hi ironwallaby,
Thank you for your information.
I've added a test cases to the new commit. Kindly check it and let me know your thought.
Regards

Looks great! Thanks for the translation! 👍
I have a couple other things to integrate before deploying this live, but it should be in the API by Monday at the latest.

This is now live.

Thank You


add namespace to root element without prefix

Allowing to add default namespaces
fixes #1

@opoudjis I've added the option to add default namespaces. Is this what you are looking for?

@ronaldtse Sure, I'll update the documentation and add the required test cases.
But what do you really mean by update the reader to indicate this new feature?

@ronaldtse Got it. I'll update the readme.

Let's merge this first because we don't want to wait to use this.


Implement encoding for function calls with dynamic tensors

This PR lifts some restriction of encoding for scalar function call.
As of now, mlir-tv can encode very limited set of functions that succeeds to meet the following criterias.

Function must have only one return value
Function operand(s) must be zero or more scalar (int, float, index) value(s)
Function must return a scalar value or a fixed-size ranked tensor // updated in this PR

More restrictions are to be lifted in the further PRs.

I think the UFs should take the dimension sizes of tensors as arguments too.
For example, this must fail:
   %t = 3xi64 zero tensor
   %t2 = tensor.cast %t to ?xi64
   %t3 = call @f(%t2)
   return %t3
=>
   %t = 2xi64 zero tensor
   %t2 = tensor.cast %t to ?xi64
   %t3 = call @f(%t2)
   return %t3


Sabnzbd improvement: add date to history tab

The sabnzbd module is missing a history field. Will be better if the module shows the date and time of each download, just like all other modules do.

What are you talking about? There is a history tab and it's awesome imo. Do you want a timestamp on each history item?

Oeps. Got the first sentence wrong. It should be, the history tab is missing a date field.

All of the modules I use (couch, sickrage, headphones) start with the date of each history item. For consistency and completeness, the same information should be in place for the sab module.

I agree, I have never thought about that.. I'll add it

Fixed

That's quick, again... Thank you.


OP login bug

Description

I use Craftbukkitlogin, an authentication plugin, for security reason. If I deop myself, i can't login nor register.
Reproduction steps

Register and login using Craftbukkitlogin.
OP myself with LuckPerms.
Exit the server.
Deop myself.
Enter the server.

Expected behaviour

I should be able to use the password i created, or at least make a new one.
Environment details

Server type/version: Spigot running version 1.16.5
LuckPerms version: v5.2.35

Any other relevant details

Okay, apparently i just needed to change manually the password from the plugin file. I have no idea about what happened, but there's no problem now


recent _module.args.pkgs errors over missing system.slice

Issue description
Pinning _module.args.pkgs on a nixpkgs commits from https://github.com/NixOS/nixpkgs/pull/43682/commits/7098b0fcdfd7fa4b82c036d8116b60b78f497316 I'm getting the following build error:
building '/nix/store/8pzgi5p8cskvhvznr1pzdra34rmqxcfv-system-units.drv'...
missing /nix/store/dsw42cg2n5qh5v6vxm9i1qh279fa4bw2-systemd-239/example/systemd/system/system.slice
builder for '/nix/store/8pzgi5p8cskvhvznr1pzdra34rmqxcfv-system-units.drv' failed with exit code 1

This seems related to the removal of system.slice in https://github.com/systemd/systemd/commit/d8e5a9338278d6602a0c552f01f298771a384798.
Steps to reproduce
sudo nixos-rebuild switch using config in https://github.com/tycho01/nix-config/tree/pin/
Technical details
nix-shell -p nix-info --run "nix-info -m" output:
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.48, NixOS, 18.03.132646.08d245eb31a (Impala)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.0.4`
 - channels(root): `"nixos-18.03.132646.08d245eb31a"`
 - channels(tycho): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs`

@tycho01 It seems like the nixpkgs version you're using doesn't contain 0ccab4946d5d0405ebced50a7b7f847730d502a9 (that was the commit that removed system.slice from upstreamSystemUnits) and you've pinned _module.args.pkgs to another version that does (i.e. system.slice is still expected but you're already using systemd 238 or later.
I'm not sure if it's a good idea to pin _module.args.pkgs to a different version in general (could cause other problems like this one).

Okay, I'll try channels then. Thanks!

Just to clarify: Pinning nixpkgs to a specific revision shouldn't cause any problems (at least if the tested job passed / it was released to a channel, e.g. nixos-unstable). But if I'm not mistaken you're pinning the pkgs attribute to a different revision than <nixpkgs>. This could cause problems because the system configuration won't necessarily be compatible with the pinned package versions (like in this case).
Also: Doing something like this should normally be fine as well:
environment.systemPackages = with (import /var/nixos-unstable {}).pkgs; [
  firefox chromium ...
];