rule processor function split to classifier and rules engine

to: @chunyong-lin, @Ryxias, @strcrzy
cc: @airbnb/streamalert-maintainers
resolves: #122 (ndjson and regular json blobs are now supported at ingest time [for s3])
resolves: #198 (exit codes are now properly used from all cli commands)
resolves: #279 (this is no longer an issue)
resolves: #353 (type checking is now performed before selection of schema and will continue to try other schemas upon failure)
resolves: #585 (the cli now warns when creds are not present)
resolves: #772 (the test will now fail, logging the rule that is missing)
resolves: #830 (the new firehose record segmentation logic will not be a victim of this error)
Background
This is the culmination of about a dozen other smaller PRs to split the monolithic rule processor function into two functions (classifier and rules engine).
Changes (high level)

Breaking out the rule processor into two smaller/more manageable packages: classifier and rules_engine.

This change also completely refactors the parsing/classification logic and greatly reduces complexity.

Leveraging the tf_lambda terraform module for these two new functions.

Also adding terraform modules for the individual functions for miscellaneous/permissions for the functions.

Deprecating (read: removing) the old tf_stream_alert module completely.
Overhaul of the CLI package and manage.py to leverage help/description text for all parsers and removing the SUPPRESS anti-pattern that was introduced.
Adding a feature to the CLI to list all available terraform modules to target.
Documentation updates for all change to the CLI.
Bumping version to 2.1.0.

See Also

#821: migration and refactor of payload and parsers
#822: adding classifier and normalizer
#823: adding firehose client for data retention
#824: adding sqs client for function bridge and metrics updates
#826: adding rules engine function
#829: terraform for classifier function, metrics, and sqs
#831: general cleanup from the current refactor
#832: terraform for rules engine function and generation code
#836: revamping manage.py and updating test framework to use new classifier/rules engine
#837: properly exiting CLI on errors for all handlers
#838: removal of all rule processor code, tests, and terraform module
#839: documentation updates mostly for new CLI changes
#840: additional doc change and adding ability to CLI to list terraform targets
#841: small change to how lookup tables are accessed and quiet test logging

Testing
All of these changes have been deployed in a test account and are operating as expected.

fyi I have added a new commit to this here that addresses some changes in the current botocore library (>=1.11.0) vs the one we have pinned (1.10.84)

@chunyong-lin / @Ryxias / @strcrzy  could you PTAL at the latest 4 commits. these are the only ones that have not gone through a prior review.
@Ryxias the latest 3 commits address the issues you noticed recently with boto3/moto. I've decided to update them both, and start packaging boto3 directly for use in the AWS Lambda environment (instead of relying on the wildly outdated version that exists in the Lambda container).


Potential timezone issues

If there is no timezone set in php.ini (or one that you aren't expecting to have set) then you can see inconsistencies in the last/next run times and the logs of the times when they actually run.
eg, I had a task set to run every 12 hours at 12 and the last/next times would show as 00:00:00 and 12:00:00 as expected, but the logs would show as 6pm, 6am as the server timezone was set to -6h.
Still looking into this really, as the logs can look correct by changing the application timezone, but they still seem to run at the wrong times.

I think this is actually fixed by setting the application timezone in the configuration file
'timeZone' => 'UTC',

I was configuring the formatter component :)


Issue #15 Use status file to get the IP and remove to look for leasefile

We don't need to have now lookupIPFromLeasesFile since all the major
distro have libvirt > 2.0.0 and that was for the 1.2.6
Also we are adding 120sec wait time in 40 loop in 3 sec interval then
default one.

@cfergeau I broken the commit messages, have a look again.


Add method to monitor for state changes

... and a couple of (breaking) changes to make using the new method (but also other scenarios) easier to use.
Fixes #5.

Sorry for late response! :sweat:
I think we should not overestimate the backwards-compatibility at this state. Because your PullRequest contains some compatibility issues, we will make an V2 branch after merging this ;)

Thanks for your reply! I'll read through them later or in the next few days.
Did you also have a look at https://github.com/rovo89/go-nuki/commits/split_client?
The idea behind it is described here: https://github.com/tarent/go-nuki/pull/8#discussion_r1223466088 and https://github.com/tarent/go-nuki/pull/8#discussion_r1223572774


Move k8s-basics content to concepts & reference

Also, add a link to the google comic describing
kubernetes


Revisit need for node/electron-browser in workbench/contrib/output

Refs https://github.com/Microsoft/vscode/issues/68302
I am not sure why src/vs/workbench/contrib/output has to have most of its files in electron-browser land. Please consider lifting this to browser if possible.
If there is something blocking this task, speak up and we need to think about introducing new services as needed.

This is due to the RotatingLogger in spdlog.
Forwarding to @sandy081 since he introduced this with @joaomoreno and might know best if there are alternatives


Improvements suggestions

Hi @delirius325,
First of all, thanks for sharing this plugin, really neat and useful.
May I suggest a few improvements?

I think it's better not to ship empty values to ES, it's unnecessary overhead and payload and often leads to warnings in Kibana; I've seen this mainly with AssertionResults and FailureMessage so far, but it's likely to happen in other use-cases as well
Introduce an option to enable/disable sending RequestBody and  ResponseBody regardless of es.test.mode
I didn't get the chance to check this one yet, but would be cool if es.parse.all.req.headers=true and es.parse.all.res.headers=true would still work in all es.test.mode
In Filters, introduce an option to exclude and not only include
Not all fields are documented, would be nice to have them all well explained

Besides that and the other issue I raised, it looks great!
Thanks again.
Cheers.

Hi @swiaam,

I'll look into this, I haven't used Kibana heavily with my plugin. I've mostly used Grafana, so I'm not aware of errors regarding Kibana. It'd be really appreciated if you could make a PR regarding this.
We'll have to look into a way of doing this gracefully, I don't want to add too many options and clutter the listener's configuration GUI.
Again, sort of refers to your previous request. The whole point of es.test.mode is to silence certain fields and alleviate payloads (according to use-case).
RegExp are supported in filters, so it's possible to do pretty much anything. Although, it'd be possible to add an exclude pattern (i.e !!!doNotIncludeThisString).
Fair point, the documentation has been lacking lately.

Thanks a lot 😄 !

Hello sir - how good elastic search is when compared to influx when it comes to handling heavy load of 10000 tps or so from jmeter? Could you please share some benchmarks.

I don't have any benchmark and I personally don't use the influx backend listener. But I've never encountered any issues in terms of performance overhead coming from the ES backend listener. If anything, you can set the es.bulk.size option to your liking to avoid making too many HTTP requests to your ES instance.


ModuleNotFoundError: No module named 'eth_account'

I'm getting this error when I run the command pulling.py -contract  "xxxxxxxxxxx"
Traceback (most recent call last):
File "C:\Users"User"\honestnft-shenanigans-master\metadata\pulling.py", line 10, in
from web3.exceptions import ContractLogicError
File "C:\Users"user"\AppData\Local\Programs\Python\Python39\lib\site-packages\web3-5.26.0-py3.9.egg\web3_init_.py", line 6, in
from eth_account import (
ModuleNotFoundError: No module named 'eth_account'

On what contract are you running the code?

Etherium...but I just found out the web3 and web3 multicall are not installed...so i'm installing it and i'll try it

@ricrosales This can be closed


[HOLD for payment 2023-05-16] Personal Details - In city name only the first letter stays capital after saving the address

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to settings > profile
Go to Personal details > Home address
In City field use N.Y.C

Expected Result:
The city name shouldn't change
Actual Result:
Only the first letter stays capital
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/233135928-86af54e2-ff90-4057-b04b-c2728ca8460f.mov
Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681841912744349
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010b96191c22f1f471
Upwork Job ID:<PHONE_NUMBER>620362752
Last Price Increase: 2023-04-19

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

This will need to be internal, since we have to update the backend. Basically following the exact same pattern as https://github.com/Expensify/App/issues/16960 for whoever gets this!

Oh wow, I don't think many new yorkers would type N.Y.C 😅
This is only happening when there are periods between the letters:

Job added to Upwork: https://www.upwork.com/jobs/~010b96191c22f1f471

Triggered auto assignment to Contributor Plus for review of internal employee PR - @mollfpr (Internal)

Triggered auto assignment to @dangrous (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

oh hey, this makes it easy. I'll essentially do the same thing I did on that other PR.

Still waiting for deploy to prod (on staging now at least); App PR is already reviewed though so it'll be quick once everything's up.

App PR is merged, on staging

As with https://github.com/Expensify/App/issues/16960, this wasn't really a bug - just an edge case that wasn't thought about. The PR was literally the creation of the file on the backend in 2012 (they used a different method to do the capitalization, but it was there from the beginning). I don't think commenting will be helpful, nor will a discussion or a regression test. Let me know if you disagree @mollfpr, but I'll check off the list for now.

Thanks @dangrous for completing the checklist.
I also agree with you 👍

@NicMendonca Applied!

@mollfpr @thesahindia sent the offer!

@NicMendonca accepted, thank you!

Both paid! Thank you!


Restructure

Changes in this pull-request:
* restructuring the riscv-test-suite to indicate clearly what is deprecated, wip and usable
  tests.
* based on the above fixed the directory structure for riscv-targets where-ever applicable. Only
  tested riscvOVPsim and spike.
* fixed script bugs for spike as well
* renamed rv32i/I-IO.S to rv32i/I-IO-01.S along with necessary changes to the reference files
  and Makefrag
* renamed mbadaddr csr to mtval as raised in issue #31
* C.SWSP-01.S test updated to fix issue #37

Close: #8
Close: #31
Close: #30
Close: #32
Close: #33
Close: #37
Close: #47
Close: #67
Close: #96

i'll resolve the conflicts in some time

Conflicts resolved.


Unable to load a pt model, [enforce fail at inline_container.cc:222] . file not found: archive/constants.pkl

I am using following dependencies in my project,
   compile "ai.djl.pytorch:pytorch-engine:0.12.0"      compile "ai.djl.pytorch:pytorch-native-auto:1.8.1"
I am trying to load a pt model generated trained using Python. Please refer to the snippet that I am using,
         PtModel model = (PtModel) Model.newInstance("model");         model.load(Paths.get("src/"));
the load operation fails with following exception,
ai.djl.engine.EngineException: [enforce fail at inline_container.cc:222] . file not found: archive/constants.pkl
We tried generating the model with different PyTorch versions such as 1.9.0, 1.8.1, 1.6.0, 1.5.0, but we are seeing the same issue.
Not sure why constants.pkl file is being looked for as the latest pt model format just contains data.pkl
Any help here would be highly appreciated.

Thanks it worked!


fix(form): fix when the form layout is vertical and there is no label…

… to hide the label

写个测试吧


license unclear

Could you please specify a license for your work.
I think the original work is Apache-2.0 license
https://github.com/nisabek/icinga2-slack-notifications
Best Regards
Nicolas

I wasn't aware of that, thanks for pointing out.
I have added the Apache 2.0 license

that was fast, thanks


Site-specific allowed content-fields

Had a shot at creating a file this time - here are the content fields we're using for each site. All of these are our site 'defaults' - anything not listed here won't become active upon import hence the need to guide any new and current XML clients towards something like this.
We don't have any clients for educations.com using XML for now but I thought it would be worth adding just in case. If this works, it would also be great to have a link to it in the main 'course' documentation page (if possible). Curious to hear any feedback/ideas for improvement! Thank you so much!

Merged! You are now a contributor of the repository!
Thank you for your help! @oligarner


max_line_width only for certain components

This is a potentially tricky issue to solve...
When I implement max_line_width, it quite correctly trims each buffer to the integer I set. Unfortunately I have a component which sticks a nice big red circle if the buffer has been modified and not saved. The max_line_width chops this off, as intended.
It would be great to be able to get max_line_width to ignore components which have a certain property like ignore_truncate = true, that way the filename of the buffer (which I do want truncated) is trimmed, but not my modified icon.

You can increase that component's priority to make sure it remains visible, for example
local nice_big_red_cirlce = {
  text = ..,
  hl = ..,
  truncation = {
    priority = 1,
  }
}

Check out the line width constraints section of the README for more infos.
The truncation can also take a direction = 'left' | 'right' key to specify the direction from which a component is truncated. In my own config I set direction = 'left' for buffer.filename and buffer.unique_prefix.


Add LED to PCB

We should add an LED to GPIO 2 (default GPIO for LEDs) which we can use for visual feedback

Added RGB LED to the board
https://www.mouser.de/ProductDetail/Kingbright/APHF1608LSEEQBDZGKC?qs=YCa%2FAAYMW02iGkI4tWMQgA==
Connected to following GPIOs of the nRF chip:

P0.04 - RED
P0.06 - GREEN
P0.08 - BLUE


Index.html processing

to start with it would be good to do variable replacement for title & url in the index.html for documentation. In addition it should also tack a version number onto the end of the documentation assets.

This has been implemented


Explicitly set RDS CA: rds-ca-rsa2048-g1

Issue Number
#848
Purpose/Implementation Notes
Unable to get the latest_version_till to resolve a single certificate in a reasonable amount of time. This may be looked into in the future but this certificate will expire in the 2060's which seems sufficient.
Types of changes

Bugfix (non-breaking change which fixes an issue)

Functional tests
N/A
Checklist

[X] Lint and unit tests pass locally with my changes

Screenshots
N/A

Correction, the allocated certificate expires around 1 year from now, but this supports auto rotation.


Might there be any problem tunneling port 80 from the current version of WSL?

I was recommended to use OpenSSH via WSL not only to authenticate to my VPS, but also to tunnel actions I do from my browser via port 80, such as PHPmyadmin actions - Several information security experts recommended me of doing so (I already closed port 3306).
I use this command to both authenticate and tunnel port 80:
ssh<EMAIL_ADDRESS>-L 22:localhost:22 -L 2222:localhost:80 -i ~/.ssh/key
Yet I ask if should there be any problem tunneling port 80 from the current version of WSL, also because I might have a small problem tunneling it, which might not be WSL related at all, I really have no idea and ask only make sure as I'm not a OS developer.
I would thank you dearly for sharing your experience.

Hi Benosika - it could be related to the issue #1554 that I just opened
there seems to be a problem with implementing servers in WSL

@lefty-kreouzis - I don't see any WSL specific issue reported by @Benosika in this post. It seems like he is asking for general guidance. There shouldn't be any general problems of implementing servers on WSL and people have been successfully able to do it. Although, some users are experiencing issues with it (sometimes it's an issue with the AV blocking access). Do let me know if I am missing something.


Export Data from Dynamics 365 Functionality

Hi Scott,
I am planning to use spkl as a base to implement data export functionality. It will be a spkl task which will extract data from a Dynamics 365 instance base on some configuration within the spkl.json file. It will create data.xml and data_schema.xml files (Similar to Configuration Migration Tool from Microsoft) and these files can be zipped up to be used by the Package Deployer.
What are your thoughts on this?
Regards John

Hi @JohnTowgood - sounds interesting - is this so that you can easily re-export the data before committing to source control - similar to unpacking the metadata? I think the challenge will be making it easy to create the schema without the configuration migration tool GUI.

Hi @scottdurow, yes it is like unpacking Metadata but in this case unpacking/exporting reference data into source control. I have already built a small command line app to do this and have used it for a year now, so just need to port it to spkl. I had no issues generating the schema and used a configuration file to control attributes and fetchxml to control what data to export.


fix: small api fixes

Description
Small api fixes
closes #4617

Let's leave this breaking change and update the API version then.
BTW, we are going to be adding more API breaking changes in the next release with the merge of debug and bee APIs. So this can be seen as a first step.
wdyt @NoahMaizels ?

Let's leave this breaking change and update the API version then. BTW, we are going to be adding more API breaking changes in the next release with the merge of debug and bee APIs. So this can be seen as a first step.
wdyt @NoahMaizels ?

Actually after considering it a bit, I think maybe it would be best to include these changes together with which release merges the debug api, since that's also a breaking change and I know we have plans to communicate about that, so I guess we may as well bundle all these breaking changes into a single release and communicate them all together in advance.

Let's leave this breaking change and update the API version then. BTW, we are going to be adding more API breaking changes in the next release with the merge of debug and bee APIs. So this can be seen as a first step.
wdyt @NoahMaizels ?

Yeah I agree with you, I think it can be included in the next release since like you said it will be including breaking changes as well and we already have plans to communicate about those in advance


Fix two bugs in PR properties

Summary

Save the refreshed PR properties, not the lookup ones - I mixed up the properties that we use to look up the PR and those that we actually fetch from the provider. Let's save those that we use to look up the PR to ensure that we have all the data available. In this particular case, we were missing the SHA.
GitHub's PR number is not int64, but our protobuf is - Our protobuf defines the PR number as int64, but I didn't notice that the GH API returns the PR number as plain int. It's easiest to upcast the GH value to int64.

Change Type

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
manually followed the steps in our smoke tests
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.285% (-0.002%) from 53.287%
when pulling bb165e2864d3555b76a4303b7f99480a58e64b20 on jhrozek:pr_fail
into f6bff2f9df7e7dbcdb3755dafaf0e3c5fa1bcb1c on stacklok:main.


Use containers/image lib instead of docker

This will use github.com/containers/image to pull images instead of connecting to the docker socket (which requires running  in privileged mode).
Use of the docker daemon is still possible via --use-docker
Fixes #35
(this PR is an update of #37)

Use of the docker daemon is still possible via --use-docker

@ilackarms I am not sure if we should break the cli backward-compatibility. We should probably use --no-docker (or similar) instead.

@mtrmac can you please review  https://github.com/openshift/image-inspector/pull/58/commits/50efed132182ea4177096ccc4042fb7e8f08fa13 to see that i have correctly understood whiteout file format in layers?

@ilackarms do we really need the go 1.8 dependency?

@simon3z sorry that was left in from a debug build; removing it now

@mtrmac can you please review 50efed1 to see that i have correctly understood whiteout file format in layers?

All I know about whiteouts is that they exist; perhaps @runcom can help or point to someone knowledgeable?

@ilackarms maybe it's time to squash commits (I am not saying to squash them all in one... but at least few).
Also, did you run dep prune I am worried about those 7000 files :blush:

@simon3z I can squash now, although I usually look to get the lgtm before squashing, in case i need to revert something

OK let's go in order... I see that this is including (of course) #57 and #38. Let's get those merged first so this will look cleaner I suppose.

@simon3z @enoodle @pweil- please (re-)review

@mfojtik PTAL

@ilackarms @simon3z i would keep the dep bumps as separate commits next time, it makes it easier to review :-)

some nits but LGTM

@simon3z the deps have already been pruned; unfortunately all the added dependencies appear to be used (at least according to dep)

@pweil- @mfojtik can you please review?

I'm currently slammed with 3.6 closing items.  Will have to get to it after that unless someone else can give it the :+1: earlier

note: we are waiting for openshift/origin#15298 to enable running pod without any special SCC / privilege

update: https://github.com/openshift/origin/pull/15298 has been merged. we should be able to run image inspector without any special privileges after this patch is merged @simon3z

@ilackarms Do you plan to update this PR?

@hypery2k not sure this project is being actively developed anymore (i'm no longer a part of it). maybe @pweil- knows the current maintainers?

@simon3z can you comment here?

@simon3z can you comment here?

@pweil- I am available for high level review, design guidance, etc.
For active development of the project you should sync with @oourfali

@hypery2k We are not going forward with this PR at this time...

okay, thanks for the update. Are there plans to support running without root rights?

okay, thanks for the update. Are there plans to support running without root rights?

@hypery2k there are several half-baked PRs that were aiming at that. All in all I think the code needed to achieve is in the PRs but they need grooming, testing, reviews, etc.

okay, i could support on the testing. Did you have any PR that looks most promising? I could even test several of them

okay, i could support on the testing. Did you have any PR that looks most promising? I could even test several of them

@hypery2k IIRC I think #87 and #95 (maybe #95 already contains #87)


Ensure updates to metricsCheckInterval are taken into account

The first implementation of the per-deployment metricsCheckInterval never took into account updates of the annotation value.
The new one read the annotation value and compare it to the current one to decide if the metrics collector should be recreated or not.

Codecov Report

Merging #52 into master will decrease coverage by 20.21%.
The diff coverage is 17.14%.

@@             Coverage Diff             @@
##           master      #52       +/-   ##
===========================================
- Coverage   58.77%   38.56%   -20.22%
===========================================
  Files          11       14        +3
  Lines         638      988      +350
===========================================
+ Hits          375      381        +6
- Misses        234      578      +344
  Partials       29       29

Impacted Files
Coverage Δ

pkg/deployments/zeroscaler/zeroscaler.go
3.92% <17.14%> (ø)

pkg/deployments/zeroscaler/metrics_collector.go
0% <0%> (ø)

pkg/deployments/zeroscaler/config.go
0% <0%> (ø)

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 3f71d07...31033fe. Read the comment docs.

@vbehar, registered one nit, but overall this is great. Thanks.

@vbehar I apologize for dropping the ball on this (and some of your other PRs as well). This LGTM and I will merge pending completion of the current CI run.


error with @input_maker_create

Im working with laracogs.
here is the error im getting:
snippet im using::
@input_maker_create('meta[phone]', ['type' => 'string'], $user)
result im getting::
<input id="Meta[phone]" class="form-control" name="meta[phone]" value="{" id":1,"user_id":1,"phone":null,"is_active":1,"activation_token":"59afc4ace32e7a6b8b3d8e69d1659f05","marketing":0,"terms_and_cond":1,"created_at":"2017-01-19="" 11:47:44","updated_at":"2017-01-19="" 11:47:44"}"="" placeholder="Meta Phone" type="text">
As you can see, I want the value from phone field from meta table to populate the table, instead chaotic is going on in here!!

Hey I found the problem, its due to the field being a null value, I have a fix I'll be pushing this week


Enable IPv6 port binding

Two areas needed tweaking to accomplish this: port parsing and binding ports on the host.
Parsing is an obvious problem - we have to accomodate an IPv6 address enclosed by [] as well as a normal IPv4 address. It was slightly complicated by the fact that we previously just counted the number of colons in the whole port definition (a thousand curses on whoever in the IPv6 standard body decided to reuse colons for address separators), but did not end up being that bad.
Libpod also (optionally) binds ports on the host to prevent their reuse by host processes. This code was IPv4 only for TCP, and bound to both for UDP (which I'm fairly certain is not correct, and has been adjusted). This just needed protocols adjusted to read "tcp4"/"tcp6" and "udp4"/"udp6" based on what we wanted to bind to.
Fixes #5715

Uh-oh. All the containers/common tests are failing on ubuntu - looks like apparmor errors?

It is looking for a container-default file installed for Ubuntu platform?  Needs this for apparmor

@lsm5 WDYT

/hold cancel


Fields docs

TITLE
Description
Description of the pull request changes and motivation.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.82%. Comparing base (8133ae5) to head (5cdfb25).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #911   +/-   ##
=======================================
  Coverage   72.82%   72.82%
=======================================
  Files         150      150
  Lines       34151    34152    +1
=======================================
+ Hits        24870    24871    +1
  Misses       9281     9281

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


[MXNET-480] New version select for Install page

Description
New Version select for install page with query string features
Checklist
Changes

[ x ] Add version select drop-down in install page
[ x ] Add query string modifying capabilities in the URL

Problem:
If I have to give someone a link to install the latest stable Python version on GPU, I guess I will have to give this URL:
http://<IP_ADDRESS>/install/index.html?version=v1.2.0&device=Linux&language=Python&processor=GPU
Note that this URL will no longer install the latest version after 1.3 is released.
Suggested solution:
Version selector can have one more option called 'Latest Stable (1.2)'. This should be the default selection. When user selects this, URL should not contain the 'version=' argument and install command must not mention any version.

Closed in favor of https://github.com/apache/incubator-mxnet/pull/11105


Use apiextensions-application v0.3.0

For https://github.com/giantswarm/apiextensions-application/pull/7

@marians Going to merge this since you're AFK. Thanks for creating the PR.


Many new things for the homepage.

1.Searching extensions
2.Extension categories
3.Filtering extensions by category or creator.
That is what I want!

bump!!


Change layer configuration after model definition

I try to change a layer configuration (in this example its regularizer) after the model definition, but before I call the compile() function. Specifically, I want to add some regularization to keras application models. Consider the following code:
base_model = InceptionV3(input_shape=(150, 150, 3), weights='imagenet', include_top=False, pooling='avg')

for layer in base_model.layers:
        if type(layer).__name__ != 'Conv2D':
            continue

        layer.kernel_regularizer = ortho(0.01)

base_model.compile(optimizer='rmsprop', loss='categorical_crossentropy', metrics=['accuracy'])

I use a custom regularizer here and monitor if it is actually called, however it is not the case. Whenever I compile the model, it calls __init__() on the regularizer, but __call__() is never beeing executed. Am I doing something obviously wrong? Setting the trainable parameter of certain layer of this model does work very well, however setting the kernel_regularizer does not appear to have any effect at all.
I am using the current keras version (2.0.9).

I have a similar issue, so I'd be interested in knowing how to solve this. A hacky workaround is saving the model in disk and loading it again.

similar issue, can't set layer attribute (i.e., kernel_initializer) after model definition


upstream: allow custom extension protocol options

Allows extension protocols to specify custom options. This is a precursor to adding Thrift-specific protocol options to the cluster configuration, but is extensible to any future extension that implements a non-HTTP protocol.
Risk Level: low, ignored by existing protocols
Testing: unit tests
Docs Changes: inline
Release Notes: n/a
Signed-off-by: Stephan Zuercher<EMAIL_ADDRESS>

(There's a bug in here that I need to fix, but the general shape of this can be reviewed.)

Ok. I think it's correct now.


Iotssl 838 selftest checks

Moved all self-test counting to the unit tests to remove duplicate counting.

Reviewed and approved for merge.


Fix 00

Fix format
Constant field group reads
Add update and create data type

ok

lmao

lmao

@everyone @Steve-Dusty


gstreamer1.0-rockchip1-extra has missed files

Hello,
I am running the latest Bionic Beaver image for Rock64.
gstreamer1.0-rockchip1-extra package contains nothing but copyright file.
# dpkg-query -L gstreamer1.0-rockchip1-extra
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/gstreamer1.0-rockchip1-extra
/usr/share/doc/gstreamer1.0-rockchip1-extra/README.Debian
/usr/share/doc/gstreamer1.0-rockchip1-extra/changelog.Debian.gz
/usr/share/doc/gstreamer1.0-rockchip1-extra/copyright

# dpkg-query -s gstreamer1.0-rockchip1-extra
Package: gstreamer1.0-rockchip1-extra
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 10
Maintainer: Jacob Chen<EMAIL_ADDRESS>Architecture: arm64
Source: gstreamer1.0-rockchip-extra
Version: 1.10-1
Description: The Extra Gstreamer plugins for Rockchip platform.
Homepage: http://www.rock-chips.com/

https://github.com/ayufan-rock64/gstreamer-rockchip-extra/pull/1


[BUG] Wrong memory sorting

Describe the bug

It seems to be sorted by string

To Reproduce
Steps to reproduce the behavior:

Create three virtual machines with 10Gi, 1Gi, 8Gi of Memory

Expected behavior

sort by memory size
Log

Environment:

Harvester ISO version:
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Also need sort volume size correctly

validated on master-head


Rename linguist command to github-linguist

Description
As pointed out in https://github.com/github/linguist/issues/3843, when Linguist is installed, it creates a command of bin/linguist which clashes with Qt's bin/linguist.
@smola pointed it in https://github.com/github/linguist/issues/3843#issuecomment-406571806 that the Debian packages has addressed this by using the name github-linguist.
This PR changes the primary Linguist command from bin/linguist to bin/github-linguist and updates the tests and documentation to reflect this change.
This has been tested on GitHub.com with no adverse effects as it uses the bin/git-linguist command.
Checklist:

[x] I am adding new or changing current functionality

[x] I have added or updated the tests for the new or changed functionality.

Fixes https://github.com/github/linguist/issues/3843

Not to self and anyone else who may be making a new Linguist release, this PR and https://github.com/github/linguist/pull/4222 introduce significant enough changes that a full version bump is called for on the next release.
/cc @kivikakk


Bulk deletion on pynetbox

For the below new bulk deletion feature on the API, how do we replicate this functionality on pynetbox?
https://github.com/netbox-community/netbox/pull/5455
REST API Bulk Deletion (https://github.com/netbox-community/netbox/issues/3436)
Thanks

https://pynetbox.readthedocs.io/en/latest/endpoint.html#pynetbox.core.endpoint.Endpoint.delete ?

https://pynetbox.readthedocs.io/en/latest/endpoint.html#pynetbox.core.endpoint.Endpoint.delete ?

Thank you, perfect. I realised I needed to upgrade pynetbox which was why it didn't work for me.


Update API docs for NLog 4.3

Done for RC1:
http://nlog-project.org/documentation/v4.3.0/html/T_NLog_Logger.htm

done, http://nlog-project.org/documentation/v4.3.0/html/R_Project_Documentation.htm
needed to update SHFB folder content with installed version (but git won't show changes), otherwise "no presentation styles" error in SHFB.


Boot a VM with a (good, old-fashioned) ISO in 5 seconds.

Mount ipfs
boot from mount

Discussion

This is probably more interesting as a demo if we were to find more obscure OSs to run. For example: Haiku (BeOS clone), Plan 9, one of the various Lisp machines.
Another interesting application for this is educational distros.

astralboot (https://github.com/zignig/astralboot) + https://gist.github.com/jbenet/76afa70955910a2ed097 does this


Subscription resource providers registration

Overview/Summary
Add a module to :
Register the most commonly used resource providers or providers provided by user input
Register resource providers features provided by user input
Closing #51
This PR fixes/adds/changes/removes
Closing #51
Breaking Changes
N/A
Testing Evidence
Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues
[ ] (LZ-Vending Core Team Only) Associated it with relevant ADO Items
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[ ] Updated one or more of the following tests (if required)

Unit
Linting

[x] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)

Has there been any recent discussion(s) with ResourceManager PG if they are willing to expose registration process with HTTP PUT requests?
How Bicep's auto-registration changes things?
ref: https://github.com/Azure/bicep/issues/3267


Use ExchangeHandle to track ref count of ExchangeContext

Problem
#7124
#6978
#7012
#6918
This PR is going to fix ExchangeContext life-cycle management problem once for all
Change overview
Introduce a shared_ptr like ExchangeHandle to automatically track the ref counter of ExchangeContext to replace raw pointer of ExchangeContext.
Testing
Not yet, make it draft first.

For what it's worth, I am currently working on a redesign of exchange context lifetime semantics that aims to fix these same issues.
Just making things shared_ptr-like does not actually fix all the lifetime problems we have, as far as I can tell.  We might want to have some sort of handle setup in addition to the semantic changes; still sorting that out.
Importantly, we need to make it much harder to get the Close() semantics wrong, which this PR doesn't really address.

IMHO, ExchangeContext::Close() will only initiate graceful shutdown, and ExchangeContext::Abort() will force put the exchange in an error state, and release underlying resources (timers, etc).  Both of them should not affect life-cycle of the object.

I am probably OK with decoupling Close() and the reference counting.  But one of our major lifetime issues is "someone is holding on to this for too long", and having a refptr doesn't, on its own, help with that.  What helps is knowing when you actually need to hold a reference.


python 3 sudo

Python3 should be default.
nobody on linux may execute this whithout sudo due to permission.

There is a PEP specific to this issue: https://www.python.org/dev/peps/pep-0394/ and it recommends that python continue to link to python2, whereas python3 should link to the latest version of Python 3 installed on a system.
This change will hurt users, whereas using python3 it will do the right thing most of the time.

Hello,
maybe @bertjwregeer i'm not sure to all understand you said.
My mind is : everyone is leaving python2 so poetry should recommand python3. maybe my PR is not the good way to do it.
Maybe I'm wrong but I believe that on every system where python3 is system standard, there are both python and python3.

Ah, I misread the PR. Sorry!

The change from python -> python3 work for me. I'm skeptical of addition of sudo -H. I left a longer comment on the line change. (Also, thanks for doing this. Finding this PR got me unblocked and trying out Poetry.)

While the change for python3 seems good to me, I am not comfortable recommending sudo. Generally, I don't think it's a good idea to install tools like poetry for the root user.

ok but there still is a problem with the recommanded way to install poetry :
curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python3
will alway fail on  a standard linux distro due to permission :
jimmy@jimmyMint ~ $ curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python3
Retrieving metadata

Installing version: 0.10.3
  - Getting dependencies
  - Vendorizing dependencies
  - Installing poetry
An error has occured: Command '('/usr/bin/python3', '-m', 'pip', 'install', '--upgrade', '--no-deps', '/tmp/poetry-installer-rr8vh6e7/poetry-0.10.3-py2.py3-none-any.whl')' returned non-zero exit status 1
Processing /tmp/poetry-installer-rr8vh6e7/poetry-0.10.3-py2.py3-none-any.whl
Installing collected packages: poetry
Could not install packages due to an EnvironmentError: [Errno 13] Permission non accordée: '/usr/local/lib/python3.5/dist-packages/__pycache__/toml.cpython-35.pyc'
Consider using the `--user` option or check the permissions.

I agree with @sdispater and personally prefer the solution proposed by #146

Is there a strong enough reason to recommend Python 3 explicitly? Don't get me wrong, I'm 100% pro-Python3, but Poetry supports 2.7 just as well.

actually I don't know if this PR is a good thing. it stays complicated to install even with the --user of #146
@sdispater why not just use pipsi. it works very good with poetry and install is only pipsi install poetry and thats it.

What is the problem in installing with --user?
For me, if poetry is installed through pipsi, it doesn't work properly. Also, I personally think poetry should provide pipsi's functionality, as suggested in #149.

I just think that installing an app via a script is something painfull.
What doesn't work by you with pipsi ?

Let's assume that I installed poetry through pipsi. If I create a new project and let poetry create the virtualenv, pip is not linked in .venv/bin and every install will fail with "permission denied" because system-wide pip will be used.

you are right. I did not see it because I only use poetry with pyenv.
But not sure is it pipsi's fault. maybe poetry which should use the pip of the created virtualenv.

That's the thing: the created virtualenv has no pip.

Closing since the new installer is now more flexible.


Add setvbuf

Add setvbuf to Sys::IO.

Implemented.
https://github.com/yuki-kimoto/SPVM-Sys/commit/a9599c675a969e98982655a2612d3a99d1e99a96


Incorrect method reference

Vineflower version
1.10.1
Describe the bug
To say you have foo() and foo(boolean) in A.class, and there is a method that accepts Runnable OR Supplier, if use use this::foo there is a compilation error, the java compiler cannot determine which method you want to use, it should be decompiled to () -> this.foo()
Additional information

I finally found out whats happening. Minecraft uses proguard to obfuscate their code, and I am not using their official mapping to deobfuscate. So another method named bar was mapped to foo, causing this error.


Online run with repl not working

The online tool to get the session string does not work. I tried with several telegram accounts and several computers, but the outcome is always the same.

I can put the API ID and API HASH with no problems, but when I press ENTER, nothing else happens
Unfortunately, I cannot complete the setup without the session string. I hope that there is a fix for this because your project seems awesome and I look forward to trying it!

Agreed with above, not working. Please fix.

+1

+1


Downstream test: add AssetGraph

AssetGraph (https://github.com/assetgraph/assetgraph) is dependency graph based optimization framework for web pages and applications. It uses Esprima to determine JavaScript dependencies.
Download rate of assetgraph npm package: 20K/month.

@ariya, thanks, that would be great :)


Update not working

Tried updating to new updated version, but just get circle progress going round and nothing happens.
Left it for 5 minutes and still not finished, exited then tried again with same issue.

Do you have to change anything before doing the upgrade?
Anyone else have this issue?
Tried viewing the release notes, but page not found.
https://github.com/firebase/extensions/blob/main/send-message/CHANGELOG.md
Forgot to add:
Current version<EMAIL_ADDRESS>

I have the exact same issues, have been waiting patiently half a day....

Working on a fix today. Will close the issue once its pushed.

Thanks

Fixed. Previously, Firebase would use the prebuilt functions in the extension when uploaded. A recent update by them made it so Google Cloud Functions runs a npm run build by default when deploying extensions and functions.
When npm run build is executed, the tsconfig.json file in send-message/functions extends its properties from the tsconfig.json file in the root directory which can only be read if its built locally but cannot be read if its built on GCP since only the send-message directory is deployed rather than the entire repo.
This commit fixes the issue by removing the extended properties from the root tsconfig.json and moves them into the /functions tsconfig.json file.
To update/install the new version that fixes the build crash, head over here<EMAIL_ADDRESS>

Thanks for doing the fix, when I try to upgrade from the Firebase Console it is still showing version<EMAIL_ADDRESS>not the fixed version 0.3.1.  Will this version be pushed to the console, for if I click the link in the link above it wants to install a new instance of the send-message.


Add Clone support for ConnError.

This will allow for ConnError to be included in other errors.

No longer applicable to current code base


clone/quick-clone with --workspace parameter.

I have clone from git repository to C:\Projects, but when I run following command
git tfs **quick-clone** --bare http://tfs.msbinfo.com:8080/tfs/main/DefaultCollection  $/RMO
it clone repository to C:\Projects\RMO.git~w. The --bare/--workspace parameter does not work well or just ignored. How I can clone to the same folder as my git repository ?

I also create TFS workspace and map this workspace to following folder C:\Projects and run following commands:

C:\Projects>git tfs clone --workspace=VALENTYNPON2D02 http://tfs.msbinfo.com:808
0/tfs/main  $/RMO
C:\Projects>git tfs clone --workspace=VALENTYNPON2D02

All of them Initialized empty Git repository in C:/Projects/RMO/.git/

--bare creates a baer git repo (see https://git-scm.com/docs/gitglossary#Documentation/gitglossary.txt-aiddefbarerepositoryabarerepository) which doesn't have a workspace.
The --workspace given to git-tfs is only for the temporary workspace used by the tool to import tfs changes, but not for development.
Please read up on the corresponding documentation.
Issue can IMHO  be closed due to a user missunderstanding


(IAC-1085) Update SAS Documentation URLs

Changes
Update the SAS Documentation links to documentation.sas.com

Please check the README.md for another go.documentation

Please check the README.md for another go.documentation

Good catch, made an update.


Live Preview made my Chrome stuck to one link whenever external call to chrome or even at bootup

Prerequisites

[Yes] Can you reproduce the problem with Debug -> Reload Without Extensions?
[Yes] Did you perform a cursory search to see if your bug or enhancement is already reported?
[Yes] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
Live Preview of Brackets was working fine for me, 2 days ago the live preview link i.e. "file:///opt/brackets/www/LiveDevelopment/launch.html" got somehow stuck with chrome. Whenever I open a chrome, this link comes. New Tab is working fine. And if I click on a hyper link from other software which opens a chrome tab will also open the above live link. I have tried purging brackets and chrome both and reinstalling again, deleting any config settings for both of them still the issue exist. It has somehow made some setting into the environment that is not getting removed when I uninstall these software. After installing and reinstalling brackets a couple of time the live preview has also stopped working.
Steps to Reproduce

Open Chrome
OR
Click on some link from other software
Chrome opens with the live link not the required one

Expected behavior: [What you expected to happen]
To open an empty page or the link which I clicked on
Actual behavior: [What actually happened]
Opening this live link -
"file:///opt/brackets/www/LiveDevelopment/launch.html"
Versions
Ubuntu 16.04.01 LTS
Brackets Release 1.8 experimental build 1.8.0-17108
Chrome Version 55.0.2883.87

Duplicate of #12872 I believe


Use Darwin Notifications for snapshots?

This isn't an actual issue, more of a suggestion.
Reading through https://github.com/fastlane/fastlane/tree/master/snapshot#how-does-it-work, I'm wondering if you ever considered using darwin notification center to trigger the snapshot on the app side? If you did, what problem did you run into that made you go down the current way of grabbing screenshots?
In case you didn't, here's a good example of it in action: http://www.matrixprojects.net/p/triggering-events-while-ui-testing/
I just ran their sample code and had good success in the sim/iOS 10/Xcode 8.
Seems a whole lot simpler than scrounging the derived data folder for filenames.

@olarivain Very interesting! We'll check this out. I'm going to leave it open as a feature request. Thanks!

Interesting, thank for letting us know. I wasn't aware of this approach, however I don't see a reason changing this in snapshot, as it works without problems with the current approach 👍
I appreciate you letting us know about this, in case something breaks in the future, this would be a great solution.

Fwiw, I've now implemented this in our app.
Huge gotcha is that you cannot pass any data at all with this method. I tried registering for all notifications, and then embed the screenshot name in the notification name (e.g "screenshot|my_screenshot").
That's not an option. Darwin notification are a very basic IPC system.
I got around it by passing the screenshot name
In environment variables (see XCUIApplication launch arg/environment). We reset the screenshot name at each test. It works for us, but it's a big limitation of the approach.

@olarivain Thanks for the update. 👍


learning stop in the middle of training

Hi @zhaolongkzz, i got this following error
EP: 912 - [alpha: 0.2 - gamma: 0.8 - epsilon: 0.25] - Reward: 185     Time: 0:52:56
EP: 913 - [alpha: 0.2 - gamma: 0.8 - epsilon: 0.25] - Reward: 4312     Time: 0:53:42
Traceback (most recent call last):
File "circuit2_turtlebot_lidar_qlearn.py", line 49, in
observation = env.reset()
File "/usr/local/lib/python2.7/dist-packages/gym/wrappers/monitor.py", line 37, in reset
self._before_reset()
File "/usr/local/lib/python2.7/dist-packages/gym/wrappers/monitor.py", line 180, in _before_reset
self.stats_recorder.before_reset()
File "/usr/local/lib/python2.7/dist-packages/gym/wrappers/monitoring/stats_recorder.py", line 68, in before_reset
raise error.Error("Tried to reset environment which is not done. While the monitor is active for {}, you cannot call reset() unless the episode is over.".format(self.env_id))
gym.error.Error: Tried to reset environment which is not done. While the monitor is active for GazeboCircuit2TurtlebotLidar-v0, you cannot call reset() unless the episode is over.
do you know how to solve this error?
this error always occurred around 1000 episde

The ending episode is earlier than the max steps, so the monitor function of the gym gets wrong.
Best to use while True and if done: break instead of giving a range for loops.


Output dates in recognised date format

Describe the bug
A number of fields in the csv export are timestamped in a way that Excel does not interpret as a date. For example activity_date_start_planned is output as YYYY-MM-DDT00:00:00Z despite the correct published format being YYYY-MM-DD. This may inhibit data interrogation post download.
Expected behavior
Output date fields in the same format as they are published.
Screenshots
Raw data:

CSV output:

@JoshStanleyDevInit what CSV endpoint for output are you using?

@siemvaessen Sorry I should have said, this is output from the QB

That is the standard of Solr date-time type if we change it to string then we can not filter the type of date-time. Or the alternative we create a new field for all date-time related Solr:

activity_date_start_planned_filter
activity_date_start_actual_filter
activity_date_end_planned_filter
activity_date_end_actual_filter

And lets activity_date_start_planned, activity_date_start_actua, activity_date_end_planned and activity_date_end_actual.
We need to discuss again about this, because related to so many things after I discuss @luminhan. From me doesn't matter, but this is a bit complicated in the frontend to filter and show the field related to the filter with a different name.


chore: 0.10.1 release proposal

Proposed release notes: https://github.com/open-telemetry/opentelemetry-js/releases/tag/untagged-6a1e363ba26c44b7f82e

We had 69 and I missed the changelog. Updating

didn't we have 67 files previously? if so which file is the "extra one" ?

We had 67 before grpc-js. now we have 69


Use constant time by default for BIGNUMs

The BIGNUM library defaults to a non-constant time implementation of various operations. Where we want to force a constant time implementation we have to remember to set the BN_FLG_CONSTTIME flag. Experience has shown that we often forget to do this. For example see:

54f007a (CVE-2018-0737)
8db7946
e913d11
6364475
6364475
3de81a5
47ae05b
033dc8f
3999446 (CVE-2016-2178)

This is not intended to be an exhaustive list - there are probably others cases that I haven't listed.
The difficulty of changing the default is that this will have a performance impact for cases where constant time is not a requirement. It is unclear to me how many of those cases there are and whether we should be worried about it or not.
PR #5969 made one attempt at fixing this. Feedback on that suggested a better approach may be to use separate APIs for constant-time and non-constant time operation:
@briansmith wrote:

See https://github.com/HACS-workshop/spectre-mitigations/blob/master/crypto_guidelines.md#1-do-not-conditionally-choose-between-constant-and-non-constant-time. I'm biased, but I think BoringSSL's solution, which was to use separate APIs for constant-time and non-constant-time implementations, is better, in general.

In my view, the following quote from Daniel Bernstein's Some thoughts on security after ten years of qmail 1.0 expresses the situation perfectly:

I don’t like waiting for my computer. I really don’t like
waiting for someone else’s computer. [...] But I find security
much more important than speed. We need invulnerable
software systems, and we need them today, even if they are
ten times slower than our current systems.

Speaking purely as a user of OpenSSL: If the approach you implement provides stronger and more valuable security guarantees, I will use it immediately, whether it is twice, thrice, or ten times slower than the current approach. So, thank you for taking this issue seriously, and thumbs up!
For comparison, here are some GMP low-level interface functions for cryptography:
8.1 Low-level functions for cryptography
These functions are resilient to side-channel attacks, and I hope that their design, implementation and trade-offs may provide some inspiration.

See also #6640.

Is this a duplicate of openssl/openssl#6640

No. #6640 is about how OpenSSL's BIGNUMs completely fail to be constant-time due to the in-memory representation it chose, causing numerous constant-time related security issues. The fix is to rework either BIGNUM or your cryptography primitives' internals to avoid this.
This issue is about how the BN_FLG_CONSTTIME flag is extremely error-prone and caused numerous other constant-time related security issues. The fix proposed in this bug is to change the "default", but I actually think that's the wrong lesson. In BoringSSL, we removed the flag altogether. Rather, I think the right observation is that windowed exponentiation with fixed and sliding windows are separate operations and should be separate functions altogether. If you're in a context where the exponent is secret, used fixed windows with a constant-time lookup in your table of precomputed multiples. If the exponent is public, used sliding windows to improve performance. If the exponent is not only public, but a constant, you may be even better off specializing to the exponent and hardcoding an optimal addition chain.


Use meteor kitchen to generate not meteor apps

Hello @perak, we are trying to begin a fully transactional accounting software and would love to use something similar to meteor kitchen to create our front and backend with a real database (not Mongo) and with React and React native if possible.
Have you thought about using your generator for another type of projects (like sails)?
If not, can we discuss a possible freelance arrangement?
Please contact me at<EMAIL_ADDRESS>

THIS IS NOT AN ISSUE...
message @perak through normal channels... anyone following his project receives your message.

+1 for idea ;)


Feat/add nonce in request auth

https://github.com/betagouv/audioconf/issues/195
Todo : more tests (end-to-end test ?)

close #195


Angular 6 Error Raven.config is not a function Evaluating src/app/app.module.ts

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
Can not start Angular app as Raven.config error
Error in src/app/app.module.ts (11:3)
Raven.config is not a function
Evaluating src/app/app.module.ts
Evaluating src/main.ts
Booting application

see https://stackblitz.com/edit/angular-sentry-ravenjs
What is the expected behavior?
No error

Use import Raven from 'raven-js'; instead of import * as Raven from 'raven-js'; and it will work.
We don't export named functions yet and Raven itself is a singleton.

Thanks, @kamilogorek.
Sentry documentation for angular need to be modified.


Implement "variant" key in legacy builder and upstream change to OCI

Currently the built image configurations will skip the variant for arm images. This variant must always be set in order to create manifest lists which can properly resolve arm variants.
Currently OCI image config specification does not have variant as a supported field.

This is been completed and just pending review of https://github.com/moby/moby/pull/39177
The OCI side has been opened and we can consider it complete in regards to this issue.


Unblock wrapping/unwrapping on SDK - add unwrapping and getter for wrapped tokens

this has been added in V1.29.11 of the SDK


Can't call multiple dispatches on a single instance

Pretty much what the title says.
The root of the problem is that the dispatch function is calling prepRoutes  inside Router.
With a second call to dispatch on the same instance, we get an exception from FastRoute that the same routes are being added again, which is obvious.
A simple fix would be to have a flag in the Router class and check it at the beginning of prepRoutes method, to see if routes are already prepared or not. If prepared, skip the method.
My use case is that I'm using this router with ReactPHP. I don't want to instantiate a new Router for every request. The same router should compile and cache routes so the same Router instance can be used to handle them all.
I'm looking for some thoughts on this.

Implemented in https://github.com/vfsoraki/route/tree/feature/multiple-calls-on-same-instance.
A review would be welcome.

Implemented in https://github.com/vfsoraki/route/tree/feature/multiple-calls-on-same-instance.
A review would be welcome.

Phil made an unmerged PR that tackles this very concern (Link here #283 )
This gives it plenty of relatively minor updates, and bumps up the minimum PHP version, but includes a cached router to support React and the like.

Phil made an unmerged PR that tackles this very concern (Link here #283 )
This gives it plenty of relatively minor updates, and bumps up the minimum PHP version, but includes a cached router to support React and the like.

@philipobenito I looked into cached router implementation @jpmc mentioned.
From what I understand, the cached router caches routes in a file and reads them back every time a request a dispatched. This seems inefficient especially when running in async environments.
Having an option to cache routes in memory would be great.

@philipobenito I looked into cached router implementation @jpmc mentioned.
From what I understand, the cached router caches routes in a file and reads them back every time a request a dispatched. This seems inefficient especially when running in async environments.
Having an option to cache routes in memory would be great.

I was aiming to get this release out last week but I’ve had flu, so now aiming for a release some point in the next two weeks.
I have no concerns about the implementation as long as it’s used in the intended way, but I need to give some thought to possible misuse and any safety concerns there.
I also need to do some more extensive testing, I’d appreciate help with that if you want to try it out.
All being well I will also implement several storage drivers for the cache with an easy way to implement more for users using anything not supported initially.
Sent from ProtonMail Mobile
On Thu, Jan 14, 2021 at 04:09, Vahid Fazlollahzade<EMAIL_ADDRESS>wrote:

@philipobenito I looked into cached router implementation @jpmc mentioned.
From what I understand, the cached router caches routes in a file and reads them back every time a request a dispatched. This seems inefficient especially when running in async environments.
Having an option to cache routes in memory would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I was aiming to get this release out last week but I’ve had flu, so now aiming for a release some point in the next two weeks.
I have no concerns about the implementation as long as it’s used in the intended way, but I need to give some thought to possible misuse and any safety concerns there.
I also need to do some more extensive testing, I’d appreciate help with that if you want to try it out.
All being well I will also implement several storage drivers for the cache with an easy way to implement more for users using anything not supported initially.
Sent from ProtonMail Mobile
On Thu, Jan 14, 2021 at 04:09, Vahid Fazlollahzade<EMAIL_ADDRESS>wrote:

@philipobenito I looked into cached router implementation @jpmc mentioned.
From what I understand, the cached router caches routes in a file and reads them back every time a request a dispatched. This seems inefficient especially when running in async environments.
Having an option to cache routes in memory would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Closing as included in imminent release

Closing as included in imminent release


Failures in exporting video snippets should not crash the instance container

https://github.com/Azure/KAN/blob/069a08ef93d6bdd6e0c0c4274315adb5c825ee9c/src/edge/EdgeSolution/modules/kanai/app/exports.py#L81
If for any reason video snippet exports fail the instance container crashes. Looking at the log, this might have something to do with the above line. According to this: https://stackoverflow.com/questions/30509573/writing-an-mp4-video-using-python-opencv, we should use "*mp4v" instead of "MP4V"? We also need to handle exceptions so that errors don't crash the container in this case.

The exact message before the container crashes:
OpenCV: FFMPEG: tag 0x5634504d/'MP4V' is not supported with codec id 12 and format 'mp4 / MP4 (MPEG-4 Part 14)'
OpenCV: FFMPEG: fallback to use tag 0x7634706d/'mp4v'
This doesn't look like an error, but the log terminates after these lines.


[Question] How to increase app performance?

Hello,
I am currently creating a proof of concept application using this project. I managed to remove some components that I don't need such as Workflow as I am only using the Image map. But when I tried to test the performance in Lighthouse, it produced this result:

What do you think should I do to reduce loading time and app size?
Thanks a lot @salgum1114 for this amazing project!

@andrewoplas
ImageMapEditor contains font files, so the application size seems to be large. If I remove some of the components of the ImageMapEditor I wrote, I think the application size can be reduced.


TensorFlow Probability

For GPU support:
https://www.tensorflow.org/probability/install

pip install --upgrade tensorflow-probability-gpu  # depends on tensorflow-gpu
Currently, TensorFlow Probability does not contain any GPU-specific code. The primary difference between these packages is that tensorflow-probability-gpu depends on a GPU-enabled version of TensorFlow.

Now, because tensorflow-probability-gpu does not actually contain any GPU-specific code, but merely depends on tensorflow-gpu, I imagine it should be easy to swap out back-ends, and depend on tensorflow-rocm instead.
Similar would apply to other libraries built on top of tensorflow-gpu.
Is there an easy way to swap out these tensorflow backends, or could we get a tensorflow-probability-rocm?
Should I file an issue at tensorflow-probability instead?

@parallelo could you help weigh in here? IIRC there was another package with similar dependency to tensorflow-gpu and there was a solution to that.

Sure, let me dig those details up again.  Stay tuned.

Have you tried the --no-deps flag for pip when installing tensorflow-probability-gpu?  If you go this route, you may need to install all of the other dependencies by hand.
Alternatively, you could try this type of workflow:

install both tensorflow-probability-gpu and tensorflow-gpu -- now you'll have all of the dependencies
uninstall tensorflow-gpu -- this should still leave the other probability-related dependencies intact
install tensorflow-rocm

Let us know if these suggestions work for you.
Looking long-term, we'll have to request new target whl support from the tensorflow/probability maintainers (and for other similar projects).

The tensorflow-rocm dependencies appear to be sufficient for using tensorflow-probability-gpu.
pip install tensorflow-rocm
pip install tensorflow-probability-gpu --no-deps

I was able to run the first graph found in Chapter 1 of Bayesian Methods for Hackers without issue.

thanks. I am trying to run the following:
import tensorflow as tf
mnist = tf.keras.datasets.mnist

(x_train, y_train),(x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(),
  tf.keras.layers.Dense(512, activation=tf.nn.relu),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation=tf.nn.softmax)
])
model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

model.fit(x_train, y_train, epochs=5)
model.evaluate(x_test, y_test)

I get the following from my pycharm IDE:
/usr/bin/python3.5 /home/c/.PyCharmCE2018.2/config/scratches/scratch.py
Traceback (most recent call last):
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
  File "/usr/lib/python3.5/imp.py", line 243, in load_module
    return load_dynamic(name, filename, file)
  File "/usr/lib/python3.5/imp.py", line 343, in load_dynamic
    return _load(spec)
ImportError: libhiprand.so.1: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/c/.PyCharmCE2018.2/config/scratches/scratch.py", line 1, in <module>
    import tensorflow as tf
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/__init__.py", line 22, in <module>
    from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/__init__.py", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 74, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "/home/c/.local/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
  File "/usr/lib/python3.5/imp.py", line 243, in load_module
    return load_dynamic(name, filename, file)
  File "/usr/lib/python3.5/imp.py", line 343, in load_dynamic
    return _load(spec)
ImportError: libhiprand.so.1: cannot open shared object file: No such file or directory

Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/install_sources#common_installation_problems

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Process finished with exit code 1

it may run if i use sudo from the command line. one second

ModuleNotFoundError: No module named 'tensorflow.contrib.linalg'

This is because tf.contrib.linalg was moved to tf.linalg in TensorFlow 1.12 (release notes). Scroll through the TF Probabiilty releases page to determine which release corresponds to your version of TensorFlow. For example (from the releases page),

This is the 0.5.0 release of TensorFlow Probability. It's tested and stable against TensorFlow 1.12.

Also, according to the installation section from their README, they no longer include tensorflow as a dependency for their package, meaning it's a bit easier to install:
# Assuming tensorflow-rocm==1.12.0 has already been installed...
pip install tensorflow-probability==0.5.0


Skip intro option

Describe your suggested feature

Other details
Hello sir please try to add skip intro option in next update. Aniyomi app is great but add some useful features make it best app...
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

The +85 sec minute is , I think, specifically for that. Probably explore the player(that is not a lot) a little.

Ok thanks i will check it out
On Wed, Jul 27, 2022, 11:19 PM sinnghabhay80 @.***>
wrote:

The +85 sec minute is , I think, specifically for that. Probably explore
the player(that is not a lot) a little.
—
Reply to this email directly, view it on GitHub
https://github.com/jmir1/aniyomi/issues/688#issuecomment-1197100779, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXXVLRBUZKCKASJE6VG4I23VWFZENANCNFSM54YDWRQA
.
You are receiving this because you authored the thread.Message ID:
@.***>

The +85 sec minute is , I think, specifically for that. Probably explore the player(that is not a lot) a little.

Hello Try this application :- https://github.com/saikou-app/saikou/releases/tag/v<IP_ADDRESS> . I use this app to watch latest anime movies.

The +85 sec minute is , I think, specifically for that. Probably explore the player(that is not a lot) a little.

Hello Try this application :- https://github.com/saikou-app/saikou/releases/tag/v<IP_ADDRESS> . I use this app to watch latest anime movies.

Saikou has a great UI but I still don't get what you mean as it also has the same +85 seconds button

Possible references:

https://github.com/jonbarrow/open-anime-timestamps
https://anime-skip.com/
API documentation
Github

This has been fixed/added in the preview
https://github.com/aniyomiorg/aniyomi-preview
Steps to shift to this build:-

Create a backup from "Backup and Restore"
Download the preview apk and install it
Restore the backup you created before in the same tab "Backup and Restore"


kprobe: minimal example of doing kprobe/kretprobe BPF programs

Hello,
this PR adds an example that shows how to use kprobes and kretprobes with libbpf, with a description in the README.
The example is similar to the Linux kernel samples/kprobe/kprobe_example.c example.
I'm not sure whether fentry/fexit should be mentioned as preferred alternatives in the README?
I've used %lx to print the tls and stack pointers as %p prints hashed values. perf probe behaves similarly, and prints the whole addresses when it is attached to the kernel_clone function and configured to print stack and tls, so I guess this should be fine for an example. Otherwise, an example that doesn't print addresses could be used, or https://www.kernel.org/doc/html/v4.17/core-api/printk-formats.html could be linked somewhere in the README for clarity.
Regards,
Juraj

Thanks for the feedback. I've fixed everything except removing the for loops, as the programs immediately exit without a loop. I have however replaced them with loops that run until SIGINT is received, similar to some BCC libbpf-tools examples. Additionally cleanup is always explicitly done that way.
The fexit example now prints the filename and PID so that the output matches the fentry one.

Thanks for the feedback. I've fixed everything except removing the for loops, as the programs immediately exit without a loop. I have however replaced them with loops that run until SIGINT is received, similar to some BCC libbpf-tools examples. Additionally cleanup is always explicitly done that way.
The fexit example now prints the filename and PID so that the output matches the fentry one.

Thanks for the contribution! I took some liberty in rewording fentry/fexit description to reduce possible confusion. And did some slight adjustments to code formating here and there. I hope that's fine.
One thing I noticed, though, is that bprm_execve() is a pretty recent change in kernel, so those examples will only work on very recent kernels. Which is quite unfortunate. If you can, please think about other simple, but interesting examples that could server as a demo for kprobe/fentry, maybe we can update them to work on older kernels just fine.

Thanks for the contribution! I took some liberty in rewording fentry/fexit description to reduce possible confusion. And did some slight adjustments to code formating here and there. I hope that's fine.
One thing I noticed, though, is that bprm_execve() is a pretty recent change in kernel, so those examples will only work on very recent kernels. Which is quite unfortunate. If you can, please think about other simple, but interesting examples that could server as a demo for kprobe/fentry, maybe we can update them to work on older kernels just fine.

Sorry, I jut saw this today. I was worried about bprm_execve() as well. I'm currently looking for an alternative and will comment again here when I find something usable.


[Feature]: Plugin registry

Describe the feature
We need some way for users to shop for plugins. I don't know if the other addon repos (like Curse) have such a mechanism. GitHub has tags, so I suggest designating a tag and advertising it in the README.
Describe the implementation
Tag plugins with something like wow-betterbags or wow-betterbags-plugin. Advertise it in the README.

You can search Curseforge for betterbags and get the core addon and several plugins.
Having a registry in BetterBags' Readme would be nice too.

For now, I'm tagging with wow-betterbags-plugin.
https://github.com/topics/wow-betterbags-plugin

You can search Curseforge for betterbags

I like this page: https://legacy.curseforge.com/wow/addons/better-bags/relations/dependents


Prepare for Windows 11 22H2

Summary
Review packages and ensure they provide the best experience for Windows 11 22H2.
To Do

[ ] Reevaluate the default Provisioned Appx Packages
[x] #27

Terminal comes preinstalled and as the default now. Terminal will no longer be packaged in this project.

Looking at insider build 22621 from May it seems that Microsoft.HEVCVideoExtension is now included by default in Windows. That is nice, if this makes it to stable. Previously you had to pay for the HEVC extension, or sideload the free manufacturer only version which is the one listed above.

Store Extension
Package
Price

HEVC Video Extensions
Microsoft.HEVCVideoExtensions
$0.99

HEVC Video Extensions from Device Manufacturer
Microsoft.HEVCVideoExtension
Free

Notice the omission of the s, in the free and now included package name.

Apparently Windows 11 22H2 will reach production sometime in late September. I'm not going to be finalizing anything regarding this issue until we get the final build and ISO.


test: use enzyme, awesome stuff

Well, LGTM. I'm not 100% happy about the browserify changes but the tests look loads cleaner and we have way more complicated tests than this, so :+1: for me

Like the syntax, looks good. Long term I guess that'll take, err.. time :)

Everybody is happy. I push the button.


added contributing-1.md

Hey @AyushSarode, there already exists a contributing file in this repo.
So I can't merge your PR.

Can I do something else for you?
On Mon, Oct 3, 2022, 12:31 PM Mohammed Hamza Malik @.***>
wrote:

Hey @AyushSarode https://github.com/AyushSarode, there already exists a
contributing file in this repo.
So I can't merge your PR.
—
Reply to this email directly, view it on GitHub
https://github.com/MohammedHamzaMalik/Coding-Ninjas-Competitive-Programming/pull/4#issuecomment-1265015190,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARGNSYB5N2FB5Q7JOAFQC4LWBKADXANCNFSM6AAAAAAQ23GHGY
.
You are receiving this because you were mentioned.Message ID:
<MohammedHamzaMalik/Coding-Ninjas-Competitive-Programming/pull/4/c1265015190
@github.com>

You can check out other issues in the issue tab of this repository.


Tinker with body of email to enable sending build URLs

This won't work as I thought. So I am closing it until I find another solution.


Show task history link in visualizer when recording.

Description
This PR adds a link to the task history page when record_task_history is enabled:

To achieve that I

added a new rpc method to Scheduler that returns the record_task_history setting,
added a template for top navigation items,
added the link to the top navigation after an initial check using the rpc method.

Motivation and Context
In some projects, easy browsing of the task history might be an important feature, so putting a link in the top navigation bar seems like a good thing to do.
Tests
I added two simple tests that invoke the added rpc method and expect either True or False, depending on the record_task_history setting.

I'm not sure i'm totally following the appearance of the change. Could you fix the link to the image? (I'm getting 401)
Glad to see new tests which are passing!

@dlstadther I fixed the image link.


Set Up SAP Data Intelligence, Trial Edition

Tutorials: https://developers.sap.com/tutorials/dataintelligence-trial-v2-setup.html
SAP Data Intelligence, Trial Edition is not available in SAP Cloud Appliance Library.

We are working on it and we will have an update shortly. Thank you.

Teams are still working on resolving the issue but I don't have a specific timeline. I will keep thread updated as we have an update.

The team is testing the solution and we should have an update soon.

As of January 31, 2023, the DI Trial CAL image is no longer available. Please contact your account executive to explore different options available to you.
Refer to the blog https://blogs.sap.com/2022/07/14/sap-data-intelligence-trial-edition-3.2/


Refactor OP & Dataset (#336)

[x] Decouple operator logic from executor. Enabled new interfaces:

[x] dataset = dataset.process(op)
[x] dataset = dataset.process([op1, op2])
[x] dataset = op(dataset)
[x] dataset = op.run(dataset)
⚠ Be careful with non-sharable loguru.logger
[x] #325

[x] Work with Ray.

[x] [skipped] Ray dataset.filter does not have batched version

[x] Work with batched op. All fault-tolerant dataset.map functions must be batched, the following methods are now wrapped:

[x] Mapper.process
[x] Filter.compute_stats
[x] Deduplicator.compute_hash

Next Steps on following PRs:

Check warnings in Ray mode
improve exception handling #331
Docs reflecting the new nice features from this refactor, interfaces, fault-tolerance, ...

Plz carefully resolve the conflicts later @drcege, especially due to #354


pytest-asyncio

Depends on #70

@graingert Thanks. There's no anyio in orm. Do you mean we add that too?

afaik, orm and databases are designed with Starlette in mind and so should also work with anyio eventually

My guess is your PR in databases anyio port should go first.


ui: rename autoscale instance group to simply autoscaling group

This just renames UI label from autoscale instance group to autoscaling group.
Shorter name in the UI menu/navigation makes it break less on some screens.
This was suggested by @msinhore
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

@blueorangutan ui

@rohityadavcloud a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan ui

@rohityadavcloud a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.


Adds WebUI support for QR code URL and parameters

On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
modified:   src/keymaster-app/src/KeymasterUI.js
modified:   src/keymaster-app/src/index.js

Resolves #315


Redefinition NEB workflow

Closes #5
@schumannj @u-gajera these are the changes:

I deleted the SCF task from the workflow.archive.yaml of Uday's data.
I fixed the method extract_total_energy_differences to get the initial task as the reference.

The only remaining question is: do we need to connect the tasks in series or is it not necessary?
Please, review before merging so we can give comments and all the changes are made before this is finished and ready to be merged 🙂

this is about what you have defined in the workflow.archive.yaml, right?
I think only the first and the last structure should be input. and the structures and energies of the intermediate images are the output of the workflow.
For the tasks, somehow they are all interconnected, can they be in parralel and in series at the same time, as they basically all happen at the same time but are connected with each other by spring forces.

this is about what you have defined in the workflow.archive.yaml, right? I think only the first and the last structure should be input. and the structures and energies of the intermediate images are the output of the workflow. For the tasks, somehow they are all interconnected. Can they be in parralel and in series at the same time, as they basically all happen at the same time but are connected with each other by spring forces?

yes indeed, it is for the workflow.archive.yaml which in summary, it will be the archive over which we can work for these workflows.
Ok, I think I understand that each image is related with the previous and the next step, I guess that by some interpolation between both configurations in the path. Right? We can of course connect as you were suggesting (i.e., a task X input will be referencing the task X-1 and X+1). Just a doubt: when you connect with X-1 and X+1, are you refering to the structure? So the inputs of image 4 are the run/0/system/-1 of image 3 and the system of image 5? Or also the run/0/calculation/-1?

in the first instance it is some kind of geometric interpolation (different methods exist for this). in further iterations the forces are also inputs, I belive. So probably it should be run/0/calculation/-1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

1 of 5 (20.0%)  changed or added relevant lines in 1 file are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-18.6%) to 46.667%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/nomad_neb_workflows/schema_packages/neb.py
1
5
20.0%

Files with Coverage Reduction
New Missed Lines
%

src/nomad_neb_workflows/schema_packages/neb.py
9
40.54%

Totals

Change from base Build<PHONE_NUMBER>:
-18.6%

Covered Lines:
21

Relevant Lines:
45

💛  - Coveralls

Is merging blocked here?

Is merging blocked here?

no no, I did merge no problem (I was just waiting for your reviews and approvals)


Exclude canceled orders

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/PT-7441.
Please use this issue to track the state of your pull request.

I have imported this one. We will have to discuss if this is an individual option or a general solution. Maybe this excluded dataset is relevant to companies for statistics.

hey @shyim I will close this PR, as we don't want to change the behaviour in general


Question on the input dimension and the image size

Thank you for the wonderful code.
I have a simple question regarding the input dimension.
I created the model and the input layer has input dimension of [(None, 80, 80, 3)], which is simply the patch size, and the output dimension of the SR layer is (None, 320, 320, 3).
I trained, and evaluated with the LR image size of 330x305 and SR size of  1320x1220, and my question is how can the model input 330x305 and output 1320x1220 while it has input layer dimension of 80803 and output layer dimension of 320*320?
It is not strictly a code issue, but I was really curious about this part.

Figured it out. path size is used in training and during eval, it is set to None.


Find multi-component objects in NVSS and TGSS

Using #31

And look at them in cut-outs

http://tgssadr.strw.leidenuniv.nl/hips/

@daccordeon Can you put a few pictures of "multi-component" objects into your report? reminiscent of #36.
No worries if you don't get time though

See comment in issue #31 , the best I've currently got are two blobs right next to each other, will keep might keep searching for something that looks convincing due to something other than separation.

I'll leave this open for you then.

See comment in #31 for blob examples.


feat!: Rename to stroke_order_animation_controller.dart

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #57

PR #58

PR #59

PR #60   👈

PR #61

PR #62

This stack of pull requests is managed by Graphite.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #57

PR #58

PR #59

PR #60   👈

PR #61

PR #62

This stack of pull requests is managed by Graphite.

Merge activity

Jan 12, 7:50 AM: @Mr-Pepe started a stack merge that includes this pull request via Graphite.


Support access devspace UI from outside an VM (virtualbox)

Is your feature request related to a problem?
No
Which solution do you suggest?
I would like to be able to open the devspace UI in the browser running on the host machine while devspace is running in a virtual machine. Therefore a route is needed going from the host to devspace on the VM, which is mostly done by configuring static port forwarding rules in virtualbox. For this, it is necessary that the UI can also be bound to a fixed IP and not only to localhost. A setting for changing the port number already exists.
It would also be nice if this setting could be added into the devspace.yml.
Which alternative solutions exist?
Opening an ssh connection into the virtual machine with the additional parameters "-L 8099:localhost:8090" enables to open the page localhost:8099 on the host, but this is very unintuitive.
Additional context
Please see this example in my github repository where I have set up the creation of three virtual machines with vagrant and ansible, creating a nearly full working kubernetes cluster and for which the final state is now to have devspace working out of the box.

/kind feature

@DanielGlaas thanks for reporting this issue! Yes, sounds like a good idea, we can add this setting

@DanielGlaas this should work now in v5.0.3

Very nice, running devspace ui --host a.b.c.d --port xyz works like a charm! Its great that you implement this within one week!
Is it also possible to specify the default parameters for host and ports somewhere in the config files?

@DanielGlaas yes its possible, however not through the config itself. Rather you'll have to create a .env file and add an environment variable which specifies this as default flag. You can checkout https://devspace.sh/cli/docs/configuration/env-file for more information

Yes, creating a .env file with "DEVSPACE_UI_FLAGS=--host a.b.c.d --port xyz" works very nice.
One final question:
In the docs for the .env file this is written in Precedence:

Variables defined in your .env file take precende over the default values defined for config variables (configured in the vars section of devspace.yaml).

My interpretation was that I also could add this variable - instead defining it in the .env file - in the vars section of devspace.yml. I created the variable DEVSPACE_UI_FLAGS there but that had no effect. Also creating other variables have no effect and are not listed by devspace list vars until they are really used somewhere in the config.
I assume this is the intended behaviour?
I only figured this out by try & error, but not by reading the manual. Maybe the page vars-->Basics could be extended to explain this explicitly.

@DanielGlaas Yes, that is indeed intended behavior. The execution order is:

get env vars from environment (.env + regular env vars)
start command execution
parse command args/flags
load config (including config vars)
run command functionality

That is pretty much how all cli frameworks are executing things. So because command args/flags are parsed (3) before the config can even be loaded (3), the vars in the config cannot have any impact on the command args/flags. However, for any other env vars, the config can be used as well as .env as well as env vars in your terminal.

Ok, thanks for this clarification.
I'm not aware of cli frameworks in principle, so maybe it is just a lack of my personal experience that I asked this question.


Fix and differentiate favicon

(#2)

Differentiates favicon with fa-link
Fixes:

Adds SVG favicon

Feel free to add yourself to the contributors list in the README @lx-is!


[Event Requests] codeunit "VAT Entry - Edit" - OnAfterVATEntryModify

Please add a new event to codeunit "VAT Entry - Edit":
  trigger OnRun()
  begin
        ...
	VATEntry.Modify();
+	OnAfterVATEntryModify(VATEntry, Rec);
	Rec := VATEntry;
  end;

+ [IntegrationEvent(false, false)]
+ local procedure OnAfterVATEntryModify(var VATEntry: Record "VAT Entry"; FromVATEntry: Record "VAT Entry")
+ begin
+ end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 12553.


Is there a way to get the status code when we have written to a characteristic?

Hello there,
At the moment, we are trying to find a way to access the status code provided by (for instance, Android in the BluetoothGattCallback) as I need to process that information for my device.
The problem we are experiencing is, our device could return a non-standard status code and we want to access this after we have written to the device.
Checking the Characteristic implementation I can see that WriteNativeAsync method ignores the status code (or does not do anything meaningful with it) and I wonder, is there a way to bubble it to the consumer?

Hi @rodrigoelp,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!


Making minsPerResolution configurable in cluster.go

What does this PR change?

Make the minsPerResolution Configurable with ETL_RESOLUTION_SECONDS env variable.

Does this PR relate to any other PRs?

No

How will this PR impact users?

I have tried to keep this most least breaking change, to avoid impact on user

Does this PR address any GitHub or Zendesk issues?

Closes ... #1291

How was this PR tested?

Yet to device a test plan tomorrow

Does this PR require changes to documentation?

No

Have you labeled this PR and its corresponding Issue as "next release" if it should be part of the next Kubecost release? If not, why not?

Will discuss it tomorrow.

Hello @AjayTripathy ,
I kept the changes as minimal as possible but just to be sure the function in costmodelenv still default to 1m for prometheus i hope the customers impacted have thanos enabled or this PR need more code change.
Not sure if  it in this scope or not but i changed all the hardcoded values of minPerResolution or of only line No 391. One of line the hardcoded value was 5 not sure how it will impact but will have to check with yall tomorrow.
CC: @michaelmdresser

Merging this code in next 30min,
Testing coducted:
Uploaded KCM image to test cluster and saw the minsPerResolution sets to default 1m
Ran go test on opencost and KCM repos.
Added the log debug statement as asked in this PR review comments by @michaelmdresser (want to give a final look?)
-Alan

Tested the scenario to check assets over 7 days, merging the code !

@avrodrigues5 Looks like you closed instead of merging. Reopening.


[ERROR] Failed to fix nested if: Expected outer if to have indented body and no else

ruff version: 0.0.230
a = True
b = True

if a:
    if b:
        print('do something')  # noqa: T201
else:
    print('at else')  # noqa: T201

Running ruff here will result with:
test.py:4:1: SIM102 Use a single `if` statement instead of nested `if` statements

If we try to autofix we get [2023-01-22][23:09:59][ruff::rules::flake8_simplify::rules::ast_if][ERROR] Failed to fix nested if: Expected outer if to have indented body and no else

Apart from the autofix error, this is a false positive, right?!

Looks like a regression introduced in #2050 \cc @harupy

I'll either fix or revert that for now

Apart from the autofix error, this is a false positive, right?!

It's a really tricky false positive.
I think if you "fix" to this code:
if a and b:
    print('do something')  # noqa: T201
else:
    print('at else')  # noqa: T201

Then only if a=True and b=False you get different program flow. Original code would not print anything, while fixed code would go in the else.
On the other hand, the places where it showed up in our code, did require some refactoring, so I don't count it as a total loss.

Yeah, I do consider it a false positive because the suggested fix actually has different behavior and semantics.

Ok, this should be fixed in the next release (either tonight or tomorrow morning).