Document base url trailing slash

Guzzle's doc mention it follows RFC 3986 but honestly that doesn't help a bit. I even tried to read that RFC but…
It could be made clearer in the docs whether a trailing slash is required, forbidden, or trimmed…
Related to #770 I guess.

Guzzle does exactly what a browser does when resolving a base URL. The RFC shows exactly how different URIs are resolved when combined with a base URI: http://tools.ietf.org/html/rfc3986#section-5.4.1
A trailing slash is not required in a base URI nor is it stripped.
Can you provide some test cases that specifically needs more documentation?

Can you provide some test cases that specifically needs more documentation?

I don't see what you mean by test cases?
Take the Clients documentation, it says:

base_url

Configures a base URL for the client so that requests created using a relative URL are combined with the base_url of the client according to section 5.2 of RFC 3986.

That's not clear because we have to go read the RFC, which is not helpful a bit when you just want to get started quickly and make sure you are writing the URL correctly. We can't expect Guzzle's users to go read HTTP RFCs.
Here is a more helpful version:

base_url

Configures a base URL for the client so that requests created using a relative URL are combined with the base_url of the client according to section 5.2 of RFC 3986 (the base url shouldn't contain a trailing slash).

I chose the word "shouldn't" because the paragraph mentions creating requests using a relative URL, so since the trailing slash isn't stripped if it was added it would end up like http://foo.com//bar.html
If you are OK with this change I can open a PR.


fix: simple changes

should be merged quickly, since these are simple + don't change behavior much + fix a few potential bugs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build 972320854:
0.0%

Covered Lines:
439

Relevant Lines:
444

💛  - Coveralls

@colleenXu For other IDs removed:

remove IDs
BiologicalProcess KEGG
CellularComponent MetaCyc
AnatomicalEntity NCIT
Cell EFO

If the reason to remove MetaCyc, NCIT, EFO is the same as KEGG ("cannot find matching field in the corresponding API"), I would not remove them as well. It's likely the underlying API has an issue to load the corresponding fields, then we should fix the data instead, or find another API.
But if their existence breaks some queries, it's strong enough reason to remove it (or better "comment out") for now.

@newgene I have changed the branch, so this will merge to biolink_v2.1 for testing.
I will add those removed IDs back in, with comments that I didn't find those fields in the corresponding APIs


Merge Snakefiles and implement workaround for config.yaml

Subtasks

[ ] Keep one master Snakefile, but source each test case's rules in a separate Snakefile
[ ] Ensure that each test case has the intended inputs and outputs, despite limitations in config.yaml

Notes

Why workaround config.yaml? Because our workflow does not fit the 7 categories of outputs defined there, and we don't want cross-dependencies among test cases. Would it be better to hardcode the input paths in each rule first? We could generalize that later into a better config.yaml, and we have issue #13 for that later.

@shamlymajeed I made this issue to seperate this need out from test case 2. No need to make a separate branch, since this affects the merging of your existing branch.


Fix Filament 3 implementation

Hi there 👋  Thank you for you efforts with this plugin.
I recently started a fresh installation of Laravel (v11) and Filament (v3) and I was finding that I was receiving an error. I think the main cause of the error was the line config('filament.middleware.base') in routes/web.php which doesn't seem to exist in Filament v3.
By way of a fix I decided to bring the plugin more in line with how it is recommended in the filament docs.
I hope this is helpful and please let me know if I can assist by making any further changes.

Thanks a lot for your PR! I do really appreciate your effort and work.
It seems like there is a test failing. I would love to merge this, but I want to make sure the tests pass first.

@bradyrenting it seems that I had removed the initialisation of a filament package service provider that was needed for registering certain views from our tests. Restored and tests are passing again :)

@robertvansteen thank you so much for your review! I have addressed both of your comments now.

Thanks all!


V3.TxInfo uses V3.TxId consistently.

in particular, GovernanceActionId newtype now wraps around the V3.TxId (used to wrap around the V2.TxId)
ScripContext contains
TxInfo contains
ScriptPurpose contains
ProposalProcedure contains
GovernanceAction contains
GovernanceActionId contains
V3.TxId

This affects some benchmark output, need to update it.


Add Type Template in Quaternion and Euler Angles

Add type template in Quaternion and EulerAngles. So instead of just storing double data, they could store other floating point data too likes float, long double, etc.

Closes by #54


Agregar subtotal (precio venta)

Coverage remained the same at 100.0% when pulling 2926b49e55743dfcf40afd5d6605e2a96ba47af8 on feature/add-subtotal into 248e5a0439c028819bdd80d0c39c0bae54f9a002 on master.


pillar migration to the new API layout

This PR has a few commits that should be reviewed separately. First of all, it updates the pillar Go code to use the new API layout. This is mostly non-controversial rename, aside from one place handlemetrics.go where I had to comment out the following code in order to make this compile
// setDeprecatedMetricAnyValue(item, i.Value)
This needs to be looked at by @zedvijay so we can either reshuffle the API a bit more or simply kill the LTE metrics generation (since it isn't really used at all at this point). The root cause of a problem is the new message deprecatedMetricItem  in api/info/info.proto
Other than that -- everything is pretty ready to be reviewed

@rvs, couple of things. These are only API there is no code operating on it. As controllers vendor these definitions, they would be packaging these in restful API bodies. I strongly feel these should be called APIs in import path rather than SDK.
Second, we need to allow controllers to add decorations if they desire so. This means that we should include original .proto files as well for govendoring support.

@rvs, the code changes in itself is ok, other than 2 comments I mentioned above.

Hey @deitch I updated the Makefile logic as per your comments and I also regularized imports as @nordmark requested.
Now one final question I'd like to resolve is the one brought up by @zedvijay
Personally, I'm on the fence as to whether to keep generated go and python files in a different folder (sdk) or to have them right next to proto files in (api). This, of course, doesn't change anything in the implementation -- it is just naming, but I think to @zedvijay point it is important for us to get this right out of the gate.
I've done a bit of sleuthing and it seems that Kubernetes, Cloud Foundry and Docker are actually mixing proto files and go files in the same folder. I'm not sure whether it was because of some toolchain limitations or something like that, but the result is that the import paths on the go side look uniform between where proto files are and where sdk is.
I'm actually starting to agree with @zedvijay that perhaps it is a better option for us as well.

@zedvijay wrote (and @rvs commented):

These are only API there is no code operating on it. As controllers vendor these definitions, they would be packaging these in restful API bodies. I strongly feel these should be called APIs in import path rather than SDK.
Second, we need to allow controllers to add decorations if they desire so. This means that we should include original .proto files as well for govendoring support.

I am not at all attached to calling it sdk. The real goal with that earlier PR was to get all 3+ parts - the messages definitions in protobuf files; the go generated code; the python generated code; maybe more langs going forward - in sane manageable places. As I recall, our original attempt had the python files polluting the root directory, the go files interleaved with the protobufs, etc. We just needed to add some clear structure, but it didn't at all have to be final.
With respect to "sdk"... I don't care much. We can call it api too.
The primary goal there remains: keep things clean. Importing a directory in any language should give me clean files for that language: node should give me .js files (if we ever decide to do that); go should give me .go files; python should give me .py files; etc. and never the twain shall meet.
So if we want to switch from:
   |
   |- sdk/
   |    |- go/ (go files here)
   |    |- python/ (py files here)
   |
   |- api/ (protobufs here)

to something more like
   |- api/
        |- src/ (protobufs here)
        |- go/ (go files here)
        |- python/ (py files here)

or similar, i.e. all under an api/ dir, that is fine too.
The one thing I think we should not have is something that looks like
   |- api/
        |- foo.proto  file
        |- foo.pb.go  file
        |- foo.pb.py  file
        |- foo.pb.js  file
        |- bar.proto  file
        |- bar.pb.go  file
        |- bar.pb.py  file
        |- bar.pb.js  file

I can see imports in one language trying to parse others, and heaven help us as we have all of these dependencies. Call it safe imports.

Also needs rebase.

Most of the Docker/containerd ones only produce Go, and Go is fine ignoring files it doesn't know about in imports. But once you have more than once language I would split the protos into their own directory.

I like the above suggestion by @deitch
How about we settle on something like:
|- api/
        |- proto/ (protobufs here)
        |- go/ (go files here)
        |- python/ (py files here)

@zedvijay & @nordmark  what do you think?

Sounds good to me

On May 10, 2019, at 8:23 AM, Roman V Shaposhnik<EMAIL_ADDRESS>wrote:
I like the above suggestion by @deitch https://github.com/deitch
How about we settle on something like:
|- api/
|- proto/ (protobufs here)
|- go/ (go files here)
|- python/ (py files here)
@zedvijay https://github.com/zedvijay & @nordmark https://github.com/nordmark what do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/zededa/eve/pull/79#issuecomment-491328163, or mute the thread https://github.com/notifications/unsubscribe-auth/AG4ZUXCYLQXMUOVHHIWFCQDPUWHPVANCNFSM4HLWJZRA.

Hey @nordmark @deitch @zedvijay I've moved this to lf-edge/eve -- the change is already there so please go and check out if it looks acceptable to you.
I also asked folks on the cloud side to start importing from lf-edge/eve/api and see if their builds still work.


Impossible to override HystrixCommand params

Javanica v1.4.21
Method marked with HystrixCommand annotation without explicit properties declaration.
@HystrixCommand(commandKey = "MFO_SERVICE", fallbackMethod = "fallback")
All the properties are stored at the application properties. I'm trying to override HystricCommand properties with stored values. Code looks like this:
@Value("${hystrix.MFO_SERVICE.execution.isolation.thread.timeoutInMilliseconds}")
private String timeoutInMilliseconds;

@Override
public void initCommandProperties(String key) {
   AbstractConfiguration configInstance = ConfigurationManager.getConfigInstance();
   configInstance.setProperty("hystrix.command.MFO_SERVICE.execution.isolation.thread.timeoutInMilliseconds", timeoutInMilliseconds);
}

Let timeoutInMilliseconds be 5000 ms. Then I'm figuring out that hystrixProperties value overrides; by following code:
HystrixCommandMetrics metrics = HystrixCommandMetrics.getInstance(HystrixCommandKey.Factory.asKey(key));
Integer timeout = hystrixCommandMetrics.getProperties().executionTimeoutInMilliseconds().get();

timeout is 5000. But real timeout value during execution is seems to be 1000ms which is default. The same thing with all the params.
What is the correct way to overrride HystricCommand params at runtime?

+1 on this. Whats actually causing this issue?


Can't find ShopifyApp facade class

I'm using the latest master branch version.
How can I do this?
$shop = ShopifyApp::shop();
$requests = $shop->api()->rest('GET', '/admin/api/2019-07/products.json')

I found an  aliase in composer.json, but Osiset\ShopifyApp\Facades\ShopifyApp class seems not exist.
I can't find it anywhere.
Thank you for your help in advance.

Oh, thanks, I think I found out how to do it!

@xyyolab How did you solve this, please? I am in the same situation but I have not a fixed.

Don't use ShopifyApp facade, just do like this!
$products = Auth::user()->api()->rest('GET', '/admin/api/2020-04/products.json')->body;


The information in this page is outdated. Please update the information.

[Enter feedback here]

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

ID: 38f16fae-1b9d-6f21-dbd5-e5fa22118685
Version Independent ID: 4e09a919-7b21-31a8-7369-78b40cea209d
Content: Buy hardware for using MITT - Windows drivers
Content Source: windows-driver-docs-pr/spb/multi-interface-test-tool--mitt--.md
Product: windows-hardware
Technology: spb
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Dupe of #2857


pip-tools: fix build

Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/184205

Things done
Added the build module to deps. The exception thrown by Nix's build.util.project_wheel_metadata when the provided directory contains a malformed setup.py is StopIteration whereas excepted was BuildBackendException cf https://github.com/jazzband/pip-tools/blob/86aa4bd044921e43a686e26b569f838c239d8bca/piptools/scripts/compile.py#L427-L432
It could be a version mismatch but it seems like both Nixpkgs and pip-tools' CI use the same version of build (0.8.0) cf

nix: https://github.com/NixOS/nixpkgs/blob/c60d5f08da0ee25b9ad5c9da5b1f978d51847b98/pkgs/development/python-modules/build/default.nix
pip-tools' CI: https://github.com/jazzband/pip-tools/runs/7527266246?check_suite_focus=true#step:9:15

As a workaround created fix-setup-py-bad-syntax-detection.patch which replaces BuildBackendException with StopIteration.

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.11 Release Notes (or backporting 22.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

2 packages built:

python310Packages.pip-tools
python39Packages.pip-tools

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

2 packages built:

python310Packages.pip-tools
python39Packages.pip-tools


broken link

Please check this documentation
https://release-v0-11.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/
This following command in the documentation fails because httpbin.yaml is not found in this location.  Please repoint this to working location. Thanks.
kubectl apply -f https://raw.githubusercontent.com/openservicemesh/osm/main/docs/example/manifests/samples/httpbin/httpbin.yaml -n httpbin

Hi @srinman - please take a look at the latest version of our documentation:
https://release-v1-2.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/
The download link should be correct in the latest version the docs

@srinman Closing this issue. Feel free to re-open this issue if the link doesn't work!


use git hash instead of mutable tags and make sure we install latest go

use git hash instead of mutable tags and make sure we install latest go

Will we continue to have dependabot updates for them?

yes, and it will also update the version comments


api: add clear_route_cache in jwt_authn Provider

Commit Message:
Add a clear_route_cache field in jwt_authn http filter config.
The jwt verifier may apply changes to the http request and some users
may want to re-resolve route.
Context: https://github.com/envoyproxy/envoy/issues/19910
View also the istio jwt_authn config discussion
Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

The v2 api change is part of ./tools/proto_format/proto_format.sh fix
Not sure why but I see it in other PRs

Hmm,  I did not see any c++ code change to use this new flag.

Hmm, I did not see any c++ code change to use this new flag.

It's only api right now. I'd like to get +1 to confirm this is the right direction.
This extension is more complicated than the istio jwt_authn
CC @yangminzhu

Hmm, I did not see any c++ code change to use this new flag.

Updated the PR title and description

I am fine with adding this flag.  Prefer to have it implemented and unit-tested in the same pr.

/wait
on CI

Not stale

not stale


Blog: Can we standardize the image header size?

It's bigger in this one – http://<IP_ADDRESS>:3000/blog/vonsubblog/posts/hewlett-packard-enterprise--threefold-sign-mou – all the other ones seem to be the same.

The original post put the image by hand (as a link), this is not intended, as images are set via metadata, not like this.
---
title: "The AirBnB of Internet Capacity"
author: Roel
tags: capacity, decentralization, farming
published_at: 2017-9-12
post_image: airbnb-for-internet-capacity.jpg
---

![Logo](../assets/images/airbnb-for-internet-capacity.jpg)


Record how the documentation was built

It would be useful to know what command was used to build the documentation you are viewing.  It would be good to have this info from within the docs themselves.

+1 :+1:


error message from openqa-review

Output will be attached.

Here is the link of openqa-review output:
https://w3.suse.de/~yxu/openqa-review-output

@yxususe The problem is that your argument to '-j' is not specific enough ending up in trying to compare two builds within the released SLE 12 HA group which does not work.
See the log output:
INFO:openqa_review.openqa_review:Job group URL for Functional: {u'SLE 15 / Functional': 'https://openqa.suse.de/group_overview/110', u'Released / SLE 12 SP3 Functional: Server': 'https://openqa.suse.de/group_overview/55', u'Released / SLE 12 SP3 Functional: Desktop': 'https://openqa.suse.de/group_overview/61', u'Released / SLE 12 SP3 Functional: HA': 'https://openqa.suse.de/group_overview/64'}
[…]
DEBUG:openqa_review.openqa_review:Comparing specified build 173.8 against last reviewed 0290

This is not what you want. You wanted -j Functional to match only on the first. Try -j 'SLE.*/ Functional' or -J https://openqa.suse.de/group_overview/110 to be specific.


remove code from onInit which creates duplicates in DD

At the moment this is just a quick and dirty fix. I don't quite get the motivation of the old code.
Personally I would expect to have in DD only valid values that can be selected i.e. in case of an one_to_one relation only id's which don't already have a relation so that no constrain issue happens on save.
Fix #6735

Please make sure the below checklist is followed for Pull Requests.

[ ] Travis tests are green

[ ] Tests are added where necessary

[ ] Documentation is added/updated where necessary

[ ] Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

Wrong approach to solve this


Not getting the nice looking popup

Tried turning on TS logging to see what's up and can't find a reason why the pop up isn't the nice preview I was expecting.
You can see the project and how it's setup here, https://github.com/0xsend/sendapp.
Any ideas on what I was missing?

Looks like it should be working.
Try pressing cmd/ctrl+space to open the suggestion details panel.
Alternatively, there should be a > on the far right if you hover with the mouse.

Aww ty. I had to click the > caret.


Compilation error on GCC 7.4 / Ubuntu 18.04

I have PyTorch installed from a nightly build. I think maybe it now needs a C++14 options in compiler.
I install ctcdecode as pip install git+https://github.com/parlance/ctcdecode
log.txt

export CFLAGS=-std=c++14 didn't help

Compiler call is still gcc -pthread -B /miniconda/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -std=c++14 -fPIC -I/tmp/pip-req-build-8t7lyg7q/third_party/kenlm -I/tmp/pip-req-build-8t7lyg7q/third_party/openfst-1.6.7/src/include -I/tmp/pip-req-build-8t7lyg7q/third_party/ThreadPool -I/tmp/pip-req-build-8t7lyg7q/third_party/boost_1_67_0 -I/tmp/pip-req-build-8t7lyg7q/third_party/utf8 -I/miniconda/lib/python3.7/site-packages/torch/include -I/miniconda/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/miniconda/lib/python3.7/site-packages/torch/include/TH -I/miniconda/lib/python3.7/site-packages/torch/include/THC -I/miniconda/lib/python3.7/site-packages/torch/include -I/miniconda/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/miniconda/lib/python3.7/site-packages/torch/include/TH -I/miniconda/lib/python3.7/site-packages/torch/include/THC -I/miniconda/include/python3.7m -c ctcdecode/src/binding.cpp -o build/temp.linux-x86_64-3.7/ctcdecode/src/binding.o -O3 -DKENLM_MAX_ORDER=6 -std=c++11 -fPIC -DHAVE_ZLIB -DHAVE_BZLIB -DHAVE_XZLIB -DINCLUDE_KENLM -DKENLM_MAX_ORDER=6 -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=ctc_decode -D_GLIBCXX_USE_CXX11_ABI=0, so the latter -std=c++11 overrides my new earlier -std=c++14

Probably https://github.com/parlance/ctcdecode/blob/master/build.py#L44 is problematic and needs to be updated to c++14

Confirmed, this is the problem. sed -i 's/11/14/g' build.py fixes the problem

When I installing ctcdecode, it shows building wheels and then my system hangs..it does not complete installation..anyone please give your suggestion. I am stucked here for a week

Probably https://github.com/parlance/ctcdecode/blob/master/build.py#L44 is problematic and needs to be updated to c++14

How can I find build.py in this repository? I find this link directed me to a 404 page.


fix typo - append time value to correct variable

The value of time for one processor was being appended to the wrong variable.
This is just a fix of a typo in variable name.
Fixes #3

@rafaelmds  Thank you for your contribution!

@aguspesce Done.
Since it was ONE character change I didn't understand why the tests failed. Anyway, ready to go! =]

@rafaelmds... The problem is old.  It was not your fix.  When I activated the Github Actions the style error was already there. So when you do the PR, the style problem was detected


Refs #2709: Isolate/fix the no-fork fault

The specs are pretty shitty, plenty of this code is untested :-(. Good
ol' past-fujin.
Use the same hack to gather the specific recipes from the cli
arguments that client now supports. No tests for this functionality,
does client have some I missed?

@tyler-ball ^^

Rebased, just now.

Latest change broke tons of other specs. :-\

Spec conversion looks super @fujin :+1:

is it worth specifying the behavior for reconfigure in both solo/client_spec to allow/expect set_specific_recipes? what about the behavior of set_specific_recipes, should I spec that? it relies on the cli_arguments provided by mixlib-cli, which can be nil. I think it would be possible to stub (or whatever you kids call it these days), all of that, out.

would be really cool (I think) to have a integration test for 'chef-solo --no-fork' too, since that is originally what brought me here, I don't know if I will be able to make the time for it though.

There are a few tests for application's reconfigure method, so you could add specs for set_specific_recipes there.
I'll have to do some looking back, but, if I remember correctly, I don't think solo is/should be allowed to run forked any more. Does running solo forked make sense?

We definitely use solo in production in no-fork mode to manage all of our containers (70k~). If it doesn't make sense for us to do so, I haven't yet analyzed what that would look like in terms of change to our infrastructure - it may very well be possible.
I think it was originally chosen to work around concurrent runs and locking. I'll double check and see what I can turn up..

Hearing word that we chose no fork mode originally during the chef-10 to chef-11 migration as it was the default during 10.
Are non-forked runs something you're considering removing from solo?

ah I completely misread your messages about forked mode. I agree that solo has little value when used with fork mode, since it is typically oneshot and doesn't run on daemon/interval.
generally speaking, if I was using solo with daemon/interval or something like Runit?, I'd use forked runs? are daemonized Solo runs something you are moving away from recommending??

Are non-forked runs something you're considering removing from solo?

I was mis-remembering some of the work that had been done in removing unforked interval runs of chef-client. Running solo forked is okay. Sorry for the confusion.

Cool, updated specs again @ 72f64e3. Waiting for a build, they all pass locally individually.

oh I should probably spec the internal behavior of set_specific_recipes duhh

Yeah, I dont think fork makes sense for solo. We run chef - client with
--no-fork in production, mostly because of bugs in signal handling with fork
On Jan 2, 2015 2:53 PM, "AJ Christensen"<EMAIL_ADDRESS>wrote:

ah I completely misread your messages about forked mode. I agree that solo
has little value when used with fork mode, since it is typically oneshot
and doesn't run on daemon/interval.
generally speaking, if I was using solo with daemon/interval or something
like Runit?, I'd use forked runs? are daemonized Solo runs something you
are moving away from recommending??
—
Reply to this email directly or view it on GitHub
https://github.com/opscode/chef/pull/2710#issuecomment-68570603.

It looks like three semi-related integration tests are failing in a non-related way
Failures:
  1) chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified directly on the command line
     Failure/Error: IO.read(path_to('tempfile.txt')).should == '1'
     Errno::ENOENT:
       No such file or directory @ rb_sysopen - /tmp/chef_repo20150102-2419-2c9gda/tempfile.txt
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:138:in `read'
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:138:in `block (4 levels) in <top (required)>'
  2) chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified as relative paths directly on the command line
     Failure/Error: IO.read(path_to('tempfile.txt')).should == '1'
     Errno::ENOENT:
       No such file or directory @ rb_sysopen - /tmp/chef_repo20150102-2419-141sr04/tempfile.txt
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:158:in `read'
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:158:in `block (4 levels) in <top (required)>'
  3) chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified directly on the command line AFTER recipes in the run list
     Failure/Error: IO.read(path_to('tempfile.txt')).should == '1'
     Errno::ENOENT:
       No such file or directory @ rb_sysopen - /tmp/chef_repo20150102-2419-1ylludb/tempfile.txt
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:182:in `read'
     # /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:182:in `block (4 levels) in <top (required)>'
Finished in 22 minutes 3 seconds
11270 examples, 3 failures, 417 pending
Failed examples:
rspec /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:116 # chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified directly on the command line
rspec /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:142 # chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified as relative paths directly on the command line
rspec /home/travis/build/opscode/chef/spec/integration/client/client_spec.rb:161 # chef-client when the chef repo has a cookbook with a no-op recipe and a private key should run recipes specified directly on the command line AFTER recipes in the run list

Any ideas?

ping @ranjib @mcquin @tyler-ball can I get a hand moving these integration tests along? any ideas on how to diagnose them?

I was able to inspect the result of shelling out this line, and it's getting WARN: received non-Array like specific_recipes argument.

@mcquin cool, that seems pretty conclusive, heh, I'll attempt to isolate and fix.

Oh fun!  Running just 1 of those tests doesn't give me the failure, but running all 3 does:
chef-client
  when the chef repo has a cookbook with a no-op recipe
    and a private key
      should run recipes specified directly on the command line

@fujin I was able to fix those 3 errors locally by removing the if cli_arguments.respond_to?(:empty) && !cli_arguments.empty? check in application.rb (one of my other comments).

Just tracking what @mcquin identified here:
    and a private key
      should complete with success even with a client key
<Mixlib::ShellOut#32038760: command: 'ruby '/home/aj/dev/chef/spec/integration/client/../../../bin/chef-client' -c "/tmp/chef_repo20150106-7482-s52gbo/config/client.rb" /tmp/chef_repo20150106-7482-s52gbo/arbitrary.rb /tmp/chef_repo20150106
-7482-s52gbo/arbitrary2.rb' process_status: #<Process::Status: pid 9878 exit 0> stdout: '[2015-01-06T13:19:41+13:00] WARN: received non-Array like specific_recipes argument
[2015-01-06T13:19:41+13:00] INFO: Started chef-zero at http://localhost:8889 with repository at /tmp/chef_repo20150106-7482-s52gbo
  One version per cookbook
[2015-01-06T13:19:41+13:00] INFO: Forking chef instance to converge...
[2015-01-06T13:19:41+13:00] INFO: *** Chef 12.0.3 ***
[2015-01-06T13:19:41+13:00] INFO: Chef-client pid: 9895
[2015-01-06T13:19:43+13:00] INFO: HTTP Request Returned 404 Not Found : Object not found: http://localhost:8889/nodes/haxstation.junglist.io
[2015-01-06T13:19:43+13:00] INFO: Run List is []
[2015-01-06T13:19:43+13:00] INFO: Run List expands to []
[2015-01-06T13:19:43+13:00] INFO: Starting Chef Run for haxstation.junglist.io
[2015-01-06T13:19:43+13:00] INFO: Running start handlers
[2015-01-06T13:19:43+13:00] INFO: Start handlers complete.
[2015-01-06T13:19:43+13:00] INFO: HTTP Request Returned 404 Not Found : Object not found: /reports/nodes/haxstation.junglist.io/runs
[2015-01-06T13:19:43+13:00] INFO: Loading cookbooks []
[2015-01-06T13:19:43+13:00] WARN: Node haxstation.junglist.io has an empty run list.
[2015-01-06T13:19:43+13:00] INFO: Chef Run complete in 0.028569048 seconds
[2015-01-06T13:19:43+13:00] INFO: Running report handlers

@tyler-ball trying -- thanks!

irb(main):001:0> [].respond_to?(:map)
=> true
irb(main):002:0> nil.respond_to?(:map)
=> false

?

683df1e

@tyler-ball Would you prefer that I switch out the warn to an App#fatal? or raise ArgumentError?

@fujin I think raising an ArgumentError is the appropriate response.

:metal: modified for ArgumentError. Rebasing the two subsequent commits into the original. Stand by.
If you have fetched/checked out this branch, you will diverge. Please Hard Reset or destroy/re-create.

b399240 -- @tyler-ball @mcquin @ranjib. Thanks again, all!

LGTM , thanks for fixing this dude.

:+1:

LGTM :100:

Thanks dude!

@ranjib have you checked to see if the buggy --fork signal handling is still there in 12.0.x?

ping, anything I can do to help here?

I see +1 from three maintainers: @ranjib, @tyler-ball, and @mcquin. I'll add a fourth :+1: myself and mark it ready for merge.

Speaking of which, is @fujin a maintainer? He should send a PR if he isn't. :)

cherry-picked into master.

95be9a0418b8db7b224092ef3e15282b5ae97eee


WordPress Services returns 500 Errors

Getting 500 Page error while accessing existing WP Deployments Settings. But while creating new WP services it works fine.
Frontend Error:

Console Error:
{"statusCode":401,"code":"FST_JWT_NO_AUTHORIZATION_IN_HEADER","error":"Unauthorized","message":"No Authorization was found in request.headers"}
Recently tried to restart the Coolify from Terminal, then after this happened.

#1166

Hey, this problem could be solved with the followings.
Unfortunately, if anything created after the database backup date (see the docs in the link above) will be lost, due that they are encrypted with a wrong key.
If you need help, contact me.

This could be solved by following this docs.
Note: Anything created between the database backup and now will be lost, due that the encryption key made some values unreadable.
If you need help, you can contact me.


fix: update /mypage borrowing formula

Codecov Report

Merging #159 (2221dbc) into master (eae8b6c) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master    #159   +/-   ##
======================================
  Coverage    3.82%   3.82%
======================================
  Files         523     523
  Lines        9557    9557
  Branches     2731    2731
======================================
  Hits          366     366
  Misses       9191    9191

Impacted Files
Coverage Δ

app/src/pages/mypage/components/TotalValue.tsx
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


MsTest stopped working

I have one unit-test class and two test-methods.
I have defined a wrong signature for the ClassInitialize method:
 //[ClassInitialize]
        //void setup()
        //{

        //}

The problem here is that the tests don't work anymore and you don't get any information back why this is the case! Neither TestExplorer nore the Output console is showing an error!
When I implement the correct signature using TestContext it works as expected.
This should definitely throw an error here and a message pointing to the source of error.
What is this for an hierarchy? UnitTests(2)-->UnitTests(2)-->UnitTest1(2) ???
What's that?

Feel free to inform your colleagues from the VS2017 Pro (latest) Team.

@jayaranigarg Thanks for your quick response.
Yes, I was using :

Updating it to version 1.3.2 showed the expected error message.
It would be nice if one creates a new unit test project, to always get the latest stable nuget packages for test with every update of VS2017.
Now the hierarchy makes sense. My fault, bad naming of Assembly/Class/Namespace which confused me.
Thanks again, sorry for wasting your time!

@Legends : Glad to hear it got fixed for you. We do update the UnitTest Templates to point to latest version of nuget packages as they get released with each VS. Latest VS 15.8 preview points to 1.3.2.


Offsets for motor control

Hi, I noticed that srt-py wasn't sending the right coordinates to the motor, and fixed them in this commit to my fork: https://github.com/imyxh/srt-py/commit/ed6d110a972cf14d4686200b1e008e877a8373b4
I'm curious about the +0.5° that you're doing, and the fact that you send [az,el] relative to the limits. This seems to be incorrect at least for our motor. Is this something that varies across models?

0.5 seems to be to prevent rounding down - a leftover from C.


Thesis paper available?

Hello friend!
First of all that i was surprised to see we studied in the same university - i was in electronics engineering though.
I saw your work from rpcs3 and i really admire all your work in emulation and RE.
Given i am interested in both LLE, and HLE. And i want to start studying LLE first, is there a chance you make the document of your thesis - concerning pctation available?
Thank you very much and congratulations for your achievements.

Whoa I completely missed this issue, sorry!
I remember to talking to someone related on Discord some months ago, was that you?

Whoa I completely missed this issue, sorry!
I remember to talking to someone related on Discord some months ago, was that you?

Hello my friend!
Honored to speak with you!
No, it wasn't me, i have never actually used discord, though i have no problem making a start there!
Which channel should i hop on (if channel is the correct word used in this platform)? Something related to Vita3k?
Like i said before, i really admire your work. Emulation seems like a dark art to me, and i am really interested in it.
I have found documentation for simple 8bit systems (NES), like javidx9 or bisqwit, or the ps1 emulation project in rust with a pdf (although, emulation reaches only the BIOS).
But nothing big demystifying beefier emus. (And very little regarding HLE as well).
I am really surprised you did a PS1 emu as part of your bachelor thesis.
Finding info is the best thing for my way of learning (especially since my coding skills are not great enough to perform such a big task - but creating an emu is one thing in my checklist that i have to do!)
Really honored to speak to you again! Tell me, again how do i find you in discord.
Have a great year!

Hello my friend!
Honored to speak with you!
No, it wasn't me, i have never actually used discord, though i have no problem making a start there!
Which channel should i hop on (if channel is the correct word used in this platform)? Something related to Vita3k?
Like i said before, i really admire your work. Emulation seems like a dark art to me, and i am really interested in it.
I have found documentation for simple 8bit systems (NES), like javidx9 or bisqwit, or the ps1 emulation project in rust with a pdf (although, emulation reaches only the BIOS).
But nothing big demystifying beefier emus. (And very little regarding HLE as well).
I am really surprised you did a PS1 emu as part of your bachelor thesis.
Finding info is the best thing for my way of learning (especially since my coding skills are not great enough to perform such a big task - but creating an emu is one thing in my checklist that i have to do!)
Really honored to speak to you again! Tell me, again how do i find you in discord.
Have a great year!

Hah so it wasn't you, that's surprising.

Which channel should i hop on (if channel is the correct word used in this platform)? Something related to Vita3k?

No need to be on a server, you can just Direct Message people. My user ID is velocity#0042, just go to Friends -> Add Friend.
That said, I also happen to moderate a Discord Server specifically for emulation development.
Link for that here: https://discord.gg/dkmJAes
We also have a community on Reddit: https://www.reddit.com/r/EmuDev though Discord is more immediate and generally has more traffic.

Like i said before, i really admire your work. Emulation seems like a dark art to me, and i am really interested in it.

Thanks! It's such an interesting and deep field.

But nothing big demystifying beefier emus. (And very little regarding HLE as well).

Yeah that tends to be really project-specific. We can talk more in detail via Discord, I don't find long-forms of communication like GitHub very fit for such discussions.

I am really surprised you did a PS1 emu as part of your bachelor thesis.

Yeah I really wanted to. I had been working on emulators for 4-5 years before starting on it (since about I started uni).

Hah so it wasn't you, that's surprising.

Which channel should i hop on (if channel is the correct word used in this platform)? Something related to Vita3k?

No need to be on a server, you can just Direct Message people. My user ID is velocity#0042, just go to Friends -> Add Friend.
That said, I also happen to moderate a Discord Server specifically for emulation development.
Link for that here: https://discord.gg/dkmJAes
We also have a community on Reddit: https://www.reddit.com/r/EmuDev though Discord is more immediate and generally has more traffic.

Like i said before, i really admire your work. Emulation seems like a dark art to me, and i am really interested in it.

Thanks! It's such an interesting and deep field.

But nothing big demystifying beefier emus. (And very little regarding HLE as well).

Yeah that tends to be really project-specific. We can talk more in detail via Discord, I don't find long-forms of communication like GitHub very fit for such discussions.

I am really surprised you did a PS1 emu as part of your bachelor thesis.

Yeah I really wanted to. I had been working on emulators for 4-5 years before starting on it (since about I started uni).


Chain DB implementation

See  https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/ChainDB.md .

@edsko I have pushed a few commits implementing some functions here and there. Feel free to change/squash/rebase/rewrite/ignore them.

Superseded by #617


the folder

f

Hello Mostafa
Now you have the folder
In your next pull request, Add your application files


fix: Fail when duplicate names are generated

Previously, it would silently create buggy code if duplicate models were generated with the same name; see https://github.com/triaxtec/openapi-python-client/pull/335 and https://github.com/triaxtec/openapi-python-client/issues/323.

cc @dbanty @emann @bowenwr @packyg

@dbanty I removed the enum check, since it turns out that IIUC we were already checking for enum name collisions (see openapi_python_client/parser/properties/__init__.py:349).

Awesome, thanks! Will merge this one now.


cannot run the aws-azure-login commands

I'm able to install aws-azure-login but cannot run this command. please see the issues below.
PS C:\Users> aws-azure-login --help aws-azure-login : The term 'aws-azure-login' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + aws-azure-login --help + ~~~~~~~~~~~~~~~ + CategoryInfo          : ObjectNotFound: (aws-azure-login:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

Hi @Raghuveer123, It sounds like an issue with your system or with windows. It works fine on my Mac:

Interesting,don't know where to troubleshoot?

@Raghuveer123 I would try to google something like windows npm global command not found

@kennethaasan Now after uninstalling the node js and after installing the node js LTS version 12.13.0.I'm able to run cli commands.Does this aws-azure-login npm module works on latest version?

Tested now and it works on Node.js version 12 and 13 on Mac.


Xupeng's update

Added Xupeng's profile, SE(2) grasp paper.

👷 Deploy Preview for helpinghandslab processing.
🔨 Explore the source changes: 4027915e25814280cbf338de2640dd5491186325
🔍 Inspect the deploy log: https://app.netlify.com/sites/helpinghandslab/deploys/6227efd6e663800007de1d24


how large is the NSD data downloaded by step 1?

Thanks for your open-source code! How large is the NSD data downloaded by step 1?

Roughly 40G

Roughly 40G

感谢回复，我把issue关了哈。


Fix issue with clicking first col in leaderboards

doesnt take you to the right groups

This issue seems to be resolved, may have been due to an outdated front-end.

Not resolved, but only affects certain tables.
For instance, for the LegalBench group on https://crfm.stanford.edu/helm/lite/v1.5.0/#/leaderboard

In the first tab:

The first column is not clickable (incorrect behavior)
The second column is clickable and goes to the all LegalBench runs for the model (correct behavior)

In the second tab:

The first column is clickable and goes to a single LegalBench run for the model (correct behavior)
The second column is clickable and goes to all the runs for the model, not just LegalBench (incorrect behavior)

Also note that the change needs to be made to helm-summarize, not the React frontend.

Yes that's right I found that right after closing, but opted not to re-open as there is a duplicate issue which I commented on and left open. I should have left a comment here as well. I'll close the other as a duplicate since you added more details here.

Great, thanks!


[CROSSDATA-172] [Connectors] Give a short name

In order to qualify datasource specific UDFs with the datasource name, the short name should used to improve the usability.

+1

+1


Ordering of jobs/workflows is somewhat random

Should at a mimimum be ordered by id (or maybe later allow users to change this...)

Fixed in https://github.com/prominence-eosc/prominence/commit/b8f0a228689128b04786fe34c4e4f4bd66ee22ff


Build OS X

This is not working. Just sending the PR so we can have a log of the issue.
Closes #1

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

Awesome. Thanks for doing this @ocefpaf.

While it would be hard to pick my favorite features from conda-forge. If this is not number 1, it is at least in the top 3. Being able to trivially share build logs and reference issues like this is simply fantastic.

Problem one: the solver chooses to downgrade netcdf4 to 1.2.3 and, by not using 1.2.4 that is pinned against libnetcdf 4.3*, it upgrades libnetcdf  to 4.4 and breaks everything.
Possible solutions: Delete the older build and hope for the best. Over pin by added libnetcdf-4.3* to iris.
===== testing package: iris-1.9.2-np110py27_0 =====
import: 'iris'
Traceback (most recent call last):
  File "/Users/travis/miniconda3/conda-bld/test-tmp_dir/run_test.py", line 25, in <module>
    import iris
  File "/Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/iris/__init__.py", line 112, in <module>
    import iris.fileformats
  File "/Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/iris/fileformats/__init__.py", line 35, in <module>
    from . import netcdf
  File "/Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/iris/fileformats/netcdf.py", line 38, in <module>
    import netCDF4
  File "/Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/netCDF4/__init__.py", line 3, in <module>
    from ._netCDF4 import *
ImportError: dlopen(/Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/netCDF4/_netCDF4.so, 2): Library not loaded: @rpath/./libnetcdf.7.dylib
  Referenced from: /Users/travis/miniconda3/envs/_test/lib/python2.7/site-packages/netCDF4/_netCDF4.so
  Reason: image not found
TESTS FAILED: iris-1.9.2-np110py27_0

Problem two: if we overcome problem one iris still does not work on Python 3. See https://github.com/conda-forge/staged-recipes/pull/280#issuecomment-206377121 and https://github.com/SciTools/conda-recipes-scitools/pull/140

Yeah, we should delete the old netcdfs. They don't pin hdf5 either, which is a huge problem. See this line. This can also be seen by inspecting the packages in conda-forge.

That is the way conda is now and we don't really have an option :unamused:
I would love to see another behavior though. My Linux distro add rules to:

never downgrade a build number unless it is a force install;
and to always maximize the versions of the specified requirements.

The latter means that netcdf4 there would never be downgraded and the former is to ensure that we would never get a broken package as build number bumps are, 99% of the time, fixing packaging issues.
When those rules cannot be satisfied the it would at least ask:
The specified dependencies are forcing packages `x,y,z` to downgrade. Are you sure [y/N]

However, I don't really want to start another conda solver thread. I just want to say that there is a better behavior and we don't need to re-invent the wheel.

Is it possible that we are pinned to netcdf 1.2.3 in some place? If that is the case, maybe we can release a one-off of netcdf 1.2.3 with a higher build number (than already present) and add the right pinnings in it.

Is it possible that we are pinned to netcdf 1.2.3 in some place?

No.

If that is the case, maybe we can release a one-off of netcdf 1.2.3 with a higher build number (than already present) and add the right pinnings in it.

No need. I removed the previous unpinned builds to avoid giving conda the bad choice of downgrading libnetcdf. That should get us building Python 2.7, but then we are still stuck with problem 2 from above.
PS: I hate to delete old builds as that is a kick in the stomach for those, like me, worried about provenance and reproducibility. However, until we fix our tools we (which I know @pelson would prefer) we don't really have a choice but to workaround this issue.

No need. I removed the previous unpinned builds...

Ok.

That should get us building Python 2.7, but then we are still stuck with problem 2 from above.

Just so I am clear, this is not a problem on Linux or Windows?
In any event, this would be better than the current situation. I have a few things that won't build on Windows or some Python versions on Windows due to weird issues.

I hate to delete old builds...

Fair. We can try upping the build number first with proper fixes on the given release in the future.

However, until we fix our tools we (which I know @pelson would prefer)...

Let's wait and see how their meeting goes on Monday. Though there are some new people being added to the mix. So it might take a couple of meetings to get something concrete.

...we don't really have a choice but to workaround this issue.

Trying the above strategy first would at least be one choice we can make. There is no guarantee that it solves it though.

Just so I am clear, this is not a problem on Linux or Windows?

By this you mean problem 1 or problem 2? Either way both are only on OS X, but probably due to different reasons.
@pelson I am puzzled that PY34 NP111 passed! Maybe that help us debug this...

Just catching up, so there may be a number of comments coming. First though:

and to always maximize the versions of the specified requirements.

conda-build is now doing this in master I believe https://github.com/conda/conda-build/pull/907

Yep, was following that. Also, @pelson and @ocefpaf, @msarahan was planning on doing a beta release of conda-build today (assuming all goes well). So, we should be able to get this functionality if we start using the beta. This would be a good time to raise any pressing bugs that you would like fixed. This should help us clear curl, which has been a major bottleneck. It will also fix some issues with shebangs on Mac (I believe).

No need. I removed the previous unpinned builds to avoid giving conda the bad choice of downgrading libnetcdf. That should get us building Python 2.7, but then we are still stuck with problem 2 from above.

Looking good, thanks @ocefpaf:
$ conda execute conda-forge.github.io/scripts/list_deps.py conda-forge --package netcdf --platform osx-64

Fetching package metadata: ..
netcdf-cxx4 4.2.1 0 osx-64         : libnetcdf
netcdf-cxx4 4.2.1 1 osx-64         : libnetcdf 4.3*
netcdf-fortran 4.4.3 2 osx-64      : krb5, libgcc, libnetcdf 4.3*
netcdf4 1.2.4 np110py27_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.10*, python 2.7*, setuptools
netcdf4 1.2.4 np110py34_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.10*, python 3.4*, setuptools
netcdf4 1.2.4 np110py35_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.10*, python 3.5*, setuptools
netcdf4 1.2.4 np111py27_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.11*, python 2.7*, setuptools
netcdf4 1.2.4 np111py34_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.11*, python 3.4*, setuptools
netcdf4 1.2.4 np111py35_1 osx-64   : hdf5 1.8.15*, libnetcdf 4.3*, numpy 1.11*, python 3.5*, setuptools

PS: I hate to delete old builds as that is a kick in the stomach for those, like me, worried about provenance and reproducibility. However, until we fix our tools we (which I know @pelson would prefer) we don't really have a choice but to workaround this issue.

Agreed. Removing builds breaks reproducibility. On the other hand, maintaining the existing builds breaks usability. I've been considering the idea of having 2 conda-forge channels within the anaconda.org conda-forge user - a "main" and a "legacy". We could avoid deleting anything from "legacy", but remove anything which isn't immaculate in "main". There are some details there, but at least (with a bit of effort) users can completely reproduce an environment from a few months ago.

Looks like an iris issue now, rather than a conda/conda-build issue:
copying lib/iris/fileformats/_pyke_rules/fc_rules_cf.krb -> build/lib.macosx-10.5-x86_64-3.4/iris/fileformats/_pyke_rules
/Users/travis/miniconda3/envs/_build/bin/python tools/generate_std_names.py etc/cf-standard-name-table.xml build/lib.macosx-10.5-x86_64-3.4/iris/std_names.py
writing [iris.fileformats._pyke_rules.compiled_krb]/fc_rules_cf_fc.py
writing [iris.fileformats._pyke_rules.compiled_krb]/compiled_pyke_files.py
Traceback (most recent call last):
  File "setup.py", line 229, in <module>
    'clean_source': CleanSource},
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/setuptools-20.7.0-py3.4.egg/setuptools/command/install.py", line 61, in run
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/command/install.py", line 539, in run
    self.run_command('build')
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/command/build.py", line 126, in run
    self.run_command(cmd_name)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "setup.py", line 180, in run
    MakePykeRules._pyke_rule_compile()
  File "setup.py", line 134, in _pyke_rule_compile
    knowledge_engine.engine(iris.fileformats._pyke_rules)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/knowledge_engine.py", line 110, in __init__
    target_package.load(self, **kws)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/target_pkg.py", line 366, in load
    self.do_by_ext('load', target_filename, engine, load_flags)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/target_pkg.py", line 265, in do_by_ext
    return getattr(self, "%s_%s" % (prefix, ext))(filename, *args)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/target_pkg.py", line 374, in load_py
    self.load_module(module_path, target_filename, engine)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/target_pkg.py", line 407, in load_module
    module = import_(module_path)
  File "/Users/travis/miniconda3/envs/_build/lib/python3.4/site-packages/pyke/target_pkg.py", line 463, in import_
    mod = __import__(modulename)
ImportError: No module named 'iris.fileformats._pyke_rules.compiled_krb'
Command failed: /bin/bash -x -e /Users/travis/build/conda-forge/iris-feedstock/recipe/build.sh

Yep. All I could do was to get you to Problem 2 :wink:
https://github.com/conda-forge/iris-feedstock/pull/2#issuecomment-217189398

Looks like an iris issue now, rather than a conda/conda-build issue...

I would agree, but...

I am puzzled that PY34 NP111 passed!

Feels funny doesn't it? :/

Lol. Thank for reminding me of my poor memory @ocefpaf 👍
I'll see if I can reproduce locally.

Lol. Thank for reminding me of my poor memory @ocefpaf 👍

BTW that is the last piece on the ioos stack holding us to Python 2.7. So no pressure :wink:

BTW that is the last piece on the ioos stack holding us to Python 2.7.

You're lucky you only have one piece.

You're lucky you only have one piece.

Lucky? No! Many, many PRs to many places :smile:

"Luck Is What Happens When Preparation Meets Opportunity" - Seneca
😉

P.S. I'm able to reproduce the problem locally.

🎉  - bravo @ocefpaf. 😄

Lucky? No! Many, many PRs sent to many places :smile:

"Luck Is What Happens When Preparation Meets Opportunity" - Seneca

The issue is not all of this software is stuff I maintain. Some of it (sadly) is not even on GitHub so it is pretty rough. We use a lot of breaking edge stuff so Python 3 is not a priority for the developers/alogrithm writers, publishing is. Even if I do help somebody convert something over to Python 3, it seems to be at my expense. So, I think this is more a matter of walking in my shoes ( 👞 ) for a month to understand what I am saying here.

Thanks for for investigating and creating the patch @pelson! I will be running my very first 100% Python 3.5 production env tomorrow! :tada:

Interestingly, I got caught by this or something similar, building py36 packages from miniconda2 install.
Switching to miniconda3 seemed to resolve my issue ;)


[review] Add "array" capability to Components

Numerical parameters as well as ParameterBlocks can have an "ArrayLength" attribute that instantiate as many identical parameters or parameter blocks.
This is now also possible for Component instances (not types).
The Semantic of this feature is very unclear, even now... use with caution.

This pull request is now managed with CodeReviewHub. Refresh.

@tcahuzax @krocard please review.

:+1:

:-1:


Does it work with Floating labels?

Does it work with Floating labels?

Yes, it does. You just have to supply a suitable adapter.
ViewDataAdapter<FloatLabeledEditText, String> fletStringAdapter = new ViewDataAdapter<>() {

    @Override
    public String getData(FloatLabeledEditText flet) throws ConversionException {
        return flet.getEditText().getText().toString();
    }
};

mValidator.registerAdapter(FloatLabeledEditText.class, fletStringAdapter);

Depending upon the rule, you have to supply adapters that return the appropriate data type.

I had to modify your code, leave it or something can be better?
ViewDataAdapter<TextInputLayout , String> fletStringAdapter = new ViewDataAdapter() {
@Override
public Object getData(View view) throws ConversionException {
TextInputLayout textInputLayout= (TextInputLayout)view;
return textInputLayout.getEditText().getText().toString();
}
};

ok, works mycode:
validator.registerAdapter(TextInputLayout.class,
            new ViewDataAdapter<TextInputLayout, String>() {
                @Override
                public String getData(TextInputLayout flet) throws ConversionException {
                    return flet.getEditText().getText().toString();
                }
            }
    );

OK great!

Hi,
I am new to Android. Could you provide more information about it? I would like to use your library to validate my inputs and use Textinpulayout. I am not sure how to set error under the input. Now I am validating next to the input which I do not like it.
  validator.registerAdapter(TextInputLayout.class,                 new ViewDataAdapter<TextInputLayout, String>() {                     @Override                     public String getData(TextInputLayout flet) throws ConversionException {                         return flet.getEditText().getText().toString();                     }                 }         );
Also I created text watcher
` private TextWatcher registerTextWatcher() {
TextWatcher validationTextWatcher = new TextWatcher() {
@Override
public void beforeTextChanged(CharSequence charSequence, int i, int i1, int i2) {
}
        @Override
        public void onTextChanged(CharSequence charSequence, int i, int i1, int i2) {
        }

        @Override
        public void afterTextChanged(Editable editable) {
            validator.validate();
        }

    };
    return validationTextWatcher;
}`

Then I use for my inputs
inputEmail.addTextChangedListener(validationTextWatcher); inputPassword.addTextChangedListener(validationTextWatcher);
But it is not working.
Thanks for any advices


Do not put version in release filename

I would like to be able to download directly the latest version of syft without making two requests. Is it possible on github if the path is like https://github.com/${ORG}/${REPO}/release/latest/download/${FILENAME}
For example here, I am looking at the version 0.100.0, I am a Linux user with x86_64 and I use the tgz so I would like the filename to be syft_linux_amd64.tar.gz instead of syft_0.100.0_linux_amd64.tar.gz.
Sent from my FP3 using FastHub-Libre

Hi, thanks for the suggestion! I will run it by the team to see if we can add a file without a version number to the list of assets. In the meantime, here are a couple of things that might help:

Our install.sh script for syft and grype has some mechanisms to find the latest version
I found a generalized tool to solve this problem: https://github.com/dvershinin/lastversion
And a long and varied discussion of a bunch of different ways to accomplish this: https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8

Hi there, after discussing this we are going to go ahead and close this issue since there are some suitable workarounds and generating a release artifact without a version number attached has some potential bad side effects if you are unsure of what's inside the release. Please let us know if you need any more help with the suggested workarounds. Thank you!

No problem it was more of a suggestion than anything else and I used a workaround, thanks


Web: expanded find widget needs more height (Firefox)

Steps to Reproduce:

use Firefox
expand the find widget to show replace

I would even say that in Chrome the border around the boxes is not the same to the bottom as it is to the top:

Thanks and good catch. FF has its own predefined css for textarea (margin top/bottom: 1px). Currently I disable it only for Find Widget as I didn't see any other component (Search, Git) suffers from it. If I do see that happening, then I'll force the margin for basic input component.


[Proposal] Add RGB-D Render Mode to MuJoCo Environments

Proposal
My proposal is to add a new render_mode to MuJoCo environments for when RGB and Depth images are required as observations, e.g. to create point clouds.
(related issue: #727)
Motivation
Currently one can achieve this by calling MujocoEnv.mujoco_renderer.render twice with both render_mode=rgb_array and render_mode=depth_array respectively. However, internally rgb and depth are always rendered and only one is returned based on the render_mode. Therefore, offering to return both rgb and depth in one step saves the effort of rendering both images twice.
Pitch
'rgbd_array' should be added as valid render_mode that returns both the rgb and the depth image either separately or as a 4 channel image (which entails conversion from uint8 to float32 and back for rgb).
Alternatives
No response
Additional context
I've already implemented a solution in my fork that returns both images separately.
Here's a comparison of execution times produced by the following script:
import timeit
import numpy as np

setup_render_twice = """
import gymnasium as gym
env = gym.make('Pusher-v5', render_mode='rgb_array')
env.reset()
"""

render_twice = """
rgb = env.get_wrapper_attr('mujoco_renderer').render('rgb_array')
depth = env.get_wrapper_attr('mujoco_renderer').render('depth_array')
"""

setup_render_once = """
import gymnasium as gym
env = gym.make('Pusher-v5', render_mode='rgbd_array')
env.reset()
"""

render_once = """
rgb, depth = env.render()
"""

times_twice = timeit.repeat(setup=setup_render_twice, stmt=render_twice, number=10, repeat=10000)
print(f"Render twice:\n\tmean: {np.mean(times_twice):.4f}+-{np.std(times_twice):.4f}\n\tmin: {np.min(times_twice):.4f}\n\tmax: {np.max(times_twice):.4f}\n")

times_once = timeit.repeat(setup=setup_render_once, stmt=render_once, number=10, repeat=10000)
print(f"RGB-D:\n\tmean: {np.mean(times_once):.4f}+-{np.std(times_once):.4f}\n\tmin: {np.min(times_once):.4f}\n\tmax: {np.max(times_once):.4f}\n")

Results:
Render twice:
        mean: 0.0301+-0.0018
        min: 0.0283
        max: 0.0633

RGB-D:
        mean: 0.0136+-0.0010
        min: 0.0127
        max: 0.0246

Checklist

[X] I have checked that there is no similar issue in the repo

@DavidPL1 Thanks for the proposal. @Kallinteris-Andreas will know best, but I think this sounds like a reasonable idea.
Having a quick look at your implementation, currently you return a tuple of the rgb and the depth.
However as they have the same shape, it would be easier to concatenate the results as rgbd of (480, 480, 4)

However as they have the same shape, it would be easier to concatenate the results as rgbd of (480, 480, 4)

Correct, however, the rgb image is of type np.uint8 while the depth image is of type np.float32. So this more of a design choice whether to have both images usable the same way as they are returned from the individual render modes or nicely fit them in a single array but require users to convert rgb back to uint8 from float32.

I am not familiar with how rgbd inputs are handled in CNNs, we should choose the output format for For whatever input is convenient for CNNs.

the rgb image is of type np.uint8 while the depth image is of type np.float32.

Ahh that makes sense, lets make a tuple like your implementation
@DavidPL1 could you make a PR with your branch?


Check response code of geocoding provider

Fixes #28.
We check the response code of the provider. If the response code is not equal to 2XX, we return a 400, with a generic exception message. We log the request as Error and ask the user to contact the support.
WDYT?

Thanks looks good!

Thanks for the reivew :)

You mean like this?

Ups, I meant completely without this sentence. Because we normally see those errors, no need to contact us.

Ups, I meant completely without this sentence. Because we normally see those errors, no need to contact us.

Ah, wasn't sure. Should be fine now, will merge this PR.


Add an Automatic-Module-Name in the jar(s) MANIFEST

Hi!
I made the same request in the jMolecules project but I also want to use moduliths library.. I would like to use Moduliths in an Intellij Java project which uses Java 9 modules. The problem is that if a library doesn't declare an Automatic-Module-Name in the Jar MANIFEST the library falls into the unnamed module, and as we speak, Intellij does not support unnamed module.
Thanks again for this(ese) library!

That should be in place now.


fix: add paths to module for require to work with node_modules

This was otherwise preventing the usage of require('my-npm-package') in Eleventy JavaScript render templates.
A working example: https://github.com/RobinCsl/11ty-webc-img-demo/tree/rcsl/use-require/03-final
I didn't test what this might break or not as I'm not familiar with the codebase and cannot appreciate the consequences of these changes, other than it helps with my specific use-case!
Hope that's helpful!

Yay! Thanks @RobinCsl!


Update Google Form implementation

Convert the current Google Form implementation from an iframe back to a form element that submits directly to the Google Form's endpoint.
Resources: https://github.com/jsdevel/google-form

This unfortunately isn't viable anymore due to CORS, but since we already have a Vercel server, can we setup a lambda function to forward the form?
cc @EthanThatOneKid

Status on this issue: We are waiting on admin to gain access to a Mailchimp account in order to properly implement the HTML form. Once the account is back in our possession, we can use the account to create an automatic email alert service for admins to receive emails from responses on the contact page.

Since the /connect page has been removed in v2.0, we no longer need to maintain the Google form.


Remove old version support

Should update install_requires then:
https://github.com/Teemu/pytest-sugar/blob/464a842d2ed3654f7338595f91b93e2111ba531a/setup.py#L45

@auvipy Fixed it in another PR :)


fix: Content type conformance check for cases when Open API 3.0 schemas contain "default" response definitions

Fixes #641

Codecov Report

Merging #642 into master will decrease coverage by 0.11%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master     #642      +/-   ##
==========================================
- Coverage   99.49%   99.37%   -0.12%
==========================================
  Files          57       57
  Lines        3545     3515      -30
  Branches      611      613       +2
==========================================
- Hits         3527     3493      -34
- Misses          6        8       +2
- Partials       12       14       +2

Flag
Coverage Δ

#unittests
99.37% <71.42%> (-0.12%)
:arrow_down:

Impacted Files
Coverage Δ

src/schemathesis/specs/openapi/schemas.py
99.23% <71.42%> (-0.77%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
97.53% <0.00%> (-2.47%)
:arrow_down:

src/schemathesis/specs/graphql/schemas.py
96.55% <0.00%> (-0.23%)
:arrow_down:

src/schemathesis/hooks.py
99.08% <0.00%> (-0.03%)
:arrow_down:

src/schemathesis/runner/impl/core.py
98.59% <0.00%> (-0.02%)
:arrow_down:

src/schemathesis/models.py
99.38% <0.00%> (-0.02%)
:arrow_down:

src/schemathesis/lazy.py
100.00% <0.00%> (ø)

src/schemathesis/stateful.py
100.00% <0.00%> (ø)

src/schemathesis/cli/context.py
100.00% <0.00%> (ø)

src/schemathesis/cli/cassettes.py
100.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Blazor WASM AAD Auth Instructions require updates to match Azure Portal changes.

This page defines steps which no longer align to the layout and options provided in the Azure portal interface. For instance options are presented which are not defined in the instructions, and some instructions are not do-able as the option is not there. Please update to match current Azure portal configuration.

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

ID: 3039ff79-ee86-20b1-0082-d3899a84c823
Version Independent ID: af4a3a75-ae52-5f6d-2120-737bc2fefb07
Content: Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @jhurdlow ... can you say exactly what was different because we've had reports like this before and it turned out that the portal hadn't been updated ... it was just a missed instruction step on the reader's part. It wouldn't surprise me, of course, if the portal did change ... it happens quite frequently. If by ...

For instance options are presented which are not defined in the instructions

... you're just saying that not ALL of the options are called out. That's normal. We won't do that here because this isn't meant to be a full tour of everything you can do in the portal for this app config. It's just meant to focus on the critical config to make it work.

An alternative to letting me know what you think requires updating is to wait a short bit longer for me to get to ...
https://github.com/dotnet/AspNetCore.Docs/issues/19503
... when I'll be looking at the portal for the RC1/Identity v2.0 updates. In that case, we'll call this a duplicate and close it without further concern.

@jhurdlow ... I'm going to close because I'd need more specific information on what's different. Like I said, we've had these sorts of issues opened in the past where there was a missed step when following the guidance. I'll be taking a look at all of these topics and the portal when I get to #19503 shortly for the .NET 5 RC1 updates (preview docs). I'll confirm or update accordingly when I get to that issue.


Made error catching across heatmap analyses consistent

Also fixed bug where cairo graphical device was not properly
instantiated before plotting the error.

Stranded pull request. Merged into https://github.com/thehyve/Rmodules/commit/819f62f4613561a49a353107e69d91fa448da9de
Closing now.


[WIP] Refactor to make more hypotheses easier to implement

Work in progress, not all of the below is implemented and/or working yet. Recommend squash merge when we demonstrate the new architecture works.

re-architect hypotheses as classes that inherit from Hypo
move hypos into retro dir (no need for subdir)
create hypo.py/Hypo base class for hypotheses
create cascade_hypo.py/CascadeHypo to encompass all cascades we've implemented, remove redundant code
create muon_hypo.py/MuonHypo to encompass all muon hypos we've implemented, remove redundant code
split pexp_5d.py into pexp.py/get_pexp_func and llh.py/get_llh_func; move up into retro dir
utils/misc.py: add function for extracting function arg names from either pure-Python or numba jit-compiled function

superseded by PR #62


Compute MRIQC's metrics

A prequel is poldracklab/mriqc#440

Has there been any progress on this, such that we can have fmriprep compute MRIQC's metrics or have MRIQC use the output of fmriprep when computing its metrics? It seems like MRIQC does a lot of the pre-processing steps that fmriprep does and so having them do them independently is wasteful. I couldn't find anything on the current documentation, but I might have missed it.

There has not. We're happy to help someone who wants to take this on, but I'm not sure that we're likely to get to it ourselves in the short term.

Okay, we might try and look into it. Is there anything you can point me to in order to get started? Otherwise, my plan would be to just look through the steps of MRIQC and try to match them up to outputs / intermediates of fmriprep -- does that make sense?

Hi, yes. Sorry about the delay. I think the easiest places to look will be the main outputnode of the BOLD workflow:
https://github.com/nipreps/fmriprep/blob/c707938e1462e77b1c3a1216a855ceb0aba70845/fmriprep/workflows/bold/base.py#L250-L257
These should mostly be hooked up to derivatives:
https://github.com/nipreps/fmriprep/blob/c707938e1462e77b1c3a1216a855ceb0aba70845/fmriprep/workflows/bold/base.py#L279-L312
So if you can find the derivative you want to generate summary statistics for, then you can hook it up from the outputnode. We'll probably want to create a new fmriprep/workflows/quality_control.py and init_func_qc_wf() function that takes inputs and generates output metrics.
Hopefully that can get you started, and then feel free to get in touch with any questions at all.


cannot set graphql_name with strawberry.field on pydantic.type

cannot set graphql_name with strawberry.field(name='someName') on pydantic.type
Describe the Bug
It's better explained as a test for tests/experimental/pydantic/test_basic.py
def test_alias_fields():
    class User(pydantic.BaseModel):
        age: int

    @strawberry.experimental.pydantic.type(User)
    class UserType:
        age: strawberry.auto = strawberry.field(name="ageAlias")

    definition: TypeDefinition = UserType._type_definition
    assert definition.name == "UserType"

    field1 = definition.fields[0]

    assert field1.python_name == "age"
    assert field1.graphql_name == "ageAlias"  # <-- field1.graphql_name is None
    assert field1.type is int

I understand that I can use pydantic.Field(alias="ageAlias") on model, but the reason I use pydantic with strawberry is because I want to separate models and graphql types.


Intent menu in navbar

Pull Request Summary

Quickly moved intent menu into navbar.
Change types

[x] Non-breaking change
[x] Front end change

Testing

[ ] I have added testing to this PR

How to manually test this PR (QA instructions)
Check out analysis page!
Questions

Not sure if we want to add the filter by star and flag here or leave that part to intent menu

CR is good. A problem with QA:

I can't use the tab key to reach the hamburger button. This is true for the Return to Main Page as well. Can anyone confirm?
Can't confirm right now as the tab key doesn't reach it, but if you do eventually fix that, we also need to make sure that you cannot access the the hamburger button with the tab key while the sidebar is open. So you may have to do a conditional render for the button (i.e. only renders when state.showIntentMenu is false).

The reason why is that the hamburger button is designed to always open the sidebar, and the X button always closes it. This is fine for clicking since an open sidebar covers the hamburger, but may not necessarily be true for tabbing.

I could probably fix the tabbing for the svgs since I did it for the stars and flags!

I'll text you on the group chat to ask about how you did the tabbing

 Found a bug while resizing my window.
Also +1 on the aside comment I made above

Wait do you mean aside instead of button? It's not a div anymore for the intent menu

Actually I just noticed theres an issue for when you open the sidebar - it shifts the logo over. See more on discord


Split third party pull into Quartz child jobs

Splits the third party Smartling pull into separate child jobs that can be processed in parallel across nodes in a worker cluster.

In general looks good to me, but this PR changed more than a thousand rows. I would suggest to split big changes in small PRs next time.

Agree in general, problem with this PR is that it's a large PR with a single new piece of functionality so it's difficult to separate without causing test failures or having to ignore tests until all functional updates are merged.


Add lighter red shades for error messages

The current one has low contrast in the dark theme and is somewhat hard to look at.
The new red color represents the "500" shaded in the palette. Other colors from the generic red palette have been adjusted in the linked palette.

Old
New

IMO this is way too "aggressive" for the eyes in dark mode and I would prefer the current desaturated variant.

Does this apply to both shades or only the button background? Note that the icon one is darker.

Two classes (there are many redundant ones with the same color but this is a different topic) but only one tone: #c93c37. (I tried using different ones in a previous state but the current one only uses one color).
It would be great if there could be additional opinions as it is hard to move on in such UI discussions if there's always a 1:1.
(just as a side note: I have found the red color being way too dark since the theme existed, this is not a recent discovery. I have also compared the WP color with other common red colors in dark themes (GH, GL, Hetzner) and none is nowhere close in terms of darkness/saturation.
Not saying that my proposed choice is a good alternative but I really think the current one is sub-optimal.)

https://github.com/woodpecker-ci/woodpecker/pull/4584#issuecomment-2562003413 - guess I'll have to close this PR?

I dont think so, Im fine with a color change.

Im also fine with the not-desaturated color, just dont had time to come back to this PR.

The desaturated looks now more pink in dark mode. Then I would prefer your initial one.

The desaturated looks now more pink in dark mode. Then I would prefer your initial one.

Still trying. Iterating in the PR, not locally.

Ok, sorry. Hard to see what is "developing commit" and whats not. Is there a reason not to use a local compose stack to test your changes? Just wondering as for me the feedback loop would be way too long otherwise.

Ok, sorry. Hard to see what is "developing commit" and whats not. Is there a reason not to use a local compose stack to test your changes? Just wondering as for me the feedback loop would be way too long otherwise.

When you iterate on 4+ PRs, letting the CI build everything and then just kill the pod is the simplest way imo (my dev instance is on k8s). I sometimes build local images but only until I am convinced this is worth a PR and the CI build actually working (and it is not a UI PR).
I think building UI PR images publicly is important as others can easily apply the images this way and verify changes in detail.

I just tested colors.red[500] and IMO it is pretty close to the custom color you selected. I Would just use this one for the dark mode and drop the desaturation.

I just tested colors.red[500] and IMO it is pretty close to the custom color you selected. I Would just use this one for the dark mode and drop the desaturation.

Hm, that's how I started out initially but wasn't convinced...but ok, I'll try again.

Yeah, it is not exactly the same color of course, but Im wondering if the minimal difference is really important. Btw we have also introduced theming by custom css to adjust such things to personal preferences without code changes.

OK, this one works for me. Updated the screenshot in OP.

Would wp-state-error-200 instead of wp-state-error-100 in dark mode work for you as well?

Can we also remove 400: 'var(--wp-state-error-400)' and 500: 'var(--wp-state-error-500)', for wp-state-error again?

The idea that was to have a larger palette defined for potential future uses that allows colors below and above the current active spectrum. (Yes, I know that the "below" part is actually missing). AFAIK there are also not all green primary colors in use which are defined?
But to move on and to avoid further discussions, I'll remove them.

Would wp-state-error-200 instead of wp-state-error-100 in dark mode work for you as well?

OK.

@xoxys Your turn again.

@pat-s there are open suggestions

There are still a lot of wp-state-error occurrences.


Secondary tuple from secondary inputs are never received.

I am trying to send tuples from 2 bolts to 1 bolt.
If in the topology, I map them 1 to 1, everything gets processed as it should.
but when in the topology I do:
NewsAlertFactoryBolt1 = NewsAlertFactoryBolt.spec(inputs={NewsAnalyticsPayloadBolt1: Grouping.SHUFFLE, NewsEnrichementBolt1: Grouping.SHUFFLE}, par=2)
I get the tuples from NewsAnalyticsPayloadBolt1 but I never receive the one from NewsEnrichementBolt1

Found, the issue. Apologise.


Visualise whitespace

Basically implement the visualise whitespace feature that is common to most IDEs. It renders spaces as a grey centre dot and tabs as a grey right arrow. In VSCode this is called "render whitespace" and has the following settings:

None
Boundary: Render whitespace except single spaces between non-whitespace characters.
Selection (the default): Render all whitespace in the selection.
Trailing: Render only trailing whitespace characters.
All: Render all whitespace characters.

Seems like a good set of options to me. I would also add this for completeness:

Leading: Render only leading whitespace characters.

Fixed in #1284


Added sacrebleu version

Without this change Bart-large was failing in https://github.com/microsoft/onnxruntime-training-examples with exception : "User program failed with AttributeError: module 'sacrebleu' has no attribute 'DEFAULT_TOKENIZER’ "

Do you mind updating individual model readme files such as bert.md, bard.md, etc to use huggingface/script instead of deprecated huggingface/azureml in the same PR?

Do you mind updating individual model readme files such as bert.md, bard.md, etc to use huggingface/script instead of deprecated huggingface/azureml in the same PR?

Sure. I have updated the model readme files

Do you mind updating individual model readme files such as bert.md, bard.md, etc to use huggingface/script instead of deprecated huggingface/azureml in the same PR?

Sure. I have updated the model readme files

Looks good! Thank you!


Addition of a new LavaLink client

Thanks for the quick response. And I'm happy to contribute to the LavaLink
community! Have a great weekend.
On Fri, 12 Jun 2020, 23:36 Frederik Ar. Mikkelsen<EMAIL_ADDRESS>wrote:

@Frederikam approved this pull request.
Client looks good. I moved the mention up and linked Discord.js.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Frederikam/Lavalink/pull/311#pullrequestreview-429940792,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVW76WMPFB67ENILDRLAOTRWJVAXANCNFSM4N4PAOAQ
.


Feature: Discover unused network policies

Is your feature request related to a problem? Please describe.
Network policies can be created for a specific use case and be left over. Go through all existing network policies and verify if they are applied to any Pods or Namespaces
Describe the solution you'd like
Kor networkpolicies
Will show all unused network policies

Hey @yonahd, I'll be happy to have a look into this. May I have this?

Hey @yonahd, I'll be happy to have a look into this. May I have this?

Assigned. Thanks!


Extract raw text including whitespace from tag

What happened?
With MarkDoc and MarkDoc NextJs plugins, it seems impossible to extract the raw text of the contents of a tag while preserving indentation as the location character is always undefined. Additionally, it appears that the location of each paragraph tag is set to the same value, which is based on the lines of the parent tag.
It seems possible to extract each line of content in a tag by iterating through each paragraph node in the transform function. However, the content already has the whitespace trimmed, and the location does not contain the necessary information to compute the indentation level.
To reproduce
...
{% foo %}
Line one
    Line two
        Line three
{% /foo %}
...

Version
0.2.2
Additional context
There may be a better way for me to extract the raw content including indentation rather than iterating through all of the paragraph nodes that may be the solution to what I need. If so I would be more than happy to go with that approach.

You are correct—the parser does not preserve indentation and it does not capture the character offset for text nodes. The lack of character offsets is a limitation of the underlying Markdown parser that we use to tokenize the content, and we may address this in the future. The indentation isn't preserved because paragraph indentation isn't syntactically relevant in Markdown.
We have considered the possibility of capturing the raw source text nested inside of a tag and exposing this as an attribute on the tag itself. You can actually do this yourself today by getting the line number of the opening and closing tags and slicing those lines out of the original source document. This doesn't prevent Markdoc from parsing the interior content as Markdoc, however.
We generally don't think it's a good idea to treat the content inside of Markdoc tags as literal text or use your own custom syntax and non-Markdown formatting inside of Markdoc tags. If you need to treat the content as literal text, you are probably better off using a fenced code block.
Would you mind describing your use case?

Yes I think the fenced code block approach would make the most sense! I was implementing a diagram tag that would render a Mermaid diagram. However, I ran into problems with some mermaid diagrams being indentation sensitive.
Thanks for the guidance!


docs: fix code snippets in README.md

I tried following the example in README.md and ran into two small issues.

The pub command is typically accessed through flutter instead of directly. On fresh Flutter installs, pub add ... returns bash: pub: command not found
GoogleMapsNavigationManager doesn't exist.  I believe this is the old name before the class was renamed / reorganized to GoogleMapsNavigator.

I am currently working on improving test stability; landing this PR is just waiting this task to finish first.


Changing the digest_path

Hi,
as per https://github.com/jekyll/jekyll-assets/blob/6eeb51fa35b2d7d8cf8335cd203e2d66848ea5fb/lib/jekyll/assets/liquid/tag/proxied_asset.rb#L105-L107, the naming convention for an asset when digest: true is ./path/to/filename-DIGEST.ext.
I'd like to be able to change this, for example: ./DIGEST/path/to/filename.ext.
I didn't find anything in jekyll-assets to do so, but I'd like to know if you'd think of a workaround towards this goal.
Cheers!

At this time we don't have that capability, we use Sprockets itself to generate the Digest path and in-order to do what you requested we would have to take over their pathing (we do in a few places but only to replicate what the upper level assets do.)
I'm not against this idea, if it's easy (or if somebody else wants to take a stab.) However, I think it should wait until we get Sprockets 4.0 implemented in the next month because that's already a lot of work to get done (Sprockets 4.0 has a ton of changes we've to account for.)

👍  I can give it a try and/or wait for the next month, whichever comes first. Let's see how it goes.
Meanwhile: glad you like the idea.

Sorry for never updating you, we've supported a prefix for quite sometime, you can now customize where your assets are placed.  Even if we add a CDN and so-forth.


Pierre/doc posterior

Fixes #342

Codecov Report

Merging #354 into master will decrease coverage by <.01%.
The diff coverage is 63.63%.

@@            Coverage Diff             @@
##           master     #354      +/-   ##
==========================================
- Coverage   88.84%   88.83%   -0.01%
==========================================
  Files          32       32
  Lines        3003     3001       -2
==========================================
- Hits         2668     2666       -2
  Misses        335      335

Impacted Files
Coverage Δ

scvi/inference/posterior.py
92.61% <63.63%> (-0.03%)
:arrow_down:

scvi/inference/autotune.py
69.11% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks Pierre! While you're at it it would be nice to have parameter annotations using python's typingmodule.  Do you have time to add that before we merge?
@jeff-regier @romain-lopez Is it ok if with review and merge simple PRs ourselves?

@gabmis Sure thingk!

@gabmis Yes, it's fine if whomever you assign to review your PR does the merge. Please use "Squash and merge" so that the whole PR is one commit in master.

Issue with blame history. I will do a new PR and promise never to use Black again

also fixes #317


HTML entities in junit error output aren't escaped

If HTML entities (such as <main> which can appear in Ruby error output) appear in the error failure output, they disappear from the output (because the Buildkite markdown parser removes the invalid elements).
All the code here needs to HTML escape the output:
https://github.com/buildkite-plugins/junit-annotate-buildkite-plugin/blob/ab61195bab3c0c920f6a4fbf3e5ea047bf1d9da7/ruby/bin/annotate#L68-L79

Ah, backticks will definitely solve it as well. But if it's raw HTML, it'll be passed through.
I didn't think we could use backticks here, because it's nested in a <details> HTML element? I'll give it a test… maybe it works now!

Well, it works for me anyway, although I'm using the annotate script directly rather than as a plugin (because I haven't set up our pipeline with pipeline.yml). I just copied the annotate script into my repo and modified it to use three backticks, and that works, although I'd prefer the tags so that I can use the term class to make the output look a little nicer.


Docker issue - How to spin up several docker containers?

Hi all,
first of all great project and appreciate all the effort and hard work to build the Juice Shop.
I want to use the Juice Shop for an internal CTF and I already got the Juice-Shop running with CTFd. I only have now one problem: How can I easily spin up several docker instances of Juice Shop that all point to a different port, e.g. 3001, 3002 and 3003. So every attendee has it's own Juice Shop?
If I execute the following command it's pointing to the same container, just a different port
docker run -d -p 3001:3000 -e "NODE_ENV=ctf" -e "CTF_KEY=XXX" bkimminich/juice-shop

When doing this, I cannot connect to port 3001
docker run -d -p 3001:3001 -e "NODE_ENV=ctf" -e "CTF_KEY=XXX" bkimminich/juice-shop

I was already going through the docker docs but somehow couldn't find an answer for this.
Thanks

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

If you add -e "PORT=3001" and so on to the second command, does that work? And you might want to specify a --name js3001 as well, or you won't be able to restart crashed containers easily.

I too ran a CTF, last week in fact. For the setup I made a script that ran the needed number of instances:
#!/bin/bash

docker run -d -p 3000:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3001:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3002:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3003:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3004:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3005:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3006:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop
docker run -d -p 3007:3000 -e "NODE_ENV=ctf" bkimminich/juice-shop

When executed the script spins up 8 separate containers with ports 3000 to 3007 exposed:
» ./jshop.sh
2de220b6b0430e6a592bc1a435d7981af71b280e33a32716a5b815fcbaa5a420
97ad864d44975d76fb6cc7b31b19e10eb27f14f34cba553b01dead0bcec63a57
f48dd5d0cba3014ed7286a80b23bd00656d7edfc7fb47142bc75ccae1ebe7355
eb728dd808bc387549680e978a2435120b5ff4b16748c060623bf84a00c55258
dccf20363987504024e6d467595f017c86196581dad775313cc356df60745f6e
ad6789b42e0a30442dc62c2c3111af785f243938d5f1ad4b1602ee80c7116466
36e08029760882054a679f99572bc903b9a0ff719bcff55c764f3285da85561c
95c377284318f86867cbcd00e72e955cfd07e5a926f2a31c3b5d130f7a62705a

~

I just assigned each team/individual a specific port to use. Running docker ps shows that 8 separate containers are now running:
» docker ps
CONTAINER ID        IMAGE                   COMMAND                  CREATED             STATUS              PORTS                    NAMES
95c377284318        bkimminich/juice-shop   "npm start"              47 seconds ago      Up 45 seconds       <IP_ADDRESS>:3007->3000/tcp   boring_goodall
36e080297608        bkimminich/juice-shop   "npm start"              48 seconds ago      Up 46 seconds       <IP_ADDRESS>:3006->3000/tcp   relaxed_wescoff
ad6789b42e0a        bkimminich/juice-shop   "npm start"              49 seconds ago      Up 47 seconds       <IP_ADDRESS>:3005->3000/tcp   determined_yalow
dccf20363987        bkimminich/juice-shop   "npm start"              49 seconds ago      Up 48 seconds       <IP_ADDRESS>:3004->3000/tcp   romantic_bhaskara
eb728dd808bc        bkimminich/juice-shop   "npm start"              50 seconds ago      Up 48 seconds       <IP_ADDRESS>:3003->3000/tcp   competent_raman
f48dd5d0cba3        bkimminich/juice-shop   "npm start"              51 seconds ago      Up 49 seconds       <IP_ADDRESS>:3002->3000/tcp   modest_varahamihira
97ad864d4497        bkimminich/juice-shop   "npm start"              51 seconds ago      Up 49 seconds       <IP_ADDRESS>:3001->3000/tcp   elated_ritchie
2de220b6b043        bkimminich/juice-shop   "npm start"              52 seconds ago      Up 50 seconds       <IP_ADDRESS>:3000->3000/tcp   angry_snyder
00afd0111e90        ctfd_ctfd               "/opt/CTFd/docker-..."   11 days ago         Up 3 days           <IP_ADDRESS>:9999->8000/tcp   ctfd_ctfd_1

~

Hope this helps. If you wish to make sure that the CTFd flags are different make sure that you add the same CTF_KEY command to each line and then run juice-shop-ctf and import that into CTFd so that all the flags are synced and working.

Thanks. Will test that tomorrow.

Hi @battletux,
thanks for sharing. It's working now. Don't know what the problem was two days ago as I was using the same commands.


[DOCS] Quickstart step 9 - link to icon search page

Description
In Step 9 of the quickstart, it is mentioned that the user must grab icon definitions from react font awesome fa/si.  To improve UX, link to the icon search page on LinkFree.  Make sure to open in a new tab automatically so the user does not lose their place in the documentation
https://linkfree.eddiehub.io/icons
Screenshots
No response
Additional information
No response

link to the icon search page on LinkFree is already there:

But yeah it does not open a new tab to that page.

@Rounak-28 so weird! It wasn't when I was reviewing, I must have missed the update but yes can it open in a new tab so the user cannot lose their place in the directions. Thank you

I tried but target="_blank" is not working on the markdown file, is it not possible on markdown?

I haven't worked on the docs page myself but some markdown allows for you to use regular HTML within it. If the docs are via GitHub markdown, you may have to look through their docs to see what is recommended in this case
I can take a look later after work if you are not able to find the answer. You can also try asking in contributor-support or help in discord as someone else may be more available to check

I believe adding something like <a href="https://linkfree.eddiehub.io/icons" target="_blank"> Icons Here </a> should work, I've not had time to set up my local dev environment but if someone wants to try the above I think it should work :smile:

@Parsifal-M I tried the same but It's not working.

@Parsifal-M I tried the same but It's not working.

Oh :disappointed:, maybe the alternative could be to use [link](url){:target="_blank"}? If that does not work we'll have to do a bit more R&D :smile:

Great collaboration going on here! One thing to add don't forget about noreferrer for security when you do implement

PR: #4250 solves this issue