Implement an example of the "contract" between backend and frontend

We could implement a mock server that delivers a Mock data just to have the "spec by example".
What do you think? We could design here the request/response protocol and then somenone grabs this issue to implement the mock server..

@tiagostutz I think it is a great ideia. So frontend could test the integration with backend. =]

Correct!
And, as the design is to have a data server, the interface with the mock data server or with a actually data server will be the same. 😃

To start this conversation, we need to list the basic information that will be transit between the embed and api projects.
I will start with some properties and objects
Image Object

name
filePath
[]Tag

Tag Object

name
[]Images

Nice! Good start. I see that you started the spec in the Go side here, right. I was thinking about the REST API that this component will invoke to get the data it will use to store and expose to the frontend.
I was thinking about not stricting only to images, building a more generic API as this could be used for videos, for instance. Agree?
I'll write some documentation as spec here for you all to review and give your opinions.  (Documentation Drive Development 😆)
Using th API
To get the choice options to be used on your stop-analyzing-api service, you could use this API that has the following endpoints:
Get all options
Retrieve all items and can be filtered using query params on the URL by:

title: item title text (e.g.: Blush Tulle and Lace Wedding Dress)
tags: comma separated list of tags (e.g.: dress,long,vintage,tulle)
subtitle: item subtitle text (e.g.: blush tulle and lace wedding dress with vintage ballerina pink ribbon details and gathered detachable sleeves for a romantic fairytale bride)

GET /items
$ curl http://localhost:8008/items
$ curl http://localhost:8008/items?tags=blush,tulle
Return:
[{
    "title": "string",
    "subtitle": "string",
    "imageURL": "string",
    "tags": ["tag1", "tag2", "tag3"]
},
{
    "title": "string",
    "subtitle": "string",
    "imageURL": "string",
    "tags": ["tag1", "tag2", "tag3"]
}]

So I would change the Image object name for for ChoiceOption name. In REST API I'd keep the even more generic term "item" as this item will be a option only when the go exposes this data to stop analyzing...
What are your thougths?

maybe change the imageURL to contentURL be an option? And what more information the frontend will need?

Yep! You are right... correcting:
Wedding dress Stop Analyzing Database
Using th API
To get the choice options to be used on your stop-analyzing-api service, you could use this API that has the following endpoints:
Get all options
Retrieve all items and can be filtered using query params on the URL by:

title: item title text (e.g.: Blush Tulle and Lace Wedding Dress)
tags: comma separated list of tags (e.g.: dress,long,vintage,tulle)
subtitle: item subtitle text (e.g.: blush tulle and lace wedding dress with vintage ballerina pink ribbon details and gathered detachable sleeves for a romantic fairytale bride)

GET /items
Examples:
$ curl http://localhost:8008/items
$ curl http://localhost:8008/items?tags=blush,tulle

Return:
[{
    "title": "string",
    "subtitle": "string",
    "contentURL": "string",
    "tags": ["tag1", "tag2", "tag3"]
},
{
    "title": "string",
    "subtitle": "string",
    "contentURL": "string",
    "tags": ["tag1", "tag2", "tag3"]
}]

How about that? I think we have a good starting point here.

Cool! The json schema helped a lot. I'm getting a more well-defined picture of what we are trying to migrate and how to model it using structs.
This issue is absolutely related to te #6 one.
I think we may have two entry-points to call the same flow
File Migration:  Read file ---------------------------> parse struct -> process
URL Migration: Call http GET -> parse response -> ^
What do you guys think?
If so, I think I can create the http get call and parse a mocked response.
@eniovalo have you created any structs to hold the parsed file content?
Thanks!

Cool! The json schema helped a lot. I'm getting a more well-defined picture of what we are trying to migrate and how to model it using structs.
This issue is absolutely related to te #6 one.
I think we may have two entry-points to call the same flow
File Migration: Read file ---------------------------> parse struct -> process
URL Migration: Call http GET -> parse response -> ^
What do you guys think?
If so, I think I can create the http get call and parse a mocked response.
@eniovalo have you created any structs to hold the parsed file content?
Thanks!

Hi, @zamariola .
Sorry, I haven't created any structs yet. =(
I'm still studying the basics of Golang and analyzing how to solve issue #7 ...

Cool! The json schema helped a lot. I'm getting a more well-defined picture of what we are trying to migrate and how to model it using structs.
This issue is absolutely related to te #6 one.
I think we may have two entry-points to call the same flow
File Migration: Read file ---------------------------> parse struct -> process
URL Migration: Call http GET -> parse response -> ^
What do you guys think?
If so, I think I can create the http get call and parse a mocked response.
@eniovalo have you created any structs to hold the parsed file content?
Thanks!

Hi, @zamariola .
Sorry, I haven't created any structs yet. =(
I'm still studying the basics of Golang and analyzing how to solve issue #7 ...

Don't you worry! I'm going to create a draft and share it with you!

Great, @zamariola !

I think we may have two entry-points to call the same flow
File Migration: Read file ---------------------------> parse struct -> process
URL Migration: Call http GET -> parse response -> ^

Let's implement the way you suggested. When you commit the structs on your fork, please put a ref #8 on the commit message so this commit will appear here in the issue and we can take a look at the progress. 😃

Don't you worry! I'm going to create a draft and share it with you!

@zamariola , Thanks. 🙂

@tiagostutz @eniovalo
I don't know if we already have a final word about it:
are we going to store the options using the ChoiceBoardModel, so we're going to have title and subtitle there or are we going to use another model?
My next step on #6 is the actual item creation.
Thanks!!

Hi @zamariola! We don't have a final word yet, but let's make the decision right now:
Following what we are implementing in https://github.com/bancodobrasil/stop-analyzing-embed/issues/34, the endpoint of to retrieve the next choice will return:
{
  "completeness": 0.3,
  "choices": [
    {
      "title": "stringt1",
      "subtitle": "strings1",
      "contentURL": "stringc1",
      "tags": ["tag11", "tag12", "tag13"]
    },
    {
      "id": "5bdae89eeae8a99",
      "title": "stringt2",
      "subtitle": "strings2",
      "contentURL": "stringc2",
      "tags": ["tag21", "tag12", "tag13"]
    },
    {
      "id": "5bdae890aa0a0993e",
      "title": "stringt3",
      "subtitle": "strings3",
      "contentURL": "stringc3",
      "tags": ["tag21", "tag12", "tag31"]
    }
  ]
}

Those choices are Items (in our model). So that's the current proposal. Do you agree with it or have some suggestions to share? We are wide open to that...

Perfect! I'm going to add it.

Just to update things a little, we are moving from a "tag" approach to an "attribute" approach. So the JSON returned to the frontend will be:
{
  "completeness": 0.3,
  "choices": [
    {
      "id": "5bdae89eadfea93",
      "title": "string-ttitle-1",
      "subtitle": "string-sub-1",
      "contentURL": "string-content-1",
      "attributes": [{
            "attr-name-1":"attr-value-1",
            "attr-name-2":"attr-value-2"
       }]
    },
    {
      "id": "5bdae89eeae8a99",
      "title": "string-ttitle-2",
      "subtitle": "string-sub-2",
      "contentURL": "string-content-2",
      "attributes": [{
            "attr-name-31":"attr-value-31",
            "attr-name-23":"attr-value-23"
       }]
  }]
}


Docker build issues

Hi,
As suggested in README, I tried to build the Dockerfile which is in the repository.
docker build -t codamosa-runner -f docker/Dockerfile --platform linux/arm64 .
However, this does not work. I saw an error related to poetry build.

I started debugging this issue and I tried several ways including changing the file structure as the following.
codamosa
│   ...
│
└───src
│   │   pynguin
│   ...

Meanwhile, I change the project name to pynguin in pyproject.toml. And run docker build -t codamosa-runner -f docker/Dockerfile --platform linux/arm64 . again. Although the above error didn't show again, a new error relating to the pynguin source file showed up.

I also tried to build a docker from pynguin repo directly. It works well. I would like to ask for your help first before trying to migrate codamosa to the newest pynguin version.
Could you please help me with that?
Thank you,
Da

Apologies for the long response time.
Can you check whether updating the pyproject.toml file in the following manner (set name to pynguin, version to "0.19.0" resolves the issue? If so, I will merge the change into main.
https://github.com/microsoft/codamosa/pull/10/commits/0d78d06d06c635f37b21bbfb9876e6b8da5b6a3e

Yes, this update resolves the building issue. Thank you! :)


gnome-graphs: init at 1.7.2

Description of changes
Very good software, reminds me of the digital signal processing course I failed last semester (although I passed the make-up exam)
This is a bit like a fool's version of matlab, if you only need basic signal transformation.
Part of https://github.com/NixOS/nixpkgs/issues/195280 but not listed

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

$ result/bin/graphs
Traceback (most recent call last):
  File "/nix/store/5c3kjz0qr2wnw1zkzg7fx18v6winpya8-gnome-graphs-1.7.2/bin/.graphs-wrapped", line 45, in <module>
    locale.bindtextdomain("graphs", "/nix/store/5c3kjz0qr2wnw1zkzg7fx18v6winpya8-gnome-graphs-1.7.2/share/locale")
    ^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'locale' has no attribute 'bindtextdomain'

So no support for platforms other than Linux: https://www.gnu.org/software/gnulib/manual/html_node/bindtextdomain.html

Result of nixpkgs-review pr 295021 run on aarch64-linux 1

1 package built:

gnome-graphs


Improve page load time for new embed

We're seeing a slower page load time in GA (around 65% slower). We should look at at ways to concatenate the files and decrease the size of the page.

after doing some more investigation the new embed is loading faster


Amending 'activity-identifier' for Mastercard Foundation

Hi AidStream,
Mastercard Foundation's IATI Organisation Identifier is currently incorrect on the IATI Registry and in their AidStream account.
It should be: CA-CRA_ACR-817387277
Mastercard have over 400 activities currently on AidStream, that are not yet published.
Once the IATI Org ID is corrected in the AidStream settings, the 'reporting-org' identifier will be automatically updated in the activity files. But we usually have to go to each activity (individually and manually) to reflect this change in the 'activity-identifier'.
As there are a large number of activities, we are looking for a non-manual way of correcting the 'activity-identifier' for each of the activities.
Do you have any suggestions as to the best way to amend the 'activity identifiers' for each of Mastercard's activities?
(Please also see my email correspondence with Mastercard).
Many thanks for your help,
Jahnvi

Hi AidStream,
Has there been any progress with looking into this?
Mastercard Foundation are hoping to publish their activities soon, but their identifiers will need to be correct before they can do so.
Many thanks, Jahnvi

Closing this issue, as this was resolved by Mastercard Foundation manually editing the identifiers in their XML files before publishing.


Upgrade default authentication API version to v1beta1

In Kubernetes 1.24 (and associated client versions), the authentication
v1alpha1 API version no longer exists. This bumps the default to v1beta1

From my unfortunately deep experience with this transition recently, I can spot a potential problem with this change. To get the credentials, the local Kubernetes library code (or whatever is doing it) will call aws eks get-token. With this change, and with a default API version of v1beta1, it's then expected that that AWS CLI command returns credentials with version v1beta1. But, whether that happens or not depends on the version of the AWS CLI that is being used. If it's 2.6.3 or higher, you get v1beta1, otherwise, v1alpha1 is all you get.
So that, in turn, depends on whatever the thing running Terraform has installed locally. (For us, Atlantis.) If it's using an old AWS CLI, which is almost certain, then it will return an v1alpha1 credential no matter what, and then the Terraform activity will fail.
So, minor can of worms. This might be a long way of saying that the default for the new api_version parameter should still be v1alpha1, so that existing uses don't break simply when moving to a new provider version.
I thought there was a way to request either a v1alpha1 or v1beta1 credential - maybe that was for aws-iam-authenticator and not aws. That would be handy because then the provider / kubeconfig file could specifically ask for what it expects to get.

We chatted about this internally, and I've come around to being OK with the default changing to v1beta1. Existing users will only break when they update the provider version, and then we'll have docs that address what they need to do: either update the AWS CLI, or explicitly specify v1alpha1.


In Producer batching is not working with synchronous mode using send api

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
3.2.x
Minimal reproduce step
ProducerBuilder producerBuilderBatching = client.newProducer(Schema.STRING)
								.accessMode("Shared")
								.compressionType("NONE")
								.enableBatching(true)
								.blockIfQueueFull(true)
								.batchingMaxMessages(5)
								.batchingMaxBytes(13270)
								.batchingMaxPublishDelay(70000, TimeUnit.MILLISECONDS);

ProducerBase<String> producerStringBatching = (ProducerBase<String>) producerBuilderBatching.topic("batch-test-topic")
								.sendTimeout(20, TimeUnit.SECONDS).create();

MessageId msgId = producerStringBatching.newMessage().value("Check batching").send();

What did you expect to see?
number of messages should increase from 0 to 4 in a single batch(as max number of messages configured in a single batch was 5) and below are the pulsar SDK logs which should print in console

2024-04-02T14:54:08,963 DEBUG [pool-22-thread-2] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-800] add message to batch, num messages in batch so far 0
2024-04-02T14:54:08,964 DEBUG [pool-22-thread-15] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-800] add message to batch, num messages in batch so far 1
2024-04-02T14:54:08,964 DEBUG [pool-22-thread-9] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-800] add message to batch, num messages in batch so far 2
2024-04-02T14:54:08,965 DEBUG [pool-22-thread-6] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-800] add message to batch, num messages in batch so far 3
2024-04-02T14:54:08,965 DEBUG [pool-22-thread-20] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-800] add message to batch, num messages in batch so far 4

just like working in async mode
What did you see instead?
number of messages in a single batch is always 0 while using the synchronous mode
2024-04-02T14:43:26,850 DEBUG [pool-22-thread-15] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-792] add message to batch, num messages in batch so far 0
2024-04-02T14:43:26,852 DEBUG [pool-22-thread-8] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-792] add message to batch, num messages in batch so far 0
2024-04-02T14:43:26,854 DEBUG [pool-22-thread-7] org.apache.pulsar.client.impl.BatchMessageContainerImpl - [batch-test-topic] [standalone_onessl-4-792] add message to batch, num messages in batch so far 0

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

For the purpose of reduce the sync-api send message latency, client will flush messages to broker when you call the sync-api.
And sync-api will block your app's threads, if we don't flush messages to broker but waiting until the batch is full, it may block all the threads of your app.
/cc @gaoran10 @codelipenghui

Thanks for the good issue report @ragaur-tibco !

For the purpose of reduce the sync-api send message latency, client will flush messages to broker when you call the sync-api.

@dao-jun  Yes, this is reasonable, but the problem is that this doesn't seem to be documented any where.
I found the flushing logic here:
https://github.com/apache/pulsar/blob/ffff639a1b73a34bbb5115503d4c7783bb2a2770/pulsar-client/src/main/java/org/apache/pulsar/client/impl/TypedMessageBuilderImpl.java#L82-L86
I think @ragaur-tibco's issue report is great and the minimum resolution is to document the behavior.
It seems that there could be a use case where one would want to achieve batching while using the synchronous API. That's not currently supported. We have 2 options for resolving this:

Documenting the behavior and making it explicit that synchronous send will trigger flushing of the current batch message.
Adding support for controlling the triggering behavior so that batching would be possible also with the synchronous API.

@lhotari
I think support batch message for sync-api has potential risks, as I mentioned before, if we don't flush messages but waiting until the batch is full, it may block users' app threads for a long while.
Especially there are may producers send message in batch in a single app, it may block all the threads.
I prefer option 1, and I'll fix the doc later.


Profile Picture Cannot Be Displayed Correctly

Description
The profile picture cannot be displayed correctly in Simplified Chinese mode.
Reproduce
https://blog.thgirls.yt/zh-cn/关于少女们/

Tested Browsers

Arc
Safari

Can be closed, seems to be fixed at https://blog.thgirls.yt/zh-cn/about-us/


metabake

adding the metabake static gen project, featuring Pug.

Not sure why it is failing.

An issue is open
https://github.com/netlify/staticgen/issues/400

Thank you!


Release 3.5.0 not tagged (so not available)

We apologize for any inconvenience caused. The tag is affixed. Also added version 3.6.0 with a new version of the font.

Thankyou, yet is is not available in packagist. Also the information there states that "This package is not auto-updated." (https://packagist.org/packages/rmrevin/yii2-fontawesome). Maybe you could set up the described webhook so everytime you create/push a new tag, also packagist is updated https://packagist.org/about#how-to-update-packages (I can open a separate issue if you want)

Thanks, I installed a webhook, the versions in packagist have been updated. Previously, everything was updated, apparently the mechanism changed.


Remove decimal places from quantity

Remove decimal places from quantity for Yes/No and Multiple Choice markets
areas that quantity look outcome list, in filled orders, positions, open orders.

I found one spot with them still....
The My Quantity in the Order Book

fixed - closed


Missing CreationDate field on all mangopay object when toJSON() is used

It's seem the CreationDate field from the Wallets object is deleted here.
There is a reason ?

Same issue opened a few months ago : https://github.com/Mangopay/mangopay2-nodejs-sdk/issues/345
But still no answer at all from Mangopay...

Hello @CanoGit,
We are looking into it
Have a nice day,


fix: brightmail

Improve bright mail move grouping to post process

:tada: This PR is included in version 2.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[O# Parity] Run and debug tests in context

O# supports a couple of commands to run and debug tests using vstest console.

In the right click menu, run and debug tests in context
In codelens on test methods - links to run and debug tests

We need to add support for these commands in the preview version of the C# extension for full parity.

This one seems high priority -- without this feature I don't think I can run tests at all without the dev kit.

This one seems high priority -- without this feature I don't think I can run tests at all without the dev kit.

It should be one of the first features coming as soon as we finish getting the infrastructure setup in this new repo.  It's a GA blocker.

Remaining TODO items:

Allow custom .runsettings file - https://learn.microsoft.com/en-us/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file?view=vs-2022
Support unitTestDebuggingOptions - https://github.com/dotnet/vscode-csharp/blob/main/package.json#L922

csharp.unitTestDebuggingOptions support here - https://github.com/dotnet/vscode-csharp/pull/6110


Ci workflow

Summary
Adds CI/CD workflows for the SelfService application
TODO:
@freshteapot I need to figure out the image tags. I would really much like us to push images on releases that are tagged with a semantic version
Added

CI/CD workflow for SelfService Backend
CI/CD workflow for SelfService Web

Changed

Describe the outwards facing code change

Removed

Unused workflows

@woksin not against building a semantic version, but having "latest-dev" is incredibly useful for the dev environment. As it means we dont need to always deploy a new version.
I think anything that lands on "master" can be considered latest-dev.
I am a fan of pinning production to a version.
The new repos (as of yesterday) are
dolittle/selfservice-web
dolittle/selfservice-backend
I do acknowledge today we have to manually delete the pod so it gets the latest build.
This deletes both dev and prod
kubectl -n application-fe7736bb-57fc-4166-bb91-6954f4dd4eb7 delete $(kubectl get pod -l "microservice=SelfServiceWeb" -o name -n application-fe7736bb-57fc-4166-bb91-6954f4dd4eb7)

Lets figure out what we want and when to build and push images. We could for instance build and push images for each successful commit for example as well as the semantically versioned ones whenever a release is triggered

I have overflowed this PR into https://teams.microsoft.com/l/message/19:da9dce1fc7e34c02b6ffac271383ec67@thread.tacv2/1629877308184?tenantId=381088c1-de08-4d18-9e60-bbe2c94eccb5&groupId=6129cf36-ac84-4b62-9266-a4478a43f021&parentMessageId=1629877308184&teamName=Dolittle P%26D&channelName=General&createdTime=1629877308184 as CI / CD I believe is not solved today in Dolittle.


Cannot add decorator if modifier is set

Suite of ticket #89
On a class :
If I declare decorators factories and set the isExported to true it throw the error :
Error: Error replacing tree! Perhaps a syntax error was inserted (Current: ExportKeyword -- New: Decorator).

Code:
@HOInherit()
    at BaseError (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/errors/BaseError.js:5:9)
    at InvalidOperationError (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/errors/InvalidOperationError.js:6:9)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:57:19)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at handleChangingParent (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:78:13)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:63:17)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at replaceTree (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:53:9)
    at Object.replaceTreeCreatingSyntaxList (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:13:5)
    at Object.insertSyntaxList (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/insertion/insertSyntaxList.js:12:12)

On a property :
If I declare decorators factories and set the scope to private it throw the error :
Error: Error replacing tree! Perhaps a syntax error was inserted (Current: PrivateKeyword -- New: Decorator).

Code:
    @HOField()
    at BaseError (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/errors/BaseError.js:5:9)
    at InvalidOperationError (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/errors/InvalidOperationError.js:6:9)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:57:19)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at handleChangingParent (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:78:13)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:63:17)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at handleNode (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:65:17)
    at replaceTree (/Users/acidspike/Development/Sources/SCM/External/TSSimpleAst/dist/manipulation/tree/replaceTree.js:53:9)

You will find below an example, which can help you to reproduce and correct these errors :
const sourceFile = ast.addSourceFileFromStructure('./test.ts', {
    imports: [
        {
            namedImports: [
                {
                    name: 'HOModel'
                },
                {
                    name: 'HOInherit'
                },
                {
                    name: 'HOMapping'
                },
                {
                    name: 'HOConnectionInfo'
                },
                {
                    name: 'HOField'
                }
            ],
            moduleSpecifier: '@harmony/orm'
        }
    ],
    classes: [
        {
            name: 'TestModel',
            'extends': 'HOModel',
            isExported: true,
            decorators: [
                {
                    name: 'HOInherit',
                    arguments: []
                },
                {
                    name: 'HOMapping',
                    arguments: [
                        '\'test\''
                    ]
                },
                {
                    name: 'HOConnectionInfo',
                    arguments: [
                        '\n    {\n        connectionName: \'test\'\n    }\n'
                    ]
                }
            ],
            properties: [
                {
                    name: 'test',
                    type: 'string',
                    decorators: [
                        {
                            name: 'HOField',
                            arguments: []
                        }
                    ],
                    scope: 'private',
                    initializer: 'null'
                }
            ],
            methods: [
                {
                    name: 'getTest',
                    bodyText: 'return this.test;',
                    returnType: 'string'
                },
                {
                    name: 'setTest',
                    parameters: [
                        {
                            name: 'test',
                            type: 'string'
                        }
                    ],
                    bodyText: 'this.test = test;\nreturn this;',
                    returnType: 'this'
                }
            ]
        }
    ]
});

console.log(sourceFile.getFullText()); // Throw errors

This is fixed in 0.71.1. Thank you for reporting it! Sorry about not looking at this yesterday when you mentioned it... I had a very busy day.

This should actually also fix some unsurfaced issues. It's basically the inverse of the issue yesterday.

Hi,
Do not apologize, we all have a life outside of our projects, I confirm that the fix has worked, thank you.


Redirects don't change to GET method

Describe the bug
When following redirects is active the redirect will not change to using the GET method as it should, but will keep the original request method.
To Reproduce
Steps to reproduce the behavior:

Make a POST request to a URL that responds with a redirect (302).
Switch to timeline and see that the redirect did not switch to GET.

I managed to reproduce with a POST to http://httpbin.org/redirect-to?url=http%3A%2F%2Fexample.com%2F
(Same example as in previous issues linked below)
Expected behavior
The redirect should switch to using GET.
Screenshots

Desktop (please complete the following information):

OS: macOS 10.15.4
Installation Method: homebrew
App Version 7.1.1

Additional context
I have only tested this using a POST request, cannot confirm or rule out that it also happens with PUT, PATCH and other methods.
Previous issues with the same bug:
https://github.com/Kong/insomnia/issues/227
https://github.com/Kong/insomnia/issues/439

@johanrosenson Reading the RFC there is a User Agent required to specify that the method should be changed to GET.
In your Response Headers on the 301, I'm not seeing a user-agent specifying as such. That said, I don't know that the application supports said user-agent, I'm just pointing this out.
MDN:

The specification did not intend to allow method changes, but there are existing user agents that do change their method.

RFC7231:

Note: For historical reasons, a user agent MAY change the request method from POST to GET for the subsequent request.

Funny enough, they don't denote what the user-agent looks like.
From CURLOPT_POSTREDIR:

The non-RFC behaviour is ubiquitous in web browsers, so the library does the conversion by default to maintain consistency.

Seems like maybe we need some tests surrounding this. I've labeled it as accepted, since it appears to be recurring and some research seems to be required.
It might have to do something with the introduction of CUSTOMREQUEST.

From your link:

The specification did not intend to allow method changes, but there are existing user agents that do change their method. 308 was created to remove the ambiguity of the behavior when using non-GET methods.

My experience is that the real world usage of 301 in all browsers is to always change to a GET, I think Insomnia need to follow suit and do the same (no matter what the specification originally intended), otherwise Insomnia would differ from all the browsers, which does made some testing more difficult then it needs to be.
It also says that 308 was created for this very reason; to remove the confusion.
So the real world usage is clearly to change to a GET for 301 (including 302 and 303), 307 and 308 are clearer in their specification and do not change the method when redirecting.
This problem have already have been an issue twice before (and twice fixed?), but i think a third fix may be needed.
Thanks for accepting the issue.

I'm using Insomnia 2020.3.3 and I've observed this behavior:
If using multipart/form-data as the content type with a POST request it will follow the redirect and send POST again. If using application/json Insomnia will follow the redirect and change to a GET request. My version of curl:
curl 7.64.1 (x86_64-apple-darwin19.0) libcurl/7.64.1 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.39.2
Release-Date: 2019-03-27
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS GSS-API HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz MultiSSL NTLM NTLM_WB SPNEGO SSL UnixSockets

just doesn't follow the redirect at all with a POST request.

Also ran into this, see https://github.com/curl/curl/issues/5145 for more details.
TL:DR: the -X/--request flag overrides the switch to GET.  Removing the -X/--request flag and relying on --data to implicitly set it works as expected. I, for one, did not find this intuitive.
I don't know exactly how Insomnia interacts with curl/libcurl, but I think there's a good chance it explicitly sets the method, which curl then uses to override the switch to GET as detailed in the other thread.
Some speculation, but I hope it helps someone!

I'm using this version:
Release date: 23/09/2020
OS: Darwin x64 19.6.0
Electron: 9.1.1
Node: 12.14.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.69.1 OpenSSL/1.1.1g zlib/1.2.11 brotli/1.0.7 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.41.0```

The POST request (with JSON payload) actually switched to GET (and this is a problem for us), but PUT/PATCH/etc. is not.

I would like to have the option to enforce keeping the original request method as it can be a valid use case (api is behind Cloudflare which responds with 301).


postgres: max_connections=100 is not enough anymore

We faced with the problems for auto-update of materialized views due to the not enough connections.
Current load is about 98-103 connections and as result cron processes can't establish new ones and failed. As result staistic data disappear from widgets and not available in the morning.
we have to find a way to double this value by default.
Workaround for existing envs:
docker exec -ti postgres bash apt-get install nano nano /var/lib/postgresql/data/postgresql.conf #double max_connection 100->200 max_connections = 200 #save, exit and restart everything

fixed: https://github.com/zebrunner/reporting/commit/f207b22085633be43add965de3eb34329dccf5df
testing scenario:

clone reporting from develop branch recursively
git clone --recurse-submodule --branch "develop" https://github.com/zebrunner/reporting.git
temporary uncomment 5432 port in [docker-compose.yml(https://github.com/zebrunner/reporting/blob/f207b22085633be43add965de3eb34329dccf5df/docker-compose.yml#L18)
start just reporting with default settings
./zebrunner.sh start
using pgAdmin connect to your postgres. Defaul password is db-changeit (https://github.com/zebrunner/reporting/blob/f207b22085633be43add965de3eb34329dccf5df/configuration/reporting-service/variables.env.original#L17)
execute below query to ensure that default max_connections is 200 now:

FROM   pg_settings
WHERE  name = 'max_connections';

Verified.


Program slow to simplify

The following program is slow to simplify
x5 = x6 = fn x11 pair(prob, prob):
           (1 *
            1 *
            (match x11:
              (x27, x28):
               x29 = prob2real(x27)
               (match (not((x29 < 3)) && not((8 < x29))):
                 true:
                  (recip(real2prob((8 + negate(3)))) *
                   x30 = prob2real(x28)
                   (match (not((x30 < 1)) && not((4 < x30))):
                     true:
                      (recip(real2prob((4 + negate(1)))) *
                       x19_ = prob2real(x27)
                       integrate x32 from negate(prob2real(∞)) to prob2real(∞):
                        (exp((negate(((x32 + negate(nat2real(0))) ^ 2)) *
                              recip(prob2real((2 * (real2prob(x19_) ^ 2)))))) *
                         recip(real2prob(x19_)) *
                         recip(natroot((2 * pi), 2)) *
                         x21_ = prob2real(x28)
                         x22_ = real2prob(x21_)
                         ((exp((negate(((nat2real(17) + negate(x32)) ^ 2)) *
                                recip(prob2real((nat2prob(2) * (x22_ ^ 2)))))) *
                           recip(x22_)) *
                          recip(natroot((nat2prob(2) * pi), 2)) *
                          integrate x35 from negate(prob2real(∞)) to prob2real(∞):
                           (exp((negate(((x35 + negate(x32)) ^ 2)) *
                                 recip(prob2real((2 * (real2prob(x19_) ^ 2)))))) *
                            recip(real2prob(x19_)) *
                            recip(natroot((2 * pi), 2)) *
                            x24_ = real2prob(x21_)
                            ((exp((negate(((nat2real(13) + negate(x35)) ^ 2)) *
                                   recip(prob2real((nat2prob(2) * (x24_ ^ 2)))))) *
                              recip(x24_)) *
                             recip(natroot((nat2prob(2) * pi), 2)) *
                             1)))))
                     false: 0))
                 false: 0)
              _: 0))
     fn x5 pair(prob, prob):
      x0 <~ (match x5:
              (noiseT, noiseE):
               weight(1/2,
                      noiseT_ <~ uniform(nat2real(3), nat2real(8))
                      return (real2prob(noiseT_), noiseE)) <|>
               weight(1/2,
                      noiseE_ <~ uniform(nat2real(1), nat2real(4))
                      return (noiseT, real2prob(noiseE_))))
      return (x0, (x6(x0) * recip(x6(x5))))
fn x4 pair(prob, prob):
 x3 <~ x5(x4)
 (match x3:
   (x1, x2):
    x0 <~ weight(min(1, x2), return true) <|>
          weight(real2prob((prob2real(1) + negate(prob2real(min(1, x2))))),
                 return false)
    return (match x0:
             true: x1
             false: x4))

In particular it takes about 20 seconds
[zv@t420 hakaru (master)]% time simplify slow.hk > /dev/null
simplify slow.hk > /dev/null  19.53s user 5.78s system 66% cpu 37.789 total

@yuriy0 Can you take a look at this?  It isn't as important as it once was, but it would still be good to know where the time seems to be going.

The replacement of int by Int should probably happen in haskell/Language/Hakaru/Pretty/Maple.hs line 188, by analogy with lines 199 and 210.

Yes, we came to that same conclusion in a discussion that happened at about the same time you posted that comment.
What we can also do is to try to evaluate those integrals 'cleverly' (meaning: in context) rather than eagerly, which is what is currently done, and does not work.

Fixed by 5118851aa and 80d3966d.


Sort out mayavi build issue

It was attempted to build via https://github.com/NSLS-II/lightsource2-recipes/pull/604, but we eventually gave up in https://github.com/NSLS-II/lightsource2-recipes/pull/612.

No, it still fails with:
conda_build.exceptions.DependencyNeedsBuildingError: Unsatisfiable dependencies for platform linux-64: {"python[version='>=3.6,<3.7.0a0']", 'python=3.7'}

where is that coming from?

A more detailed traceback:
No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.11
WARNING:conda_build.metadata:No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.11
Adding in variants from internal_defaults
Adding in variants from argument_variants
INFO:conda_build.variants:Adding in variants from internal_defaults
INFO:conda_build.variants:Adding in variants from argument_variants
Collecting package metadata: ...working... done
Solving environment: ...working... done
Collecting package metadata: ...working... done
Solving environment: ...working... failed
Traceback (most recent call last):
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda_build/environ.py", line 753, in get_install_actions
    actions = install_actions(prefix, index, specs, force=True)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/common/io.py", line 85, in decorated
    return f(*args, **kwds)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/plan.py", line 473, in install_actions
    txn = solver.solve_for_transaction(prune=prune, ignore_pinned=not pinned)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/core/solve.py", line 107, in solve_for_transaction
    force_remove, force_reinstall)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/core/solve.py", line 145, in solve_for_diff
    force_remove)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/core/solve.py", line 242, in solve_final_state
    ssc = self._run_sat(ssc)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/common/io.py", line 85, in decorated
    return f(*args, **kwds)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/core/solve.py", line 500, in _run_sat
    ssc.solution_precs = ssc.r.solve(tuple(final_environment_specs))
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/common/io.py", line 85, in decorated
    return f(*args, **kwds)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/resolve.py", line 1047, in solve
    self.find_conflicts(specs)
  File "/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.7/site-packages/conda/resolve.py", line 316, in find_conflicts
    raise UnsatisfiableError(bad_deps)
conda.exceptions.UnsatisfiableError: The following specifications were found to be in conflict:
  - python=3.7
  - vtk=8.1 -> python[version='>=3.6,<3.7.0a0']
Use "conda search <package> --info" to see the dependencies for each package.

Interesting, the defaults py37 vtk build is 8.2.

It seems that the newest mayavi recipe from CF supports vtk 8.2

Cool! Will look into updating it later.

It seems to be resolved via #627.


Repeats appearing in output

I'm seeing repeated results in the output, which is confusing the ingestion process.
  Some are twice, but several are many times.  One (probe id 1000515) is duplicated 6 times.

when changing the logic to handle clouldflare and google, a bug was introduced. I will go ahead with introducing the manual setting of --id.servermethod, so I can get rid of this logic.


jsx-no-constructed-context-values: false positive

Consider this code:
export const AzureApplicationGatewayContext = createContext({});

const AzureApplicationGatewayProvider = ({ children, sitecoreContext }) => {
  const {
    azureApplicationGateway: {
      isEnabled = false,
      paths = [],
    } = {},
  } = sitecoreContext;

  const isInternalLink = useMemo(() => {
    if (!isEnabled) { return () => true; }

    return createInternalLinkMatcher(paths);
  }, [isEnabled, paths]);

  return (
    <AzureApplicationGatewayContext.Provider value={{ isInternalLink }}>
      {/*                                           ^^^^^^^^^^^^^^^^^^ */}
      {children}
    </AzureApplicationGatewayContext.Provider>
  );
};

Don't worry about Azure. We're coping with it 😅
isInternalLink here, is being marked with:

The object passed as the value prop to the Context provider (at line 50) changes every render. To fix this consider wrapping it in a useMemo hook.
eslint(react/jsx-no-constructed-context-values)

I am wrapping it in a useMemo hook, aren't I? 🤨 Then why is it saying I should do exactly the thing I've already done? 🤔
For now, I think I'll just disable this rule. I'm in the middle of fixing other linting errors (which are true positives 😉) so maybe there's a workaround, which I'll be happy to follow if it's reasonable.

This is a valid warning to a real problem. The variable isInternalLink is memo-ed, but { isInternalLink } is a new object in every render. See https://reactjs.org/docs/context.html#caveats .

Exactly right, this is indeed a true positive.

😑 I've always learned that React is okay with passing multiple values in ad-hoc objects. Why not in this case? Come on, React.
Anyway, that's not on you. Actually, thanks for taking the time to look into this 👍🏻
Maybe something can be done about the message that's emitted, to make it clear that it's about the entire object. When passing an object with a single value, you can see it's easy to create confusion between the value and the object wrapping it.

Since the difference between those two is a basic JS thing, what prose would you suggest that would have made that more clear?

This might do it for me.

The whole object, not just the one value, passed as the value prop to the Context provider (at line 50) changes every render. To fix this consider wrapping it in a useMemo hook. See https://reactjs.org/docs/context.html#caveats for further reading.

Actually, I think the reference to the documentation might be the most important bit. When you pointed to it, it took probably less than 5 seconds to realise my mistake 😀

A PR adding that link would be most welcome.


weave scope service for systemd

[Unit]
Description=Scope UI
Documentation=https://www.weave.works/docs/scope/latest/introducing/
Requires=weave.service
After=weave.service
[Service]
EnvironmentFile=-/etc/sysconfig/scope
ExecStart=/usr/bin/scope launch $HOST
ExecStop=/usr/bin/scope stop
[Install]
WantedBy=multi-user.target
Unfortunately this service file is not working. But when i pass through command line it works. But when i try in systemd file it gives an error in logs.
: Unregistered Authentication Agent for unix-process:7103:179995403 (system bus name :1.727
Jun 19 09:41:26 test1.com  kernel: overlayfs: upper fs needs to support d_type. This is an invalid configuration.
why its not pass through systemd file

CC @errordeveloper

?

@thatsk Where did you get that systemd file? Did you create it yourself?

Yes . Because its tedius to launch the command everytime . and we don't know where is kill so i have also to check the logs. systemd is best option for service ui Similar to weave net

Understood. Let's see if @errordeveloper can help you. However, we don't officially support launching through Systemd.

It would be great to let scope launch itself on boot (as a service)...

is there any update?

Meanwhile, I think there is a workaround. It looks like the scope script basically runs the docker container. Docker has a restart policy that can make it restart after certain events.
Can you change the scope script download from git.io/scope?

scope.txt
Added please check i have configured as per weave net policy that restart always

maybe @2opremio can make those changes by @thatsk into the source code for everyone? that would be awesome

You can already set the restart policy, or supply any other additional docker arguments, by starting scope with
WEAVESCOPE_DOCKER_ARGS="--restart=always" scope launch

except at the moment this breaks because $WEAVESCOPE_DOCKER_ARGS is also passed to the arg check run, which has a --rm and hence fails with
docker: Conflicting options: --restart and --rm.

I'm be tempted to remove the $WEAVESCOPE_DOCKER_ARGS from that call. @2opremio, what do you reckon?

I'm be tempted to remove the $WEAVESCOPE_DOCKER_ARGS from that call. @2opremio, what do you reckon?

Makes sense. We could check whether --restart is passed too.

I'm be tempted to remove the $WEAVESCOPE_DOCKER_ARGS from that call.

I did that in #2715, which was released in 1.6.0.

@rade @2opremio  is it done or we have to update. Also please update the doc because user is interested in this


learning_to_simulate=> failed to train

I tried to run the code on Ubuntu18 . Got this error:
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
File "/usr/lib/python2.7/runpy.py", line 119, in _get_module_details
code = loader.get_code(mod_name)
File "/usr/lib/python2.7/pkgutil.py", line 281, in get_code
self.code = compile(source, self.filename, 'exec')
File "/home/hv/learning_to_simulate/train.py", line 133
out_dict = {**context}
^
SyntaxError: invalid syntax
if possible guide me where I am doing wrong. I checked all the version requirements and other dependencies. Thanks

Hello, I'm running into this issue and was wondering how you got it to work (I assume you got it working as you have closed the issue).


Build error

There was the build error.
../../../.pub-cache/hosted/pub.dartlang.org/xterm-0.1.0/lib/frontend/input_listener.dart:100:7: Error: The non-abstract class 'TerminalTextInputClient' is missing implementations for these members:
 - TextInputClient.performPrivateCommand
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.

class TerminalTextInputClient extends TextInputClient {
      ^^^^^^^^^^^^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/services/text_input.dart:813:8: Context: 'TextInputClient.performPrivateCommand' is defined here.
  void performPrivateCommand(String action, Map<String, dynamic> data);
       ^^^^^^^^^^^^^^^^^^^^^

Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
** BUILD FAILED **

Thank you.

Flutter 1.20.0+ is required to build 0.1.0, and flutter 1.22.0+ to build master branch.


Want to add user's current location feature

Description
In MainActivity.java, Using GPS provider and Network provider we can get the user's current location. When the user opens the app we can display weather details for that location. Anyway, the user can also search for other locations like currently they are doing.
Steps to reproduce
If the user has given permission for the location, we can get the user's location by different providers like GPS provider, Network provider. We can use the background service to get the user's current location geographic coordinates(Latitude and Longitude). Then using the openweathermap API  we can get weather details for that coordinates.
E.g. api.openweathermap.org/data/2.5/weather?lat={lat}&lon={lon}&appid={API key}
Expected behaviour
We can utilize location in different ways like when the user opens an app, the app will display details for the user's current location.
Actual behaviour
The app is displaying weather details of the last searched location.
Would you like to work on the issue?
I would like to work on this If you want.

Good idea and perfect description. Of course, I would be greatful if you implemented this issue!


Stricter typing + better split of modules + bugfix

This PR introduces stricter typing and a bugfix (wrong enum variant values).

Good catch on the enum variant. One nit about a comment but then feel free to rebase and merge.

I rebased everything @IsaacWoods

but I think we should preserve the bit about this memory needing to be preserved when hibernating.

I'm sorry, I don't know what you mean. I didn't removed anything, only made an addition?


ARROW-7675: [R][CI] Move Windows CI from Appveyor to GHA

This also includes https://issues.apache.org/jira/browse/ARROW-7202

Oh this will be glorious. So tired of waiting on Appveyor


Error exmples for DCGAN

I' tried to run python train_dcgan.py --gpu 0 and recieved this error.
Traceback (most recent call last):
  File "train_dcgan.py", line 115, in <module>
    main()
  File "train_dcgan.py", line 84, in main
    device=args.gpu)
  File "/home/s1311320/projects/practice/chainer-dev/examples/dcgan/updater.py", line 14, in __init__
    super(DCGANUpdater, self).__init__(*args, **kwargs)
  File "/home/s1311320/.pyenv/versions/chainer-dev/lib/python3.5/site-packages/chainer/training/updater.py", line 131, in __init__
    optimizer['main'].target.to_gpu(device)
KeyError: 'main'

I fixed update.py
from
if device is not None and device >= 0:
    optimizer['main'].target.to_gpu(device)

to
for opt in self._optimizers.values():
    opt.target.to_gpu(device)

This issue was fixed at #2121


Compatibility with Django 1.8 final

Do you want a test for this?

Ping @ojii

\o/ thanks @ojii !

released as 0.8.2

Thanks for your support @ojii


Always close key handle if key is persistent

Currently handles for persistent keys are kept open after generating and importing, which causes mbedtls to run out of key slots.
If a key is persistent, its handle should be closed after each generate and import operation.
Only set the handle field if the key is volatile.

Done in linked PR


Remove the concept of extended fields from our standard and experimental channels

Describe the issue:
We have 2 channels:

standard channel signifies the fields are stable and all implementations must implement all fields in this channel -> also called core API fields
experimental channel signifies standard channel plus extra new fields in addition to the core fields that are not yet stable and are waiting for implementations to implement before they can become part of the core. However these fields were called extended fields and had another notion of "optional to implement" for implementations

We have spoken in past sig-network-policy-api meetings and at kubecon that community is OK to get rid of these extended/core concept totally and just have the two channels -> All implementations that are implementing experimental must implement all the fields there and same goes for core.

We should also consider whether the "channel" terminology makes sense.

(maybe after the next release)


New release v0.1.5

@JuliaRegistrator register

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

Release notes:

## Breaking changes

- blah

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


Customize data source for Grafana in Rancher Monitoring

What kind of request is this (question/bug/enhancement/feature request): feature request

We have been using Grafana + Prometheus on prem with the cluster provisioned using RKE. It works amazing for RBAC to rancher project. Is there any way to use Azure monitor as data source instead of Prometheus?
I can install Grafana and use custom configuration, but I have to manage access control separately. It would be great if custom installed Grafana can be managed within Rancher

Steps to reproduce (least amount of steps as possible):

Enable Cluster-level Monitoring, (See: https://rancher.com/docs/rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/#enabling-cluster-monitoring).

Result:
It should now say:

Cluster level monitoring is enabled.

Under "Show advanced options", there should be a way to replace Prometheus with Azure Monitor, per the Grafana docs, (See: https://grafana.com/docs/grafana/latest/datasources/azuremonitor).
Other details that may be helpful:

We are looking for a solution to control Grafana access based on the Rancher project. Rancher does this job perfectly as long as the member has access to the Rancher project.

See: https://github.com/rancher/system-charts/tree/release-v2.3/charts/rancher-monitoring/v0.1.1
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.3
Installation option (single install/HA): single

gz#13196

See also: https://github.com/rancher/rancher/issues/28893


Swift 3 ?

Is there any plan to update this awesome library to Swift 3?

Looks like there is a pull request pending. I hope it's merged soon, my designer friend wants to use it for one of our app but the app is using Swift 3.x, and probably soon Swift 4 will be released :D
Kitasuke san お願い？

Any updates on this? Is there a way to simply use that fixed branch/pull request via Cocoa Pods?


Exclude zero hash from multiproofs

Zero hashes should probably not be included in multiproofs. I can't think of an optimal way to store this data in the multiproof off the top of my head.

Closing since I extracted the multiproof to a separate repository.


Get fees from api before create the transaction

Hi. I read the blog and saw that we will change the fees soon and I noticed that the account.service uses fixed values to validate and create a transaction.
In api we have this route: https://ark.brianfaust.me/#/Block/blocks_getFees.
I get the fees from it but I made a default variable in case the user is not connected.
Please let me know if you need any changes.

Finally! I had already commented about it in other PR's.. #272
+5 👍🏻


Documentation

I would love to use this plugin with Nextjs but this part of the documentation isn't very clear. Would you be able to elaborate?
📁 Copy required files
Inside strapi-files we have a list of folders with the Strapi version, enter to the version that correspond with your installation, and you will see this files
It seems like files from the Admin panel need to be ejected but it's not clear.
Thank you in advance for any help you can provide!

Hi! You need to go to this folder:

Enter to the version that correspond with the actual strapi version:

And copy the required files, you can see this folder there:

That files you need to copy it in the root of your strapi project

Maybe I'm missing something, but those files don't seem to be present after installing via NPM or Yarn.
This is what I'm getting after installing via NPM.

Hi! You need yo manually copy the files from GitHub (extensions) and put it in the root of your project, not inside node_modules

OHHHHHHHHH. Thank you so much! I was able to get this to work. I have a feeling that this will be one of the most popular Strapi plugins. Great work.

Maybe it should be said in the readme, like : "in our repository, not on your local project"


KAFKA-12577; Remove deprecated quota.producer.default and quota.consumer.default configurations

quota.producer.default and quota.consumer.default were deprecated in AK <IP_ADDRESS>. I propose to remove them in AK 3.0.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@rajinisivaram @ijuma I propose to remove these two configurations that were deprecated in 0.11. There is a clear alternative which consists in using the default dynamic quotas. What do you think?

Seems reasonable to me. Any downside for the alternative?

We decided not to support static quotas for request quotas and left these in for compatibility earlier. It seems ok to remove the static quotas for 3.0 and rely on just the dynamic quotas which can be set at the whole cluster level.

@rajinisivaram Thanks for your review!

I have rebased the PR to fix the conflict in the upgrade notes.

Failed tests are unrelated to this PR. Same tests fail in trunk. I will go ahead and merge this PR.


Csv 180 bump

PR for your PR https://github.com/openshift-knative/serverless-operator/pull/296
You need to rebase that PR branch first

ok - will do


Add Validate, Normalize and Fold/Unfold Hydrogen feature

These options will go into the Structure >> QuickFix dialog options along with:
#64 (Aromatize) and #63 (Cleanup)


Can I embed this plugin into the webpage?

The example you gave is embedded in the desktop application. If I want to embed this plugin into the webpage, can I do it? What should I do? Is there a relevant example?

It's not possible, you won't have enough permissions to do that.


[PE-D][Tester D] Add schedule start time can be before end time

The add_schedule command allows me to set a start time that is before the end time (which doesn't make logical sense).

Labels: type.FunctionalityBug severity.Medium
original: officialchengyud/ped#9

Not allowed to fix in v1.4.


Unhandled promise rejection Error: Error invoking FetchConfig. Check the inner error for details.

spinning up the system throws;
"Unhandled promise rejection Error: Error invoking FetchConfig. Check the inner error for details."
same thing happens when using paul van bale's aurelia-auth with the suggested fix being to replace;
import {FetchConfig} from 'aurelia-auth';
with
import FetchConfig from 'aurelia-auth/app.fetch-httpClient.config';
in client/src/app.js
however replacing
import {FetchConfig} from 'spoonx/aurelia-auth';
with
import FetchConfig from 'spoonx/aurelia-auth/app.fetch-httpClient.config';
doesn't fix the issue.

Full stack trace;
Unhandled promise rejection Error: Error invoking FetchConfig. Check the inner error for details.
inner error: Error: key/value cannot be null or undefined. Are you trying to inject/register something that doesn't exist with DI?
at Container.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:473:15)
at Object.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:359:57)
at InvocationHandler.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:309:168)
at Container.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:557:25)
at StrategyResolver.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:145:37)
at Container.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:488:41)
at r.configure (http://localhost:4000/jspm_packages/github/spoonx/aurelia-auth@master/index.js:13:41)
at http://localhost:4000/jspm_packages/npm/aurelia-framework@1.0.0-beta.1.0.7/aurelia-framework.js:34:34
at h (http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1773:66)
at http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1778:19
at Container.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:473:15)
at Object.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:359:57)
at InvocationHandler.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:309:168)
at Container.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:557:25)
at StrategyResolver.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:145:37)
at Container.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:488:41)
at r.configure (http://localhost:4000/jspm_packages/github/spoonx/aurelia-auth@master/index.js:13:41)
at http://localhost:4000/jspm_packages/npm/aurelia-framework@1.0.0-beta.1.0.7/aurelia-framework.js:34:34
at h (http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1773:66)
at http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1778:19
at new AggregateError (http://localhost:4000/jspm_packages/npm/aurelia-pal@1.0.0-beta.1.0.1/aurelia-pal.js:20:13)
at Container.invoke (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:559:15)
at StrategyResolver.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:145:37)
at Container.get (http://localhost:4000/jspm_packages/npm/aurelia-dependency-injection@1.0.0-beta.1/aurelia-dependency-injection.js:488:41)
at r.configure (http://localhost:4000/jspm_packages/github/spoonx/aurelia-auth@master/index.js:13:41)
at http://localhost:4000/jspm_packages/npm/aurelia-framework@1.0.0-beta.1.0.7/aurelia-framework.js:34:34
at h (http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1773:66)
at http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1778:19
at MutationObserver.e (http://localhost:4000/jspm_packages/npm/core-js@1.2.6/client/shim.min.js:1958:55)

same issue; https://github.com/paulvanbladel/aurelia-auth-sample/issues/10

Please ignore this was an issue with an older release


[ERROR] TypeError: Cannot set properties of undefined (setting 'minItems')

npm run build

><EMAIL_ADDRESS>build
> docusaurus build

[INFO] [en] Creating an optimized production build...
[ReDoc Compatibility mode]: Converting OpenAPI 2.0 to OpenAPI 3.0
TypeError: Cannot set properties of undefined (setting 'minItems')
    at C (/Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:33595)
    at T (/Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:43282)
    at /Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:52463
    at /Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:54330
[ERROR] Unable to build website for locale en.
[ERROR] TypeError: Cannot set properties of undefined (setting 'minItems')
    at C (/Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:33595)
    at T (/Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:43282)
    at /Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:52463
    at /Users/blacktop/Developer/Github/blacktop/ipsw/www/node_modules/redoc/bundles/redoc.lib.js:2:54330
[INFO] Docusaurus version: 2.4.1
Node version: v20.5.1

I tried reverting the commit and it still fails and I tried forcing version 1.6.1 and it still fails :(

Can you share you repo where it's failing? If I can reproduce it then I might be able to fix it

@rohit-gohri https://github.com/blacktop/ipsw/tree/master/www

here is the commit that seemed to break it - https://github.com/blacktop/ipsw/commit/59eac04013d5f490e41fa58f28cb1ce263faf8e8
However, I tried to revert back to the older version but it still errors in the same way :(

i feel like since the action doesn't run when the swagger.json is updated it actually broke because of some change in the swagger file b/w the last successful build - this commit and the first failure
You can check the diff b/w the 2 commits and see that swagger has changed in b/w - https://github.com/blacktop/ipsw/compare/d8641ab9d653f16b365ccf3b550d9b4c6e8a5c81...59eac04013d5f490e41fa58f28cb1ce263faf8e8
So maybe the issue is not the package upgrade

many thanks! I have swagger.json in my root api/ folder AND in the www/static folder.  I had removed the minItems from one but not both.  This has fixed the issue.  This is something introduced by the latest version of https://github.com/go-swagger/go-swagger it seems :(

We use the redocly cli to parse the file (https://github.com/Redocly/redocly-cli) if you want to debug exactly what property is causing the crash

thanks @rohit-gohri !


RoleManager implementation

Not available?

nm, added https://github.com/et1975/AspNet.Identity.Cassandra/commit/8f6f18c7532535cd9286d06e217e19f1d12828b4


找不到“vite-plugin-vue-layouts/client”的类型定义文件

vscode
版本: 1.78.0 (user setup)
提交: 252e5463d60e63238250799aef7375787f68b4ee
日期: 2023-05-03T20:09:00.748Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
沙盒化: No

vite.config.ts

tsconfig.json

main.ts

It's ok when I use "vite-plugin-vue-layouts": "^0.3.0"，but failed on "vite-plugin-vue-layouts": "^0.8.0"

@yb3616
设置 client-types 👉 vite-plugin-vue-layouts#client-types
set [client-types] 👉 vite-plugin-vue-layouts#client-types

I've already do it

I have some problems and I have already add client-types in tsconfig.json and vite-env.d.ts.

Has this problem been solved?

@Ardanas @FrankLin23 @yb3616 It's still in progress, you can temporarily use 👉 vite-plugin-vue-meta-layouts。
Potentially related issue 👉 #112

@markthree @Ardanas @FrankLin23 @yb3616
This problem is related to the --resolvePackageJsonExports flag in TypeScript 5.0
As written there, forces TypeScript to consult the exports field of package.json files if it ever reads from a package in node_modules.
To fix this, we need to add the following settings to the package.json file, as is done in vite-plugin-pages
"exports": {
  "./client": {
    "types": "./client.d.ts"
  },
}

Temporary solutions:

Disable the --resolvePackageJsonExports flag
Change the path in env.d.ts  from

/// <reference types="vite-plugin-vue-layouts/client" />
to
/// <reference types="vite-plugin-vue-layouts/client.d.ts" />

@kkudr Thanks for the solution and find out the reason.
Another temporary solution is replacing "vite-plugin-vue-layouts/client.d.ts" to "vite-plugin-vue-layouts/client" in tsconfig.json.
{
  "compilerOptions": {
-    "types": ["vite-plugin-vue-layouts/client"]
+    "types": ["vite-plugin-vue-layouts/client.d.ts"]
  }
}

Guys: https://github.com/JohnCampionJr/vite-plugin-vue-layouts/issues/114#issuecomment-1665922024

A temporary solution, its work for me:
// tsconfig.json
{
  "compilerOptions": {
-    "moduleResolution": "Bundler"
+    "moduleResolution": "Node"
  }
}

Will be fixed in next version.


Explore apps

There are currently only 6 apps listed on the homepage, with a button to "explore more apps". This should take you to a page where you can browse all apps by:

Popularity (installs)
Topic (TODO: curate initial list of topics)
???

Fixed by #33, and we'll do more explore stuff when needed later (cc #18)


No way to get rid of the default datahub/datahub username + password combo

Describe the bug
I followed the instruction below to configure a different password for the default datahub username when deploying to GKE in the cloud. Afterwards, the datahub/<new password> combo worked, but the old datahub/datahub combo also still worked.
https://datahubproject.io/docs/authentication/guides/add-users#helm
To Reproduce
Steps to reproduce the behavior:

Follow the instruction below to store a custom users.prop file in the kubenetes secret store. Also create a custom values.yaml file according to the instruction.
https://datahubproject.io/docs/authentication/guides/add-users#helm
Follow the instruction below to deploy to Kubenetes. When deploying the datahub chart, also pass in the custom values.yaml file created in step 1.
https://datahubproject.io/docs/deploy/kubernetes/
Access the datahub-datahub-frontend using its public ip address + port 9002
You can login using both datahub/datahub and datahub/<new password> combos.

Expected behavior
Shouldn't be able to login using datahub/datahub any more.
Additional context
I tested this in GKE.

I mounted user.props in /datahub-frontend/conf/user.props instead and the default password is overwritten.

@jinlintt Please try what @xiphl has said which will replace the user. That guide you are linking to was always for "Adding Users" not "Replacing Users".


Unable to resolve module "crypto"

🐛 Bug Report
i have this issue in my project, if i want to install crypto i find another issue that is crypto repo is empty.

package.json
{
  "name": "MyProjectName",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@react-native-community/async-storage": "^1.11.0",
    "@react-native-community/blur": "^3.6.0",
    "@react-native-community/masked-view": "^0.1.10",
    "@react-native-community/slider": "^3.0.3",
    "@react-native-community/toolbar-android": "^0.1.0-rc.2",
    "@react-navigation/bottom-tabs": "^5.7.2",
    "@react-navigation/native": "^5.7.1",
    "@react-navigation/stack": "^5.7.1",
    "axios": "^0.19.2",
    "babel-plugin-dotenv": "^0.1.1",
    "babel-plugin-dotenv-import": "^2.1.0",
    "crypto-js": "^4.0.0",
    "lodash": "^4.17.19",
    "moment": "^2.27.0",
    "native-base": "^2.13.13",
    "react": "^16.13.1",
    "react-native": "^0.63.2",
    "react-native-dotenv": "^2.2.0",
    "react-native-gesture-handler": "^1.7.0",
    "react-native-modal": "^11.5.6",
    "react-native-reanimated": "^1.10.1",
    "react-native-redash": "^14.2.3",
    "react-native-restart": "^0.0.17",
    "react-native-safe-area-context": "^3.1.1",
    "react-native-screens": "^2.9.0",
    "react-native-slider": "^0.11.0",
    "react-native-svg": "^12.1.0",
    "react-native-swift": "^1.2.3",
    "react-native-tailwindcss": "^1.1.9",
    "react-native-track-player": "^1.2.3",
    "react-native-vector-icons": "^7.0.0",
    "react-redux": "^7.2.0",
    "redux": "^4.0.5",
    "redux-thunk": "^2.3.0"
  },
  "devDependencies": {
    "@babel/core": "^7.10.5",
    "@babel/runtime": "^7.10.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "babel-jest": "24.9.0",
    "eslint": "^7.5.0",
    "jest": "^26.1.0",
    "metro-react-native-babel-preset": "^0.61.0",
    "react-test-renderer": "16.13.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

any suggestion

The source of this issue that *@€@``visual studio code import automatically process from 'bable-jest'
import {process} from 'babel-jest';


Failed to start application after migration to spring boot 2.5.3-Error creating bean with name 'httpTracing' defined in class path resource [org/springframework/cloud/sleuth/autoconfig/brave/instrument/web/BraveHttpConfiguration.class]

While upgrading to spring boot 2.5.3 from 2.3.9 ,the application failed to start .
Spring boot version -2.5.3
Spring cloud -2020.0.3
It has spring-cloud-starter-sleuth & spring-colud-sleuth-zipkin
Stack Trace  ::
[Tomcat].[localhost].[/] Exception starting filter [lazyTracingFilter]
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'braveHttpServerHandler' defined in class path resource [org/springframework/cloud/sleuth/autoconfig/brave/instrument/web/BraveHttpBridgeConfiguration.class]: Unsatisfied dependency expressed through method 'braveHttpServerHandler' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'httpTracing' defined in class path resource [org/springframework/cloud/sleuth/autoconfig/brave/instrument/web/BraveHttpConfiguration.class]: Unsatisfied dependency expressed through method 'httpTracing' parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sleuthSkipPatternProvider' defined in class path resource [org/springframework/cloud/sleuth/autoconfig/instrument/web/SkipPatternConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.cloud.sleuth.instrument.web.SkipPatternProvider]: Factory method 'sleuthSkipPatternProvider' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Unsatisfied dependency expressed through method 'healthEndpoint' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthContributorRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthContributorRegistry]: Factory method 'healthContributorRegistry' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'couchbaseHealthContributor' defined in class path resource [org/springframework/boot/actuate/autoconfigure/couchbase/CouchbaseReactiveHealthContributorAutoConfiguration.class]: Unsatisfied dependency expressed through method 'couchbaseHealthContributor' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'couchbaseConfiguration': Unsatisfied dependency expressed through field 'couchbaseClientFactory'; org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:887)
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:791)
... 200 common frames omitted
Can you please suggest on this .

Can you please provide a sample project that replicates this?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Update repo

-add service worker
-add structure for theme
-add auth context
-add protected routing
-upgrade plugins

These changes are looking great! Thank you for all of your work on this, Anna!
I have one more general nit-picky comment. Since this is a starting repo, it would be nice to have a pretty clean start to new project. Generally it can be nice to have imports organized. I think the standard we usually follow is:
//group dependency imports alphabetically

//group project imports alphabetically

//process.env constants

//code

Doesn't have to be perfect, but if things start off this way, it's easier to maintain :)

Great idea! Do you use a plugin for the alphabetizing, or do you do it manually?

These changes are looking great! Thank you for all of your work on this, Anna!
I have one more general nit-picky comment. Since this is a starting repo, it would be nice to have a pretty clean start to new project. Generally it can be nice to have imports organized. I think the standard we usually follow is:
//group dependency imports alphabetically

//group project imports alphabetically

//process.env constants

//code

Doesn't have to be perfect, but if things start off this way, it's easier to maintain :)

Great idea! Do you use a plugin for the alphabetizing, or do you do it manually?

This is a good question! The ideal solution would probably be to have an .eslintrc.json file  in the app directory so that all any developer has to do is configure their editor to use eslint on save. If you're up for adding that, that would be amazing! Here's an eslint config that is somewhat close to what we'd want. I've also noticed a couple of other small inconsistent styles like tabs instead of spaces and no new line at the end of files. eslint could automatically fix those things too. There's already an .eslintrc.json in api that could could copy over to app to get started. I may actually add the import settings to that .eslint file now that this has come up.
Otherwise, if you want a quicker solution, a plugin like this one could help!

These changes are looking great! Thank you for all of your work on this, Anna!
I have one more general nit-picky comment. Since this is a starting repo, it would be nice to have a pretty clean start to new project. Generally it can be nice to have imports organized. I think the standard we usually follow is:
//group dependency imports alphabetically

//group project imports alphabetically

//process.env constants

//code

Doesn't have to be perfect, but if things start off this way, it's easier to maintain :)

Great idea! Do you use a plugin for the alphabetizing, or do you do it manually?

This is a good question! The ideal solution would probably be to have an .eslintrc.json file in the app directory so that all any developer has to do is configure their editor to use eslint on save. If you're up for adding that, that would be amazing! Here's an eslint config that is somewhat close to what we'd want. I've also noticed a couple of other small inconsistent styles like tabs instead of spaces and no new line at the end of files. eslint could automatically fix those things too. There's already an .eslintrc.json in api that could could copy over to app to get started. I may actually add the import settings to that .eslint file now that this has come up.
Otherwise, if you want a quicker solution, a plugin like this one could help!

okay so I think I got eslint working in vscode, but I'm not sure if I successfully added it to the app, so definitely let me know if it doesn't appear to be working on your end, and if you notice anything missing!


Longer-term and relation to other RL libraries under Meta

Hi, excited to see this work on distributed RL, building off moolib (and TorchBeast originally). I'm wondering what the longer-term direction of this project is?
Will functionality be merged into TorchRL (which mentions an upcoming IMPALA implementation)? https://github.com/facebookresearch/rl#upcoming-features
Is moolib still being maintained? https://github.com/facebookresearch/moolib/issues/32#issuecomment-1085730793
There are so many RL libraries these days.

Hi, thanks for the interest. Let me provide some of my personal vision of these libs/frameworks.

Moolib is mainly for providing the low-level functionality for distributed ML trainings, not only RL.
RLMeta is a distributed RL framework which is based on moolib and provide high-level distributed RL algorithms for RL search.
TorchRL is mainly a RL lib instead of a framework. The main purpose of TorchRL is to provide official PyTorch implementation for RL components which can be used for other RL frameworks. And because of the timelines and priorities of different teams, TorchRL will be moved to pytorch repo later. Also TorchRL actually merged some of the works in RLMeta. For example the replay buffer is moved from RLMeta. And later we will consider to let RLMeta use TorchRL components.

This is a general high-level vision of the things. We don't want to put all of the things in a single repo but have different repos for different use cases. But to be honest we cannot predict the future, so this is a personal view of the current structure.
Hopefully this can help clarify some of your questions.

Thanks for the insight, looking forward to seeing the development progress! High-quality and easy to use distributed RL code is hard to come by.


Remove unnecessary warnings

Description
Brief Description of the PR:
Fixes # (issue)
Type of change

[x] Bug fix
[ ] New Tutorial
[ ] Updated or additional documentation
[ ] Additional Testing
[ ] New Activation and the changes conform to the activation contribution guidelines
[ ] New Callback and the changes conform to the callback contribution guidelines
[ ] New Image addition and the changes conform to the image op contribution guidelines
[ ] New Layer and the changes conform to the layer contribution guidelines
[ ] New Loss and the changes conform to the loss contribution guidelines
[ ] New Metric and the changes conform to the metric contribution guidelines
[ ] New Optimizer and the changes conform to the optimizer contribution guidelines
[ ] New RNN Cell and the changes conform to the rnn contribution guidelines
[ ] New Seq2seq addition and the changes conform to the seq2seq contribution guidelines
[ ] New Text addition and the changes conform to the text op contribution guidelines

Checklist:

[x] I've properly formatted my code according to the guidelines

[x] By running Black + Flake8
[x] By running pre-commit hooks

[x] This PR addresses an already submitted issue for TensorFlow Addons
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] This PR contains modifications to C++ custom-ops

How Has This Been Tested?
If you're adding a bugfix or new feature please describe the tests that you ran to verify your changes:
*

@shreyashpatodia
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.

@shreyashpatodia
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.

LGTM. I do think we should have some mixin classes to delegate those as we have many optimizer wrappers.
https://github.com/tensorflow/tensorflow/blob/v2.4.0/tensorflow/python/keras/mixed_precision/loss_scale_optimizer.py#L65-L180
https://github.com/tensorflow/tensorflow/blob/v2.4.0/tensorflow/python/keras/mixed_precision/loss_scale_optimizer.py#L816-L922

Split mixin classes in another PR.

LGTM. I do think we should have some mixin classes to delegate those as we have many optimizer wrappers.
https://github.com/tensorflow/tensorflow/blob/v2.4.0/tensorflow/python/keras/mixed_precision/loss_scale_optimizer.py#L65-L180
https://github.com/tensorflow/tensorflow/blob/v2.4.0/tensorflow/python/keras/mixed_precision/loss_scale_optimizer.py#L816-L922

Split mixin classes in another PR.

What Is the status of this?

The PR remove unnecessary warnings which are created by weights can't be found, change to trainable_weights fix it.
@bhack


Static IP address

Edit : Oops !
It was concerning the iGate !
Hi Ricardo,
Not a issue, but an improvement request.
It would be nice to have the choice between DHCP IP address or static. ;-)
73 Patrick TK5EP

Hi Patrick, why is this needed?
This gets in conflict somehow with the OTA part and also the ip could be defined easy in the WiFi router
Saludos,
Ricardo / Richon
(Enviado desde mi celular a tubos)
El 22-07-2023, a las 11:36, Patrick EGLOFF @.***> escribió:

Hi Ricardo,
Not a issue, but an improvement request.
It would be nice to have the choice between DHCP IP address or static. ;-)
73 Patrick TK5EP
—
Reply to this email directly, view it on GitHubhttps://github.com/richonguzman/LoRa_APRS_Tracker/issues/11, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQWBUGVGRAZNTW67KVHRLGDXRPXRFANCNFSM6AAAAAA2T44XII.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi Ricardo,
Why ?
It's sometimes needed in a  private network where there is no DHCP for security reason and you don't have other choice.
Doing it on the device side is much easier than on the router side, as you need to know the MAC Address of the module.  You also need to have a sysop access to the router, which is not always possible.
And when obliged to use static addressing, if there is a conflict with OTA, it's to the user to take care of this.
73 Patrick.


Upgrade to Spring Boot 3

What's going wrong and not working?
The sample application (including chapter-specific applications) should be upgraded to Spring Boot 3, once the final release is available (scheduled for November 2022).
See these resources:

https://spring.io/blog/2022/05/24/preparing-for-spring-boot-3-0
https://spring.io/blog/2022/10/20/spring-boot-3-0-0-rc1-available-now

This will require changes to the ebook, too, wherever a specific Spring Boot version is mentioned or the ebook refers to APIs deprecated with Spring Boot 3 (mainly javax.* and antMatchers()).
Expected outcome
The sample application (including chapter-specific applications) has been upgraded to Spring Boot 3.

See https://github.com/stratospheric-dev/stratospheric/pull/155


teacher forcing

firstly,thanks for your code,it's really helpful to me,but could i know where is the teacher forcing part,thanks again^_^

@zhao1402072392  teacher forcing raito may be used during training. You can have a look at the model.py, where you can find out that the ratio is actually 1. If you want to modify it, you can modify the  decoding procedure during training. That's my opinion.

@zhao1402072392 teacher forcing raito may be used during training. You can have a look at the model.py, where you can find out that the ratio is actually 1. If you want to modify it, you can modify the decoding procedure during training. That's my opinion.

Excuse me, but i have one question. Teacher forcing as you said may be used during training (or validation?). However on testing time no teacher forcing should be used. Am i right? In this implementation there is no use of teacher forcing(?). Correct me if I am wrong. Thanks in advance for your time.


Pixi v4 bug mask?

Hello, in Pixi v3 masks works in additive way (for me is correct) in Pixi v4 they work in exclude mode.
Look at the examples, same code but different results, is a bug? I need the result as in Pixi v3, but i need to use v4.
Thanks 👍
Pixi v4

Pixi v3

http://codepen.io/williammanco/pen/RpYzGV
http://codepen.io/williammanco/pen/xqaoKK

As part of my pixi learing program and my investigation :)
The problem only occurs on webGL renderer.
Graphics are packed and rendered as a single triangle strip:
webGLData.vao.draw(gl.TRIANGLE_STRIP, webGLData.indices.length);
_https://github.com/pixijs/pixi.js/blob/dev/src/core/graphics/webgl/GraphicsRenderer.js#L112_
For above examples, in area of shape intersection, multiple triangles are rendered.
That generates problem in StencilManager:
gl.stencilOp(gl.KEEP, gl.KEEP, gl.INCR);
_https://github.com/pixijs/pixi.js/blob/dev/src/core/renderers/webgl/managers/StencilManager.js#L64_
multiple pass for same area, increments the value in stencil buffer, and that implies false result in test function:
gl.stencilFunc(gl.NOTEQUAL, 0, sms.length);
_https://github.com/pixijs/pixi.js/blob/dev/src/core/renderers/webgl/managers/StencilManager.js#L69_
For example gl.REPLACE here:
gl.stencilOp(gl.KEEP, gl.KEEP, gl.REPLACE);
_https://github.com/pixijs/pixi.js/blob/dev/src/core/renderers/webgl/managers/StencilManager.js#L64_
for above examples, works well, but I don't now yet how and when stencilMaskStack may be longer than one (gl.REPLACE probably will break gl.stencilFunc(gl.NOTEQUAL, 0, sms.length);)
@themoonrat


[fix] IPset fail if set doesn't exist when attempting to add to list

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

/azp run

/azp run


Search previous unexpected behaviour in built-in docs

Godot version:
3.1
Issue description:
When you search something in the documentation of Godot's built-in docs, you can use "Enter" key to search for next occurrence and "Shift + Enter" to search for the previous occourence(you can also use the GUI arrow buttons). When searching for previous a unexpected behaviour occours, rather than shoing the previous result of the search, it shows the first result in previous "segment" of the text(see GIF below).

Steps to reproduce:

Open some doc in the editor
Search something which occours multiple times within each segment of the opened doc
Click the search next arrow until you pass a segment where your search term occoured more than once
Click the search previous arrow and step back through the segment where your search term occoured more than once

Still valid in 825ab3b