Absolute Sum

Before jumping into Pr first comment for assign.
Problem statement : Take an array of integers (positive or negative or both) and return the sum of the absolute value of each element.
Probelm Link :  https://edabit.com/challenge/jBFpjEG3tvsjTZbD4
Choose one Cateorgy - Easy
question category :  arrays, loop, math, number

Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py
[ ]  Choose label for Problem , example- "good first issue", "easy"
[ ]  In file there should be problem statement and link to problem

/* Problem-Task : This program will add two numbers
 * Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Hey @aayushi-droid, I would like to work on this issue, please assign this to me.

Please assign it to me

Assign to me

Please assign me this task

please assign

Please assign

Hey @aayushi-droid, I would like to work on this issue, please assign this to me.


sync deploy branch with master

This is my suggestion for how we do deploys.

Don't create any new branches.
Don't need to use command line.
The deploy branch is protected (needs PR reviews, requires linear history).
We should merge with "rebase and merge".
We should think about disabling "squash and merge", because that would introduce commits to deploy that are not part of master.
The PR reviewer checks that the base branch is master.

One thing to note: between raising the PR and merging it, master might change. So it is more difficult to pin the deployment to a specific commit this way. That can still be done via command line and raising a PR from a new branch, though.

One thing to note: between raising the PR and merging it, master might change. So it is more difficult to pin the deployment to a specific commit this way. That can still be done via command line and raising a PR from a new branch, though.

That is one of the reasons I was thinking that a no PR strategy is perhaps simpler.


shield fails requests for parameter objects that have more properties then definition

calling this telefunction
export async function myTelefunc(args: { foo: string }) {
	// code
}

with an additional property in the object will fail the request with 403
myTelefunc({ foo: "o", bar: "b"})

Not sure if I'm considering this a bug or not. It is definitely unexpected and dangerous behaviour which can cause your production build to fail unexpectedly because as far as typescript is concerned the types match and it will not give you a type error or warning if you write myTelefunc({ foo: "o", bar: "b"})

production build to fail unexpectedly

I'd argue it's a good thing: your code is doing something unexpected and should be fixed. (I actually wonder why TypeScript doesn't complain about this.)
So I'd say: it's not a bug but a feature.
But feel free to let me know if you find situations when it's actually annoying. E.g. if the error message is confusing, then that should be fixed.
Closing in the meantime.

Ah sorry for not being clear enough: It is not the building that is failing but the (deployed) production build at runtime.
The build process runs just fine, I would agree that if it fails at build time It's kinda a good thing, but failing at runtime without prior warning is dangerous.

Ah sorry for not being clear enough: It is not the build process that is failing but the (deployed) production build at runtime.
The build process runs just fine, I would agree that if it fails at build time It's kinda a good thing, but failing at runtime without prior warning is dangerous.

I agree. PR welcome to fail earlier. It may be tricky to implement though.

As mentioned in https://github.com/brillout/telefunc/issues/57 this is a massive footgun. Yesterday I had the fourth bug in production because of this behaviour.
The usecase was reading users config from localstorage and then sending it to a telefunc. Some months ago I removed a field from the config and only today found out that apparently some users still have that field in their localstorage, because those requests fail for them.
Can we reopen this issue? It is really not solved.
I think a good solution would be to have a config option that makes shields not fail on objects with obsolete fields.
My server code only operates on known fields anyway, and I bet a lot of others also.

I'm still thinking it would be better to fail earlier instead of being permissive. Because, if you want to be permissive, then you can/should use a more permissive type such as Record<string, any>.
Feel free to disagree and/or create a new feature request for it.


Support for sub_label

Is your feature request related to a problem? Please describe.
Using Frigate and Plate Recogniser. Plate Recogniser adds sub_label to recognised car licence plates, I would like to block events, when my car is recognised, by defining its licence plate in config like:¨
alerts:
  sublabels:
    block:
      - MY_PLATE_XYZ

Describe the solution you'd like
Possibility to allow/block notification based on sub_label (same functionality as with "label").
In MQTT there is attribute sub_lablel: ... "sub_label": ["MY_PLATE_XYZ", null] ..., so should be possibly easy to scrape.

Thanks for the suggestion. I'm good with adding support for this 👍

Linking the https://github.com/0x2142/frigate-notify/issues/107 here.

Just released v0.3.3 which includes this! See the docs for configuration


Build the ability for users to workaround SSO

DMPTool member organizations from universities with affiliate groups utilizing subdomains are having problems accessing the DMPTool. For example, Harvard has many affiliate hospitals with harvard.edu emails that are not covered under the Harvard SSO, such as Boston Children's Hospital (childrens.harvard.edu) and the Dana-Farber Cancer Institute ([dfci.harvard.edu). In this case, they would like to access the main Harvard University DMPTool account, which has their collective guidance, but since they aren't under Harvard SSO, the system is not giving them access.
We met with the admin for Children's and determined that a check box to manage their own credentials (overriding SSO) would be the best workaround for this. We'll build and deploy this to stage and then seek user feedback before moving to production.

We ran into a similar issue years ago when trying to manage departments within institutions.  While it didn't relate to SSO, managing a child entity within a parent institution was tricky in terms of overriding the parent institution customization with the child customization when the need arose. We ended up not supporting hierarchies due to the complexities it posed. I don't recall whether there is hierarchical support for institutions in the tool currently?  So It may be a mute point but something to consider when supporting these types of use cases.


[MNT] Add expected results for classifiers and regressors

Describe the issue
Typically we like to compare the results of our classifiers and regressors against a saved set. Some algorithms in these packages do not do this currently. This does not have to be done in a single PR.
This will most likely involve adding a "results comparison" parameter set for the estimator (i.e. this. The parameters chosen should be large enough that the results change when significant changes to the estimator are made, but small enough that the test does not clog up our CI runtime.
Suggest a potential alternative/fix
See the contents of testing/expected_results/. Run the missing estimators (not those which are non-deterministic, i.e. deep learners), using the utilities within, and add them to the expected results file.
Additional context
No response

Greetings! @MatthewMiddlehurst ,
From what i understand, We have to modify each script from testing/expected_results and make sure that the classifiers and regressors return output in the same set?
further, i tried running the script, but it returned  ModuleNotFoundError: No module named 'sklearn' (i have built Aeon using the guides given) , kindly guide me through this error.
Thank you for your time and consideration.

Yes, so for estimators which are currently missing from the relevant expected results file, add it to the results reproduction file and run it.
It seems like you do not have any dependencies installed from that error? Try reinstalling using the developer install guide. You will want to create a fork and clone from it instead if you are going to make a PR.

Thank you so much!, I will look into it.

Hi, I ran the test expected_classification_results.py there's seems to be mismatch between the expected output, and the actual output for HIVECOTEV2.
Actual Output:
HIVECOTEV2 - UnitTest
[
[0.2802, 0.7198],
[0.5851, 0.4149],
[0.1088, 0.8912],
[1.0, 0.0],
[0.9769, 0.0231],
[1.0, 0.0],
[0.7753, 0.2247],
[0.2571, 0.7429],
[0.7984, 0.2016],
[0.929, 0.071],
]
Expected Output:
[
[0.2469, 0.7531],
[0.6344, 0.3656],
[0.0959, 0.9041],
[1.0, 0.0],
[0.9796, 0.0204],
[1.0, 0.0],
[0.802, 0.198],
[0.2265, 0.7735],
[0.8224, 0.1776],
[0.9374, 0.0626],
]

It seems to be the same case for HIVECOTEV2 - BasicMotions

Would you assign me this issue? I'd like to work on it :)

If there are results present and there is a mismatch, there would be a test failure.
Are you using https://github.com/aeon-toolkit/aeon/blob/main/aeon/testing/expected_results/classifier_results_reproduction.py to generate the expected results?

If there are results present and there is a mismatch, there would be a test failure.
Are you using https://github.com/aeon-toolkit/aeon/blob/main/aeon/testing/expected_results/classifier_results_reproduction.py to generate the expected results?

Yes, I'm using classifier_results_reproduction.py, but there seems to be no test failure

I would expect https://github.com/aeon-toolkit/aeon/blob/main/aeon/classification/tests/test_all_classifiers.py#L70 to fail if so. Gave it a quick run,
if __name__ == "__main__":
    # change as required when adding new classifiers, datasets or updating results
    _print_results_for_classifier("HIVECOTEV2", "UnitTest")

gives me the expected results.

Hi, I ran the test classifier_results_reproduction.py there's seems to be mismatch between the expected output, and the actual output for HIVECOTEV2.
Actual Output:
HIVECOTEV2 - UnitTest
[
[0.2802, 0.7198],
[0.5851, 0.4149],
[0.1088, 0.8912],
[1.0, 0.0],
[0.9769, 0.0231],
[1.0, 0.0],
[0.7753, 0.2247],
[0.2571, 0.7429],
[0.7984, 0.2016],
[0.929, 0.071],
]

Expected Output:
[
[0.2469, 0.7531],
[0.6344, 0.3656],
[0.0959, 0.9041],
[1.0, 0.0],
[0.9796, 0.0204],
[1.0, 0.0],
[0.802, 0.198],
[0.2265, 0.7735],
[0.8224, 0.1776],
[0.9374, 0.0626],
]

It seems to be the same case for HIVECOTEV2 - BasicMotions

It seems that I've been using an older version of Aeon, I upgraded it and it works fine. There's no discrepancy in the results.

Classification has been updates in #1379


[Bug]: Inaccurate Error Message When Using an Async Function in a Widget Field

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The user used an async function (e.g., Query1.run()) in the Computed value of the Table widget column. The error message they received is that it is not a function, which is not accurate.

Steps To Reproduce

Add a Table widget to the canvas and populate it with data.
Use an async function (e.g., Query1.run()) in the Computed value field of a column.
Note the error message displayed.

Public Sample App
No response
Version
Self-Hosted

@ame-appsmith this is a Duplicate of #12179 so closing it in favor of that


WIP PR for Issue #1115

I rule and have completed some (emphasis on some) work on Case Manager that's ready for review!
These are my initial changes around adding tooltips to other areas of the applications. Honestly the stuff I was doing to the table contents in the index.html.erb is complete gibberish at this point. The important stuff is happening in _abortion_information.html.erb
This pull request makes the following changes:

Well there is a (?) next to the checkbox for Resolved without assistance from DCAF now, so that's a start!

(If there are changes to the views, please include a screenshot so we know what to look for!)
It relates to the following issue #s:

Fixes #1115

Codecov Report

Merging #1261 into master will decrease coverage by 0.38%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1261      +/-   ##
==========================================
- Coverage   93.52%   93.13%   -0.39%
==========================================
  Files          60       60
  Lines        1329     1341      +12
==========================================
+ Hits         1243     1249       +6
- Misses         86       92       +6

Impacted Files
Coverage Δ

app/helpers/patients_helper.rb
86.48% <50%> (-13.52%)
:arrow_down:

app/helpers/tables_helper.rb
90.9% <50%> (-9.1%)
:arrow_down:

app/helpers/events_helper.rb
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Mark as paid endpoint for premiums

Once the document is marked as paid for the year the premium date should be updated to next year,


set default values of output files in workflows

make sure that the default output filename of a pipeline is <id>.<pipeline name>.<output_arg>.<extension> and not <id>.<name of last component in pipeline>.<output_arg>.<extension>

I think this problem is solved with the update to viash 0.9.0. Closing!


chore: remove code for unsupported OS versions

This PR simplifies the code in params.pp by only taking into account the supported OS versions.
It also makes the module usable on Ubuntu 22.04, even though it's not officially supported or tested.
Related to #6

@cmhe I can confirm that with these changes the module works perfectly on Ubuntu 22.04.
/cc @bufferoverflow


PSM-393 Upgrade org.apache.maven.plugins:maven-checkstyle-plugin 3.1.0 -> 3.1.1

This PR contains the following updates:

Package
Update
Change

org.apache.maven.plugins:maven-checkstyle-plugin
patch
3.1.0 -> 3.1.1

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

Suggested commit message:
PSM-393 Upgrade maven-checkstyle-plugin 3.1.0 -> 3.1.1

See https://github.com/apache/maven-checkstyle-plugin/compare/maven-checkstyle-plugin-3.1.0...maven-checkstyle-plugin-3.1.1


Remove mkumatag as a reviewer

Removing myself from the OWNERS file as I hardly reviewed this repo in the past.

/cc @yussufsh


SVG images as Logo

SVG images for logo on Ooboarding page don't work

@drjakob Could you share a link to the SVG image you tried to use as a logo?

@drjakob sends you some now

https://www1.wdr.de/index.html

https://www1.wdr.de/resources/img/wdr/logo/wdr_logo.svg

@drjakob The logotype is white, on a transparent background. When displayed on our onboarding page on a white background, it’ll be invisible. You should use a logo variant with a non-white logo type instead.


Generate examples and use cases for autosuggest matches

What patterns do we expect auto-suggest to match?  We will lay out specific use cases and examples and use these as our method of setting up the index and evaluating the results.
https://docs.google.com/document/d/1bDJFYXrgaXg3huKwLJgt0WD7TGoUUMKY5lFsn-PYu7U/edit
To be edited collaboratively

This has a starter set of examples and will be updated/iteratively refined.  For now, this issue can be closed.


HIP11: Usage based rewards proposal

https://github.com/helium/HIP/pull/33/files?short_path=969aa80#diff-969aa8003dd731bf020c940f530e3091 rendered for readability.

Merging in, please direct future discussion to the tracking issue: https://github.com/helium/HIP/issues/34


rkj-repos theme unusable!

I really like this a lot but this is unusable. Everytime I fire the I get this
┌─[sumith@sumith-Lenovo-Z50-70] - [~] - [2015-12-16 07:35:26]
└─[0] <Mercurial Distributed SCM

basic commands:

 add           add the specified files on the next commit
 annotate      show changeset information by line for each file
 clone         make a copy of an existing repository
 commit        commit the specified files or all outstanding changes
 diff          diff repository (or selected files)
 export        dump the header and diffs for one or more changesets
 forget        forget the specified files on the next commit
 init          create a new repository in the given directory
 log           show revision history of entire repository or files
 merge         merge working directory with another revision
 pull          pull changes from the specified source
 push          push changes to the specified destination
 remove        remove the specified files on the next commit
 serve         start stand-alone webserver
 status        show changed files in the working directory
 summary       summarize working directory state
 update        update working directory (or switch revisions)

use "hg help" for the full list of commands or "hg -v" for details>

and I am not able to get out of this.
Thank you.

Your hg command doesn't have an hg prompt argument. Now, I don't use Mercurial so I don't know what alternative command there is to display a prompt, but you could just disable the Mercurial prompt function and call it a day.
To disable it put the following in your zshrc file, at the end of it:
hg_prompt_info(){}

Oh right, this theme uses the hg-prompt extension. You can either install that, or if you don't care about it disable the hg prompt as I said before.
Ultimately we're going to put in place a mercurial prompt that doesn't require hg-prompt, but as you can see here, there is quite the backlog of issues to triage and put together in a coherent state, so this may take a while to fix.
Thanks

Thanks @mcornella :)


about app/config/config.yml

I have this error:
Invalid configuration for path "lexik_workflow.processes.post_publication.steps.draft_created.model_status": You must specify a valid constant name as second parameter
Can somebody help me with this???
thanks!!!

I am having the same issue:
model_status: [ setStatus, AppBundle\Entity\Post::STATUS_DRAFT ]
My Post entity and PostModel are at proper namespace and used as well.
Can anyone answer this please?
thanks (Y)

I have been able to resolve the same, in your Post entity create const variables:
const STATUS_DRAFT = 'draft';
const STATUS_VALIDATED = 'validated';
...

Hope this will resolve your issue, the error is invalid/non-existing constant name.


Add minimalistic progressbar to display position inside of defined loop

Idea: http://usabilitypost.com/2013/08/19/new-ui-pattern-website-loading-bars/
Candidates:

http://nanobar.micronube.com/
http://ricostacruz.com/nprogress/
http://victorbjelkholm.github.io/ngProgress/
http://codepen.io/secretgspot/details/wJinh

While it was a cool idea in September 2014 we have much better UI now: https://github.com/lidel/yt-looper/pull/65 and https://github.com/lidel/yt-looper/issues/71 provided a clear indicator for  current position in big playlist while being less intrusive.


cheatsheet: sample vertex/edge with condition w/o index

ref: https://discuss.nebula-graph.com.cn/t/topic/9936/3?u=wey
provided by @jievince

https://github.com/vesoft-inc/nebula-docs-cn/pull/2342   added examples without indexes


Private AKS Cluster

Ability to create private AKS Clusters

A new variable named 'private_cluster_enabled' has been added.
It defaults to 'false' which then creates a public AKS Cluster.
User has an option to set it to 'true' and a private AKS Cluster will be created instead.

Important Docs
https://docs.microsoft.com/en-us/azure/aks/private-clusters
https://registry.terraform.io/providers/hashicorp/azurerm/2.67.0/docs/resources/kubernetes_cluster#private_cluster_enabled

Tested and looks good.

Resolved #90

Hi there,
Thanks for submitting this, I see no issue with it.
Just an FYI, we're a company and were using this module as the basis for a private TF module for internal use only. We've since stopped using this module and severed our internal module's dependency on it, resulting in this one no longer being maintained.
While you're free to use this module of course, I would steer you toward the community module as it's actively maintained and updated: https://github.com/Azure/terraform-azurerm-aks. The advantage of this module is that it's simpler to use, but probably doesn't do a lot of things that the other one does, and may stop working one day if something changes in the Terraform provider or the Azure API 😄
Anyway, I'm going to merge this shortly. I don't have time to test it but it looks simple enough that it can't break anything, and you said you tested it, so I'll just trust that.

Released in v4.3.0.


Pr/autocomplete

Added the config value from autocomplete-plus instead of 3 as min length. Not sure if there should be some if statement that provide 3 as an alternative if it cannot find atom.config.get("autocomplete-plus.minimumWordLength").

Thanks a lot for the PR!

Not sure if there should be some if statement that provide 3 as an alternative if it cannot find atom.config.get("autocomplete-plus.minimumWordLength").

That's exactly what flow on Travis complains about. You'd need to check if atom.config.get("autocomplete-plus.minimumWordLength") is a number and use 3 if that's not the case. Then everything should be green 😄

Not sure how you want this to be written, but I added  var minimumWordLength. It can be done without defining a new variable also.

@sigbjorngrini Are you interested in helping us maintain Hydrogen? I'd be really happy to add you to the nteract organization.

Thanks, I can try to look at some solutions to issues, but my js skills are very limited.


Change some more internal MTRDeviceControllerFactory APIs to use MTRDeviceController_Concrete.

These always return concrete controllers.
getRunningControllers was already claiming the right signature in the implementation, just not the header.

Fast-tracking platform-specific fix with platform owner review.


duplicacy: 3.1.0 -> 3.2.0

Description of changes

Bump package version
Add patch to bump upstream Go version to resolve build error

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 257113 run on aarch64-darwin 1

1 package built:

duplicacy

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2730

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

1 package built:

duplicacy


swap .random

With https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues

Done so, but need to find something that works in the browser:
This could work?
/* Assuming that window.crypto.getRandomValues is available */

var array = new Uint8Array(128);
self.crypto.getRandomValues(array);

console.log("Your lucky numbers:");
for (var i = 0; i < array.length; i++) {
  console.log( Math.floor(array[i]/256*10));
}

Figure out how to use crypto.getRandomValues for both node.js and browser in a nice bundle.

Skip node, just do it in the browser. Need Playwright for testing.

That was the wrong conclusion. It should work for nodejs too. It's the otp-encryption-toy that will only work on a phone.
The way to maybe do it:

Have two separate files for creating OTPs, one for NodeJS and one for the browser.
Have just one file for all the other functions.
Have two separate index.js files that includes one or the other OTP files.
Then bundle/build CJS, ESM and UMD for nodejs, and ESM and UMD for the browser.
Test them all.

Created a separate file for otp-creation, NodeJS and a separate file for index.mjs -> index-node.mjs.
Will need to change the function in otp-node.mjs to  crypto.getRandomValues(array) and make a separate one for the browser.

otp-node.mjs now based on crypto.getRandomValues

Tests will be a separate issue


Quicker delivery time is not quantified and did not provide enough motivation for all to choose the verified route

Impact: Some were less likely to select the verified route
Evidence: Some users read that their permit would take longer, yet still chose the un-verified route. For these users, delivery time was not an important factor.

This and issue #193 should be addressed at start page as part of benefits of going through the Verify route

@irinapencheva The start page already has too much content, which is why all the information about the Verify choice is introduced in it's own page.

This should be addressed by #240.


IndexError: list index out of range

Looking for someone who seen this error during conversion.
Can't replicate this issue without sample file.

Thanks.


Added bower support

Simple support to install this package via bower. The package is already in the bower registry.
This is my first try. I hope everything work as expected.
Fix #129

Thanks!

Actually, can you compare against the development branch?

Nevermind, I just committed the changes manually to the dev branch

Works?

Works great. I resubmitted it to bower's registry as simplemde to match npm's package name.

:+1:


Support for the autoStartup configuration.

The method  isAutoStartup() of SmartLifecycle is override in class AbstractMessageListenerContainer.But the variable of “autostartup” is setted to true constant. I hope it will be open for user to config because I want to controller it  myself in my project and I think it was an important configuration.
Thank you.

It's set to true by default but you can set it to false by calling setAutoStartup(false).
The code is here.

Sorry, I saw that method.But I misunderstanded it .
Thank you.
2016-08-15 20:36 GMT+08:00 Gary Russell<EMAIL_ADDRESS>
It's set to true by default but you can set it to false by calling
setAutoStartup(false).
The code is here
https://github.com/spring-projects/spring-kafka/blob/master/spring-kafka/src/main/java/org/springframework/kafka/listener/AbstractMessageListenerContainer.java#L165
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spring-projects/spring-kafka/issues/168#issuecomment-239791539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARnm9L2ny_ofpYesSxm_VkBXeHjA4dDuks5qgF1HgaJpZM4JkUu4
.


Need for adding requirements file

The execution of project will be made easier if this project has a requirements.txt file.
The need occurs because it's a big project.
I will added a file that will contain all the libraries and dependencies needed to execute the project.

Go with it!!

Go with it!!

Did you merge my PR ?


Consider changing pvlib.snow to expect precipitation in mm instead of cm

It would make a whole lot of sense for iotools functions to return rainfall in the units that pvlib.soiling expects and snowfall in the units that pvlib.snow expects.  However, those modules use different units: rainfall in mm in pvlib.soiling and snowfall in cm in pvlib.snow.  Thus we are faced with choosing the lesser of two evils: either we return multiple units from iotools or we burden the user with converting units before running models.
Discussion in #1767 showed tentative support for settling on mm for both types of precipitation and changing the expected units in pvlib.snow.  This would be a change that is not easy (or perhaps not possible) to robustly deprecate, so if we are going to make that change, I think it makes sense to squeeze it into 0.10.0.  But I'd like to see more support for this change first.

But ask me again tomorrow and I might have a different opinion. (https://github.com/pvlib/pvlib-python/pull/1767#pullrequestreview-1501412825)

@wholmgren now that it's tomorrow, has your opinion changed? ;)

Not yet 😀

I have preferred to think of iotools as functions that read data, and that return the data provided by the source, with minimal manipulation. That way, the functions are more easily re-used outside of pvlib.
I'm also not a big fan of changing units in model inputs from those in the source paper, but in some cases its necessary (e.g., snow.townsend) and it certainly is convenient, so I'm not strongly opposed to doing this.
We have added a kwarg that coerces variable names so that the returned data is easy to use inside pvlib. Not renaming would be a major pain for pvlib users, but I note that we don't rename without offering a way to prevent renaming. I don't think changing units (e.g. mm to cm) is nearly the burden that renaming can be.
If we try to keep both uses in mind for iotools functions (return data as read, and return data normalized to pvlib units), could that be controlled with a second kwarg? I would be OK with the default being pvlib_units=True

It seems to me that mapping variable names and mapping units ought to go hand in hand.  read_tmy3(..., map_variables=True) returning data with pvlib names but not pvlib units (e.g. its current behavior of pressure in mbar) seems like something that many will stumble over.
However, for the purposes of this issue, the immediate question is whether we should switch the canonical pvlib snowfall/snow depth unit from cm to mm.

It seems to me that mapping variable names and mapping units ought to go hand in hand. read_tmy3(..., map_variables=True) returning data with pvlib names but not pvlib units (e.g. its current behavior of pressure in mbar) seems like something that many will stumble over.

I like the idea of mapping both names and units to pvlib with map_variables=True

However, for the purposes of this issue, the immediate question is whether we should switch the canonical pvlib snowfall/snow depth unit from cm to mm.

I'm OK with the unit change but I'm unclear how that simplifies anyone's workflow, if snowfall data are usually in cm.

I took a quick look at vendor API docs. Solcast API docs say snow depth in cm. SolarAnywhere says snow depth in m. Solargis only has a snow-water equivalent in kg/m^2.


Json & XML Dbcodecs

Resolves https://github.com/AugustNagro/magnum/issues/27

Thanks for the review @guizmaii . It's a very interesting suggestion to use https://blog.7mind.io/no-more-orphans , I like the idea a lot.
I wonder can we merge these codecs as-is, and then experiment with adding the Optional codecs per https://blog.7mind.io/no-more-orphans in a new MR? I want to make sure I fully understand the implications.


Connecting over a local network

I discovered tty-share a couple of weeks ago and I have used its -public parameter to share it over the internet to a couple of friends so as to show them some python stuff.
However, I can not find a way to make it work over my local network. For instance, I run it on my rpi3b+ (debian 11 aarch64, tty-share 2.2.0, <IP_ADDRESS> local ip) and I get this output. Please notice that there is no extra output despite the -verbose parameter
$ tty-share -verbose
local session: http://localhost:8000/s/local/
Press Enter to continue!

Then I go to my desktop, open a browser, visit http://<IP_ADDRESS>:8000/s/local/ and I get a connection refused error! It even fails when I try connecting to it via the tty-share itself, as seen in the last gif of the readme!
$ tty-share http://<IP_ADDRESS>:8000/s/local/
Cannot connect to the remote session. Make sure the URL points to a valid tty-share session.

tty-share disconnected

The same thing applies if I run it on the desktop (debian unstable x64, tty-share 2.3.0). I run tty-share but I can not connect to it through the browser with http://<IP_ADDRESS>:8000/s/local/ but only with http://localhost:8000/s/local/, which is practically useless.
Is there something I am doing wrong? There is no such thing as a firewall anywhere.
Moreover, I would like to share my terminal without the need of tty-share.com. I have my own domain name, I have forwarded the port on my router properly, but a connection to http://mydomain.com:8000/s/local/ does not seem to work. Testing another app on the same port shows that the port is open and the app is visible on the internet as it should.

I might be experiencing the same issue
ERRO[0052] Cannot proxy the connection to the target HTTP server: dial tcp [::1]:8000: connect: connection refused

Trying it on a single machine. Linux.

Hey!
@pitsi , you are running it correctly, but without being explicit on what address to listen on that machine, it defaults to localhost, hence it will listen only for local connections. You can use the --listen flag to tell it to accept connections on any interface, e.g.: tty-share  --listen <IP_ADDRESS>:8000 and then from your other machines you can use the links you were already trying to use: http://<IP_ADDRESS>:8000/s/local/. I realize this is not obvious, so maybe I could listen to <IP_ADDRESS> by default... I'll think about it.
Also, did you check the tty-proxy - you can host that one yourself, and you would not need any settings on your router. I imagine you want access to your rpi from outside local network, and not use my tty-share.com - you can definitely do that if you host the proxy somewhere publicly accessible, and then pass to the tty-share command the address where the proxy is with the --tty-proxy flag. Unrelated, but perhaps you want to update to the latest version too - it now supports port forwarding, if you need that.
@andys8 , are you sure you're not using the--public flag? That log line you mention above makes me think that you are using a public session. Although, eve if you have that flag, it's still concerning that you get the error. Has it ever worked for you? Can you try with a different port to listen on, by using --listen :8001 for example, and see if you get the same error? Do you have a firewall that would prevent it (can you try with netcat and see if you can listen&connect to TCP sockets locally without issues)?

You are probably right about the first part. I will test it later and report back. Tbh, from all the available parameters, I only used --public and --readonly (for obvious reasons).
As for tty-proxy and the rest, I have no problem using your domain, but some people complained about lag. I was showcasing something in python, which was inside a 80*24 terminal and had no "moving parts" (e.g. cmatrix or tty-clock have "moving parts" in them).
Last but not least, I rely on what the debian repo can offer, because I do not know how to package stuff and I have no idea about docker etc, so all I can use is tty-share.


NIFI-5581: Disable connection pooling for OkHttpReplicationClient. We…

… should revisit this in the future, but for now, it appears that Jetty is having problems with the connections if they are reused. By disabling the Connection Pooling, we address the concern, but for secure connections this means that every request results in a TLS handshake - and for a mutable request, both the verification and the 'performance' stages require the TLS handshake. But it's better than timing out, which is the currently observed behavior
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Will review...


Documentation & init project correctly

@redDwarf03 you can merge whenever you are ready. I am not doing it because I don’t know if you finished or not.


[Feature]: Allow weak Password again

🏷 Feature Request Type
Other
🔖 Feature description
Since v1.10.0 no weak passwords are allowed anymore.
Please offer at least an option to allow the use of weak passwords.
✔ Solution
Having password complexity in general is fine - but hey, please offer at least an option to use weak passwords.
❓ Alternatives

📝 Additional Context
I am sure a lot people run UK in a strict local environment only, therefore a simple and easy PW is preferred.
⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

Currently I used this library to check the password.
https://check-password-strength.netlify.app/
If it is too weak, Uptime Kuma will reject it.
I found that the library isn't perfect, because some passwords like lskdfjlkshlgklhakjfhklsjfjksljlsafsdr is still too weak.
We could discuss a better solution.

Well, requirement for a "strong password" is now alphanumeric & min. 6 characters... thats not strong anyway.
Thats not strong at all 😉
Maybe I should be more specific; with weak I mean simple.
On my local monitors I use username=password; really simple stuff.
Means for example username 123, PW 123...
On all monitors that are somehow accessible by others or face the outside world I have strong username/pw + 2FA anyway...
If could switch off the requirement for login on some machines would even be easier.

I'm a fan of password strength based on entropy. This library, while doesn't seem very popular, seem to be pretty comprehensive in combining different tests.
In terms of allowing weak passwords, I thought using a password manager is already the norm these days? There really shouldn't be any excuse for a weak password just because it's easier to type.

Believe me, I am using a PW manager, but when you have dynamicly changing IPs and not use any domain names in a local network, you dont wanna fill up your PW manager with useless entries.
Thats why: allow weak or no PWs please.
All this "strong PW" talk is fine - I am not against it, but use-by-use case please - dont enforce it where it might not be required. At least offer the option to choose the password policy.

maybe consider something like that:
https://stackoverflow.com/questions/5142103/regex-to-validate-password-strength

Well, requirement for a "strong password" is now alphanumeric & min. 6 characters... thats not strong anyway. Thats not strong at all 😉
Maybe I should be more specific; with weak I mean simple. On my local monitors I use username=password; really simple stuff. Means for example username 123, PW 123...
On all monitors that are somehow accessible by others or face the outside world I have strong username/pw + 2FA anyway...
If could switch off the requirement for login on some machines would even be easier.

I would suggest something like abc123. 123 is clearly too short in my opinion.
FYI: I got CWE-521 report recently, that is why I added this.
https://cwe.mitre.org/data/definitions/521.html

Thats why: allow weak or no PWs please.

You could disable auth in the settings page btw.

Oh man... just saw this option now; I thought it had a different purpose...
Forget my request - I just disable auth.
For stronger passwords I however would still suggest to let the complexity be set by the admin.

There really shouldn't be any excuse for a weak password just because it's easier to type.

Exactly. If it really needs to be easy to type just use a passphrase rather than a password.

I'm a fan of password strength based on entropy. This library, while doesn't seem very popular, seem to be pretty comprehensive in combining different tests.

I'm not a fan of entropy-based password strength determination. It's proven that some weak passwords have high entropy. One great alternative library is zxcvbn that will - just like tai - provide quite a few details on the domain of password weakness ("phrase contained in US movie database", l33t variations, top100 password etc) but is not based on entropy but rather has been developed differently.
Some more details:

blog post: https://dropbox.tech/security/zxcvbn-realistic-password-strength-estimation
talk at USENIX Security 2016: https://www.youtube.com/watch?v=vf37jh3dV2I

It's easy to use and gives a lot of metrics to determine what you want to have. For UK I could think of simply using the "unthrottled online attack" metric (maybe a slider in the settings to set "how many days should cracking this password take at minimum". Or even simpler - setting minimum score (though this scales only from 0 to 4).
So a password abc123 would be cracked within 1.4 seconds:
{
  password: 'abc123',
  guesses: 14,
  guesses_log10: 1.1461280356782377,
  sequence: [
    {
      pattern: 'dictionary',
      i: 0,
      j: 5,
      token: 'abc123',
      matched_word: 'abc123',
      rank: 13,
      dictionary_name: 'passwords',
      reversed: false,
      l33t: false,
      base_guesses: 13,
      uppercase_variations: 1,
      l33t_variations: 1,
      guesses: 13,
      guesses_log10: 1.1139433523068367
    }
  ],
  calc_time: 4,
  crack_times_seconds: {
    online_throttling_100_per_hour: 504,
    online_no_throttling_10_per_second: 1.4,
    offline_slow_hashing_1e4_per_second: 0.0014,
    offline_fast_hashing_1e10_per_second: 1.4e-9
  },
  crack_times_display: {
    online_throttling_100_per_hour: '8 minutes',
    online_no_throttling_10_per_second: '1 second',
    offline_slow_hashing_1e4_per_second: 'less than a second',
    offline_fast_hashing_1e10_per_second: 'less than a second'
  },
  score: 0,
  feedback: {
    warning: 'This is a top-100 common password',
    suggestions: [ 'Add another word or two. Uncommon words are better.' ]
  }
}

While passphrase JohnnyCactusRainbow would take 133559128 seconds = 4 years to crack:
{
  password: 'JohnnyCactusRainbow',
  guesses:<PHONE_NUMBER>,
  guesses_log10: 9.125673574907456,
  sequence: [
    {
      pattern: 'dictionary',
      i: 0,
      j: 5,
      token: 'Johnny',
      matched_word: 'johnny',
      rank: 95,
      dictionary_name: 'male_names',
      reversed: false,
      l33t: false,
      base_guesses: 95,
      uppercase_variations: 2,
      l33t_variations: 1,
      guesses: 190,
      guesses_log10: 2.278753600952829
    },
    {
      pattern: 'dictionary',
      i: 6,
      j: 11,
      token: 'Cactus',
      matched_word: 'cactus',
      rank: 1173,
      dictionary_name: 'passwords',
      reversed: false,
      l33t: false,
      base_guesses: 1173,
      uppercase_variations: 2,
      l33t_variations: 1,
      guesses: 2346,
      guesses_log10: 3.37032800777951
    },
    {
      pattern: 'dictionary',
      i: 12,
      j: 18,
      token: 'Rainbow',
      matched_word: 'rainbow',
      rank: 231,
      dictionary_name: 'passwords',
      reversed: false,
      l33t: false,
      base_guesses: 231,
      uppercase_variations: 2,
      l33t_variations: 1,
      guesses: 462,
      guesses_log10: 2.6646419755561253
    }
  ],
  calc_time: 5,
  crack_times_seconds: {
    online_throttling_100_per_hour:<PHONE_NUMBER>0,
    online_no_throttling_10_per_second: 133559128,
    offline_slow_hashing_1e4_per_second: 133559.128,
    offline_fast_hashing_1e10_per_second: 0.133559128
  },
  crack_times_display: {
    online_throttling_100_per_hour: 'centuries',
    online_no_throttling_10_per_second: '4 years',
    offline_slow_hashing_1e4_per_second: '2 days',
    offline_fast_hashing_1e10_per_second: 'less than a second'
  },
  score: 3,
  feedback: { warning: '', suggestions: [] }
}

The above mentioned lskdfjlkshlgklhakjfhklsjfjksljlsafsdr would take centuries to crack (and just because it's all lowercase doesn't mean it's weak - it is very long and random and therefore quite secure):
{
  password: 'lskdfjlkshlgklhakjfhklsjfjksljlsafsdr',
  guesses: 1e+37,
  guesses_log10: 37,
  sequence: [
    {
      pattern: 'bruteforce',
      token: 'lskdfjlkshlgklhakjfhklsjfjksljlsafsdr',
      i: 0,
      j: 36,
      guesses: 1e+37,
      guesses_log10: 37
    }
  ],
  calc_time: 7,
  crack_times_seconds: {
    online_throttling_100_per_hour: 3.6e+38,
    online_no_throttling_10_per_second: 9.999999999999999e+35,
    offline_slow_hashing_1e4_per_second: 1e+33,
    offline_fast_hashing_1e10_per_second: 1e+27
  },
  crack_times_display: {
    online_throttling_100_per_hour: 'centuries',
    online_no_throttling_10_per_second: 'centuries',
    offline_slow_hashing_1e4_per_second: 'centuries',
    offline_fast_hashing_1e10_per_second: 'centuries'
  },
  score: 4,
  feedback: { warning: '', suggestions: [] }
}

Forget my request - I just disable auth.

No problem, I close this issue since I believe that weak password would not be accepted again.


"View logs" link from Traces doesn't show logs

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When clicking the "View Logs" link on a trace, I'd expect it to show logs assosciated with the trace, but instead it shows no results

Interestingly, if you click on the "Filter", then the field name seems to be missing

If you add in the traceid filter, then traces do show up, and the filter in the url changes from TraceId to log.traceid
https://localhost:17127/structuredlogs?filters=TraceId:equals:a348a0cfcb70b0188d38a3ba0a97a68e
https://localhost:17127/structuredlogs?filters=log.traceid:equals:a348a0cfcb70b0188d38a3ba0a97a68e
Expected Behavior
I'd expect clicking the"View Logs" link to show me all the logs associated with the trace

Steps To Reproduce
Click the "View Logs" link on a trace

Exceptions (if any)
N/A
.NET Version info
.NET SDK:
 Version:           8.0.303
 Commit:            29ab8e3268
 Workload version:  8.0.300-manifests.d7126b9e
 MSBuild version:   17.10.4+10fbfbf2e

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.303\

.NET workloads installed:
 [aspire]
   Installation Source: SDK 8.0.300, VS 17.10.35027.167
   Manifest Version:    8.1.0/8.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.1.0\WorkloadManifest.json
   Install Type:        FileBased

Host:
  Version:      8.0.7
  Architecture: x64
  Commit:       2aade6beb0

.NET SDKs installed:
  6.0.424 [C:\Program Files\dotnet\sdk]
  8.0.300-preview.24203.14 [C:\Program Files\dotnet\sdk]
  8.0.303 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Anything else?
Aspire 8.1

@JamesNK

Thanks for reporting this.
This issue is a known bug in 8.1. It's fixed in https://github.com/dotnet/aspire/pull/5023. The next version of Aspire will include this fix.

Awesome.  Thanks @JamesNK.


Fix cams

Turns out radial cameras were not tested sufficiently enough. Did a few tests on radial camera, and they actually have only one focal length.
This PR fixes this, as long as fixing the radius_cutoff function which was a total mess. I am almost ashamed of what i pushed before ! :smile:

Thanks! (No need to be ashamed; personally I believe that if every PR was polished to perfection, this would likely bind so much time that it would more or less halt progress on things that are actually important.)


Error Path String Empty

Describe the bug
I install de app and when executing this error comes out
To Reproduce
Start de app
Expected behavior
Open the app
Screenshots

Windows Version
Windows 10 build 19045

Did you change the default file path in any way?

I don't remember

Maybe check config file path in HKCU\Software\MicaForEveryone"?

I already solved it, but now the application does not load properly

And it does not allow to change, only default appears

Windows 10 is not fully supported, check #65

This should be fixed in the latest version. I close this.


Background Image options for components

First of all, I would like to thank you for this beautiful package.
As given in the demo examples and as I tried in my local system, it is not possible to have the background image for components like Divs and Page or full page Background image.
Is it suggestible to have another link stage (to load custom CSS) added by overwriting the prebuilt_html function?
Thanks in advance

happy to allow custom CSS in prebuilt_html, or you can write your own method, that part is not very complicated.

See #102.


Is there a way to automatically generate the swagger spec from the code?

I am creating an endpoint that serves the  swagger.json and I was wondering if I could generate the spec inside the code and not doing something like
swagger generate spec -o ./swagger.json --scan-models

We've chosen to keep everything required to get swagger support in the build phase and not the runtime phase.  This allowed us to come up with a solution that would work with many of the hundreds of go web frameworks to get support for swagger as opposed to blessing a few.
That being said, go-restful supports the mode of operation you're after.
https://github.com/emicklei/go-restful
https://github.com/emicklei/go-restful-openapi
It uses the same libraries we built in https://github.com/go-openapi

Thanks @casualjim


ament_cpplint gives test errors on generated message files

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
The ros2 message unit tests related to ament_cpplint fail with Category 'whitespace/line_length' errors.
Expected behavior
ament_cpplint shouldn't give line length errors for generated message files.
Actual behavior
I was trying to generate a new messages package named autoware_control_center_msgs.
https://github.com/autowarefoundation/autoware.core/actions/runs/3913282956/jobs/6688988149#step:7:926 fails.
To replicate it on my machine I ran:
colcon test --event-handlers console_cohesion+ --packages-select autoware_control_center_msgs --ctest-args -L ".*" --executor sequential --return-code-on-test-failure
And got the same result.
The following tests FAILED:
          2 - cpplint_rosidl_generated_c (Failed)
          5 - cpplint_rosidl_typesupport_fastrtps_c (Failed)
          8 - cpplint_rosidl_generated_cpp (Failed)
         11 - cpplint_rosidl_typesupport_fastrtps_cpp (Failed)
         14 - cpplint_rosidl_typesupport_introspection_c (Failed)
         17 - cpplint_rosidl_typesupport_c (Failed)
         20 - cpplint_rosidl_typesupport_introspection_cpp (Failed)
         23 - cpplint_rosidl_typesupport_cpp (Failed)
         26 - cpplint_rosidl_generated_py (Failed)

To test other packages, I tried it for already existing messages like autoware_planning_msgs or autoware_sensing_msgs and got the same test errors.
Then created a test PR on autoware_msgs to debug, they were successful.
In following PR, I tested with exactly same package, it passed the test.
https://github.com/autowarefoundation/autoware_msgs/actions/runs/3931108667/jobs/6721941355#step:7:870 is successful.
Steps to reproduce

Update your system?
colcon build --symlink-install  --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_EXPORT_COMPILE_COMMANDS=1  --packages-select  autoware_sensing_msgs
colcon test --event-handlers console_cohesion+ --packages-select autoware_sensing_msgs --ctest-args -L ".*" --executor sequential --return-code-on-test-failure

It should fail the test.
Versions

OS: Ubuntu 22.04
ROS2: humble
Autoware: Core/Universe

Possible causes
Maybe some update was made in humble message generation or ament_cpplint.
Additional context
No response

I have reproduced the bug following step 2 and step 3.
72% tests passed, 9 tests failed out of 32

Label Time Summary:
copyright     =   0.17 sec*proc (1 test)
cppcheck      =   1.55 sec*proc (9 tests)
cpplint       =   2.47 sec*proc (9 tests)
flake8        =   0.47 sec*proc (1 test)
lint_cmake    =   0.16 sec*proc (1 test)
linter        =   7.55 sec*proc (32 tests)
pep257        =   0.21 sec*proc (1 test)
uncrustify    =   1.61 sec*proc (9 tests)
xmllint       =   0.90 sec*proc (1 test)

Total Test time (real) =   7.56 sec

The following tests FAILED:
	  2 - cpplint_rosidl_generated_c (Failed)
	  5 - cpplint_rosidl_typesupport_fastrtps_c (Failed)
	  8 - cpplint_rosidl_generated_cpp (Failed)
	 11 - cpplint_rosidl_typesupport_fastrtps_cpp (Failed)
	 14 - cpplint_rosidl_typesupport_introspection_c (Failed)
	 17 - cpplint_rosidl_typesupport_c (Failed)
	 20 - cpplint_rosidl_typesupport_introspection_cpp (Failed)
	 23 - cpplint_rosidl_typesupport_cpp (Failed)
	 26 - cpplint_rosidl_generated_py (Failed)
Errors while running CTest
Output from these tests are in: /home/beyza/projects/autoware/build/autoware_sensing_msgs/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
---
--- stderr: autoware_sensing_msgs
Errors while running CTest
Output from these tests are in: /home/beyza/projects/autoware/build/autoware_sensing_msgs/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
---
Finished <<< autoware_sensing_msgs [7.72s]	[ with test failures ]

Summary: 1 package finished [8.17s]
  1 package had stderr output: autoware_sensing_msgs
  1 package had test failures: autoware_sensing_msgs

Why do you have to use ament_cpplint? If there is no specific reason, how about replacing it with pre-commit?

@kenji-miyake I don't have a specific reason, we generally use ament_lint_auto like in autoware_planning_msgs/package.xml and it's default in ros2.
  <test_depend>ament_lint_auto</test_depend>
  <test_depend>ament_lint_common</test_depend>

and
for example autoware_planning_msgs cmakelists:
find_package(ament_cmake_auto REQUIRED)
ament_auto_find_build_dependencies()

rosidl_generate_interfaces(${PROJECT_NAME}
  "msg/LaneletPrimitive.msg"
  "msg/LaneletRoute.msg"
  "msg/LaneletSegment.msg"
  "msg/PoseStampedWithUuid.msg"
  "srv/SetRoute.srv"
  DEPENDENCIES
    autoware_common_msgs
    geometry_msgs
    std_msgs
    unique_identifier_msgs
  ADD_LINTER_TESTS
)

if(BUILD_TESTING)
  find_package(ament_lint_auto REQUIRED)
  ament_lint_auto_find_test_dependencies()
endif()

ament_auto_package()

It's as easy as typing ADD_LINTER_TESTS in default rosidl_generate_interfaces cmake function.
I'm ok with replacing it too.

@xmfcx Then, let's use autoware_lint_common instead!
https://github.com/autowarefoundation/autoware_common/tree/main/autoware_lint_common

@xmfcx Then, let's use autoware_lint_common instead! https://github.com/autowarefoundation/autoware_common/tree/main/autoware_lint_common

I will try and report back today. Also I will create a PR to update existing autoware_messages too.

@kenji-miyake
Now I looked into https://github.com/tier4/tier4_ad_api_adaptor/blob/tier4/universe/autoware_external_api_msgs/CMakeLists.txt and removed the ADD_LINTER_TESTS from rosidl_generate_interfaces function. Now it passes the tests.
I think we should add this to the existing messages and also as a recommendation in the autoware_lint_common readme file.

FYI @mitsudome-r @yukkysaito @isamu-takagi.


EC2 cluster hosts with EBS volume for Archive service.

We are currently using an NVM instance store.


build: fix dependencies for the boost branch

@amc-nu could you have a look at this PR when you have a moment? We can't build the Debian packages for Autoware without these changes. Thanks!

@amc-nu thanks!


Support Python package names with no namespace or multiple namespaces

PR coming

Fixed by #44 and https://github.com/plone/cookieplone-templates/pull/86


Including multiple workdir instructions

What is the syntax to include multiple workdir instructions?
In other words, what is the pom.xml equivalent of the below dockerfile:
WORKDIR /tmp/dir1
RUN pwd
WORKDIR /tmp/dir2
RUN pwd

Multiple WORKDIRs is not currently supported if you are using the plugin to generate the Dockerfile. If you want to have multiple WORKDIRs then your best option is to use your own Dockerfile and point to it with the dockerDirectory configuration property.

The problem with multiple WORKDIRs when the plugin is generating the Dockerfile is that there would need to be a mechanism for you to tell the plugin which WORKDIR command to set before which other commands, and the proper sequence for outputting all the final commands, and simply using a regular Dockerfile is the simplest way of doing that.


org.endlessos.Key's caption length cannnot exceed 100

The flatpak org.endlessos.Key with endless-key-flatpak v0.4 builds failed on Flathub with the error:
$ flatpak run --env=G_DEBUG=fatal-criticals --command=appstream-util org.flatpak.Builder validate builddir/*/share/appdata/org.endlessos.Key.appdata.xml
 in dir /srv/buildbot/worker/build-aarch64-5/build (timeout 1200 secs)
 watching logfiles {}
 argv: b'flatpak run --env=G_DEBUG=fatal-criticals --command=appstream-util org.flatpak.Builder validate builddir/*/share/appdata/org.endlessos.Key.appdata.xml'
 using PTY: False
builddir/files/share/appdata/org.endlessos.Key.appdata.xml: FAILED:
• style-invalid         : <caption> is too long [3. Resources such as finance, healthy body, TED Ed, sports, games, arts & crafts, gardening, and more];longest allowed is 100 chars
Validation of files failed

https://buildbot.flathub.org/#/builders/42/builds/5938

Verified passed as v0.5 is ready for download and tested.


Fix protocol-relative URLs in Url::to() (#13156)

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#13156

Fix #13156.

@samdark This bug is not released, it is related to #13067.

Thank you!~


ps -a

Output of docker version:
(paste your output here)

Output of docker info:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):

guess this was opened by mistake, so I'll close


Consistent stack traces

My problem is that if my Error is not created in the context of the generator, the stack trace is missing:
var co = require('co');

function* a() {
  yield* b();
}

function* b() {
  yield new Promise(function(resolve, reject) {
    setTimeout(function() {
      reject(new Error());
    }, 1000);
  });
}

co(function* () {
  try {
    yield* a();
  } catch(err) {
    console.error(err.stack);
  }
});

Error
    at null._onTimeout (...)
    at Timer.listOnTimeout (...)

Stack trace is just fine, if I throw in the generator:
var co = require('co');

function* a() {
  yield* b();
}

function* b() {
  yield new Promise(function(resolve, reject) {
    setTimeout(function() {
      resolve();
    }, 1000);
  });
  throw new Error();
}

co(function* () {
  try {
    yield* a();
  } catch(err) {
    console.error(err.stack);
  }
});

Error
    at b (...)
    at GeneratorFunctionPrototype.next (...)
    at a (...)
    at GeneratorFunctionPrototype.next (...)
    at ...
    at GeneratorFunctionPrototype.next (...)
    at onFulfilled (...)

I perfectly understand that this is the correct behavior (the setTimeouts callback has absolutely no idea that the computation was suspended), but it is really annoying. Is there any other way to fix this other than wrapping every Promise in a try-catch, and wrapping the original Error with a new one?
try {
  yield new Promise(function(resolve, reject) {
    setTimeout(function() {
      reject(new Error())
    }, 1000);
  });
} catch(e) {
  var err = new Error(e.message);
  err.original = e;
  throw err;
}

PR welcomed, but i'm not a big fan of manipulating stack traces

@jonathanong the problem is not that they are not readable, they are completely missing if they are not created in the right place (see my first example). Touching stack traces is obviously a no-go, I just want to know if there is a better workaround than the one I've presented (catching and rethrowing errors). I guess co itself cannot really do anything with that, but maybe there are cleaner workarounds to avoid losing stack traces.

oh sorry. no idea.

It needs support from the promise implementation you are using, for example:
var Promise = require("bluebird");
var co = require("co");
Promise.longStackTraces();

function* a() {
  yield* b();
}

function* b() {
  yield new Promise(function(resolve, reject) {
    setTimeout(function() {
      reject(new Error());
    }, 1000);
  });
}

co(function* () {
  try {
    yield* a();
  } catch(err) {
    console.error(err.stack);
  }
});

Gives:
Error
    at null._onTimeout (test.js:12:14)
    at Timer.listOnTimeout (timers.js:90:15)
From previous event:
    at b (test.js:10:9)
    at GeneratorFunctionPrototype.next (native)
    at a (test.js:6:10)
    at GeneratorFunctionPrototype.next (native)
    at test.js:19:12
    at GeneratorFunctionPrototype.next (native)
    at onFulfilled (\node_modules\co\index.js:59:19)
    at \node_modules\co\index.js:48:5
    at co (\node_modules\co\index.js:47:10)
    at Object.<anonymous> (test.js:17:1)
    at Module._compile (module.js:446:26)
    at Object.Module._extensions..js (module.js:464:10)
    at Module.load (module.js:341:32)
    at Function.Module._load (module.js:296:12)
    at Function.Module.runMain (module.js:487:10)
    at startup (node.js:111:16)
    at node.js:809:3

Of course if you do that then you might as well do yield Promise.delay(1000) or even var co = Promise.coroutine

So it can't be solved without touching the stack trace :disappointed:...
bluebird is definitely useful for development, thanks :+1:.

So it can't be solved without touching the stack trace

Sure but why does it matter to you? Someone is going to have to create a stack trace somewhere, whether that's V8 or some custom library doesn't make a difference.

It has a huge performance impact afaik, and there should be meaningful stack traces in prod too.

If V8 provided those long stack traces there would be exactly the same performance impact, that's what I mean by platform not being magical - the same logic runs through your CPU.
Also if you were using native promises then using bluebird has no performance impact as it performs same as native promises when long stack traces are enabled, or 5-10x faster when they're disabled.

Wow, I thought that long stack traces are much more slower than the native implementation. Thanks for the info :+1: !

I have implement  stacktrace in zco , To be honest, it's a really expensive operation,but acceptable.


Implemented database reconnection loop

closes #1407
This PR adds automatic reconnection to the Postgres/MySQL database with 1-second interval if connection was not established instead of exit(1)

Hello @an-tao
Could you please review this PR. Please feel free to suggest improvements.

Thanks for the PR!
Could you put the init() methods right after the constructor? That really helps the code review.

Thanks for the PR! Could you put the init() methods right after the constructor? That really helps the code review.

Done!

My latest update failed test:
In test case PgPipelineTest
/home/admin/arenadata_drogon/drogon/orm_lib/tests/pipeline_test.cpp:37  FAILED:
  Reason: PgPipelineTest_init(0) what():SQL execution timeout

I just reproduced the issue on my personal PC. I'm going to investigate this failure on Monday.

closes #1407
This PR adds automatic reconnection to the Postgres/MySQL database with 1-second interval if connection was not established instead of exit(1)

To be noted, auto-reconnect is already supported. This exit(-1) happens on some edge cases, such as reaching open socket limits.

To be noted, auto-reconnect is already supported. This exit(-1) happens on some edge cases, such as reaching open socket limits.

From wiki

The connections managed by DbClient are always reconnected, so users don't need to care about the connection status. They are almost always connected.

The problem is not with "some edge cases" because simple drop of connection to PostgreSQL for few seconds makes the whole Drogon's application exit(-1).

The issue with PgPipelineTest should be fixed now.

One more update:

Added connection initialization to make db_listener_test test pass.

I'm not familiar with the internal Drogon tests. Do you have a guide how I can prepare the test environment on my PC and run all Drogon tests before updating PR?

One more update:

Added connection initialization to make db_listener_test test pass.

I'm not familiar with the internal Drogon tests. Do you have a guide how I can prepare the test environment on my PC and run all Drogon tests before updating PR?

You could refer to the github actions configuration: https://github.com/drogonframework/drogon/tree/master/.github/workflows


Update slf4j-simple to 1.7.31

Updates org.slf4j:slf4j-simple from 1.7.25 to 1.7.31.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.slf4j", artifactId = "slf4j-simple" } ]

labels: library-update, semver-patch

Superseded by #27.


Fix cleanvm merging to non-Staging

Looks good to me. Though I am not really able to give a ±1 here as I lack some more detailed jenkins knowledge.

Looks like the project is not sent to the triggered job: https://ci.opensuse.org/view/OpenStack/job/openstack-submit/3/

+1

+1


Steam does not have the "skins" folder on MacOS?

MacOS does not have the skins folder in this path anymore: ~/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/skins.
Basically the whole path is valid except the last folder.
I tried adding it and then do the rest of the instructions. This however did not work

This should migrate to dracula/steam (or whatever the appropriate repo name is).

Hi @bit-burger, this is a question to open in the Steam theme repository so that the project maintainers can help you with your doubt. 😊 You can do this by clicking here.
So I will close this issue! 😅


Update Feature/Improve gathering with more parameters

Added ability to require an item either in the players hands or just in their inventory in order to gather. Also added the ability to gather multiple from one interaction instead of always just one.

It may be better to assign your local variables as member variables in the class. (see what others think) Also on line 67 you create and assign a local var playerController but it is never used....
Other than that I don't see anything inherently wrong.

Went ahead and removed that unnecessary line and changed the variable to match the member variables case. Thanks!

Changed messages when unavailable so they are more informative.
Also changed default value to 1 for amount given to prevent confusion on it being 0.


fix: batch embedding queries, fix get client in tests

Closes #2905
Batch requests for aws bedrock embeddings

Awesome, thank you!


Integration with Leptos

Good morning. I was thinking to develop a charting web application using Leptos+Vello (For the charting rendering and interaction).
I saw from the examples that it's possible to attach a rendering scene to an HTML canvas element which is created starting from the window struct.
Do you think that it's a feasible integration? I'm afraid the re-rendering system of Leptos could clash with some of the rendering lifecycles of Vello.
Thanks!

I cannot comment on the feasibility of using Vello for rendering charts in Leptos. However, I happen to just have developed a web application in Leptos that included chart rendering. For the current implementation, I resorted to almost raw HTML5 canvas rendering with the Context2D API via web-sys, and my own thin abstraction on top of it. I cannot share the source code, but I hope that little hint helps a bit at least.


route alias is added with amp = false

The module adds an alias to each route which has no /amp in its path. This behaviour should not happen if the page does not serve an amp version

Hi
This should be fixed in version 0.2.1
Note: In sake of performance and simplicity aliases must add to all pages, but after version 0.2.1 module checks state of the page, if AMP is disabled for a path it client get 404


Building the plugin itself should not publish to maven local before testing

Acceptance criteria:

make all test case projects consistent in how the load the plugin
do not publish to maven local before test step. Instead, publish to a local directory

also see the references to this issue in the code while fixing


[GOBBLIN-1583] Add System level job start SLA

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1583

Description

[x] Here are some details about my PR, including screenshots (if applicable):
Use a GaaS-wide configuration to set the Job Start SLA time, so that each flow does not need to manually set their SLAs.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3437 (63fd9c7) into master (a7df7ca) will decrease coverage by 3.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3437      +/-   ##
============================================
- Coverage     46.58%   43.42%   -3.17%
+ Complexity    10331     2028    -8303
============================================
  Files          2074      404    -1670
  Lines         80880    17349   -63531
  Branches       9022     2120    -6902
============================================
- Hits          37680     7534   -30146
+ Misses        39728     8980   -30748
+ Partials       3472      835    -2637

Impacted Files
Coverage Δ

...a/org/apache/gobblin/util/limiter/NoopLimiter.java
40.00% <0.00%> (-20.00%)
:arrow_down:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0.00%> (-7.15%)
:arrow_down:

...blin/service/modules/orchestration/DagManager.java

...service/modules/orchestration/DagManagerUtils.java

...he/gobblin/service/LocalGroupOwnershipService.java

...e/gobblin/runtime/local/LocalTaskStateTracker.java

...alitychecker/task/TaskLevelPolicyCheckResults.java

...rvice/modules/flowgraph/datanodes/SqlDataNode.java

...r/filebased/SizeAwareFileBasedHelperDecorator.java

...org/apache/gobblin/writer/PartitionIdentifier.java

... and 1663 more

Continue to review full report at Codecov.

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

@phet the configuration key for DEFAULT_ is a global fallback, if the key isn't configured

@phet Yes I can have a setting to also configure the timeunit in that case, that would make sense.
This is for configuring the default (the flows themselves are allowed to overwrite this value) so we need to perform conversion for all flows in the ctor of the DagManagerThread


Tutorial Sample not working : TypeError: argument of type 'float' is not iterable

Running the python code with the following syntax
python wide_n_deep_tutorial.py --model_type=wide_n_deep
Produces the below error
` python wide_n_deep_tutorial.py --model_type=wide_n_deep
Training data is downloaded to /tmp/tmpMD6Clq
Test data is downloaded to /tmp/tmpfG7CwC
Traceback (most recent call last):
File "wide_n_deep_tutorial.py", line 210, in
tf.app.run()
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 30, in run
sys.exit(main(sys.argv))
File "wide_n_deep_tutorial.py", line 206, in main
train_and_eval()
File "wide_n_deep_tutorial.py", line 192, in train_and_eval
df_train[LABEL_COLUMN] = (df_train['income_bracket'].apply(lambda x: '>50K' in x)).astype(int)
File "/usr/lib/python2.7/dist-packages/pandas/core/series.py", line 2023, in apply
mapped = lib.map_infer(values, f, convert=convert_dtype)
File "inference.pyx", line 920, in pandas.lib.map_infer (pandas/lib.c:44780)
File "wide_n_deep_tutorial.py", line 192, in
df_train[LABEL_COLUMN] = (df_train['income_bracket'].apply(lambda x: '>50K' in x)).astype(int)
TypeError: argument of type 'float' is not iterable'

Please can you provide the information requested in the TensorFLow issues template.- namely installation method, OS/ packages versions and full repro instructions.

is there any progress?

Environment info
Operating System:
>>> 14.04.4 LTS (GNU/Linux 3.13.0-91-generic x86_64)
Installed version of CUDA and cuDNN: (please attach the output of ls -l /path/to/cuda/lib/libcud*):
Cuda is not installed
>>> ls: cannot access /path/to/cuda/lib/libcud: No such file or directory*
If installed from binary pip package, provide:
A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.version)".
If installed from source, provide
>>> 0.10.0rc0
The commit hash (git rev-parse HEAD)
The output of bazel version
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
>>>python wide_n_deep_tutorial.py --model_type=wide_n_deep
What other attempted solutions have you tried?
Test data is downloaded to /tmp/tmpmM0UO0
Traceback (most recent call last):
  File "wide_n_deep_tutorial.py", line 212, in <module>
    tf.app.run()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 30, in run
    sys.exit(main(sys.argv))
  File "wide_n_deep_tutorial.py", line 208, in main
    train_and_eval()
  File "wide_n_deep_tutorial.py", line 193, in train_and_eval
    df_train["income_bracket"].apply(lambda x: ">50K" in x)).astype(int)
  File "/usr/lib/python2.7/dist-packages/pandas/core/series.py", line 2023, in apply
    mapped = lib.map_infer(values, f, convert=convert_dtype)
  File "inference.pyx", line 920, in pandas.lib.map_infer (pandas/lib.c:44780)
  File "wide_n_deep_tutorial.py", line 193, in <lambda>
    df_train["income_bracket"].apply(lambda x: ">50K" in x)).astype(int)
TypeError: argument of type 'float' is not iterable

Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

Amazon ec2 compute optimized servers do not use nvidia gpus, I havent had much luck getting cuda working on ec2 large g4 instance.

python wide_n_deep_tutorial.py --model_type=wide
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
Training data is downloaded to /tmp/tmp2NRlQI
Test data is downloaded to /tmp/tmp1b0NGh
Traceback (most recent call last):
File "wide_n_deep_tutorial.py", line 212, in
tf.app.run()
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 30, in run
sys.exit(main(sys.argv))
File "wide_n_deep_tutorial.py", line 208, in main
train_and_eval()
File "wide_n_deep_tutorial.py", line 193, in train_and_eval
df_train["income_bracket"].apply(lambda x: ">50K" in x)).astype(int)
File "/usr/lib/python2.7/dist-packages/pandas/core/series.py", line 2023, in apply
mapped = lib.map_infer(values, f, convert=convert_dtype)
File "inference.pyx", line 920, in pandas.lib.map_infer (pandas/lib.c:44780)
File "wide_n_deep_tutorial.py", line 193, in
df_train["income_bracket"].apply(lambda x: ">50K" in x)).astype(int)
TypeError: argument of type 'float' is not iterable

I tried the version 0.8.0 and 0.10.0 of tensorflow

I find the reason, it is because of the data file's format. there is the empty line at the end of file, just delete it

I tried using the wide_n_deep_tutorial code on my personal data set. I am uploading my data file and the test file from AWS S3 and I have ensured that my data does not have an additional spaces at the end.
However, I am still getting the same error message.

Any help would be appreciated.

vasantivmahajan - did you figure out the issue? I have exactly the same problem.

since my previous comment, I have changed the classification/label data from a number (1/0) to string data (win/lose) and this has resolved this problem

Awesome, I will check it out
On Sat, Sep 24, 2016 at 12:06 PM, simon789<EMAIL_ADDRESS>wrote:

since my previous comment, I have changed the classification/label data
from a number (1/0) to string data (win/lose) and this has resolved this
problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/3919#issuecomment-249381771,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFn-MJkRm9xG20qbTXGeLJgMUS7R-ZSHks5qtXSygaJpZM4JoOSv
.

--
Regards
Chandan Maruthi

Hey,
Thank you for your response, I really appreciate it. I was able to resolve
that issue. However, while running the program I am getting another error
"TypeError: Signature mismatch. Keys must be dtype <dtype: 'string'>, got
dtype:'int64'"
http://stackoverflow.com/questions/39730528/typeerror-signature-mismatch-keys-must-be-dtype-dtype-string-got-dtype
Did you receive this error during your execution or do you know what could
be the reason for it?
Warm Regards,
Vasanti Mahajan
On Sat, Sep 24, 2016 at 3:06 PM, simon789<EMAIL_ADDRESS>wrote:

since my previous comment, I have changed the classification/label data
from a number (1/0) to string data (win/lose) and this has resolved this
problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/3919#issuecomment-249381771,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARKEuDnMO-8fCUfDQdhQ601JkfCR2oN7ks5qtXSygaJpZM4JoOSv
.

vasantivmahajan - I have taken a guess and posted it at the original link.

one other thing...once I corrected my script I had to delete the model directory as it had been corrupted by the early termination of the programme. If you dont, you may get another error message.

@chandanmaruthi : Yeah, it seems the blank lines at the end are a problem.
@hengtze : Does it make sense to update wide_n_deep_tutorial.py  to discard trailing blank lines before parsing it? Ideally we would be able to use skip_blank_lines, but that seems to exist only in newer versions of panda, while Ubuntu 14.04 seems to use pandas 0.13, which doesn't have that. So we can either use skip_footer or explicitly trim empty lines after downloading.

Is this still broken?

Closing due to inactivity. Feel free to re-open if you would like us to look again.

def input_fn(data_file, num_epochs, shuffle):
"""Input builder function."""
df_data = pd.read_csv(
tf.gfile.Open(data_file),
names=CSV_COLUMNS,
skipinitialspace=True,
engine="python",
skiprows=1)
remove NaN elements
df_data = df_data.dropna(how="any", axis=0)
labels = df_data["disease"].apply(lambda x: "no" in x).astype(str)
return tf.estimator.inputs.pandas_input_fn(
x=df_data,
y=labels,
batch_size=10,
num_epochs=num_epochs,
shuffle=shuffle,
num_threads=2)
I'm getting the following error for above code
UnimplementedError (see above for traceback): Cast string to float is not supported
[[Node: linear/head/ToFloat = CastDstT=DT_FLOAT, SrcT=DT_STRING, _device="/job:localhost/replica:0/task:0/cpu:0"]]
Can some one help to resolve it


added signature visualization with images

Hi, I added the option to set an image to the pdf signature. If you add the "signature_img" field with a path to an image in the dict for the cms signature, it will use it to display the signature.
All tests are ok and I have checked the pdf generated with
https://www.pdf-online.com/osa/validate.aspx
Everything seems fine, but since this is my first experience with the iso pdf format, if you want to take a look at the code, I will appreciate it.
Let me know.

Great, thank you.
Can you make the picture act like a button?
I don't mind such behavior, but it would be nice ...

yes sure, it was already there. Only a little typo in the code.
If you want I can also improve this feature, maybe allowing an automatic size scaling based on the image ratio. Or a more general code to integrate other kind of annotations (actually the current code is already generic and makes it possible to implement other annotations quickly). Let me know how mutch can I go deep in the code :)

Thank you for your input, I watched and did not see this typo.
Everyone can make changes but I would like this library to be as simple as possible ;)

the typo has been fixed in this commit
https://github.com/m32/endesive/pull/33/commits/706be86479f2d7335ea5cd7800034980db087d2f
:)


Node.js  Loaders Team Meeting 2024-01-30

Time
UTC Tue 30-Jan-2024 19:00 (07:00 PM):

Timezone
Date/Time

US / Pacific
Tue 30-Jan-2024 11:00 (11:00 AM)

US / Mountain
Tue 30-Jan-2024 12:00 (12:00 PM)

US / Central
Tue 30-Jan-2024 13:00 (01:00 PM)

US / Eastern
Tue 30-Jan-2024 14:00 (02:00 PM)

EU / Western
Tue 30-Jan-2024 19:00 (07:00 PM)

EU / Central
Tue 30-Jan-2024 20:00 (08:00 PM)

EU / Eastern
Tue 30-Jan-2024 21:00 (09:00 PM)

Moscow
Tue 30-Jan-2024 22:00 (10:00 PM)

Chennai
Wed 31-Jan-2024 00:30 (12:30 AM)

Hangzhou
Wed 31-Jan-2024 03:00 (03:00 AM)

Tokyo
Wed 31-Jan-2024 04:00 (04:00 AM)

Sydney
Wed 31-Jan-2024 06:00 (06:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders Team+Meeting+2024-01-30&iso=20240130T1900
or https://www.wolframalpha.com/input/?i=07PM+UTC%2C+Jan+30%2C+2024+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1nUlL3q-Ua-LQIqrdOIGAGPqpn36jO_EnCpkpY8xbc0Q/edit

Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

ESM Hook deadlocks since 21.2.0 a3e09b3 #50948

Invited

Loaders team: @nodejs/loaders

Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/97506450082

For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

I still need help with https://github.com/nodejs/node/pull/50752 if anyone wants to give it a shot. I think it'll close the issue reported above and it'll mean we can take the overall API stable.

Anyone want to meet?

Ack, sorry. I can't this week. Possibly next time


fix: prevent yarn directory traversal on plugin installation

fixes #4041 (and possibly others)
Yarn would previously traverse up the directory tree looking for a workspace package.json.
This PR prevents this behavior by writing a dummy package.json so yarn stops looking.
Solves errors that occur when a package.json exists in a parent directory (such as the user home directory or the root directory). Even when those errors don't occur, this may speed up execution very slightly by making fewer disk calls.

 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.

@gatzjames  any reason in particular this was closed?
I still have people reporting an inability to install my plugin because of the underlying issue this PR fixes.
For another recent example from a repo that isn't mine, see https://github.com/jreyesr/insomnia-plugin-batch-requests/issues/17


Parameterize regex patterns for some entity field annotations

The PersonPojo class has two properties phone1 and phone2 that are annotated with a @Pattern. This means that whenever they have a value and are triggered for validation, they try to match specifically against this regex:
^(((\\(\\+?[0-9]{3}\\))|(\\+?[0-9]{3})) ?)?[0-9]{3,4}[ -]?[0-9]{4}$
which may not be compatible with all phone numbers; I originally made it for numbers originating from Chile.
But most importantly, it is hard-coded.
Proposal

All regex pattern that are used in annotations must be parameterized. If possible, using properties files.
Additionally, the default regex could be improved to accept many more phone numbers formats/international support. Maybe such one regex exists and is somewhere to be found?

Apparently, values used in annotations cannot be changed in runtime since they are compiled with the class, just like fields or methods. So Java Reflection can achieve a dynamic change.
https://stackoverflow.com/questions/14268981/modify-a-class-definitions-annotation-string-parameter-at-runtime
But there's also another risk; regexes also need to be compiled before testing them against any strings.
Does the implementation behind @Pattern compiles the regex and then reuses it (probably)? Or does it compile a new one every time it has to validate the value (unlikely)?


Why the ISqlCollection interface was created?

The interface was created so that the consumer does not know about the internal details of the library.
What internal details?
How SQL statements are stored or what data structures are used, are details that the consumer does not need to know.
These details can be changed without having to break the consumer code. That is the advantage.
This also follows the concept of abstraction: expose only the details relevant to the consumer and hide the implementation details that don't matter to them.


PR: Fix error when updating animations

Fixes https://github.com/spyder-ide/qtawesome/issues/76

This looks good! Thanks a lot for your contribution.


Structure of DukeMTMC-VideoReID

Hello!
I would like to transform a dataset after the DukeMTMC-VideoReID structure used in this project and to just plug it in. However, it seems that the structure of Duke used in this project is not the same as https://github.com/Yu-Wu/DukeMTMC-VideoReID. Could you provide more details on how you structured the Duke dataset before giving it to the network?
Thank you!

Hey @MerceaOtniel
The DukeMTMC-VideoReID is structured as follows:
split (either train, gallery or query)
-> person folder (e.g. 7140)
----> acquisition number (e.g. 2193, more than one per person)
--------> images (e.g. 7140_C2_F0044_X200413.jpg, more than one per acquisition)
You can take a look here to see how we process it. We hash based on person_id+camera to combine frames from the same sequence.
Let me know if you have further questions :)


Restore data from dump command

Currently there is a ./gogs dump command that will generate a backup, but no way to automatically restore back.
As referenced here: https://discuss.gogs.io/t/suggestion-on-repository-load-balancing-and-replication-hot-backup-strategy/182/8

#648

Closing as duplicate of #648
Also see PR #3109


DEV: adding a concept of prompt builder

This is half baked and not working, but starts demonstrating the idea

nothing to merge here, this is all very wip atm.


The performance has regressed

After below PR is merged, the performance is slower than before.
commit f1512bded1934e34f104bf1ac8547e97e24b2fe8 (HEAD -> main)
Author: goostavz<EMAIL_ADDRESS>Date:   Mon Aug 7 09:53:04 2023 +0800

    Initial code merge of Hopper support (#2036)

    The initial code merge of Nvidia Hopper features support. Please be
    aware that the code merge is not finished yet and the trouble-shooting
    is still ongoing. The new hardware features (GMMA, TMA, STMATRIX etc.)
    and automatic warp-specialization are experimental for now and turned
    off by default. It is recommended for a trial when version 3.0 is
    released.

    The work is contributed by:
    ben-zhang-609, bealwang, donproc, qliu93, jsh20, allatit23, LyricZhao,
    ivanyinwz, goostavz & yangjunpro
    from Nvidia, in cooperation with:
    ptillet, Jokeren, ThomasRaoux & zahimoud
    from OpenAI.

    Co-authored-by: Goostav Zhu<EMAIL_ADDRESS>
Before:

After:

Which kernels are your referring to?

Hello @Jokeren
The performance of kernels in Trident has regressed and I have tested on A100.
Trident has benchmarks you can easily check it.

git clone https://github.com/kakaobrain/trident.git
cd trident
export PYTHONPATH=${PYTHONPATH}:${pwd}
python3 benchmarks/benchmarker.py --scenario group-norm --show-plots

You can check available benchmark cases with python3 benchmarks/benchmarker.py --list
Thanks!

@Jokeren Not Only this kernel, many many kernel slower.

@Jokeren
this is a opensource llm inference repo based triton.
https://github.com/ModelTC/lightllm.
recently, When use triton==2.1.0 latest code, the performance degradation.
one step decode latency:  64.7115707397461ms ----><PHONE_NUMBER>9313965ms  in a 8 * A800 80G env.

@daemyung I have a theory about what's going on with your code. Will investigate it.

@daemyung please use the following script for benchmarking
    stream = torch.cuda.Stream()
    torch.cuda.set_stream(stream)
    triton.testing.do_bench(...)

There's nothing changed in binary with regard to your group norm kernels.

@Jokeren Thank. The performance is fine now. Should I set up a stream even if it's not a benchmark?

There's nothing different in GPU kernels, at least for your use cases.
We've observed overhead on the CPU side, which will be addressed by this PR.
But for more accurate timing, it's probably better to use cudagraph in the future.

@Jokeren Thanks! BTW PR link is broken. Can you share a valid link?

Corrected, I don't know what I was doing... https://github.com/openai/triton/pull/2094


Is it possible to use it with Dynamic images from Ajax request?

I am not sure if this works with Ajax requests images, i cant manage to get it working yet. Wondering if you can give me a heads up on how to get it working, or if it would be able to perform what i need.
I am trying to loop through a list of images pulled from Ajax request from my server. But it is not working at all.
for(var j = 0; j<images.length; j++){
var image3=  "http://test.info/test/"+images[0];
console.log(image3);
var image2= "
}

This should work, can you add a fiddle?

Yup, i will try to add a fiddle in a bit. But when i do data-src= 'image' it doesnt seem to work, it will only load the image when its src=. Not sure why

The image should load, if
a) there is a lazyload class
b) it has a data-src
c) it is in viewport and is visible.

Please re-open, if you still have problems.
In case you have. A testcase demonstrating your problem would be great. You can for example use this tool: http://plnkr.co/


Changed access level of CosmosView from public to open

Under Swift 3, an access level of open is required in order to be able to create a subclass outside of the class' defining module.

Thank you very much for your help, @0x7fffffff. I have pushed a new 7.0.0 version with your update.


Update response status

Now the response status will be the standard response for successful HTTP requests unless the Range header is provided. In that case we will send a partial content response.

LGTM.


Large repos are slow with ${license.git.copyrightCreationYear}

Describe the feature
When using the ${license.git.copyrightCreationYear} feature on a large repo it can take quite a while to perform the checks (or format the headers).
Can we have an configuration option ...
<ignoreGitCopyrightCreationYear>true</ignoreGitCopyrightCreationYear>

This should default to false.
This would allow for 2 profiles ...

-Plicense-update to update/format the headers and perform the slow git lookups.
-Plicense-check to check the license headers, without the git lookup step, basically ignoring the year (or at least ensuring the year is within the range of inceptionYear and currentYear)

I was wondering, can the header template include regex?
That would be sufficient as a workaround as well.

@hazendaz : there could be a simple way to achieve this I think...
Right now, it is possible to add some placeholders in templates where the value will come from <defaultProperties> or <properties> in the plugin declaration in the pom.
In the git plugin, we could add a check: for each git property like license.git.copyrightCreationYear (but also others), if we see them already defined through the project properties, then we don't compute them.
This sort of override would allow someone to even call the plugin with CLI by passing a system property to override year, author, etc.
This fix would be very easy to do.

@joakime : for now, you could do what others are doing maybe: using a shallow clone. If you don't use the years then it might work. It's a way to limit the depth of a repo, at the expense of loosing some information from older commits like year, author, etc.

@joakime : another option too is to use license.git.maxCommitsLookup to limit the number of commits to go through in case you cannot use a shallow clone. But if you can, I really encourage you to use shallow clones in your CI : it will just speed up the clone process a lot for a big repo.

We've moved on and are no longer using the ${license.git.copyrightCreationYear} as the check on our repo was taking over 4 hours.
This issue is no longer relevant to us.


Ensure AssociatedDataSources is nonnull even for DType.Invalid

Fixes a longstanding intermmitent Arg Null Exception we've seen, when DType.Invalid leaks into the system.

✅ No public API change.


Affine loop tiling pass

Intended to tile airrt shim dma ops, to generate ipu.sync op at the end of each tile to reconfigure shim dma bds.
Added a registration template to assist with IREE integration.

This reminds me of the functionality in mlir/lib/Transform/AffineLoopOptPass.cpp, which nobody has used or touched in years.