Some tricky data for Arrow

I have this data in the JDF.jl tests. Arrow is currently failing to write it. We could incorporate something like this in the tests.
using JDF
using DataFrames
using Random: randstring
using WeakRefStrings

df = DataFrame([collect(1:100) for i = 1:3000])
df[!, :int_missing] =
    rand([rand(rand([UInt, Int, Float64, Float32, Bool])), missing], nrow(df))

df[!, :missing] .= missing
df[!, :strs] = [randstring(8) for i = 1:nrow(df)]
df[!, :stringarray] = StringVector([randstring(8) for i = 1:nrow(df)])

df[!, :strs_missing] = [rand([missing, randstring(8)]) for i = 1:nrow(df)]
df[!, :stringarray_missing] =
    StringVector([rand([missing, randstring(8)]) for i = 1:nrow(df)])
df[!, :symbol_missing] = [rand([missing, Symbol(randstring(8))]) for i = 1:nrow(df)]
df[!, :char] = getindex.(df[!, :strs], 1)
df[!, :char_missing] = allowmissing(df[!, :char])
df[rand(1:nrow(df), 10), :char_missing] .= missing

@time JDF.save("a.jdf", df) # works with JDF

# but fails with Arrow
Arrow.write("a.arrow", df)

error msg
4,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Int64,Union{Missing, UInt64},Missing,String,String,Union{Missing, String},Union{Missing, String},Union{Missing, Symbol},Char,Union{Missing, Char}}}, ::DataFrame, ::Dict{Int64,Tuple{Int64,Type,Any}}) at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:258
 [9] macro expansion at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:71 [inlined]
 [10] macro expansion at .\task.jl:332 [inlined]
 [11] write(::IOStream, ::DataFrame, ::Bool, ::Bool) at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:58
 [12] #29 at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:21 [inlined]
 [13] open(::Arrow.var"#29#30"{Bool,DataFrame}, ::String, ::Vararg{String,N} where N; kwargs::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}) at .\io.jl:325
 [14] open at .\io.jl:323 [inlined]
 [15] #write#28 at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:20 [inlined]
 [16] write(::String, ::DataFrame) at C:\Users\RTX2080\.julia\packages\Arrow\FjbLX\src\write.jl:20
 [17] top-level scope at REPL[44]:1
 [18] include_string(::Function, ::Module, ::String, ::String) at .\loading.jl:1088

It's helpful to post backtraces as that can often quickly show where the error is

It prints out alot of stuff. It's like 11pm. I will try to get a MWE together.

Alright, so the error here is because it doesn't know how to map Symbol or Char columns to arrow format. I guess in both cases, we should just map them to strings.

I guess the biggest question is if we're ok not having round-tripping in these cases; i.e. we could allow writing columns of Symbol/Char, but they'll be read back in as strings. @bkamins @nalimilan , any thoughts/preferences here?

Not sure. Maybe see what Feather.jl does? Also of interest is what RCall should do with CategoricalArray{T} when !(T<:AbstractString), as R only supports string factors (https://github.com/JuliaInterop/RCall.jl/issues/331).

I think the priority is to allow saving things with as little problems as possible. Symbol and Char are normal in Julia.
Given your comment I understand that we have a choice:

either error on them
or convert to String when saving

I would prefer the option 2. maybe with a @warn about conversion

I mean, Feather.jl will just be a wrapper around Arrow.jl pretty soon, so they'll do whatever we do. I also think I like the idea of option 2 w/ a warning. I think people should understand that Arrow.jl isn't meant to be a serialization package, even though it can handle a wide range of types of objects. But even still, I think doing some automatic conversions will be convenient.

Agreed

There is a way to arbitrary meta data right? We should remember them as Julia:symbol and julia:char types. So in Python and r they get read as string but it Julia we can use the meta data to restore them as symbol and char?

Ah, I forgot about that; yes, that's a pretty good idea. I'll have to see how we can work the plumbing in for that.

Ok, took a bit of work, but I think I've got it all working for Symbol/Char. https://github.com/JuliaData/Arrow.jl/pull/11


Focalplane export not working

Hi ,
am not sure this is the right place for this issue.
when running lbt_export_focalplane , i get this error
Traceback (most recent call last):
  File "/global/cscratch1/sd/giuspugl/toast3_software/bin/lbt_export_focalplane", line 8, in <module>
    sys.exit(main())
  File "/global/cscratch1/sd/giuspugl/toast3_software/lib/python3.9/site-packages/litebirdtask/scripts/export_focalplane.py", line 56, in main
    fp.save_hdf5(args.out)
  File "/global/cscratch1/sd/giuspugl/toast3_software/lib/python3.9/site-packages/toast/instrument.py", line 778, in save_hdf5
    table_write_parallel_hdf5(self.detector_data, handle, "focalplane", comm=comm)
  File "/global/cscratch1/sd/giuspugl/toast3_software/lib/python3.9/site-packages/toast/utils.py", line 736, in table_write_parallel_hdf5
    dset = root.create_dataset(name, dset_shape, dtype=dset_type)
AttributeError: 'str' object has no attribute 'create_dataset'

Think the issue is that  in https://github.com/hpc4cmb/litebirdtask/blob/3a5a5abd9f5144d15e322d01367198cb2da0e3c1/litebirdtask/scripts/export_focalplane.py#L56
args.out is a str not an hdf5.Group.
Changing that line into something like :
import h5py
    f = h5py.File(args.out,'w')
    grp = f.create_group("focalplane")
    fp.save_hdf5(args.out )
    f.close()

might do the work. Any suggestion ?

Please see https://github.com/hpc4cmb/toast/pull/551

Thanks a lot !
I have modified the script accordingly
https://github.com/hpc4cmb/litebirdtask/blob/e28022e2615572de1c1479ebbde17e6cb9eef35f/litebirdtask/scripts/export_focalplane.py#L56
see  PR #5 .


tooltip placement behavior wrong

Hi,
I set a tooltip of a ctrl,and set tooltipservice.placement="bottom", as the doc says,  the tooltip should be place at bottom of target and align left with target, but i got wrong display , the tooltip align right with target. I test other placement,it seems left and right are opposite in my pc. More, it looks  correct in design window,but wrong if run my exe.  I run my exe in my friend's pc, his pc behave correct.
so, what's wrong with my pc or vs2017? how to fix that?

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

ID: 88771909-3ed1-06b8-6650-cd16c8df2df2
Version Independent ID: 2fac47b4-b474-b22a-1e77-54a1a2c13b58
Content: How to: Position a ToolTip - WPF .NET Framework
Content Source: dotnet-desktop-guide/framework/wpf/controls/how-to-position-a-tooltip.md
Product: dotnet-framework
Technology: dotnet-wpf
GitHub Login: @adegeo
Microsoft Alias: adegeo

This issue was moved to dotnet/docs-desktop#165

This issue was moved to dotnet/docs-desktop#165


Plan out Semi-auto Commands

AcquireHatchPanel
AcquireCargo
PlaceHatchPanel (Cargo Ship Low/Rocket Low, Rocket Med, Rocket High)
PlaceCargo (Cargo Ship Low, Rocket Low, Rocket Med, Rocket High)
Climb

This is what I can think of so far, what else am I missing?

Closed based on discussion at meeting 2/6, and revised initial comment.


Why a new release not public in long time?

Why a new release not public in long time?
the  release latest is in 2016, now

To be fair, building a go binary is pretty easy. I did it on OpenBSD and Windows without much effort.

y,  so i need install my golang env.   make a release will help more people  to use easy

There hasn't been any new release because... there has been no need to?
Piknik works and does what it was designed to do. There are no bugs or vulnerabilities I'm aware of. The code still compiles and fine with current Go versions.


Add an new 'kind' of property which would bring up a multi line input box

Some string entries are inherently multi line, and possibly rich text.  How will the GUI know to distinguish them from the simple string ones ?
Once distinguished, when we build the UI it should include a multi-line rich text editor for them.

Is the info about which prop is what going to be stored in the schemaMetadata?

good question -
I guess it should be, since the database does not distinguish this information.  We could have properties of the schemaMetadata for each (some of) the properties of the described NDMobject classes that say what to do with them.
For example:
the description of the annotation could include a property body that is {'format':'rich-text', 'default-width':40, 'default-height':5}


refactor(core) client cache separation

Summary
New cache kong.core_cache is meant for core usage, while the existing
kong.cache is used in, e.g., plugins.

Are there any tests for kong.cache?

Hey @gszr , as Colin is saying: a lot of instances of kong.cache where transformed into kong.core_cache with this change, including specs. Since now we have two kinds of cache (core and non-core), is the non-core cache tested anywhere? Perhaps on the plugin tests themselves?

@kikito @hutchic Yes, plugins tests - e.g., cache invalidation tests - exercise the client-facing cache.


Fix Knock Off And Rapid Spin

Knock Off and Rapid Spin should still take effect even if the user faints in Generation 3 and Generation 4,
Ignore the branch name.

Thanks!


ppm run lint not working

It looks like the linter is not linting anything:

Hey, thanks for opening an issue!
I've added linting commands to relevant packages in 48ae16462b9efa5e650e5055eed4fbb85d2243e7


Edited the background color of toggle button to highlight the ON and OFF state

I changed the background color of toggle button to highlight OFF state.
Issue:1 -
The toggle button is shows same color for both ON and OFF state.

Thank you for your work @snehanagari but that does not have to do with the bug. Also, we do not edit the CSS files directly, we edit the LESS files.


jetbrains idea-ultimate segfaults when opening a project or some settings

Describe the bug
On the latest nixos-unstable-small, jetbrains idea-ultimate (even versions < 2021) crashes due to a segfault in the libharfbuzz-library.
From the crash log file:
# JRE version: OpenJDK Runtime Environment (11.0.10) (build 11.0.10+0-adhoc..source)
# Java VM: OpenJDK 64-Bit Server VM (11.0.10+0-adhoc..source, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libharfbuzz.so.0+0x2ee25]  hb_font_funcs_destroy+0x75

To Reproduce
Steps to reproduce the behavior:

Start idea-ultimate
Open a project with files
The editor crashes and exits

I was able to open an empty project without files. Once I created a file it crashed. I think this might have something to do with the rendering of font ligatures.
This also occurs when trying to open the editor font settings (not the normal font settings).
Expected behavior
Intellij IDEA Ultimate should be able to open files normally.
Screenshots
The last screen before the program exits:

Additional context
Since this problem is probably related to fonts: I am running the Fira Code font which has ligatures.
Notify maintainers
@edwtjo @Mic92
Metadata

system: "x86_64-linux"
host os: Linux 5.11.11, NixOS, 21.05.20210411.7644480 (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre20210326_dd77f71
channels(rien): ""
nixpkgs: /etc/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

The crashes are still occurring after reverting  3839373. I will try to look for recent changes with fonts that might have caused this.

I was able to pinpoint the problem. After a full reset everything works again. Going to Editor > Font and selecting "Enable font ligatures" immediately crashes it. I will make a report with JetBrains for this issue.

I was able to fix this issue by reverting this commit https://github.com/NixOS/nixpkgs/commit/af45b82a3770c1855b6fbb3d2d9fb325842f8d01 where jetbrains-jfsk was updated from 11.0.7-b64 to 11,0,10,b37. @edwtjo how should we go further with this? Revert this commit on master?


PWA-983 removed description from test id.

Pull Request Test Coverage Report for Build 1704

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

Totals

Change from base Build 1701:
0.0%

Covered Lines:
1412

Relevant Lines:
3379

💛  - Coveralls


sj_add-always-strict

:tada: This PR is included in version 2.11.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


UnhandledPromiseRejectionWarning: NoSuchBucket: The specified bucket does not exist

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
In a react native project (expo) that is using amplify services (auth, gql api, storage) after modifying the gql schema, I ran the amplify status. After being prompted to upgrade the amplify-cli, i ran the npm install -g @aws-amplify/cli which then installed the new library. Then I ran amplify status, showing that the API had been updated again. Ran amplify push and then was given the error of "UnhandledPromiseRejectionWarning: NoSuchBucket: The specified bucket does not exist" (see screenshot for additional information on the error in terminal).
I then proceded to attempt to delete the storage (as this project is still in development) with the command amplify remove storage. Then amplify status which showed the API UPDATED and the STORAGE DELETED. Ran the command amplify push and was given the same error.
I opened a blank folder in my IDE (Visual Studio Code) and ran the amplify pull < > with my projects appropriate command copied and pasted from the amplify console. The same error was thrown again with a little extra information.
"Failed to pull the backend.
The specified bucket does not exist
NoSuchBucket: The specified bucket does not exist"
After further inspection in my Amplify console, I have noted that all of my categories are now missing from the back end which were the following categories:
Authentication
API
Storage
However, when looking into all of those individual spots in my AWS account they are still there i.e. Cognito User Pools, S3 bucket, AppSync etc. AND the code that is relying on these deployments are functioning without issue in expo local and hosted app.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.27.3
To Reproduce
Steps to reproduce the behavior or terminal output if applicable
I am unsure the steps to reproduce. It is only occuring on my machine and I do not have an additional computer to attempt to reproduce. It appears it is related to my AWS account and/or Amplify Project. However, please follow the steps I listed above to see if you can reproduce.
Expected behavior
A clear and concise description of what you expected to happen.
The amplify push will work as it has before, updating my resources in the cloud. The GQL Api schema will update, and my S3 bucket will be deleted as I also have ran that command.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]

Mac OS 10.15.6
IDE: Visual Studio Code 1.48.1 using the bash terminal internal of VS Code

Node Version. You can use node -v to check the node version on your system

v.14.7.0
Additional context
Add any other context about the problem here.
Questions asked in another issue with the same problem
#4872
CLI verion : answered above
OS version : answered above
Amplify categories that you added to your project : Auth, Storage, API
Did you use Amplify Console to create your project? Yes
Have you pulled the project from github console and run amplify init on your local machine? The project was intialized locally with amplify before being pushed into github
Have you manually changed anything in the /amplify/.config folder? No.
Have you updated or deleted S3 bucket on the S3 console? No. After encountering errors I did attempt to delete the storage category from the Amplify Project.

@dev-elevate-usa what was the version of Amplify CLI before the update?
Do you have your changes tracked using version control systems like git? If you do have it tracked, could you check if there was any changes to <project-root>amplify/backend/amplify-meta.json folder

@yuth

Yes I am using git version control. The amplify-meta.json file is not being recorded though with my version control because by default it was listed inside the .gitignore. I have not made any changes to any of the autogenerated files tho.

There has not been any changes to my profile as you have listed. The last interaction I have had with any type of cloud formation was in on August 7th. I have been in a heavy development cycle and have not needed to do any changes until yesterday.

@dev-elevate-usa Do you see the <project-root>.amplify/.config/local-aws-info.json file?

@kaustavghosh06 Yes it is in my directory. It is also .gitignored.
{     "dev": {         "configLevel": "project",         "useProfile": true,         "profileName": "default"     } }

In the amplify/backend/amplify-meta.json file you can find the "DeploymentBucketName". Can you go to the AWS S3 console and check if the value of the "DeploymentBucketName" which wis your bucket-name still exists?

@kaustavghosh06 there is a bucket in my S3 however is does not match the naming convention of the "DeploymentBucketName"

{
"providers": {
"awscloudformation": {
...
"DeploymentBucketName": "amplify-repaircabanaapp-dev-160452-deployment",
...
}
},
...
}

@dev-elevate-usa The above looks like the 'storage' resource bucket and not the deployment bucket. Any chance the S3 bucket - "amplify-repaircabanaapp-dev-160452-deployment" was deleted accidently?

@kaustavghosh06 I did go through and clean up my S3 recently from some spike projects and tutorials i was running through. It is possible that i would have deleted a bucket like that 😬  Is there anywhere I can look for a log of that action being performed to confirm?

 If you're still in development, you can run "amplify env add" -> "amplify push" to clone your infrastructure and add a new environment. This would clone the deployment bucket for that environment as well which seems to be missing.

@kaustavghosh06 I have not run amplify delete
Should i try to run the command you have listed above?

I am still unsure how that would pull all my categories back into my amplify console on the back end?

Please read my comment out here - https://github.com/aws-amplify/amplify-cli/issues/5171#issuecomment-680186881
This would help clone your backend infrastructure( create a new amplify app and new resources).
If you want to retrieve back your deleted S3 bucket for your current environment then you'd have to contact AWS support -https://aws.amazon.com/premiumsupport/knowledge-center/aws-phone-support/ for help.

@kaustavghosh06 Thank you. I did actually delete that bucket, I just found the event in my cloudtrail. If i clone the backend will i have to set up all the categories again?

Nope, you wouldn't have to. You'll be cloning your current environment.

Okay. The reason I ask is because the categories are missing in my amplify console as the screenshot showed above

Yes, that's because the Amplify Console directly reads from the S3 deployment bucket which you've deleted. If you create a new environment (which would result in creation of a new deployment bucket for that environment) and push the corresponding resources, you'll see your new environment with the enabled categories on the Amplify Console as well.

Ah. I totally understand now! I am currently doing as you suggested in creating a new environment. Would you recommend me to delete the previous environment that I 💣  after i get the new environment up and running?

so just to clarify, Amplify uses S3 to store configurations for the categories of the amplify project?

That is correct. It uses S3 to store Deployment artifacts.

After creating the new environment, you can run amplify env remove and remove the older environment.

I can confirm that this issue has been resolved. Thank you so much for your time and effort to help me get back on track!

 If you're still in development, you can run "amplify env add" -> "amplify push" to clone your infrastructure and add a new environment. This would clone the deployment bucket for that environment as well which seems to be missing.

This comment solved my issue. I had deleted the S3 bucket that is used to store the Deployment Artifacts for the current amplify project enviroment. Thanks @kaustavghosh06


Spack stack build with July 2023 merge of authoritative spack fails with undefined "_iconv" symbol

Describe the bug
The build using climbfuji:feature/merge_spack_develop_20230710 branch fails on macos with unreferenced symbols related to the iconv library. One example of an unresolved reference is _iconv.
Briefly, the issue is that GNU, in their iconv library, switched the names of several symbols by prepending "lib" in front of the older names. Eg, _iconv changed to _libiconv. On macos these symbol name changes have not occurred. Unfortunately, these changes are installed in the same file name as the macos iconv: libiconv.dylib which leads to much confusion.
Dom discovered that the way to get spack-stack to build, using his feature branch (ie, spack updates from the authoritative spack repo) on the mac was to force spack-stack to use the system (/usr/lib/libconv.dylib) iconv library.
This is compounded by a change Apple did back in the Big Sur timeframe (perhaps earlier) where the library files in /usr/lib were removed from disk, are loaded into memory in a section of the kernel, and the build tools (clang, ld, dyld, etc) on the macos make it appear that the /usr/lib files are still there when compiling and linking code. This was done to speed up app startup and to save disk space.
So, this change is designed to force the use of /usr/lib/libiconv.dylib for linking and shared library execution by declaring that libiconv.dylib is not buildable, and is located in /usr/lib. The "magic" of the macos build tools takes over at that point and makes it appear that /usr/lib/libiconv.dylib does indeed exist, can be linked against and can be "loaded" at runtime.
I picked an arbitrary version number (happens to be the latest version, 1.17, that is available today) for libiconv because spack concretize wouldn't accept the externals spec line without a version number. It doesn't matter what the version number is, since the macos "magic" ignores all of that; the version number is only there to make spack happy.
I put the these changes in the site template for macos since I wanted these changes to only be applied to the mac platform.
I'm open to suggestions if there is another way to accomplish this without having to use a fake version number in these changes, or any suggestion about a better way for that matter.
To Reproduce
build spack-stack using the current feature/merge_spack_develop_20230710 branches.
Expected behavior
The spack-stack build using the feature/merge_spack_develop_20230710 branches successfully complets.
System:
macos, ventura 13.5.1 (c), apple<EMAIL_ADDRESS><EMAIL_ADDRESS>Additional context
None

This issue was fixed with the push of 6cc25bd to Dom's feature/merge_spack_develop_20230710 branch.

Thanks very much for the detailed explanation @srherbener !


changed the setup: added requirements

@maximilianmetti Could you please try the following commands:
python setup.py test

and
python setup.py sdist bdist_wheel

and tell me if it works.

@arthbous i'm cool to merge this.  all good on your end?


Extend ogre 1.x custom shaders support

🎉 New feature
Related https://github.com/gazebosim/gz-sim/issues/2002#issuecomment-1718745400
Summary
Extended to support features needed to render waves:

2d textures
cubemap textures
constant variables

Code is ported from the ogre2 implementation
Test it
Build and run the waves example
# ogre 1.x is used when no args are supplied
./waves

Sky is not supported yet in ogre 1.x so you'll only see waves in this demo:

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

is it possible to add a test ?

yep, will add one

yep, will add one

Added INTEGRATION_waves test that verifies waves can be rendered. Shaders and materials files for the test are taken from the waves demo. 20ca0c7


jsification

Created JS version (kinda scuffed but it works)

Not sure how good / useful an idea it is to include a JavaScript client in a Python package, with Python tooling

its for #25

I'm with @Robin5605, I'd be happy to make a JS repo, but I don't want to try and keep multiple implementations in the same repo. Shall we proceed with the JS repo?

sure ig

Very well, please continue the jsification over there --> https://github.com/letsbuilda/imsosorrybutinjs

Handled in https://github.com/letsbuilda/imsosorrybutinjs/pull/1


fix: Camel component type is END even if it's in between steps

Fixes #352

@kahboom This should fix the broken lines in branches

Damn, I must have forgotten to upload something...

Codecov Report

Merging #361 (c0cbe65) into main (2cdab2f) will increase coverage by 0.30%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #361      +/-   ##
============================================
+ Coverage     79.35%   79.66%   +0.30%
- Complexity      113      114       +1
============================================
  Files            45       45
  Lines          2063     2060       -3
  Branches        301      301
============================================
+ Hits           1637     1641       +4
+ Misses          273      268       -5
+ Partials        153      151       -2

Impacted Files
Coverage Δ

.../step/parser/kamelet/KameletStepParserService.java
71.66% <100.00%> (ø)

...arser/step/camelroute/CamelRouteFileProcessor.java
93.75% <100.00%> (-0.15%)
:arrow_down:

.../backend/api/resource/v1/IntegrationsResource.java
73.21% <0.00%> (+5.35%)
:arrow_up:

...parser/camelroute/CamelRouteStepParserService.java
79.48% <0.00%> (+10.25%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


RT-1.27: fixed failed tests

This PR contains following:

Changed bgp protocol instance name to default as table connection does not have a mechanism to pick a particular bgp instance.
added sortDevicesByName function to sort emulated devices such that correct bgp neighbor gets emulated on correct otg port.
Changed GetAll to LookupAll for prefixes learnt on OTG such that test does not fail fatally for cases where prefixes are not meant to be sent to otg.
Added deviations and methods to configure default-reject route-policy, metric, attribute and skip subscription for table connection.

Pull Request Functional Test Report for #3613 / e467944da3c4c26394e2e5307a935c38efcfacf6
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.27: Static route to BGP redistribution

Cisco 8000E

RT-1.27: Static route to BGP redistribution

Cisco XRd

RT-1.27: Static route to BGP redistribution

Juniper ncPTX

RT-1.27: Static route to BGP redistribution

Nokia SR Linux

RT-1.27: Static route to BGP redistribution

Openconfig Lemming

RT-1.27: Static route to BGP redistribution

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.27: Static route to BGP redistribution

Cisco 8808

RT-1.27: Static route to BGP redistribution

Juniper PTX10008

RT-1.27: Static route to BGP redistribution

Nokia 7250 IXR-10e

RT-1.27: Static route to BGP redistribution

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
1983

Relevant Lines:
3588

💛  - Coveralls

@singh-prem can you resolve the conflicts and also rebase the checks

There are some other changes for the same test - https://github.com/openconfig/featureprofiles/pull/3444
Can we check if the changes suggested in this PR are repeated in this PR?


Review Design Wireframe: Support us page

[x] Visual Hierarchy
[x] Layout
[x] Consistency
[x] Screen size
[x] Usability Principles
[x] Web Content Accessibility Guidelines (WCAG)
[x] Colors
[x] Fonts
[x] Whitespace and padding
[x] Image quality
[x] Iconography
[x] Micro interactions
[x] Error states and feedback
[x] Performance Optimization
[x] Design documentation

See Design wireframe/prototype checklist for more info

I attempted to view the grid on this page in Figma, but I couldn’t find any. It seems like the design team may not have followed a grid for this page. It’s challenging to review the layout and spacing without a grid as a guide.
In the desktop wireframe, the "VOLUNTEER", "DONATION", and "FUNDRAISING" elements have more white space at the bottom than at the top. Perhaps this section would look neater if the spacing were consistent.
In the mobile wireframe, the "VOLUNTEER", "DONATION", and "FUNDRAISING" elements have too much white space, which detracts from the user experience.
The heading "Support" lacks consistency in padding. In some of the mobile wireframes, the heading overlaps with the red section.
In the newsletter section on desktop, the buttons are placed inside the text field, which is a bit confusing and inconsistent with the mobile design. It also lacks some of the text from the mobile design.
In the contact form element, there are links to the Terms & Conditions and Privacy Policy. These links have a contrast ratio of 22.7:1, which does not meet WCAG’s expectations.

After my last comment I see that the design team have added a grid on the page, but it dosen't look like they are following it.

The typo does not follow the style guide where it says that Montserrat should be H1

Sections like this do not meet the WCAG criteria for contrast.

Fixed the spacing for section with  "VOLUNTEER", "DONATION", and "FUNDRAISING" on desktop and mobile, and the heding "Support"
"The typography on the "Support Us" page does not adhere to the style guide. According to the style guide, H1 headings should use the Montserrat font, but the font currently used is Just Another Hand." - Just another hand is listed as alternativ font as shown in the snip - however, we have updated the Style Guide to be more clear.
Red sections like "Thanks for support", "our work" etc is now changed.
"In the contact form element, there are links to the Terms & Conditions and Privacy Policy. These links have a contrast ratio of 22.7:1, which does not meet WCAG’s expectations." - fixed
We are still working on grid, and newsletter components.


VMSS complains ImageReference is null during an update of the data disks

Here is the request URL:
PATCH /subscriptions/REDACTED/resourceGroups/vmss-update/providers/Microsoft.Compute/virtualMachineScaleSets/test-vmss?api-version=2019-12-01 HTTP/1.1

And the request body:
{
    "properties": {
        "upgradePolicy": {
            "mode": "Manual"
        },
        "virtualMachineProfile": {
            "storageProfile": {
                "dataDisks": [
                    {
                        "lun": 1,
                        "caching": "ReadOnly",
                        "writeAcceleratorEnabled": false,
                        "createOption": "Empty",
                        "diskSizeGB": 20,
                        "managedDisk": {
                            "storageAccountType": "Standard_LRS"
                        }
                    }
                ]
            },
            "networkProfile": {
                "networkInterfaceConfigurations": [
                    {
                        "name": "example",
                        "properties": {
                            "primary": true,
                            "enableAcceleratedNetworking": false,
                            "dnsSettings": {
                                "dnsServers": []
                            },
                            "ipConfigurations": [
                                {
                                    "name": "internal",
                                    "properties": {
                                        "subnet": {
                                            "id": "/subscriptions/REDACTED/resourceGroups/vmss-update/providers/Microsoft.Network/virtualNetworks/test-network/subnets/internal"
                                        },
                                        "primary": true,
                                        "privateIPAddressVersion": "IPv4",
                                        "applicationGatewayBackendAddressPools": [],
                                        "applicationSecurityGroups": [],
                                        "loadBalancerBackendAddressPools": [],
                                        "loadBalancerInboundNatPools": []
                                    }
                                }
                            ],
                            "enableIPForwarding": false
                        }
                    }
                ]
            }
        }
    }
}

And the update request returns an error:
compute.VirtualMachineScaleSetsClient#Update: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidParameter" Message="Required parameter 'imageReference' is missing (null)." Target="imageReference"

@avirishuv, could you take a look at this issue?

@ArcturusZhang This error does not repro - I was able to add data disk without having to provide image ref in the request body for the PATCH API call.
Are you using a marketplace image or custom image ? And are you seeing this behavior for any specific PS or CLI cmdlet ?

@avirishuv I am using two shared image versions created by myself.
Please find more details for reproduce in this issue

@ArcturusZhang thanks for the repro steps. I can confirm the behavior. For a SIG custom image, while updating the data disks, image reference is required (cannot be null).

👋 out of interest, why is this tagged as a Question and not a Regression given this didn't need to be specified in previous API versions?

@ArcturusZhang and @tombuildsstuff we recently had a build released that should fix this issue. Would you mind checking if you are still seeing this or not ?

@ArcturusZhang , @tombuildsstuff  if no open other questions, can we close the issue ?

Closing, please feel free to reopen if you have additional questions on this issue.


Flux 0.33

This PR should not be released until InfluxDB 1.7.8 is released.

All these changes are included in the Flux 0.36.2 PR.


Improve initial placement of non-hiearchic part

We should improve the initial placement of the non-hierarchic components in the following ways:

[x] 1. Rather than using the right and left of the hierarchy only, let's use all four sides.
[x] 2. Also let's scatter these components to be of varying distance to the hierarchy so that they do not overlap.

I think this is great but I have the following concerns/issues with the initial placement:

[ ] 1. Sometimes two components do overlap or they are very close. We should fix this bug and also have some buffer between an undirected component and the hierarchy as well as a buffer between undirected components.

[ ] 2. I am worried that we are not efficiently calculating the location of components based on placement of previous components. I hope we're not checking the location of all previously placed nodes one by one to determine the location of a new component. There should be a quicker way.

Much better, but I still see overlaps (here nodes n1,5,9,11,13,15,18 are on the hierarchy):

overlap-bug.graphml.txt

Is this resolved?


Normalize the gap sizes in the range(-1 to 1)

The esteemer algorithm uses mpm model and moderators from the performer graph to score messages.
To test this issue use the following test case:
[4,"BP03","2023-01-01",75,25,100,80,85,90,90],
[4,"BP03","2023-02-01",75,25,100,80,85,90,90],
[4,"BP03","2023-03-01",75,25,100,80,85,90,90],
[4,"BP03","2023-04-01",75,25,100,80,85,90,90],
[4,"BP03","2023-05-01",75,25,100,80,85,90,90],
[4,"BP03","2023-06-01",75,25,100,80,85,90,90],
[4,"BP03","2023-07-01",75,25,100,80,85,90,90],
[4,"BP03","2023-08-01",75,25,100,80,85,90,90],
[4,"BP03","2023-09-01",75,25,100,80,85,90,90],
[4,"BP03","2023-10-01",75,25,100,80,85,90,90],
[4,"BP03","2023-11-01",82,18,100,80,85,90,90],
[4,"BP03","2023-12-01",87,13,100,80,85,90,90]
The gap size of the last record in this test case is 90-87=3.0 (top 10%), 87-85 = -2.0 (top 25%) whereas the trend slope= 1.157407e-17 which is in the range (-1 to 1).
The Social Worse causal path way depends on gap size, in this case 3.0
whereas the Improving causal pathway depends on trend slope ,in this case 1.157407e-17.
Even after multiplying the mpm values(0.5 and 0.8) for gaps and trends, the causal pathway with gaps are always higher because the range in which gaps may vary is 0 to infinity.( 0 because for scoring we consider only absolute values )and for trends slope it is (-1 to 1).
Solution:
In order to create a fair chance for the Improving causal path ways to be selected, The gap sizes must be normalized within the (-1 to 1)
Since infinity is not a possible value, let's limit the range of gap sizes from 0 to 100.
NumPy is a powerful library for numerical computing in Python, and it provides functions for various mathematical operations, including data normalization. The numpy.linalg.norm function can be used to normalize a dataset by dividing each feature by its Euclidean norm.

To be discussed with the team:
Normalized values of gaps between [-1,1]
-0.999111 -goal
-0.997882-peer
-0.999583-top 25
-0.99875-top 10
scoring algorithm:
N29cd6c29482141559ca267ad8912273f]- socialworse
[0.4997916666666667]
Na9b76338ec0743ddbc0530dbe4a1d16d- social better
[0.499375]
Ne2f7ffcb0e0340259e0e2ef06671bf16-improving
[1.2345679012345656e-17]
In this case the the absolute value of the gaps are used for the scoring algorithm, the trend slope value is less than the absolute values. The Improving causal pathways will never be selected.
Solution:
select the maximum score with absolute values of those candidates that consists of gaps alone.
And then with that maximum score used signed scores to select the improving or social worse causal pathway.

Stop gap solution:
First select the maximum for the gap size moderator
Then with the maximum gap size moderator and the other moderator(trend slope), choose a random candidate in the pool.


Remove seq_fixed_size in favor of tuple

Currently the data model uses different types for tuples like (A, B, C) and seq_fixed_size like [u64; 3]. I don't think there are any formats that treat these differently. The defining characteristic in both cases is they are heterogeneous sequences in which the length is known during deserialization without looking at the serialized data.
Let's remove seq_fixed_size and serialize fixed size arrays as tuples instead.

Fixed in #884.

I realize this is after the fact and hard to change now, but

The defining characteristic in both cases is they are heterogeneous sequences

isn't true, and this decision has led to the unfortunate situation that &[T] is serialized differently from &[T; n]. In practice, this is mainly problematic with literals:

b"abc" vs &b"abc"[..]
[1, 2, 3] vs &[1, 2, 3][..]

@birkenfeld I think that statement is true. Could you clarify why you think it is not true?
In particular, the following are identical heterogeneous sequences from Serde's perspective; the first is a Rust tuple and the second is a Rust array.
let tuple: (bool, String, ()) = (true, "birkenfeld".to_owned(), ());

let array: [serde_json::Value; 3] = [json!(true), json!("birkenfeld"), json!(null)];

Keep in mind that Serde's type system is very different from Rust's type system.
Serializing &[T] differently from &[T; n] is 100% intentional and by design. For instance in Bincode the latter can be serialized without including the value of n because the deserializing end will be expected to know the type of what it is deserializing, and therefore know n without looking at the data.

@dtolnay Thanks for the explanation! I still don't get the "heterogeneous" argument: of course if you put in Values, every sequence is potentially heterogeneous and there is no need to even mention that aspect.
My comment results from porting serde-pickle, where I've mapped tuples to Python tuples and sequences (fixed-size or otherwise) to Python lists. Fixed-size sequences allowed me to map them to lists as well, but now trying to serialize b"a byte string" will result in a tuple, which is not at all what would be expected on the Python side.
I'm probably stretching the serde framework with the pickle format, which is supposed to store arbitrary Python object graphs, but it is used as a serialization format containing only simple types in a lot of Python related software.

One other thing to note is that toml can't deserialize heterogeneous tuples but it can deserialize fixed-legth sequences.


class diagrams and uses cases

I am University student and my job is to make class diagrams and uses cases for some project. I chose this project and can make it. Ofc if you need it

Hello @ALT-KIK,
Feel free. I would be interested in seeing what you come up with. However, I am curious why you chose this repo even though you have never ⭐ ed it nor interacted with me beforehand? Do you even know what this library is and what it does?
Kind Regards,
KJ

I haven't dived into code yet. But as I understood it is library for tech analysis?

Basically


Generic6DOFJoint error

Godot version:
35b421b6954c5baff4b4fd4bc56b09c85dae6ff5
OS/device including version:
Windows 10 & 7 64-bit, GTX 960
Steps to reproduce:

Create a new project
Add a Node2D to the scene
Play the project

Issue description:

This error appears in Error tab console:

E 0:00:00:0376   Object already has property: Generic6DOFJoint
  <C Source>     core\class_db.cpp:942 @ ClassDB::add_property()

yeah this is showing up whenever I run the editor (on the mono version)

Godot version:35b421b
the same thing happens on a mac os, just add a Sprite and run the project:
E 0:00:00:0181   Object already has property: Generic6DOFJoint
     core/class_db.cpp:942 @ add_property()


fix locales (translated labels) for V2.3 model version

labels locales were broken since V2.3 model,
because the labels_file was looking for label files named V2.3,
but only V2.2 label files were present
before patch:
labels/V2.3/BirdNET_GLOBAL_3K_V2.2Labels[locale].txt
(felt back to always using V2.3 en labels from checkpoint dir)
after patch:
labels/V2.3/BirdNET_GLOBAL_3K_V2.3Labels[locale].txt
(using correct locales labels)
under the assumption that labels have not changed between V2.2 and V2.3 model version.
edit: 3337 labels are present in translated V2.2 labels and main (en) V2.3 labels from checkpoint dir.
conclusion: using label files from V2.2 for V2.3 is safe

Ah, good catch. Forgot to change file names with the last update. Thanks. You're right, labels are the same (that's why I tried to simply re-use the translated ones).


Feat: Landmark Detection Model

Pull Request for PyVerse 💡
Issue Title : 📃: Landmark Detection Web Application

Info about the related issue (Aim of the project) :
Name: Yash K. Saini
GitHub ID: <!-- Mention your GitHub ID --
Email ID:
Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a WoB 2024 participant it's, WoB Participant)

Closes: #114
Describe the add-ons or changes you've made 📃
This pull request introduces several important changes to the Machine_Learning/Landmark_Detection project. The changes include adding a .gitignore file, creating a CONTRIBUTING.md guide, including an LICENSE file, updating the README.md, and implementing a basic Streamlit app for landmark detection.
Project Setup and Documentation:

Added .gitignore file: This file includes common patterns to ignore Python-related files and directories, ensuring a cleaner repository. (Machine_Learning/Landmark_Detection/.gitignore)
Created CONTRIBUTING.md: This guide provides instructions on how to report bugs, suggest features, and submit pull requests, encouraging community contributions. (Machine_Learning/Landmark_Detection/CONTRIBUTING.md)
Included LICENSE file: Added the Apache License 2.0 to define the terms and conditions for using, reproducing, and distributing the project. (Machine_Learning/Landmark_Detection/LICENSE)
Updated README.md: Briefly describes the purpose of the Landmark Detection project. (Machine_Learning/Landmark_Detection/README.md)

Application Implementation:

Implemented basic Streamlit app: The app allows users to upload an image and classify it using a pre-trained TensorFlow model. (Machine_Learning/Landmark_Detection/app.py)

Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Code style update (formatting, local variables)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested
Describe how have you verified the changes made
Checklist: ☑

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have added things that prove my fix is effective or that my feature works.
[X] Any dependent changes have been merged and published in downstream modules.

@UTSAVS26 review this PR & add labels to it. gssoc-ext, hacktoberfest, hacktoberfest-accpeted, Level 3

@yashksaini-coder remove unnecessary files like contributing and 'licenceand.gitignore` they are not required.

unnecessary files

@UTSAVS26 All files removed and the changes are merged. check it now


update zh_cn.json

Thanks for the translation update!
I've now added it in this commit: 4021ffd2115b76c0b02d6595849e26255f47b124


ArgumentNullException when trying to update a message after interaction with AlwaysAcknowledgeInteractions to false

With AlwaysAcknowledgeInteractions set to false (as suggested in the Readme file), I'm trying to update the original message of the interaction. After casting the interaction to SocketMessageComponent:
await interaction.RespondAsync("test", type: InteractionResponseType.UpdateMessage);
I get the following exception:
System.ArgumentNullException: Value cannot be null. (Parameter 'key')
at System.ThrowHelper.ThrowArgumentNullException(String name)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at Discord.Net.Queue.RequestQueue.GetOrCreateBucket(RequestOptions options, IRequest request)
at Discord.Net.Queue.RequestQueue.SendAsync(RestRequest request)
at Discord.API.DiscordRestApiClient.SendInternalAsync(String method, String endpoint, RestRequest request)
at Discord.API.DiscordRestApiClient.SendAsync[TResponse](String method, String endpoint, BucketId bucketId, ClientBucketType clientBucket, RequestOptions options)
at Discord.API.DiscordRestApiClient.GetInteractionResponse(String interactionToken, RequestOptions options)
at Discord.Rest.InteractionHelper.SendInteractionResponse(BaseDiscordClient client, IMessageChannel channel, InteractionResponse response, UInt64 interactionId, String interactionToken, RequestOptions options)
at Discord.WebSocket.SocketMessageComponent.RespondAsync(String text, Boolean isTTS, Embed embed, InteractionResponseType type, Boolean ephemeral, AllowedMentions allowedMentions, RequestOptions options, MessageComponent component)
at EmpyManager.Bot.Modules.TemporaryChannels.UserOwnedChannel.PerformActionAsync(String action, SocketMessageComponent interaction) in C:\Users\Torto\source\repos\EmpyManager\Bot\Modules\TemporaryChannels\EmpyManager.Bot.Modules.TemporaryChannels\Entities\UserOwnedChannel.Text.cs:line 127

Update Discord .Net Labs version to 2.3.6

Seems to be working with the new update. Thanks!


new:usr updated project report

new:usr updated project report

reject because you try to include in your pull request
paper2/proceedings.pdf
paper1/proceedings.pdf

also  see
Conflicting files
paper1/proceedings.pdf
paper2/S17-IO-3010/references.bib
paper2/S17-IO-3010/report.pdf
paper2/S17-IO-3010/report.tex
paper2/proceedings.pdf
project/S17-IO-3012/report/report.pdf
project/S17-IO-3013/README.rst
this indicates you are still changing other students reports


This is not found : Download the MiDaS small model weights into model_dir.

In https://github.com/isl-org/MiDaS


PodSecurityAdmissionConfigurationTemplates should be renamed to Pod Security Admission and under the Advanced dropdown with Pod Security Policies

Setup

Rancher version: v2.7-head https://github.com/rancher/rancher/commit/6316baf1697cca085e073ccd5e9e7a3bc542d0e5
Browser type & version: Chrome

Describe the bug

When looking at the Cluster Management, here is the current view of the left banner:

Two things here that should be addressed:

PodSecurityAdmissionConfigurationTemplates name is way too busy. This should be renamed to Pod Security Admission.
The renamed Pod Security Admission should be moved down to Advanced alongside Pod Security Policies.

To Reproduce

Setup Rancher, login as the local admin user.
Navigate to Cluster Management and review the left view pane.

Result
I see PodSecurityAdmissionConfigurationTemplates instead of Pod Security Admission not in the same place as Pod Security Policies.
Expected Result
I should see Pod Security Admission in the same place as Pod Security Policies.

@cnotv I think this is covered by the ticket Ken created for minor issues - this was reported by QA, so can be moved to test when done via that other ticket

Validated in the internal test plan that this has been addressed. As such, closing this issue.


compose notification: Notify when message is not in view.

Fixes issue #10792

@showell @timabbott Please review this.

@vrongmeal thanks for working on this!  I posted a few comments.

Hey @timabbott
I don't understand why my PR fails backend tests...
======================================================================
FAIL: test_multi_user_subscription (zerver.tests.test_subs.SubscriptionAPITest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.4/unittest/case.py", line 58, in testPartExecutor
    yield
  File "/usr/lib/python3.4/unittest/case.py", line 577, in run
    testMethod()
  File "/srv/zulip/zerver/tests/test_subs.py", line 2173, in test_multi_user_subscription
    self.assertEqual(len(add_peer_event['users']), 17)
  File "/usr/lib/python3.4/unittest/case.py", line 797, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.4/unittest/case.py", line 790, in _baseAssertEqual
    raise self.failureException(msg)
AssertionError: 18 != 17

----------------------------------------------------------------------
Ran 1531 tests in 180.394s

FAILED (failures=1)

@vrongmeal looks like a nondeterministic test failure to me.  It'll likely go away if you rebase onto current master and force-push (to trigger a new build).

@timabbott The PR is ready to be merged I guess...

Hey @timabbott, I have made the required changes, could you review this, I think it is ready to be merged.

@vrongmeal thanks for working on this!  You did the hard part of figuring out how to check if the message appears offscreen.  I cleaned up several things before merging this as 372cb20f9ede094f5a9e5e3c53494a63cf9305af:

Squashed the commits and wrote a proper commit message.  Check out the Zulip commit message guidelines for details on doing this properly: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages.  Our "Git Guide" is also helpful for the tooling mechanics.
I simplified and significantly optimize the "find where the new message you just send ended up" logic.
I also added bdc4876948f4ed39325c76823b82434cfc9de28c to fix the fact that this whole subsystem wasn't tagged for translation.

Thanks @vrongmeal!
A useful follow-up would be moving the bit of logic for figuring out whether a message is onscreen into a reusable function in message_viewport.js, and potentially deduplicating the logic in any other places it appears in the codebase.

@rishig a couple things to check on the semantics here:

This is what it looks like.  This differs from most of our other above-compose notiifcations in that it doesn't have a link to "Go to that narrow".  That's probably fine.

It also differs from the other above-compose notices in that it automatically disappears in 3s.

Now that I've seen it a few times, I think I want "Scroll down" to be a link that does the scrolling.
Though it's sort of being confounded by the fact that there are lots of instances where (IMO) we should be scrolling and we don't.

It's worth noting that the "decide whether to show it" logic has been pretty buggy for me, in the false positive direction (i.e. it shows it more often than it should).
In all cases I think it's situations where the message would be hidden if Zulip didn't apply an auto-scroll right after (or maybe it's that it would be hidden if the compose box were not to subsequently shorten?)

btw, should I open an issue for making the "Scroll down" to be a link?

Yeah, open an issue for the link if you do want it.


RU distribution in case of partition split when storage exceeded 50GB limit

[Enter feedback here]
To better udnerstand how the RU's are distributed
It will be good to have one more example about partition split when data storage is increases over 50GB.
In current version of public documentation it is presented that the RU's are evenly distributed across physical partitions. But there are cases when new physical partitions are added (partition split) due to storage increase over the 50GB limit in one partition (30 GB limit in Cassandra api).
In these cases it can happen to have uneven distribution of RU's between physical partitions.
Example: Colelction with 20k manual RU

Initial distribution: 2 physical partitions with 10k RU each.
When the data size incerease in partition 1, 2 new partitions are added and the 10RU's from partition 1 will be splited between partition 3 and 4.
At the end the RU ribution between paritions 2,3 and 4 will look like this:
p1 - 10.000 RU
p3 - 5000 RU
p4- 5000 RU

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

ID: 3d8ba849-dc38-c6ff-0b8d-e6d539d3b21c
Version Independent ID: a7cd7f7a-2836-fd5d-8f79-1ee0f1ec2d48
Content: Best practices for scaling provisioned throughput (RU/s)
Content Source: articles/cosmos-db/scaling-provisioned-throughput-best-practices.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @deborahc
Microsoft Alias: dech

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

Thank you for your feedback, @alexms1281
We considered your feedback along with other actions we are taking to improve documentation. At this time, we have elected to prioritize other documentation improvements and cannot take action on this feedback. For now, we are closing this issue. If you feel this in error, please open a new issue.
#please-close


[ERROR]Task Node(3-unzip/0-phasing/000000F) failed with exit-code=1

When I run fc_unzip.py fc_unzip.cfg, some error happen:
[INFO]Popen: 'bash -C /cloud/software/falcon/fc_env_180313/lib/python2.7/site-packages/pwatcher/mains/job_start.sh >| /cloud/software/falcon/src/FALCON-sv2/3-unzip/0-phasing/000000F/run-P3540e6096f1e47.bash.stdout 2>| /cloud/software/falcon/src/FALCON-integrate/FALCON-examples/run/greg200k-sv2/3-unzip/0sh.stderr'
[INFO]sleep 0.2s
[INFO]sleep 0.3s
**[ERROR]Task Node(3-unzip/0-phasing/000000F) failed with exit-code=1**
[INFO]recently_satisfied: set([])
[INFO]Num satisfied in this iteration: 0
[INFO]Num still unsatisfied: 4
**[ERROR]Some tasks are recently_done but not satisfied: set([Node(3-unzip/0-phasing/000000F)])
[ERROR]ready: set([])
	submitted: set([])
[ERROR]Noop. We cannot kill blocked threads.
Traceback (most recent call last):
  File "/cloud/software/falcon/fc_env_180313/bin/fc_unzip.py", line 11, in <module>
    load_entry_point('falcon-unzip==1.0.0', 'console_scripts', 'fc_unzip.py')()
  File "/scratch/cdunn/repo/fork/.git/LOCAL4/lib/python2.7/site-packages/falcon_unzip/mains/start_unzip.py", line 29, in main
  File "/scratch/cdunn/repo/fork/.git/LOCAL4/lib/python2.7/site-packages/falcon_unzip/unzip.py", line 99, in run
  File "/scratch/cdunn/repo/fork/.git/LOCAL4/lib/python2.7/site-packages/falcon_unzip/unzip.py", line 33, in unzip_all
  File "/scratch/cdunn/repo/fork/.git/LOCAL4/lib/python2.7/site-packages/falcon_unzip/tasks/unzip.py", line 266, in run_workflow
  File "/cloud/software/falcon/fc_env_180313/lib/python2.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 273, in refreshTargets
    self._refreshTargets(updateFreq, exitOnFailure)
  File "/cloud/software/falcon/fc_env_180313/lib/python2.7/site-packages/pypeflow/simple_pwatcher_bridge.py", line 339, in _refreshTargets
    raise Exception(msg)
Exception: Some tasks are recently_done but not satisfied: set([Node(3-unzip/0-phasing/000000F)])**

What should I do for fix this issuse?
Best regards
Thanks

That's the stack-trace for the workflow. You need to look for stderr somewhere under 3-unzip/0-phasing/000000F. The problem will probably become obvious.

You would need to look for a stderr file under 3-unzip/0-phasing/000000F.


Refactoring to support Cedar-Go v1.1+

The Cedar-Go library has gone through a major refactoring as it moved from 0.4.0 to v1.1.0.  This issue is to update usage Policy-Mapper usage to v1.1+
Note that to make access to the Cedar AST parser we had to shadow a number of functions (done in consultation with the Cedar-go project).  Because of this, it looks like there is a fair bit of refactoring in policy-mapper required as part of the update.

Updated and re-imported internal json package from cedar-go (because we need to expose internal JSON structures).


Add Python 3.5.2 test to CI

Add Python 3.5.2 test into docker and test script. The Python 3.5.2 replaces the 3.5.8 test as tox does not support specifying micro version.
Downgrade the base docker image from ubuntu:18.04 to ubuntu:16.04
as 18.04 only support openssl 1.1.0 which does not work with Python
3.5.2.
This closes #74

Why don't you test both 3.5.2 and 3.5.7, which behave differently on type hinting?

The Python 3.5.2 replaces the 3.5.8 test as tox does not support specifying micro version.

So, tox can specify Python35, 36, 37. If we have different micro versions, only one will be used as Python35. We can do a two round tox, but that would require two tox.ini or run Python36 and 37 twice as well.
Since the bug is in Python 3.5.2, and the later micro versions are bugfixs, and fixed the bug, testing with Python 3.5.2 might be enough. Also we are testing with Python36 and 37.


github.copilot-chat requires vscode 1.93

Something weird is happening with github.copilot-chat:
https://github.com/nix-community/nix-vscode-extensions/blob/d1980fd00e84460f6769cc1684899fead5224080/data/cache/vscode-marketplace-release.json#L2
It requires VSCode 1.93, but the latest release is 1.92.2, and the latest on NixOS 24.05 is 1.92.0.
Thus, it's impossible to enable.

Yes, it requires the proposed lmTools API
Use extension from nixpkgs as a workaround


waitlist updates

📝 Changed routes:

/index.content
/state/[state].content

(view full size)
(view full size)

Commit d045d112e67fb2232050a56803ec8ddc09bfcff8 (https://opo-data-blxl4nmjb-coa-solutions.vercel.app).


Troubleshooting Guide for NuGet Client Frequently Asked Questions

I've found users asking similar questions regularly, and believe a FAQ/Troubleshooting section on our docs page would be more discoverable, and reduce bug reports which may block the user on our reply. For example, TLS issues in Windows affect our product, so those users believe NuGet has a problem. An FAQ could provide some basic context, maybe a link, and some steps to check whether TLS is working as NuGet expects.
Example docs:
https://docs.microsoft.com/en-us/xamarin/android/troubleshooting/troubleshooting
https://docs.microsoft.com/en-us/nuget/resources/nuget-faq
There's also a self-serve docset with best practices here: https://docs.microsoft.com/en-us/style-guide/design-planning
My plan for now is to write-up what I have, then check with Justin Johnson (profexorgeek) or Mike Jones (Mikejo5000) to finalize formatting.

@donnie-msft - should the Windows connection issue be a NuGet.org FAQ or a client FAQ? I don't have a strong feeling but perhaps @zhhyu can advise on any content you were planning for the client FAQ.

https://github.com/NuGet/docs.microsoft.com-nuget/pull/2884

It seems http response code for these errors are 101, so we might want to also document the response code to help with better indexing of the doc for related search queries on these issues.

Some more context to help with prioritization: Users are hitting this Microsoft Q&A page frequently making it one of the most visited top FAQ pages as they do not find documentation for it on nuget docs (most likely reason): https://docs.microsoft.com/en-us/answers/questions/959588/visual-studio-2022-won39t-connect-to-nuget.html


chore: moving plugin from api to core

Which problem is this PR solving?

Fixes #1710

Short description of the changes

Move plugin interfaces out of API package

Not sure here but isn't instrumentation the component for all the plugin topics? Or would this result in some weird circular dependency?

Not sure here but isn't instrumentation the component for all the plugin topics? Or would this result in some weird circular dependency?

Right now we have 2 ways to write instrumentations. The old way with "plugins" that use the BasePlugin class in the core module, and the new way which uses the Instrumentation base class in the instrumentation package. The old way will be deprecated when we finish migrating our existing instrumentations to the new way. The old plugin config interface was in the API package for some reason and this just moves it to core to live with the BasePlugin


mapDispatchToProps in connect only supports functions

It appears mapDispatchToProps in the connect HoC only accepts a function as a parameter.
The original connect function in react-redux also supports an object being passed. The keys/values in this object will then be bound with dispatch.
It would be nice if this scenario is also supported by this HoC.

Actually, in the current implementation it breaks my component, since the object I pass in, is ignored entirely. The actions my component expects to be there do not exist, since connect only passes in an empty object.

Thanks! I made a more robust fix. Can you upgrade to v0.6.2?

Nice! Although, is this extra code even necessary? Wouldn't it be easier to just pass the value from componentMapDispatchToProps directly to connect in react-redux?
From what I can tell, there doesn't seem to be any additional code in this HoC that does something with mapDispatchToProps. Contrary to mapStateToProps, which adds an additional value.
Might as well let react-redux figure out how to deal with the value, right? :)

Indeed, the dispatch method is not always passed by redux. To simplify things, I was thinking to remove the  componentMapStateToProps and componentMapDispatchToProps in future versions. Move that responsibility to clients, whom will have to enhance their components with Redux connect() themselves.
Example:
const enhance = compose(
    connect(mapStateToProps, mapDispatchToProps), // redux connect
    reduxFetch(mapPropsToRequestsToProps) // react-redux-fetch connect
);

export default enhance(MyComponent);

Yeah that sounds like a sensible approach. The drawback of the current implementation is that you actually need a lot more knowledge of the inner workings of react-redux, when all you want is basically is to only extend that functionality.
+1 for recompose :)


 add some aria attributes

There are still many missing, in particular a lot of labels for accessible names.
I wasn't able to get the build system working, despite following the instructions. Perhaps it hasn't been updated for v3?

@lucaslcode
Did you follow the setup step here for build? Can you tell me how it didn't work?

I get errors that @toast-ui/toastmark can't be found, despite running npm run build toastmark

@lucaslcode
It's weird. what is your npm version?
I wrote the installation environment of the editor based on the npm 7 or or higher.


Are plans from YAML yet supported?

I have the following definition in my YAML file, after the definition of the mongodb and init pods:
plans:
  deploy:
    strategy: serial
    phases:
      mongodb-deploy:
        strategy: serial
        pod: mongodb
      init-deploy:
        strategy: serial
        pod: init

I was assuming that the init pod tasks would then be started after the mongodb pod's tasks, which is not the case.
Furthermore, if I use goal: FINISHED the tasks aren't even started! Is it even possible to start one-off tasks?

I think this now works starting with https://github.com/mesosphere/dcos-commons/commit/3f4203d9251a5d4f8cc2e3e8f650b6b70f596d6a#diff-05cc6635f070bcf4f9e8ee9a339a1d96R187 At least in my first test it was starting the pods in the right sequence.
Regarding goal: FINISHED, what would be a way to run a one-off task?
Thanks for your help!

@tobilg I believe @gabrielhartmann has a PR in works that would allow you to run one-off tasks.

That'd be great! I was simply assuming that goal: FINISHED would do this already, but that's probably not the case.
If I may ask: For what use cases is goal: FINISHED usable?

goal: FINISHED is meant to be used with tasks that aren't long-running. It can be used for following use-cases:

Running bootstrap or initialization tasks that should only be run once per cluster deployment, for ex: formatting namenode.
Running side-car tasks, like backup, restore, repair, etc.

Ok, great! That's exactly what I need. Unfortunately, I can observer that the tasks aren't even started when using FINISHED instead or RUNNING.

I guess this is related to #360

I can confirm the the plans are now getting executed in the correct order/right strategy.
What still isn't working is task goal FINISHED.

Closed as of https://github.com/mesosphere/dcos-commons/pull/403


bug found

after install it, it pop snippet window at each Space key stroke (while current line is empty or just space  char)

Try setting  "editor.acceptSuggestionOnEnter" to off.


Change Character for hscript chars

What feature do you want to get added on the base engine?
As the title states can we get the ability to change a character we added via hscript
bfGhost = new Boyfriend(bfX - 400, bfY, 'bf');
/* Stupid Example */
bfGhost = change Boyfriend('bf-car');

Please?
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

triggerEvent('Change Character', v1, v2)

triggerEvent('Change Character', v1, v2)

that's lua

That's already possible, just add your character to game.boyfriendGroup, game.dadGroup or game.gfGroup 🤦

That's already possible, just add your character to game.boyfriendGroup, game.dadGroup or game.gfGroup 🤦

@ShadowMario tell me how to then idk! I'm not a source guy.

me who's a source guy now


Add build to travisci.

Purpose
Adding build step to TravisCI. Certain items can pass tests and linting, but not the build compilation.

Coverage increased (+0.3%) to 76.155% when pulling b146074af49586cb16e03145b014f8236cc020ba on rjstires:travis-build into 42ea618808fcb0b3fcbdb7e97f47d54f16a7ad6c on linode:voldemort.


Sort-search-results button

Fixes #325
The button is now available (but does not have any functionality).
Notes:

The button-padding will get fixed when #329 is merged
I am unsure about the Ergebnisse sortieren translation

PR checklist

[x] dev-branch has been merged into local branch to resolve conflicts
[x] tests and linter have passed AFTER local merge
[x] localization is supported (Guide)
[ ] another dev reviewed and approved
[x] if feature-Branch: Teams PO has approved (show via e.g. screenshots/screencapture/live demo)

Can you add a screenshot of the Button, so I can so how it looks like? :)

It looks like this :)

(desktop, extended, english)

(desktop, english)

(mobile, english)

(mobile, extended, german)

The "problem" with that is that the button is styled the same way as everywhere else. We don't have a unified style for dropdown menus. If I change the button style the search might look better (locally) but wouldn't fit into the application.
We should probably discuss this in person tomorrow.

Yes, let's talk about it tomorrow


Minor typos

Changes made to documentation and ReadME.

I will merge and modify the couple of changes I had noted.


Rework storage layer

Goal of this PR
Fixes https://github.com/optakt/flow-dps/issues/522
This PR, along with https://github.com/optakt/golang-lru/pull/1 redesigns the storage system of the trie improvements:

Instead of being a call back, the function given to the LRU cache is an eviction handler which is called BEFORE an eviction happens
If this handler returns false, the eviction is aborted, and the element that was supposed to get evicted gets pushed back to the front of the eviction list

In the store, we run the following logic in our eviction handler:
	s.cache, err = lru.NewWithEvict(config.CacheSize, func(k, v interface{}, used int) bool {
		hash, ok := k.(hash.Hash)
		if !ok {
			logger.Fatal().Interface("got", k).Msg("unexpected key format")
		}

		// If the entry is dirty and the cache is not full, abort eviction.
		s.isDirtyMu.RLock()
		if s.isDirty[hash] && used < s.cacheSize {
			s.isDirtyMu.RUnlock()
			return false
		}
		s.isDirtyMu.RUnlock()

		// If the cache is full of dirty entries, push the current commit to disk and evict the entry.
		if s.cacheFullAndDirty(used) {
			s.forceCommit()
		}

		// If the current entry is clean, we can evict it. Otherwise, abort the eviction.
		return !s.isDirty[hash]
	})

If the entry that should be evited is dirty and there is still space in the cache, we can safely abort the eviction. Aborting it will result in this entry going back all the way to the other side of the eviction list.
If the cache is full and that all of its entries are dirty, we force the current transaction to be committed and evict the entry.
Otherwise, determine whether or not to evict the value based on whether it is dirty.

Note: This PR includes changes that add error returns to the Insert method, which will conflict with the changes that @awfm9 will bring later on. It should be easy to solve those conflicts however: we just take the code from Max and add error handling in the only remaining case where we create a leaf.
Checklist
Does the PR require tests to be added or updated?
This PR probably requires adding more tests, yes.
Does the PR require documentation to be added or updated?
No
Misc

[x] PR title will be clear as part of the changelog
[x] PR is against the correct branch
[x] PR is labelled appropriately
[x] PR is linked to an issue

Merging this in the meantime, but @awfm9 if you want to change the way we handle https://github.com/optakt/flow-dps/pull/523#discussion_r787636038 please LMK and we can do it in another PR. I don't want to block this one for 10 more days though so I'll merge it now to be able to move fwd on the trie improvements.


Bump kube-state-metrics to v1.7.0

Let's wait until v1.7.0 with merging.

happy to merge this and get people testing it

Ok! :+1:

I had to push some commits @metalmatze to this PR, as we were seeing errors in kube-state-metrics logs.
cc @s-urbaniak as discussed offline PTAL :) Thanks!


[ja] Translate content/en/docs/reference/glossary/limitrange.md into Japanese

Note that this issue is for Japanese Speaker
This is a Feature Request
What would you like to be added
Translate content/en/docs/reference/glossary/limitrange.md into Japanese
Why is this needed
There is no Japanese translation for this page
Comments

File to translate:

https://github.com/kubernetes/website/blob/main/content/en/docs/reference/glossary/limitrange.md

Original:

https://kubernetes.io/ja/docs/reference/glossary/?all=true#term-limitrange

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

Japanese Localization document: https://kubernetes.io/ja/docs/contribute/localization/

/area localization
/language ja
/good-first-issue
/triage accepted

I would like to work on this issue. Can you please assign this issue to me.

Thank you for showing interest in the Japanese l10n subproject.
As mentioned in the issue description, please note that this is an issue  for Japanese speakers.

Note that this issue is for Japanese Speaker

It appears that you are living in India.
If you are a Japanese speaker, feel free to proceed. If not, it would be better to raise your hand for an issue related to Hindi:

all issues labeled language/hi: https://github.com/kubernetes/website/issues?q=is%3Aopen+is%3Aissue+label%3Alanguage%2Fhi

If you decide to proceed, please comment with /assign.
(You have commented on some issues, but I recommend working on one at a time for your first contribution.)⬤

/assign


Chapter 13 - section on preprocessing the input features missing

Hi Aurelien,
Within the Jupyter note for Chapter 13 on data processing with TF, I don't see the section titled "Preprocessing the Input Features" that you have in your book (a fairly long one, before "TF Transform").
Instead, I see "The Features API" section in the note (which is not in the book).
Looks like cool stuff, but I get errors when running it.
Thanks.
Gene.

Thanks for your feedback, Gene. You're right, I should add the code for that section in the notebook, thanks for pointing it out. Funny story: I spent a few weeks working on writing the part about the Features API, then one of the reviewers from the TF team reviewed the book and recommended that I drop that section because "it's not future proof". Indeed, the TF team is moving away from the Estimators API and the Features API (which go hand in hand). So I scratched everything I had written and started again from scratch! Unfortunately, it seems that I forgot to update the notebook. I'll try to do this asap (but I'm currently very busy as I'm moving to New Zealand shortly, so it might take a few weeks).
I'm surprised that you're getting errors when running the Features API section: if you open the notebook in Colab, it runs without any error (apart from some error messages during the installation of TFX at the very beginning, but these can be safely ignored for this notebook). Can you try checking that the library versions are identical?

Yeah, I figured that you had to have the code somewhere, since it's published in the book :)
Good luck!


New cluster attached to existing FSx filesystem

I'm trying to create a new cluster that uses the existing persistent FSx filesystem I created for another cluster. I've copied over the VPC settings from the first cluster and created a security group opening port 988 for that VPC. When I run plcuster create, I get the following error:
AWS::EC2::Instance MasterServer Received FAILURE signal with UniqueId ...

I suspect it may have something to do with Security Group / VPC settings, but I'm not sufficiently experienced to understand how to do this correctly.

Turns out I needed to associate the new security group with the FSx filesystem.


cb_fn can be called more than once with no way of knowing when the last one is

When the request is larger than the maximum IO size OR striping is enabled, _nvme_ns_split_request will be used to break the request up into multiple ones: https://github.com/hgst/libnvme/blob/master/lib/nvme/nvme_ns.c#L231
However, it just passes the cb_fn to each of these. So any consumer of this API will have the cb_fn called more than once, and it cannot be reasonably expected to keep track of how many sub-requests there are and when the last one has completed.

It appears SPDK still has this problem. So, is there some way to detect when the last request in a parent/child chain is completed that I am missing?

Ah, it appears I missed that nvme_request_cb_complete_child does handle this case. So the bug I am running into must be on my end.
It still seems strange, though, that the cb_fn is passed through during creation of the child request if it is not supposed to be called. So maybe this should be changed anyway?


useEffect status RFC

A status parameter for useEffect/useLayoutEffect callbacks.
There are some discussions in #137
View formatted RFC

Interesting idea indeed. Thanks

As AbortSignal is part of the platform and spreading, other libraries will likely start adopting AbortSignal and when they do manual cleanup code can be replaced with just passing the standard AbortSignal to them

😅 Actually, I think I underestimated the spread of this feature. Apparently Chrome 88 already supports AbortSignal on addEventListener.
https://css-tricks.com/using-abortcontroller-as-an-alternative-for-removing-event-listeners/
i.e. This code:
useEffect(() => {
  function paste(e) {
    console.log('Pasted', e);
  }
  window.addEventListener('paste', paste);

  return () => {
    window.removeEventListener('paste', paste);
  };
}, []);

If status was actually an AbortSignal, could be replaced with the following at least for browsers that support it (hopefully there's a polyfill).
useEffect((signal) => {
  function paste(e) {
    console.log('Pasted', e);
  }
  window.addEventListener('paste', paste, { signal });
}, []);

Looks like #204 includes the following in addition to the AbortSignal arg:

Accept generator functions so that React can take charge of how async things runs inside the effect.

Which IMHO is enough reason to keep this one around even if this one switches to AbortSignal too. Cause that kind of change is highly likely to stop the RFC from moving on.


created binary search.cpp using recursion method(hacktoberfest 2022)

Great work please give this repo a star and follow me for follow back 😊✨


[✨ Feature Request]: raise a more descriptive exception when no queries are defined for a Dataset

Is your feature request related to a problem? Please describe.
While familiarizing myself with the framework, I defined a Dataset object and added some examples to it. At first, I forgot to add queries before attempting to call evaluator.train(dataset, generator=False) and received the following NullPointerException:
Py4JJavaError: An error occurred while calling o176.collect.
: java.lang.NullPointerException
at cz.cvut.fel.ida.neural.networks.structure.building.Neuralizer.getQueryMatchingLiterals(Neuralizer.java:250)
at cz.cvut.fel.ida.neural.networks.structure.building.Neuralizer.supervisedNeuralization(Neuralizer.java:171)
at cz.cvut.fel.ida.neural.networks.structure.building.Neuralizer.neuralize(Neuralizer.java:145)
at cz.cvut.fel.ida.pipelines.pipes.specific.SupervisedNeuralizationPipe.lambda$apply$1(SupervisedNeuralizationPipe.java:38)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at java.base/java.util.stream.ReferencePipeline$11$1.accept(ReferencePipeline.java:442)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357)
at py4j.Gateway.invoke(Gateway.java:282)
at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
at py4j.commands.CallCommand.execute(CallCommand.java:79)
at py4j.GatewayConnection.run(GatewayConnection.java:238)
at java.base/java.lang.Thread.run(Thread.java:829)

Describe the solution you'd like
A more descriptive error could be raised in case the dataset does not contain any queries. Since it is an exception triggered by the Java backend, it is possible that it should be handled there. In that case, please let me know and I will move this issue to the backend repo.
Describe alternatives you've considered
No response
Additional context
No response

Hi, thanks for opening the feature request.
I added checks and more descriptive exceptions for cases with no queries and released them in PyNeuraLogic v0.1.1.
When there are no queries in the queries list (or queries in the example list), it will throw an exception.


Demo Request - containerTemplate on property

I was hoping to get some clarification about how to use the on property found in the containerTemplate function.
https://github.com/krakenjs/zoid/blob/master/docs/api.md#opts
I have a form that I'm embedding in a zoid iframe component. Let's say this form is 350 x 400 in dimension. This form has some fields which have dropdown menus (e.g. autocomplete). When these form fields are activated the dropdown menus may render with a height much taller then 400px. What I would like to do is extend the height of the iframe while keeping the zoid-context-iframe and zoid-outlet dimensions the same (400 height). This would allow the drop down menus to appear they are overflowing outside the iframe container.
In my iframe.html file where my form is embedded, I have a function which detects when a dropdown menu is open, and I calculate how much height is required to display the form and dropdown. I am firing an event using: window.xchild.sendToParent('onHeightChange', { height: 1000 });.
My question is, can I handle this in the containerTemplate function using the on property e.g. on('onHeightChange', function() { ... }) ? I've tried to use this handler but it does not get called. I would rather not handle this as a component property, I don't want to expose this functionality to an end user, it's best kept internally.
Any help would be appreciated.
Thanks

@davepenfold
Did you manage to get this to work? I'm attempting to do a similar thing currently but with no luck.


HODL API getHODLStatus should be able to block all HODL activity

Needed for maintains. If getHODLStatus doesn't success, all other API call results must be ignored.

Test scenario:
0. Work with QT wallet normally. Check if HODL account works well, there are output in HODL, send shows warnings, e.t.c.

Ask Chris to switch HODL server into maintenance mode.
Clean up qt wallet logs
Start QT wallet. Check UI, HODL pages should show that HODL under maintenance. No claims info should be shown.
Check Output page. Verify that you HAVE outputs in the HODL (info should come form cache). Send should show the warnings about that.
Validate logs. Check that for HODL we call only 'getHODLStatus'

cat  mwcwallet.log | grep seed2.mwc.mw
airdropUrlTestNetUrl=https://seed2.mwc.mw:8443
29.04.2020 12:44:32.182 Airdrop Requesting: https://seed2.mwc.mw:8443/v1/claimsAvailable
29.04.2020 12:44:32.183 HODL Requesting: https://seed2.mwc.mw:8443/v1/getHODLStatus
29.04.2020 12:44:32.547 Airdrop Fail respond for Tag: airdrop_claimsAvailable  requestErrorMessage: Error transferring https://seed2.mwc.mw:8443/v1/claimsAvailable - server replied: Not Found
29.04.2020 12:44:36.102 HODL Requesting: https://seed2.mwc.mw:8443/v1/getHODLStatus
29.04.2020 12:44:46.927 HODL Requesting: https://seed2.mwc.mw:8443/v1/getHODLStatus
29.04.2020 12:44:47.898 HODL Requesting: https://seed2.mwc.mw:8443/v1/getHODLStatus
Note claimsAvailable - it is Airdrop API and it is expected to call.

Ask Chris  switch HODL server into normal mode.
Revisit HODL page and see that everything is back to normal

Worked with Jim on this and confirmed everything worked for maintenance mode.


fix for Cannot read property 'head' of undefined

I'm receiving such error for each build: UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'head' of undefined
You can find more details here: https://github.com/lkurzyniec/netcore-boilerplate/runs/785983375
My fix could resolve the issue. I don't have experience in writing of github actions, so please test it thoroughly.
One important question - why did you commit whole node_modules dependency folder? By this your repo is more than 200 MB. You should add this particular folder to .gitignore and remove whole folder. Dependencies can be installed by npm install.

@lkurzyniec Thanks for the PR. I'll test it and get back to you.
On your note of committing the node_modules directory, I understand it's not a normal practice, but it's required when you commit and push action to github.
Reference here: https://help.github.com/en/actions/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action-to-github

Ok, you are right, docs says that awful directory is required. But! I'm wondering how it works for them https://github.com/codecov/codecov-action. They also have package.json with dependencies. Maybe it's a matter of dist/index.js file?
Some more examples: https://github.com/atlassian/gajira-login, https://github.com/atlassian/gajira-cli

Now I do see all other repos are doing that, which i think your point is right on... index must contain the compiled code. I’ll investigate... it’d awesome to get rid of that folder!

@lkurzyniec Your fix doesn't work for my repo for some reason. I think it's the branch name that somehow gives me trouble. In my case, instead of a real branch name, it returns /ref/merge/2. Do you see the same thing?

@atlwendy I'll double check it on my side later on in the week. I'll inform you about the results.

@atlwendy I dig into the problem and it's not so easy. You can read more info here https://stackoverflow.com/q/58033366/4197899 and especially this answer https://stackoverflow.com/a/59780579/4197899.
You get refs/pull/2/merge because it is a pull request from my repo. When you commit and/or create PR from your own repo everything should works fine.
And now, should we omit/skip CI/CD for somebody's PR to our repo? IMHO we should not. We should only skip for ours commits.
This is the reason why I slightly change my PR.
What do you think?

@lkurzyniec Hmm... I actually copied over your changes to one of my branches. Then used another repo to test out the action. I logged out the process.env that you used in the code, and it showed that process.env.GITHUB_REF returning refs/pull/2/merge. But process.env.GITHUB_HEAD_REF does return the actual branch name. Do you see it differently?


Fixes #1681: remove unsupported AMQP link detach handling

Verified that the router currently responds to a received detach(close=False) with detatch(close=True) unconditionally. If the detaching client then attempts to re-attach via pn_link_open() - as per this section of the AMQP 1.0 Spec then the link simply hangs.


Remove FP16 specific models from imagenet example

This PR removes FP16 specific models from imagenet example as we now have the default dtype feature, which perfectly works to run the example in FP16 mode without any change of the script.

Remaining is to check if it works properly with --dali option.

Removed AlexFp16 and GoogLeNetBNFp16 uses HeNormal(1 / np.sqrt(2)) as  the initializer of their weight parameters, which is equivalent to LeCunNormal() that is used in AlexFp16 and GoogleNetBN.

I applied the changes!

Jenkins, test this please

Jenkins CI test (for commit c41fb6b0e2fea87ea5cfae300291d916f70b5fab, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins test needs to be rerun. Jenkins, test this please.

Jenkins CI test (for commit c41fb6b0e2fea87ea5cfae300291d916f70b5fab, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Appveyor failure looks unrelated. Merging!

@Crissman This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@Crissman Could you make a backport PR?

@Crissman This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@Crissman This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@Crissman This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@Crissman This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

I made a backport.


[CT-472] postgres: Retry n times on connection timeout

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Runs/builds/tests can create hundreds of independent database connections depending on the size of the project and a single connection timeout due to transient network connections, EC2 load (e.g. RDS case when connecting through EC2), or postgres load can cause an entire run to fail. Connection timeouts can be, and most often are, transient and will often succeed on a retry.
Describe alternatives you've considered
No response
Who will this benefit?
Anyone using the postgres connector.
Are you interested in contributing this feature?
No response
Anything else?
This would be similar to connect_retries on Snowflake.
See: https://github.com/dbt-labs/dbt-snowflake/pull/6/files

Thanks @barberscott! I think this will be the place for the change, for both Postgres and https://github.com/dbt-labs/dbt-redshift/issues/96, since they both use dbt-postgres's psycopg2 connection.
There are related recommendations in #3303 around:

Specific error codes/messages to capture as transient, and likely to succeed on retry
A proposal for user-specified "retryable" errors, as another config in profiles.yml

At this point, given precedent in other adapters (Snowflake + Spark), I'm not opposed to a naive retry_all parameter. It makes sense to turn on in production (best-possible chance at query success), and leave off in development (quicker iteration on errors).
I sense we'd need to add both complementary configs (connect_retries + connect_timeout), with reasonable defaults. Perhaps we also want to add our attempt at retry_on_database_errors, based on the psycopg2 errors we strongly believe to be transient.

Hey all, since this issue is significantly hindering us, I went ahead and modified the Postgres adapter to take a stab at fixing it.
The basic premise was modifying PostgresCredentials to take in the new connect_retries and retry_on_errors parameters:
@dataclass
class PostgresCredentials(Credentials):
    host: str
    user: str
    port: Port
    password: str  # on postgres the password is mandatory
    connect_retries: int = 3  # 3 seemed like a sensible default number of retries
    connect_timeout: int = 10
    role: Optional[str] = None
    search_path: Optional[str] = None
    keepalives_idle: int = 0  # 0 means to use the default value
    sslmode: Optional[str] = None
    sslcert: Optional[str] = None
    sslkey: Optional[str] = None
    sslrootcert: Optional[str] = None
    application_name: Optional[str] = "dbt"
    retry_on_errors: list[str] = [
        "08006", # ConnectionFailure
    ]
...

Users can set SQLSTATE codes that they wish to retry on. I'm uncertain whether taking codes is the right approach instead of exception class names (or allowing both).
Afterwards, I added an except clause for these errors in a connection loop added to PostgresConnectionManager.open:
    @classmethod
    def open(cls, connection):
        ...

        retryable_errors = tuple([psycopg2.errors.lookup(error_code) for error_code in credentials.retry_on_errors])

        attempt = 0
        while True:
            try:
                handle = psycopg2.connect(
                    dbname=credentials.database,
                    user=credentials.user,
                    host=credentials.host,
                    password=credentials.password,
                    port=credentials.port,
                    connect_timeout=credentials.connect_timeout,
                    **kwargs,
                )

                if credentials.role:
                    handle.cursor().execute("set role {}".format(credentials.role))

                connection.handle = handle
                connection.state = "open"

            except retryable_errors as e:
                logger.debug(
                    "Got a retryable error on attempt {} to open a postgres " "connection: '{}'".format(attempt, e)
                )

                attempt += 1
                if attempt < credentials.connect_retries:
                    continue

                logger.debug(
                    "Attempt number reached or exceeded {} retries when opening a postgres connection".format(credentials.connect_retries)
                )

                connection.handle = None
                connection.state = "fail"

                raise dbt.exceptions.FailedToConnectException(str(e))

            except psycopg2.Error as e:
                logger.debug(
                    "Got an unknown error on attempt {} to open a postgres " "connection: '{}'".format(attempt, e)
                )

                connection.handle = None
                connection.state = "fail"

                raise dbt.exceptions.FailedToConnectException(str(e))

        return connection

Some iteration over the code is most likely needed (as well as documentation). However, would this work for a PR? I'll be glad to add any necessary testing + documentation and contribute this.
Thanks.

@tomasfarias I'd be very supportive of a PR for this, if you're open to submitting one! My main recommendation would be, in keeping with Nate's suggestion — rather than ask users to list error codes that are retryable, let's try to develop a good set for starting out. I'm particularly interested in connection errors / timeouts.

I'll submit a PR for this week. I've also been looking into dbt-bigquery and dbt-snowflake to ensure the retry implementation can be re-used across adapters, and it's not just a dbt-postgres/redshif thing.
Thanks for the patience, I've been on vacation for the last couple of weeks.


Add support for Strimzi Kafka in KameletBinding/Pipe

With https://github.com/apache/camel-k/issues/1686, support for Strimzi's KafkaTopic has been added, however it would be nice to have support for Strimzi's Kafka CRD also, something like:
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: twitter-stream-binding
spec:
  source:
    ref:
      apiVersion: camel.apache.org/v1alpha1
      kind: Kamelet
      name: twitter-stream
    properties:
      keyword: Camel K
      secret: ...
  sink:
    ref:
      apiVersion: kafka.strimzi.io/v1beta1
      kind: Kafka
      name: my-cluster
    properties:
      topic: "my-topic"

This way a user could override the topic, i.e. in a step to perform some sort of CBR among topics

As I'm working on this very same context, I may try to do this for 2.3 release. @lburgazzoli do you think is it still worth doing?

As I'm working on this very same context, I may try to do this for 2.3 release. @lburgazzoli do you think is it still worth doing?

+1


Document the HTTP action provider

This branch adds documentation for the upcoming HTTP action provider, including:

The URL and scope
Complete documentation of all input document keys and values
Examples of usage
Documentation of the errors that may be returned by the HTTP action provider, including suggestions for how to resolve the errors.

[sc-11704]

Note that the changes in b6defdd depend on https://github.com/globusonline/globus-automate/pull/218.

Updated to remove references to the user-configurable timeout key (which is no longer supported) and to document the new HTTP response size and total timeout errors.

The HTTP action provider is currently for internal use. Once this restriction is lifted this can be reviewed and merged.


Please allow graphical mgmt like create DB, managing logins etc. like in SSMS.

Created from twitter feedback: https://twitter.com/borgdylan/status/930894693487071233. Request is for graphical create database and user / login management. We can track using this issue.

Thanks for adding my issue.

We added Database Administration Tool Extensions for Windows extension to the gallery this month to fill this gap.  Please log new issues for any missing dialogs.

That extension only covers the Windows use case. Is naything planned for other OSes?