Suffix of report xml is missing

I do not know if this is the correct repository. Maybe it is related to itplr-kosit/validator.
Reproduction:
java -jar validationtool-1.3.1-standalone.jar -s validator-configuration/scenarios.xml  -h validator-configuration/test/testsuite/01.13a-INVOICE_ubl.xml
Generates files:
01-report.01a-INVOICE_ubl => Suffix is missing
01.01a-INVOICE_ubl-report.html

@apenski Thank you for the quick response!

fixed in master. @chmoelders  maybe you can build and test it.

@apenski I can confirm that it works.


Update examples/hello

I wrote this for #656, and I think it's an improvement, but it is no longer a counter, which is a nice reactive example. thoughts?

Verified to work nicely on Linux
The UI is getting nicer and nicer every time I look, This shows off what can be achieved  very easily and is nicer that the old example.
+1


Relation objects have no className

When retrieving a relation objects via relation.query, the resulting output have the className of the parent object, even though they have been correctly created, which causes issues downstream.

Ah, thank you. Good catch. Want to try and fix it and put up a patch?
Sent via Superhuman https://sprh.mn/
On Wed, Dec 07, 2016 at 3:05 AM, Bruce<EMAIL_ADDRESS>wrote:

When retrieving a relation objects via relation.query, the resulting
output have the className of the parent object, even though they have
been correctly created, which causes issues downstream.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HustleInc/parse-mockdb/issues/57, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMIeHrYRp1rg7pVcyLTlgl4R2Gp0eJOKks5rFpLzgaJpZM4LGdxE
.

Would love to, but have been struggling to find the culprit- if you can point me in the right direction, I'll get it done.

Fixed in #58! Thanks for the pull request. Sorry, for not responding earlier that code is definitely hacky. I can understand it taking a while to find what to fix!


Organizing Existing Customized Functionality

Below is an organization of existing customized functionalities of ExplainaBoard SDK.
Something could be discussed:

Should we disable 2? (the downside is users with customized datasets couldn't define customized features.
Regarding 4, what would be a good way to introduce customized functions?

1. Customized Dataset

users are allowed to analyze their system outputs on their customized datasets by specifying their formats (e.g.., tsv, json)
Example

        loader = get_loader_class(TaskType.text_classification)(
            load_file_as_str(self.tsv_dataset),
            load_file_as_str(self.txt_output),
            Source.in_memory,
            Source.in_memory,
            FileType.tsv,
            FileType.text,
        )

2. Customized features through system_output file

users are allowed to define and provide the value of customized features by specifying some information in their system output files
This can work for all data loaders
Example: a system output file with customized features

{
  "metadata": {
    "custom_features": {
      "rel_type": {
        "dtype": "string",
        "description": "symmetric or asymmetric",
        "num_buckets": 2
      }
    }
  },
  "examples": [
    {
      "gold_head": "/m/08966",
      "gold_predicate": "/travel/travel_destination/climate./travel/travel_destination_monthly_climate/month",
      "gold_tail": "/m/05lf_",
      "predict": "tail",
      "predictions": [
        "/m/05lf_",
        "/m/02x_y",
        "/m/01nv4h",
        "/m/02l6h",
        "/m/0kz1h"
      ],
      "rel_type": "asymmetric",
      "example_id": "1"
    },
  ...

3. Customized features through an additional config file

user can introduce customized features by specifying the feature name in an external global config file.
Note that this is only valid when DataLab loader is used
Example

{
  "sst2": {
    "custom_features": {
      "example": {
        "label": {
          "dtype": "string",
          "description": "the true label"
        }
      }
    },
...
}

4. Customized feature function through an additional config file

user can introduce customized feature functions by specifying the string-style function in an external global config file.
Note that this is only valid when DataLab loader is used
Example

{
  "sst2": {
    "label": {
      "dtype": "string",
      "description": "the true label",
      "num_buckets": 2
    },
    "text_len": {
      "dtype": "float",
      "description": "text length",
      "num_buckets": 4,
      "func": "lambda x:len(x['text'].split())"
    },
    "long_text": {
      "dtype": "string",
      "description": "whether a text is long",
      "num_buckets": 2,
      "func": "lambda x:'Long Text' if len(x['text'].split()) > 20 else 'Short Text'"
    }
...
}

Thanks @pfliu-nlp ! I created a design doc outlining some of the user stories we need to consider and some design options, let's discuss: https://docs.google.com/document/d/1lX74OrTWEjQT3A6RSandRMNKVjvfaqu-ZVl68sj17oE/edit#heading=h.8fkcz262b48a


Plotting, rebase_on_grid create extra option to specify the run to use as basis for interpolating

Also use this for rebase_on_time


English word forms

I am using the EnglishWordFormHandler for generating the word forms for verb lemmas.
How ever I am confused on how to use the Template object which is required for this task.
I am setting the name of the template object as "en-verb", and I am unable to understand what the parameters to this template object should be. Can you please help me here?
Thank you.

The Template objects model wiki-markup templates. That is, text segments of the raw Wiktionary article  that are enclosed in two curly brackets. For example, {{audio|en-us-run.ogg|Audio (US)|lang=en}} in the article run, which yields a link to a pronunciation file. The template consists of a name ("audio") and multiple parameters, which are either named ("lang=en") or unnamed ("en-us-run.ogg"). The Template class lets you access these properties using getName(), getNumberedParam()and getNamedParam(). The Template objects are typically generated using the TemplateParser.
Mind if you only want to access Wiktionary data, run the parser first (following the example code on the JWKTL homepage) and then use, e.g., IWiktionaryEntry.getWordForms() to access inflected verb forms. You won't need to parse templates then.


Rust nightly warning about dead code

The latest Rust nightly compiler raises a new warning about dead code.
D:\git\windows-rs> cargo check -p windows --features Foundation
warning: struct `IReference` is never constructed
    --> crates\libs\windows\src\Windows\Foundation\mod.rs:1024:12
     |
1024 | pub struct IReference<T>(windows_core::IUnknown, core::marker::PhantomData<T>)
     |            ^^^^^^^^^^
     |
     = note: `#[warn(dead_code)]` on by default

warning: struct `IReferenceArray` is never constructed
    --> crates\libs\windows\src\Windows\Foundation\mod.rs:1281:12
     |
1281 | pub struct IReferenceArray<T>(windows_core::IUnknown, core::marker::PhantomData<T>)
     |            ^^^^^^^^^^^^^^^

warning: `windows` (lib) generated 2 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.14s

This seems like a Rust nightly bug. I don't see what's wrong with this code.
Originally noticed here: https://github.com/microsoft/windows-rs/actions/runs/9501067497/job/26185702630

You can for example use IReference as follows (from another crate):
use windows::{core::*, Foundation::*};

fn main() -> Result<()> {
    let r: IReference<i32> = PropertyValue::CreateInt32(123)?.cast::<IReference<i32>>()?;
    assert_eq!(r.Value()?, 123);
    Ok(())
}

I may just allow dead_code to unblock other work until this is resolved in the Rust compiler.

This seems to be similar to https://github.com/rust-lang/rust/issues/126169


Clarity on 2.0.0

Hello 👋 just wanted to drop a quick note to ask what the breaking changes are for the 2.0.0 release. I realize issues are not really meant for this, but couldn't find a tag or release notes.
Much appreciated!

Hello, I would also like to know the same thing and I couldn't find it anywhere.

Thank you for raising this and I've added a Changelog file we'll keep up to date for future releases.
The main change is related to https://github.com/awslabs/serverless-plugin-lambda-insights/pull/31 and how the wrong Lambda Insights layer is used if the global provider architecture is different than the function level layer version. The deployment in CloudFormation succeeded with the wrong layer version before that PR was merged.


[BUG] CUDA OOM error when loading opt-30b

Describe the bug
I got CUDA OOM error when loading model facebook/opt-30b, however the model can be successfully loaded onto GPUs with huggingface transformers.
RuntimeError: CUDA out of memory. Tried to allocate 98.00 MiB (GPU 3; 22.20 GiB total capacity; 21.47 GiB already allocated; 16.06 MiB free; 21.47 GiB reserved in total by
PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
[2022-11-17 22:47:34,890] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88730
[2022-11-17 22:47:34,912] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88731
[2022-11-17 22:47:34,930] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88732
[2022-11-17 22:47:34,930] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88733
[2022-11-17 22:47:34,955] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88734
[2022-11-17 22:47:34,973] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88735
[2022-11-17 22:47:34,991] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88736
[2022-11-17 22:47:35,060] [INFO] [launch.py:289:sigkill_handler] Killing subprocess 88737

To Reproduce
I ran deepspeed --num_gpus 8 test_deepspeed.py
# deepspeed_test.py
import os

import deepspeed
import torch
from transformers import AutoModelForCausalLM, AutoTokenizer, pipeline

model_name = "facebook/opt-30b"

local_rank = int(os.getenv("LOCAL_RANK", "0"))
world_size = int(os.getenv("WORLD_SIZE", "1"))

tokenizer = AutoTokenizer.from_pretrained(model_name)
tokenizer.add_special_tokens({"pad_token": "[PAD]"})
model = AutoModelForCausalLM.from_pretrained(model_name, torch_dtype="auto")

model = deepspeed.init_inference(
    model,
    mp_size=world_size,
    dtype=model.dtype,
    replace_method="auto",
    replace_with_kernel_inject=True,
)

test = "test prompt"
max_new_tokens = 100

generator = pipeline(task="text-generation", model=model, tokenizer=tokenizer, device=local_rank)

result = generator(test, do_sample=True, max_new_tokens=max_new_tokens)

if not torch.distributed.is_initialized() or torch.distributed.get_rank() == 0:
    print(result)

torch                     1.12.1+cu116
deepspeed                 0.7.4
transformers              4.22.2
Expected behavior
My expectation was if the model can be loaded to GPU with hugginface, it should be able to work with deepspeed inference. Or if there's any clear documentation about how to load large models, it'll help clarify things a lot.
ds_report output
Please run ds_report to give us details about your setup.

System info (please complete the following information):

GPU count and types: a g5.48xlarge EC2 instance, with 8 A10G gpus.

Also facing similar issues

@RezaYazdaniAminabadi thanks for the fix. Is this bug introduced by DeepSpeed or HuggingFace changed the model signature in 4.23 and on?

https://github.com/microsoft/DeepSpeed/pull/2541

Hi @lanking520,
No this should not be related to HF. It was related to this PR which you mentioned in your last message. The problem is it was not injecting the kernels in this case and therefore it was not parallelizing the model.
Thanks,
Reza

@lanking520 and @Tianwei-She please re-open if you're still seeing an issue.


Problems using go get with Go Modules activated

What version of Go are you using (go version)?
go version go1.11 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN="/Users/carlca/Code/go/bin"
GOCACHE="/Users/carlca/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/carlca/Code/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/1d/1rqcnlq51zd4j_vqhp1kv3540000gp/T/go-build524150273=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Navigate to ~
Run go get github.com/<supplier>/<repo>

What did you expect to see?
I expected no error message, just a carriage return, and I expected then to find that the repo had been installed in the specified folder.
What did you see instead?
go: cannot find main module; see 'go help modules'
I gather and hope that the behaviour os go get will change in go 1.12 but, as I have been asking for two weeks now, what are we supposed to do until then?
At the moment I have to do a git clone followed by a go mod int <supplier>/<repo> yet @rsc says that "Module-based go get works for me" https://twitter.com/_rsc/status/1034625354172981248 - but has also said that there is an issue and it has to be sorted for go 1.12 https://github.com/golang/go/issues/24250.
I know I'm not the only one with these questions, but unless I'm missing some very loud and clear messages, it does seem that the communication over these issues has been somewhat lacking.

Like you have correctly found above - this issue is a duplicate of #24250. See also this https://github.com/golang/go/issues/27380 for a similar issue.

I have come up with what is a partial solution. It is a shell script which simulates the go get action. The idea is that one copies the git clone url from github.com and then runs gog.sh <kbd>⌘</kbd>v. One can then run go run, go buildorgo install` as usual.
The contents of gog.sh can be found at https://gist.github.com/carlca/e97eccd545f2465f1e2a0c42356e6ffd.
I use an alias to save me even more keystrokes, alias gog='gog.sh'!

I have come up with what is a partial solution. It is a shell script which simulates the go get action. The idea is that one copies the git clone url from github.com and then runs gog.sh [⌘]v. Of course, with Github.com you can copy the gig clone url with just a couple of keystrokes. One can then run go run, go build or go install as usual.
The contents of gog.sh can be found at https://gist.github.com/carlca/e97eccd545f2465f1e2a0c42356e6ffd.
I use an alias to save me even more keystrokes, alias gog='gog.sh'!

Duplicate of #24250.


Home Page Copy Update

Overview
Update text on home page to be updated from "Tag your project" to "Add your project".
Action Items
Two sections must warrant a text update from "Tag your project" to "Add your project": (image below for reference)

Submenu item under Join the Index
Blue button under "Join a worldwide movement..." text

Resources/Instructions

@maxskewes updated the issue description. Let me know if you need clarity

Figma file has also been updated to reflect this change.


[Diagnostics] Skip overloaded locations where all solutions have the same type

If there are multiple overloads, let's skip locations that produce
the same type across all of the solutions, such location is most
likely a consequence of ambiguity and not its source.
Resolves: rdar://109245375

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test macOS platform

@swift-ci please smoke test


BREAKING CHANGE: Use body replacement instead of details/summary or HTML comments

BREAKING CHANGE: Updates format of Skills courses to meet updated accessibility requirements.  For more information, see https://github.com/skills/introduction-to-github/pull/408

This PR has not followed the commit conventions.
The BREAKING CHANGE:  token must be in the footer of the commit.
Cf. semantic-release/semantic-release#2283

Ah, that would explain for the need for making the tags manually :) I'm terrible about commit descriptions 😂


a question about features on edges and nodes.

Does torchdrug support multi features on edges (nodes), like dgl.edata (dgl.ndata)?
If yes, how to implement it?
Thanks.

Hi, I'm not familiar with the multi-features in dgl. But you can define and register your customized features as in data.features.

Here's what I want to do: build a graph with several kinds of features (i,e, R1, R2, R3) on all edges, use functions like GNN or graph matching, and do a graph-related task like link prediction.
I find torchdrug can only build a graph with one feature (i,e, R) on edges and many functions in torchdrug only support operations over triples (head, R, tail). My goal is to use torchdrug with some modifications and reason over links like (head, R1, R2, R3, tail).
I think, except for data.features, there are many functions needed to be rewritten to meet my goal. Is that right? Do you have some suggestions for me to achieve my goal using torchdrug?
Thanks!

Thanks！


Update ProxyScraper.cs

Added new proxy list. And small change in the api call for proxyscrape.com

useless


Service operator lib copies credentials incorrectly

Issue Summary
When reading from a pod's secret file (e.g., /etc/secrets/sapbtp/xsuaa/...) the created binding does not contain the credentials section
Environment
Kubernetes/Kyma
Steps to reproduce the problem
Try to read a service binding details from the secret file
What is the expected result?
The created ServiceBinding object should contain the complete credentials section
What happened instead?
credentials section does not contain all the required details

Additional information? (attach screenshots if applicable)

https://github.com/SAP/btp-environment-variable-access/blob/main/sap-service-operator/src/main/java/com/sap/cloud/environment/servicebinding/LayeredPropertySetter.java#L40
The code is currently creating a map named credentials inside the credentials map which seems incorrect.

Issue seems elsewhere. Closing this for now


Publish selector subscription issue (#1292)

This is an attempt to show/help to further investigate the issue with publish selector raised on the ticket #1292.
As @alexandru mentioned, this is a timing on subscription, which only happens when a publish selector along with two ChainedObservable operators, one that applies to the hot one (within the brackets) and used after.
As you can appreciate in the ticket the issue was reported with ++ but for simplicity, I have added a test that uses takeLast, which is also a chained one.
The issue can be fixed by avoiding the trampolined execution on the subscription of the ChainedObservable, thus being representing a synchronous subscription flow. Probably there are important reasons why done in that way, so I am unsure if that change would impact negatively on other functionalities. So would be good if someone know of a better alternative to solve it :)

Thanks for tackling this!
It seems like upstream is subscribed before we subscribe to the inner Observable.
I'm not quite sure why though.
I'd expect
s.executeTrampolined(() => subscribeA())
subscribeB()

to always call subscribeA first but maybe I'm rusty or missing something else.

Probably there are important reasons why done in that way, so I am unsure if that change would impact negatively on other functionalities. So would be good if someone know of a better alternative to solve it :)

I feel like this light async boundary is not necessary for PipeThroughSelectorObservable but we should confirm if your solution doesn't break other use cases. I'd be mainly concerned about stack safety.
Although, we should probably start by figuring out what exactly is going on. :D

It seems like on one hand, we need the async boundary for ensuring ordering subscription, removing it only breaks monix.reactive.internal.operators.ConcatCancellationSuite which is a test to ensure that cancelation for chained observables is performed correctly...
A question to clarify myself: Is there any difference (in terms of external functionality for the user) when using
pipeThrougSelector with Pipe.publish and Pipe.replay?
To me, difference is clear when the subjects are used directly, but I am unsure of the difference in the behaviour when they are used with the wrapper method.
I am asking this because this issue does not happen when using Replay with pipeThrough, and that's because there is no weird subscription behaviour happening in there, and maybe we could try replacing it by publishSelector by replySelector or something like that.

It seems like on one hand, we need the async boundary for ensuring ordering subscription, removing it only breaks monix.reactive.internal.operators.ConcatCancellationSuite which is a test to ensure that cancelation for chained observables is performed correctly...
A question to clarify myself: Is there any difference (in terms of external functionality for the user) when using
pipeThrougSelector with Pipe.publish and Pipe.replay?
To me, difference is clear when the subjects are used directly, but I am unsure of the difference in the behaviour when they are used with the wrapper method.
I am asking this because this issue does not happen when using Replay with pipeThrough, and that's because there is no weird subscription behaviour happening in there, and maybe we could try replacing it by publishSelector by replySelector or something like that.

A question to clarify myself: Is there any difference (in terms of external functionality for the user) when using
pipeThrougSelector with Pipe.publish and Pipe.replay?
To me, difference is clear when the subjects are used directly, but I am unsure of the difference in the behaviour when they are used with the wrapper method.

The difference is the same, this example might clear it:
  val source = Observable.intervalAtFixedRate(300.millis)

  val publishSelector = source.publishSelector { hot =>
    Observable.combineLatest2(hot, hot.delayExecution(1.second))
  }

  // List((4,4), (5,4), (5,5), (6,5), (6,6), (7,6), (7,7), (8,7), (8,8), (9,8))
  publishSelector.take(10).toListL.map(println).runSyncUnsafe()

By the time the second Observable starts, other elements are consumed and discarded by the first one and the latest is 4.
  val replaySelector = source.pipeThroughSelector(Pipe.replay[Long], { hot: Observable[Long] =>
    Observable.combineLatest2(hot, hot.delayExecution(1.second))
  })

  // List((3,0), (3,1), (3,2), (3,3), (4,3), (4,4), (5,4), (5,5), (6,5), (6,6))
  replaySelector.take(10).toListL.map(println).runSyncUnsafe()

The first Observable also consumes and discards elements from the source. However, they are cached so when a delayed stream starts, it starts from the first element.

I am asking this because this issue does not happen when using Replay with pipeThrough, and that's because there is no weird subscription behaviour happening in there, and maybe we could try replacing it by publishSelector by replySelector or something like that.

It doesn't happen with replay because elements that are missed due to late subscription are cached and emitted to all new subscribers.
On the surface, it matches the expected behavior but it is less efficient.
All elements that are emitted are cached, even if the source is consuming them and we know that it is the only source.

A question to clarify myself: Is there any difference (in terms of external functionality for the user) when using
pipeThrougSelector with Pipe.publish and Pipe.replay?
To me, difference is clear when the subjects are used directly, but I am unsure of the difference in the behaviour when they are used with the wrapper method.

The difference is the same, this example might clear it:
  val source = Observable.intervalAtFixedRate(300.millis)

  val publishSelector = source.publishSelector { hot =>
    Observable.combineLatest2(hot, hot.delayExecution(1.second))
  }

  // List((4,4), (5,4), (5,5), (6,5), (6,6), (7,6), (7,7), (8,7), (8,8), (9,8))
  publishSelector.take(10).toListL.map(println).runSyncUnsafe()

By the time the second Observable starts, other elements are consumed and discarded by the first one and the latest is 4.
  val replaySelector = source.pipeThroughSelector(Pipe.replay[Long], { hot: Observable[Long] =>
    Observable.combineLatest2(hot, hot.delayExecution(1.second))
  })

  // List((3,0), (3,1), (3,2), (3,3), (4,3), (4,4), (5,4), (5,5), (6,5), (6,6))
  replaySelector.take(10).toListL.map(println).runSyncUnsafe()

The first Observable also consumes and discards elements from the source. However, they are cached so when a delayed stream starts, it starts from the first element.

I am asking this because this issue does not happen when using Replay with pipeThrough, and that's because there is no weird subscription behaviour happening in there, and maybe we could try replacing it by publishSelector by replySelector or something like that.

It doesn't happen with replay because elements that are missed due to late subscription are cached and emitted to all new subscribers.
On the surface, it matches the expected behavior but it is less efficient.
All elements that are emitted are cached, even if the source is consuming them and we know that it is the only source.

@Avasil thanks for that example, it was useful! Will look at it again to see if I find out.

@Avasil thanks for that example, it was useful! Will look at it again to see if I find out.


docs: Add preparation steps for Nebra Outdoor Hotspot

Change-type: minor

Thanks @mattstabeler that's great. Got some more bits to add to this but will merge and then add afterwards 👍


PyFerret fonts syntax

Reported by ansley b manke on 19 May 2015 23:18 UTC
This is all outlined in the document PyFerret Text Syntax:
https://docs.google.com/document/d/1lNnl5FOJRNBev9AtMc319o0FVcrEV8IvKjtCNSJDLe8/
To complete:

Subscript and superscript syntax

Set of translations for special characters using html syntax
τ or τ become lowercase Greek tau,
Τ or Τ become uppercase Greek tau
Reference: http://www.w3schools.com/Html/html_symbols.asp

The DEFINE ANNOTATION, ANNOTATE commands outlined in the Google Doc, incorporating the ideas in Andrew's comments.

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2286

Modified by ansley.b.manke on 20 May 2015 17:09 UTC

Modified by ansley.b.manke on 8 Dec 2015 23:41 UTC


Possiblity to have bookmark bar

Hi.
I love the idea of this, but my workflow is that I have the bookmark bar hidden and only visible on New Tab. With this extension the bookmark bar is not visible there.
Is this something that can even be done?
Thanks.

Hello :wave:,
I looked up possible solutions, but nothing works. This is probably a browser thing and no webextension API allows for controlling the visibility of the bookmarks bar. I might not be completely aware of your workflow, but maybe try to copy/paste your bookmarks directly into Markdown New Tab?
Thanks for opening the issue and let me know of anything else :)
Cheers!


Bug Report: Spelling mistakes in quiz

Reproduction steps
Spelling mistakes can be corrected simply.
Expected behavior
Spellings should be correct.
Actual Behavior

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Hey, @SauravMukherjee44 can you assign this issue to me?

Hey, Could you assign this issue to me, I am a GSSOC '22 contributor.

@abhil2002  @aditiitomar  try to contribute in code not in spelling mistakes like this.


Beginners guide to add their profile from scratch with step by step guide.

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Maintainers can you please check it once !

I previously added it to the README.md file but Maintainer @EmmaDawsonDev told me to add it to the CONTRIBUTING.md file.

Thanks, mistakes solved.

Hang tight with this pull request. We (the maintainers) are just reorganising the folder struccture so that this has a proper place to live. Once everything is in place we'll let you know so it can be moved to the correct folder.

Ok, can you move this into the docs/contributing folder and name it contributing-your-profile.md ?

Sure.

PR raised in docs/contributing folder #1916


Remove Calico autoscaler, as requested, to resolve cpu alerts.

Issy is raising this as @poveyd isn't around today.

https://trello.com/c/Phfs3tRa/2-resolve-cputhrottlinghigh-alert-on-verify-gsp

Seems too easy to just delete the Deployment :D ... was there no other config required?
Also... be aware nothing will delete the deployment, you will have to do it manually

@chrisfarms What do you mean by "other config required"?

I have literally no idea what this is or does or means, so I'm going to :pear: with @blairboy362 to get this out. :tada:


Incompatible files for ppc64le

Hello guys,
I’ve compiled and ran this whole project under x86_64 before, it was successful, it’s a very nice project for IC designers like me, thank you very much!
Now I’m trying to compile these components under ppc64le, some of them were successfully completed, like cts, yosys, router.
For ioPlacer, there is a little problem for me.
It seems like there’re two files maybe pre-compiled for x86_64, not compatible with ppc64le.
A part of detail information is pasted here, please have a look that if it’s possible to provide ppc64le suitable files. Thanks again!
[ 50%] Building CXX object CMakeFiles/ioPlacer.dir/src/IOPlacementKernel.cpp.o
[ 57%] Building CXX object CMakeFiles/ioPlacer.dir/src/LEFParser.cpp.o
[ 64%] Building CXX object CMakeFiles/ioPlacer.dir/src/Main.cpp.o
[ 71%] Building CXX object CMakeFiles/ioPlacer.dir/src/Netlist.cpp.o
[ 78%] Building CXX object CMakeFiles/ioPlacer.dir/src/Parameters.cpp.o
[ 85%] Building CXX object CMakeFiles/ioPlacer.dir/src/Parser.cpp.o
[ 92%] Building CXX object CMakeFiles/ioPlacer.dir/src/WriterIOPins.cpp.o
[100%] Linking CXX executable ioPlacer
/opt/rh/devtoolset-7/root/usr/libexec/gcc/ppc64le-redhat-linux/7/ld: skipping incompatible /ioPlacer/lib/libdef.a when searching for -ldef
/opt/rh/devtoolset-7/root/usr/libexec/gcc/ppc64le-redhat-linux/7/ld: cannot find -ldef
/opt/rh/devtoolset-7/root/usr/libexec/gcc/ppc64le-redhat-linux/7/ld: skipping incompatible /ioPlacer/lib/liblef.a when searching for -llef
/opt/rh/devtoolset-7/root/usr/libexec/gcc/ppc64le-redhat-linux/7/ld: cannot find -llef
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/ioPlacer.dir/build.make:410: ioPlacer] Error 1
make[1]: *** [CMakeFiles/Makefile2:68: CMakeFiles/ioPlacer.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
The command '/bin/sh -c cmake -DCMAKE_BUILD_TYPE=Release -DBOOST_ROOT=/opt/rh/rh-mongodb36/root/usr ..  &&     make' returned a non-zero code: 2

LEF/DEF were added as submodules, this should fix build issues. can you check? Thanks.

LEF/DEF were added as submodules, this should fix build issues. can you check and close the issue? Thanks.

YES!!! It's very nice of you. I've completed to compile these static libraries, both ioplacer and fastroute work fine under ppc64le now.
Also I think it would be very nice to modify the Dockerfiles, from 'git clone' to 'git clone --recursive'.
^_^

The docker file at https://github.com/The-OpenROAD-Project/alpha-release/blob/master/build/docker/ioplacer/Dockerfile has been updated.
Thanks


Add model method withRelations

This method allows you to keep the relationships you need. When you have a model which is dispatched in a job, you might only need 1 or 2 relationships and not all of them. This prevents a huge data feed in as example a job

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


add automated flags for nutrients

@CMack89 suggested adding the gross_range test and BDL levels automatically

This is now available on main branch


Py packaging

the new structure to support building data formulator as a python package, for easy install.
new experimental feature of loading images into Data Formulator as tables.

Example of loading image into Data Formulator (GPT-4o required):
https://github.com/user-attachments/assets/67f7a45b-b81f-4a54-9b88-ea1da750fca0


Python 2 only?

Given the following error:
$ galaxy-package-locator
Traceback (most recent call last):
  File "/home/simon/anaconda3/bin/galaxy-package-locator", line 4, in <module>
    __import__('pkg_resources').run_script('cargo-port==1.0', 'galaxy-package-locator')
  File "/home/simon/anaconda3/lib/python3.5/site-packages/pkg_resources/__init__.py", line 738, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/home/simon/anaconda3/lib/python3.5/site-packages/pkg_resources/__init__.py", line 1506, in run_script
    exec(script_code, namespace, namespace)
  File "/home/simon/anaconda3/lib/python3.5/site-packages/cargo_port-1.0-py3.5.egg/EGG-INFO/scripts/galaxy-package-locator", line 3, in <module>
    __requires__ = 'cargo-port==1.0'
ImportError: No module named 'urllib2'

I suspect it's currently Python 2 only? Might be good to specify that.

You can also search the package here: https://depot.galaxyproject.org/software/
Currently, this tool is only python2, thats true.

Yes, I found that, thanks! No complaints from my side, just a minor suggestion for the documentation.


Could not parse global class... But do not have sense

Godot version
Godot 4.0 Beta 4
System information
Windows 10, Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz  4.10 GHz
Issue description
Hello gentlemen!
I am developing a project in Godot 4 Beta 1 and I have tried to move to Godot 4 Beta 4 because Beta 1 when compiling the app gave me this error "Transient parent has another exclusive child". The problem is that when opening the same project in Beta 4 I get the errors shown in the image.

The problem and the madness is that I am trying to solve the
 Parse Error: Could not parse global class "NakamaSocket" from "res://addons/NakamaNetwork/socket/NakamaSocket.gd".
And when I go to Autoload, the NakamaSocket singelton does not appear and when I try to add it it appears that it already exists. And as you can see, there is nothing. is it a bug? or is there something I am missing?

Steps to reproduce
To test this you can go here https://github.com/heroiclabs/nakama-godot to download the addons folder that contains all the information on client sockets and others, which is the one I am using. And open project.
Minimal reproduction project
No response

The error clearly tell you that the scripts are broken, hence the class is not available. As for autoload problem, a plugin can add an autoload that doesn't appear on the project's list.
Please attach a MRP with ready to test setup.

The error clearly tell you that the scripts are broken, hence the class is not available. As for autoload problem, a plugin can add an autoload that doesn't appear on the project's list.
Please attach a MRP with ready to test setup.

How can my files be broken if they work perfectly in Godot 4 Beta 1? On the other hand. What do you mean by "attach to MRP"? I don't understand this.

https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#provide-a-simple-example-project

@seeergi7 Bump :slightly_smiling_face:

Please attach a MRP with ready to test setup.

Closing due to lack of response. Please comment if you can still reproduce this bug on the latest Godot version.
PS: Since no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.

I have gotten this error just now. The equivalent script of OP was attached to a resource in my case, with a class_name. The sneaky part about this is that from beta14 up to 4.0.1, it appears only on exported builds, never on editors. Will request re-opening once I get an MRP

I stripped down the project I'm working on, so it's essentially an MRP. I would strip it down to oblivion, but some errors won't happen.
MRP: MRP.tar.gz
Error Log: error-log.txt
Build (made for X11 linux):
ConflictResourceConflictExecutable.tar.gz

Reproduction Scenario:

Open the MRP
Export the project (Server Template, basically default choice with all resources/scenes loaded lol)
Open the project (./Server.x86_64)
Quit (Super+Q in my case)
The errors of the error log uploaded above display. That's a lot of script errors which I cannot fix in any way. They do not appear in the editor (if they do, its on opening so they are ignored), only on exported builds.

I am available for any kind of clarification or guidance, as this issue has halted my project (multiplayer game, cant test unless testers install godot and run the game from editor)
@Calinou @KoBeWi

@TheYellowArchitect Please open a new issue, as the exact cause most likely differs.

You are right. I opened https://github.com/godotengine/godot/issues/75582


Copyright plus sfc multi nodes examples

Copyright Info Corrections : Email Adresse Correction + Adding Advisor

Coverage decreased (-0.9%) to 68.528% when pulling 72397a0f5a5ca642c5bd0a2cdee5d57fe5537e5e on AdelBouridah:CopyrightPlusSFCMultiNodesExamples into d661152b0e346dadd5ab5989053a3ac6d8fb06ee on contiv:master.

This PR is somehow broken. Please make sure you have up-to-date version of Contiv in your fork.

Do not open duplicate PRs into master and dev branches, changes from dev will be merged to master.


Add PersianStemmer

Thanks for the PR.
You have done a great job following conventions and putting this together. However, PersianStemmer is not something that already exists in Lucene and we don't have an approval process set up for this sort of thing in .NET (yet).
Options

If you would like to see this released in Lucene.NET sooner rather than later, you can port this great contribution to Java and submit it to the Lucene repository on GitHub. See their Contributing guide for more info.
Alternatively, we can port this to Java and submit the contribution for you (when we get a chance to) and will include it in a future Lucene.NET 4.8.0 release, even though it didn't exist in Java at this version.

Either way, it would be great to keep this PR open and to report the status of the contribution to Lucene back here so we can track the progress and learn about how these sort of approvals work. We will merge it once the Lucene team makes the final approval.

Hi Shad,
I try to port this to Java.
Thank you.

Hi Shad.
I implemented your suggestions.
Please review the changes.

@raminmjj - Looks like the Lucene team decided not to make the PersianStemmer part of the built-in PersianAnalyzer, but expect users to custom build an analyzer if they want to utilize it: https://github.com/apache/lucene/pull/904
I will make the same changes to Lucene.NET in a new PR.

Hi,

Looks like the Lucene team decided not to make the PersianStemmer part of the built-in PersianAnalyzer, but expect users to custom build an analyzer if they want to utilize it: apache/lucene#904

We removed PersianStemmer from PersianAnalyzer only for 9x branch (current maintenance branch) to avoid breaking the backward compatibility in analysis in 9.x, but the change was not reverted from main and will be released in the next major release.


[SPARK-6127][Streaming][Docs] Add Kafka to Python api docs

@davies

Test build #28207 has started for   PR 4860 at commit 82de92a.

This patch merges cleanly.

LGTM, thanks!

Test build #28207 has finished for   PR 4860 at commit 82de92a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28207/
Test PASSed.


How can i ensure that the user has logged in first before navigating to specific route

Let say i have the route "/setting/adminOnly", when my user copy paste the URL to their browser, i should have the logic to that the user needs to login first before going to this route (if he is not logged in yet).
But i don't know where to put this ensurelogin logic, iron-router has that feature, i'm not sure how it should be implemented in vulcanjs. Any thoughts/hint?

I would do that check inside the React component and redirect in the componentDidMount callback.
React-Router might have a route callback feature, but I'm not sure if it would work inside Vulcan…

@iamrommel check this out https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/Redirect.md

I like the implementation here https://medium.com/the-many/adding-login-and-authentication-sections-to-your-react-or-react-native-app-7767fd251bd1
specially the EnsureLoggedInContainer, i just that I'm not sure how to create child route of specific path.
If only I can have something like this
addRoute({name: 'app', path: '/app', componentName: 'EnsureLogin'});
addChildRoute('app', { {name: 'app.workorder', path: '/app/workorder', componentName: 'Layout'}}  )

that will create the child of existing route 'app', which will generate a react-router route like this
 <Route component={EnsureLogin}>
    <Route path=”/app/workorder” component={Layout}/>
  </Route>

I can have the flexibility to define in my route which should be private and public. Which i guess a good addition in vulcan:routing.
I hope I can make a PR for this.

This addChildRoute will be helpful also if we want to define sub-routes in our route.

I don't think I've used child routes before. What's the difference between:
addRoute({name: 'app', path: '/app', componentName: 'EnsureLogin'});
addChildRoute('app', { {name: 'app.workorder', path: '/app/workorder', componentName: 'Layout'}}  )

and
addRoute({name: 'app', path: '/app', componentName: 'EnsureLogin'});
addRoute({name: 'app.workorder', path: '/app/workorder', componentName: 'Layout'})

?

Yep, there is no child route yet, that is the name of method what i'm thinking to implement.
I planned to create a route that is child of a parent route and so 'app' (EnsureLogin) is the parent and 'app.workorder' (Layout) is the child thereby creating a route like this
<Route name="app" component={EnsureLogin}>
    <Route name="app.workorder" path=”/app/workorder” component={Layout}/>
  </Route>

Oh,  On the second thought, i haven't tried if
addRoute({name: 'app', path: '/app', componentName: 'EnsureLogin'});
addRoute({name: 'app.workorder', path: '/app/workorder', componentName: 'Layout'})

will generate the same react-route route as shown above.

I guess the difference with child routes is that you can specify a {this.props.children} prop that works as a nested layout? But I don't know if you need that feature in this specific case?

The nested layout indeed is what i need. That EnsureLogin component can have the specific styles and logic and that will be the base for it's children. For this instance, i can check if the user was logged in from ComponentDidMount (as you suggested earlier to do the logic/check on component level).  Aside from that, i can put more UI customization for certain route only.

import React from 'react';
import {browserHistory} from 'react-router'
import {withCurrentUser, registerComponent} from 'meteor/vulcan:core';

class EnsureLogin extends React.Component {
    componentDidMount() {
        const {currentUser} = this.props;
        if (!currentUser) {
            browserHistory.replace("/login")
        }
    }

    render() {
        const {currentUser, children} = this.props;
        if (currentUser) {
            return children
        } else {
            return null
        }
    }
}

EnsureLogin = withCurrentUser(EnsureLogin);
registerComponent('EnsureLogin', EnsureLogin);

That makes sense. I would accept a PR to add addChildRoute if you can do it then :)

This is an important thing. I support the author and look forward to working with the child routes correctly.

This was actually added a while back. I just updated the docs: http://docs.vulcanjs.org/routing.html

Not worked if i do like this:
addRoute({name: 'main', path: '/', component: MainLayout});
addRoute({name: 'home', path: '/home', component: Home}, 'main');
addRoute({name: 'about', path: '/about', component: About},'main');
i get - Sorry, we couldn't find what you were looking for.


This dependency was not found: @rancher/auto-import in ./pkg/test/index.ts

Setup

Rancher version:2.7
Browser type & version: none

Describe the bug
follow  https://rancher.github.io/dashboard/plugins/plugins-getting-started  create a test plugin
To Reproduce
yarn create @rancher/app my-app
cd my-app
yarn install
yarn dev
Result
ERROR  Failed to compile with 1 errors
This dependency was not found:

@rancher/auto-import in ./pkg/test/index.ts
To install it, you can run: npm install --save @rancher/auto-import

Expected Result
compile with no errors
Additional context
OS:windows 10
node: v16.19.0
yarn: 1.22.19

@jingliangapp Could you provide more detail on where the test pkg came from?

Sorry，add the missiing step:
yarn create @rancher/pkg test
To Reproduce
yarn create @rancher/app my-app
cd my-app
yarn install
yarn create @rancher/pkg test
yarn dev

@richard-cox  This problem exists only on windows, no problem on linux or macos

@jingliangapp Thanks for the update, unfortunately we don't support Windows. This isn't documented anywhere and I've created https://github.com/rancher/dashboard/issues/7759 to do so


Question

This is a great example of building an elastic stack in a VM. I just have one question regarding the x-pack implementation. How do I log in to kibana with this up? I looked in the files and it looks like a variable was assigned {{kibana_user_password}}. But I can't really seem to get it done. Granted I'm a newbie at elk and I was planning on using this to ingest some old logs for a project to visualize the data with kibana. SOS.

Never mind I figured it out. Sorry to bug you!

If this is resolved, then good. I've also commented on the other issue :)


Show error if contract is not present while sending txn

Reason for current bug.
There are two cases :

You cloned se-2 freshly and forgot to do yarn deploy after yarn chain, in this situation you don't have generated dir and if you try to send transatiion it will revert because of this condition

if (!deployedContractData) {
      toast.error("Target Contract is not defined");
      return;
}

The genrated  directory is already present but after you tinker with contract you forgot to do yarn deploy after yarn chain, this is the case where transation are going through even though we havn't deployed the contract.

I think the reason for this is that both ethers and wagmi doesn't check if the address you are calling is a contract or not and since we are calling an EOA with some data filled in transation object it dosen't have any effect and does not revert, hence we are getting Minned Successfully ! and our balance is also getting deducted because its like calling EOA with value as "0.1ETH" and data as function signature and args which doesn't make sense but goes through without reverting (feel free to correct me If I have missed something or wrong 🙌 ) .
Reason for the approach taken
Currently looking at blockchain to see whats stored at deployedContractData.address, if its 0x0 then its high possibility that its not a contract.
Saying  "Possibility" because checkout this https://github.com/ethers-io/ethers.js/issues/494#issuecomment-484567506
Also I saw this approach was taken inse-1 and eth-hooks too  checkout :
https://github.com/scaffold-eth/scaffold-eth/blob/e4afffc7e3d6c2bb575240b4de830703e8925548/packages/react-app/src/components/Contract/index.jsx#L69 internal working of useContractExistsAtAddress here.
Also was suggested here : https://github.com/ethers-io/ethers.js/discussions/3084#discussioncomment-2954385
Instead of handling the error at useTransactor.tsx, handled it inside senContractWriteTx function inside useScaffoldContractWrite hook because I think useTransactor seems like dumb hook which dosen't have context of whats its calling it just calls, to handle error inside useTransactor we need to pass it more arguments.
Last thing currently we are showing error like this :

For this I have createad a new component inside packages/nextjs/components/scaffold-eth because tailwind classes dosen't work inside packages/nextjs/hooks/scaffold-eth since its path not included in tailwind.config.js.
Should we inline it inside useScaffoldContractWrite and add path to tailwind.config.js ? Also I think current approach is not minimal of showing error with component so fee free to point it out and will add a simple message asap instead of creating new components  🙌

Also should we change below message to :
https://github.com/scaffold-eth/se-2/blob/49553af6a7316d1b71cf0f51d09ad5e875a438c6/packages/nextjs/hooks/scaffold-eth/useScaffoldContractWrite.ts#L33
"Target Contract is not defined, did you forgot to do yarn deploy ?"


Prevent tmux nesting

This is the same messaging and behaviour of tmux when you try to nest sessions.

It seems that will prevent users to run overmind c proc from tmux, I always work inside tmux and overmind connects to a process without any problems, @twe4ked what the reason to prevent such nesting?

I double the question :) Are there any problems with Overmind inside tmux?

Nesting tmux sessions does work, but IMO working with them isn't ideal. You need to double hit the prefix key to actually send commands to the nested session. Even quitting the nested session can be confusing, which is why I believe tmux has the error itself.
My reasoning for preventing it is to reduce confusion if you're already running a tmux session and try to connect to one of the processes. If you really do wish to nest the sessions, you can unset TMUX when connecting or make an alias.

I always work inside tmux and overmind connects to a process without any problems

I always work in tmux too but I tried the nested sessions but I assumed it wasn't meant to work that way, and I was meant to open a separate terminal to connect. How do you find working with the nested sessions?

How do you find working with the nested sessions?

Usually I connect to the process to debug something quickly and detach, the only thing that differs from doing that in separate terminal is how you detach, instead of ctrl+b once you need to press it twice to send the prefix through your main tmux session (here some details https://stackoverflow.com/questions/8518815/how-to-send-commands-when-opening-a-tmux-session-inside-another-tmux-session/40666319)

Thanks for the discussion guys! After estimating everything I decided that it would be better to send the user a warning with an explanation on how to perform tmux commands (double hit of prefix key and stuff), wait for any key, and continue. @twe4ked could you update your PR?

Sorry I don't have time right now to add the extra functionality, I don't really know Go so I'd have to go digging through docs to work it out. Thanks for the input everyone!


Problem matcher only matches on restored PTY

I'm trying to fix an issue Alex mentioned (linked in a comment to this issue) by updating the esbuild problem matchers and am running into this issue:

Have these problem matches (on main) https://github.com/connor4312/esbuild-problem-matchers
Run an esbuild task that produces errors
Notice no task errors are detected
Reload the window
Notice the task terminal is restored and problems are now reported

A naive guess is that esbuild lines are not coming all in a single terminal write and tasks don't match regexes correctly when that happens. The Typescript problem matcher always works.

do you know when this bug appeared? IE do you think it's a regression?

Thanks, not sure when I'll get to this honestly. I'll try for October

This is still so annoying...

I have to do it every second time:


Update import functionality

Import is now able to take in file paths with paths consisting of directories with spaces in their name. (Resolves #81)
Update tests to adjust to the updated functionality.
Adjust naming of tests according to the convention.
Remove multiple_file_path test as function is now unable to distinguish between two separate file paths or a space present in the directory naming.
Add filepathWithSpace_success to test for file path with spaces in directory naming.

Codecov Report

Merging #82 (5685c9f) into master (e87473e) will increase coverage by 0.05%.
The diff coverage is 90.00%.

@@             Coverage Diff              @@
##             master      #82      +/-   ##
============================================
+ Coverage     74.91%   74.96%   +0.05%
- Complexity      617      618       +1
============================================
  Files           101      101
  Lines          1977     1981       +4
  Branches        221      222       +1
============================================
+ Hits           1481     1485       +4
- Misses          435      437       +2
+ Partials         61       59       -2

Impacted Files
Coverage Δ

...va/seedu/address/logic/commands/ImportCommand.java
89.65% <75.00%> (+0.18%)
:arrow_up:

...eedu/address/logic/parser/ImportCommandParser.java
100.00% <100.00%> (ø)

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 e87473e...5685c9f. Read the comment docs.


Addon only get fanart from titles from netflix

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

General infomration
If the movie/tv show are from another producer (e.g. Breaking Bad (tv show), Watchmen (movie) and others), fanart and clearlogo doesn't show (empty).
Prerequisites

[ ] Are you running the latest version?
0.10.13

Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Show fanart and clearlogo on all itens.
Actual behavior: [What actually happened]
Fanart and clearlogo only show on movies/tv shows from netflix.
Context (Environment)
Installation

[ ] I installed the plugin via zip from the Releases page
[x] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[x] Windows (x86/x64)
[ ] Linux (ARM)
[ ] Android

Additional informatin on the environment
[Descripe your environment a bit more detailed, are you using LibreElec f.e.]
Debug log
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
Breaking Bad has only poster

Fanart and clearlogo is empty, but thumbnail (miniatura in portuguese) is get it.

If the movie/tv show are from netflix, all art is get it

Cheers
[You can erase any parts of this template not applicable to your Issue.]

@caphm can you pls look at fanart issues? I also have noticed that for != Netflix there are things missing.
Maybe my comment in https://github.com/asciidisco/plugin.video.netflix/pull/396 was correct?

Sorry, the mention got lost in my notifications during vacation.
I have created a PR that fixes the issue with the fanarts. Clearlogo is unfortunately not available for all shows it seems. At least for breaking bad there is no logo displayed in the web frontend either and I assume this might be the case for other shows / movies as well.
If you can find a show / movie that shows a logo in the webinterface but not the addon, please report them here so I can have a look and maybe determine the yet unknown path property to query for it.


jslint.vim:154 crashes with JavaScriptCore on OSX 10.7 Lion

As a workaround, use node.js:
export JS_CMD=which node

Thanks that fixed it for me.

Thanks for suggesting this workaround!  I think that this issue is fixed in the latest version of the plugin.  There is more info in issue #13.


Feature Request: Improve usability without command line

Would prefer better usability within php itself. It is weird to transfer command line paramenter when I could simply set variables. For syncing beta to production servers, I prefer a solid php script instead of opening the cli everytime.
Regards

Hi @ptmr-io,
Thanks for your comment. This is done this way for compatibility with CI environments and DBDiff is essentially just meant to be a command-line tool.
When you say setting variables & you prefer a solid PHP script instead could you please provide an example of what you mean just so we're on the same page?
Thanks!


--json inclusion in the brew info command

This is more related to my experience while trying out Odo for the first time on my MacBook Pro machine. The brew info --installed docker-machine-driver-xhyve command at https://docs.okd.io/latest/minishift/getting-started/setting-up-virtualization-environment.html#for-macos need to have brew info --installed docker-machine-driver-xhyve --json . The reference to the page is on this page: https://github.com/minishift/minishift#documentation

Hey @navalsinghIIM
The best way to update OpenShift documentation would be to ask the people on the OpenShift team at: https://github.com/openshift/openshift-docs
I am however a tad confused with regards to the --json inclusion. Why would you require that? I believe the --json command it included for machine output / other application to feed in that information.

Navals-MacBook-Pro:~ singhn9$ brew info --installed docker-machine-driver-xhyve
Error: installed cannot be passed without json

@navalsinghIIM I'd suggest opening up an issue with the OpenShift docs team: https://github.com/openshift/openshift-docs


Expose FirstRunID in WorkflowExecutionInfo under DescribeWorkflowExecutionResponse

Is your feature request related to a problem? Please describe.
I need to workaround with issue that runId is not stable after continueAsNew or reset.
It's available in https://github.com/temporalio/sdk-go/blob/1f0296cdf9d7655269beed439ad1769dd8040654/internal/workflow.go#L1072 but I also need it from describeWF API
Describe the solution you'd like
Add it in the api and then server
Describe alternatives you've considered
No easy alternative currently (unless I redesign and rebuild the system:( )
Additional context
More context of my current workflows running in production (needed in https://github.com/indeedeng/iwf/issues/404 )
When workflowA is running, it may kickoff a workflowA1 as a child workflow and then waiting for external to signal A1.
A1 is currently based on A's workflowID+"number suffix".
However, this is not sufficient when workflowA us using IdReusePolicy to reuse the workflowID.
This could be fixed if we can use firstRunId instead. Using currentRunID will not work because of continueAsNew and reset.

Feature Request: Stable RunId for Workflow Description API
Is your feature request related to a problem? Please describe.
The current runId for a workflow is not stable after a continueAsNew or reset operation. This issue creates a need for a stable identifier to track and manage workflows in situations where workflowId is reused (e.g., due to IdReusePolicy).
For example, the continueAsNew operation creates a new workflow execution with a new runId while retaining the same workflowId. This makes it difficult to track the history of a workflow across multiple runs, especially when the same workflowId is reused.
Describe the solution you'd like
Implement a mechanism to provide a stable runId for workflow description API calls. This would involve:

Adding firstRunId to the workflow description API: This would return the runId of the first execution within a workflow chain.
Server-side implementation: The Temporal server would need to be updated to store and retrieve the firstRunId for each workflow.

Describe alternatives you've considered
Currently, there is no easy alternative to fix this issue.
Additional context
This problem impacts workflows in production that use child workflows and rely on stable identifiers for managing workflow executions.  For example, consider the following scenario:

Workflow A is running and starts a child workflow A1 based on a naming convention of workflowId+"number suffix".
Workflow A reuses its workflowId due to IdReusePolicy.
This naming convention no longer functions correctly because workflow A will have a different runId after continueAsNew or reset.

Using firstRunId instead of the current runId would solve this issue by providing a stable identifier for the entire workflow chain, regardless of continueAsNew or reset operations.
References:

GitHub Issue
Indeed Engineering iwf issue

This feature request would greatly enhance the ability to track and manage workflows in situations where workflowId is reused. It would also improve the stability and reliability of workflows in complex scenarios involving child workflows and multiple runs.

Thanks for reporting this issue! It looks like you're looking for a way to access the first run ID of a workflow using the describeWF API. Currently, the API doesn't expose this information. However, the information is available in the Workflow Execution Started Event (which the describeWF API returns), as part of the  first_execution_run_id field.
Let me know if you have any more questions.


Should just use one connection

Just looked through the code and realized that it creates a new connection for each request. Does not really make sense to have so many, if simply one will make due. Will be easier on server and also improves performance.
So it should open a bucket on load and then all requests should use the same "bucket-connection".

Like expected is creating a new connection quite expensive. So now it just creates it once and then reuses it.


Any plans to have an online playground ?

Hello !
Any plans to have an online playground ?
Something like:

https://yhirose.github.io/cpp-peglib/
https://chrishixon.github.io/chpeg/playground/
https://peggyjs.org/online.html
https://mingodad.github.io/CocoR-Typescript/playground

Cheers !

Hey, there was this  but it uses an outdated version of Pegase.
Keep in mind there is no "official" release yet, I have the roadmap to V1 in mind with major changes. Will probably be published early spring.


test branch file export

Jira: SOX-20
KBC: https://github.com/keboola/connection/pull/4491
Before asking for review make sure that:
Checklist

[x] New client method(s) has tests
[x] Apiary file is updated

Release

[x] I gave the PR a proper label:

major (BC break)
minor (new feature)
patch (backwards compatible fix)
no release (just test changes)

Sry, za zmatky, commitol som v GH to co si upravil parameter pridam v dalsom PR

rebase


List guidelines not found

https://github.com/kr1sp1n/awesome-gemini/blob/master/contributing.md says "Please ensure your pull request adheres to the list guidelines." but "list guidelines" is a link to a non-existing page.

@bortzmeyer I copied the contributing.md from here. I think the list guidelines are here. But to be honest I don't care about these guidelines. Too much overhead. So I think I will remove or simplify the contributing.md. Thanks for the hint 🙏


fix:tweak

:tada: This PR is included in version 1.0.1-alpha-5.1 :tada:
The release is available on:

GitHub release
v1.0.1-alpha-5.1

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

GitHub release
v1.0.1

Your semantic-release bot :package::rocket:


Allowing a user to retry even if the client does not set the timestamp.

The concern about setting the client timestamp in hbase is safe from the standpoint of most situations.  A Column Family with a single version and gets/scans where version=1 will not have a problem with retries that put in two cells into a qualifier.  Allow a user to set an option that will ensure that a server-side timestamp is set.
This PR is in response to a user request.

LGTM


Prevent date range for selecting through disabled date

Is there a function to prevent date range for selecting dates that are past the disabled date?

I have exactly the same concern. User currently can select a past date for the end date of a range.
Is there y way to prevent the user from doing that ?


plot_predict : 'module' object has no attribute 'indexes'

When I run the ARMAX example: http://pyflux.readthedocs.io/en/latest/arimax.html
I get the following error from  model.plot_predict(h=10,oos_data=data.iloc[-12:],past_values=100,figsize=(15,5)) :
File "/usr/local/lib/python2.7/dist-packages/pyflux/arma/arimax.py", line 778, in plot_predict
date_index = self.shift_dates(h)
File "/usr/local/lib/python2.7/dist-packages/pyflux/tsm.py", line 536, in shift_dates
if isinstance(date_index, pd.core.indexes.datetimes.DatetimeIndex):
AttributeError: 'module' object has no attribute 'indexes'

Same thing is happening to me

I have the same issue.
model = pf.ARIMA(data=df3, ar=10, ma=5, integ=0, target='sold_num')
The 'model' object looks correct and functional, but once I use 'predict' attribution.
df_predict = model.predict_is(h=30)
It shows the error: 'module' object has no attribute 'indexes'
I can run the same script on my other operating system without showing any error.
I try to uninstall and install pyflux again, but it cannot work.
Is there any conflict happen?

I succeded by monkey patching.
Here is my solution:
pd.core.indexes.datetimes.DatetimeIndex = pd.DatetimeIndex

Which pandas version are you using?

In [1]: import pandas
pa
In [2]: pandas.version
Out[2]: u'0.20.3'
"En economía no hay nada misterioso ni inaccesible al entendimiento del
hombre de la calle. Si hay un misterio, reside él en el oculto propósito
que puede perseguir el economista y que no es otro que la disimulación del
interés concreto a que se sirve."
A. Jauretche
On Thu, Sep 28, 2017 at 12:53 PM, Ross Taylor<EMAIL_ADDRESS>wrote:

Which pandas version are you using?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RJT1990/pyflux/issues/112#issuecomment-332880998, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQsotFGnmuPXFv4zC3mPuJgLLsK9xnTks5sm8EFgaJpZM4PKeOE
.

Okay this may be an issue with PyFlux's support for pandas 0.20.3 (and DatetimeIndex module treatment). I'll have a look in the next few days and push out a new version of the library. Thank you for reporting!

(And apologies for late response, but have been tied down with work so not a lot of time to maintain this library recently!)

No problem, I monkey patch it as follows:
class Object(object): pass

pd.core.indexes = Object()
pd.core.indexes.datetimes = Object()
pd.core.indexes.datetimes.DatetimeIndex = pd.DatetimeIndex

Let me know if you want me to make a pull request for you.
In another line of thoughts I would like to ask you something about pyflux VAR method and latent variables calculation. IRC is an option for you?

Thanks guys I am looking at this now - first time I've had a chance to review the library in a while.

Tried with pandas version - '0.21.0' - plot_predict is working for me. Could you upgrade to latest pandas version and reopen this issue if it still raises the same AttributeError for you.


Code Component

Code component using highlightjs
waiting for https://github.com/BuilderIO/mitosis/issues/425

Peding: edit and copy buttons

Pending, to fix some bugs


Unable to apply com.jfrog.artifactory plugin in a build-logic included build gradle.kts precompiled build script

Describe the bug
Specifying the dependency in a root-level build.gradle.kts with a version directly or via version catalog and not applying it but instead opting to apply it inside build-logic convention plugin produces the following error log
* Where:
Precompiled script plugin '***/build-logic/src/main/kotlin/artifactory-publishing.gradle.kts' line: 1

* What went wrong:
Plugin [id: 'com.jfrog.artifactory'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (plugin dependency must include a version number for this source)

Current behavior
Unable to apply com.jfrog.artifactory plugin to lift out the publishing logic into a convention plugin
Reproduction steps
No response
Expected behavior
Being able to set up publishing from a convention plugin inside an included build
Artifactory Gradle plugin version
5.1.13 or any
Operating system type and version
MacOS
JFrog Artifactory version
No response
Gradle version
8.2.0

For those interested in extracting jfrog-artifactory setup into a precompiled convention plugin, here is the quick guide.
To apply jfrog-artifactory inside your convention plugin you first need to satisfy the dependency on it inside build.gradle.kts for your included build
dependencies {
    implementation(libs.jfrog.artifactory)
}

This is where I faced the problem since applying a plugin via implementation is not allowed.
Here is the Gradle spec for addressing this problem, however it's not done yet but there is a workaround described, copying it here in case the link dies:

It is currently not possible to use the plugin id (and version) or the version catalog for dependency declaration, which means the required coordinates have to be known or be derived somehow. The steps to retrieve the coordinates are manual and cumbersome: One has to lookup the plugin on the Plugin Portal, find the coordinates in the legacy snippet at the bottom and copy them from there.

For jfrog-artifactory legacy path is org.jfrog.buildinfo:build-info-extractor-gradle
Adding this as a library to the version catalog and then referring to it from build.gradle.kts dependencies block allows you to add id("com.jfrog.artifactory") to your precompiled convention plugin.
For some reason using artifactory {} block is not possible as it keeps getting unrecognised after getting generated.
For those wondering how to configure it in case you face the same issue, extension is called ArtifactoryPluginConvention, i.e. configure<ArtifactoryPluginConvention> {...}
Hope this helps.

Thank you very much for your guidance, @maksym-moroz!
It will certainly be beneficial to others who encounter this issue.


Discovery improvements

@xuezhaokun @dtarb @martinseul @danames I conferred with Rick Hooper on how to best improve discovery. He made the following tangible observations.

The practice of clicking on a point to list overlapping regions is confusing to the naïve user.
Ordering by number of instances doesn't support use cases in which one is looking for a name in alphabetical order.
Geographical classification of coverages into "global", "continental", "national", "provincial" categories would be useful.

Rick suggests the following enhancements:

Eliminate clicking on a point to show overlapping regions. Do not show any regions by default. Do not show region markers, either. These are confusing.
a. Show point coverages on the map.
b. Show coverages that overlap with the view region in the window below.
c. Allow highlighting one of them by clicking in the listing box. This should zoom to the region in
question.
Organize the listing (on both listing and map pages) into regions via the following rubrics:
a. A global region involves two or more continents.
b. A continental region involves two or more countries.
c. A national region involves only one country.
d. Implement finer subdivisions (state, province, etc) when plausible.
In effect, this defines a "region facet" with values "global", "continental", "national", and "provincial".
Allow facets to be sorted alphabetically rather than just by number of resources.
a. Sort peoples' names by last name, not first name.

This is made somewhat difficult by the fact that some of these facets are not defined in metadata, but must be inferred from imperfect and incomplete information, including the fact that real coverages are polygons but our metadata only records bounding boxes.
For example, it is going to be very easy for a national-scale coverage to be mistaken for continental scale, simply because it overlaps marginally with other countries because countries aren't square. Likewise, it is difficult for us -- without additional metadata -- to conclude that US coverages don't include Canada or Mexico, because of the limits of what we are recording.  Thus, a rather imperfect heuristic is probably needed.

@alvacouch I am all for Discovery improvements.  I recognize that this is a tough problem.  When you review our previous issue on this #1361 you see that comments were all over the map (pun intended).  I worry that the approach of taking input from all is inefficient and generates inconsistent suggestions with the coder getting jerked around a lot.  I think we need someone (or a small group) to carefully think through the discovery goals and options, perhaps reviewing other sites and then propose a holistic design.  I'd prefer an approach different from the way we bounced around previously.  So, saying this about process, I am going to hold back on comments on the specifics.  I have some comments on specifics in #1361 that I think still have merit, but have not been tried and whenever I think about specifics find myself circling back to them.

@dtarb One of the main challenges of these specific suggestions is that several of the suggestions Rick made are not "practical", in the sense that they are not supported by the underlying data model. There are two main themes:

We have insufficient metadata to reliably sort creators by last name(!)
We have  insufficient metadata to reliably categorize coverage resources by geographic region name (global, continental, national, and provincial).

I am going to comment on each of these in detail and in separate issues. Meanwhile, @dtarb, could you briefly enumerate the suggestions that you wish us to consider again from #1361?

@dtarb I think Rick has the proper approach for sorting this out:

Concentrate on "use cases" and "enabling common workflows".
Evaluate each approach as to how well it matches the user's needs.

Here are my suggestions related to the map in response to @alvacouch request.  Some come from #1361, but many are new in reaction to the problems mentioned above.

The map should essentially function as another filter facet with the only difference between the  list tab and the map tab being the map at the top.  The resources listed below the map and displayed on the map when you are in map tab should respond to facet selections, temporal coverage selections and keyword searches just as they do in the list tab.
The display domain and map search box domain should be decoupled.
The display domain should zoom when a user clicks the + or -, or uses a shift drag, or turns on drag zoom mode.
The display should zoom when a user enters a search location and clicks Go as it currently does.
There should be a zoom back button that zooms back to previous display and zoom full button that zooms to the area covering the full extent of the boxes of the resources that satisfy the other active search facets.
The display domain should pan when a user drags the mouse in default mode.
A search rectangle should be activated when a user selects a search tool and then drags to set a rectangle, or when a user clicks a button "Filter by display", in which case it is set to just slightly less than the display so it can be seen.
A search rectangle should be deactivated when a user clicks "Clear map search" button
When a search rectangle is active only resources that overlap or are contained within the search rectangle should be shown on the map.
The search rectangle should be shown as a dashed rectangle.
Switching back to the list tab deactivates the search rectangle.
The resource list below the map should be a long list just as in the list tab.  I do not think it needs a separate scroll bar.
The display should show points for point resources that fall within the domain and satisfy the other active search facets (red dots).
The display should show points for box centers of resources that have box centers within the domain and satisfy the other active search facets
Where there are too many points to show close together a Cluster with the number of points (adding box centers and points) should be shown.
Clicking on a cluster triggers a zoom in to a box defined by the centers of all the points that define the cluster.  Where all points are at exactly the same location the zoom in should be just far enough to exclude all other points that would be on the display from the display and the points that define the cluster should be exploded using a star so each is clickable.
Clicking on a point or box center shows the title as a link to the resource landing page and if it is a box, shows the box on the display.  (Display size is not adjusted but there should be an option to zoom display to show resource extent).
Boxes should not by default be shown.
Boxes should only be shown for resources selected.
Resources may be selected by clicking on their center (which brings up the box and title label pop up) or by clicking on them in the list below (this is how boxes can be shown for resources whose center are not in the display but whose extent matches the selection (and satisfies other selection facets)
Multiple resources may be selected at once (showing multiple boxes on the display)
Selected resources may be clicked again to toggle selection off, and there should be a "Clear selections" button to clear all selected resources and the display of all boxes.

I probably have left things out, but also worry this is too much explicit detail.  While these are my suggestions, I do want to be receptive to other solutions.  I also want to be sensitive to the challenge of implementation and efficient and open to you advancing a solution that while different, works.

@cuahsimarko Is this still relevant given the recent changes to discovery?

@dtarb I think sufficient time has passed and with the most recent changes to Discover a clean process for Maps enhancements might be appropriate. Thoughts?

@cuahsimarko @Castronova I do not think we are done with the mapping part of Discover, but do not have the capacity to address more right now.  I am going to create a new label "Discover map" and use this for all issues that give ideas on this so that when we do have capacity to address it, they can be referred to in a fresh approach.  I'll also leave the label "design phase needed" as these are in this category too.

@dtarb I have a label, geo and maps that has been used to identify those areas across all the GH Issues... can we reuse that?

@dtarb @cuahsimarko I also don't think we're done with the mapping part of discover and using the new label for Discover map will work to separate out discover map issues the "geo and maps" has non discover issues as well

@dtarb @martinseul I just looked again and it appears as though all the Issues labeled geo and maps have been closed, except for one. I'm more inclined to remove that label and go with the new Discover map label. The Discover label should also apply.

@dtarb @martinseul @Castronova I don't think we are done with the Mapping part of Discover. It would be nice to capture Discover map enhancements in a new workflow, with design discussion and collaboration, similar to how the Citations work was outlined. Early involvement of the person, who will implement the work is also a good idea. The conversation should start with requirements, use cases and functionality.

@dtarb I had created the geo and maps label to capture all relevant topics. Adding a Discover label complements that label, in this case. I had spent a lot of time finding all geo and maps Issues and labeling them. Would you be ok with applying the 'Discover" label to this Issue and deleting the new Discover map label? The final state would show the Discover label and geo and maps to identify this work.

I suggest lets not machinate too much over which labels are right.  The "design phase needed" keeps this in a group to consider holistically when we design new functionality.  The "Discover map" says it has ideas for the map part of discover.  Discover is OK because it also refers to discover.  As @martinseul there are a lot of non discover issues related to geospatial information where geo and maps is used.  You are welcome to add that here if you think it helps, but I think it is not really needed.

I think we should have some conventions, though. I like having geo and maps, as I had intended to include Discover Maps but also more than just Discover Maps. I'm ok with creating the third "Discover Maps" label.

Closing per backlog review discussion on 6/9/22. discovery work is happening has part of the CZ Net work. this can be revisited if needed.


Latest pull / clone (af88f91) fails @ TASK [prerequisites : Install the required rpms]

Issue: Latest pull / clone (af88f91) fails @ TASK [prerequisites : Install the required rpms]
Hosting: AWS
RH Atomic AMI:  ami-dbb45dcd containerized=true
Openshift: RH Openshift Container Platform V3.4
Ansible Version:  2.2.0
Git Hash: af88f91a622703cf6cc6549e54c53e0982871acb
Notes:
FYI, The following clone which I pulled some weeks ago works so the change must have been introduce after this time.
Working Git Hash: 00c598647c9c6fae2ea6f22d9e4bf73fa499bd4f
Have not tested Openshift Origin Install.
TASK [prerequisites : Install the required rpms] *******************************
failed: [ose-master02.mydomain.net] (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder']) => {
    "failed": true,
    "item": [
        "atomic-openshift-excluder",
        "atomic-openshift-docker-excluder"
    ]
}

MSG:

Could not find a module for unknown.

Truncated....

PLAY RECAP *********************************************************************
localhost                  : ok=9    changed=5    unreachable=0    failed=0
ose-app-node01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-app-node02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-infra-node01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-infra-node02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-infra-node03.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-master01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-master02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
ose-master03.mydomain.net : ok=8    changed=4    unreachable=0    failed=1

Kind Regards,
SRG

Just trying to recall are you using origin or ocp?
On Mar 21, 2017 9:01 AM, "sensiblemedia"<EMAIL_ADDRESS>wrote:

Issue: Latest pull / clone (af88f91
https://github.com/openshift/openshift-ansible-contrib/commit/af88f91a622703cf6cc6549e54c53e0982871acb)
fails @ TASK [prerequisites : Install the required rpms]
Hosting: AWS
RH Atomic AMI: ami-dbb45dcd containerized=true
Openshift: RH Openshift Container Platform V3.4
Ansible Version: 2.2.0
Git Hash: af88f91
https://github.com/openshift/openshift-ansible-contrib/commit/af88f91a622703cf6cc6549e54c53e0982871acb
Notes:
FYI, The following clone which I pulled some weeks ago works so the change
must have been introduce after this time.
Working Git Hash: 00c5986
https://github.com/openshift/openshift-ansible-contrib/commit/00c598647c9c6fae2ea6f22d9e4bf73fa499bd4f
Have not tested Openshift Origin Install.
TASK [prerequisites : Install the required rpms] *******************************
failed: [ose-master02.mydomain.net] (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder']) => {
"failed": true,
"item": [
"atomic-openshift-excluder",
"atomic-openshift-docker-excluder"
]
}
MSG:
Could not find a module for unknown.
Truncated....
PLAY RECAP *********************************************************************
localhost                  : ok=9    changed=5    unreachable=0    failed=0ose-app-node01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-app-node02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-infra-node01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-infra-node02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-infra-node03.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-master01.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-master02.mydomain.net : ok=8    changed=4    unreachable=0    failed=1ose-master03.mydomain.net : ok=8    changed=4    unreachable=0    failed=1
Kind Regards,
SRG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/289, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADoslKmM_CPKxRIitEWo-JDza0mZfOhzks5rn8obgaJpZM4MjxYk
.

@cooktheryan OCP have not tested Openshift Origin Install.

Version 3.4?
On Mar 21, 2017 9:06 AM, "sensiblemedia"<EMAIL_ADDRESS>wrote:

@cooktheryan https://github.com/cooktheryan OCP have not tested
Openshift Origin Install.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/289#issuecomment-288072156,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADoslDle8ASoT1EoAMAkYfmkLNLTzb8Cks5rn8tTgaJpZM4MjxYk
.

Yep as stated in the original post ;-)

any chance the systems are still up?

this is from CI this morning using the master branch and the following util and ansible packages
atomic-openshift-utils-3.4.67-1.git.0.14a0b4d.el7.noarch
ansible-<IP_ADDRESS>-2.el7.noarch
08:33:50 TASK [prerequisites : Install the required rpms] *******************************
08:34:00 changed: [ose-app-node01.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:01 changed: [ose-app-node02.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:01 changed: [ose-infra-node03.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:01 changed: [ose-master02.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:01 changed: [ose-infra-node02.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:06 changed: [ose-master03.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:09 changed: [ose-master01.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:09 changed: [ose-infra-node01.ci.sysdeseng.com] => (item=[u'atomic-openshift-excluder', u'atomic-openshift-docker-excluder'])
08:34:09
08:34:09 TASK [prerequisites : disable excluder if installed] ***************************
08:34:10 changed: [ose-master03.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-master01.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-master02.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-infra-node01.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-infra-node02.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-infra-node03.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-app-node01.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:10 changed: [ose-app-node02.ci.sysdeseng.com] => (item=atomic-openshift-excluder unexclude)
08:34:11 changed: [ose-master01.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-master03.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-infra-node01.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-master02.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-app-node02.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-infra-node02.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-infra-node03.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)
08:34:11 changed: [ose-app-node01.ci.sysdeseng.com] => (item=atomic-openshift-docker-excluder unexclude)

Thanks Ryan.
So heres what I get when employing 00c5986 (Feb 2):
``

TASK [prerequisites : Install the required rpms] *******************************
skipping: [ose-master03.wookungfu.net] => (item=[])
skipping: [ose-master02.wookungfu.net] => (item=[])
skipping: [ose-infra-node03.wookungfu.net] => (item=[])
skipping: [ose-master01.wookungfu.net] => (item=[])
skipping: [ose-infra-node01.wookungfu.net] => (item=[])
skipping: [ose-infra-node02.wookungfu.net] => (item=[])
skipping: [ose-app-node01.wookungfu.net] => (item=[])
skipping: [ose-app-node02.wookungfu.net] => (item=[])

This goes on to complete install.
Tested af88f91 (latest), 617dd8a (march 9th) f57ec4c (Feb 23)  all fail with same error.
This is employing Ansible 2.2.0
Will try with Ansible 2.2.1

On one of your completed installs can you jump into the system and just run
a yum list and see if the excluder package is available at all?
On Tue, Mar 21, 2017 at 10:02 AM, sensiblemedia<EMAIL_ADDRESS>wrote:

Thanks Ryan.
So heres what I get when employing 00c5986
https://github.com/openshift/openshift-ansible-contrib/commit/00c598647c9c6fae2ea6f22d9e4bf73fa499bd4f
(Feb 2):
``
TASK [prerequisites : Install the required rpms]

skipping: [ose-master03.wookungfu.net] => (item=[])
skipping: [ose-master02.wookungfu.net] => (item=[])
skipping: [ose-infra-node03.wookungfu.net] => (item=[])
skipping: [ose-master01.wookungfu.net] => (item=[])
skipping: [ose-infra-node01.wookungfu.net] => (item=[])
skipping: [ose-infra-node02.wookungfu.net] => (item=[])
skipping: [ose-app-node01.wookungfu.net] => (item=[])
skipping: [ose-app-node02.wookungfu.net] => (item=[])
This goes on to complete install.
Tested af88f91
https://github.com/openshift/openshift-ansible-contrib/commit/af88f91a622703cf6cc6549e54c53e0982871acb
(latest), 617dd8a
https://github.com/openshift/openshift-ansible-contrib/commit/617dd8a51fa48e08e0ec2ff3a2e04c4133d5b6d7
(march 9th) f57ec4c
https://github.com/openshift/openshift-ansible-contrib/commit/f57ec4c625eed0334f45e1cee14d32264649cba1
(Feb 23) all fail with same error.
This is employing Ansible 2.2.0
Will try with Ansible 2.2.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/289#issuecomment-288087326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADoslLxefwTzClsuGE1j9TuzMGCQEOLaks5rn9hsgaJpZM4MjxYk
.

@cooktheryan yum does not exist since I am employing RH Atomic Image and as such its immutable so no packages can be installed right?
$ sudo atomic host status
State: idle
Deployments:
* rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
       Version: 7.3.2 (2017-01-13 22:00:41)
        Commit: 96826a0d917d7ff10f9fd0289581649f2ffbddd76f3b80efd3d95cc11915cacb
        OSName: rhel-atomic-host

Ahh ok thats the ticket. Will start coding the fix now
On Tue, Mar 21, 2017 at 11:03 AM, sensiblemedia<EMAIL_ADDRESS>wrote:

@cooktheryan https://github.com/cooktheryan yum does not exist since I
am employing RH Atomic Image and as such its immutable so no packages can
be installed right?
$ sudo atomic host status
State: idle
Deployments:

rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
Version: 7.3.2 (2017-01-13 22:00:41)
Commit: 96826a0d917d7ff10f9fd0289581649f2ffbddd76f3b80efd3d95cc11915cacb
OSName: rhel-atomic-host

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/289#issuecomment-288106986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADoslJLGi_y4zEew7rj6YGAgas7rMkDsks5rn-argaJpZM4MjxYk
.

Thanks Ryan
Hah, I kicked myself as I wrote that last comment it was right there in front of me all along but I didn't see the connection. :-)

The good thing is it appears the fix only needs this
and not openshift.common.is_atomic | bool

I'm about 3 plays away from that step. Expect the PR soon

Good to hear Ryan.

@sensiblemedia merged the fix

Thanks Ryan.


Change the field to data

Summary of Changes
The data field in requests is widely used while json is not. Internally Lyft's request client doesn't respect json field...
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #82 into master will not change coverage.
The diff coverage is 100%.

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

cc @danwom @jinhyukchang @ttannis

@danwom we need to update the docker compose file once this and FE patch is merged.


Use of JZColumnHeader to modify header font and color

Hello,
I try to use JZColumnHeader to modify the font and the color of the header, I followed your explanations to use it like JZRowHeader but I fail.
I succeed with JZRowHeader overriding  setupBasic function to modify lblTime but I don't know how to do with JZColumnHeader because this function doesn't exist.
I tried overriding init(frame: CGRect) but then in my JZBaseWeekView class, when i do :
if kind == JZSupplementaryViewKinds.columnHeader {
            let columnHeader = collectionView.dequeueReusableSupplementaryView(ofKind: kind, withReuseIdentifier: ColumnHeader.className, for: indexPath) as! ColumnHeader
            columnHeader.updateView(date: flowLayout.dateForColumnHeader(at: indexPath))
            return columnHeader
        }

It doesn't apply changes on my header view.
Can you please help me ?

Have you tried to follow the CustomWeekView.swift?
You should register this class first and implement it in viewForSupplementaryElementOfKind before super

Thank you, it works now.


Rename https://github.com/finos/purealloy to https://github.com/finos/alloy

Rename https://github.com/finos/purealloy to https://github.com/finos/alloy

Done!


EDF blocks access when io is opened.

This is coming from here in Spikeinterface:
https://github.com/SpikeInterface/spikeinterface/issues/1228
Here, basically this format can't only be opened once per file-system.
from pathlib import Path

from spikeinterface.extractors import EDFRecordingExtractor
from spikeinterface.core.base import _load_extractor_from_dict

file_path = Path("/home/heberto/neuroconv_testing_data/ephy_testing_data/edf/edf+C.edf")

recorder = EDFRecordingExtractor(file_path=file_path)
recorder_dict = recorder.to_dict()
recorder_from_dict = _load_extractor_from_dict(recorder_dict)

  File "/home/heberto/miniconda3/envs/spikeinterface_env/lib/python3.10/site-packages/neo/rawio/edfrawio.py", line 70, in _parse_header
    self.edf_reader = EdfReader(self.filename)
  File "pyedflib/_extensions/_pyedflib.pyx", line 146, in pyedflib._extensions._pyedflib.CyEdfReader.__init__
  File "pyedflib/_extensions/_pyedflib.pyx", line 209, in pyedflib._extensions._pyedflib.CyEdfReader.open
  File "pyedflib/_extensions/_pyedflib.pyx", line 181, in pyedflib._extensions._pyedflib.CyEdfReader.check_open_ok
OSError: /home/heberto/neuroconv_testing_data/ephy_testing_data/edf/edf+C.edf: file has already been opened

Wasn't this a long term issue. I have no clue how to fix. Since you have some data from somewhere are you okay trying to make a fix?

Yeah, unfortunately, the fix would be to redo the IO entirely as we use a library for this one and is blocking. I don't think it would be too hard but I would be more weary about testing it.

Mmm now that I think about it, we could use MNE. That should be easier.

@zm711 can you re-open this? I don't think this is fully solved fully yet and the IO is just restricted to get_analogsignal... but it is still blocked.
The solution will be to either use mne or roll this into our own memmaps.

I think it autoclosed when I merged. happy to reopen.

Should I also modify the milestone to future in this case?

Yes, please do.