kubernetes v1.19.5 container runtime docker-containerd error deploy coredns

Description

With kubernetes v1.19.5 container runtime docker successfully deploy coredns latest, but with container runtime docker-containerd v1.4.3 failed deploy coredns latest
Steps to reproduce the issue:

Deploy coredns in kubernetes v1.19.5 with container runtime docker-containerd

Describe the results you received:
coredns [Dec 16, 2020 12:54:40 PM GMT+7] E1216 05:54:40.324876 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:55:08 PM GMT+7] E1216 05:55:08.036263 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Namespace: failed to list *v1.Namespace: Get "https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:55:14 PM GMT+7] E1216 05:55:14.948263 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Endpoints: failed to list *v1.Endpoints: Get "https://<IP_ADDRESS>:443/api/v1/endpoints?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:55:21 PM GMT+7] E1216 05:55:21.540372 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:55:52 PM GMT+7] E1216 05:55:52.133305 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Endpoints: failed to list *v1.Endpoints: Get "https://<IP_ADDRESS>:443/api/v1/endpoints?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:56:03 PM GMT+7] E1216 05:56:03.716440 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Namespace: failed to list *v1.Namespace: Get "https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:56:18 PM GMT+7] E1216 05:56:18.694104 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:56:45 PM GMT+7] E1216 05:56:45.316567 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Endpoints: failed to list *v1.Endpoints: Get "https://<IP_ADDRESS>:443/api/v1/endpoints?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:56:51 PM GMT+7] E1216 05:56:51.972765 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Namespace: failed to list *v1.Namespace: Get "https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host coredns [Dec 16, 2020 12:56:51 PM GMT+7] E1216 05:56:51.972838 1 reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://<IP_ADDRESS>:443/api/v1/services?limit=500&resourceVersion=0": dial tcp <IP_ADDRESS>:443: connect: no route to host
Describe the results you expected:
Kubernetes v1.19.5 with container runtime docker:
coredns
.:53
coredns
[INFO] plugin/reload: Running configuration MD5 = f68047850b236e33a043cf64188722fd
coredns
CoreDNS-1.8.0
coredns
linux/amd64, go1.15.3, 054c9ae

Output of containerd --version:
core@manager-01 ~ $ containerd --version
containerd github.com/containerd/containerd 1.4.3 6806845b4f638417933f68721e289c9aeda456b1

Any other relevant information:
core@manager-01 ~ $  sudo kubectl get nodes -o wide NAME                    STATUS   ROLES    AGE   VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                                             KERNEL-VERSION   CONTAINER-RUNTIME manager-01.bnpb.go.id   Ready    <none>   10m   v1.19.5   <IP_ADDRESS>   <none>        Flatcar Container Linux by Kinvolk 2605.9.0 (Oklo)   5.4.81-flatcar   containerd://1.4.3

Likely to be CNI misconfiguration, not a containerd bug

@AkhiroSuda ,
Ok, i will check cni config and redeploy again tomorrow,
Thank you for your hint

Has been fixed, not issue with coredns but with authorization kube-apiserver secure port 6443.


Configure a few CLI args via env variables

Problem description
The candidates would be:

--frozen
--locked
--quiet/--verbose
--color

It's convenient when consuming pixi from within a docker image, as it's easy to configure a global behavior with env variables.

I like it! I think this can be easily done with https://docs.rs/clap/latest/clap/struct.Arg.html#method.env.
Do you know of any tools that also do this, that we can use as an example?

Do you know of any tools that also do this, that we can use as an example?

None that come to my mind.

Are you ok if I submit a PR? That should be quite a quick one.

Sure!, I trust you come up with a good abstraction and make sure it aligns between all cli commands that could use it.


ntp: allow more than 2 NTP servers

Replacing ntp_primary_server and ntp_secondary_server variables with ntp_servers which is an array (not limited to 2 items).
The first item will be the preferred server if no ptp interface is defined.
For now the change is retro-compatible.

good point!


Sometime response finish_reason is Null

When a request is sent, the text value of choice is present, but sometimes the value of finish_reason is passed as null, and an error occurs when attempting type conversion.

On Sat, 11 Mar 2566 BE at 17:43 YD_S @.***> wrote:

When a request is sent, the text value of choice is present, but sometimes
the value of finish_reason is passed as null, and an error occurs when
attempting type conversion.
[image: image]
https://user-images.githubusercontent.com/45446457/224479671-90b6eb7b-9b38-4acd-aff6-4a3c7c76d489.png
[image: image]
https://user-images.githubusercontent.com/45446457/224479702-b723f93f-8e28-4346-95b2-8e200659bf53.png
[image: image]
https://user-images.githubusercontent.com/45446457/224479782-3b4f98f9-f28c-4234-972d-ada8f1119527.png

You can fix it , if you using last version


Added LB1 to LB2 route bridge

Prompted by issue #159, here is a script that transforms the LB1.0 routes into the new LB2.0 format.
This script has the following arguments

-r or --routes: which is the path to the routes file
-s or --scenarios: which is the path to the scenarios file
-e or --endpoint: which is the path of the endpoint file

This change is

Changed the branch to point to master


Added the ability to retrieve recorded requests

That's what I wanted to implement like 2 years ago and it's still in my fork (never merged to upstream because of me being lazy)
Highly vote for this changes!

Still, one question I have. Where's control about retrieve format? Maybe I overlooked it?


refactor: decrease size admin-boundary files AB#8833

@jannisvisser may I know what changed in these files? I'm unable to deduce what actually changed here.

@gulfaraz see comment here.
Very detailed boundaries (with a lot of corners) are being simplified. If you want to know more let's call.

@jannisvisser this clears it. Thank you!


Pixelation and Antialiasing

The view of the graph in the game looks pixelated. This might be an issue with the way the edges (and vertices) are drawn (which might use old tech). This doesn't happen with the triangles/planes that show relators

Turns out, this is just that anti-aliasing was turned off at the main camera.
I just created #52 partially because of this. Well, I personally like #52, you might differ though


Create RC2 milestone

RC1 has a draft release and items needs to be moved /triaged into RC2 milestone and this milestone needs to be created.
What did you expect to happen:
Create milestone for RC2 and potential date.

Created.  https://github.com/deislabs/ratify/milestone/8


Fix editlog bug

Fixes #198
Previously, editlog did not correctly handle cases where a user edited a log to be the same as an existing log, because the wrong equality check method was called (duplicate checks were being done by logs having same title AND description, which is not allowed).
This bug has been fixed and one test case has been added to verify the behaviour.

Codecov Report

Merging #216 (5fcf945) into master (8cc810c) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #216      +/-   ##
============================================
- Coverage     71.40%   71.36%   -0.04%
+ Complexity      818      817       -1
============================================
  Files           121      121
  Lines          2850     2850
  Branches        426      426
============================================
- Hits           2035     2034       -1
- Misses          633      634       +1
  Partials        182      182

Impacted Files
Coverage Δ

...a/seedu/address/logic/commands/EditLogCommand.java
85.05% <100.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
72.44% <0.00%> (-1.03%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Added initial authorization to github

Upon login, the user is asked for permission to authenticate via github and is then redirected to a "Welcome" page that displays the json output of his/her public repos. Welcome page also includes a "Logout" button that redirects to index() with a new session.

Thank you @marcospereira and @gmethvin for the feedback!
Latest commit:
1. Added integration with play-silhouette along with a few tests for the application routes. (See screenshots below)
2. Started trying out play-slick, but I'm open to other ways. I'm thinking of using a mysql store for persistence and the H2 in memory database for test specifications.
Just let me know if anything should be changed or if I'm missing something conceptually.
Thanks again!
Screenshots below:
a) Index() is a UserAwareAction:

b) SignIn() is an UnsecuredAction:

c) Profile access via SecuredAction

d) Back to index

So this never made it in production... I will archive this repo.


Update the pull_request_template for release-note 📖

Changes

The release notes need to use the release-note code block.
Do not add any by default to force the block to be added
accordingly to the PR content.

Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

/cc @jerop
/kind misc

:thinking: why is the check-pr-has-kind-label still red :thinking:

/lgtm

/test check-pr-has-kind-label

/kind label

/kind misc

Reason for the CI failure: https://dashboard.dogfooding.tekton.dev/#/namespaces/tektonci/taskruns/check-pr-labels-rgx8q
File "/tekton/scripts/script-5-x7m4b", line 6
    prLabels = json.loads('[{"color":"ef8fd9","default":false,"description":"Categorizes issue or PR as a miscellaneuous one.","id":2026949470,"name":"kind/misc","node_id":"MDU6TGFiZWwyMDI2OTQ5NDcw","url":"https://api.github.com/repos/tektoncd/pipeline/labels/kind/misc"},{"color":"6aed75","default":false,"description":"Indicates that a PR is ready to be merged.","id":1053663386,"name":"lgtm","node_id":"MDU6TGFiZWwxMDUzNjYzMzg2","url":"https://api.github.com/repos/tektoncd/pipeline/labels/lgtm"},{"color":"c2e0c6","default":false,"description":"Denotes a PR that doesn't merit a release note.","id":1402691966,"name":"release-note-none","node_id":"MDU6TGFiZWwxNDAyNjkxOTY2","url":"https://api.github.com/repos/tektoncd/pipeline/labels/release-note-none"},{"color":"77bb00","default":false,"description":"Denotes a PR that changes 10-29 lines, ignoring generated files.","id":1060140553,"name":"size/S","node_id":"MDU6TGFiZWwxMDYwMTQwNTUz","url":"https://api.github.com/repos/tektoncd/pipeline/labels/size/S"}]')
                                                                                ^
SyntaxError: invalid syntax

/kind misc

/kind foo

/kind misc

/approve


Support RepoDb.Field.From Expression

To support a simplified expression-based coding when calling certain operations the required a Field, kindly support the following.
RepoDb.Field.From<Person>(p => p.Name);
Usable at InlineMerge, Merge, etc operations

Fixed and is checked in the main branch.


Contributing + import not working

Hi there!
This project is so cool, but it seems that a CONTRIBUTING.md file is missing: I want to add support for other LLM (despite not being as effective as GPT-4o)
Also, the import:
from megaparse import MegaParse
Is not working

from megaparse.Converter import MegaParse

I'm pushing a new version to fix it :)


State / retraining properties for ensemble

Closes #133
Added

Ensemble.drift_states returns dict of member drift states
Ensemble.retraining_recs returns dict of member retraining recommendations, if they exist

Changed

improved unit testing and documentation for ensemble modules

@tms-bananaquit this is all done and pretty short


mandibular foramen

abnormal mandibular foramen morphology
DEF: any structural anomaly of the opening located on the medial surface of the ramus of the mandible that is the entrance to the mandibular canal; it transmits the inferior alveolar nerve, a branch of the posterior division of the mandibular division of the trigeminal nerve that supplies all the ipsilateral teeth up to the midline
SYN: abnormal inferior alveolar foramen morphology
SOURCE: https://radiopaedia.org/articles/mandibular-foramen-1
absent mandibular foramen
DEF: absence of the opening that is normally located on the medial surface of the ramus of the mandible and forms the entrance to the mandibular canal
Annotation in J:13048

abnormal mandibular foramen morphology MP:0030234
absent mandibular foramen MP:0030235


[ETCM-492] Crossbuild against Scala-2.12 and Scala-2.13

We just need to understand why CI isn't building your commits. @KonradStaniec do you know?

And it would be good to include the ticket in the commit messages as well so we get a good history.

And I forgot but could you update the README with examples of calling the stuff with the csm[_] and specific versions as well? And update the single example.

@aakoshh about CI imo it has something to do that the source branch is from forked repo dmitry-worker:ETCM-492-crossbuild-scala-2.13. I saw this several times that CI only properly handles pr's from the same repo.

and about your earlier comments about release cycle, I am all for updating it to some form of gitflow, with a little bit of automation. It is probably time to think about such things, as library is now used in two projects, so release cycle and some form of backward compatibility will more important now

Need to re-create PR in order to CI procedures.


Contributing md file

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Having a Contributing.md file help the new contributors to understand the process of how to contribute to this project.
Describe the solution you'd like
I think the project should have a contributing.md file.
If it sounds good then you can assign this to me I will add the file.
Describe alternatives you've considered
No response
Additional context
No response

Hi @Jason2605 ,
I have added the Contributing.md file here. Let me know if it looks good or if you want me to make any changes.


Fix T292365 bug

\cc @inikulin @churkin

lgtm

Regression test?
\r-

I fixed existing regression test for these conditions.
FPR

@helen-dikareva What about comment in test?

Sorry. Added now.

lgtm


az interactive doesn't work

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az interactive
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/homebrew/Cellar/azure-cli/2.41.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
    azext_interactive.start_shell(cmd, style=style)
  File "/Users/vadymmykolaichuk/.azure/cliextensions/interactive/azext_interactive/__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "/Users/vadymmykolaichuk/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az interactive

Expected Behavior
Environment Summary
macOS-12.6-arm64-arm-64bit, Darwin 21.6.0
Python 3.10.8
Installer: HOMEBREW

azure-cli 2.41.0

Extensions:
arcdata 1.4.7
azure-devops 0.25.0
interactive 0.4.5
account 0.2.5

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Feature Request: OTA updates to future releases

Hi,
First of all, thank you for all the hard work.
As the title says, an OTA update feature would be nice. That way, the updates would be smooth. Don't know how much of a big lift that is.

@TheGammaSqueeze  any chance the OS gets updated to Android 13/14? RG505 should be capable right?


bug: Module 'Lazy' not found

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.9.1
Operating system/version
MacOS M1 AIR 13.4.1
Describe the bug
I have a windows pc already with my lazyvim configuration, my mac and my windows have the same version of neovim and the same version of LuaJIT the 2.1.0-Beta3.
Basically I am trying to install a basic version of lazyvim that is in your page, not the one in my github and I get the following error https://www.lazyvim.org/installation

Also tried, uninstalling neovim and installing again using homebrew and tar.gz file, deleting using the command sudo rm -r ~/.config/nvim and the shares and state nvim folders, then opening nvim, no errors AND then cloning the github and using nvim, error happened.
Also deleting the folders > turning off the mac > on again > nvim no errors > cloning the github > nvim and error happened.
Comand when I refer to "cloning the github" git clone https://github.com/LazyVim/starter ~/.config/nvim
I checked the issues in this github, the lazy.nvim and folke comments on reddit about this issue, a complete delete of the nvim folders did not resolve the problem :(
Steps To Reproduce

mv ~/.config/nvim ~/.config/nvim.bak
mv ~/.local/share/nvim ~/.local/share/nvim.bak
mv ~/.local/state/nvim ~/.local/state/nvim.bak
mv ~/.cache/nvim ~/.cache/nvim.bak
git clone https://github.com/LazyVim/starter ~/.config/nvim
nvim

Expected Behavior
Expectation is no error
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

the error can't find lazy.nvim at ~/.local/share/nvim/lazy/lazy.nvim.
That or there's something odd happening with your Neovim installation or XDG dirs

I'm having the same issue on Windows


First time use

Hi Frank,
First of all, a great idea of a shortner that you can manage yourself. I have deployed it to my own Azure subscription, but I can't get it to work. I must say, I'm not a developer so a lot of your info and comments are hard to understand (but with the help of google I seem to get further).
I've managed to install everything and log in to the web app, but then I'm stuck. There is no 'Add' button when you don't have a URL at all.
I've tried it with Postman (way out of my league), but I can't get the info because a link runs dead (https://github.com/FBoucher/AzUrlShortener/blob/master/src/adminTools/postman/README.md) the link for 'get the URL's'.
So if you have any info to get me a bit further that would be great!
Regards,
Jordy

I will review the deployment instruction. Can you help me by identifying where it became not clear (or less clear)?

Hi Frank,
I'm glad I can help. Hopefully this info can help you to improve the documentation.
The post-deployment info:

info about a custom domain from Microsft is clear
the FunctionApp screen is in the App Service Plan and not in the App Service (although the icons seem to indicate this). took me a while to find this ;-)
But when I found it, my screen doesn't represent the same as yours (I don't see any functions):

On the Postman page:
-I can go to the Postman page because the link is there. but having no coding experience or not being a developer, what should I do and where should I go?
-The link for getting the URL's is dead, I get a 404
-Create Short URL, I think the Postman usage needs more explaining. What URL do I need, do I need to add Extra bits (/api/ ?) in the URL, how to add the code (in the end I found it in Visual Studio Code).
Admin Blazor Frontend
The screenshot doesn't represend what I have in My screenshot. I also have some info that is already present an some is not there at all, should I alter it or has it been changed recently?

hopefully this is info you can use to improve the documentation. Iif you need more help in reviewing, let me know!
Jordy

I think your deployment failed.
You don't have any functions in the Functions tree node.
I suggest you delete the resource group and start over.


Improve performance of mergeReactProps

[x] I have followed (at least) the PR section of the contributing guide.

The mergeReactProps function uses a regex to identify event handlers and invoke them all. Since it is a low-level utility, I believe it should be optimized for performance, even at the expense of some readability.
Just suggesting an alternative approach that doesn't rely on using a regex.

Thank you for the PR!
However it seems like they're practically identical in performance to the point that the bundle size cost would instead be the more impactful trade-off?

@atomiks This can be true for high-end devices, especially in desktop environments (in my case, regex is about 20% slower). However, the drop in performance is much more noticeable on mobile devices. In a large app, this regex might be invoked hundreds or even thousands of times, making this optimization potentially worthwhile. https://github.com/mui/base-ui/assets/100380515/a0f67ad4-17b4-46ea-8166-ec07a6ef4ed2

@marcpachecog ok seems fine to me then!


[CONTROLLER/HTTP] adds vtap vif api permission check

This PR is for:

Server

adds vtap vif api permission check
Checklist

[ ] Added unit test.

Backport to branches

main
v6.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


I want to vote

Discussed in https://github.com/snapshot-labs/snapshot/discussions/767

Originally posted by metrox-eth September 29, 2021
Suggest answers below or vote for an answer.

0xa4869b07aD340a0dfFdA3Fc62C1159C691cb88cd


Readme example doesn't work

Thanks for the convenient GH action script :-)
For https://github.com/cilium/cilium/pull/13770 , I found that the readme example using the path ~/.clang does not work, neither does .clang. However, if I configured it to $HOME/.clang then it would work.

Thanks for the report, I changed the example directory to ${{ runner.temp }}/llvm which is what I use in my projects and I know it works on every operating system.


With Gradle, Save Action kicking off 1 build for every Java file

I think this is a regression as I've had this problem before.
With the Build actions "Compile Files(using "Build>Build Project") checked, it frequently kicks off several hundred builds which may correspond for each of the Java files.   Ideally, I should see only one build.
Let me know if this doesn't ring any bells and I'll provide logs or screen shots.

Hey guys, compile and reload are buggy, I'll have to deactivate them they cause too many problems.

Duplicates #209

You can disable the "Compile files" under the Build actions.    I now
trigger is manually or when I try to run something.
On Mon, Aug 26, 2019 at 2:12 PM Andre Lanouette<EMAIL_ADDRESS>wrote:

I'm experiencing the same issue on my end. It used to do it every now and
then, now I keep encountering it every few minutes and requires me to
restart IntelliJ to get back to work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dubreuia/intellij-plugin-save-actions/issues/256?email_source=notifications&email_token=AHQ4UUNBUNC6O52U6QPDZ2TQGQMHBA5CNFSM4IPPI2H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5FF4TA#issuecomment-524967500,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQ4UUOYO2BLK4F3MIEWJA3QGQMHBANCNFSM4IPPI2HQ
.


feat(app): register v7.0.0 software upgrade

Register a new v7.0.0 software upgrade 😎

Summary by CodeRabbit

New Features

Introduced a new system for managing application upgrades, including a specific upgrade handler for version 7.0.0.

Refactor

Updated the method for registering upgrade handlers to improve the upgrade process.

:tada: This PR is included in version 7.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use Land Geometries

I'm hoping to use a less detailed map, one that just does the land geometries. I'm new to Topojson, but it looks like it's also in the file. How can I get react-simple-maps to use the land instead of countries geometry?
Thanks!

import worldData from '/path-to-json/worldMap_scale_50m.json';
import { feature } from "topojson-client";

const {objects: {land}} = worldData;
const landData = feature(worldData, land).features;

then
<Geographies geographyPaths= landData} > ... </Geographies>

This should not be an issue btw, it's already in the documentation

Hi mattoni,
There's a good resource to get prepared topojson files for the world here:
https://github.com/topojson/world-atlas#world/110m.json_land
Here's a direct link to what you need. You can download this and reference it in geographyUrl of the <Geographies /> component, and you should be good to go:
<EMAIL_ADDRESS>From there, just use the basic usage approach from the documentation. Hope this helps you.

Sorry @jinqiupeter I didn't think it was very clear in the README, it didn't really explain how to do anything other than use the url to the file. Thanks for the clarification though, I think I can take it from here. :)

@mattoni No problem. I agree that it's not clear in the documentation. I realized it can be done this way after reading the source code.

geographyPaths has better documentation now (6b807dec2fcf0678b7bd7d365aad96d7868f161e), and there is also an example on how to use it to load your custom TopoJSON into react-simple-maps.
See: https://github.com/zcreativelabs/react-simple-maps/tree/master/examples/custom-json-geographyPaths


feat: load config from env-var or also /etc/evcc

enable setting the configuration information also as env variable within the container. This environment variable is also used when running commands within the contianer
add /etc/evcc as configuration directory as it is easier to mount stuff into a folder when using any orchestrator

Not quite sure if we need this. Mapping a file instead of a folder seems straight- forward? If possible I would like to avoid introducing additional config locations.

ping @mabunixda


S3 Select: gzip input and CSV output

I'm testing some code that uses S3 Select and have a need for two unsupported features:

Gzip-encoded input (in my case the compressed content is CSV, although I don't think that matters)
CSV output (right now it only outputs JSON)

I was able to get the gzip working pretty easily with this code snippet (in s3/models.py:select_object_content):
if input_details.get('CompressionType') == 'GZIP':
    import gzip
    from io import BytesIO
    with gzip.open(BytesIO(key.value), 'rt') as f:
        query_input = f.read()
else:
    query_input = key.value.decode("utf-8")  # type: ignore

The CSV output seems a bit trickier.

Hi @LucasPickering, thanks for raising this - will mark it as an enhancement.

Hi @LucasPickering, both features are now part of moto >= 5.0.4.dev46.
Please let us know if you run into any other issues.


Notebook Search: Sometimes not all find items are highlighted in a code cell

Search for "specified_Subscription"
Find 8 results in import-sql-server.ipynb in Azure SQL Hybrid Cloud Toolkit book, but only first one is highlighted.

@lucyzhang929 was this a regression previously?

No this was not a regression.

Thanks @lucyzhang929. Moved to August as a result.

Updated repro steps:

Search for "specified_Subscription"
Click on first notebook (export-sql-server.ipynb) -> all results will be highlighted
Click on second notebook (import-sql-server.ipynb) -> all results will be highlighted
Click on first result again (export-sql-server.ipynb)
Expected: all results highlighted
Actual: only first result is highlighted


sasview: init at 4.1.2

Motivation for this change
Sasview is a data fitting and analysis package for small angle scattering data.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

I'm now using html5lib from python-packages and merely overriding the version.  This has also allowed me to move xhtml2pdf into the python-packages.nix, instead of making it part of sasview.
I've also done just a bit of cleanup as I was manually importing licenses into a couple of the packages for no good reason.

@matthewbauer This one created a conflict. I manually merged master into staging right now.


Last row in editor not visible

The last row of text in the editor is not visible for me (I'm using chrome). The text is visible in the preview document and if I continue writing on the bottom row when I've moved down with the arrows on my keyboard the text appears in the preview, but I still can't see it or access it otherwise.
Additional Details
Share Link :
or
Brew code to reproduce : Click to expand
PASTE BREW CODE HERE

Screenshot?

@calculuschild, @ericscheid, I suggest that we close this one

Closing since there hasn't been a reply from the user for a while and it is assumed the problem was solved.
If you are still experiencing this issue, feel free to reopen and provide information, @sanwae


Python code not waiting for Tweepy wait_on_rate_limit

I am using the Tweepy Twitter API and Python to retrieve a fairly large number of tweets (~40,000) using this code:
def getTweets(query, num):
    #gets the specified number of tweets
    _max_queries = 100

    tweets = tweet_batch = api.search(q=query, count=num, tweet_mode='extended')
    ct = 1
    while len(tweets) < num and ct < _max_queries:
        print("Got %d tweets!" % (len(tweets)))
        tweet_batch = api.search(q=query, count=num-len(tweets), max_id=tweet_batch.max_id, tweet_mode='extended')
        tweets.extend(tweet_batch)
        ct += 1
    return tweets

I have api wait_on_rate_limit set to true. Immediately, after I call the getTweets() function I attempt to process the tweets. Only problem is that Python is not waiting for Tweepy's rate limit to reset and is proceeding with executing the process code prematurely. For example, if I try to pull 20,000 tweets Tweepy pulls about 9,000 and immediately processes them rather than waiting for the rate limit to reset, and pulling the rest of the tweets. Any suggestions?

I moved it to it's own thread and I think that it is not waiting for the 9000 tweets. It pulls the 9000 and continues. Any idea whats going on? Is there some kind of limit on the API or something?

I would also appreciate an answer on that, as it seems that it makes no difference to use the wait_on_rate* flags whilst instantiating the API class

Why not just use the python method 'time.sleep()'?
https://www.tutorialspoint.com/python/time_sleep.htm

The maximum count for the standard search API is 100.
This means you'll receive up to the maximum of 100 Tweets per request. (Twitter's API will sometimes return less than the set count/maximum.)
You set _max_queries to 100 (and ct to 1), so you only ever make 99 requests, meaning you'll get a maximum of 9,900 Tweets.
Your code is working, and this has nothing to do with wait_on_rate_limit.
I would recommend you look into using Cursor instead.


Update README.md

What's Changing and Why
Please, ref to #609.
What else might be affected
Nothing except for README.md.
Tasks

[ ] Add tests
[x] Update Documentation
[ ] Update jimp.d.ts
[ ] Add SemVer Label

@hipstersmoothie, hey.
Please, take a look at this PR. I've tried to explain as much detail as possible. It was a little bit hard because Phin parses a URL under the hood, merges a parsed URL with the other passed properties, and then passes the whole object as an options to http.request() or https.request() methods... And blebleble.

@hipstersmoothie, fixed it. Please, take a look when you have time. Thanks.


Please update known issues: does not work for flows created outside the solution

Please add a note that this functionality is only useful if you manually create each child and parent flow in a solution. There is no ability to re-use and adapt or extend flows created outside of solutions or in other solutions.

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

ID: e7f42c36-4ce0-fff2-4cfb-e191c636edf4
Version Independent ID: 510353c0-7e45-0302-d7d4-80c68bff7eb4
Content: Call Child Flows - Power Automate
Content Source: articles/create-child-flows.md
Service: business-applications
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@packnology Thanks for reporting this issue. We'll update the docs.

@packnology Please clarify what you mean here. The docuement says that you will need to have both the child and parent in a solution. Is there something that we missed?

@MSFTMan I was just suggesting to specify that the child and parent must actually be created within the solution (can't be imported), which means there's no ability to "template" a parent-child configuration for re-use in other solutions (which would be really useful for developers).

@packnology We've updated the documentation as follows:
You must create the parent flow and all child flows directly in the same solution. If you import a flow into a solution, you will get unexpected results.


Only geocode on save() if it hasn't been done

This is weird because parts of the address may change. Punting it for now.


Issue compiling under Visual Studio 2010

As reported by Mark Rivers on the netcdfgroup mailing list related to Visual Studio 2010 compilation.  Compiling doesn't work, the attached patch fixes it.

libdispatch_vs2010.patch.zip


RFC add a menu to category pages

Based on @tooomm 's https://github.com/badges/shields/pull/1808#issuecomment-409732290 on the new front-end design, I have put together a rough implementation based on that screenshot. This isn't intended as ready-to-merge, but it gives me a way to deploy something to staging so we can test something and move the conversation on.
A horizontal menu is probably not great for mobile users, so I've hidden it at low-res for now. In general I'd like to move towards a more mobile-friendly front-end although I'm aware that right now we are rendering most of our content in tables.
Something like this is probably OK as long as we have a relatively small number of categories (we've just increased to 11), but as discussed in https://github.com/badges/shields/pull/1762#issuecomment-403583651 I can see a case for moving to a situation where we might have a much larger number of menu items. I wonder if anyone has any ideas about how we could present this, particularly if we had many more 'categories' or 'headings' (more than you'd want on a single row).
Feedback generally welcome. Also probably worth keeping en eye on the issues as more users see the new layout.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS

staging deploy at https://shields-staging-pr-1842.herokuapp.com

First observations:

The new "menu headline" is not centered
When you switch between categories the old batches stay visible until they get replaced with the new ones. they should be hidden/removed with the category switch.
This can be awkward because sometimes it takes a few seconds until they properly refresh

Both can be seen on this screenshot:

Mind merging master into this branch when you have a moment? I wrote some steps here: https://github.com/badges/shields/pull/1866#issuecomment-411567524

Good idea. Now I can easily move between categories. Before this I have to go back in browser to see all categories.
My note. After page is loaded we have a vertical list of categories. After choosing one category vertical list changes to horizontal. I would like to have it consistent - we can display horizontal list form the beginning.

Given @mbrandau wants to work on menu as part of some wider (much needed) redesign work in #1899 I'm going to put this on hold for the moment as I think it fits there more naturally. If #1899 stalls, I'll revisit this.

Is it worth revisiting and giving this the last finishing (as a interim solution at least)? @chris48s
Currently, it looks like the other approach hasn't been worked on since quite some time.

With more categories being added such as Activity #2448, It may be worth pushing ahead with this.

@chris48s Would you like me to pick this up after #2441 is merged? Or would you like to tackle it?

I'm not particularly attached to it. I'm aiming to try and have a look at #2441 tomorrow. If you want to have a go at this once that's in, feel free. Cheers


[FEAT] User Status Filtering  - BACKEND

Description
Implement filtering for users in organisation based on their status (members, suspended, left workspace).
Acceptance Criteria

Filtering:

Implement server-side logic to handle filtering users by their status (members, suspended, left workspace).

User Preferences:

Store user status details securely in the database.
Handle user-specific configurations and preferences related to the filtering process.

Error Handling:

Log errors for invalid filter requests.
Display clear error messages for invalid inputs.

Security Measures:

Use HTTPS for secure data transmission.
Validate user input on the server side.

Purpose
To filter users securely and efficiently, ensuring accurate and safe user management.
Requirements

[ ] Develop server-side logic to handle user filtering.
[ ] Securely store user status details in the database.
[ ] Ensure compliance with security standards for handling user information.

Expected Outcome

The backend should handle user filtering securely and efficiently.
The system should log errors and handle invalid requests appropriately.

Tasks

[ ] Create an endpoint (GET /api/users) to fetch users based on filter criteria.
[ ] Validate user input on the server side.
[ ] Implement server-side logic to handle successful and failed filter requests.
[ ] Ensure all sensitive data is encrypted and secure.
[ ]  Implement logging for errors and filter attempts.
[ ] Write tests for the user filter endpoint.
[ ] Perform security testing to ensure data protection and compliance.

Testing

[ ] Write unit tests for backend validation and filter handling.
[ ] Write integration tests for the end-to-end filter process.
[ ] Perform security testing to ensure data protection and compliance.
[ ] Test various scenarios for user filtering (e.g., valid status, invalid status).

Duplicated

@markessien    This issue continues from issue https://github.com/hngprojects/hng_boilerplate_nestjs/issues/66 which has been closed.

Team   TechTitans slack id:
@kibe - Python
@KingTsonga - Java
@Japhet Paul - PHP
@EAZYLINK - Javascript
@Cliff - c#

Hello @Popsicool @buka4rill,
I have completed the implementation for this issue and received the first approval. Could you please review  and provide the second approval at your earliest convenience?
Thank you!

What is the "last_login_at": "Date" in the response?

It's okay, @Popsicool. I'm working on it.

@Popsicool  Done

Alright, add pagination to it

Add next and prev to your response

Okey

@Popsicool  Done with adding next and prev to the response

cool


TiKV sometimes panic when running tests

Bug Report
TiKV sometimes panic when running tests which cause the RP check failed
Full log output: https://internal.pingcap.net/idc-jenkins/blue/rest/organizations/jenkins/pipelines/tikv_ghpr_test/runs/13036/nodes/147/steps/1123/log/?start=0
[2019-11-26T12:33:36.998Z]
[2019-11-26T12:33:36.998Z] running 8 tests
[2019-11-26T12:33:36.998Z] test _1_check_system_requirement ... ok
[2019-11-26T12:33:36.998Z] test _0_ci_setup ... ok
[2019-11-26T12:33:40.267Z] test pd::test_rpc_client::test_restart_leader_secure ... ok
[2019-11-26T12:33:40.267Z] test coprocessor::test_select::test_del_select ... ok
[2019-11-26T12:33:42.162Z] test raftstore::test_merge::test_merge_approximate_size_and_keys ... ok
[2019-11-26T12:33:43.091Z] test raftstore::test_snap::test_node_cf_snapshot ... ok
[2019-11-26T12:33:53.065Z] thread 'raftstore::test_stale_peer::test_server_stale_peer_out_of_region' panicked at 'region Some(id: 1 region_epoch { conf_ver: 8 version: 1 } peers { id: 3 store_id: 3 } peers { id: 4 store_id: 4 } peers { id: 5 store_id: 5 } peers { id: 6 store_id: 6 }) has peer id: 3 store_id: 3', components/test_raftstore/src/pd.rs:771:9
[2019-11-26T12:33:53.065Z] stack backtrace:
[2019-11-26T12:33:53.065Z] test raftstore::test_prevote::test_prevote_partition_leader_in_majority_detect_in_majority ... ok
[2019-11-26T12:33:53.065Z]    0: backtrace::backtrace::libunwind::trace
[2019-11-26T12:33:53.065Z]              at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.35/src/backtrace/libunwind.rs:88
[2019-11-26T12:33:53.065Z]    1: backtrace::backtrace::trace_unsynchronized
[2019-11-26T12:33:53.065Z]              at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.35/src/backtrace/mod.rs:66
[2019-11-26T12:33:53.065Z]    2: std::sys_common::backtrace::_print
[2019-11-26T12:33:53.065Z]              at src/libstd/sys_common/backtrace.rs:47
[2019-11-26T12:33:53.065Z]    3: std::sys_common::backtrace::print
[2019-11-26T12:33:53.065Z]              at src/libstd/sys_common/backtrace.rs:36
[2019-11-26T12:33:53.065Z]    4: std::panicking::default_hook::{{closure}}
[2019-11-26T12:33:53.065Z]              at src/libstd/panicking.rs:200
[2019-11-26T12:33:53.065Z]    5: std::panicking::default_hook
[2019-11-26T12:33:53.065Z]              at src/libstd/panicking.rs:214
[2019-11-26T12:33:53.065Z]    6: std::panicking::rust_panic_with_hook
[2019-11-26T12:33:53.065Z]              at src/libstd/panicking.rs:477
[2019-11-26T12:33:53.065Z]    7: std::panicking::continue_panic_fmt
[2019-11-26T12:33:53.065Z]              at src/libstd/panicking.rs:384
[2019-11-26T12:33:53.065Z]    8: std::panicking::begin_panic_fmt
[2019-11-26T12:33:53.065Z]              at src/libstd/panicking.rs:339
[2019-11-26T12:33:53.065Z]    9: test_raftstore::pd::TestPdClient::must_none_peer
[2019-11-26T12:33:53.065Z]              at components/test_raftstore/src/pd.rs:771
[2019-11-26T12:33:53.065Z]   10: test_raftstore::pd::TestPdClient::must_remove_peer
[2019-11-26T12:33:53.065Z]              at components/test_raftstore/src/pd.rs:856
[2019-11-26T12:33:53.065Z]   11: integrations::raftstore::test_stale_peer::test_stale_peer_out_of_region
[2019-11-26T12:33:53.065Z]              at tests/integrations/raftstore/test_stale_peer.rs:61
[2019-11-26T12:33:53.065Z]   12: integrations::raftstore::test_stale_peer::test_server_stale_peer_out_of_region
[2019-11-26T12:33:53.065Z]              at tests/integrations/raftstore/test_stale_peer.rs:94
[2019-11-26T12:33:53.065Z]   13: integrations::raftstore::test_stale_peer::test_server_stale_peer_out_of_region::{{closure}}
[2019-11-26T12:33:53.065Z]              at tests/integrations/raftstore/test_stale_peer.rs:91
[2019-11-26T12:33:53.065Z]   14: core::ops::function::FnOnce::call_once
[2019-11-26T12:33:53.065Z]              at /rustc/c6e9c76c59e3c10acd63ca9ec157a8894ea1a068/src/libcore/ops/function.rs:227
[2019-11-26T12:33:53.065Z]   15: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
[2019-11-26T12:33:53.065Z]              at /rustc/c6e9c76c59e3c10acd63ca9ec157a8894ea1a068/src/liballoc/boxed.rs:922
[2019-11-26T12:33:53.065Z]   16: __rust_maybe_catch_panic
[2019-11-26T12:33:53.065Z]              at src/libpanic_unwind/lib.rs:80
[2019-11-26T12:33:53.066Z]   17: std::panicking::try
[2019-11-26T12:33:53.066Z]              at /rustc/c6e9c76c59e3c10acd63ca9ec157a8894ea1a068/src/libstd/panicking.rs:275
[2019-11-26T12:33:53.066Z]   18: std::panic::catch_unwind
[2019-11-26T12:33:53.066Z]              at /rustc/c6e9c76c59e3c10acd63ca9ec157a8894ea1a068/src/libstd/panic.rs:394
[2019-11-26T12:33:53.066Z]   19: test::run_test::run_test_inner::{{closure}}
[2019-11-26T12:33:53.066Z]              at src/libtest/lib.rs:1413
[2019-11-26T12:33:53.066Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[2019-11-26T12:33:53.066Z] test raftstore::test_stale_peer::test_server_stale_peer_out_of_region ... FAILED

/info

Duplicate bug
https://github.com/tikv/tikv/issues/7183


Pushdemont cup is an option which does push

Cup doesn't compile well. It can't compile with module capitalism. So it essentially doesn't compile with any known module in the current app ecosystem


Copy-on-write representation in SIL: instructions and builtins

This is the first PR for copy-on-write (COW) representation in SIL. It adds new SIL instructions and instruction flags and builtins which can be used in the stdlib to create the new SIL instructions.
It's still a NFC (regarding the generated code) because the new instructions and builtins are not used in the library yet.
The goal is to have a clean representation of COW data structures in SIL, most importantly for stdlib's Array. It helps the optimizer and avoids hacks in the code where we currently have to hard code the Array type.
For example, the optimizer then knows that an Array is immutable when this array is immutable in the source code. This is currently not the case.
Note that this work is purely about the SIL representation and not about a language feature. The builtins allow to use the COW representation in the stdlib. It's possible to create a nicer language feature around this, but this is not in the scope of this work.
I added a section in SIL.rst which gives an overview of the COW representation. I copy it here for convenience:
Copy-on-Write Representation
Copy-on-Write (COW) data structures are implemented by a reference to an object
which is copied on mutation in case it's not uniquely referenced.
A COW mutation sequence in SIL typically looks like:
    (%uniq, %buffer) = begin_cow_mutation %immutable_buffer : $BufferClass
    cond_br %uniq, bb_uniq, bb_not_unique
  bb_uniq:
    br bb_mutate(%buffer : $BufferClass)
  bb_not_unique:
    %copied_buffer = apply %copy_buffer_function(%buffer) : ...
    br bb_mutate(%copied_buffer : $BufferClass)
  bb_mutate(%mutable_buffer : $BufferClass):
    %field = ref_element_addr %mutable_buffer : $BufferClass, #BufferClass.Field
    store %value to %field : $ValueType
    %new_immutable_buffer = end_cow_mutation %buffer : $BufferClass

Loading from a COW data structure looks like:
    %field1 = ref_element_addr [immutable] %immutable_buffer : $BufferClass, #BufferClass.Field
    %value1 = load %field1 : $*FieldType
    ...
    %field2 = ref_element_addr [immutable] %immutable_buffer : $BufferClass, #BufferClass.Field
    %value2 = load %field2 : $*FieldType

The immutable attribute means that loading values from ref_element_addr
and ref_tail_addr instructions, which have the same operand, are
equivalent.
In other words, it's guaranteed that a buffer's properties are not mutated
between two ref_element/tail_addr [immutable] as long as they have the
same buffer reference as operand.
This is even true if e.g. the buffer 'escapes' to an unknown function.
In the example above, %value2 is equal to %value1 because the operand
of both ref_element_addr instructions is the same %immutable_buffer.
Conceptually, the content of a COW buffer object can be seen as part of
the same static (immutable) SSA value as the buffer reference.
The lifetime of a COW value is strictly separated into mutable and
immutable regions by begin_cow_mutation and
end_cow_mutation instructions::
  %b1 = alloc_ref $BufferClass
  // The buffer %b1 is mutable
  %b2 = end_cow_mutation %b1 : $BufferClass
  // The buffer %b2 is immutable
  (%u1, %b3) = begin_cow_mutation %b1 : $BufferClass
  // The buffer %b3 is mutable
  %b4 = end_cow_mutation %b3 : $BufferClass
  // The buffer %b4 is immutable
  ...

Both, begin_cow_mutation and end_cow_mutation, consume their operand
and return the new buffer as an owned value.
The begin_cow_mutation will compile down to a uniqueness check and
end_cow_mutation will compile to a no-op.
Although the physical pointer value of the returned buffer reference is the
same as the operand, it's important to generate a new buffer reference in
SIL. It prevents the optimizer from moving buffer accesses from a mutable into
a immutable region and vice versa.
Because the buffer content is conceptually part of the
buffer reference SSA value, there must be a new buffer reference every time
the buffer content is mutated.
To illustrate this, let's look at an example, where a COW value is mutated in
a loop. As with a scalar SSA value, also mutating a COW buffer will enforce a
phi-argument in the loop header block (for simplicity the code for copying a
non-unique buffer is not shown)::
  header_block(%b_phi : $BufferClass):
    (%u, %b_mutate) = begin_cow_mutation %b_phi : $BufferClass
    // Store something to %b_mutate
    %b_immutable = end_cow_mutation %b_mutate : $BufferClass
    cond_br %loop_cond, exit_block, backedge_block
  backedge_block:
    br header_block(b_immutable : $BufferClass)
  exit_block:

Two adjacent begin_cow_mutation and end_cow_mutation instructions
don't need to be in the same function.

@swift-ci smoke test

@swift-ci smoke test

@atrick Thanks for reviewing! I pushed a new version

@swift-ci smoke test and merge

@swift-ci smoke test and merge


'NumberKit' requires minimum platform version 12.0

Description
The following error occurred when adding the sdk to a simple project
The package product 'NumberKit' requires minimum platform version 12.0 for the iOS platform, but this target supports 9.0
Steps to reproduce
created a simple iOS project
added Hedera package
Clicked run
Additional context
No response
Hedera network
testnet
Version
beta
Operating system
No response

This is not a bug and is by intention. iOS versions before 13 are officially discontinued by Apple and should neither be used nor developed for.
Please update the minimum platform version in your project.

It does not help if you set the minimum platform version on the project level.
I have the exact same issue as @gregscullard mentioned.


Runtime C API: append_bytecode_module_from_memory bytespan ownership

What happened?
This is the api documentation of the function iree_runtime_session_append_bytecode_module_from_memory
// Appends a bytecode module to the context loaded from the given memory blob.
// If the module exists as a file prefer instead to use
// iree_runtime_session_append_bytecode_module_from_file to use memory mapped
// I/O and reduce total memory consumption.
//
// The data must remain valid for the lifetime of the session. If a
// |flatbuffer_allocator| is provided then it will be used to free the
// |flatbuffer_data| when the module is destroyed. This call always consumes the
// data and even if the module fails to load or be registered with the session
// the |flatbuffer_allocator| will be used to release it.
//
// NOTE: only valid if the context is not yet frozen; see
// iree_vm_context_freeze for more information.
IREE_API_EXPORT iree_status_t
iree_runtime_session_append_bytecode_module_from_memory(
    iree_runtime_session_t* session, iree_const_byte_span_t flatbuffer_data,
    iree_allocator_t flatbuffer_allocator);

I want iree_runtime_session_append_bytecode_module_from_memory not to free flatbuffer_data. It says that "If a flatbuffer_allocator is provided then it will be used to free the flatbuffer_data when the module is destroyed", but I can't find a way to NOT pass the allocator.
If I try to pass a null allocator that does nothing, it outputs:
Status: "iree/runtime/src/iree/vm/context.c:238: INTERNAL; import function hal.allocator.allocate signature
mismatch between arithmetic and source hal; expected 0riiI_r but got 0rIiiI_r; resolving module 'arithmetic' imports"

Is there any way to get around this?
Steps to reproduce your issue

Go to '...'
Click on '....'
Scroll down to '....'
See error

What component(s) does this issue relate to?
No response
Version information
https://github.com/openxla/iree/commit/2b9ade513428ed9c0714134f120a50024c5718b5
Additional context
No response

The null allocator should work just fine. I suspect you are not honoring the "The data must remain valid for the lifetime of the session." part of the comment: if you free the memory before the session is destroyed things will explode. Or, it's something completely unrelated.

Upon debugging, it appears that the bug originates from an unrelated source from this issue. Thanks for your response!

Well, I have yet to find out what went wrong here :(
DEBUG runtime: vmfb ptr: 0x12d02d200
DEBUG iree_rs::runtime::api: Appending bytecode module from memory...
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_CALLOC: size: 584 -> 0x11c643e80
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_CALLOC: size: 16 -> 0x6000006222f0
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_CALLOC: size: 16 -> 0x600000622110
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE: size: 8->0x6000006223f0
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE: size: 8->0x600000621b30
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_CALLOC: size: 1184 -> 0x11c8b2c10
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE: size: 1184->0x11c8b2c10
DEBUG iree_rs::runtime::base: null_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE, 0x12d02d200
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE: size: 584->0x11c643e80
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_CALLOC: size: 216 -> 0x600003943670
DEBUG iree_rs::runtime::base: rust_allocator_ctl: IREE_ALLOCATOR_COMMAND_FREE: size: 216->0x600003943670
thread 'append_module' panicked at 'called `Result::unwrap()` on an `Err` value: StatusError(Status: "iree/runtime/src/iree/vm/context.c:238:
INTERNAL; import function hal.allocator.allocate signature mismatch between arithmetic and source hal;
expected 0riiI_r but got 0rIiiI_r; resolving module 'arithmetic' imports")', tests/runtime.rs:77:56

I've been troubleshooting this issue but haven't been able to identify the root cause. The error message seems to indicate a signature mismatch in the import function, specifically related to 'arithmetic' imports. I would greatly appreciate it if you could provide some insights or suggestions on where I should focus my investigation to resolve this issue. Any help would be highly valuable.

The error message seems to indicate a signature mismatch in the import function.

This is likely due to the breaking HAL change in https://github.com/openxla/iree/commit/f022d29ad6d9c9ba793e08e529c0472a6b43af12

Breaking compiler/runtime changes are infrequent (a few each year). I thought we might have some version checking that could give better error messages, but maybe not...
Assuming the version info in your issue description is for the runtime, you could try updating your version of the compiler. From pip, you can do that by either switching to a nightly release by adding --find-links https://openxla.github.io/iree/pip-release-links.html to your pip install commands (docs: https://www.iree.dev/reference/bindings/python/#prebuilt-packages) OR by waiting a little bit. I'm just about to push a new stable release (https://groups.google.com/g/iree-discuss/c/_cBAm5VubN4/m/0-v0t9qvAwAJ).

(Update the compiler and use that newer compiler tool to regenerate the .vmfb file that you pass to the more recent runtime using iree_runtime_session_append_bytecode_module_from_memory)

Problem solved! Thank you for helping out.


add tests to okwolo-dom and okwolo-router using different browsers

might be easier to make a browser runnable test that is not automated
can also include #59


Cannot drag the dropdown scrollbar in IE11 in v3

This is the same issue as #36, but I'm seeing it in v3. I don't think I could reproduce it before upgrading to react v16 (which is when I upgraded to v3)

When the dropdown is a long list, the scrollbar appears.
However, in IE11, whenever you try to use your mouse to drag the scrollbar to scroll down, it immediately close the dropdown.

This is reproducible on the demo page

I found this in ReactSelectize.ls
# to prevent closing the dropdown when the user tries to click & drag the scrollbar in IE
return if @refs.dropdown-menu and document.active-element == (find-DOM-node @refs.dropdown-menu)

but document.active-element seems to be set to the body tag when this gets called

Same behavior but in latest chrome
Dropdown was placed inside of React Bootstrap Modal

yep came here to report the same issue on Chrome


fix: Prevent NullPointerException when Throwable.getMessage returns null

Throwable.getMessage() can return null but ImmutableMap may not keep
nulls, so we store "" instead.
We pass an exception instance to the constructors for convenience.
Note that ThreadInterruptedError was not updated since we plan to remove
it.

@lionel-nj
Updated to resolve merge conflicts.


Proposed Graphic and Text updates SAP-S4HANA

Hi!
Arnt de Gier here, TME for Azure NetApp Files with NetApp.
I have the following suggestions for updating this article:

As per the attached updated graphic, please insert Azure NetApp Files icons in the boxes Database subnet and Database Replica.

Update the 2 outdated Azure NetApp Files icons to the new (current) ones.

Replace the text Dedicated storage subnet to Delegated storage subnet (2x).

Add dotted lines from Azure NetApp Files in Region 1 to Region 2 and add text Azure NetApp Files Cross Region Replication (2x).

Text updates per

In the “Performance” section add at the very bottom this sentence:

ANF has unique performance features that allow for real time tuning that meet the needs of the most demanding SAP environments.  For performance considerations using ANF see here.
In above sentence, hyperlink the last word 'here' to https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse#sizing-for-hana-database-on-azure-netapp-files

[Enter feedback here]

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

ID: 009774ee-d1e4-1d7b-e53f-ecbcc4d56e5d
Version Independent ID: d14a99bb-b4d5-21ce-dd72-5759a8284c42
Content: SAP S/4HANA in Linux on Azure - Azure Architecture Center
Content Source: docs/reference-architectures/sap/sap-s4hana.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @EdPrice-MSFT
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 525968

Thank you for your feedback.  We have created internal ticket 24196 to track and investigate this issue.

#please-close


'import' and 'export' may appear only with 'sourceType: module'

I'm working on implementing Android support, but I'm running into this error when importing OAuthManager on a fresh RN project:
'import' and 'export' may appear only with 'sourceType: module'

Sounds like a Babel issue maybe? It's an entirely fresh project, so it's just using the react-native preset. Do I need to add any extra configuration to get this to work?

Weird. Can you push your source open-source? If not, I would be happy to hop on screenhero (can send you an invite if you need one)

@naiyt I can't replicate this... I've updated the README and built it off a fresh project here... any more hints as to how/when you encountered this?

Weird, tried again today and now I can't replicate it either. Clearly must have been a PEBKAC problem of some sort. =\ Sorry about that.


[CARBONDATA-2765]handle flat folder support for implicit column

Handle flat folder for implicit column
Problem:
for implicit column, the blocklet id was getting wrong beacuse of path, as the carbondata files will be present after table path in case of flat folder.
Solution:
check whether the table is standard table(where store path is Fact/Part0/Segment_), if not, form the blocklet id correctly(in case of flat folder)
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NA

[x] Any backward compatibility impacted?
NA

[x] Document update required?
NA

[x] Testing done
Added UT and tested in three node cluster
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7364/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7367/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6129/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7371/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6132/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5942/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6151/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7398/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6158/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7408/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7412/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6171/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5972/

retest sdv please

retest sdv please

LGTM

retest this please

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5997/

@ravipesala please review the changes in BlockDatamap

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7513/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7514/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6269/


screen gets too dim

Caffeinetile works only partly: after 30s my screen turns very very dim, hardly readable, but still remains on. This happens when caffeine is activated. Without it the screen just turns of add expected. I think this dimming of the screen beyond usable is nor intented, maybe a bug?

Hi there. It's not exactly a bug, but I can see how you might think it is.
The way caffeinetile works is by asking Android to keep the screen on. There are actually two options when doing that: allow the screen to dim, or keep it on full tilt.
I'll see if I can make this behavior configurable.

Oh that was a quick answer. I've used the build-in caffeine tile on some ROM that had it, and there the screen maintained the same brightness during the whole "coffee break". I really enjoy this option, but if the screen dims, I find it the same as if I wasn't using caffeine from the usability's point of view
Thanks for looking into it!

I've just pushed a new tag (1.3), which should get built by F-Droid within a few days. When that update hits your phone, you should get into the preferences screen of Caffeine Tile by tapping and holding the tile. There you'll find a new toggle, which, by default, is on, which means the screen is allowed to dim.
Let me know how it works out!

The update has been built on F-Droid, so I'm going ahead and closing this issue. Feel free to reopen if necessary!

It's working beautifully, thanks!
Only thing I'm wondering if users realize the existence of this "hidden" settings menu?


Use golangci-lint for linting

Signed-off-by: Ed Snible<EMAIL_ADDRESS>This adds golangci-lint checking and fixes all of the problems reported by golangci-lint.
The configuration file .golangci.yml is nearly identical to the one we have been using for Jaeger.  The only difference is that we don't blacklist io/ioutil.

I modified the code coverage config file .codecov.yml to allow changes that lower code coverage by <0.1%.
The linter had me remove simplify code.  The lines uncovered by tests didn't change, but the lines covered by tests were less due to the simplification.

E2E tests were passed properly in OpenShift 4.10


Pin the version of edgedb-cli that we use

This will ensure that edgedb and the cli stay in sync, require a test
suite run for cli updates, and make it possible to bisect beyond
cli/server interface breakages.

Should be merged after #3704

This currently pins to the previous cli version, so as written it is designed to be merged before, and for #3704 to be made to update the pin.
The test failures were because I missed updating the code that CI uses to figure out the cli version, which is fixed now.
(That said, if #3704 is made to go green before this, we should merge that first and I'll update the pin on this one)


Result key should support jq based fields

Currently, the scan JSON file contains the result_key which is based on a single key that calls the AWS service function and returns "ResponseMetadata", supporting JQ-based fields in the result_key option to get more granular and shortened results.
Continue to support key based filtering from response
  {
    "function": "list_clusters",
    "service": "emr",
    "parameters": {
      "ClusterStates": [
            "WAITING"
          ]
        },
    "result_key": "Clusters"
}
]

Also, support JQ based filter query
  {
    "function": "list_clusters",
    "service": "emr",
    "parameters": {
      "ClusterStates": [
            "WAITING"
          ]
        },
    "result_key": ".Clusters[]|.Id, .Name"
}
]

https://github.com/aws-samples/aws-auto-inventory/pull/60


Use FusionDirectory 1.4

Hello,
Can we easily edit the dockerfile to make your image work with Fusion Directory 1.4 ?
I need to use Web service REST API which is a plugin in the 1.4 DEV version.
Thank you.

Hi,
I saw that you updated the container's 1.4 tag but the issue seems to still be there :/

I completely butchered that release, my apologies. A new one is available now without all the errors in parsing.


Missing Language?

Program version
Newest
Operating System
Windows
Type
Cli
Service
Crunchyroll
Command used
--
Show ID
G6WE4W0N6
Episode
--
Console Output

Additional Information
No response

Added in 250709dc1d4755415c0a35029c4b3af251ef97b3


feat: Photo storage example

Example React application that shows how to upload files to an assets canister with the @dfinity/assets package.
Related PR https://github.com/dfinity/agent-js/pull/603

Thank you very much for this PR! I'd like to get back to this once https://github.com/dfinity/agent-js/pull/603 is merged. Feel free to ping me when you think I should take another look

Updated MR with above suggestions and fixed some bugs (replaced masonry dep with a more reliable masonry dep)

Also, the rust-basic-bitcoin failed test will be fixed in master in a few minutes

Looking nice, thanks a lot! Any chance you can also add a very basic e2e test to alert us (me) when a dfx update breaks the example? This is a good example you could work from. It doesn't need to be anything fancy

Added a workflow that checks if the project builds and deploys successfully.

With npm i and npm run build I get the following error:
Failed to compile.

Module not found: Error: Can't resolve 'assert' in '/Users/ssiff/Desktop/examples/hosting/photo-storage/node_modules/@dfinity/identity/lib/esm/identity'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
	- install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "assert": false }

Is this a problem introduced by myself or something wrong with the code?

With npm i and npm run build I get the following error:
Failed to compile.

Module not found: Error: Can't resolve 'assert' in '/Users/ssiff/Desktop/examples/hosting/photo-storage/node_modules/@dfinity/identity/lib/esm/identity'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
	- install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "assert": false }

Is this a problem introduced by myself or something wrong with the code?

Seems like a problem in @dfinity/identity 0.14.1, updating dependencies to 0.15.0 seems to fix it.

Thank you for fixing it that quickly! Can confirm it work now. Thank you very much for contributing!


stable/mysql with x protocol

Added the config for allowing the mysqlx protocol

Is this a new chart: No

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it: Enables the port for mysql X plugin so clients can connect with it
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #23641

Special notes for your reviewer:
Have added the following

Exposed 33060 on deployment
Exposed 33060 on service

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@olemarkus, @viglesiasce can you please review this?

/ok-to-test

/lgtm


[DOC] update download button in tutorial and model zoo

Description
doc website fixes.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)

Changes

[x] update download button in tutorial and model zoo. download buttons are now after the first header in the form of a button.
[x] allow horizontal scroll when there is content overflow. (e.g. the huge table in language model)
[x] make navbar responsive.
[x] make header links ¶ appear when hovering the title.

Comments

Require https://github.com/mli/mx-theme/pull/3 to be merged first.

Job PR-746/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/1/index.html

Job PR-746/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/2/index.html

The TOC sidebar looks fine here @szha

Job PR-746/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/3/index.html

Job PR-746/4 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/4/index.html

Job PR-746/5 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/5/index.html

Job PR-746/6 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/6/index.html

Job PR-746/8 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/8/index.html

Job PR-746/9 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/9/index.html

Job PR-746/10 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/10/index.html

Job PR-746/11 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/11/index.html

Job PR-746/13 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-746/13/index.html


Error in version 5.1.0

TypeError: Storage.AudioContext is not a constructor
I have the following error in Firefox, any ideas?

this is related to #44. Should have been solved with #45  but it is not solved entirely.

Do you have any idea why it happens, so I can do workaround or pull request ?


support for the larger noisy student models

Added include_top option to load_efficientnet, making it possible to make notop models for transfer learning
Added efficientnet-b6, b7 and l2

Hi, thanks a lot for PR, did you save weights for converted models?

Yes, i converted the weight file for the noisy student models, i planned upload them here: https://github.com/ThomasHenckel/efficientnet_noisy_student_keras_transfer_learning
I just havent gotten transfer learning working on the l2 model yet

Hi @qubvel, thanks for this repo! I used your converter script a few months ago to generate autoaugment and advprop weights (top and notop), I was thinking you may be interested in adding these weights to your efficientnet repository. Please find them in here.

Yes, i converted the weight file for the noisy student models, i planned upload them here: https://github.com/ThomasHenckel/efficientnet_noisy_student_keras_transfer_learning
I just havent gotten transfer learning working on the l2 model yet

Hi @ThomasHenckel, thanks for the support for larger noisy student models! Are you still considering uploading weights files in the GitHub repo you mentioned above? I look forward to being able to use them in @qubvel efficientnet repo!

Hi @MichaelKapre
For now default 'imagenet' weights are actually imagenet weight trained with autoaugment.
I have also already add noisy student trained weights.
I will consider adding 'advprop' weights, thanks a lot for sharing!


[Communication] ACS Chat 1.3.2 Release

Packages impacted by this PR
@azure/communication-chat
Describe the problem that is addressed by this PR
Updated to<EMAIL_ADDRESS>Added EUDB real-time notification support. https://*.trouter.teams.microsoft.com and teams.microsoft.com needs to be allowed for real-time notifications.
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Unable to update add-on config

When I'm trying to open config of the add-on I get the following error:
Error
An error occurred. Please start Anki while holding down the shift key, which will temporarily disable the add-ons you have installed.
If the issue only occurs when add-ons are enabled, please use the Tools > Add-ons menu item to disable some add-ons and restart Anki, repeating until you discover the add-on that is causing the problem.
When you've discovered the add-on that is causing the problem, please report the issue to the add-on author.
Debug info:
Anki 23.10 (51a10f09) Python 3.9.15 Qt 6.5.3 PyQt 6.5.3
Platform: macOS-14.1.2-arm64-arm-64bit
Flags: frz=True ao=True sv=3
Add-ons, last update check: 2023-12-02 21:32:35
Add-ons possibly involved: ImageResizer

Caught exception:
Traceback (most recent call last):
  File "aqt.addons", line 982, in onConfig
  File "/Users/julianemtseva/Library/Application Support/Anki2/addons21/1214357311/__init__.py", line 125, in _settings
    self.settingsMw = Settings(self, Setup.config)
  File "/Users/julianemtseva/Library/Application Support/Anki2/addons21/1214357311/__init__.py", line 379, in __init__
    self.setupUI()
  File "/Users/julianemtseva/Library/Application Support/Anki2/addons21/1214357311/__init__.py", line 516, in setupUI
    mainLayout.addWidget(self.hLine())
  File "/Users/julianemtseva/Library/Application Support/Anki2/addons21/1214357311/__init__.py", line 570, in hLine
    line.setFrameShape(QFrame.HLine)
AttributeError: type object 'QFrame' has no attribute 'HLine'

Fixed, could you update the addon and try again?


add gazebo_pwf.md

After checking the actual reflection, I found the modified part, so we will push the modified version again.

Fixed it.


Clarification

To be more clear, this page could state that when the ContinuationToken is null or an empty string, there is no additional data available in the query. This information could also be added to methods that return a CollectionQueryResult<T>.

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

ID: 774caef3-80a7-78c9-678b-58b82eea8c68
Version Independent ID: 5575a0ad-f8a0-252d-d8e6-1e89c2ef763b
Content: CollectionQueryResult<T>.ContinuationToken Property (Microsoft.Azure.NotificationHubs)
Content Source: [xml/Microsoft.Azure.NotificationHubs/CollectionQueryResult1.xml](https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.NotificationHubs/CollectionQueryResult1.xml)
Service: notification-hubs
GitHub Login: @CamSoper
Microsoft Alias: casoper

@sethmanheim are you looking into this?

@jwargo No, never saw this, probably because I'm not listed as the author.

@jwargo I would think this change needs to be made in the code, within the triple-slash doc comments since it's probably autogenerated.


cross compiler Matching variant not found

I get this issue when trying to use cross as the compiler? Any idea why?
cargo lambda build --compiler crlss

error: invalid value 'cross' for '--compiler <COMPILER>': Matching variant not found

nevermind was running on an old version


Adding missing Java import and Fixing async accessToken assignation

This causes an issue when accessing the token, I preserve the same behavior.

+1

please accept this pull request. last one related with the android token has some issues

perfect thansk @charlires


[Feature request] Integrate boost::pfr for static interface

The Boost.MySQL library already introduced using boost::describe for it. There is also another one reflection library which provides everything we need for static interface: https://github.com/boostorg/pfr
And the key benefit is no more need for BOOST_DESCRIBE_STRUCT
Don't hesitate to ask any question regarding PFR, my pleasure to provide as much help with development as it required.

Hi!
Yes, this is definitely possible.
I haven't used PFR yet, but from what I've seen, you can get struct fields by index (C++14) and field names (C++20). Unless I missed something, there is no metafunction to query whether a type T can be reflected by PFR except by using is_aggregate (C++17).
The static interface currently supports two models to match query results to struct fields: by index (this is used by std::tuple) and by field name (this is used by Boost.Describe). Matching fields by name requires reflecting field names. With PFR we could do both, but with different standards requirements. So I see some different ways of doing this:

We could support field matching by index only. static_results<RowType> would use PFR if RowType hasn't Boost.Describe metadata and is an aggregate. This would work in C++14+. But it may be too limiting. We would need a C++14 way of determining if RowType is PFR-reflectable.
We could support field matching by name only. The logic would be similar to the above. This is simpler, but C++20 only. We can use std::is_aggregate here.
We can try to support both. I don't like the idea of matching by index in C++14 and by name in C++20 because it's error-prone. So we need a way to differentiate. We could go for something like static_results<pfr_by_index<RowType>> (C++14) and static_results<pfr_by_name<RowType>> (C++20). This is a little bit more typing, but more explicit. It would also prevent Describe users from getting the PFR behavior by mistake. It would also save Describe users from including PFR headers. pfr_by_xxx would just be tag types - static_results<pfr_by_xxx<RowType>>::rows() should still return a RowType collection. We would need some trait to do this, but it shouldn't be too difficult, and opens the doors for some interesting nice-to-have behavior.

Please let me know what you think of these interfaces.
Do you have the time and energy to code this yourself and submit a PR? If it's the case, I can provide additional guidance on how to do it.
Thanks,
Ruben.

Hi, Ruben! Thanks for so quick answer.
Sure, I can create PR should we negotiate the interface once later. Regarding three variant you suggested:

Definitely NOT, but this sentence static_results<RowType> would use PFR if RowType hasn't Boost.Describe metadata and is an aggregate. sounds really nice, PFR is good candidate to be used as fallback for a probally unknown RowType.
Pretty nice, except suggestion to use std::is_aggregate. We will have a lot of false-positives should we use this trait, due to limitations(PFR not able to work with every aggretate type, for example structrures with bases are not supported). We will definitely NOT use only std::is_aggregate strictly relying on it. But we still can use fallback-strategy in this variant, as it was discussed in previous one, why not?
Pretty nice, not sure should we discuss a way to differentiate by index and by name in this topic, I believe it might be decomposed to another issue that completely not related with PFR integration. Also I see here you suggest not to use std::is_aggregate nor to use fallback-strategy, you suggest to let library's user control the answer of the question "whether a type T can be reflected by PFR" via view-like manipulator. Well, such way to query possibility of T to be reflected looks really attractive, here I understand you :) But it will be ended up collided by case with recursive reflection. It's impossible in the current version of Boost.MySQL, but we should not ignore that it's quite possible in the future(For example, should this library introduce json fields).

Concluded it all, I still belive that fallback-based way is the best way to integrate PFR into Boost.MySQL. How could I see it in short example:
struct A { ... };
BOOST_DESCRIBE_STRUCT(A, ... );

using B = std::tuple< ... >;

struct C { ... };
// no need for BOOST_DESCRIBE_STRUCT

struct E : C { ... };

struct D {
 explicit D( ... );
};

static_results<A>; // OK, boost::describe struct is acceptable as always
static_results<B>; // OK, std::tuple is acceptable too
static_results<C>; // OK, not describe struct nor a tuple, so we ask boost::pfr to reflect it
static_results<E>; // ERROR, we ask pfr as before, but it failed due to inheritance
static_results<D>; // ERROR, we even don't ask pfr, since it's not an aggregate

static_results<by_index<A>>; // OK, why not? looks redundant, but might be helpful in generic code
static_results<by_name<A>>; // OK, as default matching for describe
static_results<by_index<B>>; // OK, as default matching for tuple
static_results<by_name<B>>; // ERROR, matching by name is not supported by tuple
static_results<by_index<C>>; // OK
static_results<by_name<C>>; // ERROR(for C++14), OK(for C++20)

Let me know if I missed something. And thanks for the attention

The by_name and by_index constructs you propose are definitely interesting.
This is confusing though:
struct A { ... };
BOOST_DESCRIBE_STRUCT(A, ... );

struct C { ... };
// no need for BOOST_DESCRIBE_STRUCT

static_results<A>; // matches by field name
static_results<C>; // matches by index

They're both structs, so they must have the same behavior, regardless of the library being used. This is prone to error for Describe users: forgetting the BOOST_DESCRIBE_STRUCT will cause by-index field matching, which will result in an error only detectable at runtime (where previously it was detected at compile-time).
So either we default to matching by name for PFR, too, or, when passing a type T to static_results, we mark it somehow to use PFR reflection (something like static_results<use_pfr<C>>). The fact that there is no way to check whether T is PFR-reflectable makes me lean towards using some sort of explicit marking.

Of course, default matching for PFR have to be "by name", as it's already for Describe.
No reason to make confusion for MySQL users

BTW regarding view-like manipulator which allows explicitly mark T as reflectable.
I was already trying to introduce such way for Boost Fusion (and thus for Boost Spirit), you could see it here https://github.com/boostorg/pfr/pull/107 if it's interested. But it was ended up due to recursivness inablity, so then we decided that integrating PFR as implicit fallback is a nice way for Spirit.
I see nested structures are unlikely MySQL case. Well, we can move forward sticking explicit marking way, why not?.
But it definitely will not be use_pfr on the Boost MySQL side, something like this static_results<boost::pfr::view_t<C>> would be better, and reusable. Think I should recreate that ancient PR regarding boost::pfr::view_t and then we will moving here, what do you think?

Of course, default matching for PFR have to be "by name", as it's already for Describe.
Great, we agree.

static_results<boost::pfr::view_t<C>>
static_results<T> internally creates a std::vector<T> to store rows. boost::pfr::view_t<T> inspires me that we'd be creating a vector of views, while we'd need actually a std::vector<T>. I think the idea of implementing the type marker in PFR is good (although if it's not possible, it can go in MySQL), but having the word "view" here is misleading.

If done in MySQL, we can do something like:
// Trait to get the actual row type from the template arg passed to static_results
template <class T>
struct get_row_type { using type = T; };

// Marker for PFR types
template <class T>
struct pfr_enabled { using type = T; };

// Trait specialization
template <class T>
struct get_row_type<pfr_enabled<T>> { using type = T; };

// In static_results. This is actually a variadic template and more complex,
// I'm providing this snippet to illustrate
template <class RowType>
class static_results {
   //  ....
   std::vector<get_row_type<RowType>::type> rows_;
};

Let me know what you think.

although if it's not possible, it can go in MySQL

It's more than likely possible, of course otherwise boost::pfr::view_t will be implemented on the MySQL side

Well, we are not interested to integrate PFR as implicit fallback anymore? Only something like boost::pfr::view_t would be enough?

Sorry for the late answer. boost::pfr::marker_t looks good to me.
I'd go with the explicit marker for now and see how it goes. If we find it cumbersome, we go with the fallback. Does that sound right to you? Would you like me to provide you some implementation info to get you on the right track when writing the PR?

Sorry for the late answer. boost::pfr::marker_t looks good to me.
I'd go with the explicit marker for now and see how it goes. If we find it cumbersome, we go with the fallback. Does that sound right to you? Would you like me to provide you some implementation info to get you on the right track when writing the PR?

I'd go with the explicit marker for now and see how it goes. If we find it cumbersome, we go with the fallback.

Sure

Would you like me to provide you some implementation info to get you on the right track when writing the PR?

Yes, it would be great, thanks

You will need to add PFR support for both static_results (the normal interface) and static_execution_state (the multi-function interface). As you can image, they share a lot of code.
Most of what you will be changing is located under include/boost/mysql/detail/typing/ (support types for the static interface). Have a look at include/boost/mysql/detail/typing/static_results_impl.hpp and include/boost/mysql/detail/typing/static_execution_state_impl.hpp, too, as these are the files implementing static_results and static_execution_state.
Some general comments about the infrastructure:

The static interface performs parsing in two steps: a metadata check, performed when MySQL sends row metadata. This ensures that the types in your struct match what the query returned, and matches field names to positions; and actual row parsing, which transforms a set of field_views into the struct that the user defined.
readable_field_traits.hpp contains type traits for individual struct fields (i.e. ints, floats...). These are currently not public. You shouldn't need to touch this.
pos_map.hpp contains the structure we use to map field names to positions. We use name_table_t, which is a constexpr span of string views, to hold the field names in the user-supplied type, in order. An empty span means that the type doesn't support name matching (e.g. a tuple). pos_map is an array of std::size_t containing a mapping from C++ field index in the struct to field index in the query. You won't need to update these but you need to be aware of them.
meta_check_context.hpp contains utilities to perform the meta check step.
row_traits.hpp contains the row_traits (also private), defining what a row is. You will need to create a specialization for the PFR wrapper type you define. row_traits must provide:

A types type alias, containing a type list with all the type members of your struct (used for meta checking).
A size function containing the number of fields.
A name_table returning a name table, as described above.
A parse function that iterates over all struct fields, in order, and calls parse_functor for each of them.

static_execution_state_impl and static_results_impl implement the execution_processor interface, with a set of functions that map to protocol packets. To reduce code bloat, these are split into two: static_<xxx>_erased_impl (which doesn't depend on template arguments) and static_<xxx>_impl, which does. You may have to make minor modifications to the templated ones.

You will need to create a type trait to map from a StaticRow type to the actual, underlying row type to be to store rows. The trait needs to be public because it will appear in some functions in the public interface. You will have to modify some of the functions described above to use this type trait.
If you happen to implement the PFR type marker in MySQL, I'd advise to place all specializations in a separate file, rather than in row_traits.hpp, as this would allow users to selectively include the code they need.
Regarding testing:

There are unit tests under test/unit/test/detail/typing/, which you will need to add to.
There are integration tests under test/integration/test/static_interface.cpp. I advise to add some spotchecks like the ones already there, checking that everything works. Note that you need a real server to run this - have a look at this.
Feel free to add any other extra tests you may think are useful. Testing is one of the strong points of this library.
We have CIs (Drone and GHA) that run on pull request. You should be able to see their results, let me know if you have issues with it.

Regarding docs:

You'll need to update the discussion, which is quickbook. Mainly this page, but have a look at others that also reference Describe and add something to them, too.
An example could be nice, too. We already have similar stuff under example/order_management, so maybe you could duplicate prepared_statements_cpp14.cpp but using PFR.

Please let me know if you have any questions or any problems arise.
Thanks,
Ruben.

Thanks for the detailed information! Give me some time to configure my workstation to work with MySQL, and then I will start working on the PR

Hi @denzor200, I've implemented this. Could you please take a look at the documentation (https://anarthal.github.io/pfr-integration/libs/mysql/doc/html/mysql/static_interface.html) and share with me your feedback?
I finally implemented this as pfr_by_name and pfr_by_position because it was far simpler than pfr<by_name<T>>.


Error messages are hidden

Error messages were showing last week.  Now the error window only has the string "Connection failed: 0 error".
The console link also seems to show an empty log.

Fixed. Thanks for the report!


[Lease] Handle the 'NeedLiquidation' case on lease open

Currently, we treat it as an invalid case and panic with unreachable: "panicked at 'internal error: entered unreachable code', contracts/lease/src/contract/cmd/open.rs:105:54".
Although it'd be rare or even almost impossible it should be handled appropriately, most probably initiating a liquidation.

closing this as it's merged into #282