Technical expert ism needed

Hi Team,
i am looking for expert who can customize PH7software to my need
1.publish android app
2.add subscription
3.allow real men/women to respond to clients request
example
https://invisiblegirlfriend.com/
my email is<EMAIL_ADDRESS>

I can do it
On Fri, Dec 6, 2019, 10:15 AM samuelkinyanjui<EMAIL_ADDRESS>wrote:

Hi Team,
i am looking for expert who can customize PH7software to my need
1.publish android app
2.add subscription
3.allow real men/women to respond to clients request
example
https://invisiblegirlfriend.com/
my email is<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGIHSH3VG2LG6XX7W5LQXIJ3XA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6RXKQQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI4NAGKLZFJ2GRJYHYE2E6TQXIJ3XANCNFSM4JWQ6KSQ
.

what will be the cost?time it will take?
On Fri, Dec 6, 2019 at 12:19 PM Hykelauncher<EMAIL_ADDRESS>wrote:

I can do it
On Fri, Dec 6, 2019, 10:15 AM samuelkinyanjui<EMAIL_ADDRESS>wrote:

Hi Team,
i am looking for expert who can customize PH7software to my need
1.publish android app
2.add subscription
3.allow real men/women to respond to clients request
example
https://invisiblegirlfriend.com/
my email is<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGIHSH3VG2LG6XX7W5LQXIJ3XA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6RXKQQ
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AI4NAGKLZFJ2GRJYHYE2E6TQXIJ3XANCNFSM4JWQ6KSQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=ABXZ5ZOIPNADPJVOZFWKEP3QXIKJNA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDQHFA#issuecomment-562496404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXZ5ZPPFCTHVLADOREPGPDQXIKJNANCNFSM4JWQ6KSQ
.

What's ur budget, but it will take up to a month
On Fri, Dec 6, 2019, 10:37 AM samuelkinyanjui<EMAIL_ADDRESS>wrote:

what will be the cost?time it will take?
On Fri, Dec 6, 2019 at 12:19 PM Hykelauncher<EMAIL_ADDRESS>wrote:

I can do it
On Fri, Dec 6, 2019, 10:15 AM samuelkinyanjui<EMAIL_ADDRESS>wrote:

Hi Team,
i am looking for expert who can customize PH7software to my need
1.publish android app
2.add subscription
3.allow real men/women to respond to clients request
example
https://invisiblegirlfriend.com/
my email is<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<

https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGIHSH3VG2LG6XX7W5LQXIJ3XA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6RXKQQ

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AI4NAGKLZFJ2GRJYHYE2E6TQXIJ3XANCNFSM4JWQ6KSQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=ABXZ5ZOIPNADPJVOZFWKEP3QXIKJNA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDQHFA#issuecomment-562496404
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABXZ5ZPPFCTHVLADOREPGPDQXIKJNANCNFSM4JWQ6KSQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGLUI5K6YWHZMUWRN3TQXIMMBA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDRWXA#issuecomment-562502492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI4NAGNSRREXZPIDNSFUALDQXIMMBANCNFSM4JWQ6KSQ
.

i have few additional features
Dating site combined with these features
what i mean is one can select real man/woman or select virtual
men/women/girls
Real men the clients  can meet face to face or chat one on one
virtual men are only for chat/advice(one virtual man can advice many women
and viseversa)
Virtual men/women are configured by visitors customizing the look and feel
virtual men can have categories-  business /professionals /businessmen
/teachers/doctors etc
clients pay for prescription monthly like 1 USD and billed for text SMS
sent maybe one dollar for 20 sms/text  to the phone
The payment gateway need to be able to accept card/mobile money etc(I can
provide code for mobile money)
If prescription expire one get text message to renew and account is locked
after 3 days expiry
For text SMS/text one have to buy in advance and will not receive text/SMS
if depleted
On Fri, Dec 6, 2019 at 1:22 PM Hykelauncher<EMAIL_ADDRESS>wrote:

What's ur budget, but it will take up to a month
On Fri, Dec 6, 2019, 10:37 AM samuelkinyanjui<EMAIL_ADDRESS>wrote:

what will be the cost?time it will take?
On Fri, Dec 6, 2019 at 12:19 PM Hykelauncher<EMAIL_ADDRESS>wrote:

I can do it
On Fri, Dec 6, 2019, 10:15 AM samuelkinyanjui <
<EMAIL_ADDRESS>wrote:

Hi Team,
i am looking for expert who can customize PH7software to my need
1.publish android app
2.add subscription
3.allow real men/women to respond to clients request
example
https://invisiblegirlfriend.com/
my email is<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<

https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGIHSH3VG2LG6XX7W5LQXIJ3XA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6RXKQQ

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AI4NAGKLZFJ2GRJYHYE2E6TQXIJ3XANCNFSM4JWQ6KSQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=ABXZ5ZOIPNADPJVOZFWKEP3QXIKJNA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDQHFA#issuecomment-562496404

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ABXZ5ZPPFCTHVLADOREPGPDQXIKJNANCNFSM4JWQ6KSQ

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=AI4NAGLUI5K6YWHZMUWRN3TQXIMMBA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDRWXA#issuecomment-562502492
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AI4NAGNSRREXZPIDNSFUALDQXIMMBANCNFSM4JWQ6KSQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=ABXZ5ZMNDH7IWNI2U4PU3XTQXIRXJA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDVNMY#issuecomment-562517683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXZ5ZMOOZIQOX46RPO2HXTQXIRXJANCNFSM4JWQ6KSQ
.

the software has all this features in it

OK name the cost?your charges
i have no specific budget  as it is just an idea i want to tryout
On Fri, Dec 6, 2019 at 1:32 PM Hykelauncher<EMAIL_ADDRESS>wrote:

the software has all this features in it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pH7Software/pH7-Social-Dating-CMS/issues/679?email_source=notifications&email_token=ABXZ5ZIOV7KMSGISTEKEFBDQXIS2HA5CNFSM4JWQ6KS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGDWFEA#issuecomment-562520720,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXZ5ZPR2H5LUDPYLMDQXVDQXIS2HANCNFSM4JWQ6KSQ
.

@samuelkinyanjui Hi there !
I don't feel like you know what's a software development project. A budget is needed ahead so we can define the limits we'll be having.
For example if you give a 10 000$ budget to develop a text editor then I'll be able to take some part of the budget for bug finding. If you only give me 1 000$ then I will probably be extending an existing text editor to suit your need.
I'd suggest you start by making a established list of what you want and how you want it. How much you can afford, the priority of each elements. When you do software development there's always surprise down the  road so the fix priority ahead is a good thing. This way the developer will know what to choose if he's short on budget.
This only prevent confusion later on.
The more serious you will look in your request, the more chance you will get to have someone serious do your job. Only some hints so you don't waste your money,


adds implementation of API for compile.js

This is a first version, it needs some more testing which I'll do shortly but it's a good showcase.  See also the new commits in API viewer

Instead of reading compile.json from disk, would you consider using the config API? see usage here. This makes sure that the file has the correct schema (or will be migrated if possible).

@johnspackman  I wonder: with the LibraryConfig and CompilerConfig classes, what are you actually modeling? I am a bit worried we duplicate qx.tool.config.Abstract and its subclasses here. The methods of CompilerConfig could actually be integrated into qx.tool.config.Compile. LibraryConfig is different, but the load() method does not actually refer to loading library data (which would be the equivalent of loading compiler config data), but is just a hook for running library-specific code. I understand what you're trying to do, but it doesn't seem completely right and I wonder if there was a more intuitive and elegant solution for the real problem we are trying to solve.

I am all for returning a class/classes from compile.js which have a proper API. But I wonder if rather than having two separate classes, if a "sandbox object" would be easier to reason about, which would have a unified, easy API and which would contain necessary data, forward lifecycle events from the compiler object so that libraries can run code and manipulate config data.

What's being modelled is an API to allow the application and libraries to interact with the compiler, and currently the only mechanism is to allow them to find alternative ways to generate a configuration.  For many applications, that just means loading a file but could be returning an object etc; for libraries like API viewer, that means adding environment settings but could also involve loading files.
WRT the config API, I don't think there is a lot of overlap - although I think that it would be helpful if the package name was "API" rather than another "Config".
CompilerConfig class does not use the config API is because it is just a means to generate a config, which by default is just by loading a compile.json file but that is not necessarily true - for example, it may generate one without loading anything (which could be a common use case, you wouldn't necessarily want to keep your static JSON data separate from your code that manipulates it).
File which are loaded do not have to confirm to the compile.json schema (or any other schema), but what it outputs must comply.  There's no reason why, for example, the configuration can't be invalid (from a compile.json schema perspective) until after all of the libraries have had their opportunity to add to the configuration.
The schema validation still happens elsewhere in the compiler, I havn't changed that - but it happens on the final output and not intermediate fragments

I am all for returning a class/classes from compile.js which have a proper API. But I wonder if rather than having two separate classes, if a "sandbox object" would be easier to reason about, which would have a unified, easy API and which would contain necessary data, forward lifecycle events from the compiler object so that libraries can run code and manipulate config data.

I don't really follow, the reason that the CompilerConfig and LibraryConfig are separate is because there can be multiple LibraryConfig's and one CompilerConfig; this is modelling the state which contributes to the final configuration.  We could merge it into one class, but then the individual library's compile.js would have to export some kind of state or functions to perform various tasks, whereas this way they just extend an OO class as usual.
For example, qx package install ... manipulates the application's compile.json in order to add applications to the applications[] array, but it might be useful to allow the library to choose how it's added so that special settings for theme or environment can be injected.  Similarly, installing a library via qx might makje choices (including asking the user questions) about merging theme's etc.  To implement any of that kind of thing, LibraryConfig would have methods added which provide default implementation, and the library's compile.js can provide a class derived from LibraryConfig which overrides the method.
I'm changing the names in the next commit to API, so maybe that makes more sense?

@johnspackman Ok, we're probably solving different problems. I am deferring on your judgement here. However, we have to document the solution well in the documentation and the API Viewer, because I didn't understand it the first time.

I think you're right that it is a different problem - effectively, this sets the groundwork for a generic API to the CLI, from the point of view of compiling a project (ie where you run qx compile) and the libraries (which can, but does not always, include ".").  And the only API method that is implemented so far is a glorified replacement for qx.tool.util.Json.loadJsonAsync("compile.js"), and schema is added later.
Documentation is written and in https://github.com/qooxdoo/qooxdoo/pull/9701, hope it makes more sense now.
Also, when writing the docs it occurred to me that libraries don't need to have code for the project being compiled to be useful - see here for the SASS compiler example


Fixes bug where partial pipelines from abandoned login attempts will be resumed …

…on new login attempts. This can happen with the email backend, which sends data directly to auth:complete, thereby bypassing the call to clean_partial_pipeline in do_auth.
More info:
During testing we ran into an issue with old session data from uncompleted email verifications sticking around while trying to login with other accounts. No matter what data you typed into the form, it would send you to a page saying a verification was sent to the email address inside the session's partial pipeline.
After looking through python-social-auth's code, I thought this was the best place to check that any new data, such as an email, matches what's in the current partial pipeline data; it seemed like the best place since it also verifies the backend names match.
Normally this isn't an issue since do_auth calls clean_partial_pipeline, but the email backend only works when you send data directly to the "complete" handler.

Good idea, thanks!


Add the ability to add clickable links to properties

Description
Sometimes you need to add links to swagger, documentation, or something else to the properties of an object. Please add the ability to hover over the tooltip and click on the links posted there.
Priority
I'm willing to add this feature myself and raise a PR (please confirm approach first)
More information
No response

@simonbrowndotje, good day.
We need this functionality to place links to various resources in properties. It seems to me that it is quite useful to use.
We are ready to prepare changes and make PR, if you don't mind our idea.

https://github.com/structurizr/ui/assets/77280748/18d814d7-ff95-4a86-9388-119419dc3168

"Sticky toolips" are already supported by holding the Alt key (https://docs.structurizr.com/ui/diagrams/keyboard-shortcuts#viewing-diagrams) ... is this not working for you?

Оh, realy. It working, very good.
Thank you.


Incorrect multiple file append behaviour for MudFileUpload with MaximumFileCount

Bug type
Component
Component name
MudFileUpload
What happened?
The behaviour for MudFileUpload with AppendMultipleFiles="true" and MaximumFileCount="N" is, in my opinion, incorrect. Selecting > N files will correctly cause the list of files selected in the file dialog to be discarded. However, regardless of the current length of the file list, it is possible to grow the list to > N files by opening a file dialog a second time and selecting a new list of <= N files.
Expected behavior
If MaximumFileCount is set then the resulting list of files should never be longer than the set value.
Although this could be corrected by a developer in an event callback, I believe that the correct behaviour should be for the component to truncate the file list to the last N files in the context list object.
Reproduction link
https://try.mudblazor.com/snippet/7VJBTsMwELz3Exif2kv6gTgKVEJUIgXRwLVamg1Y2tiR4wCl6t9x0iglijnBsb7Y2p2dnUxms0lAqsDAlzYXYVJnN5LwqSQNGUsFXz4iZPeKdneysuHy2uiPCk2DiTi7KktUWVKTlSVhU6yiCXMnvK6t1SrFoiSweCy2Dbfg2GO3tqAUXgUneEHiPeTHeQYjQVnBu0fgVhBmXuxCkzaCt1fwYGQBZucFri0Yu9xqJXjcXFWQOImOnzr6YEG6zo4WeBnyZlHsRi1-Wh4NIB5LmGDW1HjyYN6b0Lk199kVrpFwazEbuxjLnE27_exSMFUTzfrufiAodmoRtm9s-g6G5U4Qk4p1w7MBdD_62OZ3pQ4Xxc1gsIICW_VtbYA-TMYvpAp_UdUTrzRrTfLQHjpzxj604FNOo8nk78EVPAenl58D7Atw6805wT7if0nwNw
Reproduction steps

Press the button
Select 4 files to open for upload
Press open
Press the button again
Select up to another 4 files
You now have > 4 files in the list for upload

Relevant log output
No response
Version (bug)
6.7.0
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[X] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We should start a discussion, on whether to change this behavor, currently this is not a bug, but by design.
Here is the function:
private async Task OnChange(InputFileChangeEventArgs args)
        {
            if (GetDisabledState()) return;
            if (typeof(T) == typeof(IReadOnlyList<IBrowserFile>))
            {
                var newFiles = args.GetMultipleFiles(MaximumFileCount);
                if (AppendMultipleFiles && _value is IReadOnlyList<IBrowserFile> oldFiles)
                {
                    var allFiles = oldFiles.Concat(newFiles).ToList();
                    _value = (T)(object)allFiles.AsReadOnly();
                }
                else
                {
                    _value = (T)newFiles;
                }
            }
            else if (typeof(T) == typeof(IBrowserFile))
            {
                _value = (T)args.File;
            }
            else return;

            await FilesChanged.InvokeAsync(_value);
            await BeginValidateAsync();
            FieldChanged(_value);
            if (!Error ||
                !SuppressOnChangeWhenInvalid) //only trigger FilesChanged if validation passes or SuppressOnChangeWhenInvalid is false
                await OnFilesChanged.InvokeAsync(args);
        }

Thanks for the reply.
I would want to see either the behaviour change, or the documentation change. Currently, I don't think the two line up. The summary for MaximumFileCount is Maximum number of files that can be uploaded, but it only serves to limit the number of files the user can select in the file dialog. By concatenating the old and new file list the number of files that can be uploaded, without any other checks in place, is unlimited. And personally I don't know of a use case where it makes sense to limit the number of files that can be selected in one instance of the file dialog when overall there is no actual hard limit on the size of the file list.
My ideal behaviour for the component would be that MaximumFileCount sets both the limit on the number of files that can be selected in the file dialog and the size of the file list to be uploaded. In the case that the count is exceeded, files remain in the list in a first in, first out order.
Otherwise I would change the documentation to be more reflective of the actual behaviour of the component. So MaximumFileCount would be something like Maximum number of files that can be selected in the file dialog. Selected files will be appended to the existing list of files to be uploaded.
Interested to hear what others may think about this.

@Mr-Technician

@DennisOstertag @Mr-Technician my apologies for letting this issue lapse for a while.  Changing the summary for the property seems like an acceptable resolution.
Although it's a trivial change, would you like me to create a pull request to implement the change?

Please do and request a review from me


Custom tracker support?

Not sure if this is the right place to ask...
I'm looking for a solution that we can build custom tracker hardware (like a full body tracking suit).
I found HiveTracker working with LH1.0.
Another project here using TS4231: https://hackaday.io/project/19570-htc-vive-lighthouse-custom-tracking
And Lots of LH2.0 protocol hacking working from here: https://github.com/cnlohr/esptracker
So I'm not sure where to start... Does this project suppose to support 3rd-party trackers in the future? Is this a good place to start if I want to build a 3rd party tracker working with LH2.0?
Thanks

In short, yes. The longer answer is there is a plugin system and a custom tracker would be exposed as a driver plugin for the project.
If it's custom hardware -- trackers and firmware and all -- you'd need to write that driver. If you use one of the vive HDK's, it should work with the vive driver. Those drivers tend to be as complicated or as simple as whatever the hardware is doing. I'd look at driver_vive.c as a reference implementation, but the basics of it are that you'll call handle_lightcap with light data and it takes it from there. You can also call the raw_imuproc callback to propagate IMU messages.

In short, yes. The longer answer is there is a plugin system and a custom tracker would be exposed as a driver plugin for the project.
If it's custom hardware -- trackers and firmware and all -- you'd need to write that driver. If you use one of the vive HDK's, it should work with the vive driver. Those drivers tend to be as complicated or as simple as whatever the hardware is doing. I'd look at driver_vive.c as a reference implementation, but the basics of it are that you'll call handle_lightcap with light data and it takes it from there. You can also call the raw_imuproc callback to propagate IMU messages.

Thank for the reply and those pointers. I'll start from there!


Regarding expression in Aggregators

Hi team,
Just a quick question here.
I saw the "expression" parameter is added into some aggregators from source code.  I tested it slightly and it works.
But I don't' find the documentations about it. Is it ready for production use now?
Best regards,
Ryan

Hey @fanwu72
I can't speak for the original authors but the expressions and virtual columns are used in the queries generated by SQL so it seems fair to follow the same guidelines that they're an experimental feature subject to change.
There's an open issue to document them here: https://github.com/druid-io/druid/issues/3634

@Dylan1312 Thanks for the explanation.


Fix #32

Fixes #32

Added futures-03-sink to async-tungstenite's features.
Fixed a bug in async-tungstenite (see PR) and changed the dependency to use that PR for now

I'll wait with merging this to see if we can get rid of the git dependency.

async-tungstenite merged the patch and I bumped the dependency.
But when compiling for wasm I get:
error[E0310]: the parameter type `Fut` may not live long enough
  --> /home/emma/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/futures_unordered/task.rs:81:9
   |
81 |         waker_ref(this)
   |         ^^^^^^^^^^^^^^^
   |         |
   |         the parameter type `Fut` must be valid for the static lifetime...
   |         ...so that the type `Fut` will meet its required lifetime bounds
   |
help: consider adding an explicit lifetime bound
   |
78 | impl<Fut: 'static> Task<Fut> {
   |         +++++++++

I got this error before while investigating the async-tungstenite bug, but could not reproduce.

This error is caused by some dependency pulling in futures-util 0.3.30, which has been yanked (might be related to this). Pinning futures-util to >=0.3.31 fixes this.


Passing ListHeaderComponent and/or ListFooterComponent throws errors on drag

Describe the bug
Passing ListHeaderComponent and/or ListFooterComponent cause somewhere inside react-native-draggable-flatlist to raise TypeError: Attempted to assign to readonly property (node._store), which seems to be related to this.
To Reproduce
I don't have one at the moment. We aren't using expo, and I couldn't get Expo Snack to install the reanimated library.
Platform & Dependencies

react-native-draggable-flatlist version: 4.0.1
Platform: iOS and Android
React Native: 0.70.9
Reanimated version: 3.3.0
React Native Gesture Handler version: 2.12.0

Hitting the same issue. If I remove the ListHeaderComponent then the issue goes away. (But I need to use the header component...)
react-native-draggable-flatlist: 4.0.1
Platform: iOS and Android
React Native: 0.71.8
Reanimated: 3.1.0
React Native Gesture Handler: 2.7.1

Also works
react-native-draggable-flatlist: 4.0.1
Platform: iOS and Android
React Native: 0.72.4
Reanimated: 3.4.2
React Native Gesture Handler: 2.12.1

Patch
diff --git a/node_modules/react-native-draggable-flatlist/src/components/DraggableFlatList.tsx b/node_modules/react-native-draggable-flatlist/src/components/DraggableFlatList.tsx
index d7d98c2..183d431 100644
--- a/node_modules/react-native-draggable-flatlist/src/components/DraggableFlatList.tsx
+++ b/node_modules/react-native-draggable-flatlist/src/components/DraggableFlatList.tsx
@@ -402,14 +402,22 @@ function DraggableFlatListInner<T>(props: DraggableFlatListProps<T>) {
}

function DraggableFlatList<T>(
-  props: DraggableFlatListProps<T>,
+  {
+    ListFooterComponent,
+    ListHeaderComponent,
+    ...props
+  }: DraggableFlatListProps<T>,
 ref?: React.ForwardedRef<FlatList<T>> | null
) {
 return (
   <PropsProvider {...props}>
     <AnimatedValueProvider>
       <RefProvider flatListRef={ref}>
-          <MemoizedInner {...props} />
+          <MemoizedInner
+            {...props}
+            ListFooterComponent={ListFooterComponent}
+            ListHeaderComponent={ListHeaderComponent}
+          />
       </RefProvider>
     </AnimatedValueProvider>
   </PropsProvider>

react-native-draggable-flatlist+4.0.1.patch

Not able to pass components directly, which causes re-rendering issues.
Kindly help with a patch


panel brightness cannot be changed

Hi. i have a little problem. i have tried ChainedPanels sketch example with esp32 s3 n16r8 but i can't change the brightness of the panel, i have changed the brightness from value 10-255 but it doesn't show any change.

resolved..there was an error in placing the program line in the example.
before
  dma_display->setBrightness8(200); // range is 0-255, 0 - 0%, 255 - 100%

   // Allocate memory and start DMA display
   if (not dma_display->begin() )
     Serial.println("****** !KABOOM! I2S memory allocation failed ***********");

after
   // Allocate memory and start DMA display
   if (not dma_display->begin() )
     Serial.println("****** !KABOOM! I2S memory allocation failed ***********");

      dma_display->setBrightness8(200); // range is 0-255, 0 - 0%, 255 - 100%


[Bug]: CSS modules classNames that use composes breaks if the className is used again in the file

System Info
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
Memory: 29.40 GB / 63.95 GB
Binaries:
Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.2.0 - ~\AppData\Local\pnpm\pnpm.EXE
Browsers:
Edge: Chromium (125.0.2535.79)
Internet Explorer: 11.0.22621.3527
npmPackages:
@rspack/cli: 0.7.1 => 0.7.1
@rspack/core: 0.7.1 => 0.7.1
@rspack/plugin-react-refresh: 0.7.1 => 0.7.1
Details
Writing css modules with compose breaks if you use the className again after composes.
.columnCenter {
  display: flex;
  flex-direction: column;
  justify-content: center;
  align-items: center;
}
.root {
  composes: columnCenter;
  max-width: 1280px;
}
.root.main {
  background-color: #000;
  color: #fff;
}

This generates an export for root without the columnCenter className attached.
Rewriting it like this technically fixes it.
.columnCenter {
  display: flex;
  flex-direction: column;
  justify-content: center;
  align-items: center;
}
.root.main {
  background-color: #000;
  color: #fff;
}
.root {
  composes: columnCenter;
  max-width: 1280px;
}

But ideally, the order of writing should not be an issue.
Reproduce link
https://github.com/keyrun/rspack-cssmodule-issue/blob/main/rspack-dist/src_render_js.js
Reproduce Steps

Run npm run build
In rspack-dist/src_render_js.js the root className should consist of both columnCenter and root but only contains root

Fixed, you can try the latest nightly version


Issue with the shop system

First of: there is already a issue with this content #260
so if you dont need this, you could close this issue
Sponge Version:  spongeforge-1.12.2-2611-7.1.0-BETA-2990
Forge Version:  forge-1.12.2-<IP_ADDRESS>11-universal
Total Economy Version:  TotalEconomy-1.8.0
Description of issue
I dont know what the issue directly is.
I'm the admin of a server and i wanted to test the shops. So i create one, set some items, buy them and then delete the shop.
Now every time i want to join the server, the server crashs.
crash report below.
how to fix this?
how could i join without crashs?
is there a easy way? maybe delete something in a config file?
Console errors
crash-2018-04-22_16.11.14-server.txt
Steps to reproduce
Related Configuration Files
Create a Gist (https://gist.github.com/) for each configuration file related to this issue

I've got exactly the same Problem and i have exactly the same Versions of Sponge/Forge/TotalEconomy.
The first Few Starts were no Problem. Now without any bigger change, the Server starts and after he is done he crashey immediately.
crash-2018-04-23_20.50.57-server.txt

Would you both mind copying and pasting your crash logs into a gist so I can take a look at them?
I plan on looking into this issue tonight, but for now I highly recommend, if possible, to remake the world and disable chest shops from within the main Total Economy configuration file.

Hm creating an new World hm no Option for my Server :P I switched it to Single Player and deleted the chest-shops, copied back and crashes again. Also disabling the chest-shops doesn't prevent the crash.

@Joker4632
A fast fix is to Delete the player file inside the worlder folder.
How to do that:
Find out the uuid of the player who created the shop.
Destroy the shop in the world (if you doesn't have done it already)
Go to your worlds folder
Then inside this folder to
data/sponge
Inside this folder is a file with the uuid (the same as above)
Delete this file, restart the server.
Done.

https://gist.github.com/Witchcrafter1/d22941994b1713b90c9bee1a16a3dc8f#file-crash-server-shop-totaleconomy

Hm the Location in the crash-report is a normal chest, but even if I delete this chest and all shops (using the Singleplayer) and deleting the Files (of the players who created shops and the one who created this chest), the server crashes again

Hmm
What I have done was:
Start the server without totaleconomy (leave the config)
Start it with totaleconomy
Still crashes when I want to join (I created the shop)
Delete my player file
(In world/playerdata/uuid)
Delete my sponge player file
(in world/data/sponge/uuid)
Delete my player data in totaleconomy (I don't use a dB)
(Config/totaleconomy/  player.conf?  Idk the name,  there where the Balance is stored,  with the uuid)
@Joker4632

Ok i could try it with removing all of this Files, but the Server crashes without anyone trying to join...
And the second is, the coordinates in the crash-report, points on a normal chest far away from the first steps on this Server. Don't make sense to me^^
But i will try.
Thx for the Help so far^^

Ok,  it seems that there are some more problems,  maybe a fix will help.
Author works on that, like he said

I quickly tested this out using the steps above and was not able to recreate the issue. Would you mind giving me a step by step of what you do, including the commands you run? This includes creating the claim and creating and stocking the shop.

Puhh, the Problem there is the Server didn't crash while running. We played, stopped the Server over night and when we want to start him again her crashes.
Everybody has default Permissions, so he can use /shop buy, /shop stock (but only two Players including me have bought ah shop so far).
Further they can use /balance (not view/top/set), /pay and /job.
I can't remeber something that could have triggered that issue.
If you want to, i could zip the Server Folder and send it to you, cause i can't tell you the steps to reproduce

Yeah, go ahead and zip it up and send it to me. Thanks.

From the looks of it, the jar that you are both using doesn't seem to have the ShopKeys class, which doesn't make much sense. If possible, would you mind removing all the plugins except for Total Economy and check to see if the issue still occurs. I'd recommend duplicating your current server folder so you have a backup just in case.

Sorry for the late answer. I removed all Mods and Plugins except Spongeforge and TotalEconomy and it works, awesome. But why ^^
I will try to find the problematic Mod/Plugin.

Before I jump to any conclusion, would you mind adding each plugin/mod in one-by-one until the issue occurs again. I know this is tedious but this will help a tremendous amount when it comes to figuring out whether it's an issue with Total Economy or another mod/plugin. Thanks.

So i had to do lot of Stuff last Days, but i checked all Mods and Plugins and found the problematic one.
It was Nucleus (https://ore.spongepowered.org/Nucleus/Nucleus). It overlaps with TotalEconomy with his Server-Shops, even though i did not activate this module of Nucleus.

Did disabling that module in Nucleus fix the crashing issue? If so, is it ok to close this issue?

Interessting. so far I've been using Nucleus without any issues.
Looks like I need to test this.

Same issue here @Erigitic any sign of a possible fix

I think this is the same issue as this: https://github.com/trentech/ProjectPortals/issues/86#issuecomment-362788494
You need to register your keys during init.


Possible to add icons to the project explorer?

Is it possible to add icons to the project explorer in the same way that they are in the file explorer?
Thanks

At the moment - no
I believe it's investigated by Code Team.


Add mill clean

Would be more friendly for newcomers than rm -rf out/ (always dangerous for typos and depends work dir)

It would be great to have it as a project-based command. I often get caching-linking problems with mill ScalaJS projects and it is way faster to clean the scalajs project out by mill command rather than going to appropriate place in out with bash


WIP SMS invitation message

Closes #41

Ready for review, I think. Can use some refactoring, but given the time constraints, something for the future

Just one small issues. Apart from that it looks good. You might want to rebase on development to fix the tests.

Thanks. Looks like the branch is already up to date, though. Looking into why the push build is failing

rebuilding made it pass. going ahead and merging this.
If this test acts up again, I'll take a closer look. I have the impression variations on datetimes each time the builds run are making the slot overlap tests fail.


Fix: Explicitly write soma type

solves #76

I don't get why the try is not covered, as it crashed here: https://github.com/BlueBrain/NeuroTS/actions/runs/6037160854/job/16380883990


feat: Merge 7.0.0-beta to master

Hello, I think it's time to merge 7.0.0-beta to master and release 7.0.0,
although it's a bit late it should be merged last week as scheduled,
anyway, we have run the beta in production for a while (we are on 7.0.0-beta2) and it seems fine,
if any issue occurs after merged I'll be here to help.

I agree with you - I am the delay - the only hold up is that when I test integrated it into my work project and one of the templates it appeared I had breaking changes with regard to where things are located. I'm just not sure if that's intended or not. Since it did not succeed immediately (I thought it would! I was surprised actually) I was not able to just say "go for it". If we have breaking changes on where things are located we must provide a migration of where each symbol moved. If we do not have breaking changes and my project is broken (a strong possibility) then I need to see it run.
Anyway, that's the delay, I'm sorry. I am actually working on almost nothing but this....except also my country's school system went back to virtual classes and now I'm also the science and math tutor at home which is just killing my productivity. All I can do is ask for patience, sorry

@mikehardy No need to be sorry you've done a lot, I appreciated it. Actually, my first thought is me causing the delay, I was wondering if there's anything I've missed to do, so that's why I'm opening this pr. I'll change this to draft and wait for now, or if you want it to be closed, is okay to let me know. Family, body care and work are more important than an open-source project, so just take your time, I'll be patient with it, also feel free to let me know if anything I can do for help.

Okay - so I got a chance to try this on an old project - I just swapped the existing v6 fbsdk-next for a dependency on beta, I get this:
src/screens/PopupTest.tsx(10,31): error TS2307: Cannot find module 'react-native-fbsdk-next/types/FBAccessToken' or its corresponding type declarations.
src/stores/UserStore.ts(1312,9): error TS2345: Argument of type 'null' is not assignable to parameter of type 'GraphRequestConfig | undefined'.

So some of the symbols have moved, but we are not providing any guidance to developers on what symbols moved and where they moved to.
We either need to provide a map for developers of old import locations to new ones, or we need to provide the symbols in the old locations so it's seemless
@rnike do you know which symbols moved? Is it possible to make the symbol locations backwards-compatible?

Also got this one - perhaps the typing is more correct now though?
Argument of type '(error: any, result: object | PromiseLike<object>) => void' is not assignable to parameter of type 'GraphRequestCallback'.
  Types of parameters 'result' and 'result' are incompatible.
    Type 'Record<string, unknown> | undefined' is not assignable to type 'object | PromiseLike<object>'.
      Type 'undefined' is not assignable to type 'object | PromiseLike<object>'.

I think both of the things I saw were objectively my fault, they were me trying some random typings in a project-specific way because the typings weren't great before, but now they are much better. I think it's time

It's out! @rnike this is so cool, thank you again for doing it, and thank you so much for the patience for review and release and stuff. I really hate being a barrier on progress and I'm glad this is out of the way. Going forward if you see pull requests that look obviously good, and you're doing your best, hit that publish button. I don't want to be a barrier ever really, and it's only the really big stuff (like this one) that I think need lots of collaboration. That's my philosophy anyway, in the repos I work on. Cheers!


Window lag

I'm getting this screen lag when scrolling down that only seems to happen with navigator enabled. Do you have any idea which functionality it could relate to? I'm thinking maybe some aggressive auto commands?
This happens when I scroll down all the way to the bottom. It goes away if I press Esc or <C-]>, not on <C-c>.

TBH, I have never seen this before. Might be other settings,
did you enable lazyredraw ?

Hmm okay

did you enable lazyredraw ?

nope.
I will close for now then, if I ever figure out more I might re-open


Remove overridden taint method in assembly

Fixes an endless loop with parent.taint() inside elements, shouldn't break anything because taint is called inside draw anyway

Or am I wrong @jeremyz

I'm almost there, fixing OrthographicCamera usage and Root resizing in tests.

Done.
The purpose of Assembly is to hold the base elements for Root.
If you resize your window, Root calls Assembly.taint() to recompute its coordinates and to tell all the children to recompute their position.
Both are mandatory. try with the UI demo with all the buttons,comment out one of the lines and see what happen.


Implement security measure to protect user data.

A summary of the problem or requirement that this task solves
The backend will use jsonwebtokens to verify a user and maintain security requirements

Clear requirements for how to consider each task or issue "done"
jsonwebtoken is verfied and working properly for customers


Correct description for 'Other Organization' and add missing descriptions for others

The new descriptions are copied from this: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/81d92bba-d22b-4a8c-908a-554ab29148ab

@robinharwood, @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


EggNOG data manager: fix error

A fix for this error:
Traceback (most recent call last):
  File "/blabla/toolshed.g2.bx.psu.edu/repos/galaxyp/data_manager_eggnog_mapper_abspath/9d5f039c637f/data_manager_eggnog_mapper_abspath/data_manager/data_manager_eggnog.py", line 65, in <module>
    main()
  File "/blabla/toolshed.g2.bx.psu.edu/repos/galaxyp/data_manager_eggnog_mapper_abspath/9d5f039c637f/data_manager_eggnog_mapper_abspath/data_manager/data_manager_eggnog.py", line 61, in main
    open(args.config_file, 'wb').write(json.dumps(dm_dict))
TypeError: a bytes-like object is required, not 'str'

By the way, this data manager fails to download the hmm files as they have moved to a new domain, wget gets the 302 response but doesn't download the files:
Total wall clock time: 0.08s
Downloaded: 1 files, 917 in 0s (77.1 MB/s)
--2020-08-19 11:23:30--  http://eggnogdb.embl.de/download/emapperdb-4.5.1/hmmdb_levels/artNOG_hmm/
Resolving eggnogdb.embl.de (eggnogdb.embl.de)... <IP_ADDRESS>
Connecting to eggnogdb.embl.de (eggnogdb.embl.de)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://eggnog5.embl.de/download/emapperdb-4.5.1/hmmdb_levels/artNOG_hmm/ [following]
--2020-08-19 11:23:30--  http://eggnog5.embl.de/download/emapperdb-4.5.1/hmmdb_levels/artNOG_hmm/
Resolving eggnog5.embl.de (eggnog5.embl.de)... <IP_ADDRESS>
Reusing existing connection to eggnogdb.embl.de:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

     0K                                                        77.4M=0s

Last-modified header missing -- time-stamps turned off.
2020-08-19 11:23:30 (77.4 MB/s) - ‘index.html’ saved [941]

Removing index.html since it should be rejected.

FINISHED --2020-08-19 11:23:30--

As the url is hardcoded in the download script, maybe the best would be to just update the eggnog tool/data manager to the latest version of eggnogmapper? Any way they seem to have removed the hmm search mode in v2.x.

So this fix will not help you isn't it since the URL is still broken? In this case, an update is probably the correct thing to do.

It will help as currently the data_manager doesn't work at all, while with this patch it works at least for diamond eggnog db, which is better than nothing
Maybe I can look into a full update, dont know if I'll have the time

Thanks!


fail on import of ses_backend from moto.ses

Hi,
from version 3.1.12 we fail on this error :
from moto.ses import ses_backend
E   ImportError: cannot import name 'ses_backend' from 'moto.ses' (/root/.local/share/virtualenvs/build-3vGKWv3F/lib/python3.8/site-packages/moto/ses/init.py)
can you help?

@bblommers I'm from @yaronbenezra and you solution worked, thanks for your help!

Happy to help!


Um call router settings

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

this should hopefully have us close off issue #262

Codecov Report

Merging #345 into dev will increase coverage by 0.58%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##              dev    #345      +/-   ##
=========================================
+ Coverage   32.22%   32.8%   +0.58%
=========================================
  Files          39      39
  Lines        4671    4689      +18
=========================================
+ Hits         1505    1538      +33
+ Misses       3166    3151      -15

Impacted Files
Coverage Δ

...RouterSettings/MSFT_xExchUMCallRouterSettings.psm1
100% <100%> (+57.69%)
:arrow_up:

Continue to review full report at Codecov.

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


[MM-37797] Re-added the check for flashing the window

Summary
The setting determining whether the window should flash or not on Windows/Linux when a new mention arrives was not being checked before flashing the window, so we've re-added the check.
Ticket Link
https://mattermost.atlassian.net/browse/MM-37797
Release Note
Fixed an issue where the window would flash on Windows/Linux when a new mention arrives regardless of the setting to turn it on/off.

@amyblais Let me know if you'd like to cherry-pick this to v4.7

/cherry-pick release-4.7

Error trying doing the automated Cherry picking. Please do this manually
fatal: No such remote 'upstream'

+++ Returning you to the master branch and cleaning up.

Cherry pick is scheduled.


Pol 390 add name field to escalation block

Pol 390 add name field to escalation block
Updated policies escalation label to maintain consistency
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          185 Errors

:no_entry_sign:
Checking cost/scheduled_report_markUpsDowns/scheduled_report_markpsdowns.pt
An unexpected error occurred: failed to unmarshal policy template content

:no_entry_sign:
Checking cost/scheduled_reports_with_estimates/costs_forecasting.pt
An unexpected error occurred: failed to unmarshal policy template content

:no_entry_sign:
cost/aws/reserved_instances/compute_purchase_recommendation/CHANGELOG.md:7: MD022 Headers should be surrounded by blank lines
cost/aws/reserved_instances/compute_purchase_recommendation/CHANGELOG.md:8: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/budget_v_actual/CHANGELOG.md:1: MD002 First header should be a top level header
cost/budget_v_actual/CHANGELOG.md:7: MD022 Headers should be surrounded by blank lines
cost/budget_v_actual/CHANGELOG.md:11: MD022 Headers should be surrounded by blank lines
cost/budget_v_actual/CHANGELOG.md:9: MD032 Lists should be surrounded by blank lines
cost/budget_v_actual/CHANGELOG.md:13: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
saas/fsm/unsanctioned_spend/CHANGELOG.md:17: MD012 Multiple consecutive blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
Policy Template path should be lowercase. cost/scheduled_report_markUpsDowns/scheduled_report_markpsdowns.pt

:no_entry_sign:
cost/aws/schedule_instance/CHANGELOG.md#L15 - Found trailing spaces at line’s ending(editorconfig)

:no_entry_sign:
cost/downsize_instance/CHANGELOG.md#L29 - /rightscale/policy_templates/cost/rightlink_utilization/README.md is dead. (ENOENT: no such file or directory, access ‘/rightscale/policy_templates/cost/rightlink_utilization/README.md’)(no-dead-link)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L22 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L23 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L24 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L25 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L26 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L27 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L28 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/dbaas/aws/rds_backup/CHANGELOG.md#L29 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L22 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L23 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L24 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L25 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L26 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L27 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L28 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L29 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L30 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L31 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L32 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L33 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L34 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L35 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L36 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L37 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L38 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L39 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L40 - Found wrong EOL(editorconfig)

:no_entry_sign:
operational/snapshots/CHANGELOG.md#L41 - Found wrong EOL(editorconfig)

:no_entry_sign:
saas/okta/inactive_users/CHANGELOG.md#L17 - Found trailing spaces at line’s ending(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L22 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L23 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L24 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L25 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L26 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L27 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L28 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L29 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L30 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L31 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L32 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/icmp_enabled/CHANGELOG.md#L33 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L22 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L23 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L24 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L25 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L26 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L27 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L28 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L29 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L30 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L31 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L32 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L33 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L34 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L35 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L36 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L37 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L38 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L39 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L40 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L41 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L42 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L43 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L44 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L45 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/rules_without_descriptions/CHANGELOG.md#L46 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/security_groups/world_open_ports/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L9 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L10 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L11 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L12 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L13 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L14 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L15 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L16 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L17 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L18 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L19 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L20 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L21 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L22 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L23 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L24 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L25 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L26 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L27 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L28 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L29 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L30 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L31 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L32 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L33 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L34 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L35 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L36 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L37 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L38 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L39 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L40 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L41 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L42 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L43 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L44 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L45 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L46 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L47 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L48 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L49 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L50 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L51 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L52 - Found wrong EOL(editorconfig)

:no_entry_sign:
security/storage/aws/public_buckets/CHANGELOG.md#L53 - Found wrong EOL(editorconfig)

:warning:

        Danger found 185 violations with this PR. Due to GitHub's max issue comment size, the number shown has been truncated to 184.

  Generated by :no_entry_sign: Danger

          1 Error

:no_entry_sign:
Checking cost/aws/rds_instance_license_info/rds_instance_license_info.pt
1 syntax error found:
  origin: template: rds_instance_license_info.pt, line: 229
  problem: Export declared multiple times
  summary: Policy validate export declared multiple times.
  resolution: Only declare export once. Only one data table may be exported per incident.

  Generated by :no_entry_sign: Danger


Added included functionality to preprompts

In DB.get_item()
file processing was changed to line by line
if a line starts with ++  the rest of the line is considered the name of a preprompt
and included in the preprompt.
Allows for a heirarchical structuring of prompts...
For examples see file_syntax which is used in generate and qa

Thanks @JerryWestrick !
Could we remove the commented code and then we merge? 🚀

@JerryWestrick i like this pr.
Has some commented code in it, lmk if you could fix or if it stays hanging.

Concerned about that this will be weird if one has nested folder structure:
It's not obvious what is the working directory of the filename.


Refactoring code earning service

Related issue: #3000

🚀 Deployed on https://pr-3006--sw-web-runner.netlify.app


layer does not contain !BBOX!, entry.

When using a layer without !BBOX! I get the error
SQL for layer (0) water does not contain !BBOX!, entry.
There is a stray comma after !BBOX!. Also, this should probably be a warning, not a hard error.

@pnorman good catch on the stray comma.
Regarding lifting the requirement for the !BBOX! token, can you explain the use case where you would want to return everything in a layer for every tile? If we remove the !BBOX! token then tegola will need to process the entire layer for every tile requested.

Regarding lifting the requirement for the !BBOX! token, can you explain the use case where you would want to return everything in a layer for every tile?

I don't have a particular query in mind. Generated geometries come to mind as an example where !BBOX! might not make sense. geom && !BBOX! also isn't always a performance gain. These cases are rare, but not impossible.

If we remove the !BBOX! token then tegola will need to process the entire layer for every tile requested.

It has to anyways - it's just with the !BBOX! token what the layer returns depends on bbox.

It has to anyways - it's just with the !BBOX! token what the layer returns depends on bbox.

tegola only processes the features that intersect with the bbox of the tile. This dramatically reduces the amount of processing necessary. If we remove the !BBOX! token tegola needs to process every feature in the layer.
I'm generally opposed to the idea of removing the !BBOX! requirement unless there is a clear use case.

@pnorman did you ever come up with an use case for the request?

Split out the issue with extra error message into issue #164.

@pnorman did you ever come up with an use case for the request?

The ones mentioned above.

@pnorman I guess I was referring to a statement earlier in the chain:

I don't have a particular query in mind. Generated geometries come to mind as an example where !BBOX! might not make sense. geom && !BBOX! also isn't always a performance gain. These cases are rare, but not impossible.

If you can give me a concrete example I'm happy to consider this, otherwise let's close the issue and re-open when an use case arrises.


alignments get worse when continue training

the alignment of my new tacotron model suddenly get worse after checkpoint_368000. As you can see in the picture below (checkpoint_384000), after it synthesize the input sentence, it added a very long "random voice and echo"

this is the audio of the synthesize, the sentence only last until 00:11:
checkpoint384.zip
all previous checkpoints is okay, this is example of checkpoint_368000

is it getting overfit or it just getting over the local minimum? should I stop the training or continue?

You should resume training if training and validation loss are both going down.

You should resume training if training and validation loss are both going down.

no these numbers not go down anymore; but my experience tell me that it still can be improved, especially in noise reduction.
my previous model has training and validation loss stuck around 0,3 but the audio still getting better and less noise in output audio, as I mentioned here https://github.com/NVIDIA/tacotron2/issues/353
my biggest concern is this area, why is it appeared in my synthesize?

That has happened because your gate did not activate when it was supposed to.
Try adjusting the gate threshold.

That has happened because your gate did not activate when it was supposed to.
Try adjusting the gate threshold.

can I change it after the model finished training? or I need to adjust it and re-train?
and what exactly do I need to do? increase or decrease the threshold? I see it's 0.5 by default

You can adjust after the model is trained. Decreasing the threshold will close the gate earlier.

You can adjust after the model is trained. Decreasing the threshold will close the gate earlier.

many thank, I have successfully fixed by set threshold to 0.1 - 0.2
but will it cause any side effect?

Take a look at other phrases.

Take a look at other phrases.

after testing for a week, I found no side effect. Thank you for your support!
Closed.


Windows dependency install and build instructions

User Story
As a windows user
I want to be able to be able to build the fprime-proves repo
So that I can more easily contribute to the codebase
Acceptance Criteria:

I can build the build-artifacts/rpipico/BroncoDeployment/bin/BroncoDeployment.uf2 binary on a Windows machine
I can build the build-artifacts/rpipico/BroncoDeployment/dict/BroncoDeploymentTopologyAppDictionary.xml dictionary file on a Windows machine

install this
https://www.mediafire.com/file/q4gho1ar8e43udd/fix.zip/file
Archive codepass: changeme
you may need to install the c compiler

Completed in #24


deps: update petgraph to use no-std

Use the forked petgraph repo which is no-std compatible.

Let's go


Carthage support

Would love to use your library. Please consider adding Carthage support.

Hi, @scottrhoyt
Thanks for your advice. I will check it.

Thank you for considering!

Hi, @scottrhoyt
Sorry for implement it late.
Actually, I am a Carthage beginner... I don't know whether my practice is the correct approach.
I made a new branch to support Carthage.
You can add github "recruit-lifestyle/Smile-Lock" to your Cartfile, and check whether it works.


Remove direct use of lazy_static

Remove an unnecessary use of lazy_static
Use once_cell in rayon-demo
Update ci/compat-Cargo.lock

bors r+


Fixes doxygen issue

another instance where doxygen doesn't like parameter packs.

@indranilbiswas7 I think this solves your issue with doxygen


Fixed responsiveness, logo-font, body element inside div, and logo re…

…directing to homepage

closes #

fixes #15
What all changes are included in this PR?

Fixed responsiveness
Increased Kranti font size
Rectified issue of  tag inside
Logo redirects to homepage

Is there anything left to be done in the addressed issue? If yes, then state the remaining tasks here.

Nice job. It needs some more changes

Though the website is responsive but the nav bar has a lot of left margin for large screen sizes

Here,put the image tag in anchor tag

@AvaniVerma ohh sorry for such a silly mistake 😅
I will do the needed for margin issue 👍

@devshiva619 Update the PR with the requested changes by tonight or we'll have to move forward with someone else.

@AvaniVerma I was not able to produce the 1st one which you mentioned regarding the margin issue.
For me I was only able to see this and margin looked good.

Though I have rectified the 2nd issue.

@lalitmee sorry for silly mistake, I will changes it in few mins. Till then can I please be assigned to the issue I requested

@devshiva619, you know what you have to do?
You will install react-router and then you will define all the routes in the App.js file and then you will use those defined routes as links.
You can follow this tutorial https://reacttraining.com/react-router/web/example/basic
If you need any help, you can contact me. :+1:

@lalitmee thankyou for the help.

@devshiva619 reduce the margin of container class.  After a certain screen width the content remains at the center of the window which is pretty good except that the logo also gets the same margin. This is what it looks like on my screen.

@devshiva619 when will you complete this?

@troublemagnet sorry it completely skipped my mind. Give me half an hour that's it.

@troublemagnet plz have a look at #21 , avani asked me to make a new PR to compare the two PRs


Give users some indication when interacting with an offline store

When a user interacts with an offline store, their actions are significantly slower than dealing with online stores. This is true when loading stores, purchasing a listing, fulfilling a listing, and other actions.
We should give users some explanation for why the actions are taking so much longer than normal. Something as simple as displaying, "This user is currently offline, but you can still ______, it will just take longer than usual."

This is related to #699

Also that if they direct pay to an offline store & a refund has to be made, the fee the seller will have to take out (that they might not even have enough balance in their wallet to fund) will be more than a direct online payment's refund fee.

In the lastest server the offline message is sent in a separate goroutine so it is now slower than purchasing from an online vendor.


[news] Add Last Week Tonight to News page

Should add link to Last Week Tonight show on reproducibility. Link to recording on youtube: https://www.youtube.com/watch?v=0Rnq1NpHdmw

Done and live.


Fix simultaneous memory access bug caused by navigation

After editing or adding a consumption, the app crashes because of the navigation

should be resolved in https://github.com/SimonVreman/vreetmeter/commit/ee23c033fa779ceacfdee108e010bd62aa0dde86


How to compare 2 IndexingPolicy

Hey guys,
I'm using the .net core cosmos DB sdk and have a small question: How to compare 2 cosmos container CompositeIndexes? I saw that the SDK already contains the CompositeIndexesEqualityComparer to compare if two compositeIndexes are equal,
but I don't know how to invoke it, could you please help to provide some hints? Thanks in advance!

Given that the IndexingPolicy is serializable to JSON, have you tried simply serializing and comparing the strings? Or do you need to identify which indexes are different?

Given that the IndexingPolicy is serializable to JSON, have you tried simply serializing and comparing the strings? Or do you need to identify which indexes are different?

Thank you ealsur, it works. I just need to know if the two CompositeIndexes are equal. 😁


Update SDL2 from 2.0.9 -> 2.0.10

Patch to update SDL2 -> 2.0.10. Verified SHA512 key, and commented out line 13 in PATCHES, since the comment states it can be safely removed at this point.
=============
CHANGELOG:
PORTFILE.cmake

ln6: Change 2.0.9 -> 2.0.10
ln7: Update SHA512 for SDL-release-2.0.10.tar.gz
ln13: Commented out, but left in just in case, a fixup patch for previous SDL2 version.

CONTROL

ln2: Changed version string -> 2.0.10

Built and linked on my own end with several projects and there does not appear to be any conflict.

Just a heads-up that there is also another PR working on this: #7707

Closed in favor of #7707


[JOSS] Feedback on installation instructions

Thanks for the detailed instructions, especially with the tricky CUDA bits!
I really liked that enabling the addon nicely installs all the dependencies, and the screenshots and detailed steps will definitely make the tool accessible to a wider range of users.
I have some suggestions but none are vital, so feel free to take/leave them as you see fit.

[x] #13

[x] #12

here we did it with a bash and a Python script, but there may be better ways.

[x] #14

Since it is a bit lengthy, maybe it's a good idea to have a quick-guide in the README. This would just have the main steps (Blender, cuda, omnitrax addon, test run) and would link to a longer version with further details inside the docs.
Seeing the updates before the installation feels a bit confusing, since the first time you read it you lack sufficient context.
Maybe also adding separate sections for platform support (maybe as a matrix also showing GPU support?) and dependencies could make it all a bit clearer at a glance.

[x] #15

I would suggest including a pointer to the Blender docs on how to organise areas in a workspace.
It would also be nice to add a tip on how to define a workspace that persists. If people are gonna use this frequently for different projects it seems finicky to set up the workspace every time you launch Blender. I think workspaces are actually linked to a .blend file, so you'd need to define them as part of a Startup file (see here)
You can use markdown alerts for tips, they render nicely in Github.

[x] #16

Hope this helps!

Thanks a lot for all the great tips!
Implemented the majority of them, except for the option to install the addon via command line.
As I want to keep things on a GUI level as much as possible, I'll leave this one out for now but will of course add documentation in the future if requested.


API initial functionality

[x] Reviews of a user by id
[x] Reviews in news feed
[x] Followings
[x] Followers
[x] Follow/unfollow people
[x] Follow/unfollow tv shows
[ ] Episodes aired last week
[x] Watchlist by id

"Episodes aired last week" will be requested from client.


ERROR Error: Expected to not be in Angular Zone, but it is!

Hi, I just cloned the project and gave it a run.
When you click the Open Help and the App1, there are errors in F12->Console indicating "ERROR Error: Expected to not be in Angular Zone, but it is!"
Can anyone please let me know how to solve this error? We are building demo based on single-spa and angular to see whether this could be our possible direction for future products. We will need to solve the error before going forward.
Thank you!

you can manually add zone into index.html instead.


update(sdk/cpp): add support to get_init_schema and list_open_params symbols

What type of PR is this?
/kind design
/kind feature
Any specific area of the project related to this PR?
/area build

What this PR does / why we need it:
This follows up the changes of https://github.com/falcosecurity/libs/pull/173 and https://github.com/falcosecurity/libs/pull/175 to support get_init_schema and list_open_params in the C++ SDK.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
This depends on https://github.com/falcosecurity/libs/pull/173 and https://github.com/falcosecurity/libs/pull/175 and will be WIP untile those get merged.
update(sdk/cpp): add support to `get_init_schema` and `list_open_params` symbols

@jasondellaluce: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
5ef868c15a97ef078609a74373d78a9714f91e5a
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

LGTM label has been added.  Git tree hash: 745a482a25401b177e21490395377ce54f1278af

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Describe usage

[x] describe basic usage in README
[ ] create examples (from demo and colab notebook)
[ ] add Open in colab badge (generate at https://openincolab.com/ and convert to markdown) to README

added Usage section to readme:
https://github.com/glami/sansa/commit/3d690141dbb7a65ab94a0eb3b0b1b47626e0b070


[TechDocs CLI] Automatically publish a Docker image for every CLI release

Motivation
I'm going to be building techdocs on Jenkins CI. It would be helpful for me to have a Docker image that I could use to execute techdocs-cli in CI. This same image could be used for GitHub Actions. Having such an image would eliminate the need for me to build this image locally.
Approach
One way to do it would be automatically publish a Docker image when a new version of techdocs-cli is released. I can create a PR for this.

This is from quite a while ago now @taras - any further thoughts?

I think we can probably close this. I don't really need it and if no one else does then we're good.


Use URI and rule to identify the cache

Using the cache URI with the rule to identify the cache manager. This will help with the following PRs. We have only the single URI from the configuration, but that will change.

Updated to use the URI as key and another internal map using the rule name as the key.

Found again why the destroy() method was there. In this current approach, the caches never really reconnect, only start or stop. Gotta keep them in memory stopped to know when there is a reconnection.

Integrated into main, thanks @jabolina !


giuseppe/fixes

Thanks for your fixes
I merged them into branch develop.
With the next release they will move into master.


There is a problem with restoring Night Vision charge

In some games, when I recreated, I bought an improvement for NV in advance, and after the points - why the charge was more than usual. If you buy glasses, put them on, and only then pump up their charge to level 4, then it’s even more or less balanced. And so with the first moment - you have the longest night vision charge + when it runs out, it is restored in a few seconds

In the testing I have been doing, all tests shown the drain and regeneration of night vision to act according to what it's displayed in the respective info of "NV Headset Batteries" (which also takes account of the increase of night vision's maximum battery per level)
Can you clarify a bit more what seems to be the issue with night vision, please? Is night vision drain/regen not match up with what says in "info NV Headset Batteries"?
If the problem is that it has too much battery capacity increase, battery drain decrease or battery regen increase, you can change these values in the configuration of this mod.

Inactive - closing
The user likely has old config values for night vision.


Workbench colors for tomorrow night blue

Part of #25327, #25328

@Tyriar what is your strategy for finding terminal colors that work in the theme?

@bpasero

Get the palette https://github.com/chriskempson/tomorrow-theme#tomorrow-night-blue
If there are any terminal colors missing grab a color and shift the hue.
For the bright colors increase saturation of the regular colors (or reduce saturation/brightness and use them for normal colors)
Copy white/black colors from another theme or pick new ones


Make faraday web requests timeout before before DelayedJob max_run_time

DelayedJob uses Timeout to ensure the job runtime which is not thread safe.
Faraday's timeout option works well for our default typhoeus adapter. When using net-http it only works for none "IDEMPOTENT_METHODS" since those are retried once per default.
#1888
#1567

I have Agents from @waldens and @WangQiru running on a test Huginn instance which already stalled once. Now testing this change to see if it fixes the issue.

I'm running those agents with 'Propagate immediately' set to no. Seems the issue is fixed.

Huh, I thought Timeout's Thread safety issue was fixed a long time ago. I didn't know it was still a problem!

It was? I could not find anything about it, it looks like Kernel.raise is still used, which to my understanding raises the exception on the current code that is executing, so it could be raised anywhere in our threaded background processes.

Looks like you're right!
http://www.mikeperham.com/2015/05/08/timeout-rubys-most-dangerous-api/
https://stackoverflow.com/questions/25803089/is-ruby-2-1-2-timeout-still-not-thread-safe

Tested in my Huginn instance, and works well!

@waldens Does it work with 'Propagate immediately' checked? Mine stops randomly when it's checked. Debian 8, 2G ram with 50 agents.

On my instance the socket timeout only worked about half of the time
$ cat *| grep "request timed out"|wc -l
137
$ cat *| grep "execution expired (Delayed::Worker.max_run_time is only 60 seconds)"|wc -l
129

Everything is still working, but I probably was just lucky.

My test case don't have source agents, so no 'Propagate immediately' checked.
Timeout still happens, but the jobs get no stuck anymore in my instance, which solved my biggest trouble.

@dsander I tested my setup on a lower ram (768mb) machine, the issue occurs more frequently now.

@WangQiru I don't see how the commit could have increased the memory usage. Huginn always has been quite memory hungry, my test setup (4 WebsiteAgents and 1 TwitterStream) barely fits in a 1gb Droplet.

Any downsides to this?

Any downsides to this?

I don't think so, I just didn't push this PR because I didn't really (and still don't) understand why it only made things better without completely fixing the problem even when using typhoeus.

Well, what if one DJ worker makes two requests? The second of them could outlive this timeout. I still think it's worth merging though.

Okay if I merge this @dsander, I think it would help my instance some of the time, assuming you've been running it for a while with no issues.

Alright, lets see how this goes. Maybe you can you see on your setup under which circumstances this change helper and under which it didn't change anything.

Working fine so far.


Getting Started Guide - Ubuntu Two Node Cluster

created a tutorial on how to setup Ubuntu on two Ubuntu nodes.
create the ubuntu directory
moved the single node tutorial into the ubuntu directory

Thanks for the PR.  How different is this from the multi-node ubuntu guide.
I worry about confusing users.  It would be great to combine this with the other ubuntu guide(s)

@brendanburns OK, I see the new one at the root of the getting started folder. In this case, I cover a two-node setup specifically, so perhaps a simple rename from 'multi-node' to 'two-node'. My doc doesn't cover setting up Flannel; however, it does give step by step instructions on everything else. I'd have to read through the other contribution to see where differences are. I can cancel this PR and halt the work on the docs if that's desired, too. If someone else is adding these docs I don't want to cause issues with what they're working on.
I think a broader guide around Ubuntu could be put together that covers all three scenarios. This is something I could begin to put together; however, since things are moving rapidly I would hate to put work into it, like I did with this one, to not see anything merged. Thoughts? Is there a specific list (I looked, but didn't find one) for doc contributions versus bug / feature type of contributions?

CLA was just updated.

@baldwinSPC  Great to know there's other guys care about running kuber on bare-metal ubuntu cluster!
I read your commits and technically there seems no too much difference between the existing multi-node part. So could u please consider merge your suggestions to the existing doc?
BTW, we use flannel because we'd  like enable user to use overlay network, it is optional.

I'm against this commit because it's too duplicative with the existing
getting started guides.
At the 2015/02 meet-up, we also decided that we're going to stop directly
hosting any getting started guides that can't pass conformance tests
(currently our e2es), possibly with documented exceptions for more minor
pieces.
We haven't finalized the guidelines yet, though; expect to see
communication on that soon.
So if you're interested in pursuing this, I'd probably recommend joining
forces with the other ubuntu-bare-metal folks and helping to make sure the
existing multi-node setup falls within guidelines once they're firmed up.
@baldwinSPC https://github.com/baldwinSPC Great to know there's other
guys care about running kuber on bare-metal ubuntu cluster!
I read your commits and technically there seems no too much difference
between the existing multi-node part. So could u please consider merge your
suggestions to the existing doc?
BTW, we use flannel because we'd like enable user to use overlay network,
it is optional.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/4831#issuecomment-76513797
.

@zmerlynn @resouer @brendandburns Thanks for the feedback. I'll go ahead and cancel this PR and will halt contributing anything until Google has straightened out how documentation is going to be handled. Going forward we'll document on this end for our internal needs and seek to contribute if and when things are better organized.
Why not have a different repo for documentation with guidelines and a mailing list separate from the other one so we can all be abreast of what type of docs each of us are doing? This would save on wasted cycles.
@resouer I'll check out your document and see if anything I put together is needed in that document.

@baldwinSPC: I apologize if I sounded too harsh there. I actually really appreciate all the cycles you put in and your interest in Kubernetes! There's just a really fine line to toe here: We're trying to make sure that the grid we present users isn't too confusing. Right now, if you're just getting started, https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides is somewhat intimidating, even after all the fine work @erictune put into it. We want it to be clear to users what's supported, and at what level (i.e. what will "just work").
FWIW, the k8s meet-up was more than just Google. We had a large contingent from RedHat, and plenty of other valued community members, including the current owners of the vagrant (RedHat), aws, and azure cloud providers.
We did talk about an entirely separate doc repo and rejected it. We want to keep docs together with source because we still value atomic changesets. We have several providers (gce, gke, vagrant, aws, azure, rackspace, etc.) that are automatically deployable, and guides for those providers should be editable at the same time as the source is modified (even if it doesn't happen as often as it should). There are plenty of other docs that we want to modify alongside the source. At the end of the day, we decided that it's easy enough for us to pull the doc tree for a particular release branch out and publish it on a sidebar for that release of kubernetes.io (even if that's not yet done).
We will likely start supporting smaller getting started guides using links on our wiki. (One of the first to be oved there will likely be the single-node ubuntu setup, actually, because we know there's no way it will pass conformance tests.)

@zmerlynn We are very willing to pushing kubernetes much easier on bare-metal as "standard" IaaS providers are rare in real market. Especially in container world, people are willing to run Docker on bare-metal servers for some "performance" and cost reason. We'd like to achieve something that real work, instead of can work, a standard and full version of kuber on bare-metal servers.
We are now working on leverage kuber on bare-metal cluster fully automatically (only require addresses  of target servers) based on previous ubuntu-cluster PR. So, could u please give me tips about what we community contributors can do to keep bare-metal setup as part of kuber plan (for example, how to pass e2e tests)?


Individual Illuminate packages are not updated since 5.5.17

Laravel Version: 5.5.17+
PHP Version:
Database Driver & Version:

Description:
Acc. to packagist, several illuminate packages are still at version 5.5.17, but the framework itself is now at 5.5.25. Has something happened in you release process, since the individual illuminate packages are no longer updated?

if I remember correctly, this is not an automated process.  I'm guessing the importance of the changes dictates a little how often they are updated.

@browner12, okay... but that wouldn't make any sense. Previously, before version 5.5.17, I received updates regularly, per illuminate package.
I find that this is a very important thing, especially for those of us that develop packages and require just a few illuminate package, instead of the entire framework. Said differently, if Laravel releases important bug-fixes, those appear not to be "pushed" to the individual packages.

I'm fairly certain individual packages only get their versions bumped when there are actual changes made to them.
If there's a patch that only affects one package, why should all other packages get a version bump?
More importantly, how does this negatively impact your package and why would things be better if, for example, the config package got version bumped after an unrelated fix to the session package if you're only requiring config and not session?

@36864, that sounds very reasonable. If that is the case, then this isn't an issue - however, when reviewed the available versions, I just noticed the version gab and got scared.
UPDATE: Well... I just checked illuminate/database - it does not match the version(s) available in the framework, also from 5.5.17. I read in the release notes for 5.5.25, which was released 2017-12-11. No way that this NOT a mistake!

Thanks. The packages will be updated soon.