sys.exit(num_alerts) in cli.py

This doesn't match my understanding of Unix error code conventions. Usually an error code means something went wrong, not the tool functioned as usual. If anything, I've seen tools throw an error code when they didn't find anything (grep, pgrep, pkill).
Any other opinions?

It depends on what you mean by "wrong." :) In your examples of grep and so forth, they still function as usual even if they don't find anything, they just consider "wrong" to be "not found." In the case of vulnerability scanning, we consider "wrong" to be that there's a vulnerability in the target application. This is important particularly when a tool like zap-cli is used as part of CI, since in general, a job fails if a part of a CI job returns a non-zero exit code, and you only want the job to fail if a vulnerability was found. If a vulnerability is not found, then it's OK and the build should succeed. This also matches the behaviour of ZAP's baseline scripts for scanning as well, i.e. https://github.com/zaproxy/zaproxy/blob/d98726bcab791a/build/docker/zap-baseline.py#L31-L35 and other similar previous tools, i.e. https://github.com/garethr/zapr/blob/8adf8a2457c4/lib/zapr/zap.rb#L52-L58

Makes sense!

Having this behavior explicitly documented somewhere would be great.

Opening this because I read something in a book today that worried me. The following one liners should demonstrate the problem with sys.exit(num_alerts).
┌─[hayden@devvm]─[~/code/zap-cli/zapcli]
└──╼ $sh -c "exit 255" && echo No error\! || echo $?
255
┌─[hayden@devvm]─[~/code/zap-cli/zapcli]
└──╼ $sh -c "exit 256" && echo No error\! || echo $?
No error!
┌─[hayden@devvm]─[~/code/zap-cli/zapcli]
└──╼ $sh -c "exit 257" && echo No error\! || echo $?
1
┌─[hayden@devvm]─[~/code/zap-cli/zapcli]
└──╼ $sh -c "exit 512" && echo No error\! || echo $?
No error!
┌─[hayden@devvm]─[~/code/zap-cli/zapcli]
└──╼ $

@Grunny

That's a good point in the event you have that many alerts. We can just change it to more like the ZAP baseline script: https://github.com/zaproxy/zaproxy/blob/d98726bcab791a/build/docker/zap-baseline.py#L31-L35 rather than like zapr like it is now. So, we'll just exit with 1 if any number of alerts are found.


Blocker: add 'return' annotation to Tuple.rename()

This is blocking https://github.com/dlang/dmd/pull/5972

Auto-merge toggled on


Button's theme={} not applying

Describe the bug
Passing a theme={} to a Button does nothing.
To Reproduce
Steps to reproduce the behavior:

Import Button from package
Pass it a custom theme through theme={}
See no changes

Expected behavior
The custom theme should be applied to the Button.
Project information:

Flowbite React: 0.4.2

Additional context
Posting this here to not lose track of it - this was discussed in the Discord last week but I didn't have time to implement it. Will probably get a PR up this week, but if anyone else wants to take this, be my guest.
On Discord, from @rluders :
const theme = mergeDeep(useTheme().theme.button, customTheme);
const groupTheme = mergeDeep(useTheme().theme.buttonGroup, customTheme.inner ?? {});

Splitting the existing useTheme() here to something like the above should do the trick. Needs testing.

Seems to be an issue to all compoents when they are applied with an individual theme

Seems to be an issue to all compoents when they are applied with an individual theme

Most likely not - Only confirmed with Button so far, although some other components are finicky with their children components (you can send root themes to the parent, but it doesn't correctly pass themes to children, etc.).
Am using custom individual themes just fine on my app with the Card, Dropdown, Footer, Modal and Navbar components.

I'm wondering if someone is interested in creating a PR for this one. I'll be happy to review it this week, or ASAP. Also, I'm curious if this issue is happening in any other components.

Inline themes for <Accordion /> not working as well. Especially those that handle borders. I tried to set the inline theme for both <Accordion /> and <Accordion.Panel /> to no avail. Here:
export const PriceHistory = () => {
    return <Accordion className="mt-3" alwaysOpen theme={{'root': {
        'base': "divide-y !border-3 !divide-gray-300 border-gray-300 dark:divide-gray-700 dark:border-gray-700",
        'flush': {
            'off': "rounded-lg border-4",
            'on': "border-b border-t border-l border-r"
        }
    }}}>
        <Accordion.Panel theme={{'root': {
            'base': "divide-y !border-3 !divide-gray-300 border-gray-300 dark:divide-gray-700 dark:border-gray-700",
            'flush': {
                'off': "rounded-lg border-4",
                'on': "border-b border-t border-l border-r"
            }
        }}}>
            <Accordion.Title className="!flex !flex-row !items-center" theme={{
                "flush": {
                    "off": "hover:bg-[#FDFDFD] bg-[#FDFDFD] dark:hover:bg-gray-800",
                    "on": "bg-transparent dark:bg-transparent"
                },
                "open": {
                    "off": "",
                    "on": "text-black bg-[#FDFDFD] dark:bg-gray-800 dark:text-white"
                },
                "base": "flex w-full items-center justify-between first:rounded-t-lg last:rounded-b-lg py-5 px-5 text-left font-medium text-black dark:text-gray-400",
            }}>
                <span className="flex items-center">
                    <SlGraph className="mr-1.5" /> Price History
                </span>
            </Accordion.Title>
            <Accordion.Content>
                Graph showing price changes :)
            </Accordion.Content>
        </Accordion.Panel>
    </Accordion>
}

When the component rendered, the component was still stuck with the default border.


add console runner

Added the ability to run .opn() from the command line (no options supported)

it can be used by package.json scripts

  .  .  .
  "scripts": {
    .  .  .
    "test:coverage": "... && nyc report --reporter=html && opn coverage/index.html"
  },
  .  .  .

Personally for me it is very useful. It opens coverage report with default browser on Linux/Windows/OSX.

It already exists https://github.com/sindresorhus/opn-cli

oh! sorry, I did not found it. Thank you


Partial Response : "Use Partial Response" enabled by default

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

I have made relevant changes in the codebase such that #6270 issue is resolved and Use Partial Response checkbox is enabled by default.

Thanks! Generally looks good, but I wonder if you came across the issue mentioned in comment: #6270 (comment)

I tried to configure it  and closely inspected all the behaviour of partial response , stored it in local storage too giving it a key the value in local storage changes when i toggle on it but when i refresh the page it takes the value stored in local storage .......

so i also tried changing the useLocalStorage hook such that if any key stored in local storage has false value it changes it to true but it only works with Use local time , Enable query history and all other elements except with Use Partial Response .                                If you have any approach please suggest .

Thanks! Generally looks good, but I wonder if you came across the issue mentioned in comment: #6270 (comment)

Hello @saswatamcode worked on the comment you suggested tested it on my local machine you can  review it again !

@Vanshikav123 Please sign off DCO

@Vanshikav123 Please sign off DCO

Done !


[TW#17081] Timer Task Freezed sometimes.

esp_timer.c
I am using ESP32 software timer to scan adc button and LED blinking feature.
Keep running the task several hours, the timer task freezed and without watchdog triggered.

@welinkio Can you please update to latest 3.0 or master. We have fix some bugs on timer.


Settings pane is blank unless reload the window

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.2
OS Version: Windows 10.0.22621.2361

Steps to Reproduce:

Any output in the devtools console during the first load?
To get to the devtools console, press Ctrl+Shift+P to open the command palette, and then run the "Developer: Toggle Developer" Tools command.

I've found that this problem occurs when I'm not connected to the internet, and it shows up fine when connected.

I'm unable to reproduce the issue. Does it occur with extensions disabled?

yes

Got it. What must've happened last time was my device reconnected me to the Internet while I was confirming the issue.


Register 0.3.5

@JuliaRegistrator register
Added dual_ranking.

Registration pull request created: JuliaRegistries/General/115136
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.5 -m "<description of version>" 7aea87eb0789c0c8044b709447585a26695ec892
git push origin v0.3.5


Implementation of FHIR Profiles

Is your feature request related to a problem? Please describe.

Accessing IPS URL and creating a place to store the data
Creating a package or module as required or even within the Reference App.
Rendering the list of patients, and ability to store detailed summary
→ Summary will include all medical history of patient
→ Including organisations, medical professionals treating and taking care at that time.

Describe the solution you'd like

Implementation of International patient page according to
http://hl7.org/fhir/uv/ips/
Render the patient list accordingly using
http://hl7.org/fhir/R4/patient.html and http://hl7.org/fhir/uv/ips/ipsStructure.html

Describe alternatives you've considered
N/A
Additional context
Related to issue #590 and #593
As per Discussion with @maimoonak.
Would you like to work on the issue?
Yes.

The following feature can be referred to #593

@Ana2k , could you please provide an update on the status of this issue? Are the code changes ready for review? If now, is there an ETA that you could please provide?

@Ana2k , could you please provide an update on the status of this issue? Are the code changes ready for review? If now, is there an ETA that you could please provide?

I am currently working on this. I will have implemented most changes by  9thAugust(Possible ETA).


inject --include-binaries on a package without binaries will remove already-existing binaries

Using inject --include-binaries original new on a new package that doesn't have binaries will remove the existing binaries from PATH.
# Create a virtualenv with ipython binary
pipx install ipython
# Add black binary to the virtualenv
pipx inject --include-binaries ipython black
which black
# Add toolz to the virtualenv, even though it doesn't have a binary
pipx inject --include-binaries ipython toolz
# Black is now missing
which black

I do this --inject-binaries even for packages that don't have binaries because I like to have a main virtualenv with most of my things in it. I want to run a single command to get everything I need. Since pipx doesn't yet support a single command to get multiple things, I'm splitting it into two.
pipx install ipython
pipx inject  --include-binaries ipython toolz pytest attrs

Thank you for reporting and following up. The reproduction was straightforward thanks to your code block. This has been fixed in <IP_ADDRESS>.


OpenCV import fails using l4t-ml:r35.1.0-py3 container

Greetings!
I am building the container at hand and when I try simply import cv2, the following trace pops up:
...
  File "/usr/local/lib/python3.8/dist-packages/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/__init__.py", line 181, in <module>
    bootstrap()
  File "/usr/local/lib/python3.8/dist-packages/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/__init__.py", line 175, in bootstrap
    if __load_extra_py_code_for_module("cv2", submodule, DEBUG):
  File "/usr/local/lib/python3.8/dist-packages/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/__init__.py", line 28, in __load_extra_py_code_for_module
    py_module = importlib.import_module(module_name)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/local/lib/python3.8/dist-packages/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/cv2/gapi/__init__.py", line 301, in <module>
    cv.gapi.wip.GStreamerPipeline = cv.gapi_wip_gst_GStreamerPipeline
AttributeError: partially initialized module 'cv2' has no attribute 'gapi_wip_gst_GStreamerPipeline' (most likely due to a circular import)

It seems like being a recursive import, circular structure but I don't exactly understand where could that be. Help would be highly appreciated :)

I was making the mistake of installing opencv-python in my requirements file.


[Android] Enable Location

Is there a way to enable geolocation, in a way similar to that of Google Maps in Android 7?
I ask this because when checking for location, if the user allowed it, and disabled it later, the user is not prompt the permission.

Hi @andreacappadona17
Could you check the isEnabled method combined with the enableLocationRequest one once again and update us back? We fully replaced the old Android implementation with the Google Play Services one (used by Google Maps).
You could check the v4.0.0 release notes here.

Hi @DimitarTachev
the new version rocks!
Thank you


Update notif-send-test.md

Since the v2.2 release of the Encryption module (July '21), the encryption key length changed to 32 characters

Probably don't have to mention the previous key length since it was changed so long ago and this is Mx 10 documentation.

@ThijsSeppen our build tool Travis was taking a long time checking for conflicts, so I implemented this change manually here: https://github.com/mendix/docs/commit/0006c5a556af8822bd876a79d74f3b6b3cab2b88
Thanks so much for the PR @ThijsSeppen . Just a note -- this "16 character" language was present in 3 versions.


feat(VIST-CPC-946) add option to choose owner and pet for visit

JIRA: link to jira ticket
Context:
This ticket serves the purpose of allowing the user to choose an owner and than a pet of the owner chosen to be added to the new visit.
The reason why we added it was because the previous post URL contained no pet or owner id so when a visit was added the pet Id column was empty for a new visit. This ticket fixed that and now display the pet Id related to the visit
Changes

The first change was adding 2 new drop downs to the form which contain the owners and the pets of that owners
The drop downs are filled dynamically based on a function that sends a get request to retrieve all the owners and the pets
Once a successful visit is made, the form automatically routes the user back to the visit list page to view all the visits with the newly created visit page

Before and After UI (Required for UI-impacting PRs)
(Before Change)

(After Change) 2 New Drop Downs and Removed the Upcoming Visits Table

(After Change) List of Owners

(After Change) List of the Selected Owner's pets

Overall, this was a great implementation of a must needed part of our service. Good job!


Installation via package managers (homebrew, ...)

We could support releasing the CLI via package managers, such as homebrew on macOS and others for Windows (chocolatey, ...), and Linux.
For some package managers, it can be possible that the shell completion can be done at installation,
For example, for homebrew, see their shell completion documentation:
https://docs.brew.sh/Shell-Completion
see related completion issue #14

There is also snap for ubuntu http://doc.ubuntu-fr.org/snap

there are also macports on Mac, scoop on windows, apt for Debian & ubuntu, (pacman for arch linux), (dnf for fedora), (pkg_add for centos)

On Linux, deb/rpm are common but these days, a more portable approach is either snap, or better, flatpack.

Related https://github.com/reliablyhq/cli/issues/192


WebGL vector tile renderer

This PR is a first attempt at getting a webgl-based vector tile renderer running. The approach is as follows:

Rely on MixedGeometryBatch and BatchRenderer used in the webgl vector renderer; here, each tile will have its own geometry batch renderer separately
Move as much logic as possible from TileTexture and WebGLTileLayerRenderer into base classes, so as to reuse logic for vector tiles; these base classes were called BaseTileRepresentation and WebGLBaseTileLayerRenderer
Create a new WebGLVectorTileLayerRenderer which tries to do as few as possible, relying on the geometry batch utilities and base classes to draw tiles on screen

See here: https://deploy-preview-14445--ol-site.netlify.app/en/latest/examples/webgl-vector-tiles.html

Known limitations:

no alpha transition
no text rendering

Remaining:

[x] add rendering tests
[x] add dedicated example

Discussion: https://github.com/openlayers/openlayers/discussions/14446
This work is sponsored by BSW-Hamburg and Landesbetrieb Geoinformation und Vermessung Hamburg.

This is ready for review!

I haven't looked at the code yet, but a first glance at the example in Safari 16.3 and 16.4 suggests that there are still a few problems:
https://user-images.githubusercontent.com/211514/220097901-4fdfd0d8-1c1d-4936-8865-d9afc5013ec8.mov

I haven't looked at the code yet, but a first glance at the example in Safari 16.3 and 16.4 suggests that there are still a few problems:

Thanks for the feedback, there was indeed an issue with pixel ratios > 1, also fixed an issue related to tile gutters not being correctly cropped.

edit: I still have issues on mobile... investigating there's a precision issue when specifying a render extent for a tile on older devices; i'll push a separate fix on the branch

This is fixed in the latests commits, I added automatic precision detection as per MDN indications.
Note that on devices which do not support highp precision for floats, tile gutters will not be cropped. This should concern very few devices and still allow showing something, even though it might have glitches; having a proper fallback for these devices isn't trivial so I'm leaving this aside for now.

Thanks for your work on this, @jahow.  It is encouraging to see this coming together.  As part of updating the canvas tile renderer (in #14262), I discovered a duplicate tile rendering issue in the webgl tile renderer.  I finally got around to correcting that in #14550.  I think it makes sense to get that fix in first so this work doesn't inherit the same problem.
After #14550 is in, it would be good if we could break this down into more easily reviewable changes.  Would you be willing to put up a branch that separates out the webgl tile renderer and tile texture logic into shared base classes (without TileGeometry and VectorTileLayer classes)?

After https://github.com/openlayers/openlayers/pull/14550 is in, it would be good if we could break this down into more easily reviewable changes. Would you be willing to put up a branch that separates out the webgl tile renderer and tile texture logic into shared base classes (without TileGeometry and VectorTileLayer classes)?

That sounds good! I'll keep that PR opened and open a new one specifically for the tile renderer/tile representation indirection

See here: https://deploy-preview-14445--ol-site.netlify.app/en/latest/examples/webgl-vector-tiles.html

The CodeSandbox configuration currently used by the examples does not support the ?. operator.  It can be seen working in some other CodeSandbox examples found via Google search, so with some configuration changes it should be able to support this valid example.

Would you be willing to put up a branch that separates out the webgl tile renderer and tile texture logic into shared base classes (without TileGeometry and VectorTileLayer classes)?

Done in https://github.com/openlayers/openlayers/pull/14594

This has been rebased on main.

This looks great, @jahow.  Thanks for your continued work on it.
In working on the particle flow renderer (#14491), I noticed some issues with alpha blending and had to adjust some things to avoid flickering and some opacity issues.  I notice some flashing during rendering in this branch and wonder if it could be related.  After this is in, I look forward to working together to making the webgl rendering work well for the various use cases we are targeting.
I'll break #14491 into smaller parts and we can see how they might affect the vector tile rendering after you merge this.

Thanks @tschaub for the multiple reviews!


Docs update

Hello!
I've added the required arch packages, a reference to PhASAR and an installation script to the documentation.

Thanks


Fixed Navbar Problem

Describe the bug
When Fixed the navbar at top. We Have to give padding to the first container.
To Reproduce
Steps to reproduce the behavior:

Give padding to the containers

Actual behavior

I would like to take this up @Vishal-raj-1

I would like to take this up @Vishal-raj-1

Sure !!

I would like to take this up @Vishal-raj-1

Sure !!

Are you cool with @m-code12 taking it?

Yes
On Sat, Dec 19, 2020, 10:59 PM Smaranjit Ghose<EMAIL_ADDRESS>wrote:

I would like to take this up @Vishal-raj-1
https://github.com/Vishal-raj-1
Sure !!
Are you cool with @m-code12 https://github.com/m-code12 taking it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/smaranjitghose/awesome-portfolio-websites/issues/325#issuecomment-748501737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIZYADSOMMJ3MQJTRADT5TSVTPG5ANCNFSM4U52GGSQ
.


Pretrained Weights

Did you check the model's performance on Pascal VOC? If yes, can you please provide the pretrained weights for the same, for those who don't want to retrain the model.
Also, do you have pretrained weights for the same model on MS COCO dataset? That would also be helpful.

Can you please provide pretrained weights for Pascal VOC dataset and MS COCO dataset


MGDOBR-207: fix refresh token expiration and add safe buffer to refresh the token

MGDOBR-207
This PR aims to add 30s buffer to the token expiration check. In addition to that, in case the refresh token has expired, a new fresh token is retrieved.
Please make sure that your PR meets the following requirements:

[x] Your code is properly formatted according to this configuration
[x] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[x] All new functionality is tested
[x] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

This fix is included in https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/198 . Closing this one


Add files via upload

Create a path to the file - Algorithmic Daily Returns #Read the df_Manufacturing_other and clean the data. # drop the 1st raw
Calculate Daily Returns

Create a path to the file - Algorithmic Daily Returns #Read the df_Manufacturing_other and clean the data. # drop the 1st raw
Calculate Daily Returns


allow 300 barcodes

We should still try to get the pulse3d fix in

that'll have to be done separately, just posted the PR for that. I'll add 0.33.10 into K8s

The amplitude in live view will be incorrect until we bring pulse3d 0.33.11 into the MA Controller

The amplitude in live view will be incorrect until we bring pulse3d 0.33.11 into the MA Controller

Oh duh, yeah forgot it's a dependency in this repo


Update Twitter Logo to 'X' in Footer Section

The current footer section of the e-commerce website displays the old Twitter bird logo, which is outdated. To align with Twitter's rebranding, update the logo to the new 'X' design. This change will ensure that the website reflects the latest branding of Twitter, maintaining consistency and modernity. Updating the logo will enhance the website's visual appeal and ensure compliance with current social media branding standards.

Hi @Priyaaa1 please assign me this issue.

@skshrinaya it was done yesterday


DRF API seems very slow

Rendering on the server side is very fast
Rendering on the client side by requesting API data is much slower
Is this a DRF issue?

https://ses4j.github.io/2015/11/23/optimizing-slow-django-rest-framework-performance/

Looks to be the related serializer fields which are causing many database reads

https://www.dabapps.com/blog/api-performance-profiling-django-rest-framework/

This has been addressed (or is being addressed). Queries need to be considered carefully, and use prefetch_related where appropriate.


Update workflows

Rearrange steps of workflows
Introduce dependency review

Signed-off-by: Gao Hongtao<EMAIL_ADDRESS>

Codecov Report

Merging #208 (2edad4c) into main (99606f5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 2edad4c differs from pull request most recent head 3932a58. Consider uploading reports for the commit 3932a58 to get more accurate results

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   44.84%   44.84%
=======================================
  Files          84       84
  Lines        8500     8500
=======================================
  Hits         3812     3812
  Misses       4354     4354
  Partials      334      334

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feat/ci

Add CI jobs for cargo check, test, clippy and fmt.
I didn't set clippy strict mode (-Dwarnings) on purpose to not fail the job, but let me know if you prefer the stricter version.

Regarding cargo fmt, if --check is not set it doesn't display anything in the logs, so it's not really useful.
--check on the other hand have the job fails as expected, as you can see in my fork's Actions.


Port combined_publisher_schemas to Rake

This PR ports the combination of Publisher V1 schemas to a Rake task from Make. For every make task, it shells out to bundle exec bin/some_script, which involves a lot of overhead in invoking the Ruby/Gems/Bundler environment for each file. This will get very unwieldy as the number of schema grows.
For benchmarking purposes, processing dist/formats/*/publisher/schema.json takes ~8.5 seconds using Make, and around half a second using Rake. Most of that is the initial boot of the Ruby environment, I imagine even once we've got all the formats ported across an entire Rake run with all tasks will take around a couple of seconds.
If people prefer this approach, I can work on porting the other tasks.
For reference, total runtime of the Make suite at the moment from clean is 1.5 minutes

:heart: for intent.

This is ready for review and merge. The second commit here is a possible refactoring. I am struggling to work out which form is more readable - opinions very welcome.
This PR now uses the Rake task in place of the main Make schema combination task, so make now takes 25 seconds less than before.
Part 1 of a few PRs to gradually port this Make suite.

This is really cool.
Do you think we could also take another approach? As far as I understand the build process, we loop through all formats, combine them if necessary and copy them to /dist. Could we avoid the rule matching by using Dir.glob() or something like that?
In pseudo-ruby:
all_formats = Dir.glob("formats/*")

all_formats.each do |format_name|
  schema = generate_dist_schema(format_name)
  file.write(schema)
end

def generate_dist_schema(format_name)
  if File.exist?(format_name + "/schema.json")
    File.read(format_name + "/schema.json") # hand-made
  else
    SchemaCombiner.new({
      definitions: File.read("definitions.json"),
      metadata: File.read("metadata.json"),
      details: File.read("#{format_name}/details.json")
    }, format_name).combined
  end
end

I don't believe Dir.glob is compatible with Rake FileLists. We want to use Rake to get the same dependency resolution / partial build functionality as Make.

use dependency resolution / partial build functionality

I'm fairly ignorant when it comes to build systems. What is the reason we want to have this for this project?

So that if one of the dependency files changes, the related schema get rebuilt. If only e.g. formats/case_study/publisher/details.json changes, then we only need to rebuild dist/formats/case_study/publisher/schema.json.

Ok, so that's what rule does somehow?
I think that there's a trade-off between build speed and maintainability of the tools. I find the flow of the rake DSL really hard to follow.
I suspect that the tasks performed here aren't that complex that we couldn't rebuild the entire thing in a few seconds, so maybe we can use pure Ruby?

While I think that this declarative style is fairly unusual within ruby frameworks, Rake is the appropriate tool for this task and this is using Rake in the correct way, too.
So :+1: from me to merge this, especially after @boffbowsh's change to make the method names less magic.

Marking as DNM until I've added some sort of tests.

Removed old bin script and ported its spec to cover the new Rake task. Also added spec coverage for the v2 schema


Alexa "All Lights 50%" command when already on

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.32.4
Python release (python3 --version):
Python 3.4.2
Component/platform:
RPi3 with All in One Installer
Description of problem:
The command, "Alexa, all lights 50%," when any light is already on fails.
Expected:
The light level should be adjusted.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
aiohttp.web: Error handling request
Traceback (most recent call last):
File "/srv/hass/hass_venv/lib/python3.4/site-packages/aiohttp/server.py", line 261, in start
yield from self.handle_request(message, payload)
File "/srv/hass/hass_venv/lib/python3.4/site-packages/aiohttp/web.py", line 88, in handle_request
resp = yield from handler(request)
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/http.py", line 504, in handle
result = yield from result
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/emulated_hue.py", line 260, in put
result = yield from self.async_put_light_state(json_data, entity_id)
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/emulated_hue.py", line 308, in async_put_light_state
parsed = parse_hue_api_put_light_body(request_json, entity)
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/emulated_hue.py", line 406, in parse_hue_api_put_light_body
return (result, brightness) if report_brightness else (result, None)
UnboundLocalError: local variable 'report_brightness' referenced before assignment

Same as #4368

Just updated to 0.40.1.  Now "all lights 50%" does not work at all.  "All lights off" works and when I try "take all lights to half" it turns them on all the way.


Redraw issues in the terminal

Version: 1.51.0-insider
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-04T18:30:27.659Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15

Create a codespace using the web UI
In the terminal of the codespace run git config --list

->

The amount of whitespace on the top reflects the number of lines that were displayed in the terminal before.
Note: Redraw fixes the problem:

Potentially related: https://github.com/microsoft/vscode/issues/110232

It does look similar to #110232.
I can't repro though:

When piping into | less I see this which is expected:

Pressing up or resizing will show that it's the end of the file:

@kieferrm do you have a value set for core.pager in your .gitconfig?


Apply Cli version configuration override during storage container creation

What does this PR do? Please provide some context
Apply configuration override for Azure Cli version for storage account creation
Where should the reviewer start?
The changes.
How can this be manually tested? (brief repro steps and corpnet-URL with change)
Run powershell -f Create-StorageContainer.ps1 (with the appropriate parameters)
Without the changes, the setup fails with Login Failed | const { required, nullable } = mapper;
With the changes, the error goes away.
What are the relevant TFS items? (list id numbers)
N/A
Definition of done:

[x] Title of the pull request is clear and informative
[ ] Add pull request hyperlink to relevant TFS items
[ ] For large or complex change: schedule an in-person review session
[ ] This change has appropriate test coverage
[ ] Get at least two approvals

Reminders DURING merge

If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.

Change Looks good.
As part of our branching strategy,
we should create the PR against oxa/dev.fic and send it to release and then to ms.fic.

please cherry-pick these into dev.fic as well.

So, do you are resolving the issue?, and wil be merge with new build of oxa-tools.
And later we need just git clone again and redeploy???
When this issue will be updated?
I'm now with Latam Lex team compromised for release a new site ASAP!...
:(

@larryuribe, I have updated the issue


What happen if we have 10000 children

Hi, i have a type here
/**
 *
 */
export interface IModelTree {
  type: string;
  expressID: number;
  elementIdMap: ElementIdMap;
  checked: boolean;
  children: IModelTree[];
}```
So what happen with performance if i have 10000 elements, each element has 10000 child anf 5 grades like that? Many thank

Hi @RyugaRyuzaki,
The component hasn't been stress-tested. Can't say much, but I guess it won't be pretty.
A good thing is that the component won't insert all items into the DOM tree until the node is expanded. So it won't attempt to render all items at once in DOM. This is good.
Although 1000 children on the same level is a problem. There are packages that try to avoid rendering items, unless they are in the view. I guess that would be the direction you should follow. So the items that the user doesn't see are not in the DOM tree. Right now, they would be.
Anyways, good luck with your project!

So @mui/treeview is beeter than this?

There are no explicit benefits in @mui/treeview, taking into account your context. The same limitations and recommendations apply: load and render only children you intend to show and/or in viewport.

There are no explicit benefits in @mui/treeview, taking into account your context. The same limitations and recommendations apply: load and render only children you intend to show and/or in viewport.
So this library can not design for load only once. I mean we can check if each child just render oly once time when we click expand

This function is long task. What if we have a parent 1000 children and 1000 grandchildren, how we can increase performance?


Fix Docker support for the app

DO NOT MERGE
The deployment script actually looks for the tmp_Dockerfile and uses it as is. However, since we don't have access to the deployment process implemented by the cloud team, it will be difficult to fix this without risking production or staging.

@shawnthompson Just an FYI on how I managed to get the app running locally. As discussed, the cloud team is not using MongoDB native but a Azure variant under their Cosmos DB service.

@wmoussa-gc, what are your thoughts about, instead of renaming. Keeping the names as-is for the cloud hosting and using the typical file naming like the renaming you did to allow us to try to run docker locally for development? This way we are touching the files the cloud is dependent on and giving us the allowance to use docker locally instead of installing Mongo and node directly on our machines?


Plumb through workflow type into client (#1170)

This is the client side change needed to plumb the workflow type into the activity info.
The following image shows the code the activity author writes to access these fields

As a follow up diff I will update metrics and logger to include these tags.

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

Coverage increased (+0.03%) to 69.105% when pulling 1c4a0a56f687bdfefedc9e1eab994f173bd9ce79 on andrewjdawson2016:andrew_dev into dca3f7dd9f624e61323a33d4eff735697ff9f175 on uber-go:master.


Taking defaults for Create New Web App results in error

Right click in App Service explorer on a subscription, choose "Create New Web App"

provide a unique name
take the defaults ...

Create new resource group
Linux
Node.js 10.10 (LTS ...)
Create new app service plan
Location: select Central US

Result:

I can repro this, there are no prompts for naming the plan or resource group.

Are you guys testing on master, released, or webpacked? The webpacked extension has not even been put up for PR yet...

Nope, on 0.10.0 from the marketplace. I made Chris uninstall and reinstall from prod

I can't repro this and these errors are not common at all in telemetry. "uninstall and reinstall" doesn't usually do anything if the versions are the same. You have to actually go here and delete the extension folder before reinstalling:

Windows %USERPROFILE%.vscode\extensions
macOS ~/.vscode/extensions
Linux ~/.vscode/extensions

Damn, I thought that was only an issue when moving ahead.. works for me, I'll update Chris'

Confirmed working correctly in stable.

Good to know, thanks. I do want to track these issues, but maybe just in OneNote or on GitHub with a "webpack" label until it makes it into master

I've created this: https://microsoft.sharepoint.com/teams/azcode/_layouts/OneNote.aspx?id=%2Fteams%2Fazcode%2FSiteAssets%2Fazcode Notebook&wd=target(Development.one|B171B793-3162-4BAC-8605-42D58625B875%2FWebpack Issues|56A53AF6-0EF2-4C69-8E42-721756C94D86%2F)
onenote:https://microsoft.sharepoint.com/teams/azcode/SiteAssets/azcode Notebook/Development.one#Webpack Issues&section-id={B171B793-3162-4BAC-8605-42D58625B875}&page-id={56A53AF6-0EF2-4C69-8E42-721756C94D86}&end
I'll move my current issues there, too.


Fix maven configuration

Make root the parent module
introduce a core-only profile, used typically for releases
fix scm configuration

Very helpful!
So with this, I assume that the normal release:prepare and similar steps would receive -Pcore-only?
I presume that I could build a 3.3 parent pom by applying the profile and scm changes to the old parent/pom.xml so that I could redo the release and retain only the parent pom in the release process. Does that make sense to you?

Yes, this should work:

mvn release:prepare release:perform -Pcore-only directy in root dir
connect to Sonatype OSS, and remove core module files from the staging repository before closing and releasing it

OK. THAT was harder than it should have been.

Java 12 versus old javadoc versus maven bug
Had to specific a language level for the javadoc plugin

./parent and ./core project structure doesn't work right with combo of github and maven so release:prepare failed. This bug has been known for nearly 10 years. See https://issues.apache.org/jira/browse/MRELEASE-767 for some history.
Had to put bogus scm connection to point to origin rather than the full git URL to fix the problem with release:prepare

Fix for item (2) breaks release:perform. That required -DlocalCheckout to avoid any reference to the github repo during the perform step.

the documentation for maven scm URLs on the maven site is wrong as to the form of github URLs.

Various items had to be copied from the core pom to the parent pom to satisfy sonatypes release checks.

But ... it worked!
See https://github.com/tdunning/t-digest-example for an example of a free-standing project that uses the new version.
Now I just have to clean up the mess for the mainline development.

Sorry, I really didn't test that :( I compile all my projects with Java 8 because of ByteBuffer binary compatibility breakage.

Actually, I suspect your issues come from the fact I didn't force/upgrade all the plugins versions so you're still using the old buggy versions from the time maven 3.0 was released and default versions were set. I'll provide a PR for upgrading/setting the plugins versions.

Actually, I moved to a much more recent version of the release plugin. No
change.
You can't really see the extra experiments that I did, but I did grid
search in options to try to understand things. I think I tried nearly a
hundred alternatives.
Still, all advice is welcome, especially regarding the newer, more standard
structure.  Frankly, in my down moods, I think I might well just revert to
using three separate projects and tell people to use maven install.
On Sun, Jun 13, 2021, 11:59 PM Stephane Landelle @.***>
wrote:

Sorry, I really didn't test that :( I compile all my projects with
Java 8 because of ByteBuffer binary compatibility breakage.

Actually, I suspect your issues come from the fact I
didn't force/upgrade all the plugins versions so you're still using the old
buggy versions from the time maven 3.0 was released and default versions
were set. I'll provide a PR for upgrading/setting the plugins versions.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/pull/173#issuecomment-860433121,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5E6TSHXTMICOIT77MCCDTSWSEFANCNFSM46KZMVAA
.

Well, I'm 100% sure I could fix things for you if you were willing to (temporarily) make me a committer (so I can create the tag and the commits) and a publisher on maven central on the com.tdunning groupId. I can perfectly understand if you're not willing to go this way.
Anyway, I'm going to provide an extra PR with all the upgrades. I've done this kind of things many times, eg https://github.com/AsyncHttpClient/async-http-client

I am happy to take your updates and test them for you. Or have you test
them..
But I would like to hear what structure you are headed for before that.
On Mon, Jun 14, 2021 at 12:37 AM Stephane Landelle @.***>
wrote:

Well, I'm 100% sure I could fix things for you if you were willing to
(temporarily) make me a committer (so I can create the tag and the commits)
and a publisher on maven central on the com.tdunning groupId. I can
perfectly understand if you're not willing to go this way.
Anyway, I'm going to provide an extra PR with all the upgrades. I've done
this kind of things many times, eg
https://github.com/AsyncHttpClient/async-http-client
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/pull/173#issuecomment-860458295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5E6SXWSDF2LAQMIRQIQLTSWWU7ANCNFSM46KZMVAA
.

But I would like to hear what structure you are headed for before that.

I don't suggest any more structure changes. The ones you've merged are plenty enough IMHO.
I'm just suggesting forcing plugins versions instead of using defaults (that were never updated since maven 3.0 ages ago, because that would be a breaking change).

Well, I would like to move to a structure that you suggested with the parent at the root. The parallel parent is a mess and seems to be outside the vision that maven has (otherwise, I wouldn't have seen so many ancient bugs).
But even that is up for debate. Should there even be a unifying pom?
And how should serialization packages be handled? My guess is that they should be parallel to core and released as separate artifacts to avoid dependencies on the core package. Your input would be valuable.

Well, I would like to move to a structure that you suggested with the parent at the root.

Sorry, I don't get it. This is what this PR you've already merged does, see https://github.com/tdunning/t-digest/pull/173/files#diff-8d04401f1cc51365fe3e32f019cd720135ba920a1a7da7f19e9c9208478701fcR27

And how should serialization packages be handled?

What are you referring to?

Sorry about the confusion. The t-digest-3.3-repair branch still has the old
structure. I don't want that to survive.
Regarding serialization, it is desirable to have serialization for digests
using, say, Avro, Arrow, Kryo, JSON, protobuf and other frameworks. But
each of these introduces dependencies that I want to avoid for the core
t-digest package. Also, users of Arrow should not need to have Kryo or
protobuf dependencies.
Thus, my thought that releasing separate serialization artifacts would be
good. To me, this is the strongest argument right now for multiple modules.
On Mon, Jun 14, 2021 at 9:07 AM Stephane Landelle @.***>
wrote:

Well, I would like to move to a structure that you suggested with the
parent at the root.
Sorry, I don't get it. This is what this PR you've already merged does,
see
https://github.com/tdunning/t-digest/pull/173/files#diff-8d04401f1cc51365fe3e32f019cd720135ba920a1a7da7f19e9c9208478701fcR27
And how should serialization packages be handled?
What are you referring to?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/pull/173#issuecomment-860805860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5E6UNNUSXSOMMSYL4IT3TSYSKTANCNFSM46KZMVAA
.

Sorry about the confusion. The t-digest-3.3-repair branch still has the old
structure. I don't want that to survive.

Well, the main branch looks pretty good to me. BTW, I had fixed your scm issue: https://github.com/tdunning/t-digest/commit/8630c2b678ae5d2c055ee26bea6cf0af79c55fa6#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R11-R12

Thus, my thought that releasing separate serialization artifacts would be
good. To me, this is the strongest argument right now for multiple modules.

Yes, each one of those should should be a module. Way cleaner than a huge module with lots of optional dependencies (or worse, not flagged as optional).

On Mon, Jun 14, 2021 at 9:55 AM Stephane Landelle @.***>
wrote:

Sorry about the confusion. The t-digest-3.3-repair branch still has the old
structure. I don't want that to survive.
Well, the main branch looks pretty good to me. BTW, I had fixed your scm
issue: 8630c2b
#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R11-R12
https://github.com/tdunning/t-digest/commit/8630c2b678ae5d2c055ee26bea6cf0af79c55fa6#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R11-R12

"fixed" in the sense of made correct. Unfortunately, this interacted with
the bugs I hit in the maven release plugin so I had to make it "wrong" to
get it to work.
I prefer your path. Make it right and make the structure work with what
maven likes.


How to convert ssd.caffemodel to mxnet_ssd.params?

For example, I have the VGG_VOC0712_SSD_300x300_iter_60000.caffemodel, and I want to get the same ssd_300-symbol.json and ssd_300-0000.params, would you show me how can I convert the ssd.caffemodel to mxnet_ssd.params and mxnet_ssd-symbol.json? Thank you.

There are several non-official caffe layers in ssd, some are not even versatile, so the mxnet converter won't recognize the caffemodel. I have not plan to modify the converter because I still can't find an elegant way to construct a network from caffemodel cause some parameters must be manually set before that, in other words, convert prototxt to .json is a bit tricky. That why the network has to be designed prior to that.
However, convert caffemodel to .params is way easier, convert convolutional layers is written in converter, all you have to do is to find the Normalize layer and grab the scaling parameters. All these operations could be done in python with numpy and protobuf, mxnet use arg_params and aux_params simply as dicts.
Feel free to submit a PR if you find better ways.

thank you, I will try it ^-^


Fix to stop the graph breaking when zoomed in too far

Resolves #411

:+1: LGTM

Might have to get it up-to-date.

:+1: - I'm happy to rebase this and merge now :)

Thanks @rjmcneill - rebased and merged in #429

Thanks @jleft :)


Fix for KAFKA-2446

This bug was introduced while committing KAFKA-2205. Basically, the path for topic overrides was renamed to "topic" from "topics". However, this causes existing topic config overrides to break because they will not be read from ZK anymore since the path is different.
https://reviews.apache.org/r/34554/

This bug was introduced while committing KAFKA-2205. Basically, the path for topic overrides was renamed to "topic" from "topics". However, this causes existing topic config overrides to break because they will not be read from ZK anymore since the path is different.
https://reviews.apache.org/r/34554/


Integrate a smtpd in order to send mail from localhost

It would be nice if the plugin supports sending from a smtp server spun up locally inside the container as well.
This could be useful if it needs to be integrated into golang: https://github.com/flashmob/go-guerrilla/wiki/Using-as-a-package

Drone plugins are supposed to be as simple and lightweight as possible. Spinning up an SMTP server just to send a build notification mail sounds like overkill to me. In my opinion, the SMTP server doesn't belong in the plugin container, but should exist as a separate one.
So, instead of integrating the SMTP server into drone-email, you should be looking into running an SMTP server in a separate container and connecting to that container using the drone-email plugin.

And in worst case everybody is encouraged to fork plugins and add functionality that doesn't make it into the existing plugins.

I'll close this now, as I don't think it should be a part of this plugin.


Add support for redirect of old id-URL

review and implement something like this old commit

redirect products
redirect categories
redirect manufacturers
redirect suppliers

 Redirect old IDs

I think this behavior isn't implementable in a clean error-proof way.
New URLs could have ID too (if the user wants it) and can be error prone to hard code a fuzzy logic to determine when a given URL is "the old one" or not ..
It would introduce unnecessary computational overhead too
The right way to accomplish the job is to add a rewrite rule in the web server (vhost or .htaccess).
This feature will not be implemented


Use the specified checkpoint during the test stage

Sorry, in the testing stage, the default is to use the best checkpoint, but if I want to use the specified checkpoint instead of the saved best checkpoint, where do I change  ？

Hi! Please have a look at our dedicated tutorial on check pointing on the SpeechBrain website :-) it's better to fully understand.

Hello @SitalLiang,
Is your question solved?

Hello,
There has been no activity for a very long time. Therefore, I am closing this issue.
Feel free to reopen if needed. Thanks! :)


failed the initial dns/balancer resolve for xxx with: table: 0x46462b88

Summary
kong api get {"message": "An unexpected error occurred"} and the error shows lots of like "failed the initial dns/balancer resolve for xxx with: table: 0x46462b88", client: xxxx, server: kong, request: "POST xxxxx", host: "xxxxx", referrer: "xxxxx"
Steps To Reproduce

Additional Details & Logs

Kong version (0.12.3)

Kong debug-level startup logs
  2018/11/15 12:55:23 [verbose] Kong: 0.12.3
  2018/11/15 12:55:23 [debug] ngx_lua: 10010
  2018/11/15 12:55:23 [debug] nginx: 1011002
  2018/11/15 12:55:23 [debug] Lua: LuaJIT 2.1.0-beta3
  2018/11/15 12:55:23 [verbose] no config file found at /etc/kong/kong.conf
  2018/11/15 12:55:23 [verbose] no config file found at /etc/kong.conf
  2018/11/15 12:55:23 [verbose] no config file, skipping loading
  2018/11/15 12:55:23 [debug] admin_access_log = "logs/admin_access.log"
  2018/11/15 12:55:23 [debug] admin_error_log = "logs/error.log"
  2018/11/15 12:55:23 [debug] admin_http2 = false
  2018/11/15 12:55:23 [debug] admin_listen = "<IP_ADDRESS>:8001"
  2018/11/15 12:55:23 [debug] admin_listen_ssl = "<IP_ADDRESS>:8444"
  2018/11/15 12:55:23 [debug] admin_ssl = true
  2018/11/15 12:55:23 [debug] anonymous_reports = true
  2018/11/15 12:55:23 [debug] cassandra_consistency = "ONE"
  2018/11/15 12:55:23 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
  2018/11/15 12:55:23 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
  2018/11/15 12:55:23 [debug] cassandra_keyspace = "kong"
  2018/11/15 12:55:23 [debug] cassandra_lb_policy = "RoundRobin"
  2018/11/15 12:55:23 [debug] cassandra_port = 9042
  2018/11/15 12:55:23 [debug] cassandra_repl_factor = 1
  2018/11/15 12:55:23 [debug] cassandra_repl_strategy = "SimpleStrategy"
  2018/11/15 12:55:23 [debug] cassandra_schema_consensus_timeout = 10000
  2018/11/15 12:55:23 [debug] cassandra_ssl = false
  2018/11/15 12:55:23 [debug] cassandra_ssl_verify = false
  2018/11/15 12:55:23 [debug] cassandra_timeout = 5000
  2018/11/15 12:55:23 [debug] cassandra_username = "kong"
  2018/11/15 12:55:23 [debug] client_body_buffer_size = "8k"
  2018/11/15 12:55:23 [debug] client_max_body_size = "0"
  2018/11/15 12:55:23 [debug] client_ssl = false
  2018/11/15 12:55:23 [debug] custom_plugins = {}
  2018/11/15 12:55:23 [debug] database = "postgres"
  2018/11/15 12:55:23 [debug] db_cache_ttl = 3600
  2018/11/15 12:55:23 [debug] db_update_frequency = 5
  2018/11/15 12:55:23 [debug] db_update_propagation = 0
  2018/11/15 12:55:23 [debug] dns_error_ttl = 1
  2018/11/15 12:55:23 [debug] dns_hostsfile = "/etc/hosts"
  2018/11/15 12:55:23 [debug] dns_no_sync = false
  2018/11/15 12:55:23 [debug] dns_not_found_ttl = 30
  2018/11/15 12:55:23 [debug] dns_order = {"LAST","SRV","A","CNAME"}
  2018/11/15 12:55:23 [debug] dns_resolver = {}
  2018/11/15 12:55:23 [debug] dns_stale_ttl = 4
  2018/11/15 12:55:23 [debug] error_default_type = "text/plain"
  2018/11/15 12:55:23 [debug] http2 = false
  2018/11/15 12:55:23 [debug] latency_tokens = true
  2018/11/15 12:55:23 [debug] log_level = "notice"
  2018/11/15 12:55:23 [debug] lua_package_cpath = ""
  2018/11/15 12:55:23 [debug] lua_package_path = "./?.lua;./?/init.lua;"
  2018/11/15 12:55:23 [debug] lua_socket_pool_size = 30
  2018/11/15 12:55:23 [debug] lua_ssl_verify_depth = 1
  2018/11/15 12:55:23 [debug] mem_cache_size = "128m"
  2018/11/15 12:55:23 [debug] nginx_daemon = "on"
  2018/11/15 12:55:23 [debug] nginx_optimizations = true
  2018/11/15 12:55:23 [debug] nginx_user = "nobody nobody"
  2018/11/15 12:55:23 [debug] nginx_worker_processes = "auto"
  2018/11/15 12:55:23 [debug] pg_database = "kong"
  2018/11/15 12:55:23 [debug] pg_host = "<IP_ADDRESS>"
  2018/11/15 12:55:23 [debug] pg_port = 5432
  2018/11/15 12:55:23 [debug] pg_ssl = false
  2018/11/15 12:55:23 [debug] pg_ssl_verify = false
  2018/11/15 12:55:23 [debug] pg_user = "kong"
  2018/11/15 12:55:23 [debug] prefix = "/usr/local/kong/"
  2018/11/15 12:55:23 [debug] proxy_access_log = "logs/access.log"
  2018/11/15 12:55:23 [debug] proxy_error_log = "logs/error.log"
  2018/11/15 12:55:23 [debug] proxy_listen = "<IP_ADDRESS>:8000"
  2018/11/15 12:55:23 [debug] proxy_listen_ssl = "<IP_ADDRESS>:8443"
  2018/11/15 12:55:23 [debug] real_ip_header = "X-Real-IP"
  2018/11/15 12:55:23 [debug] real_ip_recursive = "off"
  2018/11/15 12:55:23 [debug] server_tokens = true
  2018/11/15 12:55:23 [debug] ssl = true
  2018/11/15 12:55:23 [debug] ssl_cipher_suite = "xxxxxxx"
  2018/11/15 12:55:23 [debug] ssl_ciphers = "xxxxxxx"
  2018/11/15 12:55:23 [debug] trusted_ips = {}
  2018/11/15 12:55:23 [debug] upstream_keepalive = 60
  2018/11/15 12:55:23 [verbose] prefix in use: /usr/local/kong
  2018/11/15 12:55:23 [verbose] preparing nginx prefix directory at /usr/local/kong
  2018/11/15 12:55:23 [info] prefix directory /usr/local/kong not found, trying to create it
  2018/11/15 12:55:23 [verbose] SSL enabled, no custom certificate set: using default certificate
  2018/11/15 12:55:23 [verbose] generating default SSL certificate and key
  2018/11/15 12:55:23 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
  2018/11/15 12:55:23 [verbose] generating admin SSL certificate and key
  2018/11/15 12:55:24 [verbose] could not start Kong, stopping services(because it's already started,I shouldn't stop it here)

Kong error logs
  2018/11/15 12:20:24 [error] 30168#0: *7761784214 [lua] balancer.lua:533: get_balancer(): balancer not found for xxxxxx, will create it, client: xxxxx, server: kong, request: "GET xxxxx HTTP/1.1", host: "xxxxxx", referrer: "xxxxxxx"

  2018/11/15 12:20:54 [error] 30168#0: *7761784214 [lua] responses.lua:121: after(): failed the initial dns/balancer resolve for 'xxxxxxx' with: table: 0x46462b88, client: xxxxxxx, server: kong, request: "GET xxxxxxx HTTP/1.1", host: "xxxxxxx", referrer: "http://xxxxxxx"

Kong configuration (the output of a GET request to Kong's Admin port - see
    prefix = /opt/app/kong/       # Working directory. Equivalent to Nginx's
  proxy_listen = <IP_ADDRESS>:80     # Address and port on which Kong will accept
  proxy_listen_ssl = <IP_ADDRESS>:443 # Address and port on which Kong will accept
  admin_listen = <IP_ADDRESS>:8888   # Address and port on which Kong will expose
  admin_listen_ssl = <IP_ADDRESS>:8444  # Address and port on which Kong will
  nginx_user = nginx nginx      # Defines user and group credentials used by
  nginx_worker_processes = auto   # Determines the number of worker processes
  pg_host = xxxx             # The PostgreSQL host to connect to.
  pg_port = xxxx                  # The port to connect to.
  mem_cache_size = 256m       #The size of memcache
  client_max_body_size = 200m
  client_body_buffer_size = 1024k
  admin_access_log = logs/admin_access.log main
  #proxy_access_log = logs/access.log main
  proxy_access_log = off
  pg_user = xxx                  # The username to authenticate if required.
  pg_password = xxx                  # The password to authenticate if required.
  pg_database = xxx              # The database name to connect to.

Operating system
CentOS release 6.9 (Final)

I think it's kind of memory leak or something, because I have 4 kong on different host, it appears on host which worker used about 20% memory, after I restart kong service, the problem solved.But I can't sure once again the memory usage raise up the problem will show up, because now my production service has migrate back to nginx. I think it's the local balancers = {} lead to this issue, because I will frequently update the weight of the targets in some cases, this caused too many connections error before

can you provide the actual logs with stack traces etc?


pretrained model and single speaker adaption

hi, can you share a pretrained model and how to transfer learn to adapt to a single speaker?

@mkotha Thanks for your implementation. Any plan to share a pre-trained model with VQVAE-WaveRNN?


Tracking Issue

Post DL creation in the service if an update cannot occur due to a blocker - skip that update and record it for administrator intervention rather than fail the migration.

Version 2.4.8.
This version changes non-critical error handling.  For example, let's say when the migration started the group was a member of a distribution group.  During the migration - the group that this group was a member of was deleted.  Post migration when re-adding this group back - the script would fail and end entirely - just because one group could not be updated.
The script no longer hard fails on non-critical errors.  Non-critical errors are now tracked - and at the end they are added to the end of the log and the failure routine is called.
The list at the end of the log shows items that the administrator may need to handle manually.  The goal being to complete as much of the migration as possible without not completing tasks towards the end.


over provisioning & test cert to be configured from settings page

over provisioning & test cert to be configured from settings page

Commit_ID 3faf52c9a846f2ee6f5a64307c5afcf1f1d2468f , Branch development


Improve Dependency Resolution for Workflow Optimization

Title:
Improve Dependency Resolution for Workflow Optimization
Body:
Summary:
The current implementation of our GitHub Action, as defined in sanguine/contrib/git-changes-action, uses go.mod to determine dependencies for triggering workflows. This broad approach can lead to unnecessary workflow runs, as changes in dependencies that do not directly affect the module in question still trigger the workflow. We propose enhancing our dependency resolution mechanism to be more granular, focusing on package-level dependencies rather than module-level dependencies defined in go.mod.
Problem:
Currently, if any dependency within a module changes, our workflow is triggered, regardless of whether the change directly impacts the packages our module uses. This leads to inefficient use of resources, as workflows run for changes that are irrelevant to the module's operation. For example, if our module A directly depends on package A from module B, we want to trigger the workflow only if package A (or any package within A's dependency tree) changes. Changes in module B that do not affect package A should not trigger our module A's workflow.
Proposed Solution:
Implement a more refined dependency tracking system that:

Identifies direct package-level dependencies for each module within our project.
Triggers workflows only when there are changes in the directly dependent packages or any package within their dependency tree.
Excludes broader module-level changes from triggering workflows when the changes do not affect the directly used packages.

This approach aims to optimize our CI/CD process by reducing unnecessary workflow runs, thereby saving computational resources and developer time.
Expected Benefits:

Efficiency: Reduces unnecessary CI/CD runs, focusing only on relevant changes.
Resource Optimization: Better use of computational resources, decreasing overall run times and potential costs.
Developer Productivity: Developers can focus on changes that directly impact their work, reducing noise from unrelated workflow runs.

Request:
We seek input from the community and the project's maintainers on the feasibility of this approach and any suggestions for implementation strategies. Additionally, we're looking for contributors interested in developing this enhancement.

/bounty $800

/attempt #2235

can i get assigned?

@oliverqx apologies, this is my first time using algora. Would you happen to kno the slash command for that?

oh I see it.

thanks!

Hey @oliverqx. All the best for your PR.
But can I pick it up or you are working on it?

im currently working on the solution, feel confident about the ETA i previously shared

love to hear it

@trajan0x just to give an update,
I think i might need a couple more days, testing my changes on github actions has been a bit more challenging than i predicted but I'm almost there. Will open a PR tomorrow and keep working. I'm pretty sure I'll be done by saturday. I was doing this half time and the next two days i can go full time into it

If you guys are okay i can give it a try as well @oliverqx @trajan0x

@oliverqx got it. If there's anything I can answer to help lmk
@shashank40 gonna leave that up to @oliverqx

Till then @trajan0x you can point me to other important issues?

Any update @oliverqx ?

I'm working on it, I'll open my PR in a couple of hours

@shashank40 have something for you to try out if you're reasonably comfortable w/ docker

Sure @trajan0x. I can pick Docker. I have worked with it quite a few times.

@shashank40  actually, had a different idea first. Please see #2318
@oliverqx just checking in here

hey @trajan0x thank you for your patience. I think I'm finally done. Doing this part time was quite a challenge as I kept loosing my train of thought, and that pushed me back a couple of steps each time I did.
I've created this dummy package that showcases the changes I've made to git-changes-action.
Just a heads up, I thought having some sort of categorical relation between modules and packages would make it easier to follow their dependencies, and only later noticed this naming convention is very awkward. But I think both the readme file and opened PRs explain everything quite well.
Only two things left to do:

clean recursion for deep dependency resolution
migrate my changes to synapsecns' sanguine repo, this is because I made a clean copy of the go project to test changes more efficiently. The changes I've made so far can be seen here. But I'll be opening a formal PR after getting some sleep.