Always decoding, even with random string

var sqids = new SqidsEncoder<long>(new SqidsOptions { Alphabet = _sqidAlphabet });
return sqids.Decode(sqid);

This code always decode, even with random string. But the playground returns Error: Invalid ID with the same string. Am I doing something wrong or missing a very primitive concept?

Behind the scenes, the playground is simply doing id == encode(decode(id)) and if it's not equal, it'll output a user-friendly error.
More info: https://sqids.org/faq#valid-ids

@espindl  Also note that this has been explained in the README here.

Yeah, thank you and sorry I missed this in both faq and readme @aradalvand @4kimov


services/horizon/internal: Fix index out of range for requests with empty named url params.

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Fix index out of range for requests with empty named url params #1965
Why
Making a request without passing the named URL params can cause the following error
runtime.boundsError runtime error: index out of range [0] with length 0

This happens because of the way chi processes named params, if you don't pass the require segment, they match against the right URL, but don't push anything in the URL values. This seems like a bug in chi and someone already reported it https://github.com/go-chi/chi/issues/426
This PR fixes our param reader to return early if the number of Keys doesn't match the number of Values in the URLParams and adds regression tests for it.
While fixing this I also added some extra hardening to the account offers action to have proper validation for account_id and use better error messages.
Known limitations
[TODO or N/A]

@bartekn agree. I subscribed to the issue on chi, so we'll know when it gets fixed or there is more info about it.

hey guys, author of chi here. we uses slices instead of map for performance reasons when building the matching pattern, its been highly optimized. I'll look into this bug though, as it theoretically should never happen as even if the parameter key isn't passed, it should result in an empty param value.


Incorrect reformatting of comments

Formatting this (comment inside ()):
let x =
    ((*comment*))
    printf "a"
    // another comment 1
    printf "b"
    // another comment 2
    printf "c"

results in the following (comment text doubled and another comments in the file are placed between two comment copies):
let x =
    ((*comment*) // another comment 1
                 // another comment 2
                 (*comment*))
    printf "a"
    printf "b"
    printf "c"

Repeated reformatting will double all text in the comment.

Please, report the issue to Fantomas repository https://github.com/dungpa/fantomas/issues. VFPT uses it to make cod format.

done: https://github.com/dungpa/fantomas/issues/204


Gotcha: component style custom properties are transformed from camel case to kebab case

See here.

(Copied text so it's easier to keep an eye on from a distance)
toonddd — 09/12/2022
Astro automatically transforms component style object custom properties from camel case to kebab case.
What is the original reason/benefit for doing so?
From my current perspective it looks unnecessary and even confusing, added complexity.
nate (he/him) — 09/12/2022
Ah this is a good point! Nobody has ever brought this up as a pain point before, so I think we're stuck with it for v1.0, but it could certainly be a breaking change in the future! CSS custom properties are usually --kebab-case but there's no technical reason they can't be --camelCase

Would love to make this my first Astro contribution!
Are we wanting to add this as a 'Gotcha'/good-to-know part of the docs?
If so, I can put something together for it. Please assign to me! Thanks!

On a roll today with the contributions, @WintrCodes!  🚀
Sure, let's start by thinking of this as one of those "gotchas" for the Troubleshooting page! Depending on what you come up with, there may end up being a different fit, but I think thinking of it as troubleshooting advice makes a lot of sense to start.

This behavior no longer seems to occur. See Stackblitz: Kabab case stays as kabab case.

Here's a first draft!
Gotcha: --camelCase transformed to --kebab-case
If you attempt to override CSS variables by including them in your HTML using style object custom properties, do note that anything written in --camelCase will be transformed to --kebab-case. See the example below.

Astro

In this example, style={{ '--cssVariable': 'brown' }} will be transformed to style="--css-variable:brown", however style="--anotherVar: blue" does not get transformed.


Added new region eastus2euap to Azure staticRegionToZones

Change Overview
Added new region eastus2euap to Azure staticRegionToZones
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[x] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues
Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

@pavannd1 - lets kueue this ?


feat: Target Android 12 and build on VS2022

GitHub Issue: #
PR Type
What kind of change does this PR introduce?

Bugfix
Feature
Code style update (formatting)
Refactoring (no functional changes, no api changes)
Build or CI related changes
Documentation content changes
Other... Please describe:

Description

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Interface members are XML documented
[ ] Documentation (XML or comments) has been added and/or existing documentation has been updated
[ ] Architecture documents have been updated
[ ] Tested on all relevant platforms

Other information

Internal Issue (If applicable):

If packages updates are required, you should do a PR with only those.
You could then upgrade the targets in another PR.


Sum of elements with k-set bit indices

Sum of Values at Indices With K Set Bits
You are given a 0-indexed integer array nums and an integer k.
Return an integer that denotes the sum of elements in nums whose corresponding indices have exactly k set bits in their binary representation.
The set bits in an integer are the 1's present when it is written in binary.
For example, the binary representation of 21 is 10101, which has 3 set bits.

Input: nums = [5,10,1,5,2], k = 1
Output: 13
Explanation: The binary representation of the indices are:
0 = 0002
1 = 0012
2 = 0102
3 = 0112
4 = 1002
Indices 1, 2, and 4 have k = 1 set bits in their binary representation.
Hence, the answer is nums[1] + nums[2] + nums[4] = 13.


Separate codebases and docs of Envoy Gateway

Description:
After releasing v0.3.0, I have a worry for doc release. The current logics of doc releasing, cutting off docs in every release, this is a common versioned doc solution same as envoy website.
But compared with the envoy-website, envoy-website separates envoy codebase and its docs, but eg is not and the docs repeatedly increases and gets larger and larger. It will break the structure of our repo, we repo will contain many docs because we will copy/paste/update it every release.
For a long way, I suggest separate docs with our codebases, like open another separated repo for managing eg docs.
cc @mattklein123

Sorry I'm having trouble parsing ^. I would do whatever makes sense for the project documentation wise.

I'm in favor of separating the docs. I think the question is when to do this and the priority level of the work. The other option is that docs are published only for latest and the latest tagged release, e.g. v0.2.0. Thoughts?

agree that the split is needed, might make more sense to do it in the future when we have dedicated owners for components (like docs), for now keeping it in this repo ensures that the content can be reviewed by the reviewers of this repo

@Xunzhuo during today's community meeting, concern was expressed about this issue. I have moved this to the backlog until these concerns are resolved.

I'd vote for leaving the docs and the code in the same repository as long as possible, actually, in line with @arkodg's comment above.
While I was at Ambassador Labs, we wrestled with this quite a lot for various reasons, and even flipped between separate repos and the same repo a couple of times. Overall, my experience has been that having code and docs in the same repo is a huge win for the developers (who benefit tremendously by being able to update code and docs in a single PR), and having them in a separate repo is really only a win if you have a separate (less-comfortable with Git) team working only on documentation.
In the case of Envoy Gateway, I don't see a separate docs-only team happening in the near future, so I'd vote strongly for making the devs' lives easier by keeping everything in the same repo.

FWIW I'm +1 on @kflynn comment, though I would support whatever the team wants to do.

Echoing @kflynn, I'm more in favor with keeping in docs and code in the same repository. In my experience I find it's way easier to keep code and docs in sync when its in the same repo since you can update docs in the same PR as the code change and its something that can be enforced in code review.

Maybe what we need is a new website generator that supports fetching sources from different git branches.
Currently, the generator will iterate all docs directories: https://github.com/envoyproxy/gateway/blob/main/tools/make/docs.mk. That's why the docs from the old releases need to be kept in the main branch.
Another solution is to rewrite the current generator to clone this repo from release branches, so the multiple versions of docs will be just built artifacts.

based on the comments in this GH issue, closing this for now


Feature/typehints

After merging, can you release via make raise_and_release_minor_version: please? (But not sure if the make command works correctly on MacOS as some of the commandline-tools sometimes differ slightly)

Or anyway, I will merge quickly, hope that is okay.


at-odds information in docs about webjob types

This page says, https://docs.microsoft.com/en-us/azure/app-service/webjobs-dotnet-deploy-vs#webjob-types
"Triggered (default): A triggered WebJob starts based on a binding event, on a schedule, or when you trigger it manually (on demand). It runs on all instances that the web app runs on, but you can optionally restrict the WebJob to a single instance"
but in this page,
https://docs.microsoft.com/en-us/azure/app-service/webjobs-create#webjob-types
it says under triggered, "Runs on a single instance that Azure selects for load balancing."
and continuous says, "Runs on all instances that the web app runs on. You can optionally restrict the WebJob to a single instance."
Which one is correct?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2b7b9f5c-4610-8cea-28d4-fea8ea03e7e1
Version Independent ID: cc09b46d-cd40-45e8-ed45-7a0e3bf4b100
Content: Develop and deploy WebJobs using Visual Studio - Azure App Service
Content Source: articles/app-service/webjobs-dotnet-deploy-vs.md
Service: app-service
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @kayesmith94 , thank you for the detailed question. We are currently investigating and will update you when we have accurate information to provide.

@kayesmith94, I've made a PR to correct the doc to stating triggered jobs runs a on single instance. It does not scale out with web app instances.


Add  for social share

Hi! Thanks for taking the time to contribute! Could you please provide a description of your changes? It's easier on the maintainers and better for those who reference this pull request in the future. Thanks!

Sorry!  I forgot wrote description.
Those meta tags display the card when it is shared by twitter and facebook.
And  changes tab color only on Android Lollipop, Chrome.

Super awesome, thank you @RacioN!


Errors when running Phi-3 on NVIDIA CUDA with onnxruntime_genai

Hey all, I am trying to run Phi-3 on NVIDIA CUDA following the steps listed here (https://onnxruntime.ai/docs/genai/tutorials/phi3-python.html#run-with-nvidia-cuda), I was able to install the pip package successfully by running the command pip install --pre onnxruntime-genai-cuda --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/, but when I run the inference file with python phi3-qa.py -m cuda/cuda-int4-rtn-block-32, I got the following errors (note that the xxx in the paths in the error logs are just blurred out information for privacy reasons):
Traceback (most recent call last):
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\onnxruntime_genai\__init__.py", line 11, in <module>
    from onnxruntime_genai.onnxruntime_genai import *
ImportError: DLL load failed while importing onnxruntime_genai: The specified module could not be found.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\xxx\xxx\xxx\onnx_test\phi3-qa.py", line 2, in <module>
    import onnxruntime_genai as og
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\onnxruntime_genai\__init__.py", line 14, in <module>
    from onnxruntime_genai.onnxruntime_genai import *
ImportError: DLL load failed while importing onnxruntime_genai: The specified module could not be found.

I would really appreciate any insights or solutions to this issue. Thanks for your time and help in advance!

Could you please share your cuda environment? onnxruntime-genai-cuda requires cuda 11.8 to be installed. The python package expects that the system variable CUDA_PATH is set to the binary directory in your cuda toolkit folder.
From your error message, my guess is that python is not able to locate your CUDA binaries.
Example from my machine:

Hi @baijumeswani , thank you very much for your fast reply! Here's my environment, do I have to install CUDA 11.8 or is onnxruntime-genai-cuda backward compatible with CUDA 12.1 (which I have installed)?

Hi @baijumeswani , thank you very much for your fast reply! Here's my environment, do I have to install CUDA 11.8 or is onnxruntime-genai-cuda backward compatible with CUDA 12.1 (which I have installed)?

You need to have cuda 11.8 installed. We are yet to release cuda 12 packages.
If installing cuda 11.8 is not feasible, you could build from source. Here are instructions on building from source: https://onnxruntime.ai/docs/genai/howto/build-from-source.html

I see, thanks for the clarification!

Do you by chance know the timeline on the release of the cuda 12 packages?
Do you also by chance have containers that you can share for building the packages? I would really appreciate it!

I see, thanks for the clarification!

Do you by chance know the timeline on the release of the CUDA 12 packages?
Do you also by chance have containers that you can share for building the packages (especially for building the pip package that's compatible with CUDA 12 on Linux)? I would really appreciate it!

A follow-up to these questions. Thanks!

Do you by chance know the timeline on the release of the CUDA 12 packages?

We are planning to add cuda 12 packages for the next release (0.3.0). Probably in the next 2-3 weeks.

Do you also by chance have containers that you can share for building the packages (especially for building the pip package that's compatible with CUDA 12 on Linux)? I would really appreciate it!

We do not have any managed containers that I can share for building onnxruntime-genai-cuda. You could try looking for cuda containers here.

Hi @baijumeswani, thank you very much for your reply and update! Really looking forward to the 0.3.0 release!

Hi @baijumeswani, a quick follow-up to this, is there any update regarding a 0.3.0 release candidate that supports CUDA 12? Thanks for you guys' great work again!

@jackylu0124 the cuda 12 pipeline is almost ready. We still are working on fixing a couple of blockers before we can release 0.3.0. But my best estimate at this point is that we will be publishing the 0.3.0 package sometime this week.

@baijumeswani Got it, thank you so much for you guys' work again! Really incredible work! Can't wait to try it out!

@baijumeswani What is the CuDNN version required?

Hi @baijumeswani, just a quick follow-up to the message above, thanks!

Hi @baijumeswani, I see that v0.3.0 has been released, but I tried installed the CUDA version with the command pip install onnxruntime-genai-cuda --pre --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/, and I still see the same error reported above when I ran the sample script. Do you by chance know when I will be able to download and install the CUDA 12 compatible version?
Thanks a lot for again!

Hi @jackylu0124 sorry for the delay in responding. We ran into some trouble releasing the cuda 12 binaries dur to packaging problems.
I am working on having the package out today.

Hi @baijumeswani, thank you very much for the fast reply and update! I am looking forward to trying it out, thanks for the great work you guys are doing as always!

Hi @baijumeswani, sorry for bothering you again, is there any update on when the CUDA 12 compatible package will be avaibable? Thanks!

Ok, finally the cuda 12 packages were published:
Python:
pip install -i https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/pypi/simple/ onnxruntime-genai-cuda

Nuget: you can add this to your nuget.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="onnxruntime-cuda-12" value="https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/nuget/v3/index.json" />
  </packageSources>
</configuration>

C/C++ API: Packages uploaded to:
https://github.com/microsoft/onnxruntime-genai/releases/download/v0.3.0/
Requirements are cuda 12 and cudnn 9.

Hi @baijumeswani , thank you so much for the update and release! I really appreciate it and will try it out in a bit.
For the Python one, do I need to use the --pre flag in pip install like the example command pip install onnxruntime-genai-cuda --pre --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/ as shown on https://onnxruntime.ai/docs/genai/howto/install.html?
Thanks a lot again!

--pre is needed only for pre release versions. For the stable release such as 0.3.0, you do not need the --pre.

Got it, thanks for the clarification!

Hi @baijumeswani, thank you for the great work! I tried out the CUDA 12 package on my Windows machine and it works as expected. I have two follow-up questions:

If I want to install that particular CUDA 12 compatible onnxruntime-genai-cuda version that's just released (when I build my Docker container) for example, do I just do pip install -i https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/pypi/simple/ onnxruntime-genai-cuda==0.3.0 because that URL will be re-used for future version releases?
Regarding loading the quantized CUDA model with og.Model(), do I only need to keep the Phi-3-mini-4k-instruct-onnx/cuda/cuda-int4-rtn-block-32 folder, and can I remove the Phi-3-mini-4k-instruct-onnx/cpu_and_mobile, Phi-3-mini-4k-instruct-onnx/directml, and Phi-3-mini-4k-instruct-onnx/cuda/cuda-fp16 folders in order to save some space during deployment?

Thanks a lot for all the help again!

Hi @jackylu0124

Yes, this index url will be reused for future onnxruntime-genai-cuda python packages for cuda 12. If you want only version 0.3.0, you can use ==0.3.0.
For deployment, please only keep the model that you need for og.Model(...). If you want to only use the cuda-int4-rtn-block-32 model, you do not need to deploy any of the other models.

I'll close this issue now. Please feel free to add more comments or questions.

hi @baijumeswani
i am creating docker images using following command in the docker files
FROM nvidia/cuda:12.0.0-runtime-ubuntu20.04
RUN apt-get install libcudnn9-cuda-12 libcudnn9-dev-cuda-12
RUN pip install --pre onnxruntime-genai-cuda --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/
but not able to create the images
3.057 Looking in indexes: https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/
3.596 ERROR: Could not find a version that satisfies the requirement onnxruntime-genai-cuda (from versions: none)
3.597 ERROR: No matching distribution found for onnxruntime-genai-cuda
Dockerfile:34
34 | >>> RUN pip install --pre onnxruntime-genai-cuda --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/
35 |     RUN pip install --no-cache-dir -r requirements.txt
ERROR: failed to solve: process "/bin/sh -c pip install --pre onnxruntime-genai-cuda --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/" did not complete successfully: exit code: 1


npm install failure

I ran on NodeJS v14.8.0 and TypeScript Version 3.9.7:
npm install

I see the following errors, please investigate this.
code E401
npm ERR! Unable to authenticate, need: Basic realm="GitHub Package Registry"

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vishnu/.npm/_logs/2020-08-13T08_04_24_023Z-debug.log

I tried to authenticate using
npm login --
I am able  logedin with my account. Again tried npm install but issue still exist.
Logged in as vprdnew on https://registry.npmjs.org/.

This was because npm login --registry=https://npm.pkg.github.com was not used properly - that must be done one time with your GitHub ID and GitHub Personal Access Token (PAT).


Enable building with GHC 8.2.1

! @jystic
Without a bump to time, we get an conflict with the unix package and the bounds on base.
eg
rejecting: unix-<IP_ADDRESS>/installed-2.7... (conflict: unix =>
time==<IP_ADDRESS>/installed-1.8..., ambiata-mafia => time>=1.4 && <1.7)
rejecting: unix-<IP_ADDRESS> (avoiding to reinstall a package with same version but
new dependencies)
rejecting: unix-<IP_ADDRESS>, unix-<IP_ADDRESS> (conflict:
base==<IP_ADDRESS>/installed-4.1..., unix => base>=4.5 && <4.10)
rejecting: unix-<IP_ADDRESS> (conflict: base==<IP_ADDRESS>/installed-4.1..., unix =>
base>=4.5 && <4.9)
rejecting: unix-<IP_ADDRESS>, unix-<IP_ADDRESS> (conflict:
base==<IP_ADDRESS>/installed-4.1..., unix => base>=4.5 && <4.8)
rejecting: unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>,
unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>,
unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-<IP_ADDRESS>, unix-2.0
(conflict: ambiata-mafia => unix==2.7.*)

Also needs https://github.com/ambiata/twine/pull/41
We don't have gcc 8.2 builds in boris so it's not going to trigger any CI issues.

Any chance of pushing to the ambiata repos so we get builds? or are your keys disabled atm?

Sure I'll fire up the other laptop and do an ambiata repo version. Was
hacking on this on non-work laptop
On Wed, 6 Sep 2017 at 2:36 pm, Jacob Stanley<EMAIL_ADDRESS>wrote:

Any chance of pushing to the ambiata repos so we get builds? or are your
keys disabled atm?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ambiata/mafia/pull/181#issuecomment-327485263, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKbuZR1hTfBWVPO5AbPRrhjFh1B0E0Gks5sfp_qgaJpZM4PNFfL
.


is this inference only or training as well?

First of all, thanks for sharing this code :)
Is this code expected to be used purely in inference or can it be used for training as well?
btw - my main motivation for using batchnorm fusion isn't run speed, it's reducing memory requirements.

It is only for the inference

ok, thanks! :)


Fix Some 404 pages

There are some more to iron out in the analytics, but this is a good start

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Something went wrong with PR preview build please check

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr590.previews.kube001.services.stellar-ops.com/


Dev

piholed percent - pihole overall average.zip

The variance seems to come from the fact that "overall average" includes values with "0" like so: 1+0+2+0+3=6
6/5 =1.2 and not 6/3=2
do you agree? have to think about that ...

That makes sense


split rickshaw-run into rickshaw-validate, rickshaw-build, and rickshaw-exec

Splitting these up for the following reasons:

Smaller scripts which will be easier to port to python
Rickshaw-build needs to be run via endpoints to build on specific hosts

Changing rickshaw-run to rickshaw-exec, as I would like to support the "old" way while we introduce the "new" way.

These new scripts will use one-json exclusively, and not support cmdline to vast array of cmdline options (there still may be a couple)


Drag&Drop not working

I'm not quite sure what the cause of this is but I'm unable to use SortableJS for example to enable drag and drop of lists or tables. It just doesn't do anything. I tried reproducing it in jsfiddle. It's working there but the same code is not working in Neutronium: https://jsfiddle.net/7dsLcgv3/
Is anyone able to confirm this?

Do you have a repo with the code for reproduction? Did you check the console and verify all scripts get loaded?
There is no reason this should not work.


feat(host): adjust qemu args to support aarch64

这个 PR 实现什么功能/修复什么问题:

是否需要 backport 到之前的 release 分支:

3.6
/area host

Codecov Report

Merging #10446 (ab00f01) into release/3.6 (b9d30c0) will increase coverage by 2.20%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.6   #10446       +/-   ##
================================================
+ Coverage         5.86%    8.07%    +2.20%
================================================
  Files              828      107      -721
  Lines           129133    13008   -116125
================================================
- Hits              7577     1050     -6527
+ Misses          120876    11838   -109038
+ Partials           680      120      -560

Flag
Coverage Δ

aFlag
8.07% <0.00%> (+2.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/eval_context.go
34.25% <0.00%> (-3.89%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.86% <0.00%> (-1.03%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.09%)
:arrow_down:

pkg/util/sysutils/kvm.go
2.91% <0.00%> (-0.06%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

... and 614 more

Continue to review full report at Codecov.

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


All test segfault on Fedora Rawhide with legion-19.04.0

      Start 25: rendering
25/25 Test #25: rendering ........................***Exception: SegFault  0.44 sec
[buildhw-10:7077 :0:7077] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x7ff0db8da948)
==== backtrace ====
    0  /lib64/libucs.so.0(+0x194a3) [0x7ff0db8624a3]
    1  /lib64/libucs.so.0(+0x1965a) [0x7ff0db86265a]
    2  /lib64/libuct.so.0(+0x1b72b) [0x7ff0dbbb072b]
    3  /lib64/ld-linux-x86-64.so.2(+0xfe4a) [0x7ff0e379ee4a]
    4  /lib64/ld-linux-x86-64.so.2(+0xff51) [0x7ff0e379ef51]
    5  /lib64/ld-linux-x86-64.so.2(+0x13eae) [0x7ff0e37a2eae]
    6  /lib64/libc.so.6(_dl_catch_exception+0x79) [0x7ff0e20415b9]
    7  /lib64/ld-linux-x86-64.so.2(+0x1372e) [0x7ff0e37a272e]
    8  /lib64/libdl.so.2(+0x239c) [0x7ff0e1f0339c]
    9  /lib64/libc.so.6(_dl_catch_exception+0x79) [0x7ff0e20415b9]
   10  /lib64/libc.so.6(_dl_catch_error+0x33) [0x7ff0e2041653]
   11  /lib64/libdl.so.2(+0x2af9) [0x7ff0e1f03af9]
   12  /lib64/libdl.so.2(dlopen+0x4a) [0x7ff0e1f0342a]
   13  /usr/lib64/openmpi/lib/libopen-pal.so.40(+0x6ead7) [0x7ff0e1b01ad7]
   14  /usr/lib64/openmpi/lib/libopen-pal.so.40(mca_base_component_repository_open+0x1f4) [0x7ff0e1adf524]
   15  /usr/lib64/openmpi/lib/libopen-pal.so.40(mca_base_component_find+0x35b) [0x7ff0e1ade4eb]
   16  /usr/lib64/openmpi/lib/libopen-pal.so.40(mca_base_framework_components_register+0x2e) [0x7ff0e1ae9dfe]
   17  /usr/lib64/openmpi/lib/libopen-pal.so.40(mca_base_framework_register+0x256) [0x7ff0e1aea2e6]
   18  /usr/lib64/openmpi/lib/libopen-pal.so.40(mca_base_framework_open+0x14) [0x7ff0e1aea344]
   19  /usr/lib64/openmpi/lib/libmpi.so.40(ompi_mpi_init+0x695) [0x7ff0e1db6795]
   20  /usr/lib64/openmpi/lib/libmpi.so.40(PMPI_Init_thread+0x5b) [0x7ff0e1de6bbb]
   21  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/lib/librealm.so.1(AMMPI_SPMDSetThreadMode+0x182) [0x7ff0e2c879e2]
   22  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/lib/librealm.so.1(gex_Client_Init_GASNET_201930PARpshmFASTnodebugnotracenostatsnodebugmallocnosrclines+0x15d) [0x7ff0e2c15e5d]
   23  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/lib/librealm.so.1(_ZN5Realm11RuntimeImpl12network_initEPiPPPc+0x120) [0x7ff0e2bc6f30]
   24  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/lib/liblegion.so.1(_ZN6Legion8Internal7Runtime10initializeEPiPPPc+0x24) [0x7ff0e35ba694]
   25  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/lib/liblegion.so.1(_ZN6Legion8Internal7Runtime5startEiPPcb+0x250) [0x7ff0e35f49f0]
   26  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/bin/rendering(main+0x1b7) [0x556a7f716047]
   27  /lib64/libc.so.6(__libc_start_main+0xf3) [0x7ff0e1f2ef73]
   28  /builddir/build/BUILD/legion-legion-19.04.0/openmpi/bin/rendering(_start+0x2e) [0x556a7f7160de]
===================
0% tests passed, 25 tests failed out of 25
Total Test time (real) =  11.09 sec
The following tests FAILED:
	  1 - attach_file (SEGFAULT)
	  2 - circuit (SEGFAULT)
	  3 - dynamic_registration (SEGFAULT)
	  4 - ghost (SEGFAULT)
	  5 - ghost_pull (SEGFAULT)
	  6 - realm_saxpy (SEGFAULT)
	  7 - realm_stencil (SEGFAULT)
	  8 - spmd_cgsolver (SEGFAULT)
	  9 - virtual_map (SEGFAULT)
	 10 - attach_2darray (SEGFAULT)
	 11 - attach_array_daxpy (SEGFAULT)
	 12 - mpi_interop (SEGFAULT)
	 13 - hello_world (SEGFAULT)
	 14 - tasks_and_futures (SEGFAULT)
	 15 - index_tasks (SEGFAULT)
	 16 - global_vars (SEGFAULT)
	 17 - logical_regions (SEGFAULT)
	 18 - physical_regions (SEGFAULT)
	 19 - privileges (SEGFAULT)
	 20 - partitioning (SEGFAULT)
	 21 - multiple_partitions (SEGFAULT)
	 22 - custom_mapper (SEGFAULT)
	 23 - attach_file_mini (SEGFAULT)
	 24 - test_stl (SEGFAULT)
	 25 - rendering (SEGFAULT)
BUILDSTDERR: Errors while running CTest

Details here and here: https://koji.fedoraproject.org/koji/taskinfo?taskID=34577005
This can be reproduced with the following Dockerfile:
FROM fedora:rawhide
RUN dnf install -y spectool wget rpm-build dnf-plugins-core
RUN wget https://src.fedoraproject.org/fork/junghans/rpms/legion/raw/master/f/legion.spec
RUN spectool -g legion.spec
RUN dnf builddep -y legion.spec
RUN dnf install -y make
RUN rpmbuild -D"_sourcedir ${PWD}" -D"_srcrpmdir ${PWD}" -ba legion.spec

@junghans when I try to use the Dockerfile above, it barfs with the following:
...
[100%] Built target spmd_cgsolver
make[1]: Leaving directory '/root/rpmbuild/BUILD/legion-legion-19.04.0/serial'
/usr/bin/cmake -E cmake_progress_start /root/rpmbuild/BUILD/legion-legion-19.04.0/serial/CMakeFiles 0
+ popd
~/rpmbuild/BUILD/legion-legion-19.04.0
+ test -n ''
+ for mpi in '' mpich openmpi
+ test -n mpich
+ module load mpi/mpich-x86_64
++ /usr/share/lmod/lmod/libexec/lmod sh load mpi/mpich-x86_64
Lmod has detected the following error: The following module(s) are unknown:
"mpi/mpich-x86_64"

Please check the spelling or version number. Also try "module spider ..."
It is also possible your cache file is out-of-date; it may help to try:
  $ module --ignore-cache load "mpi/mpich-x86_64"

Also make sure that all modulefiles written in TCL start with the string
#%Module

+ eval false
++ false
error: Bad exit status from /var/tmp/rpm-tmp.3wbaeg (%build)
    Bad exit status from /var/tmp/rpm-tmp.3wbaeg (%build)

RPM build errors:
The command '/bin/sh -c rpmbuild -D"_sourcedir ${PWD}" -D"_srcrpmdir ${PWD}" -ba legion.spec' returned a non-zero code: 1

Also, can you confirm that bumping to legion-19.04.0 was the only change that took this from working to borken?  Thanks!

Hmm, on my other machine, I got the same error, however, one can just take the last image from dnf install -y make and then do docker run -it <sha> /bin/bash and execute rpmbuild -D"_sourcedir ${PWD}" -D"_srcrpmdir ${PWD}" -ba legion.spec in there, which leads to the same segfault.
legion-18.12.0 got rebuild recently, so that still worked. First I thought it might be gasnet, but it segfaults with gasnet-1.32.0 and gasnet-2019.03.0 is the same way.

Do you have any docker containers that test just MPI without GASNet and Legion? The crash is happening inside libopen-pal which is an MPI library.

Yes, the spec builds legion without MPI and with Gasnet on top of MPICH as well as OpenMPI.

Well, I mean do you have a container that just runs the OpenMPI test suite without any Legion/GASNet/etc?

The openmpi build always runs the test suite: https://src.fedoraproject.org/rpms/openmpi/blob/master/f/openmpi.spec#_236
So  openmpi can be considered tested.

Something like:
FROM fedora:rawhide
RUN dnf install -y spectool wget rpm-build dnf-plugins-core
RUN wget https://src.fedoraproject.org/rpms/openmpi/raw/master/f/openmpi.spec
RUN spectool -g openmpi.spec
RUN dnf builddep -y openmpi.spec
RUN dnf install -y make
RUN rpmbuild -D"_sourcedir ${PWD}" -D"_srcrpmdir ${PWD}" -ba openmpi.spec

That's just running 'make check'. It's not running the MPI Test Tool:
https://github.com/open-mpi/mtt

Effectively I'm going to continue to view this as not our problem. MPI should never segfault. It should either work or return an error code saying why what we did was wrong. Any segfaults in OpenMPI are the problem of the OpenMPI developers. If you get a backtrace that ends in Realm or Legion then we'll take the blame for it.

@opoplawski any ideas on this?

Looking at https://apps.fedoraproject.org/koschei/package/legion, it seems openmpi-4 broke the build.

Let's try again once they fix it.

@streichler adding
ENV MODULEPATH /etc/modulefiles:/usr/share/modulefiles

fixes the module load issue.

I've filed https://github.com/openucx/ucx/issues/3558

Just FYI, Fedora 29 and the upcoming 30 will get a legion-19.04.0 update in a couple of days.

@junghans Will that include the fix for OpenMPI 4? Looks like the bug above is still open.

Nope, Fedora 29 and 30 still use OpenMPI-3.

Ok, so with OpenMPI 3 all the test still work? So we won't break the build right?

Yes all test still pass. We will just wait for a OpenMPI-4 fix coming to rawhide.

@junghans Do we have an update on this issue? Has OpenMPI-4 made it into rawhide?

Nope, no news and openmpi-4 is in rawhide, but broken.

Actually, openmpi in rawhide is now being built without ucx, and that fixed the legion build: https://apps.fedoraproject.org/koschei/package/legion  The most recent build failed for a different reason.

Ok, the original issue is fixed, now the circuit test fails on ppc64le:
     Start  2: circuit
 2/24 Test  #2: circuit ..........................Child aborted***Exception:   1.39 sec


HTML

HTML
User Story
As a bootcamp student
I want the perwork notes to be structured on a webpage
so that I can easily find and read information
##Acceptance Criteria
Given a Prework Study Guide website
When I visit the website in my browser
Then I see four boxes titles HTML, CSS, Git, and JavaScript with associated notes listed

done


[Development] Building Out a Proper Frontend

See: https://getbootstrap.com/docs/5.2/components/modal/

Looking into React (https://reactjs.org/)


Removed duplicated links

Motivation
Due to a previous conflict merge, the team links were duplicated.

should we make fix of Managing persistent topics typo under Pulsar admin interface as well?

Sure I'll add the typo fix


Artifacts between tiles

I checked out the example project and added my custom urlTemplate and style.
The map renders streets and text, but the tiles is cutting off content.

Here is the code:
import 'package:flutter/material.dart';
import 'package:flutter_map/flutter_map.dart';
import 'package:flutter_map/plugin_api.dart';
import 'package:latlong2/latlong.dart';
import 'package:map_test/dark_theme.dart';
import 'package:vector_map_tiles/vector_map_tiles.dart';
import 'package:vector_tile_renderer/src/themes/light_theme.dart';
import 'package:vector_tile_renderer/vector_tile_renderer.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(primarySwatch: Colors.blue),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _isDarkMode = true;
  final _lightTheme = ThemeReader().read(lightThemeData());
  final _darkTheme = ThemeReader().read(darkThemeData);

  static const urlTemplate =
      "https://basemaps.arcgis.com/arcgis/rest/services/World_Basemap_v2/VectorTileServer/tile/{z}/{x}/{y}.pbf";

  @override
  Widget build(BuildContext context) {
    final centerMunich = LatLng(48.129710, 11.586124);

    return Scaffold(
      appBar: AppBar(
        actions: [
          IconButton(
            onPressed: () => setState(() => _isDarkMode = !_isDarkMode),
            icon: Icon(_isDarkMode ? Icons.dark_mode : Icons.light_mode),
          ),
        ],
      ),
      body: FlutterMap(
        options: MapOptions(
          center: centerMunich,
          zoom: 13.0,
          plugins: [VectorMapTilesPlugin()],
        ),
        layers: [
          VectorTileLayerOptions(
            theme: _isDarkMode ? _darkTheme : _lightTheme,
            tileProviders: TileProviders(
              {
                'esri': MemoryCacheVectorTileProvider(
                  delegate: NetworkVectorTileProvider(
                    urlTemplate: urlTemplate,
                    maximumZoom: 14,
                  ),
                  maxSizeBytes: 1024 * 1024 * 2,
                ),
              },
            ),
          ),
          MarkerLayerOptions(
            markers: [
              Marker(
                width: 80.0,
                height: 80.0,
                point: centerMunich,
                builder: (ctx) => Icon(
                  Icons.location_on_outlined,
                  color: _isDarkMode ? Colors.white : Colors.black,
                ),
              ),
            ],
          ),
        ],
      ),
    );
  }
}

Here is the json for the dark theme:
The content for final _darkTheme = ThemeReader().read(darkThemeData); can be found here:
https://gist.github.com/JulianBissekkou/527d0ade9d4d0a87af9fc9198ad5f94a

Thanks for the issue. I've had a quick look at the theme, it looks like there are some expressions in there that weren't supported until recently. See the vector_tile_renderer changelog for details.
You might want to pull the latest from this repository and try again. If you do, please attach a screenshot if it's any different. Theme expression support still isn't 100% so there could still be issues.

closing, but feel free to reopen if there are specific issues that you are having

Thanks for the update. You can see the result of new expression support in the gallery. The process that I used to add support for new expressions was to load  a map with the theme, with a breakpoint in UnsupportedExpression which is used for expressions that aren't recognized.
There's a chance that the problem is a mismatch between the theme and the tiles. That one is harder to troubleshoot since the theme might be fine, but just doesn't select any data from the tileset because the tiles are structured differently. One way to double check is to load your theme and tileset into an editor like maputnik to see if you get a different result.
To get an idea of what's involved, here a a couple examples of pull requests that improve support for expressions:

https://github.com/greensopinion/dart-vector-tile-renderer/pull/21
https://github.com/greensopinion/dart-vector-tile-renderer/pull/22

I added a breakpoint in UnsupportedExpression.evaluate and I also added a breakpoint in ExpressionParser._expressionChecked where the UnsupportedExpression is created.
Both breakpoints where never called and the map was renders as shown in the screenshot. Looks like its another problem 🤔

Great! What was the problem?

Hi @greensopinion, Thanks for the quick response. I have created the issue for this here. Esri map is pretty common here. If you have a chance to look at this issue. It would be great.


change the managed serviceaccount to a template type addon

issue reference: https://issues.redhat.com/browse/ACM-7067
This PR will move the managed service account to a template-type addon, so there will be no managed service account addon manager running on the hub cluster, instead, we add an addonTemplate CR on the hub.

remove managed service account addon manager deployment and add addon addonTemplate CR on the hub
change the generate charts script to generate charts for template-type addons
update permission for addontemplate and addondeploymentconfig

@qiujian16 @xuezhaojun could you help review this?

Is addonTemplate should join this rbac file? https://github.com/stolostron/backplane-operator/blob/7b9cbb638fc2d36fa0a5ce5a5f4cb2c092fd330a/pkg/templates/charts/always/rbac-aggregates/templates/clusterrole-admin-clc.yaml#L44

Thanks @xuezhaojun, Do you know if this file is generated by scripts or manually?

Thanks @xuezhaojun, Do you know if this file is generated by scripts or manually?

I viewed the history of this file it seems manually added, in klusterletconfig PR I added it manually.
This placement PR from @haoqing0110  also seems manually changed.

@xuezhaojun @qiujian16 PTAL

Hi @dislbenn, could you help review this?

@xuezhaojun @qiujian16 PTAL

Nothing update from me, good work!

/lgtm
/hold
@zhujian7 will these changes impact this story: https://issues.redhat.com/browse/ACM-7008? If not, we can unhold this PR. If yes, can you add a comment to that issue?

will these changes impact this story: https://issues.redhat.com/browse/ACM-7008?
@dislbenn, thanks for the review, As far as I understand, there should be no impact. I just refactored how the managed service account addon is installed(deployment -> addontemplate), its functionality has not changed.

/unhold


pfctl rules.debug appears unnecessary and has poor performance

I don't see where this has poor performance. What specifically are you seeing poor performance with there? That was added specifically to be faster, though I don't see any difference either way in the pfctl times.
Regardless, this isn't something we're going to merge into RELENG_2_2 at this point, please submit against master with specifics as to why it's preferable/what is slow.

"I don't see where this has poor performance."
Two places.  Firewall log display with descriptions, also clicking the action icon to reveal the rule that triggered the action.
"What specifically are you seeing poor performance with there?"
pfctl -vvPnf /tmp/rules.debug is slow due to parsing large table sources such as bogonsv6 and alias urltables.
pfctl -vvPsr is very fast but is only used in place of the other if /tmp/rules.debug file does not exist.
"That was added specifically to be faster, ..."
It may be faster with some specific pristine /tmp/rules.debug file.  But add a fairly large real world table source or two for it to parse and it is suddenly much slower.
"...though I don't see any difference either way in the pfctl times."
Then the performance test setup scenario, dataset, etc. being used is insufficient to reveal the performance difference.


Very slow with giant libraries

My Koel instalation is very slow since I've added all my musics. SELECT COUNT(*) FROM songs; returns 10943 results.
Can you add an option(or something like) to search and manage all musics in server side?

I have nearly 10K songs without any issues.

@SamuelMoraesF What version?

I'm running the latest version (v2.1.0).
On my smartphone, Koel is slow in every action(play/pause a music, change to artists/albums page...) at Firefox for Android, I've tried on Moto X and Moto G devices. With Google Chrome it works normally.
On my computer, Koel is running normally, but when I search for something, it take ~5 seconds to reply(and seems to use a lot of memory, as my browser animations stop) this happens with my smartphone too(with any browser).

@SamuelMoraesF Thanks. That seems to be #231, which has been fixed on the master branch. I'm still finishing several remaining issues before bumping up the tag, but you can try using master for now (it's pretty stable).


Raspberry Pi3

this works with RPi3???
I'm trying to use it, but it seems they don't work together

i haven't tested pi specifically, but which browser are you using?
i would suspect there is a good chance it will work if using a supported browser
Currently, the following are supported:
Chrome (33)
FireFox (>=44)
Watson Speech to Text
Microsoft Edge
Firefox (<44)
Opera


Docs need to explicitly state that phone call authentication is blocked on trial tenants

Azure AD Tenants that are on trial subscriptions do not have the ability to use phone call verification. Customers should have a better experience when trying to set this up because our documentation doesn't align with what they see in the tenant. The SSPR blade will show that it's not possible but our docs page needs to have this added in the FAQ page.

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

ID: cd8e9708-dae9-55bb-4bcf-b2bad768b695
Version Independent ID: e78950ad-e28a-a3be-b526-c77bfba7e82c
Content: Phone authentication methods - Azure Active Directory
Content Source: articles/active-directory/authentication/concept-authentication-phone-options.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@adamdost-msft
Thanks for your feedback! We will investigate and update as appropriate.

@adamdost-msft
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

#please-close


PR for auto-generating eth. address

Thanks @owonwo
It looks like you are getting the same error message that I got before when trying to build with Netlify: two inconsistent versions of babel-eslint is specified.
1:18:02 PM: $ react-scripts build
1:18:02 PM: There might be a problem with the project dependency tree.
1:18:02 PM: It is likely not a bug in Create React App, but something you need to fix locally.
1:18:02 PM: The react-scripts package provided by Create React App requires a dependency:
1:18:02 PM:   "babel-eslint": "10.0.3"
1:18:02 PM: Don't try to install it manually: your package manager does it automatically.
1:18:02 PM: However, a different version of babel-eslint was detected higher up in the tree:
1:18:02 PM:   /opt/build/repo/node_modules/babel-eslint (version: 10.0.2)
1:18:02 PM: Manually installing incompatible versions is known to cause hard-to-debug issues.
1:18:02 PM: If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
1:18:02 PM: That will permanently disable this message but you might encounter other issues.
1:18:02 PM: To fix the dependency tree, try following the steps below in the exact order:
1:18:02 PM:   1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
1:18:02 PM:   2. Delete node_modules in your project folder.
1:18:02 PM:   3. Remove "babel-eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
1:18:02 PM:   4. Run npm install or yarn, depending on the package manager you use.
1:18:02 PM: In most cases, this should be enough to fix the problem.
1:18:02 PM: If this has not helped, there are a few other things you can try:
1:18:02 PM:   5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
1:18:02 PM:      This may help because npm has known issues with package hoisting which may get resolved in future versions.
1:18:02 PM:   6. Check if /opt/build/repo/node_modules/babel-eslint is outside your project directory.
1:18:02 PM:      For example, you might have accidentally installed something in your home folder.
1:18:02 PM:   7. Try running npm ls babel-eslint in your project folder.
1:18:02 PM:      This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.
1:18:02 PM: If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.

I'll take a look at the version numbers. Let me know if you can find where the babel-eslint package versions are inconsistent too, many eyes will make this bug shallow.

Can i update the PR now?

@owonwo yes you can push new changes to this PR anytime,
and they will update the code review.
I am still working on the netlify build error, due to package version mismatches.
We might need to downgrade react-scripts to use the older version of jest that gets pre-installed by netlify.

I tried downgrading to<EMAIL_ADDRESS>which caused me to downgrade typescript to v3.5.2. npm run start worked without any error, but then typescript give error messages. @cryptogoth

I'll be needing your email to transfer the zero-knowledge instance on netlify.

thanks @owonwo I'm online in the gitter instance now and responded to you there about my email address. Good progress on the netlify package versions problem, I'll take a look and see what the typescript issue is.

@cryptogoth We are done with this issue, right?


Add Processing Tabs for Batch Processing

Currently dealing with a bug that is causing the target image to not render properly after adding a new tab


Danger check

Warnings

:warning:
No Changelog changes!

Messages

:book:
According to the blame info, we recommended @MrRaindrop to be the reviewers.

  Generated by :no_entry_sign: dangerJS


Update README.md

added some simple instructions about cloning with --recursive flag.

Not necessary anymore, removed submodule and went with a new custom theme on new-theme branch.


Fish Weirs symbol issue

This is an issue in:

[ ]  2525C
[ ]  2525B

It is not an issue in APP6-B, APP-6-D
It is fixed in 2525D (https://github.com/Esri/military-symbology/issues/270)

Fixed
SIDC
Name
Feature Type

- [ ]
46120310
Hydrography-Ports and Harbors- Fish Wiers (Point)
Oceanographic Point

Should be:

This issue was moved to ArcGIS/military-symbology-styles#76


Transfer management api

Let's transfer management api ( GetStorageSlice is an exception, it will be transferred letter) here from artipie, set up github actions, rultor and whole infrastructure and make-up readme file.

@yegor256 could you please touch .rultor here, so we could release when necessary?

@olenagerasimova @olegmoz done

@rultor release, tag=0.1

@rultor release, tag=0.1

@olenagerasimova OK, I will release it now. Please check the progress here

@rultor release, tag=0.1

@olenagerasimova Done! FYI, the full log is here (took me 11min)

@olenagerasimova the puzzle #22 is still not solved.


[Bug] password prompt in knack does not work with CTRL+V in windows

Az devops login password prompt does not work when ctrl+v is used on the prompt.
https://github.com/microsoft/knack/issues/160
Possible change to make it easy to troubleshoot will be to add token length check.. and if the length is too small than expected (guid length) then warning message to the console indicating this issue.
And login suggested through right click.

Let's go ahead with the string length check since the *(star) experience is again a framework level change that might take time. There are two things that we need to convey

Inform the user that the token has not been entered
Address the common scenario which is CNTRL + V

Proposed experience

az devops login
Token:

Please provide a PAT token. If you are using CNTRL + V to paste the token, it won't work in command line or powershell - https://github.com/microsoft/knack/issues/160. Use right click or console menu to paste the token.
@atbagga @ishitam8 @mitsha-microsoft for review.


Special character sequences in git commands

This is for other people's future reference. I was using the MSBuildGitHash Nuget package v2.0.2.
While trying to run some custom git commands to capture additional information, I ran into problems with character sequences that needed to be escaped.

% needs to be escaped as %%
ae needs to be escaped as``a%e`
cd needs to be escaped as``c%d`

These are the git commands I was trying to run:

git show --quiet --format=%ae
git show --quiet --format=%an
git show --quiet --format=%cd --date=iso-strict
git show --quiet --format=%B
git show --quiet --format=%H

This is the corresponding ItemGroup with correctly escaped character sequences:
  <ItemGroup>
    <AssemblyMetadataCommand Include="GitAuthorEmail">
      <Command>git show --quiet --format=%%a%e</Command>
    </AssemblyMetadataCommand>
    <AssemblyMetadataCommand Include="GitAuthorName">
      <Command>git show --quiet --format=%%an</Command>
    </AssemblyMetadataCommand>
    <AssemblyMetadataCommand Include="GitCommitDate">
      <Command>git show --quiet --format=%%c%d --date=iso-strict</Command>
    </AssemblyMetadataCommand>
    <AssemblyMetadataCommand Include="GitCommitMessage">
      <Command>git show --quiet --format=%%B</Command>
    </AssemblyMetadataCommand>
    <AssemblyMetadataCommand Include="GitFullHash">
      <Command>git show --quiet --format=%%H</Command>
    </AssemblyMetadataCommand>
  </ItemGroup>

There may be other character sequences that require escaping which I am not yet aware of.

If you want to add a brief description about this to the readme.md, I will merge it.


Add support for package registry interaction

wskdeploy should ease the interaction with public and private OpenWhisk package registries. This proposal is about adding the following commands:

publish: publishes packages and notify registry
install: installs the dependencies describes in the manifest. No registry interaction.
unpublish: unpublishes packages

A separate effort is underway to provide an experimental public registry (more information about it soon).
The issue depends on #41.

[ ] Publish command #154

@lionelvillard is this still relevant?

Nope. closing.


innernet: 1.5.3 -> 1.5.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tonarino/innernet/releases.
meta.description for innernet is: "A private network system that uses WireGuard under the hood"
meta.homepage for innernet is: "https://github.com/tonarino/innernet"
meta.changelog for innernet is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4/bin/innernet had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4/bin/innernet-server had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 1.5.4 with grep in /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4
found 1.5.4 in filename of file in /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
innernet

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A innernet https://github.com/r-ryantm/nixpkgs/archive/7ff0080e8dbd68affe13a7646b379b8ca7b58ef9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4
ls -la /nix/store/nx4zixk9k4l37dahv5r0g74qwprz82md-innernet-1.5.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

innernet

Maintainer pings
cc @tomberek @0x4A6F for testing.

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

1 package built:

innernet


[REQ] Can you Please add the change api option again?

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
i get way higher frames in vulkan rather than directx 11, to be specific i get 100 fps more :(

i get way higher frames in vulkan rather than directx 11, to be specific i get 100 fps more :(

If you had done a little bit of research you would know that this option was removed due to Direct3D 11 being the only rendering API that isn't broken. Vulkan and OpenGL trigger Hyperion and D3D 10 works only with low graphics quality

If Vulkan works just fine for you, then you can manually add the FFlagDebugGraphicsPreferVulkan flag in the editor, and set it to True. If Roblox breaks sometime in the future, just be mindful about the fact that you have it enabled.

If Vulkan works just fine for you, then you can manually add the FFlagDebugGraphicsPreferVulkan flag in the editor, and set it to True. If Roblox breaks sometime in the future, just be mindful about the fact that you have it enabled.

ill definitely use that command, thanks!


Adjust LICENSE to make it GitHub friendly

This should allow GitHub to dislay the nicer Apache-2.0 license title like in assertj/doc.

did not seem to work :(

I'll try to follow the local test mentioned in https://github.com/licensee/licensee/blob/master/docs/CONTRIBUTING.md#reporting-an-improperly-detected-license (I have some issue with my Ruby at the moment), in the worst case the GitHub support is also an option.

It looks like license-header.txt is detected as NOASSERTION license. Result of licensee:
$ ./script/git-repo https://github.com/joel-costigliola/assertj-core.git
License:        NOASSERTION
Matched files:  LICENSE, licence-header.txt
LICENSE:
  Content hash:  ab3901051663cb8ee5dea9ebdff406ad136910e3
  Confidence:    100.00%
  Matcher:       Licensee::Matchers::Exact
  License:       Apache-2.0
licence-header.txt:
  Content hash:  3e8118b64de81dd0cdadee5cb923a2294c26fcde
  License:       NOASSERTION


feat: Failed uploads should not be returned via utapi.listfiles()

Describe the feature you'd like to request
Failed uploads should not be returned when calling utapi.listfiles() or utapi.getFileUrls(failedUploadKey)
Right now there is no way to see if a file url actually works, or not.
Describe the solution you'd like to see
Either do not return failed uploads, or add a status property to filter them out.
Additional information
No response
👨👧👦 Contributing

[ ] 🙋♂ Yes, I'd be down to file a PR implementing this feature!

Good call. Will get this out today 👍

listFiles should now include a status field, matching with what shows on the dashboard

You guys are impressively fast! Thanks!

I opened a PR for this types of listFiles: https://github.com/pingdotgg/uploadthing/pull/430


"invalid pixel format attribute" on OS X

All of the examples fail to run correctly on my OS X 10.8.5 machine at the moment, logging "invalid pixel format attribute" then failing to the create the OpenGL context and quitting. This may not be a recent change that caused this, since I have not touched glutin or glium since December.

After upgrading to OS X 10.10, the problem no longer occurs. So this looks to be specific to 10.8.3 at least. Not sure whether you want to continue supporting that version.

The only pixel format attributes that were added since December, 2014 seem to be NSOpenGLPFAOpenGLProfile (10.7). I don't have access to an earlier version of OS X so testing this seems tricky.
@dylanede did it panic and say invalid pixel format attribute? Replacing an enum with some random numbers only gives me this:
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: OsError("Couldn\'t create OpenGL context")', /Users/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-mac/build/src/libcore/result.rs:768
Process didn't exit successfully: `target/debug/examples/vsync` (exit code: 101)

@fkaa The message I received was very similar to that, only the previous the line of output would say
invalid pixel format attribute

Just to be clear, the last time that I used Glutin on OS X 10.8.5 before encountering this problem was in December 2014, but I think the actual date was near the start of December, so if you're looking for relevant changes make sure to include those in December.

Possible perpetrator: NSOpenGLProfileVersion4_1Core.
OS X 10.8.5 only supported up to 3.2 Core (NSOpenGLProfileVersion3_2Core) and NSOpenGLProfileVersion4_1Core is defined separately in rust-cocoa as 0x4100. This could be a simple case of requesting a context which is not available (NSOpenGLProfileVersion4_1Core is default, afaik).
Possible solution: Check against current OS version and cap version accordingly (eg. on 10.8.5, GlRequest::Latest would request NSOpenGLProfileVersion3_2Core instead)

Should be fixed in #470.


Unexpected result when I use compute_at

The case is shown as below:
import tvm
A = tvm.placeholder((15,), name='A')
B = tvm.compute((15,), lambda i: A[i]+1, name='B')
C = tvm.compute((5,3), lambda i, j: B[i+j*5]*2, name='C')
s = tvm.create_schedule(C.op)
s[B].compute_at(s[C],s[C].op.axis[0])
print(tvm.lower(s, [A, B, C], simple_mode=True))
And I get the result as below:
produce C {
for (i, 0, 5) {
produce B {
for (i, 0, 11) {
B[(i + i)] = (A[(i + i)] + 1.000000f)
}
}
for (j, 0, 3) {
C[((i3) + j)] = (B[(i + (j5))]*2.000000f)
}
}
}
Seems this is an error? @tqchen

It is right. Although there are two axes with the same name i, tvm does not distinguish axes by name.
To avoid the name conflict, you can replace i with k in B = tvm.compute((15,), lambda i: A[i]+1, name='B')

Please raise this discussion question at https://discuss.tvm.ai/ @merrymercy seems to provide a reasonable answer,

that's not Kun talking about, the result is
produce C {
  for (i, 0, 5) {
    produce B {
      for (i, 0, 11) {
        B[(i + i)] = (A[(i + i)] + 1.000000f)
      }
    }
    for (j, 0, 3) {
      C[((i*3) + j)] = (B[(i + (j*5))]*2.000000f)
    }
  }
}

however we are expecting
produce C {
  for (i, 0, 5) {
    produce B {
      for (i, 0, 3) {
        B[(i + i)] = (A[(i + i)] + 1.000000f)
      }
    }
    for (j, 0, 3) {
      C[((i*3) + j)] = (B[(i + (j*5))]*2.000000f)
    }
  }
}

Because the range inference of compute_at only supports continuous layout.
To compute C, if we only support fetch a continuous range of B, then 11 = (3-1) * 5 + 1 is the minimum. So I say it is correct..

I see, is it possible to support fetching with stride?


Update python versions, include changes from kxxoling

I can't speak for all these changes, but I'd love it if the parent of all our forks was the most up to date version.

Hi, thanks for proposing the improvements. I'll accept them partially. Things like the new .editorconfig file and the addition of more recent Python versions are nice to have. Other changes either do not relate to the project, such as removing the copyright notice from all the files – this could be a y/n option thou.

Before I accept them, however, would you please fix the errors on Travis?


Support for probe response and client disconnect thresholds

Added support to configure probe response and client disconnect thresholds
via ovsdb.
Signed-off-by: Yashvardhan<EMAIL_ADDRESS>

merged into pending, Thanks !


ol.source.MapQuest logo not found

The mapquest logo url is not present anymore.

Right I noticed the same and have asked them on Twitter: https://twitter.com/6artvde/status/613256118287114240

Has been fixed by MapQuest.


Automated testing with default settings does not work

I am running the command \vendor\bin\phpunit and tests are returning:
1) Tests\Unit\UserTest::access_student_birthdate
BadMethodCallException: SQLite doesn't support multiple calls to dropColumn / renameColumn in a single modification.

Using default test settings as per .env.testing

Seems to be related to this bug at laravel/framework:
https://github.com/laravel/framework/issues/2979

Okay so using array notation works:
Does not work:
    public function up()
    {
        Schema::table('course_skill', function (Blueprint $table) {
            $table->string('order')->nullable()->after('weight');
            $table->dropColumn(['created_at']);
            $table->dropColumn('updated_at');
            $table->dropColumn('deleted_at');
        });
    }

Does work:
    public function up()
    {
        Schema::table('course_skill', function (Blueprint $table) {
            $table->string('order')->nullable()->after('weight');
            $table->dropColumn(['created_at', 'updated_at', 'deleted_at']);
        });
    }

Okay, I think it's just that migration that causes the whole suite to fail.
I will do a PR now.


@styled-system/should-forward-prop: Add shadow to the list of composed functions

I noticed that the default shouldForwardProp does not exclude from the DOM props for shadow and variants (buttonStyle, colorStyle, & textStyle). This PR adds those to the list of composed functions to exclude.

Thanks!


Merge regions into develop

This PR brings back all the 5.3 specific documentation changes into the develop branch of ome-documentation. The OMERO 5.2 documentation is now derived from the dev_5_2 branch.

👍 Both sets of staging pages look as expected


decode_label() function

Is there any special purpose to implement custom decode function instead of using (more general) keras.backend.ctc_decode()?

Hi @qjadud1994
I'm trying to customize your code for my own data, where I have plates with 8 numbers (with different characters in the middle). However, I don't understand your decode function. More specifically, I don't understand why your output's shape is (1,32,42). I know that you have 41 letters, but shouldn't the model predict 9 set of 42 scores (instead of 32)? So that getting the maximum index out of each would lead to a 9 character license plate, as in your example images?

Hi @szm2015 ,
the 32 is for segmentation of feature map that generated bu CNN, in dead this is similar to segmentation the input image to 32 segmentation, and we select 8 unique character from 32 label character for each segment.


Spelling issue when creating the sample API

Description:
Spelling issue when creating the sample API. (Screenshot attached)
should be "Updating"
Steps to reproduce:

Open the publisher portal
Click create and deploy sample application

Environment details (with versions):

OS: Ubuntu 20.04

We need to make each starting letter capital.

"Creating Sample API" text also need to be corrected.

This is fixed in the master now, We have improved the progress view and this issue is no longer in the master


bazel build succeeds, but bazel-mobile install fails

The build succeeds on OS 10.11.6, with bazel version 0.3.1-homebrew. However, the bazel mobile-install fails. This is not a TensorFlow capitalization problem or a camera permissions issue!
Thanks ||
bazel mobile-install //tensorflow/examples/android:tensorflow_demo --verbose_failures
The main error is listed below:
ERROR: /private/var/tmp/_bazel_kg/16cb3f28d531847b42ceb660896dbffa/external/bazel_tools/tools/android/BUILD:132:1: Converting to Python 3: external/bazel_tools/tools/android/incremental_install.py failed: 2to3 failed: error executing command
(cd /private/var/tmp/_bazel_kg/16cb3f28d531847b42ceb660896dbffa/execroot/tensorflow &&
exec env -
bazel-out/host/bin/external/bazel_tools/tools/python/2to3 --no-diffs --nobackups --write --output-dir bazel-out/host/genfiles/python3/external/bazel_tools/tools/android --write-unchanged-files external/bazel_tools/tools/android/incremental_install.py): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
Target //tensorflow/examples/android:tensorflow_demo failed to build
INFO: Elapsed time: 0.396s, Critical Path: 0.15s
WARNING: Bazel Android NDK crosstools are based on Android NDK revision 11. The revision of the Android NDK given in android_ndk_repository rule 'androidndk' is '12.1.2977051'.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/debug:debug_graph_utils.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/debug:debug_graph_utils.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:avgpooling_op.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:bounds_check.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_activations.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_attention.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_backward_cuboid_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_backward_spatial_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_cuboid_convolution.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_patch_3d.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_pooling.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_softmax.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_spatial_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:maxpooling_op.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:ops_util.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:ops_util.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:pooling_ops_common.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:pooling_ops_common.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_entry.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_scorer.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_search.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_decoder.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_loss_util.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:tensor_bundle.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/core/BUILD:667:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:tensor_bundle.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kg/tensorflow/tensorflow/examples/android/BUILD:56:12: in srcs attribute of android_binary rule //tensorflow/examples/android:tensorflow_demo: please do not import '//tensorflow/contrib/android:java/org/tensorflow/contrib/android/TensorFlowInferenceInterface.java' directly. You should either move the file to this package or depend on an appropriate rule there.
INFO: Found 1 target...
ERROR: /private/var/tmp/_bazel_kg/16cb3f28d531847b42ceb660896dbffa/external/bazel_tools/tools/android/BUILD:132:1: Converting to Python 3: external/bazel_tools/tools/android/incremental_install.py failed: 2to3 failed: error executing command
(cd /private/var/tmp/_bazel_kg/16cb3f28d531847b42ceb660896dbffa/execroot/tensorflow &&
exec env -
bazel-out/host/bin/external/bazel_tools/tools/python/2to3 --no-diffs --nobackups --write --output-dir bazel-out/host/genfiles/python3/external/bazel_tools/tools/android --write-unchanged-files external/bazel_tools/tools/android/incremental_install.py): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
Target //tensorflow/examples/android:tensorflow_demo failed to build
INFO: Elapsed time: 0.396s, Critical Path: 0.15s
NOTE: Only file GitHub issues for bugs and feature requests.  All other topics will be closed.
For general support from the community, see StackOverflow.
To make bugs and feature requests more easy to find and organize, we close issues that are deemed
out of scope for GitHub Issues and point people to StackOverflow.
For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
Environment info
Operating System:
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
If installed from binary pip package, provide:

A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.__version__)".

If installed from source, provide

The commit hash (git rev-parse HEAD)
The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
What other attempted solutions have you tried?
Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

My guess is that incremental_install.py is a python2 script, but you are using python3, and the automatic conversion is failing. Does it work if you use python2 instead?
If you run:
bazel-out/host/bin/external/bazel_tools/tools/python/2to3 --no-diffs --nobackups --write --output-dir bazel-out/host/genfiles/python3/external/bazel_tools/tools/android --write-unchanged-files external/bazel_tools/tools/android/incremental_install.py
does it tell you anything else about the failure?
If you just want to go ahead and install/run the demo, here's the typical command sequence:
bazel build -c opt //tensorflow/examples/android:tensorflow_demo
adb install -r bazel-bin/tensorflow/examples/android/tensorflow_demo.apk

You can even auto-start the activity with:
adb shell am start -n org.tensorflow.demo/.CameraActivity

Andre - thanks much for the kind note. Running the command you suggested
"bazel-out/host/bin/external/bazel_tools/tools/python/2to3 --no-diffs --nobackups --write --output-dir bazel-out/host/genfiles/python3/external/bazel_tools/tools/android --write-unchanged-files external/bazel_tools/tools/android/incremental_install.py"
does not return anything.
I also forgot to add that  the "adb install.."  goes through without errors - however, that is when the App crashes on start.
Probably python3 is the culprit - I will check it out and let you know.

What is the runtime error you're seeing? Have you added the model and label files to tensorflow/examples/android/assets/?

Yes, Andrew. I have the model and label (*.txt) files in the assets directory. I am starting over again and will let you know the outcome. Thanks so much! ||

Andrew, I started over and the adb install works fine now. Perhaps I was missing the labels (*.txt) file. I am sorry for the inconvenience and will close the issue. Also, thank you so much for your help in resolving this. ||


question : Yolo v1 confidence and probability class map

Hello,
I am trying to understand in details Yolo V1 but I have some questions about it regarding the confidence and class probability. In fact, the confidence is equal to : ground truth label * IOU(pred, truth). To find the ground truth label, we just need to get an array of size 7x7 and put the cell to 1 if the center of an object is inside the cell in the dataset. But, to compute the IOU I have some doubt. Do you compute the IOU only when the center of the prediction box and the center of the object (truth)  is INSIDE the same cell ?
I have also a question regarding P class|object, if there is no object in a cell ou multiple object which label do you return during the training step ?
I thank you for the help !

Hi, sorry for late reply.
In yolo v1, each cell has two pred box, I think the center of two pred box will always fall in the cell. We should compute IOU for the two box and ground truth box which INSIDE the same cell, then, choose the bigger IOU, and the pred box with bigger IOU is responsiable for the target.
If there is no object in a cell, CLASS LOSS will not be computed. So wen there is no object in a cell, we don't need return any label.
By the way, in my implementation, i did something wrong. I don't compute IOU between pred box and target box during training, i just set it to one. I fix this later, the performance on validation is a little better, but not so good,  so i haven't upload it yet.

I see, thanks for the answer !

@xiongzihua HI
从现在的code来看，您在训练时，是计算了IOU between pred box and target box的．
体现在yoloLoss.py中：
contain_loss = F.mse_loss(box_pred_response[:,4],box_target_response_iou[:,4],size_average=False)
此时的标签不是简单的1，而是具体计算的iou值box_target_response_iou[:,4]
不知道自己的理解对吗？？


LaTeX equations not showing when character '$' is abscent in .ipynb files

In regular Jupyter Notebooks, one can include a LaTeX-style equation without surrounding the equation with '$' in a markdown cell.
But when I try to do the same in VS Code with the Python extension, the equation won't render.
For example, in regular Jupyter Notebook:
\begin{align*}
(a+b)^2 = a^2+2ab+b^2
\end{align*}

Renders

But in VS Code, the equation will only render when the code is surrounded with '$', like this:
$\begin{align*}
(a+b)^2 = a^2+2ab+b^2
\end{align*}$

Is it possible to include the same funcionality for .ipynb files as in Jupyter Notebooks? It breaks many of my codes with LaTeX equations, and adding '$' to all of them is infeasible.
Edit:
Python VS Code extension version: 2019.10.41019
VS Code version: 1.39.1

Is this intentional or do you plan on fixing it on a future update?

I think we would fix it. Depends upon if it breaks something else or not. Not sure why nteract requires '$' (we use nteract to render latex/markdown).

Until now the rendering is the only problem i've had. Thank you for the support!

Not sure why you closed this? We'd still like to fix it.

@DavidKutu did you mean to close this? Shouldn't it have gone into Validate?

Most equations work now, but I had some problems with stuff like this:
\begin{equation} x=y+3 \label{eq:xdef}
\end{equation}
In equation (\ref{eq:xdef}) we saw $\dots$

http://www.personal.ceu.hu/tex/cookbook.html.
I don't this is related to this change though.

Sorry, I'm a beginner on github issues so I thought I had to close it. My bad!


Paremeterized test has empty shard with test class

Describe the bug

A clear and concise description of what the bug is.

Having one parameterized test method in a test class creates multiple shards. One for parameterized tests and one for class of the tests. Since there is no normal tests in shard with class parameterized.TestClass, shards finishes with no tests and results error.
To Reproduce

Steps to reproduce the behavior:

Run a parameterized test with single test method in it,
Open test result on firebase test lab an see two shards. One with tests and one with no test and failed result.

Expected behavior

A clear and concise description of what you expected to happen.

There shouldn't be a shard if class has no test other than parameterized tests.
Details (please complete the following information):

Have you tested on the latest Flank snapshot?
Post the output of  flank --version.

Flank 20.08.1

This is not a real issue. https://github.com/Flank/flank/issues/984 Confused me about which test are actually needs to be in the shards. After fixing suppress issue, it is clear that parameterized test land in single shard and there is no extra shard.

@kozaxinan Good to know 👍


unambigious reference to configmaps and secrets

Requirement
As a route developer I want to reference properties in existing configmaps and secrets without collision to easier integrate to existing infrastructure and to avoid managing globally unique key names in configmaps and secrets.
Problem
As documented only the key names from configmaps and secrets are used as properties. Obviously, this easily leads to problems: suppose two existing secrets for a source and target system of routes, both containing the keys username and password. There seems to be no possibility to use this without creating redundant secrets with globally unique key names.
Proposal
Camel seems to support something like configmap:<name>/<key>[:defaultValue] and secret:<name>/<key>[:defaultValue]. However, trying this, I get the error Mount path must be configured. According to mentioned Camel documentation the properties should be available

Use OS ENV variable with key camel.k.mount-path.configmaps and camel.k.mount-path.secrets (Camel K compatible).

In my case the environment variable CAMEL_K_MOUNT_PATH_SECRETS is set in the pod and the folder contains the secret files as expected.
Open questions
No response

Camel K property setting via kamel run -p option is an helper provided in the CLI. If the user has multiple keys with the same value, then, it's something up to the user to know and prevent.
"Using Kubernetes property placeholder functions" is a feature available generically in any runtime using camel-kubernetes component. I think that, in order to use it, you need to provide the dependency -d camel:kubernetes and the required configuration for the application to connect to the cluster [1] via properties.
However, from a deployment point of view, this may not be the best scenario when managing the application via Camel K operator. Going through that scenario, the application would require to connect to Kubernetes via REST API every time it uses the value, instead of using the native mechanics you can get mounting the configmap/secrets via the operator.
[1] https://camel.apache.org/manual/using-propertyplaceholder.html#_configuring_kubernetes_client

I'm not into the details who is doing its magic (Camel, Camel K, Kubernetes). However, I don't see the need to access REST API every time we use the secret because they are mounted in the pods file system in a directory containing also the secret name. The files containing the secrets can be uniquely references in the file system. There "just" needs to be some format to specify it in the integration and map that to the file contents.
For example {{secret:<name>/<key>}} maps to the content of file CAMEL_K_MOUNT_PATH_SECRETS/<name>/<key>. From my understanding that is populated on pod startup and never updates even if the secret changes, so the secrets could also be cached in the Camel process of the pod.

According to the code, there may be an issue in the way the path is discovered.
can you try to sue the jvm trait  to set the camel.k.mount-path.configmaps and the camel.k.mount-path.secrets system properties ?

Tried the following (not sure if my trait value is correct).
kamel run --trait jvm.config="-Dcamel.k.mount-path.secrets=/etc/camel/conf.d/_secrets" --config=secret:some  props.groovy

from('timer:props?period=1000')
    .log('{{secret:some/username}}')

That still gives "Mount path must be configured".

Did another check and it doesn't matter if I specify the jvm.config trait. The resulting pod looks exactly the same and there is no evidence of any impact. Especially the container args don't have an additional setting. The jvm.enabled trait doesn't seem to be necessary because I tried jvm.classpath and that entry was visible in the container args.

 It works if being used correctly (i.e. jvm.options instead of jvm.config). The value is referenced successful now.

So I guess the issue is that camel.k.mount-path.secrets is uses for both properties and env vars, whereas the env var should have been uppercase to match what camel-k injects

For future reference, it is also working in YAML based integrations:
spec:
  traits:
    mount:
      configs:
        - secret:some
    jvm:
      options:
        - "-Dcamel.k.mount-path.secrets=/etc/camel/conf.d/_secrets"

@aklemp can you please report an issue on Apache Camel here ? https://issues.apache.org/jira/projects/CAMEL

Sure, created https://issues.apache.org/jira/browse/CAMEL-20054

The above was fixed in the framework. We can keep it open and verify as soon as we release next camel k runtime.

@squakez @oscerd This needs to be reopen, I don't know why it was closed.

Fixed by camel-k-runtime 3.8.1


V1.2.1alpha.0

There's a problem with the class variables that are all named the same.  This addresses that and adds tests to verify the behavior.

Note, this should be manually merged against the v1.2.0 tag.

I think I'm going to merge this in this afternoon as the 1.2.1alpha.1 release so we can get the fix out while I try to figure out what is up with the other mixins.  They should be failing, but aren't. :-/


Support new speed percentage targets for fans

With 2021.3 the speed percentage for fan control is out and supporting it would be great.

After upgrading to HA 2022.2.0 my fans speeds do not work.
I can't even seem to find a way to access this component anymore via the UI.
Are we to use the native Lutron integration or what is going on?

I have pushed a change to update the fan component to use percentage instead of speeds provided as string. This is a potential breaking change depending on how you are using the component, but it is aligned with the documentation of the  Home Assistant fan component.
If anyone is still using this component and has a fan controller, please give it a test and leave any feedback.

I can try it but I do not show an update available for HACS component.  Do I need to just download the repo directly or can I point to a branch?
I noticed out of my 6 fans, sometimes some show up with lightning icons for on and off and others don't.

I can try it but I do not show an update available for HACS component. Do I need to just download the repo directly or can I point to a branch?
I noticed out of my 6 fans, sometimes some show up with lightning icons for on and off and others don't.

Probably not identified in your config yaml as a fan.
I bit the bullet and switched to the core integration since I had free time

I just did a re-download in HACS and a restart and they all work now.  All my fans are identified in my yaml.  I can't move to the built in config because I use pico remotes with custom commands, and this is the best way for me to do that.

I just did a re-download in HACS and a restart and they all work now. All my fans are identified in my yaml. I can't move to the built in config because I use pico remotes with custom commands, and this is the best way for me to do that.

The core integration has Pico support now.  You will have to convert your automations for them though.  Blueprints are out there to speed it up but if it ain't broke!


How to build the wheel package on ppc64le

Now , I am try to install the tensor2tensor on the ppc64le, however it is required ortools:
ERROR: Could not find a version that satisfies the requirement ortools (from mesh-tensorflow->tensor2tensor===1.13.4) (from versions: none)
ERROR: No matching distribution found for ortools (from mesh-tensorflow->tensor2tensor===1.13.4)

so, I am try  build the whl  on the ppc64le, Could I know what is right steps to build the whl?

Can you use docker ?
If yes, look at or-tools/tools/docker
there is a makefile and some docker files.
Adapt them, the command to build in the end (inside the hosted image) would
be make pypi_archive
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 15 oct. 2019 à 11:25, Leilei Hu<EMAIL_ADDRESS>a écrit :

Now , I am try to install the tensor2tensor on the ppc64le, however it is
required ortools:
ERROR: Could not find a version that satisfies the requirement ortools (from mesh-tensorflow->tensor2tensor===1.13.4) (from versions: none)
ERROR: No matching distribution found for ortools (from mesh-tensorflow->tensor2tensor===1.13.4)
so, I am try build the whl on the ppc64le, Could I know what is right
steps to build the whl?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1646?email_source=notifications&email_token=ACUPL3PWFYKLF5YNQGIHQNDQOWECFA5CNFSM4JAZXYR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HR2A2YA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3J2BCTJ23BJU7JPI73QOWECFANCNFSM4JAZXYRQ
.

@lperron , Thanks for your suggestion, Meanwhile, Could I know how to build the whl using the  setup.py  , linking this : python setup.py bdist_wheel ?

OR-Tools is a complex C++ code wrapped in python.
You can have a look at:
https://developers.google.com/optimization/install/python/source_linux
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 15 oct. 2019 à 11:46, Leilei Hu<EMAIL_ADDRESS>a écrit :

@lperron https://github.com/lperron , Thanks for your suggestion,
Meanwhile, Could I know how to build the whl using the setup.py
https://github.com/google/or-tools/blob/stable/tools/setup.py , linking
this : python setup.py bdist_wheel ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1646?email_source=notifications&email_token=ACUPL3JFVQH6L4HUBQJU7L3QOWGOXA5CNFSM4JAZXYR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBIEI2I#issuecomment-542131305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3J4VFN4MOUEGNROFNLQOWGOXANCNFSM4JAZXYRQ
.


publish<EMAIL_ADDRESS>

Requested by: @lforst
Merge target: 1.x
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[x] gcs

[x] npm[@sentry/cli-darwin]

[x] npm[@sentry/cli-linux-arm]

[x] npm[@sentry/cli-linux-arm64]

[x] npm[@sentry/cli-linux-i686]

[x] npm[@sentry/cli-linux-x64]

[x] npm[@sentry/cli-win32-i686]

[x] npm[@sentry/cli-win32-x64]

[ ] npm[@sentry/cli]

[ ] brew

[ ] github

[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

do not release

did we skip 1.77.2 by design?

I fumbled it by running the action from the wrong branch and now we gotta override it: https://github.com/getsentry/publish/issues/3269

#retract

this is messed up...