Create a secret for external PostgreSQL instances

What this PR does / why we need it:
SonarQube makes an assumption about the name of a PostgreSQL secret when using an external server, which doesn't necessarily align with what a user has done. Instead, the chart should create a secret to store the PostgreSQL password, and consume that.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
N/A (issue as PR)
Special notes for your reviewer:
Simple change, I think?

/assign
/ok-to-test

/lgtm

/retest

@rjkernick Looks like the PostgreSQL chart isn't setting up the user properly; have you seen this behaviour before?

I have not. I'll take a look in the morning and see if there are any recent
changes to the postgres chart.
On Wed, May 2, 2018, 10:12 PM Michael Laccetti<EMAIL_ADDRESS>wrote:

@rjkernick https://github.com/rjkernick Looks like the PostgreSQL chart
isn't setting up the user properly; have you seen this behaviour before?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/charts/pull/5351#issuecomment-386174547,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFL5WE7vJTYMvMkiOTEd0It2sJoWgh3Rks5tumeegaJpZM4TvegX
.

Not seeing any breaking changes in the postgres chart. I have a feeling it is an issue with the charts test environment

/retest

Created #5374 to address the test failures. Once that is merged, you can rebase and the tests should pass

Please rebase master and bump chart version

Looks like something went wrong on you rebase.

BTW, in general, please don't rebase. Merge in the latest master.  In the PRs are squashed anyways.

@rjkernick Merged.

Thanks. Looks like you just need to bump the version in Chart.yaml to 0.5.5.

/lgtm

/retest


Bump Dependencies

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3549433744

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3549433744
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3551623695

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/3551623695
Status: success


Wrong ELF class: ELFCLASS32

Environment

LWJGL version: 3.2.3
Java version: 11.0.10
Platform: Linux (Ubuntu 20.04)

Description
I set up a lwjgl project using gradle on Ubuntu 20.04. Yes, I do have 64 bit java, as seen below
The Error
OpenJDK 64-Bit Server VM warning: You have loaded library /home/theo/lwjgl/3.2.3-SNAPSHOT/liblwjgl.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /home/theo/lwjgl/3.2.3-SNAPSHOT/liblwjgl.so: /home/theo/lwjgl/3.2.3-SNAPSHOT/liblwjgl.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
        at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
        at

Java Version Proof

File Command Output
❯ file 3.2.3-SNAPSHOT/liblwjgl.so
3.2.3-SNAPSHOT/liblwjgl.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=9ef3fe71bdc1625ae5e589f417b770c1e50a2a6f, stripped

It looks like you're using the snapshot of 3.2.3. 3.2.3 is already released, and 3.3.0 is in its snapshot stage. The link error might be because you selected the wrong natives type (ARM32, rather than ARM64 or x64) on the customize page, or that you switched profiles with Maven.


fix: not raise exceptions during get_challenge_data

Coverage decreased (-0.03%) to 81.348% when pulling a46ca49183f8f8afdbec11f4eae6c7cdcb91277b on 673-get_challenge_data_raise_error into 4013969dc8b5e575041f9b1da9980c5ae0c9fbc2 on master.


BadRequestError

SDK version: sendbird_sdk: ^3.1.4
I received error: "BadRequestError":

i has updated sendbird_sdk: ^3.1.1 to sendbird_sdk: ^3.1.4 but i still receive same error. Please let me know what should i do.

@BatunaAz, are you still seeing that BadRequestError in version 3.1.7?


Leap frog years

Describe the bug
Not sure this is a bug as I could not setup a code sandbox based on the examples.
When clicking on "non-leapfrog" years, the zoom-out-to-year works as expected. When clicking on a "leap-frog" year, nothing happens.
I should mention I have a localized Moment version to "fr-CH":
import 'moment/locale/fr-ch';
Did anybody experience similar issue?
Really puzzling...
To Reproduce
As said, I can't reproduce it on code sandbox.
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Library Version

0.26.7

Desktop (please complete the following information):

OS: MacOS (any version), Windows (any "current" version)
chrome & safari (latest)

Smartphone (please complete the following information):
Additional context

Was in my code... Leap frog year has got 366 days... if you didn't know ;-)
Happy end of the year to everyone!


[Bug]: NoModuleFoundError messsage for Third-Party Integrations

Bug Description
With the update of code modularization in the repo, for each third party integration(LLM's, VectorDB, etc) we need to install a new library/package which is tedious at the first place. Further, when i tried to access those third party LLM lets say HuggingFaceLLM without installing any integration package, the current warning only states  No module found, instead it should be please do `pip install llama_index.llms.huggingface` . This kind of error messages helps the user to understand the background without him searching across StackoverFlow of what went wrong.
I suggest to have these kind of package missing error for each of the third party integrations.
Version
0.10.18.post1
Steps to Reproduce
from llama_index.llms.huggingface import HuggingFaceLLM
Relevant Logs/Tracbacks
ModuleNotFoundError: No module named 'llama_index.llms.huggingface'

It's not possible (to my knowledge) to have an error message for every possible import/package. If you know of a way I welcome a PR though
Checkout out https://llamahub.ai for a listing of all packages + imports
Imo having modular imports allows users to more easily manage their dependencies. All our notebook examples are also updated with proper imports.


Fix macOS target for spm.

When I try integrate library to macOS target via SPM I get error, because UIKit does not exists.
I just add precompile checks, because spm does not allow add exceptions for file.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

I signed it!

Confirmed! @Juraldinio has signed the Contributor License Agreement. Thanks so much.

Hey @Juraldinio Thanks for the PR!
We're about the release v2, are you ok for this to be included in v2? I'd like to get v2 out of the door rather than make another v1 release.
There are some breaking changes but it's not a huge migration effort. The beta will be out today/early next week and the final release in April. We will publish a migration doc too which we can link you to.

Sure! Waiting v2.

Hi @Juraldinio , thanks a lot for reporting this and for the PR.
We are going to release today the version 2.0 as it was already prepared and tested for the release.
I'll take care to add your fix to the next patch version 2.0.1.

Thank you!


Feature Request: Windows Support?

I will try but can't promise anything, first I need to get JDTLS running in Windows (something I've tried and wasn't successful).
As an ex Windows user, I suggest you try using WSL


docs: Added more directions for Blog-Only Mode

The original docs did not explicitly explain that it is possible to keep a homepage and alter the name of the route for the blog. There was also no recommendations to adjust the default links in the navbar/footer. I also added in some behavior that is expected if they do not delete their home index.js and duplicate routes are found.

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

That's a lot of duplicated content from docs-only. Maybe we should link to there instead and note about the discrepancies?

Related to https://github.com/facebook/docusaurus/pull/8382
Docs should remain consistent across content plugins and avoid duplication.
Let me know if you want to work on a better doc for the whole routeBasePath thing, otherwise we'll close both PR and handle this ourselves.

Thanks for taking a look at this! I was walking through the blog-only setup and wanted to add some information that was helpful for me. I certainly agree with not duplicating the information. Ultimately I was able to get it working given the current state of the doc so maybe this change is unnecessary.
Honestly - did not see the plugin-specific section in the API section of the docs when I submitted this pull request. Maybe I should have seen this. The link is at the top of the page :laughing:. It's a bit more clear now that I have read what's going on there for the blog plugin specifically. Feel free to close this as it looks like a fix is being worked on via #8382.

Thanks, let's close then, we'll still try to improve this doc but in another PR ;)


It stops downloading?

HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/?next=/graphql/query
myusername: Redirected to login page. Use --login.
Errors or warnings occurred:
myusername: Redirected to login page. Use --login.
It goes along perfect then i started to get this error and it would stop the download? Could someone help thanks

duplicate of #1617 (and #1666).

My bad did not read those


All service areas from all services at location inherited when using 'keyword' search.

See issue and discussion
https://github.com/codeforamerica/ohana-api/issues/365

Build out a search vector for each service, remove search vector from locations.  See if that corrects the issue.

Vector to testing stage, but root partition on drive is full.  Must complete computer maintenance and try again.

Conversation is on wrong project


Update Django 3.0.11 to 3.1.6

Description
Django dependencies upgrade.
Checklist:

[X] I've made sure that tests/test_cookiecutter_generation.py is updated accordingly (especially if adding or updating a template option)
[X] I've updated the documentation or confirm that my change doesn't require any updates

Rationale
Fix #2795

Thanks for the review @browniebroke, I have added fixes to the PR.
What's the methodology for making those deployment? Who is making them?
Is it the community running those test manually and fetching this PR to test?

Needs to be done manually. Can be tested by running the following command and answering the usual questions:
cookiecutter https://github.com/areski/cookiecutter-django --checkout fix_django_31

already released few days ago: https://docs.djangoproject.com/en/dev/releases/3.1.7/

Thanks @mmmcorpsvit, I just pushed a fix for this.


⚠ Bofrost.es has degraded performance

In 783433d, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1552 ms

Resolved: Bofrost.es performance has improved in 40abc64 after 9 minutes.


macos-13: Error: Unable to locate executable file: ninja (ninja 1.10）

on Hi,
I'm trying to migrate my CI jobs to use your get-cmake action to install CMake and Ninja. This seems to work fine on windows and Linux, but all the macos jobs fail with the following error:
 Error: get-cmake action execution failed: 'Error: Unable to locate executable file: ninja. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.'

CI step
      - name: Install CMake
        uses: lukka/get-cmake@4e6d17d5fe05e957a14fb19626cd67b1c192efda # latest commit
        with:
          cmakeVersion: "~3.22.0"
          ninjaVersion: "~1.10.0"

Link to a failing job: https://github.com/corrosion-rs/corrosion/actions/runs/7934441594/job/21665440748?pr=487
Using the latest ninja version seems to work fine, but since Ubuntu 22.04 ships ninja 1.10, I would prefer to test with 1.10 on all OSes.

@jschwe thank you, this is a long standing failure which does not have code coverage. Looks like the ninja archive for the 1.11 release contains one file, ninja, while the 1.10's one has one file called ninja-1.10.2.g51db2.kitware.jobserver-1-macos-universal. This was not accounted for, and needs to be fixed indeed.


Handle unknown date in FileInformation

When I don't know the creation or modification date of the files, what should I set the LastWriteTime and CreationTime in FileInformation to?
According to the documentation for FILE_BASIC_INFORMATION I understand that I should set it to -1, but DateTime don't have any -1. The most logical I can think of is DateTime.MinValue or default(DateTime), but that generate an System.ArgumentOutOfRangeException when DokanOperationProxy.AddTo use DateTime.ToFileTime().
I suggest that DokanOperationProxy.AddTo check for DateTime.MinValue and then set it to -1.

Hi @magol ,
I agree with the proposition, if you can provide a pull request for it, it would be nice !
It should be handle here by a helper:
https://github.com/dokan-dev/dokan-dotnet/blob/40740f2f50c437e5f5fdb9e7729e780d3c6ba9b0/DokanNet/DokanOperationProxy.cs#L335
https://github.com/dokan-dev/dokan-dotnet/blob/40740f2f50c437e5f5fdb9e7729e780d3c6ba9b0/DokanNet/DokanOperationProxy.cs#L471
I never try with -1 value so it should be also tested to be sure of the FS behaviour.

I was wrong with -1, it is only used when you don't wan't to update the date.
According to WIN32_FILE_ATTRIBUTE_DATA structure, you must use 0 if  the underlying file system does not support date.

I changed FileInformations to accepte NULL DateTime as proposed here https://github.com/dotnet/coreclr/issues/6186#event-724927526
https://github.com/dokan-dev/dokan-dotnet/commit/7d0028fbda1814fa261f5a708ed807535954b845


formatOnType strips space on single item unpacking

a, = [1]

becomes
a, =[1]

The space should not be removed.

This is similar to #1788.

Yeah, actually exactly the same


RestClientBuilder doesn't allow AutoCloseable extension of client interface with a type level URI template

The RestClientBuilder throws a RestClientDefinitionException when building from a client interface that extends AutoCloseable and has a URI template on the type level. The Exceptions says Rest client failed: org.eclipse.microprofile.rest.client.RestClientDefinitionException: Parameters and variables don't match on interface on interface Foo::close.
The specification says that the client interface is allowed to extend AutoCloseable. The implementation doesn't allow the unresolved URI template of the close method.

What version of RESTEasy MicroProfile Client are you using? Please note that my replies may be delayed this week as I'm going to be in meetings all this coming week.

Sorry, I should have included that. I'm using Wildfly 27.0.0.Final and it says resteasy-client-microprofile-2.0.0.Final.
I've written a test case that illustrates the issue, you can find it here: AutoCloseableClient.java.


permission denied error

I did chmod a+x checkchan2tgbot.sh, there is also permission denied in logs.

could post your docker compose yaml file?

docker compose file
version: '3'
services:
  webhook:
    container_name: webhook
    image: soulteary/webhook:extend-3.4.5
    environment:
      HOST: "<IP_ADDRESS>"
      PORT: 9000
      VERBOSE: true
      HOOKS: "/app/hooks.yml"
    volumes:
      - ./app:/app
    ports:
      - <IP_ADDRESS>:19000:9000
    restart: always

webhook config
- id: checkchan2tgbot
  execute-command: "/app/checkchan2tgbot.sh"
  command-working-directory: "/app"
  include-command-output-in-response: true
  include-command-out-in-response-on-error: true
  response-message: I got the payload!
  response-headers:
  - name: Access-Control-Allow-Origin
    value: "*"
  pass-arguments-to-command:
  - source: payload
    name: payload.id
  - source: payload
    name: payload.url
  - source: payload
    name: payload.value
  - source: payload
    name: payload.html
  - source: payload
    name: payload.link
  parse-parameters-as-json:
  - source: payload
    name: payload.id
  - source: payload
    name: payload.url
  - source: payload
    name: payload.value
  - source: payload
    name: payload.html
  - source: payload
    name: payload.link

@leic4u
I tried it out, and no exception occurred. I personally guess it's the behavioral difference of Docker under different operating systems.
To solve this issue and avoid similar problems in the future, I made some program improvements. You can replace the program version with 3.5.0 or later versions to resolve such issues.
(No need to manually set the script executable anymore.)
https://github.com/soulteary/webhook/releases

After redeploying v3.5.0, permission denied still appears

Even I also did the chmod a+x /app/checkchan2tgbot.sh.

https://github.com/soulteary/webhook/tree/main/example/muti-webhook
You can try this configuration example, and before starting, execute chmod +x trigger.sh, I tested in macOS and Ubuntu environments, no problem. Either before the container starts, set up or go into the container settings.
But in the Ubuntu environment, if permissions are not set before starting, the permissions may not be recognized by SH. I have thought of a solution and will improve it later. @leic4u

@leic4u try 3.6.0

I haven't encountered this issue because I used the volumes feature in k8s to set the permissions to 0755 when mounting. I hope this helps you
@leic4u
    volumeMounts:
            - mountPath: /etc/webhook/
              name: hooks
...
      volumes:
        - name: hooks
          configMap:
            name: hooks
            defaultMode: 0755


Problems with ungoogled-chromium 88

I use linux Pop!_OS Nvidia 20.10 as OS (Ubuntu).
Since I updated yesterday I have being noticing problems, basically running some streaming video parts are jumpy, like quick cuts while going on. Sound is not affected.
Also while I was resetting my github password filling the text box, github said that my browser was doing something wrong.
I only use unblock origin as add-on, I turned it off and nothing changed.
flatpak version 88.0.4324.104 (Build oficial) (64 bits)
To reproduce:
https://www.youtube.com/watch?v=uhwGD0ADSKI (At 5 min noticeable)
https://www.youtube.com/watch?v=f66VoHQbSdA (Almost since start)
Could anyone confirm if this only happening to me with this new version or it is actually a bug?

It's happening to me too, same flatpak version as yours. I don't know if it's happening also in non-flatpak versions, since I couldn't get the H.264 codec to work with ungoogled-chromium in Fedora.
I think it has to do with the H.264 codec. What you're seeing in youtube videos is probably the automatic setting of video resolution, which is changing from VP8/9 to H.264. Try watching a few videos in dailymotion. They use -afaik- the H.264 codec in all their videos, so you should see the same problem in all of them.

Hi @Pelagius740 , I have tried three different videos at dailymotion and each one are unaffected.
I hope our investigations helps @Eloston .

I'm on Fedora, non-Flatpak UC built without non-free codecs, and I cannot see the problem in the videos you posted. It is probably flatpak specific.

I'm on Debian using unportable (non-free codecs and VA-API). I do not have any issues either. Since you're on a Debian-based system, you could try unportable and see if you have any issues.

Happens to me as well after updating to latest flatpak version, on both youtube videos as well as animated gifs for example on twitter. On youtube, the problem occurs after resolution is set to 360p or above. The codecs thing seems plausible, though I noticed that on the linked video, the codec is shown as avc1 regardless of which resolution is chosen. This is on Manjaro by the way.

Closing because regular Debian builds are back, and OBS is updated. You can try to give them a shot

Unfortunately, the Flatpak version is not updated and still have the video stuttering issue.

I think is solved, I am trying with fjust installed flatpack version Version 87.0.4280.141 (Official Build) built on Debian buster/10, running on Pop groovy/20.10 (64-bit)


[Suggestion] Add a "Back" button

OS: Win10
Build Version: 20191009.1
Regression: Not a Regression
Repro Steps:

F1 --> Type and select "SQL(DocumentDB): Create Stored Procedure".
Prompt to select one subscription if there are 2 applied subscriptions at least --> Select one.

Actual:
There is no "Back" button.
Suggestion:
Add a "Back" button. In this case, it is more convenient for the users to select another resource.

There is no "Back" button when executing command "Import Document into a Collection...".

Closing as duplicate of https://github.com/microsoft/vscode-azurefunctions/issues/1946


If you are using a proxy you don't need to set credentials

currently the config enforces credentials

done


SQL Context tests

Coverage increased (+5.04%) to 83.453% when pulling 4f48dc2252c0d8ad3904420d1290f60b1e6b9248 on htssouza:sql-context-tests into 9e447fa64c8a197c5da6265f3efc2ddc06e347a4 on wdm0006:master.


Update change log for release

Now that the database cluster is self-initializing we can make a release

Pr merged


Add support for pine queries on Concept Type properties

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

I self-certify!

@thgreasi Thanks for adding it! Just a FYI I read it ;) LGTM


Segmentation faults on macOS Sierra.

Godot version:
2.1.5 stable
OS/device including version:
Macos Sierra (10.12.6)
Issue description:
2 of our players have reported crashes at our games launch, we noticed they were both on macos sierra and that they both had segfault: 11 in their console logs.
The full discussion from our players can be read below:
https://steamcommunity.com/app/466800/discussions/1/133256240740552280/
We run a custom module in godot for steamworks integration, unfortunatly we cant easily test if it is caused by the engine or our module since the game in question uses the module as a dependency and taking out all the code would be too time consuming. however because of the console logs mentioning physics 2D i think the cause lays within the engine.
The module in question and its instructions can be found here:
https://github.com/Gramps/GodotSteam/tree/godot2
The game in question can be found here:
https://store.steampowered.com/app/466800/The_Dope_Game/
I have requested one of the players to try and upgrade to high sierra or mojave to confirm if the cause of the problem really lies within that specific OS version. If any further information or other support is needed we will do our best to help out. We really want our players to be able to play without further issue.
Steps to reproduce:
I am unable to reproduce their issue as my own system is running macos mojave, where the game runs fine.

@thisismike97  Can you (or anyone else) still reproduce this bug in Godot 3.2.2 or any later release?
If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.

Closing, since nobody has been able to reproduce this recently. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.


Nuke 13/Python 3 compatibility

The Nuke 13 beta is now public, but with the transfer to Python 3, it looks like a few things have broken.
https://www.foundry.com/products/nuke/beta/13.0
To launch with Nuke 13, you need to add brackets to a bunch of print statements, beyond that there might be other things that have also broken,
While Nuke 13 is still in beta, it would be a good time to look at making everything Python 3 compatible.

Pretty much all of the python is inside of gizmos. So... technically it's a gizmo authors' job to prepare an update for py3.
Plus, I actually think what 1) Foundry will release py2-compatible version, at least initially. Houdini does have both branches to help with transitioning. 2) It's pretty sure Nuke 13 will be barely usable for at last half a year due to bug infestation ;)

Yes, it looks like the change from Python 2 to 3 is still a major challenge for the industry.
A lot of the tools / gizmos etc within the NukeSurvivalToolkit are maybe not maintained anymore, or a bit legacy (written once 5 years ago...).
There are some Python scripts/tools to automatically do the conversion to Python 3.
I wrote to the Nuke support... maybe there is a way to move to Py3 with the help of the original maintainers, Foundry and the community...
And thanks to Tony for putting together the Nuke Survial Toolkit!
Just for the record, here are error messages I am currently getting from Nuke 13 Beta:
Nuke 13.0v1.628907b, 64 bit, built Feb  4 2021.
Copyright (c) 2021 The Foundry Visionmongers Ltd.  All Rights Reserved.
Using "nuke" (RLM) licence.  Beta expires on: 2021/4/5
Traceback (most recent call last):
  File "C:/Users/martin/.nuke/init.py", line 8, in <module>
    import cryptomatte_utilities
  File "C:/Users/martin/.nuke\cryptomatte_utilities.py", line 279
    print "Cryptomatte: Invalid sidecar path (Back-slashes not allowed): ", sidecar_path
                                                                         ^
SyntaxError: invalid syntax

Commenting out the cryptomatte imports I get the following:
Traceback (most recent call last):
  File "C:/Users/martin/.nuke/menu.py", line 34, in <module>
    import stamps
  File "C:/Users/martin/.nuke\stamps.py", line 35, in <module>
    if not globals().has_key('Stamps_LastCreated'):
AttributeError: 'dict' object has no attribute 'has_key'

And commenting out the stamps import:
C:/Users/martin/.nuke/NukeSurvivalToolkit\spin_tools\Keying
  File "C:/Users/martin/.nuke/NukeSurvivalToolkit/menu.py", line 290
    print "Could not load VectorTracker.py"
                                          ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("Could not load VectorTracker.py")?

I've been fighiting with old pluings for compatibility for a while and most of them can be easily updated. The main issues across the board are print statements and how the threading module has been handled.
The main thing is that any update should be backwards compatible but and I doubt most of the tools developers will actually update the codebase. Nukepedia is full PySide tools that were never updated to PySide2.

Some people used this service with success  : https://pythonconverter.com/

Thanks for looking in to this guys,  I'll try and do some research and attempt to convert at least my tools in the toolset.  I know a lot of people are posting updates, so I will try and grab those and update them as well as they pour in.  Feel free to chip in if you fix a python code within a tool and wish to share the fix, I'll try and update the tool.  You can also write an issue ticket per tool you wish to update, might be a nice way to manage.  We'll get it all working, will just take a bit of time and updating.  Thanks again

Hi, did we get anywhere with this?
Looking to use this toolkit with Nuke 13 but getting the below error in the terminal after seeing '.../init.py - error interpreting this plugin':
nuke.pluginAddPath(".\NukeSurvivalToolkit")
^
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 1-2: malformed \N character escape

Put "r" before your path
So you will get something like this:
nuke.pluginAddPath(r".\NukeSurvivalToolkit")
*\n *is interpreted as the new line. With the *r *you avoid this.
There are other solutions, but this one is the easiest one
😉
Il giorno gio 22 lug 2021 alle ore 10:04 DanGraMMU @.***>
ha scritto:

Hi, did we get anywhere with this?
Looking to use this toolkit with Nuke 13 but getting the below error in
the terminal after seeing '.../init.py - error interpreting this plugin':
nuke.pluginAddPath(".\NukeSurvivalToolkit")
^
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in
position 1-2: malformed \N character escape
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CreativeLyons/NukeSurvivalToolkit_publicRelease/issues/10#issuecomment-884727631,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGUI5FWXVKVVUBER324NUDTY7GJ5ANCNFSM4WTDRAMA
.

Hi @gere89
Still getting an issue I'm afraid

Okay, I tried changing the backslashes, to double backslashes and I'm not getting the error anymore. However, the toolkit isn't showing for me in nuke when it boots up. Is this an issue with Nuek 13?

Got it working - cheers for that tip. Ended up having to change a few bits, but works now

Hey folks, Tried many things and every time it gives me this error with Nuke 13
NukeX 13.0v3, 64 bit, built Jun 30 2021.
Copyright (c) 2021 The Foundry Visionmongers Ltd.  All Rights Reserved.
File "C:/Users/Administrator/.nuke/init.py", line 1
nuke.pluginAddPath(r".\NukeSurvivalToolkit")
^
SyntaxError: invalid syntax

nuke.pluginAddPath(r".\NukeSurvivalToolkit")

@gere89 Tried as you said but didn't work also

NST_PlanarProjection.gizmo is still on py2. It's been updated in comment on the gist here

I'm aware that NST expects the original authors to migrate to Python 3.
In that spirit:
CardToTrack by Alexey Kuchinski & Helge Stang has been updated to Python 3.
https://www.nukepedia.com/python/3d/cardtotrack/


allow pushpin at 0,0

This change was made in the compiled version of the code. We have to keep the compiled version in source control for bower to serve it properly. Please reimplement this change in the src/angular-bing-maps/* directory inside the appropriate file.


Tatum daemon on https://api-us-west1.tatum.io

I have a subscribed api key on region us-west1, when I'm trying to run tatum-kms daemon --api-key=XXXXXXX --chain=MATIC it is getting transactions on https://api-eu1.tatum.io/v3/kms/pending/MATIC?signatures=XXXXXX. Is there a way to change TATUM_API_URL using command line?

@manojCoe not sure if you have resolved the issue, but just for the benefits of others, the following is the solution for this issue:
Create an .env file with the following content:
TATUM_API_KEY=<Your Tatum API Key>
TATUM_API_URL=https://api-us-west1.tatum.io

Start the Tatum KMS in daemon mode:
tatum-kms daemon --path=wallet.dat --testnet --chain=BTC  --period=10
If you are using Docker,  run with the similar Docker command:
docker run -d --env-file .env -v $HOME:/root/.tatumrc tatumio/tatum-kms daemon


option to run grunt commands with sudo

my project is so large that i can't run it without sudo. would it be possible to make a checkbox for 'run with sudo'?

Unfortunately I fear that this project is abandoned.


the alonzo UTxO rule to use alonzo minfee function

This PR cherry picks the commit from #2936 for the release branch release/1.0.0. The cherry pick required a bit of massaging due to the glorious recent cleanup in #2901, but can be compared line by line with #2936 to check that is is semantically the same.

I am going to merge, even though ci/hydra:Cardano:cardano-ledger-specs:required is reporting Pending. If you follow the link, all the tests have actually passed.


set ulimits

Hi,
I already sent a mail to dev-nix but i figured here would be a better place ;)
i would like to be able to set ulimits in nixstyle
example:
security.ulimits = {
ejabberd = {
soft = {
nofile = 65536;
nproc = 65536;
};
hard = {
nofile = 65536;
nproc = 65536;
};
};
};
which translates in standard linux /etc/security/limits.d/ejabberd.conf
ejabberd soft nofile 65536
ejabberd hard nofile 65536
ejabberd hard nproc 65536
ejabberd soft nproc 65536
cheers,
peter

(The nixos tree is deprecated, use nixpkgs tree instead.)
You can use the security.pam.loginLimits option for this.

Is anyone able to provide an example of a working security.pam.loginLimits? My nixos-rebuild switch --upgrade worked but the default limits are still used. Here's what I had:
 security.pam.loginLimits = [{     domain = "-";     type = "-";     item = "nofile";     value = "4096";   }];


Update dataset the-stack-v2

This just update bigcode/the-stack to bigcode/the-stack-v2, 67.5TB for all programming languages.
Before submitting

[x] Did you read the contributor guideline?

These datasets only contain the SWHIDs to download the code files and not the content of the files itself. See examples below to see how to download content. We are working on making the training datasets available in the coming weeks.

We cannot directly load this dataset for fine-tuning


Fix _CumprodGrad for 0. inputs

Copyed from https://github.com/tensorflow/tensorflow/pull/32714

Emmm, I just can not visit google at this moment, I'll continue it tomorrow.

@googlebot I signed it!

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!


Problem with path in non-root hosting like Github Pages

When hosted in non-root path, the Manifest and other vite-plugin-pwa are not loaded as it is pointing to a wrong location.

I have tried configuring the vite config

but still having the preceding slash

@hubert17  where is the hosted url?

@userquin https://hubert17.github.io/GabsVuetifyNoCLINodeWebpack

@hubert17
You need to remove the / from manifest icons and includeAssets on vite.config.js:
Just lookup // <== here below:
VitePWA({
            base: '',
            // for prompt comment the option or just remove this option, since it is the default behavior */
            registerType: 'prompt',
            includeAssets: ['favicon.svg'], // <== here
            manifest: {
              name: 'Gabs Vue App PWA',
              short_name: 'Gabs Vue',
              description: 'Gabs Vue App + Vite + Vite PWA ',
              theme_color: '#ffffff',
              icons: [
                {
                  src: 'pwa-192x192.png', // <== here
                  sizes: '192x192',
                  type: 'image/png',
                },
                {
                  src: 'pwa-512x512.png', // <== here
                  sizes: '512x512',
                  type: 'image/png',
                },
                {
                  src: 'pwa-512x512.png', // <== here
                  sizes: '512x512',
                  type: 'image/png',
                  purpose: 'any maskable',
                },
              ],
            }
          })

Done with <==here stuff. :)
I emptied the base for both Vite and Vite-pwa config. But still the manifest link is being preceded with /. My recommendation is for it to behave just like the base in Vite. Where empty string is really empty string. In Vite-pwa, assiging empty string defaults base to "/".

you were looking the page before the reload button clicked:

where is the base entry? I cannot find it.

right now it seems to be working ok, no errors: on network tab, sw and manifest.webmanifest

@userquin
I've added this workaround..

I hope it this would be fixed.

I emptied the base for both Vite and Vite-pwa config. But still the manifest link is being preceded with /. My recommendation is for it to behave just like the base in Vite. Where empty string is really empty string. In Vite-pwa, assiging empty string defaults base to "/".

Add this below manifest entry on vite.config.js:
      workbox: {
        runtimeCaching: [
          {
            urlPattern: /^https:\/\/cdn\.jsdelivr\.net\/.*/i,
            handler: 'CacheFirst',
            options: {
              cacheName: 'jsdelivr-cache',
              expiration: {
                maxEntries: 10,
                maxAgeSeconds: 60 * 60 * 24 * 365, // <== 365 days
              },
              cacheableResponse: {
                statuses: [0, 200],
              },
            },
          },
          {
            urlPattern: /^https:\/\/fonts\.googleapis\.com\/.*/i,
            handler: 'CacheFirst',
            options: {
              cacheName: 'google-fonts-cache',
              expiration: {
                maxEntries: 10,
                maxAgeSeconds: 60 * 60 * 24 * 365, // <== 365 days
              },
              cacheableResponse: {
                statuses: [0, 200],
              },
            },
          },
        ],
      }

You also need to add to index.html crossorigin="anonymous" to exteranl links and scripts:
    <link crossorigin="anonymous" href="https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700,900|Material+Icons" rel="stylesheet" />
    <link crossorigin="anonymous" href="https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>rel="stylesheet" />
    <link crossorigin="anonymous"<EMAIL_ADDRESS>rel="stylesheet" />

    <title>Hello Vue World!</title>
    <script crossorigin="anonymous"<EMAIL_ADDRESS>    <script crossorigin="anonymous"<EMAIL_ADDRESS>    <script crossorigin="anonymous"<EMAIL_ADDRESS>    <script crossorigin="anonymous"<EMAIL_ADDRESS>    <script crossorigin="anonymous"<EMAIL_ADDRESS>

This will make you pwa work offline.

I forget to include fonts.gstatic.com:
``js
workbox: {
runtimeCaching: [
{
urlPattern: /^https://cdn.jsdelivr.net/./i,
handler: 'CacheFirst',
options: {
cacheName: 'jsdelivr-cache',
expiration: {
maxEntries: 10, // <== for testing
maxAgeSeconds: 60 * 60 * 24 * 365, // <== 365 days
},
cacheableResponse: {
statuses: [0, 200],
},
},
},
{
urlPattern: /^https://fonts.googleapis.com/./i,
handler: 'CacheFirst',
options: {
cacheName: 'google-fonts-cache',
expiration: {
maxEntries: 10, // <== for testing
maxAgeSeconds: 60 * 60 * 24 * 365, // <== 365 days
},
cacheableResponse: {
statuses: [0, 200],
},
},
},
{
urlPattern: /^https://fonts.gstatic.com/.*/i,
handler: 'CacheFirst',
options: {
cacheName: 'google-fonts-cache',
expiration: {
maxEntries: 10, // <== for testing
maxAgeSeconds: 60 * 60 * 24 * 365, // <== 365 days
},
cacheableResponse: {
statuses: [0, 200],
},
},
},
],

This will not be fixed, since you are using it in a wrong way.
All server backends have a document root or a default context.
This will work on any server, also on development:
// src/router.js
const router = new VueRouter({
  base: '/GabsVuetifyNoCLINodeWebpack/',
  mode: 'history', // real path
  routes, // short for `routes: routes`
});

// vite.config.js
...
  base: '/GabsVuetifyNoCLINodeWebpack/',
  plugins: [
    createVuePlugin(),
    VitePWA({
      // for prompt comment the option or just remove this option, since it is the default behavior */
      base: '/GabsVuetifyNoCLINodeWebpack/',
      registerType: 'prompt',
      includeAssets: ['favicon.svg'],
      manifest: {
        name: 'PWA Vue2',
        short_name: 'PWA Vue2',
        description: 'Vite PWA + Vue2 + Vite',
        theme_color: '#ffffff',
        start_url: '/GabsVuetifyNoCLINodeWebpack/',
        icons: [
...

I need to do this

So that  "/" (home route) in Vue will point to "/GabsVuetifyNoCLINodeWebpack/".
Again this became an issue because I am hosting in github.io subdirectory.
This preceding slash in manifest's href is the only remaining issue that I have.  If only we could have the option to set that to pure empty string (instead of defaulting it to / when base is ""), that would solve the last issue that I have. :D
But other than that everything is working great! I lovue, vite, and you guys in vite-pwa!!!
Here: https://github.com/hubert17/GabsVuetifyNoCLINodeWebpack
PWA site: https://hubert17.github.io/GabsVuetifyNoCLINodeWebpack/


How do I set up the email forware to gmail or frontapp

How do I set up the email remail to gmail or frontapp

Hi,
You can do it in postfixadmin.  You can set email forward for all incoming emails for a mailbox or a domain as well.

Hi,
You can do it in postfixadmin. You can set email forward for all incoming emails for a mailbox or a domain as well.

Yes, its works.


Fixes #1429: Performance enhancement of backend connect with database by NIO in sharding-proxy

Fixes #1429.
Changes proposed in this pull request:

Replace CountDownLatch with List and Count (means trade space for time), and remove SynchronizedFuture.
Initialize channel pools for every eventLoop of frontend handler and data source name.
If the query results need to be merged, use other thread pool to process for no-blocking.

Pull Request Test Coverage Report for Build 6211

44 of 264 (16.67%)  changed or added relevant lines in 21 files are covered.
16 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-0.4%) to 72.55%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/util/ChannelUtils.java
0
1
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/response/ResponseHandler.java
0
2
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/ShowDatabasesBackendHandler.java
5
8
62.5%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/transport/mysql/packet/command/admin/initdb/ComInitDbPacket.java
6
9
66.67%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/common/FrontendHandler.java
2
6
33.33%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/runtime/schema/MasterSlaveSchema.java
0
4
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/runtime/schema/ShardingSchema.java
0
4
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/response/mysql/MySQLQueryResult.java
0
5
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/mysql/MySQLFrontendHandler.java
0
5
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/common/netty/ServerHandlerInitializer.java
0
7
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/response/ResponseHandler.java
1
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/mysql/CommandExecutor.java
1
37.04%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/common/netty/ServerHandlerInitializer.java
1
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/runtime/schema/MasterSlaveSchema.java
1
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/BackendNettyClient.java
2
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/response/mysql/MySQLResponseHandler.java
2
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/NettyBackendHandler.java
2
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/mysql/MySQLFrontendHandler.java
2
40.74%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/netty/client/response/mysql/MySQLQueryResult.java
2
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/frontend/common/FrontendHandler.java
2
22.73%

Totals

Change from base Build 6210:
-0.4%

Covered Lines:
9359

Relevant Lines:
12900

💛  - Coveralls

Closed. reason just ref #1893


Laravel 10.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.
Before merging, you need to:

Checkout the l10-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: Shift updated your build matrix for Laravel 10. However, since you are supporting older versions of Laravel, you need to add the following exclusions:
exclude:
  - laravel: 10.*
    php: 8.0

:warning: Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 10. However, you should review these changes to ensure the desired combination of versions are built for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/inertiajs-tables-laravel-query-builder.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "protonemedia/inertiajs-tables-laravel-query-builder": "dev-l10-compatibility",
    }
}

Finally, run: composer update

Can a maintainer approve this PR, please!


Updates DLP comments and variables to be better canonical samples

Addresses @alixhami's comments about canonical DLP samples

Leaving this up to @alixhami since he's more familiar with sample standards.

To be honest, I don't think this is a quality improvement overall. These are my concerns:

Prefer to keep documentation text out of samples - There is a lot of explanation in comments about the parameters that is probably already explained in the docs page that will show this sample. It's not a best practice to have redundant information in sample comments because it takes up extra space, is prone to typos, and is less likely to be updated than the documentation copy. Example of information that should be in the documentation copy instead:// (Optional) The name of the surrogate custom info type to use
// Only necessary if you want to reverse the deidentification process
// Can be essentially any arbitrary string, as long as it doesn't appear
// in your dataset otherwise.

Prefer samples to be as short and clear as possible - The samples are noticeably longer now. It's harder to grasp what's going on in a sample if you have to scroll to see the whole thing. This would be fine if the operation was complex enough to need to be long, but I think these are longer than necessary.
Prefer in-context example values to parameters - In our rubric meetings, we decided that it was a best practice to remove as many parameters as possible, which was not done here. It's easier to tell what's going on if you have literal example values in-context rather than parameters. The commented out parameters do show some literal example values, but these are separated from where they are used and the commented out values are not subject to testing, so they are prone to typos. As the user is reading the sample, they have to scroll back and forth between where the parameters are defined and where they are used. This hinders comprehension. (More explanation in my comment on the previous PR). An example of something that does not need to be parameterized is the string to deidentify:
Current (out of context parameter):// The string to deidentify
// $string = 'My SSN is 372819127';
//...
// <lots of code here, requiring user scrolling>
//...
$item = (new ContentItem())
    ->setValue($string);

Proposed (in-context literal):$item = (new ContentItem())
    ->setValue('My SSN is 372819127');

Makes sense. One of these days I'll get around to making these changes.


Roles Empty

I am having an issue with roles.
When I retrieve a user that has roles assigned by doing:
var user = await _userManager.FindByEmailAsync(model.Email);
The roles collection is returned empty.  The same occur w/ FindByIdAsync & FindByNameAsync
Thanks for your work on this library.

Well, what is the behavior of MS Identity? It's lazy loaded or it brings when you use Find methods?
To fix this i'll have to make joins on tables and have a hard mapping, maybe it's easier to use GetRolesAsync.

Fixed in https://github.com/grandchamp/Identity.Dapper/commit/a6dceec67d5516fe14a0feb1c72913be91d322aa
I have to work on FindByLogin.

FindByLogin fixed in https://github.com/grandchamp/Identity.Dapper/commit/ca4e39de2e638838fa9ab4cb4fc6a2578398905d
Check NuGet for the 0.6.3 version.

Thank you very much for your quick response and fix. I was about to send a PR. I was taking a similar approach with the LEFT JOINS.
Again, great work on this lib. Filled a much needed gap.
I am not a fan of EF and tend to use Dapper and other micro ORM's on all my projects.

Oh, If you told me that you were preparing a PR i wouldnt have done. 😁
Thanks for the words! Glad you liked It.


Automatically take Odoo db dump and save it in file system with todays data.

Write a python script which automatically take db dump and save it in local file system for this discussion project. If the #30 is working fine, then also inform user by sending message.
Repeat this process after every week.


scollector on Windows 2008 and 2012 appears to be consuming High CPU processor time

On Windows 2008 SP1 and Windows 2012 Data Center we are seeing the scollector-windows-and64 process consuming 40+/- %Processor Time every 10 seconds (default settings). We are watching the process in perfmon.  Has anyone else seen this?  Is it expected?  On OEL 6 we see single digit CPU being consumed....

Is it a VM? Also how many CPU Coress does it have? Also what version are you using (see scollector -version )

Yes, both are VMs with 2 Cores.
On 2008
C:\scollector>scollector-windows-amd64.exe -version
scollector version<PHONE_NUMBER>0110 (1b01fb0a96425d225a00f8a741c8b7911f3ad953)
On 2012 - same.

hmm... we don't get that on our 4 core VMs. The only spikes we see are from WmiPrvSE durring our DSC configuration runs every 15 minutes. Can you use bosun to graph os.cpu and win.proc.cpu_total (with a * under name) for one of your VMs and see if it shows what is consuming the CPU.
Example from Stack Exchange:

Maybe one of the WMI queries that scollector is doing is expensive due to your workload. For example, we had to refactor the linux network collector because it was reading the proc network table in a slow way. That was on our load balancer, which had thousands of open connections. Does your machine have a similar high load of something?
Possible feature: have scollector report runtimes of its collectors.

OK. I’ll have a look.
Have you looked on the windows servers with perfmon which is set to gather 1 second metrics?  Rather than 15sec average?
From: Greg Bray<EMAIL_ADDRESS>Sent: Monday, March 09, 2015 8:14 PM
To: bosun-monitor/bosun
Cc: Kossack, Ken
Subject: Re: [bosun] scollector on Windows 2008 and 2012 appears to be consuming High CPU processor time (#773)
hmm... we don't get that on our 4 core VMs. The only spikes we see are from WmiPrvSE durring our DSC configuration runs every 15 minutes. Can you use bosun to graph os.cpu and win.proc.cpu_total (with a * under name) for one of your VMs and see if it shows what is consuming the CPU.
Example from Stack Exchange:
[https://cloud.githubusercontent.com/assets/304401/6567105/ecb6a2d0-c687-11e4-9fa6-74663100f34f.png]https://cloud.githubusercontent.com/assets/304401/6567105/ecb6a2d0-c687-11e4-9fa6-74663100f34f.png
—
Reply to this email directly or view it on GitHubhttps://github.com/bosun-monitor/bosun/issues/773#issuecomment-77972120.

Looks like we have spikes up to 16% every 15 seconds and larger spikes every 15 minutes (again due to DSC). Overall average is 3.0-4.5%.

I think Matt is right, you may just have a different work load that causes the WMI queries to be more expensive. I'll look at adding per collector timing metrics, which we can then use to help find and fix expensive collectors.

Is that 16% with 4 cores?  I understand the approach of looking for the expensive WMI calls and removing them, if necessary. The concern I have is that we have another other tool I mentioned also using WMI calls and its CPU usage is in the single digits. So people ask why move to open source solution if it taking more cpu to gather the metrics.  We would like to pursue this beyond avoidance.
From: Greg Bray<EMAIL_ADDRESS>Sent: Tuesday, March 10, 2015 12:50 PM
To: bosun-monitor/bosun
Cc: Kossack, Ken
Subject: Re: [bosun] scollector on Windows 2008 and 2012 appears to be consuming High CPU processor time (#773)
Looks like we have spikes up to 16% every 15 seconds and larger spikes every 15 minutes (again due to DSC). Overall average is 3.0-4.5%.
[cid:image001.png@01D05BE2.B86815F0]https://cloud.githubusercontent.com/assets/304401/6579922/e1ab3f78-c712-11e4-9ab1-dd6d4720ae2e.png
I think Matt is right, you may just have a different work load that causes the WMI queries to be more expensive. I'll look at adding per collector timing metrics, which we can then use to help find and fix expensive collectors.
—
Reply to this email directly or view it on GitHubhttps://github.com/bosun-monitor/bosun/issues/773#issuecomment-78096104.

Two things I can think of. You can lower the default frequency so the
queries run less. On our side I wonder if are checks basically run in
lockstep - maybe we need a scheduler that can smooth out the load.
On Mar 11, 2015 10:04 AM, "kkossack"<EMAIL_ADDRESS>wrote:

Is that 16% with 4 cores? I understand the approach of looking for the
expensive WMI calls and removing them, if necessary. The concern I have is
that we have another other tool I mentioned also using WMI calls and its
CPU usage is in the single digits. So people ask why move to open source
solution if it taking more cpu to gather the metrics. We would like to
pursue this beyond avoidance.
From: Greg Bray<EMAIL_ADDRESS>Sent: Tuesday, March 10, 2015 12:50 PM
To: bosun-monitor/bosun
Cc: Kossack, Ken
Subject: Re: [bosun] scollector on Windows 2008 and 2012 appears to be
consuming High CPU processor time (#773)
Looks like we have spikes up to 16% every 15 seconds and larger spikes
every 15 minutes (again due to DSC). Overall average is 3.0-4.5%.
<EMAIL_ADDRESS>https://cloud.githubusercontent.com/assets/304401/6579922/e1ab3f78-c712-11e4-9ab1-dd6d4720ae2e.png>
I think Matt is right, you may just have a different work load that causes
the WMI queries to be more expensive. I'll look at adding per collector
timing metrics, which we can then use to help find and fix expensive
collectors.
—
Reply to this email directly or view it on GitHub<
https://github.com/bosun-monitor/bosun/issues/773#issuecomment-78096104>.
—
Reply to this email directly or view it on GitHub
https://github.com/bosun-monitor/bosun/issues/773#issuecomment-78268437.

@kylebrandt I like the idea of scheduling distributed over time. I wonder if @kkossack could be experiencing some single collector being more expensive on his servers for some reason though. I can't think of a way to diagnose that except by using filters and trial and error.

As of https://github.com/bosun-monitor/bosun/commit/6fccddefdea3254dad01e4e7c424c5615fe9047b you can now see the wall time duration of individual collectors using scollector.collector.duration. Here is an example from the same 4 core vm:

Most collectors take an average of less than 1 second, although we do see spikes up to 10-15 seconds that correlate with our DSC runs. If you find any collectors that are expensive you can try disabling them in the code or use the -f filter to only run the ones you care about.
DSC also uses WMI for processing, so it may be that multiple processes using WMI causes higher CPU. You might want to try running scollector on a VM by itself (no other tools) to see if you still see the high cpu load. It is based on a custom wmi/ole package, so there may be some performance improvements we can make, or as Kyle mentioned you can change the default collection frequency using -freq="15"

I'm seeing similar issues but with "unknown" status during the high cpu spikes. The spikes go from 1 minute up to 90 minutes on some machines. Have not found the cause yet.


Staking Change

This is a staking change as proposed by Sols. This new system would work off a 24 coin hour period and no longer rely on the network weight to generate staking rewards. This would be to help the smaller coin holders feel more rewarded and allow them to get their staking rewards faster. I feel like there are some functions that I may have overlooked that might need to be changed for this new staking system to work. If anyone has a better understanding of how the staking system is integrated please leave a commit so I can make sure this will be done correctly.  (Work in Progress)

i'm not sure i understand the point of this change,
but what would happen if the average small coin holder you wanted to advantage had 4k coins,
and i had 1,000,000
so i split those into 250 inputs of 4,000 coins
you will find that any changes you made will still benefit large coin holders who are willing to game the system for personal benefit.


OCICL should not hook into asdf:load-asd

I'm using asdf:load-asd to load plugins into a project. When calling load-asd ocicl hooks into the call (by supplying searcher function to asdf:*system-definition-search-functions*) and tries to download the named system. However, the system should not be downloaded but indeed loaded from specified path to load-asd.

If I understand it correctly then load-asd works so that ASDF/SYSTEM-REGISTRY:SEARCH-FOR-SYSTEM-DEFINITION should not find anything so that the previously registered ('undefined-system) with the path to the .asd (in asdf.lisp):
(let ((system (make-instance 'undefined-system
                                         :name primary-name :source-file pathname)))
              (register-system system)

and code that follows will load the system from the specified file.
But ocicl intercepts here and tries to load the system from it's sources instead which then prevents asdf to load the system from specified file.
Unfortunately I don't know the asdf sources well enough. Maybe my assumption of how load-asd works is wrong. But this is so, then I think ocicl should not intercept when load-asd was called.

This is interesting.  I don't suppose you could change your code to do
something like...
(let ((ocicl-runtime:*download* nil))
    (load-my-plugin plugin-name))

?
(or, I suppose, do that conditionally if ocicl-runtime is loaded)
Also, if ocicl-runtime can't load it, I would expect asdf to keep trying
different methods.  Is that not what's happening?
On Thu, Jul 25, 2024 at 2:43 AM Manfred Bergmann @.***>
wrote:

If I understand it correctly then load-asd works so that
ASDF/SYSTEM-REGISTRY:SEARCH-FOR-SYSTEM-DEFINITION should not find
anything so that the previously registered ('undefined-system) with the
path to the .asd (in asdf.lisp):
(let ((system (make-instance 'undefined-system
:name primary-name :source-file pathname)))
(register-system system)
and code that follows will load the system from the specified file.
But ocicl intercepts here and tries to load the system from it's sources
instead which then prevents asdf to load the system from specified file.
Unfortunately I don't know the asdf sources well enough. Maybe my
assumption of how load-asd works is wrong. But this is so, then I think
ocicl should not intercept when load-asd was called.
—
Reply to this email directly, view it on GitHub
https://github.com/ocicl/ocicl/issues/62#issuecomment-2249575610, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAV7CKUSGDYSFAGRUHRHCDZOCNCVAVCNFSM6AAAAABLNEGY2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZGU3TKNRRGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Setting *download* NIL works. I guess that could be a workaround for when :OCICL is found in *features*.
Generally though I think this changes behavior of load-asd which it should not.

Hmm, well. This workaround then only works for load-asd. A succeeding load-system then again fails trying to download the system which is defined in the asd.
I'm not sure what's going on under the hoods there in asdf, I'll probably have to dig a bit into it.
In Quicklisp this procedure works OK. Wondering how this does it.

Seems to work now. Not sure why or what has changed. Despite load-asd fails to download the system the rest of the process works now OK. Closing.


nesting a core-dropdown on a custom pol component prevents it's closing by similar instances

I created a custom dart/polymer component with this code:
...

             <core-dropdown id="optionsDropDown" class="colored" layered="true" autoCloseDisabled="false">
                 <core-selector single valueattr="label">
                    <core-item label="Display for 8 seconds"></core-item>
                 </core-selector>
             </core-dropdown>

    </template>
</polymer-element>

The Problem/Bug:
If I deploy multiple instances of this component on the same screen. Clicking on another instance of the same component does NOT close the previous core-dropdown menu, and sometimes clicking on a different component does NOT close this component's dropdown.
I was going to attempt to traverse all the shadow doms on my doc to close all instances, but this just sounded like mad science... Is there a way to close all core-dropdowns on a doc regardless if they're inside a shadow dom or not?

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Exporting classes for use from C

One of Zig's strengths is its interoperability with C, in both directions. The current functionality of this library allows users to consume GObject code written in C or C-compatible languages, but it doesn't immediately offer a good way to export GObject code written in Zig back to the broader ecosystem.
Perhaps some comptime magic could be used to export a type and its functions using C naming conventions? For bonus points, somehow generating the C macros associated with custom types in a header file would make interoperability even more seamless.

I'm thinking of a similar idea, not sure if they are same.
Currently zig-gobject is a binding, so running this project needs goject.
I'm thinking of a pure zig implemented "gobject protocol" / or "gobject interface", so the code base is purely zig, but it is compatible to gobject interface, from binary level, just like Microsoft's COM interface, which is language independent.
If we have a zig implemented gobject system, it will be easy to extend gobject app or eco-system in zig. It will also be benificial to zig as well: zig does not have a object system or programming patterns, following gobject might be a good idea.

Thanks for the input and suggestion! To expand on what this issue is aiming at, I'd like to be able to generate an interface and glue code to interact with GObject-based code written using this project (e.g. with gobject.ext.defineType). To compare this goal with Zig's own functionality, the current functionality of this project is basically "enhanced zig translate-c for GObject"; what this issue is proposing is to also offer an "enhanced -femit-h for GObject".
As for the idea of a pure Zig "GObject protocol" as you describe it, if I understand it correctly, I think the missing piece for doing that with this project is an implementation of GObject itself in Zig (the underlying runtime and its functions for type registration and management). That would certainly be an interesting idea, although probably further in the future, as it would likely be a lot of work to replicate all the functionality that GObject (the C implementation) currently provides.


Allow newly uploaded assets from an active record mount automatically be set to publicly available if bucket is set to public

For example include the ACL defintion in: https://github.com/metaware/carrierwave-google-storage/blob/master/lib/carrierwave/storage/gcloud_file.rb#L72
From ACL definition here: http://googlecloudplatform.github.io/google-cloud-ruby/#/docs/google-cloud-storage/v1.4.0/google/cloud/storage/bucket?method=create_file-instance

This works fine if you configure gcloud directly with public permissions, so it may not be necessary to implement.

@johnmcconnell let me know if this issue can be closed or you still need assistance with this?

I'd leave it open but mark it as low priority.

IMO, if you configure the library to make assets public it should update the ACL definitions in gcloud to allow a non public bucket to publicly share assets uploaded via this library.

@johnmcconnell I'll be working on this issue within the next week. Need this functionality for my own app.

I think it's about time to add proper ACL support to this library. I'll be tracking this development on this issue here.
Same feature mentioned in #25 as well. Closing #25 in favor of this issue.


Add dotnetRunMessages  to launchSettings.json

It's a dotnet run feature. It permits dotnet run to print messages as part of running the app. At this point, all it does is cause dotnet run to print the "Building..." prior to invoking dotnet build. Does this help?

See https://github.com/dotnet/aspnetcore/issues/32273#issuecomment-828625524
cc @RehanSaeed

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ceffa6a2-770c-1cd9-5145-dcd423f9dd22
Version Independent ID: 1cb5eb30-dd84-e5e1-5826-d74243fabf04
Content: Use multiple environments in ASP.NET Core
Content Source: aspnetcore/fundamentals/environments.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Add a link  to Development and launchSettings.json

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.

Thanks for reporting this. Any chance you could PR this? At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.


Simplify the HTTP Proxy test image a bit

Changes
Basically the same as https://github.com/knative/serving/pull/12399. We didn't have the DNS cache stuff in Serving, so maybe this is good enough?

/lgtm
Yeah, I wonder why DNS cache stuff was added :thinking:


support operations behind proxy

Signed-off-by: Michael Steiner<EMAIL_ADDRESS>

@bvavala Can you please check this CR since you are also living behind a proxy.


DOC-9008 Differences in Metrics Between Datadog & DB Console

Addresses DOC-9008
(1) Added Differences in Metrics between Third-Party Monitoring Integrations and DB Console page with images. (2) Updated Troubleshooting sidebar. (3) Updated troubleshooting overview page. (5) Added See Also links on Third-party Monitoring Integrations, Prometheus, and Export Metrics pages. (6) Updated 23.2 files.

@abarganier PTAL
This is the html formatted page: https://deploy-preview-17973--cockroachdb-docs.netlify.app/docs/v23.1/differences-in-metrics-between-third-party-monitoring-integrations-and-db-console.html

@kevin-v-ngo created follow-up JIRA issue: https://cockroachlabs.atlassian.net/browse/DOC-9195


HostSubnet resource is missing

cluster-scoped-resources/apiextensions.k8s.io/customresourcedefinitions/hostsubnets.network.openshift.io.yaml

Opened the issue openshift/must-gather#298 to have these resources collected

Closing, since https://github.com/openshift/must-gather/pull/342 has been merged.


Add tests for multi_host_url_schema() and definitions_schema()

Change Summary

Adds unit tests for json_schema.py functions multi_host_url_schema() and definitions_schema()

Related issue number
No related issue
Checklist

[x] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Thanks @vickumar1981 for the path.
I've added some comments that are valid for other tests as well(I didn't add same comments for other tests). let's wait for @samuelcolvin to see what he thinks

also, looks like there are conflicts, please update.

closing as no response.


[tool_requirements] Set Verilator and Ninja checks to as_needed

Previously, we were always checking the tool version of Verilator and Ninja in lint runs even when the tools were not used.
While this is typically not a problem (these are standard tools every developer has to install locally), it can be an issue for Dvsim runs that are dispatched to cloud runners which only load the tool image needed for a given lint run. E.g. Verilator lint runs were failing due to a missing Ninja installation.
This change sets Verilator and Ninja to "as_needed", and modifies the checks in the common checker core such that only the version of the requested tool is being checked.
I am not entirely sure, but it looks like this checker script is currently only invoked in lint runs.
Let me know if I missed an invocation elsewhere.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

Just a word of caution here: We do not have a clear and detailed understanding of which tool is a dependency on which build step, and have even less resources to support such use cases. Our guidance has always been: install all requirements listed in the documentation for a supported OpenTitan development environment. If you only install a subset of it, you're on your own (and likely need to fix strange breakages along the line).
So I'm fine with this PR if it unbreaks something for the nightly lint CI jobs, but it still remains an unsupported approach. The better way would be to just always run in an environment where all tools are available.

Yes I agree that ideally all tool requirements should always be installed.
This targets a special case for the nightly CI cronjobs where DVsim is executed on a system where all requirements are met - but the individual tool invocations are dispatched to a cloud runner that currently only mounts the tool needed for that run.
To Rupert's point: such a script could come in handy and could be run after following the installation guide here: https://docs.opentitan.org/doc/ug/install_instructions/.

When we run tool flows on external machines, it may not be always possible to satisfy all tool requirements on those machines. Requiring everything to be present causes tool flows that are already ready to go to be delayed as well.


Reduce slow sine/cosine usage in U3 gates

sine/cosine require hundreds of clock cycles, while multiplication and addition require only a few.

The accuracy difference seems to be on a small order e.g. 1e-15.  The hardware sin/cos functions are actually very good approximations, but its worth noting this as the only potential downside.

Its unclear if gcc is using a custom sin/cos in the math library actually.  Regardless, multiplication and addition is cheaper.
If it uses hardware, here is an example on Intel Skylake for the micro-ops fused/latency (from https://www.agner.org/optimize/instruction_tables.pdf):
FSIN 53-105 50-120
FCOS 53-105 50-130
FSINCOS 55-120 55-150
F2XM1 16-90 65-80
FYL2X 40-100 103
FYL2XP1 56 77
FPTAN 40-112 140-160
FPATAN 30-160 100-160
load and store into the x87 for execution via FLD and FST are 1 clock cycle each from registers or non-segmented memory.

I have failing build with:
/home/rakytap/Documents/software_testing/sequential-quantum-gate-decomposer/gates/U3.cpp: In member function ‘Matrix U3::calc_one_qubit_u3(double, double, double)’:
/home/rakytap/Documents/software_testing/sequential-quantum-gate-decomposer/gates/U3.cpp:555:25: error: ‘sin_Lambda’ was not declared in this scope
u3_1qbit[1].imag = -sin_Lambda*sin_theta;

Sorry its fixed.  glibc on x86-64 does apparently use some SSE2-based library to do sin/cos and such.  x87 also has accuracy issues if not in range abs(x)<=3PI/4 for FSIN and abs(x)<=3PI/8 for FCOS.  I dont know about glibc, if the parameter range is an issue we should fmod(, 2*M_PI) on updates.
But square root being 1 clock cycle is at least very intriguing.  Even on FPGA, I think its not hard to implement.  Which is giving me some inspiration for e.g. Hafnians.  Division is more complex than square root though!  Who would have thought...


Footer - social icons

Above the NYCulture, etc. logos, add social media icons and associated URLs for:
Soundcloud
Instagram
Facebook
Twitter

Social icons added


update github container location to use new mono repo in infra scripts

On main running the command cargo make --makefile ./infra/fendermint/Makefile.toml testnode leads to failure because we are pointing to the previous gh repo, not this current mono repo.
This PR addresses this concern that was raised in issue #546
when running the makefile from this PR we have the following success output:
:~/dev/consensus-shipyard/ipc$ cargo make --makefile ./infra/fendermint/Makefile.toml testnode
[cargo-make] INFO - cargo make 0.37.5
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Build File: ./infra/fendermint/Makefile.toml
[cargo-make] INFO - Task: testnode
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Execute Command: "docker" "stop" "ipc-node-cometbft"
ipc-node-cometbft
[cargo-make] INFO - Execute Command: "docker" "rm" "--force" "ipc-node-cometbft"
ipc-node-cometbft
[cargo-make] INFO - Execute Command: "docker" "stop" "ipc-node-fendermint"
ipc-node-fendermint
[cargo-make] INFO - Execute Command: "docker" "rm" "--force" "ipc-node-fendermint"
ipc-node-fendermint
[cargo-make] INFO - Execute Command: "docker" "stop" "ipc-node-ethapi"
ipc-node-ethapi
[cargo-make] INFO - Execute Command: "docker" "rm" "--force" "ipc-node-ethapi"
ipc-node-ethapi
[cargo-make] INFO - Execute Command: "docker" "network" "rm" "r0"
r0
[cargo-make] INFO - Running Task: fendermint-pull
latest: Pulling from consensus-shipyard/ipc
Digest: sha256:16db626542b6f780086dff8f197088a5a6d097f163cfd5ce914c686ccafcc5ba
Status: Image is up to date for ghcr.io/consensus-shipyard/ipc:latest
ghcr.io/consensus-shipyard/ipc:latest
[cargo-make] INFO - Running Task: node-clear
clearing all IPC data
[cargo-make] INFO - Running Task: node-mkdir
creating directories: /home/mikers/.ipc/r0/ipc-node /home/mikers/.ipc/r0/ipc-node/ipc-node/fendermint /home/mikers/.ipc/r0/ipc-node/ipc-node/cometbft
[cargo-make] INFO - Execute Command: "docker" "network" "create" "r0"
b48eeaca8bc2517b83925892a36ff376347befa187faeea9cfc3e016a80dadc9
[cargo-make] INFO - Execute Command: "docker" "pull" "cometbft/cometbft:v0.37.x"
v0.37.x: Pulling from cometbft/cometbft
Digest: sha256:e6220583125171b617e79e112c8fbff5c9c56d569bf53c5faea3b124cf1b432a
Status: Image is up to date for cometbft/cometbft:v0.37.x
docker.io/cometbft/cometbft:v0.37.x
[cargo-make] INFO - Running Task: cometbft-init
Running cometbft init to create (default) configuration for docker run.
I[2024-01-12|02:12:18.596] Generated private validator                  module=main keyFile=/cometbft/config/priv_validator_key.json stateFile=/cometbft/data/priv_validator_state.json
I[2024-01-12|02:12:18.596] Generated node key                           module=main path=/cometbft/config/node_key.json
I[2024-01-12|02:12:18.596] Generated genesis file                       module=main path=/cometbft/config/genesis.json
I[2024-01-12|02:12:18.607] Found private validator                      module=main keyFile=/cometbft/config/priv_validator_key.json stateFile=/cometbft/data/priv_validator_state.json
I[2024-01-12|02:12:18.607] Found node key                               module=main path=/cometbft/config/node_key.json
I[2024-01-12|02:12:18.607] Found genesis file                           module=main path=/cometbft/config/genesis.json
[cargo-make] INFO - Running Task: fendermint-deps
ipc:latest
ghcr.io/consensus-shipyard/ipc:latest
ipc image already exists
ghcr.io/consensus-shipyard/ipc          latest     14a87820af5a   13 hours ago   204MB
ipc                                     latest     14a87820af5a   13 hours ago   204MB
[cargo-make] INFO - Running Task: genesis-new
[cargo-make] INFO - Running Task: genesis-new-key
[cargo-make] INFO - Running Task: genesis-new-account-f1
[cargo-make] INFO - Running Task: genesis-new-account-eth
[cargo-make] INFO - Running Task: genesis-add-validator
[cargo-make] INFO - Running Task: genesis-new-gateway
[cargo-make] INFO - Running Task: genesis-write
[cargo-make] INFO - Running Task: testnode-export-keys
[cargo-make] INFO - Running Task: fendermint-start
ecf22b76f48c0502d746688a8be27802f8772eef030877d7b5c8c04e60aff094
[cargo-make] INFO - Running Task: cometbft-start
554d17bcd435109d4badcd573c34c1e95ddbb0566af5dd1e4fc32ad92f6434a9
[cargo-make] INFO - Running Task: cometbft-wait
[cargo-make] INFO - Running Task: ethapi-start
3594c5d5252c1be1349b0430763a4088839c6e93ba0cd446c80f92932fbe677e
[cargo-make] INFO - Running Task: testnode-report
############################
#                          #
# Testnode ready! 🚀       #
#                          #
############################

Eth API:
	http://<IP_ADDRESS>:8545

Accounts:
	x:<PHONE_NUMBER>0000000000000000000 coin units
	x:<PHONE_NUMBER>0000000000000000000 coin units

Private key (hex ready to import in MetaMask):
	x

Note: both accounts use the same private key @ /home/mikers/.ipc/r0/ipc-node/keys/validator_key.sk

Chain ID:
	x

Fendermint API:
	http://localhost:26658

CometBFT API:
	http://<IP_ADDRESS>:26657
[cargo-make] INFO - Build Done in 34.13 seconds.

This is fixed now, see https://github.com/consensus-shipyard/ipc/pull/549#issuecomment-1888809645

thank you @aakoshh !! will test these fixes today !


[Fix] Fix SGD implementation

Proposed changes
This fixes #440 by correctly implementing SGD's weight decay and momentum. This changes includes

The original implementation will make weight decay not take any effect if not setting a momentum & set momentum <= 0. We should first adjust gradients regarding to weight decay then do momentum instead.
With dampening > 0, originally we always update v to momentum * v + (1-dampening) * gradient, but when we are in the first round of iteration where v is zero, we should update v to gradient instead of (1-dampening) * gradient.

Reference: I implemented SGD according to the algorithm described in https://pytorch.org/docs/stable/generated/torch.optim.SGD.html#sgd
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have updated the necessary documentation (if needed)

@angeloskath
I tried to simplified it a little bit, but I still don't quite understand what do you mean by v = state.get("v", (self.dampening / self.momentum) * gradient), especially why we have self.dampening / self.momentum?
Also I'm totally fine if you want me to change it back to use (1 - self.dampening) * gradient for the first iteration. I'm just following the algorithm displayed in that PyTorch link and don't know if that's going to make a big difference.

Oh I just meant that if you initialize v with (self.dampening / self.momentum) * gradient then you don't need the check for first_iter. Simply put v should be gradient in the first iteration, right? So
v = state.get("v", (self.dampening / self.momentum) * gradient)
if self.dampening > 0:
    v = self.momentum * v + (1-self.dampening) * gradient

will result in
v = self.momentum * (self.dampening / self.momentum) * gradient + (1-self.dampening) * gradient
  = gradient

In addition to the above the algorithm you implemented now is kinda wrong as it doesn't apply momentum at all when dampening is 0.
I would say the only things that needed changing were

moving the if self.momentum <=0: after the weight decay
initializing v with (self.dampening / self.momentum) * gradient so that the first iteration is exact

Ah yes I see. I fixed it by moving momentum after weight decay and initializing v with default value (self.dampening / self.momentum) * gradient when dampening > 0.
When dampening <= 0 I think we need to initialize v with default value 0, so we can have v = gradient for the first iteration.
Curious why a negative dampening value is treated as zero (although I know such a negative value doesn't make any sense).

Ping


Hide voice search when in edit mode with user input

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3477

PR #3583   👈
PR #3574
PR #3489

PR #3516
PR #3491
PR #3490

PR #3528

PR #3541

PR #3564

PR #3567

PR #3550

This comment was auto-generated by Graphite.


CROMFS implement "." and ".." in the wrong

"." and ".." shouldn't set LINK flag because LINK flag is only used for the soft link, not the hard link.

BTW, it doesn't require to implement "." and ".." by adding the real entry into the file system, we can simulate them from readdir callback, like what Linux done:
https://github.com/torvalds/linux/search?q=!dir_emit_dot&unscoped_q=!dir_emit_dot

Improving a correcting features is welcome.  Removing them is totally unacceptable without broad concurrence from the team.

There are lots of other issues with CROMFS hard links that also need to be addressed.  The logic follows the hard links seems to be missing.  It can probably be cloned from ROMFS function romfs_followhardlinks();

The correct fix is not simply to change the flags, but instead to implement following the hardlinks.  Both "." and ".." are hardlinks in CROMFS.  For all hardlinks, the file system should follow the hardlink which may refer to a directory, a file, or another hardlink.  When this finally resolves to a a directory or a file, then the correct type should be reported which may or may not a directory.  In the case of the hardlinks "." and ".." will, of course be a directory, but it may not be a directory in the general hardlink case.
I verified this logic in ROMFS (and fixed a bug in ROMFS too).  I will port the hard-link following logic into CROMFS in the next few days.  See PR #1546 ... I will make CROMFS work just like this.  I am only working part time these days, so it will take me some time to accomplish this.
Other file systems that don't support hardlinks can only fake the "." and ".." entries.

"." and ".." shouldn't set LINK flag because LINK flag is only used for the soft link, not the hard link.

@xiaoxiang781216 The root pseudo-filesystem does support soft links and should return S_IFLNK.  Is this okay?

"." and ".." shouldn't set LINK flag because LINK flag is only used for the soft link, not the hard link.

@xiaoxiang781216 The root pseudo-filesystem does support soft links and should return S_IFLNK. Is this okay?

The soft link(the file data contain the path to the target) return S_IFLNK, the hard link(inode directly point to the target block) should resolve the link internally(don't set S_IFLNK). So, it's right behaviour that the  root pseudo-filesystem return S_IFLNK because the link implemented by root pseduo filesystem contain the target path.

Fixed by #1554


Ajax: the dropdown doesn't allow me to make a selection

Hi, this plugin is so awesome! I'm having a small issue though
Could you possibly let me know if im doing something wrong? code below
var $ajax = $(".js-example-data-ajax");
  function formatTenant (tenant) {
    if (tenant.loading) return tenant.text;

    var markup =  '<option value="http://' + tenant.host + '" class="select2-results__option" id="'+ tenant.host +'" target="_blank">'
                    + tenant.displayName + " - " + tenant.countryCode +
                  '</option>';

    return markup;
  }

  function formattenantSelection (tenant) {
    return tenant.displayName || tenant.text;
  }

  $ajax.select2({
      ajax: {
        url: "https://admin.unity.ac/api/search/tenants",
        dataType: 'json',
        delay: 250,
        data: function (params) {
          return {
            q: params.term, // search term
            page: params.page
          };
      },
      processResults: function (data, params) {
        // parse the results into the format expected by Select2
        // since we are using custom formatting functions we do not need to
        // alter the remote JSON data, except to indicate that infinite
        // scrolling can be used

        params.page = params.page || 1;
        console.log(data.results);
        return {
          results: data.results
        };
      },
      cache: true
    },
    escapeMarkup: function (markup) { return markup; },
    minimumInputLength: 1,
    templateResult: formatTenant,
    templateSelection: formattenantSelection
  });

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


STORM-3109: Fixed incorrect conversion from relative path to absolute path for STORM_LOCAL_DIR

See issue: https://issues.apache.org/jira/browse/STORM-3109

Could you explain a bit more why the conversion to absolute path is a problem? I'm having a hard time understanding why kill_workers would break if the STORM_LOCAL_DIR is given as an absolute path.

It would break if it’s given as a relative path. File.getCanonicalPath converts it to cwd/STORM_LOCAL_DIR

Ah right. Thanks, that makes sense. +1


OS: add Chrome OS crouton support

Description
Add support for distros installed via crouton on Chrome OS
Screenshot

LGTM :+1:

Thanks for the PR :D


shot_profile: player_variable doesn't make sense when applied to more than one shot

Currently we have a player_variable: setting in shot profiles that lets you override the name of the player var that will hold the current state of that profile. (The default player var is a combination of the shot name and profile name.)
The problem is that if you apply a profile with a custom var name to more than one shot, it breaks the shots since essentially you have multiple shots using the same var which means they can't have their own states. (Maybe that's a feature? Probably not.)
I vote that we just remove that setting. Reason is that to keep a single player var which is shared across shots, we'd have to store some kind of array or dict or something which is probably not desirable.
Alternately we could make it so that the player var setting was not valid if a profile is applied to a shot group (but valid if it's applied to a single shot), though that sort of seems like a band-aid to cover bad design.

removed


Fixes go GC crash on trap

Fixes https://github.com/wasmerio/wasmer-go/issues/291. Please, check https://github.com/wasmerio/wasmer-go/issues/291#issuecomment-1104443467 for the detailed description of the problem.
The crash can be reproduced in the master branch by adding runtime.GC() twice to the end of examples/example_early_exit_test.go file.

Upvoting this fix


[Feature] Print command duration

Gradle builds print time info:
 BUILD SUCCESSFUL
[22:54:52]: ▸ Total time: 4 mins 58.471 secs

It'd be nice to have a Total time that represents the amount of time from the start of flank until the end. Currently I have to wrap flank in a script to figure out how long we're waiting for flank to run the tests.

Isn't this the 'Combined execution time?'

Good idea. We'll add it.
On Jun 2, 2017 6:42 AM, "bootstraponline"<EMAIL_ADDRESS>wrote:

Gradle builds print time info:
BUILD SUCCESSFUL
[22:54:52]: ▸ Total time: 4 mins 58.471 secs
It'd be nice to have a Total time that represents the amount of time from
the start of flank until the end. Currently I have to wrap flank in a
script to figure out how long we're waiting for flank to run the tests.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TestArmada/flank/issues/27, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKGpQhtiWfEV2KitdV3lI2FH4a-Pu2iks5sABFAgaJpZM4NuTOL
.

Isn't this the 'Combined execution time?'

No. I'm not sure why 'Combined execution time' exists. Here's a real example:

Billable time:  111.0 min(s)

Estimated cost:  $1.85(virtual) $9.25(physical)

Combined test execution time: ~41 minutes

End time: 2017-06-02_09:30

This command takes ~13 minutes to run. The printed information doesn't tell me that. Billable time is valuable because that's directly related to costs. End time and combined test execution time... I'm not sure what value there is for those numbers. It's possible there's a use case I'm unaware of.

This has been added.


feat: enabled kubernetes auth for SC and SS

Solves- https://issues.redhat.com/browse/RHSTOR-4212

/assign @SanjalKatiyar
/assign @bipuladh
/assign @GowthamShanmugam

/approve
/lgtm

@debjyoti-pandit also add PRs to respective Jira story/task and move them to correct status...
and add link to that Jira here as well...

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

e2e tests are failing, @debjyoti-pandit PTAL

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/test odf-console-e2e-aws

@debjyoti-pandit check KMS tests locally, most probably u need to fix them...

ack

/test odf-console-e2e-aws

/test odf-console-e2e-aws

/lgtm


apiRoot - page not found

Hi! Cool project!
I just started the docker container but I'm not able to call any of the API endpoints.  I'm not sure what the value for apiRoot is supposed to be, and when I make a GET to http://localhost:8080/ I'm getting the following error.
Any idea what I've done wrong?
404
b'{"message":"Page Not Found","_links":{"self":{"href":"/","templated":false}}}'

Does http://localhost:8080/taxii2 work?

Nope, same thing.

@VVX7 can you try in the browser to go to localhost:8080/taxii2?  You should get a basic auth (see readme) and then you should get
{"title":"Some Default TAXII Server","description":"This is some Default TAXII Server","contact":"Some Contact goes here","default":"/default-root-1","api_roots":["/default-root-1","/root2","/root3"]}

The Taxii endpoint is not implement is normal for any endpoint that does not have a "Provider"
Example: https://github.com/StephenOTT/TAXII-Server/blob/master/src/main/kotlin/com/github/stephenott/stix/taxii/action/actions/DiscoveryProvider.kt vs https://github.com/StephenOTT/TAXII-Server/blob/master/src/main/kotlin/com/github/stephenott/stix/taxii/action/actions/GetCollectionProvider.kt

localhost:8080 should return a "client does not have access to this resource" (assuming you passed basic auth)
localhost:8080/anything-goes-here anything in the apiRoot position will return the same root as the provider is just statically coded to return {"title":"default-root-1","description":"this is the default root 1","versions":["application/taxii+json;version=2.1"],"max_content_length":104857600}
In practice the provider would be connected with a data repository like another system, database, rest, queue, etc.

In the browser I'm also getting a 501.

I'm using python requests with basic auth (default credentials in the README) and getting that message.
import requests
from requests.auth import HTTPBasicAuth

request = requests.get("http://localhost:8080/taxii2", auth=HTTPBasicAuth("sherlock", "password"))

print(request.content)

>>> b'{"title":"This TAXII Endpoint is not implemented.","http_status":"501"}'

I just pushed some code that was not committed.  Try downloading source again and try it.  It should not make a difference, but maybe did not see something.
You are getting a not implemented response.  So it is picking it up as a Taxii endpoint.  But it was not implemented, BUT it is implemented here: https://github.com/StephenOTT/TAXII-Server/blob/master/src/main/kotlin/com/github/stephenott/stix/taxii/action/actions/DiscoveryProvider.kt

The docker image pulls release 0.5.  I'll try building from source tomorrow.  Thanks for your help so far.

Sorry yes you are correct. That was error on my part.  I have updated the build release to 0.6 and the docker file:
https://github.com/StephenOTT/TAXII-Server/releases/tag/v0.6
https://github.com/StephenOTT/TAXII-Server/blob/v0.6/dockerfile

All good now.  Thanks!

Great!!


Create Monitor- Multiple where clauses in Visual Graph option

 Issue by taha2009
Monday Nov 30, 2020 at 11:32 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/307

Is your feature request related to a problem? Please describe.
Currently while creating a monitor, while using visual graph option I can give a where clause, for our purposes we want user to be able to give more filters (Where clauses)
Describe the solution you'd like
Please provide option for user to create multiple where clauses (Filter)
Describe alternatives you've considered
For now we are planning to add a textarea where user can provide lucene queries for more detailed searches.
Additional context
N/A

Hey @taha2009,
As of OpenSearch 1.1, we've refactored the Alerting frontend experience and this includes adding multiple where clauses (which is now labeled as "Data filter").
You can see an example of what it looks like in the demo included in this PR but I suggest trying it out for yourself.


How to set the project version from within the initializer

In the following issue, it is mentioned that the documentation for setting the project version is incorrect:
https://github.com/pybuilder/pybuilder/issues/261
However, it is not clear to me how we should go about setting the project version from within the initializer. I would like to do this because the version name will depend on the environment with which the pyb build is launched.
Thanks,
Dustin

Please see my response to the OP of #261.
https://github.com/pybuilder/pybuilder/issues/261#issuecomment-158417548

project.version is a read-only property that is initialized based on the configuration supplied via build.py

Namely, global variable version in build.py is used to specify the version or version template. This is different from project.version, which specifies the actual version as computed.
You don't set the project version from the initializer. You set it from the top-level of build.py.
See https://github.com/pybuilder/pybuilder/blob/master/build.py#L81