Update index.md

Added other ways to print data

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Were you serious when you checked?

My pull request has a descriptive title (not a vague title like Update index.md)

Please use PR titles which explain what you are changing instead of "Update index.md."
Preview your change before you submit a pull request and format your article correctly with Markdown
Thank you


Link to Robin Greenwood on community.html leads to broken website

On https://prometheus.io/community/ the link to Robin Greenwood, the contributor of the logo, leads to a (broken?) website. According to whois the domain is still registered to Robin Greenwood.
Suggestion: remove the link?
Other ideas?

@juliusv Do you have updated details for Robin?

Asking him...


Please add an "Approve" Button to the Menu

Rather than having to go to the edit menu and then selecting "approve" from the drop down, it would be a
great time-saver to just have an approve button on the menu.
It may not seem like a a huge deal, but (at least the way I use YNAB) is I am repeatedly going back and selecting approve from the menu, and also the menu tends to be slightly laggy which is bit of a nit pick, but I thought I would ask.
Thanks

There are a couple of alternatives;

Easy Transaction Approval
Quickly approve scheduled or linked transactions by selecting the transaction(s) and pressing 'a' or 'enter' on your keyboard. Alternately, approve single scheduled or linked transactions by right clicking on the blue 'i' or link icon.
Show Menu When Right Clicking On Transaction
Right clicking on a transaction will show the contextual menu, allowing easy access to the Edit menu options.

We prefer not to add options to the menu as it quickly gets crowded especially for users on smaller screen.

Hello and thank you for the feature request. For organization purposes and the ability for the community to decide what features get built next, we track all feature requests in Trello!
I've added your request here. Thanks once again!


add type definitions and format code

okay lets be honest your code is really messed up right now. please go through all the commits and understand the usage of typescript. i have also added 2 todos for you to do. the main flaw in your app is that you've declared todos an array of arrays of strings and when you map over it you use todo which will be an array of stings. you pass that as a prop into todo.tsx but there you're using todo[1] as a boolean value. this is a very type unsafe and could bring about a lot of bugs. please do fix at least this.
edit: you hadn't passed keys when mapping over an array so i added that here but then i saw it could be simplified so please check this commit too. i also recommend reading this: https://reactjs.org/docs/lists-and-keys.html
edit 2: since you're using Vercel you can see a preview deployement of my changes. please check that as well.

thanks lol


clr-datagrid doesn't resize correctly last data grid column when it displays long data  and columns have specified width

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
The horizontal scroll bar not to appear when resize columns.
Actual behavior
The horizontal  scroll bar appears.
If the grid has row actions the horizontal  scroll bar doesn't appear. I would like the same behavior
when there is no row actions.
Reproduction of behavior
https://stackblitz.com/edit/clarity-light-theme-v11-s1mu2h
Environment details

Angular version: 5.2.1

**Clarity version: 0.11.1

**OS and version: Windows 10

Browser: Chrome

This looks like a bug to me, some variation of the automatic column width computing + extra columns (checkboxes, actions, expand caret, ...) that we supposedly fixed a while back.
At the very least both version of the datagrid in this stackblitz should have the same behavior. In the second one, it looks like the width computed for the last column doesn't use the proper column's data.

Fixed by #2670.


Argument is needless?

Thanks for your code — it's a pure beauty!
I just wonder if method

has a needless argument activity which is passed to queuePhoto and never used there at all.

You're absolutely right, thanks for that. I've commited a fix
https://github.com/thest1/LazyList/commit/fe1baee74473f234e51d613d0bd103c3f0e161c7
.
2011/11/17 Aleksey Malevaniy <
<EMAIL_ADDRESS>

Thanks for your code — it's a pure beauty!
I just wonder if method
imageView)

has a needless argument activity which is passed to queuePhoto and
never used there at all.

Reply to this email directly or view it on GitHub:
https://github.com/thest1/LazyList/issues/3


Headless UI Combobox?

Is the combobox component in the work or is this something you are not looking to implement currently? Was there a reason you didn't do port it with the others?

Hey thanks for reaching out!
So to be honest I didn't implement the ComboBox yet for two reasons:

I didn't need to use it myself so far
I am scared about the efforts of implementing and maintaining it. It is a rather complex component and also it will be really difficult to deliver the same developer experience as the JS packages of Headless UI do. One part for example which will take some brainstorming to implement is Binding objects as values.

So I want to definetly implement it at some point but was lacking the motivation so far... I hope I will find some time in the upcoming weeks. On the other hand there is also a big update on Headless UI in the pipeline which will introduce even more new components which I want to implement using Ignis (https://github.com/tailwindlabs/headlessui/releases/tag/%40headlessui%2Freact%40v2.0.0-alpha.1). But before I will start with this I will make sure to implement the ComboBox!

I will leave this issue open until the ComboxBox component is implemented and I will also pin it for visibility.

@DavidVollmers I appreciate the reply. I thought reason one would likely be the case. Also v2 looks good. Thanks for the great work.
Also would it be a good idea to enable Discussions for the repo. Would be good to ask question about the library that are not issues? Or are you happy them being open as issues?

Good point! I enabled discussions right away. Completely forgot that feature exists...


Consider enabling semantics in tests and debug mode always

See https://github.com/flutter/flutter/issues/31139
We have asserts in various places (and want to add more) to guard against incorrect semantics constructions.  Violating these asserts can result in crashes in the a11y bridge implementations at runtime in release mode.
However, even adding more asserts could still result in developers not seeing the assertion errors in their apps unless they test in an environment where accessibility services are enabled - e.g. the iOS Simulator where we always turn them on, or an Android device with accessibility settings enabled.  Unfortunately, it is very easy to test only on an Android device and find that everything appear to work when it does not.
We should consider enabling semantics for all tests and in debug mode, so that developers can see these errors firing and be more likely to fix or at least report them before going to production.
/cc @goderbauer @jonahwilliams @Hixie @tvolkert

I like the idea. Obviously, just like with any crash, we have to make sure its obvious why people a re seeing a crash.

I'm wondering if we should give developers the option to turn this off - though I suspect it would be better to just make sure that hot restart/hot reload play nicely with clearing/refreshing the semantics tree.  I've fixed bugs related to that but there may be more.

Yeah, everything should "just work" :)
We should probably also include this change in the changelog and maybe tell people on flutter-announce. so nobody is surprised if they see more asserts.

We probably don't want this on by default for the web though, until we make performance improvements

The change I'm proposing in Flutter/engine is completely in Native code - this will have no impact on flutter for web.

Right, but we also probably want to consider consistency of experience

I guess that is already not consistent because of how the iOS simulator behaves, so it probably doesn't matter

Testing is done, at least for widget tests.
I'm running into some challenges with trying to do this for actual apps.
It's easy enough to get the framework to generate the tree. It's not much harder to get the engine to tell the framework to do that.
The problem right now is that each embedding listens to the OS for whether accessibility services are enabled, and if they're not the embedding doesn't listen to accessibility events. So while turning this on for apps would exercise the framework side semantics code, it would not exercise the bridge implementation for the platform, which is the kind of bug i was hoping to get to.
Another way to approach this is to write tests for the variants of the public API of the bridges. It would probably be better to do that for now, though I think this would be worth coming back to if we can figure out a way to make it worthwhile (or if we're convinced that at least turning on the framework side semantics code is worthwhile).


No tag list wrap on New Community Resource

As an authenticated or unauthenticated user, when I use the new community resource form the tags list does not wrap, even upon reaching the viewport edge.
Deployed commit f30c47a
Tested in FF 77, Chrome, Edge.

No longer an issue.


Input.is_action_just_pressed isn't working

Godot version
Android version 4.1.1
System information
Android - Godot 4.1
Issue description
I want to make buttons on the screen for a mobile game, for example i have action "jump" for jumping, (added it to the actions in input map and also in the TouchScreenButton too, but when i use Input.is_action_just_pressed i don't get any output at all, if saying that the button doesn't work? It does, Input.is_action_pressed works fine..... But i want 1output/click, and that's what Input.is_action_just_pressed does..... PLEASE HELP I'M LITERALLY SO TIRED... I'm giving up my project until this gets a fix or a solution 🥺🙏
Steps to reproduce
@test_project.zip
Minimal reproduction project
test_project.zip

Thank you for the report. This is a known issue and already reported.
Consolidating as a duplicate of #66318.


Reverse force setting value to empty string

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
#19322

👍


'AppCommand' has no attribute 'option_list'

I'm attempting to run the generator for app named "manager"
python manage.py generate manager --format modelviewset
I'm getting the following error
  File "/python/api/lib/python3.5/site-packages/drf_generators/management/commands/generate.py", line 8, in <module>
    class Command(AppCommand):
  File "python/api/lib/python3.5/site-packages/drf_generators/management/commands/generate.py", line 33, in Command
    option_list = AppCommand.option_list + base_options
AttributeError: type object 'AppCommand' has no attribute 'option_list'

What django version are you on?

@Brobin I followed blog tutorial, it uses python3 / django 1.7

Ah, yes. We may have to monkey patch this if the same features aren't backward compatible.

Marking as duplicate of #28


Peer Dependencies issue

@whoisandie When I npm install this it doesn't work. Here are my errors:
npm ERR! argv "/usr/local/Cellar/node/6.6.0/bin/node" "/usr/local/bin/npm" "install" "react-input-range"
npm ERR! node v6.6.0
npm ERR! npm  v2.15.1
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| ^15.0.0
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| ^15.0.0
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| ^15.0.0```

@grp06 Looks like some problem with the package you're trying to install (react-input-range). Rangeslider has react as its only peer dependency. Try installing react-dom and then install react-input-range.


Need instructions on how to handle the event

The documentation suggests that valueChange will be fired when the user toggles the button , Can you share an example with usage of the callback.
I tried using valueChange just like other options of the plugin and catch the event, But nothing happens.
Angular version : 6.0
ngx-toggle version: 2.0.1

@gopal-g Can you provide an example of what you're referring to? You can use the output (valueChange) or use the ngModel method.

I want to be able to trigger a method/function in the component when user toggles the button.
suppose this is my component HTML
<ngx-toggle name="verifiedToggle" onColor="{{verifiedToggle.onColor}}" onText="{{verifiedToggle.onText}}"
                    offColor="{{verifiedToggle.offColor}}" offText="{{verifiedToggle.offText}}" [disabled]="verifiedToggle.disabled"
                    [size]="verifiedToggle.size" [(ngModel)]="verifiedToggle.value">
                  </ngx-toggle>

this is my component
import { Component } from '@angular/core';

@Component({
  selector: 'my-app',
  templateUrl: './app.component.html',
  styleUrls: [ './app.component.css' ]
})

export class AppComponent  {

  name = 'Angular';

  actualToggleValue = "NO";

  public verifiedToggle = {
        'onColor': 'success',
        'offColor': 'secondary',
        'onText': 'Yes',
        'offText': 'No',
        'disabled': false,
        'size': 'sm',
        'value': false
    };

  onToggle(state){
     console.log('' current toggle state is ", state);
     this.actualToggleValue = state ? "YES" : "NO";
  }

}

How do i trigger the onToggle function inorder to track the toggle status ? Cause i want to set the value of the actualToggleValue variable instead of true or false.

Hi @gopal-g . Do you understand Angular output events and how to use them?
If you're simply wanting to display a value based on the boolen result, I suggest checking out this Angular guide: https://angular.io/guide/component-interaction

Thank you for this I had no idea, Will have a look and try it out.


Example ids

This introduces a new metadata key :rerun_file_path.  This is usually the same as :file_path but can be different for situations such as an abstract example defined in a shared example group.  In that situation :file_path would be file the shared example group is defined in (e.g. spec/support/model_shared_examples.rb), whereas :rerun_file_path would be the file would be something like spec/models/my_model_spec.rb -- a particular spec file that includes the shared example group.  The :rerun_file_path is the file arg you would have to pass to rspec to cause the example to be re-run.
I wound up with a slightly different format for example ids than what was discussed in #1767 (e.g. ./spec/rspec/core/example_spec.rb[1:14]). You can also specify multiple examples or groups: ./spec/rspec/core/example_spec.rb[1:14,1:15]. I thought the brackets make a nice syntax for separating the id part from the file part, and it makes it clear that you are passing an example id, whereas in the syntax suggested in #1767, it's harder to differentiate between an id filter and a location filter -- file_name:1 would be ambiguous about whether it's a line number or id filter.  This allows us to support passing ids simply as the main args to rspec, e.g. rspec ./spec/rspec/core/example_spec.rb[1:1] ./spec/rspec/core/example_group_spec.rb[1:1], which I think is better than a specific --ids flag.  One downside to this syntax is that zsh makes you wrap it in quotes due to the use of [...].  Bash doesn't, though.  I'm not sure about Windows, but it's the syntax Rake uses for task arguments so I figured it's already been vetted and proved out by rake and I have to assume rake works fine on windows.
The rerun command printed for each failed example will now use the example id if the location would match multiple examples, so that the rerun command is always guaranteed to match only the specific example it is intended for.  (This is commonly needed for failed examples from shared example groups).  One issue with this change: if you run zsh (as I do), you can't simply copy and paste the rerun command anymore in these situations, since zsh forces you to escape the [] characters.  It'd be nice to do something about that but I'm not sure what.

TODOs:

[ ] Ensure rerun command can be copied/pasted in zsh
[ ] Add changelog entries

(...continued...)
What do people think about the semantics and syntax of the example id filtering?
/cc @rspec/rspec @JoshCheek

OK, the build is green and this is ready for a review.
/cc @rspec/rspec @JoshCheek

I did a partial review, I'll give more feedback when I get more time.

OK, I'm done. Let me know what you think :)

Today and tomorrow are pretty packed full, but I'll try and take a look sometime in the several days.

OK, I'm done. Let me know what you think :)

Thanks for the review!  Any ideas what we can do about the zsh square bracket problem?

Today and tomorrow are pretty packed full, but I'll try and take a look sometime in the several days.

Thanks, @JoshCheek...more :eyes: on a PR is always nice :).

I had a scan, looks good too me

I had a scan, looks good too me

Any ideas for what to do about zsh complaining about []?  That's the main thing left here.  I may just always escape ids when printing them as a re-run command but that seems kinda lame given that bash is more common...

I'm not a zsh user either :/

OK, so looks like ENV['SHELL'] tells us what shell is being used, and it's easy to look for zsh in that.  We need to decide between two strategies:

Printing the example ids un-escaped by default, and only escaping them if the shell is one we know has a problem with it.
Printing the example ids escaped by default, and only disable the escaping if the shell is one we know is OK w/ [].

I'm thinking we should go with the second option.  We can test the common shells (zsh, bash, csh, any others?) and for anything unknown have it escape to be on the safe side.  Question is, which of these forms do we prefer?
rspec ./path/to/spec.rb\[2:2\]

# or

rspec './path/to/spec.rb[2:2]'

I think I prefer the latter...the / looks ugly.

I agree on the later, and on escaping unless we know we're good.

zsh users can also run the command with noglob e.g. noglob rspec ./path/to/spec.rb[2:2] lots of zsh users will already have this aliased for rake (many without knowing).
See: https://github.com/sorin-ionescu/prezto/blob/b41f4855286cd9ec2b00f7c8d91a6e2778009d51/modules/utility/init.zsh#L43
and: https://github.com/robbyrussell/oh-my-zsh/blob/cea29ff7ce4094809d0089b7469d0f9e1f22b407/plugins/rake/rake.plugin.zsh#L5

zsh users can also run the command with noglob e.g. noglob rspec ./path/to/spec.rb[2:2] lots of zsh users will already have this aliased for rake (many without knowing).

Right.  I'm aware of that, but the re-run command should "just work" and not require users to do something special like that.  Good to know, though.

OK, I implemented the quoting for non-bash shells as discussed.  Anyone know what other shells (if any) support the id syntax w/o quoting? I tested it on:

bash
zsh
tcsh
csh
ksh

We can add more to the list later but if anyone knows of others we can add them now.

I use fish, it doesn't need quoting:
$ ruby -e 'p ARGV' ./path/to/spec.rb[2:2]
# ["./path/to/spec.rb[2:2]"]

$ fish -c 'ls [lt][im][bp]'
# ls: [lt][im][bp]: No such file or directory

$ bash -c 'ls [lt][im][bp]'
# lib:
# rspec
#
# tmp:
# aruba

Thanks, @JoshCheek, I added fish to the list of shells that allow unquoted ids.

@JonRowe is this good to merge?

LGTM


fixes a bug where qx serve ignored bundling

fixes a bug reported by @voger on gitter

Merging, thank you @johnspackman


failing test to show Decimal serialization fails when using rest_framework

Failing test to illustrate #97

I can definitely reproduce this bug locally thanks to your test. I'm not sure where the issue does come from though, I need a closer look!

I'm closing as it was included in #99


Move linting to separate job.

Currently, each job in the matrix strategy runs golangci-lint, which is slightly inefficient and expensive given the price of macOS runners. This PR moves the lint step to a separate job and defaults to the stable version of Go.

/lgtm

/approve


Two personality traits

PHB123 says that you should give your character two personality traits. Currently the generator only chooses one trait.
I will endeavour to add the second trait and open a PR in due course, but feel free to add it yourself, @trwolfe13.
Thanks.

Solved by #2.


feat: Create frontend support for AI Hint generation using ChatGPT for the basic layout

Create a renderGPTText helper function
Create frontend support for ChatGPT AI generated hints with streaming
Load the function URL through github secrets workflow

https://github.com/user-attachments/assets/14db8c8e-f50f-48db-ab35-fc163a896803

Updated video with reloading hints
https://github.com/user-attachments/assets/79fcb04b-b8b0-4df5-b0b1-169346948588


CASMTRIAGE-3727-1.3 : INSTALL: Postgres test needs to specify a container

Summary and Scope
Specifies postgres container in postgres goss test scripts
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CASMTRIAGE-3727
Change will also be needed in NA
Future work required by NA
Documentation changes required in NA
Merge with/before/after NA

Testing
surtur
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
Verified that the tests that were failing now pass.

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[x] Target branch correct
[ ] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Looks like the goss RPM doesn't exist yet?


Add new hindi and english course

Please merge my pr
https://github.com/EbookFoundation/free-programming-books/pull/7217/

Please merge my PR
#7386


release: 0.8.0

Codecov Report

Merging #30 (91c85bc) into master (1408f72) will not change coverage.
The diff coverage is 100.00%.

@@          Coverage Diff           @@
##           master     #30   +/-   ##
======================================
  Coverage    4.92%   4.92%
======================================
  Files           6       6
  Lines         142     142
======================================
  Hits            7       7
  Misses        135     135

Impacted Files
Coverage Δ

reana_workflow_engine_snakemake/version.py
100.00% <100.00%> (ø)


KAFKA-14722: Make BooleanSerde public

Overview
Addition of boolean serde
https://cwiki.apache.org/confluence/display/KAFKA/KIP-907%3A+Add+Boolean+Serde+to+public+interface
Testing strategy
Unit tests in SerializationTest, I've also checked if unit tests for NullableValueAndTimestampSerializer work because that's the only code that currently depends on BooleanSerde
@mjsax
I'm stating that contribution is my original work and I license the work to the project under the project's open source license.

The build is currently failing with spotbug errors.
[2023-03-19T21:19:57.094Z] * What went wrong:

[2023-03-19T21:19:57.094Z] Execution failed for task ':clients:spotbugsMain'.

[2023-03-19T21:19:57.094Z] > A failure occurred while executing com.github.spotbugs.snom.internal.SpotBugsRunnerForHybrid$SpotBugsExecutor

[2023-03-19T21:19:57.094Z]    > Verification failed: SpotBugs ended with exit code 1. See the report at: file:///home/jenkins/workspace/Kafka_kafka-pr_PR-13382/clients/build/reports/spotbugs/main.xml

You can ignore spotbugs for this file/class at spotbugs-exclude.xml

Hello I've looked into the pr-merge and the only warning that I see is this:
[2023-03-22T22:21:56.566Z] Recording test results
[2023-03-22T22:22:14.166Z] [Checks API] No suitable checks publisher found.
So I think now the changes should be ok.
I've tried to run ./gradlew test on my computer but I got many errors in unrelated modules from this change for some reason.

@SpacRocket The tests don't look related. Can you run them locally?

Apple M1:
JDK 17, Scala 2.13
testDeleteInternalTopic [1st test] (2/2 tests passed)
testDescribeQuorumStatusSuccesful [2nd test] (6/6 tests passed)
testTaskRequestWithOldStartMsGetsUpdated [3rd test] (test passed)

JDK 8, Scala 2.12.17
I've run this test without any issues
testDynamicListenerConnectionCreationRateQuota [4th test] (test passed)

@SpacRocket I forgot to ask earlier, but can you update the upgrade notes to include this change? We try to document all the public changes

@wcarlson5 Thank you for your time, a question what do you mean exactly by upgrade notes?
I've searched for it in wiki and couldn't find it:
The KIP is currently in this table:

also I've seen that JIRA story hasn't been closed automatically so I left a comment.

@SpacRocket Walker is mentioning upgrade notes for 3.5 similar to https://kafka.apache.org/documentation.html#upgrade_340_notable You can modify them at https://github.com/apache/kafka/blob/trunk/docs/upgrade.html#L83 (you will have to create a new section here for 3.5). Let us know if you are hit a roadblock doing it.

@SpacRocket -- what @divijvaidya says. -- Can you do a follow up PR?
This is a smaller feature though, and I don't think it should go into docs/upgrade.html but only into docs/streams/upgrade-guide.html.

@mjsax Sure thanks for the suggestion. I've pushed a new commit in this pull request:
https://github.com/apache/kafka/pull/13491


Added 'messagetype'-option

I've added 'messagetype' as a configurable value. It is required to be set to 'unicode' for UTF-8 messages.
http://www.mobilant.de/files/Mobilant_Gateway_HTTP_API_Specifications_DE.pdf

Closing this because of inactivity. Please reopen, if there is something new.


link to paper in README is broken

The link to the paper: Practical considerations for measuring the effective reproductive number, Rt in the last section of README.Rd is broken

Thanks @kylieainslie. Fixed in b5563d9


Allow use of base classes in permission checks [SCI-4597]

It makes possible use of base classes in permission checks, useful for creation of common permission checks, for example for models using STI

I think this is okay :+1:.


Invalid prop: type check failed for prop "size". Expected Object, got String with value "lg"

Describe the bug
After upgrade to 0.17.2 I have this warning in browser console:
Invalid prop: type check failed for prop "size". Expected Object, got String with value "lg".
the same for variant or all props defined on component
this happens on all my InputText object.
I think it's something to export type related but I can't understand what it is.
Below reproduction, please remember to open console
Reproduction
https://stackblitz.com/edit/github-dqx2in?file=src%2FApp.vue,package.json,src%2Fcomponents%2FTextInput.vue
Used Package Manager
pnpm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

This appears to be a bug in Vue. I tried switching between Vue v3.4.23 -> 3.4.24 and before/after it caused the issue.
In-lining
interface BaseSize {
  sm: unknown
  md: unknown
  lg: unknown
}

// type Size = 'sm' | 'md' | 'lg'
type Size = keyof BaseSize

Onto

Shows the issue more clearly
Please make an issue in Vue core


Only copy a subpart of a source image to a directory

An image can be copied to a directory by using the skopeo dir
transport. Currently, all parts (config, layers, manifest) of the
source image are copied to that directory.
I would like be able to only copy subparts of the source
image. These subparts could be layers, configs, or manifests.
Is it already possible?
If not, do you think it would be feasible?
And are you also interested by this feature?
Use case: Efficient Docker image storage in Nix
Nix has a content addressable store and images are currently
stored as Docker archives. If several images share identical
layers, these layers are duplicated which is really
inefficient. Instead of storing images as tar, I would like to
store them in directories. This would allow us to symlink layers
in order to share them across several images. Note that Nix does
this kind of things pretty well.
Basically, we could use skopeo inspect to generate several Nix expressions
to pull the image. Each build expression would use Skopeo to download
a part of the image and let Nix stores them into its own store. If two
images use the same layer, Nix is able to reuse this layer, so the
layer is not duplicated in the Nix store.
User Interface proposal
We could add some options on the copy command.
For instance, to copy the first layer of the ubuntu image:
skopeo copy --copy-layer sha256:1be7f2b886e89a58e59c4e685fcc5905a26ddef3201f290b96f1eff7d778e122 docker://ubuntu dir:///tmp/first-ubuntu-layer/

The --copy-config and --copy-manifest flags would be used to
copy the image configuration and manifest. Without any of these
flags, all parts of the image would be copyied. Note these
options would only works with the dir transport.

@mtrmac @runcom WDYT?

Most of this already exists, to serve exactly the same needs of the ostree transport, as skopeo layers – but deprecated. It should be very easy to write a similar wrapper around ImageSource which extracts exactly the needed blobs, if you don’t need the whole copy machinery (signatures, manifest conversion, compression/decompression) etc.
There is also a somewhat previous conversation in https://github.com/containers/image/pull/218 , and IIRC there may have been a few others; the “copy an image but only actually copy the specified layers” idea has definitely come up before.

But, overall, I think it would be much cleaner, and more efficient, to implement the Nix storage directly as an ImageDestination in containers/image.  That would allow using the native storage format, with no extra temporary files, only a single pass initializing everything (e.g. only pinging the registry once, and fetching the manifest/config/signatures once), and automatically ensure that e.g. a copy from a :latest tag keeps consistently using the same image, even if the latest tag is redirected while copying the big blobs.
The code to copy into ostree storage has similarly been converted from an external program using skopeo inspect and skopeo layers into a native destination (initially calling out ostree CLI, later converted to call in-process libraries).
Would something like that make sense for Nix? It would be perfectly fine for PutBlob to be a 10-line callout to an external process, or a separately maintained Golang package, for example.
(Sure, that may be too much work, or add too much friction to your development process at this time.)

Since Nix is a build system, we generally prefer to let Nix build stuffs since it does this pretty well:) So, I would like to let Nix build an image from the image dependencies which are layers, config and manifest.
This is a common pattern in the Nix ecosystem. For instance, we have a tool called go2nix that takes a go project as input and generates a Nix expression for each go dependency (which is not vendorized). There are same kind of tools for Python, Rust...
I'm thinking about same kind of tool for container images: a tool that generates Nix expressions to build an image.
So, unlike ostree, we can not implement this in skopeo.
I've tryied the layers command and it seems this is exactly what I need! In fact, I don't really need to download the config and the manifest independently.
Would it be possible to revert the deprecation of the layers command?
Or is there any other plans regarding this feature?

I don’t know of any more plans for skopeo layers (in particular, there is not a set removal schedule) — but ultimately it seems like such a trivial wrapper around c/image that anyone could re-implement / resurrect it again if that happened.
A more complete history is in https://github.com/projectatomic/skopeo/pull/242 and https://github.com/projectatomic/skopeo/pull/264 ; and an old implementation of precisely this RFC is available in https://github.com/containers/image/pull/159/files .
The trouble with skopeo layers is that it is literally exposing a low-level implementation aspect, unlike skopeo copy, which is intended to be a high-level tool that takes care of all the details for the user.
Notably, skopeo inspect does not do any signature verification, and skopeo layers does not verify the downloaded blobs against their supposed digests.  So, in a manually-scripted inspect+layers implementation, even a name@sha256:digest reference does not protect the user against a MITM, or a malicious registry/cache, from substituting the image contents with something unwanted!
I suppose the verification could be done outside of skopeo as well, using skopeo only as a raw docker/distribution client or something like that… but that would make the skopeo capabilities pretty dangerous for uninformed users; I’d be tempted to recommend writing a separate Nix-specific containers/image client which provides this raw access, instead of exposing that in skopeo. Of course, I still don’t really understand the problem space :)

In our case, we don't really care about layer signatures since we must provide the hash of the layer in the Nix expression. This hash is computed in a previous step, a step that relies on the signature of the image but not on the layers command.
I understand that you don't want to expose the layers command to end users. FYI, as a end user, I didn't know it:) So it would be nice if this command could stay hidden.
Thanks for mentioned posts and for your explanations.
I then close this ticket since I get enough information for now.


Non-mini xlsx.js missing "Root Entry" removal for proper ZIP parsing

There is a difference in safegetzipfile method between xlsx.js & xlsx.mini.js.
One is missing replace(/^Root Entry[\/]/,"") so I get this error "Cannot find file [Content_Types].xml in zip" every time trying to read a XLSX file 🤷♂

Thanks for reporting (and for the amusing commentary elsewhere :)
The xlsx.js script was not intended to be used on its own -- there are browser builds in the dist/ folder, and nodejs does something different that avoids the problem.
In particular, the mini build uses cfb for zip processing while the "full" build uses a modified jszip and assumes it exists.  The CFB library presents a zip file like an OLE blob, with an implied root folder "Root Entry" even though it doesn't exist in the zip archive.
Fortunately there's an easy patch.  The fix should be applied to https://github.com/SheetJS/sheetjs/blob/master/bits/21_ziputils.js#L32 :
-		var n = k[i].toLowerCase();
+		var n = (zip.FullPaths ? k[i].replace(/^Root Entry[\/]/,"") : k[i]).toLowerCase();

https://reklamajans.websites.co.in/update/google-reklam-ajansi-hizmetinizde/308177

google reklam ajansı

erinn tjernagel

When will it be published?

I'm trying to develop a new functionality (excel taskpane add-in) and was also trying to use xlsx.js in a browser and got a corruption error when opening the xlsx file.
If you include the jszip.js script before xlsx.js it works.
<script src="jszip.js"></script>
<script src="xlsx.js"></script>

@szilardd make dist generates all of the standalone browser files.  After doing so, dist/xlsx.full.min.js is the desired script.

ef4aec8796c72dc891b619edcd3ef24dde4829d6


Add option to control Oryx sow/reap debug image interface

At the moment, we sow a few intermediate values and gradients of the integrate function using Oryx. It would be nice to sow all of these values, but only if the a certain flag is provided. We can then reap all of these functions and visualize them with Tensorboard.

Added oryx_debug


feat: afterSourcesLoaded hook

What I was trying to achieve was connecting collection entries of two sources with each other, based on certain fields.
However, using the getCollection action in the loadSources hook for this case won´t work, as the collections from the source plugins aren´t loaded before, but afterwards and getCollection always returns 'undefined'.
To solve this, I´ve created a new hook, called afterSourcesLoaded which is called after all source plugins have fetched their data and created their corresponding collections. You can do manipulation on all available data (that is loaded with the data store api).
Although it is working as expected, I´m not sure if it´s done correctly. For example I´ve used the BOOTSTRAP_SOURCES phase twice, not sure if it has side effects in some way.
Also, the createSchemaActions(api, this._app) is called from loadSources and afterSourcesLoaded. Consequences if any?
BTW: Is there any date specified for the next Gridsome release? I have no idea how I can use my changes in production (CI build) without using the NPM releases

Hi @hjvedvik ,
This does unfortunately not work.

    hooks.bootstrap.tapPromise({name: 'afterLoadSources', before: 'createSchema'}, async () => {
        const collection = store.getCollection('Products')
        const post = store.getCollection('Post')

        console.log(collection)
        console.log(post)
    })

    api.afterLoadSources(({getCollection}) => {

    })

the hook is not available and I get gridsome.server.js: api.afterLoadSources is not a function (25:9).
I´m also not sure how, if this would work the hook is called. Would that be done automatically because of the 'before' property?


TypeError: TextEncodeInput must be Union[TextInputSequence, Tuple[InputSequence, InputSequence]]

Hello,
Try to run
bash abtbuy/run_pretraining_clean_roberta.sh 1024 5e-5 0.07 all

on Ubuntu with GPU, torch==1.13.1, but got the following error. I was not able to catch the None as suggested by here. The data were prepared using
src/processing/preprocess/preprocess_deepmatcher_datasets.py
src/processing/contrastive/prepare_data_deepmatcher.py
Any suggestions?
Thank you.
[INFO|trainer.py:1650] 2023-02-06 21:08:47,560 >> ***** Running training *****
[INFO|trainer.py:1651] 2023-02-06 21:08:47,560 >>   Num examples = 1725
[INFO|trainer.py:1652] 2023-02-06 21:08:47,560 >>   Num Epochs = 5
[INFO|trainer.py:1653] 2023-02-06 21:08:47,560 >>   Instantaneous batch size per device = 1024
[INFO|trainer.py:1654] 2023-02-06 21:08:47,560 >>   Total train batch size (w. parallel, distributed & accumulation) = 1024
[INFO|trainer.py:1655] 2023-02-06 21:08:47,560 >>   Gradient Accumulation steps = 1
[INFO|trainer.py:1656] 2023-02-06 21:08:47,560 >>   Total optimization steps = 10
[INFO|trainer.py:1657] 2023-02-06 21:08:47,560 >>   Number of trainable parameters = 124647168
Traceback (most recent call last):
  File "run_pretraining_deepmatcher.py", line 245, in <module>
    main()
  File "run_pretraining_deepmatcher.py", line 231, in main
    train_result = trainer.train(resume_from_checkpoint=checkpoint)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/trainer.py", line 1543, in train
    return inner_training_loop(
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/trainer.py", line 1765, in _inner_training_loop
    for step, inputs in enumerate(epoch_iterator):
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 628, in __next__
    data = self._next_data()
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1333, in _next_data
    return self._process_data(data)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1359, in _process_data
    data.reraise()
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/_utils.py", line 543, in reraise
    raise exception
TypeError: Caught TypeError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
    data = fetcher.fetch(index)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 61, in fetch
    return self.collate_fn(data)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/trainer_utils.py", line 700, in __call__
    return self.data_collator(features)
  File "contrastive-product-matching/src/contrastive/data/data_collators.py", line 87, in __call__
    batch_left = self.tokenizer(features_left, padding=True, truncation=True, max_length=self.max_length, return_tensors=self.return_tensors)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2523, in __call__
    encodings = self._call_one(text=text, text_pair=text_pair, **all_kwargs)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2609, in _call_one
    return self.batch_encode_plus(
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/tokenization_utils_base.py", line 2800, in batch_encode_plus
    return self._batch_encode_plus(
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/models/roberta/tokenization_roberta_fast.py", line 263, in _batch_encode_plus
    return super()._batch_encode_plus(*args, **kwargs)
  File "/anaconda/envs/azureml_py38_PT_TF/lib/python3.8/site-packages/transformers/tokenization_utils_fast.py", line 429, in _batch_encode_plus
    encodings = self._tokenizer.encode_batch(
TypeError: TextEncodeInput must be Union[TextInputSequence, Tuple[InputSequence, InputSequence]]

Thanks very much for the feedback. It could be due to my local settings. I am using transformers==4.26.0.
It turns out my error was caused by this line:
where
doc = Doc(data, self.tokenizer(data))

self.tokenizer on data such as
"[COL] brand [VAL] [COL] title [VAL] tomtom gps mount and usb car charger 9s00006 [COL] price [VAL] 28.0 [COL] description [VAL] tomtom..."
will not treat [COL] as a stopword. Instead, it will tokenize [COL] to [,COL, and ]. So I have to change [COL] to COL in dataset.py.
In addition, this line, where
aug.augment(string)

returns a list or a string by chance and I have to change it to
aux = aug.augment(string)
return aux[0] if type(aux) is list else aux

to ensure a string is returned.
The above changes solved my problem. Let me know if there is any concern for this change. Thanks.

[COL] and [VAL] tokens should actually not be split apart as we add them specifically to the vocabulary of the Transformer (see Line 109 in datasets.py). If you are using a custom tokenizer, make sure you do include those as well.
Regarding the augment function: If the input is a string, it should return a string and not a list. Can you double-check that the input you pass to aug.augment() is really a string and not already a list for some reason?

Yes, you set it in Line 109, but didn't pass it to Augmenter at Line 114,
The 2nd issue may be reproduced by
import nlpaug.augmenter.word as naw
import nlpaug.augmenter.char as nac

import numpy as np
np.random.seed(42)
import random
random.seed(42)

stopwords = ['[COL]', '[VAL]', 'title', 'name', 'description', 'manufacturer', 'brand', 'specTableContent']
aug_swap = naw.RandomWordAug(action="swap", stopwords=stopwords, aug_p=0.1)

string = "[COL] brand [VAL] [COL] title [VAL] tomtom gps mount and usb car charger 9s00006 [COL] price [VAL] 28.0"
print(aug_swap.augment(string))
#my result shows a list and bracket was tokenized
#['COL [] brand [VAL] [COL] title VAL [tomtom] gps mount and usb car 9s00006 charger [COL] price [VAL] 28. 0']

As long as the tokenizer knows [COL] and [VAL] as special tokens during initialization it should not split them as in your previous example. Of course it can happen that the augmentation may corrupt them but this should only be the case for the "crop" augmentation as this does not handle pre-defined stopwords (see below).
As far as I understand the documentation of nlpaug your example should not happen as you explicitly pass [COL] and [VAL] as stopwords which should exempt them from augmentation for the swapping operation (see here)

I was testing action="swap", not crop using the latest version of nlpaug. Have you run the code snippet above and got fine result?

@junwei-h hi, do you reproduce the results in any datasets?

i tried running your snippet (copy/paste) and my output is
COL [] brand [VAL] [COL] title VAL [tomtom] gps mount and usb car 9s00006 charger [COL] price [VAL] 28. 0
It is not a list, just a simple string as it should be. But the problem of still tokenizing the COL and VAL brackets happens as well for me. So it may be that brackets are not correctly handled by nlpaug when they are part of the stopwords. One would have to look into their source code to see how this is done. Regarding the experiments in this paper I do not think this bug has a large impact on the actual results, I would guess they could minimally improve if this bug was fixed and the tokens were properly excluded from the augmentation.
Thank you for bringing this to my attention!

Thanks for confirming your run is similar. The impact on your experiment results could be low, but unknown. For Abt-Buy dataset, using R-SupConf(F)+aug is 93.43% (not 94.29% claimed on paper). My batch size has to be reduced to 512 from 1024 to fit the memory; all other hyperparameters are from your paper.
Would be nice to refresh your experiment results with the bug fixed.


Simon Game

Added a simon game to web dev projects

This is a contribution for hacktoberfest 2021
please review my pr #60 @manjunani


Dew point value incorrect for weather underground

It looks like the dew point that is being received from weather underground is in degrees (f) but being interpreted incorrectly as degrees (c) and then “converted to degrees (f) resulting in a number like 50 degrees for dew point showing up on HomeKit as incorrectly as approx 113 degrees (f)
if the bug is not obvious I can give you my login info to test. I can see this mixed units in the homebridge configuration UI which I attached here.

I updated everything and now the due point is showing correctly! Very odd as I did not notice a fix for this.  Dry curious. The WU code looks OK so some other fix must have fixed this?

Oh I do see a fix for this in characteristics.js in the latest release. I will reopen this only to let you mark it fixed.

I see this is a duo of #178 so I will just close this one.


Transitioning from Node 16 to Node 20

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Nice work!

@JacksonTian @denverdino Could we merge this PR?

Thanks for your contribution


Share screen functionality

This issue will be done after completing:
#150 (Must be done first).
#148
#147

Hey @fyoungqualabs, just a heads up that you can do subtasks in github by adding task lists to the first comment in the issue :)


Clarifications on Cluster documentation and no-data errors

So I am dealing with clustering graphite for a week now. It mostly works, but I would like to check some stuff that between blog posts/documentation/issues in GH is a little confusing.
This is my setup at the moment, using graphite pip installed from master tarball as of last week:

The frontend server has server 1 and 2 on DESTINATIONS and using consistent hashing. There's also a nginx that only load balances requests to port 80 to the graphite web interfaces on server 1 and server 2.
Servers 1 and 2 are configured the same way: 1 carbon relay also using consistent-hashing to 3 carbon caches running on different ports and <IP_ADDRESS>.
The web apps on servers 1 and 2 are configured with DATA_DIRS pointing to the whisper and rrd paths (RRDs are not used, the path is just there). They also have CLUSTER_SERVERS set to include server 1 and 2,  and CARBONLINK_HOSTS set to the localhost carbon caches, matching the order on the relay DESTINATIONS. Each server also has a MEMCACHE_HOSTS configured with only a localhost memcached server.
Now the main problem I have is "no data" errors on both graphite-web dashboards/graphs, Grafana graphs and on nagios tests using check_graphite. Usually they only stand for a few seconds, where no data is sent (on json output, that means []), and they the data appears again, with no interruption or anything, the data is there, it's just not served.
Those are the things I have tried, based on blog posts, documentation and  github issues:

First setup used a graphite-web with CLUSTER_SERVERS configured to point to all 3 web apps (server 1, server 2 and frontend). I got a lot more missing data and weird errors. Also DATA_DIRS and CARBONLINK_HOSTS made no sense in this context for the frontend web app, but graphite would not start without them configured. Read somewhere that you have to get a carbon cache instance on the frontend that receives no data and add it to CARBONLINK_HOSTS, but that sounded a little crazy.
Tried many CLUSTER_SERVERS options, but between blog posts, issues and documentation I could not ever figure out if you are supposed to have all servers on this list, or all servers except for local host, or not to include the frontend web app.
Gave up on the frontend web app, started using nginx as a load balancer between server 1 and server 2 webapps. This worked a little better. CLUSTER_SERVERS confusion still though. Tried to have only 'the other' server on each CLUSTER_SERVERS. ATM I have both servers there.
MEMCACHE_HOSTS is another point of confusion. In #1102 @obfuscurity mentions not using memcached on backend hosts, what I tried and generated horrible load on the servers. Using the same list of memcache hosts on both servers also didn't help with the no-data issue. ATM I am running each web app with a <IP_ADDRESS> memcached.

So my question is really about clarifications and how to actually configure the cluster on the RIGHT WAY, specially if I should continue doing the nginx load balancing or to go back to a frontend web app, and in this case, what are the correct values for CLUSTER_SERVERS, DATA_DIRS and CARBONLINK_HOSTS. If someone has a working cluster and want to share some config files, I would be grateful.

Maybe these will help you if it's still relevant:
http://www.slideshare.net/AnatolijDobrosynets/graphite-cluster-setup-blueprint
https://answers.launchpad.net/graphite/+question/228472

Yes this still a problem. I will try some more fiddling this week.

Apologies for the late reply.  There is a lot of documentation work to be done, and I simply have not had time to contribute much lately.
There are a few excellent blog posts out there (sadly more of lesser quality) that I use as reference for whisper-based graphite clustering:

BitProphet's "Clustering Graphite"
Richard Crowley's "Federated Graphite"
The Architecture of Clustering Graphite

@coredump do you have any sample for the cluster configurations of carbon.conf, relay-rules.conf, local-settings.py. I've tried creating a two node graphite cluster but not successful. Here's my config looks like:
I have two machines dedicated for graphite <IP_ADDRESS> and <IP_ADDRESS> in this I wanted to use 52 as the main host.
local_settings.py
CLUSTER_SERVERS = ["<IP_ADDRESS>:80", "<IP_ADDRESS>:80"]
CARBONLINK_HOSTS = ["<IP_ADDRESS>:7002:a", "<IP_ADDRESS>:7102:b"]

carbon.conf
[cache]
GRAPHITE_STORAGE_DIR = /opt/graphite/storage/
LOCAL_DATA_DIR = /opt/graphite/storage/whisper/
LOG_DIR        = /var/log/carbon/
ENABLE_LOGROTATION = True
MAX_CACHE_SIZE = inf
MAX_UPDATES_PER_SECOND = 1000
MAX_CREATES_PER_MINUTE = 5000

LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2003

ENABLE_UDP_LISTENER = False
UDP_RECEIVER_INTERFACE = <IP_ADDRESS>
UDP_RECEIVER_PORT = 2003

PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2004

USE_INSECURE_UNPICKLER = False
CACHE_QUERY_INTERFACE = <IP_ADDRESS>
CACHE_QUERY_PORT = 7002
USE_FLOW_CONTROL = True
LOG_UPDATES = False
LOG_CACHE_HITS = False
CACHE_WRITE_STRATEGY = sorted
WHISPER_AUTOFLUSH = False

[relay]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2013
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2014

RELAY_METHOD = consistent-hashing
REPLICATION_FACTOR = 2

DESTINATIONS = <IP_ADDRESS>:2004:a, <IP_ADDRESS>:2004:b

MAX_QUEUE_SIZE = 10000
MAX_DATAPOINTS_PER_MESSAGE = 1000
QUEUE_LOW_WATERMARK_PCT = 0.8
TIME_TO_DEFER_SENDING = 0.0001
USE_FLOW_CONTROL = True
USE_RATIO_RESET=False
MIN_RESET_STAT_FLOW=1000
MIN_RESET_RATIO=0.9
MIN_RESET_INTERVAL=121

[aggregator]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
LINE_RECEIVER_PORT = 2023

PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_PORT = 2024
DESTINATIONS = <IP_ADDRESS>:2004:a, <IP_ADDRESS>:2004:b

REPLICATION_FACTOR = 1
MAX_QUEUE_SIZE = 10000
USE_FLOW_CONTROL = True
MAX_DATAPOINTS_PER_MESSAGE = 5000
MAX_AGGREGATION_INTERVALS = 5

relay-rules.con
[default]
default = true
destinations = <IP_ADDRESS>:2004:a, <IP_ADDRESS>:2004

Now when I try to test by creating a metric in <IP_ADDRESS>, the same is not replicating in <IP_ADDRESS>.
As a newbie tried and couldn't get through, requesting you to help me :-)

From your config relay is running on port 2013. But you are sending the metrics to port 2003 directly to the carbon cache process which will not replicate and store locally.
Also since you are running just one carbon-cache per node you don't have to specify :a or :b

@ashokrajar thanks for rightly pointing :-) echo "test.metric.a.count 25<PHONE_NUMBER>" | nc <IP_ADDRESS> 2013 is working very well !


Update Gatekeeper package to latest version

Feature Request
Gatekeeper is currently shipping 3.6.0
TCE is still on 3.2.3
Describe alternatives you've considered
Stay on the old version

I have an implementation for this. Working through the process as this is my first contribution.

@pksheldon4 Let me know if you need any help with the process on your contribution.

@pksheldon4 Looks like Gatekeeper has released a 3.7.0. If you're still working on an implementation would you want to update it to that? I'm hoping to get this updated for our 0.10.0 release. Still happy to help out with your PR if you need it!

@pksheldon4 Looks like Gatekeeper has released a 3.7.0. If you're still working on an implementation would you want to update it to that? I'm hoping to get this updated for our 0.10.0 release. Still happy to help out with your PR if you need it!
Thanks, upgrading should be easy enough to do.  I tried to fill out a CLA at https://cla.vmware.com/  but it doesn't seem to have an option. I need to find some dedicated time to pair with someone who's done this before.

I was trying to navigate the CLA for a vmware employee but the PR had me sign one. Not sure if that's the correct process.

@seemiller looks like we got the newer gatekeeper in. Can we close this out?

Can confirm that 3.7.0 is in the 0.9.2 package repository.
tanzu package available list gatekeeper.community.tanzu.vmware.com
/ Retrieving package versions for gatekeeper.community.tanzu.vmware.com...
  NAME                                   VERSION  RELEASED-AT
  gatekeeper.community.tanzu.vmware.com  1.0.0
  gatekeeper.community.tanzu.vmware.com  3.7.0


Add more property (ex: price) in annotation

I want to add 1 more property (ex: Price) in annotation. It will show on the annotation but i dont know how to add.

(MKAnnotationView *)mapView:(MKMapView *)mapView viewForAnnotation:(id)annotation
{
MKAnnotationView *annotationView;
if ([annotation isKindOfClass:CCHMapClusterAnnotation.class]) {
static NSString *identifier = @"clusterAnnotation";
HOMPropertyAnnotation *clusterAnnotationView = (HOMPropertyAnnotation *)[mapView dequeueReusableAnnotationViewWithIdentifier:identifier];
if (clusterAnnotationView) {
    clusterAnnotationView.annotation = annotation;
} else {
    clusterAnnotationView = [[HOMPropertyAnnotation alloc] initWithAnnotation:annotation reuseIdentifier:identifier];
    clusterAnnotationView.canShowCallout = NO;
}

CCHMapClusterAnnotation *clusterAnnotation = (CCHMapClusterAnnotation *)annotation;
clusterAnnotationView.priceValue = @"2.5 Billon";
clusterAnnotationView.count = clusterAnnotation.annotations.count;
clusterAnnotationView.blue = (clusterAnnotation.mapClusterController == self.mapClusterControllerRed);
clusterAnnotationView.uniqueLocation = clusterAnnotation.isUniqueLocation;
annotationView = clusterAnnotationView;

}
return annotationView;
}

In above mode, i added clusterAnnotationView.priceValue = @"2.5 Billon" and all annotations always show 2.5 billion. Now i want to change this value corresponding from json data  . Do i need subclass CCHMapClusterAnnotation? Pls. give some advise. Thanks.

You have to create a custom class with your property inheriting from NSObject that implements MKAnnotation. Then, add objects of this class to the cluster controller. Here is an example

Hi guys,
I want to add more attribute in MKAnnotationView not in MKAnnotation. The sample you give is adding to MKAnnotation. That attribute will replace the annotation count attribute. Is it possible ? Thanks

Add the additional property to the MKAnnotation. You will always have access to the annotation in the view as well through the annotation property.

Thanks. It works great!
But i got a new issue: The price value in Annotation and the price value when click on annotation to show Callout view, they're different. How can I fix this issue? Thanks

You probably forgot to implement mapClusterController:willReuseMapClusterAnnotation, see here

I assume you have solved your problem because I haven't heard back for a while. Please reopen if needed.

How do I refer to my custom subclass in viewForAnnotation?


Feat/schema validation

What this PR does / why we need it:
When complete, this PR will close 5081.
Special notes for your reviewer:
Very much a work in progress. Any advice is greatly appreciated.
If applicable:

[x] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

From the conversation in #2431 and in the proposal, it was agreed that utilizing JSON schema for validation was the right way forward. Would you mind looking into that?
If you're looking for inspiration, the CNAB project utilizes JSON schema validation for the application bundle schema. Here's an example of how that schema looks.

Glad to see that this already exists and doesn't need to be built from scratch. I was getting pretty deep in the weeds with some of those changes...
The last commit should now meet the basic requirements of the spec. There's still some features to be added though.

There's still some features to be added though.

Okay. Let me know when those features have been added and I'll take another look. Thanks!

The proposal mentions being able to generate a JSON schema from a given values file. However, Values are currently stored as map[string]interface{}, which means that the only information we can draw from a given property is its type. The types that we can determine are limited to what the json  library's Unmarshal uses, which means no integers. Furthermore, if a property is null, there's no way to determine its type, and it must be omitted.
This last commit adds that functionality, but given the current limitations, the schemas it generates are very bare. In practice, a user could generate a schema, then modify it with more specific information. Is this the intention for this feature?

@bacongobbler This is just about finished, but I'm not sure where to put schema generation. Do we want to add a flag to install?

Hey @ian-howell, thanks for the ping! I'll have a look at this tomorrow and see what we need to do to tie this one off. Thanks for taking the time to implement this!

This should be just about ready to merge. I've added some documentation in the last commit - let me know if it's sufficient, or if I need to add more documentation somewhere else.
Also, appveyor is failing, but it looks like that check was supposed to be removed in https://github.com/helm/helm/pull/5413. Does anyone know what's going on with that?

After talking with Adam and pondering this some more, I would suggest a couple change....

The file to use for checking the schema should be put in a $schema property in the values.yaml file. This will enable editors to do live schema checking. In some places this works today for YAML but there are requests for more of it in the future. This would provide a nice experience in editor workflows.
Why YAML for the schema file? Why not JSON? It it called JSON Schema after all. Somehow this didn't occur to me before. Why not support JSON for the schema files. This will play nicely with other JSON Schema tools (like UI builders and editor linters).

When I stopped to consider my whole experience I realized I want the schemas to be interoperable with other tools for my overall experience.
Thoughts?

@mattfarina @adamreese With regards to the YAML vs JSON issue, I have to be honest, I was just blindly following the specification in the community roadmap. I agree that it makes a lot more sense for these JSON schema files to be written in JSON. I'll be focusing my efforts on switching to that format

@mattfarina With regards to this:

The file to use for checking the schema should be put in a $schema property in the values.yaml file. This will enable editors to do live schema checking. In some places this works today for YAML but there are requests for more of it in the future. This would provide a nice experience in editor workflows.

Where would this attribute be located in the values.yaml file? I assume the top?
How should the schema file be referenced? Relative to the values file that references it? or relative to the helm chart's base directory?

Why YAML for the schema file? Why not JSON? It it called JSON Schema after all. Somehow this didn't occur to me before. Why not support JSON for the schema files. This will play nicely with other JSON Schema tools (like UI builders and editor linters).

Just my 2 cents, I think we can leave that decision up to the chart author. IIRC https://github.com/ghodss/yaml supports unmarshalling JSON as well as YAML, we could support files named values.schema.(yaml|json).

The file to use for checking the schema should be put in a $schema property in the values.yaml file. This will enable editors to do live schema checking. In some places this works today for YAML but there are requests for more of it in the future. This would provide a nice experience in editor workflows.

It looks like VS Code uses this, though note the caveat:

Adding the $schema key changes the JSON itself, which systems consuming the JSON might not expect, for example, schema validation might fail. If this is the case, you can use one of the other mapping methods.

This might affect the validation implemented here, if the schema itself does not specify that values should have a $schema property?

@ian-howell thanks for continuing to engage on the changes...

With regards to the YAML vs JSON issue, I have to be honest, I was just blindly following the specification in the community roadmap.

Well, in that case, thanks for following the directions we threw together and are now questioning. I had not realized what we'd put together back then. This might be worth talking about in the Helm Dev Call.

Where would this attribute be located in the values.yaml file? I assume the top?

As @prydonius noted, VS Code provides the ability to have the $schema root level property point to the JSON Schema. It looks like some other editors (e.g., Oxygen XML Editor, that handles JSON too - docs here) use the $schema property, too.
This all appears to be a continuation of the $schema property in JSON schemas that point to the schema for the spec being used.
Here's a list of the most popular editors as recently measured by Stack Overflow. VS Code, at the top, supports $schema. Notepad++, coming in after MS products, doesn't appear to support json schema validation at all. It looks like IntelliJ and other jetbrains editors do a manual mapping. I looked at a couple VIM plugins and it appears they do manual mapping (e.g., Vision). Sublime Text packages for schema validation, like Schema Validator work for the $schema property. Looks like Eclipse is a manual mapping to schema files. I could be wrong about these as it's just based on my reading docs and googling.
As far as I can tell, using $schema this way is not officially in the spec but it continues the idea of the $schema property in the spec and is in use via several popular editors.
We should talk more about this. I just wanted to collect some data.

How should the schema file be referenced? Relative to the values file that references it? or relative to the helm chart's base directory?

If I understand it correctly, for the $schema property to work it needs to use a URI following RFC 3986. I'd be happy to be corrected on this by someone who knows better.
I think it needs to be referenced relative to the values.yaml file for it to work.
Though, with people copying and pasting values.yaml files to other locations they will need to update these paths for them to work. The more I think about it the more I'm unsure of how to make the UX of people creating their own values.yaml files work well. Ideas or thoughts are welcome.

If I understand it correctly, for the $schema property to work it needs to use a URI following RFC 3986. I'd be happy to be corrected on this by someone who knows better.

This is correct. I tested this when initially giving this PR a spin, though I was testing that the schema of a vaules.schema.yaml file was valid, not that a values.yaml complied with a schema.

1. The file to use for checking the schema should be put in a `$schema` property in the `values.yaml` file. This will enable editors to do live schema checking.

Good point. However, that would require a few design changes in the proposal here, which would further delay this work from being merged:

We'd have to fetch the schema using the URI provided during loader.Load rather than using the schema on-disk
This proposal would remove the need for a values.schema.json entirely. I like that, but that also requires work to remove it from this PR

We should talk more about this. I just wanted to collect some data.

I'd love to talk more about this and perhaps even propose these changes here as a follow-up. However, would it be okay to merge this as-is and hash out the optimal design as a follow-up? The proposed design here solves the original use case for validating values files against JSON schemas according to the proposal laid out. While I definitely think we should take these thoughts into consideration for the design, I would prefer that we merge what @ian-howell  has worked on to get it into the first alpha release, then iterate on the design from here. That way we can gather early feedback from users trying out this new functionality and see if there are other design issues we may need to address.
What do you think about that?

Can you test when a sub-chart has validation supplied?
RootChart/
├── Chart.yaml
└── charts/
    └── SubChart
        ├── Chart.yaml
        ├── values.yaml
        └── values.schema.json

@adamreese sure, I should be able to get a unit test in by the end of the week

@adamreese Alright, this should be good to go. Let me know if there's anymore changes I need to make.

I think we can leave that decision up to the chart author. [...] we could support files named values.schema.(yaml|json).

I think this would be great. If values.schema.json exists, use that. Otherwise if values.schema.yaml exists use that. Feed both through a yaml parser and there wouldn't be any issues, JSON is valid YAML after all.
Personally, I have already written all of my JSON schema files in yaml a long time ago since that's what the specification in the community roadmap had said to do and have been using that in my CI/CD workflows. I'm sure I'm not alone.


CI Cache

This should help reduce MacOS CI times.

Ah, I guess they must have changed things on the recent release such that MacOS build times match that of Linux and Windows. Still useful for shaving ~10 seconds, probably.

I'm a code monkey so this is not my area of expertise. Thanks for keeping up with it.


3d secure confirmation page claim text

Hi!
This is my scenario.
I'm going to register a new payment methos for feature payments.
I recently introduced the 3d secure flow without webhook.
It means I use the createPaymentMethod to manage the 3ds flow.
I'd need to customize the text (or at least the app name) that is shown when you're redirect to a web view in order to confirm the card with a passcode.
The reason is that I also develop whitelabel, and I'd like to force to show the partner name in that webview, and not the main company one.

it basically means to customize the text hidden by the red stroke
Is it possible in some way?
Thanks a lot

hi @wiulma! the value that's displayed is using the statement descriptor that you set in your profile, and it's also the value that we will use when sending authorization, which later shows in the cardholder's bank statement. for reflecting the statement descriptor based on the actual merchant that the cardholder is paying for, you should consider:

setting up a dedicated stripe account for your partner
setting up a Connect account for your partner and use Connect Direct Charge or On behalf of


SIMD Friendly Math and Noise refinements to work inside SIMD loops

Introduce sfm (SIMD Friendly Math) namespace with versions of math functions friendly to use inside SIMD loops.
Introduce IntHashBasedNoise to serve as base for HashNoise & CellNoise.
Reimplemented PeriodicHashNoise and PeriodicCellNose to use an adapter to wrap their input values and reuse existing HashNoise & CellNoise implementations.
Introduce code generation policies for Perlin based based functions and Noise objects in order to resuse the same perlin noise functions with or without SIMD intrinsics.  Using a "scalar"(non-intrinsic) version of the algorithm is required when calling from inside a SIMD loop.
Defined Scalar versions of any Noise objects that used SIMD intrinsics internally.
Provide optimized inthash, sfm_simplexnoise, sfm_gabornoise implementations suitable for use inside SIMD loops.
Introduce wide.h with Block<T, int Width> to store data as structure of arrays internally, more Wide and Masked wrappers to Block be added in future.
Added osl::conjunction and osl::enable_if_type for compatibility with older C++ versions that do not have their equivalents defined in std::
Added OSL_NON_INTEL_CLANG = [0 | 1] to identify when compiler is a truely clang, as OSX still has clang defined when using Intel compiler.
Added OSL_NODISCARD
Added OSL_OMP_PRAGMA(unquoted_text) that will only be emitted when -DOSL_OPENMP_SIMD and -DNDEBUG (disabled in debug builds)
Added OSL_FORCEINLINE_BLOCK on supported compilers will recursively inline the following statement
Split common portions of gabornoise.cpp into gabornoise.h that can be shared with sfm_gabornoise.h (the SIMD friendly version of gabornoise).

[X ] I have read the contribution guidelines.
[X] I have previously submitted a Contributor License Agreement.
[X] I have updated the documentation, if applicable.
[X] I have ensured that the change is tested somewhere in the testsuite (adding new test cases if necessary).
[X] My code follows the prevailing code style of this project.

I have not forgotten about this, @AlexMWells , it's just a lot to digest.
The gist of this work LGTM, but I want to do some benchmarking on my end before merging, and also double check that nothing breaks in OptiX mode, which the CI tests do not check. I feel like I need to read through it deeply one more time, too.
After I merge, I'll take a pass at porting a lot of the SIMD-friendly versions of things in OIIO, back to OIIO, and perhaps eventually removing them from here if we are willing to live with the assumption that consumers of the SIMD OSL might be expected to have a higher version floor of OIIO than those who don't need those features.

A lot of this breaks the build when USE_OPTIX=1
I'm sure it's not rocket science to fix, but will require a pass over it. I might be able to do it, but probably not for a couple days.

Yes, the fixes build cleanly with USE_OPTIX=1 and in passes the OptiX-enabled OSL testsuite.
I will merge.

Note: as I explained before, I intend to migrate a good portion of the "sfm" functions back into OIIO fmath.h and OpenEXR's headers, and then undo some of these changes to use those versions rather than replicating that code here. It will require that people wanting full performance of the SIMD batch shading will need sufficiently new OIIO+OpenEXR, but I'm ok with that restriction.

Also passes our renderer's testsuite.

I intend to migrate a good portion of the "sfm" functions back into OIIO fmath.h and OpenEXR's headers, and then undo some of these changes to use those versions rather than replicating that code here

Yes, that is a solid plan.


Cannot compile as C library, has to be C++

There is a tiny inconvenience in OpenCL.std.h included by libspirv.h. That OpenCL header file is a C++ header file and so a client including libspirv.h cannot compile as C application, but must use a C++ compiler. (msvc complains when compiling a .c file including spirv-tools\libspirv.h)
Simply guarding the "namespace" directive with an #ifdef __cplusplus , or removing that namespace declaration, helped.

The problem is upstream.  This file comes from the SPIR-V repo, and we've been reluctant to change it locally.
Keeping the issue open for now, until it's resolved.
See also #138.

Oh, didn't see that. :)

Sorry about the problem persisting.  I've fixed our code when I closed #138, but it's still impossible to compile in C. :disappointed:
We're hesitant to diverge OpenCL.std.h because it complicates upgrading from upstream.
@antiagainst: might #170 resolve this, do you think?

It's really not a big thing for me. I simply patched my local repo version and will keep it at that.
It's not like the OpenCL.std.h is going to change frequently.
And if it is abount to change again, then maybe you guys could persuade Khronos to add a tiny little ifdef guard around it for the future? :)

Yes, we're working on having it fixed at the source.  And now that I've reviewed #170, I can confirm that it will remove all public-API dependence on upstream headers. :+1:

@dekimir: Yeah. :) Sorry for the late reply. With #170, users of libspirv.h are free of upstream SPIR-V headers.

Hi @httpdigest, #170 is merged so it should be able to compile as C library now. Thanks!

Hi @antiagainst, yes clients compile now fine using C-only. Thanks!


Enter as editor method

Store the enter function as a prototype method of squire instead of just an anonymous function in keyHandlers. This mirrors the structure of backspace, allows easier control of squire from the outside (testing, etc).

Assuming won't be controversial, gonna merge.


Feature: Add implicit layer types to MlGeoJsonLayer

and default paint props for each layer type.
@mapcomponents/react-maplibre version: v0.1.9
Feature description
Derive the layer type of MlGeoJsonLayer from the given geojson props data if props.type is not explicitly set.
POINT > "circle"
LINESTRING > "line"
POLYGON > "fill"
Example
...
Summary
...

Implicit layer types have been added in v0.1.17. https://github.com/mapcomponents/react-map-components-maplibre/commit/b7b0485b5e824b14b08d8a48a24f8aa4db87f4ed


asynctest / websocket tests

I'm trying to uplift my asynctest-based tests from py34 to py35/36.
After receiving and implementing some suggestions in https://github.com/aaugustin/websockets/issues/359, I'm seeing new issues.
I'm finding that older asynctest (prior to 0.11) are showing a problem : AttributeError: '_UnixDefaultEventLoopPolicy' object has no attribute 'reset_watcher'
Commenting out the following lines allows my tests to pass as expected:
        if not self.use_default_loop:
            self.loop.close()
            #policy.reset_watcher()
        #asyncio.set_event_loop_policy(policy.original_policy)

And newer asynctest (0.11.0 and newer) are showing another problem:
RuntimeError: Event loop is closed
Any suggestions on how to resolve ?
nostg-ott-vm-8:363> python -m unittest test_laas_async.TestVmCloudRest.test_websockets_1
E
======================================================================
ERROR: test_websockets_1 (test_laas_async.TestVmCloudRest)
Ensure reserve/create/delete/release requests are made as expected.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/ws/mdear-ott/pyatsve_36/lib/python3.6/site-packages/asynctest/case.py", line 186, in _unset_loop
    policy.reset_watcher()
AttributeError: '_UnixDefaultEventLoopPolicy' object has no attribute 'reset_watcher'

----------------------------------------------------------------------
Ran 1 test in 0.961s

FAILED (errors=1)
[pyatsve_36] nostg-ott-vm-8:364> python -m unittest test_laas_async.TestVmCloudRest.test_websockets_1
Traceback (most recent call last):
  File "/ws/mdear-ott/pyats_36/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/__main__.py", line 18, in <module>
    main(module=None)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/main.py", line 95, in __init__
    self.runTests()
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/main.py", line 256, in runTests
    self.result = testRunner.run(self.test)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/runner.py", line 176, in run
    test(result)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/suite.py", line 122, in run
    test(result)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/suite.py", line 122, in run
    test(result)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/unittest/case.py", line 653, in __call__
    return self.run(*args, **kwds)
  File "/ws/mdear-ott/pyatsve_36/lib/python3.6/site-packages/asynctest/case.py", line 302, in run
    self.loop.run_until_complete(self.doCleanups())
  File "/ws/mdear-ott/pyatsve_36/lib/python3.6/site-packages/asynctest/case.py", line 224, in wrapper
    return method(*args, **kwargs)
  File "/ws/mdear-ott/pyats_36/lib/python3.6/asyncio/base_events.py", line 443, in run_until_complete
    self._check_closed()
  File "/ws/mdear-ott/pyats_36/lib/python3.6/asyncio/base_events.py", line 357, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

Closing issue, the "event loop closed" problem was on my end.  asynctest is working for me in py35/py36 now.


Can't install with yarn?

When I do:
yarn add @formkit/auto-animate
I get:
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@formkit%2Fauto-animate/vue: Request "https://registry.yarnpkg.com/@formkit%2Fauto-animate/vue\" returned a 405".
info If you think this is a bug, please open a bug report with the information provided in "/home/qc/Projecten/solar-maps3/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Ok well now it seems to have worked


Work in progress to fix the test suite

The goal of the work which is partially done in this PR is to be able to run camaleon-cms's test suite using its repository.
To that end this PR makes the following changes:

A dummy rails application added under spec directory
Bootstrap/initialization changes so that rake invokes rspec and runs both cms and dummy app's migrations
bundle exec rspec now works too
Development dependencies added on sass-rails, jquery-rails and coffee-rails - all needed by admin assets to compile
Mailer tests are passing
Routing tests are changed to match the code and are passing
Development dependency added on selenium-webdriver for feature specs
Feature specs are running in firefox, some are passing, not all yet
#478 is required for feature specs to pass

:heart:
Building in circleci: https://circleci.com/gh/Decor-Aid/camaleon-cms/4


Seems that readJSR303Annotations(component) is not working properly with DataTable inner components

Hi,
I'm getting PropertyNotFoundException when trying to read the value of a component inside a dataTable.
Seems that when trying to evaluate the value attribute of the component when the value is relative to the var attribute of the DataTable it is not working properly and return null when calling to vex.getValue(elContext) in ELTools.evalAsObject.
This is the stack trace:
AstValue.getTarget(EvaluationContext) line: 98
AstValue.getValueReference(EvaluationContext) line: 355
ValueExpressionImpl.getValueReference(ELContext) line: 277
ELTools.evalAsObject(String) line: 93
ELTools.getField(String) line: 266
ELTools.readAnnotations(String) line: 411
ELTools.readAnnotations(UIComponent) line: 432
NGBeanAttributeInfo.readJSR303Annotations(UIComponent) line: 154
NGBeanAttributeInfo.(UIComponent) line: 63
ELTools.getBeanAttributeInfos(UIComponent) line: 166
AddTypeInformationCallback.visit(VisitContext, UIComponent) line: 35
FullVisitContext.invokeVisitCallback(UIComponent, VisitCallback) line: 106
HtmlSelectBooleanCheckbox(UIComponent).visitTree(VisitContext, VisitCallback) line: 1689
Columns(UIComponent).visitTree(VisitContext, VisitCallback) line: 1700
DataTable(OUIData).visitTree(VisitContext, VisitCallback) line: 1185
DataTable(AbstractTable).visitTree(VisitContext, VisitCallback) line: 374

Hi Dima, it's good to hear from you again! What do I have to do to reproduce your bug? Do you have a demo program I can simply download?
Thanks in advance
Stephan

It is reproducing when using in a data table the columns tag but unfortunately I wasn't able to reproduce it with PrimeFaces as wasn't able to use this tag as in the showcase (http://www.primefaces.org/showcase/ui/data/datatable/columns.xhtml). I'm currently using openfaces components and it is reproducing there with o:columns. I will keep trying to reproduce it with prime and update.

In the meanwhile it seems that the client side validation has other issues i.e. it is initializing jsf beans to try and find the jsr303 annotation of the bean members but while creating this beans they are not necessarily on the right state e.g. in my app invacation of ajax is (lazy) loading a panel and giving its bean an apropriate state (by implicitly calling some methods of it) but if this bean was created in the pre render view by the annotation scanner - it is on a wrong state what can cause an exception.

I think that I found somthing, one of the problems is that you are scanning components that are not yet rendered and this is why you force initialization of beans that shouldn't be initialized yet.
What I have found is that in PuiAngularTransformer.processEvent when you are creating the FullVisitContext at line 80 (root.visitTree) the hintsEnumSet is empty while I would expect it to have at least SKIP_UNRENDERED because on UIComponent.isVisitable the check fails if the component is not rendered but the hints has no SKIP_UNRENDERED.
What do you think?

Hi,
Did you had a chance to check regarding SKIP_UNRENDERED?

I'm sorry, your ticket was pushed aside by my eagerness to finish the BootsFaces release.
When I scanned the source code briefly, I didn't find SKIP_UNRENDERED. Is it a prefined constant of JSF?
However, I remembered something different. PrimeFaces reads annotations, too, but they used another approach that works fine with tables. I think I should examine this approach again and try to implement it in AngularFaces.

While I couldn't reproduce your bug, I found several other bugs related to data tables. Plus, I examined and implemented your proposal regarding SKIP_UNRENDERED. It's a good idea, thanks!
Please try again with AngularFaces 2.1.9, which I've uploaded to Maven Central a couple of minutes ago.
<dependency>
  <groupId>de.beyondjava</groupId>
  <artifactId>angularFaces-core</artifactId>
  <version>2.1.9</version>
</dependency>

Hi,
Thank you for the reply and fix.
I hope to test it during next week and will update when done.

Hi,
It passed this phase so I guess your fix is working - thank you!
I'm now crashing on other stuff and still unvestigating the cause of it.


Registry Scan fails on parsing URL for ECR

Description
I followed the instructions on this docs-page for adding a public ECR repository using the same repository as on the documenation.

On the Test-Registry-Connectity step it fails with failing to get `https://https/v2/". So I have a strong assumption that it's related to the url parsing.

I assume this is an operator issue, as there was no reaction on the side of Kubevuln.
Environment
OS: Windows Docker-Desktop K8s Cluster
Version:  v1.18.6 <!-- Helm Chart Version
Steps To Reproduce
Follow the instructions of the Documentation.
It should fail on the registry-test-connectivity page failing to parse.

@NeutralMindFlayer did ARMO support help you on that?

closing for lack of information


Indented code should be respected when line breaks in rendered code block

It would be really nice to have an option to activate respected code indentation when code line breaks in rendered document.
(I could also help implementing this feature but don't know how to start)
Code indentation in vs code (line 928,929) with line break on and respected indentation

Code indentation in rendered document (line 4,5) without respected indentation (goal would be to have it like in vs code above)

I agree with you, but it proves tricky, i'll have a look tomorrow.

Actually, it was surprisingly easy, completed in 2b30708


Always pulls new image regardless of setting on properties when running on Windows

Using the annotation @LocalstackDockerProperties we should be able to set "pullNewImage" to false - indeed it should be false by default.
However, I have found running this on Windows always attempts to pull a new image, regardless of the setting.
I believe this is due to the check for whether the image exists within cloud.localstack.docker.Container line 71 checks if the list of images contains the image name but does not account for Windows line endings within the ListImagesCommand.execute() method as the list is split on \n only, leaving a \r at the end of the name which is not on the expected fullImageName.
I only noticed this was the expected behaviour when I was trying to work around this issue and noticed that the option didn't work!
Steps to reproduce:

Create a JUnit class annotated with:

@LocalstackDockerProperties(
		imageTag = "0.12.11",
		pullNewImage = false,
		services = { "s3" }
)

Run the JUnit

Expected:
The log message below is not produced:
cloud.localstack.docker.Container createLocalstackContainer
INFO: Pulling latest image...

Actual:
It is.

Thanks for reporting @jmaes12345 - this should be fixed in #65 . We have just released a new version 0.2.13 to Maven Central. Please let us know if the problem persists. Thanks!

I just tried it with 0.2.13, and can confirm that it's fixed 😄
Thanks @pinzon and @whummer !


Change dependencies to non-shaded targets

Can we use as dependencies for Java examples bigtable-hbase-1.x instead of bigtable-hbase-1.1?
Based on the comment in cloud-bigtable-client:
bigtable-hbase-1.x: use for standalone applications where you are in control your dependencies.

This was done.


Language server appears to be broken

I'm sad to report that you make it very hard to use code consistently for data science. I, as MANY MANY data scientists use conda for virtual environments. This update broke the already frail intellisense we still had. If you are considering competing with jupyter notebooks for this market, please add this very simple procedure to your tests:
import pandas as pd
df = pd.DataFrame()
And verify if you still have suggestions. Do this for every release and no problems! :) As it is, specially as i update code as part of apt (own fault) I am dealing with this instead of doing my work.
Sometimes NOT updating something or going VERY slowly is the best course of action!

/extPython


Add option to disable navigation sidebar

I have a question about how to remove the left hand menu in certain pages
My API docs are in OpenAPI.
I have used redo-cli bundle to create HTML (and sed to add the front matter)
However the OpeAPI content is very wide (3 columns) and it would be very useful to switch off the left hand nav menu on this one page.
Is there some cleaver shortcode or front matter content I can use to switch this off please?
BTW, the issue is the same if you use Swagger
Originally posted by @alecthegeek in https://github.com/thegeeklab/hugo-geekdoc/discussions/122

Tested. Works for me


Major Test Cases

I'm going to build a bunch of different tests, and I need to ensure that at least each of the following is captured at least once in an automated test.
Ideally, I would like to be able to target a single test configuration or run "the entire suite" of tests.

[x] Single disk setup on machine with 1 disk (tc01)
[x] Single disk setup on a machine with multiple disks (smallest-ignore) (tc02)
[x] Multi disk setup request on machine with only 1 disk (tc03)
[x] Multi disk setup request on a machine with only 2 disks (tc04)
[x] Multi disk setup request on machine with more than 2 disks, smallest-smallest configuration respected (tc07)
[x] Multi disk setup request on machine with more than 2 disks, smallest-largest configuration respected (tc08)
[x] Multi disk setup request on machine with more than 2 disks, largest-smallest configuration respected (tc09)
[x] Multi disk setup request on machine with more than 2 disks, largest-largest configuration respected (tc10)
[x] Single disk setup with specific drive requested (/dev/sda) with no other disks (tc05)
[x] Single disk setup with specific drive requested (/dev/sda) with other disks present (tc06)
[x] UEFI installation (tc01)
[x] BIOS installation (tc02)
[x] Install Debian from Debian Live ISO (tc01)
[x] Install Ubuntu from Debian Live ISO (tc05)
[x] Test different locale (tc04)
[x] Test different timezone (tc03)
[x] Debian 'stable' edition (tc01)
[x] Debian 'testing' edition (tc03)
[x] Debian 'sid' edition (tc06)
[x] Debian 'bookworm' edition (any named edition) (tc04)
[x] Ubuntu 'lts' edition (tc07)
[x] Ubuntu 'rolling' edition (tc05)
[x] Ubuntu 'jammy' edition (any named edition) (tc08)
[x] Debian default kernel (tc01)
[x] Debian backport kernel (tc04, only verifies it attempted and ran that pathway)
[x] Debian backports kernel (tc02)
[x] Ubuntu default kernel (tc05)
[x] Ubuntu hwe kernel (tc08)
[x] Ubuntu hwe-edge kernel (tc07)
[x] Ubuntu backport kernel (tc09)
[x] Ubuntu backports kernel (tc10)
[x] Installation with overridden repo URL (tc06)
[x] Hostname default without domain (tc01)
[x] Hostname default with domain (tc02)
[x] Hostname provided without domain (tc03)
[x] Hostname provided with domain (tc04)
[x] Single disk with encryption (tc03)
[x] Single disk without encryption (tc01)
[x] Multi disk with encryption (tc04)
[x] Multi disk without encryption (tc08)
[x] Encryption using the default 'file' option (single and multi) (tc03)
[x] Encryption using provided local file option (single and multi) (tc07)
[x] Encryption using provided URL file (download) option (single and multi) (tc04)
[x] Root account disabled (only a created user) (tc03)
[x] Root account enabled (no created user) (tc02)
[x] Root account enabled with created user (tc01)
[x] Root account with provided password clear text (tc01)
[x] Root account with provided password hashed (tc04)
[x] Root account with default password, inherit from created user (tc01)
[x] Root account with default password (blank, also blank from created user) (tc05)
[x] Created user with provided password clear text (tc01)
[x] Created user with provided password hashed (tc01)
[x] Created user with default password (tc05)
[x] Created user with default username (tc05)
[x] Created user with provided username (tc01)
[x] Use data folder (tc02)
[x] Do NOT use data folder (tc01)
[x] Use the default stamp location, with data folder (/data) (tc02)
[x] Use default stamp location, without data folder (/srv) (tc01)
[x] Override stamp location, with data folder (tc03)
[x] Override stamp location, without data folder (tc04)
[x] Configuration Management (none) (tc01)
[x] Configuration Management (ansible) (tc03)
[x] Configuration Management (ansible-pip) (tc05)
[x] Configuration Management (saltstack) (tc08)
[x] Configuration Management (saltstack-repo) (tc09)
[x] Configuration Management (saltstack-bootstrap) (tc10)
[x] Configuration Management (puppet) (tc04)
[x] Configuration Management (puppet-repo) (tc07)
[x] Install with no extra packages (tc01)
[x] Install with some extra packages (tc03)
[x] Install with no extra pre-installation packages (tc01)
[x] Install with extra pre-installation packages (tc05)
[x] Install without before script (tc01)
[x] Install with before script (tc05)
[x] Install without after script (tc01)
[x] Install with after script (tc07)
[x] Install without first boot script (tc01)
[x] Install with first boot script (tc06)
[x] Install with confirm settings turned off (tc01)
[x] Install with reboot (tc01)

The goal should be to combine these to produce as few test runs as possible.

All major test cases covered


Public variables not visible in inspector

Having an issue where public variables from scripts such as Billboard.cs don't display in the inspector window, all that's visible is the title. Compiling and script functionality work as expected though.
Have tried in Unity 2017.3.1f1 and 2017.2.1f1 with no luck. Any ideas?
Unity Editor Version
2018.1.0f2
Mixed Reality Toolkit Release Version
2<IP_ADDRESS>

Yep, this one was my bad. Some fields weren't properly serialized. It's fixed for the next release, and you can grab that version here: https://github.com/Microsoft/MixedRealityToolkit-Unity/blob/may18_dev/Assets/HoloToolkit/Utilities/Scripts/Billboard.cs

Great! Thanks for the quick reply.
Just for completeness, are there other scripts where this issue is also present?

@derekfleming95 I'm not aware of any others present in the previous release, so this should be the only script you'll need to update.


701 | Insert into a Binary Search Tree | C++

Title - 701 | Insert into a Binary Search Tree | C++
What will change -
Adding a solution to this Leetcode problem.
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[x] C++
[ ] Java
[ ] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign it to me

[x] @aditsawant Assigned


Allowing for extension of BaseLoggerTarget

I was looking at your example and found BaseLoggerTarget wasn't extensible due to Swift 3's new access modifiers.  This PR uses the new open modifier.  I verified the original behavior in meschbach/swifty-logger-derived and that it's been fixed with this patch.

Yeah, you are right. For now your fix is fine, but I think that in near future I will update the rest of the classes, so they will be open as well.
Any way, thanks for checking this library and contributing. I really appreciate it.


Failed to start KMS service with java keystore provider keys and its password

In the KMS kms-site.xml we did set the  keystore path and password. The password for the generated keystore is 'password'and the same did configure as given below.
<property>
   <name>hadoop.kms.key.provider.uri</name>
<EMAIL_ADDRESS>   <description>
     URI of the backing KeyProvider for the KMS.
   </description>
</property>

<property>
    <name>hadoop.security.keystore.JavaKeyStoreProvider.password</name>
    <value>password</value>
    <description>
      If using the JavaKeyStoreProvider, the password for the keystore file.
    </description>
  </property>

Main issues:

After we set the key file with its password then we are getting key file tempered error all the time when we start the KMS service.

Kindly provide more information on how to set up keys in kms-site.xml and to configure Hadoop hdfs  (datanode & namenode settings) with nucypher kms.


FIX: Loosen validation requirements for account owner in payment-provisioning / bank-account-step

Request from client to loosen validation requirements in payment-provisioning component's bank account step
We currently have regex validations in place that restrict the account_owner field to be a string with only alphabetical characters. Clients may need to use this field to list the name of a business instead of a person.
Let's ensure we are using the same regex validation we use to validate business names for this field.

Requested by team leadership to hold off on proceeding with this one for now. ✋🏻