Travel time exponential

The final formula I decided to implement is:
$c_t = p ((\frac{t_t}{t_b})^q -1) $ (clipped at 0)
This has the nice property of starting at 0 cost for no delays while still exhibiting exponential behavior with a gradient of at least 1.

However, the significance of the delays is still minor?

Yes, I left the factor at 1, so we can tune it once we have the rest of the environment updated. It should probably be in the millions later.

Then, all is working well! :) We can just tune it later.

I tuned the factor to -500_000 and the value is still very small:

I tuned the factor to -500_000 and the value is still very small:

I think given that a single replacement is 35 million and delays are in the single-digit percentages, we will need to set the tuning factor quite a bit higher than that 😄
Maybe something relative to the budget we give.


clarify INF encoding requirement

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks @jasonknichel this is now live at https://docs.microsoft.com/en-us/windows-hardware/drivers/display/general-unicode-requirement


Alerts on partial rollout

Consider the following scenario: I created a key, and used gradual released - let say, 50% true, 50% false. Then, I moved on to the next task and totally forgot about that key. Would be nice to have an email reminder, let's say - after a week - to remind me that I did not complete the rollout.

I think that once the salt #437 will be up and we'll have datetime operations #165, you can create a rules that increase the rollout automatically by date, something like:
Date> 01/04 -> open to 10%
Date> 04/04 -> open to 30%
Date> 11/04 -> open to 50%
Date> 13/04 -> true

Closing for now


Ordered arguments

The idea of this project is really cool. However, it would be nice to add ability to use ordered arguments in terminal.
Implementation might be different.
For example we could use decorators to define command declaration:
@ordered_args('a', 'b')
def cmd(a: int, b: str='\n', c: int=0):
    ...

Or some special values:
def cmd(a: int=Ordered(), b: str = Ordered('\n'), c: int = Named(0)):
    ...

Or something else

Additionally I think this tool will be more useful if there is a more flexible control of input arguments.
My suggestions:

add ability to use shortcuts for arguments names (-f filename instead of --filename FILENAME)
use shortcuts (-f, --filename FILENAME)
describe  default values in help menu
can use flags without values (-d without any value, -d D used now).

Hi and thanks for opening this issue!
can you provide usage example? do you mean by ordered arguments positional arguments like in argparse?

Yes. I mean positional arguments.
For example, I want to pass one positional argument filename to program:
echo "Hello world" | python write_to_file.py output.txt

But now I have to do it by keyword argument
echo "Hello world" | python write_to_file.py -filename output.txt

sounds great, I assume to support more advanced per param config the best pattern would be:
from cbox import Arg, cli

@cli
def foo(x: int=0, y: Arg(positional=True, pos=1)=5):
    pass

later we can make Arg with more options.
probably pos=1 implies positional=True so one can do Arg(pos=1).
is that sounds ok? do you want to implement it and submit a PR 😃

Yes. That sounds really good.
About implementation. Well, I can do it but only next week.

ok feel free to submit PR :) no need to rush

I'm closing this issue for now, feel free to reopen it or push something to the PR.


Add option for Optimal Controller to run as part of Sequence Manager

Currently optimal controller needs to be ran as a loop of the same controller. It should be straight forward to make this into a variation of sequence manager

Would be nice if this can also go into the sequence manager? https://github.com/sdrogers/vimms-fusion/blob/master/analysis/experiment_2020_09/02_Top N with Persistent Exclusion List.ipynb

Let's think about this -- it's a general problem that somehow the state of the controller needs to be passed onto the next controller

Yeah it was already discussed before too in https://github.com/sdrogers/vimms/issues/39 (see last comment there).

easy enough to just update schedule between each sample, but I guess thats a quick fix. For the more advanced fix we'd need to remember that we wouldnt necessarily want to pass things on each time


openapi: Use response schema for describing simple success response.

In zulip.yaml simple json success response which only contains 'msg'
and 'result' properties has been described repeatedly in multiple
endpoints. Instead, use SimpleSuccess template for such responses
to increase code modularity and reusablility.

LGTM @timabbott.  The commit messages are clear, and it's basic YAML changes.  The ref change already has precedent.

I merged the first commit; for the second commit, can you fix the line-wrapping of the "description" fields?  Some of them, especially the short ones, look odd with just adding a newline after the |.

@timabbott wrapped the required text with 72 character width.

@orientor can you rebase this?

@timabbott resolved the merge conflicts.

I ended up expanding this to all of our descriptions that aren't "Bad request" or "Success", since I think we'll ultimately end up wanting almost all of them to be verbose enough to be a paragraph.  I merged the result as cfa7724bcc0220c5f8a5663230199e0127ced77a.
(I also un-indented some descriptions that were needlessly deeply indented in your PR).
Thanks @orientor!  @shubhamgupta2956 @akashaviator FYI; this will merge conflict with other OpenAPI changes, and we should use the description: | first line style for future description elements we add.


Super duper simple RTL support

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
add rtl support with dir='auto' on inputs and text areas
Ref: https://mough.xyz/312/psa-add-dir-auto-to-your-inputs-and-textareas
Motivation and context
RTL languages need love too.

We have RTL support.


Move zkasm generation into zkasm_codegen.rs

TODO: We need to find a better place for this module

TODO: We need to find a better place for this module

Why you think so? Exploring filetests/src I seen files which do very different stuff, all in one directory. Or you want to move away this code from tests folder and put somewhere like cranelift_codegen?

TODO: We need to find a better place for this module

Why you think so? Exploring filetests/src I seen files which do very different stuff, all in one directory. Or you want to move away this code from tests folder and put somewhere like cranelift_codegen?

Mainly because this functionality is not strictly specific to tests. For example, @mooori is planning to use it in the benchmarking tools that will move outside of filetests folder.
cranelift_codegen might be a reasonable place, specifically cranelift/codegen/src/isa/zkasm, but we need to understand the visibility rules there a bit better.
@nagisa , where would you say is the good location for this functionality?

@nagisa , where would you say is the good location for this functionality?

I don't have any particular suggestions off top of my head right now, but I will suggest to not overthink it now and move the shared code out into a a shared dependency when a 2nd user of this code shows up. Moving the code around in anticipation of this 2nd user may very well end up with that code having a singular user in perpetuity anyhow (if e.g. benchmarks' needs turn out to be different enough and it becomes more sensible for it to have its own copy) with all of the associated complexity.
Not to mention that it'll be much easier to pick an appropriate place for the code once the two users actually materialize.


x509: certificate signed by unknown authority

Describe the bug
Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")
To Reproduce
Install ck8s-kubespray use version 2.18.0. and apply apps.
Expected behavior
We don't want this to happen!!
Version (add all relevant versions):

Compliant Kubernetes apps version [e.g. v2.18.0]

Additional context
This can be solved by recreating new certs and use them as kubeconfig

maybe just a one time error


Harbor launches slowly when registry has too many repositories

Version:

docker 1.12.0
docker-compose 1.8.1
harbor 0.4.0

Registry use aliyun OSS as storage backend. There are 12000+ repositories in registry.
harbor/ui log:
Nov 10 11:56:50 <IP_ADDRESS> ui[727]: 2016-11-10T03:56:50Z [DEBUG] [utils.go:246]: Start syncing repositories from registry to DB...
Nov 10 11:56:50 <IP_ADDRESS> ui[727]: 2016-11-10T03:56:50Z [DEBUG] [authutils.go:67]: scopes: [registry:catalog:*]
Nov 10 11:56:50 <IP_ADDRESS> ui[727]: 2016-11-10T03:56:50Z [INFO] current access, type: registry, name:catalog, actions:[*]
Nov 10 12:18:29 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:29Z [DEBUG] [transport.go:51]: 200 | GET http://registry:5000/v2/_catalog?n=200000
Nov 10 12:18:29 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:29Z [DEBUG] [utils.go:249]: reposInRegistry count:12008
Nov 10 12:18:29 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:29Z [DEBUG] [utils.go:266]: reposInDB count:0
Nov 10 12:18:35 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:35Z [DEBUG] [utils.go:271]: reposToAdd count:0
Nov 10 12:18:35 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:35Z [DEBUG] [utils.go:272]: reposToDel count:0
Nov 10 12:18:35 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:35Z [DEBUG] [utils.go:311]: Sync repositories from registry to DB is done.

It takes about 20 minutes to sync repositories from registry to DB.

I see the time was spent here:
Nov 10 11:56:50 <IP_ADDRESS> ui[727]: 2016-11-10T03:56:50Z [INFO] current access, type: registry, name:catalog, actions:[*]
Nov 10 12:18:29 <IP_ADDRESS> ui[727]: 2016-11-10T04:18:29Z [DEBUG] [transport.go:51]: 200 | GET http://registry:5000/v2/_catalog?n=200000
The intention is to avoid inconsistency between DB and registry data.
We can add a flag to skip the sync so it won't try to call the API v2/_catalog to sync image to DB.  However due to internal release schedule the change can't be made shortly.
To workaround, you can comment the line 83~85 in src/ui/main.go to skip this step.
Sorry for the inconvenience

Closing as we disabled syncing registry by default now.


fix(adapters): Revert new adapters

The newly added adapters require a MAJOR policy bundle update so that they can work with older versions of Trivy.
Without a new MAJOR policy bundle update, the following issue will happen: https://github.com/aquasecurity/trivy/issues/4124
The plan is to merge all adapters at once (for all new AWS services at least), when they are all ready. At that point we will bump the MAJOR policy bundle version as per short term proposal idea described in this proposal here: https://github.com/aquasecurity/trivy/issues/4134

hi @knqyf263 - if you have time could you help me test this? Below are the instructions to test:

Run a local docker registry to push the bundle to:

docker run -it --rm -p 5000:5000 registry

Create a policy bundle with this branch. You can use the following operations:

rm -rf bundle bundle.tar.gz && make bundle  && oras push localhost:5000/defsec:1 --config /dev/null:application/vnd.cncf.openpolicyagent.config.v1+json  bundle.tar.gz:application/vnd.cncf.openpolicyagent.layer.v1.tar+gzip

Build an "old" version of Trivy (anything works, I selected the v0.40.0 tag), build it with the following patch:

diff --git a/pkg/policy/policy.go b/pkg/policy/policy.go
index 19d27bd34..1e4c3076b 100644
--- a/pkg/policy/policy.go
+++ b/pkg/policy/policy.go
@@ -18,8 +18,10 @@ import (
 )

 const (
-       bundleVersion    = 0 // Latest released MAJOR version for defsec
-       bundleRepository = "ghcr.io/aquasecurity/defsec"
+       bundleVersion    = 1 // Latest released MAJOR version for defsec
+       bundleRepository = "localhost:5000/defsec"
        policyMediaType  = "application/vnd.cncf.openpolicyagent.layer.v1.tar+gzip"
        updateInterval   = 24 * time.Hour
 )

Build with mage build as normal after applying this patch.

Run Trivy as following:

rm -rf ~/Library/Caches/trivy/ &&  ~/repos/trivy/trivy --debug config .

Where the trivy is the locally built binary in step 2. The above should clear the policy  bundle on disk, download a locally built one from step 1, complete the scan and not throw any errors.

I confirmed it worked.
$ rm -rf ~/Library/Caches/trivy/policy/content/policies
$ make bundle
$ tar xvf bundle.tar.gz -C ~/Library/Caches/trivy/policy/content
$ trivy config .


Upgrade an account is not possible for storage once created

[Enter feedback here]

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

ID: 8bf5c2f8-d961-6460-194e-caa06ecfafa6
Version Independent ID: 29c0ec30-d312-9e9f-0bff-8c5e6b7eb907
Content: Upgrade to a general-purpose v2 storage account - Azure Storage
Content Source: articles/storage/common/storage-account-upgrade.md
Service: azure-storage
Sub-service: storage-common-concepts
GitHub Login: @akashdubey-ms
Microsoft Alias: akashdubey

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

@sapkotamit007 Once a storage account is created, you cannot change its account kind to a different type. If you want to move your data to a storage account of a different type, you must create a new account and copy the data to the new account.

@SaibabaBalapur-MSFT yes I believe that's correct, I was marking the same as Documentation has it written differently

@sapkotamit007
Thanks for your contribution. Please add your feedback in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)


Self updater doesn't respect package manager installation if cargo-dist installation occurred before

The self updater ignores that the currently running binary was installed by a package manager if the recipe is present because a different cargo-dist curl installation happened before.
This is based on https://github.com/astral-sh/uv/pull/2228
Let's install uv 0.1.14 through the cargo-dist curl installer first, then a package manager installation of 0.1.13 on top:
$ curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.1.14/uv-installer.sh | sh
downloading uv 0.1.14 x86_64-unknown-linux-gnu
installing to /home/konsti/.cargo/bin
  uv
everything's installed!

Let's install a different, also not up-to-date version. In this case i took https://github.com/astral-sh/uv/pull/2228, edited it to 0.1.13 and called pipx run maturin build.
$ pipx install /home/konsti/projects/uv/target/wheels/uv-0.1.13-py3-none-linux_x86_64.whl
⚠  Note: uv was already on your PATH at /home/konsti/.cargo/bin/uv
  installed package uv 0.1.13, installed using Python 3.11.6
  These apps are now globally available
    - uv
done! ✨ 🌟 ✨

Or there's a different version of uv, let's remove it, or alternatively just change path precedence.
$ rm /home/konsti/.cargo/bin
$ which uv
/home/konsti/.local/bin/uv
$ uv --version
uv 0.1.13 (e73705607 2024-03-06)

Call the updater:
$ uv self update
success: You're on the latest version of uv (v0.1.13).

In this case, we should have gotten the "you're in a managed environment message", not the (incorrect) latest version.

That's an interesting issue! Like you say, the presence of the receipt is the proxy we use to determine if it was installed by a package manager. Is there another method we could have used to determine if the binary was installed via a package manager for your usecase?

We could add a feature flag and only activate it for github releases builds. Otherwise, the binary should imo check that the recipe version is not the binary version

Could we check if the currently-running executable is the same as the one that's going to be updated / replaced?

Thought about this, and since we do have information about the installation root the receipt is for, we can compare that against the actively running EXE.


Error on config read on standard readme execution

Hello there, i was playing around trying the "template" and got two different problems in Debian.
First, with current trunk state following standard readme instructions i got:
'/bin/sh -c go mod download' returned a non-zero code: 1. during docker build  .  -t api-rest
Secondly, i bypassed previous 'dependecy' problem updating to latest alpine image version
on Dockerfile:  golang:1.15.3-alpine3.12
after that, all goes smoothly until you get execution error
can't read cofig file './cmd/api/config.yml'
May you have a look?

I just fixed the error in the last commit. Check that it works well for you.

Antonio sé que es bastante tarde (porque se me olvidó responder) pero gracias por mirarlo
en su momento! Me sirvió!


Initial state with sort on column

Hello,
is there some option to set up defaut sort on column? I have columns with IDs in my table, at this moment to sort, user need to click on column heading. Can i somehow make initial state with sort active on IDs column?
Cheers!

Trivial, look in the docs: http://allenfang.github.io/react-bootstrap-table/docs.html#defaultSortName

@jabberwo, thanks, it's certainly answer :)


feat(fsengagement): Added renderBackButton prop

requisite feature ticket: https://brandingbrand.atlassian.net/browse/REL-3669
mocks: https://www.figma.com/file/M5oqOpYs8mm4Z3KvZ4UM08/Related-App?node-id=8493%3A115
associated feature PR on Related project: https://github.com/brandingbrand/related.rn/pull/1999
description:
this adds a prop renderBackButton?: (navigation?: Navigator) => void to EngagementComp, allowing a custom backButton to be rendered in the content view when !props.animatedScroll && !props.animate


Engineering Call - Jul 24

Engineering Call
Date: Wed, Jul 24, 2019 10am.
Attendees: @itamarreif @faddat @modkaffes @guylepage3
Minutes from Call

@faddat got the Feather mobile device talking to devices.
Went over the Universe Flow Illustration / Diagram from #23 Proposal: Update to path to obfuscation and beyond...
Determined goals and deliverables for next few weeks to have the web app interacting with a running mobile/feather device in a client-server relationship. There are two portions to accomplish this during Sprint 5 (Current sprint) and Sprint 6;

1a. Build BLE (Bluetooth Low Energy) server with CRUD capability. @itamarreif @faddat
2a. Build Web Client to interact with Feather device. @modkaffes @guylepage3
2b. Build out crypto infrastructure running on Feather device. @itamarreif @faddat

Discussed mobile deployment.

@guylepage3 to setup call with @itsprof and get his take on the mobile side of things.

Goals

Have the web app interacting with a running mobile/feather device in a client-server relationship by the end of Sprint 6.

A few useful resources discussed:

The official Espressif ESP32 documentation: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/index.html
React Native BLE library: https://github.com/Polidea/react-native-ble-plx
A primer on the security infrastructure built into the ESP32 chips: https://medium.com/the-esp-journal/understanding-esp32s-security-features-14483e465724
More docs about the Flash Encryption feature: https://docs.espressif.com/projects/esp-idf/en/latest/security/flash-encryption.html

Please comment with any more relevant links and ideas!

@itamarreif I just updated your notes slightly.

Closiing


fix not able to contact new people

fixes #1062

Also fixes #1075, #1073, #1071, #1060, #1058 and #1055
:) looks like people don't read opened issues before logging a new one...

@ifedapoolarewaju if you can take a look, this is a bit massive right now...

thank you!

fixes #1062, #1075, #1073, #1071, #1060, #1058 and #1055

looks like we should have pre-fixed each issue with "fixes", otherwise it doesn't close automatically.. can you close them?
also, how often do you create a new release? I think a 2.7.1 could be useful right now with this fix


feat(i18n): add default language to html tag.

Description:
This PR implements a vital modification to improve screen reader accessibility. It dynamically adjusts the HTML lang attribute when there's a change in the user-selected language, ensuring accurate pronunciation for screen readers.
Changes:

Language Change Event Handler in Layout.tsx:

Path: src/components/Layout/Layout.tsx
The useEffect hook now sets the HTML lang attribute based on the i18n.language variable.
Ensures that the lang attribute is only modified when it differs from the current setting.

Example:
useEffect(() => {
  document.documentElement.setAttribute('lang', i18n.language);
}, [i18n.language]);

To-Do Items:

[ ] Resolve Pr Comments and Suggestions.

Test Cases:

[x] Test case ensuring that the lang attribute updates correctly on language change.
[x] Test case verifying the default language is set on initialization.

Related Story:
This PR addresses the requirements outlined in Jira - OTT-397.
Request for Review:
Your feedback is crucial in fine-tuning these enhancements and ensuring the best user experience. Eager to hear your thoughts and suggestions. Thanks in advance for your valuable input!

@R-Cloud-Designs, you can merge this PR. We prefer merging with a "Squash and merge" strategy to keep a linear GIT history.


[BUG] hot-relod doesn't work in firefox(but works in chrome though)

Bug Report Quick Checklist
I do all css stuff if firefox and snowpack's hot-reload isn't working in firefox and thats a little sad to me. :(
 node -v
v14.16.0
npm -v
7.6.3

Describe the bug
Hot reload for firefox doesn't work but hot-reload for chrome works neatly.
To Reproduce
We can't fix bugs that we can't see for ourselves. Issues often need to be closed if this section is skipped.

npm init snowpack-app --template @snowpack/app-template-NAME (TRY ANY APP, ITS COMMON ISSUE ~sahil).
Try setting height of body tag in css i.e., body{height: 200vh}
Now, browse the server in firefox, and scroll down so you get to end of page and add color to body i.e., body{height: 200vh; background-color: red;}
You'll notice the page indeed reloaded but we lost the scroll position.
The hot-reload can be easily done with parcel bunder in firefox if you wanna try parcel index.html, idk why snowpack is not supporting it or is it a bug?

Expected behavior
Scroll position should not be lost on changing the css file at all.
Anything else?
Snowpack is awesome, also its size is very efficient, i love snowpack.
Thanks.

Just in case you are using the plugin-react-refresh in your snowpack.config.js file, please remove it cause I believe Snowpack does better without it.
That's a personal opinion so give it a try and let's see cause I was about to file an issue after spending a whole trying to find out why I couldn't get Hot Reload when using Tailwind only to find this plugin being the culprit

Just in case you are using the @snowpack/plugin-react-refresh in your snowpack.config.js file, please remove it cause I believe it's the cause and also Snowpack does better without it.
That's a personal opinion so give it a try and let's see cause I was about to file an issue after spending a whole trying to find out why I couldn't get Hot Reload when using Tailwind only to find this plugin being the culprit

I am not using config file for snowpack!
What else would you suggst me to try.?


Not an issue, just a help request: IPs?

Hi @instantsc ,
Thank you for your SimpleDnsCryp version... very useful!
Please, I have a simple question: How can I block IPs?
By following the regular DNSCryp Wiki, and using your SimpleDnsCrypt <IP_ADDRESS>, I edited my dnscrypt-proxy.toml by adding:
[blocked_ips]
blocked_names_file = "C:\Program Files\SimpleDNSCrypt\dnscrypt-proxy\IPblacklist.txt"
... where IPblacklist.txt is a file containing my IPs blocked list.
Unfortunately is not working for me.
Please, can you help me?
Thank you in advance.

blocked_ips => blocked_ips_file


Can't DL some videos

Hi, why is it that there videos that can't be downloaded?
sample vid https://www.youtube.com/watch?v=2-FHu_WqmMw

I'll have a look into this, but as far as I can tell it won't be possible to fix from this PHP project. This appears to be a YouTube issue (well, it's a restriction from YouTube) and I cannot effect this.
If you do find a way round this, please create a pull request. 👍

Just a note that it looks to be possible over at https://github.com/Rudloff/alltube using CTRL-S
I might take a look at it over the next week.

Thanks for that @Macdeviant, I'll have a look into it 😄


tests/test_flobject.py::test_accessor_methods_on_settings_objects failing in the latest Fluent image

For now, I'm going to disable the test.

Resolved with the current fluent image.


Enable bats backup and restore test

#132578535
Signed-off-by: Konstantin Maksimov<EMAIL_ADDRESS>

Closing - in Go CLI and bbr world, this workflow is no longer supported.


Bypass cudaStreamLegacy related bug that exists in early version of NCCL

There is a bug related to cudaStreamLegacy (default stream) in early version of NCCL. This PR solves it. it uses cupy's solution that bypasses this bug with 0 pointer (in below picture).

Also, some of these header files are not used. https://github.com/alpa-projects/tensorflow-alpa/blob/c6da162d80954c00fc9ca3d0848e5300ffbc980a/tensorflow/compiler/xla/service/gpu/alpa_nccl_wrapper.cc#L24-L33
Please delete them in later PRs.

Also, some of these header files are not used.
https://github.com/alpa-projects/tensorflow-alpa/blob/c6da162d80954c00fc9ca3d0848e5300ffbc980a/tensorflow/compiler/xla/service/gpu/alpa_nccl_wrapper.cc#L24-L33
Please delete them in later PRs.

OK


Possibly PR'ed the wrong branch.


Update cats-effect to 3.3.2

Updates org.typelevel:cats-effect from 3.3.0 to 3.3.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #209 (83c54c5) into master (f8261e7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #209   +/-   ##
=======================================
  Coverage   87.30%   87.30%
=======================================
  Files          28       28
  Lines         843      843
  Branches       39       39
=======================================
  Hits          736      736
  Misses        107      107

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 f8261e7...83c54c5. Read the comment docs.

Superseded by #210.

Superseded by #210.


Facet and Filters behavior

@curqui I've added the Issues Summary part!

I don't know if it's too late to suggest this, but I would strongly recommend we change the filters parameter to just filter. I think it's less confusing, mainly because the parameter's value will only ever be a single filter string or array.
Even if the value can be nested allowing for complexity, it's still just a logical expression. It's not as though you can define multiple filters that are applied independently or sequentially.
I would also recommend filterDistribution and filterAttributes to replace facetsDistribution and attributesForFaceting.

I don't know if it's too late to suggest this, but I would strongly recommend we change the filters parameter to just filter. I think it's less confusing, mainly because the parameter's value will only ever be a single filter string or array.
Even if the value can be nested allowing for complexity, it's still just a logical expression. It's not as though you can define multiple filters that are applied independently or sequentially.
I would also recommend filterDistribution and filterAttributes to replace facetsDistribution and attributesForFaceting.

@curquiza Can we rename filters to filter at this time? I also think it helps to use it this way as a contextual verb.
@react-learner I think we need to keep facetsDistribution since it expresses the fact that we want from MeiliSearch to distribute those facets as a search result parameter. On the other side, I agree with the fact that attributesForFaceting is lacking precision because it is now used to authorize filtering and faceting on those fields. We will handle that in another spec.

I would also recommend filterDistribution and filterAttributes to replace facetsDistribution and attributesForFaceting.
facetsDistribution

Personally, I think both of them may be confusing. As intuitively I would think this would give me back the "median" distribution of filters amongst all previous filters ? I don't know. It's not very clear.
I thought of documentDistribution as we show the distribution of documents between each category. And also, as it clearly informs the users he is going to receive a distribution of documents. So even if it loses in facet context, it at least informs about the return value.
Finally, about the word choices if we had to go for one of the mentioned option:

Facets: Its not a common word. Its mainly used by Algolia and was previously used by elastic search. I feel like its something we can relate to as french people because the etymology of the word is french
one side of something many-sided, especially of a cut gem. The definition makes sense, but is not intuitive for non native English or french speaker.
Aggregate: The word that is now used by ElasticSearch. a whole formed by combining several separate elements.. Which is also technically accurate to describe the distribution. I still feel this is confusing and not intuitive.
Filter: Very common word, but filter distribution implies that we would have that kind of distribution x > 12: 1200 documents

So if we make the assumption that the user will have to go to the documentation to understand the meaning of this field, I would choose

Documents Distribution: As at least it is not an intimidating word
Facet Distribution: As that is what we already have and what algolia uses
Aggregate Distribution: As it is the one used by elastic search, a good chunk of our users
But not Filter Distribution: As it is not really accurate

@gmourier I agree that facetsDistribution describes the behavior pretty well; I can't really imagine any scenario besides building a faceted search UI where I would want to use this parameter. However, I also think it's worth noting that with the changes proposed here, facets no longer has a particular meaning within MeiliSearch. As far as the software is concerned, faceting is a specific way of using filters. In other words, knowledge of the term "faceting" is optional to use filters, or even to make a faceted search UI w/ MeiliSearch. So, why not make it optional throughout our software and documentation?
I recognize that "Faceted search" is one of MeiliSearch's desirable features, so I'm definitely not proposing that we eliminate the keyword from the docs—it attracts web traffic and communicates well with the search-focused crowd. However, I think we could background "facets"/"faceting"/"faceted search" by keeping these words off of parameter names, substituting more intuitive names like categoryDistribution or resultDistribution. By doing so, we can reduce friction for people who have never seen the word "facets" before (i.e. less search-focused users: hobbyists, solo devs, IT professionals) without impacting those who are more knowledgeable.
It's an extreme example, but I wouldn't want someone to search "facets meilisearch" on Google and end up on the facetsDistribution reference page instead of our main guide on setting up faceted search. Also, having a single software-level reference to facets when all others have been removed just seems inconsistent to me 🤷♂

Some possible names for facetsDistribution:
hitsByField : this one is really intuitive, since the value of the parameter should be a list of field names. Of course numberOfHitsByField would be more accurate, but that's pretty long. hits could also be replaced by matches or results depending on how we define these terms internally.
documentDistribution : proposed by @bidoubiwa
result/hit/matchDistribution : similar to Bidoubiwa's. The nice thing about the word distribution is it instantly conveys that the response will be a number (this is not as clear with hitsByField)
facetDistribution : at the very least, we must get rid of the s to be more Anglophone 😆

I've updated the spec to mention that we are renaming filters to filter.


Cookie is broken when there are too many permission for a user.

Dear Sir/Madam,
We use Asp.Net Identity framework as our ACL and wrote some custom code to fit our requirement.  The framework works fine. We use Claims-based authorisation.
We found a very strange issue today. There is a user who belongs many roles which have lots of permission claims. And this use keep getting:
"HTTP Error 400. The size of the request headers is too long." error.
And I checked and found there are some ASP.Net core identity cookies as attached image:

I manually removed cookie and that user could work for a while. And I also found this only happens after second AJAX call (not cross domain AJAX call).
After I remove this user from some roles and only keep one or two roles for him, everything works perfectly.
My development environment is .Net Core 1.1.
Does anyone have some idea on this issue?
Thanks.
Regards,
Max

There are limits to the size of your request headers. Both IIS as Kestrel have options to configure these limits. So you have the option to increase this limit.

Hi Niels,
Thanks for your information. I have changed IIS request limit size but does not work. I will check Kestrel options.
Thanks again.

There might also be restriction by http.sys. Check these SO posts:
https://stackoverflow.com/questions/35749180/do-web-config-header-size-limits-override-http-sys-limits-in-the-registry
https://stackoverflow.com/questions/37112367/size-of-the-request-headers-is-too-long
But for another, more robust, solution you can also look into implementing a SessionStore. It is a settable property on the CookieAuthenticationOptions, designed for these kind of issues. The complete set of claims for the user are stored in the specified session store, and only a session identifier is stored in the cookie, greatly decreasing the site of the cookie.

Hi Niels,
Thanks for help. It seemed that this is IIS issue. It works after I modified registry entry for MaxFieldLength,MaxRequestBytes.
It is very strange that modified httpRuntime maxRequestLength with IIS Configuration Editor does not work. But this is not Asp.net Identity problem.
Thanks again.
Regards,
Max

How many claims do you have? If you're seeing a cookie of that size your user claims must be huge Do you really need that many? Are you treating claims as permissions perhaps?
The server and even the browser itself will set limits on header sizes and lengths. As @Niels-V suggests you could move to using a session store; there's a sample in https://github.com/aspnet/Security/tree/dev/samples/CookieSessionSample

As you're unblocked I'm closing the issue.


Add Front Row Github and add Remote to location

We're not hiring engineers right this second, but we will be in the future. Thanks for making this list!

Thanks for the update!


[API-3392] Profitability Checks

This PR adds checks when relaying a settlement (or any type of relay, but this is only implemented for settlements for now) that the settlement is going to be profitable for the relayer (since gas costs can be very high for the settlement relay on evm chains). Profitability is determined as follows:

Simulate the Process call on the evm side (process is the function that delivers the hyperlane message and calls the recipient contract, in our case that the is gateway contract).
Calculate (base fee + estimated gas tip cap) * estimated gas of process call to get the estimated tx fee in gwei
Fetch the current price of ETH in usd from CoinGecko (we are assuming a 1 usd = 1 usdc conversion)
Convert price of eth in usdc to price of gwei in usd
Convert tx fee in gwei to tx fee in usd
Convert tx fee in usd to tx fee in uusdc
Then, we get the % of the total value of the relay that the tx fee will take. Compare this % with the user specified min tx fee % on the relays destination chain. If the tx fee % is less than the min fee %, then the relay is profitable.

This also does some refactoring work around how hyperlane relays are submitted from other services that require replying. The order settler and the order fulfiller (specifically the timeout portion of the order fulfiller) have been refactored to directly call SubmitTxToRelay on the hyperlane relayer runner, instead of there being an impact dependency on them inserting a row into the submitted tx's table, and the hyperlane relayer runner polling that table for transfers to relay.

two small comments otherwise lgtm 🙏

Oh also, I dont think the current way this PR estimates tx costs is adequate for all evm chains. We had to do some L2 specific tx cost in the relayer which you can see here https://github.com/skip-mev/relayer/tree/c0dd40d52000c6d63086854552b2064ec432e4e2/shared/feequoter/tx_cost_estimation. The way tx fees are estimated in this PR are adequate for eip 1559, but iirc, dont adequately capture the fees L2s charge for L1 gas costs.

Oh also, I dont think the current way this PR estimates tx costs is adequate for all evm chains. We had to do some L2 specific tx cost estimation in the relayer which you can see here https://github.com/skip-mev/relayer/tree/c0dd40d52000c6d63086854552b2064ec432e4e2/shared/feequoter/tx_cost_estimation. The way tx fees are estimated in this PR are adequate for eip 1559, but iirc, dont adequately capture the fees L2s charge for L1 gas costs. Double check this but I think you'll end up just being off by cents at most for L2s which is not a huge deal, and you can add better L2 fee estimation later if so.

For arbitrum at least, when looking at what is returned for the gas estimate and what the actual tx fee ended up being on chain for a settlement, the estimate was always above by a slight bit, which imo is what we want (instead of being below the actual cost). The arbitrum docs as well say that using the standard l1 way of estimating a tx cost will include the l1 gas costs as well https://docs.arbitrum.io/build-decentralized-apps/how-to-estimate-gas#skip-the-formula-focus-on-practical-know-how


Modified notebook notebooks/official/workbench/demand_forecasting/forecasting-retail-demand.ipynb

Error from regression test:
InternalServerError: 500 An internal error occurred and the request could not be completed. This is usually caused by a transient issue. Retrying the job with back-off as described in the BigQuery SLA should solve the problem: https://cloud.google.com/bigquery/sla. If the error continues to occur please contact support at https://cloud.google.com/support. Error: 1001262
Location: US
Job ID: 9197741a-8472-488f-b4dd-a0f3b4f4de42
Fix: Ran the notebook. It ran fine without error
Changes made: Modified notebook according to template

[X] Use the notebook template as a starting point.
[X] Follow the style and grammar rules outlined in the above notebook template.
[X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[X] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[X] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

#5: Step #4: ModuleNotFoundError                       Traceback (most recent call last)
Step #5: Step #4: Cell In [9], line 5
Step #5: Step #4:       3 from google.cloud import bigquery
Step #5: Step #4:       4 from google.cloud.bigquery import Client
Step #5: Step #4: ----> 5 from sklearn.metrics import (mean_absolute_error,
Step #5: Step #4:       6                              mean_absolute_percentage_error,
Step #5: Step #4:       7                              mean_squared_error)
Step #5: Step #4:       9 get_ipython().run_line_magic('matplotlib', 'inline')
Step #5: Step #4:      11 import warnings
Step #5: Step #4:
Step #5: Step #4: ModuleNotFoundError: No module named 'sklearn'


Remove procmacros

PR for codecov

of course there's a clippy bug.. cba to deal with this at the moment


Could not load opencoarrays under ubuntu 18.04

I am using ubuntu 18.04. I tried to load opencoarrays using the instruction
sudo apt install libcoarrays-dev libopenmpi-dev open-coarrays-bin
But it did not work. Could you please send me the correct procedure to load the software? I am using gfortran.
$gfortran --version
GNU Fortran (Ubuntu 7.3.0-16ubuntu3) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
Thanks,
Subrata Ray
<EMAIL_ADDRESS>

It's not clear from your description what you're thinking went wrong. After installing OpenCoarrays, please compile using the caf wrapper that OpenCoarrays provides:
It works for me on Lubuntu 18.04.  A transcript is below.  I'm closing this for now. If you encounter further issues, please let us know and please fill out the issue template with more details.
$ sudo apt install open-coarrays-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  gfortran gfortran-7 libcaf-mpi2 libcoarrays-dev libgfortran-7-dev
Suggested packages:
  gfortran-multilib gfortran-doc gfortran-7-multilib gfortran-7-doc
  libgfortran4-dbg
The following NEW packages will be installed:
  gfortran gfortran-7 libcaf-mpi2 libcoarrays-dev libgfortran-7-dev
  open-coarrays-bin
0 upgraded, 6 newly installed, 0 to remove and 149 not upgraded.
Need to get 7,746 kB of archives.
After this operation, 28.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libgfortran-7-dev amd64 7.3.0-16ubuntu3 [531 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 gfortran-7 amd64 7.3.0-16ubuntu3 [7,101 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 gfortran amd64 4:7.3.0-3ubuntu2 [1,352 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcaf-mpi2 amd64 2.0.0~rc1-2 [36.4 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcoarrays-dev amd64 2.0.0~rc1-2 [65.7 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 open-coarrays-bin amd64 2.0.0~rc1-2 [10.1 kB]
Fetched 7,746 kB in 4s (1,970 kB/s)
Selecting previously unselected package libgfortran-7-dev:amd64.
(Reading database ... 194295 files and directories currently installed.)
Preparing to unpack .../0-libgfortran-7-dev_7.3.0-16ubuntu3_amd64.deb ...
Unpacking libgfortran-7-dev:amd64 (7.3.0-16ubuntu3) ...
Selecting previously unselected package gfortran-7.
Progress: [ 26%] [##############............................................]
Unpacking gfortran-7 (7.3.0-16ubuntu3) ...
Selecting previously unselected package gfortran.
Preparing to unpack .../2-gfortran_4%3a7.3.0-3ubuntu2_amd64.deb ...
Unpacking gfortran (4:7.3.0-3ubuntu2) ...
Selecting previously unselected package libcaf-mpi2:amd64...................]
Preparing to unpack .../3-libcaf-mpi2_2.0.0~rc1-2_amd64.deb ...
Unpacking libcaf-mpi2:amd64 (2.0.0~rc1-2) ...
Selecting previously unselected package libcoarrays-dev.
Preparing to unpack .../4-libcoarrays-dev_2.0.0~rc1-2_amd64.deb ...
Unpacking libcoarrays-dev (2.0.0~rc1-2) ...
Selecting previously unselected package open-coarrays-bin.
Preparing to unpack .../5-open-coarrays-bin_2.0.0~rc1-2_amd64.deb ...
Unpacking open-coarrays-bin (2.0.0~rc1-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libgfortran-7-dev:amd64 (7.3.0-16ubuntu3) ...
Setting up libcaf-mpi2:amd64 (2.0.0~rc1-2) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up gfortran-7 (7.3.0-16ubuntu3) ...
Setting up gfortran (4:7.3.0-3ubuntu2) ...
update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f95 (f95) in auto mode
update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f77 (f77) in auto mode
Setting up open-coarrays-bin (2.0.0~rc1-2) ...
Setting up libcoarrays-dev (2.0.0~rc1-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
$ which caf
/usr/bin/caf
$ caf --version

OpenCoarrays Coarray Fortran Compiler Wrapper (caf version 2.0.0-rc1)
Copyright (C) 2015-2016 Sourcery, Inc.

OpenCoarrays comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of OpenCoarrays under the terms of the
BSD 3-Clause License.  For more information about these matters, see
the file named LICENSE that is distributed with OpenCoarrays.

Thank you. This refers to your mail
I received these messages.
ab@ab:~$ which caf
/usr/bin/caf
ab@ab:~$ caf --version
OpenCoarrays Coarray Fortran Compiler Wrapper (caf version 2.0.0-rc1)
Copyright (C) 2015-2016 Sourcery, Inc.
OpenCoarrays comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of OpenCoarrays under the terms of the
BSD 3-Clause License.  For more information about these matters, see
the file named LICENSE that is distributed with OpenCoarrays.
ab@ab:~$ caf b.f90 -ob
/usr/bin/caf: line 333: /usr/bin/mpifort: No such file or directory
Error: comand:
/usr/bin/mpifort -I/usr/include/OpenCoarrays-2.0.0-rc1_GNU-7.3.0 -fcoarray=lib b.f90 -ob /usr/lib/x86_64-linux-gnu/libcaf_mpi.a
failed to compile.
ab@ab:~$
Subrata Ray
On Fri, Aug 17, 2018 at 7:33 PM, Damian Rouson<EMAIL_ADDRESS>wrote:

It's not clear from your description what you're thinking went wrong.
After installing OpenCoarrays, please compile using the caf wrapper that
OpenCoarrays provides:
It works for me on Lubuntu 18.04. A transcript is below. I'm closing this
for now. If you encounter further issues, please let us know and please
fill out the issue template with more details.
$ sudo apt install open-coarrays-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
gfortran gfortran-7 libcaf-mpi2 libcoarrays-dev libgfortran-7-dev
Suggested packages:
gfortran-multilib gfortran-doc gfortran-7-multilib gfortran-7-doc
libgfortran4-dbg
The following NEW packages will be installed:
gfortran gfortran-7 libcaf-mpi2 libcoarrays-dev libgfortran-7-dev
open-coarrays-bin
0 upgraded, 6 newly installed, 0 to remove and 149 not upgraded.
Need to get 7,746 kB of archives.
After this operation, 28.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libgfortran-7-dev amd64 7.3.0-16ubuntu3 [531 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 gfortran-7 amd64 7.3.0-16ubuntu3 [7,101 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 gfortran amd64 4:7.3.0-3ubuntu2 [1,352 B]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcaf-mpi2 amd64 2.0.0~rc1-2 [36.4 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcoarrays-dev amd64 2.0.0~rc1-2 [65.7 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 open-coarrays-bin amd64 2.0.0~rc1-2 [10.1 kB]
Fetched 7,746 kB in 4s (1,970 kB/s)
Selecting previously unselected package libgfortran-7-dev:amd64.
(Reading database ... 194295 files and directories currently installed.)
Preparing to unpack .../0-libgfortran-7-dev_7.3.0-16ubuntu3_amd64.deb ...
Unpacking libgfortran-7-dev:amd64 (7.3.0-16ubuntu3) ...
Selecting previously unselected package gfortran-7.
Progress: [ 26%] [##############............................................]
Unpacking gfortran-7 (7.3.0-16ubuntu3) ...
Selecting previously unselected package gfortran.
Preparing to unpack .../2-gfortran_4%3a7.3.0-3ubuntu2_amd64.deb ...
Unpacking gfortran (4:7.3.0-3ubuntu2) ...
Selecting previously unselected package libcaf-mpi2:amd64...................]
Preparing to unpack .../3-libcaf-mpi2_2.0.0~rc1-2_amd64.deb ...
Unpacking libcaf-mpi2:amd64 (2.0.0~rc1-2) ...
Selecting previously unselected package libcoarrays-dev.
Preparing to unpack .../4-libcoarrays-dev_2.0.0~rc1-2_amd64.deb ...
Unpacking libcoarrays-dev (2.0.0~rc1-2) ...
Selecting previously unselected package open-coarrays-bin.
Preparing to unpack .../5-open-coarrays-bin_2.0.0~rc1-2_amd64.deb ...
Unpacking open-coarrays-bin (2.0.0~rc1-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libgfortran-7-dev:amd64 (7.3.0-16ubuntu3) ...
Setting up libcaf-mpi2:amd64 (2.0.0~rc1-2) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up gfortran-7 (7.3.0-16ubuntu3) ...
Setting up gfortran (4:7.3.0-3ubuntu2) ...
update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f95 (f95) in auto mode
update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f77 (f77) in auto mode
Setting up open-coarrays-bin (2.0.0~rc1-2) ...
Setting up libcoarrays-dev (2.0.0~rc1-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
$ which caf
/usr/bin/caf
$ caf --version
OpenCoarrays Coarray Fortran Compiler Wrapper (caf version 2.0.0-rc1)
Copyright (C) 2015-2016 Sourcery, Inc.
OpenCoarrays comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of OpenCoarrays under the terms of the
BSD 3-Clause License.  For more information about these matters, see
the file named LICENSE that is distributed with OpenCoarrays.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-413876302,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL1apenPl5uX0gQnENQ9-7vlShbfSe55ks5uRs1KgaJpZM4WBlTF
.

--
Subrata Ray
Phone:  +91 33 24006625,<PHONE_NUMBER> (M)

Hi @srandroiddev
This is an issue for the ubuntu package maintainers. Are they putting a dependency on MPI that they used to install OpenCoarrays? It looks like no. Or that you uninstalled the MPI package.
What happens when you type which mpifort? You may need a sudo apt install OpenMPI (or MPICH) I don't know how they package it. Looking here it looks like open-coarrays-bin depends on libcaf-mpi2 which depends on libopenmpi2. I'm guessing that they need/should have open-coarrays-bin depend on openmpi-bin. I would guess that installing openmpi-bin would fix this for you. (sudo apt install openmpi-bin)
Also, for future reference we will be closing bug reports that do not fill out the bug report template without comment.
Thanks,
-Zaak

@amckinstry Any chance we could get the debian package for open-coarrays-bin to depend on openmpi-bin?
Thanks!

Yes.

I did the following. Now it works.
How to load opencoarray
sudo apt update
sudo apt install gfortran
sudo apt install open-coarrays-bin
sudo apt install libmpich-dev
sudo apt install libopenmpi-dev
Reboot
Create file a.f95
Program test
Print *, this_image()
End
Now compile and run
caf a.f95 -oa
cafrun -n 4 a
You should get 4 lines on the screen containing 1 2 3 4 ( may not be in
this order). n 4 specifies no of processors.
Subrata Ray
Phone: +91 33 24006625,  +918902683691(m)
On Fri, Aug 17, 2018, 10:03 PM zbeekman<EMAIL_ADDRESS>wrote:

Hi @srandroiddev https://github.com/srandroiddev
This is an issue for the ubuntu package maintainers. Are they putting a
dependency on MPI that they used to install OpenCoarrays? It looks like no.
Or that you uninstalled the MPI package.
What happens when you type which mpifort? You may need a sudo apt install
OpenMPI (or MPICH) I don't know how they package it. Looking here
https://packages.ubuntu.com/bionic/open-coarrays-bin it looks like
open-coarrays-bin depends on libcaf-mpi2 which depends on libopenmpi2. I'm
guessing that they need/should have open-coarrays-bin depend on
openmpi-bin. I would guess that installing openmpi-bin would fix this for
you. (sudo apt install openmpi-bin)
Also, for future reference we will be closing bug reports that do not fill
out the bug report template without comment.
Thanks,
-Zaak
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-413920533,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL1apRhbrJzSxlnck2c3rmHEkf9TC7yoks5uRvA7gaJpZM4WBlTF
.

I highly doubt you need libmpich-dev and libopenmpi-dev
On Sun, Aug 19, 2018 at 12:04 PM srandroiddev<EMAIL_ADDRESS>wrote:

I did the following. Now it works.
How to load opencoarray
sudo apt update
sudo apt install gfortran
sudo apt install open-coarrays-bin
sudo apt install libmpich-dev
sudo apt install libopenmpi-dev
Reboot
Create file a.f95
Program test
Print *, this_image()
End
Now compile and run
caf a.f95 -oa
cafrun -n 4 a
You should get 4 lines on the screen containing 1 2 3 4 ( may not be in
this order). n 4 specifies no of processors.
Subrata Ray
Phone: +91 33 24006625, +918902683691(m)
On Fri, Aug 17, 2018, 10:03 PM zbeekman<EMAIL_ADDRESS>wrote:

Hi @srandroiddev https://github.com/srandroiddev
This is an issue for the ubuntu package maintainers. Are they putting a
dependency on MPI that they used to install OpenCoarrays? It looks like
no.
Or that you uninstalled the MPI package.
What happens when you type which mpifort? You may need a sudo apt install
OpenMPI (or MPICH) I don't know how they package it. Looking here
https://packages.ubuntu.com/bionic/open-coarrays-bin it looks like
open-coarrays-bin depends on libcaf-mpi2 which depends on libopenmpi2.
I'm
guessing that they need/should have open-coarrays-bin depend on
openmpi-bin. I would guess that installing openmpi-bin would fix this for
you. (sudo apt install openmpi-bin)
Also, for future reference we will be closing bug reports that do not
fill
out the bug report template without comment.
Thanks,
-Zaak
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-413920533
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AL1apRhbrJzSxlnck2c3rmHEkf9TC7yoks5uRvA7gaJpZM4WBlTF
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-414137516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAREPGLiE3PFcpYnUh67pa4Vn0HtiVs-ks5uSYyJgaJpZM4WBlTF
.

I tested both with and without. Without those two dev packages opencoarray
does not work,  with the dev packages opencoarray works under ubuntu 18+
gfortran 7.
However, it may noted that the present version of opencoarray contains some
bugs.
Subrata Ray
Phone: +91 33 24006625,  +918902683691(m)
On Sun, Aug 19, 2018, 11:38 PM zbeekman<EMAIL_ADDRESS>wrote:

I highly doubt you need libmpich-dev and libopenmpi-dev
On Sun, Aug 19, 2018 at 12:04 PM srandroiddev<EMAIL_ADDRESS>wrote:

I did the following. Now it works.
How to load opencoarray
sudo apt update
sudo apt install gfortran
sudo apt install open-coarrays-bin
sudo apt install libmpich-dev
sudo apt install libopenmpi-dev
Reboot
Create file a.f95
Program test
Print *, this_image()
End
Now compile and run
caf a.f95 -oa
cafrun -n 4 a
You should get 4 lines on the screen containing 1 2 3 4 ( may not be in
this order). n 4 specifies no of processors.
Subrata Ray
Phone: +91 33 24006625, +918902683691(m)
On Fri, Aug 17, 2018, 10:03 PM zbeekman<EMAIL_ADDRESS>wrote:

Hi @srandroiddev https://github.com/srandroiddev
This is an issue for the ubuntu package maintainers. Are they putting a
dependency on MPI that they used to install OpenCoarrays? It looks like
no.
Or that you uninstalled the MPI package.
What happens when you type which mpifort? You may need a sudo apt
install
OpenMPI (or MPICH) I don't know how they package it. Looking here
https://packages.ubuntu.com/bionic/open-coarrays-bin it looks like
open-coarrays-bin depends on libcaf-mpi2 which depends on libopenmpi2.
I'm
guessing that they need/should have open-coarrays-bin depend on
openmpi-bin. I would guess that installing openmpi-bin would fix this
for
you. (sudo apt install openmpi-bin)
Also, for future reference we will be closing bug reports that do not
fill
out the bug report template without comment.
Thanks,
-Zaak
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<

https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-413920533

,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AL1apRhbrJzSxlnck2c3rmHEkf9TC7yoks5uRvA7gaJpZM4WBlTF

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-414137516
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAREPGLiE3PFcpYnUh67pa4Vn0HtiVs-ks5uSYyJgaJpZM4WBlTF
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/580#issuecomment-414144890,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL1apT3rezGydHCC4n8BFEZUkG5V3Opxks5uSamigaJpZM4WBlTF
.


as_array should not return a copy by default

Possibly add the parameter copy=False to as_array. This is only valid for the current DataContainer which is wrapping NumPy arrays.

actually it makes sense to return a copy by default as this would be the behaviour of any DataContainer not wrapping numpy arrays.


Can you write short doc about main features?

This is currently at an experimental stage and major API changes can jappen at any time, thus the lack of documentation. Now, since I'd appreciate some feedback on the direction people may want this crate to go, I think it is time the crate has some documentation indeed.

thanks a lot.


Why was the DCC ticketing feature implemented in the app, although the BfDI has not finished their audit yet?

Your Question
As announced in the blog post Corona-Warn-App simplifies certificate checks when booking tickets, since version 2.15, the app offers the so called DCC ticketing feature.
This feature was implemented in version 2.15, although the BfDI had and still has not finished their audit of this feature yet.
When asked on Twitter, why this was implemented, someone working at the BfDI responded:

Das müssen Sie den Herausgeber der Software fragen

As the development team is in close contact with the stakeholders (RKI/BMG), the following questions arise and could be internally clarified and then answered here:

Why was the DCC ticketing feature implemented in version 2.15, although the audit by the BfDI was not finished?
Was it a request by the RKI/BMG to implement the DCC ticketing feature in version 2.15 or was this brought up by the project team (SAP/T-Systems)?
Should the feature be removed from the apps again until the audit from the BfDI is finished?

@All, we are working on a statement about the approach to planning and implementing features in the app. Please keep in mind that our objective is to stay as up-to-date as possible with the app. However, development (including testing) will always lag behind the current decision-making process.
So, yes, we are aware that the released version may not always reflect national and/or regional rulings or dynamically changing decisions and recommendations of the authorities. Obviously, we will not and cannot implement and publish anything that has not been approved by the stakeholders and the necessary legislative authorities (including BfDI).However, in the interest of time, we try to parallelize some activities within the SCRUM approach. In rare cases, this may also lead to redundant coding, but in terms of risk assessment, we accept this risk to be able to ensure timely delivery.
Be assured, we will use the momentum and we are on track to cover the ongoing legislative amendments with the next versions of the app.
Please remain patient.

@GisoSchroederSAP Thank you for letting us know that you are working on a statement! Enjoy Friday & your weekend!

Closing as the DCC ticketing feature was put on ice: https://github.com/corona-warn-app/cwa-website/issues/2218#issuecomment-1094809124.


Add info in SUBSTRING entry's warning that SLICE may be a better choice than SUBSTRING

Not sure when the SLICE function was added.....or maybe I've just been overlooking it forever.  Regardless, it seems that the SLICE function doesn't throw an error when the StartIndex or EndIndex parameters are larger than the length of the text input parameter unlike SUBSTRING which does.
It would be helpful to either mention SUBSTRING has been deprecated in favor of SLICE, or at least mention the SLICE function in the SUBSTRING function and the same in reverse, please.

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

ID: 03aa9e88-7fa0-56ab-f794-58f0c37b6d7a
Version Independent ID: 25c5ef5c-6ba4-f5ff-f94b-8f2818ec2feb
Content: Reference guide for expression functions - Azure Logic Apps
Content Source: articles/logic-apps/workflow-definition-language-functions-reference.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@DTronD, thanks for reaching out with your feedback!
@RyZum, can you help address these questions from @DTronD? Thanks!

#assign:@ryzum

@RyZum, do you have a response for the feedback from @DTronD?

Thanks @DTronD for the feedback. Indeed Slice is a method we've added recently and decided to add support for negative parameters or parameters larger than the length of the original string.
For backward compatibility reasons, we have decided not to change the current substring function.
Thanks for reporting the issue, I'll add a section to the documentation of the substring function to mention that slice also exist. Please not that we are not deprecating substring but just providing an alternative way to do some string manipulation in a cleaner way.
Thanks again for your feedback.

@DTronD, thanks for your patience. The docs should be updated by 04/221/2022 after 11 AM Pacific Time. We'll close this issue now.
@MayankBargali-MSFT: #please-close


[Flutter Web] When pressing the Tab key in TextField, incorrect behavior occurs while Japanese IME composition mode is ON.

Steps to reproduce

Focus on a TextField.
Turn on Japanese Input Mode of IME.
Hit any characters. (eg. ああ)
Press Tab key.
[Bad Behavior] Composing mode is ends and the focus moved to the next TextField.

Environment: Chrome on Mac & Google Japanese Input
Flutter version: 3.19.6 (Stable), 3.22.0-16.0.pre.13 (Master)
Expected results
It becomes predictive text choice state.

Actual results
Characters are entered automatically and the focus moves to the next TextField.

Code sample
Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: Column(
          children: [
            TextField(),
            TextField(),
          ],
        ),
      ),
    ),
  );
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel master, 3.22.0-16.0.pre.13, on macOS 14.4.1 23E224 darwin-arm64, locale ja-JP)
    • Flutter version 3.22.0-16.0.pre.13 on channel master at /Users/ffunada/src/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision a9a556be29 (17 hours ago), 2024-04-23 07:11:33 -0400
    • Engine revision ffd3911b1f
    • Dart version 3.5.0 (build 3.5.0-89.0.dev)
    • DevTools version 2.35.0-dev.8

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/ffunada/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.86.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[☠] Connected device (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    ✗ Exception: Connected device exceeded maximum allowed duration of 0:04:30.000000
    •

[✓] Network resources
    • All expected network resources are available.

@huycozy Thanks for your reply! I'll follow the issue that you mentioned.


Please specify tensorflow version tested on the homepage.

I'm having trouble getting your code to work because of different tensorflow versions :
output = tf.nn.relu(inp) + tf.mul(alpha, -tf.nn.relu(-inp)) AttributeError: 'module' object has no attribute 'mul'
This is while testing to validate : https://github.com/davidsandberg/facenet/wiki/Validate-on-lfw
(And by the way it should be ~/datasets/lfw/ instead of ~/datasets/lfw/raw)

Fixed in 5725d9b7bad3c20b12c3965b4f4da0d296effd4f. Thanks!

Sorry, but the commit you linked to is not related to my issue in any way and I am still getting the issue after a pull today.

In order to see  if the issue is due to my tensorflow version, could you please run this for me to tell me your exact tensorflow version ?python -c 'import tensorflow as tf; print(tf.__version__)'  # for Python 2 python3 -c 'import tensorflow as tf; print(tf.__version__)'  # for Python 3

Sorry, the commit hash was supposed to be fbe15bf414164e6c5e9c13e14dc12d4d3944d30b (i.e. update of the readme file).
The TF version i'm using is r0.12, installed using pip. I will run the command for you this evening.
However, it looks like your problem is due to an API change in TF r0.12 and should be fixed by changing instances of tf.mul to tf.multiply.

Ok, great ! Trying right now. Thanks !

Well I was indeed a bit too up-to-date. This is working now, thanks.


Flip not working on IE 11.0.24 on Windows 10, v1511

The flip effect is working absolutely fine upto IE 11.0.22 in Windows 10 RTM 10240. But, after the November update of Windows 10, v1511, Build 10586, the effect is no longer working. Tested on many upgraded systems. Please check and fix / suggest patch.

There is a problem in Microsoft Edge too.

@MateEke, Nope, working totally fine in Edge on Windows 10 RTM 10240 and v1511, 10586.

The tile disappearing in the middle of the animation, but still better than in IE.
https://onedrive.live.com/redir?resid=91DC0784642EB42F!217591&authkey=!AJ8P3fNMNgFJP1Q&ithint=video%2Cmp4

There are z-index properties that could cause this...
Please have a look at the source... I would recommend experimenting a bit and telling us your findings.
The longer I'm working on this project, the more I begin to suspect that it is impossible to make a Flip script that works on all browsers without doing some tricks here and there based on in which browser we are running. So if you can find what is causing the problems, we can put in a feature-detect to get rid of the problematic code (or add some code) just for IE.
However I have no time to dive into this atm. We really need specific feedback. The best thing would be for you to fork this repo and create a Pull Request with your suggested changes. I'll promise to take the time to merge and release them if they are ok.

@sktnetwork @MateEke

@Download, here's how it looks on IE 11.0.24 on Windows 10 v1511.
http://screencast-o-matic.com/watch/coXqijhFRU
Tried, but could not find out the real reason. Maybe someone can help. Works find on Edge.

@sktnetwork  Ok, the behaviour on IE11 is different from Edge. In Edge it looks better but also gives a weird flicker at the end of the animation.
Can you try with different versions of Flip? You can easily grab older versions from CDN by changing the version number in the URL. E.G.:
https://cdn.rawgit.com/nnattawat/flip/v1.0.18/dist/jquery.flip.min.js
https://cdn.rawgit.com/nnattawat/flip/v1.0.17/dist/jquery.flip.min.js
https://cdn.rawgit.com/nnattawat/flip/v1.0.16/dist/jquery.flip.min.js
https://cdn.rawgit.com/nnattawat/flip/v1.0.15/dist/jquery.flip.min.js
https://cdn.rawgit.com/nnattawat/flip/v1.0.14/dist/jquery.flip.min.js
There have been some changes to the Flip behavior to fix other issues... One of these may have caused this. If we can find a version where it does work, we can look at the changes since then to narrow it down.

@Download , I have found out the problem but don't know the solution.

First, I tried v1.0.1 to v1.0.18. None of them work in IE11.0.24+ on Windows 10 v1511.
Second, I commented out this line number 139:
"backface-visibility": "hidden",
to
/"backface-visibility": "hidden",/

Doing this, it works half fine on IE11: Like this
http://screencast-o-matic.com/watch/coXqjDhFSf
The only problem now is that the back view changes after all animations are loaded. What should be the fix for this now?
I hope this helps.

The only problem now is that the back view changes after all animations are loaded.
Actually, that fixes the problem that is happening during the animation: The backface of the red side is showing during the turn and only after the turn completes is it hidden. The part where it is hidden after the animation is done with 'z-index'.
The backface-visibility rule is the one that is preventing the backface from showing, so given you disabled that rule the effect seen in the video is more or less what one would expect.
Flip uses three elements for it's card flip effect, Container, Front face and Back face. I would try to see if you can improve by setting the back-face rule only to the element that needs it to get rid of this issue.
I can't recommend much more than experimenting with the style rules to try to improve. If you do find a solution that makes it work in IE, we can then see if we can integrate that back into Flip.

Please try #43. I fixed an issue i was seeing in Edge there, but forgot to merge it.

https://github.com/nnattawat/flip/pull/43 has been merged

Still, I am facing this issue in IE. Flip effect is not working on any IE version in Windows 10.
Please fix this issue.

@pradeepjavac Reopened, but please know that this project is run by volunteers who are not getting paid to do this. So if you need a quick fix, you'll have to put in some work yourself.

This may be related to a bug reported in certain IE 11 builds here
It may be worth trying the example code and marking as reproducible if it is, and hopefully MS will take notice.

@Shinface, yes you're right. It's now IE 11.0.30 today, and the bug is still there. It's IE's and MS' fault but they are not going to fix it. In the bug report, MS has acknowledged the issue and is saying they won't fix it because it's fixed in Edge.
Sad state :(

@sktnetwork Can you link to that bug request please?

@JemarJones Here it is: https://connect.microsoft.com/IE/Feedback/Details/2474735

@Download @nnattawat If Microsoft has more or less dropped support for IE, should we as well?

That's what I did personally already. I don't bother testing my code for http://www.bridalapp.net on Internet Explorer anymore. I only occasionally test with Edge.
That being said, I did make an interesting discovery the other day that might end up being a fix for this issue...
I am working with React now and that doesn't mesh so well with jQuery, so when I needed a flip effect I couldn't turn to our beloved jQuery Flip. So I coded it by hand and had these flickering artifacts where the card faces would move 'through' each other. Then I discovered that I could get rid of them without resorting to the z-index declarations by using another z axis... The real 3D z-axis!
Currently, flip is doing this:
$dom.find($dom.data("front")).css({
  transform: rotateAxis + ($dom.data("reverse") ? "(-180deg)" : "(180deg)"),
  "z-index": "0"
});

$dom.find($dom.data("back")).css({
  transform: rotateAxis + "(0deg)",
  "z-index": "1"
});

But in my code for Bridal App, I am now doing this:
.mdl-card>.mdl-card__face.mdl-card__front {
	-webkit-transform: rotateY(0deg);
	transform: rotateY(0deg);
}

.mdl-card>.mdl-card__face.mdl-card__back {
	-webkit-transform: rotateY(180deg) translateZ(1px);
	transform: rotateY(180deg) translateZ(1px);
}

.mdl-card.is-flipped>.mdl-card__face.mdl-card__front {
	-webkit-transform: rotateY(-180deg);
	transform: rotateY(-180deg);
}

.mdl-card.is-flipped>.mdl-card__face.mdl-card__back {
	-webkit-transform: rotateY(0deg) translateZ(1px);
	transform: rotateY(0deg) translateZ(1px);
}

Note the translateZ(1px). This seems to work a lot better generally than the z-index. We could try this out with jQuery Flip maybe? It would be interesting if someone would test the flip effect on bridalapp.net with Internet Explorer to see if it indeed helps.


UAR-789: Patch roles and responsibilities

JIRA link
https://companieshouse.atlassian.net/browse/UAR-789
Change description
Mapping roles and responsibilites to an empty string until API is update to bring back correct data.
Work checklist

[ ] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

@joshuahigginsonCH will ping you about this PR as I am not sure on this fix


Add github api key for sources.

Rate limit error with sources page where we use the github API. Error prevents page from displaying.

Provide an API key to fix.
Localize error to sources date info area.

@candicecz does this issue still need to be addressed?


Avoid to print a warning for each sensor tag in loaded URDF file

Fix https://github.com/ami-iit/ADAM/issues/59 .

Thanks a lot @traversaro!


Refactor Cargo features

Summary

Refactor the Cargo features to provide a better, more fine-grained structure.
Separate the features for selecting pins from the features for selecting peripherals.
Reorganize and better document the Cargo.toml file.

NOTE: Reviewers will probably want to read through the entirety of Cargo.toml, but the rest of the changes will probably be overwhelming to review. Everything builds, but none of this is tested on hardware, since I don't have any hardware to work with at the moment.
Checklist

[ ] CHANGELOG.md for the BSP or HAL updated
[x] All new or modified code is well documented, especially public items
[x] No new warnings or clippy suggestions have been introduced (see CI or check locally)

@sajattack had a suggestion on Matrix:

maybe some of the gpio features could be called min-pb00 instead of just pb00
just thought of that, since I was a bit confused until I read the comment

I responded, but I realized that discussion should really stay in the PR, so I'm copying my response here.
@sajattack, here was my thought process for feature naming:

I wanted to create feature "namespaces" using prefixes. That's how I came up with pins- and periph-.
However, using a periph- prefix for every single peripheral is extremely verbose, e.g. periph-sercom0, periph-tcc0, etc..
For peripherals with no possible confusion with a user feature, I just named it the most natural thing, e.g. sercom0, tcc0, etc.
For peripherals with a possible name collision, I appended a p to the user-selectable version, e.g. usb and usbp.
I originally had the pb00 feature within the pins- namespace as pins-pb00. But I thought a specific pin is akin to a specific peripheral, which does not have the namespace prefix, so I removed it.

Questions for you:

Do you have any broad feedback on this scheme?
What was the min- prefix supposed to convey in your suggestion?
Do you think I should change back to pins-pb00? Or use something else, like min-pb00?
If I change pb00, should I also change the peripheral features?

I just had a philosophical realization. You say:

I was a bit confused until I read the comment

Several times recently, both at work and outside of work, people have effectively told me:

This wasn't intuitive to me, and it didn't make sense until I read the documentation.

While I agree that we should try to make things as intuitive as possible, sometimes things can't be made intuitive, either because the motivation is too complicated & subtle, or because people's intuitions don't match. At some point, I think the solution has to be "Read the documentation". But exactly where that happens is debatable.
Where do you think this situation falls? Would adding min- make things more intuitive to everyone? Or is it only intuitive if you're already familiar with our prior min-samxxx features?

Questions for you:
* Do you have any broad feedback on this scheme?

Not really, it seems reasonable enough

* What was the min- prefix supposed to convey in your suggestion?

Similar to min-samd51g, it conveys that it includes pb00, and everything up to it

* Do you think I should change back to pins-pb00? Or use something else, like min-pb00?

Honestly I'm not too fussed about it, it was just an idea that came to me

* If I change pb00, should I also change the peripheral features?

The -p ones are a little unintuitive as well

I just had a philosophical realization. You say:

I was a bit confused until I read the comment

Several times recently, both at work and outside of work, people have effectively told me:

This wasn't intuitive to me, and it didn't make sense until I read the documentation.

While I agree that we should try to make things as intuitive as possible, sometimes things can't be made intuitive, either because the motivation is too complicated & subtle, or because people's intuitions don't match. At some point, I think the solution has to be "Read the documentation". But exactly where that happens is debatable.

Part of the problem in this instance, is that, in doing a full code review, I see pb00 in multiple places, but the documentation is only in one of them. That's where an intuitive name has benefits over documentation.

The -p ones are a little unintuitive as well

Yeah, I'm not a huge fan of it either, but I didn't come up with anything better at the time.

Similar to min-samd51g, it conveys that it includes pb00, and everything up to it

My hesitance comes from the fact that this statement isn't quite accurate. Pins aren't strictly additive. The best example is pin PA28, which I had to make special accommodations for. PA28 is included in the 48 and 64 pin packages for D21 chips, but it's not present in the same packages for D51 chips.
While thinking about your responses, I had an idea. What do you think of using a has- prefix for all individual pin & peripheral features, e.g. has-sercom0, has-tcc0, has-pb00, etc. It's more verbose, but I think it communicates exactly what is meant by the feature. Then, the pins- and periph- namespaces would exist to group has- features into reusable sets.

The -p ones are a little unintuitive as well

Yeah, I'm not a huge fan of it either, but I didn't come up with anything better at the time.

Similar to min-samd51g, it conveys that it includes pb00, and everything up to it

My hesitance comes from the fact that this statement isn't quite accurate. Pins aren't strictly additive. The best example is pin PA28, which I had to make special accommodations for. PA28 is included in the 48 and 64 pin packages for D21 chips, but it's not present in the same packages for D51 chips.
While thinking about your responses, I had an idea. What do you think of using a has- prefix for all individual pin & peripheral features, e.g. has-sercom0, has-tcc0, has-pb00, etc? It's more verbose, but I think it communicates exactly what is meant by the feature. Then, the pins- and periph- namespaces would exist to group has- features into reusable sets.

Sounds like a good idea.

has- eliminates both problems in my mind, so I'm not sure why your last sentence mentions pins- and periph-

The pins- and periph- prefixes would still exist to group together other features. The periph- features would only exist in the Cargo.toml file, so there shouldn't be any confusion there. But the pins- features would be in the code as well (as they are right now). Since you didn't comment on the pins- features, I take it they were self-explanatory enough.
I'll rename the features and push an update.

@sajattack, the scripts I modified were definitely very brittle. They used something that was TOML-aware for reading fields, but they still modified the contents of the file by hand. I'm not quite sure why. My guess is that the Python toml library doesn't preserve style and comments, so a round-trip read & write would not yield the same file. The new TOML library I used is fully capable of a round-trip without modifications.
I guess we'll just see what happens. If we run into errors when trying to release, we can fix things then.


When will live reload of certificates be supported?

Hello,
Live reload of certificates is a critical feature in our telco application where certificates are renewed frequently. I see this feature is planned for future but can you state approximate when in time this will be available?
We currently use Spark Java where this is possible to achieve by implementing the spark.embeddedserver.Embeddedserver interface. Does Javalin provide anything similar as a temporary workaround until this feature is released?

The feature is present as part of the 5.3.0 release of javalin/javalin-ssl.
Unfortunately we're having some trouble publishing to Maven central, as soon as we get that sorted I'll publish it. We're expecting a ticket response in the following days, I estimate it should be out by the end of the week.
You can subscribe to release notifications on the plugins repo if you want.


Grant the service account twice

No big deal, but on section 6 the command gcloud kms keys add-iam-policy-binding is repeated twice unnecessarily

Hi @Streppel
Thanks for opening an issue. I'm not sure I understand what you mean though. Can you link to a specific point in the code?
There are only two calls to add-iam-policy-binding in the entire repo - one on the project and one on the KMS key.

@sethvargo Oh, I'm sorry! I'm looking at https://codelabs.developers.google.com/codelabs/vault-on-gke/, more specifically at https://codelabs.developers.google.com/codelabs/vault-on-gke/index.html#5.
This is what I see:

Also, thanks for the quick reply! :)

Fixed


Link to ESMValTool diagnostic scripts and recipes from recipe documentation pages

If we linked directly to diagnostic code and recipes from each recipe documentation page, this would better support traceability of published results. E.g. a scientist who is not familiar with ESMValTool would be able to find the relevant code more easily*.
Ideally, a given version of the recipe documentation would link to a specific revision in the repository. But if that is unfeasible, then even linking to latest revision would be a step forward.
(*) Assuming that they can find the appropriate recipe document page in the first place, but that is another issue (#3260).
Would you be able to help out?
I will make the time, and possibly have the skills (depending on solution chosen) to implement this.

Some straightforward options that are possibly within my skill set:

If we assume that filenames for diag scripts and recipes are unique, then it would be easy to write a script that would convert all .yml, .py, .ncl, ... file names to links, using find on a local repository clone to identify the relative paths. If that is not a safe assumption then either...
Also use the paths that are listed in the recipe documentation and combine with the filenames. This seems risky since it would require some assumptions to be made, and some differences in approach (see e.g. "and subroutines" in blocking).
Or just turn directory paths into URLs, and a reader can cross reference the filenames listed against those in the directory. E.g.

Diagnostics are stored in [diag_scripts/miles/](https://github.com/ESMValGroup/ESMValTool/tree/main/esmvaltool/diag_scripts/miles)

@ESMValGroup/technical-lead-development-team @ESMValGroup/scientific-lead-development-team does anyone have views on the above options, or has a better idea.
Would also welcome any ideas about linking to specific revisions of the code. Does readthedocs support this? I think @zklaus mentioned something that might be relevant here?

Ahah, @zklaus has found a solution for using Sphinx roles with recipes, which would solve the versioning question: #3264. Other questions above are on hold pending some further investigation.


configuration provider for cpptools / IntelliSense

Hi,
it would be awesome if this extension would serve as a configuration provider for cpptools / IntelliSense.
Most importanly provide the include paths for all the consumed conan packages dynamically.
Docu: https://github.com/Microsoft/vscode-cpptools-api#readme
Example: https://github.com/microsoft/vscode-cmake-tools/blob/develop/src/cpptools.ts
Cheers

Thank you for this input. We will have a look into it and it would be a great addon to our Plugin.

Thank you for this input. We will have a look into it and it would be a great addon to our Plugin.

I'd say this is currently the biggest productivity blocker for me when using VS Code and Conan together. Do you know any workaround that's possible today that let's you use IntelliSense correctly with headers from Conan dependencies?
I tried a few things a while ago, also with this (no longer maintained) alternative plugin. If I remember correctly, I could partially get it to work but some manual configuration of include paths was needed and it wasn't easy to set up.
If this plugin could make that process automated and works stable for both Conan packages in the cache and editable packages, that would be a big step forward in improving the Conan experience in VS Code!

Here is one way that seems to work to get IntelliSense for Conan dependencies. It is assumed that you build manually using conan source, conan install, conan build inside a folder called build in your workspace folder. It is also assumed that you use CMake to build your project.

In conanfile.py, adapt your build() function to enable the CMake option CMAKE_EXPORT_COMPILE_COMMANDS. E.g.:def build(self):
    cmake = CMake(self)
    cmake.definitions["CMAKE_EXPORT_COMPILE_COMMANDS"] = "ON"
    cmake.configure()
    cmake.build()
    cmake.test()

Build your project. E.g.:mkdir build
cd build
conan install ..
conan build ..

The file build/compile_commands.json should have been generated now.
In VS Code, press Ctrl+Shift+P and run command C/C++: Edit Configurations (JSON). Add a new property compileCommands to the default configuration that points to the generated compile_commands.json file:{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "windowsSdkVersion": "10.0.18362.0",
            "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.28.29333/bin/Hostx64/x64/cl.exe",
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "windows-msvc-x64",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json"
        }
    ],
    "version": 4
}

You may also want to check and adapt the other attributes in the configuration, in particular includePath. IntelliSense will fall back to the search paths specified there when you e.g. create a new source file that is not listed in compile_commands.json.
Saving the C/C++ configuration.

You should now be able to get IntelliSense for functions/types defined in Conan dependencies.
When you create new source files or add/change Conan dependencies, make sure to rebuild your project so that compile_commands.json gets updated. However, I haven't found an easy way to make IntelliSense reload the compile_commands.json apart from e.g. closing and reopening the folder in VS Code.

@chausner. Currently I am using the same approach as you mention, with exporting compile_commands.json from CMake. But I agree it would be a great help to integrate cpptools into the conan plugin. It will be my next task.

CMAKE_EXPORT_COMPILE_COMMANDS is not supported by the default Visual Studio generator on Windows. A workaround that I have found is to change the generator to Ninja which ships with Visual Studio. See https://docs.conan.io/en/latest/integrations/build_system/ninja.html.


Add resource subtype to masthead v2

Weirdness with the old PR made me close that but for ref here it is
Some resources like Service and Secret have a type (service) but also a Subtype (ClusterIP). This exposes the mechanism to set that from the resource.
@vincent99 @lvuch Would it make sense to change create to match edit now?
rancher/dashboard#1073

Yes create should be consistent as well, and view/detail.
Linking all of "Edit LoadBalancer Service" seems like a bit much, and linking the verb is confusing (click the word "Edit" go to back).
I think all should either be:
{type}: {Create|Edit, empty for view} {subtype if applicable} {name if edit}
[Secret]: Create
[Secret]: Edit foo
[Secret]: foo

[Service]: Create ClusterIP
[Service]: Edit ClusterIP foo
[Service]: ClusterIP foo

or
{subtype if applicable} {type}: {Create|Edit, empty for view} {name if edit}
[Secret]: Create
[Secret]: Edit foo
[Secret]: foo

[ClusterIP Service]: Create
[ClusterIP Service]: Edit foo
[ClusterIP Service]: foo

And lean towards the former, since clicking on the link part brings you to a list of all types, not just ones of that subtype.

@vincent99 Opted for the former as well.


Add fix for masking IDP properties in IDP flow

Description
Need to port this fix from IS 6.0.0 to APIM.
Affected Component
APIM
Version
4.2.0-SNAPSHOT
Related Issues
No response
Suggested Labels
No response

Update : PR https://github.com/wso2/carbon-identity-framework/pull/4366 already sent. Waiting for approval from the IS team.

Update : This PR was merged. Release is done. And the identity version in carbon-apimgt and product-apim are upgraded.


Unlock Immediately bug

The Unlock Immediately feature makes the animation incomplete and it only unlocks if I press the home button.

That feature is meant to be used when you have touch-home-to-unlock turned on.


Incomplete pattern matches problem with True/False

Because True and False are treated as literals, they are assumed to be infinite like all the other literals like ints, floats, chars, and strings. They are not though.
-- MISSING PATTERN ---------------------------------------------- ./src/Http.elm

The following `case` does not handle all possible inputs.

430│>  case 200 <= response.status && response.status < 300 of
431│>    False ->
432│>        fail (BadResponse response.status response.statusText)
433│>
434│>    True ->
435│>        case response.value of
436│>          Text str -> handle str
437│>          _ -> fail (UnexpectedPayload "Response body is a blob, expecting a string.")

The following patterns are not being handled:

    <values besides: False True >

Did you add a new tag to a union type? Add how it should be handled here and
you will be all set!

Not sure how to resolve this right now.

I guess that a workaround would be something like:
case 200 <= response.status && response.status < 300 of
   False ->
       fail (BadResponse response.status response.statusText)

   _ ->
       case response.value of
            Text str -> handle str
            _ -> fail (UnexpectedPayload "Response body is a blob, expecting a string.")

But I don't mean to say that that is ultimately desirable :-)

I already did a different workaround, but I think this in unacceptable as is. The actual fix is quite tricky and depends on a lot of internal compiler details, so I want threads like this to stay focused on that kind of stuff.


rubygems ownership

per https://rubygems.org/gems/sensu-plugins-microsoft-teams it does not look like ownership of the gem has been given to the community. Can you please run gem owner sensu-plugins-microsoft-teams -a<EMAIL_ADDRESS>

done.


Mobile navigation doesn't show the context switcher for user / team

Describe the Bug
The desktop view shows a dropdown to switch context to a Team or user, but it doesn't show up on mobile.

Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
2.11.1
Which browser are you using? (if relevant)
Chrome
How are you deploying your application? (if relevant)
No response

Do you know what mobile device you are on? I can't seem to reproduce the issue. You should be able to see an icon to switch team context on mobile devices.
https://github.com/umami-software/umami/assets/31608805/55ed5b75-9334-4a8a-b84b-8ababa243fcb

Sorry should have added that. I'm on an iphone 12 with google chrome.

Can you verify you are running the latest version? Websites should now have the visits metrics which is missing from your screenshot.

You're right, @franciscao633. I tried pulling the docker image again and this time it is showing the context button. Thank you for helping out. 🙂


Allow display of single node topologies

Fixes https://github.com/twitter/heron/issues/976
Example:

@cckellogg can you have a look at this PR?

👍


VTK8: confirm obj rebaselines

Have a look at these results http://portal.nersc.gov/project/visit/tests/20181025-08:47/pascal_trunk_serial/obj_box.html I am wondering if the thick mesh lines are a problem in VTK we're using on trunk
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3255
Status: Pending
Project: VisIt
Tracker: Bug
Priority: High
Subject: VTK8: confirm obj rebaselines
Assigned to: -
Category: -
Target version: 3.0
Author: Mark Miller
Start: 10/25/2018
Due date:
% Done: 0%
Estimated time:
Created: 10/25/2018 08:45 pm
Updated: 10/30/2018 06:50 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: trunk
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Have a look at these results http://portal.nersc.gov/project/visit/tests/20181025-08:47/pascal_trunk_serial/obj_box.html I am wondering if the thick mesh lines are a problem in VTK we're using on trunk
Comments:

I didn't see any thick mesh lines, but I saw some extra mesh lines and I believe it is because a face of the cube is missing in 3.0.0b. I rotated it around and 5 of the 6 sides are present. Here are the images from 2.13.3 and 3.0.0b. The image from 3.0.0b is on top.

Here is the script that generates the image.
obj_test.py.txt

I suspect the thick mesh lines I am (still) seeing are related to X windows issues. When I kill and restart my X server on OSX, I get different behavior. It seems like aliasing can get turne on somehow but this behavior is intermittent and the same X server execution instance will vary in behavior from run to run. Might be ok to reject/close this.

I've taken a closer look at this. Indeed the missing face is the correct behavior for the case tested here which turns off all SIL sets except box, which is the union of 5 of the boxes 6 faces. I ran all tests on my OSX system and they agree (not bit-for-bit but don't expect that either) with the current baselines.


Fixes #281, default attribute for ssl_protocols

This commit adds a default-precedence attribute for SSL protocols to be defined and consumed by others who use this cookbook. One would use this in a config template:
ssl_protocols <%= node['nginx']['ssl_protocols'] %>;

Should be closed in favour of #306