Any plan to release 0.3.1?

Sorry to post here, if there is a forum to discuss it, I am happy to move this topic to :-)
The lase release: 0.3.0 has been released half a year, do you have any plan when to release 0.3.1? Thank you very much! :-)

I second this. A project I'm working on depends on some of the new functionality. Thank you!

+1

+1 waiting for the new release.

+1 waiting for latest release

+1 for the new release

I would like to prepare a release for next week...Is there something which should be come into the release ?

Can you take a look at the jarjar pull request for guava? I'm not sure if the author ever cleaned it up per my comments. I would like to get that in so that we can keep this working with Stash.

So we have a release in a staging repository available:
https://oss.sonatype.org/content/repositories/comoffbytwo-1008
Can someone take a look on it...

Great news.
I tested the 0.3.1 against the staging repository, it works great on my cases(getJob,createJob,updateJob, JobWithDetails.build(), etc).

So release is done and within a few hours available from maven central.


403 error when generating a model

I've been getting the following when I try to generate a model:
dpipkin@CORP-WEB01:~/neo_blog$ rails generate scaffold User name:string email:string
/usr/local/rvm/gems/ruby-2.1.2/gems/neo4j-core-4.0.7/lib/neo4j-server/resource.rb:33:in `handle_response_error':
Expected response code 200 Error for request http://localhost:7474/db/data/, 403, 403
(Neo4j::Server::Resource::ServerException)
...

and my config file looks like this:
require File.expand_path('../boot', __FILE__)

require "rails"
# Pick the frameworks you want:
require "active_model/railtie"
require "active_job/railtie"
# require "active_record/railtie"
require "action_controller/railtie"
require "action_mailer/railtie"
require "action_view/railtie"
require "sprockets/railtie"
require 'neo4j/railtie'
require "rails/test_unit/railtie"

# Require the gems listed in Gemfile, including any gems
# you've limited to :test, :development, or :production.
Bundler.require(*Rails.groups)

module NeoBlog
  class Application < Rails::Application

    config.generators do |g|
      g.orm             :neo4j
    end

    # Configure where the embedded neo4j database should exist
    # Notice embedded db is only available for JRuby
    # config.neo4j.session_type = :embedded_db  # default #server_db
    # config.neo4j.session_path = File.expand_path('neo4j-db', Rails.root)
    config.neo4j.session_path = 'http://localhost:7474'
    config.neo4j.session_options = { basic_auth: { username: 'neo4j', password: 'neo4j' } }

    # Settings in config/environments/* take precedence over those specified here.
    # Application configuration should go into files in config/initializers
    # -- all .rb files in that directory are automatically loaded.

    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
    # config.time_zone = 'Central Time (US & Canada)'

    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
    # config.i18n.default_locale = :de
  end
end

Hrmmm, the 403 might mean that the password isn't correct.  Did you change it when going to the web console?  If it isn't that, you could try troubleshooting it by disabling auth to see if auth is the problem:
http://stackoverflow.com/questions/29096616/how-to-disable-basic-auth-on-neo4j-2-2-0-rc01
You also might want to uncommend the session_type line and make it :server_db instead of : embedded_db

When I disabled auth it worked. I hadn't changed the password through the web console so I'm not sure what the underlying issue was.

Interesting.  I've not tried this, but you might check out this post about resetting the password:
http://zacharywolffs.ghost.io/2015/04/08/changing-password-in-neo4j-v2-20/
Closing, but feel free to re-open if you need anything else


Utilizing subaccounts / credentials

I was looking over this library out of curiosity (not yet using on a project). I use Twilio Ruby heavily and was comparing against this. One thing that I noticed is that it might not be possible to specify the account sid / token that an API request will be made against.
Is it possible to specify the sid / token that an API request will make?
If it's not, is this something you'd consider accepting a PR for? I was looking at how I might go about it and do not see an obvious path forward currently which is why I ask.

Try this:
ExTwilio.Message.create(%{to: "15196356330", from: "16666666666", body: "hellow world"}, [account: "XXX", token: "YYY"])

Thanks, I think you're right!


commit in example seems redundant

The commit  statement here seems redundant, I have removed this line and the code runs ok.
And I just went through the code , I found the command already called commit in exec_cmd.

Hi,
Thanks for reporting this issue :)
This is indeed a typo in the code. I already noticed it is fixed on my development version which will be released as soon as #101 is merged (this will be a major release, technically this weekend or next week).
The fix will remove the call to .commit inside exec_cmd such that you need to call commit on your side to flush the pipelined commands as expected.
Please let me know if you have any other questions.
Best,


Turicreate sometimes randomly uses GPU and other times can only find the CPU when using a MacPro with FIrePro D300

I've been training a model and when sometimes train its, it sometimes can find the GPU, and sometimes can't.  If it does find a GPU to use on the MacPro it will keep using it, until I reboot that instance of Anaconda and Jupyter.  If restart the instance of Jupyter it stop working again and only uses CPU.  Is this a known bug?

This is not a known bug.
Only certain models in Turi Create use the GPU, see the GPU Support of our README for a list of those models. Perhaps this explains the behavior you're seeing.

I understand that, I'm using Object Detection and it's the same model each time on different machines, but both machines (Mac Pro with two FirePro D300's) and a a MacBook Pro with a Radeon Pro 460 with the same configurations randomly use GPU.  Once I get one using GPU, I make sure I never reboot it, because after I do GPU stops working again.  This is really odd, when I try to force the GPU, I get the error that there is no GPU that is suitable.

@yungdai - Sorry you are having this problem. Unless we can reproduce this issue, it's going to be very difficult for us to fix it. I know you said it seems to be random, but if you can find steps to reproduce it, that would be ideal.
If you are not using the most recent version Turi Create (currently that's 5.1), please upgrade to that.
What macOS version are you using?
What is the exact error message you get about no suitable GPU?

I'm using Turicreate 5.1, I'm using macOS 10.14.1 Beta 4(18B67a).  I'll get you the error when I finish this CPU training.  It's taking a looooong time with CPU.

The error I"m getting is the following.
"Using 'image' as feature column
Using 'annotations' as annotations column
ToolkitError                              Traceback (most recent call last)
 in ()
9
10 # Create a model
---> 11 model = tc.object_detector.create(train_data, max_iterations=5000)
12
13 # Save predictions to an SArray
~/anaconda3/envs/turienv/lib/python3.6/site-packages/turicreate/toolkits/object_detector/object_detector.py in create(dataset, annotations, feature, model, classes, max_iterations, verbose, **kwargs)
229     num_anchors = len(anchors)
230
--> 231     num_gpus = _mxnet_utils.get_num_gpus_in_use(max_devices=params['batch_size'])
232     batch_size_each = params['batch_size'] // max(num_gpus, 1)
233     # Note, this may slightly alter the batch size to fit evenly on the GPUs
~/anaconda3/envs/turienv/lib/python3.6/site-packages/turicreate/toolkits/_mxnet_utils.py in get_num_gpus_in_use(max_devices)
77     # Unlike turicreate.config.get_num_gpus() which returns an option that may
78     # be set to -1, this function returns GPUs actually in use.
---> 79     gpu_ctx = [ctx for ctx in get_mxnet_context(max_devices=max_devices) if ctx.device_type == 'gpu']
80     return len(gpu_ctx)
81
~/anaconda3/envs/turienv/lib/python3.6/site-packages/turicreate/toolkits/_mxnet_utils.py in get_mxnet_context(max_devices)
42     from turicreate.util import _CUDA_GPU_IDS
43     import mxnet as _mx
---> 44     assert_valid_num_gpus()
45     num_gpus = _tc_config.get_num_gpus()
46     if num_gpus == 0 or not _CUDA_GPU_IDS:
~/anaconda3/envs/turienv/lib/python3.6/site-packages/turicreate/toolkits/_mxnet_utils.py in assert_valid_num_gpus()
84     num_gpus = _tc_config.get_num_gpus()
85     if not _CUDA_GPU_IDS and _sys.platform == 'darwin' and num_gpus > 0:
---> 86         raise _ToolkitError('Using GPUs is currently not supported on Mac')
87     _numeric_param_check_range('num_gpus', num_gpus, -1, _six.MAXSIZE)
88
ToolkitError: Using GPUs is currently not supported on Mac"

AFAICT that error is from turicreate-4.3.2. Consider this portion of your traceback:
~/anaconda3/envs/turienv/lib/python3.6/site-packages/turicreate/toolkits/object_detector/object_detector.py in create(dataset, annotations, feature, model, classes, max_iterations, verbose, **kwargs)
229 num_anchors = len(anchors)
230
--> 231 num_gpus = _mxnet_utils.get_num_gpus_in_use(max_devices=params['batch_size'])
232 batch_size_each = params['batch_size'] // max(num_gpus, 1)
233 # Note, this may slightly alter the batch size to fit evenly on the GPUs

Line 231 appears as indicated for this file in 4.3.2, but not 5.1:
https://github.com/apple/turicreate/blob/v4.3.2/src/unity/python/turicreate/toolkits/object_detector/object_detector.py#L231
https://github.com/apple/turicreate/blob/5.1/src/unity/python/turicreate/toolkits/object_detector/object_detector.py#L231
Please double-check what version of turicreate you have installed on the affected machines!


feat(cli): return nonzero exit code on failed validation

addresses #17
the validate function currently returns an aggregation of errors and warnings, if any were found.
This gives us the opportunity to make the process return a nonzero status code, which makes it possible to use the CLI in Continuous Integration or git hooks.

That's a good suggestion and thank for the PR! but I would like this functionality to be added as an optional param that can be passed in CLI. So when we pass the option -e or --exit-on-err it would exit the process. Raised #19 to address this.

Good thinking, that way it'll stay compatible. I'll raise a new PR with the flag then!


4.x can't use gdal plugin with /vsi paths

node-mapnik's gdal plugin doesn't follow GDAL's virtual filesystem (/vsicurl or /vsis3) paths for some reason.
Background: here's a small TIF file in S3
root@cff8afe58600:/app# gdalinfo -nomd /vsicurl/https://kx-craig-misc-test-bucket.s3.ap-southeast-2.amazonaws.com/v4-8018-5194.tif
Driver: GTiff/GeoTIFF
Files: /vsicurl/https://kx-craig-misc-test-bucket.s3.ap-southeast-2.amazonaws.com/v4-8018-5194.tif
Size is 8453, 16384
...

However, this minimal JS script using node-mapnik can't seem to load it:
root@cff8afe58600:/app# ./test-vsis3-url.js
ERROR 4: /vsicurl/https://kx-craig-misc-test-bucket.s3.ap-southeast-2.amazonaws.com/v4-8018-5194.tif: No such file or directory
[Error: /vsicurl/https://kx-craig-misc-test-bucket.s3.ap-southeast-2.amazonaws.com/v4-8018-5194.tif: No such file or directory  encountered during parsing of layer 'x' in Layer]

versions:

Tested (failing) with node-mapnik 4.0.0 and 4.5.9.
It previously worked fine for us using a really old version (1.4.15)

It looks like the gdal plugin is statically compiled these days (so no longer depends on having libgdal installed separately at runtime). Any idea what version of GDAL it's pulling in and how it's building it?

Hi @craigds - right, I think the statically compiled GDAL linked into the plug-in is likely the limitation. My understanding is that VSI needs curl and linking curl statically would have been quite involved due to the need for OpenSSL for SSL support in curl.
So I doubt this is a GDAL version issue as much as how it was compiled in the binaries provided.
If fixing this is important, feel free to reach out to me by email to discuss.

that makes sense, thanks. Is it possible to build it without static linking? I looked for docs on this but didn't find much yet. I'm not a JS native so forgive me if I've overlooked something really basic


Output tab does not show cyrrilic symbols

Issue Type: Bug
The only enabled extension is C# extension for VSCode.
System language is ru-RU.
VSCode interface language was both english and russian (russian language extension pack), issue happened on both.
Dotnet --version returns 6.0.101 .
Steps to reproduce:

Make any change in project to make omnisharp asking executing "dotnet restore" command. Deleting /obj folder and restarting omnisharp server might do the job.
Accept executing "dotnet restore" command from omnisharp pop-up.
In Output tab any cyrillic symbol is replaced with rombus with "?" symbol on it.

Other than output tab, everything is normal and shown correctly (in debug console tab, in problems, in integrated terminal).
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.91GB (8.50GB free)

Process Argv
--crash-reporter-id de6d76a4-5091-497f-b5c6-b5d71a3bc989

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

csharp
ms-
1.23.17

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vscop804:30404766
vs360:30404995
vsrem710cf:30416617
vscexrecpromp3t1:30407762

It seems this output channel is owned by csharp extension, can you please first reach out to csharp extension and let them investigate first to see if they are doing something different. Otherwise, It would be great if you can provide a sample extension with source code to reproduce this. Thanks


Issue with autocompletion in portable-pty terminal, used in running scripts.

Describe the bug
Issue with autocompletion in portable-pty terminal, used in running scripts. seems to be an issue with the package portable-pty used as another terminal instance to run other bash scripts such as in utils.
To Reproduce
Steps to reproduce the behavior:

Go to Utils and run any script
if  tab is pressed for autocompletion, it doesn't work.

Expected behavior
similar behaviour as the terminal which is used.

Linutil has no support for tab-completion. Also most shells only have support when specifying a command to use before hand.
/close


Implement and track pricing clicks #124

fixes problem #124
closes #124
Add get in link[link?plan=number], add send to ga click info

@etf-yrm Is this in alignment with https://github.com/WoTTsecurity/api/pull/335?

@vpetersson Yes

@etf-yrm Is this in alignment with WoTTsecurity/api#335?

@vpetersson Yes

@etf-yrm Can we please use more readable values than 1,2,3 for the type of plan? You should always be able to look at a variable and determine what it does/is without context. There is literally no upside in saving a few characters in 2019.

@etf-yrm Can we please use more readable values than 1,2,3 for the type of plan? You should always be able to look at a variable and determine what it does/is without context. There is literally no upside in saving a few characters in 2019.

@vpetersson Done in last commit

I think there's a misunderstanding here. I get where the 1..4 is coming from. My point was that they are not very useful in the context of Google Analytics. When you look at the events fired off to Google Analytics, you need to be able to look at them and understand what they are. 1..4 isn't very descriptive. It should be the actual plan as the event, such as 'Clicked Signup for Standard'.


Add integration tests

Complete adding integration tests

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 98.03922% with 1 line in your changes missing coverage. Please review.

Project coverage is 99.30%. Comparing base (885fd80) to head (db430e3).

Files
Patch %
Lines

src/ClientBase.php
91.66%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main       #7      +/-   ##
============================================
+ Coverage     98.23%   99.30%   +1.06%
- Complexity      120      126       +6
============================================
  Files            35       36       +1
  Lines           511      430      -81
============================================
- Hits            502      427      -75
+ Misses            9        3       -6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ARO Gateway Work

Gateway installer work

@mjudeikis hold for https://github.com/Azure/ARO-RP/pull/1492

I'm going to rebase release-4.7-azure on top of upstream release-4.7 branch to bring latest fixes + to fixup diff: I'm squashing some commits together so it is more clear that they belong to a specific feature.
You will probably have to rebase your PR. Sorry about that.
Before we merge, could we make sure that:

Commit messages are meaningful. We already have commits in our diff with the upstream installer with messages "HACK: use dnsmasq for cluster DNS" and "CARRY: HACK: commit data/assets_vfsdata.go".
Make sure that we do not generate a merge commit (rebase and fast forward merge please)


Incorrect License Change from MIT to ISC

I noticed that the original project was under the MIT license, but it seems you've changed it to the ISC license after forking. While the MIT and ISC licenses are similar, they are not the same, and changing the license without the explicit permission of the original authors might not be appropriate or legal.

sorry for mistake. I saw the github detected the original license as "ISC", please see https://github.com/tidwall/shardmap/blob/master/LICENSE

So I think it might a typo and change it to ISC, now I changed it back


Action does not use Azure context set by azure/login step

I created a workflow that simply connects to Azure and calls Get-AzSubscription. It follows the sample in the README.md file for this action almost exactly.

When I run the workflow on the windows-latest GitHub-hosted runner (installed software), it succeeds.

When I run the workflow on a self-hosted runner with the same (relevant) software, the azure/login step succeeds:

Azure PowerShell session successfully initialized
Login successful.

...but the azure/powershell step fails with this error:
Run Connect-AzAccount to login.

Here's the entire workflow:
name: Connect to Azure
on:
  push:
    branches: master
    paths:
    - '.github/workflows/connect-to-azure.yml'
jobs:
  deploy:
    runs-on: windows-latest
    steps:
    - name: Login to Azure
      uses<EMAIL_ADDRESS>      with:
        creds: ${{secrets.AZURE_DEPLOYMENT_SERVICE_PRINCIPAL}}
        enable-AzPSSession: true

    - name: Deploy app package
      uses: azure/powershell@v1
      with:
        azPSVersion: latest
        inlineScript: Get-AzSubscription -SubscriptionId "<my-subscription-id>"

Both environments have the following software installed:

GitHub runner 2.262.1
PowerShell Core 7.0.1
Azure CLI 2.5.1
Az 3.8.0
Az.Accounts 1.7.5

What am I missing? This workflow should be trivial to get working on a self-hosted runner.
Additional info:

The self-hosted runner OS is Windows 10 Pro 18362.
I get the same error with the following software versions installed:

PowerShell Core 6.2.4
Azure CLI 2.6.0
Az 3.8.0
Az.Accounts 1.8.0

I can connect to Azure successfully on the self-hosted runner using this PS command, which is the same as what the azure/login action does:

Connect-AzAccount -ServicePrincipal -Tenant <tenant-id> -Credential <service-principal-creds> -Environment AzureCloud

Currently self-hosted runner is not supported.

Documentation is updated with supported runners for this action.
Closing this issue, please reopen if needed.


TOC links lead to .md domain instead of a sibling file

I have a doc directory, with:

blank index.mdx
some docs in build.md

mdx-go renders the default page as:

Project Documentation
TOC

<li href="//build.md"> build

I imagine that ./build.md or simply build.md was intended in the link target 🤔
Edit: actually, ./build or build is intended, because that renders markdown, while build.md shows raw file...

Ah! it turns out that was not generated by mdx-go, but rather I had a README.md that was automatically included into index.mdx (why?)


Loading external LDIF and Schema files from Microsoft AD

I am new to ldap world, so please dont mind terminology lapses if any
problem statement - we are trying to use AWS Microsoft AD in one of our projects. For performing integration tests in my micro, i was looking at some docker image for Ldap and docker-openldap was the best option, so i started playing with it.i intend to use it in a docker-compose setup.
What we have done is on AD side , extended schema to add few attributes that we need. Now i need those changes in docker image.
so i started with ldif file which had , just schema extensions we did. For e.g. Extension ldif has something like this
1 Define the capabilities attribute
dn: CN=capabilities,CN=Schema,CN=Configuration ,DC=adds-dev,DC=dev,DC=dev,DC=us
changetype: add
objectClass: top
objectClass: attributeSchema
cn: capabilities
distinguishedName:
CN=capabilities,CN=Schema,CN=Configuration ,DC=adds-dev,DC=dev,DC=dev,DC=us
attributeID: 1.2.840.113556.1.8000.2554.34082.29356.12951.18334.48550.5797021.610587.41
attributeSyntax: <IP_ADDRESS>
isSingleValued: FALSE
adminDisplayName: capabilities
adminDescription: capabilities
oMSyntax: 64
lDAPDisplayName: capabilities
name: capabilities
objectCategory:
CN=Attribute-Schema,CN=Schema,CN=Configuration ,DC=adds-dev,DC=cidev,DC=sas,DC=us
But i get an error stating , objectClass: attributeSchema is invalid , coz its not present in openldap.
so i tried to export entire schema from Microsoft AD, as a ldif and tried to load it in this image . but i get many other errors.
i used Seed ldap database with ldif, Seed from internal path options.
so in short question is is there a way and is it feasible ,to export and then import schema for Microsoft AD and use it in openldap image. I see that schema  being quite huge.
as its obvious our code depends on the additional classes and attributes, i will need them in image to run my tests.
please comment/advise if this approach is right one.

We would also like to use OpenLDAP for the same thing - loading LDIF exports from an AD instance.
It would be really helpful to have an example of how to do this.


Grabbing things too fast issues in loosing the item

When grabbing some events on the timeline (or their handles), if you're too fast with the mouse, the 'mousout' DOM event is fired because it lost focus. This drops the grabbed item on the timeline where you don't want it to go.
Absolutely no idea how to fix that... It seems to be a performance issue.

All right, I've found the solution!
I just had to replace element.bind() by $document.on() and put it inside the mouseDown event handler's function ! (cf lines 474 & 475 of plantt.js)


add option to configure externally supplied implementation for sensitive data masking

Current feature to hide sensitive data is not good enough for us.
E.g. we have interfaces containing key-value like structures and we want to hide only values of element where key value is some concrete value etc.
Hence would like to make it possible to plug in own implementation.

@reta : This is ticket i just made https://issues.apache.org/jira/browse/CXF-8831
Having option to provide own instance of MaskSensitiveHelper subclass would be also fine for me.
Perhaps it can be even refactored to interface.
Only not so nice thing might be, that method setSensitiveElementNames is invoked from AbstractLoggingInterceptor#setSensitiveElementNames and LoggingFeature and LoggingFeature.Portable.
Similar for setSensitiveProtocolHeaderNames.
In case of our implementation such method would have no use. But for backward compatibility we would need to keep them.
Do you want to do stuff yourself, or should i provide it?
If i should do it, do you prefer to keep MaskSensitiveHelper a class or should be interface refactored out of it?
thanks

@reta : This is ticket i just made https://issues.apache.org/jira/browse/CXF-8831

Thank you @JohnMTu !

Having option to provide own instance of MaskSensitiveHelper subclass would be also fine for me. Perhaps it can be even refactored to interface.

I think extracting interface would be cleaner in general

Only not so nice thing might be, that method setSensitiveElementNames is invoked from AbstractLoggingInterceptor#setSensitiveElementNames and LoggingFeature and LoggingFeature.Portable. Similar for setSensitiveProtocolHeaderNames. In case of our implementation such method would have no use. But for backward compatibility we would need to keep them.

Yes, the delegation model could be used instead (in this regards, subclassing would be simpler than interface extraction), but preserving backward compatibility is necessary.

Do you want to do stuff yourself, or should i provide it? If i should do it, do you prefer to keep MaskSensitiveHelper a class or should be interface refactored out of it?

Up to you, would be great if you finish the change since this is your idea and most of the work is done already. I am not sure you have time though (no pressure).

thanks

Thanks to you!

i didn't forget, just no time atm. But is in my list.

hello,
@reta: so far i removed "final" from maskSensitiveHelper field and added setters. Hence subclasses can be passed.
In next step i tried to extract interface. Here I realized there is some inconsistency, as configuration used for hiding data is in once case on Interceptor org.apache.cxf.ext.logging.AbstractLoggingInterceptor#sensitiveProtocolHeaderNames while in other case it's near to implementation in org.apache.cxf.ext.logging.DefaultMaskSensitiveHelper#replacementsJSON (and replacementsXML).
Best would be to cleanup it and keep it next to implementation, but unfortunately that would mean to change to some public methods, e.g.
org.apache.cxf.ext.logging.event.DefaultLogEventMapper#map(org.apache.cxf.message.Message, java.util.Set<java.lang.String>) would not need 2nd argument anymore.
And also org.apache.cxf.ext.logging.MaskSensitiveHelper#maskHeaders would not need it.
Anyway, i'm not sure, if even change MaskSensitiveHelper to from class to interface is allowed in terms of backward compatibility. Please give me some hints,
So here is my attempt:
https://github.com/JohnMTu/cxf/compare/3.5.x-fixes...JohnMTu:cxf:CXF-8831_extract_interface?expand=1
Unfortunately github doesn't show rename of MaskSensitiveHelper to DefaultMaskSensitiveHelper and instead shows diff against extracted interface .. but when checking commit by commit, rename is visible. Not sure how it would look like, if squash would be used.
Please check.
Thanks you.

Hey @JohnMTu

@reta: so far i removed "final" from maskSensitiveHelper field and added setters. Hence subclasses can be passed.

I think this is great!

Anyway, i'm not sure, if even change MaskSensitiveHelper to from class to interface is allowed in terms of backward compatibility. Please give me some hints,

That would be a breaking change sadly, if subclassing works, that would be the best option (for now)

then lets stick to subclassing.
And for rest, if you want, put come cleanup TODO for next major version or so.

So i suggest, from https://github.com/JohnMTu/cxf/compare/3.5.x-fixes...JohnMTu:cxf:CXF-8831_extract_interface?expand=1 i would take at least changes in rt/features/logging/src/main/java/org/apache/cxf/ext/logging/event/DefaultLogEventMapper.java
and in rt/features/logging/src/main/java/org/apache/cxf/ext/logging/AbstractLoggingInterceptor.java extend setSensitiveDataHelper with call to
this.eventMapper.setSensitiveDataHelper(maskSensitiveHelper);
hence also 2nd usage can be replaced with subclass.

would take at least changes in rt/features/logging/src/main/java/org/apache/cxf/ext/logging/event/DefaultLogEventMapper.java and in rt/features/logging/src/main/java/org/apache/cxf/ext/logging/AbstractLoggingInterceptor.java extend setSensitiveDataHelper with call to
this.eventMapper.setSensitiveDataHelper(maskSensitiveHelper);

Sure, would you like to make this changes in scope of this pull request or open another one?

i can do it here, but only in 2 weeks. What is better for you?

i can do it here, but only in 2 weeks. What is better for you?

Let me merge this one and you will be able to work on the next improvements at you own pace, thank you


Feat: Add new table colors

Motivation
Use CSS variables for the colors of the new table in the Tokens page.
In this PR, add variables in the dark and light themes.
Changes

Add four new CSS variables for colors in light and dark themes.

Screenshots
No changes.

@dskloetd as agreed with Artem, I added the new colors to gix-components.

@dskloetd ready for another review


Unused value warning is not being displayed

The line hmacsha.Key = helloBytes is not showing a warning of unused boolean value. See below

In the case of VisualStudio this is displayed:

Can't reproduce anymore, let's assume it got fixed accidentally with some other fixes.


Possible to have tags and categories for collections

In gh-1256 which is a couple of years old, I asked whether it is possible to use tags for collections. Do you know whether that has been implemented, as I would like to use it with a new site based in your awesome theme - https://github.com/lsolesen/legestue-net-jekyll

To my knowledge it has not been added yet. Check out jekyll/jekyll's repo. I believe it was being discussed as a feature for 4.0 to harmonize how categories and tags work across collections... not just on posts.


Import errors with ollama-0.4.0

Hi thank you for all your work on the great project.
New install using pip in a venv installs ollama-0.4.0 by default which gives the below errors.  Downgrading to ollama-0.3.3 resolves the problem.
Traceback (most recent call last):
File "/home/user/oterm_venv/bin/oterm", line 5, in
from oterm.cli.oterm import cli
File "/home/user/oterm_venv/lib/python3.11/site-packages/oterm/cli/oterm.py", line 7, in
from oterm.app.oterm import app
File "/home/user/oterm_venv/lib/python3.11/site-packages/oterm/app/oterm.py", line 10, in
from oterm.app.chat_edit import ChatEdit
File "/home/user/oterm_venv/lib/python3.11/site-packages/oterm/app/chat_edit.py", line 17, in
from oterm.ollamaclient import OllamaLLM, parse_ollama_parameters
File "/home/user/oterm_venv/lib/python3.11/site-packages/oterm/ollamaclient.py", line 16, in
from oterm.tools import ToolDefinition
File "/home/user/oterm_venv/lib/python3.11/site-packages/oterm/tools/init.py", line 3, in
from ollama._types import (
ImportError: cannot import name 'Parameters' from 'ollama._types' (/home/user/oterm_venv/lib/python3.11/site-packages/ollama/_types.py)

Hey @walcode
Thanks for the heads up, seems like ollama-python changed the definition of tool-related classes.
I will adapt and release asap.
In the meantime, downgrading to 0.3.3 is indeed the workaround.

I released for the meantime 0.6.9 pinning ollama to <0.4 as there are a number of breaking changes.
Will keep this open till I release an update for 0.4.


DBC22-2605: disabled state for favorite cams on saved route

Converted to draft as the cam details card is too cramped with the new button updates.


How to save the value of an input field for a specific node

Hello,
I used an input field for the title so that user can change the title if required. How to save the value of the input to that specific node? I used onChange for the input but couldn't find a possible way to save the value to the node.
And when input is saved I want to disappear the input text box so that the node appears like a normal node in a react sortable tree. How to achieve this?

You can find an example implementation of that in the storybook example called Modify nodes:
https://fritz-c.github.io/react-sortable-tree/storybook/?selectedKind=Basics&selectedStory=Modify nodes&full=0&down=1&left=1&panelRight=0&downPanel=storybook%2Fnotes%2Fpanel

Thank you fritz-c. But this didn't work for my case. I have an add button to add children.(See attachment) I need to save the user entered value and I have added it as the onChange in the add button.

Following is my code snippet of onChange event.
handleChange(event) {
    this.setState({
        title: event.target.input_value,
        treeData: changeNodeAtPath({
            treeData: state.treeData,
            path,
            getNodeKey,
            newNode: { node, title },
        }),
    })
}

Following is my code snippet of sortable tree implementation.
                        <SortableTree
                            treeData={this.state.treeData}
                            onChange={treeData => this.setState({ treeData })}
                             generateNodeProps={({ node, path }) => ({

                                buttons: [
                                    <button className="btn" id=
                                        {path.length == 1 ? (
                                            "btn_add_parent"
                                        ) : (
                                            "btn_add_children"
                                        )}
                                            onClick={() =>
                                                this.setState(state => ({
                                                    treeData: addNodeUnderParent({
                                                        treeData: state.treeData,
                                                        parentKey: path[1 - 1], //parentKey: path[path.length - 1]..path.length=1 here
                                                        expandParent: false,
                                                        getNodeKey,
                                                       newNode:
                                                            {
                                                                title: (
                                                                    <input type="text" value={this.state.input_value} input_value={node.title} onChange={this.handleChange} />

                                                                )
                                                            },

                                                    }).treeData,
                                                }))}
                                    >

                                    </button>,
                                ],
                            })}
                        />

Any idea on how to resolve this?

Thank you fritz-c. But this didn't work for my case. I have an add button to add children.(See attachment) I need to save the user entered value and I have added it as the onChange in the add button.

Following is my code snippet of onChange event.
handleChange(event) {
this.setState({
title: event.target.input_value,
treeData: changeNodeAtPath({
treeData: state.treeData,
path,
getNodeKey,
newNode: { node, title },
}),
})
}
Following is my code snippet of sortable tree implementation.
<SortableTree
treeData={this.state.treeData}
onChange={treeData => this.setState({ treeData })}
generateNodeProps={({ node, path }) => ({
                                buttons: [
                                    <button className="btn" id=
                                        {path.length == 1 ? (
                                            "btn_add_parent"
                                        ) : (
                                            "btn_add_children"
                                        )}
                                            onClick={() =>
                                                this.setState(state => ({
                                                    treeData: addNodeUnderParent({
                                                        treeData: state.treeData,
                                                        parentKey: path[1 - 1], //parentKey: path[path.length - 1].. path.lenth=1 here
                                                        expandParent: false,
                                                        getNodeKey,
                                                        newNode:
                                                            {
                                                                title: (
                                                                    <input type="text" value={this.state.input_value} input_value={node.title} onChange={this.handleChange} />
                                                                )
                                                            },
                                                    }).treeData,
                                                }))}
                                    >

                                    </button>,
                                ],
                            })}
                       />

Thank you fritz-c. But this didn't work for my case. I have an add button to add children.(See attachment) I need to save the user entered value and I have added it as the onChange in the add button.

Following is my code snippet.
class test extends React.Component {
constructor(props) {
super(props);
this.state = {
treeData: [{title: 'Parent1', children: [{title: 'Child1'}, {title: 'Child2'}]},
{title: 'Parent2', children: [{title: 'Child1'}, {title: 'Child2'}]}],
input_value:"user_input"
}
}
handleChange(event) {
    this.setState({
        title: event.target.input_value,
        treeData: changeNodeAtPath({
            treeData: state.treeData,
            path,
            getNodeKey,
            newNode: { node, title },
        }),
    })
}

render() {
const getNodeKey = ({ treeIndex }) => treeIndex;
return (

 this.setState({ treeData })}
                                dndType={externalNodeType}
                                shouldCopyOnOutsideDrop={shouldCopyOnOutsideDrop}
                                generateNodeProps={({ node, path }) => ({
                                    buttons: [

                                                    this.setState(state => ({
                                                        treeData: addNodeUnderParent({
                                                            treeData: state.treeData,
                                                            parentKey: path[1 - 1], //parentKey: path[path.length - 1].. path.lenth=1 here
                                                            expandParent: false,
                                                            getNodeKey,
                                                            newNode:
                                                                {
                                                                    title: (

                                                                    )
                                                                },
                                                        }).treeData,
                                                    }))}
                                        >

,
                                    ],
                                })}
                            />

Any idea how to resolve this?

Thank you fritz-c. But this didn't work for my case. I have an add button to add children.(See attachment) I need to save the user entered value and I have added it as the onChange in the add button.

Following is my code snippet.
class test extends React.Component {
constructor(props) {
    super(props);
    this.state = {

        treeData: [{title: 'Parent1', children: [{title: 'Child1'}, {title: 'Child2'}]},
            {title: 'Parent2', children: [{title: 'Child1'}, {title: 'Child2'}]}],

        input_value:"user_input"
    }
}

handleChange(event) {
    this.setState({
        title: event.target.input_value,
        treeData: changeNodeAtPath({
            treeData: state.treeData,
            path,
            getNodeKey,
            newNode: { node, title },
        }),
    })
}

render() {

    const getNodeKey = ({ treeIndex }) => treeIndex;

    return (

                        <SortableTree
                            treeData={this.state.treeData}
                            onChange={treeData => this.setState({ treeData })}
                            generateNodeProps={({ node, path }) => ({

                                buttons: [
                                    <button className="btn" id=
                                        {path.length == 1 ? (
                                            "btn_add_parent"
                                        ) : (
                                            "btn_add_children"
                                        )}
                                            onClick={() =>
                                                this.setState(state => ({
                                                    treeData: addNodeUnderParent({
                                                        treeData: state.treeData,
                                                        parentKey: path[1 - 1], //parentKey: path[path.length - 1].. path.lenth=1 here
                                                        expandParent: false,
                                                        getNodeKey,
                                                        newNode:
                                                            {
                                                                title: (
                                                                    <input type="text" value={this.state.input_value} input_value={node.title} onChange={this.handleChange} />
                                                                )
                                                            },
                                                    }).treeData,
                                                }))}
                                    >

                                    </button>,
                                ],
                            })}
                        />

Any idea on how to resolve this?

class test extends React.Component {
    constructor(props) {
        super(props);

        this.state = {
            treeData: [
                {
                    title: 'Parent1',
                    children: [{ title: 'Child1' }, { title: 'Child2' }],
                },
                {
                    title: 'Parent2',
                    children: [{ title: 'Child1' }, { title: 'Child2' }],
                },
            ],
        };
    }

    render() {
        const getNodeKey = ({ treeIndex }) => treeIndex;

        return (

                <SortableTree
                    treeData={this.state.treeData}
                    onChange={treeData => this.setState({ treeData })}
                    generateNodeProps={({ node, path }) => ({
                        title: !node.needsTitle ? (
                            node.title
                        ) : (
                            <form
                                onSubmit={event => {
                                    event.preventDefault();
                                    const { needsTitle, ...nodeWithoutNeedsTitle } = node;
                                    this.setState(state => ({
                                        treeData: changeNodeAtPath({
                                            treeData: state.treeData,
                                            path,
                                            getNodeKey,
                                            newNode: nodeWithoutNeedsTitle,
                                        }),
                                    }));
                                }}
                            >
                                <input
                                    autoFocus
                                    value={node.title}
                                    onChange={event => {
                                        const title = event.target.value;

                                        this.setState(state => ({
                                            treeData: changeNodeAtPath({
                                                treeData: state.treeData,
                                                path,
                                                getNodeKey,
                                                newNode: { ...node, title },
                                            }),
                                        }));
                                    }}
                                />
                            </form>
                        ),
                        buttons: [
                            <button
                                className="btn"
                                id={path.length === 1 ? 'btn_add_parent' : 'btn_add_children'}
                                onClick={() =>
                                    this.setState(state => ({
                                        treeData: addNodeUnderParent({
                                            treeData: state.treeData,
                                            parentKey: path[path.length - 1],
                                            expandParent: false,
                                            getNodeKey,
                                            newNode: {
                                                title: '',
                                                needsTitle: true,
                                            },
                                        }).treeData,
                                    }))}
                            >

                            </button>,
                        ],
                    })}
                />

        );
    }
}

Thank you. This is exactly what I was looking for. But in this, only one character can be entered in the input field. How to modify it?

@fritz-c the code works brilliantly, but there's one problem - for some reason autoFocus isn't working. The newly added input field isn't being focused for some reason on Chrome (neither it's focused on Safari). I am not sure what's the problem, but it would be really good if there was a simple solution.
One way to do this is to add refs, but I think it'll complicate things way too much. Any other thoughts?

@ChathurangiShyalika how did you resolve the input disappearing?

@NickEmpetvee you need to add the utils file somewhere in your project and add this to imports:
import { addNodeUnderParent, changeNodeAtPath } from '../<wherever>/utils/tree-data-utils';

@fritz-c https://fritz-c.github.io/react-sortable-tree/storybook/?selectedKind=Basics&selectedStory=Modify nodes&full=0&down=1&left=1&panelRight=0&downPanel=storybook%2Fnotes%2Fpanel  link is broken can you please provide the correct one


Bump @types/node to 20.17.6

Summary
This bumps @types/node to 20.17.6.
@types/node was recently targeting node 16, which Dashboard no longer supports as of the Vue 3 migration.

Occurred changes and/or fixed issues

bump @types/node to 20.17.6

Technical notes summary

Dashboard no longer supports node 16 after migrating to Vue 3

Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

@rak-phillip the key here is the check-plugins-build step... It failed in a simpler usecase of a newly generated extension: https://github.com/rancher/dashboard/actions/runs/11846587182/job/33014521563?pr=12616#step:5:2370
All extensions migrated to vue3 should have this resolution for @types/node:
"@types/node": "~20.10.0"

@rak-phillip the key here is the check-plugins-build step for all these PRs for dependencies updates... It failed in a simpler usecase of a newly generated extension: https://github.com/rancher/dashboard/actions/runs/11846587182/job/33014521563?pr=12616#step:5:2370
All extensions migrated to vue3 have this resolution for @types/node:
"@types/node": "~20.10.0"

@aalves08  Then it's settled, 2.10.8 is the version that we want to target. Although, I do question why we need to set the resolution for @types/node, my expectation is that we should be able to remove the resolution now that we target types that match our actual node version.

@rak-phillip the key here is the check-plugins-build step for all these PRs for dependencies updates... It failed in a simpler usecase of a newly generated extension: https://github.com/rancher/dashboard/actions/runs/11846587182/job/33014521563?pr=12616#step:5:2370
All extensions migrated to vue3 have this resolution for @types/node:
"@types/node": "~20.10.0"

@aalves08 Then it's settled, 2.10.8 is the version that we want to target. Although, I do question why we need to set the resolution for @types/node, my expectation is that we should be able to remove the resolution now that we target types that match our actual node version.

Hopefully we can, mate! 🤞 🤞 🤞  no it's just a matter of testing it with extensions

I've just generated a new extension via yarn create @rancher/extension my-app and the output was "hideous" in terms of dependencies....
{
  "name": "my-app",
  "version": "0.1.0",
  "private": false,
  "engines": {
    "node": ">=20"
  },
  "dependencies": {
    "cache-loader": "^4.1.0",
    "color": "4.2.3",
    "ip": "2.0.1",
    "node-polyfill-webpack-plugin": "^3.0.0",
    "@rancher/shell": "^3.0.0"
  },
  "resolutions": {
    "@types/node": "~20.10.0",
    "d3-color": "3.1.0",
    "ejs": "3.1.9",
    "follow-redirects": "1.15.2",
    "glob": "7.2.3",
    "glob-parent": "6.0.2",
    "json5": "2.2.3",
    "@types/lodash": "4.17.5",
    "merge": "2.1.1",
    "node-forge": "1.3.1",
    "nth-check": "2.1.1",
    "qs": "6.11.1",
    "roarr": "7.0.4",
    "semver": "7.5.4",
    "@vue/cli-service/html-webpack-plugin": "^5.0.0"
  },
  "scripts": {
    "dev": "NODE_ENV=dev ./node_modules/.bin/vue-cli-service serve",
    "build": "./node_modules/.bin/vue-cli-service build",
    "clean": "./node_modules/@rancher/shell/scripts/clean",
    "build-pkg"<EMAIL_ADDRESS>    "serve-pkgs": "./node_modules/@rancher/shell/scripts/serve-pkgs",
    "publish-pkgs": "./node_modules/@rancher/shell/scripts/extension/publish",
    "parse-tag-name": "./node_modules/@rancher/shell/scripts/extension/parse-tag-name"
  }
}

We need to clean this up and consolidate it... This hasn't been touched in a bit (I forgot to update them 💦  when I reviewed some dependencies).
In theory it should only be:
{
  "name": "my-app",
  "version": "0.1.0",
  "private": false,
  "engines": {
    "node": ">=20"
  },
  "dependencies": {
    "@rancher/shell": "^3.0.0"
  },
  "scripts": {
    "dev": "NODE_ENV=dev ./node_modules/.bin/vue-cli-service serve",
    "build": "./node_modules/.bin/vue-cli-service build",
    "clean": "./node_modules/@rancher/shell/scripts/clean",
    "build-pkg"<EMAIL_ADDRESS>    "serve-pkgs": "./node_modules/@rancher/shell/scripts/serve-pkgs",
    "publish-pkgs": "./node_modules/@rancher/shell/scripts/extension/publish",
    "parse-tag-name": "./node_modules/@rancher/shell/scripts/extension/parse-tag-name"
  }
}

I've yarn linked your branch to a newly generated extension with just the shell dependency:
{
  "name": "my-app",
  "version": "0.1.0",
  "private": false,
  "engines": {
    "node": ">=20"
  },
  "dependencies": {
    "@rancher/shell": "^3.0.0"
  },
  "scripts": {
    "dev": "NODE_ENV=dev ./node_modules/.bin/vue-cli-service serve",
    "build": "./node_modules/.bin/vue-cli-service build",
    "clean": "./node_modules/@rancher/shell/scripts/clean",
    "build-pkg"<EMAIL_ADDRESS>    "serve-pkgs": "./node_modules/@rancher/shell/scripts/serve-pkgs",
    "publish-pkgs": "./node_modules/@rancher/shell/scripts/extension/publish",
    "parse-tag-name": "./node_modules/@rancher/shell/scripts/extension/parse-tag-name"
  }
}

And the build failed 🤔

Moving to draft until I'm able to repro and identify issues with a newly generated extensions, as described above

Sorry for taking a long time to reply but me and @jordojordo have been fine tuning dependencies and all. I'll revisit this in a few days once we are more stable. I'll keep it in my todo list. Thanks @rak-phillip

This PR seems to generate a successful build on Elemental, however we still can't remove the resolution for @types/node IF we remove the current yarn.lock since there must be a library that has conflicting @types/node version

@jordojordo any thoughts? This issue, for me, had the additional challenge of possibly removing the resolution from extensions, but I would say that otherwise, LGTM 🤔

If we are to keep this with a more simpler approach (not removing yarn.lock) then the check-plugins-build step may just be the QA we need to move these issues forward, imo. We are currently testing 6 different official extensions there (I don't know if you would need to rebase this PR to get them all because it a rather recent change having all of them enabled and green at the same time)


Ingress gateway proxies missing from istioctl proxy-status

Bug Description
We have a bug in our development cluster that I have been trying to resolve.
The problem happens occasionally, like every few hours, where we will find access logs in ingress gateway with the code 503 UF URX coming from a particular ingress gateway container, with external client like a browser to see message upstream disconnection error. When this happens, an ingress gateway proxy is either missing (like below) or STALE according to istioctl proxy-status. It seems to me that basically ingress gateway pod has become disconnected with IstioD and is not reconnecting for some reason, and I have not had success to figure out why. I am working around this problem by deleting the missing ingress gateway pod.
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % istioctl proxy-status | grep -i stale
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % istioctl proxy-status | grep public
istio-public-ingressgateway-6bf56c555c-2jzcp.istio-system                  Kubernetes     SYNCED     SYNCED     SYNCED     SYNCED     istiod-6b4b545db9-t2m8w     1.13.3
istio-public-ingressgateway-6bf56c555c-md45k.istio-system                  Kubernetes     SYNCED     SYNCED     SYNCED     SYNCED     istiod-6b4b545db9-wf6nw     1.13.3
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % k get pods -n istio-system
NAME                                           READY   STATUS    RESTARTS   AGE
istio-public-ingressgateway-6bf56c555c-2jzcp   1/1     Running   0          109m
istio-public-ingressgateway-6bf56c555c-md45k   1/1     Running   0          109m
istio-public-ingressgateway-6bf56c555c-p4459   1/1     Running   0          109m
istiod-6b4b545db9-d5b2s                        1/1     Running   0          109m
istiod-6b4b545db9-t2m8w                        1/1     Running   0          53m
istiod-6b4b545db9-wf6nw                        1/1     Running   0          109m

In this development cluster, we are frequently updating. We are deploying for each developer's branch a new namespace that includes a new VirtualService, AuthorizationPolicy, and the rest of the resources to deploy this version of our application. The VirtualService is associated with a shared Gateway resource. In terms of scale, I think it should not be too much, since we only have 30-100 namespaces at any given time, with each being updated every few minutes. This amounts to hundreds of pods, but not all being updated very rapidly - perhaps each one updates every few minutes. We have the default Sidecar configuration in place to prevent excessive cross-namespace updates, but I think this does not prevent the ingress gateway pods from being updated a lot. The scale you can also see from the data plane version information in the next section by looking at the total proxy count.
If anyone has some tips on how to troubleshoot such an issue, I would really appreciate your help.
Version
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % istioctl version
client version: 1.13.2
control plane version: 1.13.3
data plane version: 1.13.3 (205 proxies)

stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % kubectl version --short
Client Version: v1.22.5
Server Version: v1.20.15-eks-a64ea69
WARNING: version difference between client (1.22) and server (1.20) exceeds the supported minor version skew of +/-1

Additional Information
So far, I am tracking metrics pilot_proxy_convergence_time, pilot_proxy_queue_time, pilot_xds_push_time. We see very large push times in spikes on these metrics. I have not found any error metrics pilot_xds_*, these metrics are missing, and someone mentioned if they are missing that is because there aren't any errors.
I tried several batching configurations, following along with the Istio In Action book, trying these in my IstioOperator.
Output of  k get -o yaml istiooperator -n istio-system istio-default
this configuration includes batching configurations I have tried to resolve this issue with (did not work), and also special configuration to coordinate the lifecycle of the istio ingressgateway pods with the AWS NLB in ip mode (seems to work).
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: | (omitted)
    kustomize.toolkit.fluxcd.io/checksum: dc8d90111fe1d6f457379fa2050650b6d0adc655
  creationTimestamp: "2022-06-08T15:44:01Z"
  finalizers:
  - istio-finalizer.install.istio.io
  generation: 9
  labels:
    kustomize.toolkit.fluxcd.io/name: istio-system
    kustomize.toolkit.fluxcd.io/namespace: flux-system
  name: istio-default
  namespace: istio-system
  resourceVersion: "275910394"
  uid: e9dfac3e-cfe9-4606-8604-c048c5514dd2
spec:
  components:
    ingressGateways:
    - enabled: true
      k8s:
        env:
        - name: DD_ENV
          value: development
        - name: DD_SERVICE
          value: istio-public-ingressgateway
        - name: DD_VERSION
          value: v1
        - name: DD_APM_ENABLED
          value: "true"
        hpaSpec:
          maxReplicas: 15
          minReplicas: 3
        nodeSelector:
          spotinst.io/node-lifecycle: od
        overlays:
        - kind: Deployment
          name: istio-public-ingressgateway
          patches:
          - path: spec.template.spec.containers[name:istio-proxy].lifecycle.preStop.exec.command
            value:
            - /bin/sh
            - -c
            - sleep 180
          - path: spec.template.spec.terminationGracePeriodSeconds
            value: 200
          - path: spec.template.metadata.labels.spotinst\.io/restrict-scale-down
            value: "true"
        podAnnotations:
          ad.datadoghq.com/tags: '{"source": "envoy", "service": "istio-public-ingressgateway"}'
          apm.datadoghq.com/env: '{ "DD_SERVICE": "istio-public-ingressgateway" }'
        podDisruptionBudget:
          maxUnavailable: 20%
        serviceAnnotations:
          external-dns.alpha.kubernetes.io/hostname:*****omitted******.com
          service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
          service.beta.kubernetes.io/aws-load-balancer-healthcheck-healthy-threshold: "2"
          service.beta.kubernetes.io/aws-load-balancer-healthcheck-unhealthy-threshold: "2"
          service.beta.kubernetes.io/aws-load-balancer-internal: "false"
          service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
          service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
          service.beta.kubernetes.io/aws-load-balancer-target-group-attributes: deregistration_delay.timeout_seconds=200,deregistration_delay.connection_termination.enabled=true,preserve_client_ip.enabled=false
          service.beta.kubernetes.io/aws-load-balancer-type: external
        strategy:
          rollingUpdate:
            maxSurge: 100%
            maxUnavailable: 0
      name: istio-public-ingressgateway
    - enabled: false
      name: istio-ingressgateway
    pilot:
      k8s:
        env:
        - name: PILOT_ENVOY_FILTER_STATS
          value: "true"
        - name: PILOT_XDS_CACHE_STATS
          value: "true"
        - name: PILOT_PUSH_THROTTLE
          value: "500"
        - name: PILOT_ENABLE_EDS_DEBOUNCE
          value: "true"
        - name: PILOT_DEBOUNCE_AFTER
          value: 2500ms
        - name: PILOT_DEBOUNCE_MAX
          value: 30s
        hpaSpec:
          maxReplicas: 10
          minReplicas: 3
        resources:
          limits:
            cpu: 2000m
            memory: 2Gi
          requests:
            cpu: 500m
            memory: 2Gi
        serviceAnnotations:
          ad.datadoghq.com/endpoints.check_names: '["istio"]'
          ad.datadoghq.com/endpoints.init_configs: '[{}]'
          ad.datadoghq.com/endpoints.instances: |
            [
              {
                "istiod_endpoint": "http://%%host%%:15014/metrics",
                "use_openmetrics": true
              }
            ]
  hub: gcr.io/istio-release
  meshConfig:
    accessLogFile: /dev/stdout
    defaultConfig:
      terminationDrainDuration: 10s
      tracing:
        datadog:
          address: $(HOST_IP):8126
        sampling: 100
    enableTracing: true
    extensionProviders:
    - envoyExtAuthzHttp:
        headersToDownstreamOnDeny:
        - uid
        - client
        - access-token
        headersToUpstreamOnAllow:
        - uid
        - client
        - access-token
        includeHeadersInCheck:
        - uid
        - client
        - access-token
        pathPrefix: /api/v1/auth/istio
        port: "80"
        service: auth-service.apps.svc.cluster.local
      name: auth-service
    rootNamespace: istio-config
    tcpKeepalive:
      interval: 30s
      time: 60s
  profile: default
  values:
    global:
      proxy:
        tracer: datadog
    pilot:
      traceSampling: 100
status:
  componentStatus:
    Base:
      status: HEALTHY
    IngressGateways:
      status: HEALTHY
    Pilot:
      status: HEALTHY
  status: HEALTHY

Sidecar configuration:
apiVersion: networking.istio.io/v1beta1
kind: Sidecar
metadata:
  name: default-sidecar-config
  namespace: istio-config
spec:
  egress:
  - hosts:
    - "./*"
    - "istio-system/*"

Gateway:
output of k get gateway -o yaml istio-public-gateway -n istio-system
apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: | omitted
    kustomize.toolkit.fluxcd.io/checksum: efa92508cf871f00fa32f852bc817d640c0def5e
  creationTimestamp: "2022-06-06T14:14:47Z"
  generation: 1
  labels:
    kustomize.toolkit.fluxcd.io/name: infrastructure
    kustomize.toolkit.fluxcd.io/namespace: flux-system
    velero.io/backup-name: velero-hour-20220606000052
    velero.io/restore-name: velero-hour-20220606000052-20220606101017
  name: istio-public-gateway
  namespace: istio-system
  resourceVersion: "270552973"
  uid: be62f7e5-73cf-48ca-8bc5-ad5de16f4971
spec:
  selector:
    istio: ingressgateway
  servers:
  - hosts:
    - '*.omitted.com'
    port:
      name: http
      number: 80
      protocol: HTTP
    tls:
      httpsRedirect: true
  - hosts:
    - '*.omitted.com'
    port:
      name: https
      number: 443
      protocol: HTTPS
    tls:
      credentialName: platform-certificate-private-key
      minProtocolVersion: TLSV1_2
      mode: SIMPLE

Sample Virtual Service
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  annotations:
    meta.helm.sh/release-name: master-server
    meta.helm.sh/release-namespace: master
  creationTimestamp: "2022-06-06T14:23:05Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
    helm.toolkit.fluxcd.io/name: server
    helm.toolkit.fluxcd.io/namespace: master
  name: master-server
  namespace: master
  resourceVersion: "255878137"
  uid: 06d15a4e-6465-4515-a602-679bab7ce700
spec:
  gateways:
  - istio-system/istio-public-gateway
  hosts:
  - api-master.omitted.com
  http:
  - route:
    - destination:
        host: master-server.master.svc.cluster.local

Sample auth policy
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  annotations:
    meta.helm.sh/release-name: master-server
    meta.helm.sh/release-namespace: master
  creationTimestamp: "2022-06-06T14:23:05Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
    helm.toolkit.fluxcd.io/name: server
    helm.toolkit.fluxcd.io/namespace: master
  name: master-server
  namespace: master
  resourceVersion: "255878124"
  uid: 0bd73c55-56fa-4c0b-a6d7-c6ce8bad4bc9
spec:
  rules:
  - to:
    - operation:
        paths:
        - '*'
  selector:
    matchLabels:
      app.kubernetes.io/instance: master-server
      app.kubernetes.io/name: server
      component: api

Also, I am tracking the resources of istio control plane and the ingress gateway proxies, but they do not seem heavily utilized.
It seems to me likely there is some limited resource we are hitting in the ingress gateway pods that I have not yet figured out how to measure. For example like total connections (to all the data plane pods), sockets, or something like that. Another option is that for some misconfiguration in the surrounding network, but I haven't thought of what to check. The total network utilization on the Nodes seems fine, well within limits.

I am further investigating this problem. I believe I have a situation where:

Istio thinks a gateway proxy is stale
Gateway proxy is still TCP connected to istio discovery
Low resource utilization on both gateway proxy and istiod.

It seems to me there may be some bug, but I'm not sure.
I created a load on istio by performing a rolling restart of all the data plane deployments. After this, we have the problem triggered again.
Resource utilization:

XDS metrics and errors in the ingress gateway:

still TCP connected to discovery:

IP addresses from above packet capture:
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % k get pods -o wide -n istio-system
k get NAME                                           READY   STATUS    RESTARTS   AGE     IP             NODE                           NOMINATED NODE   READINESS GATES
istio-public-ingressgateway-7bbc49799c-2jj9g   1/1     Running   0          3h      <IP_ADDRESS>   ip-10-3-211-80.ec2.internal    <none>           3/3
istio-public-ingressgateway-7bbc49799c-hsqh6   1/1     Running   0          3h      <IP_ADDRESS>   ip-10-3-211-80.ec2.internal    <none>           3/3
istio-public-ingressgateway-7bbc49799c-pcvtj   1/1     Running   0          3h      <IP_ADDRESS>   ip-10-3-132-27.ec2.internal    <none>           3/3
istiod-5f89bc4466-6t5w9                        1/1     Running   0          97m     <IP_ADDRESS>   ip-10-3-167-141.ec2.internal   <none>           <none>
istiod-5f89bc4466-742np                        1/1     Running   0          97m     <IP_ADDRESS>    ip-10-3-126-114.ec2.internal   <none>           <none>
istiod-5f89bc4466-h4rm6                        1/1     Running   0          17m     <IP_ADDRESS>   ip-10-3-199-219.ec2.internal   <none>           <none>
ksniff-bc7sm                                   1/1     Running   0          3m33s   <IP_ADDRESS>    ip-10-3-211-80.ec2.internal    <none>           <none>
ksniff-pf52m                                   1/1     Running   0          56m     <IP_ADDRESS>    ip-10-3-132-27.ec2.internal    <none>           <none>
stevencerebral@Stevens-MacBook-Pro kubernetes-cerebral-platform % k get svc -n istio-system
NAME                          TYPE           CLUSTER-IP       EXTERNAL-IP                                                                     PORT(S)                                      AGE
istio-public-ingressgateway   LoadBalancer   <IP_ADDRESS>    **** omitted   22d
istiod                        ClusterIP      <IP_ADDRESS>   <none>

It recovered on its own after about 20 minutes. And there is a strange XDS metrics with a massive latency number reported.

I now thing something like:

a bunch of updates coming to gateway
one of these updates is not working for some reason, related service can't be connected to by the gateway
eventual retry?

I wanted to get the envoy and istio diff like this, but I didn't catch it this time.

I found this log from the config logger in the STALE ingress gateway pod. Not sure yet, but seems related.
2022-07-01T18:58:58.406051Z	debug	envoy config	StreamAggregatedResources gRPC config stream closed: 14, closing transport due to: connection error: desc = "error reading from server: EOF", received prior goaway: code: NO_ERROR

According to google search, this is an expected connection reset. When I did the packet capture, the TCP stream did not close. I will have to monitor both this log and the packet capture at the same time.

This log is also showing up in the healthy pods. Not sure this is the right thing to be looking at right now.

We upgrade to 1.14.1, and now convergence metrics look a lot different, and the problem has not recurred yet, but it hasn't been that long yet on this new version.

Still the problem has not recurred. In the change notes, there is one thing that sounds kind of related, but I don't know if it's really it or not.

Improved XDS generation to send less resource when possible, sometimes omitting a response entirely. This can be disabled by the PILOT_PARTIAL_FULL_PUSHES=false environment variable. (Issue #37989),(Issue #37974)

https://istio.io/latest/news/releases/1.14.x/announcing-1.14/change-notes/


Trajectory mission slow final waypoint approach

Describe the bug
When using the Jerk-limited trajectory (default, MPC_AUTO_MODE 1) the final approach to a waypoint for example but not limited to the return altitude in RTL is significantly slower than with the previous implementation. Don't get me wrong, I would not prefer the old implementation but I think it's something we need to fix with medium priority.
To Reproduce
It's also visible in SITL:

Fly e.g. 10m away from home
Trigger RTL while you're clearly lower than the return altitude
Pay attention to the vehicle reaching the return altitude
It it's a very continuous motion but it almost looks like it's breaking too early and then takes quite long to fly into the acceptance radius and continue. The same can be observed in other missions.

Expected behavior
It's clear that a jerky corner takes less time and we don't have an optimized trajectory around corners yet but it would be nice if the vehicle could break down what intuitively looks more spot on to the waypoint. Maybe that's just tuning.
Log Files and Screenshots
Should I create a comparison for approaching times?
Drone:

First seen in SITL and default parameters
Now tested in real world on a small racing platform

Additional context
Original trajectory based mission pr: https://github.com/PX4/Firmware/pull/10746

@MaEtUgR Yes, the default gains of the "virtual pilot" (MPC_XY_TRAJ_P and MPC_Z_TRAJ_P) are 0.3 and really conservative to ensure stability on a wide range of velocities, accelerations and jerks parameters.
To decrease the time is takes to reach a waypoint, simply increase those gains.

Then we should adjust the default or find a different solution. If SITL on master already shows that behavior I still consider it an issue.

#11841 Could be a viable solution.


Fix Undo Behavior

Fixes https://github.com/nix-gui/nix-gui/issues/46
Fixes bug where old form value was retained even after undo
"Progress" in undos - if you continue editing the same option, that is considered one undoable action
Add "undefined" field

I think https://github.com/nix-gui/nix-gui/pull/60/files#diff-563739db64db2a1984fb0c6a970dce4b767ee64078ed65bfaf5257e3139b945eR365
should be self.validate_field(value)
but otherwise LGTM and should be merged.


"Fun" section assets loading slowly

When switching between options on the "Fun" section, the photos take an extra second or so to change but the text has already changed.
https://github.com/byronwang93/byronwang.com/assets/55601970/a2821e65-5804-4fdf-a544-a7ab1f7e254c
This is completely unacceptable.

thanks for bringing this up, will be addressed as soon as finals season is over! 🤝


Vertex colouring

Hi! Firstly, great package you have here. The control/scene system is really good and solves a lot of problems I've been having with other packages.
So I was just wondering if you had any plans to implement vertex colouring for obj files? (Or if it's already there and I haven't found it?)
If you aren't aware, there is a flavour of obj that allows for vertex definitions like:
v 1220.094482 -572.500000 177.713943 0.984314 0.764706 1.000000
where the last three parameters are RGB.
It's not part of the official specification, but there are some applications (in my case, a Unity exporter plugin) that export in this format.

@alexobviously Thank you, I'm happy you liked the package.
I'd love to add this feature, but sadly I don't know how to. I got the core of this code from a Flutter demonstration from @gskinner and adapted it into a library format, adding the controllers, etc. This means that I don't actually have any experience with parsing obj files, so I wouldn't know how to implement this. But if you'd like to give it a try, I'd be happy to help! You just gotta see if Flutter also supports rendering vertices with colors in the canvas (although I think it does).

@alexobviously there currently isn't any support for that flavor of specifying colors in the object file. However there is support for multiple materials which can be used to color sets of vertices independently.

@alexobviously Thank you, I'm happy you liked the package.
I'd love to add this feature, but sadly I don't know how to. I got the core of this code from a Flutter demonstration from @gskinner and adapted it into a library format, adding the controllers, etc. This means that I don't actually have any experience with parsing obj files, so I wouldn't know how to implement this. But if you'd like to give it a try, I'd be happy to help! You just gotta see if Flutter also supports rendering vertices with colors in the canvas (although I think it does).

Hey, thanks for replying so quickly and sorry it took me a while to get back to you, I was working on another project. I've had a look at the parsing code for vertex and I'm sure I can easily add the ability to parse vertex colours without affecting the normal behaviour at all.
For rendering, I'm not 100% sure that it will be trivial, but I see that the Vertices class in flutter has this definition:
Vertices(
    VertexMode mode,
    List<Offset> positions, {
    List<Offset>? textureCoordinates,
    List<Color>? colors,
    List<int>? indices,
  })

so I'm fairly sure it'll be possible.

@alexobviously there currently isn't any support for that flavor of specifying colors in the object file. However there is support for multiple materials which can be used to color sets of vertices independently.

Yeah, in the official .obj definition it doesn't exist, and I'd maybe even also say it's not a very good way to do it, but it is relatively common (there is even support by default in OSX quicklook). In my case, I'm working with a long and complicated tool chain starting with 3D cameras that generate these vertices with colour in that way by default.

@alexobviously it should be pretty easy to implement the parsing as you mentioned as long as I can keep compatibility with the spec unambiguously. I have some time this week, I'll try to submit a PR if that's okay with you @nythrox.

I've tried to implement this here: https://github.com/alexobviously/vertex
It sort of works - colours are getting parsed and assigned but they're not the right colours. The actual colours should be quite dark but I'm getting very bright whites and blues, and it looks like only some of the faces are being rendered. I replaced the movable star in example01 with a vertex coloured model.
If either of you can figure out what's going wrong here I'd appreciate the help 👍
Here's what the model (test.obj) should actually look like:

@alexobviously I think there is a base lighting added to the vertices, maybe it could be that?

Here in this block of code https://github.com/alexobviously/vertex/blob/master/lib/mesh.dart#L151
Seems like it adds some lighting, maybe this is what is causing it. Maybe you can change this to only be activated when there is no colors being applied?

Here in this block of code https://github.com/alexobviously/vertex/blob/master/lib/mesh.dart#L151
Seems like it adds some lighting, maybe this is what is causing it. Maybe you can change this to only be activated when there is no colors being applied?

Lighting sounds like about the right thing here, but I'm not sure that anything in that bit of code would affect it?
The 'xn' variable isn't referenced after it's assigned (so actually normals aren't used at all for colouring?) and b is just fixed at 1.0, so the colours should be just passed through as far as I can see.

I've updated my version of the repository with an 'example03' to make it simpler to compare. This is what I get at the moment.

There seems to be two problems. Firstly, some of the faces seem to be invisible. I'm not sure what's going on there. Can either of you see anything wrong?
The other problem is that actually the colours are backwards! When I set red to 0, for example, I get a totally red model. (This is also useful for seeing how some of the faces are not getting drawn).

Confirmed that the missing faces are actually transparent, not just white:

@cenomla @nythrox do either of you have any ideas about this? I'm a bit stuck on this problem.

@alexobviously sorry man... I really have no idea what could be causing the problem, maybe you could try reaching out to the gskinner team but it's a long shot

Are the faces in your mesh triangulated? It's not just the colors that are off from what I can tell in your screen shots, the geometry is also incorrect. Currently the obj loader only supported triangulated faces.


Digital clock

We want to try to implement a digital clock that would have a live ticking after activation of the focuses or break periods.
See: https://codepen.io/alvandisetvat/pen/WNzJaOB

After a research I can conclude that the only way to show that type of clock will be through the WebApps


Bot doesn't drop Pokemon once bag is full

Running dev branch
Bot doesn't drop Pokemon once bag is full

Well if you want a quick fix; I have an issue with the bot not notifying me when the bag is full, so I added this release config and it cleaned up the mess. (Keeping the strongest of duplicates and releasing the rest, therefore emptying my bag)
"release": {
    "any": { "keep_best_iv": 1 }
}

I would add, if you have any pokemon you want to keep, mark them as favourite first. The game doesn't transfer favourite pokemons, so it should protect them.

what pokemon would it drop?


Failed to load resource: the server responded with a status of 404 () sweetalert2.css and sweetalert2.min.js

Laravel Version: 5.6.31
PHP Version: 7.2.6-dev
Laravel-admin: 1.6.7

Description:
After login on /admin/auth/login it goes to "Dashboard" and I got this error messages in my Chrome Console:
Failed to load resource: the server responded with a status of 404 ()
sweetalert2.min.js:1
Failed to load resource: the server responded with a status of 404 ()
sweetalert2.css:1

It looks for the files here /public/vendor/laravel-admin/sweetalert2/dist/
I don't have sweetaler2 I have only /public/vendor/laravel-admin/sweetalert/dist/sweetalert.css
Steps To Reproduce:
After I upgraded from 1.5.19 to 1.6.7 I start getting the errors.

Sorry, I haven't delete public/vendor before running composer install


when a column contains alpha numeric ending with 'e', pandas converts these to float64

I'm reading some excel spreadsheets (xlsx format) into pandas using read_excel, which generally works great. The problem I have is that when a column contains alpha numeric ending with 'e', pandas converts these to float64 type without 'e' in its value, and I would like them to be treated as strings. After reading them in, I can convert the column to str:

dataset = read_excel(excel_file,sheet_name,na_values=[" "])
while reading this excel file to dataset it shows loan id as a number without 'e'

closing, but pls reopen if the issue persists.


MaskedView for android?

Hi, I was wondering if there's any plans for masking view in android? MaskedViewIOS is working perfectly great.

This should be opened.


limit user details based on user type

Proposed Changes

Removed sensitive fields from user list response for non admin users

Associated Issue

https://github.com/coronasafe/care_fe/issues/7374

@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins

@khavinshankar

as a nurse id , iam able to view all restricted details mention in the issue, can you fix it

LGTM


Updated Lobby, made sure prod url is used in prod, closes #32

@trofej it's not deleted, I moved it up to line 42 so it would apply to both host and guest. The reason this is important is that only either the host or the guest should call startGame, not both, otherwise one overwrites the changes of the other and we get a mess. This had somehow gotten lost in previous updates.

@trofej it's not deleted, I moved it up to line 42 so it would apply to both host and guest. The reason this is important is that only either the host or the guest should call startGame, not both, otherwise one overwrites the changes of the other and we get a mess. This had somehow gotten lost in previous updates.

Okk, nice, makes sense :]


[Impeller] fullscreen clips can de-opt clear color optimization.

This is one of the causes of excessive overdraw on flutter/gallery. There are multiple full screen color draws which are expensive, but these don't always hit the clear color optimization as there is some clipping happening.
Additionally, unecessary clipping is more expensive on Android, so avoiding extra stencil operations might be good independently of the clear color optimization.

Navigator.of(context).push(PageRouteBuilder(
opaque: false,
pageBuilder: (BuildContext context, _, __) {
return YourFullScreenAlertDialog()
}
));


Revert "bazecor: init at 1.3.2"

Reverts NixOS/nixpkgs#254716
This package is a duplicate of the existing bazecor top-level attribute and merging it broke the pkgs/by-name CI test.
Additionally, the version submitted is older than the version we already have.
When merging, use squash and insert the reason into the commit message

Interesting to finally see such a failure in the wild, thanks for the ping!

I restarted all CI jobs from other PR's that failed. For future reference, here's a failing CI run result: https://github.com/NixOS/nixpkgs/actions/runs/6944912028/attempts/1#summary-18893104856

When merging, use squash and insert the reason into the commit message

Oh sorry I didn't do that!


Creating flexbutton from Code Behind has jumping issue

Hello,
I am having an issue where the width of my button is changing when it is added from the code behind. this is resulting in the last letter of my button being shifted to a second line for a second.
The button which is added from the XAML is not affected.
Any help would be hugely appreciated.
Regards,
Shane
XAML
<StackLayout BackgroundColor="White">         <ScrollView Orientation="Horizontal"                     Padding="0">             <StackLayout Orientation="Horizontal" HeightRequest="50"                           Padding="0" BackgroundColor="MidnightBlue"                          Spacing="0">                 <flex:FlexButton                     WidthRequest="70"                     HeightRequest="50"                     Icon="folder_up.png"                     Padding="0"                     HorizontalOptions="Center"                     ForegroundColor="#ffffff"                     HighlightForegroundColor="#49516F"                     BackgroundColor="#6279B8"                     HighlightBackgroundColor="#8EA4D2"                     ClickedCommand="{Binding BackUpBtnCommand}"/>                 <StackLayout Orientation="Horizontal" x:Name="TopButtons"                              Padding="0" Spacing="0">                                  </StackLayout>             </StackLayout>         </ScrollView>
C#
`private void CreateTopButtons()
{
TopButtons.Children.Clear();
TopButtons.HeightRequest = 50;
        foreach (var bc in ViewModel.BreadCrumbs)
        {
            var butt = new FlexButton
            {
                Text = bc.Name,
                WidthRequest = 100,
                HorizontalOptions = LayoutOptions.Start,
                ForegroundColor = Color.FromHex("#ffffff"),
                HighlightForegroundColor = Color.FromHex("#49516F"),
                BackgroundColor = Color.FromHex("#6279B8"),
                HighlightBackgroundColor = Color.FromHex("#8EA4D2"),
                TouchedUpCommand = ViewModel.SetCommand(bc)
            };
            TopButtons.Children.Add(butt);
        }
    }`

(sorry about the huge screenshots)

Can you please check, if this is still an issue in v0.9.0? Fixed in version 0.9.0: https://www.nuget.org/packages/Forms.Controls.FlexButton/0.9.0
You can control the max number of lines now, which is 1 by default.


JsonGenerator createJsonGenerator is deprecated

https://fasterxml.github.io/jackson-core/javadoc/2.2.0/com/fasterxml/jackson/core/JsonFactory.html#createJsonGenerator(java.io.OutputStream)

Deprecated Since 2.2, use createGenerator(Writer) instead.

https://github.com/marklogic/marklogic-contentpump/blob/81c78f8a023c9097d36ad2ca7f3bc130a06ca854/src/main/java/com/marklogic/contentpump/utilities/JSONDocBuilder.java#L59

Hi,
This issue will be fixed in 10.0.9 release (scheduled in Feb 2022).
Regards,
Abika


Profiles break when openapi.servers is defined

Spent some time trying to figure out why API generated from a flattened openapi spec wouldn't work.
Cmd such as restish hiro get-status returns ERROR: Caught error: Get "https://extended/v1/status": dial tcp: lookup extended on <IP_ADDRESS>:53: no such host
On deletion of
servers:
  - url: https://stacks-node-api.mainnet.stacks.co/
    description: Mainnet
  - url: https://stacks-node-api.testnet.stacks.co/
    description: Testnet
  - url: http://localhost:3999/
    description: Local

The command works

Restish spec
{
  "hiro": {
    "base": "https://stacks-node-api.mainnet.stacks.co/",
    "spec_files": ["openapi.yaml"]
  }
}

This was a super interesting bug due to the trailing slashes in the server URLs. Thanks for reporting! Should be fixed in the next release coming soon!

Awesome, thanks for fixing


Why does iperf3 measure asymmetric throughput?

I'm working on a project that builds on top of gvisor-tap-vsock. I reproduced your iperf3 throughput measurements and noticed that server-to-client traffic is about 3x faster than client-to-server traffic—at least in our more complex test setup.
The README says "[...] depending on which side the test is performed [...]", so this is not news to you. I wonder however why that is? What exactly contributes to the throughput being asymmetric?

Guillaume who ran these tests and added this to the README is no longer active on gvisor-tap-vsock, so I'm afraid this knowledge was lost :-/

Guillaume who ran these tests and added this to the README is no longer active on gvisor-tap-vsock, so I'm afraid this knowledge was lost :-/

Having studied the code for a while, I can now answer my own question. The send and receive path for network packets differs in non-trivial ways. The same is true for the tools cmd/gvproxy and cmd/vm. I haven't measured the exact overhead but I'm fairly confident that this explains the difference. See this PR for some additional context.


chore(master): release 6.7.4

:robot: I have created a release beep boop
6.7.4 (2024-02-27)
Bug Fixes

do not dispose arraybuffer in browser (#906) (1524f74)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/bee-js/releases/tag/v6.7.4 :sunflower:

Release v6.7.4 addresses this.


Update to catkin instead of catkin_make

catkin_make is deprecated, use catkin build, migration per http://catkin-tools.readthedocs.io/en/latest/migration.html

Needs to be done along side https://github.com/rosmod/rosmod-comm/issues/5

closed by #162


Add scripts/run_kto.py

Description
As briefly discussed with @lewtun this morning, this PR adds the scripts/run_kto.py script to fine-tune LLMs using the trl.KTOTrainer from the alignment-handbook.
The script should work as is, but still needs to be tested, cc in case you're interested @jiwooya1000 and @nlee-208
The main reference used to put the script together has been https://github.com/huggingface/trl/blob/main/examples/scripts/kto.py.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Crash when starting thread

Godot version:
Mono 98caeb635
OS/device including version:
Windows 10 1903
Issue description:
Game crashes when trying to start a thread. Also tried GodotSharp.attach_thread() since i use mono version:
extends Node2D

onready var thread = Thread.new()

func _ready() -> void:
	thread.start(self, "test")
	thread.wait_to_finish()

func test():
	print("Thread started")

func test2():
	GodotSharp.attach_thread()
	print("Thread started")
	GodotSharp.detach_thread()

EDIT: Turns out that you HAVE to pass an argument, even if you don't use it. Since this is still a bug, i'm not sure if i should close. There are probably duplicates out there. Here is the code that worked for me:
extends Node2D

onready var thread = Thread.new()

func _ready() -> void:
	thread.start(self, "test", [])
	thread.wait_to_finish()

func test(p_dummy_param = ["NEVER USED!"]):
	print("Thread started")

func test2():
	GodotSharp.attach_thread()
	print("Thread started")
	GodotSharp.detach_thread()

On macOS non-mono version it's not crashing, but is printing following error instead:
E 0:00:00:0386   _start_func: Could not call function 'test' to start thread 4: Too Many Arguments.
  <C++ Error>    Method/Function Failed.
  <C++ Source>   core/bind/core_bind.cpp:2671 @ _start_func()

On macOS non-mono version it's not crashing, but is printing following error instead:
E 0:00:00:0386   _start_func: Could not call function 'test' to start thread 4: Too Many Arguments.
  <C++ Error>    Method/Function Failed.
  <C++ Source>   core/bind/core_bind.cpp:2671 @ _start_func()

Same message for me but it also crashes :grimacing:

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?
If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.

@akien-mga Sorry for the late replay. The crash is not happening anymore but I get:

Same as @bruvzg. So although it does not crash, the error message is still misleading since it says Too Many Arguments. but in fact the problem is that you have to Add an empty argument for it to work. I've also added a minimal reproduction project in case this stays open.

@akien-mga Sorry for the late replay. The crash is not happening anymore but I get:

Same as @bruvzg. So although it does not crash, the error message is still misleading since it says Too Many Arguments. but in fact the problem is that you have to Add an empty argument for it to work. I've also added a minimal reproduction project in case this stays open.


adding new cypress test for CreateImageWizard

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report

Merging #519 (27bcc3a) into master (f91ed00) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 27bcc3a differs from pull request most recent head 99a3305. Consider uploading reports for the commit 99a3305 to get more accurate results

@@           Coverage Diff           @@
##           master     #519   +/-   ##
=======================================
  Coverage   31.07%   31.07%
=======================================
  Files         124      124
  Lines        2616     2616
  Branches      798      798
=======================================
  Hits          813      813
  Misses       1654     1654
  Partials      149      149

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


Visual Studio: Don't override user options. Add additional vs hint information

All of NMakePreprocessorDefinitions/NMakeIncludeSearchPath/AdditionalOptions entries that we generate are hints to VS about where to find things, what defines are active, etc, and they're generated based on what scons knows about a particular build configuration. However, there's a lot of implicit compiler settings (like default include paths, default defines, etc), that the compiler adds automatically and that scons can't tell us about. For VS to resolve things more accurately in the editor, either the user or the platform (or both!) need to add some extra information.
This PR makes sure both users and our build system can add additional information to VS about where things are found and what things are defined. It also lets users customize the binary name, in case they want to debug or deploy from VS and the final deployed binary name differs from the default one.
/cc @akien-mga @bruvzg @mhilbrunner
Contrbuted by W4Games ❤

Thanks!


Incorrect information in information box

It looks like the information box in the top of the section
#column-level-encryption-by-using-an-asymmetric-key-from-the-key-vault
should state:
You cannot use the same asymmetric key for column level encryption if you've already used that key for TDE or backup encryption (the preceding examples).
Currently it does not mention column level encryption, but references backup encryption twice.

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

ID: 561a78d9-5662-287c-2599-a36b2102b8d5
Version Independent ID: 9820cfde-5caa-1a7f-cdb5-06df907b7395
Content: Use SQL Server Connector encryption with Azure Key Vault - SQL Server
Content Source: docs/relational-databases/security/encryption/use-sql-server-connector-with-sql-encryption-features.md
Product: sql
Technology: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

@Dottn -- thank you for your thoughtful feedback.
@jaszymas -- please look into this issue.

Thanks for reporting this, @Dottn, and thank you for your patience. The section in question will be updated in the next day or so.