[Feature]: Dark mode

🚀 Feature Request
Describe the solution you'd like
I would like to add a toggle button which could change the theme of the website between light and dark mode

@Anuran12 same issue is already assigned below.
So closing this issue.


Exclude slf4j-api from metrics-httpclient

Not sure why this wasn't picked up by the enforcer.
metrics-httpclient relies on slf4j-api 1.7.7, not 1.7.10

The slf4j-api dependency is defined in the dependencyManagement section of the parent POM (https://github.com/dropwizard/dropwizard/blob/e85a6b71806a6da35cfc723d9c879d912a0e289f/pom.xml#L292-296) which is why the Maven Enforcer plugin doesn't throw an error.

I see. When I include dropwizard-client and I don't have slf4j-api stuck to 1.7.10 in my dependencyManagement, dropwizard-client tries to bring in both versions and triggers my own enforcer run.
It would be nice for users not to have to set slf4j-api in their dependencyManagement, although it's not a big issue.

No, you're completely right with excluding it. I just wanted to provide an explanation why Maven Enforcer didn't seem to work in this case. Thanks!

Gotcha. Cheers!


Update scheduler configuration

I don't know exactly why, but it works.
According to the docs of the newest pl version, we should use trainer.estimated_stepping_batches property, but in our case, it doesn't work (I updated PL version locally to test it).
Probably it is connected with additional sanity check steps (?) but in spite of using trainer = Trainer(num_sanity_val_steps=0), OneCycleLR scheduler doesn't work neither. :( It work's properly for the fix I proposed in this PR, but I'm not able to explain it well. :(


client: properly close down internal idpool on Close

Client.Close() now also close the internal idPool implementation,
which effectively close the channel in it.

In favor of #70, close this PR.


Normalization of CLI options format (CamelCase => kebab-case)

Even though options values are internally converted to lowercase before being parsed, currently some CLI commands are shown in CamelCase while others in kebab-case.
This PR normalizes the format to (lower) kebab-case (e.g. "HelloWorld" => "hello-world").
Main motivations:

project-wide coherence
inline with how options are normally specified on other programs/tools found on Unix-like OSs
faster to type (opinionated) :-)

Some Examples
Execution strategy
Before
--execution <STRATEGY>
    ...
    [possible values: Native, Wasm, Both, NativeElseWasm]

Now:
--execution <STRATEGY>
    ...
    [possible values: native, wasm, both, native-else-wasm]

Key generation
Before:
--scheme <SCHEME>
    ...
    [possible values: Ed25510, Sr25519, Ecdsa]

Now:
--scheme <SCHEME>
    ...
    [possible values: ed25510, sr25519, ecdsa]

Database
Before and Now:
--database <DB>
    ...
    [possible values: rocksdb, paritydb, paritydb-experimental, auto]

Wasm Execution
Before and Now:
--wasm-execution <METHOD>
    ...
    [possible values: interpreted-i-know-what-i-do, compiled]

Drawback
Because the option's arguments are internally converted to lowercase, this modification is almost fully backward compatible.
The only exceptions are THREE "multiword" arguments that were previously shown as CamelCase strings. With this modification their words are split by the - character (i.e. conversion to lowercase doesn't provide backward compatibility).
These are the three non backward compatible values:

(--execution) "NativeElseWasm" => "native-else-wasm"
(--offchain-worker) "WhenValidating" => "when-validating"
(--sync) "FastUnsafe" => "fast-unsafe"

This is good, but do you think there's an easy way to provide backwards compatibility for those 3 arguments that changed? Ideally printing a warning saying that the pascal case version is now deprecated.

Yes, it can be easily achieved by implementing the FromStr trait for the enum we are parsing:
(this strategy has been already adopted for the options that are already adopting kebab-case format, like database)
Example for "execution strategy"
impl std::str::FromStr for ExecutionStrategy {
	type Err = String;

	fn from_str(s: &str) -> Result<Self, String> {
		if s.eq_ignore_ascii_case("native") {
			Ok(Self::Native)
		} else if s.eq_ignore_ascii_case("wasm") {
			Ok(Self::Wasm)
		} else if s.eq_ignore_ascii_case("both") {
			Ok(Self::Both)
		} else if s.eq_ignore_ascii_case("native-else-wasm") {
			Ok(Self::NativeElseWasm)
		} else if s.eq_ignore_ascii_case("NativeElseWasm") {
			println!("Warning: detected deprecated 'execution-strategy' value '{}', use 'native-else-wasm' instead", s);
			Ok(Self::NativeElseWasm)
		} else {
			Err(format!("Unknown variant `{}`, known variants: {:?}", s, Self::variants()))
		}
	}
}

The only drawback here is that we can't print the warning using the "logger" since it is not active yet.
Here I've used println to print the warn.
Do you think it is a good compromise? Obviously this will be removed after the notice has made its time...

This is good, but do you think there's an easy way to provide backwards compatibility for those 3 arguments that changed? Ideally printing a warning saying that the pascal case version is now deprecated.

@andresilva Yes, it can be easily achieved by implementing the FromStr trait for the enum we are parsing: (this strategy is adopted for the options that are already using kebab-case format, like "database")
Example for "execution strategy"
impl std::str::FromStr for ExecutionStrategy {
	fn from_str(s: &str) -> Result<Self, String> {
		if s.eq_ignore_ascii_case("native") {
			Ok(Self::Native)
	        }
	       ...
		} else if s.eq_ignore_ascii_case("native-else-wasm") {
			Ok(Self::NativeElseWasm)
		} else if s.eq_ignore_ascii_case("NativeElseWasm") {
			println!("Warning: deprecated 'execution' value '{}', use 'native-else-wasm' instead", s);
			Ok(Self::NativeElseWasm)
		} else {
			Err(format!("Unknown variant `{}`, known variants: {:?}", s, Self::variants()))
		}
	}
}

The only drawback here is that afaik we can't emit the warning using the "logger" since it is not active yet. Here I've used println to print the warn.
Do you think it is a good compromise? Obviously this will be removed after the deprecation notice has made its time (~1 major version cycle?!)...

I don't we need to do this. While these values exist, I don't think that anyone ever used them. Even if they used then, clappy will show them the new value.


Unable to connect to database inside Lambda function with VPC

I'm really not sure if this is an issue related to developmentseed/geolambda or osgeo itself.
I'm using geolambda/python layers to access some files in s3 from inside a lambda function. My goal is to send data from s3 to a database. The database is a postgres+postgis in RDS on amazon AWS using VPC. The lambda is using x86_64 with Python 3.7 as it should. I've already configure lambda's VPC and permissions correctly, so I can connect to the database using psycopg2. However, when I try to create the connection with conn = osgeo.ogr.Open(connectionstring), the object conn is None.
I know that everything in connectionstring works, because I can connect to that same database from another computer in the exact same way.

Facing the same issue with MySQL. Were you able to find any work around @RicardoFCJ ?


It's not possible to distinguish between errors

Since this library uses only native Error, it's hard to distinguish the reason why transaction failed. The only way at the moment is to compare error message, which is very cumbersome. I'd like to be able to do the following:
try {
    // some transaction code
} catch (e) {
    if (e instanceof errors.AbortedError) {
         // retry
    }
}

Does this make sense or is there any better way to achieve this?

dgraph-js doesn't use different error types but uses global error constants, so you can do:
try {
    // some transaction code
} catch (e) {
    if (e === dgraph.ERR_ABORTED) {
         // retry
    }
}

Look at file src/errors.ts for all the error values.

I didn't realize those errors were instantiated only once. Thanks 👍

This is not a good practice, because stack traces are generated at the time of instantiating the error. Therefor the error won't have a useful stacktrace


 Was it intentional?

 The plan at the moment, as far as I'm aware, is to release a v10.0.0 including that change once #87 is in.


Configure renovate to bump FLAGD_VERSION in Makefile

Automate the bumping of FLAGD_VERSION in Makefile.

Testing that renovate picks up the version correctly in my forked repo

Success! https://github.com/skyerus/open-feature-operator/pull/63/files


bad version number

in file charts/service-broker-proxy-k8s/Chart.yaml
version set 0.0.0

The idea here was that when we create a new release in GitHub the chart is packaged with this specific version automatically and it is uploaded to releases. See for version 0.1.1 https://github.com/Peripli/service-broker-proxy-k8s/releases/tag/v0.1.1
We could use the latest released version in master but we decided to leave it 0.0.0 which is ok to install with helm.

I see that for tag 0.1.1 the version is bad :

If you don't change the version , the helm chart version will be bad and stick to 0.0.0 so you cannot upgrade your chart deployment. It's a very bad idea to stay 0.0.0 for helm chart.
Note that the helm chart version is frequently not same as application release version as development of application as not the main velocity as the helm chart.

I meant in the uploaded chart to releases the version is changed https://github.com/Peripli/service-broker-proxy-k8s/releases/download/v0.1.1/service-broker-proxy-k8s-0.1.1.tgz But I agree it is strange and we should fix it.


:rocket: Integrate Multicall3 with External Libraries

Overview
Once deployed to the networks outlined in the README, Multicall3 should be integrated into external libraries.
Libraries
A list of external libraries that use existing Multicall or Multicall2 contracts:

[ ] https://github.com/snapshot-labs/snapshot.js
[ ] https://github.com/makerdao/multicall.js
[ ] https://github.com/0xsequence/sequence.js

Is this still worth keeping open?

Closing as Multicall is currently used by many tools:

wagmi
ethers-rs
ethereum-multicall
ethcall


The problem of dividing regions and offsets

Hi, thanks for your great work!
I have some questions to ask:

    keep_mask_s0, drop_lvl_s0 = self.drop_single_shift(batch_win_inds_s0)

    drop_lvl_s0 = drop_lvl_s0[keep_mask_s0]

    voxel_keep_inds = voxel_keep_inds[keep_mask_s0]

    batch_win_inds_s0 = batch_win_inds_s0[keep_mask_s0]

    batch_win_inds_s1 = voxel_info['batch_win_inds_shift1']

    batch_win_inds_s1 = batch_win_inds_s1[keep_mask_s0]

    keep_mask_s1, drop_lvl_s1 = self.drop_single_shift(batch_win_inds_s1)

    drop_lvl_s0 = drop_lvl_s0[keep_mask_s1]

    voxel_keep_inds = voxel_keep_inds[keep_mask_s1]

    batch_win_inds_s0 = batch_win_inds_s0[keep_mask_s1]

    drop_lvl_s1 = drop_lvl_s1[keep_mask_s1]

    batch_win_inds_s1 = batch_win_inds_s1[keep_mask_s1]

According to the above code，after the first area division, the number of voxels after padding and drop in each area is obtained. Why is the first keep_mask used in the second offset division area, and the keep_mask obtained in the second time should be applied to The top is divided for the first time?

I do not fully understand your question. Would you mind making it more clear? It would be fine to use Chinese.
对于第一个问题: 为了去掉被扔掉的token, 在第二次划分之前会使用keep_mask_s0过滤一遍batch_win_inds_s1.
您后面的问题我没太理解．

I do not fully understand your question. Would you mind making it more clear? It would be fine to use Chinese. 对于第一个问题: 为了去掉被扔掉的token, 在第二次划分之前会使用keep_mask_s0过滤一遍batch_win_inds_s1. 您后面的问题我没太理解．

您好。非常感谢您对第一个问题的解答。针对第二个问题：第二次划分之前会进行过滤，但是第二次划分结束后，上述代码14行，会重新扔掉token,那这样我们第一次划分好的区域是不是就不够原有的30，60，100了？（代码12-17不是很理解）

扔掉两次是为了降低实现的复杂度，这样之后两次attention的输入都是一样的．　30/60/100是指会用零值padding到30/60/100, 实际上有效的token数本来就是不到30/60/100的（并且这里还没有真正进行padding），所以再扔掉一点也无妨，最终在get_flat2win_inds_v2函数中还是会把它们padding到30/60/100的．

扔掉两次是为了降低实现的复杂度，这样之后两次attention的输入都是一样的．　30/60/100是指会用零值padding到30/60/100, 实际上有效的token数本来就是不到30/60/100的（并且这里还没有真正进行padding），所以再扔掉一点也无妨，最终在get_flat2win_inds_v2函数中还是会把它们padding到30/60/100的．

明白了。非常感谢您的讲解！


Replace the module with NAVI

Hi my module is without Navi and with only one slot so I can not patch it with toolbox. If I changed the module to a Navi could I patch it? Although originally my radio did not have. The Ships button.

This is MIB1 and Toolbox does not support it.


Shorts Option not working

Shorts hide button not working
[YouTube Reborn v5.0.0 (BETA-5.1)]

Thanks
I use the latest version of Youtube

Try this https://github.com/arichornlover/YouTube-Reborn-v5/releases/tag/v5.0.0-beta5.2 also if you already installed the debs, I recommend doing it again since I reuploaded them with some fixes to the Shorts Options

Thank you it worked

Try this https://github.com/arichornlover/YouTube-Reborn-v5/releases/tag/v5.0.0-beta5.2 also if you already installed the debs, I recommend doing it again since I reuploaded them with some fixes to the Shorts Options

Thank you it worked


fixed codecov

fixed codecov

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.43%. Comparing base (2c7d7cd) to head (b4b9d12).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3895   +/-   ##
=======================================
  Coverage   60.43%   60.43%
=======================================
  Files         105      105
  Lines       13263    13263
=======================================
  Hits         8015     8015
  Misses       5248     5248

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Data file

Dear authors,
When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

Dear authors, When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

And do you konw how the '_fixed_tfidf.pt' files are obtained？

Dear authors, When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

And do you konw how the '_fixed_tfidf.pt' files are obtained？

This file  is available at   https://github.com/CurryTang/Graph-LLM.

Dear authors, When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

Thanks for your interest! The cora_template_sample.json samples from Cora, but it is not generated by LLM/graphedit/data/sample.py. We sample the labeled node pairs in the Cora and set whether there is a connection based on the consistency of the labels. The positive and negative sampling ratio is 2:1. For the Cora, we additionally consider the situation where text is missing. For any node in a node pair where text is missing, we set the connection label as True.

Dear authors, When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

And do you konw how the '_fixed_tfidf.pt' files are obtained？

The data can get from 1. Download TAG datasets

Dear authors, When considering the Cora dataset, could you please clarify how cora_template.json is obtained? Additionally, I guess that cora_template_sample.json is generated by LLM/graphedit/data/sample.py, am I correct?
Thank you very much!

Thanks for your interest!
The cora_template_sample.json samples from Cora, but it is not generated by LLM/graphedit/data/sample.py. We sample the labeled node pairs in the Cora and set whether there is a connection based on the consistency of the labels. The positive and negative sampling ratio is 2:1. For the Cora, we additionally consider the situation where text is missing. For any node in a node pair where text is missing, we set the connection label as True.

Thank you so much for your response.
Can I find the relevant code for generating cora_template.json and cora_template_sample.json in this repository?

Sorry, no code can be used directly, but it can be modified according to LLM/scripts/create_ins.py, and the template is the same. More instruction templates can be found in 3. Instruction Template

Sorry, no code can be used directly, but it can be modified according to LLM/scripts/create_ins.py, and the template is the same. More instruction templates can be found in 3. Instruction Template

Thank you so much for your response  : )


RDS postgres cannot be upgraded from 11.10 to 11.8

I have been running in to issues on each of my terraform applies after initial deploy. The database error specifically is problematic as it messes up deploy of a new container, say in the example where package requirements for our airflow server change. The terraform module will fail on trying to update the RDS and no changes to the server will be inacted.
Can you suggest a solution? I haven't seen this error around and would just like to highlight it.

@DirksCGM 👀 (for reference)

@nicogelders @samueldumont
Just wanted to highlight a solution for this issue.

change Terraform RDS auto_minor_version_upgrade == False to stop AWS RDS from automatically upgrading.

https://stackoverflow.com/questions/66245653/aws-rds-database-version-is-different-than-terraform-version


obtaining per codon counts for each mRNA

Hi,
I was wondering whether riboWaltz can also provide read counts for each individual codon of an mRNA, as this would be very beneficial for downstream analysis when comparing footprint distributions between different conditions.
Kind regards

Hi,
the current version of riboWaltz doesn't provide any information about the number of reads (P-site) per codon, but it's definitely a function that we will implemented in the near future.
Thank you for your question and your suggestion.
Bests,
Fabio

Hi,
I would like to inform you that we just updated the package by the addition of a new function named codon_coverage. It provides the codon coverage defined either as the number of read footprints per codon or as the number of P-sites per codon according to the choice of the user.
We are going to exploit this kind of data in a new function generating transcript-specific profiles and allowing direct graphical comparisons between replicates or conditions.
Bests,
Fabio

Dear Fabio,
These are great news, I will give this a try right away and close the thread since the issue has been addressed.
Best


Add an explanation for φ-quantile to the operators section

Sadly, just linking to the Histogram best practice document, as done
for histogram_quantile, would be confusing here because the best
practice document only deals with quantiles in the context of
Histograms and Summaries, but that has nothing to do with the
quantile aggregator and quantile_over_time function, which is
already a source of a lot of confusion.
Thus, I think the least bad solution is to add a short explanation in
parentheses directly here. There isn't even a good resource on the
internet we can link to. A lot of statisticians use φ-quantiles, but
they don't have a generally accepted name for it.
Conveniently, the quantile aggregator is already at the end of the
list, so the explanation in parentheses doesn't destroy the flow too
much.
A footnote would be a ideal, but I don't know if/how we would do this
in Nanoc.
Fixes #3791 .

Removed the "i.e.".

Will merge on green.


Make WsPathMatcher accessible

Thanks for the pr @MrRamych. What is the use case for this?

In my personal project i use annotation to find services and add their handlers to javalin.
However, once handler was registered, there is no clean way to add another handler to same path.
In my case i use code similar to this
for (Method method : service.getClass().getMethods()) {
    if (method.isAnnotationPresent(WsHandler.class)) {
        //annotation, that contains path and handler type
        WsHandler wsHandlerInfo = method.getAnnotation(WsHandler.class);
        javalin.ws(wsHandlerInfo.path(), wsHandler -> {
            switch (wsHandlerInfo.handlerType()) {
                case CONNECT:
                    wsHandler.onConnect(ctx -> method.invoke(service, ctx));
                    break;
                case MESSAGE:
                    wsHandler.onMessage(ctx -> method.invoke(service, ctx));
                    break;
                case ERROR:
                    wsHandler.onError(ctx -> method.invoke(service, ctx));
                    break;
                case CLOSE:
                    wsHandler.onClose(ctx -> method.invoke(service, ctx));
                    break;
            }
        });
    }
}

It throws IllegalArgumentException every time after first method was added.

Fair enough @MrRamych, thanks for explaining. New release will be in a couple of weeks, I think!


Const value read

Read of const values in config does not propagate back the chosen variant
When setting:

When reading:

This obviously works but is not nice for the eye :smile:
This is a followup from https://github.com/Skaginn3x/framework/pull/297

Similar issue,


Increase retries for retrieving profiler

The git machines serving this data seem to be somewhat flaky, increasing the retries seems to help.
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

Increasing the number of retries doesn't help against this specific error unfortunately 🙁

@fasmat I'll close for now, as I'll be on vacation till the 7th August and this doesn't seem to be helping.


'put' --from file/directory does not work

http://localhost:8080/oba/api/processes:> put 712 --from process_data.json
You should specify option (--data, --follow, --output) for this command

I think this is partly because "data" is a required argument
 Keyword:                  data
   Help:                   The JSON data to use as the resource.
   Mandatory:              true
   Default if specified:   '__NULL__'
   Default if unspecified: '__NULL__'

I'm using version 1.2.1.RELEASE

I'm trying to post several records at once using POST --form bulkfilr and cannot get it to work what should be the format inside this fileI put 10 lines/json simple objects like this {name:'S1"}, it says file uploaded succesfully but my entries not added to the collection


Add OVH provider

Related to rancher/community-catalog#750
Fix rancher/rancher#8735

Tested with :

my community catalog fork https://github.com/stephane-monnot/community-catalog.git   on master
my public docker image : nanoka/rancher-external-dns:latest

@stephane-monnot looks like only vendor.conf got changes, but there are no vendor dependencies updates for ovh. You should run trash (https://github.com/rancher/trash) to pull them in. And on our side, the Drone build should be fixed to catch this type of thing in CI

Done. I am used to ignore vendor.

@stephane-monnot could you exclude trash.lock from the commit?

Done. I tried to rebase with master, but I got some errors with the package dnssimple. It seems to be missing.

@stephane-monnot thanks!


[bug]: Migration of db fails, prosgres too old

2022-01-13T16:08:08.444960Z 2022-01-13 16:08:08.443 UTC [108] FATAL:  database files are incompatible with server
2022-01-13T16:08:08.445399Z 2022-01-13 16:08:08.443 UTC [108] DETAIL:  The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 13.5.

Probably need to upgrade Postgres to match the new 030 version of Mastodon.

It actually seems like it needs to be downgraded. I'm weirded out though that postgres doesn't have the ability to migrate from 12 to 13.

Was the version of mastodon updated from what we had on 02x?

@elvece yes, the old version of mastodon was no longer building because some dependency got yanked

Even after downgrading postgres, a similar bug occurred because 64-bit postgres cannot read 32-bit postgres db files. Renaming to reflect

Fixed by #12


Allow upload to timeseries with data set id

Not an issue: don't need the data set id when uploading data points. The API key needs write access to the data set of the time series.


Allow prebuliding image without a Dockerfile

resolves https://github.com/devcontainers/cli/issues/106


gmailctl: 0.10.0 -> unstable-2022-03-24

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

It'd have been nice if you could have waited more then 32 minutes from the time evaluation finished, to the time you merged. Not to mention the fact that there is no explanation either in the commit message or the PR message for why nixpkgs needs the unstable version. Reverting: https://github.com/NixOS/nixpkgs/pull/165965 .


Idempotency of the kubestellar-kube-bind script

The kubestellar-kube-bind script should be idempotent. That is, given a space, the script should be able to know whether a konnector is started for this specific space, and start it if not.
The script may start multiple konnectors, where the command lines are identical. We discussed this, and @MikeSpreitzer suggests that we can use environment variables to distinguish the konnector processes.

Once we made the script idempotent, we can to use it to ensure the bindings wherever we need. One place is the kubectl-kubestellar-ensure-location script.


MINOR: User Guide: Move Data Types and Information Schema to their own pages

Which issue does this PR close?

N/A
Rationale for this change

Move important content into more prominent location
What changes are included in this PR?

Move Data Types from sql_status to new page
Move Information Schema from sql_status to new page
Delete some now redundant content from sql_status

Are there any user-facing changes?

No

Codecov Report

Merging #3131 (f218124) into master (b1765f7) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3131      +/-   ##
==========================================
- Coverage   85.95%   85.94%   -0.01%
==========================================
  Files         291      291
  Lines       52382    52382
==========================================
- Hits        45025    45022       -3
- Misses       7357     7360       +3

Impacted Files
Coverage Δ

datafusion/expr/src/window_frame.rs
92.43% <0.00%> (-0.85%)
:arrow_down:

datafusion/expr/src/logical_plan/plan.rs
77.43% <0.00%> (-0.35%)
:arrow_down:

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


[TEST] Update Rancher version to 2.9.2 for daily CI run

What's the test to develop? Please describe
Currently daily e2e Rancher integration test runs with Rancher 2.8.2. We need to update Rancher to 2.9.2 and K8s version 1.30.
Rancher is running as VM in the management cluster.

@lanfon72 has already configured Rancher 2.9.2 in new lab. Thanks @lanfon72


[WIP] Gitlab

Opening this PR for tracking purposes and comments from everyone else. There's still some work that needs to be finished up

[ ] Implement and adopt tests
[ ] Make sure we get a new version of the gitlab gem issued
[ ] For GitLab CI to work we need to convince/implement some changes in GitLab

cc @orta, @connorshea, @hjanuschka, @jk

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

          2 Warnings

:warning:
External contributor has edited the Gemspec

:warning:
.gemspec modified

          1 Message

:book:
@k0nserv is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: danger

On the topic of the gitlab gem I've reached out to Narkos over email. He is the registered owner of the gem on https://rubygems.org. Issuing a 3.7.0 of gitlab is currently the largest blocker for this to be merged

@k0nserv any reply from Narkos?

Might be possible to convince them to give @asedge push access

i would be scared if it would work!
how about forking it to gitlab-official  or gitlab-gitlab?

I think it's better we see if we can get either the attention of asedge, or someone who works at GitLab, it's a pretty clear-cut choice to say that they should have access in the absence of Narkos.

I'm undecided as to whether we should try to get control of the gem or create a new one, I've asked fellow GitLabbers for their input.
It'd also be good to have your thoughts, @asedge, seeing as you're the primary maintainer currently.

@orta Do you wanna exclude GitLab CI on account of it not being supported?

You mean merge this, but not let the code-paths be accessible? That can work for me

Either that or not merge it at all. Until they support some way of exposing the MR id in GitLab CI Danger won't work at all, even after that they need to support triggering builds on comments/edits for full support

All though if we include it as it stands right now people are free to build small servers that interact with GitLab's build hooks to expose the correct env variables

I'd merge it and allow people to build their own workflows, even if GitLab CI doesn't work now, people can still use Jenkins or any other form of CI to trigger the build.

The question is not about other CI tools though, it's specifically about Danger::CISource::GitlabCI.

Aye, I'm on the let's merge it, but comment out the Danger::CISource::GitlabCI - it'll end up in the autogenerated docs on the website

I also believe that assuming that Danger only works on PRs is wrong as in fact danger could work on any given changeset. We need to start thinking about removing that tight coupling somehow and maybe even move out PR updaters to a plugin.

I also believe that assuming that Danger only works on PRs is wrong as in fact danger could work on any given changeset.

Could, yes, I guess I can see some usage as a pre-linter, but it might not be worth the overhead for support.

We may need to fork the gem, I don't want this PR sitting idle for this long

It's not unheard of, @KrauseFx had to do it for shenzhen - https://github.com/fastlane/shenzhen

Yes I agree that might be the best course of action. I've been ill for a few weeks so haven't really had the time and energy to work on this unfortunately.

wouldn't it make sense to build this PR in two parts? One preparing danger to go multi source and then another adding GitLab? Some of the changes in this PR would be really nice to have even if GitLab doesn't release the gem.

Yeah I was thinking about extracting

f1df25888402e673269305fd0cb59ffaa0f12829
6604c9ada41e9bf2baacd464a080c9de054646f7
6ff527f02d8962654f9e8b9c77490cbd1fce61e3

into a separate PR because they can all be merged and makes supporting multiple sources easier and can provide value right away

@k0nserv wanted to check up on this, besides the gitlab gem, what else is blocking this?
(Apologies if this was already asked and I forgot 🙈)

@connorshea For this PR specifically the test for request_source/gitlab.rb still need to be written which is the work I've been unable to do due to being ill the past few weeks. From GitLab's side it's still interesting to explore the blockers for GitLab CI, but since there are other CI providers this change can still go into Danger before that

This looks good :+1:  Any update so far? I would like to use Danger for all my projects :smile:

It's looking like it needs some tests, and for a decision around whether we have to have our own fork of the gitlab gem in order to accommodate the changes.
Another option, is that we say it can only be used via a Gemfile with the reference to master for the moment. Shipped with caveats is better than uncertainty.

Yeah still needs more tests, but the most uncertain outstanding question is around the gitlab gem. I raised the question about ownership of the gems with rubygems last week, but I am yet to hear from them. I'd suggest we wait and see if the problem can't be resolved by promoting one of the existing contributors. If that's not possible we'll have to fork it

Ah ok, I'll see if I can copy the GH tests and get them working. Can my commits be added to this PR or would I need to create a separate one?

@deanpcmad it would need to go to this branch on @k0nserv's repo - https://github.com/k0nserv/danger/tree/gitlab

I can handle a lot of the documentation issues that Danger is raising too, post-merge.

Sure thing @deanpcmad you're welcome to take a stab at finishing up the tests. I've invited you to my fork so you can push to this branch.

I've fixed a couple of tests. I can't work out why the EnvironmentManager tests fail though...

Ah, I found the culprit! ENV should have been env 😃

I've just created a MR for adding CI_MERGE_REQUEST_ID into GitLab - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5698

There's another meta problem with GitLab that might be good to document somewhere. From my understanding GitHub and GitLab differs around builds with forks. In GitHub with Travis when you submit a PR from a fork it's built under the namespace of the original project. For example this PR is from my fork, but builds are still build under danger's travis namespace.
On GitLab the default behaviour of forks is that nothing happens unless the fork sets up CI as well. There are open issues for GitLab about changing this behaviour

Found an old issue and for this on GitHub and reopened it on GitLab

So I was working on this and found another issue.
GitLab seems to be stripping out the data attributes from the submitted HTML :(

@deanpcmad thanks ❤ Conflicts on that MR

GitLab seems to be stripping out the data attributes from the submitted HTML :(

Interesting, when I C&P'd the danger HTML into an issue the raw text kept the attributes:

However the rendered markdown doesn't. I would guess that Danger is reading the markdown, so that may be ok?

@k0nserv @orta does GitHub not strip out the data attributes? I'm looking at the Danger table in this thread and there don't seem to be any data attributes.

I was only looking at the frontend, might just be the case that it happends during rendering yes

Yeah my bad it's in the frontend rendering

@deanpcmad Do you have any WIP for this branch? If not I've finished the tests and rebased the branch so I'll force push those changes

@k0nserv go ahead :)

This will require quite some cleaning up among the commits, but I'll do that as the very last thing. Still have a few more tests to write, but for the gitlab request source we now have 100% coverage

:+1: looking forward to adding this to all my tests now :smiley:

There's also the question of organization danger files which isn't implemented yet

Don't do this ATM, I've already removed it in one PR - https://github.com/danger/danger/pull/418 - I'm not sure what its replacement should look like yet

Hey all, we've gotten the current maintainer of the GitLab gem able to ship new releases! 3.7.0 is now out! https://rubygems.org/gems/gitlab

🎉

I believe this should be ready for review now. I haven't written any code to update the status of the merge request yet, but I'd prefer to merge first and then add this

The other thing that remains is updating CI sources that support GitLab. I don't believe this to be a blocker for the merge either

OK, so yeah, this looks good, I have only minor nitpicks about the tests - but that's not a blocker for me at all. I'm going to merge this into another branch on danger ( I want to be able to deploy master whenever ) so I can get this rebased, documented and green. A new PR will be coming in soon, once I get back to my main computer.


Improved percent/URL-encoding

Fixes https://github.com/k6io/har-to-k6/issues/69
Adds a new example/test HAR to verify the above
minor tweak to JSON.parse (json.trim())
minor addition to launch.json to show debug output for "Debug selected HAR" in VSCode

I think the logic for decoding URLencoded postData params needs to be moved to function normalize in src/normalize/index.js.
Mainly to be able to get a HAR in the test builder that actually matches the script.

Hi folks 👋🏻
Heads up that this very specific issue just popped up in a support thread. A user had a very similar issue, and this Pull-Request addressed the Byte-Order-Mark related issue.

I will close this PR. Both problems mentioned in this PR have now been fixed by two recent PRs and are soon to be released.
https://github.com/grafana/har-to-k6/pull/96
https://github.com/grafana/har-to-k6/pull/98


web-ui: add msg component tests

web-ui: add msg component tests.
@mfellner @bhaskarmelkani Two doubts are in my head now that I start working with Jest, React plus node all together.....

For the "react client" we should use snapshot testing or doing like in this PR and test the DOM?
I see some potential problems in the approach used in this PR with DOM testing, caused by the usage of css class names to locate dom nodes... can be problematic to maintain but on the other hand it "really" assures that the dom structure is the one that we expect.

We should use the folder structure that seems "suggested" in JEST documentation?

---\
  |-- client
      |-- components
          |-- dress-code.jsx
          |-- __tests__
             |-- dress-code.test.jsx
  |-- server
      |-- env-handler.js
      |-- __tests__
         |-- env-handler-spec.js

With the above folder structure I see two benefits:
a) tests are close to the source code (personally something that I like)
b) don't go too crazy with relative paths (eg .import {Msg} from '../../../../../src/client/app/components/dress-code.jsx will be ìmport {Msg} from '../dress-code.jsx')
@mfellner @bhaskarmelkani WDYT?

I guess for unit tests,  to me it makes sense to have the the directory structure suggested by JEST.

👍

👍


Improve recipe building algorithm

The algorithm is flawed when creating recipes, especially when there is either an ingredient that appears too many times in the directions or not all the ingredients are used

Hi Gabriel!
I'd love to work on this!

Awesome! I assigned the issue to you

Great! This is a great project, so I'll start working on this right away. Thanks!!!

@gabLaroche, I had started to work on this, but since there are some interesting, facilitating and somewhat impacting changes potentially coming in #13 I will wait until this is merged and update my fork and continue the work on this issue, if that's OK with you.

That is perfectly Ok with me, the last thing I want to cause with this project is stress! I just merged the PR!

#17
@gabLaroche, let me know if you want me to comment the code further.
Also, I was wondering if it was by design that the copy to clipboard functionality didn't include the numbering for the steps?

@sylvaindessureault Nope not by design, that is a bug :) I guess we could hide the <ol>'s list-style-type and add the numbering in a span.


remove Dockerfile

I won't have the resources to maintain a Dockerfile (see discussion e.g. in #2004) and I don't use it. As the image is already outdated for several months it is obvious that users are fine with our current installation procedure that mainly consists of installing a JVM and then running our maintained graphhopper.sh bash script.
Feel free to point to your docker images here. Make sure you always mention the GraphHopper version that is used.
I also removed the pointer to the DEB or RPM packaging because also there no maintainer was found.
I forgot to remove a file: https://github.com/graphhopper/graphhopper/commit/5f324b56c66144e7d6130f5e1195d500ed84ccea

Great project and thanks for the work and dedication you clearly put in!
Sad to see the Dockerfile gone as this makes spinning a new build up very quick and consistent across Windows, Linux, and so on (what I'm facing now!).
Can the blog announcement be updated? [link]

Great project and thanks for the work and dedication you clearly put in!
Sad to see the Dockerfile gone as this makes spinning a new build up very quick and consistent across Windows, Linux, and so on (what I'm facing now!).
Can the blog announcement be updated? [link]


Validation while typing through this library

I've been using this library for development and I realized that you use validation only by submitting the form, it would be nice to perform a validation while the user types, however in the mobile environment.
Well, you made a library that is very well made for performance, but it would be nice to have a validation like that, as you write, you will be validating it.
I had some examples of libraries that do this, but the performance was not ideal, I believe you can do something like this with better performance, because unform came for this, to improve the performance.
Thank you very much in advance!

Pleases edit this issue using issue templates...


Recursive function that passes itself to a helper function not equal its definition

F* cannot prove that my parallel substitution function is equal to its definition when applied to an abstraction. The following assert fails:
    assert(subst (EAbs t e1) s1 = EAbs t (subst e1 (subst_eabs subst s1)));

This is exactly the case that F* couldn't prove terminating, so either the termination problem is causing F* to ignore this match branch, or there is something strange going on.
[3:16:03 PM] Catalin Hritcu: Hey Nik, what happens after F* can't prove a function terminating and it yields a corresponding error; does the definition of the function still get fed to Z3?
[3:16:25 PM] Catalin Hritcu: i.e. does a termination failure affect the logical encoding?
[3:17:38 PM] Catalin Hritcu: I'm asking because the termination argument of my parallel substitution function is highly nontrivial, still I was hoping to prove the rest before returning to termination
[3:18:13 PM] Catalin Hritcu: just that it seems that F* doesn't properly use the non-obviously terminating definition in other proofs

The problem seems to be caused by the recursive function passing itself to a helper function. I've added a self-contained file bug121.fst that reproduces the problem.

We have similar problems with hoisting a nested closure out of the recursive definition of parallel substitution. We can only prove the correctness of hoisting if substitution_extensional lemma has some super general SMT patterns, that increase the checking time of our file by 10s or so. We need a better solution to this.

The simplified bug121a.fst works now, but bug121.fst still fails.

@catalin-hritcu can you kindly repro the issue with --universes and reopen the issue ?

This still appears with --universes:
[hritcu@detained bug-reports]$ fstar.exe --universes bug121.fst
/home/hritcu/Projects/fstar/pub/examples/bug-reports/bug121.fst(57,63-58,26): could not prove post-condition
Error: 1 errors were reported (see above)

My code in bug121.fst regressed since Jun 18, 2016. Now even the code of subst / sub_elam fails with a couple of new subtyping failures:
./bug121.fst(38,28-38,29): (Error) Subtyping check failed; expected type (s#1846:sub{(precedes LexTop (LexCons (LexCons (is_var e) (LexCons (is_renaming s) (LexCons e LexTop))) LexTop))}); got type sub (see ./bug121.fst(33,0-44,30))
./bug121.fst(44,21-44,30): (Error) Subtyping check failed; expected type (e#3592:exp{(precedes (LexCons (LexCons (is_var e@0) (LexCons (is_renaming sub_inc) (LexCons e@0 LexTop))) LexTop) y)}); got type exp (see ./bug121.fst(33,0-44,30))

I updated the code in bug121.fst to use the same definition of sub as in StlcStrongDbParSubst.fst (our flagship STLC development). With this change I can reproduce the original problem, i.e. the following still fails (unless adding the SMTPats):
val sub_lam_hoist : e:exp -> s:sub -> Lemma (requires True)
      (ensures (subst s (ELam e) = ELam (subst (sub_lam s) e)))
let sub_lam_hoist e s = ()

./bug121.fst(56,15-56,63): (Error) could not prove post-condition

This issue seems related to a recent post of @cpitclaudel on the mailing list:
https://lists.gforge.inria.fr/pipermail/fstar-club/2017/000105.html

I think the root cause is the inner definition of sub_elam, which doesn't let F* conclude that the two sides are equal (the RHS uses the top-level sub_elam, which is morally the same, but not quite).
Defining subst and sub_elam mutually recursively makes the final assertion true (although I admitted the termination check for this test).

Confirmed that bug121 still fails


Sec 3.10 uses old register format.

Sec 3.10 uses old register format, e.g.

qreg = QuantumRegister(8, 'q')   # First 4 are for counting, last 4 for 'searching'
t = 4   # no. of counting qubits
n = 4   # no. of searching qubits
creg = ClassicalRegister(4, 'c')
circ = QuantumCircuit(qreg, creg)

I don't know if it should be called the 'old format'. As far as I know, it's the only format to use when we need to specify different registers.
In this section, the explanation uses the notion of there being two qubit registers. So it would make sense to use this notion in the circuit too. However, the circuit actually only uses one register (combining the two), but nevertheless doesn't use the shortened form to declare it.
So there is indeed something that needs to be changed here. Either we keep the circuit with a single qubit register, but change to the shortened form of declaration. Or we use two qubit registers (as in the explanation).

I agree that there are a few places in the textbook where the circuits could be made clearer using multiple QuantumRegisters. Some feedback on the Deutsch-Joza chapter was that the reader forgot which qubits were the 'input' qubits and which the 'output' qubit. I'm sure this can extend to other algorithms such as this one.


Fix Default Address Space for Azure VNets

RFC 1918 specifies <IP_ADDRESS>/8, not <IP_ADDRESS>/6, as part of the private network address space. This fixes what appears to be a typo.

@ahmetalpbalkan  ?

Yes it looks like a typo. So if we merge this only the newly created vnets will get the fix as we check existence of vnet and skip creating/updating it if exists. I don't see a problem merging this.

So I think what you're trying to say is...

LGTM


Use multiple mask per image

Hello,
I see in the original paper, they sometimes use multiple mask (or patch) in a single image.
However, I feel like the code is designed for 1 mask / image.
The function random_bbox only return 1 bbox, and there is no dimension to multiple bbox / image.
Did I miss something ?
Thanks

You are right! It has been discussed in #31

In the original paper, however, they show images with multiple regions in the mask (multiple bboxes). Is it done using the same code ?
Thank you.

@lchauvin Sorry, this repo is not the official code and I am not the paper's author. The official code is implemented in TensorFlow.

Indeed, the v1 implementation uses a patch-based computation for the l1 loss, but it seems gone in the v2 for some reason.


📖 Disable MFA requirement in the Analytical Platform

User Story
As an AP user
I need to log in to AP services without being requested for multiple MFA codes
So that I can access the AP quickly and easily
Value / Purpose
All access to the AP is via GitHub, where MFA is required for all users. As such there is no reason why the AP should also enforce MFA when logging in, as this slows down user access to the platform.
We have also recently had a a number of users complain about this issue, so making this change will reduce support overhead.
Useful Contacts
No response
User Types
No response
Hypothesis
No response
Proposal
Disable MFA in the AP dev and prod tenants. We will disable this on 19/6/2024.
Currently this is enforced via an Auth0 rule named Multifactor-Google-Authenticator-Do-Not-Rename. We should keep this rule in place in case we want to re-enable MFA in the future, but we should amend it so that MFA is disabled for all users. Suggested addition to the top of the rule below:
    let mfa_enabled = false;
    if (!mfa_enabled) {
      console.log("MFA is disabled for all users");
      return callback(null, user, context);
    }

Additional Information
No response
Definition of Done

[x] MFA disabled in dev auth0 tenant
[x] Testing in dev
[x] Notify users of the change
[ ] MFA disabled in prod auth0 tenant
[ ] Testing in prod

Change communicated to users via analytical-platform-support channel https://mojdt.slack.com/archives/C4PF7QAJZ/p1718714782206819

I have disabled MFA requirement in the rule in the dev tenant, and completed testing. Findings below:

Tested logging in to dev control panel, no MFA requirement after clicking "Log in with github" button
From dev control panel, opened VS code and RStudio. Both logged me straight in, no MFA requirement
When logging out of dev Control Panel, I remain logged in to the tool. This is unrelated to the MFA change, as tested in prod and saw the same behaviour:

Log in to Control Panel (with MFA)
Log in to tool (with MFA)
Log out of Control Panel
Remain logged in to tool

Accessing AWS console via control panel, there is no MFA requirement

MFA has now been disabled in the Auth0 production tenant.
To do this, I decided to comment out github from the ENABLED_CONNECTIONS list in the Multifactor-Google-Authenticator-Do-Not-Rename rule.
    var ENABLED_CONNECTIONS = [
        //'github',
        'google-oauth2',
    ];

The reason for this (rather than using the proposed solution) is because there was a possibility that disabling MFA the 'google-oauth2' connection could have unintended consequences.


Problem: There is one master node by default when using cluster?

When setup multi nodes at local, e.g.
iex --name<EMAIL_ADDRESS>-S mix
iex --name<EMAIL_ADDRESS>-S mix
iex --name<EMAIL_ADDRESS>-S mix
After running these nodes and manually ping them for each other.
Scheduler
defmodule QuantumDemo.Scheduler do
  use Quantum.Scheduler, otp_app: :quantum_demo
end

config.exs
config :swarm,
  node_whitelist<EMAIL_ADDRESS>
config :quantum_demo, QuantumDemo.Scheduler,
  global: true,
  overlap: false,
  jobs: [
    [
      name: "cleaner",
      schedule: "* * * * *",
      task: {QuantumDemo, :run_cleaner, []},
      run_strategy: {Quantum.RunStrategy.Random, :cluster}
    ],
  ]

Using:
gen_stage: 0.14.1
quantum: 2.3.3
swarm: 3.3.1
From observer's perspective, I find in swarm application, there is one "master" node<EMAIL_ADDRESS>see the following screenshot) with JobBroadcaster/ExecutionBroadcaster/TaskRegistry

The prepared processes for quantum_demo are both ready:

If I close ac2/ac3 node, this application still working, the restarted and joined nodes can keep run the job working as global.
If I close<EMAIL_ADDRESS>node, the reset cluster nodes won't work together any more with the following error:
2018-10-23 18:30:12.759 [warn] [swarm on<EMAIL_ADDRESS>[tracker:broadcast_event] broadcast of event ({:untrack, #PID<21404.219.0>}) was not recevied by<EMAIL_ADDRESS>2018-10-23 18:30:12.759 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_monitor] lost connection to QuantumDemo.Scheduler.TaskRegistry (#PID<21404.216.0>) on<EMAIL_ADDRESS>node is down
2018-10-23 18:30:12.759 [info] [swarm on<EMAIL_ADDRESS>[tracker:nodedown] nodedown<EMAIL_ADDRESS>2018-10-23 18:30:12.759 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_topology_change] topology change (nodedown for<EMAIL_ADDRESS>2018-10-23 18:30:12.759 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_topology_change] restarting QuantumDemo.Scheduler.ExecutionBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.760 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] starting QuantumDemo.Scheduler.ExecutionBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.760 [debug]<EMAIL_ADDRESS>Unknown last execution time, using now
2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] started QuantumDemo.Scheduler.ExecutionBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_topology_change] restarting QuantumDemo.Scheduler.JobBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] starting QuantumDemo.Scheduler.JobBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.761 [debug]<EMAIL_ADDRESS>Loading Initial Jobs from Config
2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] started QuantumDemo.Scheduler.JobBroadcaster on<EMAIL_ADDRESS>2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_topology_change] restarting QuantumDemo.Scheduler.TaskRegistry on<EMAIL_ADDRESS>2018-10-23 18:30:12.761 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] starting QuantumDemo.Scheduler.TaskRegistry on<EMAIL_ADDRESS>2018-10-23 18:30:12.762 [debug] [swarm on<EMAIL_ADDRESS>[tracker:do_track] started QuantumDemo.Scheduler.TaskRegistry on<EMAIL_ADDRESS>2018-10-23 18:30:12.762 [info] [swarm on<EMAIL_ADDRESS>[tracker:handle_topology_change] topology change complete
2018-10-23 18:30:12.763 [info] GenStage consumer QuantumDemo.Scheduler.ExecutionBroadcaster is stopping after receiving cancel from producer #PID<21404.217.0> with reason: :noconnection

2018-10-23 18:30:12.786 [error] GenServer QuantumDemo.Scheduler.ExecutorSupervisor terminating
** (stop) no connection
Last message: {:DOWN, #Reference<0.1873331614.2499280897.10951>, :process, #PID<21404.218.0>, :noconnection}
State: %ConsumerSupervisor{args: %Quantum.ExecutorSupervisor.InitOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, execution_broadcaster_reference: {:via, :swarm, QuantumDemo.Scheduler.ExecutionBroadcaster}, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}, children: %{}, max_restarts: 3, max_seconds: 5, mod: Quantum.ExecutorSupervisor, name: QuantumDemo.Scheduler.ExecutorSupervisor, producers: %{}, restarting: 0, restarts: [], strategy: :one_for_one, template: {Quantum.Executor, {Quantum.Executor, :start_link, [%Quantum.Executor.StartOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}]}, :temporary, 5000, :worker, [Quantum.Executor]}}
2018-10-23 18:30:12.802 [error] GenServer QuantumDemo.Scheduler.ExecutionBroadcaster terminating
** (stop) no connection
Last message: {:DOWN, #Reference<0.1873331614.2499280897.16020>, :process, #PID<21404.217.0>, :noconnection}
State: %Quantum.ExecutionBroadcaster.State{debug_logging: true, jobs: [], scheduler: QuantumDemo.Scheduler, storage: Quantum.Storage.Noop, time: ~N[2018-10-23 10:30:12.760287], timer: nil}
2018-10-23 18:30:12.802 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_monitor] lost connection to QuantumDemo.Scheduler.ExecutionBroadcaster (#PID<0.351.0>) on<EMAIL_ADDRESS>node is down
2018-10-23 18:30:12.803 [info] GenStage consumer QuantumDemo.Scheduler.ExecutorSupervisor is stopping after receiving cancel from producer #PID<0.351.0> with reason: :noconnection

2018-10-23 18:30:12.804 [error] GenServer QuantumDemo.Scheduler.ExecutorSupervisor terminating
** (stop) no connection
Last message: {:DOWN, #Reference<0.1873331614.2499280898.12891>, :process, #PID<0.351.0>, :noconnection}
State: %ConsumerSupervisor{args: %Quantum.ExecutorSupervisor.InitOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, execution_broadcaster_reference: {:via, :swarm, QuantumDemo.Scheduler.ExecutionBroadcaster}, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}, children: %{}, max_restarts: 3, max_seconds: 5, mod: Quantum.ExecutorSupervisor, name: QuantumDemo.Scheduler.ExecutorSupervisor, producers: %{}, restarting: 0, restarts: [], strategy: :one_for_one, template: {Quantum.Executor, {Quantum.Executor, :start_link, [%Quantum.Executor.StartOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}]}, :temporary, 5000, :worker, [Quantum.Executor]}}
2018-10-23 18:30:12.805 [info] GenStage consumer QuantumDemo.Scheduler.ExecutorSupervisor is stopping after receiving cancel from producer #PID<0.351.0> with reason: :noproc

...
...

2018-10-23 18:30:12.827 [error] GenServer QuantumDemo.Scheduler.ExecutorSupervisor terminating
** (stop) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
Last message: {:DOWN, #Reference<0.1873331614.2499280898.13046>, :process, #PID<0.351.0>, :noproc}
State: %ConsumerSupervisor{args: %Quantum.ExecutorSupervisor.InitOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, execution_broadcaster_reference: {:via, :swarm, QuantumDemo.Scheduler.ExecutionBroadcaster}, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}, children: %{}, max_restarts: 3, max_seconds: 5, mod: Quantum.ExecutorSupervisor, name: QuantumDemo.Scheduler.ExecutorSupervisor, producers: %{}, restarting: 0, restarts: [], strategy: :one_for_one, template: {Quantum.Executor, {Quantum.Executor, :start_link, [%Quantum.Executor.StartOpts{cluster_task_supervisor_registry_reference: QuantumDemo.Scheduler.ClusterTaskSupervisorRegistry, debug_logging: true, task_registry_reference: {:via, :swarm, QuantumDemo.Scheduler.TaskRegistry}, task_supervisor_reference: QuantumDemo.Scheduler.Task.Supervisor}]}, :temporary, 5000, :worker, [Quantum.Executor]}}
2018-10-23 18:30:12.827 [debug] [swarm on<EMAIL_ADDRESS>[tracker:handle_monitor] :"Elixir.#Reference<0.1873331614.2499280898.13027>" is down: :shutdown
2018-10-23 18:30:12.829 [info] Application quantum_demo exited: shutdown

Could you please advise this is a known behavior/design?
If quantum elects one node as "master" by default, can we configure more nodes to be "master" for the availability of application?

@xinz This is a known issue (#374, https://github.com/quantum-elixir/quantum-core/issues/368). I didn't have the time at the moment to come up with a final solution.
I'm going to close the issue as a duplicate therefore.

If quantum elects one node as "master" by default, can we configure more nodes to be "master" for the availability of application?

This is not possible with the current design of the application. If we wanted to implement it like that we'd need a much more complicated setup.
If you would want to have multi master as a feature and are willing to help out with the implementation, feel free to open an issue and start the discussion regarding that.

@maennchen thanks, actually I hope any node shutdown won't affect the job(s) continue working on the rest nodes(if existed), each node of the clusters should be the same role/priority to process the distribution of worker processes.
I will keep watch the related issue.


Fix compilation errors with App.xaml

New user here. I copy-pasted the code from App.xaml like the README said, and while the first 2 lines worked fine, I got compiler errors on the others. Decompiling the assemblies with ILSpy shows that there are no Recommended, Accent, or Primary directories in MaterialDesignColors:

So now I removed the extra directories and everything's good.
This should save other users a lot of headache.

Hi, sorry, there's been some work on the Colors this week and you just caught it in a state of flux...the docs have got a little ahead of the actual Nuget package for the Colors assembly (which is published manually as  it rarely changes).  I am just updating the Colors assembly now, and the .nuspec depedency for the Themes assembly.  Once this is done the App.xaml should work as per the latest docs.

OK  if you update the Themes package to the latest CI build you'll get the latest Colors package, with the new resources.  I will update the WIKI to reflect that they are in effect pre-release instructions.


typeahead: not selecting on click

Partial typing and pressing Enter works, but clicking on an item has no effect.
Can be verified at the typeahead demo i.e. http://valor-software.com/ng2-bootstrap/#typeahead

:+1:
Was trying in the code and at noticed that removing the this.hide() in onBlur() function in typeahead.directive will fix the issue. Obviously this is not a real fix, because somehow the container does need to hide, but at least it points to where the problem lies.

this is fixed already, see https://github.com/valor-software/ng2-bootstrap/issues/363 and https://github.com/valor-software/ng2-bootstrap/pull/398


Mention nested sampling earlier

Section 3.2: I know we might have some (friendly!) differences over here with Dan in particular, but it might be good to mention that optimizing the GPs together with certain physical models out there might not be easy. In particular, when using samplers, it’s very important to keep in mind that for MCMC based inference the starting points can have a huge impact as to whether your fit converges or not. This is particularly true for some hard problems in radial-velocity data, where the GP hyperparameters might fall close to planetary parameters (e.g., GP period and planetary periods), or where multi-modality might be present. I’ve found a lot of success with Nested Samplers on this because of their thorough (although costly!) exploration of the parameter space, as they sample from the prior. All this is to say: might be good to mention Nested Samplers too as a good alternative for sampling here (I know they are mentioned in Section 3.3 --- but they are only mentioned as tools to get the log-evidence)

Added an earlier mention!


QR code to initiate a SEPA wire transfer

People use a lot the feature to pay by wire transfer on allforclimate.
However, it's cumbersome and quite error prone. People have to copy paste the IBAN number and don't always provide the necessary communication to help the host admin to reconcile donations arriving on the bank account. Many also forget to do the actual transfer (a loss for everyone). Others make the donation of the amount for the collective, not including the tip (a loss for OC).
EU institutions have come up with a standard for initiating a SEPA wire transfer with a QR codes that banks must follow: https://en.m.wikipedia.org/wiki/EPC_QR_code
Needless to say that showing such a QR code at the end of the checkout process would greatly improve the UX and reduce human error.
Here is an example that I just tried:

QR code content (note the use of a comma, not a dot, to separate cents):
BCD
001
1
SCT
VDSPBE22
All for Climate / Citizen Corner
BE54891874114597
EUR30,50
CHAR

Donation to the Citizen Corner. Ref: 580520
QR code to initiate a SEPA transfer

And when I scan it with my ING mobile bank app:

See also

Official guidelines
https://en.m.wikipedia.org/wiki/EPC_QR_code
https://www.scan2pay.info

Thank you for the proposal, we already had an issue there.
https://github.com/opencollective/opencollective/issues/5225

Wow, almost a year ago. What's the best way to get this prioritized? Do we need to rally more users/hosts to upvote this request?

@xdamman, we're starting a beta test for the SEPA Debit payments using Stripe, would you be interested in testing this feature? Can you suggest a few collectives where we can enable this?

What is the state of this? Vivid bank also supports this feature and it would make it much easier to contribute using SEPA transfers!


change setting activity to setting fragment

https://github.com/winstonmoon/motivational-todo-list-android/pull/21


Fix CI and bump MSRV

Checklist:

[x] cargo +nightly fmt --all
[ ] Modify CHANGELOG.md if applicable

This fixes both CI, appveyor and travis.
First, moves rustfmt check to its own job and use pinned nightly. Also, removes duplicate keys in the Travis config.
Second, sets MSRV to 1.43.0 to compile deps fine.

Seems a maintainer addressed the issue in a different commit, closing this.


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 3307 ms

Resolved: Samsung performance has improved in caad030.


CD

[x] Domain name (I bought one)
[x] Obtain AWS EC2 (I have one)
[ ] Continuous deployment of backend to AWS EC2 thru GitHub Action
[ ] Continuous deployment of frontend to Vercel thru Vercel CLI - @Dara2004 and I both have accounts already

[ ] Dream goal: static site rendering (SSR)
[ ] Dream goal: switch from MongoDB to CosmosDB, and file system static hosting to Azure Hot Blob
[ ] Dream goal: add caching to backend (NestJS built-in cache or Redis)
[ ] Dream goal: add caching to frontend (SWR) or switch to GraphQL for Apollo Client

Putting on hold for now

Closing as we will not have time for it


Show a users' of achievements on the profile page

A logged in user has access to a profile page:
https://explorers.netlify.com/profile
Once they have attained their first achievement, this should include a list of their achievements including either:

Mention of the reward the've earned if a reward is associated, with a call to action to claim the reward
An indication that their reward has been claimed

@lsell We'd love to get a little design help with this task. We're not looking to redesign this profile page at this stage (although we can evolve it over time) but instead we'd like to add an achievements section to the page in a similar format to the Your Courses progress section. Could you help us with the visuals of this?

Here's a visual output of the said achievement section. Except we need it to look so much better 😄

Although I like positioning this in the sidebar under the certificate progress, the need for flexible text there, and the amount of likely text made it a little incompatible with the narrow element and the centered text. So I've "designed" this as a another component in the body of the profile page.

Here you can see three variants:

with a claimed reward indicator
with a "claim reward" CTA
with no associated reward

Also note the ability to include descriptive text for each achievement which might include markup for the purposes of including links.
All text styles and alignments are taken from the "Your Courses" component.

The notification nude in the menu bar should also use the same device/asset which is echoed in the achievements listing in the profile page. Here's a design for that.

The rosette icon used i both places is available as an SVG. And linked up in slack
https://netlify.slack.com/files/U1U80996Z/F01PQN3PY1M/rosette.svg

Small iteration of the achievement / rewards display to accommodate the representation of a reward code.
Where the reward is for a specific item in the swag store, we should include a link to that item along with suitable instructions of how to redeem this code. I've taken a stab at that language here.


Stop building the app when failure

Fixes https://github.com/plotly/streambed/issues/14719
This PR changes the options used for the set bash builtin so that the deployment fails when there is a failure instead of continuing to build the app.
This is how I tested this:

Using the currently shipped conda buildpack, deploy an app with the following .condarc file, which refers to a non-existing conda channel.

channels:
  - https://my.anaconda.repo:8080/conda/

Notice that even when it fails to fetch the packages from the non-existing conda channel, it continues to build the app and fails at the end of the build because the app can't be started with the following error:

File "/app/app.py", line 1, in <module>
           import dash
       ModuleNotFoundError: No module named 'dash'
       [2021-01-14 21:13:51 +0000] [204] [INFO] Worker exiting (pid: 204)
       [2021-01-14 21:13:51 +0000] [13] [INFO] Shutting down: Master
       [2021-01-14 21:13:51 +0000] [13] [INFO] Reason: Worker failed to boot.
=====> end conda-app web container output
To hamza400.plotly.host:conda-app
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@hamza400.plotly.host:conda-app'

Add a .buildpacks file to the app directory root and point it to this buildpack repo's branch that I pushed my change to and deploy again.

Notice that now it fails and exits the deployment as soon as it doesn't find the conda channel:

remote: An HTTP error occurred when trying to retrieve this URL.
remote: HTTP errors are often intermittent, and a simple retry will get you on your way.
remote: ConnectionError(MaxRetryError("HTTPSConnectionPool(host='my.anaconda.repo', port=8080): Max retries exceeded with url: /conda/linux-64/repodata.json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f5db4a81898>: Failed to establish a new connection: [Errno -2] Name or service not known'))"))
remote:
remote:
To hamza400.plotly.host:conda-app
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@hamza400.plotly.host:conda-app'

@tarzzz, could you please review?

Thanks @tarzzz I thought of doing that as well after I submitted my PR and tested it. It works too, I'll add it to my test plan above.

Thanks @tarzzz I thought of doing that as well after I submitted my PR and tested it. It works too, I'll add it to my test plan above.


Standard Region template should have a button slot alongside the title

Substitution strings #PREVIOUS# #NEXT#, respectively before and after the title. Vertically centered.

Button should be after the title only, right aligned to the container. Standard region and card region.


Run Travis CI Tests Against Multiple k8s Versions

Is your feature request related to a problem? Please describe.

The problem is that the automated e2e tests for eunomia that are run through Travis CI are only executed against a single k8s version. The user of eunomia are more than likely running on a variety of k8s versions. Also, right now it is difficult know if updating eunomia dependencies will break eunomia(Go version, operator-sdk version, updating/adding Go modules).
Describe the solution you'd like

Update minikube to the latest version
Create a Travis CI build matrix to run e2e tests in parallel against multiple k8s versions
Use k8s versions 1.17, 1.16, 1.15, and 1.11 in the build matrix

Describe alternatives you've considered

Roll the dice each release and hope that it works.
What version of eunomia are you using?
eunomia version: v0.1.1
Additional context

In the future we will want to make sure that we add a build matrix for OpenShift versions too. But that is not in scope for this enhancement request.

The initial test matrix has been created and minikube has been updated to the latest version. I still need to ...

finalize the k8s versions to be used in the test matrix
fix issue with the deploy step running for each item in the matrix

I need to do something similar to this to only run the deploy stage once.
https://docs.travis-ci.com/user/build-stages/matrix-expansion/

It works ... https://travis-ci.com/KohlsTechnology/eunomia/builds/148846276.


Possibilty to skip creation of RAW DBs

We have an issue with the creation of RAW DBs whose names exceed the number of characters (32!)
Would it be possible to have a flag to skip the creation of RAW DBs?
This is not necessarily something that is used for every project, particularly if we go directly to datapoints (like DB extractor or many customer extractors running on extractor-utils)
the best would be of course to increase the number of characters in the RAW DB name, but that is out of our control
Getting the error below
cognite.client.exceptions.CogniteAPIError: dbName is too long. dbName cst2:prj:001:ship:002:rawdb:state cannot have more than 32 characters.
by setting this line to False, everything runs smoothly
https://github.com/cognitedata/inso-bootstrap-cli/blob/4d4d14992d3a84c612dff8cc973908580727802e/incubator/bootstrap_cli/__main__.py#L823
i hope it is possible to consider such a flag :)
But i understand if you think it would make it too custom, but that would prevent us from using it and we would need to fork the repo to adapt it to our needs which we would like to avoid 👍

@gaetan-h pls checkout branch new-flag-with-raw-capability

and test diagram and deploy with new parameter
see PR #29 comment for examples how to use them

skipping some of the "templated access-control packages" (like RAW DBs) is against the idea of this approach

supporting a workaround here (for a special case, which don't require any RAW capabilities) is mitigating the 32chars name-length limit of RAW DBs
in parallel I started a discussion to get more "room to breath" for structured-hierarchical-namespaces (256 characters for name or externalId` properties of access-control related CDF configurations)

but as there is no ETA when this change will happen, we have this this new CLI parameter for now

Thanks @spex66 will check it out :)

Looks good, completed successfully now

closing this issue

merged PR #29 and new feature is available in v1.10.0 now for deploy and diagram commands :)
thx for the request and testing @gaetan-h
thx @sdorheim for review


TOTP not accepted:

Prerequisite
Read this, have a little chuckle to yourself.
After that: no seriously really do confirm it. Most of the reported issues with TOTP follow that pattern.
PAM config
E.g. /etc/pam.d/ssh, or common-auth if it uses that.
SSH config (or equivalent if not using SSH)
/etc/ssh/sshd_config
Enable debug on the module, and paste what's logged
Maybe from /var/log/auth.log.
Ns.4444<EMAIL_ADDRESS>

I'd need the contents of those configs.
And… I don't know what those characters are at the end of this issue, but it's not the contents of any logfile.


Add Python 3 support.

This PR contains some changes to make sure the right libraries and
dependencies are loaded to support Python 3. There is no big change in the source code since most
of the code is Python 3 compatible.
Apart from that there are some improments and bug fixes included:

Implement base class for resin exceptions.
Fix a bug in resin.models.device.get_all_by_application() to make it
works with API v3.

Maybe you should also add python3.5 and python3.6 to the .travis.yml config? :)

...and perhaps the PR description should be updated to say that this fixes #35 and #45 ?

@lurch, I've fixed all your comments, can you check the PR again please?

This all LGTM now, but I won't "approve" this PR as I've not run any of the code in this repo and I've never even used the Resin API. I'll request Tim, since he approved your other SDK changes :)


Linux 4.7.3 keyboard not working

Issue description
Linux Kernel 4.7.3 seems broken, as my laptops keyboard doesn't work.
experienced by the arch community too: https://bugs.archlinux.org/task/50700
Steps to reproduce
update, reboot - 4.6 and 4.7.2 work, 4.7.3 doesn't
Technical details

nixos-version: 17.03.git.8179a23 (Gorilla)
nix-env --version: nix-env (Nix) 1.11.4
nix-instantiate --eval github/nixpkgs -A lib.nixpkgsVersion: "17.03.git.515bc7c"

Same issue with kernel 4.4.20 (lts). I can no longer enter my cryptsetup password.

@Mic92 Thanks, created a quick fix with your solution, which should fix it for everyone


Enable editing in the View/Edit Hours screen of MainScreen.

Table edits should actively edit the data.

Implemented with commit 1018357.


Missed jobs scheduler not working for retries

According to docs:
Missed Jobs Periodical Handler
Recommended especially when you don't use Sidekiq Pro's super_fetch. If you dequeue job from Redis and the process is killed (by OOM, for example) then good luck with having the job finished. However, if the job is stored in Postgres, this is not an issue. You can just look for the jobs that look as if they were missed and re-enqueue them. Periodically.

That being said it works only for the case when OOM would happen on first attempt.
If first attempt fails, then failed_at will be set. Then on retry OOM happens. Missed Jobs Scheduler uses:
def missed_jobs(missed_job_policy:)
      jobs_database
        .where(completed_at: nil, dropped_at: nil, failed_at: nil)
        .select { |potentially_missed_job| missed_job_policy.call(potentially_missed_job) }
    end

to find missed jobs, so as failed_at was assigned - it's never rescheduled.
As I understand the biggest challenge is to figure out which missed job qualifies due to backoff, so perhaps this scenario should be addressed on specific application knowing it's internals. On the other hand whenever it's supposed to be retried we could bump execute_at to match next attempt. That way we could easily find  jobs that were supposed to be executed already?
That being said - we should at least mention that in documentation as right now it can give false confidence in reliability of this gem.

@StoneFrog How about explicitly assigning "missed" label when rescued for the first time, so that we could use or query, like jobs_database.where(completed_at: nil, dropped_at: nil, failed_at: nil).or(jobs_database.where(completed_at: nil, dropped_at: nil, missed_job: true))? looking for missed jobs is executed every few hours, so having some potential conflicts and risk of duplication and processing the same job twice etc. is very low

@Azdaroth what do you mean with "when rescued"? When failed_at is set for the first time?
Assuming it was actually a legit non-recoverable failure won't that interfere with retry? i.e. even though regular sidekiq would push that to retry queue with exponential backoff, we will be executing that every time  missed job scheduler is executed?

@StoneFrog By "rescued" I mean the one that were picked Missed Jobs Handler.
Maybe it would interfere, but what's the risk here? Some jobs might be executed a couple of times and fail each time I guess (otherwise, it would be executed just once) and it would happen only to the one that were labeled as such.
This of course depends on the frequency of the OOMs but they should not be that common to make more than few % of all jobs (which would already be massive but probably we could live with that).

@Azdaroth But that problem is that Missed Job Handler never picked them.

@StoneFrog that's why we would need to introduce some extra labelling and change the query. Wouldn't that be enough ?

@Azdaroth Maybe I don't fully get you proposal, but you have said that:
you want to label it when "rescued" and by rescued you mean the one that were picked Missed Jobs Handler.
But in described case they will never be picked by handler, so they will never be labeled and this query won't change a thing 😛


where the logs conversion chat is stored for retraining?

As mention in the docs https://nlu.rasa.ai/closeloop.html
where the log files of conversion are stores ?

There is a configuration value where you can configure that, it is called response_log: https://nlu.rasa.com/config.html#response-log

Yes I tried that, but still log file of conversion is not generates.
configuration file:
{
"pipeline": "spacy_sklearn",
"path" : "./models/nlu",
"data" : "./data/nlu.md",
"language": "en",
"response_log": "logs/",
"log_level": "INFO",
"log_file": "./logs"
}

We changed the configuration in the latest master. Would be good if you could try there. Otherwise I'd suggest to remove the trailing slash from response_log: 'logs/'

I'll close this for now, please let us know if you have any further questions.

@tmbo  it would be great if we can have the server also push logs to the cloud say aws s3 like it does for models .

Absolutely, pushing response logs to AWS S3 would be very useful.

Hope this helps someone. If you run the server using the following command the logs file will be generated under the project root logs folder
python -m rasa_nlu.server --path projects --response_log logs


Question: How can this package be used to download img from a URL?

How can this package be used to download img from a URL? Is there any example for this?

I am working to add a downloadFromUri function. Meanwhile you may get a Stream from the package of your choice (e.g. http or dio) and pass it to the download function.
I will let you know when i complete the new function.

I am working to add a downloadFromUri function. Meanwhile you may get a Stream from the package of your choice (e.g. http or dio) and pass it to the download function.
I will let you know when i complete the new function.

Hello,when will it be finished?Thanks!

There is ETA. But i do my best to update the package ASAP.

How do you create a stream compatible with the library from dio?

@newradius
Any Stream object will do.

@newradius Any Stream object will do.

I tried with:
Future downloadFile(String imageUrl) async {   Response<ResponseBody> rs;   rs = await Dio().get<ResponseBody>(     'https://i.picsum.photos/id/492/1920/1080.jpg?hmac=_kiWj9u8dWK4CKGUbl3Yp2GM1bQzyse4KKBhvedwfz4',     options: Options(         responseType: ResponseType.stream), // set responseType to stream`
);
download(rs.data.stream, 'image.png');
}`
But the stream is not compatible: The argument type 'Stream' can't be assigned to the parameter type 'Stream

Can you send a full project? Either a link to github repo or attaching a zip file.

Sure, you can download it here https://we.tl/t-8LsRqMRw1I the piece of code is located at lib/image_container/image_container_widget.dart
The project was made with flutterflow.

ok, here's the fix use need:
  final stream = rs.data!.stream.transform(
    StreamTransformer<Uint8List, int>.fromHandlers(
      handleData: (value, sink) {
        for (final v in value) {
          sink.add(v);
        }
      },
    ),
  );

  download(stream, 'image.png');


Added ability to dismiss modal by tapping on the background

Closing this because it clashes with user expectations, and isn't opt-in. Tapping at the top doesn't dismiss modals in iOS; it scrolls to the top. There is no way to check for that, or scroll to the top, so this change cannot be implemented


Cannot "try" path operations. 'pname' of undefined

Hi, this looks like a great project! I'm trying to integrate the component into a svelte application.
This is the code I'm using to invoke the element in Svelte.
<script>
    import 'rapidoc'; // <-- import rapidoc
</script>

<div>
    <rapi-doc
        spec-url = "REMOVED_FOR_GITHUB"
        style = "width:100%"
        render-style = "read"
    > </rapi-doc>
</div>

<style lang="scss">
    rapi-doc {
        height: calc(100vh - 150px)
    }
</style>

The rapidoc component shows up and looks wonderful. But anytime I try to "try" an endpoint, I get an error saying...
rapidoc-min.js:5409 Uncaught (in promise) TypeError: Cannot read property 'pname' of undefined
    at rapidoc-min.js:5409
    at Array.map (<anonymous>)
    at HTMLElement._callee9$ (rapidoc-min.js:5409)
    at tryCatch (runtime.js:45)
    at Generator.invoke [as _invoke] (runtime.js:274)
    at Generator.prototype.<computed> [as next] (runtime.js:97)
    at asyncGeneratorStep (web.url.js:1007)
    at _next (web.url.js:1007)
    at web.url.js:1007
    at new Promise (<anonymous>)

This is the swagger json spec I'm giving it (edited to remove dev server...)
{
    "openapi": "3.0.1",
    "info": {
        "title": "DeploymentTest",
        "version": "0.0.0"
    },
    "servers": [
        {
            "url": "REMOVED_FOR_GITHUB"
        }
    ],
    "paths": {
        "/admin/HealthCheck": {
            "post": {
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {}
                        }
                    }
                },
                "responses": {}
            }
        },
        "/admin/Docs": {
            "post": {
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {}
                        }
                    }
                },
                "responses": {}
            }
        },
        "/Sum": {
            "post": {
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "properties": {
                                    "numbers": {
                                        "title": "numbers",
                                        "type": "array"
                                    }
                                }
                            }
                        }
                    }
                },
                "responses": {}
            }
        },
        "/AdminGrant": {
            "post": {
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "properties": {
                                    "dbid": {
                                        "title": "dbid",
                                        "type": "integer"
                                    },
                                    "c": {
                                        "title": "c",
                                        "type": "object"
                                    },
                                    "amount": {
                                        "title": "amount",
                                        "type": "integer"
                                    }
                                }
                            }
                        }
                    }
                },
                "responses": {},
                "security": [
                    {
                        "user": [],
                        "scope": []
                    }
                ]
            }
        },
        "/Reverse": {
            "post": {
                "requestBody": {
                    "content": {
                        "application/json": {
                            "schema": {
                                "properties": {
                                    "message": {
                                        "title": "message",
                                        "type": "string"
                                    }
                                }
                            }
                        }
                    }
                },
                "responses": {}
            }
        }
    },
    "components": {
        "securitySchemes": {
            "scope": {
                "type": "apiKey",
                "description": "Customer and project scope. This should contain the '<customer-id>.<project-id>'.",
                "name": "X-DE-SCOPE",
                "in": "header"
            },
            "user": {
                "type": "http",
                "description": "Bearer authentication with an player access token in the Authorization header.",
                "scheme": "bearer",
                "bearerFormat": "Bearer <Access Token>"
            }
        }
    }
}

Any help of guidance would be greatly appreciated.
I'm using "rapidoc": "^9.0.0",

the spec that you provided has few missing sections
try to run your spec on https://editor.swagger.io/ and fix those gap if the issue still persist then provide me with a minimal spec may be with a one or two end-points and I will take a look in case it has anything to do with RapiDoc

hope it fixed your case. closing it now,
in case you have other queries, flee free to open a new issue


This cmdlet usage need to be clarified

If we use "-Role Owner" the user is only added to as Owner of the group, this seems fine with Teams but not with all workloads.
For example, if an user is only set as Owner of a Group and not a member, that user will not see the plan associated with the Office 365 group in Planner (or it is Planner that doesn't work correctly).
When we create an Office 365 Group from Teams, Outlook or SharePoint, we are added as both member and owner, so I guess it is the right way.
Maybe you should make Add-TeamUser to add the user as member and owner, or you should clarify the documentation so we first add the user as member and then as owner.

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

ID: da0c53f2-1c62-14f6-6371-f54bf86b0c24
Version Independent ID: aac162db-a9c0-fbfb-dd40-526e94d3bef8
Content: Add-TeamUser (teams)
Content Source: teams/teams-ps/teams/Add-TeamUser.md
Service: teams-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

@mrik23 Thank you for this feedback
I will get this over to the PowerShell team so we can get this article updated.
I was able to get this into the backlog for the PowerShell team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Hi @mrik23 , thank you for your feedback.
I am adding a line to let readers know that if they use this cmdlet to add an owner, they need to run this cmdlet again to add him as member.

PR:
https://github.com/MicrosoftDocs/office-docs-powershell/pull/2786

Agree with @mrik23. But I found the explanation part added by @adriomws306 is missed now (5/30).
I can see from article history that it was overwritten in Apr 24.
Teams PowerShell Module 1.0 was released in the same day. But cmdlet's add owner movement remained the same as commented by @mrik23.
Sorry but could you confirm this case one more time?

Hi @paarthchothani,
Could you help with this?
It's true that you get different behavior. If you add an owner from the Team Client or Web, the owner is also added as member in the Office 365 group. If you add an owner from Powershell, it's not added as a member in the Office 365 group. Then you can get some issues or different experience as @mrik23 and @moegitree commented.
So I think the article should have a note about this.
Thanks!


Make DefaultEntryPointResolver.Resolve virtual

In the DefaultEntryPointResolver implementation, the Resolve method has a nice algorithm to find an entry point.
What I'd like to do is inherit from DefaultEntryPointResolver and based on the condition viewContext.HttpContext.IsDebuggingEnabled, I'd like to change the result to be a minified entry point (add .min in the name of the javascript file if it exists).
Rigth now, the method is not virtual and I don't want to copy the logic as it may change in future versions. By making it virtual, all I have to do is call the base method and add my logic in the overridden method.
If you feel like it could be useful to other people, it could be another implementation that is provided by RequireJS.Net.

Please share your .min implementation as a gist or fork, could be useful for others.
Thanks


Expose metrics of Caffeine caches

Motivation
Collect and expose metrics related to the Caffeine and Guava caches in brokers.
This will report the sizes, hit/misses rates and load latency.

run java8 tests
run integration tests

run integration tests


Support websockets

Hi Dan,
Just released katon 0.9.0 with WebSocket support. I've done some tests but since it's a new feature, feel to create issues if you find bugs.

Excellent, thank you!


Add Google's embedding models as an Encoder

I'm interested in using Google's embedding models with Semantic Router, but I noticed there isn't a Google Encoder class.
I'd love to help develop a base encoder for Google models, namely those in the textembedding-gecko family.

If this is in-scope, I've drafted a pull request for this.
https://github.com/aurelio-labs/semantic-router/pull/224

thanks @smwitkowski! I've merged your PR #224 and released this as part of semantic-router==0.0.31


Implement the latest changes to room lifecycle spec

Many questions came up whilst implementing the spec; the conversation is ongoing on ably/specification#200. Once these questions are answered, make any required code changes.
Since creating the initial set of room lifecycle tasks, Andy has added further room lifecycle stuff to the spec (e.g. operation priorities, the INITIALIZING state). See what's new and implement.
Some questions that were clarified but didn't result in spec changes:

CHA-RL1h6 means to retry the whole DETACH operation, not just the channel detach

┆Issue is synchronized with this Jira Task by Unito

I’ve opened https://github.com/ably-labs/ably-chat-swift/pull/156 which implements a bunch of spec alignment, and split the remaining work into the following issues:

https://github.com/ably-labs/ably-chat-swift/issues/119
https://github.com/ably-labs/ably-chat-swift/issues/151
https://github.com/ably-labs/ably-chat-swift/issues/152
https://github.com/ably-labs/ably-chat-swift/issues/153
https://github.com/ably-labs/ably-chat-swift/issues/154
https://github.com/ably-labs/ably-chat-swift/issues/155
https://github.com/ably-labs/ably-chat-swift/issues/157
https://github.com/ably-labs/ably-chat-swift/issues/158
https://github.com/ably-labs/ably-chat-swift/issues/159

I’ll close the current issue now.


Fix: Distribution and bail from webpack on error

In the last PR the webpack build exited but didn't
have a fail exit code.
Here we fix the dist and add --bail to npm run dist
so this won't happen again.

Current coverage is 100.00%

Merging #101 into master will not affect coverage as of b258590

@@            master    #101   diff @@
======================================
  Files           16      16
  Stmts          134     134
  Branches        16      16
  Methods          0       0
======================================
  Hit            134     134
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of b258590

Powered by Codecov. Updated on successful CI builds.

LGTM :honey_pot:


Relations are not being returned using Mongo Connector with Prisma Client

Describe the bug
Hi! 👋
In the recent alpha/beta releases, a found a bug/different behavior using Prisma Client. After creating a document with embed/inline relations, the data from this relation is not being returned.
To Reproduce
Steps to reproduce the behavior:

Create three different relations and deploy the changes. Mine are:

type Recipe {
  id: ID! @id
  name: String
  ingredients: [Ingredient!]! @relation(link: INLINE)
  author: Author! @relation(link: INLINE)
  createdAt: DateTime! @createdAt
}

type Author {
  id: ID! @id
  name: String
}

type Ingredient {
  id: ID! @id
  name: String
}

Run a mutation using the Playground. Mine is:

mutation {
  createRecipe(
    data: {
      name: "Prisma with Mongo"
      author: { create: { name: "Prisma Team" } }
      ingredients: { create: [{ name: "Prisma" }, { name: "Mongo" }] }
    }
  ) {
    id
    name

    author {
      id
      name
    }

    ingredients {
      id
      name
    }
  }
}

Notice everything is fine. Now try to do the same using Prisma Client. In my case, i'm using the TypeScript client. That's how it would look like:

import { prisma } from './clientTs';

(async () => {
  const recipe = await prisma.createRecipe({
    name: 'Prisma with Mongo',
    author: {
      create: {
        name: 'Prisma Team',
      },
    },
    ingredients: {
      create: [
        {
          name: 'Prisma',
        },
        {
          name: 'Mongo',
        },
      ],
    },
  });

  console.log(recipe);
})();

The recipe variable contains a object with only id, name and createdAt. Both ingredients and author are not being returned, but they're being added to the collection.

Expected behavior
Both ingredients and author should be returned.
Versions (please complete the following information):

OS: macOS Mojave
prisma CLI: 1.22.0-beta.0
Prisma Server: 1.22.0-beta.0
Prisma Client Lib: 1.22.0-beta.0

Additional context
I'm not sure if that was intentionally changed or it's a bug. 🙃

@iagomelanias thanks for reporting. What you are reporting is 100% correct and expected behavior. The typings of the createRecipe mutation don't change depending on your input right now, as that is not possible to implement in a clean way with TypeScript.
The convention is, that the client always returns only the scalar fields of a type.
We're working on a new API to also allow deep related data to be returned.
However, this is the expected behavior for now. You can also check the return value in the TypeScript typings.

@SilencerWeb can you please post the code where you're invoking the Prisma Client?
Where are you making the query you posted? In the Playground?

@timsuchanek

Can you please post the code where you're invoking the Prisma Client?
Can you explain better what kind of the code?

Where are you making the query you posted? In the Playground?
I tried both in the playground and on the frontend, the result is the same. In the end I just rolled back to old Prisma API (version 1.5.3) and it works perfect right now.


Fix the namespace in the service provider

Replaced the skeleton namespace with the correct one.

Good catch!
Do not look at the code too closely (yet). It's a very rough draft, a braindump really. Nothing has been tested (or even executed) yet.

Thanks for merging it.
I know no worries ;) It's just I'm really excited about this package 👍